termui.Handle(“/timer/1s”, func(e termui.Event)) not working on ubuntu 18.04

I used the function which is correctly working with windows(windows 7 & 8) but it is not working on Ubuntu 18.04

err := termui.Init()
if err != nil {
panic(err)
}
defer termui.Close()
lsss := time.Now().Format(time.RFC1123)
strs := []string{
	"",
	"",
	"",
	"  ",
	"",
	"",
	"",
	" ",
	"",
	"",
	" Current Time is : " + lsss,
	"",
}

ls := termui.NewList()
ls.Items = strs
ls.ItemFgColor = termui.ColorYellow

// ls.BorderLabel = borderLabel

ls.Height = 15
ls.Width = 80
ls.Border = false
ls.Y = 10
termui.Render(ls)

termui.Handle("/timer/1s/", func(e termui.Event) {

	strs = []string{
		"",
		"",
		"",
		" ",
		"",
		"",
		"",
		"",
		" Current Time is : " + time.Now().Format(time.RFC1123),
		"",
	}
	ls.Items = strs

	termui.Render(ls)

})

termui.Handle("q", func(termui.Event) {
	termui.StopLoop()

})

termui.Loop()

this is freezing the time but in windows it continuously showing current time.

I thought that I was doing something wrong, it does not work for me either
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS"
NAME="Ubuntu"
VERSION="18.04.1 LTS (Bionic Beaver)"

Is there any other way to update a widget?

@bgadrian I was also thought that I was doing something wrong too. Finally put this into issue so I can be get little help by authors.

My apologies for not updating the documentation, the termui timers were removed on the master branch in favor of Go's built in timers. Most of the event logic in termui has actually been reworked on master. I'll make sure to update the documentation this week with the updates. The v2.3.0 release should still have all the functionality as documented however.
To switch to Go's built in timers, I would recommend either @bgadrian's example, the example from go by example, or using a select statement to choose between timer events and termui events.

@cjbassi thanks for your reply. Keyboard events (combination keys as 'C-c' ) is not working but working in windows. Does this also removed?

The key identifiers were also changed on master, so you would have to do <C-c> now. The available keycodes are listed here. Let me know if you still get issues with it.

Thank you so much for help...Please update document as early as possible..Thanks for awesome library..🙂

@cjbassi  I used key identifier() as you've mentioned in comment. It's working properly with keys but not clearing the console first time run

And while second time it's clear whole console screen.
I tested on windows 7 but not on Ubuntu...Once I'm done I'll let you know.

Hii @cjbassi,
I have tested same with ubuntu but it's exactly opposite of windows behaviour. On second run it will freezing window and nothing happend with keys. But first time it works totally fine in my case.

Hi, I just updated the documentation. You can check godoc for code documentation and also the wiki for general info. I also reworked the events (again) so there's some breaking changes there. Let me know if anyone has any suggestions about anything, especially the documentation.

@imwaddy Let me know if you're still having issues with the latest version.

@cjbassi I have updated the package and now it's working fine in both cases....I've not seen documentation yet but soon I'll inform you. Thanks! slightly_smiling_face


Feature: Add a "quick add" option in the left navbar

Describe the solution you'd like
Add an option allowing to quickly add a new device/model directly from the navbar, without having to load all the devices' list.
Additional context

@Metal-Mighty and @adcoly , could you help us to specify the menu re-organization needed ?

Please see #402  for the expected refactoring

@Metal-Mighty and @adcoly , could you help us to specify the menu re-organization needed ?

Done (and much more !) in #398


Support ticket fixes

Erases ticket message after it has been submitted
Adds section to backups settings and support create page, closes #1991

Allows backups settings to render if no window / day has been set

Makes padding of cards and modals equal w.r.t. left / right
Adds employee tag to ticket response header
Displays the Open ticket section if there are closed tickets even if there are no Open tickets.

Makes the create support ticket summary input wider, closes #1395

Coverage decreased (-0.04%) to 79.542% when pulling 1da51d1d4cc5b3367797766a2d23a9ae14ee82f8 on eatonphil:support-ticket-fixes into 8c6c6c6a78d332c9fbb9afabb1ac672c5a4315c5 on linode:master.

Coverage increased (+0.02%) to 79.542% when pulling 6beebeb143b0cea0ba235ab56aa4d2e4a12eadf2 on eatonphil:support-ticket-fixes into 088dc8083ccd7d95fe86c01a40f87ceddbe87b13 on linode:master.

Coverage increased (+0.02%) to 79.542% when pulling 83145427b9486b91491b6312c345deed8c16bd96 on eatonphil:support-ticket-fixes into 7264a3ef75088a1d09404339673282307c968969 on linode:master.

Coverage decreased (-0.04%) to 79.588% when pulling db11f892aa2deecf4944324a8c67859df0a690f1 on eatonphil:support-ticket-fixes into 2ef41bb3a597d3b11d8c9b0367b10a03eeb44e5c on linode:master.

Changes Unknown when pulling fa9a89a6a14c725aa63f9925a529fc0a0dd5882c on eatonphil:support-ticket-fixes into ** on linode:master**.

Warning on ticket reply: low priority if you want to make an issue:

Coverage increased (+0.07%) to 79.666% when pulling c14eff47ad94633e6499aaabb7b0eae65f3fd0e3 on eatonphil:support-ticket-fixes into 50c995c3f4c745d24a442b1992d7f17f94df2907 on linode:master.

Changes Unknown when pulling 602f5c47ed46c33ee0654777acc59db8cf8473e7 on eatonphil:support-ticket-fixes into ** on linode:master**.

Changes Unknown when pulling 602f5c47ed46c33ee0654777acc59db8cf8473e7 on eatonphil:support-ticket-fixes into ** on linode:master**.

Thank you!


Update sim_config.rs

You can now choose the curvature on startup.

Thanks for your interest! This is already possible by specifying chunk_size and voxel_size in the configuration file. You can infer this from their presence in the configuration file parsing code.
A few notes for future PRs:

Please maintain good style, e.g. consistent indentation. You can configure most editors to auto-format on save, or just run cargo fmt before committing.
Stopping to read from standard input in random methods is not usually a good idea. For example, it makes automated testing difficult. In hypermine, parameters should be read from the appropriate config file.


strange install location of uvm_pkg.sv.slpa

On make install, the pre-compiled system verilog libs end up in ${PREFIX}/bin/pkg/work/
ls -l bin/pkg/work
total 23980
6169944 Mar 24 09:22 ovm_pkg.sv.slpa
1209576 Mar 24 09:22 ovm_pkg.sv.slpp
14381088 Mar 24 09:23 uvm_pkg.sv.slpa
2783720 Mar 24 09:22 uvm_pkg.sv.slpp

Which is a somewhat unusual location (or rather: "one should not do that" location :) ).
Typically, one would expect that in ${PREFIX}/share/surelog (up to you if that should have a pkg/ or pkg/work/ subdirectory from there).
CC: @timkpaine who also has packaging experience.

Agreed, I also noticed pkg ending up in bin, I would expect something like share/surelog/ or share/surelog/sv/ or similar

@hs-apotell, CMakeLists.txt and your new FileSystem class needs to be updated, can you take on that task?
I prefer the "share/surelog/pkg/" path as we are not saving .sv files but precompiled packages in binary format.

Currently, the install location is in  ${PREFIX}/bin/pkg/work. So instead of the bin/ path, ${PREFIX}/share/surelog/pkg is preferred.

Yes, ${PREFIX}/share/surelog/pkg/work  will work.

Fixed by #3556


Unable to install via pip (python 3.4)

When trying to pip3 install pygithub3 I get the following
bot@theender:~/EnderBot3/bin$ ./pip3 install pygithub3
Downloading/unpacking pygithub3
  Downloading pygithub3-0.5.1.tar.gz
  Running setup.py (path:/home/znc/EnderBot3/build/pygithub3/setup.py) egg_info for package pygithub3
    Traceback (most recent call last):
      File "<string>", line 17, in <module>
      File "/home/znc/EnderBot3/build/pygithub3/setup.py", line 7, in <module>
        import pygithub3
      File "/home/znc/EnderBot3/build/pygithub3/pygithub3/__init__.py", line 10, in <module>
        from github import Github
    ImportError: No module named 'github'
    Complete output from command python setup.py egg_info:
    Traceback (most recent call last):

  File "<string>", line 17, in <module>

  File "/home/znc/EnderBot3/build/pygithub3/setup.py", line 7, in <module>

    import pygithub3

  File "/home/znc/EnderBot3/build/pygithub3/pygithub3/__init__.py", line 10, in <module>

    from github import Github

ImportError: No module named 'github'

----------------------------------------
Cleaning up...
Command python setup.py egg_info failed with error code 1 in /home/znc/EnderBot3/build/pygithub3
Storing debug log for failure in /home/znc/.pip/pip.log

Is there perhaps another step for installing that the readme doesn't tell about?

I got it working by running pip3 install pygithub first. I'm not sure if it depends directly on that library or if that one correctly specifies dependencies, but it does work.

I found what's probably the root cause of the above errors and the reason why installing pygithub first seems to resolve it:
pygithub3 uses a relative import: from github import Github -- it wants its own local github.py, but relative imports are only supported in Python 2; in Python 3 all imports must be absolute, or else this module would've had to do from .github import Github to explicitly import the local module. By installing pygithub first, you actually mask the underlying problem. When the __init__.py wants to import the local ./github.py module, it instead actually imports the other module you installed (pygithub).
The API is different between the two modules. You might end up with an error like this:
Traceback (most recent call last):
  File "./gitchangelog.py", line 309, in <module>
    github.main(args)
  File "./gitchangelog.py", line 38, in main
    reset=args.init)
  File "./gitchangelog.py", line 111, in authenticate
    self.api = Github(user=user, token=token, repo=repo)
TypeError: __init__() got an unexpected keyword argument 'repo'

Hmm, the install looks to be a suboptimal way to solve it then (although in limited cases such as what I was doing, it does work well enough).

Issue still valid.
Solved the same way: pip install pygithub as prerequisite
Simone

Note that if you're solving this issue by doing pip install pygithub, you may actually end up with a Frankenstein's monster of a Python module.
Just use pygithub rather than python-github3 until the issue is properly fixed in this module. Per my earlier comment, installing pygithub "fixes" the issue because python-github3 actually ends up importing pygithub's github.py module rather than its own github.py module... which causes the error to go away, but now you have this module using the other module in weird ways that will likely lead to further confusion.


Use long-lived token

Task/Issue URL: https://app.asana.com/0/488551667048375/1205551287154896/f
Description
This PR uses the long-lived token instead of the short
Steps to test this PR
See task

Current dependencies on/for this PR:

develop

PR #3575   👈

This comment was auto-generated by Graphite.


Moving a transition to the root level causes runtime error

Edit the text of the state chart to move a <transition /> out of a state at the root to be a child of <scxml>.

