Add Pass action to Antrea-native policies

Describe what you are trying to solve

Currently there is no way to delegate rule evaluation from Antrea-native policies to K8s NetworkPolicies. Consider the use case where inter-tenant namespaces traffic must be denied by ACNP but intra-tenant traffic is explicitly delegated to namespace owners and devs. This can be done by ensuring that higher order deny rules don't deny intra-tenant traffic which requires complex rule writing.
Describe the solution you have in mind

Introduce a new Pass action which skips all the ANP/ACNPs from all higher order Tiers and consults the K8s NetworkPolicy tables. If there is no match in K8s NetPol tables (ie no rule was created by the namespace owner for this traffic) then enforce any baseline Tier policy, if any. Finally if no rule was matched, allow the traffic.
Describe how your solution impacts user flows

Admins may write explicit rules to delegate traffic to namespace owners.
Describe the main design/architecture of your solution

Introduce a new Action value "Pass" for ANP/ACNP. Traffic that matches this rule will skip evaluation of further rules from ANP/ACNP tables and is submitted to the Ingress/Egress K8s NetPol tables.
Alternative solutions that you considered

Test plan

Additional context

cc @Dyanngg @GraysonWu @qiyueyao

Just to make sure: the rule with Pass action will have the highest priority right?

Just to make sure: the rule with Pass action will have the highest priority right?

Practically, emergency Deny rules should be highest; followed by Pass action rules and then the allow and deny rules.
However, since we provide the flexibility of arranging rules and priorities however we want, we should honor such ordering. When the policy is as follow:
Rule1 - Allow
Rule2 - Deny
Rule3 - Pass
Rule4 - Deny
...
RuleN - Allow
traffic matching Rule3 must skip all rules from 4 to N and move on the K8s NetPol. But it will still honor Rule1 and 2.


Fix min torch version

