s_axilite ports should not be used for array arguments

According to Vivado HLS documentation, s_axilite interfaces should be generated for non-array arguments.
The wording in the INTERFACE pragma also implies that it generates a register map. (See under offset)
Weirdly, under Creating SDAccel kernels, array arguments are mapped with both m_axi and s_axilite interfaces.

@ViviYe pointed out this example from the SDAccel repo which claims that arrays in fact require both m_axi and s_axilite.

That's quite contradictory! It clearly says:

The AXI4 interfaces supported by Vivado HLS include the AXI4-Stream (axis), AXI4-Lite (s_axilite), and AXI4 master (m_axi) interfaces, which you can specify as follows:
[...]
AXI4-Lite interface: Specify on any type of argument except arrays.

This job provides some insight in SDAccel's implicit checks for interfaces:
ERROR: [XOCC 213-400] The Vivado HLS generated IP does not comply with SDAccel integration requirements. Check interface pragmas to ensure the design only uses one s_axilite interface including the 'return' port and one or more m_axi interfaces with offset=slave set to the s_axilite interface; there should not be any other port interface used.


How to use VSCodeCall in vim?

I can't figure out how to save file with my custom keybindings.
Check this out if something is needed.
These are my config files  for neovim.
keybinding
~modified vscode-neovim~

Is there a reason you are defining VSCodeCall, VSCodeCallRange, etc yourself? They should already be there when you open VCode with this plugin.

I could find any documentation for calling VSCode functions from vim, which I could understand. So I started to do my stuff.
Can you explain what is happening?
I made it work now, but I don't have any idea why it works.
I updated my configs, check them out.

You are right that VSCodeCall is already loaded - when this extension loads and runs your init.vim, it first defines VSCodeCall, VSCodeNotify, and other functions/maps; You can look at the files in the vim directory of this repo to see what exactly is defined.
It also defines g:vscode before loading your script - which means that when you put your code in an if exists('g:vscode') block, your code will only run if it's running from vscode.
As for documentations for this:
You have this section in the README: https://github.com/asvetliakov/vscode-neovim#invoking-vscode-actions-from-neovim
In particular, look at this example:
nnoremap <silent> <C-w>gd <Cmd>call VSCodeNotify('editor.action.revealDefinitionAside')<CR>

So in your case it would be:
if exists('g:vscode')
  nnoremap <silent><Leader>l <Cmd>call VSCodeCall("workbench.action.files.save")<CR>
endif

Thanks for the thorough explanation. It makes sense now.
I had implemented a crude version of your given mapping.
This solves my problem.


Add geospatial projects

We should add the two geospatial projects to the readme

Leaving this to the main project website


[WIP][Discussion]: Ensuring data persistence in S3 and Elasticsearch

Context/Background:
The data that a user supplies when editing an ATBD is persisted in 3 different places:

a PostgreSQL database, hosted in AWS RDS
a PDF document, hosted in AWS S3
an elasticsearch instance, hosted in AWS OpenSearch

While an ATBD is still in the editing/review stages, its data is stored only the database. PDFs can be generated for the ATBD, but, since they are still considered "drafts" they are not persisted anywhere. Once the ATBD is published, the journal and regular PDFs get generated and persisted to S3, and the document is indexed in Elasticsearch.
Once an ATBD is published, users have the ability 1) increment the minor version and 2) create a new major version, from the current major version. When a user increments the minor version, whatever changes have been made to the ATBD version overwrite that ATBD version in the database. This means that the database stores only the most recent minor version. This decision was made on the basis that 1) maintaining records for each major and minor version would lead to a very complex database design (essentially entailing a branching workflow model) and 2) minor version updates are supposed to occur only for small, non-essential changes (typos, formatting edits, etc), which aren't crucial to maintain within the document's history.
However, the Impact team requested that the PDFs for each minor be accessible (this seemed to be as a "just in case" measure, since the APT cannot enforce proper usage of the major/minor versioning system,  users might make a big enough change when incrementing the minor versions that would still want to access previous minor version PDFs).
The solution was to generate both the journal and regular PDFs whenever a user publishes a major version, or increments a minor version. This is why it the response from the backend sometimes takes a long time when publishing an ATBD or incrementing the minor version: under the hood, the API is generating both PDFs and indexing the ATBD in Elasticsearch. Indexing each minor version in the Elasticsearch wasn't a requirement set by Impact, but it seemed logical to us (if you can download a specific minor version of an ATBD you should probably also be able to search for it).
As an example, here are all the copies of a hypothetical ATBD, that is currently on it's 3rd major version:
Elasticsearch (searchable):
- v1.0
- v1.1
- v1.2
- v2.0
- v2.1

S3 (PDFs):
- v1.0
- v1.1
- v1.2
- v2.0
- v2.1

Postgres (RDS):
- v1.2
- v2.1
- v3.0 # <-- not yet published

Storing PDFs and indexing new minor versions in Elasticsearch was implemented using FastAPI's background tasks, however, since the API is implemented in a Lambda function, the Lambda function has no notion of threads and background tasks, so it simply runs the background tasks within the same execution context as the request, before returning the API result to the user. This is one of the disadvantages of using FastAPI in Lambda.
The problem:
We recently encountered an issue in staging where the Elasticsearch instance crashed and somehow restarted. I'm not able to figure out either why the instance crashed in the first place, or which of my actions in the AWS console got the instance back to a reachable state (since the AWS console still shows the instance status as "in progress"), however I suspect the issue may be similar to what these people have experienced.
In our case, all of the previously indexed ATBDs were lost (and are therefore no longer searchable). What's more is that there is no way to re-index previous minor versions in Elasticsearch, since they were overwritten in the database. In the example above, we would only be able to recover the documents indexed in Elasticsearch to this state:
Elasticsearch:
- v1.2
- v2.1

