Saving tags on models who have UUID as a primary key throw error

For models that uses UUID as its PK
class Foo(models.Model):
    foo_id = models.UUIDField(
        primary_key=True,
        default=uuid.uuid4,
        editable=False
    )
    tags = TaggableManager()

When I go and try to add a new tag
f = Foo.objects.latest('pk')
f.tags.add("testing")

I get DataError: integer out of range
When I import pdb on the cursor to view the SQL going in I see this.
(Pdb) params
(1,<PHONE_NUMBER>91563438098836942573405313042, 9)
(Pdb) sql
'INSERT INTO "taggit_taggeditem" ("tag_id", "object_id", "content_type_id") VALUES (%s, %s, %s) RETURNING "taggit_taggedit
m"."id"'

That long integer<PHONE_NUMBER>91563438098836942573405313042) trying to be insterted is obvsiouly the cause for the error. This number is the int of the UUID for foo_id
In [6]: foo.foo_id.int
Out[6]:<PHONE_NUMBER>91563438098836942573405313042

@austinhuminski ran into the same issue. Figure out any solution?

Nevermind, solution was in the custom tagging text docs: https://github.com/alex/django-taggit/blob/1f8c3ded5c62017b09d0cb251b4f966341967125/docs/custom_tagging.txt#L75

This issue should be closed then


Individual Contributor License Agreement link is broken in CONTRIBUTING.md

CONTRIBUTING.md refers to an Individual Contributor License Agreement with a URL of https://www.clahub.com/agreements/Nike-Inc/fastbreak
Loading that URL shows a generic app setup page.
Expected Behavior
Viewing ICLA URL shows the agreement
Current Behavior
This is what I see:

The link to the individual contributor license agreement of https://www.clahub.com/agreements/Nike-Inc/fastbreak now returns a 301 redirect to https://clahub.com, which is currently an article in french about "Rick et Morty". This is amusing, but not helpful.


No static method loadLibrary in class

(Hi @passy, if you're reading this, good to 'see' you again.)
This was previously reported in #10. I get https://pastebin.com/R5zfJtNn when starting up our app. Occurs with 0.5.0 and also with 0.4.1, but not with 0.3.0. Rebooting the Mac, as advised in that issue, did not help. We didn't attempt running with Windows.
Repro steps:
Our app had been running fine with SoLoader 0.4.1 and Fresco 1.9.0. We were doing a lazy-init of SoLoader; it is initialized by Fresco, and we didn't initialize Fresco until loading the first view with an image.
Lately we tried to add Sonar to the app. This requires calling SoLoader.init directly in the Application.onCreate method. This craps out.
The workaround is to downgrade to 0.3.0, but hopefully this can be fixed long term.

@tyronen  did you figured this out? I'm also having this error

Hey! Sorry for the slow response. I'm not entirely sure where this would come from. I don't have a good repro for this, so the best thing I can offer right now is to just publish another release based off master and see if that does anything.

I've put up a 0.5.1 which should trickle through the Maven Central release process within the next hour or so. It would be great to know if that makes any difference at all for you two.

Hi @tyronen :)
The error message complains about lack of void loadLibrary(String) method. Well, it is indeed gone as of https://github.com/facebook/SoLoader/commit/9169960c56e826d49bad66bfeb46fab970664f63#diff-be862dcc6d9e7bd0e7fe754df40a9bca. Seems that your app includes libraries that were compiled against different versions of SoLoader interface.

Ahh, thanks for the explanation, @michalgr!

The interface changed between 4.1 and 5.0. Fresco pulls in SoLoader 5.0 and Sonar pulls in 4.1 and we have a disaster.
Valuable lesson for me: do not let public API to change. I am sorry for that.
@passy: can we update Sonar deps and organize a new release ?

Just started having this problem too a few hours ago..
Can't believe I caught this thread live
@passy after your PR get's approved it should be resolved after a gradle sync?

I'll need to push out a new release too, but that should take care of it.
On Tue, 17 Jul 2018, 17:38 Gadigg<EMAIL_ADDRESS>wrote:

Just started having this problem too a few hours ago..
Can't believe I caught this thread live
@passy https://github.com/passy after your PR get's approved it should
be resolved after a gradle sync?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/facebook/SoLoader/issues/13#issuecomment-405647350,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAmsqftXLiDEvBQypKEMrYpWe89l-fKks5uHhL4gaJpZM4VFZWb
.

--
timezone: eu/london | utc+1
@passy

@passy any ideea how soon will this happen? When will we be able to pass this? :sob:

@cristianonescu The Sonar release? I can do that tomorrow.

Related react-native issue: https://github.com/facebook/react-native/issues/20242#issuecomment-405767309

New Sonar release is out as 0.6.12.

Still working on the long tail of this. Released 1.9.0 of Yoga today which uses the new version of SoLoader will release 0.19.0 of Litho tomorrow which will have both SoLoader >= 0.5.0 and Yoga 1.9.0 as dependency.

0.5.1 still has this issue.

@gengjiawen The SoLoader package is fine. You have an old dependency that is linked against an older version of SoLoader and are mixing it with a > 0.5.1. I'm closing this issue now because I've updated all the packages I have any control over.

@passy Nope, You can see https://github.com/facebook/react-native/pull/20325.


fix: made eval harness more reliable, using Manager

Codecov Report
Attention: Patch coverage is 50.00000% with 26 lines in your changes missing coverage. Please review.

Project coverage is 79.93%. Comparing base (0208e76) to head (bf079eb).
Report is 1 commits behind head on master.

:white_check_mark: All tests successful. No failed tests found.

Files with missing lines
Patch %
Lines

gptme/eval/main.py
51.02%
24 Missing :warning:

gptme/eval/suites/init_projects.py
33.33%
2 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #119      +/-   ##
==========================================
+ Coverage   79.77%   79.93%   +0.15%
==========================================
  Files          49       49
  Lines        2903     2920      +17
==========================================
+ Hits         2316     2334      +18
+ Misses        587      586       -1

Flag
Coverage Δ

anthropic
?

openai
79.93% <50.00%> (+1.97%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


build: Add sonar workflow

This PR introduces the initial version of the SonarCloud workflow. https://github.com/MudBlazor/MudBlazor/issues/9236
Related PR https://github.com/MudBlazor/Workflows/pull/2

Analyzes only the dev branch on push events.

Not included

This PR does not include PR analysis features.

Open todos

We need a new GitHub secret  SONAR_TOKEN for the workflow before we merge this. We can create a token here. Unfortunately, this is a personal access token of a user. There is no token for a project.
Configure/Update the Quality Gate and Quality profile to our needs. Currently, the build defaults are used.

@henon, I would appreciate it if you could add the SONAR_TOKEN to the project secrets.

Done


Vulkan portable raytracing

CI gfxreconstruct build queued with queue ID 178064.

For this to build on Windows you'll need to demote to C++17 - designated initializers are a C++20 feature.

hello @bartosz-muszarski-arm!
we'd like to catch up with your progress on portable raytracing for Vulkan.
you mentioned lately that this branch does not reflect the latest state, so the question:
you think it's possible to update here (or another branch),
allowing us to internally review/discuss and align with current dev?

CI gfxreconstruct build queued with queue ID 240036.

CI gfxreconstruct build # 4637 running.

CI gfxreconstruct build # 4637 failed.

CI gfxreconstruct build queued with queue ID 240051.

hello @bartosz-muszarski-arm!
we'd like to catch up with your progress on portable raytracing for Vulkan. you mentioned lately that this branch does not reflect the latest state, so the question:
you think it's possible to update here (or another branch), allowing us to internally review/discuss and align with current dev?

I'm on it, will update this branch

CI gfxreconstruct build # 4638 running.

CI gfxreconstruct build # 4638 failed.

CI gfxreconstruct build queued with queue ID 241152.

CI gfxreconstruct build # 4664 running.

CI gfxreconstruct build # 4664 failed.


Cassandra Grafana dashboard link broken

Link to Grafana dashboard yields 404.
Line 74 - https://github.com/kudobuilder/operators/blob/master/repository/cassandra/3.11/docs/monitoring.md

This would ideally be fixed in the KUDO C* create_operators_pull_request.py script.

(The link works there: https://github.com/mesosphere/kudo-cassandra-operator/tree/master/monitoring/grafana)

added the fix here https://github.com/mesosphere/kudo-cassandra-operator/pull/141

this is fixed now https://github.com/kudobuilder/operators/blob/master/repository/cassandra/3.11/docs/monitoring.md#2-install-the-grafana-dashboard


Unhandled error event

My Command, was: ffmpeg-gif order_flow.mov order.gif
The error I get is,
events.js:160
      throw er; // Unhandled 'error' event
      ^

Error: spawn ffmpeg ENOENT
    at exports._errnoException (util.js:1036:11)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:193:32)
    at onErrorNT (internal/child_process.js:359:16)
    at _combinedTickCallback (internal/process/next_tick.js:74:11)
    at process._tickCallback (internal/process/next_tick.js:98:9)
    at Module.runMain (module.js:592:11)
    at run (bootstrap_node.js:394:7)
    at startup (bootstrap_node.js:149:9)
    at bootstrap_node.js:509:3

I encounter the same issue, is there any workaround?

Ah, I should have closed that long ago.


feat: theme up, five-fold ready, Testimonials comp up

Current dependencies on/for this PR:

main

PR #11   👈

This stack of pull requests is managed by Graphite.


feat: add parameter flip to the client endpoint

There are four orientations in total for the reMarkable 2 screen: two for portrait and two for landscape.
When the orientation of the reMarkable 2 screen changes, I also want goMarkableStream to rotate.
Since there is already an endpoint parameter portrait to control the portrait or landscape, I add another parameter flip to control if it needs to rotate 180 degrees at each case.

Looks good to me and this fixes https://github.com/owulveryck/goMarkableStream/issues/105


Quic 5 inspector

Quic5 inspector with NFQ based demo application.
TODO

Check for possible endian problems.
Implement salt chooser
Check that the previous quic decoder (for older quic versions) still works

Thanks David! :)


[P2P] refactor: message handling

Description
Before
The P2P module is responsible for handling incoming messages from the router's host. When it receives a message, it calls into the router to unpack the RainTreeMessage (and facilitate further broadcast propagation). The resulting PocketEnvelope is returned to the P2P module to be emitted over the application event bus.
classDiagram
    class RainTreeMessage {
        <<protobuf>>
        +Level uint32
        +Data []byte
        +Nonce uint64
    }

    class PocketEnvelope {
        <<protobuf>>
        +Content *anypb.Any
    }

    RainTreeMessage --* PocketEnvelope : serialized as `Data`

    class P2PModule {
        -handleNetworkData([]byte) error
        -handleStream(stream libp2pNetwork.Stream)
        -readStream(stream libp2pNetwork.Stream)
    }

    class RainTreeRouter {
        +HandleNetworkData func([]byte) ([]byte, error)
    }

    RainTreeRouter --> P2PModule
    P2PModule --> RainTreeRouter
    RainTreeRouter --o RainTreeMessage
    P2PModule --o PocketEnvelope

