lein-nvd always uses the latest version of nvd-clojure

We've been on an older version of lein-nvd for awhile now and last weeks release of 1.1.0 suddenly broke our existing builds which was surprising. I did some digging and it looks like no matter what version of the 'lein-nvd' plugin you use, it grabs the latest version of 'nvd-clojure' which is what controls the 'dependency-check' version. This is easy to reproduce:
[Nicks-MacBook-Pro:20:46:39 ] git$ lein new nvd-test
Generating a project called nvd-test based on the 'default' template.
The default template is intended for library projects, not applications.
To see other templates (app, plugin, etc), try `lein help new`.
[Nicks-MacBook-Pro:20:46:46 ] git$ cd nvd-test/
[Nicks-MacBook-Pro:20:46:51 ] nvd-test$ vim project.clj
[Nicks-MacBook-Pro:20:47:25 ] nvd-test$ cat project.clj
(defproject nvd-test "0.1.0-SNAPSHOT"
  :description "FIXME: write description"
  :url "http://example.com/FIXME"
  :license {:name "EPL-2.0 OR GPL-2.0-or-later WITH Classpath-exception-2.0"
            :url "https://www.eclipse.org/legal/epl-2.0/"}
  :dependencies [[org.clojure/clojure "1.9.0"]]
  :plugins [[lein-nvd "0.5.2"]]
  :repl-options {:init-ns nvd-test.core})
[Nicks-MacBook-Pro:20:47:46 ] nvd-test$ lein nvd update
Retrieving lein-nvd/lein-nvd/0.5.2/lein-nvd-0.5.2.pom from clojars
Retrieving lein-nvd/lein-nvd/0.5.2/lein-nvd-0.5.2.jar from clojars
Retrieving nvd-clojure/nvd-clojure/1.1.1/nvd-clojure-1.1.1.pom from clojars
Retrieving org/owasp/dependency-check-core/5.0.0/dependency-check-core-5.0.0.pom from central
Retrieving org/owasp/dependency-check-parent/5.0.0/dependency-check-parent-5.0.0.pom from central
Retrieving org/owasp/dependency-check-utils/5.0.0/dependency-check-utils-5.0.0.pom from central
Retrieving nvd-clojure/nvd-clojure/1.1.1/nvd-clojure-1.1.1.jar from clojars
Retrieving org/slf4j/slf4j-api/1.7.26/slf4j-api-1.7.26.jar from central
Retrieving org/owasp/dependency-check-core/5.0.0/dependency-check-core-5.0.0.jar from central
Retrieving org/owasp/dependency-check-utils/5.0.0/dependency-check-utils-5.0.0.jar from central
Retrieving joda-time/joda-time/2.9.9/joda-time-2.9.9.jar from central
Retrieving org/slf4j/jcl-over-slf4j/1.7.15/jcl-over-slf4j-1.7.15.jar from central
[2019-06-17 20:48:19.599] INFO Engine - Checking for updates
...

First I cleared my local .m2 repo and then ran the above. You can see that it first downloads lein-nvd 0.5.2 which is what is specified for the plugin, but then downloads nvd-clojure 1.1.1 and hence dependency-check 5.0.0. The behavior is the same if you use a more recent version like 1.0.0 which should use dependency-check 4.0.2:
[Nicks-MacBook-Pro:20:51:54 ] nvd-test$ cat project.clj
(defproject nvd-test "0.1.0-SNAPSHOT"
  :description "FIXME: write description"
  :url "http://example.com/FIXME"
  :license {:name "EPL-2.0 OR GPL-2.0-or-later WITH Classpath-exception-2.0"
            :url "https://www.eclipse.org/legal/epl-2.0/"}
  :dependencies [[org.clojure/clojure "1.9.0"]]
  :plugins [[lein-nvd "1.0.0"]]
  :repl-options {:init-ns nvd-test.core})
[Nicks-MacBook-Pro:20:52:00 ] nvd-test$ lein nvd update
Retrieving lein-nvd/lein-nvd/1.0.0/lein-nvd-1.0.0.pom from clojars
Retrieving lein-nvd/lein-nvd/1.0.0/lein-nvd-1.0.0.jar from clojars
Retrieving nvd-clojure/nvd-clojure/1.1.1/nvd-clojure-1.1.1.pom from clojars
Retrieving org/owasp/dependency-check-core/5.0.0/dependency-check-core-5.0.0.pom from central
Retrieving org/owasp/dependency-check-parent/5.0.0/dependency-check-parent-5.0.0.pom from central
Retrieving org/owasp/dependency-check-utils/5.0.0/dependency-check-utils-5.0.0.pom from central
Retrieving nvd-clojure/nvd-clojure/1.1.1/nvd-clojure-1.1.1.jar from clojars
Retrieving org/owasp/dependency-check-utils/5.0.0/dependency-check-utils-5.0.0.jar from central
Retrieving org/owasp/dependency-check-core/5.0.0/dependency-check-core-5.0.0.jar from central
...

I'm not really sure how lein gets the dependency on nvd-clojure since it isn't listed explicitly. I tested this behavior on both lein 2.8.3 and lein 2.9.1 (latest).

Oh I see the issue.
https://github.com/rm-hull/lein-nvd/blob/1.0.0/plugin/src/leiningen/nvd.clj#L32
It's adding the nvd-clojure dep dynamically there and using the "RELEASE" special version string to always grab the latest. So is this the intended behavior? If it is I'd say it's definitely worth documenting in the README as it's very counter intuitive.

Also, for what its worth, having the dependency on nvd-clojure set dynamically like that makes it pretty  hard to debug things. The nvd-clojure dep doesn't make it into the output of 'lein deps :plugin-tree' so its a bit hard to see where certain things are coming from. In my case, the new OSS Sonatype analyzer is throwing an exception during initialization due to an issue with the version of guava it is using.
Also, just so these comments don't sound overly negative/critical, thanks a ton for putting lein-nvd out there! It's been a great tool for us.

So is this the intended behavior?

Yes, this is intended behaviour, when I originally wrote this plugin, I heavily based it on cloverage (which I also worked on), but you are right, it should be documented behaviour, along the lines of https://github.com/cloverage/cloverage#lein

This is also biting me in the ass for the past week.

We downgraded the plugin to 1.0.0 and in our CI environment we run nvd like this:
NVD_VERSION=1.0.0 lein nvd check

Which pins the nvd-clojure version (and hence dependency-check version). In my head I've been pondering if this really needs to use leins 'eval-in-project' which is what causes the guava conflict between dependency-check and my project. Seems like it could evaluate outside of the project but still pass the project classpath to dependency check. That's probably worth a separate issue though.

Related: #10

Is this now fixed via #10 ?

Yes, it is. Closing


null checks for #3364 and fix some bugs

@Jim8y I removed the new warnings created by #3364 , but I found a bug, sortedPool in line 407 can be null because line 259

this should be your pr on master, please do it on master directly


Use Sample Programs as Language Dictionary

Why generate our own mapping when we have a collection of programming languages right there for the taking? Let's use the Sample Programs repo as the language dictionary. Obviously, there are drawbacks to this. For example, languages don't have their original names (e.g. C++ vs. C-Plus-Plus). That said, we don't have to worry about scale when all the languages are already labeled in the dataset.

Also, there may be a way to generate the proper names by extracting keywords like "plus" and replacing them with their symbolic representations.


File "/root/XssPy/XssPy.py", line 36 || How to Solve this error ?

