Default timestamp in CSV files should be Unix Time

currently after naarad processing, the timestamp is epoch time (e.g.,, 132455555), we should use unix time (e.g., 2014-03-02 22:11:11).
If we really want epoch time in some cases, we can use config file to specify.

This sounds reasonable to me so that CSV files are more readable. This will add some overhead on write as all timestamps need to be translated.
This will affect both the generation of CSV files and also must look into the JavaScript code that touches the download of the CSV file as that I think converts timestamps as well.

In naarad, every timestamp will translate into epoch time in naarad.utils.get_standardized_timestamp. We could change this function to use unix time instead of epoch time. But the trickiest thing is that plot library(e.g matplotlib) uses the csv file to plot graph and it only recognizes epoch time. It will trigger exception if the csv time series is not epoch time. Any advise for the fix?

The goal of the "filed issue" is to store Unix time in *.csv file (for easy human reading afterwards).
In naarad, the unix time needs to be translated to epoch time for plotting.

From: feng-tao<EMAIL_ADDRESS>Sent: Thursday, March 26, 2015 6:08 PM
To: linkedin/naarad
Cc: Zhenyun Zhuang
Subject: Re: [naarad] Default timestamp in CSV files should be Unix Time (#310)
In naarad, every timestamp will translate into epoch time in naarad.utils.get_standardized_timestamp. We could change this function to use unix time instead of epoch time. But the trickiest thing is that plot library(e.g matplotlib) uses the csv file to plot graph and it only recognizes epoch time. It will trigger exception if the csv time series is not epoch time. Any advise for the fix?
—
Reply to this email directly or view it on GitHubhttps://github.com/linkedin/naarad/issues/310#issuecomment-86779393.

Matplotlib can handle unix timestamps, do you have documentation when it cannot? I believe, I tried to just have the CSV files have the same timestamps as logs and it seemed to graph correctly. I can try to dig that up another time.
I think the biggest issue, the last time I looked at this, was that there are timezone details to deal with as well.

Figure out the issue. I just push the initial fix which works on my example sar configure file. So now the csv file will show unix time and graph is generated correctly. I dont think the time zone is an issue as it shows up correctly in my test. But I may be wrong.

BTW, the fix combines for both bug #277  and bug #310 . Do you think I need to separate them?

Push a second fix(#328) per Richard's comment


[Feature] Introduce ha flag for table materialisation and iceberg tables to allow users to control final location

Is this your first time submitting a feature request?

[X] I have searched the existing issues, and I could not find an existing issue for this feature

Describe the feature
The current behaviour for table_type=iceberg and materialization=table implements high availability by default, this means that a new table is created with a not final name in a unique location, then the final target table is renamed. As consequence of this implementation we need to force the user of using unique locations.

What if the user don't want to have high availability and specific locations to be fully in control of where the data is stored?

Adding the possibility to use the ha flag for iceberg table allow the user to be more in control.
Here the proposal - note only for iceberg tables, as they are the affected one:

ha=true -> follow the current implementation
ha=false -> drop the table and create the table to the final location - doing so we allow the user to use external_location, or data_naming: table, schema_table or whatever they want.

Describe alternatives you've considered
No response
Who will this benefit?
Users that want to control final iceberg table location in S3.
Are you interested in contributing this feature?
No response
Anything else?
The current behaviour for iceberg tables is set to "ha=true", maintain this behavior to avoid breaking changes for the users.

@amychen1776 this is a super relevant feature requested by quite some people.
We never managed to prioritize it, but I just wanted to flag it, and it's iceberg related, therefore you can add the iceberg flag.


Code review requested: add finishing touches for concurrent recipe execution

I did a little polishing for concurrent recipes, namely the audit details/summaries, some additional validation of thread names, etc. I also tested the work that leekirchhoff did regarding filesystem paths for different threads.
I've already acted on some code review feedback from smessier, so I nominate him as the reviewer for the rest of these changes.

needs some fixes


Passing pipeline parameters as yaml config

Describe changes
Add ability to pass in pipeline params as yaml config:
parameters:
  environment: production

Also added a RuntimeError for the cases when runtime config conflicts with YAML config (both steps and pipeline params) - @schustmi please confirm that this is acceptable or shall I revert to config-dominant silent mode.
Docs: https://app.gitbook.com/o/-MCl1Hlw9oU4xibZ-ymf/s/9oLgDi1mkUbwQiTmrEit/user-guide/advanced-guide/pipelining-features/configure-steps-pipelines#parameters-for-your-steps
BREAKING CHANGES

What passed silently before now throws an error (step/pipeline params configured in file and code differently)

# config.yaml
parameters:
    some_param: 24

steps:
  my_step:
    parameters:
      input_2: 42

# run.py
@step
def my_step(input_1: int, input_2: int) -> None:
    pass

@pipeline
def my_pipeline(some_param: int):
    # here an error will be raised since `input_2` is
    # `42` in config, but `43` was provided in the code
    my_step(input_1=42, input_2=43)

if __name__=="__main__":
    # here an error will be raised since `some_param` is
    # `24` in config, but `23` was provided in the code
    my_pipeline(23)

Pre-requisites
Please ensure you have done the following:

[x] I have read the CONTRIBUTING.md document.
[ ] If my change requires a change to docs, I have updated the documentation accordingly.
[ ] If I have added an integration, I have updated the integrations table and the corresponding website section.
[ ] I have added tests to cover my changes.
[x] I have based my new branch on develop and the open PR is targeting develop. If your branch wasn't based on develop read Contribution guide on rebasing branch to develop.

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Other (add details above)

@schustmi , these changes clash a bit with what you created in https://github.com/zenml-io/zenml/pull/1638.
Can I have your perspective on this? I made an error to be raised if a user provides confusing configurations (step input is set in code and config), but before config, it just dominated it. WDYT, shall I revert to the old behavior or update the test case instead?

@bcdurak @schustmi can you have a look?


git: add (edit) creating blank "GIT-ADD: notes", fails to apply.

After I save a file with changes, when I do git: add (edit) the "GIT-ADD: notes" tab comes up blank and SUPER-Enter results in the following console entry

/usr/bin/git apply --cached - failed with following output:
fatal: unrecognized input

I used to get a diff and I could apply it.

Here is log output:
[{
    command: [
        "status",
        "-b",
        "--porcelain"
    ],
    type: "git",
    stdout: "## master...origin/master M "
    notes / NUC stuff.txt " M notes/scratch-bao.txt M notes/useful-commands.txt ",
    stderr: "",
    stdin: null
}, {
    command: [
        "status",
        "-b",
        "--porcelain"
    ],
    type: "git",
    stdout: "## master...origin/master M "
    notes / NUC stuff.txt " M notes/scratch-bao.txt M notes/useful-commands.txt ",
    stderr: "",
    stdin: null
}, {
    command: [
        "rev-parse",
        "--show-toplevel"
    ],
    type: "git",
    stdout: "/Users/Lownin/git-repos/notes ",
    stderr: "",
    stdin: null
}, {
    command: [
        "status",
        "-b",
        "--porcelain"
    ],
    type: "git",
    stdout: "## master...origin/master ",
    stderr: "",
    stdin: null
}, {
    command: [
        "status",
        "-b",
        "--porcelain"
    ],
    type: "git",
    stdout: "## master...origin/master ",
    stderr: "",
    stdin: null
}, {
    command: [
        "status",
        "-b",
        "--porcelain"
    ],
    type: "git",
    stdout: "## master...origin/master M "
    notes / NUC stuff.txt " M notes/scratch-bao.txt M notes/useful-commands.txt ",
    stderr: "",
    stdin: null
}, {
    command: [
        "status",
        "-b",
        "--porcelain"
    ],
    type: "git",
    stdout: "## master...origin/master M "
    notes / NUC stuff.txt " M notes/scratch-bao.txt M notes/useful-commands.txt ",
    stderr: "",
    stdin: null
}, {
    command: [
        "status",
        "-b",
        "--porcelain"
    ],
    type: "git",
    stdout: "## master...origin/master M "
    notes / NUC stuff.txt " M notes/scratch-bao.txt M notes/useful-commands.txt ",
    stderr: "",
    stdin: null
}, {
    command: [
        "rev-parse",
        "--show-toplevel"
    ],
    type: "git",
    stdout: "/Users/Lownin/git-repos/notes ",
    stderr: "",
    stdin: null
}, {
    command: [
        "status",
        "-b",
        "--porcelain"
    ],
    type: "git",
    stdout: "## master...origin/master ",
    stderr: "",
    stdin: null
}, {
    command: [
        "status",
        "-b",
        "--porcelain"
    ],
    type: "git",
    stdout: "## master...origin/master ",
    stderr: "",
    stdin: null
}, {
    command: [
        "status",
        "-b",
        "--porcelain"
    ],
    type: "git",
    stdout: "## master...origin/master M "
    notes / NUC stuff.txt " M notes/scratch-bao.txt M notes/useful-commands.txt ",
    stderr: "",
    stdin: null
}, {
    command: [
        "status",
        "-b",
        "--porcelain"
    ],
    type: "git",
    stdout: "## master...origin/master M "
    notes / NUC stuff.txt " M notes/scratch-bao.txt M notes/useful-commands.txt ",
    stderr: "",
    stdin: null
}, {
    command: [
        "rev-parse",
        "--show-toplevel"
    ],
    type: "git",
    stdout: "/Users/Lownin/git-repos/notes ",
    stderr: "",
    stdin: null
}, {
    command: [
        "diff",
        "--no-color"
    ],
    type: "git",
    stdout: "",
    stderr: "",
    stdin: null
}, {
    command: [
        "status",
        "-b",
        "--porcelain"
    ],
    type: "git",
    stdout: "## master...origin/master ",
    stderr: "",
    stdin: null
}, {
    command: [
        "status",
        "-b",
        "--porcelain"
    ],
    type: "git",
    stdout: "## master...origin/master ",
    stderr: "",
    stdin: null
}, {
    command: [
        "status",
        "-b",
        "--porcelain"
    ],
    type: "git",
    stdout: "## master...origin/master ",
    stderr: "",
    stdin: null
}, {
    command: [
        "status",
        "-b",
        "--porcelain"
    ],
    type: "git",
    stdout: "## master...origin/master ",
    stderr: "",
    stdin: null
}, {
    command: [
        "status",
        "-b",
        "--porcelain"
    ],
    type: "git",
    stdout: "## master...origin/master ",
    stderr: "",
    stdin: null
}, {
    command: [
        "apply",
        "--cached",
        "-"
    ],
    type: "git",
    stdout: "",
    stderr: "fatal: unrecognized input ",
    stdin: ""
}, {
    error: "'`/usr/bin/git apply --cached -` failed with following output:\n\nfatal: unrecognized input\n'",
    type: "error"
}, {
    command: [
        "status",
        "-b",
        "--porcelain"
    ],
    type: "git",
    stdout: "## master...origin/master M "
    notes / NUC stuff.txt " M notes/scratch-bao.txt M notes/useful-commands.txt ",
    stderr: "",
    stdin: null
}, {
    command: [
        "status",
        "-b",
        "--porcelain"
    ],
    type: "git",
    stdout: "## master...origin/master M "
    notes / NUC stuff.txt " M notes/scratch-bao.txt M notes/useful-commands.txt ",
    stderr: "",
    stdin: null
}, {
    command: [
        "rev-parse",
        "--show-toplevel"
    ],
    type: "git",
    stdout: "/Users/Lownin/git-repos/notes ",
    stderr: "",
    stdin: null
}, {
    command: [
        "status",
        "-b",
        "--porcelain"
    ],
    type: "git",
    stdout: "## master...origin/master ",
    stderr: "",
    stdin: null
}, {
    command: [
        "status",
        "-b",
        "--porcelain"
    ],
    type: "git",
    stdout: "## master...origin/master ",
    stderr: "",
    stdin: null
}]

I noticed the issue occurs on my Macs (three different Macs) but that it works fine on my Windows box.

Sorry to have let this issue sit @Lownin.  Busy prepping for a conference talk right now!  Can you also get me the version of OS, Sublime, and Git that you're using?  Thanks for the log dump!

No worries @divmain
OS: OS X 10.11.6
Sublime: Stable build 3114
Git: version 2.7.4 (Apple Git-66)

Hello. What should I do? I have the same bug

@Lownin 's screen cast gif shows the "notes" directory is missing the file. Was the file deleted prior to running the add command? Try saving the file first somewhere in the repo working dir and rerun the command.
@xahon if you have the same issue check the same. Otherwise please provide a log, a screencast, directory and files tree/listing and any other information you deem significant.

ping @Lownin @xahon

@Lownin,  @xahon, Could you to use git diff in stead of git: add (edit) you can submit hunk by hunk but not change it?

@asfaltboy I am saving the file inside the repo working directory before git add.  I have not deleted the files this is occurring with.
@stoivo git diff actually seems to properly generate a diff where git add does not.
FWIW, git add .  from the CLI always works fine.

@Lownin thanks. It seems when git diff --no-color is being run in /Users/Lownin/git-repos/notes  it returns no output, as if there were no changes yet (it does match the animated gif which shows that the file was not yet saved when running the command).
Unfortunately, we cannot reproduce this issue. Can you create a step-by-step guide to reproduce this? You can even push a simple repository to github with the specific files that cause the error.

Closing as stale.  Either the status dashboard or the diff views are the natural GitSavvy way of staging atm.


Clarification Needed on Few-Shot Experiment Settings for 16 Shots

Hello there,
Thank you for this work!
I am running the few-shot experiments, but I am a bit confused about the 16-shot setting. I checked the base-to-novel script, and its default is shot=16. However, for the few-shot benchmark, I noticed that the results for 16 shots are different from the base-to-novel.
Is there anything I am missing? I appreciate your help in advance!

And there is a minor qeustion hope you can help with: I found you did few-shots experiments on MaPLe as well, but I cannot find the config file for that. Could you kindly share the setting with me?

Very much appreciated your detailed reply!

For MaPLe few shot experiments, batch size 4, lr 0.0035 (same as basetonovel setting) and epochs 50 gives different accuracy numbers (average over 3 seeds) than what is reported in the Table. Could you please provide the proper parameters for MaPLe few shot learning to reproduce the results?


[CLOSED] Added Fund State to finder result metadata

 Issue by binaryberry
Wednesday 24 June 2015 at 15:18 GMT
Originally opened as https://github.com/alphagov/specialist-publisher/pull/505

...and displaying full label name for closing date, as
ESIF required more obvious distinction between open and closed
cases.
Pivotal ticket: https://www.pivotaltracker.com/story/show/96316390
cc @boffbowsh
Before:

After (ignore different formatting):

binaryberry included the following code: https://github.com/alphagov/specialist-publisher/pull/505/commits

 Comment by boffbowsh
Wednesday 24 June 2015 at 15:19 GMT

:+1: but won't merge as I paired on it.


lagging on ios

looks like it only happens for the first few drawables. once there are enough drawables the bug goes away
Can reproduce on iPhone 14 pro max simulator and iPad Mini (6th gen) simulator, and a real iPhone 14 Pro max device. Didn't try others but I believe it will give the same result.  BTW, the web version works fine.
https://github.com/omarhurani/flutter_painter/assets/126376236/5243ee73-b902-43ac-b505-ddb2496e268a

I was faced same issue in IOS 16.x with Flutter 3.10.x.
Solution:
Downgrade flutter version to 3.7 (Use flutter version 3.7). work fine in IOS 16.x

I reproduce in Flutter 3.13.0 and iOS 16.5.1

The problem seems to be linked to the new Flutter rendering engine, Impeller, which is now enabled by default on iOS.
Disabling it seems to fix the issue:
flutter run --no-enable-impeller

You can also disable it when deploying your app, in your app's Info.plist:
 <key>FLTEnableImpeller</key>
  <false />

Any other way yet?

Possible related issues:

https://github.com/flutter/flutter/issues/129235
https://github.com/flutter/flutter/issues/126212
https://github.com/flutter/engine/pull/46282


Behaviour when system time changes

I am a little bit confused about why you are internally using AlarmManager.RTC instead of AlarmManager.ELAPSED_REALTIME.
If am setting a job to be run in 1 min and the system time changes inbetween, than the job will run immediatly or even too late (depending on how the time changes), although this is not the expected behaviour if the wall clock time is irrelevant for the job.
Is this really intended?

I don't have a strong opinion. At least this allows our QA team to test curtain jobs and scenarios. I'm not sure if it makes sense to change that. Are there any other side effects?

Android's JobScheduler and your way of using AlarmManager are working differently.
Jobs scheduled with JobScheduler are not effected by system time changes (this is what can i see in sample test app).
So using this library the app will work differently on devices with different OS versions..

As noted in the documentation of SystemClock System.currentTimeMillis()
should only be used when correspondence with real-world dates and times is important, such as in a
calendar or alarm clock application.
elapsedRealtime() is the recommend basis for general purpose interval timing.

I think if the library provides an abstraction of different schedulers then it have to assure that
every concrete implementation works the same way.
The API with JobRequest says "run this job in x ms", but it does not say "run this job in x ms according to the wall clock".

Good explanation, I agree!

I'm sorry for the long delay. I finally had time to take a look at this.
If I switch to ELAPSED_REALTIME_WAKEUP, then for some reason exact jobs aren't exact anymore, although I only changed the constant and adjusted the time offset. The code looks like this:
        long triggerAtMillis = Common.getAverageDelayMs(request); // is 10_000L in my test
        if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.M) {
            alarmManager.setExactAndAllowWhileIdle(AlarmManager.ELAPSED_REALTIME_WAKEUP, triggerAtMillis, pendingIntent);
        } else if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.KITKAT) {
            alarmManager.setExact(AlarmManager.ELAPSED_REALTIME_WAKEUP, triggerAtMillis, pendingIntent);
        } else {
            alarmManager.set(AlarmManager.ELAPSED_REALTIME_WAKEUP, triggerAtMillis, pendingIntent);
        }

