Kata container cannot skip host cache.

Description of problem
I set block_device_cache_set = true and block_device_cache_direct = true in /usr/share/defaults/kata-containers/configuration.toml, and then ran FIO benchmark in a kata container using directIO. Before running the benchmark, I cleared the host cache by echo 3 > /proc/sys/vm/drop_caches, however, the host cache is still used during the benchmark execution. This can be observed by:
Before running the FIO in kata container, the host shows:
# free -g
              total        used        free      shared  buff/cache   available
Mem:             31           1          29           0           0          29
Swap:             1           0           1

After running the FIO in kata container, the host shows:
# free -g
              total        used        free      shared  buff/cache   available
Mem:             31           1          25           0           4          29
Swap:             1           0           1

Inside kata container, the file system is 9p
root@0aaa9025c921:/# df -Th
Filesystem     Type   Size  Used Avail Use% Mounted on
kataShared     9p      45G   20G   23G  46% /

Following is the command to run the FIO benchmark:
FIO_RW=read NUM_JOBS=1  fio fio_jobfile.fio --fallocate=none --runtime=60 --directory=/ --blocksize=4096 --output=1_read.json
fio_jobfile.fio:
[global]
; Parameters common to all test environments

; Ensure that jobs run for a specified time limit, not I/O quantity
time_based=1

; To model application load at greater scale, each test client will maintain
; a number of concurrent I/Os.
ioengine=libaio
iodepth=8

; Note: these two settings are mutually exclusive
; (and may not apply for Windows test clients)
direct=1
buffered=0

; Set a number of workers on this client
thread=0
numjobs=${NUM_JOBS}
group_reporting=1

; Each file for each job thread is this size
filesize=4G
size=4G
; filename_format=$jobnum.dat

[fio-job]
; FIO_RW is read, write, randread or randwrite
rw=${FIO_RW}

Expected result
Expect the host cache is not used by the FIO in kata container
Actual result
Host cache is used by the FIO benchmark in kata container.

This issue is being automatically closed as Kata Containers 1.x has now reached EOL (End of Life). This means it is no longer being maintained.

Important:
All users should switch to the latest Kata Containers 2.x release to ensure they are using a maintained release that contains the latest security fixes, performance improvements and new features.

This decision was discussed by the @kata-containers/architecture-committee and has been announced via the Kata Containers mailing list:

http://lists.katacontainers.io/pipermail/kata-dev/2020-November/001601.html
http://lists.katacontainers.io/pipermail/kata-dev/2021-April/001843.html
http://lists.katacontainers.io/pipermail/kata-dev/2021-May/001896.html

If you believe this issue still applies to Kata Containers 2.x, please open an issue against the Kata Containers 2.x repository, pointing to this one, providing details to allow us to migrate it.


Clarify that copy often retries

The documentation was accurate for the task, but misleading in common contexts.
cc @matkoch who asked about this: https://twitter.com/matkoch87/status/1301483272065691648?s=20

@rainersigwald : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Supporting .pypirc in publish command

Assuming #759 is merged, it'd be nice to add  --config-file dispatch to more consciously support .pypirc (I can't remember if Twine will dynamically load this with incomplete arguments).
It might be nice to implement this so that .pypirc can be used in place of Rye's credentials management.
So something like this would tell Rye to disregard managed credentials in favor of the .pypirc file.
rye publish --config-file <path>

And if this pattern works well, we could extend it to support other credentials files.
Originally posted by @cnpryer in https://github.com/astral-sh/rye/issues/759#issuecomment-1963112728

Just found this crate from Charlie Marsh, it is probably what is needed to parse the .pypirc. I tried a little bit with expecting it to be a .toml and that didn't work out at all. I'm pretty sure a .INI-style is used.
https://github.com/charliermarsh/configparser-rs

Double posting from #759 which @cnpryer kindly made me aware of:
Any chance that Twine's --config-file option could be dispatched as well?
In my current use-case, this would support the TwineAuthenticate@1 task from Azure Pipelines
Originally posted by @camilo-s in https://github.com/astral-sh/rye/issues/759#issuecomment-2037687739

@camilo-s just FYI, it is possible to supply them via command line in the current version or Rye. It should be possible to either get this information from Azure or setting it up locally on your machine and look at your local .pypirc. Everything is stored in clear text so it is just copy/pasting.
I.e. you wouldn't have to run the task TwineAuthenticated-task at all. I have this in my Github Action when publishing to a private repo on Google Cloud:
rye publish -r ${{ env.REPO_NAME }} --repository-url ${{ env.REPO_URL }} --username ${{ env.USERNAME }} --token ${{ env.PASSWORD }} -y

And that works great for me.


test: e2e concurrency + split e2e tests

Thanks for submitting a PR! Please check the boxes below:

[ ] I have run pre-commit to check linting
[ ] I have filled in the "Changes" section below?
[ ] I have filled in the "How did you test this code" section below?
[ ] I have used a Conventional Commit title for this Pull Request

Changes
Please describe.
How did you test this code?

Please describe.

Codecov Report
Patch coverage: 97.67% and project coverage change: -0.01% :warning:

Comparison is base (34f9a5b) 95.52% compared to head (d95e734) 95.52%.
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2761      +/-   ##
==========================================
- Coverage   95.52%   95.52%   -0.01%
==========================================
  Files         993      994       +1
  Lines       28031    28044      +13
==========================================
+ Hits        26778    26790      +12
- Misses       1253     1254       +1

Files Changed
Coverage Δ

api/e2etests/views.py
94.11% <83.33%> (-5.89%)
:arrow_down:

api/app/settings/common.py
88.11% <100.00%> (+0.15%)
:arrow_up:

api/e2etests/e2e_seed_data.py
100.00% <100.00%> (ø)

...sts/tests/end_to_end/test_integration_e2e_tests.py
100.00% <100.00%> (ø)

api/e2etests/urls.py
100.00% <100.00%> (ø)

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


Allow custom helpers

Allow custom helpers
This pull request makes it possible to use custom helpers with Ghost.
Custom helpers can be placed in /content/helpers, or inside a theme folder: /content/themes/casper/helpers.
Example
Place the following code into /content/helpers/stringify.js:
module.exports = function stringify(object) {
    return JSON.stringify(parseJson);
 }

