Error cannot find type definition: decimal.NullDecimal

Describe the bug
I create a struct with decimal.NullDecimal inside then when generate swaggo got this error
Error cannot find type definition: decimal.NullDecimal
To Reproduce
Steps to reproduce the behavior:

Create a struct with decimal.NullDecimal field
Swag init

Expected behavior
Generate normally like decimal.Decimal
Your swag version
swag version v1.8.10
Your go version
go version go1.20 linux/amd64
Desktop (please complete the following information):

OS: Windows 10
Version: 21H2 (OS Build 19044.2965)

If the type is internal you have to add the flag --parseInternal, if its from a dependencies use --parseDependency
swag init --parseDependency --parseInternal

Hi all!)
I have the same issue with swag init --parseInternal --parseDepth 2 -g path/to/my/main.go
Maybe there are other solutions to resolve this issue?

stanlyzoolo

I have another solution, make the .swaggo file among with your go.mod
Content inside .swaggo will be
replace JsonNullBool boolean replace JsonNullNumber integer replace JsonNullNumberStr string replace decimal.NullDecimal number
maybe your case will be
replace sql.NullTime string

Thanks for an advice)
I found the better solution by adding swaggertype:"string" tag for changed sql.NullTime type
It works well for me :)


Sub called tasks with chokidar don't work as expected.

Since the 3.0 update, I can no longer get chokidar to work in sub tasks. Either as a chokidar-cli command called with run, or by requiring chokidar directly in node.
chokidar './src/files/**/*.js' -c "run reload"
or
chokidar.watch('./src/files/**/*.js', {}).on('all', (event, path) => {
  console.log('reloading'')
  run(`reload`);
});

Any errors ?

Can you task reload directly as a function:
chokidar.watch('./src/files/**/*.js', {}).on('all', (event, path) => {
  console.log('reloading'')
  reload() // or task['reload']() depending on your runfile.js
});

@nverba I've checked chokidar with runjs 3.0.0 and everything works perfectly fine. Looks like your task call in a callback is incorrect. So construction should be something like this:
import { run } from 'runjs'
import chokidar from 'chokidar'

export function watch () {
  chokidar.watch('.', {}).on('all', (event, path) => {
    console.log('WATCH', event, path)
    reload()
  });
}

export function reload () {
  console.log('reloading')
}

Thank you for the assist.
I would often call run tasks from within run tasks. This worked without issue in previous versions of runjs, and seemed like a simple (read: lazy) way of building up/chaining complex build steps.
I see now that this was a bad pattern. Having spent yesterday refactoring our build process, I'm happy to say your advice has not only fixed the issue I was having, but the code quality is looking much better now too.
Thanks again.

@nverba very cool 👍  happy to help


r

Summary

Simplest Example to Reproduce

request({
  method: 'GET',
  url: 'http://example.com', // a public URL that we can hit to reproduce, if possible
  more: { 'options': 'here' }
},

Expected Behavior

Current Behavior

Possible Solution

Context

Your Environment

software
version

request

node

npm

Operating System

What is the sense of this empty issue?

What is the sense of this empty issue?

@Tizioincognit0 maybe spam bots perhaps?


Url decorator partially broken starting with v0.2.12

When I initially started using ui-router, I'd define the url for each state using the UrlMatcherFactoryProvider so that I could set the caseInsensitivity to false. What I didn't realize was that this required absolute urls, so I went on a quest to find what I think is a better solution.
Decorators For The Win
After perusing the API docs for awhile I stumbled upon the decorators of the $stateProvider. After a little trial and error, I came up with the following code:
	$stateProvider.decorator('url', function (state, parent) {
		var matcher = parent(state)
		if (matcher && !state.abstract) {
			matcher = matcher.concat("", { caseInsensitive: true });
		}
		return matcher;
	});

For the uninitiated, this callback will receive all registered states. The 'parent' parameter is a function that will retrieve the UrlMatcher for the state passed in. The callback should return a UrlMatcher. Since some state don't have urls and/or are abstract, I weed those out. Once I have a proper UrlMatcher, I use the concat function to make it case-insensitive.
This code works for all states in v0.2.11 but the versions  up to 0.2.13 (as of this writing) causes any state with a url containing a queryString parameter to fail validating the ParamSet. Here's the offending code in ui-router:
    $$validates: function $$validate(paramValues) {
      var result = true, isOptional, val, param, self = this;

      forEach(this.$$keys(), function(key) {
        param = self[key];
        val = paramValues[key];
        isOptional = !val && param.isOptional;
        result = result && (isOptional || !!param.type.is(val));
      });
      return result;
    },

The parameter paramValues has the keys I pass in but self doesn't. I understand that self is supposed to be the url ParamSet but I don't get why it doesn't pick up the parameters I placed in the state url property. I also understand that something may have gotten more strict in how things are done and now my url decorator callback may not be fully compliant. Either way, I'd like to know if this is a bug or what needs to be done to fix my decorator callback.
Thanks

can you use $urlMatcherFactory.caseInsensitive(true) to make all your urls case insensitive?
http://angular-ui.github.io/ui-router/site/#/api/ui.router.util.$urlMatcherFactory

Well I presumed that I have to do that in the .config() section which doesn't allow factories. I did notice that it is also available as $urlMatcherFactoryProvider and I tried using that but it didn't seem to have an effect, which is why I fell back on using the decorators.
I went back and tried it again and $urlMatcherFactory.caseInsensitive(true) did not work for v0.2.11 but I also then tried it for v0.2.13 and it does work.... partially. I don't know if you can do anything about it, but if you use a base tag and change the casing in it, the case insensitivity doesn't work. But I consider that extremely minor. Sorry for bothering you, keep up the good work! :)

I don't know if you can do anything about it, but if you use a base tag and change the casing in it, the case insensitivity doesn't work.

Can you give me some more details?

Well I looked at the crash details and ui-router doesn't seem to be involved. Basically, I have an application in a folder instead of on the root of the domain. Let's say it's /MyApp and I have the base tag in the HTML set to href="/MyApp/". If I go to /myApp instead of /MyApp, the site doesn't load because of an exception: TypeError: Cannot read property 'replace' of undefined. The stack track is all angular.js so I believe ui-router is totally absolved of this issue.


Allow lists to be built from iterators

In particular, allow lists to be built from
double ended iterators, which avoids allocating
intermediate vectors.

Nice! Did you compare the performance of both approaches?

make_list_from_end was actually 20% faster when encoding arrow arrays. I am yet to benchmark if it makes the default Vector encoding faster too. Later today I Will have some numbers. :)

Ok, so this is tricky. Here are the numbers:
## New (this PR)

Name               ips        average  deviation         median         99th %
16 elems        1.03 M      971.63 ns  ±1498.29%         958 ns        1083 ns
32 elems      668.49 K        1.50 μs   ±918.15%        1.46 μs        1.58 μs
128 elems     220.57 K        4.53 μs   ±388.58%        4.38 μs        4.75 μs
1k elems       31.51 K       31.73 μs     ±5.36%       31.29 μs       36.92 μs
1M elems         28.28       35.37 ms     ±7.33%       33.73 ms       40.14 ms

## Old (master)

Name               ips        average  deviation         median         99th %
16 elems      915.15 K        1.09 μs  ±1399.89%        1.08 μs        1.21 μs
32 elems      696.04 K        1.44 μs   ±943.38%        1.42 μs        1.54 μs
128 elems     274.22 K        3.65 μs   ±289.96%        3.54 μs        3.88 μs
1k elems       42.16 K       23.72 μs    ±67.46%       23.17 μs       29.50 μs
1M elems         38.43       26.02 ms     ±7.68%       24.69 ms       30.16 ms

You can see this PR is faster for small lists but then it gets slower, most likely because enif_make_list_from_array allocates the whole area upfront, while this PR has to allocate cell by cell. On the other hand, the current approach uses less memory.
I will be glad to revert the changes to rustler::types::list if you would prefer to not change the default encoding.

With regards to https://github.com/erlang/otp/issues/6293:
There are a couple of places I can think of where the performance difference might come from between approach 1. and 2.:
a. The alloc/free of the buffer used to store terms passed to enif_make_list_from_array
b. The allocation on the process heap inside enif_make_list_from_array/enif_make_list_cell
c. The function call overhead each time enif_make_list_cell is called
The two different approaches are affected by the different factors as follows:

a and b dominates
b and c dominates

I have nothing hard to base this on, but I have a gut feeling the reason why approach 2 gets slower is because c becomes the dominating factor.
If this is the case, introducing an API like enif_alloc_list/enif_set_list might not improve things by much.

@hansihe if the NIF cost is the culprit, then we can emulate it? Here is what I did, I changed encode to perform a NIF call to enif_make_list(env, 0), which is as cheap as a NIF can be:
impl<T> Encoder for [T]
where
    T: Encoder,
{
    fn encode<'b>(&self, env: Env<'b>) -> Term<'b> {
        let env_as_c_arg = env.as_c_arg();
        let term_array: Vec<NIF_TERM> = self.iter().map(|x| {
            unsafe { rustler_sys::_enif_make_list(env_as_c_arg, 0) };
            x.encode(env).as_c_arg()
        }).collect();
        unsafe { Term::new(env, list::make_list(env.as_c_arg(), &term_array)) }
    }
}

These are the results:
16 elems       945.72 K        1.06 μs  ±1417.14%        1.04 μs        1.17 μs
32 elems       703.49 K        1.42 μs   ±889.53%        1.38 μs        1.58 μs
128 elems      278.42 K        3.59 μs   ±367.05%        3.46 μs        3.88 μs
1k elems        43.41 K       23.04 μs    ±51.07%       22.46 μs       29.45 μs
1M elems          37.20       26.88 ms     ±7.57%       25.52 ms       31.26 ms

As you can see, it is slightly lower for the large case, but sometimes even slightly faster, so I don't think the NIF call adds to much? WDYT?

@josevalim Smart way of testing it!
Seems I was very off target with what cost dominated. The API you suggested would probably work pretty well


feat: Add optional policy_path variable used for policy definitions

Description
Add optional policy_path variable used for policy definitions.
Motivation and Context
If you are using policy_path for security reasons and need to set the policy_path, you will not be able to use the terraform-aws-step-functions. With this change, the path can be configured using the policy_path variable, or leave the default "/" if the variable is omitted.
Breaking Changes
No Breaking Changes the default for policy_path remains "/".
How Has This Been Tested?

