Potential bug, .bashrc not read on startup of brand new user with nothing configured

Hello, brand new user to Ghostty excited to try it out. I ran into a problem when first launching ghostty so I thought I'd share since it may impact other new users, of .bashrc not being picked up at first launch. Here are some more details:
OS: MacOS 15.1 (24B2082) (M4)
Install method: brew install ghostty
ghostty --version
Ghostty 1.0.0

Version
  - version: 1.0.0
  - channel: stable
Build Config
  - Zig version: 0.13.0
  - build mode : builtin.OptimizeMode.ReleaseFast
  - app runtime: apprt.Runtime.none
  - font engine: font.main.Backend.coretext
  - renderer   : renderer.Metal
  - libxev     : main.Backend.kqueue

coming from iTerm2
I have absolutely nothing configured in ghostty, just my .bashrc file  located at ~/.bashrc and no ~/.bash_profile . The first few lines of my bashrc file look like this, with more stuff below:
# .bashrc
export HISTSIZE=100000
export HISTFILESIZE=100000
export HISTCONTROL=ignoreboth:erasedups
shopt -s histappend
PROMPT_COMMAND="history -a;$PROMPT_COMMAND"

An unfortunate byproduct of not reading the .bashrc is that my bash_history has been truncated to 500 lines the first time I ran ghostty 😞  , might be good to look into this so other new users don't run into a similar pickle.

forgot to mention, running source ~/.bashrc after the terminal loads from ghostty works.

Hm. Cc @jparise

I'm not able to reproduce this yet, but I'll continue to look for the root cause.
@velicanu, can you say which version of bash you're using so I can continue to narrow down your environment? In particular, it would be helpful to know if this is the default macOS /bin/bash or another version that you've installed via e.g. homebrew.

This is homebrew bash:
m4 ~ $ which bash
/opt/homebrew/bin/bash
m4 ~ $ bash --version
GNU bash, version 5.2.37(1)-release (aarch64-apple-darwin24.0.0)
Copyright (C) 2022 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>

This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

And I assume setting shell-integration = none fixes it?
Also, what permissions do you have set on your .bashrc file?

And I assume setting shell-integration = none fixes it?

It doesn't seem to fix it, I put that line in the config and restarted ghostty but the behavior is the same.

Also, what permissions do you have set on your .bashrc file?

m4 ~ $ ls -tralp .bashrc
-rw-r--r--@ 1 dragosvelicanu  staff  9329 Dec 26 15:53 .bashrc

seems to be default perms that new files get
m4 ~ $ touch mynewfile
m4 ~ $ ls -tralp mynewfile
-rw-r--r--@ 1 dragosvelicanu  staff  0 Dec 27 10:05 mynewfile


could not import name 'jetraw_decode' from 'imagecodecs'

Hello,
I tried to read an image compressed with jetraw, but I have the following error message:
imagecodecs.imagecodecs.DelayedImportError: could not import name 'jetraw_decode' from 'imagecodecs'
I am using imagecodecs 2023.3.16 from Pypi on Windows x64.
Should I install something else (e.g. jetraw binaries)?

It worked! The os.add_dll_directory did the trick. Thank you very much for your help, and for all the work you put into developing this wonderful library.


Added support for custom objects for FormArrays

THIS IS FANTASTIC!! THANK YOU FOR STARTING THIS!!
I needed to be able to pass custom arrays and have it build out the form rather than just simple types. I have added support for the custom object arrays (doesn't work with IEnumerable (at the moment) but works with the basic ClassType[] array type).
I also added a sample angular project to help folks who may be new to Formly to see how to integrate with a client/server approach for dynamic forms and some basic formly templates.
Finally, added a new test case for this new feature and updated the readme.
AGAIN THANK YOU TIMES A BILLION FOR GETTING THIS GOING!!

Thanks for the contribution. I'll take a look soon.


Files inheriting permissions do not show in delta query

Previous discussion that was automatically closed: https://github.com/OneDrive/onedrive-api-docs/issues/1250
Kinda related: https://github.com/OneDrive/onedrive-api-docs/issues/1248
Category

[ ] Question
[ ] Documentation issue
[x] Bug

Expected or Desired Behavior
According to the docs:
By default, the delta query response will include sharing information for all items in the query that changed even if they inherit their permissions from their parent and did not have direct sharing changes themselves

For a directory dir1 containing fileA, changing the permission on dir1 should show fileA in the GET /delta response.
Observed Behavior
Changing permission on a directory does not produce items in the GET /delta query response for files inheriting the directory permission.
Steps to Reproduce

Create directory dir1
Create fileA in dir1
Get the latest delta token via GET /users/{userId}/drive/root/delta?token=latest
Create a shareable link on dir1 giving everyone with the link access.
Get the latest changes via GET /users/{userId}/drive/root/delta?token=<token from step 3>
fileA is not included in the respone

No Prefer: header is provided in any query.

Here is s a related QA Forum question: https://learn.microsoft.com/en-us/answers/questions/1000006/unexpected-drive-delta-query-behavior-with-inherit


[build] Changes for RH build

Adds a dockerfile for the RH UBI build.
Dockerfile uses the Habana base image

Let me go ahead and update it with the latest in our fork

Thanks @Xaenalt

https://github.com/HabanaAI/vllm-fork/pull/602


chore(remove): rox_postgres_datastore

Description

Cleaning some stuff up to remove ROX_POSTGRES_DATASTORE.
User-facing documentation
(must be 2 items and both must be checked)

[ ] CHANGELOG update is not needed
[ ] Documentation PR is created and linked above
[ ] Documentation is not needed

Testing

[ ] inspected CI results

Automated testing
(must be at least 1 item and all items must be checked)

[ ] modified existing tests

How I validated my change

change me!

/retest


Feat/pagination

[nextui]/[pagination]
#103
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] Documentation Only
[ ] Refactor

Description, Motivation and Context

New component Pagination added
Component's a11y improved with the focus state

Screenshots - Animations

Codecov Report

Merging #111 (6c7ebe5) into main (d661d90) will decrease coverage by 0.92%.
The diff coverage is 75.82%.

@@            Coverage Diff             @@
##             main     #111      +/-   ##
==========================================
- Coverage   84.99%   84.06%   -0.93%
==========================================
  Files         117      123       +6
  Lines        2079     2278     +199
  Branches      697      776      +79
==========================================
+ Hits         1767     1915     +148
- Misses        302      351      +49
- Partials       10       12       +2

Impacted Files
Coverage Δ

packages/nextui/src/button/button-group.tsx
100.00% <ø> (ø)

packages/nextui/src/button/button-icon.tsx
100.00% <ø> (ø)

packages/nextui/src/collapse/collapse-icon.tsx
100.00% <ø> (ø)

packages/nextui/src/grid/grid-container.tsx
100.00% <ø> (ø)

...ages/nextui/src/pagination/pagination-ellipsis.tsx
9.09% <9.09%> (ø)

packages/nextui/src/card/card.tsx
77.55% <55.55%> (-5.38%)
:arrow_down:

packages/nextui/src/switch/switch.tsx
88.00% <60.00%> (-3.12%)
:arrow_down:

packages/nextui/src/collapse/collapse.tsx
93.47% <66.66%> (-4.09%)
:arrow_down:

packages/nextui/src/pagination/pagination-item.tsx
68.75% <68.75%> (ø)

packages/nextui/src/checkbox/checkbox.tsx
96.22% <71.42%> (-3.78%)
:arrow_down:

... and 12 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d661d90...6c7ebe5. Read the comment docs.


Deprecate the use of carto

I made carto well before 1.18, and I'd like to sunset it.
All the structs that were created using carto should be made from scratch according to their specific function, since the core functionality of the library is pretty much stable

manager/std/check_result_map.go
manager/std/checker_map.go
manager/std/health_map.go
manager/std/reporter_map.go
reporter/stdout/check_map.go

decided to keep this around for a while


[BUG] If you enable a VLAN NIC after install dashboard stops loading

Describe the bug

If you specify a NIC for the VLAN after install the dashboard stops loading
To Reproduce
Steps to reproduce the behavior:

Install harvester
Go to advanced settings
Edit config for VLAN
Enable then specify second NIC name in interface
Save
Refresh page

Expected behavior

The NIC should save and the dashboard should load
Support bundle

Environment:

Harvester ISO version: master from yesterday
Underlying Infrastructure (e.g. Baremetal with Dell PowerEdge R630): virtualized environment

Additional context
Add any other context about the problem here.
I got the NIC name from ip link in the console/SSH. This was in a KVM virtualized environment using 2 virtIO NICs.

@noahgildersleeve
Didn't understand what problem was encountered. Does it mean that you cannot access the UI after configuring the NIC?
You can add a screenshot to tell me what problem you encountered。

I have the same problem. it got back online after a manual restart of all network-related pods.

Here's the support bundle
bundle.zip

I can also reproduce this issue on my 3-node vagrant environment.

Right now it appears enabling network on management NIC renders the entire cluster non-functional.

Same here as Guang mentioned with the latest master image.

The root cause is because the first management NIC name is set as the default canal iface, it will make the cluster network dysfunctional if the other node has a different management NIC name, a temporary solution is to set the flannel.iface config to empty and use the default route config.
kubectl edit helmchartconfigs.helm.cattle.io rke2-canal -n kube-system # and set spec.valuesContent.flannel.iface to ""

A proper fix will be addressed via https://github.com/harvester/harvester/issues/1207 with using the bond NIC.

and multi NICs case is fixed via https://github.com/harvester/harvester/issues/1259

Tested in master-1a041d23-head with 2 NICs on 2 node cluster. Fixed.


Shell Script step fails with OSX build agent "Input required: cwd"

I'm having an issue with a bash shell script failing on my OSX build agent. Here are the logs:
##[Debug] 2016-02-12T01:52:48.004Z: scriptPath: /Users/burstingsilver/myagent/_work/2/s/tools/BuildUtilites/Set-iOSVersionNumber.sh
##[Debug] 2016-02-12T01:52:48.005Z:
##[Debug] 2016-02-12T01:52:48.005Z: args:
##[Debug] 2016-02-12T01:52:48.005Z: cwd:
##[Debug] 2016-02-12T01:52:48.005Z: failOnStandardError: false
##[Debug] 2016-02-12T01:52:48.005Z:
##[Debug] 2016-02-12T01:52:48.009Z: cwd: /Users/burstingsilver/myagent/_work/2/s
##[Debug] 2016-02-12T01:52:48.148Z: check path : /Users/burstingsilver/myagent/_work/tasks/ShellScript/1.0.15/task.json
##[Debug] 2016-02-12T01:52:48.149Z: set resource file to: /Users/burstingsilver/myagent/_work/tasks/ShellScript/1.0.15/task.json
##[Debug] 2016-02-12T01:52:48.149Z: system.culture=en-US
##[Debug] 2016-02-12T01:52:48.149Z: load strings from: /Users/burstingsilver/myagent/_work/tasks/ShellScript/1.0.15/task.json
##[Debug] 2016-02-12T01:52:48.149Z: load loc strings from: /Users/burstingsilver/myagent/_work/tasks/ShellScript/1.0.15/strings/resources.resjson/en-US/resources.resjson
##[Debug] 2016-02-12T01:52:48.150Z: check path : /bin/bash
##[Debug] 2016-02-12T01:52:48.151Z: bash=/bin/bash
##[Debug] 2016-02-12T01:52:48.151Z: load strings from: /Users/burstingsilver/myagent/_work/tasks/ShellScript/1.0.15/node_modules/vsts-task-lib/lib.json
##[Debug] 2016-02-12T01:52:48.151Z: load loc strings from: /Users/burstingsilver/myagent/_work/tasks/ShellScript/1.0.15/node_modules/vsts-task-lib/strings/resources.resjson/en-US/resources.resjson
##[Debug] 2016-02-12T01:52:48.152Z: task result: Failed
##[Error] 2016-02-12T01:52:48.156Z: Input required: cwd
##[Error] 2016-02-12T01:52:48.156Z:

I am absolutely clueless on how to resolve this issue. My script takes no arguments. Can someone help?

As a workaround, can you try setting the task input Working Directory under the advanced section for the task inputs.

Thanks, that's helpful!

Did that workaround your issue? If so, it sounds like something broke for this task running on an xplat agent. I couldn't repro the issue on a Windows agent.

I'll investigate ...

Yeah, the workaround allows the bash script to run without issue.

I just experienced the same issue as Dylan. The work around solved the problem from me as well.

I'll fix this today - fell off my radar

This is fixed in the sprint that will roll out in the next couple of weeks

I am getting below error while building in VSTS
2017-10-01T17:47:53.6039080Z ##[debug]Evaluating condition for step: 'Transform deploy.yaml'
2017-10-01T17:47:53.6060950Z ##[debug]Evaluating: succeeded()
2017-10-01T17:47:53.6079460Z ##[debug]Evaluating succeeded:
2017-10-01T17:47:53.6105680Z ##[debug]=> (Boolean) True
2017-10-01T17:47:53.6125390Z ##[debug]Expanded: True
2017-10-01T17:47:53.6146430Z ##[debug]Result: True
2017-10-01T17:47:53.6164880Z ##[section]Starting: Transform deploy.yaml
2017-10-01T17:47:53.6226700Z ==============================================================================
2017-10-01T17:47:53.6245790Z Task         : Command Line
2017-10-01T17:47:53.6261440Z Description  : Run a command line with arguments
2017-10-01T17:47:53.6274170Z Version      : 1.1.3
2017-10-01T17:47:53.6286310Z Author       : Microsoft Corporation
2017-10-01T17:47:53.6299210Z Help         : More Information
2017-10-01T17:47:53.6312250Z ==============================================================================
2017-10-01T17:47:53.8964120Z ##[debug]agent.workFolder=/opt/vsts/work
2017-10-01T17:47:53.8992840Z ##[debug]loading inputs and endpoints
2017-10-01T17:47:53.9023580Z ##[debug]loading INPUT_FILENAME
2017-10-01T17:47:53.9045180Z ##[debug]loading INPUT_ARGUMENTS
2017-10-01T17:47:53.9069790Z ##[debug]loading INPUT_WORKINGFOLDER
2017-10-01T17:47:53.9093410Z ##[debug]loading INPUT_FAILONSTANDARDERROR
2017-10-01T17:47:53.9117040Z ##[debug]loading ENDPOINT_AUTH_SYSTEMVSSCONNECTION
2017-10-01T17:47:53.9139960Z ##[debug]loading ENDPOINT_AUTH_SCHEME_SYSTEMVSSCONNECTION
2017-10-01T17:47:53.9162780Z ##[debug]loading ENDPOINT_AUTH_PARAMETER_SYSTEMVSSCONNECTION_ACCESSTOKEN
2017-10-01T17:47:53.9187770Z ##[debug]loading SECRET_CONTAINER_USERNAME
2017-10-01T17:47:53.9210390Z ##[debug]loading SECRET_CONTAINER_PASSWORD
2017-10-01T17:47:53.9231730Z ##[debug]loaded 9
2017-10-01T17:47:53.9258970Z ##[debug]check path : /opt/vsts/work/_tasks/CmdLine_d9bafed4-0b18-4f58-968d-86655b4d2ce9/1.1.3/task.json
2017-10-01T17:47:53.9328990Z ##[debug]set resource file to: /opt/vsts/work/_tasks/CmdLine_d9bafed4-0b18-4f58-968d-86655b4d2ce9/1.1.3/task.json
2017-10-01T17:47:53.9358080Z ##[debug]system.culture=en-US
2017-10-01T17:47:53.9384230Z ##[debug]filename=bash
2017-10-01T17:47:53.9407200Z ##[debug]check path : /bin/bash
2017-10-01T17:47:53.9431470Z ##[debug]bash=/bin/bash
2017-10-01T17:47:53.9455140Z ##[debug]workingFolder=/opt/vsts/work/1/s
2017-10-01T17:47:53.9481670Z ##[debug]testing directory '/opt/vsts/work/1/s'
2017-10-01T17:47:53.9509520Z ##[debug]arguments=-c "sed -i ‘s/$BUILD_ID/22/; s/$ACR_DNS/saviantkubernetespoc.azurecr.io/’ deploy.yaml"
2017-10-01T17:47:53.9537120Z ##[debug]/bin/bash arg: -c "sed -i ‘s/$BUILD_ID/22/; s/$ACR_DNS/saviantkubernetespoc.azurecr.io/’ deploy.yaml"
2017-10-01T17:47:53.9563440Z ##[debug]failOnStandardError=false
2017-10-01T17:47:53.9586240Z ##[debug]exec tool: /bin/bash
2017-10-01T17:47:53.9607470Z ##[debug]Arguments:
2017-10-01T17:47:53.9631750Z ##[debug]   -c
2017-10-01T17:47:53.9657510Z ##[debug]   sed -i ‘s/$BUILD_ID/22/; s/$ACR_DNS/saviantkubernetespoc.azurecr.io/’ deploy.yaml
2017-10-01T17:47:53.9676680Z [command]/bin/bash -c sed -i ‘s/$BUILD_ID/22/; s/$ACR_DNS/saviantkubernetespoc.azurecr.io/’ deploy.yaml
2017-10-01T17:47:53.9695610Z sed: -e expression #1, char 1: unknown command: `�'
2017-10-01T17:47:53.9714010Z /bin/bash: s//saviantkubernetespoc.azurecr.io/’: No such file or directory
2017-10-01T17:47:53.9737360Z ##[debug]rc:127
2017-10-01T17:47:53.9759280Z ##[debug]success:false
2017-10-01T17:47:53.9856820Z ##[error]/bin/bash failed with return code: 127
2017-10-01T17:47:53.9870490Z ##[debug]Processed: ##vso[task.issue type=error;]/bin/bash failed with return code: 127
2017-10-01T17:47:53.9893290Z ##[debug]task result: Failed
2017-10-01T17:47:53.9931920Z ##[error]/bin/bash failed with error: /bin/bash failed with return code: 127
2017-10-01T17:47:53.9945150Z ##[debug]Processed: ##vso[task.issue type=error;]/bin/bash failed with error: /bin/bash failed with return code: 127
2017-10-01T17:47:53.9980210Z ##[debug]Processed: ##vso[task.complete result=Failed;]/bin/bash failed with error: /bin/bash failed with return code: 127
2017-10-01T17:47:54.0007170Z ##[section]Finishing: Transform deploy.yaml
Can anyone help me?

FYI, this still happens:
##[section]Starting: AzureCLI
==============================================================================
Task         : Azure CLI
Description  : Run Azure CLI commands against an Azure subscription in a PowerShell Core/Shell script when running on Linux agent or PowerShell/PowerSheell Core/Batch script when running on Windows agent.
Version      : 2.0.3
Author       : Microsoft Corporation
Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/deploy/azure-cli
==============================================================================
[command]/usr/local/bin/az --version
WARNING: You have 2 updates available. Consider updating your CLI installation.
azure-cli                         2.0.75 *

command-modules-nspkg              2.0.3
core                              2.0.75 *
nspkg                              3.0.4
telemetry                          1.0.4

Python location '/usr/local/Cellar/azure-cli/2.0.75/libexec/bin/python'
Extensions directory '/Users/runner/.azure/cliextensions'

Python (Darwin) 3.7.5 (default, Nov  1 2019, 02:16:32)
[Clang 11.0.0 (clang-1<IP_ADDRESS>)]

Legal docs and information: aka.ms/AzureCliLegal

Setting AZURE_CONFIG_DIR env variable to: /Users/runner/runners/2.160.0/work/_temp/.azclitask
##[error]Script failed with error: Error: Input required: connectedServiceNameARM
##[section]Finishing: AzureCLI

The workarounds don't seem to help.


Quick-Scope like functionality.

Over at LunarVim we are wanting to integrate lightspeed, some users also want to have quick-scope installed, but this is vim-script only.
Would this functionality be something you'd consider adding to lightspeed (or accepting a patch for)..
It would be great to have the one lightspeed plugin to rule them all.

First, I'm really glad that you like the plugin and are considering adding it to LunarVim!
Regarding quick-scope, however, I don't think I'll ever want to add such a feature, even as opt-in. quick-scope looks very impressive at first, but I have uninstalled it after a day or so. IMHO, it is based on a flawed idea: it creates disorienting visual noise all the time, just for helping out in the few occasions when one wants to do an f/t-jump inside a line. Even the static highlighting is disorienting a bit, but those flashing letters at every single cursor movement amount to an untenable trade-off. And I'm not even sure it helps so much - if you want to target a word, it is much easier on the brain to just enter the 1-2 random characters your eyes catch first, than to process those highlighted "beacons". Sometimes the former might be slower by a fraction of a second, if you have to press repeat (1-char search) or type a label (2-char search), but that doesn't matter, because it is less cognitive load, and that is ultimately much more important.

@ggandor Many thanks for your detailed explanation and thought process when looking into this concept..
I'll forward a link to this on our thread about this.
I agree with what you are saying, and it is probably best to get new users to start thinking about their motion in the way you describe.


Change Dataset#each_statement to Dataset#each

to keep with description in RDF::Enumerable.
Fixes #365.

Coverage decreased (-0.3%) to 91.224% when pulling e03a94d262b137b15bd4bd21fef7bfc4f4fb5f7d on feature/dataset-each into da525ad24ff7a262d756c02d438640ea6cf9aed2 on develop.

Coverage decreased (-0.3%) to 91.224% when pulling e03a94d262b137b15bd4bd21fef7bfc4f4fb5f7d on feature/dataset-each into da525ad24ff7a262d756c02d438640ea6cf9aed2 on develop.

Coverage decreased (-0.3%) to 91.224% when pulling e03a94d262b137b15bd4bd21fef7bfc4f4fb5f7d on feature/dataset-each into da525ad24ff7a262d756c02d438640ea6cf9aed2 on develop.


fix: key exposed in api call, closes #1152

Fixes #1152

@kyranjamie Please add the tests from here: https://github.com/friedger/stacks.js/commit/f51614c4eff2ad4a00edcc34c5ef10ffb3cbd3ae


Spam boxes does not work i use it today and it just did Made By Gliz

it just does not work on the new box sorry.

@glixxzzy if you made the boxes automated instead of manual, it would work


[cdc] CDC between clk_spi_in_buf and clk_spi_out_buf

Two signals which come from clk_spi_in_buf and clk_spi_out_buf seem to be propagated to the same destination logic.

#13108 should help with that :smile:

can I get access to this deck?

I reviewed #13108. It seems to include FPGA constraint to resolve timing issue on clk_spi_in_buf and clk_spi_out_buf in that both clocks come from the same source clk_spi_out_muxed and generated through different clock buffers. I am not clear of How they are handled in ASIC and SDC. Can you help me to understand?

This CDC issue is related to https://github.com/lowRISC/opentitan/issues/13155.

Hm... actually, is the tool confused by all of this?
We have the generated clocks that relate clk_spi_in_buf and clk_spi_out_buf here: https://github.com/lowRISC/opentitan/blob/master/hw/top_earlgrey/syn/chip_earlgrey_asic.sdc#L212-L215 . What rule is their relationship violating? They should be timed, as they have the same source.
Then clk_spi_out_buf and sys_clk are marked as asynchronous groups here:
https://github.com/lowRISC/opentitan/blob/master/hw/top_earlgrey/syn/chip_earlgrey_asic.sdc#L417-L426
That said, the CDC for the TPM access reg looks busted to me. I'm not seeing anything that either holds the sys_clk value stable to meet timing or has synchronizing flops to push away from metastable output.

