SQL support?

Hello.
I briefly looked at the website and readme and couldn’t at a glance figure out if Bonsai is NoSQL DB or not. Do you have plans to add SQL support?
Thank you for working on a DB in Rust.

Thank you for checking BonsaiDb out. I currently don't foresee supporting SQ, but I do want to add a high-level query language someday.


Fix typos and inaccuracies in Supply Chain documentation

This PR fixes spelling/grammar errors and misaligned code blocks in the Supply Chain Transaction Family document. It does not alter the wording or flow of this document.
It also addresses some inaccurate and unclear docstrings in the Supply Chain proto-files. These have been reworded somewhat more heavily than the Transaction Family document.
This PR does not alter any functionality.

@cianx Probably true if anyone checks. In this case there were offset errors which have gone unnoticed for at least a few weeks. It's also only obvious if you build the docs. You cannot tell from the source code.
I'm also not sure including the exact source code is important. People can always look that up if they need it. A doc should have enough example code to explain how to use a component. Minor inaccuracies may not impair that use case. And regardless of whether it is in the example code, or elsewhere in the doc, you will always have the headache of making sure engineers update documentation when they change functionality.


As a professor I can retrieve statistics of covid cases in different student groups

... so that I can use it for research.

summarise command enables this user story to be made possible


Remove deprecated WinGet package for October 2023 GDK Update 6

Remove deprecated WinGet package for October 2023 GDK Update 6
Microsoft Reviewers: Open in CodeFlow

@microsoft/xbox-developer-experience-toolbox for review


install command fails when downloading GH CLI

Orb version:
2.5.0, 2.6.0
What happened:
After upgrading orb version to 2.5.0, install command started to fail with the following stacktrace:
Downloading the GitHub CLI from "https://github.com/cli/cli/releases/download/v/gh__linux_amd64.deb"...
Installing the GitHub CLI...
+ apt install --yes ./gh-cli.deb
Reading package lists... Error!
E: Invalid archive signature
E: Internal error, could not locate member control.tar{.zst,.lz4,.gz,.xz,.bz2,.lzma,}
E: Could not read meta data from /root/project/gh-cli.deb
E: The package lists or status file could not be parsed or opened.
+ set +x
Something went wrong installing the GH CLI. Please try again or open an issue.

Exited with code exit status 1