After
The router encapsulates handling incoming RainTreeMessages, unpacking them and passing them along to the P2P module as PocketEnvelopes to be emitted over the application event bus.
classDiagram
    class RainTreeMessage {
        <<protobuf>>
        +Level uint32
        +Data []byte
        +Nonce uint64
    }

    class PocketEnvelope {
        <<protobuf>>
        +Content *anypb.Any
    }

    RainTreeMessage --* PocketEnvelope : serialized as `Data`

    class P2PModule {
        -handleAppData([]byte) error
    }

    class RainTreeRouter {
        -appDataHandler RouterHandler
        -handleRainTreeMsg([]byte) ([]byte, error)
        -handleStream(stream libp2pNetwork.Stream)
        -readStream(stream libp2pNetwork.Stream)
    }

    RainTreeRouter --> P2PModule : `appDataHandler` == `handleAppData`
    RainTreeRouter --o RainTreeMessage

    P2PModule --o PocketEnvelope

Issue
Second deliverable in #762
Type of change
Please mark the relevant option(s):

[ ] New feature, functionality or library
[ ] Bug fix
[x] Code health or cleanup
[ ] Major breaking change
[ ] Documentation
[ ] Other

List of changes

Added Handler field to RainTreeConfig & BackgroundConfig
Refactored rainTreeRouter logging methods
Renamed rainTreeRouter#HandleNetworkData() to #handleRainTreeMsg()
Renamed p2pModule#handleNetworkData() to #handleAppData()
Added -tags=test to all test make targets
Fixed mockdns usage in TestP2PModule_Insecure_Error test
Moved message handling from p2p module to router

Testing

[ ] make develop_test; if any code changes were made
[ ] make test_e2e on k8s LocalNet; if any code changes were made
[ ] e2e-devnet-test passes tests on DevNet; if any code was changed
[x] Docker Compose LocalNet; if any major functionality was changed or introduced
[x] k8s LocalNet; if any infrastructure or configuration changes were made

Required Checklist

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have added, or updated, godoc format comments on touched members (see: tip.golang.org/doc/comment)
[ ] I have tested my changes using the available tooling
[ ] I have updated the corresponding CHANGELOG

If Applicable Checklist

