Open Model Thread Group, not able to exit http client and taking much more time than expected to exit.

Expected behavior
I am getting this error at the last requests of open model thread group,
java.lang.InterruptedException
at java.base/java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1048)
at java.base/java.util.concurrent.CountDownLatch.await(CountDownLatch.java:230)
at org.eclipse.jetty.client.util.FutureResponseListener.get(FutureResponseListener.java:95)
at com.blazemeter.jmeter.http2.core.HTTP2JettyClient.send(HTTP2JettyClient.java:238)
at com.blazemeter.jmeter.http2.core.HTTP2JettyClient.sample(HTTP2JettyClient.java:210)
at com.blazemeter.jmeter.http2.sampler.HTTP2Sampler.sample(HTTP2Sampler.java:60)
at org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSamplerBase.java:1301)
at org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSamplerBase.java:1290)
at org.apache.jmeter.threads.JMeterThread.doSampling(JMeterThread.java:651)
at org.apache.jmeter.threads.JMeterThread.executeSamplePackage(JMeterThread.java:570)
at org.apache.jmeter.threads.JMeterThread.processSampler(JMeterThread.java:501)
at org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:268)
at org.apache.jmeter.threads.openmodel.OpenModelThreadGroup$ThreadsStarter.run$lambda-0(OpenModelThreadGroup.kt:128)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:577)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
at java.base/java.lang.Thread.run(Thread.java:1589)
Open Model thread group isn't running for the said time. I ran the traffic by defining random_intervals(15 min) and it took it around 2 hours to complete.
summary = 901886 in 02:00:10 =  125.1/s Avg:  7539 Min:     0 Max: 34826 Err: 277839 (30.81%)
summary +   2098 in 00:00:27 =   77.4/s Avg:   659 Min:    17 Max: 19453 Err:    72 (3.43%) Active: 1 Started: 904076 Finished: 904075
summary = 903984 in 02:00:37 =  124.9/s Avg:  7523 Min:     0 Max: 34826 Err: 277911 (30.74%)
summary +     24 in 00:00:03 =    9.1/s Avg:    22 Min:    18 Max:    58 Err:     0 (0.00%) Active: 0 Started: 904100 Finished: 904100
summary = 904008 in 02:00:40 =  124.9/s Avg:  7523 Min:     0 Max: 34826 Err: 277911 (30.74%)
Tidying up ...    @ 2023 Apr 21 14:40:32 UTC<PHONE_NUMBER>649)
... end of run
Also, at the end of open model thread group many HTTP client threads are on sleep mode and do not exit itself, i have to kill them manually.
1145201 jenkins   20   0   38.8g   1.5g  24080 S   0.0   1.5   0:00.00 HttpClient-3674
1145205 jenkins   20   0   38.8g   1.5g  24080 S   0.0   1.5   0:00.00 HttpClient-3674
1147190 jenkins   20   0   38.8g   1.5g  24080 S   0.0   1.5   0:00.00 HttpClient-3672
1148992 jenkins   20   0   38.8g   1.5g  24080 S   0.0   1.5   0:00.00 HttpClient-3677
Actual behavior
No response
Steps to reproduce the problem
The problem is while the open model thread group gets to the end.
JMeter Version
5.5
Java Version
No response
OS Version
Oracle Linux

Could you provide a reproducer?

I think the issue is that com.blazemeter.jmeter.http2.core.HTTP2JettyClient fails to handle the interrupt properly. It should cancel the ongoing request, however it fails to do so.
I suggest raising a ticket to the plugin maintainers


Add initial configuration for Dependabot

Description
This PR resolves #42 by providing the initial configuration for Dependabot to update npm packages and create a PR. I have:

Set the reviewing team to be the current members of Seneca-CDOT/osd700-dps911-winter-2023
Capped open PRs by Dependabot to 5
Disabled auto rebasing
Scheduld checks/PRs to held weekly on Saturday, Toronto time

I tried to closely configure Dependabot based on how Telescope has renovatebot set up.

Looks good to me. Can you do follow-ups to add checks for github actions and docker images too?

Sure.

@humphd, The follow-ups you mentioned seem to be assigned to @Ririio in the 0.1 Planning Document.

@SerpentBytes do you want to merge this?


samples: mesh: nrf52: Removed bug in reassignment of transition type

This PR will solve bug in reassignment of transition type to
Server.
Signed-off-by: Vikrant More<EMAIL_ADDRESS>

@jhedberg Sorry I was working on this commit & that is why not able to add it in last PR.
It is to solve the bug in the implementation.

Codecov Report

Merging #11397 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #11397   +/-   ##
=======================================
  Coverage   48.37%   48.37%
=======================================
  Files         265      265
  Lines       42188    42188
  Branches    10137    10137
=======================================
  Hits        20408    20408
  Misses      17703    17703
  Partials     4077     4077

Continue to review full report at Codecov.

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


cast etherscan-source seems to not work

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

[X] Foundry
[X] Foundryup

What version of Foundry are you on?
No response
What command(s) is the bug in?
cast 0.0.2 (fb6d0c5 2024-08-08T00:23:13.876828000Z)
Operating System
macOS (Apple Silicon)
Describe the bug
When downloading source contracts from etherscan using cast, getting a Failed to deserialize content error.
To reproduce, run this command: RUST_LOG=trace cast etherscan-source --chain-id 324 -d downloads/POOL_ADDRESSES_PROVIDER 0xE8bC6e12faf260dbA1c942134070221B11BF37Fb

Getting the trace error message:

2024-08-08T12:36:49.650595Z TRACE foundry_config: load config with provider: Metadata { name: "Default", source: None, provide_location: None, interpolater:  }
2024-08-08T12:36:49.896194Z TRACE etherscan: GET https://zksync2-mainnet-explorer.zksync.io/
2024-08-08T12:36:49.897997Z TRACE hyper_util::client::legacy::pool: checkout waiting for idle connection: ("https", zksync2-mainnet-explorer.zksync.io)
2024-08-08T12:36:49.898210Z DEBUG reqwest::connect: starting new connection: https://zksync2-mainnet-explorer.zksync.io/
2024-08-08T12:36:49.898712Z TRACE hyper_util::client::legacy::connect::http: Http::connect; scheme=Some("https"), host=Some("zksync2-mainnet-explorer.zksync.io"), port=None
2024-08-08T12:36:49.899033Z DEBUG hyper_util::client::legacy::connect::dns: resolving host="zksync2-mainnet-explorer.zksync.io"

2024-08-08T12:36:50.161061Z DEBUG hyper_util::client::legacy::connect::http: connecting to <IP_ADDRESS>:443
2024-08-08T12:36:50.162003Z TRACE mio::poll: registering event source with poller: token=Token(4348109952), interests=READABLE | WRITABLE
2024-08-08T12:36:50.414206Z DEBUG hyper_util::client::legacy::connect::http: connected to <IP_ADDRESS>:443
2024-08-08T12:36:51.077874Z TRACE hyper_util::client::legacy::client: http1 handshake complete, spawning background dispatcher task
2024-08-08T12:36:51.078555Z TRACE hyper_util::client::legacy::pool: checkout dropped for ("https", zksync2-mainnet-explorer.zksync.io)
2024-08-08T12:36:51.483496Z TRACE hyper_util::client::legacy::pool: put; add idle connection for ("https", zksync2-mainnet-explorer.zksync.io)
2024-08-08T12:36:51.483586Z DEBUG hyper_util::client::legacy::pool: pooling idle connection for ("https", zksync2-mainnet-explorer.zksync.io)
2024-08-08T12:36:51.485085Z ERROR etherscan: Failed to deserialize response: EOF while parsing a value at line 1 column 0 res=""
2024-08-08T12:36:51.486246Z TRACE mio::poll: deregistering event source from poller
Error:
Failed to deserialize content: EOF while parsing a value at line 1 column 0

My guess is it is breaking due to incorrect api url.

It indeed seems that the URLs present on alloy-chains are not the ones we expect.
Unfortuantely, it seems there's no way to specify which URL to use manually, so there's no easy workaround for it yet.

shouldn't it be possible to just replace the default explorer to https://era.zksync.network/ as i think should be api compatible

@Karrq alloy-chains is now pointing to the correct api. #78

@brotherlymite Since this functionality has just been merged, we'd need to wait for the new release from the maintainers. Once it's done we can patch it in our repository.
@sakulstra Since cast relies on chain-id to infer urls, this would be inconsistent with the url provided in the config. In any case, this involves adding a feature that's not present on upstream foundry, and could take a while. Similar to https://github.com/foundry-rs/foundry/issues/4776


docs(glossary): no RouteConfig

Decorator @RouteConfig -> @Routes

Thanks. I'm going to decline for now because this just scratches the surface. Everything here describes the Beta Deprecated router.  We're staying with that until we're ready to talk about the Release Router which will be substantially different/improved.


ERROR when running testing

Here is the information:
Traceback (most recent call last):
File "/opt/conda/lib/python3.8/runpy.py", line 185, in _run_module_as_main
mod_name, mod_spec, code = _get_module_details(mod_name, _Error)
File "/opt/conda/lib/python3.8/runpy.py", line 111, in _get_module_details
import(pkg_name)
File "COSA/env/lib/python3.8/site-packages/torch/init.py", line 527, in
class DoubleStorage(_C.DoubleStorageBase, _StorageBase):
AttributeError: module 'torch._C' has no attribute 'DoubleStorageBase'
I also tried different version of torch, got other errors

Now the problem was solved by udpated it to 1.13, but I got another error as:
Traceback (most recent call last):
File "./train.py", line 87, in
main(args, input_args)
File "./train.py", line 58, in main
model = COSA.from_pretrained(opts,checkpoint)
File "/work//COSA/model/modeling.py", line 99, in from_pretrained
model = cls(opts, *inputs, **kwargs)
File "/work//COSA/model/pretrain.py", line 83, in init
super().init(opts)
File "/work//COSA/model/modeling.py", line 181, in init
self.load_swin_model(config)
File "/work//COSA/model/modeling.py", line 316, in load_swin_model
swin_config = get_config('./pretrained_weights/SWIN/swin_base_patch4_window7_224_22k.yaml')
File "/work//COSA/model/swin_config.py", line 350, in get_config
update_config(config,config_file)
File "/work//COSA/model/swin_config.py", line 280, in update_config
_update_config_from_file(config, config_file)
File "/work//COSA/model/swin_config.py", line 266, in _update_config_from_file
with open(cfg_file, 'r') as f:
FileNotFoundError: [Errno 2] No such file or directory: './pretrained_weights/SWIN/swin_base_patch4_window7_224_22k.yaml'
The file is not in the pretrained_weights that I downloaded from the link

How did you solve that problems? Could you please offer some code or command?

