text:
Aqara Switch Opple Phoscon

Hello, I am using Homebridge V1.1.0, Hue plugin 0.11.69 and Phoscon 2.05.77
I have Aqara Opple 4/6 Switch these are also shown in Phoscon (with picture, but i don't know if you can configure buttons, it's my first project with Phoscon...) i would like to use the switches in HomeKit.
They also appear, just like the Phoscon Gateway in HomeKit.  But there is a call sign at the switches.  I guess it is because no battery status is transmitted.
Unfortunately the buttons do not work.  I have assigned a scene or device but nothing happens.
Is this a known problem?  Can I help with the solution or is there already someone who has the Opple switches in HomeKit?
Thanks a lot!

I have the 6-button Opple and it works just fine in HomeKit.  All buttons register Single Press, Double Press and Long Press.
Did you just pair the switch?  It might take a few hours before the battery is populated.
Note that you need a Home hub (Apple TV, HomePod, or always-powered iPad) for the buttons to work.  Handling the buttons is like a HomeKit automation: this is done by the Home hub.
If you need more help troubleshooting, please capture a debug log file, while pressing the Opple's buttons, and attach the file here.  See https://github.com/ebaauw/homebridge-hue#debug-log-file.

Hey you, I got an iPad. I'm afraid I just got to the logs, but I think they're incorrect, don't you?
I'm not able to switch buttons with it yet.
Unfortunately I still get an error in the battery display.
homebridge.log.gz
homebridge-hue.json.gz

@ebaauw can you help me? I don't know if the logs are right or if I'm doing something wrong.
But unfortunately I still can't figure it out, the buttons don't trigger any action and a battery problem is displayed.
Thanks a lot

Sorry, haven’t yet found the time to look at the logs.  Need to be at my mac to do that.

I'm afraid I just got to the logs, but I think they're incorrect, don't you?

The debug log is what I want to see, but it looks like you didn't press any buttons while capturing the log.
The debug dump file reveals two Opple switches: a 6-button one that seems to work, and a 4-button one for which Homebridge Hue has never received a buttonevent.  I think it hasn't paired correctly to deCONZ.

Thanks for your Support!!!
This is strange, both switches are displayed in Phoscon (Deconz).  But I do not understand why I have problems in HomeKit.  The problem with the battery indicator is still there, it does not disappear even after a few days.
this is what it looks like for me in HomeKit.Maybe it's the same problem?

This is strange, both switches are displayed in Phoscon (Deconz).

That only means that the REST API plugin has created resources for the switches.  It say nothing about whether the switches are actually communicating with deCONZ.
I think the issue is between the switch and deCONZ, nothing to do with Homebridge Hue.  You can double-check in the deCONZ GUI if the Present Value attribute of the Multistate Input cluster changes when pressing the corresponding button.  If it doesn't, message from the switch don't arrive at deCONZ.

Thanks for your Support!
After upgrading to Homebridge-Hue V. 0.11.71 and deCONZ v2.05.78, every think works Fine!

authors: ebaauw ebrger

repo: ebaauw/homebridge-hue


text:
build: install tests into libexecdir

Tests are ELF files, so in case of multilib they will conflict. Using libexecdir will tell that this package is not multilib.
@ebassi though I'm not sure if we should use $libdir instead of $libexecdir.

eog, glib2, gjs are installing elfs into libexecdir

I've merged manually, and fixed @TingPing's comment as well.

source: gharchive/pull-request

authors: ebassi ignatenkobrain

repo: ebassi/graphene

license: mit

license_type: permissive

license_source: bigquery


text:
WIP: Add Message Items

WORK IN PROGRESS
Add MessageItems and MessageItem similar to Facebook.

@nahtnam see how the other controls behave...  they dont expose the ability to customize the CSS of every single tag. Its necessary

authors: ekampf nahtnam

repo: ebates-edc/ebates-chat-kit

license: MIT

license_source: github-api


text:
Investigate why datasets are stuck in exporting

Description of the problem
In the last few days the same issue has happened repeatedly when exporting a project:
The project status remains stuck in Exporting but the staging area contains the newly generated json files
see Yusra's comment on ticket #121
Datasets affected

ticket #666 - ingest  - 425c2759-db66-4c93-a358-a562c069b1f1
ticket #121 - ingest - 005d611a-14d5-4fbf-846e-571a1f874f70
ticket #766   - ingest - 074a9f88-729a-455d-bca5-0ce80edf0cea

A bug ticket has been created to find the root cause and fix it: #795
Acceptance criteria

[x] change project status for ticket #666 #121

Amnon added logging messages to the exporter

Needs reviews, and integration test running before promoting. Catchup after standup with devs.

A bug ticket has been created to find the root cause and fix it: #795

source: gharchive/issue

authors: ESapenaVentura gabsie idazucchi ke4

repo: ebi-ait/hca-ebi-wrangler-central


text:
Containerize, add SIGINT handler and instruction.

Feel free to close this if it's unwanted, but I was bored.

Cool, I like it.

authors: ebrian triangletodd

repo: ebrian/cryptowatch


text:
Ignore files in .gitignore

It would be nice if the plugin ignored files that match patterns in .gitignore by default. I currently have to add new directories (e.g. node_modules) to both .gitignore and to the plugin's  in my pom.xml.

I've submitted #53 which allows a single file to be used for exclude patterns. There are many ignore-type files (not just .gitignore) and .gitignore can appear in any directory which is more complicated to deal with.
Still, this is hopefully enough for you as you can set <excludesFile>.gitignore</excludesFile>.

+1 for adding an option to exclude files ignored by git.
I'd prefer an implementation based on a proper .gitignore parser and proper evaluation of the patterns as documented in https://git-scm.com/docs/gitignore . JGit might contain all we need and I would not mind having a non-optional JGit dependency because of this.
The proposal in #53 does not meet the above requirement.

@ppalaga I recently noticed that, in a multi-module project, the exlcudesFile parameter is failing if the file does not exist in every module. This looks to be my fault. Either we should modify the option not to fail if the file is missing, or have a single file for the entire project. Something like .gitignore may appear in other directories, but it certainly is not required. Appologies if I should not have reported this on this ticket.

Yeah, please open a new ticket. A fix is welcome!