tensor.view() usage requires [torch-1.11](Enable all dtype combinations in torch.Tensor.view(dtype) (#66493) · pytorch/pytorch@0420545 (github.com))

Adding link to passing P40 Torch 1.10 version: https://github.com/microsoft/DeepSpeed/actions/runs/6251995306/job/16974269387


Document images in terminal formatting and in less

I have idea for a new feature for jQuery Terminal
Document images in terminal formatting and in less. Create example that showcase both.

kindly add the needed tags and assign the task to me.

You don't need assignments no one on GitHub actually uses them. The only use of them is on Open Source contribution guides.

Apologies @jcubic but I won't be able to do this part of me. My bad I supposed the topic is under my expertise but it is yet to learnt by me.


Fix for emails not being sent out when a single email was not on the …

…safe list.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the bcrs-entities-create-ui license (Apache 2.0).

Codecov Report

Merging #48 (599539d) into main (0fe1eda) will increase coverage by 1.07%.
The diff coverage is 74.08%.

@@            Coverage Diff             @@
##             main      #48      +/-   ##
==========================================
+ Coverage   84.37%   85.45%   +1.07%
==========================================
  Files          35       40       +5
  Lines         768      976     +208
  Branches       72       61      -11
==========================================
+ Hits          648      834     +186
- Misses        117      135      +18
- Partials        3        7       +4

Flag
Coverage Δ

notifyapi
85.45% <74.08%> (+1.07%)
:arrow_up:

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

Impacted Files
Coverage Δ

notify-api/src/notify_api/models/db.py
100.00% <ø> (ø)

...api/src/notify_api/services/providers/gc_notify.py
56.41% <27.27%> (-11.34%)
:arrow_down:

notify-api/src/notify_api/models/email.py
44.00% <44.00%> (ø)

...tify-api/src/notify_api/services/notify_service.py
60.81% <47.72%> (-39.19%)
:arrow_down:

notify-api/src/notify_api/models/content.py
95.23% <70.00%> (-4.77%)
:arrow_down:

notify-api/src/notify_api/models/attachment.py
96.36% <71.42%> (-3.64%)
:arrow_down:

notify-api/src/notify_api/resources/v2/notify.py
93.93% <71.42%> (+93.93%)
:arrow_up:

notify-api/src/notify_api/models/notification.py
96.80% <72.72%> (-3.20%)
:arrow_down:

...otify-api/src/notify_api/resources/v2/safe_list.py
80.00% <80.00%> (ø)

notify-api/src/notify_api/models/safe_list.py
80.55% <80.55%> (ø)

... and 11 more

... and 2 files with indirect coverage changes


Pip filter phony packages

Please have a look at the individual commit messages for the details.

FYI @mmurto.

FYI @mmurto.

I'll test this asap!

Superseded by https://github.com/oss-review-toolkit/ort/pull/5319.


Consider moving to Jetpack DataStore

More info here: https://android-developers.googleblog.com/2020/09/prefer-storing-data-with-jetpack.html

This should be doable, and would remove the dependency on Room, which seems flakey for our use case


Inquiry About Addition of Google Analytics Consent Options for Ad Personalization and User Data

I am reaching out to inquire about a potential enhancement to the Firebasex that could significantly benefit users who rely on Google Analytics.
As you know, with the increasing importance of privacy and data protection, managing user consents for cookies and data collection has become a crucial aspect of website management. Google Analytics offers options for ad personalization (ad_personalization) and access to user data (ad_user_data), which are essential for delivering a tailored advertising experience while adhering to privacy regulations.
Ad Personalization Consent (ad_personalization): This would allow users to opt-in or out of personalized advertising delivered by Google Analytics.
User Data Access Consent (ad_user_data): This would give users the option to control whether their data can be used by Google Analytics for advertising purposes.
Could you please share if there are any plans to incorporate these specific consent options into Firebasex? If so, do you have an estimated timeline for when these features might be available?

Thanks, this is what I needed

Resolved by release of<EMAIL_ADDRESS>


TypeError: fs.readdirSync is not a function

fs.readdirSync and fs.statSync functions doesnot exists in require('fs');
Please find alternate

https://nodejs.org/dist/latest-v12.x/docs/api/fs.html#fs_fs_readdirsync_path_options
https://nodejs.org/dist/latest-v12.x/docs/api/fs.html#fs_fs_statsync_path_options

@dougwilson
installed fs from using 'npm i fs' from https://www.npmjs.com/package/fs .
Installed version - 0.0.1-security
Please advise from where to install and what version

Modules that are part of node.js like fs do not need to be installed.

if i go by the default - and debug inside require-all, i'm getting fs as below

Please let me know where i'm going wrong

I'm not sure, that fs doesn't look at all like the fs included with Node.js. What version of Node.js are you running this on? If your fs does not have a fs.readdirSync, what methods does it have?

node version - v12.14.1
you can check the fs object in console of above given screenshot.

Weird, I think you may have something wrong with your Node.js installation, then. You may want to open an issue with Node.js to help determine what is wrong with your system, as I'm not sure there is anything I can do in this module, as the only purpose of this module is to read the list of files from the file system.
In my first comment https://github.com/felixge/node-require-all/issues/60#issuecomment-573030763 I linked to the 12.14.1 docs for the fs methods I'm using, so it would seem to indicate that if you're missing them, there is something wrong with your Node.js install.


 This is based on
current Linux mainline with some extra reMarkable patches on top. This
doesn't yet have the same support as the vendor kernel, but does have
most of the core functionality.
Known issues with the 5.16 mainline kernel:

[ ] No support for low power mode (suspend uses more power then it should)
[ ] Cyttsp5 (touchscreen) doesn't come back up after sleep
[ ] WiFi sometimes is off on boot (can be turned on in Oxide though)
[ ] GUI shutdown in Oxide doesn't work
[ ] Wacom stylus doesn't work in Xochitl (works everywhere else though)
[ ] No RDNIS (network) access over USB
[ ] No OTG control support

You can see the diff with mainline here: https://mainline.space/
This simplifies the install process specified here:
https://remarkablewiki.com/tech/updatingkernel
Signed-off-by: Alistair Francis<EMAIL_ADDRESS>

So far everything I have tried works fine, so I don't think there are many deltas.
Someone else is welcome to work on the rm1 kernel. That's another massive effort

Any comments?

I can't test as I don't have a rM2.

I’d love to test this but I still haven’t managed to make the rM2 recovery work. I have all the required parts but no soldering iron at hand, yet some soldering seems to be required to make the connection stable enough. I’m on a tight budget right now so it’ll probably be a few month until I buy one. Anyone else available to test this?

I had a quick look at the package and I have a question: why did you decide not to perform the actions in configure and postremove?

I had a quick look at the package and I have a question: why did you decide not to perform the actions in configure and postremove?

Because of the risk of bricking the device. That said, we probably should include some sort of helper script to automate the actions.

Why do you think that running the code in the package is any riskier than asking the user to run the same commands by hand?
Anyway I agree: a script would be nice to have.
Having said this, given the amount of things not working with a mainline kernel, I doubt this package will be used for other than development.

Why do you think that running the code in the package is any riskier than asking the user to run the same commands by hand?

Because you have to choose to make the change. Doing it automatically could completely break things for users without them expecting it on upgrade or by just poking around.
That aside we tend to avoid making changes like this with toltec install scripts. You have to explicitly enable services when you install them. We aren't like debian, who enables services on install by default.

Having said this, given the amount of things not working with a mainline kernel, I doubt this package will be used for other than development.

That list should shrink as time goes on.

Ok, I see the point.
I gave this package a spin and it works as advertised. The only thing that needs to be changed is line 45 because it mentions the wrong version. Maybe this should automatically point to pkgver.

I had a quick look at the package and I have a question: why did you decide not to perform the actions in configure and postremove?

I was worried that someone would install the package without realising and then upgrade their kernel. By adding the manual install steps it's harder to install, but not too hard. As for removing I didn't want to delete modules from a running system unless the user really wanted to.

Having said this, given the amount of things not working with a mainline kernel, I doubt this package will be used for other than development.

I'm using it daily, it does some a few issues but there aren't that many.

Just rebased and address the outdated string comment. Hopefully this is ready to merge now

Any more comments?

Any more comments?

Sorry it is taking me ages to find some spare time to review this. I'll try to have a look at it today.

I think the list of known issues with the mainline kernel (as mentioned in the original post) should be shown to users in configure().

Something is still not working with the uninstall instructions: it says
rm -rf /lib/modules/5.16.0/ but it should say rm -rf /lib/modules/5.16.0-rc8/
I am also having issues intalling this due to my partition being almost full. Can a bigger part of the package be offloaded to /opt?

Note to self: when this package does not install properly because of space constraints be careful about the backup: you might end up backupping mainline rather than upstream and then, when reverting, you end up with a brick due to mssing modules.

A follow-up comment due to my space constraints. Would it  be safer to install directly the kernel into /boot rather than /usr/boot and then ask the user to update symlinks? In this way if there is a failure cause by disk space it happens at install time and a simple opkg remove should fix the problem automagically.

It might be a good idea to add a utility to manage switching kernels and validating that backups are properly in place etc. kernelctl or something. That way it can handle failure more gracefully instead of assuming users will fully understand the implications of issues they encounter.

It might be a good idea to add a utility to manage switching kernels and validating that backups are properly in place etc. kernelctl or something. That way it can handle failure more gracefully instead of assuming users will fully understand the implications of issues they encounter.

Since it looks unlikely that they will revert the change to TRIM_UNUSED_KSYMS (cf. https://github.com/reMarkable/linux/issues/8#issuecomment-1043664468) I am considering making another toltec package with an upstream kernel, TRIM_UNUSED_KSYMS=n, and maybe some exra modules like uinput. We may want to coordinate such a utility to deal with all aftermarket kernel toltec ships.

Here is a proposal for a script, say kernelctl, to manage aftermarket kernels.
kernelctl provides 4 commands:

kernelctl help: the obvious thing,
kernelctl init: to be run when it is installed and every time one updates the OS,
kernelctl list: show a numbered list of available kernels (the current one being marked by a *),
kernelctl set number/name: configure the system to boot the desired kernel.

Kernel packages in toltec will only install a tar.gz file inside a staging
directory, say /opt/kernelctl. Ideally the file should be named something
like kernelname-version.tar.gz. It should be possible to extract such a file
in / to have a working system booting kernelname. By this I mean that it should
contain lib/modules/version/, boot/zImage, and anything else that is
required respecting the correct paths.
kernelctl init should create /opt/kernelctl, a backup of the current
running kernel in it, say upstream-version.tar.gz, and write
current_kernel=upstream-version in some configuration file (I do not know
which could be a sane location for this file to be).
kernel set number/name should list the content of current_kernel-version.tar.gz
and use this list to delete the corresponding files, extract
new_kernel-version.tar.gz and set current_kernel=new_kernel-version,
optionally ask to reboot.
Uninstalling kernelctl should first run kernelctl set default, then remove /opt/kernelctl.
All kernel packages in toltec should depend on kernelctl and say that to enable the newly installed kernel one should use it.

/opt/kernelctl

It would need to be stored elsewhere, /opt mirrors the standard folder structure. So /opt/usr/share/kernelctl would be a better location.

/opt/kernelctl

It would need to be stored elsewhere, /opt mirrors the standard folder structure. So /opt/usr/share/kernelctl would be a better location.

sounds good to me, any other comment/change?

Nothing jumps out to me at the moment.

Just addressed the comments on this PR, let me know if you think it should directly be installed in /boot instead.
A kernelctl tool would be useful to have as well

A kernelctl tool would be useful to have as well

I am working on it, it should be available soon. Meanwhile could you please make so that this package uses it?
Here is what needs to be done:

this package has to depend on a package not yet in toltec that will be called kernelctl
all the files needed to deploy your kernel need to be in a .tar.bz2 file named something like kernelname-kernelversion.tar.bz2 (for example the kernel shipped by remarkable will be saved in a file of the form upstream-20220202133838.tar.bz2)
to boot your kernel it should suffice to extract kernelname-kernelversion.tar.bz2  in /, do not worry about any cleanup of other kernels
this package should only install kernelname-kernelversion.tar.bz2  in /opt/usr/share/kernelctl and print a message directing users to kernelctl to boot the new kernel

Thanks

I was finally able to make the recovery steps work, so I’ll also give this kernel a try as soon as I can!

@Etn40ff I'd recommend getting a PR opened so we can provide feedback there.

I will as soon as I have the package closer to being reviewed

#569 has been opened. We'll probably want to block this PR until it's done.

I am hijacking this PR to talk to @alistair23
Did you figure out why is RDNIS not working? I just noticed that it does not work also in a test kernel that I built directly from the vendor sources. In theory it should work there.

I haven't figured out the RDNIS issue. That's strange it's not working from the vendor sources, have you changed any configs? Also I'm in the reMarkable Matrix room if you want to talk there

I haven't figured out the RDNIS issue. That's strange it's not working from the vendor sources, have you changed any configs? Also I'm in the reMarkable Matrix room if you want to talk there

Which is linked to #general in discord.

I just realized that this kernel is twice as big as the default one: zImage is 12Mb compared to 6Mb . Do you have a guess on why is it so?

I would guess the size difference is related to the defconfig, this is just using the in-tree defconfig which enables lots of extra features

I see. Maybe later on (after getting all components to work) it could be useful to try to shrink the size: space is unfortunately very limited in the
root partitions.
On a related note, in case you missed it I made a preliminary attempt to modify
this package to use kernelctl: https://github.com/alistair23/toltec/pull/1

It works! 🎉
$ uname -a
Linux reMarkable 5.18.0 #1 SMP Sat Jun 25 19:41:28 UTC 2022 armv7l GNU/Linux

Thanks @alistair23 for the excellent work, and sorry for the abysmally slow review process. From some initial tests, everything seems to work as expected, so I think we can merge this to testing.
I added some minor changes above (most notably moving the package to a dedicated kernel section). I’m working to change the package() a little bit to produce a kernel archive suitable for #569 and then we should be good for merge.

I added the change described in my previous comment, based on @Etn40ff’s work in https://github.com/alistair23/toltec/pull/1 (thanks!). The plan will be to merge this PR first (and leave in the manual post-install instructions for now), then use this package to test and finalize #569.


transfer submission files at submit time, not from the job

So don't even transfer them TO the job to begin with. This transfers every file in the submit dir, which I think is OK (like, we never expect there to be credentials in there?)
Fixes #311

Looks like you need to rebase?

'tis done, twice since the first time I messed up. rebase -i (or really magit r i) is a lifesaver :)

As far as whether or not we expect credentials to be in the submit directory - I'm not sure we can make that assumption.  @vitodb would be a good person to ask this question to.  If anyone has a legitimate reason to do so, it'd probably be him.

Is here submit directory the actual directory where users run the jobsub_submit command?

but we need to wait for that until the persistent areas are in the token scopes, otherwise we'll break
--use-pnfs- dropbox...

I thought that --use-pnfs-dropbox writes to resilient, and those scopes are in the token...


Org mode org-schedule (C-c C-s) error

Expected behavior
I press C-c C-s and expected to prompt the calendar to chose a date.
Actual behavior
But, actually, for a split second the calendar appears, and then emacs returns me the message:
version-to-list: Invalid version syntax: ‘’ (must start with a number)
Steps to reproduce the problem
Create a TODO item, press C-c C-s on top of it.
Environment & Version information
All my org related packages are up to date.
Emacs version
GNU Emacs 27.1 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.22, cairo version 1.17.3) of 2020-08-29
Operating system
Artix Linux (Arch with runit et el.)

https://user-images.githubusercontent.com/59554283/103458396-4ba18e00-4ce6-11eb-81b8-4e79cf486f95.mp4

https://user-images.githubusercontent.com/59554283/103458396-4ba18e00-4ce6-11eb-81b8-4e79cf486f95.mp4

I'm getting the exact same error, I'm not well versed with emacs debugging, if there are anythings I can provide, please let me know. This is the content of the Warnings buffer:
Error (use-package): org-journal/:catch: Invalid version syntax: ‘’ (must start with a number)
And this is the MEssages:
version-to-list: Invalid version syntax: ‘’ (must start with a number)

This error is described here and here. Installing org-mode 9.4.4 from Elpa and restarting Emacs resolved the issue for me.

Thank you, that fixed the problem.


how pods get their ip address

https://ronaknathani.com/blog/2020/08/how-a-kubernetes-pod-gets-an-ip-address/


File Merge Group

Adds a calc prop to help determine if files in a file set are candidates for merge
Adjusts access key automated expiration to 30 days

I think it works as expected.


make test clean, build, and reset dist

inent it to make it easier to run npm test. see https://github.com/ramda/ramda/issues/1152

:deciduous_tree:

:+1:

:herb:


[Feature]: Add Hold and Double-tap action to Menu chip card

Is your feature request related to a problem?
I would like to have the option to add a hold and double tap action to the menu chip card. This way, I can use the menu chip to disable kiosk mode by holding the button and then open the menu by tapping on it.
Describe the solution you'd like
See above.
Describe alternatives you've considered
I tried the action chip card, but there's no action to open the menu.
Additional context
No response

I just came here to add this same feature request!

I was searching for this aswell. This would allow to use the hold action to enbale the edit view, making for a much cleaner UI!


drop-while and take-while are not external in the serapeum

Hello, those two functions does not seems to be exported from serapeum package and it certainly looks like they should.

Exported, thanks.


Spotty kubernetes event collection

Output of the info page (if this is a bug)
» k exec -it datadog-5lnhk agent status
Getting the status from the agent.

===============
Agent (v6.10.0)
===============

  Status date: 2019-03-25 13:53:10.729646 UTC
  Pid: 380
  Python Version: 2.7.15
  Logs:
  Check Runners: 4
  Log Level: WARNING

  Paths
  =====
    Config File: /etc/datadog-agent/datadog.yaml
    conf.d: /etc/datadog-agent/conf.d
    checks.d: /etc/datadog-agent/checks.d

  Clocks
  ======
    NTP offset: -71µs
    System UTC time: 2019-03-25 13:53:10.729646 UTC

  Host Info
  =========
    bootTime: 2019-03-20 10:55:24.000000 UTC
    kernelVersion: 4.19.25-coreos
    os: linux
    platform: debian
    platformFamily: debian
    platformVersion: buster/sid
    procs: 73
    uptime: 58s
    virtualizationRole: guest
    virtualizationSystem: kvm

  Hostnames
  =========
    host_aliases: [redacted]
    hostname: redacted
    socket-fqdn: datadog-5lnhk
    socket-hostname: datadog-5lnhk
    hostname provider: container
    unused hostname providers:
      aws: not retrieving hostname from AWS: the host is not an ECS instance, and other providers already retrieve non-default hostnames
      configuration/environment: hostname is empty
      gce: unable to retrieve hostname from GCE: Get http://<IP_ADDRESS>/computeMetadata/v1/instance/hostname: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

=========
Collector
=========

  Running Checks
  ==============

    cpu
    ---
      Instance ID: cpu [OK]
      Total Runs: 29,508
      Metric Samples: Last Run: 6, Total: 177,042
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 0s

    disk (2.1.0)
    ------------
      Instance ID: disk:e5dffb8bef24336f [OK]
      Total Runs: 29,507
      Metric Samples: Last Run: 244, Total: 1 M
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 123ms

    docker
    ------
      Instance ID: docker [OK]
      Total Runs: 29,507
      Metric Samples: Last Run: 317, Total: 1 M
      Events: Last Run: 0, Total: 1,916
      Service Checks: Last Run: 1, Total: 29,507
      Average Execution Time : 48ms

    file_handle
    -----------
      Instance ID: file_handle [OK]
      Total Runs: 29,507
      Metric Samples: Last Run: 5, Total: 147,535
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 0s

    io
    --
      Instance ID: io [OK]
      Total Runs: 29,507
      Metric Samples: Last Run: 130, Total: 1 M
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 0s

    kubelet (2.4.0)
    ---------------
      Instance ID: kubelet:d884b5186b651429 [OK]
      Total Runs: 29,507
      Metric Samples: Last Run: 437, Total: 1 M
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 4, Total: 118,025
      Average Execution Time : 427ms

    kubernetes_apiserver
    --------------------
      Instance ID: kubernetes_apiserver [OK]
      Total Runs: 29,507
      Metric Samples: Last Run: 0, Total: 0
      Events: Last Run: 0, Total: 377
      Service Checks: Last Run: 5, Total: 225
      Average Execution Time : 100ms

    load
    ----
      Instance ID: load [OK]
      Total Runs: 29,507
      Metric Samples: Last Run: 6, Total: 177,042
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 0s

    memory
    ------
      Instance ID: memory [OK]
      Total Runs: 29,507
      Metric Samples: Last Run: 17, Total: 501,619
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 0s

    network (1.9.0)
    ---------------
      Instance ID: network:2a218184ebe03606 [OK]
      Total Runs: 29,508
      Metric Samples: Last Run: 105, Total: 1 M
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 345ms

    ntp
    ---
      Instance ID: ntp:b4579e02d1981c12 [OK]
      Total Runs: 29,507
      Metric Samples: Last Run: 1, Total: 29,507
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 1, Total: 29,507
      Average Execution Time : 0s

    uptime
    ------
      Instance ID: uptime [OK]
      Total Runs: 29,508
      Metric Samples: Last Run: 1, Total: 29,508
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 0s

========
JMXFetch
========

  Initialized checks
  ==================
    no checks

  Failed checks
  =============
    no checks

=========
Forwarder
=========

  Transactions
  ============
    CheckRunsV1: 29,508
    Dropped: 0
    DroppedOnInput: 0
    Events: 0
    HostMetadata: 0
    IntakeV1: 3,718
    Metadata: 0
    Requeued: 0
    Retried: 0
    RetryQueueSize: 0
    Series: 0
    ServiceChecks: 0
    SketchSeries: 0
    Success: 62,734
    TimeseriesV1: 29,508

  API Keys status
  ===============
    API key ending with e5d88: API Key valid

==========
Endpoints
==========
  https://app.datadoghq.com - API Key ending with:
      - redacted

==========
Logs Agent
==========

  docker
  ------
    Type: docker
    Status: OK
    Inputs: 86865f94527467d22142d81c3fd535d4ba3c824aad2df3f7d1c12ede6b131cb5

=========
Aggregator
=========
  Checks Metric Sample: 39.2 M
  Dogstatsd Metric Sample: 73,768
  Event: 2,294
  Events Flushed: 2,294
  Number Of Flushes: 29,508
  Series Flushed: 33.7 M
  Service Check: 502,328
  Service Checks Flushed: 531,835

=========
DogStatsD
=========
  Event Packets: 0
  Event Parse Errors: 0
  Metric Packets: 73,768
  Metric Parse Errors: 0
  Service Check Packets: 0
  Service Check Parse Errors: 0
  Udp Packet Reading Errors: 0
  Udp Packets: 73,769
  Uds Origin Detection Errors: 0
  Uds Packet Reading Errors: 0
  Uds Packets: 0

Describe what happened:
Kubernetes event collection breaks shortly after an agent acquires leader lock. If I kill the agent that holds the leader lock another one acquires it, collects evens for a short while (minutes) but then it also stops reporting k8s events. I can seemingly repeat this any number of times.
Weirdly enough we have another cluster where event collection seems to work fine.
You can see in the above agent output it collected 377 events and nothing on later runs.
Describe what you expected:
K8s event collection to work reliably
Steps to reproduce the issue:
Datadog deployed with official helm chart (values user: here) on k8s 1.12
Additional environment details (Operating System, Cloud provider, etc):
CoreOS Container Linux (latest stable), on-premises

While searching through the issue tracker I bumped into https://github.com/DataDog/datadog-agent/issues/2020 which could be related, except the cluster where we have working event collection is actually the cluster with a higher number of events (though not necessarily more stressed) so I'd expect its events endpoint to be busier/take longer.
That 100ms timeout seems awfully low though. Is there no way to override that without having a config dropin (e.g. env var)? 😞

Hey @andor44 - Sorry to hear that you are having this issue.
We are working on improving the Kubernetes event collection as one of the top priority tasks.
I am marking this issue so we can track it internally.
We will keep you posted as soon as we make progress.
Best,
.C

I tried enabling the cluster agent. At first it also didn't collect events but after raising CPU limits event collection seems to work with the cluster agent. This leads me to believe the issue I'm experiencing is related to #2020 still.
I think it might be worth adding a section about the low request timeout for event collection to the readme and/or to the troubleshooting section.

Understood, as it uses the same code path I would expect the same behaviour.
Thanks for sharing, we will start addressing this week.
Best,
.C

Just chiming in that we're also experiencing this issue.

@mshade would you mind opening a ticket with our solutions team, we'd like to gather more details to confirm that.
Thank you, and sorry for the headache.
Best,
.C

Thanks @CharlyF -- we do have a ticket open, but I hadn't seen the github issue, so I just wanted to ping on it as well.

I have a similar problem with missing kubernetes events, although the agent does not seem to completely stop sending events, but rather just skips the bulk of them.  I have opened case 225225.

In case anybody finds this helpful, here is what Datadog support had to say:

We determined that there was a rate limit applied to kubernetes events for your account back in 2019. Specifically, it was limiting 95% of the kubernetes traffic. This was a standard practice at the time- due to excessively high traffic and billing concerns for customers. Back then, Kubernetes events were considered custom events, and therefore customers were charged for them.
Now that Kubernetes events are no longer considered custom events, and my colleagues will remove the limit.

...so if anybody else encounters this, open a support ticket and ask for this rate limit to be removed for your account.


Release 1.23.0

PTAL

Codecov Report

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

@@            Coverage Diff            @@
##             master     #519   +/-   ##
=========================================
  Coverage     72.64%   72.64%
  Complexity      853      853
=========================================
  Files           169      169
  Lines          3864     3864
  Branches        294      294
=========================================
  Hits           2807     2807
  Misses          914      914
  Partials        143      143

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 2e782a3...2fba805. Read the comment docs.


Fixed an occurrence of a panic while preloading non existent fields.

I have encountered a possible panic while preloading non existent fields (e.g. a foreign key can be NULL).
Check the unit tests. Uncomment my bugfix in callback_query_preload.go and run the tests to verify the bug. You will get a panic because currentScope.getColumnAsScope can possibly return nil pointer and you don not check for that case currently.

@jinzhu Can you look into the wercker failure? It fails to get the code form github for some reason.
I ran all tests with ./test_all.sh and they all pass so this should be fine.

Thank you for your PR


Cleaner WARP10_HOME, resolving relative path.

After your modifications the OS variable remains unused. It could be removed


Add checklist for Soulsow and Harvest Moon

Add the checklist for Soul Sow & Harvest Moon usages on pre-pull and between fight downtimes.
Changelog will be added after #1482 is merged because my info is there.

Deprecated by #1559.


View Add/Edit User: Get user

Description
Editing a given user needs a service to get its data:

username
password
password expired
email
active
locked
organisation
roles
curatory groups

So we need a GET:
GET /users/42?_embed=organisations, curatorGroups

{
  data: {
    id: 42,
    name: ‘Frank’,
    passwordExpired: true,
    email<EMAIL_ADDRESS>    active: true,
    locked: false,
    organisationId: 42,
    roleIds: [{ id: 42, name: ‘Contributor’ }, { id: 33, name: ‘Editor’ }],
    curatoryGroups: [{ id: 42, name: ‘LASeR’ }, ... ],
    _links: {
      self:  { href: ‘/users/42’’ },
      update: { href: ‘/users/42’ },
    }
  }
}

The existence of an update link in the result tells the frontend whether an update is allowed or not.
Estimated Workload: 1-2 d
Actual Workload:

I always get a 404, not found. Maybe my guess of an id is to bad, but the id of my profile does also not work: https://phaeton-dev.hbz-nrw.de/gokb/rest/users/1859007.
What am I doing wrong?

nothing.
The implementation of the user endpoint is on another branch (mine), than the one that's deployed (Moritz'), therefore, it's not online yet on phaeton-dev.
Sorry 'bout that.


[BUG] Import of btp_subaccount_trust_configuration not possible - Unexpected Import Identifier

Is there an existing issue for this?

[X] I have searched the existing issues

What version of the Terraform provider are you using?
v1.0.0-rc1
What version of the Terraform CLI are you using?
1.6.6
What type of issue are you facing
bug report
Describe the bug
We'd like to log in to applications in a BTP subaccount only by custom IDP and deactivate the user login for sap.default.
When a new subaccount will be created, the trust configuration for the custom IDP should be done and the user login for sap.default on the just created subaccount should be deactivated.
That's why we'd like to set "available_for_user_logon" for the sap.default IDP to false.
We added the following config to our script to get the config of the sap.default IDP to change the attribute:
data "btp_subaccount_trust_configuration" "default" {
  subaccount_id = btp_subaccount.subaccount-dev.id
  origin        = "sap.default"
}

import {
  to = btp_subaccount_trust_configuration.default-idp
  id = data.btp_subaccount_trust_configuration.default
}

Unfortunately, we are getting the following error:
│ Error: Unexpected Import Identifier
│ Expected import identifier with format: subaccount_id,origin. Got: "sap.default"
Expected Behavior
Import without errors
Steps To Reproduce
No response
User's Role Collections
No response
Add screenshots to help explain your problem
No response
Additional context
No response

Hi, thanks for the hint with the combined key, we have come one step further and the import in general works. Unfortunately, the import does not seem to work in the same run as the subaccount is created (a general terraform issue). It does not seem to be possible to create a subaccount, activate the custom IDP and deactivate the login with the default IDP in the same run.

Hi @TVSiemens great that you could sort the import out. You are right (and I indeed forgot to mention that), that the setup you want to achieve is not feasible within in one single step but needs to be done in two sequential steps in your CI/CD setup.
This is due to the fact that the default IdP gets created behind the scenes by the BTP and we have no way to influence that or to inject the right configuration from the start. So unfortunately nothing that can be fixed on the provider side.
Do you face further issues or have questions. If this is not the case I would close the issue.

Hi, we don't have other questions, case can be closed. Thanks a lot!

Hi, deactivating the user login on sap.default works, but leads to the following error:
Error: Provider produced inconsistent result after apply

When applying changes to btp_subaccount_trust_configuration.default-idp, provider "provider[\"registry.terraform.io/sap/btp\"]" produced an unexpected new value:
 .identity_provider: was cty.StringVal("sap.default"), but now cty.StringVal("").

 This is a bug in the provider, which should be reported in the provider's own issue tracker.

@TVSiemens I created a new dedicated issue for the behavior you reported to avoid mixing up things  in one issue.


check if the backlinks are dofollow

As I got an intresting proposal to actually check wheather the link we're checking is dofollow or not, this should be implemented.
So make sure, that the link which is checked on the website we get the response of is dofollow.
My approach would be:
use beautifulsoup and look for the all links, then check for sponsored and nofollow, which we don't want our backlinks to be.
if this isn't the case, print ok, otherwise print("---link marked as nofollow or sponsored")

I was thinking the same thing.
link = soup.find_all('a', href=""+do_check[1]+"")
try:
rel = link.get('rel')
except AttributeError:
print('is DoFollow') # no rel? is dofollow by default
if rel contains 'no-follow':
print('is NoFollow')

@peterkr10 feel free to solve that issue and pull-request.


how to build im2rec from im2rec.cc on a Windows machine?

For bugs or installation issues, please provide the following information.
The more information you provide, the more likely people will be able to help you.
Environment info
Operating System: Windows 10, x64
Compiler: VS2015
Package used (Python/R/Scala/Julia): c-api
MXNet version:
Or if installed from source: 0.9.4
MXNet commit hash (git rev-parse HEAD):
If you are using python package, please provide
Python version and distribution:
If you are using R package, please provide
R sessionInfo():
Error Message:
I have created a console solution using im2rec.cc and linking it with libmxnet.lib. However the symbols used in im2rec.cc are not exported by libmxnet.lib, producing linker errors. Has anyone being able to build im2rec on Windows and how should it be done? Possible to share the project file?
1 of the 14 unresolved externals:
Severity	Code	Description	Project	File	Line	Suppression State
Error	LNK2019	unresolved external symbol "public: static class dmlc::InputSplit * __cdecl dmlc::InputSplit::Create(char const *,unsigned int,unsigned int,char const *)" (?Create@InputSplit@dmlc@@SAPEAV12@PEBDII0@Z) referenced in function main	Bin2Rec	C:\Projects\MXNet\Examples\Bin2Rec\Bin2Rec\im2rec.obj	1
Minimum reproducible example
if you are using your own code, please provide a short script that reproduces the error.
Steps to reproduce
or if you are running standard examples, please provide the commands you have run that lead to the error.

What have you tried to solve it?

You need to build mxnet your self and create a new vc project and reference the mxnet solution.

This worked out, thanks:)


