text:
Added disable_service_types option to protobuf-ts/plugin for disabling service metadata generation

Summary of changes
Small change to introduce optionality in generating service metadata for proto messages. I have named the option disable_service_types.
Precaution
I am having difficulty understanding how to run tests after following the guide provided in CONTRIBUTING.md. I was not able to run tests successfully against packages/plugin, as I have an error that @protobuf-ts/plugin-framework is missing. I made sure to build and test the plugin-framework, but still I encounter issues when trying to run tests for the plugin package. Any help in contributing is appreciated, I'd like to make sure I'm not introducing bugs into this library. Thanks everyone.

Hey @timostamm I was wondering if the option name disable_service_types was okay with you. The reason I pluralized "types" and added some extra spacing between each word was for clarity sake when reading. I did the same for any variables/keys of objects, I tried to keep the code as cohesive as possible with the conventions that have already been established within the project.

I am having difficulty understanding how to run tests after following the guide provided in CONTRIBUTING.md. I was not able to run tests successfully against packages/plugin, as I have an error that @protobuf-ts/plugin-framework is missing. I made sure to build and test the plugin-framework, but still I encounter issues when trying to run tests for the plugin package.

This is likely caused by lerna, the tool to link the packages within this monorepo. Please try to run make lerna-bootstrap in the root directory of the project. In general, just running make should runs all builds and all test, but you will need to have all build tools mentioned installed.

This is also a feature that we need, since we only are using protobuf-ts to generate the TS types and encoding/decoding functions.

Released in v2.7.0.

authors: ColinLaws tannera-cargill timostamm

repo: timostamm/protobuf-ts


text:
Get current brightness, temperature and power state

Hello,
Thanks again for writing this library @timrogers. I was looking for something to help me write a Stream Deck plugin and this seems like a good starting point.
I've added the following functions to the driver that people may find helpful:

getBrightnessInLumen
getTemperatureInKelvin
getPowerState
toggle

I've also updated the CLI to include a litra-toggle command and made the brightness/temp commands return the current value if no argument is passed into them. I did not change brightness percentage command or include a power state command.
Kudos to @abergmeier as this thread  gave me what I needed. I managed to figure out the format of temperature values after a few hours of staring at the two bytes being returned (comments in the temp function).
Let me know if you need anything else from me to get this merged 🎉
Ref #42

@hhaidar Thanks! This is great ❤
I'm actually already working on a PR locally for checking the current on/off state which I will push in the next couple of hours.
I'll push that up and will take a look at this, and we can figure out how to move forward. Thank you for taking the time to contribute.

@hhaidar Could you also tick the box to allow maintainers to update your PR? ☺

Fixes #42.

@timrogers thank you for the quick feedback, I will rebase and squash into 1 comment at the end if that's alright

@timrogers thank you for the quick feedback, I will rebase and squash into 1 comment at the end if that's alright

Sure! Just ping me once you're ready for re-review.

@timrogers I'm actually ready now, all issues should be resolved I think.

Hello friends, I first want to say I am grateful for all the hard work in reverse engineering the litra api! I am a windows user who has been taking tips from all this conversation to construct python scripts that will increment/decrement temperature and brightness on the stream deck.
I was excited to see that someone had figured out a way to get the current state of the device as my current scripts utilize reading/writing to a text file as a psuedo-database for storing the current temp or brightness. I wish I could instead read the current status of the device and increment/decrement brightness/temp
I wrote the following python script which will do such a thing for brightness and temp, In the example for brightness, what it does is read in a txt file which has the current brightness as a hex value, then it increments/decrements the hex value by a "1C" hex step and writes the new value back to a file. it then takes that new hex value and processes it to be injected into a hidapitester.exe command which sends the correct hex output string to make the light adjust accordingly.
The script has a static path for the brightness.txt file and uses a command that specifically targets one of two of my litra lights:
import os
import subprocess
def adjust_and_invoke_hidapitester(increment):
# Set the file path
file_path = "C:/Users/jortega/Documents/Stream Deck Bashes/Litra Stuff/left_current_brightness.txt"
# Read the current brightness value from file (as hex)
with open(file_path, 'r') as file:
    current_brightness = file.read().strip()

# Increment or decrement the hex value by "1C"
if increment:
    current_brightness = hex(int(current_brightness, 16) + 0x1C)[2:].zfill(4)
else:
    current_brightness = hex(int(current_brightness, 16) - 0x1C)[2:].zfill(4)

# Validate the current brightness range
if int(current_brightness, 16) < 0x1C:
    current_brightness = "001C"
elif int(current_brightness, 16) > 0xFF:
    current_brightness = "00FF"

# Write the new current brightness back to file
with open(file_path, 'w') as file:
    file.write("0x" + current_brightness)

# Split the base 16 value into two 2-character strings
split1 = current_brightness[:2]
split2 = current_brightness[2:]

# Construct the command for hidapitester.exe
command = (
    'hidapitester.exe --vidpid 046d/c900 --usagePage ff43 --open-path '
    '"\\\\?\\HID#VID_046D&PID_C900&Col02#8&1e2a4b18&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}" '
    f'--send-output 0x11,0xFF,0x04,0x4F,0x{split1},0x{split2}'
)

# Execute the command with subprocess
subprocess.run(command, shell=True)

def main():
# Set the increment flag to True for incrementing the brightness
increment = True
# Call the function to adjust the brightness and invoke hidapitester.exe
adjust_and_invoke_hidapitester(increment)

