Duplicate matches for same object

Note: Using branch "randonneur-transformations"
Using the attached fixtures, and running:
flowmapper map \
    --fields config/simapro-ecoinvent.py \
    --output-dir dev \
    a.json \
    b.json

Leads to the following mapping file:
[
  {
    "source": {
      "name": "Sulfate",
      "categories": [
        "Emissions to water",
        ""
      ],
      "unit": "kg"
    },
    "target": {
      "uuid": "17a7db69-d874-4ecd-af5d-48c98def445f",
      "name": "Barite",
      "context": "water/unspecified",
      "unit": "kg"
    },
    "conversion_factor": 1.0,
    "comment": "Identical synonyms"
  },
  {
    "source": {
      "name": "Sulfate",
      "categories": [
        "Emissions to water",
        ""
      ],
      "unit": "kg"
    },
    "target": {
      "uuid": "28bca51a-6cc7-46af-961a-fd2b675a1376",
      "name": "Sulfate",
      "context": "water/unspecified",
      "unit": "kg"
    },
    "conversion_factor": 1.0,
    "comment": "Identical names"
  }
]

However, a.json only had one input record. This should be matched only to the first strategy which produced a match.
The synonym match is based on a data error, "sulfate" is not a real synonym for "barite".
a.json
b.json

This behaviour is on main as well.
After finding a match and breaking out of the rules loop, the code does not stop processing the current source flow. It continues to compare this source flow with the remaining target flows. This is why we are getting more than one match for a single source flow.
Should we not allow 1:N mappings at all? I need to keep the for loop as is because we don't know the order of the target flows, but I can remove mappings at the end and keep only the mapping produced by the match rule with higher priority.

This is fixed on main and randonneur-transformations

Should we not allow 1:N mappings at all?

You always get to the heart of the matter... this is a tough question, and my answer is based on my experience on how I have personally and seen others use these mappings. In those cases, a single match is desired.
In the future we could use the randonneur verb disaggregate, if needed.

https://github.com/GreenDelta/olca-app/issues/102 has some useful tidbits for this discussion as well.


Validate core dtypes for core operation implementations

This supersedes https://github.com/Quantco/ndonnx/pull/17. It allows you to, for instance, implement binary operators like add where one argument is a user-defined dtype array while another is a type exported by ndonnx without falling into promotion errors.

Did you consider implementing it in ndonnx._core._utils.variadic_op instead?

The function implementations are much easier to reason about if you can assume that the data types of the array are known. e.g. you can type promote safely, etc. We can make the validation function decorators but I'd want to know more about the reasons for your skepticism first.

The class decorator is very implicit and lives outside of the usual inheritance. What happens with subclasses? Should they be decorated again? What should be the behavior for private helper functions?  I realize that the data type abstraction is broken more generally and that the need for this work-around is a symptom rather than the place to properly fix it. If we can't find a nicer work-around right now so be it, but this is technical debt that really needs a proper fix soon.

We can make them function decorators to address the subclass point but naturally any design work on the dtypes is outside the scope of this PR and requires some separate thinking.

I reworded my previous comment. I think using individual function decorators is maybe a bit excessive boiler plate. If you are happy with this solution then I think we can merge this!


CAMEL-10462: Improve MDC Logging in DefaultCamelContext and RouteService

I added nested classes to help with the MDC logging (to avoid a bunch of duplicate code).  The nested classes have some duplication as well, so longer term, it may be nice to combine them and move them into util.

Just to be sure in this PR the only thing you have done is to move the code inside that try block with the MDCHelper. You have not changed any other code right ? The code change diff viewer makes this harder to spot.

Yes - that's correct.
I wrapped sections of code with a try-with-resources block and used the MDCHelper as a "resource" that the try-with-resources block would automatically close.
I tried a couple of different ways - this way seemed to be the clearest with the least amount of code duplication.

Thanks for the PR it has been merged. Do you mind closing this?


MAX-11493 Icon and Words are Too Closed in App Switcher

Fixed Dropdown item icon spacing issue.
Removed useless class name.

@joshsylvester @sheela-svmx , please help review.

@joshsylvester @sheela-svmx cc @sabrinalui-ge
No action from UI team?

@benjaminliugang  this was merged on the main repo correct. I saw Josh reviewed and had comments and it was fixed in the other repo?  Are we using both the fork and the Main px-dropdown?

It seems we already switch to the main repo in ui-components-predix last week, just  close this PR, let's focus on the main repo.


Number of workers and cpus per worker

https://github.com/vatlab/sos/issues/1290#issuecomment-536595178
Currently we have
task: trunk_workers=[4]*3, cores=4

which means

Each task will use 4 cores
Each trunk with have four workers on three nodes.
Therefore each node will require 4*4=16 cores.

Now, For SLURM (and other clusters)

we should always set ncpus per task to 1, and njobs per node to cores, which is 16.
sos accepts parameters -j node1:ncpu node2:ncpu node3:ncpu to sos execute
sos also knows trunk_workers=[4]*3, so it should start 4 workers on node1, node2 and node3 instead of 16.

Please verify if this is the case.

we should always set ncpus per task to 1,, and njobs per node to cores, which is 16

I thought we should set number of tasks to 1 for each job, and ncpus per task to cores for that job? Basically we should bypass the task concept because in SoS we've got our way to handel tasks.

I thought we should set number of tasks to 1 for each job, and ncpus per task to cores for that job?

You are right, there is only 1 "job" which uses n_workers * cores cpus. It is the terminology between cluster job, cluster task, and sos task, sos workers that become confusing.

Currently #1290 seems to be fixed and we are on the same page that multiple tasks wound not be necessary. However in your first thread on this post:

we should always set ncpus per task to 1, and njobs per node to cores, which is 16.

while I was sugesting always set number of tasks to 1 and ncpus per task to cores then the actual {cores} will be cores times number of trunk workers on that node. Is that currently the case?

while I was suggesting always set number of tasks to 1 and ncpus per task to cores then the actual {cores} will be cores times number of trunk workers on that node. Is that currently the case?

yes.

Just double checked that the implementation is correct regarding this issue.


[feature request] lyrics font size

Hey!
First, thanks A LOT for your awesome theme. I really love it and it has replaced two apps I was using before!
There is only one thing that bothers me at the moment: I am using a tablet in landscape mode in the kitchen to control my LMS. I use the desktop mode to use most of the space available (1920x1080 pixels).
However, when I switch to see the lyrics the font-size is far too small (I am reading the lyrics while cooking from a meter or so away). So I'm always modifying the CSS to get a bigger font-size for "np-info-lyrics" to xx-large or xxx-large. But I have to do this every time there is an update :-(
So this is my request:
Could you maybe include a plus/bigger and minus/smaller button on the lyrics page to change the font-size? And remember the setting? That would be so cool!
Best regards

Implemented in 1.2 branch for 1.2.0

Wow, that was fast! Thank you! :-)


Specify name for dispatched job batches within the Exporter & Importer classes

Description
Implemented the functionality to specify a name for dispatched job batches within the Exporter & Importer classes. This enhancement facilitates streamlined tracking of job batches in Laravel Horizon.

[x] Visual changes (if any) are shown using screenshots/recordings of before and after.

Code style

[x] composer cs command has been run.

Testing

[x] Changes have been tested.

Documentation

[x] Documentation is up-to-date.

Thanks!


Heavy time.Now usage cause taskgated to consume lots of cpu

Please answer these questions before submitting your issue. Thanks!

What version of Go are you using (go version)?

go version devel +bd72497 Mon Apr 11 01:52:10 2016 +0000 darwin/amd64

What operating system and processor architecture are you using (go env)?

darwin/amd64

What did you do?
Run this program

package main

import (
        "fmt"
        "time"
)

func main() {
        t1 := time.Now().Add(-1 * time.Second) // ensure there is no collision on first iteration
        for {
                t2 := time.Now()
                d := t2.Sub(t1)
                if d == 0 {
                        fmt.Println("collision at", t2)
                }
                t1 = t2
        }
}

What did you expect to see?

This program should cause 100% cpu usage.

What did you see instead?

The program causes 100% cpu usage, but taskgated is also heavily used , around 20% on my system.
https://developer.apple.com/library/mac/documentation/Darwin/Reference/ManPages/man8/taskgated.8.html
Reports that taskgated is responsible for implemting the mach task_for_pid syscall (?), so it looks like we're calling this syscall many times, we should probably not do that and cache the task port once per process.

Can't verify it on OS X 10.11.4 with both 1.6.1 and devel +285e786. taskgated is nowhere near the top, dtruss doesn't show anything unexpected.


Exposed nextStep in the impress:stepleave event for the sake of collaboration

I wrote a really simple impress.js presentation sync and in the process modified the impress.js source to surface the nextStep in the impress:stepleave event. I need to know the destination step immediately upon leaving to ensure real-time syncing with minimal lag.
This was a very minor change, I hope you'll consider accepting it into the official release. Thanks for this library! It's wonderfully simple.
Tim

Hi @TimHeckel, in an effort to clear up older issues/PRs we are pinging back to know if you are still tracking this request.
To give a little bit of context, recently a decision was made in the project to make the development more active and the first task is to clear up older issues like this one to see if the OP is still interested in keep it going.

Closing due to the lack of feedback from the OP. If you want to work in the PR again, feel free to comment here to open up the discussion again
In the meantime, refer to the issue #375.


[Bug]: issue with jest-runtime between 27.1.0 and 27.1.1 and jest.isolateModules

Version
27.2.0
Steps to reproduce
unable to link my repo, but can give an example that currently works. seems how mocks are applied changed between 27.1.0 and 27.1.1. assume related to this PR: https://github.com/facebook/jest/pull/11818
Expected behavior
const someModule = require('some-module');

jest.mock('some-module')

describe('test', () => {
  let app;
  beforeEach(() => {
    jest.isolateModules(() => {
      app = require('./app.js')
    })
  })

  test('expect module to have been called', () => {
    expect(someModule.function).toHaveBeenCalled();
  })
})

I would expect this to pass, which is currently does if I pass in a yarn resolution to downgrade jest-runtime to version 27.1.0.
Actual behavior
Using above example, the instance of some-module inside of the test and inside the required file appear to be different. Inside the file, the module is indeed mocked, but the expectation does not pass.
Additional context
No response
Environment
System:
    OS: macOS 11.5.2
    CPU: (12) x64 Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz
  Binaries:
    Node: 14.17.6 - /usr/local/bin/node
    Yarn: 1.22.11 - /usr/local/bin/yarn
    npm: 7.21.1 - /usr/local/bin/npm
  npmPackages:
    jest: 27.2.0 => 27.2.0

have the same problem with ts-jest, here is a repro repo https://github.com/rburgst/ts-jest-27.1

Please put together a minimal repository showing the error (i.e. without ts-jest - I have zero clue what mocked is)

Actually never mind, just ripping it out wasn't too bad - fix incoming 🙂

https://github.com/facebook/jest/releases/tag/v27.2.1


Add Spec for AzureStack Compute Admin - managed Disk

The change is adding the new spec file for azurestack admin compute scenario:
a. It is adding the Disk resource which support get and list
b. It is adding the DiskMigration resource which support, get, list, create and cancel.
#######
This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[x] The title of the PR is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[x] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[x] If applicable, the PR references the bug/issue that it fixes.
[x] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[x] I have read the contribution guidelines.
[x] My spec meets the review criteria:

[x] The spec conforms to the Swagger 2.0 specification.
[x] The spec follows the guidelines described in the Swagger checklist document.
[x] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

Automation for azure-sdk-for-python

Automation for azure-sdk-for-go

Automation for azure-sdk-for-ruby

Automation for azure-sdk-for-node

Automation for azure-sdk-for-java

@knithinc is added to the review. #Closed

@bganapa is added to the review. #Closed

@viananth is added to the review. #Closed

@deathly809 is added to the review. #Closed

how can I add 2 versions for tag?

Refers to: specification/azsadmin/resource-manager/compute/readme.md:34 in 241db40. [](commit_id = 241db40628cc2e3c973284810235c52d077fd76d, deletion_comment = False)

Compute Admin

where can I add description for this PR?

Refers to: specification/azsadmin/resource-manager/compute/readme.md:1 in 241db40. [](commit_id = 241db40628cc2e3c973284810235c52d077fd76d, deletion_comment = False)

@shanswmicrosoft have these new APIs been reviewed by ARM?

Not yet. I plan to send a review very soon.

In reply to: 405139511 [](ancestors = 405139511)

Ping @ravbhatnagar

ARM review not needed as this is Azure Stack admin APIs. Someone from Azure Stack should likely review.

@jhendrixMSFT / @ravbhatnagar My understanding is that all properties which should be modified on the client side should be marked readOnly: true.  Is this a correct assumption?
https://github.com/Azure/azure-rest-api-specs/blob/master/documentation/openapi-authoring-manual-guidelines.md

Rule
Severity
Category
Applies to

Read only parameters of the model properties MUST be labeled as "readOnly": true in OpenAPI(Swagger) spec
Error

ARM and Data plane OpenAPI(Swagger) specs

Can one of the admins verify this patch?

@jhendrixMSFT We are okay with the current spec.  Is there anything you see?

@deathly809 I wasn't sure if this was still iterating.  I'll wrap up my review shortly and merge if it all looks good.


Code failing with dlt 1.3.0

I have some code that worked fine with 1.2.0 and now fails with 1.3.0 with this error:
current_value, traces = _resolve_config_field(
^^^^^^^^^^^^^^^^^^^^^^
File "/bin/app/lib/python3.11/site-packages/dlt/common/configuration/resolve.py", line 321, in _resolve_config_field
value, traces = _resolve_single_value(
^^^^^^^^^^^^^^^^^^^^^^
File "/bin/app/lib/python3.11/site-packages/dlt/common/configuration/resolve.py", line 420, in _resolve_single_value
providers_context = container[PluggableRunContext].providers
~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^
File "/bin/app/lib/python3.11/site-packages/dlt/common/configuration/container.py", line 67, in __getitem__
item = spec()
^^^^^^
File "/bin/app/lib/python3.11/site-packages/dlt/common/configuration/specs/pluggable_run_context.py", line 72, in __init__
self._plug(run_dir=None)
File "/bin/app/lib/python3.11/site-packages/dlt/common/configuration/specs/pluggable_run_context.py", line 125, in _plug
m = plugins.manager()
^^^^^^^^^^^^^^^^^
File "/bin/app/lib/python3.11/site-packages/dlt/common/configuration/plugins.py", line 41, in manager
return Container()[PluginContext].manager
~~~~~~~~~~~^^^^^^^^^^^^^^^
File "/bin/app/lib/python3.11/site-packages/dlt/common/configuration/container.py", line 67, in __getitem__
item = spec()
^^^^^^
File "/bin/app/lib/python3.11/site-packages/dlt/common/configuration/plugins.py", line 34, in __init__
load_setuptools_entrypoints(self.manager)
File "/bin/app/lib/python3.11/site-packages/dlt/common/configuration/plugins.py", line 51, in load_setuptools_entrypoints
if hasattr(dist, "name") and not dist.name.startswith("dlt-"):
^^^^^^^^^^^^^^^^^^^^
AttributeError: 'NoneType' object has no attribute 'startswith'

I apologize for not providing a minimum example yet. However, I wanted to report this right away.

Fixed in #2024


Provixion x1 instances for carbonplan

Requested by Joe in https://github.com/2i2c-org/pilot-hubs/issues/291#issuecomment-858075940
Refresh auth credentials, they had expired. Fixed in
https://github.com/2i2c-org/pilot-hubs/issues/381

Depends on https://github.com/2i2c-org/pilot-hubs/pull/470

Already deployed!


o.c.r.PropertiesFileRuleSetConfigurer -- RuleSet configuration properties file [codenarc.properties] not found.

I've recently upgraded my npm-lint version from 9 to 13. However, i'm facing the below issue when running the npm-groovy-lint command.
+ npm-groovy-lint --noserver
GroovyLint: Error running CodeNarc:
22:57:47.254 [main] INFO  o.c.r.PropertiesFileRuleRegistry -- Loaded properties file in 300ms; 397 rules
22:57:59.960 [main] INFO  o.c.r.PropertiesFileRuleSetConfigurer -- RuleSet configuration properties file [codenarc.properties] not found.

My .groovylintrc.json is below
{
  "extends": "all",
  "rules": {
    "basic.DeadCode": "error",
    "convention.CompileStatic": {
      "severity": "info"
    },
    "convention.FieldTypeRequired": "info",
    "convention.IfStatementCouldBeTernary": "info",
    "convention.NoDef": "info",
    "convention.TrailingComma": "off",
    "convention.VariableTypeRequired": "info",
    "dry.DuplicateListLiteral": "info",
    "dry.DuplicateMapLiteral": "warning",
    "dry.DuplicateNumberLiteral": {
      "ignoreNumbers": [0, 1, 2, 3, -1],
      "severity": "info"
    },
    "dry.DuplicateStringLiteral": "info",
    "exceptions.ThrowException": "info",
    "exceptions.ThrowNullPointerException": "info",
    "exceptions.ThrowRuntimeException": "info",
    "exceptions.ThrowThrowable": "info",
    "formatting.BracesForClass": "info",
    "formatting.BracesForForLoop": "info",
    "formatting.BracesForIfElse": "info",
    "formatting.BracesForMethod": "info",
    "formatting.BracesForTryCatchFinally": "info",
    "formatting.Indentation": {
      "spacesPerIndentLevel": 4,
      "severity": "info"
    },
    "formatting.SpaceAroundMapEntryColon": "off",
    "groovyism.ExplicitCallToEqualsMethod": "info",
    "logging.Println": "off",
    "unused.UnusedArray": "error",
    "unused.UnusedObject": "error",
    "unused.UnusedPrivateField": "error",
    "unused.UnusedPrivateMethod": "error",
    "unused.UnusedPrivateMethodParameter": "error",
    "unused.UnusedVariable": "error",
    "unnecessary.UnnecessaryReturnKeyword": "off"
  }
}

I tried adding codenarc.properties file with ruleset=org.codenarc.ruleset.AllRules as data in it. Still the issue persist.
@nvuillam

@harishjangam6979 it seems to be an output from CodeNarc...
Do you have a sample repo where we could reproduce it ?
cc @stevenh

Note: 14.0.0 has been released and contains again more refactoring, please can you upgrade from 13 to 14 to see if the issue persists ?
https://github.com/nvuillam/npm-groovy-lint/releases/tag/v14.0.0

I don't think that's anything to worry about, previously this could well have been hidden but with the new logging setup you'll see INFO and above both npm-groovy-lint and CodeNarc.
Are you seeing any adverse effects?

Closing as duplicate of https://github.com/nvuillam/npm-groovy-lint/issues/342


News websites updated

Checkout the new websites that i have added!

Please review the contribution guide

Checkout the new websites that i have added!
@falconcode16
Hey I just checked you added resources.
But don't remove resources already added.


步进值不为1， 滑动的最大值会超出

在move方法重应该加个判断 ： value[index] = newValue > max ? max : newValue;

Sorry, I do not know what is being asked here. If you can provide some more information and an example, we can reopen the ticket.


<EMAIL_ADDRESS>

ElementUI version

OS/Browers version

Vue version

Reproduction Link

Steps to reproduce
What is Expected?
What is actually happening?

keyup.native.enter

提问前请阅读 FAQ


Governance. Delegations. When Voted last 30 days is 0 - shows wrong

Description
Voted last 30 days shows wrong, when its 0:
Expected result:

Actual result:

Status verification: ✅


Fix -r inside requirements.txt files (#132)

This fixes Issue #132 to support using "-r" inside requirements.txt files.
There was already logic to handle these files, but there was a bug in the string parsing.
Tested on Ubuntu 18.04 with python 2.7.17 and 3.6.9.
$ cat tests/reqs_1.txt
-r reqs_2.txt

$ cat tests/reqs_2.txt
insecure-package==0.1.0
--requirement reqs_3.txt # with comment

$ cat tests/reqs_3.txt
insecure-package==0.1.1

$ safety check -r tests/reqs_1.txt
...
│ insecure-package           │ 0.1.0     │ <0.2.0                   │ 25853    │
│ insecure-package           │ 0.1.1     │ <0.2.0                   │ 25853    │
...

This looks good to me. Would you mind making some minor changes as commented below?

All comments addressed. Thanks for the speedy review!


BreadCrumb: SVG location of the DOM

https://github.com/primefaces/primereact/issues/4438
Needs to add class

Fixed in #4438 of PrimeReact Theme Designer.


⚠ SceneTime has degraded performance

In b91fea9, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 3977 ms

Resolved: SceneTime performance has improved in d17ce2a.


WIP [Ruby 2.7] Numbered parameters

Added specs for:

Numbered parameters as default block parameters are introduced. Feature #4475

@eregon Thanks. Fixed minor issues.


Jan 19 - LWDG Rocket Delays

Event Information

Category
Details

Stream Date
January 19, 2021

Stream Time
3-4p

Title
In Review

Description
In Review

Speaker
Sarah

SharePoint ID
8034

SharePoint Status
Generic Published

Additional Resources:

Event Checklist
10 Weeks Prior

[ ] Title & Description Finalized
[ ] Tracking Links/Short links
[ ] Title Card
[ ] Survey Card
[ ] Info Sheet
[ ] Published
[ ] Calendar Invite

This has been streamed and details added to Stream doc

This has been streamed and details added to Stream doc


Patch: define synchronized_data_class on all rounds

Proposed changes
set synchronized_data_class on all remaining rounds that did not explicitly set it.
Fixes
If it fixes a bug or resolves a feature request, be sure to link to that issue.
Types of changes
What types of changes does your code introduce? (A breaking change is a fix or feature that would cause existing functionality and APIs to not work as expected.)
Put an x in the box that applies

[ ] Non-breaking fix (non-breaking change which fixes an issue)
[ ] Breaking fix (breaking change which fixes an issue)
[ ] Non-breaking feature (non-breaking change which adds functionality)
[ ] Breaking feature (breaking change which adds functionality)
[ ] Refactor (non-breaking change which changes implementation)
[ ] Messy (mixture of the above - requires explanation!)

Checklist
Put an x in the boxes that apply.

[ ] I have read the CONTRIBUTING doc
[ ] I am making a pull request against the main branch (left side). Also you should start your branch off our main.
[ ] Lint and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have locally run services that could be impacted and they do not present failures derived from my changes

Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

Various rounds, e.g. VotingRound, which cause the issue @Adamantios is facing, have synchronized_data_class = BaseSynchronizedData  set by default and hance will not be raising or logging a warning.
https://github.com/valory-xyz/open-autonomy/blob/923a0bbe25d7fbed432eaed2ffadee88955ba480/packages/valory/skills/abstract_round_abci/base.py#L1353
https://github.com/valory-xyz/open-autonomy/blob/923a0bbe25d7fbed432eaed2ffadee88955ba480/packages/valory/skills/abstract_round_abci/base.py#L1405
https://github.com/valory-xyz/open-autonomy/blob/923a0bbe25d7fbed432eaed2ffadee88955ba480/packages/valory/skills/abstract_round_abci/base.py#L1492


CB-10439: Option for windows8 option must be removed from cordova-mob…

…ile-spec package
Removed windows8 platform from the list
@dblotsky @riknoll @nikhilkh Can you please review and commit this PR?

LGTM

+1 LGTM

LGTM.


Unable to parse JestResult into POJO if search limited by field

jestResult.getSourceAsObjectList(Class.class) does not work if the initial search query specifies fields to limit in response. In my test, I used SearchSourceBuilder to limit the fields returned by ES as shown below.
        SearchSourceBuilder searchSourceBuilder = new SearchSourceBuilder();
        searchSourceBuilder.query(QueryBuilders.wildcardQuery("description","*"))
                                .field("glassdoorID")
                                .field("logoURI")
                                .size(Integer.MAX_VALUE);

This is a known issue, see #157.


Handle Host header parameter transformation allowing for non Windows …

…EOL and 'host:' as well as 'Host:'

console.log(chunk.toString());

Fixed in master


Add URL to the playground

I think it'd be a great idea to encourage people to take the test, and showcase this link somewhere: http://arc-editor.lab42.global

Is there an https version of your link?

Thanks, @gkamradt! I actually will revisit the challenge this year. =)


Remove dev and stable and merge everything to main?

Right now we have dev and stable that have the latest changes and documentation. This setup introduces a bit of overhead in managing the repo. How about we just remove these and have all PR target main?

Just made these changes


python: limnoria: Add optional dependencies and enable tests.

Motivation for this change
Limnoria has optional features enabled when these dependencies are available.
Things done
I copied dependencies from the source requirements.txt file.
I also enabled tests while I was at it, but I can remove them if you think it's too much overhead (5 to 10 min on an average PC)

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

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

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

cc @cillianderoiste

Thanks for the review, and sorry for the late reply, I missed the notification somehow.
This should be fixed now.

Result of nixpkgs-review pr 84989 run on x86_64-linux 1

2 packages built:

python37Packages.limnoria
python38Packages.limnoria

Result of nixpkgs-review pr 84989 run on x86_64-darwin 1

2 packages failed to build:

python37Packages.limnoria
python38Packages.limnoria

Hmm, besides the "Operation not permitted" ones, they look like actual bugs, though.

@SuperSandro2000 If you don't mind, could you re-run them with the -vv option added to the checkPhase command, and show me the output? (Sorry, I don't have access to any darwin machine)

@SuperSandro2000 If you don't mind, could you re-run them with the -vv option added to the checkPhase command, and show me the whole output? (Sorry, I don't have access to any darwin machine)