Migrate useQueue from react-use

What new hook does?
A react state hook implements simple first-in-first-out (FIFO) queue migrated over from react-use
Checklist

[x] Have you read contribution guideline?
[x] Does the code have comments in hard-to-understand areas?
[x] Have the files been linted and formatted?
[x] Is there an existing issue for this PR?

link issue here

[x] Have the docs been updated?
[x] Have the tests been added to cover new hook?
[x] Have you run the tests locally to confirm they pass?

Thanks for the review @ArttuOll. I really hope you'll decide to merge it in. This is my first contribution to open source. I used 'react-use' quite a bit until the SSR bit started biting me in the butt. So I thought "If I want good hooks, might as well start helping out" haha.

I've thought about this and I can't help but think that if this hook is added, it should be implemented with useList, because it is just a limited version of it. That way, if we fix bugs in useList, the bugs would also get fixed in this hook. This is one of the reasons why it's preferrable to compose previously implemented hooks to implement new ones.
Could you do this @jpwallace22 ?

The returned methods required a bit more work in order to be referentially stable, but that's my fault, because the test I gave you was actually faulty! When I wrote the test, I did not take into account that it was actually the invokation of the methods which caused them to get new references instead of just plain rerendering of the component using the hook.

Thanks for taking care of that and explaining it to me as well. Like I said, I'm new to testing and reasonable unfamiliar with referential stability. Though now reading up a lot on it. Everyday is a learning day!