[ ] I have updated at least one of the examples/* to demonstrate and validate my change(s)
I have not updated the examples as role_path is also not used in the examples and I suspect that it was done that way on purpose.
[ ] I have tested and validated these changes using one or more of the provided examples/* projects

[x] I have executed pre-commit run -a on my pull request

Thank you, @rgrund-inform !

This PR is included in version 4.1.0 :tada:


[condition][dockerfile] It's not possible to define a condition on a Dockerfile arg with a default value

Describe the bug
conditions:
  isARGTINIVERSIONSet:
    name: Is ENV TINI_VERSION set
    kind: dockerfile
    spec:
      file: Dockerfile
      Instruction: ARG[1][0]
      Value: "tini_version"

for the Dockerfile instruction ARG tini_version=v0.19.0, like for ENV, I expect  ARG[1][0] to be 'tini_version' but it is 'tini_version=v0.19.0'
Version (please complete the following information):

OS: linux
Version: v0.30.0

Proposal for a syntax adaptation for the dockerfile's kind (UX), to help solving this issue:
The idea is to:

Not using the array syntax []
Delegate the "research" of the expected instruction to updateCLI

conditions:
  isENVSet:
    name: Is ENV HELM_VERSION set
    kind: dockerfile
    spec:
      ## Search for the presence of an `ENV HELM_VERSION=.*` instruction.
      ## Condition is true if it fins 1 or more occurrences in the Dockerfile
      file: docker/Dockerfile
      Instruction:
        env: "HELM_VERSION"
targets:
  updateENVHELMVERSION:
    name: Update HELM_VERSION
    kind: dockerfile
    spec:
      ## Update all the occurrences of `ENV HELM_VERSION=.*`
      file: docker/Dockerfile
      Instruction:
        env: "HELM_VERSION"

Same could be applied for ARGS and FROM:
targets:
  updateARGHELMVERSION:
    name: Update HELM_VERSION
    kind: dockerfile
    spec:
      ## Update all the occurrences of `ARG HELM_VERSION=.*`, but do not update `ARG HELM_VERSION` with no value
      file: docker/Dockerfile
      Instruction:
        arg: "HELM_VERSION"

targets:
  updateFROMGOVERSION:
    name: Update GO_VERSION
    kind: dockerfile
    spec:
      ## Update all the occurrences of `FROM golang.*`
      file: docker/Dockerfile
      Instruction:
        from: "golang" # or "golang:alpine" for tag strict matching

Additionnaly:

A new keyword onlyFirst could be added, with a default value set to false, valid for the 3 instructions (for ENV and arg it is straightforward. For the FROM it would cover cases with multistage builds)

targets:
  updateENVHELMVERSION:
    name: Update HELM_VERSION
    kind: dockerfile
    spec:
      ## Update only the first occurrence of `ENV HELM_VERSION=.*`
      file: docker/Dockerfile
      Instruction:
        env:
          key: "HELM_VERSION"
          onlyFirst: true

A new keyword onlyDefaultValues (default to true) could be added but only for the ARG instruction, to only replace the instruction holding a (default) value (e.g. ARG TERRAFORM_VERSION=0.14.5), and not the unvalued declarations (e.g. ARG TERRAFORM_VERSION):

targets:
  updateARGTERRAFORMVERSION:
    name: Update TERRAFORMVERSION
    kind: dockerfile
    spec:
      ## Update all the occurrences of `ARG TERRAFORMVERSION=.*` and `ARG TERRAFORMVERSION`
      file: docker/Dockerfile
      Instruction:
        env:
          key: "TERRAFORMVERSION"
          onlyDefaultValues: false

Proposal for a syntax adaptation for the dockerfile's kind (UX), to help solving this issue:
The idea is to:

Not using the array syntax []
Delegate the "research" of the expected instruction to updateCLI

conditions:
  isENVSet:
    name: Is ENV HELM_VERSION set
    kind: dockerfile
    spec:
      ## Search for the presence of an `ENV HELM_VERSION=.*` instruction.
      ## Condition is true if it fins 1 or more occurrences in the Dockerfile
      file: docker/Dockerfile
      Instruction:
        env: "HELM_VERSION"
targets:
  updateENVHELMVERSION:
    name: Update HELM_VERSION
    kind: dockerfile
    spec:
      ## Update all the occurrences of `ENV HELM_VERSION=.*`
      file: docker/Dockerfile
      Instruction:
        env: "HELM_VERSION"

Same could be applied for ARGS and FROM:
targets:
  updateARGHELMVERSION:
    name: Update HELM_VERSION
    kind: dockerfile
    spec:
      ## Update all the occurrences of `ARG HELM_VERSION=.*`, but do not update `ARG HELM_VERSION` with no value
      file: docker/Dockerfile
      Instruction:
        arg: "HELM_VERSION"

targets:
  updateFROMGOVERSION:
    name: Update GO_VERSION
    kind: dockerfile
    spec:
      ## Update all the occurrences of `FROM golang.*`
      file: docker/Dockerfile
      Instruction:
        from: "golang" # or "golang:alpine" for tag strict matching

Additionnaly:

A new keyword onlyFirst could be added, with a default value set to false, valid for the 3 instructions (for ENV and arg it is straightforward. For the FROM it would cover cases with multistage builds)

targets:
  updateENVHELMVERSION:
    name: Update HELM_VERSION
    kind: dockerfile
    spec:
      ## Update only the first occurrence of `ENV HELM_VERSION=.*`
      file: docker/Dockerfile
      Instruction:
        env:
          key: "HELM_VERSION"
          onlyFirst: true

A new keyword onlyDefaultValues (default to true) could be added but only for the ARG instruction, to only replace the instruction holding a (default) value (e.g. ARG TERRAFORM_VERSION=0.14.5), and not the unvalued declarations (e.g. ARG TERRAFORM_VERSION):

targets:
  updateARGTERRAFORMVERSION:
    name: Update TERRAFORMVERSION
    kind: dockerfile
    spec:
      ## Update all the occurrences of `ARG TERRAFORMVERSION=.*` and `ARG TERRAFORMVERSION`
      file: docker/Dockerfile
      Instruction:
        env:
          key: "TERRAFORMVERSION"
          onlyDefaultValues: false


Cannot read property 'destroy' of null

Hi, I'm using NuxtJS I have a problem when I want to go to the home page and I click in a button that uses vue-router to go to another page this problem show up

This question is available on Nuxt community (#c9626)

Hi. I faced the same problem. How did you solve it?

Me too. Anyone knows how to solve this?

I've solved this problem.
It turned out that I used the reserved name "watcher" in the computed properties.


[Bug]: awq marlin error for deepseek v2 lite

Your current environment
vllm==0.6.3.post1
Model Input Dumps
ValueError: Weight input_size_per_partition = 10944 is not divisible by min_thread_k = 128. Consider reducing tensor_parallel_size or running with --quantization gptq.

🐛 Describe the bug
When I run the command on one gpu:
python -m vllm.entrypoints.openai.api_server --port 10086 --model TechxGenus/DeepSeek-Coder-V2-Lite-Instruct-AWQ --dtype float16 --gpu-memory-utilization 0.8 --max-model-len 8192 --enable-prefix-caching --disable-log-requests --trust-remote-code --enforce-eager

It raise the error:
ValueError: Weight input_size_per_partition = 10944 is not divisible by min_thread_k = 128. Consider reducing tensor_parallel_size or running with --quantization gptq.

Then I try to change the configuration of marlin kernel at https://github.com/vllm-project/vllm/blob/main/vllm/model_executor/layers/quantization/utils/marlin_utils.py#L14:
-GPTQ_MARLIN_MIN_THREAD_K = 128
+GPTQ_MARLIN_MIN_THREAD_K = 64

It run successfully, and the output also looks well.
Will this have any other impact on the marlin kernel? If there is no other impact, I hope this change can be applied to support it.
Before submitting a new issue...

[X] Make sure you already searched for relevant issues, and asked the chatbot living at the bottom right corner of the documentation page, which can answer lots of frequently asked questions.

thx it helps alot 🌹


dev-cmd/dispatch-build-bottle: remove testing code.

This was accidentally merged in https://github.com/Homebrew/brew/pull/9444.

Review period will end on 2020-12-08 at 14:42:52 UTC.

Review period skipped due to critical label.

Confirmed working in latest builds


fix sql injections vulnerabilities

Checkmarx One – Scan Summary & Details – d59b711c-c732-4f78-852e-53e9299ec326
Fixed Issues

Severity
Issue
Source File / Package

SQL_Injection
/Controllers/ProductsController.cs: 65

CSRF
/Controllers/ProductsController.cs: 80

CSRF
/Controllers/ProductsController.cs: 32


Add Lastpass source

This source will pull users from Lastpass
Only one new node:

Lastpass

It uses Human as pivot with other modules (GSuite, GitHub, HiBob ...)

Sure I can do that.
Tenant Node will be pretty empty but that make sense.
Le mar. 14 févr. 2023, 07:11, Alex Chantavy @.***> a
écrit :

@.**** commented on this pull request.
In cartography/intel/lastpass/schema.py
https://github.com/lyft/cartography/pull/1083#discussion_r1105334990:

admin: PropertyRef = PropertyRef('admin')

totalscore: PropertyRef = PropertyRef('totalscore')
mpstrength: PropertyRef = PropertyRef('mpstrength')
sites: PropertyRef = PropertyRef('sites')
notes: PropertyRef = PropertyRef('notes')
formfills: PropertyRef = PropertyRef('formfills')
applications: PropertyRef = PropertyRef('applications')
attachments: PropertyRef = PropertyRef('attachments')
password_reset_required: PropertyRef = PropertyRef('password_reset_required')
multifactor: PropertyRef = PropertyRef('multifactor')

@.***(frozen=True)
+class LastpassUserSchema(CartographyNodeSchema):

label: str = 'LastpassUser'
properties: LastpassUserNodeProperties = LastpassUserNodeProperties()

@resilience-jychp https://github.com/resilience-jychp - hey, one more
thought - what would make sense to use for a Lastpass sub resource? If
there is a concept of an "organization" or "tenant" or something similar
then we would link the Lastpass user to that so that cleanup jobs become
more safe.
—
Reply to this email directly, view it on GitHub
https://github.com/lyft/cartography/pull/1083#pullrequestreview-1296891422,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A3FFJZRYFBOGQICQCTFECELWXMOYRANCNFSM6AAAAAAT2SA5KM
.
You are receiving this because you were mentioned.Message ID:
@.***>

@achantavy
I migrate to new model architecture, but not sure how auto_cleanup work, so I kept the old way.

@achantavy this PR should be ready for new model, waiting for you comments before working on other ones

@achantavy @ramonpetgrave64 changes made

Thank you @resilience-jychp !


nixos-manual: start gradual conversion to markdown

Basically copied from the nixpkgs manual infrastructure.
Converted 'installation/upgrading' as a test.
I guess we should find a way to represent the 'xref linkend'
links to 'proper' markdown as well

Motivation for this change
Wanted to document creating udev rules to load kernel modules when certain USB devices are plugged in, but didn't really want to deal with docbook, so shaved this yak first ;)
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

/cc @ryantm

This approach may be problematic because NixOS needs to build it's own manual as part of rebuilds (I think).
Cc @jtojnar

That is right, NixOS systems depend on NixOS manual by default so we would have to introduce pandoc into the NixOS build closure. I would not mind since we compile pandoc statically these days and its closure is pretty small, and for most people, the binary cache is leveraged for the manual anyway, but there was some opposition, particularly from @edolstra.
Also, I do not think it is really possible to achieve the closure size of libxslt + docbook-xsl if we want to use anything but the barest CommonMark implementation. https://github.com/NixOS/rfcs/pull/72 mandates extensibility and I am not aware of any extensible Markdown implementations outside of Pandoc, Python/Sphinx and JavaScript ecosystems.
Since https://github.com/NixOS/rfcs/pull/72, was not concrete enough, I am afraid we cannot really do much until the expectations for building NixOS manual are settled.

OK, I guess this change is premature :). Let's gather some experience converting the nixpkgs manual, and revisit this later.

NixOS systems depend on NixOS manual by default

Random thought: in the "in case of emergency" situations where this is useful, I'd be happy reading the raw markdown version...

Also, I do not think it is really possible to achieve the closure size of libxslt + docbook-xsl if we want to use anything but the barest CommonMark implementation.

Given that Markdown is supposed to be a light-weight, trivial format, it would be quite sad if it required adding gigabytes and hours of build-time dependencies...
Of course, we could disable building the manual by default (see https://github.com/NixOS/nixpkgs/pull/83871) in which case the issue would be moot.

Given that Markdown is supposed to be a light-weight, trivial format, it would be quite sad if it required adding gigabytes and hours of build-time dependencies...

Well, the issue is that that supposition is at odds with requirements for complex technical documentation documents. That is why CommonMark/Markdown is almost never used as is and most implementations extend it. Even https://github.com/NixOS/rfcs/pull/72, vague as it is on other implementation details, acknowledges the necessity of extensions.

@raboof We can still move forward with the conversion without including Pandoc in the closure, we just need to store the generated Docbook XML files in the git repository. I was thinking there could be a separate folder for these generated documents so we don't accidentally edit them manually.

Copied from https://github.com/NixOS/nixpkgs/pull/107444#discussion_r547917359:

Keeping both files in sync won't work. People are not aware they need to edit both files when updating docs, and these files will just diverge.

Yes, pandoc is a heavy ask, but we also build half of firefox due to polkit rules being in javascript, so having pandoc in the build closure is a small problem - and if people want to quickly iterate on a new rebuild, disabling the manual for that local test is probably the better way forward than dumping two different and slowly diverging documentation file formats.


Add new Dockerfile for a python3.8-cyvcf2-venv image

This PR adds | fixes:

Added a Dockerfile for a base images containing Python 3.8 with cyvcf2 installed insided a virtual environment

How to test:

Build the image with the command: docker build -t python3.8-cyvcf2-venv --file python3.8-cyvcf2-venv/Dockerfile

Expected outcome:

[ ] There should be no build errors

Review:

[ ] Code approved by
[ ] Tests executed by
[ ] "Merge and deploy" approved by

This version is a:

[ ] MAJOR - when you make incompatible API changes
[x] MINOR - when you add functionality in a backwards compatible manner
[ ] PATCH - when you make backwards compatible bug fixes or documentation/instructions

the image builds as expected: 🆗

This is now pushed to docker hub: https://hub.docker.com/repository/docker/clinicalgenomics/python3.8-cyvcf2-venv


MM-36687 Fix CRT Notifications

Summary

Added is_crt_enabled field
Grouping notifications by thread_id when CRT is enabled in iOS
root_id is always sent from server, moving It to common fields

https://mattermost.atlassian.net/browse/MM-36687
Related PRs
https://github.com/mattermost/mattermost-server/pull/18347/files
Ticket Link
https://mattermost.atlassian.net/browse/MM-36687

Is this ready to be reviewed? Also, I cannot find the related server PR, can you point me to it?

@enahum do we need to get this in the servers? or this is nice to have?

@cpanato i think @anurag6713 requires this to be deployed, not sure about the timing of it, but yes this is required not only a nice to have


Bucket name length is being generated too large when adding domain and redirects

Bucket has a problem: expected length of bucket to be in the range (0 - 63)

is this directly when creating a bucket or is this from another component?

@danielstevenberger Fixed in 0.0.212. Feel free to re-open if issue persists.


BUG in select2.js  MultiSelect2

this.opts.initSelection(this.opts.element, function(data){
                    var ids=$.map(data, self.id);
                    self.setVal(ids);
                    self.updateSelection(data);
                    self.clearSearch();
                    if (triggerChange) {
                        self.triggerChange(this.buildChangeDetails(oldData, this.data()));
                    }
});

Line 2947:
In the line self.triggerChange(this.buildChangeDetails(oldData, this.data()));  this is undefined.
In the newer version of Select2 it's already fixed.

Thanks to reporting the issue. It will be fixed in coming release.

Fixed in 1.9 release. Thanks for reporting this!


cmd/govim: decide on best popup styles for various situations

We will likely want different types for different situations
For example, the hover popup menu popup will likely want to look quite different to an alert-style error popup
Should the hover popup have a border to make it stand out more?
All these sorts of questions are covered by this issue.

I like the config option to set border etc so far.

the hover popup menu popup will likely want to look quite different to an alert-style error popup

they might look same with different color imo

@varun06 - in your comment, please can you share the config options that look best for you? Perhaps with a quick screenshot?


Firefox: InputExample - needs double click to change cursor in input element

I have the feeling, FF is relying on global mouse events for selecting within the input element.
As IsolatedNodes stop the propagation of these events ultimatively the native behavior is prevented.
Chrome and Edge work as expected: stopPropagation does not break the native selection.
I suppose, we can't fix that without a more elaborated event handler. Shifting this to beta 5.


Commands do not yell in #yelling

Commands such as /weekisit do not yell in #yelling.

I've decided to comb through the code for a bit. I discovered that commands that output texts calls yelling_exemptor from yelling.py. I wonder if that's blocking the bot from yelling out commands.

Thanks for looking into this! I don't think that this is the issue, as yelling_exemptor just allows you to run commands with lowercase arguments. For example, /whatsdue has yelling_exemptor, so you don't get blocked when you search for whats due in csse1001 (note the lowercase). In contrast, /cowsay does not have the yelling_exemptor, so trying to run /cowsay hello will get blocked by the bot in #yelling (try it for yourself).
I don't blame you for being confused. I think the documentation for yelling_exemptor is lacking, both in the codebase and on the GitHub wiki. Given the complexity of yelling exemptor (in the sense that it is a decorator with also a wrapping function), this is a bit of a problem. I might try to write something up this weekend if no-one beats me to it.
Once again, thank you for having a look into this. If you want to have a go at making certain commands yell, I'd suggest looking haiku.py, specifically how it responds to haikus:
        if message.channel == discord.utils.get(
            self.bot.uqcs_server.channels, name=YELLING_CHANNEL_NAME
        ):
            await message.reply(f"Nice haiku:\n{haiku}".upper())
        else:
            await message.reply(f"Nice haiku:\n{haiku}")

Hopefully it should just be about going through all the interesting commands and doing something similar. Feel free to assign yourself to this issue if you want to have a crack.

Ah, not quite (yet another example of how the @yelling_exemptor is confusing and silly).
What it actually does is checks through every argument on the command it's attached to, and then if its a string, requires it to be UPPERCASE in the yelling channel. Effectively, ensures that someone can't /echo lower case text - they have to /echo UPPER CASE TEXT or else uqcsbot will still :disapproval: them.


Update Grafana AWS SDK dependencies

Requested by @robbierolin

@ryantxu e2e tests were failing when upgrading some of the frontend dependencies, so i limited this to the AWS requested go package updates


Failure to boostrap shutdown or evicted nodes

How to reproduce:
Use the following yaml to deploy a new cluster
apiVersion: opensearch.opster.io/v1
kind: OpenSearchCluster
metadata:
  name: doha-opsearch
  namespace: open-search

spec:
  general:
    serviceName: doha-dic-poc
    setVMMaxMapCount: true
    version: 2.2.1
    # pluginsList: ["opensearch-knn", "opensearch-ml", "opensearch-notifications", "opensearch-alerting"]
    # pluginsList: ["opensearch-alerting"]
  dashboards:
    enable: true
    version: 2.2.1
    replicas: 1
    resources:
      requests:
         memory: "512Mi"
         cpu: "200m"
      limits:
         memory: "512Mi"
         cpu: "200m"
  nodePools:
    - component: masters
      replicas: 3
      diskSize: "6Gi"
      jvm: -Xmx8g -Xms8g
      NodeSelector:
      resources:
         requests:
            memory: "8Gi"
            cpu: "2"
        #  limits:
        #     memory: "2Gi"
        #     cpu: "500m"
      roles:
        - "data"
        - "cluster_manager"

After successful deployment, manually terminate any of the master nodes.
The terminated node is re-provisioned as expected but stuck in unready state.
Digging into logs of this unready node reveals the following error:
`luster-manager not discovered or elected yet, an election requires a node with id [jP-5_H9nSEyqCcrTEuX3sg]z

Duplicate of: https://github.com/Opster/opensearch-k8s-operator/issues/266


Greenville Library System Events - Custom API

@ChristinaDRoberts mentioned seeing a library computer class posted.
The Greenville County Library System has a number of adult and kids classes / events, which we've never syndicated because there probably was no structured data or API.
However, there is now a custom API that's public and easy to figure out using web dev tools in the browser.
"Computer Classes" (event-type=12)
https://www.greenvillelibrary.org/api/v2/events?mode=calendar&group=1&date-start=2024-01-28&date-end=2024-03-02
"Computer Classes" (event-type=12) and "STEAM" (event-type=19)
https://www.greenvillelibrary.org/api/v2/events?event-type=**12+19**&mode=calendar&group=1&date-start=2024-01-28&date-end=2024-03-02
There are other filters, like "Location", which the API can filter.
They have a decent number of events and aren't historically the "HackGreenville" crowd, since it's more of a tech beginner (kids or adults), but we do have enough overlap into listing other STEAM and career changers orgs that it's probably worth consideration now that it looks like there's some custom structured data from their Drupal API.

greenville-library-openapi-spec.json
OpenAPI spec for the /api/v2/events endpoint, along with a couple of others.

Tagging with "suggestion" and putting on the list of future ideas to clean up the active issue queue.
https://github.com/orgs/hackgvl/projects/7


MAINT: update changelog via github-activity

@mmcky are you OK with this change in CHANGELOG style? It would be good if all of our projects used the same release workflow. If we migrate to github-activity across all projects, it will be easier to introduce some kind of action that let's us automate more of the release (e.g. like jupyter-releaser).

I think the general plan for EB repos (of my own devising, I should add) is to move to low-maintenance standardised tools. For us, that means GitHub activity.


fix: 🐛 table chart edit mode

https://metakeen.atlassian.net/browse/FEE-838

Codecov Report

Merging #336 (96c02ed) into develop (1d8be7e) will decrease coverage by 0.01%.
The diff coverage is 0.00%.

@@             Coverage Diff             @@
##           develop     #336      +/-   ##
===========================================
- Coverage    86.91%   86.90%   -0.02%
===========================================
  Files          554      554
  Lines         7123     7124       +1
  Branches       715      715
===========================================
  Hits          6191     6191
- Misses         845      846       +1
  Partials        87       87

Impacted Files
Coverage Δ

...idgetEditor/components/ChartEditor/ChartEditor.tsx
79.31% <0.00%> (-0.93%)
:arrow_down:

Continue to review full report at Codecov.

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


Failed to start nameserver on port 53

Hello, I have this error and I don't know how to fix it, something is already using my port 53? If yes how to see what is it and disable it?
Thank you!

Try running netstat -tunalp and it will tell you what process runs on what port.
In your case it is probably bind.


Support for older ASP.NET Core hosting models - IWebHost, IHostBuilder

I have just updated an existing ASP.NET Core app to .NET 8. I tried to add .NET Aspire Orchestrator support via the Visual Studio tooling and received this error:
Microsoft Visual Studio  Failed to insert code for project [ApiProject]. Cant find  a call to method(s) Build on type  Microsoft.AspNetCore.BuiIder.WebAppIicationBuiIder in the  program main.
After some digging I have concluded it is due to an older unsupported hosting model, IWebHost. I updated to a newer IHostBuilder, but still no luck. It looks like ASP.NET Aspire requires IHostApplicationBuilder.
I think this should be made clearer at least in the documentation. It would be good to have a note stating that you need to be using IHostApplicationBuilder not just .NET 8.
I would also consider making the error from the tooling a bit better. It is clear from the Extensions part of ServiceDefaults project that you need to use IHostApplicationBuilder, but when relying on tooling the error message doesn't help that much.

Is there an updated on this?  I too need IHostBuilder

I do too. Will check on this.

@varndellwagglebee and @Swellenator - what version of .net is the worker you're trying to orchestrate with aspire?


Uncaught TypeError: undefined is not a function

[Enter steps to reproduce below:]

...
...

Atom Version: 0.172.0
System: Mac OS X 10.10.2
Thrown From: autocomplete-plus package, v2.13.1
Stack Trace
Uncaught TypeError: undefined is not a function
At /Users/cwheeler/.atom/packages/autocomplete-plus/lib/suggestion-list-element.coffee:112

TypeError: undefined is not a function
  at autocomplete-suggestion-list.SuggestionListElement.render (/Users/cwheeler/.atom/packages/autocomplete-plus/lib/suggestion-list-element.coffee:112:16)
  at autocomplete-suggestion-list.SuggestionListElement.itemsChanged (/Users/cwheeler/.atom/packages/autocomplete-plus/lib/suggestion-list-element.coffee:107:21)
  at autocomplete-suggestion-list.SuggestionListElement.attachedCallback (/Users/cwheeler/.atom/packages/autocomplete-plus/lib/suggestion-list-element.coffee:54:6)
  at OverlayManager.module.exports.OverlayManager.renderOverlay (/Users/cwheeler/Downloads/Atom.app/Contents/Resources/app/src/overlay-manager.js:42:24)
  at OverlayManager.module.exports.OverlayManager.render (/Users/cwheeler/Downloads/Atom.app/Contents/Resources/app/src/overlay-manager.js:19:16)
  at [object Object].module.exports.React.createClass.componentDidUpdate (/Users/cwheeler/Downloads/Atom.app/Contents/Resources/app/src/lines-component.js:149:71)
  at CallbackQueue.mixInto.notifyAll (/Users/cwheeler/Downloads/Atom.app/Contents/Resources/app/node_modules/react-atom-fork/lib/CallbackQueue.js:75:22)
  at ReactReconcileTransaction.ON_DOM_READY_QUEUEING.close (/Users/cwheeler/Downloads/Atom.app/Contents/Resources/app/node_modules/react-atom-fork/lib/ReactReconcileTransaction.js:88:26)
  at ReactReconcileTransaction.Mixin.closeAll (/Users/cwheeler/Downloads/Atom.app/Contents/Resources/app/node_modules/react-atom-fork/lib/Transaction.js:214:42)
  at ReactReconcileTransaction.Mixin.perform (/Users/cwheeler/Downloads/Atom.app/Contents/Resources/app/node_modules/react-atom-fork/lib/Transaction.js:155:16)
  at ReactUpdatesFlushTransaction.Mixin.perform (/Users/cwheeler/Downloads/Atom.app/Contents/Resources/app/node_modules/react-atom-fork/lib/Transaction.js:141:20)
  at ReactUpdatesFlushTransaction.mixInto.perform (/Users/cwheeler/Downloads/Atom.app/Contents/Resources/app/node_modules/react-atom-fork/lib/ReactUpdates.js:98:38)
  at Object.flushBatchedUpdates (/Users/cwheeler/Downloads/Atom.app/Contents/Resources/app/node_modules/react-atom-fork/lib/ReactUpdates.js:176:19)
  at ReactDefaultBatchingStrategyTransaction.Mixin.closeAll (/Users/cwheeler/Downloads/Atom.app/Contents/Resources/app/node_modules/react-atom-fork/lib/Transaction.js:214:42)
  at ReactDefaultBatchingStrategyTransaction.Mixin.perform (/Users/cwheeler/Downloads/Atom.app/Contents/Resources/app/node_modules/react-atom-fork/lib/Transaction.js:155:16)
  at Object.ReactDefaultBatchingStrategy.batchedUpdates (/Users/cwheeler/Downloads/Atom.app/Contents/Resources/app/node_modules/react-atom-fork/lib/ReactDefaultBatchingStrategy.js:70:19)
  at Object.enqueueUpdate (/Users/cwheeler/Downloads/Atom.app/Contents/Resources/app/node_modules/react-atom-fork/lib/ReactUpdates.js:209:22)
  at [object Object].ReactCompositeComponentMixin.forceUpdate (/Users/cwheeler/Downloads/Atom.app/Contents/Resources/app/node_modules/react-atom-fork/lib/ReactCompositeComponent.js:1232:18)
  at /Users/cwheeler/Downloads/Atom.app/Contents/Resources/app/src/text-editor-component.js:313:28

Commands
     -1:24.2 editor:newline (atom-text-editor.editor.is-focused.autocomplete-active)
  3x -1:20.7 core:backspace (atom-text-editor.editor.is-focused.autocomplete-active)
     -1:19.5 command-palette:toggle (atom-text-editor.editor.is-focused.autocomplete-active)
  2x -1:16.5 core:move-down (atom-text-editor.editor.mini)
     -1:15.5 core:move-up (atom-text-editor.editor.mini)
     -1:15.3 core:confirm (atom-text-editor.editor.mini)
     -1:15.3 settings-view:install-packages-and-themes (atom-text-editor.editor.is-focused.autocomplete-active)
     -1:02.3 core:confirm (atom-text-editor.editor.mini)
     -0:22.2 window:update-available (atom-workspace.workspace.scrollbars-visible-when-scrolling.theme-atom-dark-syntax.theme-atom-dark-ui)
     -0:00.9 editor:select-to-first-character-of-line (atom-text-editor.editor.is-focused.autocomplete-active)
     -0:00.5 core:backspace (atom-text-editor.editor.is-focused.autocomplete-active)
     -0:00.0 core:save (atom-text-editor.editor.is-focused.autocomplete-active)

Config
{
  "core": {}
}

Installed Packages
# User
autocomplete-plus, v2.13.1

# Dev
No dev packages

/cc @atom/core

Please update to the latest version of atom.


Add link checker

This PR adds a link checker to the website's CI pipeline and fixes existing broken links.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign lucperkins
You can assign the PR to them by writing /assign @lucperkins in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

bbde8d3 Merge remote-tracking branch 'upstream/master' into lperkins/link-checker

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

LGTM label has been added.  Git tree hash: a49ea230600ab646873e2b48e819bbe29442f440

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: fntlnz
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [fntlnz]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Good job! Thanks @lucperkins

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: fntlnz, leodido
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [fntlnz,leodido]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM @lucperkins!
Needs a rebase on top of master, btw :)

/hold
This pr has conflicts and is in merge pool so its blocking other PRs.

Anyone please remove the hold once a rebase is done, it seems that there are conflicts

New changes are detected. LGTM label has been removed.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign fntlnz
You can assign the PR to them by writing /assign @fntlnz in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign fntlnz
You can assign the PR to them by writing /assign @fntlnz in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: 65ac2800519f3579ef4c3d8eda1b1f7ca7b651a4

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: leodido
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [leodido]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/hold cancel


Require treydock/gpg_key in metadata.json

The readme calls out dependencies on this, the apt module, epel, gentoo-portage, and chocolatey. These are all I believe implicitly called implicit dependencies. If we're going to promote implicit dependencies to real dependencies we should be consistent about that.

Yes... I saw those too. If that's the case, then this can be ignored. I half expected to get that response, but I wasn't sure if the jump to version 1.0.0 just missed it.

I'd be interested to see what others think about implicit dependencies.

I asked around about this earlier and Puppetlabs + others indicated that implicit dependencies should not be in the metadata.json.
By the way with Puppet 3.6 (I think) and higher, there is no need for treydock/gpg_key if there are also some key-related additions done to the yumrepo resource as well. But that is a potential PR for another day.

@juniorsysadmin of course implicit dependencies won't be in metadata.json, that is what makes them implicit dependencies. The question, in my mind, is if having implicit dependencies is a good idea.

The implicit dependencies are spelled out in the README, so...

Closing this, as the status quo seems to be okay with people. Feel free to re-open if you want to continue the conversation. @everestx thanks for the patch.

Np. Thanks for the feedback everyone.


Not using history api back method?

Is there any way to include the same tie in to the historyAPI .back() method? Similar to the way you've incorporated it into html5-history-anchor via adding the back attribute to an anchor tag?

I could add it but ideally I want to leave this as a pure history.pushState() element. The goal is to have something similar to a link like this that triggers a popstate instead of a hashchange.
back

The back functionality is easy to implement with an event handler as well. I think even this would work.
back

Or an event handler that calls history.back().

Thank you so much for the reply.  I love the implementation of going back via the 'back' attribute in html5-history-anchor. I may just replace pushtate-anchor with that so I can get the added functionality throughout the project. Cheers!


add Feature/menu for Revery_Native

add Menu module to Revery:

I don't know why but I can't call OCaml functions as callback
https://github.com/Et7f3/revery/blob/feature/menu/src/Native/menu_win32.c#L52
Maybe I don't use the right C function.
I have added printf to debug.
I'm new to interfacing C and OCaml.

I have seen that my dispatch cause the crash it seem that I don't use well reference 🤔 🤷♂ . I have used reason try to obtain this function bug maybe it is not the reason paradigm.
I have added lot of printf and it get printed until I access assocCallback^ and try to do pattern-matching.
I have not tryed with switch syntax but I have no hope.
@Akin909 I have changed the naming convention

I try to implement https://github.com/revery-ui/revery/issues/250 and https://github.com/revery-ui/revery/issues/322 (because it is the same system under windows)
my current progress:

[x] new Menu()
[ ] Menu.setApplicationMenu(menu) (partially)
[ ] Menu.getApplicationMenu()
[x] Menu.buildFromTemplate(template)
[ ] menu.popup(options)
[ ] menu.closePopup([browserWindow])
[ ] menu.append(menuItem)
[ ] menu.getMenuItemById(id)
[ ] menu.insert(pos, menuItem)
[ ] Event: 'menu-will-show'
[ ] Event: 'menu-will-close'
[ ] menu.items
[ ] Event: 'menu-created'

getApplicationMenu return application menu but when multi window will be avaible we could have getWindowMenu also on windows
we don't have setApplicationMenu but we have assignMenu that assign menu to a window

If someone want to explore tray here is a hint https://docs.microsoft.com/fr-fr/windows/desktop/api/shellapi/nf-shellapi-shell_notifyicona. Don't know if I should open a new pull request.

Thanks for the note about the tray, @Et7f3 ! We actually have another issue tracking that (https://github.com/revery-ui/revery/issues/322) - would be fine to have as a separate PR 👍

Thanks for all the work on this, @Et7f3 ! So cool to have that menu in our example app 😍
It looks like there are a few things we need:

[ ] Latest master needs to be merged (for the lock files - it might be easiest to just delete them and re-generate them - let me know if you need help)
[ ] Remove debug logs (The printfs like 'We have created menu')

Overall looks good to me though - great foundation for us to continue building on 👍 Some opportunities for additional PRs down the road based on our discussions:

JavaScript implementation for the API
Other related APIs (like the tray API or right-click menus)
Supporting other platforms (Cocoa, GTK, etc)

Very cool 😎

👀 right-click menus is already implemented see here https://github.com/revery-ui/revery/blob/4bfc981ecbddbe7267370a47efeb5d3406c833d1/examples/Examples.re#L236-L237 (Or I haven't understand)
thanks for glfwGetCursorPos tips: it is used here https://github.com/revery-ui/revery/pull/463/commits/77ba0c8eb4cde5334ab4caddb6ed54c41ed4715c
Very-last details I have to do:

[ ] keep window handle in the menuInfo and remove it when the menu is removed of the window
[ ] transform append so it redraw menu on the window if needed
[ ] insert
[ ] remove
[ ] produce rei file
[ ] implement all missing js primitives no-ops
[ ] add comment to explain what to change when multiple windows will be supported
[ ] erase printf
[ ] merge lock file (should be last thing)

This should be done by monday evening if I have time.
checkbox subitem for next PR
and we can change callback by using Hashtbl and manipulating callback value of each menu: next PR to protect it (so we can't erase useful callback)

I tried to merge and it seem I should better start from scratch. I was not aware of brisk-reconciler: So I have a lot of code to emulate that + the new ppx want Brisk_reconciler.element and non-generic 'a like the old one + incomplete Sdl2 binding: They are no more glfwGetCursorPos That was used in popup-menu.


Idea: Running in VS Code WebView

A sidebar button which open Icones app in new webview tab would be great 🤔

Transferred to vscode-iconify. Might be a nice-to-have feature.

https://github.com/afzalsayed96/vscode-icones


video compression

can we compress video through jcodec if yes then please provide step by step guidelines in case of android

Hi i am having a problem when trying to create a video from the images present in the external storage directory of my phone. Since the pictures have different dimensions, so the video comes out isn't satisfactory.
I am also having issues regarding the duration of the video file. How to set it programatically?
Video Link-
https://drive.google.com/file/d/0B5oBHXQjPljob2lVSWNFWHU0WUE/view?usp=sharing


regression: surelog allows to bit-select on real data type

TEST:
module top();
        real a = 0.5;
        wire [3:0] b;
        wire c;

        assign c = b[a];
endmodule

It was fixed in: https://github.com/chipsalliance/Surelog/issues/2325, but using current master, this test is passing OK and no error is reported.

I just ran that test from master:
[ERR:UH0714] tests/ScratchPad.sv:6:22: Can't use a real type as bit select "a".


"Export Notebook as SQL" button still enabled when using python kernel

Looks like the action is disabled correctly, but the styling doesn't change to reflect that i.e. getting grayed out and being unclickable.


Better errors

hey! i was looking to create a github action worker. i've made it through a few of the setup steps, but the error messages from the runner are really hard to decipher. is there a version i can run that has more verbose error messages/stack traces so i can understand what's wrong with my configuration?

also, i saw the medium post that was written about the release of this, are there any other resources that walk through setting up a github app + configuration for a runner using Cilicon?

Hi @AndrewSB, sorry for the late response!
Cilicon relies on Error's localizedDescription for displaying errors, which should provide a human readable error description to the user. It looks like SwiftJWT may not be implementing this correctly. I will have a look and hopefully fix it soon.
Since it's JWT related I'm almost certain that the pem key you're using is the problem. Could you try re-generating it?

The error description should be fixed by https://github.com/Kitura/Swift-JWT/pull/111

awesome! thanks @Marcocanc


automatic opt-out of opacity scale

Fixes #1308; adds automatic opt-out of opacity scale.
Fixes #1309; adds per-channel scale overrides for bin & group transform outputs.

What do you think, @fil? If you don’t think automatic opt-out of the opacity scale is a good idea, I could extract the fix for #1309 into a separate PR. I have mixed feelings about this because it feels like it’s more likely to get a false positive (false negative?) where numbers that happen to be in the interval [0, 1] are erroneously interpreted as literal opacities.

Could we get this for just "opacity" (in addition to "strokeOpacity" and "fillOpacity")?

good catch, @net! this is fixed now in main (issue #1570, merged PR #1571).

@Fil awesome!


ctxt.lyricTextColor is not heeded

I want to change the foreground color of all elements. I can change the colour of dividers (ctxt.dividerLineColor), neumes (ctxt.neumeLineColor) and staff lines (ctxt.staffLineColor), but the following three does not work:

ctxt.lyricTextColor;
ctxt.annotationTextColor;
ctxt.dropCapTextColor.

Is it a bug?

Yes, it's probably a bug.
I released this as an experimental project, but haven't done any work on it for about four years. You could try looking at some of the forks of the project and seeing if others have made more progress on it, and possibly improved rendering.

I see, @frmatthew. Thanks anyway for this awesome project. Could you archive the project or otherwise label it as non-maintained? :wink:

Well, I looked at the forks and as far as I see it right, the one made by @bbloomf has 200+ ahead commits, so he could help me out, however, he disabled the issue tracker his fork. @bbloomf, could you help me with this and #91? Thanks in advance! :pray:

@bbloomf, ctxt.lyricTextColor works as expected in your fork, however, the issue described in #91 does not.
Because of this, I’ll close this issue.


what is the version of tensorflow?

Thanks for your excellent work. But I have some trouble when try to reproduce your work, and I think it may due to the version of tensorflow and other package

2.0.0


When integrating react-native-fbsdk-next in IOS, App is opening with the blank screen

🐛 Bug Report
On integrating react-native-fbsdk-next in IOS, App is opening with the blank screen
Goal
Our Goal is to track App Installs from the facebook Ads.
To Reproduce
I followed below article to integrate the react-native-fbsdk-next.
https://www.vairix.com/tech-blog/react-native-facebook-sdk-integration.
npx yarn install react-native-fbsdk-next
npx pod-install
In Info.plist,
<key>CFBundleURLTypes</key>
<array>
  <dict>
	  <key>CFBundleURLSchemes</key>
	  <array>
		  <string>Acme</string> <!-- This line is added while integrating react-native-branch -->
		  <string>fb[our_fb_app_id]</string>
	  </array>
  </dict>
</array>

<key>LSApplicationQueriesSchemes</key>
<array>
  <string>fbapi</string>
  <string>fb-messenger-share-api</string>
</array>

<key>FacebookAppID</key>
<string>[our_fb_app_id]</string>
<key>FacebookDisplayName</key>
<string>Acme Corp</string>
<key>FacebookClientToken</key>
<string>[our_fb_client_id]</string>
<key>FacebookAutoLogAppEventsEnabled</key>
<true/>
<key>FacebookAdvertiserIDCollectionEnabled</key>
<true/>

Added the below lines in
AppDelegate.m
#import <FBSDKCoreKit/FBSDKCoreKit.h>

[[FBSDKApplicationDelegate sharedInstance] application:application
    didFinishLaunchingWithOptions:launchOptions];

//- (BOOL)application:(UIApplication *)application openURL:(NSURL *)url
- (BOOL)application:(UIApplication *)app openURL:(NSURL *)url options:(NSDictionary<UIApplicationOpenURLOptionsKey,id> *)options

  sourceApplication:(NSString *)sourceApplication annotation:(id)annotation
{
//  return [RCTLinkingManager application:application openURL:url
//                      sourceApplication:sourceApplication annotation:annotation];

  if ([[FBSDKApplicationDelegate sharedInstance] application:app openURL:url options:options]) {
    return YES;
  }
  if ([RNBranch application:app openURL:url options:options])  {
    return YES;
  }
  return NO;

  //return [RNBranch application:app openURL:url options:options];

}

I was trying to run the app from xCode in my personal IPhone.(iPhone 12 Pro - OS version - 15.1.1)
The below is the xCode Log
2021-12-24 20:37:18.220024+0530 Acme[12866:1408261] You've implemented -[<UIApplicationDelegate> application:didReceiveRemoteNotification:fetchCompletionHandler:], but you still need to add "remote-notification" to the list of your supported UIBackgroundModes in your Info.plist.
2021-12-24 20:37:18.296955+0530 Acme[12866:1408466] 6.34.0 - [Firebase/Core][I-COR000003] The default Firebase app has not yet been configured. Add `[FIRApp configure];` (`FirebaseApp.configure()` in Swift) to your application initialization. Read more: https://goo.gl/ctyzm8.
2021-12-24 20:37:18.344054+0530 Acme[12866:1408261] File Path /private/var/containers/Bundle/Application/FFD49476-B011-447D-BC34-4B947CEAA294/Acme.app/GoogleService-Info_Dev.plist
2021-12-24 20:37:18.353124+0530 Acme[12866:1408472] 6.34.0 - [Firebase/Analytics][I-ACS025020] Analytics requires Google App ID from GoogleService-Info.plist. Your data may be lost. Google App ID has been changed. Original, new ID: 1:943915815926:ios:3c0b000b6199e0b905add7, 1:732520158131:ios:62300deac1358ff41eb1c6
2021-12-24 20:37:18.354046+0530 Acme[12866:1408472] 6.34.0 - [Firebase/Analytics][I-ACS023007] Analytics v.60900000 started
2021-12-24 20:37:18.354129+0530 Acme[12866:1408472] 6.34.0 - [Firebase/Analytics][I-ACS023008] To enable debug logging set the following application argument: -FIRAnalyticsDebugEnabled (see http://goo.gl/RfcP7r)
2021-12-24 20:37:18.360495+0530 Acme[12866:1408466] 6.34.0 - [Firebase/Messaging][I-FCM001000] FIRMessaging Remote Notifications proxy enabled, will swizzle remote notification receiver handlers. If you'd prefer to manually integrate Firebase Messaging, add "FirebaseAppDelegateProxyEnabled" to your Info.plist, and set it to NO. Follow the instructions at:
https://firebase.google.com/docs/cloud-messaging/ios/client#method_swizzling_in_firebase_messaging
to ensure proper integration.
2021-12-24 20:37:18.360979+0530 Acme[12866:1408261] [Firebase/Crashlytics] Version 4.6.2
2021-12-24 20:37:18.458822+0530 Acme[12866:1408261] RELEASE
2021-12-24 20:37:18.461076+0530 Acme[12866:1408261] RELEASE
2021-12-24 20:37:18.462652+0530 Acme[12866:1408261] [native] Running application acme_app ({
    initialProps =     {
    };
    rootTag = 1;
})
2021-12-24 20:37:18.484869+0530 Acme[12866:1408261] -canOpenURL: failed for URL: "activator://package/com.example.package" - error: "This app is not allowed to query for scheme activator"
2021-12-24 20:37:18.485633+0530 Acme[12866:1408261] -canOpenURL: failed for URL: "cydia://package/com.example.package" - error: "This app is not allowed to query for scheme cydia"
2021-12-24 20:37:18.485885+0530 Acme[12866:1408261] -canOpenURL: failed for URL: "filza://package/com.example.package" - error: "This app is not allowed to query for scheme filza"
2021-12-24 20:37:18.486640+0530 Acme[12866:1408261] -canOpenURL: failed for URL: "sileo://package/com.example.package" - error: "This app is not allowed to query for scheme sileo"
2021-12-24 20:37:18.487108+0530 Acme[12866:1408261] -canOpenURL: failed for URL: "undecimus://package/com.example.package" - error: "This app is not allowed to query for scheme undecimus"
2021-12-24 20:37:18.487373+0530 Acme[12866:1408261] -canOpenURL: failed for URL: "zbra://package/com.example.package" - error: "This app is not allowed to query for scheme zbra"
2021-12-24 20:37:18.498135+0530 Acme[12866:1408261] -canOpenURL: failed for URL: "activator://package/com.example.package" - error: "This app is not allowed to query for scheme activator"
2021-12-24 20:37:18.498400+0530 Acme[12866:1408261] -canOpenURL: failed for URL: "cydia://package/com.example.package" - error: "This app is not allowed to query for scheme cydia"
2021-12-24 20:37:18.498616+0530 Acme[12866:1408261] -canOpenURL: failed for URL: "filza://package/com.example.package" - error: "This app is not allowed to query for scheme filza"
2021-12-24 20:37:18.498818+0530 Acme[12866:1408261] -canOpenURL: failed for URL: "sileo://package/com.example.package" - error: "This app is not allowed to query for scheme sileo"
2021-12-24 20:37:18.499053+0530 Acme[12866:1408261] -canOpenURL: failed for URL: "undecimus://package/com.example.package" - error: "This app is not allowed to query for scheme undecimus"
2021-12-24 20:37:18.499276+0530 Acme[12866:1408261] -canOpenURL: failed for URL: "zbra://package/com.example.package" - error: "This app is not allowed to query for scheme zbra"
2021-12-24 20:37:18.507965+0530 Acme[12866:1408261] -canOpenURL: failed for URL: "activator://package/com.example.package" - error: "This app is not allowed to query for scheme activator"
2021-12-24 20:37:18.508171+0530 Acme[12866:1408261] -canOpenURL: failed for URL: "cydia://package/com.example.package" - error: "This app is not allowed to query for scheme cydia"
2021-12-24 20:37:18.508376+0530 Acme[12866:1408261] -canOpenURL: failed for URL: "filza://package/com.example.package" - error: "This app is not allowed to query for scheme filza"
2021-12-24 20:37:18.508566+0530 Acme[12866:1408261] -canOpenURL: failed for URL: "sileo://package/com.example.package" - error: "This app is not allowed to query for scheme sileo"
2021-12-24 20:37:18.508767+0530 Acme[12866:1408261] -canOpenURL: failed for URL: "undecimus://package/com.example.package" - error: "This app is not allowed to query for scheme undecimus"
2021-12-24 20:37:18.508958+0530 Acme[12866:1408261] -canOpenURL: failed for URL: "zbra://package/com.example.package" - error: "This app is not allowed to query for scheme zbra"
2021-12-24 20:37:18.510421+0530 Acme[12866:1408473] 6.34.0 - [Firebase/Analytics][I-ACS800023] No pending snapshot to activate. SDK name: app_measurement
2021-12-24 20:37:18.521650+0530 Acme[12866:1408473] [Client] Updating selectors after delegate addition failed with: Error Domain=NSCocoaErrorDomain Code=4099 "The connection to service with pid 93 named com.apple.commcenter.coretelephony.xpc was invalidated from this process." UserInfo={NSDebugDescription=The connection to service with pid 93 named com.apple.commcenter.coretelephony.xpc was invalidated from this process.}
[VGSCollectSDK -  Final URL to validate custom hostname: https://js.verygoodvault.com/collect-configs.x.txt - logLevel: info]
[VGSCollectSDK -  Final URL to validate custom hostname: https://js.verygoodvault.com/collect-configs.x.txt - logLevel: info]
2021-12-24 20:37:18.528799+0530 Acme[12866:1408261] -canOpenURL: failed for URL: "activator://package/com.example.package" - error: "This app is not allowed to query for scheme activator"
2021-12-24 20:37:18.529059+0530 Acme[12866:1408261] -canOpenURL: failed for URL: "cydia://package/com.example.package" - error: "This app is not allowed to query for scheme cydia"
2021-12-24 20:37:18.529330+0530 Acme[12866:1408261] -canOpenURL: failed for URL: "filza://package/com.example.package" - error: "This app is not allowed to query for scheme filza"
2021-12-24 20:37:18.529566+0530 Acme[12866:1408261] -canOpenURL: failed for URL: "sileo://package/com.example.package" - error: "This app is not allowed to query for scheme sileo"
2021-12-24 20:37:18.529773+0530 Acme[12866:1408261] -canOpenURL: failed for URL: "undecimus://package/com.example.package" - error: "This app is not allowed to query for scheme undecimus"
2021-12-24 20:37:18.530064+0530 Acme[12866:1408261] -canOpenURL: failed for URL: "zbra://package/com.example.package" - error: "This app is not allowed to query for scheme zbra"
2021-12-24 20:37:18.540761+0530 Acme[12866:1408261] -canOpenURL: failed for URL: "activator://package/com.example.package" - error: "This app is not allowed to query for scheme activator"
2021-12-24 20:37:18.542486+0530 Acme[12866:1408261] -canOpenURL: failed for URL: "cydia://package/com.example.package" - error: "This app is not allowed to query for scheme cydia"
2021-12-24 20:37:18.545125+0530 Acme[12866:1408261] -canOpenURL: failed for URL: "filza://package/com.example.package" - error: "This app is not allowed to query for scheme filza"
2021-12-24 20:37:18.545350+0530 Acme[12866:1408261] -canOpenURL: failed for URL: "sileo://package/com.example.package" - error: "This app is not allowed to query for scheme sileo"
2021-12-24 20:37:18.545536+0530 Acme[12866:1408261] -canOpenURL: failed for URL: "undecimus://package/com.example.package" - error: "This app is not allowed to query for scheme undecimus"
2021-12-24 20:37:18.545715+0530 Acme[12866:1408261] -canOpenURL: failed for URL: "zbra://package/com.example.package" - error: "This app is not allowed to query for scheme zbra"
2021-12-24 20:37:18.554901+0530 Acme[12866:1408261] -canOpenURL: failed for URL: "activator://package/com.example.package" - error: "This app is not allowed to query for scheme activator"
2021-12-24 20:37:18.555142+0530 Acme[12866:1408261] -canOpenURL: failed for URL: "cydia://package/com.example.package" - error: "This app is not allowed to query for scheme cydia"
2021-12-24 20:37:18.555415+0530 Acme[12866:1408261] -canOpenURL: failed for URL: "filza://package/com.example.package" - error: "This app is not allowed to query for scheme filza"
2021-12-24 20:37:18.555604+0530 Acme[12866:1408261] -canOpenURL: failed for URL: "sileo://package/com.example.package" - error: "This app is not allowed to query for scheme sileo"
2021-12-24 20:37:18.555912+0530 Acme[12866:1408261] -canOpenURL: failed for URL: "undecimus://package/com.example.package" - error: "This app is not allowed to query for scheme undecimus"
2021-12-24 20:37:18.556148+0530 Acme[12866:1408261] -canOpenURL: failed for URL: "zbra://package/com.example.package" - error: "This app is not allowed to query for scheme zbra"
[VGSCollectSDK -  Final URL to validate custom hostname: https://js.verygoodvault.com/collect-configs.x.txt - logLevel: info]
2021-12-24 20:37:18.571242+0530 Acme[12866:1408462] [Client] Updating selectors after delegate addition failed with: Error Domain=NSCocoaErrorDomain Code=4099 "The connection to service with pid 93 named com.apple.commcenter.coretelephony.xpc was invalidated from this process." UserInfo={NSDebugDescription=The connection to service with pid 93 named com.apple.commcenter.coretelephony.xpc was invalidated from this process.}
2021-12-24 20:37:18.610731+0530 Acme[12866:1408462] [assertion] Error acquiring assertion: <Error Domain=RBSServiceErrorDomain Code=1 "target is not running or doesn't have entitlement com.apple.runningboard.assertions.webkit" UserInfo={NSLocalizedFailureReason=target is not running or doesn't have entitlement com.apple.runningboard.assertions.webkit}>
2021-12-24 20:37:18.610840+0530 Acme[12866:1408462] [ProcessSuspension] 0x10ebf9980 - ProcessAssertion: Failed to acquire RBS assertion 'ConnectionTerminationWatchdog' for process with PID=12869, error: Error Domain=RBSServiceErrorDomain Code=1 "target is not running or doesn't have entitlement com.apple.runningboard.assertions.webkit" UserInfo={NSLocalizedFailureReason=target is not running or doesn't have entitlement com.apple.runningboard.assertions.webkit}
2021-12-24 20:37:18.624929+0530 Acme[12866:1408459] [general] *** -[NSKeyedUnarchiver validateAllowedClass:forKey:] allowed unarchiving safe plist type ''NSString' (0x1db07f6e8) [/System/Library/Frameworks/Foundation.framework]' for key 'NS.keys', even though it was not explicitly included in the client allowed classes set: '{(
    "'NSDate' (0x1db074ac0) [/System/Library/Frameworks/CoreFoundation.framework]",
    "'NSDictionary' (0x1db074c28) [/System/Library/Frameworks/CoreFoundation.framework]"
)}'. This will be disallowed in the future.
2021-12-24 20:37:18.641394+0530 Acme[12866:1408459] [general] *** -[NSKeyedUnarchiver validateAllowedClass:forKey:] allowed unarchiving safe plist type ''NSString' (0x1db07f6e8) [/System/Library/Frameworks/Foundation.framework]' for key 'NS.keys', even though it was not explicitly included in the client allowed classes set: '{(
    "'NSDate' (0x1db074ac0) [/System/Library/Frameworks/CoreFoundation.framework]",
    "'NSDictionary' (0x1db074c28) [/System/Library/Frameworks/CoreFoundation.framework]"
)}'. This will be disallowed in the future.
2021-12-24 20:37:18.662511+0530 Acme[12866:1408460] 6.34.0 - [Firebase/Analytics][I-ACS023012] Analytics collection enabled
2021-12-24 20:37:18.662620+0530 Acme[12866:1408460] 6.34.0 - [Firebase/Analytics][I-ACS023220] Analytics screen reporting is enabled. Call +[FIRAnalytics logEventWithName:FIREventScreenView parameters:] to log a screen view event. To disable automatic screen reporting, set the flag FirebaseAutomaticScreenReportingEnabled to NO (boolean) in the Info.plist
2021-12-24 20:37:18.707179+0530 Acme[12866:1408484] [native] Unbalanced calls start/end for tag 12
2021-12-24 20:37:18.712908+0530 Acme[12866:1408485] [native] Unbalanced calls start/end for tag 12
2021-12-24 20:37:18.732428+0530 Acme[12866:1408464] Attribution returned an error: Error Domain=ADClientErrorDomain Code=1 "The app is not authorized for ad tracking" UserInfo={NSLocalizedDescription=The app is not authorized for ad tracking}
2021-12-24 20:37:18.732968+0530 Acme[12866:1408464] 6.34.0 - [Firebase/Analytics][I-ACS032010] Cannot send request for Search Ad campaign attribution. Error: Error Domain=ADClientErrorDomain Code=1 "The app is not authorized for ad tracking" UserInfo={NSLocalizedDescription=The app is not authorized for ad tracking}
2021-12-24 20:37:18.746016+0530 Acme[12866:1408485] [native] Unbalanced calls start/end for tag 12
2021-12-24 20:37:18.990618+0530 Acme[12866:1408463] 6.34.0 - [Firebase/Analytics][I-ACS023012] Analytics collection enabled
2021-12-24 20:37:18.990699+0530 Acme[12866:1408463] 6.34.0 - [Firebase/Analytics][I-ACS023220] Analytics screen reporting is enabled. Call +[FIRAnalytics logEventWithName:FIREventScreenView parameters:] to log a screen view event. To disable automatic screen reporting, set the flag FirebaseAutomaticScreenReportingEnabled to NO (boolean) in the Info.plist
2021-12-24 20:37:19.021721+0530 Acme[12866:1408459] 6.34.0 - [Firebase/Analytics][I-ACS023012] Analytics collection enabled
2021-12-24 20:37:19.021816+0530 Acme[12866:1408459] 6.34.0 - [Firebase/Analytics][I-ACS023220] Analytics screen reporting is enabled. Call +[FIRAnalytics logEventWithName:FIREventScreenView parameters:] to log a screen view event. To disable automatic screen reporting, set the flag FirebaseAutomaticScreenReportingEnabled to NO (boolean) in the Info.plist
2021-12-24 20:37:19.028500+0530 Acme[12866:1408485] [native] Unbalanced calls start/end for tag 1
2021-12-24 20:37:19.076199+0530 Acme[12866:1408451] [native] Manifest does not exist - creating a new one.

(null)
2021-12-24 20:37:19.156547+0530 Acme[12866:1408261] [native] [GESTURE HANDLER] Initialize gesture handler for root view <RCTRootContentView: 0x105f52a70; reactTag: 1; frame = (0 0; 390 844); gestureRecognizers = <NSArray: 0x2827c3b40>; layer = <CALayer: 0x282905220>>
2021-12-24 20:37:19.212159+0530 Acme[12866:1408261] [native] Invalidating <RCTCxxBridge: 0x105f51d50> (parent: (null), executor: (null))
2021-12-24 20:37:19.274172+0530 Acme[12866:1408464] [assertion] Error acquiring assertion: <Error Domain=RBSServiceErrorDomain Code=1 "target is not running or doesn't have entitlement com.apple.runningboard.assertions.webkit" UserInfo={NSLocalizedFailureReason=target is not running or doesn't have entitlement com.apple.runningboard.assertions.webkit}>
2021-12-24 20:37:19.274230+0530 Acme[12866:1408464] [ProcessSuspension] 0x10ebf9aa0 - ProcessAssertion: Failed to acquire RBS assertion 'ConnectionTerminationWatchdog' for process with PID=12868, error: Error Domain=RBSServiceErrorDomain Code=1 "target is not running or doesn't have entitlement com.apple.runningboard.assertions.webkit" UserInfo={NSLocalizedFailureReason=target is not running or doesn't have entitlement com.apple.runningboard.assertions.webkit}
2021-12-24 20:37:19.275903+0530 Acme[12866:1408459] [general] *** -[NSKeyedUnarchiver validateAllowedClass:forKey:] allowed unarchiving safe plist type ''NSString' (0x1db07f6e8) [/System/Library/Frameworks/Foundation.framework]' for key 'NS.keys', even though it was not explicitly included in the client allowed classes set: '{(
    "'NSDate' (0x1db074ac0) [/System/Library/Frameworks/CoreFoundation.framework]",
    "'NSDictionary' (0x1db074c28) [/System/Library/Frameworks/CoreFoundation.framework]"
)}'. This will be disallowed in the future.

Expected Behavior
App should load properly and work as expected. And be able to track the App Installs from Facebook Ads.
Environment
"react-native": "0.63.2",
Xcode version 13.0
SDK version react-native-fbsdk-next - 6.1.1

Try this instead in your AppDelegate.m
initialize
- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions
{
  [[FBSDKApplicationDelegate sharedInstance] application:application didFinishLaunchingWithOptions:launchOptions];

  // ... your other code
}

handle universal links
- (BOOL)application:(UIApplication *)application
            openURL:(NSURL *)url
            options:(NSDictionary<UIApplicationOpenURLOptionsKey,id> *)options
{
  // https://developers.facebook.com/docs/ios/getting-started/#app-delegate
  BOOL handlFacebook = [[FBSDKApplicationDelegate sharedInstance] application:application openURL:url options:options];
  BOOL handleLinkingManager = [RCTLinkingManager application:application openURL:url options:options];

  return handlFacebook || handleLinkingManager;
}

Thanks for the reply @rnike
.
No Luck with the above change. Same issue

I'm curious why you have links prefix with cydia, filza, undecimus ... , those looks like jailbreak stuff for me, perhaps you can try something described in this post


FW-5588: Add hostname and ASN lists

Description
This adds support for Hostname and ASN lists
Has your change been tested?
Integration tests were written to ensure the requests are parsed successfully.
Screenshots (if appropriate):
Types of changes
What sort of change does your code introduce/modify?

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.
[x] This change is using publicly documented in cloudflare/api-schemas
and relies on stable APIs.

Codecov Report

Merging #1288 (656b03b) into master (62eaa9a) will increase coverage by 0.00%.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1288   +/-   ##
=======================================
  Coverage   49.06%   49.07%
=======================================
  Files         134      134
  Lines       13066    13066
=======================================
+ Hits         6411     6412    +1
+ Misses       5155     5154    -1
  Partials     1500     1500

Impacted Files
Coverage Δ

list.go
25.00% <ø> (ø)

... and 1 file with indirect coverage changes


SIMSBIOHUB-552: Migrate existing wldtaxonomic_units_id values to their respective ITIS TSN

Links to Jira Tickets

https://apps.nrs.gov.bc.ca/int/jira/browse/SIMSBIOHUB-553

Description of Changes

Migrates existing wldtaxonomic_units_id values to their respective ITIS TSN
Adds indexes to the survey_observation and study_species tablese

Testing Notes

You can see the database with sample wldtaxonomic_units_id values:

const insertSurveyObservationData = (surveyId: number, count: number) => {
  // The array of  wldtaxonomic_units_ids that are actively being used in prod:
  const testValue = [
    2012, 2013, 828, 2019, 1594, 1718, 2037, 2062, 2068, 2065, 2070, 2069, 23918, 23922, 23920, 35369, 35370, 28516
  ][Math.floor(Math.random() * 18)];

  return `
  INSERT INTO survey_observation
  (
    survey_id,
    wldtaxonomic_units_id,
    ...
  )
  VALUES
  (
    ${surveyId},
    ${testValue},
    ...
`;
}

... and you may want to do the same for study_species.

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

Project coverage is 72.64%. Comparing base (31b036d) to head (17900c0).

Additional details and impacted files
@@             Coverage Diff             @@
##              dev    #1254       +/-   ##
===========================================
+ Coverage   52.38%   72.64%   +20.26%
===========================================
  Files         578      216      -362
  Lines       17212     8791     -8421
  Branches     2678     1254     -1424
===========================================
- Hits         9016     6386     -2630
+ Misses       7589     2049     -5540
+ Partials      607      356      -251

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


Question: mimic release support

Hi everyone. First of all I want to thank you for this useful package.
When I try  to use it with mimic release, I get this error: Operation not supported. I want to know following things:

I use librados-dev 10.x.y from debian stretch repositories. As I can understand it is not suitable, right? How I should install librados for mimic release?
Does this package support mimic release? If not - which ceph release is the latest suitable for this package?

Hi nuqz. When you see operation not supported, is it only when running the tests? I've seen this too running tests on Mimic, but it was a minor issue that shouldn't affect applications using go-ceph. I have a large pending update that works with Mimic (and fixes those errors), and I'll be merging that soon.
As for compatibility, I think you should be fine with the 10.x.y library. The current approach I'm taking is to get all the outstanding issues with the current code base, which should work with Jewel to Mimic, but has some deprecation warnings with newer libraries. Once that is solid, we'll tag it or create a branch for fixes.
Then move forward with breaking changes that would be nice to have.

@noahdesu No, not only when running tests. I have a program, which works fine with jewel release. I have deployed mimic release using Docker (host network). Then I have updated go-ceph package and built application. Now it throws the error: operation not supported.
The program is very simple:

Create connection instance with rados.NewConn(), read default config file conn.ReadDefaultConfigFile(), connect conn.Connect();
Write/append key(s) to existing pool: create new IO context, ioctx.WriteFull(k, v)/ioctx.Append(k, v), destroy context;
Destroy connection conn.Shutdown().

Is there anything I should change?

Hi @nuqz thanks for this detailed update. just a quick clarification: are you running jewel / mimic mixed (e.g. jewel client mimic server?). it was a little unclear the relation between how you were using jewel and mimic at the beginning of the post.

@noahdesu, sorry for a huge delay. I'm not sure what is the client in this case.
My first cluster was powered by Jewel version inside the virtual machine (VirtualBox). I used librados-dev from Debian Stretch repository and the latest version (downloaded it near March-April this year) of go-ceph.
After that, when I had new hardware, I deployed a cluster powered by the Mimic release, imported my pool data and updated the go-ceph package. The librados-dev library has not been updated.
The program code remained the same.

Hi @nuqz . The go-ceph project now has CI setup for mimic and luminous so we should see any issue now that arise between the two. If you are still running into any mimic issues I'd love to get unit tests created for those issues.
Regarding performance, that is a good question. I haven't invested this at all. An io context is thread safe, and in general can be shared by many threads running in the same application assuming they are interacting with the same pool. However, I haven't thought much about how goroutines will effect correctness since they aren't real threads. This is something we need to look at!


Add autoPan option to ol.Overlay

This PR adds an autoPan option to ol.Overlay (active by default). When calling overlay.setPosition(..),  the map will be panned such that the overlay is entirely visible in the current viewport.
The panning animation can be customized by setting the option autoPanAnimation (olx.animation.PanOptions) and the margin between the overlay and the map borders can be set with autoPanMargin.
Note: This implementation does not work with Bootstrap Popovers used in the Overlay example. There is a problem with getting the real width/height of the overlay element and also the positioning logic of Popovers seems to conflict with the logic of the ol overlay.
Closes #928
cc @fredj
@walkermatt Your implementation saved me some time, thanks! :)

I've added a number of comments. Otherwise looks good to me.

Thanks for your comments, Eric. I updated the branch.

LGTM. Please merge.


Port 80/443 and tls error, {"time":"2016-09-30T15:49:30-03:00","level":"FATAL","prefix":"armor","file":"asm_amd64.s","line":"2086","message":"open : no such file or directory"}

Hey! This looks super cool, and I can get it to work fine with non privileged ports, but get fails when trying to use the LetsEncrypt support. I tried to use a slightly modded config from your README.md, but admittedly I may be trying stuff I shouldnt?
I tried to run the following config using
$ sudo armor -c /tmp/armor.json
and get this fail:
{"time":"2016-09-30T15:53:26-03:00","level":"FATAL","prefix":"armor","file":"asm_amd64.s","line":"2086","message":"open : no such file or directory"}

Here's my config:
{
  "address": ":443",
  "tls": {
    "auto": true
  },
  "plugins": {
    "remove-trailing-slash": {
      "redirect_code": 301
    },
    "logger": {},
    "gzip": {}
  },
  "hosts": {
    "super.ez.com": {
      "plugins": {
          "cors": {},
          "proxy": {
              "targets": [{
                  "url": "http://api.ls"
              }]
          }
      }
    },
    "test.ez.com": {
      "plugins": {
        "non-www-redirect": {},
        "static": {
          "root": ".",
          "html5": true
        }
      }
    },
    "how.com": {
      "plugins": {
        "static": {
          "root": "."
        }
      }
    }
  }
}

Other than this, I think it'd be a good idea to:

mention that sudo is required to run this on ports 80/443
not use a privileged port in your example in the README (ie use 8080)
use "/var/www/html" as your example root html folder
supply lots of example configs
have at least one simple LetEncrypt example that describes the setup required, if any!

Thanks a ton again!

I also have trouble with setup letEncrypt auto mode, which show the same error.

address is for http. For auto TLS you don't need to specify any address, as it always has to be 443. Let me know how that goes.

@bradparks you need to specify a cache_file to get rid of your error.
try:
{
  "tls": {
    "auto": true,
    "cache_file": ".armor"
  },
  ...

also drop "address": ":443" as it specifies port 443 for your http listener which will then clash with the https listener (because it always listens on 443 as @vishr mentioned)

Need to update examples on site.


ddoc for find-indexes must differ from design document for map/reduce views

I discover that find() returns {} when the index is stored in the same design document (e.g _design/my_indexes) for map/reduce views. When ddoc (e.g. indexes) refers to another _design document (like _design/indexes) than everything works well.
I am not sure if this is specified somewhere in the documentation. (If I missed this, than my apologises in advance.) Nor if this is known / designed behaviour.
Either this is known behaviour and should be documented explicitly, and/or an proper error should be provided. Or it is a bug to be solved, some day :-)

I just read your page about "secondary indexes" again and noticed the strong advise to create one view per ddoc. If I follow your advice, this issue (#115) will not occur :-)

Thanks @cornelisse I will look and see if we can at least add a warning about this.

This issue was moved to pouchdb/pouchdb#6284


Can't run without CUDA

Comfyui has IPEX pytorch version. Many models are running without CUDA. Please make it happen.

+1


Mirror listener retry

Problem
The mirror listener doesn't appear to be setup to retry in the event of a loss of communication with the Mirror Node
Solution
If the listener is subscribing, it should handle an error() event and re-subscribe from the  consensus timestamp of the last message (+1 nano) it received. This will ensure no notifications are missed.
Alternatives
There are no alternatives that would ensure no loss of data.

If this is related to the appnet example, it actually does restart listeners on the event of communication loss (see AppnetServer methods that start topic listeners) immediately after the error occurs.  Listeners are restarted with crash time -10 seconds.
Though probably a better way, is as you described - to use the timestamp of the last message received a restart time.

This ticket should be closed as the proposed solution was already implemented earlier. for more info vist
https://github.com/hashgraph/did-sdk-java/commit/112270a12d7244367a0524833d9c635f3ebcbd1a


New Singleton enum for PatternMatchSingleton node

Summary
This PR adds a new Singleton enum for the PatternMatchSingleton node.
Earlier the node was using the Constant enum but the value for this pattern can only be either None, True or False. With the coming PR to remove the Constant, this node required a new type to fill in.
This also has the benefit of narrowing the type down to only the possible values for the node as evident by the removal of unreachable.
Test Plan
Update the AST snapshots and run cargo test.

It also seem to make sense from a technical perspective (I didn't know that) because None, True, and False are indeed all singleton values 🤯

Ah yes, I should've written that in the PR description.

The one alternative I could think of is a KeywordLiteral.

This might be confusing as other keywords are not part of it.


Generating self signing ssl cert gives chmod error

Hi there.
When I try to run "dokku certs:generate APP DOMAIN" I get the openSSL questions and all seems fine. Yet it finished with this statement:
-----> Installing certificate and key...
chmod: cannot access ‘/home/dokku/everseller/tls/server.csr’: No such file or directory
When I run "dokku ps:restartall" to restart my app I see these lines:
-----> No matching configured domains for everseller found in SSL certificate. Your app will show as insecure in a browser if accessed via SSL -> this is ok
-----> Please add appropriate domains via the dokku domains command -> my app has the appropriate domain installed.
-----> Creating https nginx.conf -> So I guess some SSL stuff is getting configured?
The app restarts successfully and serves my app fine without ssl. But when requesting the app over https the connections get refused.
What would be a solution? :-)
I did not have this issue under 0.4.4.
Thanks!

Seems #1708 caused this. Might be worth backing out that change somehow.
@petewest since you wanted the original change, what do you think the permissions should be?

The chmod error is because the .csr is generated in $TMP_WORK_DIR and not copied/moved to $APP_SSL_PATH so it really doesn't exist to chmod.  Has it copied the .key & .crt to the tls folder?
If not, you could 770 $APP_SSL_PATH, and 660 the files so they can be overwritten or change the cp , mv and chmod to use sudo.

It should be copied over here: https://github.com/progrium/dokku/pull/1708/files#diff-226056642bb78caf7bee818b3ea48ce3R96.

Thanks for the quick response :-). I am new to unix/bash. @petewest, could you please describe your solution in beginner terms so I can apply it?

@josegonzalez that line moves the .crt & .key, but https://github.com/progrium/dokku/pull/1708/files#diff-226056642bb78caf7bee818b3ea48ce3R98 also tries to change a .csr which I think is only in $TMP_WORK_DIR
@Corstiaan84 it should be possible to get yours up by running the following:
sudo touch /home/dokku/everseller/tls/server.csr
sudo chown dokku:dokku /home/dokku/testapp/tls/server.csr
dokku certs:generate APP DOMAIN

This should create the file that's missing and causing an error, then re-generate the certs and set everything back up again (I think...)

Oh gotcha, that makes sense. Mind making a PR to fix that?

@petewest thanks :-).
Removed the cert to start with clean slate. Ran "sudo touch /home/dokku/everseller/tls/server.csr" and got this message:
"touch: cannot touch ‘/home/dokku/everseller/tls/server.csr’: No such file or directory"
Ideas? :-)

@Corstiaan84 certs:remove deletes that tls folder, you can recreate it (and the temporary fix):
sudo mkdir /home/dokku/everseller/tls/
sudo touch /home/dokku/everseller/tls/server.csr
sudo chown -R dokku:dokku /home/dokku/everseller/tls

Then run your certs:generate as before.
@josegonzalez I'll create a test environment to see if I can recreate the original issue so I can make sure this is all that's required to fix it.

@petewest Ok, that worked thanks :-). No errors.
However, the https urls still gets refused. After the succesfull restart of the app, I see these two lines at the end:
=====> Application deployed:
http://app-domain.com
http://app-domain.com
Shouldn't one of these two read httpS://app-domain.com?

Fixed with #1732


ADMIN: Unban User -> PHP Error is shown when method for unbanning user is typed on the browser

Original issue: https://github.com/ejmstark/event_system/issues/420

commit id: 503f6546df4c8fb5b2fa94472163554c20ca6aae


Added screenshots

@shwetank, could you please send me original screen shots without shadows?

Sure, will mail to you.


multiple ranges support

Description
Added logic and documentation for allowing multiple ranges to be provided to schedule setting ranges. It follows a similar pattern to the recent 106 change for allowing multiple weekly values separated by "|"
Issues Fixed or Closed

N/A

Type of Change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation change (non-code changes affecting only the wiki)
[ ] Infrastructure change (changes related to the github repo, build process, or the like)

Checklist

[ ] My code was submitted to the nightly branch of the repository.

Tested on local server with expected results.


Add Carles's GitHub OIDC documentation to the GitHub pages

Describe the Issue
We want to have some documentation around GitHub OIDC for teams to look at. We want to provide it in a public place that we can keep up to date (not a pdf, which might go stale).
Additional Context
Add any other context, attachments or screenshots
Acceptance Criteria

translate the information in the GitHub OIDC doc that carles wrote into a new page in the GitHub pages
Connect with someone from the tech team to deploy app locally

.
.
.
.
.
.
.
.
.
.
.
Extra Template Info
Definition of Ready
These set of conditions will need to be met in order to bring a ticket into the sprint and start work. Protects the team from unclear requirements.
Issues (Task/Story/Spike) aligned to an EPIC and linked appropriately.
Assigned to the appropriate CPF MEMBER (and is not left blank in ZenHub) at the start of sprint (1st day of the sprint)
Acceptance has been defined for the issue and has been reviewed with CPF team and approved by the necessary approver.
Has been sized and estimated by the delivery team.
Detailed breakdown of the steps required to complete the story in the additional context
Any additional specifications have been documented, reviewed with CPF and approved by the necessary approver.
Acceptance Criteria
A set of pre-defined requirement that need to be met in order to mark the user story as “done”.
It should be testable with no room for interpretation
It should be either “pass” or “fail”
It should be clear enough for business stake holders to understand
As part of the user story, it should be written from the user perspective
A well written acceptance criteria is great for

managing expectations
defining scope
reducing ambiguity
establishing testing criteria for QA
Given (Pre-condition)
When (Action)
Then (Outcome)

Definition of Done
These set of conditions are met for work to be considered as complete on an issue.
All acceptance criteria(s) have been validated.
All the necessary documentation for the issue has been uploaded to Teams.
Functionality has been tested when applicable.
Functionality has been demonstrated to the relevant stakeholders (where applicable).
Story has been scheduled for a Sprint Demo/community update and impacted teams invited to the Demo.
Stories accepted by PO and documented for potential sharing with impacted users.

Documented = Captured in Community Update (CU) deck
Release notes = aspirational goal of providing a bulleted list of features and changes that our users can touch. Was going to store them in our Cloud Pathfinder repo. Can also display to users in the CU

No longer relevant


doc: Add an example

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

Project coverage is 92.42%. Comparing base (c732bd2) to head (06ac3bd).
Report is 3 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main       #6      +/-   ##
==========================================
- Coverage   93.43%   92.42%   -1.02%
==========================================
  Files           1        1
  Lines         198      132      -66
==========================================
- Hits          185      122      -63
+ Misses         13       10       -3

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

It is failing on the doc test introduced in this pull request. I will take a look why that is the case.

@larseggert can you try the following:
modified   .github/workflows/check.yml
@@ -88,7 +88,7 @@ jobs:

           for sanitizer in $SANITIZERS; do
             echo "Running tests with $sanitizer sanitizer..."
-            RUSTFLAGS="-Z sanitizer=$sanitizer" cargo +nightly test -Z build-std --target $TARGET
+            RUSTFLAGS="-Z sanitizer=$sanitizer" RUSTDOCFLAGS="-Z sanitizer=$sanitizer" cargo +nightly test -Z build-std --target $TARGET
           done

test src/lib.rs - get_interface_mtu (line 32) ... ok

Seems to work.

I don't think the latest commit will compile. See https://github.com/mozilla/mtu/pull/6#discussion_r1741020895 in case it is already hidden by GitHub UI.


add gentx

Hello, your gentx seems invalid; you have to set min self delegation to a positive integer. Could you resubmit your gentx?

@yoongbok-lee
Resubmitted https://github.com/certikfoundation/chain/pull/127


fix(discovery): add retries to discover kubernetes api

Signed-off-by: AmitKumarDas<EMAIL_ADDRESS>

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