(missing v1.0, v1.1, v2.0)
Similarly, if, for some reason the indexing process fails when creating a new minor version, the data in database will be updated, but nothing will retry the failed indexing operation.
Similarly for the PDF generation: if the PDF generation fails when a user publishes a document or increments the minor version, there will be no way for the user to regenerate those PDFs, and they will be missing from S3 (which might also cause problems in the frontend since, the "Download PDFs" button expects past minor versions to be available to download).
Problem:
The problem can be summarized as: since we do not store each minor version individually, missing PDFs and indexed documents cannot be recovered if they are lost, or fail to generate in the first place.
Solutions:
At first glance there are 2 solutions:
1. Abandon the requirement for minor version PDFs and searchable documents (low lift - requirements based)
This is the easiest solution since it allows us to index whatever documents are in the database, and, if ever we loose all the data in the Elasticsearch instance, we can simply re-index everything that's in the database.
This kind of bluk operation is obviously not ideal if we have tens of thousands of records in the database, but we don't anticipate that kind of usage, and we don't anticipate the ES instance crashing often (just often enough to be a problem).
Similarly, we abandon the requirement to persist any documents in S3, and we simply regenerate the most recent minor version from whatever is stored in the database every time a user clicks "Download PDF".
I would argue that this is an acceptable solution on the basis that minor versions are only supposed to be used for minor edits, so indexing and persisting PDFs for each minor versions is not really storing any meaningfully different or new data (as long as users are using the versioning system as intended).
Lift: 0.5 FT sprint
2. Re-inforce the indexing/PDF persisting (high lift - technical solution)
If we want to maintain the requirement that past minor versions are searchable and accessible as PDFs, there are a couple different approaches we can take:
2.1. Make PDF generation and ES indexing a blocking workflow:
The problem lies in the fact that user can increment the minor version, and if the minor version update goes through successfully but the PDF generation or ES indexing fails, even if the user knows about it, the operation cannot be retried. A solution to this is to make the PDF generation and ES indexing a blocking part of the workflow. This means that when the user goes to publish the document or increment the minor version, if the PDF generation or ES indexing fails, then the whole operation fails, and the minor version number will not be indexing in the database. This would ensure that documents are indexed in ES and PDFs are generated for each minor version increment, at the expense of a possibly poorer user experience, since they might now be blocked from publishing their document because of a PDF generation error outside of their control. (This would also catch (and block) the case where users attempt to publish a malformatted document, that would result in broken PDF generation or ES indexing.
This solution alone does not protect us from the Elasticsearch instance crashing and loosing all data, so we would also have to persist indexable documents to S3 before indexing them in Elasticsearch, so that we can re-index from S3 if needed.
Lift: 1 FT sprint
2.2. SQS Queue based workflow
When users update a minor version or publish a new version we send the updated document to an SQS queue, where it is processed by a separate lambda function. This constitutes "proper" background processing.
SQS Queues comes with auto-retry behaviour and exponential backoff, in case the ES indexing or PDF generation operation fails, and a dead-letter queue for any message that fails to process 5 times. We can hook up the dead-letter queue to some sort of notification system in order to handle the exception manually (* Note: I don't really have an idea of what handling a failure case like this one "manually" would entail).
Since the SQS Queue alone wouldn't protect us against issues with the Elasticsearch instance crashing and loosing all data, we would also likely want to persist the ES indexable documents to S3 before indexing them so that we can re-index from S3 if needed (if the ES instance crashes).
Note: AWS Opensearch service supports both Elasticsearch and Opensearch, which is AWS's open-sourced version of Elasticsearch, since the group behind Elasticsearch modified the license and won't be providing update to Elasticsearch anymore. The APT backend still uses Elasticsarch. While migrating from Elasticsearch to Opensearch should be relatively easy, since AWS maintains backwards compatibility with Elasticsearch, and it would likely  help reduce the chances of data loss due to crashes in the futures (since it will be actively maintained by AWS going forward), it isn't guaranteed to resolve the issue of losing indexed documents due to the service crashing, and it doesn't resolve the issue of missing documents due to failed indexing / failed PDF generation
Lift: 2 FT sprint

[UPDATE: Decision made]
Handle using options 2.1 above: make elasticsearch indexing and PDF generation a blocking workflow.

@sunu @thenav56 is there any value to keeping this ticket open, or can I close it?


fix: Chart crashing if timeseries_limit_metric is an empty array

SUMMARY
In some existing charts, timeseries_limit_metric could be an empty array instead of expected string or metric object. That caused a bug where an empty array was pushed to metrics array in buildQuery, causing error like on the screenshot.
Shoutout to @villebro for reproducing the problem and suggesting a solution!
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

🏷 preset:2023.11


Kernel crash while keying a dot after pandas Series

Applies To

[X] Notebooks (.ipynb files)
[ ] Interactive Window and/or Cell Scripts (.py files with #%% markers)

What happened?
Kernel crash while keying a dot after pandas Series.

ipykernel 6.29.5
jupyter_client 8.6.0
jupyter_core 5.7.2
VS Code Version
1.92.1
Jupyter Extension Version
v2024.8.2024080201 (pre-release)
Jupyter logs
23:54:42.649 [error] Disposing session as kernel process died ExitCode:<PHONE_NUMBER>, Reason:

Coding Language and Runtime Version
Python 3.10.14 | packaged by Anaconda, Inc.
Language Extension Version (if applicable)
v2024.12.2
Anaconda Version (if applicable)
conda 24.5.0
Running Jupyter locally or remotely?
Local

Maybe it 's same as #15577

Thank you for filing this issue and sorry you are running into this.
Please can you disable the following setting and see if that makes a difference?


Remove WerMetric from init

This PR removes WerMetric from __init__.py of fairseq2.metrics since it transitively causes a dependency on the editdistance package. It also moves wav2vec 2.0 ASR metric bags to their own module for similar reason.


Optimize the implementation of command RANDOMKEY

Search before asking

[X] I had searched in the issues and found no similar issues.

Motivation
Currently the result key of command RANDOMKEY is not randomized enough, so we'd better do some research and optimize it.
Solution
No response
Are you willing to submit a PR?

[ ] I'm willing to submit a PR!

I'll try this.

@Yangsx-1 Assigned.

Can we add a random_scan function?
This function will select the key at random intervals during the scan, after scan we can randomly select keys from the scan result. This may be more random. @PragmaTwice @git-hulk @torwig

Could you give more detailed design of it? I cannot get your point well.
Besides, I think one possible way is to add more random cursors, and select one of them each time.

Could you give more detailed design of it? I cannot get your point well.
Besides, I think one possible way is to add more random cursors, and select one of them each time.

Oh, i mean, we can add a random interval in the iteration of scaning.
For example, the scan result may be 1 2 3 4 5 6 now, after add a random interval, the result may be 1 3 6 9 10 12 rather than pure sequential scanning. And we can select a key from the result of random scan.


Contact list in add new friends screen seems to go off bottom of screen so can't scroll all the way down

my swarm is enormous

fixed


golang filter extension: add recover in defer to catch panic in go code

Then, sendLocalReply with 500 status after recover.
So that, those panic only terminate the current request, not crash the Envoy process.
Note: not all kinds of Go panic could be recovered, i.e. concurrent map writes, launch a nil function as a goroutine could not be recovered, users still need to be very careful about these cases.

/assign @doujiang24


JBPM-4937: Data Modeler loading time very long and increasing with more 'instances'

@manstis Hello Mike, would you mind review this PR?
Thanks.

+1 to merge.

Depends on: https://github.com/droolsjbpm/kie-wb-common/pull/319/

6.4.x: f5f94e9bc29685c55c7e7d47efeeba8474466f04


iptables in Docker 1.9.

I haven't found any information about iptables in Docker 1.9.
Within  man docker there is no information about iptables too.
The last reference about iptables was in Docker 1.8 documentation
http://docs.docker.com/v1.8/articles/networking/#between-containers
But, in Docker 1.9
I can use this option --iptables=false in order to force Docker never make changes to my system iptables rules.
Is it option deprecated?
Or is it incomplete description?
Or is it a bug?

Hi!
Please read this important information about creating issues.
If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
This is an automated, informational response.
Thank you.
For more information about reporting issues, see https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
uname -a:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

No this options is not deprecated. The information is still there, but moved to a different URL; see http://docs.docker.com/engine/userguide/networking/default_network/container-communication/
And the option is still documented in the list of daemon options; http://docs.docker.com/engine/reference/commandline/daemon/
Does the --iptables option not work correctly for you? Or were you just unsure if it was deprecated?

Oh, thank you!
I used to the information is located in "Network configuration".
Unfortunately, google couldn't find your links by query "docker iptables".

Does the --iptables option not work correctly for you? Or were you just unsure if it was deprecated?

I was just unsure.
And i see that information about iptables is in man docker-daemon.
I don’t have any questions.
Thanks.

thanks! perhaps we should have a look at google not properly indexing that
/cc @moxiegirl


[Add] Badge in README.md

Add CI, codecov, cypress, issues, license, repo size badge

Codecov Report

Merging #15 (9b3968d) into main (2d050c3) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main       #15   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            1         1
  Lines            2         2
=========================================
  Hits             2         2

Continue to review full report at Codecov.

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


fix: use std.experimental allocator

This removes the dependency on stdx.allocator by using the built-in std.experimental.allocator.
Closes #166.

std.experimental.allocator is not a drop in replacement for its older counterpart.
In newer versions, you should be using RCIAllocator/RCISharedAllocator rather than IAllocator/ISharedAllocator directly. So this would be a much more involved PR that breaks things in user code. For that reason, I am inclined to prefer #173 approach rather than this.
Also you have your CI file in there, which will need to be removed prior to a rebase.

this PR fixes the failing build and tests on the master branch. Dub test fails for ldc2 because of the UnrolledList bugs reported in #164, #175, #151, etc, which should be fixed separately.

I have nothing else to do regarding this PR. I am waiting for someone to merge this.

Pulled in #180


Non-deterministic test failure of CanLoginTest test_0002_Can Login and edit

Running the test suite non-deterministically fails during CanLoginTest test_0002_Can Login and edit, while it's using Capybara and PhantomJs.  Initial tests suggests that it's more likely to fail when the rails app and/or a browser are running in the same machine.
Sample output when it fails:
Run options: --seed 18466

# Running:

...........................E......................................................................

Finished in 39.137195s, 2.5040 runs/s, 83.5011 assertions/s.

  1) Error:
CanLoginTest#test_0002_Can Login and edit using custom account:
Capybara::ElementNotFound: Unable to find css "#repo_distributed_enough[src*=\"result_symbol_dash\"]"
    test/features/can_login_test.rb:51:in `block in <class:CanLoginTest>'

98 runs, 3268 assertions, 0 failures, 1 errors, 0 skips
Coverage report generated for MiniTest to /home/dwheeler/cii-best-practices-badge/coverage. 687 / 731 LOC (93.98%) covered.

The problem seems to be in the test framework, not the system under test.

It'd be great if we could find a better solution, but this eliminates the pain.  So I'm going to close out this issue for now... but if someone tracks this down in details and solves it, that'd still be great.


check if contact deletion works, fix if necessary

see mgr.py line 16 (TODO: fix)

appears to be another race condition with get_contacts() but this is easily accomplished via UI so closing


About components use cases

Currently, we see that for a component there is only a single use case as an example in the docs, Is it intentional or do you guys want to add more use cases in the docs in the future and extend components functionality more?

We definitely want to add more examples, and if you're willing we can pay for that.


Updates list of contributors and links to tensorflow.org

... instead of GitHub. Fixes #69 .

Hold on a second. The links aren't working.

OK @jameshensman  working now.

@jameshensman This one is good to go.


TypeError: "_this.$data.$apolloData is undefined"

Code breaks after beta.14, but works on beta.13.
TypeError: "_this.$data.$apolloData is undefined"
1 webpack-internal:///./node_modules/vue-apollo/dist/vue-apollo.esm.js:1854:15

I think this commit is at fault: https://github.com/Akryum/vue-apollo/commit/a043654f8e7ea5f4ae2e0427f581057aef19e51b
My component looks something like this:
@Component({
  apollo: {
     foos: {
       query: QUERY,
     }
   }
})
export default class Sidebar extends Vue {
  @Prop({ default: false })
  public expand!: boolean;
  public foos: IFoo[] = [];

  @Watch('$route') onRouteChange(to, from) {
    this.expand = false;
  }
}

As you can see I have a watch, but it doesn't target apollo code.

Could you share a full minimal reproduction please? 😸


Blog template text updates

I think because the content is being tested here: https://github.com/ampproject/ampstart/blob/6dc33a89c1a74045a30808eb5cc5ae6c0679ee60/templates/test-all.amp.json  ?

The JSON is invalid , someplace you broke the JSON.

Removed —those commas get me every time...


Frontend registration with same email in bound sales channel still present in <IP_ADDRESS>

In relation to Ticket [https://shopware.atlassian.net/browse/NEXT-35555|https://shopware.atlassian.net/browse/NEXT-35555|smart-link]
The issue of customer registration in 2 Saleschannels with active channel bounding and active commercial extension is still present.
Tested with Shopware <IP_ADDRESS> and commercial 6.6.2

[public] Shopware automated response: This issue is linked to the internal issue: NEXT-39054
[created from NEXT-39054, comment 504336]

[public] The issue is already covered by the ticket referred to in the description. The fix was integrated into the Commercial plugin, so any customers with this issue need to update their Commercial Plugin version to 6.7.0.
[created from NEXT-39054, comment 505678]


[BACKLOG-23395] Revises MDI descriptions

@pentaho/r2d2 Shouldn't need to wait for wingman, just descriptions revision


Introduction

Nice. Can be little bit pictorial if possible?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 14618620-83fc-fd68-93a9-03626c76d680
Version Independent ID: ea7fbbaf-fd41-75cb-28fb-a2f36c8d3967
Content: A Tour of C# - C# Guide
Content Source: docs/csharp/tour-of-csharp/index.md
Product: dotnet-csharp
Technology: csharp-get-started
GitHub Login: @BillWagner
Microsoft Alias: wiwagn

Thanks for writing this @chetan21k  I'm planning on updates to this content this month. I'll look into ways to enhance this.


Fix import name

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Merge setup.cfg spec with pyproject.toml one and deprecate setup.py and setup.cfg

Now we have a bunch of files. It's a mess:
1 python packages metadata is in fact generated by setup.py script. This means if you need to parse it you'll have to execute the script.
2 Recently pyproject.toml was introduced, which contains for now only the description of the packages needed to build a package. Why do we need this? It can be put into setup.cfg
So I propose to
0 ship setuptools with python
1 merge setup.cfg into pyproject.toml and publish a PEP
2 setuptools should be workable without setup.py, only with pyproject.toml in a repo
3 pyproject.toml should allow additional fields to support non-standard extensions
4 pyproject.toml is the primary source of metainfo. setup.py should be executed if and only if it pyproject.toml uses some variables from it.
5 Write a warning in red that setup.py is deprecated each time setuptools.setup is used

0 ship setuptools with python

Not going to happen. In fact, we're discussing moving distutils into setuptools (@jaraco, see disttutils-sig).

1 merge setup.cfg into pyproject.toml and publish a PEP

Just noting that setup.cfg is being used by several tools like flake8, pytest, etc.

4 pyproject.toml is the primary source of metainfo. setup.py should be executed if and only if it pyproject.toml uses some variables from it.

Care to elaborate how would pyproject.toml use variables from setup.py?

as things currently are, setup.py is the entrypoint and could use variables from pyproject.toml
i propose starting with a tool.setuptools.opptions section for putting plain setup.py parameters
a tool.setuptools.metadata for the plain metadata sections and tool.setuptools.comands for commands/aliases

I'm going to close this in favor of #1688. We are not going to deprecate setup.py, and Nathaniel is probably right that any deprecation period for setup.cfg would probably be "forever" (though it's certainly possible).


Maybe use something like https://iconify.design as icon source

Maybe it will be easier to uniformly integrate multiple icon sets by using some icon set aggregator? I know that Iconify has a repository with all the icons as json files: https://github.com/iconify/icon-sets/tree/master/json.

This is surely something to consider.
I don't like the fact that a user has to be online to use the iconify API. The other way to do this would be to download the iconify icons. This would work, but we are already downloading every icon package, and I would prefer that only required icon libraries be downloaded to reduce the crate size because a crate can be a maximum of 10MB in size.
This is why I personally prefer the more fine-grain approach.
Do you see any advantages to using iconify?

I got the impression that it's nontrivial amount of work to add a new icon
set to the library in a unified way and most of that work is already done
by projects like Iconify, so I proposed it.
I don't think that online approach will work. For offline, I propose having
each image set in a separate crate. The main crate will conditionally
depend on feature-enabled image sets only. This approach is scalable to any
number of sets. It also means the user won't download image sets that are
feature-disabled.
Another idea to reduce crate size is that image set crate will only contain
a json file and a build script that generates classes from it. The build
script should be a single call to yet another crate so the builder code is
compiled once even when multiple image sets are enabled.
On Thu, 30 Mar 2023, 19:01 Charles Edward Gagnon, @.***>
wrote:

This is surely something to consider.
I don't like the fact that a user has to be online to use the iconify API.
The other way to do this would be to download the iconify icons. This would
work, but we are already downloading every icon package, and I would prefer
that only required icon libraries be downloaded to reduce the crate size
because a crate can be a maximum of 10MB in size.
This is why I personally prefer the more fine-grain approach.
Do you see any advantages to using iconify?
—
Reply to this email directly, view it on GitHub
https://github.com/Carlosted/leptos-icons/issues/8#issuecomment-1490633390,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFQQIXWTW424T6MXLIKCL3W6W35LANCNFSM6AAAAAAWNQJLRY
.
You are receiving this because you authored the thread.Message ID:
@.***>


HADOOP-18240. Upgrade Yetus to 0.14.0

Description of PR
Upgrade Yetus to 0.14.0

JIRA: HADOOP-18240

[x] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 59s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+0 :ok:
shelldocs
0m  1s

Shelldocs was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

_ trunk Compile Tests _

+0 :ok:
mvndep
14m 17s

Maven dependency ordering for branch

+1 :green_heart:
shadedclient
24m 52s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 27s

Maven dependency ordering for patch

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
shellcheck
0m  0s

No new issues.

+1 :green_heart:
shadedclient
21m 53s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
asflicense
0m 42s

The patch does not generate ASF License warnings.

65m 16s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4328/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/4328

Optional Tests
dupname asflicense codespell detsecrets shellcheck shelldocs

uname
Linux 34bb5c7214dd 4.15.0-175-generic #184-Ubuntu SMP Thu Mar 24 17:48:36 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 7dd18d1b8e8da573b73f2e11b25dca8a61549269

Max. process+thread count
597 (vs. ulimit of 5500)

modules
C:  U:

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4328/2/console

versions
git=2.25.1 maven=3.6.3 shellcheck=0.7.0

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

Actually, I just noticed the "Unprocessed flag(s)" error. Any concerns there?

Actually, I just noticed the "Unprocessed flag(s)" error. Any concerns there?

I don't have any concern. The error comes from the first run in Yetus 0.13.0. In this version the flags are not allowed.


Make echidna working

Problem
Echidna ci/cd script looks great but what we want here is to get the script working for even 1 ~ 2 solidity files.
So we want to make the echidna script working for both BondingV2.sol and BondingShareV2.sol
Acceptance Criteria

[ ] Create echidna.yml in github workflow for BondingV2.sol and BondingShareV2.sol
[ ] The echidna script should be able to catch up the possible errors.

I am very interested in that issue. I am wondering from what branch to start ? I can't find the echidna ci/cd script in the development branch so I am guessing it is the fix/echidna branch right ?
The thing is that branch has not been rebased on development so the first thing to do is a huge rebase IMO.

I will appreciate it if you complete this bounty. hmm, I prefer to take echidna script from fix/echidna and apply its changes to new branch forked from development. You don't need to start on fix/echidna branch. I made that branch to not miss the echidna script.

Roger that we only miss a bounty for this issue

Perhaps you guys could provide a time estimate on this?

Echidna ci/cd script looks great but what we want here is to get the script working for even 1 ~ 2 solidity files.
So we want to make the echidna script working for both BondingV2.sol and BondingShareV2.sol

Doesn't it make sense for the bounty to set up Echidna for every smart contract? I would increase the Profit label to 50% if so. Kind of wish we had Profit: <25% lol cause current price seems low for Bonding.

I'm interested in this bounty
How can I get started?

Some caveats:

zgo thinks that some prerequisite work might need to be finished before.

I am very interested in that issue. I am wondering from what branch to start ? I can't find the echidna ci/cd script in the development branch so I am guessing it is the fix/echidna branch right ? The thing is that branch has not been rebased on development so the first thing to do is a huge rebase IMO.

Are you familiar with Echidna?

Assuming both are ok with you, then this may be a good first bounty to attempt.

Some caveats:
* zgo thinks that some prerequisite work might need to be finished before.

I am very interested in that issue. I am wondering from what branch to start ? I can't find the echidna ci/cd script in the development branch so I am guessing it is the fix/echidna branch right ? The thing is that branch has not been rebased on development so the first thing to do is a huge rebase IMO.

* Are you familiar with Echidna?

Assuming both are ok with you, then this may be a good first bounty to attempt.

Also you first need to identify what are the invariants that you want to preserve for BondingV2 and BondingShareV2. If invariants don't make sense echidna testing is useless

@0xcodercrane @zgorizzo69
Perhaps we can modify this task to "create foundry fuzzing tests for all of the ubiquity contracts"? As far as I understand foundry fuzzing tests do the same job as echidna.

Yep! exactly. echidna is originally fuzz tests in which the foundry has that feature embedded. I agree

I recall having this conversation some months ago. The conclusion was that Echidna handles a slightly different problem space. This should be confirmed before scrapping it.

Hi! I have came across your project and would enjoy working on this.
A few words on my relevant background:
I used libfuzzer in the past for "traditional" fuzzing. It was mostly integration and results analysis.
I tried slither for static analysis about 2-3 years ago.
Therefore, I do not have much Echidna experience yet but would like to check how useful it is.
My plan for this:

Install the latest Echidna release locally
Set up Echidna to test in assertions / property mode
Implement a property test for StakingShare.sol
update Github action to use latest Echidna v2.2.0

I will experiment today and tomorrow and give you a first update by Wednesday.
I believe first thing will be to compile the contract with Echidna and @openzeppelin, might require some remappings.
After this task is completed and Echidna founds to be useful I would like to work on Echdina standard properties test
https://github.com/crytic/properties/blob/main/PROPERTIES.md#erc20 (https://github.com/ubiquity/ubiquity-dollar/issues/587)
Resources:

Echidna tutorials https://github.com/crytic/building-secure-contracts/tree/master/program-analysis/echidna
Echidna "Fuzz like a pro" workshop https://www.youtube.com/playlist?list=PLciHOL_J7Iwqdja9UH4ZzE8dP1IxtsBXI

If I will not be able to open a PR by Friday EOD I will step down from this task.

/assign

/wallet 0x7e92476D69Ff1377a8b45176b1829C4A5566653a

<1 week

Hi @pavlovcik I noticed the @ubiquibot time is set for <1 day, would be grateful if you could adjust this to <1 week.

@gitcoindev sorry but this task is not ready yet, we're using foundry which has a built-in fuzzing feature, pls wait while we update the description

@gitcoindev sorry but this task is not ready yet, we're using foundry which has a built-in fuzzing feature, pls wait while we update the description

I thought that they cover different scenarios and so it makes sense to use both?

@gitcoindev sorry but this task is not ready yet, we're using foundry which has a built-in fuzzing feature, pls wait while we update the description

I thought that they cover different scenarios and so it makes sense to use both?

Both echidna and foundry can be used for invariant testing
The hardest part is put those invariants in the right places because this requires an overall project understanding at a decent level
As long as we use foundry as a dev framework we'd better stick to a tool that is already implemented in our environment

seems a duplicate of #587 where there are discussions to decide if echidna will be part of the repo

seems a duplicate of #587 where there are discussions to decide if echidna will be part of the repo

My understanding is that Echidna covers different problems compared to the foundry fuzzer so we should use it.

yeah but let's gather another perspective in a different issue

seems a duplicate of #587 where there are discussions to decide if echidna will be part of the repo

My understanding is that Echidna covers different problems compared to the foundry fuzzer so we should use it.

Foundry supports both fuzzing tests and invariant (i.e. echidna) tests

ChatGPT response:

I did a quick search for more information and here's what I found.
Echidna is a prominent tool for fuzzing Ethereum smart contracts. It's developed in Haskell and focuses on property-based testing. Echidna uses sophisticated grammar-based fuzzing campaigns based on a contract's ABI to test user-defined predicates or Solidity assertions. It's particularly known for its unique approach to 'property-based fuzzing', where it tries to falsify user-defined invariants instead of looking for crashes like a traditional fuzzer. This capability allows it to write custom analyses for more complex contracts. Echidna's focus is on Ethereum Virtual Machine (EVM) bytecode, using tools like cryptic compile for testing contracts【9†source】【10†source】【11†source】.
Foundry, on the other hand, is a newer toolkit that includes fuzzing capabilities along with other features for Ethereum development. Its design emphasizes integration with the overall development workflow, making it easy to use alongside other Foundry tools. Foundry is known for its efficiency and the speed of its operations, which can be a significant advantage in certain development scenarios.
Comparing the two, it's clear that while there may be some overlap in core functionality, each tool has unique features and strengths. Echidna's property-based fuzzing is highly specialized and suited for complex contract testing, while Foundry's integrated approach and speed make it attractive for a more streamlined development process. The choice between these tools would largely depend on the specific needs and preferences of the development team, as well as the complexity of the contracts being tested.
Therefore, Foundry fuzzing doesn't necessarily render Echidna fuzzing redundant. Instead, they can be viewed as complementary tools, each excelling in different aspects of smart contract testing. In some cases, using both might offer the most comprehensive testing coverage for smart contracts.
https://chat.openai.com/c/84accfbb-7198-419d-bfde-246c719770c1

echidna scope highly different from foundry built in fuzzing, since pavlovcik wants it will best to just have it rendering but instead executing this on a newer issue, with new specific inputs for the task, upcoming

Well I want to make it very clear that I have no experience using Echidna and almost none with Foundry. I haven't even heard a lot of people on Twitter talking about Echidna lately. Perhaps its obsolete? I'm not sure.

Yes echidna came first before foundry, it was mainly targeted to fuzzing ERC20 in initials stages, will have to research but it only supports a set of properties to fuzz

Interestingly, I found a yet another player in the game called Medusa which apparently won the comparison:
https://github.com/devdacian/solidity-fuzzing-comparison

the goal is finding the best performance "out of the box" with as little guidance & tweaking as possible.

Source: https://github.com/devdacian/solidity-fuzzing-comparison/blob/main/README.md
I think thats pretty nifty. Although I am more keen to adopt technologies that I see the people I follow start talking about. However if its easy to set up then I see no issue with adding this to the CI.


Github Pages deployment option

We could do something similar to the mkdocs guys and automate the usage of the gh-pages branch.

See also git worktree which could help with keeping both branches checked out.

https://github.com/usmu/usmu-github-pages is a thing now!


access django command-line utilities?

I was able to get Cabot installed and working, and set up several services and checks for my system.  All of this was done using a single user.  Embarrassingly, I then set this user to "inactive", which has served to fully lock me out of the app - I can't log into ANY Django Admin pages...
Redeploying Cabot did not have any effect.
I was wondering if there is a way to access the django user information on the host machine running cabot directly?  I was hoping to simply create a new django superuser, and then log in with that.  I tired python manage.py createsuperuser on both the ubuntu server running cabot as well as the machine I deployed cabot from, but it seems like manage.py was not able to access the same environment that cabot is running in:
 File "/usr/lib64/python2.7/UserDict.py", line 23, in __getitem__     raise KeyError(key) KeyError: 'CELERY_BROKER_URL'
Is there a way to directly add a Django user to a Cabot instance?  Or another possible solution?  I'd prefer not to start over.
Thanks very much for any advice, I'm really liking Cabot so far!

You need to just use the same environment as you are running on production - so something like foreman run ./manage.py createsuperuser -e conf/production.env should work.

Going to close this but please re-open if you think there's a bug anywhere.

Thanks very much!  I ended up doing a fresh install but it's good to realize where I was going wrong with my previous approach.


Firefox port

Hi, I really liked this extension when I used Chrome. I switched to Firefox some time ago and it seem that there is no analogue. Hence the question: is there any hope for Firefox port?

AFAICT this would be a full rewrite, I have no intentions of pursuing this
project. However, feel free to port the code!
On Wed, Feb 25, 2015 at 6:17 AM, Eugeny Loy<EMAIL_ADDRESS>wrote:

Hi, I really liked this extension when I used Chrome. I switched to
Firefox some time ago and it seem that there is no analogue. Hence the
question: is there any hope for Firefox port?
—
Reply to this email directly or view it on GitHub
https://github.com/borismus/Question-Monitor-for-Stack-Exchange/issues/11
.


Use the manage interface application  filter for the provider report

Use the same filter for file exports as the one used for the manage interface. This means that the numbers will match because the filter will use current_course_option_id instead of the course_option_id.

 File export application count not matching manage numbers


samples: xtensa_asm2: Cleanup stray IS_TEST reference

We removed IS_TEST a while ago.  Remove this stray reference
Signed-off-by: Kumar Gala<EMAIL_ADDRESS>

Codecov Report

Merging #7756 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #7756   +/-   ##
=======================================
  Coverage   55.01%   55.01%
=======================================
  Files         483      483
  Lines       53949    53949
  Branches    10494    10494
=======================================
  Hits        29680    29680
  Misses      19983    19983
  Partials     4286     4286

Continue to review full report at Codecov.

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


fix path to jar-with-dependencies in instructions to run locally

Instructions in the README erroneously mention the packaged jar file is at "target/github-profile-summary-1.0-jar-with-dependencies.jar" while it is actually "target/github-profile-summary-jar-with-dependencies.jar"

Thanks!


Work toward better OpenSSF Best Practices badge

Currently, LXD meets all the criteria to obtain the passing badge. When checking the criteria to meet the silver badge, it seems that most of them only need to be filled out as we already apply those best practices. Same goes for the gold badge.
As of today, LXD compliance level with the 3 badges is:
Passing: 100%
Silver: 13%
Gold: 17%

I've updated our responses now though that still doesn't clear us for anything but passing.
There are some no-go items in both silver and gold so we're unlikely to ever qualify.

Thanks @stgraber! Just for the record, here are the new compliance levels:
Passing: 100%
Silver: 80%
Gold: 30%


[Next] Problem with MongoDB when running some imports(?)

It seems that in some cases when using MongoDB (but not SQLite) the importer attempts to make calls to /cockpit/call/collections/save that fail with 500.
Emailed with details.

It appears to be failing when trying to save objects that contain multiple values in a collection link field. Emailed with details


Dexie with Angular 2

I am creating a project with angular 2 and Gulp but wen trying to use Dexie I have the following problem :

GET http://localhost:5000/dexie 404 (Not Found)f
deps.js:47711 Error: XHR error (404 Not Found) loading http://localhost:5000/dexie(…)

Declaration:
import Dexie from 'dexie';
...
export class Context extends Dexie {
constructor() {
super("database")
}

Are you using requirejs? If so, did you miss to locate dexie in the require.config? The location differs from Dexie v1.2. In v1.3, the location should be
require.config({
paths: {
"dexie": "node_modules/dexie/dist/latest/dexie.min"
}
});
or if you want to fetch it over the net:
require.config({
paths: {
"dexie"<EMAIL_ADDRESS>}
});

My bad requirejs config. Should be:
require.config({
    paths: {
        "dexie": "node_modules/dexie/dist/latest/dexie" // Won't work with 'dexie.min'
    }
});

or if you want to fetch it over the net:
require.config({
    paths: {
        "dexie"<EMAIL_ADDRESS>    }
});

I don't use requireJs. I use Gulp

var config = {
    scriptsPath: "./wwwroot/scripts/",
    cssPath: "./wwwroot/css/",
    depsFiles: [
            "./node_modules/systemjs/dist/system.src.js",
            "./node_modules/es6-shim/es6-shim.js",
            "./node_modules/dexie/dist/dexie.min.js",
            "./node_modules/rxjs/bundles/Rx.js",
            "./node_modules/angular2/bundles/angular2.dev.js",
            "./node_modules/angular2/bundles/http.js",
            "./node_modules/angular2/bundles/router.js",
            "./node_modules/angular2/bundles/angular2-polyfills.js"
    ],
    cssFiles: [
            "./node_modules/bootstrap/dist/css/bootstrap.min.css"
    ]
};

// Bundle js files
gulp.task('bundle:js', function () {
    return gulp.src(config.depsFiles)
      .pipe(concat("deps.js"))
      .pipe(gulp.dest(config.scriptsPath))
      .pipe(rename("deps.min.js"))
      .pipe(uglify())
      .pipe(gulp.dest(config.scriptsPath));
});

The other modules are differents with dexie. For example rxjs is include in deps.js:
System.register("rxjs/util/noop", [], true, function(require, exports, module) {
  var global = System.global,
      __define = global.define;
  global.define = undefined;
  function noop() {}
  exports.noop = noop;
  global.define = __define;
  return module.exports;
});

but dexie don't use Sytem.register

Have you tried with the version I just released today (v1.3.2)? Solved issues that affected projects using typescript/requirejs and typescript/browserify. I also added support for systemjs by adding a jspm element to package.json.
Please give :+1:  or :-1:  if it solves the issue or not. If not, I'll try diving into it as well.

To clarify, Dexie should now adapt better to ES6 based build systems by providing both jsnext:main and jspm.main attributes in package.json. There are lots of stacks out there to support, but I'll try my best to fix it.

:-1: Not work

If I change the dexie/dist/dexie.js by
System.register("dexie", [], true, function(require, exports, module) {
  var global = System.global,
      __define = global.define;
  global.define = undefined;
(function (global, factory) {
....

this work fine.

Thanks!
I think you can configure Systemjs to handle other module formats. Dexie currently supports AMD, CommonJS and ES6. dist/dexie.js supports AMD,COmmonJS and plain script includes. dist/dexie.es6.js is in ES6 format.
You'll probably stumble on a couple of other modules as well with the same problem. If I'm not mistaken, you can make your system.js be capable of loading other formats, have a look at https://github.com/ModuleLoader/es6-module-loader. Also, check out http://jspm.io which seems to be promising.
Cheers,
David


Fix Issue: Update Specific Role Without Removing Others

Developer Name: vinit
Issue: #1654
Purpose
By adding new role data with the existing roles in the Firestore document then the previous roles got removed. This change will ensure that the update only affects the specified role without affecting other roles that may already be present.
PR Number(s): 1624
Backend Changes

[x] Yes
[ ] No

Is Under Feature Flag

[ ] Yes
[x] No

Database changes:

[ ] Yes
[x] No

Breaking changes (If your feature is breaking/missing something please mention pending tickets):

[ ] Yes
[x] No

Deployment notes:
NA
Tested in local

[ ] Yes
[x] No

Tests Stats

Are tests not needed for this. Please confirm

Added some tests Please check


FFI export extension - pass state between Eta and Java

I have couple of scenarios where I need to pass state from Eta to Java and back.
If I have in Eta some data/ type: T -
I would like be able to pass instances of T to java and then be able to call eta  from Java with a same T.
foreign export java "[export-string]" [eta-identifier]
  :: T -> [arg-type-2] -> .. -> T

Where T is any eta Type. (not JWT).
For instance if I build Conway's Game Of Life
I would like to have in Eta. This will let me to build interactive Game of life with all logic in Eta.
data GameOfLifeState = ....

nextStep::GameOfLifeState ->GameOfLifeState

foreign export java "life.Life.nextStepo" nextStep
  :: GameOfLifeState  -> GameOfLifeState

From java side this object might be encapsulating Closure (and context?). It does not have to expose any properties.
At the moment my workaround is to model all types in Java and import them to eta, so that Eta works on Java Types. This is however very tedious (and probably affects poerformance).

This can be done using the StablePtr's which are hard references to an Eta value, represented as an int on the Java side.
foreign export java "life.Life.nextStepo" nextStep
  :: StablePtr GameOfLifeState  -> IO (StablePtr GameOfLifeState)

The above would generate:
package life;

public class Life {
    public int nextStep(int gameStatePtr) {
        ....
   }
}

For working with StablePtr's, you can check out the API:
https://hackage.haskell.org/package/base-<IP_ADDRESS>/docs/Foreign-StablePtr.html

Comfirmed. It works and solves my problem.
Suggestion: Maybe would be good to put this xplicitly in documentation of FFI.
Issue may be closed.

I'll leave this open to track that we  need to document it.


npm i guide issue in sql docs #4453

Fixes # (issue) 4453

Place for the issue: https://js.langchain.com/docs/use_cases/sql/quickstart

@jacoblee93 Can you check why the docs build is failing?
I am not able to open vercel!

Thank you!


opencl-clhpp: 2.0.12 -> 2.0.15

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/KhronosGroup/OpenCL-CLHPP/releases.
meta.description for opencl-clhpp is: "OpenCL Host API C++ bindings"
meta.homepage for opencl-clhpp is: "http://github.khronos.org/OpenCL-CLHPP/"
meta.changelog for opencl-clhpp is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 2.0.15 in filename of file in /nix/store/09kywf13gaxgg0zl1j0zag4clzzhhq1m-opencl-clhpp-2.0.15

directory tree listing: https://gist.github.com/17b34ab31c4411d2ef7679156d4887ce

du listing: https://gist.github.com/4430744705f2c4dda39d7f100e06e59e

Rebuild report (if merged into master) (click to expand)

31 total rebuild path(s)

13 package rebuild(s)

13 x86_64-linux rebuild(s)
9 i686-linux rebuild(s)
2 x86_64-darwin rebuild(s)
7 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
arrayfire
bumblebee
clfft
clpeak
ethminer
ethminer-cuda
ethminer-free
forge
mandelbulber
opencl-clhpp
opencl-info
virtualgl
virtualglLib

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/09kywf13gaxgg0zl1j0zag4clzzhhq1m-opencl-clhpp-2.0.15 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A opencl-clhpp https://github.com/r-ryantm/nixpkgs/archive/24ab0321592390eb94559e7e2b59b1953acc80e9.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/09kywf13gaxgg0zl1j0zag4clzzhhq1m-opencl-clhpp-2.0.15
ls -la /nix/store/09kywf13gaxgg0zl1j0zag4clzzhhq1m-opencl-clhpp-2.0.15/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review took longer than 45m and timed out

Maintainer pings

On nixos x86_64:
builder for '/nix/store/9ic61jw2i45cqg2ax17cwl5a0anhbhp1-opencl-info-2014-02-21.drv' failed with exit code 2; last 10 log lines:
        |     CL_API_PREFIX__VERSION_1_2_DEPRECATED
  In file included from opencl-info.cpp:10:
  /nix/store/09kywf13gaxgg0zl1j0zag4clzzhhq1m-opencl-clhpp-2.0.15/include/CL/cl2.hpp:18:151: note: '#pragma message: cl2.hpp has been renamed to opencl.hpp to make it clear that it supports all versions of OpenCL. Please include opencl.hpp directly.'
     18 | #pragma message("cl2.hpp has been renamed to opencl.hpp to make it clear that it supports all versions of OpenCL. Please include opencl.hpp directly.")
        |                                                                                ^
  opencl-info.cpp: In function 'int main()':
  opencl-info.cpp:167:22: warning: catching polymorphic type 'class cl::Error' by value [8;;https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html#index-Wcatch-value=-Wcatch-value=8;;]
    167 |     catch (cl::Error err) {
        |                      ^~~
  make: *** [Makefile:12: opencl-info] Error 1

Result of nixpkgs-review pr 134226 at 24ab0321 run on aarch64-linux 1

1 package marked as broken and skipped:

forge

1 package failed to build:

opencl-info

5 packages built successfully:

arrayfire
mandelbulber
opencl-clhpp
virtualgl
virtualglLib

1 suggestion:

warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/libraries/opencl-clhpp/default.nix:25:3:
   |
25 |   meta = with lib; {
   |   ^

Note that build failures may predate this PR, and could be nondeterministic or hardware dependent.
Please exercise your independent judgement. Does something look off? Please file an issue or reach out on IRC.

Needs https://github.com/NixOS/nixpkgs/pull/134228

Needs #134228

merged

rebased: https://github.com/NixOS/nixpkgs/pull/147981


When no MIME type is found in Picker on Android no files can be selected

It should use */* as MIME type then.

Thanks for reporting this issue! I'm able to reproduce it. I'm going to push a fix quickly 👌

I'm preparing a new version today with the fix.


Long Idle time starting a new VScode

Clipboard info
clipboard.txt
prof-8qXYWlcE.main.cpuprofile.txt

Please fill out the issue template

Thanks for creating this issue! We figured it's missing some basic information or in some other way doesn't follow our issue reporting guidelines. Please take the time to review these and update the issue.
Happy Coding!

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Fix the aarch64 tests.

Closing, since it seems that the virtfs appliance that we use to create the VM images does not work on aarch64. So we would need another method to create the images.


Remove standalone-cluster from e2e tests in external-dns addon

cc @vmware-tanzu/pkg-external-dns-owners team
We are removing the deprecated standalone-cluster plugin in v0.11.0 of TCE. The e2e tests currently rely on standalone-cluster.
We are introduced unamanged-cluster in v0.10.0 which should suffice for your e2e tests.
Reference: https://github.com/vmware-tanzu/community-edition/issues/3005

cc @vmware-tanzu/pkg-external-dns-owners

Hi Friends,
We're looking to remove the reference to ./test/docker/run-tce-docker-standalone-cluster.sh from the external-dns test README.md and replace it with a reference to an updated script and/or Makefile task that uses unmanaged-cluster.
There doesn't appear to be such scripts or Makefile tasks yet. We can certainly add a task/script, but we'd like to check in with you first. Thoughts?

@karuppiah7890 @rajaskakodkar is that script something your team maintains for release testing?
I would assume we would want something similar using unmanaged-clusters, but not sure who is best to own that.

I've created this issue to track work for replacing standalone e2e tests with unamanged ones: https://github.com/vmware-tanzu/community-edition/issues/3045
For now @tylerschultz, can your team use managed clusters with this script?
./test/docker/run-docker-managed-cluster.sh

I think we will just point to the getting started guide to explain how to deploy a cluster. Thus removing the need for maintenance of this Readme when scripts change.


As a User, I want Curve VolumeGauge tests to show how much gas is being used for read/writes.

As a User, I want Curve VolumeGauge tests to show how much gas is being used for read/writes so that we can track the expense of the read/writes and focus on reducing costs.
Acceptance Criteria

Add gas costs display to tests when run so we know the gas cost.

Closed as delivered.

Closed as delivered.


Build Fails in XCode

Hello,
I followed your documentation, however, when I attempted to add the RCTRealtimeMessaging in XCode, my project failed to build. I'm using React Native 0.15.
Thanks

Hi #davidsims9t, can you tell more details about the build error on your project?
Thanks

I can't unfortunately. There's no errors that I'm actually getting, it just fails.

can you please send a screen shot of xcode after the build fails?
Thanks

No dia 12/12/2015, às 00:32, David Sims<EMAIL_ADDRESS>escreveu:
I can't unfortunately. There's no errors that I'm actually getting, it just fails.
—
Reply to this email directly or view it on GitHub https://github.com/realtime-framework/RCTRealtimeMessagingIOS/issues/6#issuecomment-164089079.

Hi @davidsims9t, see if the fix for issue #8 solves your problem. Thanks.
Closing this for now.


Update discosrv image for v0.12 on Docker Hub

Everything is in the title.

We don't run it via docker, so it was contributed by some third party.

Actually I think I built it, but it should probably be discontinued as we don't use it any more.

Or maybe not. https://forum.syncthing.net/t/discovery-docker/6034
(moving discussion there to keep things in one place)

Let's close?

Leaving open for visibility as it came up multiple times on just the release day. :)


Client example requests

I have some requests for examples if possible.

Authentication
Way to select sync or async
Maximum redirect option and possibilty to disable it
Possiblity of aborting request
One example with crypto (BTW, does it support LibreSSL? I see some openssl headers in crypto.hpp
.)
One simple REST call example.

Thanks in advance.

Authentication is implemented on top of HTTPS, and is not in the scope of this project.
See the new examples for async request examples
No redirection supported, at the moment you have to implement this on top of this library
Set timeouts. Requests are also cancelled when you stop the io_service.
The crypto header file is only added for convenience. Asio uses OpenSSL, and that is basically the reason why it is used in the crypto header file.
Most important use cases should be shown in the example files I think.

Please have a look at the Response class, the header and content is separated.

Thanks,
-Do you have idea on how to download mp3 file(1MB-10MB) from URL? I saw that HTTP has limit on response size.
-Do you have any plan to implement FTP?

This is unmaintained implementation from asio author. He wanted also add couple of feature. This is for reference only.
http://think-async.com/Urdl/doc/html/urdl/planned_features.html

There is a limit on response size? Might be a timeout maybe?
No plans to implement FTP, sorry.


Client listing reports error as of f1aa8b3

In testing the disk size reporting issue addressed at https://github.com/munkireport/munkireport-php/issues/277 I updated the server and client installer to the build created in f1aa8b3.  I'm now getting the attached error when accessing the "Client" listing:

The current code also contains a database change. You need to enable migrations in your config file.

That was it.  Closed.


Update Composer dependencies (2024-04-23-00-10)

Visual regression test passed!
View the visual regression test report


allow returning of Response object from return or callback.

allow returning of Response object from return or callback.

still need to merge

https://gist.github.com/RichardHightower/36825eb81fb21c05bc41


Could you provide videos from the beggining until the udemy videos was downloaded? I took 2 days full not yet downloaded one videos..[Feature Request]:

Is your feature request related to a problem?

[X] Yes
[ ] No

If yes, please describe
Could you provide videos from the beggining until the udemy videos was downloaded? I took 2 days full not yet downloaded one videos..[Feature Request]:
Describe the solution you'd like
Could you provide videos from the beggining until the udemy videos was downloaded? I took 2 days full not yet downloaded one videos..[Feature Request]:
Describe alternatives you've considered
Could you provide videos from the beggining until the udemy videos was downloaded? I took 2 days full not yet downloaded one videos..[Feature Request]:
Additional context
Could you provide videos from the beggining until the udemy videos was downloaded? I took 2 days full not yet downloaded one videos..[Feature Request]:

Invalid


Update suite setup script for mutating webhooks to run once per package

Is there a related GitHub Issue?
What is this change about?
Update the suite setup script to match the guidelines followed in other packages for setting up envtest by using beforeSuite and afterSuite functions`
Does this PR introduce a breaking change?
No
Acceptance Steps
make test should succeed and envtest setup should execute once per package.
Tag your pair, your PM, and/or team
@Birdrock

this PR has changes unrelated to the issue its trying to address, closing the PR without merging


SWARM-1052: Wrong path is resolved in the HealthAnnotationProcessor.p…

…rocessArchive()
Motivation
fix the wrong path resolved in the HealthAnnotationProcessor.processArchive()
Modifications
changed to use the safeAppend() for resolving the path declared on method level
Result
Now the path of Health endpoint could be resolved correctly(aligned with JAX-RS)

[ ] Have you followed the guidelines in our Contributing document?
[ ] Have you created a JIRA and used it in the commit message?
[ ] Have you checked to ensure there aren't other open Pull Requests for the same issue?
[ ] Have you built the project locally prior to submission with mvn clean install?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

ok to test

retest this please

retest this please

Hi Ken, are you asking me to retest it?
I tested with the test case in SWARM-1052 and there is NO problem.

No that's a signal for our CI to run the tests again.
On Wed, Feb 8, 2017 at 9:06 AM Harry Chan<EMAIL_ADDRESS>wrote:

Hi Ken, are you asking me to retest it?
I tested with the test case in SWARM-1052
https://issues.jboss.org/browse/SWARM-1052 and there is NO problem.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/wildfly-swarm/wildfly-swarm/pull/326#issuecomment-278337417,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAA-TzPSmakizaqmWzSCEUODyg-Z6RWNks5racvbgaJpZM4L3E7g
.

Sorry @hei1233212000, we had an issue with our CI server yesterday that meant by attempt yesterday to retest failed, so I did it again today

got it, I do not know that lol
Thanks :)


[HELP]I wanna get the suorce code of v.3.6.3. by switch branches or check out tags ,but I have some problem.?

I tried to  switch branches and check out tags to get suorce code of v.3.6.3,when i  run the project, I found that the version is 3.3.0,what should I do?

uncover is closed source now

Can we add a discussion label to this? It'd be great to hear more about the reasoning behind close-sourcing this project.


Return the UUID as a string from the query builder

Hi
I want to get the UUID as a string from the result of a query executed through the query builder.
I use the following code:
$query = $this->createQueryBuilder('a')
    ->select('a.id AS id, at.name AS name')
    ...

The id field is the UUID, declared as follows into the entity file:
    /**
     * @ORM\Id
     * @ORM\Column(type="uuid", unique=true)
     * @ORM\GeneratedValue(strategy="CUSTOM")
     * @ORM\CustomIdGenerator(class="Ramsey\Uuid\Doctrine\UuidGenerator")
     */
    private $id;

The query result returns the UUID as an object of type Uuid. Is there any way to get directly the UUID as a string from the query builder result ?
Thanks!

Yes. The following code works and returns the UUID as a string:
$result = $query->getResult();
dump($result[0]['id']->toString());

But it requires to call toString() on every query result. Is there any way to handle it directly from the DQL query ?

@jean553, unfortunately, I don't know the answer to this, but I'll ask around and see what I can find.

I was trying to move my project from incrementing IDs to uuid, and got stuck here! :D

@ramsey btw why is it that I would need the id to be of type UuidInterface  and not just string
That would make things so much easier, and if I wanted to do any operation with the uuid, I could always convert the string to UuidInterface

The purpose of this library is to provide a Doctrine type that returns a ramsey/uuid object for UUID columns in a database.
If you just want UUID strings returned, there is a native Doctrine type for guid that already provides this. Take a look at that and see if it suits your needs: https://www.doctrine-project.org/projects/doctrine-orm/en/2.6/reference/basic-mapping.html

@ramsey Exact. I misunderstood that point in the first place. Thanks for your explanation.

Sorry for the confusion. Glad I was able to help.

why nobody advised to use
$query = $this->createQueryBuilder('a')
    ->select('a.id AS id, at.name AS name')
    ...
    ->getQuery()->getScalarResult()


UserWarning: No training configuration found in save file

I ran python server.py, and the following happened:

Help!

This is a warning. We programmers are just blind to warnings.


Error compiling 'al/createPackage' failed with error

Describe the bug
I added a new extension folder to a project, copied some AL files from another folder, renamed the files, and compiled the Workspace.
To Reproduce

Compile
Error:
[Error - 5:32:32 PM] Please report this issue to https://github.com/microsoft/al/issues including information on how to reproduce it, if possible. Processing of message 'al/createPackage' failed with error: 'Index (zero based) must be greater than or equal to zero and less than the size of the argument list.' Details: System.FormatException: Index (zero based) must be greater than or equal to zero and less than the size of the argument list. at System.Text.StringBuilder.AppendFormatHelper(IFormatProvider provider, String format, ParamsArray args) at System.String.FormatHelper(IFormatProvider provider, String format, ParamsArray args) at System.String.Format(IFormatProvider provider, String format, Object[] args) at Microsoft.Dynamics.Nav.CodeAnalysis.Diagnostics.DiagnosticFormatter.Format(Diagnostic diagnostic, IFormatProvider formatter) in F:\a\586\s\source\Prod\Microsoft.Dynamics.Nav.CodeAnalysis\Diagnostics\DiagnosticFormatter.cs:line 57 at Microsoft.Dynamics.Nav.CodeAnalysis.CommandLine.CommonCompiler.ReportErrors(IEnumerable1 diagnostics, CompilerTextWriter consoleOutput, ErrorLogger errorLogger) in F:\a\586\s\source\Prod\Microsoft.Dynamics.Nav.CodeAnalysis\CommandLine\CommonCompiler.cs:line 258
at Microsoft.Dynamics.Nav.CodeAnalysis.CommandLine.CommonCompiler.RunCoreImpl(CompilerTextWriter consoleOutput, ErrorLogger errorLogger, Compilation compilation, AnalyzerDriver analyzerDriver, IEnumerable1 analyzerExceptionDiagnostics, IEnumerable1 additionalTextFiles, CancellationToken cancellationToken) in F:\a\586\s\source\Prod\Microsoft.Dynamics.Nav.CodeAnalysis\CommandLine\CommonCompiler.cs:line 524
at Microsoft.Dynamics.Nav.CodeAnalysis.CommandLine.CommonCompiler.RunCore(CompilerTextWriter consoleOutput, ErrorLogger errorLogger, CancellationToken cancellationToken) in F:\a\586\s\source\Prod\Microsoft.Dynamics.Nav.CodeAnalysis\CommandLine\CommonCompiler.cs:line 490
at Microsoft.Dynamics.Nav.CodeAnalysis.CommandLine.CommonCompiler.Run(CompilerTextWriter consoleOutput, CancellationToken cancellationToken) in F:\a\586\s\source\Prod\Microsoft.Dynamics.Nav.CodeAnalysis\CommandLine\CommonCompiler.cs:line 349
at Microsoft.Dynamics.Nav.EditorServices.Protocol.LanguageServer.Extensions.CreatePackageRequestHandler.d__8.MoveNext() in F:\a\586\s\source\Prod\Microsoft.Dynamics.Nav.EditorServices.Protocol\LanguageServer\Extensions\CreatePackageRequestHandler.cs:line 174
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Dynamics.Nav.EditorServices.Protocol.LanguageServer.Extensions.CreatePackageRequestHandler.d__7.MoveNext() in F:\a\586\s\source\Prod\Microsoft.Dynamics.Nav.EditorServices.Protocol\LanguageServer\Extensions\CreatePackageRequestHandler.cs:line 103
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Dynamics.Nav.EditorServices.Protocol.MessageProtocol.RequestHandlerBase`1.d__9.MoveNext() in F:\a\586\s\source\Prod\Microsoft.Dynamics.Nav.EditorServices.Protocol\MessageProtocol\RequestHandlerBase.cs:line 43
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Dynamics.Nav.EditorServices.Protocol.RequestRegistry.d__6.MoveNext() in F:\a\586\s\source\Prod\Microsoft.Dynamics.Nav.EditorServices.Protocol\Endpoints\RequestRegistry.cs:line 64

`
Expected behavior
A clear and concise description of where the error occurred.
Screenshots
None.
5. Versions:

AL Language: 4.0.182565

Business Central: 14

I found the resolution.  There is an action subscribing to a non-existent action.  That said, this should probably be fixed.

@MBK75 if you found the cause of the issue, can you share with us a small snippet of code that reproduces it?

Note: This looks like a duplicate of #5292

@MBK75 I can actually reproduce this issue. Closing as duplicate of #5292. Please follow issue #5292 to know when it gets resolved.


[job status] A job shows running in more than 5 minutes, but no resource assigned.

a nni test job from int bed
Should it be waiting status?

It is by design, this application has been submitted to YARN,  but AM's resource requirements hasn't been meet.

From AM log, it seems due to there is no free GPU


Notification on adding users to projects and chairs

When a representative / assistant adds a user to a chair or a project, the added user should receive a notification (even email?) about this.
The event should also be logged to the activity stream.

Duplicate: https://github.com/hpi-swt2/wimi-portal/issues/546


Add a notification settings section on user profile page

What options this page should have?

for now notification for direct message and mention


"Bytes must be in range" while re-adding

For some reason my WF-RAC integration stopped polling information last night. Rather than rebooting (which probably would have solved it straight away) my first thought was to disable and re-enable the device.
After a reboot that still did not work so I tried to delete the device and add it again. It is even automatically detected and suggested as a new device, but unfortunately it is impossible to add the device. Well it adds it, but you end up with a device called airco and some random string with zero entities in it.
In journalctl I see this:
Nov 16 19:20:52 homeassistant homeassistant[492]: 2022-11-16 20:20:52.015 WARNING (MainThread) [custom_components.mitsubishi-wf-rac] Something whent wrong setting up device [<IP_ADDRESS>] bytes must be in range(0, 256)
Also in the logs I found errors from the time when the reading was not working correctly:
Nov 16 17:07:10 homeassistant homeassistant[492]: 2022-11-16 18:07:10.504 ERROR (MainThread) [homeassistant.helpers.entity] Update for climate.airco_a043b0bd3ff9 fails
Nov 16 17:07:10 homeassistant homeassistant[492]: Traceback (most recent call last):
Nov 16 17:07:10 homeassistant homeassistant[492]:   File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 527, in async_update_ha_state
Nov 16 17:07:10 homeassistant homeassistant[492]:     await self.async_device_update()
Nov 16 17:07:10 homeassistant homeassistant[492]:   File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 722, in async_device_update
Nov 16 17:07:10 homeassistant homeassistant[492]:     raise exc
Nov 16 17:07:10 homeassistant homeassistant[492]:   File "/config/custom_components/mitsubishi-wf-rac/climate.py", line 151, in async_update
Nov 16 17:07:10 homeassistant homeassistant[492]:     await self._device.update()
Nov 16 17:07:10 homeassistant homeassistant[492]:   File "/config/custom_components/mitsubishi-wf-rac/wfrac/device.py", line 69, in update
Nov 16 17:07:10 homeassistant homeassistant[492]:     self._airco = self._parser.translate_bytes(response["airconStat"])
Nov 16 17:07:10 homeassistant homeassistant[492]:   File "/config/custom_components/mitsubishi-wf-rac/wfrac/rac_parser.py", line 270, in translate_bytes
Nov 16 17:07:10 homeassistant homeassistant[492]:     ac_device.Electric = int.from_bytes(vals[i + 2: i + 3], "little", signed=False ) * 0.25
Nov 16 17:07:10 homeassistant homeassistant[492]: ValueError: bytes must be in range(0, 256)
Is it possible the AC is running too long (has been on 24x7 for ±1 week heating at 20C ) forcing some value to go out of the expected range? (since I would never cool for 1 week continiously) Because it seems the reading were already out of range causing it to malfunction. Have not started and stopped the AC unit yet.
I do use a static IP and did also reset the WF-RAC hardware module on the AC unit just to rule that out.
Worked amazingly well until today 👍

Can confirm that turning off the unit does not work. But starting it again (and resetting the power used since last cycle) does solve this bug.
Hope you can look into this 🥇

I think that you have nailed the cause of this error. It would appear that the function int from bytes can only parse values up to 255. (~64 kWh). ac_device.Electric = int.from_bytes(vals[i + 2: i + 3], "little", signed=False ) * 0.25The current input to this function is two bytes long, and will exceed 255.I do not know how to program this nicely in Python, but the line below will probably solve this issue: ac_device.Electric = int.from_bytes(vals[i + 2], "little", signed=False ) * 64 + int.from_bytes(vals[i + 3], "little", signed=False ) * 0.25Op 16 nov. 2022 om 22:07 heeft RBMaurice90 @.***> het volgende geschreven:
For some reason my WF-RAC integration stopped polling information last night. Rather than rebooting (which probably would have solved it straight away) my first thought was to disable and re-enable the device.
After a reboot that still did not work so I tried to delete the device and add it again. It is even automatically detected and suggested as a new device, but unfortunately it is impossible to add the device. Well it adds it, but you end up with a device called airco and some random string with zero entities in it.
In journalctl I see this:
Nov 16 19:20:52 homeassistant homeassistant[492]: 2022-11-16 20:20:52.015 WARNING (MainThread) [custom_components.mitsubishi-wf-rac] Something whent wrong setting up device [<IP_ADDRESS>] bytes must be in range(0, 256)
Also in the logs I found errors from the time when the reading was not working correctly:
Nov 16 17:07:10 homeassistant homeassistant[492]: 2022-11-16 18:07:10.504 ERROR (MainThread) [homeassistant.helpers.entity] Update for climate.airco_a043b0bd3ff9 fails
Nov 16 17:07:10 homeassistant homeassistant[492]: Traceback (most recent call last):
Nov 16 17:07:10 homeassistant homeassistant[492]:   File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 527, in async_update_ha_state
Nov 16 17:07:10 homeassistant homeassistant[492]:     await self.async_device_update()
Nov 16 17:07:10 homeassistant homeassistant[492]:   File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 722, in async_device_update
Nov 16 17:07:10 homeassistant homeassistant[492]:     raise exc
Nov 16 17:07:10 homeassistant homeassistant[492]:   File "/config/custom_components/mitsubishi-wf-rac/climate.py", line 151, in async_update
Nov 16 17:07:10 homeassistant homeassistant[492]:     await self._device.update()
Nov 16 17:07:10 homeassistant homeassistant[492]:   File "/config/custom_components/mitsubishi-wf-rac/wfrac/device.py", line 69, in update
Nov 16 17:07:10 homeassistant homeassistant[492]:     self._airco = self._parser.translate_bytes(response["airconStat"])
Nov 16 17:07:10 homeassistant homeassistant[492]:   File "/config/custom_components/mitsubishi-wf-rac/wfrac/rac_parser.py", line 270, in translate_bytes
Nov 16 17:07:10 homeassistant homeassistant[492]:     ac_device.Electric = int.from_bytes(vals[i + 2: i + 3], "little", signed=False ) * 0.25
Nov 16 17:07:10 homeassistant homeassistant[492]: ValueError: bytes must be in range(0, 256)
Is it possible the AC is running too long (has been on 24x7 for ±1 week heating at 20C ) that some value is going out of the expected range? Because it seems the reading were already out of range causing it to malfunction. Have not started and stopped the AC unit yet.
I do use a static IP and did also reset the WF-RAC hardware module on the AC unit just to rule that out.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>

I think that you have nailed the cause of this error. It would appear that the function int from bytes can only parse values up to 255. (~64 kWh).
ac_device.Electric = int.from_bytes(vals[i + 2: i + 3], "little", signed=False ) * 0.25
The current input to this function is two bytes long, and will exceed 255.
I do not know how to program this nicely in Python, but the line below will probably solve this issue:
ac_device.Electric = int.from_bytes(vals[i + 2], "little", signed=False ) * 64 + int.from_bytes(vals[i + 3], "little", signed=False ) * 0.25

I have the same issue and would like to get the remote commanding back to operation. Since this is my first HACS integration I am a bit lost. Can I just change that line in .py file and reboot to get the integration back working?

I'll wait until there will be a new version with fix, until that i just turn off the Airco and on again via the remote. Then WF-RAC interface resets the calculation and it will work again. Atleast it does for me :).

That should fix it yes 👍
Verstuurd vanaf mijn iPhone
Op 22 nov. 2022 om 09:55 heeft maglerod @.***> het volgende geschreven:

I'll wait until there will be a new version with fix, until that i just turn off the Airco and on again via the remote. Then WF-RAC interface resets the calculation and it will work again. Atleast it does for me :).
—
Reply to this email directly, view it on GitHubhttps://github.com/jeatheak/Mitsubishi-WF-RAC-Integration/issues/28#issuecomment-1323318833, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AZXT7OQYSUITDGARTDSNMGDWJSC7VANCNFSM6AAAAAASCVJ6SE.
You are receiving this because you authored the thread.Message ID: @.***>

Hey Guys,
It looks like it is indeed what @mcheijink is saying.
I will try to implement it but have very little time at the moment.
Sorry for the delay.

My try except did the trick until bug is fixed :)