Not necessary. self.socket.bind(self.server_address) is not allowed in the darwin sandbox. Just disable those tests.

I know, but it only explains the PermissionError: [Errno 1] Operation not permitted failures, not the other ones.

I know, but it only explains the PermissionError: [Errno 1] Operation not permitted failures, not the other ones.

You can just mark it broken on darwin if you do not want to deal with this now.

Heh, I can't find a Darwin machine to debug, so let's mark it as broken.
How do I do it? meta.broken = !hostPlatform.isDarwin?

Heh, I can't find a Darwin machine to debug, so let's mark it as broken.
How do I do it? meta.broken = !hostPlatform.isDarwin?

You probably want to set meta.broken = stdenv.isDarwin if you want to mark it broken on darwin.

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
Result of nixpkgs-review pr 84989 run on x86_64-linux 1

2 packages failed to build and are new build failures:

python38Packages.limnoria: plain log  |  pretty log
python39Packages.limnoria: log was empty

@ofborg build pythonPackages.limnoria

@ofborg build python3Packages.limnoria


Allow options for fade

Allow a fast dismissal option (maybe a setting for fade time) that disables the fade out of images. I have my images on top of my run button and if i just misspell one variable it sometimes takes longer to wait for the image to disappear, then the combined time of fixing my spelling mistake and clicking run again (especially if i forgot to first dismiss the image and then fix my error)

Right now, things are set up such that the gif will at least get one full playthrough. So if it is a long gif, I don't think the faster fade out time will work.

spelling mistake and clicking run again (especially if i forgot to first dismiss the image and then fix my error)

So you are are that you can click the displayed image, and click outside of it to dismiss it before it completes? That isn't sufficient? If not you could bind a shortcut to the clear meme action.


0.2.14 feature "multiple nested uiSref directives" does not seem to work

It seems the "multiple" part does not work. This is the way it's supposed to work right?
There is always only one item "active", for menu 1 it's menu 1 and for menu 2 it's the parent li

	main menu item

menu 1

menu 2

added plunkr, seems obvious enough
http://plnkr.co/edit/Cp56i7lfCEFuNUraf7fv?p=preview

Seems to be working fine. When menu 1 is active, the
 has active class. When menu 2 is active,
 has active class.

The first ui-sref-active found at the same level or above the ui-sref will be used.

Nevermind, my bad.
I was way too excited and thought the following new feature was for ui-sref-active.
uiSrefActive: Added support for multiple nested uiSref directives (b1844948)


BMI Calculator

The Body Mass Index (BMI) Calculator can be used to calculate BMI values based on height and weight. BMI is a fairly reliable indicator of body fatness for most people. By using this BMI calculator people can easily check if they are normal weight, overweight or underweight.

Hey! My friend @D-TheProgrammer and I would like to work on this. Can we get assigned to it?
We are computer science students and we have a course in which we have to make a contribution in a project. It would be great to do it with yours.

@Sindhu-2004 Thank you for providing your insight but it is not required as of now.


New examples working.

All markers examples working again with the new logic.
Added bootstrap again to the bower.json dependencies to make the AwesomeMarkers examples work

LGTM


pip install broken?