Now the problem was solved by udpated it to 1.13, but I got another error as:
Traceback (most recent call last): File "./train.py", line 87, in main(args, input_args) File "./train.py", line 58, in main model = COSA.from_pretrained(opts,checkpoint) File "/work//COSA/model/modeling.py", line 99, in from_pretrained model = cls(opts, *inputs, **kwargs) File "/work//COSA/model/pretrain.py", line 83, in init super().init(opts) File "/work//COSA/model/modeling.py", line 181, in init self.load_swin_model(config) File "/work//COSA/model/modeling.py", line 316, in load_swin_model swin_config = get_config('./pretrained_weights/SWIN/swin_base_patch4_window7_224_22k.yaml') File "/work//COSA/model/swin_config.py", line 350, in get_config update_config(config,config_file) File "/work//COSA/model/swin_config.py", line 280, in update_config _update_config_from_file(config, config_file) File "/work//COSA/model/swin_config.py", line 266, in _update_config_from_file with open(cfg_file, 'r') as f: FileNotFoundError: [Errno 2] No such file or directory: './pretrained_weights/SWIN/swin_base_patch4_window7_224_22k.yaml'
The file is not in the pretrained_weights that I downloaded from the link

Sorry for the incomplete files. A full pretrained_weights file have been updated now.


Update to CenturyLink Marketplace Provider Program Guide

Closing as these changes are incorporated into https://github.com/CenturyLinkCloud/PublicKB/pull/2007


Stack View

A stackview that shows which numbers are pushed to the stack and where the different numbers are located on the stack. It should also show where the LV and SP registers are pointing to.


JSX Conditional Rendering

Hello,
I'm wondering how to render things conditionally using the JSX syntax. I found this comment which suggested that the normal react syntax (bool && <Tag />) should work: https://github.com/snabbdom/snabbdom/blob/255c87d1a99e38e7ec973267ff993994562b85c9/src/jsx.ts#L13
When I try this though, the boolean itself is getting rendered. For example:
const Component = () => {
  return

    {false &&
Hello World!
}

;
};

renders 'false'.
I've also tried this:
const Component = () => {
  return

    {false ?
Hello World!
 : null}

;
};

but that renders the string 'null'.
Here's a codepen reproduction: https://codepen.io/bhaines-yext/pen/LYjORYm. Am I doing something incorrectly?
Edit: I've messed around a little more and there are some interactions that I don't understand going on. For example here: https://codepen.io/bhaines-yext/pen/WNEXGor?editors=0010 currently nothing is rendered. But removing the <Component3 /> call from the Parent component causes false null to be rendered.

The workaround I've found that seems to work most consistently is using an empty array like:
const Component = () => {
  return

    {false ?
Hello World!
 : []}

;
};

Try using the jsx pragma provided by snabbdom instead of the snabbdom-jsx package.
/** @jsx snabbdom.jsx */
import * as snabbdom from<EMAIL_ADDRESS>
Here is a codepen reproduction. Hope this solves your problem.

Thank you that's what I was missing!


Add /edit layer - Error is missing if multiple layer IDs are an empty string

Currently it is possible to add a Layer without ID which is required and must be unique.

It turns out that the version of @mapbox/mapbox-gl-style-spec we're using, doesn't throw an error.
Todo

Check latest version
If still an issue, raise ticket/PR in the @mapbox/mapbox-gl-style-spec repo

Ok so the new version of the spec doesn't throw a validation error either. We probably shouldn't go adding in additional checks to the style spec. Maybe we should just disable the 'Add Layer' button if the id attribute is empty.

I did some testing with gl-style-validate and I was wrong with "currently it is possible to add a Layer without ID".
When adding a layer with an empty ID attribute the ID is an empty string:  "id": "" and not missing.
The spec only throws an error if the whole "id" property is missing (error: missing required property "id").
However, there is still an issue here, because it is possible to add multiples layers with  "id": "". It is also possible to edit/delete layer IDs so that there are multiple layers with  "id": "".
In this case the spec throws an error with gl-style-validate (error: duplicate layer id "") but with Maputnik this error is somehow missing.

This was fixed by @orangemug in https://github.com/maputnik/editor/pull/625.


Not able to change the cluster

Currently we are using a Mongodb 3.6 version cluster and to Elasticsearch syncing we are using mongo-connector. I want to upgrade it to 4.0. So we are following the below steps -

Taken a snapshot of 3.6 cluster
Created a new cluster with 4.0 version and restore the 3.6 sanpsot in it successfully.
Updated the new 4.0 replicaset name into existing oplog.ts file (with existing value)

Now my syncing has been stopped. Can someone provide any help on it so that i can start syncing again?
Note: Since we have the same data into new 4.0 cluster so i don't want the syncing since starting. Syning should work when i insert a new record into new cluser 4.0
Thanks in advance. As it's very urgent for me.

Hi @jaraco, @AayushU and @ShaneHarvey,
Since you guys are the most active contributor of mongo-connector.
Actually, I need to change the MongoDB cluster in our application. So I created a new cluster with the updated version and dump all the data into it from old cluster. But after doing this my mongo-connector syncing stopped and if i remove my oplog.ts file it starts the syncing beginging.
Current in our DB we have around 2 CRs data collection so sync them into Elastic Search via mongo-connector since starting it will take time.
So do you guys any suggestion and idea so that we can point out the new cluter and start the syncing where our old cluster left?  I have no issue to pay you guys for this efforts. Pleaes let us know so that we can proceed accordinngly.
It's very urgent so please have a look and do the needful.

Hi @singhmahendrapal, apologies for the situation. It does sound frustrating. Unfortunately, I do not work on mongo-connector anymore. Taking a look through the open issues shows that mongo-connector only has limited support for MongoDB 3.6 (https://github.com/yougov/mongo-connector/issues/767) and does not support MongoDB 4.0 (https://github.com/yougov/mongo-connector/issues/865). It seems like you would need to wait for those projects to be completed before using mongo-connector with MongoDB 4.0.
Note that if you're using MongoDB Atlas than you might be interested in using Atlas Search which provides full text search natively in the MongoDB cluster itself. With Atlas Search there's no need to manually sync data to other systems.

Hello Singh. I unfortunately have little to add. I also have moved to a new role where I spend little time with MongoDB and mongo-connector. I wish I could have help, but I have neither context nor bandwidth to offer. I wish you luck. Feel free to ping me on PRs that would aid in supporting your needs. I'm happy to merge and release contributions.


Registering a reminder with the same name as an existing one should overwrite the first

In what area(s)?
/area runtime
What version of Dapr?

0.3
Expected Behavior

Registering reminders with the same name from the same actor should result in the 2nd registration overwriting the first.
Actual Behavior
Subsequent reminder registrations using the same name (but different state/duetime/period) result in additional registered reminders.
Steps to Reproduce the Problem
Call register reminder 3 times, eg
    super.registerReminder(
        name,
        "40",
        Duration.ofSeconds(1),
        Duration.ofSeconds(2)).block();

      System.out.println("registering again");
      super.registerReminder(
        name,
        "42",
        Duration.ofSeconds(1),
        Duration.ofSeconds(2)).block();

      System.out.println("registering again again");
      super.registerReminder(
        name,
        "41",
        Duration.ofSeconds(2),
        Duration.ofSeconds(2)).block();

All 3 reminders will fire.
When unregister is called using name, only 1 is removed - the other 2 keep firing.

Possibly slightly related, when a reminder is registered after being unregistered there appears to be state from the previous reminder reused. The reminder does not fire at dueTime instead it fires on the period.

I was able to repro this issue by using a modified version of the dotnet sdk sample. I modified the ActorClient code to register the reminder 3 times in quick succession. I changed the DemoActor::RegisterReminder() implementation to modify the due to a random number between 1-10 (to ensure the reminder data changes in every registration).
By adding logs in the code, I found two issues:-
Issue#1: The existing logic, inside CreateReminder code, when sees the same reminder is re-registered but needs update, calls DeleteReminder on the old one and then continues as if a new reminder is added. The DeleteReminder code cancels the old reminder values by calling a.activeReminders.Load(reminderKey) and then calling delete. However, the activeReminders is updated by the CreateReminder in a go routine inside startReminder func. Since the reminders were called in quick succession, the sequence was this:-

Reminder with values A created
Go routine inside startReminder that adds reminder with values A scheduled (not executed)
Reminder with values B create request comes in
Try to delete reminder by calling a.activeReminders.Load(reminderKey) but entry not found
Go routine inside startReminder that adds reminder with values B scheduled (not executed)
and so on

Issue#2: Every time a reminder is registered with new values, a.activeReminders is updated with a new stop channel. However, the DeleteReminder that is called to cancel the old reminder, calls close on the old value of stop channel. Since the reminders were registered in quick succession, after fixing Issue#1, the order of events was:-

Reminder with values A created with stopChannelA
Go routine inside startReminder that adds reminder with values A scheduled (not executed)
Reminder with values B create request comes in
DeleteReminder deleted a.activeReminders(reminderKey) and closed stopChannelA
CreateReminder logic proceeded and updated a.activeReminders with stopChannel B
Go routine inside startReminder that adds reminder with values B scheduled (not executed)
Go routine for reminder with values A started execution. It gets the stop channel by looking up a.activeReminders which is now stopChannelB. This channel is not closed and therefore, reminder gets fired
Go routine for reminder with values B started execution. It gets the stop channel by looking up a.activeReminders which is now stopChannelB. This channel is not closed and therefore, reminder gets fired


Add hovered_anyway() to Response to deal with child widgets events when hovered

Add hovered_anyway() to Response, this can help to deal with child widgets events when current widget is hovered
usage

I think something like this is a better solution: https://github.com/emilk/egui/issues/1010


1.0 DOCS added gsoc page

Signed-off-by: krishna katyal<EMAIL_ADDRESS>

/approve
/lgtm


Rewrite of module "FileFilter" engine

Currently, the module "FileFilter" engine is really arbitrary, restrictive and basically meets the really basic needs of what people want. That doesn't really fit with the way that I think DSJAS should be in terms of extensibility.
I propose a regex-based system, where DSJAS will parse and attempt to match user-supplied regex to the current directory and file name. This will allow for better selection of specific paths and even to select for multiple different possibilities.
Progress

[ ] Rewrite FileFilter engine code in main module engine
[ ] Rewrite existing modules to select for their targets better
[ ] Rewrite documentation to document the new regex system
[ ] Regression testing

Turns out this was a much quicker job than expected. Ready to merge into mainline once the docs are done

All done. Ready to merge once the release is finalized.


Projector Manifold requires extra information

This might be me not understanding the Renderman environment, but I have found the following:
When Assigning the PxrProjector  I have found that unless you put something in the Coord field (a space will do), PRman will not render out the image. PRMan itself reports and error messages stating that a coordination system must be named.  This does not match the renderman documentation which states that "" will do.
So I am not sure that this is a bug in PRMan-for-Blender, PRMan or the PRMan documentation.  (Or me)

Sounds like a documentation bug.  You definitely need something there.

Documentation stats the following.
Coordinate System
Name of coordinate system transform (e.g. place3dTexture node in Maya).
RIB: string coordsys
Default: ""
Which does seem to indicate that it could be blank.   Happy to accept it as a documentation error and that something needs to be put in the slot. (And I will go and learn what a coordinate system transform is, and try and work out how it might link in with blender ;-))