I think that you have nailed the cause of this error. It would appear that the function int from bytes can only parse values up to 255. (~64 kWh).

The error also occurred here but when reaching 32 kWh and not 64 kWh. 32.75 was the last value I saw before the error.
I have a SRK35ZS

I think that you have nailed the cause of this error. It would appear that the function int from bytes can only parse values up to 255. (~64 kWh).

The error also occurred here but when reaching 32 kWh and not 64 kWh. 31.75 was the last value I saw before the error. Looks like vals[i+2] is a signed byte. I have a SRK35ZS-W2
edit: vals[x] is a signed integer already because of this:
content_byte_array = [ (256 - a) * (-1) if a > 127 else a for a in content_byte_array ]
For me this is working when reaching 32kWh: ac_device.Electric = ( ((vals[i + 3] & 0x7f) + (vals[i + 3] & 0xF0) * 64) + (vals[i + 2] & 0x7f) + (vals[i + 2] & 0xF0) )* 0.25

I changed the line to this and now it works, BUT I am pretty sure the calculation is now wrong. But for me this is ok, i mainly need the controllability. Thanks guys.

For me it is working also above 64kWh and matching my kWh meter.

I don't understand what kind of encoding could work with your expression @glsf91, can you elaborate? Why is the lower part of the first byte multiplied by 64, but the other masks not multiplied?
I think the original code is wrong for two reasons:

it slices just the first byte (vals[i + 2: i + 3]) when it should take both bytes (vals[i + 2: i + 4])
it assumes the value is unsigned, but that is no longer try because of the content_byte_array manipulation mentioned by @glsf91 above

So wouldn't the best fix just be to undo the signing prior to conversion (with both bytes included), like so:
int.from_bytes([v if v >= 0 else 256 + v for v in vals[i + 2: i + 4]], "little", signed=False )* 0.25

I wrote a quick comparison for some example values. Unfortunately I don't have any values >32kWh handy right now, but let me know if this seems correct: https://gist.github.com/bjorne/20829735df1063b1e776ca83f259bf2c

Basically I make it unsigned.
I think your are right: also the upper upper bit should by included in the multiply.
So my solution should be:
ac_device.Electric = ( (((vals[i + 3] & 0x7f) + (vals[i + 3] & 0xF0)) * 64) + (vals[i + 2] & 0x7f) + (vals[i + 2] & 0xF0) )* 0.25
I'm not a python expert. So there are many ways to do this.

I don't understand what kind of encoding could work with your expression @glsf91, can you elaborate? Why are the upper bits of the first byte multiplied by 64, but the other masks not multiplied at all?
I think the original code is wrong for two reasons:

it slices just the first byte (vals[i + 2: i + 3]) when it should take both bytes (vals[i + 2: i + 4])
it assumes the value is unsigned, but that is no longer try because of the content_byte_array manipulation mentioned by @glsf91 above

