Cannot configure solution that contains a .Net Core project

How to reproduce
Create a solution with a .Net Core library
What version and selected configuration ?
v1.6.0b3
Can you provide detailed log of your build ?
When running DllExport_configure.bat
[03:11:55 PM.9349] [Fatal] ERROR-Wizard: The default XML namespace of the project must be the MSBuild XML namespace. If the project is authored in the MSBuild 2003 format, please add xmlns="http://schemas.microsoft.com/developer/msbuild/2003" to the <Project> element. If the project has been authored in the old 1.0 or 1.2 format, please convert it to MSBuild 2003 format.  D:\Air\Source\Repos\CLR-DEV9\CLR_DEV9\CLR_DEV9_CORE.csproj

Thanks for the report.
The problem because of new SDK-based format of project files and old MS-logic.
That is, this part controlled by MvsSln project, and this exactly from Microsoft.Build.Evaluation-classes. As I understand, today MS don't want to support many incompatible changes (like this https://github.com/3F/MvsSln/issues/1) at least for .net 4.0...
But, this is not a big problem for DllExport project at least for current features :)
Before fixes, temporarily try to use this by adding xmlns="http://schemas.microsoft.com/developer/msbuild/2003" attr, for example:
<Project Sdk="Microsoft.NET.Sdk" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
  <PropertyGroup>
    <TargetFramework>netcoreapp2.0</TargetFramework>
  </PropertyGroup>
</Project>

It now complains about the Remove attribute in element  being unrecognizable.
Below is the containing item group
    <Compile Remove="obj_netfx\**" />
    <EmbeddedResource Remove="obj_netfx\**" />
    <None Remove="obj_netfx\**" />