@xobotyi I asked you this once already, but I think you forgot to answer: are other maintainers allowed to merge PRs or do you want everything to go through you?
I know that maintainer's are allowed to merge their own PRs after they've been reviewed by some other maintainer, but that's a different case.

@ArttuOll @xobotyi I'd love to get this merged in. Are there any actionable items I can help with to get it merged?

@ArttuOll it depends on hook tbh) for now let's pass everything through me.

SO!

as this hook does not implement any queue, nor has switch to change the type of queue - it has to be named useFifoQueue or has to be polimorphic, meaning it has to be switchable between fifo\lifo
i would expect list itself to be exposed, to be able to peek the items at any position without need to remove them. I'd expect overall api to be like that:interface UseQueueResponse<T> {
  // internal array itself
  items: T[];
  add: (item: T) => void;
  remove: () => T;
  first: T;
  last: T;
  size: number;
}

Yes it kind of compromises abstraction and allows arbitrary changes to the queue, but it is better as allows weird implementation not covered by base queue algorithm.

@xobotyi Thanks for the feedback! Good callouts all around.
I implemented the feedback by adding a fifo/lilo option. Seemed the better approach than just remaining it and limiting the hook. I also added the items property to the return.
One thing to note, I DID make it LILO and not LIFO as you specified, but I'm 99% sure that was a typo as that wouldn't be a queue. 😆
Let me know if you need anything else 🙌🏽

Looks good to me. I updated the docs a little.

Yes it kind of compromises abstraction and allows arbitrary changes to the queue, but it is better as allows weird implementation not covered by base queue algorithm.

If we want to prevent arbitrary changes to the queue (which btw don't cause a rerender, because useList is used under the hood), we could substitute items with a peek: (n: number) => T[] method.

Despite of getting the point of LILO (the other way of naming FIFO) i'm hearing this obbreviation for the first time.
I'd rather use common names for things that are used in CS - therefore it should be named FIFO

Reading your comment again - LIFO != LILO LIFO is a 'stack' quque, when items pushed to the back and removed from the back, while FIFO is 'line' queue where items pushed to the back and removed from the front.

Reading your comment again - LIFO != LILO LIFO is a 'stack' quque, when items pushed to the back and removed from the back, while FIFO is 'line' queue where items pushed to the back and removed from the front. Both are queues.

I think @jpwallace22  was concerned that LIFO queue is commonly considered to be a stack and thus not suitable for this hook. However, LIFO queue seems to be a synonym for stack (makes sense, of course, when you think about it. I also hadn't ever thought of it this way) so it could be included here.

@ArttuOll @xobotyi At this point, I'm not too sure what you all want done to this. There seems to be a lot of back and forth.
FIFO != LILO. They are both queues, but going in different directions. I have never heard of a stack being called a queue, so I assumed lifo was a type-o. I don't agree with adding the ability lifo for the useQueue. That would go against standard CS language. Would you prefer I remove all the 'lilo' logic and change the name to useFifoQueue?

@jpwallace22 welp here comes language differences =) since both lifo and fifo are queuing containers there comes confusion between CS and natural language🙃
ill tidy things up and merge in couple of hours i hope

:tada: This PR is included in version 20.1.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Split error for nil

I'm getting this error, but I'm not quite sure what I've done wrong or if its a bug in the gem.
NoMethodError: undefined method split' for nil:NilClass 	from /home/carsonwright/.rvm/gems/ruby-2.1.2/gems/ltree_hierarchy-0.0.7/lib/ltree_hierarchy/hierarchy.rb:96:in prevent_circular_paths'

@carsonwright could you describe what you were doing then to help me reproduce this issue? :)

Yes sorry, um I was trying to add a child to a parent
I added a path column with ltree as its type and a parent_id with integer as its type and added an index to parent_id
And placed
has_ltree_hierarchy
in the organization model
Then tried to run the following:
root = Organization.find(1)
Organization.find(2).update_attributes(parent: root)

Thanks! I will take a look as soon as possible!

Thank you

@carsonwright I wasn't able to reproduce the issue :(
Could you run:
\d organizations
and
SELECT * FROM organizations WHERE id IN (1, 2)
?

     Column         |            Type             |                         Modifiers

------------------------+-----------------------------+------------------------------------------------------------
id                     | integer                     | not null default nextval('organizations_id_seq'::regclass)
parent_organization_id | integer                     |
created_at             | timestamp without time zone |
updated_at             | timestamp without time zone |
path                   | ltree                       |
parent_id              | integer                     |
Indexes:
"organizations_pkey" PRIMARY KEY, btree (id)
"index_organizations_on_parent_id" btree (parent_id)
"index_organizations_on_parent_organization_id" btree (parent_organization_id)

id | parent_organization_id |        created_at         |         updated_at         | path | parent_id
----+------------------------+--------+----------+------+--------------+-------+------------------+-----------+
1 |                    |  2015-08-07 20:39:02.792114 | 2015-08-21 06:21:50.638611 |      |
2 |                 1 |  2015-08-07 20:39:49.742189 | 2015-08-21 18:07:55.590456 |      |

Ok so I understand now I had data already created, and that data did not have its own id as the path so it was breaking everything

Thank you for your help

Oh, it looks like so! I didn't have time to look at this. Glad it's all solved now!


remove kata rpm version

Type of change
Note: Fill x in []