Another idea would be to only format scm tracked files. That I think would be easier to implement because then you can just rely on the maven-scm-plugin to get the list of files tracked by the scm.
The other advantage of that would be that its not only git specific. (While git is probably the most used scm nowadays I'd say there are still a fair amount of non-git tracked projects out there)

authors: StefanD986 dwalluck ppalaga vrevelas


text:
pass in token as a parameter to MarkdownExporter

Currently, there is no way to pass the Notion_Token as a parameter to the MarkdownExporter. This means that the only way for it to work in a python script is to set the environment variable to the correct notion_token.
Can we add notion_token as parameter to markdownexporter and check if it's passed use whatever was passed otherwise fetch from os.environ ?
This makes it hard to work with multiple notion keys in the same code.

Sounds Good. At that time I had no idea how to pass the token, but now I think this can be implemented by adding the token argument from cleo Command(block_command). Thank you for bring useful idea


text:
Parsing failed For Tailwind 2.0

I get an JS error when trying to import my Tailwind 2.0 project. The ui gives me no errors or indication anything happened. For some context: it's a fairly complex project with a few plugins.

I've attached the json file I attempted to use:
tailwind.json.txt

I think the author abandoned this project. It should be archived

authors: CaptainYarb dzienisz

repo: ecklf/tailwindcss-figma-plugin


text:
Adding Files in AAS for download

Hi there,
first of all a happy new year.
I am currently using the basyx-server, basyx-registry and Mongo-DB via docker. It all works great and I've downloaded the basyx java sdk and created a small aas. That being said, I have a small question.
I wonder if it is possible to store a File in a AAS.
My Use-case is: Store a File in a AAS -> use REST-API or Java-SDK to get that file and change something inside the file -> Update the File in the AAS.
What I tried so far to store the File in a AAS:
File f = new File("MyPathToObject/teapot.obj", "text/plain");
f.setIdShort("teapot");
submodel.addSubmodelElement(f);
manager.createSubmodel(aasId, submodel);

When looking at the json in MongoDB it shows me the path to the file on my computer (kind of like a Property with the value being the path to the file).
I wonder if it is possible to also store the file on the server/docker container via the java-sdk, so anyone who needs the file can download it if needed.
Best,
Samed

Hi Samed,
it took some time but we're now in the implementation phase of this feature. It will be included in the upcoming release BaSyx Java 1.4.
Best regards,
Frank

Implemented, cf. https://github.com/eclipse-basyx/basyx-java-sdk/pull/252, https://github.com/eclipse-basyx/basyx-java-sdk/pull/251, https://github.com/eclipse-basyx/basyx-java-sdk/pull/239

authors: FrankSchnicke SamedAga

repo: eclipse-basyx/basyx-java-components


text:
chore: simplify DataSourceFactory and DataSinkFactory APIs

Feature Request
Currently, both DataSourceFactory and DataSinkFactory define a validation method like this:
@NotNull Result<Boolean> validate(DataFlowRequest request);

Although the Boolean wrapped type does not mean anything and in fact is not used by anyone. The propose would be to have them represented by a simpler:
@NotNull Result<Void> validate(DataFlowRequest request);

Which Areas Would Be Affected?
data-plane
Why Is the Feature Desired?
api expressiveness
Solution Proposal
To make the API not break from day to night, a good approach could be to define a new method with a default behavior like
default @NotNull Result<Void> validateRequest(DataFlowRequest request) {
    return validate(DataFlowRequest request).mapTo();
}

then deprecate the validate method and suggesting to override the validateRequest as the validate will be removed soon.
change the call to validate to validateRequest

Hello @ndr-brt, the code you mentioned is to be changed only on DataSourceFactory and DataSinkFactory and deprecate the validate. Also, we need to change the call from validate to validateRequest wherever used.

Hello @ndr-brt, the code you mentioned is to be changed only on DataSourceFactory and DataSinkFactory and deprecate the validate. Also, we need to change the call from validate to validateRequest wherever used.

yes, that's what I wrote in the issue

repo: eclipse-edc/Connector


text:
A way to locate configurations in known locations

As an application developer or deployer, I expect that the configuration file(s) can be found or deployed into predictable location(s), so that I can easily determine what the configuration is.
Source: https://github.com/eclipse-ee4j/config/discussions/27#discussioncomment-1809272

If config is in a jar, it must be under a known file location e.g. meta-inf/config/ with a file name and file extension
If config is in file system, it must be under a known path.

Classpath: we need to use a known resource (such as a file name config with a supported suffix (properties, yaml)). We need to support runtimes that do not support runtime classpath scanning.

authors: Emily-Jiang tomas-langer


text:
Release CI/CD pipeline

We need to create a release CI/CD pipeline for this project.
Use these documents as a reference:

How to release the first Eclipse version of projects
JSONP release job

Release jobs have been created:
https://jenkins.eclipse.org/jaf/job/jaf-branch-build-release/
https://jenkins.eclipse.org/jaf/job/jaf-branch-release-final/


text:
Add some language improvements and rephrasing to the SDV intro tutorial

This PR fixes some typos and adds some rephrasing and additional links to make the SDV intro tutorial more accessible

@eriksven WDYT?

repo: eclipse-leda/leda


text:
Create RDS postgresql instance

Create pass database
System property in pass-core results in schema creation on app launch

Created the database pass-core-db. Have been investigating how to launch pass-core against it to test the setup.

authors: dkriethof markpatton

repo: eclipse-pass/main


text:
GH-4878 optimise sub-select

GitHub issue resolved: #4878
Briefly describe the changes proposed in this PR:

PR Author Checklist (see the contributor guidelines for more details):

[ ] my pull request is self-contained
[ ] I've added tests for the changes I made
[ ] I've applied code formatting (you can use mvn process-resources to format from the command line)
[ ] I've squashed my commits where necessary
[ ] every commit message starts with the issue number (GH-xxxx) followed by a meaningful description of the change

Develop branch
This branch
Benchmark                                                     Mode  Cnt    Score    Error  Units
QueryBenchmark.complexQuery                                   avgt    5    1.061 ±  0.004  ms/op
QueryBenchmark.different_datasets_with_similar_distributions  avgt    5    0.472 ±  0.002  ms/op
QueryBenchmark.groupByQuery                                   avgt    5    0.606 ±  0.003  ms/op
QueryBenchmark.long_chain                                     avgt    5  172.897 ± 18.938  ms/op
QueryBenchmark.lots_of_optional                               avgt    5   44.313 ±  3.020  ms/op
QueryBenchmark.minus                                          avgt    5  914.117 ± 23.632  ms/op
QueryBenchmark.nested_optionals                               avgt    5   64.688 ±  2.071  ms/op
QueryBenchmark.pathExpressionQuery1                           avgt    5    5.386 ±  0.596  ms/op
QueryBenchmark.pathExpressionQuery2                           avgt    5    0.478 ±  0.027  ms/op
QueryBenchmark.query_distinct_predicates                      avgt    5   53.481 ±  1.733  ms/op
QueryBenchmark.simple_filter_not                              avgt    5    1.878 ±  0.519  ms/op

@JervenBolleman Any chance you could take a look at this PR? I made a test, but I didn't make a benchmark query yet. The benchmark run I did shows that there at least doesn't seem to be any performance degradation.

@JervenBolleman I actually found out that the QueryJoinOptimizer is able to optimise sub-selects, but not if there are multiple sub-selects or if there are any BIND clauses anywhere. I've made two benchmarks that will make sure that we don't break that optimisation later.


text:
GH-5055 make mapdb3 default for the FedX engine as well

GitHub issue resolved: #5055
Briefly describe the changes proposed in this PR:
Also use MapDB3 for FedX
Hand tested that this resolves the reported problem

I will try regarding the test case. I also want to mark the mapdb1 as
deprecated.
On Sat, Jun 29, 2024, 18:48 Håvard M. Ottestad @.***>
wrote:

@.**** approved this pull request.
LGTM! Thanks for fixing this.
Any chance you'd like to create a test so that we can increase our test
coverage of the workbench?
https://github.com/eclipse-rdf4j/rdf4j/blob/main/e2e/tests/workbench.spec.js
We use Playwright: https://playwright.dev
—
Reply to this email directly, view it on GitHub
https://github.com/eclipse-rdf4j/rdf4j/pull/5067#pullrequestreview-2149726810,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAHQYFMLISGJUGYENZ3F3SDZJ3QO5AVCNFSM6AAAAABKDJKSF2VHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDCNBZG4ZDMOBRGA
.
You are receiving this because you were assigned.Message ID:
@.***>


text:
GH-5149 Lucene numdocs param

GitHub issue resolved: #5149
Briefly describe the changes proposed in this PR:
I added a virtual property to specify the maximum amount of results the user wants in a LuceneSail search.
For example, with the example in rdf4j.org it gives something like that:
PREFIX search: <http://www.openrdf.org/contrib/lucenesail#>

?subj search:matches [
	      search:query "search terms...";
	      search:numDocs 200 ] .

At the same time, I added the sail parameter maxQueryDocuments to set the maximum amount of documents the user can query. By default, it takes the value of maxDocuments to keep a backward compatibility.
LuceneSail lc = new LuceneSail();
lc.setParameter(LuceneSail.MAX_QUERY_DOCUMENTS_KEY, "200");

PR Author Checklist (see the contributor guidelines for more details):

[x] my pull request is self-contained
[x] I've added tests for the changes I made
[x] I've applied code formatting (you can use mvn process-resources to format from the command line)
[x] I've squashed my commits where necessary
[x] every commit message starts with the issue number (GH-xxxx) followed by a meaningful description of the change

This looks very good. Thanks for the tests!
I've added some comments. In particular I'm a bit unsure about the introduction of a second max config option.


text:
chore(consortia): fix reference to secret

Description
consortia: fix reference to secret
Why
https://github.com/eclipse-tractusx/portal/issues/230
Checklist

[x] I have performed a self-review of my changes

merged with https://github.com/eclipse-tractusx/portal/pull/246

repo: eclipse-tractusx/portal


text:
Migrate Tractus EDC to 0.6.x

As ... ,
I want ... ,
so that ... .
Hints / Details

...

Outcome / Acceptance Criteria

Outcome

...

Acceptance Criteria

Local Deployment has been updated
INT deployments have been updated
Code changes - if needed - have been done

Out of Scope

...

Update of EDC has a problem with proxyMethod. I asked in the EDC Chatgroup: https://matrix.to/#/!mYxOilDPMLCQhMoIVc:matrix.eclipse.org/$umGUGgudYbvGIQSeETJgJXN9RBxgZ9wo3lMgZc5k5yY?via=matrix.eclipse.org&via=matrix.org&via=dev-null.rocks

authors: f-zimmer tom-rm-meyer-ISST

repo: eclipse-tractusx/puris


text:
Helm chart structure check fix

exclude non-chart folders in the helm chart structure

@tomaszbarwicki Not sure, if we should create a new issue or if it directly relates to this issue:
We have a mono repo with following structure in which the charts/puris-backend/Chart.yaml is not found. See run.
Structure:

backend
charts/
charts/frontend/
charts/backend/
docs/
docs/README.md
backend

We don't yet follow the TRG 5.08 for product chart. Maybe that's the reason?

authors: tom-rm-meyer-ISST tomaszbarwicki

repo: eclipse-tractusx/sig-infra


text:
[Compatible Implementations Announcement] MP 5.0 - WildFly 27.0.0.Final

Organization Name
Name: Red Hat
Product Version and download URL
URL: WildFly 27.0.0.Final
Java runtime used to run the implementation
TCK results - JDK 11, 17
Media Description
Just mention please @WildFlyAS on Twitter.
Design Card  (for MicroProfile designer)
Notes

CCR - https://github.com/eclipse/microprofile/issues/333

scheduled

authors: rstjames xstefank

repo: eclipse/microprofile-marketing


text:
June 18th 2024 MicroProfile Technical Meeting video for YouTube

Here is the link to the video for upload to YouTube. Please update the Meeting Minutes with a link to the recording.
Thanks!

https://youtu.be/ZoVKa8Qu_2I

authors: jclingan rstjames


text:
Content of microprofile-config.properties contains entries for non selected specifications

In the case Config and/or Rest Client is not selected, the file microprofile-config.properties still contains values of the examples for those spec examples.

Fixed By #243

repo: eclipse/microprofile-starter


text:
Docker build should act like the maven build and use the local code instead of downloading a different version of RDF4J

The docker build currently has three different dockerfiles that use two different approaches for building. One uses the local code and another uses a downloaded version of rdf4j. We should always use the local code. If we want to build an older version we should checkout git branch instead.

This issue is still in the inbox/triage column, but it has an associated pull request (closed, unmerged, unsure why). What's the status?

Need to fix one thing based on feedback from Bart.

See also #1439

@hmottestad has this now been addressed?

If I understand the files correctly, docker will now indeed use the local version.
Perhaps useful to include the experimental docker option "--squash" to squash layers: if not, the COPY to copy the rdf4j.zip (which is only use to obtain the wars) from the local build directory into the docker image will make the docker image at lot larger, even if the file is removed from docker image afterwards
removing the file in docker and squashing should remove the temporary zip from the docker file system

authors: barthanssens hmottestad jeenbroekstra


text:
Add support for optional package name

In case a package has a different name than the library, the path might never be found.
Case in point odc (in pyodc project):

Library name: odccore
Library filename: libodccore.{so,dylib}
Supported environment variables: ODC_DIR, odc_DIR

By providing an optional package name as a second parameter to find(), we can check expected environment variables. Additionally, support for both upper and lowercase variable names has been added and search extended to two architectures (lib and lib64).
Test suite based on pytest and pytest-mock was also added, since the module lacked any tests.
The README was suitably extended to document the new behaviour.q

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

authors: FussyDuck dvuckovic

repo: ecmwf/findlibs


text:
Feature/irregular grid mapper

Create an irregular grid mapper which handles irregular grids and uses a different engine slicer

Codecov Report
Attention: Patch coverage is 60.44905% with 229 lines in your changes are missing coverage. Please review.

Project coverage is 86.26%. Comparing base (2c8787d) to head (04a8a74).
Report is 51 commits behind head on develop.

:exclamation: Current head 04a8a74 differs from pull request most recent head 9fb93c9. Consider uploading reports for the commit 9fb93c9 to get more accurate results

Files
Patch %
Lines

tests/test_quad_tree.py
23.52%
78 Missing :warning:

polytope/datacube/quad_tree.py
78.37%
24 Missing :warning:

tests/test_quadtree_indices.py
28.00%
18 Missing :warning:

tests/test_quadtree_optimisation.py
33.33%
18 Missing :warning:

tests/test_polytope_extract_fdb.py
34.61%
17 Missing :warning:

polytope/engine/quadtree_slicer.py
70.83%
14 Missing :warning:

tests/test_quadtree_edge_cases.py
38.88%
11 Missing :warning:

polytope/engine/engine.py
40.00%
9 Missing :warning:

polytope/datacube/backends/fdb.py
0.00%
8 Missing :warning:

polytope/datacube/backends/quad_test.py
0.00%
8 Missing :warning:

... and 6 more

Additional details and impacted files
@@             Coverage Diff             @@
##           develop     #112      +/-   ##
===========================================
- Coverage    88.45%   86.26%   -2.20%
===========================================
  Files           83       95      +12
  Lines         7131     7672     +541
===========================================
+ Hits          6308     6618     +310
- Misses         823     1054     +231

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

authors: codecov-commenter mathleur

repo: ecmwf/polytope


text:
真机调试下报错：HTMLCanvasView is not defined

提问前应该做的事
请确保提问前做了以下事，将完成的项目的 [] 改为 [x]：

[x] 我已通读过 README
[x] 我已阅读过 FAQ

需提供的信息
将符合项的 [] 改为 [x]，并补充需要的信息：
简单描述问题：
真机调试的结果是否会影响到实际的真机效果
预期效果：
没有报错
实际效果：
预览模式下不存在该问题(定制的echarts文件需改名称echarts.min.js--->echarts.js在预览模式下才能不报错,否则一样的错误)

复现环境：

[x] 在微信开发工具中存在该问题
1.真机调试模式存在该问题
2官方示例（lazyload示例），

me too

我也遇到同样的问题

+1  有解决办法吗？

实测，在真机调试下的错误，到实体设备上不影响使用。但是我还是希望官方能给出解释、或者修复此问题

遇到同样问题，请问解决了嘛？请提供一下思路。谢谢啦

authors: Ttomsjson curiousbabyMz godoge sjfkai yiguozhen0510

repo: ecomfe/echarts-for-weixin


text:
已经构建了echarts的工程，如何运行测试用例？

One-line summary [问题简述]
我改了点代码，想看看效果。已经npm install和webpack构建了工程，如何执行/test/下的测试html？打开这些html显示文件404:
Failed to load resource: net::ERR_FILE_NOT_FOUND
path.js Failed to load resource: net::ERR_FILE_NOT_FOUND
Path.js Failed to load resource: net::ERR_FILE_NOT_FOUND
Image.js Failed to load resource: net::ERR_FILE_NOT_FOUND
Text.js Failed to load resource: net::ERR_FILE_NOT_FOUND
Version & Environment [版本及环境]

ECharts version [ECharts 版本]:
Browser version [浏览器类型和版本]:
OS Version [操作系统类型和版本]:

Expected behaviour [期望结果]
ECharts option [ECharts配置项]

option = {

}

Other comments [其他信息]

下载 https://github.com/ecomfe/zrender 到 echarts 的同级目录

authors: logicouter pissang

repo: ecomfe/echarts


text:
🛑 NAS is down

In 34730bb, NAS (https://ddns.ecwuuuuu.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: NAS is back up in 87ca79d.

repo: ecwu/uptime


text:
ERROR: can't convert Array into String when using with "oh-my-zsh" cookbook

Hello,
I am getting the following error when I use this cookbook with: https://supermarket.getchef.com/cookbooks/oh-my-zsh#librarian

==> default: [2014-08-09T12:39:30+00:00] ERROR: can't convert Array into String
==> default:
==> default: ================================================================================
==> default: Recipe Compile Error in /tmp/vagrant-chef-3/chef-solo-1/cookbooks/oh-my-zsh/recipes/default.rb
==> default: ================================================================================
==> default:
==> default:
==> default: TypeError
==> default: ---------
==> default: can't convert Array into String
==> default:
==> default:
==> default: Cookbook Trace:
==> default: ---------------
==> default:   /tmp/vagrant-chef-3/chef-solo-1/cookbooks/chef-solo-search/libraries/search/overrides.rb:91:in `search_data_bag'
==> default:   /tmp/vagrant-chef-3/chef-solo-1/cookbooks/chef-solo-search/libraries/search/overrides.rb:48:in `search'
==> default:   /tmp/vagrant-chef-3/chef-solo-1/cookbooks/chef-solo-search/libraries/search.rb:69:in `search'
==> default:   /tmp/vagrant-chef-3/chef-solo-1/cookbooks/oh-my-zsh/recipes/default.rb:23:in `from_file'
==> default:
==> default:
==> default: Relevant File Content:
==> default: ----------------------
==> default: /tmp/vagrant-chef-3/chef-solo-1/cookbooks/chef-solo-search/libraries/search/overrides.rb:
==> default:
==> default:  84:          end
==> default:  85:        end
==> default:  86:        return _result
==> default:  87:      end
==> default:  88:
==> default:  89:      def search_data_bag(_query, bag_name, start, rows, &block)
==> default:  90:        _result = []
==> default:  91>>       data_bag(bag_name.to_s).each do |bag_item_id|
==> default:  92:          bag_item = data_bag_item(bag_name.to_s, bag_item_id)
==> default:  93:          if _query.match(bag_item)
==> default:  94:            _result << bag_item
==> default:  95:          end
==> default:  96:        end
==> default:  97:        return _result
==> default:  98:      end
==> default:  99:    end
==> default: 100:  end
==> default:
==> default:
==> default:

Can you please help me out here?

I'm having the same error when trying to fetch either a data bag or a data bag item. I agree; it's apparently a problem in the data_bag function itself.

authors: SamuelDavis munjalpatel

repo: edelight/chef-solo-search


text:
Table of unclassified expenses per delegate

As a user I would like to see a table in which I find the information of all the different delegates where I show all the unclassified expenses.
This will help the community to have a better understanding of how resources are spent.

this issue is done

repo: edenia/eden-spend-explorer


text:
Feat/refactor boilerplate

New Webapp Boilerplate
What does this PR do?

Update to React 18
Update React Router to v6
Add TypeScript into the project
Update Dev dependencies
Configuration for EsLint and Prettier
Modify Project structure in order to add new folders
Add UAL hook (by Edenia Labs)
Migrate Context, components, layouts, routers pages, hooks, graphql and config files to Typescript version
Improve mobile/desktop performance
Increase google metrics such as Accessibility, Best practice and SEO
Configure module resolver plugin
Update README file

Steps to test

run yarn
run yarn start
go to localhost:3000

CheckList

[ ] Follow proper Markdown format
[ ] The content is adequate
[ ] The content is available in both english and spanish
[ ] I Ran a spell check

great work @tetogomez !
cam we replicate this is the full stack boilerplate?

@xavier506 sure thing!!

repo: edenia/webapp-boilerplate


text:
documentaion review

The documentation needs to be reviewed for completeness.
All ... should be replaced with meaningful descriptions.
Examples should be added where appropriate.

After adding all the auto generated errors the godoc output is almost unusable. It is quite difficult to find anything or determine what is important in the enormous list of error names (see first image). It seems much more useful with all the errors removed (see second image). If the error types were moved to a separate package godoc would put the errors on their own page. I'm not sure if this is a good idea since the API is probably nicer to use with only one package. @1st1 what do you think?

After adding all the auto generated errors the godoc output is almost unusable. It is quite difficult to find anything or determine what is important in the enormous list of error names (see first image). It seems much more useful with all the errors removed (see second image). If the error types were moved to a separate package godoc would put the errors on their own page. I'm not sure if this is a good idea since the API is probably nicer to use with only one package. @1st1 what do you think?

Ю I'm not sure if this is a good idea since the API is probably nicer to use with only one package. @1st1 what do you think?
I think it's a good idea. Do you have any good example of how the separate package for errors would make code look worse?  We can probably keep the root Error (which should be called EdgeDBError, no?) type in the main package.

Ю I'm not sure if this is a good idea since the API is probably nicer to use with only one package. @1st1 what do you think?
I think it's a good idea. Do you have any good example of how the separate package for errors would make code look worse?  We can probably keep the root Error (which should be called EdgeDBError, no?) type in the main package.

the root Error (which should be called EdgeDBError, no?)

I don't think so. In go you must always use the package name when referring to imported identifiers, so this will always be edgedb.Error.

the root Error (which should be called EdgeDBError, no?)

I don't think so. In go you must always use the package name when referring to imported identifiers, so this will always be edgedb.Error.

Do you have any good example of how the separate package for errors would make code look worse?

In go you can't nest package names like this edgedb.errors.SomeError you can only write something like errors.SomeError so I'm not sure what the package should be called. There are already several prominent packages called errors and error is a built in type name. Maybe edberr or edgedberr. edgedberr feels long to me especially considering how long most of the error names are already. Some other name... My hesitation in breaking out a separate error package is only because edgedb.SomeError seems like the nicest name.

Do you have any good example of how the separate package for errors would make code look worse?

In go you can't nest package names like this edgedb.errors.SomeError you can only write something like errors.SomeError so I'm not sure what the package should be called. There are already several prominent packages called errors and error is a built in type name. Maybe edberr or edgedberr. edgedberr feels long to me especially considering how long most of the error names are already. Some other name... My hesitation in breaking out a separate error package is only because edgedb.SomeError seems like the nicest name.

We can probably keep the root Error type in the main package.

We could but why is it special? Keeping it in the main package might make be misleading for someone that is just skimming the documentation. It would look like there is only one error type. It seems better to me to keep all error types and ErrorTag in the same package whichever that ends up being.

We can probably keep the root Error type in the main package.

We could but why is it special? Keeping it in the main package might make be misleading for someone that is just skimming the documentation. It would look like there is only one error type. It seems better to me to keep all error types and ErrorTag in the same package whichever that ends up being.

We could but why is it special? Keeping it in the main package might be misleading for someone that is just skimming the documentation. It would look like there is only one error type. It seems better to me to keep all error types and ErrorTag in the same package whichever that ends up being.

The use case I have in mind for keeping just the Error type in the edgedb package is that I believe most people won't check what specific error the API has returned. Basically, I imagine that a common use case would be to check if it's an EdgeDB-related error or something else. Also checking for specific errors is a somewhat advanced pattern. We can also document that there are more error types in the docs of edgedb.Error.

We could but why is it special? Keeping it in the main package might be misleading for someone that is just skimming the documentation. It would look like there is only one error type. It seems better to me to keep all error types and ErrorTag in the same package whichever that ends up being.

The use case I have in mind for keeping just the Error type in the edgedb package is that I believe most people won't check what specific error the API has returned. Basically, I imagine that a common use case would be to check if it's an EdgeDB-related error or something else. Also checking for specific errors is a somewhat advanced pattern. We can also document that there are more error types in the docs of edgedb.Error.

In go you can't nest package names like this edgedb.errors.SomeError you can only write something like errors.SomeError so I'm not sure what the package should be called. There are already several prominent packages called errors and error is a built in type name. Maybe edberr or edgedberr. edgedberr feels long to me especially considering how long most of the error names are already. Some other name... My hesitation in breaking out a separate error package is only because edgedb.SomeError seems like the nicest name.

As for naming -- I'd go with edgedberr. IMO it's nice and predictable for the user when related packages are prefixed with the name of the main package.

In go you can't nest package names like this edgedb.errors.SomeError you can only write something like errors.SomeError so I'm not sure what the package should be called. There are already several prominent packages called errors and error is a built in type name. Maybe edberr or edgedberr. edgedberr feels long to me especially considering how long most of the error names are already. Some other name... My hesitation in breaking out a separate error package is only because edgedb.SomeError seems like the nicest name.

As for naming -- I'd go with edgedberr. IMO it's nice and predictable for the user when related packages are prefixed with the name of the main package.

Is the plan to use godoc to publish the docs, or are we going to parse/integrate into the main docs like we do with Sphinx?  If it's the latter, then I think we can separate errors at the rendering stage, no?  IMO, the suckiness of the tool shouldn't be informing the package structure.

Is the plan to use godoc to publish the docs, or are we going to parse/integrate into the main docs like we do with Sphinx?  If it's the latter, then I think we can separate errors at the rendering stage, no?  IMO, the suckiness of the tool shouldn't be informing the package structure.

Is the plan to use godoc to publish the docs, or are we going to parse/integrate into the main docs like we do with Sphinx?

The plan is to do both.  A lot of go users prefer the output of godoc when they google the package. I don't expect everybody to use our website for that.

IMO, the suckiness of the tool shouldn't be informing the package structure.

My research indicates that this is actually the Go way -- layout your code to make godoc happy and produce readable results.

Is the plan to use godoc to publish the docs, or are we going to parse/integrate into the main docs like we do with Sphinx?

The plan is to do both.  A lot of go users prefer the output of godoc when they google the package. I don't expect everybody to use our website for that.

IMO, the suckiness of the tool shouldn't be informing the package structure.

My research indicates that this is actually the Go way -- layout your code to make godoc happy and produce readable results.

A lot of go users prefer the output of godoc when they google the package.

Can we maybe just stick a hyperlink to our docs or is that frowned upon?

A lot of go users prefer the output of godoc when they google the package.

Can we maybe just stick a hyperlink to our docs or is that frowned upon?

Can we maybe just stick a hyperlink to our docs or is that frowned upon?

I guess we could, but it seems to me that we'd be going against the grain with that. Maybe breaking out error types into a separate package isn't that bad?

Can we maybe just stick a hyperlink to our docs or is that frowned upon?

I guess we could, but it seems to me that we'd be going against the grain with that. Maybe breaking out error types into a separate package isn't that bad?

Can we maybe just stick a hyperlink to our docs or is that frowned upon?

It's not that its frowned upon. Its that pkg.go.dev/github.com/edgedb/edgedb-go/ is likely to be the top result for may edgedb-go related searches and people are accustomed to looking there for documentation. If the first thing they find there is terrible, its not a great first impression.

Can we maybe just stick a hyperlink to our docs or is that frowned upon?

It's not that its frowned upon. Its that pkg.go.dev/github.com/edgedb/edgedb-go/ is likely to be the top result for may edgedb-go related searches and people are accustomed to looking there for documentation. If the first thing they find there is terrible, its not a great first impression.

Random thought. This has already been discussed more or less but maybe it is worth looking at again. What about implementing the error hierarchy using a method on edgedb.Error?
err := pool.Query(...)

var edbErr edgedb.Error
if errors.As(err, &edbErr) && edbErr.Is(edgedb.ConfigureationError) {
    ...
}

This would make it so that there is only one error type. Having tones of error types or interfaces is very uncommon in go.
There would not be a need to split the edgedb package because the edgedb.XYZErrors would be constants instead of interfaces so they won't show up in the index. godoc still includes them it just puts them in the section for their type edgedb.ErrorCategory or something.

Random thought. This has already been discussed more or less but maybe it is worth looking at again. What about implementing the error hierarchy using a method on edgedb.Error?
err := pool.Query(...)

var edbErr edgedb.Error
if errors.As(err, &edbErr) && edbErr.Is(edgedb.ConfigureationError) {
    ...
}

This would make it so that there is only one error type. Having tones of error types or interfaces is very uncommon in go.
There would not be a need to split the edgedb package because the edgedb.XYZErrors would be constants instead of interfaces so they won't show up in the index. godoc still includes them it just puts them in the section for their type edgedb.ErrorCategory or something.

What about implementing the error hierarchy using a method on edgedb.Error?

Yeah. Maybe we should do that, indeed.
BTW, remind me, what API will we have for letting users access error types properties? E.g. consider I have this error type (using https://github.com/edgedb/edgedb/discussions/1849 proposal):
  error type MyError extending errors::Error {
    property app_code -> int64;
  }

How would I access the app_code property on an var edbErr edgedb.Error object?

What about implementing the error hierarchy using a method on edgedb.Error?

Yeah. Maybe we should do that, indeed.
BTW, remind me, what API will we have for letting users access error types properties? E.g. consider I have this error type (using https://github.com/edgedb/edgedb/discussions/1849 proposal):
  error type MyError extending errors::Error {
    property app_code -> int64;
  }

How would I access the app_code property on an var edbErr edgedb.Error object?

In any case, I think this is an orthogonal consideration. There is going to have to be a pattern like this for user defined errors regardless of weather we have 1 error type or many.

Not really. If we end up with a single error type we also need to figure out how we reflect various properties, built-in and user defined. Looking at https://github.com/edgedb/edgedb/discussions/1849, how would I unpack something like Error.location, a tuple type, using the Property(...) API you suggested?
(I'm only using Error.location as an example here; there will be other complex properties defined on child built-in error types, so they'll have to be accessed via Property(...).)

Perhaps more relevant, having a single error type with a method like Is(edgedb.ErrorCategory) bool allows the category checking to be extended to user defined types using the same mechanism. The error category type might be type ErrorCategory string and the value could be the fully qualified type name "mymod::UserError3". I'm not sure it would be practical, but it at least seems possible.

Sure, that works.

In any case, I think this is an orthogonal consideration. There is going to have to be a pattern like this for user defined errors regardless of weather we have 1 error type or many.

Not really. If we end up with a single error type we also need to figure out how we reflect various properties, built-in and user defined. Looking at https://github.com/edgedb/edgedb/discussions/1849, how would I unpack something like Error.location, a tuple type, using the Property(...) API you suggested?
(I'm only using Error.location as an example here; there will be other complex properties defined on child built-in error types, so they'll have to be accessed via Property(...).)

Perhaps more relevant, having a single error type with a method like Is(edgedb.ErrorCategory) bool allows the category checking to be extended to user defined types using the same mechanism. The error category type might be type ErrorCategory string and the value could be the fully qualified type name "mymod::UserError3". I'm not sure it would be practical, but it at least seems possible.

Sure, that works.

how would I unpack something like Error.location, a tuple type, using the Property(...) API you suggested?

Using the 2 return value approach would look something like this:
err := con.Query(...)
var edbErr edgedb.Error
if errors.As(err, &edbErr) {
    location, ok := edbErr.Property("location")
    if ok {
        lineNo := location.([]int64)[0]
    }
}

But with known properties we aren't limited to a completely generic method. There can be methods that return a struct when the type implements that field and returns nil otherwise. This would be reminiscent of the net package's Error type. Its also nicer to work with because it doesn't require type assertions everywhere because the return value is typed Location() *struct{ LineNo int }.
err := con.Query(...)
var edbErr edgedb.Error
if errors.As(err, &edbErr) {
    location := edbErr.Location()
    if location != nil {
        fmt.Println(location.LineNo)
    }
}

how would I unpack something like Error.location, a tuple type, using the Property(...) API you suggested?

Using the 2 return value approach would look something like this:
err := con.Query(...)
var edbErr edgedb.Error
if errors.As(err, &edbErr) {
    location, ok := edbErr.Property("location")
    if ok {
        lineNo := location.([]int64)[0]
    }
}

But with known properties we aren't limited to a completely generic method. There can be methods that return a struct when the type implements that field and returns nil otherwise. This would be reminiscent of the net package's Error type. Its also nicer to work with because it doesn't require type assertions everywhere because the return value is typed Location() *struct{ LineNo int }.
err := con.Query(...)
var edbErr edgedb.Error
if errors.As(err, &edbErr) {
    location := edbErr.Location()
    if location != nil {
        fmt.Println(location.LineNo)
    }
}

@fmoor, as we discussed on the call, let's rewrite the API to follow the design you outlined in https://github.com/edgedb/edgedb-go/issues/64#issuecomment-765014347.

@fmoor, as we discussed on the call, let's rewrite the API to follow the design you outlined in https://github.com/edgedb/edgedb-go/issues/64#issuecomment-765014347.

authors: 1st1 elprans fmoor

repo: edgedb/edgedb-go


text:
No TLS Option for Reverse Proxies

Add an option to disable TLS for serving the admin ui behind a reverse proxy. I believe this should definitely be an feature and would make things much easier.

Got some information on this today. It turns out, you're already able to disable TLS on the server by launching with edgedb-server —http-endpoint-security=optional. That should do what you want to do, although we don't recommend it because it leaves your connection to the EdgeDB endpoint unencrypted. Just make sure you're aware of that before you proceed.
I'll go ahead and close this since the option is already available, but let me know if you feel this doesn't address your issue.

That leaves me to wonder why the EDGEDB_SERVER_HTTP_ENDPOINT_SECURITY env var isn't documented properly. It's just in the 1.0 RC 2 changelog.

authors: kyuuaria raddevon

repo: edgedb/edgedb


text:
[frontend] Add Base Images

Based on #240
Adds forms and logic to create, update and delete Base Images.
Create Base Image:
https://user-images.githubusercontent.com/26611935/218417772-beb2610b-234e-45b0-b899-b3b08c5bd88c.mp4
Update and delete Base Image:
https://user-images.githubusercontent.com/26611935/218417983-fd11b138-925c-4b96-b2c6-7d49da364354.mp4

Pull Request Test Coverage Report for Build 4161900113

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-80.3%) to 0.0%

Totals

Change from base Build 72a69ac6dc2a9b1897ecba915757169dad1f898b:
-80.3%

Covered Lines:
0

Relevant Lines:
0

💛  - Coveralls

authors: coveralls szakhlypa

repo: edgehog-device-manager/edgehog


text:
feat: image generation

To get to a fully functional Image Generation endpoint, the following is required:

Design the API

[ ] Design a new Image Generation endpoint interface, since OpenAI does not have one we can mimic. This should be the first step, as everything else depends on this.

Implement a backend

[ ] Implement a backend using candle that can at least provide the API's functionality. It doesn't necessarily have to implement the API directly, it can (maybe should) be a fully featured backend similar to llama.cpp or whisper.cpp. It's up to the endpoint implementation later to directly implement the API, not the backend. Image generation example in candle: https://github.com/huggingface/candle/blob/main/candle-examples/examples/stable-diffusion/main.rs

Edgen implementation

[ ] Define an Image Generation endpoint that follows the API directly and translates the API calls to backend calls. This may be implemented according to the already existing traits LLM and Whisper traits in edgen_core.
[ ] Implement the model endpoint according to the LLM and Whisper endpoints in edgen_server.
[ ] Implement the loading and downloading logic for the new model kind in edgen_server/src/model.rs.
[ ] Implement the new endpoint using the backend. edgen_server/src/openai_shims.rs may provide some inspiration.
[ ] Implement new server routes for the API and connect it to the endpoint (in edgen_server/src/routes.rs).

hi @francis2tm  can you assign the issue to me, also, let's have a call to discuss the structure of the codebase later this week

repo: edgenai/edgen


text:
Implement the design: SMA to get Metrics via Executor.

This issue tracks the implementation of the design that was created previously per Issue#1414
The goal here is to refactor metrics collection - moving metrics collection to the executor so that it can remain platform and even service implementation agnostic.
Effectively, this is a direct follow-up to: Issue #1414

@anonymouse64
I agree with your assessment (made on several abandoned PRs related to the system executor) that we should have a standard contract for metrics and, further, that we should also return the raw metrics for optional consumption.
The Fuji road map specifies:

Refactor metrics collection - moving metrics collection to the executor so that it can remain platform and even service implementation agnostic.

I believe this implies the executor will become the source of metric collection and the existing service-based metric collection implementation and endpoints will be removed.  I discussed this with @akramtexas this morning and I'll be working to obtain clarity from @jpwhitemn on this point when he returns from his vacation next week.

@michaelestrin the discussion I had with Jim and Akram was that we would keep the service-based metric collection as an option for non-docker based implementations such as the snap or native process deployments, etc. So you can pick which implementation to use from the configuration.

@anonymouse64
That makes sense to me.  Services in non-containerized environments would be the likeliest source for metrics.  You could obtain them by querying a separate OS-specific process (i.e. top) but I'm not sure why one would take on the added complexity.
Which raises a separate but related question -- why not continue to use the service-based metric collection implementation for Docker-based deployments (i.e. what is the value of having the executor handle metrics collection for Docker-based deployments)?
I appreciate everyone's patience.  I'm not trying to be difficult or to change the existing agreements or design.  I'm just trying to understand why we're doing what we're doing the way we're doing it.

TBH, I don't recall the reasoning for creating a new docker-specific implementation... I think we should have 2 choices for collecting metrics:

ask the service through the service endpoints, like what we do today
call out to an arbitrary binary that responds in JSON or some other structured format

The second option allows folks running inside different distribution mechanisms or where they have more accurate or useful metrics to implement their own and use it instead.

@anonymouse64 That's helpful.  Thank you.  Perhaps the Docker-specific implementation is intended as an example implementation of an arbitrary binary.  I'll proceed under that assumption.

Good discussion here, @michaelestrin and @anonymouse64, and I appreciate it: Our goal, as an open-source community, is to help steer System Management (in its evolution) in the right direction forward, in the best way possible.
Yes, one of the goals of the roadmap for the Fuji Release is to "Refactor metrics collection - moving metrics collection to the executor so that it can remain platform and even service implementation agnostic."
I thank you, @anonymouse64, for succinctly capturing here per the discussion (from a little while ago) that we would keep the service-based metric collection as an option for non-Docker based implementations such as the snap or native process deployments, etc., whereby you can pick which implementation to use from the configuration.

@anonymouse64 That's helpful. Thank you. Perhaps the Docker-specific implementation is intended as an example implementation of an arbitrary binary. I'll proceed under that assumption.

@michaelestrin, you are correct in this assumption: The Docker-specific implementation is indeed intended as a reference implementation of an arbitrary binary 👍

Michael graciously joined hands with me to tackle this issue. I've transitioned the completion of the associated work to him. As such, the (original) PR associated with this issue (PR-1672) has been closed. As for the original feature branch on which I had done the relevant work, it reflects the valuable feedback I got from Michael, as well as the invaluable pair-programming sessions we did, and for which I'm most grateful 👍

I propose a standard contract for metrics that specifies four values -- cpuUsedPercent, memoryUsedPercent, rawType, and rawResult.  All four will be required, will be provided by all metric gathering implementations, and may require a specific implementation to normalize/transform its gathered data.  Sample result from the example Docker executor follows:
{
  "operation": "metrics",
  "service": "edgex-core-data",
  "success": true,
  "cpuUsedPercent": 1.73,
  "memoryUsedPercent": 0.11,
  "rawType": "DockerExecutor",
  "rawResult": {
    "cpu_perc": "1.73%",
    "mem_usage": "8.582MiB / 7.786GiB",
    "mem_perc": "0.11%",
    "net_io": "246MB / 418MB",
    "block_io": "14.9MB / 0B",
    "pids": "19"
  }
}

This provides a basic set of universal metrics that do not require a metrics consumer to have knowledge of the underlying metrics gathering implementation.  The raw data (and a corresponding type indicator) is provided should a consumer wish to go beyond the contract to obtain implementation-specific metrics data.
Thoughts @anonymouse64?

LGTM @michaelestrin

First pass work merged.  PR with refactored agent and unit tests to follow.

First pass work merged. PR with refactored agent and unit tests to follow.

@michaelestrin Now that the associated PR has been merged should we close this issue and track remaining work in additional issues?

Agreed.

repo: edgexfoundry/edgex-go


text:
Create common EdgeX error type

🚀 Feature Request
Relevant Package
All core services and possibly consumers of core services.
Description
At the router level in the EdgeX services, there is a lot of logic regarding error handling. Specifically type checking and mapping to a relevant HTTP response code. For example,
https://github.com/edgexfoundry/edgex-go/blob/03f28e5980c37459c208a296556b0d148bea68db/internal/core/metadata/rest_deviceprofile.go#L108-L117
Describe the solution you'd like
I think we can create a common error type which encapsulates all the necessary data(HTTP response code, description, etc...) so that when errors bubble up to the router we can  simply extract the HTTP response code, rather then checking for a specific type and duplicating the logic. This is more evident as we are incorporating the operator pattern in the REST handlers where we are attempting to abstract the business logic from the REST handler and have the operator simply return an error to the caller(REST handler). For example,
https://github.com/edgexfoundry/edgex-go/blob/818be3dfd721e644cbac9b5acdcbef0f0d1fb2ce/internal/core/metadata/rest_device.go#L88-L89
Taking this a step further, I think we can create an interface to which all of our custom errors would conform. We can than return that interface type in our functions(rather than the standard error)
Going even further, I think this will allow us to communicate errors more effectively to clients. Right now, we rely solely on the HTTP status code. If we standardise the errors we would be able to respond to the user with the common error marshaled in the response body. This would allow the client to serialise the custom error type and handle the information how they want, most likely log.
Describe alternatives you've considered
None, the alternative to this feature is to continue to handle errors as we are today.

I want to make sure you're aware of this type in go-mod-core-contracts
That error type is used for service to service interactions. The use case is that Service A calls Service B. Some error happens in Service B and the call returns to Service A. When Service A replies to its caller, we want the details of Service B's error to be passed through.
Having said, that, it sounds like you're referring to something else -- whereby the error type checking we currently perform is encapsulated within a more streamlined API for use in the router. This layer would need to handle errors caused by a service to service call and also errors that cause an in-process unwinding of the stack. The type checking of errors from the lower layers shown in the example above would be wrapped by the proposed type. If that's correct, is your proposal to adopt this on a service by service basis or to implement something across the platform?

The ErrServiceClient does handle the functionality I am referring to regarding service to service communication, I completely missed that :disappointed:.
I was thinking of implementing something for the lower layers across the platform for consistency and possibly reduction in code.

As I thought about this a little more, I realized that the ErrServiceClient is one half of the issue I am mentioning. The ErrServiceClient is useful when the client receives an error from another API and turns an HTTP response code and body into a struct to be bubbled up the call stack. The other half of this is the invoked API does not return useful information to the client. For example, in some of our creation APIs we return true if the operation is successful, but return only a status code(500,404,419,etc) when the operation fails. The client is never given any additional information, like a message, description, or reason. What I am proposing here is that from the invoked API's perspective we use a common "error struct"  when responding with a non 2xx response. That way the client can then translate that common error into an ErrServiceClient with the body and status code populated. This will allow the client to handle the error more effectively. Futhermore, using a common struct will allow us to respond in the appropriate format, like JSON or YAML.
I am thinking from the two different perspectives when it comes to this issue:

A non-EdgeX-service invoking EdgeX APIs - The current implementation can make it difficult when dealing with non 2xx responses as the problem may not be clear to the client.

Distributed EdgeX platform - Tracing an error can be more difficult if the information as to why a request failed is only located within the logging system of the API which generated the error.

What I am proposing here is that from the invoked API's perspective we use a common "error struct" when responding with a non 2xx response.

Related https://github.com/edgexfoundry/edgex-go/issues/1573


text:
feat: Add new build-noziti and docker-noziti targets into Makefile

related to https://github.com/edgexfoundry/go-mod-bootstrap/pull/795
To allow to build services without openziti, add new targte build-noziti and docker-noziti into Makefile. Also revise README.md to include such information.

If your build fails  due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/edgex-go/blob/main/.github/Contributing.md
PR Checklist
Please check if your PR fulfills the following requirements:

[x] I am not introducing a breaking change (if you are, flag in conventional commit message with BREAKING CHANGE: describing the break)
[x] I am not introducing a new dependency (add notes below if you are)
[ ] I have added unit tests for the new feature or bug fix (if not, why?)
[ ] I have fully tested (add details below) this the new feature or bug fix (if not, why?)
[ ] I have opened a PR for the related docs change (if not, why?)

Testing Instructions

New Dependency Instructions (If applicable)

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 28.07%. Comparing base (187954f) to head (8a1c9a0).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main    #5004   +/-   ##
=======================================
  Coverage   28.07%   28.07%
=======================================
  Files         243      243
  Lines       17591    17591
=======================================
  Hits         4938     4938
  Misses      11525    11525
  Partials     1128     1128

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

🚨 Try these New Features:

Flaky Tests Detection - Detect and resolve failed and flaky tests

authors: codecov-commenter judehung


text:
"container = client.containers.get(containerName)" alternative for non-docker environment

Hi @cloudxxx8 ,
In case of the test cases where the requirement is to get information of the service container running, the following command is being used ,
**container = client.containers.get(containerName)**
where,
client = docker.from_env()
Now, when I need to implement the test case for non-docker environment, what can I use as an alternative for client.containers.get() and docker.from_env() ?
Please let me know for any suggestions. Thanks in advance.

Close this issue due to no activity. If you have further question, please file questions on Github Discussions (https://github.com/orgs/edgexfoundry/discussions). Thank you.

authors: cherrycl dipshirajput

repo: edgexfoundry/edgex-taf


text:
Fix missing exvcr custome path causing error

This PR fixes the issue when running the MIX_ENV=test mix vcr where missing custom_cassette_library_dir will default to nil.
...
** (FunctionClauseError) no function clause matching in IO.chardata_to_string/1

    The following arguments were given to IO.chardata_to_string/1:

        # 1
        nil

    Attempted function clauses (showing 2 out of 2):

        def chardata_to_string(string) when is_binary(string)
        def chardata_to_string(list) when is_list(list)

    (elixir 1.10.3) lib/io.ex:572: IO.chardata_to_string/1
    (elixir 1.10.3) lib/file.ex:214: File.exists?/2
    lib/exvcr/task/runner.ex:17: anonymous fn/1 in ExVCR.Task.Runner.show_vcr_cassettes/1
    (elixir 1.10.3) lib/enum.ex:783: Enum."-each/2-lists^foreach/1-0-"/2
    (elixir 1.10.3) lib/enum.ex:783: Enum.each/2
    (mix 1.10.3) lib/mix/task.ex:330: Mix.Task.run_task/3
    (mix 1.10.3) lib/mix/cli.ex:82: Mix.CLI.run_task/2

Coverage remained the same at 92.097% when pulling ee8726690d2a340310f6480a1de3333fb9b01436 on kianmeng:fix-mix-vcr-path-error into dc2ac9130c4a84e1be5a9e0a71fcda33f5b3d67a on edgurgel:master.

Thank you!

authors: coveralls edgurgel kianmeng

repo: edgurgel/tentacat


text:
Persist queue stats counts to Redis

Related to #32
TODO

[x] Save per queue counts
[x] Save total counts

Changes Unknown when pulling 2c153e4b2034fecaddf565bb388d0d213b7c3fec on iurifq:persist_queue_stats into ** on edgurgel:master**.

Changes Unknown when pulling cd05a6df493a913598c2a9e9893734d1284289ac on iurifq:persist_queue_stats into ** on edgurgel:master**.

Changes Unknown when pulling 3dfd626b2e72260c65052e8bb6ee04358d46ec7e on iurifq:persist_queue_stats into ** on edgurgel:master**.

This has been improved in #39

authors: coveralls iurifq

repo: edgurgel/verk


text:
how to execute the munki_enroll.sh script

Can someone please tell me how i can execute the munki enroll script through terminal or Deploy Studio.

Client Configuration
Edit the included munki_enroll.sh script to include the full URL path to the enroll.php file on your Munki repository.
SUBMITURL="https://munki/munki-enroll/enroll.php"
The included munki_enroll.sh script can be executed in any number of ways (Terminal, ARD, DeployStudio workflow, LaunchAgent, etc.). Once the script is executed, the Client Identifier is switched to a unique identifier based on the system's hostname.

Try ./munki_enroll.sh from the Terminal or add a script step in your DeployStudio workflow. The latter is how it was deployed at my employer. You may need to chmod +x if you downloaded the script from the web.

repo: edingc/munki-enroll


text:
Image placement doesn't appear to factor in wrapped lines

This plugin is so cool! I look forward to when I can post issues and browse github while viewing images all without leaving my terminal... The day when developers not doing front-end web can have zero browser windows open is finally approaching!
I noticed that without line wrapping, the image placement is mostly pretty good. When I turn on line wrapping though, image placement is as though line wrapping is still no on.
Would be awesome to have line wrapping awareness, since a lot of images will be embedding in markdown files that look best in my view when they are not hard wrapped, so that any size terminal will work.

I'm having the same issue.
I didn't know line wrapping was the issue, thanks for pointing that out!

authors: HanneMaes erwin


text:
Values ontology removal

This addresses https://github.com/edmcouncil/auto/issues/15.
However, after the removal of non-existent FIBO Value ontology, some of its, non-existent classes, had to be replaced with the appropriate restrictions.

Sounds reasonable, but the problem is, as indicated in https://github.com/edmcouncil/auto/issues/15, that Values ontology does not exist any more, so there is nothing to be moved or kept.
@trypuz do you remember when Values ontology was deleted?

I'm working on a new pull request that will address this problem.

authors: mereolog trypuz

repo: edmcouncil/auto


text:
FIBO Domain for General Ledger, Profit & Loss as well as Capital Market Ratio available?

Dear FIBO Team,
I understand that the FIBO Content Teams (FCTs) are working groups that are formed when the FIBO Community Group decides what existing or new FIBO Domain should be further developed.
Maybe I overlooked this, but I could not see what is all in the Pipeline. I understood that the complete overview of all avalable FIBO ontologies are available here: https://spec.edmcouncil.org/fibo/ontology/
I am basically trying to find out more if within FIBO an ontology for General Ledger, Profit & Loss and / or more general available Capital Market Ratios exist. Is someone able to help me?
I understand that multiple regulator and companies have published different standards for reporting purposes based on available GAAP but what I was looking a general global standard around this which is not linked to any of the XBRL standards or similarly.
Thanks a lot for your help
Best regards
Johannes

Speaking personally, I would see Capital Market Ratios being in the scope of FIBO - we've started exploring areas such as market cap.
However I would argue that generic accountancy concepts such as General Ledger would not be in scope (FIBO is already arguably too large, and as I'm sure you're aware there are both US GAAP and IFRS perspectives to consider). I'm involved in work happening in OMG around the Standard Business Report Model https://www.omgwiki.org/SBRM/doku.php that is intended to bring an ontology treatment to XBRL; that provides the structure and the aggregation and allows Accountancy subject matter experts to contribute the ontology for the core accounting concepts: we do have some of those onboard.

Speaking personally, I would see Capital Market Ratios being in the scope of FIBO - we've started exploring areas such as market cap.
However I would argue that generic accountancy concepts such as General Ledger would not be in scope (FIBO is already arguably too large, and as I'm sure you're aware there are both US GAAP and IFRS perspectives to consider). I'm involved in work happening in OMG around the Standard Business Report Model https://www.omgwiki.org/SBRM/doku.php that is intended to bring an ontology treatment to XBRL; that provides the structure and the aggregation and allows Accountancy subject matter experts to contribute the ontology for the core accounting concepts: we do have some of those onboard.

Thanks a lot rivettp for your feedback. Very much appreciated

@ebnerj  Hi Johannes,
Pete is right for the most part - we have a few very high level accounting concepts.  FIBO includes individuals for IFRS and US GAAP, and classes for 'ledger account' and for GL, but we haven't integrated details at a transaction / record level, or for the many other accounting concepts that would allow for representation and roll-up of a P/L statement or balance sheet, and that's really not in scope for FIBO.  I'm working with a client for which we've represented a general transaction record, and hope to integrate that soon, which might get you partway there.  We also have a number of concepts describing statistical measures that might be useful, which we developed with the assistance of Statistics Canada and the Bureau of Labor Statistics.
If you would like a cook's tour of those aspects of the model that you might be able to reuse, please don't hesitate to ask - we can set up a webex for that over the next couple of weeks.  My email address is ekendall@thematix.com, and Pete's is pete.rivett@adaptive.com - feel free to send us a note if that would be helpful and we can set up a time.
Best regards,
Elisa

@ebnerj Hi Johannes,
Pete is right for the most part - we have a few very high level accounting concepts. FIBO includes individuals for IFRS and US GAAP, and classes for 'ledger account' and for GL, but we haven't integrated details at a transaction / record level, or for the many other accounting concepts that would allow for representation and roll-up of a P/L statement or balance sheet, and that's really not in scope for FIBO. I'm working with a client for which we've represented a general transaction record, and hope to integrate that soon, which might get you partway there. We also have a number of concepts describing statistical measures that might be useful, which we developed with the assistance of Statistics Canada and the Bureau of Labor Statistics.
If you would like a cook's tour of those aspects of the model that you might be able to reuse, please don't hesitate to ask - we can set up a webex for that over the next couple of weeks. My email address is ekendall@thematix.com, and Pete's is pete.rivett@adaptive.com - feel free to send us a note if that would be helpful and we can set up a time.
Best regards,
Elisa

Thanks Elisa - very much appreciated. I will look into the details and connect with you

authors: ElisaKendall ebnerj rivettp

repo: edmcouncil/fibo


text:
Fix typo (Betatable → Betable) in 2017-02.md

Hi Nathan!  Thank you for hosting the meeting last night!
Great meeting and great turnout!
Cheers!

thanks!

authors: anthonyfok nathany


text:
Chore/refactor rollup

@edmundhung I'm not sure why, but rollup will not build within the packages directory, do you have any ideas? (I've just converted 1 package for testing purposes)

Maybe the copy plugin is failed because it couldn't find the readme and license files?

@edmundhung I just tried to update copy plugin locally, but the error has to do with the TS code.
 ./index.ts → ....
│ [!] (plugin babel) SyntaxError: /Users/lifeiscontent/GitHub/edmundhung/conform/packages/conform-dom/index.ts: Unexpect…
│   1 | export {
│ > 2 |  Otype Combine,
│     |  t     ^
│   3 |  ttype Constraint,
│   4 |  Mtype ControlButtonProps,
│   5 | ngtype FormId,
│ index.ts (2:6)
│ SyntaxError: /Users/lifeiscontent/GitHub/edmundhung/conform/packages/conform-dom/index.ts: Unexpected token, expected …
│   1 | export {
│ > 2 |   type Combine,
│     |        ^
│   3 |   type Constraint,
│   4 |   type ControlButtonProps,
│   5 |   type FormId,
│     at toParseError (/Users/lifeiscontent/GitHub/edmundhung/conform/node_modules/.pnpm/@babel+parser@7.23.5/node_modul…
│     at Parser.raise (/Users/lifeiscontent/GitHub/edmundhung/conform/node_modules/.pnpm/@babel+parser@7.23.5/node_modul…
│     at Parser.unexpected (/Users/lifeiscontent/GitHub/edmundhung/conform/node_modules/.pnpm/@babel+parser@7.23.5/node_…
│     at Parser.expect (/Users/lifeiscontent/GitHub/edmundhung/conform/node_modules/.pnpm/@babel+parser@7.23.5/node_modu…
│     at Parser.parseExportSpecifiers (/Users/lifeiscontent/GitHub/edmundhung/conform/node_modules/.pnpm/@babel+parser@7…
│     at Parser.maybeParseExportNamedSpecifiers (/Users/lifeiscontent/GitHub/edmundhung/conform/node_modules/.pnpm/@babe…
│     at Parser.parseExport (/Users/lifeiscontent/GitHub/edmundhung/conform/node_modules/.pnpm/@babel+parser@7.23.5/node…
│     at Parser.parseStatementContent (/Users/lifeiscontent/GitHub/edmundhung/conform/node_modules/.pnpm/@babel+parser@7…
│     at Parser.parseStatementLike (/Users/lifeiscontent/GitHub/edmundhung/conform/node_modules/.pnpm/@babel+parser@7.23…
│     at Parser.parseModuleItem (/Users/lifeiscontent/GitHub/edmundhung/conform/node_modules/.pnpm/@babel+parser@7.23.5/…
│     at Parser.parseBlockOrModuleBlockBody (/Users/lifeiscontent/GitHub/edmundhung/conform/node_modules/.pnpm/@babel+pa…
│     at Parser.parseBlockBody (/Users/lifeiscontent/GitHub/edmundhung/conform/node_modules/.pnpm/@babel+parser@7.23.5/n…
│     at Parser.parseProgram (/Users/lifeiscontent/GitHub/edmundhung/conform/node_modules/.pnpm/@babel+parser@7.23.5/nod…
│     at Parser.parseTopLevel (/Users/lifeiscontent/GitHub/edmundhung/conform/node_modules/.pnpm/@babel+parser@7.23.5/no…
│     at Parser.parse (/Users/lifeiscontent/GitHub/edmundhung/conform/node_modules/.pnpm/@babel+parser@7.23.5/node_modul…
│     at parse (/Users/lifeiscontent/GitHub/edmundhung/conform/node_modules/.pnpm/@babel+parser@7.23.5/node_modules/@bab…
│     at parser (/Users/lifeiscontent/GitHub/edmundhung/conform/node_modules/.pnpm/@babel+core@7.23.5/node_modules/@babe…
│     at parser.next (<anonymous>)
│     at normalizeFile (/Users/lifeiscontent/GitHub/edmundhung/conform/node_modules/.pnpm/@babel+core@7.23.5/node_module…
│     at normalizeFile.next (<anonymous>)
│     at run (/Users/lifeiscontent/GitHub/edmundhung/conform/node_modules/.pnpm/@babel+core@7.23.5/node_modules/@babel/c…
│     at run.next (<anonymous>)
│     at transform (/Users/lifeiscontent/GitHub/edmundhung/conform/node_modules/.pnpm/@babel+core@7.23.5/node_modules/@b…
│     at transform.next (<anonymous>)
│     at step (/Users/lifeiscontent/GitHub/edmundhung/conform/node_modules/.pnpm/gensync@1.0.0-beta.2/node_modules/gensy…
│     at evaluateAsync (/Users/lifeiscontent/GitHub/edmundhung/conform/node_modules/.pnpm/gensync@1.0.0-beta.2/node_modu…
│     at /Users/lifeiscontent/GitHub/edmundhung/conform/node_modules/.pnpm/gensync@1.0.0-beta.2/node_modules/gensync/ind…
│     at new Promise (<anonymous>)
│     at fn (/Users/lifeiscontent/GitHub/edmundhung/conform/node_modules/.pnpm/gensync@1.0.0-beta.2/node_modules/gensync…
│     at stopHiding - secret - don't use this - v1 (/Users/lifeiscontent/GitHub/edmundhung/conform/node_modules/.pnpm/@b…
│     at Object.transformAsync (/Users/lifeiscontent/GitHub/edmundhung/conform/node_modules/.pnpm/@babel+core@7.23.5/nod…
│     at transformCode (/Users/lifeiscontent/GitHub/edmundhung/conform/node_modules/.pnpm/@rollup+plugin-babel@5.3.1_@ba…
│     at transform (/Users/lifeiscontent/GitHub/edmundhung/conform/node_modules/.pnpm/rollup@2.79.1/node_modules/rollup/…
│     at ModuleLoader.addModuleSource (/Users/lifeiscontent/GitHub/edmundhung/conform/node_modules/.pnpm/rollup@2.79.1/n…
└

figured it out, I'd forgotten to copy the babel config to the CJS config.
@edmundhung if this looks good to you, I'll go ahead and migrate all the other packages.

@edmundhung updated :)

authors: edmundhung lifeiscontent

repo: edmundhung/conform


text:
Dispersive thin films do not work

It appears currently wavelength-dependent refractive indices fail when used as thin films. This is because internally, there is no separation between the permittivity/index used for the purposes of actually calculating modes (which needs to have the shape of the incident harmonics) and the underlying dispersive data. This should be a relatively straightforward fix, and requires separating the two.

Fixed in  1fcf6c9.

repo: edmundsj/rcwa


text:
Website down..

On https://classroom.github.com/desktop I get:

The page you were looking for doesn't exist.
You may have mistyped the address or the page may have moved.
If you are the application owner check the logs for more information.

@yvan-sraka Thanks for opening this, as we're still developing this application there is no landing page yet. We'll put one up once this is ready to go.

authors: johndbritton yvan-sraka

repo: education/classroom-desktop


text:
Release NuGet package

What NuGet package do you want to release?
dotnet-sdk-extensions-testing
What is the new version for the NuGet package?
1.0.18-alpha
Auto-generate release notes?
Yes
Custom release notes?
No response

/retry-nuget-release

/retry-nuget-release

/retry-nuget-release

/retry-nuget-release

authors: LN-BrodiePestell edumserrano

repo: edumserrano/dotnet-sdk-extensions


text:
Form Functionality feature parity with TornadoFx

The Form functionality feature set is behind that available in the TornadoFx (Kotlin) version.
If you provide a list of features that are missing, I will attempt to update the functionality here to be in sync.
Thanks,
Grant

OK, trying this off the top of my head first.
ButtonBar
To support this properly, an AbstractField class was added with the default functionality of the old Field class. Then two subclasses were added: Field and ButtonBarField.
Abstract field also has an abstract inputContainer: Region property. For the standard Field class, this is either an HBox or VBox depending on the orientation property (javafx.geometry.Orientation).  For ButtonBarField this is a ButtonBar. This was done so that the builders would operate on the correct parent type. I haven't thought about if this is necessary for the JavaFX version.
prefWidth calculations fixed
The Form.labelContainerWidth function now gets a height property, I think it didn't use to. I think there was a bug inside Field.computePrefWidth as well, where fieldset.labelPosition == HORIZONTAL should be changed to fieldset.labelPosition == VERTICAL.
Menemonic target (setting labelFor)
This was done as an extension function on node, it will probably be a function on AbstractField in the JavaFX version.
That's all I can remember right now, I think this covers most of it :)

Important notice: The field builder used to operate on the inputContainer inside the Field. This has been changed so that it now operates on the
field itself. If you did something like parent.isVisible = false to hide the field, you must now change your code to isVisible = false. This new
behavior is more as one would expect and hopefully the change won't cause any trouble to anyone.

This doesn't apply to the Java version, since there are no builders.

Okay - thanks

I'll close this issue as your PR took care of all of it!

authors: edvin gtnarg

repo: edvin/tornadofx-controls


text:
🛑 Chatbot is down

In 6eb0998, Chatbot (https://chatbot.agi.zjuici.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Chatbot is back up in a691c52 after 11 hours, 16 minutes.

repo: edwardzjl/chatbot-uptime


text:
Fix Read the Docs builds

Builds were failing on Read the Docs because it doesn't set DJANGO_SETTINGS_MODULE like tox does.  Now doing this directly in docs/conf.py instead.
Also upgraded dependencies again via pip-compile; no major changes.

Current coverage is 100% (diff: 100%)

Merging #5 into master will not change coverage

@@           master    #5   diff @@
===================================
  Files          12    12
  Lines         416   416
  Methods         0     0
  Messages        0     0
  Branches       48    48
===================================
  Hits          416   416
  Misses          0     0
  Partials        0     0

Powered by Codecov. Last update 56bad1e...fb1f8cc

@nedbat @clintonb Up for a quick review of this?

I'm not a fan of sys.path shenanigans, but it is common in sphinx configuration, and we have bigger fish to fry. :+1:

authors: codecov-io jmbowman nedbat

repo: edx/django-user-tasks


text:
编码有点问题

我把第36行改成config = safe_load(open(config_path, "r", encoding="utf-8").read())
可以运行，但还是有点小瑕疵

有中文，编码问题，忘记改了

给config.yaml加了中文解释，回头忘记给代码加编码了

ok，问题已解决，多谢提醒

authors: eeeeeeeeee-code zhifana


text:
Russian Language, please :3

Hello, please add Russian Language to your mod

go ahead

repo: eerussianguy/firmalife


text:
View not rendering when calling route's render method

routes/application.js
Ember.Route.extend({
    actions: {
        openModal: function openModal(modalName, controller) {
            var opts = {
                into: 'application',
                outlet: 'modal'
            }
            if (!!controller) {
                opts.controller = controller
            }
            return this.render(modalName, opts)
        }
        ,closeModal: function closeModal() {
            return this.disconnectOutlet({
                outlet: 'modal',
                parentView: 'application'
            })
        }
    }
})

templates/applicaiton.hbs
{{liquid-outlet 'main'}}
{{liquid-outlet 'modal'}}

This code work fines when I don't use a liquid-outlet for the modal outlet, but not when using the liquid-outlet. Am I doing something wrong here?

Figured out what the issue is... liquid-outlet's height is 0... so the view is being rendered, but not shown. This issue can be closed


text:
Updated the empty project wrapper .mag file.

Updated the empty project wrapper .mag file.  (Take two;  first time I didn't notice that it was trying to merge into the original repository this was forked from, which is a really stupid thing for git or github to do.)

@marwaneltoukhy :  I think I just duplicated your pull request;  should have read further ahead in my emails before doing that.  I'll close this one.


text:
🛑 Nodo UTT Ramos Mejia is down

In 6b426c4, Nodo UTT Ramos Mejia (https://www.uttnodoramosmejia.com.ar) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Nodo UTT Ramos Mejia is back up in aea73bf after 16 minutes.

repo: efecear/upptime


text:
🛑 Tierra Firme is down

In 9d4c625, Tierra Firme (https://www.tierrafirmenodoutt.com.ar) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Tierra Firme is back up in 78a0934.


text:
🛑 Nodo UTT Morón is down

In eee54a6, Nodo UTT Morón (https://www.nodouttmoron.com.ar) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Nodo UTT Morón is back up in 15490f5.


text:
🛑 Almacén BioPandora is down

In 763277a, Almacén BioPandora (https://www.biopandora.com.ar) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Almacén BioPandora is back up in 9448bd5.


text:
🛑 Nodo UTT Morón is down

In 9a2f059, Nodo UTT Morón (https://www.nodouttmoron.com.ar) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Nodo UTT Morón is back up in ace5eb5.


text:
🛑 La Semilla Que Crece is down

In 8b3dc08, La Semilla Que Crece (https://www.lasemillaquecrece.com.ar) was down:

HTTP code: 0
Response time: 0 ms

Resolved: La Semilla Que Crece is back up in 0607838.


text:
🛑 Almacén BioPandora is down

In 8c065b4, Almacén BioPandora (https://www.biopandora.com.ar) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Almacén BioPandora is back up in ae81bad.


text:
What are stopID and stopCode?

submitted by Pim van Toolen

Nice! The first national specs... Stopcode is used in the Centraal Halte Bestand... Please change it into stopID and maybe a country code?

Centraal Halte Bestand defines ScheduledStopPoints (logical domain) and Quays (physical domain). The latter can be grouped by StopPlaces (single transport mode) and a Place.
In GTFS a StopID is dataset unique. Ideally this would match QuayId. In GTFS a StopCode is a big number on the stop which the traveler identifies the stop with. It is not a platform code. In The Netherlands I have not seen stop codes.

Hmmm. The domain model of CHB mentions 'stopplacecode'...

StopPointCode (a specific position to board or alight) or StopPlaceCode (the group of stoppoints). Choose wisely what you want to represent or query.

authors: edwinvandenbelt efel85 skinkie


text:
非同期読み込み時のエフェクト読み込み

Effekseer for DXライブラリにて、SetUseASyncLoadFlag(TRUE)で非同期読み込みを行っているときに、
LoadEffekseerEffect()でエフェクトを読み込むと-1が返されます。
また、SetDrawBlendMode()などを使用して、再生中のエフェクトを半透明で表示させることはできないのでしょうか。
なにか解決法がよろしくおねがいします。
<環境>
i5 6500
ram 8gb
gtx1060
VS 2017
DXライブラリ Ver 3.19a
Effekseer 1.31

了解しました。
ご回答ありがというございます。

1.4 beta3相当のEffekseerForDXライブラリを生成しました。
https://github.com/effekseer/Effekseer/releases/download/NightlyBuild/EffekseerForDXLib_140_319dBeta3.zip
色を変更する関数が増えています。
ただ、非同期に関してはDXライブラリ側で現在非同期読み込みかどうかを取得する機能がないので対応できておりません。後日、DXライブラリの開発者に問い合わせてみます。

repo: effekseer/Effekseer


text:
Seg Fault when running inference_gui2.py

user@ubuntu:~/github/so-vits-svc$ python3 inference_gui2.py
DEBUG:matplotlib:matplotlib data path: /home/user/.local/lib/python3.8/site-packages/matplotlib/mpl-data
DEBUG:matplotlib:CONFIGDIR=/home/user/config/matplotlib
DEBUG:matplotlib:interactive is False
DEBUG:matplotlib:platform is linux
DEBUG:matplotlib:CACHEDIR=/home/user/.cache/matplotlib
DEBUG:matplotlib.font_manager:Using fontManager instance from /home/user/.cache/matplotlib/fontlist-v330.json
pygame 2.3.0 (SDL 2.24.2, Python 3.8.10)
Hello from the pygame community. https://www.pygame.org/contribute.html
Automatic mode enabled. Press ctrl+shift+r to toggle recording.
Note: Rubberband is not available. Timestretch not available.
Segmentation fault (core dumped)

user@ubuntu:~/github/so-vits-svc$ python3 --version
Python 3.8.10

user@ubuntu:~/github/so-vits-svc$ uname -a
Linux ubuntu 5.15.0-67-generic #74~20.04.1-Ubuntu SMP Wed Feb 22 14:52:34 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Try running python3 -X faulthandler inference_gui2.py and post the output please

Well, I tried it and it's all working today! :shrug:
Mysterious, I'll close the issue.

authors: effusiveperiscope lawrencehook

repo: effusiveperiscope/so-vits-svc


text:
lib: Update the whole project to node 8,10

'uws', due to some personal issues (See: https://github.com/socketio/socket.io/issues/3319), the author
has destroyed it since 10.148.1. And after several times of trying. Only 10.148.0 can work very very properly in both Nodejs 8.x and 10.x. So use this instead.

Remove "please find another reliable library instead" in the corresponding docs because we HAVE TO use 'uws', which is in the engine.io library, it will check whether you are referring this lib or not. If not, an error will be thrown out to you. See: https://github.com/socketio/engine.io/blob/6a16ea119280a02029618544d44eb515f7f2d076/lib/server.js#L107.

Upgrade the whole project to the latest version (Node 8, 10).

CI is time out, run again

What's wrong with CI？I will see the random that sometimes Nodejs 8 won't work, sometimes Nodejs 10 won't work：

/cc：@ngot,@atian25

/cc：@ngot,@atian25

Thanks


text:
ファイルが無い状態になるものがある

ダウンロードをしようとするとdoneと出るもののフォルダーだけ作られて中にファイルが無い状態になる
https://comic-days.com/magazine/3269754496500226218.json

$ jget -u "xxxxxxxxxxx@xxxxxxxx" -p "xxxxxxxxxxxxxxxx" "https://comic-days.com/magazine/3269754496500226218.json"
get: https://comic-days.com/magazine/3269754496500226218.json
saved: .\週刊少年マガジン\週刊少年マガジン２０２２年２９号
done.

ダウンロード自体はできファイルもあるが、作られたフォルダーの中に入らず親フォルダー内にファイル名が文字化けした状態で出力される
https://shonenjumpplus.com/episode/13933686331692600972.json

$ jget https://shonenjumpplus.com/episode/13933686331692600972.json
get: https://shonenjumpplus.com/episode/13933686331692600972.json
saved: .\久保さんは僕を許さない\[episode.001]久保さんは僕を許さない
done.

荵・ｿ昴＆繧薙・蜒輔ｒ險ｱ縺輔↑縺Ы[episode.001]荵・ｿ昴＆繧薙・蜒輔ｒ險ｱ縺輔↑縺Ы00.jpg
荵・ｿ昴＆繧薙・蜒輔ｒ險ｱ縺輔↑縺Ы[episode.001]荵・ｿ昴＆繧薙・蜒輔ｒ險ｱ縺輔↑縺Ы01.jpg...

ValueError: Unfamiliar width https://shonenjumpplus.com/magazine/3270296674401895776.json

$ jget -u "xxxxxxxxxxx@xxxxxxxx" -p "xxxxxxxxxxxxxxxx" "https://shonenjumpplus.com/magazine/3270296674401895776.json"
get: https://shonenjumpplus.com/magazine/3270296674401895776.json
Traceback (most recent call last):
  File "c:\programdata\anaconda3\lib\runpy.py", line 194, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "c:\programdata\anaconda3\lib\runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "C:\ProgramData\Anaconda3\Scripts\jget.exe\__main__.py", line 7, in <module>
  File "c:\programdata\anaconda3\lib\site-packages\getjump\main.py", line 175, in main
    get_one(args)
  File "c:\programdata\anaconda3\lib\site-packages\getjump\main.py", line 154, in get_one
    _, prev_title, ok = g.get(
  File "c:\programdata\anaconda3\lib\site-packages\getjump\getjump.py", line 98, in get
    self.__save_images(pages, save_dir, only_first)
  File "c:\programdata\anaconda3\lib\site-packages\getjump\getjump.py", line 167, in __save_images
    img = self.__get_image(page)
  File "c:\programdata\anaconda3\lib\site-packages\getjump\getjump.py", line 187, in __get_image
    dice_width = int((width - self.__get_width_gap(width)) / offset)
  File "c:\programdata\anaconda3\lib\site-packages\getjump\getjump.py", line 227, in __get_width_gap
    raise ValueError(
ValueError: Unfamiliar width (please let me know with issue <https://git.io/J2jV3>): 959

度々すみません ご対応いただけると嬉しいです

1と2に関してはWindowsに問題があるようです。Linux環境では正常にダウンロードと閲覧ができました。
3は定期購読が必要なので今の所検証していません。

3ですが、
git clone https://github.com/eggplants/getjump && cd getjump
pip instal -e .

した後、getjump/gap.pyのWIDTH_GAPに959: 0,などを追記して
getjump -o -f -u "***" -p "***" "https://shonenjumpplus.com/magazine/3270296674401895776.json"

で1ページだけダウンロードし、画像がずれているようなら959: 2,などと数字を増やしていい感じの値を探索すると解決できます。

1と2についてはこれっぽい
https://qiita.com/SKYS/items/cbde3775e2143cad7455

authors: eggplants minahoku

repo: eggplants/getjump


text:
CH EMED Dosage Structured Profile (MedicationStatement / MedicationDispense) -  define EventTiming for 1-1-1-1 dosing (Oliver Egger, ahdis)

ch.fhir.ig.ch-emed#0.2.0 /StructureDefinition-ch-emed-dosage-structured.html
TiminEvent: Our "Swiss" dose time regime, like 1 - 1 - 1 -1 as TimingEvent, How should it be coded? There is also the open issue mentioned here (https://art-decor.org/art-decor/decor-issues--ch-pharm-?id=2.16.756.5.30.1.127.77.4.6.20&language=en-US)
CDA-CH-EMED / CH EMED examples:
ACM - ACD- ACV - HS
Cistec:
CM", "CD", "CV", "HS"
Oliver Egger, ahdis

Zur Auswahl stehen folgende TimingEvents: https://terminology.hl7.org/1.0.0/CodeSystem-v3-TimingEvent.html
Der deutsche Medikationsplan verwendet: https://simplifier.net/medikationsplanplus/einnahmezeitpunkte-1
Aus klinischer Sicht wäre je nach Medikament die Möglichkeit, strukturiert "vor dem Essen", "zum Essen" oder "nach dem Essen" zu erfassen, durchaus sinnvoll. Somit wären alle diese Schemen wünschenswert:.
ACM - ACD- ACV - HS
CM -   CD-   CV - HS
PCM - PCD- PCV - HS
Bei einem Grossteil der Medikamente spielt es aber kaum eine Rolle, dort würden wir als Defaultwert ohne A (ante) und P (post) codieren, wie in Deutschland.
Daniel Ratschiller, Cistec AG

es stehen noch mehr als die genannten Events zur Auswahl, nämlich: https://www.hl7.org/fhir/valueset-event-timing.html (besteht aus fast dem vollständigen v3-Timing-Event-Value-Set plus noch zusätzliche Codes wie "MORN", "NOON" etc)
mit Cara (Haupt-CDA-Nutzerin) wurde diskutiert, das v3-Value-Set mit diesem breiteren Value-Set zu ersetzen (vgl. Link Art-Decor oben). Das Event-Timing-Value-Set von FHIR ist "required"

TimingEvents sind alle erlaubt, im IG machen wir aber eine explizite Empfehlung jetzt:
http://build.fhir.org/ig/ehealthsuisse/ch-emed/dosage.html
For the representation of the time of administration according to the 1-1-1-1 scheme, the values MORN-NOON-EVE-NIGHT from the ValueSet EventTiming are highly recommended for the Swiss use.

Umsetzung wie am 25.5.21 besprochen, herzlichen Dank! Ticket geschlossen

authors: drats-cis eHealth-Suisse ig-feedback oliveregger

repo: ehealthsuisse/ch-emed


text:
手环无法选取应用

使用小米手环时没法选择应用，通知只能选择QQ，没有QQ通知增强程序选择

root的话选QQ就好，暂时不打算做界面

authors: ChaosHeadNo ekibun

repo: ekibun/QQNotifyPlus


text:
container not starting, TypeError: Cannot call method 'split' of undefined

Hi, I cloned the docker-index repo, built the image successfully, but when attempting to run the container, I got the following errors multiple times.
Error: Cannot parse config file: '/opt/app/config/docker.js': TypeError: Cannot call method 'split' of undefined
    at Config._parseFile (/opt/app/node_modules/config/lib/config.js:949:11)
    at /opt/app/node_modules/config/lib/config.js:718:25
    at Array.forEach (native)
    at /opt/app/node_modules/config/lib/config.js:714:14
    at Array.forEach (native)
    at Config._loadFileConfigs (/opt/app/node_modules/config/lib/config.js:713:13)
    at new Config (/opt/app/node_modules/config/lib/config.js:118:5)
    at Object.<anonymous> (/opt/app/node_modules/config/lib/config.js:1402:64)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)

/opt/app/node_modules/config/lib/config.js:949
    throw new Error("Cannot parse config file: '" + fullFilename + "': " + e3)

I am not familiar with Node.js. Can you help me to find the problem?

How are you trying to start the container?

At a minimum you need to set the following environment variables using the docker run command
REGISTRIES=registry.private.io

thanks. I had forgotten to check the docker.js file....
I finally got stuff working using a modified version of the fig.yml file you provided to use my own containers.
thanks a lot!

Fantastic. Glad its working. I welcome any feedback you might have about it.

authors: ekristen mimizone

repo: ekristen/docker-index


text:
Unexpected behavior writing booleans as 'true'

Following the issue #273, I have done a unit test that reproduces the behavior and you can prove it yourself.
This test generates a list of CustomObjects where they have a bool property called "Enabled" and are always set to "true", after writing this list of CustomObjects to file in parquet, reads the parquet data and verify that all columns are true.
Regards!
using Microsoft.VisualStudio.TestTools.UnitTesting;
using System.Collections.Generic;
using System.Linq;

namespace UnitTest
{
    public class CustomObject
    {
        [Newtonsoft.Json.JsonProperty("id")]
        public int Id { get; set; }
        [Newtonsoft.Json.JsonProperty("enabled")]
        public bool Enabled { get; set; }

        public CustomObject(int id, bool enabled)
        {
            this.Id = id;
            this.Enabled = enabled;
        }
    }

    public class CustomDataSet : Parquet.Data.DataSet
    {
        public CustomDataSet() : base(new Parquet.Data.SchemaElement<int>("id"), new Parquet.Data.SchemaElement<bool>("enabled"))
        {
        }

        public void Add(CustomObject co)
        {
            this.Add(co.Id, co.Enabled);
        }
    }

    [TestClass]
    public class TestClass
    {
        [TestMethod]
        public void TestMethod()
        {
            const int _numberOfItemsToGenerate = 100;
            const string _parquetFile = @"C:\data\output.parquet";

            IEnumerable<CustomObject> itemsGenerated = this.GenerateData(_numberOfItemsToGenerate);

            this.WriteFileParquet(itemsGenerated, _parquetFile);

            Parquet.Data.DataSet dataset = this.ReadParquet(_parquetFile);

            IList<int> idOfItemsAreNotTrue = new List<int>();

            for (int n = 0; n < dataset.Count; n++)
            {
                Parquet.Data.Row row = dataset.ElementAt(n);

                if (row.GetBoolean(1) != itemsGenerated.ElementAt(n).Enabled)
                {
                    idOfItemsAreNotTrue.Add(row.GetInt(0));
                }
            }

            Assert.IsTrue(idOfItemsAreNotTrue.Count == 0);
        }

        private IEnumerable<CustomObject> GenerateData(int n)
        {
            IList<CustomObject> elements = new List<CustomObject>();

            for (int i = 0; i < n; i++)
            {
                elements.Add(new CustomObject(i, true));
            }

            return elements.AsEnumerable();
        }

        private void WriteFileParquet(IEnumerable<CustomObject> list, string path)
        {
            CustomDataSet customDataSet = new CustomDataSet();
            list.ToList().ForEach(x => customDataSet.Add(x));

            using (System.IO.Stream fileStream = System.IO.File.OpenWrite(path))
            {
                using (var writer = new Parquet.ParquetWriter(fileStream))
                {
                    writer.Write(customDataSet);
                }
            }
        }

        private Parquet.Data.DataSet ReadParquet(string path)
        {
            Parquet.Data.DataSet dataset;

            using (System.IO.Stream fs = System.IO.File.OpenRead(path))
            {
                dataset = Parquet.ParquetReader.Read(fs);
            }

            return dataset;
        }
    }
}

Brilliant thank you, enough details to get on) this will go into 2.0 release, should be in preview shortly

Hi @macalbert I couldn't reproduce this in 2.0, I've shortened the test to:
[Theory]
      [InlineData(100)]
      [InlineData(1000)]
      public void Write_loads_of_booleans_all_true(int count)
      {
         var ds = new DataSet(
            new DataField<int>("id"),
            new DataField<bool>("enabled"));

         //generate data
         for(int i = 0; i < count; i++)
         {
            ds.Add(i, true);
         }

         DataSet ds1 = DataSetGenerator.WriteRead(ds);

         for(int i = 0; i < count; i++)
         {
            Assert.True(ds[i].GetBoolean(1));
         }

      }

Can't see any difference?

Hi @aloneguid great shortening of the test, but you must check ds1 object instead of ds. And if you check ds1 the test continues failing

Assert.True(ds[i].GetBoolean(1));

Assert.True(ds1[i].GetBoolean(1));

My bad, schoolboy error)

released hotfix as v2.0.1, hopefully this is fixed, passes all tests on my side ;)

It's seems to be ok. Nice job @aloneguid!! ;)

authors: aloneguid macalbert

repo: elastacloud/parquet-dotnet