Upgrade to v6.03

Today i tried to update from v6.02 to 6.03 using curl -L https://power-mailinabox.net/setup.sh | sudo bash, got the upgrade stuck on : Installing Mail-in-a-Box system management daemon... for more than 10 minutes.

Tried again, after i do a reboot, with the same outcome. I use Hetzner server, and i have firewall and fail2ban active. @ddavness any solution ? What you suggest ?

You mean 60.2 and 60.3 respectively - 6.02 and 6.03 do not exist 😅
I am unable to reproduce the problem, however (that is, mine doesn't get stuck for 10 minutes). For all we know, it could be one of two things:

Intermittent datacenter problems, which I find unlikely to happen (or Hetzner would have put up a notice about it already);
The SSH connection decided to go to sleep, but the setup is still continuing on the background - in that case try pressing Enter and see if the rest of the setup magically happens in half a second.

I managed to upgrade it, i stopped fail2ban and tried again but still had to wait few minutes 6-7 minutes until the upgrade ended. Not sure what was the culprit but i managed to make it work. But i`ve noticed something that before 60.2 i didnt , now on the status check i get messages about IPv6. Should i ignore them ? Or should i try to fix them ? I am using your fork with Cloudflare.

Awesome. To be fair, there's a compile step on the Management Daemon but it shouldn't have taken that long to finish (30 seconds at worst).
Are you by any chance running this on Ubuntu 22.04? I've seen some folks complain about fail2ban on the upstream project.

Yes, i run  it Ubuntu 22.04. Then i need to find a fix for the IPv6 DNS problems, and the one with SSH on IPv6, even if i dont understand why does it needs access SSH on IPv6 .
Here are the messages without the IPv6
HTTP Web (nginx) is running (and available over IPv4 and the local IPv6 address), but it is not publicly accessible at
SSH Login (ssh) is running (and available over IPv4 and the local IPv6 address), but it is not publicly accessible at...:22.
Public DNS (nsd4) is running and available over IPv4 but is not accessible over ... port 53
Incoming Mail (SMTP/postfix) is running (and available over IPv4 and the local IPv6 address), but it is not publicly accessible at ...:25
Outgoing Mail (SMTP 465/postfix) is running (and available over IPv4 and the local IPv6 address), but it is not publicly accessible at ...:465
Outgoing Mail (SMTP 587/postfix) is running (and available over IPv4 and the local IPv6 address), but it is not publicly accessible at...:587...
and the list continues for Sieve, Dovecot, and HTTPS nginx.

@ddavness if i will disable the IPv6 function will affect the functionality of the mail server ?

Public IPv6? Probably not. However, the system keeps local IPv6 enabled (::1) to ensure nsd doesn't break.

I looked up how to add ipv6 to ufw allowance rules and it seems a bit
complicated. And i mistaken it's not Ubuntu the distro. It's Debian
Bullseye.
mie., 2 nov. 2022, 11:51 David Duque @.***> a scris:

Public IPv6? Probably not. However, the system keeps local IPv6 enabled
(::1) to ensure nsd doesn't break.
—
Reply to this email directly, view it on GitHub
https://github.com/ddavness/power-mailinabox/issues/90#issuecomment-1299959556,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASDEWEMV64VBHMAOXBX7TITWGI2S3ANCNFSM6AAAAAARS2RPCA
.
You are receiving this because you authored the thread.Message ID:
@.***>


Auto upgrade elemental ability

Was this suggested before? If not, I have two ideas for it:

Auto purchase it whenever we have the money to upgrade;
Auto purchase it when it is cost-effective (?)

Auto purchase it whenever we have the money to upgrade, but please add an additional Option for it to disable/enable it.

@K4r0qtuYNE5G4qgZ that was the idea.

ok, yeah only to be sure ;)

It should be compared against Lucky Shot money cost.

@GreatOldOne so, check if elemental upgrade is more cost effective than Lucky Shot?

Cost effective. Elemental should be about 3 levels higher than Lucky Shot.

Please do not have Elemental upgrade higher than level 20. It is useless late game due to not stacking with crit as it says here:
https://github.com/SteamDatabase/steamSummerMinigame/issues/57

But it does increase Click Damage nicely 25x at lvl 16 and so one, so instead only 500k damage you have 12'500k damage on matching Element Lanes, that's a lot and its increasing in 1.5x Steps per Level.
And compared to Crit it's per tick, Crits are only sporadic...

Crit buffs take one minute to cool down, so investing in elemental early game is still a good strategy.

@xPaw this was addressed in #222


Create 1209-Remove-All-Adjacent-Duplicates-in-String-II

My Attempt to 1209

File(s) Modified: 0001-two-sum.py, 0002-add-two-numbers.py, etc...
Language(s) Used: python, javascript, etc...
Submission URL: _https://leetcode.com/problems/[problem-name]/submissions/xxxxxxxxx/_

Important
Please make sure the file name is lowercase and a duplicate file does not already exist before merging.

My C# Attempt to 1209


Upgrade design system, to fix issue with menu on mobile

Ouf :sweat_smile: il y a encore le toggle du mode nuit

Spacing is broken, the class names changed

Fixed! Ready for review.


Feature suggest: Search and Sort

Why there is no search function for such a long list, and why there isn't any time info provides to sort out which app is recently added?

By the way, you shouldn't include "amacTests.xctest" when packaging that App, which showing that you start to learn and coding in a hurry, without learning developing macOS/iOS App SYSTEMATICALLY.

@ExTEnS10N
amac 应用是一个 React Native for mac，我只学习了一些基础的 Swift，为探索开发 HTTP server，目前还没有精力去完善 Mac 应用。
如果你有兴趣可以 PR 改善应用，或者 自己建一个仓库完善自己的想法，如果你干的不错，我将把你的应用贴在文档的前面进行推广。


If spatialite detected, mark idx_XXX_Geometry tables as hidden

https://timezones-api.now.sh/timezones-faf26d0

Need to update this logic:
https://github.com/simonw/datasette/blob/e2750c7cc0585adaa8c866be611089e62961ee35/datasette/app.py#L1276-L1288

Hiding tables with the idx_ prefix should be good enough here, since false positives aren't very harmful.


Content Security Policy (CSP) supported?

Do Rivets support CSP? This is a web standard to protect browser from XSS-related attacks.

@nonw Can you give some context to your issue?  Do you know what Rivets is?  When you wrote that issue, how were you connecting Rivets and CSP in your mind?

Most template engines break CSP because they use eval (or some form of it). Since Rivets doesn't produce functions which take some parameters and return string, but rather operate DOM directly, this is not the case.
I used Rivets in Chromium-based browser in it's WebUI, and it worked without changing CSP settings.


communities: schema fields

Currently the schema for the communities field is:
"community": {
      "type": "object",
      "properties": {
        "primary": {"type": "string"},
        "secondary": {
          "type": "array",
          "minItems": 0,
          "items":{"type": "string"}
        }
      }
    }

Is this enough or should we add something like (also applicable to secondary):
{
  "primary": {
    "type": "object",
    "properties": {
      "name": { "type": "string"},
      "identifier": {"type": "string"}
    }
}

Grooming
This should be tackled when invenio-communities is out (wait for it to come out first).


Add identifierQuoting to archive behavior tables

Archive behavior was not acknowledging the identifierQuoting parameter on the parent table.

Beschde Danke!


Recover Public Key From Signed Message

A standard utility is a function for recovering a public key from a signed message.
See, for instance, https://github.com/ethereum/ethereumj/blob/80be70c3428f244706c6fc6ac67e1bd5374eeb05/ethereumj-core/src/main/java/org/ethereum/crypto/ECKey.java#L527

Okay, it doesn't look like the elliptic package supports this :(
Maybe someday I'll shave that yak, but for now not so much...


Migration script for WRFV4.4

Based on the existing migration script for migrating to WRFV4.2 the script should be split and extended to allow the migration from old versions to WRFV4.2 and also a separate migration step from 4.2 to 4.4 since these two version steps contain the most breaking changes for the execution of the model.

Done with 4ffcc31587b637958a38b93a3583dfda1c32922d.


Azure OpenAI

Add Azure OpenAI client.
Ref: https://plugins.jetbrains.com/plugin/21335-ai-commits/reviews#105902.

thank you !
waiting for this update to be release on jetbrains marketplace !


Uplink code does not check if bringing up the packet switched layer worked

The uplink code calls connect_to_internet() but does not check the return value.
It should return early if the connection fails rather than reporting a failure for every file to be sent.

A related problem that can be fixed at the same time is that if the modem becomes unresponsive after bringing up the packet switched layer and is rebooted using the PWR_ON pin, connect_to_internet does not redo the packet switched layer initialisation.

Fixed by commit e0aa61ab640c73cc5ac78de84d5e4e112f5fe715.


Async write/update support

I see in #203 / #204 that async support for graph traversals has been added. What about async support for writes?
For example:
case class Person(firstName: String, lastName: String)
graph.V().head.updateAs[Person](_.copy(firstName = "Name Change!)).promise()

Otherwise, it seems that any write operation is a synchronous (i.e. thread blocking) operation. When your graph DB is remote, that's going to be 5-50ms of blocking...
Is that true? Is the underlying network call asynchronous or blocking?

The underlying gremlin-java only allows for async ops in a traversal, so your best bet is probably to update the property in a traversal like this. The below is repl-friendly, just replace toList with promise for async.
import gremlin.scala._
import org.apache.tinkerpop.gremlin.tinkergraph.structure.TinkerFactory

val g = TinkerFactory.createModern.asScala
val Name = Key[String]("name")

g.V(1).property(Name, "updated").toList
g.V.value(Name).toList //List(updated, vadas, lop, josh, ripple, peter)

Is the underlying network call asynchronous or blocking?

That depends on the database driver implementation.

Not sure sure I understand. Should it be:
g.V(1).promise(_.property(Name, "updated"))

to become async? promise takes an onComplete method.

Is there any way to do this with case classes? Otherwise, one needs a Key[_] per case class property.

promise takes an onComplete lambda, which you may or may not need. I guess there should be an overloaded promise() that doesn't take a lambda...
g.V(1).property(Name, "updated").promise(_ => _) // don't do anything with the result

// convert to case class
g.V(1).property(Name, "updated").promise(_.toCC[Person])

You may be confused by the fact that g.V(1).property(Name, "updated") is lazy - it doesn't do anything unless you execute the traversal with e.g. toList or promise. That's different to working with elements directly. Unfortunately you can't do much with case classes in the traversal, because you want to be able to execute your traversal remotely, and the DB typically doesn't know your case class.

I just got curious and actually pasted the above in my repl, and it doesn't compile.. hang in there

ok, updated the above to something that compiles. Note that this only works with a remoteGraph and I haven't actually tested to run it against one yet.

FYI: just added a little convenience step promise() in 35c21f8999b8cd127a07f0a8821d3b7c6553cb8d

Thanks for the syntactic sugar!
It's clear now how to make async updates to Vertices and Edges. Is there any way to create Vertices and Edges asynchronously? E.g.
scala> val futV = graph.addVertexAsync()
futV: Future[scala.Vertex]

I'd like to get to the point where I can use gremlin-scala like Slick or another asynchronous DB. Each DB operation would (ideally) explicitly be a Future where the package allows configuration of it's own execution threadpool / actors.

you can use the addV and addE steps to add vertices and edges during a traversal. Examples here:
https://github.com/mpollmeier/gremlin-scala/blob/master/gremlin-scala/src/test/scala/gremlin/scala/TraversalSpec.scala#L705
https://github.com/mpollmeier/gremlin-scala/blob/master/gremlin-scala/src/test/scala/gremlin/scala/TraversalSpec.scala#L769


Service Definition item (Area_Of_Operation1) exists without an associated hosted service

Hosted service Area_Of_Operation1/MapServer no longer exists, but associated service definition item exists; please delete the following item:
id: 4e3286e4de62400e87b09d8b590edaff
type: Service Definition
service: Area_Of_Operation1/MapServer

@erikreid I deleted this item.


AI-Enhanced Docusaurus Version Updater: Dynamic Error Handling, Intelligent Link Validation, and Automated Content Adjustment

In this update, the script has been significantly enhanced with AI-driven features to automate and optimize the process of updating versioned HTML files in a Docusaurus site.

Dynamic Error Handling with AI Assistance: The script now includes AI-driven error handling, which automatically detects and resolves common issues during the update process. The AI can predict potential points of failure and suggest corrective actions, minimizing manual intervention and improving script robustness.

Intelligent Link Validation: The AI feature has been integrated to validate all the links dynamically. It ensures that the URLs are correctly formed and checks if they are reachable. If any link appears to be broken or incorrect, the AI suggests alternatives or automatically corrects them based on context.

Version Management Optimization: The AI assists in managing the list of versions more effectively. It analyzes the existing versions, predicts future versioning needs, and optimizes the appending process. The AI also ensures that the "latest" version is always correctly referenced and linked throughout the site.

Automated HTML Content Adjustment: The AI feature has been enhanced to adjust HTML elements intelligently. For example, it now automatically updates headers, navigation links, and version titles based on the version being processed. The AI takes into account the specific structure and content of each HTML file, ensuring that all relevant elements are accurately updated.

Enhanced Logging and Reporting: The AI now provides detailed logs and reports of the update process. It not only logs the steps taken but also analyzes the outcomes and provides insights into how the process could be further optimized in future runs.

These updates collectively make the script more intelligent, efficient, and capable of handling complex versioning tasks with minimal human oversight.

This update introduces AI-driven enhancements to the Docusaurus version updater script. Key improvements include:

Dynamic Error Handling: Integrated AI-based error detection and handling to ensure robust processing, minimizing disruptions during version updates.
Intelligent Link Validation: Added AI-driven link validation to automatically verify and correct URLs, ensuring that all links are accurate and functional across different versions.
Automated Content Adjustment: The script now intelligently adjusts content, including title and navigation links, based on the AI analysis of version-specific changes.

These enhancements are designed to streamline the version update process, reduce manual intervention, and improve overall reliability.


Catch errors from bots.create

This wraps the requests made in the bots.create method in a try catch block, and throws any errors returned. This means that a .catch(err => ...) can be used on the client to then show any errors from bot creation, such as name already being taken.

Is the try / catch necessary? Errors in async functions just propagate upwards.

As far as I'm aware it was needed, as it previously wasn't passing errors along (in my case, to the client)

I just tested it in the client and errors do correctly propagate through.


NEXT-11068 - Fix range slider

1. Why is this change necessary?
The current filter-range:

does not stop updating listing if any validation error occurs / also not the current check if min higher than max
does not respect any browser-validation (min and max value)

2. What does this change do, exactly?
3. Describe each step to reproduce the issue or behaviour.
4. Please link to the relevant issues (if any).
https://issues.shopware.com/issues/NEXT-11068
5. Checklist

[ ] I have written tests and verified that they fail without my change
[x] I have squashed any insignificant commits
[x] I have created a changelog file with all necessary information about my changes
[x] I have written or adjusted the documentation according to my changes
[x] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

Hey @tinect, thanks for your contribution 💙 A test would be nice 🙂

This PR was closed due to inactivity. If this change is still important to you, feel free to create a new pull request.
For more information about our contribution guidelines, see https://docs.shopware.com/en/shopware-platform-dev-en/contribution/contribution-guideline


Failed dependency resolution on using npm ci instead of npm install

Did you see the documentation relating to installation?
Yes
Have you ensured the architecture and platform of Node.js used for npm install is the same as the architecture and platform of Node.js used at runtime?
Yes, it is Rhel 7
Are you using the latest version? Is the version currently in use as reported by npm ls sharp the same as the latest version as reported by npm view sharp dist-tags.latest?
I am using Next.js v10.0.5 and sharp 0.26.3 is a dependency of it.
If you are installing as a root or sudo user, have you tried with the npm install --unsafe-perm flag?
Not using root or sudo
If you are using the ignore-scripts feature of npm, have you tried with the npm install --ignore-scripts=false flag?
Yes
What is the complete output of running npm install --verbose sharp? Have you checked this output for useful error messages?
What is the output of running npx envinfo --binaries --system?
System:
OS: Linux 4.19 Red Hat Enterprise Linux Server 7.9 (Maipo)
CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
Memory: 623.18 MB / 1.94 GB
Container: Yes
Shell: 4.2.46 - /bin/bash
Binaries:
Node: 14.15.4
npm: 6.14.10
My project has a package-lock.json file and I use npm ci to install the node_modules.
For our build, we are generating an RPM for the UI.
The node_module sharp that gets downloaded on using npm ci vs on using npm install is different. While trying to install the rpm generated when using npm ci fails with the following error:
 --> Processing Dependency: libvips.so.42()(64bit) for package: node-ui.el7.x86_64   --> Processing Dependency: libvips-cpp.so.42()(64bit) for package: node-ui.el7.x86_64   --> Finished Dependency Resolution               Error: Package: node-ui.el7.x86_64                          Requires: libvips-cpp.so.42()(64bit)               Error: Package: node-ui.el7.x86_64                          Requires: libvips.so.42()(64bit)
I don't get the same error on using npm install which is weird.
On inspecting the node_module sharp, the differences are:
npm ci : has a vendor folder and build folder with a sharp.node file
I am not sure if it is an issue with next or sharp. Can you please instruct on what may be causing this issue?

How is the rpm built? Are you explicitly specifying a dependency on libvips?
What is the output of running npm ci --verbose, especially the part when sharp is installed?

How is the rpm built? Are you explicitly specifying a dependency on libvips?
What is the output of running npm ci --verbose, especially the part when sharp is installed?

Using the rpmbuild utility, we just copy the node_modules,
I don’t specify any dependency on libvips explicitly
`npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>
<EMAIL_ADDRESS>install /usr/src/app/node_modules/sharp
(node install/libvips && node install/dll-copy && prebuild-install) || (node-gyp rebuild && node install/dll-copy)
info sharp Downloading https://github.com/lovell/sharp-libvips/releases/download/v8.10.0/libvips-8.10.0-linux-x64.tar.br
prebuild-install info begin Prebuild-install version 6.0.0
prebuild-install info looking for cached prebuild @ /root/.npm/_cacache/_prebuilds/3a1d54-sharp-v0.26.3-napi-v3-linux-x64.tar.gz
prebuild-install http request GET https://github.com/lovell/sharp/releases/download/v0.26.3/sharp-v0.26.3-napi-v3-linux-x64.tar.gz
prebuild-install http 200 https://github.com/lovell/sharp/releases/download/v0.26.3/sharp-v0.26.3-napi-v3-linux-x64.tar.gz
prebuild-install info downloading to @ /root/.npm/_cacache/_prebuilds/3a1d54-sharp-v0.26.3-napi-v3-linux-x64.tar.gz.139-9230fb6b69499.tmp
prebuild-install info renaming to @ /root/.npm/_cacache/_prebuilds/3a1d54-sharp-v0.26.3-napi-v3-linux-x64.tar.gz
prebuild-install info unpacking @ /root/.npm/_cacache/_prebuilds/3a1d54-sharp-v0.26.3-napi-v3-linux-x64.tar.gz
prebuild-install info unpack resolved to /usr/src/app/node_modules/sharp/build/Release/sharp.node
prebuild-install info install Successfully installed prebuilt binary!
npm verb lifecycle<EMAIL_ADDRESS>unsafe-perm in lifecycle false
npm verb lifecycle<EMAIL_ADDRESS>PATH: /node/npm/node_modules/npm-lifecycle/node-gyp-bin:/usr/src/app/node_modules/sharp/node_modules/.bin:/usr/src/app/node_modules/.bin:/usr/bin:/opt/rh/devtoolset-8/root/usr/bin:/opt/rh/rh-git218/root/usr/bin:/opt/rh/rh-git218/root/usr/bin/:/bin64:/bin:/opt/rh/rh-git218/root/usr/bin:/bin64:/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
npm verb lifecycle<EMAIL_ADDRESS>CWD: /usr/src/app/node_modules/sharp
npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>`

Using the rpmbuild utility, we just copy the node_modules,
I don’t specify any dependency on libvips explicitly
`npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>
<EMAIL_ADDRESS>install /usr/src/app/node_modules/sharp
(node install/libvips && node install/dll-copy && prebuild-install) || (node-gyp rebuild && node install/dll-copy)
info sharp Downloading https://github.com/lovell/sharp-libvips/releases/download/v8.10.0/libvips-8.10.0-linux-x64.tar.br
prebuild-install info begin Prebuild-install version 6.0.0
prebuild-install info looking for cached prebuild @ /root/.npm/_cacache/_prebuilds/3a1d54-sharp-v0.26.3-napi-v3-linux-x64.tar.gz
prebuild-install http request GET https://github.com/lovell/sharp/releases/download/v0.26.3/sharp-v0.26.3-napi-v3-linux-x64.tar.gz
prebuild-install http 200 https://github.com/lovell/sharp/releases/download/v0.26.3/sharp-v0.26.3-napi-v3-linux-x64.tar.gz
prebuild-install info downloading to @ /root/.npm/_cacache/_prebuilds/3a1d54-sharp-v0.26.3-napi-v3-linux-x64.tar.gz.139-9230fb6b69499.tmp
prebuild-install info renaming to @ /root/.npm/_cacache/_prebuilds/3a1d54-sharp-v0.26.3-napi-v3-linux-x64.tar.gz
prebuild-install info unpacking @ /root/.npm/_cacache/_prebuilds/3a1d54-sharp-v0.26.3-napi-v3-linux-x64.tar.gz
prebuild-install info unpack resolved to /usr/src/app/node_modules/sharp/build/Release/sharp.node
prebuild-install info install Successfully installed prebuilt binary!
npm verb lifecycle<EMAIL_ADDRESS>unsafe-perm in lifecycle false
npm verb lifecycle<EMAIL_ADDRESS>PATH: /node/npm/node_modules/npm-lifecycle/node-gyp-bin:/usr/src/app/node_modules/sharp/node_modules/.bin:/usr/src/app/node_modules/.bin:/usr/bin:/opt/rh/devtoolset-8/root/usr/bin:/opt/rh/rh-git218/root/usr/bin:/opt/rh/rh-git218/root/usr/bin/:/bin64:/bin:/opt/rh/rh-git218/root/usr/bin:/bin64:/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
npm verb lifecycle<EMAIL_ADDRESS>CWD: /usr/src/app/node_modules/sharp
npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>`

That log looks OK, so my best guess is that there's something going wrong after this, perhaps in the rpmbuild configuration. Are you able to share this, perhaps as a separate, standalone repo that allows someone else to reproduce the problem?

That log looks OK, so my best guess is that there's something going wrong after this, perhaps in the rpmbuild configuration. Are you able to share this, perhaps as a separate, standalone repo that allows someone else to reproduce the problem?

Working on creating a separate repo.
Meanwhile, do you think that the node_module of sharp downloaded being separate on using npm ci and npm install is an issue?

@lovell https://github.com/chandrasekhar1996/libvips-issue
you can run the docker file and then try to install the rpm created in rpmbuild folder

You need to add an explicit Requires: section to the spec otherwise rpmbuild will do it for you.
https://rpm.org/user_doc/more_dependencies.html#automatic-dependencies
This is a feature of rpmbuild unrelated to sharp or libvips. Please consider a more general site such as StackOverflow for this kind of question.

Sorry for opening the issue but I am not sure I understand how using Requires:  would solve the issue.
The rpm shows a dependency on libvips-cpp.so.42 and libvips.so.42 which is present inside the /sharp/vendor/8.10.0/lib/ in the rpm files.
So what would I need to specify in Requires:  field?

fyi, earlier I found an article of how it may be an issue of permission to the file and I added the following lines in %install of my spec file and I was able to install the rpm:
chmod 0755 %{buildroot}/home/chandu/var/%{name}/node_modules/sharp/vendor/8.10.0/lib/libvips-cpp.so.42 chmod 0755 %{buildroot}/home/chandu/var/%{name}/node_modules/sharp/vendor/8.10.0/lib/libvips.so.42
not sure if this is the right fix so would like to understand it better


Releases missing linux vst3s for v0.7.0 onwards

The releases are missing linux vst3s for v0.7.0 onwards, I ended up compiling it from source instead

Hello row454,
sorry for your inconvenience and thanks for the hint!
There was an error in the distribution script that left out the Linux VST as well as several programs of the MacOS distribution. I have updated the 0.7.1 release files accordingly.
Best regards,
Prof. Spock

Hello row454,
the new release v0.7.5 removes any fluidsynth library for Linux from the distribution and instead requires a fluidsynth package installation; this is also described in the appendix of the documentation.
Hence the issue should be fixed now as soon as you have a fluidsynth package installation on you Linux system.
Please let me know, whether this is correct or not.
Best regards,
Prof. Spock


networkx 2.0 api changes

The digraph class in networkx has changed api.  We should pin to < 2.0

This is actually from odo, and there are a few issues for it.

https://github.com/blaze/odo/issues/588
For reference sake


ionic cordova platform add ios not copying variables from config.xml

Short description of the problem:
ionic cordova platform add ios not copying variables from config.xml to <app>-info.plist file.
Variables:
<plugin name="cordova-plugin-camera" spec="2.4.0">
  <variable name="CAMERA_USAGE_DESCRIPTION" value="My Description"/>
  <variable name="PHOTOLIBRARY_USAGE_DESCRIPTION" value="My Description"/>
</plugin>

What behavior are you expecting?
Have those variables on info.plist file as below
    <key>NSCameraUsageDescription</key>
    <string>My Description</string>
    <key>NSPhotoLibraryUsageDescription</key>
    <string>My Description</string>

Steps to reproduce:

add variables info do config.xml
ionic cordova platform add ios

Post the output of ionic info below please
global packages:
@ionic/cli-utils : 1.0.0
Cordova CLI      : 6.5.0
Ionic CLI        : 3.0.0

local packages:
@ionic/app-scripts              : 1.3.7
@ionic/cli-plugin-cordova       : 1.0.0
@ionic/cli-plugin-ionic-angular : 1.0.0
Ionic Framework                 : ionic-angular 3.1.1

System:
Node       : v7.9.0
OS         : macOS Sierra
Xcode      : Xcode 8.3.2 Build version 8E2002
ios-deploy : 1.9.1
ios-sim    : 5.0.13

No error occur during the build, but deploy to Itunes connect fails because of lack of information.

Is this done with a hook? I may need more information.

On ionic cli 2, this is done on platform add and/or ionic state restore, but state restore was removed..

We don't do much on top of just running cordova platform add ios directly. This is a Cordova issue. Additionally, I'm unable to reproduce.
$ ionic cordova plugin add cordova-plugin-camera --variable CAMERA_USAGE_DESCRIPTION="your usage message" --variable PHOTOLIBRARY_USAGE_DESCRIPTION="your usage message"`

contents of platforms/ios/MyApp/MyApp-Info.plist contains:
    <key>NSCameraUsageDescription</key>
    <string>your usage message</string>
    <key>NSPhotoLibraryUsageDescription</key>
    <string>your usage message</string>

Now delete platforms folder and re-add them. The variables from config.xml are ignored

This is also broken for me! Having to manually copy them into the plist and build from xcode for now.

@andrefa @CookieCookson Please help me to reproduce this issue.
On a new ionic project, I put this in my config.xml:
<plugin name="cordova-plugin-camera" spec="2.4.0">
  <variable name="CAMERA_USAGE_DESCRIPTION" value="My Description"/>
  <variable name="PHOTOLIBRARY_USAGE_DESCRIPTION" value="My Description"/>
</plugin>

Then:
$ ionic cordova platform add ios

Then it finds the variables in the plist file:
$ grep -R NSCam .
Binary file ./build/emulator/MyApp.app/Info.plist matches
./ios.json:                    "NSCameraUsageDescription": [
./MyApp/MyApp-Info.plist:    <key>NSCameraUsageDescription</key>

After I build with ionic cordova build ios, the variables still exist in the plist file.

@dwieeb - I'll try and create a repo today that reproduces the issue. I managed to get it to pull through ONE of the plugins descriptions and not the other after doing a platform rm/add.

@dwieeb In typical fashion, I was not able to reproduce this on a new project. My original project is still doing it, however after cloning the project from source into a different folder and following the standard install procedure it copies across all of the plist entries correctly. Not sure if its a mis-installed node package or the if cordova 6 projects just don't like being updated to 7.

I also faced with the same issue. Privacy descriptions is not copied from config.xml

Same here, I do have custom plugins that should be restored and platforms added via ionic cordova prepare. Unfortunately the CLI crashes while installing the plugins because of supposedly missing variables (both provided via config.xml).

For anyone else still having this issue - I ended up getting it to work by cloning my project to a new folder and re-installing the platforms.

I found the root of the problem, seems like ionic reads plist details from package.json instead of config.xml
so, add something like this into your package json:
    "cordova": {         "platforms": [             "android",             "ios"         ],         "plugins": {             "cordova-plugin-camera": {                 "CAMERA_USAGE_DESCRIPTION": "To take photo"             },             "cordova-plugin-photo-library": {                 "PHOTO_LIBRARY_USAGE_DESCRIPTION": "To choose photos"             }         }     }

Please provide the exact list of commands executed and things done so someone can actually reproduce this. Also include your ionic info output so we know which Cordova version (which is actually doing all that stuff, Ionic is only calling this...) you are using and if you are on current software.

I had the same problem.
It started happening after I removed all my plugins and when re-adding them I neglected to add the variables to the plugin add command.
Afterwards I tried updating the package.json and config.xml with the correct descriptions, without any luck, even tried removing and adding the platform again.
The only way I could get it to work is to remove the plugin again and add it with the variable options.

I was able to reproduce this.. I am using the cordova-plugin-camera and cordova-plugin-geolocation with the variables. However, when I checked the info.plist file xcworkspace via XCode, I did not see any of the variable is included..
Here is my ionic info
`
cli packages: (/usr/local/lib/node_modules)
@ionic/cli-utils  : 1.19.1
ionic (Ionic CLI) : 3.19.1

global packages:
cordova (Cordova CLI) : 8.0.0

local packages:
@ionic/app-scripts : 3.1.8
Cordova Platforms  : android 6.4.0 ios
Ionic Framework    : ionic-angular 3.8.0

System:
Android SDK Tools : 26.1.1
ios-deploy        : 1.9.2
ios-sim           : 4.1.1
Node              : v7.6.0
npm               : 4.1.2
OS                : macOS High Sierra
Xcode             : Xcode 9.2 Build version 9C40b

Environment Variables:
ANDROID_HOME : /Users/ting/Library/Android/sdk

Misc:
backend : pro

`


hwmv2: boards: Fix bools and selections

Fixes issues with some outstanding bools being defined and wrong usage of soc selection

@nordicjm , @aescolar ,
About numaker_pfm_m467 & numaker_pfm_m487, their schematics are different and SOC also really different. This PR want to merge these 2 boards into “numaker_pfm” will cause some incompatible and complex on numaker_pfm/m467 v.s numaker_pfm/m487.
Please keep as:
boards/nuvoton/numaker_pfm_m467
boards/nuvoton/numaker_pfm_m487


Don't assume the application is deployed to "/"

Fixes #1

I merged your fix of the issue with the base branch. Thank you very much for your support.


Downgrading rust version?

I came across this from Zellij — great idea for an action!
Should this be downgrading the rust version though? https://github.com/prql/prql/pull/928/files

Ah great, that makes sense! Thanks!
I have another question I'll open a separate issue for


inverse_transform() in BaseNEncoder does not raise an exception

inverse_transform() in BaseNEncoder does not raise an exception when the test set contains a new value:
        X = create_dataset(n_rows=100, has_none=False)
        X_t = create_dataset(n_rows=50, has_none=False)
        X_t_extra = create_dataset(n_rows=50, extras=True, has_none=False)
        cols = ['underscore', 'none', 'extra', 321]

         enc = category_encoders.BaseNEncoder(verbose=1, cols=cols)
         enc.fit(X, y)
         with self.assertRaises(ValueError):
                _ = enc.inverse_transform(enc.transform(X_t_extra))

It looks like an error could be in the remaining encoders. OneHot, Binary and Ordinal use following code:
for col in self.cols:
    if any(X[col] == 0):
        raise ValueError("inverse_transform is not supported because transform impute "
                                     "the unknown category -1 when encode %s"%(col,))

While BaseN uses:
for col in self.cols:
    if any(X[col] == -1):
        raise ValueError("inverse_transform is not supported because transform impute "
                                     "the unknown category -1 when encode %s"%(col,))

Note the difference between X[col] == 0 and X[col] == -1.
My hypothesis is that there should be -1 everywhere. 0 is merely a historical artifact from the time when 0 used to be used to mark unknown categories. Am I right?

Ah yes, should be -1 everywhere, 0 is legacy and causes issues. Should switch it to -1.

Resolved with commit https://github.com/scikit-learn-contrib/categorical-encoding/commit/037c7cdcbe133dcfea5f23809f74b903c599d457


Generate Jenkins AMI if it doesn't exist

Determine if Jenkins AMI exists and it’s the correct version; otherwise, it will launch Packer. Jenkins is maintained in https://github.com/stelligent/tophat

Jenkins AMI and jenkins-instance.json only describes for us-east-1 region. this will fail if it is launch in any other region

https://github.com/stelligent/dromedary/issues/54 Correct. The AMI needs to be updated for all supported CodePipeline regions, not all AWS regions, since this solution runs on CodePipeline. As of today, this is us-east-1 and us-west-2.

Paul, can you confirm the security settings on https://s3.amazonaws.com/stelligent-training-public/master/jenkins-instance.json ? it seem it's not public.

Done. Sorry about that. I'd uploaded some new changes and didn't change the default permissions


Move AlgorithmIdentifier values to here from rustls-webpki

Any downstream crate defining a custom rustls::CryptoProvider currently needs to take a dependency on rustls-webpki to reuse these values (alternatively they can redefine these values, but meh.)
Moving them here removes that need, and eliminates another reason for people to depend on rustls-webpki directly.
fixes #27

How about we move AlgorithmIdentifier into the new module, with a top-level re-export for compatibility?


Flask Babel issue with dates < 1902.

What is the context of this PR?
The original issue stems from: trello. If a date was passed to format_date before December 14 1901 then format_date would change the hour by -1, meaning that 1902 would become 1901 when piped into another question.
I originally thought we needed to set rebase=False on flask_babel.format_date, this did fix the issue, but we were not converting dates to BST anymore, breaking a test.
Investigating further, I found that 1901 coincides with the earliest possible unix timestamp, e.g. minimum value of a signed 32 bit integer. If you run zdump -v Europe/London you can actually see a couple of BST transitions in 1901, which shouldn't really be there, since it was introduced in 1916. I found a few vague references to similar problems on stack overflow which suggested issues with the Olsen database (used by pytz).
One fix for the issue was to fork flask-babel (fork here can be removed if this is merged.) and replace their use of pytz with pendulum. Pendulum fixes the issue found in pytz with dates before 1902 (and potentially a few others). This solution is problematic because flask-babel isn't well maintained and we are unlikely to be able to merge any changes upstream. The issue would probably need to be fixed upstream in pytz, which lives on sourceforge and has a mailing list.
An alternate fix is to skirt the issue in flask babel by avoiding the to_user_timezone function in flask_babel, which is where the issue comes into play. I did this by calling flask_babel.format_datetime with a date object rather than a datetime object. This fixes our use of format_date and doesn't rely on maintaining a fork of flask_babel. I think it's the better solution in the short term.
As a part of this, I did have a look at replacing our use of datetime with pendulum, which on the face of it looks like it would fix some common datetime issues we have. I found that the now() method is a local time object and there is no utcnow() method, additionally, the datetime.strptime() function is not replicated exactly (different format strings etc.). Having investigated a little, I don't think there are any major advantages for us switching at the moment. Though it could become useful in future if we start doing complex manipulations of timezones etc.
How to review
Enter a date of e.g. January 1 1901 on the test_dates schema. The playback on the next page should show 1901, not December 1900. This is replicated in the functional test.
Checklist

[ ] New static content marked up for translation
[ ] Newly defined schema content included in eq-translations repo

Should probably ensure that Codacy works before this is merged. Not sure how to trigger it though...

Codacy finally seems to have run @ajmaddaford. Should be ready to merge.


[android] Remove uribeacon library services

The uribeacon library services are no longer needed.

Don't you need these for configuration?

Oh duh...I was wondering what the gatt service was for.


breakpoint-to-ems - base font size?

Hello,
Firstly, great library - thanks very much for building and supporting it! My question is regarding the $breakpoint-to-ems variable. My preference is to use ems for layouts and so have this enabled. Where does breakpoint get the base font size to calculate the em value from? It appears by default it is using 16px. Can this be changed anywhere and if so, where?
Thanks!

Update: I found what should be the value that sets the base font size in _breakpoint.scss. However, changing the value does not appear to work.
Using the default value:
.test {
  color: green;

  @include breakpoint(320px) {
    color: blue;
  }

  @include breakpoint(768px) {
    color: red;
  }
}

This resulted in the following:
.test {
  color: green;
}
@media (min-width: 20em) {
  .test {
    color: blue;
  }
}
@media (min-width: 48em) {
  .test {
    color: red;
  }
}

I created a $breakpoint-base-font-size value which I set to 10px and recompiled my sass file. Same results:
.test {
  color: green;
}
@media (min-width: 20em) {
  .test {
    color: blue;
  }
}
@media (min-width: 48em) {
  .test {
    color: red;
  }
}

Not sure this is quite correct? Or is it? I would have expected min-width: 32em and min-width: 76.8em.
Any thoughts?
Thanks!

Media query em conversion is not based on the document's root font size, but rather the de facto standard conversion of 1em / 16px that is true across all browsers. As such, we don't allow users to change this ratio when using em based media queries. The ems aren't document ems, they are browser ems.

Gotcha. I can work with that!
Cheers


Missing Thor class for invoke middleman:generator

Expected behavior and actual behavior
Missing Thor class for invoke middleman:generator raised when doing middleman init
Steps to reproduce the problem (from a clean middleman installation)
Additional information

Ruby version: 3.2.2
Middleman version: 4.5.0
OS version: OSX

Can you try on 4.5.1?

Can you try on 4.5.1?

ERROR:  Could not find a valid gem 'middleman' (= 4.5.1) in any repository```

Seems like 4.5.1 is not available through ruby gems and I do not see 4.5.1 TAG on the repo

Also checked with 5.0.0.rc.1 but with this one you'll get other error:
uninitialized constant Haml::Options

4.5.1 is definitely on rubygems: https://rubygems.org/gems/middleman/versions/4.5.1

When doing gem install middleman, rubygems installs the 4.5.0 version. Forcing the version also fails.
─$ gem install middleman -v 4.5.1
ERROR:  Could not find a valid gem 'middleman' (= 4.5.1) in any repository
ERROR:  Possible alternatives: beans-middleman, branchable_cdn_assets-middleman, capistrano-middleman, capistrano-middleman-presentation, capistrano-middleman2, contentful-middleman-pages, contentful_middleman, ember-middleman, fdt_middleman_tools, font-awesome-middleman

It could be rubygems issue though.

I've got the same error. By using an older version of thor (1.2.2) instead 1.3.0 the middleman init command works.

Any updates on this? I also am having this problem and can't get 4.5.1 to install.

Seems like 474 people have successfully installed 4.5.1

I may just have to republish and hope that ruby gems stops being confused

@tdreyno I successfully installed the v4.5.1 release for my projects under Ruby 3.2.
I miss the git tag in the repository, they are useful to compare changes between versions: https://github.com/middleman/middleman/tags.
Not sure how is your current release process, but just in case, Bundler provides a very easy command to release gems (it builds the gem, push the tags and push to RubyGems automatically):
> rake release


Can return values be ignored?

Random example:
The C version of crypto_box_curve25519xsalsa20poly1305 is tagged with __attribute__ ((warn_unused_result)) (see https://github.com/jedisct1/libsodium/blob/master/src/libsodium/include/sodium/crypto_box_curve25519xsalsa20poly1305.h#L49), but sodiumoxide ignores it: https://github.com/dnaq/sodiumoxide/blob/0c9f41f0dfc085669c603f7fd0b393983947b266/src/crypto/box_/curve25519xsalsa20poly1305.rs#L84
I'm not sure if this is an issue at all and I can see that the obvioiusly important ones (like crypto_box_curve25519xsalsa20poly1305_open) are not ignored.

The only way that function can fail is when the input is too short (the C API requires zero-padded messages), but since we add the correct amount of padding there's no way that can happen. That being said it might be prudent to check the return value and panic if it's not zero. I'd accept a pull request.


Use simpler code in unreachable

This was recommended by aatch in a discussion on the rfcs repo.
I would prefer to remove the link to the void crate. The void crate makes sense to have a common definiton of a Void type, but here we're not using it in a user visible interface, and any voidish enum will do. It's simpler to just define it where it is needed.

See https://github.com/rust-lang/rfcs/issues/1385#issuecomment-166308865
I verified this version of unreachable still produces good results in one of my projects.

By the way, I'd recommend using a 0.1.0 for the next version. That way you can provide non-breaking bugfixes to your users easily. (Cargo doesn't upgrade a 0.0.2 to 0.0.3)

I'd rather keep a reference to the void crate for the void::unreachable function. I think it's best to keep the best way to diverge given a Void value in the void crate, so any changes to it propagate automatically.
The best definition to me would be void::unreachable(*(1 as *const Void)).

It seems better to not have any function calls at all inside unreachable, though

Ok, it's a super small change, so you can be free to make it as you want, saves us the back and forth. aatch's comments are valuable to take care of though.


Upgrade to Scout 0.3.0, and have --query-only

kubernaut kubeconfig --query-only won't output anything on success, and will use the exit code to indicate if you have a cluster claimed.

I'm a little concerned with the --query-only option because it adds a new CLI design constraint I have to adhere to for future versions when I think there is a better mechanism for finding out if you have a cluster (e.g. I'd like to have kubernaut list-claims and kubernaut get-claim <name> return list of claims and details about a claim.
Is the only reason for this to avoid printing output? Is > /dev/null 2>&1 not good enough? What about the -p option? I'm curious what the use case was.


feat: allow specifying catalog component to question

Allow specifying components the question is related to in the ask question page. This would allow to integrate questions related to component in the catalog page.

If so, what gets specified should be the entity ref (e.g. component:default/foo), rather than the UID. That's the universal reference we use everywhere for referring to entities.


Poor np.full performace with jit

numba version: 0.54.1
This is the testing code.
import numpy as np
from numba import jit, prange, set_num_threads
import time

set_num_threads(4)

@jit
def f1(shape):
    return np.full(shape, np.nan, np.float64)

@jit
def f2(shape):
    ans = np.empty(shape, np.float64)
    for i in range(ans.shape[0]):
        for j in range(ans.shape[1]):
            ans[i, j] = np.nan

@jit(parallel=True)
def f3(shape):
    ans = np.empty(shape, np.float64)
    for i in prange(ans.shape[0]):
        for j in range(ans.shape[1]):
            ans[i, j] = np.nan

# Warm up
shape = (12, 10)
f1(shape)
f2(shape)
f3(shape)

shape = (128000, 1000)

t0 = time.time()
np.full(shape, np.nan, np.float64)
print(time.time() - t0)

t0 = time.time()
f1(shape)
print(time.time() - t0)

t0 = time.time()
f2(shape)
print(time.time() - t0)

t0 = time.time()
f3(shape)
print(time.time() - t0)

This is the output
0.24103260040283203 # numpy
0.5575239658355713 # np.full in jit
0.45681166648864746 # fill with for-loop
0.18029499053955078 # fill with parallel for-loop

The speed of np.full in jit is less than half compared with the normal one from my testing.

This is similar to the problem outlined in https://numba.readthedocs.io/en/stable/user/faq.html#can-numba-speed-up-short-running-functions - there's nothing Numba can do to optimize inside np.full, so when you wrap it in a jitted function you're just adding the overhead of calling a jitted function on top of the time it takes to execute np.full.
If you're trying to understand whether Numba can help speed up your application, it would be more representative to benchmark something that looks a bit more like a portion of your application code.

But this does not look like just overhead. This is the output that I increase the shape 10 times up. (shape = (1280000, 1000))
2.9751839637756348
5.439911603927612
4.502171516418457
1.7119011878967285

OK, I see. There's probably some difference in implementation between Numba and NumPy's implementation - we could compare with the NumPy implementation to see if there's a more efficient way we can implement it.

I can't exactly reproduce this, but the problem is that numba's np.full uses np.ndindex as the iterator, which is quite slow. Some of the other numba array creation routines that are fill element-by-element use array.flat and iterate over it using enumerate, which is a good bit faster.
@jit
def nb_full(shape, fill_value, dtype):
    ans = np.empty(shape, dtype)
    fl = ans.flat
    for idx, v in enumerate(fl):
      fl[idx] = fill_value
    return ans

@jit
def f4(shape):
  return nb_full(shape, np.nan, np.float64)

@jit
def f1(shape):
    return np.full(shape, np.nan, np.float64)

f1(shape)
f4(shape)

t0 = time.time()
np.full(shape, np.nan, np.float64)
print(time.time() - t0)

t0 = time.time()
f1(shape)
print(time.time() - t0)

t0 = time.time()
f4(shape)
print(time.time() - t0)

On my end, this outputs the following:
0.1057584285736084 # numpy
0.2277970314025879 # current implementation
0.10829496383666992 # array.flat implementation

This at least matches the numpy implementation, which should be as good as it gets.

@rishi-kulkarni Many thanks for providing the additional info and example! Would you be keen to modify Numba's flat implementation so that it uses the same process as your nb_full function and submit a PR?

@gmarkall Yep, not a problem. I'll take a crack at it this weekend.

@gmarkall Yep, not a problem. I'll take a crack at it this weekend.

Many thanks, that's very kind of you - please though, don't feel any pressure to hurry on it... Whenever it's convenient for you to work on it, that will be more than great!


Asserts in tests

I was dabbling around and noticed the Assert.Equal methods in the tests are having the wrong signature.
For example:
Assert.Equal(result.Succeeded, expected);
should be:
Assert.Equal(expected, result.Succeeded);
Is it OK to change this (Assert.True and Assert.False) by using Shouldly?
This way all our tests are written with Shouldly.

I agree, we should switch fully to shouldly 👍


Feature request - add comment style to eslint.codeAction.disableRuleComment

TLDR:
I'd like a setting added to eslint.codeAction.disableRuleComment to have it inject block-style comments (/* */) rather than line style (//)
Context:
I use eslint-require-description to enforce the use of comments for eslint-ignore comments. (See https://github.com/eslint/rfcs/pull/33).
This helps us reduce abuse of ignore comments and to aid in code review. We also have a formatting rule that limits comment line length and wraps them.
The automatic injection of ignore rules is very useful, but when adding descriptions to said ignore comments I nearly always overrun our line length and have to convert the comment to a block style. This does look nicer and I don't want to disable this feature.
It would be very nice to be able to have a setting to have the ignore rule use block-style comments. The most logical place I see to attach such a setting is to eslint.codeAction.disableRuleComment.

I think we can close this now @dbaeumer :)
@OneHoopyFrood see #1499 for info on using the new setting!

@MariaSolOs thanks for pointing this out.
Closing the issue.


[DOCS] Add PR & Issue Templates

Add the following:
Issue Templates - Basic Issue Templates
PR Template - Fallback PR Template

-- I will create this

-- I will create this

I actually created this so people new to open-source can contribute, hence I added the EddieHub label, but you can work on this too!

Any update @Adarsh-jaiss?

@KendallDoesCoding can i work on this ??

@KendallDoesCoding can i work on this ??

Yes you can!


Long name in ConnectionManager hides control buttons

Create new connection
Give it long name
Save

https://github.com/Microsoft/RTVS/commit/8de1e26b844cb341ffc08044aa4950412d7dd7a5


fixed compatibility with Processing 3

First thanks @sebnil this code is tremendously helpful!!
I'm not a coder but this was too frustrating not to be able to use the control panel so I looked around and used this fix in the reported issue https://github.com/sojamo/controlp5/issues/17.
Tested on Processing 3.5.4 on Ubuntu 18.04.
Funny is the second frame is blank when the stop button label is "stop", so I just changed it to "stop1"

Cool thank you! I tested it and it seems to work (I could not test on a physical microprocessor unfortunately but I believe that code should still work the same).
If you make any other improvements please share.


Is the negative samples in PointInfoNCE across batch dimension?

Thank you for the great work. I really love it.
I have questions about the PointInfoNCE implementation. Is the negative samples in PointInfoNCE across batch dimension?
The paper defined PointInfoNCE

In this formulation, we only consider points that have at least one match and do not use additional non-matched points as negatives. For a matched pair (i, j) ∈ P, point feature f^1_i will serve as the query and f^2_j will serve as the positive key k+. We use point feature f^2_k where ∃(·, k) ∈ P and k != j as the set of negative keys.

I wonder the all the pair in the matched pair set P here is the two views in the same scene or bigger than that. When I read the paper and pseudo code, I assume the batch dimension is ignored. For a point in x^1,  the negative keys are all from the x^2. The P is down sample to 4096 point pairs for each mini-batch.
However, in the implementation ddp_trainer.PointNCELossTrainer , it seems like the negative keys are across the batch dimension. The negative samples for a point in x^1 may come from points in other scene. Am I correct?
    sinput0 = ME.SparseTensor(
        input_dict['sinput0_F'], coords=input_dict['sinput0_C']).to(self.cur_device)
    F0 = self.model(sinput0).F

    sinput1 = ME.SparseTensor(
        input_dict['sinput1_F'], coords=input_dict['sinput1_C']).to(self.cur_device)
    F1 = self.model(sinput1).F

    N0, N1 = input_dict['pcd0'].shape[0], input_dict['pcd1'].shape[0]
    pos_pairs = input_dict['correspondences'].to(self.cur_device)

    q_unique, count = pos_pairs[:, 0].unique(return_counts=True)
    uniform = torch.distributions.Uniform(0, 1).sample([len(count)]).to(self.cur_device)
    off = torch.floor(uniform*count).long()
    cums = torch.cat([torch.tensor([0], device=self.cur_device), torch.cumsum(count, dim=0)[0:-1]], dim=0)
    k_sel = pos_pairs[:, 1][off+cums]

    q = F0[q_unique.long()]
    k = F1[k_sel.long()]

    if self.npos < q.shape[0]:
        sampled_inds = np.random.choice(q.shape[0], self.npos, replace=False)
        q = q[sampled_inds]
        k = k[sampled_inds]

Hi @liu115 - Thank you for your question. You are totally right, the negative keys are sampled across the entire mini-batch (more accurately, only the per GPU mini-batch for distributed training, since we are not doing all_gather operations across all GPUs when computing the loss).
Unfortunately this is not clearly noted in the paper when we are describing the formulation. However, we recently did additional experiments and tried pre-training with negatives sampled only from the scene that contains the positive. The results are very similar, at least on the S3DIS semantic segmentation task we tested.
Let me know if you have further questions.

Thank you for the clarification.


Attach to [:phoenix, :live_view, :render]

Aside from :mount, :handle_params, and :handle_event, attach to
:render in the LiveView integration.
With this patch, the LiveView integration hooks into all LiveView
telemetry
events (https://hexdocs.pm/phoenix_live_view/telemetry.html).

This PR belongs to this issue https://github.com/appsignal/feature-requests/issues/325, right?
Also the PR is broken on a formatting issue.


Inspect should accept a --target

Version
3.0.0-beta.9
Reproduction link
https://github.com/doublemarked/vue-libconf-issues
Steps to reproduce
vue inspect
What is expected?
vue inspect should show webpack configuration that matches that used when building the project, including configuration options like --target lib and --target wc, both of which inject custom webpack config.
What is actually happening?
Running vue inspect produces inaccurate output because it cannot be instructed to load the lib-specific configuration.

This would require inspect to include all other flags including --name and entry, because the config relies on those values. In addition, both targets uses multiple configs.
In fact, the only difference between the lib/wc config vs. the app version are entry/output options, which are not customizable anyway, so I don't think there is too much value in here considering the complexity in implementing it. I'd be open to a PR if someone wants to work on this though.


Can't release with untracked files

$ ./gradlew clean release

[...]

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':checkCommitNeeded'.
> You have unversioned files:
  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  ?? relink
  ?? relink.py
  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

This might be intentional, but I don't understand why it would be useful. The files are scripts I used to fix image links and are not a part of Cardshifter, though I found it useful to keep them in the same directory.
I worked around this by stashing those files before re-running Gradle.
If we decide to not fix this, the wiki on creating a release should be updated to explain this quirk.

I don't think that this should be fixed. Such files should either be removed, be added to .gitignore, or be added to the repository. I think this is a completely reasonable alert by the Gradle-release plugin.
For the record, I believe this is configurable, but I don't think we should change the configuration.

Basically what the task seems to do is to check that the working directory is in a clean state, which is a good thing to have before making a release.

I added this as a step to https://github.com/Cardshifter/Cardshifter/wiki/Creating-a-release


proper calendars for religious orders (e.g. Dominicans)

Would be great if this service could be configured to incorporate  the calendar of a religious order such as the Dominicans. Have you considered this?

Hello @jhemak, yes I have been thinking about how to integrate calendars for Religious Orders that have an approved Proper Calendar. It will take some planning on how to go about doing this, since the Proper of Religious Orders (in my experience) adapts to the local "national" calendar of the nation in which they are present. So the calendar for the Dominicans in the United States will be in English and will also have the patron saints of the Americas and national celebrations such as Day of Prayer for the Unborn or Thanksgiving, whereas the calendar for the Dominicans in Italy will be in Italian and have the patron saints of Europe and of Italy.
Am I correct in this interpretation?
If this is the case, we could plan on Proper Calendars for Religous Orders listing the nations in which they are present, so as to integrate with those national / wider region calendars, and being translatable for the languages in those nations.
This will take some time and effort to accomplish. I've been working in the meantime at completely refactoring the API for better expected data structures and better API paths, and I still have quite a bit of work to do to finish this process (these changes will be released as v4 of the API). So perhaps integration of Proper Calendars for Religious Orders could be an idea for a v5 of the API.

to this end, it would also be useful to have a list of all Religious Orders that have an approved Proper Calendar, other than having the data for each of these calendars.
Do you have a copy of the Proper for the Dominicans that you can share?

That's great.  I am not an expert, but I believe you are correct.
Here is a link to the official calendar for the Dominicans, published in Latin in 2019:
https://www.op.org/calendar-ordinis-praedicatorum/
And here is the English version used in the USA (2nd link at this page):
https://dominicanvocations.com/news/calendarium-ordinis-praedicatorum

OP English Calendar 2019.pdf

Calendarium Ordinis Praedicatorum 2019.pdf


WIP: adds support for cloud SQL second gen

Coverage decreased (-2.4%) to 95.894% when pulling 0277dcfe280b3e55575ca330c78382e6fd007747 on cloud-sql-second-gen into 143fd695447ea562c47e456bd6c6396fd45d9760 on master.

Coverage decreased (-2.009%) to 96.055% when pulling b2794e844d263bc1c0155845047439cbbba9bfa1 on cloud-sql-second-gen into a30b7934e826d8ae3a3195b54a49ad5ca536d492 on master.

Coverage decreased (-2.009%) to 96.055% when pulling b2794e844d263bc1c0155845047439cbbba9bfa1 on cloud-sql-second-gen into a30b7934e826d8ae3a3195b54a49ad5ca536d492 on master.

Coverage decreased (-0.2%) to 97.855% when pulling 90a1a1999aca8334d3927784633a9a139e75549e on cloud-sql-second-gen into a30b7934e826d8ae3a3195b54a49ad5ca536d492 on master.

Coverage decreased (-0.2%) to 97.855% when pulling 33644fb078b8403748e309f2eedf6d41cdce4493 on cloud-sql-second-gen into a30b7934e826d8ae3a3195b54a49ad5ca536d492 on master.

@tmatsuo made some pretty large changes - removed google/apiclient in favor of DatastoreClient. PTAL!

The test says "Class 'Google_Client' not found in /home/travis/build/GoogleCloudPlatform/getting-started-php/4-auth/src/app.php on line 72"

Coverage decreased (-0.7%) to 97.337% when pulling 5c88bbb5dad30429edeaeee0e3b51d8cd1ddb455 on cloud-sql-second-gen into e6d2f1c8fb42d6681a3893d05a4963420203b3b4 on master.

Coverage decreased (-0.8%) to 97.229% when pulling cfb0c2280911a6b61a36f3735d944eb025771ed7 on cloud-sql-second-gen into e6d2f1c8fb42d6681a3893d05a4963420203b3b4 on master.

Coverage decreased (-0.8%) to 97.229% when pulling cfb0c2280911a6b61a36f3735d944eb025771ed7 on cloud-sql-second-gen into e6d2f1c8fb42d6681a3893d05a4963420203b3b4 on master.

Coverage decreased (-0.8%) to 97.229% when pulling cfb0c2280911a6b61a36f3735d944eb025771ed7 on cloud-sql-second-gen into e6d2f1c8fb42d6681a3893d05a4963420203b3b4 on master.


LoongArch64: Enable cmake cross-compilation

Refer to the following instructions：
cmake ../ -DCMAKE_TOOLCHAIN_FILE=toolchain.cmake
                -DTARGET=LOONGSON3R5
                -DDYNAMIC_ARCH=1
                -DCMAKE_C_COMPILER=${CROSS_TARGET}-gcc
                -DCMAKE_Fortran_COMPILER=${CROSS_TARGET}-gfortran

Contents of toolchain.cmake:
set(CMAKE_SYSTEM_NAME Linux)
set(CMAKE_SYSTEM_PROCESSOR loongarch64)

@XiWeiGu  @martin-frbg
This PR still uses old core names since it was issued before the Rename core PR https://github.com/OpenMathLib/OpenBLAS/pull/4900 was merged. I just did some tests and find that we should rename those old core names to new ones to avoid cmake errors. See below.
System details: Loongson 3A6000 CPU, Debian sid, kernel 6.11.0, gcc 14.2.0, gfortran 14.2.0, cmake 3.30.4.
cmake commands: CC=gcc FC=gfortran cmake -B build -DBUILD_TESTING=OFF -DUSE_OPENMP=1 -DDYNAMIC_ARCH=1  and then cmake --build build.
The result:
...
-- Compiling a 64-bit binary.
-- Reading vars from /home/loongson/test/build/kernel/loongarch64/KERNEL...
-- Reading vars from /home/loongson/test/build/kernel/loongarch64/KERNEL.LOONGSON2K1000...
CMake Error at cmake/utils.cmake:23 (file):
  file STRINGS file
  "/home/loongson/test/build/kernel/loongarch64/KERNEL.LOONGSON2K1000" cannot
  be read.

-- GEMM multithread threshold set to 4.
-- Multi-threading enabled with 8 threads.
-- Running getarch
-- GETARCH results:
CORE=LA464
LIBCORE=la464
NUM_CORES=8
MAKEFLAGS += -j 8

-- Compiling a 64-bit binary.
-- Reading vars from /home/loongson/test/build/kernel/loongarch64/KERNEL...
-- Reading vars from /home/loongson/test/build/kernel/loongarch64/KERNEL.LOONGSON3R5...
CMake Error at cmake/utils.cmake:23 (file):
  file STRINGS file
  "/home/loongson/test/build/kernel/loongarch64/KERNEL.LOONGSON3R5" cannot be
  read.
Call Stack (most recent call first):
  kernel/CMakeLists.txt:13 (ParseMakefileVars)
  kernel/CMakeLists.txt:1365 (build_core)

LOONGSONGENERIC
LOONGSON2K1000
LOONGSON3R5
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Success
-- Found Threads: TRUE
-- Generating openblas_config.h in include/openblas
-- Generating f77blas.h in include/openblas
-- Generating cblas.h in include/openblas
-- Copying LAPACKE header files to include/openblas
-- Configuring incomplete, errors occurred!

I then rename "LOONGSONGENERIC LOONGSON2K1000 LOONGSON3R5 " at line 98 in cmake/arch.cmake:
https://github.com/OpenMathLib/OpenBLAS/blob/624e9d110e121030041f8a75c440c33fc0633c05/cmake/arch.cmake#L97-L99
to new core names "LA64_GENERIC LA264 LA464", and also rename old core names at lines 1352,1367,1383 in cmake/prebuild.cmake:
https://github.com/OpenMathLib/OpenBLAS/blob/624e9d110e121030041f8a75c440c33fc0633c05/cmake/prebuild.cmake#L1352-L1383
to "LA64_GENERIC", "LA264", and "LA464" correspondingly.
After these changes I observe that cmake errors for LOONGSON2K1000 and LOONGSON3R5 disappear. But a new cmake error appears:
...
CMake Error at cmake/utils.cmake:23 (file):
  file STRINGS file
  "/home/loongson/test/build/kernel/loongarch64/KERNEL.LA64_GENERIC" cannot be
  read.
Call Stack (most recent call first):
  kernel/CMakeLists.txt:13 (ParseMakefileVars)
  kernel/CMakeLists.txt:1365 (build_core)
...

since there is no file called "kernel/loongarch64/KERNEL.LA64_GENERIC":

Rename the file "kernel/loongarch64/KERNEL.LOONGSONGENERIC" to "kernel/loongarch64/KERNEL.LA64_GENERIC" the above cmake error disappears and the compilation works well.

Yes, the #4904 was revised based on the old core name, and a patch is still needed to fix the cmake build after the core name revision.

My fault for merging these in the wrong order, sorry. I'll try to fix this later today


Fix Resample instantiation to include device argument

What does this PR do?
This pull request fixes a runtime error that occurs when the Resample object from torchaudio.transforms is instantiated without being assigned to the specified device. The lack of device assignment can cause a mismatch when the downstream operations are performed on tensors residing on non-CPU devices (e.g., CUDA devices).
The change includes the addition of the .to(device) method call during the Resample object instantiation, ensuring that the object is created on the correct device as specified by the device argument in the download_vctk function.
No dependencies are added with this change, and the fix is isolated to the instantiation of the Resample object.
Before submitting

[x] Did you read the contributor guideline?
[x] Did you make sure your PR does only one thing, instead of bundling different changes together?
[x] Did you make sure to update the documentation with your changes? (if necessary)
[ ] Did you write any new necessary tests? (not for typos and docs) (You would mark this as complete if you added tests, otherwise explain why they are not necessary)
[x] Did you verify new and existing tests pass locally with your changes?
[x] Did you list all the breaking changes introduced by this pull request? (Mark this as complete if there are no breaking changes)
[x] Does your code adhere to project-specific code style and conventions?

PR review

[x] Is this pull request ready for review? (if not, please submit in draft mode)
[x] Check that all items from Before submitting are resolved
[x] Make sure the title is self-explanatory and the description concisely explains the PR
[ ] Add labels and milestones (and optionally projects) to the PR so it can be classified
[x] Confirm that the changes adhere to compatibility requirements (e.g., Python version, platform)
[x] Review the self-review checklist to ensure the code is ready for review

Thank you for the fix @ywk991112!


fix: add missing options.ignoreOrder details in Error message

https://github.com/webpack-contrib/extract-text-webpack-plugin/pull/520 Adds an option: "ignoreOrder" this is not listed in the available options in the error output for this plugin. Which can be confusing.

I've signed the CLA ... Guess it's pending.

@gl2748 - It's pretty much an instant thing, I'd try it agin. If that doesn't work -> close & open pull request to trigger it again.
If that doesn't work, @ me and i'll try and figure out what the deal is.


⚠ Bofrost.lu has degraded performance

In 56eb8a6, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1261 ms

Resolved: Bofrost.lu performance has improved in a6c007f.


fix filepath for screenshotter tmp dir. fixes #6675

fixes https://github.com/zumper/zumper_code/issues/6675.  Will create PR for updated SHA in zumper repo once this is merged.
Ya embarrassing error.  Sorry.
Tested it with env variable set and it works.

lgtm.


Extension massively slowing down vsCode

This plugin is incredible, unfortunately it makes vsCode almost unusable. When trying to 'Rename Symbol' it was taking up to 20 seconds to respond, once this extension was disabled it is near instant.
Hover information was also taking 5+ seconds to show.
Extension version: v0.0.17
VSCode Version: 1.84.2
Apple M1 Pro Mac Sonoma 14.1.1

Hi @locateAChris! Thanks for bringing up this issue. Performance has been a continued struggle when developing this extension and I am always trying to improve it.
Would you mind sharing the type that is causing 5+ seconds on hover? Does this happen only on the first time you hover over something in a project, or anytime you hover over something even after the extension has fully loaded?

faces same issue
it's really slow on any project with playwright installed.
may be it's possible to incorporate some kind of logs with performance metrics? then we could easily report if anything is really broken

Hi @ColCh and @locateAChris -
With it's current implementation using ts-morph, unfortunately, there is nothing that can be done to improve the speed for the extension.
However, I am currently exploring re-engineering the extension as a TypeScript plugin. This should greatly improve the performance issues. I am currently trying to re-scope the project as part of this to determine which features should move forward.
If you don't mind me asking, what do you use the extension for? Do you ever use the sidebar, or is the hover menu the main appeal?

Sure! Of course. Personally, I often find myself using it as hover preview. I personally never use sidebar for types, in my opinion it's too slow to check out and strikes me out of deep focus

Hi @ColCh and @locateAChris
Here is a link to try out the pre-release for the re-engineered project, which should include massive performance increases. If interested in testing out, simply download the vsix file under the release and install using the official instructions found here. If you try it out, please let me know if your performance issues are resolved with this!
https://github.com/mylesmmurphy/prettify-ts/releases/tag/v0.1.0-alpha

using it as hover preview. I personally never use sidebar for types, in my opinion it's too slow to check out and strikes me out of deep focus
double it

Hi @inoyakaigor @ColCh @locateAChris
I just released v0.1.5 of the extension which includes a massive overhaul of how it behaves under the hood, as well as many customization options in the settings. Please try this version and let me know if your problems are resolved.

Works good to me now! Many thanks :)

Works good to me now! Many thanks :)

Great to hear! Closing this now 🥳


🍒 Cherry pick PR #21447 to staging 🍒

🍒 Cherry pick https://github.com/Expensify/App/pull/21447 to staging 🍒

This pull request has merge conflicts and can not be automatically merged. :disappointed:
Please manually resolve the conflicts, push your changes, and then request another reviewer to review and merge.
Important: There may be conflicts that GitHub is not able to detect, so please carefully review this pull request before approving.

Sorry, we're just testing / working through kinks for now


CSS attr() function

CSS attr() function

This issue was imported from Google Moderator
Moderator votes: +8
Issue added by Timwi on 2014-06-19
To vote this issue up or down, simply include +1 or -1 in your comment.

Already part of http://caniuse.com/#feat=css-gencontent


Date range with multiple months

I use DatePicker to select date range as stated in https://hacker0x01.github.io/react-datepicker/#example-12 and I've set multiple months visible to 2. The problem is that selected date is always shown within first month, whereas I would like it show start date as first month and end date as second month. Is it possible?

this is something im looking into too and it would be so much smoother to be able to do that rather than 2 boxes

I need to pre-populate multiple date range in range picker. How i need to implement

@mudassirmmt this could help
<DatePicker   inline   selected={this.state.startDate}   startDate={this.state.startDate}   endDate={this.state.endDate}   onChange={this.handleDateSelect}   monthsShown={2}   shouldCloseOnSelect={false} />

@mudassirmmt this could help
<DatePicker
  inline
  selected={this.state.startDate}
  startDate={this.state.startDate}
  endDate={this.state.endDate}
  onChange={this.handleDateSelect}
  monthsShown={2}
  shouldCloseOnSelect={false}
/>

Thanks.
But i need to display multiple date range at once in the date range picker.
My requirement is to select date range at once at a time but need to pre populate(dispaly) all date ranges at once in the calender.

Any updates on this?


What is the License / Source of the BinaryImage files?

@mattmassicotte the BinaryImage files do not contain a header with your name. I was curious what the source of them is and what the license of the files is?
I would have to know this to use your library, but the on-device symbolication is quite slick especially if done during a background processing task or something like. Since Apple explicitly states in their videos symbolication is to take place off device, it seems like a happy compromise that would be an accepted solution by them.

The license covering these is the one at the root. My intention is for it to cover the entire repo.
I had assumed that was implied, but perhaps I'm wrong. Do you think each file need its own explicit license reference?
The general technique used for this symbolication process uses only public API, and is used by other crash reporting services. So should be 100% App Store-compatible!

@mattmassicotte since it didn't have the header I wasn't sure if you were the author or if you pulled it from somewhere else that would potentially have its own license or be updated outside of this SPM.
I let SwiftLint find these things for me when the headers don't match the code. The following header style was not in BinaryImage.h / .m
//
//  CallStackTree.swift
//  Meter
//
//  Created by Matt Massicotte on 2020-06-30.
//

Yeah, I began removing the header comment from new files a while ago. But, I typically don't go back to remove pre-existing ones unless I work in the file. Very sorry about the confusion!

Hope this is now all resolved!


Echo current deliverable in non-verbose mode

Description
I'm building hundreds of deliverables in a batch on GitHub Actions. So far I am publishing with --verbose, which leads to huge log files. My log files have exceeded now a size of 50 MB (for a plaintext file!). Now I am getting difficulties to parse it. The idea was to turn-off the --verbose mode.
The problem now is, that the context is now missint in the log. I do not know what deliverable has thrown what error. What I am missing are these lines:
Publishing deliverable 67 of 159: NAME OF DELIVERABLE [id-of-deliverable]

Possible Solution
Add these lines to non-verbose logging.
Potential Alternatives
None

Currently, #4100 (not yet merged) only issues deliverable messages in verbose mode. Like you, I would also like to see deliverable messages in non-verbose mode too. This is for two reasons:

Publishing multiple deliverables tends to have a longer runtime and thus is more deserving of a status indicator.
The deliverable messages provide context for errors that occur.

Closing this as a duplicate of https://github.com/dita-ot/dita-ot/issues/3948.


#60: allow retrieving the generated request ids

Auth now has getLastLoginRequestId/getLastLogoutRequestId methods
that allow retrieving the id of the generated AuthnRequest/LogoutRequest
message to be used in response validation

@miszobi thanks for the contribution.


Update README.md

Fix what I believe to be a typo

We just merged a PR to rename the two structs for trajectory sampling (https://github.com/TuringLang/AdvancedHMC.jl/pull/114).
Related issue: https://github.com/TuringLang/AdvancedHMC.jl/issues/99

Ah, nvm then :)


RFC: Exploration of use-cases for Angular JIT compilation mode

@satanTime Maybe this is interesting for you because it will affect the test as well.
The introduction from the Angular team on this topic:
The Angular team would like to understand the remaining use-cases for Angular's JIT compilation mode, and discover any gaps that prevent adoption of the AOT compilation mode for these use-cases.
You would like the community, to share with Angular-Team how and why you still use JIT mode, and what prevents you from using AOT.
See also:

https://github.com/angular/angular/issues/43133
https://github.com/angular/angular/issues/43133#issuecomment-898477405

...you are right that the testing components today rely on JIT. Usually not because they are dynamic but because you need the flexibility to declare them inline, usually within functions of a test file as your example shows.

Hi @SerkanSipahi,
thanks for the info. it looks like we are fine here based on their conclusion.
I'll add support for .ɵ* once Angular runs tests in AOT out of the box, but considering the trend that everybody uses jest for angular now, and jest development is so slow that I cannot imagine how long it will take to migrate everything there.


WIP: Fix CircleCI

CircleCI is failing on a couple examples on main and a recent PR:
https://app.circleci.com/pipelines/github/mne-tools/mne-python/13057/workflows/73fd5c5d-72f1-4efb-be9a-7ba7892b8b7c/jobs/42068
https://app.circleci.com/pipelines/github/mne-tools/mne-python/13070/workflows/a2c08a05-2b91-4c82-ad77-4356b1ca0560/jobs/42097
I hope this fixes the error. We'll see!

Closing for #10388


Make this crate clippy clean

Running cargo clippy spits out a ton of simplifications and patterns that could be replaced by more canonical code.

Thanks for letting me know. I will take a look when I have time (on or after Feb 2025)


How to remove default spacing between tables

hey,
is there a way to remove space between tables?. i just tried to remove space between tables, but in this caracal documentation i found nothing that can help  me on this.
please help me on this.

There's a PR available right now that purports to handle the issue.  I haven't had time to review and integrate the change yet, but if you need an immediate solution, I'd peg bundler to that branch for the short term.  At least one other user felt the PR was helpful.
I'll have time in December to catch up on the various PRs that have been submitted.  There should be a new official release in the next few weeks.

thank you for your update, we can wait till December.

Hi John,
We are waiting for your official release. It will be a great help if you can release this within a week.
Thanks.

That's definitely not going to happen.  I won't have time for Caracal until later this month when I have time off for Christmas/New Year's.

This is fixed in Release v1.4.0.  Table spacing must now be handled explicitly.


Not linting

Hi guys.
I jut installed linter-js-standard on my system
atom 1.1.0
apm  1.1.1
node 0.10.40
ubuntu-gnome 14.04
I'm struggling to get it to lint. I've tried the following:

Change node version to 0.11.x, 0.12.x, 4.x
Disable all other packages (apart from linter ofc)
made sure everything is latest version
force lint in command palette

None of which seem to work
I did have linter-jscs and linter-jshint installed and they seem to lint ok.
I'm running out of things to try. Got any ideas?
Cheers.

Not to worry,
I finally got it to work after reinstalling a few times. I'll re-open if I can reliably reproduce it again.
Cheers.


Apply Limitations on Streaming Services

Context
On 6/26 a CAMPD user requested a large amount of data and caused CAMPD to crash.
Need to apply limititaions on the streaming services
Discussed if the data is going to take longer than 15-20 mins need to cut it off. Need to discuss requirements

Will need to take a look at the endpoints in the streaming services and their parameter. Will need to have further discussion on how to limit the endpoints

Addressed with the time out.


train co_deformable_detr_r50_1x_coco, the AP lower.

Hi Thank you for your great work!
When I used "tools/dist_train.sh projects/configs/co_deformable_detr/co_deformable_detr_r50_1x_coco.py 1 ./weight/" trained the co_deformable_detr_r50_1x_coco on coco2017, not modify the parameters, and not using the pretrain model, the AP is lower. Should I use the pretrain model for training? Or others need modify? I am looking forward to your reply.
I test the coco result:
{  Average Precision  (AP) @[ IoU=0.50:0.95 | area=   all | maxDets=100 ] = 0.461
Average Precision  (AP) @[ IoU=0.50      | area=   all | maxDets=1000 ] = 0.633
Average Precision  (AP) @[ IoU=0.75      | area=   all | maxDets=1000 ] = 0.502
Average Precision  (AP) @[ IoU=0.50:0.95 | area= small | maxDets=1000 ] = 0.280
Average Precision  (AP) @[ IoU=0.50:0.95 | area=medium | maxDets=1000 ] = 0.499
Average Precision  (AP) @[ IoU=0.50:0.95 | area= large | maxDets=1000 ] = 0.604
Average Recall     (AR) @[ IoU=0.50:0.95 | area=   all | maxDets=100 ] = 0.649
Average Recall     (AR) @[ IoU=0.50:0.95 | area=   all | maxDets=300 ] = 0.649
Average Recall     (AR) @[ IoU=0.50:0.95 | area=   all | maxDets=1000 ] = 0.649
Average Recall     (AR) @[ IoU=0.50:0.95 | area= small | maxDets=1000 ] = 0.433
Average Recall     (AR) @[ IoU=0.50:0.95 | area=medium | maxDets=1000 ] = 0.697
Average Recall     (AR) @[ IoU=0.50:0.95 | area= large | maxDets=1000 ] = 0.826 }
some log(loss is bigger than yours):
{"mode": "train", "epoch": 1, "iter": 50, "lr": 0.0002, "memory": 10678, "data_time": 0.07217, "enc_loss_cls": 2.1538, "enc_loss_bbox": 1.30198, "enc_loss_iou": 1.16616, "loss_cls": 2.14317, "loss_bbox": 2.60367, "loss_iou": 2.14343, "d0.loss_cls": 1.96131, "d0.loss_bbox": 2.63388, "d0.loss_iou": 2.16948, "d1.loss_cls": 2.15417, "d1.loss_bbox": 2.60833, "d1.loss_iou": 2.15319, "d2.loss_cls": 2.23642, "d2.loss_bbox": 2.60134, "d2.loss_iou": 2.14901, "d3.loss_cls": 2.1437, "d3.loss_bbox": 2.60013, "d3.loss_iou": 2.14763, "d4.loss_cls": 2.11218, "d4.loss_bbox": 2.60227, "d4.loss_iou": 2.14508, "loss_rpn_cls": 3.50659, "loss_rpn_bbox": 0.47681, "loss_cls0": 5.12987, "acc0": 94.27344, "loss_bbox0": 1.34195, "loss_cls1": 14.23468, "loss_bbox1": 13.64706, "loss_centerness1": 7.91569, "loss_cls_aux0": 1.76192, "loss_bbox_aux0": 1.0423, "loss_iou_aux0": 0.56317, "d0.loss_cls_aux0": 1.65817, "d0.loss_bbox_aux0": 1.03151, "d0.loss_iou_aux0": 0.51077, "d1.loss_cls_aux0": 1.65367, "d1.loss_bbox_aux0": 1.03382, "d1.loss_iou_aux0": 0.52373, "d2.loss_cls_aux0": 1.72817, "d2.loss_bbox_aux0": 1.03599, "d2.loss_iou_aux0": 0.53485, "d3.loss_cls_aux0": 1.75864, "d3.loss_bbox_aux0": 1.0379, "d3.loss_iou_aux0": 0.5451, "d4.loss_cls_aux0": 1.75284, "d4.loss_bbox_aux0": 1.03995, "d4.loss_iou_aux0": 0.55428, "loss_cls_aux1": 1.79561, "loss_bbox_aux1": 1.18594, "loss_iou_aux1": 1.14411, "d0.loss_cls_aux1": 1.69971, "d0.loss_bbox_aux1": 1.18362, "d0.loss_iou_aux1": 1.14339, "d1.loss_cls_aux1": 1.71459, "d1.loss_bbox_aux1": 1.18391, "d1.loss_iou_aux1": 1.14331, "d2.loss_cls_aux1": 1.76991, "d2.loss_bbox_aux1": 1.18443, "d2.loss_iou_aux1": 1.14341, "d3.loss_cls_aux1": 1.80116, "d3.loss_bbox_aux1": 1.18488, "d3.loss_iou_aux1": 1.14361, "d4.loss_cls_aux1": 1.78536, "d4.loss_bbox_aux1": 1.18529, "d4.loss_iou_aux1": 1.14385, "loss": 136.48589, "grad_norm": 158.88891, "time": 0.77338}
{"mode": "train", "epoch": 1, "iter": 100, "lr": 0.0002, "memory": 10678, "data_time": 0.00637, "enc_loss_cls": 1.76474, "enc_loss_bbox": 1.1683, "enc_loss_iou": 1.16472, "loss_cls": 2.05801, "loss_bbox": 2.06883, "loss_iou": 1.80247, "d0.loss_cls": 1.88228, "d0.loss_bbox": 2.09778, "d0.loss_iou": 1.81527, "d1.loss_cls": 1.93532, "d1.loss_bbox": 2.0773, "d1.loss_iou": 1.79806, "d2.loss_cls": 1.96658, "d2.loss_bbox": 2.06948, "d2.loss_iou": 1.80279, "d3.loss_cls": 2.03127, "d3.loss_bbox": 2.06957, "d3.loss_iou": 1.80236, "d4.loss_cls": 2.05364, "d4.loss_bbox": 2.06872, "d4.loss_iou": 1.80287, "loss_rpn_cls": 2.22799, "loss_rpn_bbox": 0.37238, "loss_cls0": 3.29344, "acc0": 96.75781, "loss_bbox0": 1.24619, "loss_cls1": 13.36668, "loss_bbox1": 13.64313, "loss_centerness1": 7.90339, "loss_cls_aux0": 1.54687, "loss_bbox_aux0": 1.09403, "loss_iou_aux0": 0.55488, "d0.loss_cls_aux0": 1.37439, "d0.loss_bbox_aux0": 1.09063, "d0.loss_iou_aux0": 0.53468, "d1.loss_cls_aux0": 1.39558, "d1.loss_bbox_aux0": 1.0916, "d1.loss_iou_aux0": 0.54084, "d2.loss_cls_aux0": 1.44337, "d2.loss_bbox_aux0": 1.09214, "d2.loss_iou_aux0": 0.54455, "d3.loss_cls_aux0": 1.49814, "d3.loss_bbox_aux0": 1.09262, "d3.loss_iou_aux0": 0.54755, "d4.loss_cls_aux0": 1.52944, "d4.loss_bbox_aux0": 1.09319, "d4.loss_iou_aux0": 0.55106, "loss_cls_aux1": 1.59381, "loss_bbox_aux1": 1.14691, "loss_iou_aux1": 1.17268, "d0.loss_cls_aux1": 1.40565, "d0.loss_bbox_aux1": 1.14653, "d0.loss_iou_aux1": 1.17178, "d1.loss_cls_aux1": 1.44506, "d1.loss_bbox_aux1": 1.14654, "d1.loss_iou_aux1": 1.17201, "d2.loss_cls_aux1": 1.4978, "d2.loss_bbox_aux1": 1.14658, "d2.loss_iou_aux1": 1.17212, "d3.loss_cls_aux1": 1.55235, "d3.loss_bbox_aux1": 1.14668, "d3.loss_iou_aux1": 1.17229, "d4.loss_cls_aux1": 1.57807, "d4.loss_bbox_aux1": 1.14692, "d4.loss_iou_aux1": 1.1726, "loss": 122.95549, "grad_norm": 107.07448, "time": 0.70219}

I will check it, do you use imagenet pretrained r50?

I will check it, do you use imagenet pretrained r50?
Thank you for your feedback!
No, I havn't using any models for pretained.
Should I use imagenet pretrained r50?  Could you sent me a link?

The code init_cfg=dict(type='Pretrained', checkpoint='torchvision://resnet50') in r50 configs means we use the resnet50 weights from torchvision

The code init_cfg=dict(type='Pretrained', checkpoint='torchvision://resnet50') in r50 configs means we use the resnet50 weights from torchvision
Yes, I didn't modify the config "co_deformable_detr_r50_1x_coco.py", so configs means we use the resnet50 weights.
I used cuda number one train it, Will it make a difference?

20230803_035648.log
This is my log, please help me check there has any question. Thank you very much.

It seems you only use 1 GPU for training. We use a batch size of 16 (2 images per GPU).


Why does Set-AksHCIRegistration remove tags from the resource group?

Noticed when running this is removed the tags from the resource group? Is there any reason to do this as we have policies in place to deny creation of a resource group without tags attached,

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

ID: 37e3139e-399b-be0f-d80e-d78b094b214a
Version Independent ID: f18262fc-0401-68d0-964a-ee4e19be10e0
Content: Use PowerShell to set up Kubernetes on Azure Stack HCI and Windows Server clusters - AKS hybrid
Content Source: AKS-Hybrid/kubernetes-walkthrough-powershell.md
Service: azure-stack
Sub-service: aks-hci
GitHub Login: @sethmanheim
Microsoft Alias: sethm

@anwather
It would be great if you could add a link to the documentation you are following for these steps? This would help us redirect the issue to the appropriate team. Thanks!!

https://learn.microsoft.com/en-us/azure/aks/hybrid/kubernetes-walkthrough-powershell#step-4-sign-in-to-azure-and-configure-registration-settings

@anwather
Thank you for bringing this to our attention.
I've delegated this to content author @sethmanheim, who will review it and offer their insightful opinions.

@sethmanheim
Could you please review add comments on this, update as appropriate.

@anwather Thank you for reaching out. I am not seeing the issue you mention. However, as we are moving to a new content feedback system, we have opened corresponding work items and are tracking all open issues in our internal database.  We are closing all public issues, but as mentioned above, there are other ways to provide feedback. #please-close


Source Specific Custom Metadata

<
What would you like to be added:
Some of the applications in our environment are writing logs to file on persistent volume and information related to  Kubernetes environment is lost such namespace, pod name etc. For all these logs file, I would like to add metadata which includes this missing information which is known such as namespace or pod name etc.
This inclusion of metadata shall be specific to files only.
Why is this needed:
Logs read from the files can be filtered in Splunk base on the namespace, pod name etc.

@wrahmann I guess you need an addon with props.conf to add some field extractions for namespace & pod, and install this addon on Splunk forwarder or indexer for log file monitoring? If so, I'm afraid it's out of our scope. Anyways I can help to create a ticket and hopefully our PM can put some comments. Thank you.

@wrahmann I guess you need an addon with props.conf to add some field extractions for namespace & pod, and install this addon on Splunk forwarder or indexer for log file monitoring? If so, I'm afraid it's out of our scope. Anyways I can help to create a ticket and hopefully our PM can put some comments. Thank you.

@cheneysplunk
Thank you so much for your feedback. My understanding was all this data is being passed from fluentd.  If that is correct then it is better to add at the source?
Do create a ticket and we can follow from there.

@wrahmann , created following ticket and assigned to our PM. Feel free to add more comments there.
https://jira.splunk.com/browse/ADDON-30794
BTW, fluentd input will be available on UF soon. Maybe we can have a try as well.
To be clear, file monitoring, fluentd input & k8s connector are 3 different GDI solutions. We need to enable fields for search separately.  Saying that this feature request will not be a part of this github repo, but another product in SplunkBase.

@wrahmann
To enrich with k8s metadata info, the record need to have docker.container_id, kubernetes.namespace_name, kubernetes.pod_name, kubernetes.container_name, to query k8s api server.
https://github.com/fabric8io/fluent-plugin-kubernetes_metadata_filter

@cheneysplunk please keep in mind that non-Splunk employees do not have access to the internal Splunk jira so therefore cannot add comments!

@wrahmann , created following ticket and assigned to our PM. Feel free to add more comments there.
https://jira.splunk.com/browse/ADDON-30794
BTW, fluentd input will be available on UF soon. Maybe we can have a try as well.
To be clear, file monitoring, fluentd input & k8s connector are 3 different GDI solutions. We need to enable fields for search separately. Saying that this feature request will not be a part of this github repo, but another product in SplunkBase.

@cheneysplunk ,
We tried to add our comments but had no access. Please update us if there is feedback available on this JIRA ticket at your end.


Configure with no-asm still generates crypto/uplink-x86_64.s

When I configure with perl Configure no-asm VC-WIN64A an assembly file is still produced: crypto/uplink-x86_64.s. I think it should use a C implementation instead?

Ok, fair enough. Thanks.


Generate translations from .liquid files

Can you generate .po files by inspecting the .liquid files in Views?
The pattern would be like this:
{{ "string to be localized" | t }}

I don't want to parse liquid files myself and Fluid library doesn't expose filter names right now (https://github.com/sebastienros/fluid/pull/96). But I will try to generate .po files with a custom build of the Fluid library.


Implement Module Loading via Webpack Module Federation

Webpack Module Federation was designed to support micro frontends.
Benefits:
Feature apps can load libraries and share them with others that therefore don't need to load those libraries. With the current externals solution only one single version of a library is supported to be shared and needs to be provided by the integrator as an external. Module Webpack Federation also supports version matching in identifying if a library can be shared.

released with v2.9.0


Automated Package Upgrade

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


github_scraper.py completed, commented and Linted

Description
Script to fetch Girhub User Details.
Fixes #10
Type of change
Choosing one or more options from the following as per the nature of your Pull request.

NOTE: These boxes can be checked using [X]

[ ] Bug fix (non-breaking change which fixes an issue)

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

[ ] Documentation Update

Checklist:
Please tick all the boxes that are fulfilled by your Pull Request.

[x] I have named my files and folder, according to this project's guidelines.
[x] My code follows the style guidelines of this project.
[x] My Pull Request has a descriptive title. (not a vague title like Update index.md)
[x] I have commented on my code, particularly in hard-to-understand areas.
[x] I have created a helpful and easy to understand README.md, according to the given README_TEMPLATE.
[x] I have included a requirements.txt file (if external libraries are required.)
[x] My changes do not produce any warnings.
[ ] I have added a working sample/screenshot of the script.

@anandhakrishnanaji  remove the old files from commit

@AdityaJ7 fixed

@all-contributors please add @anandhakrishnanaji  for code


BlockFromToEvent-style event

Bukkit has a BlockFromToEvent that is called when water & lava try to mix together to form stone/cobblestone/obsidian.
This event, when cancelled:

does not cause any block changes
does not send any effects (sounds, particles)

This is somewhat doable with NotifyNeighborBlockEvent, but not all cases are handled. To fully do what a single event does in Bukkit someone would need to subscribe to NotifyNeighborBlockEvent, a ScheduledBlockUpdate event, and possibly more.

Isn't this the same as https://jd.spongepowered.org/3.0.0/org/spongepowered/api/event/block/ChangeBlockEvent.Modify.html ?

ChangeBlockEvent.Pre + NamedCause.LIQUID_FLOW should do this

I believe this can be handled with other events and the improvements of cause and contexts. If the dragon egg needs more special handling, a different issue can be opened with more specific features as well due to its unique behavior.


Use correct import to fix status updates

What
Describe what the change is solving
Fix errors.As() casting with *ngrok.Error with different versions of ngrok-go-api imported :/
How
Describe the solution
Use correct ngrok-go-api/v6 in base controller
Breaking Changes
Are there any breaking changes in this PR?
No.

#473  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @hjkatz and the rest of your teammates on  Graphite

Merge activity

Oct 29, 3:16 PM EDT: A user merged this pull request with Graphite.


Scaffold a new controller using kubebuilder

Description
Changes proposed in this pull request:

Scaffold a new controller using kubebuilder
Checklist

Related issue(s)

https://github.com/kyma-project/eventing-manager/issues/4

/test all

/test all


Doctrine\ORM\EntityManager is Deprecated

Per DoctrineORMModule "An alias has been set to reference Doctrine\ORM\EntityManager to help with BC but it is deprecated and will be removed in the future. The new service name is doctrine.entitymanager.orm_default."
This project currently uses the old reference.

Thx, fixed in #92


Extend TypeDescription codegen with referenced type inclusion, disable option, raw sources

Part of ros2/ros2#1159
Bundled with (must be merged together):

https://github.com/ros2/rosidl_typesupport/pull/141
https://github.com/ros2/rosidl_typesupport_fastrtps/pull/101
https://github.com/ros2/rmw_fastrtps/pull/680
https://github.com/ros2/rmw_connextdds/pull/113
https://github.com/ros2/rmw_cyclonedds/pull/448
https://github.com/ros2/rcl/pull/1053

Replaces (or extends) ros2/rosidl#727. Key differences

type_support_t->get_type_hash_func rather than bare value
get_type_description and get_type_sources take a typesupport struct argument (for use by dynamic types)
Type descriptions and sources include referenced types, rather than baking in full recursive dependencies per-interface
Expected hashes of referenced types are included in codegen to optionally error-check with at runtime

Key features:

Changes  TYPE_HASH_TUPLES to more accurate TYPE_DESCRIPTION_TUPLES in cmake
Adds new C interface  functions get_type_description, get_individual_type_description_source,  and get_type_description_sources
Implements above, generating code for type descriptions and raw interface definition sources, embedded in the binaries
Optionally disables embedding that information in the generated code by the CMake flag ROSIDL_GENERATOR_C_DISABLE_TYPE_DESCRIPTION_CODEGEN
Refactors rosidl_generator_type_description to output a new structure of type_description_msg plus a flat list of all referenced  types and their hashes at the time of generation. These hashes are used at runtime (in Debug builds) to detect  ABI breaks when constructing type descriptions the first time

Windows also needs to open(encoding='utf-8') explicitly:

Windows


Allow passing a custom function via -f / --custom_function

Hey there, I'm currently looking into some string extraction, found this tool (Thanks!! :-)), but I do have custom localisation functions. So this is mainly based on #14. I rebased it, fixed some merge issues and added tests for both the new and the genstrings extractor.
I also changed the short-option as "-c" was already taken by now. Given "-s" is already used as well (the genstrings option), I don't really have an opinion and just went with "-f" for function :-)
The tests didn't build for me. (I used the framework-scheme and ran the tests). If those work for you, I can just remove the commit working around that issue.
Let me know what you think!

Hey mate, just shortly want to say sorry, been busy these days and couldn't have a look. I hope to be able to do so until next week and give feedback / merge. Bear with me ...

Hey @Dschee @diederich, have you have planned on merging this PR? I think that it's a great feature 👍

Thanks everybody for the patience. I could finally invest some time and merge this (via rebases) and release this feature with version 3.8.0. Thanks for all your help!

🚀 🙏🏽