@a-will thanks for reply. The rule is W_MASYNC - reports crossings that are being driven by multiple asynchronous transmit clock domains.
== general description =============================================
CDC signals in the design are in multiple clock domains. The following situations are reported:
A signal entering a clock domain is dependent upon two or more different clock domains.
An output signal is dependent upon two or more clock domains.
A W_MASYNC on a CNTL implies cross-domain control that may lead to data stability errors.
Suggested Action : Run either formal verification or SimPortal to verify that the W_MASYNC condition does not lead to data stability errors.
CDC between clk_spi_in_buf and clk_spi_out_buf : I think the tool somehow seems not to recognize the timed clock constraint in ASIC SDC.
CDC between clk_spi_out_buf and sys_clk : I agree because of no synchronization across async clock domains.

@jeoongp is the tool really misunderstanding paths between clk_spi_in_buf and clk_spi_out_buf? or is the sys_clk the main issue?

Category 1) CDC between clk_spi_in_buf and clk_spi_out_buf : yes, I think it's the tool issue..
Category 2) CDC between clk_spi_out_buf and sys_clk : it's a potential RTL issue..

RuleDataID 1329 (one sample) : ReceivingFlop : top_earlgrey.u_spi_device.u_memory_2p.u_mem.gen_generic.u_impl_generic.mem[129][35:0]
As I dug RuleDataID 1329, it is not a category 1 issue (CDC between clk_spi_in_buf and clk_spi_out_buf).
The generic memory module is designed as follows.
https://github.com/lowRISC/opentitan/blob/master/hw/ip/prim_generic/rtl/prim_generic_ram_2p.sv#L75-L103
Two flip flops are accessing the same memory cells. These errors will be gone if we choose ASIC libs instead of the FPGA generic.

Category 1 : We are looking for a tool support to treat this dual-port sram as a black box and generate a mesh model.
Real Intent Roger and Oren are working with us.
Category 2 : I will create a new ticket to track this potential RTL issue

Churning out 1k W_MASYNC errors with two interim solutions while waiting for the tool support to recognize bit-masked memory.

Black-boxing dual port SRAM
Removing bitmask as a CDC model only

@jeoongp i think this specific issue is closed right? can we close this one..?

@tjaychen no problem. AEs are still looking for a tool support. I will keep you posted.

No problem. The PR https://github.com/lowRISC/opentitan/pull/13462 was approved but not merged. I have no permit to merge.. Can you merge it? If any CDC issue in this dual port sram, we can reopen this ticket.

sounds good, thanks @jeoongp


Bug 1192645: Fix error in the compatibility validation viewer.

I haven't been able to test this locally. I've never been able to get the compat validator to run anywhere but on production, and the viewer explodes if you try to get it to run with fake compatibility results.
I tested the individual pieces of this code when I made this change, so aside from the missing .prototype, it should work. But I really wish I had a way to test it properly.

Scratch that. After about a dozen attempts, I managed to get the standalone compatibility tester running.

r+wc


Make sure that we don't have more holidays than the ones tested.

We have tests that makes sure of the correct holidays for a given year.
However we don't have a way to assert all present days are tested. We don't test if days are present that shouldn't be there.
I wish we could have a set of holidays that should be present and compare that we don't have some that shouldn't be present.

One solution : instead of doing
holidays = holidays_set()
self.assertIn(date(2013, 12, 25), holidays)  # Christmas
# ...

we could do:
self.assertEqual(holidays_set(), {
    date(2013, 12, 25),  # Christmas
    # ...
})

This only works if you're testing all the holidays, but I assume it's what you do in these tests.

If you look at the tests especially Germany you will see that it is not necessarily that easy but I agree with you that we could go simple here and just validate a set.


feat: sticky header in series and spotlight.

Thank you for your contribution to the KodaDot NFT gallery.
👇 _ Let's make a quick check before the contribution.
PR type

[ ] Bugfix
[x] Feature
[ ] Refactoring

What's new?

[x] PR closes #2353
[x] see the 1st comment I added below

Before submitting Pull Request, please make sure:

[x] My contribution builds clean without any errors or warnings
[x] I've merged recent default branch -- main and I've no conflicts
[x] I've tried to respect high code quality standards
[x] I've didn't break any original functionality
[x] I've posted a screenshot of demonstrated change in this PR

Optional

[ ] I've tested it at </rmrk/collection/26902bc2f7c20c546a-1FVG7>
[x] I've tested PR on mobile and everything seems works
[ ] I found edge cases
[ ] I've written some unit tests 🧪

Had issue bounty label?

[x] Fill up your KSM address: Payout

Community participation

[x] Are you at KodaDot Discord?

Screenshot

[x] My fix has changed sticky header in series and spotlight on UI; a screenshot is best to understand changes for others.
see the 1st comment I added below

the docs I followed when finishing the task: Table | Buefy.

page/platform
Web
Mobile

/series
:white_check_mark:
:white_check_mark:

/spotlight
:white_check_mark:
:x:

Preview:
series on Web:
https://user-images.githubusercontent.com/31362988/154210050-266f8bcc-9038-4a9d-8d22-33a2c5bfebba.mov
spotlight on Web:
https://user-images.githubusercontent.com/31362988/154211743-b315ddb2-05e9-4bbf-a09b-7a4bd3b04f8d.mp4
series on Mobile:
https://user-images.githubusercontent.com/31362988/154209923-9df4b3be-d0a1-4a40-bbce-89724d8c54d8.mov
The spotlight on Mobile is hard to implement.
two reasons:

strange behavior caused by tooltip

https://user-images.githubusercontent.com/31362988/154212359-6be44657-a361-445f-b490-8b1e90a851ca.mov

oh, I guess for mobile we should stick with the native buefy table component which is already there :)

Something is broken there

Seems same bug for spotlight

I guess we can also add more results into the series, like bumping it to 200. As there will be lots of collections coming:)

I guess we can also add more results into the series, like bumping it to 200. As there will be lots of collections coming:)

It's breakpoint issue, and maybe you need change your system preference: try set scrolling to always:

huh, we will ask users to change their settings to use our page? :)
you've posted me showing scrollbars, that's not the issue.
The issue it's not showing the whole content of results and in your PR it seems broken, we need to find out why:)
This is how it should look like, screenshot from https://beta.kodadot.xyz which is main branch :)

@yangwao the same issue found in https://beta.kodadot.xyz/, there is an empty space left when I resize my window to 25%.

and we have pagination for it, so more items may take a long time to load.

https://beta.kodadot.xyz

I agree with it, but there is also an outer scrollbar, so we need to scroll back to see what the column name is.
is this the expected behavior?

I would change $table-sticky-header-height size (default is 300px)

I agree with it, but there is also an outer scrollbar, so we need to scroll back to see what the column name is.
is this the expected behavior?

@yangwao the same issue found in beta.kodadot.xyz, there is an empty space left when I resize my window to 25%.

yes, because you have only 10 items set to show :)

@yangwao Yes, I see 🙈
So any ideas for this issue, just double the table sticky header height from 300px to 600px?

@yangwao Yes, I see 🙈
So any ideas for this issue, just double the table sticky header height (from 300px to 600px)?

Remove fixed height of content :)
I see that sticky prop is cutting height which is unwanted
https://buefy.org/documentation/table/

@yangwao Yes, it limits the table height to 300px as @roiLeo said.
but if no fixed height (even overwrite the default value) , it's hard to position the table with sticky.

but if no fixed height (including overwrite the default value) , it's hard to position the table with sticky.

Try this on table header:
top: 120px;
position: sticky;
background-color: #090909;

but if no fixed height (including overwrite the default value) , it's hard to position the table with sticky.

Try this on table header:
top: 120px;
position: sticky;
background-color: #090909;

@roiLeo it works well on PC 👍, I will figure out how to do this on mobile.

but if no fixed height (including overwrite the default value) , it's hard to position the table with sticky.

Try this on table header:
top: 120px;
position: sticky;
background-color: #090909;

@roiLeo it works well on PC 👍, I will figure out how to do this on mobile.

on mobile, we don't need sticky header 🥺

Sorry for misunderstood.
https://user-images.githubusercontent.com/31362988/154377737-ef0074bb-bd6f-4289-bec6-6105806476a0.mov
The image is so cute when scrolling, is it allowed?

@yangwao
the CI is broken because incompatible node version, I have upgraded node version to 16.14.0 on my local machine, and run lint, it works:

I will update my forked repo (instead of merging the main branch) and submit a new PR to check if CI works.

New PR still failed, I found the reason for it:
The node version is cached by CI (setup-node action), so even if we upgraded it on our codebase, it will still use cached node version 16.13.2
How to fix it?
Set check-latest flag to true

@roiLeo got it

pay 100 usd

😍 Perfect, I’ve sent the payout
💵 $100 @ 163.58 USD/KSM ~ 0.611 $KSM
🧗 H2DifyJqaansQREdGFU4BxZyaApbkCgP1a9Pq4xKaebSFZh
🔗 0xdf8eaeb1b335e02783eaeea11bbe91bb74a9b00001efcdfb22cd50ee0eda6ced
🪅 Let’s grab another issue and get rewarded!
🪄 github.com/kodadot/nft-gallery/issues


Plugin types not visible on Probot instance

Bug Report
Current Behavior
The probot instance using a custom Octokit does not inherit the types added by plugins.
// plugin.ts
import { ProbotOctokit } from 'probot';

export function plugin(octokit: InstanceType<typeof ProbotOctokit>) {
  return {
    methods: {
      // plugin methods
      itWorks: async () => {}
    },
  };
}

export const MyOctokit = ProbotOctokit.plugin(plugin);

import { NextApiRequest, NextApiResponse } from "next";
import { createNodeMiddleware, createProbot, Probot } from "probot";
import { MyOctokit } from "./plugin";

const app = (bot: Probot) => {
  bot.on('issues', async (context) => {

    // Property 'methods' does not exist on type 'Octokit & { retry: { retryRequest: (error: RequestError, retries: number, retryAfter: number) => RequestError; }; } & { paginate: PaginateInterface; } & RestEndpointMethods & Api & API'
    context.octokit.methods.itWorks();
  })
};

async function handler(req: NextApiRequest, res: NextApiResponse) {
  const bot = createNodeMiddleware(app, {
    probot: createProbot({
      defaults: {
        Octokit: MyOctokit,
      },
    }),
    webhooksPath: '/api/github/webhooks',
  });

  bot(req, res);
}

export default handler;

Expected behavior/code
Context has the proper type information about the methods added using plugins:
const app = (bot: Probot) => {
  bot.on('*', async (context) => {
    // no type error
    context.octokit.methods.itWorks();
  })
};

Environment

Probot version(s): v12.2.1
Node/npm version: Node 16
OS: macOS 12.1

Can you please check if the problem also occurs with @octokit/core: https://github.com/octokit/core.js/
It would be a better place to file an issue.
If I recall correctly, there is a problem when using the throttle plugin that breaks types for some reason that I couldn't figure out. The types are fairly complicated

@octokit/core works as expected:
// plugin.ts
import { ProbotOctokit } from 'probot';

export function plugin(octokit: InstanceType<typeof ProbotOctokit>) {
  return {
    methods: {
      // plugin methods
      itWorks: async () => {}
    },
  };
}

export const MyOctokit = ProbotOctokit.plugin(plugin);

const myoctokit = new MyOctokit();

// no type errors here
myoctokit.methods.itWorks();