[ ] I have updated the corresponding README(s); local and/or global
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added, or updated, mermaid.js diagrams in the corresponding README(s)
[ ] I have added, or updated, documentation and mermaid.js diagrams in shared/docs/* if I updated shared/*README(s)

Wdyt about adding the mermaid diagram in the github description to the README for p2p?

@Olshansk I was planning on incorporating the diagrams from #505, which represents the composition of this and #769, into #732. My thinking was that the diagrams in the PRs are trimmed down versions which only show what's relevant for understanding the change, whereas what I expect we want to keep in the repo is the representation of the desired state with sufficient context.
Do you imagine a step in between?


MODFISTO-363 updated FY samples for 2023

Purpose
Describe the purpose of the pull request.
Approach
How does this change fulfill the purpose?
TODOS and Open Questions

[ ] Use GitHub checklists. When solved, check the box and explain the answer.

Learning
Describe the research stage. Add links to blog posts, patterns, libraries or addons used to solve this problem.


Why does for_each not run on initial value?

I was experimenting with reactivity a little bit and noticed something that feels a bit inconsistent: Apparently, with_for_each does not to run on the first/initial value, only on subsequent/updated values. My expectation from other reactive frameworks was that an "effect" would run on all values, including the initial value. This also creates an awkward inconsistency with map, which does run on the initial value as well (well, it has to :wink:).
I'm also a bit confused about with_for_each vs for_each: I vaguely remember seeing plain usages of for_each in older examples, i.e., usages that didn't explicitly hold on to the returned handle. But it looks like it is no longer possible to use just for_each without doing something (what exactly?) with the handle.
The following example summarizes my observations:
use cushy::figures::units::Lp;
use cushy::value::{Dynamic, IntoReader, Source};
use cushy::widget::MakeWidget;
use cushy::widgets::slider::Slidable;
use cushy::Run;

fn main() -> cushy::Result {
    let value = Dynamic::new(50_i32);

    // This doesn't run on the initial value, but subsequent values.
    let value = value.with_for_each(|value| {
        println!("value: {value} [with_for_each]");
    });

    // This doesn't run at all, probably due to dropped handle.
    let _ = value.for_each(|value| {
        println!("value: {value} [for_each, dropped handle]");
    });

    // Interestingly, a "dropped" map runs on the initial value, but not
    // on subsequent values.
    value.map_each(|value| {
        println!("value: {value} [map_each, unused]");
    });

    // This runs on all (initial and subsequent) values.
    let dummy = value.map_each(|value| {
        println!("value: {value} [map_each, used]");
        *value
    });

    "value: "
        .and(value.clone().into_label())
        .and(dummy.clone().into_label())
        .into_columns()
        .centered()
        .and(
            value
                .slider_between(0, 100)
                .width(Lp::points(400)..Lp::points(800)),
        )
        .into_rows()
        .contain()
        .centered()
        .run()
}

My expectation would have been:

a dropped for_each and dropped map would both run never.
a used for_each and used map would both run on all values, including the first.

Is there any deeper reason why that is not the case?

Thank you for trying out Cushy! In short, I've tried to make Cushy as predictable as possible, but clearly the fact that you've been confused by its behavior is an indication I may not be there yet and/or I need better documentation.
To answer the question that is the title of this issue, the reason it doesn't do it is that it doesn't need to. With map_each, the function returns a Dynamic<T> which must already contain the result of invoking the mapping function once. for_each has no such requirement, so I never wrote it to invoke with the initial value.
The reason I like this behavior is that it allows you to make your callback stateful and be able to observe all future values without having to write special logic to ignore the first value. If for_each called its callback with the initial value, such a callback would need to look something like this:
dynamic.for_each({
  let mut first_value = false;
  move |value| {
    if !first_value {
      first_value = true;
      return;
    }

    ....
  }
});

With the current setup, to have your closure invoked with the first value, the code can be written to first store the closure in a variable, use map_ref, then map_each:
    let d = Dynamic::new(0_u8);
    let mut all_values = Vec::new();
    let mut callback = move |value: &u8| {
        all_values.push(*value);
    };
    d.map_ref(&mut callback);
    d.for_each(callback);

I'm also a bit confused about with_for_each vs for_each

The difference is who owns the callback handle. with_for_each is meant to be used in a builder-style pattern like:
let my_dynamic = Dynamic::new(0_u8).with_for_each(...);
The for_each function is designed to be standalone and gives full control over the lifecycle of the attached callback by returning the callback handle.
Regarding your expectations of the example, mappings do not give access to the underlying CallbackHandle. If you wish to have full control over breaking a callback from executing, you must create the linkage directly with for_each as you've seen. The callback created with map_each uses a weak reference to the dynamic being observed. The callback will continue being invoked as long as a strong reference to the underlying dynamic still exists.
All of what I've written are the reasons why or explanations how it's currently designed, but I fully understand how my decisions can feel arbitrary. I'll definitely take your feedback into account and try to improve things in the future -- I also welcome any further feedback or questions! Thank you again!

Update with additional thought: Maybe renaming for_each to for_each_subsequent and adding a new for_each that invokes with every value would be a good solution.

Yes, that would be the simplest solution.
Out of curiosity:

The reason I like this behavior is that it allows you to make your callback stateful and be able to observe all future values without having to write special logic to ignore the first value.

Interesting, so it comes down to what's is the more common use: Observe all values, or all but the first?
From my experience with React/Solid/Leptos, the corresponding mechanisms (useEffect, createEffect, ...) typically always run on the initial value as well. I'm not really familiar with the theoretical foundations in functional reactive programming, but the similarity suggested to me that this is general concept.
My use cases typically always matched these semantics. The standard use case in webapps is probably fetching data (HTTP requests), which should normally be done also for the initial state. If skipping a side effect is needed (be it the initial one, or any subsequent), it is often rather expressed in the value/type, e.g. by using null. Admittedly, making a slider Option<u8> for that purpose would be awkward.
What would be examples where one doesn't want to run the initial side effect? My first use case where I needed the opposite was e.g. this.

The for_each function is designed to be standalone and gives full control over the lifecycle of the attached callback by returning the callback handle.

I forgot that there is actually a difference between let _ = value.for_each(...) and let _handle = value.for_each(...).
And looking at the examples again, I've noticed that the reason why you never have to use a dummy handle on the left-hand-side is because you're using value.for_each(...).persist(). That's the pattern I was missing :+1:

Interesting, so it comes down to what's is the more common use: Observe all values, or all but the first?

Probably not very common. In fact, the lack of emitting the first value can lead to confusion as you point out. I think that's what made me like the idea I came up with after writing my comment initially.

What would be examples where one doesn't want to run the initial side effect?

I personally don't have good examples because I learned a long time ago that I prefer to write idempotent chunks of code as often as possible. In the past I would usually cite examples where you already have a current state and the observing callback should only ever observe updates from the initial state, not the initial state because it was already initialized using the initial state. This could be a callback that is designed to track changes that must be initialized with an initial state first. A properly idempotent callback it doesn't matter if it fires an extra time, but if it's not designed that way, the difference matters.
To me, Cushy shouldn't assume people only write idempotent code, so I want to offer both options.

That's the pattern I was missing

This is good to know! Maybe the must_use hint for CallbackHandle can be improved to hint at persisting it.

Turns out the DebugWindow relies on this in a subtle way :laughing: I did the suggested change and even noted I didn't add a for_each_subesquent to the ForEach. The problem arises not because of needing to track first state, it's due to local thread lock management. In this particular case, the callback needed to lock another dynamic to perform actions on it, but that dynamic was already locked as part of the setup code being executed. By causing for_each to be invoked with the initial value, it caused a deadlock error to be raised.
To work around it without having for_each_subsequent, I would have to do extra lock management which would increase the code complexity. So I'm just going to add ForEach::for_each_subsequentand use it in the DebugWindow implementation.

I guess after 7bd13e2a0a5bff238c45200530db5abbb4ecc5a5 this issue should be fully resolved, right? Thanks for the fix!

There's still a little more macro work to make ForEachCloned::for_each_subsequent_cloned, there was something tricky about that macro that I needed to revisit.

Nevermind, apparently this was completely implemented at some point. While the previously mentioned method does not exist, it doesn't exist on Source either, so it's not missing functionality from what I was doing at the time.
Thanks for noticing and closing!


Tap events are not notified correctly.

Hello.
I have encountered problems using a multi-tap display and i.MX8MP board.
In flutter_elinux_view.h/.cc, instance variable touch_event_ is not initialized, so it contains an garbage value.
Therefore, it is not processed correctly in function GgeTouchPoint().
I think it needs to be initialized as follows:
struct touch_event {
    touch_point points[10] = {
      {false, -1, 0, .0, .0}, {false, -1, 0, .0, .0},
      {false, -1, 0, .0, .0}, {false, -1, 0, .0, .0},
      {false, -1, 0, .0, .0}, {false, -1, 0, .0, .0},
      {false, -1, 0, .0, .0}, {false, -1, 0, .0, .0},
      {false, -1, 0, .0, .0}, {false, -1, 0, .0, .0},
    };
  };

Thank you for reporting the bug.


how is this even possible, like where you get the numbers

Hi, this is possible by using a API, which give you the number and a order id, using this orderid you can check if a verification code appeard. if so we pass it over to discord and verify the account. if not we wait until the code is there. At the moment there is a bug which give some erros when choosing more than 1 Thread. I'm currently working on a fix.

Yo, i updated the code a lot since you created this issue, please try it again with the new version of the code :)

Closing due to some inactivity.


add browsersync plugin to webpack-dev-server

hi,
it would be nice to add this plugin https://github.com/Va1/browser-sync-webpack-plugin to get browsersync features along with webpack-dev-server ones.
i've already implemented in another project and it's working well.
what do you think guys?
i can do this maybe the next week.
cheers.

@phra sounds good. I did the same thing. Looking forward that this here 💯


Better explanation/example of room listeners

Just like the topic says, can you please provide some more examples and/or better explanation on how these room listeners work?
According to your example, the entities property for your state is assumed to be an array, correct? From my experience when the user is removed from the room (via refreshing the page) there is no value, it just returns undefined.
When should I use :id, :string, etc, and what are all the options?
Thanks in advance

Hey @gregmax17, sorry, I'm a bit busy lately because I'm moving abroad, I'll write some more documentation as soon I get back to normal schedule :)

According to your example, the entities property for your state is assumed to be an array, correct?  In that example, entities is assumed to be a dictionary, like:

{
  entities: {
    'playerid1': { x: 0, y: 0 },
    'playerid2': { x: 0, y: 0 },
    'playerid3': { x: 0, y: 0 },
    // ...
  }
}

From my experience when the user is removed from the room (via refreshing the page) there is no value, it just returns undefined.

That's correct. When a remove operation is performed, only the path of the variable that has been removed will be available.

When should I use :id, :string, etc, and what are all the options?

Usually, you can just use :your_own_identifier - to be populated in the path whenever the callback is called. (change.path.your_own_identifier).
You can use :id, :string, :number, :axis to prevent path clashes.
For example:
{
   entities: {
      "player1id": {
        name: "Greg",
        x: 10,
        y: 10
      }
   }
}

Let's say the path entities/playerid1/name has been updated from "Greg" to "gregmax17". If listen for changes using the :axis placeholder, the callback will be triggered only for changes on x and y.
You can see all the built-in placeholders here: https://github.com/endel/delta-listener/#built-in-placeholders
Cheers!

I started writing about this in the wiki: https://github.com/gamestdio/colyseus/wiki/Patch-handling

I'm going to assume any required data to explain state synchronization is explained here, otherwise, feel free to submit a PR here.


Fix typo

Just removed the extra parenthesis, in the code snippet
Fixes #9151

Deploy preview for docsdocker ready!
Built with commit bbc2eebc5553298d929a2967fa24d0013c3f25c0
https://deploy-preview-9164--docsdocker.netlify.com

@thaJeztah correct me if I'm wrong, but it looks like there are two docker statements, hence the two closing parentheses.

Had to double check as well, but this looks correct;
REPLICA_ID=$(docker inspect -f '{{.Name}}' $(docker ps -q -f name=dtr-rethink) | cut -f 3 -d '-')); \
            |                               |--------------------------------|                  |
            |-----------------------------------------------------------------------------------|
``

that last `)` should indeed not be there

Good catch, and thanks for contributing!


Url rewriting not working with .styles() outside Laravel

I am using following config in my webpack.mix.js file
mix.options({
    publicPath: 'assets'
});
mix.styles([
        'assets/v3/plugins/pace/pace-theme-flash.css',
        'assets/v3/plugins/boostrapv3/css/bootstrap.min.css',
        'assets/v3/plugins/font-awesome/css/font-awesome.css',
        'assets/v3/plugins/jquery-scrollbar/jquery.scrollbar.css',
        'assets/v3/framework/css/pages-icons.min.css',
        'assets/v3/framework/css/pages.min.css',
        'assets/v3/framework/css/themes/corporate.min.css',
        'assets/v3/css/style.css'
    ], 'assets/compiled/css/core.css');

But the image/font urls in the files are not rewritten in the final combined file. I am using this outside laravel.
I am using laravel-mix version 2.1.14.

.styles() method runs outside of webpack thus url rewriting does not take place by this method.
I would recommend to create a app.scss file then import your css in there and use mix.scss() method
// app.scss
@import<EMAIL_ADDRESS>@import<EMAIL_ADDRESS>@import<EMAIL_ADDRESS>@import "~vue-multiselect/dist/vue-multiselect.min.css";
@import "~flatpickr/dist/flatpickr.min.css";

mix..sass('./resources/sass/app.scss', './public/css')


Bump version to 3.3.9

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Failing win build caused by a dill dependency that is not installed on windows (https://github.com/conda-forge/dill-feedstock/pull/2)


[Project] GitHub Issue templates: need updated to be GetNighthawk-specific

The GH issue templates - https://github.com/layer5io/getnighthawk/tree/master/.github/ISSUE_TEMPLATE - need to be updated with details and links specific to the GetNighthawk project.

@Grumpyyash?

can I do this task?

@leecalcote can @akashprasher take this

That would be great, yes. 👍

Thanks, @leecalcote, can you tell me what needs to change and what to add? I'll do it.


Not working after migrating from georgezhao2010 version to 0.5.9.

HA版本
2024.9.2
集成版本
0.5.9
之前可正常使用的集成版本
0.3.22
设备类型及型号
Air Conditioner 22396279 (0)
使用的App
Homeassistant
问题详细描述
Not working after migrating from georgezhao2010 version to 0.5.9.
The logs
No response

@goddadel just for a test and a internal reference, can you try downgrading to 0.5.7 ?
Thank you

@goddade just for a test and a internal reference, can you try downgrading to 0.5.7 ? Thank you

Version 0.5.7 works well.

I tried 0.5.9 again, no luck.

I tried 0.5.9 again, no luck.

@goddade
we need debug log and error description to confirm the error.
if you always not provided  the error log and description the error detail, no one can understand it.
also not confirm it's a knonw issue or new issue.
please follow the issue template to report bug.

@goddade just for a test and a internal reference, can you try downgrading to 0.5.7 ? Thank you

from 0.3.22 to 0.5.9......do you understand what's the bug ? and what's the error?

This is the log of version 0.5.7.
The microwave and water purifier are not working.
2024-09-26 00:26:33.467 DEBUG (微波炉) [midealocal.device] [211106238056629] Connection timed out
2024-09-26 00:26:33.470 DEBUG (微波炉) [midealocal.device] [211106238056629] Connecting to <IP_ADDRESS>:6444
2024-09-26 00:26:36.553 DEBUG (微波炉) [midealocal.device] [211106238056629] Connection error
2024-09-26 00:26:36.555 DEBUG (微波炉) [midealocal.device] [211106238056629] Connecting to <IP_ADDRESS>:6444
2024-09-26 00:26:39.625 DEBUG (微波炉) [midealocal.device] [211106238056629] Connection error
2024-09-26 00:26:39.626 DEBUG (微波炉) [midealocal.device] [211106238056629] Enabling device
2024-09-26 00:26:39.626 DEBUG (微波炉) [midealocal.device] [211106238056629] Status update: {'available': False}
2024-09-26 00:26:39.630 ERROR (微波炉) [root] Uncaught thread exception
Traceback (most recent call last):
File "/usr/lib/python3.12/threading.py", line 1075, in _bootstrap_inner
self.run()
File "/srv/homeassistant/lib/python3.12/site-packages/midealocal/device.py", line 515, in run
raise CannotConnect
midealocal.exceptions.CannotConnect
2024-09-26 00:26:45.533 ERROR (净水机) [midealocal.device] [186916977215679] Socket error - Connection closed by peer
2024-09-26 00:26:45.535 DEBUG (净水机) [midealocal.device] [186916977215679] Connecting to <IP_ADDRESS>:6444
2024-09-26 00:26:45.538 DEBUG (净水机) [midealocal.device] [186916977215679] Connection error
2024-09-26 00:26:45.542 DEBUG (净水机) [midealocal.device] [186916977215679] Connecting to <IP_ADDRESS>:6444
2024-09-26 00:26:45.545 DEBUG (净水机) [midealocal.device] [186916977215679] Connection error
2024-09-26 00:26:45.547 DEBUG (净水机) [midealocal.device] [186916977215679] Connecting to <IP_ADDRESS>:6444
2024-09-26 00:26:45.578 DEBUG (净水机) [midealocal.device] [186916977215679] Connection error
2024-09-26 00:26:45.578 DEBUG (净水机) [midealocal.device] [186916977215679] Enabling device
2024-09-26 00:26:45.578 DEBUG (净水机) [midealocal.device] [186916977215679] Status update: {'available': False}
2024-09-26 00:26:45.583 ERROR (净水机) [root] Uncaught thread exception
Traceback (most recent call last):
File "/usr/lib/python3.12/threading.py", line 1075, in _bootstrap_inner
self.run()
File "/srv/homeassistant/lib/python3.12/site-packages/midealocal/device.py", line 515, in run
raise CannotConnect
midealocal.exceptions.CannotConnect

After I disabled and enabled the air conditioner, it worked again.
But version 0.5.7 does not require re enable.

After I disabled and enabled the air conditioner, it worked again.
But version 0.5.7 does not require re enable.

@


Tweak timing parameters for CNI installation

tuning some knobs for CNI installation

@kopiczko could you please take a look?
w/o this change it's like 50% that I end up with:
gcapeverde-rf2pm                     NotReady   control-plane,master   42m   v1.22.5+vmware.1
gcapeverde-worker-5d9c447686-2b7gt   NotReady   <none>                 41m   v1.22.5+vmware.1
gcapeverde-worker-5d9c447686-bl5w2   NotReady   <none>                 40m   v1.22.5+vmware.1
gcapeverde-worker-5d9c447686-p2fmn   NotReady   <none>                 41m   v1.22.5+vmware.1

I don't think this is the way to go. If flux is stuck then you can use this workaround https://gigantic.slack.com/archives/CLPMFRVU6/p1681997344382939?thread_ts=1681386408.659829&cid=CLPMFRVU6. Also in the newest release I added spec.dependsOn to coredns and cloud-provider-vsphere HelmRelease CRs which means only cilium has to be reconciled at the beginning which should help as well.

ok closing, the CNI installation using the HelmRelease mechanism is still not 100% reliable though, but I have a workaround


OpenCVSharp Version 4.5 depends on mfplat.dll/ Windows Essentials Media Pack

Summary of your issue
We are having issues on multiple Windows 2012 R2 Servers with the same error as in the issue #589
Because the issue is closed I am opening a new one. I am hoping there is a solution without installing the Feature Packs. Thanks for any kind of help/info.
Environment
Windows Server 2012 R2. Recreatable with the newest 4.5 release, the last 4.4 rlease and the last 4.3 release.
What did you do when you faced the problem?
Installing Windows Server Essentials Feature and Windows Essentials Media Pack (https://www.microsoft.com/en-us/download/details.aspx?id=40837) fixed the issue on one System.
Example code:
  using (Mat image = new Mat(filePath))
            {
                Cv2.Resize(image, image, new Size(Width * 0.5, Height * 0.5));
                double newResolutionX = HorizontalResolution * 0.5;
                double newResolutionY = VerticalResolution * 0.5;
                int newWidth = image.Image.Cols;
                int newHeight = image.Image.Rows;

                double cmToInch = 0.393701;

                using (Mat croppedImage = new Mat(image.Image, new Rect(
                    (int)(leftEdgeIgnorance * cmToInch * newResolutionX),
                        (int)(topEdgeIgnorance * cmToInch * newResolutionY),
                        (int)(newWidth - (rightEdgeIgnorance + leftEdgeIgnorance) * cmToInch * newResolutionX),
                        (int)(newHeight - (topEdgeIgnorance + bottomEdgeIgnorance) * cmToInch * newResolutionY))))
                {
                    Cv2.CvtColor(croppedImage, croppedImage, ColorConversionCodes.BGR2GRAY);

                    int kernelSize = (int)(0.06 * newResolutionX);
                    if (kernelSize % 2 == 0) kernelSize++;
                    double sigmaX = 0.02 * newResolutionX;

                    Cv2.GaussianBlur(croppedImage, croppedImage, new Size(kernelSize, kernelSize), sigmaX);

                    int newBlockSize = (int)(0.18d * (newResolutionX * 0.5) * 2d);
                    if (newBlockSize % 2 == 0)
                        newBlockSize++;
                    Cv2.AdaptiveThreshold(croppedImage, croppedImage, 255, OpenCvSharp.AdaptiveThresholdTypes.GaussianC, ThresholdTypes.Binary, newBlockSize, 3);
                    whitePixels = croppedImage.CountNonZero();
                    imagePixels = croppedImage.Cols * croppedImage.Rows;
                }
            }

Output:
Failed to detect whether JPEG is blank.
   bei Imaging.Picture.DetectBlankPage(Double minEmptyPixels, Double leftEdgeIgnorance, Double rightEdgeIgnorance, Double topEdgeIgnorance, Double bottomEdgeIgnorance)
   bei Imaging.Picture.RemoveBlank(String sourceFile, Double minEmptyPixels, Boolean useOriginalCompression, Int32 quality, Double leftEdgeIgnorance, Double rightEdgeIgnorance, Double topEdgeIgnorance, Double bottomEdgeIgnorance)
Der Typeninitialisierer für "OpenCvSharp.Internal.NativeMethods" hat eine Ausnahme verursacht.
   bei OpenCvSharp.Internal.NativeMethods.imgcodecs_imdecode_vector(Byte* buf, Int32 bufLength, Int32 flags, IntPtr& returnValue)
   bei OpenCvSharp.Cv2.ImDecode(ReadOnlySpan`1 span, ImreadModes flags)
   bei OpenCvSharp.Cv2.ImDecode(Byte[] buf, ImreadModes flags)
   bei ITAMS.Imaging.Picture.ItamsImage.LoadImageIntoMat()
   bei ITAMS.Imaging.Picture.ItamsImage.IsImageBlankV3(Double minEmptyPixels, Double leftEdgeIgnorance, Double rightEdgeIgnorance, Double topEdgeIgnorance, Double bottomEdgeIgnorance)
Die DLL "OpenCvSharpExtern": Das angegebene Modul wurde nicht gefunden. (Ausnahme von HRESULT: 0x8007007E) kann nicht geladen werden.
   bei OpenCvSharp.Internal.NativeMethods.redirectError(CvErrorCallback errCallback, IntPtr userdata, IntPtr& prevUserdata)
   bei OpenCvSharp.Internal.NativeMethods.LoadLibraries(IEnumerable`1 additionalPaths)
   bei OpenCvSharp.Internal.NativeMethods..cctor()

Translation: The type initializer for "OpenCvSharp.Internal.NativeMethods" has caused an exception.
DLL "OpenCvSharpExtern": The selected module could not be found. (Exception with HRESULT: 0x8007007E) can not be loaded.
What did you intend to be?
I am not sure whether it is possible to be independent of these Windows dll´s?

As an update we reproduced this issue only when the software is running in 64 bit. 32 bit works fine. We tried the latest 4.5, 4.3, and 4.1.1 releases. The only one working without the windows features is the release 4.0.1. We will role back our OpenCv Version to this Version for now.


Avoid iterating over classList using for..of

This fails in browsers which do not support Iterable on DOMTokenList, such as Googlebot.

Is there a compatibility table for googlebot somewhere?

Not sure. But also, just because something is identifying as "Googlebot", it doesn't mean that it is in fact Googlebot. It could be a rogue bot, but it still logs exceptions.


switch to tiny.en-q8_0 whisper model

q5_1 isn't much faster and may cause quality degradation. It's better to be on the safer side and go with q8_0, which is still blazingly fast (at least on my Pixel 7, but there isn't any noticable speed difference).

https://github.com/soupslurpr/Transcribro/blob/master/app%2Fsrc%2Fmain%2Fkotlin%2Fdev%2Fsoupslurpr%2Ftranscribro%2Frecognitionservice%2FMainRecognitionService.kt#L70
This still refers to old version(?)

You're correct, my bad lol!


How to train Sparsecontrol?

Your work is very valuable and has a good role in promoting the field of video generation.
I would like to ask how Sparse Control modules are trained, and it would be great if the training code could be released.
With best wishes

I second, third and fourth this!

I would also like to know if there is any information about SparseCtrl training. Thanks!


update to 0.13.1

With this PR and the other, fsrs-browser passes its tests.

Is it OK to Squash and merge this PR? Or you prefer to rebase or merge commit?

I'm okay with whatever you prefer!

Just checking - is there a reason why there's an empty commit? I know you prefer minimalism, so just checking.

Just checking - is there a reason why there's an empty commit? I know you prefer minimalism, so just wondering.

The GitHub action doesn't work, so I merge the main branch into fsrs-browser manually in my local device. It generated the empty commit.

so I merge the main branch into fsrs-browser manually in my local device

I believe it failed because
Already on 'fsrs-browser'
Your branch is up to date with 'origin/fsrs-browser'.
Already up to date.

https://github.com/open-spaced-repetition/fsrs-rs/actions/runs/8733011449/job/23960915778#step:5:33
Which is why the merge commit was empty. I think if I add --no-ff  to the git command it will not fast-forward and generate merge commits as you did. The original article uses this. I removed it because I thought you would prefer it. I can add it back if you want :) also please don't hesitate to @ me if that action doesn't do what you want.

Which is why the merge commit was empty. I think if I add --no-ff  to the git command it will not fast-forward and generate merge commits as you did. The original article uses this. I removed it because I thought you would prefer it. I can add it back if you want :)

Could you add it back? Thanks!


{{ model.name }} via RPC resolves to 'request' instead of the model name

Describe the bug
The model object appears to store 'request' instead of the model name when generating SQL in the IDE
Steps To Reproduce

In dbt Cloud, create a new model with the following jinja:

-- {{ model }}
--
-- {{ model.name }}
--
-- {{ this }}

Click 'compile sql' and observe the model name resolve to 'request' instead of your model name
Run the model in the IDE, and observe the correct model name resolve

Expected behavior
Generated SQL resolves to the model name rather than 'request'
Screenshots and log output
Loom link: https://www.loom.com/share/568facc746f04064819aa8442f5abc97
System information
Which database are you using dbt with?

[ ] postgres
[ ] redshift
[ x] bigquery
[ ] snowflake
[ ] other (specify: ____________)

The output of dbt --version:
0.20.2

The operating system you're using:
dbt Cloud
The output of python --version:
n/a
Additional context
Add any other context about the problem here.

@saraleon1 Thanks for the detailed report! You're totally right. Unfortunately, this is a limitation of how interactive SQL commands (compile_sql, run_sql) are implemented in the RPC server today. While it's possible to compile/run with project context, it isn't possible to compile/run arbitrary SQL with the context of a specific node.
dbt does create a placeholder node for interactive RPC requests—and it's named request. (Ugh.) I think we could do a better job here, along the lines of the proposal(s) in https://github.com/dbt-labs/dbt/issues/3587. Given that a significant rework of the dbt Server is in our near-term future, which will include a top-to-bottom rethink of how we support interactive SQL requests, I think we ought to tackle this issue in the context of that broader effort.
In the meantime, so long as dbt doesn't think it's compiling/running a particular model, rather than compiling/running a chunk of SQL named request, dbt-Jinja expressions such as model, this, and is_incremental() won't return correct results.
I'm going to close this as a dupe of #3587.


chore: set up chromatic

Description
Fixes https://github.com/appsmithorg/appsmith/issues/26702
Type of change

Chore (housekeeping or task changes that don't impact user perception)

How Has This Been Tested?

Manual on storybook
Manual on main repo
Jest
Cypress

Test Plan

Add Testsmith test cases links that relate to this PR

Issues raised during DP testing

Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR)

Checklist:
Dev activity

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

QA activity:

[ ] Test plan has been approved by relevant developers
[ ] Test plan has been peer reviewed by QA
[ ] Cypress test cases have been added and approved by either SDET or manual QA
[ ] Organized project review call with relevant stakeholders after Round 1/2 of QA
[ ] Added Test Plan Approved label after reveiwing all Cypress test

@tanvibhakta Please publish the findings of your POC.

@albinAppsmith

Please publish the findings of your POC.

This is not the POC, this is the implementation. The POC document for testing strategy is here.

@albinAppsmith

Please publish the findings of your POC.

This is not the POC, this is the implementation. The POC document for testing strategy is here.

I mean the POC you did for commenting functionality.

@albinAppsmith I didn't do a POC for commenting functionality, I wanted to implement it. But when I was attempting to, you said you had already done it and it wasn't working.

I wasn't able to find any details of your POC, but based on the conversation in the screenshot and your strong recommendation that chromatic should be triggered on every push, I've built this functionality (which now works).

I'm not talking about my POC, since I haven't made the POC findings, you did the POC again and you made me merge the PR.

And as per your this conversation, I'm curious to know your findings around on-demand. And we merged all the below PRs for you to just do that POC.
https://github.com/appsmithorg/design-system/pull/618
https://github.com/appsmithorg/design-system/pull/623
https://github.com/appsmithorg/design-system/pull/625

you did the POC again and you made me merge the PR.

I didn't do the POC again, I was attempting the implementation. This is the final version of that implementation, based on the conversation we had on Friday, with chromatic builds that work.

https://github.com/appsmithorg/design-system/pull/618
https://github.com/appsmithorg/design-system/pull/623
https://github.com/appsmithorg/design-system/pull/625
All of those were test PRs, this is the final PRs.
I'm afraid I don't understand what you're expecting from me here. If you're hoping for a POC document then I would refer you to the testing strategy document. If you have further questions would you like to get on a call with me - perhaps that will help?

No @tanvibhakta  what I'm saying is,
Before merging that on-demand PR, I mentioned it will not work because I already did a POC for that. You still wanted to merge that PR and now in this PR you are deleting all what you merged that time. So my question is to publish the finding of  why you are deleting on-demand workflow code. That time you convinced me that on-demand is the way to go and now why are you falling back to on commit workflow? I'm just curious about what changed your mind because this is the exact thing I was telling you last to last Friday.
cc: @rohitagarwal88

Thanks for your clarification, @albinAppsmith!

Before merging that on-demand PR, I mentioned it will not work because I already did a POC for that.

And I told you that I didn't understand what the results of your POC was because I couldn't find any details of the POC or the results, nor were you able to provide me with anything.

You still wanted to merge that PR

Like with all code that is new to engineers, I understand what is happening better by doing. So I made modifications to your PR to understand what was happening.
As I am sure you are aware, workflows get triggered from what is on release. This is something you've done multiple times as well when you don't understand exactly how a workflow works

I was following the precedent you set up earlier on how to set up a workflow within the app, before I found a better way to test workflows out.

and now in this PR you are deleting all what you merged that time.

I'm not actually deleting anything I merged last time, I'm deleting the workflow you made the POC for that didn't work. Since the workflow was not being run, or being used, I replaced it with something that does. Can you please help me understand what you would have preferred my course of action to be here?

So my question is to publish the finding of why you are deleting on-demand workflow code.

Because it doesn't work.

That time you convinced me that on-demand is the way to go and now why are you falling back to on commit workflow?

 Since you were very sure of the results of your POC, and my priority was to get chromatic up and running foremost, I took your suggestion into account and published a simple chromatic build script. Given that we hadn't yet tried the TurboSnap approach, I figured I would give that a shot instead. What is the alternative course of action you would suggest here?

I'm just curious about what changed your mind because this is the exact thing I was telling you last to last Friday.

You, and your conversation changed my mind. When there's a conflict I prefer to disagree but commit instead of moving on in my own direction, because that way at least the team can move. You had some really strong opinions about how the workflow should be so I decided to take it into account.
I want to remind you that we decided to move ahead with chromatic because we decided to deprioritise unit tests, and this was a conversation we had perhaps three weeks ago - @rohitagarwal88's fathom note taker will be able to verify this.

@albinAppsmith
The task https://github.com/appsmithorg/appsmith/issues/26702 has also existed for three weeks, and the scope for this task has been written out quite clearly. Could you please make an effort to review the board periodically or during the sprint planning sessions and bring up any concerns you have during scoping so that we avoid these long, time consuming conversations after the work has already been done, and you have the context you would like?


Go back function

The function emy.goBack() doesn’t work.
L 220 : showView wait for an element view, not an id.
L 227 The first navStack.pop() contains the current view. The old function
does a showView on the… current view so ; and that’s not what we
expect.
I test if the navStack.pop return the currentView. If its the current
view, i do a second navStack.pop() and it returns the right previous
view.

i just tested your commit and it doesn't seem to work as expected either?

I remember that it doesn't work either ; sorry for that.

Should we close this PR ?
There is definitely a massive bug in the showView, or actually more in the goBack stack.
Not really something we can fix while keeping the iUI-like anchor-based navigation mechanism imho (which is btw broken with AppCache on iOS)
HTML5 History API seems the only way to do this properly.


Difficulty in block page is not correct

Difficulty of block N is weight of block N - weight of block N-1

PR was merged


dc/129 press enter key for securitykey input

Pull Request Details
What issue does this PR address

Press the enter key to perform the same action as clicking the OK button in the security key input widget.

Link to associated issue: #129

Checklist
Complete the check-list below to ensure your branch is ready for PR.
Flutter Style Guide: https://survivor.togaware.com/gnulinux/flutter-style.html

[x] Screenshots included in linked issue
[x] Changes adhere to the team style and coding guideline
[x] No confidential information
[x] No duplicated content
[ ] No lint check errors related to your changes (make prep or flutter analyze lib)
[ ] Pre-exisiting lint errors noted: [HERE]
[x] Tested on at least one device

[ ] Android Phone
[ ] Android Emulator
[ ] Chrome on Android
[ ] Chrome
[ ] iOS
[x] Linux
[ ] MacOS
[ ] Windows

[x] Added 2 reviewers (or 1 for private repositories then they add another)

Finalising
Once PR discussion is complete and 2 reviewers have approved:

[ ] Merge dev into the branch
[ ] Resolve any conflicts
[ ] Add one line summary into CHANGELOG.md
[ ] Bump appropriate version number in pubspec.yaml
[ ] Push to git repository and review
[ ] Merge PR into dev

Please see the screenshot and comment here https://github.com/anusii/solidpod/issues/129#issuecomment-2141263588


Incorrect pipeline total element count for bst track

See original issue on GitLab
In GitLab by [Gitlab user @tristanvb] on Jul 19, 2017, 08:32
When running bst track without --deps all, the pipeline status area still shows a total element count inclusive of the track target's elements, even though the intention (and behavior) is only to track a single element.
This may also be true in other scenarios like with bst fetch, the counter should be changed to be based on the real list of elements which are queued for scheduling.

In GitLab by [Gitlab user @juergbi] on Jul 24, 2017, 11:28
As far as I can tell, it currently shows both, the number of session elements (i.e., 1 in the above bst track case) and the total number of elements (always counting all dependencies). It may indeed be confusing to show the total element count in the status area, especially as it's formatted like progress (1/42).
I propose to drop the total element count from the status area and add a counter of processed elements instead, i.e., how many elements have passed through the whole pipeline. And keep the number of session elements. Or did you have something else in mind?

In GitLab by [Gitlab user @tristanvb] on Jul 26, 2017, 15:48
Ok so this is a bit confusing.
What you say is literally correct (about pipeline total vs session count).
However, the use case is basically something we derived from YBD's counter, we want to know:

How many total elements there are for a build
How many of those elements needed to be built in this session
How many elements have we built so far in this session

What I have in mind for the status area is to reflect that information, the last bit is represented in the scheduler queues, and the first two are in the first status line.
In this light, I suppose that it does not make sense to include the "total elements" in the status area for any bst commands where this does not make sense:

It makes sense for a build
It does not make sense at all for bst track, because bst track will do unconditional processing on each element
It might make sense for bst fetch, if we first filter out any already consistent sources from the session elements fed to the scheduler (i.e. fetching 8/26 elements makes sense)
It also might make sense for a potential bst push command, where we can first consult the summary and say "Pushing 3/26 elements", by filtering out any elements which already exist on the server from the scheduler input.

In GitLab by [Gitlab user @tlater] on Sep 25, 2017, 10:57
created branch 48-incorrect-pipeline-total-element-count-for-bst-track


Store Metric data in ODIMRA db

Get below metric data from southbound and store it in DB

MetricDefinitionCollection
MetricReportDefinitionCollection
MetricReportCollection
TriggerCollection

issue created in LFN jira portal


approach to defining associations between subnets & related resources

Currently, the code creates a list of subnets like this:
  subnet_prefixes     = ["<IP_ADDRESS>/24", "<IP_ADDRESS>/24", "<IP_ADDRESS>/24"]
  subnet_names        = ["subnet1", "subnet2", "subnet3"]

& associations are done like this (this example illustrates service delegations:
  subnet_service_endpoints = {
    subnet1 = ["Microsoft.Storage"]
    subnet2 = ["Microsoft.Sql", "Microsoft.AzureActiveDirectory"]
  }

A more "terraform-like" way to do this is illustrated in this repository:
https://github.com/Azure/terraform-azurerm-subnets
An example from this project:
  subnets = {
    subnet0 = {
      address_prefixes                          = ["<IP_ADDRESS>/24"]
      private_endpoint_network_policies_enabled = false
      service_endpoints = [
        "Microsoft.Storage", "Microsoft.Sql"
      ]
      delegations = [
        {
          name = "Microsoft.Sql.managedInstances"
          service_delegation = {
            name = "Microsoft.Sql/managedInstances"
            actions = [
              "Microsoft.Network/virtualNetworks/subnets/join/action",
              "Microsoft.Network/virtualNetworks/subnets/prepareNetworkPolicies/action",
              "Microsoft.Network/virtualNetworks/subnets/unprepareNetworkPolicies/action",
            ]
          }
        }
      ]
    }
    subnet1 = {
      address_prefixes                          = ["<IP_ADDRESS>/24"]
      private_endpoint_network_policies_enabled = false
      service_endpoints                         = ["Microsoft.AzureActiveDirectory"]
    }

This is better as it allows you to specify the subnet hierarchy as a typed variable, instead of the current method which is more prone to error.
It also improves readability as the number of subnets grows, since the information relating to a subnet is in the same object definition.
@herms14 - would you support a PR to align to this approach?

also - the above repository says:

For the new infrastructure, you should use this module instead of terraform-azurerm-vnet. For existing infrastructure, we'll maintain terraform-azurerm-vnet module, fix bugs and amend new features.

Hi @kewalaka,
Thanks for the feedback. You are right, the subnet should be converted into an object to support all of those dependencies. I'm working on improving this and is scheduled for the next update. Will update once it has been released.
Thanks!

@herms14 no worries glad to contribute help 🙂  I was just checking before I created something, but what I was going to propose was to swap out the main body of the code for the content here - https://github.com/Azure/terraform-azurerm-subnets
There will be some features we may need to fold back in, but I think that's a better starting point.    I'll raise a PR to illustrate, hopefully in the next couple days.

Hi @kewalaka , I already have the code ready and is pending review by the AVM core team. Will update once PR has been approved.


Integrate Book Description API

To get the genre, rating and description of the selected book

Currently, we have used the dummy data to get an idea of that.


Feature Proposal: Plugin Architecture for Custom Prompt Interfaces

Issue
Problem
As aider grows in functionality, users will have varying preferences for the prompt interface—much like how users prefer different shells (e.g., bash, zsh, fish). Managing all these preferences through a single configuration file could lead to overwhelming complexity and conflicts, making it difficult to satisfy everyone’s preferences in a maintainable way.
Proposed Solution
Introduce a plugin architecture for aider that allows different prompt interface projects to be created and swapped out easily. This would allow developers and users to customize the prompt interface by using plugins, rather than overloading the main configuration file with an ever-growing list of options. These plugins could be developed and maintained by different contributors or communities, allowing innovation and competition between various prompt styles.
Example Use Case

Default Interface: A basic, out-of-the-box prompt interface comes bundled with aider for general use.
Custom Interfaces: Users can download or create plugins to replace the default prompt interface with customized versions that better fit their preferences (e.g., minimalist prompt, advanced autocomplete, themed prompts).
Swapping Prompt Interfaces: Users can easily switch between different prompt interfaces by installing and selecting a plugin, allowing them to experiment with new prompt styles or features without modifying the core functionality of aider.

Why This is Useful

Customization: Enables deep customization of the user interface, allowing users to tailor their interaction with aider to their specific needs or preferences.
Modularity: Keeps the core of aider lightweight and focused by delegating prompt interface complexity to external, interchangeable plugins.
Innovation: Encourages the community to create new prompt interfaces that can cater to specific workflows or preferences, leading to innovative solutions for various user needs.
Flexibility: Users can choose interfaces that suit their current workflow and change them as their needs evolve, without being constrained by a single design.

Conclusion
By introducing a plugin architecture for the prompt interface, aider could provide a flexible, customizable experience that adapts to the diverse needs of its user base, much like how shell environments have evolved to accommodate different preferences.
Version and model info
No response

Just an idea for the long run. Obvioulsy, not necessarily a short-term need...

This looks like a duplicate of #895, so I'm going to close it so discussion can happen there. Please let me know if you think it's actually a distinct issue.


Some special characters confuse matches()

Certain special characters (amperstands, question marks)? seem to confuse matches() and cause no result to be returned even if the given string exists in the collection being searched.
Example code (problem in comments):
const flatDb = require('flat-db');

let link = new flatDb.Collection('links', {
  link: '',
  tags: []
});

link.add({
    link : 'https://www.youtube.com/watch?v=XthcNLnnlug&feature=youtu.be&t=3m35s',
    tags: ['vr', 'ai']
});

link.add({
    link: "https://www.newscientist.com/article/mg22830412-800-earthquake-artificial-intelligence-knows-where-damage-is-worst/",
    tags: ['vr', 'ai']
})

//Will not be found
let youtubeLink : Array<Object>;
youtubeLink = link.find()
    .matches('link', "https://www.youtube.com/watch?v=XthcNLnnlug&feature=youtu.be&t=3m35s")
    .run();

//Found as expected
let newScientistLink : Array<Object>;
newScientistLink = link.find()
    .matches('link', "https://www.newscientist.com/article/mg22830412-800-earthquake-artificial-intelligence-knows-where-damage-is-worst/")
    .run();

console.log(link.all()); //has the youtube link
console.log(youtubeLink); //empty
console.log(newScientistLink); //has the new scientist link

The problem is you need to escape the regex in match(). PR is coming.

@insprintorob  Yes, you're correct. I'm going to merge pr now.

@insprintorob The changes have been applied to v2.1.16, so I would close this issue now.


OnPress opacity changed

Hey !
I've removed the opacity when you click on a TabIcon to look like the real iOS Tab Bar.

Could we make it configurable? Some users may want opacity change.

For the moment no, I will do it later today.

What is default opacity ? Will opacity work if no props is given?

The default opacity is 0.
Yes it works, I've just tried.


License?

Please include a license file and copyright declaration. Optionally, place a license header in the source files.

Thanks for this feedback, but license is a little bit problematic. I have cloned the project from this one: https://github.com/MatrixFrog/scribedroid There is no license file and I am not confident how to deal with your request. Most of the code is written by Tyler Breisacher and I do not know what is his idea for license. I will ask him.

Thanks for this feedback, but license is a little bit problematic. I have cloned the project from this one: https://github.com/MatrixFrog/scribedroid There is no license file and I am not confident how to deal with your request. Most of the code is written by Tyler Breisacher and I do not know what is his idea for license. I will ask him.

It is solved.


make integration issue

trying to run the integration test and this is failing. After debugging, it seems the issue is coming to the fetch_macaroon() function.
docker ps -q -f status=running -f name="${PWD##*/}_$1_" is returning without any output.
if I remove -f name="${PWD##*/}_$1_" then I have a list of container running.
I am running/just updated my docker, and docker compose is v2. our documentation mention compatibility with v1, so maybe this is related. but v2 comes now installed by default so we should support it if this is the issue