</ItemGroup>```

It also complains about the Version attribute in element <PackageReference>

temporarily removing theses attributes, in addition to your suggestion, allows the configuration tool to run, allowing me to add it to both netfx and netcore projects (although the netcore won't build, complaining that it can't find ildasm.exe (using default IL Assembler)).

well yes, because of obsolete schema.

it can't find ildasm.exe

Can you clarify this part in details ? Currently DllExport still does not support .net core projects if you're trying this. But if you have problem for others, please send detailed build log.

This is on a .Net Core project, when attempting to build, there is an error stating it can't find ildasm.exe
The relevant part of the log;
1>Target DllExportMod:
1>  Using "DllExportAppDomainIsolatedTask" task from assembly "D:\Air\Source\Repos\CLR-DEV9 - Copy\packages\DllExport.1.6.0-beta3\tools\RGiesecke.DllExport.MSBuild.dll".
1>  Task "DllExportAppDomainIsolatedTask"
1>    Cannot find lib.exe in 'D:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\bin'.
1>    D:\Air\Source\Repos\CLR-DEV9 - Copy\packages\DllExport.1.6.0-beta3\tools\net.r_eg.DllExport.targets(56,5): error : Microsoft.Build.Utilities.ToolLocationHelper could not find ildasm.exe.
1>  Done executing task "DllExportAppDomainIsolatedTask" -- FAILED.
1>Done building target "DllExportMod" in project "CLR_DEV9_CORE.csproj" -- FAILED.

If you want the full log I can also attach it (it's quite long).

yes, please attach the full detailed log as an additional file using the following command:
msbuild <YourSlnFile> /t:Rebuild /m:4 /v:diag > build.log

https://we.tl/LX7hwZTwrk
The Solution has 4 projects
CLR_DEV9 is the main project and is a .netfx project
CLR_DEV9_CORE is the same project, but configured as a .netcore project
DNS Test Thing & UPNP Test Thing are test projects and do not use DllExport (and are both .netfx projects).
The solution file had C++ (Linux) projects, but those where removed to install v1.6.0 (and never readded)

Something went wrong with your configuration because I see calling DllExportMod for both projects "CLR_DEV9.csproj" & "CLR_DEV9_CORE.csproj" (.NETCoreApp,Version=v2.0)
4>Target "DllExportMod: (TargetId:77)"
in file "D:\Air\Source\Repos\CLR-DEV9 - Copy\packages\DllExport.1.6.0-beta3\tools\net.r_eg.DllExport.targets"
from project "D:\Air\Source\Repos\CLR-DEV9 - Copy\CLR_DEV9\CLR_DEV9.csproj" (target "PostBuildEvent" depends on it):

5>Target "DllExportMod: (TargetId:86)"
in file "D:\Air\Source\Repos\CLR-DEV9 - Copy\packages\DllExport.1.6.0-beta3\tools\net.r_eg.DllExport.targets"
from project "D:\Air\Source\Repos\CLR-DEV9 - Copy\CLR_DEV9\CLR_DEV9_CORE.csproj" (target "PostBuildEvent" depends on it):

Can you try to reconfigure all this again by removing from all projects, and also choose '.targets file' storage (.net.dllexport.targets). I still can't reproduce this error even if .net core-based project has dependencies to projects with DllExport modification. In addition, you also may reproduce this structure of projects as an simple demo, then attach for debug.
p.s.: please attach anything (including text-based log above) as zip archive etc. still via github attachments.

The configuration was intentional, I was wanting to see if DllExport export worked with .Net Core projects (It didn't).
The solution builds correctly if DllExport is removed from CLR_DEV9_CORE and only configured for CLR_DEV9.
I mentioned before that the two projects are effectively the same, CLR_DEV9 is intended for windows users and CLR_DEV9_CORE is the Linux port (hence the need for CoreCLR), the builds are not dependent on each other.
If DllExport does not support .NetCore, then I will have to create a wrapper for the .NetCore version of the project.

The solution builds correctly if DllExport is removed from CLR_DEV9_CORE and only configured for CLR_DEV9.

Good ! as I expected.
And yes, again: we still have no official support for .net core projects.

Details: https://github.com/3F/DllExport/issues/17#issuecomment-335001440

@TheLastRar please check the latest changes - build70 ( 20eb9db )

The new bat file failed with
'a4' is not recognized as an internal or external command,
operable program or batch file.
MSBuild tools was not found. Try with `-msb` key. `-help` for details.

If i use the old bat file, but keep the files in DllExport.1.6.0-beta3 as build70, the configuration tool launches correctly, detecting the Core and C++ projects as unload-able and allows me to configure the framework project (CLR_DEV9).
I uninstalled and reinstalled DllExport to check if that works and builds (it does).

Thanks for the reply ! Seems problem for LF from AppVeyor CI
Please check new build71 (same commit) with:
git config --global core.autocrlf true

https://ci.appveyor.com/project/3Fs/dllexport/build/build-71

Yes that version works correctly

Good ! v1.6 will be soon. Anyone else, please test latest beta as carefully as possible.


METRON-1518 Build Failure When Using Profile HDP-<IP_ADDRESS>

The build fails when using the 'HDP-<IP_ADDRESS>' profile.
/Users/ottofowler/src/apache/forks/metron/metron-analytics/metron-profiler/src/main/java/org/apache/metron/profiler/bolt/ProfileBuilderBolt.java:45:
error: cannot find symbol
import org.apache.storm.StormTimer;
                       ^
  symbol:   class StormTimer
  location: package org.apache.storm
/Users/ottofowler/src/apache/forks/metron/metron-analytics/metron-profiler/src/main/java/org/apache/metron/profiler/bolt/ProfileBuilderBolt.java:167:
error: cannot find symbol
  private StormTimer expiredFlushTimer;
          ^
  symbol:   class StormTimer
  location: class ProfileBuilderBolt
/Users/ottofowler/src/apache/forks/metron/metron-analytics/metron-profiler/src/main/java/org/apache/metron/profiler/bolt/ProfileBuilderBolt.java:450:
error: cannot find symbol
  private StormTimer createTimer(String name) {
          ^
  symbol:   class StormTimer
  location: class ProfileBuilderBolt

This was caused by my PR; #977.  That code relied on a class that is only available in Storm 1.0.3+.  When using the Maven profile HDP-<IP_ADDRESS>, the code is built against Storm 1.0.1, where that class is not defined.
Changes

This completely removes the use of aStormTimer.  There is no need for it.  I had thought it would help me drive testing, but it has not ended up being useful at all.

An executor is used to drive a separate thread which flushes expired profiles on a regular basis.

Updated the Travis CI builds so they are run with the HDP-<IP_ADDRESS> profile.  This ensures that the CI tests are run against the same version of Storm as the dev environments are built against.  This will help ensure we catch similar issues in the future.

Manual Testing

Run a development environment and ensure that alerts are visible in the Alerts UI.

+1 by inspection, thanks!

+1 ship it

Thanks for the reviews.  Just to be sure, I ran up the CentOS dev environment, validated that alerts are being created, created a profile and made sure that values were written.


Document the "transformers" field in the pubspec

This should only happen once we're ready to put forth barback for more public consumption.

This issue has been moved to dart-lang/pub#628.


Any option to use SPDY?

SPDY now available for nginx. Any plan to do automatically?
Thanks :)

Yes - Love that SPDY is enabled.  Thank you.
FYI - you can check your compliance here:
https://spdycheck.org/
Also, you might want to add this to the server block to add the HSTS header.
config to enable HSTS(HTTP Strict Transport Security) https://developer.mozilla.org/en-US/docs/Security/HTTP_Strict_Transport_Security
add_header Strict-Transport-Security "max-age=31536000; includeSubdomains;";
Reference Links/Information:
https://scotthelme.co.uk/setting-up-hsts-in-nginx
https://gist.github.com/plentz/6737338
https://raymii.org/s/tutorials/HTTP_Strict_Transport_Security_for_Apache_NGINX_and_Lighttpd.html

Just add listen 80 spdy; to any server block to enable spdy.

This shouldn't be done. SPDY doesn't use port 80 like regular HTTP does.
Also, since HTTP/2 will be released soon SPDY will no longer be relevant so I suggest closing this issue, @rahul286.

Closing this as we now have HTTP2 :)


Cursor Style Not Working (Safari)

The css cursor properties, such as pointer and text, do not work and only appear as default cursor instead.
On the main page, the text cursor appears from time to time when the first mouse hover start from the bottom part of the "Welcome to Glance", and continues to show as text cursor when hovering outside of the "Welcome to Glance" section border.
(May also relate to issue #164.)
Question/Concern: Maybe it's because I have the newest OS version?

Ok so the text cursor does appear over text in the welcome box, then returns to a normal cursor when not over text. The cursor also changes to a hand style when hovering over buttons which i believe is as designed.
I will be closing this issue if there are no objections.


Inconsistent commenting

Thanks for this nice plugin. It surely can replace tcomment which I am currently using.
While using this plugin, I found a weird behavior while commenting. So, If some block of code has an empty line then the commenting doesn't exclude the tab width. The behavior is clearly shown in the video below.
https://user-images.githubusercontent.com/24727447/128667810-736b5014-cf9e-4c87-a247-be0b905be365.mp4
As you can see, the function below has some empty lines thus the weird commenting is happening. But the above function doesn't have empty lines, so the commenting is as expected. I also checked this behavior in typescript and this issue is also there.

Any update on this?

I have created https://github.com/numToStr/Comment.nvim  if you wanna use it.

Nice, I'll check it out

@cacharle ahh sorry pal, been supper busy, @paegodu did a nice fix for this.


Mash up the index.html and its relative links

https://github.com/Azure/azure-sdk-tools/issues/1246

https://github.com/Azure/azure-sdk-tools/issues/1246

@sima-zhu  do you plan to run this mash-up on the existing docs? While keeping the /api/index.html working as well, at least for the existing docs.


Individual Permissons?

Description
I want to share a board with my friend but have it so he cannot see my main board. I do not want it to be anonymously accessible, but rather by login to protect the page.
Please tick the boxes

[X] You've read the docs
[X] You've checked for duplicate issues

Duplicate of #1668


Molecule not finding Python Docker driver

Issue Type

Bug report

Molecule and Ansible details
ansible --version: 2.3.1
molecule --version: 1.25.0
docker version 1.12.6
docker python sdk version 2.4.2
OS version RHEL 7.4

Molecule installation method: pip
Ansible installation method: OS Package from Tower
Docker installation: os package
Docker Python SDK installation: pip

Desired Behaviour
Molecule use the Python Docker SDK bindings during a test.
Actual Behaviour (Bug report only)

Error: python docker drive missing, install the docker package

Right, you need to install it :)
pip install docker

As stated in the issue above, we already installed the docker sdk binding with pip. The issue also goes beyond what was asked in the template and rpovides extra information beyond what was requested.

It's a simple try/catch around the import of docker.  I can't reproduce the issue.
[jodewey:~/git/molecule/test/scenarios/command_test] [molecule-env-2.7.13] v1+ ± molecule test --driver docker
ERROR: python docker driver missing, install the docker package.
[jodewey:~/git/molecule/test/scenarios/command_test] [molecule-env-2.7.13] v1+ 1 ± pip install docker -U
Collecting docker
  Using cached docker-2.4.2-py2.py3-none-any.whl
Requirement already up-to-date: six>=1.4.0 in /Users/jodewey/.pyenv/versions/2.7.13/envs/molecule-env-2.7.13/lib/python2.7/site-packages (from docker)
Collecting requests!=2.11.0,!=2.12.2,!=2.18.0,>=2.5.2 (from docker)
  Using cached requests-2.18.3-py2.py3-none-any.whl
Requirement already up-to-date: backports.ssl-match-hostname>=3.5; python_version < "3.5" in /Users/jodewey/.pyenv/versions/2.7.13/envs/molecule-env-2.7.13/lib/python2.7/site-packages (from docker)
Requirement already up-to-date: ipaddress>=1.0.16; python_version < "3.3" in /Users/jodewey/.pyenv/versions/2.7.13/envs/molecule-env-2.7.13/lib/python2.7/site-packages (from docker)
Collecting websocket-client>=0.32.0 (from docker)
  Using cached websocket_client-0.44.0-py2.py3-none-any.whl
Requirement already up-to-date: docker-pycreds>=0.2.1 in /Users/jodewey/.pyenv/versions/2.7.13/envs/molecule-env-2.7.13/lib/python2.7/site-packages (from docker)
Collecting certifi>=2017.4.17 (from requests!=2.11.0,!=2.12.2,!=2.18.0,>=2.5.2->docker)
  Using cached certifi-2<IP_ADDRESS>-py2.py3-none-any.whl
Collecting chardet<3.1.0,>=3.0.2 (from requests!=2.11.0,!=2.12.2,!=2.18.0,>=2.5.2->docker)
  Using cached chardet-3.0.4-py2.py3-none-any.whl
Collecting urllib3<1.23,>=1.21.1 (from requests!=2.11.0,!=2.12.2,!=2.18.0,>=2.5.2->docker)
  Using cached urllib3-1.22-py2.py3-none-any.whl
Requirement already up-to-date: idna<2.6,>=2.5 in /Users/jodewey/.pyenv/versions/2.7.13/envs/molecule-env-2.7.13/lib/python2.7/site-packages (from requests!=2.11.0,!=2.12.2,!=2.18.0,>=2.5.2->docker)
Installing collected packages: certifi, chardet, urllib3, requests, websocket-client, docker
  Found existing installation: chardet 3.0.2
    Uninstalling chardet-3.0.2:
      Successfully uninstalled chardet-3.0.2
  Found existing installation: requests 2.13.0
    Uninstalling requests-2.13.0:
      Successfully uninstalled requests-2.13.0
  Found existing installation: websocket-client 0.40.0
    Uninstalling websocket-client-0.40.0:
      Successfully uninstalled websocket-client-0.40.0
  Found existing installation: docker 2.2.1
    Uninstalling docker-2.2.1:
      Successfully uninstalled docker-2.2.1
Successfully installed certifi-2<IP_ADDRESS> chardet-3.0.4 docker-2.4.2 requests-2.18.3 urllib3-1.22 websocket-client-0.44.0
[jodewey:~/git/molecule/test/scenarios/command_test] [molecule-env-2.7.13] v1+ ± molecule test --driver docker
--> Destroying instances...
--> Checking playbook's syntax...

playbook: playbook.yml
--> Creating instances...
--> Creating Ansible compatible image of ubuntu:latest ...
--> Building ansible compatible image...
	Step 1/8 : FROM ubuntu:latest
	Pulling fs layer ...
	Waiting ...
	Downloading ...
	Verifying Checksum ...
	Download complete ...
	Downloading ...
	Verifying Checksum ...
	Download complete ...
	Downloading ...
	Verifying Checksum ...
	Download complete ...
	Downloading ...
	Verifying Checksum ...
	Download complete ...
	Downloading ...
	Download complete ...
	Extracting ...
	Pull complete ...
	Extracting ...
	Pull complete ...
	Extracting ...
	Pull complete ...
	Extracting ...
	Pull complete ...
	Extracting ...
	Pull complete ...
	Digest: sha256:34471448724419596ca4e890496d375801de21b0e67b81a77fd6155ce001edad ...
	Status: Downloaded newer image for ubuntu:latest ...
	 ---> ccc7a11d65b1
	Step 2/8 : RUN /bin/sh -c 'if [ -x "$(command -v apt-get)" ]; then apt-get update && apt-get install -y python sudo bash; fi'
	 ---> Running in d41583d012cf
	Get:1 http://archive.ubuntu.com/ubuntu xenial InRelease [247 kB]
	Get:2 http://security.ubuntu.com/ubuntu xenial-security InRelease [102 kB]
	Get:3 http://security.ubuntu.com/ubuntu xenial-security/universe Sources [43.9 kB]
	Get:4 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages [426 kB]
	Get:5 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [102 kB]
	Get:6 http://security.ubuntu.com/ubuntu xenial-security/restricted amd64 Packages [12.8 kB]
	Get:7 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 Packages [191 kB]
	Get:8 http://security.ubuntu.com/ubuntu xenial-security/multiverse amd64 Packages [2935 B]
	Get:9 http://archive.ubuntu.com/ubuntu xenial-backports InRelease [102 kB]
	Get:10 http://archive.ubuntu.com/ubuntu xenial/universe Sources [9802 kB]
	Get:11 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages [1558 kB]
	Get:12 http://archive.ubuntu.com/ubuntu xenial/restricted amd64 Packages [14.1 kB]
	Get:13 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages [9827 kB]
	Get:14 http://archive.ubuntu.com/ubuntu xenial/multiverse amd64 Packages [176 kB]
	Get:15 http://archive.ubuntu.com/ubuntu xenial-updates/universe Sources [210 kB]
	Get:16 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages [784 kB]
	Get:17 http://archive.ubuntu.com/ubuntu xenial-updates/restricted amd64 Packages [13.3 kB]
	Get:18 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages [652 kB]
	Get:19 http://archive.ubuntu.com/ubuntu xenial-updates/multiverse amd64 Packages [17.5 kB]
	Get:20 http://archive.ubuntu.com/ubuntu xenial-backports/main amd64 Packages [4934 B]
	Get:21 http://archive.ubuntu.com/ubuntu xenial-backports/universe amd64 Packages [6236 B]
	Fetched 24.3 MB in 19s (1261 kB/s)
Reading package lists...

[jodewey:~/git/molecule/test/scenarios/command_test] [molecule-env-2.7.13] v1+ 2 ± pip freeze | grep docker
docker==2.4.2
docker-pycreds==0.2.1

I would double check your python environment is setup properly.  Molecule is doing nothing special but an import.

Thanks for the non-reproducibility proof. We will double-check the environment tomorrow, as that does seem the most likely explanation.
Did you test that on a RHEL 7.4 env by any chance (a CentOS 7.4 Vagrant instance, for example, would be the same as far as I am concerned)?

So we figured out the issue. The exception message was assuming that the failure to import the docker module meant that it was not installed. We did a simple python script to import docker and discovered in the stack trace that what actually was failing was the import of a dependency lower down the chain. We updated/reinstalled dependencies iteratively to work it out, since the dependencies installed for the docker sdk bindings were not accurate for what was actually required.
Could you please update the exception message to expand to our situation so in the future people will know the problem may be something else?

Can you provide the details as to what was missing?

If molecule was installed using pip then molecule's dependencies will be installed.  However, molecule does require you to install the driver dependencies.  By running pip install docker you should get all of those dependencies installed.  I'm thinking a pip install -U docker would have corrected any issue you had with docker's deps.

As noted above, the basic installation procedure was installing docker via yum, ansible via package from a tower install, molecule via pip, and docker (python sdk bindings) via pip. Doing pip install docker did pick up its dependencies, but python failed to find them until we reinstalled all of them.
In any case, the point is there is no bug with molecule here, just an exception message that was inaccurate for our situation.

Closing. currently satisfied with the level of error reporting in Molecule.  Others can reference this issue, if they run across this problem.  Will reevaluate my decision in the future, if this becomes a more prominent problem.

I'm running into this, as is:
https://www.503error.com/2019/molecule简介/1657.html
It's difficult to pin down what exactly is missing, I've reinstalled the docker pywheel without success.

For anybody finding this in a google search, pip install docker didn't do it, but pip install molecule-plugins did.

For Molecule 5+:
pip install 'molecule-plugins[docker]'


[Test]
public void EventResourcesCanBeZeroedOut()
{
    var e = GetSimpleEvent();
    var resources = new[] {"Foo", "Bar", "Baz"};

    e.Resources = new List<string>(resources);
    CollectionAssert.AreEquivalent(e.Resources, resources);

    var newResources = new[] {"Hello", "Goodbye"};
    e.Resources = new List<string>(newResources);
    CollectionAssert.AreEquivalent(e.Resources, newResources);
    Assert.IsFalse(e.Resources.Any(r => resources.Contains(r)));

    e.Resources = null;
    //See https://github.com/rianjs/ical.net/issues/208 -- this should be changed later so the collection is really null
    Assert.AreEqual(0, e.Resources?.Count);
}

nuget package 2.2.31


Enable multiclient support

Add orchestration of sandboxes on multiple host client instances.

The work is being done on a different branch.


irmin-pack: use Lwt in gc finished callback

This PR updates the gc finished callback to allows callers to more easily use Lwt.

Codecov Report

Merging #2035 (fdd16e8) into main (e9ac278) will decrease coverage by 0.00%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main    #2035      +/-   ##
==========================================
- Coverage   64.51%   64.50%   -0.01%
==========================================
  Files         130      130
  Lines       15574    15576       +2
==========================================
+ Hits        10047    10048       +1
- Misses       5527     5528       +1

Impacted Files
Coverage Δ

bench/irmin-pack/trace_replay.ml
41.63% <0.00%> (-0.18%)
:arrow_down:

src/irmin-pack/unix/ext.ml
65.78% <0.00%> (-0.20%)
:arrow_down:

src/irmin-test/store.ml
94.82% <0.00%> (-0.06%)
:arrow_down:

src/irmin-fs/irmin_fs.ml
82.42% <0.00%> (+1.21%)
:arrow_up:

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


Just downloading Metadate doesnt work anymore.

After updating it seems like the feature of just downloading the metadata of a video doesnt work.
I used this: pyk.save_tiktok("https://www.tiktok.com/@vaex.edits/video/7278224599261777185?is_from_webapp=1&sender_device=pc&web_id=7295861439716460064", False,'video_data.csv','chrome')

After looking into this, I'm seeing that for me, TT doesn't store nearly as much metadata in its video pages using the new data storage format denoted by __UNIVERSAL_DATA_FOR_REHYDRATION__. However on my pages I still see the original format denoted by SIGI_STATE which contains all the expected metadata. So from that I conclude that different users will see different results depending on which data package they get.
For your case, I would check the page source to see if the string 'SIGI_STATE' is present; since metadata isn't working for you I'm guessing it's not. If that's the case, someone will need to rewrite pyktok's metadata-saving code to function properly with the new data package, which I'm not seeing. (The existing code attempts to do this but references a JSON key that is absent for me.) I'll leave this open until the situation is resolved.

using the same call i keep on getting the same error:
tt_video_url = tt_json["__DEFAULT_SCOPE__"]['webapp.video-detail']['itemInfo']['itemStruct']['video']['downloadAddr']                    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^ KeyError: 'downloadAddr'

Yeah, 'webapp.video-detail' doesn't exist for me, but I have SIGI_STATE so the old way still works for me. I suggest you explore that JSON object to see if the data you want are in there--there's no guarantee you and I will see the same content.

I am trying to run that function specify_browser('chrome') but giving me PermissionError: [Errno 13] Permission denied: 'C:\Users\Usman\AppData\Roaming\..\Local\Google\Chrome\User Data\Default\Network\Cookies'
kindly help me to resolve that issue. I am stuck there after trying to resolve this issue

This works as of today, so closing.


[Feature request] --disable-preserve-newlines to one line

Could it be configurable so that multiple consecutive empty lines can be replaced with one empty line rather than removed entirely?
e.g.
function Whatever ()
{
  var a = 1;

  this.something = 1;
  this.blah = function ()
  {

  }

  this.blah2 = function ()
  {

  }

};

becomes
function Whatever ()
{
  var a = 1;

  this.something = 1;
  this.blah = function ()
  {

  }

  this.blah2 = function ()
  {

  }

};

rather than
function Whatever ()
{
  var a = 1;
  this.something = 1;
  this.blah = function ()
  {
  }
  this.blah2 = function ()
  {
  }
};

Thanks again for your time.

Make sense to me as a default blank line preservation behavior, I'll take a stab at that.


Enable WriteCore feature for changeanalysis

We need to enable WriteCore feature to changeanalysis. Therefore add use-write-core: true and do a regen.

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.ResourceManager.ChangeAnalysis


Bump harmonize to 1.4.0

Please bump harmonize to support running in node v0.12 and iojs. This request obviously does not attempt to address all issues to fully support node v0.12 or iojs, but does allow users to install and run jest-cli in those environments. Tested in node v0.10.36, node v0.12.0, and iojs v1.2.0.
Fixes facebook/jest/issues/235.
Part of the work required for facebook/jest/issues/243.
See dcodeIO/node-harmonize/issues/1.

:+1: This should be merged ASAP, without this the call to harmonize in jest on 0.12 causes a major memory leak (in addition to simply not working).

Just published 0.3.0 which includes this update. Thanks a ton for sending this over!

Just an FYI - the version of harmonize included with<EMAIL_ADDRESS>depends on<EMAIL_ADDRESS>which has a bug on Windows... (submitted a pull request). This bug prevents jest from running and renders it unusable.

I'm on v0.4.1 and Jest doesn't seem to work on anything more than node 0.10.x
I tried io.js 2.0.1 and that didn't work either. (I didn't try, io 1.x)
I didn't try to use the harmony flag anywhere.


Add 'forward-csp-report-to-telegram.js'

Forward CSP (Content Security Policy) Report to Telegram via bot with Cloudflare Workers.
Remember to set TELEGRAM_BOT_TOKEN and TELEGRAM_CHAT_ID in Cloudflare Workers Environment Secrets.
Example accepted JSON format (see https://scotthelme.co.uk/content-security-policy-an-introduction/):
Headers:
Content-Type: application/json

Body:
{
    "csp-report": {
        "document-uri": "https://scotthelme.co.uk",
        "referrer": "",
        "blocked-uri": "http://scotthelme.co.uk",
        "violated-directive": "default-src https:",
        "original-policy": "default-src https:; report-uri https://report.scotthelme.co.uk"
    }
}

References:

https://developers.cloudflare.com/workers/examples/read-post/
https://developers.cloudflare.com/workers/examples/fetch-json/
https://developer.mozilla.org/en-US/docs/Web/API/fetch
https://core.telegram.org/bots/api#sendmessage

Seems great, I think that will be better if we add content-type header and set status code to the responses, something like:
return new Response('{"code":200,"message":"Successfully reported."}', { headers: { "content-type": "application/json;charset=utf-8" }, status: 200 });
return new Response('{"code":400,"message":"Report content is not a valid json."}', { headers: { "content-type": "application/json;charset=utf-8" }, status: 400 });
return new Response('{"code":504,"message":"Report not received, channel maybe down."}', { headers: { "content-type": "application/json;charset=utf-8" }, status: 504 });

@fernvenue Updated. 😆


CVV number should display in dot like input Type password

Hello,
I faced one issue that CVV number is directly shown to user. The CVV number should not be visible to user because it is private for security.
Like password field

Hi @masterGennadij! Most online checkout forms don't mask out the CVC number. The PCI and other appropriate standards also don't recommend doing so.

This is very important this, I think so.
If possible, I want to hide the CVC part in CardElement
How can I do so?
Please help me.

Hi @dalba1992, there is no way to do this with Stripe Elements. Is there a particularly strong reason you need to do so?

@dalba1992 did you ever figure out a way around this?

Hello,
I have the same problem, but I have not seen a solution.
Could you please say whether such an opportunity has arisen?

Can this be re-opened?

The PCI and other appropriate standards also don't recommend doing so.

The customer experience when looking at their unhidden CVV is horrible. A person nearby can also read the CVV. This should be a feature provided by Stripe.

Please reopen this. This is very important. A nearby person may take picture and get all the credit card information


fixes \Datetime set to 0 instead of null

Coverage decreased (-0.2%) to 42.578% when pulling ba82dfdbbaadfb05986168d1e5809b0d89101305 on Tr0nYx:master into 1d701bac22f0f2eb649b6b7d503b7be2f7abb690 on Alpha-Trader:master.


Setting up documentation

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

Project coverage is 87.39%. Comparing base (4e5a2b5) to head (13f7dd0).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main       #9   +/-   ##
=======================================
  Coverage   87.39%   87.39%
=======================================
  Files           9        9
  Lines         746      746
=======================================
  Hits          652      652
  Misses         94       94

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


compile-cli issue for angular/cli on node

Bug Report or Feature Request (mark with an x)
- [ ] bug report -> please search issues before submitting
- [ ] feature request

Versions.

Repro steps.

The log given by the failure.

Desired functionality.

Mention any other details that might be useful.

Please either update this issue or create a new issue following the new issue template. This will allow us to triage and resolve your issues/requests quickly. Thank you!


Typescript Definitions are missing

When you install the package from npm, the typescript definitions although listed in the package.json are missing, when you check node_modules.

I don't know anything about typescript, what do you think should be done? the file exists,
although I don't remember who helped me create it. I personally loath typescript :)

Yeah I did see it in your repo, it's just not present on NPM as you should be able to see here https://www.npmjs.com/package/@yaireo/relative-time?activeTab=code , it is your ’package.json’ too, so as long as the file is present and not ignored with ’.npmignore’ or ’.gitignore’ it should uploaded when you next do a ’npm publish’.

fixed (now) in v1.0.4


⚠ Jenkins Plugins Artifactory has degraded performance

In f480dcb, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1390 ms

Resolved: Jenkins Plugins Artifactory performance has improved in e4ef4e4 after 12 minutes.


[INLONG-6009][Agent] Report data size to InLong Audit

Prepare a Pull Request
(Change the title refer to the following example)

[INLONG-6009][Agent] Report data size to audit

(The following XYZ should be replaced by the actual GitHub Issue number)

Fixes #6009

Motivation
Explain here the context, and why you're making that change. What is the problem you're trying to solve?
Modifications
Describe the modifications you've done.
Verifying this change
(Please pick either of the following options)

[ ] This change is a trivial rework/code cleanup without any test coverage.

[ ] This change is already covered by existing tests, such as:
(please describe tests)

[ ] This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end deployment with large payloads (10MB)
Extended integration test for recovery after broker failure

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)
If a feature is not applicable for documentation, explain why?
If a feature is not documented yet in this PR, please create a follow-up issue for adding the documentation

Unit tests failed, please check it:
Error:  Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 60.155 s <<< FAILURE! - in org.apache.inlong.agent.task.TestTaskWrapper
Error:  testTaskRunning(org.apache.inlong.agent.task.TestTaskWrapper)  Time elapsed: 60.044 s  <<< FAILURE!
java.lang.AssertionError: reader is not equals to writer expected:<3> but was:<2>
  at org.apache.inlong.agent.task.TestTaskWrapper.testTaskRunning(TestTaskWrapper.java:81)

Unit tests failed, please check it:
Error:  Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 60.155 s <<< FAILURE! - in org.apache.inlong.agent.task.TestTaskWrapper
Error:  testTaskRunning(org.apache.inlong.agent.task.TestTaskWrapper)  Time elapsed: 60.044 s  <<< FAILURE!
java.lang.AssertionError: reader is not equals to writer expected:<3> but was:<2>
  at org.apache.inlong.agent.task.TestTaskWrapper.testTaskRunning(TestTaskWrapper.java:81)

done


Dropping Compatibility Mode

Now that Shopify's theme requirements have been changed to require only IE9+, I'd like to drop the compatibility additions made in #22.
@bakura10  - wanted to get your thoughts on this as you were the main driving force behind the IE8 compatibility.

YES YES YES. I was so happy when I read the new guidelines. This can be removed :D.

Haha. That's the sort of positivity I was hoping for.
Will take this out and the Rivets portion of Cart.js will support only IE9+. The core library should support IE6+, depending on the version of jQuery used.

Compatibility mode dropped!
This change will be pushed in the next release, which will be 0.4.0.


Fix languages buttons accessible names

Description
Simple accessibility fix.
Motivation & Context
The name of the buttons must be included in their accessible names.
See Success Criterion 2.5.3 Label in Name for more details.
Types of change

Bug fix (non-breaking which fixes an issues)

Live previews

https://deploy-preview-1629--boosted.netlify.app/docs/5.2/components/orange-navbar/#with-additional-navbar

Checklist

[x] I have read the contributing guidelines
[x] My code follows the code style of the project (using npm run lint)
[x] My change introduces changes to the documentation
[x] My change introduces changes to the migration guide
[x] I have updated the documentation accordingly
[x] I have added tests to cover my changes
[x] All new and existing tests passed

Haven't reviewed the PR but I'm wondering whether we should mention it into the migration guide or not. I'd say yes but not 100% sure neither :)

Haven't reviewed the PR but I'm wondering whether we should mention it into the migration guide or not. I'd say yes but not 100% sure neither :)

Same here, I was waiting for your opinion ;)

Tried something in https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap/pull/1629/commits/44298a705bc42846c878ffa35589168f9db7f757. Let me know what you think.

Tried something in 44298a7. Let me know what you think.

Looks good. I am just wondering if we should add why it could be useful (because for accessibility purposes, the visible name must be included in the accessible name)? I don't know if the migration guide is the right place to explain that?


[CT-3041] [Bug] Semantic Model yml does not support doc blocks (reuse of descriptions)

Is this a new bug in dbt-core?

[X] I believe this is a new bug in dbt-core
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
The semantic model has entities, measures and dimensions. Each of these can have name, description etc.
Writing a manual description works, but re-using a predefined description does not work. Compilation fails with
12:51:01  Running with dbt=1.6.0
12:51:02  Registered adapter: databricks=1.6.1
12:51:02  Encountered an error:
Compilation Error
  Could not render {{ doc('orders_created') }}: 'doc' is undefined

Yes, I am absolutely sure the doc block referenced does exist as it is used in the metric description as well.
Expected Behavior
As everywhere else in dbt, I would expect DRY and I would expect to be able to reuse descriptions.
Steps To Reproduce
Semantic model that compiles:
semantic_models:
  - name: orders
    defaults:
      agg_time_dimension: created_date_local
    description: Some description
    model: ref('orders')
    # Entities. These usually corespond to keys in the table.
    entities:
      - name: order_key
        description: Manual description
        type: primary
      - name: city
        type: foreign
        expr: city_id
    # Measures. These are the aggregations on the columns in the table.
    measures:
      - name: orders_created
        description: Manual description
        expr: 1
        agg: sum
    # Dimensions. Either categorical or time.
    dimensions:
      - name: created_date_local
        description: Manual description
        type: time
        type_params:
          time_granularity: day
      - name: city_id
        type: categorical

and this does not compile
semantic_models:
  - name: orders
    defaults:
      agg_time_dimension: created_date_local
    description: Some description
    model: ref('orders')
    # Entities. These usually corespond to keys in the table.
    entities:
      - name: order_key
        description: "{{ doc('orders_created') }}"
        type: primary
      - name: city
        type: foreign
        expr: city_id
    # Measures. These are the aggregations on the columns in the table.
    measures:
      - name: orders_created
        description: "{{ doc('orders_created') }}"
        expr: 1
        agg: sum
    # Dimensions. Either categorical or time.
    dimensions:
      - name: created_date_local
        description: "{{ doc('orders_created') }}"
        type: time
        type_params:
          time_granularity: day
      - name: city_id
        type: categorical

I have tested the descriptions of entities, measures and dimensions separately as well, none of them accept the doc block.
Relevant log output
No response
Environment
- OS: Mac OS
- Python: 3.9.17
- dbt: 1.6.0

Which database adapter are you using with dbt?
spark
Additional Context
No response

Hey thanks for catching this! We definitely want to support docs blocks in semantic model yml files.

This feels very similar to:

https://github.com/dbt-labs/dbt-core/issues/8540


mark test 0220 with network tag

This test is missing the pytest network mark despite trying to access a webserver at cern.ch

Thanks!


ENH: RunEngine Signal Handling Refactor

Description

Tom and I split RunEngine into two classes: RunEngineBase which contains all of the core functionality and RunEngine which defines only the signal handling.
Motivation and Context

It is currently inconvenient to use RunEngine in a background thread, such as in a GUI, because it catches and handles SIGINT. These sorts of applications can use RunEngineBase instead, while the normal RunEngine class can continue to be used for normal operations.
How Has This Been Tested?

The existing bluesky tests still pass with the changes to RunEngine.

Codecov Report

Merging #1007 into master will increase coverage by 0.01%.
The diff coverage is 90.27%.

@@            Coverage Diff             @@
##           master    #1007      +/-   ##
==========================================
+ Coverage   90.25%   90.27%   +0.01%
==========================================
  Files          50       50
  Lines        8044     8060      +16
==========================================
+ Hits         7260     7276      +16
  Misses        784      784

Impacted Files
Coverage Δ

bluesky/run_engine.py
95.82% <90.27%> (+0.06%)
:arrow_up:

Continue to review full report at Codecov.

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

attn @ronpandolfi

Works great. Thanks!

Closing this in favor of the approach in #1008, which will accomplish the same goals and more in a better way.


Publish multiple systems page

This is ready for review! This PR:

publishes the new multiple systems page,
splits the circuits, protocols, and games page into two pages, and
adds new words to the spellchecker.

Thank you!


Added L.Path.Drag

It's a dragging interaction support(extension) for vector shapes. Consistent with Marker.Drag interaction and events. It also adds matrix transformation support to SVG/VML renderers, which can be used for other transformations - skew/scale/etc. As the matter of fact, I think this particular thing could make a good part of Leaflet core functionality.

Not necessary in the core. It's extremely rare to need vector shape dragging, and things like this are usually covered by sophisticated drawing/editing plugins like Leaflet.draw.

No, not the dragging, I agree, I meant the SVG/VML matrix transformations, on top of which things like that could be built. But of course, it's up to you to decide. Thanks for the consideration

@w8r oh wow, didn't notice that! I think this would work well as a separate plugin for future Leaflet 1.0 version , with Canvas support baked in too.

Ok, thanks, I'll look into it and will try to have it ready then. Good point about canvas renderer. I've already proposed that as a part of Leaflet.draw as well.


POS checkout name not used

Our POS payment method is called "KASSA"
But we dont see this in the CART
I expect to see KASSA on the button

Hi Sean,
Good point, we can use the title instead of the label. For now you can translate the label through Magento translation.
Regards,
Adyen

Hi Sean,
We have implement this.
Regards,
Rik
Adyen


Holographic ICE

Tested between Firefox and Chrome in various NAT configurations.
Fixes https://github.com/uProxy/uproxy/issues/1255

Very nice.
FYI, I just tried on my machine and the problems I experienced related to my Docker virtual interfaces are gone. Very cool.
I haven't looked at this in-depth -- right now, I had a couple of suggestions for reducing the amount of signalling messages. We also need to think a tiny bit more about backwards compatibility.

Review status: 0 of 8 files reviewed at latest revision, 7 unresolved discussions, some commit checks failed.

src/churn/candidate.ts, line 13 [r1] (raw file):
Some comments would really help here, even if just to link to the RTC, e.g.:
// Represents candidates as described in section 15.1 of the ICE RFC:
//   http://tools.ietf.org/html/rfc5245#section-15.1

It would be nice to provide an example candidate line too, e.g.
a=candidate:9097 1 udp 4175 <IP_ADDRESS> 50840 typ relay raddr <IP_ADDRESS> rport 56635

src/churn/candidate.ts, line 18 [r1] (raw file):
It seems like every candidate will have an address and port; perhaps rename these fields to address and port?

src/churn/candidate.ts, line 26 [r1] (raw file):
I wonder if you could get by with just modelling candidate lines?

src/churn/candidate.ts, line 29 [r1] (raw file):
This returns the publically addressable endpoint?

src/churn/candidate.ts, line 90 [r1] (raw file):
naming suggestion: stringToNumber

src/churn/churn.ts, line 218 [r1] (raw file):
Could you send multiple publicEndpoint signals? They're much more compact than the raw candidate lines.

src/churn/churn.ts, line 218 [r1] (raw file):
Can you filter out TCP candidates here? Right now, we're sending a lot of unuseable signalling messages.

Comments from the review on Reviewable.io

Review status: 0 of 8 files reviewed at latest revision, 7 unresolved discussions, some commit checks failed.

src/churn/candidate.ts, line 13 [r1] (raw file):
Done.

src/churn/candidate.ts, line 18 [r1] (raw file):
OK.  I renamed them to ip and port, following the latest ORTC nomenclature.

src/churn/candidate.ts, line 26 [r1] (raw file):
That would work, but I think it would require four additional mentions of sdpMid and sdpMLineIndex in churn.ts, so I think this is more convenient overall.

src/churn/candidate.ts, line 29 [r1] (raw file):
Sometimes.  Added a comment.

src/churn/candidate.ts, line 90 [r1] (raw file):
Done.

src/churn/churn.ts, line 218 [r1] (raw file):
Already done, see the if statement above.

src/churn/churn.ts, line 218 [r1] (raw file):
This would definitely work but it makes me a little uncomfortable.  I feel like the less we get in the way (and the more we preserve things like priority and generation), the more likely WebRTC is to work quickly and well.  We might find that we need sdpMid if we want to enable voice and video.
However, switching to a pure publicEndpoint-based solution would actually work fine with this code, (no compatibility problem).  That makes me inclined to consider that option later.

Comments from the review on Reviewable.io

Agh, sorry I didn't see this yesterday.
I'm getting closer to understanding this -- some suggestions, and we need to think a little about backwards compatibility, viz. publicEndpoint.

Review status: 0 of 8 files reviewed at latest revision, 12 unresolved discussions, some commit checks failed.

src/churn-pipe/churn-pipe.ts, line 98 [r2] (raw file):
What are the keys?

src/churn-pipe/churn-pipe.ts, line 107 [r2] (raw file):
I am currently not following the purpose of this field :-)

src/churn-pipe/churn-pipe.ts, line 124 [r2] (raw file):
I remember this point being a subtle could-but-probably-won't-trip-us-up-but-would-be-super-hard-to-debug thing.
Probably worth mentioning at the class level instead.

src/churn-pipe/churn-pipe.ts, line 161 [r2] (raw file):
Clearly, this function is clearly super confusingly named!
A TODO to rename it is fine for now.

src/churn/candidate.ts, line 23 [r1] (raw file):
Thanks.

src/churn/candidate.ts, line 28 [r1] (raw file):
OK. And relatedIp? :-)
Is this type only used by the pipe? I think it might get super annoying to remember which types use address and which use ip. But if this type is only used here, sure.

src/churn/candidate.ts, line 40 [r1] (raw file):
A method-level comment would be better, I think.

src/churn/churn.ts, line 66 [r2] (raw file):
Reads a lot better, easier to modify. Neat!

src/churn/churn.ts, line 218 [r1] (raw file):
Agree we should manipulate the lines as little as possible.
In that case, we have a backwards compatibility question. If you know the remote peer is running holographic ICE, there's no need to send publicEndpoint. I would suggest adding a constructor argument indicating this support; it will be straightforward to update the UI to set it.

src/churn/churn.ts, line 218 [r1] (raw file):
Oh, I see. Sorry.

src/churn/churn.ts, line 285 [r2] (raw file):
Is endpoint the source of a packet received? A comment would help.

src/churn/churn.ts, line 290 [r2] (raw file):
So this callback tells us the endpoint of a new "local socket"?
It's not clear why this is received so asynchronously from the calls to bindLocal.

Comments from the review on Reviewable.io

Review status: 0 of 8 files reviewed at latest revision, 9 unresolved discussions, some commit checks pending.

src/churn-pipe/churn-pipe.ts, line 98 [r2] (raw file):
Added a comment.grun

src/churn-pipe/churn-pipe.ts, line 107 [r2] (raw file):
Done.

src/churn-pipe/churn-pipe.ts, line 124 [r2] (raw file):
Done.

src/churn-pipe/churn-pipe.ts, line 161 [r2] (raw file):
Done.

src/churn/candidate.ts, line 28 [r1] (raw file):
Don't blame me.  Blame the working group: http://ortc.org/wp-content/uploads/2015/06/ortc.html#rtcicecandidate*.
Candidate is only used by churn.ts (not churn-pipe.ts).

src/churn/candidate.ts, line 40 [r1] (raw file):
Done.

src/churn/churn.ts, line 218 [r1] (raw file):
Done.

src/churn/churn.ts, line 285 [r2] (raw file):
Done.

src/churn/churn.ts, line 290 [r2] (raw file):
Tried to clarify with a comment.

Comments from the review on Reviewable.io

Awesome. I think we have some work to do to make the code more readable - imagine trying to understand churn now, looking just at this! - but :+1:. Great work.

Review status: 0 of 8 files reviewed at latest revision, 1 unresolved discussion, some commit checks failed.

src/churn/candidate.ts, line 28 [r1] (raw file):
Okay :-)

Comments from the review on Reviewable.io


Deleting wallets

https://track-expenses-app-frontend.netlify.app/wallets/my

To implement this feature one needs to start backend by pulling this repo https://github.com/bycza-zagroda/track-expenses-app-backend and running docker-compose up. Docker needs to be installed.
Deleting wallets

After clicking on Delete button for specific wallet we should open confirm modal with title Deleting [name_of_the_wallet] wallet and text Are you sure you want to delete [name_of_the_wallet] wallet and all related data? and also buttons Yes and No
After clicking on the button we should return to the component opening confirm modal boolean value (true when Yes was clicked and false when No was clicked)
In case of clicking Yes component that have opened confirmation modal should perform a request and delete the wallet
We should show snackbar informing user about successful deletion of the wallet https://material.angular.io/components/snack-bar/overview or failed deletion
We should remove deleted wallet from the wallets list
All new code should have code coverage

Tips

We should use Angular Material dialog component for the confirm modal https://material.angular.io/components/dialog/overview
We should create reusable ConfirmDialogService that we will be able to reuse in the whole app to open confirm dialogs -> It should be able to open confirm modal with preconfigured title, text and buttons (all of them except text should have default values)
We should also use tooltip with loading indicator to show that request is ongoing

Nad zadaniem pracuje DawidS (nick z discorda)


fix: allow decoding enums that overlap with bool types

Fixes https://github.com/dagger/dagger/pull/8673#issuecomment-2407223417
false and true values are always decoded by gqlparser as booleans - however, this might not always be the case: a standalone value might potentially be decodable as an enum instead.
The solution for this is to just add another case for decoding booleans in enums.

[!NOTE]
There's really no way to avoid this hack from what I can tell - you can put a false/true value as an enum value, but when you come to parse it, the parse tree you should construct is dependent on the types that you declare inside the parse tree :cry: Not actually sure if there exists a general class of parser that can correctly parse these :laughing:

Refactored this patch slightly, and now instead of trying to force all of the magical parsing logic everywhere to consider this, we can just handle it directly in dagql's ParseField and perform a clever conversion there.

One general comment: I guess I would have expected that enum values are all sent as strings and thus an enum value would be sent as "true" rather than true (i.e. string instead of json literal)

I would have expected this too - this is sadly not how graphql enums work though - they're unquoted.
However, we could switch our clients to sending string values? Dagql just does the right thing in these cases - but I think this might require some changes in all our querybuilders.


Point alarm control

Description:
Adds support for toggling the alarm part of the Minut Point.
Pull request in home-assistant.io with documentation (if applicable): home-assistant/home-assistant.io#8477
Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.

If user exposed functionality or configuration variables are added/changed:

[x] Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[x] New dependencies have been added to the REQUIREMENTS variable (example).
[x] New dependencies are only imported inside functions that use them (example).
[x] New or updated dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[x] New files were added to .coveragerc.

Wip:

[x] Community tests.
[x] Version bump github.com/fredrike/pypoint.
[x] (Supported features of alarm_control_panel), apparently doesn't the alarm_control_panel implement supported features like the climate platform does.

Will this reach 0.88?

No, 0.89.


Style taxonomy sidebar like related links

We will be iterating both components as part of a multivariate test. This commit avoids a more thorough refactor to make them identical, in favour of making them alike. It’s an alternative to #1177.

Port related links styles directly from related links component
Makes two components similar
Increases spacing around links for easier clicking on mobile
Adds more examples

This PR does not address:

Need to use pub-c as the prefix
Inconsistent API between related links and taxonomy sidebar
Style re-use between components

https://govuk-static-pr-1185.herokuapp.com/component-guide/taxonomy_sidebar
Part of:
https://trello.com/c/FN3ppmn2/60-update-taxonomy-related-links-in-right-column-to-match-the-design-used-by-mainstream-browse-related-links
Screenshots
Old on left, new on right

Thin viewport

@andysellick PR aims for consistency with related links rather than perfection in both. Better spacing is a side effect of related links being more spacious.
I have observed users interact with related links on mobile in user research without a problem, but the spacing might not be ideal for everyone.
We'll be doing design iterations on these elements in the next few sprints.


Error requesting sensor data

Version of the custom_component

1.0
Configuration
Add your logs here.

Describe the bug
I've installed the custom component and I was able to add it in the integration page. However, I'm not getting the sensors in my HA. I might be missing something, but I don't know what.
Debug log

Logger: custom_components.google_home
Source: helpers/update_coordinator.py:160
Integration: Google Home (documentation, issues)
First occurred: 10:53:42 (3 occurrences)
Last logged: 10:55:19

Error requesting sensor data: Cannot connect to host 192.168.xx.xx:8443 ssl:default [None]

What type of Google Assistant Enabled devices do you have?

2x GH mini and 1x GH Home

Are you using VLANs?
We are in the middle of adding a better way to debug this application. When that is done. We will have a better way to help you. Please standby, it should be done hopefully later today 😊

Yeah, I'm using VLANS but the devices are on the same as HA. I now see that the error is for the Shield TV. Nevertheless I'd expect to see some sensors. No hurry's!

Thanks for the feedback. I don't know if the Shield supports alarms and timers. So that's probably why it cannot connect. 😊

I also think that the Shield doesn't support timers, never thought of it.
But would this effect not creating the right sensors? I do see that component gets his data from the rest of GH's.
2021-03-22 11:55:20 DEBUG (MainThread) [custom_components.google_home] Finished fetching sensor data in 33.193 seconds

Just so i 100% sure i understand. There are no sensors for the rest of you Google devices, even though they are supported?
As there is many different devices out there, we don't use a whitelist approach. If it generates a token in the right format it is expected to support it (This obliviously does not).

Yes, there're no sensors indeed. Also I don't find a sensor with "token" in the name when I search for it.
Under integrations I don't see any entities or devices which I'd expect.

The readme have not been update i can see, its name should be sensor."device"_device instead. Can you please set google_home logger level to debug and past all the logs points relating to google_home here. This will make it easier to know why this is happening 😄

➜  ~ grep .google_home /config/home-assistant.log | tail -100
2021-03-22 16:09:35 WARNING (MainThread) [homeassistant.loader] You are using a custom integration google_home which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2021-03-22 16:09:40 INFO (MainThread) [homeassistant.bootstrap] Setting up stage 2: {'zeroconf', 'remote', 'cast', 'light', 'history', 'stream', 'ssdp', 'ffmpeg', 'homekit', 'spotify', 'hacs', 'input_boolean', 'media_player', 'edgeos', 'dhcp', 'media_source', 'default_config', 'sun', 'input_number', 'philips_js', 'weather', 'map', 'automation', 'ziggonext', 'anniversaries', 'conversation', 'tag', 'blueprint', 'harmony', 'alarm_control_panel', 'discovery', 'kodi', 'unifi', 'onvif', 'system_health', 'mqtt', 'wake_on_lan', 'sensor', 'climate', 'scene', 'camera', 'speedtestdotnet', 'input_text', 'counter', 'input_datetime', 'script', 'spotcast', 'esphome', 'zone', 'fan', 'group', 'persistent_notification', 'emulated_hue', 'my', 'hue', 'google_home', 'adaptive_lighting', 'proxmoxve', 'tts', 'zha', 'updater', 'logbook', 'panel_custom', 'ios', 'mobile_app', 'input_select', 'wled', 'tasmota', 'device_tracker', 'influxdb', 'timer', 'google_assistant', 'notify', 'google', 'switch', 'binary_sensor', 'ipp', 'adguard'}
2021-03-22 16:10:01 INFO (MainThread) [homeassistant.setup] Setting up google_home
2021-03-22 16:10:01 INFO (MainThread) [homeassistant.setup] Setup of domain google_home took 0.0 seconds
2021-03-22 16:10:04 INFO (MainThread) [custom_components.google_home]
2021-03-22 16:10:40 WARNING (MainThread) [homeassistant.bootstrap] Waiting on integrations to complete setup: google_home
2021-03-22 16:10:41 ERROR (MainThread) [custom_components.google_home] Timeout fetching sensor data
2021-03-22 16:10:41 WARNING (MainThread) [homeassistant.config_entries] Config entry<EMAIL_ADDRESS>for google_home integration not ready yet. Retrying in background
2021-03-22 16:11:24 ERROR (MainThread) [custom_components.google_home] Error requesting sensor data: Cannot connect to host <IP_ADDRESS>:8443 ssl:default [None]
2021-03-22 16:12:08 ERROR (MainThread) [custom_components.google_home] Timeout fetching sensor data
2021-03-22 16:13:01 ERROR (MainThread) [custom_components.google_home] Error requesting sensor data: Cannot connect to host <IP_ADDRESS>:8443 ssl:default [None]
2021-03-22 16:14:04 DEBUG (MainThread) [custom_components.google_home] Fetching data from Google Home device Slaapkamer - https://<IP_ADDRESS>:8443/setup/assistant/alarms
2021-03-22 16:14:04 DEBUG (MainThread) [custom_components.google_home] Fetching data from Google Home device Keuken 3 - https://<IP_ADDRESS>:8443/setup/assistant/alarms
2021-03-22 16:14:04 DEBUG (MainThread) [custom_components.google_home] Fetching data from Google Home device SHIELD - https://<IP_ADDRESS>:8443/setup/assistant/alarms
2021-03-22 16:14:04 DEBUG (MainThread) [custom_components.google_home] Fetching data from Google Home device Woonkamer - https://<IP_ADDRESS>:8443/setup/assistant/alarms
2021-03-22 16:14:15 ERROR (MainThread) [custom_components.google_home] Error requesting sensor data: Cannot connect to host <IP_ADDRESS>:8443 ssl:default [None]
2021-03-22 16:14:15 DEBUG (MainThread) [custom_components.google_home] Finished fetching sensor data in 33.176 seconds

Can you please try to turn of the Shield and try adding it again to see if that solves the problem? So is obviously not the best solution, but it should solve it for now. 😄

Hmmmm... well basically what i think happens here is that sensor initialization fails on your Shield TV device. The log error line: Error requesting sensor data:... is HomeAssistant fallback handler meaning that it bypasses the logic of this integration. That also means that integration discovers all devices successfully but when fetching data from them fails to fetch data for Shield TV. That in it's turn simply bypasses any other sensor creation. We need to add better error handling there not to break the logic of initialization of other sensors. :)

That sounds right to me; is there any benefit in adding sensors for devices like Chromecasts and soundbars (in my case), since they don't support timers and alarms, I personally see no use for the token-sensor for those devices in my environment at all, but I might be missing something.

See my PR and #102

@LEJOUI  Will you bewilling to try to install this dev branch? here. It should fix your issue, we just need to confirm that it is working. 😄

So I powered off the Shield and by a restart it added the sensors.
Restart HA with the shield made the sensors unavailable as expected.
Copied the dev branche into the custom component and they went availble again.
Fun fact the shield is now also apperearing :)

NICE! Glad to here that it works again.
Thanks for testing it 😄

Please remove and reinstall from `master``. 😄