Cool.  I'll log that doc bug back at work on monday.  The default coordinate systems are "shader, object, camera, world,.." Normally if you export a coordinate space (there's a button to do this that might not work at the moment but is an easy fix).  You could say export the coordinate space of an object "Cube" and use that coordinate space in other objects.


[HPRO-669] Add "Return to Participant" button for finalized Biospecimen orders

@jt2k I was thinking the same. Actually, I added the button at the bottom of the form then saw the ticket description and changed it to top. Good to review this with Caroline.

Closing this PR as we decided not to implement this.


Make the pull request helper tests pass

Currently the pull request helper tests don't pass, but nobody notices because the filename doesn't end in _spec, so they're not actually run.
This patch fixes the test (should count 3 PRs, not just 1), renames it so it runs, and makes sure it covers the 'only this year' case.

🎄


Add LEDC ledc_calculate_divisor() function to the /driver/ledc.h. (IDFGH-14070)

The ledc_timer_set() function requests uint32_t clock_divider parameter.
https://github.com/espressif/esp-idf/blob/7a305c0284b7af7cd8b8f12b48f72e2685d9a363/components/esp_driver_ledc/include/driver/ledc.h#L365
clock_divider is not a trivial.
It can be calculated with the ledc_calculate_divisor() function.
https://github.com/espressif/esp-idf/blob/7a305c0284b7af7cd8b8f12b48f72e2685d9a363/components/esp_driver_ledc/src/ledc.c#L451
This function is not accessible in the LEDC API driver.
Please add ledc_calculate_divisor() function to the esp-idf/components/esp_driver_ledc/include/driver/ledc.h
uint32_t ledc_calculate_divisor(uint32_t src_clk_freq, int freq_hz, uint32_t precision);

AFAIK, some of the ledc driver API is redundant, why not use ledc_timer_config to setup the ledc timer? You only need to provide the source clock and the target timer resolution, the driver can help calculate the divisor.

some of the ledc driver API is redundant

Ok. Then please mark ledc_timer_set() as obsolete.


Nuxt-Icon keeps adding classes to non-icon svgs imported

Hi, i'm using nuxt-svgo to import svgs as components, and i also have nuxt-icon for icons. The issue here is that if i use nuxt-svgo to import an svg as a component, nuxt-icon adds .nuxt-icon and .nuxt-icon--fill classes, and overwrites my svg colors

Could you please open a reproduction / sandbox?

same issue here.

Same issue.

Thank you, took me long time to figure it out that why my svg element was getting automatically following element added:
.nuxt-icon--fill, .nuxt-icon--fill * {
    fill: currentColor;
}

And my component looks this atm:
<UndrawSecureLogin
   class="w-64 h-64 sm:w-80 sm:h-80 md:w-96 md:h-96 lg:w-128 lg:h-128"
  :fontControlled="false"
  :filled="false"
/>

So if either :filled="false" is mentioned or its removed, then svg is going to be automatically filled with parents text color.
Everything is working as expected if I change value to true.
My package.json looks following:
{
  "name": "nuxt-app",
  "private": true,
  "type": "module",
  "scripts": {
    "build": "nuxt build",
    "dev": "nuxt dev",
    "start:preview": "nuxt start",
    "start:prod": "node .output/server/index.mjs",
    "generate": "nuxt generate",
    "preview": "nuxt preview",
    "postinstall": "nuxt prepare"
  },
  "dependencies": {
    "@supabase/supabase-js": "^2.46.1",
    "h3": "^1.13.0",
    "nuxt": "^3.13.2",
    "nuxt-svgo": "^4.0.8",
    "vue": "latest",
    "vue-router": "latest"
  },
  "devDependencies": {
    "autoprefixer": "^10.4.20",
    "postcss": "^8.4.49",
    "tailwindcss": "^3.4.14"
  }
}

And for context using Node.js version v22.9.0


[Android] Better error handling if react context initialization fails

Description
When I create ReactInstanceManager I am able to pass in a native exception handler. However, in case ReactContextInitAsyncTask  fails, this exception handler is completely skipped and the error is passed into dev support manager, which will crash the app in release. https://github.com/facebook/react-native/blob/master/ReactAndroid/src/main/java/com/facebook/react/ReactInstanceManager.java#L232
Reproduction
No reproduction, just concern looking at your code
Solution
Why not copy the code here https://github.com/facebook/react-native/blob/master/ReactAndroid/src/main/java/com/facebook/react/ReactInstanceManager.java#L911-L913 as the exception handler passed into catalyst instance manager and reuse it for rest of the error handling?
NativeModuleCallExceptionHandler exceptionHandler = mNativeModuleCallExceptionHandler != null
        ? mNativeModuleCallExceptionHandler
        : mDevSupportManager;

Or why does DisabledDevSupportManager at https://github.com/facebook/react-native/blob/master/ReactAndroid/src/main/java/com/facebook/react/devsupport/DisabledDevSupportManager.java#L34 not use my custom exception handler (which will not crash the app) but forcefully create default exception handler?
Additional Information

React Native version: Latest (0.42)
Platform: Android
Operating System: Any
Dev tools: Android

We're cutting down on the number of outstanding issues, in order to allow us to focus. I'm closing this issue because it has been open for over 60 days with no activity. If you think it should still be opened let us know why. PRs are always welcome.


Invalid comment in LSP-pylsp.sublime-settings

See https://github.com/sublimelsp/LSP-pylsp/blob/81fabfe5761e92bdcc202cd1f72dec2d9dd4d8b6/LSP-pylsp.sublime-settings#L62
flake8 is invalid according to
https://github.com/sublimelsp/LSP-pylsp/blob/master/sublime-package.json#L35-L38
Should it be pyflakes instead? Flake8 is a wrapper around pyflakes (and more).

The default configuration source is pycodestyle. Change the pylsp.configurationSources setting to ['flake8'] in order to respect flake8 configuration instead.

that sentence is from this README https://github.com/python-lsp/python-lsp-server#configuration
I did a quick check of the python-lsp-server repo and found this
python-lsp-server\pylsp\config\config.py

DEFAULT_CONFIG_SOURCES = ['pycodestyle']
sources = self._settings.get('configurationSources', DEFAULT_CONFIG_SOURCES)

---
python-lsp-server\test\plugins\test_flake8_lint.py
 workspace.update_config({"pylsp": {"configurationSources": ["flake8"]}})

So I would say that the acceptable values are: pycodestyle and flake8

That makes more sense. So https://github.com/sublimelsp/LSP-pylsp/blob/master/sublime-package.json#L37 should be corrected.

Yes, feel free to open a PR :)

PR was merged.


XMonad.actions.search: Add NixOS and home-manager searchEngines

feat(search): add nixos as searchEngine
feat(search): add homeManager as searchEngine

Description
(I've only skimmed contributing and docs, and haven't tested this, which I will ofc do before changing from draft)
Include a description for your changes, including the motivation
behind them.
Checklist

[ ] I've read CONTRIBUTING.md

[ ] I've considered how to best test these changes (property, unit,
manually, ...) and concluded: XXX

[ ] I updated the CHANGES.md file

The only thing I'd note is we keep the list of search engines in sorted order so it's easier to check if one you want is present.


Add endpoint for dashboard to collect logs (pprof) as zip file

We could also read the journal and display the logs in the dashboard.
example: https://github.com/coreos/go-systemd/blob/b14d3eb023cc860c82b1bb143bb98122d3c40224/sdjournal/journal_test.go


Clarity Grid Misalignment Issues

Please find attached below,  chat transcript between keshav and Eudes Petonnet-Vincent
Whenever we use *clrDgItems to create rows for datagrid records, we see a misalignment. If we use *ngFor, clarity does not seem to get full control w.r.t pagination.
Please advise a solution (or) ETA for fixing this issue.

@tnravik could you edit this issue or close and re-file using the template provided by default including the version used, reproduction behavior, etc? It's tough for others on the team to pick this up by simply looking at the conversation or the description provided.

@keshav, please do the needful as per the above comment.
Thanks,
Ravi

@tnravik: Grid alignment issues have already been fixed in Clarity 0.9.1 (3 weeks ago): https://github.com/vmware/clarity/commit/505a3ad4438c3e5fb2d7a5ded917ee49bcab8071


ACR Task - Unable to bypass firewall via Trusted service

Summary
The following doc states you can bypass ACR public network access when its set to either "Selected networks" or "Disabled". I followed the steps described (explained below)

Create the ACR with public network access set to "Disabled" and "Allow trusted Microsoft services to access this container registry" checked.
Used Azure CLI to create an ACR task with a system assigned identity az acr task create --registry myRegistry --name acr-task-build --image devops-aci-agent:latest --file acrtask.yaml --context /dev/null --auth-mode None --assign-identity [system]
Obtained the ACR task identity via az acr task identity show --name acr-task-build --registry myRegistry and granted ACRPush RBAC permissions via bicep.
Ran az acr task run -n acr-task-build -r myRegistry -c . -f .\Dockerfile to build and push to my registry.
Private link is disabled at this point in time.

ACRTask.yaml
version: v1.1.0
steps:
  - build: -t $Registry/devops-aci-agent:latest -f Dockerfiletest .
  - push:
    - $Registry/devops-aci-agent:latest

Error
Packing source code into tar to upload...
Excluding '.git' based on default ignore rules
Excluding '.gitignore' based on default ignore rules
Uploading archived source code from 'C:\Users\eroshoko\AppData\Local\Temp\cli_source_archive_396cf06127aa41c6b85d9e73d0b858bc.tar.gz'...
Sending context (101.430 KiB) to registry: myRegistry...
Queued a run with ID: chb
Waiting for an agent...
2022/08/01 18:32:39 Downloading source code...
2022/08/01 18:32:40 Finished downloading source code
2022/08/01 18:32:41 Alias support enabled for version >= 1.1.0, please see https://aka.ms/acr/tasks/task-aliases for more information.
2022/08/01 18:32:41 Creating Docker network: acb_default_network, driver: 'bridge'
2022/08/01 18:32:41 Successfully set up Docker network: acb_default_network
2022/08/01 18:32:41 Setting up Docker configuration...
2022/08/01 18:32:41 Successfully set up Docker configuration
2022/08/01 18:32:41 Executing step ID: acb_step_0. Timeout(sec): 600, Working directory: '', Network: 'acb_default_network'
2022/08/01 18:32:41 Scanning for dependencies...
2022/08/01 18:32:42 Successfully scanned dependencies
2022/08/01 18:32:42 Launching container with name: acb_step_0
Sending build context to Docker daemon  654.3kB
Step 1/5 : FROM ubuntu:20.04
20.04: Pulling from library/ubuntu
d7bfe07ed847: Pulling fs layer
d7bfe07ed847: Verifying Checksum
d7bfe07ed847: Download complete
d7bfe07ed847: Pull complete
Digest: sha256:fd92c36d3cb9b1d027c4d2a72c6bf0125da82425fc2ca37c414d4f010180dc19
Status: Downloaded newer image for ubuntu:20.04
 ---> 20fffa419e3a
Step 2/5 : WORKDIR /azp
 ---> Running in 6b7d2cd5e538
Removing intermediate container 6b7d2cd5e538
 ---> 33de6aefb449