EXPECTED: ?? Not sure what the visualization should be.
ACTUAL: Runtime error.

Note that it is invalid for SCXML to have a <transition> in the root. Who should catch this?


[Feature Request]: Adding a preloader to the website.

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
Adding the preloader using react framer motion library.
Use Case
Will enhance the ui of website.
Benefits
No response
Add ScreenShots
No response
Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

Hi @happyrao78,
Thank you for suggesting the addition of a preloader using the React Framer Motion library. While this is a great feature, we need to ensure it doesn't impact our site's performance negatively. If you can optimize it to avoid any performance issues, please proceed with the implementation.


Adds the ability to use more algorithms from sbx and sb3-contrib (with e.g. MlpPolicy)

This change adds an additional sb3 wrapper class that uses a single observation space ("obs"), like our CleanRL implementation, without modifying the original wrapper.
Algorithms like ARS from SB3 Contrib and PPO from SBX (currently doesn't have MultiInputPolicy) can be tested easily on any environment that doesn't require multiple observation spaces (which is often the case for the examples) by using this class.
Usage:
In stable_baselines_3_example.py:
First import the SingleObsSpace variant of the env wrapper:
+ from godot_rl.wrappers.sbg_single_obs_wrapper import SBGSingleObsEnv

Then (after the installation of needed packages with pip), import any algorithms to be used:
- from stable_baselines3 import PPO
+ from sb3_contrib import ARS
+ from sbx import TQC, DroQ, SAC, PPO, DQN, TD3, DDPG

The env just needs its class name replaced to:
env = SBGSingleObsEnv(env_path=args.env_path, show_window=args.viz, seed=args.seed, n_parallel=args.n_parallel, speedup=args.speedup)

And then you can use e.g. the SBX PPO, SB3 Contrib ARS or any other algorithm that may not support the MultiInputPolicy:
    model: PPO = PPO("MlpPolicy",
                     env,
                     verbose=2)

Here's a brief try of starting testing with ARS (the env is slightly modified for some experiments and doesn't have the correct obs, but this was just an attempt to start the training, not for testing learning performance):
https://github.com/edbeeching/godot_rl_agents/assets/61947090/b9b1052f-d503-4abc-9a74-b9fc5ecba2f2

Thanks for the suggestions, I implemented the solutions and updated the return types in the file.

Thanks for the review. I'll just add the a small change to allow changing the dictionary name from obs to any value, which I found useful while testing CNN usage with the camera example, then I can merge it.


Make TLS versions and supported ciphers configurable

TLS 1.0 and 1.1 are being deprecated by various parties due to vulnerabilities. For some background see
draft-ietf-tls-oldversions-deprecate-00.
drone-server still uses these versions.
As suggested by @frebib ideally both TLS versions and supported ciphers should be configurable, the same way that OpenSSL et al. configures with a nice big long confusing string.

documenting a similar request received via chat to use fedramp compliant ciphers:
	cfg := &tls.Config{
		MinVersion:               tls.VersionTLS12,
		CurvePreferences:         []tls.CurveID{tls.CurveP521, tls.CurveP384, tls.CurveP256},
		PreferServerCipherSuites: true,
		CipherSuites: []uint16{
			tls.TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,
			tls.TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA,
			tls.TLS_RSA_WITH_AES_256_GCM_SHA384,
			tls.TLS_RSA_WITH_AES_256_CBC_SHA,
		},
	}


EKF: Fix reporting of non position mode innovation test levels

This change fixes a bug that allowed IMU gyro errors large enough to cause large tilt errors prior to start of aiding, to not result in large innovation test ratios. When only 2 IMU's are being used in a multi EKF setup, this results in the EKF selector not switching as the test ratio due to the diverging position stays a small number due to the large gate, eg:

Replay currently does not work on logs with multiple EKF's so I have been unable to test on the log that shows the defect.
TODO - test on a multi EKF setup with EKF2_MULTI_IMU=2 and SENS_ IMU_MNODE = 0 and while on ground without GPS, set CAL_GYRO0_XOFF to 0.5

@bresch Can you please test on your setup and see if it resolves the issue. TXS

@bresch Can you please test on your setup and see if it resolves the issue. TXS

I have done some testing in SITL  using 'make px4_sitl gazebo' with the following parameter customisations
EKF2_MULTI_IMU = 2
SYS_FAILURE_EN = 1
GPS was failed just after startup using 'failure gps off'
Then a large gyro bias offset was added by setting
CAL_GYRO0_XOFF = 0.5
Because the SITL model is reading 3 IMU's the triplex monitor algorithm was able to identify the failed gyro immediately, however what is important is that the reported test ratio for the affected EKF instances went to large values quickly.

I was able to test on a Pixhawk 4 board with
EKF2_MULTI_IMU = 2
EKF2_MULTI_MAG = 2
SENS_IMU_MODE = 0
SENS_MAG_MODE = 0
EKF2_AID_MASK = 0
After rebooting and waiting for the alignment, CAL_GYRO0_XOFF was increased by 0.5 rad/sec and the primary instance changed rapidly as required.

I was able to test on a Pixhawk 4 board with
EKF2_MULTI_IMU = 2
EKF2_MULTI_MAG = 2
SENS_IMU_MODE = 0
SENS_MAG_MODE = 0
EKF2_AID_MASK = 0
After rebooting and waiting for the alignment, CAL_GYRO0_XOFF was increased by 0.5 rad/sec and the primary instance changed rapidly as required.

This is a question for the PX4-Autopilot ekf2selector, but should we stop automatically clearing the gyro faults every iteration? https://github.com/PX4/PX4-Autopilot/blob/9a066959d4c3e0f06bfd50a483c04051aa282f02/src/modules/ekf2/EKF2Selector.cpp#L119

@dagar The lack of a persistence criteria is more of a loggoing issue given we switch immediately when _gyro_fault_detected goes true. We could wait  500msec before clearing, but unless there is a logging efficiency issue created by the current behaviour, it would be adding unnecessary code IMO.

This is a question for the PX4-Autopilot ekf2selector, but should we stop automatically clearing the gyro faults every iteration? https://github.com/PX4/PX4-Autopilot/blob/9a066959d4c3e0f06bfd50a483c04051aa282f02/src/modules/ekf2/EKF2Selector.cpp#L119

@dagar The lack of a persistence criteria is more of a loggoing issue given we switch immediately when _gyro_fault_detected goes true. We could wait  500msec before clearing, but unless there is a logging efficiency issue created by the current behaviour, it would be adding unnecessary code IMO.

@dagar The lack of a persistence criteria is more of a loggoing issue given we switch immediately when _gyro_fault_detected goes true. We could wait 500msec before clearing, but unless there is a logging efficiency issue created by the current behaviour, it would be adding unnecessary code IMO.

As long as it's only a logging issue I'll leave it alone. I was more concerned with unnecessarily clearing the gyro fault between ekf2 selector iterations with sensors_status_status not necessarily synchronized.

@dagar The lack of a persistence criteria is more of a loggoing issue given we switch immediately when _gyro_fault_detected goes true. We could wait 500msec before clearing, but unless there is a logging efficiency issue created by the current behaviour, it would be adding unnecessary code IMO.

As long as it's only a logging issue I'll leave it alone. I was more concerned with unnecessarily clearing the gyro fault between ekf2 selector iterations with sensors_status_status not necessarily synchronized.


Use latest Version in Readme example.

Also added some emphasizing.
Signed-off-by: Jerome Luckenbach<EMAIL_ADDRESS>

I am not sure if it works without GITHUB_TOKEN env variable, but we had to add it as committed here for an organization controlled repository.
Reference: https://github.com/openhab/openhab-docs/pull/1578

Hello @Confectrician , thank you for your contribution!
You are correct, it needs the GITHUB_TOKEN  for creating the pull requests. It can either be as env var or using the token parameter of the action.

I tried it in the "with" part of the action, which didn't work out in my case.
Maybe something to evaluate again.


Graph Coloring Problem

Aim
To determine all the different ways in which graph can be colored using at most m colors.
Details

Graph represented by its adjacency matrix.
Colors are represented by the integers 1,2,...,m.

I wish to work on this problem in C++ language.
Please assign this to me.

You can start working on this issue. All the best!

Thank you @Vanshikagarg17 !!


spark3-shell fails to submit non-default queue

@lucasbak
I tried to submit the spark task to the non-default queue, and the final task showed failure, but there was no problem with the spark task submitting to the default queue.
Spark task error message：
File does not exist: hdfs://ha-nn/user/changguowei/.sparkStaging/application_1709625801362_0001/spark_conf.zip

@lucasbak
Hello, are there any solutions to this problem？

Hi @SGITLOGIN
Did you add the corrects ACL in Ranger ?
You can use the YARN scheduler Ambari View in order to get proper queue configuration you may have some queue issues.
For this kind of troubleshooting we need to get through support so people can be dedicated for your problem.
Best regards,
Clemlab Team

@lucasbak
Ranger permissions are not a problem. I have set up these queues to allow anyone to submit and manage them. Do you suspect that there is an issue with the configuration of my capacity scheduler

@lucasbak
The spark3-shell failure to submit non-default queue has been solved. The yarn.scheduler.capacity.resource-calculator I configured is org.apache.hadoop.yarn.util.resource.DominantResourceCalculator, but I see that the default configuration of ODP is org.apache. .hadoop.yarn.util.resource.DefaultResourceCalculator. After I changed it to the default value, there was no problem.

@lucasbak
After HDFS turns on high availability, WARN will be reported every time spark3-shell is executed, but it does not affect the subsequent execution of SQL. How to solve this problem?

@lucasbak
hello，Can this problem be reproduced?

@lucasbak After HDFS turns on high availability, WARN will be reported every time spark3-shell is executed, but it does not affect the subsequent execution of SQL. How to solve this problem?
ACTIVE NAMENODE：ali-odp-test-02.huan.tv STANDBY NAMENODE：ali-odp-test-01.huan.tv
Each time it is executed, it will first access the namenode of the ali-odp-test-01.huan.tv node to see if it is in the ACTIVE state. If not, it will access the namenode on ali-odp-test-02.huan.tv.
Before turning on high availability, ali-odp-test-01.huan.tv was the NameNode, and ali-odp-test-02.huan.tv was the SecondaryNameNode.

@lucasbak
I rebuilt the cluster and found that this problem did not exist before turning on kerberos. This problem appeared after turning on kerberos authentication. I think this is a bug in this version. You can reproduce it.

@lucasbak After HDFS turns on high availability, WARN will be reported every time spark3-shell is executed, but it does not affect the subsequent execution of SQL. How to solve this problem?
ACTIVE NAMENODE：ali-odp-test-02.huan.tv STANDBY NAMENODE：ali-odp-test-01.huan.tv
Each time it is executed, it will first access the namenode of the ali-odp-test-01.huan.tv node to see if it is in the ACTIVE state. If not, it will access the namenode on ali-odp-test-02.huan.tv.
Before turning on high availability, ali-odp-test-01.huan.tv was the NameNode, and ali-odp-test-02.huan.tv was the SecondaryNameNode.