MXNet Parser has not supported operator Crop with name crop0

Platform (like ubuntu 16.04/win10): 18.04
Python version: 3.6
Source framework with version (like Tensorflow 1.4.1 with GPU):
MXNET
Destination framework with version (like CNTK 2.3 with GPU):
Tensorflow
Pre-trained model path (webpath or webdisk path): mnet.25
https://drive.google.com/drive/folders/1OTXuAUdkLVaf78iz63D1uqGLZi4LbPeL
Running scripts:
mmconvert -sf mxnet -in ~/.insightface/models/retinaface_mnet025_v1/mnet10-symbol.json -iw ~/.insightface/models/retinaface_mnet025_v1/mnet10-0000.params -df tensorflow -om tf_retinaface_mnet_v1 --inputShape 3,480,640 --dump_tag SERVING
The error with MMDNN lastest release
Warning: convert the null operator with name [data] into input layer.
Warning: MXNet Parser has not supported operator Crop with name crop0.
Traceback (most recent call last):
  File "/home/dmp/Silent-Face-Anti-Spoofing/luandd/bin/mmconvert", line 8, in <module>
    sys.exit(_main())
  File "/home/dmp/Silent-Face-Anti-Spoofing/luandd/lib/python3.6/site-packages/mmdnn/conversion/_script/convert.py", line 102, in _main
    ret = convertToIR._convert(ir_args)
  File "/home/dmp/Silent-Face-Anti-Spoofing/luandd/lib/python3.6/site-packages/mmdnn/conversion/_script/convertToIR.py", line 120, in _convert
    parser.run(args.dstPath)
  File "/home/dmp/Silent-Face-Anti-Spoofing/luandd/lib/python3.6/site-packages/mmdnn/conversion/common/DataStructure/parser.py", line 22, in run
    self.gen_IR()
  File "/home/dmp/Silent-Face-Anti-Spoofing/luandd/lib/python3.6/site-packages/mmdnn/conversion/mxnet/mxnet_parser.py", line 263, in gen_IR
    self.rename_UNKNOWN(current_node)
  File "/home/dmp/Silent-Face-Anti-Spoofing/luandd/lib/python3.6/site-packages/mmdnn/conversion/mxnet/mxnet_parser.py", line 374, in rename_UNKNOWN
    raise NotImplementedError()