[ ] bug
[ ] enhancement
[ ] documentation
[ ] dependencies

Description

For security reasons, all pull requests need to be approved first before running any automated CI

Duplicate PR


we are not using the correct UA string

The user agent should be / number. The version number should be the same that is used in setup.py (not just the value - please import the same variable - typically something like from .version import VERSION)


Prepare GG manifests and integrate with pygluu

helm chart was committed by accident and should be fixed in next commit


Popup editing for QTable

See https://quasar.dev/vue-components/table#popup-editing
Sry, if this already possible.
An old discussion: https://discourse.julialang.org/t/editable-table-using-stipple-ui/71854

That is possible using templates. But since today we have an option edit = true, which allows you to edit the table.
If you just want to edit certain columns you can write edit = ["column1", "column2"].
Styling is also possible, see the docstrings of table and cell_template.


Question about behavior working with Models

Hi @troyanskiy
I'm working with the ResourceModel and I was thinking if exist a way to use this behavior:
//Create a new instance of RsourceModel
let resource = new User();
//Setting the attributes
resource.username = "juliowar";
// Sending to the server
resource.$save();

Correct me if I'm wrong, but actually the behavior only works in this case:
//Get user
this.user = this.userResource.get({id: 1});

//change and save user
this.user.first_name = 'Bob'
this.user.$save()

Thanks, I will be in touch.

Hello @JulioWar
Sorry for the delay.
In your case you should use static method create.
//Create a new instance of RsourceModel
// First param is initial data and second is to send the request to server immediately (default is true)
let resource = User.create({}, false);
//Setting the attributes
resource.username = "juliowar";
// Sending to the server
resource.$save();

Shorter
let resource = User.create({username: "juliowar"});

Don't worrry @troyanskiy. Thanks for the solution.


github.com/GoASTScanner/gas install path is incorrect

This repository seems to have been updated, and the correct install path is now github.com/GoASTScanner/gas/cmd/gas in order to build the binary.

Note that this should not impact installation of gas if you're using the bundled version. We do this specifically to avoid issues like this.
That said, we should update our vendored version at some point to point to the new location.


Cors issue

Search before asking

[X] I searched in the issues and found nothing similar.

Version
using the 2.10 version
Minimal reproduce step
We are creating a react Application for publishing the message in the topic using the post https://pulsar.apache.org/docs/next/client-libraries-rest/   method but we are facing a Cors issue. Tried to fix that issue by changing the configuration files using the following steps:

we are changing the broker.config file add set Access-Control-Allow-Origin "*".
Also change standalone.conf  file add allowedOrigins=http://<IP_ADDRESS>:8080/, http://<IP_ADDRESS>:5174/ and:

# Enable the WebSocket API service in broker
webSocketServiceEnabled=true

But we can't publish the message on that topic.
Error:
Access to XMLHttpRequest at 'http://<IP_ADDRESS>/topics/persistent/dev/compsource/policy_change_stat' from origin 'http://<IP_ADDRESS>:5174' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.

Request Header:
Request URL: http://<IP_ADDRESS>/topics/persistent/dev/compsource/policy_change_stat
Referrer Policy: strict-origin-when-cross-origin
What did you expect to see?
It should allow  to connect and publish the message in that topic
What did you see instead?
Getting cors error in the post method when we send to the pulsar topic
Anything else?
No response
Are you willing to submit a PR?

[ ] I'm willing to submit a PR!

@gk0307 Can you provide a minimal reproduce repo? I don't find Access-Control-Allow-Origin config in broker.conf and also other configs.

Closing as stale. If it's still relevant to maintained versions, feel free to open a new issue with reproduce.


Hitting Segmentation fault when running Vitest .

Describe the bug
When I run vitest on without limiting the threads, the process will crash half way through with the following output:
Segmentation fault (core dumped)
error Command failed with exit code 139.

Reproduction
https://github.com/OpenQDev/OpenQ-Frontend/tree/vite-staging
I can't really provide a minimal reproduction because it seems to depend on the number of tests you run. To reproduce it with this repo just run yarn then, run yarn json-server in one terminal and then yarn vitest in another.
System Info
System:
    OS: Linux 5.4 Ubuntu 20.04.5 LTS (Focal Fossa)
    CPU: (16) x64 Intel(R) Xeon(R) Platinum 8272CL CPU @ 2.60GHz
    Memory: 26.75 GB / 31.36 GB
    Container: Yes
    Shell: 5.0.17 - /bin/bash
  Binaries:
    Node: 19.7.0 - ~/nvm/current/bin/node
    Yarn: 1.22.19 - /usr/bin/yarn
    npm: 9.5.0 - ~/nvm/current/bin/npm
  npmPackages:
    @vitejs/plugin-react: ^3.1.0 => 3.1.0
    vitest: ^0.29.8 => 0.29.8

Used Package Manager
yarn
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Facing the same here. Really blocking our build flows.
In our case we're facing this issue when running the tests on a github action

My work around at the moment has been to run it with the --no-threads flag when in circleci, but that slows down the workflow a lot.
Locally it works if for us if we are just testing a portion of the code base as long as we limit the threads to 1 or 2.

Potentially similar root cause/duplicate of https://github.com/vitest-dev/vitest/issues/3143
Do you have a promise that sometimes rejects in your tests, similar to the reproduction on the linked issue?

We're potentially hitting this in Github Actions as well, works fine locally though... @nakleiderer did you mean to link to a different issue?

@adrianisk Yes, apologies, I've updated the original comment. This is the link I meant to use: https://github.com/vitest-dev/vitest/issues/3106

We have the same issue. Works fine locally, but in CI on GitHub Actions we have to run sequentially with the --no-threads flag.

We're also hitting this issue which happened when we introduced an @aws-sdk dependency. I happened to stumble upon https://github.com/awslabs/aws-crt-nodejs/issues/452 while looking into something else, might be related?

Same here.

Can be fixed by setting threads in vite.config.ts to false, until a better solution is found.

Instead of disabling threads option completely, you could also move only the @aws-sdk related test cases to node:child_process. This way all other tests are running in node:worker_threads fast as usual, and the ones that are not compatible with node:worker_threads are run in node:child_process.
Use the poolMatchGlobs option:
import { defineConfig } from 'vitest/config'

export default defineConfig({
  test: {
    poolMatchGlobs: [
      // Run AWS tests in child_process - @aws-sdk crashes when run in 'node:worker_threads'
      ['**/tests/aws-infra-etc-pattern/**', 'child_process'],
    ]
  }
})

On repeatability, I can repeat this in a docker container with just 1 test.And indeed using @aws-sdk.

Fixed by https://github.com/vitest-dev/vitest/pull/3925 and https://github.com/vitest-dev/vitest/pull/4172.
Vitest 1.0.0-beta has now --pool=forks which uses multiple node:child_process in parallel. The previous --no-threads was using a single node:child_process.
If the code you are testing is incompatible with node:worker_threads, switch to --pool=forks. If you run into same error with that pool, feel free to open new issue with minimal reproduction.


[BUG] - Quick Start Instructions broken

Describe the bug
Running
conda install -c conda-forge conda-store conda-store-server
conda-store-server  --standalone

as instructed from https://conda.store/conda-store/introduction#quickstart
yields
ModuleNotFoundError: No module named 'conda_lock'
Installing conda_lock fixed the issue
Expected behavior
conda store UI should be launched
How to Reproduce the problem?
see above
Output
No response
Versions and dependencies used.
2024.1.1 of conda-store
Anything else?
No response

This is to be fixed in this PR though I have not had time to finish it off https://github.com/conda-incubator/conda-store/pull/801/files#diff-2798205d73e8179f7cd9fbc9da2c6446c88c25f80180a50971c37ea9c345c8f5

Fixed already


Component generator should use module name as tag name

donejs add my/component should use my-component as the tag name.

Closed via #78


usersForFuzzyName expects user.name to exist when it may not

In some cases, there may be user data missing the name property, but usersForFuzzyName does not check to ensure this and instead throws an error:
ERROR TypeError: Cannot read property 'toLowerCase' of undefined
   at Brain.usersForRawFuzzyName (/app/node_modules/hubot/src/brain.coffee:135:7, <js>:123:22)
   at Brain.usersForFuzzyName (/app/node_modules/hubot/src/brain.coffee:144:20, <js>:132:27)

In what scenario would the name property be missing?

In my case, name is missing either because the user data is being overwritten by redis-brain or by hubot-slack.
It seems that once redis connects and robot.brain is populated there are some items in that list that do not have the name property.
Tomorrow I'll do a little more debugging to see why.