I think that the problem originates in the way the types in the Probot instance are propagated. For instance, the octokit's type in Context does not seem to take into account the types provided in the Options, but assumes ProbotOctokit.


Fixes locale setting including UTF8

It wasn't working on linux after last update, missing parameter on setlocale()

I am getting this error around locale, maybe he is referring to this? I am on Linux as well.

I am getting this error around locale, maybe he is referring to this? I am on Linux as well. UPDATE: Using @alceasan 's fix, the error in the screenshot below goes away.

Thanks @bricep , that's the error I was having.
Aside from this problem, after the recent changes it's always forcing the locale of the country based on the IP adddress, the arguments for country and language are always overriden.

Thanks for all your messages. I see on the code that a PR changed some things so args no longer works. I'll fix that.
For locales, this PR is not the right way to fix the issue. It really depends on the computer you're using, it's not always with .utf8 (and even not on Windows). I'll fix that to work on all computers.

Fix it the right way !

It isn't working form me


Dots in the table names

What steps will reproduce the problem?
Set up an active record for a table contains dots in the name (Yes, ms sqlserver table names can has a dots like this: [SRV_NAME].[DB_NAME].[SCHEMA_NAME].[TABLE.NAME.WITH.A.LOT.OF.DOTS.]).
What is the expected result?
Nothing too bad.
What do you get instead?
Database Exception.
resolveTableNames method in yii\db\mssql\Schema treats every dot like qualifier delimiter.
Additional info

Q
A

Yii version
<IP_ADDRESS>

PHP version
7.2

Operating system
Win srv 2012 r2

See https://github.com/yiisoft/yii2/pull/17408#issuecomment-507680530


Test Issue

Description:

[x] thing 1
[x] thing 2
[ ] thing 3

DoD:

[x] thing 1
[x] thing 2
[ ] thing 3

Comment 1


Add a "hello world" test

In an attempt to learn how to use this library, I tried to port https://github.com/dr-m/hellovm to it.
Apparently I am doing something wrong, because both the interpreter and the compiler front-end are triggering a SIGSEGV when trying to invoke the generated code, on AMD64. Is the problem simply that I am reusing some registers, that is, violating the SSA (static single assignment) form? I understand that adding diagnostics (even as a compile-time option) could be against the goals of this project.
Because no other test is covering the function MIR_new_call_insn(), this program (once it has been cleaned up) could be a useful addition to the built-in test suite.

The problem with the code is wrong place of func and return value.  Call insn operands are:
proto
called function
return value
args
With the right place of called func and return value operands, you code works as expected.