The issue seems to be related to this piece of code:
download_gh_cli() {
    local platform=$1
    local file_extension=$2
    if [ "$PARAM_GH_CLI_VERSION" = "latest" ]; then
        LATEST_TAG=$(curl url -s https://api.github.com/repos/cli/cli/releases/latest | jq -r '.tag_name')
        PARAM_GH_CLI_VERSION="${LATEST_TAG#v}"
    fi
    local download_url="https://github.com/cli/cli/releases/download/v${PARAM_GH_CLI_VERSION}/gh_${PARAM_GH_CLI_VERSION}_${platform}.${file_extension}"
    echo "Downloading the GitHub CLI from \"$download_url\"..."

    if ! curl -sSL "$download_url" -o "gh-cli.$file_extension"; then
        echo "Failed to download GH CLI from $download_url" >&2
        return 1
    fi
}

In particular, it seems that:

if [ "$PARAM_GH_CLI_VERSION" = "latest" ] evaluates false
as such, it tries to create a download_url with an empty or null PARAM_GH_CLI_VERSION

What I tried so far:

setting explicitly the version parameter, even though it should be optional
setting directly the  PARAM_GH_CLI_VERSION environment variable

In both cases the behaviour didn't change
Expected behavior:
The install command should be able to download GH CLI
Additional Information:
The same issue was reported here but it was closed without a fix

Does it work fine on 2.4? The issue you linked seems to be the same, but it was on 2.4


multi-user setup with slack doesn't work with a single agent

Describe the bug
A clear and concise description of what the bug is.
In the root readme.md file it mentions the suggested setup for a multi-user setup.
How do I implement MemGPT for multiple users?
The REST API for [MemGPT](https://memgpt.readme.io/reference/api) is flexible and leverages PostgreSQL DB or SQLite for its backend. To implement a multi-user setup, first determine the user_id (either create a UUID or use the user_id from your own database). Then [create an agent](https://memgpt.readme.io/reference/create_agent_api_agents_post), and finally use the agent_id and user_id to post a message or run a command. Internally the following occurs:

a user creates an agent
that agent is "owned" by a user
when the user sends the agent a message, that's stored in a message collection (messages are indexed by user and agent ids)
on the higher-level agents side (not talking about db implementation details), the agent can only see a few messages at a time, but has access to all the messages ever sent between it and the user via the recall memory search functions
the database is multi-user, and the REST endpoints function in a way where user data is not shared

From that implementation suggestion this what I what I heard the suggested implementation is:

Listen for app mentions
When user mentions slack bot
Chat with that specific user using user's version of AI persona
Ignore all other messages that don't mention slack bot and other users mention of AI persona

Please correct me if I'm wrong in my assumptions.
From what I understand is that this creates a personalised agent for each user, and only interactions with that user are recorded within it's memory.
There are some problems that I can see with this structure:

You need to create a new agent for each user
The agent only creates persona memories with respect to one user, so when the persona is talking with multiple users it's got a split personality, because the memories it creates regarding it's persona are only specific to that user.
It doesn't have a frame of reference with respect to the channel thread, conversations that occur in the channel thread are ignored, so it doesn't remember conversations or messages that are in the channel thread.
memories that are created with a user in private channel or one on one could be shared when chatting with an agent in broader channel like the #general channel.
There is no contextual awareness of the organization in which the agent is chatting with.

I've done a search for similar issues and found this one.
#668
In order to address these issues here is what I'm thinking should be done in order refactor memGPT to support a multi-tenant group chat environment like slack.

There should be one chat agent for the entire organization
The agent should listen/monitor conversations in all public channels, private channels it was invited to, group channels it was invited to and private one on one DM's it was invited to.
The agent should only respond when mentioned using the @ syntax
when creating memories of conversations it should store metadata about which message derived the memory, Who was the sender of the message and who has access to that message.
when doing retrieval of messages it should filter the messages based on the intended audience of the memory and who has access to those memories. So memories sent in one on one conversations are not shared in the general channel.
The agent should keep an array of user memories for each user in the system, each memory should contain metadata about which message or messages it was derived from and who has access to those memories.
The agent should follow GDRP regulations for the right to be forgotten, if a user is deleted within the system all memories of that user should be purged.
When conversing all memories that are used within the conversation should include references to the original message that was used to create the memory. This way the user can validate the memory contents on their own and should have access to that original message.
The agent should keep an array of channel topic memory banks that it uses to reference the channel history of conversation so it retains contextual awareness of what was talked about within the channel.
The agent should retain an organizational awareness of all the public channels and an overview of the content contained within them, as well as user overview as to easily be able to reference channels and users within the entire slack environment.

I did a brief overview of the code prompts and logic and found that Persona and Human objects appear to be like object storage banks for memories in order to implement a structure suggested above I would need to create an Organization object, refactor the Human object to be an array/map of Human objects, and create a channels/threads array/map of objects to store memories about.
Please let me know if there is any current or planned development in any of these directions. or any suggestions you may have in developing this.
Thank you for your time and your efforts in developing MemGPT, I think the work done here is excellent and I'm looking forward to developing it further.

@deefactorial we have considered making the "core memory" (the memory held in the LLM's context) more flexible (e.g. a key/value store) rather than having designated human/persona sections, but don't have concrete on the roadmap yet. If this is something you're interested in, I recommend implementing an extension of the CoreMemory object  that is more general or includes the sections you want (e.g. an organization).
Once you have a custom memory class, you want to give the agent the ability to modify that custom memory class. You can do that by modifying the core memory related functions (https://github.com/cpacker/MemGPT/blob/main/memgpt/functions/function_sets/base.py#L59) to match your memory class. Once you have the memory editing function, you'll want to create a custom preset that connects your memory functions instead:
system_prompt: "custom_prompt"
functions:
  - "send_message"
  - "pause_heartbeats"
  - "custom_core_memory_append"
  - "custom_core_memory_replace"
  - "conversation_search"
  - "conversation_search_date"
  - "archival_memory_insert"
  - "archival_memory_search"

You can also add other functions like delete_user_memories that clears out memories related to a user -- and you might want to extend the 'Passage' (archival memory rows) class to include metadata about what user a memory corresponds to.
This is a pretty advanced use-case that I'm not sure someone has tried before, but we do want to make the memory "programmable" to developers so feel free to reach out here or on discord and we'd be happy to help you make it work.


Coverage Error: could not find anchor: no matching instruction in range

Component
Forge
Have you ensured that all of these are up to date?

[X] Foundry
[X] Foundryup

What version of Foundry are you on?
forge 0.2.0 (5279f69 2022-06-29T00:09:16.192779Z)
What command(s) is the bug in?
forge coverage
Operating System
macOS (Intel)
Describe the bug
Getting an error when trying to run coverage:
(ERC20Upgradeable is an OZ contract)
all test run without issues
Analysing contracts...
Error:
could not find anchor: no matching instruction in range ERC20Upgradeable:2193:91:3

Some additional info:
same error when running forge coverage in this example repo: https://github.com/devanonon/ERC4626Votes (from this blog post)
Error is gone when reverting to a slightly earlier version of foundry - forge 0.2.0 (https://github.com/foundry-rs/foundry/commit/538548620b6f88760be9995084771c9c7697227e 2022-06-27T00:03:53.397337486Z)

This is a known issue, abstract contracts do not work right now. forge coverage is not production ready yet! Thank you for your report :smile:
The reason it works on a previous version is that the previous version used a different system to figure out what opcodes mark source ranges as covered, but that system is not super accurate.


Multi-threaded parameter estimation

Distributed has a lot of overhead. I think we should return to providing also multi-threaded assembly of linear systems

Very open to this, but I would prefer to see some scalability tests first. Could be something for a student to do.

I wrote a first version of this - not yet exported. My distributed assembly problems are immediately gone and I can now assemble larger datasets fully utilising all cores I have.

This problem probably only arises when there are many very small structures

This makes me wonder if adjusting the pmap batch size argument might also fix your problem. I'm happy to merge a PR if it improves things, although if a one-size-fits-all distributed option can work I slightly prefer that

I appreciate that, but the other thing to keep in mind is that for people like me who don't work with clusters but large shared memory nodes, the overhead of working with processes is pretty annoying.

the overhead of working with processes is pretty annoying

Is it starting up the processes that is annoying? Or just the throughput? If the throughput, I think we might be able to address that by increasing the batch size to reduce communication latency. I also work on single nodes most of the time.
But by all means do submit the PR if important

Starting up really is the issue - and for some reason Julia seems to want to precompile everything again on every process. Otherwise I wouldn't mind too much.

Make sure to test with datasets that have a lot of variation in structure size. I believe that's where we get the worst performance. A few huge structures and many unit cells.

Here's what I could manage today. It's for the PRX Silicon dataset (2475 configs of somewhat varying size), with a 4,16 basis (528978, 1445 design matrix). The threaded implementation is @cortner's ... the others I tried were comparable but slower.
Both plots are for the matrix assembly. The first plot includes Julia startup and compilation time (to look out for any extra distributed overhead). The second plot shows the time for a subsequent assembly (so, not affected by startup or compilation).
The main takeaways are how similar they are and that both hit diminishing returns fairly quickly. The distributed does seem to have marginally higher startup cost, but then slightly outperforms the threaded when that aspect is removed.

Do you want me to try one of your datasets? If the trend there is the same, then I suppose we need to look for system-dependent explanations?

Thank you for looking into this. I'll have to ask to share the dataset I'm using.

Starting up really is the issue - and for some reason Julia seems to want to precompile everything again on every process. Otherwise I wouldn't mind too much.

Because precompile does not work (for P4ML) Julia will compile everything for every process.
From what I read for performance above and here it seems that performance is limited by memory bandwidth. Most likely by random writes. This means that there is no difference between multithreading and multiprocessing.
In fact, if there is svd that takes a lot of time also. The option is to have multithreading with normal Lapack or multiprocessing with ScaLapack (this means also MPI). Basically having only multithreading is probably just easier.

seems that performance is limited by memory bandwidth

I didn't say this is always true and I would in fact be surprised if it is. I think this varies a lot between datasets.

In fact, if there is svd that takes a lot of time also

The SVD comes later. This discussion is only about assembling the design matrix.

Do you want me to try one of your datasets?

It was public after all. Would you mind trying this one?
https://archive.materialscloud.org/record/2022.102
If the performance is the same again, then I'll rerun your tests on my machine.

Sure - can you give me rough basis settings? Or even just the matrix size?

We should add proper benchmarking using PkgBenchmark.jl. I can add basics for of it, if you give me an example input. After that you can add more tests on the file.

TDEGS_4 = [
      [ 18, 14, 10, 6 ],  # 183
      [ 20, 16, 12, 8 ],  # 314
      [ 22, 18, 14, 10],  # 539
      [ 24, 20, 16, 12 ], # 929
      [ 26, 22, 18, 14 ], # 1609
      [ 28, 24, 20, 16 ], # 2773
      [ 30, 26, 22, 18 ], # 4789
   ]

make_model(tdeg;
         transform = (:agnesi, 2, 4),
         pair_transform = (:agnesi, 1, 4),
         pure = false, ) =
   ACE1x.acemodel(;
         elements = [:Fe],
         order = length(tdeg),
         totaldegree = tdeg,
         transform = transform,
         pair_transform = pair_transform,
         pure = pure,
         rcut = r_cut,
         Eref = Dict(:Fe => -3455.6995339),  )

make_model(TDEGS_4[6])

That's the model that should work.
The one that failed is
make_model(TDEGS_4[3]; pure=true)

Don't do this with level larger than 3 since generating the model then takes very very long.

I started to dig into this today. The first thing I wanted to test are drop-in threaded replacements for map from ThreadedIterables.jl and ThreadsX.jl.

Use Folds.jl rather than ThreadsX.jl.  Both use Transdusers.jl on the background, but Folds.jl is newer and can use distributed excecution also.

Ah, thank you! I was wondering about that, actually.

@cortner, I can confirm your distributed vs threading observation on the iron dataset, with one caveat, which is that I can't find the original data (from the earlier paper - whose links to the data appear broken), so I am only fitting to the "extensions" in the paper you linked (2306 configs, matrix size 36725,2773). Here are plots analogous to the above. I can't really explain them at this point.

We should add proper benchmarking using PkgBenchmark.jl.

I'm open to this, but don't have time to clean things up at the moment

that's much much smaller than the full dataset I'm working with, but perfectly fine if it repreduces the problem :)

I spent most of last night and today (without much success) trying to improve the parallel scaling of assembly, looking at both multiprocess and multithreaded. In particular, I set a goal to reduce assembly time for the silicon dataset (same model parameters as in the plots above) to below one minute using 50 threads and/or processes. I tried a lot of things, but I never got below 100 seconds.
A few observations:

At first, I thought the bottleneck might be that we have all processors/threads write to a single matrix, but that's wrong. If I simply compute the matrix elements and throw them away immediately - eliminating any synchronization concerns - the timings don't improve.

I expected threaded evaluation of the assembly loop over data (without writing/saving any of the results) to be extremely fast and parallelizable - but not so. I believe the explanation is related to garbage collection, as I saw high GC times; see also www.github.com/JuliaLang/julia/issues/32304.

I learned about CachingPools for pmap, which didn't solve my problem but may be useful in the future (www.github.com/JuliaLang/julia/pull/33892).

I did see some improvement from batching, although it wasn't dramatic.

All together, I think I will put add a batch_size option to the main assembly routine, but I'm running out of ideas for dramatic improvement.

That means that the reason for the bad performance is in feature_matrix, target_vector and/or weight_vector execution. They do calculate energy, forces and virials? So, it might be that those are the cause the issues.
Do those energy, forces and virial calls go back to JuLIP?

They do - and in the past we ensured that the JuLIP calculators switch to single-threaded mode. But maybe we need to double-check this here.

Also with JuLIP retirement incoming, we need to reimplement them to at some point. So, we could consider doing it now.

That's a very risky and huge change. We cannot do this before publishing.

That means that the reason for the bad performance is in feature_matrix, target_vector and/or weight_vector execution.

Agree - at one point I confirmed it was basically all feature_matrix. If I were going to push this further (not likely in the short term), I would probably try to reduce the allocations there


HBASE-26325 Backport the HBASE-26305 to branch-1. Move NavigableSet add operation to writer thread in BucketCache

https://issues.apache.org/jira/browse/HBASE-26325

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m  0s
Docker mode activated.

-1 :x:
docker
5m 34s
Docker failed to build yetus/hbase:633d966bfe.

Subsystem
Report/Notes

GITHUB PR
https://github.com/apache/hbase/pull/3720

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3720/1/console

versions
git=2.17.1

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

This message was automatically generated.

Have you rebased your codes on latest branch-1? @YutSean


Clean old layer selector code.

This PR remove old code related to the editor's layer_selector.
cc @alonsogarciapablo @xavijam

There is nothing like remove old code.
🔥


translate -> getLocalizedString

This seems to be what mojang calls it. Also translate doesn't make much sense because the string you pass in is unlocalized. Translation would happen between two languages, not between unlocalized and localized

Would you guys prefer getLocalizedString or simply localize?

Let's do localize. We know the quality of mojang names, so let's use efficient names instead.

On a side note, should translate in other usages, e.g. TranslatableText, be converted to localized, e.g. LocalizeableText

@Yanis48 Agree with this change from translate to localize?

Nope I don't

Hmm, we really need more discussion on this one then.


Scan unsuccessful until another app scanned.

EDIT:
I have noticed issues similar to mine have been submitted, and often result in a redirection to a closed issue. Since the recurring fix to these issues is often related to permissions, I want to specify this is not a permissions problem. The scan works perfectly fine for most devices I have handled, ranging from Android 8 to 11, with notably S10, S20. As for iOS, I have had no problem on any version/phones (iPhone 8/11/12).
Hello, I have had a strange error which I just can't figure out. I have an app using Plugin.BLE, and at some point I start a scan to detect a specific device type. After implementing the scan, it worked well (i.e it scanned and found the devices) on just about every phone I could lay my hands on, both Android and iOS. However, there is this one phone (Samsung Galaxy S10, Android v11.2) who would never find any device from the scanning operation. It seemed to be, by all evidence, a problem with this particular phone. However !
Steps to reproduce

Scan for a bluetooth device using Plugin.BLE. The device is not found, no matter the amount of retries.

Scan for the same bluetooth device using the app nRF Connect. The device is found.

Scan for a bluetooth device using Plugin.BLE. The device is NOW found.

Expected behavior
The initial scan should find the device without using another app.
Actual behavior
The scan will not detect my device until another app discovered it prior.
Crashlog
Configuration
Version of the Plugin: 2.1.1
Platform: Android 11
Device: Samsung Galaxy S10

Hi @5CoJL,
I'm the friendly issue checker.
Thanks for using the issue template :star2:
I appreciate it very much. I'm sure, the maintainers of this repository will answer, soon.

Update:
I have now fallen on another problem in the likes of the one detailled above.
On a Xiaomi XI9, I cannot find any devices when scanning with either my app using Plugin.BLE, or the app nRF Connect.
However, I find the devices via the Bluetooth App native to the phone. I cannot figure out if this is a problem from my app, Android or even the plugin.

Ok, the issue was enabling the service location. I am slightly ashamed.


test:  There are some false positives in e2e-test ,Need to be fixed.

Issue description
Environment

your apisix-ingress-controller version (output of apisix-ingress-controller version --long);
your Kubernetes cluster version (output of kubectl version);
if you run apisix-ingress-controller in Bare-metal environment, also show your OS version (uname -a).

Minimal test code / Steps to reproduce the issue

What's the actual result? (including assertion message & call stack if applicable)
What's the expected result?

Currently our e2e test case seems to run pretty well.
I will close this issue. Feel free to reopen it, if you have any question.


Plugin Broken with 3.1.2 ?

Each tpsheet import make Godot 3.1 not responding, the application has to be killed and restarted for it to import the next tpsheet which will again crash it and so on.
So right now, it's not usable at all :(
Is this plugin still maintained ?

The issue appear when at least 2 tpsheet files are present during the import, the first one is processed correctly and the second one freeze GoDot.

Yes it is. You can try if the current version fixes the issue for you.


change message

recent update jira-ticket # 12772

additional redo recent update jira-ticket # 12772

now we are closing jira-ticket # 12772


fix: update to eye v10.2.5

fix: update to eye v10.2.5

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

npm package (@latest dist-tag)
GitHub release
v15.2.5

Your semantic-release bot :package::rocket:


Michael Chen - Assignment6

"ERROR: Permission to DS219/spark-seprep.git denied to michen32."

Good job @michen32 10/10

But this PR has assignment 6 alongwith assignment7. cc @sallyom @umohnani8

To be 100% honest, I can't remember what I did for branching and PR... will this be an issue right now?

@michen32 @aakankshaduggal I'll merge the assignment6 & assignment7 PRs tomorrow in class - I'll first show Michael how to best separate the files so the assignment6 files are with this PR and the assignment7 files are with #138 - here's what you'll need to do (we can do this in class if it's not clear)- since you've already opened the PR from your main branch, we'll stick with using your main branch for this PR:
git checkout main
git log (cp the sha from the commit below `87ed...`
git rebase -i <commit below 87ed>
with vim, delete the 3 lines with the 3 unwanted commits, then close vim
git push -f origin main

Note: the 2 files for assignment 7 live in another branch, assignment-7-branch - deleting those commits from this PR won't affect that branch.

@aakanksha I'm merging this, it has the image for assignment 7 too.


Whitelisting based on Components gives false message

Description
Using components to whitelist items in storage gives the message "that doesn't go there" even though it does. It doesn't stop the item from going in. Just gives the message.
Reproduction
Setup a whitelist on a storage entity using "components," Try to add the whitelisted item into the storage entity. Get message.
Screenshots

Additional context
n/a

this is likely because the component being used isn't networked.

this is likely because the component being used isn't networked.

That's a little over my head and not quite sure what it means. This is the example of what I was trying to do:

both foodcomponent and producecomponent only exist on the server, so the client, which is handling the popups, thinks that the item doesn't pass the whitelist.

Ok, that makes sense.


--debug Logback Classic Logger instance check

Spoke with @abextm about this on Discord...
When using the example-plugin base project, the build.gradle imports slf4j-simple, and excludes logback-classic. However, this (slightly misleadingly) causes a crash if you're using the --debug flag, since the runtime log level setting is a logback-classic specific feature (it's not an action you can do with just slf4j-api).
This PR adds a check to make sure that the root logger being modified is actually a logback-classic logger, by checking which SLF4J implementation has been bound. If --debug was set, but we don't have a logback-classic logger instance, it prints out a warning to the developer to set the root logger level using another method.
I used fully-qualified names for the Logger classes to avoid any confusion about which type we have at any given time.

Amended commit to satisfy checkstyle errors

I think I would rather just have the pluginhub plugins use logback. abex says that should work.

Resolved in runelite/plugin-hub#881


npm/npmjs/-/mocha/5.2.0

Type: Auto
Summary:
npm/npmjs/-/mocha/5.2.0
Details:
Add MIT-feh license
Resolution:
Auto-generated curation. Newly harvested version 5.2.0 matches existing version 5.0.1.
Matching license file(s): package/LICENSE
Matching metadata: registryData.manifest.license: 'MIT'
Affected definitions:

mocha 5.2.0

You can review the change introduced to the full definition at ClearlyDefined.


(FACT-1588) Fix for OpenSSL 1.1.0

Building with OpenSSL 1.1.0 failed due to a change in const-ness of the
BIO_f_base64 return value. Update functions to accept a const value
when appropriate. Should be backwards compatible with non-const version.

CLA signed by all contributors.

Mostly unrelated side note, I reeeally want to get updating the POT file out of these PRs and into CI like it is for Ruby projects.

I can drop the POT portion, it may not be relevant anymore.

No you should keep it for now. We're not updating this any other way right now. I just want to get it automated and in line so we have one story around how and when we do it. Also want to stop relying on whatever tool a dev has installed (because different gettext versions sometimes spit out different metadata).


UnderlineSpaces and StrikethroughSpaces don't seem to work properly

We're supposed to be able to use these methods to decide whether spaces are subject to the underline/strikethrough styles.
Unfortunately, this effect is not reached. There's no visible difference in the output.

Found while working on #109.

cc @muesli @meowgorithm

Seeing the same

I investigated this issue and it looks like both UnderlineSpaces and StrikethroughSpaces don't work because Underline will underline the whole string along with the spaces.
More info in the below screenshot and code:

buttonStyle = lipgloss.NewStyle().
			Foreground(lipgloss.Color("#FFF7DB")).
			Background(lipgloss.Color("#888B7E")).
			Padding(0, 3).
			MarginTop(1)

	activeButtonStyle = buttonStyle.
				Foreground(lipgloss.Color("#FFF7DB")).
				Background(lipgloss.Color("#F25D94")).
				MarginRight(2).
				Underline(true).UnderlineSpaces(false)

To solve this one would have to check the flag when writing to the string buffer and skip the spaces when underlining or using strikethrough.


use moment.js for date stuff

so much easier

actually date-fns works too, has less bloat also
https://github.com/date-fns/date-fns


Header from H2 -> H3 in error summary page

Checklist:

[ x ] Documentation
[ x ] Tests
[ x ] Ready to be merged

Codecov Report

Merging #368 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master   #368   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          77     77
  Lines         409    409
  Branches       14     14
=====================================
  Hits          409    409

Impacted Files
Coverage Δ

components/error-summary/src/index.js
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

nice one!


Claim event when no message from claimant sent showing up as empty

When no message sent from view claim yet there is an update it is being displayed on claimant side as this and empty on the caseworker side as well

verified


Repository name not camel case

Even though not really established as a standard across all computer languages used in OHDSI, we do tend to use camel case for the repo names. So could we change THEMIS into Themis?

If it helps getting the conventions figured out better... :)


Plan how to generate the data and make prototype

Build a script to webscrape vx-underground for all the samples and their families.
All the samples will be saved on my SSD. In the issue #2 I mentioned how I will take the data of scicore.

Current high level plan is:
Take 1-5 samples and fuzzy hash them into a nosql with the following schema:
{
family:
hash:
fuzzy_hash:
prediction:
}
Then i will test the 4 fuzzy hashers and on of accurate they can predict the family and calculate the ROC curve.

see Testing_Framework.md


arm64 support - set c# target framework to netcoreapp6.0

netcoreapp2.0 does not seem to support arm64

please create a PR against https://github.com/ros2-dotnet/ros2_dotnet - we are using the repo from there - as of https://github.com/4am-robotics/orga/issues/5221


Merge support specified services

Sonar coverage improvement will be done in test sprints. Right now merge the changes to avoid blocks.


Fix/string-references-handling

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 0% with 12 lines in your changes missing coverage. Please review.

Files with missing lines
Patch %
Lines

src/pymailai/message.py
0.00%
12 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.

Files with missing lines
Coverage Δ

src/pymailai/message.py
0.00% <0.00%> (ø)


[BACKLOG-41224] Updated the IBM MQ libraries to version <IP_ADDRESS> to de…

…al -- 10.2 branch
with Java17 compatibility issues.

Original master (10.3) PR: https://github.com/pentaho/pentaho-kettle/pull/9472

 Note:

Frogbot also supports Contextual Analysis, Secret Detection, IaC and SAST Vulnerabilities Scanning. This features are included as part of the JFrog Advanced Security package, which isn't enabled on your system.

🐸 JFrog Frogbot

:white_check_mark: Build finished in 29m 4s
Build command:
mvn clean verify -B -e -Daudit -Djs.no.sandbox -pl \
plugins/streaming/impls/jms

:ok_hand: All tests passed!
Tests run: 26, Failures: 0, Skipped: 0    Test Results

:information_source:  This is an automatic message


ubuntu 16.04, node v8.5.0,npm 5.4.1

$ sudo npm install -g elm
npm WARN deprecated<EMAIL_ADDRESS>Use uuid module instead
/usr/bin/elm -> /usr/lib/node_modules/elm/binwrappers/elm
/usr/bin/elm-make -> /usr/lib/node_modules/elm/binwrappers/elm-make
/usr/bin/elm-package -> /usr/lib/node_modules/elm/binwrappers/elm-package
/usr/bin/elm-reactor -> /usr/lib/node_modules/elm/binwrappers/elm-reactor
/usr/bin/elm-repl -> /usr/lib/node_modules/elm/binwrappers/elm-repl

<EMAIL_ADDRESS>install /usr/lib/node_modules/elm
node install.js

Error extracting linux-x64.tar.gz - Error: EACCES: permission denied, mkdir '/usr/lib/node_modules/elm/Elm-Platform'
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>install: node install.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /home/m/.npm/_logs/2017-09-14T08_43_28_874Z-debug.log

Solution by this

I had same problem, but solved it by running sudo npm install -g elm --unsafe-perm=true --allow-root from this issue in electron
ubuntu 16.04
node -v  v7.10.0
npm -v 5.3.0

I also encountered this issue recently. The problem I think is that the default installation of NodeJS in Ubuntu 16.04 installs "nodejs" rather than "node", to resolve this, run this command on CLI:
sudo ln -sf /usr/bin/nodejs /usr/bin/node
After this, try to install elm as usual. Hope this helps :)

OP's issue has been resolved: https://github.com/elm-lang/elm-platform/issues/218#issuecomment-329420591


Websocket codes

Pull Request Type

[x] Feature addition
[ ] Bugfix
[ ] Documentation update
[ ] Code refactor
[ ] Tests improvement
[ ] CI/CD pipeline enhancement
[ ] Other: [Replace with a description]

Description

Creating on behalf of @zevaryx.
This PR marks additional gateway close codes as recoverable/resumable.
to be clear
If your bot is online 24/7 you need a process manager like docker, systemd or whatever. Do NOT rely on the library to automatically restart itself. The library certainly tries to recover, but the internet is a scary place
Changes

As above
Adds a sanity check for development to ensure resumable is a subset of recoverable

Related Issues

Test Scenarios

Python Compatibility

[ ] I've ensured my code works on Python 3.10.x
[x] I've ensured my code works on Python 3.11.x

Checklist

[x] I've run the pre-commit code linter over all edited files
[x] I've tested my changes on supported Python versions
[ ] I've added tests for my code, if applicable
[ ] I've updated / added  documentation, where applicable

Codecov Report
Patch coverage: 57.14% and project coverage change: -12.94 :warning:

Comparison is base (4a661d9) 60.32% compared to head (90a9b91) 47.39%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@              Coverage Diff              @@
##           unstable    #1403       +/-   ##
=============================================
- Coverage     60.32%   47.39%   -12.94%
=============================================
  Files           139      139
  Lines         14633    14638        +5
=============================================
- Hits           8828     6937     -1891
- Misses         5805     7701     +1896

Impacted Files
Coverage Δ

interactions/client/const.py
87.23% <57.14%> (-4.91%)
:arrow_down:

... and 65 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

besides my suggestions it looks good to me, but I won't approve it since I don't know the codes and whether they are correct or not

Merging without approval due to importance of this PR


metrics metadata gc

Hi, I found timescale db often has a lot of left over metadata (e.g. prom_data, prom_catalog, internal chunk tables) after we delete the series.
How do I properly cleanup these data? thanks

If you want to completely delete a metric you can use the prom_api.drop_metric('container_cpu_load_average_10s'). Take into account that the function won't run if the Promscale connector is running. You can find more information here
If you're interested on what the function does, you can look at the source code here:
https://github.com/timescale/promscale_extension/blob/3087f70d18f158b0af1531a778360e7ec997a165/migration/idempotent/001-base.sql#L1000-L1029
Cheers


Outdated dependency npm-install-peers

In version 5.0.1 the package.json npm-install-peers has been added as a dependency. This dependency is last updated 2 years ago.
"dependencies": {
    "@types/glob": "^8.0.0",
    "npm-install-peers": "^1.2.2"
  }

We've added the npm-glob-promise to our project, and since version 5.0.1 we get 10 vulnerabilities (1 low, 6 moderate, 3 high), which all trace back to npm-install-peers.
Version 5.0.0 doesn't have this dependency, and with that specific version we don't get any vulnerabilities.
Could the dependency get removed?

The npm-install-peers has a prerequisite of npm < 7. When I removed that, npm threw an error saying that some functionality has been removed in npm v8.
Because of the nom requirements, npm will install npm v4. That contains all the vulnerabilities.
I don't know anything about the workspaces, but maybe there is another way to get them to work.

I added that dependency to address node v14 / npm 6 where peer dependencies are not automatically installed ...
I think the easiest path forward is to declare node v14 no longer supported ...

released v6.0.0 that declares node v14 no longer supported

Thanks for the quick fix!

Hi @ahmadnassri. First of all, thank you for maintaining this project.
It's an excellent solution to declare that v14 is no longer supported in v6.0.0. However, My understanding is that 5.0.1 should not impose node 16, as this would be a breaking change that requires a major upgrade (not a patch one).
I work on a private project that has a dependency using this library:
A -> B -> C - where:

A: is the project I work on;
B: is a direct dependency of ours (which we have no control over);
C: is glob-promise.

A still relies on node 14. We have plans to upgrade it, but it''ll require significant changes in our infrastructure, so it'll still take time for us to accomplish that.
I can see<EMAIL_ADDRESS>in B's dependencies. Since 5.0.1 was released, this dependency is automatically resolved to 5.0.1, which breaks our build.
As a temporary solution, I'm relying on yarn resolutions to force B to use 5.0.0. Here are a couple of reasons why this isn't an ideal scenario:

It could make B behave unexpectedly;
We won't benefit from future updates to this library.

Besides, Node 14 EOL is not yet here (Apr 30).
With that in mind, could you remove Node 16 as a requirement for version 5.x.x? At least while Node 14 is still officially maintained?
P.s.: Let me know if you want me to open an issue for this.
Thank you for your support!


Do conditional import higher up to make sure import stays in scope

This fixes issue-#174 while keeping a conditional import

@wouterdebie @ravwojdyla if you have the time please check and merge this as now kerberos authentication is blocked by this issue.

Thanks @bolkedebruin for your contributions! I would maybe rename the global variable to internal notation _kerberos_available (do you agree?). Otherwise looks good.
We really need to create some kerberos testing env.

@ravwojdyla agreed and fixed.
Love the have kerberos testing. I am doing some research on it, but it is not pulled off easily. Does travis support docker-on-docker?

Sorry to nit-pick, but could you squash this commit?

@wouterdebie np. Done.


CDN Purging is broken, stale JSON responses are served instead

In https://github.com/pypi/warehouse/pull/11920 we removed traversal for our legacy JSON views, however our purging mechanisms depend on traversal to determine when to issue purges. As a result, PyPI is currently serving stale data for all JSON endpoints for which responses existed before the merge of #11920, as no purges have been issued for these when something changes which would update the responses here (e.g., publishing a new release).
(ref: https://github.com/pypi/warehouse/issues/11934, https://github.com/pypi/warehouse/issues/11936, https://github.com/pypi/warehouse/issues/11937, https://github.com/pypi/warehouse/issues/11939, https://github.com/pypi/warehouse/issues/11940)

Hi @di! Thanks for your work resolving this. I'm coming from the related https://github.com/python-poetry/poetry/issues/3543 and https://github.com/mrabarnett/mrab-regex/issues/475 issues. Will you confirm whether purging is finished for "projects which had old releases but new files added after the bug was introduced"? Thanks

Yes, should be. If you're still having problems though, let us know.

Still seeing problems. For example:
https://pypi.org/project/virtualenv/
Stated release is 20.16.0, but shield shows latest as 20.15.1.
curl shows the same behavior that I reported in #11936 several days ago:
$ curl --silent --location --header 'Accept: application/json' https://pypi.org/pypi/virtualenv/json | jq '.releases' | grep '20\.15\.1' || echo $?
  "20.15.1": [
      "filename": "virtualenv-20.15.1-py2.py3-none-any.whl",
      "url": "https://files.pythonhosted.org/packages/6f/43/df7c7b1b7a5ac4e41fac24c3682c1cc32f2c1d683d308bba2500338d1e3e/virtualenv-20.15.1-py2.py3-none-any.whl",
      "filename": "virtualenv-20.15.1.tar.gz",
      "url": "https://files.pythonhosted.org/packages/a4/2f/05b77cb73501c01963de2cef343839f0803b64aab4d5476771ae303b97a6/virtualenv-20.15.1.tar.gz",
$ curl --silent --location --header 'Accept: application/json' https://pypi.org/pypi/virtualenv/json | jq '.releases' | grep '20\.16' || echo $?
1

I'm not as familiar with the metadata APIs, but I get Unable to find installation candidates for regex (2022.7.25), an error message from poetry, even after starting from scratch.

I'm not as familiar with the metadata APIs, but I get Unable to find installation candidates for regex (2022.7.25), an error message from poetry, even after starting from scratch.

@gregorybchris : Interesting. The JSON API shows a ton of wheels available for that release. (I won't paste the lengthy results list here, but you can see for yourself with something like: curl --silent --location --header 'Accept: application/json' https://pypi.org/pypi/regex/json | jq '.releases' | grep '2022\.7\.25') (You can also use the Simple API to see the list as well: curl --silent --location --header 'Accept: application/vnd.pypi.simple.v1+json' https://pypi.org/simple/regex | jq '.' | grep '2022\.7\.25') Some of the other people, who filed issues around the same time I did, reported that they could not find the release files on pythonhosted / pypi.io. Do you know which wheel Poetry is trying to fetch? Feels like there may actually be two different modes of breakage at work.

I'm not as familiar with the metadata APIs, but I get Unable to find installation candidates for regex (2022.7.25), an error message from poetry, even after starting from scratch.

Have you cleared your poetry cache? poetry cache clear pypi --all

Thanks @neersighted!! That worked.

I'm still experiencing issues: https://pypi.org/pypi/picked-group-fdr/json still shows version 0.2.2, even though https://pypi.org/pypi/picked-group-fdr/0.2.3/json correctly shows the newest version

Same issue as @MatthewThe.
https://pypi.org/pypi/codemagic-cli-tools/json shows 0.29.2 however the following links are up to date and existing:
https://pypi.org/pypi/codemagic-cli-tools/0.30.0/json
https://pypi.org/project/codemagic-cli-tools/0.30.0/

Same issue here.  I am seeing the same issue with https://pypi.org/pypi/nautobot/json shows 1.3.8 however https://pypi.org/pypi/nautobot/1.3.9/json and https://pypi.org/project/nautobot/1.3.9/ show 1.3.9 has been released.

I released a new version of minicapy 20 hours ago which is still not visible in the API when requesting with headers Accept-Encoding: gzip,deflate, seems this issue was closed a bit too fast.

@di dbt-core is having this issue for me as well - the json response still shows 1.1.1 even though 1.2.0 was released yesterday. Is this expected? I experimented locally, leaving off the Accept-Encoding header, and that got me 1.2.0, but requests adds the encoding header by default.

Hi, just in case, this is happening for jsonschema too (version 4.8.0 was released +-10 hours ago but the json response returns as latest release 4.7.2)

For people still encountering this issue, @dstufft recommended the following in #11936 to help PyPA debug:

It would be useful to know for someone who is getting a stale response, can they add the Fastly-Debug: 1 header, and see if there is a Surrogate-Key header, and if so, what the value is of that header?

Can confirm jsonschema is still broken:
$ curl --silent --location --header 'Accept: application/json' https://pypi.org/pypi/jsonschema/json | jq '.releases' | grep '4\.8\.0' || echo $?
1

$ curl --head --verbose --location --header 'Accept: application/json' --header 'Fastly-Debug: 1' https://pypi.org/pypi/jsonschema/json | egrep '(surrogate|fastly-debug|pypi|etag)'
etag: "MSWJBwrgR1jE+dkxcgGFlw"
surrogate-control: max-age=86400, stale-while-revalidate=300, stale-if-error=86400
surrogate-key:
x-pypi-last-serial: 14406929
fastly-debug-path: (D cache-bfi-krnt7300063-BFI<PHONE_NUMBER>) (F cache-bfi-krnt7300080-BFI<PHONE_NUMBER>) (D cache-iad-kjyo7100124-IAD<PHONE_NUMBER>) (F cache-iad-kjyo7100124-IAD<PHONE_NUMBER>)
fastly-debug-ttl: (H cache-bfi-krnt7300063-BFI - - 424) (H cache-iad-kjyo7100124-IAD 48778.980 86400.000 37621)
fastly-debug-digest: c2b71dfdc359c26a52aa1c6f362af62292fdbc19166c67968435e503b1e77686

Just in case, jsonschema is now working :) 🎉


Auto-number attribute UI is available in maker portal

This page states there's no UI for Auto-number attribute but maker portal gives UI for creating auto number attribute.
https://docs.microsoft.com/en-us/powerapps/maker/common-data-service/autonumber-fields

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

ID: 97ed5d32-c7ea-cf1b-4b67-42d220bced10
Version Independent ID: 809601df-9094-fa16-2aba-f8941c2fd1db
Content: Create auto-number attributes (Microsoft Dataverse) - Power Apps
Content Source: powerapps-docs/developer/common-data-service/create-auto-number-attributes.md
Service: powerapps
GitHub Login: @NHelgren
Microsoft Alias: jdaly

Hi @bhshastr, The note in the document indicates that the classic web client does not provide the ability to manage the attribute, which is true. This is available for the UCI though. Once the web client is retired the document will be updated.

Hi @NHelgren -
The page states "There is no user interface to add this type of attribute" which is misleading.

Ahh I found the issue, this was submitted on the Maker document but the problem was in the Developer document here: https://docs.microsoft.com/en-us/powerapps/developer/common-data-service/create-auto-number-attributes
I have submitted a fix and it should appear shortly.


categorize UAM as basal if at least 1h of carb absorption observed

We've seen problems with autotune failing to converge, and instead constantly trying to reduce basals until it hits safety limits, because too much data that would otherwise indicate basals are too low is being excluded as UAM.  We were able to avoid this issue by using --categorize-uam-as-basal=true, so it appears that categorize-uam-as-basal should be the default behavior at least when meals are being properly announced and CSF exclusion is working.  To preserve the UAM exclusion for folks who don't routinely announce meals, this PR sets the --categorize-uam-as-basal=true behavior as the default whenever at least 1h per day of CSF exclusion is observed, which will be nearly all days where one or more meals is announced.

👍  We have had very similar experiences, and always use --categorize-uam-as-basal=true.
Unless we consistently miss an announcement at the same time every day (like coffee 😄), we don't see a negative effect of basals creeping up too high due to autotune's dampened response to basal changes.

We've got the same issue - without the setting, autotune consistently suggested decreased basals - so I think this would help a lot.
Semi-related
Since turning autotune off, we're still taking manually-ran autotune suggestions with a bit of a grain - it's still suggesting basals that seem to be too low. Combined with autosens, ISF dropping because "extra" basal required means ISF continues to be pushed down during the day which causes a roller coaster.

@zgohr have you been running with or without --categorize-uam-as-basal=true?

When I referred to running autotune manually, we're running it with the setting true.

Ready to merge this if no objections.


Streamline func create for newcomers

Currently func create takes a mandatory argument (language) in the shape of a flag. It also requires to be run inside an empty directory (unless you specify the path) which is not optimal or expected by all users.
Mandatory arguments
Currently, the "language" flag is the only mandatory parameter so,
If you type func create on an empty directory you get:
> func create
Error: Required flag "language" not set.
Available language runtimes are:
  go
  node
  python
  quarkus
  rust
  springboot
  typescript

This doesn't help a newcomer to know what the language flag is, for some people this will mean --language or -l but it might not be clear for everyone. Notice that this is a required parameter hence making this a positional argument might make some sense. In such a case we can make something like this:
>func create

Language is missing, please add the language argument:
Example: func create <language> choosing one from the following list
Available language runtimes are:
  go
  node
  python
  quarkus
  rust
  springboot
  typescript

Checking the func create --help, it shows an example that is not working:
 o Create a Node.js Function in the directory 'myfunc'.
          $ func create myfunc

Directory creation
Creating or not creating a directory for the function is a controversial topic that, in my opinion, we need to fix.
If we follow the git, npm  or even go mod approach you are always working in a directory where your project will live. For these cases, the user needs to create a directory. Current func create checks if the user is in an empty directory to create a function if the name of the function is not provided as the last argument, in which case it creates a directory.
For example:
func create -l go func3
Created go Function in /tmp/func3

Created a directory and a function inside it.
For this one I have mixed feelings, as we should decide if we create or not create directories with func, supporting both in my opinion causes confusion.
if we change [path] to be a flag, it will make more sense for cases where a CI tool is running create, so we don't loose the functionality.
Open Questions
Do you have any other categories of things to improve for func create ? Any other thoughts or ideas?
@lance @lkingland @zroubalik @matejvasek

We have talked in the past about entering "confirm" mode when a user types simply func create with no flags/parameters. See https://github.com/knative-sandbox/kn-plugin-func/issues/573#issuecomment-1017995470
Personally, I like this a lot.

Current release v1.7.0 shows after func create this:
Error: Function name 'Knative' must consist of lower case alphanumeric characters or '-', and must start and end with an alphanumeric character (e.g. 'my-name',  or '123-abc', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?')

I'll take over the task: enter "confirm" mode after func create; as proposed above.

/assign @grafvonb

@lance @salaboy Could you clearly state what is the scope to implement for this issue? I think I have mixed it with #573...

@grafvonb we talked a little about this in the working group meeting. It's not very clearly laid out, and could benefit from coordination between this issue and a few others - or it could be closed as a duplicate. @salaboy do you want to chime in here?

Looking closer at old comments and such, I think this is almost certainly a duplicate of #573 but will let @salaboy and @lkingland chime in.

/remove-lifecycle stale

@lkingland after going through each comment, my question is what shall be the final design for this? I mean shall we put user in the confirm mode triggering func create -c or shall we build  fully interactive func create command.


:cyclone: Move database deconnection to the finally block

Describe this PR
The purpose of this PR is to refactor the legacy code which disconnects the database twice :
1 . In the Success phase of the promise.
2. In the Failed phase of the promise.
It is possible to set await prisma.$disconnect() in the finally block of the code you provided. This ensures that the connection to the database is always properly closed, regardless of whether the then or catch block is executed.
Changes
I have added a new block finally and moved prisma.$disconnect() inside it.
Before
main()
  .then(async () => {
    await prisma.$disconnect()
  })
  .catch(async (e) => {
    console.error(e)
    await prisma.$disconnect()
    process.exit(1)
  })

After

main()
	.then(async () => {
		console.log('Success');
	})
	.catch(async (e) => {
		console.error(e);
		process.exit(1);
	})
	.finally(async () => await prisma.$disconnect());

Unfortunately after our docs migration is this a change that should now be in a number of new pages. If you'd like to re-submit, please let us know and we'd be happy to help!


AGENT-629: add image to the release payload

This patch enables the include of the agent-installer-utils image into the release payload

/lgtm


Webview is loading continuously in iOS.

Bug description:
We are using Webview to HTML dom in Android it's working as expected but in iOS, it is continuously loading.
To Reproduce:
<WebView
originWhitelist={["*"]}
source={{ html: this.state.htmlDOM, baseUrl: Services.mSiteDomain }}
onShouldStartLoadWithRequest={request => {
const categoryId = FNPUtils.parseHtmlLink(request.url);
this.props.navigation.push("GiftListScreen", {
productCategoryId: categoryId
});
return false;
}}
showsVerticalScrollIndicator={false}
/>
Expected behavior:
It should open only once and when the user clicked on anything on Webview then it should redirect to a particular thing
Environment:

react-native version: 0.60.0
react-native-webview version: 8.0.0

I'm experiencing this same exact issue - Everything loads fine on Android, but iOS just shows the loader forever. I added all of the event props, and onLoadProgress gets triggered twice - First with "0.1", and second with "0". So it seems like something is failing, but none of the other events ever get called.

I can't imagine no one else is running into this issue. Anyone know what we might be doing wrong?

@ryanmcclure4 No, I didn't get why it is.

I'm also stuck in same issue,  onShouldStartLoadWithRequest   loads only once in case of Android,  but for iOS it loaded multiple times,  ideally it should be called only once

I've been getting same type of error.

"react-native": "0.61.5",
"react-native-webview": "^8.0.5",

My component has;

onShouldStartLoadWithRequest
onLoadStart
onLoadEnd

onShouldStartLoadWithRequest & onLoadStart are called but onLoadEnd isn't called.
With some URL, it works well, but with some other URL, onLoadEnd never be called.
Android is OK, only iOS has this problem.

This happens because the behaviour of onShouldStartLoadWithRequest is not the same for iOS and Android. On iOS the event is triggered on the first page load, so you need to return true the first time. On Android the event is triggered only when navigation between pages occurs.

for me, the webview progress stuck at value 0.870618947737071 and it does not fire the next onNavigationStateChange that i expected

i randomly reproduced this bug, and i got this error
Could not signal service com.apple.WebKit.WebContent: 113: Could not find specified service

and maybe related to this link?

it appears to me, my users are using iOS 14. there is no finding yet on previous version of iOS.

As a temporary solution, I removed the "onLoadStart" on iOS throught "Platform.OS", and let it only in Android.
Another solution would be: create a modal with loader above the webview, and display it until you want, change the state of visibility of the modal.


volume bind-mount commandline is wrong

Volumes & bind-mount
Bind-mount your prometheus.yml from the host by running:
docker run -p 9090:9090 -v /tmp/prometheus.yml:/etc/prometheus/prometheus.yml
prom/prometheus
SHOULD BE
docker run -p 9090:9090 -v /etc/prometheus/prometheus.yml:/tmp/prometheus.yml
prom/prometheus

my mistake


Errors console extensions

VSCode Version: 1.14.0 - Insiders (b8cd5b9 - Date 2017-07-06T20:24:26.721Z)
OS Version: Windows 10

-- Sorry for the English, I used Google Translator --
See the gif. Using the command to open the VSCode with the exceptions disabled appears this error. With the enabled extensions appear as well.

The error appears for an extension of mine that is already disabled, and the others for extensions that are not even installed.
Can it hurt something in performance?

Reproduces without extensions: Yes

This is as designed for now. SVGs are blocked from loading. The errors are harmless and will be gone soon.


Installation Error

As per the README file, we need to have the "MethyLasso.tar.gz" &  "conda_env.yml" files , but I couldn't find the files in the github repository.
$ ls
DESCRIPTION  input  LICENSE  man  MethyLasso.R  NAMESPACE  R  README.md  src
$ R CMD INSTALL --preclean MethyLasso
Warning: invalid package ‘MethyLasso’
Error: ERROR: no packages specified
Environment Details:
R version : 4.3.0 (2023-04-21)
OS : RHEL7.9
Python : 3.10.10
Kindly suggest the way to install MethyLasso.
Thanks.

Hello ,
Thank you for bringing this to my attention. I apologize for any inconvenience you've experienced regarding the missing file. I have taken the necessary steps to resolve this issue.
I have now added the "conda_env.yml" file to the GitHub repository. You should be able to use it to create the Conda environment required for MethyLasso.
Delphine

Dear secabhk001,
For your information, if you were using bismark output files as input to MethyLasso, we just fixed an issue in MethyLasso.R to take the correct columns as input so this file should be replaced or options "--mC 5 --uC 6" specified.
I'm very sorry for that.
Best,
Anaïs


pretrain model for test

Thank you very much for this good realization of PercepNet, Can you upload your pretrained model?

Hi, @dtx525942103
now I'm trying to training with small dev dataset and verifying this enhancement process is work or not before upload pretrained model to here
Stay tune Thanks

look forward to

Hi! Looking forward for the model as well! thank you for your implementation!

+1

@jzi040941
Hi, Can you upload your pretrained model?

Hi! Looking forward for the model too :) Thanks for your hard work.

For training you could consider the Mozilla Common Voice and UrbanSound8K datasets too.
Also looking forward for the model too :) Thanks for your hard work.


presubmit refuses to start when CLA isn't happy

for instance on #306 right now:

not sure if same issue but
GitHub PR Polling Log

View as plain text
Running GitHub Pull Request trigger check for May 22, 2017 10:16:01 PM on GitHubRepositoryName[host=github.com,username=istio,repository=istio.github.io]
GitHub rate limit before check: GHRateLimit{remaining=0, limit=5000, resetDate=Mon May 22 22:24:02 UTC 2017}
ERROR: Can't end trigger check
Finished GitHub Pull Request trigger check for GitHubRepositoryName[host=github.com,username=istio,repository=istio.github.io] at May 22, 2017 10:16:01 PM. Duration: 100ms

it refuses to build:
Skipping [#306 167 index design updates] because of user restriction (user - GHUser@2121c72e[login=ryangrahamnc,location=,blog=,email=,name=,company=,followers=0,following=0,url=https://api.github.com/users/ryangrahamnc,id=1237156])

THis has nothing to do with CLA. That user is not part of the org and that s why we are not testing.

Although for some reason, the plugin does not pick up your comments. I filed a bug for the plugin a while back but never got answer back.

pretty sure the user thing blocks everything
can we remove that user check ?

@sebastienvas this is really handicapping - can we fix it before changing the whole infra ?

We would need to fix the jenkins plugin. I am not familiar with Jenkins development. I don't think it worth the time.
https://github.com/KostyaSha/github-integration-plugin/blob/16922b98b9757e57646d8a51c3cc41c4b0545edc/github-pullrequest-plugin/src/main/java/org/jenkinsci/plugins/github/pullrequest/events/impl/GitHubPRCommentEvent.java#L88
Not convinced that this does the right thing:
https://github.com/kohsuke/github-api/blob/master/src/main/java/org/kohsuke/github/GHIssueComment.java#L72

This is not going to scale at all. We can't add every contributor to Istio org. Esp if we have folks providing small fixes here and there. What do the kube folks or other Jenkins users do?

The new infra will fix this. Can we please focus our energy on something else.

@sebastienvas can you please document the exact details of the workaround (where/how exactly does one add the person to the org...)

All you need to do is add the user as a Member of the istio org, by clicking here:
https://github.com/orgs/istio/people#invite_member_to_org

This is resolved with the Migration to Prow

can we get prow for istio.github.io ? we're going to get a bunch of PRs and if the tests aren't run, we'll break the site

Let's not use the bot for the docs site. The amount of churn is huge.
Waiting for N /retests and /LGTMs is going to slow us down terribly.
On Mon, Sep 18, 2017 at 9:56 PM Laurent Demailly<EMAIL_ADDRESS>wrote:

Reopened #308 https://github.com/istio/istio.github.io/issues/308.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio.github.io/issues/308#event-1254581042,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AH0qd7P9AfjFrFNsSnQwZ6lcYA8IogXHks5sjx9pgaJpZM4Ni9Mj
.

--
~shriram

Please open a different request for this:
FYI - https://github.com/istio/test-infra/tree/master/prow#creating-a-job-on-your-repo

@rshriram it's either you implement a bot that works better and allow us to type /ok-to-test on PRs submitted from outside the org or we use the existing bot that works fine (and doesn't have /restest issues, the restest are because the tests were broken, not because of the bot)
also if you could consider finally starting to trim your email replies that'd be awesome/less churn

actually I did a quick fix. If you can add the ok-to-test label to the PR it should start, but you ll have to do it even if you are part of the org ? Does it work ? I ll try to migrate it to Prow quick in the meantime.

I manually pushed the last PR so I can't test right now but it sounds great (so if it'd run automatically like today for existing contributors that'd be a plus; I am worried people will just push broken stuff like it's been happening historically and if the current job doesn't trigger I think it may happen "oh I didn't know about /ok-to-test so I merged...")

Yes I can also remove the ok-to-test for this repo.

I removed it so it should be fine, if someone kills jenkins I won't resurrect it ;)

I am gonna close this. I ll do the migration as part of https://github.com/istio/istio.github.io/issues/466

seems to be working for existing contributors: https://github.com/istio/istio.github.io/pull/468

thanks!


[Request] Lines in DOM should be ordered by line number

Hello
This is a super niche request for a hack I'm trying to implement, but thought I would ask anyway.
Problem:
Can only draw decorations on characters in a line
What I want:
Draw decoration on an empty line
Why:

Because my custom indent lines have holes in them.
Solution:
Instead of decorating every line, I can just decorate the last line, inject css and stretch it upwards
borderStyle += "; transform-origin: bottom; transform: scaleY(" + scale + ");"

However this only works for empty lines that were already in the document when it was opened.
If I now add a new empty line:

Fiddlesticks! What is wrong?

The new line I just added is appended to the end of the dom, so the DOM order doesn't match the logical line number order, and I can't stretch my decoration over it.
Request:
Either add a way to decorate empty lines, or make DOM view-lines logically ordered.
Thanks for listening!

I can just inject  z-index:1000;


feat(bindNodeCallback): remove resultSelector

Removes the optional result selector to simplify the API

BREAKING CHANGE: resultSelector removed, use map instead: bindNodeCallback(fn1, fn2)() becomes bindNodeCallback(fn1)().pipe(map(fn2))

Coverage decreased (-0.005%) to 97.549% when pulling 26e6e5c59d1010fd2dacd4b6bf5fcfc65bae29eb on benlesh:remove-resultSelector-from-bindNodeCallback into 0a3a04a1532fff84407b4bceb86d19f2e9ef05af on ReactiveX:master.


Wrong Tilt position when pressing My function through TaHoma

Hardware
ESP32
Firmware version
v2.4.3
Application version
v2.4.4
What happened? What did you expect to happen?
I have an integrated tilting blind.
I have configured My favourite position to be tilt of 50%
When I press my in the virtual remote or in my physical remote ESPSomfy correctly sets tilting to 50%
I also have TaHoma integration, which is also linked as a remote to ESPSomfy
When I press My function in TaHoma ESPSomfy always incorrectly assumes that tilting is now 97% even though my blinds actually tilt to 50%.
I looked at the logs of the transmitter and noticed an interesting difference of what happens when I press My on my physical remote vs TaHoma.
When I press My on my physical remote it registers 2 times My command with 80-S bits.
When I press My on my TaHoma remote for some reason it registers 2 times My command with 56-S bits and 1 Favourite command with 80-S bits. (see attached image, the bottom 2 commands are from physical remote, top 3 are from TaHoma)
I assume this different behaviour of My on a physical remote and My on TaHoma is what causing ESPSomfy to set tilting value to incorrect 97%.
Also another peculiarity I noticed is that if I keep pressing My on TaHoma then my blinds won't move as they are already in my favourite position after pressing it the first time, but ESPSomfy continues reducing tilt by 3% each time I press My on TaHoma.

How to reproduce it (step by step)
Press My on Somfy TaHoma and it will reduce tilt by 3% each time it is pressed instead of just setting it to the right value of tilt and then not change regardless how many times I keep pressing My in TaHoma.

Logs
No response

Also another peculiarity I noticed is that if I keep pressing My on TaHoma then my blinds won't move as they are already in my favourite position after pressing it the first time, but ESPSomfy continues reducing tilt by 3% each time I press My on TaHoma.

The first 3 frames look like they are from the Tahoma  are the last two from a remote?  It looks like the Tahoma sends a my command to get the ball rolling in 56-bits then follows up with a favorite command for any 80 bit motors.  Can you capture a few of the my commands that move the ESPSomfy RTS device ~3% and paste that output here is a code block?

I have attached a few images.
Step 1 is how my blind looks like when I close it.
Step 2 is how it looks like after I press My on TaHoma. This time it got to 94%, but it should have been 50%. Blind itself moves correctly to 50% tilt.
Step 3 is how it looks like after I press My on TaHoma again. This time it got to 92%. Blind itself correctly didn’t move at all.
And so on if I keep pressing my the blind won’t move after it took My position, while ESPSomfy will keep reducing tilt each time I press My button in TaHoma. Again, this behaviour is only when using My in TaHoma. It works correctly when using My button on a physical remote.
Attached is alos a screenshot of pressing My in Tahoma 3 times. Is it what you were after?
￼￼￼￼

On 8 Jun 2024, at 00:15, rstrouse @.***> wrote:
Also another peculiarity I noticed is that if I keep pressing My on TaHoma then my blinds won't move as they are already in my favourite position after pressing it the first time, but ESPSomfy continues reducing tilt by 3% each time I press My on TaHoma.
The first 3 frames look like they are from the Tahoma are the last two from a remote? It looks like the Tahoma sends a my command to get the ball rolling in 56-bits then follows up with a favorite command for any 80 bit motors. Can you capture a few of the my commands that move the ESPSomfy RTS device ~3% and paste that output here is a code block?
—
Reply to this email directly, view it on GitHub https://github.com/rstrouse/ESPSomfy-RTS/issues/393#issuecomment-2155641953, or unsubscribe https://github.com/notifications/unsubscribe-auth/AD2QG7T2UCFBYGT7AZIET7TZGIWGJAVCNFSM6AAAAABI7LDPYOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJVGY2DCOJVGM.
You are receiving this because you authored the thread.

Yes, you’re right. First 3 frames are from tahoma, bottom 2 are from remote. As you can see both send different frames when pressing My button.

On 8 Jun 2024, at 00:15, rstrouse @.***> wrote:
Also another peculiarity I noticed is that if I keep pressing My on TaHoma then my blinds won't move as they are already in my favourite position after pressing it the first time, but ESPSomfy continues reducing tilt by 3% each time I press My on TaHoma.
The first 3 frames look like they are from the Tahoma are the last two from a remote? It looks like the Tahoma sends a my command to get the ball rolling in 56-bits then follows up with a favorite command for any 80 bit motors. Can you capture a few of the my commands that move the ESPSomfy RTS device ~3% and paste that output here is a code block?
—
Reply to this email directly, view it on GitHub https://github.com/rstrouse/ESPSomfy-RTS/issues/393#issuecomment-2155641953, or unsubscribe https://github.com/notifications/unsubscribe-auth/AD2QG7T2UCFBYGT7AZIET7TZGIWGJAVCNFSM6AAAAABI7LDPYOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJVGY2DCOJVGM.
You are receiving this because you authored the thread.

Unfortunately, your screenshots never made it.  Part of the discrepancy is because the Tahoma is trying to cover its bases.  It is first sending a Favorite on 80 bits then repeats it as a my command.  Notice that the rolling code did not change.  This is the method that they are using to allow for 80 and 56 bit motors.  I'll have to think about whether I want to adopt that hack or simply ignore my commands that follow a favorite.
I can't imagine that doesn't cause problems with some motors.  Perhaps stuff like this is why Tahoma is not well liked.
I do want a copy of the log when using only the Tahoma.  Not a screenshot but click the copy button on the log and paste it into a reply.

Got it. Here you go. I pressed My 3 times on Tahoma:
[{"encKey": 196,
"address": 6443519,
"rcode": 2597,
"command": "Favorite",
"rssi": -86,
"bits": 80,
"proto": 0,
"valid": true,
"sync": 24,
"pulses": [2015,2497,2480,2520,2482,2509,2489,2506,2484,2526,2482,2505,2508,2464,2557,2462,2500,2504,2503,2517,2474,2505,2498,2514,4805,1278,629,653,1274,632,657,631,625,1294,1282,641,630,1276,657,629,1279,1273,1285,649,620,659,633,636,636,1298,633,635,1284,1279,653,626,1276,1282,1286,1272,676,603,656,643,620,658,634,652,623,648,625,658,633,635,647,651,1255,650,648,1282,632,652,624,649,1277,1279,644,631,633,658,1271,653,629,1287,630,649,1276,653,624,648,624,658,632,1272,647,634,1285,646,647,1261,632,646,646,632,1283,646,645,655,607,653,651,1274,1281,639,646,624,653,631,642,1299,1255,1291,645,633,1279,638,648,1275,1286,647,623,1285,633,635,1299,1262,27,660,624],
"time": "2024-06-08T01:48:32.831+0200"
},
{"encKey": 196,
"address": 6443519,
"rcode": 2597,
"command": "My",
"rssi": -83,
"bits": 56,
"proto": 0,
"valid": true,
"sync": 11,
"pulses": [645,2936,1397,2454,2497,2471,2526,2502,2501,2488,2502,2488,2523,2493,4802,1280,632,650,1274,655,631,644,634,1273,1281,647,645,1283,633,647,1271,1289,1261,649,651,631,631,644,646,1287,664,595,1294,1275,647,628,1303,1277,1276,1283,623,647,626,659,636,647,621,654,630,643,651,648,623,637,656,635,1276,632,656,1269,644,631,632,653,1270,1305,634,639,644,629,1275,649,619,1307,632,645,1273,656,609,656,634,648,674,1240,658,630,1272,634,659,1248,673,635],
"time": "2024-06-08T01:48:32.944+0200"
},
{"encKey": 196,
"address": 6443519,
"rcode": 2597,
"command": "My",
"rssi": -83,
"bits": 56,
"proto": 0,
"valid": true,
"sync": 11,
"pulses": [663,1271,632,649,1269,1299,633,632,1287,1283,1270,630,649,670,604,652,2967,1335,2482,2486,2517,2477,2503,2503,2501,2502,2496,2497,2526,4777,1299,631,653,1276,632,630,656,628,1297,1254,649,646,1276,634,649,1268,1288,1282,646,625,662,633,648,621,1282,634,649,1296,1260,654,647,1276,1283,1275,1280,634,615,647,655,632,657,630,647,622,658,633,653,623,651,622,642,1295,628,654,1287,625,648,626,662,1258,1297,628,642,649,622,1300,636,628,1303,627,632,1287,647,624,634,657,637,650,1273,631,643,1270,659,618,1294,645,633],
"time": "2024-06-08T01:48:33.074+0200"
},
{"encKey": 193,
"address": 6443519,
"rcode": 2598,
"command": "Favorite",
"rssi": -85,
"bits": 80,
"proto": 0,
"valid": true,
"sync": 24,
"pulses": [2048,2487,2457,2523,2475,2502,2501,2514,2499,2494,2499,2519,2475,2499,2501,2508,2505,2489,2497,2506,2499,2497,2505,2519,4786,1298,624,655,1260,645,646,634,633,639,653,646,624,1294,631,629,647,657,1257,1294,1270,646,623,1301,658,625,642,627,626,662,1259,1290,631,662,1280,626,654,1263,634,646,651,634,632,650,648,628,653,633,633,647,645,631,630,644,648,646,1275,650,644,1278,631,650,618,649,1276,1290,646,634,635,649,1270,634,656,1267,645,653,1280,622,675,626,632,631,631,1301,625,636,1284,647,621,1307,635,646,620,637,1281,648,646,631,656,621,646,1275,1283,638,647,650,629,658,631,1290,1249,1308,645,634,1253,650,647,1282,1281,648,620,1287,631,646,1272,1284,644,647],
"time": "2024-06-08T01:48:37.778+0200"
},
{"encKey": 193,
"address": 6443519,
"rcode": 2598,
"command": "My",
"rssi": -84,
"bits": 56,
"proto": 0,
"valid": true,
"sync": 11,
"pulses": [624,3023,1277,2522,2460,2502,2502,2495,2501,2507,2494,2508,2499,2519,4803,1254,656,625,1296,632,630,662,630,646,622,657,631,1280,622,656,631,652,1295,1237,1309,645,646,1260,632,649,647,632,658,627,1281,1279,631,646,1278,659,632,1264,646,654,654,607,655,647,621,656,634,651,624,646,624,661,634,636,646,650,1252,662,622,1303,632,644,622,625,1297,1301,619,659,618,642,1297,605,677,1273,621,657,1285,647,620,633,644,650,622,1304,636,634,1281,654,629,1288,633,648],
"time": "2024-06-08T01:48:37.924+0200"
},
{"encKey": 193,
"address": 6443519,
"rcode": 2598,
"command": "My",
"rssi": -93,
"bits": 56,
"proto": 0,
"valid": true,
"sync": 11,
"pulses": [633,1285,649,629,1276,1285,647,622,1289,1277,1300,630,628,642,647,628,2972,1305,2521,2498,2492,2497,2498,2497,2505,2498,2517,2485,2520,4795,1280,620,658,1267,641,639,653,643,630,635,646,633,1278,650,655,618,632,1289,1291,1281,622,648,1277,639,658,624,651,622,658,1258,1304,631,654,1256,648,626,1314,628,660,615,625,661,644,621,663,621,635,631,648,647,659,636,621,656,671,1228,645,652,1271,632,652,655,653,1234,1300,657,610,657,635,1278,653,645,1274,624,659,1265,656,627,668,603,659,634,1271,647,636,1282,651,627,1272,642,647],
"time": "2024-06-08T01:48:38.171+0200"
},
{"encKey": 136,
"address": 6443519,
"rcode": 2599,
"command": "Favorite",
"rssi": -84,
"bits": 80,
"proto": 0,
"valid": true,
"sync": 24,
"pulses": [2012,2511,2449,2521,2488,2500,2511,2506,2482,2498,2505,2508,2502,2492,2503,2505,2507,2475,2504,2512,2499,2491,2499,2498,4809,1271,1282,647,647,630,630,1307,1272,635,632,639,649,1273,1282,643,644,1284,1284,1271,630,643,1276,1283,1286,648,619,1289,630,668,620,634,1284,647,645,1279,1285,1273,630,642,644,648,1274,1269,644,658,633,628,652,647,1274,1269,645,633,1283,644,645,1285,636,634,1298,632,632,637,627,1298,1306,623,645,625,630,642,644,1278,652,627,644,649,1277,1270,645,632,656,644,621,649,1276,643,644,627,649,644,627,1297,1279,622,649,653,628,635,651,1274,1277,1277,646,633,1283,647,646,1286,1259,646,648,1288,630,646,1273,1288,625,648],
"time": "2024-06-08T01:48:40.974+0200"
},
{"encKey": 136,
"address": 6443519,
"rcode": 2599,
"command": "My",
"rssi": -84,
"bits": 56,
"proto": 0,
"valid": true,
"sync": 11,
"pulses": [624,2966,1328,2501,2483,2528,2500,2486,2506,2486,2504,2498,2496,2522,4806,1281,1251,644,651,624,650,1292,1281,628,653,633,632,1288,1273,659,628,1272,1303,1273,618,658,1258,1299,1277,646,633,1269,644,644,643,652,1256,646,646,1279,1285,1276,627,658,636,639,1272,1278,652,645,646,610,656,635,1279,1280,658,623,1270,660,634,1294,621,654,1256,648,644,651,629,1294,1271,633,631,644,646,654,630,1289,623,650,626,662,1281,1275,630,633,655,646],
"time": "2024-06-08T01:48:41.081+0200"
},
{"encKey": 136,
"address": 6443519,
"rcode": 2599,
"command": "My",
"rssi": -83,
"bits": 56,
"proto": 0,
"valid": true,
"sync": 11,
"pulses": [629,1287,619,657,1284,1258,687,589,1295,1285,1276,638,681,602,642,627,3455,833,2498,2488,2522,2485,2500,2505,2496,2508,2504,2504,2498,4779,1305,1260,646,647,633,632,1293,1272,659,628,645,621,1284,1282,648,625,1289,1274,1282,633,661,1262,1306,1259,644,647,1283,626,646,646,635,1285,648,622,1289,1284,1272,629,644,647,646,1277,1280,646,629,631,644,651,646,1274,1274,644,634,1281,635,647,1281,633,651,1273,659,631,645,625,1273,1283,649,648,629,630,653,628,1301,630,644,629,645,1299,1281,620,652,653,627],
"time": "2024-06-08T01:48:41.230+0200"
}]

On 8 Jun 2024, at 01:30, rstrouse @.***> wrote:
Unfortunately, your screenshots never made it. Part of the discrepancy is because the Tahoma is trying to cover its bases. It is first sending a Favorite on 80 bits then repeats it as a my command. Notice that the rolling code did not change. This is the method that they are using to allow for 80 and 56 bit motors. I'll have to think about whether I want to adopt that hack or simply ignore my commands that follow a favorite.
I can't imagine that doesn't cause problems with some motors. Perhaps stuff like this is why Tahoma is not well liked.
I do want a copy of the log when using only the Tahoma. Not a screenshot but click the copy button on the log and paste it into a reply.
—
Reply to this email directly, view it on GitHub https://github.com/rstrouse/ESPSomfy-RTS/issues/393#issuecomment-2155693051, or unsubscribe https://github.com/notifications/unsubscribe-auth/AD2QG7UEW4VBIAM36B7JQVLZGI7BHAVCNFSM6AAAAABI7LDPYOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJVGY4TGMBVGE.
You are receiving this because you authored the thread.

Hopefully these images make it now:

Ok so I will process the secondary my command that is defined as repeated to the original favorite as a synonym for the original
command and that should do it.

Also another peculiarity I noticed is that if I keep pressing My on TaHoma then my blinds won't move as they are already in my favourite position after pressing it the first time, but ESPSomfy continues reducing tilt by 3% each time I press My on TaHoma.

I think this is because it is getting an indication that it should move to the my position then about 240ms later it is getting a my but it looks at this as a stop command because movement has already started from the original favorite command.  I guess because the TaHoma doesn't know whether the motor is in transit it has to send all the commands.  The bad part of that is that this has the effect of making the stop command not work.

Install v2.2.4 pre-release using the GitHub update button.  I think I have it all working.   I don’t have a TaHoma box so I need to rely on you.

In Tahoma app, stop is a separate button to my. And it makes Tahoma send a STOP command to stop the motor and not My command. Here is a copy of the commands when I press My and then follow by a Stop press. And Stop does seem to stop motor from travelling to My favourite position when it is in transit:
[{"encKey": 178,
"address": 6443519,
"rcode": 2616,
"command": "Favorite",
"rssi": -82,
"bits": 80,
"proto": 0,
"valid": true,
"sync": 24,
"pulses": [2019,2487,2501,2492,2507,2476,2505,2511,2510,2475,2513,2501,2488,2501,2512,2501,2513,2475,2506,2496,2506,2505,2508,2496,4783,1281,1286,1271,652,632,1284,648,624,1286,1302,1258,1286,1276,1277,1287,1296,1261,652,621,647,636,1288,1273,1278,647,645,626,652,636,633,1278,648,638,1288,623,667,1261,657,620,1296,643,629,1272,652,637,631,647,645,633,631,628,676,621,1297,1271,640,633,658,638,1280,1276,1286,1272,1277,1290,1272,637,656,1277,1272,1265,1302,1281,1263,1296,629,637,1288,649,622,637,660,624,648,1280,1286,620,649,629,657,644,623,1277,1282,1296,624,659,1282,620,647,1284,1270,655,629,1281,649,627,1278,1297,645,636],
"time": "2024-06-08T07:37:17.593+0200"
},
{"encKey": 178,
"address": 6443519,
"rcode": 2616,
"command": "My",
"rssi": -82,
"bits": 56,
"proto": 0,
"valid": true,
"sync": 11,
"pulses": [633,2935,1353,2496,2485,2511,2497,2489,2508,2505,2510,2486,2505,2487,4801,1282,1287,1274,653,637,1284,620,648,1288,1281,1279,1285,1272,1276,1280,1297,1270,627,644,647,634,1287,1272,1279,652,647,626,651,632,632,1271,649,637,1286,645,645,1285,629,646,1271,656,630,1273,652,635,630,647,644,632,632,665,626,645,1271,1288,645,623,654,636,1284,1267,1282,1271,1299,1269,1297,633,642,1297,1255,1254,1297,1289,1302,1257],
"time": "2024-06-08T07:37:17.593+0200"
},
{"encKey": 178,
"address": 6443519,
"rcode": 2616,
"command": "My",
"rssi": -82,
"bits": 56,
"proto": 0,
"valid": true,
"sync": 11,
"pulses": [655,1304,602,653,1268,1277,655,630,1287,1273,1285,657,622,645,632,657,2914,1346,2493,2533,2467,2511,2499,2512,2499,2483,2516,2509,2494,4783,1289,1284,1273,658,611,1281,648,652,1267,1275,1280,1311,1249,1278,1291,1293,1263,652,623,645,634,1286,1273,1279,649,644,652,628,633,660,1273,625,637,1288,645,646,1284,629,646,1270,643,643,1273,653,617,667,624,651,607,657,645,644,633,1286,1281,647,635,633,651,1273,1284,1270,1300,1261,1296,1275,626,668,1250,1284,1270,1298,1266,1296,1269],
"time": "2024-06-08T07:37:17.727+0200"
},
{"encKey": 167,
"address": 6443519,
"rcode": 2617,
"command": "Stop",
"rssi": -82,
"bits": 80,
"proto": 0,
"valid": true,
"sync": 24,
"pulses": [2044,2461,2513,2503,2488,2500,2510,2499,2506,2492,2506,2491,2509,2474,2530,2478,2507,2501,2503,2497,2507,2480,2524,2477,4808,1280,1284,1268,1280,651,647,1277,633,644,646,626,657,629,1282,1274,658,639,628,646,1272,1286,646,625,652,636,1288,1272,631,645,1291,628,655,611,655,1272,652,632,1282,648,625,660,633,1275,1274,637,654,621,670,1259,664,634,621,654,1280,1272,1299,1258,1298,1258,1314,1257,652,629,653,623,1298,1257,643,653,1283,1261,1296,636,634,638,645,1278,1284,619,670,1260,1293,629,650,632,657,620,644,1287,1283,621,647,634,658,618,668,1255,1312,1250,652,635,634,647,644,633,657,637,629,646,645,634,634,653,624,648,649,637,634,622,1296],
"time": "2024-06-08T07:37:20.458+0200"
},
{"encKey": 167,
"address": 6443519,
"rcode": 2617,
"command": "My",
"rssi": -83,
"bits": 56,
"proto": 0,
"valid": true,
"sync": 11,
"pulses": [3629,1305,2476,2508,2500,2496,2482,2527,2499,2498,2501,2497,2494,4802,1281,1286,1270,1280,650,648,1282,632,645,643,625,652,637,1284,1270,656,616,643,645,1274,1294,646,611,657,626,24,1292,1286,635,644,1269,632,662,636,646,1278,634,651,1269,632,657,629,651,1270,1282,636,646,626,656,1285,622,648,652,617,1312,1253,1284,1272,1300,1257,1297,1289,629,644,644,635,1286,1271,648,636,1285,1275,1281,646,645,630,629,1289,1274,634,657],
"time": "2024-06-08T07:37:20.458+0200"
},
{"encKey": 167,
"address": 6443519,
"rcode": 2617,
"command": "My",
"rssi": -82,
"bits": 56,
"proto": 0,
"valid": true,
"sync": 11,
"pulses": [648,631,658,630,636,645,647,639,632,643,644,626,1304,627,636,1275,1310,3586,1316,2485,2520,2493,2506,2485,2512,2500,2488,2499,2512,2500,4794,1286,1283,1277,1284,621,646,1289,634,635,646,628,653,633,1281,1274,657,628,643,649,1276,1281,644,630,631,643,1288,1307,632,623,1274,635,657,637,628,1297,628,644,1280,627,655,639,627,1294,1280,646,620,655,629,1282,647,627,654,634,1284,1279,1281,1274,1299,1264,1299,1259,638,647,644,631,1283,1290,646,634,1283,1272,1276,648,645,620,653,1284,1276,632,634],
"time": "2024-06-08T07:37:20.460+0200"
}]

On 8 Jun 2024, at 03:28, rstrouse @.***> wrote:
Ok so I will process the secondary my command that is defined as repeated to the original favorite as a synonym for the original
command and that should do it.
Also another peculiarity I noticed is that if I keep pressing My on TaHoma then my blinds won't move as they are already in my favourite position after pressing it the first time, but ESPSomfy continues reducing tilt by 3% each time I press My on TaHoma.
I think this is because it is getting an indication that it should move to the my position then about 240ms later it is getting a my but it looks at this as a stop command because movement has already started from the original favorite command. I guess because the TaHoma doesn't know whether the motor is in transit it has to send all the commands. The bad part of that is that this has the effect of making the stop command not work.

—
Reply to this email directly, view it on GitHub https://github.com/rstrouse/ESPSomfy-RTS/issues/393#issuecomment-2155744262, or unsubscribe https://github.com/notifications/unsubscribe-auth/AD2QG7SK44WMJDQQVCYLWG3ZGJM2DAVCNFSM6AAAAABI7LDPYOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJVG42DIMRWGI.
You are receiving this because you authored the thread.

I'm sorry I meant to tell you to install 2.4.4 pre-release not 2.2.4.   This should handle both cases.

Confirm, it is working correctly now.
Couple of additional questions:

I see that my physical remote always repeats each command twice. Should I setup ESPSomfy do that too, or if everything works well with 1 command no need?
I have integrated blinds. Often I need to move blinds to a particular location and keep them closed. Then later tilt. Right now there is only a command to move blinds to a location and then restore tilt that it had before starting the movement. Is there a way to also be able to move blinds to a particular location and leave them closed (i.e. do not restore previous tilt)?
Tilt function is not always consistent. Depending on whether blind was previously already tilted, or it was open, closed or moving it gets same % tilt to a slightly different position. Such impression means that I sometimes won’t turn the blinds correctly against the sun. Is it due to impression of the motor I have or is there a way to tune parameters in the ESPSomfy app to make it more precise?

On 8 Jun 2024, at 07:57, rstrouse @.***> wrote:
I'm sorry I meant to tell you to install 2.4.4 pre-release not 2.2.4. This should handle both cases.
—
Reply to this email directly, view it on GitHub https://github.com/rstrouse/ESPSomfy-RTS/issues/393#issuecomment-2155826036, or unsubscribe https://github.com/notifications/unsubscribe-auth/AD2QG7XVT7A3EIDK6I5GXC3ZGKMMBAVCNFSM6AAAAABI7LDPYOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJVHAZDMMBTGY.
You are receiving this because you authored the thread.

I see that my physical remote always repeats each command twice. Should I setup ESPSomfy do that too, or if everything works well with 1 command no need?

There is no need.  In fact your remote is actually trying really hard to only send one frame and if you work at it you can get it to send one without any repeats but our thumbs and the mechanical button are not fast enough.  Believe it or not the most common reason to need repeats is because the motors have a cooling off period while they are processing a frame that makes them unable to hear any other frames.   This is likely the reason TaHoma sends 1 80-bit and two 56-bit in a pattern.  Most motors won't hear the first My.

I have integrated blinds. Often I need to move blinds to a particular location and keep them closed. Then later tilt. Right now there is only a command to move blinds to a location and then restore tilt that it had before starting the movement. Is there a way to also be able to move blinds to a particular location and leave them closed (i.e. do not restore previous tilt)?

You can send the movement and tilt commands consecutively on an integrated tilt.

Tilt function is not always consistent. Depending on whether blind was previously already tilted, or it was open, closed or moving it gets same % tilt to a slightly different position. Such impression means that I sometimes won’t turn the blinds correctly against the sun. Is it due to imperfection of the motor I have or is there a way to tune parameters in the ESPSomfy app to make it more precise?

The integrated tilt mechanisms are all mechanical and I imagine that there could be some slop in the mechanism.  The motor only runs at one speed and for the integrated tilt these are typically balanced by pulling on either side of the slat mechanism so the load should be the same.  Tilt time is calculated down to the millisecond so do some tweaking but I believe the wider the slat the more accurate you can be.

In home assistant automation is there a command I can use to set position and tilt of the blind together? Right now I have to set position, then have some sort of time delay to wait until it gets to that position and then run a separate tilt command. This is not a very elegant way of doing it. You probably have a better way to set those 2 parameters together?

You do not need to wait between these commands.

Unfortunately I tried sending consecutive position and tilt commands and it doesn’t work. Second command seems to cancel the first if first hasn’t finished by the time second is run. This is the reason for questions 2 and 4. Is it another kind of bug? Or am I missing something?On 8 Jun 2024, at 16:37, rstrouse @.***> wrote:
I see that my physical remote always repeats each command twice. Should I setup ESPSomfy do that too, or if everything works well with 1 command no need?
There is no need.  In fact your remote is actually trying really hard to only send one frame and if you work at it you can get it to send one without any repeats but our thumbs and the mechanical button are not fast enough.  Believe it or not the most common reason to need repeats is because the motors have a cooling off period while they are processing a frame that makes them unable to hear any other frames.   This is likely the reason TaHoma sends 1 80-bit and two 56-bit in a pattern.  Most motors won't hear the first My.
I have integrated blinds. Often I need to move blinds to a particular location and keep them closed. Then later tilt. Right now there is only a command to move blinds to a location and then restore tilt that it had before starting the movement. Is there a way to also be able to move blinds to a particular location and leave them closed (i.e. do not restore previous tilt)?
You can send the movement and tilt commands consecutively on an integrated tilt.
Tilt function is not always consistent. Depending on whether blind was previously already tilted, or it was open, closed or moving it gets same % tilt to a slightly different position. Such impression means that I sometimes won’t turn the blinds correctly against the sun. Is it due to imperfection of the motor I have or is there a way to tune parameters in the ESPSomfy app to make it more precise?
The integrated tilt mechanisms are all mechanical and I imagine that there could be some slop in the mechanism.  The motor only runs at one speed and for the integrated tilt these are typically balanced by pulling on either side of the slat mechanism so the load should be the same.  Tilt time is calculated down to the millisecond so do some tweaking but I believe the wider the slat the more accurate you can be.
In home assistant automation is there a command I can use to set position and tilt of the blind together? Right now I have to set position, then have some sort of time delay to wait until it gets to that position and then run a separate tilt command. This is not a very elegant way of doing it. You probably have a better way to set those 2 parameters together?
You do not need to wait between these commands.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

Update. I did another test of sequential calling of setting position and then tilt and confirm all working now. Strange it didn’t work before, but all good now. Seems false alarm on my side. FYI I played a bit more with tilting and noticed that when I set tilt to 50% then it looks different if it is setting tilt after closing blinds or opening blinds (which direction it was running before setting the tilt). This led me to idea of trying to play with tilt time a bit more. My measured tilt time is consistently 4000ms. However, it is only after I set it to 5000ms that it seems that it sets tilt to roughly the same angle, regardless of which direction it was previously running to. On 8 Jun 2024, at 20:27, Elnar Hajiyev @.> wrote:Unfortunately I tried sending consecutive position and tilt commands and it doesn’t work. Second command seems to cancel the first if first hasn’t finished by the time second is run. This is the reason for questions 2 and 4. Is it another kind of bug? Or am I missing something?On 8 Jun 2024, at 16:37, rstrouse @.> wrote:
I see that my physical remote always repeats each command twice. Should I setup ESPSomfy do that too, or if everything works well with 1 command no need?
There is no need.  In fact your remote is actually trying really hard to only send one frame and if you work at it you can get it to send one without any repeats but our thumbs and the mechanical button are not fast enough.  Believe it or not the most common reason to need repeats is because the motors have a cooling off period while they are processing a frame that makes them unable to hear any other frames.   This is likely the reason TaHoma sends 1 80-bit and two 56-bit in a pattern.  Most motors won't hear the first My.
I have integrated blinds. Often I need to move blinds to a particular location and keep them closed. Then later tilt. Right now there is only a command to move blinds to a location and then restore tilt that it had before starting the movement. Is there a way to also be able to move blinds to a particular location and leave them closed (i.e. do not restore previous tilt)?
You can send the movement and tilt commands consecutively on an integrated tilt.
Tilt function is not always consistent. Depending on whether blind was previously already tilted, or it was open, closed or moving it gets same % tilt to a slightly different position. Such impression means that I sometimes won’t turn the blinds correctly against the sun. Is it due to imperfection of the motor I have or is there a way to tune parameters in the ESPSomfy app to make it more precise?
The integrated tilt mechanisms are all mechanical and I imagine that there could be some slop in the mechanism.  The motor only runs at one speed and for the integrated tilt these are typically balanced by pulling on either side of the slat mechanism so the load should be the same.  Tilt time is calculated down to the millisecond so do some tweaking but I believe the wider the slat the more accurate you can be.
In home assistant automation is there a command I can use to set position and tilt of the blind together? Right now I have to set position, then have some sort of time delay to wait until it gets to that position and then run a separate tilt command. This is not a very elegant way of doing it. You probably have a better way to set those 2 parameters together?
You do not need to wait between these commands.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

Awesome.  Glad we got it all worked out.

Thank you very much for quick help. Its working flawlessly. So grateful for your project. It is mind boggling why it is not a standard feature of Somfy. On 9 Jun 2024, at 16:57, rstrouse @.***> wrote:
Awesome.  Glad we got it all worked out.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

I am going to close this as I believe we have you all sorted out.