Calling this a bug for now, though it derives largely from a poorly defined interface on the User class. Is name a required and expected property (i.e. doesn't need to be checked everywhere) or an optional property that should be gracefully handled when missing?
I think it is an expected property based on the code (hence the bug label), but I'm intrigued if there is a reason why the Slack adapter is producing User objects without a name.

Even if it is a bug, I would be :+1: to some defense around users here, since adapters need to fill that in and we can't always control it. If we want to be prickly about it, we could just throw an error blaming the adapter. But there's no reason to be ornery unless this cascades into 10 other places with the same assumption.
@mshwery, since I'm not sure how to replicate this, are you willing to put together a PR with a guard for the nil case? Just to see how deep the rabbit hole goes?

@michaelansel hm, that actually makes this issue seem even more unusual – I hadn't dug into the User constructor, but it seems unless explicitly removed, a user object should have a name.
I have a fork looking at this issue to see if I can nail it to hubot-slack or something else, but haven't had time to get to it yet.
I would happily PR it @bhuga, hopefully sooner than later.

In my case, name is missing either because the user data is being overwritten by redis-brain or by hubot-slack.
I have a fork looking at this issue to see if I can nail it to hubot-slack or something else, but haven't had time to get to it yet.

I ran into something similar with the hubot-slack adapter actually. Slack was sending back a user without a profile. https://github.com/slackhq/hubot-slack/pull/232 is the PR to fix it, and that's released now.


Deployment location

All the commands used to deploy the template require a region - in the samples it's just referred to as <AzureRegion>. My initial assumption was that it had to be in the same region as the resources access is being given to, but experiments show this not to be the case.
Does the region the deployment is created in have any real bearing on the authorization process? Are there any surprises that might come up later if the regions are different?

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

ID: 85dc331a-0f34-f9a2-43d9-8ab7e0e635c6
Version Independent ID: 96c07c81-f84c-f47b-659c-b3d055aefb03
Content: Onboard a customer to Azure delegated resource management - Azure Lighthouse
Content Source: articles/lighthouse/how-to/onboard-customer.md
Service: lighthouse
GitHub Login: @JnHs
Microsoft Alias: jenhayes

@mikegoatly Thanks for the feedback! We are currently investigating and will update you shortly.

Hi @mikegoatly - The location is for the deployment resource itself, that needs to target an Azure region. The resources being created as part of the deployment will not be bound to this location, nor any coupling to the actual deployment.

For example, if I have a deployment resource in Central US that is deploying resources into North Europe, then the only inter-region communications that would take place are the necessary Resource Manager API calls made from the US to Europe?
In which case, once the deployment is complete there would be no further interactions between the deployment resource and deployed resources, which I think is what I'm actually trying to understand!

@mikegoatly That's correct - no further interactions after the deployment is completed!

We will close the issue for now. If there are further questions , please revert and we will be glad to assist you.


Fixed C++ compilation in C literal in call to SetShapesTexture

This fixes the same problem mentioned in #33, but I guess this particular line was introduced later.
I see there's RAYGUI_CLITERAL but also CLITERAL from raylib, is there a reason for this distinction?

@codecat thanks for the review!
The distinction us because, despite raygui depends a lot on raylib, other backends could be  added (RAYGUI_STANDALONE) and raylib could be not included...


chore(deps): bump ethers

Motivation
bump ethers for #3899

Solution

#3899 has fixes for breaking changes.


ClearCommand is (still) Missing

Hi!
php artisan

Is complaining
Class Gtk\Larasearch\Console\ClearCommand does not exist

Did some digging and found out that there is no ClearCommand class in console folder! ?? Am I the only one here?

@sevmardi It was changed to FlushCommand. reference: #3

yep the error still exist

@mouhsinelonly you can use 1.1.3 to avoid that


Bump agent version

Upgraded the agent version to v0.0.4-beta1.
See https://github.com/mariadb-operator/agent/pull/5#pullrequestreview-1727838242

I replaced the agent module import to my fork to check if the test passed. Will remove the replace directive once we tag a new version 👍🏼


Revert "Add docs survey link to site header"

This reverts commit 4a7f2192f9cf95f0c8fa4b0742eb472c13ee2859.
Adding the link breaks mobile

By analyzing the blame information on this pull request, we identified @bestander and @skevy to be potential reviewers.

How about fixing it instead? :)
I think if you use '&nbsp' instead of spaces it won't break into multiple lines.
And we could temporarily remove another link to free up space.
And also use media queries to style it for small screens if necessary

@bestander .... @vjeux is suggesting and coming up with a more amenable solution/fix right now I think...

@facebook-github-bot shipit

Thanks for importing. If you are an FB employee go to Phabricator to review.


Replace link to image folder

Resolves #52

I'm new here and start as Web Dev.any one help me please.
Singh-ux


Needless line breaks injected

    let searchSpace = [currentDirectory.path] + (
      ProcessInfo.processInfo.environment["PATH"] ?? ""
    ).split(separator: pathSeparator).lazy.map(String.init)

It's confounding that swift-format forces a line break after the = in this case, and then rearranges everything else.  Is there any way to turn that off?

Not as something easily configurable today. We have logic that determines whether something on the RHS of an assignment is a "complex expression", so things like a single function call would remain on the same line:
let foo = bar(
   some, really, long, arguments)

But a multi-term expression with infix operators would be wrapped before the expression:
let foo =
  bar(x, y) + baz(a, b, c)

IMO, I wouldn't mind being more prescriptive here and always wrapping after the = if any part of the RHS wraps, à la the rectangle rule, but that's probably controversal. And, there are always exceptions (it would be silly to wrap between the = [ of a multi-line collection literal).
So I'm open to considering refinements to the logic we have today, but we'd have to make sure that it doesn't have adverse side effects elsewhere.

FWIW, this "complex expression" consideration does not correspond to anything I use when deciding where to break lines, and it clashes with what I consider to be optimal formatting in several cases.  Rewinding to the origin of the line-breaking rules (which may no longer be relevant—but are something I know well 😉), the point was to enforce what's required to get basic readability, make efficient use of space, and avoid situations that will cause reformatting busywork on other lines when one line changes, while being easy to follow.  The point of my insistence on a "discretionary line breaks" option is that below the level of my rule, humans often have information they can use to convey more about the meaning of the code, and can usually be trusted not to put every token on its own line.
The "complex expression" consideration is vague (not documented AFAICT) and makes it hard for humans to follow the rules without using a tool.  I'm not particularly that your example above is better than the alternative, and it's easy for me to think of cases where it's clearly suboptimal, so I'm dubious of its value:
let foo =
  somethingUnlikeTheOtherTerms(x, y) + bar(a, b, c)
   + baz(a, b, c) + qux(a, b, c)

really should be
let foo = somethingUnlikeTheOtherTerms(x, y)
   + bar(a, b, c) + baz(a, b, c) + qux(a, b, c)

Because it also clashes with my discretion around line breaks, it should at least be disabled when discretionary line breaks are allowed.  If you really, really believe in its value, you could say that with discretionary breaks on, lines following the other rules will be left alone but a line that the tool must wrap has the "complex expression" heuristic applied.


[FEATURE] Typlog image content

https://blog.typlog.com/images
Can you please add support for this?
It allows for easily organizing images in content, making them fit properly in page.
It was also implemented in hugo for this theme:
https://docs.stack.jimmycai.com/writing#insert-image
https://github.com/CaiJimmy/hugo-theme-stack/

https://blog.typlog.com/images
Can you please add support for this?
It allows for easily organizing images in content, making them fit properly in page.
It was also implemented in hugo for this theme:
https://docs.stack.jimmycai.com/writing#insert-image
https://github.com/CaiJimmy/hugo-theme-stack/

I'll choose to upgrade LightGallery to version 2 instead of using this

@khusika

I'll choose to upgrade LightGallery to version 2 instead of using this
https://www.lightgalleryjs.com/

Wow, that looks great! LightGallery v2 would indeed be preferable over Typlog.


Latest Articles

Regarding the articles section we can either add the logo of the news channels that have shared the stories or we can use the headlines. Ideally we don't add boxes as it looks cleaner and more refined.

Isn't it better to select a few articles and add them to the homepage instead of listing the logo of the news?
I can't see the screenshot that you shared, but if you guys have a few links, news articles, or any specific design in your mind, please share so I can add them.


Add the commit ID key as constant for log label

Fixes: https://github.com/knative/serving/issues/1934
From https://github.com/knative/serving/pull/2371:

introduce a lib in pkg to read GitHub commit ID from "$KO_DATA_PATH/HEAD".
Use the lib to add the first 7 bits as logs label.

/assign @mattmoor


Implement OAuth Authentication (GitHub & Google) and Email/Password Login, Registration Page and Login Page

Description
This PR introduces GitHub OAuth, Google OAuth, and email/password authentication methods across both the frontend and backend.
Frontend:

Created a login page with options for GitHub OAuth, Google OAuth, and email/password login.
Integrated GitHub and Google OAuth login flows in the frontend, including token handling and user details display after successful login.
Added error handling for invalid login credentials and empty fields in the email/password login form.

Backend:

Implemented the GitHub OAuth authentication API to handle user login via GitHub, including token exchange and user info retrieval from GitHub.
Implemented the Google OAuth authentication API to handle user login via Google, with token exchange and user info retrieval from Google.
Created email/password login and registration APIs, including password hashing, email validation, and error handling for missing or incorrect credentials.
Updated the user model to store GitHub ID, Google ID, and password.

Database:

Modified the user schema to support OAuth credentials (GitHub and Google), in addition to email/password authentication.
Ensured secure password storage using bcrypt hashing.

Related Issue
#108
Motivation and Context
This change introduces multiple authentication options to make the application more flexible and secure. By adding OAuth integrations for GitHub and Google alongside the traditional email/password login, users can authenticate via their preferred method. This enhances user experience and makes the application more accessible.

Screenshots (In case of UI changes):

Login Page

Registration Page:

Types of changes

[x] New feature (non-breaking change which adds functionality)

Checklist:

[x] My code follows the code style of this project.
[x] All new and existing tests have passed and it does not give any unexpected errors.

Demo
https://github.com/user-attachments/assets/80e77e8f-2557-4e31-9c89-dbbfc6b309c7

@rajutkarsh07 Please review this PR

ENV File Format
To get Google OAuth working, you'll need to generate an mkcert as Google OAuth allows only HTTPS requests.
Here's the .env file setup for the server:
PORT=5100
MONGODB_URI=
JWT_SECRET=
GITHUB_ACCESS_TOKEN=
# Google OAuth
GOOGLE_CLIENT_ID=
GOOGLE_CLIENT_SECRET=
GOOGLE_REDIRECT_URI=

# GitHub OAuth
GITHUB_CLIENT_ID=
GITHUB_CLIENT_SECRET=
GITHUB_REDIRECT_URI=

SSL_KEY_PATH=
SSL_CERT_PATH=


Build: Add script to bump copyright year

Note: Please transform - [ ] into - (NA) in the description when things are not applicable
Related issues
Closes #13.
Description
Change the year of copyright.
The regex might be rethought for the project, but it seems to work pretty well here.
Motivation & Context
Ease maintenance and avoid to forget a file during the bump.
Types of change

New feature (non-breaking change which adds functionality)

Test checklist

[ ] Check by changing ${new Date().getFullYear()} by 2021 for example and run npm run copyright. Then check all the changes.

My bad on this, I realized just before committing that the All was missing to replace all occurrence in one file, I forgot to rerun. It should be good now.


Add logging to LoadBalancedFargateService

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license.

Approved modulo naming.


ios   build  failed

[Uploading 屏幕快照 2015-11-18 下午3.51.32.png…]
xcode 6.3.1     build  Failed

Do you solve your problem?

yes


Check for CPU cores and free memory in IT script

This fixes #3859
Signed-off-by: Chong Gao<EMAIL_ADDRESS>

build

since most of our nightly IT tests are in docker, the cpu num and mem size you see is the value of the host but not for the container which means you can hardly get the real limitation value (cgroup on host) here,
For memory, you may get it in docker but it varies differently in different linux kernel
/sys/fs/cgroup/memory/memory.limit_in_bytes (4.x-sth)
/sys/fs/cgroup/memory.max (5.x-sth)
I would recommend to not rely on /proc info here, and take the cpu_cores and mem_size as ENV variable for this script

Updated, please review again.

build

since most of our nightly IT tests are in docker, the cpu num and mem size you see is the value of the host but not for the container which means you can hardly get the real limitation value (cgroup on host) here,
For memory, you may get it in docker but it varies in different linux kernels /sys/fs/cgroup/memory/memory.limit_in_bytes (3.x-sth) /sys/fs/cgroup/memory.max (5.x-sth)
I would recommend to not rely on /proc or other system info here, take the cpu_cores and mem_size from ENV variables if any (could give them some conservative defaults and let people to increase the value if needed), and then do the calculation in this script~

If set TEST_PARALLEL, this code will not invoke.
As I know premerge always set TEST_PARALLEL.
   if [[ "${TEST_PARALLEL}" == "" ]]; then
   ......   // code changes
   fi

since most of our nightly IT tests are in docker, the cpu num and mem size you see is the value of the host but not for the container which means you can hardly get the real limitation value (cgroup on host) here,
For memory, you may get it in docker but it varies in different linux kernels /sys/fs/cgroup/memory/memory.limit_in_bytes (3.x-sth) /sys/fs/cgroup/memory.max (5.x-sth)
I would recommend to not rely on /proc or other system info here, take the cpu_cores and mem_size from ENV variables if any (could give them some conservative defaults and let people to increase the value if needed), and then do the calculation in this script~

If set TEST_PARALLEL, this code will not invoke. As I know premerge always set TEST_PARALLEL.
   if [[ "${TEST_PARALLEL}" == "" ]]; then
   ......   // code changes
   fi

@pxLi

that was a workaround here, we would like to also benefit from auto-resource detection and auto-math here if any stable ones. But I am fine to keep setting TEST_PARALLEL by experience for now

build


HBASE-25012 HBASE-24359 causes replication missed log of some RemoteE…

…xception

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
2m 31s
Docker mode activated.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 57s
the patch passed

+1 :green_heart:
compile
1m 17s
the patch passed

+1 :green_heart:
javac
1m 17s
the patch passed

+1 :green_heart:
shadedjars
8m 12s
patch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 45s
hbase-server in the patch failed.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
5m 28s
the patch passed

+1 :green_heart:
compile
1m 27s
the patch passed

+1 :green_heart:
javac
1m 27s
the patch passed

+1 :green_heart:
shadedjars
9m  1s
patch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 48s
hbase-server in the patch failed.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 38s
the patch passed

+1 :green_heart:
compile
1m 18s
the patch passed

+1 :green_heart:
javac
1m 18s
the patch passed

+1 :green_heart:
shadedjars
7m 29s
patch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 43s
hbase-server in the patch failed.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 36s
the patch passed

+1 :green_heart:
compile
1m 19s
the patch passed

+1 :green_heart:
javac
1m 19s
the patch passed

+1 :green_heart:
shadedjars
7m 33s
patch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 43s
hbase-server in the patch failed.


distributed training on two machine gets error when load checkpoint

Describe the bug
I'm trying to run distributed training on two machine with 3 gpu cards each, distributed training on single node works fine, but when using the launch utility to distributed training on two machines, I got
Reproduction
run script tools/dist_train_master.sh on master node:
#!/usr/bin/env bash

PYTHON=${PYTHON:-"python"}

CONFIG=$1
GPUS=$2

$PYTHON -m torch.distributed.launch --nproc_per_node=$GPUS --nnodes=2 --node_rank=0 --master_addr="<IP_ADDRESS>" \
   --master_port=7008 $(dirname "$0")/train.py $CONFIG --launcher pytorch ${@:3}

run script tools/dist_train_worker.sh on worker node:
#!/usr/bin/env bash

PYTHON=${PYTHON:-"python"}

CONFIG=$1
GPUS=$2

$PYTHON -m torch.distributed.launch --nproc_per_node=$GPUS --nnodes=2 --node_rank=1 --master_addr="<IP_ADDRESS>" \
   --master_port=7008 $(dirname "$0")/train.py $CONFIG --launcher pytorch ${@:3}

error on master:
2019-07-31 09:39:04,485 - INFO - Distributed training: True
2019-07-31 09:39:05,466 - INFO - load model from: modelzoo://resnet50
Traceback (most recent call last):
  File "./tools/train.py", line 106, in <module>
    main()
  File "./tools/train.py", line 84, in main
    cfg.model, train_cfg=cfg.train_cfg, test_cfg=cfg.test_cfg)
  File "/home/wangtao/prj/_mmdetection/mmdetection/mmdet/models/builder.py", line 43, in build_detector
    return build(cfg, DETECTORS, dict(train_cfg=train_cfg, test_cfg=test_cfg))
  File "/home/wangtao/prj/_mmdetection/mmdetection/mmdet/models/builder.py", line 15, in build
    return build_from_cfg(cfg, registry, default_args)
  File "/home/wangtao/prj/_mmdetection/mmdetection/mmdet/utils/registry.py", line 74, in build_from_cfg
    return obj_type(**args)
  File "/home/wangtao/prj/_mmdetection/mmdetection/mmdet/models/detectors/mask_rcnn.py", line 31, in __init__
    pretrained=pretrained)
  File "/home/wangtao/prj/_mmdetection/mmdetection/mmdet/models/detectors/two_stage.py", line 57, in __init__
    self.init_weights(pretrained=pretrained)
  File "/home/wangtao/prj/_mmdetection/mmdetection/mmdet/models/detectors/two_stage.py", line 65, in init_weights
    self.backbone.init_weights(pretrained=pretrained)
  File "/home/wangtao/prj/_mmdetection/mmdetection/mmdet/models/backbones/resnet.py", line 484, in init_weights
    load_checkpoint(self, pretrained, strict=False, logger=logger)
  File "/home/wangtao/anaconda3/envs/open-mmlab/lib/python3.7/site-packages/mmcv/runner/checkpoint.py", line 137, in load_checkpoint
    checkpoint = load_url_dist(model_urls[model_name])
  File "/home/wangtao/anaconda3/envs/open-mmlab/lib/python3.7/site-packages/mmcv/runner/checkpoint.py", line 101, in load_url_dist
    torch.distributed.barrier()
  File "/home/wangtao/anaconda3/envs/open-mmlab/lib/python3.7/site-packages/torch/distributed/distributed_c10d.py", line 1358, in barrier
    work = _default_pg.barrier()