──(root㉿kali)-[~/XssPy]
└─# python3 XssPy.py bing.com
File "/root/XssPy/XssPy.py", line 36
print color.BOLD + color.RED + """
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
SyntaxError: Missing parentheses in call to 'print'. Did you mean print(...)?
Q: I am getting this error Please give me the solution.

I am getting the same error. I just cloned and tried to run the first example test on website.com, and this happened. How do we fix?


fix(host,glance): qemuimg convert optimize, allow write out of order and increase coroutines

What this PR does / why we need it:

Does this PR need to be backport to the previous release branch?:
release/3.11

/lgtm


Make elasticmoveapp navigate to space by default

Checklist

[x] commits conform to the Commit message format
[ ] documentation updated

Squash commit message
Make elasticmoveapp navigate to space by default

If we navigate to a new space I would expect the artifactmap to be filled the the apps from the space we navigate to so apps there could be opened. Filling with new apps would have two more consequences,

we should add a flag to keep or not to keep current artifacts (like in elasticexplore)
adding apps to artifactmap will break the existing flow of scripts,

Right! I see two ways to go:
1. Move to space and add apps to artifactmap, but not by default (opposite of the default in browser-client).
2. Do not merge this pr.

I think it should navigate by default so that default matches the normal user flow.

I think it should navigate by default so that default matches the normal user flow.

Strong point. As long as it does not cause too many scripts to fail or pick another app than before.

I think it should navigate by default so that default matches the normal user flow.

Strong point. As long as it does not cause too many scripts to fail or pick another app than before.

If we add the apps from the space we move to (which we should) it'd cause scripts randomizing a selection from apps to also pick from these in actions subsequent to this one. So if navigating is default there need to be clear communication about this change (and bump minor on release of it).

Or maybe even go 1.0.0 😲

Yeah, it's a semi-breaking change. Not functionally, but the scenarios may become different. But we should probably do it anyway if it's a new default user flow in order to get away from legacy behavior as much as possible. That's my 2 cents at least.

Artifact map logic is implemented, so this is ready for a second round of review


Add character count to description block + tweak description for the content block

As a system admin user, I want to know the number of characters I entered in the description content section so I can easily see how many characters I already have typed in or need to remove.
As a system admin user, I want to know the maximum number of characters I can enter in the description content section so I don't try to save my engagement to learn it.

@djnunez-aot character count is 0 when first loading the engagement:


Check for errors when saving in the ResourceSaver example documentation

This also replaces a non-breaking space that was accidentally added in the EditorFeatureProfile documentation.
This closes #31393.

Thanks!

Cherry-picked for 3.2.2.


LMPC with optimization of the initial state

In this pull request, I added a class InitialStateLMPC that derives from LMPC. It includes the initial state as additional optimization variables, which may be bounded via the resetInitialStateBounds() function.
A separate test file demonstrates its usage.
The underlying idea is part of my ICRA-2021 paper.

Hi,
Thank you for the PR. :)
I will start checking the code itself but it seems that the tests are failing with a Core dumped.
I can not accept the PR until this is fixed.

I see you are using <Eigen/LU>. Be careful, some algorithms are non-MPL2 licensed.
To ensure you are not using non-MPL2 features, add EIGEN_MPL2_ONLY from CMake definitions.

@vsamy I am computing the inverse of a eigen-matrix here and that's why I added #include <Eigen/LU>.
I just added set(EIGEN_MPL2_ONLY 1) to the cmake, but it seems there are still problems...

You have modified the constraint/cost in a hard way. Someone who would want to use the vanilla LMPC would have to provide the X,Y,z,etc matrices that it does know about.
Since you have inherited the LMPC for yours, you could do the same for all constraints and costs to avoid the problem.


Fix invoker to survive reboots

we noticed that the invoker did not restart with automatically after a VM reboot. we do set the docker.restart.opts for each container so we should do for invoker as well.
when doing this, it's important that the invoker also recovers the numbers that are required for the calculation of the queue. we see that the loadbalancer is out of sync when the invoker restarts.

This work is completed and merged.  The various counts are now reset and this was tested at least once by @markusthoemmes in a deployed system.


Rancher UI gradual slowdown and performace loss as session time increases

Rancher Version: 1.1.0-dev1
Docker Version: 1.9.1
OS and where are the hosts located? (cloud, bare metal, etc): CoreOS, VMWare
Setup Details: (single node rancher vs. HA rancher, internal DB vs. external DB) Single
Environment Type: (Cattle/Kubernetes/Swarm/Mesos) Cattle
Steps to Reproduce:
Start a Rancher UI session to an Environment with a number of Hosts and Stacks.  Leave this running for several days (as in a Dashboard scenario).
Results:
The web browser memory used increases gradually, and the scripts slow down until the web browser (Firefox in this case) pops up 'slow script' warnings.  This would seem to indicate a memory leak in the UI scripts somehow.
Expected:
Performance to remain constant over time.
Obviously this is a hard one to track down and replicate; and most people are unlikely to leave a session running for this long.  However operation staff are likely to have a dashboard screen up and running on a constant basis; when the Rancher UI starts to include gauges for usage etc even more so.

+1 The UI is very difficult to use once i'm logged in for more than 10 minutes. Each page becomes sluggish and/or unresponsive.

I have this problem too.
Desktop OS: Mac OS X 10.11.6
Google Chrome: 54.0.2840.98 (Official Build) (64-bit)
OS: Mac OS X
JavaScript: V8 5.4.500.41
Flash: <IP_ADDRESS>
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6)
Rancher Server:
Image: rancher/server:v1.1.0
/version returns:
{
"major": "1",
"minor": "2+",
"gitVersion": "v1.2.0-rancher-1",
"gitCommit": "ed6532f975cff184196dbe214de8fa0198b415ef",
"gitTreeState": "clean"
}
If there are more than 30+ containers running for a single service the browser stop responding when going to inspect the service.
The longer the rancher UI is used the slower it becomes.

@jthrelfall777 rancher 1.1 is quite old. Can you try this out with rancher 1.2?

you'll also want to make sure all hosts are 'active' and not 'reconnecting' those impact performance negatively.

@aemneina ok no problem, I will look into this today.

is this still happening?

@will-chan Yea I've given up with the web UI, I just use the CLI now. At a 108 containers the UI is unusable.

@jthrelfall777 What version of Rancher are you using? There have been improvements and we are doing a new Rancher UI.

@deniseschannon This is still an issue. When leaving a UI browser tab open the memory and CPU usage gradually increases. For example after leaving the container details page open over night, the memory usage for that tab increased from initially 100MB to over 1GB of memory according to Chrome task manager.

Performance testing and metrics will have to be redone on 2.0

closing as this is s a 1.6. we are tracking 2.0 performance an scale separtely


ESP32-C3: Move linker scripts and source files to folder common to all boards

Summary
This PR intends to reduce the repetition of Linker-related files and driver initialization and configuration routines among boards based on ESP32-C3 by moving the generic ones to a common folder.
Impact
No relevant impact expected to neither existing boards on the repository, nor to custom boards.
Custom boards, in fact, may benefit from this change and avoid the aforementioned duplication of linker script files.
Testing
CI build pass.
Verification in Internal CI that each defconfig from affected chips boots fine.

Let's ignore the ci broken by https://github.com/apache/nuttx/pull/7832


Missing field in Zapier integration

Describe the bug
It seems that the field Data Order Total Amount is empty on Zapier integration.
To Reproduce
Steps to reproduce the behaviour:
This is the setup I have in Zapier:

This is a real message in our Discord channel:

Note that the amount is missing.
Also worth noting that if I use the "test" feature in Zappier setup I do get a message with an amount in the message:

Expected behavior
The amount field should be populated with correct value.
Additional context

I'm using Zapier app v1.0

@Betree can you have a look?

@josesimoes Thanks for reporting this issue, we indeed have a bug for this webhook event that should be fixed by https://github.com/opencollective/opencollective-api/pull/2826.

@Betree thanks!
Worth pointing out that the icon on the message is the one from Zappier and not the user avatar. Unlike what's showing on the test message. Probably related...

@josesimoes I'll look at that as well.
Feel free to re-open this issue if the problem is not solved on your end.

@Betree we got a contribution today and it looked too generous to be true, so I went and double check it. Seems that the decimal separator is missing. See below the output that we got at our endpoint.

@josesimoes Amounts are in cents (we do this to handle the imprecision of processors when dealing with float amounts). You can add a formatter on Zappier to handle this (just divide amount by 100).
We recognize that this is not ideal, which is why #2117 was started.


[UBS Tariffs Page. Add new service "Послуга"] Digits and special characters must be allowed in Найменування послуги and Name of the service fields of the "Додати послгу" pop-up window

Environment: Windows 10, Chroome Version 111.0.5563.65
Reproducible: always
Build found: 13.05.2023
Preconditions

The user should be authorized as Admin
Main UBS menu -> page 'Тарифи' should be opened
Click on the tariff card available from the list

Steps to reproduce

Click on "Add service"/"Додати послугу" button
Pay attention to the 'Name of the tariff' field
Pay attention to the 'Найменування послуги' field

Actual result
only letters are allowed
Expected result
Letters, digits and special characters are allowed. From minimum 1 to maximum 30 characters are allowed.
User story and test case links
User story #4429
Labels to be added
"Bug", Priority ("pri: "), Severity ("severity:"), Type ("UI, "Functional"), "API" (for back-end bugs).

Digits and special characters shouldn't be allowed to enter the 'Найменування послуги' and 'Name of the tariff' fields.
But it must be allowed, according to the link.


For curl to json conversion, the xml type data seems to be coming in key value pairs

For curl to JSON conversion, the XML-type data seems to be coming in key-value pairs. Instead, it should have come in a single-string format like other converters give.

By the way, great library. Impressive.

maybe we need to add a "raw_data": key so that you can distinguish
curl example.com --json '"string"'

and
curl example.com --json 'string'

which are both converted to "data": "string" since the latter is invalid JSON.

hi @verhovsky
can you please tell me how much time will it take to get these changes reflected in the npm package? When do you plan to release these changes?

@eknathyadav we published 4.9.0 to npm just now with the change.


Add Spanish to list of locales

Allow users to select Spanish in the language selector.

Depends on https://github.com/terraware/terraware-server/pull/1067


Added option to either display the field on lower case or as it was defined

Context:
We had a request to change one the modules behavior: vocab.
Vocab has a component, called bucket and within this component the name of the field that was selected is displayed. The thing is that one the fields contains a name, Fyler, thus it should not be lower cased.
Solution:
I added an option to let the field not be lower cased.

Hi, @bruth . I made this small change. I was hoping you could review and share your thoughts about this change.
Thanks!

A more general solution could be to provide a function in the config that takes the names as an argument and then call that in the component if defined.
{
  // ..

  fieldNameDisplay: function(names) {
    return {
      single: names.single.toLowerCase(),
      plural: names.plural.toLowerCase()
    }
  },
}

Thanks reviewing it! I agree with what you said and I think it's better.
I changed the code and I hope it's closer to what you said.
Now one can change the function to execute whatever they want with certain names.
Example:
fieldNameDisplay: function fieldNameDisplay(names) {
    if (names.single.toLowerCase() !== 'fyler diagnosis') {
        return {
          single: names.single.toLowerCase() || '',
          plural: names.plural.toLowerCase() || ''
        };
    }
    return names;
}


upgrade xorm to v1.1.1

as title.

Codecov Report

Merging #16339 (65d9a26) into main (fae07cb) will increase coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main   #16339      +/-   ##
==========================================
+ Coverage   45.43%   45.44%   +0.01%
==========================================
  Files         709      709
  Lines       83686    83686
==========================================
+ Hits        38022    38032      +10
+ Misses      39564    39556       -8
+ Partials     6100     6098       -2

Impacted Files
Coverage Δ

models/repo_list.go
77.82% <0.00%> (+0.77%)
:arrow_up:

modules/queue/workerpool.go
55.72% <0.00%> (+1.90%)
:arrow_up:

modules/util/timer.go
85.71% <0.00%> (+42.85%)
:arrow_up:

Continue to review full report at Codecov.

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


feat(op-node): add pre fetch receipts logic

The process of fetching receipts is notably time-consuming. This issue can escalate further when the L1 network is busy, leading to an even more protracted duration of this logic. To mitigate these time constraints, it is imperative for the sequencer to execute this logic preemptively and store it in a cache. This will help prevent any negative impact on the block generation process.

move to https://github.com/bnb-chain/opbnb/pull/57


Add smarty block around "back to shop" button

1. Why is this change necessary?
Not a huge deal probably, but currently the "back to shop" button is appended to the block frontend_index_logo_trusted_shops, which means if you wanted to hide it, you'd have to hide the whole block. By default, the block is empty, but it might have been appended or edited, so I just feel that it would be a good idea to add an extra block here.
2. What does this change do, exactly?
Wrap the code for the "back to shop" button in a block frontend_register_back_to_shop_button.
3. Describe each step to reproduce the issue or behaviour.
-/-
4. Please link to the relevant issues (if any).
-/-
5. Which documentation changes (if any) need to be made because of this PR?
-/-
6. Checklist

[x] I have written tests and verified that they fail without my change
[x] I have squashed any insignificant commits
[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.

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/SW-21337
Please use this issue to track the state of your pull request.

I rebased this PR since it seems to have gotten stale

Hi @hrombach, thank you for your help! Your change will be part of the upcoming 5.4.4 release! 🎉


[python] Strip needless wrapper-class docstrings

Issue and/or context: As tracked on issue #2407 / [sc-51048].
Note that the intended Python and R API changes are all agreed on and finalized as described in #2407.
Changes:
At present we have four layers:

User-facing Python like DataFrame
Wrappers in _tdb_handles.py
pybind11 as in apis/python/soma_dataframe.cc
libtiledbsoma as in libtiledbsoma/src/soma/soma_array.h

Throughout the new-shape project (#2407) I've been putting docstrings in the _tdb_handles.py layer which is silly because:

Users don't read them
It's double-keystroking on my part to write them (content is the same as in the user-facing layer)

Notes for Reviewer:
This PR is a work in progress. It is not ready for review.

This was included in my merge of #3236 into main (inadvertently).


TextField mask prop

Fixes #818. Adds mask prop to TextField.

Changes being made by @hbowden so closing this PR.


Proposal: Remove informers from SharedInformerFactory

SharedInformerFactory just only adds resource informers into itself, but can not remove. I think we could add RemoveResource() method into SharedInformerFactory interface for removing resource informer.
Please give me to more advice.
THX!

What is the use-case for removing one?

@deads2k In v2.0.0 version without SharedInformerFactory, we can control every separate informer. Since v3.0.0-beta0 version, SharedInformerFactory can simplify the informer operation   for developers, but the developers

@deads2k We just want to control every separate informer using SharedInformeFactory. Every informer can start and stop.

@deads2k We just want to control every separate informer using SharedInformeFactory. Every informer can start and stop.

We haven't found a use-case for a selective stop in kube, so I'm not very excited about plumbing one through without a clear use-case.


Fixed app banner can not be removed in the theme setting page

I only added one line bellow in the template file
<input type="hidden" name="remove_banner" value="0">

travis-ci unpassed, It's not because of the cause of my fix.

@jbrooksuk
Merge this pull-request please.


importError when running model_zoo

import torchsparse.backend
ImportError: /home/kelsiegao/anaconda3/envs/torch/lib/python3.7/site-packages/torchsparse/backend.cpython-37m-x86_64-linux-gnu.so: undefined symbol: ZN3c106detail14torchCheckFailEPKcS2_jS2
How to solve this problem?I want to download some pretrained models to test the code. However, the above error happens
python 3.7.11
pytorch 1.7.1

Could you please try re-installing TorchSparse with pip install -v git+https://github.com/mit-han-lab/torchsparse.git?

Could you please try re-installing TorchSparse with the following command?
pip install -v git+https://github.com/mit-han-lab/torchsparse.git

Please post the error log if there is any. Thanks!

I reinstall torchsparse as your command. However, it remains the same error as before like the following details
Failed to import tensorflow.
Traceback (most recent call last):
File "evaluate.py", line 19, in
from model_zoo import minkunet, spvcnn, spvnas_specialized
File "/home/kelsiegao/Downloads/spvnas/model_zoo.py", line 9, in
from core.models.semantic_kitti.minkunet import MinkUNet
File "/home/kelsiegao/Downloads/spvnas/core/models/semantic_kitti/init.py", line 1, in
from .minkunet import *
File "/home/kelsiegao/Downloads/spvnas/core/models/semantic_kitti/minkunet.py", line 3, in
import torchsparse.nn as spnn
File "/home/kelsiegao/anaconda3/envs/torch/lib/python3.7/site-packages/torchsparse/nn/init.py", line 1, in
from .modules import *
File "/home/kelsiegao/anaconda3/envs/torch/lib/python3.7/site-packages/torchsparse/nn/modules/init.py", line 3, in
from .conv import *
File "/home/kelsiegao/anaconda3/envs/torch/lib/python3.7/site-packages/torchsparse/nn/modules/conv.py", line 9, in
from torchsparse.nn import functional as F
File "/home/kelsiegao/anaconda3/envs/torch/lib/python3.7/site-packages/torchsparse/nn/functional/init.py", line 2, in
from .conv import *
File "/home/kelsiegao/anaconda3/envs/torch/lib/python3.7/site-packages/torchsparse/nn/functional/conv.py", line 7, in
import torchsparse.backend
ImportError: /home/kelsiegao/anaconda3/envs/torch/lib/python3.7/site-packages/torchsparse/backend.cpython-37m-x86_64-linux-gnu.so: undefined symbol: ZN3c106detail14torchCheckFailEPKcS2_jS2

Is there any error or warning from the installation? If so, could you please post them here? Also, you could try to upgrade your PyTorch to the latest version.


"Concești" and "Movileni" are listed in the drop-down menu

Description:
"Concești" and "Movileni" are the drop-down menu alongside its corresponding county and commune, according to the law
Precondition:
The website is up an running.

Step 1
Type "Concești" in the search bar.

Expected results
The location is listed in the drop-down menu as "Concești, Botoșani (Concești)".

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Type "Movileni" in the search bar.

Expected results
The location is listed in the drop-down menu as "Movileni, Botoșani (Concești)".

ATTENTION:
STEP1:
Request - "Concești, Botoșani (Concești)"
In dropbox, the request is displayed correctly. - "Concești, Botoșani (Concești)"
After you click on the text, what is displayed in the window this is different - "Concești, BOTOȘANI (Concești)"
STEP3:
Request - "Movileni, Botoșani (Concești)"
In dropbox, the request is displayed correctly. - "Movileni, Botoșani (Concești)"
After you click on the text, what is displayed in the window this is different - "Movileni, BOTOȘANI (Concești)"


Daru::Index#[] should only be used for index value and Index#at for position.

Daru::Index#[] behaves as follows:
index = Daru::Index.new([100, 200, 300])

# access with Range:
index[0..1] # => #<Daru::Index(2): {100, 200}>

# access with Integer:
index[1] # => 1

# What I assumed:
index.at(1) # => 200

From the behavior of index[0..1], I assumed that index[] takes position as argument and returns value of index.
In other words, Index#[] sometimes takes position as argument and at other times takes value.
Is there any special reason for this confusing (at least for me) behavior ?

I think @lokeshh can answer this best.

Daru::Index#[] method in Daru takes values or positions as it arguments and is supposed to give only positions as its output. In case the input is both a valid value and a valid position, argument is assumed to be a value.
The reason for this behavior is this. Daru::Vector#[] also accepts both index value or position as its argument and return a vector value with preference given to index value over position. So, when user specifies an argument to Daru::Vector#[] we simply pass that argument to Daru::Index#[] and it returns us a position and that position to find the corresponding vector value.
For example, Vector is stored as Index + Array. So, a vector {:a => 100, :b => 200, :c => 300} will be stored as a index [:a, :b, :c] and an array [100, 200, 300]. When user specifies the index value/position in Vector#[] we pass that on to Index#[] and it returns a position regardless if index value is passed or position and we then use that position to return the corresponding element from the array [100, 200, 300].
So, you can say to support both index value and position in Vector#[] we have allowed Index#[] to accept both a index value and position.

@v0dro @lokeshh  I got it. Thanks!
However, I still think those behaviours are confusing.
My suggestion is: #[] method take only index value, and if we wanna access by position, we use #at method.
How do you think about it?

If you're using integer index only why not use only #at?
However, I like this proposition. The #[] method can raise an error if the index value is not found, irrespective of the kind of object that the index value is.
@zverok @gnilrets WDYT? I think @zverok has talked about this before too if I remember correctly...

We've had several unexpected bugs arise (see the last group_by issue last week) due to #[] serving two purposes.  I strongly prefer using #at for position and #[] for index value.

Alright then. Marking this as an enhancement.

Shall we also do the same for Daru::Index#[]?

@lokeshh Yeah works for me. I think we should. Will remove confusion once and for all.

Maybe I should have propose earlier, but another solution is creating new method that only accepts index value.
In other words, we will have three methods at, of, and []:

at only accepts position
of only accepts index value
[] accepts both.

There might be more suitable name for of method...
@v0dro @gnilrets How do you think about this?

I think that [] should be predictable.  It currently isn't because if an index doesn't exist then it falls back to position and there is no predictable relationship between index and position.  I also think it should accept an index since that seems to be the default reference mechanism.

I also don't think we should go for of. [] and at should be sufficient.
I can't think of use cases where a method that accepts both index and position is being used when dedicated methods exist for that purpose. If such a need does arise we can simply build a wrapper over at and [] (not the current versions of these methods, of course).

@v0dro - If this hasn't been fixed, I'd like to fix this. :smile:

I want to take up this issue.

What should be the output for multiple keys like index[100,200] ? In case one of the index is valid and the other one is not what should be the output?

What should be the output for multiple keys like index[100,200] ? In case one of the index is valid and the other one is not what should be the output?

What regular Ruby's arrays return in this case?

Regular ruby arrays show a range of values between the comma separated indices, i.e. providing a range or comma separated values give the same output in arrays.

Well, I believe when first index is valid, then everything from this index to the end of Index should be returned.

Should it raise an error if the first index is invalid or should it return nil as in regular Ruby arrays?

Just nil

What should be the output for multiple keys like index[100,200] ? In case one of the index is valid and the other one is not what should be the output?

I think IndexError should be raised.
Reasons:

Daru::Index#[] raises error when given invalid argument.

index = Daru::Index.new([:a, :b, :c, :d])
index[:x] # => IndexError: Specified index :x does not exist

array[100, 200] and index[100, 200] has different meanings.

array[start, length] means array[start...(start+length)].
On the other hand, index[index1, index2] means Daru::Index.new([index[index1], index[index2]]).
Examples:
array = [:a, :b, :c, :d]
array[1, 3] # => [:b, :c, :d]

index = Daru::Index.new(array)
index[:b, :d] # => #<Daru::Index(2): {b, d}>

Thanks.
reference: https://ruby-doc.org/core-2.2.0/Array.html#method-i-5B-5D

Well I think we should return nil for indexes that don't exist and the positions for indexes that exist as that was discussed
index = Daru::Index.new([:a, :b, :c, :d])
index[:a, :b] # => [0, 1]
index[:a, :d] # => [0, nil]
index[:d, :e] # => nil

Also should we deprecate range options in Daru::Index#[] to avoid ambiguity? As it is already available in Daru::Index#at and makes more sense there.

Well I think we should return nil for indexes that don't exist (only support indexes not position)and the positions for indexes that exist as that was discussed

Why Daru::Index#[] should return nil ?
If IndexError is raised, users can notice that they specify wrong index.
However, if nil is returned, error will raised from other place.
I think this will complicate debug process.
If you have any advantages of returning nil, please tell me it.
Thanks.

If you have any advantages of returning nil, please tell me it.

Well, most of the time we a copying Ruby array's/hashes behavior. Just to be consistent. Returning nil instead of errors is OK for Array#[] and Hash#[] -- I believe, that's because when index is taken from variable, you can have data in one case, and just "no data" in another, and it is not an "error".

I believe, that's because when index is taken from variable, you can have data in one case, and just "no data" in another, and it is not an "error".

OK. I undestand the advantage, and agree with it.

So I am going by these definitions. Daru::Index#[] will return index object if positions are given as argument and return positions if argument is index values and return nil if no values are found. No error is raised. Some examples
index = Daru::Index.new([:a, :b, :c, :d])

index[0..3] # => #<Daru::Index(4): {a, b, c, d}>
index[:a..:c] # => [0, 1, 2]
index[0, 3] # => #<Daru::Index(2): {a, d}>
index[:a, :c] # => [0, 2]
index[0] # => :a
index[:a] # => 0
index[:g] # => nil
# index[:e..:f] # => nil

Daru::Index#pos returns positions corresponding to a valid index value. It only accepts valid index value as arguments. If an invalid index or position is given as argument it shows IndexError. Example
index.pos(:a) # => 0
index.pos(:a, :k) # => IndexError: k is not a valid index
index.pos(1) # => IndexError: 1 is not a valid index

Daru::Index#at returns indexes corresponding to valid positions. It only accepts valid positions as arguments and raises error for invalid positions. Example
index.at(0) # => :a
index.at(:a) # => ArgumentError: Unkown position type.
index.at(5) # => IndexError: 5 is not a valid position.

Can this be closed given the PR merged above?


Commands from mod buttons don't trigger custom commands.

Describe the bug

When clicking a moderation button, the command is not processed like a normal command from the chat box, instead custom commands made inside the client aren't triggered.
To reproduce

Add create a command, for this example, I'm gonna use /test => Test 123 {1+},
Add a mod button like, /test {user}
Click it on a message
observe that the command wasn't processed inside Chatterino, it was send to Twitch.

Chatterino version

Chatterino 2.1.7 (commit 175e41c58)

If this is intention behavior, it would be nice to see this as an added feature to make it work.


integrate google map in the footer section

This issue aims to add Google Maps integration to the footer section of our project. By integrating Google Maps, we can enhance user experience by displaying a map with relevant location information in the footer. This feature will enable users to quickly locate our business or organization and access helpful location-related details. The integration will involve implementing the necessary API calls and ensuring a seamless user interface. Let's work together to make our project even more engaging and user-friendly with Google Maps integration in the footer section.

Hey @khushi1711 , thanks for stepping up!
Yea, the idea sounds good. We have already added the navigation to preferred location through google map in the contact section. So, if we again include it in footer, I think it would be little messy.
Can u pls provide provide the draft footer layout which includes everything, u can  just design it and send the screenshot before implying it. We would then think whether the google map has to be integrated in the footer or not.....

Assign me this issue under GSSoC'23 label

Please assign this task to me under gssoc'23


Update conventions & reset Object API

This PR:

Closes #24
Closes #31
Removes the current object API code

So, here's where I think my personal confusion stems from. By default, these are the directions in three.js and also in pygfx:

+X is right
+Y is up
-Z is forward

However, when you have a random object, and you use it's lookAt function to make it face a target, it's rotation will be adjusted such that it's local positive Z axis will point to target. See the screenshot below. I've translated the cylinder a little, and then made the cylinder "look at" the origin using lookAt(0,0,0).

@Korijn Could this simply be a bug/inconsistency in ThreeJS?

I played with the editor too. Indeed, calling lookAt at an object turns it's local +Z axis toward the target. Doing the same with a camera turns it's -Z axis towards the target. --> Looks like the implementation of lookAt is different for camera's, which is an inconsistency. I wonder whether this has a historical thing that we can avoid by doing it right from the start, or whether there is another reason ...

@Korijn Could this simply be a bug/inconsistency in ThreeJS?

No, I think it's intentional! There are similar differences when I try the Unity editor locally.

--> Looks like the implementation of lookAt is different for camera's, which is an inconsistency. I wonder whether this has a historical thing that we can avoid by doing it right from the start, or whether there is another reason ...

Same for lights: https://github.com/mrdoob/three.js/blob/acb58df60448e75561c363f142f0df878705443d/src/core/Object3D.js#L284

I've updated the conventions document with your suggestions and included the Z-axis distinction for cameras and lights and other objects.

I think I've found the reasoning for three.js exception for cameras and lights, it is based on the glTF conventions.

https://github.com/mrdoob/three.js/pull/14935
https://registry.khronos.org/glTF/specs/2.0/glTF-2.0.html#coordinate-system-and-units
https://registry.khronos.org/glTF/specs/2.0/glTF-2.0.html#view-matrix
https://github.com/KhronosGroup/glTF/tree/main/extensions/2.0/Khronos/KHR_lights_punctual#adding-light-instances-to-nodes

In the above links you can find the glTF conventions, including the exceptions to the Z-axis for cameras and lights.
So I think perhaps one of three.js goals is to be compatible with glTF assets out of the box. I wonder if that means their positive X axis points left instead of right in accordance with the glTF convention...

I'm still don't fully understand why the view direction of cameras and lights is the backward direction for normal objects. But I think we can assume that the ppl from glTF have thought about this well. So let's adopt this and also mention glTF instead of pygfx (and link to it too).

glTF uses a right-handed coordinate system. glTF defines +Y as up, +Z as forward, and -X as right; the front of a glTF asset faces +Z.

This confused me, until I realized that if you rotate around these axiii, so that you view down the -Z axis, then +X is to the right again.

It also explains why the lookAt call in threejs just flips eye and target for cameras and lights.

@FirefoxMetzger would you mind taking over this PR? I think you are better at documenting the coordinate frames and conventions than I am, and also I fractured a rib yesterday so I won't be using my laptop a whole lot anytime soon (typing this on my phone).

@Korijn Sure. I'll do a review and finish it up during the next sprint 👍

I fractured a rib yesterday

Ouch. Hope that things will heal back together smoothly.

I've split up this PR so we can merge #47 more quickly, and so that @FirefoxMetzger can take over this PR which is now isolated to just the changes to CONVENTIONS.md.

If you both agree with the updates to the definition of spherical coordinates then I think we can merge. Looks good from my side otherwise :)

I'm good! Since I opened the PR, it requires you or Almar's approval.

Nice work! This exercise will prove very much worthwhile.


[Ambient mode]Application failedhealthness checks(liveness, readiness, startup), no NetworkPolicy configured

Is this the right place to submit this?

[X] This is not a security vulnerability or a crashing bug
[X] This is not a question about how to use Istio

Bug Description
Hi team,
I am currently rolling out Ambient mesh to our cluster, hit very weird issues. When I add label to the deployment: istio.io/dataplane-mode: ambient and roll it out. The new pods will fail every configured probes. I've read this article and some related issue, doesn't seem to be a match as we don't have a networkpolicy configured in that namespace.
Workload:
apiVersion: apps/v1
kind: Deployment
metadata:
  labels:
    app: vonline
    app.kubernetes.io/instance: vonline
    appInst: vonline
    cost_center: vonline
    tags.datadoghq.com/service: vonline
  name: vonline
  namespace: default
spec:
  progressDeadlineSeconds: 600
  replicas: 0
  revisionHistoryLimit: 3
  selector:
    matchLabels:
      appInst: vonline
  strategy:
    rollingUpdate:
      maxSurge: 5%
      maxUnavailable: 5%
    type: RollingUpdate
  template:
    metadata:
      creationTimestamp: null
      labels:
        admission.datadoghq.com/enabled: "true"
        app: vonline
        appInst: vonline
        cost_center: vonline
        istio.io/dataplane-mode: ambient
        tags.datadoghq.com/service: vonline
    spec:
      containers:
      - env:
        - name: CLUSTER
          value: staging2
        - name: GOMAXPROCS
          value: "1"
        - name: JWT_ENABLED
          value: "true"
        image: xxx
        imagePullPolicy: IfNotPresent
        lifecycle:
          preStop:
            exec:
              command:
              - /bin/sleep
              - "25"
        livenessProbe:
          failureThreshold: 3
          httpGet:
            path: /ping
            port: 5000
            scheme: HTTP
          initialDelaySeconds: 1
          periodSeconds: 30
          successThreshold: 1
          timeoutSeconds: 3
        name: vonline
        ports:
        - containerPort: 5000
          protocol: TCP
        readinessProbe:
          failureThreshold: 3
          httpGet:
            path: /ready
            port: 5000
            scheme: HTTP
          initialDelaySeconds: 1
          periodSeconds: 60
          successThreshold: 1
          timeoutSeconds: 30
        resources:
          requests:
            cpu: 100m
            memory: 200Mi
        securityContext:
          allowPrivilegeEscalation: false
          capabilities:
            drop:
            - ALL
          privileged: false
          readOnlyRootFilesystem: true
        terminationMessagePath: /dev/termination-log
        terminationMessagePolicy: File
        volumeMounts:
        - mountPath: /app/config
          name: config
        - mountPath: /var/run/secrets/cross_server_tokens
          name: cross-server-tokens
      dnsPolicy: ClusterFirst
      restartPolicy: Always
      schedulerName: default-scheduler
      securityContext:
        fsGroup: 1000
        runAsGroup: 1000
        runAsNonRoot: true
        runAsUser: 1000
      serviceAccount: vonline
      serviceAccountName: vonline
      terminationGracePeriodSeconds: 30
      topologySpreadConstraints:
      - labelSelector:
          matchLabels:
            appInst: vonline
        maxSkew: 1
        topologyKey: topology.kubernetes.io/zone
        whenUnsatisfiable: DoNotSchedule
      volumes:
      - configMap:
          defaultMode: 420
          name: vonline-config-4b445d7
        name: config
      - name: cross-server-tokens
        projected:
          defaultMode: 420
          sources:
          - serviceAccountToken:
              audience: verkada
              expirationSeconds: 7200
              path: verkada
          - serviceAccountToken:
              audience: vonline
              expirationSeconds: 7200
              path: vonline
          - serviceAccountToken:
              audience: remotesh
              expirationSeconds: 7200
              path: remotesh
          - serviceAccountToken:
              audience: globaldevice
              expirationSeconds: 7200
              path: globaldevice

ztunnel logs:
istio-cni-node logs:
contexts:
- context:
    cluster: local
    user: istio-cni
  name: istio-cni-context
current-context: istio-cni-context
kind: Config
preferences: {}
users:
- name: istio-cni
  user:
    token: REDACTED

2024-09-12T04:53:04.695695Z	info	install	install/install.go:72	missing (or invalid) configuration detected, (re)writing CNI config file at
2024-09-12T04:53:04.695718Z	info	install	install/cniconfig.go:105	Using CNI config template from CNI_NETWORK_CONFIG environment variable.
2024-09-12T04:53:04.695737Z	info	install	install/cniconfig.go:124	CNI config: {
  "cniVersion": "0.3.1",
  "name": "istio-cni",
  "type": "istio-cni",
  "log_level": "debug",
  "log_uds_address": "/var/run/istio-cni/log.sock",
  "ambient_enabled": true,
  "cni_event_address": "/var/run/istio-cni/pluginevent.sock",
  "kubernetes": {
      "kubeconfig": "/etc/cni/net.d/ZZZ-istio-cni-kubeconfig",
      "cni_bin_dir": "/opt/cni/bin",
      "exclude_namespaces": [ "kube-system" ]
  }
}
2024-09-12T04:53:04.695948Z	info	install	install/cniconfig.go:217	CNI config file /host/etc/cni/net.d/10-aws.conflist exists. Proceeding.
2024-09-12T04:53:04.696331Z	info	install	install/cniconfig.go:166	Created CNI config /host/etc/cni/net.d/10-aws.conflist
2024-09-12T04:53:04.696365Z	info	install	install/install.go:97	Installation succeed, start watching for re-installation.
2024-09-12T04:53:04.798242Z	info	cni-agent	nodeagent/ztunnelserver.go:196	received hello from ztunnel.
The pod has a securitygrouppolicy binded, after I delete that securitygrouppolicy, all the probes just pass through and it's running fine...
https://github.com/istio/istio/discussions/51588#discussioncomment-10355431
this comment seems related, but I didn't find an existing post regarding this.

Lots of discussion in slack https://istio.slack.com/archives/C041EQL1XMY/p1726258013262219?thread_ts=1726157670.382619&cid=C041EQL1XMY. root cause is POD_SECURITY_GROUP_ENFORCING_MODE: strict

See also https://github.com/aws/amazon-vpc-cni-k8s/issues/2797 which I think is the issue we are impacted by here.

(for anyone who finds this) more details for what exact EKS config is required to hit this added here: https://github.com/istio/istio.io/pull/15785
It is also worth noting that using AWS SecurityGroups to enforce pod traffic is functionally nearly identical to using NetworkPolicy to do so, and NetworkPolicy does not have this issue.


Run files of Vanilla BERT checkpoints do not match test folds in data/robust

First of all, thanks a lot for your interesting work on CEDR and for the code in this repository.
I downloaded the Vanilla BERT and CEDR-KNRM checkpoints from #18 and checked the query ids in the .run files contained in the downloaded archive. While the sets of query ids in cedrknrm-robust-f[1-5].run match those in data/robust/f[1-5].test.run, the sets of query ids in vbert-robust-f[1-5].run do not match those in data/robust/f[1-5].test.run (e.g. the set of query ids in vbert-robust-f1.run is different from the set of query ids in data/robust/f1.test.run, and also cedrknrm-robust-f1.run).
Why are the folds for Vanilla BERT and CEDR-KNRM different? On which folds have the Vanilla BERT checkpoints been trained/validated? Given that the test folds of the Vanilla BERT and CEDR-KNRM checkpoints are different I assume that the provided Vanilla BERT checkpoints have not been used as initial weights for obtaining the provided CEDR-KNRM checkpoints. Is this assumption correct? If yes, which Vanilla BERT checkpoints have been used to initialize CEDR-KNRM training? Do you mind sharing these checkpoints too?
I'm currently investigate issues reproducing the results published in the paper. More on that in a separate ticket ...

To be more precise regarding

e.g. the set of query ids in vbert-robust-f1.run is different from the set of query ids in data/robust/f1.test.run, and also cedrknrm-robust-f1.run

the number of common query ids in vbert-robust-f1.run and data/robust/f{x}.test.run for x = 1..5 is:

x = 1: 7
x = 2: 13
x = 3: 12
x = 4: 7
x = 5: 11

Hi Marin,
Thanks for pointing out this inconsistency! I suspect that it can be explained by a mismatch between the original code used for running the experiments (which reflect the vbert-robust-f1.run files), and the simplified example we released here. Specifically, I'm thinking it may have been a problem with the code that exported the data/robust/f{x}.test.run files from the original source. But I'll need to spend some time digging into exactly what happened.

sean


The Dataset panel prematurely shows an ERROR message while it's still loading large-ish files

Fixed by #290


How to call wallet_store_wallet_wasm to save wallet_wasm?

This method is used to store the byte array of the wasm file. But don't know how to call it. I tried two ways, both failed:

The UI interface first gets the byte array of the wasm file, and then calls the store_wasm_file method to store it, but querying the wasm byte array will cause the browser to out of memory.
 But Linux will report an error when executing the command: Argument list too long

I found a solution from motoko-cdn: format the buffer of the file and convert it into an array of u8.


Error in vismodel(sppspec_sub, visual = "apis") : wavelength range in spectra and visual system data do not match

I'm attempting to visualize reflectance specta with bee vision using the vismodel function, but get the following error:
Error in vismodel(sppspec_sub, visual = "apis") : wavelength range in spectra and visual system data do not match
I see in the package documentation that functions only work over 300-700 wavelength range for visual, and so subset my spectra to that range but still get the above error. Any suggestions for how to solve this?

Hi @stephen1694, thanks for reaching out!
I cannot reproduce the error on my end.
library(pavo)
#> Welcome to pavo 2! Take a look at the latest features (and update your bibliography) in our recent publication: Maia R., Gruson H., Endler J. A., White T. E. (2019) pavo 2: new tools for the spectral and spatial analysis of colour in R. Methods in Ecology and Evolution, 10, 1097-1107.

data(flowers)
vis.bee <- vismodel(flowers, visual = "apis")

head(vis.bee)
#>                                 s          m         l lum
#> Goodenia_heterophylla 0.104029618 0.47542207 0.4205483  NA
#> Goodenia_geniculata   0.027006318 0.27708151 0.6959122  NA
#> Goodenia_gracilis     0.002372168 0.03041115 0.9672167  NA
#> Xyris_operculata      0.031573663 0.41665174 0.5517746  NA
#> Eucalyptus_sp         0.067245812 0.39203714 0.5407170  NA
#> Faradaya_splendida    0.045571892 0.24722183 0.7072063  NA

Created on 2022-06-22 by the reprex package (v<IP_ADDRESS>00)
There must be something different with your data: do you have one value per nanometer? If not, you will need to update your data to be this way. The simplest option to do so is to run:
sppspec_sub <- as.rspec(sppspec_sub)

Otherwise, could you please share your dataset so we can investigate? You can email us at<EMAIL_ADDRESS>/<EMAIL_ADDRESS>

Thanks for your response! I'm not sure why this happened before, but I restarted Rstudio to try what you suggested and my .R file ran fine this time without error, so I guess there isn't an issue.


Implement logarithm function

Division, SquareRoot and Logarithm are more difficult than addition and multiplication because they can result in infinite digits. The simple algorithm for long division gives a simple way to find the answer up to x digits though. Squareroot can also be found exactly up to x digits by using the bisection method (works particularly well for binary floats). But logarithm is slightly harder to get the precise answer up to ``x` digits because there isn't an exact exponential function either. This means that in order to get the correct rounding, more sophisticated error bounding is needed.
Typically this is done with Newton-Raphson iteration and precomputed tables, and continuing until the error is between floating-point values. I would like to keep the code simpler than anything more complex than what I can understand directly from reading the code though. One of the goals of this project is to have a readable, correct floating-point implementation; using more complex algorithms runs counter to that goal.
I'm not sure how to proceed. I will probably just work on other things until I get an idea (it worked for sqrt).

I have come to the realization that a precise logarithm is not required by the specification. Instead only a logarithm to integers is needed, which is not difficult to do.
This should allow this project to move forward again. I may take it up as my main project for the remainder of the semester.


transparency issues

white where it should be transparent
https://epik.isthebestwaifu.club/kMSNH1w0

This kind of problem is caused by the fact that Windows itself doesn't allow edge rounding the way we use it, so we use a library that does that, on some computers it may present this kind of error, maybe in the future I will try to change the rounding method to see if it is possible to get a better look.


See which resolve caused package conflicts

Inspired by #971
It will be nice to have something similar for when there is package conflict.
e.g. when a resolve errors with:
The context failed to resolve:
The following package conflicts occurred: (python-2 <--!--> python-3)

and you want to find out:

which packages/dependency chain requested python-2, and
which packages/dependency chain requested python-3

Rather than digging through a re-resolve with rez env --verbose, include the resolve/request information in the initial error message like:
The context failed to resolve:
The following package conflicts occurred: (python-2 <--!--> python-3)
python-2: pymel <-- maya-2020.2 <-- proj_env_foobar-0.2
python-3: houdini-18.5

Considered closed by #1083

Yeah I agree this would be useful actually. It's really just displaying the
graph in cli format, where each line is a chain in the resolve DAG
terminating at one of the package requests involved in the conflict.
On Fri, Nov 6, 2020 at 9:17 AM Joe Yu @.***> wrote:

Inspired by #971 https://github.com/nerdvegas/rez/pull/971
It will be nice to have something similar for when there is package
conflict.
e.g. when a resolve errors with:
The context failed to resolve:
The following package conflicts occurred: (python-2 <--!--> python-3)
and you want to find out:

which packages/dependency chain requested python-2, and
which packages/dependency chain requested python-3

Rather than digging through a re-resolve with rez env --verbose, include
the resolve/request information in the initial error message like:
The context failed to resolve:
The following package conflicts occurred: (python-2 <--!--> python-3)
python-2: pymel <-- maya-2020.2 <-- proj_env_foobar-0.2
python-3: houdini-18.5
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/nerdvegas/rez/issues/972, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMOUSUR6HBJHLIPB3LGTNLSOMQAVANCNFSM4TL527LQ
.

Adding context from the time I was doing #1083 ：）
Yes, understanding the conflict/cycle by reading the path from the failure point toward init requests like the format above could be easier.
But the path growing from failure point may split if it's related to multiple requests, which may not easy to represent in CLI ?
This was the main reason of #1083 describing the failure starting from init requests.

Yeah sorry David I've been a bit distracted this morning, and yes your PR
addresses this already. What I was actually thinking about is a similar CLI
representation of the graph, for any nominated package. Ie, the CLi
equivalent of rez-context -g --pp {pkg} - so you can see how a given
package version was selected, even in a successful resolve.
On Wed, Jun 2, 2021 at 8:08 AM David Lai @.***> wrote:

Adding context from the time I was doing #1083
https://github.com/nerdvegas/rez/pull/1083 ：）
Yes, understanding the conflict/cycle by reading the path from the failure
point toward init requests like the format above could be easier.
But the path growing from failure point may split if it's related to
multiple requests, which may not easy to represent in CLI ?
This was the main reason of #1083
https://github.com/nerdvegas/rez/pull/1083 describing the failure
starting from init requests.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/nerdvegas/rez/issues/972#issuecomment-852493100, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMOUSXWRPA7YWQHEQDWDRDTQVK5DANCNFSM4TL527LQ
.


[AST] Properly adjust substitution type for inherited conformances.

When we substitute into an inherited conformance, make sure that we
follow the superclass chain from the new conforming type up to the
matching superclass before doing the substitution.
Fixes rdar://problem/35632543. Also add a test for the related but already-fixed rdar://problem/35480728.

@swift-ci please smoke test and merge


Vulnerability roundup 108: connect-1.105: 1 advisory [9.8]

search, files

[ ] CVE-2021-40719 CVSSv3=9.8 (nixos-unstable)

CVE details
CVE-2021-40719
Adobe Connect version 11.2.3 (and earlier) is affected by a Deserialization of Untrusted Data vulnerability to achieve arbitrary method invocation when AMF messages are deserialized on an Adobe Connect server. An attacker can leverage this to execute remote code execution on the server.

Scanned versions: nixos-unstable: 942eb9a335b.
Cc @jcumming

False positive, our connect package isn't adobe connect.


Add conda recipe

This adds a templated conda recipe that can be used to build streamparse conda packages very easily.  You just run conda build . in the directory where you have it checked out after you make a new release, and this will take care of giving the package the right version number and all that.
One advantage of using conda for packaging streamparse is that there is already a leiningen conda recipe and package (available in my binstar channel), and that is listed as a dependency for streamparse.  That means if you do conda install streamparse, you get something that works right away.

For reference, the leiningen recipe that I built my leiningen package with is available in the conda/conda-recipes repo.

I've also put together a Storm recipe, so we might want that to be a prereq for this.


Fixes for Frigg CI

The 'Frigg CI' workflow is currently failing, this PR is supposed to fix the errors

Hey @seanspeaks or @MichaelRyanWebber, I'm trying to make the CI pass. Do you have any idea why this test is failing?
FAIL module-plugin/test/auther.test.js
  ● HubSpot Module Tests › Test credential retrieval and module instantiation › retrieve by entity id

    TypeError: Cannot read properties of null (reading 'credential')

      113 |                 params.credentialId
      114 |             );
    > 115 |         }
          |          ^
      116 |         let credential = {};
      117 |         let entity = {};
      118 |         if (instance.credential) {

@igorschechtel I wonder if perhaps the in-memory mongo is not working in CI. It's passing for me when I run it (thanks to your fixes to the imports), is that the same for you?

@MichaelRyanWebber yes, this test is also passing when I run it locally.
It seems to me that the issue is that instance is null. So when it tries to access instance.credential we get the error:
TypeError: Cannot read properties of null (reading 'credential')

If this is true I think the origin for the error is line 105:
const instance = new this(params);

Not sure why this would return null though... maybe an error in the constructor? The fact that it passes locally but not in the workflow makes it even weirder.


December, 2016 App SDK documentation work for Dec. 12 2016 release of App SDK bits

:warning: Validation status: warnings

File
Status
Preview URL
Details

Skype/UCWA/startOnlineMeeting_ref.md
:warning:Warning

Details

Skype/UCWA/startOnlineMeeting_ref.md

Line 77: [Warning] Invalid file link:(~/UCWA/OnlineMeetingInvitationResource_ref.md).

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Move away from Aruba?

The build on master is currently broken - I think this is because the Aruba / Cucumber @disable-bundler hint has been broken in recent releases.
I've used Aruba for a while now, but would like to suggest a simpler alternative. I think Aruba grown overly complex (supporting Cucumber, RSpec, Minitest etc) and buggy. They've also deprecated the functionality to run tests in a directory outside your project structure (like /tmp/x) which isn't helpful when one wants to write tests with commands like git init and rails new etc.
Summary of changes:

Remove Aruba / Cucumber / Turnip etc
Rewrite specs in plain RSpec with JetBlack (new gem I've been working on!)
Removes rails & it's dependencies as a development dependencies of the gem
Bumps Travis from Ruby 2.2 (now EOL) to 2.3, 2.4 and 2.5

FWIW, @disable-bundler is only broken in the 1.0 pre-releases of Aruba, and should work fine in the 0.14.5 release you're using. Something else must be causing those build failures.
Handling of absolute paths is a bit of a mess at the moment. The current plan is to continue to allow it, but give a warning that can be turned of.

@mvz thanks for the clarification. I did try a couple of different version but still saw bundler related errors.


[baremetal] Add SCA countermeasures to AES

Description
Add SCA countermeasures to AES implementation. Add total of 5 dummy calculation rounds to AES encryption/decryption.

1 additional dummy round calculated with first and last round (order randomised).
3 additional dummy AES rounds calculated with middle rounds (order randomized)

Impact on code-size:

GCC
ARMC5
ARMC6

libmbedtls.a before
15069
16511
17065

libmbedtls.a after
15069
16511
17065

libmbedcrypto.a before
17999
18427
20599

libmbedcrypto.a after
17843
18129
20477

libmbedx509.a before
4729
4868
5159

libmbedx509.a after
4729
4868
5159

gain in bytes TLS
==
==
==

gain in bytes Crypto
156
298
122

gain in bytes X.509
==
==
==

gain Total
156
298
122

Impact on performance (countermeasures activated):

before
after

MD4
3867 KB/s
3846 KB/s

MD5
3134 KB/s
2873 KB/s

RIPEMD160
730 KB/s
725 KB/s

SHA-1
1262 KB/s
1259 KB/s

SHA-256
621 KB/s
619 KB/s

SHA-512
383 KB/s
384 KB/s

ARC4
2783 KB/s
2781 KB/s

3DES
140 KB/s
137 KB/s

DES
414 KB/s
412 KB/s

3DES-CMAC
128 KB/s
126 KB/s

AES-CBC-128
536 KB/s
258 KB/s

AES-CBC-192
472 KB/s
234 KB/s

AES-CBC-256
422 KB/s
213 KB/s

AES-CTR-128
563 KB/s
265 KB/s

AES-CTR-192
493 KB/s
240 KB/s

AES-CTR-256
437 KB/s
217 KB/s

AES-GCM-128
318 KB/s
193 KB/s

AES-GCM-192
293 KB/s
179 KB/s

AES-GCM-256
272 KB/s
166 KB/s

AES-CCM-128
240 KB/s
122 KB/s

AES-CCM-192
213 KB/s
112 KB/s

AES-CCM-256
192 KB/s
102 KB/s

AES-CMAC-128
471 KB/s
243 KB/s

AES-CMAC-192
419 KB/s
221 KB/s

AES-CMAC-256
378 KB/s
202 KB/s

AES-CMAC-PRF-128
471 KB/s
243 KB/s

CAMELLIA-CBC-128
489 KB/s
489 KB/s

CAMELLIA-CBC-192
381 KB/s
381 KB/s

CAMELLIA-CBC-256
381 KB/s
381 KB/s

BLOWFISH-CBC-128
692 KB/s
692 KB/s

BLOWFISH-CBC-192
692 KB/s
692 KB/s

BLOWFISH-CBC-256
692 KB/s
692 KB/s

CTR_DRBG (NOPR)
419 KB/s
211 KB/s

CTR_DRBG (PR)
311 KB/s
159 KB/s

HMAC_DRBG SHA-1 (NOPR)
90 KB/s
90 KB/s

HMAC_DRBG SHA-1 (PR)
84 KB/s
84 KB/s

HMAC_DRBG SHA-256 (NOPR)
65 KB/s
65 KB/s

HMAC_DRBG SHA-256 (PR)
65 KB/s
65 KB/s

RSA-2048
63 ms/ public
64 ms/ public

RSA-2048
2448 ms/private
2455 ms/private

ECDSA-secp384r1
940 ms/sign
950 ms/sign

ECDSA-secp256r1
628 ms/sign
636 ms/sign

ECDSA-secp384r1
1825 ms/verify
1848 ms/verify

ECDSA-secp256r1
1242 ms/verify
1244 ms/verify

ECDHE-secp384r1
1762 ms/handshake
1777 ms/handshake

ECDHE-secp256r1
1183 ms/handshake
1209 ms/handshake

ECDH-secp384r1
855 ms/handshake
864 ms/handshake

ECDH-secp256r1
582 ms/handshake
588 ms/handshake

ECDHE-Curve25519
981 ms/handshake
1007 ms/handshake

ECDH-Curve25519
495 ms/handshake
509 ms/handshake

Status
READY
Additional comments
~Work in progress, not ready yet.~
This PR is made on top of PR ~#2870~~#2891~ baremetal

@artokin I'm surprised by the presence of a few commits about X.509 here (from "Changed x509.c to be one single compilation unit for all x509 files." to "Changed generate_visualc_files.pl to exclude x509_xxx files"). Is that intentional, or just an unintended side-effect of how you prepared the branch?

Rebased on top of #2891 due merge conflicts.

Thanks for your comments @mpg , I'll address them next.
I just rebased this PR on top of updated #2891

Rebased on top of 0252cd6.

Removing "needs: preceding PR" as all prerequisites are now merged.

With two approvals and a passing CI, and no conflicts or dependencies, this is ready for merge.

Approving on the understanding we'll fix the issues I raised in a follow-up PR.


kite: trust only verified keys

deps: #157

Hey @rjeczalik could you please rebase this? depended PR is merged.

@cihangir Sure thing sir, rebased. 💥

A PR of AWESOMENESS.


try to create opensuse vmi in kubevirt getting error like "failed to find a sourceFile in containerDisk containerdisk: failed to determine default image path : lstat /proc/1/root/run/containerd/io.containerd.runtime.v2.task/k8s.io/8c08ed3038b10898e8af8a3a72cac81484075fcf53203fef69684694848d8311/rootfs/disk: no such file or directory     Reason:                Synchronizing with the Domain failed."

Please find below yaml for creating opensuse vmi.
apiVersion: kubevirt.io/v1
kind: VirtualMachineInstance
metadata:
name: susi-vm
spec:
terminationGracePeriodSeconds: 30
domain:
resources:
requests:
memory: 1024M
devices:
disks:
- name: containerdisk
disk:
bus: virtio
- name: emptydisk
disk:
bus: virtio
- disk:
bus: virtio
name: cloudinitdisk
volumes:

name: containerdisk
containerDisk:
image: registry.suse.com/suse/sle15:15.1
name: emptydisk
emptyDisk:
capacity: "2Gi"
name: cloudinitdisk
cloudInitNoCloud:
userData: |-
#cloud-config
password: fedora
chpasswd: { expire: False }

$kubectl describe vmi susi-vm
Name:         susi-vm
Namespace:    default
Labels:       kubevirt.io/nodeName=kubernetes-worker01
Annotations:  kubevirt.io/latest-observed-api-version: v1
kubevirt.io/storage-observed-api-version: v1alpha3
API Version:  kubevirt.io/v1
Kind:         VirtualMachineInstance
Metadata:
Creation Timestamp:  2023-03-20T12:41:31Z
Finalizers:
foregroundDeleteVirtualMachine
Generation:  6
Managed Fields:
API Version:  kubevirt.io/v1
Fields Type:  FieldsV1
fieldsV1:
f:metadata:
f:annotations:
.:
f:kubectl.kubernetes.io/last-applied-configuration:
f:spec:
.:
f:domain:
.:
f:devices:
.:
f:disks:
f:resources:
.:
f:requests:
.:
f:memory:
f:terminationGracePeriodSeconds:
f:volumes:
Manager:      kubectl-client-side-apply
Operation:    Update
Time:         2023-03-20T12:41:31Z
API Version:  kubevirt.io/v1alpha3
Fields Type:  FieldsV1
fieldsV1:
f:metadata:
f:annotations:
f:kubevirt.io/latest-observed-api-version:
f:kubevirt.io/storage-observed-api-version:
f:labels:
.:
f:kubevirt.io/nodeName:
f:status:
f:activePods:
.:
f:2c11b735-49f4-4f82-ad9a-f1e6f86a0479:
f:conditions:
f:migrationMethod:
f:migrationTransport:
f:nodeName:
f:phase:
f:phaseTransitionTimestamps:
f:qosClass:
f:selinuxContext:
f:volumeStatus:
Manager:         Go-http-client
Operation:       Update
Time:            2023-03-20T12:41:35Z
Resource Version:  2230074
UID:               83cf48ba-cd6d-457b-aa65-00161312a49f
Spec:
Domain:
Cpu:
Cores:    1
Model:    host-model
Sockets:  1
Threads:  1
Devices:
Disks:
Disk:
Bus:  virtio
Name:   containerdisk
Disk:
Bus:  virtio
Name:   emptydisk
Disk:
Bus:  virtio
Name:   cloudinitdisk
Interfaces:
Bridge:
Name:  default
Features:
Acpi:
Enabled:  true
Firmware:
Uuid:  c44784ae-1968-4259-bc28-4441697d71af
Machine:
Type:  q35
Resources:
Requests:
Memory:  1024M
Networks:
Name:  default
Pod:
Termination Grace Period Seconds:  30
Volumes:
Container Disk:
Image:              registry.suse.com/suse/sle15:15.1
Image Pull Policy:  IfNotPresent
Name:                 containerdisk
Empty Disk:
Capacity:  2Gi
Name:        emptydisk
Cloud Init No Cloud:
User Data:  #cloud-config
password: fedora
chpasswd: { expire: False }
Name:  cloudinitdisk
Status:
Active Pods:
2c11b735-49f4-4f82-ad9a-f1e6f86a0479:  kubernetes-worker01
Conditions:
Last Probe Time:       2023-03-20T12:41:31Z
Last Transition Time:  2023-03-20T12:41:31Z
Message:               Guest VM is not reported as running
Reason:                GuestNotRunning
Status:                False
Type:                  Ready
Last Probe Time:
Last Transition Time:
Message:               cannot migrate VMI which does not use masquerade to connect to the pod network
Reason:                InterfaceNotLiveMigratable
Status:                False
Type:                  LiveMigratable
Last Probe Time:
Last Transition Time:  2023-03-20T12:41:35Z
Message:               failed to find a sourceFile in containerDisk containerdisk: failed to determine default image path : lstat /proc/1/root/run/containerd/io.containerd.runtime.v2.task/k8s.io/a3da40812902c48ac51e227f6ef68d3748c5b74131c131b13c2d3b8c236c2c98/rootfs/disk: no such file or directory
Reason:                Synchronizing with the Domain failed.
Status:                False
Type:                  Synchronized
Guest OS Info:
Migration Method:     BlockMigration
Migration Transport:  Unix
Node Name:            kubernetes-worker01
Phase:                Scheduled
Phase Transition Timestamps:
Phase:                       Pending
Phase Transition Timestamp:  2023-03-20T12:41:31Z
Phase:                       Scheduling
Phase Transition Timestamp:  2023-03-20T12:41:31Z
Phase:                       Scheduled
Phase Transition Timestamp:  2023-03-20T12:41:35Z
Qos Class:                     Burstable
Runtime User:                  107
Selinux Context:               none
Volume Status:
Name:    cloudinitdisk
Target:
Name:    containerdisk
Target:
Name:    emptydisk
Target:
Events:
Type     Reason            Age                From                       Message

Normal   SuccessfulCreate  22s                virtualmachine-controller  Created virtual machine pod virt-launcher-susi-vm-4rvxr
Warning  SyncFailed        7s (x12 over 18s)  virt-handler               failed to find a sourceFile in containerDisk containerdisk: failed to determine default image path : lstat /proc/1/root/run/containerd/io.containerd.runtime.v2.task/k8s.io/a3da40812902c48ac51e227f6ef68d3748c5b74131c131b13c2d3b8c236c2c98/rootfs/disk: no such file or directory

/cc @vasiliy-ul
Does the container image contain the VM image(raw or qcow?)?

@ankurshukla2112, registry.suse.com/suse/sle15:15.1 is a regular SUSE-based container image. It is not a contaierdisk suitable for KubeVirt. I.e. it does not include a VM image.
To boot openSUSE VM in KubeVirt you can use https://en.opensuse.org/Portal:JeOS. You can download either TW or Leap image and create a containerdisk following the user guide.

HI @vasiliy-ul  can you provide url of opensuse image version 13.2

@ankurshukla2112, 13.2 is a very old distro. I am not sure if there are cloud images available. You can still find an installation ISO somewhere around and run it with KubeVirt.


build failed: /usr/bin/ld: cannot find -ledit

Hi, I followed Install from Source to compile tvm on ubuntu-16.04, but got failure from linker.
/usr/bin/ld: cannot find -ledit
I have install the requirements like this,
sudo apt-get update && sudo apt-get install -y python3 python3-dev python3-setuptools gcc libtinfo-dev zlib1g-dev build-essential cmake
Would you please tell how to install edit library? Thanks.

OK, I find the solution.
apt-get install libedit-dev
apt-get install libxml2-dev
I suggest add these two libs to the documentationInstall from Source.

Thanks for the suggestion, please send a PR to fix the docs https://github.com/dmlc/tvm/tree/master/docs this is a dependency of LLVM
For subsequent trouble shooting related question, please open a new thread on https://discuss.tvm.ai/

sudo apt-get install libgmp3-dev


feat: update to use go 1.22.0

will redo the PR after https://github.com/infracost/infracost/pull/2875

cc @aliscott


Windows errors

Hi guys,
OK, doing the right thing here and reporting formally. Here is a screenshot of the error that my RAs get whey the are done/close-to-done the 100 blocks (note the error text that is in the command prompt I believe occurs every time, not just upon completion of blocks, may or may not be related):

I just went through labeling 100 blocks to try and recreate this issue. I think the problem is that certain files in the clips directory got deleted (or moved) before having the labels sent back, and this prevents the files from being released from the "Active Blocks" list for that user. So for the Jessica user in particular, it looks like they've successfully sent back 97 reliability blocks to the server, but it also looks like the server thinks Jessica is still in possession of these blocks:

0001_000613s_reliability:::8
0274_000221_reliability:::33
0032_000604s_reliability:::39

So it's expecting you to submit those back, even though you're asking it for more blocks to be able to reach 100, it thinks it's already handed out 100 blocks to you, and it's waiting for responses to the last 3 (those listed above). It's likely that these 3 blocks were downloaded and then somehow lost either through someone deleting them from the clips directory, or moving them (or the directory) somewhere else. This is why it's important to basically never touch (or move) anything in the clips directory, and to always use the same directory across sessions. If you still have that directory somewhere on the computer, with those 3 blocks still sitting in there, try using that as the clips directory and submitting blocks back that way. If not, then you're just stuck with only being able to submit 97 blocks by this user. In the latest version of the program you're able to request specific blocks from the server and this wouldn't be an issue, but the current version doesn't allow it.
The Gateway Error response that it sends back should definitely be more informative though. I'll make sure to have this fixed before releasing the new version of the program. Thank you for bringing up this issue!


Move functions of LedControl into MFSegments

Description of changes
Fixes #49 and fixes #52
Required functions from LedControl lib are integrated into MFSegments.cpp. With these changes a buffer[64] can be avoided which will save additional RAM.
Furthermore no memory is allocated  on runtime (new LedControl()) and more important no delete _ledControl in case of writing a new config is required. delete seems not to be working properbly and fragmentates the memory.

Can I ask that you change all the added from LedControl:: to have the driver name in it so that other drivers can be added.

This PR is scoped to just the work required to fix some memory issues. Let's hold off on any additional changes until a future pull request so we can get this work completed and out the door.

@elral I'm actually of the philosophy that MFSegment should be made generic. The only per-driver info would be an enum of the supported types. Then, just as the LedControl lib is, have the 16K33 and TM1637 in their own libraries.
If you strip down the 3 libraries into bare bones MF only, instead of general purpose libs, they should be very small.
It's why I cloned them to my repo - to gut them of the unused functions since link-time-optimization (-flto) doesn't always remove unused functions in a class, and isn't supported in every toolchain linker.
To make MFSegment even more generic you could potentially Template the 3 drivers so that no if/else/switch is needed to call the class members.
`/* An enumeration of the supported types of LED digit displays */
enum eSegmentType
{
kSegmentType_undefined = 0,
kSegmentType_7seg = 7,
kSegmentType_14seg = 14,
kSegmentType_16seg = 16,
kSegmentType_16x8matrix = 128,
};
/* An enumeration of the supported multi-segment and dot-matrix drivers */
enum eSegmentDriver
{
kSegmentDriver_undefined = 0,
kSegmentDriver_MAX1719, // SPI
kSegmentDriver_MAX1721, // SPI
kSegmentDriver_HT16K33, // I2C
kSegmentDriver_TM1637   // pseudo I2C
};`


Nightmare 3.0.0

Hello!
Nightmare was released few hours ago. Is this plugin compatible with the new version?
I'm having a dependency issue:
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.

Given that 3.0 is about a change that probably breaks all plugins (https://github.com/segmentio/nightmare/pull/1391), almost certainly not. I probably won’t have any time to get to this soon, but if you want to work on it, I’ll happily review a PR.


Modfiy default colors to more distinct

Using the default color scheme in alacritty the current color scheme was hard to differentiate between dark grey, grey, and white
perhaps pick a more muted color for the bg cursor and a more distinct fg cursor color that will survive between common terminals
maybe consider 24bit color as default as well to get around relying on a terminals color settings.

Updated cursor colour. Blue on black


Add https://github.com/aquasecurity/trivy

See also https://github.com/LinuxSuRen/hd-home/issues/63#issuecomment-937875301

/assign


[Travis] Test against RubyGems 2.6.3

@homu r+

:pushpin: Commit 0236bb8 has been approved by segiddins

:hourglass: Testing commit 0236bb8 with merge 325d6b1...

:sunny: Test successful - status


Hacktoberfest 2018

This is a good project to work on if you want to do Hacktoberfest #Hacktoberfest Some things that might be fun to work on:

Adding ability to login to save jobs.
Adding your resume.
Add stackoverflow jobs.
Add some cool graphics that look like they are from the 80's.
Update the layout for the job post so it looks nicer.
Fix typos or grammer
Add the source for the job post to the listings on the home page.
Fix menu in mobile

@willywos is just sent a PR to Add stackoverflow jobs 👍

hey @chivoX yeah that was something that I recently added with a friend. I'll update this issue. Thanks

Why don't you migrate to Javascript, it will be better when the project scales and will have good performance also.

@vipulrawat just personal preference I suppose. I like to use ruby on rails and I've been doing lots of javascript at work using React Native and I really missed programming with the ruby language. I'm not really looking to move it to JS. As far as scale, I don't know if I'll ever have that problem and if I did I don't think I would have much of a problem because its not in js.
Feel free to work on this project if you want to work on one of these for hacktoberfest.
Thanks!

@willywos - just submitted a PR to add login / save job features. Let me know what you think

@willywos - just submitted a PR to fix mobile navbar - https://github.com/willywos/jobbyjobjob/pull/6

@willywos - small grammar fixes / initial project cleanup - https://github.com/willywos/jobbyjobjob/pull/7

@jakesorce you da man 👊
thank you for contributing and happy hacktoberfest!

Hi @willywos, I will gladly help on the "resume"  item, however I feel like we need to clarify some items.
What kind of features do you except?
How about(inspired by linkedin):

Small Bio - Text area
Experience section - Ability to add past or present jobs(with dates and a short description)
Skills section - Ability to add skills.

Or would you prefer a single text area that can be edited using a html editor(something like ckeditor https://ckeditor.com/ckeditor-5/)

@willywos I see that the project has authentication implemented, how about authorization? Are you familiar with the "cancan" gem? I could add it and configure the permisions for the existing controllers.

@willywos I see that the project has authentication implemented, how about authorization? Are you familiar with the "cancan" gem? I could add it and configure the permisions for the existing controllers.

@OvidiuToma Yeah I'm familiar with cancan, if you want to take that on that would be great. Thanks!

Thank You Everyone!


chore(ci): bump backwards compat tests to 1.0

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?

Checklist

[ ] I have written necessary rustdoc comments
[ ] I have added necessary unit tests and integration tests
[ ] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934).
[ ] My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
[ ] All checks passed in ./risedev check (or alias, ./risedev c)
[ ] My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

[ ] My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

[ ] My PR contains user-facing changes.

Click here for Documentation
Types of user-facing changes
Please keep the types that apply to your changes, and remove the others.

Installation and deployment
Connector (sources & sinks)
SQL commands, functions, and operators
RisingWave cluster configuration changes
Other (please specify in the release note below)

Release note

Minor release should not break backwards compat only.

Backwards compat tests now auto derive the base and newest version to test: #10413


Add check component

Changes proposed
This resolves some aspects discussed in #20 and #66
This PR provides an checkbox component with a single option.
It returns true if checked and false otherwise
To made this possible, parseValue method was changed to receive the component ref instead of value.
This will make sense for the next component, which should accept many options with multiple checkboxes.

Additional context
<Check name="fieldName" label="Test Field" />

will render
<input type="checkbox" id="fieldName" name="fieldName" />
<label for="fieldName">TestField</label>

and when form is submitted, you will receive { ..., fieldName: true | false, ... }

Look at #110


refactor(label): use "AttrsMixix" in label module

Pull Request Test Coverage Report for Build 892291466

168 of 169 (99.41%)  changed or added relevant lines in 21 files are covered.
3 unchanged lines in 2 files lost coverage.
Overall coverage increased (+0.09%) to 83.241%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

tensorbay/label/label_sentence.py
13
14
92.86%

Files with Coverage Reduction
New Missed Lines
%

tensorbay/label/basic.py
1
97.67%

tensorbay/utility/attr.py
2
97.5%

Totals

Change from base Build 892024798:
0.09%

Covered Lines:
4366

Relevant Lines:
5245

💛  - Coveralls


[Content UI] Code formatted as plain text

Steps to reproduce the problem

Go to https://learn.qiskit.org/course/ch-demos/bonus-level-make-your-own-puzzles
See error near the top where it says "from qiskit_textbook.games import hello_quantum". Should that be contained in a code block?

What is the current behavior?
text is displayed as plain text on the page
What is the expected behavior?
the code should be formatted like code
Screenshots (optional but very helpful)

Environment (optional but very helpful)

Device: macbook pro and samsung phone
OS: android and osx
Browser: firefox and brave

probably all environments
Additional context (optional)
Add any other context that could help debug the problem.

@JRussellHuffman - do you think this could be related?
https://github.com/Qiskit/platypus/issues/357
In this issue ☝, I'm suggesting that design provide guidance on 'syntax highlighting'. Do we have designs for what code syntax highlighting should look like for the following two use cases:

at the block level (imagine lines of code that take up the entire width of a paragraph)

pip install example

inline code, for example, this would be inline and site right inside some content

I see the two as separate.
The item described in the issue should just be a bug where text that should be code is formatted like text.
The content of #357 seems like an enhancement to how we render code, which is definitely a good idea, but not really a bug. I'll give some input over in 357, but for this issue, I think the code just needs to be dropped into a code block (instead of plain text).

New URL: https://learn.qiskit.org/course/ch-demos/bonus-level-sandbox#bonus-148-0
@JRussellHuffman, the text from qiskit_textbook.games import hello_quantum is indeed being rendered as HTML code:
Code:

Screenshot:

But I get the point that it's confusing since it looks too similar to regular text.
To change this, we first need a design of how we want to style text that is inside a code tag. But this would be a new feature request and not a bug, unless we have another instance on the Textbook when we display this kind of code (not whole code cells) differently or if we already have a design for it.

The new URL is broken for me.
It sounds like this might be a content issue. Is the code tag different from how code gets rendered inside of a code cell? My assumption is that these snippets of code are supposed to be displayed inside a code block like most other code on most other pages.

yes, code tag is rendered different from an actual code cell. notebook code cells are meant to be executed, while the code tag is in a markdown cell (and not intended for execution). being in a markdown cell, it is being parsed/rendered using the markdown renderer.  i agree these should be inside some code block styling, but as @eddybrando mentioned we'd need a design for  this.
since these <code> blocks are not meant to be executed/run, but rather just complement the prose, one option is reusing the current code blocks components styling, but without a Run button.
however, i think reusing the same style as the current code block, but without a Run button may cause confusion (i.e. falsely thinking something is broken since Run button missing)? i
maybe a slightly more different design for these <code> blocks so they dont look like plain text but are distinguishable enough them from the executable code cells 🤷🏽♂

I like this solution. Our standard code block can be pretty heavy, so a slim version that is basically just the cool-gray-10 background for inline code makes sense.
The example above isn't inline, but do you two think this proposed solution still makes sense?

The example above isn't inline, but do you two think this proposed solution still makes sense?

True. For block code GitHub has a similar solution:
I'm code.
I'm life.

so do we agree on something like this (block code vs inline code, using cool-gray-10)

I personally like what you're showing, @vabarbosa
just noting that on Carbon's website, they use a slight 4px border-radius, and a little bit of left/right padding:

This repository is no longer maintained. It has been superseded by IBM Quantum Learning.


Add a license to the repository

I recently came across your project qiskit and I noticed that the repository github.com/gabridi1/qiskit currently does not have a license specified.
Why Adding a License is Important?
As GitHub documents

Public repositories on GitHub are often used to share open source software. For your repository to truly be open source, you'll need to license it so that others are free to use, change, and distribute the software.

Would be possible to add a valid license to this repository? Probably something really OpenSource such as the Apache 2.0 license would fit really well.
Thanks!

Thanks!


Helm repo broken

What happened:
❯ helm repo add bitpoke https://helm.bitpoke.cloud/charts
Error: looks like "https://helm.bitpoke.cloud/charts" is not a valid chart repository or cannot be reached: Get "https://helm.bitpoke.cloud/charts/index.yaml": dial tcp: lookup helm.bitpoke.cloud: no such host

What you expected to happen:
❯ helm repo add bitpoke  https://helm.bitpoke.cloud/charts
"bitpoke" has been added to your repositories

How to reproduce it (as minimally and precisely as possible):
❯ helm repo add bitpoke https://helm.bitpoke.cloud/charts

Was able to install via:
❯ helm repo add presslabs https://presslabs.github.io/charts
❯ helm install wordpress-operator presslabs/wordpress-operator

Not sure if this is now the intended way.


Add HOMEBREW_NO_INSTALL_FROM_API

This allows HOMEBREW_INSTALL_FROM_API functionality to be disabled and will stick around once HOMEBREW_INSTALL_FROM_API is made the default behaviour.

Review period skipped due to critical label.


"ANCM Failed to Start" after upgrade to ASP .NET 3.0 -- breaking change for debugger only

I'm going to right out admit I don't know how Visual Studio's right click -> Start Debugging works for web projects.
I've more or less followed the instructions for upgrading projects to 3.0, manually project files to do so. (I've got too much stuff in there that Visual Studio doesn't understand for me to trust the IDE to handle it.) I've gotten to the point where the projects light up and run with dotnet run and I can point my web browser at them.
But when it comes to Right Click -> Debug in Visual Studio, it doesn't work. The browser takes a long time to yield the ANCM Failed to Start message. Debugging didn't take very long. The project is listening on its default port in appsettings.json and whatever method has historically been used for Visual Studio to redirect the startup sequence isn't working more. I'm convinced it's supposed to be environment variables.
Here's my current entry point:
            var builder = new ConfigurationBuilder()
                    .SetBasePath(Directory.GetCurrentDirectory())
                    .AddJsonFile("appsettings.json", optional: false, reloadOnChange: true)
                    .AddJsonFile("devsettings.json", optional: true, reloadOnChange: true)
                    .AddEnvironmentVariables();
            var config = builder.Build();

            var host = new WebHostBuilder()
                .UseKestrel(options =>
                {
                    // Kestrel really does require one port per service.
                    var port = config.GetValue<ushort>("Port", 0);
                    var httpsport = config.GetValue<ushort>("HttpsPort", 0);
                    var certificate = config.GetValue<string>("Certificate", "");
                    var certificatepw = config.GetValue<string>("CertificatePassword", "");
                    var bindaddr = config.GetValue<string>("BindAddress", "*");
                    System.Net.IPAddress bindto = (string.IsNullOrEmpty(bindaddr) || bindaddr == "*") ? null : System.Net.IPAddress.Parse(bindaddr);
                    Action<Microsoft.AspNetCore.Server.Kestrel.Core.ListenOptions> https =
                            listenOptions =>
                            {
                                if (!string.IsNullOrEmpty(certificate))
                                    listenOptions.UseHttps(certificate, certificatepw);
                            };
                    bool disableIPv6 = config.GetValue<bool>("DisableIPv6", false);
                    if (!config.GetValue<bool>("DisableIPv4", false))
                    {
                        if (port > 0)
                            options.Listen(System.Net.IPAddress.Loopback, port);
                        // DisableIPv4 doesn't reaally work because Kestrel will bind anyway to IPv4 if possible and given IPv6 any;
                        // this switch can only be used to avoid blowing up if the host doesn't have an IPv4 stack.
                        // Don't bind twice
                        if (httpsport > 0 && certificate != null
                            && (!(bindto is null) || disableIPv6)
                            && (bindto is null || bindto.AddressFamily == System.Net.Sockets.AddressFamily.InterNetwork))
                        {
                            options.Listen(bindto ?? System.Net.IPAddress.Any, httpsport, https);
                        }
                    }
                    if (!disableIPv6)
                    {
                        if (port > 0)
                            options.Listen(System.Net.IPAddress.IPv6Loopback, port);
                        if (httpsport > 0 && certificate != null
                            && (bindto is null || bindto.AddressFamily == System.Net.Sockets.AddressFamily.InterNetworkV6))
                        {
                            options.Listen(bindto ?? System.Net.IPAddress.IPv6Any, httpsport, https);
                        }
                    }
                    options.AllowSynchronousIO = true;
                })
                .UseContentRoot(Directory.GetCurrentDirectory())
                .ConfigureLogging((logging) =>
                {
                    logging.ClearProviders();
                    logging.AddConsole();
#if DEBUG
                    logging.AddDebug();
#endif
                })
                .UseIISIntegration()
                .ConfigureServices((services) =>
                {
                    services.AddSingleton<IStartup>((sp) => new Startup(config));
                })
                .UseSetting(WebHostDefaults.ApplicationKey, "Cedaron.FormBuilder.WebAPI")
                //.UseApplicationInsights()
                .UseConfiguration(config)
                .Build();

            host.Run();

The only differences in this code between 2.1 startup and 3.0 startup are the .ConfigureLogging block (used to be in Startup.cs) and commenting out .UseApplicationInsights().
There is no launchsettings.json anymore. We haven't been using that since NET Core 1.0.

Tag @jkotalik - any ideas?

By default in 3.0, we use an Inprocess IIS server to host within IISExpress. Can you see what happens when you call .UseIIS() after calling UseIISIntegration()?
We also recommend using CreateDefaultHostBuilder as well: https://docs.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.webhost.createdefaultbuilder?view=aspnetcore-2.2

.UseIIS() was the key. Thank you. Anyway, we are very far from CreateDefaultBuilder() now. In fact, this particular server should not set ContentRootPath ever. We no longer use the stock static file provider due to bugs.


chore: fix focuses layout

merge #188 before

:tada: This PR is included in version 1.26.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Building costs grow too quickly to sustain games beyond an hour

Looking at the formula for building costs it becomes prohibitively expensive for a player to purchase buildings after the first hour of play.  From generator.ts: return gen.StartingCost * gen.CostFactor ** own_count;

Some type of dampening should be considered for own_count, perhaps dividing it by 2, 3 or even 4 (shown below):

Nice analysis :) To be fair, we didn't expect most people to play Afterlife for more than 5 minutes. It's a jam game, and it's understandable that the attention span of participant is short.

I know this was a little over the top. ;)  Thanks for the replies, comments in the code, and bravo on the game - one of my favorites from the jam.


Please provide a minimum php version

Recommending Php 7 is a bad idea and will discourage people using older php versions from using this package. Please specify the minimum Php version required

I have mention both in composer.json and in the readme file that the required (not recommended) version is PHP 7+. This is because I have used scalar type declarations which are only available at PHP 7 and up.
Anyone really needs to use this library on older PHP versions can easily fork it and remove the scalar type declarations for compatibility.
I really do believe the best option is to upgrade to PHP 7 which has many great new features, security updates and huge performance boost. I understand this might sometimes be hard but there are some tools that can help make it much easier and it will definitely be worth it.