(Apologies if this is just a quirk of my local setup, but I noticed there was a recent change to the way the project is packaged, and thought that might be related to the issue I'm having.)
I ran pip install mwviews and it appeared to install successfully. But if I try to run something like python -m mwviews, I get No module named mwviews.
pip show mwviews shows the package as being installed. Its location is given as: Location: /home/colin/.local/lib/python3.6/site-packages (as expected)
However, my site-packages does not have a mwviews subdirectory. And if I try to use pip to uninstall mwviews, the list of files to be removed looks like...
  /home/colin/.local/bin/mwviews
  /home/colin/.local/lib/python3.6/site-packages/api/__init__.py
  /home/colin/.local/lib/python3.6/site-packages/api/__pycache__/__init__.cpython-36.pyc
  /home/colin/.local/lib/python3.6/site-packages/api/__pycache__/pageviews.cpython-36.pyc
  /home/colin/.local/lib/python3.6/site-packages/api/pageviews.py
  /home/colin/.local/lib/python3.6/site-packages/mwviews-0.2.0.dist-info/INSTALLER
  /home/colin/.local/lib/python3.6/site-packages/mwviews-0.2.0.dist-info/LICENSE.txt
  /home/colin/.local/lib/python3.6/site-packages/mwviews-0.2.0.dist-info/METADATA
  /home/colin/.local/lib/python3.6/site-packages/mwviews-0.2.0.dist-info/RECORD
  /home/colin/.local/lib/python3.6/site-packages/mwviews-0.2.0.dist-info/WHEEL
  /home/colin/.local/lib/python3.6/site-packages/mwviews-0.2.0.dist-info/entry_points.txt
  /home/colin/.local/lib/python3.6/site-packages/mwviews-0.2.0.dist-info/top_level.txt
  /home/colin/.local/lib/python3.6/site-packages/utilities/__init__.py
  /home/colin/.local/lib/python3.6/site-packages/utilities/__pycache__/__init__.cpython-36.pyc
  /home/colin/.local/lib/python3.6/site-packages/utilities/__pycache__/aggregate.cpython-36.pyc
  /home/colin/.local/lib/python3.6/site-packages/utilities/__pycache__/fetch_global_namespaces.cpython-36.pyc
  /home/colin/.local/lib/python3.6/site-packages/utilities/__pycache__/util.cpython-36.pyc
  /home/colin/.local/lib/python3.6/site-packages/utilities/aggregate.py
  /home/colin/.local/lib/python3.6/site-packages/utilities/fetch_global_namespaces.py
  /home/colin/.local/lib/python3.6/site-packages/utilities/util.py

In other words, it looks to me like the contents of the package is getting exploded into the top-level site-packages directing, rather than its own proper subdirectory. (In fact, it turns out that as a workaround I can do something like from api import PageviewsClient rather than from mwviews.api import PageviewsClient)

this indeed seems like broken packaging.  Thanks for noticing, I'll see
what I did wrong and try to fix!
On Wed, Mar 2, 2022 at 3:14 PM Colin @.***> wrote:

(Apologies if this is just a quirk of my local setup, but I noticed there
was a recent change to the way the project is packaged, and thought that
might be related to the issue I'm having.)
I ran pip install mwviews and it appeared to install successfully. But if
I try to run something like python -m mwviews, I get No module named
mwviews.
pip show mwviews shows the package as being installed. Its location is
given as: Location: /home/colin/.local/lib/python3.6/site-packages (as
expected)
However, my site-packages does not have a mwviews subdirectory. And if
I try to use pip to uninstall mwviews, the list of files to be removed
looks like...
/home/colin/.local/bin/mwviews
/home/colin/.local/lib/python3.6/site-packages/api/init.py
/home/colin/.local/lib/python3.6/site-packages/api/pycache/init.cpython-36.pyc
/home/colin/.local/lib/python3.6/site-packages/api/pycache/pageviews.cpython-36.pyc
/home/colin/.local/lib/python3.6/site-packages/api/pageviews.py
/home/colin/.local/lib/python3.6/site-packages/mwviews-0.2.0.dist-info/INSTALLER
/home/colin/.local/lib/python3.6/site-packages/mwviews-0.2.0.dist-info/LICENSE.txt
/home/colin/.local/lib/python3.6/site-packages/mwviews-0.2.0.dist-info/METADATA
/home/colin/.local/lib/python3.6/site-packages/mwviews-0.2.0.dist-info/RECORD
/home/colin/.local/lib/python3.6/site-packages/mwviews-0.2.0.dist-info/WHEEL
/home/colin/.local/lib/python3.6/site-packages/mwviews-0.2.0.dist-info/entry_points.txt
/home/colin/.local/lib/python3.6/site-packages/mwviews-0.2.0.dist-info/top_level.txt
/home/colin/.local/lib/python3.6/site-packages/utilities/init.py
/home/colin/.local/lib/python3.6/site-packages/utilities/pycache/init.cpython-36.pyc
/home/colin/.local/lib/python3.6/site-packages/utilities/pycache/aggregate.cpython-36.pyc
/home/colin/.local/lib/python3.6/site-packages/utilities/pycache/fetch_global_namespaces.cpython-36.pyc
/home/colin/.local/lib/python3.6/site-packages/utilities/pycache/util.cpython-36.pyc
/home/colin/.local/lib/python3.6/site-packages/utilities/aggregate.py
/home/colin/.local/lib/python3.6/site-packages/utilities/fetch_global_namespaces.py
/home/colin/.local/lib/python3.6/site-packages/utilities/util.py
In other words, it looks to me like the contents of the package is getting
exploded into the top-level site-packages directing, rather than its own
proper subdirectory. (In fact, it turns out that as a workaround I can do
something like from api import PageviewsClient rather than from
mwviews.api import PageviewsClient)
—
Reply to this email directly, view it on GitHub
https://github.com/mediawiki-utilities/python-mwviews/issues/18, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAH5UUCHHM7IEEFIZGIRT5TU57DY3ANCNFSM5PYPSLPA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Ok, I published 0.2.1 on pypi, please give that a shot and let me know if the install has issues.  I noticed some of the commands on the executable aren't working anymore, but hopefully the general package is ok now.

Seems to be fixed with 0.2.1. Thanks!


Testing, please ignore. (pfqdha)

Bug bounty test - please ignore.... Please DO NOT APPROVE THIS! (pfqdha)

Dear colleagues, I close this PR.
It could be malicious code!
I have reported the user to GitHub and will also report it internally.


Update README.md

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 82.156%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
3011

Relevant Lines:
3665

💛  - Coveralls


Feature/generator improvements

Added --nbf and --cti commands for deterministic generation
Fixed a bug where kid was not included in protected headers

Hi @gizmoguy, just following up, this PR allowed me to generate test cases for @vaxxnz/nzcp-js which I merged in https://github.com/vaxxnz/nzcp-js/pull/62
So this change certainly produces working custom NZCP passes.
What do I need to do to get this merged?

Apologies @noway, it's been a busy start to the year at day job and managed to miss this PR.
All merged now, thanks again for your contribution.


Unsubscribe using transactional email with dynamic template

Issue Summary
When sending transactional emails using a dynamic template I want to offer subscribers the option to unsubscribe.
At the moment the Unsubscribe link and the Unsubscribe preferences link are empty and do nothing:

Steps to Reproduce

Create a template.
Add the unsubscribe module.
Send a transactional email using such template.

I know, there's another option, which is including the unsubscribe text under every email by using the "Settings > tracking > Subscription Tracking" option, but I'm not interested in it.
I want to be able to include the text in my template.
Technical details:

sendgrid-php Version: master latest

You may need to set the ASM Unsubscribe Group ID as shown here (in ruby, but the concept is the same):
https://github.com/sendgrid/sendgrid-ruby/issues/59#issuecomment-379083848

This seems to be an unsolved problem for several years now.
How about some settings on the unsubscribe module in the editor? maybe some info near the module?
Or maybe some example with unsubscribe?
Why does global unsubscribe need a group id?
cant it default to the group id marked default?

Anyone found a solution?

@Elyx0 something along the lines of
mail.setASM(new ASM());
mail.asm.setGroupId(request.unsubscribeGroup);

For whatever language youre using. The group ID is under unsubscribe groups

hello, i went to menu Settings > Tracking  option. I activated Subscription Tracking

Hello everyone,
It looks like there were a few solutions offered here (thanks for chipping in :)) so I will close this one out. If someone is still having difficulty with this feature, please let us know. Thanks!
With best regards,
Elmer

Definitely still having issues with this. I have Subscription Tracking activated and still not working.

@admarko Please open a new issue with details about the problem you're experiencing.


ESM modules are not loaded by AWS lambda

Describe the bug
When packaging a lambda function with platform: neutral, the lambda fails at runtime with:
{
    "errorType": "Runtime.UserCodeSyntaxError",
    "errorMessage": "SyntaxError: Unexpected token 'export'",
    "stack": [
        "Runtime.UserCodeSyntaxError: SyntaxError: Unexpected token 'export'",
        "    at _loadUserApp (file:///var/runtime/index.mjs:997:17)",
        "    at async Object.UserFunction.js.module.exports.load (file:///var/runtime/index.mjs:1035:21)",
        "    at async start (file:///var/runtime/index.mjs:1200:23)",
        "    at async file:///var/runtime/index.mjs:1206:1"
    ]
}

This suggests the runtime is trying to load it as CJS. This document explains that either package.json must indicate the type as module or the lambda file should have a .mjs file extension: https://aws.amazon.com/blogs/compute/using-node-js-es-modules-and-top-level-await-in-aws-lambda/
As a workaround, it is fortunately possible to specify outputFileExtension as .mjs which fulfils the second condition and might be what you had in mind when enabling ESM support (judging by the test cases), but this is neither mentioned in the documentation for serverless-esbuild nor selected by default.
To Reproduce

Have a project setup with type: module
Configure esbuild with platform: neutral
Include a minimal demo lambda
Verify that when built, the artifact ZIP file includes a .js file containing a top-level async method as expected
Deploy and try to invoke on AWS

Expected behavior
I expected a package.json file containing only type: module to be included with the bundle.
This is what SST does out of the box.
Screenshots or Logs
n/a
Versions (please complete the following information):

OS: Mac
Serverless Framework Version: 3.24.0
Plugin Version: 1.32.8

Additional context
Looks like there is a workaround as indicated.

+1 I had the same issue as OP.
I was unable to include the package.json at all using the documented method for packaging e.g.
// serverless.yml
package:
  patterns:
    - '!node_modules/@aws-sdk/**'
    - package.json

Fortunately i was able to add outputFileExtension: .mjs to achieve this too thanks to OP

The workaround isn't enough when using sls invoke local: https://github.com/serverless/serverless/issues/11308#issuecomment-1366781871


Remove installation specifics

remove campaign page files
remove config
add template for config
adding config copy to CI task

Sorry that I needed more time for taking care of the conflicts :(


Natural sorting of properties

Some values are messed up (ordered alphabetically), for example, 'Maximum Clamping Voltage' of 'Circuit Protection/TVS':

I tried localeCompare with {numeric: true} and it was better but still not perfect:

I found "@discoveryjs/natural-compare" package and it seems to work just fine:

Thanks for the PR. The original idea of the project was to parse the data in backend, normalize them and present them in uniform form. Therefore, if your original intention is to fix problem of the fields 'Maximum Clamping Voltage' and 'Circuit Protection/TVS' I suggest a "better" fix: adding them to this list: https://github.com/yaqwsx/jlcparts/blob/17adb09b9d9b3289dead846d93f94c2c360dd81b/jlcparts/datatables.py#L66
Overall, I like the idea of the fallback solution (string compare) behaving more reasonable.

TVS was just an example. I think we can't parse/normalize every single property so at least the default sorting could be better.

I think we can - it is just laborious (we already support an arbitrary field format with multiple values in various units).


iops parameter error

I am currently using Chef Automate via AWS OpsWorks with Chef-Workstation installed on my local.  I'm running Chef-Workstation 23.5.1040 and 'knife --version' returns Chef Infra Client: 18.2.7.  Whenever I run knife ec2 server create, I'm getting an error returned of: ERROR: The parameter iops is not supported for gp2 volumes.  I'm not specifying iops at all, just --ebs-volume-type gp2.
Any help would be greatly appreciated.

Just for what it's worth, the issue goes away when specifying the Amazon Linux 2 ami.  Thanks again.

having the same issue with debian 12 on aws

it's a duplicate of #673 and can be fixed by manually replacing the ec2_server_create.rb file with the one here https://github.com/data-axle/knife-ec2/commit/a2bf0037c4a9e783b2210d8ad7f54a4585ec58dd


docs: clarify that PodSecurityPolicy is now deprecated

Addressing PodSecurityPolicy removal in Kubernetes v1.25. Explaining our reasons for keeping this section for now, even though it's slated for removal in the near future.
Closes #3991

/ok-to-merge documentation


Facebook's extracted mpd (MPEG-DASH manifest) is missing base url for live stream

Please follow the guide below

You will be asked some questions and requested to provide some information, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your issue (like that [x])
Use Preview tab to see how your issue will actually look like

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2016.12.22. If it's not read this FAQ entry and update. Issues with outdated version will be rejected.

[x] I've verified and I assure that I'm running youtube-dl 2016.12.22 also confirmed with latest commit or live ebuild.

Before submitting an issue make sure you have:

[ ] At least skimmed through README and most notably FAQ and BUGS sections
[ ] Searched the bugtracker for similar issues including closed ones

What is the purpose of your issue?

[x] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[] Feature request (request for a new functionality)
[ ] Question
[ ] Other

The following sections concretize particular purposed issues, you can erase any section (the contents between triple ---) not applicable to your issue

If the purpose of this issue is a bug report, site support request or you are not completely sure provide the full verbose output as follows:
youtube-dl -v -o t.out  "https://www.facebook.com/YesThatKevinSmith/videos/10153977324206930/"
[debug] System config: []
[debug] User config: []
[debug] Command-line args: [u'-v', u'-o', u't.out', u'https://www.facebook.com/YesThatKevinSmith/videos/10153977324206930/']
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2016.12.12-gentoo_no_offensive_sites (confirmed in latest live 9999 ebuild/commit also)
[debug] Python version 2.7.12 - Linux-4.4.26-gentoo-x86_64-AMD_Phenom-tm-_9850_Quad-Core_Processor-with-gentoo-2.3
[debug] exe versions: ffmpeg 3.2.2, ffprobe 3.2.2, rtmpdump 2.4
[debug] Proxy map: {}
[facebook]<PHONE_NUMBER>4206930: Downloading webpage
[facebook]<PHONE_NUMBER>4206930: Downloading webpage
[debug] Invoking downloader on u'https://video.xx.fbcdn.net/hvideo-frc1/v/dash-abr1/10153977324231930.mpd?_nc_rl=AfDeJiUm0OgCdFjV&oh=bbe9ff443988d7923f64d4a3ca1e3638&oe=58614952'
[download] Destination: t.out
[download] 100% of 3.83KiB in 00:00
<?xml version="1.0"?>
<MPD
    type="dynamic"
    xmlns="urn:mpeg:dash:schema:mpd:2011"
    availabilityStartTime="2016-12-24T19:35:41-08:00"
    availabilityEndTime="2016-12-24T19:53:25-08:00"
    publishFrameTime="1021"
    minimumUpdatePeriod="PT1S"
    minBufferTime="PT1S"
    timeShiftBufferDepth="P00Y00M00DT00H00M10.01S"
    suggestedPresentationDelay="PT2S"
    profiles="urn:hbbtv:dash:profile:isoff-live:2012,urn:mpeg:dash:profile:isoff-live:2011"
    xmlns:xsi="http://www.w3.org/2011/XMLSchema-instance"
    xsi:schemaLocation="urn:mpeg:DASH:schema:MPD:2011 DASH-MPD.xsd">
  <Period start="PT0S" id="dash">
    <AdaptationSet
        id="1"
        segmentAlignment="true">
      <Representation
          id="live-md_H264"
          mimeType="video/mp4"
          codecs="avc1.4d401e"
          width="360"
          height="640"
          FBQualityClass="sd"
          FBQualityLabel="360p"
          frameRate="29"
          sar="1:1"
          startWithSAP="1"
          bandwidth="500000">
        <SegmentTemplate
            presentationTimeOffset="0"
            timescale="1000"
            media="../dash-md/10153977324231930-$Time$.m4v"
            initialization="../dash-md/10153977324231930-init.m4v">
          <SegmentTimeline>
             <S t="909942" d="1001"/>
             <S t="910943" d="1001"/>
             <S t="911944" d="1001"/>
             <S t="912945" d="1001"/>
             <S t="913946" d="1001"/>
             <S t="914947" d="1001"/>
             <S t="915948" d="1001"/>
             <S t="916949" d="1001"/>
             <S t="917950" d="1001"/>
             <S t="918951" d="1001"/>
          </SegmentTimeline>
        </SegmentTemplate>
      </Representation>
      <Representation
          id="live-ld_H264"
          mimeType="video/mp4"
          codecs="avc1.4d401e"
          width="240"
          height="426"
          FBQualityClass="sd"
          FBQualityLabel="240p"
          frameRate="29"
          sar="1:1"
          startWithSAP="1"
          bandwidth="250000">
        <SegmentTemplate
            presentationTimeOffset="0"
            timescale="1000"
            media="../dash-ld/10153977324231930-$Time$.m4v"
            initialization="../dash-ld/10153977324231930-init.m4v">
          <SegmentTimeline>
             <S t="909942" d="1001"/>
             <S t="910943" d="1001"/>
             <S t="911944" d="1001"/>
             <S t="912945" d="1001"/>
             <S t="913946" d="1001"/>
             <S t="914947" d="1001"/>
             <S t="915948" d="1001"/>
             <S t="916949" d="1001"/>
             <S t="917950" d="1001"/>
             <S t="918951" d="1001"/>
          </SegmentTimeline>
        </SegmentTemplate>
      </Representation>
    </AdaptationSet>
    <AdaptationSet
        id="2"
        segmentAlignment="true">
      <AudioChannelConfiguration
          schemeIdUri="urn:mpeg:dash:23003:3:audio_channel_configuration:2011"
          value="1"/>
      <Representation
          id="live-md_AAC"
          mimeType="audio/mp4"
          codecs="mp4a.40.2"
          audioSamplingRate="48000"
          startWithSAP="1"
          bandwidth="62000">
        <SegmentTemplate
            presentationTimeOffset="0"
            timescale="1000"
            media="../dash-md/10153977324231930-$Time$.m4a"
            initialization="../dash-md/10153977324231930-init.m4a">
          <SegmentTimeline>
             <S t="909942" d="1001"/>
             <S t="910943" d="1001"/>
             <S t="911944" d="1001"/>
             <S t="912945" d="1001"/>
             <S t="913946" d="1001"/>
             <S t="914947" d="1001"/>
             <S t="915948" d="1001"/>
             <S t="916949" d="1001"/>
             <S t="917950" d="1001"/>
             <S t="918951" d="1001"/>
          </SegmentTimeline>
        </SegmentTemplate>
      </Representation>
    </AdaptationSet>
  </Period>
</MPD>

Description of your issue, suggested solution and other information
The MPD extracted or produced is not adding enough information to the manifest for media players to parse in non-verbose mode.  It provides the relative location "../" for media and initialization but not the server/domain or the necessary directories.
There needs to be post-processing of the extracted documents before they are sent out the pipe (to vlc or mplayer) as stdin to another player or dumped to a file.  After it downloads the extracted mpd file, it should use an XML editor or module to inject the base URL  <BaseURL> node with server address into the MPD manifest exactly under the <MPD> node.
 Instead you should just pass the MPD URL to players instead of the document.

The problem is that the mpd url is not disclosed.  It is known by youtube-dl internally but not by the user and the mpd file and the media player.  The user sends the video url but not the MPD url.  People are not reading.

I provide this: https://www.facebook.com/YesThatKevinSmith/videos/10153977324206930/
youtube-dl exposes only in debug mode not production code: https://video.xx.fbcdn.net/hvideo-frc1/v/dash-abr1/10153977324231930.mpd?_nc_rl=AfDeJiUm0OgCdFjV&oh=bbe9ff443988d7923f64d4a3ca1e3638&oe=58614952

The problem is that the mpd url is not disclosed

You can use -g:
MP4Client $(youtube-dl -g "https://www.facebook.com/appledaily.tw/videos/10155432762962069/")

Okay, thanks for clarifying.  But, it should be in the FAQ or man page.

It's indeed on the man page:
-g, --get-url                    Simulate, quiet but print URL


How am I supposed to use Amplify Environment variables in my Lambda @functions?

Which Category is your question related to?
Environment variables, Amplify and Lambda
This is a pretty straightforward feature and question. It has been mentioned in many issues here

https://github.com/aws-amplify/amplify-cli/issues/684
https://github.com/aws-amplify/amplify-cli/issues/678

Or elsewhere:

https://www.reddit.com/r/aws/comments/dia7bn/how_do_you_access_amplify_environment_variables/
https://stackoverflow.com/questions/57446615/creating-process-env-variables-using-aws-amplify

And the terrible documentation does not help, only the first part of it (setting the variables) makes sense.
Here is from where I started, what I went through and what didn't work. Let me know if I have missed something.
Where I started
I wanted to remove the api id from dynamoDB generated tables for @model, in order to have a table name e.g. "project-dev" instead of "Project-6ezfre56g4erg-dev". It would have been much easier, to reference it, especially since I have multiple api using the same table.
As I understood it, Amplify is opinionated and it abstracts the implementation details, we then cannot have both custom data sources and an API generated through the @model directive.
I still tried to update the cloudFormation template of my nested stack to remove the apiId from the table name (GetAttGraphQLAPIApiId) everywhere it was mentionned, but the update rollback:
"TableName": {
                    "Fn::If": [
                        "HasEnvironmentParameter",
                        {
                            "Fn::Join": [
                                "-",
                                [
                                    "Project",
                                    {
                                        "Ref": "GetAttGraphQLAPIApiId"
                                    },
                                    {
                                        "Ref": "env"
                                    }
                                ]
                            ]
                        },

Again, this is a managed approach, so I guess I should comply with it. However, when you offer a managed approach, it should consider that the AppSync data sources are exposed, can be changed, and that it has no consequence on the API. This is very inconsistent with the managed approach and misleading to say the least.
So I needed environment variables to store my table names. I found the documentation, switched to the managed hosting of the frontend apps to have the possibility to add environment variables (no idea why it is mandatory) and defined my env variables at the amplify app level as mentioned here.
I expected these global, app level, env variables to be global env variables. However, as far as I know, they are not. In my lambda workers, I cannot find them at the process.env level. Why are they not inherited? Am I missing something?
I really don't want to manually add to my 50+ lambda workers local env variables, at the lambda level.
I also tried to update the cloudFormation template of the lambda with the same approach than the snippet above but GetAttGraphQLAPIApiId is not available. Since I can't have custom table names, I am back to square one.
Since it seems that Amplify env variables are exposed at build step, I tried to assign them to the backend at the build level in the amplify.yml file. No luck there either, it fails to build if I assign a variable.
I really like Amplify but this issue has made me lose a lot of time and was a real disappointment. I still think I could have missed something so I took the time to write all this. Please consider the effort and let me know how I should proceed to have my env variables available in my lambda workers, or change my tables names to custom names while keeping the @model directive benefits.

@Billybobbonnet Apologize for the confusion out here. Did you try out the amplify update function flow to add the table names generated by the GraphQL transformer (i.e data sources) as environment variables to the function? We provide that flow and it's documented out here -https://docs.amplify.aws/cli/function#function-templates
Unfortunately at this time, the lambda functions generated by the CLI do not inherit the env variables defined in the Amplify Console. The env variables defined in the Amplify console is just used in your build configs and are build time environment variables.

@kaustavghosh06 Thank you for your answer. I'll look into the doc you mentioned.

Unfortunately at this time, the lambda functions generated by the CLI do not inherit the env variables defined in the Amplify Console. The env variables defined in the Amplify console is just used in your build configs and are build time environment variables.

@kaustavghosh06 - is there a feature request ticket for this functionality? And is there a workaround - some better way of centrally managing e.g. a cryptographic secret and automatically getting it into lambdas as an environment variable without putting it into a file that will be in version control?

Any chance this will be picked up in a upcoming release? Becoming a real headache to deal with

@anandsathe67 we're working on this now, unsure of a date but will try to come back soon with something close.

hi @dabit3 do you have a PR or an Issue to track the status of it? many thanks

I need so much this feature. Any update about this?

Any updates? Would be cool to have a native solution

Why is this closed? We are facing similar issues when we want to set env vars...

+1. Bit silly not having this, really.

+1

+1

+1

+1

+1

+1

+1

@dabit3 - there are a lotta prayers being sent into the void here. Is there any update on making this crucial feature work?  If you could check, I would really appreciate it. Thanks!  It would be real nice to have env vars in Lambdas.

@dabit3 - there are a lotta prayers being sent into the void here. Is there any update on making this crucial feature work?  If you could check, I would really appreciate it. Thanks!  It would be real nice to have env vars in Lambdas.

+1

+1

+1

+1

Hey gang.
So, FYI, it's totally possible to manually add ENV vars to the Lambda after it has been created by Amplify, if you just need your Lambda to have access to ENV vars.  I manually copied mine from the Amplify config into the AWS webtop...  Just to get up and running.
Go to Lambda > Functions > Configuration and scroll down to the Environment variables section.  🤦♂  And set your env vars by hand.  That avoids the hassle of inserting them via a script, or having to integrate with AWS Secrets Manager.

Hey gang.
So, FYI, it's totally possible to manually add ENV vars to the Lambda after it has been created by Amplify, if you just need your Lambda to have access to ENV vars. I manually copied mine from the Amplify config into the AWS webtop... Just to get up and running.
Go to Lambda > Functions > Configuration and scroll down to the Environment variables section. 🤦♂ And set your env vars by hand. That avoids the hassle of inserting them via a script, or having to integrate with AWS Secrets Manager.

These will be overwritten by amplify at some point... Trust me, I did this as the first thing, somewhere along the road it will update the CF template and remove them, potentially breaking your applications.

+1

Hi
Any update on this?

Coming back to this since it's a popular topic in order to address some ways to implement environment variables today in Lambda with Amplify (until the CLI implements this feature natively).
There are two main approaches (other than manually adding values in the Lambda console):

If your value is secret, you can use Secrets Manager. To do so, you first need to create a secret in the secrets manager console.

Next, add a statement to the PolicyDocument in amplify/backend/function/<function_name>/.json to give the Lambda function permission to use the secret:
{
  "Effect": "Allow",
  "Action": [
    "secretsmanager:GetSecretValue"
  ],
  "Resource": {
    "Fn::Sub": [
      "arn:aws:secretsmanager:${region}:${account}:secret:key_id",
      {
        "region": {
          "Ref": "AWS::Region"
        },
        "account": {
          "Ref": "AWS::AccountId"
        }
      }
    ]
  }
}

Next, access the token in your function:
const AWS = require('aws-sdk')

const secretsManager = new AWS.SecretsManager()
const secret = await secretsManager.getSecretValue({ SecretId: 'YOUR_KEY' }).promise()

console.log(secret.SecretString)

There are a few approaches outlined in this thread.

If your value is just a configuration value you can configure the CloudFormation configuration locally to set the value - in amplify/backend/function/<function_name>/.json

For this purpose there is a section in the template - Parameters - that you can set.
"Parameters" : {
  "MyKey" : {
    "Type" : "String",
    "Default" : "my-environment-variable"
  }
}

And then use these parameters in Environment declaration:
"Environment":{
   "Variables":{
      "MY_ENV_VAR":{
         "Ref":"MyKey"
      }
   }
}

You can also specify a CFN param in team-provider-info.json under .categories.function. if you want to specify environment-specific parameters

@dabit3 , in the case of using team-provider-info.json, how should the lambda function access the env variable value? Thanks!


Typos in [scalar_fields] eigenvalues.ipynb

Line 161 and 286 in source blob view has minor typos:
You cand learn more about hoy to convert a triangular mesh into a point cloud in the examples/[sampling] notebooks.
You cand learn more about hoy to find neighbors in examples/[neighbors] notebooks.

Hola @k-d1951 ! Thanks for pointing out those typos!
It looks like a very good oportunity for making a litte contribution :)
If you are willing to contribute those changes, don't hesitate in asking doubts


When npm run dev the app crashes

Description

Type: Question

Hi all, i just cloned the repo and tried running the app, but the server keeps crashing and i cant figure out why:
i run: npm run dev -> and this is the output:
`><EMAIL_ADDRESS>dev /Users/horaciogiovine/react-webpack-node

cross-env NODE_ENV=development nodemon

[nodemon] 1.9.2
[nodemon] to restart at any time, enter rs
[nodemon] watching: app/server.jsx app/routes.jsx app/helmconfig.js app/components/Meta.jsx /Users/horaciogiovine/react-webpack-node/server//* /Users/horaciogiovine/react-webpack-node/webpack//*
[nodemon] starting npm run build:dev && npm run babel-node -- server/index.js

<EMAIL_ADDRESS>build:dev /Users/horaciogiovine/react-webpack-node
cross-env NODE_ENV=development webpack --colors --config ./webpack/webpack.config.dev-server.js

Hash: 59794b0cb1aeb79568ba
Version: webpack 1.13.0
Time: 86126ms
Asset     Size  Chunks             Chunk Names
server.js  1.18 MB       0  [emitted]  server
+ 357 hidden modules

<EMAIL_ADDRESS>babel-node /Users/horaciogiovine/react-webpack-node
babel-node --presets es2015,stage-0 --ignore node_modules,public "server/index.js"

===> 😊  Starting Server . . .
===>  Environment: development
===>  Listening on port: 3000
===>  Using DB TYPE: MONGO
events.js:141
throw er; // Unhandled 'error' event
^
Error: listen EADDRINUSE :::3000
at Object.exports._errnoException (util.js:870:11)
at exports._exceptionWithHostPort (util.js:893:20)
at Server._listen2 (net.js:1234:14)
at listen (net.js:1270:10)
at Server.listen (net.js:1366:5)
at EventEmitter.listen (/Users/horaciogiovine/react-webpack-node/node_modules/express/lib/application.js:617:24)
at Object. (index.js:54:5)
at Module._compile (module.js:409:26)
at loader (/Users/horaciogiovine/react-webpack-node/node_modules/babel-cli/node_modules/babel-register/lib/node.js:158:5)
at Object.require.extensions.(anonymous function) [as .js] (/Users/horaciogiovine/react-webpack-node/node_modules/babel-cli/node_modules/babel-register/lib/node.js:168:7)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Function.Module.runMain (module.js:441:10)
at /Users/horaciogiovine/react-webpack-node/node_modules/babel-cli/lib/_babel-node.js:171:48
at Object. (/Users/horaciogiovine/react-webpack-node/node_modules/babel-cli/lib/_babel-node.js:172:7)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Function.Module.runMain (module.js:441:10)
at startup (node.js:139:18)
at node.js:968:3
npm ERR! Darwin 14.1.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "babel-node" "--" "server/index.js"
npm ERR! node v4.4.4
npm ERR! npm  v2.15.1
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>babel-node: babel-node --presets es2015,stage-0 --ignore node_modules,public "server/index.js"
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>babel-node script 'babel-node --presets es2015,stage-0 --ignore node_modules,public "server/index.js"'.
npm ERR! This is most likely a problem with the react-webpack-node package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     babel-node --presets es2015,stage-0 --ignore node_modules,public "server/index.js"
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs react-webpack-node
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!
npm ERR!     npm owner ls react-webpack-node
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     /Users/horaciogiovine/react-webpack-node/npm-debug.log
[nodemon] app crashed - waiting for file changes before starting...`
This is what i get in the console, the npm-debug.log file has the following:
0 info it worked if it ends with ok 1 verbose cli [ '/usr/local/bin/node', 1 verbose cli   '/usr/local/bin/npm', 1 verbose cli   'run', 1 verbose cli   'babel-node', 1 verbose cli   '--', 1 verbose cli   'server/index.js' ] 2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose run-script [ 'prebabel-node', 'babel-node', 'postbabel-node' ] 5 info prebabel-node<EMAIL_ADDRESS>6 info babel-node<EMAIL_ADDRESS>7 verbose unsafe-perm in lifecycle true 8 info<EMAIL_ADDRESS>Failed to exec babel-node script 9 verbose stack Error<EMAIL_ADDRESS>babel-node: babel-node --presets es2015,stage-0 --ignore node_modules,public "server/index.js"9 verbose stack Exit status 1 9 verbose stack     at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/lifecycle.js:217:16) 9 verbose stack     at emitTwo (events.js:87:13) 9 verbose stack     at EventEmitter.emit (events.js:172:7) 9 verbose stack     at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/spawn.js:24:14) 9 verbose stack     at emitTwo (events.js:87:13) 9 verbose stack     at ChildProcess.emit (events.js:172:7) 9 verbose stack     at maybeClose (internal/child_process.js:827:16) 9 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5) 10 verbose pkgid<EMAIL_ADDRESS>11 verbose cwd /Users/horaciogiovine/react-webpack-node 12 error Darwin 14.1.0 13 error argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "babel-node" "--" "server/index.js" 14 error node v4.4.4 15 error npm  v2.15.1 16 error code ELIFECYCLE 17 error<EMAIL_ADDRESS>babel-node:babel-node --presets es2015,stage-0 --ignore node_modules,public "server/index.js"17 error Exit status 1 18 error Failed at the<EMAIL_ADDRESS>babel-node script 'babel-node --presets es2015,stage-0 --ignore node_modules,public "server/index.js"'. 18 error This is most likely a problem with the react-webpack-node package, 18 error not with npm itself. 18 error Tell the author that this fails on your system: 18 error     babel-node --presets es2015,stage-0 --ignore node_modules,public "server/index.js" 18 error You can get information on how to open an issue for this project with: 18 error     npm bugs react-webpack-node 18 error Or if that isn't available, you can get their info via: 18 error 18 error     npm owner ls react-webpack-node 18 error There is likely additional logging output above. 19 verbose exit [ 1, true ]
Does anyone know why this happens and how can i fix it? btw, i cloned from master.
Thanks in advance