we have moved to docker compose v2


I have a problem with the installation.

I have a problem with the installation.
When I call composer require --dev divix1988 / laminas-cli-commands I always get the following error message
Problem 1
- Root composer.json requires divix1988/laminas-cli-commands ^1.1 -> satisfiable by divix1988/laminas-cli-commands[1.1].
- divix1988/laminas-cli-commands 1.1 requires laminas/laminas-cli ^0.1.4 -> found laminas/laminas-cli[0.1.4, 0.1.5, 0.1.6] but it conflicts with your root composer.json require (^1.1.1).

@WDSB  sorry for late response.
I have updated the the dependencies to match the latest versions. You should be able to include divix1988/laminas-cli-commands now into your project. Just make sure to target the newest 1.3.1 release at least:
composer require --dev divix1988/laminas-cli-commands 1.3.1
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Package operations: 1 install, 0 updates, 0 removals
  - Installing divix1988/laminas-cli-commands (1.3.1): Downloading (100%)
Writing lock file
Generating autoload files
composer/package-versions-deprecated: Generating version class...
composer/package-versions-deprecated: ...done generating version class

Let me know if you get any more issues.


update Traefik image to latest 1.7.x release

What this PR does / why we need it:
update Traefik image to latest 1.7.x release
Which issue (if any) this PR fixes:
Fixes # n/a
Any other useful info:
I've been running this since 04/17/20 without problems.

