text:
Allow validators to detect transaction censorship attempts:

The XRP Ledger is designed to be censorship resistant. Any attempt to censor transactions would require coordinated action by a majority of the system's validators.
Importantly, the design of the system is such that such an attempt is detectable and can be easily proven since every validators must sign the validations it publishes.
This commit adds an automated censorship detector which is active on servers configured as validators. The detector tracks all transactions proposed by the validator and issues warnings of increasing severity for any transactions which, despite being proposed repeatedly by the validator, has not been included.

Jenkins Build Summary
Built from this commit
Built at 20180930 - 03:07:34
Test Results

Build Type
Log
Result
Status

msvc.Debug
logfile
1033 cases, 0 failed, t: 790s
PASS :white_check_mark:

gcc.Debug -Dcoverage=ON
logfile
1036 cases, 0 failed, t: 851s
PASS :white_check_mark:

docs
logfile
1 cases, 0 failed, t: 2s
PASS :white_check_mark:

gcc.Release -Dassert=ON, MANUAL_TESTS=true
logfile
1101 cases, 0 failed, t: 933s
PASS :white_check_mark:

clang.Debug
logfile
1036 cases, 0 failed, t: 284s
PASS :white_check_mark:

rpm
logfile
1035 cases, 0 failed, t: n/a
PASS :white_check_mark:

clang.Debug -Dunity=OFF
logfile
1036 cases, 0 failed, t: 441s
PASS :white_check_mark:

gcc.Debug
logfile
1036 cases, 0 failed, t: 290s
PASS :white_check_mark:

msvc.Debug, NINJA_BUILD=true
logfile
1033 cases, 0 failed, t: 651s
PASS :white_check_mark:

gcc.Debug -Dunity=OFF
logfile
1036 cases, 0 failed, t: 439s
PASS :white_check_mark:

clang.Release -Dassert=ON
logfile
1035 cases, 0 failed, t: 405s
PASS :white_check_mark:

gcc.Debug -Dstatic=OFF
logfile
1036 cases, 0 failed, t: 292s
PASS :white_check_mark:

gcc.Release -Dassert=ON
logfile
1035 cases, 0 failed, t: 423s
PASS :white_check_mark:

gcc.Debug -Dstatic=OFF -DBUILD_SHARED_LIBS=ON
logfile
1036 cases, 0 failed, t: 292s
PASS :white_check_mark:

gcc.Debug, NINJA_BUILD=true
logfile
1036 cases, 0 failed, t: 275s
PASS :white_check_mark:

msvc.Debug -Dunity=OFF
logfile
1033 cases, 0 failed, t: 1211s
PASS :white_check_mark:

msvc.Release
logfile
1032 cases, 0 failed, t: 416s
PASS :white_check_mark:

clang.Debug -Dunity=OFF -Dsan=address, PARALLEL_TESTS=false, DEBUGGER=false
logfile
1036 cases, 0 failed, t: 1068s
PASS :white_check_mark:

clang.Debug -Dunity=OFF -Dsan=undefined, PARALLEL_TESTS=false
logfile
1036 cases, 0 failed, t: 1174s
PASS :white_check_mark:

Is is possible to do these checks on non-validating nodes too? Some "censorship probes" scattered throughout the network (to have better chances of receiving censored valid transactions) would probably be another use case for this and maybe even better suited for the task than validators.

@MarkusTeufelberger: you could, I guess, but it could result in false positives, which is something I'd like to avoid. The protocol is such that if a validator proposes some transaction T that's valid but doesn't make it into consensus for round X, it's going to have priority for round X+1. That's something that doesn't happen with regular servers.
For that reason, I think it's better to only perform these checks on validators. If someone is interested in probing this, running a validator is no more expensive or computationally intensive than is running a regular node.

I copied the header from some other file and didn’t really think much about it so, 2016. Will fix. Thanks!

I haven't reviewed yet, but two things stick out. First, typo in commit message, "every validator[s] must". Second, this probably should be enabled on non-validators as well as validators. All participants want to now if censorship is affecting the network.

@JoelKatz: I considered making this available for non-validators, but I believe it would complicate things unnecessarily and not be as good. My rationale, copy-pasted from an earlier message to this thread:

The protocol is such that if a validator proposes some transaction T that's valid but doesn't make it into consensus for round X, it's going to have priority for round X+1. That's something that doesn't happen with regular servers.
For that reason, I think it's better to only perform these checks on validators. If someone is interested in probing this, running a validator is no more expensive or computationally intensive than is running a regular node.
To do what you suggest would require adding more (and more complicated) code which is something I’d like to avoid.

If you believe it's super-important to have this operate on non-validators as well, we'll have to go back to the drawing board and design something more complicated.

I do feel fairly strongly that everyone who uses the system wants to know if they're seeing censorship, whether they're running a validator or not. If you see censorship, whether you're running a validator or not, that's unexpected and indicates something is wrong that a human should look at.

@JoelKatz, you and @MarkusTeufelberger have convinced me that the best thing to do is to have this running on every server and not just validators. I will update this PR accordingly. Thanks.

Rebased against 1.2.0-b5 and modified the code so that every server performs censorship detection as long as it entered a round synced to the network.

That's an interesting point, and I agree that we should do this. But I think I'm going to punt right now. I want to get censorship detection merged so it can be included in 1.2.0. We can augment the code to log in a future PR.

authors: JoelKatz MarkusTeufelberger nbougalis ripplelabs-jenkins


text:
SYSSUSP_SUSPEND should allow platform-specific quiescent states, not only WFI

Currently, the SYSSUSP_SUSPEND service description contains the following requirement:

The application processor which called this service must enter into the WFI state by executing the WFI instruction. The platform microcontroller will transition the system to the requested SUSPEND_STATE upon the successful WFI state transition of the application processor.

However, not all implementations use the WFI instruction to enter into a quiescent state. The HSM_HART_STOP service allows for this flexibility:

The hart upon successful acknowledgement can perform the final context saving if required and must enter into a quiesced state such as WFI which can be detected and allow the platform microcontroller to proceed to stop the hart. The mechanism to detect the hart quiesced state by the platform microcontroller is platform specific.

The SYSSUSP_SUSPEND service should be updated to use similar language.

Yes thanks @SiFiveHolland , let me raise the PR

source: gharchive/issue

authors: SiFiveHolland pathakraul

repo: riscv-non-isa/riscv-rpmi

license_type: permissive

license_source: github-api


text:
Vector Test Generator

Write a python script to automatically generate vector json tests. Add support for the script to be able to parse Mavis as well to generate the tests.

hey @aarongchan Can I take up this issue?

@aarongchan , @danbone I’ve completed a script for generating vector JSON tests and parsing Mavis data. Could you advise on the best directory to place this file in the riscv_model project? Should it go in tests, core, or elsewhere? Your guidance on adhering to project conventions would be greatly appreciated.

authors: Shubhf aarongchan

repo: riscv-software-src/riscv-perf-model


text:
Value of vstopi.IPRIO cannot be 256 for candidate #3

Hi,
The width of vstopi.IPRIO is 8 bits, the maximum value is 255, but candidate 3 says priority number 256 is used.

Read-only CSR vstopi is VSXLEN bits wide and has the same format as stopi:
bits 27:16 IID
bits 7:0 IPRIO

if bit 9 is one in both vsip and vsie, and neither of the first two cases applies:

a supervisor external interrupt (code 9) with priority number 256;

As specified by Table 5.5 on page 66, IPRIO should be set to 255 in this case.

repo: riscv/riscv-aia


text:
actionlint errors: shellcheck double quote to prevent globbing; deprecated command set-output

I  ran actionlint https://github.com/rhysd/actionlint on repo:
kbroch@~/rvi/riscv-docs-base-container-image on  main via 🐍 v3.11.2 (venv)
❯ actionlint
.github/workflows/build.yaml:32:9: shellcheck reported issue in this script: SC2086:info:1:33: Double quote to prevent globbing and word splitting [shellcheck]
   |
32 |         run: echo "NOW=$(date +'%m%d%Y')" >> $GITHUB_ENV
   |         ^~~~
.github/workflows/weekly_build.yaml:33:14: workflow command "set-output" was deprecated. use `echo "{name}={value}" >> $GITHUB_OUTPUT` instead: https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions [deprecated-commands]
   |
33 |         run: echo "::set-output name=date::$(date +'%Y-%m-%d')"
   |              ^~~~

IMO fixing these are useful and we should consider adding pre-commit hook

Fixed with #9

repo: riscv/riscv-docs-base-container-image


text:
What is the step-by-step process for two-stage address translation