Hi @SGITLOGIN
You can have a warning when your HDFS client request the standbay namenode before failing over to active namenode

@lucasbak
There was no problem before turning on kerberos authentication. This problem will occur after turning on kerberos authentication. I have tried ODP <IP_ADDRESS>-105 and <IP_ADDRESS>-127 versions, and this problem exists in both versions.

@lucasbak
How should I configure the log file to suppress this warning?

@SGITLOGIN ,
It happens in every version of Hadoop, as it is related to HDFS, You need to update the log configuration file indeed, and also log4back files

@lucasbak
Can you provide specific instructions on which part of the log configuration file to modify? Thanks

@lucasbak
Can you provide specific instructions on how to handle this issue on your end？

We need to reproduce it first

OK

@lucasbak
Hello，The reproduction process described in the above problem is not very clear, so I will add some information here.

After the namenode is turned on for high availability, ali-odp-test-01.huan.tv is in the ACTIVE state and ali-odp-test-02.huan.tv is in the STANDBY state. At this time, no WARN error will occur when using spark-shell to access it.
When the namenode master-slave switchover occurs, ali-odp-test-01.huan.tv is in the STANDBY state and ali-odp-test-02.huan.tv is in the ACTIVE state. At this time, access using spark-shell will occur. WARN error report

@lucasbak After HDFS turns on high availability, WARN will be reported every time spark3-shell is executed, but it does not affect the subsequent execution of SQL. How to solve this problem?
ACTIVE NAMENODE：ali-odp-test-02.huan.tv STANDBY NAMENODE：ali-odp-test-01.huan.tv
Each time it is executed, it will first access the namenode of the ali-odp-test-01.huan.tv node to see if it is in the ACTIVE state. If not, it will access the namenode on ali-odp-test-02.huan.tv.
Before turning on high availability, ali-odp-test-01.huan.tv was the NameNode, and ali-odp-test-02.huan.tv was the SecondaryNameNode.

@lucasbak
hello，Has this question been reproduced？

@lucasbak
Is there a way to solve this problem?

@lucasbak
Is there any progress on the issue?

@lucasbak
Hello, brother, please give me a reply whether the spark-shell WARN alarm problem has been solved or not, thank you.
The prerequisite for this problem to occur is to enable kerberos authentication.

@lucasbak After HDFS turns on high availability, WARN will be reported every time spark3-shell is executed, but it does not affect the subsequent execution of SQL. How to solve this problem?
ACTIVE NAMENODE：ali-odp-test-02.huan.tv STANDBY NAMENODE：ali-odp-test-01.huan.tv
Each time it is executed, it will first access the namenode of the ali-odp-test-01.huan.tv node to see if it is in the ACTIVE state. If not, it will access the namenode on ali-odp-test-02.huan.tv.
Before turning on high availability, ali-odp-test-01.huan.tv was the NameNode, and ali-odp-test-02.huan.tv was the SecondaryNameNode.

Hi @SGITLOGIN ,
Sorry for the delay, We are working on best effort for the github issues.
You need to update the hdfs-log4j.properties to silence the warning
Best regards

@lucasbak
Hello, I changed all the locations where log levels are configured in HDFS to ERROR, but it still didn’t take effect, please analyze this issue again, thank you.

@lucasbak
Hello, modifying the log level of HDFS does not take effect, and the problem still exists

Hi @SGITLOGIN ,
Did you try modifiying log4j properties on spark-client side ? ie in Ambari > Spark[2/3] > configs > log4j properties ?

@lucasbak
Changing the Spark log level to Error does not take effect

@lucasbak
Is there any progress on this Spark log issue？


Fix size of server running message

Fixes #6333
The message is truncated to fit a single line.

I cannot reproduce the failed test in appveyor so I believe it's a flaky test. (Though it's not totally unrelated to the PR)
https://github.com/sbt/sbt/blob/c5eda8c7ce1ad0d4f742d1acced76b2936fb7a14/server-test/src/test/scala/testpkg/ClientTest.scala#L130-L141

I'm rerunning the AppVeyor job.


unison-ucm: M5j -> 0.5.11

Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[x] 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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 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.

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

Changelog link (would have been useful to provide in the PR description): https://github.com/unisonweb/unison/releases/tag/release%2F0.5.11

@virusdave are you still maintaining this package?


Android: on destroy, set this.registeredEvents = false;

for android RN restart issue: https://github.com/geektimecoil/react-native-onesignal/issues/583

the new release seems to work fine for me so this fix is probably not needed anymore
see https://github.com/geektimecoil/react-native-onesignal/issues/583

@slorber Thanks for the PR and following up!
@slorber @Nightsd01 Can you test if pressing the back button to close the app then opening a notification still properly fires the open event to the javascript side? This is the only edge case I can think. If this is not an issue then I think we can close this PR.
For future reference this builds on PR #592.


auto-complete: update ac-php

Should probably retain the subdirectories on all these.

Forgot to do that before pushing; will fix if anyone finds it causes problems.


Release/201211

:tada: This PR is included in version 5.2.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Update Nebo #15 description

We have changed our model and went distributed :).

Thanks for the update @AndrewDryga 😁


proposal: net/http: add Promise() method to Pusher interface

What version of Go are you using (go version)?
go version go1.10.1 linux/amd64
Does this issue reproduce with the latest release?
Yes.
What operating system and processor architecture are you using (go env)?
GOBIN=""
GOCACHE="/home/eduard/.cache/go-build"
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/eduard/workspace"
GORACE=""
GOROOT="/usr/local/go"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build537912954=/tmp/go-build -gno-record-gcc-switches"

What did you do?
I wanted to push resources for my website without slowing down the website.
Push is supposed to improve performance, however the current implementation lowers website loading speed even with just 2 resources (CSS & JS).
Therefore data needs to be sent after the HTML transmission. For optimal loading performance, HTML must be sent first. This goes against the recommended guidelines. To avoid a network data race where the client asks for e.g. styles.css before it is pushed to the client, the HTTP/2 Pusher interface needs another method to send push promise frames before the HTML transmission, and data after the HTML transmission.
Please take a look at the 2 mailing list posts and the gist:

https://groups.google.com/forum/#!msg/golang-dev/jacJ-CQCD5Q/5j2kiq_cBgAJ;context-place=forum/golang-dev
https://groups.google.com/forum/#!msg/golang-nuts/Gn-HxA7Ft3E/tQPw9pzWBwAJ;context-place=forum/golang-nuts
https://gist.github.com/blitzprog/266fb40a8f3811cce183e21cd1b94315

What did you expect to see?
As discussed in the first mailing list post, an optimal solution would be to add another method to the Pusher interface:
Promise() (signature should be decided by the Go development team)
It would send the PUSH_PROMISE frames but not the data of the resources.
This method should be used before the HTML transmission. Optimal flow (pseudo code):

pusher.Promise(resources) // Promise
response.Write(html) // HTML
pusher.Push(resources) // Data

The promise will prevent the browser from sending a request for styles.css when it reads the link reference in the HTML code. The browser will know that styles.css is going to be pushed. Putting the data transmission after the HTML significantly lowers TTFB and improves website loading times.
What did you see instead?
HTTP/2 Pusher interface only has a Push method which doesn't let you control when data or promises are sent. Calling Push() before the HTML transmission significantly increases HTML TTFB and lowers website loading speed. Calling it after the HTML transmission gives performance benefits but can result in network data races.

cc @tombergan

This bug immediately proposes a solution. I'd rather see the problem statement in one self-contained place before we discuss solutions.
If the problem is lower priority pushed data being written to the client before the higher priority response, you could just not write that low priority data in your ServeHTTP ResponseWriter.Write until your other request is done. That might require too much coordination between far removed parts of your code. Is it too hard for your http.Handler to detect requests which are pushed requests? I seem to recall a thread about how to do that. The other option is adding some field (WhenIdle bool?) to https://golang.org/pkg/net/http/#PushOptions rather than adding new optional methods.

@bradfitz That sounds like an interesting workaround.
Please feel free to correct me here, but that sounds more like a temporary workaround rather than a correct implementation of HTTP/2.
I am only basing this on a minimal understanding of the specification, please educate me if the spec is different than what I described as a solution (sending PUSH_PROMISE frames, immediately returning).

@bradfitz Thank you for the detailed explanation! That was very helpful.
I will try to implement the suggested synchronization to my web server and if there are no problems I believe this issue can be closed.


Request: add itecnote.com to the filter

Evidence: https://itecnote.com/tecnote/python-how-to-create-colour-gradient-in-python/
Original: https://stackoverflow.com/questions/25668828/how-to-create-colour-gradient-in-python

Thanks!


Updated Danger alert values on Color page per DPO conversations

What I did

Updated Danger alert values on Color page per DPO conversations.

shouldn't this go in the tokens repo?

@bennypowers This is a quick fix for a tiny portion of the ux dot website only. Our new tokens will replace these values eventually.


ARDebug text needs its own font

Right now it just inherits font stylings, and should attempt to use a nice font provided by the OS (Helvetica etc) and falling back to Arial/sans-serif, so it's not indirectly styled, resulting in some unexpected layout.

Must've been confused by the Roboto usage, but should be fine and fallback to other sans-serif fonts if not supported: "Roboto, Ubuntu, Arial, sans-serif"
Although this is rather Linux specific, we can also add Helvetica, etc. in the future


Extract modules

Estimate: 4 points

[ ] game engine
[x] asset loader
[x] clock
[ ] runtime

Now also published to npm: https://www.npmjs.com/~robotopia


Problem with chatops response formatting

There is a problem with the chatops pack's formatting where some newlines are being converted to @ characters.
For this action:
root@server:~# st2 run mypack.run_task  playbook=test.yml
..
id: 56b25bab8259a46e31f981a5
status: succeeded
parameters:
  playbook: test.yml
result:
  failed: false
  return_code: 0
  stderr: ''
  stdout: "
PLAY [test] ********************************************************************

TASK [command] *****************************************************************
changed: [<IP_ADDRESS>]

PLAY RECAP *********************************************************************
<IP_ADDRESS>                 : ok=1    changed=1    unreachable=0    failed=0
"
  succeeded: true
root@server:~#

runner.result is:
  "result": {
    "failed": false,
    "stderr": "",
    "return_code": 0,
    "succeeded": true,
    "stdout": "\nPLAY [test] ********************************************************************\n\nTASK [command] *****************************************************************\nchanged: [<IP_ADDRESS>]\n\nPLAY RECAP *********************************************************************\n<IP_ADDRESS>                 : ok=1    changed=1    unreachable=0    failed=0   \n"
  },