Using tag 1.7 should reference the latest 1.7 cut (which is 1.7.24 at the moment), according to this: https://hub.docker.com/_/traefik.
By changing to something more specific we're pinning to that minor version, which is not what we want.

GTK: lesson learned!


err: max fee per gas less than block base fee mainnet

Thanks for filing a bug report :-)
making this just for our record
Steps to Reproduce

Open a channel on the mainnet

We need to adjust the gas fee on the meta mask
Expected Result
Actual Result
err: max fee per gas less than block base fee: address 0xCDFC863705eb4c55cf59458d0879EE4549137140, maxFeePerGas:<PHONE_NUMBER>2 baseFee:<PHONE_NUMBER>1 (supplied gas 220248)

2021-09-20T13:50:41.921Z #13262975 [info] 	=> %c action     {"type":"channel/open/request","payload":{"deposit":{"_hex":"0x8ac7230489e80000","_isBigNumber":true}},"meta":{"tokenNetwork":"0x5F41Ff141B64c684F224B7748413F282c5Ef9428","partner":"0xcaCff1D95d55d49f0C3BeaBf179F3Aa2cb8b7469"}}
2021-09-20T13:50:46.984Z #13262977 [info] 	=> %c action     {"type":"block/time","payload":{"blockTime":13550}}
2021-09-20T13:50:47.389Z #13262977 [info] 	=> %c action     {"type":"block/gasPrice","payload":{"gasPrice":{"_hex":"0x15a6271497","_isBigNumber":true}}}
2021-09-20T13:51:07.856Z #13262978 [info] 	=> %c action     {"type":"block/gasPrice","payload":{"gasPrice":{"_hex":"0x14c8df87fd","_isBigNumber":true}}}
2021-09-20T13:51:12.433Z #13262979 [info] 	=> %c action     {"type":"block/gasPrice","payload":{"gasPrice":{"_hex":"0x14193d1405","_isBigNumber":true}}}
2021-09-20T13:51:27.666Z #13262983 [info] 	=> %c action     {"type":"block/gasPrice","payload":{"gasPrice":{"_hex":"0x1135734daa","_isBigNumber":true}}}
2021-09-20T13:51:47.744Z #13262985 [info] 	=> %c action     {"type":"block/gasPrice","payload":{"gasPrice":{"_hex":"0x1252e637b7","_isBigNumber":true}}}
2021-09-20T13:51:48.122Z #13262985 [info] 	=> retryWhile giving up {"count":0,"maxRetries":10} {"code":-32000,"message":"err: max fee per gas less than block base fee: address 0xCDFC863705eb4c55cf59458d0879EE4549137140, maxFeePerGas:<PHONE_NUMBER>2 baseFee:<PHONE_NUMBER>1 (supplied gas 220248)"}
2021-09-20T13:51:48.126Z #13262985 [info] 	=> %c action     {"type":"channel/open/failure","payload":{"code":-32000,"message":"err: max fee per gas less than block base fee: address 0xCDFC863705eb4c55cf59458d0879EE4549137140, maxFeePerGas:<PHONE_NUMBER>2 baseFee:<PHONE_NUMBER>1 (supplied gas 220248)"},"meta":{"tokenNetwork":"0x5F41Ff141B64c684F224B7748413F282c5Ef9428","partner":"0xcaCff1D95d55d49f0C3BeaBf179F3Aa2cb8b7469"},"error":true}