The log
08-20 15:56:10.136 17233-17233/com.evernote.android.job.demo D/JobProxy14: Scheduled alarm, request{id=6, tag=job_demo_tag, transient=false}, delay 00:00:10, exact true, reschedule count 0
08-20 15:56:15.196 17233-17416/com.evernote.android.job.demo D/PlatformAlarmServiceExact: Run job, request{id=6, tag=job_demo_tag, transient=false}, waited 00:00:05, delay 00:00:10

I can't explain why it's not working properly. Now I'm strongly considering not to change the current implementation as I don't want to introduce any bugs or regressions.
@misrakli Do you have an idea why that's the case?

I vaguely recall running into this before - ended up listening for time_changed and timezone_changed broadcasts and adjusting and rescheduling the alarms there.

@vRallev sorry for the late delay, I was on vacation.
I don't have any idea why the alarm should not treated as exact.
On which device/API did you run your tests?
Are you calculating the offset using SystemClock.ellapsedRealtime()?
Did you try different offsets for testing purpose?
Do you have a branch with this changes so I can have a look on the code and try to test it?
@strooooke Your way is only a workaround, the preferred way is I think that the library handles this the right way, see the discussion before.

@misrakli I've created the branch test/elapsed-realtime. I was using an API 26 emulator. I'm getting such logs:
09-11 09:21:04.236 10931-10931/com.evernote.android.job.demo D/JobProxy14: Scheduled alarm, request{id=2, tag=job_demo_tag, transient=false}, delay 00:00:10, exact true, reschedule count 0
09-11 09:21:09.245 10931-10997/com.evernote.android.job.demo D/PlatformAlarmServiceExact: Run job, request{id=2, tag=job_demo_tag, transient=false}, waited 00:00:05, delay 00:00:10

@misrakli I agree that the library should handle this; I was just trying to be helpful by relaying my on experience about the "for some unclear reason, alarms aren't exact anymore when switching to ELAPSED_REALTIME_WAKEUP" snag - maybe a bit too vague to be actually helpful, but as I said, I've seen this before.

@misrakli You can test 1.2.0-RC3.

Thanks for that quick response, I will give it a try.

Works as expected, changing the system time does not effect the alarms!
However, there is one little problem when logging the time we waited for the alarm (JobProxy#executeJobRequest). The calculation there is based on System.currentTimeMillis, which will return a wrong result when the system time changes while waiting for the alarm.
Do you think that we can use for scheduledAtthe elapsedRealtime? Actually I cannot evaluate the impact, for example the behaviour after reboot.
We can create a new issue for that if you want and close this one.

No, it's not necessary to create a separate issue. This log message should be fixed. I use it a lot to make sure that jobs are running as expected.

I have some concerns about using SystemClock.elapsedRealtime() for JobRequest#getScheduledAt field

It's part of public api. Clients could rely some logic on its value. Semver doen't allow backward incompatible changes in minor update 1.1 -> 1.2
If job is executed after device reboot long waited = SystemClock.elapsedRealtime() - request.getScheduledAt() can have negative value. Reboot is more common case than changing system time. So it won't be useful for debuging purposes.

@nesterov-n it was not a suggestion but a thougt, so this is your way of implementation :-)
I share your concerns. The point with the negative value struck me, too, that's why I asked cautious.
For a correct way of the calculation of the wating time I think we need a monotone time running we can rely on, which we don't have on the system AFAIK (only the elapsedRealtTime which is reseted after reboot).

So I finally had time to take look. Yes, the log message is misleading if the system time has changed, but it's really tricky to change the timestamps like you both explained. We need to live with the wrong log messages, but this was already the case with the JobScheduler on newer versions.
This ticket is implemented. But I'll keep it open until the final version 1.2.0 has been released.

@vRallev

but this was already the case with the JobScheduler on newer versions.

I didn't understand what you exactly mean with that. Is there already a known restriction?

No I just meant that even in the old versions of the library the log message could be wrong if you change the time and the JobScheduler is being used. Now we have the same behavior with the AlarmManager, what actually is good, because now it's consistent.

Ok, I see. Maybe we'll find a solution in future releases :-)

Version 1.2.0 has been released.


Error split tea: panic:invalid absolute path:

On macOS 13 arm64, zsh, node version v16.18.0 I get the following error when trying to run the example directly after installing (sh <(curl tea.xyz)). It told me that I have to report the bug, so here you go 😆 Do you have any hint on how I can debug this? Thanks!
❯ tea +gnu.org/wget wget -qO- tea.xyz/white-paper | tea +charm.sh/glow glow -
tea: installed: ~/.tea/openssl.org/v1.1.118
tea: installed: ~/.tea/gnu.org/wget/v1.21.3

panic: split tea. we’re sorry and we’ll fix it… but you have to report the bug!

    https://github.com/teaxyz/cli/issues/new?title=panic%3Ainvalid+absolute+path%3A+.

