Unify Preimage definition for incoming and outgoing contracts

We previously have preimages defined as a 32-byte slice for outgoing contracts. Presumably, this is the Secp256k1 point x coordinate, but we have no guarantees as we can pass any [u8; 32] data slice.
For incoming contracts, we had enforced XOnlyPubkey Preimages. This PR unifies the definition so we can have the same guarantees for incoming and outgoing contracts, with the benefits like early detection of invalid preimages returned from RPC (for example, cln-rpc) calls. We don't save invalid preimages to the database.

Codecov Report

Merging #505 (49f0f1f) into master (2a02caa) will increase coverage by 0.03%.
The diff coverage is 88.63%.

@@            Coverage Diff             @@
##           master     #505      +/-   ##
==========================================
+ Coverage   72.74%   72.77%   +0.03%
==========================================
  Files          83       83
  Lines       10637    10829     +192
==========================================
+ Hits         7738     7881     +143
- Misses       2899     2948      +49

Impacted Files
Coverage Δ

client/client-lib/src/lib.rs
86.74% <0.00%> (-1.56%)
:arrow_down:

client/client-lib/src/ln/mod.rs
76.92% <ø> (ø)

client/client-lib/src/ln/outgoing.rs
100.00% <ø> (ø)

fedimint-core/src/outcome.rs
40.32% <0.00%> (ø)

ln-gateway/src/lib.rs
39.81% <ø> (-1.62%)
:arrow_down:

ln-gateway/src/ln.rs
0.00% <0.00%> (ø)

modules/fedimint-ln/src/contracts/incoming.rs
100.00% <ø> (ø)

modules/fedimint-ln/src/contracts/outgoing.rs
100.00% <ø> (ø)

modules/fedimint-ln/src/db.rs
100.00% <ø> (ø)

modules/fedimint-ln/src/contracts/mod.rs
91.54% <100.00%> (+7.33%)
:arrow_up:

... and 18 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

This doesn't work. Preimages on LN aren't pub keys in general but just 32 random bytes. Preimages being pub keys is just a hack we use to encode a pub key without using an additional data field in the contract. We probably just shouldn't do this.

We probably just shouldn't do this.

What should we do? Add another field to the contract? If so, let's make an issue.

Preimages being pub keys is just a hack we use to encode a pub key without using an additional data field in the contract. We probably just shouldn't do this.

If I'm understanding this correctly, then maybe going in the opposite direction may be useful: To encode pubkeys in compressed form within the contract, though I'm not sure how we keep strong guarantees that a  compressed pubkey in preimage field is not a random 32 byte slice

I don't think any big change is worth the trouble here. See https://github.com/fedimint/fedimint/issues/605#issuecomment-1256541240

Looks good to me. Will defer to @elsirion for merging.

@okjodom Seems to be getting stale. Can you rebase and ping Eric to land?

@okjodom Seems to be getting stale. Can you rebase and ping Eric/Justin to land?

Ack.
@elsirion , can you help close? These changes are bound to have more churn as modularization items come in

Just landed. Indeed it's going to be a lot of churn and rebasing. @okjodom https://github.com/fedimint/fedimint/pull/505#discussion_r982941499 doesn't look like it's going to explode but would be great if you could follow-up with a quick fix if needed&possible. Thanks!


Gets stuck at self.socket.recv()

Generation gets stuck at:
  File "/Users/nruiz/Documents/research/domain_sim/tdw_image_dataset/tdw_image_dataset/image_dataset.py", line 185, in __init__
    super().__init__(port=port, launch_build=launch_build, check_version=False)
  File "/Users/nruiz/anaconda3/lib/python3.7/site-packages/tdw/controller.py", line 64, in __init__
    self.socket.recv()

Any idea what this might be?
Thanks!

Nevermind, I guess I have to run the build right?


Bump some stale dependencies in go.mod.

Changes
This bumps:

go-containerregistry (and k8schain)
multierr
x/net
zap

Signed-off-by: Dan Lorenc<EMAIL_ADDRESS>/kind cleanup
Submitter Checklist
As the author of this PR, please check off the items in this checklist:

[ ] Docs included if any changes are user facing
[ ] Tests included if any functionality added or changed
[ ] Follows the commit message standard
[ ] Meets the Tekton contributor standards (including
functionality, content, code)
[ ] Release notes block below has been filled in or deleted (only if no user facing changes)

Release Notes
NONE

Go 1.17 adds these lines, and our diff checker seems to be running Go 1.16.

Whoops, good catch @imjasonh

Go 1.17 adds these lines, and our diff checker seems to be running Go 1.16.
edit: actually, gofmt; source https://golang.org/doc/go1.17

//go:build lines
The go command now understands //go:build lines and prefers them over // +build lines. The new syntax uses boolean expressions, just like Go, and should be less error-prone. As of this release, the new syntax is fully supported, and all Go files should be updated to have both forms with the same meaning. To aid in migration, gofmt now automatically synchronizes the two forms. For more details on the syntax and migration plan, see https://golang.org/design/draft-gobuild.

Oh.. that's.. kind-of bad.. because this means running the ./hack/update-deps.sh will have different output from 1.16 (or before) and 1.17 ?

Oh.. that's.. kind-of bad.. because this means running the ./hack/update-deps.sh will have different output from 1.16 (or before) and 1.17 ?

yeah.... I think I got it by running in a go 1.16 container.

/kind cleanup

/kind cleanup

/lgtm


Request port to GoLand

Hello, I am a GoLand user and I am wondering if it would be possible for this plugin to be ported to the GoLand IDE and presumably other IntelliJ IDEs?
Thanks

Currently this plugin depends on IntelliJ platform's java feature to run TLC (https://github.com/ocadaruma/tlaplus-intellij-plugin/blob/v0.7.3/src/main/resources/META-INF/plugin.xml#L25) but yeah, it sounds reasonable to make it works also on other IDEs.
Let me consider if it's possible.

https://github.com/ocadaruma/tlaplus-intellij-plugin/releases/tag/v0.7.4 has been released.
Now all IntelliJ-based IDEs (including GoLand) is now supported.
Please try it out

It looks good, this is the only strange thing that I note. Though it does not impede me using your plugin.
Please run the Java VM, which executes TLC with a throughput optimized garbage collector, by passing the "-XX:+UseParallelGC" property.

Thank you for doing this work!

Ah yeah, that's a known warning message because G1GC is used by default now.
I think it shouldn't cause any actual problem.


Error: Sec-WebSocket-Accept header

Hello, I looked through some of the closed issues, but didn't necessarily find something to match..
every so often(not exact) I receive the error 'webOS - Error: Sec-WebSocket-Accept header from server didn't match expected value ############'
it doesn't really seem to affect anything, but I see if randomly in the logs. anything I should be aware of? thanks!

You do not have to worry about this issue. I also get it randomly and never noticed any issues from it.


[Intermediate React-Js]: I want to add Dynamic React Dashboard

Closes: #897

Title: [Intermediate React-Js]: I want to add Dynamic React Dashboard
Name: inkerton
Idenitfy yourself: GSSOC

Describe the add-ons or changes you've made 📃
I added the dynamic dashboard project.
Screenshots 📷

Link
Type of change ☑

What sort of change have you made:

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Code style update (formatting, local variables)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist: ☑

[x] My code follows the Contributing Guidelines & Code of Conduct of this project.
[x] This PR does not contain plagiarized content.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly wherever it was hard to understand.
[x] My changes generate no new warnings.

Note to reviewers 📄

@Avdhesh-Varshney What changes do you required can you specify?

@Avdhesh-Varshney  I have made the requested changes

@Avdhesh-Varshney Are there more changes Required?

It can't be approved. Don't create more than 10 commits and not follow guidelines.

Never commit directly in main branch.


[FLINK-7561][streaming] Implement PreAggregationOperator

What is the purpose of the change
To improve performance in certain situations this PR adds basic implementation of pre-aggregation operator for DataStream API.
Verifying this change
This change added PreAggregationOperatorTest
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency):  no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: no

Documentation

Does this pull request introduce a new feature? yes
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented): extensive JavaDocs.

I have benchmarked this code and here are the results of using this operator for tumbling windows, with 1000 number of distinct values in the key and watermark once every 16000 elements:

Benchmark
Score
Error
Units

WindowBenchmarks.preAggregateTumblingWindow
4136.634
± 72.370
ops/ms

WindowBenchmarks.tumblingWindow
2592.292
± 67.317
ops/ms

(benchmark code: https://github.com/dataArtisans/flink-benchmarks/pull/2 )

@mproch you might be interested in this one :)

I think it would be nice to have a utility here in order to make this easier to use:
DataStream result =
    Utils.withPreaggregation(
        stream.timeWindow(Time.minutes(5)),
        myAggregateFunction
    )
    .apply(windowFunction);

The utility would basically take the aggregate function and insert the stream transformation for the pre-aggregation on the "predecessor or the keyed stream, and then set up the WindowedStream again.
Pseudo code:
public static <T, K, W extends Window, A> WindowedStream<T, K, W> preaggregate(
        WindowedStream<T, K, W> windowedStream,
        AggregateFunction<T, A, T> preAggregator) {

   // sanity check that the windowedStream has no custom trigger and evictor

   PreAggregationOperator preAggOp = new PreAggregationOperator(preAggregator, properties from windowed stream);

    DataStream<T> originalStream = 'get predecessor before keyBy from windowed stream'
    DataStream<T> preAggregated = originalStream.transform(preAggOp , ...);

    WindowedStream<T, K, W> windowedAgain = preAggregated
        .keyBy(key extractor from original windowed stream)
        .window(assigner);

    return windowedAgain;
}

I moved everything to flink-streaming-contrib.
@StephanEwen I went one step further and created following helper function:
	public static <K, IN, ACC, OUT, W extends Window> SingleOutputStreamOperator<OUT> aggregateWithPreAggregation(
			DataStream<IN> input,
			KeySelector<IN, K> keySelector,
			AggregateFunction<IN, ACC, OUT> aggregateFunction,
			WindowAssigner<? super IN, W> windowAssigner)

It adds a final aggregation step as well. With version that you proposed user would have to implement two slightly different windowAssigner and aggregationFunction for both the pre aggregation and final aggregation step. This could lead to a confusion and mistakes. Those functions have to be different because assigning windows, creating accumulators and accumulating happens only in the pre aggregation step and it works on INPUT data type, while in final aggregation we are working on a Tuple3<KEY, WINDOW, ACCUMULATOR> and we perform only merging of already created windows and accumulators.