NotImplementedError

Thank you for your issues. We are sorry that we didn't add this op for mmdnn, we will fix it soon.

Hi @cookieli
I have same problem, thanks for your checking.


X-Pack/SQL does not seem to be available on the Elasticsearch node

Description
正常连接后，打开表时报错：
SQL 错误 [bad_server]: X-Pack/SQL does not seem to be available on the Elasticsearch node using the access path ':'. Please verify X-Pack is installed and SQL enabled. Alternatively, check if any proxy is interfering the communication to Elasticsearch
X-Pack/SQL does not seem to be available on the Elasticsearch node using the access path ':'. Please verify X-Pack is installed and SQL enabled. Alternatively, check if any proxy is interfering the communication to Elasticsearch
X-Pack/SQL does not seem to be available on the Elasticsearch node using the access path ':'. Please verify X-Pack is installed and SQL enabled. Alternatively, check if any proxy is interfering the communication to Elasticsearch
UPD: Edited host and port in the description to hide them_
DBeaver Version
21.3.2，23.0.4
Operating System
windows10 64
Database and driver
1、elasticsearch 7.10.2
2、x-pack-sql-jdbc:7.10.2

Thank you for bug report.
Could you provide minimal example to reproduce your issue?

Thank you for bug report.
Could you provide minimal example to reproduce your issue?

