Toggling a radio button or toggle switch to disabled via javascript is not graphically reflected

Not sure if this might already be fixed in the master branch, but when making a radio button or a toggle switch to be disabled, the change is not reflected graphically, only in functionality.
Somebody else also already experienced this bug: http://stackoverflow.com/questions/31322380/disabling-material-design-lite-toggle-switch
With the radio buttons I can add, that only when selects another radio button from the same 'group', the updated disabled state is at that point (but thus too late) graphically shown.

We might have a similar issue here like #908 fixed. Thanks for reporting, we’ll look into it.

I posted about this on StackOverlow yesterday thinking it's something I'm doing... more info here with JSFidle and video example: http://stackoverflow.com/questions/31322380/disabling-material-design-lite-toggle-switch

@surma That is unrelated.
Here, we don't toggle views based on [disabled]. It is done via the is-disabled class which is only triggered via JS. I'd need to dig into the JS more to tell if we can do a simple style addition (is-disabled,[disabled]) to fix this in a BC way.
What's odd is, currently the only way to "disable" via JS is calling the widget against the element. However widget functionality for radio and checkbox are never exposed.

Just linking the @Garbee answer in the stackoverflow question and relating the #1013 PR that he does.
In the example mentioned in the answer we are querying the input element like this:
document.querySelector('#my-checkbox').MaterialCheckbox.disable()

But, we need to query the label and not the input[type=checkbox].
Maybe, we can query input and use something like this
document.querySelector('#my-checkbox').parentElement.MaterialCheckbox.disable()

With that implementation its working, but IMO it's strange that we need to access the parenteElement.

@HenriqueLimas Just think of it as "The widget is assigned to where I define the JS class, not the input itself."

Yeah, it makes sense, Thanks. And I know you just make an example. Maybe we can close this issue.

I'm going to allow Surma to review and close as he sees fit. He may see something actionable here that I don't.

Definitely see the issue here. I am thinking whether we should add some very lightweight JS to the checkbox to make the widget accessible via the <input> as well.
Let me pull in @sgomes and @addyosmani ;)

I'm worried about having multiple ways to target things like this. Consistency is best had by just saying "Target where you define the js class to access the widget." Instead of, "That works, except for X components where you can also target the inputs."

@Garbee Now that you say that, I agree. Classes should be the way to address the widget. So is this a wont-fix?

Well, this is actually "fixed" since the component is forced as a widget in 1.0.1 which allows for developers to update the checkbox dynamically. Before the widget check was failing somehow causing it to not be added, so there was no way to access disable() and other public methods for the MaterialCheckbox component. ;)
We can't fix it the way requested, since that means adding in observers and/or other polyfills which is not happening.

I am not sure if it i something broken in my code, but on 1.0.1 I cannot toggle the disable state on MaterialRadio.

@mfonville Please use StackOverflow for support. Disabling works as expected in 1.0.1.

@Garbee Thank you for confirming that it works on 1.0.1, I will try to find the error in my code then :-)


Error with queue_size been removed

Hello,
When I run "puppet agent -t" I receive this error message:
Error: /Stage[main]/Filebeat::Config/File[filebeat.yml]/content: change from {md5}372f9bd50cb5445dbd20be7e25f164bb to {md5}5df1557e2cdad6e28b85430b9cbc19e8 failed: Execution of '/usr/share/filebeat/bin/filebeat -N -configtest -c /etc/filebeat/filebeat.yml20180405-18063-1n2d3ob' returned 1: Flag --configtest has been deprecated, configtest flag has been deprecated, use test config subcommand Exiting: 1 error: setting 'queue_size' has been removed
   class { 'filebeat':         outputs => {          'elasticsearch' => {                 'hosts'         => [                     'Something-int:9200',                     'Something:9200'                 ],                 'protocol'      => 'https',                 'username'      => 'something',                 'password'      => 'Something',                 'registry_file' => '/var/lib/filebeat/registry',                 'major_version' => '6',                 'package_ensure' => 'latest',                 'ssl.certificate_authorities' => '/Path ssl/',           },        },      }     filebeat::prospector { 'syslogs':         paths         => [             '/var/log/*.log',             '/var/log/*/*',             '/var/log/*',         ],         doc_type      => 'syslog-beat',         exclude_files => ['\.dat$', '\.gz$', 'filebeat'],     }     filebeat::prospector { 'client-prod':         paths         => [             '/folder/client/*.log',         ],         doc_type      => 'syslog-beat',         exclude_files => ['\.dat$', '\.gz$', 'filebeat'],     }
I try removing the filebeat package on Centos and let puppet reinstalling but I have the same issue
Let me know if you need more information

According to the readme:
To upgrade to Filebeat 6.x, simply set $filebeat::major_version to 6 and $filebeat::package_ensure to latest.
According to the code, the default version is now version 6 ?

I will close the ticket my settings were under filebeat::output class instead of filebeat class
Sorry


Exclude empty functions from coverage

Good catch, thanks! I'll let the coverage run (~1 hour) just to get CodeCov to post the change in coverage.


Fixed PHP 7.2 compatibility issue

Guzzle 6.2 wasn't compatible with PHP 7.2

You're welcome.

Thanks for fixing this Rick Mills.

No problem at all @mikebarlow 🙌🏻


improve Add txn insert p2 case

Proposed changes
Add a p2 case for txn insert.


Updated Gemfile (ruby 1.9.3 and downgraded redis-namespace)

Noticed you've forked this, a project with zero documentation..! I probably don't have time to rectify that, but if you've got any questions feel free to ask :)


Bump OpenTelemetry from 1.31.0 to 1.32.0 and OpenTelemetry Semconv from 1.21.0-alpha to 1.23.1-alpha

Description
Bump OpenTelemetry from 1.31.0 to 1.32.0 and OpenTelemetry Semconv from 1.21.0-alpha to 1.23.1-alpha
Related Issues
N/A

Check List

[X] New functionality includes testing.

[X] All tests pass

[X] New functionality has been documented.

[X] New functionality has javadoc added

[X] Failing checks are inspected and point to the corresponding known issue(s) (See: Troubleshooting Failing Builds)
[X] Commits are signed per the DCO using --signoff
[X] Commit changes are listed out in CHANGELOG.md file (See: Changelog)
[X] Public documentation issue/PR created

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

❌ Gradle check result for 285e56c: FAILURE

https://github.com/opensearch-project/OpenSearch/issues/10704

❌ Gradle check result for 285e56c: FAILURE

https://github.com/opensearch-project/OpenSearch/issues/6445
https://github.com/opensearch-project/OpenSearch/issues/10193

Do you want this in 2.x?


eval_limit and batch don't do what I expect

I'm not sure what the chain eval_limit and batch should do e.g.
`SomeModel.eval_limit(5).batch(5)`

Should that get 5 records, in a batch of 5, or 5 batches of 5 records each?
When I tried it it scanned the entire table ignoring the limit.

@andrykonchin do you have any idea about this?

@pboling
Model.where({}).eval_limit(n) means we load first n items
Model.where({}).batch(m) means we load all matched items but internally paginate them and load m items at a time.
Model.where({}).eval_limit(n).batch(m) chain completely ignores limit n and works like batch call. But yes, I was expected behavior described by @JohnSmall too.

So, it is a bug 👍 , We'll leave this open to track it until we fix it.

This is updated again in https://github.com/Dynamoid/Dynamoid/pull/183 to handle scan limit as well.

@richardhsu so #183 doesn't fix this bug, but it adds another type of limit "support" that will be ignored if batch is chained?
Model.where({}).eval_limit(n).batch(m)
Model.where({}).scan_limit(n).batch(m)

Both limit types are ignored?