Step 3/5 : COPY start.sh .
 ---> cad85c3d8696
Step 4/5 : RUN chmod +x start.sh
 ---> Running in ccc059ef8888
Removing intermediate container ccc059ef8888
 ---> aa8481eca16a
Step 5/5 : CMD ["./start.sh"]
 ---> Running in 1a8c4d82bd9f
Removing intermediate container 1a8c4d82bd9f
 ---> 3876ea4f357d
Successfully built 3876ea4f357d
Successfully tagged myRegistry.azurecr.io/devops-aci-agent:latest
2022/08/01 18:32:49 Successfully executed container: acb_step_0
2022/08/01 18:32:49 Executing step ID: acb_step_1. Timeout(sec): 600, Working directory: '', Network: 'acb_default_network'
2022/08/01 18:32:49 Pushing image: myRegistry.azurecr.io/devops-aci-agent:latest, attempt 1
The push refers to repository [myRegistry.azurecr.io/devops-aci-agent]
9b6c2e5b3da9: Preparing
45641fa42d9a: Preparing
394cca797501: Preparing
af7ed92504ae: Preparing
denied: client with IP '<IP_ADDRESS>' is not allowed access. Refer https://aka.ms/acr/firewall to grant access.
2022/08/01 18:32:50 Pushing image: myRegistry.azurecr.io/devops-aci-agent:latest, attempt 2
The push refers to repository [myRegistry.azurecr.io/devops-aci-agent]
9b6c2e5b3da9: Preparing
45641fa42d9a: Preparing
394cca797501: Preparing
af7ed92504ae: Preparing
denied: client with IP '<IP_ADDRESS>' is not allowed access. Refer https://aka.ms/acr/firewall to grant access.
2022/08/01 18:32:51 Pushing image: myRegistry.azurecr.io/devops-aci-agent:latest, attempt 3
The push refers to repository [myRegistry.azurecr.io/devops-aci-agent]
9b6c2e5b3da9: Preparing
45641fa42d9a: Preparing
394cca797501: Preparing
af7ed92504ae: Preparing
denied: client with IP '<IP_ADDRESS>' is not allowed access. Refer https://aka.ms/acr/firewall to grant access.
failed to run step ID: acb_step_1: failed to push images successfully
Run ID: chb failed after 14s. Error: failed during run, err: exit status 1
Run failed

My understanding is Firewall rules shouldn't be applicable since trusted service is enabled on the registry. I should be able to build and publish locally or via Azure DevOps via ACR Task.
Any guidance on this will be greatly appreciated.

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

ID: e9a7797a-6eb0-4321-c99a-2b0088d69407
Version Independent ID: 779bb545-f07f-661c-e2d9-7797d744e6f7
Content: Access network-restricted registry using trusted Azure service - Azure Container Registry
Content Source: articles/container-registry/allow-access-trusted-services.md
Service: container-registry
GitHub Login: @tejaswikolli-web
Microsoft Alias: tejaswikolli

Looks like I was missing a step to add the system assigned identity credentials to the ACR task documented https://docs.microsoft.com/en-us/azure/container-registry/container-registry-tasks-authentication-managed-identity#4-optional-add-credentials-to-the-task

Thanks for sharing the update.
If there are further questions regarding this matter, please tag me in a comment. I will reopen it and we will gladly continue the discussion.


STORM-3422: TupleCaptureBolt is not thread-safe

Fixes STORM-3422.
Note, this is a preview PR meant as a base for more discussion.
There are two commits, two different approaches to the same problem, please take a look. The latter, I believe, is simpler and easier to understand.
The synchronization is expected to be completely uncontended, we simply need a way to safely publish the changes made by one thread or the other. Either way, the usage of the class feels dirty, but there isn't much we can do now, is there?

I think I like the ListMultiMap approach a little better, since it's not as easy to forget to synchronize a reference to the map. I would also expect there to be some contention on the map field, as it will be updated by every tuple in the local topology.
You're right that using a static field for this is a bit hacky. Best alternative I can think of would be creating a field in LocalCluster, and figuring out a way to share it with these bolts. It would probably be more complicated though. Either way, I don't think this is too bad, as the TupleCaptureBolt isn't supposed to be used outside a LocalCluster, and we can make sure to e.g. clear the field between topology submissions.
If you can think of a good alternative, I don't think anyone would miss this bolt :)

I would also expect there to be some contention on the map field, as it will be updated by every tuple in the local topology.

D'oh! Of course. That was bad.
I updated the PR with another take - this time taking advantage of the happens-before guarantees provided by ConcurrentHashMap#compute(). This now allows parallelism among different bolts, and will correctly work even if two instances of the same bolt are executed at the same time. The change is simpler, and there's no need to synchronize on the list anymore. The cost is that the inner lambda is a capturing one and has therefore be instantiated with every iteration...
Do you guy have any benchmarks impacted by this? I could not find one. Or do we not really care in tests?
(and I rebased the branch)

Looks great, +1 assuming tests pass. I don't think performance in tests is terribly important.

Thanks! How do I manage backporting? Do you guys take care of those things, or should I cherrypick manually and open another PR once this one gets merged?

Normally we could cherrypick it for you, but this uses Java 8 features and 1.x targets Java 7. If you still want this backported, we need a new PR.

1.x targets Java 7

Aha. Nevermind then, it's a possible, but annoying fix and apparently not many people care as they'd discover this too.
Thanks for your help and rapid responses!


actions_intent_TRANSACTION_DECISION is never called using Order API v3

I am building a simple shopping cart app using actions-on-google. I can present the order, and the user can accept and authorise payment in the assistant. But the event "actions_intent_TRANSACTION_DECISION" is never fired which would trigger my intent that raises the transaction and updates the order
Built using Dialogflow and fulfillment through firebase cloud functions.
I have had this working using the sample here: https://github.com/actions-on-google/dialogflow-transactions-nodejs and worked through to the end. I am using Stripe it would retrieve a token and raise a transaction successfully
However the guides now reference version 3 of the Orders API https://developers.google.com/actions/transactions/physical/dev-guide-physical-gpay and given v2 is deprecated I figured I'd use v3.
The code will present the order to the user (note the snippet is basically copied from the example in the guide) and they can authorise payment and the token is created in Stripe. But for some reason the actions_intent_TRANSACTION_DECISION event is never triggered so I can't handle the user's decision in my follow up intent. The assistant just responds "Sorry, something went wrong. Please try again later"
All required information has been set here:
left sidebar -> DEPLOY -> Directory information -> (Details, Image, Contact Details, Privacy and consent, Additional Information)

There are no errors in firebase and the assistant completes the transaction decision for the order.

const now = new Date().toISOString();
const order = {
      createTime: now,
      lastUpdateTime: now,
      merchantOrderId: "UNIQUE_ORDER_ID",
      userVisibleOrderId: "USER_VISIBLE_ORDER_ID",
      transactionMerchant: {
        id: 'http://www.example.com',
        name: 'Example Merchant',
      },
      contents: {
        lineItems: [
          {
            id: 'LINE_ITEM_ID',
            name: 'Pizza',
            description: 'A four cheese pizza.',
            priceAttributes: [
              {
                type: 'REGULAR',
                name: 'Line Item Price',
                state: 'ACTUAL',
                amount: {
                  currencyCode: 'USD',
                  amountInMicros: 8990000,
                },
                taxIncluded: true,
              },
            ],
            notes: [
              'Extra cheese.',
            ],
            purchase: {
              quantity: 1,
              unitMeasure: {
                measure: 1,
                unit: 'POUND'
              },
              itemOptions: [
                {
                  id: 'ITEM_OPTION_ID',
                  name: 'Pepperoni',
                  prices: [
                    {
                      type: 'REGULAR',
                      state: 'ACTUAL',
                      name: 'Item Price',
                      amount: {
                        currencyCode: 'USD',
                        amountInMicros: 1000000,
                      },
                      taxIncluded: true,
                    },
                  ],
                  note: 'Extra pepperoni',
                  quantity: 1,
                  subOptions: [],
                },
              ],
            },
          },
        ],
      },
      buyerInfo: {
        email<EMAIL_ADDRESS>        firstName: 'Jane',
        lastName: 'Doe',
        displayName: 'Jane Doe',
      },
      priceAttributes: [
        {
          type: 'TOTAL',
          name: 'Total Price',
          state: 'ESTIMATE',
          amount: {
            currencyCode: 'USD',
            amountInMicros: 15770000,
          },
          taxIncluded: true,
        },
        {
          type: 'TAX',
          name: 'Tax',
          state: 'ESTIMATE',
          amount: {
            currencyCode: 'USD',
            amountInMicros: 3780000,
          },
          taxIncluded: true,
        },
        {
          type: 'SUBTOTAL',
          name: 'Subtotal',
          state: 'ESTIMATE',
          amount: {
            currencyCode: 'USD',
            amountInMicros: 9990000,
          },
          taxIncluded: true,
        },
        {
          type: 'DELIVERY',
          name: 'Delivery',
          state: 'ACTUAL',
          amount: {
            currencyCode: 'USD',
            amountInMicros: 2000000,
          },
          taxIncluded: true,
        },
      ],
      followUpActions: [
        {
          type: 'VIEW_DETAILS',
          title: 'View details',
          openUrlAction: {
            url: 'http://example.com',
          },
        },
        {
          type: 'CALL',
          title: 'Call us',
          openUrlAction: {
            url: 'tel:+16501112222',
          },
        },
        {
          type: 'EMAIL',
          title: 'Email us',
          openUrlAction: {
            url<EMAIL_ADDRESS>          },
        },
      ],
      termsOfServiceUrl: 'www.example.com',
      note: 'Sale event',
      promotions: [
        {
          coupon: 'COUPON_CODE',
        },
      ],
      purchase: {
        status: 'CREATED',
        userVisibleStatusLabel: 'CREATED',
        type: 'FOOD',
        returnsInfo: {
          isReturnable: false,
          daysToReturn: 1,
          policyUrl: 'http://www.example.com'
        },
        fulfillmentInfo: {
          id: 'FULFILLMENT_SERVICE_ID',
          fulfillmentType: 'DELIVERY',
          expectedFulfillmentTime: {
            timeIso8601: '2017-01-16T01:30:15.01Z',
          },
          location: {
            zipCode: '94086',
            city: 'Sunnyvale',
            postalAddress: {
              regionCode: 'US',
              postalCode: '94086',
              administrativeArea: 'CA',
              locality: 'Sunnyvale',
              addressLines: [
                '222, Some other Street',
              ],
            },
          },
          price: {
            type: 'REGULAR',
            name: 'Delivery Price',
            state: 'ACTUAL',
            amount: {
              currencyCode: 'USD',
              amountInMicros: 2000000,
            },
            taxIncluded: true,
          },
          fulfillmentContact: {
            email<EMAIL_ADDRESS>            firstName: 'John',
            lastName: 'Johnson',
            displayName: 'John Johnson',
          },
        },
        purchaseLocationType: 'ONLINE_PURCHASE',
      },
    };

  conv.ask(new TransactionDecision({
    orderOptions: {
      requestDeliveryAddress: false,
      userInfoOptions: {
        userInfoProperties: [
          'EMAIL',
        ],
      },
    },
    paymentParameters: {
      googlePaymentOption: {
        // facilitationSpec is expected to be a serialized JSON string
        facilitationSpec: JSON.stringify({
          apiVersion: 2,
          apiVersionMinor: 0,
          merchantInfo: {
            merchantName: 'Mahalia Coffee',
          },
          allowedPaymentMethods: [
            {
              type: 'CARD',
              parameters: {
                allowedAuthMethods: ['PAN_ONLY', 'CRYPTOGRAM_3DS'],
                allowedCardNetworks: [
                  'AMEX', 'DISCOVER', 'JCB', 'MASTERCARD', 'VISA'],
              },
              tokenizationSpecification: {
                type: 'PAYMENT_GATEWAY',
                parameters: {
                  "gateway": "stripe",
                  "stripe:version": "2019-08-14",
                  "stripe:publishableKey": "pk_test_MY_STRIPE_KEY"
                },
              },
            },
          ],
          transactionInfo: {
            totalPriceStatus: 'FINAL',
            totalPrice: (subtotal + delivery / 1000000).toString(),
            currencyCode: 'AUD',
          },
        }),
      },
    },
    presentationOptions: {
      actionDisplayName: 'PLACE_ORDER',
    },
    order: order,
  }));