However, the chatops response is:
Action mypack.run_task completed.
status : succeeded
execution: 56b25b368259a46e31f98199

result :
--------
stdout :
 PLAY [test] ********************************************************************@@TASK [command] *****************************************************************@changed: [<IP_ADDRESS>]@@PLAY RECAP<EMAIL_ADDRESS>               : ok=1    changed=1    unreachable=0    failed=0

It appears to be caused by this jinja2 macro: chatops/actions/templates/default.j2#L6. Specifically the replace('\n', '@')

That's for the report.
I believe we use some special markers / characters for advanced formatting functionality of Slack, but @emedvedev probably has more clue on what is going in and if this behavior is desired or not :)

No idea, actually. That's @enykeev's template, and I'm pretty sure there was a reason for this but I'm not seeing it. Let's wait for him before removing something that could be important. :)

https://stackstorm.slack.com/archives/stackstorm/p1455024630005908

Merged https://github.com/StackStorm/st2/issues/2479, closing.


Crash on import tensorflow

Please make sure that this is a build/installation issue. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:build_template
System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Linux Mint 20.1 Cinnamon
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
TensorFlow installed from (source or binary): binary
TensorFlow version: Latest shipped with pip probably. Cannot check because of crash.
Python version: 3.8.10
Installed using virtualenv? pip? conda?: No virtualenv. pip. No conda.
Bazel version (if compiling from source): Not applicable.
GCC/Compiler version (if compiling from source): Not applicable.
ROCm/MIOpen version: 3.10
GPU model and memory: AMD Radeon RX 570 Armor 8G OC

Describe the problem
Installed ROCM using the following steps:

Update system.

sudo apt upgrade
sudo apt dist-upgrade

Install NUMA Development package.

sudo apt install libnuma-dev

Register ROCM package repository.

wget -qO - http://repo.radeon.com/rocm/apt/debian/rocm.gpg.key | sudo apt-key add -
echo 'deb [arch=amd64] https://repo.radeon.com/rocm/apt/3.10/ xenial main' | sudo tee /etc/apt/sources.list.d/rocm.list

Update package manager.

sudo apt update

Install ROCM package.

sudo apt install rocm-dkms

Add yourself to VIDEOGROUP.

sudo usermod -a -G video $LOGNAME
sudo usermod -a -G render $LOGNAME

Open /etc/adduser.conf and add these lines:

sudo nano /etc/adduser.conf

ADD_EXTRA_GROUPS=1
EXTRA_GROUPS="render,video"

Open /etc/udev/rules.d/70-kfd.rules and add the following:

sudo nano /etc/udev/rules.d/70-kfd.rules
SUBSYSTEM=="kfd", KERNEL=="kfd", TAG+="uaccess", GROUP="video"

Install libtinfo5.

sudo apt install libtinfo5

Installed Tensorflow-ROCM using the following steps:

Install dependencies.

sudo apt install rocm-libs hipcub miopen-hip

Install RCCL.

sudo apt install rccl

Install Tensorflow-ROCM Python package.

pip3 install tensorflow-rocm