I'm closing this as "Abandoned", since there is no more activity and the code base has moved on quite a bit. Please re-open this if you feel otherwise and work should continue.


Avoid allocating new page for read in case of MEM Cache on client

What changes are proposed in this pull request?
When MEM cache is used on client, we try to acquire an new/empty page from the cache manager before reading from external UFS. When the external read request completes, the data is copied to user-provided buffer, and this page is added back to cache manager. So, this will avoid allocating new page for every read.
Please outline the changes and how this PR fixes the issue.
Why are the changes needed?
This will improve the read performance when MEM cache is used on client.
Does this PR introduce any user facing changes?
Performance Improvement is expected.
Original-author: Huang Hua<EMAIL_ADDRESS>

I think it's definitely desirable that we avoid unnecessary allocations, but this approach is less ideal.
First of all, this new acquire method only works for memory page store, but is added as a public method for any kind of page stores. It's a burden on the caller to check if the underlying store can return a buffer.

This patch is to avoid unnecessary page allocation when MEM page store is used.
If other page store is used, at this moment, the API (acquire()) is not used. Other page stores will write the data to persistent storage, so no need to keep this page as a cache.
Caller should check the return value, in all cases. I don't think it is a burden, but a good practice.

Second, a raw byte array does not carry any ownership, or lifetime information.

Yes, this is a disadvantage.

The page pool inside memory page store is meant to be an optimization trick and implementation detail to reduce GC thrashing, rather than a reliable public API. Returning a page in the pool to outside MemPageStore has the risk that people forget to release the page back to the pool,

The tricky part here is that, the returned page, is just a byte array. It is not managed by the MemPageStore.
As you mentioned, the disadvantage is that it does not carry ownership.
No harm if it is forgotten to be put back to this pool, but that would be a potential bug.

or even worse, accidentally keeps a reference to the array and modifies it after it is returned back to the pool.
This would definitely be a severe bug.
I intended to add a comment to CacheManager:put() to say that, when the ByteBuffer is added to cache manage, the ByteBuffer should not be accessed/modified any further.

This is especially dangerous as it can because mysterious data corruption and is super hard to debug.
I agree, but let's avoid it by testing and code review.

I prefer a more high level abstraction to reuse the underlying buffer, such as a Channel-based API. This way, if a page is backed by a local file, we have FileChannel, if it's backed by a byte array, we can use ByteArrayInputStream wrapped in a channel. Channels have a well-defined lifecycle and is closeable, so people know to properly close them.

I have some discussion with @beinan.
The current patch is not a total solution. Maybe we can have some global memory pool for frequently used buffers, like those in this place. So any cache pages can be tracked, quota-managed to avoid OOM, zero-copy, etc.
This needs more design work, and needs to interact with more components.
For now, this patch may benefit some of the Alluxio users. This needs to be tested and verified.

@huanghua78 @dbw9580 are you still working on this PR? or this PR can be closed?

Let's ask @dbw9580 and @beinan if this is still needed.
If not, it's fine to close it.

@huanghua78 @dbw9580 are you still working on this PR? or this PR can be closed?

Close it since it is not needed currently.


ion-virtual-scroll shows only a limited amount of items and messes up the order when scrolling

Bug Report
Ionic Info
Run ionic info from a terminal/cmd prompt and paste the output below.
cli packages: (/usr/local/lib/node_modules)
    @ionic/cli-utils  : 1.7.0
    ionic (Ionic CLI) : 3.7.0
System:
    Android SDK Tools : 26.1.1
    Node              : v10.5.0
    OS                : macOS High Sierra
    ios-deploy        : 1.9.0
    npm               : 6.1.0

Describe the Bug
When showing a list of items using ion-virtual-scroll, only a limited set if items are visible. When you show a list of 1000 items, only the first 18 items are visible. When you scroll slowly, extra items become visible. When you scroll further down the list (which is invisible) and back up, the items are displayed in the wrong order.
Steps to Reproduce
I created a little test app to reproduce this problem: https://github.com/yannickvg/ionic-virtualscroll. If you run this app you will see the problems described above
Related Code
https://github.com/yannickvg/ionic-virtualscroll
Expected Behavior
The complete list of 1000 items should be visible and when scrolling they should stay in the correct order.
Additional Context
This is maybe related to an issue i created for an earlier version https://github.com/ionic-team/ionic/issues/14682

Fixed in ionic beta.3


New

What is the change?
Made a new folder 'Linked List ' inside the data structures
Moved the file Linkedlist.md to this folder
Created two new files (stacks_intro.md and stacks_example1.md in the stacks folder)
Related issue?
new content
Checklist:
Before you create this PR, confirm all the requirements listed below by checking the checkboxes [x]:

[ y] I have followed the Code of Conduct.
[y ] I have  checked there aren't other open Pull Requests for the same update/change.
[y ] I have you tested the code before submission.
[y ] I have commented my code, particularly in hard-to-understand areas.
[y ] My changes generates no new warnings.
[y ] I'm Hacktoberfest'21 contributor.

Screenshots (if any)

make a issue first


feat: added ctor args that include the environment

feat: added ctor args that include the environment
feat: moved everything but window to __internal for environment

Hi sorry, I was working on it in parallel. Just pushed the exact same changes.

https://github.com/forgojs/forgo/commit/c4001449900574b47dcd358d6969f141bea1884f


Fix order of AXIS_ALIASES

According to Mondrian's javadoc, the order of the axis aliases is:

Columns
Rows
Pages
Chapters
Sections

This PR reflects that.

Hi @rsim, any news about this? Let me know if there's anything that you'd like to be added or changed from this PR.

Sorry, that I didn't merge this earlier.
I found out that in the original Microsoft Server 2000 MDX specification (and Mondrian MDX was based on that specification) the order of axis is columns, rows, pages, sections, chapters https://technet.microsoft.com/en-us/library/aa216771(v=sql.80).aspx
So initially I probably specified the order like this because I found it in MSDN documentation.
So I am wondering that maybe Mondrian has unintentionally mixed the order in their implementation? As probably only few users are using these sections and chapters aliases, then nobody has noticed it.
Are you using these axis aliases?

Are you using these axis aliases?

Yes, and I can confirm that queries that have >= 4 axes will trigger this bug.
See: Mondrian's AxisOrdinal.java

OK, I will merge this to be compliant with Mondrian implementation and will ask them why the order is different than in Miscrosoft implementation.

Thanks! And thanks again for an awesome piece of software.
BTW, I'm using it for a live project for budget and public spending visualization:

http://bahia.presupuestoabierto.org
http://caba.presupuestoabierto.org

See https://github.com/olap4j/olap4j/issues/41.


SCons: Prevent using disable_3d or disable_advanced_gui with tools=yes

Those make no sense for tools build, as the editor uses advanced GUI features heavily, and adding checks for 3D/physics features everywhere in the editor would be cumbersome (and error-prone).
Fixes #1701.

So does this mean that we're officially removing the ability for the engine to be compiled without 3D? What other places is disable_3d useful? If it's cumbersome to add checks for 3D in the editor then what about in other situations? I'm just wondering if it makes sense to have disable_3d as an option at all.

I'm just wondering if it makes sense to have disable_3d as an option at all.

It is still useful for export templates. The editor has everything coupled, it's hard to isolate the 3D part and disable it, but the rest of the engine is still very modular.


Feature request: GUI

Is your feature request related to a problem?
A simple GUI to replicate the functionality of the CLI, similar to what BleachBit offers, would be very helpful.

not actually sure it'll be used much
I suggest to wait a bit and look if other guys will be interested


'Error: undefined' appears on failure-details Slack message

SLACK_MESSAGE_FORMAT=failure-details npx testbeats publish -c testbeats.config.js

Example junit.xml from jest-junit:
<?xml version="1.0" encoding="UTF-8"?>
<testsuites name="E2E Test" tests="38" failures="12" errors="0" time="334.312">
  <testsuite name="site-info" errors="0" failures="12" skipped="0" timestamp="2024-07-09T14:03:34" time="332.454" tests="38">
    <testcase classname="foo should be correct for: bar" name="foo should be correct for: bar" time="20.74" file="test.ts">
      <failure>Error: expect(received).toMatchObject(expected)

- Expected  - 1
+ Received  + 1