So the issue is with v3, but not v2? Even though your order object is the same?

So the issue is with v3, but not v2? Even though your order object is the same?

@Fleker sorry that was unclear in my post. V2 worked but it was using the v2 order object which is different.
I pointed out that it worked in v2 to point out that the conversation flow and how the intent was being triggered was working when I was using v2. I changed to v3 and modified the order object accordingly and have been unable to get it to fire the actions_intent_TRANSACTION_DECISION  event.

So the issue is with v3, but not v2? Even though your order object is the same?

@Fleker sorry that was unclear in my post. V2 worked but it was using the v2 order object which is different.
I pointed out that it worked in v2 to point out that the conversation flow and how the intent was being triggered was working when I was using v2. I changed to v3 and modified the order object accordingly and have been unable to get it to fire the actions_intent_TRANSACTION_DECISION event.

Was there ever a solution identified?

Was there ever a solution identified?

@sburrell63  Not that I have found. I couldn't get it working so had to shelf the project. I will have to try again as the project still has to go ahead.


Logout Tweak after i dies with status effect

it will blackscreen. i can still close app and re open

Is this problem still happening? Logout Tweaks does not edit the Status Effect manager, so my initial thought is that this might be another mod. Status Effects from your last logout are applied when the character is loaded only. It's possible that an old status effect was added to your player that might be causing an issue. If you are playing with any other mod that adds/edits status effects can you please list them?


2024-10-02_01-35-16_master-next_aws-sdk-cpp

Automatically created.

Successfully created backport PR for kirkstone-next:

#9800

Backport failed for scarthgap-next, because it was unable to cherry-pick the commit(s).
Please cherry-pick the changes locally.
git fetch origin scarthgap-next
git worktree add -d .worktree/backport-9798-to-scarthgap-next origin/scarthgap-next
cd .worktree/backport-9798-to-scarthgap-next
git checkout -b backport-9798-to-scarthgap-next
ancref=$(git merge-base 693598b650270168edc77864cfe312830a3637a3 858158dec2a67ae176caf903e670fe8b4691c637)
git cherry-pick -x $ancref..858158dec2a67ae176caf903e670fe8b4691c637

Successfully created backport PR for styhead-next:

#9801


expose request start time

When implementing time based throttle mechanism, the start of request time is quite useful, please consider expose it as instance property, so we don't need to wrap requests in a multiple time.utctime() calls. It's a waste of syscall and duplicated code.
https://github.com/kennethreitz/requests/blob/master/requests/sessions.py#L570

I don't think we're going to expose it. We weren't keen to expose the elapsed attribute in the first place. We're not going to add yet another attribute, especially one we've never had a request for before. elapsed was only necessary because the hooks provided by requests were severely trimmed in 1.0.

If no one comments in the next 6 days, I'm going to close this.

I am ok with closing this,  as long as elapsed will be obsolete

Why do you want a widely used feature to be removed?
Sent from my Android device with K-9 Mail. Please excuse my brevity.

@sigmavirus24 Pardon my poor English, but how could  elapsed be widely used and you weren't keen to expose it?
My rationale is like this, since elapsed is widely used, and it involves a system call to get start request time, so it'd better to directly expose the start request time as a property directly, so other developers can make more use of this measure without wrapping yet another get current time system calls. As you can see people use requests often involve with time based constraints and there would be a ton duplicated code.

how could elapsed be widely used and you weren't keen to expose it?

It wasn't widely used before we added it. We were hesitant to add the attribute in the first place but (like most things that are added to public APIs) people use it because it's there. It's widely used now and it's not something we're going to remove.
There's two things to consider though:

Requests is in a feature freeze at the moment. That means no new additions to the API.
You are the first person in several years to ask us to expose this feature. Without a large number of people needing this to be provided by requests, the default answer is "No."

That said, you keep complaining about needing this causing you to make another system call. If you think system calls are inhibiting the performance of your application, I would strongly urge you to do real benchmarking to determine what is the actual cause of performance degradation. If you've already optimized every part of your application and have found that these system calls are causing performance problems that are noticeable, I think you have other problems to solve.

Me alone is complaining this so this must be a bad idea. Sorry for my bad idea and waste of your time, I'll see myself out.


Issue connecting LWM2M client

I wasn't able to run your LWM2M client example from the betwixt project - the client would connect sucessfully to a LWM2M server, but even the registration message did not get send out successfully.
I traced this down to an issue in canopus:

serveServer() in server.go starts listening to a local socket
run_basic_client.go then triggers sending out a registration message via Send()
Send() starts listening to another local socket and sends the registration message to the server from there
server then responds back to the socket opened by Send(), not the one by serveServer()

Actually, the LWM2M client should only ever need to listen to one socket. In this branch, I implemented a change where Send() reuses the already opened UDP socket, instead of opening another one: https://github.com/crenz/canopus/commit/6dc7ba1671f3e23c6af4ad05986b5a0a94a77dcc
Registration now suceeds, and requests are received successfully from Leshan and Wakaama LWM2M servers.

Fixes the connection issue to LWM2M


Mobile View Layout Optimization for "blog-home" Page

Description:
The current "blog-home" page layout on mobile and smaller screens places the avatar, tags, and custom section at the top. This arrangement requires excessive scrolling to reach the actual content, which impacts user experience.
Steps to Reproduce:
Open the "blog-home" page on a mobile device or in a mobile view emulator.
Observe the placement of avatars, tags, and custom sections.
Note the excessive scrolling required to view the main content.
Expected Behavior:
The layout should be optimized to improve content accessibility and reduce scrolling. Consider reorganizing elements to prioritize content visibility.
Suggested Solution:
Refer to the optimization approach used in the sugar-blog repository for inspiration on how to better structure the mobile view layout.
Additional Notes:
The current theme is well-appreciated. Keep up the good work!

Thanks for raising this issuse. Your feedback is extremely valuable to me.


add sample configuration load class and yaml example

This is just a example, customized from gateway code, we can modify this in the future

I don't think we need the ServiceConfiguration in archive service which is similar to the gateway/sidecar, it's mainly used for proxy. Archive service could be a simple rest web server which Quarkus self-provision could already archive.
@ruhan1 @ligangty

I don't think we need the ServiceConfiguration in archive service which is similar to the gateway/sidecar, it's mainly used for proxy. Archive service could be a simple rest web server which Quarkus self-provision could already archive.
@ruhan1 @ligangty
If we want to keep the config for further usage, it might be good to do in general-way, like firstly wiping off the proxy services portion(host, ssl...), it should not be used in this service I think.

Yes I agree, as quarkus can automatically load configuration in config/ folder at the same folder of the uber jar. I think there is no need to add this parsing logic for configuration.


Cluster restructuring

Some efforts to undertake
Creste a pluggable ID resolver infrastructure.
Instead of having a built in distributed hashtable for ID lookups, lets abstract this away to an ID resolver interface.
This way, we could use e.g. Redis or Memcache as storage.
This module would be dependant on cluster events such as join/leave events.
It should also be aware of cluster leader so that a specific node can take the role of updating the DB if needed.
We can likely augment the cluster events / infra to contain leader information.
And/Or, update some cluster infra to allow us to take a lock of some sort.
Extract the core logic of the Cluster so that it becomes more testable
This goes hand in hand with the task above, but it would also make life easier if we could have a test spec for cluster, which we then run against the different cluster and id providers to verify correctness.
cc @alexeyzimarev  @cpx86
Any thoughts / reflections on how to go about this all?

I've made it possible to disable the PidCache for cluster.
The idea is to make sure that everything works 100% correct w/o cache, then we can enable caching ontop of this.
Easier to pinpoint issues in this case

Current progress.
IIdentityLookup
Responsible for returning a PID given an actor Identity/name
This allows us to plug in completely different cluster providers, eg. if you want to store all id->PIDs in mongodb, this is now totally possible
Actors
Old partition actor per kind is now removed.
Instead each node has one PartitionIdentityActor and one PartitionPlacementActor.
PartitionIdentityActor is responsible for the lookup of ID->Pid, this is what the default IIdentityLookup uses
PartitionPlacementActor is responsible for spawning actors on a node in the cluster. it is also responsible for transferring ownership if the ID owner of an actor leaves
Leader Election
Cluster now does leader election, this is based on Consul session locks, the node that acquires a lock becomes the leader.
Banned Members (not devs :D )
When a node fails, other nodes will consider it to be failed and ban it from the cluster.
This is done live whenever a topology change occurs.
But in order to feed correct information to new nodes, we also let the leader store this in the consul session.
So that newly joined nodes can read and see what previous members have been banned.
This is mostly a safetynet to prevent nodes that previously failed but later recovered tries to re-join.
We do not allow failed nodes to rejoin simply because that will mess up cluster state, lookups and placements.

What happens with a failed node then? If a cluster runs in an unstable network, would it not eventually ban all the nodes and prevent them from rejoining?

Each node has a guid to identify it's instance id, if a node fails it should preferably stop itself and be rebooted by outer infrastructure (docker/kubernetes/whatever). this will give it a new instance id, even if it has the same port and host.
This is the same as what both Orleans and Akka does. don't let corrupt state back into the system. let it crash and start fresh.

Yeah, I agree. That’s what RabbitMQ suffers from, the partitioned cluster state.

btw. Running a local 100 nodes cluster with nodes being added every second, and still have stable lookups to the actors :-)
This needs some serious battle testing but so far it looks very nice

I am certain that we’ll battle test it soon enough :)

This is done


int vs double

https://github.com/Sentenai/py-sentenai/blob/4e589996d65058166b9b566043b90c2c70ddecfe/sentenai/flare.py#L370
any particular reason?

good question. @xnomagichash is this a typo? looks like we should have vt = 'int' here (and better testing to enforce it)