Now you can use it like after restarting ghost:
{{#get "posts" limit="all"}}
{{#stringify posts}}

Hi @mariusbolik thanks for supplying this PR.
We don't have support for custom helpers in Ghost for a couple of key reasons:

The first is that it would allow users/theme developers to run arbitrary custom code, which needs careful, in-depth consideration from both a usability and security point of view. We not only have to add support, but would need to maintain it, ensuring Ghost is secure and usable long term.
The second is that to date, no one has provided a clear use case for custom helpers, such that there's value to offset the costs I mentioned above. Every time we dig into the underlying reason why someone is trying to add a custom helper they are trying to either do something that can already be done with Ghost's existing, extensive set of helpers, that wouldn't work as expected e.g. rendering dynamic content into a statically rendered template, or they were trying to do something that should have been possible and so we added a helper to accomplish the goal.

It appears you're trying to output Ghost data as JSON, which doesn't make much sense to me as a use case in production, but I'd hazard a guess you were trying to make development and debugging easier, in which case the closest thing we have right now is the {{log}} helper, that will output the JSON to your terminal. We have discussed adding a {{json}} helper for this as well, which we would happily accept a PR for, and makes more sense for all the reasons I've outlined than adding generic custom helper support.
If I'm wrong and your use case is something else, let me know :)


feat: support transactions sent to address 0

Feature Request
Describe the Feature Request
Currently, transactions sent to the address 0 are processed as deploy transactions.
We need to distinguish transactions sent to the 0 address from deploy transactions in a way that enables sending txs to the 0 address.

Closed by #951


FE: MVP

Look at all those commits!

It's almost like we all worked really hard on this. Almost. ;)

Looks good to me! :shipit:

looks good after merging develop-cleanup


Eliminate acm_cpp filetype.

We should greatly simplify acm_cpp filetype logic: ee can just make it cpp filetype, and have a few buffer-local autocommands for *.acm files.

Closed by #6


[ts-http-runtime] Port core-util fixes

Packages impacted by this PR
@typespec/ts-http-runtime
Describe the problem that is addressed by this PR
A simple port of core-util fixes from PR #27441 and #27515

API change check
APIView has identified API level changes in this PR and created following API reviews.
typespec-ts-http-runtime


Drakula Eclipse in Windows (Top Bars)

How in Windows can you have the same theme in the IDE as in the image?
Current Windows

draculatheme

In draculatheme the IDE seems much cleaner with the hidden bars (or the same color as the background), the more attractive checkboxes or even everything cleaner. How can it be done?

@scottzach1 can you take a look?

Hey @drakgoku, your question appears to overlap with #2, which I just replied to, so I will copy my response here.

Unfortunately, the taskbar cannot be changed by Eclipse as they natively use the default system title bars to the best of my
knowledge. In the provided screenshots, these title bars are using Dracula colours as they are taken on a system running Linux > where GTK has additionally been themed using dracula/gtk. A little > searching online yielded the following unofficial Dracula theme for Windows system title bars. I do not know of the developer or > software, so I cannot comment on whether it is working / safe. Best of luck!
https://www.deviantart.com/niivu/art/Dracula-for-Windows-10-843182521

Sorry, I don't have any easy answer to your question. I would love to hear how you get on if you decide to take this further!
Best of luck :smile:

Good news. I've only done 2 things. It is a much prettier arrangement than before, it is not 100% what I am looking for, but it is a great help.
1 - Copy Drakula's aero in windows resources
2 - Install UltraUXThemePatcher

I haven't installed anything else and it really changed the windows GUI.

Awesome work! Thanks for sharing that looks super tidy 😋.
Unfortunately I think this extends beyond the scope of this project. Feel free to close the issue if you feel it has been resolved.
Cheers!


Update baseTemplate.mnky

added default for hiding error messages for AppDynamics controllers

Note that this will only update the base template for new users of DemoMonkey.


Added 'The Modern JS Tutorial' to JavascriptSyntax section

I think this is a fantastic JS resources for all the members of our community.
If you want to review it, have a look here: https://javascript.info/

Thanks for your contribution @odv


Respect HTTP 429 and Retry-After header

When a 429 is received, sleep for the length of time indicated by Retry-After, then try again.
Try up to 3 times before giving up, although the count can be configured with :ratelimit_retries if you want more or less
If no Retry-After is sent by the server, defaults to 2 seconds (something is better than nothing). That should only happen with quite old and unsupported versions of GitLab

I plan to release this week.

@NARKOZ It's been a while; any chance we could get that release soon?  I would be very grateful.

@craigmiskell-gitlab I've just released a new version and pushed to Rubygems https://github.com/NARKOZ/gitlab/releases/tag/v4.18.0
Sorry for the wait!


Scaling for pyglet.gui widgets.

I think every widget in pyglet.gui should have scale, scale_x and scale_y properties.
These properties would change the scale of all images the widget contains before drawing them to the screen. This would work in a similar way to how the pyglet.sprite module scales images.
Users of pyglet could use this feature to create GUIs for differing screen sizes.

I think this might be a little out of scope for this module.
Also, most UIs don't scale their widgets individually when the screen is resized.
For desktop applications, the widgets are usually just re-positioned when reshaping a Window.
For games, they tend to just scale the entire framebuffer, instead of individual components on the screen. Some games do offer options to adjust the size of widgets separately from the base resolution, but that's the exception rather than the rule. In those cases, I'd argue that it's better to provide multiple images for the different sizes, and just change the widgets when adjusting the size.  For actual infinitely resizable widgets, it's probably best to make a custom object for that.

Scale with projection could work?

That's what I was thinking.

Can you scale them with a projection whilst still maintaining functionality (collision boxes update)?

What I did is instead of batch drawing, I made a draw function in the widgets class and drawed each indivual item in that function. Then did widget.draw() that way you can update a size variable.

@benmoran56
Every gui library I've used they allow you to change each widgets size indivually. And the only thing I do now is software development. So I know alot about gui.

Also every gui library I've used has had a outline on each widget set by default to False and can be used by setting it to true.

pyglet isn't aiming to be a full featured GUI library, so unfortunately advanced features like this are out of scope.
The existence of the pyglet.gui module was really just to provide the very basics, that someone could potentially build on themselves.
More advanced GUI features would be better suited for a third party library, and in fact there already existst a few.
For example the Glooey library:
https://github.com/kxgames/glooey
Thank you for opening the ticket and voicing your ideas!


Improve ndimage convolve/correlate

This PR improves performance of convolve and correlate in cupyx.scipy.ndimage.filter.py.
I was investing why the performance of convolve and correlate was slower than expected, and it seems one of the causes is that raw array access via CArray is slow.. The issue will be addressed with this PR.
Performance (convolution, fp32)

[sec]
scipy convolve
cupyx convolve (current)
cupyx convolve (this PR)

x.shape = (4000, 4000), w.shape = (3,3)
0.225978
0.002195
0.000670

x.shape = (4000, 4000), w.shape = (5,5)
0.390014
0.005525
0.001229

x.shape = (4000, 4000), w.shape = (7,7)
0.761595
0.011325
0.002043

x.shape = (300, 300, 300), w.shape = (3, 3, 3)
0.702484
0.028360
0.002025

Quadro GV100
CUDA 10.2

That is a very nice speedup for such a small change!
Not directly related to this PR, but for cases when the kernel is small enough to fit, do you think it would help to copy it to shared memory? I suppose with a RawModule you could also keep the kernel in global/constant memory via get_global, but I don't think there is a way to do the equivalent with an ElementwiseKernel.

This is a very good catch, @anaruse! Do you think the CArray class is too abstract to provide good performance? I've had a hard time understanding it...

Note that I currently have a similar solution but then also generalizes to all of ndimage.filters. I too did notice the slow CArray lookups and then when using custom handling of indices it was way faster.

Your current version does always force the input array to be C contiguous and if it isn't copies the entire array. With a little extra work as done in mine (which I am going to submit a PR for in just a bit) it doesn't require non-contiguous arrays to be copied first.

Your current version does always force the input array to be C contiguous and if it isn't copies the entire array. With a little extra work as done in mine (which I am going to submit a PR for in just a bit) it doesn't require non-contiguous arrays to be copied first.

I agree that this is a limitation, but it could potentially be worth always enforcing contiguity for performance? We would have to benchmark on various contiguous and non-contiguous inputs to be sure. In memory-limited scenarios, avoiding the copy would obviously be preferable, though.
In any case, contiguity was already being enforced prior to this PR, so at least it is not a new requirement:
https://github.com/cupy/cupy/blob/05c8194dc9955f5fad2fbd8fb538389decca1756/cupyx/scipy/ndimage/filters.py#L106-L107

@grlee77 I did some very basic timing tests on my machine and having the non-contiguous helping of the input image (but not the weights, I still always make that contiguous since it should be relatively small) did not make a time difference with my code as in the other PR. I didn't actually test with any non-contiguous array, but the lack of speed difference isn't surprising since the current code essentially multiples by the stride right now anyways:
https://github.com/cupy/cupy/blob/05c8194dc9955f5fad2fbd8fb538389decca1756/cupyx/scipy/ndimage/filters.py#L175
It just computes the sx_j variables (the strides) from the shape instead of just using x.strides()[{j}].
Here are the times for some convolutions, first line is not assuming contiguous arrays and second assumes contiguous (but doesn't actually do the check). Sometimes assuming contiguous is slower.
(4000, 4000) ⊗ (3, 3)
1.32 ms ± 1.34 µs per loop (mean ± std. dev. of 7 runs, 1000 loops each)
1.31 ms ± 6.88 µs per loop (mean ± std. dev. of 7 runs, 1000 loops each) # assuming contiguous
(4000, 4000) ⊗ (5, 5)
2.91 ms ± 6.05 µs per loop (mean ± std. dev. of 7 runs, 100 loops each)
2.95 ms ± 9.63 µs per loop (mean ± std. dev. of 7 runs, 100 loops each) # assuming contiguous
(4000, 4000) ⊗ (7, 7)
5.15 ms ± 2.04 µs per loop (mean ± std. dev. of 7 runs, 100 loops each)
5.25 ms ± 6.88 µs per loop (mean ± std. dev. of 7 runs, 100 loops each) # assuming contiguous
(300, 300, 300) ⊗ (3, 3, 3)
17.1 ms ± 2.87 µs per loop (mean ± std. dev. of 7 runs, 100 loops each)
17.1 ms ± 4.89 µs per loop (mean ± std. dev. of 7 runs, 100 loops each) # assuming contiguous

@leofang The problem with CArray is that if you use a linear index it incurs several divisions/modulos to compute the new index (even if that index will end up being the same exact same index since it is a contiguous array). That means every single lookup or set has a fairly large unexpected overhead.
I understand why it is doing this - it is to protect ElementwiseKernel authors from having to worry about non-contiguous array access. But it would be nice if:

The array was contiguous then CArray directly used the linear index (and no division/modulo/multiplication)
The ElementwiseKernel author could optionally turn off linear index conversion (even for non-contiguous arrays)

I can't remember if the tuple-index lookup has the same division problem, but I suspect not since I think it should only need the multiplications.

The array was contiguous then CArray directly used the linear index (and no division/modulo/multiplication)

This should be fairly easy to do

I will allow this PR to go to the master branch while I review #3184. This will allow having some performance benefits right now.
Jenkins, test this please

Jenkins CI test (for commit f151fc744e68dab877b14e89c63dfe681e9cf7fd, target branch master) succeeded!


Fix port selection bug

Old conditional would not result in port 0 being selected if specified by the user.

https://github.com/Dragon2fly/logger_tt/issues/9

Hi @AlphonsG
Please add the test for your pull request.
You can refer to this previous test , set the port to 0 and try out.

Hello, I tried writing a test based on the one you linked, but it was failing due to the way the logging is implemented. For example, if we have port 0 assign an unused port to the logger, then if you reinitialise that logger in a spawned process (specifying port 0 again), then you won't log to the same address as the logger in the parent process. I tried passing the parent logger to the child as an argument, but nothing was logged in the child process. It seems the "fix" would need to be a bit more involved than I'd initially thought.
For anyone wanting to assign an unused port to logger_tt, I suggest they just determine the port number first and then pass that to logger_tt, for example:
with socket.socket() as s:
    s.bind(('', 0))  # bind to a free port
    port = s.getsockname()[1]

then pass the port to setup_logging.
Perhaps it can be added to the documentation then that assigning port 0 to logger_tt actually assigns port handlers.DEFAULT_TCP_LOGGING_PORT?
Thanks for requesting a test for this by the way, it would've caused issues if merged.


Codemirror integration is broken after v0.10.2 update

deprecation highlighting and type information are missing.
v0.10.1

after update to v0.10.2

Thanks @OlegIlyenko - I'll take a look now.

@OlegIlyenko before fixing this I'll need to update a bunch of dependencies first, in graphql-language-service and codemirror-graphql. I'm on this though - will PR out soon.

Annnd 4cca03eb02df16215e9c28bd24d537bdfbeb4cc1 fixes it! Thanks for the report!

@asiandrummer Thanks a lot for fixing it! 🏆


kubelet port 10250 not available for pods

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
Preface: I have migrated a cluster from Calico to Cilium. Switched completely to eBPF mode. Removed all calico and kube-proxy components. Policy enforcement is set as 'default', meaning by default communications are allowed. Also enabled host firewall, but no cluster wide / host policies are present so far. Routing mode is left default - encapsulation. Full final values file will be attached in the end.
Issue: After the move, the communication to kubelet port 10250 to scrape metrics got broken. Neither metrics-server, nor prometheus pods can connect to this endpoint to collect data.
The error that metrics-server prints during the failure:
E0731 09:18:55.370578       1 scraper.go:140] "Failed to scrape node" err="Get \"https://<IP_ADDRESS>:10250/metrics/resource\": context deadline exceeded" node="wallet7"

Things tried:

Removed all netpol and cnp resources in kube-system namespace to make sure metrics server is unrestricted.
Stopped UFW on the nodes to make sure it doesn't affect it. In the setup, UFW doesn't restrict backnet communications at all, all k8s nodes communicate with no blocking policies on OS level.
hubble observe to port 10250 show traffic is forwarded and not dropped.
Tried adding allowing CNP that didn't change anything:

spec:
  egress:
  - toEntities:
    - host
    - remote-node
  endpointSelector:
    matchLabels:
      app.kubernetes.io/name: metrics-server

Tried to tcpdump traffic on the node, it shows that the packet reaches cilium_net interface (for the node where both metrics-server and target kubelet reside). But confirmed with strace that kubelet pid does not receive this connection. So it gets lost somewhere between cilium_net and host routing.
It's important to note that communication to kube-apiserver (node ip and port 6443) works fine, but it's a pod running in hostNetwork mode on the same node.

Can I ask for any tips/hints what could cause such behavior? Or any troubleshooting items to try?
Cilium Version
cilium-cli: v0.15.3 compiled with go1.20.4 on darwin/arm64
cilium image (default): v1.13.4
cilium image (stable): v1.14.0
cilium image (running): 1.13.4

Kernel Version
5.15.0-78-generic

Host OS is Ubuntu 22.04
Kubernetes Version
Server Version: version.Info{Major:"1", Minor:"25", GitVersion:"v1.25.6", GitCommit:"ff2c119726cc1f8926fb0585c74b25921e866a28", GitTreeState:"clean", BuildDate:"2023-01-18T19:15:26Z", GoVersion:"go1.19.5", Compiler:"gc", Platform:"linux/amd64"}

Sysdump
cilium-sysdump-20230731-161450.zip
Relevant log output
tcpdump on cilium_net interface
root@wallet7:~# tcpdump -n -i cilium_net 'port 10250'
tcpdump: verbose output suppressed, use -v[v]... for full protocol decode
listening on cilium_net, link-type EN10MB (Ethernet), snapshot length 262144 bytes
09:36:04.186886 IP <IP_ADDRESS>.46150 > <IP_ADDRESS>.10250: Flags [S], seq<PHONE_NUMBER>, win 64860, options [mss 1410,sackOK,TS val<PHONE_NUMBER> ecr 0,nop,wscale 7], length 0
09:36:05.293010 IP <IP_ADDRESS>.40826 > <IP_ADDRESS>.10250: Flags [S], seq<PHONE_NUMBER>, win 64860, options [mss 1410,sackOK,TS val 285850807 ecr 0,nop,wscale 7], length 0
09:36:06.294836 IP <IP_ADDRESS>.40826 > <IP_ADDRESS>.10250: Flags [S], seq<PHONE_NUMBER>, win 64860, options [mss 1410,sackOK,TS val 285851809 ecr 0,nop,wscale 7], length 0

hubble observe:
root@wallet7:/home/cilium# hubble observe --to-port 10250 --to-ip <IP_ADDRESS> | tail -10
Jul 31 09:37:45.562: observability/prometheus-kube-prometheus-stack-prometheus-0:50584 (ID:53295) -> <IP_ADDRESS>:10250 (host) to-stack FORWARDED (TCP Flags: SYN)
Jul 31 09:37:49.146: kube-system/metrics-server-6bd8d699c5-xjcc6:39112 (ID:15550) -> <IP_ADDRESS>:10250 (host) to-host FORWARDED (TCP Flags: SYN)
Jul 31 09:37:49.146: kube-system/metrics-server-6bd8d699c5-xjcc6:39112 (ID:15550) -> <IP_ADDRESS>:10250 (host) to-stack FORWARDED (TCP Flags: SYN)
Jul 31 09:37:49.503: observability/prometheus-kube-prometheus-stack-prometheus-0:57470 (ID:53295) -> <IP_ADDRESS>:10250 (host) policy-verdict:L3-Only EGRESS ALLOWED (TCP Flags: SYN)
Jul 31 09:37:49.503: observability/prometheus-kube-prometheus-stack-prometheus-0:57470 (ID:53295) -> <IP_ADDRESS>:10250 (host) to-host FORWARDED (TCP Flags: SYN)
Jul 31 09:37:49.503: observability/prometheus-kube-prometheus-stack-prometheus-0:57470 (ID:53295) -> <IP_ADDRESS>:10250 (host) to-stack FORWARDED (TCP Flags: SYN)
Jul 31 09:37:56.570: observability/prometheus-kube-prometheus-stack-prometheus-0:57470 (ID:53295) -> <IP_ADDRESS>:10250 (host) to-host FORWARDED (TCP Flags: SYN)
Jul 31 09:37:56.570: observability/prometheus-kube-prometheus-stack-prometheus-0:57470 (ID:53295) -> <IP_ADDRESS>:10250 (host) to-stack FORWARDED (TCP Flags: SYN)
Jul 31 09:37:56.876: kube-system/metrics-server-6bd8d699c5-xjcc6:33320 (ID:15550) -> <IP_ADDRESS>:10250 (host) to-host FORWARDED (TCP Flags: SYN)
Jul 31 09:37:56.876: kube-system/metrics-server-6bd8d699c5-xjcc6:33320 (ID:15550) -> <IP_ADDRESS>:10250 (host) to-stack FORWARDED (TCP Flags: SYN)

Anything else?
cilium installation values:
bpf:
  hostLegacyRouting: false
  masquerade: true
cluster:
  name: cluster.local
cni:
  customConf: false
  uninstall: false
hostFirewall:
  enabled: true
hostPort:
  enabled: true
hubble:
  relay:
    enabled: true
    tolerations:
    - key: node-role.kubernetes.io/control-plane
      operator: Exists
  ui:
    enabled: true
    frontend:
      server:
        ipv6:
          enabled: false
    tolerations:
    - key: node-role.kubernetes.io/control-plane
      operator: Exists
ipam:
  mode: cluster-pool
  operator:
    clusterPoolIPv4PodCIDRList:
    - <IP_ADDRESS>/16
kubeProxyReplacement: strict
k8sServiceHost: <IP_ADDRESS>
k8sServicePort: 6443
operator:
  replicas: 1
  unmanagedPodWatcher:
    restart: true
policyEnforcementMode: default
serviceAccounts:
  cilium:
    name: cilium
  operator:
    name: cilium-operator
tunnel: vxlan
tunnelPort: 8473

Code of Conduct

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

Root cause: IPAddressAllow inside /etc/systemd/system/kubelet.service that limited communications to kubelet. This was a result of cluster security hardening.


Temporary fix for #1204

It's temporary! It just prevents the crash, it doesn't fix the issue

Would be better to have a proper fix in create fabric/porting lib for this so it can come out alongside the patch f PRs


DB password should not be mandatory (if postgres credential uses the unix account directly)

On Debian, it's possible to create a postgres user without password, the authentication is done directly with the unix credential (ex: if the user "citydb" starts pgsql and the postgres user "citydb" exists, then the
user can have acces to his database directly).
The java importer/exporter imposes to enter a db password, the password should be optional in this case.

A database connection password is now optional (1966a46ab868efb4fa82147ec161dfdbd499c74c).
Can you please verify whether this commit already solves your issue? Simply download the source and run the build.xml with Ant to compile the Importer/Exporter tool.

Hi Claus, thanks for your speedy feedback.
I downloaded your patch and tested it, but sadly it will not solve my problem but I think I know why...
The error I get is
The server requested password-based authentication, but no password was provided
After some digging I found out that I use the "peer" authentication which uses unix socket to talk
to the linux kernel to get the credential. The Java JDBC driver only supports TCP connection (which needs a password), so the authentication without password will not work in this context (until a native JDBC is available...)
Postgres JDBC doc
Sorry for the trouble, and thanks for your work in any case.

I see, too bad. Thanks for pointing to the relevant chapter of the PostreSQL documentation.


Consider adding Open Data Capture playground example to docs

Hi again,
We are creating an open-source platform for data collection (Open Data Capture) that includes support for interactive tasks. As part of the platform, we have a browser-based code editor that supports implementing arbitrary interactive tasks using various libraries (including JsPsych). I think this could be helpful for users to get started with JsPsych (even if they are not using ODC). It allows users to get started immediately with modern tools and intelisense (you can have a look at our JsPsych example here.
Let me know what you think!

Hey @joshunrau,
Happy to think about this. We're going to be doing some documentation overhauls over the next 6-12 months, and I think adding more information about 3rd party integrations and resources will be a huge piece of that. We have a few urgent priorities to handle first, but will come back to this asap.

Hey @joshunrau,
Happy to think about this. We're going to be doing some documentation overhauls over the next 6-12 months, and I think adding more information about 3rd party integrations and resources will be a huge piece of that. We have a few urgent priorities to handle first, but will come back to this asap.

Great!


Migrate from 'Travis CI' to 'GitHub Actions' (...)

Changes

Move codecov config into .github.
Convert fromtravis to GitHub Actions runners.
Update gitignore for package building results ignoring.
Cleanup Makefile:

... We will return docs some day as a make command ...

Update README.
Unpin pylint:

... update any pylint error reports.

Update setup.py for further cleanup
Update touched copyright dates.
Fix up any type hint / code smell issues during PR.
Upgrade version checker via rip from this commit

Notes
Why not have python3.9 ?
PyLint was not happy:
make pylint
pylint --rcfile=./.pylintrc --reports=y --output-format=text nistbeacon
************* Module nistbeacon.nistbeaconvalue
nistbeacon/nistbeaconvalue.py:373:41: E1136: Value 'Optional' is unsubscriptable (unsubscriptable-object)
************* Module nistbeacon.nistbeacon
nistbeacon/nistbeacon.py:61:43: E1136: Value 'Optional' is unsubscriptable (unsubscriptable-object)

See also:

http://pylint-messages.wikidot.com/messages:e1136
https://github.com/PyCQA/pylint/issues/3882

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@43e0c3d). Click here to learn what that means.
The diff coverage is 91.66%.

@@            Coverage Diff            @@
##             master      #36   +/-   ##
=========================================
  Coverage          ?   99.47%
=========================================
  Files             ?        4
  Lines             ?      191
  Branches          ?        0
=========================================
  Hits              ?      190
  Misses            ?        1
  Partials          ?        0

Impacted Files
Coverage Δ

nistbeacon/nistbeacon.py
97.95% <83.33%> (ø)

nistbeacon/nistbeaconcrypto.py
100.00% <100.00%> (ø)

nistbeacon/nistbeaconvalue.py
100.00% <100.00%> (ø)

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 43e0c3d...b7864f2. Read the comment docs.

I might have broken my CodeCov lol 😅


Unlockable numbers numbers do not match

I was checking the drop page with waifu minter, and I'm not sure why these numbers are like this:
Here you can see the total available items: 224/300

But if you open the collection, you can see only 74 items minted.

Its bit confusing - what are those 224/300 numbers for?

74 minted items

*76

Thanks, you are right : )

@JustLuuuu, those are available nfts to be minted - the whole drop consists of 300 nfts. When the 0/300 is reached, there are no nfts left.


updated docstrings & contributing.ms

written docstrings for all code files.
updated the contributing.md file

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (173a6fd) 80.12% compared to head (d947a23) 80.16%.

:exclamation: Current head d947a23 differs from pull request most recent head f01bcd0. Consider uploading reports for the commit f01bcd0 to get more accurate results

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #52      +/-   ##
==========================================
+ Coverage   80.12%   80.16%   +0.03%
==========================================
  Files          29       29
  Lines        2239     2238       -1
==========================================
  Hits         1794     1794
+ Misses        445      444       -1

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


[ja] Translate CNCF Cloud Native AI white paper into Japanese

Background
We have started Japanese localization in #147. This will be a long journey, but we have decided to begin with the l10n of "CNCF Cloud Native AI White Paper". (Thanks @kenta-iijima!!)
Feature Description

Translate  "CNCF Cloud Native AI White Paper" into Japanese

Note
This White Paper is approximately 700 lines long. Should we divide it into several parts to work on it? (I think we should divide it into a first half and a second half.)

First half: From the beginning of the file to ## Challenges For Cloud Native Artificial Intelligence
Second half: From ## Path Forward with Cloud Native Artificial Intelligence to the end of the file

ref #150


Querying Requested Extras in build_ext

Hi,
I am building an external CMake extension with
from setuptools import setup, Extension
from setuptools.command.build_ext import build_ext

class CMakeExtension(Extension):
    def __init__(self, name, sourcedir=''):
        Extension.__init__(self, name, sources=[])
        self.sourcedir = os.path.abspath(sourcedir)

class CMakeBuild(build_ext):
    def run(self):
        # ...

        for ext in self.extensions:
            self.build_extension(ext)

    def build_extension(self, ext):
        # ...

# ...
setup(
    # ...
    ext_modules=[CMakeExtension('openpmd_api')],
    extras_require={
        'mpi': ['mpi4py'],
    },
    # ...
)

and would like to query the user-requested extras during the build_extension step, in order to find out if the extra 'mpi' was requested (via pip install .[mpi]) or not. Is there a way to query this?
Full example: setup.py

I may be displaying my ignorance of how this all works here, but I think the specified extras are not intended to be build flags, but optional install time dependencies. I'm not sure that setuptools ever gets that information, much less uses it for anything. I think extras are basically just install-time metadata about additional features that can be enabled in the project, not build-time flags.
I think the most "standard" way to do this sort of thing (and I admit it's not great UX) is to factor out the things that have your extra (e.g. mpi) as a build-time dependency into their own packages that install into your project's namespace. So the [mpi] extra introduces a dependency on mypkg.mpi_extension, which has a hard build dependency on mpi.

Thanks for the help! Urgh, I feared that when checking the self.__dict__ of setuptools.Extension and found no traces... It would be really complicated and verbose to implement your suggested work-around in my case...
Can I maybe hook into some call inside setup() to set a global before building the extension or so?

@ax3l I do not think that "extras" are intended to control additional functionality in the build, they are intended to allow you to specify dependencies for optional runtime features (see the documentation). I could certainly be wrong because I don't know much about the history of the "extras" feature, but it's really about declaring metadata for the front-end.
At least the way the build tools currently work, the idea is that at build time you would build everything you support, and at install time those features would only actually be usable if you had specified the extra options. This means that either you make a hard build-time requirement of mpi, regardless of the extra options, but make it optional at install time, or you separate out the parts that require mpi into a separate package that itself has a hard requirement of mpi.

"extras" are intended to control additional functionality in the build, they are intended to allow you to specify dependencies for optional runtime features

I agree, looks the same to me. Unfortunately, "everything can be checked at runtime" is a very pythonic viewpoint and doesn't work well with all the binary (e.g. C)-extensions that get lot of their features through build-time configuration.
Anyway, that just means I can't currently express build-time variants in the pip/setuptools canon. I will control my build with environment variables instead. Popular projects have done this for the same reasons since a long time, e.g. h5py and I will just do the same.
Thanks for your help still, too bad extras are not deeper integrated to allow such workflows :)

Here's my (late) response as posted in the Gitter inquiry (I haven't read the thread above).

That’s not possible as far as I know. If the current project depends on it to decide how to build itself, then it’s not really an extra (as intended). Extras are intended for install-time dependency resolution, not build-time. You’ll want to structure your project so it can support running with and without the extras at run-time… maybe that means building with and without the libs the extras might require, or maybe it means pushing that functionality into the extras themselves.

Closing as out of scope.


tweak letter error responses

made the example rate limit not use team key (since that's not allowed for letters)
changed the team api key and trial mode error messages to be more accurate

#yolo merge


Vulnerabilities in Docker images

Hello!
I decided to scan docker images, that have been creted after docker-compose up -d command. So, Snyk've found multiple vulnerabilities  in datalens images. In attachment you can find full scan results. The great concern is about critical vulnerabilities with RCE. Are they affect to current version of datalnes? Is there any plans to update old components in the future?
Thank you!
datalens-us_0.96.0.txt
datalens-ui_0.795.0.txt
datalens-data-api_0.2037.0.txt
datalens-control-api_0.2037.0.txt

Hi. Most of the triggers listed in attached files are related to various packages that are not directly involved with the service itself (like vim). We'll probably switch to more lightweight base images with fewer dependencies in the future.
We are regularly analyse our dependencies, but we'll take a thorough look at your listing too, in case there is really something that can be exploited.
P.S. Just in case if you'll want to report some confirmed security problem in the future, please take a look at SECURITY.md

The pull request describes what has been updated https://github.com/datalens-tech/datalens-backend/pull/48 if needed.
Reports are the attached. These files contain scan results for the new images. There remain two vulnerabilities marked as high risk:

one does not affect us at all, because we do not use the vulnerable part of the library
the second can cause file parser fail in some situations, we'll look into it later

snyk-data-api-report.txt
snyk-control-api-report.txt
All vulnerabilities, including these two, which we can still correct (i.e., those that did not come with the base image of Ubuntu and somehow affect us), are additionally described below and why we did not update immediately
Upgrade<EMAIL_ADDRESS>to<EMAIL_ADDRESS>to fix ✗ Missing Cryptographic Step (new) [Medium Severity][https://security.snyk.io/vuln/SNYK-PYTHON-CRYPTOGRAPHY-6036192] in<EMAIL_ADDRESS>== Not vulnerable, will update later
Upgrade<EMAIL_ADDRESS>to<EMAIL_ADDRESS>to fix ✗ Information Exposure [Medium Severity][https://security.snyk.io/vuln/SNYK-PYTHON-REQUESTS-5595532] in<EMAIL_ADDRESS>== Not vulnerable, will update later
Upgrade<EMAIL_ADDRESS>to<EMAIL_ADDRESS>to fix ✗ Double Free [Medium Severity][https://security.snyk.io/vuln/SNYK-PYTHON-UJSON-2940619] in<EMAIL_ADDRESS>✗ Improper Handling of Syntactically Invalid Structure [Medium Severity][https://security.snyk.io/vuln/SNYK-PYTHON-UJSON-2942122] in<EMAIL_ADDRESS>✗ Out-of-Bounds Write [High Severity][https://security.snyk.io/vuln/SNYK-PYTHON-UJSON-2359034] in<EMAIL_ADDRESS>== Breaks current behavior, need to consider, the vulnerability  does not affect users.
Upgrade<EMAIL_ADDRESS>to<EMAIL_ADDRESS>to fix ✗ Inefficient Algorithmic Complexity (new) [Medium Severity][https://security.snyk.io/vuln/SNYK-PYTHON-WERKZEUG-6035177] in<EMAIL_ADDRESS>✗ Denial of Service (DoS) (new) [High Severity][https://security.snyk.io/vuln/SNYK-PYTHON-WERKZEUG-6041510] in<EMAIL_ADDRESS>== Not vulnerable
Pin<EMAIL_ADDRESS>to<EMAIL_ADDRESS>to fix ✗ Information Exposure Through Sent Data [Medium Severity][https://security.snyk.io/vuln/SNYK-PYTHON-URLLIB3-5926907] in<EMAIL_ADDRESS>✗ Information Exposure Through Sent Data (new) [Medium Severity][https://security.snyk.io/vuln/SNYK-PYTHON-URLLIB3-6002459] in<EMAIL_ADDRESS>== Seems not vulnerable, medium, potentially breaking changes, will update later


Spam filters

Some bad guys write just one or two words A LOT to recive 2 or 3 points.
Like "Fantastic! Fantastic! Fantastic!".
:(

Naturally ;) Whenever you make rules, people will try to game them. (Is that Somebody's Law yet? If not, I claim it!)
My first thought was: we could score each comment based on its gzipped size using gzcompress. Such repetitive comments will compress really well. However, then people will just mash their keyboard or even use an actual PRNG. In the end, it's just pathetic behaviour, which like most social problems is difficult or impossible to solve with technical means.
If you could post links to the offending users, we can blacklist them.

Because comments they've made show up on their page as well, it's fairly obvious who's done this sort of stuff, and thus easy to call out when reviewing their game.

Hmm.. gzip idea looks surprisingly. I started to think line algorithm, but it's can works.
I looked all posts of [http://feedback.ld.intricati.com/?event=ludum-dare-36&uid=54139](this man), but found only one semi-illegal comment (for me). So I don't think what we should blacklist he.
I agreed, it's wrong way to fix a problem with algorithms. Maybe, it can be solved by community-self-moderating system, as part of likes-dislikes system. If this project will be used for LD in the future. Anyway, thank you for comfortable site.

Yes, a like/dislike system (or even just a Report button) would help a lot. But that's for the main Ludum Dare site to implement, I think.


Change Mount.from_local_python_packages remote path to /root

Describe your changes
Was previously /pkg, which differed from where auto-mounted packages were put (/root). This makes it consistent, so that explicit mounting is put at the same location as auto-mounting, which is probably what users want most of the time, e.g. when manually adding static content to packages that isn't being picked up by the auto mounting logic.
Fixes MOD-2102
Backward/forward compatibility checks
If users mount packages and then refer to their location using /pkg this would be a breaking change once they upgrade to this new client version.
Changelog

Mount.from_local_python_packages now places mounted packages at /root in the Modal runtime by default (used to be /pkg). To override this behavior, the function now takes a remote_dir: Union[str, PurePosixPath] argument.

Maybe this motivates a minor version bump on the client version


Set up a Wikibase instance for enKORE testing purposes

This could help with testing in the context of

data models of hypotheses, as per

#12

import / export workflows, e.g. around OAI-PMH, as per

#10

other issues

Here is a library used for syncing between two Wikibase instances: https://github.com/the-qa-company/WikibaseSync .
It is in use and developed by the EU Knowledge Graph.

Some pointers about strategic planning in the Wikibase ecosystem: https://loomio.rhizome.org/d/RB2QztuD/strategy-for-the-wikibase-ecosystem-2021

A promising option to do this seems to be the upcoming Wikibase cloud, here announced for "around January" 2022.

The timeline for the launch of Wikibase Cloud has been given in some more detail today as "by the end of the first quarter of 2022", with streamlined migration from WBStack. See the write-up at
https://addshore.com/2022/02/wbstack-close-and-migration/ for details.


'SkiaSharp' 2.88.1-preview.1 has a known high severity vulnerability

Sounds like it should be updated

I will have a look at it. There are a few things which need an update here :sweat_smile:


[Frontend]: I just added articles created in april to their var…

…ious section of the table

@Aysha-py  Thanks for your contribution.
Could you fix the conflict?


Update Cancun Besu Status

Update MCOPY and SELFDESTRUCT for Besu

Be honest, it was because @jflo had a cute animal picture and I didn't.  That's what I get for ignoring the template. ;)


Read config value in view.

I have a Blog module and i have a config file in it . i want to display the value of config on the view . but i am not able to do it ..
i tired  .. {{ config('blog::config.name') }}
{{ Config::get('blog::config.name') }}
didnt work. pls can anyone help me with this ?

Make sure your module service provider publishes and merges the config file with a Laravel. For this,
Publish the config file using in your module service provider under registerConfig method:
           module_path($this->moduleName, 'Config/name.php') => config_path('name.php'),
       ], 'config');```

And merge the config file using :
```$this->mergeConfigFrom(
           module_path($this->moduleName, 'Config/name.php'), 'name'
       );```

Now, you can access the config file by:
``` config("name.key") ```


ResponsiveWrapper is not working

when i use ResponsiveWrapper it gives an error that it is an undefined class, i have tried it with .builder but still not working, but when i use ResponsiveBreakpoints then it works.

There is no ResponsiveWrapper in the latest version. See the migration guide:
https://github.com/Codelessly/ResponsiveFramework/blob/master/migration_0.2.0_to_1.0.0.md

There is no ResponsiveWrapper in the latest version. See the migration guide:
https://github.com/Codelessly/ResponsiveFramework/blob/master/migration_0.2.0_to_1.0.0.md
So, the library is not offering the most important thing, the auto Scale? Now is the same to put a sizedBox with a burned value?

There is no ResponsiveWrapper in the latest version. See the migration guide:
https://github.com/Codelessly/ResponsiveFramework/blob/master/migration_0.2.0_to_1.0.0.md

adssadasdasdasd

@F7085 No, it provides autoscaling like it used to, but now it is set up differently - using ResponsiveScaleBox and ResponsiveValue instead of ResponsiveWrapper, as it is described in the guide.


fix(GUI): correct relative notification icon path

We update the relative icon path to the correct relative path containing
the Etcher icon.
See: https://github.com/resin-io/etcher/issues/1443
Changelog-Entry: Correct the relative notification icon path.

@Shou can you rebase this to the latest version of master to pick up the fix in #1471 please?

Done.


Fix invalid yaml 🤦♂ in the node-ci workflow

Summary:
ugh
I wonder if we can set up prettier or eslint for our .yml files? That would at least make these errors more obvious.
Issue: XXX-XXXX
Test plan:
🤞

@jaredly  Looks like the jest action doesn't like having no files.

oh it doesn't like it when I reference a nonexistent step 😭 fixed 🤞


Spyglass hide blocks of VanillaX

https://github.com/CLADevs/VanillaX/issues/167

Okay i update it

Okay i update it

Thx <3

VanillaX good plguins

Okay i update it

Thx <3

Review 1.0.2 fix or not


71360 illegal hardware instruction  python main.py

Macbook M1 2022
everything required is installed.
(base) ➜  ProphitBet-Soccer-Bets-Predictor git:(main) ✗ python main.py [1]    71360 illegal hardware instruction  python main.py

I'm having the same problem here. I also have a Mac. Found a solution yet?

Try python3 instead of python

Still same error :(


USBDevice4Cube Project Initialization

Hi,
I setup a TrueStudio project with CubeMX and tried to integrate the USBDevice Library.
I'm not sure I correctly followed instruction detailed in [https://github.com/IntergatedCircuits/USBDevice4Cube].
In the attached TrueStudio Project, I have a compilation error and I don't reach to solve it.
Project.zip
I would like to try this library to mount MSC + HID class in a custom F7 board.
Could you help me please ?

Hello,
Compilation error is solved.  Sorry it was a silly mistake.
Thanks to old issues and related solutions, I reach mounting MSC+ HID without error in Windows.
A victory for beginners !
Thanks a lot for sharing this Library.


Fix flipped

Flip() requires aFlipLeftRight (it would be cool to parameterize this in the future)
get flipped from props
use XOR to simplify the code

👍 for v5 compatibility


Update dependencies

From my brief experience with golang, its better to have vendor directory checked in with repo for reliably reproducible builds
I had seen instances where the dependency repo changed or even removed breaking the future builds


remove unneccesary astro glob

Follow up to #365, I don't know if this actually helped our perf in dev, but it can't hurt :) Passing props from getStaticPaths is the official way to pass data down to the page so that you don't need to re-request it a second time.
There are two more perf improvements that I'd like to look into, separate from this, but that we appear to be blocked on:

Removing [slug] and [...slug]: Tony is planning to look into moving docs.astro.build -> astro.build/docs next week, which we should combine with a big "finalize our slugs and remove all of our old redirects".
Vite seems to be building all of our markdown files 3 times, during dev. No idea why this is, but it will need investigation!

cc @delucis

Hmm, this is a weird bug:
 error   Unable to render SidebarToggle!

  This component likely uses @astrojs/react or @astrojs/preact,
  but Astro encountered an error during server-side rendering.

@delucis possibly related to this? https://github.com/withastro/astro/issues/2480

I actually tried this approach initially! But there appears to be a bug with framework components when you pass the content this way. (Errors on build but appears to work in dev, IIRC.)
My wild guess was: Astro uses imports to know to load various assets. When the "import" (via Astro.glob) is inside getStaticPaths some of these don't get picked up. I noticed it with this error but also certain (component-specific, I think) styles.
Obviously would be good to fix this, but FWIW I don't think I actually saw a huge perf difference between the two approaches. Maybe the glob is cached or something. The bigger issue was https://github.com/withastro/docs/pull/365/commits/adb545da17a43e0c6f8626f8676696a7d9eba961

@delucis possibly related to this? withastro/astro#2480

Hmm, the errors I was getting on that issue were quite different although I don't want to rule it out that they share something.

The bigger issue was adb545d

Agreed, and to make matters worse I think that's being compounded by the same "why is Vite building every markdown file 3 times" issue 🤦

As this is still failing, I’ve marked it as a draft to help us triage the PRs tab. I’d love for this to work, so keeping this around for the glorious future in which the bug is fixed.


cmd/asm: new x86 instructions

We've had a request on golang-dev for
LDDQU
PSLLDQ
PSRLDQ
PMOVZXBD
PMULLD
PHADDD
PADDD
CVTDQ2PS

Also HADDPS, HADDPD.


Initial version of the code for people to look at

A reference to the issue / Description of it
See Automation to provide info for new onboarders#3451 got full details
How does this PR fix the problem?
Sends the email once the request is closed
How has this been tested?
Used act to test via "act -W 'email-requester-onboarding-close.yml'"
Initial errors corrected in updated version.
Deployment Plan / Instructions
No impact to other services
Checklist (check x in [ ] of list items)

[x] I have performed a self-review of my own code
[x] All checks have passed

Additional comments (if any)
{Please write here}

Code amended to correct an error on the if statement.


➕ [RESOURCE] - ADD RESPONSIVENESS to THE NAVBAR

Idea Contribution

[X] I have read all the resource request issues.
[X] I'm interested in working on this issue
[X] I'm part of GSSOC organization

Where do you want to add the resource? Specify the category and section.
Want to add more responsiveness to the navbar
Provide the URLs of the resources you are adding
No response
Any alternative approaches/features
No response
Additional Context
No response
Code of Conduct

[X] I follow the CONTRIBUTING GUIDELINE of this project.

We're currently redesigning the site.
Read #998


Increase buffer size to 4096 for net_dns_record requests

Example query results

Results
select value from net_dns_record where domain = 'github.com' and type = 'TXT'

Hi @cbruno10 - what is the ETA to get this pull request approved?

Hey @massyn , sorry for the delayed response. I think instead of increasing the buffer size, we should instead look to retry with TCP if we get a truncated response, similar to how nslookup does it. It's on our radar to implement, but we haven't had a chance yet.
If you're interested in attempting this update in this PR, please let us know and we're happy to help along the way.
One note I'll mention is we currently use a utility retryHydrate function (https://github.com/turbot/steampipe-plugin-net/blob/main/net/table_net_dns_record.go#L273), which is defined in https://github.com/turbot/steampipe-plugin-net/blob/main/net/utils.go#L183. So we should continue to use this, but we shouldn't wrap the UDP + TCP attempts in the same retryHydrate, since if we know the response is truncated, we don't want to retry the UDP request with each TCP request.

@massyn In the meantime, as a workaround you can use this branch and build locally wherever you need the plugin in order to override the default buffer size. If you run into other technical issues with this workaround though, please let us know.

@massyn I'm closing this PR for now, as I'm hesitant to increase the buffer size to 4096 for all requests. I believe the better solution is to implement a proper TCP fallback mechanism if we discover that the UDP request response was truncated as I mentioned in https://github.com/turbot/steampipe-plugin-net/issues/56#issuecomment-1419866875.
This item will be in our backlog, so we may not get to it in the near future. If you'd like to try implementing it, please feel free to do so and we'll be happy to help. Thanks!

Hey @cbruno10 - I've got the workaround branch already running.  If this is not getting fixed in the short term, I think the better approach for me will be top stop using this plugin, and revert to using a python script instead, so I can have a reliable data source.

Hi @massyn , this item is still on our TODO list, but we have some other items in front of it unfortunately. If the workaround branch works is working for you, then the requests should still complete OK; however, I understand if using a local plugin version is not feasible for any reason.
We'll update the original issue once we start working on implementing the backoff solution.


Willow/ Home Assistant Websocket error

          Following all the suggestions I have gotten Willow Flashed across!

But am faced with the following error when I monitor
" (04:20:13.436) WILLOW: [ + ] HTTP client HTTP_STREAM_ON_REQUEST, length=4096
I (04:20:13.439) WILLOW: AUDIO_REC_VAD_END
Total bytes written: 45056
Total bytes written: 47104
I (04:20:13.509) AUDIO_ELEMENT: IN-[http_stream_writer] AEL_IO_DONE,-2
I (04:20:13.510) WILLOW: [ + ] HTTP client HTTP_STREAM_POST_REQUEST, write end chunked marker
I (04:20:14.123) HTTP_CLIENT: Body received in fetch header state, 0x3d955d93, 41
I (04:20:14.124) WILLOW: [ + ] HTTP client HTTP_STREAM_FINISH_REQUEST
I (04:20:14.128) WILLOW: Got HTTP Response = {"text":"Turn on light.","language":"en"}
I (04:20:14.138) WILLOW: sending command to Home Assistant via WebSocket: {
"end_stage":	"intent",
"id":<PHONE_NUMBER>,
"input":	{
"text":	"Turn on light."
},
"start_stage":	"intent",
"type":	"assist_pipeline/run"
}
I (04:20:14.245) WILLOW: home assistant response_type: error
I (04:20:14.250) WILLOW: received run-end event on WebSocket: {
"id":<PHONE_NUMBER>,
"type":	"event",
"event":	{
"type":	"run-end",
"data":	null,
"timestamp":	"2023-05-29T09:20:14.375267+00:00"
}
}
I (04:20:14.263) AUDIO_THREAD: The play_tone_err task allocate stack on external memory
I (04:20:16.165) AUDIO_ELEMENT: [http_stream_writer] AEL_MSG_CMD_PAUSE
I (04:20:24.271) WILLOW: Wake LCD timeout, turning off LCD
"
Originally posted by @MathewJH1 in https://github.com/toverainc/willow/issues/60#issuecomment-1566834175

found the fault was user error

:) Glad you found the issue Mathew

@MathewJH1 what was the solution? I have the same problem.

So the problem was home assistant Assist preffered assistant selected with not english language. Changing it to english made willow work. Then changing it to polish made it not work again.


test_array_constructor_return crashes cpu-only omniscidb server 5.4

2020-07-01T09:59:36.097923 F 26936 NativeCodegen.cpp:204 Stored value type does not match pointer operand type!
  store i1 true, i8* %13
 i8Stored value type does not match pointer operand type!
  store i1 true, i8* %28
Aborted (core dumped)

OmniSci Version: 5.4.0dev-20200701-9b87e0f99b

xref:
https://github.com/xnd-project/rbc/issues/81
https://github.com/xnd-project/rbc/issues/112
https://github.com/xnd-project/rbc/issues/113
https://github.com/xnd-project/rbc/issues/115


Native Federation doesnt support PWA

When you install angular PWA and then native federation (v. 17.1.1), is not compatible together.
Steps to reproduce

prepare shell and mfe1 projects
install PWA into the shell application ( ng add @angular/pwa)
install native federation for shell and mfe1 and do basic native federation setup
run shell as PWA application. You can see Service Worker, also "install application" icon
change shell component code
press F5 to see how PWA will notify us about code change in shell project.

Here you can see issue in the console, when service worker in the shell register changes in the code:
Failed to install app version 'ba26c71599a1f0659db57d9bfd88189cf776562a': Hash mismatch (cacheBustedFetchFromNetwork):
https://my-website.com/shell/index.html: expected 42f3a2438c0057d38ce5056b3aa640913e30a3e2, got a8909d252e746f6123a05e4ab0d40c8750dead2b (after cache busting)
Error: Hash mismatch (cacheBustedFetchFromNetwork): https://my-website.com/shell/index.html: expected 42f3a2438c0057d38ce5056b3aa640913e30a3e2, got a8909d252e746f6123a05e4ab0d40c8750dead2b (after cache busting)
    at PrefetchAssetGroup.cacheBustedFetchFromNetwork (https://my-website.com/shell/ngsw-worker.js:479:21)
    at async PrefetchAssetGroup.fetchFromNetwork (https://my-website.com/shell/ngsw-worker.js:454:19)
    at async PrefetchAssetGroup.fetchAndCacheOnce (https://my-website.com/shell/ngsw-worker.js:433:21)
    at async https://my-website.com/shell/ngsw-worker.js:538:9
    at async https://my-website.com/shell/ngsw-worker.js:524:9
    at async https://my-website.com/shell/ngsw-worker.js:524:9
    at async https://my-website.com/shell/ngsw-worker.js:524:9
    at async https://my-website.com/shell/ngsw-worker.js:524:9
    at async PrefetchAssetGroup.initializeFully (https://my-website.com/shell/ngsw-worker.js:523:7)
    at async https://my-website.com/shell/ngsw-worker.js:927:11

Yes, this is currently not supported. In general, it would be hard to make both worlds work together because the host's service worker doesn't know a thing about the remotes. Also, Angular's simple PWA support is a turn-key solution that assumes everything is known at compile time. If you really need PWA support + Federation, I would use sth like workbox.


Window is open and checkbox is checked added to ui.rs example

Added demonstration how to use egui::Window::open(self, &'open mut bool). Since I am a newcomer to rust I have been struggling with passing a mutable bool. Should be useful for other newcomers as well since closing or opening a window is such a common use case.
Hope that helps.

Yes, it can. But then the default state will be a closed window unless we provide a manual Default implementation for UiState. Is there a way to make is_open default to true and leave #[derive(Default)] on UiState?

Using only UiState now. Left default as is but introduced configure_ui_state startup function to set is_window_open to true.

can we merge it or is there something else to be fixed?

Merged. Thank you!


Update usage.md "Hello World" :|

"Hello World." That just seemed embarrassing ;p

@dphrag Thanks!


Flaky test for PsuedoRandomAddress

I tried to build the Herald demo app using:
$ git rev-parse HEAD
b08c291c5c8a403a07d93528fdeb183bd98a18d5
$ ./gradlew build

It failed running the tests:
> Task :herald:testDebugUnitTest

com.vmware.herald.sensor.datatype.PseudoDeviceAddressTests > testRandomBytes FAILED
    java.lang.AssertionError at PseudoDeviceAddressTests.java:47

https://github.com/vmware/herald-for-android/blob/b08c291c5c8a403a07d93528fdeb183bd98a18d5/herald/src/test/java/com/vmware/herald/sensor/datatype/PseudoDeviceAddressTests.java#L40
Looking at testRandomBytes it is not surprising -- there's no reason to expect that every byte of the result will change every time. I'd expect this test to fail about 21% of the time.
Similarly, the testSecureRandom is not in any way a test for (secure) randomness.
Additionally, please see https://github.com/vmware/herald-for-android/issues/90#issuecomment-737527900 -- why does the implementation of PsuedoRandomAddress need to be so complicated?

Thanks, this is a known issue with these initial tests. There is work ongoing to resolve this - see #81 . (I'm expecting a PR any moment with more tests provided). The bulk of that code has been used on prior projects, and so is well tested.
Also for the other closed issue, our code refers to a NIST document with advice for SHA1PRNG, amongst other items. Please refer to that NIST document for the rationale.
Please also remember we have to support a large number of devices and we have to do so in a way where the OS won't halt if the pool of entropy runs out - SecureRandom's default implementation on some phones does do this - causing any Bluetooth to potential fail if the phone sits there for a few hours (2-3 in our testing). For this reason we're looking to find some entropy elsewhere.
As you probably know, entropy is generally provided in many phones' SecureRandom implementations by moving the phone, writing to disc, interacting with the screen and so on. Especially older phones. This entropy does run out if the phone sits there, causing the SecureRandom call to block - effectively halting all BLe work.
We're looking at a way to determine a mechanism for creating an entropy pool from how Bluetooth physically reacts when in use, but will need to review this for suitability before deployment. Not a quick task as you can imagine.
If you have time please feel free to provide input on a way to generate enough randomness of a good enough quality (nothing is perfect) in the 6-byte pseudo device address without using a mechanism that halts Android phones, if you have time to look in to it? I have others looking in to it of course, but more heads are better than fewer. Bear in mind it must work back to Android 5. It would be interesting, for example, to review how Android OS does this for Mac address generation, and how random that really is itself.
Keeping this issue open (so it doesn't get missed) for now, but marking as a duplicate of #81.


Long term planning

Only 2 websites

Your Legal Help  https://yourlegalhelp.co.uk

RevivalDirect.co.uk

Coaches4Lawyers
RevivalDirect Weddings, Schools, Funerals, Private Hire
CPD Coaches

Avada theme weddings  https://avada.theme-fusion.com/wedding/

Avada Church   https://avada.theme-fusion.com/church/news/

Close this for now as site is now underway.


VCIO-next: Create improver to detect issues

We have sometimes issues and conflicts in the data we collect. For instance, we may have related advisories that contain different affected package version ranges. Or may disagree on the severity of a vulnerability or else. This is also something
For this we should create new improver to detect issues: it could detect and report discrepancies and conflicts in related advisories for a CVE, and flag these. That would later be input to curate these issues.

can I work on this issue?

@saransh1307 you sure can, but this is a fairly complex issue for a start.
May I suggest you check first some of the version issues in https://github.com/aboutcode-org/univers/issues?q=is%3Aissue+is%3Aopen+label%3A"good+first+issue" ... they are not always easy, but bite-size and much less complex.

Alright, @pombredanne, I'll focus on the suggested good first issues to build a solid understanding of the application. As I get more familiar with its structure and flow, I'll revisit this issue with a more informed perspective.


Fix and consolidate digitization scripts: tested with all 3 types

These follow mu2e_trig_config definition of trigger configuration.  Not all problems have been resolved, but the production scripts for all types of digitization now run.  In particular, mixing has still not been fixed.

Hi @brownd1978,
You have proposed changes to files in these packages:

JobConfig
Scripts

which require these tests: build.
@Mu2e/write, @Mu2e/fnalbuild-users have access to CI actions on main.
:hourglass: The following tests have been triggered for 886eb97d148c14b47b9fba43e5efa9e83a81193f: build  (Build queue is empty)
About FNALbuild. Code review on Mu2e/Offline.

:sunny: The build tests passed at 886eb97d148c14b47b9fba43e5efa9e83a81193f.

Test
Result
Details

test with
:white_check_mark:
Command did not list any other PRs to include

merge
:white_check_mark:
Merged 886eb97d148c14b47b9fba43e5efa9e83a81193f at 70b319ad0750f71cf6aa64ea2a61165c9c420b55

build (prof)
:white_check_mark:
Log file. Build time: 11 min 08 sec

ceSimReco
:white_check_mark:
Log file.

g4test_03MT
:white_check_mark:
Log file.

transportOnly
:white_check_mark:
Log file.

POT
:white_check_mark:
Log file.

g4study
:white_check_mark:
Log file.

cosmicSimReco
:white_check_mark:
Log file.

cosmicOffSpill
:white_check_mark:
Log file.

ceSteps
:white_check_mark:
Log file.

ceDigi
:white_check_mark:
Log file.

muDauSteps
:white_check_mark:
Log file.

ceMix
:white_check_mark:
Log file.

rootOverlaps
:white_check_mark:
Log file.

g4surfaceCheck
:white_check_mark:
Log file.

FIXME, TODO
:white_check_mark:
TODO (0) FIXME (0) in 0 files

clang-tidy
:white_check_mark:
0 errors 0 warnings

N.B. These results were obtained from a build of this Pull Request at 886eb97d148c14b47b9fba43e5efa9e83a81193f after being merged into the base branch at 70b319ad0750f71cf6aa64ea2a61165c9c420b55.
For more information, please check the job page here.
Build artifacts are deleted after 5 days. If this is not desired, select Keep this build forever on the job page.

It doesn't yet integrate with Validation.  I'm still working on that.
On Thu, Feb 29, 2024 at 10:01 AM Rob Kutschke @.***>
wrote:

I see this is approved and passes CI. Does it require coordination with
other PRs?
—
Reply to this email directly, view it on GitHub
https://github.com/Mu2e/Production/pull/300#issuecomment-1971671895, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABAH576A6XLM4K6JT7Z45N3YV5WH5AVCNFSM6AAAAABD5N3AEWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZRGY3TCOBZGU
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
David Brown            @.***
Office Phone<PHONE_NUMBER>
Lawrence Berkeley National Lab
M/S 50R5008 (50-6026C)  Berkeley, CA 94720

It doesn't yet integrate with Validation. I'm still working on that.

Does this mean I should wait for more commits?  Or merge now and you will make a new PR?

I'm done.  I asked Ray to review the validation changes
On Thu, Feb 29, 2024 at 11:04 AM Rob Kutschke @.***>
wrote:

It doesn't yet integrate with Validation. I'm still working on that.
Does this mean I should wait for more commits? Or merge now and you will
make a new PR?
—
Reply to this email directly, view it on GitHub
https://github.com/Mu2e/Production/pull/300#issuecomment-1971783651, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABAH57YE6GB7XO27WZ3QHZTYV55UBAVCNFSM6AAAAABD5N3AEWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZRG44DGNRVGE
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
David Brown            @.***
Office Phone<PHONE_NUMBER>
Lawrence Berkeley National Lab
M/S 50R5008 (50-6026C)  Berkeley, CA 94720

@FNALbuild run build test

:hourglass: The following tests have been triggered for cb1ce861381b23783cc737f6ef7db82132ee1596: build  (Build queue is empty)

:umbrella: The build tests failed for cb1ce861381b23783cc737f6ef7db82132ee1596.

Test
Result
Details

test with
:white_check_mark:
Command did not list any other PRs to include

merge
:white_check_mark:
Merged cb1ce861381b23783cc737f6ef7db82132ee1596 at 70b319ad0750f71cf6aa64ea2a61165c9c420b55

build (prof)
:white_check_mark:
Log file. Build time: 11 min 13 sec

ceSimReco
:white_check_mark:
Log file.

g4test_03MT
:white_check_mark:
Log file.

transportOnly
:white_check_mark:
Log file.

POT
:white_check_mark:
Log file.

g4study
:white_check_mark:
Log file.

cosmicSimReco
:white_check_mark:
Log file.

cosmicOffSpill
:x:
Log file. Return Code 65.

ceSteps
:white_check_mark:
Log file.

ceDigi
:x:
Log file. Return Code 65.

muDauSteps
:white_check_mark:
Log file.

ceMix
:x:
Log file. Return Code 65.

rootOverlaps
:white_check_mark:
Log file.

g4surfaceCheck
:white_check_mark:
Log file.

FIXME, TODO
:white_check_mark:
TODO (0) FIXME (0) in 0 files

clang-tidy
:white_check_mark:
0 errors 0 warnings

N.B. These results were obtained from a build of this Pull Request at cb1ce861381b23783cc737f6ef7db82132ee1596 after being merged into the base branch at 70b319ad0750f71cf6aa64ea2a61165c9c420b55.
For more information, please check the job page here.
Build artifacts are deleted after 5 days. If this is not desired, select Keep this build forever on the job page.

@FNALbuild run build test

:hourglass: The following tests have been triggered for 0f923b1aeaf9b65be4a2c2291d3cdfd5a48cf286: build  (Build queue has 1 jobs)

:sunny: The build tests passed at 0f923b1aeaf9b65be4a2c2291d3cdfd5a48cf286.

Test
Result
Details

test with
:white_check_mark:
Command did not list any other PRs to include

merge
:white_check_mark:
Merged 0f923b1aeaf9b65be4a2c2291d3cdfd5a48cf286 at 70b319ad0750f71cf6aa64ea2a61165c9c420b55

build (prof)
:white_check_mark:
Log file. Build time: 11 min 16 sec

ceSimReco
:white_check_mark:
Log file.

g4test_03MT
:white_check_mark:
Log file.

transportOnly
:white_check_mark:
Log file.

POT
:white_check_mark:
Log file.

g4study
:white_check_mark:
Log file.

cosmicSimReco
:white_check_mark:
Log file.

cosmicOffSpill
:white_check_mark:
Log file.

ceSteps
:white_check_mark:
Log file.

ceDigi
:white_check_mark:
Log file.

muDauSteps
:white_check_mark:
Log file.

ceMix
:white_check_mark:
Log file.

rootOverlaps
:white_check_mark:
Log file.

g4surfaceCheck
:white_check_mark:
Log file.

FIXME, TODO
:white_check_mark:
TODO (0) FIXME (0) in 0 files

clang-tidy
:white_check_mark:
0 errors 0 warnings

N.B. These results were obtained from a build of this Pull Request at 0f923b1aeaf9b65be4a2c2291d3cdfd5a48cf286 after being merged into the base branch at 70b319ad0750f71cf6aa64ea2a61165c9c420b55.
For more information, please check the job page here.
Build artifacts are deleted after 5 days. If this is not desired, select Keep this build forever on the job page.

@FNALbuild run build test

:hourglass: The following tests have been triggered for 437c80a8db2d32e9c2bf4cf07771b236f8b66bea: build  (Build queue is empty)

:sunny: The build tests passed at 437c80a8db2d32e9c2bf4cf07771b236f8b66bea.

Test
Result
Details

test with
:white_check_mark:
Command did not list any other PRs to include

merge
:white_check_mark:
Merged 437c80a8db2d32e9c2bf4cf07771b236f8b66bea at 70b319ad0750f71cf6aa64ea2a61165c9c420b55

build (prof)
:white_check_mark:
Log file. Build time: 10 min 52 sec

ceSimReco
:white_check_mark:
Log file.

g4test_03MT
:white_check_mark:
Log file.

transportOnly
:white_check_mark:
Log file.

POT
:white_check_mark:
Log file.

g4study
:white_check_mark:
Log file.

cosmicSimReco
:white_check_mark:
Log file.

cosmicOffSpill
:white_check_mark:
Log file.

ceSteps
:white_check_mark:
Log file.

ceDigi
:white_check_mark:
Log file.

muDauSteps
:white_check_mark:
Log file.

ceMix
:white_check_mark:
Log file.

rootOverlaps
:white_check_mark:
Log file.

g4surfaceCheck
:white_check_mark:
Log file.

FIXME, TODO
:white_check_mark:
TODO (0) FIXME (0) in 0 files

clang-tidy
:white_check_mark:
0 errors 0 warnings

N.B. These results were obtained from a build of this Pull Request at 437c80a8db2d32e9c2bf4cf07771b236f8b66bea after being merged into the base branch at 70b319ad0750f71cf6aa64ea2a61165c9c420b55.
For more information, please check the job page here.
Build artifacts are deleted after 5 days. If this is not desired, select Keep this build forever on the job page.


Fixes#1580 Pagination added in imagesearch

Fixes#1580 Pagination added in image search.
Fixes#1580 (Search results sometimes appear twice)
Description (required)

Added a parameter "sroffset" for getting list of images in search. (It helps in providing images after that offset)
On last recieved of recyclerview we are calling API again with offset = size of query list it gives us next 25 images .
We add the images to the already existing list and refresh the adapter.

Tests performed
Manually Tested on {API 25 & Moto G5S+}, with ProdDebug variant.

@nicolas-raoul @neslihanturan can you test this feature. Any suggestions on the implementation would be helpful.

Codecov Report

Merging #1597 into browse-commons-via-app will decrease coverage by <.01%.
The diff coverage is 0%.

@@                    Coverage Diff                    @@
##           browse-commons-via-app   #1597      +/-   ##
=========================================================
- Coverage                    3.79%   3.78%   -0.01%
=========================================================
  Files                         154     154
  Lines                        7730    7749      +19
  Branches                      716     717       +1
=========================================================
  Hits                          293     293
- Misses                       7420    7439      +19
  Partials                       17      17

Impacted Files
Coverage Δ

...rw/commons/explore/images/SearchImageFragment.java
0% <0%> (ø)
:arrow_up:

...rw/commons/mwapi/ApacheHttpClientMediaWikiApi.java
4.72% <0%> (-0.02%)
:arrow_down:

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 8edfae5...c847dbf. Read the comment docs.

If you clean comment, I will merge.

Thanks @ujjwalagrawal17


requests is not included in requirements, had to install it manually

Hi @rajahaidarIBM, the sdk still uses the vendored version of the requests package.
Did you get an error when you tried to run your application....

Duplicate issue. The reference provided has resolved the issue for users. There is an internal JIRA ticket to track the issue.