Logs:
raiden_0xB161070B755EEfE31151575455C7B12a102f0E53_2021-09-20T14 00 51.599Z.log

I get this again during UDC deposit as well.
logs
raiden_0xB161070B755EEfE31151575455C7B12a102f0E53_2021-09-20T16 07 32.226Z.log
Error

I tried the UDC deposit a few more times but it always fails.
@andrevmatos care to have a look here. ?
Uploading raiden_0xB161070B755EEfE31151575455C7B12a102f0E53_2021-09-20T16 15 18.260Z.log…

Tested it on the mainnet  with  a deposit. Works
https://etherscan.io/tx/0xa2704ed647a8751bb69745c05ba22a097bede88ee889d13139629c22350a2345


Characters Are Opponents an Players

What feature do you want to get added on the base engine?
You should make the characters a folder an put 2 .jsons one as 'mom' an 'bf-mom' an put the sprites in there, something like FNF Multiplayer
example:
https://user-images.githubusercontent.com/66497511/148302763-5f9d4aa2-bed5-4eea-9287-2dd1cf32f329.mp4
To test your sight, and reliability, please select the option of what should NOT be requested.
Useful feature

🗿🗿🗿🗿🗿🗿🗿🗿🗿🗿🗿🗿🗿🗿🗿🗿🗿🗿🗿🗿🗿🗿🗿🗿

useful feature moment


onlyoffice-bin: fixes Icon location

Description of changes

fixes: https://github.com/NixOS/nixpkgs/issues/197385
Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[X] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Nit: commit messages should be written in imperative style, so please use "fix" instead of "fixes". And lower-case "icon"?

any update on this? thanks

I'm going to update this PR this weekend.

Any updates?

Here in Plasma it hasn't arrived yet, I'm waiting for it.

Result of nixpkgs-review pr 197434 run on x86_64-linux 1

1 package built:

onlyoffice-bin


[Bug]:

Minimal, reproducible example
margin: {
                top: "26mm", bottom: "14mm", left: "14mm", right: 0,
            },
            format: "A4",
            displayHeaderFooter: true,
            omitBackground: true,
            webkit_print_color_adjust: "exact",
            printBackground: true,
            encoding: 'utf-8'

Error string
Chinese garbled characters
Bug behavior

[ ] Flaky
[X] PDF

Background

Expectation
How to solve the problem of Chinese garbled characters? The same text appears normally on top, but garbled characters appear below
Reality
How to solve the problem of Chinese garbled characters? The same text appears normally on top, but garbled characters appear below
Puppeteer configuration file (if used)
No response
Puppeteer version
20.9.0
Node version
16.16.0
Package manager
npm
Package manager version
8.11.0
Operating system
Windows

Please provide a sample of the text (or part of the html) that is being garbled. As we can't verify it without it.
Keep in mind that we only call the browsers internal PDF printing. Are you seeing the same behavior when you try to print from Chrome? Also can you try with a slightly older version of Puppeteer 20.7.2, as that includes an older browser.


Microsoft Graph Change Notifications public cloud IP range is not in sync to setup firewall restrictions for inbound traffic to receive change notifications.

While implementing change notifications for O365 mail boxes, we used the given list for whitelisting inboud traffic, but still notifications were not getting delivered. On investigating the issue with product team it was found that the IP list shared on this page is not the updated one.
It will be nice to publish the latest Public Ips which customers can use for whitelisting.

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

ID: 5de1e69c-aee8-2cd4-3f69-5288253d9b2a
Version Independent ID: 3bcee52a-c7be-6ce3-05a9-2409ec30661c
Content: Other endpoints not included in the Office 365 IP Address and URL Web service - Microsoft 365 Enterprise
Content Source: microsoft-365/enterprise/additional-office365-ip-addresses-and-urls.md
Service: microsoft-365-enterprise
GitHub Login: @kelleyvice-msft
Microsoft Alias: kvice