@xnomagichash should we do the same thing in the JS library? we currently use Number.isInteger:
https://github.com/Sentenai/js-sentenai/blob/0a250cceaf8eff16b3c7ceb15e4ab2577fc4f2e7/src/flare.js#L262

@brandly Yes, definitely.


Freeze when importing large XLSX file

Hi Robin,
I love your tool, it's wonderful! It only has one problem: If I am trying to import a 100.000 rows XLSX-file with 150 columns, the execution never returns (I was waiting > 15min), even if I give it 8G of memory via the xmx-parameter. The memory is consumed, but nothing happens then. Not even the index is created in elastic after 15min. Splitting the file manually to ~14.000 rows works and imports the data within ~1min – even though some
"io.vertx.core.impl.BlockedThreadChecker WARNING: Thread Thread[vert.x-eventloop-thread-3,5,main] has been blocked for 47 io.vertx.core.VertxException: Thread blocked"
exceptions are thrown, the data seems to be transferred to elastic completely and without any loss (AFAIK).
Any tips for me how I can manage even to import the large file at once, saving to manually split it?
Thanks!

Hello!
Thanks for submitting an issue.
That sure is one big excel file. The problem here is that the application attempts to parse the full excel file in memory as json, to make sure that it can parse the whole file. Because we'd like to avoid having the import fail halfway due to a parsing error, leaving the index in an undesired state. If it runs out of out of memory in doing so, it will stall indefinitely until more memory is available.
The real solution here would be to save the file to disk and stream it twice, first to parse it and make sure it is valid and then parse it again when importing. When importing we should only parse a few hundred rows at a time.
Additionally I will fix the warning message.
There is a similar issue already in #44, I will add some priority to fixing this and leave both issues open.


Add comprehensive beginner friendly DSA notes in C++ along with beginner to advance level projects in C++ and most commonly asked interview questions

Hi there,
I have detailed notes on Data Structures and Algorithms (DSA) in C++, including clear explanations of sorting algorithms and other core concepts. Additionally, I've prepared some commonly asked DSA interview questions (focused on C++) to help others prepare effectively for job interviews.
I would like to contribute by:
Adding detailed DSA notes in C++
Covering sorting algorithms like Linked list ,All the Sorting and Searching algorithms especially Quick Sort, Merge Sort, and more
Providing interview-level questions with solutions
These resources would help beginners and job seekers. If you find this contribution valuable, Please let me know if I can go ahead and start working on this.
Looking forward to your feedback!
Best regards,
Abhishek Saxena

Hey please assign this issue to me for Hactoberfest.

hey @abhisheksaxena15  please assign this issue to me


Cannot read property 'invoke' of undefined.

I am running a validation inside a component. The first time I trigger the validation, it is working perfectly. Once the form is valid, I transition to a new route. Then, if a go back to the previous page and trigger this.validate() again, I get this error message:
Uncaught TypeError: Cannot read property 'invoke' of undefined (code)
It seems to be linked to this issue #123, however I am already using the .on('init') handler.
ember-cli: 1.13.1
ember-validations: ~2.0.0-alpha.4

I am going to close this issue for now, feel free to reopen this issue if you feel like it's still relevant and we should take a look at it.


Cannot format in-place

This is regression.
Steps to reproduce (on a-Shell):
$ cd
$ echo 'let a:Int=0' > sample.swift
$ swift-format format -i sample.swift
<unknown>: error: Unable to format sample.swift: Error Domain=NSPOSIXErrorDomain Code=58 "Not supported"

Environment:

swift-format 510.1.0-wasm32-wasi, wasm32-wasi branch
a-Shell 1.14.1 (409)
iPadOS 17.5.1

509.0.0-wasm32-wasi doesn't have this issue.

The commit c13a7ff863b6a788ea80ef381cb66db5f3966959 may be the cause.

https://github.com/apple/swift-corelibs-foundation/blob/d7c868a21d086711de2cca72e619d4e8ce6bed49/Sources/Foundation/NSData.swift#L463
https://github.com/apple/swift-corelibs-foundation/blob/d7c868a21d086711de2cca72e619d4e8ce6bed49/Sources/Foundation/NSPathUtilities.swift#L752

If #54 is merged, another error still occurs, but writing itself succeeds.
https://github.com/kkebo/swift-format/pull/54#issuecomment-2156174961

In the latest artifact, all errors including https://github.com/kkebo/swift-format/pull/54#issuecomment-2156174961 have been resolved!
https://github.com/kkebo/swift-format/actions/runs/9586739128


Add custom billing flag whether the subscription is not billed automatically

Task linked: QF-2024 Add custom billing flag whether the subscription is billed separately

Task linked: QF-2023 Add max organization members configuration


Add button for the molecule rotation and full screen functions

currently rotating the molecule forces the user into full screen


Eheza Reports - visual addaptations

@adamhstewart

Allow access to each scope from the admin menu (right now you can only access Global) and use revised scope names.

Global scope is available because it does not require any further selection.
Other 2 scopes require selection of HC / Demographic fields, and this is not something that can be reflected on the menu.

@adamhstewart
Maybe we should get a file without the:

Deployed to live


numFound returns null

numFound has not been implemented for any calls that I can see.  This would be useful for web development especially.
{
"associations": [...],
"compact_associations": null,
"objects": [...],
"facet_counts": {...},
"numFound": null,
"start": null,
"facet_pivot": null
}

It looks like this issue is coming from Ontobio, where we use PySolr to query and parse the response from Solr.
PySolr parses the response and interprets numFound as hits. While the raw_response still contains numFound, the actual property to access would be results.hits.


chore: delete PModal and edit components.ts

To Reviewers

[x] Skipping review is not a problem (style, chore ONLY)
[x] Not that difficult

Type of Change

[ ] New feature
[ ] Bug fixes
[ ] Feature improvement

[ ] These changes require a usage change

[x] Others (performance improvement, refactoring, CI/CD, etc.)

Checklist

[ ] Updated Storybook documents for component
[ ] Wrote test codes for composable, utils and etc.
[ ] Tested with console(if usages are changed)

Description

delete PModal
edit components.ts more readable
move directory of PTextList (from others/console to data-display)

:tada: This PR is included in version 2.0.0-beta.59 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


fix: allow nullable field of equality delete writer

According to the doc fixed in https://github.com/apache/iceberg/pull/8981, the equality delete writer can have an optional field id. This PR fixes this.

cc @liurenjie1024 @Fokko @Xuanwo @sdd


App is not recognizing that I'm in a draft

Just upgraded to 3.07. Started a Shadows Remastered Premier Draft. When I opened the Magic Draft app, it said Current Draft: None. No recognition that I was drafting at all. The draft that I did shows up in 17lands so it was being recorded by the draft log. This is the 2nd time this has happened. Any ideas?

Hi Phyrre56,
Have you tried the solution listed in the troubleshooting section of the readme?

I did try the solution in the readme, but the app using the regular .exe also started working fine again. It seems to be a transient issue, only pops up occasionally. Next time I'm going to try restarting the computer or something and see if it fixes it, or if specific events for some reason seem to break it. (It's not format specific though, it happened once with a ONE draft and then was fine for the next ONE draft, and the same with SIR.)

I tried to reproduce your issue by starting a SIR draft, opening and closing the application, and modifying the settings mid-draft. The application was able to detect the draft every time and I didn't see any issues.
Is the application still unable to detect a draft after you restart it?
The next time this happens, if you could send me your Player.log file and debug.log files, then I can look into this further. Since I can't reproduce this issue on my own, there isn't much I can do without the log files.


Tests: Add a test for bad intersection behaviour

The test that fails now should just work.

Unfortunately, we can't accept failing tests. Please open an issue with your repro case and we'll fix it. Thanks!


ZE services not working anymore

Since 01.02.2020 the node is not working anymore due API key change. The new kamareon key is "Ae9FDWugRxZQAGm3Sxgk7uJn6Q4CGEA2" as discussed here:
https://gist.github.com/mountbatt/772e4512089802a2aa2622058dd1ded7

@fischifischi thanks.
At the moment I tried to fetch the data directly from a published JSON.
I will create today a new release with this hard coded API key.

@fischifischi please check version 1.2.0

@konne  yes, works again. Thank you!


flutter drive crashes when taking a screenshot after a signal

Thread 0 main threadArgumentError: Invalid argument(s): Invalid type for "path": null
at FileSystem.getPath(file_system.dart:160)
at LocalFileSystem.directory(local_file_system.dart:23)
at ErrorHandlingFileSystem.directory(error_handling_io.dart:130)
at DriveCommand._takeScreenshot(drive.dart:446)
at DriveCommand._registerScreenshotCallbacks.<anonymous closure>(drive.dart:369)
at LocalSignals._handleSignal.<anonymous closure>(signals.dart:136)
at asyncGuard.<anonymous closure>(async_guard.dart:111)
at _rootRun(zone.dart:1398)
at _CustomZone.run(zone.dart:1300)
at _runZoned(zone.dart:1803)
at runZonedGuarded(zone.dart:1791)
at runZoned(zone.dart:1743)
at asyncGuard(async_guard.dart:109)
at LocalSignals._handleSignal(signals.dart:136)
at <asynchronous gap>(async)

It seems like there might be a race w.r.t. the order that signal handlers are run?

on stable/3.10.0
with command flutter drive --driver=test_driver/integration_test.dart --target=integration_test/in_app_localhost_server/load_asset_file.dart
ArgumentError: Invalid argument(s): Invalid type for "path": null
at FileSystem.getPath(file_system.dart:160)
at LocalFileSystem.directory(local_file_system.dart:23)
at ErrorHandlingFileSystem.directory(error_handling_io.dart:128)
at DriveCommand._takeScreenshot(drive.dart:469)
at DriveCommand._registerScreenshotCallbacks.<anonymous closure>(drive.dart:392)
at LocalSignals._handleSignal.<anonymous closure>(signals.dart:136)
at asyncGuard.<anonymous closure>(async_guard.dart:111)
at _rootRun(zone.dart:1399)
at _CustomZone.run(zone.dart:1301)
at _runZoned(zone.dart:1804)
at runZonedGuarded(zone.dart:1792)
at runZoned(zone.dart:1744)
at asyncGuard(async_guard.dart:109)
at LocalSignals._handleSignal(signals.dart:136)
at <asynchronous gap>(async)


feat: add cert rotator

Description
What this PR does / why we need it:
This is a following PR of https://github.com/deislabs/ratify/pull/831. Add cert-rotator in Ratify to support rotating TLS related certificates automatically. The overall design doc can be found here: https://hackmd.io/@akashsinghal/BySB4VbHh

We adopt the cert-controller used in Gatekeeper. The cert-controller checks the validation of certificates every 12 hours and generates a new certificate that is valid for 10 years 90 days before the old certificate expires.
Upgrade GK versions from 3.10.0/3.11.0 to 3.11.0/3.12.0 as cert-controller only works for the externaldata.gatekeeper.sh/v1beta1.
Add access permissions to providers and secrets for Ratify as it needs to list/update them.
Add featureFlag CERT_ROTATION so that this feature is behind FF.
Add Ratify_NAME env var to Ratify as cert-rotator needs it for validation and cert generation.
Updated generate-tls-certs.sh so that the generated certs can pass the cert-rotator validation.
Add blocker for tlsCertWatcher so that cert-rotator will not start until certWatcher is ready.