Could you please provide the log files? You can find instructions here: https://dbeaver.com/docs/wiki/Log-files/. Thank you.

It seems like the issues has nothing to do with DBeaver. The issue is connected with your server configuration.


Implement light traps into foodbase

The foodbase package needs to be updated to accommodate light trap and sticky trap data, which are now standardized and QA/QC'd in the database and just need to be implemented with R code.

Finished this in April 2021.


LoadImage - TypeError: Object of type Image is not JSON serializable

How to use LoadImage? I'm getting this error
TypeError: Object of type Image is not JSON serializable

specifically, I'm trying to add this to my workflow (some hardcoded values for now):
def cnet_zoedepth(ctx, img):
    control_net = ControlNetLoaderAdvanced(ControlNetLoaderAdvanced.control_net_name.diffusers_xl_depth_mid, None)
    img = ImageResize(img, 'rescale', 'true', 'lanczos', 1, ctx.width, ctx.height)
    preprocessed_img = ZoeDepthAnythingPreprocessor(img, 'indoor', ctx.width)
    ctx.pos, ctx.neg, ctx.model = ACNAdvancedControlNetApply(ctx.pos, ctx.neg, control_net, preprocessed_img, strength=0.4, start_percent=0, end_percent=0.4)

img, _ = LoadImage("D:\sd\input\clipspace\clipspace-rgba-534537233.png")
cnet_zoedepth(ctx, img)