@sapinderpalsingh Thanks for reaching out to the Microsoft 365 Enterprise content team. Because all Microsoft 365 endpoints data displayed in learn.microsoft.com articles is autogenerated by the Microsoft 365 endpoints web service, the content team cannot resolve issues directly related to this data.
We recommend that you escalate your inquiry to the engineering team associated with the endpoint in question.
Hope this helps!
Thanks
Sri


LogFactory.Setup - SetupInternalLogger

Created as follow up to #3686

There seems to be a build error

There seems to be a build error

Seems you are right. Trying again :)

:+1:


docs: remove reference to support contracts

Release Please is an OSS project released as a community contribution. It is not part of the Google Cloud SDK.

Release please was using the default templates for support requests. This created confusion for customers.

I thought I had turned off owlbot on this repository already.


Error: Could not parse package: '+--- org.projectlombok:lombok -> 1.18.24'

When using dependencyManagement workflow fails with
Error: Could not parse package: '+--- org.projectlombok:lombok -> 1.18.24'

example:
dependencies {
    implementation 'org.projectlombok:lombok'
}
dependencyManagement {
    imports {
        mavenBom "org.springframework.cloud:spring-cloud-dependencies:2021.0.3"
    }
}

Thank you for the report @neerup
Will have a look into how this one differs from other scenarios.

Complete spring project...
demo.zip

@neerup thank you very much. I see now what's going on.
Due to the usage of the bom. the dependency is not defined as:
+--- org.projectlombok:lombok:1.18.24

But instead as:
+--- org.projectlombok:lombok -> 1.18.24

Will expand the parser to handle this situations

Please try again with v0.2.0.
Appreciate the report and the provided sample

Currently using v0.8.0. Facing similar issue.
`Run<EMAIL_ADDRESS>2
with:
3
gradle-project-path: .
4
gradle-dependency-path: build.gradle
5
token: ***
6
use-gradlew: true
7
sub-module-mode: IGNORE
8
include-build-environment: false
9
📘 Reading input values
10
No 'gradle-build-module' passed, using ':'
11
🔨 Processing gradle dependencies for root module - ':'
12
Completed retrieving the 'dependencies' within 37001ms
13
📄 Parsing gradle dependencies graph - ':'
14
Dependency output of 1988 lines
15
Error: Could not parse package: '--- org.projectlombok:lombok (n)' (1)
16
17
/home/runner/work/_actions/mikepenz/gradle-dependency-submission/v0.8.0/webpack:/gradle-dependency-submission/lib/parse.js:68
18
throw Error(The given '${pkg} can't be parsed as a gradle package.);
19
^
20
Error: The given '--- org.projectlombok:lombok (n) can't be parsed as a gradle package.
21
at parseGradlePackage (/home/runner/work/_actions/mikepenz/gradle-dependency-submission/v0.8.0/webpack:/gradle-dependency-submission/lib/parse.js:68:1)
22
at parseGradleDependency (/home/runner/work/_actions/mikepenz/gradle-dependency-submission/v0.8.0/webpack:/gradle-dependency-submission/lib/parse.js:166:1)
23
at parseGradleGraph (/home/runner/work/_actions/mikepenz/gradle-dependency-submission/v0.8.0/webpack:/gradle-dependency-submission/lib/parse.js:117:1)
24
at /home/runner/work/_actions/mikepenz/gradle-dependency-submission/v0.8.0/webpack:/gradle-dependency-submission/lib/process.js:195:1
25
at Generator.next ()
26
at fulfilled (/home/runner/work/_actions/mikepenz/gradle-dependency-submission/v0.8.0/webpack:/gradle-dependency-submission/lib/process.js:28:1)
27
at processTicksAndRejections (node:internal/process/task_queues:96:5)`

@Srinath22N please create a new ticket for it. Also please provide the dependency output so we can expand the tests for this case