@horacio-giovine did you resolve this? i'm getting the same error.

Do you have other node projects running? Error: listen EADDRINUSE :::3000 means that the port is already serving something.  I would checkout http://localhost:3000/ and see what you have running, and maybe restart your computer.


Add configuration examples section

Adds example to disable hashed asset filenames, as discussed in #1649
Adds example of disabling the generation of index.html, as discussed in #1478
Adds a tip about not needing to use assetsDir when overriding filename or chunkFilename, as discussed in #1753

I like this.
While the Guide contains a few examples of the general approach, there sure are some adjustments that people tend to ask for quite often, so a collection of those does make sense.


Caldera Login 405 Method Not Allowed

Hi there,
Deployed BAS and Win1 instances via terraform, login screen for Caldera comes up on public IP on port 8888. Attempting to login with credentials from Terraform output but not getting past login screen.
Ran Dev Tools and can see I'm getting a 405 Method Not Allowed in the request.  I tried from the Win1 instance via RDP and getting the same error from the Private IP on port 8888.  Thought it might be the haproxy.conf but thats not explicitly denying or defining any methods.  Something i've done wrong or perhaps something in the AWS config ?  I simply deployed with terraform apply --auto-approve
I'll keep investigating but just thought I'd reach out and see if anyone might know why

Hi @MattRamsey, thanks for reporting this.
Please do a pull from the latest code and let me know if it now works.  I fixed an issue yesterday:
https://github.com/iknowjason/AutomatedEmulation/issues/4
The implementation broke from a Caldera change.  Now the transport should be https on port 8443.