So wouldn't the best fix just be to undo the signing prior to conversion (with both bytes included), like so:
int.from_bytes([(256 + v) % 256 for v in vals[i + 2: i + 4]], "little", signed=False ) * 0.25

I wrote a quick comparison for some example values. Unfortunately I don't have any values >32kWh handy right now, but let me know if this seems correct: https://gist.github.com/bjorne/20829735df1063b1e776ca83f259bf2c
I'm gonna try my version for a while and see what happens :)
I have the MHI running 24/7 so i've ran into this issue several times now, until i found this thread.

I'm no expert in all of this so i had a quick learning curve in HA to change what you guys wrote about:
Here goes:
/config/custom_components/mitsubishi-wf-rac/wfrac/rac_parser.py (Use 'File Editor' in HA)
Change
ac_device.Electric = int.from_bytes(vals[i + 2: i + 3], "little", signed=False ) * 0.25
to
ac_device.Electric = int.from_bytes([(256 + v) % 256 for v in vals[i + 2: i + 4]], "little", signed=False ) * 0.25
Just changed that single line to yours, restarted HA and MHI WF-RAC integration started working again without restarting the AC.
Hope it will continue to work until the fix is added.
Thanks!

Great to hear @FrankM0. It’s working well for me as well, 125 kWh and counting:

Is the definitive fix ready to be pushed to the main project?
Op 19 dec. 2022 om 22:21 heeft Björn Ramberg @.***> het volgende geschreven:

Great to hear @FrankM0https://github.com/FrankM0. It’s working well for me as well, 125 kWh and counting:
[D2FB9BF9-594B-4EE3-9354-43BD990E41B0]https://user-images.githubusercontent.com/65805/208526235-701eb55a-8305-4403-8f87-c28889aecc05.jpeg
—
Reply to this email directly, view it on GitHubhttps://github.com/jeatheak/Mitsubishi-WF-RAC-Integration/issues/28#issuecomment-1358384266, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AZXT7OXJWINFPKQTKSHJVG3WODGVFANCNFSM6AAAAAASCVJ6SE.
You are receiving this because you authored the thread.Message ID: @.***>

Any timeline on a fix?

@RBMaurice90 the change has been merged into main, as far as i understand.
https://github.com/jeatheak/Mitsubishi-WF-RAC-Integration/commit/38e6dc4af8859e9aa3e440f8eae9a9861be4cff0
Doing this manually has fixed it for me.
So i guess if you redownload main you'll have the fix?

It doesn’t have a new version number? So I can’t upgrade I think, only delete and start over? How do I get this change without breaking my existing HA entities/integrations.