----------------------------------------------------->> attachment begin
Error: invalid absolute path: .
    at new Path (file:///opt/tea.xyz/src/v0.11.13/src/vendor/Path.ts:38:19)
    at find_tea (file:///opt/tea.xyz/src/v0.11.13/src/hooks/useShellEnv.ts:177:22)
    at useShellEnv (file:///opt/tea.xyz/src/v0.11.13/src/hooks/useShellEnv.ts:89:29)
    at exec (file:///opt/tea.xyz/src/v0.11.13/src/app.exec.ts:18:32)
    at async file:///opt/tea.xyz/src/v0.11.13/src/app.ts:29:9
<<------------------------------------------------------ attachment ends
tea: installed: ~/.tea/charm.sh/glow/v1.4.1

panic: split tea. we’re sorry and we’ll fix it… but you have to report the bug!

    https://github.com/teaxyz/cli/issues/new?title=panic%3Ainvalid+absolute+path%3A+.

----------------------------------------------------->> attachment begin
Error: invalid absolute path: .
    at new Path (file:///opt/tea.xyz/src/v0.11.13/src/vendor/Path.ts:38:19)
    at find_tea (file:///opt/tea.xyz/src/v0.11.13/src/hooks/useShellEnv.ts:177:22)
    at useShellEnv (file:///opt/tea.xyz/src/v0.11.13/src/hooks/useShellEnv.ts:89:29)
    at exec (file:///opt/tea.xyz/src/v0.11.13/src/app.exec.ts:18:32)
    at async file:///opt/tea.xyz/src/v0.11.13/src/app.ts:29:9
<<------------------------------------------------------ attachment ends

thank you! It appears you have . in your PATH. Correct?

 You can watch the build in @teaxyz/pantry.core/actions (not there yet). Once built you can update with sh <(curl tea.xyz)
Please close if fixed!

Indeed, I do! Working now, thanks!


Sensors unavailable

Good afternoon everyone,
I installed this custom component and created the client ID and client secret.
Although they were accepted by the integration, the only sensor that is not "unavailable" is the sensor "weight".
All other sensors remain unavailable.
Is there some kind of step that I am missing?
Thanks in advance.
Kind regards.

Hello
do you have an error in logs ?

Home Assistant Core
No issues found for search term 'polar'

Some additional information:
System Information

version
core-2023.7.3

installation_type
Home Assistant OS

dev
false

hassio
true

docker
true

user
root

virtualenv
false

python_version
3.11.4

os_name
Linux

os_version
6.1.34

arch
x86_64

timezone
Europe/Brussels

config_dir
/config

Home Assistant Community Store

GitHub API
ok

GitHub Content
ok

GitHub Web
ok

GitHub API Calls Remaining
4987

Installed Version
1.32.1

Stage
running

Available Repositories
1337

Downloaded Repositories
50

AccuWeather

can_reach_server
ok

remaining_requests
47

Home Assistant Cloud

logged_in
false

can_reach_cert_server
ok

can_reach_cloud_auth
ok

can_reach_cloud
ok

Home Assistant Supervisor

host_os
Home Assistant OS 10.3

update_channel
stable

supervisor_version
supervisor-2023.07.1

agent_version
1.5.1

docker_version
23.0.6

disk_total
97.7 GB

disk_used
20.8 GB

healthy
true

supported
true

board
ova

supervisor_api
ok

version_api
ok

installed_addons
Duck DNS (1.15.0), File editor (5.6.0), AppDaemon (0.13.3), Spotify Connect (0.12.4), Terminal & SSH (9.7.1), Home Assistant Google Drive Backup (0.111.1), Node-RED (14.4.2), AdGuard Home (4.8.12), Samba share (10.0.2), Studio Code Server (5.9.0), UniFi Network Application (2.7.0), Mosquitto broker (6.2.1)

Dashboards

dashboards
4

resources
16

views
21

mode
storage

Recorder

oldest_recorder_run
July 14, 2023 at 7:53 AM

current_recorder_run
July 23, 2023 at 4:32 PM

estimated_db_size
481.56 MiB

database_engine
sqlite

database_version
3.41.2

Spotify

api_endpoint_reachable
ok

can you enable debug logs and paste them

Dear Aohzan, I have found the error. Apparently the Polar watch did not sync correctly, but now it does and the issue is solved.


Add support for a terraform target

Adds initial support for terraform target. Integration design as a followup.
This will allow validation against a terraform plan's resource_changes directly.

@morgante @melinath
Doesn't look like I am able to add reviewers here, could you help to take a look.

Added @melinath and myself as reviewers.

looks like I was able to align to the original target testing framework... great call on code reuse ! This is way more elegant.

@morgante I think this is looking pretty good; would you be able to take a look?


remove reference to package that doesn't exist and swap in new one

Thanks for the patch. I think it shouldn't be logging at all. If it must, there is a better pattern to follow: https://dave.cheney.net/2017/01/23/the-package-level-logger-anti-pattern


In building develop branch, make -j16 is too demanding for an 8-core i9 CPU with a 16GB memory

https://github.com/EOSIO/eos/blob/44e216b484ad2fdf3367a8ff5bb9f604ff7048c2/scripts/.build_vars#L43
https://github.com/EOSIO/eos/blob/44e216b484ad2fdf3367a8ff5bb9f604ff7048c2/scripts/helpers/general.sh#L75
The current JOBS as in the make -j${JOBS} in the build script is determined by the code listed above.
In short, JOBS is the lower of

the number of logical CPU cores
the size of main memory in GB

However, in building the current develop branch, this configuration is too demanding, at least for my case. My Macbook Pro has an 8-core i9-9880H CPU with a 16GB memory, so it counts as having 16 logical cores, and thus JOBS=16.
Now the eosio_build.sh consistently freezes my Mac (for four times) when it arrives at
[ 77%] Building CXX object libraries/chain/CMakeFiles/eosio_chain.dir/webassembly/privileged.cpp.o

I am attaching a screenshot of the Activity Monitor at the freezing moment.

Workaround
The workaround is to terminate the build script before it comes to the compilation, go to the build folder, and manually run make -j8.
Suggestion
Consider changing
https://github.com/EOSIO/eos/blob/44e216b484ad2fdf3367a8ff5bb9f604ff7048c2/scripts/.build_vars#L43
into
 export CPU_CORES=$(grep -c ^processor /proc/cpuinfo 2>/dev/null || sysctl -n hw.physicalcpu)

which counts the number of physical CPU cores.
Or maybe other ways to avoid the freezing in the compilation.

I second this. The memory consumption is too much that ends up to freeze the compilation

Changes have been merged from the PRs referenced in this issue.

Changes have been merged from the PRs referenced in this issue.

Thanks for the fix. The developer branch is fine now, but it seems the release/2.1.x branch still experience the problem.


Reg DeleteAllItemsByPartitionKeyStreamAsync Preview feature in CosmosDB client

Is your feature request related to a problem? Please describe.
Yes. Currently DeleteAllItemsByPartitionKeyStreamAsync has been in preview mode for sometime. This requires us to maintain an update to cosmos DB client version separately (orignally we had used Aspire's internal version of cosmosDB client) and causing maintenance burden to track and update the cosmosDB client separately.
Describe the solution you'd like
To make the  DeleteAllItemsByPartitionKeyStreamAsync feature available in general release.
Describe alternatives you've considered
Currently maintaining explicit preview version overriding the version used by Aspire.

Additional context
Could you provide any update on when this feature will be generally available ?

@richagaur thoughs?

@arun-msx To clarify, the client SDKs do not define when service features are out of preview. We move the APIs out of the preview package when the service feature is Generally Available.

@richagaur can you please take a look?


fixed #467

Fixes Issue
Closes #467
Changes proposed
The leaderboard table is refined with UX in mind, letting the table columns Rank and Users be aligned at the start which increases the readability, the column Points is right aligned as it will be easier for users to compare the values with other users. Additionally, I added a hover effect on table row  which will increase readability. Padding in the x-axis in the table body is fixed.

Added two styled-components

LeaderboardTableHeaderPoints
LeaderboardTablePoints

Added hover effect on a table row
Added text-align to start for Rank and Users column and text-align to right for Points column
Padding on x-axis fixed for table body rows

Screenshots

Note to reviewers

Code of Conduct

[x] By submitting this pull request, I confirm I've read and complied with the CoC 🖖

Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[ ] My change requires changes to the documentation.
[ ] I have updated the documentation accordingly.
[x] All new and existing tests passed.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

You can also join our Discord community.
Feel free to check out other cool repositories of the Thecyberworld.
Join the Thecyberworld GitHub Organisation by raising an issue (you will be sent an invitation).

Hey
hey, rank and points part looks good but, users are not , because of crown
just a questions, can uu make design like this?
You can remove left crown from the username aswell
if u have any doubts or questions, feel free to ask
Thank yyou..

You mean to show trophy icon on left of the rank position right ?
I will work on this...

Hey
hey, rank and points part looks good but, users are not , because of crown
just a questions, can uu make design like this?
You can remove left crown from the username aswell
if u have any doubts or questions, feel free to ask
Thank yyou..

You mean to show trophy icon on left of the rank position right ?
I will work on this...

tropy is different crown is different, we can show golden one for 1, and same color for rest of those, and then there is no need for crown for top 1
and can you also make the same design that i have mentiond, here we just have to give padding, and margins with some light colors..

UI fixed with your guidelines as mentioned.
screenshots:
Leaderboard section:

CTF page:

If there is any other things needs to be changed, please mention it.

Thanks for contributing to Thecyberworld Community


DBZ-6652 Blog post about JMX signaling and notification

closes: https://issues.redhat.com/browse/DBZ-6652

Nice blog post @mfvitale ! I left a comment how to get rid off cryptic container IDs in the commands.

Thanks for the suggestions! Much better now.

Hi @mfvitale, I've made some suggestions for the text. I'd also recommend that we try and stick to one sentence per line as that's generally the style we've preferred to use in .adoc files, including our documentation.
Overall however, this was a great read.

Thank you @Naros for your precious suggestions!  Do you think it's mergiable?

Absolutely @mfvitale, feel free to merge when ready, it's good from my PoV.


Can picam-streamer be run on any other ARM board eg NVIDIA JETSON

Hi iizukanao, Are you planning to make picam-streamer work on any other ARM board capable of H.265 encoding, the draw back of using it on raspberry pi is it's video encoding H.264 only

Unfortunately, I don't have a plan for supporting devices other than Raspberry Pi.

Thankyou for your early reply, Raspberry pi is a very versatile  board, but
there are few limitations specially the video encoder only supports H.264,
so if we want to stream 4K at better FPS, then we are stuck.🙏🙏🙏🙏
On Mon, Aug 9, 2021 at 8:50 PM Nao Iizuka @.***> wrote:

Unfortunately, I don't have a plan for supporting devices other than
Raspberry Pi.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/iizukanao/picam-streamer/issues/48#issuecomment-895314208,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJFDX6UGFPIAOI7LTW5U53DT37W3ZANCNFSM5BZN6F6Q
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.

Understandable. Is there any alternative to Raspberry Pi that comes with H.265 hardware encoding?

Hi iizukanao, The  Odroid C2  and Rock64   support H.265
On Tue, Aug 10, 2021 at 7:28 AM Nao Iizuka @.***> wrote:

Understandable. Is there any alternative to Raspberry Pi that comes with
H.265 hardware encoding?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/iizukanao/picam-streamer/issues/48#issuecomment-895669224,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJFDX6U64XBJVMBTOSF3VR3T4CBUXANCNFSM5BZN6F6Q
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.

Thanks. If I have a chance to use one of the boards, I'll take a look.

Thankyou 🙏🙏🙏🙏
On Tue, Aug 10, 2021 at 11:20 AM Nao Iizuka @.***>
wrote:

Thanks. If I have a chance to use one of the boards, I'll take a look.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/iizukanao/picam-streamer/issues/48#issuecomment-895747355,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJFDX6XDRUDHWJO2RUWCMJ3T4C4YRANCNFSM5BZN6F6Q
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.


remove preview flag for import extension

This PR fixes #20498
I will remove the preview flag from extension's package.json in a separate PR.

@corivera @Charles-Gagnon

any context on this error?

☹ https://github.com/dotnet/interactive/pull/2403/files?show-deleted-files=true&show-viewed-files=true&file-filters[]=
Was deleted.
Mind updating it to https://raw.githubusercontent.com/dotnet/interactive/main/src/dotnet-interactive-vscode/images/icon.png for now?

thanks! will do. @Charles-Gagnon

well, looks like I have to fix the extension package first.

currently, I can only produce the vsix locally, @aasimkhan30 has verified that it was working as expected.


Disable julia depot path

We're hitting the julia depot path-related race condition too frequently. Let's disable it temporarily.
cc @szy21, @simonbyrne

I have an idea for an alternative solution: let me open a quick PR

Superseded by #444.


Invalid namespace

Receiving the following error after issuing the Show-PSChiaPlotter command in Powershell:
UI Runspace Error
Invalid namespace
Line # -6
Line -      $AllVolumes = Get-CimInstance -Namespace
"ROOT/Microsoft/Windows/Storage" -ClassName MSFT_Volume |
This is on a Windows 7 SP2 machine with updated Powershell (5.1 I believe).  I am also running Stablebit Drivepool (for drive aggregation) which I think installs it's own driver to mimic an NTFS volume type.  Additionally I have some drives in mountpoint folders (so those have no drive letters associated, only paths from a subfolder of C:).
Any tests I can do or further information I can provide, simply ask and I'll get what I can.  The tool runs fine on my other workstation, a W10 installation.  I am thinking that due to PS being at the equivalent revision, it has something to do with the drive letters and mountpoints.

The issue is due to Windows 7 not having that WMI namespace.
"The Windows Storage Management API supersedes the Virtual Disk Service API beginning with the Windows 8 and Windows Server 2012 operating systems." - https://docs.microsoft.com/en-us/previous-versions/windows/desktop/stormgmt/windows-storage-management-api-portal?redirectedfrom=MSDN
That namespace was not introduced until Windows 8. The network drives should appear now on PSChiaPlotter version 1.0.26 and above.

Sounds like it's not something you can work around then (or at least not easily).  I'll have to make a hard decision whether or not to update the server to W10.  W7 is just so much easier to work with, and so much less unobtrusive.
I did notice the network drive compatibility being added, thanks for that.

For quick and dirty fix you could fork the repo and replace the Get-ChiaVolume.ps1 with the following. This should work on windows 7 but to be sure I would have to spin up a VM and test.
    function Get-ChiaVolume {
    [CmdletBinding()]
    param()

$WinVer = [int](Get-CimInstance Win32_OperatingSystem).BuildNumber

if($WinVer -ge 9200){

#grabbing all volumes, partitions, disks, and physicaldisks at once since it has proven to be faster.
$AllVolumes = Get-CimInstance -Namespace "ROOT/Microsoft/Windows/Storage" -ClassName MSFT_Volume |
        Where {$_.DriveLetter -ne $Null} | sort -Property DriveLetter
    $AllPartitions = Get-Partition
    $AllDisks = Get-Disk
    $AllphysicalDisk = Get-PhysicalDisk

    foreach ($volume in $AllVolumes){
        try{
            $partition = $AllPartitions | where DriveLetter -eq $volume.DriveLetter
            $disk = $AllDisks | where DiskNumber -eq $partition.DiskNumber
            $physicalDisk = $AllphysicalDisk | where DeviceId -eq $disk.DiskNumber

            $Label = $volume.FileSystemLabel
            if ([string]::IsNullOrEmpty($volume.FileSystemLabel)){
                $Label = "N/A"
            }
            if ($physicalDisk){
                $ChiaVolume = [PSChiaPlotter.ChiaVolume]::new($volume.DriveLetter,$Label,$volume.Size,$volume.SizeRemaining)
                $ChiaVolume.BusType = $physicalDisk.BusType
                $ChiaVolume.MediaType = $physicalDisk.MediaType
                $MaxTempCount = [math]::Floor([decimal]($volume.size / (239 * 1gb)))
                $ChiaVolume.MaxConCurrentTempChiaRuns = $MaxTempCount
                $ChiaVolume
                Clear-Variable PhysicalDisk,Disk,Partition,MaxTempCount
            }
        }
        catch{
            Write-PSChiaPlotterLog -LogType "Error" -LineNumber $_.InvocationInfo.ScriptLineNumber -Message $_.Exception.Message -DebugLogPath $DataHash.LogPath
            Write-Warning "Unable to create a ChiaVolume from driveletter $($volume.DriveLetter)"
        }
    }
} Else {
$AllVolumes = Get-WmiObject -Class Win32_logicaldisk |
        Where {$_.DeviceID -ne $Null -and $_.ProviderName -notlike '\\*' }
    $AllPartitions = Get-Partition
    $AllDisks = Get-Disk
    $AllphysicalDisk = Get-PhysicalDisk

    foreach ($volume in $AllVolumes){
    $shortVol = $volume.DeviceID -replace ":.*"
        try{
            $partition = $AllPartitions | where DriveLetter -eq $shortVol
            $disk = $AllDisks | where DiskNumber -eq $partition.DiskNumber
            $physicalDisk = $AllphysicalDisk | where DeviceId -eq $disk.DiskNumber

            $Label = $volume.VolumeName
            if ([string]::IsNullOrEmpty($volume.VolumeName)){
                $Label = "N/A"
            }

            if ($physicalDisk){
                $ChiaVolume = [PSChiaPlotter.ChiaVolume]::new($shortVol,$Label,$volume.Size,$volume.FreeSpace)
                $ChiaVolume.BusType = $physicalDisk.BusType
                $ChiaVolume.MediaType = $physicalDisk.MediaType
                $MaxTempCount = [math]::Floor([decimal]($volume.size / (239 * 1gb)))
                $ChiaVolume.MaxConCurrentTempChiaRuns = $MaxTempCount
                $ChiaVolume

                Clear-Variable PhysicalDisk,Disk,Partition,MaxTempCount
            }
        }
        catch{
            Write-PSChiaPlotterLog -LogType "Error" -LineNumber $_.InvocationInfo.ScriptLineNumber -Message $_.Exception.Message -DebugLogPath $DataHash.LogPath
            Write-Warning "Unable to create a ChiaVolume from driveletter $($shortVol)"
        }
    }
  }
    $mappedDrives = Get-CimInstance -ClassName Win32_MappedLogicalDisk
    $BusType = "Network"
    $MediaType = "Unknown"
    foreach ($drive in $mappedDrives){
        try{
            if ([string]::IsNullOrEmpty($drive.ProviderName)){
                $Label = "N/A"
            }
            else{
                $Label = $drive.ProviderName
            }
            if (-not[string]::IsNullOrEmpty($drive.DeviceID)){
                $DriveLetter = $drive.DeviceID.TrimEnd(':')
                $ChiaVolume = [PSChiaPlotter.ChiaVolume]::new($DriveLetter,$Label,$drive.Size,$drive.FreeSpace)
                $ChiaVolume.BusType = $BusType
                $ChiaVolume.MediaType = $MediaType
                $MaxTempCount = [math]::Floor([decimal]($drive.size / (239 * 1gb)))
                $ChiaVolume.MaxConCurrentTempChiaRuns = $MaxTempCount
                $ChiaVolume
                Clear-Variable DriveLetter
            }
        }
        catch{
            Write-PSChiaPlotterLog -LogType "Error" -LineNumber $_.InvocationInfo.ScriptLineNumber -Message $_.Exception.Message -DebugLogPath $DataHash.LogPath
            Write-Warning "Unable to create a ChiaVolume from driveletter $($DriveLetter.DriveLetter)"
        }
    }
  }

Thanks sc00t3r, if I decide to stick with W7 I'll keep a snippet of the code handy and perhaps give it a try.
Would make a fantastic feature addition to have the code detect OS capabilities and auto-choose which method to use.  I know there are still a lot of W7 users out there.  I keep it purely for it's ease of use and small footprint.

Unfortunately I cannot support Win 7 since it is no longer supported by Microsoft and no longer receiving security updates. sk00t3r appears to have put in place a workaround if you want to fork the repo and add that portion.


Found typo in code, terraform-provider-looker/pkg/looker/resource_connection.go

I found a typo in the code on line 176. The word 'passowrd' should be 'password'. This is maybe causing the code to produce unexpected results.
https://github.com/hirosassa/terraform-provider-looker/blob/89a1ec42026600176be2843b77727b352030e327/pkg/looker/resource_connection.go#L176
https://github.com/hirosassa/terraform-provider-looker/blob/89a1ec42026600176be2843b77727b352030e327/pkg/looker/resource_connection.go#L436

@nut1204 Thank you for writing in! Cloud you create a PR to solve this? or I can go, too.

@nut1204 I'm sorry for keeping you waiting so long.
This bug is fixed in @jbennett77 's contribution.
cc @jbennett77
https://github.com/hirosassa/terraform-provider-looker/pull/48


Move to the MicroProfile parent

The first step in #351. This is a bigger change that is not directly tight to Jakarta alignment but it is a prerequisite.

I will schedule a review of this this week unless anyone else cares to look at it before then,

@xstefank this PR seems uncontentious so I'd say it is fine to merge with just one reviewer.

@mmusgrov agreed. I'll merge this so I can proceed with the jakarta changes. Thanks for the review.
-- the formating is now done automatically on compile.


Table not displaying correctly on Pagination component docs

Extra column dividers were breaking the variants table on this page

@dianasanborn Thank you but I already have a PR to resolve this issue that is waiting to be merged https://github.com/carbon-design-system/carbon-website/pull/4267

@dianasanborn Thank you but I already have a PR to resolve this issue that is waiting to be merged #4267

Okay great! I just came across it while looking into the guidance, but glad you already got it :).


AI command

make something to stop the ai chat, i recommend checking for if message.content == "stop": #stop the char

"Bye" stops AI CHAT doesn't it?

"Bye" stops AI CHAT doesn't it?

ig u should add more of them (stop words) or add a subcommand to stop too...

Hi can you please suggest more stop words? things like
bye stop and ?? I cant really think of more


Umm, Excuse me...

so i use hacks in tower defense and ended up like this

and its still going for the past 2 hours

lol

LOL, yes. Some levels are too high to beat quickly, even with fully OP towers.

LOL

We can close this as completed as it is not really an issue.
Some levels are too high to beat quickly, even with fully OP towers.


Update README.md

Remove mention of frontend js in readme
References:

Issue #65 - frontend js fileis removed
PR #62 - 3.4.0

Should the readme include a mention to remove the inclusion of the file in the spree/frontend/all.js when updating the version?


libtpm2-pk11 segfaults

I have compiled and installed the latest master branches from tpm2-tss, tpm2-abrmd and tpm2-tools. They talk to an IBM soft-TPM. I had to slightly modify tpm2-pk11 to make it compatible with the new TCTI device and socket API (https://github.com/irtimmer/tpm2-pk11/compare/master...svenschwermer:master). The tpm2-tools work as expected.
When I run p11tool --provider=libtpm2-pk11.so --list-privkeys, however, libtpm2-pk11 segfaults in attr_get. Running the command with a debug build from gdb with logging enabled yields:
─── Output/messages
2018-03-07 21:38:44 [tpm-pk11] C_GetInfo
2018-03-07 21:38:44 [tpm-pk11] C_GetSlotList: present = true
2018-03-07 21:38:44 [tpm-pk11] C_GetTokenInfo: id = 4660
2018-03-07 21:38:44 [tpm-pk11] C_GetSlotInfo: id = 4660
2018-03-07 21:38:44 [tpm-pk11] C_OpenSession: id = 4660, flags = 4
2018-03-07 21:38:44 [tpm-pk11] C_CloseSession: session = 55800e30
2018-03-07 21:38:44 [tpm-pk11] C_GetSlotList: present = true
2018-03-07 21:38:44 [tpm-pk11] C_GetTokenInfo: id = 4660
2018-03-07 21:38:45 [tpm-pk11] C_GetSlotInfo: id = 4660
2018-03-07 21:38:45 [tpm-pk11] C_OpenSession: id = 4660, flags = 4
2018-03-07 21:38:45 [tpm-pk11] C_CloseSession: session = e400b8c0
2018-03-07 21:38:45 [tpm-pk11] C_GetSlotList: present = true
2018-03-07 21:38:45 [tpm-pk11] C_GetTokenInfo: id = 4660
2018-03-07 21:38:45 [tpm-pk11] C_GetSlotInfo: id = 4660
2018-03-07 21:38:45 [tpm-pk11] C_OpenSession: id = 4660, flags = 4
2018-03-07 21:38:45 [tpm-pk11] C_CloseSession: session = e400bb70
2018-03-07 21:38:45 [tpm-pk11] C_GetSlotList: present = true
2018-03-07 21:38:45 [tpm-pk11] C_GetTokenInfo: id = 4660
2018-03-07 21:38:45 [tpm-pk11] C_GetSlotInfo: id = 4660
2018-03-07 21:38:45 [tpm-pk11] C_OpenSession: id = 4660, flags = 4
2018-03-07 21:38:45 [tpm-pk11] C_FindObjectsInit: session = e400be00, count = 1
2018-03-07 21:38:45 [tpm-pk11] C_FindObjects: session = e400be00, max = 8192

Thread 1 "p11tool" received signal SIGSEGV, Segmentation fault.
─── Assembly
0x00007ffff5ca4fb3 attr_get+277 mov    -0x18(%rbp),%eax
0x00007ffff5ca4fb6 attr_get+280 movslq %eax,%rdx
0x00007ffff5ca4fb9 attr_get+283 mov    -0x28(%rbp),%rax
0x00007ffff5ca4fbd attr_get+287 mov    0x18(%rax),%rax
0x00007ffff5ca4fc1 attr_get+291 cmp    %rax,%rdx
0x00007ffff5ca4fc4 attr_get+294 jb     0x7ffff5ca4eba <attr_get+28>
0x00007ffff5ca4fca attr_get+300 mov    $0x0,%eax
─── Source
48   attr_dynamic_index_of(CKA_SERIAL_NUMBER, PkcsX509, serial, serial_size),
49   attr_index_of(CKA_CERTIFICATE_TYPE, PkcsX509, cert_type),
50 };
51
52 void* attr_get(pObject object, CK_ATTRIBUTE_TYPE type, size_t *size) {
53   for (int i = 0; i < object->num_entries; i++) {
54     pAttrIndexEntry entries = &object->entries[i];
55     for (int j = 0; j < entries->num_attrs; j++) {
56       if (type == entries->indexes[j].type) {
57         pAttrIndex index = &entries->indexes[j];
58         if (index->size_offset == 0) {
─── Stack
[0] from 0x00007ffff5ca4fbd in attr_get+287 at /home/sven/tpm2/tpm2-pk11/src/object.c:53
arg object = 0x0
arg type = 0
arg size = 0x7fffffffcf60
[1] from 0x00007ffff5ca63f2 in C_FindObjects+277 at /home/sven/tpm2/tpm2-pk11/src/pk11.c:181
arg session_handle =<PHONE_NUMBER>41920
arg object_handle = 0x5555558094b0
arg max_objects = 8192
arg found = 0x7fffffffd408
[+]
───
0x00007ffff5ca4fbd in attr_get (object=0x0, type=0, size=0x7fffffffcf60) at /home/sven/tpm2/tpm2-pk11/src/object.c:53
53	  for (int i = 0; i < object->num_entries; i++) {

We can see that attr_get is called with object=0.

I just tried the same with the following versions:

tpm2-tss 1.3.0
tpm2-abrmd 1.2.0
tpm2-tools 3.0.3
tpm2-pk11 at 0876bca

The same thing happens.

I managed to make everything work on a different machine (Ubuntu 16.04 vs. Arch which I used before). However, I do run into a segfault in the working setup when the TPM doesn't hold any keys (remanufactured) and then run p11tool --list-keys. Perhaps this was the reason for the crash on the other machine as well.

It indeed crashes when there are no keys. I already have a patch to fix it, but haven't it committed and pushed it.

Fixed with commit 2f0ed78f33d09b401f2392b34c12dae0152e5519


Feature_Request: Add back to top Scroll button

Is your feature request related to a problem? Please describe.
There is no back to top scroll button which we can add to make it look organized.
Describe the solution you'd like
I want to add the button on the bottom-right corner or in the middle according to the alignment.
Are you contributing under any open-source program ?
I am contributing under GSSoC'24
Please assign this issue to me @apu52

Please assign this issue to me @apu52

Hi ,
This issue has been already resolved. Please raise a new issue that is meaningfull.
Regards
Project Mentor (GSSoC' 24)


Pending transactions only mentioned in activity tab, lack hints in the wallet tab

Go to https://1inch.exchange/#/r/0x147615dceb7aac2e7389037300b65e99b3b94f96
Claim 1inch token, confirm and send the transaction
Observe the claim transaction is correctly recorded in etherscan as pending
Go to wallet tab and not seeing any difference. Panic.

Expected:

Go to the wallet tab and it shows Ether balance is reduced (by an estimated amount)
There is a red circle with a number (1) on the Activity tab icon, so the user is lead to Activity to observe the pending tx.

Might tomek produce a design to address this?

I have already claimed my 1inch tokens so I can't replay the same flow.

Do you have screenshots or anything that can help me here?

This requires a full node connection - since the transaction for the claim is not issued directly from AW it has no knowledge of the transaction until written.
With a full node connection we can scan the memory pool and see the transaction pending.

Do you have screenshots or anything that can help me here?

I renamed the issue to make it clear what I meant.
The problem is that there is no VISUAL hint on a pending transaction.
It helps little with a screenshot because on the screenshot I cannot show you what is missing.
I can make a design myself to point out what I think is missing though.

This requires a full node connection - since the transaction for the claim is not issued directly from AW it has no knowledge of the transaction until written.
With a full node connection we can scan the memory pool and see the transaction pending.

What you described is not this issue; I changed the issue title to add clarity.

Ah I see, yes showing pending tx like that would be a good idea. How about 'new transactions' since the user last looked at the activity page?

Linking this issue to a related problem https://github.com/AlphaWallet/alpha-wallet-ios/issues/2545

@colourful-land
A Wallet tab view is not a place where you should look for a confirmation of your transactions. With the upcoming 'Samoa' update, it will be mostly to tell you how is your balance and how did it change in the last 24H. Without cluttering it with the content, that should go to Activities.

Go to wallet tab and not seeing any difference. Panic.

There are two places, where you can see a difference.

Activities
Token's activities

First and foremost this should be found in Activities.
The second is when you open a token (Ether for example) and you can open the 'Activity' tab. That should be enough for you.

But what is missing is out of my control, as a token balance should deduct your balance if this is pending.
So besides #2545 which is a problem to solve, we have to answer ourselves a question:
Do we want to deduct your token balance if a transaction is still pending?
I understand your banking experience, when the chances that a transaction sent will not go through is very, very low. So you can deduct a balance immediately. You keep the clarity and control. But here, you never know. Because even if we deduct it from the total balance, then would be able to speed up the transaction with 0 Balance?


NaN problem

I'm having a problem with BoxShap.RayTest function which under some special conditions gets a NaN.
I'm raycasting with (0,-1,0) to get the height of the terrain, this means that inverse direction goes to infinite.
https://github.com/bepu/bepuphysics1/blob/e0438719412e2eab8683d5ca65c1b0bb0e9b177a/BEPUphysics/CollisionShapes/ConvexShapes/BoxShape.cs#L214
This is probably not a problem and the code is thought with this Infinite in mind to happen (it'd have been catched much earlier) however my real problem is that in the next line, (-halfWidth - localOrigin.X) is exactly zero, giving t1 a NaN value and bringing caos to characters walking over that box.
https://github.com/bepu/bepuphysics1/blob/e0438719412e2eab8683d5ca65c1b0bb0e9b177a/BEPUphysics/CollisionShapes/ConvexShapes/BoxShape.cs#L215
This is also happening to me when checking the Z component (same situation) a few lines below.
Could you please suggest me what to do in order to fix this?  I think setting t1 to Infinite when NaN is detected (and do the same for t2, and all the other components) would be ok, but I'd like to check this with you, as I don't understand the implications this can take.
Thanks! :)

Hi! Sorry for the delay.
I've been testing the code and it fixes the problem, and everything else seems to work well too.
Only a minor problem: "hit = default;" in lines 233 and 267  gives an error because the project is configured to use C# 7.0 . I've replaced it with hit = new RayHit()
thanks!


--match-contract and --match-test changed to glob pattern

Motivation
Wanted to contribute to https://github.com/foundry-rs/foundry/issues/1230
Solution
Same as discussed
definitely happy to get any feedback/mentoring and make adjustments
the way I handled vectors was not the way i wanted to do it, but I wasn't sure how to do it the iterator way.

going to do new pull request with one commit


Does deleting bridge EP clean out EP flash? (CON-830)

Lots of clusters have persistent attribute values which are kept in flash. If I make a bridged device which contains persistent clusters, does flash get cleaned up if I delete the bridged EP?  I have not tested this yet.
Probably should be part of your test suite to make sure that this stuff doesn't accumulate in flash.

No. currently we don't clean the persistent attribute values after remove an endpoint, Thanks for the report! We will fix it ASAP.

This has been fixed with https://github.com/espressif/esp-matter/commit/98c6e8070b582c9b18058256f490e6b02a4264e1


Attribute fetchpriority doesnt work on  tag with styled object

I am using styled-component with STYLED OBJECT! (so no template literals solution, pls)
Usually attributes pass thru. but in the case of the image ( tag) that is not the case!?
Pls help!!

Please try v6 beta, we no longer filter attributes you pass to your styled components outside of transient props ($ prefix.)


Implement facet search api

As a user I want to be able to search for facets. This ticket is about exposing the opensearch index to the user to enable a fuzzy text search of facet label via a new API endpoint.
The API endpoint will accept a query string and a context (target or disease). It will return search hits. The hits will include the facet label, the target or disease ids, the facet category and the id of the facet label.
Background
See https://github.com/opentargets/issues/issues/3239
Tasks

[x] define the data models in the API, one for target facets, one for disease facets
[x] implement an endpoint enabling the fuzzy text search of the facet label within either the target or disease facet search index

Acceptance tests
How do we know the task is complete?

The API has an endpoint all

After some discussion, it might be best to use OR filter within category and an AND filter between categories


Add (back) support for interruptions

We had it in a previous version, but we refactored some internals and it went away. We'll have it back soon.

Being implemented in https://github.com/pipecat-ai/pipecat/pull/144

I believe this can be closed now after 0.0.17.


Esprima can't parse codes which already have flow type annotations

Problem
Esprima can't parse codes which already have flow type annotations.
When we have foo.js like this:
// @flow

/**
 * @param {string} str
 */
function foo(str): string {
  return str;
}

... then flow-jsdoc dies, because esprima.parse() can't parse flow type annotation and throws a parse error.
$ flow-jsdoc -f foo.js

/Users/fand/.nodenv/versions/6.9.5/lib/node_modules/flow-jsdoc/node_modules/esprima/dist/esprima.js:552
	        throw this.unexpectedTokenError(token, message);
	        ^
Error: Line 6: Unexpected token :
    at ErrorHandler.constructError (/Users/fand/.nodenv/versions/6.9.5/lib/node_modules/flow-jsdoc/node_modules/esprima/dist/esprima.js:3396:22)
    at ErrorHandler.createError (/Users/fand/.nodenv/versions/6.9.5/lib/node_modules/flow-jsdoc/node_modules/esprima/dist/esprima.js:3414:27)
    at JSXParser.Parser.unexpectedTokenError (/Users/fand/.nodenv/versions/6.9.5/lib/node_modules/flow-jsdoc/node_modules/esprima/dist/esprima.js:542:39)
    at JSXParser.Parser.throwUnexpectedToken (/Users/fand/.nodenv/versions/6.9.5/lib/node_modules/flow-jsdoc/node_modules/esprima/dist/esprima.js:552:21)
    at JSXParser.Parser.expect (/Users/fand/.nodenv/versions/6.9.5/lib/node_modules/flow-jsdoc/node_modules/esprima/dist/esprima.js:716:19)
    at JSXParser.Parser.parseFunctionSourceElements (/Users/fand/.nodenv/versions/6.9.5/lib/node_modules/flow-jsdoc/node_modules/esprima/dist/esprima.js:2572:15)
    at JSXParser.Parser.parseFunctionDeclaration (/Users/fand/.nodenv/versions/6.9.5/lib/node_modules/flow-jsdoc/node_modules/esprima/dist/esprima.js:2713:26)
    at JSXParser.Parser.parseStatementListItem (/Users/fand/.nodenv/versions/6.9.5/lib/node_modules/flow-jsdoc/node_modules/esprima/dist/esprima.js:1809:39)
    at JSXParser.Parser.parseProgram (/Users/fand/.nodenv/versions/6.9.5/lib/node_modules/flow-jsdoc/node_modules/esprima/dist/esprima.js:3061:29)
    at parse (/Users/fand/.nodenv/versions/6.9.5/lib/node_modules/flow-jsdoc/node_modules/esprima/dist/esprima.js:117:24)

It would be great if flow-jsdoc could parse such codes.
Replacing Esprima with Babylon will solve the problem.
Also, It would be nice if flow-jsdoc could handle the confliction between JSDoc types and existing flow type annotations 😺

Please state the problem, not a proposed solution in your issues, thanks!

I've thought about this and not really ever intended this tool to be used on projects which already have actual flowtype annotations because:

Why aren't you just using flowtype annotations throughout?
What do you do if you get conflicting information between JSDoc and flowtype annotations?

This feels too feature creepy for my liking. Leaving it open on the off-chance this is a highly requested feature, which would force my hand the other way.

Why aren't you just using flowtype annotations throughout?

I encontered this propblem while working on a project, which already has JSDoc annotations and going to use flowtype.
We've already added some flowtype annotations before we adopt flow-jsdoc, so we had to remove flowtype annotations.
Handwritten flowtype annotations are always correct while we check types in CI.
But JSDoc type annotations are not always correct because we don't use Closure Compiler.
(Most developers don't use Closure Compiler, AFAIK)
So It would be great if flow-jsdoc treats existing flowtype annotations well.

What do you do if you get conflicting information between JSDoc and flowtype annotations?

Well, this might be a hard problem.
There are 2 possible solution:

Overwrite existing flowtype annotations with JSDoc annotations (or vice versa) by default
Let users to specify the priorities for JSDoc and flowtype annotations

Maybe we can start by just replacing the parser, and ignore the confliction.

we can start by just replacing the parser, and ignore the confliction

If we do this then in about a month I'm going to get the following issues submitted to this issue tracker:

flow-jsdoc is replacing flow type annotations with JSDoc types
flow-jsdoc is not replacing flow type annotations with JSDoc types

It's not clear what the correct behaviour should be, so really the conflict needs to be sorted at the same time as the parser. I'm open to the idea of swapping this project to use Babylon in order to fix this issue, given your use case feels completely valid.


LibWeb: Make “create an event” set the event’s isTrusted to true

This change ensures that when then the code corresponding to the “create an event” operation at https://dom.spec.whatwg.org/#concept-event-create is called, the event’s isTrusted is set to true — as the spec requires.
That causes the failures for the following WPT tests to pass:

https://wpt.fyi/results/html/semantics/forms/the-input-element/checkbox.html?run_id=5080423051034624
https://wpt.fyi/results/html/semantics/interactive-elements/the-dialog-element/dialog-close.html?run_id=5080423051034624

…and there are likely a number of similar WPT tests that hit this same code path which this commit will cause to be changed to passes.
Otherwise, without this change, the “create event” implementation doesn’t conform to the spec requirements – nor behave interoperably with other existing engines — and those WPT test would continue to fail.

CI testing if the macOS build is failing, but from the log at https://github.com/LadybirdBrowser/ladybird/actions/runs/10644053431/job/29508372504?pr=1227 I can’t yet figure out what the failure is… Will keep looking


[Feature Request] DynamicTensorSpec a TensorSpec for sequential data

Motivation
There is currently no TensorSpec such that it allows sequential data. For example, if an environment was supposed to represent a sentence, it would be represented as (batch_size, sequence_len, embedding_size). Such a TensorSpec could also be used for graphs or any other application that is represented as sequence.Since, the length sequence is not fixed it would helpful to allow to define a TensorSpec with shape (batch_size, -1, embedding_size). In such cases, the embedding_size is fixed and -1 represent the dynamic shape of the length of the sequence.
Solution
Such a TensorSpec would have to be described by either a nested tensor, LazyStackedTensorDict or a padded tensor.
Alternatives
Currently, it's not possible to have any such structure in TorchRL. By using other TensorSpecs can solve the issue if as long as  we avoid enforcing the shape restrictions and we don't use batched ends.
Checklist

[x] I have checked that there is no similar issue in the repo (required)

Closed by #2143


Update solarmanpv to 0.5.3

Please update my adapter ioBroker.solarmanpv to version 0.5.3.
This pull request was created by https://www.iobroker.dev c0726ff.

Release 0.5.2 increases to requirement for js-controller to 5.0.19 and node.js to 18.x
This requires a new minor release.
Please create a new minor release and create a new PR after the release is available at latest repository for approximatly 1 to 2 weeks.


HDH-284-harness-u-on-hdh-minor-improvements

Thanks for contributing to the Harness Developer Hub! Our code owners will review your submission.
Description

Please describe your changes: __________________________________
Jira/GitHub Issue numbers (if any): ______________________________
Preview links/images (Internal contributors only): __________________

PR lifecycle
We aim to merge PRs within one week or less, but delays happen sometimes.
If your PR is open longer than two weeks without any human activity, please tag a code owner in a comment.
PRs must meet these requirements to be merged:

[ ] Successful preview build.
[ ] Code owner review.
[ ] No merge conflicts.
[ ] Release notes/new features docs: Feature/version released to at least one prod environment.

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

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

Will review.

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


Question about Off-chain Decider and the time of ”generated Decider proof”

Hi!
Recently, I’ve been working with Nova to fold my circuit based on Sonobe. However, I couldn't find any example code for implementing the off-chain Decider implement.
All the code in the examples folder is focused on generating a  DeciderEthCircuit final proof, I would like to generate a  DeciderCircuit final proofinstead, and I don't want it to be based on EVM. Could you advise me on what I should do?
Another question I have is about the time it takes to generate the Decider proof.
I tried folding my own circuit as well as the example, circom_full_flow.rs.
I found that the time to generate the Decider proof is quite long—around 300 seconds. What could be the reason for this? Is it because my laptop's memory (16GB) is too small?
Below is the result from running the circom_full_flow.rs example:

Could you help me figure out what I should do?
Thanks!
Looking forward to your reply.

Hi！
Thanks for your reply!
I have read and test the test_decider in decider.rs, but the type of circuit in it was CubicFCircuit.
So I changed the N and D code in the circom_full_flow.rs, tried to use off-chain Decider on CircomFCircuit.
But it did not run successfully.
use folding_schemes::{
    commitment::{kzg::KZG, pedersen::Pedersen},
    folding::{
        nova::{
            decider_eth::{prepare_calldata, Decider as DeciderEth},
            decider::{Decider as Decideroffchain},
            Nova, PreprocessorParam,
        },
        traits::CommittedInstanceOps,
    },
    frontend::FCircuit,
    transcript::poseidon::poseidon_canonical_config,
    Decider,
    FoldingScheme,
    // Error,
};

use ark_mnt4_298::{
    constraints::G1Var as GVar, Fr, G1Projective as Projective, MNT4_298 as MNT4,
};
use ark_mnt6_298::{
    constraints::G1Var as GVar2, G1Projective as Projective2, MNT6_298 as MNT6,
};

// initialize the Circom circuit
    let r1cs_path = PathBuf::from("D:/ZKP_file/Work/test/sonobe-main/frontends/src/circom/test_folder/with_external_inputs.r1cs");
    let wasm_path = PathBuf::from(
        "D:/ZKP_file/Work/test/sonobe-main/frontends/src/circom/test_folder/with_external_inputs_js/with_external_inputs.wasm",
    );

    let f_circuit_params = (r1cs_path.into(), wasm_path.into(), 1, 2);
    let f_circuit = CircomFCircuit::<Fr>::new(f_circuit_params).unwrap();

    type N = Nova<
        Projective,
        GVar,
        Projective2,
        GVar2,
        CircomFCircuit<Fr>,
        KZG<'static, MNT4>,
        KZG<'static, MNT6>,
        false,
    >;
    type D = Decideroffchain<
        Projective,
        GVar,
        Projective2,
        GVar2,
        CircomFCircuit<Fr>,
        KZG<'static, MNT4>,
        KZG<'static, MNT6>,
        Groth16<MNT4>,
        Groth16<MNT6>,
        N, // here we define the FoldingScheme to use
    >;

    let poseidon_config = poseidon_canonical_config::<Fr>();
    let mut rng = rand::rngs::OsRng;

    // prepare the Nova prover & verifier params
    let nova_preprocess_params = PreprocessorParam::new(poseidon_config, f_circuit.clone());
    let nova_params = N::preprocess(&mut rng, &nova_preprocess_params).unwrap();

Above is part of the test code, and there was an error when running to this line of code let f_circuit = CircomFCircuit::<Fr>::new(f_circuit_params).unwrap();

Could you help me to fix this error?
Looking forward to your reply!
Thanks


Is it possible to have the date range? (E.g you can pick between 8:00 am to 11:00 am)

As per title says, is it really possible?

it will be available in the next version.


Error when running danger: GitLab gem is not installed

Report
What did you do?
GitLab CI run danger
What did you expect to happen?
Danger to be executed
What happened instead?
$ danger
The GitLab gem was not installed, you will need to change your Gem from `danger` to `danger-gitlab`.

 - See https://github.com/danger/danger/blob/master/CHANGELOG.md#400
ERROR: Job failed: exit code 1

Your Environment

Which CI are you running on? GitLab CI
Are you running the latest version of Danger? Yes
What is your Dangerfile?

message "You have added 3 more gems to the app."

btw. the template where the code block starts with ```ruby has the wrong indention which breaks the formatting

The installation output:
$ gem install bundler danger-gitlab --no-ri --no-rdoc
Successfully installed bundler-1.16.4
Successfully installed claide-1.0.2
Successfully installed nap-1.1.0
Successfully installed colored2-3.1.2
Successfully installed cork-0.3.0
Successfully installed open4-1.3.4
Successfully installed claide-plugins-0.9.2
Successfully installed git-1.5.0
Successfully installed multipart-post-2.0.0
Successfully installed faraday-0.15.2
Successfully installed faraday-http-cache-1.3.1
Successfully installed public_suffix-3.0.3
Successfully installed addressable-2.5.2
Successfully installed sawyer-0.8.1
Successfully installed octokit-4.12.0
Successfully installed kramdown-1.17.0
Successfully installed unicode-display_width-1.4.0
Successfully installed terminal-table-1.8.0
Successfully installed no_proxy_fix-0.1.2
Successfully installed danger-5.6.6
Successfully installed multi_xml-0.6.0
When you HTTParty, you must party hard!
Successfully installed httparty-0.16.2
Successfully installed gitlab-4.5.0
Successfully installed danger-gitlab-6.0.0
24 gems installed

Perhaps this only works if are using a Gemfile? I'm unsure- you might need to investigate yourself.

I have the same problem. It's a very interesting situation when you using GitLab only as CI for your project but source code still on GitHub. Have no idea what to do now. Any ideas?

Still a problem , tried to build a custom rspec and downgrade gitlab version but the error still pops
The GitLab gem was not installed, you will need to change your Gem from dangertodanger-gitlab.


[Support Request]: Documentation-Enhancement Deploying with internal URL but also serve via Apache-Proxy with external URL.

Attempted Debugging

[X] I have read the debugging page

Searched GitHub Issues

[X] I have searched GitHub for the issue.

Describe the Scenario
First of all. I didn't really know which type of ticket would be best so please be gentle :-).
I just got this working and wanted to share it for those who are also deploying the Bookstack-App in an local Domain-Environment but also want to access it via e.g. WAN.
With Apache mod_proxy and mod_substitute i used the following Configuration

Apache WAN

<Location "/wiki">
    RewriteEngine on
    RewriteRule .* - [E=PROXY_USER:%{LA-U:REMOTE_USER}] # note mod_rewrite's lookahead option
    RequestHeader set Proxy-User %{PROXY_USER}e
    ProxyPreserveHost off
    SetOutputFilter INFLATE;SUBSTITUTE;DEFLATE
    AddOutputFilterByType SUBSTITUTE text/html
    AddOutputFilterByType SUBSTITUTE text/css
    AddOutputFilterByType SUBSTITUTE text/javascript
    AddOutputFilterByType SUBSTITUTE application/javascript
    AddOutputFilterByType SUBSTITUTE application/x-javascript
    Substitute "s/local.hostname.tld/external.hostname.tld/iq"
        ProxyPass https://local.hostname.tld/wiki
        ProxyPassReverse https://local.hostname.tld/wiki
</Location>

I left the Proxy-User as it suits my setup with SSO. (No, not SSO in Bookstack but all other Sites)

Apache INTERNAL

ProxyPreserveHost on
ProxyPass /wiki http://localhost:40280
ProxyPassReverse /wiki http://localhost:40280

<Location /wiki/api>
#This one is from allowing API-Access without SSO-Auth as the API uses the Token
Order allow,deny
allow from all
</Location>

Maybe there is something that can be done better. All tests I've done so far worked.
regards,
~crpb
Exact BookStack Version
v21.11
Log Content
No response
PHP Version
No response
Hosting Environment
Bookstack-App:
docker-compose
image: ghcr.io/linuxserver/bookstack:version-v21.11
Bookstack-Host:
Ubuntu 18.04
Apache 2.4.29 with Kerberos-SSO
WAN-Host:
Ubuntu 18.04
Apache 2.4.29

Thanks for sharing @crpb.
Since there's no action to perform here I'll close this off but hopefully it'll remain useful to anyone searching when in a similar scenario.
Just to confirm, BookStack only supports being accessed via a single host URL (or APP_URL value). Performing edit activities via mulitple URLs could lead to issues depending on a bunch of factors.


Breaking change in langchain-google-genai after version from 1.0.3 -> 1.0.4 or higher gives 'TypeError: generate_content() got an unexpected keyword argument 'request'

Hi,
We are using langchain-google-genai   in our AI sdk and for langchain integration of gemini model, we use langchain-google-genai, which was working fine with version 1.0.3 and as soon as I update it to version 1.0.4 or higher I get below error from chat_models.py:187: in _chat_with_retry.
Previously we had following library version:
langchain~=0.1.16
google-generativeai~=0.5.4
langchain-google-genai==1.0.3

now when I update to :
langchain[openai]~=0.2.1
google-generativeai~=0.5.4
langchain-google-genai==1.0.4

This request parameter is added in https://github.com/langchain-ai/langchain-google/blob/f11446a743f104703ddd9bac811a4527a85ae90a/libs/genai/langchain_google_genai/chat_models.py#L760
The version 1.0.3 worked as expected but not in version 1.0.4 or higher and I see there was a refactoring done, could you please let me know if there is any change in the way we invoke the chain or initialize the model is exactly like before.
It looks like the refactoring https://github.com/langchain-ai/langchain-google/pull/209/files#diff-789e24521c3e983e4ad9f51a1c0db73ea6fe0e36a60609b2d20026b106c4b813 has caused breaking changes.

chat_model = ChatGoogleGenerativeAI(proxy_model_name='gemini-1.0-pro', proxy_client=self.proxy_client)
self.assertIsNotNone(chat_model.model)
tweet_prompt = PromptTemplate.from_template("You are a content creator. Write me a tweet about {topic}.")
chain = LLMChain(llm=chat_model, prompt=tweet_prompt, verbose=True)

  response = chain.invoke('How does it feel to experience snow in summer?')

test_google.py:44:

../../ENV/lib/python3.9/site-packages/langchain/chains/base.py:166: in invoke
raise e
../../ENV/lib/python3.9/site-packages/langchain/chains/base.py:156: in invoke
self._call(inputs, run_manager=run_manager)
../../ENV/lib/python3.9/site-packages/langchain/chains/llm.py:126: in _call
response = self.generate([inputs], run_manager=run_manager)
../../ENV/lib/python3.9/site-packages/langchain/chains/llm.py:138: in generate
return self.llm.generate_prompt(
../../ENV/lib/python3.9/site-packages/langchain_core/language_models/chat_models.py:599: in generate_prompt
return self.generate(prompt_messages, stop=stop, callbacks=callbacks, **kwargs)
../../ENV/lib/python3.9/site-packages/langchain_core/language_models/chat_models.py:456: in generate
raise e
../../ENV/lib/python3.9/site-packages/langchain_core/language_models/chat_models.py:446: in generate
self._generate_with_cache(
../../ENV/lib/python3.9/site-packages/langchain_core/language_models/chat_models.py:671: in _generate_with_cache
result = self._generate(
../../ENV/lib/python3.9/site-packages/langchain_google_genai/chat_models.py:760: in _generate
response: GenerateContentResponse = _chat_with_retry(
../../ENV/lib/python3.9/site-packages/langchain_google_genai/chat_models.py:189: in _chat_with_retry
return _chat_with_retry(**kwargs)
../../ENV/lib/python3.9/site-packages/tenacity/init.py:289: in wrapped_f
return self(f, *args, **kw)
../../ENV/lib/python3.9/site-packages/tenacity/init.py:379: in call
do = self.iter(retry_state=retry_state)
../../ENV/lib/python3.9/site-packages/tenacity/init.py:314: in iter
return fut.result()
/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/concurrent/futures/_base.py:438: in result
return self.__get_result()
/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/concurrent/futures/_base.py:390: in __get_result
raise self._exception
../../ENV/lib/python3.9/site-packages/tenacity/init.py:382: in call
result = fn(*args, **kwargs)
../../ENV/lib/python3.9/site-packages/langchain_google_genai/chat_models.py:187: in _chat_with_retry
raise e

kwargs = {'metadata': [], 'request': model: "gemini-1.0-pro"
contents {
parts {
text: "You are a content creator. Write m...loods affect Heidelberg, Germany."
}
role: "user"
}
generation_config {
candidate_count: 1
temperature: 0.7
}
}
@retry_decorator
def _chat_with_retry(**kwargs: Any) -> Any:
    try:

      return generation_method(**kwargs)

E           TypeError: generate_content() got an unexpected keyword argument 'request'
../../ENV/lib/python3.9/site-packages/langchain_google_genai/chat_models.py:171: TypeError

@lkuligin I see that the refactoring was done by you. It would be great if you could take a look at this issue as this is blocking us from using latest langchain and langchain-google versions.

It looks like you're doing some additional transformations on your side.
This code works fine with the latest version of libraries:
from langchain_google_genai import ChatGoogleGenerativeAI

llm = ChatGoogleGenerativeAI(model="gemini-pro", google_api_key=api_key)

from langchain_core.prompts.prompt import PromptTemplate
from langchain.chains import LLMChain

tweet_prompt = PromptTemplate.from_template("You are a content creator. Write me a tweet about {topic}.")
chain = LLMChain(llm=llm, prompt=tweet_prompt, verbose=True)

response = chain.invoke('How does it feel to experience snow in summer?')
print(response)

so essentially there're no breaking changes to the standard interfaces, if you're using low-level private methods, maybe you need to adjust things on your side accordingly, but I'm not sure it can be treated as a "breaking change".

@lkuligin There hasn't been any code changes in our sdk where we use langchain-google, the above error is caused only when I upgrade the library to version 1.0.4 or higher. If I use 1.0.3 the "invoke" call works fine.
The argument "request" in the error is also something that is added within langchain_google_genai and not from our code.
E TypeError: generate_content() got an unexpected keyword argument 'request'

../../ENV/lib/python3.9/site-packages/langchain_google_genai/chat_models.py:171: TypeError

This request attribute is set within https://github.com/langchain-ai/langchain-google/blob/f11446a743f104703ddd9bac811a4527a85ae90a/libs/genai/langchain_google_genai/chat_models.py#L760

Hi,
To give more information on where the breaking changes is -> https://github.com/langchain-ai/langchain-google/pull/207/files#diff-789e24521c3e983e4ad9f51a1c0db73ea6fe0e36a60609b2d20026b106c4b813
With this refactoring in chat_models.py, the client part of the ChatGoogleGenerativeAI is "GenerativeServiceClient" instead of "GenerativeModel"
Since, we need provide our Authorization via request headers, we have a overridden class for GenerativeModel class, which is also the native google client "google.generativeai.GenerativeModel" from "google-generativeai" library. With older version this client was compatible due to above reason. Whereas with newer version with change in client, it requires to add authorization and URI for the new client. Since the existing library doesn't support passing these parameters for Authorization, it requires to re-write some of the implementation, making it quite difficult to integrate.
Could we know the reaon for changing the client from "GenerativeModel" to "GenerativeServiceClient" in ChatGoogleGenerativeAI class?
Thanks,
Namitha


Windows Config Changes

Proposed Changes
Add logic to install NFS Addon, with option to continue with SMB (NFS should resolve performance issues)
Add logic for relevant mount types based on OS/Addon installed
Add cleanup script for Windows (Powershell only)

Think I'm done with the Windows changes, tried to squash the commits but failed badly! :)


fix: check only first sublevel for validators with each_item

Change Summary
When using a validator with each_item, the items are all validated
one by one. But if an item is also iterable the subitems are then
validated because the validator is kept as it is.
Now the validator passed to the items is changed and won't be propagated
Related issue number
closes #1255
closes #1933
Checklist

[x] Unit tests for the changes exist
[x] Tests pass on CI and coverage remains at 100%
[x] Documentation reflects the changes where applicable
[x] changes/<pull request or issue id>-<github username>.md file added describing change
(see changes/README.md for details)

I'll reply on the issue.

see https://github.com/samuelcolvin/pydantic/issues/1933#issuecomment-735418328, let's update this to add recursive.

@samuelcolvin Glad you accepted the proposal! Done here 8c336abdd8bd3de5cec97c319ed44028704d4144

@samuelcolvin Glad you accepted the proposal! I added the recursive kwarg to ensure the breaking change is easy to fix. But as you can see in my test the behaviour before was really weird. Before it was not really recursive but more a validation for the "last sublevel" based on the field type! if I'm not mistaken.
Should I rename the kwarg to deep or last_sublevel? recursive may be misleading. Should I try to explain the old behaviour?
Or should we actually have a real "recursive" way of validating in which case the old behaviour was buggy

Sorry for the slow reply.
I agree recusive is wrong. Let's drop it and call this a breaking change.

Since we agree on the breaking change I removed the last few commits and just added the "breaking change" note with some basic explanation

Since we agree on the breaking change I removed the last few commits and just added the "breaking change" note with some basic explanation


Allow HTML to be passed to summary table cells

Table cells can contain things like:

lists
links

…and we've decided that the prefered way to do this is build the HTML in the app and pass it through to the toolkit, like we do with the beta banner, etc.
The alternative would be to have the pattern know about things like assurance approaches, which would make our toolkit very tightly coupled to our current, limited set of data structures.

Looks |safe to me.


Periodic error getting scan results

aws-ecr-client, version v0.4.0

Note: Stage repo is not specified - will use destination repo as scanning silo

First push image to scanning repo as ***.dkr.ecr.eu-central-1.amazonaws.com/image:tag-523bd7200e45bdsadbba1d17ce3a6885a782b7-scan-16502334369[34](https://github.com/XXXXX/image/runs/1489473298?check_suite_focus=true#step:9:34)[36](https://github.com/XXXX/image/runs/1489473298?check_suite_focus=true#step:9:36)9

Checking scan result for the image ***.dkr.ecr.eu-central-1.amazonaws.com/image:tag-c[37](https://github.com/XXXXX/image/runs/6089783298?check_suite_focus=true#step:9:37)523bd7200e45bdsadbba1d17ce3a6885a782b7-scan-16502334369
operation error ECR: DescribeImageScanFindings, https response error StatusCode: 400, RequestID: 2c912c3a-a676-4c44-b768-e669cdc[39](https://github.com/XXXX/image/runs/1489473298?check_suite_focus=true#step:9:39)46b, ImageNotFoundException: The image with imageId {imageDigest:'sha256:b98e1583d206104249ac2e959d7bdefeeff144171c09dcb789757fdb6b007be', imageTag:'tag-c37523bd7200e45b199bba1d17ce3a6885a782b7-scan-1650434369'} does not exist within the repository with name 'image' in the registry with id '***'
Error: Process completed with exit code 1.

P.S. May be fixed in older versions

that issue is still exist in v.0.5.1

@vladimir-cageyv-firi any suggestions on how to reproduce?

The error is very floating and appeared about once or twice a week
I think that we can just run github actions with matrix and do 50-100 push & wait operations
This will not require rebuilding the image, the image can be the same
And after we could catch this issue


Need more seed nodes

We've added seed nodes to init.go, and now need known validators to add their seed nodes directly to that file using a pull request.  Make sure to label your seed as yours.
https://github.com/osmosis-labs/osmosis/blob/main/cmd/osmosisd/cmd/init.go

Kinda not maybe?
The thinking:
We should have validator engagement here on Github, as well.
Maybe I'm wrong about this and maybe we should close the issue, but the way that I'm looking at being a validator across a number of chains is that part of that task overall, is things like this.
Actually have reached out over discord, too.
Maybe I am over-expanding what we should think of validators as doing?
I look at the validator set like 100 engineering team members, each of whom bring unique skills to the table.
https://commonwealth.im/osmosis/proposal/discussion/2036-proposal-per-validator-epoch-bonus-for-better-decentralization
Sort of tied into that.
Does it make sense?

Hey, I'm going to add a node to the file, and will add a few others.
The issue is this:
Infrastructure is dynamic.

We've gotten some more seeds since the issue was made! I don't think this github issue is going to reach more people,  we can brainstorm more ways to get more seeds.


[TASK] Bump Longhorn to v1.7.0-rc4

Is your enhancement related to a problem? Please describe.

To fix the issue longhorn-csi-plugin pods can't reach longhorn-manager on another host.
Describe the solution you'd like

Bump Longhorn to v1.7.0-rc4. And verify the longhorn-csi-plugin pods can reach all longhorn-managers.
Test plan:

in longhorn-csi-plugin pods, curl http://longhorn-backend:9500/v1 repeatedly should work well.

Describe alternatives you've considered

Additional context

tracked within https://github.com/harvester/harvester/issues/6172


⚠ Cioos National CKAN has degraded performance

In 60d1071, Cioos National CKAN (https://catalogue.cioos.ca/) experienced degraded performance:

HTTP code: 200
Response time: 21917 ms

Resolved: Cioos National CKAN performance has improved in 040d751 after 11 minutes.


No longer able to use buffer_setup

Hello, first of all, thank you for writing this plugin! I really like it 👍
Checklist

[x] Have you updated the plugin to the latest version on main branch?
[x] Have you checked the Breaking Changes issue?
[x] Have you read through :h nvim-surround to see if there might be any relevant information there?

Describe the bug
Before the changes in this commit: 306a92830ede75d7d3a48ba04c7e603b73c3f377 I was able to call the buffer_setup method in a FileType autocmd. After this commit I am now receiving an error on config.lua:122.
To Reproduce
Step 1: Open Neovim with nvim -u NONE (assuming nvim-surround is installed in packpath)
Step 2: Enter :lua require('nvim-surround').buffer_setup()
Step 3: You should see the following error:
E5108: Error executing lua .../packer/start/nvim-surround/lua/nvim-surround/config.lua:122: attempt to index field 'keymaps' (a nil value)
stack traceback:
        .../packer/start/nvim-surround/lua/nvim-surround/config.lua:122: in function 'set_keymaps'
        .../packer/start/nvim-surround/lua/nvim-surround/config.lua:268: in function 'buffer_setup'
        ...ck/packer/start/nvim-surround/lua/nvim-surround/init.lua:34: in function 'buffer_setup'
        [string ":lua"]:1: in main chunk

Expected behavior
The call to buffer_setup to be successful.
Thank you for your time!

I decided to do some additional digging by rolling back 1 commit at a time, and it seems that this error supposedly was always there. I am no longer convinced this is a bug in your plugin at this moment so I'll close it for now. If I find out more I'll add info to this conversation. Apologies for the potential noise!

Hmn I'm not sure what it is exactly, the reason I thought it was odd is because I've used it quite often without any warnings and upon updating this issue started to pop up. I've uninstalled all my packer packages, reran the experiment and still same error so I'm a bit clueless how to continue 😅
Instead of digging further I wrote some Lua which fixes the issue for me:
-- what I added
local surround_config = require('nvim-surround.config')
surround_config.user_opts = surround_config.default_opts

-- what I had originally
require('nvim-surround').buffer_setup()

Just putting it out there in case anyone else needs a quick monkeypatch basically :)

Do you have buffer_setup called without setup already called?

Yep! My goal is to not have any "global" mappings as this interferes with some mappings of my own file explorer plugin (in which having surrounds also wouldn't really make sense).
For this reason I decided to use just the buffer_setup function which did work for a while until I started to see this error.

@SidOfc I would recommend you just disable everything for global maps, e.g.
require('nvim-surround').setup({
    keymaps = { normal = false, insert = false, --[[ ... ]] },
})

that should disable everything by default, and then buffer_setup should override it to give you buffer-local maps.

With this in my packer setup:
    use({
      'kylechui/nvim-surround',
      config = function()
        require('nvim-surround').setup({
          keymaps = {
            insert = false,
            insert_line = false,
            normal = false,
            normal_cur = false,
            normal_line = false,
            normal_cur_line = false,
            visual = false,
            visual_line = false,
            delete = false,
            change = false,
          },
        })
      end,
    })

Calling :lua require('nvim-surround').buffer_setup() results in the error I posted in the issue:

This does not seem to look right to me but I could be wrong of course 😅

For reference I'm just using :lua require('nvim-surround').buffer_setup() manually from ex-mode after having loaded my vim configuration file (passing an empty table as argument also doesn't make a difference). At this point everything should have been set up if I am understanding correctly.

Ah this is something that I think is intentional---whatever you call setup with becomes your "global" setup, so wherever you call buffer_setup you'll need to have the table
    keymaps = {
        insert = "<C-g>s",
        insert_line = "<C-g>S",
        normal = "ys",
        normal_cur = "yss",
        normal_line = "yS",
        normal_cur_line = "ySS",
        visual = "S",
        visual_line = "gS",
        delete = "ds",
        change = "cs",
    },

@kylechui I can confirm this works indeed!
Additionally I've actually made some changes to my file explorer plugin. Using nowait = true in its mappings. This allows me to use the regular require('nvim-surround').setup() without any problems.
Thank you very much for your time researching and providing solutions, it is much appreciated!
Your plugin is absolutely wonderful and in my opinion it's a step up from tpope/vim-surround since it can also highlight what will be surrounded :)
This can certainly remain closed, have a good one!


Feat analysis include exclude config parameter

Changes the include parameter to target-include
Changes the exclude parameter to target-exclude
Adds the analysis-include parameter
Adds the analysis-exclude parameter
Adds a file selector class

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 51.763%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
800

Relevant Lines:
1476

💛  - Coveralls


how to start the config server

Write your question here
Screenshots
Where and how could we improve the readme?

Hi @sowndarya123, the configuration is released as a jar, so you can simply start it with java -jar configuration-server.jar
See also our latest releases: https://github.com/inspectIT/inspectit-ocelot/releases/tag/2.1.1


Support transparency

The public API needs to support transparency somehow. I have a way to add it I think, and am going to test in next few hours and maybe PR if it works.
This has been known for a while upstream. Cf. saitoha#28, saitoha#149.

I don’t know how far you’ve gotten, but the first hurdle appears to be that it reads the source image to an RGB buffer.