@iknowjason that worked and I'm able to login now.  Should've checked the repo activity more closely :)
Thanks for the support, and for the project.  This is more than a considerable amount of effort


Add support for using .NET Aspire Dashboard (Standalone) as alternative observability stack

The .NET Aspire Dashboard could also act as single container observability stack. Compared to PLG and other stacks, standalone .NET Aspire Dashboard is way more lightweight.
After looking at the current implementation, I would prefer adding a single flag to spin otel setup. If the flag is present, a different compose.yaml file will be used. I would introduce a simple Stack type, to make this extensible (simplifies adding additional observability stacks in the future).
Other commands should not be affected from this change, as we will still leverage underlying docker compose.

.NET Aspire Dashboard supports header based authentication for its OTLP(s) endpoint. However, Spin does not support this yet.
I've created a corresponding issue at https://github.com/fermyon/spin/issues/2880
Although we could run .NET Aspire Dashboard without using authentication for its OTLP endpoint(s), users will be presented with a prominent warning in the dashboard UI.


Fixed xContent dependencies due to OSCore changes

Issue #, if available:
https://github.com/opensearch-project/alerting/issues/837
Description of changes:
Fixed xContent dependencies due to OSCore changes
CheckList:

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #839 (8d2a692) into 2.x (1bc8c82) will increase coverage by 0.34%.
The diff coverage is 89.14%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@             Coverage Diff              @@
##                2.x     #839      +/-   ##
============================================
+ Coverage     75.82%   76.17%   +0.34%
  Complexity      116      116
============================================
  Files           125      125
  Lines          6868     7050     +182
  Branches       1031     1031
============================================
+ Hits           5208     5370     +162
- Misses         1135     1153      +18
- Partials        525      527       +2

Impacted Files
Coverage Δ

...pensearch/percolator/PercolateQueryBuilderExt.java
30.16% <ø> (ø)

...pensearch/percolator/PercolatorFieldMapperExt.java
76.33% <ø> (ø)

...n/kotlin/org/opensearch/alerting/AlertingPlugin.kt
93.75% <ø> (ø)