Which issue(s) this PR fixes (optional, using fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when the PR gets merged):
Fixes https://github.com/deislabs/ratify/issues/834
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)
[ ] Helm Chart Change (any edit/addition/update that is necessary for changes merged to the main branch)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Please also list any relevant details for your test configuration
Adding a new e2e test which will be provided an expiring cert in deployment, which will trigger a cert rotatation immediately.
Checklist:

[ ] Does the affected code have corresponding tests?
[ ] Are the changes documented, not just with inline documentation, but also with conceptual documentation such as an overview of a new feature, or task-based documentation like a tutorial? Consider if this change should be announced on your project blog.
[ ] Does this introduce breaking changes that would require an announcement or bumping the major version?
[ ] Do all new files have appropriate license header?

Post Merge Requirements

[ ] MAINTAINERS: manually trigger the "Publish Package" workflow after merging any PR that indicates Helm Chart Change

As discussed offline, lets validate if Ratify throws error on startup when customer provides a expired cert.

As discussed offline, lets validate if Ratify throws error on startup when customer provides a expired cert.

with cert-rotator, Ratify will just rotate expired (ca or tls) cert and will not throw error. The previous implementation will throw error when requests come in but not on startup.

PR looks great Binbin, could you provide more details on logs and test coverage?
Have we covered cases for:

rotation customer provided cert
rotation for ratify auto generated cert
Are there any customer provided cert that we don't support rotation that we should document?
Once a cert is rotated by the rotator, what does ratify log look like?
Have we validated ratify 's configuration matrix with cert rotater disabled?
thanks!

For customer provided/ratify generated certs, cert-rotator will behave in the same way. If they're invalid, rotator will refresh invalid certs, and generate a log like:

And if it's valid, it will generate a log like:

Actually if customer provided any incompatible/invalid certs, cert-rotator will just auto-rotate it. But I can add some docs on the cert generated by cert-rotator so that customers can follow.

I'll add a basic notation test with rotator disabled.


Network policy does not work as expected in native routing mode

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
I have two cilium clusters one with an overlay network (vxlan) and one without (native routing mode).
Each cluster has two nodes (<IP_ADDRESS>,<IP_ADDRESS>).
In the cluster with overlay I see no problems when running the setup described below.
In the one which is running in the native routing mode I see a lot of packets being dropped with cilium monitor because the traffic seems to come from the outside world (identity: world) but it is not.
A small reproduction case includes two pods labeled with name: net2 running in the default namespace.
A nginx pod labeld with k8s-app: nginx which is exposed via service on port 80 in the default namespace.
The nginx pod runs on node <IP_ADDRESS>.
And the following two networkpolicies:
# Not Working
---
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
  name: to-nginx
  namespace: default
spec:
  podSelector:
    matchLabels:
      k8s-app: nginx
  ingress:
  - from:
    - podSelector:
        matchLabels:
          name: net2
  policyTypes:
  - Ingress
---
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
  name: to-nginx2
  namespace: default
spec:
  podSelector:
    matchLabels:
      name: net2
  egress:
  - {}
  policyTypes:
  - Egress

When I allow all egress from the net2 pods (<IP_ADDRESS>,<IP_ADDRESS>) and allow only ingress on the nginx from those two pods, curling of the nginx ( pod ip: <IP_ADDRESS>) service fails on one node <IP_ADDRESS>.
When running cilium monitor type=drop on node <IP_ADDRESS>, I see the reason for that:
xx drop (Policy denied) flow 0x1e30736e to endpoint 3359, file bpf_lxc.c line 1918, , identity world->31125: <IP_ADDRESS>:49936 -> <IP_ADDRESS>:80 tcp SYN
xx drop (Policy denied) flow 0x1e30736e to endpoint 3359, file bpf_lxc.c line 1918, , identity world->31125: <IP_ADDRESS>:49936 -> <IP_ADDRESS>:80 tcp SYN

The traffic comes in with the node IP (<IP_ADDRESS>) and is dropped.
# Working
---
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
  name: to-nginx
  namespace: default
spec:
  podSelector:
    matchLabels:
      k8s-app: nginx
  ingress:
  - {}
  policyTypes:
  - Ingress
---
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
  name: to-nginx2
  namespace: default
spec:
  podSelector:
    matchLabels:
      name: net2
  egress:
  - to:
    - podSelector:
        matchLabels:
          k8s-app: nginx
  policyTypes:
  - Egress

When I allow all ingress and and allow only egress traffic from pod net2 pod to the nginx pod everything works.
I do not understand, why the traffic is in the first case coming from the node IP and is dropped (SNAT is disabled).
It looks to me like in the first case somehow the identity got lost which is according to cilium identity list:
7315   k8s:io.cilium.k8s.namespace.labels.kubernetes.io/metadata.name=default
           k8s:io.cilium.k8s.policy.cluster=default
           k8s:io.cilium.k8s.policy.serviceaccount=default
           k8s:io.kubernetes.pod.namespace=default
           k8s:name=net2

and instead has now the identity world.
Shouldn't the identity here be obtained? Is there a way to somehow tell cilium that the k8s node cidr range should not have the identity reserved:world?
16777218   cidr:<IP_ADDRESS>/16
           reserved:world

Cilium Version
Client: 1.12.4 6eaecaf 2022-11-16T05:45:01+00:00 go version go1.18.8 linux/amd64
Daemon: 1.12.4 6eaecaf 2022-11-16T05:45:01+00:00 go version go1.18.8 linux/amd64
Kernel Version
Linux ip-10-180-25-21.eu-west-1.compute.internal 5.10.141-garden-cloud-amd64 #1 SMP Debian 5.10.141-0gardenlinux1 (2022-09-07) x86_64 x86_64 x86_64 GNU/Linux
Kubernetes Version
1.25.4
Sysdump
No response
Relevant log output
No response
Anything else?
For reproduction:
apiVersion: apps/v1
kind: DaemonSet
metadata:
  name: net2
spec:
  selector:
    matchLabels:
      name: net2
  template:
    metadata:
      labels:
        name: net2
    spec:
      hostNetwork: false
      dnsPolicy: ClusterFirst
      containers:
      - name: net2
        image: nicolaka/netshoot
        command: ["/bin/sh"]
        args: ["-c", "while true; do sleep 3600;done"]
        ports:
        - containerPort: 80
      tolerations:
      - key: ""
        operator: Exists

nginx pod was created with:
kubectl run nginx --image=nginx
kubectl expose pod nginx --port 80

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Do you have <IP_ADDRESS>/16 anywhere in your policies like toCIDR or fromCIDR?

Can you also provide further repro instructions for initiating the dropped traffic?

Can you also provide further repro instructions for initiating the dropped traffic?
I've curled the service ip and pod ip out of the net2 pods.

curl <svc-ip-of-nginx>
curl <pod-ip-of-nginx>

Do you have <IP_ADDRESS>/16 anywhere in your policies like toCIDR or fromCIDR?

Yes it's also included in the kube-dns network policy:
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
  name: allow-dns
  namespace: kube-system
spec:
  egress:
  - ports:
    - port: 443
      protocol: TCP
    - port: 53
      protocol: TCP
    - port: 53
      protocol: UDP
  ingress:
  - from:
    - namespaceSelector: {}
      podSelector: {}
    - ipBlock:
        cidr: <podCIDR>
    - ipBlock:
        cidr: <IP_ADDRESS>/16
    ports:
    - port: 9153
      protocol: TCP
    - port: 8053
      protocol: TCP
    - port: 8053
      protocol: UDP
  podSelector:
    matchExpressions:
    - key: k8s-app
      operator: In
      values:
      - kube-dns
  policyTypes:
  - Ingress
  - Egress

For
    - ipBlock:
        cidr: <podCIDR>

Cilium doesn't support this.
And I assume
    - ipBlock:
        cidr: <IP_ADDRESS>/16

is to allow traffic from nodes (or pods with host-network)? I'd advise using CNPs with entities-based rules.

Issue is solved.

I stumbled across the same problem.
But I and the initial poster are using a standard K8s NetworkPolicy not a CiliumNetworkPolicy.
I still don't get why it is not working.


Please add a license to this repo

First, thank you for sharing this project with us!
Could you please add an explicit LICENSE file to the repo so that it's clear
under what terms the content is provided, and under what terms user
contributions are licensed?
Per GitHub docs on licensing:

[...] without a license, the default copyright laws apply, meaning that you
retain all rights to your source code and no one may reproduce, distribute,
or create derivative works from your work. If you're creating an open source
project, we strongly encourage you to include an open source license.

Thanks!

Thanks for your advice.
I have added the license.

Thank you!!


Crash in deleteDatabaseFromDisk method

The "path" property may release, May be should retain it in init method
I changed the init function:

It's works fine

^noticed the same thing

replace retain with copy
`/**
The path of the database on disk
*/
@property (nonatomic, retain) NSString *path;
/**
The name of the database.
*/
@property (nonatomic, retain) NSString *name;`
`/**
The path of the database on disk
*/
@property (nonatomic, copy) NSString *path;
/**
The name of the database.
*/
@property (nonatomic, copy) NSString *name;`


Bump cryptography from 39.0.2 to 40.0.0 (#5738)

Pull request opened by the merge tool on behalf of #5738

Merged in e6fe8556a7377bc4dea444e06963b1fe1e34ec60


Create getTestBuildsByMachine API

Create a getTestBuildsByMachine API to allow users to get test build info by machine name.
Inputs:

machine - required. can be regex
buildName - optional. can be regex

Output:
[{
buildName = Test_openjdk17_j9_sanity.openjdk_x86-64_linux_testList_1
machine = ub20x64rt1-7.fyre.ibm.com
passRate = 3/10
},
...]

@momanmalik could you take a look at this one? Thanks


Feature request

disable IE 11 (Powershell): Disable-WindowsOptionalFeature -FeatureName Internet-Explorer-Optional-amd64 –Online

remove Edge (Powershell):remove-appxpackage [ path:"get-appxpackage edge | Select Name, PackageFullName" ]

remove Cortana (Powershell): remove-appxpackage [ path:"get-appxpackage cortana | Select Name, PackageFullName" ]

Are these safe? I don't want to add something that can potentially break future updates.

Dont implement those without testing. I am currently under Linux, but am interested in contributing to this repo, so i will bee soon testing those and create a pull request. Maybe a feature request label could be helpful? Found this via reddit, nice work so far! :)

Thanks, sure, I will add the labels and stuff, I opened the repo recently, as it was a personal tool, didn't expect it to blow off like that. Now I have to make it more user friendly :)


chore(build): Enable building hyper in docker containers on travis

By stating that hyper does not need sudo to build it can be compiled in
a container:
http://blog.travis-ci.com/2014-12-17-faster-builds-with-container-based-infrastructure/

Good catch! This makes builds much faster.

Oh awesome!!


parliamentlive.tv has stopped working

Please follow the guide below