RuntimeError: NCCL error in: /opt/conda/conda-bld/pytorch_1556653114079/work/torch/lib/c10d/ProcessGroupNCCL.cpp:272, unhandled cuda error
Traceback (most recent call last):
  File "/home/wangtao/anaconda3/envs/open-mmlab/lib/python3.7/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/wangtao/anaconda3/envs/open-mmlab/lib/python3.7/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/home/wangtao/anaconda3/envs/open-mmlab/lib/python3.7/site-packages/torch/distributed/launch.py", line 235, in <module>
    main()
  File "/home/wangtao/anaconda3/envs/open-mmlab/lib/python3.7/site-packages/torch/distributed/launch.py", line 231, in main
    cmd=process.args)
subprocess.CalledProcessError: Command '['/home/wangtao/anaconda3/envs/open-mmlab/bin/python', '-u', './tools/train.py', '--local_rank=0', 'configs/mask_rcnn_r50_fpn_1x.py', '--launcher', 'pytorch']' returned non-zero exit status 1.

error on worker:
Traceback (most recent call last):
  File "./tools/train.py", line 106, in <module>
    main()
  File "./tools/train.py", line 84, in main
    cfg.model, train_cfg=cfg.train_cfg, test_cfg=cfg.test_cfg)
  File "/home/wangtao/prj/_mmdetection/mmdetection/mmdet/models/builder.py", line 43, in build_detector
    return build(cfg, DETECTORS, dict(train_cfg=train_cfg, test_cfg=test_cfg))
  File "/home/wangtao/prj/_mmdetection/mmdetection/mmdet/models/builder.py", line 15, in build
    return build_from_cfg(cfg, registry, default_args)
  File "/home/wangtao/prj/_mmdetection/mmdetection/mmdet/utils/registry.py", line 74, in build_from_cfg
    return obj_type(**args)
  File "/home/wangtao/prj/_mmdetection/mmdetection/mmdet/models/detectors/mask_rcnn.py", line 31, in __init__
    pretrained=pretrained)
  File "/home/wangtao/prj/_mmdetection/mmdetection/mmdet/models/detectors/two_stage.py", line 57, in __init__
    self.init_weights(pretrained=pretrained)
  File "/home/wangtao/prj/_mmdetection/mmdetection/mmdet/models/detectors/two_stage.py", line 65, in init_weights
    self.backbone.init_weights(pretrained=pretrained)
  File "/home/wangtao/prj/_mmdetection/mmdetection/mmdet/models/backbones/resnet.py", line 484, in init_weights
    load_checkpoint(self, pretrained, strict=False, logger=logger)
  File "/home/wangtao/anaconda3/envs/open-mmlab/lib/python3.7/site-packages/mmcv/runner/checkpoint.py", line 137, in load_checkpoint
    checkpoint = load_url_dist(model_urls[model_name])
  File "/home/wangtao/anaconda3/envs/open-mmlab/lib/python3.7/site-packages/mmcv/runner/checkpoint.py", line 101, in load_url_dist
    torch.distributed.barrier()
  File "/home/wangtao/anaconda3/envs/open-mmlab/lib/python3.7/site-packages/torch/distributed/distributed_c10d.py", line 1358, in barrier
    work = _default_pg.barrier()
RuntimeError: NCCL error in: /opt/conda/conda-bld/pytorch_1556653114079/work/torch/lib/c10d/ProcessGroupNCCL.cpp:272, unhandled cuda error

Did you make any modifications on the code or config? Did you understand what you have modified?
NO
What dataset did you use?
Default COCO dataset
Environment

OS: Ubuntu 16.04.4 LTS
GCC  5.4.0
PyTorch version 1.1.0
How you installed PyTorch conda install -c pytorch pytorch torchvision -y
GPU model RTX2080ti
CUDA and CUDNN version CUDA9.0 cudnn 7.2
[optional] Other information that may be related (such as $PATH, $LD_LIBRARY_PATH, $PYTHONPATH, etc.)

Thanks for reporting! We will look into that.

You may want to check your NCCL.https://github.com/pytorch/pytorch/issues/17349

Thank you. but the issue seems been removed?