...ensearch/alerting/MonitorRunnerExecutionContext.kt
100.00% <ø> (ø)

...in/org/opensearch/alerting/MonitorRunnerService.kt
82.00% <ø> (+2.00%)
:arrow_up:

...ensearch/alerting/action/ExecuteMonitorResponse.kt
100.00% <ø> (ø)

...nsearch/alerting/action/GetDestinationsResponse.kt
100.00% <ø> (ø)

...pensearch/alerting/model/AlertingConfigAccessor.kt
75.00% <ø> (ø)

...arch/alerting/model/BucketLevelTriggerRunResult.kt
90.00% <ø> (ø)

...ch/alerting/model/DocumentLevelTriggerRunResult.kt
85.00% <ø> (ø)

... and 65 more

... and 1 file with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

Security Test Workflows failed due to docker not coming up, since 2.7 security and PA has not been not built into the last 2.7 distribution build yet.


bump version to 2020.11.3

Issue Number

Overview

[ ] I have ...

Comments

Should we wait for a patch release of cardano-addresses? Because it can't be built with cabal currently due to https://github.com/input-output-hk/cardano-addresses/commit/8ececd0d7c0ed6e0c654ff94dac8ad91a5ad596a#diff-3ff3d7b39854fd35883974ce0822dd5a599e98e093b8079419e9ecf21a7c6000

@hasufell I think there is some more time for cardano-addresses release. There is one PR to be merged (should be merged around tomorrow), but also prefixes PR (HRPs compliant with CIP5) waits for be done <- @KtorZ

bors r+


evm_tokens: fix potential nil-pointer dereference

On Testnet Production:
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x1109189]

goroutine 70736 [running]:
github.com/oasisprotocol/oasis-indexer/analyzer/evmtokens.Main.processStaleToken({{0x14cb622, 0x8}, {0x18b5680, 0xc000450a30}, {0x18bbc40, 0xc0003a6370}, 0xc0006ac4e0}, {0x18b39b0, 0xc000922f80}, 0xc000b771e0, ...)
        /code/go/analyzer/evmtokens/evm_tokens.go:122 +0x449
github.com/oasisprotocol/oasis-indexer/analyzer/evmtokens.Main.processBatch.func1()
        /code/go/analyzer/evmtokens/evm_tokens.go:170 +0x4e
golang.org/x/sync/errgroup.(*Group).Go.func1()
        /go/pkg/mod/golang.org/x/sync@v0.1.0/errgroup/errgroup.go:75 +0x64
created by golang.org/x/sync/errgroup.(*Group).Go
        /go/pkg/mod/golang.org/x/sync@v0.1.0/errgroup/errgroup.go:72 +0xa5