if name == 'main':
main()
So I directly run this script on an System > Open command on Streamdeck button and it works. If you want to decrement, you just change the value of increment in the main() function to False. Temperature follows the same idea of having a base 16 value except instead of being a base 10 value between 20-250, temperature is 2700-6500 (source: https://www.reddit.com/r/LogitechG/comments/sacz2x/comment/ixtez4q/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button)

source: gharchive/pull-request

authors: hhaidar jaaortega timrogers

repo: timrogers/litra

license: MIT

license_type: permissive

license_source: github-api


text:
Store configuration information in the same SPI flash that stores the gateware

It would be good to store configuration information in the SPI flash that stores the gateware.
Both the Opsis and Atlys have similar SPI flash available that is much bigger then required for the gateware.
On the Opsis, the SPI flash will also be storing two firmware for the FX2 as well. So we need some type of "file system" I guess?

Seems related to https://github.com/timvideos/HDMI2USB-misoc-firmware/issues/111.
We first have to define memory map of the flash: bitstream / FX2 firmware1 / FX2 firmware2 and user data.
For user data, we can try to keep things simple (store raw data) or use a file system. If we choose to use a file system, IIRC something similar exists in ARTIQ.

I was suggesting we spit the flash into 2 parts, bit stream and "user".
Then put a simple file system on the user section which lets us store the
fx2 firmwares, user configs and maybe a logo or two?
On 15 Oct 2015 12:46 a.m., "enjoy-digital" notifications@github.com wrote:

Seems related to #111
https://github.com/timvideos/HDMI2USB-misoc-firmware/issues/111.
We first have to define memory map of the flash: bitstream / FX2 firmware1
/ FX2 firmware2 and user data.
For user data, we can try to keep things simple (store raw data) or use a
file system. If we choose to use a file system, IIRC something similar
exists in ARTIQ.
—
Reply to this email directly or view it on GitHub
https://github.com/timvideos/HDMI2USB-misoc-firmware/issues/113#issuecomment-148054319
.

Is the overhead of a filesystem worth it? Could you have "partitions", with a simple header in the first page of the flash that describes the layout?

The first page has to be what ever Xilinx wants it to be for the FPGA.
The last page can be used for such a layout. That layout is pretty much a filesystem though :)
The simplest filesystem is just a concatenated list of;
filename (null terminated string)
filesize (32bit int)
pointer to filedata (pointer to byte array // offset)

Yeah. That sounds good to me.

@fallen - FYI

source: gharchive/issue

authors: enjoy-digital mithro shenki


text:
Radio group field is not responsive

Description
When using the radio group field button variant and you resize the sidebar the button does not resize with it.
Video: https://www.loom.com/share/1366454af483429d9596d27052c37b26
cc @spbyrne

The whole sidebar is not responsive, as it was just set loose of it's default fixed with, same happens with other components like buttons and such.

There are some low-level issues with the way this is handling refs. Tabling the animation challenges and keeping it simple will allow us to move forward quickly

As far as I can tell we are not using this UI anymore

authors: DirtyF jeffsee55 logan-anderson

repo: tinacms/tinacms


text:
Use "null" for default "data" value in getStaticProps in our examples

As a user (dev) I want code-examples to initially set data as null, not {}, so that when I implement document-creation, I can easily avoid 500 errors when going to production.
Expected Outcome:

All starters should initially set "data" as null, not {}

E.g: This needs to be updated https://github.com/tinacms/tina-docs-starter/blob/main/pages/docs/[filename].js#L88

Docs should refer to initially setting data as null, not {}
tina init should initially set data as null, not {}

Notes:
@perkinsjr Ran into an issue where on Vercel, when we added a new page, it was giving a 500 error when being brought to that new page address (until the new build completed).
The issue was that the page layout was checking for data, which was still truthy:
export default function Home(props) {
  // data passes though in production mode and data is updated to the sidebar data in edit-mode
  const { data } = useTina({
    query,
    variables: props.variables,
    data: props.data,
  });
  if (!data) { // <- this is never true as-is
    return
loading...
;
  }

export const getStaticProps = async (ctx) => {
// ...
  let data ={}; // <-- This will still be truthy in the renderer
  try {
    data = await staticRequest({
      query,
      variables,
    });
  } catch (error) {
    // swallow errors related to document creation
  }

  return {
    props: {
      data,
      variables,
    },
  };
};

Things blew up later when we tried to do: data.getPostDocument.data
If we change the default value of data to null within getStaticProps, in all of our examples, docmentation, starters. codegen, etc, it will be easier for devs to setup working doc-creator logic

No longer applicable with the new api-driven patterns. ISR would be the next-based solution for this


text:
The current operating system is not capable of running this task

Describe the bug
I tried to setup the dependabot on a Azure DevOps Server 2020.
I installed the extension (1.30.0.776).
I created the dependabot.yml-File and the pipeline.
But the task in the pipeline fails immediately with this error: "The current operating system is not capable of running this task. That typically means the task was written for Windows only. For example, written for Windows Desktop PowerShell."
Repository
It's a private (self hosted) repo.
Expected behavior
I expect the dependabot to complete successfully and create the pull requests to update the old packages.
Extension

Host: Azure DevOps Server 2020 Update 1.2
Version (Extension): 1.30.0.776

Additional context
I tried to give the Project Collection Service Accounts all possible permissions.
As an Agent pool i use: Ubuntu - 20.04.5 LTS (Focal Fossa).
On the agent docker is installed. Docker-Version: 20.10.21, build baeda1f
This agent is used for the "normal" builds and works without any problems.
The Output is:
Starting: Run Dependabot
==============================================================================
Task         : Dependabot
Description  : Automatically update dependencies and vulnerabilities in your code
Version      : 1.30.776
Author       : Tingle Software
Help         : For help please visit https://github.com/tinglesoftware/dependabot-azure-devops
==============================================================================
##[error]The current operating system is not capable of running this task. That typically means the task was written for Windows only. For example, written for Windows Desktop PowerShell.
##[debug]System.InvalidOperationException: The current operating system is not capable of running this task. That typically means the task was written for Windows only. For example, written for Windows Desktop PowerShell.
   at Microsoft.VisualStudio.Services.Agent.Worker.TaskRunner.RunAsync()
   at Microsoft.VisualStudio.Services.Agent.Worker.StepsRunner.RunStepAsync(IStep step, CancellationToken jobCancellationToken)
Finishing: Run Dependabot

pipeline-yaml:
name: 'Dependabot CI'
trigger: none
stages:
  - stage: CheckDependencies
    displayName: 'Check Dependencies'
    jobs:
      - job: Dependabot
        displayName: 'Run Dependabot'
        pool:
          name: 'LinuxDocker'
        steps:
        - task: dependabot@1
          displayName: 'Run Dependabot'
          inputs:
            failOnException: false

dependabot-yaml:
version: 2
updates:
- package-ecosystem: "npm"
    directories:
      - "/path/to/package.json/" (replaced fo this issue / bug)
    schedule:
      interval: "weekly"
    labels:
      - "dependabot"
      - "dependencies"

I don't know if it is possible to run a container in another container specifically for Azure DevOps. That's what I gather from the pool named LinuxDocker. Try the hosted agents (the free minutes per month should generally be enough for weekly runs) or an agent that is not a docker container.

The agent itself is not a container. The name (LinuxDocker) is choosen to indicate that docker is available.

I suggest that you check the setup for the private agent. The only requirements are run on an Agent/DeploymentGroup here, docker be present and discoverable here, and the agent be version be recent here.

All this requirements are fulfilled (Agent-Version is 2.181.2).
I also tried it with another agent (that also meets this requirements) but it throws the same Exception.
I guess that I will try a hosted agent.

The change in #1246 should ideally solve the issue. I released 1.30.2 you can test and report back.

The new version (1.30.2.800) doesn't solve the problem. The same error occurs immediately after starting the dependabot-task.

Could you give an example of some of the "normal" builds that work without any problems? This will be useful to see tasks in them that work for comparison sake.

This is the requested pipeline for a "normal" build:
stages:
  - stage: BuildAndTests (Reducted - here the .NET Solution and the react-app gets build / published on another agent)
  - stage: Docker_Build
    displayName: Docker Build
    pool:
      name: 'LinuxDocker'
    variables:
      NumericVersion: $[ stageDependencies.BuildAndTests.BuildAndTests.outputs['CreateVersionVariable.numericVersion'] ]
    jobs:
      - job: DockerImage
        steps:
        - task: Docker@2
          displayName: 'Build Docker'
          inputs:
            containerRegistry: '<Reducted>'
            repository: '<Reducted>'
            command: 'build'
            Dockerfile: 'src/**/Dockerfile'
            tags: |
              $(Build.BuildNumber)
              latest
            arguments: '--build-arg BUILDNUMBER=$(NumericVersion)'
  - stage: Docker_Deploy
    displayName: Docker Deploy
    pool:
      name: 'LinuxDocker'
    jobs:
      - deployment: <Reducted>
        displayName: Deploy
        environment: '<Reducted>'
        strategy:
          runOnce:
            deploy:
              steps:
                - task: Docker@2
                  displayName: 'Push image'
                  inputs:
                    containerRegistry: '<Reducted>'
                    repository: '<Reducted>'
                    command: 'push'
                    tags: |
                      $(Build.BuildNumber)
                      latest

Perhaps relevant: This features are available on the agent (LinuxDocker)

Agent.Name				REDUCTED
Agent.Version			2.181.2
_						./externals/node/bin/node
Agent.ComputerName		REDUCTED
Agent.HomeDirectory		REDUCTED
Agent.OS				Linux
Agent.OSArchitecture	X64
curl					/usr/bin/curl
docker					/usr/bin/docker
dotnet					/usr/bin/dotnet
git						/usr/bin/git
HOME					REDUCTED
InteractiveSession		False
INVOCATION_ID			REDUCTED
JOURNAL_STREAM			9:45971
LANG					en_US.UTF-8
LOGNAME					REDUCTED
PATH					/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
PWD						REDUCTED
python					/usr/bin/python
python3					/usr/bin/python3
sh						/bin/sh
SHELL					/bin/bash

authors: MichaelSchHtc mburumaxwell

repo: tinglesoftware/dependabot-azure-devops


text:
4 Digit Seasons

Version: 3.0-SNAPSHOT
Build: 2018-02-06 01:21
OS: Windows 7 6.1
JDK: 1.8.0_162 amd64 Oracle Corporation
What is the actual behaviour?
TMM Scrapes A Shows With A 1 Or 2 Digit Season Number.  While Trying To Scrape On TVDB For The Show 'Mythbusters', You Get An Error 'Failed Getting Episode Metadata'. After A Few Attempts, I Pulled The Show Up In TVDB And Realize The Season Number Are Listed By The Year The Show Aired, Ex. Season 2003, Season 2004, Etc. After I Renamed The Folders And The Files To The Correct Year For Season Number, TMM Was Able To Scrape The Show.
What is the expected behaviour?
To Be Able To Scrape A Show, The Was TMM Was Designed. But I Know Of No Other Way To Do For This For A Show Like 'Myhtbusters', Without Renaming The Season Number, As Stated Before.
Steps to reproduce:
Try Scraping The Show 'Mythbusters', I Know Of No Other Shows Formatted Like This,  With A 1 Or 2 Digit Season Number. Then Change The Season Numbers On The Folders And Files To Reflect The Year The Episode Aired.
Additional
Have you attached the logfile from the day it happened?

Our file system parser should be already aware of 4 numbers in seasons.
Have to check if there might be a problem on our scraper side...

we've migrated v3 to GitLab (https://gitlab.com/tinyMediaManager/tinyMediaManager) along with all issues. The issues for v2 at GitHub will be closed - we will respond to the corresponding issue in GitLab in the future
br
Manuel

repo: tinyMediaManager/tinyMediaManager

license_source: bigquery


text:
Simplify symbolic.SumNode.floordiv logic

Simplify the logic, also fix an inconsistency that
(a*6+b*6)//16 -> (((a*6)+(b*6))//16) but (a*6+b*6+16)//16 -> ((((a*3)+(b*3))//8)+1).
With the change now (a*6+b*6)//16 -> (((a*3)+(b*3))//8) too.

Did you run the fuzzer to test?

I did not. I just ran test/external/fuzz_symbolic.py for 10k times and it all matched.

Cool. I'd merge a PR that runs both fuzzers for a bit in CI.

authors: geohot leastcompressible

repo: tinygrad/tinygrad


text:
Fix NOUNROLL

The NOUNROLL option is currently broken. Does it make sense to add a test run of test/test_ops.py with NOUNROLL enabled to catch this in future?
Also I've noticed that the currently failing Metal tests do pass with NOUNROLL enabled. Should we maybe enable these tests and run them like that?

Changes made in tinygrad/:
------------------------------------------------------------
files                             insertions       deletions
------------------------------------------------------------
tinygrad/codegen/cstyle.py                 1               1
------------------------------------------------------------
lines added in the tinygrad folder: 0

Nice fix. It's not a mainline option, so idk if it needs a test, and there's just getting lucky on METAL, have to root cause

authors: akretz geohot tinyb0t


text:
Unit testing

It's a miracle the project made it this far without it. Add coverage for the vital parts and fix any bugs uncovered along the way.

Unfortunately, because of how strongly interwoven this project is with the game itself and libraries like SMLHelper, it is very difficult to run small parts without an active game instance. The core logics in particular are so intertwined with the game they're basically inseperable, and if those vital parts cannot be tested, what is the point of tests?
It might be possible with heavy mocking. But at that point, maintainability suffers. The tests would likely need to be rewritten every time an implementation detail changes. Ultimately, for this project at least, tests seem to add more headaches than they resolve.

repo: tinyhoot/SubnauticaRandomiser


text:
wait for confirmation could run into infinite loop

It could happen that the function wait_for_confirmation(client, txid) is running/waiting undefinitely. This happens some times for a reason that I cannot explain.
Do you know in which case this situation can happen?
A suggestion could be to define the wait_for_confirmation and submit functions with an additional timeout parameter, for example:
def wait_for_confirmation(client, txid, timeout)
and/or
def submit(transaction_group, wait, timeout): ---> when wait = True, a timeout could be given.

Hi @BrelKsiba,
wait_for_confirmation is added to py-algorand-sdk too (see). It has the feature you have requested with a default value of 1000 blocks which is the maximum range (first valid - last valid). So you can start to use it think.
I think it can be removed from the tinyman-py-sdk, or keep it an alias.

Do you know in which case this situation can happen?

Probably it happens if your transaction is not approved by the protocol.
For example, if the price changes more than the given slippage, your transaction fails.

Thx.
Using wait_for_confirmation from py-algorand-sdk fixed the problem. Still need to modify the submit function in Tinyman SDK to add a third parametr for wait_rounds.

authors: BrelKsiba cobang

repo: tinymanorg/tinyman-py-sdk


text:
使用tools/torch_inference.py在pyharm中直接进行推理报错？

Before Asking

[X] I have read the README carefully. 我已经仔细阅读了README上的操作指引。

[X] I want to train my custom dataset, and I have read the tutorials for finetune on your data carefully and organize my dataset correctly; 我想训练自定义数据集，我已经仔细阅读了训练自定义数据的教程，以及按照正确的目录结构存放数据集。

[X] I have pulled the latest code of main branch to run again and the problem still existed. 我已经拉取了主分支上最新的代码，重新运行之后，问题仍不能解决。

Search before asking

[X] I have searched the DAMO-YOLO issues and found no similar questions.

Question
设置参数部分：
def make_parser():
parser = argparse.ArgumentParser('damo eval')
parser.add_argument(
    '-f',
    '--config_file',
    default=r'configs/damoyolo_tinynasL25_S.py',
    type=str,
    help='pls input your config file',
)
parser.add_argument('-p',
                    '--path',
                    default=r'D:\hb\DAMO-YOLO\DAMO-YOLO-master\assets\dog.jpg',
                    type=str,
                    help='path to image')
parser.add_argument('-c',
                    '--ckpt',
                    default=r'path/to/your/damoyolo_tinynasL25_S.pth',
                    type=str,
                    help='ckpt for eval')
parser.add_argument('--conf',
                    default=0.6,
                    type=float,
                    help='conf of visualization')

parser.add_argument('--img_size',
                    default=640,
                    type=int,
                    help='test img size')
return parser

运行报错：
Traceback (most recent call last):

File "D:\hb\DAMO-YOLO\DAMO-YOLO-master\tools\torch_inference.py", line 125, in
main()
└ <function main at 0x000001861B046DC8>

File "D:\hb\DAMO-YOLO\DAMO-YOLO-master\tools\torch_inference.py", line 73, in main
config = parse_config(args.config_file)
│            │    └ 'configs/damoyolo_tinynasL25_S.py'
│            └ Namespace(ckpt='path/to/your/damoyolo_tinynasL25_S.pth', conf=0.6, config_file='configs/damoyolo_tinynasL25_S.py', img_size=6...
└ <function parse_config at 0x000001861B0469D8>
File "D:\hb\DAMO-YOLO\DAMO-YOLO-master\damo\config\base.py", line 134, in parse_config
return get_config_by_file(config_file)
│                  └ 'configs/damoyolo_tinynasL25_S.py'
└ <function get_config_by_file at 0x0000018619256AF8>
File "D:\hb\DAMO-YOLO\DAMO-YOLO-master\damo\config\base.py", line 122, in get_config_by_file
"{} doesn't contains class named 'Config'".format(config_file))
└ 'configs/damoyolo_tinynasL25_S.py'
ImportError: configs/damoyolo_tinynasL25_S.py doesn't contains class named 'Config'
请问大佬应该如何解决？
期待回复，谢谢。
Additional
No response

可能是PYTHONPATH设置问题。可以尝试执行export PYTHONPATH=当前项目路径，试试是否能够成功运行。

可能是PYTHONPATH设置问题。可以尝试执行export PYTHONPATH=当前项目路径，试试是否能够成功运行。

您好，我是在Windows10的系统下进行搭建环境与推理训练的。

可能是PYTHONPATH设置问题。可以尝试执行export PYTHONPATH=当前项目路径，试试是否能够成功运行。

您好，我是在Windows10 的系统环境下搭建虚拟环境，进行推理/训练。

如图所示，我在windows的环境变量中添加了项目的文件路径为环境变量，但是使用tools/torch_inference.py在pycharm运行/推理的时候任然是出现以下报错：

我输入的参数如下图：

请问我应该如何解决这个问题呢？期待您的回复！

您好，首先您可以先确认下在configs路径下是否存在该配置文件。
其次，请问您是否是在pycharm里直接右键点击tools/torch_inference.py的代码编辑页面然后点击Run运行的？
如果是的话，这样会在根目录下运行绝对路径的torch_inference.py，此时config文件的路径就不再是configs/xxx.py。
我们建议您在DAMO-YOLO的主目录下运行tools/torch_inference.py，如在命令行下运行：
cd <path_to_DAMO-YOLO>
python tools\torch_inference.py -f configs\xxx.py -p xxx.jpg -c xxx.pth

这样能够有效地避开这类路径相关的问题。
此外，注意到您没有指定ckpt路径，您可以在DAMO-YOLO代码库的Model Zoo中找到各个模型的torch模型地址，下载后记得指定哈~

您好，首先您可以先确认下在configs路径下是否存在该配置文件。
其次，请问您是否是在pycharm里直接右键点击tools/torch_inference.py的代码编辑页面然后点击Run运行的？
如果是的话，这样会在根目录下运行绝对路径的torch_inference.py，此时config文件的路径就不再是。configs/xxx.py
我们建议您在DAMO-YOLO的主目录下运行tools/torch_inference.py，如在命令行下运行：
cd <path_to_DAMO-YOLO>
python tools\torch_inference.py -f configs\xxx.py -p xxx.jpg -c xxx.pth

这样能够有效地避开这类路径相关的问题。
此外，注意到您没有指定ckpt路径，您可以在DAMO-YOLO代码库的Model Zoo中找到各个模型的torch模型地址，下载后记得指定哈~

您好，谢谢您的回复。
按照您的指导，已解决我当前的问题，谢谢您！

authors: HYLcool cwhgn havefunheehee

repo: tinyvision/DAMO-YOLO


text:
Booking Model Review

Working on updated Models/Migrations/Factories based on @sl0wik 's updated logic structure https://whimsical.com/booking-VrUF3bVpqu7JEjKy9tmr3Q
Current Status: WIP

@sl0wik should I worry about policies and nova resources based on the notion.so task for now?

In ref to policies - you can keep everything allowed for now (but if you got new resource good to create policy)

remove slot config array and service_class use in slot classes
remove SlotFactory
remove Slot migration
remove slot from the BookingServiceProvider
remove Slot model
change the namespaces in the filterClassList array in the booking model
remove FutureSlots from nova filters
remove SlotDayFilter
remove Nova Slot Model
remove SlotPolicy
remove slot from the novaPackageServiceProvider
changes pulled from https://github.com/tipoff/bookings/pull/52 and merge into this PR

Besides pending resolving comments and determining @sl0wik 's intentions in #49, I'm going to transition this into review. Will keep DNM tag until all comments are resolved.

repo: tipoff/bookings


text:
fix: Add an option DB_AUTH for PGSQL

In this PR:

Added an option DB_AUTH for PGSQL
Fixed lint issues and typos in README files

Many thanks @alwynpan for your handful of contributions to this repository for the benefit of others. Tagged as 3.12.0

Thank you muchly @tiredofit  for your speedy action and providing such a great tool! Happy Halloween. 🎃

authors: alwynpan tiredofit

repo: tiredofit/docker-db-backup


text:
script 10-cloudflare-companion did not pass completion check

Summary
I built the local docker image on armV7 succesfully a couple of weeks ago. When I update the local docker build with the newest version, it build successfully, but doesn't launch.
Steps to reproduce

What is the expected correct behavior?
no errors
Relevant logs and/or screenshots
**********************************************************************************************************************
**********************************************************************************************************************
****                                                                                ****
****       ERROR - Some initialization scripts haven't completed - All services are now halted                    ****
****             - The following scripts in '/etc/cont-init.d' did not pass their completion check                ****
****                                                                                ****
**********************************************************************************************************************
**********************************************************************************************************************

10-cloudflare-companion

[cont-init.d] 06-messaging: exited 0.
[cont-init.d] 10-cloudflare-companion: executing...
foreground: warning: unable to spawn /var/run/s6/etc/cont-init.d/10-cloudflare-companion: No such file or directory
[cont-init.d] 10-cloudflare-companion: exited 127.
[cont-init.d] 99-container: executing...
However, the file does exist

bash-5.1# cat /var/run/s6/etc/cont-init.d/10-cloudflare-companion
#!/command/with-contenv bash
source /assets/functions/00-container
prepare_service single
PROCESS_NAME="traefik-cloudflare-companion"
Sanity Test
sanity_var TARGET_DOMAIN "Target Domain"
sanity_var DOMAIN1 "Domain 1"
sanity_var DOMAIN1_ZONE_ID "Domain 1 Zone ID"
liftoff
### Environment

- Image version / tag:  docker built locally
- Host OS: Linux 5.10.63-v7+ #1496 SMP Wed Dec 1 15:58:11 GMT 2021 armv7l GNU/Linux

<details>
  cf-companion:
    container_name: cf-companion
    image: cf-comp:latest
    restart: always
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock:ro
    environment:
      - TIMEZONE=Europe/Brussels
      - TRAEFIK_VERSION=2
      - CF_EMAIL=${CF_API_EMAIL}
      - CF_TOKEN=${CF_GLOBAL_API_KEY}
      - TARGET_DOMAIN=${DOMAIN_NAME}
      - DOMAIN1=${DOMAIN_NAME}
      - DOMAIN1_ZONE_ID=${CF_ZONE_ID}
      - DOMAIN1_PROXIED=TRUE
      - </details>

<!-- Include anything additional -->

### Possible fixes
<!-- If you can, provide details to the root cause that might be responsible for the problem. -->

You'll want to update your base image as the first line is now trying to launch from /command/with-contenv instead of previously /usr/bin/with-contenv. This is a change with the S6 Overlay init system that the base images rely on. Once you update the image should build correctly.

I was only able to make the build successful by change the Dockerfile to
FROM docker.io/tiredofit/alpine:3.14
instead of
FROM docker.io/tiredofit/alpine:latest


text:
tds-theme 패키지 추가

PR 설명

https://github.com/titicacadev/triple-frontend/issues/1523

기존 color-palette 패키지와 core-elements의 global style을 대체할 패키지입니다.
디자인 시스템의 가장 밑바닥이 되는 계층입니다. 디자인 요소를 일관되게 적용할 수 있는 역할을 합니다.
정적 타입 지원을 쓸 수 있습니다.
(지금은 없지만 나중에) 디자인 토큰이나 다크 모드를 지원하게 된다면 쉽게 확장할 수 있을 것입니다.
만약 다른 css-in-js 라이브러리나 tailwind css를 사용하게 된다면 이 패키지만 수정해서 전환하기 편리할 것입니다.

변경 내역

tds-theme 패키지 추가
colors foundation 추가
default theme 추가

그 설명을 안 썼네요. Triple Design System 줄임말이고 디자인 용어를 통일하려고 합니다.

repo: titicacadev/triple-frontend


text:
Cristian Neftali Hernandez Ramirez

DESCRIPTION
Nombre:Cristian Neftali Hernandez Ramirez
Email:cristian0402218@gmail.com
WhatsApp:9513135291
Ciudad:Oaxaca de Juarez
Pais:Mexico
Retos:

[x] Primer problema
[x] Segundo problema
[x] Tercer problema
[x] Cuarto problema
[x] Quinto problema
[x] Opcional

¿Como explicarias el proposito de este proyecto? (opcional)
Ayuda a implementar los conocimientos básicos de JavaScript y proporciona experiencia práctica en el desarrollo web.
¿Cuál es tu stack tecnológico preferido? ¿Por qué? (opcional)
PERN (PostgreSQL, Express, React, Node.js).
Me gusta por su eficiencia en el manejo de datos, la flexibilidad en el desarrollo frontend y backend, y la comunidad activa.

Hola Cristian,
¡Gracias por tu contribución! Aquí está el feedback sobre tu PR:

Funcionalidad: La solución cumple con los requisitos, resolviendo correctamente los problemas planteados.
Algoritmo: El uso de promesas y async/await mejora la claridad y evita el Callback Hell, buen trabajo.
Pruebas: No se incluyen pruebas unitarias, sería importante añadirlas para validar el código.
Calidad del Código: El código es limpio y bien estructurado. Los nombres de variables son claros y descriptivos.
Documentación y Estructura: Buena documentación y comentarios. La estructura del código es adecuada.
Sugerencia: Considera agregar pruebas unitarias y un archivo .gitignore.

¡Buen trabajo y sigue así!
Saludos,
Alejandro


text:
Issue with dir_names, dir_names_max_depth, json, files

Version: v36.0.6
Error:
Error when evaluating 'strategy' for job 'publish-terraform'. .github/workflows/publish-terraform.yaml (Line: 55, Col: 15): Matrix vector 'project' does not contain any values

Workflow manifest: https://github.com/onedr0p/home-ops/blob/961ff6db1a3d93567011f2c6a1e99d1be32831ae/.github/workflows/publish-terraform.yaml#L30-L45
Workflow run: https://github.com/onedr0p/home-ops/actions/runs/5095027403

@onedr0p I assume the error is because there aren't any changed directories.

🤦 thanks for pointing that out you're absolutely correct. I jumped the gun a bit because of the major update.

repo: tj-actions/changed-files


text:
Some suggestions for improvement

Hi there,
thanks for the plugin, I extended some base functionality - unfortunately I can not share as I also added functionality proprietary to our business, but you could consider the following:

Allow customisation / templating of Jira issue title - in our case we extract exception messages and inject it into the Jira issue title
Allow customisation / templating of Jira description - in our case we use [PLACE_HOLDER] variables for the message and also place-holders for the LastMessage fields
Include logging the LastMessage of the stream alert (then you will be able to extract custom fields etc)
Avoid logging of duplicate Jira issues. I just implemented this generating the MD5 of the log-message (without the date) and then embed the M5 within the Jira issue's description. Before logging a new Jira task I do a JQL query on the project and check if the same issue already exists (and then skip the logging of it).

I didn't want to wait for a release / fix and redid the plugin - https://github.com/magicdude4eva/graylog-jira-alarmcallback

repo: tjackiw/graylog-plugin-jira


text:
How to mix ocamlformat and ocamlformat-mlx

In my own Conform set up config have the ocaml file type mapped to ocamlformat, e.g.:
opts = {
    formatters_by_ft = {
      ocaml = { "ocamlformat" },
    }
}

If I keep that config and open an mlx file with the filetype ocaml.mlx, conform match on the first part of the file type an tries to format with ocamlformat.
If I remove the config above, then this plugin configuration takes over and ocaml.mlx is mapped to ocamlformat-mlx.
Is there a way to have both ocamlformat and ocamlformat-mlx configured with each being applied to the correct filetypes?

I realised we can pass a function to the conform table, so I went with:
function()
  if vim.bo.filetype == "ocaml.mlx" then
    return { "ocamlformat_mlx" }
  else
    return { "ocamlformat" }
  end
end

It seems to do the trick


text:
根证书和签发的子证书验证问题

使用fabric-ca生成了根证书，并使用该根证书签发一个子证书，使用 openssl verify -CAfile root.pem child.pem 显示是 ok的。可是使用国密时，openssl 和gmssl 都无法检验通过，报错：
crypto/sm2/sm2_sign.c 504: sm2_do_verify
C = US, ST = North Carolina, O = Hyperledger, OU = client, CN = admin
error 7 at 0 depth lookup: certificate signature failure
error signcerts/cert.pem: verification failed
4497929664:error:0D0C5006:asn1 encoding routines:ASN1_item_verify:EVP lib:crypto/asn1/a_verify.c:188:

请问这个问题解决了吗？我也遇到同样的问题。这边生成的证书，使用gmssl做证书验证，报和你同样的错误。
但也不是每本证书都出错，做个几百次，就会有一对CA和Ca签发的子证书验证不过。

请问这个问题解决了吗？我也遇到同样的问题。这边生成的证书，使用gmssl做证书验证，报和你同样的错误。
但也不是每本证书都出错，做个几百次，就会有一对CA和Ca签发的子证书验证不过。

为什么我直接每次验证都是不通过的，这个到底是什么原因引起的？直接看证书内容的话并没发现什么问题啊

authors: cyberwave dddengyunjie victortanjh

repo: tjfoc/fabric-ca-gm


text:
fix segfault on MacOSX

For example, hw execute with this repository.
$ hw href ~/.ghq/github.com/servo/servo/tests/wpt/css-tests/compositing-1_dev/html/
zsh: segmentation fault  hw href
$

Perhaps the cause is because the buffer is insufficient for omit dot.
see also #19

Thank you :smile:

:+1:

authors: hhatto tkengo

repo: tkengo/highway

license: mit


text:
Release 0.4.27

@JuliaRegistrator register(branch=release)

Registration pull request created: JuliaRegistries/General/14537
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.4.27 -m "<description of version>" 3dc40c481242e40f5fc507adbf9a43d62fcaf9b4
git push origin v0.4.27

authors: JuliaRegistrator tkf


text:
Rewrite error-trace view with VSCode Webview UI toolkit

https://code.visualstudio.com/blogs/2021/10/11/webview-ui-toolkit
https://github.com/tlaplus/vscode-tlaplus/issues/260
https://github.com/tlaplus/vscode-tlaplus/issues/259
https://github.com/tlaplus/vscode-tlaplus/issues/258
https://github.com/tlaplus/vscode-tlaplus/issues/257
https://github.com/tlaplus/vscode-tlaplus/issues/256
https://github.com/tlaplus/vscode-tlaplus/issues/255
https://github.com/tlaplus/vscode-tlaplus/issues/250
https://github.com/tlaplus/vscode-tlaplus/issues/239
https://github.com/tlaplus/vscode-tlaplus/issues/229
https://github.com/tlaplus/vscode-tlaplus/issues/215
https://github.com/tlaplus/vscode-tlaplus/issues/164

Hi, I'm available to work on this one.
My proposal would be to start migrating the check-result-view "as it is" to the webview toolkit component library following the "default samples" (https://github.com/microsoft/vscode-webview-ui-toolkit-samples). This is replacing current ui elements with equivalent webui components and moving the current ui code to typescript.
After that the ui design could be changed to address the listed issues.

@afonsonf It would be beneficial to determine the scalability of the webview-ui-toolkit early in the process. Currently, the HTML-based viewer tends to have slow rendering times when dealing with extensive traces (comprising hundreds of states) and intricate states (involving dozens of variables). Additionally, I recall implementing a viewport feature in the past for the older Toolbox to manage lengthy traces.

Created here some specs to stress test the extension: https://github.com/afonsonf/vscode-tlaplus-stress-specs
In my pc, using the current version of the extension in codespaces, I can run the BigState spec until around the counter 40 and the BigTrace until around the counter 500, I would use those values as the base to achieve in the refactoring
Current state of the refactoring can be checked in the following branch (Buttons, run status, states and coveragestats done): https://github.com/afonsonf/vscode-tlaplus/tree/refactor-webview-using-vscode-toolkit
In my current implementation I made the webview stateless, does not require the state to be sent by the extension as a message, this means all the html is generated in the extension side, and not "filled" in the webview side, but still need to do some tests to check if it is better or not, if not those classes can easily be reused to "fill" the html in the webview side

authors: afonsonf lemmy

repo: tlaplus/vscode-tlaplus


text:
Redis 6 ACL config

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Use Redis 6 with ACL user
"databaseConfig": {
    "redis": {
        "path": "/run/redis/redis.sock",
	"password": "admin:xxxx"
    }

},
Can I use ":" to separate user and password maybe another config ?
Error in laravel-echo (password is OK, it's working with laravel
Unhandled error event: ReplyError: WRONGPASS invalid username-password pair or user is disabled.
Expected behavior
Connection working

have to fallback with default user and password

repo: tlaverdure/laravel-echo-server


text:
[Parser] Add FuncType support

Support FuncType in Parser & Printer.
If a relax function's return type is a FuncType,  we are using Callable type to do the type annotation in the printed IR, and  Callable can take other Callable as argument to handle multi-nested functions.
# Example
@R.function
def func( x: Tensor((m, n), "float32")) -> Callable((Tensor((m, n), "float32")), Tensor((m, n), "float32")):
    @R.function
    def local_func(z: Tensor((m, n), "float32")) -> Tensor((m, n), "float32"):
        return relax.add(z, z)
    return local_func_1

cc @YuchenJin @psrivas2 @sunggg @Hzfengsy

Thanks for the review! @Hzfengsy @sunggg @YuchenJin

repo: tlc-pack/relax


text:
Exception thrown when drawing a long line

I have a lot of pages with many strokes on them. When I draw a long squiggly line (back and forth over itself) this happens:
ReferenceError: structuredClone is not defined
    at n.r.updateShapes (https://beta.tldraw.com/_next/static/chunks/pages/_app-fdae74dd5cccf047.js:25:152895)
    at n.e.onPointerMove (https://beta.tldraw.com/_next/static/chunks/pages/_app-fdae74dd5cccf047.js:25:146476)
    at n.t.handleEvent (https://beta.tldraw.com/_next/static/chunks/pages/_app-fdae74dd5cccf047.js:25:142371)
    at n.t.handleEvent (https://beta.tldraw.com/_next/static/chunks/pages/_app-fdae74dd5cccf047.js:25:142435)
    at n.t.handleEvent (https://beta.tldraw.com/_next/static/chunks/pages/_app-fdae74dd5cccf047.js:25:142435)
    at https://beta.tldraw.com/_next/static/chunks/pages/_app-fdae74dd5cccf047.js:25:226328
    at https://beta.tldraw.com/_next/static/chunks/pages/_app-fdae74dd5cccf047.js:25:116346
    at https://beta.tldraw.com/_next/static/chunks/pages/_app-fdae74dd5cccf047.js:25:876248
    at x (https://beta.tldraw.com/_next/static/chunks/pages/_app-fdae74dd5cccf047.js:25:876339)
    at e.batch (https://beta.tldraw.com/_next/static/chunks/pages/_app-fdae74dd5cccf047.js:25:116269)
    at n.r.batch (https://beta.tldraw.com/_next/static/chunks/pages/_app-fdae74dd5cccf047.js:25:205439)
    at n.r.dispatch (https://beta.tldraw.com/_next/static/chunks/pages/_app-fdae74dd5cccf047.js:25:221324)
    at onPointerMove (https://beta.tldraw.com/_next/static/chunks/pages/_app-fdae74dd5cccf047.js:25:431372)
    at Object.eU (https://beta.tldraw.com/_next/static/chunks/framework-8080449f0215cedd.js:9:14912)
    at eH (https://beta.tldraw.com/_next/static/chunks/framework-8080449f0215cedd.js:9:15066)
    at https://beta.tldraw.com/_next/static/chunks/framework-8080449f0215cedd.js:9:33374
    at re (https://beta.tldraw.com/_next/static/chunks/framework-8080449f0215cedd.js:9:33473)
    at rn (https://beta.tldraw.com/_next/static/chunks/framework-8080449f0215cedd.js:9:33887)
    at https://beta.tldraw.com/_next/static/chunks/framework-8080449f0215cedd.js:9:39345
    at oP (https://beta.tldraw.com/_next/static/chunks/framework-8080449f0215cedd.js:9:96345)
    at eF (https://beta.tldraw.com/_next/static/chunks/framework-8080449f0215cedd.js:9:14046)
    at ro (https://beta.tldraw.com/_next/static/chunks/framework-8080449f0215cedd.js:9:35178)
    at nU (https://beta.tldraw.com/_next/static/chunks/framework-8080449f0215cedd.js:9:20847)
    at nI (https://beta.tldraw.com/_next/static/chunks/framework-8080449f0215cedd.js:9:20747)
    at HTMLDivElement.r (https://beta.tldraw.com/_next/static/chunks/pages/_app-fdae74dd5cccf047.js:25:2666)

Thanks, I'll take a look! Nice tree!
By the way, please could you let me know what browser and device you're using?

I did "add to homescreen" from Chrome 96 on Android. I can send the JSON file if you want.

I did "add to homescreen" from Chrome 96 on Android. I can send the JSON file if you want.

Hey we've fixed this internally and will hopefully release the fix next week!
You can test it out on https://staging.tldraw.com

repo: tldraw/tldraw-beta


text:
Error - ... provided an invalid property of "default" - with 1.0.0 and babel 6

Uncaught Exception:
Error: Plugin 0 specified in "/home/mike/slack-wrapped-2/.babelrc" provided an invalid property of "default"
    at Plugin.init (/home/mike/slack-wrapped-2/node_modules/babel-core/lib/transformation/plugin.js:124:13)
    at Function.normalisePlugin (/home/mike/slack-wrapped-2/node_modules/babel-core/lib/transformation/file/options/option-manager.js:155:12)
    at /home/mike/slack-wrapped-2/node_modules/babel-core/lib/transformation/file/options/option-manager.js:183:30
    at Array.map (native)
    ...

{
  ...
  "plugins": [
    ["babel-plugin-module-alias", [
      { "src": "./src/main", "expose": "main" },
      { "src": "./src/web", "expose": "web" }
    ]]
  ]
}

I wonder if this is this related to https://github.com/babel/babel/pull/2697?

It seems that it probably was. The fix https://github.com/babel/babel/commit/b5b7e346a04c99da8793e2c65cc3b3c7c720253d is included in babel 6.0.15, and this problem does not occur with 6.0.15.

repo: tleunen/babel-plugin-module-alias


text:
Feature request: Show line number when parsing failed

I got an error with the following that killed the development server:

[ Info: ⌛ processing introduction-to-julia/index.md
ERROR: FranklinParser.FranklinParserException(:BlockNotClosed, "An opening token 'RAW' was found but not closed.\n")
Stacktrace:
 [1] serve(fw::LiveServer.SimpleWatcher; host::String, port::Int64, dir::String, verbose::Bool, coreloopfun::Xranklin.var"#239#240"{OrderedCollections.LittleDict{Symbol, OrderedCollections.LittleDict{Pair{String, String}, Float64}, Vector{Symbol}, Vector{OrderedCollections.LittleDict{Pair{String, String}, Float64}}}}, preprocess_request::typeof(identity), inject_browser_reload_script::Bool, launch_browser::Bool, allow_cors::Bool)
   @ LiveServer ~/.julia/packages/LiveServer/srpPq/src/server.jl:333
 [2] serve(d::String; dir::String, folder::String, clear::Bool, final::Bool, single::Bool, prepath::String, prefix::String, base_url_prefix::String, debug::Bool, cleanup::Bool, port::Int64, host::String, launch::Bool)
   @ Xranklin ~/.julia/packages/Xranklin/xncHr/src/build/serve.jl:126
 [3] serve (repeats 2 times)
   @ ~/.julia/packages/Xranklin/xncHr/src/build/serve.jl:63 [inlined]
 [4] top-level scope
   @ none:1

caused by: FranklinParser.FranklinParserException(:BlockNotClosed, "An opening token 'RAW' was found but not closed.\n")
Stacktrace:
  [1] parser_exception
    @ ~/.julia/packages/FranklinParser/nI6nq/src/utils/errors.jl:6 [inlined]
  [2] _find_blocks!(blocks::Vector{FranklinParser.Block}, tokens::SubArray{FranklinParser.Token, 1, Vector{FranklinParser.Token}, Tuple{UnitRange{Int64}}, true}, templates::OrderedCollections.LittleDict{Symbol, FranklinParser.BlockTemplate, Vector{Symbol}, Vector{FranklinParser.BlockTemplate}}, is_active::Vector{Bool}; process_linereturn::Bool)
    @ FranklinParser ~/.julia/packages/FranklinParser/nI6nq/src/blocks/find_blocks.jl:148
  [3] _find_blocks!
    @ ~/.julia/packages/FranklinParser/nI6nq/src/blocks/find_blocks.jl:98 [inlined]
  [4] find_blocks(tokens::SubArray{FranklinParser.Token, 1, Vector{FranklinParser.Token}, Tuple{UnitRange{Int64}}, true}; is_md::Bool)
    @ FranklinParser ~/.julia/packages/FranklinParser/nI6nq/src/blocks/find_blocks.jl:21
  [5] (::FranklinParser.var"#66#67")(t::Vector{FranklinParser.Token})
    @ FranklinParser ~/.julia/packages/FranklinParser/nI6nq/src/partition.jl:108
  [6] partition(s::SubString{String}, tokenizer::FranklinParser.var"#64#65"{OrderedCollections.LittleDict{Char, Vector{Pair{FranklinParser.TokenFinder, Symbol}}, Vector{Char}, Vector{Vector{Pair{FranklinParser.TokenFinder, Symbol}}}}}, blockifier::FranklinParser.var"#66#67"; tokens::SubArray{FranklinParser.Token, 1, Vector{FranklinParser.Token}, Tuple{UnitRange{Int64}}, true}, disable::Vector{Symbol}, postproc::typeof(FranklinParser.default_md_postproc!))
    @ FranklinParser ~/.julia/packages/FranklinParser/nI6nq/src/partition.jl:40
  [7] #md_partition#70
    @ ~/.julia/packages/FranklinParser/nI6nq/src/partition.jl:111 [inlined]
  [8] md_partition
    @ ~/.julia/packages/FranklinParser/nI6nq/src/partition.jl:111 [inlined]
  [9] convert_md(md::SubString{String}, c::Xranklin.LocalContext; tohtml::Bool, nop::Bool, kw::Base.Pairs{Symbol, Union{}, Tuple{}, NamedTuple{(), Tuple{}}})
    @ Xranklin ~/.julia/packages/Xranklin/xncHr/src/convert/markdown/md_core.jl:62
 [10] convert_md
    @ ~/.julia/packages/Xranklin/xncHr/src/convert/markdown/md_core.jl:51 [inlined]
 [11] #html#109
    @ ~/.julia/packages/Xranklin/xncHr/src/convert/markdown/md_core.jl:126 [inlined]
 [12] html
    @ ~/.julia/packages/Xranklin/xncHr/src/convert/markdown/md_core.jl:126 [inlined]
 [13] #html#110
    @ ~/.julia/packages/Xranklin/xncHr/src/convert/markdown/md_core.jl:130 [inlined]
 [14] html
    @ ~/.julia/packages/Xranklin/xncHr/src/convert/markdown/md_core.jl:130 [inlined]
 [15] _process_md_file_html(lc::Xranklin.LocalContext, page_content_md::String; skip::Bool)
    @ Xranklin ~/.julia/packages/Xranklin/xncHr/src/process/md.jl:405
 [16] process_md_file_io!(io::IOBuffer, gc::Xranklin.GlobalContext{Xranklin.LocalContext}, fpath::String; opath::String, initial_pass::Bool, tohtml::Bool)
    @ Xranklin ~/.julia/packages/Xranklin/xncHr/src/process/md.jl:331
 [17] process_md_file(gc::Xranklin.GlobalContext{Xranklin.LocalContext}, fpath::String, opath::String; initial_pass::Bool, kw::Base.Pairs{Symbol, Union{}, Tuple{}, NamedTuple{(), Tuple{}}})
    @ Xranklin ~/.julia/packages/Xranklin/xncHr/src/process/md.jl:60
 [18] process_file(gc::Xranklin.GlobalContext{Xranklin.LocalContext}, fpair::Pair{String, String}, case::Symbol, t::Float64; skip_files::Vector{Pair{String, String}}, initial_pass::Bool, final::Bool, reproc::Bool)
    @ Xranklin ~/.julia/packages/Xranklin/xncHr/src/process/process.jl:68
 [19] process_file(gc::Xranklin.GlobalContext{Xranklin.LocalContext}, fpair::Pair{String, String}, case::Symbol, t::Float64)
    @ Xranklin ~/.julia/packages/Xranklin/xncHr/src/process/process.jl:35
 [20] build_loop(cycle_counter::Int64, #unused#::LiveServer.SimpleWatcher, watched_files::OrderedCollections.LittleDict{Symbol, OrderedCollections.LittleDict{Pair{String, String}, Float64}, Vector{Symbol}, Vector{OrderedCollections.LittleDict{Pair{String, String}, Float64}}})
    @ Xranklin ~/.julia/packages/Xranklin/xncHr/src/build/build_loop.jl:111
 [21] #239
    @ ~/.julia/packages/Xranklin/xncHr/src/build/serve.jl:124 [inlined]
 [22] serve(fw::LiveServer.SimpleWatcher; host::String, port::Int64, dir::String, verbose::Bool, coreloopfun::Xranklin.var"#239#240"{OrderedCollections.LittleDict{Symbol, OrderedCollections.LittleDict{Pair{String, String}, Float64}, Vector{Symbol}, Vector{OrderedCollections.LittleDict{Pair{String, String}, Float64}}}}, preprocess_request::typeof(identity), inject_browser_reload_script::Bool, launch_browser::Bool, allow_cors::Bool)
    @ LiveServer ~/.julia/packages/LiveServer/srpPq/src/server.jl:326
 [23] serve(d::String; dir::String, folder::String, clear::Bool, final::Bool, single::Bool, prepath::String, prefix::String, base_url_prefix::String, debug::Bool, cleanup::Bool, port::Int64, host::String, launch::Bool)
    @ Xranklin ~/.julia/packages/Xranklin/xncHr/src/build/serve.jl:126
 [24] serve (repeats 2 times)
    @ ~/.julia/packages/Xranklin/xncHr/src/build/serve.jl:63 [inlined]
 [25] top-level scope
    @ none:1
make: *** [develop] Error 1

The error message did not contain the line number from the source markdown file.
The issue was I had What??? in my markdown file, and I believe ??? is the beginning of a code block in this version of Franklin (?). This took me a long time to find because every time I had to restart the serve function, and that just takes a really long time for the repository I'm currently working on. I had to create a test site and copy over the markdown file into there to debug this.
This would have been a lot easier if the parser exception returns the line number from the source which I guess requires a source map.
Related feature request:
I'd like to serve just one file while developing. The serve process takes upwards of 15 minutes for me with all the other libraries and code block executions it has to do in other files, and restarting the server is an expensive operation and when exceptions occur it completely breaks by workflow.
Currently, my plan to deal with this is delete the files I'm not developing, and once I'm ready to deploy, git restore the files and then make a push. I'm pretty sure colleagues of mine who are not super familiar with git will not do this.
It would be nice if there was a way to run serve(ignore="completed-*.md") or serve(only="filename.md").

I'll need to come back to this to reply in full but in short:

yes Line number makes sense, it's not easy, I had tried and failed to do it properly with Franklin, the recursive aspect makes it fairly difficult but it's worth trying to do it right. Definitely what's possible is to give the surrounding string which helps locate the source
yes ??? is the indication of a specific raw block, what is inside one is left completely untouched by Xranklin, it can be toggled off, you can also escape the question marks to avoid this
your third one is handled by the cache, Xranklin does not re execute stuff that have already been built successfully unless it has reasons to believe things need to be rebuilt.

Modifications to Utils is one such reason as it can affect the whole site. You can help indicate whether pieces of code should not be reevaluated by marking them as fully independent from the test using the # indep marker in the code block, this will allow Xranklin to skip the code if it has a code representation already available and the code hasn't changed.
So in a REPL, you should very seldom have to pay for the full build price unless you're changing utils all the time.
Btw I recommend you call it from a REPL and not using Julia -e otherwise when it does crash you not only get kicked out of the server but you also lose all the hot loading of packages.

Thanks for the quick reply. I didn't realize I should be starting it from the REPL. That helps, I'll do that going forward.

Definitely what's possible is to give the surrounding string which helps locate the source

I think this would have been more than sufficient to help me find the issue, and I imagine it'll be as useful as having a line number in the error message.

I think similarly it would be nice if the error message here showed the output of the codeblock, or a more detailed stacktrace. Maybe this is not as important since one can just look at the output in the rendered page to see which block errored.

what would you have liked to see here instead of this? (and maybe could you open this in a separate issue?)
Stacktrace handling is not the easiest, but I was under the impression this is ok, the warning in the REPL might alert the user and the full message is displayed in stderr on the webpage?

The only times this has been a problem is when I run the file for the first time and there’s lots of code execution blocks, so it takes a while. And I know there’s an error but don’t know where so I have to go hunting. Once live reload works, it’s painless to open the browser to see the error.
Maybe the best thing is to just add a warning message saying the error / stacktrace is on the page.

authors: kdheepak tlienart


text:
Capability name from requirement assignment is not rendered

Consider an example:
tosca_definitions_version: tosca_simple_yaml_1_3

topology_template:

  node_templates:

    node_1:
      type: tosca:Root
      requirements:
        - dependency:
            node: node_2
            capability: feature

    node_2:
      type: tosca:Root

Here I explicitly point to a capability named feature and expect it to show up in the normalized output:
requirements:
      - name: dependency
        capabilityTypeName: tosca::Node
        capabilityName: feature

However, I get the following output:
requirements:
      - name: dependency
        capabilityTypeName: tosca::Node
        capabilityName: ""

@Shishqa Your PR fixes one issue but breaks others. Will investigate.

Generally I recommend running scripts/test before submitting a PR!

Sorry for that 🌚
I found the problem, will submit a fixing PR now

It might be tricky... I am trying to fix it, too, and it's not so simple to discover in that piece of code if it's a type name or a capability name...

I see, my fix brings everything back and not solves the issue above

I am working on it ... it's tricky :)

authors: Shishqa tliron

repo: tliron/puccini


text:
Getting Error while building the tlspuffin

error: failed to run custom build command for `wolfssl-sys v0.1.7 (/home/ubuntu/Desktop/TLS-Puffin/tlspuffin/crates/wolfssl-sys)`

Caused by:
  process didn't exit successfully: `/home/ubuntu/Desktop/TLS-Puffin/tlspuffin/target/debug/build/wolfssl-sys-2ed1b5a032076794/build-script-build` (exit status: 101)
  --- stdout
  running: "sh" "-c" "exec \"$0\" \"$@\"" "autoreconf" "-ivf"
  libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'.
  libtoolize: copying file 'build-aux/ltmain.sh'
  libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
  libtoolize: copying file 'm4/libtool.m4'
  libtoolize: copying file 'm4/ltoptions.m4'
  libtoolize: copying file 'm4/ltsugar.m4'
  libtoolize: copying file 'm4/ltversion.m4'
  libtoolize: copying file 'm4/lt~obsolete.m4'
  running: "sh" "-c" "exec \"$0\" \"$@\"" "/home/ubuntu/Desktop/TLS-Puffin/tlspuffin/target/debug/build/wolfssl-sys-0381a3ec0fcd6955/out/configure" "--prefix=/home/ubuntu/Desktop/TLS-Puffin/tlspuffin/target/debug/build/wolfssl-sys-0381a3ec0fcd6955/out" "--disable-shared" "--enable-static" "--enable-debug" "--enable-opensslall" "--enable-opensslextra" "--enable-context-extra-user-data" "--enable-keygen" "--enable-certgen" "--enable-tls13" "--enable-aesni" "--enable-dtls" "--enable-sp" "--enable-sp-asm" "--enable-dtls-mtu" "--disable-sha3" "--enable-intelasm" "--enable-curve25519" "--enable-secure-renegotiation" "--enable-postauth" "--enable-psk"
  checking for gcc... clang
  checking whether the C compiler works... yes
  checking for C compiler default output file name... a.out
  checking for suffix of executables...
  checking whether we are cross compiling... no
  checking for suffix of object files... o
  checking whether the compiler supports GNU C... yes
  checking whether clang accepts -g... yes
  checking for clang option to enable C11 features... none needed
  checking whether clang understands -c and -o together... yes
  checking build system type... x86_64-pc-linux-gnu
  checking host system type... x86_64-pc-linux-gnu
  checking target system type... x86_64-pc-linux-gnu
  checking for a BSD-compatible install... /usr/bin/install -c
  checking whether build environment is sane... yes
  checking for a race-free mkdir -p... /usr/bin/mkdir -p
  checking for gawk... no
  checking for mawk... mawk
  checking whether make sets $(MAKE)... yes
  checking whether make supports the include directive... yes (GNU style)
  checking whether make supports nested variables... yes
  checking whether UID '1000' is supported by ustar format... yes
  checking whether GID '1000' is supported by ustar format... yes
  checking how to create a ustar tar archive... gnutar
  checking dependency style of clang... gcc3
  checking whether make supports nested variables... (cached) yes
  checking how to print strings... printf
  checking for a sed that does not truncate output... /usr/bin/sed
  checking for grep that handles long lines and -e... /usr/bin/grep
  checking for egrep... /usr/bin/grep -E
  checking for fgrep... /usr/bin/grep -F
  checking for ld used by clang... /usr/bin/ld
  checking if the linker (/usr/bin/ld) is GNU ld... yes
  checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
  checking the name lister (/usr/bin/nm -B) interface... BSD nm
  checking whether ln -s works... yes
  checking the maximum length of command line arguments... 1572864
  checking how to convert x86_64-pc-linux-gnu file names to x86_64-pc-linux-gnu format... func_convert_file_noop
  checking how to convert x86_64-pc-linux-gnu file names to toolchain format... func_convert_file_noop
  checking for /usr/bin/ld option to reload object files... -r
  checking for objdump... objdump
  checking how to recognize dependent libraries... pass_all
  checking for dlltool... no
  checking how to associate runtime and link libraries... printf %s\n
  checking for ar... ar
  checking for archiver @FILE support... @
  checking for strip... strip
  checking for ranlib... ranlib
  checking command to parse /usr/bin/nm -B output from clang object... ok
  checking for sysroot... no
  checking for a working dd... /usr/bin/dd
  checking how to truncate binary pipes... /usr/bin/dd bs=4096 count=1
  checking for mt... mt
  checking if mt is a manifest tool... no
  checking for stdio.h... yes
  checking for stdlib.h... yes
  checking for string.h... yes
  checking for inttypes.h... yes
  checking for stdint.h... yes
  checking for strings.h... yes
  checking for sys/stat.h... yes
  checking for sys/types.h... yes
  checking for unistd.h... yes
  checking for dlfcn.h... yes
  checking for objdir... .libs
  checking if clang supports -fno-rtti -fno-exceptions... yes
  checking for clang option to produce PIC... -fPIC -DPIC
  checking if clang PIC flag -fPIC -DPIC works... yes
  checking if clang static flag -static works... yes
  checking if clang supports -c -o file.o... yes
  checking if clang supports -c -o file.o... (cached) yes
  checking whether the clang linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
  checking dynamic linker characteristics... GNU/Linux ld.so
  checking how to hardcode library paths into programs... immediate
  checking whether stripping libraries is possible... yes
  checking if libtool supports shared libraries... yes
  checking whether to build shared libraries... no
  checking whether to build static libraries... yes
  checking whether the -Werror option is usable... yes
  checking for simple visibility declarations... yes
  checking size of long long... 8
  checking size of long... 8
  checking size of time_t... 8
  checking for __uint128_t... yes
  checking for arpa/inet.h... yes
  checking for fcntl.h... yes
  checking for limits.h... yes
  checking for netdb.h... yes
  checking for netinet/in.h... yes
  checking for stddef.h... yes
  checking for time.h... yes
  checking for sys/ioctl.h... yes
  checking for sys/socket.h... yes
  checking for sys/time.h... yes
  checking for errno.h... yes
  checking for sys/un.h... yes
  checking for socket in -lnetwork... no
  checking whether byte ordering is bigendian... no
  checking for __atomic... yes
  checking for gethostbyname... yes
  checking for getaddrinfo... yes
  checking for gettimeofday... yes
  checking for gmtime_r... yes
  checking for gmtime_s... no
  checking for inet_ntoa... yes
  checking for memset... yes
  checking for socket... yes
  checking for strftime... yes
  checking for atexit... yes
  checking for clang options needed to detect all undeclared functions... -fno-builtin
  checking whether gethostbyname is declared... yes
  checking whether getaddrinfo is declared... yes
  checking whether gettimeofday is declared... yes
  checking whether gmtime_r is declared... yes
  checking whether gmtime_s is declared... no
  checking whether inet_ntoa is declared... yes
  checking whether memset is declared... yes
  checking whether socket is declared... yes
  checking whether strftime is declared... yes
  checking whether atexit is declared... yes
  checking for size_t... yes
  checking for uint8_t... yes
  checking for uintptr_t... yes
  checking dependency style of clang... gcc3
  checking for thread local storage (TLS) class... _Thread_local
  checking for debug... yes
  checking how to run the C preprocessor... clang -E
  checking whether clang is Clang... yes
  checking whether pthreads work with "-pthread" and "-lpthread"... yes
  checking whether Clang needs flag to prevent "argument unused" warning when linking with -pthread... no
  checking for joinable pthread attribute... PTHREAD_CREATE_JOINABLE
  checking whether more special flags are required for pthreads... no
  checking for PTHREAD_PRIO_INHERIT... yes
  checking for openssl... yes
  checking for fast RSA... no
  checking for cos in -lm... yes
  checking for library containing gethostbyname... none required
  checking for library containing socket... none required
  checking for vcs system... none
  checking for vcs checkout... no
  checking whether the linker accepts -Werror... yes
  checking whether the linker accepts -z relro -z now... yes
  checking whether the linker accepts -pie... yes
  checking whether C compiler accepts -Werror... yes
  checking whether C compiler accepts -g... yes
  checking whether C compiler accepts -ggdb... yes
  checking whether C compiler accepts -O0... yes
  checking whether C compiler accepts -Wno-pragmas... yes
  checking whether C compiler accepts -Wall... yes
  checking whether C compiler accepts -Wextra... yes
  checking whether C compiler accepts -Wunknown-pragmas... yes
  checking whether C compiler accepts -Wthis-test-should-fail... no
  checking whether C compiler accepts -Waddress... yes
  checking whether C compiler accepts -Warray-bounds... yes
  checking whether C compiler accepts -Wbad-function-cast... yes
  checking whether C compiler accepts -Wchar-subscripts... yes
  checking whether C compiler accepts -Wcomment... yes
  checking whether C compiler accepts -Wfloat-equal... yes
  checking whether C compiler accepts -Wformat-security... yes
  checking whether C compiler accepts -Wformat=2... yes
  checking whether C compiler accepts -Wmaybe-uninitialized... no
  checking whether C compiler accepts -Wmissing-field-initializers... yes
  checking whether C compiler accepts -Wmissing-noreturn... yes
  checking whether C compiler accepts -Wmissing-prototypes... yes
  checking whether C compiler accepts -Wnested-externs... yes
  checking whether C compiler accepts -Wnormalized=id... no
  checking whether C compiler accepts -Woverride-init... yes
  checking whether C compiler accepts -Wpointer-arith... yes
  checking whether C compiler accepts -Wpointer-sign... yes
  checking whether C compiler accepts -Wshadow... yes
  checking whether C compiler accepts -Wshorten-64-to-32... yes
  checking whether C compiler accepts -Wsign-compare... yes
  checking whether C compiler accepts -Wstrict-overflow=1... yes
  checking whether C compiler accepts -Wstrict-prototypes... yes
  checking whether C compiler accepts -Wswitch-enum... yes
  checking whether C compiler accepts -Wundef... yes
  checking whether C compiler accepts -Wunused... yes
  checking whether C compiler accepts -Wunused-result... yes
  checking whether C compiler accepts -Wunused-variable... yes
  checking whether C compiler accepts -Wwrite-strings... yes
  checking whether C compiler accepts -fwrapv... yes
  creating wolfssl-config - generic 5.5.4 for -lwolfssl -lpthread
  checking the number of available CPUs... 2
  configure: adding automake macro support
  configure: creating aminclude.am
  configure: added jobserver support to make for 3 jobs
  checking that generated files are newer than configure... done
  configure: creating ./config.status
  config.status: creating stamp-h
  config.status: creating Makefile
  config.status: creating wolfssl/version.h
  config.status: creating wolfssl/options.h
  config.status: creating cyassl/options.h
  config.status: creating support/wolfssl.pc
  config.status: creating rpm/spec
  config.status: creating wolfcrypt/test/test_paths.h
  config.status: creating scripts/unit.test
  config.status: creating config.h
  config.status: executing depfiles commands
  config.status: executing libtool commands
  config.status: executing wolfssl/wolfcrypt/async.h commands
  config.status: executing wolfssl/wolfcrypt/fips.h commands
  config.status: executing wolfssl/wolfcrypt/port/cavium/cavium_nitrox.h commands
  config.status: executing wolfssl/wolfcrypt/port/intel/quickassist.h commands
  config.status: executing wolfssl/wolfcrypt/port/intel/quickassist_mem.h commands
  configure: ---
  configure: Running make clean...
  configure: ---
  configure: Generating user options header...
  checking for wolfssl/openssl/aes.h... no

  --- stderr
  Cloning into '/home/ubuntu/Desktop/TLS-Puffin/tlspuffin/target/debug/build/wolfssl-sys-0381a3ec0fcd6955/out'...
  autoreconf: export WARNINGS=
  autoreconf: Entering directory '.'
  autoreconf: configure.ac: not using Gettext
  autoreconf: running: aclocal --force -I m4
  autoreconf: configure.ac: tracing
  autoreconf: configure.ac: creating directory build-aux
  autoreconf: running: libtoolize --copy --force
  autoreconf: configure.ac: not using Intltool
  autoreconf: configure.ac: not using Gtkdoc
  autoreconf: running: aclocal --force -I m4
  autoreconf: running: /usr/bin/autoconf --force
  autoreconf: running: /usr/bin/autoheader --force
  autoreconf: running: automake --add-missing --copy --force-missing
  configure.ac:22: installing 'build-aux/compile'
  configure.ac:24: installing 'build-aux/config.guess'
  configure.ac:24: installing 'build-aux/config.sub'
  configure.ac:28: installing 'build-aux/install-sh'
  configure.ac:28: installing 'build-aux/missing'
  Makefile.am: installing 'build-aux/depcomp'
  parallel-tests: installing 'build-aux/test-driver'
  autoreconf: Leaving directory '.'
  configure: error: Error including wolfssl/openssl/aes.h. Possible circular dependency introduced or missing include.
  thread 'main' panicked at '
  command did not execute successfully, got: exit status: 1

  build script failed, must exit now', /home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/autotools-0.2.5/src/lib.rs:715:5
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

@maxammann , How to resolve above error?

Very weird. Can you confirm compiling wolfssl manually on your Ubuntu? https://www.wolfssl.com/documentation/manuals/wolfssl/chapter02.html

I have complied the wolfssl manually and it works perfectly

Which command did you use for compiling tlspuffin? That defines the version of wolfssl.

I meet the same error while building tlspuffin. There are my command using for compiling tlspuffin.
unzip ./wolfssl-5.4.0.zip
cd wolfssl-5.4.0
./configure
make
make install
./testsuite/testsuite.test
How can I resolve the error?

You mean for compiling wolfssl? Did the commands you posted work or did they fail?

You mean for compiling wolfssl? Did the commands you posted work or did they fail?

Yes, these commands were used to compile wolfssl, and they worked successfully. In addition, I run command ./testsuite/testsuite in the home directory of wolfssl, and passed all tests.

I just tried to reproduce this. On my system calling cargo build after a checkout works sucessfully.

On which OS are you?

Closing because of inactivity, let's continue here: https://github.com/tlspuffin/tlspuffin/issues/229

authors: apran-vs arpan-vs maxammann s1awwhy

repo: tlspuffin/tlspuffin


text:
Submit matike

Submit is maybe broken.

Coverage decreased (-0.5%) to 71.145% when pulling ba10ef7bce52920d8da81cfe966a456e61596890 on submit-matike into 99e00b0199329682bf5ab4d2aa3626515156a657 on master.

Changes Unknown when pulling b03a4e0f02f1740a6e370685b20d9c9839014406 on submit-matike into ** on master**.

Changes Unknown when pulling 732c51a21bf77f522b67ff4690ee6de807066005 on submit-matike into ** on master**.

LGTM.

authors: Salmela coveralls matike

repo: tmc-cli/tmc-cli


text:
Use of the archived and experimental hcl2 library

It seems that we are pulling a library that was experimental and is no longer supported by the vendor see Hashicorp's HCL Readme.
According to their docs, they advise everyone to move to the newest versions, hosted in the hcl2 branch of the HCL Project.
See for more information: Version Selection Guide.
I'll open a PR to upgrade to this version of the HCLv2 library.

I'll open a PR to upgrade to this version of the HCLv2 library.

That would be awesome. Thank you.

This was done in 5c1402dc2b410e362afee45a3cf15dcb08bc1f2c

authors: menendezjaume tmccombs


text:
pygments gem is not working on ruby 2.2.2 -> undefined method size on nil:NilClass Error.

gem install pygments.rb
ERROR:  Error installing pygments.rb:
	invalid gem: package is corrupt, exception while verifying: undefined method `size' for nil:NilClass (NoMethodError) in /Users/arpit/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/cache/pygments.rb-0.6.3.gem

And due to this reason jekyll is also failing.

Sorry for the trouble. My bad. Got it sorted out from above jekyll's issue page.


text:
Adding client accounts

I have created the roles in both base and client account and made sure the trust is configured in the client account and modified the cloud watch event role with the client account number.
With that said, the UI isn't showing data from the client account where should I look for errors to troubleshoot this misery?

@ammar-alim , Data collection from new account is taken care of data collection batch job execution and the same will be occurring once in an hour. So hopefully in an hour time the data will be available on the PacBot dashboard.

The steps mentioned in the documentation is enough for onboarding new accounts to base account.
Could you please quickly verify below points?

Created iam role called pacman_ro (recommended) with ReadOnlyAccess (arn:aws:iam::aws:policy/ReadOnlyAccess)
Updated trusted relation in newly created role to assume from pacman_ro in base account
Updated pacman_ro policy in base account by adding new role arn along with the existing one
Updated cloudwatch rule in base account with client account's number as follows,"encrypt": false,
"value": "Base_Account_ID,Client_Account_ID_1,Client_Account_ID_2",
"key": "accountinfo"
 }

believe we are talking about the file
installer/terraform/lambda-submit/function.tf
 {
      "encrypt": false,
      "value": "${var.accountid},${var.client_accountid}",
      "key": "accountinfo"
    },

authors: ammar-alim johnakash jonshern

repo: tmobile/pacbot


text:
Possibility of "if" in templates?

Hey @tmrts
I'm really tempted to use boilr, but one critical feature is missing. I need the possibility to create a condition in the questions. Nothing very complicated, but still. I had the idea of implementing it on my own, but there are so many libraries and tools out there, I didn't want to make "just another templater".
So I found your boilr.
Do you think it would be possible to add an if condition to the project.json?
Like:
{
    "AppName": "Demo",
    "ExpertMode": [
        true,
        false
    ],
    "FolderName": {
        "value": "Demo",
        "condition": "ExpertMode"
    }
}

Only ask the question about the FolderName if the answer to ExpertMode is evaluated truthly.
Cheers
Chris

Chris thank you for trying out boilr.
What you need is already implemented and can be used as such:
{
    "ExpertMode": false,
}

Default value of ExpertMode will be false and the user will see a boolean prompt for true/false.
In template usage:
{{ If ExpertMode }}
....
{{ end }}

For more information please take a look at the wiki pages.
It explains the templating features of boilr.
For creating templates check this page.

There is a little misunderstanding :wink:
I don't want to use {{ If ExpertMode }} in the templates. Its the initial questioning of the user that I'm interested in.
So if I define my condition stuff, the user gets asked about this question only if the condition is true.
project.json:
{
    "AppName": "Demo",
    "ExpertMode": false,
    "FolderName": {
        "value": "Demo",
        "condition": "ExpertMode"
    }
}

Example workflows:
1.)

boilr template use demo .
User gets asked: Please choose a value for "AppName"
User gets asked: Please choose a value for "ExpertMode"
User selects "false".
Template engine does its magic.

2.)

boilr template use demo .
User gets asked: Please choose a value for "AppName"
User gets asked: Please choose a value for "ExpertMode"
User selects "true".
User gets asked: Please choose a value for "FolderName"
Template engine does its magic.

Cheers

@buehler gotcha I see what you mean :+1:
I can make an enhancement as such:
{
    "AppName": "Demo",
    "ExpertMode": {
        "FolderName": "Demo",
        "RepoNumber: 5,
    }
}

The workflow:

Prompt for AppName
Confirmation prompt for ExpertMode
If ExpertMode enabled, Prompt for the fields inside. Else, use default values of those.

Thanks for bringing this up, I was thinking about this earlier but got sidetracked and forgot.

Cool! :+1:
Yea that's exactly what I meant. This would be awesome!
And to be a little "challenging": in the same changes, would it be possible to add variables to the default values? i.e. run the default variables through go-templates first.
Like:
"AppName": "Demo",
"FolderName": "{{AppName}}"

If this is possible (and easy) too, it would be as awesome as any other template engine! :wink:
Well, maybe I'll find the time to implement this one on my own and send you a PR, we'll see.

Thanks for another good suggestion. I'll see what I can do, but It'd be a good idea to move this suggestion to a new issue just so it doesn't get lost.

authors: buehler tmrts

repo: tmrts/boilr


text:
Question about: Some test suites likely terminated without passing on results

Hi,
First off, thanks for the repo and work :)
So i want to use this package in our tests, but am seeing the following error randomly on my test runs:
Some test suites likely terminated without passing on results
I know that it's a validation, but do we know why this is happening?
Thanks,
-arnon

I am also facing a similar kind of issue,
Found test suites does not match results.
Test suites found: 1036
Test suite results: 44
Some test suites likely terminated without passing on results, exit with error
This is the error I am getting:
npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! ui@0.1.0 cypress:parallel: cypress-parallel -s cypress:run -t 2 -d './src' -a '"--config baseUrl=http://localhost:3000 integrationFolder=src testFiles=**/integration-test/*cypress.js" '`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the ui@0.1.0 cypress:parallel script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/maarunkumar/.npm/_logs/2022-03-26T05_14_05_325Z-debug.log`

I am also facing same issue any updates?

I passed correct tests directory with correct regexp and in 95% tests pass without any issues. But sometimes randomly I've got results like
Found test suites does not match results. Test suites found: 71 Test suite results: 61 Some test suites likely terminated without passing on results, exit with error
It mentions specific suites that were not found, but I see results for these suites. Any ideas why it could happen?

Also tests failed with the same message in console ^^  - if launch by specific tag.

@tnicola is this package abandoned? Maybe someone has working fork?
This script should using glob/pattern for spec files, there is no reason to do this differently than Cypress itself. I'm using Cypress for component testing, and like many other people I have spec files together with component files. All my specs are passing, but I'm still getting false error from cypress-parallel :/

Any update on this one ? Facing this issue and there is no information on why this is happening

I am also facing similar issue, but for me, results shows only 0 even though tests are running successfully.
Any updates on this ticket?

Has anyone managed to solve/bypass this issue?
Still getting this issue on version 0.13.0

For us it was an issue with different threads that used the same results folder. After small update to put results in different folders for different threads (unfortunately it's hardcoded in source lib) we didn't meet these problem. For now 2nd month without this issue

I'm not a developer but since we don't get answers here I've been digging trough the code and I think I found what the issue was for us...
First of all, the error I was getting is:
Found test suites does not match results.
Test suites found: 68
Test suite results: 0
Some test suites likely terminated without passing on results, exit with error
The following tests suites are missing results: { test1, test2, ... all 68 files }

So, it was false failing even if all the tests passed and the statement triggering the error is this -> https://github.com/tnicola/cypress-parallel/blob/710dd191692c8f11c2823183fcfa36fa81fcd91e/lib/cli.js#L99
To make shorter the story, after debugging it I realized that for "some" unknown reason none of the tests was generating the .json file needed by this plugin in order to output the results, it creates a runner-results folder for that but basically it was empty after any execution and that's why Test suite results: 0 (timeMap.size). I continued debugging and found where this issue started to happen:
We have mochawesome, mocha-junit-reporter and cypress-multi-reporters, so our code looked like this:
cypress v10.11
mochawesome v6.2.2
cypress-multi-reporters v1.6.1
mocha-junit-reporter v2.0.2
cypress-parallel v0.13.0
Piece of our cm-desktop.config.js file
module.exports = defineConfig({
	e2e: {
	        specPattern: 'cypress/user/*.test.js',
		reporter: 'cypress-multi-reporters',
		reporterOptions: {
			configFile: 'cypress/config/user/reporter-config.json',
		}
	}
});

Our reporter-config.json file
{
  "reporterEnabled":"mochawesome, mocha-junit-reporter",
  "mochaJunitReporterReporterOptions":{
    "mochaFile":"cypress/results/user/dsk/user-[hash].xml"
  },
  "mochawesomeReporterOptions":{
    "reportDir":"cypress/results/user/dsk",
    "overwrite":false,
    "html":false,
    "json":true
  }
}

Our package.json scripts
"cm:dsk:user": "cypress run --config-file ./cypress/config/user/cm-desktop.config.js --browser chrome",
"cm:run:dsk:user:parallel": "cypress-parallel -s cm:dsk:user -t 4 -d ./cypress/user",

^ That way, I was getting the error... So, after almost a full day of trial and error, I found that when I was executing this way then the multi-reporter-config.json file generated by default by the plugin was writing this lines:
{
  "reporterEnabled": "cypress-parallel/json-stream.reporter.js, cypress-parallel/simple-spec.reporter.js"
}

So, it immediately made me think that my reporter and reporterOptions flag was not being read... why? I don't know the answer, I thought it should have worked but looks like it's not working in that way, maybe a bug?? anyway... this statement confirmed my theory (https://github.com/tnicola/cypress-parallel/blob/710dd191692c8f11c2823183fcfa36fa81fcd91e/lib/thread.js#L36), effectively it was not recognizing my reporting flags.
The solution? ... I made it work by doing this:

Removed the reporter and reporterOptions flags from the cm-desktop.config.js file (yes, deleted those lines from there)
Our reporter-config.json file now looks like this:

{
  "reporterEnabled":"mochawesome, cypress-parallel/json-stream.reporter.js, cypress-parallel/simple-spec.reporter.js, mocha-junit-reporter",
    "mochawesomeReporterOptions":{
      "reportDir":"cypress/results/user/dsk",
      "overwrite":false,
      "html":false,
      "json":true
    },
  "cypressParallelSimpleSpecReporterJsReporterOptions": {
    "reportDir": "runner-results"
  },
  "mochaJunitReporterReporterOptions":{
    "mochaFile":"cypress/results/user/dsk/user-[hash].xml"
  }
}

Our package.json now look like this:

"cm:dsk:user": "cypress run --config-file ./cypress/config/user/cm-desktop.config.js --browser chrome",
"cm:run:dsk:user:parallel": "cypress-parallel -s cm:dsk:user -t 4 -d ./cypress/user -p 'cypress/config/user/reporter-config.json'",

I found that -p flag in the settings file (https://github.com/tnicola/cypress-parallel/blob/710dd191692c8f11c2823183fcfa36fa81fcd91e/lib/settings.js#L50) which is not documented in README but it was the correct for us, now I'm not passing a reporter flag and letting the reporter-config.json to drive the enabled reporters.
Hope it helps anyone to solve the issue, I don't know if it's a bug or a miss by me while following instructions but that's what it is.
cc @tnicola

hi @ezunigaf90
May I know after your change above , has this issue happened again ?

hi @guychienll
in lib/cli.js you can find such line of code const resultsPath = path.join(process.cwd(), 'runner-results');
So here the name of directory for results  is hardcoded. I've added here parameter that could be added from command line, so now if I use this plugin for different types of tests run in one workspace it wrote results in different directories. After this we don't have problems with empty or not full results

hi @olga-govor thanks lots ! you are awesome !

hi @olga-govor thank your reply ,
But I want to know how do you wrote the result in diff folder ?
If it's what you mean (the PR below has implementation),
How to trigger the command once and wrote results in different folders at the same time?
https://github.com/tnicola/cypress-parallel/pull/176

Hello, any news on this? Im wondering how this can be fixed, it is a little annoying that same build is failing due to missing results. I'm running one testing procedure with multiple test suits split into 4 threads. Maybe there is any workaround?

This is too irritating, I would rather let the tests run longer than fail randomly.
Unfortunately, this was a deal breaker for us at https://coretex.ai so we are moving away from using cypress-parallel until this issue is fixed.

@olga-govor can you please share the npm script, how to store the execution of threads in different folders and merge them all for reporting purpose.

@ketteq-neon I'm not storing results of execution of threads in different folders as I don't need it. But as I use this plugin in one space for different types of tests I need to store results from different test types in different folders ( you can see in prev.comments how it was achieved)
As this plugin split by threads and you know in which thread are you (at least you have list of tests for each thread) you can place also some index of thread, so it can be used to identify folder for each thread

authors: Densf2 SaniaSid aram-bigid chojnicki ezunigaf90 guychienll igorperic17 ketteq-neon kganczarek mahanthi-arun-kumar olga-govor prashantpundhir ronit15

repo: tnicola/cypress-parallel


text:
Version mismatch in documentation

Documentation version mentions 0.12.3 as latest, but SAQ has 0.13.3

i'm not sure how to fix this

@grigi could you help me figure out and fix this? i don't know how docs are deployed or why they aren't updating.

I did manually click the build docs option, but I see a lot of features have been added (like using Postgres as a queue).
I'll see if I have time to update some of the docs, but the PG feature changes a lot of assumptions made before.

@grigi i changed the master branch to main, and i think i broke the read the docs, can you take a look?sorry about that

@grigi ok i think readthedocs finally updated their ui

Hi @tobymao seems that their UI took a while to realise a new branch exists.
You still need to setup the Github integration. Either go to https://readthedocs.org/accounts/3rdparty/ and setup github integration directly.
or
Go to https://github.com/tobymao/saq/settings/hooks/new and enter the url and secret from https://readthedocs.org/dashboard/saq-py/integrations/278319/
And instruct GitHub to use that webhook when an update to main happens.
This should setup readthedocs to automatically have up-to-date docs.
If you need to you're welcome to delete the webhook I setup.

ok, i set up the web hook

Sweet! Hopefully documentation is now automated for the future :+1:

authors: Seemone grigi tobymao

repo: tobymao/saq


text:
Warnings in with NativeScript 2.5.0 > "Unable to sync files. Error is: ENOENT: no such file or directory..."

Platform: iOS
TNS: 2.5.0
Unable to sync files. Error is: ENOENT: no such file or directory, stat '/Users/name/testApp/platforms/ios/testApp/app/app.scss'
This is what I get every time it resyncs a change of SCSS files. Is there a way to ignore messages like these?

Closing because of duplicate issue #18.

repo: toddanglin/nativescript-dev-sass


text:
[FEATURE] Server Side Jukebox

**Is your feature request related to a problem? Please describe. **
It would be pretty cool if we could have a Jukebox block (kind of like the conductor really) that syncs to receivers. The main difference is that the Midi files are being read from a server folder so that way someone can run up to the jukebox at any time and play a song which will play to the connected receivers.
That way even if someone doesn't have their own midi's downloaded at that moment they can hear some music.
Also useful for playing a repeating playlist of songs in spawn for example or some other RP type situation.
Describe the solution you'd like
A Midi folder on the server that can be linked to a Jukebox block (or an option on the conductor block) that is linked to receivers to play music in a playlist without a player needing to hold the transmitter specifically.
Describe alternatives you've considered
I can't think of another way to do this without just having a player account afk in game lol
Additional context
Maybe as an optional feature we could allow midi files saving to the server that comes from a player client but this is kind of out of scope for this specific request and would add a lot of additional work.

Thanks for the suggestion! I'm glad you brought this idea up! I had previously considered doing something like this but at the time I wasn't sure that the version of Java installed on servers (since it can vary quite a bit and a specific version of Java isn't bundled with the server like it is with the Minecraft client) would be guaranteed to include the required implementations of various MIDI functionality. However now on version 1.18+ I include all of the MIDI implementations that I need (because Java 17+ doesn't easily let you access the bundled MIDI implementations anymore) so that shouldn't be a problem.
I will definitely look into this!

This feature will be available in the next update, 3.0.0, releasing tomorrow!

Closed by #71

authors: majorcyto tofodroid

repo: tofodroid/mimi-mod


text:
Added easybook.io integration

Hi,
This pull request adds support for easybook.io.
You can test the integration by signup on easybook web app: https://app.easybook.io/register

Hey,
Thanks for contributing!
However, I'm having trouble finding the button in easybook. I have a feeling easybook may show a newer design for newly-created accounts as it looks a bit different from your screenshot.
Here's what my "Edit Organization" screen looks like.
Also, please run make lint and fix any linting errors :)

Hey @adrihein , we decided to clear up old PRs to make way for some big refactoring that is upcoming. If you wish to continue work on this PR please feel free to reopen or add an issue for adding easybook.io support!

authors: adrihein bryanph syko

repo: toggl/toggl-button