generate_trait attribute explanation

#263

sorry commit name is very wrong. should be extend generate_trait 😅

Hi @rkdud007, could you please

Move all cairo code blocks under listings/ as it's already done for other chapters
Refer to specific line of codes using the anchor system https://rust-lang.github.io/mdBook/format/mdbook.html?highlight=ANCHOR#including-portions-of-a-file
Work on making the explanations clearer? It's very confusing as it is written now.
Show what the compiler is producing exactly so that we can understand what kind of magic is happening and how to use the correct naming patterns to use traits when using generate_trait on impls

Try to be as explicit as possible: A framework that could be apply to write any section in the book is

Introduction (present a use case that validates this requirement) / Motivation (why are we doing this)
Solution (present how you can do things)
Example

I will review the PR once these are addressed

@rkdud007 you should close this one and reopen one from main

Alright🫡


[BUG] Search result does not match the criterion on the VM page

Describe the bug
Search result does not match the criterion on the VM page
To Reproduce
Steps to reproduce the behavior:

Go to the VM page
Search a
Then search ar

Result
Search a and search ar came out different results

Environment:

Harvester ISO version: master-head
Installation Mode: ISO
Underlying Infrastructure (e.g. Baremetal with Dell PowerEdge R630):

a is search by id, which prefix is a namespace. I guess is 'default'.
After fixed, It only searches by name, state, CPU, and memory.

Tested on version master-902bee60-head. I was able to filler by VM name, CPU, RAM and state. I was not able to reproduce the previous behavior, namespace is not part of the filtering anymore.
Issue closed.


Batch insert using transactions

Hi everyone,
I'm facing an issue while inserting simultaneously multiple documents in couchbase, using transactions.
What I have read on the couchbase documentation (batching paragraph) is to instantiate a Task for each insertion and wait for the completion of all of them (as documented here)
If I try to execute many inserts in a batch (by instantiating multiple tasks) without using transactions everythings works fine, but when I call the InsertAsync method from the AttemptContext object, an exeception will randomly be thrown.
Here  I've created a repository where you can reproduce the error.
You can find the stack trace listed below:

Couchbase.Transactions.Error.TransactionFailedException: Transaction failed.
---> System.InvalidOperationException: Collection was modified; enumeration operation may not execute.
at System.Collections.Generic.List`1.Enumerator.MoveNextRare()
at System.Linq.Enumerable.Any[TSource](IEnumerable`1 source, Func`2 predicate)
at Couchbase.Transactions.AttemptContext.InsertAsync(ICouchbaseCollection collection, String id, Object content)
at TransactionBulkInsert.Program.<>c__DisplayClass7_1.<b__0>d.MoveNext() in C:\Users\user\source\repos\TransactionBulkInsert\Program.cs:line 73
--- End of stack trace from previous location where exception was thrown ---
at Couchbase.Transactions.Transactions.ExecuteApplicationLambda(Func`2 transactionLogic, TransactionContext overallContext, ILoggerFactory loggerFactory, TransactionResult result)
--- End of inner exception stack trace ---
at Couchbase.Transactions.Transactions.RunAsync(Func`2 transactionLogic, PerTransactionConfig perConfig)
at TransactionBulkInsert.Program.SaveBatch() in C:\Users\user\source\repos\TransactionBulkInsert\Program.cs:line 64
-----------------------Context Info---------------------------
null

Examining the source code I suppose is something related to _stagedMutations property of AttempContext class. In particular seems that the exception was thrown at line 424 when searching for staged mutations while another task may have changed the same collection.
Currently I'm using these nuget packages:

CouchbaseNetClient: v3.1.7
Couchbase.Transactions: v1.0.0

and Couchbase Server Community v.6.6.0
Do you have any suggestion?

@RiPont should be able to help.


simple tool to print out brew and z/os tool versions

This tool is a little hokey - but it's a good 'one off' tool to see what packages we have are lower level than what brew has
Lots of room for improvement.

It would be cool if we can integrate this into the docs or in the progress page (maybe via https://github.com/ZOSOpenTools/meta/blob/main/tools/getbinaries.py).


Fixed integration tests

All tests should now be up-to-date with recent changes in SH service and pass successfully.

Looks ok, tests now pass. I'd now concatenate some split lines (they are not long enough to merit newline split), but that does not impact the functionality whatsoever.
A side note: did you visualise the various OGC requests to understand the different statistics? Any other difference apart from simple/V3 evalscript related transitions?

A side note: did you visualise the various OGC requests to understand the different statistics? Any other difference apart from simple/V3 evalscript related transitions?

I didn't visualize but the main things I noticed are:

changes are only for bands layer, true color layers remain unchanged,
all bands layers now return dataMask as an additional band
all bands layer now return data in FLOAT32 format
Sentinel-1 and I think also Sentinel-3 layers return nan values for areas with no data FLOAT32 format. This is a bit inconsistent with e.g. Sentinel-2 and Landsat 8 which return zeros but in general not a problem.


Upgrade MSRV, dependencies, edition, whitespace

The build is already broken on the specified Minimum Supported Rust Version, because regex and tempfile has moved underneath. This is very hard to resolve with pins, because regex fights back. This probably requires them making changes. Upgrade MSRV 1.34.2 instead.
Upgrade multipart, url (exported), rand and base64. url (via. percent_encoding) requires >=1.33. rand requires >=1.32.
Remove compatibility hacks with 1.24.1, and other deprecated usages.
Run rustfmt and dos2unix to make everything consistent, such that we can...
Move to edition = "2018", via. cargo fix --edition, as we now require a compiler where this is super stable.

Thanks for the PR. I'll be honest, though: I'm extremely reluctant to merge that kind of PRs, because if I wanted to maliciously introduce a vulnerability in a library, I would do it in a PR like this one, that just changes everywhere.

I reviewed up to 59ecbb6 and it looks good!
If you submit up to 59ecbb6, I'll merge.

Done. The old branch (09ce37a) exists at https://github.com/FauxFaux/rouille/tree/bumps-long
The other two commits are just these operations with no other changes, which you can run yourself:

find src examples -name \*.rs -exec dos2unix {} + && dos2unix CHANGELOG.md .gitignore
cargo fmt --all
cargo fix --edition
add edition = "2018" to Cargo.toml
delete extern crate lines


Feature Request: ConsoleOutput as context

To automatically fix errors or have a kind of chat history I think it could be helpful to have the console output visible to the LLM or at least a part of it (1-2k tokens)

Good idea! But very prone to sending sensitive data to OpenAI. Would welcome a PR that puts this under a configuration option that's disabled by default.

Probably won't go with this for shell-ai, it will require being inside a terminal emulator like tmux or screen to have buffer access, I'll let other projects go down that route


function naming conflict

function "UseBear" from file "FluffalUse.lua" conflicts with a function for the Firefist AI of the same name.

I got it, I will change it to UseFluffalBear
Thanks


IndexError: index 1 is out of bounds for axis 3 with size 1

Hello,
I am trying to implement the trainin on the raccoon data on my PC. I have 1 GPU and the process works fine for the Tiny Yolo method.
This is the readout when I am trying to run V3. Im using a Anaconda and Tensorflow backend. Any help would be appreciated.

@JoseMcgee Hi did you manage to solve the issue? I'm facing this issue as well

I'm having the same issue


What Graph API version to use with the policy recording bot?

With the current Graph version 4.24, the bot encounters an exception in AnswerAsync ( same as issue #528 and #523 ). In that issue, it is suggested to use Graph 4.17. But that version has the issue that AdditionalData field is null for a Call in OnNotificationProcessed.
What is the latest supported and recommended Graph version to use?

@zhengni-msft


Dome document enhancement on ValueObject:  only retrieve the mount:'/' from fsSize

Is your feature request related to a problem? Please describe.
I am trying to pull all information of a system by defining a ValuObject
Describe the solution you'd like
I am sure this must be possible: only retrieve the mount:'/' from fsSize
but an example will be most helpful
Describe alternatives you've considered
Document enhancement of providing examples of being able to refine the ValuObject so that only 1 call is needed
Additional context
I have been cobbling together bits and pieces together from different modules but getting everything at once is preferred.
The documentation is very good but I am only missing the above.
Kind Regards,
Gerrit Kuilder

@GerritKuilder this is currently not possible. The ValueObjectlets you define the keys you want to get back for a specific function but if the result is an array, you currently cannot define a filter for the returning array. I will think of how I can include this to the get() function. And of course then I will also extend the documentation how this can be done. Will come back later with a solution.

@GerritKuilder Version 5.0 just released!
Now you have the possibility to also filter results sets in the get function. Here you should find the documentation
https://systeminformation.io/general.html in the lower section.
Be aware: Version 5 is NOT fully backwards compatible to version 5 ... see https://systeminformation.io/changes.html to get an overview over all breaking changes.

@GerritKuilder Version 5.0 just released!
Now you have the possibility to also filter results sets in the get function. Here you should find the documentation
https://systeminformation.io/general.html in the lower section.
Be aware: Version 5 is NOT fully backwards compatible to version 5 ... see https://systeminformation.io/changes.html to get an overview over all breaking changes.


Swap a left column for a right column

ChainerUI draws in a single column on narrow screens like smartphones.
At that time, I changed it to display a chart and a table column first.
Before:

After:

LGTM 🙇


Can anyone please review mio tutorial code?

I'm giving a talk on how to us mio at an upcoming Rust Meetup. I put together a project that is a syslog server in 5 stages that supports UDP v4/v6, TCP v4/v6, and TLS v4/v6 using mio. Before I give the talk, it would be great if someone who's not a beginner like me would take a look at it and make some suggestions for improvement.
https://github.com/pusateri/rslogd
I'm going to continue on with additional stages and add  an example to create a custom evented but that might come at a future meeting. Thanks!

See https://github.com/pusateri/rslogd/issues/4.


Change the image alt attribute from the main file with empty string

Change the alt attributes with the empty string from the main page which language is English.
#42832

/area web-development

But I can not see any alt attribute in this homepage:

But I can not see any alt attribute in this homepage: https://github.com/kubernetes/website/blob/main/content/en/_index.html

But I can not see any alt attribute in this homepage: https://github.com/kubernetes/website/blob/main/content/en/_index.html

@MeenuyD The index page employs Hugo shortcode  to display images, as seen in the file: "{{% blocks/feature image="scalable" %}}". To address the issue with the alt attributes of the images displayed on the homepage, we should modify the shortcode file.
Navigate to the shortocde file feature.html, go to line 11, and remove the alt="{{ .Title }}" attribute, to see if it resolves the problem. I hope this suggestion will be of assistance!
Additionally, please feel free to submit another PR to rectify the alt attributes on the community index page. Your contributions are greatly appreciated!


runtime: eliminate stack rescanning

One of the largest remaining contributors to GC STW time is stack rescanning. I have an approach for eliminating this entirely. This is a tracking bug for implementing this approach.
I will upload a design document and proof soon, and I have a working implementation that I plan to have cleaned up and mailed out in a day or two.
I'm marking this Go 1.9. My current plan is to get the change in for Go 1.8, but have a GODEBUG flag to fall back to the current algorithm for debugging purposes (and in case something goes wrong).
Edit: Design doc
Edit: Things to follow up on in Go 1.9:

Remove stack rescanning
Remove (or replace) stack barriers and delete TestStackBarrierProfiling
Remove debug.gcrescanstacks
Fix early mark termination race
Remove work draining from mark termination and work.helperDrainBlock
Revisit 100us wait in stopTheWorldWithSema
Revisit making the second shade conditional (and the condition for channel ops)

/cc @RLH

We used the "double barrier" to address stack scanning issues in the IBM J9 implementation of Metronome.  It's in section 4.3 of "Design and implementation of a comprehensive real-time java virtual machine" by Auerbach et al, section 4.3.  In that case we were incrementalizing over many thread's stacks, as opposed to the individual stack, but it solves the same problem.
It worked well, although the extra barrier overhead was annoying.  Let me know if you have any questions.
david<EMAIL_ADDRESS>

@davidfbacon, thanks for the reference! Indeed, that looks like the same barrier design. It's good to know that it worked well for Metronome.
I'll update the proposal document to add a citation.

@aclements any numbers on the performance impact of the new barrier?  I haven't checked, but I suspect we've gained more than that from other optimizations since Go 1.7.
They are harder to eliminate at compile time. I completely disabled the optimizations that don't carry over directly to the hybrid barrier and binaries got about 1% larger. We could eliminate some of these, but it requires flow analysis and the current insertion code doesn't do any flow analysis. OTOH, the places where we can eliminate write barriers with the current write barrier aren't all that common anyway (how often do you write the address of a global to something?), so we're not losing much.

Thanks for the clue. The design doc has been updated. It's comforting to
know that this path has been traveled and no gotchas materialized.
On Fri, Oct 21, 2016 at 12:23 PM, Austin Clements<EMAIL_ADDRESS>wrote:

@davidfbacon https://github.com/davidfbacon, thanks for the reference!
Indeed, that looks like the same barrier design. It's good to know that it
worked well for Metronome.
I'll update the proposal document to add a citation.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/golang/go/issues/17503#issuecomment-255420735, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA7Wn1yxx5Gh26g2QaeCeflflTu5vCpdks5q2Ob-gaJpZM4KZ1aw
.

Thank you for the design doc. It looks really great!

For channel operations, the shade(ptr) is necessary if either the source stack or the destination stack is grey.

I'm wondering whether this is necessary.

If the source stack is black, ptr cannot be an unprotected white pointer, so there is no need to shade it.
If the destination stack is grey, ptr will be scanned eventually when the destination stack becoming black (or ptr becomes dead before it).

So maybe we only need to shade(ptr) when the source stack is grey and the destination stack is black. Of course it is ok to just conservatively shade it in Go 1.8.

The hybrid barrier is now live on master.
Detailed benchmark results are in the commit message for bd640c8. The high level summary is that this reduces worst-case STW time to about 100 µs and typical 95%ile STW time to 50 µs (assuming, of course, that the OS doesn't get in the way and that the system isn't otherwise overloaded). Performance impact is about 1% on average and goes up to about 5% for pointer-intensive workloads. However, we've more than paid for this with other throughput improvements in Go 1.8, so nearly all of the benchmarks still show a performance gain relative to Go 1.7.

@cherrymui, I think you're right that channel operations only need the second shade if the source stack is grey and the destination stack is black. For 1.8 we're always performing the second shade (channel operations or not), which is more conservative for correctness and makes it easier to have the GODEBUG setting to fall back to the current behavior (or a superset thereof). But I'll definitely consider your observation in depth for Go 1.9 when I look at making the second shade conditional.

Austin, looks like this can be closed? I'm trying to close or remilestone all Go1.9Early bugs.

Ping @aclements : Should this issue be kept open?


iOS - Edit comment - Editing a message up in the history will make the chat scroll down

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Expected Result:
Message is in focus, user is able to edit it and submit the change
Actual Result:
User is able to edit the message, but message loses focus - the screen is scrolled down until the newest message
Action Performed:

Open app and login
Choose a chat that has a lot of messages (so you have to scroll up)
Long press the message and select edit

Workaround:
Unknown
Platform:
Where is this issue occurring?
Web
iOS ✔
Android
Desktop App
Mobile Web
Version Number: 1.0.58-0
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:
https://user-images.githubusercontent.com/44479856/120241791-81b15280-c231-11eb-881d-1de59da48c13.mp4
Expensify/Expensify Issue URL:
View all open jobs on Upwork

Triggered auto assignment to @jasperhuangg (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

I don't have a physical iOS device to test with (it's not reproducible in a simulator and I assume it's because it doesn't pull up the keyboard). Going to throw this back into the pool!

@jasperhuangg You can open t he soft keyboard on simulator as well.

Issue reproducible today during KI retests

Issue reproducible today during KI retests

@isagoico This is fixed https://github.com/Expensify/Expensify.cash/pull/3551

Issue not reproducible during KI retests (First week)

Issue not reproducible during KI retests (Second week)

Issue not reproducible during KI retests (Third week) - Closing


Dependabot shows npm errors when I only configure pip ecosystem

I have a repository that is showing npm security advisories from dependabot, even though I only have the "pip" ecosystem configured:
version: 2
updates:
  - package-ecosystem: "pip"
    directory: "/src/" # Location of package manifests
    schedule:
      interval: "weekly"

My npm packages are only used at build time, and not deployed. But looks like dependabot sees them because they are in the src/static directory.
I haven't found documentation on this particular issue.
Has anyone found the same situation? How did you solve it?

Hi @tutuca! The .dependabot.yml file is used to configure Dependabot version updates.
The alerts you're getting for npm packages are Dependabot alerts. To configure Dependabot alerts, please follow the steps provided in this article.


Possible bug in startup code for Cortex-M0

Hello,
maybe I have found a bug using this crate. Normally I would say, that the problem is on my side, but I reduced the case as much as I could and the error still arose. I cannot find a user-error in this reduced code, but I may be wrong. So, whats the bug?
When using a large zero-initialized array, the generated startup code is incorrect. Dependend on the optimization setting, the zero_bss code will either loop infinite, produce a HardFault or will work!
I have created a repository with a minimal working example and steps to reproduce:
jfrimmel/cortex-m-rt-bug-MWE.
I'm happy to provide more information, if necessary.

Hi, thanks for reporting and providing a MWE!
I had a go with your MWE on an STM32F0 with just one change (memory.x flash address updated to 0x08000000 for this MCU) it seems to behave as expected in debug mode -- that is, it correctly zeros bss, main runs to increment each element of GLOBAL_ARRAY, and then sits in the final loop{}.
(gdb) r
The program being debugged has been started already.
Start it from the beginning? (y or n) y
Starting program: /home/adam/tmp/cortex-m-rt-bug-MWE/target/thumbv6m-none-eabi/debug/cortex-m-rt-bug-mwe
^C
Program received signal SIGINT, Interrupt.
main () at src/main.rs:20
20	    loop {}
(gdb) p GLOBAL_ARRAY
$6 = [1 <repeats 1024 times>]

Compared to what you note in your README, I see a sensible address for sbss:
(gdb) b zero_bss
Breakpoint 2 at 0x8000b7c: file /home/adam/.cargo/registry/src/github.com-1ecc6299db9ec823/r0-0.2.2/src/lib.rs, line 171.
(gdb) r
The program being debugged has been started already.
Start it from the beginning? (y or n) y
Starting program: /home/adam/tmp/cortex-m-rt-bug-MWE/target/thumbv6m-none-eabi/debug/cortex-m-rt-bug-mwe

Breakpoint 2, r0::zero_bss (sbss=0x20000000 <cortex_m_rt_bug_mwe::GLOBAL_ARRAY>, ebss=0x20000400)
    at /home/adam/.cargo/registry/src/github.com-1ecc6299db9ec823/r0-0.2.2/src/lib.rs:171
171	    while sbss < ebss {
(gdb) p sbss
$3 = (u32 *) 0x20000000 <cortex_m_rt_bug_mwe::GLOBAL_ARRAY>
(gdb) p ebss
$4 = (u32 *) 0x20000400
(gdb) p &sbss
$5 = (u32 **) 0x200007f0

Whereas you apparently see &sbss as inside GLOBAL_ARRAY. Are you absolutely sure you printed &sbss instead of sbss at that point? Since sbss is updated to point to each address in bss in turn (check out zero_bss here), it absolutely makes sense to see sbss as 0x200003f0 but would be a bizarre error for the stack-allocated function variable to be allocated inside what the linker already knows is an allocated object.
You might try sticking cortex_m::asm::nop() inside your loop{} since there is a known issue with LLVM mishandling empty loops. You could also try using arm-none-eabi-gcc as the linker (put "-C", "linker=arm-none-eabi-gcc" in your .cargo/config) and see if that makes any difference.

First, excuse me for the long delay, but I was very busy with other projects.
I had some more time to investigate this issue on my embedded system. I'm very certain, that the observed behavior is not due to this crate. I never really thought of this, as the Rust code looked correct at all time. Below you'll find my debugging steps, maybe they will be helpful in future issues of this kind.
So, first of all, where was the error? To answer the question I should add the used microcontroller: it was a EFM32TG11B120, which is a relatively new controller by SiLabs. This controller comes equipped with an internal bootloader, that runs first after the reset, i.e. before the first instruction of the flashed application. This bootloader sets up the stack pointer incorrectly!
The stack pointer was set to a value 1kiB above the RAM start. So the stack pointer could eventually reach the bottom of the RAM when initializing the array with 1kiB size. That has hidden the error, when only using little memory, since the stack pointer was always inside the RAM (although it could override user data, which almost certainly happend in my application before...).
Note, that the stack pointer value, i.e. the first entry in the "vector table" was specified correctly to the top of the RAM, but the bootloader didn't set this value up before calling the application.
The solution (for me) was to disable the bootloader via the MSC unit. Refer to the datasheet how to do this or reach out to me if you have problems doing that. After disabling the bootloader the stack pointer was set up correctly by the Cortex-M core and everything worked as expected.
I'm not sure if this is a real error of the bootloader or again an error in its usage. But I think that sharing the solution might help someone out there :smile:

Thanks for wrapping this issue up!


[Bug Report] The last 84 dimensions of Humanoid-v4 are always zero.

Describe the bug
The documentation of Humanoid-v4 says it no longer has the contact force issue. But I still find that the last 84 dimensions of states in Humanoid-v4 are always zero.

Code example
import mujoco
import gymnasium
env = gymnasium.make("Humanoid-v4")
s, _ = env.reset()
for i in range(3):
    action = env.action_space.sample()
    next_state, reward, done, truncated, _ = env.step(action)
print(next_state[-84:])

System info
gymnasium_ver: 0.26.3
mujoco_ver 2.2.0
Ubuntu
Additional context
No response
Checklist

[X] I have checked that there is no similar issue in the repo

In this environment the humanoid is spawned in mid-air. Thus it won't touch the ground and there will be no external contact forces detected.
If you step the simulation a little longer until the humanoid touches the ground, contact forces should appear.


Flexible export configuration syntax

Hey 👋,
We think that we'll eventually need a more sophisticated mechanism to define output.resolvers and output.models. An opinionated mechanism is an option but we should aim for good defaults rather than making such decisions at the current stage of graphqlgen
We thought something similar to {typeName} could work quite nicely but there might be a better solution. 🙂

Superseded by https://github.com/prisma/graphql-resolver-codegen/issues/106.


report error in windows

hello, i use in windows, and it report the error:
PS D:\hpmq> cargo generate --git http://git.netfuse.cn/iiot-pub/hpmq-wasi-template.git
Error: 拒绝访问。 (os error 5)

the reason for this is https://github.com/XAMPPRocky/remove_dir_all/issues/7
i think not remove the .git folder, in turn not to copy .git to project's folder can avoid this problem?

I am having what I believe to be the same issue, and discussed it with some people on the Rust Embedded matrix channel who were able to replicate the issue.
The problem seems to occur on Windows machines (I am on windows 10) when using cargo generate on a remote template. I tested with a github template From here
cargo generate      --git https://github.com/knurling-rs/app-template      --branch main      --name my-app
The current workaround we found was to manually clone the template and run generate locally. Hope this helps!

unfortunately on windows 11 for arm I was not able to reproduce this problem.

I vaguely remember having that issue reproducible. The solution was very stupid, a little waiting time after the git clone before the recursive remove was doing the trick back then.
So this code should actually take care of the mess.
Did you actually get the warning message below?
warn!("Git history cleanup failed with a windows process blocking error. [Retry in {:?}]", wait_for);

Update: which cargo-generate version do you folks use?

Version was the latest, I even forced a fresh install with cargo when I was having problems.
I do recall getting some error relating to windows blocking operation where it would retry after a second or two. Sometimes it would take several retries but would always result in the permission denied/ os error 5 eventually.
This would happen maybe 20% of the time, it would usually just go straight to permission denied.

i try again in other pc and it also report error. i had commited a pull(https://github.com/cargo-generate/cargo-generate/pull/621),  It should be more intuitive to look at the code

#621 should solve this, and will be released soon


Horizontal scroll blocking natural body scroll

Check out this homepage http://solascriptura.ro/
When hovering over the scroll-container the page scrolls just horizontally
Maybe this behavior is the desired one, but I've found this commit
https://github.com/echa/ng-scrollable/commit/7c3cfa4aac8f081294e6e6505d955ba7615d9c66
where on line 601 the if block is commented. If I uncomment that block I do get the natural vertical page scroll.
(maybe by the time you see this issue the page will be updated and you won't see the issue as a demo)
Thank you very much for this useful component

Hey, the quick fix for you would be to add scrollY:'none' to your horizontal ngScrollable.
Vertical scrolling is enabled by default and the older version you use does not read the height of your content correctly (so it does not know when the end is reached). You can update to the latest master branch if you like.
Feel free to reopen if this did not solve your problem.


feat(runtime): add extract to process specified token(s)

What's the use case of this?

My use case in vue is to preempt style update before render begin. This should ensure the css are available particularly before animating/showing overlay etc.


Add optimization notebook

Initial version of the optimization notebook. I have not yet added all the "bells and whistles" that are possible, because I want to get feedback on the core first.  Then we can make it pretty.
One thing that I think can immediately be improved is to replace much of the manual contribution/ROAS calculation code with things like mmm.channel_contributions_forward_pass() etc. These helper functions didn't exist when the notebook was first created.
Also, I had planned on omitting all the MMM example notebook code, but realized I need to serialize the model, the inferenceData object, and the input data (and possibly more?). So I just kept the code but stripped it down to the essentials. Keeping all these cells also prevents "syncing" issues between this notebook and the MMM example notebook.
Todos:

[ ] Replace objective function code with pymc-marketing functionality as possible
[ ] Make objective function a compiled pytensor function to avoid eval()s
[ ] Add additional exploration of optimization results (e.g., risk attitudes, diversification penalty, etc.)

:books: Documentation preview :books:: https://pymc-marketing--358.org.readthedocs.build/en/358/

This seems stale. Shall we close and turn into smaller issues?
Thoughts @cluhmann @juanitorduz

This notebook has many great ideas that I would like to explore further. Can we leave it open while I try to get some time? Maybe we can add a special label?

Or actually, as it is a dev notebook, can we merge it into the folder (as the clv dev ones)?

Happy to help hammer this into something (more) useful.

How about merge in since it is dev notebook and then create an issue or two?

Fine with me.

Did the latest optimization notebooks kill the need for this?

The one thing that I will want out of this PR is a notebook in which we compare one model/data set and various approaches to optimization, including:

optimization using point estimates (i.e., the old method of optimization)
optimization using full posterior but neutral utility (e.g., mean/expected response)
optimization using full posterior but utility functions reflecting various risk profiles

I think this that seeing how these different approaches yield different optimized spends would really drive home the value of this new approach to optimization and introduce the Bayesian decision theory stuff at the same time.  I talked to @carlosagostini about this when he was first working on the optimization.


dts: bindings: Update Nordic owned memory bindings

This concerns both nordic,owned-memory and nordic,owned-partitions.
Introduce a property named nordic,access, which is meant to replace
the owner-id and perm-* properties. It allows for describing how
multiple domains should access a single memory region, possibly with
different permissions per owner, but without having to create more than
one DT node for this purpose.
This change is also motivated by updated memory protection requirements
on the nRF54H20, which mandate that a given memory region must only be
reserved by one domain, even if multiple domains can have access to it.
This restriction is now described in the binding itself.

@57300 , I understood this change should be merged. Do you plan to continue working on this?

@57300 , I understood this change should be merged. Do you plan to continue working on this?

Yes, I will reopen once internal dependencies are resolved.

I think I'll need this for #78253.

Reopened, rebased, and added new changes for nrf9280pdk.


Update sbt to 1.7.1

Updates org.scala-sbt:sbt from 1.4.9 to 1.7.1.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Applied Scalafix Migrations

org.scala-sbt:sbt:1.5.0

https://gist.githubusercontent.com/eed3si9n/57e83f5330592d968ce49f0d5030d4d5/raw/7f576f16a90e432baa49911c9a66204c354947bb/Sbt0_13BuildSyntax.scala
Documentation: https://eed3si9n.com/syntactic-scalafix-rule-for-unified-slash-syntax

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-sbt", artifactId = "sbt" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "org.scala-sbt", artifactId = "sbt" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, scalafix-migrations, commit-count:n:2

Superseded by #116.


Change token used for pipeline templates

Describe your changes
Swap token used by the pipelines to get templates. The "Planning-Inspectorate" token is automatically created and uses the GitHub Azure Pipelines app instead of an OAuth token. This will stop the token expiring and the need for it to be refreshed.
Type of change 🧩

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update
[x] Other (please explain in the description section above)

Checklist before requesting a review

[x] I have performed a self-review of my own code
[x] I have double checked this work does not include any hardcoded secrets or passwords
[ ] I have made corresponding changes to the documentation
[ ] I have provided details on how I have tested my code
[ ] I have referenced the ticket number above
[x] I have provided a description of the ticket
[ ] I have included unit tests to cover any testable code changes

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


test_app does not have a config object

I'm using the async with app.test_app() to ensure that the before_serving and so on routines are run to run functional tests. Unfortunately, it seems that the config object is not added to the test app and thus needs to be added manually, i.e. with the workaround:
 async with app.test_app() as my_test_app:
     my_test_app.config = app.config

This seems like a bug, as my before_serving routines populate app.config.
Minimal example:
import asyncio
from quart import Quart

app = Quart(__name__)

print(app.config)

async def test():
    async with app.test_app() as my_test_app:
        print(my_test_app)
        print(my_test_app.config)

asyncio.run(test())

crashes with output
<Config {'APPLICATION_ROOT': None,  .... >
<quart.testing.app.TestApp object at 0x7f985e30b430>
...
AttributeError: 'TestApp' object has no attribute 'config'

Environment:

Python version: 3.10
Quart version: 0.18.4

The test client is not the same as the app, it wouldn't have the same attributes or methods. You still have the app, access it directly.

The test app object is documented as being for ensuring lifecycle and background tasks complete. https://quart.palletsprojects.com/en/latest/how_to_guides/background_tasks.html#testing-background-tasks It's not intended as a proxy to the actual app.

Ok, I understand what to do then. Using
@pytest.fixture
async def test_app()
  await app.startup()
  yield app
  await app.shutdown()

yields a test_app that has undergone startup / shutdown.


The syndicatide [April Fools]

About the PR

Syndicate reinforcement 16TC->5TC, maybe could be reduced even more?
Media

[ ] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Changelog

:cl:

tweak: The Syndicate has recently received a massive influx of reinforcement agents.

We already have enough "high chaos" things like everyone getting a gun.


Add support for hidden recipients

When receiving an encrypted email that doesn't contain my key ID, OutlookPirvacyPlugin fails by declaring that it couldn't find the secret/private key to decrypt the message.
The expected behaviour is that the decryption logic should attempt to decrypt using available secret keys until either the decryption is successful or all available secret keys have been attempted.
More on this issue:
https://github.com/open-keychain/open-keychain/issues/626
https://www.gnupg.org/documentation/manuals/gnupg/GPG-Key-related-Options.html

BETA 52 will have support for this.

Closing. Please re-open if this is still an issue.


Added function to set destination path for binary

Allows to set a path where the binary will be placed (with package name, still)

why?


all runs associated with dataset (list view)

User story: (3.5) I want to see all runs associated with this dataset + filter/sort within the dataset so that I can easily navigate large amounts within dataset
Tasks

[ ] show list of runs

Link to design: https://www.figma.com/file/WEmbsjtlBUtRy7pzmuCCjj/CryoET-Data-Portal---Phase-2-Designs?type=design&node-id=757%3A86414&mode=dev

@codemonkey800 - backend story where you'll find the key photos https://github.com/chanzuckerberg/cryoet-data-portal/issues/56

Following defects found:
"Run" title in single dataset page should be in blue and clickable for sorting #166
Clickable area taking the user to Run page is not responding #167
Tooltips overlap when open one after another #168
Clickable area next to "Run"/"Dataset" title is too long #169

Passing this item to Completed as bugs opened are taking care of already, no need to track this one here, thank you!


Bandwidth limitation not working for HLS/Safari

Have you read the FAQ and checked for duplicate open issues?
Yes
What version of Shaka Player are you using?
3.1.1
Can you reproduce the issue with our latest release version?
Yes
Can you reproduce the issue with the latest code from master?
Yes
Are you using the demo app or your own custom app?
Custom App
If custom app, can you reproduce the issue using our demo app?
What browser and OS are you using?
macOS Big Sur, Safari 14.1.1
For embedded devices (smart TVs, etc.), what model and firmware version are you using?
What are the manifest and license server URIs?

Provided via Email
What configuration are you using?  What is the output of player.getConfiguration()?

"{
"drm": {
"retryParameters": {
"maxAttempts": 2,
"baseDelay": 1000,
"backoffFactor": 2,
"fuzzFactor": 0.5,
"timeout": 30000,
"stallTimeout": 5000,
"connectionTimeout": 10000
},
"servers": {
"com.widevine.alpha": "...",
"com.microsoft.playready": "...",
"com.apple.fps.1_0": "..."
},
"clearKeys": {},
"advanced": {
"com.apple.fps.1_0": {
"distinctiveIdentifierRequired": false,
"persistentStateRequired": false,
"videoRobustness": "",
"audioRobustness": "",
"sessionType": "",
"serverCertificate": {
...
},
"individualizationServer": ""
}
},
"delayLicenseRequestUntilPlayed": false,
"logLicenseExchange": false,
"updateExpirationTime": 1
},
"manifest": {
"retryParameters": {
"maxAttempts": 2,
"baseDelay": 1000,
"backoffFactor": 2,
"fuzzFactor": 0.5,
"timeout": 30000,
"stallTimeout": 5000,
"connectionTimeout": 10000
},
"availabilityWindowOverride": null,
"disableAudio": false,
"disableVideo": false,
"disableText": false,
"disableThumbnails": false,
"defaultPresentationDelay": 0,
"dash": {
"clockSyncUri": "",
"ignoreDrmInfo": false,
"disableXlinkProcessing": false,
"xlinkFailGracefully": false,
"ignoreMinBufferTime": false,
"autoCorrectDrift": true,
"initialSegmentLimit": 1000,
"ignoreSuggestedPresentationDelay": false,
"ignoreEmptyAdaptationSet": false,
"ignoreMaxSegmentDuration": false,
"keySystemsByURI": {
...
}
},
"hls": {
"ignoreTextStreamFailures": false,
"useFullSegmentsForStartTime": false
}
},
"streaming": {
"retryParameters": {
"maxAttempts": 2,
"baseDelay": 1000,
"backoffFactor": 2,
"fuzzFactor": 0.5,
"timeout": 30000,
"stallTimeout": 5000,
"connectionTimeout": 10000
},
"rebufferingGoal": 2,
"bufferingGoal": 10,
"bufferBehind": 30,
"ignoreTextStreamFailures": false,
"alwaysStreamText": false,
"startAtSegmentBoundary": false,
"gapDetectionThreshold": 0.1,
"smallGapLimit": 0.5,
"jumpLargeGaps": false,
"durationBackoff": 1,
"forceTransmuxTS": false,
"safeSeekOffset": 5,
"stallEnabled": true,
"stallThreshold": 1,
"stallSkip": 0.1,
"useNativeHlsOnSafari": true,
"inaccurateManifestTolerance": 2,
"lowLatencyMode": false,
"autoLowLatencyMode": false,
"forceHTTPS": false,
"preferNativeHls": false
},
"offline": {
"usePersistentLicense": true
},
"abr": {
"enabled": true,
"useNetworkInformation": true,
"defaultBandwidthEstimate": 1000000,
"switchInterval": 8,
"bandwidthUpgradeTarget": 0.85,
"bandwidthDowngradeTarget": 0.95,
"restrictions": {
"minWidth": 0,
"maxWidth": null,
"minHeight": 0,
"maxHeight": null,
"minPixels": 0,
"maxPixels": null,
"minFrameRate": 0,
"maxFrameRate": null,
"minBandwidth": 0,
"maxBandwidth": 1400000
}
},
"preferredAudioLanguage": "",
"preferredTextLanguage": "",
"preferredVariantRole": "",
"preferredTextRole": "",
"preferredAudioChannelCount": 2,
"preferForcedSubs": false,
"restrictions": {
"minWidth": 0,
"maxWidth": null,
"minHeight": 0,
"maxHeight": null,
"minPixels": 0,
"maxPixels": null,
"minFrameRate": 0,
"maxFrameRate": null,
"minBandwidth": 0,
"maxBandwidth": null
},
"playRangeStart": 0,
"playRangeEnd": null,
"useMediaCapabilities": false
}"
What did you do?

Enabling a maximum Bandwidth via the abr config
abr: { enabled: true, restrictions: { maxBandwidth: 1400000 } }
What did you expect to happen?
Video player loading lower quality segments with a bandwidth not exceeding the configured limit
What actually happened?

For Chrome/Dash only low quality segments get loaded according to the configuration.

Unfortunately when playing on Safari/Hls the configured bandwidth limit seems to be ignored.

I see from your configuration that the streaming.useNativeHlsOnSafari configuration value is set to true. Because of that, Shaka Player will leave playing HLS content completely to the browser on Safari... and in that case, we can no longer apply bandwidth limits. You should try setting it to false instead; setting it to true is mostly useful for Fairplay support, I think.

When setting the value for streaming.useNativeHlsOnSafaristreaming.useNativeHlsOnSafari to false I'm receiving an error with code 4032 (CONTENT_UNSUPPORTED_BY_BROWSER).

setting it to true is mostly useful for Fairplay support, I think.

We probably will have to implement Fairplay which will not work if streaming.useNativeHlsOnSafaristreaming.useNativeHlsOnSafari is set to false,if I am not mistaken?

CONTENT_UNSUPPORTED_BY_BROWSER means that all of the streams within the manifest are unplayable... either because no streams meet the restrictions, or because we didn't get DRM keys for the streams. When you say that you got that error, was it with the assets you sent us, or a different one? I tried playing the manifest you provided in Safari, using MediaSource playback, and both of them seemed to work fine.
As for Fairplay... for a long time, the documentation on how to use Fairplay in MSE was very sparse. Because of that, at the moment, we have to leave Fairplay entirely to the browser.
Apple has improved their documentation, so we probably have enough information now to add actual Fairplay support, so that we can handle it in non-iOS Safari. But we haven't had time to get to that, yet.
See: https://github.com/google/shaka-player/issues/3346

When you say that you got that error, was it with the assets you sent us, or a different one?

Yes, I received the error with the provided assets, which are DRM free.

I see an .aac file, which we don't support yet (see #2615).  So you either need to get content with TS or MP4 audio, or play using native playback.

I see, thank you :)


Question: "fragment" elements

Let's say you make a component (numberDisplay) that renders a different Vnode depending on certain conditions.
patch(render(2)) /*
Your number is:
2

 */
patch(render(0)) /*
Your number is: 0
 */
patch(render(-2))

function render (n) {
  return h('div', {}, [
    'Your number is:',
    numberDisplay(n)
  ])
}

function numberDisplay (n) {
  if (n !== 0) {
    return h('div', {}, ['' + n])
  } else {
    return h('span', {}, ['0'])
  }
}

Is there a way I can attach a on.create or on.update handler on numberDisplay itself?
I would've done this, but I don't like the extra div:
function numberDisplay (n) {
  h('div', {on: {create: /*...*/, update: /*...*/}}, [
    (n !== 0)
    ? h('div', {}, ['' + n]),
    : h('span', {}, ['0'])
  ])
}

Maybe there's a way to make an "virtual" element of sorts that doesn't appear on the DOM (similar to DOM DocumentFragment).

Honest question: any reason why you wouldn't want to do something like the following?
function numberDisplay (n) {
  var o = {on: {create: /*...*/, update: /*...*/}};
  if (n !== 0) {
    return h('div', o, ['' + n])
  } else {
    return h('span', o, ['0'])
  }
}


Llama-2-7b-chat - RuntimeError: Inference tensors cannot be saved for backward

The model is: Llama-2-7b-chat (https://huggingface.co/meta-llama/Llama-2-7b-chat)
{'prompt': 'A patient diagnosed with carcinoma of {} presented with a serum calcium level of 16.4 mmol/L. What will be the first step in management?', 'subject': 'lung', 'target': 'IV fluids and furosemide', 'queries': []}
Executing ROME algorithm for the update: [A patient diagnosed with carcinoma of lung presented with a serum calcium level of 16.4 mmol/L. What will be the first step in management?] -> [IV fluids and furosemide]
Computing left vector (u)...
Selected u projection object lung
Left vector shape: torch.Size([11008])
Computing right vector (v)
Lookup index found: -37 | Sentence: A patient diagnosed with carcinoma of lung presented with a serum calcium level of 16.4 mmol/L. What will be the first step in management?IV fluids and furosemide | Token: lung
Rewrite layer is 5
Tying optimization objective to 31
Recording initial value of v*
Traceback (most recent call last):
File "/mnt/lustre/bo/medical_llm/evaluate_model_with_multiple_datasets.py", line 300, in
File "/mnt/lustre/bo/medical_llm/edit_util.py", line 50, in edit_model
model_new, _ = apply_rome_to_model(
File "/mnt/lustre/bo/medical_llm/FastEdit/fastedit/rome/rome_main.py", line 56, in apply_rome_to_model
deltas = execute_rome(model, tokenizer, request, hparams, batch_first)
File "/mnt/lustre/bo/medical_llm/FastEdit/fastedit/rome/rome_main.py", line 118, in execute_rome
right_vector: torch.Tensor = compute_v(
File "/mnt/lustre/bo/medical_llm/FastEdit/fastedit/rome/compute_v.py", line 97, in compute_v
logits = model(**input_tok).logits
File "/home/bo/anaconda3/envs/lora/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
return forward_call(*args, **kwargs)
File "/home/bo/anaconda3/envs/lora/lib/python3.9/site-packages/transformers/models/llama/modeling_llama.py", line 1038, in forward
outputs = self.model(
File "/home/bo/anaconda3/envs/lora/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
return forward_call(*args, **kwargs)
File "/home/bo/anaconda3/envs/lora/lib/python3.9/site-packages/transformers/models/llama/modeling_llama.py", line 925, in forward
layer_outputs = decoder_layer(
File "/home/bo/anaconda3/envs/lora/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
return forward_call(*args, **kwargs)
File "/home/bo/anaconda3/envs/lora/lib/python3.9/site-packages/transformers/models/llama/modeling_llama.py", line 632, in forward
hidden_states = self.input_layernorm(hidden_states)
File "/home/bo/anaconda3/envs/lora/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
return forward_call(*args, **kwargs)
File "/home/bo/anaconda3/envs/lora/lib/python3.9/site-packages/transformers/models/llama/modeling_llama.py", line 113, in forward
return self.weight * hidden_states.to(input_dtype)
RuntimeError: Inference tensors cannot be saved for backward. To work around you can make a clone to get a normal tensor and use it in autograd.

I think I hadn't used any @torch.inference_mode decorator in my code. What are your torch and transformers versions?

thanks for the hint! yea, I used the @torch.inference_mode decorator in my own function call to get the model and tokenizer. The code works fine after removing this.


add healthcheck configuration to service definition

This adds Health Check configuration.

My first go at go. So do let me know if missed a mark 🙈

Thanks @ibolmo merged to latest.  I'll wait a bit and then tag based on feedback :)


Improve android log

If I press log button and start react-native log-android
/bin/adb logcat *:S ReactNative:V ReactNativeJS:V
Log from console plugin now is displayed like that:
12-02 15:13:23.295  3622  3689 I ReactNativeJS: action %cSET_CONTAINER_ID %c@ 15:13:23.282
12-02 15:13:23.306  3622  3689 I ReactNativeJS: '%c prev state', 'color: #9E9E9E; font-weight: bold', { appReducer: { storeLoaded: true },
12-02 15:13:23.306  3622  3689 I ReactNativeJS:   icards:
12-02 15:13:23.306  3622  3689 I ReactNativeJS:    [ { identifier: '1001',

Is better to parse redux state log and display it the same like react-native-debugger
The advantage of react native console log is that not need 'Debug JS Remotely' to be started on device to display log.
I think we can parse and display redux state from Android log like that:

I've looking into the source code or RN debugger, and it's based on the chrome runtime and written in Node, so this might not be easy to integrate to a Java IDE like IDEA. But your suggestion does make sense, I'll trying to create a standalone log viewer app without using debug mode. And this might be a lot of time to implements it, so please wait.


Typing Error with Container

Describe the bug
Typing warning. Expected type 'Optional[IContainerLikeInterface]', got 'IUIContainerInterface' instead on container=self.get_container().
To Reproduce
Steps to reproduce the behaviour:

Create UIImage (or UITextbox) with container=self.get_container()

Platform and software (please complete the following information):

OS: Windows 10 64bit
Pygame GUI version: 0.5.7
Pygame version: 2.0.0.dev 10

Is there a bit more code context than what you posted above? I'm fairly sure you can stick images and text boxes inside panels and windows.
What exactly are you trying to do?

Sorry mate, here're two uses. Both of these throw a typing error on the container argument, as detailed above.
class TileInfo(UIPanel):
    def __init__(self, rect: pygame.Rect, manager: UIManager):
     ui_image = UIImage(relative_rect=image_rect, image_surface=image, manager=self.ui_manager, container=self.get_container())
    ui_text = UITextBox(html_text=text, relative_rect=rect, manager=self.ui_manager,
                              wrap_to_height=True, layer_starting_height=1,
                              container=self.get_container())

Can I give any more info on this that would help?

I believe you just need to change it to something like this:
class TileInfo(UIPanel):
    def __init__(self, rect: pygame.Rect, manager: UIManager):
        super().__init__(relative_rect=rect, starting_layer_height=1, manager=manager)

        ui_image = UIImage(relative_rect=image_rect,
                           image_surface=image,
                           manager=self.ui_manager,
                           container=self)
        ui_text = UITextBox(html_text=text, relative_rect=rect, manager=self.ui_manager,
                            wrap_to_height=True, layer_starting_height=1,
                            container=self)

If I understand your intent correctly. At some point the container interface was changed to be more natural so you don't need to call get_container() from objects that are already container-like such as panels and windows. Not sure if you had skipped the super().__init__() call in your posted code or not.

Spot on, thanks mate. All my assignments to container wereself.get_container() and amending to just self removed the typing error without any issues.


Cursor stuck out of window as of latest commit

Problem
After commit 0080eaeca3f3ed62d3a1b3d0f84b077dacf88053, whenever I enter a new terminal, my cursor gets stuck outside of the floating window.
Recreating
Just open any terminal window and try to enter something into the prompt.

I tried it before and it was working fine for me. Would you mind telling me the command that you are running?

After further investigation, it appears to only be a problem when editing Go files, so it might be vim-go. I'll close this issue because I don't think there's much you can do about it.


Feature selection & Regression model

@DamianAtlass thanks for the review. I still need to fix the documentation error, caused by the unregistered LARS package, when I will merge it...


Create a version using Playwright [Exercice 05 - Install Dependencies]

Once Playwright is an Open-Source tool and is from Microsoft, I think we could change the example using Playwright! I created this branch and ask you to consider the possibility. It could be a way to promote the tool throughout the Node.js course.
Link: Exercise - Install packages

LGTM


Use relative paths to luci.mk

If absolute path to luci.mk (i.e. $(TOPDIR)/feeds/luci/luci.mk) is specified and LuCI feed has a different name than "luci", errors like this one are raised:
Makefile:36: /openwrt/feeds/feedname/luci.mk: No such file or directory

This pull request contains fixes for three applications that use absolute paths in their Makefiles and replaces them with relative ones.

just seen I send this also as PR #614 ( and #615 for 15.05)


Sometimes gzip Content-Encoding header is given for query results

From @adamtheturtle on May 27, 2018 11:14
See assert_query_success and figure out why, then mock this reason.
Copied from original issue: adamtheturtle/vws-python#602

Right now we are seeing this is always the case so hard coded that and we will see!


[Joy] Autocomplete should dim the arrow icon when disabled

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Steps to reproduce 🕹
No response
Current behavior 😯

Expected behavior 🤔
No response
Context 🔦
No response
Your environment 🌎
No response

Good point. Thanks for reporting the issue.


Fix namespace matching

This fixes the bug where, for example, the namespace App\DomainService incorrectly gets matched using App\Domain
Resolves https://github.com/carlosas/phpat/issues/253

Hi. Thanks for the PR.
Can you create a test for this?
I'll have a look to the failing PHPCS-Fixer ASAP, it doesnt seem an error from the changes, probably related with an update

I added a test, but I don't know if this is the proper way to do this. There don't seem to be existing tests specifically targeting selectors. However, I verified that it gives an error with the old code, and a success after the modification, as it should.

it seems to work 👍 that test is enough, I will try to improve the system in the future.
however, there are two failing steps in the CI:

php-cs-fixer: it seems that now they catch FQCNs in the comments as well, and I want to test that FQCNs are catched. there seems to be a WIP way to ignore certain rules in some lines https://github.com/PHP-CS-Fixer/PHP-CS-Fixer/pull/7569
For now, can you try locking the php-cs-fixer version so the maximum is the previous one? otherwise just apply it on local using the last version and I will revert to using the FQCN again in the future.
phpunit on php 7 here: it seems "Namespace" is a reserved token word even inside a use statement on php 7 (they fixed it on php 8), can you rename the fixture namespace to something else? I will drop support for php 7 soon so I can rollback this workaround as well in the future.

It looks all OK now


integration none adobe MarTechs without impacting performance (consents managers, analytics etc.)

@eKrausedivae please write down in this issue your lessons learned in the conti project

https://github.com/diva-e/conti-home-landing-page/pull/196


Add ability to split enso translations and own translations

Use case:
I added own translation keys via frontend which are stored in assests/lang/xx.json. In the same file there are the enso translations too.
If you deploy a new version with new translations I have to merge those files.
It would be better if it would be possible to split translations into groups which are stored in different files.
assests/lang/enso/xx.json
assests/lang/mauthi/xx.json
...

Yes, this is indeed a problem. But I think that the __ method expects a json in the assests/lang/ root, named "$locale.json".
What we could do here is an artisan command that will merge the lang json when needed.

would be a good idea

are there any news? I left the translation topic out in the last month, but now I would need a solution

And how is the process for new translations here - for example the footer line is not translated but in the localisation menu everything looks good:

I'm interested in the process how to get actual with this.

What do you mean by

but in the localisation menu everything looks good

The problem is that not all the keys that are used in the app are also present in the localisation.
It would be a great help if you would just search for __(" and i18n(" and add the missing keys to any of the language (german). And then commit the changes in laravel-enso/localisation. You should do this from the interface, so all the languages will get the update. (keys without values).

New keys are added to each language and default translation is the english value (for application wide keys for enso)

The keys are in English, so if the translation in missing the label will be already displayed in English.

Developer has the possibility to add new keys for his application if needed
During build process both, the enso translations and the custom translations get merged

I have plans for this, in fact is one of the last few things to address, but I need to find the time for this.
In fact, we need to first think this through, to find the best approach.

It would be a great help if you would just search for __(" and i18n(" and add the missing keys to any of the language (german).
I think there are too many keys missing - therefore I created a pull request for a new "add key" route.
To use this I think off something like this in __ in the locale.js:

       if (state.i18n[lang] && state.i18n[lang][key] != undefined) {
            //console.log("existing key: " + lang + " - " + key + " - " + (state.i18n[lang][key] || key));
            return (state.i18n[lang][key] || key);
        } else {
            if (true) { // check if we are in local env or insert a new config for localisation debug mode
                //console.log("create key: "+lang+" - "+key);
                axios.post("/api/system/localisation/addLangKey", { langKey: key }).then((response) => {
                    // xxx
                }).catch((error) => {
                    // xxx
                });
            }
            return key;
        }

Purpose:

Check if key exists - if not add it to all languages

Explaination / missing things:

instead of if (true) we should add something like if (env == local) or if (config.languageDebugMode == true) but I don't know how to do this

What do you think about this? If not needed I will add it to my repo and add the missing keys.

I have plans for this, in fact is one of the last few things to address, but I need to find the time for this.

I think the easiest solution would be:

add 2 language files for each language (one master of enso, one local)
if new keys are added add them to local file
if keys are defined twice local is the "master" and overrides the enso key
if new enso keys are added file is published

what do you think about this?

I think that adding the auto-add-missing-keys is a really clever idea and I like it a lot. And indeed, it should work only in dev mode. We already have this flag in the front end, maybe you noticed by now the orange indicator ;)

The flag in in the vuex store under the meta object.
meta.env === 'local'
If would be great if we could figure out a mechanism to sanitize the lang files against wrong keys. Often I find myself renaming the labels, and in this case we would have leftovers (we already have some). It's not a must to have this safety mechanism, but it would be better if we did.
Regarding the second part, the __ helper that we use on the server side is Laravel's native implementation for jsons, and last time I checked it could only work with one file per locale. Did something got updated in this area?

I will check this.
First time you said that something from me is a really clever idea - I got red in face :)

ROTFL, what can I say, seems like something to improve on my side :)

I think that adding the auto-add-missing-keys is a really clever idea and I like it a lot. And indeed, it should work only in dev mode. We already have this flag in the front end, maybe you noticed by now the orange indicator ;)

added the check for env === 'local' and created a PR for locale.js in core repo.
if ok can you please merge the two PR and open all default pages in your local env to get the new keys. Then please commit the new files to localisation package and ask the translators to update them.
(I have not checked out an "empty" enso package, otherwise I could do this - if I start this with my version you get my keys too)

If would be great if we could figure out a mechanism to sanitize the lang files against wrong keys. Often I find myself renaming the labels, and in this case we would have leftovers (we already have some). It's not a must to have this safety mechanism, but it would be better if we did.

I don't have any idea how to achieve this because you never know which translations are used (because not all keys are used on one page). I think the only way to do this is a manual cleanup :(

Regarding the second part, the __ helper that we use on the server side is Laravel's native implementation for jsons, and last time I checked it could only work with one file per locale. Did something got updated in this area?

Maybe this can help us (did not read the article<EMAIL_ADDRESS>Other solution:

Create 2 files lang/enso/de.json and lang/app/de.json
After changing keys in frontend merge both files and create the lang/de.json
After composer update to the same

What do you think?

I think it could work out.

Having 3 lang files for each language like you proposed lang/enso/xx.json, lang/app/xx.json and one mergedlang/xx.json`
Adding a flag to the .env / config where we can specify if we develop an enso (core) package or a project / app.
At every change from the UI the appropriate /enso.xx.json || /app/xx.json will be updated considering the above flag, and also the merged file.
Having a temporary artisan command that can merge the files manually and find differences.

Adding a flag to the .env / config where we can specify if we develop an enso (core) package or a project / app.

For me it's not clear why we need this flag?
Rest is clear - if I have time I will start with this in the next days.

What do you think about this?
https://www.npmjs.com/package/merge-jsons-webpack-plugin (than we can watch the folder and build it automatically?)

For me it's not clear why we need this flag?

because

At every change from the UI the appropriate /enso/xx.json || /app/xx.json will be updated considering the above flag, and also the merged file.

If we develop a new package for Enso, all the new lang keys should be added to lang/enso/de.json. But if you develop your personal project, you will want the new lang keys added to lang/app/de.json.

ok

Just submitted a new Commit to PR.

Having 3 lang files for each language like you proposed lang/enso/xx.json,lang/app/xx.jsonand one mergedlang/xx.json`

Done!

Adding a flag to the .env / config where we can specify if we develop an enso (core) package or a project / app.

Done!

At every change from the UI the appropriate /enso.xx.json || /app/xx.json will be updated considering the above flag, and also the merged file.

For adding new keys: Done (new key gets added to the right file based on flag)
Missing: Updating existing keys. If I use the flag above all keys are added to the file. e.g. if we update app translations the core keys get added to app keys (because all keys are submitted)
Is this OK?
Other solution:

If flag says core = true then only load and update core translations from enso folder
If flag says core = false then check if key is changed, if yes add it to translation file in app folder

What do you think?

Having a temporary artisan command that can merge the files manually and find differences.
Done

php artisan localisation:sync (all languages)
php artisan localisation:sync --locale=de (only one language)

Can you please review my PR - infos and tips are welcome!

Looks good at the first sight. I will review it in detail soon.

can you  maybe answer my question according to update soon - because then I can finish this part in meantime and you can review alltogether

@mauthi sorry it was a very busy day for me, sorry for the late response.

Missing: Updating existing keys. If I use the flag above all keys are added to the file. e.g. if we update app translations the core keys get added to app keys (because all keys are submitted)
Is this OK?
Other solution:
If flag says core = true then only load and update core translations from enso folder
If flag says core = false then check if key is changed, if yes add it to translation file in app folder
What do you think?

I was thinking at this, and I believe that maybe we don't want this feature to be always "on". So we can have a flag in .env and in config/enso/config.php, something like collectMissingKeys and the allowed values should be off, core, app. After we develop (meanwhile maybe we change 30 times some of the new labels), when we consider the new feature done, we can turn this flag to core/app and navigate through the pages, and collect all the labels. After that, just turn it off.
What do you think?
@gandesc what's your take on this?

We definitely don't want the collectMissingKeys flag always on while developing, as it's very likely we'll end up with unused keys. Also, unless I'm missing anything, we could have this flag just in the front end, there's no need for it in the backend(env) just to move it around.

We definitely don't want the collectMissingKeys flag always on while developing, as it's very likely we'll end up with unused keys. Also, unless I'm missing anything, we could have this flag just in the front end, there's no need for it in the backend(env) just to pass it around (we could put a switch in the settings side-bar, visible only on dev)

ninja, stick with one profile!
I like the idea with a switch on the settings bar.

I think we should add 2 flags:

core: if true, add keys to core, if false to app
collectMissingKeys

And we need it in BE to decide to which file we should add the missing keys

core in BE, collect Missing in FE

perfect

Just created a new PR #25
Done:

added switch to FE

Missing:

add switch to config sidebar (@aocneanu can you do this?)
test "add language"
test full feature

Looking forward to your review.

I did some refactor but it still needs a lot of work and tests - @y0net.. at least it seems stable.
I added the missing logic for creating and deleting language from the interface.
I'm putting now v2.5.0. We should really test all the scenarios...

Thx - will take a look on PR to learn from your refactoring.
Will test the scenarios today if this will help you?
Possible test scenarios:

Add lang

Delete lang

Update lang (change shortcode)

Update lang file in package and publish changes

Add translation key (core = true and false)

Remove translation key (core = true and false)

Change translation key (core = true and false)

Test collectMissingKeys on/off (frontend)

I really don't like the quality of the refactor, so maybe we can improve it.
About testing, would be perfect. We can open a new ticket for testing and write the feedback there.


IFU-master-2021-05-27

The conflicts in the following files have been resolved:
op_builder/transformer.py
op_builder/init.py
IFU-master-2021-05-27.zip
cc: @jithunnair-amd

@rraminen The 2 conflicting files have been correctly resolved. However, for DeepSpeedExamples, I see "Submodule DeepSpeedExamples updated from 9524d9 to 177d53". Where is that 177d53 SHA coming from?


It's possible to locate .moor files in other directory

Hi,
I've a question. It's possible to locate the .moor files in another directory without database.dart?
Example:
@UseMoor(
    tables: [TABLE1],
    daos: [DAO],
    include: {'../module/feature/example2/data/example2.moor'})

Yes. As long as the file is reachable from the build (this usually means being in the same package), it should work. If you need to include a moor file from another package, you can use the package import from Dart: include: {'package:foo/bar.moor'}.
Please let me know if you run into problems!


Treat EPIPE as an expected error.

If the other end of a TCP connection closes its read end of the socket, you get an EPIPE when you try to send. I saw that happen in the CI once:
https://neon-github-public-dev.s3.amazonaws.com/reports/pr-4136/release/4869464644/index.html#suites/c19bc2126511ef8cb145cca25c438215/7ec87b016c0b4b50/
2023-05-03T07:53:22.394152Z ERROR Task 'serving compute connection task' tenant_id: Some(c204447079e02e7ba8f593cb8bc57e76), timeline_id: Some(b666f26600e6deaa9f43e1aeee5bacb7) exited with error: Postgres connection error

Caused by:
    Broken pipe (os error 32)

Stack backtrace:
   0: pageserver::page_service::page_service_conn_main::{{closure}}
             at /__w/neon/neon/pageserver/src/page_service.rs:282:17
      <core::panic::unwind_safe::AssertUnwindSafe<F> as core::future::future::Future>::poll
             at /rustc/9eb3afe9ebe9c7d2b84b71002d44f4a0edac95e0/library/core/src/panic/unwind_safe.rs:296:9
      <futures_util::future::future::catch_unwind::CatchUnwind<Fut> as core::future::future::Future>::poll::{{closure}}
             at /__w/neon/neon/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-util-0.3.28/src/future/future/catch_unwind.rs:36:42
      <core::panic::unwind_safe::AssertUnwindSafe<F> as core::ops::function::FnOnce<()>>::call_once
             at /rustc/9eb3afe9ebe9c7d2b84b71002d44f4a0edac95e0/library/core/src/panic/unwind_safe.rs:271:9
   ...

In the passing, add a comment to explain what the "expected" in the is_expected_io_error function means.

In the passing, add a comment to explain

don't see it, probably it got lost or not added yet

Forgot to "git add" it :facepalm:. Added now


How can I add a column to table dynamically?

I am updating the column object in settings object after loading page but the new column is not updating in table. Is there any way to do it?

Sorry I found it here https://github.com/akveo/ng2-smart-table/issues/483


Split large pages

Fixes #2060

looks good

Oh ya, you should add a test that gets regions from an empty page.

looks good

This is merged.


Message formatting not supported

The Slack API seems to support mrkdwn and mrkdwn_in as options as stated here: https://api.slack.com/docs/formatting
Would be great if those options were supported. (Unless I'm missing something here)

I was missing something... After longer investigation I got it to work. My issue was that my text was in an attachment so mrkdwn=true wouldn't work.
If someone else has the same issue here is my code:
slack.send({
	'text': 'some text',
	'attachments': [{
		'fallback': 'Details',
		'pretext': 'Details',
		'color': '#0074C4',
		'mrkdwn_in': [
			'text',
			'pretext',
			'fields',
		],
		'fields': [
			{
				'title': 'more text',
				'value': 'lots of *markdown* _here_ and `there`',
				'short': false,
			},
			{
				'title': 'text',
				'value': 'text',
				'short': false,
			}
		],
	}],
	'channel': channel,
	'username': username,
	'icon_url': App.SLACKICON,
});


Make QUE use untrusted data explicitly

Previously, QUE relied on getting large batches of data at a time to compute statistics on untrusted data. That was a deliberate design decision at one point before we had the current task structure, but I now think it's pretty bad. We should make all detectors that want untrusted data explicitly require untrusted data during training.
To support that, I had to make it possible for a statistical detector to use both trusted and untrusted data. This added some complexity, maybe there's a good way to redesign it, but I'm ok with this version for now (at some point, we'll likely want to refactor statistical detectors quite a bit anyway, see #42 ).
Ideally, we'd somehow enforce that detectors treat the batch dimension as an actual batch dimension, but the only way I see would be to have them implement elementwise anomaly scores, which we'd then need to compile to make it efficient. So I think we should just keep that in mind manually.

I checked that the tests still run (with some minor changes) and that Mahalanobis still gives the same result on one task.

Closing in favor of #53 (which includes these changes but fixes conflicts and should be merged soon). I checked QUE performance on MNIST corner pixel backdoors there and it seems fine, about as good as Mahalanobis (though I didn't directly compare against older numbers)


IGV session layout

UCMU ratio's plotting:  events with ratio = 0 are not displayed properly.
This is probably a problem with IGV + window size, but might be solved using 'height' in the different tracks.

Fixed


Build system fail to catch the error sometime

Here is an example:
https://github.com/apache/incubator-nuttx/pull/1693/checks?check_run_id=1085270278
You can see that there are some compiler errors in arch/sim/src/sim/up_tapdev.c, but the precheck consider build pass the test.
Now, the typo error is merged into the mainline. The strange thing happen, some build consider it fail:
https://github.com/apache/incubator-nuttx-apps/pull/379/checks?check_run_id=1094370101
but some build consider it pass:
https://github.com/apache/incubator-nuttx/pull/1742/checks?check_run_id=1094753731
@btashton and @liuguo09

Hmm also strange because you can see the build on master that passed for this. I'm not sure how this PR would have passed both prior to merge and and then also on the build on master branch triggered by the merge. All the builds keep an artifact that is the source repos used for the build so I can take a look in the morning.

@btashton  I'm not very sure. But it seems it's caused by ccache enabled in incubator-nuttx, while incubator-nuttx-apps doesn't enable ccache now,  it works rightly.

Cache key is specific to the run so it's not that. Also with the new cache v2 I have noticed the source bundle is usually not there so it grabs it from the artifact instead. Something else funny is going on.

Ahhh ccache not cache. You might be right. I wonder why ccache is getting the false hits.

I pulled the source bundle that it used and it failed to build as expected.  That really leaves ccache as the only option but I could not reproduce it by clearing my cache and using an earlier build and then building the bad build.  I do notice that we have direct mode enabled which we should not but the hash of up_tapdev.c must have changed so I don't see how this could have been missed.


Document testing runtime upgrades

try-runtime
fork off substrate + local test

https://github.com/threefoldtech/tfchain/blob/development/docs/production/upgrade_process.md


Support replicasets - support running mongo scripts - attempt to clean-up orphan containers

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

39 of 202 (19.31%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-9.4%) to 35.948%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

signal_handler.go
15
21
71.43%

container_cache.go
3
17
17.65%

mongotest.go
21
164
12.8%

Totals

Change from base Build<PHONE_NUMBER>:
-9.4%

Covered Lines:
220

Relevant Lines:
612

💛  - Coveralls


CIV-3459 Cover Proceed Heritage and order made api

Before creating a pull request make sure that:

[x] commit messages are meaningful and follow good commit message guidelines
[x] README and other documentation has been updated / added (if needed)
[x] tests have been updated / new tests has been added (if needed)

Please remove this line and everything above and fill the following sections:
JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/CIV-3459
Change description
1V1 and 1V2
Judge Make the decision and order made ->Order made
Judge Make the decision and accept Strike out Defence Application -> Proceeds in Heritage
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ ] No

[ ] Refactor Judge_Makes_Decision to Make_Decision


It's looking for whisper 0.3.0?

 pip install -r requirements.txt
Collecting keyboard==0.13.5 (from -r requirements.txt (line 1))
  Using cached keyboard-0.13.5-py3-none-any.whl.metadata (4.0 kB)
Collecting openai==0.27.0 (from -r requirements.txt (line 2))
  Using cached openai-0.27.0-py3-none-any.whl.metadata (13 kB)
Collecting pyaudio==0.2.11 (from -r requirements.txt (line 3))
  Using cached PyAudio-0.2.11.tar.gz (37 kB)
  Preparing metadata (setup.py) ... done
Collecting pyttsx3==2.90 (from -r requirements.txt (line 4))
  Using cached pyttsx3-2.90-py3-none-any.whl.metadata (3.6 kB)
Collecting tk==0.1.0 (from -r requirements.txt (line 5))
  Using cached tk-0.1.0-py3-none-any.whl.metadata (693 bytes)
ERROR: Could not find a version that satisfies the requirement whisper==0.3.0 (from versions: 0.9.5, 0.9.6, 0.9.7, 0.9.8, 0.9.9, 0.9.10, 0.9.11, 0.9.12, 0.9.13, 0.9.14, 0.9.15, 0.9.16, 1.0.0, 1.0.1, 1.0.2, 1.1.0, 1.1.1, 1.1.2, 1.1.3, 1.1.4, 1.1.5, 1.1.6, 1.1.7, 1.1.8, 1.1.9, 1.1.10)
ERROR: No matching distribution found for whisper==0.3.0

You could try updating the requirements.txt file to this:
keyboard==0.13.5
openai==0.27.0
pyaudio==0.2.11
pyttsx3==2.90
tk==0.1.0
whisper==v20231117


[6.0.2] reduxForm.js:340 Uncaught TypeError: name.replace is not a function

Hi,
I've been using redux-form on my project for building some fairly large forms (100+ fields). Everything has been working well so far, but I've been running into type errors with the async validation:

reduxForm.js:340 Uncaught TypeError: name.replace is not a function

My current test function looks like this:
const asyncValidate = (values, props) => {
return sleep(100) // simulate server latency
    .then(() =>
    {
        if(_.get(values, part7.field1, -1) <= 0 ){

            throw {
                'part7.field1': 'Error: field value too small, must be at least 1'
            };
        }
     }

...
)}  export default asyncValidate
Line 340 (actually 294) in redux-form. js looks like this:
var isBlurredField = !submitting && (!asyncBlurFields || ~asyncBlurFields.indexOf(name.replace(/\[[0-9]+\]/g, '[]')));
Any help would be appreciated.

Hi @Lumiahma, do you still have this problem? If you don't, what was the resolution?
I'm curious because I know async validation used to have a few problems back in the first releases of the 6.x.x versions.


Bodygroups not updating when changing cosmetics on Linux.

When adding cosmetics,the bodygroups don't change. A good example is the chest, it's meant to remove the vest but doesn't and adds the new one anyways. You can see this in the image below.

This might have something to do with me using Linux, but I'm not sure. I'm using Manjaro if you wanted to know what distro I'm using.

This along with issues with respawn particles are being addressed, no ETA and no real updates to provide as of now. I highly suggest using Proton for now since its pretty much fine from my experience.
Leaving this open for now.

Closed as we no longer support linux - reopen if you can reproduce this on proton.


docs(demo): add example of ngx-datatable integration

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
add docs with example of datatable integration
ngx-datatable
issue: custom type with ngx-datatable #1061
Please check if the PR fulfills these requirements

[ ] The commit messages follow our guidelines: https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit-message-format
[ ] A unit test has been written for this change.
[ ] Running npm run build produced a successful build. (Unit testing can be done by running npm test;)
[ ] My code has been linted. (npm run lint to do this. npm run build will fail if there are files not linted.)

Please provide a screenshot of this feature before and after your code changes, if applicable.

Other information:
@aitboudad  I added the example.

Thank you @enricooliva!


Using Insteon PLM does not register an integration.

Home Assistant release with the issue:

Version 0.97.2
Last working Home Assistant release (if known):
Operating environment (Hass.io/Docker/Windows/etc.):

Linux Debian Buster
pip installed homeassistant
Component/platform:

https://www.home-assistant.io/components/insteon/
Description of problem:
Insteon serial PLM is set in configuration.yaml
Insteon:
port: /dev/ttyUSB0
Homeassistant finds PLM and all switches and lights function.
Insteon is not found under Configuration->Integrations
Seems to be no way to associate an Insteon light or switch with an AREA without finding it under integrations.
Interestingly all Insteon .storage/core.entity_registry devices have a config_entity_id: of null.  Not sure if this is related.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
# Configure a default setup of Home Assistant (frontend, api, etc)
default_config:

# Uncomment this if you are using SSL/TLS, running in Docker container, etc.
# http:
#   base_url: example.duckdns.org:8123

# Text to speech
tts:
  - platform: google_translate

group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml

insteon:
  port: /dev/ttyUSB0

Traceback (if applicable):

Additional information:

Why should Home Assistant register Insteon as an integration? I cannot find any evidence in the Insteon Component Documentation for that claim. Please explain if I am missing something :)

Well I may very well be missing something as well.  I thought all components were now known as Integrations.  I have three other Integrations in addition to Insteon:
Hue
Zwave
ESPHome
If I go to Configuration->Integrations I can select any of the Integrations and view the devices, such as a light, and set an AREA.  Without Insteon showing up as an integration and listing it's devices I don't see a way to set that.  I may be mistaken that all components register as an Integration.
If they don't then how does one go about selecting and setting an AREA?

You are correct that Home Assistant is currently in the transition from components to only integrations.
However, not every component/integration can be accessed or configured via Configuration -> Integrations e.g. the Insteon integration cannot.
Plus the docs usually describe how to set up such an integration e.g. AdGuard Home Docs.
Setting an area is exclusive for such Integrations, which means that you cannot set an area for your Insteon devices, at least for now. It is still a work in progress.
Ideally you would only have to use the UI and then go to Configuration -> Integrations to set up, access and configure all of your integrations and their devices without ever touching any YAML files. That is the vision for the future as far as I know.

Awesome thanks for the response.  I suppose this is good as part of a task list of things to be done for Insteon.  A sort of reminder if you will.
I do hope HA will always be able to be run by manual config of YAML files, it's really nice to have comments in the file and right now I see that using the UI strips all comments out, which I don't care for.
Once again thanks.


Set real mapk value.

In the old version mapk value was incorrect.

Associated with updated apk().
@xenx I don't see much importance in fixing it (one would rerun the notebook anyway), but okay.


Building dictionaries fails

Describe the bug
When running npm run build or npm run dev, the last build task (dictionaries) fails. When running npm run dev it is blocking, but not when running npm run build.
To Reproduce
Steps to reproduce the behavior:

npm run dev
See error:

kytwbs-MacBook-Pro:ferdi kytwb$ npm run dev

><EMAIL_ADDRESS>dev /Users/kytwb/Downloads/Side Projects/ferdi
> cross-env NODE_ENV=development gulp dev

[11:36:24] Requiring external module @babel/register
[11:36:24] Using gulpfile ~/Downloads/Side Projects/ferdi/gulpfile.babel.js
[11:36:24] Starting 'dev'...
[11:36:24] Starting 'clean'...
[11:36:26] Finished 'clean' after 1.71 s
[11:36:26] Starting 'mvSrc'...
[11:36:26] Starting 'mvPackageJson'...
[11:36:26] Starting 'mvLernaPackages'...
[11:36:26] Finished 'mvPackageJson' after 157 ms
[11:36:27] Finished 'mvLernaPackages' after 604 ms
[11:36:27] Finished 'mvSrc' after 612 ms
[11:36:27] Starting 'html'...
[11:36:27] Starting 'scripts'...
[11:36:27] Starting 'styles'...
[11:36:27] Finished 'html' after 485 ms
[11:36:28] Finished 'styles' after 1.15 s
[11:36:33] Finished 'scripts' after 5.9 s
[11:36:33] Starting 'dictionaries'...
executing npm install --prefix /Users/kytwb/Downloads/Side Projects/ferdi/temp  hunspell-dict-bg-bg hunspell-dict-ca-es hunspell-dict-cs-cz hunspell-dict-da-dk hunspell-dict-de-de hunspell-dict-el-gr hunspell-dict-en-gb hunspell-dict-en-us hunspell-dict-es-es hunspell-dict-et-ee hunspell-dict-fa-ir hunspell-dict-fo-fo hunspell-dict-fr-fr hunspell-dict-he-il hunspell-dict-hr-hr hunspell-dict-hu-hu hunspell-dict-it-it hunspell-dict-ko hunspell-dict-lt-lt hunspell-dict-lv-lv hunspell-dict-nb-no hunspell-dict-nl-nl hunspell-dict-pl-pl hunspell-dict-pt-br hunspell-dict-pt-pt hunspell-dict-ro-ro hunspell-dict-ru-ru hunspell-dict-sk-sk hunspell-dict-sl-si hunspell-dict-sr hunspell-dict-sv-se hunspell-dict-ta-in hunspell-dict-tg-tg hunspell-dict-tr hunspell-dict-uk-ua hunspell-dict-vi
exec error: Error: Command failed: npm install --prefix /Users/kytwb/Downloads/Side Projects/ferdi/temp  hunspell-dict-bg-bg hunspell-dict-ca-es hunspell-dict-cs-cz hunspell-dict-da-dk hunspell-dict-de-de hunspell-dict-el-gr hunspell-dict-en-gb hunspell-dict-en-us hunspell-dict-es-es hunspell-dict-et-ee hunspell-dict-fa-ir hunspell-dict-fo-fo hunspell-dict-fr-fr hunspell-dict-he-il hunspell-dict-hr-hr hunspell-dict-hu-hu hunspell-dict-it-it hunspell-dict-ko hunspell-dict-lt-lt hunspell-dict-lv-lv hunspell-dict-nb-no hunspell-dict-nl-nl hunspell-dict-pl-pl hunspell-dict-pt-br hunspell-dict-pt-pt hunspell-dict-ro-ro hunspell-dict-ru-ru hunspell-dict-sk-sk hunspell-dict-sl-si hunspell-dict-sr hunspell-dict-sv-se hunspell-dict-ta-in hunspell-dict-tg-tg hunspell-dict-tr hunspell-dict-uk-ua hunspell-dict-vi
npm ERR! code ENOLOCAL
npm ERR! Could not install from "Projects/ferdi/temp" as it does not contain a package.json file.

npm ERR!      /Users/kytwb/.npm/_logs/2019-09-24T04_36_35_498Z-debug.log

[11:36:35] The following tasks did not complete: dev, <series>, dictionaries
[11:36:35] Did you forget to signal async completion?

In Travis, stderr is a bit different as it seems to be complaining about the missing package.json but still manage to install the hunspell modules: https://travis-ci.org/getferdi/ferdi/jobs/588587113#L456
All good in AppVeyor: https://ci.appveyor.com/project/kytwb/ferdi#L341

Hmm, when running npm run dev on my computer it also complains about no package.json but it does just continue
$ npm run dev

><EMAIL_ADDRESS>dev /Users/vantezzen/Projects/ferdi
> cross-env NODE_ENV=development gulp dev

[09:09:28] Requiring external module @babel/register
[09:09:35] Using gulpfile ~/Projects/ferdi/gulpfile.babel.js
[09:09:35] Starting 'dev'...
[09:09:35] Starting 'clean'...
[09:09:35] Finished 'clean' after 525 ms
[09:09:35] Starting 'mvSrc'...
[09:09:35] Starting 'mvPackageJson'...
[09:09:35] Starting 'mvLernaPackages'...
[09:09:36] Finished 'mvPackageJson' after 257 ms
[09:09:37] Finished 'mvSrc' after 1.29 s
[09:09:37] Finished 'mvLernaPackages' after 1.32 s
[09:09:37] Starting 'html'...
[09:09:37] Starting 'scripts'...
[09:09:37] Starting 'styles'...
[09:09:39] Finished 'html' after 2.25 s
[09:09:43] Finished 'styles' after 5.96 s
[09:09:47] Finished 'scripts' after 11 s
[09:09:47] Starting 'dictionaries'...
executing npm install --prefix /Users/bennetthollstein/LokaleProjekte/ferdi/temp  hunspell-dict-bg-bg hunspell-dict-ca-es hunspell-dict-cs-cz hunspell-dict-da-dk hunspell-dict-de-de hunspell-dict-el-gr hunspell-dict-en-gb hunspell-dict-en-us hunspell-dict-es-es hunspell-dict-et-ee hunspell-dict-fa-ir hunspell-dict-fo-fo hunspell-dict-fr-fr hunspell-dict-he-il hunspell-dict-hr-hr hunspell-dict-hu-hu hunspell-dict-it-it hunspell-dict-ko hunspell-dict-lt-lt hunspell-dict-lv-lv hunspell-dict-nb-no hunspell-dict-nl-nl hunspell-dict-pl-pl hunspell-dict-pt-br hunspell-dict-pt-pt hunspell-dict-ro-ro hunspell-dict-ru-ru hunspell-dict-sk-sk hunspell-dict-sl-si hunspell-dict-sr hunspell-dict-sv-se hunspell-dict-ta-in hunspell-dict-tg-tg hunspell-dict-tr hunspell-dict-uk-ua hunspell-dict-vi
stdout: +<EMAIL_ADDRESS>+<EMAIL_ADDRESS>[...]
added 36 packages from 1 contributor and audited 36 packages in 4.197s
found 0 vulnerabilities

stderr: npm WARN saveError ENOENT: no such file or directory, open '/Users/vantezzen/Projects/ferdi/temp/package.json'
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN enoent ENOENT: no such file or directory, open '/Users/vantezzen/Projects/ferdi/temp/package.json'
npm WARN temp No description
npm WARN temp No repository field.
npm WARN temp No README data
npm WARN temp No license field.

[09:09:57] Finished 'dictionaries' after 9.73 s

Which versions of node and npm are you on? In my case:
$ node -v
v10.16.3
$ npm -v
6.9.0

Hmm, when running npm run dev on my computer it also complains about no package.json but it does just continue
$ npm run dev

><EMAIL_ADDRESS>dev /Users/vantezzen/Projects/ferdi
> cross-env NODE_ENV=development gulp dev

[09:09:28] Requiring external module @babel/register
[09:09:35] Using gulpfile ~/Projects/ferdi/gulpfile.babel.js
[09:09:35] Starting 'dev'...
[09:09:35] Starting 'clean'...
[09:09:35] Finished 'clean' after 525 ms
[09:09:35] Starting 'mvSrc'...
[09:09:35] Starting 'mvPackageJson'...
[09:09:35] Starting 'mvLernaPackages'...
[09:09:36] Finished 'mvPackageJson' after 257 ms
[09:09:37] Finished 'mvSrc' after 1.29 s
[09:09:37] Finished 'mvLernaPackages' after 1.32 s
[09:09:37] Starting 'html'...
[09:09:37] Starting 'scripts'...
[09:09:37] Starting 'styles'...
[09:09:39] Finished 'html' after 2.25 s
[09:09:43] Finished 'styles' after 5.96 s
[09:09:47] Finished 'scripts' after 11 s
[09:09:47] Starting 'dictionaries'...
executing npm install --prefix /Users/vantezzen/Projects/ferdi/temp  hunspell-dict-bg-bg hunspell-dict-ca-es hunspell-dict-cs-cz hunspell-dict-da-dk hunspell-dict-de-de hunspell-dict-el-gr hunspell-dict-en-gb hunspell-dict-en-us hunspell-dict-es-es hunspell-dict-et-ee hunspell-dict-fa-ir hunspell-dict-fo-fo hunspell-dict-fr-fr hunspell-dict-he-il hunspell-dict-hr-hr hunspell-dict-hu-hu hunspell-dict-it-it hunspell-dict-ko hunspell-dict-lt-lt hunspell-dict-lv-lv hunspell-dict-nb-no hunspell-dict-nl-nl hunspell-dict-pl-pl hunspell-dict-pt-br hunspell-dict-pt-pt hunspell-dict-ro-ro hunspell-dict-ru-ru hunspell-dict-sk-sk hunspell-dict-sl-si hunspell-dict-sr hunspell-dict-sv-se hunspell-dict-ta-in hunspell-dict-tg-tg hunspell-dict-tr hunspell-dict-uk-ua hunspell-dict-vi
stdout: +<EMAIL_ADDRESS>+<EMAIL_ADDRESS>[...]
added 36 packages from 1 contributor and audited 36 packages in 4.197s
found 0 vulnerabilities

stderr: npm WARN saveError ENOENT: no such file or directory, open '/Users/vantezzen/Projects/ferdi/temp/package.json'
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN enoent ENOENT: no such file or directory, open '/Users/vantezzen/Projects/ferdi/temp/package.json'
npm WARN temp No description
npm WARN temp No repository field.
npm WARN temp No README data
npm WARN temp No license field.

[09:09:57] Finished 'dictionaries' after 9.73 s

Which versions of node and npm are you on? In my case:
$ node -v
v10.16.3
$ npm -v
6.9.0

Got it after reading a bit more carefully:

Could not install from "Projects/ferdi/temp"

My project is in a "Side Projects" directory containing a space.
Fixed via https://github.com/getferdi/ferdi/commit/52d2899bfd40a8383fe1f3592ef2f5b43e0bde8d.


docs - cuprite configuration

For anyone googling for magic_test and cuprite, here's how I configured headless: in the Cuprite::Driver:
# test/support/system/cuprite_setup.rb
require "capybara/cuprite"

Capybara.register_driver(:cuprite) do |app|
  Capybara::Cuprite::Driver.new(
    app,
    **{
      window_size: [1200, 800],
      # See additional options for Dockerized environment in the respective section of this article
      browser_options: {},
      # Increase Chrome startup wait time (required for stable CI builds)
      process_timeout: 10,
      # Enable debugging capabilities
      inspector: true,
      # Allow running Chrome in a headful mode by setting HEADLESS env
      # var to a falsey value
      headless: !ENV["HEADLESS"].in?(%w[n 0 no false]) && !ENV["MAGIC_TEST"].in?(%w[y 1 yes true])
    }
  )
end
...

This issue can be closed; just wanted to share it somewhere :)

Thanks, @drnic! Added this as the first page in the Wiki!

Cool. If I'm wrong/or if I change my mind, I'll update that page 👍


Several improvements

Only at first glance, bootload_reboot_stub.bin appears to be a binary file, and I'm not the biggest fan of checking in those. Is it necessary?


Profile Page

The profile page of the customer should allow a customer to perform CRUD actions on their-

personal information
resumés

This is a duplicate issue of issue #13. So, closing this issue.

User can visit their profile page to see their details.


Very large bundle size

According to Bundlephobia, the bundled package size is quite large (10kb gzipped!)
If only the required APIs from crypto are included, the bundle size reduces to a much more reasonable 1-2kb gzipped. It would be great if the crypto require could be tree-shaken!

@smithki PRs are welcome! This module is not very actively maintained otherwise, though.

Well, it'd be great if the published package didn't include the test folder and  dist/object_hash_test.js and other developer flow related files like gulpfile, karma, bower, travis, etc...

#92 handles removing the extra clutter. @smithki's concern could also be solved but it would require that the browser bundle is transpiled using something else than deprecated gulp-browserify that doesn't support the destructuring syntax that would (maybe?) make it tree-shaken?

I’m a big proponent of microbundle. If the project maintainers are not opposed to replacing the build system, it’s a solid option that can solve this issue without any configuration.

I would be willing to make a PR, but I don’t want to overstep if this is out of scope for the maintainers.

@smithki Generally, anything that doesn’t affect consumers of this module should be just fine

Any progress on this?
i could help out , depending on whether @smithki is already working on it.
i dont have time to rework the whole build system, but could implement gulp-rollup, (or something similar?) which would just change how the browser bundle is build.

@jburghardt -- So sorry, things are busy for me at the moment. I don't think I'll get to this anytime soon. You're welcome to take it on.

Bumping this issue. pull request is pending.

PRs are still welcome.

https://github.com/puleos/object-hash/pull/94

Any interest in an ESM version for tree-shaking support? I'd be happy to send a PR for this 😄


6.35 issue

I'm having this error when trying to use it on playstation 5, some friends are also not able to use it, any idea what it could be or how to solve it?

Update your ffxiv executable.

same problem here

Mine is also broke rip rip :(

I'm having the same issue as above, even made a clean install but still get this. Does anyone know how to fix it?

What version of ffxiv.exe do you use?

I got my executable through a MF link instead of using the HFS method. Don't know how to check it. It was working before the latest update.
But if this could be the issue, I will download the game on my laptop and attempt with a fully updated one. Thank you.


Feats as rewards

It would be really cool if a feat could be part of the reward for a quest.

Hard to tell what do you mean, but if in system you are using feats are items, then you can have them as rewards (any Item can be a reward)


crash when ever I upgrade

when I upgrade the table I just crash immediately
this is the
log:
2020-09-21-7.log.gz
thank you

There is nothing in that file, I just see the world loading and unloading, I guess that's the crash but really I've never experienced this bug so I have no clue what the problem is.