It works on my side. Maybe the error isn't caused by these code?

hmmm, I think this was user error. I separated out some functions into a separate block in the notebook. Probably just forgot to rerun that.


Simple typo issue

Running kubefwd 1.4.3
When I shutdown kubefwd by hitting Ctrl+C, I get output like this...
^CStoped forwarding <IP_ADDRESS>:7002 and removing spin-clouddriver-rw from hosts.
Stoped forwarding <IP_ADDRESS>:6383 and removing play-others-redis from hosts.
Stoped forwarding <IP_ADDRESS>:7002 and removing spin-clouddriver-ro from hosts.
...

Stoped should be spelled Stopped.
Opened a PR #18 for this

Closed with PR #18


Feature: Consolidate Travis Jobs

Jira
N/A
Summary
Consolidates Travis CI jobs to reduce overall build times for feature branches by around 50% — shaving off nearly 15 minutes per commit, per feature branch.
Details

Updates version of PHP running on Travis to 7.3
Consolidates our existing Travis CI jobs to run as many tests as possible in as few jobs as possible, as quickly as possible 😁
Limits the default browsers tested by Nightwatch on feature branches to just Chrome and IE 11 to speed things up. Firefox still gets tested when Nightwatch tests are run on master, release, bug / hotfix, and tagged releases.
Also reduces the frequency we run sanity checks on Drupal Lab / the last previous Bolt release’s Build Tools

Based on description and code review, approved 👍
I noticed cache is now always true instead of !travis or !prod. Not necessary to turn off cache for these environments anymore?

Thanks @danielamorse! Like we chatted about, I’m pretty optimistic with this docs-site specific config update after testing this out quite a bit.
We can always switch back if need be!

PR was released with v2.8.4-canary.bde01a443.0

PR was released with v2.9.0


quantum-espresso: 6.6 -> 7.2

Description of changes
Quantum-espresso update, skipping many versions in between: https://www.quantum-espresso.org/release-notes/release-notes-QE7-2.html
Also adds wannier90 and libmbd as dependencies of the new quantum-espresso versions. Some other dependencies are built via Git submodules by quantum-espresso's cmake on the fly.
I wasn't able to add the GPU support as it requires the NVidia Fortran compiler from the Cuda HPC SDK, which is not yet in nixpkgs.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Priorities
Add a :+1: reaction to pull requests you find important.

Fixed the Quantum-Espresso hash and restricted Wannier90 to x86-64-linux.


Fix focus and selection issues

See individual commits.
Also bump the version, so that we can depend on it from cockpit.

Let's make this also a PR on https://github.com/chjj/term.js and add it to the list of PRs in the README.

Let's make this also a PR on https://github.com/chjj/term.js and add it to the list of PRs in the README.

That project is no longer maintained. The author says so in the project's current README and suggests using xterm.js instead. I looked into that a while ago and found that it isn't CSP ready and requires quite modern browsers. They don't seem to accept patches for that, as they've rewritten it to use canvas. I felt that jumping on such a young code base was not a good fit—especially as they haven't released that version yet—and decided to do the couple of fixes we need in our fork of term.js.
Sorry, which list of PRs do you mean?

Sorry, which list of PRs do you mean?

The one in our README, that we use to justify the fork.

That project is no longer maintained.

Ahh, I see.


Remove space below header in 'About' tab

Has anyone been able to shorten the space between the 'about' (main) tab and the header?
All other tabs have way less space below the header and the page title.
Thanks!

Which browser did you see this in? I'm not sure I'm seeing the extra space you are referring in the stock template.

Since there has been no follow-up and I can't seem to find the source of the problem, closing as unreproducible.


Script ideas.

Hi, this is mosty a thanks for the new recorder script. :)
possibly add being able to disable ffmpeg conversion, never had a problem playing the recorded stream and if the stream dies i want to start recording again as quickly as possible not wait until ffmpeg finishes. misnamed ffmpeg for now.
thanks again.

