add Share component

Closed, it is better for this type of components to be created by the developers as it is not slide-related.


Multiline lists not recognised

Where my scripts use multiline lists, they are flagged as invalid.  Here’s an example:
specialdirs=(
                var/log/*
                var/run/*
)

The open paren is flagged as “unexpected token”; the close parens is tagged “Expected a command”.

Which version of BashSupport do you use?
I can't reproduce this here with the latest version. The error may happen if the code is inside of other elements like subshells, if statements, etc.

On 30 Jan 2016, at 07:20, J. Ansorg<EMAIL_ADDRESS>wrote:
Which version of BashSupport do you use?

I’m using BashSupport <IP_ADDRESS>

I can't reproduce this here with the latest version. The error may happen if the code is inside of other elements like subshells, if statements, etc.

I’ve just had a look at the shell file and I’ve discovered that it’s wrapped in an outer set of brackets to redirect the output of all the commands.  This does produce the error.  I’ll attach the script.
Thanks for looking into it and getting in touch with me.  It makes me want to report more issues.
Ben.

Fixed for the next update.


When i go back(Poptoview) application was crash

Can you give me your consle log ?

@MillmanY  i resolve this issue. Thanks .


fix for Invalid Hook Call error

Fix for the Invalid Hook Call error https://github.com/VamOSGS/react-preloaders/issues/28
Problem:
The possible cause is that there is a duplicate React library.
Solution:
We transfer the React to the peerDependencies section
@VamOSGS

Fix for the Invalid Hook Call error #28
Problem:
The possible cause is that there is a duplicate React library.
Solution:
We transfer the React to the peerDependencies section
@VamOSGS

How do we transfer React to peerDependencies section?

@Afn377  check the changed files.... @VamOSGS please check this PR. Thanks


Resolve strict dependencies from Ivy repositories

See #3462

@bigdaz I have addressed all comments, except for the redundant code in MavenDependencyMetadata, which I think can be solved separately. Build passes. I will address latest.status in a subsequent PR, I need this one to make progress on test fixtures.


DXF defective if it contains an Ellipse

In one of our programs, I noticed the created dxf seems to be defetive sometimes. AutoCAD (2020, 2021) can't open those dxfs. I've also tried to open the files with QGIS 3.10. QGIS seems to be a little bit more tolerant, sometimes it is able to open those files, sometimes not.
To me, it looks like it always happens, when the dxf contains Ellipses. See my minimal working example.
It creates two dxfs: one containing only a Line. The resulting dxf can be opened with AutoCAD. The other one only contains an Ellipse with Color red. This dxf cannot be opened with AutoCAD. I also attached both dxfs. I don't see any exceptions, return value of doc.Save(..) is always true.
Tried it with versions netDxf 2.2.1 and netDxf.standard 2.4.0, both from nuget.org.
Is this an issue with netDxf or with the dxf-consuming software?
static void Main(string[] args)
{
  var docDefective = new DxfDocument(DxfVersion.AutoCad2013);
  Ellipse ellipse = new Ellipse(new Vector2(105.4387, 321.6599), 0.3, 6);
  ellipse.Color = new AciColor(0, 0, 255);
  docDefective.AddEntity(ellipse);
  var result = docDefective.Save($"c:\\users\\{Environment.UserName}\\desktop\\defective.dxf");
  Console.WriteLine(result);

  var docOk = new DxfDocument(DxfVersion.AutoCad2013);
  Line l = new Line(new Vector2(105.4387, 321.6599), new Vector2(205.4387, 321.6599));
  docOk.AddEntity(l);
  result = docOk.Save($"c:\\users\\{Environment.UserName}\\desktop\\ok.dxf");
  Console.WriteLine(result);
}

dxfs.zip

This is what AutoCAD 2021 (german) says when loading defective.dxf:

Folgender Fehler wurde beim Lesen
in ELLIPSE beginnend bei Zeile 1068 ermittelt:
Unzulässige Daten für Ellipsendefinition
Ungültige oder unvollständige DXF-Eingabe -- Zeichnung abgebrochen.

Translated:

The following error occurred while reading
determined in ELLIPSE starting at line 1068:
Invalid data for ellipse definition
Invalid or incomplete DXF input - drawing aborted.

The Ellipse entity works fine, but the major axis, as its names implies, must be greater than the minor axis.

Thanks.
Would you mind throwing some kind of ArgumentException in this case?


if NodeClaims are not satisfied, Karpenter still create the NIC and does no delete it

Version

Karpenter Version: 0.29.2

Kubernetes Version: v1.27.7
Expected Behavior
When a NodeClaim cant be satisfied and is removed, the NIC should not be created or deleted afterwards.
Actual Behavior
Karpenter creates and deletes the NodeClaims but does not remove the NIC. So you end up with a lot of NICs in the MC_ resource group.
Steps to Reproduce the Problem
run kubectl scale deploy inflate --replicas 300 -n default and  watch the Karpenter pods logs, you will see for example this error: \"error\": {\n    \"code\": \"OperationNotAllowed\",\n    \"message\": \"Operation could not be completed as it results in exceeding approved Total Regional Cores quota. Additional details - Deployment Model: Resource Manager, Location: northeurope, Current Limit: 65, Current Usage: 54, Additional Required: 96, (Minimum) New Limit Required: 150.
Karpenter creates the NodeClaim and you will see them appear and disappear (kubectl get nodeclaim -w). For every NodeClaim a NIC is created but not deleted. So you end up with a lot of NICs in the MC_ resource group.
Resource Specs and Logs
{"level":"ERROR","time":"2023-12-15T21:40:08.562Z","logger":"controller.nodeclaim.lifecycle","message":"creating instance, insufficient capacity, regional on-demand vCPU quota limit for subscription has been reached. To scale beyond this limit, please review the quota increase process here: https://learn.microsoft.com/en-us/azure/quotas/regional-quota-requests","commit":"76a3b5a-dirty","nodeclaim":"general-purpose-rmshj","nodepool":"general-purpose"}
{"level":"INFO","time":"2023-12-15T21:40:08.601Z","logger":"controller.nodeclaim.termination","message":"deleted nodeclaim","commit":"76a3b5a-dirty","nodeclaim":"general-purpose-rmshj","nodepool":"general-purpose","node":"","provider-id":""}
Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

@philwelz  I have the fix in the linked pr if you want to take a look!

Thanks @Bryce-Soghigian ! As im not that good at Go i deployed from your branch and the issue is still the same :( from the logs i could see this should be the correct version with your fix : "commit":"0f27f21-dirty" and your fix is https://github.com/Azure/karpenter/commit/0f27f212b19a1392a14db81576391bf43a4f67f8 .

Hey @philwelz, I just pushed some new code, seems we have gotten past the extra sad case, but there is another error I caught as well.
Fix for Leftover NICs in Karpenter
Here is an initial write up of the testing I performed.
Scale Up Operations
We conducted 2 scale-up operations. The first scale up to 10 nodes took 55 seconds, with the readiness of the nodes monitored with the very official benchmark of spamming k get nodeclaims until we saw all of them were ready.
~/dev/karpenter (bsoghigian/nic-fix*) » k get nodeclaims.karpenter.sh                                             sillygoose@Bryces-MacBook-Pro
NAME                       TYPE               ZONE       NODE                           READY   AGE
sm-general-purpose-4c4mg   Standard_D2ls_v5   eastus-2   aks-sm-general-purpose-4c4mg   True    55s
sm-general-purpose-52hbw   Standard_D2ls_v5   eastus-3   aks-sm-general-purpose-52hbw   True    55s
sm-general-purpose-7bwx5   Standard_D2ls_v5   eastus-3   aks-sm-general-purpose-7bwx5   True    55s
... Removed 7 nodes for brevity

Subsequent scale-ups were performed to 100 nodes:
~/dev/karpenter (bsoghigian/nic-fix*) » k get nodes | wc -l                                                       sillygoose@Bryces-MacBook-Pro
     100

Checking for Ghost NICs
Checking, I hit the Quota error 78 times in this scale up run
~/dev/karpenter (bsoghigian/nic-fix*) » k logs -n karpenter karpenter-769b948689-dnc8d| grep OperationNotAllowed | wc -
      78

To check for ghost NICs at 100 nodes, I looked at the portal, checked with a script, and with make az-resc.
I only see 1 ghost NIC, whereas with the previous logic we would see 78, one for each failure to provision the vm.
~/dev/karpenter (bsoghigian/nic-fix*) » ./nic.sh                                                                  sillygoose@Bryces-MacBook-Pro
NICs without a VM in the resource group 'MC_storagetest2_karpenter8_eastus':
"/subscriptions/(redacted-subscription)/resourceGroups/MC_storagetest2_karpenter8_eastus/providers/Microsoft.Network/networkInterfaces/aks-sm-general-purpose-6wtkg"

While its nice to see the improvement, what is the root cause for the single ghost nic?
Grepping through the karpenter logs for this resource aks-sm-general-purpose-6wtkg, It looks like we ran into a new Error Code NicReservedForAnotherVm. Here is the full breakdown of actions we took on the aks-sm-general-purpose-6wtkg NIC, VM, and machine.
Steps taken on aks-sm-general-purpose-6wtkg from Karpenter Log

Creating Network Interface (Success)

Timestamp: 2023-12-17T05:31:18.458Z
Operation: Creation of a network interface named aks-sm-general-purpose-6wtkg.
Status: Successful creation of the network interface.

Creating Virtual Machine (Initial Attempt)

Timestamp: 2023-12-17T05:31:20.158Z
Operation: Attempt to create a virtual machine named aks-sm-general-purpose-6wtkg, with the specification Standard_D2ls_v5.
Status: Initial attempt, status not yet known from this log entry.

Error in Creating Virtual Machine (Quota Exceeded)

Timestamp: 2023-12-17T05:31:20.555Z
Operation: Creation of the virtual machine aks-sm-general-purpose-6wtkg.
Error: The operation failed due to exceeding the approved quota for standardDLSv5Family Cores. The current limit is 100, and the creation of this VM would require an additional 2 cores, bringing the required total to 102.
Action Required: A quota increase request is necessary, with instructions to submit it via a provided URL.

Error Deleting Network Interface (Reserved NIC)

Timestamp: 2023-12-17T05:31:20.841Z
Operation: Attempt to delete the network interface aks-sm-general-purpose-6wtkg.
Error: Failure due to the network interface being reserved for another Virtual Machine for 180 seconds. This implies that the network interface cannot be deleted immediately as it is temporarily locked or reserved.

{"level":"DEBUG","time":"2023-12-17T05:31:18.458Z","logger":"controller.nodeclaim.lifecycle","message":"Creating network interface aks-sm-general-purpose-6wtkg","commit":"25adaf2-dirty","nodeclaim":"sm-general-purpose-6wtkg","nodepool":"sm-general-purpose"}
{"level":"DEBUG","time":"2023-12-17T05:31:20.158Z","logger":"controller.nodeclaim.lifecycle","message":"Successfully created network interface: /subscriptions/(subscription-redacted)/resourceGroups/MC_storagetest2_karpenter8_eastus/providers/Microsoft.Network/networkInterfaces/aks-sm-general-purpose-6wtkg","commit":"25adaf2-dirty","nodeclaim":"sm-general-purpose-6wtkg","nodepool":"sm-general-purpose"}
{"level":"DEBUG","time":"2023-12-17T05:31:20.158Z","logger":"controller.nodeclaim.lifecycle","message":"Creating virtual machine aks-sm-general-purpose-6wtkg (Standard_D2ls_v5)","commit":"25adaf2-dirty","nodeclaim":"sm-general-purpose-6wtkg","nodepool":"sm-general-purpose"}
{"level":"ERROR","time":"2023-12-17T05:31:20.555Z","logger":"controller.nodeclaim.lifecycle","message":"Creating virtual machine \"aks-sm-general-purpose-6wtkg\" failed: PUT https://management.azure.com/subscriptions/(subscription-redacted)/resourceGroups/MC_storagetest2_karpenter8_eastus/providers/Microsoft.Compute/virtualMachines/aks-sm-general-purpose-6wtkg\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: OperationNotAllowed\n--------------------------------------------------------------------------------\n{\n  \"error\": {\n    \"code\": \"OperationNotAllowed\",\n    \"message\": \"Operation could not be completed as it results in exceeding approved standardDLSv5Family Cores quota. Additional details - Deployment Model: Resource Manager, Location: eastus, Current Limit: 100, Current Usage: 100, Additional Required: 2, (Minimum) New Limit Required: 102. Submit a request for Quota increase at https://aka.ms/ProdportalCRP/#blade/Microsoft_Azure_Capacity/UsageAndQuota.ReactView/Parameters/%7B%22subscriptionId%22:%22(subscription-redacted)%22,%22command%22:%22openQuotaApprovalBlade%22,%22quotas%22:[%7B%22location%22:%22eastus%22,%22providerId%22:%22Microsoft.Compute%22,%22resourceName%22:%22standardDLSv5Family%22,%22quotaRequest%22:%7B%22properties%22:%7B%22limit%22:102,%22unit%22:%22Count%22,%22name%22:%7B%22value%22:%22standardDLSv5Family%22%7D%7D%7D%7D]%7D by specifying parameters listed in the ‘Details’ section for deployment to succeed. Please read more about quota limits at https://docs.microsoft.com/en-us/azure/azure-supportability/per-vm-quota-requests\"\n  }\n}\n--------------------------------------------------------------------------------\n","commit":"25adaf2-dirty","nodeclaim":"sm-general-purpose-6wtkg","nodepool":"sm-general-purpose"}
{"level":"ERROR","time":"2023-12-17T05:31:20.555Z","logger":"controller.nodeclaim.lifecycle","message":"virtualMachine.BeginCreateOrUpdate for VM \"aks-sm-general-purpose-6wtkg\" failed: PUT https://management.azure.com/subscriptions/(subscription-redacted)/resourceGroups/MC_storagetest2_karpenter8_eastus/providers/Microsoft.Compute/virtualMachines/aks-sm-general-purpose-6wtkg\n--------------------------------------------------------------------------------\nRESPONSE 409: 409 Conflict\nERROR CODE: OperationNotAllowed\n--------------------------------------------------------------------------------\n{\n  \"error\": {\n    \"code\": \"OperationNotAllowed\",\n    \"message\": \"Operation could not be completed as it results in exceeding approved standardDLSv5Family Cores quota. Additional details - Deployment Model: Resource Manager, Location: eastus, Current Limit: 100, Current Usage: 100, Additional Required: 2, (Minimum) New Limit Required: 102. Submit a request for Quota increase at https://aka.ms/ProdportalCRP/#blade/Microsoft_Azure_Capacity/UsageAndQuota.ReactView/Parameters/%7B%22subscriptionId%22:%22(subscription-redacted)%22,%22command%22:%22openQuotaApprovalBlade%22,%22quotas%22:[%7B%22location%22:%22eastus%22,%22providerId%22:%22Microsoft.Compute%22,%22resourceName%22:%22standardDLSv5Family%22,%22quotaRequest%22:%7B%22properties%22:%7B%22limit%22:102,%22unit%22:%22Count%22,%22name%22:%7B%22value%22:%22standardDLSv5Family%22%7D%7D%7D%7D]%7D by specifying parameters listed in the ‘Details’ section for deployment to succeed. Please read more about quota limits at https://docs.microsoft.com/en-us/azure/azure-supportability/per-vm-quota-requests\"\n  }\n}\n--------------------------------------------------------------------------------\n","commit":"25adaf2-dirty","nodeclaim":"sm-general-purpose-6wtkg","nodepool":"sm-general-purpose"}
{"level":"ERROR","time":"2023-12-17T05:31:20.841Z","logger":"controller.nodeclaim.lifecycle","message":"networkInterface.Delete for aks-sm-general-purpose-6wtkg failed: DELETE https://management.azure.com/subscriptions/(subscription-redacted)/resourceGroups/MC_storagetest2_karpenter8_eastus/providers/Microsoft.Network/networkInterfaces/aks-sm-general-purpose-6wtkg\n--------------------------------------------------------------------------------\nRESPONSE 400: 400 Bad Request\nERROR CODE: NicReservedForAnotherVm\n--------------------------------------------------------------------------------\n{\n  \"error\": {\n    \"code\": \"NicReservedForAnotherVm\",\n    \"message\": \"Nic(s) in request is reserved for another Virtual Machine for 180 seconds. Please provide another nic(s) or retry after 180 seconds. Reserved VM: /subscriptions/(subscription-redacted)/resourceGroups/MC_storagetest2_karpenter8_eastus/providers/Microsoft.Compute/virtualMachines/aks-sm-general-purpose-6wtkg\",\n    \"details\": []\n  }\n}\n--------------------------------------------------------------------------------\n","commit":"25adaf2-dirty","nodeclaim":"sm-general-purpose-6wtkg","nodepool":"sm-general-purpose"}

Summary
With the change, we fix most of the NIC errors, but still need to have some followup work seeing the best way to deal with NicReservedForAnotherVm. I want to do some additional testing on the old code, just to show the contrast in my statement of their being 78 ghost nics, for each vm creation error vs the 1 ghost nic.

I have a couple of additional scenarios I want to test, but wanted to share progress here.

hey @Bryce-Soghigian , when calling make az-resc you do net get all nics as they do not have correct label. I added an PR to fix that: https://github.com/Azure/karpenter/pull/74

@philwelz  merging in this change, should significantly improve the scenario, there is still an edgecase but it wont leave 100s of nics now


Add Owner : check if already owner before adding.

on /ManagePackageOwners there is not dup check.

Current Owners
•aldion
•aldionRemove
•aldionRemove
•aldionRemove

This is being checked since August 2013, time to close the issue :)


Create last-stand-timer

This simple plugin adds a 3min timer when the player dies.
This is made to give players an indication when their last stand timer is about to come up.

See https://github.com/runelite/plugin-hub/pull/7091#issuecomment-2510201293


Card section with images – icon placement

Detailed description
Describe in detail the issue you're having.
The icon in the card is 4px off in alignment, it should be pinned to the bottom left edge.
It looks like the footer area is 24px tall and the 20x20px icon is top aligned in that container.

Is this a feature request (new component, new icon), a bug, or a general issue?
Bug / design defect
Is this issue related to a specific component?
Cards used within Card section with images
What did you expect to happen? What happened instead? What would you like to see changed?
Icon should align to the bottom margin of the card.
What browser are you working in?
Chrome
What version of the IBM.com Library are you using?
What offering/product do you work on? Any pressing ship or release dates we should be aware of?
Web simplification
Steps to reproduce the issue

Step one
Step two
Step three
etc.

Additional information
I had a discussion with Wonil, Lara, Jeff and Kenny about how we are using icons in the components and patterns and if we need to implement some standards around how to utilize icons. We are considering if a wrapper would be a better solution.

Design exploration study to follow up on the conversation between design and development on Feb 26 – Icon placement standards #1500

@RobertaJHahn while testing this issue in my local the footer icon in cardSection-images pattern looks like below not like in the ticket description. And I have checked with @oliviaflory it's fixed so, could you close this bug.

closing issue based on Mahesh's comments above.


Problem attempting to Upgrade from BookStack v23.05.2 to the latest release

Attempted Debugging

[X] I have read the debugging page

Searched GitHub Issues

[X] I have searched GitHub for the issue.

Describe the Scenario
When using the following command:   git pull origin release    I receive the following error message:
Resolving deltas: 100% (3956/3956), completed with 473 local objects.
From https://github.com/BookStackApp/BookStack

branch              release    -> FETCH_HEAD
4ac8ecad..457adc1f  release    -> origin/release
error: Your local changes to the following files would be overwritten by merge:
.env.example
Please commit your changes or stash them before you merge.
Aborting
Updating 4ac8ecad..457adc1f

I did NOT modify this file - in any case how do I commit changes?
Exact BookStack Version
v23.05.2
Log Content
No response
Hosting Environment
Windows 2012 R2 Server

Hi @EAwesomeK, please could you share the output of running git diff .env.example from your BookStack directory?

Thanks for sharing @EAwesomeK.
That output does fairly clearly reflect that the file was modified.
You can just run git restore .env.example to undo any changes though, then re-attempt the update.

Thanks - have no idea how it was changed,  I;m the only one that maintains the system
It works now

Good to hear things are working now! Will therefore close this off.


Jython: ImportError: No module named pkg_resources

This is probably a Jython issue, but I'd like to have a fallback, since pytypes used to work with Jython apart from this.
As far as I understand, this is about some functionality of setuptools.
I didn't explicitly run setup.py on Jython, so something might be ill-configured.
However, I also didn't do such a thing on CPython, but there it runs out of the box.
How to fix it?

Note: I tried it with jython-standalone and after using the installer.
With the installer, the error is different, but also biols down to pkg_resources:
'/home/stefan/jython2.7.1/bin/jython' tests/test_typechecker.py
Traceback (most recent call last):
  File "tests/test_typechecker.py", line 28, in <module>
    import pytypes
  File "/data/workspace/linux/pytypes/pytypes/__init__.py", line 560, in <module>
    from .typelogger import dump_cache, log_type, typelogged, typelogged_module, \
  File "/data/workspace/linux/pytypes/pytypes/typechecker.py", line 62, in _pytypes___import__
    res = _python___import__(name, globls, locls, fromlist, level)
  File "/data/workspace/linux/pytypes/pytypes/typelogger.py", line 30, in <module>
    import pkg_resources
  File "/data/workspace/linux/pytypes/pytypes/typechecker.py", line 62, in _pytypes___import__
    res = _python___import__(name, globls, locls, fromlist, level)
  File "/home/stefan/jython2.7.1/Lib/site-packages/pkg_resources/__init__.py", line 74, in <module>
    __import__('pkg_resources.extern.packaging.requirements')
  File "/data/workspace/linux/pytypes/pytypes/typechecker.py", line 62, in _pytypes___import__
    res = _python___import__(name, globls, locls, fromlist, level)
  File "/home/stefan/jython2.7.1/Lib/site-packages/pkg_resources/_vendor/packaging/requirements.py", line 9, in <module>
    from pkg_resources.extern.pyparsing import stringStart, stringEnd, originalTextFor, ParseException
  File "/data/workspace/linux/pytypes/pytypes/typechecker.py", line 62, in _pytypes___import__
    res = _python___import__(name, globls, locls, fromlist, level)
  File "/home/stefan/jython2.7.1/Lib/site-packages/pkg_resources/extern/__init__.py", line 43, in load_module
    __import__(extant)
  File "/home/stefan/jython2.7.1/Lib/site-packages/pkg_resources/extern/__init__.py", line 43, in load_module
    __import__(extant)
  File "/data/workspace/linux/pytypes/pytypes/typechecker.py", line 62, in _pytypes___import__
    res = _python___import__(name, globls, locls, fromlist, level)
  File "/home/stefan/jython2.7.1/Lib/site-packages/pkg_resources/_vendor/pyparsing.py", line 4720, in <module>
    _reBracketExpr = Literal("[") + Optional("^").setResultsName("negate") + Group( OneOrMore( _charRange | _singleChar ) ).setResultsName("body") + "]"
  File "/home/stefan/jython2.7.1/Lib/site-packages/pkg_resources/_vendor/pyparsing.py", line 1201, in setResultsName
    newself = self.copy()
  File "/home/stefan/jython2.7.1/Lib/site-packages/pkg_resources/_vendor/pyparsing.py", line 1160, in copy
    cpy = copy.copy( self )
  File "/home/stefan/jython2.7.1/Lib/copy.py", line 88, in copy
    rv = reductor(2)
  File "/data/workspace/linux/pytypes/pytypes/typechecker.py", line 62, in _pytypes___import__
    res = _python___import__(name, globls, locls, fromlist, level)
UnboundLocalError: local variable 'globls' referenced before assignment

If I remove pkg_resources from typelogger.py and set the version to some constant, both variants pass again.

Jython does come with setuptools preinstalled, does it not? Installing it normally should make it work. I don't quite understand how the above error relates to pkg_resources.

On second look, I see that importing pkg_resources causes the pytypes code to be imported. This is an import order issue. I'll look into it.

That fixed the issue in principle, thank you.
However, it does not work with Jython-standalone.jar. I guess only the installer pre-installs setuptools.
I find the version string not important enough to break workability with jython-standalone.jar, so I will add some fallback (i.e. hard-coded version-string), unless we see a better solution.
Also, if we find a better solution over time, we can fix this later.
Do you know if it's possible to include Jython into travis tests?

From Travis documentation:

Python 2.4 and Jython are not supported and there are no plans to support them in the future.

So I'd say it's possible but not without some degree of hacking.

There is an alternative to setuptools_scm, named pbr but it adds its own complexity to the build process. The upside is that it doesn't require pkg_resources at runtime.

Okay, let's stick to setuptools_scm now. You'll probably not like the workaround in https://github.com/Stewori/pytypes/commit/872bd338263217f821c83683afdf22064d1d903c, I also don't like it.
Still I think this hack is an acceptable price for getting it work with jython-standalone; at least at the moment.
If you don't have further concerns, I'd file a release soon (just writing the release notes...)

Before the release please check that you are fine with how you are mentioned in https://github.com/Stewori/pytypes#authors and in https://github.com/Stewori/pytypes/blob/master/NOTICE

Best,

-Stefan

Gesendet: Samstag, 08. Juli 2017 um 12:48 Uhr
Von: "Alex Grönholm"<EMAIL_ADDRESS>An: Stewori/pytypes<EMAIL_ADDRESS>Cc: "Stefan Richthofer"<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Betreff: Re: [Stewori/pytypes] Jython: ImportError: No module named pkg_resources (#9)
On second look, I see that importing pkg_resources causes the pytypes code to be imported. This is an import order issue. I'll look into it.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Yeah, looks okay to me.

WTF, I commented on another issue and it appeared here too?

Anyways, the hack is ugly but it doesn't matter if it's just temporary workaround.

Seems like I broke travis with the assert. Removed it as of https://github.com/Stewori/pytypes/commit/d07414f930441636d9234780cdc5362e5fec2d64
This can be closed for now I'd say.


Bug: SVG not created with correct namespaceURI

Describe the bug
We use Icomoon (icomoon.io) for the icons in the app I'm working on, specifically with the SVG spritesheet option. Icons use markup like:
<svg class="icon icon-bell">
  <use xlink:href="/fonts/icomoon/symbol-defs.svg#icon-bell" />
</svg>

From what I'm reading of the documentation, the million version should look like:
function icon(iconName) {
    return svg(m('svg', {
        className: `icon icon-${iconName}`
    }, [
        // SVG 2 support means that HREF should be enough now;
        // otherwise we may need an xlinkHref setter for setAttributeNS
        m('use', { href: `/fonts/icomoon/symbol-defs.svg#icon-${iconName}` })
    ]));
}

From my research into JSX that should look like:
function icon(iconName) {
    return (
        <svg className={`icon icon-${iconName}`}
             xmlns="http://www.w3.org/2000/svg"
             xmlnsXlink="http://www.w3.org/1999/xlink">
            <use xlinkHref={`/fonts/icomoon/symbol-defs.svg#icon-${iconName}`} />
        </svg>
    );
}

However, the icon does not display. The created element's $0.namespaceURI is incorrect.
To Reproduce
Use one of the functions above and inspect the resulting node. I noticed that $0.namespaceURI in the console returns http://www.w3.org/1999/xhtml.
Expected behavior
The created nodes should have the correct SVG namespace. Functionally, the output should be roughly equivalent to this plain JS function:
function icon(iconName) {
    let svg = document.createElementNS('http://www.w3.org/2000/svg', 'svg');
    let use = document.createElementNS('http://www.w3.org/2000/svg', 'use');

    svg.setAttribute('xmlns:xlink','http://www.w3.org/1999/xlink');
    svg.setAttribute('class', ['icon', 'icon-' + iconName].join(' '));
    use.setAttributeNS('http://www.w3.org/1999/xlink', 'href', '/fonts/icomoon/symbol-defs.svg#icon-' + iconName);
    svg.appendChild(use);

    return svg;
}

I'm not super worried about setAttributeNS support for the JSX style xlinkHref attribute, because SVG2 support is pretty broad. Browsers should support <use href="" /> across the board now.
Screenshots
I'll attach a screen shot in a comment, since drag/drop doesn't work on this field.

Operating System
MacOS Catalina 10.15.7 (19H1419)
Browser
Chrome 94; FireFox 92
Additional context
I'm actually working on adding a new feature with heavy front-end reactivity using million, so I have a lot of things to test in a real world scenario. I'll probably find a variety of things as I implement the feature. It was Vue3 or Million, and I decided to give million a try. 😄

Should be working in the commit that is referenced. This is really good to know! Million hasn't really been seriously pressure tested, so these issues mean a ton!

So far, my Renderer for the page's data is 426 lines long. Of that, 256 lines are JSX/million. I'm even using million's onchange/onclick event handler binding, which was a little tricky at first. I'm completely impressed by how fast million is with reflecting changes to the VDOM.
I have a sort of ViewModel <- (message bus) -> Million architecture set up. In fact, sorting and then patch()-ing the DOM only took (in Chrome, across 563 DOM elements):

29ms scripting
10 ms rendering
3 ms painting

Given that I am currently rebuilding the entire VDOM representation freshly (no joke!) with each update/render, the 29ms is so fast to swap that it feels instantaneous. We'll see how it goes during real world testing, once the feature is complete enough to run through QA processes.
Even as early as million is in development, it feels very stable. Very well done aidenybai!

Should be fixed in https://github.com/aidenybai/million/releases/tag/v0.6.3!


[Bug]: Onboarding visual distraction from the entity explorer being hidden

Is there an existing issue for this?

[X] I have searched the existing issues

Description
Entity explorer is visible when the user starts the onboarding, and remains visible till the cursor is moved
The immediate movement causes a great distraction, and the user immediately scans to the entity explorer, rather than looking at the instructions, or the run button
https://user-images.githubusercontent.com/20532920/180756972-c3d06619-2e9f-435d-9edc-05d8a8a5662a.mov
Steps To Reproduce

Start the onbaording
click on Start building
observe

Public Sample App
No response
Version
v1.7.9 Cloud

Stats

Stat
Values

Reach
4000

Effort (months)
0.5

This issue is fixed now, closing it.
https://user-images.githubusercontent.com/93259714/181729547-4e57aa66-6f93-4412-baea-a9583c6bd35f.mp4


Fix: Increase terminal-container height to show full terminal

Fix MCSManager/MCSManager#1007

https://github.com/MCSManager/MCSManager/issues/1007


Reselect + react/redux useSelector() doesn't work as intended

https://react-redux.js.org/next/api/hooks#using-memoizing-selectors
Hello,
If I create a ShopCartList component:
`
export default () => {
const cartItems = useSelector(selectShopCartItems);
 console.log("I'm rerendering even on unrelated state changes");

return (
    cartItems ?

            {
                Object.entries(cartItems).map(([id, item]) => (

                        <ShopCartListItem item={item}/>

                ))
            }

        :
        null
);

}
`
where selectShopCartItems is:
`const selectShopCart = state => state.shopCart;
export const selectShopCartItems = createSelector(
[selectShopCart],
shopCart => shopCart.cartItems
);`
ShopCartList component will still rerender on every unrelated state changes.

Please create a CodeSandbox project that demonstrates the issue.

I just found that the official react-redux docs have really good, thoroughly explained examples of usage with reselect: https://react-redux.js.org/next/api/hooks#useselector-examples


forward request - what really is the default?

In this section:
https://docs.microsoft.com/en-us/azure/api-management/api-management-advanced-policies#attributes-1
It is mentioned that forward request's timeout property is not required, but also does not have a default.
I presume it doesn't hang indefinitely particularly as it's mentioned that "Values greater than 240 seconds may not be honoured as the underlying network infrastructure".
Is it perhaps that depending upon if you were using a vnet?
Additional detail would be handy.

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

ID: 5310021d-de39-9418-2a55-ccdd9c2f4db0
Version Independent ID: ad38bf02-de35-7d67-def7-b1a064dd032f
Content: Azure API Management advanced policies
Content Source: articles/api-management/api-management-advanced-policies.md
Service: api-management
GitHub Login: @vladvino
Microsoft Alias: apimpm

@AlexKeySmith Thank you for your feedback! We will review and update as appropriate.

@AlexKeySmith APIM does not maintain that TCP connection long enough for the backend server to send the response. The Azure LB has a default timeout for 4 minutes, which is not changeable from the user side even if you set forward-request timeout greater than 4 minutes via Policy. For VNET, AFAIK this would not be applicable if the call is made inside the VNET only. Let me know if you have any more questions.

@AlexKeySmith So for now I will proceed with closure of this and If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.

Cool thanks @DixitArora-MSFT is it recommended to set the value explicitly to 240 seconds if you want the maximum timeout i.e. do you get more sensible errors returned from APIM? Or is it best if you don't want a timeout just to let it happen on the network stack? I suppose I'm wondering should we give ourselves a default 240 seconds timeout?

@AlexKeySmith Setting up explicitly always make more sense. This will always add more information what is happening.

Cool thanks @DixitArora-MSFT for the speedy response. Have a nice day.


No such file or directory: 'yt-dlp'

I tried to run the example python yt_fts.py download "https://www.youtube.com/@TimDillonShow/videos"
UC4woSp8ITBoYDmjkukhEhxg
and consistently end up with an error No such file or directory: 'yt-dlp'

Downloading channel
Saving vtt files to /var/folders/x7/0r36c9sn7yg7tvs5sdm471000000gn/T/tmpbrh06qzz
The Tim Dillon Show
Traceback (most recent call last):
  File "/Users/saif/WORKSPACE/yt-fts/yt_fts.py", line 273, in <module>
    cli()
  File "/Users/saif/opt/anaconda3/envs/yt/lib/python3.10/site-packages/click/core.py", line 1130, in __call__
    return self.main(*args, **kwargs)
  File "/Users/saif/opt/anaconda3/envs/yt/lib/python3.10/site-packages/click/core.py", line 1055, in main
    rv = self.invoke(ctx)
  File "/Users/saif/opt/anaconda3/envs/yt/lib/python3.10/site-packages/click/core.py", line 1657, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/Users/saif/opt/anaconda3/envs/yt/lib/python3.10/site-packages/click/core.py", line 1404, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/Users/saif/opt/anaconda3/envs/yt/lib/python3.10/site-packages/click/core.py", line 760, in invoke
    return __callback(*args, **kwargs)
  File "/Users/saif/WORKSPACE/yt-fts/yt_fts.py", line 31, in download
    download_channel(channel_id)
  File "/Users/saif/WORKSPACE/yt-fts/yt_fts.py", line 84, in download_channel
    subprocess.run([
  File "/Users/saif/opt/anaconda3/envs/yt/lib/python3.10/subprocess.py", line 503, in run
    with Popen(*popenargs, **kwargs) as process:
  File "/Users/saif/opt/anaconda3/envs/yt/lib/python3.10/subprocess.py", line 971, in __init__
    self._execute_child(args, executable, preexec_fn, close_fds,
  File "/Users/saif/opt/anaconda3/envs/yt/lib/python3.10/subprocess.py", line 1863, in _execute_child
    raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: 'yt-dlp'

Looks like you're using an Anaconda virtual environnement (https://xkcd.com/1987/) and yt-dlp is not installed globally.
The best thing to do is to follow the Installation instructions from the README.

This is probably related to yt-dlp not being installed globally on your machine or your virtual environment interfering with something. You can find more specific instructions on getting yt-dlp installed on their wiki: https://github.com/yt-dlp/yt-dlp/wiki/Installation


Revert "Remove failed auto update workflow"

Reverts hainusii/docs#1

content/github/collaborating-with-issues-and-pull-requests/dypfinance:main


Investigate Firebase initialization

The Firebase Android library initializes itself automatically using the ContentProvider trick, which leaves a lot to be desired! It is too much magic for my taste and I would prefer to do it manually if possible.

See Take Control of Your Firebase Init on Android for some info about how to do this.
It's not clear that it's worth the maintenance effort to do so.


Text input field in message block

How to use text input field in thread message actions block(Message Surface) but not in modal view.
If possible can you provide an example with input field and select field in same row with both fields sitting beside each other like elements group in actions?
I tried it in this way by placing select field and input field in same elements group in action block in Blockkit but didnt work.
		{
			"type": "actions",
			"elements": [
				{
					"type": "conversations_select",
					"placeholder": {
						"type": "plain_text",
						"text": "Select a conversation",
						"emoji": true
					},
					"action_id": "actionId-0"
				},
				{
			         "type": "input",
				"action_id": "plain_input",
				"placeholder": {
					"type": "plain_text",
					"text": "Enter some plain text"
			     	  }
			      }
			  ]
		}

Please help!

You can try Block Kit Builder for checking available blocks / block elements and how they work: https://app.slack.com/block-kit-builder

input field and select field in same row with both fields sitting beside each other like elements group in actions?

Unfortunately, this layout is not supported for input blocks.
By the way, if you don't mind, may I ask you to post general questions about the Slack Platform in the community Slack workspace instead? If you are not in the workspace, you can join from this URL. In the workspace, more and more folks can help you out (of course, I'm also in the workspace!). The channels like #lang-javascript or #tools-bolt would be good places to have discussions with others.
We would like to use the issue tracker mainly for this library's bugs/issues and questions directly related to bolt-js. It'd be appreciated if you could understand this.

ok I have a small doubt. How to get a thick left border for a block in response?

You can use attachments that contain blocks inside. Check how the attachments work in the Block Kit Builder:

But I need response similar to this:

In single response I need multiple left borders.


Subscribe v3

What?
Allows subscription to v3 messages.
Why?
To support multipart messages.

          1 Warning

:warning:
Any changes to library code should be reflected in the Changelog. Please consider adding a note there. \nYou can find it at CHANGELOG.md.

SwiftLint found issues
Warnings

File
Line
Reason

PCCurrentUser.swift
1178
Else and catch should be on the same line, one space after the previous declaration.

PCCurrentUser.swift
1181
Else and catch should be on the same line, one space after the previous declaration.

PCCurrentUser.swift
1184
Else and catch should be on the same line, one space after the previous declaration.

PCCurrentUser.swift
1187
Else and catch should be on the same line, one space after the previous declaration.

PCCurrentUser.swift
1190
Else and catch should be on the same line, one space after the previous declaration.

PCCurrentUser.swift
26
TODOs should be avoided (This should probably be [PCUse...).

PCCurrentUser.swift
436
TODOs should be avoided (Use the soon-to-be-created new...).

PCCurrentUser.swift
526
TODOs should be avoided (Do we need to fetch users in t...).

PCCurrentUser.swift
760
TODOs should be avoided (Do we need a Last-Event-ID opt...).

PCCurrentUser.swift
1066
TODOs should be avoided (What to do with an error? Just...).

PCCurrentUser.swift
877
Function body should span 40 lines or less excluding comments and whitespace: currently spans 55 lines

PCCurrentUser.swift
695
Lines should not have trailing whitespace.

PCCurrentUser.swift
702
Lines should not have trailing whitespace.

PCCurrentUser.swift
705
Lines should not have trailing whitespace.

PCCurrentUser.swift
716
Lines should not have trailing whitespace.

PCCurrentUser.swift
719
Lines should not have trailing whitespace.

PCCurrentUser.swift
788
Lines should not have trailing whitespace.

PCCurrentUser.swift
804
Lines should not have trailing whitespace.

PCCurrentUser.swift
216
MARK comment should be in valid format. e.g. '// MARK: ...' or '// MARK: - ...'

PCCurrentUser.swift
311
MARK comment should be in valid format. e.g. '// MARK: ...' or '// MARK: - ...'

PCCurrentUser.swift
678
Arguments can be omitted when matching enums with associated types if they are not used.

PCCurrentUser.swift
678
Arguments can be omitted when matching enums with associated types if they are not used.

PCCurrentUser.swift
8
Variable name should be between 3 and 40 characters long: 'id'

PCCurrentUser.swift
65
Variable name should be between 3 and 40 characters long: 'id'

PCCurrentUser.swift
186
Variable name should be between 3 and 40 characters long: 'id'

PCCurrentUser.swift
203
Variable name should be between 3 and 40 characters long: 'id'

PCCurrentUser.swift
252
Variable name should be between 3 and 40 characters long: 'id'

PCCurrentUser.swift
328
Variable name should be between 3 and 40 characters long: 'id'

PCCurrentUser.swift
388
Variable name should be between 3 and 40 characters long: 'id'

PCCurrentUser.swift
126
Collection literals should not have trailing commas.

PCCurrentUser.swift
729
Opening braces should be preceded by a single space and on the same line as the declaration.

PCCurrentUser.swift
207
Line should be 120 characters or less: currently 122 characters

PCCurrentUser.swift
557
Line should be 120 characters or less: currently 143 characters

PCCurrentUser.swift
585
Line should be 120 characters or less: currently 121 characters

PCCurrentUser.swift
611
Line should be 120 characters or less: currently 147 characters

PCCurrentUser.swift
616
Line should be 120 characters or less: currently 147 characters

PCCurrentUser.swift
638
Line should be 120 characters or less: currently 133 characters

PCCurrentUser.swift
646
Line should be 120 characters or less: currently 139 characters

PCCurrentUser.swift
649
Line should be 120 characters or less: currently 134 characters

PCCurrentUser.swift
706
Line should be 120 characters or less: currently 124 characters

PCCurrentUser.swift
720
Line should be 120 characters or less: currently 124 characters

PCCurrentUser.swift
772
Line should be 120 characters or less: currently 123 characters

PCCurrentUser.swift
814
Line should be 120 characters or less: currently 128 characters

PCCurrentUser.swift
915
Line should be 120 characters or less: currently 123 characters

PCCurrentUser.swift
1021
Line should be 120 characters or less: currently 136 characters

PCCurrentUser.swift
1173
Line should be 120 characters or less: currently 122 characters

PCMultipartMessage.swift
43
Operators should be surrounded by a single whitespace when defining them.

PCMultipartMessage.swift
11
Lines should not have trailing whitespace.

PCMultipartMessage.swift
14
Lines should not have trailing whitespace.

PCMultipartMessage.swift
42
Lines should not have trailing whitespace.

PCMultipartMessage.swift
62
Lines should not have trailing whitespace.

PCMultipartMessage.swift
7
Colons should be next to the identifier when specifying a type and next to the key in dictionary literals.

PCMultipartMessage.swift
5
Variable name should be between 3 and 40 characters long: 'id'

PCMultipartMessage.swift
16
Variable name should be between 3 and 40 characters long: 'id'

PCMultipartMessage.swift
69
Variable name should be between 3 and 40 characters long: 'id'

PCPayloadDeserializer.swift
171
Lines should not have trailing whitespace.

PCPayloadDeserializer.swift
183
Lines should not have trailing whitespace.

PCPayloadDeserializer.swift
185
Lines should not have trailing whitespace.

PCPayloadDeserializer.swift
195
Lines should not have trailing whitespace.

PCPayloadDeserializer.swift
208
Lines should not have trailing whitespace.

PCPayloadDeserializer.swift
219
Lines should not have trailing whitespace.

PCPayloadDeserializer.swift
225
Lines should not have trailing whitespace.

PCPayloadDeserializer.swift
230
Lines should not have trailing whitespace.

PCPayloadDeserializer.swift
234
Lines should not have trailing whitespace.

PCPayloadDeserializer.swift
237
Lines should not have trailing whitespace.

PCPayloadDeserializer.swift
242
Lines should not have trailing whitespace.

PCPayloadDeserializer.swift
246
Lines should not have trailing whitespace.

PCPayloadDeserializer.swift
250
Lines should not have trailing whitespace.

PCPayloadDeserializer.swift
255
Lines should not have trailing whitespace.

PCPayloadDeserializer.swift
20
Variable name should be between 3 and 40 characters long: 'id'

PCPayloadDeserializer.swift
174
Variable name should be between 3 and 40 characters long: 'id'

PCPayloadDeserializer.swift
198
Variable name should be between 3 and 40 characters long: 'id'

PCPayloadDeserializer.swift
67
Line should be 120 characters or less: currently 145 characters

PCPayloadDeserializer.swift
100
Line should be 120 characters or less: currently 156 characters

PCPayloadDeserializer.swift
140
Line should be 120 characters or less: currently 122 characters

PCPayloadDeserializer.swift
145
Line should be 120 characters or less: currently 161 characters

PCPayloadDeserializer.swift
160
Line should be 120 characters or less: currently 148 characters

PCPayloadDeserializer.swift
181
Line should be 120 characters or less: currently 158 characters

PCPayloadDeserializer.swift
206
Line should be 120 characters or less: currently 163 characters

PCPayloadDeserializer.swift
232
Line should be 120 characters or less: currently 141 characters

PCPayloadDeserializer.swift
236
Line should be 120 characters or less: currently 142 characters

PCPayloadDeserializer.swift
244
Line should be 120 characters or less: currently 138 characters

PCPayloadDeserializer.swift
248
Line should be 120 characters or less: currently 124 characters

PCPayloadDeserializer.swift
265
Line should be 120 characters or less: currently 141 characters

PCRoomDelegate.swift
21
TODOs should be avoided (This should be unnecessary).

PCRoomSubscription.swift
217
TODOs should be avoided (What happens if you provide bo...).

PCRoomSubscription.swift
16
Function body should span 40 lines or less excluding comments and whitespace: currently spans 98 lines

PCRoomSubscription.swift
61
Lines should not have trailing whitespace.

PCRoomSubscription.swift
127
Lines should not have trailing whitespace.

PCRoomSubscription.swift
179
Lines should not have trailing whitespace.

PCRoomSubscription.swift
183
Lines should not have trailing whitespace.

PCRoomSubscription.swift
271
Lines should not have trailing whitespace.

PCRoomSubscription.swift
281
Lines should not have trailing whitespace.

PCRoomSubscription.swift
296
Lines should not have trailing whitespace.

PCRoomSubscription.swift
306
Lines should not have trailing whitespace.

PCRoomSubscription.swift
308
Lines should not have trailing whitespace.

PCRoomSubscription.swift
311
Function should have 5 parameters or less: it currently has 6

PCRoomSubscription.swift
365
Function should have 5 parameters or less: it currently has 8

PCRoomSubscription.swift
77
Line should be 120 characters or less: currently 146 characters

PCRoomSubscription.swift
109
Line should be 120 characters or less: currently 146 characters

PCRoomSubscription.swift
133
Line should be 120 characters or less: currently 145 characters

PCRoomSubscription.swift
9
Delegates should be weak to avoid reference cycles.

PCRoomSubscription.swift
423
File should contain 400 lines or less: currently contains 423

CurrentUserTests.swift
19
Function body should span 40 lines or less excluding comments and whitespace: currently spans 67 lines

CurrentUserTests.swift
97
Variable name should be between 3 and 40 characters long: 'ex'

TestingDelegates.swift
40
Returning Void in a function declaration is redundant.

TestingDelegates.swift
44
Returning Void in a function declaration is redundant.

TestingDelegates.swift
111
Returning Void in a function declaration is redundant.

TestingDelegates.swift
115
Returning Void in a function declaration is redundant.

TestingDelegates.swift
119
Returning Void in a function declaration is redundant.

TestingDelegates.swift
138
Lines should not have trailing whitespace.

MessageTests.swift
538
Function body should span 40 lines or less excluding comments and whitespace: currently spans 64 lines

MessageTests.swift
638
Function body should span 40 lines or less excluding comments and whitespace: currently spans 44 lines

MessageTests.swift
703
Function body should span 40 lines or less excluding comments and whitespace: currently spans 44 lines

MessageTests.swift
23
When using trailing closures, empty parentheses should be avoided after the method call.

MessageTests.swift
30
When using trailing closures, empty parentheses should be avoided after the method call.

MessageTests.swift
226
Lines should not have trailing whitespace.

MessageTests.swift
229
Lines should not have trailing whitespace.

MessageTests.swift
232
Lines should not have trailing whitespace.

MessageTests.swift
235
Lines should not have trailing whitespace.

MessageTests.swift
243
Lines should not have trailing whitespace.

MessageTests.swift
246
Lines should not have trailing whitespace.

MessageTests.swift
249
Lines should not have trailing whitespace.

MessageTests.swift
252
Lines should not have trailing whitespace.

MessageTests.swift
260
Lines should not have trailing whitespace.

MessageTests.swift
269
Lines should not have trailing whitespace.

MessageTests.swift
272
Lines should not have trailing whitespace.

MessageTests.swift
275
Lines should not have trailing whitespace.

MessageTests.swift
278
Lines should not have trailing whitespace.

MessageTests.swift
287
Lines should not have trailing whitespace.

MessageTests.swift
299
Lines should not have trailing whitespace.

MessageTests.swift
302
Lines should not have trailing whitespace.

MessageTests.swift
394
Lines should not have trailing whitespace.

MessageTests.swift
397
Lines should not have trailing whitespace.

MessageTests.swift
399
Lines should not have trailing whitespace.

MessageTests.swift
408
Lines should not have trailing whitespace.

MessageTests.swift
413
Lines should not have trailing whitespace.

MessageTests.swift
416
Lines should not have trailing whitespace.

MessageTests.swift
419
Lines should not have trailing whitespace.

MessageTests.swift
426
Lines should not have trailing whitespace.

MessageTests.swift
435
Lines should not have trailing whitespace.

MessageTests.swift
438
Lines should not have trailing whitespace.

MessageTests.swift
441
Lines should not have trailing whitespace.

MessageTests.swift
446
Lines should not have trailing whitespace.

MessageTests.swift
449
Lines should not have trailing whitespace.

MessageTests.swift
455
Lines should not have trailing whitespace.

MessageTests.swift
460
Lines should not have trailing whitespace.

MessageTests.swift
465
Lines should not have trailing whitespace.

MessageTests.swift
468
Lines should not have trailing whitespace.

MessageTests.swift
471
Lines should not have trailing whitespace.

MessageTests.swift
478
Lines should not have trailing whitespace.

MessageTests.swift
487
Lines should not have trailing whitespace.

MessageTests.swift
490
Lines should not have trailing whitespace.

MessageTests.swift
493
Lines should not have trailing whitespace.

MessageTests.swift
498
Lines should not have trailing whitespace.

MessageTests.swift
501
Lines should not have trailing whitespace.

MessageTests.swift
507
Lines should not have trailing whitespace.

MessageTests.swift
512
Lines should not have trailing whitespace.

MessageTests.swift
515
Lines should not have trailing whitespace.

MessageTests.swift
518
Lines should not have trailing whitespace.

MessageTests.swift
525
Lines should not have trailing whitespace.

MessageTests.swift
534
Lines should not have trailing whitespace.

MessageTests.swift
97
Variable name should be between 3 and 40 characters long: 'ex'

MessageTests.swift
125
Variable name should be between 3 and 40 characters long: 'ex'

MessageTests.swift
163
Variable name should be between 3 and 40 characters long: 'ex'

MessageTests.swift
195
Variable name should be between 3 and 40 characters long: 'ex'

MessageTests.swift
228
Variable name should be between 3 and 40 characters long: 'ex'

MessageTests.swift
248
Variable name should be between 3 and 40 characters long: 'ex'

MessageTests.swift
274
Variable name should be between 3 and 40 characters long: 'ex'

MessageTests.swift
304
Variable name should be between 3 and 40 characters long: 'ex'

MessageTests.swift
396
Variable name should be between 3 and 40 characters long: 'ex'

MessageTests.swift
440
Variable name should be between 3 and 40 characters long: 'ex'

MessageTests.swift
492
Variable name should be between 3 and 40 characters long: 'ex'

MessageTests.swift
236
Line should be 120 characters or less: currently 132 characters

MessageTests.swift
256
Line should be 120 characters or less: currently 142 characters

MessageTests.swift
261
Line should be 120 characters or less: currently 136 characters

MessageTests.swift
282
Line should be 120 characters or less: currently 143 characters

MessageTests.swift
283
Line should be 120 characters or less: currently 161 characters

MessageTests.swift
430
Line should be 120 characters or less: currently 131 characters

MessageTests.swift
447
Line should be 120 characters or less: currently 169 characters

MessageTests.swift
448
Line should be 120 characters or less: currently 155 characters

MessageTests.swift
482
Line should be 120 characters or less: currently 131 characters

MessageTests.swift
499
Line should be 120 characters or less: currently 169 characters

MessageTests.swift
500
Line should be 120 characters or less: currently 155 characters

MessageTests.swift
529
Line should be 120 characters or less: currently 131 characters

MessageTests.swift
769
File should contain 400 lines or less: currently contains 769

RoomEventBufferingTests.swift
6
Type body should span 200 lines or less excluding comments and whitespace: currently spans 230 lines

RoomEventBufferingTests.swift
70
Colons should be next to the identifier when specifying a type and next to the key in dictionary literals.

RoomEventBufferingTests.swift
71
Colons should be next to the identifier when specifying a type and next to the key in dictionary literals.

RoomEventBufferingTests.swift
76
Colons should be next to the identifier when specifying a type and next to the key in dictionary literals.

RoomEventBufferingTests.swift
77
Colons should be next to the identifier when specifying a type and next to the key in dictionary literals.

RoomEventBufferingTests.swift
94
Colons should be next to the identifier when specifying a type and next to the key in dictionary literals.

RoomEventBufferingTests.swift
95
Colons should be next to the identifier when specifying a type and next to the key in dictionary literals.

PCBasicMultipartMessage.swift
4
Variable name should be between 3 and 40 characters long: 'id'

PCMultipartMessageEnricher.swift
103
TODOs should be avoided (There may well be ways to make...).

PCMultipartMessageEnricher.swift
8
Lines should not have trailing whitespace.

PCMultipartMessageEnricher.swift
13
Lines should not have trailing whitespace.

PCMultipartMessageEnricher.swift
18
Lines should not have trailing whitespace.

PCMultipartMessageEnricher.swift
24
Lines should not have trailing whitespace.

PCMultipartMessageEnricher.swift
28
Lines should not have trailing whitespace.

PCMultipartMessageEnricher.swift
33
Lines should not have trailing whitespace.

PCMultipartMessageEnricher.swift
40
Lines should not have trailing whitespace.

PCMultipartMessageEnricher.swift
42
Lines should not have trailing whitespace.

PCMultipartMessageEnricher.swift
48
Lines should not have trailing whitespace.

PCMultipartMessageEnricher.swift
54
Lines should not have trailing whitespace.

PCMultipartMessageEnricher.swift
63
Lines should not have trailing whitespace.

PCMultipartMessageEnricher.swift
72
Lines should not have trailing whitespace.

PCMultipartMessageEnricher.swift
76
Lines should not have trailing whitespace.

PCMultipartMessageEnricher.swift
78
Lines should not have trailing whitespace.

PCMultipartMessageEnricher.swift
86
Lines should not have trailing whitespace.

PCMultipartMessageEnricher.swift
100
Lines should not have trailing whitespace.

PCMultipartMessageEnricher.swift
102
Lines should not have trailing whitespace.

PCMultipartMessageEnricher.swift
109
Lines should not have trailing whitespace.

PCMultipartMessageEnricher.swift
111
Lines should not have trailing whitespace.

PCMultipartMessageEnricher.swift
121
Lines should not have trailing whitespace.

PCMultipartMessageEnricher.swift
124
Lines should not have trailing whitespace.

PCMultipartMessageEnricher.swift
129
Lines should not have trailing whitespace.

PCMultipartMessageEnricher.swift
134
Lines should not have trailing whitespace.

PCMultipartMessageEnricher.swift
141
Lines should not have trailing whitespace.

PCMultipartMessageEnricher.swift
16
Variable name should be between 3 and 40 characters long: 'messagesAwaitingEnrichmentDependentOnUserRetrieval'

PCMultipartMessageEnricher.swift
101
Variable name should be between 3 and 40 characters long: 'id'

PCMultipartMessageEnricher.swift
12
Line should be 120 characters or less: currently 136 characters

PCMultipartMessageEnricher.swift
25
Line should be 120 characters or less: currently 126 characters

PCMultipartMessageEnricher.swift
57
Line should be 120 characters or less: currently 159 characters

PCMultipartMessageEnricher.swift
60
Line should be 120 characters or less: currently 138 characters

PCMultipartMessageEnricher.swift
67
Line should be 120 characters or less: currently 132 characters

PCMultipartMessageEnricher.swift
97
Line should be 120 characters or less: currently 130 characters

PCMultipartMessageEnricher.swift
101
Line should be 120 characters or less: currently 141 characters

PCMultipartMessageEnricher.swift
106
Line should be 120 characters or less: currently 136 characters

PCMultipartMessageEnricher.swift
116
Line should be 120 characters or less: currently 133 characters

PCMultipartMessageEnricher.swift
145
Line should be 120 characters or less: currently 145 characters

PCMultipartMessageSubscription.swift
13
Lines should not have trailing whitespace.

PCMultipartMessageSubscription.swift
33
Lines should not have trailing whitespace.

PCMultipartMessageSubscription.swift
39
Lines should not have trailing whitespace.

PCMultipartMessageSubscription.swift
47
Lines should not have trailing whitespace.

PCMultipartMessageSubscription.swift
52
Lines should not have trailing whitespace.

PCMultipartMessageSubscription.swift
63
Lines should not have trailing whitespace.

PCMultipartMessageSubscription.swift
72
Lines should not have trailing whitespace.

PCMultipartMessageSubscription.swift
77
Lines should not have trailing whitespace.

PCMultipartMessageSubscription.swift
85
Lines should not have trailing whitespace.

PCMultipartMessageSubscription.swift
94
Lines should not have trailing whitespace.

PCMultipartMessageSubscription.swift
100
Lines should not have trailing whitespace.

PCMultipartMessageSubscription.swift
105
Lines should not have trailing whitespace.

PCMultipartMessageSubscription.swift
111
Lines should not have trailing whitespace.

PCMultipartMessageSubscription.swift
116
Lines should not have trailing whitespace.

PCMultipartMessageSubscription.swift
121
Lines should not have trailing whitespace.

Errors

File
Line
Reason

PCCurrentUser.swift
7
Type body should span 200 lines or less excluding comments and whitespace: currently spans 666 lines

PCCurrentUser.swift
769
Variable name should be between 3 and 40 characters long: 'r'

PCCurrentUser.swift
811
Variable name should be between 3 and 40 characters long: 'r'

PCCurrentUser.swift
1090
Variable name should be between 3 and 40 characters long: 'm'

PCCurrentUser.swift
1096
Enum element name should only contain alphanumeric characters: 'noSubscriptionToRoom(_:)'

PCCurrentUser.swift
1124
Enum element name should only contain alphanumeric characters: 'messageIDKeyMissingInMessageCreationResponse(_:)'

PCCurrentUser.swift
1196
File should contain 400 lines or less: currently contains 1196

PCMultipartMessage.swift
63
Enum element name should only contain alphanumeric characters: 'inlinePayload(payload:)'

PCMultipartMessage.swift
64
Enum element name should only contain alphanumeric characters: 'urlPayload(payload:)'

PCMultipartMessage.swift
65
Enum element name should only contain alphanumeric characters: 'attachmentPayload(payload:)'

PCPayloadDeserializer.swift
273
Enum element name should only contain alphanumeric characters: 'incompleteOrInvalidPayloadToCreteEntity(type:payload:)'

PCPayloadDeserializer.swift
18
Function should have 5 parameters or less: it currently has 14

PCRoomSubscription.swift
204
Function should have 5 parameters or less: it currently has 9

PCRoomSubscription.swift
259
Function should have 5 parameters or less: it currently has 9

MessageTests.swift
5
Type body should span 200 lines or less excluding comments and whitespace: currently spans 498 lines

MessageTests.swift
578
Variable name should be between 3 and 40 characters long: 'b'

MessageTests.swift
664
Variable name should be between 3 and 40 characters long: 'b'

MessageTests.swift
730
Variable name should be between 3 and 40 characters long: 'b'

RoomEventBufferingTests.swift
19
Function body should span 40 lines or less excluding comments and whitespace: currently spans 222 lines

PCMultipartMessageEnricher.swift
151
Enum element name should only contain alphanumeric characters: 'success(_:)'

PCMultipartMessageEnricher.swift
152
Enum element name should only contain alphanumeric characters: 'error(_:)'

  Generated by :no_entry_sign: Danger

 [0.5] Subscribe to v3 message

also that CI bot is a disgrace and we should remove it until we're going to start enforcing its rules 😅

Ugh stupid Xcode. Removing it from Xcode just removes the file from the directory view but doesn't remove the actual file itself..


Changing assets post deployment on a STAMP

Hi, we're currently having an issue changing the assets such as the logo being used. We've overwritten the logo.png in the lms/static/images folder. We then ran the update assets and compile static commands and we do see the new logo along with its compiled version in the var/staticfiles/images folder so I know that at least the update assets and compile static commands worked.
We restarted the lms and cms afterwards but how come the logo that shows up on the lms is still the default one? We tested this out on a bitnami devstack and it worked. Pretty much all documents/sites we can find pertaining to changing assets for openedx describes more or less the same thing we did.
Is there some other command that we're supposed to run to make changes or we can't make any asset change on an openedx deployed on azure via oxa-tools?
Edit:
Actually we tried deploying another instance of a STAMP deployment of ficus, when we checked the staticfiles folder, it was actually empty and yet the theme that we set during/prior to deployment in the parameters.json reflected the desired theme. Problem is we can't seem to be able to make any changes onto the theme.

Hi @fyrlandt, the suggested approach for making theme modifications is to create your own theme repository and reference it during deployment. We have provided some details about that here: Open edX theming guidance video

Yeah that's what we did and it worked however what if we want to make theme modifications after deployment? That's what we can't seem to do.

That is not suggested. You always want to capture all of your changes in your theming repo.

Hmm, actually what we intend to do is to update the theming repo if for example a client wants his logo changed but we've tried updating the theming repo and the added/changed files aren't being seen. Is there any way to prompt edx to pull from the theming repo again just like during deployment?

There's always a way if you know what you are doing. Typically, this would involve working on the application instance (not recommended), doing a git pull of the theming repo (you'd need to know the path: usually under the platform code) and re-compile the assets on the instance (consult edx docs for details). That should be sufficient. Again, these are not processes we recommend particularly for a live system like a STAMP cluster.

Weird thing is we've been git pulling the theming repo into the Comprehensive_themes_dir stated in the lms.env.json (/edx/app/edxapp/edx-platform/themes in our case) and we've done the update assets and compile static commands:

sudo -H -u edxapp bash
source /edx/app/edxapp/edxapp_env
cd /edx/app/edxapp/edx-platform
paver update_assets lms --settings=aws
python manage.py lms --settings=aws collectstatic --noinput

Then we also restart the lms and cms:

sudo /edx/bin/supervisorctl restart edxapp:
sudo /edx/bin/supervisorctl restart edxapp_worker:
sudo service nginx restart

I do see it state that my theme is being compiled during the update static command however after restarting and despite the theme being set in the django admin page, it still doesn't update. I'm wondering if there's some sort of caching that's happening on the server/jumpbox? Been testing on various browsers and incognito in chrome so it doesn't seem to be a browser caching issue.

There are additional settings in the *.env.json file that need to be updated to use the theme specified in additional to compiling and restarting services.

Ok, I finally got it to work, turns out I was trying to change the files in the jumpbox instead of the instance with a private IP.

Excellent. Again, this is not a recommended approach. For trial purposes, that should suffice. Meanwhile, I will close this issue.


Unable to connect 403 error on sample -> location and file uploading

What sample tool are you using?
I want to try the sample : https://github.com/microsoft/CopilotStudioSamples/tree/master/BuildYourOwnCanvasSamples/2.location-and-file-uploading
Describe the bug
When npm start ->
{   "error": {     "code": "BadArgument",     "message": "Invalid token or secret"   } }
To Reproduce
Steps to reproduce the behavior:

Go to PVA details -> get the TenantID and Copilot App ID
Edit the .env file with this ids and azure storage name and key
npm start
See error

Expected behavior
No error but just app working
Screenshots

In the .env file, the BOT_ID is the Copilot app ID ?

@leofrk2 did you manage to successfully connect to directLine ?

Nop, I just switched to bot framework in order to be able tu upload file, but don't still understand where the issue is


Update README.md

Ludy87, thanks for this integration. I was hoping for an Xplora integration for a long time already. Thank you for making this available!
I fixed a few  minor spelling/grammar issues in the readme.

thanks for your support

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.


Change variables and update graphs

User story

As a user
I need to change the variables of a scenario
So that I create the costumers desired scenario and compare it with the baseline scenario

Acceptance criteria

Graphs are updated after I change the variables
I can only choose between predefined variable and I cannot add anything new
Change the graphs automatically. If it is not possible, I need a button to click on and update the graphs


Rolling dataset generation now truncates dynamic features.

Issue #, if available:
Solves #1390
Description of changes:
This PR changes such that dynamic features such as feat_dynamic_real and feat_dynamic_cat are truncated along with the target of the timeseries.
Previously, running make_evaluation_predictions on rolled datasets failed if the dataset had dynamic features.
This happened as the target of the timeseries was shorter than the dynamic features which remained unchanged.
The changes has been tested with the following code:
import pandas as pd
from gluonts.dataset.common import ListDataset
from gluonts.dataset.field_names import FieldName
from gluonts.dataset.rolling_dataset import (
    generate_rolling_dataset,
    StepStrategy,
)
from gluonts.evaluation.backtest import make_evaluation_predictions
from gluonts.evaluation import Evaluator

prediction_length = 1
train_len = 10
test_len = 15

def create_dataset(length):
    return ListDataset(
        [
            {
                FieldName.TARGET: list(range(length)),
                FieldName.START: pd.Timestamp("01-01-2019"),
                FieldName.FEAT_DYNAMIC_REAL: [list(range(length))],
            }
        ],
        freq="D",
    )

train_ds = create_dataset(train_len)
test_ds = create_dataset(test_len)
rolled_ds = generate_rolling_dataset(
    dataset=test_ds,
    strategy=StepStrategy(prediction_length=1),
    start_time=pd.Timestamp("01-13-2019"),
)

from gluonts.model.deepar import DeepAREstimator
from gluonts.mx.trainer import Trainer

estimator = DeepAREstimator(
    freq="D",
    prediction_length=prediction_length,
    context_length=2 * prediction_length,
    use_feat_dynamic_real=True,
    trainer=Trainer(epochs=1),
)
predictor = estimator.train(training_data=train_ds)
forecast_it, ts_it = make_evaluation_predictions(
    rolled_ds, predictor=predictor, num_samples=100
)
training_agg_metrics, _ = Evaluator(num_workers=0)(ts_it, forecast_it)
from pprint import pprint

pprint(training_agg_metrics)

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

There is no test in place since previously, i'll add a few.

Docs build is failing. Can you fix that @arangatang ?

Yeah I started to look into it yesterday but I was not able to reproduce it locally.
There seem to be some issue with the synthetic_data_generation.md notebook in the docs folder. It cannot be built since  #1380 although the changes made there seems unrelated.
Perhaps there is a dependency which was updated somewhere, I'll keep digging!


[Phenzic] - Sage - Unit testing with celo & truffle / Celo's POS consensus

Thanks for submitting this tutorial for Celo Sage
Before you hit "Create Pull Request", make sure you have read the Tutorial Contribution Guidelines and reviewed the Sample Tutorial Structure.
Please confirm the following before submitting your tutorial for review -

[x] My tutorial follows the Tutorial Contribution Guidelines.
[x] The title of the Pull Request matches the title of my tutorial.
[x] I've followed the tutorial template structure.
[x] I've proofread the tutorial for spelling and grammar mistakes.
[x] I've thoroughly explained the code, with inline code comments and text explanations.
[x] I've run a linter & prettifier to format my code blocks.
[x] I've run the tutorial to test it and the code works.

NOTE: We cannot review your Pull Request if it does not meet the standard outlined above.
Reviewers - @joenyzio & @viral-sangani

@Julius170 I was expecting more content related to POS in your POS article. But that's fine. Make sure in your future article content is related to the title.
Please resolve the changes I have suggested and I can merge the PR after that.
Thanks


Disable automatic loss scaling option for inference

What does this PR do?
Fixes # (issue)

Issue where popart throws an error in evaluation if automatic loss scaling option is enabled.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


fix crash when run sonobuoy in serverless kubernetes cluster

We found a crash when ran sonobuoy in serverless kubernetes cluster, see below error log.
In serverless kubernetes cluster, pod may need 10s to start after creation, before container start, pod.Status.StartTime is nil.
kubectl -n sonobuoy get pod
NAME                                READY   STATUS    RESTARTS   AGE
sonobuoy                            0/1     Error     0          4h57m
sonobuoy-e2e-job-61031ae7baac48e1   2/2     Running   0          4h57m
kubectl -n sonobuoy logs sonobuoy
time="2020-04-20T02:49:23Z" level=info msg="Starting aggregation server" address=<IP_ADDRESS> port=8080
time="2020-04-20T02:49:23Z" level=info msg="Starting annotation update routine"
time="2020-04-20T02:49:23Z" level=info msg="Running plugin" plugin=e2e
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x10 pc=0x1010651]
goroutine 121 [running]:
github.com/vmware-tanzu/sonobuoy/pkg/plugin/driver/utils.IsPodFailing(0xc0004e8a80, 0x16a5e60, 0xc000514500, 0xc0004e8a80)
/go/src/github.com/vmware-tanzu/sonobuoy/pkg/plugin/driver/utils/utils.go:71 +0x3b1
github.com/vmware-tanzu/sonobuoy/pkg/plugin/driver/job.(*Plugin).monitorOnce(0xc0000fa000, 0x16a5e60, 0xc000514500, 0x0, 0x0, 0x0, 0xc0003e8600, 0x0)
/go/src/github.com/vmware-tanzu/sonobuoy/pkg/plugin/driver/job/job.go:219 +0x8d
github.com/vmware-tanzu/sonobuoy/pkg/plugin/driver/job.(*Plugin).Monitor(0xc0000fa000, 0x16744e0, 0xc000129ec0, 0x16a5e60, 0xc000514500, 0xc000284840, 0x1, 0x1, 0xc000129e00)
/go/src/github.com/vmware-tanzu/sonobuoy/pkg/plugin/driver/job/job.go:195 +0x190
created by github.com/vmware-tanzu/sonobuoy/pkg/plugin/aggregation.(*Aggregator).RunAndMonitorPlugin
/go/src/github.com/vmware-tanzu/sonobuoy/pkg/plugin/aggregation/run.go:233 +0x227
What this PR does / why we need it:
Which issue(s) this PR fixes

Fixes #

Special notes for your reviewer:
Release note:
release-note

Thanks for this PR, @jovizhangwei! I'd like to include a test with this change so I will push that to your branch before merging and hopefully get a release out with this change either today or Monday.


Forms: multiple select must support up to 63 values on 64bit systems

Default value select shown only 31 items

If you use 64x system on your server then it's recommended to change the value of BX_DOL_INT_MAX constant in inc/params.inc.php file from<PHONE_NUMBER> to PHP_INT_MAX. So, you'll have
define('BX_DOL_INT_MAX', PHP_INT_MAX);
instead of
define('BX_DOL_INT_MAX',<PHONE_NUMBER>);


Feature/bench target anim 107037876

Adds grunt benchmark target for cli
Moves Animation Benchmarks from tests to benchmarks


Broken build in mmmagic

Receiving this error when installing mmmagic, i didn't find a solution yet
Using node.js v10.5.0
CentOS 8

node-gyp rebuild

make: Entering directory '/srv/asd/node_modules/mmmagic/build'
  CC(target) Release/obj.target/libmagic/deps/libmagic/src/apprentice.o
  CC(target) Release/obj.target/libmagic/deps/libmagic/src/apptype.o
  CC(target) Release/obj.target/libmagic/deps/libmagic/src/ascmagic.o
  CC(target) Release/obj.target/libmagic/deps/libmagic/src/cdf.o
  CC(target) Release/obj.target/libmagic/deps/libmagic/src/cdf_time.o
  CC(target) Release/obj.target/libmagic/deps/libmagic/src/compress.o
  CC(target) Release/obj.target/libmagic/deps/libmagic/src/der.o
  CC(target) Release/obj.target/libmagic/deps/libmagic/src/encoding.o
  CC(target) Release/obj.target/libmagic/deps/libmagic/src/fsmagic.o
  CC(target) Release/obj.target/libmagic/deps/libmagic/src/funcs.o
  CC(target) Release/obj.target/libmagic/deps/libmagic/src/is_tar.o
  CC(target) Release/obj.target/libmagic/deps/libmagic/src/magic.o
  CC(target) Release/obj.target/libmagic/deps/libmagic/src/print.o
  CC(target) Release/obj.target/libmagic/deps/libmagic/src/readcdf.o
  CC(target) Release/obj.target/libmagic/deps/libmagic/src/readelf.o
../deps/libmagic/src/readelf.c: In function ‘dophn_core’:
../deps/libmagic/src/readelf.c:1024:13: warning: ‘nh64.n_type’ may be used uninitialized in this function [-Wmaybe-uninitialized]
  Elf64_Nhdr nh64;
             ^~~~
../deps/libmagic/src/readelf.c:1023:13: warning: ‘nh32.n_type’ may be used uninitialized in this function [-Wmaybe-uninitialized]
  Elf32_Nhdr nh32;
             ^~~~
../deps/libmagic/src/readelf.c: In function ‘dophn_exec’:
../deps/libmagic/src/readelf.c:1024:13: warning: ‘nh64.n_type’ may be used uninitialized in this function [-Wmaybe-uninitialized]
  Elf64_Nhdr nh64;
             ^~~~
../deps/libmagic/src/readelf.c:1023:13: warning: ‘nh32.n_type’ may be used uninitialized in this function [-Wmaybe-uninitialized]
  Elf32_Nhdr nh32;
             ^~~~
../deps/libmagic/src/readelf.c: In function ‘doshn’:
../deps/libmagic/src/readelf.c:1024:13: warning: ‘nh64.n_type’ may be used uninitialized in this function [-Wmaybe-uninitialized]
  Elf64_Nhdr nh64;
             ^~~~
../deps/libmagic/src/readelf.c:1023:13: warning: ‘nh32.n_type’ may be used uninitialized in this function [-Wmaybe-uninitialized]
  Elf32_Nhdr nh32;
             ^~~~
  CC(target) Release/obj.target/libmagic/deps/libmagic/src/softmagic.o
  CC(target) Release/obj.target/libmagic/deps/libmagic/src/fmtcheck.o
  CC(target) Release/obj.target/libmagic/deps/libmagic/src/strlcat.o
  CC(target) Release/obj.target/libmagic/deps/libmagic/src/strlcpy.o
  AR(target) Release/obj.target/deps/libmagic/magic.a
  COPY Release/magic.a
  CXX(target) Release/obj.target/magic/src/binding.o
In file included from ../src/binding.cc:3:
../node_modules/nan/nan.h: In function ‘void Nan::AsyncQueueWorker(Nan::AsyncWorker*)’:
../node_modules/nan/nan.h:2294:62: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
     , reinterpret_cast<uv_after_work_cb>(AsyncExecuteComplete)
                                                              ^
../src/binding.cc: In static member function ‘static void Magic::DetectFile(const Nan::FunctionCallbackInfo<v8::Value>&)’:
../src/binding.cc:184:59: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
                                  (uv_after_work_cb)Magic::DetectAfter);
                                                           ^~~~~~~~~~~
../src/binding.cc: In static member function ‘static void Magic::Detect(const Nan::FunctionCallbackInfo<v8::Value>&)’:
../src/binding.cc:217:59: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
                                  (uv_after_work_cb)Magic::DetectAfter);
                                                           ^~~~~~~~~~~
In file included from ../src/binding.cc:1:
../src/binding.cc: At global scope:
/root/.node-gyp/10.5.0/include/node/node.h:539:43: warning: cast between incompatible function types from ‘void (*)(v8::Local<v8::Object>)’ to ‘node::addon_register_func’ {aka ‘void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, void*)’} [-Wcast-function-type]
       (node::addon_register_func) (regfunc),                          \
                                           ^
/root/.node-gyp/10.5.0/include/node/node.h:573:3: note: in expansion of macro ‘NODE_MODULE_X’
   NODE_MODULE_X(modname, regfunc, NULL, 0)  // NOLINT (readability/null_usage)
   ^~~~~~~~~~~~~
../src/binding.cc:415:3: note: in expansion of macro ‘NODE_MODULE’
   NODE_MODULE(magic, init);
   ^~~~~~~~~~~
In file included from /root/.node-gyp/10.5.0/include/node/node.h:63,
                 from ../src/binding.cc:1:
/root/.node-gyp/10.5.0/include/node/v8.h: In instantiation of ‘void v8::PersistentBase<T>::SetWeak(P*, typename v8::WeakCallbackInfo<P>::Callback, v8::WeakCallbackType) [with P = node::ObjectWrap; T = v8::Object; typename v8::WeakCallbackInfo<P>::Callback = void (*)(const v8::WeakCallbackInfo<node::ObjectWrap>&)]’:
/root/.node-gyp/10.5.0/include/node/node_object_wrap.h:85:78:   required from here
/root/.node-gyp/10.5.0/include/node/v8.h:9360:16: warning: cast between incompatible function types from ‘v8::WeakCallbackInfo<node::ObjectWrap>::Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<node::ObjectWrap>&)’} to ‘Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<void>&)’} [-Wcast-function-type]
                reinterpret_cast<Callback>(callback), type);
                ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/root/.node-gyp/10.5.0/include/node/v8.h: In instantiation of ‘void v8::PersistentBase<T>::SetWeak(P*, typename v8::WeakCallbackInfo<P>::Callback, v8::WeakCallbackType) [with P = Nan::ObjectWrap; T = v8::Object; typename v8::WeakCallbackInfo<P>::Callback = void (*)(const v8::WeakCallbackInfo<Nan::ObjectWrap>&)]’:
../node_modules/nan/nan_object_wrap.h:65:61:   required from here
/root/.node-gyp/10.5.0/include/node/v8.h:9360:16: warning: cast between incompatible function types from ‘v8::WeakCallbackInfo<Nan::ObjectWrap>::Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<Nan::ObjectWrap>&)’} to ‘Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<void>&)’} [-Wcast-function-type]
  SOLINK_MODULE(target) Release/obj.target/magic.node
  COPY Release/magic.node
make: Leaving directory '/srv/asd/node_modules/mmmagic/build'

Have you tried upgrading at least to the latest node v10.x?

Yes, i tried to upgrade to v12 and no success, and i'm reverted to v10.5.0 again

Wait, the build output shows it was successful, so you should be able to use the addon...

So, i use a project named pterodactyl and they use the mmmagic, and when this error occurr an option in the project that is vital dont work, and i already installed in other OS like ubuntu or centOS 7 and work dont have any errors from mmmagic.

If you can paste output of the build actually failing, I can try to suggest something. Otherwise I don't think there's much I can do as there could be any number of things causing the problem.

Ok, thanks!

same error when node:12.18.2-alpine docker image
but when don't use alpine, it works well


add proposal of nodepool with host network mode

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespace from that line:
/kind bug
/kind documentation
/kind enhancement
/kind good-first-issue
/kind feature
/kind question
/kind design
/sig ai
/sig iot
/sig network
/sig storage

What this PR does / why we need it:
Add proposal of support nodepool with host network mode
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

Does this PR introduce a user-facing change?

other Note

@Lan-ce-lot Very appreciate for your proposal about host network NodePool. and would you like to share your proposal on the community meeting?

@Lan-ce-lot @rambohe-ch If cni config use /etc/cni/net.d/0-loopback.conf,  Did the pod deploy on the node must set hostnetwork=true ?

@Lan-ce-lot @rambohe-ch If cni config use /etc/cni/net.d/0-loopback.conf, Did the pod deploy on the node must set hostnetwork=true ?

@huiwq1990 yes, if the node belongs to a hostnetwork mode nodepool, The hostNetwork field of pod that is assigned to this node will be modified to true by the filter in yurthub.

/lgtm

/lgtm


Webull officially supports OpenAPI (微牛官方已支持OpenAPI)

https://developer.webull.hk/api-doc/
cool !

It seems only support Hong Kong account?

https://developer.webull.com/api-doc/

Those docs must be WIP.  I see no option in Webull WebUI to request or access API keys on US site. US API FAQ still says there is no official API yet.  The endpoints seem quite limited.  I see no OCO or bracket type ordering.

Cool!! Have to find a time to test it out!

@dereckmartin  did you see limited end points. For me not even one end point. when i approached telling me not avaible at the moment in USA

cool, hope to add more


PDF figures, tables, and listings are broken

The PDF generated by readthedocs has missing figures, tables, and unreadable code listings.
https://leaf-obd.readthedocs.io/_/downloads/en/latest/pdf/
rtd-leaf-obd-build-16042842-log.zip
Figures
All figures and images are missing, replaced with white space.

Figure 1.1
Figure 1.2
Figure 3.1
Figure 3.2
Appendix D section D.2 Creative Commons logo

Example: Figure 1.1
HTML correctly rendered: https://leaf-obd.readthedocs.io/en/latest/diagnostic-connector.html#leaf-diagnostic-connector
Screenshot of PDF incorrectly rendered:

Tables

Table 1.1, header and rows 1-6 are correctly rendered, rows 7-16 are not rendered.
Tables 2.1, 2.2, 2.3, 2.4, 2.5, 2.6 are correctly rendered.
Table 3.1 has missing rows.
Table 3.2 is correctly rendered.

Example: Listing 1
HTML correctly rendered: https://leaf-obd.readthedocs.io/en/latest/pid/358.html#elm327-358-turn-signal
Screenshot of PDF incorrectly rendered:

Making the following changes to to the source documents has no effect on the PDF produced by Read the Docs.
However, when built on a workstation the following changes (which may be specific the the workstation environment) do result in a correctly built PDF with make latexpdf. The PDF contains all images, correctly rendered tables, and readable listings.

Remove Unicode char ⋅ (U+22C5)! Package inputenc Error: Unicode char ⋅ (U+22C5)
(inputenc)                not set up for use with LaTeX.

Remove equations in table cells! Package amsmath Error: \begin{split} won't work here.

See the amsmath package documentation for explanation.
Type  H <return>  for immediate help.
...

l.573 \end{tabulary}
! LaTeX Error: Bad math environment delimiter.

Remove equations from source/pid/5b3.rst and source/pid/5c5.rst

Reverting to the default Read the Docs latex_engine resolves all issues with the PDF.
diff --git a/source/conf.py b/source/conf.py
index 6bc5d10..b8f6f38 100644
--- a/source/conf.py
+++ b/source/conf.py
@@ -116,10 +116,8 @@ latex_elements = {
 \setcounter{tocdepth}{1}
 """,
 }
-latex_engine = "platex"
 latex_show_pagerefs = True
 latex_show_urls = "footnote"
-latex_use_xindy = False

 linkcheck_ignore = [


Nand support

Hi bvernoux
Can you add firmware later x8 and x16 nand support (I read about nand support somewhere in web for this board)? And also add 1-2-3 wire support would be good. I noob but trying MN101EF31G MCU firmvare dumping MCU have a "Clock Synchronous Serial" port 2 or 3 wire adjustable, my board have a 2-wire type programming port, Bus pirate 2-wire is I2C based but I suspect this mcu Full or Half duplex SPI based (bus speed up to 5mhz datasheet). Some people tied MOSI and MISO together for half duplex SPI but one of the pin must be hi-z status other is working condition and other problem I can't understand "AAAh AAh 555h 55h" sequence in flash command table, datasheet says command address = 0x04000 + addr .Command data ? .Can you any advice for firmvare dumping for me or any source link? I am really helpless for this thing and I open couple of thread in forums but nobody help me. Thanks, sorry for my English.

Such feature (NAND 8 or 16bits) Is planned in TODO list but not in top priority (as I'm the only one developer doing this project in my spare time) as there is lot of things to do before, if a developer is motivated (and have time & hardware to test it) I can even provide free HydraBus hardware for such task.

I'm waiting hardware to test NAND/NOR Flash (mainly 48-Pin TSOP), tests will be done on:

Hynix HY27US08281A NandFlash 3.3V 16Mbyte
Spansion S29GL064A90TFIR4 NandFlash 3.3V 8MByte (x8/x16)
Spansion S29AL016J70TFI020 NandFlash 3.3V 2MByte (2 M x 8-Bit/1 M x 16-Bit)
Samsung K9F1G08U0C NandFlash 3.3V 16Mbyte (x8) from http://www.waveshare.com/wiki/NandFlash_Board_(A)
Samsung S29GL128P NORFlash 56TSOP (x16) (to test with flashrom support) from http://www.waveshare.com/wiki/NorFlash_Board_(A)

Hello , i am understand and thanks for your answer. Some people including me search this type cheap or diy project for usb flash and ssd data recovery(nand programmers are very expensive). These features would be nice if it were. I am so sorry for the delayed answerSorry for my English, thanks.

NandFlash support is coming Read ID already work with my Samsung NandFlash (Samsung K9F1G08U0C NandFlash 3.3V 16Mbyte (x8) (TSOP48) from http://www.waveshare.com/wiki/NandFlash_Board_(A))
see https://github.com/bvernoux/hydrafw/tree/flash

Made some changes in order to get this mode working.
Right now, it is possible to read/write 8x NANDs with the patches included in this branch
To test it, you can use this modified version of DumpFlash
Demo :
~/Projects/DumpFlash > python2 DumpFlash.py -i                                                                                [master]
Into BBIO mode
Switching to flash mode
Setting chip enable
Full ID:	AD73AD73AD73
ID Length:	6
Name:		NAND 16MiB 3,3V 8-bit
ID:		0x73
Page size:	0x200
OOB size:	0x10
Page count:	0x8000
Size:		0x10
Erase size:	0x4000
Block count:	1024
Options:	0
Address cycle:	3
Bits per Cell:	4
Manufacturer:	Hynix

NAND 8x mode has been added to hydraFW (https://github.com/bvernoux/hydrafw/commit/5247a8379c008bc5c481aa8afc3f5dc9e2c6a620)

Since Hydraflash is now available for purchase (https://lab401.com/collections/hardware/products/hydraflash), we can consider this issue as closed.


move some things from cdk/testing to cdk/internal-testing

This is in preparation for when we publish cdk/testing with the component harness infrastructure. cdk/internal-testing will be an unpublished package that we use for our own shared testing utilities.
I've also added @docs-private to all symbols that remain in cdk/testing. They are not really intended to be used directly (at least not until we review the API and add docs and tests), instead they will be used by the harness infrastructure which will be a public API.

That sounds good as long as it works. I know some of our scripts don't really expect to deal with tertiary entry points, but it might be ok since we're not publishing it. I'll try putting it under @angular/cdk/private/testing and see if it works


markPoint doesn't show sometimes

Version
5.3.0
Link to Minimal Reproduction
https://codepen.io/rogelio-trivi-o-gonz-lez/pen/WNXaOVB
Steps to Reproduce
depending on params, sometime draw markPoint and sometimes don't. One example of each on codepen
Current Behavior
markpoint draw sometimes
Expected Behavior
markpoint draw always
Environment
- OS:
- Browser:
- Framework:

Any additional comments?
No response

@rogeliotg I created a PR. Can this solve your problem~?


Aria-labels can't be added to slider buttons

For compliance, I need to add aria-labels to the slider buttons in an implementation like this one: http://localhost:9001/?path=/story/slider--rtl-multiple-handle. There doesn't seem to be a way to do this currently.

Running into the same issue.

+1
I would love to see this fix as well!


Automated cherry pick of #2824: Fix for what looks like a copy-paste error

Cherry pick of #2824 on release-v1.31.
#2824: Fix for what looks like a copy-paste error

/merge-when-ready delete-branch

OK, I will merge the pull request when it's ready, leave the commits as is when I merge it, and delete the branch after I've merged it.

I'm sorry but I failed delete the branch after merging the pull request.


nodejs: 10.22.0 -> 10.22.1, 12.18.3 -> 12.18.4

Motivation for this change
https://nodejs.org/en/blog/release/v10.22.1/
https://nodejs.org/en/blog/release/v12.18.4/
Things done

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

[X] NixOS
[X] macOS
[ ] other Linux distributions

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

Backported to 20.09 in https://github.com/NixOS/nixpkgs/commit/05a6efb5084d3a46742b7aa2301f1bbb9f31c93d https://github.com/NixOS/nixpkgs/commit/ea4b39d48a9153781df67e301ca917651b88c9ad


set new checkpoits till today

added:
Block 1000000
Block 1200000
Block 1204390
will help at sync from scratch and helps to find right chain.

Thank you @Caberhagen,  the codebase will be completely new


Error when building Docker image from demo

Running docker build with Dockefile produces the following error:
Step 7/10 : RUN apt-get -y install linux-tools-common linux-tools-`uname -r` linux-cloud-tools-`uname -r` lttng-tools lttng-modules-dkms liblttng-ust0 zip
 ---> Running in bcc38dd5d269
Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package linux-tools-4.9.49-moby
E: Couldn't find any package by regex 'linux-tools-4.9.49-moby'
E: Unable to locate package linux-cloud-tools-4.9.49-moby
E: Couldn't find any package by regex 'linux-cloud-tools-4.9.49-moby'
The command '/bin/sh -c apt-get -y install linux-tools-common linux-tools-`uname -r` linux-cloud-tools-`uname -r` lttng-tools lttng-modules-dkms liblttng-ust0 zip' returned a non-zero code: 100

I see the same or at least a similar issue with the current version of Docker on Windows.  I assume this means that linux tools for the linuxkit kernel are not in the default apt repos.  Do these exist?  The linux tools and perf binaries for linuxkit need to be built added to apt to get this DockerFile to work.
Ironically this means Docker for Windows isn't working but I assume that this script would work if I was running on an Ubuntu machine.
Step 7/10 : RUN apt-get -y install linux-tools-common linux-tools-`uname -r` linux-cloud-tools-`uname -r` lttng-tools lttng-modules-dkms liblttng-ust0 zip
 ---> Running in d585d91c6749
Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package linux-tools-4.9.125-linuxkit
E: Couldn't find any package by regex 'linux-tools-4.9.125-linuxkit'
E: Unable to locate package linux-cloud-tools-4.9.125-linuxkit
E: Couldn't find any package by regex 'linux-cloud-tools-4.9.125-linuxkit'


ja: Make docs/concepts/architecture/controller.md follow v1.19 of the original text

update ja/docs/concepts/architecture/controller.md
#26854

/assign @nasa9084

@KobayashiD27 Base branch is incorrect. Please use dev-1.19-ja.1 .

@KobayashiD27 Base branch is incorrect. Please use dev-1.19-ja.1 .

Thank you for pointing out.
Sorry, I took mistake. I changed the base branch.

/lgtm

I don't think these blanks are necessary. Please check there's any other too.

Thanks. I checked for unnecessary blanks, but nothing else.

/approve
/lgtm


Added python util

Contains a few well used functions in an interface to allow users to import into a given python script and use these functions.
We intend to evolve it as we develop more examples.

Hi andy,
I am upgrading the tutorials for the other issue, should I include this in that or here. Yes the many files thing should be doable. I can upgrade it if you want, now or later?

I think for this PR you can just add a one-line page saying something like "We have a python utility package here: link" and link it from the main page or something. Then your upgraded tutorial can be a separate PR
If it's easy to do the many files thing now, then go for it; otherwise, we can just open an issue and come back to it later

I've added a simple tutorial. Let's open a new issue for the multiple files, I need to look over some examples

continued on https://github.com/Mu2e/TrkAna/issues/178