cranelift: Consider functions with TLS values as non leaf

👋 Hey,
@bjorn3 reported an issue with TLS values in the RISC-V backend, when testing it with cg_clif. This presented as a segfault running the cg_clif testsuite.
Digging into it, it looks like we would call the elf_tls_getaddr function, which would clobber the ra register and before returning from the current function we would not restore the correct ra value from the stack. This would cause the function to recurse back into the middle of itself and cause a segfault.
This function met all criteria for us to avoid emitting a prologue and epilogue sequence, that would correctly restore the ra value. The check that was failing here is the is_leaf check. It assumes that a function will only call other functions if it contains any signatures itself.
This PR adds an additional check for TLS values, and assumes that if such a value exists we will be calling a function to retrieve it's address. This is not necessarily true, but it is a good conservative estimate.
More importantly I don't think this fully addresses the issue. I think we can still have a similar issue if we decide to use a libcall instead of native instruction during lowering. I'm not entirely sure how to fix that.

Would it be possible to backport this to cranelift 0.101? That would allow me to ship riscv64 support in cg_clif one month earlier and this shouldn't affect Wasmtime.

Certainly yeah, would you be up for sending a PR to the release-14.0.0 branch?

Done: https://github.com/bytecodealliance/wasmtime/pull/7195


No published analyzer available for language version 2.14.0

Looks like we need a new release for 2.14 dev