Patch K8s Manifest with Tab Query Strings

Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the maintainers.
e.g
http://localhost:3000/tutorials/cd-pipelines/kubernetes/manifest?pipeline=cd-pipeline&cli-os=linux&linux-platform=amd&deployment=rolling#pick-your-deployment-strategy
What Type of PR is This?

[ ] Issue
[x] Feature
[ ] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s)

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[x] Tested Locally
[x] Optional Screen Shoot.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app


Release v0.36.0

Release Notes
Another day, another release. These are the release notes for the version v0.36.0.
Features

feat(api): Implement GcpGkeAudit CloudAccount interface (#821) (Ross)(fd01c7f)
feat(cli): lacework query fail_on_count (#415) (hazedav)(0b1de6a)
feat: Lacework CDK (Cloud Development Kit) (#544) (Salim Afiune)(b0ba78c)

Other Changes

style(cli): use switch instead of if statements (#822) (Salim Afiune)(e40322c)
chore(deps): bump github.com/mitchellh/mapstructure from 1.4.3 to 1.5.0 (#779) (dependabot[bot])(af66b8e)
chore(deps): bump github.com/imdario/mergo from 0.3.12 to 0.3.13 (#819) (dependabot[bot])(47007f0)
ci: version bump to v0.35.2-dev (Lacework)(1ff58d2)

Docker Images

docker pull lacework/lacework-cli:latest
docker pull lacework/lacework-cli:scratch
docker pull lacework/lacework-cli:ubi-8
docker pull lacework/lacework-cli:debian-10
docker pull lacework/lacework-cli:ubuntu-1804
docker pull lacework/lacework-cli:amazonlinux-2

Closing as there is currently an issue with the pipeline. Waiting for fix.


meshio import errors on sphinx builds

This error seems to have popped up very recently, maybe related to meshio 5.2 or 5.1.2 https://pypi.org/project/meshio/#history
https://github.com/BAMWelDX/weldx/runs/4570280776?check_suite_focus=true

it seems to be related to meshio 5.2.0
https://github.com/CagtayFabry/weldx/runs/4570326311?check_suite_focus=true


If the bundle radio option is not required from the admin panel for the bundle product. so getting Space issue in the none option of the radio option on the bundle product on the shop.

Terms

[X] Before you openning this issue, i have checked if the issue has already been reported.

Bagisto Version(s) affected
master
Issue Description
If the bundle radio option is not required from the admin panel for the bundle product. so getting Space issue in the none option of the radio option on the bundle product on the shop.
Preconditions

Admin should be logged in.
Admin should have at least one bundle product with radio option without required.

Steps to reproduce

Go to 'Shop'
Click on 'The Bundle Product'
See the error

Expected Result
Add space between radio box and text.
Actual Result
Space is missing between radio box and text. Here
Screenshots
No response
Additional context
No response

@Amitk-webkul Assign this issue to me.


Output working data to work_dir in ocean diagnostics

As mentioned in PR #711, none of the ocean diagnostics save the final plotted "working" data as in cfg['work_dir']. This will need to be implemented in the near future.
As @bouweandela  said, these files are:

the  netcdf files containing the exact same data as in the plots, they should be stored in
work/diag_timeseries/Regional_Ocean_Surface_mean_timeseries (path available in cfg['work_dir'] when running the diagnostic). These are needed for e.g. interactive plotting.

adding iris.save(cube, os.path.join(cfg['work_dir'], cube_name)) everywhere you need to save the cube you plotting will do the trick, man

I've been thinking about this. The philosophy of the ocean diagnostics tools is for the preprocessor to do (nearly) all the heavy lifting, then for the diagnostic to just plot the data as it comes. That's why they're written as generic plotting tools. The most we do is to change the units, or take a moving average.
I think it would be a counterproductive to make a second copy of the preproccessed data. There are very few cases where the data are manipulated enough by the ocean diagnostics to warrant being re-written.

I agree! but I think a debug option would still be useful and only if activated it should save the cubes that are plotted, just those ones, and if there was any sort of manipulation that was done to the data inside the diagnostic, if the cubes are just the preprocessed ones then there is no need to save them

that's very useful for debugging and/or review pupropses - imagine your plot will look crazy and then you'll have to either put print statements in the source code or do an actual save of the plotted/final metrics data


Titus oci wrapper

Intercept OCI bundles and inject Netflix environment.

Why isn't all of this logic server-side?

It's in my notes to move this, along with the ENI allocation server side.
Q3.
On Thu, Jun 11, 2020 at 3:13 AM Sargun Dhillon<EMAIL_ADDRESS>wrote:

Why isn't all of this logic server-side?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Netflix/titus-executor/pull/399#issuecomment-642551165,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABGC56JHSGTDHQOQEXGAFHTRWCU4VANCNFSM4N3HJROA
.

We're going to try and use a web hook on "pods/bind" before we go down this road.


Install via Homebrew

Hi Martin,
I'm a MacOS user and find Homebrew useful to manage tools like pagerduty-cli.
It will be great to make it available via Homebrew. I don't know how it can be done, but if it can help see there.
It seems to include a way to publish new release via a Github Action.
Regards,
Sébastien

@sdenef-adeo I wanted a homebrew formula for myself and it can be used as follows:
brew install zph/zph/pagerduty-cli

Which installs it from: https://github.com/zph/homebrew-zph/blob/master/Formula/pagerduty-cli.rb. This is in turn performing an isolated install of node, npm and then v0.1.15 of pagerduty-cli.


May 3rd 2022, Community Meeting Agenda

Dapr Community Meetings
Every two weeks we host a community meeting to showcase new features, review upcoming milestones, and engage in Q&A with the Dapr community - all are welcome, and we encourage participation.
The purpose of this thread is to form a discussion amongst the Dapr community on potential topics to highlight during the meeting. If you have a topic you wish to present or learn more about, please comment and be sure to include your name and a short description of the topic.
The conversations in this thread will directly influence the meeting agenda for the community call on May 3rd, 2022, at 10:00am PST. The meeting agenda will be finalized by a Community Call Host days prior to the meeting.
Thank you and we look forward to hearing your input.

Agenda ideas

https://github.com/dapr/community/issues/158#issuecomment-1090788687

I would like to see a talk on the current best practices for ASP.NET Core based applications. For example, the documentation shows using Invoke functions via the SDK to call these services which has since been deprecated. Specifically interesting to me, calling ASP.NET Core gRPC API's via Dapr. Also, any talk on Blazor WASM and ASP.NET Core APIs are also points of interest for me personally! :D


JSX styles disappear after either a hot reload or navigation

Description
While working on a site I started running into odd behaviour where Panda styles disappear from the site entirely after either a hot reload or a page navigation until yarn dev is killed and restarted. On first page load, the styles are fine, then after either saving a .tsx file or clicking a <Link /> any styles from atomic classes (which I use jsx style props for) disappear from the bundled .css file.
This appears to only affect yarn dev and the production deployed sites are fine.
I've bisected the issue across all recent Panda versions and the site works fine on 0.24.0 and upgrading Panda CSS to either 0.25.0 or any future versions results in this bug. Here's the diff between those two versions if useful: https://github.com/chakra-ui/panda/compare/@pandacss/dev@0.24.0<EMAIL_ADDRESS>Here's a video, hot-linked from the original Discord report:
https://cdn.discordapp.com/attachments/1120305029056831548/1226474491325059124/Screen_Recording_2024-04-07_at_11.03.00.mov?ex=6624e661&is=66127161&hm=49fabe3bf221b0fa60875038cc6e8fe38a2c68b7f0a5ab4885dfee51e628eaab&
(GitHub doesn't support .mov containers so I can convert it if anyone wants to see it and doesn't have Discord)
I'm not fully up to date with how Next.js, PostCSS and Panda really work under the hood so I've got no idea where to really look for solutions. Luckily, since 0.24.0 works fine I can stick on that version for now.
Link to Reproduction
https://github.com/Southclaws/southcla.ws
Steps to reproduce

Clone this repo
yarn dev
click any of the posts
or
open up a page.tsx file and make a change then save the file to trigger a hot reload

JS Framework
React TS
Panda CSS Version
0.25.0+
Browser
All major browsers
Operating System

[X] macOS
[X] Windows
[ ] Linux

Additional Information
Usually, all these atomic classes end up in one of the two css files which Next.js generates:

however, once you either trigger a hot reload or navigate to a new page, the css file only contains styles from global.css and does not contain any atomic classes at all.

It seems because I'm outputting the styled-system directory to src/ via:
https://github.com/Southclaws/southcla.ws/blob/main/panda.config.ts#L20
But I did not specify importMap this caused the issue.
So, solved! But a DX improvement here would be awesome if it's possible for the Panda compiler to figure this out and throw an error!

hey, I'm almost certain (havent tried tho) that it's related to https://github.com/chakra-ui/panda/pull/2500
and yes importMap fixes this, glad you found it !