In the latest pdf build (5/23/23) of the Privileged Architecture, the step-by-step description in 5.3.2 Virtual Address Translation Process is clear and concise for single stage translation. However, when we move to two-stage translation, the differences specified in  9.5.1 Guest Physical Address Translation (e.g., hgatp substitutes for the usual satp) seem to be incomplete.
For example, applying step 7 in 5.3.2  (as updated by 9.5.1) "if the original memory access is a store, also set pte.d to 1" is a bit confusing when trying to apply it to G-stage translations. The intent is probably for all traversed G-stage PTEs to have A=1 and, if the operation that kicked off the original translation was a STORE, the final G-stage PTE (i.e. pointing to the SPA of the page of the STORE) needs D=1. We should have a clarification of some sort for this.
Furthermore, the updated steps in 5.3.2 do not provide any guidance on how to update the G-stage PTE that points to the VS-stage leaf cell. Presumably, if the VS-stage leaf cell is updated, this G-stage that points to it must have D=1.
It appears to me that the various models  (SPIKE, RISC-V, and QEMU) are missing this last step (actually, SPIKE is currently being corrected based this issue being raised in  Are G-stage D bits set correctly as a result of setting a VS-stage D bit? #1447 with the changes in
A/D updates in G-stage PTE #1448)
I suggest that we add clarifications to the Privileged Architecture in the form of a step-by-step Two-stage Virtual Address Translation Process in 9.5.1 Guest Physical Address Translation. Alternatively, we  could add a normative description that explicitly calls out of these differences in two-stage translations.

Alternatively, we could add a normative description that explicitly calls out of these differences in two-stage translations.

The section 9.5.1 does call out these differences:

hgatp substitutes for the usual satp;
For the translation to begin, the effective privilege mode must be VS-mode or VU-mode;
When checking the U bit, the current privilege mode is always taken to be U-mode; and
Guest-page-fault exceptions are raised instead of regular page-fault exceptions.
For G-stage address translation, all memory accesses (including those made to access data structures for VS-stage address translation) are considered to be user-level accesses, as though executed in U-mode.
Access type permissions—readable, writable, or executable—are checked during G-stage translation the same as for VS-stage translation. For a memory access made to support VS-stage address translation (such as to read/write a VS-level page table), permissions are checked as though for a load or store, not for the original access type. However, any exception is always reported for the original access type (instruction, load, or store/AMO).
The G bit in all G-stage PTEs is reserved for future standard use.

We agree that section 9.5.1 calls out those differences. However, applying those differences to the single-stage step-by-step virtual address translation process does not yield a complete two-stage step-by-step description. There is no mention in these steps, for example, of when to set the D bit in a G-stage PTE as a result of the setting of an A bit in a VS-stage PTE.
Since people seem to be relying on these step-by-step instructions when creating models or RTL implementations, it would be helpful to create a version that explicitly and completely covers two-stage translation.

Probably would be useful for writing the complete ACT tests as well.
On Tue, Sep 5, 2023 at 12:09 PM Ken Dockser @.***>
wrote:

We agree that section 9.5.1 calls out those differences. However,
applying those differences to the single-stage step-by-step virtual
address translation process does not yield a complete two-stage
step-by-step description. There is no mention in these steps, for example,
of when to set the D bit in a G-stage PTE as a result of the setting of an
A bit in a VS-stage PTE.
Since people seem to be relying on these step-by-step instructions when
creating models or RTL implementations, it would be helpful to create a
version that explicitly and completely covers two-stage translation.
—
Reply to this email directly, view it on GitHub
https://github.com/riscv/riscv-isa-manual/issues/1103#issuecomment-1707175122,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHPXVJSQXZJGYILHZVBX4A3XY52HDANCNFSM6AAAAAA4DJNDPI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Or (to Ken's and Ved's last posts) just add one more bullet to the section 9.5.1 bullet list that explicitly makes clear when to set the D bit in a G-stage PTE as a result of the setting of an A bit in a VS-stage PTE.

Section 9.5.1 states:

For a memory access made to support VS-stage address translation (such as to read/write a VS-level page table), permissions are checked as though for a load or store, not for the original access type.

For added clarity, the phrase "permissions are checked as though for a load or store" could be expanded to "permissions, A, and D bits are checked as though for a load or store".

"permissions, A-bit, and the D-bit are checked" reads in a confusing way.  I assume this is trying to refer to setting of G-stage A&D bits as a function of the VS-level PTE read or write access (and not of the original access type)?
If so, then this might read better as:
For a memory access made to support VS-stage address translation (such as to read/write a VS-level page table), permissions and the need to set A and/or D bits at the G-stage level are checked as though for a load or store, not for the original access type.

Also, consider expanding "for a load or store" to explicitly state "for an implicit load or store." The distinction between implicit and explicit guides the decision on the value reported in [h|m]tinst when a guest-page fault trap occurs.
As follows:
For a memory access made to support VS-stage address translation (such as to read/write a VS-level page table), permissions and the need to set A and/or D bits at the G-stage level are checked as though for an implicit load or store, not for the original access type.

The addresses in hgatp and the G-stage paging structures are supervisor physical addresses. Please clarify what the second bullet implies by "to support G-stage address translation".

authors: allenjbaum gfavor kdockser ved-rivos

repo: riscv/riscv-isa-manual


text:
xTVAL missing from MEDELEG/MIDELEG description

It seems like xTVAL delegation rules are missing
https://github.com/riscv/riscv-isa-manual/blob/7cf3673198998d38b7235c879974cdcfa0912031/src/machine.tex#L1044

You're right, thanks.

authors: as-sc aswaterman


text:
Add Bubble Sort in Algorithm folder

There is a folder "Bubble sort" in DSA/JAVA/Algorithm you need to add java source file (your code) and readme file describing algorithm in details.

Would love to work on this @risingstar-bit . Please assign this to me :)

Would love to work on this @risingstar-bit . Please assign this to me :)

Assigned👍

Thanks :)

Please assign.I am done with it.@risingstar-bit.Will make pr immediately.

Please assign.I am done with it.@risingstar-bit .Will make pr immediately.

You didn't ask me to assign this.

Bubble sort is already added

repo: risingstar-bit/Compose-Community

license: MIT


text:
Support abort state in transaction

Is your feature request related to a problem? Please describe.
In postgresql, transcation will encouter abort state when occurs error. It will refuse the following request until the COMMIT or ROLLBACK in this state.
// Postgresql
test_db=> begin read only;
BEGIN
test_db=*> select v1;
ERROR:  column "v1" does not exist
LINE 1: select v1;
               ^
test_db=!> select 1;
ERROR:  current transaction is aborted, commands ignored until end of transaction block

// RW
dev=> begin read only;
BEGIN
dev=*> select 1;
 ?column?
----------
        1
(1 row)

dev=*> select v1;
ERROR:  QueryError: Bind error: failed to bind expression: v1

Caused by:
  Item not found: Invalid column: v1
dev=*> select 1;
 ?column?
----------
        1
(1 row)

Describe the solution you'd like
No response
Describe alternatives you've considered
No response
Additional context
No response

Tracked in #10736

Let's keep it open to track it. 😂

Currently we only support read-only transaction, so it's not a big deal. But for better compatibility with Postgres wire protocol, it's still a good-to-have.

authors: BugenZhao ZENOTME

repo: risingwavelabs/risingwave


text:
feat(batch): support batch read for file source

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
This pr will introduce batch read for new file source(s3_v2, gcs), and the next pr will bring PredicatePushdown for them.

Checklist

[ ] I have written necessary rustdoc comments
[ ] I have added necessary unit tests and integration tests
[ ] I have added test labels as necessary. See details.
[ ] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934).
[ ] My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
[ ] All checks passed in ./risedev check (or alias, ./risedev c)
[ ] My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

[ ] My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

[ ] My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

The e2e test passed:

source: gharchive/pull-request


text:
refactor: no need to resolve hanging channel

Signed-off-by: Bugen Zhao i@bugenzhao.com
I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
The hanging channel is a channel that's external for a table fragments subgraph. We introduced this for MV on MV long ago, but after https://github.com/risingwavelabs/risingwave/pull/4045 and https://github.com/risingwavelabs/risingwave/pull/6170, this becomes not that necessary: we can simply create a pair of channels if not found in the ChannelPool.
https://github.com/risingwavelabs/risingwave/blob/b1891423a68b98dff39d7220a891cdea8bd67951/src/stream/src/task/mod.rs#L123-L138
This is a preparation step for #7908.
Checklist

[x] I have written necessary rustdoc comments
[x] I have added necessary unit tests and integration tests
[x] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features).
[x] I have demonstrated that backward compatibility is not broken by breaking changes and created issues to track deprecated features to be removed in the future. (Please refer to the issue)
[x] All checks passed in ./risedev check (or alias, ./risedev c)

Documentation

[x] My PR DOES NOT contain user-facing changes.

Click here for Documentation
Types of user-facing changes
Please keep the types that apply to your changes, and remove the others.

Installation and deployment
Connector (sources & sinks)
SQL commands, functions, and operators
RisingWave cluster configuration changes
Other (please specify in the release note below)

Release note

Signed-off-by: Bugen Zhao

This PR is so successful...

authors: BugenZhao shanicky


text:
[Feature Request] onLoad callback

Description
I've noted the web version has an onLoad callback when loading files over the URL. I dug through the code and I think this may not be even exposed from native iOS/Android level?
Would be great for us to have this functionality so we could show some sort of loaders while waiting for the Rive animation to be loaded. If this can be done on the native side I would be happy to write the bindings on React native's JS layer :)
Provide a Repro
N/A
Expected behavior
Have an onLoad Callback

I agree, I'm implementing animations with state, and it's quite complicated to find a way to understand the right time to set the initial state
For the moment this is the workaround but it seems very complicated to maintain
const BlobAnimation = () => {
  const [mood, setMood] = useState(-2);
  const [riveRef, setRiveRef] = useState<RiveRef | null>(null);

  useEffect(() => {
    if (!riveRef) return;

    setTimeout(() => {
      riveRef.setInputState(blobStateMachineName, 'mood', mood);
    }, 300);
  }, [mood, riveRef]);

  return (
    <>
      <Rive
        ref={setRiveRef}
        autoplay
        url={blobUrl}
        stateMachineName={blobStateMachineName}
        style={{ width: 200, height: 200 }}
      />
      <Button onPress={() => setMood((value) => value + 1)} label="mood + 1" />
    </>
  );
};

Any updates?

Any updates?

authors: SergeyYurkevich cosimochellini edgartoomik ridwansameer

repo: rive-app/rive-react-native


text:
Feature: Telegram zu notifiers hinzugefügt

Als kleine Ergänzung habe ich Telegram als möglichen notifier hinzugefügt.

Cool, vielen Dank. Sinnvolle PRs sind immer willkommen 😄

Top @pandaslide das Feature funktioniert wunderbar. Steht ab Release 5.6.2 bereit!

Danke für den schnellen Merge und das tolle Tool!


text:
Add Tech Stack Filter

Problems
The website can only filter the people/engineers only by their location. The employer might find it hard to search for specific engineers that match their requirements.
Solution

Add the Tech-Stack filter feature

Implementation

Added Svelte-Select library to provide a Select component with common features (e.g. Multi-values)
Added Tech-Stack filter component and function to filter people/engineers by inputted stacks
Repositioned filter layout (Tech-Stack and Location filter) using flex
Refactored filter function and implemented multiple filtering that triggers a single function. It would be easy to add another filter feature in the future

Wah, mantap sekali ini. Terimakasih 🙏

authors: luthfihizb rizafahmi

repo: rizafahmi/carikerja


text:
pair programming exercise

This was fun! Turned prompt to function!

looks great!  thanks for playing!

authors: ChanceHarmon rkgallaway

repo: rkgallaway/about-me


text:
Consider Supporting Alfred Gallery?

I apologize as I've just learned about this, myself, but apparently we can keep our workflows updated through the Alfred Gallery. I don't know what it takes to do such, but I was going to look at it later as a possible PR.

ooo i was unaware of this, but this is awesome. i've been dying for some official support for something like this given that packal is incredibly outdated. i will definitely look into adding this workflow to alfred gallery at some point

topic added here on official forums to get the ball rolling on getting access to submit the workflow

authors: SeanSith rkoval

license: mit

license_source: bigquery


text:
How do I get the test to run with specific environment variables set?

In order for my test to run properly, I need certain environment variables set.  As is, I can run the test fine outside of vscode, but when I use this extension, the test fails because a certain environment variable is not set.

You can open a PR to add the ability to use custom env vars :)
sounds like a good addition

authors: fmaddenflx rluvaton

repo: rluvaton/vitest-vs-code-plugin


text:
Do you plan to publish the codes (MAML, RL^2, PEARL) to reproduce the paper?

It would be very helpful if you could make it public.

Hi @emuemuJP, you can find code for the algorithms that you have listed in
https://github.com/rlworkgroup/garage , along with working examples on metaworld.

Please note that the above is not the exact code originally used in the metaworld paper, which is unfortunately not available.

Thank you for letting me know!

authors: avnishn emuemuJP krzentner

repo: rlworkgroup/metaworld


text:
🛑 Micro.blog is down