Have you checked the pytorch version in different nodes, they must be same.
When I install pytorch-nightly in one node and pytorch-1.1.0 in another node, I encounter the same error as yours. However, when I replace pytorch-nightly with pytorch-1.1.0, the program runs successfully.
My nccl version is 2402, you can check it using command torch.cuda.nccl.version().

yes, I'm using the same conda created environment on the two nodes with pytorch 1.1.0, and I'm also using nccl 2402. So it seems it is not caused by different pytorch version. I'm wondering if you use similar script to launch the training on different nodes?

Yes, this is my scripts. I just change the ip address of master node. I first run the script on master node, wait for some seconds, and then run the scipt on worker node.
On master node:
#!/usr/bin/env bash

PYTHON=${PYTHON:-"python"}

CONFIG=$1
GPUS=$2

$PYTHON -m torch.distributed.launch --nproc_per_node=$GPUS --nnodes=2 --node_rank=0 --master_addr="<IP_ADDRESS>" \
   --master_port=7008 $(dirname "$0")/train.py $CONFIG --launcher pytorch ${@:3}

On worker node:
#!/usr/bin/env bash

PYTHON=${PYTHON:-"python"}

CONFIG=$1
GPUS=$2

$PYTHON -m torch.distributed.launch --nproc_per_node=$GPUS --nnodes=2 --node_rank=1 --master_addr="<IP_ADDRESS>" \
   --master_port=7008 $(dirname "$0")/train.py $CONFIG --launcher pytorch ${@:3}

Thanks for sharing the scripts, I'm wondering do you have same cuda and nvidia-driver version on master and worker nodes? what is their version and GPU model?

Yes.  nvidia smi Driver Version: 396.24.  nvcc version: 9.0, V9.0.176.  cudnn version: 7.1.1


refactor(kernels::grisubal): rewrite step 1 to enable parallelization

there are two main changes to make it happen:

split the main iterator in two, to compute and preallocate intersection metadata vector, allowing edition of the vector with no pushes
rewrite the second part of the iterator to collect (K, V) pairs directly into the Hashmap rather than insert each manually

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

Project coverage is 82.18%. Comparing base (d79671f) to head (48105a5).

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #210      +/-   ##
==========================================
+ Coverage   82.04%   82.18%   +0.14%
==========================================
  Files          41       41
  Lines        5681     5727      +46
==========================================
+ Hits         4661     4707      +46
  Misses       1020     1020

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

I think I will split the kernel.rs file into a module in a separate PR. the file is starting to be very long, and each step are starting to contain many substeps


CC-1391: Figure out why CI tests end early for Kotlin (SQLite)

I didn't end up figuring out why it happened, but this PR fixes the issue by:

Logging out everything about the file stream. It beats me why simply observing it can banish the phantom, but silent exits just won't repeat themselves anymore.

Adding sanity check which will fail the job if course-sdk test silently quits again and leaves no tester artifact behind.

Will look at this today!

Will look at this today!

@rohitpaulk If you need to run the updated workflow, just point test_course_definition in test.yml in sqlite course to "andy1li/course-sdk/.github/workflows/test-course-definition.yml@main"

Fixed by https://github.com/codecrafters-io/course-sdk/commit/aa786a8131de325563a9eec3b77be91a6573410b


Warning ouput when building from source

Context & versions
When following the 'building from source' steps, the output shows (below image). This is confusing an creates the idea that something was incorrect.

Will be fixed within the changes for the HF. See the following commit: https://github.com/cardano-foundation/cardano-rosetta-java/pull/233/commits/5481799545af37740f23cb4a2a71edcf827a41b7


Publish voxel sandcastles

Description
This PR moves the two voxel-related Sandcastles from the /development subfolder into the main /gallery. These Sandcastles will now appear on sandcastle.cesium.com for easier testing and linking from documentation.
Along the way, some of the Sandcastle code was cleaned up to remove dead code and use more concise syntax.
The relevant Sandcastles are:
Voxels.html. This CustomShader was updated to render with transparency, to highlight our support of that feature.

VoxelPicking.html. This one renders the voxels fully opaque and demonstrates the lighting capabilities added in https://github.com/CesiumGS/cesium/pull/11875.

Issue number and link
Resolves https://github.com/CesiumGS/cesium/issues/11886.
Testing plan
Load the Voxels and Voxel Picking Sandcastles and verify that the different shapes and input data types are rendered correctly, and that Voxel Picking works, as described in https://github.com/CesiumGS/cesium/pull/11828.
Author checklist

[x] I have submitted a Contributor License Agreement
[x] I have added my name to CONTRIBUTORS.md
[ ] I have updated CHANGES.md with a short summary of my change
[x] I have added or updated unit tests to ensure consistent code coverage
[x] I have update the inline documentation, and included code examples where relevant
[x] I have performed a self-review of my code

I spotted some warnings in the picking example but I can't reproduce... Might've been a weird one-off but figured I'd comment it

This is looking good to me! Thanks @jjhembd, and thanks @jjspace!


How to use It?

: )

Can you see the Qs？

@MapMaths

Sorry, this project is delayed and it won't continue for maybe a long time


Elb

This is a remake of #92 with signed off commits. Running CI before merging.

@chuckha looks like Jenkins failed ...

I changed the default to internet facing so there should be no change now. It's configurable so it should work with @danhartfiction's networking setup, but the default should be internet-facing for a new vpc.


Compatibility Issue with UnityEngine.Windows.Speech namespace ?

Hello, I'm posting this in a few places as I'm not sure exactly who is the culprit for this issue.
I'm making a VR training app and the target platform is Standalone>Windows. I'm using Unity 2020.3 and OpenXR. See below for specific versions.
I have a script that uses the UnityEngine.Windows.Speech namespace that lets me subscribe to the PhraseRecognizedDelegate OnPhraseRecognized event. ( this API is part of the UnityEngine.CoreModule.dll )
My Issue: Everything works great EXCEPT when I have WMR headset connected and the WMR Portal running with Mixed Reality OpenXR runtime.
I have tested that my voice commands DO work fine when running in editor (without WMR headset attached), as a built .exe (again without WMR headset attached), AND even works with Oculus Quest (via Link and the Oculus OpenXR runtime.)
My voice commands DO NOT work with either HP Reverb G1 or G2 and running the WMR portal and the Mixed Reality OpenXR runtime.
I have verified that the microphone device is working as I created a simple echo script that plays what the microphone hears back to me.
As another data point I have an older VR project that I built with Unity 2019.4 with the same target but that uses the Windows Mixed Reality plugin (not OpenXR). The voice commands DO work fine in that app.
So this kinda points me to some problem with the Mixed Reality OpenXR runtime as being compatible with the UnityEngine.CoreModule.dll and specifically with the UnityEngine.Windows.Speech namespace.
Any help with this would be appreciated. Thank you!
SW Versions:
Windows 11 Pro
Unity 2020.3.16
WMR Runtime 107.2109.10010
Packages Include:
XR Plugin Management 4.07
XR Interaction Toolkit 1.0.0-pre.5
OpenXR Plugin 1.2.8
Microsoft Plugins:
Mixed Reality OpenXR Plugin 1.0.2
Mixed Reality Input 0.9.2006
Microsoft Spatializer 1.0.196

@jasonhbartlett Thanks for the report.  The openxr plugin to unity doesn't interact with speech input APIs.  That said, we can help to route this problem to the experts in this area to diagnose.  Next step, it would be nice to get the unity project that shows the bug, so we can report to the speech team with more precision.  A unity trace logging can also help.

@yl-msft It's very easy to reproduce this issue:

Make new 2020.3.16 Unity project
Enable preview packages in project settings
Enable XR Plugin Mgmt
4.a. Enable OpenXR
4.b. Add the Microsoft Motion Controller Profile to the OpenXR interaction profiles
Add XR Interaction Toolkit package (this is the preview package)
Create new empty scene
Convert main camera to XR rig
Added a floor and cube
Create new script (below) and add to the cube
Add 3 elements to the string array ("Green", "Blue", "Purple")

(Note: MS plugins mentioned above not necessarry to reproduce this issue)
TEST: If WMR headset IS NOT connected and WMR portal IS NOT running
RESULT: The cube changes color when one of the color names is spoken
TEST: If WMR headset IS connected and WMR portal IS running
RESULT: Nothing happens when the color names are spoken
If needed I've zipped and stuck the Unity project folder on my google drive here: SpeechCommandIssue
I've also added the stack trace logs in that folder. One log shows the results WITH the WMR headset and one WITHOUT. I've looked at these but did see anything except to note that no keywords recognized logs appear in the latter.
using System;
using System.Text;
using UnityEngine;
using UnityEngine.Windows.Speech;

public class VoiceCommandTest : MonoBehaviour
{
    [SerializeField]
    private string[] m_Keywords;

    private KeywordRecognizer m_Recognizer;
    private Renderer rend;

    void Start()
    {
        //Get the component for the material
        rend = GetComponent<Renderer>();

        //KeywordRecognizer
        m_Recognizer = new KeywordRecognizer(m_Keywords);

        //I dont know what this does
        m_Recognizer.OnPhraseRecognized += OnPhraseRecognized;

        //Start listening
        m_Recognizer.Start();
    }

    private void OnPhraseRecognized(PhraseRecognizedEventArgs args)
    {
        //Log stuff
        StringBuilder builder = new StringBuilder();
        builder.AppendFormat("{0} ({1}){2}", args.text, args.confidence, Environment.NewLine);
        builder.AppendFormat("\tTimestamp: {0}{1}", args.phraseStartTime, Environment.NewLine);
        builder.AppendFormat("\tDuration: {0} seconds{1}", args.phraseDuration.TotalSeconds, Environment.NewLine);
        Debug.Log(builder.ToString());

        //See what the KeywordRecognizer Recognized
        if (args.text.Equals("Green"))
        {
            this.rend.material.color = Color.green;
        }
        else if (args.text.Equals("Blue"))
        {
            this.rend.material.color = Color.blue;
        }
        else if (args.text.Equals("Purple"))
        {
            this.rend.material.color = Color.magenta;
        }
    }
}
`

Please let me know if I can continue to help troubleshoot this issue and I'll do whatever I can. Would be great to know initially if you can reproduce this issue.  Thanks!

@jasonhbartlett ,  in the latest main branch of this sample repo, we published a new sample to test the speech feature on HoloLens 2.   You can find the sample using "BasicSample" project, and here's the source of the sample scripts.  It's similar to what you are showing.   This sample worked fine in our tests.  I wonder if you can try this out and see if this works for you?