@@ -1,7 +1,7 @@
  Object {
-   "Address": "7, Stone Hill",
+   "Address": "",
    "First Name": "Bob",
    "Last Name": "Tree",
    "Status": "",
    at /test.ts:113:33
    at processTicksAndRejections (node:internal/process/task_queues:96:5)</failure>
    </testcase>
  </testsuite>
</testsuites>

failure element should have a message property to include the error.

Does use="optional"mean it's optional? If so, then it doesn't mean it should.

The message property or failure element may be optional. According to the schema, error text should belong to the message property and not elsewhere.
I understand that many test frameworks do not consistently adhere to a specific pattern. It would be beneficial to address this within the jest-unit reporter. We are also open to making adjustments if this can benefit the community overall.

@mnoorenberghe we might have a workaround here.
According to jest-junit plugin code, adding --noStackTraceto your jest test should create the junit XML with nested message attributes (if everything else checks out) for failure tests.
https://github.com/jest-community/jest-junit/blob/master/utils/buildJsonResults.js#L86
Note: this would mean the entire stack trace will likely be removed and may not be reported to slack.
You could try adding a link to the test run/build in the notification for users to view the error message printed on the console instead.

The message property or failure element may be optional. According to the schema, error text should belong to the message property and not elsewhere.

I would be fine with it just omitting the Error: undefined portion of the Slack message if that is undefined (since it's optional according to the xsd)

According to jest-junit plugin code, adding --noStackTraceto your jest test should create the junit XML with nested message attributes (if everything else checks out) for failure tests.

Thanks, I'll give that a try now.

According to jest-junit plugin code, adding --noStackTraceto your jest test should create the junit XML with nested message attributes (if everything else checks out) for failure tests.

Thanks, I'll give that a try now.

The code never sets the message attribute AFAICT, regardless of --noStackTrace.

Does this project have any interest in retrieving the error message from the contents of the <failure> like how jest-junit produces it?

I see a growth in number of users using jest-junit reporter. We can fix this issue in the following ways..

Make changes to the actual package to follow the jUnit standards.
Fork it. Fix it. And release it under a new name.
Or use patch-package to fix the issue.


#50 support installation from custom repository or package file

Adds more flexible installation methods - #50

Refactored adding apt or rpm repository to separate recipe intead of
repeating code in agent and server recipe
Added possible installation from remote_file.
Default install method is still thoughtworks repository
Updated and fixed readme

@tomzo - sorry about merging in #53 first, I'll resolve the merge conflicts and merge your changes in.


Update github-developer-program.md

Why:

What's being changed:

Check off the following:

[ ] All of the tests are passing.
[x] I have reviewed my changes in staging.
[ ] For content changes, I have reviewed the localization checklist
[x] For content changes, I have reviewed the Content style guide for GitHub Docs.

Accepted request


Add support for client credentials grant

OAuth (and therefore OpenID Connect) specifies a client credentials grant with which an authenticated client can request access tokens that are issued to the client itself and not to a specific user.
This is useful to for example support service account functionality.
This PR implements support for that grant type.

I have also tested this with keycloak which works as expected


ADR for Config & GuardDuty

Related to #2328
Changes proposed in this pull request:

add ADR to outline implementation for AWS Config & GuardDuty

security considerations
None, just documentation architecture decisions and implementation plan

@jameshochadel All very good points. I added some notes on responsibility for addressing notifications, which I identified as the maintenance engineer in both cases. Though with AWS Config, there may frankly be a lot of notifications that don't need immediate attention, while for GuardDuty they should always get immediate attention.
Regarding the new accounts, it seems like AWS recommends having an account with the sole responsibility of security tooling. Again, with the "principle of least privilege", the idea would be that the account has the sole purpose of managing security tooling and no permissions to do anything else. Here's some documentation where I think that's what they're saying:
https://docs.aws.amazon.com/prescriptive-guidance/latest/security-reference-architecture/management-account.html
https://aws.amazon.com/blogs/mt/using-delegated-admin-for-aws-config-operations-and-aggregation/
As for the Tooling accounts, I'm not sure which ones you're referring to. We do have some existing accounts that are labeled with "tool" in the name in our aws-admin code. According to @rbogle, they were intended to be for running BOSH, Credhub in a separate account for each environment than the actual deployment resources.
In discussion with @rbogle , we thought it might be best to just create dedicated accounts for the purpose of administering organization-wide security services.


add test to prevent accidental breakage of data-hydrate mechanism

supersedes #4698, closes #4685. This is a compromise measure — it keeps the existing behaviour, but adds a test to make sure we don't accidentally change the hydration mechanism in a way that breaks apps manipulating the markup in certain ways.
Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

[x] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
[x] This message body should clearly illustrate what problems it solves.
[ ] Ideally, include a test that fails without this PR but passes with it.

Tests

[x] Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

[ ] If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpm changeset and following the prompts. All changesets should be patch until SvelteKit 1.0

Should we make it data-sveltekit-hydrate (or sveltekit:hydrate 🐐 if our non-standard adventures make it to 1.0) as well? It'd be good regardless, but especially so if we're officially making it user-facing.

cc @john-michael-murphy — we're planning to change data-hydrate to data-sveltekit-hydrate

@Rich-Harris sorry for delay! Been in OOO.  Thanks for the heads up.


tmux is not displayed correctly when running under mosh

Describe the bug
tmux rendered with strange glitches if running under mosh.exe
To Reproduce
Steps to reproduce the behavior:

mosh.exe -l USER HOST
tmux
bottom bar is get overlapped with terminal commands output; others strange rendering glitches

Environment (please complete the following information):

OS + Version: Windows 1809
Shell: cmd.exe/mosh.exe/tmux

mosh.exe and mosh-client.exe is attached.
aminal-mosh-windows-2019-02-07.zip

It's turned out that the experienced issue is related to extra new line character inserted by ConPTY's internals. Issue with detailed reproducible description reported to MS Console team https://github.com/Microsoft/console/issues/380
Meanwhile, it's supposed to use custom build of mosh-client.exe with workaround to generate console output 1 column shorter than it is to avoid odd ConPTY behavior.
mosh-build-2019-02-27.zip
Moving the issue to Backlog

MS Console Team helped to figure out that tmux issue happens because vt processing is OFF on mosh-client.exe side. Currently mosh-client.exe is built based on MSYS2 toolchain and it seems it has impact of how data goes to std output stream. I was not able to turn vt processing ON directly in mosh-client.exe, but if writing to std stream happens from mosh.exe built with GoLang MinGW based toolchain the issue doesn't happen.
Current direction is to move mosh-client sources to be built under GoLang MinGW toolchain to have native integration with Aminal. This issue shoudn't appear with such solution.

Closed due to complete rewrite as part of bringing the project back to life, please create a new issue if still relevant. Thank you!


Improve 'Duplicates' error caused by table maintenance FUGR

Resolves #3027

Instead of incorrectly reporting 'Duplicates', the error message now informs about the skipped FUGR.
No changes to what is serialized.

New message:

I would like it to be an info message instead of error though. Does abapgit support different error categories?

ZCL_ABAPGIT_GUI_CHUNK_LIB renders different message boxes: warning (e.g. if master language of the repo and system are different), error for exceptions and info for e.g. the version notes of abapGit. But it seems there's no blue info message box which would be cool in my opinion to give the user some feedback about some processes.

The control flow here relies on an exception occurring to exclude the group. I think a reasonable change would be to add severity as an attribute of zcx_abapgit_exception for zif_abapgit_log to decide on.

Seems to work:

After staging the deletions

I've checked out the changes in our project and the change skips the whole function group. This is not a good solution, because generated function groups can contain non-generated coding or even function modules (e.g. required for adapted maintenance views) and custom events may be stored in includes linked to the function group itself.
I'm currently testing a solution, which determines if an include is custom
or SAP, based on the namespace ownership and so far it looks to be working quite well.
The system is closer to how SAP identifies coding and works for Z/Y coding just as well as partner coding (/xy/ Namespaces, like in our add-on).
If I skip the maintenance groups completely, we would loose a good chunk of our add-on coding and not have it in our repository.

@mkaesemann I don't particularly like my or the existing code, bu it seemed to work for my use-cases. I was not aware people put more development on top of the autogenerated content though. This is a dealbreaker. I'm therefore closing this in favor of your upcoming solution.

Please, no smart detection of generated code which works on every system differently - use a robust solution "version everything and let people easily add to ignore list".


[fix]Compile UI error under Node.js 17 version, compatible with nodejs 17

The recently released OpenSSL3.0 in Node.js 17 version, and OpenSSL3.0 has added strict restrictions on the allowable algorithm and key size, which may have some impact on the ecosystem. When compiling the UI, you need to add the environment variable to the A variable to drop OpenSSL back to the old strategy:
export NODE_OPTIONS=--openssl-legacy-provider
Proposed changes
Issue Number: close #xxx
Problem Summary:
Describe the overview of changes.
Checklist(Required)

Does it affect the original behavior: (Yes/No/I Don't know)
Has unit tests been added: (Yes/No/No Need)
Has document been added or modified: (Yes/No/No Need)
Does it need to update dependencies: (Yes/No)
Are there any changes that cannot be rolled back: (Yes/No)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

Why closed ? It's useful


Discover Jackson modules

Switch to using JsonMapper.Builder.findAndAddModules() to allow test extensions to add other modules they need to the SystemTestMapper.
Reviewer checklist

[ ] Ensure relevant issues are linked (description should include text like "Fixes #")
[ ] Ensure any appropriate documentation has been added or amended

Coverage remained the same at 99.308% when pulling ae59f72bf9b8756acd2ec4ad66e52b7873402f98 on discover_jackson_modules into 9e8bd5b9515680409b615315df67b7be3394e282 on main.


Implement a MidenVM Verifier

See https://github.com/Hyle-org/hyle/issues/25
This issue will be closed alongside the other one.

Hello @wraitii can I be assigned this issue? I’m ready to work.

Still available? I can work on this

Sorry, this one is done actually.


Can I use integrated Unit Test panel in Xamarin?

Hi,
is there a way to use the built in unit test functionality of Xamarin Studio (Visual Studio Preview for Mac) to run and display unit tests written with nspec?

Hi,
sorry I don't know how integration with Xamarin works. Maybe there will be hints here:
https://developer.xamarin.com
Are you talking about Visual Studio for Mac?
https://developer.xamarin.com/visual-studio-mac/
Afaik, this is basically rebranded Xamarin Studio. It's still a preview and I don't expect it to work with the same extensions from VS for Windows, but I might be wrong.


Allow PHP-Parser 4.0.1

While updating https://github.com/rectorphp/rector/pull/392, I got an error:
  Problem 1
    - Removal request for nikic/php-parser == 4.0.9999999.9999999-dev
    - rector/better-reflection v3.0.6 requires nikic/php-parser 4.0.x-dev -> satisfiable by nikic/php-parser[4.0.x-dev].
    - rector/better-reflection v3.0.6 requires nikic/php-parser 4.0.x-dev -> satisfiable by nikic/php-parser[4.0.x-dev].
    - Removal request for nikic/php-parser == 4.0.9999999.9999999-dev
    - Installation request for rector/better-reflection ^3.0.6 -> satisfiable by rector/better-reflection[v3.0.6].

rector/better-reflection need to be updated to 4.0 firsr


Can Not Install ANY Packages!

Description
I am trying Install Eslint Package in atom on windows. Installing Starts but there is no progress and it still stuck.
I am NOT using any proxies and internet connection is well.

Thanks for reaching out!
We require the template to be filled out on all new issues and pull requests. We do this so that we can be certain we have all the information we need to address your submission efficiently. This allows the maintainers to spend more time fixing bugs, implementing enhancements, and reviewing and merging pull requests.
Thanks for understanding and meeting us half way :grinning:

And just to clarify, what other packages besides ESLint have you tried to install?  Are you seeing any errors?
And were you trying to install to install https://atom.io/packages/linter-eslint or https://atom.io/packages/eslint?


Fix links in readme

I guess those should be also updated in master branch.

Cool, thanks!

Merged into master.


Better ROS support

Currently the ros_agent.py are basically a simple version of carla ros-bridge. Could you please change it to one that fully ultilize carla ros-bridge? For example, the transformations between frames are not published yet in the script.

And also, the sign of y location is a big problem for us

Hi,
the current form of the ros_agent was intended to be used for the CARLA AD Challenge. As a consequence, the amount of information provided by this agent is very limited to ensure that participants cannot access ground truth data. Hence, the ros_agent offers only a significantly reduced feature set compared to the ros-bridge.
The question is, if you require something that is comparable to the ros-bridge, why not using the ros-bridge directly? You could basically have an agent that starts the ros-bridge (via start.sh as in the ros_agent) and then only does some minimal control work.

Thanks for your reply, I think I would try to implement an agent using that existing code


Add support for json validator

After adding recursive types, we should be able to add json validator that will match every JSON.

Blocked by #2

Blocked by #2


User experience on drawer with large content is not very good

What happened?
In continuation of this issue https://github.com/VolkovLabs/volkovlabs-calendar-panel/issues/157, When label content is a bit long, user experience is not very good, In older version labels with large content was taking the whole width of the drawer, making it readable. But with the new version, labels are restricted with fixed width and large content brings up the vertical scroll and make the experience bad.
Did this work before?
Yes - in old version - I believe it was v1.x
Attach dashboard snapshot below
Environment:
Grafana: 10.3.1
Old Snap v1.0.0

New Snap V3.1.0

Dashboard JSON
New dashboard-1717585093298.json

@yusuf-multhan We update drawer layout #192 and it will be a part of the upcoming release.
@vitPinchuk please test the provided dashboard that issue resolved.

@yusuf-multhan Thank you for your question
Our current implementation and changes #157 #192 suggest using short text tags as labels.
They can be 1-2 or more.
Previously they were not limited in width in pixels, and it was the reason why they broke a layout when the content was long. This was fixed in #157
We currently recommend using a description field for text with long content
The main changes drawer layout in #192 and it will be a part of the upcoming release
Thank you.

@yusuf-multhan Thank you for providing feedback.
@vitPinchuk We can consider to supporting multiple description fields like labels and display them one by one using the latest updates.


Fix compile error at push with vector #59

Coverage increased (+0.4%) to 98.517% when pulling 307e0d3cafc3a7bc8d2594842b91234de25a2cc6 on error_with_vector_bool into 13701eba0b72033b913a12d6a0e24285cb595962 on master.

Coverage increased (+0.005%) to 98.095% when pulling 4a5d369073ae66ddb95e68281e59a18cdc0b9cca on error_with_vector_bool into 13701eba0b72033b913a12d6a0e24285cb595962 on master.


Update sus.py

Hopefully fixed nothing printing if a player doesn't have a hypixel login (raw approved)

ok I need to stop merging without actually looking


APP_BUILD_COMMAND was ignored in pipeline

Describe the bug
Since Octaber 7th 2022 the variable APP_BUILD_COMMAND failed to work on Bitbucket pipeline, which coincide with a new commit on azure-static-web-apps-deploy repository in Bitbucket.
Oryx will ignore the APP_BUILD_COMMAND variable and use the command npm only as demonstrated in the build log: Oryx will build app with the following custom override command: npm.
To Reproduce

Create a bitbucket-pipelines.yml to deploy the static web app using Bitbucket pipeline:image: atlassian/default-image:3
definitions:
  services:
    docker:
      memory: 3072

pipelines:
  branches:
    release:
      - step:
          name: Deploy staging to Azure
          service: docker
          deployment: release
          script:
            - pipe: microsoft/azure-static-web-apps-deploy:main
              variables:
                APP_LOCATION: "$BITBUCKET_CLONE_DIR"
                OUTPUT_LOCATION: "$BITBUCKET_CLONE_DIR/dist/fulfillment"
                API_TOKEN: $API_TOKEN
                APP_BUILD_COMMAND: npm run build-release
                DEVELOPMENT_ENVIRONMENT: release

Push the code to release branch and let the pipeline run.

Expected behavior
Oryx should use my APP_BUILD_COMMAND variable to build the app: Oryx will build app with the following custom override command: npm run build-release
Additional context

The pipelines that are not using APP_BUILD_COMMAND variable deployed successfully which make believe that it was only the APP_BUILD_COMMAND that was causing the issue.

Looking for event info
Could not get event info. Proceeding
Starting to build app with Oryx
Azure Static Web Apps utilizes Oryx to build both static applications and Azure Functions. You can find more details on Oryx here: https://github.com/microsoft/Oryx
Oryx will build app with the following custom override command: npm
Calling oryx build "/opt/atlassian/pipelines/agent/build" -o /bin/staticsites/ss-oryx/app --manifest-dir /bin/staticsites/ss-oryx/app-manifest -p require_build -p disable_recursive_lookup=true -p ORYX_APP_TYPE="static-sites"
---Oryx build logs---

Operation performed by Microsoft Oryx, https://github.com/Microsoft/Oryx
You can report issues at https://github.com/Microsoft/Oryx/issues

Oryx Version: 0.2.20220621.1, Commit: 82ed84f0f3fd3a25ded3029f137601f54e7a1d05, ReleaseTagName: 20220621.1

Build Operation ID: |s1TpePy1KBw=.bcbb4b6e_
Repository Commit : ed9f5043ed654bbf70dd48f0bc2c843e001bdfc4

Detecting platforms...
Detected following platforms:
 nodejs: 16.14.2
Version '16.14.2' of platform 'nodejs' is not installed. Generating script to install it...
Detected the following frameworks: Angular,Typescript

Source directory     : /opt/atlassian/pipelines/agent/build
Destination directory: /bin/staticsites/ss-oryx/app

Downloading and extracting 'nodejs' version '16.14.2' to '/opt/nodejs/16.14.2'...
Downloaded in 0 sec(s).
Verifying checksum...
Extracting contents...
performing sha512 checksum for: nodejs...
Done in 2 sec(s).

Removing existing manifest file
Creating directory for command manifest file if it does not exist
Creating a manifest file...
Node Build Command Manifest file created.

Found npm version spec to follow in package.json: '>=8.1'
Updating version of npm installed to meet the above version spec.

removed 24 packages, changed 93 packages, and audited 212 packages in 2s

11 packages are looking for funding
 run `npm fund` for details

found 0 vulnerabilities

Using Node version:
v16.14.2

Using Npm version:
8.19.2

Running 'npm install --unsafe-perm'...

npm WARN deprecated<EMAIL_ADDRESS>See https://github.com/lydell/source-map-resolve#deprecated
npm WARN deprecated<EMAIL_ADDRESS>Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated<EMAIL_ADDRESS>this library is no longer supported
npm WARN deprecated<EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated<EMAIL_ADDRESS>You can find the new Popper v2 at @popperjs/core, this package is dedicated to the legacy v1
npm WARN deprecated<EMAIL_ADDRESS><EMAIL_ADDRESS>is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.

added 1112 packages, and audited 1113 packages in 1m

125 packages are looking for funding
 run `npm fund` for details

found 0 vulnerabilities

npm <command>

Usage:

npm install        install all the dependencies in your project
npm install <foo>  add the <foo> dependency to your project
npm test           run this project's tests
npm run <foo>      run the script named <foo>
npm <command> -h   quick help on <command>
npm -l             display usage info for all commands
npm help <term>    search for help on <term>
npm help npm       more involved overview

All commands:

   access, adduser, audit, bin, bugs, cache, ci, completion,
   config, dedupe, deprecate, diff, dist-tag, docs, doctor,
   edit, exec, explain, explore, find-dupes, fund, get, help,
   hook, init, install, install-ci-test, install-test, link,
   ll, login, logout, ls, org, outdated, owner, pack, ping,
   pkg, prefix, profile, prune, publish, query, rebuild, repo,
   restart, root, run-script, search, set, set-script,
   shrinkwrap, star, stars, start, stop, team, test, token,
   uninstall, unpublish, unstar, update, version, view, whoami

Specify configs in the ini-formatted file:
   /root/.npmrc
or on the command line via: npm <command> --key=value

More configuration info: npm help config
Configuration fields: npm help 7 config

<EMAIL_ADDRESS>/opt/nodejs/16.14.2/lib/node_modules/npm

---End of Oryx build logs---
Oryx build has completed. Took 76.5160407 seconds. Exit Code: 1
Oryx has failed to build the solution.

For further information, please visit the Azure Static Web Apps documentation at https://docs.microsoft.com/en-us/azure/static-web-apps/
If you believe this behavior is unexpected, please raise a GitHub issue at https://github.com/azure/static-web-apps/issues/
Exiting

Hi @yt11sf, thanks for bringing this to our attention, we've worked on fixing this issue, can you test it now and please let us know if the issue still persists. Thanks

@rupareddy5-21 It was resolved indeed. Thanks for the quick fix and hard work!


feat[ENG 892] MISO Constraints

Summary
This adds the 8 datasets (10 total data getter methods, 2 of which are historical backfill methods) that constitute MISO Constraints.
Details
This is a fair number of new datasets in a single PR and might be a bit of a chore to review, so it may make sense to break up these tasks into either a single dataset or cap it at 5 or something. Can discuss further if we feel it's an issue.
Dataset Handling
Each of these files has gotchas, from persistent typos and slight variations in column headers to varying disclaimer text rows to file types. I think I catch them all, but it makes the code look a bit unkempt IMO. LMK if you have improvement suggestions.
Some of these datasets are sparse, with the files having no useful rows on many days. There are a couple ways to treat this, and I seem to include several without being sure what exactly the Grid Status opinionated way of doing it is.
For instance, we want to separate the idea of other failures (file doesn't exist, date range invalid, etc) from the "file exists and was properly parsed, but there was no constraint data for that day". Right now I handle this with some explicit returning of an empty dataframe with the correct columns:
if data.empty:
            return pd.DataFrame(
                columns=[
                    "Interval Start",
                    "Interval End",
                    "Constraint Name",
                    "Shadow Price",
                    "Constraint Description",
                ],
            )

and subsequently skip the testing of values in the tests:
assert list(df.columns) == [
                "Interval Start",
                "Interval End",
                "Constraint Name",
                "Shadow Price",
                "Constraint Description",
            ]

            if df.empty:
                pytest.skip(
                    "No data available for this date range, so skipping data-comparison assertions",
                )

            assert min(df["Interval Start"]).date() == pd.to_datetime(date).date()

However, the decorator @support_date_range throws an error if there is no data in any of the dfs collected when it tries to concatenate them, making these approaches only work for single day returns (the decorator knowing to eject if there is not actually a date range it needs to handle).

I'm thinking we should handle the case of "successful file pull but empty" with the @support_date_range decorator, but that decorator is used across the codebase so I don't want to touch it here (repo-wide refactoring confidence is not high enough currently, IMO). The decorator could also use some modernization in other areas (f-strings, logging, etc), so that might just be a separate effort, and I don't want it to be a blocker for these datasets.
Tests
Passing Locally (except for the test_get_lmp_weekly_historical_date_range, which I don't touch in this PR)

Currently this punts a bit on figuring out flatfile/binary file VCR fixtures. VCR is really good for standard API response formats (JSON, XML), but the cassette yaml files for binary files are a bit strange, large, and don't seem to have the same replayability as the JSON responses. The binary fixtures are not useless, just not as much of a speedup as a JSON fixture. For now the tests function as the integration style tests on the initial local run, after which you will have fixtures.
Right now I put the fixture creation code in, but add the cassette directory to the .gitignore since

The binary files (e.g. their yaml fixtures) are large, not suitable for source control
The cassette yaml structure gets caught up on the precommit hook check-yaml

Really the "fixture saving" and the "raw file saving" start to look similar in a flatfile implementation. So I will continue to investigate csv, xls, etc binary file fixtures, but sidestep it here, probably until there is a strategy for raw response files saving in general. There is a MISO API that will likely continue to be developed, and future datasets should pull from that if they can, in which case this is a temporary problem and will be slowly remedied by shifting everything we can to pulling from JSON response APIs where vcrpy is exceptionally useful. However, these datasets are not yet available from the MISO API, per @cwaldoch's investigation.
Future Work

Shift what we can to the MISO API, when applicable
Limit Dataset addition tickets to a manageable number of datasets TBD
Figure out strategy for flatfile fixtures with or w/o vcrpy.
Handle successful-but-empty dataframe returns, modernize the @support_date_range decorator

Followup on "what to do with empty dfs" is that downstream systems may not want to try to use empty data.

Followup on "what to do with empty dfs" is that downstream systems may not want to try to use empty data.

For empty data, we often raise NoDataFoundException. Downstream systems can handle that however they need to.


[TR-82] add in logic for risk tagging after synching with ESCU requirements

I think there are a bunch of things missing:

change of the spec file (not only the .md file)
add some validation checks for this value if possible

Questions:

are the risk values mandatory or optional? (I hope optional)
what happens with existent content? Will they all get 3 fields more with default values or will dedicated RBA content developed which have these 3 fields?

@P4T12ICK some quick off the cuff answers for your questions:

are the risk values mandatory or optional? optional
what happens with existent content? We will let the content author decide if he wants to use/include RBA fields when he writes the detection, not included by default. The goal is to enable anyone to tag the fields and modify the detection to be used by RBA, but not modify content to use it by default


Selection isn't visible on editor's text

When any part of code in PyCharm's editor is selected, the selection isn't visible because it is coloured black, while the background is dark grey.
Expected behavior
The contrast of the selection must be increased, by brightening the selection colour or changing it to a brighter one
Screenshots

@alexbeewise thanks, fix will be available in new release in a couple of days

@VladyslavVolkov Are there any updates? Selections are still hardly distinguishable (in a code and in dialog window fields especially).

Will be live in next few days

Should be released in 2023.1.9 tag, use https://plugins.jetbrains.com/files/12118/274760/jetbrains-ide-theme-2<IP_ADDRESS>8.zip until moderation completes


studentCSVCRUD frontend

This pull request contains the frontend of the studentCSVCRUD story. There is also some backend code added to this; however, the full code will be for the backend of the studentCSVCRUD story.
We have rated this a 4 due to the various components needed to implement a fully functional CRUD for students and to be able to implement adequate test coverage for the different cases.

Closed because PR #91 has the code from the branch that the team decided to go forward with


[Bug]

🐛 Bug
NER documentation is inaccurate.
To reproduce
https://libradocs.github.io/html/nlp.html says
newClient = client('path_to_txt’)
newClient.get_named_entities('detect from text')

However this produces error.
newClient.get_named_entities('detect from text')
Traceback (most recent call last):

  File "<ipython-input-8-ae853ca01d72>", line 1, in <module>
    newClient.get_named_entities('detect from text')

AttributeError: 'client' object has no attribute 'get_named_entities'

dir(client):

dir(client)
Out[9]:
...
 'named_entity_query',
...

Spyder4/Python 3.8.5

This is about https://github.com/Palashio/libra, not https://github.com/libra/libra. They're different projects. You'll need to re-file this in the right place.


1.12 compatibility

This switches our UI to use create-react-app for managing our build.
It also updates the UI to be compatible with 1.12.
Fixes #898
/cc @ehazlett

LGTM


Event Type: update, Reason: Parameters: [authRoleName, unauthRoleName] must have values

How did you install the Amplify CLI?
yarn
If applicable, what version of Node.js are you using?
v16.17.0
Amplify CLI Version
10.7.0
What operating system are you using?
MAc
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
no
Describe the bug
If i run amplify push, I get the error:
Name: apiSocialMediaApp (AWS::CloudFormation::Stack), Event Type: update, Reason: Parameters: [authRoleName, unauthRoleName] must have values
Learn more at: https://docs.amplify.aws/cli/project/troubleshooting/
Session Identifier: 582cce8b-5335-4eed-a835-ada81f34056e
I saw someone else had this issue, but nobody gave a solution, they said it was patched in version 10.5.0, but im still getting this error.
Expected behavior
I expected it to push the changes I made
Reproduction steps

Install and set up Amplify Cli
Run amplify push

Project Identifier
8741d2665676fac5a5554da0cf079d3b
Log output

# Put your logs below this line

zsh: no such file or directory: issue-date

Additional information
No response
Before submitting, please confirm:

[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

Similar issue here.
As soon as I modify any resouorce (i.e some lambda code), when I push I get an error like this:
🛑 The following resources failed to deploy:
Resource Name: auth<myAuthReosurceName> (AWS::CloudFormation::Stack)
Event Type: update
Reason: Parameters: [hostedUIDomainName, autoVerifiedAttributes, allowUnauthenticatedIdentities, hostedUI, smsVerificationMessage, breakCircularDependency, oAuthMetadata, mfaTypes, userpoolClientGenerateSecret, mfaConfiguration, authProvidersUserPool, adminQueries, permissions, resourceNameTruncated,
userPoolGroups, smsAuthenticationMessage, passwordPolicyMinLength, userPoolName, userpoolClientWriteAttributes, dependsOn, useEnabledMfas, parentStack, resourceName, triggers, unauthRoleArn, requiredAttributes, authTriggerConnections, aliasAttributes, userpoolClientLambdaRole, authRoleArn, userpoolClientReadAttributes, emailVerificationSubject, sharedId, useDefault, identityPoolName, userPoolGroupList, authSelections, hostedUIProviderMeta, usernameCaseSensitive, serviceName, emailVerificationMessage, userpoolClientRefreshTokenValidity, userpoolClientSetAttributes, passwordPolicyCharacters, defaultPasswordPolicy] must have values
URL: https://console.aws.amazon.com/cloudformation/home?region=eu-central-1#/stacks/<mystakhere>/events

Cli version: 10.7.0

Hey @Arnav7501 :wave: thanks for raising this! What were the last few actions performed prior to receiving this error? Are you running amplify push or amplify push api?
@andreav while your issue is similar in that you are missing paramters' values, the effected resource is different and appears to have a different root cause. Would you mind filing a separate bug report for this?

The last action i performed was adding a new model from amplify studio's UI. The model wouldn't update locally, even though my models had updated after i pulled the changes., so i ran amplify push in hopes of syncing the local files, which led to this error

Hey @Arnav7501 thanks for clarifying!

The model wouldn't update locally, even though my models had updated after i pulled the changes.

Were you running amplify pull to pull the changes you made in Studio? Were these changes deployed with Studio? And lastly, what sort of issues were you experiencing when attempting to update the model locally?

Hey @Arnav7501 are you still experiencing this?

no sorry, I can't remember what i fixed, i think re-installing amplify fixed it

Same problem I cannot update anything even after amplify pull. Any updates on any categories give erros:
Event Type: update
Reason: Parameters: [hostedUIDomainName, oAuthMetadata, authProvidersUserPool, thirdPartyAuth, adminQueries, userPoolGroups, audiences, hostedUIProviderMeta] must have values
`````


Questions and possible error in program.py

Hello,
I am a student and intend to use DSO in my work as I find the concept interesting. I am studying the code, and today I have some problems understanding some lines of code in control.py:

a tostring method is used twice, and I don't find where it is defined, I also don't think it is a python built-in function.

in from_str_tokens in the part where a list of str|float is converted into a list of tokens we have those lines:

for s in str_tokens:
    if s in Program.library.names:
        t = Program.library.names.index(s.lower())
    elif U.is_float(s):
        assert "const" not in str_tokens, "Currently blablabla..."
        t = Program.library.const_token
        constants.append(float(s))
    else:
        raise ValueError("Did not blablabla...")
    traversal.append(t)
traversal = np.array(traversal, dtype=np.int32)

Say we have no PlaceholderConstant in the library. Then according to library.py, Program.library.const_token should be equal to None. Say we have a float in str_tokens. Then we go to the elif part. There is no assertion error since there is no PlaceholderConstant in the library and thus no "const" in the list attribute Program.library.names. So t is set to None and is added to traversal. This should, as I understand it, raise this error:
TypeError: int() argument must be a string, a bytes-like object or a number, not 'NoneType'

in the last line of code (the one converting traversal into a numpy array of integers).

in set_constants, it is written assert U.is_float, "Input blablabla...", but I believe it should be: assert U.is_float(const), "Input blablabla...".

Anyway, even if the things I pointed are errors indeed, it should not be a problem for me as I should only use HardcodedConstant. But as I intend to use your work, I better understand the code in depth.
Looking forward to your reply,
Respectfully, TOP1RM

In program.py we call tokens.tostring() a few times, where tokens is an np.ndarray with dtype=np.int32. This is part of the NumPy API: https://numpy.org/doc/stable/reference/generated/numpy.ndarray.tostring.html.

It is correct that Program.library.const_token is None when you have HardcodedConstant and no PlaceholderConstant. However, if you have a HardcodedConstant like 1.23 in your Library, you will not hit the elif you quoted because the name of the HardcodedConstant is "1.23", so the first if will be True.

Yes, it should be assert U.is_float(const).

Ok thanks for your responses (here and by email !). I just realized that I figured it out months ago for the tostring but I forgot. For the second question, I understand your answer, but then I don't see in what case you will have a float and hit the elif. But that is not a problem, as it is a case I will not encounter I believe.
I close this issue, but may reopen it whenever I have other questions !
Thanks again !

You'd hit the elif when using a PlaceholderConstant because the string will be something like "4.56" (not "const"), so it adds a PlaceholderConstant to traversal.
E.g., str_tokens = ["add","4.56","x1"], where the Library has a PlaceholderConstant but not HardcodedConstant.

TOP1RM is coming back
Hello again, tell me if I should keep my remarks/questions for myself or gather them in order to avoid spamming your repository ! Else I may reopen this issue whenever I can't understand a line I will need (as I said before, I am studying the code, but will only work on the parts that I need).
Today, I think there might be an error in subroutines.py in the function jit_check_constraint_violation_descendant_with_target_tokens. Just below is the code sample I am suspicious about:
if a_in_b(action, effector_tokens, T):
    # Does action match a target token?
    descendant = True
    dangling = 1
elif a_in_b(action, target_tokens, T):
    if descendant:
        return True

I believe having well understood the mechanics of this function, but as I understand it, it should be something like that:
if a_in_b(action, effector_tokens, E):
    # Does action match an effector token?
    descendant = True
    dangling = 1
elif a_in_b(action, target_tokens, T):
    # Does action match a target token?
    if descendant:
        return True

And E would be equal to effector_tokens.shape[0].
Please accept my apologies if I am wrong.
Best regards, TOP1RM

I'm happy to have you pick out the details for us! I think you are correct above. However, it would be much better to actually show code examples where it's providing the wrong result, instead of relying on us re-interpreting the DSO logic :)
Also, we are happy to accept pull requests for this sort of thing! I think you know exactly the changes to be made :)


DUPLO-10400 fixed.

DUPLO-10400 fixed.

Task linked: DUPLO-10400 TF Provider: don't force replacement of msk clusters on config change


is this based in the latest UIKIT version??? are server render compatible??

Hi guys, would be great if you can include in the README.md which uikit version are you using, not sure but I can't see flex component here https://vuikit.js.org/#/ ...so I assume it's not using the latest uikit version no???
also would be great if you include which components are SSR compatible...thank you guys...

Hi, it's based on Vue 2 and UIkit 3, readme updated :)
The flex component is more of a CSS style helper than a component, as such simply use it as indicated in the UIkit documentation. Anyhow, porting those docs in the Vuikit ones could be helpful.
The entire library is compatbile with SSR, at least it should not brake it rendering.

thank you @miljan-aleksic now it's much more clear to me...I going to test it and check...
another question: uikit allows you change the theme just changing your scss variables...
$global-link-color: #DA7D02;

// 2. Import default variables and available mixins.
@import "uikit/src/scss/variables-theme.scss";
@import "uikit/src/scss/mixins-theme.scss";

// 3. Your custom mixin overwrites.
@mixin hook-card() { color: #000; }

// 4. Import UIkit.
@import "uikit/src/scss/uikit-theme.scss";

with vuikit how must I edit these variables???...I'm using nuxt, thank you

The Vuikit Theme is just a custom UIkit theme, is not necessary to be used or imported in your themes. Simply create a custom UIkit Theme in your project.

thanks for the fast response...could for instance. keep using the scss files from uikit and my custom variables???...right now I'm using nuxt and I've a file inside my assets with the imports to the uikit theme and variables, my understand is that vuikit would overwrite this variables so I'm not totally clear how handle the scss files here...
$some-custom-variable: ....;
@import "uikit/src/scss/variables-theme.scss";
@import "uikit/src/scss/mixins-theme.scss";
@import "uikit/src/scss/uikit-theme.scss";

would I keep this file with the style or would cause some troubles???...
thank you so much

Yes, you can do as such and simply don't load the Vuikit theme.

That's a good idea, will take it into consideration.
You are welcome :)


sweepSketch along a drawing not yet available?

As mentioned in #47 I did not find an equivalent to sweepSketch in the drawing API.

// draw curve of hook with Drawing API
let hookCurveDraw = draw().cubicBezierCurveTo(tp1,cp1s,cp1e).cubicBezierCurveTo(tp2,cp2s,cp2e).cubicBezierCurveTo(tp3,cp3s,cp3e).cubicBezierCurveTo(tp4,cp4s,cp4e).done().sketchOnPlane("XY")

// draw curve of hook with Sketcher object
let hookCurveSketch = new Sketcher("XY",1).movePointerTo([0,0]).cubicBezierCurveTo(tp1,cp1s,cp1e).cubicBezierCurveTo(tp2,cp2s,cp2e).cubicBezierCurveTo(tp3,cp3s,cp3e).cubicBezierCurveTo(tp4,cp4s,cp4e).done()

// define cross section of hook
    let hookWidth =   3;
    let hookHeight =  2

// sweep along the sketch works, sweep along the drawing is not available yet?
    let loftedHook = hookCurveSketch.sweepSketch((plane, origin) =>
    sketchRectangle(hookWidth, hookHeight, { plane, origin }) );

As it is now you can just replace hookCurveSketch with hookCurveDraw - it works, doesn't it?

You aren right, it works! Don't know what I did wrong earlier. I thought that in my earlier attempts the error message was that sweepSketch was not defined. This time I also got an error as I forgot to move the plane for the drawing in the Z-direction. In my code above you can see that the drawing is placed on the XY plane whereas the sketch was placed on the XY,1 plane (The XY plane moved one unit up in the Z-direction). I close the issue then.


Translucent effect

To enable/disable translucent effect via attribute

I am sorry for 4 pull requests but I don't know how to merge/edit more files via GitHub.com web interface.

@JonasJonny No worries, thanks for this! I'll merge this in, update the readme and publish the updated version to NPM :)


Allow running previously downloaded installer after failed rustup

I've been having connection timeouts while using rustup all afternoon today, and each time I restart it it has to download the installer all over again. It would be nice if rustup were smart enough to cache artifacts and avoid downloading them again.

Yeah, it would be perfect if this feature is added. I often encounter the timeout problem. It's quite annoying.

Should have been fixed in #958


Secure Supply Chain Slide

File: ee/index.md, CC @gbarr01
The Secure Supply Chain slide seems to be outdated, has a red flag in the top right saying "Not in beta1"

ping @joaofnfernandes

This is already being tracked on a private repo.


New Feature: Omnibar

So, if you've used an editor like Sublime or and IDE like IntelliJ, you've probably encountered a bar like this:

It's a bar which contains all of the available commands for the application and allows you to dynamically search for them. I'd like to add something like that to CQUI, because I think there's lots of potential for dramatically improving UI speed for powerusers this way.
Example: open omnibar, start typing city name, tab to autocomplete, type "pro", tab to autocomplete "produce", type "hor", tab to autocomplete "horseman", enter to send a new horseman entry to the start of the selected city queue.
The possibilities are basically endless here, so I definitely think it's worth the effort investment. Still, it's a considerable undertaking that would come at the cost of other features if I started working on it right now, which is why I'm hoping to gauge excitement for something like this. So what do you guys think? What kind of actions would you like to be completeable using an omnibar, and what kind of syntax do you think would work best?

@Remolten Ultimately, the stated goal of CQUI is to reduce clicks and make useful information more readily available. An omnibar feature falls squarely within the reducing clicks category, it's effectively just a very flexible way to implement keyboard shortcuts when you get right down to it.
As for implementation cost, it wouldn't be an all-or-nothing endeavor. This is definitely the kind of feature that can be implemented piecemeal over time


Handle problematic responses from the Auth0 API

Mo raised this ticket to ensure all API calls from Auth0 are error checked. He (correctly) noted that there were routes through the code that assumed a good response, but would still be called if a bad response were returned. This has the potential for all sorts of bad things to happen.
This PR follows the guidance of two aspects of the Zen of Python:

Explicit is better than implicit.
Errors should never pass silently.

Therefore, all erroneous API responses result in an exception being raised. That's it..!

So it has become apparent that the problem we have is that we're using an empty dictionary to represent several different things in the code: it's a problem in some situations, it's an empty response (apparently) in others and in either case, code that makes changes to state is run (i.e. there is no differentiation in the code).
This fix forces differentiation in that it assumes empty dictionary to be false-y. I'll check again to see what changes need to happen to ensure things are even more explicit. ;-)

OK... I've spent quite a while looking into this. As far as I can tell, the protections we put into place with Mo are enough.
I'm not certain my modifications in this PR add anything to the stability of the app (in fact, they may make it worse since I've added the interpretation of an empty dictionary as a problem in most situations). @xoen has correctly pointed out that get_or_create actually relies on the result being an empty dictionary.
My feeling is this code could be revised to make it more readable. The reason I've not been able to make such changes quickly is because it's not obvious (to me) how the appropriate endpoints are worked out. They come from the resource's __object__.__name__ which is an implementation detail (!) rather than an explicit description of the endpoint. Such implicit usage of Python's dunder attributes makes it really hard to work out where such values come from.
I'm going to add a ticket to the backlog to suggest we address such technical debt and try to make the code more obvious and less magical. Boring, straightforward code is easier to maintain.
Closing as a won't fix.


⚠ Processors has degraded performance

In d28c7aa, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 62 ms

Resolved: Processors performance has improved in 628ab3f.


CandidateExtractor not returning Ngram subspans

Calling CandidateExtractor.apply() with Ngrams(n_max) as the candidate space only returns candidates that are n-grams of length == n_max. The bug I'm reporting is that CandidateExtractor.apply() should return candidates that are n-grams of length <= n_max. As a feature request, it would be great to be able to pass in a range of indices and extract all candidates that are n-grams in that range.
====================
Reproducing the bug:
    ngrams         = Ngrams(n_max=3)
    my_matcher = MyRegexMatcher()
    cand_extractor = CandidateExtractor(candidate,
                                        [ngrams],
                                        [my_matcher],
                                        symmetric_relations=False)
    cand_extractor.apply(sentences, split=0)

    # train_candidates will only contain 3-grams. will not contain 1-grams or 2-grams
    train_candidates = session.query(candidate).filter(candidate.split == 0)

I have written a small program that reproduces the bug. I can send to Alex or pull request if it would be helpful.
=====================
Discoveries:

I found the bug:
on line 68 of /snorkel/matchers.py

            if self.f(c) and (not self.longest_match_only or not any([self._is_subspan(c, s) for s in seen_spans])):
                if self.longest_match_only:
                    seen_spans.add(self._get_span(c))
                yield c

1-grams and 2-grams won't be returned because of the check self._is_subspan(c, s). 1/2-grams are      subspans of 3-grams. I changed matchers.py to just check if c is in seen_spans, rather than if c _is_subspan of a span in seen_spans, and the candidate extractor works as expected, returning all 1-grams, 2-grams, and 3-grams.

Ngrams seems to be working:
Played around with Ngrams class in /snorkel/candidates.py and it appears to be functioning as expected.

@ajratner

@elboy thanks for posting!!  I'll let you know if we need your code but pretty sure we'll be fine- as you were able to locate, this is just something that used to be a flag (for whether to include non-longest-matches, e.g. subsequences of candidate), and must have gotten dropped.  I think we didn't notice because most people use matchers like DictionaryMatch where this is almost always the desired behavior...
Either way will fix soon!

My bad for not answering this properly the first time / the delay in following up: the longest_match_only flag is indeed implemented, so here you would just do e.g.:
my_matcher = MyRegexMatcher(longest_match_only=False)

and then this will work as desired above


Run three node benchmark

this introduces benchmarking of the new node on local machines with a cluster of three nodes, an explorer, and a tx generator.
the setup requires a Postgres instance for the explorer, and the explorer compiled before launching benchmarks.
then the one-button approach to benchmarking is starting the script ./start.sh

bors r+

bors r+

bors r+


2024-08-06 03:57:16.449987: [NET] Routine: decryption worker 3 - started
2024-08-06 03:57:16.449992: [NET] Routine: handshake worker 7 - started
2024-08-06 03:57:16.450058: [NET] Routine: decryption worker 8 - started
2024-08-06 03:57:16.450135: [NET] Routine: TUN reader - started
2024-08-06 03:57:16.450143: [NET] Routine: encryption worker 7 - started
2024-08-06 03:57:16.450345: [NET] peer(zj8L…AHTg) - UAPI: Updating endpoint
2024-08-06 03:57:16.450455: [NET] peer(zj8L…AHTg) - UAPI: Updating persistent keepalive interval
2024-08-06 03:57:16.450506: [NET] peer(zj8L…AHTg) - UAPI: Removing all allowedips
2024-08-06 03:57:16.450587: [NET] peer(zj8L…AHTg) - UAPI: Adding allowedip
2024-08-06 03:57:16.450967: [NET] UDP bind has been updated
2024-08-06 03:57:16.451006: [NET] Routine: receive incoming v4 - started
2024-08-06 03:57:16.451016: [NET] Routine: receive incoming v6 - started
2024-08-06 03:57:16.451035: [NET] peer(zj8L…AHTg) - Starting
2024-08-06 03:57:16.451098: [NET] Interface state was Down, requested Up, now Up
2024-08-06 03:57:16.451112: [NET] peer(zj8L…AHTg) - Routine: sequential sender - started
2024-08-06 03:57:16.451117: [NET] Device started
2024-08-06 03:57:16.451142: [NET] peer(zj8L…AHTg) - Routine: sequential receiver - started
2024-08-06 03:57:16.451190: [NET] Tunnel interface is utun5
2024-08-06 03:57:16.451489: [NET] Network change detected with satisfied route and interface order [en0]
2024-08-06 03:57:16.451651: [NET] Routine: receive incoming v4 - stopped
2024-08-06 03:57:16.451691: [NET] Routine: receive incoming v6 - stopped
2024-08-06 03:57:16.451841: [NET] UDP bind has been updated
2024-08-06 03:57:16.451866: [NET] Routine: receive incoming v6 - started
2024-08-06 03:57:16.451897: [NET] Routine: receive incoming v4 - started
2024-08-06 03:57:16.452179: [APP] Tunnel 'mba15m3' connection status changed to 'connected'
2024-08-06 03:57:16.453357: [NET] peer(zj8L…AHTg) - Sending handshake initiation
2024-08-06 03:57:16.471088: [NET] Network change detected with satisfied route and interface order [en0, utun5]
2024-08-06 03:57:16.471687: [NET] Routine: receive incoming v4 - stopped
2024-08-06 03:57:16.471910: [NET] Routine: receive incoming v6 - stopped
2024-08-06 03:57:16.473139: [NET] UDP bind has been updated
2024-08-06 03:57:16.473297: [NET] Routine: receive incoming v6 - started
2024-08-06 03:57:16.473347: [NET] Routine: receive incoming v4 - started
2024-08-06 03:57:21.204258: [APP] Status update notification timeout for tunnel 'mba15m3'. Tunnel status is now 'connected'.
2024-08-06 03:57:21.693098: [NET] peer(zj8L…AHTg) - Handshake did not complete after 5 seconds, retrying (try 2)
2024-08-06 03:57:21.693346: [NET] peer(zj8L…AHTg) - Sending handshake initiation
2024-08-06 03:57:22.321496: [APP] startDeactivation: Tunnel: mba15m3
2024-08-06 03:57:22.325254: [APP] Tunnel 'mba15m3' connection status changed to 'disconnecting'
2024-08-06 03:57:22.430670: [NET] Network change detected with satisfied route and interface order [en0]
2024-08-06 03:57:22.431139: [NET] Routine: receive incoming v4 - stopped
2024-08-06 03:57:22.431354: [NET] Routine: receive incoming v6 - stopped
2024-08-06 03:57:22.431815: [NET] UDP bind has been updated
2024-08-06 03:57:22.431918: [NET] Routine: receive incoming v4 - started
2024-08-06 03:57:22.432041: [NET] Routine: receive incoming v6 - started
2024-08-06 03:57:22.726137: [NET] Stopping tunnel
2024-08-06 03:57:22.726717: [NET] Device closing
2024-08-06 03:57:22.727160: [NET] Routine: TUN reader - stopped
2024-08-06 03:57:22.727262: [NET] Routine: event worker - stopped
2024-08-06 03:57:22.727369: [NET] Routine: receive incoming v4 - stopped
2024-08-06 03:57:22.727655: [NET] Routine: receive incoming v6 - stopped
2024-08-06 03:57:22.727850: [NET] peer(zj8L…AHTg) - Stopping
2024-08-06 03:57:22.728117: [NET] peer(zj8L…AHTg) - Routine: sequential sender - stopped
2024-08-06 03:57:22.728144: [NET] peer(zj8L…AHTg) - Routine: sequential receiver - stopped
2024-08-06 03:57:22.728432: [NET] Device closed
2024-08-06 03:57:22.728459: [NET] Routine: decryption worker 4 - stopped
2024-08-06 03:57:22.728467: [NET] Routine: decryption worker 5 - stopped
2024-08-06 03:57:22.728500: [NET] Routine: handshake worker 6 - stopped
2024-08-06 03:57:22.728529: [NET] Routine: decryption worker 6 - stopped
2024-08-06 03:57:22.728534: [NET] Routine: decryption worker 3 - stopped
2024-08-06 03:57:22.728605: [NET] Routine: handshake worker 3 - stopped
2024-08-06 03:57:22.728607: [NET] Routine: decryption worker 8 - stopped
2024-08-06 03:57:22.728678: [NET] Routine: decryption worker 7 - stopped
2024-08-06 03:57:22.728697: [NET] Routine: handshake worker 7 - stopped
2024-08-06 03:57:22.728703: [NET] Routine: handshake worker 1 - stopped
2024-08-06 03:57:22.728740: [NET] Routine: handshake worker 4 - stopped
2024-08-06 03:57:22.728817: [NET] Routine: decryption worker 1 - stopped
2024-08-06 03:57:22.728867: [NET] Routine: decryption worker 2 - stopped
2024-08-06 03:57:22.728998: [NET] Routine: handshake worker 2 - stopped
2024-08-06 03:57:22.728989: [NET] Routine: handshake worker 5 - stopped
2024-08-06 03:57:22.729030: [NET] Routine: handshake worker 8 - stopped
2024-08-06 03:57:22.729267: [NET] Routine: encryption worker 2 - stopped
2024-08-06 03:57:22.729275: [NET] Routine: encryption worker 4 - stopped
2024-08-06 03:57:22.729286: [NET] Routine: encryption worker 8 - stopped
2024-08-06 03:57:22.729316: [NET] Routine: encryption worker 7 - stopped
2024-08-06 03:57:22.729311: [NET] Routine: encryption worker 1 - stopped
2024-08-06 03:57:22.729346: [NET] Routine: encryption worker 3 - stopped
2024-08-06 03:57:22.729361: [NET] Routine: encryption worker 5 - stopped
2024-08-06 03:57:22.729365: [NET] Routine: encryption worker 6 - stopped
2024-08-06 03:57:22.761309: [APP] Tunnel 'mba15m3' connection status changed to 'disconnected'
2024-08-06 04:23:59.045840: [APP] App version: 1.0.16 (27)

I have an update.
I think I know what the problem is.
I tried it from my friends house that has ipv4 only, and i can connect! but when i go to my neighbour who has ipv4 and ipv6, it does not work.
Same for my cellular, it only has an ipv4 address.
my modem and wireguard used to support both ipv4 and ipv6, but now the isp has yet to activate my ipv6. could this be causing some weird issue???

I figured out that I needed to change my home network to 198.168.1.xx and everything worked properly for the last half year.

No you need to change the home network to something other than <IP_ADDRESS>/24 (for example <IP_ADDRESS>/24) to avoid conflicts with other networks that use the same subnet. Work on cellular because cellular doesn't use <IP_ADDRESS>/16.


add MIT License

Wasn't sure what to write in the username field.
Tell me if I should change it from WeHows to Harel's full name or something else

thanks. adding.


Allow for toggling events

Closes #7

unknown placings should count for points when the event is selected, might need to add a data attribute for n since when an unknown placing is in a trial event, the point score is lost


Cannot see custom Services or Characteristics on scan (Android)

Hello,
I've been having a very hard time getting my Android phone to recognize custom UUIDs and their associated services and characteristics (using either nRF Connect and even just a custom built Android app using Android.Bluetooth library for Xamarin).
No matter what I do, I cannot get the nRF app to see ANYTHING other than the following:

The iOS app LightBlue recognizes the custom UUIDs and characteristic values no problem! Same with the iOS cross platform version of my own custom Xamarin app.
So this doesn't seem to be an issue with either Xamarin, iOS, or nRF Connect...it seems to be an issue with the way that the Android hardware is scanning for the beacon.
blueoothd IS disabled...hci0 is up and running.
Results of hcidump -i hci0 following "connect" from nRF Connect app on Android

HCI sniffer - Bluetooth packet analyzer ver 5.43
device: hci0 snap_len: 1500 filter: 0xffffffff
HCI Event: Command Status (0x0f) plen 4
LE Read Remote Used Features (0x08|0x0016) status 0x00 ncmd 1

Code running on Raspberry pi
const bleno = require("bleno");
const UUID = '0001000089BD43C8923140F6E305F96D';
const HGHT = '0001000089BD43C8923140F6E305F96D';

var heightChar = new bleno.Characteristic({
        uuid: HGHT,
        properties: ['read'],
        value: new Buffer('77', 'ascii')
});

var primaryService = new bleno.PrimaryService ({
        uuid: UUID,
        characteristics: [heightChar]
});

bleno.on("advertisingStart", err => {

        console.log("advertisingStart");
        if( err ) {
                console.log(err);
                return;
        }
        bleno.setServices([primaryService], err => {
                if(err) console.log(err);
                else console.log("Services set to PrimaryService with one characteristic");
        });
});

bleno.on("stateChange", state => {
        if( state == 'poweredOn' ) {
                bleno.startAdvertising('SmartDesk', [primaryService.uuid], err => {
                        if( err ) { console.log(err); }
                        else {
                                console.log('Broadcasting iBeacon. UUID: ' + UUID);
                        }
                });
        }
        else {
                console.log('Stopped advertising');
                bleno.stopAdvertising();
        }
});

Any help would be greatly appreciated. Thanks.

In nRF Connect the solution was to "Refresh" the device, and then I could see the characteristics.
On the C# Xamarin side the solution was to use the hidden Java reflection method within a function
private void RefreshGattCache() {
    Method m = gatt.Class.GetMethod("refresh",null);
    method.Invoke(gatt,null)
}


Set neutron osp 17 as non-voting

Until rhbz#2069099 is resolved.

The bz is now resolved https://bugzilla.redhat.com/show_bug.cgi?id=2069099#c4, so can now consider revert of the workaround.

The bz is now resolved https://bugzilla.redhat.com/show_bug.cgi?id=2069099#c4, so can now consider revert of the workaround.

Hey Yatin,
I just checkend and indeed the unit test jobs succeed, however there is some problem reported by bandit in pep8 job:
2022-04-11 17:01:59.659623 \| container \| pep8 run-test: commands[8] \| bandit -r neutron -x tests -n5 -s B104,B303,B311,B604
--
1517 | 2022-04-11 17:01:59.659819 \| container \| setting PATH=/root/src/code.engineering.redhat.com/neutron/.tox/lint/bin:/root/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
1518 | 2022-04-11 17:01:59.672613 \| container \| [1652] /root/src/code.engineering.redhat.com/neutron$ /root/src/code.engineering.redhat.com/neutron/.tox/lint/bin/bandit -r neutron -x tests -n5 -s B104,B303,B311,B604
1519 | 2022-04-11 17:02:00.074385 \| container \| [main]	INFO	profile include tests: None
1520 | 2022-04-11 17:02:00.074431 \| container \| [main]	INFO	profile exclude tests: None
1521 | 2022-04-11 17:02:00.074439 \| container \| [main]	INFO	cli include tests: None
1522 | 2022-04-11 17:02:00.074457 \| container \| [main]	INFO	cli exclude tests: B104,B303,B311,B604
1523 | 2022-04-11 17:02:00.074900 \| container \| [main]	INFO	running on Python 3.9.10
1524 | 2022-04-11 17:02:22.768133 \| container \| 1039 [0.. 50.. 100.. 150.. 200.. 250.. 300.. 350.. 400.. 450.. 500.. 550.. 600.. 650.. 700.. 750.. 800.. 850.. 900.. 950.. 1000.. ]
1525 | 2022-04-11 17:02:22.773763 \| container \| Run started:2022-04-11 17:02:22.773106
1526 | 2022-04-11 17:02:22.773818 \| container \|
1527 | 2022-04-11 17:02:22.773826 \| container \| Test results:
1528 | 2022-04-11 17:02:22.773833 \| container \| >> Issue: [B324:hashlib] Use of weak MD4, MD5, or SHA1 hash for security. Consider usedforsecurity=False
1529 | 2022-04-11 17:02:22.773840 \| container \|    Severity: High   Confidence: High
1530 | 2022-04-11 17:02:22.773846 \| container \|    CWE: CWE-327 (https://cwe.mitre.org/data/definitions/327.html)
1531 | 2022-04-11 17:02:22.773852 \| container \|    Location: neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py:2314:23
1532 | 2022-04-11 17:02:22.773858 \| container \|    More Info: https://bandit.readthedocs.io/en/1.7.4/plugins/b324_hashlib.html
1533 | 2022-04-11 17:02:22.773864 \| container \| 2312	            else:
1534 | 2022-04-11 17:02:22.773870 \| container \| 2313	                # Create 32-bit Base32 encoded hash
1535 | 2022-04-11 17:02:22.773875 \| container \| 2314	                sha1 = hashlib.sha1(ip_address.encode())
1536 | 2022-04-11 17:02:22.773881 \| container \| 2315	                iphash = base64.b32encode(sha1.digest())
1537 | 2022-04-11 17:02:22.773887 \| container \| 2316	                return iphash[:hashlen].decode().lower()
1538 | 2022-04-11 17:02:22.773892 \| container \|
1539 | 2022-04-11 17:02:22.773897 \| container \| --------------------------------------------------
1540 | 2022-04-11 17:02:22.773903 \| container \|
1541 | 2022-04-11 17:02:22.773909 \| container \| Code scanned:
1542 | 2022-04-11 17:02:22.773914 \| container \| 	Total lines of code: 104420
1543 | 2022-04-11 17:02:22.773920 \| container \| 	Total lines skipped (#nosec): 3
1544 | 2022-04-11 17:02:22.773925 \| container \| 	Total potential issues skipped due to specifically being disabled (e.g., #nosec BXXX): 0
1545 | 2022-04-11 17:02:22.773931 \| container \|
1546 | 2022-04-11 17:02:22.773936 \| container \| Run metrics:
1547 | 2022-04-11 17:02:22.773941 \| container \| 	Total issues (by severity):
1548 | 2022-04-11 17:02:22.773947 \| container \| 		Undefined: 0
1549 | 2022-04-11 17:02:22.773953 \| container \| 		Low: 0
1550 | 2022-04-11 17:02:22.773958 \| container \| 		Medium: 0
1551 | 2022-04-11 17:02:22.773964 \| container \| 		High: 1
1552 | 2022-04-11 17:02:22.773970 \| container \| 	Total issues (by confidence):
1553 | 2022-04-11 17:02:22.773975 \| container \| 		Undefined: 0
1554 | 2022-04-11 17:02:22.773981 \| container \| 		Low: 0
1555 | 2022-04-11 17:02:22.773986 \| container \| 		Medium: 0
1556 | 2022-04-11 17:02:22.773991 \| container \| 		High: 1
1557 | 2022-04-11 17:02:22.773997 \| container \| Files skipped (0):
1558 | 2022-04-11 17:02:22.871664 \| container \| ERROR: InvocationError for command /root/src/code.engineering.redhat.com/neutron/.tox/lint/bin/bandit -r neutron -x tests -n5 -s B104,B303,B311,B604 (exited with code 1)
1559 | 2022-04-11 17:02:22.871713 \| container \| pep8 finish: run-test  after 379.17 seconds
1560 | 2022-04-11 17:02:22.872061 \| container \| pep8 start: run-test-post
1561 | 2022-04-11 17:02:22.872081 \| container \| pep8 finish: run-test-post  after 0.00 seconds
1562 | 2022-04-11 17:02:22.872270 \| container \| ___________________________________ summary ____________________________________
1563 | 2022-04-11 17:02:22.872287 \| container \| ERROR:   pep8: commands failed

Yours, Szymon

@sdatko So bandit one is a different issue, i will report seperate bz for it and propose a fix.

Reported https://bugzilla.redhat.com/show_bug.cgi?id=2074383 and pushed https://review.opendev.org/c/openstack/neutron/+/837462, if it get's accepted will backport till wallaby.

pep8 jobs also clear now after the backport https://bugzilla.redhat.com/show_bug.cgi?id=2074383, test patch https://code.engineering.redhat.com/gerrit/c/neutron/+/401401

Nice, this is great news @karelyatin, thanks for taking care of this. I will make the jobs voting today.


cmake: fix multiple shield parsing

When multiple shields are defined, only the shield last in the -DSHIELD
list gets defined in .config. This is due to too many backslashes
used defining it for an env setting.
To test this out, you can run the command west build -b stm32f723e_disco samples/hello_world -DSHIELD="x_nucleo_idb05a1 x_nucleo_iks01a1" from a clean environment and take a look at the build/zephyr/.config file. You noticed that there will only be CONFIG_SHIELD_X_NUCLEO_IKS01A1=y without this fix.
With this fix you'll see both CONFIG_SHIELD_X_NUCLEO_IKS01A1=y and CONFIG_SHIELD_X_NUCLEO_IDB05A1=y
Signed-off-by: Ryan McClelland<EMAIL_ADDRESS>

Thanks.  Tested locally as well and works for our build system.

I see that the other user of SHIELD_AS_LIST=${SHIELD_AS_LIST_ESCAPED} surrounds it with ". Did you first test if that would work?

A small suggestion that doesn't add yet another variant of escpaped list.

please ignore for now.
We should probably find tsome time to cleanup and minimize / remove the use of going through environment variables when calling those python scripts.

I see that the other user of SHIELD_AS_LIST=${SHIELD_AS_LIST_ESCAPED} surrounds it with ". Did you first test if that would work?

I did, it did not make a difference.


Clear cache on reboot

Describe Your Problem:
Is there a way to clear the cached accessories every time on reboot?
I am using a plugin that does not support cached accessories called homebridge-nhc2 and I would like to skip that manual step every time the system reboots
Logs:

Show the Homebridge / Homebridge Config UI X logs here.

Homebridge Config:
Show your homebridge config.json here

Screenshots:

Environment:

Node.js Version: v12.16.2
NPM Version: v6.14.4
Homebridge Version: v0.4.53
Homebridge Config UI X Version: v4.16.0
Operating System: MacOS Catalina
Process Supervisor: hb-service

Hi @WesleyLiekens,
The plugin instructions telling you to clear cached accessories is a terrible idea and is just a work around for a broken plugin. Doing this every restart would make it impossible to run any other plugins at the same time.
I'd recommend the plugin author fix their plugin on their end, as I don't think it's a good idea for the UI to facilitate bad design.

That may be so. But I only have need for this one plugin. And the author doesn’t seem to be fixing this anytime soon.
And I have no idea how to do it myself so I’m stuck with doing this manually