In 53dbcca, Micro.blog (https://roberto.mateu.me) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Micro.blog is back up in a29ed6b.

repo: rmateu/statuspage


text:
Update README.md

Adds the workaround from https://github.com/rmculpepper/iracket/issues/11 to the readme.

I am not a fan of copying files installed by a package manager to other places on the system. It clutters up your drive and can lead to issues when trying to uninstall.
IMO a better approach is to chance the lib-search-dir racket uses to find dynamic libraries. This can be achieved by something like:
cat /Applications/Racket\ v8.3/etc/config.rktd

#hash(
(build-stamp . "")
(catalogs . ("https://download.racket-lang.org/releases/8.3/catalog/" #f))
(doc-search-url . "https://download.racket-lang.org/releases/8.3/doc/local-redirect/index.html")
(lib-search-dirs . (#f "/opt/homebrew/lib")))

This has the additional benefit that Racket will be able to find other dynamic libs installed with homebrew.

authors: NightMachinary mpcjanssen

repo: rmculpepper/iracket


text:
Problem when generating audio for new epoch

Traceback (most recent call last):
File "train.py", line 335, in
main()
File "train.py", line 326, in main
verbose=0,
File "/usr/local/lib/python3.7/dist-packages/tensorflow/python/keras/engine/training.py", line 1229, in fit
callbacks.on_epoch_end(epoch, epoch_logs)
File "/usr/local/lib/python3.7/dist-packages/tensorflow/python/keras/callbacks.py", line 435, in on_epoch_end
callback.on_epoch_end(epoch, logs)
File "/content/gdrive/My Drive/prism-samplernn/callbacks.py", line 103, in on_epoch_end
self._generate(ckpt_path, self.generation_args)
File "/content/gdrive/My Drive/prism-samplernn/callbacks.py", line 109, in _generate
args['temperature'], args['seed'], args['seed_offset'])
File "/content/gdrive/My Drive/prism-samplernn/generate.py", line 135, in generate
file_name = f'{file_name}_t={temperature[i][0]}.wav'
IndexError: too many indices for array: array is 0-dimensional, but 1 were indexed

@deccolquitt Hi, looks like a problem with the value being passed to temperature parameter. Could you post how you're calling the train.py script, with the parameters? Thanks.

@deccolquitt OK I can see what's causing it - I'm assuming you weren't explicitly passing a temperature value. I've identified a bug in that circumstances, am fixing it now.

Hi, thanks for getting back so quickly, just in case you need it, here are the parameters I was using anyway:
!python train.py
--data_dir ./chunks
--num_epochs 100
--batch_size 64
--max_checkpoints 2
--checkpoint_every 1
--output_file_dur 5
--sample_rate 16000

Thanks, that's just as I expected. It would be using the default temperature if you don't explicitly set it (either as a list or as one float value), but the default value was not being passed down internally in the correct format
Should work fine now, just pushed the fix.

brilliant, will it try tomorrow

BTW, we're experimenting with replacing the default config params, you might want to try these:
{
    "seq_len": 512,
    "frame_sizes": [2,8],
    "dim": 1024,
    "rnn_type": "gru",
    "num_rnn_layers": 1,
    "q_type": "mu-law",
    "q_levels": 256,
    "emb_size": 256
}

These worked well for our Beethoven Piano Sonata model, though as always YMMV.

authors: deccolquitt relativeflux

repo: rncm-prism/prism-samplernn


text:
jira.plugin.zsh:52: parse error near `else'

Two else branches in this if......

I'll be darned. Reproduces for me on OS X if I just add jira to my plugins list.
Last login: Mon Jun 15 16:43:18 on ttys001
/Users/janke/.oh-my-zsh/plugins/jira/jira.plugin.zsh:52: parse error near `else'
[@ in ~]
$

Looks like it was caused by a recent commit for #2898, probably as a result of bad merge conflict resolution with the jira-prefix support introduced in #2955. (The fact those are out of order makes me think we're looking at merge conflict problems and not a bad individual PR.)

Agreed, now idea how a conflict resulted that way but this is bad.

I think it's that #2898 just had the bug in the first place after it was rebased after 2955 was merged (see its comment history), and wasn't re-tested after the rebase. So the "merge conflict" happened inside #2898 when it was rebased, not when you pulled it in to easymerge or anything after that. The bug's present in tsldh/master if you check that out on its own and the diffs are clear.

Oh yes, good catch! So indeed the merge conflict was triggered (and improperly solved) during the rebase.

Taking a look, I'll see if #4041 solves it...

#4041 tests good, let's get that reopened and pulled in.

I have same problem.

@tresni gj

I have same problem

Also experiencing the same issue.

I've been getting this same issue since the last zsh update I had.

is there unit tests on oh-my-zsh?

To all: #4041 should fix this issue.
@diwu1989 not at all, but we are working on improving the update/release process, and any suggestion or contribution is welcome.

Sad, also having this issue still.

Same here:
-> % upgrade_oh_my_zsh --help
Upgrading Oh My Zsh
From https://github.com/robbyrussell/oh-my-zsh
 * branch            master     -> FETCH_HEAD
Current branch master is up to date.
[...]
-> % zsh
/Users/fabian/.oh-my-zsh/plugins/jira/jira.plugin.zsh:52: parse error near `else'

Unit tests with some build tool would be a good option.
oh-my-zsh/plugins/jira/jira.plugin.zsh:52: parse error near `else'

Did the fix never get pushed to master?

Hi all, this will be merged later today. Sorry for the long wait!
El mié., 1 jul. 2015 a las 12:51, Ion Caza (notifications@github.com)
escribió:

Did the fix never get pushed to master?
—
Reply to this email directly or view it on GitHub
https://github.com/robbyrussell/oh-my-zsh/issues/4027#issuecomment-117601221
.

authors: JohnCaza JohnSmithX Schrank apjanke arnoldnedap diwu1989 ericop feiyan35488 francisbautista hasannawaz ladyborg mcornella ncanceill tresni xyalan

repo: robbyrussell/oh-my-zsh


text:
The only thing vi-mode does is ignore some key presses

I used to use bindkey -v to use vi-like keybindings in zsh. After installing oh-my-zsh, this stopped working. I changed the line to plugins=(vi-mode). Now if I hit escape and try to hit command keys it will ignore some number of key presses and then start inserting again. From what I can tell, it will skip one key press if I start by hitting '$' and two key presses if I start by hitting '0'. Here is a mapping from key sequences to observed behavior:
ESC 0 0 0 => one 0 is inserted
ESC 0 0 $ => one $ is inserted
ESC 0 $ $ => one $ is inserted
ESC $ $ $ => two $'s are inserted
ESC $ $ 0 => one $ followed by one 0 is inserted
ESC $ 0 0 => two 0's are inserted
ESC $ 0 $ => one 0 followed by one $ is inserted
ESC 0 $ 0 => one 0 is inserted

I am running Arch Linux with zsh verison 5.3.1. I have no other oh-my-zsh plugins installed. I have zsh-syntax-highlighting installed, but disabling it did not change the behavior of the program.

Can't reproduce on
zsh 5.3.1
archlinux
urxvt
Can you try to use another terminal, like urxvt?

I found behavior you talking about.
I cut all set -o vi, binkey -v and vi-mode plugin from my zsh.
"ESC 0 0 0 => one 0 is inserted" is emacs-mode.
So you should overlook your zshrc and all includes.

Alright, I found two problems with my zshrc, and after resolving them everything appears to be working as expected.
The first problem that I had was that I thought that the line plugins=(vi-mode) would enable the plugin, not just load it, so I had removed my bindkey -v line when I discovered that this plugin exists.
The second problem that I had was that I sourced oh-my-zsh at the end of my zshrc, after plugins=(vi-mode). I did this because I also use zsh-syntax-highlighting which says that it needs to be the last thing sourced, and it seemed natural to group the sourcing of external files.
Thanks for the help, much appreciated.

authors: SaffronSnail slavaGanzin


text:
Add robin theme

Just slight modification of agnoster

adding timestamp
icon fixup

New themes are currently not being accepted, but you can add a link to it on the external themes wiki page.

authors: robinwolny stevenspasbo


text:
adding Productboard

https://www.productboard.com/pricing/

@deethreedouble it appears productboard raised their pricing for enterprise to be $200/user/month (without any discounts)
I just went through the sales process with them and they are able to shave SSO off a la carte, but at the total per-user cost of $167/month.

authors: CalebAlbers deethreedouble

repo: robchahin/sso-wall-of-shame


text:
So, where are the icons?

This is the first time I've ever done this.
https://1drv.ms/i/s!AlnGeQSYLUVaoocds4rUwd7LmxHtzg
https://1drv.ms/i/s!AlnGeQSYLUVaoocenxf_W_aZSQsSfg
I'm new to a lot so any way to know what I'm doing wrong based on the screenshots? Everything is updated to the fullest.
Checklist:

I'm using Visual Studio Code Version [1.x.x] [Stable/Insider]
I'm using the extension version [1.x.x]
[ ] I've regarded to the FAQ and they did not help.
My system is: [OS] [Arch]
[ ] I'm sure this issue is not a duplicate?
[ ] I want to create an icon request(if not, remove these lines below):
- Type: [extension/folder]
- Icon Name: [name]
- Sample original Icon(32x32/png/transparent whenever possible): [url]
- Extensions: .just, .a, .bunch, .of, .extensions
- [ ] I crossed out "Description", "Steps to reproduce", "Expected behaviour" and "Actual behaviour".

Description:
[short description of the bug, enhancement or feature request]
[PLEASE INSERT THE ERROR(S) YOU CAN SEE IN DEV CONSOLE HERE]
[Where is the dev console? Launch code, click on "Help" in the menubar at the top, click on "Toggle Developer Tools", and click on that window on "Console".]
Steps to reproduce:

First step
Second step
And you can count yourself, can't you?

Expected behaviour:
[these lines are only important if you're submitting an issue]
Actual behaviour:
[these lines are only important if you're submitting an issue]

I read and read and found that they were disable in file icons under preferences. I read in the extension description with how to turn them off or disable them, so I checked and there it was. I didn't know this was possible as I could disable the extension from the extension list, but when I enabled them, I thought they were enabled. So one has to enable and then make sure they are double enabled under file icons. Sorry I had no idea this existed. You may delete this issue post as it is pointless and silly noobish.
Sorry to bother and thank you for the cool icons!

repo: robertohuertasm/vscode-icons


text:
🛑 Revista Cómo ves is down

In e1cb84c, Revista Cómo ves (http://www.comoves.unam.mx) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Revista Cómo ves is back up in 111d452 after 5 minutes.

repo: robertormzg/upptime-dgdc


text:
Support eoy definition in taskwarrior 2.5.2 (Closes: #87)

taskwarrior 2.5.2 switched the end of year definition:
$ task calc eoy
2000-12-31T23:59:59 (version 2.5.1)
2021-01-01T00:00:00 (version 2.5.2)

Coverage decreased (-1.7%) to 90.488% when pulling 57384842951b36a2201a3a5db3586201ed8991f2 on jspricke:develop into 8b045552526e83e6d592aaa8d64b115d7cc7bb54 on robgolding:develop.

Coverage decreased (-1.7%) to 90.488% when pulling 57384842951b36a2201a3a5db3586201ed8991f2 on jspricke:develop into 8b045552526e83e6d592aaa8d64b115d7cc7bb54 on robgolding:develop.

Ah, just realised the usage of six is causing an issue here - no need for that anymore as this library is Python 3 only! If you can fix that up I'll merge this PR!

Fixed. (I wrote it for the Debian version, initially).
Btw. can you push tags for the latest versions? pypi lists 2.2.1 but latest tag is only 1.3.0, or is pypi the official source?

Thanks, and Happy New Year! Merging this now. I've also pushed tags for the missing versions to match PyPI.

Thanks, and Happy New Year! Merging this now. I've also pushed tags for the missing versions to match PyPI.

authors: coveralls jspricke robgolding

repo: robgolding/tasklib


text:
Чи могли б оновити додаток, а також підсказати як використовувати квантонізовану версію?

Чи могли б оновити додаток, а також підсказати як використовувати квантонізовану версію?
Намагався запустити, сходу не запустилось, після встановлення залежностей з файлу залежностей, видавало помилку, Бо вже не сумісне з бібліотекою.
Після того, як використовуючи ChatGPT з горем пополам запустив, то свопнуло на 80 гб. Чи могли б підсказати, як запустити так, щоб влазило в 10 гб пам'яті?

Завчасно дякую!

@olehbozhok, доброго дня, тут демо нової моделі, можете взяти код як запустити звідти:
https://huggingface.co/spaces/robinhad/UAlpaca
В цьому файлі є приклад як запустити:
https://huggingface.co/spaces/robinhad/UAlpaca/blob/main/app.py

authors: olehbozhok robinhad

repo: robinhad/kruk


text:
Make the change method the default and comment out up/down

This is potentially a big change moving forwards.
In newly created migrations up and down would be commented out by default and change would become the default method.
This is the opposite of the present behaviour.
Background
The change method is far simpler to use and suffices for most users. The up /  down methods are more flexible but should be used less.

Does change() work correctly with data migration, not just schema migration? In other words, if I modify a column in a table and have to adjust existing rows based on a SELECT, won't I have to create a custom down() method? Or if I drop a table/column in a migration and need to recreate it on rollback? Of course, you are just talking about changing the default here and I will still be able to override it by creating an up()/down() method when I need it?
I am looking at moving to phinx on a project and am trying to understand what the approximate limits are to understand the impact of planned changes and how I should organize my initial setup.

@evought see the note about limitations at the end of http://docs.phinx.org/en/latest/migrations.html#the-change-method

"see the note about limitations..."
Understood, thank you. Been experimenting with the behavior this evening and it seems fairly logical.

With regard to the current state, and the proposal to make change() the default operation, would it be advantageous (and more defensive) to validate that the migration can be rolled-back BEFORE the migration takes place? Maybe by using a variant of the adapters that only allow the reversible methods?
So, up() and down() would use the current adapter and I am at will to do whatever I want.
But change() would use a limited adapter that simply does not have any method that cannot be reversed.
For me, the advantage here is that the developer is protected from making non-reversible mistakes. Make their/our lives easier.

Hey @RQuadling I'd prefer to keep Phinx as dumb as possible. Some people run Phinx on massive production systems with 100's of tables and terrabytes of data. I'd sleep much better knowing they are in full control of their migrations (even if they write something nasty). If Phinx started to become opinionated about migrations I'm worried it might lead to problems. Better to keep it simple.

p.s moving to 0.5.0 now.

I agree with @RQuadling, those people would not have full control on their migration because they would unknowingly make a change in the change() method that can't be reverted. The full control is having up() and down() and being able to make mistakes because of my code and not phinx's.

What I was saying is that the methods that can be called in the change() method should be limited to reversible ones. If a user requires something that cannot be automatically reversed in a migration then they need to use up() and down().

done in 5ffb2324f5789c8919271dd2c6bb0b448a0b02a1

I suppose we need to see a use case of a non reversible change() call. I'm still not sure that every use of change IS reversible.
up()/down() IS the "in the hands of the developer" control that is required.
On the other hand, I never use change(), so meh!

authors: RQuadling evought maxgalbu robmorgan rquadling shadowhand

repo: robmorgan/phinx


text:
Deprecate showInterface from Font initialization?

I'm not sure how desirable or immediately necessary this change is, but given that there's potential for a clean break with the roboFab implementation, I'm opening this issue as a point of discussion.
Usually when you see a boolean option for any method, it's either a signal that there is a method that is doing double duty, or domain model that hasn't been defined. I'm wondering if this isn't a place where another object might be introduced in order to better encapsulate the design space that fontParts works within:
Font('foo.ufo', showInterface=True)
# vs. proposed:
Editor().open(Font('foo.ufo'))

I'd propose introducing some kind of Editor or Application concept that would be a generic container that explicitly interacts with whichever application is the subject of a fontParts implementation.
I think that this could be a cleaner separation of responsibilities, and would allow the implementation of Font to be ignorant of the details of the manipulating the UI, which I like. There are ramifications for testing (isolating UI concerns to fewer areas), and for conceptually decoupling interface from editor (the latter of which may or may not include an interface that can be shown, but still have the concept of opening a font). It could also mean that a specialized Editor object could open different kinds of resources (e.g. just glyphs, features, etc.).
It would still be possible to maintain the old showInterface API (with a deprecation warning?).
Thoughts?

My two cents:
Most folks writing scripts will have a much easier time with:
Font('foo.ufo', showInterface=True)

I see the appeal of
Editor().open(Font('foo.ufo'))

on a higher level, but would not want the first to go away. This is based on my experience teaching typeface designers to write code, they are not out to be the world's best programmers, they just want to easily understand something and get on with it.

I guess it comes down somewhat to the philosophy of the library… Keeping both feels like it violates the Pythonic tenant of one right way, so I suppose this could be something that just can't change.

Hm, I kinda like the general idea. I think there are some gnarly backwards compatibility and environment things that we need to think through. For example, not all environments have an interface and not all environments have a no-interface way of opening a font. OpenFont("foo.ufo") in FontLab and RoboFont will show an interface. The same thing in NoneLab will not.
Let me think on it...

I was looking through the OpenFont and friends after I opened this issue. For me these have always felt like convenience functions wrapping the mid-level interfaces, to mask some of the underlying implementation details. Perhaps it's worth considering what the primary interface to the library is, and which APIs are changeable, even if this proposal goes too far in introducing new functionality.
The the case of NoneLab Editor#open could simply be a no-op.

I also don't want to imply that Editor is the most appropriate name for this—nor Application. I can think of several situations where one or the other may not be the appropriate term for the context. Interface could be general enough, or at least on the opposite end from Editor

I would agree with @benkiel. One thing to consider is that these calls are part of almost all robofab centric scripts. It would break whatever portability they have. "Clean break" is expensive.

You could kind of use the same reason against the creation of this library entirely. I guess my question is still, if portability is a goal, then which interfaces are changeable and which ones are frozen? Is there a priority among interfaces? One of the stated goals is to remove cruft, and I think that—arguably—this keyword arg is a wart, in not at least crufty.
The second question that I have would be, if these changes are not possible—or not a priority—now, is it possible they could be in the future? Is there a plan to make a long-term roadmap possible? I think that having this library versioned and available on pypi would go a long way to being about to say "now that this is v.2 here are the breaking changes" and offer deprecation warnings up to that point.

I guess my question is still, if portability is a goal, then which interfaces are changeable and which ones are frozen?

There isn't a hard and fast rule. It's more of an intuitive, "How many scripts do we think this will break?" vs, "Ugh, I can't live with this mistake from 2003 anymore so everyone can just deal with the break." kind of thing.

The second question that I have would be, if these changes are not possible—or not a priority—now, is it possible they could be in the future?

Yes. Right now the focus is on trying to get reasonable compatibility with RoboFab so we can stop answering RoboFab tech support questions. After that, we're going to need to bring the API up to date with new stuff.
All that said, we need to make sure that we keep in mind that this is supposed to be a simple scripting API for non-programmers. I've been struggling with that from time to time as evidenced by the looks I got when I proposed a couple of weird things at Typographics. 😕

I've been thinking about an Editor object a bit more. It could be useful for abstracting some of the other common interface interactions that we have needed. For example, robofab.interface.all.dialogs. <bigboldtype>This was a huge headache in RoboFab so I'm sweating a bit even bringing it up.</bigboldtype> But, I know how valuable being able to have a common API for triggering extremely simple user interactions from my experiences writing scripts that had to work equally well in RoboFont and Windows FontLab. Something like this:
app = Application()
path = app.showGetFile(...)
go = app.askYesNo(...)
# etc.

<bigboldtype>FontParts would not implement any of this. Ever. At all. It would only define the API.</bigboldtype> Still, I'm shaking a bit just thinking about it. It's a short road from here to <insert horrible "universal" windowing API name here>.

We've put UI things into fontParts.ui, this is explicitly for an implementation of fontParts to handle, fontParts is not going to make ui components. These are simple, for common things that a scripter would likely want, anything fancier can be done with something else (dialogKit, vanilla, etc). As such, I'm going to close this for now, but it may be worth coming back to the idea of an Editor object at some point.

authors: LettError benkiel jackjennings typesupply

repo: robofab-developers/fontParts


text:
Finished main development of the DVL drivers

I also moved the drivers directory up a level like was in the refactor notes.

Also need to work on the actual build integration, at the moment the makefile just spits things into the bin directories next to the source, which probably isn't the best idea.

repo: robotics-at-maryland/qubo


text:
Path intersections between (x,y, x,y)

Hi,
The Glyphs API has intersectionBetweenPoints and while looking for a UFO equivalent, I found robofab.path.intersect; I was wondering if this feature is missing from fontParts or if it was intentionally left out as out-of-scope? Or maybe it is implemented with a different name and I just missed it?

A lot of half-working apis where removed in the transition between robofab and fontParts: easier to maintain, smaller codebase, ... . The path module was not ported over to fontParts.
BooleanOperations has getIntersections of  list of contours. see https://github.com/typemytype/booleanOperations
from booleanOperations import getIntersections

f = CurrentFont()
g1 = f["A"]
g2 = f["B"]

result = getIntersections(g1.contours + g2.contours)

print(result)

good luck!

Hi @typemytype - thank you, but I think I did not do a great job wording my question - or possibly I misunderstood robofab.path.intersect - but this is not the kind of intersection I am looking for.  Rather than the intersection of glyphs themselves, I'm trying to run a straight line run across a glyph from arbitrary point (x,y) to another arbitrary point (x,y) - pretty much the measurement or slice tool but without creating new points, and without a GUI
Hopefully this demonstrates the values I am looking for in such an API - imagine I were to run some imaginary code like getLineIntersection((-1000,200), (1000,200)) and would get something like {51,200}, {263, 200}, {446, 200}, {658, 200} as an output.
I would love to know what you recommend! (And if it is something that might make sense in fontParts, I would be happy to try and contribute)

if you are in a RoboFont world then you can use IntersectGlyphWithLine
from mojo.tools import IntersectGlyphWithLine

result = IntersectGlyphWithLine(CurrentGlyph(), ((startX, startY), (endX, endY))
print(result)

see https://robofont.com/documentation/building-tools/api/mojo/mojo-tools/#mojo.tools.IntersectGlyphWithLine
good luck!

Something along these lines could work in fontShell on the command line:
`from booleanOperations import getIntersections
from fontParts.fontshell.glyph import RGlyph
def getLine(sx,sy,ex,ey):
line = RGlyph()
line.width = ey
pen = line.getPen()
pen.moveTo((sx, sy))
pen.lineTo((ex,ey))
pen.closePath()
return line.contours
def getLineIntersection(glyph, sx,sy,ex,ey):
return getIntersections(getLine(sx,sy,ex,ey) + glyph.contours)`
I've tested a bit, didn't quite get it working, but that's the idea

Thanks again for the quick response! That's exactly the functionality I am looking for, but outside of RoboFont - hopefully I would just be able to point a Python script to a UFO file

@jpt It's not in fontParts, as @typemytype said; it didn't make the move over from roboFab. Hopefully the bit above helps set you down the path to do it with a script.

Thank you @benkiel - my previous reply happened at the same time as yours; I see now how the two libraries can work together with RGlyph as the basis -- I'll get experimenting! Closing the issue, thanks again

@jpt note that that code doesn't pull in a font, but you can do so with an import of RFont.

there’s also MarginPen in fontPens, but it only works for vertical or horizontal lines — see this example

Ah, that's likely easier, @jpt

if you draw it first into a transformPen with the correct angle, then it also works of arbitrary lines!!

and done:
from fontPens.marginPen import MarginPen
from fontTools.pens.transformPen import TransformPen
from fontTools.misc.transform import Transform
import math

def intersectGlyphWithLine(glyph, line):
    # expand the line into seperate variables
    (startx, start), (endx, endy) = line
    # calculate the diff
    yDiff = endy - starty
    xDiff = endx - startx
    # use the atan2 to get the angle of the line
    angle = math.atan2(yDiff, xDiff)
    # create a marginPen, starting from the starty
    pen = MarginPen(g.font, starty, isHorizontal=True)
    # create an empty transform matrix
    matrix = Transform()
    # set the starting point tot the origin
    matrix = matrix.translate(startx, starty)
    # rotate the matrix around the origin
    matrix = matrix.rotate(-angle)
    # translate back
    matrix = matrix.translate(-startx, -starty)
    # draw in a transform pen with the margin pen
    glyph.draw(TransformPen(pen, matrix))
    # get the inverse matrix
    inverseMatrix = matrix.inverse()
    # create an empty list of possible intersections
    intersections = []
    # calculate the min max of the x's
    minx = min((startx, endx))
    maxx = max((startx, endx))
    # get all margin x values
    for x in pen.getAll():
        # convert the straight line back to with an inverse matrix
        x, y = inverseMatrix.transformPoint((x, starty))
        # if the point is inbetween the min, max its a point on the line
        if minx < x < maxx:
            # add it to the intersections
            intersections.append((x, y))
    return intersections

g = CurrentGlyph()
startx, starty = 94, 356
endx, endy = 60, 142

results = intersectGlyphWithLine(g, ((startx, starty), (endx, endy)))

print(results)

Perhaps we should add this to fontTools?

wow, I can't overstate my thanks for this @gferreira @typemytype @benkiel - it solves the problem, but it's also so generous and  educational. I can have trouble locating the right library for this or that, I appreciate the demonstration of interoperability between them!

authors: benkiel gferreira jpt typemytype

repo: robotools/fontParts


text:
Add trevorhauter/gitportal.nvim

Repo URL:
https://github.com/trevorhauter/gitportal.nvim
Checklist:

[x] The plugin is specifically built for Neovim, or if it's a colorscheme, it supports treesitter syntax.
[x] The lines end with a .. This is to conform to awesome-list linting and requirements.
[x] The title of the pull request is Add/Update/Remove `username/repo`  (notice the backticks around `username/repo`) when adding a new plugin.
[x] The description doesn't mention that it's a Neovim plugin, it's obvious from the rest of the document. No mentions of the word plugin unless it's related to something else. No .. for Neovim.
[x] The description doesn't contain emojis.
[x] Neovim is spelled as Neovim (not nvim, NeoVim or neovim), Vim is spelled as Vim (capitalized), Lua is spelled as Lua (capitalized), Tree-sitter is spelled as Tree-sitter.
[x] Acronyms should be fully capitalized, for example LSP, TS, YAML, etc.

Thanks for the PR!

authors: trevorhauter tversteeg

repo: rockerBOO/awesome-neovim


text:
Dispute text for GMC operations is not totally clear

There are 3 bullets like this

Anyone MAY file an RPIP disputing a grant, bounty, or retrospective award within two weeks of the announcement of recipients. Such an RPIP SHALL be subject to a snapshot vote.
If a majority of the GMC agrees that a grant recipient is failing to provide the specified services to the protocol in a timely manner (as documented in the original application and in subsequent monthly updates), the GMC SHALL publicly announce such a decision and cease any future payments. This decision MAY be disputed by anyone through the creation of an RPIP within two weeks of the GMC’s announcement. The RPIP SHALL be subject to a snapshot vote.
Any group or individual MAY submit a publicly-available document to the GMC claiming successful completion of the bounty. The GMC SHALL discuss all such applications. If a majority of the GMC agrees then the GMC SHALL announce the award of the bounty. Anyone MAY dispute the awarding of the bounty through the creation of an RPIP within two weeks of the GMC’s announcement. The RPIP SHALL be subject to a snapshot vote.

The term "creation an RPIP", is not as clear as it should be.
In discussion, https://discord.com/channels/405159462932971535/1143603646592987237/1143616540600717332, we thought it should be a merged Draft that was actively being pursued. This could be measured by having a Draft RPIP and an open sentiment poll.

Niche

authors: Nichebiche Valdorff

repo: rocket-pool/RPIPs


text:
Enable usage of IOStreams::Pgp with keys that don't have an email.

Description of changes
Allow usage of keys without email. Also so allow key_id to be used for delete_keys and trust methods.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Excellent work, impressive tests. :100:
Thank you for adding support for using the key_id. Had not encountered keys before with an email address. This enhancement will help anyone that runs into this scenario.

Changes are now available in gem: iostreams v1.3.0

authors: andresfcamacho reidmorrison

repo: rocketjob/iostreams


text:
Can't disable started, processing and rendered logs when using log_level debug

Environment

Ruby Version: 2.6.6
Rails Version: 6.0.3.2
Semantic Logger Version: 4.7.4
Rails Semantic Logger Version: 4.5.0
Puma: 4.3.6
Rails configuration:

config.log_level = :debug
STDOUT.sync = true
config.rails_semantic_logger.rendered = false
config.rails_semantic_logger.add_file_appender = false
config.semantic_logger.add_appender(io: STDOUT, level: config.log_level, formatter: config.rails_semantic_logger.format)

Expected Behavior
Using above configuration I should not see the ActionView rendered output, but I am.
Actual Behavior
I am still seeing the rendered logs being output, same goes for the started and processing logs (These are disabled by default as well).
It seems when I set the log_level to :info the started, processing and rendered config settings do take effect.

I believe this is the offending line for the "Processing" log,
https://github.com/rocketjob/rails_semantic_logger/blob/47112b2c9effe7ab72f4f99d46875ed8d67d0965/lib/rails_semantic_logger/action_controller/log_subscriber.rb#L8
which has a comment:  # Log as debug to hide Processing messages in production
As far as the other "started" and "rendered" logs, you can set their log level using:
RailsSemanticLogger::Rack::Logger.started_request_log_level = :trace
RailsSemanticLogger::ActionView::LogSubscriber.rendered_log_level = :trace

@andrew-newell Thanks! In the end I chose to go with another gem because this didn't feel like the best solution for our problem.

authors: andrew-newell yourivdlans


text:
Adding dashboard data route on backend

Describe feature

Add a protected route on the backend for fetching and updating data for user dashboard like Profile image, social links,, badges, bio/description, and others.
Add a new collection in db for uploading these details.

Additional context
@rockingrohit9639  @kanak22, please assign it to me, I'd like to work on it :)

You can start working on it


text:
use of env

see https://github.com/slackapi/bolt-js/blob/main/examples/getting-started-typescript/src/utils/env.ts

ups - solved in branch 7

ups - solved in branch 7

repo: roebi/slack-to-ticket


text:
[BUG] Activities: baseline starts/finishes don't match values from SmartPM UI

Current Behavior

I am attempting to recreate this figure:

But for baseline starts and finishes, the values are way off.
Expected behavior

For this specific project, I am plotting 967 starts/finishes, but the SmartPM UI is only showing 464. So my thought is that we are not filtering activities that we probably should.
Steps To Reproduce
Steps to reproduce the behavior:

Run python snippets/explore_activities.py and view the activity_distribution.csv file in the references directory.
Find the same project on SmartPM and find this figure
Export the data
Compare Baseline Starts/Finishes

Additional context

Might be worthwhile talking to SmartPM users to see why or why not certain activities would not be included.

The Planned Start/Finishes are also wrong, but only for the month that the data date falls within

repo: rogers-obrien-rad/smartpm-python-sdk


text:
Added a C++ code in the C++ folder [Linear Search in C++] ( Issue #4)

Written the code for Linear Search in C++ programming language.

Resolved the issue. Please merge

The PR got excluded from hacktoberfest pls merge and add the label after 1st oct if possible

I want to work on this. Please assign me this.


text:
How to pass redoc options

Redoc has a number of configurable options documented here. How do you pass these to the Redocusaurus plugin?
I saw one issue that suggested to add this to the theme object but this does not work. For example:
    // Redocusaurus config
    [
      'redocusaurus',
      {
        // Plugin Options for loading OpenAPI files
        specs: [
          {
            spec: 'openapi/openapi.yaml',
            route: '/api/',
            config: {
              disableSearch: true
            }
          },
        ],
        // Theme Options for modifying how redoc renders them
        theme: {
          // Change with your site colors
          primaryColor: '#1890ff',
          redocOptions: {
            disableSearch: true,
            hideDownloadButton: true
          }
        }
      },
    ],

You can pass it as options - https://redocusaurus.vercel.app/docs/getting-started/theme-options

authors: benfoster rohit-gohri

repo: rohit-gohri/redocusaurus


text:
[TASK] Release 1.13.0

Description
Release version 1.13.0 and submit the following modules for deployment:

Events BB
API Doc

Acceptance Criteria
Version 1.13.0 tagged in GitHub and the above modules submitted for deployment.

Completed and submitted for deployment.

repo: rokwire/rokwire-building-blocks-api


text:
y211ga: Installed FW 12 and Hack 0.2.6, motion detection not working

After FW 12.0.37.0_202211241030 installing by official app and 0.2.6 hack reinstalled the camera does not really allow any motion detection anymore (MQTT in HA). Even more interesting, in camera settings the switch for motion detection always switches back to off after I refresh the page.

Trying the same over REST link http://x.x.x.x:8080/cgi-bin/camera_settings.sh?motion_detection=yes brings back this:
{
"error":"false"
}

This happens on two cams, not just one, so I think that a problem on flashing is not our problem here...

Check this commit:
https://github.com/roleoroleo/yi-hack-Allwinner-v2/commit/b40b880afa217446582eeaa6664541f661ccb59c

Ooops, I thought this one was in 0.2.6 already. OK, then this is fine as it's already fixed upstream.
Regarding the motion detection failing. After I switched on the cam on Addin side and it was active on both sides (cam and ha) it did not work... Now a few hours later it indeed sends images again. I think it takes a while to start working maybe?
Regardless, I think it's working as expected now.


text:
Typo in EncodedPayload->decreaseSize

https://github.com/rollbar/rollbar-php/blob/c2f8be87983ecdd3c46ceb3c459de02376af4707/src/Payload/EncodedPayload.php#L26
$this->size =- $amount

@ramapitecus thanks for bringing this to our attention (as well as #427 and #428).
@ArturMoczulski can you take a look when you get a chance?

I'm not sure I understand what the problem is here

I'm sorry I wasn't clear. The method is called decreaseSize so I assume that if $this->size is 10, and you call $obj->decreaseSize(2) you'ld want $this->size === 8 but there is a typo there, the =- is flipped. And $this->size === -2 after that call.

Fixed in master. Will be included in the next release.

Released in v1.7.3

authors: ArturMoczulski Ramapitecus jessewgibbs

repo: rollbar/rollbar-php


text:
Incorrect typescript type on fallbackUI prop on ErrorBoundary

The fallbackUI prop of ErrorBoundary has incorrect type in index.d.ts:
fallbackUI?: ReactNode;

But the docs says it should be a react component. If I pass a react component:
const FatalError = () => {
    return 'Error';
}

<ErrorBoundary fallbackUI={FatalError}>
   ...
</ErrorBoundary>

typescript will complain with
No overload matches this call.
  Overload 1 of 2, '(props: ErrorBoundaryProps | Readonly<ErrorBoundaryProps>): ErrorBoundary', gave the following error.
    Type 'FC<{}>' is not assignable to type 'ReactNode'.
  Overload 2 of 2, '(props: ErrorBoundaryProps, context: any): ErrorBoundary', gave the following error.
    Type 'FC<{}>' is not assignable to type 'ReactNode'.

The doc is passing the component correctly. If you try to satisfy the typescript, you'll get this error:
Unhandled Runtime Error
Error: Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: object.

Check the render method of `ErrorBoundary`.

What I did was hard cast the type on my side:
      <ErrorBoundary
        errorMessage="Error in React render"
        fallbackUI={Error as unknown as React.ReactNode} // Prop is wrongly typed
        extra={(_error, _info) => ({
          // Extra information that need to be sent to rollbar
        })}
      >
        {children}
      </ErrorBoundary>

authors: jfbaraky rnovacek

repo: rollbar/rollbar-react


text:
TestAccTeamDeleteOnAPIBeforeApply no longer passes

The code now contained in TestAccTeamDeleteOnAPIBeforeApply used to pass reliably.  Now, however, it does not pass.  Why?

Disabling this test caused a decrease in coverage: https://coveralls.io/builds/35531461
The original purpose of this test was indeed to cover handleErrNotFound().  And it used to work.  Again bringing us to the puzzling question: why does it no longer work?

During testing I have uncovered similar bugs when reading a deleted project or a deleted project access token.  Terraform should recognize that the resource has been deleted from the server and re-create it.  Instead, Terraform fails.
Maybe, before recent changes, Rollbar API allowed "deleted" teams to be read if requested by ID, even tho the "deleted" teams were not included in the list of teams?

repo: rollbar/terraform-provider-rollbar


text:
ICS consumer chain generation

TODO

[x] Add / remove ICS as expected with tags
[x] Add new 'staking' option. This feature is on by default but hidden

If ICS is used, then staking is disabled, removes all references for staking. \
Also remove Distr, Mint, etc.

[x]  Integrate Interchaintest w/ simple ICS test ( https://github.com/strangelove-ventures/interchaintest/pull/1088 )
[x] Add test_ics_node.sh instead of test_node.sh w/ Stide's provider hack
[x] CI: Run test_ics_node.sh for ics chain (matrix?)
[x] Speed up CI
[ ] Unit Test (ref: stride, neutron)
[ ] rename to ics_basic_test.go - see if we can abstract in setup.go so we can reuse standard test instead of new ones
[ ] Update to ICTest v8.3.0 + IBC  validation (from upstream ICT)
[ ] Local Interchain proper generation (remove default)
[ ] In UI, if ICS selected, deselect POA

Test Basic
make install && rm -rf testics1/
spawn new testics1 --disable=poa,tf,globalfee,packetforward,ibc-ratelimit,cw,wasm-lc,ignite-cli

spawn new chain1 --disable=ics
spawn new chain2

[ ] merge different ChainSepc array setups into 1. This way it can be used in all the test. Then just have the provider setup automatically. We just switch between Ethos, CosmosHub, and Saga (only allow 1 for an ICS chain, Hub default)
[ ] Local-Interchain have ICS be renamed to the normal file start testnet (For JSON generation, maybe have a struct instead of the raw JSON files. (we only bech32 convert wasm1 & wasmd info, so other networks like cosmoshub, neutron, ethos, are safe to support directly in the file)
[ ] Local-IC delete encoding-options which are not used (probably part of the above JSON builder)

TODO: push up ICS 4.1.0 with heighliner to confirm make template-ics and make template-staking's make ictest-basic function as expected

repo: rollchains/spawn


text:
updated README.md with releases

Overview

Checklist

[ ] New and updated code has appropriate documentation
[ ] New and updated code has new and/or updated testing
[ ] Required CI checks are passing
[ ] Visual proof for any user facing features like CLI or documentation updates
[ ] Linked issues closed with keywords

We are not compatible with mocha-4 / arabica 10 until we do a new release with #1166

Markdown lint still breaks as we don't have a rc13 release yet

authors: gupadhyaya nashqueue

repo: rollkit/rollkit


text:
More installer changes

A handful of changes to support installing Romana with different CIDRs.

Adds a docker_cidr variable to specify the IP and subnet that docker0 interface will bind to.
Makes sure the docker configs are in place before it's installed, because it gets started automatically. (Applying config after means it needs a restart)
Make sure we calculate the host bits based on the romana_cidr (16 - subnet prefix length) and put that in the config.
Sort the hosts (for AWS) so the inventory is consistent on multiple runs of the installer. They're discovered dynamically, so the values would be in an arbitrary order. Sorting by private IP seemed reasonable.

A command-line that uses allthethings is like this:
./romana-setup -n newcidrs -s kubernetes install -e romana_cidr=172.16.0.0/12 -e host_cidr=10.0.0.0/24 -e docker_cidr=192.168.255.1/24
Special note for AWS: The CIDR prefix needs to be at least 16. It really doesn't like having a 10/8.

Is the docker_cidr even used? If I recall correctly, our docker0 interface doesn't even carry an address? Could be wrong, I don't currently have a cluster to look at.

It's not used in a useful way, but it is there by default after installation. Most of the time, nobody cares because 172.16/12 is an uncommon CIDR to use.
But when we want to use it, this variable helps us put docker in a different spot.

As long as this is documented in that way somewhere...

Added documentation (in PR #100) so that we can get this closed.

authors: cgilmour jbrendel

repo: romana/romana


text:
Initiating roles and permissions

Hey,
on L5 where would you put this initiating roles and permissions file?
Do you create some database/rbac/rbac_init.php file for it?
I understand that later for new users I would integrate this to users management but for initial start do you create them in some init file?

Hello.
Well, sorry, but I don't understand you.
When you are starting, create you first roles and permissions through database seeds and attach permissions for example to a administrator role.
Then create administration panel, where you can attach (or detach of course) roles and permissions to a new users.

Ok, forgot about db seeds. Thanks for hint!

authors: janareit romanbican

repo: romanbican/roles


text:
feat: add react/react-jsx-no-duplicate-props

This pull request implements the react/jsx-no-duplicate-props lint rule, disallowing duplicate props on JSX elements.
References #341
Supersedes #351
Coauthored by @zackargyle

Looks great, thank you!

authors: bitpshr sebmck

repo: romejs/rome


text:
0606的版本，导航树里的图标不能显示

网络控制台里显示以下资源404
http://xxx:9091/transmission/web/tr-web-control/style/icons/warning.png
服务器的对应路径下没有该文件
旧版里的资源地址是
http://xxx:9091/transmission/web/tr-web-control/script/easyui/themes/icons/warning.png
应该是icons文件件没一起提交到这里
https://github.com/balonik/transmission-web-control/tree/master/src/tr-web-control/style/icons

@Cye3s 非常感谢，确实是我没有加icons的文件夹，现在应该好了。

新的transmission-control-full.tar.gz里两个 html 是0字节

repo: ronggang/transmission-web-control


text:
How do I change the default path of posh-gvm? (https://github.com/flofreud/posh-gvm/issues/16)

Copy of https://github.com/flofreud/posh-gvm/issues/16
I found that posh-gvm default set its path as C:\Users\user.posh_gvm.
However, in my case, the space of my C: is not very large. So, can I set the default path of posh-gvm to other path ? such as D:\posh_gvm (in my case).
Thanks a lot.

Copy of https://github.com/flofreud/posh-gvm/issues/16#issuecomment-178069660
You need to declare $Global:PGVM_DIR before loading posh-gvm.

repo: ronnypolley/posh-sdkman


text:
ERROR  syntax error, unexpected ')', expecting variable (T_VARIABLE)

ERROR  syntax error, unexpected ')', expecting variable (T_VARIABLE) in vendor/ronvanderheijden/openid-connect/src/IdTokenResponse.php on line 39.
There is a comma symbol beyond the last parameter in constructor .
public function __construct(
IdentityRepositoryInterface $identityRepository,
ClaimExtractor $claimExtractor,
Configuration $config,
CurrentRequestServiceInterface $currentRequestService = null,
$encryptionKey = null , <============================== comma
)

You are using an outdated PHP version. You should upgrade to a newer version (preferable 8.3).

this repo should not tell composer it supports PHP 7.4 if it uses a syntax introduced in PHP 8.0 though.

This is true, but still, PHP 7.4 is not actively supported for almost 3 years.

authors: goldgeer ronvanderheijden stof

repo: ronvanderheijden/openid-connect


text:
🛑 SSH 🇬🇧 United Kingdom UKO 2 is down

In b20eb11, SSH 🇬🇧 United Kingdom UKO 2 (http://uks-2.opensvr.net:8080/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SSH 🇬🇧 United Kingdom UKO 2 is back up in 44799f8.

repo: roosterkid/opentunnel-status-server


text:
🛑 TROJAN 🇭🇰 Hong Kong HKE 1 is down

In 6b8afe4, TROJAN 🇭🇰 Hong Kong HKE 1 (https://hkt-1.opensvr.net/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: TROJAN 🇭🇰 Hong Kong HKE 1 is back up in cc82206.


text:
🛑 XRAY 🇨🇦 Canada CAO 1 is down

In 43f2495, XRAY 🇨🇦 Canada CAO 1 (https://cax-1.openv2ray.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: XRAY 🇨🇦 Canada CAO 1 is back up in 51bd40e.


text:
🛑 XRAY 🇩🇪 Germany DEH 1 is down

In f37472b, XRAY 🇩🇪 Germany DEH 1 (https://dex-1.openv2ray.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: XRAY 🇩🇪 Germany DEH 1 is back up in 54fda12.


text:
🛑 TROJAN 🇺🇸 United States USF 1 is down

In 80afc15, TROJAN 🇺🇸 United States USF 1 (https://ust-1.opensvr.net/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: TROJAN 🇺🇸 United States USF 1 is back up in 73b91ba.


text:
🛑 V2RAY 🇭🇰 Hong Kong HKM 1 is down

In 569d7c1, V2RAY 🇭🇰 Hong Kong HKM 1 (https://hkv-1.openv2ray.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: V2RAY 🇭🇰 Hong Kong HKM 1 is back up in 10730c9.


text:
🛑 TROJAN 🇩🇪 Germany DEH 1 is down

In 864ca04, TROJAN 🇩🇪 Germany DEH 1 (https://det-1.opensvr.net/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: TROJAN 🇩🇪 Germany DEH 1 is back up in 6517291.


text:
🛑 TROJAN 🇸🇬 Singapore SGO 1 is down

In f8e9d41, TROJAN 🇸🇬 Singapore SGO 1 (https://sgt-2.opensvr.net/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: TROJAN 🇸🇬 Singapore SGO 1 is back up in 1bb81c6.


text:
🛑 V2RAY 🇸🇬 Singapore SGO 3 is down

In c235793, V2RAY 🇸🇬 Singapore SGO 3 (https://sgv-4.openv2ray.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: V2RAY 🇸🇬 Singapore SGO 3 is back up in 1f36b86.


text:
🛑 V2RAY 🇮🇩 Indonesia IDG 1 is down

In 67a7f38, V2RAY 🇮🇩 Indonesia IDG 1 (https://idv-2.openv2ray.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: V2RAY 🇮🇩 Indonesia IDG 1 is back up in a6b67d0.


text:
🛑 XRAY 🇸🇬 Singapore SGO 2 is down

In ad675d2, XRAY 🇸🇬 Singapore SGO 2 (https://sgx-3.openv2ray.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: XRAY 🇸🇬 Singapore SGO 2 is back up in 414bc49.


text:
🛑 SSH 🇺🇸 United States USO 1 is down

In b4f31a1, SSH 🇺🇸 United States USO 1 (http://uss-4.optnl.com:8080/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SSH 🇺🇸 United States USO 1 is back up in cdc7eec.


text:
🛑 V2RAY 🇳🇱 Netherlands NLI 1 is down

In 0e8a8c5, V2RAY 🇳🇱 Netherlands NLI 1 (https://nlv-6.openv2ray.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: V2RAY 🇳🇱 Netherlands NLI 1 is back up in 260727b.


text:
🛑 V2RAY 🇱🇻 Latvia LVH 1 is down

In 57080e8, V2RAY 🇱🇻 Latvia LVH 1 (https://lvv-1.openv2ray.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: V2RAY 🇱🇻 Latvia LVH 1 is back up in 850ec18.


text:
🛑 XRAY 🇩🇪 Germany DEH 1 is down

In 07a1d70, XRAY 🇩🇪 Germany DEH 1 (https://dex-1.openv2ray.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: XRAY 🇩🇪 Germany DEH 1 is back up in 6afcc58.


text:
🛑 V2RAY 🇸🇬 Singapore SGV 1 is down

In a23a15b, V2RAY 🇸🇬 Singapore SGV 1 (https://sgv-5.openv2ray.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: V2RAY 🇸🇬 Singapore SGV 1 is back up in f8a2fc8.


text:
🛑 SSH 🇮🇩 Indonesia IDA 2 is down

In 14b4958, SSH 🇮🇩 Indonesia IDA 2 (http://ids-4.opensvr.net:8080/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SSH 🇮🇩 Indonesia IDA 2 is back up in 5437b2c.


text:
🛑 XRAY 🇸🇬 Singapore SGD 1 is down

In 6390e82, XRAY 🇸🇬 Singapore SGD 1 (https://sgx-3.openv2ray.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: XRAY 🇸🇬 Singapore SGD 1 is back up in ac404a5.


text:
🛑 TROJAN 🇸🇬 Singapore SGV 1 is down

In 5193ec3, TROJAN 🇸🇬 Singapore SGV 1 (https://sgt-1.opensvr.net/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: TROJAN 🇸🇬 Singapore SGV 1 is back up in 0be4514.


text:
🛑 V2RAY 🇳🇱 Netherlands NLB 1 is down

In bd22c25, V2RAY 🇳🇱 Netherlands NLB 1 (https://nlv-1.openv2ray.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: V2RAY 🇳🇱 Netherlands NLB 1 is back up in 3e8a069.


text:
🛑 TROJAN 🇳🇱 Netherlands NLB 1 is down

In ca3dd68, TROJAN 🇳🇱 Netherlands NLB 1 (https://nlt-1.opensvr.net/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: TROJAN 🇳🇱 Netherlands NLB 1 is back up in fbcf789.


text:
Hunain/issue 12/settings

Related Task # https://github.com/roots-id/roots-react-native/issues/12
ChangeLog:

Added settings screen
Added developer screen link with dummy on settings
Added save screen with mock data
Implemented Picker Component to look better on IOS , previously it was not working with current styling

IOS
https://user-images.githubusercontent.com/19255438/197067056-0619cee2-609f-42c2-bc42-c0e9881f72a7.mov
Android
https://user-images.githubusercontent.com/19255438/197067392-d1cdbffe-18a1-47d1-b3e4-c4111144818c.mov

I had some trouble with this one @HunnySajid.
Web loaded fine. But android didn't load at all and iOS i wasn't able to click around.
I'll try to look into it a bit more tomorrow.

I had some trouble with this one @HunnySajid. Web loaded fine. But android didn't load at all and iOS i wasn't able to click around. I'll try to look into it a bit more tomorrow.

@2byrds for ios its behavior is different. It provides a swapping up/down instead of showing a dropdown.
Can you provide some details about android phone you are using so that I can look into it if it is os/mobile specific issue?

ah yes @HunnySajid I was able to swipe the picker on ios.  thx :)

I think my android emulator was in a bad state.  i started a fresh one and it worked great.

repo: roots-id/roots-react-native


text:
Feature request: Confirm Reboot/PowerOff

When I wanted to reboot my Pi, in the menu I choose 'Reboot' and it just rebooted.
Exactly what it should do of course.
What about a confirmation: Are you sure? A mistake is easily made.
Same with 'Off' probably. Did not try that.

Feel free to give this a try - sounds like a good "first issue" :-D

My first issues were #1281 and #1297 but I will give it a try this weekend. Good third issue.
I don't have a screen but the Update/Patch menu has a lot of confirmation questions. So I'll take a look at that.

[ ] merge and adapt PR

tested and is working. closing issue.

authors: adevoss frennkie rootzoll

repo: rootzoll/raspiblitz


text:
Test & Fix CLN-Rescue Export & Import

Tested the CLN-Import from an older/veryearly c-lightning node ... the test failed. To be retested.

Test worked with RC3 - closing issue.


text:
[CL] CLBOSS needs a warning

I was close to a heart attack today when I installed CLBOSS via the Blitz menu and suddenly funds were seemingly moving out of my CL node. Just CLBOSS doing its thing, but this needs a proper warning that CLBOSS is taking control over funds and will take action right after installation.

@openoms is this addressed or should I push to v1.8.1?

not yet, but will add a notice to the menu also

@openoms Can I close for v1.8.0 RC2 release?

@openoms please signal when we can close this one - or we push to v1.8.1

authors: kilrau openoms rootzoll


text:
btcpay update v1.8.2, postgres database fix

btcpay update and database creation modified to follow:
https://docs.btcpayserver.org/BTCPayServer/db-migration/
migration is not done yet automatically for old sqlite instances - will test migrating an old store first
cc @NicolasDorier
covers #3701

@openoms plz merge if ready

authors: openoms rootzoll


text:
🛑 Oshi is down

In f8e053a, Oshi (https://oshi.at) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Oshi is back up in 82eb21b after 6 minutes.

repo: roozbehzarei/filester-status


text:
Add MuJoCo by FZI

ros2_control system interface for MuJoCo. Not tested but looks great!

@mergifyio backport humble iron

@christophfroehlich
Thanks for spotting and referencing that implementation! However, I'm afraid that's a little robot dependent at the moment. As far as I'm concerned, MuJoCo needs a specific configuration .xml that specifies the robot to simulate. We could adapt/change it to provide a more generic interface between MuJoCo and ros2_control so that users can simulate arbitrary robots (manipulators). I didn't continue this idea lately, but I'm interested in supporting/implementing if that's of use for the community.

@christophfroehlich
Thanks for spotting and referencing that implementation! However, I'm afraid that's a little robot dependent at the moment. As far as I'm concerned, MuJoCo needs a specific configuration .xml that specifies the robot to simulate. We could adapt/change it to provide a more generic interface between MuJoCo and ros2_control so that users can simulate arbitrary robots (manipulators). I didn't continue this idea lately, but I'm interested in supporting/implementing if that's of use for the community.

For the scope of this PR it is fine like it is. It should just give a reference implementation for users on control.ros.org
I have a personal interest in bringing MuJoCo and ros2_control closer due to a research project I'm working on. But I haven't tried it out yet and can't comment on the limitations. @traversaro pointed me to https://github.com/google-deepmind/mujoco/issues/1432, so I think there is more work to be done to provide a seamless integration like with Gazebo (classic). Once I have the time to work on that, I'd be happy to discuss future steps to find a more general solution.

@traversaro pointed me to google-deepmind/mujoco#1432, so I think there is more work to be done to provide a seamless integration like with Gazebo (classic). Once I have the time to work on that, I'd be happy to discuss future steps to find a more general solution.

Just to complement the link, I think most of people using URDF with MuJoCo either manually or automatically change the URDF before the loading in MuJoCo, or the resulting .mjcf after the conversion,  and that is why there are not a lot of discussion like https://github.com/google-deepmind/mujoco/issues/1432 in MuJoCo issue tracker.


text:
Remove publish_rate parameter

It was removed https://github.com/ros-controls/ros2_controllers/pull/468

CI is failing, the service_msgs package was added 3 weeks ago https://github.com/ros2/rcl_interfaces/commits/rolling/service_msgs and it was released last week, maybe a package that uses this dependency is not released yet and that's why is failing?

just to clarify, are you asking me the question? :smile:

@bmagyar or @destogl can you relaunch the Github actions ?

just to clarify, because that's unrelated to my PR, are you asking me the question? smile

This was not a question, it was a clarification, but for some reason I added ?.  Let's relaunch CI

authors: ahcorde tonynajjar


text:
Fixes for 24.04 build

Related to https://github.com/ros-industrial/reach/pull/83

Fix MPI_C not found error similar to https://github.com/ros-industrial/reach/pull/82
Use tf2_eigen.hpp instead of tf2_eigen.h https://github.com/ros2/geometry2/pull/645

Closing; addressed in #35 and #39; thanks for bringing this up


text:
Not understand MoveItGroupInterface

Description
I've downloaded Universalrobots driver and followed the procedure to use moveIt!2, it actually works what showed in the README and i use "ur_manipulator" in Rviz to move my arm. But my interest is to use moveit2_tutorials to send pose and design a pick and place application with MoveItGriuoInterface.
What i have designed is:
#include <memory>

#include <rclcpp/rclcpp.hpp>
#include <moveit/move_group_interface/move_group_interface.h>

int main(int argc, char * argv[])
{
  rclcpp::init(argc, argv);
  auto const node = std::make_shared<rclcpp::Node>(
    "hello_moveit",
    rclcpp::NodeOptions().automatically_declare_parameters_from_overrides(true)
  );

  auto const logger = rclcpp::get_logger("ur_manipulator");

  // Create the MoveIt MoveGroup Interface
using moveit::planning_interface::MoveGroupInterface;
auto move_group_interface = MoveGroupInterface(node, "ur_manipulator");
printf("picvkandplace");

// Set a target Pose
auto const target_pose = []{
  geometry_msgs::msg::Pose msg;
  msg.orientation.w = 1.0;
  msg.position.x = 0.28;
  msg.position.y = -0.2;
  msg.position.z = 0.5;
  return msg;
}();
move_group_interface.setPoseTarget(target_pose);

// Create a plan to that target pose
auto const [success, plan] = [&move_group_interface]{
  moveit::planning_interface::MoveGroupInterface::Plan msg;
  auto const ok = static_cast<bool>(move_group_interface.plan(msg));
  return std::make_pair(ok, msg);
}();

// Execute the plan
if(success) {
  move_group_interface.execute(plan);
} else {
  RCLCPP_ERROR(logger, "Planing failed!");
}
  // Shutdown ROS
  rclcpp::shutdown();
  return 0;
}

i launch ros2 run hello_moveit hello_moveit as in the tutorial but i get:
[ERROR] [1664871447.339399807] [hello_moveit]: Could not find parameter robot_description_semantic and did not receive robot_description_semantic via std_msgs::msg::String subscription within 10.000000 seconds.
Error:   Could not parse the SRDF XML File. Error=XML_ERROR_EMPTY_DOCUMENT ErrorID=13 (0xd) Line number=0
         at line 715 in ./src/model.cpp
[ERROR] [1664871447.342434566] [moveit_rdf_loader.rdf_loader]: Unable to parse SRDF
[FATAL] [1664871447.342740966] [move_group_interface]: Unable to construct robot model. Please make sure all needed information is on the parameter server.
terminate called after throwing an instance of 'std::runtime_error'
  what():  Unable to construct robot model. Please make sure all needed information is on the parameter server.
[ros2run]: Aborted

I can't understand what should i look for also because in that everything is set to use moveit, robot_description_semantic included.
Hope someone could help to this endless problem!
Enrico

I have same problem. Who can solve this problem?

@enriLoniterp Did you find an answer? I am developing a similar program.
Thanks for your help!

You are likely missing the step of launching the move_group node for your robot package before running the program.
For example, you can try ros2 launch moveit_resources_panda_moveit_config demo.launch.py. If you are using a different robot there likely alredy exists a package and a launch file that does the same, otherwise you're gonna need to either 1) use MoveIt Setup Assistant to generate an appropriate moveit_config package, or 2) write the launch file by hand.
All of this is more or less covered in the MoveIt docs.

The problem is that your program (actually the MoveGroupInterface constructor) cannot find the SRDF robot description MoveGroupInterface in either of the two places it looks in: 1) in the robot_description_semantic parameter in your node's parameters list, or 2) in a published /robot_description_semantic ROS topic.
It follows that you can solve this in two ways: either 1) feed the robot_description_semantic parameter to your program node when launching it, or 2) configure the move_group node to publish its own robot_description_semantic parameter to a matching topic from which other nodes in the system can read it.
Personally I prefer the second method.
To do this, find the launch file that is creating the move_group node and set its node parameter publish_robot_description_semantic = True . I suggest you set the publish_robot_description as well.
To verify the SRDF is published correctly run
ros2 topic echo /robot_description_semantic

Which should spit out the .srdf file.

Thanks for your fast answer!. I am going to check.

Looks like the discussion is resolved. Feel free to re-open if you'd like to continue it

authors: enriLoniterp felipebapa jwson97 okvik sjahr


text:
renamed cartesian limits file

Description
Renamed cartesian_limits.yaml to avoid warning when running dual arm demo
Checklist

[ ] Required by CI: Code is auto formatted using clang-format
[ ] While waiting for someone to review your request, please consider reviewing another open pull request to support the maintainers

Thank you @henrygerardmoore !

authors: henrygerardmoore vatanaksoytezer


text:
Clean up move_group and moveit_cpp tutorials

Description

Added panda_hand_controller to the loaded controllers in launch files
switched joint_state_controller to joint_state_broadcaster
updated visual_tools text to snake case for better readability
added collision object example to moveit_cpp tutorial (I am planning on making a PR to remove the demo code from moveit2)

Checklist

[ ] Required by CI: Code is auto formatted using clang-format
[ ] While waiting for someone to review your request, please consider reviewing another open pull request to support the maintainers

Turns out I cannot run because of joint_state_broadcaster is not registered in moveit_resources.

authors: MarqRazz vatanaksoytezer


text:
geometry_experimental: 0.5.13-0 in 'jade/distribution.yaml' [bloom]

Increasing version of package(s) in repository geometry_experimental to 0.5.13-0:

upstream repository: https://github.com/ros/geometry_experimental.git
release repository: https://github.com/ros-gbp/geometry_experimental-release.git
distro file: jade/distribution.yaml
bloom version: 0.5.20
previous version for package: 0.5.12-0

geometry_experimental
* Remove LGPL from license tags
  LGPL was erroneously included in 2a38724. As there are no files with it
  in the package.
* add missing dependencies in the meta-package geometry_experimental
  This partly fixes the doc jobs in #120 <https://github.com/ros/geometry_experimental/issues/120>
* Contributors: Jochen Sprickerhof, Vincent Rabaud

tf2

No changes

tf2_bullet
* Don't export catkin includes
  They only point to the temporary include in the build directory.
* Contributors: Jochen Sprickerhof

tf2_eigen
* Added missing inline
* Added unit test
  - Testing conversion to msg forward/backward
* Added eigenTotransform function
* Contributors: Davide Tateo, boris-il-forte

tf2_geometry_msgs
* Add missing python_orocos_kdl dependency
* make example into unit test
* vector3 not affected by translation
* Contributors: Daniel Claes, chapulina

tf2_kdl
* converting python test script into unit test
* Don't export catkin includes
* Contributors: Jochen Sprickerhof, Tully Foote

tf2_msgs

No changes

tf2_py

No changes

tf2_ros
* fix documentation warnings
* Adding tests to package
* Contributors: Laurent GEORGE, Vincent Rabaud

tf2_sensor_msgs
* add missing Python runtime dependency
* fix wrong comment
* Adding tests to package
* Fixing do_transform_cloud for python
  The previous code was not used at all (it was a mistake in the __init__.py so
  the do_transform_cloud was not available to the python users).
  The python code need some little correction (e.g there is no method named
  read_cloud but it's read_points for instance, and as we are in python we can't
  use the same trick as in c++ when we got an immutable)
* Contributors: Laurent GEORGE, Vincent Rabaud

tf2_tools
* casted el to string in view_frames
* Contributors: g_gemignani

hold for coordinated release

repo: ros/rosdistro


text:
pacmod3: 1.2.0-0 in 'lunar/distribution.yaml' [bloom]

Increasing version of package(s) in repository pacmod3 to 1.2.0-0:

upstream repository: https://github.com/astuff/pacmod3.git
release repository: https://github.com/astuff/pacmod3-release.git
distro file: lunar/distribution.yaml
bloom version: 0.6.9
previous version for package: 1.1.1-0

pacmod3
* Merge pull request #41 <https://github.com/astuff/pacmod3/issues/41> from astuff/fix/vector_comp_dbc_file
  Removing unnecessary line preventing Vector CANdb++ editor from opening
* Merge pull request #39 <https://github.com/astuff/pacmod3/issues/39> from astuff/feat/add_comp_rpt
  Feature add component report for each PACMod component.
* DBC: Fixing errors. CI: Adding DBC validation to workflow.
* DBC: Typo on two lines.
* Adding encoding for CLEAR_FAULTS flag.
* Adding parsing and publishing for COMPONENT_RPT.
* DBC: Add COMPONENT_RPT and CLEAR_FAULTS flag.
* Merge pull request #38 <https://github.com/astuff/pacmod3/issues/38> from astuff/feature/add_veh_6
  Adding VEHICLE_6.
* Contributors: Daniel-Stanek, Joshua Whitley, Mike Lemm, Nate Imig

Holding for sync

authors: JWhitleyAStuff tfoote


text:
add python3-xmltodict-pip package

Signed-off-by: Masaya Kataoka ms.kataoka@gmail.com
xmltodict Packages in rosdistro is Python2 version.
https://packages.ubuntu.com/search?keywords=python-xmltodict&searchon=names&suite=groovy&section=all
We want to use it with Python3, so we want to add python3-xmltodict-pip package to rosdistro.

Sorry, I cannot understand why CI was failed.
Does anyone has idea about it?

changed to native packages.

Ubuntu : https://packages.ubuntu.com/search?keywords=python3-xmltodict
Arch : https://www.archlinux.org/packages/community/any/python-xmltodict/
Alpine：https://pkgs.alpinelinux.org/package/edge/community/x86/py3-xmltodict
Debian：https://packages.debian.org/search?keywords=python3-xmltodict


text:
Revert "mavlink: 2023.5.5-1 in 'melodic/distribution.yaml' [bloom] (#…

…37150)"
This reverts commit 18c62e19dfc6dd53258cc14c76903fc00cd6ce22.
This has failed to build since it was merged: https://build.ros.org/job/Mbin_uB64__mavlink__ubuntu_bionic_amd64__binary/ .  FYI @vooon

@clalancette i've updated patches and can confirm build for Noetic and Iron. But i'm unsure if that's good idea to release for Melodic, as i EOL and i haven't tested for Python 2.
So tomorrow i'm going to release for Noetic, Humble, Iron and Rolling. Is i'm right?

authors: clalancette vooon


text:
log_view: 0.2.4-1 in 'iron/distribution.yaml' [bloom]

Increasing version of package(s) in repository log_view to 0.2.4-1:

upstream repository: https://github.com/hatchbed/log_view.git
release repository: https://github.com/ros2-gbp/log_view-release.git
distro file: iron/distribution.yaml
bloom version: 0.12.0
previous version for package: null

log_view
* Fix build error caused by mvwprintw. (#19 <https://github.com/hatchbed/log_view/issues/19>)
* Contributors: Marc Alban

Given that this has never been released into Iron before, I'm going to consider this a new package and close this out.

authors: clalancette malban


text:
Updated rosdep rules for the libaria package

Updated rosdep rules to use the binary libaria-dev package, where available.

Fixed.


text:
Add dependency on system poco.

If there is a suitable system version of poco, prefer to use it rather
than building poco locally. For bouncy the necessary version of poco is
available from the bionic repositories.
Necessary to bloom poco_vendor without patching.

Thanks for your review @mjcarroll I realized just after when checking this package.xml against the one from ardent that some additional dependencies are needed in the case that poco upstream is not available.

@mjcarroll @dirk-thomas ready for a second round of review with the poco build dependencies removed.

Apologies I'm not aware of the background for this PR - on xenial, libpoco-dev does not pull in PCRE or zlib.
As someone who builds ROS2 from source in CI on xenial and bionic, and depends on catkin_pkg/rosdep to resolve dependencies, I wonder: is there any harm in keeping those build_depends in poco_vendor, given that xenial is nominally a supported platform?

authors: nuclearsandwich paulbovbel