Looking at the code, the EVMDownloadNewToken can return EVMTokenTypeUnsupported which will cause tokenData.TotalSupply to be nil (so shouldn't call .String() on it without checking): https://github.com/oasisprotocol/oasis-indexer/blob/f33b4a9558b4d5736af5c137592ed951cf1c0fff/analyzer/runtime/evm/client.go#L243

Don't have a lot of context about the code around here, so I just pushed a minimal change to avoid the nil pointer here.

testnet, was this emerald? can we figure out the height and/or contract address? the ERC spec says the total supply is required. we're meant to treat the contract as not ERC-20 if the total supply is not supported

was this emerald

Looking at the DB it looks like this is sapphire. (there is no stale emerald tokens found if running the RuntimeEVMTokenAnalysisStale query).
Also, a lot of "ERC20 call failed" errors in the logs:
2023-06-05T05:31:41.558081128Z {"analyzer":"evm_tokens_sapphire","caller":"client.go:180","err":"runtime client evm simulate call: rpc error: code = Canceled desc = context canceled","level":"info","method":"name","module":"analysis_service","msg":"ERC20 call failed","round":1454725,"token_eth_addr_hex":"ed33e0bb03fefd0f343f634c3f40a5f6839753f2","ts":"2023-06-05T05:31:41.557871724Z"}
2023-06-05T05:31:41.559847210Z {"analyzer":"evm_tokens_sapphire","caller":"client.go:180","err":"runtime client evm simulate call: rpc error: code = Canceled desc = context canceled","level":"info","method":"name","module":"analysis_service","msg":"ERC20 call failed","round":1454725,"token_eth_addr_hex":"d708be8af397cd28b69520db3bd2d92429efb1a8","ts":"2023-06-05T05:31:41.559580189Z"}
2023-06-05T05:31:41.561058059Z {"analyzer":"evm_tokens_sapphire","caller":"client.go:180","err":"runtime client evm simulate call: rpc error: code = Canceled desc = context canceled","level":"info","method":"name","module":"analysis_service","msg":"ERC20 call failed","round":1454725,"token_eth_addr_hex":"8e6b9362275b93c0e4da3662938456dff485604f","ts":"2023-06-05T05:31:41.560914619Z"}
2023-06-05T05:31:47.634407918Z {"analyzer":"evm_tokens_sapphire","caller":"client.go:180","err":"runtime client evm simulate call: roothash: block not found","level":"info","method":"name","module":"analysis_service","msg":"ERC20 call failed","round":1454754,"token_eth_addr_hex":"af0d800b67f2688e4c40e1879537df956f3f1c12","ts":"2023-06-05T05:31:47.634183789Z"}
2023-06-05T05:31:47.634454950Z {"analyzer":"evm_tokens_sapphire","caller":"client.go:180","err":"runtime client evm simulate call: rpc error: code = Canceled desc = context canceled","level":"info","method":"name","module":"analysis_service","msg":"ERC20 call failed","round":1454754,"token_eth_addr_hex":"d239ce2b79f1d9757c6fe6bf44f83bf74a969010","ts":"2023-06-05T05:31:47.634317936Z"}
2023-06-05T05:31:47.634489488Z {"analyzer":"evm_tokens_sapphire","caller":"client.go:180","err":"runtime client evm simulate call: rpc error: code = Canceled desc = context canceled","level":"info","method":"name","module":"analysis_service","msg":"ERC20 call failed","round":1454754,"token_eth_addr_hex":"06f3c5b365c7af22140c1f5cd3f80a43c186df3a","ts":"2023-06-05T05:31:47.634388413Z"}

Also, a lot of "ERC20 call failed" errors in the logs:

Are there any successful ones as well or do they all fail?

It could be that all are failing, not sure how to check actually, I don't think there's anything logged for successful calls. Someone that understands the tokens analysis code should probably check.

If all are failing this likely means that the client node is not configured correctly or is not whitelisted for key manager access. @gw0 do you know?

If all are failing this likely means that the client node is not configured correctly or is not whitelisted for key manager access. @gw0 do you know?

Looks correct. The production testnet-oasis-indexer is using our internal Testnet Sapphire gRPC node. Its P2P pubkey is whitelisted in our Testnet Keymanager nodes.


Moving a view into panel does not distribute size evenly

In this case I would expect output and npm scripts to have the same size:

@sbatten Still happening, is there a reason we cannot distribute the size as shown in the drop feedback?

There are 2 separate problems here.

The NPM Scripts view is collapsed by default and the containers were using this to determine that it should be collapsed when added. This is fixed by the above commit.
The sizing of a view is far removed from the moving of a view so its not trivial to make the sizing right mainly because if we try to manually size the view that's added we must manually size the view that is being shrunk at the same time so the split view doesn't recalculate.

For now, I think fixing one helps the experience a lot, but 2 would be very nice to have.

I do not fully understand the problems, but if it helps: editors have a similar problem, when you open 2 side by side and the sizes are not distributed evenly and you drop a third editor in to have 3 side by side, I simply make all editors the same size.

Yea so the commit above will expand a collapsed view when dropped which will make things much closer to an even split, though it's not perfect.


[BUG]  Incorrect Price Display for Stflow Token

Description:
There is an issue with the price display for the Stflow token in both Flow account and COA, as the current price shown does not accurately reflect the market value.
Current Behavior:
The price displayed for Stflow tokens is 1 in Flow accounts.
The price displayed for Stflow tokens is 0 in COA accounts.

Expected Behavior:
The Stflow token price should accurately reflect the current market value.
API: https://lilico.app/api/v3/evm/[address]/fts?network=mainnet
Steps to Reproduce:
Navigate to the homepage.
Observe the displayed price for Stflow..
Compare it with a reliable market source (e.g., exchange rates).

[BUG] Errors displaying st.FLOW balance
#59

#duplicate


[planning] stopped on top of the crosswalk.

Hi team,
I ran some testings with LGSVL and Apollo 5.0 stack.
and came across this issue where Apollo stopped on top of the crosswalk.
Here's runtime video

video_1
video_2

Here's runtime recording with cyber_recorder
Steps to Reproduce

start Apollo 5.0 docker containers
start bootstrap.sh
open browser, select vehicle Lincoln2017MKZ and map Borregas Ave
cyber_recorder play -f xxx.rec.0000 -l

Expected behavior
When there is a pedestrian crossing, even though it's a green light, Apollo should stop early to give way, instead of braking late and eventually stopped on top of the crosswalk ...
Desktop (please complete the following information):

OS: Ubuntu 1804
Browser chrome

@ntutangyun based on the position/heading/speed of the pedestrian, the predicted trajectory of this pedestrian (the yellow line) crosses ADC's trajectory until ADC gets too close.  If it doesn't cross ADC's trajectory within our planning time scope, planning thinks it would be safe to ignore it. That's why the STOP decision shows up pretty late. There's always improvements(on perception, prediction, and planning) on how we decide when we shall stop for pedestrian. We'll continue to explore it in future release.  BTW, I'm a big fan of JJ, your profile pic LOL.


1.9.0: M+ font rendering

Version 1.9.0 of Atom has introduced some nasty regression with font rendering:

Take a look at "offset": despite using monospace font (it's M+ 1mn, size 17), letters 'f' are sticked to each other and occupy 1 space instead of two.
I cannot reproduce it on Liberation Sans Mono or DejaVu Sans Mono, only M+ (https://mplus-fonts.osdn.jp). Downgrading to 1.8.0 solves this, thus running in Safe mode (or with erased configs) makes no sense. Atom 1.9.7 also contains this bug.
Xubuntu 14.04.5 64-bit.

I suspect this is a "problem" with the font you use. So-called ligatures can provide additional value even with monospaced fonts, and they are enabled by default in Atom 1.9+. If you use the free font Fira Code, for example, it uses ligatures a lot to improve legibility. You font seems to have ligatures enabled, but uses them incorrectly - ff is a common "traditional" ligature, such as ft and st, for example.
You can try to disabled ligatures in Atom (maybe these instructions for enabling ligatures will help), or you use an updated version of the font, where this ligature has been disabled.
I hope this helps a bit.

@bernharduw, disabling ligatures solves this. So you're right, it's not Atom problem but M+ font feature. Thanks!
Issue is incorrect itself, closing.


Create MIRO fields images.csv

What is this PR trying to achieve?
Adding to the spreadsheet summarising MIRO fields some new information that clarifies the distinction between the Catalogue 1 and Catalogue 2 areas and particularly the various Description fields.
Who is this change for?
All Platform team
Have the following been considered/are they needed?

Thank you!
From: Robert Kenny<EMAIL_ADDRESS>Sent: 13 June 2017 17:48
To: wellcometrust/platform-api
Cc: Christopher Hilton; Author
Subject: Re: [wellcometrust/platform-api] Create MIRO fields images.csv (#404)
@kenoir approved this pull request.
Great small PR! 👍
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/wellcometrust/platform-api/pull/404#pullrequestreview-43785797, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AYNgqnWJTSbKhnaplCElxIReijrYJZqyks5sDr1HgaJpZM4N4eQP.
This message has been scanned for viruses by Websense Hosted Email Security - www.websense.com


[RFC] Make archival asynchronous

The prime benefit being sought here is for large archives to not
clog up the rendering process and cause unsightly proxy timeouts.
As a secondary benefit, archive-in-progress is moved out of the
way into a /tmp file so that new archival requests for the same
commit will not get fulfilled based on an archive that isn't yet
finished.
Fixes #11265
This decidedly needs, at a minimum:

[] Some tests to go with it
[] Perhaps an actual "loading" icon... right now it slaps a loading class on the download icon, sending that sucker spinning.

I've deployed this to my production git instance; the benefit can be seen here: https://git.kevans.dev/kevans/freebsd/branches/ -> any of these branches will take probably 2/3 minutes to finish archiving, so the user experience is slightly improved by making this async. There's a cron job on that instance that will wipe out any generated archives every 15 minutes, so it should be easy to reproduce.
Ultimately, all archival requests get pushed into a queue. The queue handler will asynchronously process all of the requests within it and periodically purge the local archiveInProgress slice. This probably didn't need to be a queue in the end, as we ended up not using the queue very effectively; a later refactor may just move the queue handler into ArchiveRepository().

why deleting them every 15 minutes? imho that is way too fast

why deleting them every 15 minutes? imho that is way too fast

Ah, this is just for testing, since I only have a handful of branches on this repo for easily checking the behavior when a branch takes too long to archive. I can relax this, but the main point was just to invalidate them quickly enough that I don't need to manually purge. =)

Hmm... I've just browsed the code a little, but I think this will affect robots and other automated calls that require the link to resolve itself in the same request. Maybe we should keep the current endpoint for that purpose and use a different URL for the UI.

Hmm... I've just browsed the code a little, but I think this will affect robots and other automated calls that require the link to resolve itself in the same request. Maybe we should keep the current endpoint for that purpose and use a different URL for the UI.

I naively hadn't considered the possibility, but as I had re-assessed what I've done more I did come to realize that the current endpoint didn't really need to change like it did. This seems like a compelling enough reason to fully revert it to being synchronous (enqueue then wait for completion) -- they'd still reap the benefit of never seeing an incomplete archive, even if such a thing would likely timeout the first time they attempted to fetch it.

There's always the option -to a point- of sending a periodic redirect. 😏

Here's a checkpoint with most of your comments, I think, addressed... along with an attempt at fixing the test after re-working waiting for completion.

I applied a little bit of critical thinking and realized that of course the /archive/status endpoint could induce a naming headache... I then applied even more and decided it was worthless anyways, so it's been removed.

Codecov Report

Merging #11296 into master will increase coverage by 0.07%.
The diff coverage is 66.82%.

@@            Coverage Diff             @@
##           master   #11296      +/-   ##
==========================================
+ Coverage   43.84%   43.91%   +0.07%
==========================================
  Files         613      614       +1
  Lines       87221    87374     +153
==========================================
+ Hits        38238    38371     +133
+ Misses      44271    44268       -3
- Partials     4712     4735      +23

Impacted Files
Coverage Δ

routers/repo/repo.go
35.14% <0.00%> (+2.50%)
:arrow_up:

services/archiver/archiver.go
75.70% <75.70%> (ø)

routers/routes/routes.go
86.72% <100.00%> (+0.03%)
:arrow_up:

models/repo_mirror.go
2.12% <0.00%> (-10.64%)
:arrow_down:

modules/git/repo.go
49.79% <0.00%> (-2.52%)
:arrow_down:

modules/queue/unique_queue_disk_channel.go
53.84% <0.00%> (-1.93%)
:arrow_down:

services/pull/pull.go
32.63% <0.00%> (-1.91%)
:arrow_down:

services/mirror/mirror.go
18.75% <0.00%> (-0.66%)
:arrow_down:

modules/notification/webhook/webhook.go
43.00% <0.00%> (-0.59%)
:arrow_down:

models/issue.go
51.94% <0.00%> (-0.47%)
:arrow_down:

... and 9 more

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 091d053...091d053. Read the comment docs.

Codecov Report

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

@@           Coverage Diff           @@
##           master   #11296   +/-   ##
=======================================
  Coverage   43.92%   43.92%
=======================================
  Files         614      614
  Lines       87374    87374
=======================================
  Hits        38379    38379
  Misses      44262    44262
  Partials     4733     4733

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 091d053...091d053. Read the comment docs.

Thanks for the feedback- I'm hoping to drum up some time this week to incorporate it. =)

Following discussion with @zeripath on Discord (Thanks!), I've simplified the logic that ensures we aren't blocking shutdown to remove the new channels and extra goroutines.

Hi @kevans91 how's this PR progressing?

Hi @kevans91 how's this PR progressing?

As far as I'm aware, I've addressed all of the feedback and am awaiting further review- I'd left one unresolved because I wasn't sure if the solution was satisfactory or not. We discussed it a bit, now I'm just unsure if I need to change those to use a different context (re: #12560

Please resolve conflicts

Heh, a minute after I pushed a version with conflicts resolved, another set of conflicts popped up. =D
I think I've reconciled the differences correctly; WaitForCompletion/TimedWaitForCompletion now use Done() channels on the request context, and the service itself passes shutdown context to CreateArchive().

:rocket:

Codecov Report

Merging #11296 (c93c520) into master (1b65536) will increase coverage by 0.16%.
The diff coverage is 67.06%.

@@            Coverage Diff             @@
##           master   #11296      +/-   ##
==========================================
+ Coverage   42.01%   42.17%   +0.16%
==========================================
  Files         692      693       +1
  Lines       75985    76098     +113
==========================================
+ Hits        31924    32095     +171
+ Misses      38839    38746      -93
- Partials     5222     5257      +35

Impacted Files
Coverage Δ

routers/repo/repo.go
32.63% <0.00%> (+3.63%)
:arrow_up:

services/archiver/archiver.go
77.14% <77.14%> (ø)

routers/routes/routes.go
84.41% <100.00%> (+0.05%)
:arrow_up:

models/repo_mirror.go
2.38% <0.00%> (-11.91%)
:arrow_down:

modules/secret/secret.go
66.66% <0.00%> (-7.41%)
:arrow_down:

modules/cron/tasks_basic.go
87.35% <0.00%> (-3.45%)
:arrow_down:

modules/git/utils.go
73.77% <0.00%> (-3.28%)
:arrow_down:

modules/git/blame.go
75.43% <0.00%> (-1.76%)
:arrow_down:

modules/queue/unique_queue_disk_channel.go
53.84% <0.00%> (-1.54%)
:arrow_down:

services/pull/check.go
49.63% <0.00%> (-1.46%)
:arrow_down:

... and 15 more

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 1b65536...c93c520. Read the comment docs.


Added link for Algorithm analysis

Hey, it seems to be conflicting with the main branch. would you look after this issue.
Thanks a lot for your contribution.
Looking forward for more such resources which helps others and make the community grow. ❤

Updated...Please have a look now.
On Wed, 12 Oct 2022 at 01:00, Debraj Karmakar @.***>
wrote:

Assigned #186
https://github.com/debrajhyper/Topic_Learning_Resources/pull/186 to
@lakshay451 https://github.com/lakshay451.
—
Reply to this email directly, view it on GitHub
https://github.com/debrajhyper/Topic_Learning_Resources/pull/186#event-7565786252,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVKT4ROQS2JDKFHKW3XI4XTWCW54ZANCNFSM6AAAAAARBPIMXU
.
You are receiving this because you were assigned.Message ID:
<debrajhyper/Topic_Learning_Resources/pull/186/issue_event/7565786252@
github.com>


263 produce sex pop estimates scotland

Closes #263 .
Here is an example of what it outputted:

Any feedback is welcome!

Hey @paigeh1 please can you look into making a data cleaning stage that standardizes column values to "Male" and "Female".

We are using local authority boundaries of 2021. Does it make more sense to put the year as 2021 instead of 2011? The lookupfile goes from OA11CD TO LAD21NM and there will be other lookupfiles for other lad years.
I suspect if we put the year as 2011, that is the only estimate that Scotland would get.
Let me know if you have strong opinions on it either way :)

Taken on board James' comment and put it the same as SDG_11.2.1_main.py

Antonio to create an issue to look into sourcing 2011 local authority boundary data.

Ticket created #285 to use 2011 La Boundaries for Scotland.

Happy to merge in. #206 and #285 need to be completed next.


Webviewer: UI Folder / Item Formatting and Widget Fixes

Changes

Add colouring to items and folders which can be set vis CSS. This makes it easier to tell what areas are under what folders.
Close UI advanced folders and close all but first material on load. Both make it so that the drop-down is not really long. Especially for the chess set or any file with more than a few materials which requires a fair bit of scrolling to find the materials (and collapse them).

Fixes

Fix string disable setting (was using old API)
Fix parenting of enum widgets to be under current folder instead of top level.
Restore lost ui advanced code.

Results:

Chess set with multiple materials collapsed
Standard surface w/ advanced collapsed. Coloring also shown
Enum properly parented (Alpha Mode)

Thanks for putting this proposal together, @kwokcb!
I really like the added colors and fixes to API calls, but I'm not as sure about the marking of folders as "Advanced", which has the odd visual impact of making them look like section headers (e.g. making them more visually prominent rather than hiding them).  Since the "Advanced" folder idea likely needs additional visual refinement, perhaps it should be considered a separate proposal?

Sure thing. I'll revert the advanced formatting changes.


The latest version contains security vulnerabilities

Postgres version: 17-alpine3.20
The version is vulnerable because it uses gosu v17 (which uses stdlib v1.18.2):

Is it possible to upgrade the Go stdlib to v1.23?
Thanks

I think this is technically a duplicate of https://github.com/docker-library/postgres/issues/1271 (because "stdlib" is probably your scanner picking up the Go standard library inside the gosu binary).
See especially https://github.com/docker-library/postgres/issues/1271#issuecomment-2356959694, https://github.com/tianon/gosu/blob/4233b796eeb3ba76c8597a46d89eab1f116188e2/SECURITY.md, and https://github.com/docker-library/faq#why-does-my-security-scanner-show-that-an-image-has-cves


Request: Pull the pinned shortcuts in the sidebar to rearrange the sequence

Is your feature request related to a problem? Please describe.
I added several paths to be pinned to sidebar, but it's ordering by the pinned time, and I cannot change the sequence by pulling the items.
Describe the solution you'd like
Pull the items to rearrange the sequence, like the win10 build-in file explorer.
Describe alternatives you've considered
Right click on the items pinned to sidebar, select up or down in the right-click menu. (Sorry, I don't know the term in English...)
Additional context
None. By the way, thanks for your application! It's wonderful!

Merging with #1069