@pboling can you give me examples that you're seeing don't work?
I'm seeing it respect the scan_limit and record_limit and making batch queries to DynamoDB with batch_size assuming batch_size < scan_limit or batch_size < record_limit.
# Record Limit with batch of 3
> model.where({}).record_limit(5).batch(3).to_a.count
REQUEST {:table_name=>"dynamoid_tests_customer", :limit=>3}
REQUEST {:table_name=>"dynamoid_tests_customer", :limit=>2, :exclusive_start_key=>{"age"=>#<BigDecimal:3e64828,'0.3E1',9(18)>, "id"=>"1"}}
=> 5

# Record limit with batch of 1
> model.where({}).record_limit(5).batch(1).to_a.count
REQUEST {:table_name=>"dynamoid_tests_customer", :limit=>1}
REQUEST {:table_name=>"dynamoid_tests_customer", :limit=>1, :exclusive_start_key=>{"age"=>#<BigDecimal:3ee4370,'0.1E1',9(18)>, "id"=>"1"}}
REQUEST {:table_name=>"dynamoid_tests_customer", :limit=>1, :exclusive_start_key=>{"age"=>#<BigDecimal:3f139e0,'0.2E1',9(18)>, "id"=>"1"}}
REQUEST {:table_name=>"dynamoid_tests_customer", :limit=>1, :exclusive_start_key=>{"age"=>#<BigDecimal:1077988,'0.3E1',9(18)>, "id"=>"1"}}
REQUEST {:table_name=>"dynamoid_tests_customer", :limit=>1, :exclusive_start_key=>{"age"=>#<BigDecimal:10413b0,'0.4E1',9(18)>, "id"=>"1"}}
=> 5

# Scan limit with batch of 1
> model.where({}).scan_limit(5).batch(1).to_a.count
REQUEST {:table_name=>"dynamoid_tests_customer", :limit=>1}
REQUEST {:table_name=>"dynamoid_tests_customer", :limit=>1, :exclusive_start_key=>{"age"=>#<BigDecimal:3e92fc0,'0.1E1',9(18)>, "id"=>"1"}}
REQUEST {:table_name=>"dynamoid_tests_customer", :limit=>1, :exclusive_start_key=>{"age"=>#<BigDecimal:3e150c0,'0.2E1',9(18)>, "id"=>"1"}}
REQUEST {:table_name=>"dynamoid_tests_customer", :limit=>1, :exclusive_start_key=>{"age"=>#<BigDecimal:3d9f1b8,'0.3E1',9(18)>, "id"=>"1"}}
REQUEST {:table_name=>"dynamoid_tests_customer", :limit=>1, :exclusive_start_key=>{"age"=>#<BigDecimal:3d4d2c8,'0.4E1',9(18)>, "id"=>"1"}}
=> 5

# Scan limit with batch of 2
> model.where({}).scan_limit(5).batch(2).to_a.count
REQUEST {:table_name=>"dynamoid_tests_customer", :limit=>2}
REQUEST {:table_name=>"dynamoid_tests_customer", :limit=>2, :exclusive_start_key=>{"age"=>#<BigDecimal:3bff768,'0.2E1',9(18)>, "id"=>"1"}}
REQUEST {:table_name=>"dynamoid_tests_customer", :limit=>1, :exclusive_start_key=>{"age"=>#<BigDecimal:3bbb270,'0.4E1',9(18)>, "id"=>"1"}}
=> 5

These seem to be all expected number of requests, unless I'm misunderstanding the batch? (This is off master)

Oh, also just noticed one slight issue with query though that Chain isn't passing batch_size down to the query so I'll open up quick PR for that.

I was just asking if the PR actually did fix the bug, it wasn't clear to me that it did.  Looks like it is all working!

Ah, yes, sorry it does :) Will be clearer in future PR for these types of fixes!


sudo: football: command not found

i cant run sudo football config, and get notif sudo: football: command not found
i used zsh shell in LinuxMint OS
how to fix this?

Yes, i can. but yesterday i can't get the result, issue with the token when token is correct

I entered token with  football config without sudo

Yup, documentation should be fixed and sudo should not be part of the command, unless required.

Closing this issue. Please feel free to open again if the problem persists.

Thanks for your reply..


Feature: Custom benchmark tags

I want to test the waters on whether the community would be receptive to a PR that adds the ability to apply custom tags to a benchmark.
This specifically targets a use case with Influx where I want to run the same benchmark multiple times under different constraints/scenarios.
For example:
for size in [10, 100, 1000] {
    Benchmark("TestFoo", tags: [ "size": size ]) {
        foo(size)
    }
}

This would allow me to get better dimensionality on a benchmark that, when exported to Influx, is more easily queried etc.
This would require some amendments to the Influx format exporter to include these custom tags for the particular benchmark.
We (myself and/or @ORyanHampton) are happy to take this PR on - just don't want to spend time on it if it's not a direction that the community finds appropriate.

I think that is a good direction for packaging of parameterised benchmarks - we currently do it by changing the benchmark description string, e.g.:
let benchmarks = {
  let parameterization = (0...5).map { 1 << $0 } // 1, 2, 4, ...

  parameterization.forEach { count in
    Benchmark("ParameterizedWith\(count)") { benchmark in
      for _ in 0 ..< count {
        blackHole(Int.random(in: benchmark.scaledIterations))
      }
    }
  }
}

but to give an exporter access to better structured information of the parameterization in use as you suggest would be nicer and avoid string parsing.
Some considerations/questions would be:

Need to validate behaviour with multiple benchmarks with the same name (including baselines, filtering  etc) - haven't really tried or considered that - the expectation has been that a benchmark name is unique, so there may be some assumptions there that breaks things
Should adopt the standard textual output to also print parameterisation in a nice compact way (perhaps simply TestFoo (size = 100, otherParameter = "test") is ok)
What are thoughts about supported types and cardinality for such parameterisation?
Perhaps "parameterization" would be a better term than "tags" to better reflect what it actually is used for (then we can reserve "tags" or "labels" for a future feature that could be used for metadata filtering of benchmarks to run by "tag" or "label", WDYT?

Overall I think it would be a nice improvement!

Need to validate behaviour with multiple benchmarks with the same name (including baselines, filtering etc) - haven't really tried or considered that - the expectation has been that a benchmark name is unique, so there may be some assumptions there that breaks things

This makes sense. What are the odds we could just give each Benchmark a default unique uuid? User doesn't have to explicitly provide one (or maybe it's not even parameterized)? I assume there would just need to be a mapping back to the string-based name - which with your suggestion below modifying the textual output would definitely be useful in disambiguating when outputting a description of the benchmark.

Should adopt the standard textual output to also print parameterisation in a nice compact way (perhaps simply TestFoo (size = 100, otherParameter = "test") is ok)

Love this.

What are thoughts about supported types and cardinality for such parameterisation?
It's a good question. Crossed my mind while writing the example code above.
I'm thinking about something like this to give some flexibility to the user like what you have shown above:

enum Value { // Not necessarily the ideal naming
  case int(Int)
  case string(String)
}
extension Value: ExpressibleByStringLiteral {}
extension Value: ExpressibleByIntegerLiteral {}

// Then this can work pretty transparently.
let parameterization: [String: Value] = ["size": 100, "otherParameter": "test"]

Thoughts?

Perhaps "parameterization" would be a better term than "tags" to better reflect what it actually is used for (then we can reserve "tags" or "labels" for a future feature that could be used for metadata filtering of benchmarks to run by "tag" or "label", WDYT?

Sure - this is excellent feedback as one of my concerns was how this feature would fit within the ecosystems of the other exporters.
On this note, in Influx land, in addition to tags there are fields and I'm wondering if there's a generalization that could be applied to facilitate both of these. I do believe I'm going to need both to do what I want to do.
The tags I anticipate using for the static and constrained metadata about a particular test - whereas the fields I will need to use for the more dynamic metadata about the test.
For example, I want to do a bit of randomization in my Benchmarking but want to record the results of that randomization along with the test. Specifically, the randomized values would be a double between 0.0 and 1.0 (a percentage). This wouldn't fit well as a tag because there are infinite values between 0.0 and 1.0 - which is where a field is more useful.
Importantly, this value is not a measurement so a custom metric wouldn't be appropriate here.
Do you have any recommendations or preferences about a generalization around the notion of "parameterizations" with finite ranges vs infinite ranges.


Adopt to black 20.8b

Description of the problems or issues
Is your pull request related to a problem? Please describe.
Black has been updated to 20.8b just recently, which made #497 fail.
Does your pull request fix any issue.
N/A.
Description of the proposed changes

Reformat codes to comply with black 20.8b
Print versions of check tools
Update .pre-commit-config.yaml
Remove seed-isort-config from .pre-commit-config.yaml as "this is no longer needed as of isort>=5" (https://github.com/asottile-archive/seed-isort-config)

Test plan
Existing tests would be good enough.
Checklist

[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.
[ ] I have updated the CHANGELOG.rst accordingly.

Codecov Report

Merging #499 into master will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master     #499   +/-   ##
=======================================
  Coverage   85.76%   85.76%
=======================================
  Files          88       88
  Lines        4567     4567
  Branches      853      853
=======================================
  Hits         3917     3917
  Misses        466      466
  Partials      184      184

Flag
Coverage Δ

#unittests
85.76% <100.00%> (ø)

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

Impacted Files
Coverage Δ

src/fonduer/parser/visual_linker.py
84.18% <ø> (ø)

src/fonduer/utils/visualizer.py
80.00% <ø> (ø)

src/fonduer/parser/models/utils.py
84.61% <100.00%> (ø)


Feature Request: LanguageServiceHost plugin

Search Terms
language service host compiler plugin
Refs #16607
Suggestion
Currently, TypeScript only supports proxying the language service.  It would be good to have an officially supported way of being able to proxy the LanguageServiceHost as well.
Use Cases
Being able to provide a plugin that changes how the language service host behaves is often a requirement for use cases where the default behaviour of TypeScript in Visual Studio Code does not mirror the compile time behaviour when using tools that implement a language service host with TypeScript.
For example in Deno, we utilise full path names for modules, including TypeScript ones.  The standard language service host disallows this (because it assumes that the module name won't end in .ts at runtime).
There are likely to be other use cases where the behaviour of the language service host differs when using other forms of TypeScript other than tsc and Visual Studio Code, where it would be useful to allow plugins to mimic that behaviour, in particular in Visual Studio Code, so that the editing experience can be more rich.
Examples
I currently have a plugin which just monkey patches the LanguageServiceHost to inject similar logic for module resolution to what is done in Deno.  This is because I cannot return a proxy, like I could with the LanaguageService.
Checklist
My suggestion meets these guidelines:

[X] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[X] This wouldn't change the runtime behavior of existing JavaScript code
[X] This could be implemented without emitting different JS based on the types of the expressions
[X] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
[X] This feature would agree with the rest of TypeScript's Design Goals.

Hey there.
I'm trying to do something similar and faced the same issue...
@fis-cz Do you have any idea why monkey patching has stopped working??? couldn't find any change related to that.

Hey there.
I'm trying to do something similar and faced the same issue...
@fis-cz Do you have any idea why monkey patching has stopped working??? couldn't find any change related to that.

Sure I do. It is because they enclosed important parts of the compiler to “private” closures so it is not accessible anymore thus it can’t be monkey patched once the compiler is loaded.

Sure I do. It is because they enclosed important parts of the compiler to “private” closures so it is not accessible anymore thus it can’t be monkey patched once the compiler is loaded.

A note for those who come after, I learned one workable workaround here: https://github.com/mrmckeb/typescript-plugin-css-modules/blob/main/src/index.ts. In short, you can create a completely new language service instance with a customized host then return it.


very slow performance with pfring...

regardless of the number of slots, Using the pfring in 1gbps occured a lot of drop(Tot pkt Lost)

Could you provide a little more detail on the code you're running?  Do you have a minimum viable program that exhibits this?
If you're using PacketSource or ReadPacketData, maybe switch to ReadPacketDataTo to avoid an extra alloc.  Doesn't look like we've implemented ZeroCopyReadPacketData for pfring, but we probably should.
Are you doing other stuff in your code, tcp assembly or the like?
Could you generate a CPU profile with your run (https://golang.org/pkg/runtime/pprof/) and generate a SVG of its output to add here?  That might point to a smoking gun.

I have a similar issue with PF_RING. Specifically the latencies seem very high.
I have created a minimal ping using gopacket and pfring here: https://github.com/redsift/pingdemo
When testing this on Ubuntu 16.04.1 LTS with PF_RING 6.6.0 and the pfring e1000e driver, the latency suggests something is wrong.
The linked project fires a ping packet and times the response.
Hitting <IP_ADDRESS> takes ~500ms
PF_RING ping timing demo: ping <IP_ADDRESS> from <IP_ADDRESS>
ping time=500.586337ms
ping time=500.571822ms
ping time=500.571827ms
ping time=500.575797ms
ping time=500.577616ms

The same test with the zero copy interface is mostly the same though I guess this is not relevant for my single packet test case.
PF_RING ping timing demo: ping <IP_ADDRESS> from <IP_ADDRESS>
#########################################################################
# ERROR: You do not seem to have a valid PF_RING ZC license <IP_ADDRESS>424 for eno1 [Intel 1 Gbit e1000e family]
# ERROR: Please get one at http://shop.ntop.org/.
#########################################################################
# We're now working in demo mode with packet capture and
# transmission limited to 5 minutes
#########################################################################
ping time=500.57761ms
ping time=500.579852ms
ping time=500.565223ms
ping time=500.56318ms
ping time=500.569313ms

As a control, command line ping reports tiny latencies.
PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.
64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=59 time=4.50 ms
64 bytes from <IP_ADDRESS>: icmp_seq=2 ttl=59 time=4.12 ms
64 bytes from <IP_ADDRESS>: icmp_seq=3 ttl=59 time=4.07 ms
64 bytes from <IP_ADDRESS>: icmp_seq=4 ttl=59 time=4.41 ms
64 bytes from <IP_ADDRESS>: icmp_seq=5 ttl=59 time=4.20 ms

In another application, gopacket with libpcap reports times within 10% of the command line ping to this ~500ms latency is specific to PF_RING.
What am I missing?

Not sure if this is correct, but my guess is that PF_RING might be trying to buffer multiple packets before returning the set to you, the caller.  If you're only seeing one, it may be waiting for a timeout (500ms) before returning.  I'll dig briefly into the code and see if that makes sense.

Hmm, there's a very suspicious pfring global called DEFAULT_POLL_DURATION set to 500.

We might need to expose pfring_set_poll_duration to fix this...

Could you throw some printf-debugging around the ReadPacketDataTo call and make sure it's the function that's actually taking ~500ms?

Yes, the 500ms is in ReadPacketDataTo.
Looks like you are right. Combination of pfring_set_poll_duration (default = 500) and pfring_set_poll_watermark (default = 128). Clients of gopacket likely want to tweak these based on use case.

PF_RING NOT FREE.  I got same problem .  i use dpdk at last.

Same problem here, in input flow. Sending a UDP packet with netcat, netcat exits almost immediately but I see the packet only 2 or 3 seconds later.


Sticky feature support

Sticky feature can be implemented with pure CSS using position: sticky.
For example,

    <input
            type="text"
            data-jplist-control="textbox-filter"
            data-group="group1"
            data-name="model-text-filter"
            data-path=".card-title"
            data-clear-btn-id="model-clear-btn"
            class="form-control"
            placeholder="Filter by Model" />

    ....

Sticky has pretty good browser support now and works in all browsers except IE.
So IMHO there is not need to add JS support for this feature in the library.


How to apply .Net core claim-base authorization when using Istio end-user authentication

Currently, I am using Istio end-user authentication; it is fine, don't need to use any authentication middleware from code but we can still authenticate JWT token from request and reject that request if the token is invalid (return 401).
However, it is out side of the service (implemented by .Net core). So User.Identity will be null and authorization step (by role base or claim base) always be fail. Because JWT token is not analyzed.
So, how can we apply claim-base authorization without any UseAuthentication middleware.
Thanks,

You can't.
You need some sort of middleware to construct the User object for it to be usable by authorization. If Istio passes information along in headers you'd be able to write middleware to use those, but it's going to be very custom.

Thanks @blowdart, currently, do we have any available middleware to analyze JWT token and construct the User object in .Net Core without validate back IDP? Or could you please share me the source code to build it?

If the jwt middleware doesn't allow you to disable the metadata retrieval for signing keys, and I don't think it does, then it's probably the best place to start.

Thanks, let me try; maybe this is what I want to find.

We're closing this issue as no response or updates have been provided in a timely manner. If you have more details and are encountering this issue please add a new reply and re-open the issue.


Uvdar led fix

Changed parameter names for the new UVDAR simulateor connection schema.

Can you please fix it for all models of drones?  F550 and T650 have uvdar too.

Ok, it works with f550 and t650 drones now.


Add cache handler for predis

Signed-off-by: Geoffrey Hughes<EMAIL_ADDRESS>As discussed in #192, here's the cache drive for predis/predis.

Awesome. Thanks!


Feature Request: Some method of dragging an item link from its own sheet

I often will open up quick insert, type some stuff in, click an entry that looks promising, read through it's description, decide yes, that's what I want, and then... I need to open quick insert again and retype to actually drop the item somewhere. There's no way from just that sheet to drag a copy of that item to a token or character sheet or whatever. I think having this option would be a very nice QoL improvement.
The drag handle could either be the item's icon, or maybe if its possible to add drag handling to the 'get id' button? or, worst case, add a specific new thing to grab, somewhere on the sheet.

This is more a limitation of the Quick Insert module: all core and system workflows leave a draggable link in place after clicking it to open an item sheet.


Add canBePausedByOtherPlayers option

Hi,
This pull request adds a simple functionality to control whether a player can be paused by other players. This is useful for certain cases like a background video, that needs to keep running when an other inline player is started.
I hope this can be added to the next release!
Thanks!

@johndyer Do we need to change something for this one to be merged then, based on your last comment?

Closing this PR since it is considered irrelevant for now. If you'd like to reopen this, let us know. Thanks!


I don't have an issue, I would like to ask question.

Good day.
I really like your repository like a lot but
I am having a confusion regarding .env.
Particularly in database_url =
Can you further explain to me about what to put or any methods.
Thank you for your response.

Can you further explain to me about what to put or any methods.

As of now, the repository is using mysql from planetscale. You can get your connection uri at https://planetscale.com, sign up with credit card then connect (select nodejs from dropdown menu).
P.S. They are about to drop free tier at April 8th. Speaking of which, I am planning to migrate this repo to use neonDB PostgreSQL since it's free and I don't afford planetscale's scaler plan.

is there any changes of codes if you migrate it?
On Tue, Mar 26, 2024, 7:03 PM Rohi @.***> wrote:

Can you further explain to me about what to put or any methods.
As of now, the repository is using mysql from planetscale. You can get
your connection uri at https://planetscale.com, sign up with credit card
then connect (select nodejs from dropdown menu).
P.S. They are about to drop free tier at April 8th. Speaking of which, I
am planning to migrate this repo to use neonDB PostgreSQL since it's free
and I don't afford planetscale's scaler plan.
—
Reply to this email directly, view it on GitHub
https://github.com/gneiru/kd/issues/88#issuecomment-2020128580, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AEBSUCNJMHATKOE3DFOKELTY2FIXTAVCNFSM6AAAAABFIN6SBOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRQGEZDQNJYGA
.
You are receiving this because you authored the thread.Message ID:
@.***>

is there any changes of codes if you migrate it?

yes

there will be a lot. not only because of migrating from planetscale to neon but also because of migrating from mysql to postgresql.

Ok, thanks for the clarification. i will wait for your update then.
On Tue, Mar 26, 2024, 9:56 PM Rohi @.***> wrote:

there will be a lot. not only because of migrating from planetscale to
neon but also because of migrating from mysql to postgresql.
—
Reply to this email directly, view it on GitHub
https://github.com/gneiru/kd/issues/88#issuecomment-2020498027, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AEBSUCJI5CNYEYWVFRGI5HDY2F5AVAVCNFSM6AAAAABFIN6SBOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRQGQ4TQMBSG4
.
You are receiving this because you authored the thread.Message ID:
@.***>

its so nice.. thanks bro.. its a big help..let me try it

hi @gneiru i am having this error when i try npm install ❌ Invalid environment variables: { DATABASE_URL: [ 'Invalid input: must include "neondb"' ] }
C:\Users\USER\Desktop\kd-master\node_modules@t3-oss\env-core\dist\index.js:29
throw new Error("Invalid environment variables");
i have already put all the requirements in .env.

hi @gneiru i am having this error when i try npm install ❌ Invalid environment variables: { DATABASE_URL: [ 'Invalid input: must include "neondb"' ] }
C:\Users\USER\Desktop\kd-master\node_modules@t3-oss\env-core\dist\index.js:29
    throw new Error("Invalid environment variables");

i have already put all the requirements in .env.

What is your database name? I thought "neondb" is the default name so it should work.

i think it has something to do with this code? "DATABASE_URL: z.string().url().includes("neondb")"
i guess :)

i already figure it out. i need to change the neondb to my databasename

i already figure it out. i need to change the neondb to my databasename

Nice catch

but im having this issue again :D

I think your api requests are failing. Please check the enpoints in src/lib/dramacool. It should return JSON with matching types

i use consumet api and host my own. the api seems to be ok in the hosting
side.
On Sun, Mar 31, 2024, 2:30 AM Rohi @.***> wrote:

I think your api requests are failing. Please check the enpoints in
src/lib/dramacool. It should return JSON with matching types
—
Reply to this email directly, view it on GitHub
https://github.com/gneiru/kd/issues/88#issuecomment-2028435390, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AEBSUCP6R7HCOUUMUWQDOUDY24ADZAVCNFSM6AAAAABFIN6SBOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRYGQZTKMZZGA
.
You are receiving this because you were mentioned.Message ID:
@.***>

maybe because of the type. i dont know it
On Sun, Mar 31, 2024, 10:33 AM Novan Mar Tejares @.***>
wrote:

i use consumet api and host my own. the api seems to be ok in the hosting
side.
On Sun, Mar 31, 2024, 2:30 AM Rohi @.***> wrote:

I think your api requests are failing. Please check the enpoints in
src/lib/dramacool. It should return JSON with matching types
—
Reply to this email directly, view it on GitHub
https://github.com/gneiru/kd/issues/88#issuecomment-2028435390, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AEBSUCP6R7HCOUUMUWQDOUDY24ADZAVCNFSM6AAAAABFIN6SBOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRYGQZTKMZZGA
.
You are receiving this because you were mentioned.Message ID:
@.***>

Try checking the endpoints, my API_URL ends with /api

this is the consumet api i have hosted. and this is the one i put in the
env.
https://anime-api-ashen.vercel.app
On Sun, Mar 31, 2024, 10:39 AM Rohi @.***> wrote:

Try checking the endpoints, my API_URL ends with /api
—
Reply to this email directly, view it on GitHub
https://github.com/gneiru/kd/issues/88#issuecomment-2028534041, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AEBSUCKDTAUNROCM46EWYXTY25ZOXAVCNFSM6AAAAABFIN6SBOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRYGUZTIMBUGE
.
You are receiving this because you were mentioned.Message ID:
@.***>

What's the endpoimt of getting trending, recent etc?

i just put dramacool in the url like this
https://anime-api-ashen.vercel.app/movies/dramacool/recent
and it returns like this:
{"currentPage":1,"totalPages":1,"hasNextPage":false,"results":[{"id":"drama-detail/get-old-recently","title":"Get
Old Recently (2021)","url":"https://dramacool.com.pa/drama-detail/get-old-recently","image":"https://asianimg.pro/cover/get-old-recently.png"}]}
does it mean its ok now?
On Sun, Mar 31, 2024, 11:52 AM Rohi @.***> wrote:

What's the endpoimt of getting trending, recent etc?
—
Reply to this email directly, view it on GitHub
https://github.com/gneiru/kd/issues/88#issuecomment-2028544333, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AEBSUCIVFMW6DNSYA2VCNG3Y26CAJAVCNFSM6AAAAABFIN6SBOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRYGU2DIMZTGM
.
You are receiving this because you were mentioned.Message ID:
@.***>

You should put https://anime-api-ashen.vercel.app/movies/dramacool in your .env file. However, the response schema doesnt match with the app's

i see. this is what in my mind also. let me try again.
Thanks for the help. your such a big help.
On Sun, Mar 31, 2024, 12:26 PM Rohi @.***> wrote:

You should put https://anime-api-ashen.vercel.app/movies/dramacool in
your .env file. However, the response schema doesnt match with the app's
—
Reply to this email directly, view it on GitHub
https://github.com/gneiru/kd/issues/88#issuecomment-2028549750, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AEBSUCO7EOJELIY7PXITUO3Y26F7RAVCNFSM6AAAAABFIN6SBOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRYGU2DSNZVGA
.
You are receiving this because you were mentioned.Message ID:
@.***>

everthing looks fine until i got this error. this is when i click button going to home page

Add this code to your dramacool parser methods
featured = async () => {     try {       const url = new URL(${this.baseUrl}`);
const res = await this.client.get(url.toString());
  const $ = load(res.data);

  const featured: IMovieEpisode[] = [];

  $("#layerslider .ls-slide").each((i, el) => {
    featured.push({
      id: $(el).find("a").attr("href")?.slice(1)!,
      title: $(el).find("img").attr("title")!,
      image: $(el).find("img").attr("src"),
    });
  });
  return featured;
} catch (err) {
  throw new Error("Something went wrong. Please try again later.");
}

};`
Then add a route to call this method, in my case it is /featured

im sorry for not getting it. im so noob right now. but should  i put it here?

No, in your self hosted code. If you want, I'll make a PR on your repo of the self hosted consumet API

Yes, of course you can!
On Mon, Apr 1, 2024, 1:57 PM Rohi @.***> wrote:

No, in your self hosted code. If you want, I'll make a PR on your repo of
the self hosted consumet API
—
Reply to this email directly, view it on GitHub
https://github.com/gneiru/kd/issues/88#issuecomment-2029211607, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AEBSUCJ2JQKJ7QJUORSYHRLY3DZMBAVCNFSM6AAAAABFIN6SBOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRZGIYTCNRQG4
.
You are receiving this because you were mentioned.Message ID:
@.***>

Which repo? Is it public? If not, could you please add me as collaborator.

https://github.com/novanmartejares/anime_api
On Mon, Apr 1, 2024, 6:07 PM Rohi @.***> wrote:

Which repo? Is it public? If not, could you please add me as collaborator.
—
Reply to this email directly, view it on GitHub
https://github.com/gneiru/kd/issues/88#issuecomment-2029520756, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AEBSUCN7XLXNUCDWOEXJ373Y3EWV3AVCNFSM6AAAAABFIN6SBOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRZGUZDANZVGY
.
You are receiving this because you were mentioned.Message ID:
@.***>

Can't access it for some reason

i think its private
On Mon, Apr 1, 2024, 7:07 PM Rohi @.***> wrote:

Can't access it for some reason
—
Reply to this email directly, view it on GitHub
https://github.com/gneiru/kd/issues/88#issuecomment-2029592316, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AEBSUCL32QYSXSK3IOINVZLY3E5XRAVCNFSM6AAAAABFIN6SBOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRZGU4TEMZRGY
.
You are receiving this because you were mentioned.Message ID:
@.***>

i have added you as collaborator
On Mon, Apr 1, 2024, 7:39 PM Novan Mar Tejares @.***>
wrote:

i think its private
On Mon, Apr 1, 2024, 7:07 PM Rohi @.***> wrote:

Can't access it for some reason
—
Reply to this email directly, view it on GitHub
https://github.com/gneiru/kd/issues/88#issuecomment-2029592316, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AEBSUCL32QYSXSK3IOINVZLY3E5XRAVCNFSM6AAAAABFIN6SBOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRZGU4TEMZRGY
.
You are receiving this because you were mentioned.Message ID:
@.***>

animeapi-two.vercel.app
this is the api.. not the other one
On Mon, Apr 1, 2024, 7:41 PM Novan Mar Tejares @.***>
wrote:

i have added you as collaborator
On Mon, Apr 1, 2024, 7:39 PM Novan Mar Tejares @.***>
wrote:

i think its private
On Mon, Apr 1, 2024, 7:07 PM Rohi @.***> wrote:

Can't access it for some reason
—
Reply to this email directly, view it on GitHub
https://github.com/gneiru/kd/issues/88#issuecomment-2029592316, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AEBSUCL32QYSXSK3IOINVZLY3E5XRAVCNFSM6AAAAABFIN6SBOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRZGU4TEMZRGY
.
You are receiving this because you were mentioned.Message ID:
@.***>

I can't add the code unfortunately. Your API is using the API wrapper of consumet.ts, while mine is a fork of consumet.ts that has API routes in the same codebase. All I can offer is give you my API_URL, which is https://v1.api.ani.rohi.dev/api/dramacool, my apologies.

it's now working. it displays the homepage and popular. I can also search now. but there's an error occurred.
Upon clicking the image box to play the video it will display like this

You need to run pnpm db push on your terminal

wow .. its working now.. :)

i use this command pnpm drizzle-kit push:pg

hello
@gneiru while deploying it to vercel or netlify i got a error message .

build: Error occurred prerendering page "/sitemap.xml". Read more: https://nextjs.org/docs/messages/prerender-error
--
11:49:18.034 | build:
11:49:18.034 | build: error: relation "kd_episode" does not exist
11:49:18.034 | build:     at /vercel/path0/.next/server/app/sitemap.xml/route.js:9:29101
11:49:18.034 | build:     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
11:49:18.034 | build:     at async n_.execute (/vercel/path0/.next/server/app/sitemap.xml/route.js:33:28439)
11:49:18.034 | build:     at async at (/vercel/path0/.next/server/app/sitemap.xml/route.js:33:38298)
11:49:18.034 | build:     at async aa (/vercel/path0/.next/server/app/sitemap.xml/route.js:33:39203)
11:49:18.034 | build:     at async /vercel/path0/node_modules/.pnpm/next@14.1.4_@babel+core@7.24.0_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:6:42484
11:49:18.034 | build:     at async eI.execute (/vercel/path0/node_modules/.pnpm/next@14.1.4_@babel+core@7.24.0_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:6:32486)
11:49:18.035 | build:     at async eI.handle (/vercel/path0/node_modules/.pnpm/next@14.1.4_@babel+core@7.24.0_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:6:43737)
11:49:18.035 | build:     at async exportAppRoute (/vercel/path0/node_modules/.pnpm/next@14.1.4_@babel+core@7.24.0_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/export/routes/app-route.js:77:26)
11:49:18.035 | build:     at async exportPageImpl (/vercel/path0/node_modules/.pnpm/next@14.1.4_@babel+core@7.24.0_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/export/worker.js:175:20)
11:49:18.035 | build:  build:  ✓ Generating static pages (14/14)
11:49:18.041 | build:
11:49:18.041 | build: > Export encountered errors on following paths:
11:49:18.041 | build: 	/sitemap.xml/route: /sitemap.xml
11:49:18.109 | build:  ELIFECYCLE  Command failed with exit code 1.
11:49:18.122 | build: ERROR: command finished with error: command (/vercel/path0/) /pnpm8/node_modules/.bin/pnpm run build exited (1)
11:49:18.122 | build: command (/vercel/path0/) /pnpm8/node_modules/.bin/pnpm run build exited (1)
11:49:18.123 |
11:49:18.123 | Tasks:    0 successful, 1 total
11:49:18.123 | Cached:    0 cached, 1 total
11:49:18.123 | Time:    44.779s
11:49:18.123 | Summary:    /vercel/path0/.turbo/runs/2ecl4rkuLRFdTlXi1yhBB2sjuEX.json
11:49:18.123 | Failed:    //#build
11:49:18.123 |
11:49:18.123 | ERROR  run failed: command  exited (1)
11:49:18.182 | Error: Command "turbo run build" exited with 1

i recieved this error and i have no idea how to fix this can u help me with this

i use this command pnpm drizzle-kit push:pg

This command also works

i use this command pnpm drizzle-kit push:pg

This command also works

i got this error for this command

ERR_PNPM_RECURSIVE_EXEC_FIRST_FAIL  Command "drizzle-kit" not found
--
12:35:25.167 | Error: Command "pnpm drizzle-kit push:pg" exited with 1

Try pnpm i first then pnpm db:push

@gneiru
bro i tried but it stll says drizzle-kit not found

sh: line 1: drizzle-kit: command not found
--
12:59:37.167 | ELIFECYCLE  Command failed.
12:59:37.174 | WARN   Local package.json exists, but node_modules missing, did you mean to install?
12:59:37.196 | Error: Command "pnpm db:push" exited with 1

You dont have node modules so it will not work. You have to run pnpm install first, then wait for node modules to appear in your root directory. Finally, pnpm db:push will definitely not throw error.

@gneiru
bro i tried but it stll says drizzle-kit not found
sh: line 1: drizzle-kit: command not found
12:59:37.167 | ELIFECYCLE  Command failed.
12:59:37.174 | WARN   Local package.json exists, but node_modules missing, did you mean to install?
12:59:37.196 | Error: Command "pnpm db:push" exited with 1

You dont have node modules so it will not work. You have to run pnpm install first, then wait for node modules to appear in your root directory. Finally, pnpm db:push will definitely not throw error.

Hi @gneiru thanks to ur help i was able to deploy the site sucessfully.
but i have another help to ask with authentication when  i do the signin with google i get the eror 500:internal server error.
can u help me how to fix this.  this is my Redirect_uri
https://kdramax.vercel.app/api/auth/callback/google

Check your project's logs in vercel, it might help us debug the error

Check your project's logs in vercel, it might help us debug the error

here`s the log file
logs_result.json
it says something about environments variables being invalid.

Ah. Then, make sure you have env values for google client id and secret. Once you're done, hit redeploy on your latest production deployment.
Regarding edge invocation failing, what I can help atleast is to remove the line of code which set the runtime to edge in your api/auth/[...next-auth]/route.ts. If it still fails dynamically, let me know but edge in my case works fine. Vercel's edge function in your vercel workspace might be a factor too!

Ah. Then, make sure you have env values for google client id and secret. Once you're done, hit redeploy on your latest production deployment.
Regarding edge invocation failing, what I can help atleast is to remove the line of code which set the runtime to edge in your api/auth/[...next-auth]/route.ts. If it still fails dynamically, let me know but edge in my case works fine. Vercel's edge function in your vercel workspace might be a factor too!

i have already added all env variables before deploying the app but
the error accurs after the app is authorized


Resolved some warnings

Resolved warnings in

Team.js
Navbar.js
Footer.js
Example.js
etc.

yet few warnings are in the backend files so I will remove it later.

@akrishna0 Don't comment them just remove them and see if the project is working fine.

Please check the PR again updated the PR deleted all the unnecessary comments


First iteration of working melting PCM example

The old tests all now pass; but we need a new test for a melting PCM before merging this.


runtime error

Describe the bug
the runtime exec fails every time I try to run cbug.
To Reproduce
cbug ./fileName.out
Expected behavior
Should return memory report
Screenshots

Additional context
No TA was able to fix the problem

Was this compiled outside of cbug? Because it is being run in a virtual machine, you must use g++ from within cbug.


[SPARK-22203][SQL]Add job description for file listing Spark jobs

What changes were proposed in this pull request?
The user may be confused about some 10000-tasks jobs. We can add a job description for these jobs so that the user can figure it out.
How was this patch tested?
The new unit test.
Before:

After:

cc @gatorsmile

Test build #82460 has started for PR 19432 at commit aaf41dd.

Test build #82460 has finished for PR 19432 at commit aaf41dd.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/82460/
Test PASSed.

Thanks! Merging to master.


Player list flooded, no easy way to clean it!

My player list is flooded with a ton of names. I'd like to wipe it clean and start over. I don't know how to do this though!

Hey, you can delete %AppData%\XIVLauncher\pluginConfigs\PlayerTrack and it'll remove all your players and categories.

Awesome! Thanks for that!


test(x/gamm): remove liquidity events

Part of: https://github.com/osmosis-labs/osmosis/issues/1942
What is the purpose of the change
Tests remove liquidity events that should be emitted when a pool is exited.
Similarly to #2141, I noticed that they were emitted twice:

at the end of the message server
right after a pool state is updated.

I removed 1. while keeping 2.
No breaking changes.
Passthrough changes

moved AssertEventEmitted test helper to be defined on the suite. It is also useful for testing events in other modules
cleaned up some tests by creating variables for keepers and ctx
added suite.Run() to some table-driven tests

Testing and Verifying
Documentation and Release Note

Does this pull request introduce a new feature or user-facing behavior changes? no
Is a relevant changelog entry added to the Unreleased section in CHANGELOG.md? no
How is the feature or change documented? not applicable

Planning on merging this once CI passes. All comments are addressed and no API or state-breaking changes


Add gym monitoring to display result video in colab

#23
I add gym monitoring to display result video in colab. I don't remove existing method(JSA animation) because gym monitoring method is not working in jupyter notebook.
@Curt-Park Please review and approve it.

Thanks for the information. I will revert the JSA animation code of Rainbow-is-all-you-need for Jupyter execution.


Test_write_errors() fails: Expected 'E505: ' but got 'E503: …'

Test_write_errors() fails all the time on my xubuntu-18.04.5 x86_64 machine.
The test was recently introduced by:
commit 36f96a515109dc1fad279571a645c0f0d65f2de4 (tag: v8.2.2849)
Author: Yegappan Lakshmanan<EMAIL_ADDRESS>Date:   Thu May 13 18:33:16 2021 +0200

    patch 8.2.2849: bufwrite not sufficiently tested

    Problem:    Bufwrite not sufficiently tested.
    Solution:   Add a few more tests. (Yegappan Lakshmanan, closes #8192)

To Reproduce
$ cd vim/src/testdir
$ make test_writefile
...snip...
Executed 28 tests                        in   1.875718 seconds
1 FAILED:
Found errors in Test_write_errors():
command line..script /home/pel/sb/vim/src/testdir/runtest.vim[473]..function RunTheTest[44]..Test_write_errors line 53: Expected 'E505: ' but got 'E503: "/dev/loop0" is not a file or writable device': write

$ ls -l /dev/loop0
brw-rw---- 1 root plugdev 7, 0 mei 13 18:37 /dev/loop0

Environment

OS: xubuntu-18.04.5
Vim version

VIM - Vi IMproved 8.2 (2019 Dec 12, compiled May 14 2021 02:36:52)
Included patches: 1-2850
Compiled by pel@pel-cirrus7
Huge version with GTK3 GUI.

I am running Ubuntu 21.04 and the test passes there. If you manually
edit /dev/loop0 and run the ":write" and ":write!" commands, what error
code do you see? Do you run as a user who has root privileges?
Thanks,
Yegappan

The test was recently introduced by:
commit 36f96a515109dc1fad279571a645c0f0d65f2de4 (tag: v8.2.2849)
Author: Yegappan Lakshmanan @.***>
Date:   Thu May 13 18:33:16 2021 +0200
patch 8.2.2849: bufwrite not sufficiently tested

Problem:    Bufwrite not sufficiently tested.
Solution:   Add a few more tests. (Yegappan Lakshmanan, closes #8192)

To Reproduce
$ cd vim/src/testdir
$ make test_writefile
...snip...
Executed 28 tests                        in   1.875718 seconds
1 FAILED:
Found errors in Test_write_errors():
command line..script /home/pel/sb/vim/src/testdir/runtest.vim[473]..function RunTheTest[44]..Test_write_errors line 53: Expected 'E505: ' but got 'E503: "/dev/loop0" is not a file or writable device': write
$ ls -l /dev/loop0
brw-rw---- 1 root plugdev 7, 0 mei 13 18:37 /dev/loop0
Environment

OS: xubuntu-18.04.5
Vim version

VIM - Vi IMproved 8.2 (2019 Dec 12, compiled May 14 2021 02:36:52)
Included patches: 1-2850
Compiled by @.***
Huge version with GTK3 GUI.  Features included (+) or not (-):
+acl               -farsi             +mouse_sgr         +tag_binary
+arabic            +file_in_path      -mouse_sysmouse    -tag_old_static
+autocmd           +find_in_path      +mouse_urxvt       -tag_any_white
+autochdir         +float             +mouse_xterm       -tcl
-autoservername    +folding           +multi_byte        +termguicolors
+balloon_eval      -footer            +multi_lang        +terminal
+balloon_eval_term +fork()            -mzscheme          +terminfo
+browse            +gettext           +netbeans_intg     +termresponse
++builtin_terms    -hangul_input      +num64             +textobjects
+byte_offset       +iconv             +packages          +textprop
+channel           +insert_expand     +path_extra        +timers
+cindent           +ipv6              +perl              +title
+clientserver      +job               +persistent_undo   +toolbar
+clipboard         +jumplist          +popupwin          +user_commands
+cmdline_compl     +keymap            +postscript        +vartabs
+cmdline_hist      +lambda            +printer           +vertsplit
+cmdline_info      +langmap           +profile           +virtualedit
+comments          +libcall           -python            +visual
+conceal           +linebreak         +python3           +visualextra
+cryptv            +lispindent        +quickfix          +viminfo
+cscope            +listcmds          +reltime           +vreplace
+cursorbind        +localmap          +rightleft         +wildignore
+cursorshape       -lua               -ruby              +wildmenu
+dialog_con_gui    +menu              +scrollbind        +windows
+diff              +mksession         +signs             +writebackup
+digraphs          +modify_fname      +smartindent       +X11
+dnd               +mouse             +sound             -xfontset
-ebcdic            +mouseshape        +spell             +xim
+emacs_tags        +mouse_dec         +startuptime       +xpm
+eval              +mouse_gpm         +statusline        +xsmp_interact
+ex_extra          -mouse_jsbterm     -sun_workshop      +xterm_clipboard
+extra_search      +mouse_netterm     +syntax            -xterm_save
system vimrc file: "$VIM/vimrc"
user vimrc file: "$HOME/.vimrc"
2nd user vimrc file: "~/.vim/vimrc"
user exrc file: "$HOME/.exrc"
system gvimrc file: "$VIM/gvimrc"
user gvimrc file: "$HOME/.gvimrc"
2nd user gvimrc file: "~/.vim/gvimrc"
defaults file: "$VIMRUNTIME/defaults.vim"
system menu file: "$VIMRUNTIME/menu.vim"
fall-back for $VIM: "/usr/local/share/vim"
Compilation: clang-12 -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK -pthread -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -O2 -D_REENTRANT -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -DEXITFREE -DABORT_ON_INTERNAL_ERROR
Linking: clang-12 -Wl,-E -L/usr/local/lib -Wl,--as-needed -o vim -lgtk-3 -lgdk-3 -lpangocairo-1.0 -lpango-1.0 -latk-1.0 -lcairo-gobject -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0 -lSM -lICE -lXpm -lXt -lX11 -lXdmcp -lSM -lICE -lm -ltinfo -lselinux -lcanberra -lacl -lattr -lgpm -ldl -Wl,-E -fstack-protector-strong -L/usr/local/lib -L/usr/lib/x86_64-linux-gnu/perl/5.26/CORE -lperl -ldl -lm -lpthread -lcrypt -L/usr/lib/python3.6/config-3.6m-x86_64-linux-gnu -lpython3.6m -lpthread -ldl -lutil -lm

On Fri, May 14, 2021, 03:35 vim-dev ML @.***> wrote:

Hi Dominique,
On Thu, May 13, 2021 at 6:01 PM Dominique Pellé @.***>
wrote:

Test_write_errors() fails all the time on my xubuntu-18.04.5 x86_64
machine.

I am running Ubuntu 21.04 and the test passes there. If you manually
edit /dev/loop0 and run the ":write" and ":write!" commands, what error
code do you see? Do you run as a user who has root privileges?

II get E503, as when I run the test.
I do not run as root but as regular user.
Sorry I'm brief as my Internet is currently broken (sent from my phone).
Dominique

Hi,
On Fri, May 14, 2021 at 12:36 AM Dominique Pellé @.***>
wrote:

On Fri, May 14, 2021, 03:35 vim-dev ML @.***> wrote:

Hi Dominique,
On Thu, May 13, 2021 at 6:01 PM Dominique Pellé @.***>
wrote:

Test_write_errors() fails all the time on my xubuntu-18.04.5 x86_64
machine.

I am running Ubuntu 21.04 and the test passes there. If you manually
edit /dev/loop0 and run the ":write" and ":write!" commands, what error
code do you see? Do you run as a user who has root privileges?

II get E503, as when I run the test.
I do not run as root but as regular user.
Sorry I'm brief as my Internet is currently broken (sent from my phone).

I tried running the test on a Xubuntu 18.04.5 system and this test
passes without any problems.
If I manually execute the ":write" and ":write!" commands for
/dev/loop0 as root, then E503 error message is displayed instead
of E505.

Yegappan

What is the output of ls -l /dev/loop0 for you?
I posted the output of that command on my system in the bug description.

Hi,
On Fri, May 14, 2021 at 11:47 AM Dominique Pellé @.***>
wrote:

What is the output of ls -l /dev/loop0 for you?
I posted the output of that command on my system in the bug description.
The output of the relevant commands from the Xubuntu system is below:

$ ls -l /dev/loop0
brw-rw---- 1 root disk 7, 0 May 14 12:15 /dev/loop0
$ uname -a
Linux yega-xubuntu 5.4.0-73-generic #82~18.04.1-Ubuntu SMP Fri Apr 16
15:10:02 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
$ id
uid=1000(yega) gid=1000(yega)
groups=1000(yega),4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),118(lpadmin),126(sambashare)
$ groups
yega adm cdrom sudo dip plugdev lpadmin sambashare

Yegappan

It appears the problem is that somehow /dev/loop0 is not considered read-only.
The check for it being a special device, which you can't write to anyway comes later.
So the ":write /dev/loop0" may or may not say the file is readonly, but
it always fails for ":write! /dev/loop0" because it's a special device.
We should probably check for a special device earlier, so that it's clear adding a "!" won't help.

I did not reply earlier as I had a broken internet (now resolved).
Anyway, this ticket was fixed in the mean time.
For the record and for comparison with what @yegappan posted earlier, this is what I get on my machine where the test used to fail:
$ ls -l /dev/loop0
brw-rw---- 1 root plugdev 7, 0 mei 18 04:59 /dev/loop0

$ uname -a
Linux pel-cirrus7 4.15.0-143-generic #147-Ubuntu SMP Wed Apr 14 16:10:11 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

$ id
uid=1000(pel) gid=1000(pel) groups=1000(pel),4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),118(lpadmin),126(sambashare),132(libvirt)

$ groups
pel adm cdrom sudo dip plugdev lpadmin sambashare libvirt


[iOS] Can't build with react-native 0.67.4

:beetle: Description

I'm trying to build with react-native 0.67.4 bare react-app on iOS but it always fails with the following errors:
node_modules/react-native-sound/RNSound/RNSound.m:236:44: Implicit declaration of function 'RCTJSErrorFromNSError' is invalid in C99

node_modules/react-native-sound/RNSound/RNSound.m:236:44: Declaration of 'RCTJSErrorFromNSError' must be imported from module 'React.RCTUtils' before it is required

node_modules/react-native-sound/RNSound/RNSound.m:236:44: Conflicting types for 'RCTJSErrorFromNSError'

It works fine with android though.
XCode: Version 13.3 (13E113)
:beetle: What is the observed behavior?

Build fails when building for ios.
:beetle: What is the expected behavior?

It should not fail building.
:beetle: Please post your code:
N/A
:bulb: Does the problem have a test case?

:bulb: Possible solution

:bulb: Is there a workaround?

:bulb: If the bug is confirmed, would you be willing to create a pull request?

Is your issue with...

[x] iOS
[ ] Android
[ ] Windows

Are you using...

[x] React Native CLI (e.g. react-native run-android)
[ ] Expo
[ ] Other: (please specify)

Which versions are you using?

React Native Sound: 0.11.2
React Native: 0.67.4
iOS: 12
Android:
Windows:

Does the problem occur on...

[x] Simulator
[x] Device

If your problem is happening on a device, which device?

Device: N/A

Possible workaround:
Applying the following patch, works:
diff --git a/node_modules/react-native-sound/RNSound/RNSound.m b/node_modules/react-native-sound/RNSound/RNSound.m
index df3784e..17e5894 100644
--- a/node_modules/react-native-sound/RNSound/RNSound.m
+++ b/node_modules/react-native-sound/RNSound/RNSound.m
@@ -1,10 +1,5 @@
 #import "RNSound.h"
-
-#if __has_include("RCTUtils.h")
-#import "RCTUtils.h"
-#else
 #import <React/RCTUtils.h>
-#endif

 @implementation RNSound {
     NSMutableDictionary *_playerPool;


UPS to Azure AD connection setup missing

Great info on the permissions' required for the UPS to Azure AD connection but next steps to setup the UPS make no mention of using AAD.  https://docs.microsoft.com/en-us/SharePoint/administration/manage-profile-synchronization

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

ID: f95ecc6f-90c2-338c-cb74-f202da4afd4b
Version Independent ID: b7c5da87-33d9-e82d-f3f5-20ab9e970c58
Content: Enable SharePoint User Profile service with Azure AD DS
Content Source: articles/active-directory-domain-services/deploy-sp-profile-sync.md
Service: active-directory
Sub-service: domain-services
GitHub Login: @Justinha
Microsoft Alias: justinha

@abates100 sorry for delay and thanks for raising this. You are right, it's confusing to refer to Next steps in this case because you should really have the UPS service account name before you even begin. This is mentioned in the prerequisites but I added how to get the account name and clearer links to more info.


Validate issue

@dadhi First of all thanks a lot, DryIoc is really fast, but also very easy to use.
We use it and have multiple scopes defined:

"global"

then thread scoped

then custom scoped

We always call Validate, and just found one case where Validate wouldn't spot an issue:

class CS is custom scoped
class TS is thread scoped, its constructor requires CS

In theory that shouldn't be OK: TS has a more general scope/lifetime, it shouldn't be able to use CS.
In practice it works and it's really bad: TS will be constructed with an instance of CS.
TS has a longer lifetime but it will still hold CS which shouldn't be used anymore.
Do you think we could throw an exception during Validate for such cases?

You have a very specific setup here.
Maybe it make sense to add a pluggable Validation rule.. or could you check the validity of reuse within IReuse.CanApply implementation?
Do you use a custom IReuse implementation or just a scope with the special name?

We don't use a custom IReuse implementation, but now that I think about what we do, for sure Validate cannot enforce anything... It's our fault for assuming that.
However I still believe this misconfiguration could be detected during runtime when resolving things.
What is your opinion?
Our registration is kind of like:
using DryIoc;
using System;

namespace TestDryIoc
{
    class Program
    {
        static void Main(string[] args)
        {
            using (var container = new Container())
            {
                container.Register<SomethingDefinedInOuterScope>(Reuse.InCurrentNamedScope("Outer"));
                container.Register<SomethingDefinedInInnerScope>(Reuse.InCurrentNamedScope("Inner"));
                container.Validate();

                using (var outerScopedContainer = container.OpenScope(name: "Outer"))
                {
                    using (var innerScopedContainer = container.OpenScope(name: "Inner"))
                    {
                        var item = container.Resolve<SomethingDefinedInOuterScope>();
                    }
                }
            }

            Console.WriteLine("Hello World!");
        }
    }

    class SomethingDefinedInOuterScope
    {
        public SomethingDefinedInOuterScope(SomethingDefinedInInnerScope dependency) // we were expecting DryIoC to not allow that, it's wrong since the dependency has a tighter lifetime
        {

        }
    }

    class SomethingDefinedInInnerScope
    {

    }
}

Yep, now it is much clearer. Need to think about this.

@molinch
Was thinking how to address this issue.
The main problem is that we are not defining the scope hierarchy in registration - the Reuse.ScopedTo(name) is just a binding to that named scoped. It may be perfectly valid to have this named scope in unnamed scope and the vice versa.
So probably the validity should be defined externally via some validation rules applied to container. Validate may provide the rules as a sugar for thing like this Rules.WithValidation( req => req.Reuse.Name != null && req.Parent != null && req.Parent.Reuse.Name == null ? Error.Of("Hey, stop!") : null)

Given that situation with ensuring the scope hierarchy is quite common (see https://stackoverflow.com/questions/60092293/dryioc-scope-and-reuse) maybe we can add a sugar ValidateScopeHierarchy(name1, name2).
Maybe it can validate opening scopes too, hmm...

Maybe it can validate opening scopes too, hmm...

I am not sure that it is useful anymore because the check is happen at runtime operation - when the scope is opening and not in validation phase.
Regarding the check maybe its enough to expose the Lifetime in Reuse.Scoped(lifetime: Reuse.DefaultScopedLifetime - 1)

Another interesting idea is to remove the runtime checks after Validate() is called.
Why to double-check?
To ensure that container is not changed after Validate DryIoc already has a thing c.WithNoMoreRegistrationAllowed()`


undefined symbol: napi_add_finalizer

I have upgraded the library from 0.24.1 to 0.25.0 because the problems with the former. I have removed node_modules and run yarn install. When running the application this is what I get:
/usr/bin/node: symbol lookup error: /home/alex/dev/src/other/strenux/strenux-api/node_modules/sharp/build/Release/sharp.node: undefined symbol: napi_add_finalizer

I cannot do anything, Sharp has broken my project.
Node: 12.16.0
OS: Ubuntu 18

Hi, it looks like some of the prebuilt binaries for v0.25.0 erroneously used N-API v5 rather than v4. I'll roll out a fix for this in the next hour or so.

Although there is a problem, I don't think it should affect you as N-API v5 was added in Node.js 12.11.0 and you say you're using Node.js 12.16.0.
Are you sure about the version being used at runtime, as I would not expect this error from Node.js 12.16.0? I notice you've commented on other issues recently about runtime problems - perhaps you have multiple, conflicting versions of Node.js made available at runtime?

v0.25.1 pins N-API to v3 and is now available, thanks for reporting.

Hi @lovell, thanks for informing. I have tested the new version v0.25.1 with Node 12.16.0 and 13.8.0 and it's working fine after a clean install (removed node_modules and did yarn install).
I was using Node 12.16.0 and upgraded recently to 13.8.0.
I do use nvm indeed for managing different Node.js versions. I never had problems with nvm and Sharp before, I started seeing these issues recently (few weeks ago).


Environment variable not found: DIRECT_DATABASE_URL.

npx prisma db push && prisma migrate dev && prisma generate
Prisma schema loaded from prisma\schema.prisma
Datasource "db": PostgreSQL database
Error: Prisma schema validation - (get-config wasm)
Error code: P1012
error: Environment variable not found: DIRECT_DATABASE_URL.
-->  schema.prisma:4
|
3 |   url               = env("DATABASE_URL")
4 |   directUrl         = env("DIRECT_DATABASE_URL")
|
Validation Error Count: 1

I think it is the same answer as my previouse post
#56

Hey all. I've just simplified the repo to remove auth and payments so you can clone and deploy very easily, only with a Replicate environment variable. Try it out and if you still have any problems, please open a new issue and I will take a look!


[Top Navbar] Change the user name dynamically

Get the value of Name and User's profile picture URL from Google Authentication response

Set the name and image here: (accessible from AdminNavbar.js)

Need to use React Context to implement this

Look for UserProvider inside src/context/UserContext.js

Set a new name attribute and profileImage that stores image URL

@meet59patel can I work on this issue ?

@meet59patel would like to work on this issue.


Add build failure notification

Description
Sends build failure message to notification chat
Fixes # (issue)
Related Pull Requests (remove if not relevant)

Pull request 1
Pull request 2

One line release note:

One line describing the feature/improvement/fix made by this PR

Type of change
Please delete options that are not relevant.

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

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[ ] Test A
[ ] Test B

Test Configuration:

Ballerina Version:
Operating System:
Java SDK:

Checklist:
Security checks

[ ] Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines?
[ ] Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets?

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Charuka Tharindu seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Revamp to React JS

I would like to implement React JS in the project so it can be further enhanced & look more interactive.
First approach is to design a landing page for the Canvas-Editor.
@vishanurag can you assign me this issue as GSSOC-ext contributor & add labels to it.

Hi @vishanurag can you assign me this issue


Add POJO classes required for cluster state publication from remote

Description
Add the POJO classes required for publication of cluster state from remote repository.
Related Issues
Resolves #13791
Check List

[x] New functionality includes testing.

[x] All tests pass

[x] New functionality has been documented.

[x] New functionality has javadoc added

[ ] API changes companion pull request created.
[x] Failing checks are inspected and point to the corresponding known issue(s) (See: Troubleshooting Failing Builds)
[x] Commits are signed per the DCO using --signoff
[ ] Commit changes are listed out in CHANGELOG.md file (See: Changelog)
[x] Public documentation issue/PR created

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

This PR resolves #14108 as well.

❌ Gradle check result for https://github.com/opensearch-project/OpenSearch/commit/f7c62e4168a68ebd19d9737498fe6d7607a05e7a: FAILURE

Unrelated test is failing, opened a new issue for the test
org.opensearch.index.reindex.ReindexBasicTests.testCopyManyWithSlices: #14120

❌ Gradle check result for https://github.com/opensearch-project/OpenSearch/commit/955871a3d47d4e49a9945aa2c2d804c3b8e1482a: FAILURE

Already identified as flaky:
org.opensearch.upgrades.IndexingIT.testIndexingWithSegRep - #12336

❌ Gradle check result for https://github.com/opensearch-project/OpenSearch/commit/955871a3d47d4e49a9945aa2c2d804c3b8e1482a: FAILURE

Created new issue #14139 for unrelated failure: org.opensearch.index.reindex.CancelTests.testUpdateByQueryCancelWithWorkers

❌ Gradle check result for https://github.com/opensearch-project/OpenSearch/commit/20cb7c02ca52e9d81adc52504da717db0d49609c: FAILURE

org.opensearch.remotestore.RemoteStoreStatsIT.testDownloadStatsCorrectnessSinglePrimaryMultipleReplicaShards - #10152
org.opensearch.search.basic.SearchWithRandomExceptionsIT.testRandomExceptions {p0={"search.concurrent_segment_search.enabled":"false"}} is unrealted failure, creating a new issue for this.

@shiv0408 please raise manual backport and update version checks accordingly.


[Request for External] Codeunit 12 "Gen. Jnl.-Post Line", function PostGenJnlLine

Hello, we cannot use RunWithCheck.
We tried that function, it results in a "G/L entry already exists error", as it seems to reset internal values of the codeunit.
The requirement is to post additional G/L entries within an existing RunWithCheck call.
Therefore, please change function PostGenJnlLine to global.
Originally posted by @ChristianFeitl in https://github.com/microsoft/ALAppExtensions/issues/20707#issuecomment-1285536743

No, this is wrong way, you cannot use this method globally, please read this first
https://learn.microsoft.com/en-us/dynamics365/business-central/design-details-posting-engine-structure

Ok, thanks for the info but all the functions mentioned in the article are local too (looked into BC20 CU05).
So I cannot use them either in our extension.

I don't know if you receive notifications, therefore I do it this way, @AlexanderYakunin

You should not expect any external functions for 20.x, we do not make such changes to PROD versions. Try to use existing events and add what you need in subscribers.
We only provide it for Master (currently it is 22.x).

@AlexanderYakunin , to my understanding subscribers cannot help me with the task of adding G/L entries.
On the other hand if we do not get the possibilty to use the mentioned functions we have to use a changed BaseApp which is not an option.

Please explain in more details what you are doing and maybe I will guide you to right direction.

While reviewing our code to answer your request I maybe found a way to solve this issue. I will look more into that and will open a new request if necessary. Thank you for guiding me!


Params are not working properly

Hello! I hope you can answer this issue, for sure it´s something I´m doing wrong but...hope to solve it soon.
I´ve created the map component and the html and this is the code:
HTML:

TS (Only ngx-leaflet options):
options = {
    layers: [
      tileLayer('http://{s}.tile.openstreetmap.org/{z}/{x}/{y}.png', {
        maxZoom: 19,
        attribution:
          '© OpenStreetMap',
      }),
    ],
    zoom: 17
  };

  center = latLng(lat, lng);

  zoomControl = {position: 'bottomright'};

  fitBounds: number[][] = [[0,0]];

  fitBoundsOptions: any = {
    maxZoom: 17,
    animated: true
  };

  tree: TreeviewItem[];

  drawItems: FeatureGroup = featureGroup();

  readonly drawOptions = {
    position: 'topright',
    draw: {
      circle: false,
      circlemarker: false
    },
    edit: {
      featureGroup: this.drawItems,
      remove: false
    }
  };

  readonly drawLocalOptions = {
    draw: {
      toolbar: {
        buttons: {
          polyline: 'Medir línea',
          polygon: 'Medir área',
          rectangle: 'Zoombox',
          marker: 'Obtener coordenadas'
        }
      },
      handlers: {
        polyline: {
          tooltip: {
            start: 'Start',
            edit: 'Edit'
          }
        }
      }
    }
  };

The problem here is that POSITION param is not working anycase and DRAW params like circle or circlemarker that I´ve put in FALSE are not working too.
What can be the problem?

Solved, was an issue with map div


Fix status update reminders a multiple run in a channelcontext

Summary
Makes status update reminders work with multiple runs in a channel.
Problem
We were assuming one run per channel and we navigated channel->run at redux selector expecting one only result.
That broke UI by showing same run name for multiple status-update-request in the same channel when multiple were asked. Additionally, when you wanted to snooze the status update, the post wasn't deleted.
Approach
Inject playbookRunId in the post.props when is type=custom_update_status:

for new ones through code changes
for old ones with a SQL migration

In the webapp component, several changes have been done:

Stop relying on redux data, removed selector
Exrtact playbookRunId from post.props and use an inline GraphQL query to get the relevant data

Extra

[X] server e2e added
[x] cypress e2e added
[ ] MySQL migration

Ticket Link
Fixes https://github.com/mattermost/mattermost-plugin-playbooks/issues/1741
Checklist

[ ] Telemetry updated
[ ] Gated by experimental feature flag
[X] Unit tests updated

@agarciamontoro I've added you as a reviewer to increase confidence & awareness with the database migration (posts table).

Was my review removed by on purpose?

Was my review removed on purpose?

Yes, based on the Ci failures and @lieut-data feedback

Ok! Feel free to re-assign me if needed :)


Display fee configuration in node information

Display fee configuration from config.toml in node information.
/pactus/network/get_node_info

{
  "moniker": "foobar",
...
  "fee": {
    "daily_limit": 250, // uint32
    "unit_price": 0.000005, // float64
    "fixed_fee": 0.01 // float64
  }
}

@b00f We display consumption configuration or not planning?

I don't think we need to add in in gRPC. Please keep this issue open. We may add it in future.

I don't think we need to add in in gRPC. Please keep this issue open. We may add it in future.

Ok, remove this issue from parent issue.


Actually making the clang format test properly fail sanity.

Looks like a few faults:
++ pwd
+ docker run -e TEST=true --rm=true -v /var/local/git/grpc:/local-code -t grpc_clang_format /clang_format_all_the_things.sh
find: `/local-code/src/core': No such file or directory

Beautiful. This worked 5 seconds ago on my machine. Meaning it never actually worked on Jenkins. Yay.

Can one of the admins verify this patch?

Can one of the admins verify this patch?

I picked this up


Table component

<Table data {...prefs}>
I would need something similar to slick grid in which from preferences we can display selected columns in a defined format and:

there is a callback onHover row
there is a callback onClick row
we can add actions in the row
from preferences we can select the properties to display, the component to render it and the options to render it.

We could foreseen the possibility to edit a value.

data.json.zip
{
  columns: [
    {
       jpath: ['em'],
       renderer: Numeral,
       rendererOptions: {
         format: '0.0000'
       }
    },
    {
       jpath: ['ionization','mf'],
       renderer: 'MF'
    }
  ]
}

Related to https://github.com/zakodium-oss/react-science/issues/252


[ESP32] Notify-update-applied command and fixed initialization order

Problem

Added IsFirstImageRun and ConfirmCurrentImage definations for ESP32.
Fixed initialization order of ESP32.
Fixes #13760

Change overview
Schedule notify-update-applied command.
Testing

Manually tested esp32 apps.

/rebase


Transferred token is shown under "Currently holding"

Highlighted token has been transfered to another wallet, yet it is shown under "Currently holding"

Like happens if both sellTransaction and buyTransaction are transfer events.
Will fix together with #12

Fixed


Addon/compatibility for mobile android firefox

Is your feature request related to a problem? Please describe.
As it stands there doesn't seem to be a way to install this script into firefox on mobile.
Describe the solution you'd like
Maybe if it could be made into a plugin or addon it might be easier to install or make. Otherwise I don't know coding that well so I couldn't say.
Describe alternatives you've considered
There arn't a lot of alternatives, using tor maybe. But tor can be slow and for a decent many people it is overkill. Don't get me wrong more privacy/security is good but that trade off might not be worth for some.
Additional context
The reason I bring this up is because it was recomended by chris titus tech that standard firefox is great but with this script it's almost as good as it gets. However a lot of people including myself use mobile browsers often.
So if this could be made to work with it that would benifit a lot of people that previously didn't have access.

Is your feature request related to a problem? Please describe. As it stands there doesn't seem to be a way to install this script into firefox on mobile.
Describe the solution you'd like Maybe if it could be made into a plugin or addon it might be easier to install or make. Otherwise I don't know coding that well so I couldn't say.
Describe alternatives you've considered There arn't a lot of alternatives, using tor maybe. But tor can be slow and for a decent many people it is overkill. Don't get me wrong more privacy/security is good but that trade off might not be worth for some.
Additional context The reason I bring this up is because it was recomended by chris titus tech that standard firefox is great but with this script it's almost as good as it gets. However a lot of people including myself use mobile browsers often.
So if this could be made to work with it that would benifit a lot of people that previously didn't have access.

Unfortunately there is no way to make this work on mobile.
Your best bet is to configure the settings described in the config manually. Or if your threat model allows, run this script on a pc that is signed into firefox sync, and sync the settings to mobile. Otherwise just use Firefox Focus and add Ublock Origin. That'll get you most of the way there.

@simeononsecurity So I did the sync method because it's seems fine to me. How would I check to make sure it applied?
This probably goes for the script regardless of the way I installed it. Either just on windows or windows and mobile.
Also, it might be nice to add to the instructions as a verification step.

@simeononsecurity So I did the sync method because it's seems fine to me. How would I check to make sure it applied? This probably goes for the script regardless of the way I installed it. Either just on windows or windows and mobile. Also, it might be nice to add to the instructions as a verification step.

Just have to go into your mobile settings and check if it synced.


Resolve index out of range when running locally

This seeks to close #668.
Removed the if block so that storageAddr is used, preventing the controller from panicking if RUNTIME_NAMESPACE is non-empty and doesn't contain hyphens

@pjbgf Thanks for the feedback. I've signed off on the latest commit. Let me know if there is more I should do.

@pjbgf I have squashed the previous commits and signed it off with Signed-off-by: full name <email>  however, the DCO check has still failed.  Is there something I have missed?

@EdwinWalela Your branch current have 4 commits, you can drop the last 2 by resetting the state back to the second commit:
git reset 1bd61efa6389fa01a20a06d33542e5b2973f8078
You can then squash the two commits by rebasing interactively:
git rebase -i HEAD~2
You will be shown a list of the commits prefixed with "pick", change the second commit's prefix to "s" or "squash". Save and exit (:wq).
Then you will be presented with the commit message, which you can amend to become a single message with the correct signature.

@pjbgf  Thanks for the help, I noticed I did a mistake on renaming the sign off. I'll open a new PR instead.


Eloquent: Is it possible to change table name on runtime?

Hello,
Given that I have some tables that share a common structure, like "something_1", "something_2", "something_3".
Is it possible to switch the target $table that my model will handle?
Thanks

https://stackoverflow.com/questions/26757452/laravel-eloquent-accessing-properties-and-dynamic-table-names


field offset wrong at src_user and source_name in transforms.conf

Describe the bug
In default/transforms.conf, there was a time when src_user was repalced by source_name in the transforms.conf but that does not match the format of the logs. This causes all fields after src_ip to be mislabeled (an offset +1 according to the log spec and examples from the field.
Expected behavior
We expect timeout_threshold to appear in the timeout_threshold field and action_flags to appear in the action_flags field, etc
Current behavior
action_flags appears in the device_group_level1 field, sequence_number appears in the action_flags field.
Given PANOS 11 and at least as far back as panos9 : https://docs.paloaltonetworks.com/pan-os/11-0/pan-os-admin/monitoring/use-syslog-for-monitoring/syslog-field-descriptions/user-id-log-fields
Format: FUTURE_USER, Receive Time, Serial Number, Type, Threat/Content Type, FUTURE_USE, Generated Time, Virtual System, Source IP, User, Data Source Name, Event ID, Repeat Count, Time Out Threshold, Source Port, Destination Port, Data Source, Data Source Type, Sequence Number, Action Flags, Device Group Hierarchy Level 1, Device Group Hierarchy Level 2, Device Group Hierarchy Level 3, Device Group Hierarchy Level 4, Virtual System Name, Device Name, Virtual System ID, Factor Type, Factor Completion Time, Factor Number, User Group Flags, User by Source, Tag Name, High Resolution Timestamp, Origin Data Source, FUTURE_USE, Cluster Name
src_user and source_name are two distinct fields, where src_user comes first and source_name comes second.
Possible solution
Add src_user before source_name in the fields list in transformst.conf
[extract_userid]
DELIMS = ","
FIELDS = "future_use1","receive_time","serial_number","log_type","log_subtype","version","generated_time","vsys","src_ip","source_name","event_id","repeat_count","timeout_threshold","src_port","dest_port","source","source_type","sequence_number","action_flags","devicegroup_level1","devicegroup_level2","devicegroup_level3","devicegroup_level4","vsys_name","dvc_name","vsys_id","factor_type","factor_completion_time","factor_number"
should be:
[extract_userid]
DELIMS = ","
FIELDS = "future_use1","receive_time","serial_number","log_type","log_subtype","version","generated_time","vsys","src_ip","src_user","source_name","event_id","repeat_count","timeout_threshold","src_port","dest_port","source","source_type","sequence_number","action_flags","devicegroup_level1","devicegroup_level2","devicegroup_level3","devicegroup_level4","vsys_name","dvc_name","vsys_id","factor_type","factor_completion_time","factor_number"
Steps to reproduce
If you just look at the source_name, action_flags or any field following src_ip then it should be clear that the positional fields are off by 1.
Context
This bug corrupts data models and breaks CIM
Your Environment

This fix is part of PR #294


[#1376] Add livedata android extension.

I gave this a go but could use a bit of guidance on how it should look like for the clients.
The tricky bit is that given LiveData has no error propagation I would have to either wrap the returned value with a data class that also holds an Exception or do it the same way as Room which is:

LiveData<Value>: Will emit a value if exists (filter out nulls) or only the first match when multiple rows returned on the same cursor and ignore the rest.
LiveData<List<Value>>: easy just matches Query#executeAsList()

Also, thank you for taking this on!

I failed to read your pull request description early enough in this process. I started looking into this more by writing more test cases and I don't think we can support live data at all. Problems in your query, the data, or the mapper which cause an exception have nowhere to go. We could send them to your supplied executor's uncaught exception handler, but it's unlikely that will actually go anywhere useful. We can't crash synchronously because we would be blocking the caller thread which can be the main thread. I have no idea how people use live data with Room. It seems like a giant anti-pattern, and I feel somewhat validated in resisting it in Retrofit as well. Forcing everything into our own sealed class doesn't feel like a great solution either.

Yeah after working on it and comparing it to the coroutines or rxjava extensions this one seems weird...
As for your Room comment I think they enforce clients to use a background thread by crashing if they use the main thread (this can be overriden by calling a static method). Errors just get logged on the background...
As promised I'll do the test module for the tests after :)

But what about if the query contains a semantic error that they cannot validate at compile-time? That throws an exception when executing and you're saying that just gets logged and the consumer of the live data is never notified?

Sorry for the delay!
Scratch what I said about the LiveData extension in Room. I simulated a crash when Room is fetching data with the cursor and it did propagate and crashed the app. Sorry about that, I barely use LiveData :sweat_smile:

I've never used LiveData. I'm not sure whether it makes sense to ship something that has unrecoverable behavior like that. Plus it's on the main thread which means we have to round-trip through the main thread for every query.
Do you have any thoughts on it now that you explored it more?

I'm going to close this because at present we have no plans to expose LiveData directly. It's not a good fit for exposing the result of a database query. It's really not a good fit for anything but the very last bridge over into your UI despite having widespread usage nearly everywhere else.
Sorry that you did all this work and we're just going to throw it away. But having never used LiveData I didn't know that it was unfit for the use case going in.


Hardhat with external dependency

Hi I am using typeChain with hardhat.
I try to import dependency (json file).
Is there any way to include json path (in node_modules folder) when generating typeChain files

I think currently there is no way to achieve it. Thanks for raising this. I will make sure to add it in: https://github.com/ethereum-ts/TypeChain/pull/363

btw. as a quick workaround you can always run TypeChain again as a separate build step (and for example set outDir to something else). Ugly but it should work.

Yeah, right now, I am doing that way.
The thing is it will create 2 typechain folders (1 for my repo and 1 for the library), so it is kind of ugly solution

Sorry, I decided to drop it from the release. Feel free to pick it up.

people who use the Uniswap V3 npm artifacts probably want this

people who use the Uniswap V3 npm artifacts probably want this

+1. I ended up doing this as a workaround:
https://github.com/omarish/uniswap-v3-staker/blob/55c0b03f68eef947b41205ce6623c0f3f13292ad/hardhat.config.ts#L9-L32

people who use the Uniswap V3 npm artifacts probably want this

Actually, I work at Kyber. :))))
But we built a lot of bridge reserve and tried to publish our artifacts as well

The good news is that @ducquangkstn 's fix looks good. Just needs a little bit of tweaking so this should be done soon.


Build failed: ConcurrentModificationException in Github Action

Current Behavior
Tried Gradle 8.8-8.10. Buildable at local, but not at Action.
Scan: Build Scan® | Develocity
Action log: build: use gradle 8.8 · SettingDust/preloading-tricks@8198e6e · GitHub
Expected Behavior
No error like in local
Context (optional)
No response
Steps to Reproduce
The project is complex. I can't find out what's could be the reason. Need help to provide a minimal reproducible repo
Gradle version
8.10
Build scan URL (optional)
https://scans.gradle.com/s/5crxbewwmtgqc
Your Environment (optional)
No response

This is unlikely to be specific to the GitHub Action execution. What can happen is that pre-existing local state prevents the error from being observed.

I tried re-clone the project and build --refresh-dependencies but still no error.


Make dialyxir and ex_doc runtime: false

Luckily neither was available for :prod builds, so the dependencies
would propogate to hex.pm. However, there was some confusion on other
projects when they got built into the runtime issue and at least one
person ran into wx being pulled in by dialyxir. This changes avoids the
surprise by forcing those deps to runtime: false. It's also important
that their :only settings doesn't let them to propogate into :prod
builds, but that wasn't a problem here.

Thanks, @fhunleth. I will push a new release today.

Thanks!


Add support for keeping the camera state when switching files

Add a new option keep-camera-between-file for the global default behavior
Add _keeping_camera variants to the commands load_{previous,next}_file_group
Add default key bindings to the above new commands
Add tests and docs

@mwestphal Do you have any idea on how to fix TestInteractionCheatsheetAnimationNameRaytracing on macos 9.3.1/9.2.6? The error is rendering difference with reference image: 0.0609307 is higher than the threshold of 0.05. I guess it is some font rendering problem, but not sure how to reproduce/fix it as I don't have the development environment.

@mwestphal Do you have any idea on how to fix TestInteractionCheatsheetAnimationNameRaytracing on macos 9.3.1/9.2.6? The error is rendering difference with reference image: 0.0609307 is higher than the threshold of 0.05. I guess it is some font rendering problem, but not sure how to reproduce/fix it as I don't have the development environment.

This failure is expected because you are adding an interaction, which is shown in the spreadsheet.
If you do not have the raytrading setup locally, you can easily grab the new baselines from the CI, right here:
https://github.com/f3d-app/f3d/actions/runs/12216735579
Let me know if you need further help :)
You can also ask such question on discord for faster feedback

Please also rebase on master, some change were just merged and they conflich with some baselines updates.


Add a couple of integration tests

@jpkrohling the new itests are not passing yet, hence do not merge yet. If you could just have preliminary look. As promissed earlier today, I have split the the changes into two commits.

With 336cfe5 the tests should be passing. This PR is ready to be merged from my PoV.

hm... Appveyor failed. Let me have a look why...

Good that it is passing, let me make the history nicer before merging.

@jpkrohling CI passing, history prettyfied, could you please make a final review and eventually merge?

Looks good to me, I had only a couple of minor questions, but it looks very good overall.

LGTM. Should I squash and merge, or just create a merge commit?

LGTM. Should I squash and merge, or just create a merge commit?

I prefer a merge commit.


Added Sequence.take and Sequence.skip

These lazy iterator producing methods are useful when working with arbitrary sequences and you need to skip or take some number of elements at the start.

Love it!
I made one change: I turned skipping or taking a negative count into a runtime error. My hunch is that is more often than not a user error, so I figured it was better to bring that to their attention. In particular, I don't want them to think that calling take() with a negative index takes from the end, which is doesn't.

I made one change: I turned skipping or taking a negative count into a runtime error. My hunch is that is more often than not a user error, so I figured it was better to bring that to their attention. In particular, I don't want them to think that calling take() with a negative index takes from the end, which is doesn't.

Sounds like a good call, though it could also lead to otherwise unnecessary conditions in the code. Do you know what other frameworks do in this case?
Though it's been a while, my reasoning was probably that these skip and take methods replace the same functionality implemented with a for loop, which also silently does what you'd expect with negative numbers.

Though it's been a while, my reasoning was probably that these skip and take methods replace the same functionality implemented with a for loop, which also silently does what you'd expect with negative numbers.

That's a fair point. I looked a couple of other languages to see what they do:

Dart requires a non-negative count.
Ruby throws if the count is negative.
C# allows it.
Java throws.

So I think it's OK for Wren to make it an error. We could always loosen it later if it ends up being annoying for people.

Alright, thanks for looking up the other languages!


gnome-themes-standard: 3.22.3 -> 3.27.90

Semi-automatic update generated by https://github.com/ryantm/nix-update tools. These checks were done:

built on NixOS
Warning: no binary found that responded to help or version flags. (This warning appears even if the package isn't expected to have binaries.)
found 3.27.90 with grep in /nix/store/bawbjvlldazy2xmvhkq478709ygg04by-gnome-themes-standard-3.27.90

cc @lethalman @jtojnar for review

This package was renamed to gnome-themes-extra and will be merged as part of https://github.com/NixOS/nixpkgs/pull/36893

No attempt on x86_64-darwin
The following builds were skipped because they don't evaluate on x86_64-darwin: gnome-themes-standard
No log is available.

Success on x86_64-linux (full log)
Attempted: gnome-themes-standard
Partial log (click to expand)
glibPreFixupPhase
hicolorPreFixupPhase
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/bawbjvlldazy2xmvhkq478709ygg04by-gnome-themes-standard-3.27.90
shrinking /nix/store/bawbjvlldazy2xmvhkq478709ygg04by-gnome-themes-standard-3.27.90/lib/gtk-2.0/2.10.0/engines/libadwaita.so
strip is /nix/store/b0zlxla7dmy1iwc3g459rjznx59797xy-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/bawbjvlldazy2xmvhkq478709ygg04by-gnome-themes-standard-3.27.90/lib
patching script interpreter paths in /nix/store/bawbjvlldazy2xmvhkq478709ygg04by-gnome-themes-standard-3.27.90
checking for references to /tmp/nix-build-gnome-themes-standard-3.27.90.drv-0 in /nix/store/bawbjvlldazy2xmvhkq478709ygg04by-gnome-themes-standard-3.27.90...
/nix/store/bawbjvlldazy2xmvhkq478709ygg04by-gnome-themes-standard-3.27.90

Success on aarch64-linux (full log)
Attempted: gnome-themes-standard
Partial log (click to expand)
glibPreFixupPhase
hicolorPreFixupPhase
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/pzd9c992hca0kpkyav0m59vx2x7p27ns-gnome-themes-standard-3.27.90
shrinking /nix/store/pzd9c992hca0kpkyav0m59vx2x7p27ns-gnome-themes-standard-3.27.90/lib/gtk-2.0/2.10.0/engines/libadwaita.so
strip is /nix/store/lvx1acn1ig1j2km8jds5x3ggh3f2wa8v-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/pzd9c992hca0kpkyav0m59vx2x7p27ns-gnome-themes-standard-3.27.90/lib
patching script interpreter paths in /nix/store/pzd9c992hca0kpkyav0m59vx2x7p27ns-gnome-themes-standard-3.27.90
checking for references to /build in /nix/store/pzd9c992hca0kpkyav0m59vx2x7p27ns-gnome-themes-standard-3.27.90...
/nix/store/pzd9c992hca0kpkyav0m59vx2x7p27ns-gnome-themes-standard-3.27.90