Thank you for your help! I updated the program based on your advice. I realize that there is not much that can be done to protect against this type of a mistake, because unlike LLVM IR, MIR has rather liberal implicit type casts.
The program now almost works in both interpreted and compiled mode (selected by modifying the #if in the source code).
LANG=C make hello-test
gcc -I. -fPIC -g -std=gnu11 -Wno-abi -fsigned-char -fno-tree-sra -fno-ipa-cp-clone -O3 -DNDEBUG -DMIR_PARALLEL_GEN  mir.o mir-gen.o mir-tests/hello.c -o ./hello-test -lm -ldl -lpthread && ./hello-test
hello
world
goodbye
world
make: *** [GNUmakefile:354: hello-test] Error 26

The 26 is the number of characters written. Actually, I intended it to write "all" as the last word. I will debug and fix that later.
Which command line option would you prefer for specifying whether to use the interpreter or the generator? How would you suggest to modify this to look and feel more like the existing tests or examples? I see that there are .expect files only in c-tests, none in mir-tests.

I implemented a simple command line parser, modelled after mir-tests/run-test.c. By default, the program will dump the generated MIR code. With the option -i or -g the generated code will be executed either in interpreted or generated form.

Thank you for the test.  You've chosen the right directory for the test.  I've merged your PR.

Thank you very much!


pureUsePlatformOptimizations: add stdenv adapter

Motivation for this change
This allows one to force a compiler to use optimizations for a particular architecture (for example "sandybridge" or "skylake-avx512").
The resulting binaries won't work on the older or incomparible architecture (likely will crash with "Invalid instruction").
Contrary to impureUseNativeOptimizations of https://github.com/NixOS/nixpkgs/pull/37600,
this adapter does not break purity and allows to prepare a NixOps deployment specifying exact CPU architecture of each node,
so it might become the default one day.

This pull request has been mentioned on Nix community. There might be relevant details there:
https://discourse.nixos.org/t/targeting-particular-x86-64-generation-haswell-ivybridge-skylake/2280/5

I feel like these should be handled by cc-wrapper. That is if you pass something like --arg localSystem '{ arch = "native"; }' you should just automatically get the "impureUsePlatformOptimizations" likewise with whatever other thing. These are called "gcc" but they really aren't gcc specific. Both Clang and GCC support these flags.
Anyway, this is probably okay for now to avoid mass rebuild, but there's definitely room for further integration with cc-wrapper. In the same way, that platform-flags.nix should go as it just sets the default gcc values, but they can be changed at any time, so they are just costly rebuilds just to set defaults.

Agree with Matt, except native still shouldn't be used. That said this is a fine stop-gap in the meantime.

These are called "gcc" but they really aren't gcc specific. Both Clang and GCC support these flags.

Actually, they are.
cmake have similar TARGET_ARCHITECTURE which is different (for example it uses "sandy-bridge" instead of "sandybridge"). And there is also Microsoft Visual C++ with own flags.
So gcc seems to be a good name for noting that architecture should be specified as for GCC and "Clang in GCC-compatible mode" (Clang has also a MSVC-compatible)

Anyway, this is probably okay for now to avoid mass rebuild, but there's definitely room for further integration with cc-wrapper.

Just to not for those who will do the mass-rebuild change, this hack
https://github.com/NixOS/nixpkgs/blob/663bfb1/pkgs/development/compilers/gcc/8/default.nix#L280
coule be handled by specifing gcc.arch for "i386-linux", "i586-linux", "i686-linux" platforms

cc @dylex for their attempt to use gcc.arch which had no effect

One more argument for moving -march=${stdenv.hostPlatform.platform.gcc.arch}  to cc-wrapper:
this -march= should have lower priority than -march= explicitly set by the build process.
For example, openblas compiles some source files with -march=skylake-avx512
Curretly -march=sandybridge (or any particular arch from gcc.arch) overwrites it so the build of openblas fails if gcc.arch points to an older arch than skylake-avx512
Giving -march=${stdenv.hostPlatform.platform.gcc.arch} less prio would allow to enable this hook globally, so the whole derivation with non-empty platform.gcc.arch will be optimized for a particular CPU architecture (in a Gentoo style).

It seems difficult to implement this correctly as an adapter.
At least requiredSystemFeatures = [ "gccarch-${stdenv.hostPlatform.platform.gcc.arch}" ]; should infect all ````mkDerivations, including for example python37.stdenv.mkDerivation, etc. Skipping one of them results in crash "Invalid instruction"```.
So it is better to be made as a patch to stdenv


tasks.test is up-to-date even if the output of tasks.prepareTestingSandbox has changed

Inspired by the FAQ I have some code in build.gradle.kts which installs custom artifacts in my plugin home directory:
tasks.prepareTestingSandbox {
    from(customPluginArtifacts) {
        into(intellij.pluginName)
    }
}

The problem is that the outputs of the prepareTestingSandbox task are not modeled as inputs to the test task. I.e., in my example, if the customPluginArtifacts change, then the test task remains up-to-date and is skipped.
It was easy for me to fix it by adding this line:
tasks.test {
    inputs.files(tasks.prepareTestingSandbox)
}

However, I wonder if the gradle-intellij-plugin should always add this dependency automatically. What do you think?

Hi. Sounds reasonable, let's try to do that


How would I make a fixed rod between two bodies?

Aren't constraints what you are looking for?

Yeah sounds like it, check out the constraints demo and the code.


FIX: update spm version to 2018b

SPM12's dev version was linking to version 2018a. But the corresponding file under this link seems to be 2018b.
This PR updates the version where necessary.

thanks for the pr @miykael - the 2018b mcr url will have to be added to the mcr template https://github.com/kaczmarj/neurodocker/blob/master/neurodocker/templates/matlabmcr.yaml
and the mcr version (it is 95) will have to be added here https://github.com/kaczmarj/neurodocker/blob/f52d03d2690996ddc67633f23a249b987feb5b0a/neurodocker/interfaces/interfaces.py#L140-L155

Codecov Report

Merging #227 into master will decrease coverage by 3.24%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #227      +/-   ##
==========================================
- Coverage   80.95%   77.71%   -3.25%
==========================================
  Files          33       33
  Lines        1512     1512
  Branches      156      156
==========================================
- Hits         1224     1175      -49
- Misses        213      264      +51
+ Partials       75       73       -2

Impacted Files
Coverage Δ

neurodocker/interfaces/tests/test_convert3d.py
70% <0%> (-30%)
:arrow_down:

neurodocker/interfaces/tests/test_petpvc.py
70% <0%> (-30%)
:arrow_down:

neurodocker/interfaces/tests/test_neurodebian.py
70% <0%> (-30%)
:arrow_down:

neurodocker/interfaces/tests/test_spm12.py
70% <0%> (-30%)
:arrow_down:

neurodocker/interfaces/tests/test_dcm2niix.py
70% <0%> (-30%)
:arrow_down:

neurodocker/interfaces/tests/test_minc.py
70% <0%> (-30%)
:arrow_down:

neurodocker/interfaces/tests/test_mrtrix.py
70% <0%> (-30%)
:arrow_down:

neurodocker/interfaces/tests/test_freesurfer.py
70% <0%> (-30%)
:arrow_down:

neurodocker/interfaces/tests/test_fsl.py
70% <0%> (-30%)
:arrow_down:

neurodocker/interfaces/tests/test_miniconda.py
70% <0%> (-30%)
:arrow_down:

... and 3 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f52d03d...dbf7fad. Read the comment docs.

Thanks @kaczmarj , I added the proposed changes. I hope the tests pass now.

this looks great, thank you so much @miykael!

Thank you for neurodocker :-)


Salesforce is requiring an upgrade to TLS 1.1 or higher by July 22, 2017

Hi
Just to confirm if the latest version already address the TLS 1.1 or higher  requirement of Salesforce?
https://help.salesforce.com/articleView?id=Salesforce-disabling-TLS-1-0&language=en_US&type=1
Thank you
Limber jaimes

As far as I know, no. Our workaround is to call the following before calling AuthenticationClient methods:
ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12 | SecurityProtocolType.Tls11 | SecurityProtocolType.Tls;

Latest version is broken without this workaround! Using the sample WebServerOAuthFlow.Web project, just adding @avesse 's line of code in CallbackController.Get will work.
Also, the client doesn't handle the HTML response page about the TLS error because it only parses json.
https://github.com/developerforce/Force.com-Toolkit-for-NET/blob/313c4b9106b9a0f9779d42514189addc713799a5/src/CommonLibrariesForNET/AuthenticationClient.cs#L80
So you'll get a ForceAuthException saying

Unexpected character encountered while parsing value: <. Path '', line 0, position 0.

Thanks for documenting this - it got me up and running again as well.

There were issues with the PCLs and including ServicePointManager. I'm hopeful that .NET Standard 2.0 will resolve this. I haven't investigated, but if I could move this into the AuthenticationClient itself it would be a big win.


[spl-account-compression] V1 Release

Features:

[ ] Append only merkle trees
[ ] Sparse initialization (can immediately replace on any node, but no append capabilities)
[ ] Batch initialization (can partially init tree, with append capability in-tact)
[ ] Rust SDK getters

[ ] get current root
[ ] get current changelog
[ ] get current active index

Implementation details:

[ ] new v1 instructions

[ ] use emit_cpi! instead of noop cpi
[ ] remove use of noop in instructions

[ ] new v1 CMT header

Getting the current root:
fn get_root_at_index(
    tree_bytes: &[u8],
    max_depth: usize,
    max_buffer_size: usize,
    current_index: usize,
) -> Result<[u8; 32], &'static str> { // Assuming the root is 32 bytes
    if current_index >= max_buffer_size {
        return Err("Current index is out of bounds");
    }

    // Size of each field in ChangeLog
    let node_size = 32; // Assuming size of Node is 32 bytes
    let u32_size = 4;   // Size of u32

    // Size of ChangeLog
    let changelog_size = node_size + (node_size * max_depth) + u32_size + u32_size;

    // Calculate the starting position of the ChangeLog at the current index
    let changelog_start = (8 + 8 + 8) + (changelog_size * current_index);
    let root_start = changelog_start; // Root is the first element in ChangeLog

    // Extract the root bytes
    let root_bytes = &tree_bytes[root_start..root_start + node_size];

    // Convert the bytes to a 32-byte array
    root_bytes.try_into().map_err(|_| "Failed to extract root")
}

Getting the current active index:
fn get_rightmost_proof_index(
    tree_bytes: &[u8],
    max_depth: u32,
    max_buffer_size: u32,
) -> Result<u32> {
    let changelog_size = 32 + 32 * max_depth + 4 + 4;
    let path_start = 8 + 8 + 8 + changelog_size * max_buffer_size;

    let index_start = path_start + 32 * max_depth + 32;
    let (_, _index_bytes) = tree_bytes.split_at(index_start as usize);
    let (index_bytes, _) = _index_bytes.split_at(4);

    let index = u32::try_from_slice(index_bytes)?;
    Ok(index)
}


Module UI broken in Stars Without Number system

Module UI is technically functional, but essentially unuseable, in the system Stars Without Number: Revised (wsAI Alter.) 0.5.5 for Foundry v9.238

On module activation, throws the flag better-rolltables| Spell cache could not be initialized/updated.
-
UI Text is white
UI Rolltable Configuration does not properly expand the table dialog box, resulting in overlapping menu & table options. See screenshots below.

Update: v1.8.95 seems to have fixed these issues, although the error flag better-rolltables| Spell cache could not be initialized/updated. still appears on activation. Despite this, the module seems to function correctly.

Regarding the  better-rolltables| Spell cache could not be initialized/updated.
This is to be expected as BetterRolltables does not have any concept of WwN System.
Only the error message is true.
Please check if you have set a spell compendium in the settings like so:

Typically its like systemName.spells

I see, so it's just searching for something that's not there, but isn't necessary to its function.
Re: setting a spell conpendium, that option doesn't seem to mesh with the SWN system, as it doesn't appear on that menu:

FYI: I'm also seeing the white text issue in the Cyberpunk RED Core system.

I see, so it's just searching for something that's not there, but isn't necessary to its function.
Re: setting a spell compendium, that option doesn't seem to mesh with the SWN system, as it doesn't appear on that menu.

Thanks, I will try to look into why that is.


Training metrics not reported in log file

🐛 Bug

In the Pytorch Lightning Google Collab notebook the training loss, training accuracy, and training f1 score are not logged in the metrics file.
The training metrics are not logged by the Logger.
The validations metrics are logged in validation steps and are found in the log file.
The training metrics are not logged in the training step function and are not found in the log file.
How can these metrics be logged?

We found some issues with the logger in Lightning itself too. I believe is known issue, @Borda ?

I have open investigation over here - https://github.com/PyTorchLightning/pytorch-lightning/pull/6854


Unable to build with GCC 7.3

https://github.com/bjornus/Radon/blob/9d2324393d3e2dd5f835938ff31d3b40fd07af86/Radon/source/File.cpp#L41
/home/ajenbo/code/devilutionX/3rdParty/Radon/Radon/source/File.cpp: In constructor ‘radon::File::File(const string&, bool)’:
/home/ajenbo/code/devilutionX/3rdParty/Radon/Radon/source/File.cpp:41:31: error: cannot bind non-const lvalue reference of type ‘radon::Key&’ to an rvalue of type ‘radon::Key’
       sections.back()->addKey(Key(nameOfElement, valueOfElement));

I got it working but encountered a few more issues:

keys not being saved
crashes if key ore section is missing
I fixed the issues in this commit: https://github.com/diasurgical/devilutionX/commit/c2c0dd05f241c7a81874e243df0ecf091781bd6f
Tell me if you want me to send it as a PR, or if you prefer you can pick out the parts you agree with.

Fixed in https://github.com/szewczukk/Radon/pull/3


We've released 0.5 in another PR:https://github.com/dashevo/drive/pull/285


refac: Move CreateBatch to use nswag client

Description

References

#0000

Codecov Report

Merging #1551 (be2ed58) into main (a1f26b9) will increase coverage by 15.35%.
The diff coverage is 23.40%.

@@             Coverage Diff             @@
##             main    #1551       +/-   ##
===========================================
+ Coverage   24.26%   39.62%   +15.35%
===========================================
  Files          60       75       +15
  Lines        1360     1797      +437
  Branches      116        0      -116
===========================================
+ Hits          330      712      +382
- Misses       1019     1070       +51
- Partials       11       15        +4

Impacted Files
Coverage Δ

...ntegration/Controllers/WholesaleControllerTests.cs
97.82% <ø> (ø)

...Hub.WebApi/Clients/Wholesale/V3/WholesaleClient.cs
12.75% <21.73%> (+1.64%)
:arrow_up:

...Hub.WebApi/Controllers/WholesaleBatchController.cs
67.92% <100.00%> (+3.77%)
:arrow_up:

... and 19 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Incorrect checksum for api.community.zip

Looks like the published checksum for version 2.3.2 of api.community.zip is incorrect…?
The checksum contained in the file https://envkey-releases.s3.amazonaws.com/apicommunity/release_artifacts/2.3.2/d49329bf2ab7da3f.version.shasum is d49329bf2ab7da3f00574a6ab9e3ca61cf0c2766e5aac281eb50fed4986ce28c
When I run shasum -a 256 api.community.zip I get this result:
18cd1747071764aae2181a8d3d17fffa64de2b8020786cefd4545cda3b44487c  api.community.zip

Hi @cpach, the shasum is derived from the compiled code (which is wrapped in a binary) and the Dockerfile rather than the final zip artifact. It's intended for use by our build process rather than an integrity check for end users. You can instead verify the release signature with minisign for this purpose. Details here: https://docs-v2.envkey.com/docs/verifying-releases

Ok, got it! Thank you for clariyfing.
My use-case was to validate the integrity of the .zip in an Ansible playbook.
You might want to include a checksum of the .zip file too. (AFAICT Ansible doesn’t currently support minisign signatures.)

I see, I can understand how it's a bit misleading. We'll look at generating checksums for the zip files as well--thanks for flagging this. I'm going to move this to discussions so we don't lose track.


Mixed view hangs with Firefox

Hi,
I'm using FF 36.0.4 and when I open the mixed view for a transaction, it hangs.
Thanks

We are mainly supporting chrome currently but we're looking to support other browsers as much as possible.
In the mean time, could you use chrome?
Thanks.

Yes, I'm using Chrome and it is much faster than FF.  I did not find other issue with FF except this.
Thanks.


fix: update go-sarif

Description
With go-sarif 2.3.2, the '$schema' value is a uri for a file that does not exist now, https://raw.githubusercontent.com/oasis-tcs/sarif-spec/master/Schemata/sarif-schema-2.1.0.json
For 2.3.3, the hard-coded entry in the library changed to match the new location of the file in the github repository: https://github.com/owenrumney/go-sarif/commit/07358e7d8271397d059d18ae6869ea55893ed669
Updating, a new roxctl compiled with 2.3.3 go-sarif library generates sarif files with the $schema property set to a uri for the schema file that exists right now in the repository: https://github.com/stackrox/stackrox/actions/runs/11472923411/job/31926878236?pr=13084#step:9:96
User-facing documentation

[ ] CHANGELOG is updated OR update is not needed
[ ] documentation PR is created and is linked above OR is not needed

Testing and quality

[ ] the change is production ready: the change is GA or otherwise the functionality is gated by a feature flag
[ ] CI results are inspected

Automated testing

[ ] added unit tests
[ ] added e2e tests
[ ] added regression tests
[ ] added compatibility tests
[ ] modified existing tests

How I validated my change
I changed the build workflow to run the validation with the roxctl built on this branch, and verified that the sarif printed included the existing schema file.

@davdhacs could you revert https://github.com/stackrox/stackrox/commit/434edc59d18f6fdc3f330929b3550758ba08d48d in your branch and see if your bump fixes the upload issue?

This was not requested by dependabot because we have exceeded our dependabot pr limit (set by us) for months?

https://github.com/stackrox/stackrox/blob/master/.github/dependabot.yaml#L46
Should we bump this limit?

Can we make/ask @stackrox/backend-dep-updaters to review the list more regularly?


Make generation of data spines in post processing separate functions

Goal
Streamline post-processing function so that they call other functions that generate the data-spines that we will pass to the user and use to create the draws dataframe
Context
https://github.com/CDCgov/ww-inference-model/pull/5#discussion_r1670878652
Requirements

[ ] separate functions for each of the returned data spines in postprocess.R

Also consider naming them as _mapping rather than _spine


Remove default subspecs

To minimize library size, CoreData and realm shouldn't be included as default subspecs. Users should opt in to whatever behavior they need ala SugarRecord/Realm

Good idea, I'll remove it and force the developer to specify the configuration they want manually.

Woo! Love the library by the way. Especially with Realm, it makes it a lot easier to deal with threading.

Really? Realm has a really nice interface. I tried to replicate it for CoreData and find a generic interface that could be used in both scenarios.

Oh don't get me wrong, Realm is awesome. The hard part comes in when you create a Realm, say on the main thread, and then offload updates to a background thread. Realm throws an exception because changes have to be made on the same thread that the realm was made on but with SugarRecord, I don't have to worry about that!

Oh, I get your point now. Yes, it's kind of encapsulated, and it ensures good practices with the interface. Just execute your operation and save if you want to save your changes. That's all. And if you use Reactive you also have the reactive interface.


Among them, there is three files that have a useless indent for 95~99% of their length…

Well I don't know, the indents are annoying, but so is not being able to use blame...

this is absolutely obsolete, has to be redone from scratch, then closing it for the moment.


graphql ignores variables passed by react-router v4 params.

I'm stumped as to why graphql seems to ignore variables passed to it by react-router params.
Steps to Reproduce
I've setup a small demo here:
https://github.com/peitalin/react_apollo_reactrouter_v4_test
Buggy Behavior
I'm attempting to pass router params to graphql as variables.
However graphql is ignoring variables supplied to the query.
The resulting error message is:
Uncaught Error: The operation 'PokeQuery' wrapping 'PokemonPage' is expecting a variable: 'name' but it was not found in the props passed to 'Apollo(PokemonPage)'
Expected Behavior
React-router passes pokemon name to graphql via ownProps.params.name, and the query succeeds
Version
"apollo-client": "^0.8.0",
"graphql-tag": "^1.2.3",
"react-apollo": "^0.8.3",
"react-router": "next"

It's a typo: https://github.com/peitalin/react_apollo_reactrouter_v4_test/blob/master/src/components/PokemonPage.tsx#L48 should be variables.

Perhaps the error message here could be clearer?

No, should be fine, I just somehow missed that.


typescript and javascript language features extension loading foreever

Type: Bug
This is happening a lot lately. After working for a while on my TypeScript Next.js project, Intellisense is taking forever to do whatever. "Loading Intellisense Status" is not ending.

I'm also experiencing this, using wsl on windows. It seems like every file under node_modules is being registered by file watcher, and just errors thrown all over the place

I've worked for 4 hours now using VS Code Insiders without extensions and no issues so far.

I've worked for 4 hours now using VS Code Insiders without extensions and no issues so far.

I don't know if it's related, but these past few days, VSCode has been a real pain to use. V1.95.3. Intellisense takes forever to load, auto-imports work only for the first import of an index (after, all other imports from same index don't auto-import, I have to type it manually). Ctrl+click on classes take forever to navigate (if they ever load). Autocomplete on class. and using ctrl + space either never loads, ever, or I have to restart VSCode and then it will be slow to autocomplete.

I'm also experiencing this, using wsl on windows. It seems like every file under node_modules is being registered by file watcher, and just errors thrown all over the place

The same thing is happening to me on mac.


HAP node.js warning / Homebridge 2.0 Support

Prerequisite

[X] Yes, I've read the readme completely.

Cache

[X] Yes, I've cleaned accessory cache and the issue still exists.

Version
1.7.0-beta-54
Device Infomation JSON File
No response
Device Control Mode
Standard Instruction
Logs
[02/09/2024, 20:36:21] [@0x5e/homebridge-tuya-platform] Child bridge starting (pid 1866)...
[02/09/2024, 20:36:22] Registering platform<EMAIL_ADDRESS>[02/09/2024, 20:36:22] [@0x5e/homebridge-tuya-platform] Child bridge started successfully (plugin v1.7.0-beta.54).
HAP-NodeJS WARNING: The accessory '@0x5e/homebridge-tuya-platform' has an invalid 'Name' characteristic ('@0x5e/homebridge-tuya-platform'). Please use only alphanumeric, space, and apostrophe characters. Ensure it starts and ends with an alphabetic or numeric character, and avoid emojis. This may prevent the accessory from being added in the Home App or cause unresponsiveness.
[02/09/2024, 20:36:22] Loaded 4 cached accessories from cachedAccessories.0E27A7C7E432.
[02/09/2024, 20:36:22] [@0x5e/homebridge-tuya-platform] Loading accessory from cache: Office Bookcase 2
[02/09/2024, 20:36:22] [@0x5e/homebridge-tuya-platform] Loading accessory from cache: Office Bookcase 3
[02/09/2024, 20:36:22] [@0x5e/homebridge-tuya-platform] Loading accessory from cache: Office Bookcase 1
[02/09/2024, 20:36:22] [@0x5e/homebridge-tuya-platform] Loading accessory from cache: FSTWIFITU
HAP-NodeJS WARNING: The accessory '@0x5e/homebridge-tuya-platform D89D' has an invalid 'Name' characteristic ('@0x5e/homebridge-tuya-platform D89D'). Please use only alphanumeric, space, and apostrophe characters. Ensure it starts and ends with an alphabetic or numeric character, and avoid emojis. This may prevent the accessory from being added in the Home App or cause unresponsiveness.
[02/09/2024, 20:36:22] [@0x5e/homebridge-tuya-platform] Log in to Tuya Cloud.
[02/09/2024, 20:36:22] [@0x5e/homebridge-tuya-platform] [TuyaOpenAPI] Login to: https://openapi.tuyaeu.com
[02/09/2024, 20:36:22] Homebridge v2.0.0-beta.15 (HAP v1.1.1-beta.2) (@0x5e/homebridge-tuya-platform) is running on port 34982.
[02/09/2024, 20:36:23] [@0x5e/homebridge-tuya-platform] Start MQTT connection.
[02/09/2024, 20:36:23] [@0x5e/homebridge-tuya-platform] Fetching home list.
[02/09/2024, 20:36:23] [@0x5e/homebridge-tuya-platform] Got home_id=74774721, name=The Old Bakery
[02/09/2024, 20:36:23] [@0x5e/homebridge-tuya-platform] Found home_id=74774721 in whitelist; including devices from this home.
[02/09/2024, 20:36:23] [@0x5e/homebridge-tuya-platform] Fetching device list.
[02/09/2024, 20:36:23] [@0x5e/homebridge-tuya-platform] Fetching scene list.
[02/09/2024, 20:36:24] [@0x5e/homebridge-tuya-platform] Got 4 device(s) and scene(s).
[02/09/2024, 20:36:24] [@0x5e/homebridge-tuya-platform] Device list saved at /var/lib/homebridge/persist/TuyaDeviceList.eu1671172634845eJuvS.json
[02/09/2024, 20:36:24] [@0x5e/homebridge-tuya-platform] Restoring existing accessory from cache: Office Bookcase 1
[02/09/2024, 20:36:24] [@0x5e/homebridge-tuya-platform] [Office Bookcase 1] Light type: C
[02/09/2024, 20:36:24] [@0x5e/homebridge-tuya-platform] [Office Bookcase 1] Adaptive Lighting disabled.
[02/09/2024, 20:36:24] [@0x5e/homebridge-tuya-platform] Restoring existing accessory from cache: Office Bookcase 2
[02/09/2024, 20:36:24] [@0x5e/homebridge-tuya-platform] [Office Bookcase 2] Light type: C
[02/09/2024, 20:36:24] [@0x5e/homebridge-tuya-platform] [Office Bookcase 2] Adaptive Lighting disabled.
[02/09/2024, 20:36:24] [@0x5e/homebridge-tuya-platform] Restoring existing accessory from cache: FSTWIFITU
[02/09/2024, 20:36:24] [@0x5e/homebridge-tuya-platform] Restoring existing accessory from cache: Office Bookcase 3
[02/09/2024, 20:36:24] [@0x5e/homebridge-tuya-platform] [Office Bookcase 3] Light type: C
[02/09/2024, 20:36:24] [@0x5e/homebridge-tuya-platform] [Office Bookcase 3] Adaptive Lighting disabled.

Other Infomations
Plugin updated to comply with naming conventions/restrictions. HAP node.js in Homebridge 2.0 is more verbose hence this surfacing (I think). Plugin does still work, but logs are reporting this

Sorry @Quickstep3 I'm not going to maintain this project anymore... but PRs are still welcome.


Block select with Shift-Alt

Issue Type: Feature Request
I often use the block select fucntionality.  to achieve that in Visual Studio (not VSCode) I used to use the Alt key with the mouse click&drag and it worked like a charm.
Now must combine Shift-Alt keys for that.  In Windows that key comibation switches the keyboard language when you have more than one!  Which is pretty annoying.
I strongly think that shortcut should be configurable.
Thanks
Daniel
VS Code version: Code 1.40.2 (f359dd69833dd8800b54d458f6d37ab7c78df520, 2019-11-25T14:54:45.096Z)
OS version: Windows_NT x64 10.0.14393

@danbord In VS Code, we call that column selection. Here is what I recommend:

install the VS keymap, which defines the keybindings shift+alt+arrows to do column selection.
free up alt for column selection mouse gestures. Configure "editor.multiCursorModifier": "ctrlCmd" which will make it that mouse selection + alt will switch to column selection mode.

Once you do these, column selection should hopefully feel similar to the one in VS. But there are still caveats, and some things do not work in the same way, mainly because VS Code does not have virtual spaces. You can find the existing issues here


CFFL

CFFL

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_c6pptqelj9/clone/recipe/meta.yaml:1: missing_python: For pypi packages, python should be present in the host and run sections. Missing in host
ERROR: /tmp/abs_c6pptqelj9/clone/recipe/meta.yaml:1: missing_wheel: For pypi packages, wheel should be present in the host section
ERROR: /tmp/abs_c6pptqelj9/clone/recipe/meta.yaml:1: missing_python_build_tool: Python packages require a python build tool such as setuptools.
ERROR: /tmp/abs_c6pptqelj9/clone/recipe/meta.yaml:16: uses_setup_py: python setup.py install is deprecated.
ERROR: /tmp/abs_c6pptqelj9/clone/recipe/meta.yaml:28: missing_pip_check: For pypi packages, pip check should be present in the test commands
ERROR: /tmp/abs_c6pptqelj9/clone/recipe/meta.yaml:34: incorrect_license: The recipe's about/license key is not an SPDX compliant license or license exception, closest match: LPPL-1.0
ERROR: /tmp/abs_c6pptqelj9/clone/recipe/meta.yaml:42: missing_license_family: The recipe is missing the about/license_family key.
Errors were found


Additional filter for Free events (Like EventBrite)

Describe the feature you'd like
I would like to add additional filter (Free events) the search results of events
Screenshots
From  eventBrite

Additional context

Would you like to work on the issue?

[  :heavy_check_mark: ] Yes
[ ] No
Other:

Server doesn't provide this filter AFAIK

It does, see JSON:API spec, you can use nested filters to achieve the same effect

@theLimitBreaker I've implemented it can I make PR it if you're okay with it?

@aggarwalpulkit596 don't mind , but I already said I would be working on this . Also I just created this issue today .  Atleast give some time

okay no issues

@theLimitBreaker can i make pr for this now as there has been no activity from you and i've already completed it, i just need to make a PR @iamareebjamal

Give 4 more days

@iamareebjamal  I am getting error , failure on every API call (which were previously were working ) after pulling latest commits.
For free events I made the filter param like this
[{
                    "name":"tickets",
                    "op":"any",
                    "val":{
                        "name":"price",
                        "op":"eq",
                        "val":"free"
                    }
}]

Also in kotlin code I replaced " with \" before making calls .
I get HTTP 500

Open an issue on server

@theLimitBreaker let me check them

@iamareebjamal @aggarwalpulkit596 I am getting error , failure on every API call (which were previously were working ) after pulling latest commits.
For free events I made the filter param like this and I m hitting the endpoint /events
[{
                    "name":"tickets",
                    "op":"any",
                    "val":{
                        "name":"price",
                        "op":"eq",
                        "val":"0"
                    }
}]

Also in kotlin code I replaced " with \" before making calls .
I get HTTP 500. As Api calls are not working here. Could you tell I am heading in right direction

Update
API are working
It gave me error regarding Room can't verify its integrity. Schemas been changed.
I had to clear the storage. For api working.

@iamareebjamal can I make PR now?

We generally allow PRs from different contributors when there are no updates for a week. Last update was 1 day ago

okay cool


X11 does not support transparent border color.

As a side-effect, X11 is now ready for full window transparency.


Method invocation syntax

Any sufficiently complicated C or Fortran program contains an ad hoc, informally-specified, bug-ridden, slow implementation of half of Common Lisp. - Philip Greenspun

Proposal: method invocation, formatted as s-expressions to be passed directly to public_send
Qig.qig([1, nil, 2], [:compact]) # => [1, 2]

This is on-theme with other syntax already in qig or proposed for qig, namely:
[]        # unboxing
[[]]      # reboxng
['', key] # quoting

So this would add
[:method, *args]

Doesn't collide with anything, easy to distinguish, easy to implement.
Given the existence of yield_self, this can also be used to call methods not defined on the subjects.
So it can be done, but should it be done?
More specifically: can we limit the sprawl of this half-implemented lisp?
Let's try to box it in by tightening down the specifications. In particular:

this syntax SHALL NOT extend more than one level deep
anything that is easily performed as a method call under this syntax SHALL NOT get a bespoke language extension

[1] prevents this feature from sprawling. public_send is powerful enough I shouldn't need to go more than one level of s-expressions deep,

don't have to go more than 1 level deep at least from the qig language perspective. if individual subargs are complex that's fine because I don't actually need to evaluate them
Just consider one layer, ship things off to public_send, and the rest is ruby's job.

Since this extension opens up the world of arbitrary method calls, I can use it to avoid bespoke extensions and actually limit DSL sprawl. [2] makes this intent explicit.

Q: does this mean I should throw out #5 , since under the send syntax I can now do ['[]', key]? A: probably, yes. Though I'm tempted to make an exception or a sugar rule for this.

Apply to Subject(s)
For caller sanity, this should always apply at the subject(s) level, NOT the stream level.
There are temptations way from this. For example, wouldn't it be convenient to allow [:compact] to always compact the top-level?

If you're in collection_qig mode, you can pop up and back down [[]], [:compact], []. A bit wordy, but should work
all other operations are at the subject level, even []. "value iteration" expresses the action from the point of view of the subject(s), not the point of view of the stream (which would see it as "flattening").

This suggests an escape hatch for compelling use cases--invent a verb that flips the subject from collection to units, and then turn that into an operator. Running with the compact example, we could reframe it as presence_or_expunge or somesuch. This would stay in the spirit of jq syntax.

Updates here:
Most of the useful operators take a block, but there is no built-in method to pass a block to an array and splat it onto the block argument of a method call. As such, revised the call syntax:
[:method, [*args], block]

This allows passing the block as a lambda, and has enough structure to detect the block by pattern-match rather than trying to guess by context or destination :method or typechecking.

Apply only to subject turned out to be misguided. jq has plenty of operators that apply at stream level (e.g. select). As such, revised the syntax to have a top-level version and a subject-level version
[:method, [*args], block]   # => for each subject, `subject.public_send(:method, *args, &block)
[[:method, [*args], block]] # => top.public_send(:method, *args, &block)


Embed cluster.Config in cluster.Spec

Continues the work started by #1343
Description of changes:
This makes cluster.Config available almost everywhere in the CLI, since
we pass cluster.Spec as argument to most calls.
Removed a few parsed api structs from cluster.Spec that are not used
anymore.
Removed the GitOps default method from cluster.Spec and use the one for
cluster.Config when necessary (just in tests).
Testing (if applicable):
I ran all unit test and a couple e2e for vsphere and docker, all good.
However, I want to keep this on hold until we release, to avoid extra noise if any of the e2e tests fail.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/hold until next release

/lgtm

/lgtm

/lgtm


export all programs of a user as a zip file

a user may want to have a backup of his/her programs, which he/she has stored in the data base.
Workflow:

login
select menu entry "export all programs as zip file"
a file selection dialog appears. The user selects a fiel name
the programs are stored

Remarks:

the place in the menu should be discussed
other formats (tar, ...) could be an option

Shouldn't there also be an "import zip to my programs"? Because if not, Loading a back up is just as tedious as currently creating one.

yes, it should be symmetric. But, importing has the risk of an DOS attack by importing millions of programs. Maybe we need a limitation of the number of programs (100, 1000?)

should export also export all Programs that are shared with the user including the programs of group members of those groups, that are owned by the user? like in the getProgramInfoOfProgramsOwnedByOrSharedWithUser() from ProgramProcessor.java (but instead of for one Robot for every Robot or should it only include the Programs owned by the User

I think, we should discuss this. I propose:

to save NOT the programs that are shared by other users (because they are responsible to backup them),
but, to save the programs of all members of all groups the user owns

The problem is to see this. The only possibility I can imagine is to encode the information into the name of the member, e.g.

my programs:
group member programs:

Ideas?

Something along those lines is already being done here if  I'm not mistaken just instead of loadall(user,robot) it has to be loadAll(user). I think its best to put those parts into their own helper methods and use them maybe overload them with (user) and (user robot). The method this is in is way too long anyways.

Due to the nature of how this feature is being implemented right now, it is possible to check if a program is the default program with no changes to the config and a check for default ProgramText shouldn't be too difficult either , i suggest to not Download programs that are unchanged, so you don't download unnecessary files. With this you could also use the feature to clean up your workspace.
But i can also see this causing confusion if you don't know why certain Programs are missing, and if you have a certain naming structures (like numbering your programs) this structure would have holes when you had a few empty programs within it.

I have thought about the possible Folder Structure please let me now what combination of general folder structure and group structure is prefered, i like: general: V2 with group: V3
General Structure V1:
Export_structureV1.pdf
General Structure V2:
Export_structureV2.pdf
Group Structure:
GroupStructures.pdf


Download files by matching filename portion

And since I’m emailing, I may as well ask about the problem I expected to meet.  The GRACE series has four files per month:
https://urldefense.us/v3/__https:/archive.podaac.earthdata.nasa.gov/podaac-ops-cumulus-protected/GRACEFO_L2_CSR_MONTHLY_0060/GSM-2_2018152-2018181_GRFO_UTCSR_BA01_0600__;!!PvBDto6Hs4WbVuu7!fkCBBvOS_eUQeDZNU3GiZ6z2fwP1D3v2U1KrurcGsD0Ymkrt3az62vBuTQaAxr1Zaap4SSzUtw$
https://urldefense.us/v3/__https:/archive.podaac.earthdata.nasa.gov/podaac-ops-cumulus-protected/GRACEFO_L2_CSR_MONTHLY_0060/GAC-2_2018152-2018181_GRFO_UTCSR_BC01_0600__;!!PvBDto6Hs4WbVuu7!fkCBBvOS_eUQeDZNU3GiZ6z2fwP1D3v2U1KrurcGsD0Ymkrt3az62vBuTQaAxr1Zaaqs4JY7SQ$
https://urldefense.us/v3/__https:/archive.podaac.earthdata.nasa.gov/podaac-ops-cumulus-protected/GRACEFO_L2_CSR_MONTHLY_0060/GSM-2_2018152-2018181_GRFO_UTCSR_BB01_0600__;!!PvBDto6Hs4WbVuu7!fkCBBvOS_eUQeDZNU3GiZ6z2fwP1D3v2U1KrurcGsD0Ymkrt3az62vBuTQaAxr1Zaap1qjG6fA$
https://urldefense.us/v3/__https:/archive.podaac.earthdata.nasa.gov/podaac-ops-cumulus-protected/GRACEFO_L2_CSR_MONTHLY_0060/GAD-2_2018152-2018181_GRFO_UTCSR_BC01_0600__;!!PvBDto6Hs4WbVuu7!fkCBBvOS_eUQeDZNU3GiZ6z2fwP1D3v2U1KrurcGsD0Ymkrt3az62vBuTQaAxr1ZaapwXWrIyQ$
Is there any way to use this downloader to only download, say, the GSM “BA” format and the GAC file, as I used to via FTP/Drive?  (GRACE is a small enough data series that this isn’t crucial, but I thought I’d ask.)

The above issue was from Jennifer Bonin


Director

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version:
OS Version:

Steps to Reproduce:

We closed this issue because we don't plan to address it in the foreseeable future. If you disagree and feel that this issue is crucial: we are happy to listen and to reconsider.
If you wonder what we are up to, please see our roadmap and issue reporting guidelines.
Thanks for your understanding, and happy coding!


R package reproducibility

I can add R packages and rpy, and R to my mach-nix derivation.
Very cool.
Doesn't quite work (import rpy2.robjects says missing R_HOME), but that's gotta be somewhere in the way I invoke mach-nix.
But how do I lock those versions down?
In my previous life I found that if you're not using a specific bioconductor release
(and the resulting R version), and a specific date snapshot of CRAN (which microsoft provides) you are going to go insane.
Any pointers on how to achieve this would be appreciated!

packagesExtra = [pkgs.rWrapper] ++ (with mach-nix.rPackages; [edgeR]);
solves the R_HOME problem.
Now, how do I get an R with the same packages?

let my_r_packages = with pkgs.rPackages; [ edgeR ];
     my_r = pkgs.rWrapper.override { packages = my_r_packages; };
in mach-nix.mkPython ... packageExtras = [my_r] ++ my_r_packages;...

Do you really need the ++ my_r_packages despite the packages already being included in my_r?
I do not really use R packages myself. If you could help in contributing an improvement in the way mach-nix assembles R environments, that would be great.
Currently what mach-nix does to include R packages is to add them to buildInputs of the rpy2 package. See these lines https://github.com/DavHau/mach-nix/blob/d223656fc0eff33f4da77d69db19752edc9a5ba5/mach_nix/nix/mkPython.nix#L83-L85
As I understand from your issue, this is not enough to make things work.
@InLaw, do you have any opinion on this?

yes, I do need them, because my_r does not declare an rCommand, and the the mach-nix 'is there any r packages about' detection fails.
I envy you. I had a deep dive into R packing this afternoon (once again, into the breach...), and I found that while it's at least possible to get CRAN into a reproducible shape, thanks to daily mirroring by microsoft, bioconductor is a whole different beast.
The bioconductor authors replace their PACKAGES description file inside one release to do update the z in x.y.z. package versions. And they throw away the old package.x.y.z.tar.gz in favor of package.x.y.z+1.tar.gz
Rstudio has it's own mirror, it actually keeps the old package.x.y.z.tar.gz in an archive, but it also always has the newest PACKAGES, and I can't find the archived versions. The interactive/api websystem they build knows about them though.
And don't get me started on Bioconductor Release X, on date Y, after such a point update referencing CRAN packages and versions that did not exist on date Y.

Currently what mach-nix does to include R packages is to add them to buildInputs of the rpy2 package. See these lines
https://github.com/DavHau/mach-nix/blob/d223656fc0eff33f4da77d69db19752edc9a5ba5/mach_nix/nix/mkPython.nix#L83-L85
As I understand from your issue, this is not enough to make things work.

They have to go into propagatedBuildInputs.

I've solved all my issues in my anysnake2 project, thanks for y'all's feedback!


(GH-1688) Add BoltSpec helper to load bolt constructs

This creates a new helper module BoltSpec::BoltContext which provides
the in_bolt_context method. This method makes Bolt datatypes and
functions available to a block allowing code that references Bolt
constructs to be tested. The Plans module was already doing all of this
work, creating a mock executor, stubbing run_* functions, and setting
default config, inventory, and modulepath values. This moves all of that
logic into a common BoltContext module so that it can be generally
useful as opposed to being coupled with testing Bolt plans. This allows
things like Puppet functions that refer to the TargetSpec datatype to
be tested without having to wrap them in a Bolt plan for testing.
Closes #1688
!feature

Add Boltspec helper to load Bolt constructs (#1688)
A new helper function in_bolt_context can be used to wrap code that
references Bolt constructs, such as the TargetSpec datatype.

CLA signed by all contributors.


feat(website): Move blog to CC and fix RSS

Summary
The current blog was using the old recommended method for querying content (Astro.glob()) which had several disadvantages in comparison to the current approach, named Content Collections.
This PR moves the entire blog set up to the recommended approach, refactors the internal blog components used, and as a bonus, fixes the generated RSS which was empty before.
There are some considerable changes for the team to be aware of:

Content should now be written in src/content/blog instead of src/content/docs/blog.

All blog posts now have a different set of frontmatter properties. I went for a very similar structure, but a few properties weren't necessary anymore or could be improved, for example:
Before:
---
title: Announcing Biome
template: splash
url: /blog/annoucing-biome
description: Biome continues Rome's legacy; in this blog post, we explain why the fork, with some context and history.
summary: Biome continues Rome's legacy; in this blog post, we explain why the fork, with some context and history.
authorName: Emanuele Stoppa
authorAvatar: https://avatars.githubusercontent.com/u/602478?v=4
authorUrl: https://twitter.com/ematipico
coauthorName: Biome Core Team
coauthorAvatar: /img/circle-indent-logo.svg
pubDate: 2023-08-29
layout: ../../../layouts/Blog.astro
coverImage: blog/announcing-biome/biome-logo-slogan.png
coverImageAltText: The name of the project - "Biome", with the slogan underneath that says "Toolchain of the web"
socialImage: blog/announcing-biome/biome-logo-slogan.png
---

After:
---
title: Announcing Biome
description: Biome continues Rome's legacy; in this blog post, we explain why the fork, with some context and history.
summary: Biome continues Rome's legacy; in this blog post, we explain why the fork, with some context and history.
authors:
  - ema
  - core
pubDate: 2023-08-29
coverImage:
  src: blog/announcing-biome/biome-logo-slogan.png
  alt: The name of the project - "Biome", with the slogan underneath that says "Toolchain of the web"
socialImage: blog/announcing-biome/biome-logo-slogan.png
---

Authors are now .json files inside src/content/authors.
To create a new author, create a new (author).json file following the format:
{
	"name": "Emanuelle Stoppa",
	"avatar": "https://avatars.githubusercontent.com/u/602478?v=4",
	"url": "https://twitter.com/ematipico" // This is optional!
}

And to reference it inside a blog post (the author reference id will be its file name without the extension):
---
authors:
  - ema
---

Note that authors are shown in a blog post in the order specified in the frontmatter, meaning you can decide who's the main author according to the blog post.

Test Plan
By visually inspecting the deploy preview you can see how all blog posts are as expected.
For the RSS fix, this is the snippet of current RSS feed and the one built by this PR:
Before:
<rss version="2.0">
	<channel>
		<title>Biome Blog</title>
		<description/>
		<link>https://biomejs.dev/</link>
		<language>en-us</language>
	</channel>
</rss>

After:
<rss version="2.0">
	<channel>
		<title>Biome Blog</title>
		<description>Biome's toolchain official blog</description>
		<link>https://biomejs.dev/</link>
		<language>en-us</language>
		<item>
			<title>Biome formatter wins the Prettier challenge</title>
			<link>https://biomejs.dev/blog/biome-wins-prettier-challenge/</link>
			<guid isPermaLink="true">https://biomejs.dev/blog/biome-wins-prettier-challenge/</guid>
			<description>Biome formatter now 95% compatible with Prettier</description>
			<pubDate>Mon, 27 Nov 2023 00:00:00 GMT</pubDate>
		</item>
		<item>
			<title>Announcing Biome</title>
			<link>https://biomejs.dev/blog/annoucing-biome/</link>
			<guid isPermaLink="true">https://biomejs.dev/blog/annoucing-biome/</guid>
			<description>Biome continues Rome's legacy; in this blog post, we explain why the fork, with some context and history.</description>
			<pubDate>Tue, 29 Aug 2023 00:00:00 GMT</pubDate>
		</item>
		<item>
			<title>Biome v1</title>
			<link>https://biomejs.dev/blog/biome-v1/</link>
			<guid isPermaLink="true">https://biomejs.dev/blog/biome-v1/</guid>
			<description>New formatter options, CLI improvements, JSONC support and more.</description>
			<pubDate>Tue, 29 Aug 2023 00:00:00 GMT</pubDate>
		</item>
	</channel>
</rss>

@Yan-Thomas Let's change the base branch to website-v2

Let's change the base branch to website-v2

Any particular reason @victor-teles? I thought this branch was for the rebranding, and considering this PR mostly fixes/improves what we already had I think we can merge it into main and update branch on website-v2, so people there can also use the new layout. I won't argue against it though, it's your call!


Any plan to add Tags for UE4?

Do you have a plan to add "git-project-tag" for UE 4.27?
After converting to UE5, It's quite hard to get UE4 version. I think some beginners would have to pay lots of time on this
Someone struggling with How to use this project on UE4, Use this command
git clone
git reset --hard 756524f2055a6b9964e5af4bb417201b4666f796
you can see above hash (756524....)  on git log
Anyway, thank you for making this opensource-project. Awesome!

Oh you have branch for this, sorry.
I am used to it so much ( It support downloads on git hub) so didn't check that
never mind.


Enhance log message for ClusteredStatisticsCountTest.countTest

The test failure  may be transient, but we are enhancing the log message, so that next time it would be easier to debug.

Haha, I still don't hope for random build failure....

I created another PR to exclude TDB ref: https://github.com/ehcache/ehcache3/pull/2546


optimization: Leader log sampled handshake

Background: #144

At the moment, a raft node only accepts MsgApp log appends from the latest leader it knows about, i.e. when MsgApp.Term == raft.Term. This restriction could be relaxed, which can reduce the message turnaround during the times when the leader changes.
The safety requirement is that we don't accept entries that are not in the raft.Term leader log. If we can deduce that an entry is in the leader's log (before / other than by getting a MsgApp directly from this leader), we can always safely accept it.
One way to achieve this:

When we vote for a leader, we know a (term, index) of the last entry of the new leader's log. If the election wins, the new leader will not overwrite entries up to this index, and will append new entries strictly after it.
If we receive a MsgApp (from any leader) that contains this entry, we have the guarantee that all entries <= index in this append are contained in the leader's log. It is safe to accept them.

A more general way to achieve this is:

When a leader campaigns, it should not only attach the last entry (index, term), but also a sample of K other (index, term) in its log. Specifically, it would be wise to attach the "fork" points of the last K terms.
When a node votes for a new leader, it remembers this sample.
When a follower handles MsgApp, it can deduce from this sample the overlap between this append message and the leader's log. The overlapping part can be safely accepted regardless of who sent it.

The practical K would be 2 or 3, because leader changes are typically not frequent. 2 or 3 last term changes cover a significant section of the log.
This sampling technique is equivalent to the fork point search that the leader does in the StateProbe state to establish the longest common prefix with the follower's log before transitioning it to the optimistic StateReplicate state.
This gives significant benefits:

By including a sample of K fork points rather than just the latest one, we increase chances of finding an overlap immediately, and reduce message turnaround.
By including a sample in the votes, we avoid the first MsgApp in the StateProbe, and will typically be able to transition straight to StateReplicate.
The bonus point is that the sample can be used to safely accept some MsgApp.Entries (that arrived just slightly late) from a recent leader who is stepping down.

This technique will minimize cluster disruption / slowdown during election, and reduce tail replication/commit latency in some cases.

Can we optimize it further, by including voter's last K fork points in its vote response, so that leader can immediately know the next index to replicate. This would let leader to immediately replicate entries to its voters. Other followers would still need the first MsgApp to determine the matching index.

Some concerns we may need to consider:

Both new and old leaders may replicate entries to a follower until its log catches up with the longest common prefix of the two leader logs. Half of the entry payloads would be wasted.
When would the old leader stop replicating entries to followers? Follower can response with specific flag when its log goes beyond the last fork point. But what if there are unreachable followers.
When would the old leader steps down to follower and stop receiving client requests?

@joshuazh-x There is no need for the old leader to continue replication if it learns there is a new leader.

Both new and old leaders may replicate entries to a follower until its log catches up with the longest common prefix of the two leader logs. Half of the entry payloads would be wasted.

I do not expect this to happen, because the old leader will be notified about the existence of the new leader, and stop replicating. The only difference is that the last append message that the old leader has sent may have been accepted rather than outright rejected.

When would the old leader stop replicating entries to followers? Follower can response with specific flag when its log goes beyond the last fork point.

I think it should be as simple as a MsgAppResp with a new leader Term. We don't want the old leader to continue replicate in parallel to the new leader.

But what if there are unreachable followers.

Same thing will happen as today. Any leader will try to probe unreachable followers. The old leader will stop doing so when it learns about the new leader.

When would the old leader steps down to follower and stop receiving client requests?

The moment it learn about the new leader Term.


[Feature Request]: Theme changeable

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
The overall website is only in dark mode. I think changing the website theme according to the user can enhance the overall user experience for this website.
Use Case
Themes are very common feature of almost any website. Providing this feature can be beneficial for the website
Benefits
No response
Add ScreenShots
No response
Priority
Medium
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

@HimanshuNarware Please assign this job to me ,I can do really good work in this

Its already been created, so closing this as of now


Release version 2.3.4

Questions
Answers

Description?
Release new version of the module. We forgot to update the version in the last one.

Type?

BC breaks?

Deprecations?

Fixed ticket?

How to test?

Merging as it's only a version bump.


Bugfix/parameter set to

There is a small bug in parameter.set_to that this PR fixes.
The bug:
Have an instrument driver.
Have a parameter, p, of that driver with a validator that does not accept None.
Connect to instrument (now all parameters have _latest["value"] == None).
Use with p.set_to(some_valid_value):.
Get ValueError from the setter of p that None is invalid.
This PR fixes the bug by querying p in case _latest["value"] == None.
@QCoDeS/core

This was meant as a quick bugfix. I have some more features coming for the set_to functionality. I'll make a larger PR.


wasm-smith: allow generating single function modules

This change adds SingleFunctionModule, an alternative to Module and
ConfiguredModule that allows the user to specify the function
signature to generate. It avoids previous issues with Module where
min_funcs and max_funcs would be configured as 1 but the function
would at times not be exported.

I like the idea of reusing Module where possible since it's got quite a lot internally already. If we can though I think I'd prefer to continue to lean heavily on Config. I'm not too too concerned about trying to rationalize all the configuration options with one another so if something falls through the cracks there that seems reasonable to me.
I think though the main purpose of this would be to generate function signatures differently though, right? In that we'd generate arbitrary parameters but we wouldn't know the results until after the function was generated (presumably taking all of the results from the function)

I think though the main purpose of this would be to generate function signatures differently though, right? In that we'd generate arbitrary parameters but we wouldn't know the results until after the function was generated (presumably taking all of the results from the function)

You mentioned this in the other thread but I didn't quite understand the "why." Is it because not restricting the result types would be easier to implement or something else? It seems valuable to provide a target for the function to "head towards" but perhaps that is too difficult (I haven't really looked at the code builder changes yet).

but the function would at times not be exported.

We could also add a export_all method that performs a post-generation pass to export everything (or export_all_funcs and just export the functions)

One of my worries about the current generation of wasm-smith is that we generate a bunch of code which has all these nice values on the wasm stack, only to have them all get dropped at the end of the function because the function has a different signature. That means that differential fuzzing is pretty unlikely to actually pick up any differences in execution since the values going in/out are always canned.
I don't know how best to fix it but picking the result types later was a strawman at doing so. It's still not great though I think.

Another thing we could do is, when we have a memory, write the extra values to memory instead of dropping them.

That's sort of another thing which makes me think we should continue to add heuristics and config options but probably no need to make a whole new generator just yet.

Yeah, thinking about this more, a combination of export_everything, allowed_instructions, and whatever we come up with for https://github.com/bytecodealliance/wasm-tools/issues/655 is probably enough to generate small functions with observable results.


[WIP] aio.api.github: Logging cleanups

Signed-off-by: Ryan Northey<EMAIL_ADDRESS>

more changes needed? Or remove draft label?

more work needed, and some test fixups/additions i think


Support for Custom Titles

Add support for users entering their own titles, for display purposes as well.

Added some testing code with 1f47add17f73588c1c7ee7611ea5559b664a558c
Right now, you have to leave the main game grid and come back for it to refresh with the right name.
Still needs to be totally fixed.
Right now, it only displays for the cards, but I'll probably put it on the main info too.


[11.0.x] ISPN-13229 LocalPublisherManagerImpl doesn't clean up changeListener …

…for publish methods

Closing as not going to integrate upstream.


[CT-884] Make unique ids of document records consistent

Nodes and other records in the manifest have a generally consistent pattern of unique ids except for docs.  Models and other nodes follow the pattern "node_type.project_name.name", but instead of "doc.my_project.my_document" the unique ids for documents follow the pattern "my_project.my_document".
This should be made consistent.

Concerns:

This may have backwards compatibility issues.
This may also have implications in dbt-docs.

Should not be that hard since we don't access docs in many places.  Updating all the tests may be most of the work here.


Tokio-console is not working

When enable tokio-console, the compiling is fine, but once vertex start, it will hanging. And tokio-console status is always 'CONNECTING'.

It is upgrad to latest version, it should work now.
#1305