Hey, noted. Maybe at the end of the week when I'm not busy, but I can't promise anything ;)
Have a good day

many thanks.


Fix copy_partitions when used with static partitions

resolves #1349
docs dbt-labs/docs.getdbt.com/#

Problem

Solution

The copy_partitions was originally designed for dynamic partitions but it can be adapted for static partitions which is done in that PR.
Checklist

[x] I have read the contributing guide and understand what's expected of me
[x] I have run this code in development and it appears to resolve the stated issue
[x] This PR includes tests, or tests are not required/relevant for this PR
[x] This PR has no interface changes (e.g. macros, cli, logs, json artifacts, config files, adapter interface, etc) or this PR has already received feedback and approval from Product or DX

+1 for this pull request


migrate to the new Android APIs based on FlutterPlugin

Thank you.

@lykhonis would you please publish the new version to pub.dartlang.org ?

@lykhonis would you please publish the new version to pub.dartlang.org ?

Done.


NotImplementedError in examples/generative/vae.py

Dear all,
when running the script examples/generative/vae.py without any changes, I get this error message
   raise NotImplementedError('When subclassing theModelclass, you should' NotImplementedError: When subclassing theModelclass, you should implement acallmethod.
I have python3.6.9 and tensorflow-gpu 1.12.0, but I think this might be a general problem with this script.
Thanks a lot for your answers.
Best,
Wilhelm

You need TF 2.2 or higher

Thanks, the error has disappeared after installing the latest stable TF version as described here.

Also getting this error running in TF 2.3


Patch 1

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

dynamicsax2012-msdn/variable-names.md
:white_check_mark:Succeeded
View

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


Identifier Service

[ ] What id service do we use for identifiers

SURI on lyberservices subset of calls
~SURI Rails rewrite / cbeer~
ID Proxy stuff (that calls SURI; rewriting might be required)
Fake out entirely within TACO codebase

[ ] Based on the above, get one implemented & connections available to TACO
[ ] Larger topic (to be broken out): implement DRUID-based identifier schema in TACO

tech team walks through identifier schema
identifier for system different from DRUID identifiers (versioning plays into this too)?

https://github.com/sul-dlss/suri_rails

blocked by #189

Stretch goal to write this in go to replace SURI and avoid a proxy api

https://github.com/sul-dlss-labs/id-proxy-api/blob/setup/api/identifier_api_swagger.json


[tool_crash] ArgumentError: Invalid argument(s): Cannot find executable for E:\DevEnvironment\flutter\bin\cache\artifacts\engine\android-arm-release\windows-x64\gen_snapshot.

Command
flutter --quiet assemble --depfile E:\work\zhengfeng\flutter_library\.android\Flutter\build\intermediates\flutter\release/flutter_build.d --output E:\work\zhengfeng\flutter_library\.android\Flutter\build\intermediates\flutter\release -dTargetFile=lib/main.dart -dTargetPlatform=android -dBuildMode=release -dTrackWidgetCreation=true android_aot_bundle_release_android-arm android_aot_bundle_release_android-arm64 android_aot_bundle_release_android-x64

Steps to Reproduce

...
...
...

Logs
ArgumentError: Invalid argument(s): Cannot find executable for E:\DevEnvironment\flutter\bin\cache\artifacts\engine\android-arm-release\windows-x64\gen_snapshot.
#0      _getExecutable (package:process/src/interface/local_process_manager.dart:124:5)
#1      LocalProcessManager.start (package:process/src/interface/local_process_manager.dart:40:30)
#2      ErrorHandlingProcessManager.start.<anonymous closure> (package:flutter_tools/src/base/error_handling_io.dart:638:33)
#3      _run (package:flutter_tools/src/base/error_handling_io.dart:532:20)
#4      ErrorHandlingProcessManager.start (package:flutter_tools/src/base/error_handling_io.dart:638:12)
#5      _DefaultProcessUtils.start (package:flutter_tools/src/base/process.dart:472:28)
#6      _DefaultProcessUtils.stream (package:flutter_tools/src/base/process.dart:491:35)
#7      GenSnapshot.run (package:flutter_tools/src/base/build.dart:73:26)
#8      AOTSnapshotter.build (package:flutter_tools/src/base/build.dart:194:56)
#9      AndroidAot.build (package:flutter_tools/src/build_system/targets/android.dart:232:52)
#10     _BuildInstance._invokeInternal (package:flutter_tools/src/build_system/build_system.dart:796:27)
<asynchronous suspension>
#11     Future.wait.<anonymous closure> (dart:async/future.dart)
<asynchronous suspension>
#12     _BuildInstance.invokeTarget (package:flutter_tools/src/build_system/build_system.dart:734:32)
<asynchronous suspension>
#13     Future.wait.<anonymous closure> (dart:async/future.dart)
<asynchronous suspension>
#14     _BuildInstance.invokeTarget (package:flutter_tools/src/build_system/build_system.dart:734:32)
<asynchronous suspension>
#15     FlutterBuildSystem.build (package:flutter_tools/src/build_system/build_system.dart:563:16)
<asynchronous suspension>
#16     AssembleCommand.runCommand (package:flutter_tools/src/commands/assemble.dart:220:32)
<asynchronous suspension>
#17     FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:1157:12)

[✓] Flutter (Channel stable, 2.0.1, on Microsoft Windows [Version 10.0.19043.844], locale zh-CN)
    • Flutter version 2.0.1 at E:\DevEnvironment\flutter
    • Framework revision c5a4b4029c (15 hours ago), 2021-03-04 09:47:48 -0800
    • Engine revision 40441def69
    • Dart version 2.12.0
    • Pub download mirror https://pub.flutter-io.cn
    • Flutter download mirror https://storage.flutter-io.cn

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at E:\DevEnvironment\AndroidSDK
    • Platform android-30, build-tools 30.0.3
    • ANDROID_HOME = E:\DevEnvironment\AndroidSDK
    • Java binary at: E:\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
    • All Android licenses accepted.

[✗] Chrome - develop for the web (Cannot find Chrome executable at .\Google\Chrome\Application\chrome.exe)
    ! Cannot find Chrome. Try setting CHROME_EXECUTABLE to a Chrome executable.

[✓] Android Studio (version 4.1.0)
    • Android Studio at E:\Android Studio
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)

[✓] IntelliJ IDEA Community Edition (version 2020.3)
    • IntelliJ at D:\IntelliJ IDEA
    • Flutter plugin version 52.1.5
    • Dart plugin version 203.6912

[✓] Connected device (2 available)
    • SM N9760 (mobile) • R3CM80CKCZY • android-arm64  • Android 11 (API 30)
    • Edge (web)        • edge        • web-javascript • Microsoft Edge 88.0.705.74

! Doctor found issues in 1 category.

Flutter Application Metadata
Type: module
Version: 1.0.0+1
Material: true
Android X: true
Module: true
Plugin: false
Android package: com.zendaccess.flutter_library
iOS bundle identifier: com.zendaccess.flutterLibrary
Creation channel: stable
Creation framework version:<PHONE_NUMBER>7c3a836feee883712c241a5fd22983
Plugins
flutter_custom_dialog-1.0.20
path_provider_linux-0.0.1+2
path_provider_windows-0.0.5
shared_preferences-0.5.12+4
shared_preferences_linux-0.0.2+4
shared_preferences_macos-0.0.1+11
shared_preferences_web-0.1.2+7
shared_preferences_windows-0.0.2+3

Duplicate of https://github.com/flutter/flutter/issues/68475.


Inconsistent output between 'twa' and 'twa --help'

Reproducing
$ twa
Usage: twa [-w] <domain>

$ twa --help
Usage: twa [-csvw] <domain>

What I expect
Both outputs are the same
What actually happened
twa doesn't show all possible flags

Thanks for the report! I'll fix this in a moment.


ApplicationBus.md enhancement

Translated to english with some minor markdown changes.

I think, the translation is OK.


Introduce ${dotEnv:VAR_NAME}  to .devcontainer.json

Could you introduce something like ${dotEnv:VAR_NAME}  to variable substation .devcontainer.json?
That would allow us to keep project/developer-specific information in one or more .env file like image-name or other settings (like mounts points on developer host systems like for private keys) that are also used in other files.
I would suggest adding "dotEnvFiles" : [".env-defaults", ".env"]  so we can have defaults. The later file overwrites the vars from the preceding one.
Additonally

dotEnvStopOnMissing: bool could throw an error if one file is missing, otherwise just skip.
dotEnvStopOnError: bool could throw an error of parsing failed or dotEnvStopOnMissing == true.

dotEnvFiles would be read before actually any other keys in devcontainer.json so they can be used in value expressions. No preprocessing of value strings. Meaning I would not allow putting ${localEnv:HOME} in .env files to keep things simple.
https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_variables-in-devcontainerjson

Ok, I see a meta.env and copyLibraryScriptsForAllDefinitions in https://github.com/microsoft/vscode-dev-containers/blob/bd53a6615fa12ccb8fade3426b9c0ff0fbfce317/build/src/prep.js . Currently looking at it and how it is used.
Using other extensions like https://github.com/direnv/direnv-vscode is not seen as option since like for that enforcing dotenvto be installed on host system is nothing we want to do. Also we want to use well maintained extensions.

Only workaround imaginable would be to run initializeCommand and use a a local hard-coded image name for the container image. Still the problem isn't solved and would open some other glitches.

Hi @markus-geiger, thanks for opening.
We are making dev containers an open specification (info), and I think this type of request would be fitting for the spec repo: https://github.com/devcontainers/spec/issues. Please let me know if this makes sense to you as well, and if so, we can close out this issue if you open one over there. Thanks!


test

https://user-images.githubusercontent.com/59060246/126339422-b9369a88-4b9d-4c3d-a62a-af2912ef5510.mp4

I'll remove this stuff after sometime


emacs: epkgs.treesit-grammars can't find native libraries anymore