Currently using v0.8.0. Facing similar issue.
Parsing gradle dependencies graph - ':'
[14](https://github.com/Cowbell-Cyber/fir-account/actions/runs/3243471872/jobs/5318234548#step:3:17)
  Dependency output of 1988 lines
[15](https://github.com/Cowbell-Cyber/fir-account/actions/runs/3243471872/jobs/5318234548#step:3:18)
  Error: Could not parse package: '\--- org.projectlombok:lombok (n)' (1)
[16](https://github.com/Cowbell-Cyber/fir-account/actions/runs/3243471872/jobs/5318234548#step:3:19)

[17](https://github.com/Cowbell-Cyber/fir-account/actions/runs/3243471872/jobs/5318234548#step:3:20)
  /home/runner/work/_actions/mikepenz/gradle-dependency-submission/v0.8.0/webpack:/gradle-dependency-submission/lib/parse.js:68
[18](https://github.com/Cowbell-Cyber/fir-account/actions/runs/3243471872/jobs/5318234548#step:3:21)
              throw Error(`The given '${pkg} can't be parsed as a gradle package.`);
[19](https://github.com/Cowbell-Cyber/fir-account/actions/runs/3243471872/jobs/5318234548#step:3:22)
  ^
[20](https://github.com/Cowbell-Cyber/fir-account/actions/runs/3243471872/jobs/5318234548#step:3:23)
  Error: The given '\--- org.projectlombok:lombok (n) can't be parsed as a gradle package.
[21](https://github.com/Cowbell-Cyber/fir-account/actions/runs/3243471872/jobs/5318234548#step:3:24)
      at parseGradlePackage (/home/runner/work/_actions/mikepenz/gradle-dependency-submission/v0.8.0/webpack:/gradle-dependency-submission/lib/parse.js:68:1)
[22](https://github.com/Cowbell-Cyber/fir-account/actions/runs/3243471872/jobs/5318234548#step:3:25)
      at parseGradleDependency (/home/runner/work/_actions/mikepenz/gradle-dependency-submission/v0.8.0/webpack:/gradle-dependency-submission/lib/parse.js:166:1)
[23](https://github.com/Cowbell-Cyber/fir-account/actions/runs/3243471872/jobs/5318234548#step:3:26)
      at parseGradleGraph (/home/runner/work/_actions/mikepenz/gradle-dependency-submission/v0.8.0/webpack:/gradle-dependency-submission/lib/parse.js:117:1)
[24](https://github.com/Cowbell-Cyber/fir-account/actions/runs/3243471872/jobs/5318234548#step:3:27)
      at /home/runner/work/_actions/mikepenz/gradle-dependency-submission/v0.8.0/webpack:/gradle-dependency-submission/lib/process.js:195:1
[25](https://github.com/Cowbell-Cyber/fir-account/actions/runs/3243471872/jobs/5318234548#step:3:28)
      at Generator.next (<anonymous>)
[26](https://github.com/Cowbell-Cyber/fir-account/actions/runs/3243471872/jobs/5318234548#step:3:29)
      at fulfilled (/home/runner/work/_actions/mikepenz/gradle-dependency-submission/v0.8.0/webpack:/gradle-dependency-submission/lib/process.js:28:1)
[27](https://github.com/Cowbell-Cyber/fir-account/actions/runs/3243471872/jobs/5318234548#step:3:30)
      at processTicksAndRejections (node:internal/process/task_queues:96:5)


Update implementation to 1.0 spec

This involves removing some hacks added for compatability with Java.

done


Allow the user to override the environmentName

This change allows the user to override the environmentName of the deployed environment reported to github. This affects what is shown on the repo page and PR timeline items.

Allow the user to override the environmentName
Run npm run prettify

Thank you for your help in maintaining this repository 🧡. We've migrated to wrangler-action and are making improvements to ensure that contributions like this will be more easily integrated and better supported. Please come join us at wrangler-action!


Initial commit of CONSOLIDATED NI VeriStand Custom Device project tem…

[x] This contribution adheres to CONTRIBUTING.md.

What does this Pull Request accomplish?
Initial commit of CONSOLIDATED VeriStand Custom Device project template.
Why should this Pull Request be merged?
Because this is the initial version of the project template, ready to be used and tested.
What testing has been done?
Manual smoke testing of generating each of the 6 custom device types, then visual inspection of the resulting projects and CD XML files to make sure original functionality from the previous project template tools was preserved.

You introduced two extra layers into the folder hierachy with "NI VeriStand\Consolidated Custom Device". Remove these extra folders and place all files directly into "Source" folder. The "Source" folder represents the source for the repository, not the directory structure under the ProjectTemplates folder.

I did this for convenience, since the stuff needs to be put in the right spot in the LabVIEW folder in order to actually use it. In the instructions in CONTRIBUTING.md, I pointed out that you just need to copy the 'MetaData' and 'Source' folders to your [LabVIEW 20xx]\ProjectTemplates folder to get up and running. I figured this was the easiest way right now since we don't currently have an installer or a VIP, you have to manually copy files in order to actually use things.
If you don't want extra folders, then we could just put everything (the three subfolders and two .lvproj files in 'Source', along with the XML file in 'MetaData') in the top-level folder of the repo. Now the extra folders are gone, but the manual copy instructions get more complicated. Let me know how you want to proceed. The issue is kinda weird because we're providing our source code, but this source code has to be in a particular place in the LV folder in order for somebody to use it. So who are we making things easier for, the person editing the source or the person using the source as a feature? Right now it's the latter.

The initial folder contains "Time This". Remove this

This was added by the Project Template framework. There is a token in your LabVIEW INI file (NewProjectSpecPagePath) that is the last folder where you saved a project from the Create Project window (regardless of which project template it was). This value is used to populate the UI the next time it runs. So it looks like the last time you created a project, you saved it in the 'Time This' folder on your desktop. If you manually change that path to remove 'Time This' and then create the project, then the next time you create a project, it should properly populate with a new folder on the desktop without 'Time This'.

I get build errors when I try to build the generated project.

The path generation appears to work properly for me (it's the same as what was in the original Inline-Async project template). I am able to build the Configuration LLB without errors. I know you can get that error if you don't have HTML Help Workshop installed, as the .chm won't be generated in that case, causing the Copy function to return an error.

The "Built" folder is created as a sibling to the project folder.

This is consistent with default App Builder behavior. If you make a new EXE/DLL/SDIST/etc. build, the default 'builds' output folder is a sibling to the folder that owns the .lvproj file. Is there a particular reason why the CD build outputs should be treated differently?

The pre-build step makes some assumptions about the folder hierarchy.

I get the same behavior. The CHM file that gets generated by Build CHM.vi creates a help file matching the name of the custom device. But, LLB Pre-Build CHM Build.vi has an extra strip path and is looking for a file named .chm. If I remove the last strip path, I can build just fine.

I recommending dropping the intermediate folders. The ultimate goal is to have package installers for this repository. We will introduce package installers in this revision, but I imagine it will come shortly thereafter.

[ ] Move the template source into "Source" folder. The folder structure is too flat if everything goes into the root. Refer to my original review comment for proposed folder hierarchy.

..\niveristand-custom-device-wizard\Source\NIVS_Consolidated_CDW_MetaDataObj
..\niveristand-custom-device-wizard\Source\Template Classes
..\niveristand-custom-device-wizard\Source\Template Files
..\niveristand-custom-device-wizard\Source\Consolidated Custom Device.lvproj
..\niveristand-custom-device-wizard\Source\Null.lvproj

Added code to remove Engine Release_depinstr.bin, Engine
Debug_depinstr.bin, and NIVeriStand_DataServices.dll after copying build
output to NI VeriStand [ver] folder. This was easier than trying to
remove the files from the build output.

When we build the nipkg installers of the built custom devices, we build from the build output directory (i.e. Built). So, this change won't affect the outputs of the automated builds; they will continue to have these files. But that's not a huge deal at the moment since we already ship those.


Added the right single quotation mark to diactritics.

This pull request includes a

Bug fix

The following changes were made

Added the RIGHT SINGLE QUOTATION MARK character to diacritics

It should be simplified to a typewriter apostrophe: https://en.wikipedia.org/wiki/Apostrophe#Unicode
I could also add all the apostrophe variants but I feel this should be the most common one as this is the preferred character to use for apostrophe according to the Unicode standard.

Failing some jshint checks:
   src/js/[secure]/diacritics.js

    844 |    '\u2019': "'"

                          ^ Strings must use singlequote.

   src/js/[secure]/i18n/lt.js

      2 |  // rules from http://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html#lt

                                                                                ^ Line is too long.

      6 |    } else if ((count % 10 >= 2 && count % 10 <= 9) && (count % 100 < 11 || count % 100 > 19)) {

                                                                                ^ Line is too long.

>> 3 errors in 92 files

Warning: Task "jshint:code" failed. Use --force to continue.

@alexweissman just pushed an adjusted commit.

Oh, awesome, thanks!


WIP: Support exporting revlog for optimizer

Summary 🎯
I want to try to make the optimizer https://github.com/open-spaced-repetition/fsrs4anki/blob/main/fsrs4anki_optimizer.ipynb work for RemNote's repetition history. My plan is to write a function to export all the repetition history for a user's KB as a csv in the same format as the Anki revlog. Everything else seems to get calculated based on that, so it seems pretty doable 👍. Once the revlog is created no changes to the optimizer should be required.
Changes 🔁

A bit of refactoring / run prettier to format code.
Create a function to export revlog data

Two things I'm confused about are the "type" field and  "factor" field:
df.columns = ['id', 'cid', 'usn', 'r', 'ivl',
'last_lvl', 'factor', 'time', 'type']
I looked for documentation here: https://gist.github.com/sartak/3921255 but it's not clear to me what they are.

Two things I'm confused about are the "type" field and "factor" field:
df.columns = ['id', 'cid', 'usn', 'r', 'ivl',
'last_lvl', 'factor', 'time', 'type']

I often read this wiki for reference: https://github.com/ankidroid/Anki-Android/wiki/Database-Structure

The ease factor of the card in permille (parts per thousand). If the ease factor is 2500, the card’s interval will be multiplied by 2.5 the next time you press Good.

type -- 0=learn, 1=review, 2=relearn, 3=cram

ok thanks @L-M-Sherlock
I don't think there's a direct way to get the ease factor or the learning type. (I could be wrong, just not sure.)
Here's an idea to get the ease factor. Let me know if there is an easier way:

For each repetition get the array containing the rep and all the reps before it.

const fullRepHistory = thisRep.card.repetitionHistory || [];
const indexOfThisRep = filteredRepHistory.findIndex((rep) => rep == thisRep);
const slicedRepHistory = filteredRepHistory.slice(0, indexOfThisRep);

Append a "Good" score
Call getNextSpacingDate to work out what the next interval would have been for a "Good" score.
Divide the new calculated interval by the interval without the "Good" score to get the ease factor?
Multiply by 1000.

We don't need to get the factor because the optimizer doesn't use it. For the learning type, you can read this blog: https://www.juliensobczak.com/inspect/2022/05/30/anki-srs.html

Ok great, thanks again!

Where can I find the command create-revlog-csv?

Sorry @L-M-Sherlock  I forgot to push my latest work :face_with_spiral_eyes:. Just added it now.

Ok I tried to implement the review type.

If the repetition was done with FSRS, then I use customData.stage as the review type.
If the repetition was done with a different scheduler, I use the create_init_custom_data function to get the stage and use that as the review type.

Hope the code makes sense!


Detected blocking call to open with args STATUS NOTIFICATION

Registratore: homeassistant.util.loop
Fonte: util/loop.py:136
Prima occorrenza: 15:30:46 (1 occorrenze)
Ultimo accesso: 15:30:46
Detected blocking call to open with args ('/usr/local/lib/python3.13/site-packages/ocpp/v16/schemas/StatusNotification.json', 'r') inside the event loop by custom integration 'ocpp' at custom_components/ocpp/chargepoint.py, line 516: await super()._handle_call(msg) (offender: /usr/local/lib/python3.13/site-packages/ocpp/messages.py, line 164: with open(path, "r", encoding="utf-8-sig") as f:), please create a bug report at https://github.com/lbbrhzn/ocpp/issues For developers, please see https://developers.home-assistant.io/docs/asyncio_blocking_operations/#open Traceback (most recent call last): File "", line 198, in _run_module_as_main File "", line 88, in _run_code File "/usr/src/homeassistant/homeassistant/main.py", line 227, in  sys.exit(main()) File "/usr/src/homeassistant/homeassistant/main.py", line 213, in main exit_code = runner.run(runtime_conf) File "/usr/src/homeassistant/homeassistant/runner.py", line 154, in run return loop.run_until_complete(setup_and_run_hass(runtime_config)) File "/usr/local/lib/python3.13/asyncio/base_events.py", line 708, in run_until_complete self.run_forever() File "/usr/local/lib/python3.13/asyncio/base_events.py", line 679, in run_forever self._run_once() File "/usr/local/lib/python3.13/asyncio/base_events.py", line 2027, in _run_once handle._run() File "/usr/local/lib/python3.13/asyncio/events.py", line 89, in _run self._context.run(self._callback, *self._args) File "/usr/local/lib/python3.13/site-packages/ocpp/charge_point.py", line 238, in start await self.route_message(message) File "/usr/local/lib/python3.13/site-packages/ocpp/charge_point.py", line 261, in route_message await self._handle_call(msg) File "/config/custom_components/ocpp/chargepoint.py", line 516, in _handle_call await super()._handle_call(msg)

Having the same problem.


modules/output: produce empty files by default

This PR removes empty
vim.cmd([[

]])

block from config.
I know that this is already handled by #1889, but I've added tests to make sure that this is the behavior. Also I added the test to make sure that all extraConfigs are outputted.
NOTE: The tests will fail until #1906, #1907 and #1908 are merged.

Thanks! I'd already looked at doing this in https://github.com/nix-community/nixvim/pull/1889, however since that one is larger in scope and unfinished it's better to have this merged sooner than later!
It's also good to have tests, which I hadn't implemented in https://github.com/nix-community/nixvim/pull/1889.
Would you mind looking over how I'd done it in that other PR to see if there's any elements you'd like to incorporate in this one?
E.g. it probably makes sense to move hasContent into our helpers lib and maybe come up with some kinda wrapper function to reduce boilerplate when wrapping potentially empty lua/vim strings?
Not too important as those things may expand the size/scope of this PR unnecessarily making it harder to review. But worth a quick look.

Would you mind looking over how I'd done it in that other PR to see if there's any elements you'd like to incorporate in this one?

Your implementation is better, because it doesn't output empty lines. I like it more. But I intentionally didn't rip it off, because I wanted something simple to get started (and functional) + tests. And since you already implemented a better version, I thought that you'll easily rebase to it later. But if you think that it's better to include your version here, I probably can extract it from there.

But if you think that it's better to include your version here, I probably can extract it from there.

I don't mind too much either way. There's certainly value in keeping this PR simple as you said.

I don't mind too much either way. There's certainly value in keeping this PR simple as you said.

I rewrote it completely. See if it's OK.
Also I replaced a couple of global instances of optionalString with mkIf. It's in a separate commit, I can drop it if needed.
Before:
nix-repl> c.options.extraConfigLuaPre.definitions
[ "\n\n\n\n" "" "" "-- Ignore the user lua configuration\nvim.opt.runtimepath:remove(vim.fn.stdpath('config'))
     -- ~/.config/nvim\nvim.opt.runtimepath:remove(vim.fn.stdpath('config') .. \"/after\")  -- ~/.config/nvim/after\nvi
m.opt.runtimepath:remove(vim.fn.stdpath('data') .. \"/site\")     -- ~/.local/share/nvim/site\n" ]

nix-repl> c.options.extraConfigLuaPost.definitions
[ "" "" ]

After:
nix-repl> c.options.extraConfigLuaPre.definitions
[ "-- Ignore the user lua configuration\nvim.opt.runtimepath:remove(vim.fn.stdpath('config'))              -- ~/.config
/nvim\nvim.opt.runtimepath:remove(vim.fn.stdpath('config') .. \"/after\")  -- ~/.config/nvim/after\nvim.opt.runtimepath
:remove(vim.fn.stdpath('data') .. \"/site\")     -- ~/.local/share/nvim/site\n" ]

nix-repl> c.options.extraConfigLuaPost.definitions
[ "" ]

Notice that there is no empty definitions by default.
But similar cases with empty definitions are still present in some of the plugins, although they are guarded by mkIf cfg.enable, if plugin is enabled, they appear. But I definitely not going to edit them now.

I'll check comments tomorrow. Please decide if a second commit removing empty lines from outputs in a various places is wanted or not.

This would be better off in a dedicated PR, IMO.
I don't see how it relates to this one?

After reading your replies I agree it makes sense in this PR, but it would benefit from a commit message that explains the motivation behind the change, as I was clearly confused 😉

Since other PRs are merged, tests are passing.

@mergifyio queue


some issues

too many problem here
log :
Traceback (most recent call last):
File "breakfold.py", line 113, in
visit()
File "breakfold.py", line 95, in visit
session.get(address, headers=header)	#visiting the URL given by the user
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 487, in get
return self.request('GET', url, **kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 475, in request
resp = self.send(prep, **send_kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 585, in send
r = adapter.send(request, **kwargs)
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 370, in send
conn = self.get_connection(request.url, proxies)
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 273, in get_connection
proxy_manager = self.proxy_manager_for(proxy)
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 169, in proxy_manager_for
**proxy_kwargs
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 43, in SOCKSProxyManager
raise InvalidSchema("Missing dependencies for SOCKS support.")
requests.exceptions.InvalidSchema: Missing dependencies for SOCKS support.

Hi @havefun77612
Did you install the stem library using pip? (pip3 if python3)
Did you follow all the steps I mentioned in the installation?
If yes can you give me some more details? (os, python version)

I've tried each step you've mentioned
I've try using python2 and the program said it need python3 to work so I follow it
And yes I used pip install stem and also used pip3 install stem
OS Ubuntu 17
Device : VMware

I also have the same issue on this

will look into this!

That requests is using socks as a proxy and that socks is not installed.
Just run pip install pysocks

Hi, @rori4 @havefun77612 sorry for the delay!
As @webzf mentioned pysocks will solve the problem!
I will add pysocks as a dependency to the readme.
Thanks,

I solve that problem using
python3 -m pip install -U requests[socks]

in terminal.

Closing this now!
Be safe everyone!!

After updating CookieAuthentication 1, restarted  tor services and it worked for me.