You will be asked some questions and requested to provide some information, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your issue (like this: [x])
Use the Preview tab to see what your issue will actually look like

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2<IP_ADDRESS>. If it's not, read this FAQ entry and update. Issues with outdated version will be rejected.

[X] I've verified and I assure that I'm running youtube-dl 2<IP_ADDRESS>

Before submitting an issue make sure you have:

[X] At least skimmed through the README, most notably the FAQ and BUGS sections
[X] Searched the bugtracker for similar issues including closed ones

What is the purpose of your issue?

[X] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

The following sections concretize particular purposed issues, you can erase any section (the contents between triple ---) not applicable to your issue

If the purpose of this issue is a bug report, site support request or you are not completely sure provide the full verbose output as follows:
Add the -v flag to your command line you run youtube-dl with (youtube-dl -v <your command line>), copy the whole output and insert it here. It should look similar to one below (replace it with your log inserted between triple ```):
youtube-dl --verbose http://parliamentlive.tv/Event/Index/1c220590-96fc-4cb6-976f-ade4f23f0b65
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: [u'--verbose', u'http://parliamentlive.tv/Event/Index/1c220590-96fc-4cb6-976f-ade4f23f0b65']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2<IP_ADDRESS>
[debug] Python version 2.7.10 - Darwin-17.0.0-x86_64-i386-64bit
[debug] exe versions: ffmpeg 3.4, ffprobe 3.4, rtmpdump 2.4
[debug] Proxy map: {}
[parliamentlive.tv] 1c220590-96fc-4cb6-976f-ade4f23f0b65: Downloading webpage
ERROR: Unable to extract kaltura widget config; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
  File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 784, in extract_info
    ie_result = ie.extract(url)
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 434, in extract
    ie_result = self._real_extract(url)
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/parliamentliveuk.py", line 32, in _real_extract
    webpage, 'kaltura widget config'), video_id)
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 797, in _search_regex
    raise RegexNotFoundError('Unable to extract %s' % _name)
RegexNotFoundError: Unable to extract kaltura widget config; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

If the purpose of this issue is a site support request please provide all kinds of example URLs support for which should be included (replace following example URLs by yours):

Single video: http://parliamentlive.tv/Event/Index/1c220590-96fc-4cb6-976f-ade4f23f0b65

Note that youtube-dl does not support sites dedicated to copyright infringement. In order for site support request to be accepted all provided example URLs should not violate any copyrights.

Description of your issue, suggested solution and other information
Parliamentlive.tv seems to have stopped working. The above error log is for the first video I tried but I have recreated this on several videos on the site.

Here's a workaround:

Open the page with the video
Right-click and choose "Inspect"(or whatever your browser calls it)
Go to the Network tab, and refresh the page
Once the video starts playing use the filter box in the Network tab to search for "m3u8"
Right-click the result and choose "Copy URL"(if there is more than one just try each one using the next steps until you find your video)
Make sure you have ffmpeg installed or in the same path as youtube-dl
Now run youtube-dl 'http://M3U8URL' -F, If you get shown a selection of video qualities then it's possible to download the video
Now run youtube-dl 'http://M3U8URL' to download the video. (use the -f flag with the codes displayed in step 7 if you wish to choose a specific format or quality)

NOTE: If you get the error:
No such file or directory
ERROR: ffmpeg exited with code 1

Then add the -o Parliament.mp4 flag to your command


EthereumApp, ERC20App data decoding and asset unlocking

[x] Refactor Bank contract to EthereumApp contract and ERC20App contract
[x] Decode data packages for EthereumApp and ERC20App

Git history is a bit messy.

Re https://github.com/Snowfork/polkadot-ethereum/pull/57#discussion_r479502090, https://github.com/Snowfork/polkadot-ethereum/pull/57#discussion_r479505173 - the upside here is that 'submit' facilitates a generalized relayer as each transaction has the same function signature and only the receiving application's contract address changes. Using unlock as the standardized function name would accomplish the same thing, but in the future not all applications will necessarily be unlocking tokens.

Re #57 (comment), #57 (comment) - the upside here is that 'submit' facilitates a generalized relayer as each transaction has the same function signature and only the receiving application's contract address changes. Using unlock as the standardized function name would accomplish the same thing, but in the future not all applications will necessarily be unlocking tokens.

Makes sense 👍

I'm closing this since its already been merged in via the integration PR #59. Task #66 tracks addressing the feedback.


Investigate policies for Flink statements

Investigate if it is possible to create policies to allow only certain types of Flink statements, for example, not allowing INSERT statements. Will need to research how to sanitize/normalize a Flink statement to ensure input is clean, e.g., https://cheatsheetseries.owasp.org/cheatsheets/Input_Validation_Cheat_Sheet.html

Ref: https://cheatsheetseries.owasp.org/cheatsheets/SQL_Injection_Prevention_Cheat_Sheet.html


gateway: Upgrade API version

This is to avoid the below warning
W0205 12:29:06.703289  146168 warnings.go:70] The v1alpha2 version of ReferenceGrant has been deprecated and will be removed in a future release of the API. Please upgrade to v1beta1.

AFAIU this will break backward compatibility support for clusters with Cilium v1.13 installed. This version still installs Gateway API in version 0.5.1 that doesn't contain the new api versions.
Is this ok?

I think it should be alright as long as we have another entry for 1.15+ in https://github.com/cilium/cilium-cli?tab=readme-ov-file#releases


💡[Feature]: Enhancement of UI of Features page

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
Making changes in font, image with better pixels and height, width and using proper font sizes to enhance the UI.
Use Case
This will improve the aesthetics of the website.
Benefits
This will ensure that the text is appealing and the images are in proper pixel size hence, easy to understand the amazing features of this website.
Add ScreenShots

Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

i want to work on this issue ,please assign me

@rohir1132yadav assigned


Add "format : color" to Profiles Schema color items

A simple one-liner addition to profiles.schema.json.
Enables VSCode to recognize Color-type entries in profiles.json and show a color decorator in the editor.
"format" : "color" is a nonstandard, VSCode-specific extension to the schema format, but it shouldn't hurt validation for this case.

If this schema extension causes VScode to emit an alpha channel, it will be incompatible with the Terminal’s actual schema

I just tested locally, and while you can use VSCode's color picker to set an alpha value, it gets marked with a warning as being incompatible with the defined schema. So it shouldn't cause any real issues, the warning is right there in the editor.

/azp run


refactor: remove web component source

source is now hosted at https://github.com/uPortal-contrib/notification-web-components
resolves #291

/cc @rmathis


Try to fix self-serve failure

This seems to fix the issue in local tests

A check to see whether headers is defined (and a dict) would also be a good idea. If called with e.g. headers=None, it should probably just create a new empty dict on the spot, so copy doesn't fail.


Update web site links for the 2.8.0 release

Update web site links for the 2.8.0 release

Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

It will help us expedite review of your Pull Request if you tag someone (e.g. @username) to look at it.
 It is a website only change.


Fix the javascript function  of calculator .

i think the js Function have Bug or  something is wrong with it , it show 1+1 =10  and 1/0 broke the application, fix this answer Zero is not showing , like = 1*0 = empty .
please don't change the whole, function try to solve with minor changes .

i think the js Function have Bug or something is wrong with it , it show 1+1 =10 and 1/0 broke the application, fix this answer Zero is not showing , like = 1*0 = empty .
please don't change the whole, function try to solve with minor changes .

It's a binary calculator, that's why 1 + 1 = 10 because 10 is binary from 2


Find Blood Page UI Update

Related Issue
fixes #177
Description

Added new Donor Card Comoponent
Used shadcn Select component in Filter by Blood Group
Used Donor Card in Find Blood Page
Slightly change Navbar (link hover style)

Type of PR

[ ] Bug fix
[ ] Feature enhancement
[ ] Documentation update
[X] Other (specify): Styling Change

Screenshots / videos (if applicable)

Checklist:

[X] I have performed a self-review of my code
[X] I have read and followed the Contribution Guidelines.
[X] I have tested the changes thoroughly before submitting this pull request.
[X] I have provided relevant issue numbers, screenshots, and videos after making the changes.
[X] I have commented my code, particularly in hard-to-understand areas.

Additional context:
NA

@msanchariii cool


lnwallet+docs: minrelayfee always above fee floor

The minimum relay fee is always ensured to be above our fee floor except
in the very first min relay fee query to bitcoind. This commit ensures
that the fee floor is respected in this first query.
Fixes #6072

Thank you! I tested this branch to open a channel on my node that was previously stuck on 250 sat/kw which was insufficient for channel broadcasts on testnet.
The channel funding tx broadcast worked, but interestingly I got a higher fee rate than expected of 3 sat/byte, see below
[INF] CHFD: Performing funding tx coin selection using 747 sat/kw as fee rate
https://blockstream.info/testnet/tx/8d21ecf648fd99a7781f16ef99e90d52d120f42b7c53dcc49c38f5a00f7cc64f
This was during a flurry of blocks on testnet (multiple within a minute) and near empty mempools and 1 sat/byte recommended by mempool.space. So I found this a bit odd, but I'll try a channel open again when testnet is under more normal conditions with blocks spaced a few minutes apart.

Thank you! I tested this branch to open a channel on my node that was previously stuck on 250 sat/kw which was insufficient for channel broadcasts on testnet.
The channel funding tx broadcast worked, but interestingly I got a higher fee rate than expected of 3 sat/byte, see below
[INF] CHFD: Performing funding tx coin selection using 747 sat/kw as fee rate
https://blockstream.info/testnet/tx/8d21ecf648fd99a7781f16ef99e90d52d120f42b7c53dcc49c38f5a00f7cc64f
This was during a flurry of blocks on testnet (multiple within a minute) and near empty mempools and 1 sat/byte recommended by mempool.space. So I found this a bit odd, but I'll try a channel open again when testnet is under more normal conditions with blocks spaced a few minutes apart.

747 sat/kw is roughly 3 sat/byte

This was during a flurry of blocks on testnet (multiple within a minute) and near empty mempools and 1 sat/byte recommended by mempool.space.

lnd will just use w/e is returned by the fee estimator. Testnet is weird at times, and you'll see transactions over paying routinely as there're no economic constraints, so I wouldn't take too much stock in estimate returned on testnet.


ci: bump test suite to k8s 1.26 and 1.29

Motivation
Drops testing for an EOL K8s version (1.25) and adds e2e testing for the latest version (1.29)
Modifications

changed the test suite minimum to k8s 1.26
changed the default test suite k8s version to 1.29
updated the supported versions in releases.md

Verification
The test suite will verify the change

The test failure looks like https://github.com/argoproj/argo-workflows/issues/12836


js.map files reference non-existant .ts files

All of the package's .js.map files reference .ts files that don't exist in the installation.
But the browser (Edge, in my case) tries to load them, creating 404 errors that one has to chase down in order to understand and know to ignore.
Version: 1.0.17

Oh, dear. I am sorting this out now.


Explore the implications of plural abstractions

Explore the implications of plural abstractions as "partial functions in the domain of types." How does this interact with higher-order logic?

This seems to remain sound with respect to interactions with most existing Lambda Calculus based Term,Type systems. Inference may become weaker.