@scheglov any idea what the timeline would be on this? I just want to know so I can decide whether to disable the test on our end temporarily or if I should just wait for a new release and have a bit less churn in our repo (to be clear this doesn't need to influence the decision, I just would like a rough timeline to help inform us of the best path forward).

I started a change to analyzer APIs that I'd like to finish before publishing. It will take me several days to finish, and verify that it works well for all internal clients. So, it seems that we will publish somewhere next week.

Ok thanks, I will disable the test on our end to get things green for now then thanks!


culled unnecessary info, moved all the getting started examples to the top

Hey @mreinstein, you removed a bunch of things that other people do find necessary, like the fact that the docs are for the next version of the library. This is going to waste a lot of time for people who try to figure out why something doesn't work. I value your opinion, but it would have been nice to leave this open for some comments and a healthy discussion by other maintainers.

Feel free to revert.

@mreinstein I don't want to revert this, I just want that paragraph back. The other changes look good. Do you agree?

on a related note, I'm moving the repo i created back under my account (alexa-verifier.) I think you should remove me from the alexa-js org because I'm not interested in participating in these interactions.
Thanks for your time, and good luck.

Alright. You're being unnecessarily confrontational. Done.

yes I'm "unnecessarily confrontational" in that I don't want to re-write projects that are essentially done.

Thanks for contributing @mreinstein, good luck to you.


Handle rest of haystack if it is not a multiple of vector size.

Fixed by https://github.com/jeschkies/go-memmem/commit/6643048faccbcc5d5d56ee493947d937523ea112


Fix tf.variable_scope unique name after entering root scope

This PR fixes a bug in creating unique scope name after entering and closing the root scope.
The following snippet exploits the bug
import tensorflow as tf

with tf.variable_scope(None, "Block") as scope:
    print("SCOPE:" + scope.name)
with tf.variable_scope('') as scope:
    print("SCOPE:" + scope.name)
with tf.variable_scope(None, "Block") as scope:
    print("SCOPE:" + scope.name)

Executing it produces
    SCOPE:Block
    SCOPE:
    SCOPE:Block

While the expected behavior should be
    SCOPE:Block
    SCOPE:
    SCOPE:Block_1

As it turns out, closing the root scope ('') results in resetting the dict self.variable_scopes_count to 0,
since not '' evaluates to True, which is unlikely the required behavior.

@lukaszkaiser I am honestly not sure what the "correct" behavior here is. I have a strong feeling that the current behavior is what we have, backwards compatibility will prevent us from changing this.

@martinwicke : this is just another "None vs empty string" python bug. It's a small bug and I believe this correction could be good and not cause any incompatibility problems. But let's wait for the tests -- if they're passing, then we should accept it. If a lot of tests are failing, then I'm afraid we may need to keep the state as is, but let's see.

@lukaszkaiser Passing the tests doesn't quite make me comfortable -- can you pull this CL in and merge it internally so we get more coverage of actual use?

On it, will report back here.

@lukaszkaiser any update?

This looks fine! I'll need to update some internal tests. I'll try to do it next week, but due to ICLR it may only happen the week after. Martin: should we wait for that before merging this PR?

Yes, let's wait until then, otherwise it'll block merges.

The internal part is now updated. Martin: should we merge? What's the process?


keras and tensorflow version for installation

Hi Bonlime,
Thanks for sharing the code, would you like to clarify which version of tensorflow and keras you are supporting?  It seems to me that the original deeplab V3 code only works for tensorflow=1.5.

Yes, I want to know this too.

I'm using
Keras==2.1.5
tensorflow-gpu==1.6.0
with CUDA 9


Command suggestion not work properly: No candidates found

Version confirmation

[X] Confirm

Following prerequisites

[X] Confirm

Neovim version
NVIM v0.8.3 Build type: Release LuaJIT 2.1.0-beta3 Compiled by builduser  Features: +acl +iconv +tui
Operating system/version
Arch linux 6.1.11
Terminal name/version
kitty 0.27.1
$TERM environment variable
No response
Branch info
main (Default/Latest)
Fetch Preferences
SSH (use_ssh = true)
How to reproduce the issue

Open nvim.
Tab : to input commands.
Try to input something.

Expected behavior
It should work fine.
Actual behavior
No matter what input or not, the suggestion panel just displays No candidates found, and tab completion also doesn't work. If I tried to tab, my input became a single 0.
Additional information
No command input:

Input command like help:

Before using tab to complete commands:

After:

checkhealth shows nothing wrong at all

Can't repo, but you can try :UpdataRemotePlugins

Tried, but still did not work.

Tried, but still did not work.

I have same error

check :messages
nvim-data/site/lazy/wilder.nvim/lua/wilder/internal.lua:4: loop or previous error loading module 'fzy-lua-native'

Got it, thanks. My error messages have a little different:
..share/nvim/site/lazy/wilder.nvim/lua/wilder/internal.lua:4: in function <...share/nvim/site/lazy/wilder.nvim/lua/wilder/internal.lua:3> function: builtin#18 ...share/n
vim/site/lazy/wilder.nvim/lua/wilder/internal.lua:4: attempt to index a boolean value

It seems to be an upstream error but found no similar issue in wilder.nvim, and that plugin looks like stop developing now.

Sorry, I can't reproduce it on my machine. I don't know any better solution than rm -fr ~/.local/share/nvim/site/lazy/wilder.nvim and then nvim.

try
runtime! vim/rtp.vim

UpdateRemotePlugins

Thanks for all your advice!
I decide to take a while to find an alternative to wilder.nvim because this seems just individual circumstances.

I ran intot this issue b4. Maybe it has something to do with using fzf-native-lua. I notice that when I remove the pipeline setup, the error went away.

@Tgist1024 I got similar warning, I remove all plugin(rm -rf ~/.local/share/nvim/*) and reload again.
The problem disappears. I think you can try it.

I also had the same problem, and when I started nvim, I also reported that I could not find the configuration file of the relevant plug-in

@Tgist1024 I got similar warning, I remove all plugin(rm -rf ~/.local/share/nvim/*) and reload again. The problem disappears. I think you can try it.

Actually, I have tried this many times before.

I ran intot this issue b4. Maybe it has something to do with using fzf-native-lua. I notice that when I remove the pipeline setup, the error went away.

It just works! Thank you!

@nkta3m @HATTER-LONG @Tgist1024 @Yan-weihao This should be an upstream issue. Current workaround is to change return require('.init') in ~/.local/share/nvim/site/lazy/fzy-lua-native/lua/fzy-lua-native.lua to return require('init').
Looks like this is an issue related to native rtp. Maybe someone will be interested in looking into this weird behavior?

This should be an upstream issue. Current workaround is to change return require('.init') in ~/.local/share/nvim/site/lazy/fzy-lua-native/lua/fzy-lua-native.lua to return require('init') (remove that period .).
Looks like this is an issue related to native rtp. Maybe someone will be interested in looking into this weird behavior?
cc @nkta3m @HATTER-LONG @Tgist1024 @Yan-weihao @aarnphm

I am surprised that there is nothing in this file of mine

This should be an upstream issue. Current workaround is to change return require('.init') in ~/.local/share/nvim/site/lazy/fzy-lua-native/lua/fzy-lua-native.lua to return require('init') (remove that period .).这应该是一个上游问题。当前的解决方法是将 ~/.local/share/nvim/site/lazy/fzy-lua-native/lua/fzy-lua-native.lua 中的 return require('.init') 更改为 return require('init') （删除句点 return require('.init')）。
Looks like this is an issue related to native rtp. Maybe someone will be interested in looking into this weird behavior?看起来这是与原生 rtp 相关的问题。也许有人会对调查这种奇怪的行为感兴趣？
cc @nkta3m @HATTER-LONG @Tgist1024 @Yan-weihao @aarnphm

I re-installed this plug-in, and now it has worked, thanks for your reminding,

I got the same issue after update lazy.nvim.

Looks like this is an issue related to native rtp. Maybe someone will be interested in looking into this weird behavior?

I think the reason is that lazy clear the rtp for faster startup hence causing the issue.

I have create a tmp fork and submit a PR to fzy-lua-native.
Others can use this tmp fork for now if u don't want to edit the file.
https://github.com/CharlesChiuGit/fzy-lua-native

this version of nvim might fiz this issue.


Add a 96+ VMs job

This is job to test 100+ nodes with Crowbar in virtualized test environment.
Currently reserved to be run on uv300x.arch.suse.de machine.

I am a bit hesitant to increase  the memory, since the this machine has only 256 GB of ram.
Also only 64 vCPUs.

looks OK, but would like to test-push it to ci.suse.de

Removed the inline comments after the parameters since they would appear in string parameters in jenkins.
Did the test-push with @bmwiedemann . Resolved the hdd space problem.
The job looks more or less fine now.
Perhaps ready to merge?


Update JenkinsFile

JenkinsFile updated to use predefined configurations.

This was the only failure:
08:15:23 [UBLOX_EVK_ODIN_W2 IAR ATMEL thd] Failed in branch UBLOX_EVK_ODIN_W2 IAR ATMEL thd

Should we merge in and resolve that as a separate commit?


HardatConfig instead of HardatUserConfig

Hi,
we've notice that in the exported module you've used the wrong type. You have to set HardhatUserConfig and not HardhatConfig in order to make the parameter enabled in hardhat.config.js, otherwhise we have a static error (using TS).
You have to set like:
declare module "hardhat/types/config" {
interface HardhatUserConfig {
disableEthernal?: boolean;
}
}
and not:
declare module "hardhat/types/config" {
interface HardhatConfig {
disableEthernal?: boolean;
}
}

Mmmh that actually didn't work for me when using HardhatUserConfig, only HardhatConfig. I thought you said it was working in the other thread though?
I'll take a look to see how to move it on UserConfig

It was working still using my custom interface declared in hardhat.config.js (no error like really disable all the ethernal features in that case and it's fine). But trying to set the correct interface for hardhat (HardatUserConfig) we have static problem adding disableEthernal.
Could you check how the guys have done for gasReporter ?
https://github.com/cgewecke/hardhat-gas-reporter/blob/97258f99e9a7d6bfa1852363e7ba92beb20f64f3/src/type-extensions.ts

And you are adding the flag in the object exported by hardhat.config? Can you put your config file here, please?

import '@nomiclabs/hardhat-waffle';
import '@nomiclabs/hardhat-ethers';
import '@nomiclabs/hardhat-etherscan';
import 'solidity-coverage';
import 'dotenv/config';
import { extendEnvironment, HardhatUserConfig } from 'hardhat/config';
import './tasks';
import 'hardhat-ethernal';
import 'hardhat-gas-reporter';
extendEnvironment((hre) => {
hre.ethernalSync = true;
hre.ethernalWorkspace = 'Sample';
hre.ethernalTrace = false;
hre.ethernalResetOnStart = 'Sample';
});
const config: HardhatUserConfig = {
solidity: {
version: '0.8.4',
settings: {
optimizer: {
enabled: true,
runs: 800,
},
},
},
networks: {
hardhat: {
chainId: 31337,
mining: {
auto: true,
//interval: [3000, 6000]
},
},
ropsten: {
url: https://eth-ropsten.alchemyapi.io/v2/${process.env.ALCHEMY_KEY},
accounts: [${process.env.ACCOUNT_PRIVATE_KEY}],
},
rinkeby: {
url: https://eth-rinkeby.alchemyapi.io/v2/${process.env.ALCHEMY_KEY},
accounts: [${process.env.ACCOUNT_PRIVATE_KEY}],
},
},
gasReporter: {
currency: process.env.CURRENCY,
coinmarketcap: process.env.COINMARKETCAP,
enabled: (process.env.GAS_REPORTER === 'true'),
},
disableEthernal: (process.env.ETHERNAL === 'true'),
etherscan: {
apiKey: process.env.ETHERSCAN,
},
};
export default config;
The line with disableEthernal give us static Error.

setting in types/estensions/ts like:
declare module "hardhat/types/config" {
interface HardhatUserConfig {
disableEthernal?: boolean;
}
}
it works

Thank you Antoine for the big support with this product and sorry for my
late response.
I'll try everything soon but I think should be everything ok. I'll do more
tests in the next days with your newer version.
I'll let you know.
Again, thanks.
Best regards
Il giorno lun 9 mag 2022 alle ore 18:18 Antoine @.***>
ha scritto:

Ok, so I've pushed v1.0.0 with quite a few changes in the config.
Everything is now done in the Hardhat config object, under an ethernal
key, so that's much cleaner.
You can do something like:
export default {
ethernal: {
disabled: 'true',
workspace: 'hardhat'
}}
I've updated the README with all the changes. If you were using the local
keychain to login (ie you logged in with ethernal login, you'll have to
set some env variables now).
Let me know how that goes
—
Reply to this email directly, view it on GitHub
https://github.com/tryethernal/hardhat-ethernal/issues/23#issuecomment-1121307509,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGYK7EUHBYFSQVBLMCKP2N3VJE3GPANCNFSM5VKRWCLQ
.
You are receiving this because you authored the thread.Message ID:
@.***>


Latest release (v0.6.9) doesn't match with documentation regarding self-signed certificates

First and foremost: thanks for this amazing library!, it saved me tones of work!.
Now a quick (and hopefully easy to fix ;) ) issue: I've been banging my head for some two days now, trying to figure out why cradle won't make any difference wether I configure the self-signed certificate or not, using the "ca" param stated in the documentation.
Tried to debug from the sources in node_modules and found that there was no code using the parameter, although there certainly was in the github repo.
Long story short: the latest release available, doesen't contain that code, thus doesn't match the documentation as seen in github, leading to the error at hand.
Fixed easy and dirty removing the dependency and reinstalling with "npm install --save git+https://github.com/flatiron/cradle.git#632a9fededb774ba5ecb94d3a268280f1bb62a88" (latest commit at the moment). All working now! (though it would be better to avoid that hack ;) )
Thanks again and happy coding!

Yeah, we haven't had a release in a while. 0.7.0 should be released soon.

Now, THAT was FAST!
Thanks!!

The package json is referring to v0.7.1, but the latest github release is v.0.6.9?


Dashboard template should not suffix with .yml.j2

Currently, the generated template file for dashboard become /etc/kubernetes/dashboard.yml.j2, which should be /etc/kubernetes/dashboard.yml

ci check this


Use up-to-date checks for creating the JAR manifest

For generating the manifest for the JAR task Gradle currently uses a GeneratedSingletonFileTree. This file tree generates the file for every build, and then Gradle needs to snapshot the file since it is an input to the JAR task.
We should not generate the manifest if it already exists and the configuration didn't change. So we want to use up-to-date checks for generating the manifest to improve performance for incremental builds.

cc: @gradle/execution

Related to #11818.

Adding a new task to create the manifest would add up-to-date checks, but also is hard with respect to backwards compatibility. We can easily add a manifest task for the JAR task added by Gradle plugins, but we can't add the task easily for arbitrary JAR tasks.
Another option would be to use the execution engine in GeneratedSingletonFileTree to create the manifest. For that to work, we would need to declare the inputs to the manifest work unit from the JAR task. We could also schedule the generation of the manifest as a separate node in the execution graph.

If we want to change how manifests are added, we might need to do it in 7.0.


Error on receiving meta information from model

https://github.com/carlrobertoh/LLM-Client/blob/9e6fe09a719a42744a9c8e574180615aa624d4df/src/main/java/ee/carlrobert/llm/client/openai/completion/OpenAIChatCompletionEventSourceListener.java#L19
SSE can come with meta information, which has empty choices array. E.g.:
data: {"id":"","object":"","created":0,"model":"","prompt_filter_results":[{"prompt_index":0,"content_filter_results":{"hate":{"filtered":false,"severity":"safe"},"self_harm":{"filtered":false,"severity":"safe"},"sexual":{"filtered":false,"severity":"safe"},"violence":{"filtered":false,"severity":"safe"}}}],"choices":[]}

Hello @paintkeeper can you confirm that the change https://github.com/carlrobertoh/llm-client/commit/3831d02c7ac0bd932dfad844605f3bd41d709d2b in 0.6.0 fixes that problem?


Fixed opengl family duplicates issue and add tests

Overview: What does this pull request change?

Fixes #2085
When migrating cairo family tests to opengl, a test was failing as opengl was including duplicates objects in the family. This PR ensures only unique elements are added to family and also migrates cairo tests.
Motivation and Explanation: Why and how do your changes improve the library?

Links to added or changed documentation pages

Further Information and Comments

Reviewer Checklist

[ ] The PR title is descriptive enough for the changelog, and the PR is labeled correctly
[ ] If applicable: newly added non-private functions and classes have a docstring including a short summary and a PARAMETERS section
[ ] If applicable: newly added functions and classes are tested

Tested with one of my videos where I was having trouble with duplicates and it fixed it, so thank you! Other than that, tested with other videos and everything looks good to me.

Can you share a code snippet of what it fixes please ? Just to keep an eye on any other issues that could be affected by duplicates

Can you share a code snippet of what it fixes please ? Just to keep an eye on any other issues that could be affected by duplicates

If the code were a snippet, I would. But the code uses a Manim plug-in I am developing and have not yet made public.


Add @indoorequal/vue-maplibre-gl

This is a fork of https://github.com/razorness/vue-maplibre-gl with added features and support for maplibre-gl 4

Wouldn't it be easier to simply upstream the work?

I tried, but there is no answers on my PR since 10 months :(

I've added a comment to the relevant PR.
The last commit was 4 month ago, so I hope this repo is still maintained.
Ping me in a few days here if there's no response in the other issue and we'll replace the link instead of adding a new one.

To follow up on this, there's still been no response (or commits or anything). @francois2metz's fork is very active and adding new features.


Adding new maintainers

As described in https://github.com/hubotio/hubot/issues/1541#issuecomment-1512130320 , I want to add these folks to the Maintainers team:

@joeyguerra
@xurizaemon
@joh6nn

I've tried to do it manually, but they keep getting removed. I suspect it has to do with entitlements that are resetting the team?

cc @levenleven as someone still on a team at GitHub that may have something to do with hubot?

I've tried adding them to hubotio/hubot, so we'll see if that gets wiped as well or not

I think adding me to hubotio/hubot worked, at least. I've successfully closed several stale issues. Probably best to wait a day before we call that certain, though

I just got an invite to the Hubotio org from @entitlements . Thanks ya'll.

@technicalpickles can I please get added to the Maintainers team? Or get member access to all the repos in the Hubotio org? I'd like to start updating those other repos as well. Starting with the Hubot-help one.

I forgot to update here, but I got word that y'all were added to the organization. Organization membership is what it was managing, not teams, so I've updated those manually.


Jupyter Notebooks don't support Halo

While Halo works perfectly fine in the terminal, I can't get Halo to work inside a Jupyter notebook. I am running the following code in the first cell of the notebook:
from halo import Halo
from time import sleep
with Halo(text='Loading', spinner='dots'):
    sleep(5)

The program runs through without any errors, but no spinner is shown at all.
I figured out, that if you write something to stdout with sys.stdout prior to calling Halo, then the spinner is shown, but each spinner and corresponding text are shown next to each other, i.e. clearing the current line doesn't work.
from halo import Halo
import sys
from time import sleep
sys.stdout.write('test\n')
with Halo(text='Loading', spinner='dots'):
    sleep(5)

returns the output
test
⠋ Loading⠙ Loading⠹ Loading⠸ Loading⠼ Loading⠴ Loading⠦ Loading⠧ Loading⠇ Loading⠏
Loading⠋ Loading⠙ Loading⠹ Loading⠸ Loading⠼ Loading⠴ Loading⠦ Loading⠧ Loading⠇
Loading⠏ Loading⠋ Loading⠙ Loading⠹ Loading⠸ Loading⠼ Loading⠴ Loading⠦ Loading⠧
Loading⠇ Loading⠏ Loading⠋ Loading⠙ Loading⠹ Loading⠸ Loading⠼ Loading⠴ Loading⠦
Loading⠧ Loading⠇ Loading⠏ Loading⠋ Loading⠙ Loading⠹ Loading⠸ Loading⠼ Loading⠴
Loading⠦ Loading⠧ Loading⠇ Loading⠏ Loading⠋ Loading⠙ Loading⠹ Loading⠸ Loading⠼
Loading⠴ Loading⠦ Loading⠧ Loading

Is there something wrong on my end, and do you have an idea how to fix that?
It would be really nice if Halo worked with Jupyter too. Thanks for your efforts and for sharing this library!

@HBadertscher This is one feature I would love to include. I feel we would need to create a widget for jupyter notebook and ipython so that spinner renders as expected. I don't have experience with that, hence will take me a while to finalize the fix and get this working.
If you would like to work on this, feel free to take this one up and I will assign it to you.

Just adding here. If spinner is started in a cell in iPython and not stopped within the same cell, the spinner cannot be stopped. Need to explore this a little more. A widget might fix this.

@ManrajGrover Can I try to implement this feature? I don't have experience with ipython and jupyter widget too, but it's so interesting to work.
refer

tqdm jupyter integration
tqdm notebook
widget user guide

@JungWinter sure! Please go ahead and give it a try.

@ManrajGrover I made prototype and can test in notebook.
First, from ipywidgets import HTML is tried, but problem was happen about color ansi code.
Second, from ipywidgets.widgets import Output, It's work well now. I overwrite __init__, clear, _render_frame_, start, stop_and_persist.
I checked examples work fine, but not yet contain any jupyter test code.

And when I run pylint, SyntaxError is occured. Could you help me to handle this error?
(halo-venv) halo git:feature-notebook ❯❯❯ pylint --errors-only --rcfile=/Users/WinterJ/Github/halo/.pylintrc --output-format=colorized halo
Traceback (most recent call last):
  File "/Users/WinterJ/.pyenv/versions/halo-venv/bin/pylint", line 11, in <module>
    sys.exit(run_pylint())
  File "/Users/WinterJ/.pyenv/versions/3.6.1/envs/halo-venv/lib/python3.6/site-packages/pylint/__init__.py", line 13, in run_pylint
    Run(sys.argv[1:])
  File "/Users/WinterJ/.pyenv/versions/3.6.1/envs/halo-venv/lib/python3.6/site-packages/pylint/lint.py", line 1260, in __init__
    'init-hook')))
  File "/Users/WinterJ/.pyenv/versions/3.6.1/envs/halo-venv/lib/python3.6/site-packages/pylint/lint.py", line 1361, in cb_init_hook
    exec(value) # pylint: disable=exec-used
  File "<string>", line 8
    ZGljdChfX2ZpbGVfXz1hY3RpdmF0ZV90aGlzKSkK'.decode('base64')
                                            ^
SyntaxError: invalid syntax

@JungWinter This looks amazing! I'll have a look at the code soon. Regarding lint error, I'll have a look at it as well while going through your code. Could you please check if this works on ipython as well?

@ManrajGrover Thanks for reviewing! I checked Halo already works well. Although HaloNotebook doesn't work in ipython shell. I think it's not a problem because there is the original halo. If there are any problems I didn't recognize, please let me know.

@JungWinter I remember the issue with iPython. If a user does not handle keyboard interrupt and the spinner is running, a KeyboardInterrupt is thrown but the spinner keeps spinning. I'm creating an issue for this.

@ManrajGrover Oh, I didn't check that issue. I worked a little to solve that problem. Please check my comment. https://github.com/ManrajGrover/halo/issues/35#issuecomment-354552242

This is fixed in #40 thanks to @JungWinter! This will be made available soon in next release. I need to do few fixes before making a release.


custom-headers

@JustSteveKing array_merge is in place

🎉 great job @dominikzogg

closed before merging 😆 sunday coding, am I right!

@JustSteveKing thanks


getting the below error

I took the credits in Capsolver and followed the steps mentioned but I am getting the below error
ERROR:
403 Forbidden

403 Forbidden
Microsoft-Azure-Application-Gateway/v2

+1

Got this Error

<EMAIL_ADDRESS>start
ts-node --transpile-only src/index.ts

[12/26/2024 4:17:13] Texas Scheduler v5.0.0 is starting...
[12/26/2024 4:17:13] Requesting Available Location....
[12/26/2024 4:17:13] Waiting for captcha token from task ffd3dc1f-940f-419a-9b98-94b907654584...
[12/26/2024 4:17:14] Captcha token received successfully
[12/26/2024 4:17:14] WARNING -> Got 403 status code
[12/26/2024 4:17:14] Endpoint: /api/Auth
[12/26/2024 4:17:14] ERROR:
403 Forbidden

403 Forbidden
Microsoft-Azure-Application-Gateway/v2

It just works again for me .
seems like it's capsolver api issue

[12/26/2024 10:14:59] Captcha token received successfully
[12/26/2024 10:15:00] WARNING -> Got 403 status code
[12/26/2024 10:15:00] Endpoint: /api/Auth
[12/26/2024 10:15:00] ERROR:
403 Forbidden

403 Forbidden
Microsoft-Azure-Application-Gateway/v2

{
'Content-Type': 'application/json;charset=UTF-8',
Origin: 'https://public.txdpsscheduler.com',
Referer: 'https://public.txdpsscheduler.com'
}
[12/26/2024 10:15:00] WARNING -> Got rate limited, sleep for 10s...
[12/26/2024 10:15:10] WARNING -> Got 403 status code
[12/26/2024 10:15:10] Endpoint: /api/Auth

It just works again for me . seems like it's capsolver api issue

okay ill keep trying

started working for me with no changes aswell.

sometime capsolver didnt get confident score high enough. I got that issue too

fyi, you guys can contact capsolver if the confident score isn't high enough
If you guys want me to add more solver services make a new issue and i will work on it ;)

I am also getting this error. I am not using the paid solution. I am trying to use the manual token. I still have to put this part like this. "Browser" isn't working.

@TracyZhou619 where are you running this? Github codespaces or localhost?

Oh i know what you mean now, will fix on next release

@TracyZhou619 where are you running this? Github codespaces or localhost?

Github codespace @phamleduy04

Github codespace isn't supported broswer mode as mentioned on the wiki

Just comment out switch case for CreateCaptchaSolverTask and GetCaptchaSolverResult until its fixed..


Support viewing remarks

Description
As an OSCAL content author, I want to view remarks in regard to metadata.
Acceptance Criteria

[ ] The 'remarks' field is properly displayed within the React library with proper formatting

Proposed Solution
This could be displayed at the bottom of the metadata section, underneath the "Parties" panel.
Additional Notes
No response
Implementation

[ ] I can (or plan to) submit a pull request to implement this
[ ] Implementing this may result in a breaking change

For context https://pages.nist.gov/OSCAL/reference/latest/complete/json-reference/#/catalog/metadata/remarks

Issue #689 builds on this. May want the same person to work both.

Proposed design
@EasyDynamics/oscal-editor-reviewers
Background
Currently the page looks like https://oscal-viewer.msd.easydynamics.com/catalog/?url=https://raw.githubusercontent.com/EasyDynamics/oscal-demo-content/test-content/catalogs/basic-test-catalog.json

Design
metadata.remarks can be handle with just a markup-multiline component. I imagine just having a text area in an accordion underneath Locations.

A modal for remarks doesn't seem especially useful. I think it'd be far better to display it above the accordions just as regular text. Maybe as body2 text, and after some number of lines, have it truncate and a "See more" button that would expand to show the rest (to avoid several screen fulls of text).
I can see "Remarks" button being useful in the general sense; especially since nearly every OSCAL object has them. We likely need something a little shorter than the word "Remarks" to use as an idiom (perhaps the Comments icon?) that would fit in more places (with a useful aria-label or other attribute to maintain accessibility).
But I think at the metadata/document level, we have a little more room to display them (and the content may be a bit longer in some cases) than what you'd get for remarks on a prop on a part on a control.
I want to avoid making literally everything a dialog just because.


generate black image

thanks for your job! i found a error in the code,whatever image i use which always generated black image,how to solute this error?looking forward to your answer!

thanks for your job! i found a error in the code,whatever image i use which always generated black image,how to solute this error?looking forward to your answer!

I also encountered the same problem, have you solved it?

谢谢你的工作！我在代码中发现了一个错误，无论我使用什么图像，它总是生成黑色图像，如何解决这个错误？期待您的答复！

我也遇到了同样的问题，你解决了吗？

yes! i found a part of code is strange which is in adain.py, in the calc_mean_std function,there is a "mask" for formal parameter,it is none by default,so it will generate black image,so we need delete a part of codes , it is"if mask is not None:..." reserve  the codes behind the "else",although it not generate black image,but it have not good effect,so i am also finding the reason now

谢谢你的工作！我在代码中发现了一个错误，无论我使用什么图像，它总是生成黑色图像，如何解决这个错误？期待您的答复！

我也遇到了同样的问题，你解决了吗？

yes! i found a part of code is strange which is in adain.py, in the calc_mean_std function,there is a "mask" for formal parameter,it is none by default,so it will generate black image,so we need delete a part of codes , it is"if mask is not None:..." reserve the codes behind the "else",although it not generate black image,but it have not good effect,so i am also finding the reason now

Thank you. It no longer generates black images, but the results are not satisfactory. I will continue to find the reason. Thank you again❤❤.

@1289600760 hi, really thanks for you suggestion, and have you finally find the reason?

@1289600760你好，非常感谢你的建议，你最终找到原因了吗？

sorry ，i didn't found the reason

@1289600760你好，非常感谢你的建议，你最终找到原因了吗？

it have not good effect,so this method is not adapt my dataset,

@1289600760 Could we please communicate with each other? if you not mind, please add me:13186212510, very thanks to you.

If you're getting a black image, this could be because the prompt you are passing the model does not match the image that you are giving the model. This then causes the automatic segmentation that we use for AdaIN to not segment the object correctly.
There are two ways to fix this:

Refine the prompt you are using and ensure that the prompt matches the object in the image.
Disable the use of the AdaIN using the appropriate flag in the config.
Hope this helps


[Docs] add explanation of reasoning behind immutability

From @lennartschoch on the [immutability of the api](https://github.com/zino-app/graphql-flutter/issues/521#issuecomment-591918379:

Is there any specific reason for making the clients properties immutable?
Me (and I guess a lot of other devs) would highly appreciate an option to set headers for each individual request instead of having to replace the whole client every time.
Apart from that, replacing the client also makes it quite hard to test and to mock.
When my client wrapper is able to interchange the whole client at any time, it seems uncertain to me whether I am working with a mock client still.

We should provide the reasoning for this decision, or if it is unnecessary and would make users lives easier reconsider

linking to #741

@lennartschoch idk if it was mentioned before, but it is possible to set headers for an individual request through Context. On v4 beta one would do:
QueryOptions(
  ...
  context: Context.fromList(
    const [
      HttpLinkHeaders(
        headers: {
          "foo": "bar",
        },
      ),
    ],
  ),
)

Merging this into #741


License on the project will be good

Hello.
First of all I wat to thank you (@dandoh) for this boilerplate. It helps me, a lot, to understand how to make a setup for a Haskell web application. I have use it in on of my side project as my base, which led me to think about whether I can use it or not license wise.
It will be great if it can has some license.
I have seen a lot of BSD-3-Clause and MIT aswell in the haskell comunity and both of them will be okay.
Thank you.

Hi @Pacific01
I added MIT Licence.
Feel free to tell me if you have any issue.
Stay safe!

Nice. 😁
In fact I have a little pull request prepared in it I have added some Docker{file, composer,...} so anyone can easily run and test it.
Thank you!

@Pacific01 That would be superb! Please send your PR 🙇


Using with normal from inputs

If I wanted to sync up the multiselect with a normal input field, lets say an input:hidden, it all works well if I use primitive values for the multiselect. If I use an array of objects on the other hand,  like
[ { value: 1, label: 104 },
   {value: 2, label: 105}]

it writes the whole selected object to the synced up property, but that cant be sent over as a normal form submit data if I`m not mistaking. If I use something like v-model="synced.value" on the aforementioned hidden input, It will get only the value, but then If I try to pass it back to multiselect (after a page refresh for example) it wont work as multiselect needs the whole object it passed as current in the first place, correct?
Should I do some toString parsing or there is a better way.

As far as I know, regular inputs accept only primitives as value.
Right now multiselect doesn’t support recognizing whole objects based on the key/id (even if it uses it internally to match and compare objects).
I’m not sure what you mean by normal form submit data. If you use regular XHR requests (or with a wrapper library like vue-resource or axios) you can send a JSON object. The same goes with FormData.

No I had to do a normal form.submit() on the form. Complicated to explain but to work around this i had two inputs. For the value and for the Label. If I used multiple prop I just separated the values with a comma and all worked.

Could you provide a snippet of the submit code? Is this some kind of remote service where you send the form?

I will try to give a better explanation later.

In the other issue you asked for an on-close event. If you need something similar to it, you can pass a callback function to :on-change prop. This method would need to accept the selected new value. Additionally you would have to remove the .sync modifier.
You can look into the documentation at the Vuex section.
Hope this helps.


feat: embed youtube videos

We could also add some breaks around this: https://ab0a921a.snort-social.pages.dev/e/note1mju85jc587326vqgjkkn9f4sy5c4a578azayzhy4q0f54m4qslusfehluj

Also styling should be extended for youtube iframes
https://github.com/v0l/snort/blob/7831bdbcc28a46eea436afa32d0db252df200c13/src/element/Note.css#L25-L28

@v0l addressed your comments, I think is best to transform HTTP links in one pass, added a better regex for extracting youtube vid ids.


feature: possibility to override diagnostic configuration

Did you check the docs?

[X] I have read all the lazy.nvim docs

Is your feature request related to a problem? Please describe.
Current renderer code setting up diagnostics for lazy popup without any respect to user's (global) diagnostic setup.
And that leads to some rendering artifacts.
For example, it doesn't know anything about lsp_lines (which I'm using), so when it enables virtual_text, it doesn't disable lines, which leads to them both being enabled, which in turn causes rendering artifacts:

Also, it doesn't respect my "fallback" virtual_text setings ({ spacing = 1, prefix = "●" }) and just set it to true...
It would be nice, if there was a setting that renderer would use to set diagnostic config up, so user wold have a way to override current renderer defaults (which in turn would give me a chance to fix this up).
Describe the solution you'd like
Something like
ui.diag = <table of `vim.diagnostic.config()` options | boolean (false => disable diagnostic, true => current defaults) | function returning either of previous>

in lazy.setup() config, and a bit of logic to hadle that in render.lua
Describe alternatives you've considered
:man_shrugging:
Additional context
No response

https://www.lazyvim.org/plugins/lsp
Search for diagnostics

@folke are you sure it is right link, or it is related to the described issue?
The issue is not about diagosric in general.
It is about diagnostic setup lazy uses by itself in the lazy popup (to mark available updates and actions (fetch, log, ...)).

the only mentions of "diagnostic" on the link is in lspconfig and in null-ls.
Both are not related to this issue.

And it is definitelly impossible to override (pseudo)diagnostic configuration that sets up in render.lua, because of the code there...

// Well, I temprary hacked that arounnd by creating autocommand, that triggers on TextChanged and re-sets diagnostics, but that is still not ideal (and also hurts perfomance).
What is needed is option to pass to vim.diagnostic.set() (in render.lua) as local bufer diagnostic configuration, which it will use on creating pseudo "diagnostics" for actions and available updates....

right, then just disable lsp_lines for the lazy filetype

I.e. what I talking about is to change https://github.com/folke/lazy.nvim/blob/652b6febf8d5c99eb8cf4a1cec63da6db62e77d2/lua/lazy/view/render.lua#L86 to the code, that will try to take that table from lazy.setup() options

Like I said, if it bothers you, then disable lsp_lines for the lazy filetype. I'm not going to support other diagnostics renderers. sorry

right, then just disable lsp_lines for the lazy filetype

Well, not that it was too easy.
And I found the only way to (poperly) did that by a bunch of kludges with using state-functions in global vim.diagnostic.config(), which checks current filetype and return corresponding value...
But still, it only solves lsp_lines issue, but it can't solve the fact that there is just true set to virtual_text in render.lua, but not the configuration I use globally for virtual_text when it is enabled (as I mentioned above, I set spacing to 1 instead of default 4, and prefix to round instead of square).

well, I agree, that remaining part of the issue is mostly about "I want to customize that what you don't consider customizable", but... Why not?
// Actually, I'd even made a PR myself, just if I'd been sure you're refuse it.
And if you have some strong objections, I'd like to know reasoning :man_shrugging:


Stroom v5 findReplaceFilter isn't escaping the replace sequence

I  can't get a newline to output as the replace value in a findReplaceFilter.
I've tried \n and \n to no avail.

Fixed in v6.0-beta.9

Fixed in v6.0-beta.9


Global operator conversion

All changes with respect to new release for Private Cloud portal 6.7.0

@Nidhi251289 almost done, just one question. In the release notes, there was this line: "We have removed the unreliable uptime field from Namespace overview page."
Is the name of the field "Uptime"? Or "Unreliable Uptime"? I'm guessing it's just Uptime but wanted to make sure.

Ready and waiting for the go ahead.


Blacken our code

Checklist

[ ] npm install && npm test passes
[x] tests are included
[ ] documentation is changed or added
[ ] commit message follows commit guidelines

Description of change

Like #1899 but for Python code.  Uses the Python Software Foundation's Black https://github.com/psf/black to format all Python in the cononical way an adds a test to Travis CI to avoid any backsliding.

By doing this, we're basically making it impossible for changes from refack/GYP3 to be pulled over, so we'd need to be sure that we're committing to maintaining GYP here and having the canonical version. I'm fine with applying consistent style linting, it makes contributions much more straightforward, but this is a big step, so let's let this linger and see what others have to say.

If we blacken both codebases, we will get really clean diffs.

If we blacken both codebases, we will get really clean diffs.

but lose the ability to cherry-pick isolated changes


isSubmitting is still true if synchronous onSubmit throws error

Bug report
Current Behavior
If onSubmit() is defined as a synchronous function, then any time an exception occurs within submission execution will cause the isSubmitting state to stay true.
Expected behavior
isSubmitting is set to false after an error occurs during onSubmit() execution.
Reproducible example
Code sandbox: https://codesandbox.io/s/formik-issubmitting-error-example-k0fwd

In the sandbox I linked, fill out the email form, though not required
click submit (i defined the onSubmit() function to throw an error rather than show alert, and it's synchronous)
Observe the props in the json printout shows  "isSubmitting": true and the submit and refresh buttons are still disabled. Changing the form doesn't reset them

Suggested solution(s)
See expected behavior section.
Additional context
This has proved to be a problem for me because I need to use some non-async calls for my form submission which use the .then() promise callbacks. Because my submission buttons disable if isSubmitting is true, they stay disabled.

Your environment

Software
Version(s)

Formik
2.2.5

React
16.11.0

TypeScript
3.8.3

Browser
n/a

npm/Yarn
n/a

Operating System
n/a

Just saw this remark on the onSubmit API.

I have changed my code to use async submissions to resolve this issue on my end, but wanted to ask if there is any future work to make synchronous submissions set isSubmitting to false after finishing? it might mean fewer conditionals users have to bake into their own code and perhaps a bit of a re-render performance boost.
https://formik.org/docs/api/formik#onsubmit-values-values-formikbag-formikbag--void--promiseany

@mryanlo we don't want to assume that isSubmitting should be false after a sync callback because there is no way to tell whether the dev used asynchronous code in a fire-and-forget format. Examples are functions like setTImeout which don't return a Promise.
We should probably have forced users to wrap code like this in a Promise from the beginning and setSubmitting(false) automatically after sync code, but this didn't make too much sense when Promises were less ubiquitous and I don't think it makes sense to do this now, when there's probably so much code out there that works without this limitation.


suport lombok.experimental.var

Hello.
https://projectlombok.org/features/experimental/var.html

@var was introduced as experimental feature in lombok v1.16.12.

Please suport it.
Thank you.

There is a PR #323 for this, but I did not have much time yet to look into it.


Test generate target

The automated testing needs to test make generate.
Now that devtools is a separate build job, Shroud is available to all host configurations.

Ideally, Shroud should have a (gitlab) pipeline that tests its new versions against Axom's develop branch
e.g. as part of its PR review and/or release process.
Tag: @ltaylor16


problem with offline signature for token transfer

Faced with the problem it is necessary to transfer the token from one user to another for the fee of the receiving user. One way is to create an offline transaction by the user and call it by the receiving user. With the translation of SOL, I did everything, but with tokens it does not work in any way.
Preparation:
file user.json
[241,225,43,156,175,192,111,231,247,139,134,189,175,90,238,176,156,195,203,117,157,175,16,33,147,25,242,243,253,56,228,211,193,95,123,80,62,95,143,190,239,31,6,185,154,48,222,2,141,160,169,68,43,168,127,136,21,187,113,159,146,13,10,16]
file payer.json:
[227,159,215,62,236,242,137,43,50,62,46,77,89,46,14,128,17,229,184,99,60,213,63,240,40,137,56,108,18,196,251,15,17,16,28,202,133,181,130,110,4,2,218,70,184,114,79,168,171,244,181,139,66,121,77,218,173,170,222,119,241,136,237,163]
file conf.yml:
json_rpc_url: "http://localhost:8899"
websocket_url: ""
keypair_path: payer.json
address_labels:
"11111111111111111111111111111111": System Program
commitment: confirmed
There are 2 users: user and payer. The user wants to send 1 token to payer. If there are no tokens, then you can do it in the following way:
spl-token create-token --decimals 0  => 8R3dZ5fEGVraDqGSRJmMGj63NqQNoDVUJkM2eiwfuQjg
spl-token create-account 8R3dZ5fEGVraDqGSRJmMGj63NqQNoDVUJkM2eiwfuQjg
spl-token mint 8R3dZ5fEGVraDqGSRJmMGj63NqQNoDVUJkM2eiwfuQjg 1000
The following commands are needed just for convenience:
BLOCKHASH=$(solana block | grep "Recent Blockhash" |  awk '{print $3}')
PAYER=$(solana-keygen pubkey payer.json)
USER=$(solana-keygen pubkey user.json)
USERTOKEN=$(spl-token accounts -v --fee-payer payer.json --owner $USER | grep $TOKEN | awk '{print $2}')
USERTOKEN - user`s token account
This is how I make the signature of the user USER:
SIGNER=$(spl-token transfer $TOKEN $AMOUNT $PAYER
--blockhash $BLOCKHASH
--sign-only
--from $USERTOKEN
--owner user.json
--fee-payer $PAYER
--allow-unfunded-recipient --mint-decimals 0 | grep "=" | grep -v Pubkey )
And so I want to perform a transaction for PAYER:
spl-token transfer $TOKEN $AMOUNT $PAYER
--blockhash $BLOCKHASH
--from $USERTOKEN
--signer $SIGNER
--config conf.yml
What gives an error: #ERROR: RPC response error -32002: Transaction simulation failed: Error processing Instruction 0: custom program error: 0x4 [5 log messages]

Hi!  We don't use Github for support requests.  Please join us in #wallet-support on https://solana.com/discord


Integrate pages into global searches

Replace notion logo with higher quality and png background.
Pages now show up on global searches without needing to tab through "Notion: Find Pages".

Hello,
having pages show in global searches is a good idea. I think it should be optional (configurable in a /src/notion.ini file) though, I am personally inclined to no as a default.

Hi @wolloda, a great suggestion. I've implemented the logic as recommended in the latest commit.

Hello @CallumWigg thanks for implementing the config option.
Please make it False by default and mention the option in the README


Fix Pino HTTP types

This PR will fix the problem with pino and pino-http types.
#699

Hi @iamolegga please take a look of this PR. I did all the changes as we discussed it in #699

Hey @jarcodallo , thanks! It looks like it needs to be rebased again (thanks, dependabot) 😅

And I'm still wondering do we really need to include pino in deps here as it goes as dep of pino-http. I'm going to fork your branch and exclude it from the deps to see the result for the test project if it will work without pino as a direct dep of this lib

Hey @jarcodallo , thanks! It looks like it needs to be rebased again (thanks, dependabot) 😅  And I'm still wondering do we really need to include pino in deps here as it goes as dep of pino-http. I'm going to fork your branch and exclude it from the deps to see the result for the test project if it will work without pino as a direct dep of this lib

OMG! remove the deps bot hahaha (flipping the table meme here).
I included it, because the @nestjs/platform-fastify install an old version of pino that need the types from @types/pino package.  I will check if everything work w/o pino in devDeps. Thanks

@iamolegga I remove pino from the devDeps and get this error:

With pino installed as devDep:

Ok then, let's keep pino in deps, I believe we can drop it when platform-fastify will be updated.
Thank you very much for this improvement! Merging!

Ok then, let's keep pino in deps, I believe we can drop it when platform-fastify will be updated.
Thank you very much for this improvement! Merging!

Happy to help 🚀

@jarcodallo now I'm thinking which version update should be for this update. major, minor, fix 🤔 API of this lib didn't change, but imports/types of underlying logger have changed slightly

@jarcodallo now I'm thinking which version update should be for this update. major, minor, fix 🤔 API of this lib didn't change, but imports/types of underlying logger have changed slightly

My personal opinion is that you shouldn't update the major version just the minor, because currently v2.x is broken when try to install pino-http@v6 as peer dep.

Thanks for fixing this. Looking forward to be abe to update pino and related libs.
I would also vote for a minor version change for the same reason as @jarcodallo

Yes, correct, will ship now, thanks, everyone!

please check out v2.4.0 🎉


feat: new variation import workspace

Description
This variation helps customers who have existing VPC landscape and PowerVS workspace, to make use of SAP HANA on Power VS catalog solution, by importing the landscape information and make it consumable for next catalog tile.
Release required?

[ ] No release
[ ] Patch release (x.x.X)
[x] Minor release (x.X.x)
[ ] Major release (X.x.x)

Release notes content

Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

For mergers

Use a conventional commit message to set the release level. Follow the guidelines.
Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
Use the Squash and merge option.

/run pipeline

/run pipeline

/run pipeline

/run pipeline

:tada: This PR is included in version 3.2.0 :tada:
The release is available on:

GitHub release
v3.2.0

Your semantic-release bot :package::rocket:


[Client] Hardware integration: Install code in '/opt'

In story #8, we introduced the POSBoxless server, a proxy to handle the peripherals like the barcode scanner. This software is currently installed in /usr/src/odoo, however I think it would be a better idea to install it in /opt/odoo like /opt/eca-web.


Automatically make channel for year-day

Closes #26

@TrojanerHD

This is untested and not sure if it will work
According to https://discord.js.org/docs#/docs/main/stable/class/CategoryChannel?scrollTo=createChannel it should

Could you add a ( Closes #26 ) to the title or description of the pull request, well, if I can't add it by having it in this comment that is.

This is untested and not sure if it will work
According to https://discord.js.org/docs#/docs/main/stable/class/CategoryChannel?scrollTo=createChannel it should

Also, the link is broken, here is the working one:
https://discord.js.org/#/docs/main/stable/class/CategoryChannel?scrollTo=createChannel

Both links work for me

Both links work for me

Interesting, on mobile the first link doesn't work for me, but on my PC it does.

Could you add a ( Closes #26 ) to the title or description of the pull request? Well, if I can't add it by having it in this comment that is.

Apparently, adding it to the title doesn't work. I changed the initial comment and the title and now it works

Could you add a ( Closes #26 ) to the title or description of the pull request? Well, if I can't add it by having it in this comment that is.

Apparently, adding it to the title doesn't work. I changed the initial comment and the title and now it works

Interesting


It should be simpler to support piping input

ArgumentParser version: 1.1.2.
Swift version:
swift-driver version: 1.45.2 Apple Swift version 5.6.1 (swiftlang-<IP_ADDRESS>3.66 clang-13<IP_ADDRESS>)
Target: arm64-apple-macosx12.0

Checklist

[ ] If possible, I've reproduced the issue using the main branch of this package
[x] I've searched for existing GitHub issues

Steps to Reproduce
a simple argument parser that could take an array of input
@main
struct Main: ParsableCommand {
    @Argument
    var path: [String]

    func run() throws {}
}

compile this and run it with pipeline echo **/*.jpg | .build/arm64-apple-macosx/debug/main
it seems that the stdout is not pass as stdin
Expected behavior
the stdout from lhs is passed to rhs
Actual behavior
Describe or copy/paste the behavior you observe.

What's not working?
A shell piping stdout of one process to stdin of another process doesn't have any impact on the arguments passed to the second process.
There are argument parser libraries for other languages that do support mapping a single argument to either a provide file or stdin if no file is provided, but that doesn't seem to be related to what you might be asking about.  It sorta sounds like you are asking for the library, when given no arguments, to parse all of stdin and map that to arguments?  I don't think I've seen that feature in any argument parsing library for any language.

Oh i miss understand about argument parser as also able to parse stdin
I thought piping stdin is same with passing an argument to the executable

@wendyliga Thanks for the feedback! We’ve had a few requests for being able to automatically populate an argument with stdin, so I think it’s worth looking at more. I’m going to convert this to an enhancement request 👍🏻

@wendyliga Thanks for the feedback! We’ve had a few requests for being able to automatically populate an argument with stdin, so I think it’s worth looking at more. I’m going to convert this to an enhancement request 👍🏻

Just a thought - maybe an async sequence? If building a pipeline took the amount of data coming can be infinite.

I was just working on a project where this really would have been useful! Perhaps something like @Argument(takeFromStandardInput: true) var input: String


Sequenced motion via MoveIt2

Hello,
I am a student conducting research on MED14 in South Korea. First of all, I would like to express my gratitude for sharing the code you developed.
I am currently using the code provided at https://github.com/lbr-stack/lbr_fri_ros2_stack/issues/152 to control a robot.
there is an issue with this code where the robot starts from x=0.3, y=0.3, z=0.8, stops at x=0.35, y=0.3, z=0.8, and then resumes to reach x=0.4, y=0.3, z=0.8.
However, I would like to know how to modify it so that the robot can move directly from x=0.3, y=0.3, z=0.8 to x=0.4, y=0.3, z=0.8 without stopping at x=0.35, y=0.3, z=0.8.
Additionally, I am curious about how to input the path of the robot's end effector to make it move.
Thank you always.

hi @SUUHOLEE , yes no problem. Assume you have a list of waypoints
    # List of poses to move the robot to
    poses = [
        Pose(
            position=Point(x=0.3, y=0.3, z=0.8),
            orientation=Quaternion(x=1.0, y=0.0, z=0.0, w=0.0),
        ),
        # Pose(
        #     position=Point(x=0.35, y=0.3, z=0.8),
        #     orientation=Quaternion(x=1.0, y=0.0, z=0.0, w=0.0),
        # ),
        Pose(
            position=Point(x=0.4, y=0.3, z=0.8),
            orientation=Quaternion(x=1.0, y=0.0, z=0.0, w=0.0),
        ),
        # Add more poses as needed
    ]

Just remove / add points as needed (commented out above).
May I ask whether you aim to control the end-effector's position or velocity? Do you want to use Moveit or would something suffice?

It seems that my intended purpose wasn't conveyed properly.
In the code provided in https://github.com/lbr-stack/lbr_fri_ros2_stack/issues/152, when there are three points forming a straight line, removing the middle point allows the movement to proceed as desired.
However, there is an issue with implementing a waypoint at x=0.35, y=0.3, z=0.8 while moving from x=0.3, y=0.3, z=0.8 to x=0.4, y=0.4, z=0.8.
Attempting to incorporate this waypoint with only three points causes the movement to stop at the middle point. ( The point I want to address. )
Thank you

okay I understand. I'll have to figure this out myself first to be honest. There is some documentation for Moveit 1 here, which was posted by @andyze on ROS Discourse.
Doing this through the ros2_control Joint Trajectory Controller should be relatively simple, but Moveit has to take collision avoidance into consideration. I'll let you know once I figure it out.

Okay I managed to get the sequence action server up and running at least.
Thank you for adding this issue @SUUHOLEE , very much appreciated. I'll try to provide you with an example as soon as possible.

yes I'll try to provide you an example. In a nutshell:

Moveit supports sequences motions using the Pilz motion planner: https://moveit.picknik.ai/main/doc/how_to_guides/pilz_industrial_motion_planner/pilz_industrial_motion_planner.html#sequence-of-multiple-segments
They provide an action server to interface the Pillz motion planner
You can e.g. interface this action server from Python

Thank you for always being willing to answer my questions.
Have you had a chance to resolve the issue? I tried looking for relevant documentation and attempted to solve the problem myself, but I found it difficult to find any clues or solutions.
Therefore, I'm reaching out to you again for assistance. Thank you.

hi @SUUHOLEE , really sorry for the delay. Will have significantly more time next week! Will attempt to close a bunch of related issues then. Hope this is okay.

okay let me revisit this topic, just got some big chunk of work off my table!

hi @SUUHOLEE , I added a demo for you in a dev- branch. Please let me know if this works for you
https://github.com/lbr-stack/lbr_fri_ros2_stack/tree/dev-humble-sequenced-motion/lbr_demos/lbr_demos_moveit_python

Thank you for your response.
After trying to run it as mentioned in the link provided:
https://github.com/lbr-stack/lbr_fri_ros2_stack/tree/dev-humble-sequenced-motion/lbr_demos/lbr_demos_moveit_python
It seems that the inverse kinematics cannot be solved.
Even after several attempts, it appears that MoveIt struggles to solve the inverse kinematics.
What I'm looking for is similar to what is described in the following link, where I want to set multiple points to be passed through sequentially:
https://moveit.picknik.ai/main/doc/how_to_guides/pilz_industrial_motion_planner/pilz_industrial_motion_planner.html#sequence-of-multiple-segments

The demo I provided uses the Pilz planner from the link you provide. Maybe try moving the robot into slightly different initial configuration first before you call the demo. Otherwise, if you could figure out why the IK fails that would be great!

Thank you for your prompt response.
I am using the med14 robot, and I will try the method you provided and let you know the results.
Thank you.

no worries. Sorry for the massive delay!
You can git pull the changes to your local repo and run
ros2 launch lbr_bringup bringup.launch.py model:=med14 moveit:=true

and
ros2 run lbr_demos_moveit_python sequenced_motion

Thank you for providing helpful responses and test code.
Even after modifying kinematics_solver_timeout = 1.0 in
lbr_fri_ros2_stack/lbr_moveit_config/iiwa7_moveit_config/config/kinematics.yaml and executing sequenced_motion, I still see the message [sequenced_motion]: Waiting for /lbr/sequenced_move_group..., indicating that the inverse kinematics is not being solved. ( Before executing it on Med14, I tried running it on iiwa7.)
Do you have any idea why this problem might be occurring?
(When I execute the command 'ros2 run lbr_demos_moveit_python sequenced_motion', I get an error saying 'Package 'lbr_demos_moveit_python' not found'. To resolve this, I downloaded the Python code and tried running 'python3 sequenced_motion.py'. Is this causing the error?)

so you will have to checkout the dev-humble-sequenced-motion branch. Here is a full example:

Follow the install instructions

mkdir -p lbr-stack/src && cd lbr-stack
vcs import src --input https://raw.githubusercontent.com/lbr-stack/lbr_fri_ros2_stack/humble/lbr_fri_ros2_stack/repos.yaml
rosdep install --from-paths src -i -r -y

Checkout required branch

cd src/lbr_fri_ros2_stack
git checkout dev-humble-sequenced-motion
cd ../..

Build

colcon build --symlink-install --cmake-args -DFRI_CLIENT_VERSION=1.15 --no-warn-unused-cli # replace by your FRI client version

4.Run the demos.
Please feel free to keep this issue open, as it is not solved in the humble branch yet.

It seems that there was an error when using the default humble instead of the dev-humble-sequenced-motion branch.
After testing with the dev-humble-sequenced-motion branch, I confirmed that it runs without errors.
Thank you for always providing helpful and detailed responses.

awesome! Let's keep this issue open until solved in humble branch. Thank you for all the valuable feedback. Please feel free to open other issues as needed.


Shortest arc rotation animation improvements and upgrade notes

After #6965, spin effect animations like "Spin to Rome" or "Rotate around Rome", as shown in the animation.html example, do not animate any more. This pull request updates the example and adds upgrade notes to restore the previous behavior.
This pull request also improves the situation after rotating beyond 360 degrees, by normalizing the rotation to an angle between -180 and 180 degrees at the end of an animation. The result of this can be seen in the animation example after rotating. Previously, the button of the Rotation control did not disappear. Now it does.

Updated, now ready for review.

How long will it be until this patch lands in a release? Trying to decide if we need to serve this patch from our server or if it will be downloadable via the CDN soon enough.

I just published v4.3.0-beta.2, both for the ol and openlayers packages. It should also be available on cdnjs.com within the next view hours.


[Wip] Slimmer JPropertyKeyedCollection

A simpler solution, and one I have been thinking about for a while is not tracking keys in a dictionary until someone actually uses them.

Hmmm
Writing JSON doesn't care about the key - it is looping over collections and writing the content, but I guess parsing will always care because of duplicate keys, and having to check for that by the key.

I'm going to close this. If you make further progress on the issue I raised above you are welcome to submit a new PR.


I managed to make it work after commenting out the flavors in app/build.gradle

I managed to make it work after commenting out the flavors in app/build.gradle
    // productFlavors {
    //     debug {
    //         dimension "default"
    //         applicationIdSuffix ".debug"
    //     }
    //     staging {
    //         dimension "default"
    //         applicationIdSuffix ".staging"
    //     }
    //     prod {
    //         dimension "default"
    //     }
    // }

The output was rightfully built in build/app/outputs/apk/debug/app-debug.apk.
Of course I'm not commiting these to source control. It's just until there isn't a fix.
Not a definitive solution, but at least I can work.

I have no flavours at all in my build.gradle.  This may be 'a' cause of this issue, but it is not 'the' cause.   We really need a fix on the all the critical stability issues for this platform.
Originally posted by @ArtfulDodgerB92 in https://github.com/flutter/flutter/issues/44796#issuecomment-612299477

I'm going to assume this was opened accidentally and close this issue.
If you have an actual issue to report, kindly file a new issue and provide the information requested in the template. If you are going to reference a closed issue, you should still provide the information requested in the template.
Closing as this issue doesn't provide any information.
Thank you


[card-group]: Refactor to use subgrid in favor of sameHeight

Related Ticket(s)
Closes #11998
Description
This is a refactoring of card group to make use of CSS subgrid instead of the Javascript sameHeight logic on all the pieces of the card group.
Changelog
Changed

Use CSS subgrid for layout out the card elements within a card group

I've put together a couple demo pages showing the implications of this change.

using sameHeight
using subgrid

Card contents width dependent on body text
If we remove the card's body text something is getting squished. Seems like a rule inherited from card about justify-content causing this.

I don't know that we need to subgrid all the way down into the main slot
After fixing the card width issue above, it's easier to see that the tags will never be able to line up in this scenario due to the grid lines. This would also likely end up happening if we had multiple
 tags in a card as well.

We should make sure grid placement is more explicit
Right now all items just get placed into whatever grid cell is open next. If we are more explicit with our placements we'll get a better result
Before:

After:

The easiest way to do this might be to wrap all our slots in additional divs:
Current:

  <slot name="image"></slot>

      <slot name="eyebrow"></slot>
      <slot name="heading"></slot>

        <slot></slot>

      <slot name="pictogram"></slot>
      <slot name="footer"></slot>

Suggested:

<slot name="image"></slot>

<slot name="eyebrow"></slot>

<slot name="heading"></slot>

        <slot></slot>

<slot name="pictogram"></slot>

<slot name="footer"></slot>

In this way, the interaction with the grid is limited to the card-group and the card-group-item. Styles on slotted content shouldn't break our grid's alignment. Additionally, we can apply the necessary spacing to the wrapper divs. With spacing applied to those internal elements we can also hide them with use of :has()
:host(c4d-card-group-item) {

  [part="heading-wrapper"] {
    margin-bottom: 64px // Required spacing below heading
  }

  :not(:has([slot="heading"])) [part="heading-wrapper"] {
    display: none;
  }

}

Thanks for the updates, alignments are looking much better now.
The pictogram one still has some weirdness, though:

Pictograms seem to disable eyebrows
Pictograms seem to create their own footer cta icons
The body text is double-wrapped in p tags

We should be looking pretty good now. Waiting on the Storybook, but here is a rundown of the feedback so far.

This is great, thanks @m4olivei! Just some spots to use tokens instead of hard-coded units.

All set there, thanks @kennylam. Fixed in https://github.com/carbon-design-system/carbon-for-ibm-dotcom/pull/12063/commits/2e3e15b9bf03aa45fe62b482fba442a54724045f

I've put together a couple demo pages showing the implications of this change.

These are great, thanks @andy-blum .

If we remove the card's body text something is getting squished. Seems like a rule inherited from card about justify-content causing this.

Yep, fixed in https://github.com/carbon-design-system/carbon-for-ibm-dotcom/pull/12063/commits/3ab3d81e1419f0501648c4d4b608171c78ec9a0d

I don't know that we need to subgrid all the way down into the main slot

This whole thing threw me off at first too. Originally I was trying to declare a subgrid on a grandchild element to the grid container and expecting it to like get placed on the nearest grid ancestor. I realized pretty quickly that it doesn't work that way. The child, which was just a regular old grid item gets placed in the parent grid first, in the first row and column. Then the grandchild getting grid-template-rows: subgrid makes no sense, b/c its immediate parent is just a grid item of the grandparent ... not a grid container. As it turns out, you have to have each element in the tree except for the leaves be display: grid. And we have to start up at the element that wraps all of our items, then go all the way down. You can effectively take out some child elements using display: contents, but that's not always appropriate.

We should make sure grid placement is more explicit

Resolved in https://github.com/carbon-design-system/carbon-for-ibm-dotcom/pull/12063/commits/29f5b4f34421320fa02553b02e2dd30cfab365ef also in https://github.com/carbon-design-system/carbon-for-ibm-dotcom/pull/12063/commits/b72b45c7d28cb658d67f1eb20405267fe27371b9 . The wrappers work well.
The only thing is, I made changes to the card markup, which is widely used, so we'll need to be careful to regression test.

The pictogram one still has some weirdness, though:
Pictograms seem to disable eyebrows

Fixed in https://github.com/carbon-design-system/carbon-for-ibm-dotcom/pull/12063/commits/b72b45c7d28cb658d67f1eb20405267fe27371b9

The pictogram one still has some weirdness, though:
Pictograms seem to create their own footer cta icons

I haven't been able to reproduce this one.

The pictogram one still has some weirdness, though:
The body text is double-wrapped in p tags

This is also the case on main. There is some code that is responsible in updated. Haven't touched that here, so I want to say it's out of scope for this.

Looks like the only remaining alignment issue is some extra margin thrown on .cds--card__copy when pictograms are involved.

Looks like the only remaining alignment issue is some extra margin thrown on .cds--card__copy when pictograms are involved.

I'm not sure that's worth fixing TBH. Pictogram margins appear to be intentionally unique. I don't think it's worth trying to make them conform in the mixed card type case, when my read is that Pictograms are meant to appear in the card-group exclusively with other pictograms.

We do need to make sure the spacing is correct when pictograms are used, however.


compiling problems because of kconfig on mac os sierra

When I want to compile using make menuconfig , the compiler throws the following error:
./zconf.hash.c:166:1: error: conflicting types for 'kconf_id_lookup'
kconf_id_lookup (register const char *str, register size_t len)
^
./zconf.hash.c:33:31: note: previous declaration is here
static const struct kconf_id *kconf_id_lookup(register const char *str, register unsigned int len);
                              ^
1 error generated.
make[1]: *** [zconf.tab.o] Error 1

Could you please check the suggestions mentioned here and see if they fix the issue?
https://github.com/pfalcon/esp-open-sdk/issues/236#issuecomment-271697219

I had this same issue. I modified the declaration in zconf.hash.c to use size_t instead of unsigned int, and that got it to build.

gperf 3.1 changed the type signature for this function, for 64-bit compatibility reasons.
A permanent fix is pending and will be in master soon.
In the meantime you can delete this entire line from zconf.gperf and it will fix the problem:
https://github.com/espressif/esp-idf/blob/master/tools/kconfig/zconf.gperf#L12
(Editing zconf.hash.c will work until you make clean, because this file is generated from zconf.gperf.)

same problem


Generate build to be published in npm

At the moment I'm generating the build but when I link the project in local with npm link I get an error Invalid Hook
I've checked the suggestion by FB team, and there is no mismatch version and no duplicated react. The thing is coming from MapContainer which is coming from an external library, but if I copy and paste the build.js into my project's src and just import it as a component, it all works. So the problem might be an npm link or something around. I'm not an expert in this kind of issue as this is my first "library" that I would like to publish to npm.
I appreciate any help. Here is also a test project with instructions to link both of them

solved


Add range methods to TreeMap

Since the TreeMap structure guarantees an ordering for its contents, it would be very useful to have front popFront, back, and popBack methods to get the largest or smallest items out of the container.

I see that d44cb6a6dde18de835ac88b82ce389a8e4a9d85c added front and back methods which return values, which I guess would correspond to the smallest and biggest keys.
I think for map-like types it would be better to have distinct iterator constructors, like byKey and byValue to facilitate this.


Modify Scoped User System

Details
Update the scoped user system to be attached per page instead of a tree like structure. User scopes are baked into the page settings, and each element that can use a scope will access that information from a reference to a scope object.
The scope object will need to be initialized and/or otherwise updated depending on how it is used. For a local user scope, it still needs to be explicitly defined in the page. For form scopes, the for that modifies the scope needs to be attached to the scope itself. Multiple forms could be attached to the scope and all forms should update if a single one updates.
Draft UserScope object
public class UserScope : DataObject<Guid>
{
    public bool LocalUser { get; set; }
    public CustomPageSettings PageSetting { get; set; }
    public Guid PageSettingsId { get; set; }
    public string ScopeName { get; set; }
    public List<CustomComponentBase> AttachedListeners { get; set; }
    public List<CustomComponentBase> AttachedAssigners { get; set; }
}

Where listeners would listen to user updates and assigners would update the selected user for that scope.

Rough implementation for this is done. Check the UserScope object.


fix(#154): Removes the tilde as a prefix to camel -> MBeans

tilde unnecessary for sorting as the node is added last to its parent and so is in the correct location despite its name

@phantomjinx Is that all we need to fix the issue?


Split the configuration files

Fixed here https://github.com/Jannik-dev/nak-transferleistung-template/commit/95983b97521f2b4af96de040c4537e5103e7ff2c


Fix rounding on y-axis labels

The following is a result of some overzealous rounding:

This should instead show 4.5 billion, 4 billion, 3.5 billion, 3 billion etc. In fact, it would probably be better to show 0.5 billion instead of 500 million here.

Looks like d3-format is the way to go.

Fixed in 51e6258.


R5: Testing, Validation, and API Prefix Addition

As a developer,
I need to test the Flask-RESTX implementation and add '/api' prefix to all REST API endpoints,
So that I can ensure the application functions as expected, maintains high test coverage, and the API is clearly separated from UI routes.
Details and Assumptions

Tests must confirm that the Flask-RESTX refactor and new API structure work without reducing functionality.
Adding '/api' to the endpoint paths helps delineate API routes from front-end routes.

Acceptance Criteria
Given the Flask-RESTX refactored API and modified routes
When I run the full test suite
Then all tests should pass, the coverage should be at least 95%, and all API routes should function correctly with the '/api' prefix

#83


storage: do not panic from exported rev var

Since we now export the start revision to clientv3 package, if a client
passes a bad revision (like 5 when the current revision is 1), it will
panic the whole node. We should print out warning message instead.

/cc @xiang90 @heyitsanthony Please review. Thanks.

@heyitsanthony Just fixed. PTAL. thanks!

lgtm

thanks. merging in green lights.

I think it is better for us to do this at API layer? So API layer checks the specified rev vs current rev, api will never pass in an invalid rev?

@xiang90 Ok I will rework on this. Thanks.

@xiang90 None of our Watch APIs has error in return type. Can I have some kind of error flag in WatchResponse? Not sure about what's the best wayt to prevent clients from passing bad start rev.

func (w *watcher) Watch(ctx context.Context, key string, rev int64) WatchChan {
	curRev := 0 // how we want to get this...
	if rev > curRev {
		panic("can't watch past sync revision")
	}
	return w.watch(ctx, key, "", rev)
}

Right. We have a few todos for watcher. Returning error is one of them. I am not sure right now.

@xiang90 Ok, I will think more about this. Let's discuss on Wednesday. Thanks.

Closing via https://github.com/coreos/etcd/pull/4612.


chore(deps): remove array subset dependency

A fancy package that it's not really necessary.

I wish that assert was part of codeception or phpunit.

it was part of phpunit, but removed on version 8 🤷🏻♂


rsync 3.1.2

Update to 3.1.2 and use the new upstream rsync-patches tarball.

I think we'd be happier retaining the existing method of patching. In-formula patching in the manner you've applied is a little problematic in terms of not being obvious what is happening and why, and can potentially fail silently.
Ideally the patches required should be vendored in https://github.com/Homebrew/patches and then that link used here, with an explanation above each patch as to why it is required, if you wouldn't mind. Cheers!

There's plenty of precedent in the existing set of Library/Formula for the way I've done this, so unless those all need to be overhauled (issue link?), I'm not sure why this isn't sufficient. Also, since the patches are now distributed in bulk by upstream, there's no reason to expect silent failures.

The only core usage I can find like this is fakeroot which is kind of special because the patch is written into the formula inline rather than being under an __END__ block or fetched externally. That's not a ton of precedent.

Also in llvm33.rb and glib.rb, but ok.

@DomT4 This should be added to brew audit if it's disallowed.

Since the required method is less efficient and will involve more on-going maintenance than what is proposed here, I'll leave this to someone else who sees the wisdom in a less efficient, more maintenance intensive approach.

less efficient, more maintenance intensive approach

Which is also, as pointed out, more likely to fail in confusing ways for end-users.

@mikemcquaid Since these patches are distributed and signed by upstream, part of their commit, release, build, and lsb packaging, all of which anticipate an in tree "patches" directory, I cannot see how versioning and distributing them separately on a homebrew website makes any sense unless homebrew's model of the world is simply broken.

@ilovezfs When they can be applied with a patch do block: I'd agree.

@mikemcquaid Is a patch do block possible/permissible within the install method with a file:///$PWD/patches url key or some other magical key for relative paths?

No.

@mikemcquaid Is there a subclass of abstract download that is able to re-use the same tarball as other patch do blocks while only selectively extracting a single file?

No, we need direct URLs to individual patches, sorry.

@mikemcquaid Would that be an enhancement you'd be interested in having?

@ilovezfs Probably not unless there 3+ projects that use these similarly and have no other way of downloading these patches (e.g. from their version control system).

@mikemcquaid Seems like a rather unfortunate waste of the flexibility of these long-standing archive formats.
For instance:
tar -t --include '*hfs-compression.diff' -f rsync-patches-3.1.2.tar.gz

 tar -x --strip-components 2 --include '*hfs-compression.diff' -f rsync-patches-3.1.2.tar.gz

Given infinite resources: yes, it'd be nice to support that.

@mikemcquaid It depends on https://github.com/Homebrew/homebrew/pull/47614

@mikemcquaid Changed the name from @file to @extracts and @extract to avoid collision with the preexisting "files" method and allow for a single patch block to handle more than one at time, as you suggested. Also, multiple instances of @extracts and @extract are supported.

@mikemcquaid With apply now merged, is there a way for you to re-trigger these tests?

@BrewTestBot test this please

Pushed, really great work here @ilovezfs.

@mikemcquaid Thanks! :)


CASMINST-5757 Revert "CASMMON-208: Automate prometheus, grok exporter and grafana gets  instantiated automatically on PIT node."

Reverts Cray-HPE/csm-rpms#674

The revert in pit-init effectively promotes 1.2.38 to the latest version.
[518]rusty@C02F43JEMD6P:~/gitstuffs/cray-shasta/pit-init> git log
commit 121576153bb18481870568133f2014a66e07ca0b (HEAD -> main, origin/main, origin/HEAD)
Author: Russell Bunch<EMAIL_ADDRESS>Date:   Tue Jan 3 10:47:01 2023 -0600

    CASMINST-5757 Revert "CASMMON-208: Automate prometheus, grok exporter and grafana gets instantiated automatically on PIT node." (#62)

    Revert "CASMMON-208: Automate prometheus, grok exporter and grafana gets instantiated automatically on PIT node. (#60)"

    This reverts commit cae73f85c993d3b2f109bf907afea6c0a0d2718b.

commit cae73f85c993d3b2f109bf907afea6c0a0d2718b (tag: v1.2.39, MTL-2048)
Author: shreni123<EMAIL_ADDRESS>Date:   Wed Dec 14 00:52:33 2022 +0530

    CASMMON-208: Automate prometheus, grok exporter and grafana gets instantiated automatically on PIT node. (#60)

    * CASMMON-208: Automate prometheus, grok exporter and grafana gets instantiated automatically on PIT node.

    * Apply suggestions from code review

    Signed-off-by: Russell Bunch<EMAIL_ADDRESS>
    Signed-off-by: Russell Bunch<EMAIL_ADDRESS>    Co-authored-by: Rambabu Bolla<EMAIL_ADDRESS>    Co-authored-by: Russell Bunch<EMAIL_ADDRESS>
commit 99fd34c258b9af82a64ac18bcbd0b577943e19f4 (tag: v1.2.38)
Author: John Heemstra<EMAIL_ADDRESS>Date:   Thu Dec 8 15:06:44 2022 -0500

    CASMTRIAGE-4671 CASMTRIAGE-4672: nix the ncn-m001 hardcode (#59)

    The pit isn't really m001, so stop pretending it is.


examples: add usb-i2c mctp app

Overview
Add a sample libtock-rs app that allows a host machine without exposed I2C/SMBus capabilities to communicate to an MCTP endpoint.
The following topology is used:
[Host PC] <-- UART --> [Usb-I2C Bridge Device] <-- I2C --> [Target Endpoint]

This app operates by first waiting for an MCTP request packet to be sent over UART from the host, which is then forwarded to the target endpoint (based on the target address) through the I2C bus. The endpoint must then master the I2C bus and write a response back to us, as we wait in target mode (Note: MCTP mandates writes only).  This is then forwarded to the host machine via UART.
A sample use-case  can be to communicate with an SPDM responder that uses  MCTP/SMBus/I2C, directly from the host machine.
Host app requirements
The host app must attach a small packet header (metadata) that wraps the data message, the packet formatting is detailed in the rust-docs for the app. It must also parse the same packet upon reception of data.

@alistair23

ping! this is ready to merge


OpenDefi/MVP-4110+4111

[x] Describe the purpose of the change

Empty inbox\ Dashboard page redesign
Information bar for history list

[ ] Create test cases for your changes if needed
No need

[x] Include the ticket id if possible (Collaborator only)
MVP-4110 MVP-4111

seems it takes a pretty long time to show the empty inbox view

should we remove work 'inbox' in empty view?

Great catch~.
And the loading speed depends on the endpoint response speed FYI.


[SERF-1594] Convert broker urls to string slice explicitly

Description

In this PR we fix a problem with converting the string representation of kafka.broker_urls into a slice of strings. The issue has been spotted while testing the web-analytics-ingestion service.
P.S.: this is what @fotos was asking about one day, but I wrongly checked the wrong configuration 🤷♂
Checklist

[x] Prefixed the PR title with the JIRA ticket code
[x] Performed simple, atomic commits with good commit messages
[x] Verified that the commit history is linear and commits are squashed as necessary
[x] Thoroughly tested the changes in development and/or staging
[ ] Updated the README.md as necessary

Related links

SERF-1594
https://github.com/scribd/web-analytics-ingestion/pull/140

@fotos

Is the ENV comma or "whitespace" separated? Based on the test, I think it's whitespace separated? Is this the default?

it is the only way to get a slice of strings out of a string with the viper API. It is converted from comma-separated to whitespace-separated in terraform. If we want to make this consistent, we can do this with a comma, but it will require some adjustments in terraform code.

it is the only way to get a slice of strings out of a string with the viper API.

Sounds reasonable.
Should we document that to read slices from the environment the string must be comma-separated, in the go-sdk README?


Prevent thread relating functions from calling dllmain

This wasn't on purpose, but not doing this has given us compatibility to be able to also load other, existing dlls with the launcher that aren't mods. I don't think there is a reason in which we would need to restrict this functionality

Alright


Add coveralls neo3.1

Tests pass on circle ci :)
https://circleci.com/gh/Financial-Times/alphaville-series-rw-neo4j/35

Changes Unknown when pulling a967bfef317c1aee1505b5aeebf01fc69e45caae on AddCoverallsNeo3.1 into ** on master**.

Still passing
https://circleci.com/gh/Financial-Times/alphaville-series-rw-neo4j/36

Changes Unknown when pulling fd91f4365c25473dca47de59c12d4e46627e9f0b on AddCoverallsNeo3.1 into ** on master**.


There is no index.js

From README.md:

Import the element definition into your HTML page:
<script type="module"<EMAIL_ADDRESS>
But there is no index.js file. Looks like it should be mwc-icon.js.
This applies to all packages.

True. sorry about the confusion. The filename should be the actual .js filename for the component. The Readme and docs need to be updated. If someone wants to assign that to me. I'll take care of it. In the meantime, use:
<script type="module"<EMAIL_ADDRESS>


⚠ Bofrost.at has degraded performance

In e661ca8, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1096 ms

Resolved: Bofrost.at performance has improved in 4ad5b22.


FIX: Incorrect supported proof type in Credential Issuer Metadata #1

Fixes #1

I accidentally merged this PR to master (as you specified) instead of develop and had to drop that commit from master and re-commit manually to develop.

I'm sorry for that mistake. I will use develop next time. thanks


Determine practical parameters for generating RPs

When generating new RPs, we should investigate what parameters would lead to output at a similar level of detail as the USPS data.
In particular, what values for mask_width and threshold would yield

Approx. 1.0 mile distance between nearest RPs
Approx. 40,000 points for California
?

Update: mask_width 6 pixels and threshold 0.4 ppp results in ~600,000 points for the United States, with 45,000 in Texas and ~20,000 in California. Rural areas appear somewhat under-represented with these parameters.

@tetraptych just to clarify, this is what we are currently implementing despite the somewhat under-representing rural areas?
if we wanted better representation, would you adjust mask-width or threshold first?

I ran again with 8 pixels and 0.05 ppp and uploaded the results to MapBox. This seems much better for the less dense parts of the country. The USPS data has more points following roads in these areas. These are overwhelmingly are points representing < 5 people.

Nice -- @tetraptych is this what's in QA right now?

Yep! I'm pretty happy with how things look now (and the performance for the entire US). It's easy enough to re-generate the points if we have strong feelings either way, but I worry we'll get into a #445 nightmare if the threshold is too low.

@viviandien, how do you feel about using the current RPs for the soft launch?


REST API: Controllers and Views

This PR adds JSON Controllers, Views, and ControllerTests for the upcoming REST API. It also stubs out a new Guardian pipeline that's purposefully not implemented in this PR. The next PR will focus on implementation for creating / revoking the JWTs associated with the ApiToken schema by implementing this Guardian pipeline.
One thing we should consider before publishing this REST API is whether or not we want to change the port_type and port_range format. Currently, they must be specified like so:
port_type: "tcp" (lower-case only)
port_range: "1 - 65000" (integer range as a string)

I propose we consider allowing case-insensitive port_types and we split up the port range into port_range: {start: 1, end: 65000} to make it easier for other systems interacting with the API to parse / use.
cc @conectado

Pull Request Test Coverage Report for Build b6e8f02cf4848f8c405fbcb9bf3b04d741155501-PR-1148

0 of 57 (0.0%)  changed or added relevant lines in 10 files are covered.
557 unchanged lines in 71 files lost coverage.
Overall coverage decreased (-33.5%) to 33.12%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

apps/fz_http/lib/fz_http_web/auth/www/error_handler.ex
0
1
0.0%

apps/fz_http/lib/fz_http_web/router.ex
0
1
0.0%

apps/fz_http/lib/fz_http_web/auth/api/error_handler.ex
0
2
0.0%

apps/fz_http/lib/fz_http_web/controllers/fallback_controller.ex
0
2
0.0%

apps/fz_http/lib/fz_http_web/views/changeset_view.ex
0
2
0.0%

apps/fz_http/lib/fz_http_web/auth/api/authentication.ex
0
5
0.0%

apps/fz_http/lib/fz_http_web/controllers/api/configuration_controller.ex
0
5
0.0%

apps/fz_http/lib/fz_http_web/views/api/configuration_view.ex
0
11
0.0%

apps/fz_http/lib/fz_http_web/controllers/api/user_controller.ex
0
13
0.0%

apps/fz_http/lib/fz_http_web/views/api/user_view.ex
0
15
0.0%

Files with Coverage Reduction
New Missed Lines
%

apps/fz_http/lib/fz_http/connectivity_check_service.ex
1
95.65%

apps/fz_http/lib/fz_http_web/views/error_view.ex
1
0%

apps/fz_http/lib/fz_http/users/user.ex
1
93.33%

apps/fz_http/lib/fz_http_web/endpoint.ex
1
0%

apps/fz_http/lib/fz_http/validators/openid_connect.ex
1
0%

apps/fz_http/lib/fz_http/oidc.ex
1
12.5%

apps/fz_http/lib/fz_http/telemetry.ex
1
84.38%

apps/fz_http/lib/fz_http/mfa/method.ex
1
88.89%

apps/fz_http/lib/fz_http_web/controllers/root_controller.ex
1
0%

apps/fz_http/lib/fz_http_web/live/rule_live/index_live.ex
1
0%

Totals

Change from base Build 2d9c2b79b4506b27bba1acb7db490817f571220e-PR-1155:
-33.5%

Covered Lines:
620

Relevant Lines:
1872

💛  - Coveralls

@akrousset This piece is ready for review. I've updated the description to guide what you should expect from this PR.

Seems like we're getting some intermittent test failures I'll need to debug.