Describe the bug
After a recent nixpkgs update my emacs can't find native tree-sitter libraries anymore: Warning (treesit): Cannot activate tree-sitter, because language grammar for rust is unavailable (not-found): (libtree-sitter-rust libtree-sitter-rust.0 libtree-sitter-rust.0.0 libtree-sitter-rust.so libtree-sitter-rust.so.0 libtree-sitter-rust.so.0.0) No such file or directory.
I still have epkgs.treesit-grammars.with-all-grammars in emacs deps and emacs-packages-deps has those libs in /nix/store/m8v80bwvl8hs4pq1ayxfg6wrdfc3yjms-emacs-packages-deps/lib/ like it was before. But for some reason emacs doesn't look there anymore. It works if I add this path to LD_LIBRARY_PATH.
Steps To Reproduce
Steps to reproduce the behavior:
Install emacs with epkgs.treesit-grammars.with-all-grammars (here is how I do it)
Notify maintainers
@AndersonTorres @adisbladis @jwiegley @lovek323 @matthewbauer
Metadata
 - system: `"x86_64-linux"`
 - host os: `Linux 6.7.6, NixOS, 24.05 (Uakari), 24.05.20240228.9099616`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.1`
 - channels(root): `"nixos-21.11"`
 - nixpkgs: `/nix/store/cbbsvzjcqvzlylq9s7p6d2gyxh64q88p-source`

Add a :+1: reaction to issues you find important.

I am having this same issue, I even added the following to home-manager
programs.emacs = {
      enable = true;
      package = pkgs.emacs29-pgtk;
      extraPackages = epkgs: with epkgs; [ tsc tree-sitter-langs tree-sitter ];
 };

Hey @kurnevsky  I was actually able to stop this from happening by taking these steps

I added those extraPackages as you saw above.
I deleted the emacs/.local directory that doom emacs had been using(previously setup via emacs within distrobox).
I rebuilt doom emacs with doom sync
I am not sure if you are using doom emacs but hopefully this helps.

I'm not using doom emacs - it's plain emacs with config built with nix.

Before the update emacs successfully found this lib:
openat(AT_FDCWD, "/nix/store/ggxdmj3c02bx6b3pnv9ngcl1xg52k2dm-emacs-packages-deps/lib/libtree-sitter-rust.so", O_RDONLY|O_CLOEXEC) = 12

But it was looking for it only after rust-ts-mode was activated. Now it looks at startup, hm...

ok, found out that now treesit is loaded after early-init but before init, and in early-init the variable treesit-extra-load-path is still nil, that's why the lib is not found. Now need to understand why it started to load so early :)


How to subscribe to several substates?

store.subscribe(self) {
    $0.select { ($0.monogenicListState, $0.monogenicListSearchState) }
}

Type of expression is ambiguous without more context

And
func newState(state: (MonogenicListState, MonogenicListSearchState)) {
    ...
}

Does the error change to something more specific when you add the closure paramter types?

no, these 2 fragments are both there

meh, I've been having these problems because I've inherited from another store subscriber class and obviously the compiler couldn't quite understand, what do I want.


[Fix #3629] Add TargetRailsVersion functionality

As described in https://github.com/bbatsov/rubocop/issues/3629 , this
adds the option to add a TargetRailsVersion to the rubocop.yml under
AllCops. Thus, Rails-5-specific cops do not have to be manually
disengaged.
The main problem this solves is when adding RuboCop to an older Rails 4
project, running the autocorrect will actually break the specs without
much indication why.
There is a fair bit more duplication (specifically of specs) than I'd
usually like, but I figured it is better to refactor once this PR gets a
+1 from maintainers.

Before submitting the PR make sure the following are checked:

[x] Wrote good commit messages.
[x] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Used the same coding conventions as the rest of the project.
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[ ] Added an entry to the Changelog if the new code introduces user-observable changes. See changelog entry format.
[x] All tests are passing.
[x] The new code doesn't generate RuboCop offenses.
[x] The PR relates to only one subject with a clear title
and description in grammatically correct, complete sentences.
[x] Updated cop documentation with rake generate_cops_documentation (required only when you've added a new cop or changed the configuration/documentation of an existing cop).

The cop looks good to me. I think some cops are Rails 4 only, so this might also be denoted in them, although probably few people are running Rails 3 in production these days.

Requested changes made. I'm happy to squash it all down to one commit when we are all 👍 .

I think some cops are Rails 4 only, so this might also be denoted in them, although probably few people are running Rails 3 in production these days.

I'm not totally sure which cops this would apply to. The only one I came across what the http verb cop. Are there any others I should look at updating?

I'm not totally sure which cops this would apply to. The only one I came across what the http verb cop. Are there any others I should look at updating?

This is certainly Rails 4+ https://rubocop.readthedocs.io/en/latest/cops_rails/#railsactionfilter
Not sure about the rest. Guess someone should consult the Rails 4 changelog as it happened a while ago and I don't remember what else was added then.

Squash the related commits together and we're good go to.

I opted to skip the cop if using Rails < 4.0. All commits fixed up and rebased master

👍


Refactored code to address code smells and improve readability

This commit focuses on refactoring the code to address identified code smells and enhance the overall readability of the codebase. The following specific changes have been made:

In the ExecutationSetupView class:
Fixed indentation and removed unnecessary empty lines.
Renamed the class to correct a the typo.

In the NewBufferView class:
Reorganized imports for better organization.
Improved variable naming to enhance code clarity.

In the PowerLineView class:
Added null safety checks to ensure robustness.
Extracted a separate method for setting the file name, improving code modularity.

Additionally, a few changes were applied to Main.kt and MainView.kt to align with the overall refactoring effort.
These modifications significantly contribute to the maintainability and comprehensibility of the codebase, facilitating future development and maintenance tasks.

Thank you for your work


slow

ts-to-jsdoc is painfully slow
running the 2 small tests from #6 takes 40 seconds on my quad-core laptop
im aware that this is a limitation of the upstream ts-morph which uses typescript under the hood
maybe we can disable type checking?
maybe we can use swc?

Hm, a ts-to-jsdoc with ts-morph ripped out wouldn't really be ts-to-jsdoc.. I want to avoid scope creep for what's truthfully a quick-and-dirty script I open-sourced. If you want to try implementing that, go for it; I'd be happy to include a link in the README pointing to it as a faster option, but I don't think it's something I want to include in this project.

yeah, demand is like zero.
most people will just use deno (based on swc) to run typescript


[staging] Build failure: coreutils

Steps To Reproduce
Steps to reproduce the behavior:

Switch to the staging branch (31311bf6910f0c55437924277659a845c9667a1d at the moment)
nix-build -A coreutils

Build log
https://gist.github.com/Jayman2000/73ce990a6da460a9ba6b057ce6198d2d
Additional context
This bug is blocking me from reporting another bug. At the moment, I think that there’s a bug with the update script for staging’s version of the git package. I can’t try to reproduce that bug at the moment because coreutils fails to build.
Notify maintainers

@dasJ
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.9.1, NixOS, 23.11 (Tapir), 23.11.7224.a8695cbd09a7`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.1`
 - channels(root): `"nixos-23.11"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

$

Add a :+1: reaction to issues you find important.

Is coreutils failing in checkPhase?

Coreutils have been failing for me on staging after the 9.5 upgrade(#299945), not sure why because master is on 9.5 too. Please do share logs and @dasJ might wanna take a look here.

I see in the logs:
FAIL: tests/shred/shred-exact.sh
Are you testing on some exotic filesystem? See #306760.

Not sure about Jayman2000, but I am on bcachefs, yes.

Duplicate of #306760, see https://github.com/NixOS/nixpkgs/issues/306760#issuecomment-2080317009


allow system contract to modify rate limiting inputs

related to #2777
Description
The system contract should be able to set more parameters that tweak the resource rate limiting math.
A non-exhaustive list of these parameters:

[ ] the cpu_usage window size used to track accounts
[ ] the net_usage window size used to track accounts
[ ] the cpu_usage window size used to track block congestion
[ ] the rates of expansion and decay for the virtual block limits for cpu_usage
[ ] the net_usage window size used to track block congestion
[ ] the rates of expansion and decay for the virtual block limits for net_usage

Care should be taken to ensure that setting these values does not create numeric limit issues.
A non-exhaustive list of potential issues (that should be checked as part of ATC)

[ ] new cpu/net windows for accounts allows for an account to consume the block maximum cpu/net usage for the entire window without overflowing our higher precision tracking values *_ex
[ ] the rates of expansion and decay do not cause overflow in the processing of elastic virtual limits

@wanderingbort Is this still a desired change?  If I don't get a response I will presume that it is not.

No longer a desired change.


cannot close body fd auto while upload file

The example below, have a bug that cannot close body fd and also cannot close upload.file
@route('/upload', method='POST')
def do_upload():
    category   = request.forms.get('category')
    upload     = request.files.get('upload')
    name, ext = os.path.splitext(upload.filename)
    if ext not in ('.png','.jpg','.jpeg'):
        return 'File extension not allowed.'

    save_path = get_save_path_for_category(category)
    upload.save(save_path) # appends upload.filename automatically
    return 'OK'

suggest to change to the following code, or add self.body.close() in POST function and add self.file.close() in save function
@route('/upload', method='POST')
def do_upload():
    category   = request.forms.get('category')
    upload     = request.files.get('upload')
    request.body.close()
    name, ext = os.path.splitext(upload.filename)
    if ext not in ('.png','.jpg','.jpeg'):
        return 'File extension not allowed.'

    save_path = get_save_path_for_category(category)
    upload.save(save_path) # appends upload.filename automatically
    upload.file.close()
    return 'OK'

You can use a with bottle.request.body: block to prevent the resource warning and properly close the request body.
Automatically closing the body after each request would break backwards compatibility because it is currently allowed to move body processing to a separate thread or access the body after the request was already closed.

so,follow your  suggestion, I suggest to edit the example code for File Uploads in https://bottlepy.org/docs/dev/tutorial.html, This sample code does not close the file handle properly

We have a fix now in master branch that avoids the ResourceWarning. Still not perfect, but It'll do for now.


Import left hand drive custom map

CARLA version: 0.9.12
Platform/OS: Ubuntu 18.04
Problem you have experienced: I am trying to import a custom map from RoadRunner R2021b with left-hand driving direction. The map is exported to OpenDrive 1.4 with Driving Side "Left". However, after import the map to Carla, it's shown that the routes are still perceived as right hand driving. Any suggestion on how to make Carla work with left hand driving? Thanks!
Map in RoadRunner (OpenDrive view):

Map in Carla:

Export settings:

With reference to issue #2442, I managed to get the route planners generated at expected positions. The direction of spawn points, however, still follows right-hand drive manners.
Even after rotating every spawn point for 180 degrees, the vehicles spawned with generate_traffic.py will try to make U-turn and disappear after a short while.

@

With reference to issue #2442, I managed to get the route planners generated at expected positions. The direction of spawn points, however, still follows right-hand drive manners. Even after rotating every spawn point for 180 degrees, the vehicles spawned with generate_traffic.py will try to make U-turn and disappear after a short while.

hello, have you ever resolved this issue? I am using CARLA 0.9.15, I am looking forward to your reply.


Add a separate page for signup (/sign/up)

It should contain the form that is right now on the landing page and should be located at /sign/up.
It can be similar to sign in page that we have right now at /sign/in.
Extracted from #25, for more context you can see this comment.
Feedback and suggestions are welcome.

A bit more additional info:

when creating this page, we should change link Create account on page /sign/in to point to new page (Just to not forget to change it later when landing will be redesigned :) )
form error handling and redirect after success should be the same as for current sign up form (I think it can be just copied)
style for desktop and mobile view can be taken from sign/in page
page should have same links to terms and privacy policy as form on the index page right now (I think it can be just copied)

Deployed to https://devv.jobs.


gulp-uglify-es to support ES6 support question.

Isn't it dangerous to use ES6 without a transpiler (browser support), wouldn't it better just to use babel then uglify instead? Maybe am not getting something, curious. Thanks

You are right, using babel would better and more robust in name of browser support. I'm happy to merge PR ;)

Finally solved in 6.0.4 where we had utter and complete js build process rewrite so closing this issue.