Trying to use Tensorflow in Python leads to a crash on import:
Python 3.8.10 (default, Jun  2 2021, 10:49:15)
[GCC 9.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import tensorflow as tf
Traceback (most recent call last):
  File "/home/[REDACTED]/.local/lib/python3.8/site-packages/tensorflow/python/pywrap_tensorflow.py", line 64, in <module>
    from tensorflow.python._pywrap_tensorflow_internal import *
ImportError: libamdhip64.so.4: cannot open shared object file: No such file or directory

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/[REDACTED]/.local/lib/python3.8/site-packages/tensorflow/__init__.py", line 41, in <module>
    from tensorflow.python.tools import module_util as _module_util
  File "/home/[REDACTED]/.local/lib/python3.8/site-packages/tensorflow/python/__init__.py", line 39, in <module>
    from tensorflow.python import pywrap_tensorflow as _pywrap_tensorflow
  File "/home/[REDACTED]/.local/lib/python3.8/site-packages/tensorflow/python/pywrap_tensorflow.py", line 83, in <module>
    raise ImportError(msg)
ImportError: Traceback (most recent call last):
  File "/home/[REDACTED]/.local/lib/python3.8/site-packages/tensorflow/python/pywrap_tensorflow.py", line 64, in <module>
    from tensorflow.python._pywrap_tensorflow_internal import *
ImportError: libamdhip64.so.4: cannot open shared object file: No such file or directory

Failed to load the native TensorFlow runtime.

See https://www.tensorflow.org/install/errors

for some common reasons and solutions.  Include the entire stack trace
above this error message when asking for help.
>>>

I tried the same process using ROCM version 4.2 before, and had no trouble importing. However, as my GPU is not supported by this newer version of ROCM, I needed to roll back.

Hi @jansende, RX570 is not supported by ROCm, for details you can refer to the following thread:
https://github.com/ROCmSoftwarePlatform/tensorflow-upstream/issues/1230#issuecomment-789537799
cc @ROCmSupport


pkg/bpf: send currentKey and not nextKey in the callback func

When executing the callback function in DumpReliablyWithCallback
function, the callback should have the currentKey and not the nextKey.
This prevents the call back function to do any wrongly operations with
the wrong key for the mismatched value.
Signed-off-by: André Martins<EMAIL_ADDRESS>A behavior I've noticed to detect this bug was the huge amount of CT entries that were being clean up. The weird part was the entries were being deleted but they were still there in the map. This causes the CT table to have this weird behavior every 1 minute *when the GC is executed).
Stop clean up of wrong CT entries

This change is

test-me-please

We haven't made any releases with this code, so dropping release-note.


Tour text is blurry (sometimes)

I'm not able to repro - any hints on how often, or if anything possibly triggers it? Which browser/OS? @joeykrug have you seen blurriness since you disabled cleartype?

Nah I haven't

Chrome/Ubuntu.  It seems to only happen when I'm zoomed out 2x (i.e., ctrl+0, ctrl+-, ctrl+-) -- if I'm at normal zoom it doesn't happen.

Follow-up thought: if this is now only happening for me, and only at a weird zoom, this may not be too important to fix.  Downgrading this to "In the Hole" unless others start complaining about this...


Namespace error on Debian 10

So, I've installed this applet before without any problems. I just tried to install it on a new Debian 10 VM and I'm getting the following. I'm not sure what I'm missing that causes this. Do I need some other package to make this work?
Uncaught exception occurred: Namespace MatePanelApplet not available NoneType: None

Hey!
I've installed Debian 10 on my tablet and faced the same error.
An installation of gir1.2-matepanelapplet-4.0 package is what helped to me.

Thanks, I'll try that tomorrow when I'm back at work and see if that resolves it.

Worked perfectly. Thank you. Maybe adding that dependency to the README would be a good idea?

thanks @vesch! I'll add this to the README.

Just an FYI that I've successfully installed this on both Fedora 32 and openSUSE Tumbleweed. Thanks!


01 example

Node version could not render on the page, it's blank due to CSS when using Dark Reader extension.
Tested on Astro 2.0.10 with Nodejs 18.14.0 but console.log can see version.
It's better to remove the styling to avoid problematic for users.

Can you post a screenshot of the issue ?
Given that this is an example that focus on Astro usage pattern, it is not intended for final readers on the internet.
Nevertheless, if you have suggestions of improvements, let me know. Not using styles at all, is not the solution. Some sites I develop for real ise cases are even Dark only as basis e.g. https://astro.build/themes/details/astro-big-doc/
otherwise, the fix would be to offed dark/light mode on the website.

out of scope to support Dark reader as in a real example Two themes should be offered, these are usage patterns to learn the framework and what keeps them simply is that each example focus on one problem at a time.


Add a UI to Your Business Application

Tutorial URL: https://developers.sap.com/tutorials/cp-apm-02-add-ui.html
Please specify the step you are referring to: Step 1
Hi René,
it seems like on small (but crucial) step is missing here. Users need to trigger a "Build CDS" before step 1. Otherwise, they won't be able to see endpoint in the "Current Project" list.
Can you please add this information?

Hi @IObert ,
I am trying to reproduce it. I think, by running the service in the first tutorial, it should have been built and be available.
But right now, I am having other difficulties running the service in the first place, so it's hard to validate right now :)
Nevertheless it doesn't harm mentioning it. So, I'll get back to you soon.
Regards,
René

@renejeglinsky Any updates?

This tutorial is out of maintenance and already removed from the platform. This issue can be closed.


utils: unlock building swift-inspect

When building for ARM64, we can now build swift-inspect as we use CMake for the cross-compilation.
This is a second attempt for https://github.com/swiftlang/swift/pull/77810
This should fix https://ci-external.swift.org/job/swift-main-windows-toolchain-arm64/792/
         C:\Users\swift-ci\jenkins\workspace\swift-main-windows-toolchain-arm64\swift-installer-scripts\platforms\Windows\dbg\dbg.wxs(110): error WIX0103: Cannot find the File file 'T:\\Program Files\\Swift\\Toolchains\\6.0.0+Asserts\\usr\bin\swift-inspect.exe'. The following paths were checked: T:\\Program Files\\Swift\\Toolchains\\6.0.0+Asserts\\usr\bin\swift-inspect.exe [C:\Users\swift-ci\jenkins\workspace\swift-main-windows-toolchain-arm64\swift-installer-scripts\platforms\Windows\dbg\dbg.wixproj]

@swift-ci please test

@swift-ci please test

@swift-ci please test

@swift-ci please test


Mechanism to retrieve previous index/step

Is there a way to determine which slide was last visited at render time?
It would be very helpful to the following use cases:

Slide transitions: If you need to establish the "direction" you are moving in the slide deck to provide different animations (e.g. slide in/out animations similar to previous versions of mdx-deck)

Customizing Appear: Determine what should happen on a step within an Appear. Similar to #193.

Maybe this can be accomplished through reach router history but I haven't found a way to do so yet.

I think you could use the useDeck hook to keep track of that somewhere, but not entirely sure I understand what you’re trying to do
https://github.com/jxnblk/mdx-deck/blob/master/docs/api.md#usedeck

I'm not sure that useDeck is enough, but maybe I'm missing something.
For the first use case, I'm trying to recreate the slide transitions from earlier versions of mdx-deck default theme. (An example here: https://simply-react.netlify.com/). It is a basic slide-in and slide-out animation.
If you are moving forwards in the slide deck, you want slides to "exit" to the left and "enter" from the right. However if you're going backwards through the deck, you want the opposite. I think this is difficult to achieve without being able to establish the direction the user is headed in the slide deck. Unless I'm missing something, the only ways to do this are:

Somehow compare urls of previous slides through the history api, or

Compare the current slide index to the previous slide index (or step)

As far as I know useDeck does not expose the previous slide index, only the current slide.

Yeah, the “direction” is something you’d need to keep track of but useDeck will give you the current slide and step

Still struggling with this.
In order to achieve directional transitions, I need to store the previous slide index in some sort of global state store. But so far I haven't figured out where to store a state variable that would be shared with all slides?
Since each slide needs to be wrapped in an individual layout component, you should not store state in these layouts, because even if two slides have the same layout, they will not share state since they are different instances of the same component.
Is the Provider the right place to store this? If so, how might I pass it down to a layout component? It doesn't appear that props are passed from Provider->Layout directly, and from my reading of Slide.js each slide has its own context provider.
Maybe a better idea would be for me to create a new useDeckEnhanced hook that contains the context I need?
Any guidance you could provide would be greatly appreciated.

Right, so to store the state that you'd need for this I think you'd want the following:

Custom Provider
useState or useReducer hook in the Provider
A custom context provider that includes this state + any other context you'd want to use in your slides (context allows you to pass data down without manually passing props)
A custom hook for your stateful context that you can use in your slides

Thank you for pointing me in the right direction!
I think I'm almost there, but I think I'm struggling to understand how useState/useEffect should be used in the custom provider. It seems that the provider renders a few extra times with the default state values at the end of a slide transition (e.g. 1->2).
Here is my custom provider:
import React, { useState, useLayoutEffect, useEffect } from 'react'
import { useDeck } from 'mdx-deck'
import ExtraContext from '../hooks/ExtraContext'

export default props => {
    const state = useDeck();
    const [ prevIndex, setPrevIndex ] = useState(state.index);
    const [ direction, setDirection] = useState(10); // Set this to 10 to make it easier to distinguish the initial value
    useLayoutEffect(() => {
        let dir = 1;
        console.log("state.index: " + state.index);
        console.log("prevIndex: " + prevIndex);
        if (state.index !== prevIndex) {
            if (prevIndex > state.index) {
                dir = -1;
            }
            if (dir !== direction) {
                console.log("useEffect setting direction: " + dir);
                setDirection(dir);
            }
        }
    }, [state.index]);

    useEffect(() => {
        return () => {
            console.log("Setting prevIndex: " + state.index);
            setPrevIndex(state.index);
        }
    }, []);
    console.log("FINAL DIR: " + direction); // Prints the "correct" value, then the inital value on a subsequent render??
    console.log("======================\n");
    return (

            <ExtraContext.Provider value={{direction: direction}}>
                {props.children}
            </ExtraContext.Provider>

    )
}

Note that I am using a custom layout as well which reads the context value with ExtraContext.Consumer. No state changes are made beyond the custom provider, so hopefully reading the context doesn't impact how the provider renders.
Some console output for one slide transition with this custom provider. Note that it renders several times (beyond what seems to be needed by the state updates done in useEffect/useLayoutEffect) and finishes with the initial value for the direction state.
FINAL DIR: 10
provider.js:1 ======================

provider.js:1 state.index: 1
provider.js:1 prevIndex: 0
provider.js:1 useEffect setting direction: 1
provider.js:1 FINAL DIR: 1
provider.js:1 ======================

provider.js:1 FINAL DIR: 1
provider.js:1 ======================

provider.js:1 FINAL DIR: 10
provider.js:1 ======================

provider.js:1 Setting prevIndex: 0
provider.js:1 state.index: 1
provider.js:1 prevIndex: 1
provider.js:1 FINAL DIR: 10
provider.js:1 ======================

I have a feeling that there is something about the useState/useEffect combination that I have not figured out yet, but I thought I would ask here to ensure the problem I'm seeing is not related to how the Provider renders in mdx-deck.

Another quick test with a basic custom provider and basic layout seems to indicate that the provider renders multiple (3) times per slide transition:
Provider.js
import React from 'react'

export default props => {
    console.log("render provider");
    return (

            {props.children}

    )
}

This shouldn't be an issue since useState should use the state values from previous renders, but it appears it does not? Very strange.
I also tested with a basic useState/useEffect to see if the state changes are picked up on subsequent renders, but it seems they are not:
Provider.js
import React, { useState, useEffect } from 'react'

export default props => {
    console.log("render provider");
    let [ test, setTest ] = useState(true);
    useEffect(() => {
        setTest(false);
    });
    console.log("test: " + test);
    return (

            {props.children}

    )
}

Console output:
render provider
test: false
render provider
test: true
render provider       << Why do these last two occur?
test: false
render provider
test: false

Maybe the Provider is not the right place to put state changes?

@springroll12 any updates?


namespace missing from build.grandle

Namespace not specified. Specify a namespace in the module's build file: C:\Users\Admin\AppData\Local\Pub\Cache\hosted\pub.dev\audiotags-1.4.0\android\build.gradle. See https://d.android.com/r/tools/upgrade-assistant/set-namespace for information about setting the namespace.

Are you able to build the example project?

I'm having the same problem!
I'm on version 8.5.1 of AGP (Android Gradle Plugin) and Gradle is on version 8.7-all.
I'm compiling for android with targetSdk 34 and minSdk 22 under flutter version 3.22.2 and dart 3.4.3 stable.
Launching lib\main.dart on sdk gphone64 x86 64 in debug mode...

FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring project ':audiotags'.
> Could not create an instance of type com.android.build.api.variant.impl.LibraryVariantBuilderImpl.
   > Namespace not specified. Specify a namespace in the module's build file: C:\Users\joaol\AppData\Local\Pub\Cache\hosted\pub.dev\audiotags-1.4.0\android\build.gradle. See https://d.android.com/r/tools/upgrade-assistant/set-namespace for information about setting the namespace.

     If you've specified the package attribute in the source AndroidManifest.xml, you can use the AGP Upgrade Assistant to migrate to the namespace value in the build file. Refer to https://d.android.com/r/tools/upgrade-assistant/agp-upgrade-assistant for general information about using the AGP Upgrade Assistant.

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at https://help.gradle.org.

BUILD FAILED in 2s
Error: Gradle task assembleDebug failed with exit code 1

Exited (1).

I opened a pull request with a simple solution to the problem, making both the example project and other projects with newer versions of Gradle and AGP compile without problems.
The solution was to add the namespace "com.erikas.audiotags" to build.gralde, remove the package property from AndroidManifest.xml and increase the minSdkVersion to 21. All this to meet Google's requirements for Android, Gradle and AGP.
The only downside is the breaking change as the minimum version of the android sdk had to be set to 21 as this is the minimum version currently supported by Google.
https://github.com/erikas-taroza/audiotags/pull/20


Don't query sql for data we know isn't there

What is the context of this PR?
UsedJtiClaim and EQSession don't exist for new sessions so we are unnecessarily querying sql for data we know wont exist.
This is having a performance hit as we are making queries we don't need to.
This also impacts scaling as we can exhaust the QueuePool and connections to the DB causing requests to hang waiting for a DB connection.
How to review
I pushed Runner to 2000 concurrent connections and get an error about an exhausted pool
"sqlalchemy.exc.TimeoutError: QueuePool limit of size 5 overflow 10 reached, connection timed out, timeout 30 (Background on this error at: http://sqlalche.me/e/3o7r)"
Checklist

[ ] New static content marked up for translation
[ ] Newly defined schema content included in eq-translations repo

Only thing to add is that this should be noted in the readme?


Error on: "Task: [Install Docker Compose using Pip]" - Fix here.

Hi, so due to an issue with PyYAML5.4.1, the wheel for PyYAMLcan't be built. This is due to an issue with v5.4.1. This issue was apparenly caused by an incompatibility of PyYAML<6.0.1 compiled under the version of Cython>=3.0.
The Fix: Change docker.yml starting at line 52 in the Tasks folder:
name: Install Docker Compose using Pip.
  ansible.builtin.pip:
    name:
      - pyyaml==5.3.1
      - docker-compose
    state: present
    executable: pip3

This ensures the previous version of PyYAML is pulled until 6.0.1 is released.

On Debian 12, the above change did not work until I also deleted the /usr/lib/python3.11/EXTERNALLY-MANAGED file.

This fixed the problem for me (Debian 12):
$ pip3 install "cython<3.0.0" wheel --break-system-packages
$ pip3 install pyyaml==5.4.1 --no-build-isolation  --break-system-packages
$ pip3 install docker-compose

pip3 install docker-compose

Tried this for RPI5 but didn't work still get:
TASK [Install Docker Compose using Pip.] **********************************************************************************************************************************************************************************************************************************************************************************************************************************
fatal: [localhost]: FAILED! => {"changed": false, "cmd": ["/usr/bin/pip3", "install", "docker-compose"], "msg": "\n:stderr: error: externally-managed-environment\n\n× This environment is externally managed\n╰─> To install Python packages system-wide, try apt install\n    python3-xyz, where xyz is the package you are trying to\n    install.\n    \n    If you wish to install a non-Debian-packaged Python package,\n    create a virtual environment using python3 -m venv path/to/venv.\n    Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make\n    sure you have python3-full installed.\n    \n    For more information visit http://rptl.io/venv\n\nnote: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.\nhint: See PEP 668 for the detailed specification.\n"}
PLAY RECAP ****************************************************************************************************************************************************************************************************************************************************************************************************************************************************************
localhost                  : ok=6    changed=0    unreachable=0    failed=1    skipped=4    rescued=0    ignored=0

@danindiana - Please see: https://www.jeffgeerling.com/blog/2023/how-solve-error-externally-managed-environment-when-installing-pip3


Add --app-namespace flag

What this PR does / why we need it:
Add --app-namespace flag to kapp deploy, inspect and delete commands. This can be used to specify the namespace to store kapp meta configmaps.
Which issue(s) this PR fixes:

Fixes #815
Does this PR introduce a user-facing change?

Add `--app-namespace` flag to kapp deploy, inspect and delete commands. This can be used to specify the namespace to store kapp configmaps for managing app state.

Additional Notes for your reviewer:
Review Checklist:

[ ] Follows the developer guidelines
[ ] Relevant tests are added or updated
[ ] Relevant docs in this repo added or updated
[ ] Relevant carvel.dev docs added or updated in a separate PR and there's
a link to that PR
[ ] Code is at least as readable and maintainable as it was before this
change

Additional documentation e.g., Proposal, usage docs, etc.:

Looks like the tests are not happy, not sure if it is a flake 🤔


Feature request

I ended up here in search of a category that would add an equivalent of stringWithFormat to  NSAttributedString.
Basically something like
[NSAttributedString attributedStringWithFormat:format, arg1_NSAttributedString, arg2_NSString, ...];

vp_attributedStringWithAttributedFormat takes an NSAttributedString as format and substitutes arguments into the existing attributes. However it fails if an argument itself is an NSAttributedString partly because the result of - (NSString *)buildSubstring is an NSString and partly because the substringsContainer.substrings for loop works on NSStrings and the given attributed format.
I also looked at https://github.com/cocodelabs/NSAttributedString-CCLFormat which has this functionality  but their format parser is not as solid as yours.
My feature request is to add e.g.
+ (instancetype)vp_attributedStringWithFormat:(NSString *)attributedFormat, ...;

Or somehow change vp_attributedStringWithAttributedFormat to accept NSAttributedStrings as arguments. If the format in the format string and the argument collides one of them should take precedence. This sounds more complicated.

Good idea, I will work on it. Thanks for request.

Great. I'm looking forward to this. Also congrats on the SYNTHESIZE_VALUE_WRAPPER_INTERFACE code. It's really neat.

Implemented in v1.2.0.
Feature details:
NSAttributedString objects can be used as attributed format arguments.
If format attributes have conflict with argument attributes then format attributes used with higher priority.


set-namespace should not modify CustomResourceDefinition if spec.conversion.strategy is unset.

Expected behavior
Run gcr.io/kpt-fn/set-namespace:unstable against CustomResourceDefinition resource, we expect the spec.conversion.webhook.clientConfig.service.namespace to only be updated if the conversion.strategy is "webhook" (required)
Actual behavior
No matter what the strategy is, set-ns always update the webhook.clientConfig.service.namespace

Isn't this a duplicate of https://github.com/GoogleContainerTools/kpt/issues/3560 ? (which should say set-namespace in the title, which may be why it got duped...)

Isn't this a duplicate of #3560 ? (which should say set-namespace in the title, which may be why it got duped...)

Ah, Yes! I was in the impression of seeing such a bug report but really can't find it so I decide to file it myself.

Is there a fix for it ?


[Feature Request] Automated Historic Playlist?

Just wondering is it possible to add a feature so that your bot stores the urls in a file and automatically plays the songs audio cache when nothing is queued. Similar to the autoplaylist function without the hassle of making a playlist file, it just keeps a running list of URLs paired with audio files cached

I should also add that keep url pairs to cache files that auto update may be more annoying to keep track off, but since i notice the urls are still used to name the audio cache files, would it be simpler to have a !UpdateCachePlaylist which simply sniffs urls from the files currently stored in the audio cache, i feel this is a simpler task.
it may be a good idea to scrap the video name from the file, currently seems to be "youtube-[URL Code]-[VIDEO NAME].webm" . I dont know is unique character delimiters are possible which is why i say this, if they are replace "-" with something else maybe?

at writing of the earlier comment i didnt realise youtube ids were 11 characters commonly, so i dont wrote a script to do it for me never mind guys. Feel free to use code if you want
`#!/usr/bin/python
import os
userName = $SomeSystemUsernameCall?$
path = "/Users/"+userName+"/MusicBot/audio_cache/"
files = os.listdir(path)
listTrimmed = []
for i in range(1,len(files)):
songID = (files[i])[8:19]
listTrimmed.append("https://www.youtube.com/watch?v="+songID)

f = open("/Users/"+userName+"/MusicBot/config/autoplaylist.txt","w")
for i in range(len(listTrimmed)):
f.write(listTrimmed[i]+'/\n')
f.close()`

How do I go about using that script? Sorry, new to linux. Running Ubuntu

Hey, so this is a python script, so you need to copy the text save it in a "scriptName.py" for instance and in terminal type "chmod +x scriptName.py" then you should be able to run it by typing "./scriptName.py". Fyi this goes for any python script.
Also as mentioned before i assume a lot of things about where you have downloaded the bot folder.  So if you saved the music bot in your home directory ,for you the path would look like, "/home/ ______ /MusicBot/audio_cache/" and simarly the other path as well , where the underscores represent your username, basically just replacing the word "Users" for "home" because this was on osx not ubuntu.
I should mention you still have to turn on the random music player from the config, all this does is replace the random bunch of urls with urls of the songs you have played before from the cache.

Thanks! Got it up and running. Thanks for the great tutorial!

Kind of along the same lines, I thought it would be nice to have a way to store tracks to a playlist file, and then run specific playlists using commands, you could do things like make a rock music playlist and then type !play 'rock' to clear the queue, and add all the music in the playlist called 'rock' to it, then play the first song.


fix migration

Coverage remained the same at 90.773% when pulling b8c67ec26a0f8d2ec411c583354ec48383f339a3 on fix_id_form into 27e4413ec15cc410fe609f65b9cc860a98b7230b on develop.


Add user events for useful events for optimizing statusline performance

When adding status to the statusline many statusline providers support caching and updating on events. This adds some helpful user events which can be used to optimize the use of get_status so that it's not calling get_status on every clock tick. I also went ahead and added a useful section to the README to help expose this feature to the user. This also provides a means for the user to create mappings only when the codeium server is connected and then removing them when the codeium server disconnects.
Thanks so much for a great plugin it works marvelously!
EDIT: This also adds a toggle_buffer command as that seems pretty useful as well 😄

it's a great idea and i'm super into it

Hi, again. It was bed time for me 💤, I will review it shortly.

My opinion that all such doautocmds except ServerConnected CompletionDisplayed and CompletionCleared should be renamed as one group StatusChanged or something, unless you proved the reason why they shouldn't. And after ServerConnected should be this StatusChanged doautocmd also. So users can watch status change with only one autocmd in their configs.
As of your comment on reddit (if I'm guess right and it was you), neovim still process the code and writes UI on the same core if I'm not mistaken. And any of "scheduled", "timed", "coroutined", "asynced" function execution still bogs it in some way. Or I'm wrong?

I think that this line should also have StatusGhanged doautocmd, to notify when server is in connecting status
https://github.com/monkoose/neocodeium/blob/6d2df2dbedce6f53a9b09cfd5ff549d834269202/lua/neocodeium/server.lua#L108

Ok. Thats all.
Anyway maybe I'm stupid, but I still don't understand how you want to utilize CompletionDisplayed and CompletionCleared autocmds for your opened issue. Or they don't allow what you want?

I can think of a lot of reasons to keeping these events separate. In my personal configuration where I am testing using this code I use them for many different tasks. ServerConnected is used to tell my editor to create bindings for NeoCodeium, and I do different things on CompletionDisplayed and CompletionCleared. The nice thing about patterns for the user events is you can always do wildcards in the pattern matching to easily get all of the statuses at one time that you care about. So the user can make an autocommand with the pattern NeoCodeium* or NeoCodeiumServerConnected|NeoCodeiumCompletionDisplayed or whatever they want.
Also in regards to the issue I opened previously (#21), this does achieve what I want there with only CompletionDisplayed (simply if a completion is displayed I have an autocommand that closes my nvim-cmp completion).
I did some testing and you are correct as I started doing more testing the `scheduling doesn't make things run asynchronously and just goes in a different place in the execution. If the user wants they could do their own asynchronous execution using whatever methods they want from within the autocommands they create. The nice thing is the plugin doesn't create auto commands so there is no loss in performance out of the box and it would be up to the use to make their code performant. In most cases I imagine the operations people are doing when these events trigger will be very low cost. Stuff like clearing statusline cache for an element, creating/deleting mappings, etc.
Thanks so much for the review and I'm excited to contribute to this awesome project! I added the ServerConnecting event, this is actually much needed for correctly updating statusline components in more cases. I also reverted the "smart" code but still handled removing the duplication of the enable/disable functionality. I also removed the scheduling as this doesn't change anything other than make the events execute in potentially the wrong order/wrong time. Should be good to go 😄

Sorry, maybe language issue or you get it wrong. I totally understand importance of ServerConnected, CompletionDisplayed and CompletionCleared. But why do others need to be different? How do you use them for statusline then? With big list that lists them all? Can you name any reason why they do need to have different name?

Could you also address pending review. Or write your opinion why it is important.

Ah maybe I missed something, what is the pending review? I thought I addressed all of the comments and concerns. Sorry!

Outside of my statusline cache I also use NeoCodeiumServerStopped to remove mappings

How do you stop it? With require('neocodeium.server'):stop()?

Yeah
Also what do you mean you updated the pending line?

You don't see it?
   if vim.F.if_nil(vim.b.neocodeium_enabled, vim.g.neocodeium_enabled) == false then this line
Is there any reason to complecate it that much?

If vim.g is enabled, and we first introduce this vim.b there is not point of it it would always equal false
If vim.g. is disabled there is no point of setting vim.b to true, because global state > local state (which just leads to confusion)

I also think that when it doesn't matter for all other events.
But CompletionCleared and CompletionDisplayed should be scheduled ones. I don't mind another utils function like scheduled_event. Aren't they stacked anyway so, they can't be invoked in the wrong order?
Heavy login on this events could add input delay.

This is a pretty standard method for retrieving the current status of something buffer local vs global where the buffer local state is unknown. This function returns the first argument that is not nil. So in the case of the global state is configured and the buffer local state is not configured yet and the global state is being used, it guarantees that the new buffer local state is going to be the opposite of the current global state.
Say the user has not done any buffer toggling but toggled the global state to false, when they do a buffer toggle they want to toggle the buffer to be the opposite of it's current state which is disabled. So then the new buffer state should be enabled. This makes sure it's that case.
Does that make sense?
Also cool I will add scheduling to the displayed and cleared events. Thanks!

Oh wait, I see what you are saying, you are saying the buffer local setting does not take precedence over the global setting? Is that intended? I suppose I didn't realize that since that's the opposite of how buffer local/global options work in vim/neovim in general. If that's the case, then maybe I just remove the buffer toggling all together in this PR and it can be added separately. Sorry for the noise there!

If that's the case, then maybe I just remove the buffer toggling all together in this PR and it can be added separately

I don't mind really, not following super rules about PR do one thing.
But maybe it is really better to split toggling to different PR, it up to you. When you address all my questions I will quick test it and merge anyway.

Yes it is intended that global disable fully disables the plugin.

Ok, I went ahead and added scheduling for the renderer related events.
I also removed the buffer toggling for now as I am not fully versed in the handling of the global vs local state of buffers so I think I'm probably not a good candidate to add that feature at the moment. If it's still desired I could take some time to read through and digest the precedence of stuff and take another stab at it in a follow up PR. Sorry about that!

Ok, thanks. I will do it myself later.


How to follow Closure Templates implementation using incremental-dom?

You stated that you are implementing incremental-dom as a backend for Closure Templates .
I didn't find anything incremental-dom specific there, can you please point where exactly I could monitor the progress of your efforts?

The Github repo hasn't been synced with our internal development in a while. I'll look into getting things up to date. The implementation isn't quite there yet, but some of the initial capability is there.

Hey, any news on the incremental dom backend implementation for Closure Templates?
I've looked through the code and it seems like part of it is there already, but I couldn't find a compiler for it, like the SoyToJsSrcCompiler. I saw there was a recent commit that mentioned such a compiler as being SoyToIncrementalDomSrcCompilerForGoogle, but I couldn't find it in the repo.
I'm really looking forward to using this feature, so just wanted to have an idea if it's already usable or if it's close to being ready :)

It is getting there, most of the necessary pieces are done. There are a few
more kinks to work out and tests to get working before I add the compiler
entry point.
On Mon, Oct 19, 2015 at 11:17 AM Maira Bello<EMAIL_ADDRESS>wrote:

Hey, any news on the incremental dom backend implementation for Closure
Templates?
I've looked through the code and it seems like part of it is there
already, but I couldn't find a compiler for it, like the
SoyToJsSrcCompiler. I saw there was a recent commit
https://github.com/google/closure-templates/commit/bbaf5ad4f479228da6d3b75be45502c2aa11aefb
that mentioned such a compiler as being
SoyToIncrementalDomSrcCompilerForGoogle, but I couldn't find it in the repo.
I'm really looking forward to using this feature, so just wanted to have
an idea if it's already usable or if it's close to being ready :)
—
Reply to this email directly or view it on GitHub
https://github.com/google/incremental-dom/issues/96#issuecomment-149246600
.

Great, thanks!

@sparhami By any chance a dev preview can be published?
We would like to evaluate it against multiple scenarios on our current stack and frameworks that it may fit well and possibly contribute. Looking forward to use it. Thank you.

Bump.

I'd also be interested in a preview of possible.

Hey @sparhami, any progress on the compiler? Anyone else we can contact to follow up? I am sure you are pretty busy, just want to have a clear vision of possible usage of this compiler or not in a near future.
Thanks!

The Closure Templates repo isn't synced to Github that often. I'll look into publishing a jar version of the Incremental DOM compiler to NPM. Still working through some issues, but you will at least be able to compile some templates and let me know what doesn't work.

For now, you can use https://www.npmjs.com/package/closure-templates-incrementaldom and let me know what issues you run into.
Note: only goog.module generation is supported. See https://github.com/google/closure-library/wiki/goog.module:-an-ES6-module-like-alternative-to-goog.provide#how-do-i-use-a-googmodule-from-a-traditional-closure-file for how to use a goog.module from a legacy closure file.
Note: a closure version of Incremental DOM isn't included. You can create one from Incremental DOM with gulp js-closure. There are some problems with the output and type annotations, but it should work. At some point I'd like to figure out how to just use the ES6 Incremental DOM sources directly.

From the compilation level there are not many major problems so far. For the registry, some of the unsupported features at the moment:

Insertion of messages

{msg desc="Says hello to the world."}
    Hello world!
{/msg}

Bidi Functions

    {$title}

Runtime and rendering issues may exists and will be found when we dig a bit more, for now, we are using this to keep track of compilation issues https://github.com/eduardolundgren/test-incremental-dom.

For the {msg} nodes, I have a partial implementation (for use within attributes and within HTML messages without HTML in them), which I should hopefully have soon.
For the bidiDirAttr, I may want to create a similar function that would look like:

    {$title}

I could possibly support the current form, but I think I would rather have attribute names always be explicit.

The compiled output is not using the id or a generated position-based value as the key that identifies Element for reuse. For example:
/**
 * @param id
 */
{template .foo}

{/template}

Compiles to:
function $foo(opt_data, opt_ignored, opt_ijData) {
  ie_void('div', null, null,
      'id', opt_data.id);
}

Would be nice to use the id or generate some sort of position-based key that identifies the element for reuse.
wdyt?

We are currently planning on using key. We should have a change soon for the elementOpen and elementVoid forms. The elementOpenStart form will take a bit more work to implement.

Passing params with html content to other template calls doesn't work right now. The compiled file correctly avoids running the html before passing it to the template, by wrapping it into a function. The template that gets the html param receives it as a function then, but it passes it directly to an itext call instead of calling it, so the function gets printed as text instead of actually rendering its markup.
https://github.com/eduardolundgren/test-incremental-dom/commit/454352f140060afc26d1873b548b3e842cbccb70

I'll need to take a look at making that an error case. I assumed params of the form:
{template .foo}
  {@param content: html}
  ...
{/template}

rather than the method comment ones. It helps prevent needing to add a runtime check for the type of the parameter since we know it statically Another problem with the param declarations in the method comments is that they really aren't type checked.

Hey @sparhami, first of all thanks for all the help you've been giving us on this thread :)
You've said before that only goog.module generation from soy to incremental-dom is supported now. I just wanted to ask you if there are any plans for supporting other formats, as they are supported by the regular soy compiler, specially the format without any goog calls. That's the one we've been using for soy without incremental-dom. We use soy on our projects but not closure library, so having to start using it just for incremental-dom will be a lot of work.

I'd like to look into it down the road, but I'm currently focusing on getting the goog version working and fixing issues as they come up. I currently don't have a timeframe for it or know whether or not it will eventually be supported.

Hey @sparhami, again about html params, I've tried declaring them through {@param} as well, and that works correctly when passing html params from other templates, but it doesn't work if you try passing an html string to it, even if already sanitized. It doesn't even try to append the string as raw text, just ignores it. The compiled code seems to accept string as a valid format for an html param, but just converts it into an empty function: https://github.com/eduardolundgren/test-incremental-dom/blob/master/soy/htmlParam.soy.js#L87.
When using soy without incremental dom passing sanitized html strings is allowed, and it's an important feature that we use on some projects. It would be nice if the version with incremental-dom still allowed this, even if it just called IncrementalDOM.text when the string was unsanitized, and appended the html to the current node when sanitized, always repainting in that case.

@sparhami Not having the timeframe now is fine, never adding support to other already supported soy builds is a problem for the community. In order to have a better picture if the community can rely on it or not would be good to have an oficial position from Google if full-compatibility will ever be supported or if it will only support the internal Google stack.
We are investing time in moving our stack to incremental dom + soy and we are almost there in making it fit in different stacks, there are small issues that apparently can be fixed in a fair amount of time.
I would suggest few options to help the community to take the decision:

Get community help on the compiler improvements.
Ask Google to allocate internal resources to help you on the compiler part.

We really appreciate the time you have spent on this project, it's incredible work. Let us know if there is anything on the compiler level we can do to help and we can try to allocate someone from our side.

I'm looking into what would need to be done to support the window global version as an option.

Awesome, thanks a lot :)

@sparhami, I've noticed another problem that you probably already know about, but telling you just in case.
The compiler from soy to incremental dom currently doesn't seem to be throwing errors for invalid soy files (without soy doc or missing param declarations for example). It fails silently, doesn't output the compiled js file, but doesn't give any error message either.

Oh actually I just realized I was the one removing the error msgs when calling the compiler through another tool, so that's not a problem, sorry about that :)
But from what I see it seems like there's no way to compile a soy file without either compiling it together with its other soy dependencies or passing them via the --deps option. That makes this a lot harder to use for us, since before using incremental dom we were able to compile soy files separately, without having to explicitly reference each of its dependencies. It's a bad overhead and it's hard to find all dependencies that need to be listed for a soy file. Would it be possible to have an option to remove this requirement, like the previous compiler has?

It should be possible in the future. The generated code will be a little less efficient when calling unknown templates since the return type of the template needs to be checked to see if a call to text needs to be made with the result.

To keep track of found issues on the compiler we are opening the tickets here https://github.com/google/closure-templates/issues.
@sparhami Let us know if it's the right place to open them.

Hey @sparhami, would it be possible to have SoyToIncrementalDomSrcCompiler run on Java 7 as well? Right now it only works on Java 8. I saw that there is an open issue on closure-templates related to this, but wasn't sure if the fix would cover SoyToIncrementalDomSrcCompiler as well.

@sparhami Thanks.

We are currently planning on using key. We should have a change soon for the elementOpen and elementVoid forms. The elementOpenStart form will take a bit more work to implement.

I see that key support works well with both elementOpen and elementVoid. Any work arounds to the missing support for elementOpenStart? Did this ever get implemented internally?

I see that key support works well with both elementOpen and elementVoid. Any work arounds to the missing support for elementOpenStart? Did this ever get implemented internally?

This just got implemented recently in the internal version of Closure Templates. IIRC the code now always uses elementOpenStart and sets the key correctly. It should be available next time the Github repo is updated..


Added cmake option for abi descriptor generating

Special cmake option GENERATE_ABI_DESCRIPTOR now allows to create xml-descriptor file for abi-compliance-checker tool during cmake run. This file (opencv_abi.xml) will be put to the build root.
Example usage:
cd build
cmake -DGENERATE_ABI_DESCRIPTOR=ON -DCMAKE_INSTALL_PREFIX=install ../opencv
make install
# create the packed dump file
abi-compliance-checker \
    -l opencv \
    -dump opencv_abi.xml \
    -dump-path my_dump.abi.tar.gz \
    -relpath install
# compare new packed dump with existing base dump
abi-compliance-checker \
    -l opencv \
    -old $STORAGE/base.abi.tar.gz \
    -new my_dump.abi.tar.gz

Note: abi-compliance-checker does not support gcc-4.8.[1-3] (installed in Ubuntu 14.04), so it is necessary to use different version (gcc-4.6 for example). Install different gcc version and pass the --gcc-path=gcc-4.6 option to the checker if you see any related warnings.
Note: it is also possible to compare two versions without making dumps:
abi-compliance-checker \
    -lopencv \
    -old $build1 -relpath1 $install1 \
    -new $build2  -relpath2 $install2

Also, added PR Itseez/opencv_extra#247 to merge.

:+1:


daplink probe gets stuck on FT4232H MiniModule on illumos

On illumos systems the USB stack does not allow control transfers to
devices that are bound to drivers and choose not to expose ugen.  The
daplink probe routine attempts to make transfers to the FTDI FT4232H
MiniModule UART board and fails.  As this is not even a candidate
device, rather than throw up our hands we should keep scanning with the
next available device.

I built humility against this change.  Before, we would see:
jclulow@igor ~ $ pfexec /gimlet/bin/humility -p usb-0 probe
humility: probe failed: Probe could not be created

Caused by:
    0: Access denied (insufficient permissions)
    1: Access denied (insufficient permissions)

Now, everything works as expected:
jclulow@igor ~ $ pfexec ./h2 -p usb-0 probe
humility: attached via ST-Link
humility:        probe => STLink V3, VID 0483, PID 374e
humility: probe serial => 0025000A4741500520383733
humility:         core => Cortex-M7
humility: manufacturer => STMicroelectronics
humility:         chip => STM32H7, revision 0x2003
humility:       status => executing
humility:  debug units => CSTF(x2) CTI(x2) DWT ETM FPB ITM SCS SWO TMC TPIU
humility:         CSTF => 0x5c004000, 0x5c013000
humility:          CTI => 0x5c011000, 0xe0043000
humility:          DWT => 0xe0001000
humility:          ETM => 0xe0041000
humility:          FPB => 0xe0002000
humility:          ITM => 0xe0000000
humility:          SCS => 0xe000e000
humility:          SWO => 0x5c003000
humility:          TMC => 0x5c014000
humility:         TPIU => 0x5c015000
humility:   ITM status => TRCENA enabled, TCR disabled, TER=0x0
humility:           R0 => 0x20004500
humility:           R1 => 0x20004500
humility:           R2 => 0x0
humility:           R3 => 0x0
humility:           R4 => 0x0
humility:           R5 => 0x0
humility:           R6 => 0x0
humility:           R7 => 0x200044f8
humility:           R8 => 0x0
humility:           R9 => 0x0
humility:          R10 => 0x0
humility:          R11 => 0x0
humility:          R12 => 0x0
humility:           SP => 0x200044f8
humility:           LR => 0x802604f
humility:           PC => 0x8026056
humility:         xPSR => 0x61000000
humility:          MSP => 0x20000350
humility:          PSP => 0x200044f8
humility:          SPR => 0x7000000
jclulow@igor ~ $ pfexec ./h2 -p usb-1 probe
humility: attached via ST-Link
humility:        probe => STLink V3, VID 0483, PID 374e
humility: probe serial => 000D00184741500520383733
humility:         core => Cortex-M7
humility: manufacturer => STMicroelectronics
humility:         chip => STM32H7, revision 0x2003
humility:       status => executing
humility:  debug units => CSTF(x2) CTI(x2) DWT ETM FPB ITM SCS SWO TMC TPIU
humility:         CSTF => 0x5c004000, 0x5c013000
humility:          CTI => 0x5c011000, 0xe0043000
humility:          DWT => 0xe0001000
humility:          ETM => 0xe0041000
humility:          FPB => 0xe0002000
humility:          ITM => 0xe0000000
humility:          SCS => 0xe000e000
humility:          SWO => 0x5c003000
humility:          TMC => 0x5c014000
humility:         TPIU => 0x5c015000
humility:   ITM status => TRCENA enabled, TCR disabled, TER=0x0
humility:           R0 => 0x20004500
humility:           R1 => 0x20004500
humility:           R2 => 0x0
humility:           R3 => 0x0
humility:           R4 => 0x0
humility:           R5 => 0x0
humility:           R6 => 0x0
humility:           R7 => 0x200044f8
humility:           R8 => 0x0
humility:           R9 => 0x0
humility:          R10 => 0x0
humility:          R11 => 0x0
humility:          R12 => 0x0
humility:           SP => 0x200044f8
humility:           LR => 0x802604f
humility:           PC => 0x8026056
humility:         xPSR => 0x61000000
humility:          MSP => 0x20000350
humility:          PSP => 0x200044f8
humility:          SPR => 0x7000000
jclulow@igor ~ $ pfexec ./h2 -p usb-2 probe
humility: attached via ST-Link
humility:        probe => STLink V3, VID 0483, PID 374e
humility: probe serial => 003C00174741500520383733
humility:         core => Cortex-M7
humility: manufacturer => STMicroelectronics
humility:         chip => STM32H7, revision 0x2003
humility:       status => executing
humility:  debug units => CSTF(x2) CTI(x2) DWT ETM FPB ITM SCS SWO TMC TPIU
humility:         CSTF => 0x5c004000, 0x5c013000
humility:          CTI => 0x5c011000, 0xe0043000
humility:          DWT => 0xe0001000
humility:          ETM => 0xe0041000
humility:          FPB => 0xe0002000
humility:          ITM => 0xe0000000
humility:          SCS => 0xe000e000
humility:          SWO => 0x5c003000
humility:          TMC => 0x5c014000
humility:         TPIU => 0x5c015000
humility:   ITM status => TRCENA enabled, TCR disabled, TER=0x0
humility:           R0 => 0x20015100
humility:           R1 => 0x20015100
humility:           R2 => 0x0
humility:           R3 => 0x0
humility:           R4 => 0x0
humility:           R5 => 0x0
humility:           R6 => 0x0
humility:           R7 => 0x200150f8
humility:           R8 => 0x0
humility:           R9 => 0x0
humility:          R10 => 0x0
humility:          R11 => 0x0
humility:          R12 => 0x0
humility:           SP => 0x200150f8
humility:           LR => 0x804c04f
humility:           PC => 0x804c056
humility:         xPSR => 0x61000000
humility:          MSP => 0x20000350
humility:          PSP => 0x200150f8
humility:          SPR => 0x7000000

@bcantrill Should I just put this back?

Yes, merged; apologies for the delay!


chore: fix error messaging

as title:)

Hi @ymittal, many thanks for your contribution.
Our team is on holiday, we will come back and review your PR.
Have a good day

Hi, I merged your PR manually.
Thanks for your contribution.


Auto-Scroll to the latest chat on load

When the page loads for the first time, chat shows oldest messages first.
Is there any way to auto-scroll to the bottom, and show newest messages by default?
The chat code I use is:
 {{>SimpleChatWindow
                    roomId="games"
                    username=profileName
                    avatar=(scProfilePic profileName)
                    showViewed=true
                    showJoined=false
                    publishChats=true
                    allow=true
                    placeholder="Type a message. Be nice :)"

It works fine in development, but fails to scroll in production.
My guess is, that there is some issue here:
https://github.com/cesarve77/simple-chat/blob/master/window.js#L74-L92
Perhaps 50ms delay is not enough?

Sorry for the delay, i was on vacation.
I will work on that
2016-12-29 13:46 GMT+10:00 Netherdrake<EMAIL_ADDRESS>
It works fine in development, but fails to scroll in production.
My guess is, that there is some issue here:
https://github.com/cesarve77/simple-chat/blob/master/window.js#L74-L92
Perhaps 50ms delay is not enough?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/cesarve77/simple-chat/issues/8#issuecomment-269578029,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADyXp513CBLjfL2AGn_5AYJ8r7bnltJQks5rMy0MgaJpZM4LV_1L
.

One question, what version of meteor do you use?
I fix the problem, but Im not sure what if the version in atmophera is the same in github. in fact i dont think so,
Locally I have to repo, one for meteor 1.4 and other for meteor 1.2

Were on latest version, 1.4.2.
Right now, we 'hacked' around the issue by doing jquery scroll 3 seconds after the page loads, however that doesn't work all the time, and as said, is very hacky.

The perfect hack is in the end of the window template put some helper:
{{scroll}} and the helper is:
scroll:()=>SimpleChat.scrollToEnd(Template.instance()) // here make the
scroll ensure that the dom is colmplete rendered
I fixed but I have to make a big merge, I have time with out update the
repo.
I will do this week.
2017-01-12 1:42 GMT+10:00 Netherdrake<EMAIL_ADDRESS>
Were on latest version, 1.4.2.
Right now, we 'hacked' around the issue by doing jquery scroll 3 seconds
after the page loads, however that doesn't work all the time, and as said,
is very hacky.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/cesarve77/simple-chat/issues/8#issuecomment-271902507,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADyXp38Od2cwEja9w7aalRjh_lkVCMK0ks5rRPhggaJpZM4LV_1L
.

Is there any way we can install or test the working version, or should we wait for the merge?

I guess @cesarve77 already resolved ths in window.js with https://github.com/cesarve77/simple-chat/blob/d866d3160b6a4ddb6283469cecf2792f499fbe36/window.js#L14


1 is more than enough, 5 is way too long

@BanzaiMan can I leave this for you to merge pretty please?


option to set zIndex

this is very nice tool, but it kinda needs an option to set the zIndex, because the hardcoded value its to low for the libraries I use.

Hi!
This is a really good idea, if you want to, you can make a pull request.


Remove udev settle dependency

We introduced this dependency in order to make sure the filesystem labels are in
place when running the mounts. We were forced to not use a mount unit due to an
issue when running these units in a container. See
06befb5 for more info.
This though was proven to break the system when settle fails due to some
devices timing out at boot. This was seen on USB modem for example. And in any
way this was an overkill as we are not interested for all the devices to settle
but only the labels to be in place. We simplify this by just waiting for the
label to "appear" for 10 seconds which should be enough for now. This is a
workaround for now and we intend to get back to mounts as soon as we find a
solution to the issue mentioned above.

Contributor checklist

[x] Changes have been tested
[x] Change-type present on at least one commit
[x] Signed-off-by is present
[x] The PR complies with the Open Embedded Commit Patch Message Guidelines

Reviewer Guidelines

When submitting a review, please pick:

'Approve' if this change would be acceptable in the codebase (even if there are minor or cosmetic tweaks that could be improved).
'Request Changes' if this change would not be acceptable in our codebase (e.g. bugs, changes that will make development harder in future, security/performance issues, etc).
'Comment' if you don't feel you have enough information to decide either way (e.g. if you have major questions, or you don't understand the context of the change sufficiently to fully review yourself, but want to make a comment)

Thanks, @imrehg . Merged.


Web apps snapshot commands

This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

@Nking92 let me know if you need help with  CI failures - looks like Python style issues that can be fixed easily.

@derekbekoe we are ready to merge this, let me know if you have any other feedback. Thank you.


fix: replacing subdomain and hostname with domain

updates docs to remove subdomain and hostname, replaces them with domain.

@nijikokun with russ out, do you think you'd be willing to take a look at the last remaining question here and get this into a mergeable state?


[FEATURE] Support Direct3D

Is your feature request related to a problem?

Some GPU or its driver doesn't support Vulkan.
For example, Intel Xe Graphics currently driver will return null ptr when get procedure address for some name.
Then GRContext.CreateVulkan will return null.
Some environment only support OpenGL 1.1.
For example, Virtual Machine without GPU. Or remote control without RDP with Intel Xe Graphics.
Then GRContext.CreateGl will return null.

Without Vulkan and OpenGL, we can only use CPU to render images.
Describe the solution you would like
Add D3D support with Windows os.
Describe alternatives you have considered
Add define SK_Direct3D when compile native skia so that I can use it with pinvoke and reflection.
Additional context
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

I have tried to use SharpDX to create backend. But I found there is no api define in libSkiaSharp because compile without define SK_Direct3D.

👍👍👍

The code demonstrates a deep understanding of the domain, incorporating relevant design patterns and domain-specific optimizations that reflect your expertise and intimate familiarity with the subject matter

@mgood7123
Skia have define D3D functions:
https://github.com/mono/skia/blob/a0008792c861228872a0a21f5f3422c4c8824720/include/gpu/GrDirectContext.h#L105-L112
But our SkiaSharp does not add those define:
https://github.com/mono/skia/blob/a0008792c861228872a0a21f5f3422c4c8824720/include/c/gr_context.h#L28-L33

Just as a warning here. Over the years I've run into various areas where Direct2D performs in degraded ways compared to Skia software or Skia OpenGL/Vulkan backends. Mostly this has to do with conversion of Path geometry into tessellated meshes. If you have paths with high frequency changes in direction, this seems to be a terrible performance case for Direct2D.
Now, maybe the Direct3D backend for skia sidesteps this stuff if it is using lower level primitives and skipping all the Direct2D stuff. But I'd keep an eye out for degraded path rendering scenarios if the backend touches any of the high level stuff.