Add option for tags on import

With this small change, tags can be added inside the import by adding them after whitespace, ie:
https://google.com search other
will add google with two tags, search and other.
We are looking at using changedetection to track a larger number of websites, the URLs for which are added automatically and should be categorized. Hence I thought this was a useful change.
I had disabled black, but isort was still running, so the imports in __init__.py have been sorted as well. I thought it's fine to leave, as better organized imports don't hurt. If you'd rather not do this, I'm happy to revert those changes.
Also, PR onto master because dev seems to have been abandoned a short while ago?

Nice PR! so two things

Please add a test
Please add some note at the bottom of the import textarea like You can also import tags, example...

for tests, you can see the a simple existing test in changedetection.io/tests/, import say 2-3 URL's with tags, and then do something like, get the main page, then assert b'tag1' on the page, check the existing tests

I had disabled black, but isort was

not sure what you mean here

I'll make the changes as requested later!

I had disabled black, but isort was

not sure what you mean here

I use the black code formatter (https://github.com/psf/black), which I turn off for work that isn't already formatted (otherwise my PR would format the whole file in a different style). I didn't find any code-style guidelines in the contributing file, may be good to add?

@timlod I just realised that you need to also add support for exporting the tags in a url list in the [backup] functionality, I think it's best to dump these to an extra text file called url-list-with-tags.txt
https://github.com/dgtlmoon/changedetection.io/blob/eeba8c864d8375775ac04720856e537036ca643e/changedetectionio/__init__.py#L815
also, still waiting for tests :)

@dgtlmoon OK! I have been busy, but will do this tonight.

@dgtlmoon I am in the process of writing the test, but I can't run any tests? May be because I don't normally use pytest for tests and I'm doing something wrong, but I get:
TEST RUNNING tests/test_access_control.py
ERROR: usage: pytest [options] [file_or_dir] [file_or_dir] [...]
pytest: error: unrecognized arguments: --no-start-live-server --live-server-port=5005
  inifile: /home/tim/correlaid/banktrack/changedetection.io/changedetectionio/pytest.ini
  rootdir: /home/tim/correlaid/banktrack/changedetection.io/changedetectionio```

@timlod make sure you're using these version..
pytest ~=6.2
pytest-flask ~=1.2

pytest tests/test_access_control.py

Thanks - pushed the test! I didn't have pytest-flask installed, wasn't aware of it. Let me know if anything else needs fixing.
Am I missing some document outlining things like these? Would it perhaps make sense to update https://github.com/dgtlmoon/changedetection.io/blob/master/CONTRIBUTING.md with instructions on how to run the test suite, and perhaps some other guidelines?

@timlod wonderful! hmm, there is https://github.com/dgtlmoon/changedetection.io/blob/master/requirements-dev.txt but I've updated that https://github.com/dgtlmoon/changedetection.io/blob/master/CONTRIBUTING.md just now with your recommendations, thanks!

@timlod check out https://github.com/dgtlmoon/changedetection.io/pull/385
This is why it's super important to follow the 'zen' of testing :) on the front end "quick add" widget it doesn't allow you to add duplicate URLs

@timlod in view of #385 I think just making those URL's unique at the test import step will be enough for me to merge this in, the actual fixes for the inconsistency will go in #385

@dgtlmoon See above - how do you feel about the actual URLs used?
Can you confirm that requests are actually made during testing? Because if running tests will attempt to download these pages, we should make sure that the URLs for this are appropriate.
Also, can you comment on the duplicate issue? I would think that allowing duplicates is fine - because you may want to monitor a site twice with different rules each time. Plus this is supported by the clone feature.

@timlod

Can you confirm that requests are actually made during testing? Because if running tests will attempt to download these pages, we should make sure that the URLs for this are appropriate.

all requests happen in a separate thread, otherwise the application would crash, they are inserted into a queue, so there is zero chance they will "block" the insert, but they will get requested (in the background thread)

I would think that allowing duplicates is fine - because you may want to monitor a site twice with different rules each time. Plus this is supported by the clone feature.

Actually you have a point, but for now, the front end widget has always NOT let you add duplicates.. and now the 'import' tab allows you to add duplicates.. so.. it has to be one or the other, but not both right?

so yeah ok.. we can continue this in #385 :)

Agreed about moving the talk for duplicates. It may still be good to not actually make any requests for tests that do not require checking the stored data, as that would be checked by a different unit, and ie. these tests only require adding the item, not making the request. Anyways, it works now, and if it's simpler this way it's prudent to keep the current behaviour.


add shell.nix file for Nix users

NixOS users may need this file to build Cursive if they don't want to install ncurses in their user profile.

Thank you for your contribution!
I don't know much about NixOS; when would this file be required?
Would this help if a NixOS user tries to compile a rust application that depends on cursive?

when would this file be required?

Every time they try to build Cursive. NixOS users enter a shell environment with the dependencies declared in shell.nix present so they get reproducible builds.
In theory those dependencies could also be installed system-wide, but I just tried that and it fails for some reason. I guess nix-shell environments keep references to build dependencies that are removed when the dependencies are installed as applications for the user.

Would this help if a NixOS user tries to compile a rust application that depends on cursive?

In this case Cursive is fetched as a compiled library so shell.nix is not included. They would need to write their own shell.nix for that project. However, if we have a shell.nix here they can just copy our dependencies into theirs.

If nix users use cargo, I think it downloads dependencies and compiles them locally?
Anyway, I can merge that if there's cases where it helps.

Even then, Cursive's shell.nix would not be downloaded into their project's root dir, so they'd need to type its full path somewhere in target/build/cursive-* every time. And if they need additional dependencies they still have to create their own file.
Cool, thanks!


update dataLayer data with ga4 recommendation

follow the optimize ga4 recommendation.
@see https://developers.google.com/optimize/devguides/experiments?technology=ga4#add-ga-tracking-code-to-variants
Fix #1

Thanks! :+1:


Tooltips

We have lots of helpful links, but sometimes we don't want to make readers go to a different page to find out what something is.
We also don't want to clog the page full of definitions.
It'd be great to have tooltip markdown so that we can have a short explanation appear on hover.

Good idea, although worth remembering there is no hover on mobile, so you may need a small info icon that you can press.


Time parsing

We will need to parse time points and durations for start dates, run times and diagnostic frequencies. One good template to use would be how XIOS handles time definitions (which is fairly standard).
I probably cannot continue to just typedef the TimePoint and Duration classes, as this means I cannot create overloads for operator>>, as the type system only sees them as instances of the class they are defined as.
Issue #100 depends on this.

Fixed as part of PR #101.


associated function new is private

Bug Description
When multiple-pymethods is enabled, it does not compile because
Pyo3MethodsInventoryFor[MyClassName]::new is private
Steps to Reproduce
#[pyo3::pyclass]
#[derive(Clone, Debug)]
pub struct Client {
..
}

features = [
"extension-module",
"multiple-pymethods",
]
expands to
...
#[doc(hidden)]
    pub struct Pyo3MethodsInventoryForClient {
        items: _pyo3::impl_::pyclass::PyClassItems,
    }
    impl Pyo3MethodsInventoryForClient {
        const fn new(items: _pyo3::impl_::pyclass::PyClassItems) -> Self {
            Self { items }
        }
    }
    impl _pyo3::impl_::pyclass::PyClassInventory for Pyo3MethodsInventoryForClient {
        fn items(&self) -> &_pyo3::impl_::pyclass::PyClassItems {
            &self.items
        }
    }
    _pyo3::inventory::collect!(Pyo3MethodsInventoryForClient);
...

I had to manually paste the expanded code and change const fn new to pub const fn new
Backtrace
No response
Your operating system and version
.
Your Python version (python --version)
.
Your Rust version (rustc --version)
.
Your PyO3 version
rev = "3ed0df1169f43d28c493fdbd485d24feb4e00782"
How did you install python? Did you use a virtualenv?
.
Additional Info
No response

Can you show more code please? That is not enough to reproduce it.

Here is a reproduce:
https://github.com/elbaro/pyo3-2168

Thanks, that reproduces it for me :)

https://github.com/PyO3/pyo3/pull/2169 should fix this


ClinVar submission via API

Direct submission of single and batched ClinVar submissions from the VCI via ClinVar's API
JIRA ticket: https://broadinstitute.atlassian.net/browse/CSP-155
Replaces https://github.com/ClinGen/clincoded/issues/2300

From https://github.com/ClinGen/clincoded/issues/2029 :

Ability to generate ClinVar submissions (included in R27)
Ability to upload ClinVar reports such that SCV numbers are integrated into VCI
Allow bulk generation of ClinVar submissions
Tie ERepo and ClinVar submission together (tandem submission)

https://broadinstitute.atlassian.net/browse/CSP-99

Note: the Broad has developed a python script to use the ClinVar API, the code could be stood up as a service or incorporated into the VCI code.

is this done? @cgpreston

We met with the PharmGKB group today, they plan to assess the ClinVar API documentation and test platform to determine if the current REST API will support all their use cases.
Once that is complete the team plans to assess the best path forward to building submission system(s) supporting the various curation platforms. The team also identified that it makes sense to build a single 'surveillance" system to update all platforms (v3 VCI, PGx submissions, v4 VCI, HLA (?)), on the status of their submissions.


Is this a right approach?

PydObject my_import(string name) {
    debug assert(Py_IsInitialized(), "python not initialized");
    auto list=new PydObject(PyImport_GetModuleDict());
	if(list.has_key(name))
    	return new PydObject(PyImport_ReloadModule(PyImport_AddModule(zcc(name))));
    else
    	return new PydObject(PyImport_ImportModule(zcc(name)));
}

The idea behind this is that scripts are loaded dynamically when certain command received, and if it fails then we can fix script's code without restarting the "kernel".

Seems like I've got a problem with this... Might need your help to solve it. I'll try to debug first.

I've managed it. The problem was that imports are global and I had been trying to run them as "stand alone scripts" having globals in them, and it's all got messed up between two separate contexts (for two different users). Resoled like this:
InterpContext loadScript(string modName){
	auto script = new InterpContext;
	try{
		script.py_stmts("import os, sys");
		script.py_stmts("sys.path.append(os.getcwd())");
		script.py_stmts("sys.path.append(os.getcwd()+'/"~scriptHome~"/')");//for loading extra modules
		script.mod=my_import(scriptHome~"."~modName);
		script.error="";
	}catch(Exception e){
		logInfo("Importing script failed!");
		logInfo(e.msg);
		script.error=e.msg;
	}
	return script;
}
........
InterpContext script;
script = loadScript(sc.moduleName);
script.comm=script.py_eval("mod.Interface()");
script.cmd=command;
script.py_stmts("comm.command(cmd)");

This way separate sessions do not get mixed up :)))

nice. but this line
script.py_stmts("sys.path.append(os.getcwd()+'/"~scriptHome~"/')");

is making me twitch (xss vuln)

Is there a better way to add path to global python system vars?

script.scriptHome = scriptHome;
script.py_stmts("sys.path.append(os.getcwd()+ scriptHome)");

or somesuch

Thx, fixed :)


Not impute to 0 not_imputable data

Dear Sir,
while using the fancyimpute package (many thanks for your work), I'd find appreciable if I could have the possibility not_to_set_to_zero the values that for some reason do not get filled by the algorithm.
Many thanks for your time
Best

Howdy. Sorry to say, but we're pretty much in maintenance mode and not really adding features.

Sure! We'd love to look at  PR.


Verifying Email Issue

There was an error about verifying email for the user when they create a new user.
I added this line to app/services/user_service.py :
await email_service.send_verification_email(new_user)

Issue was fixed in this commit : 7de8bf2


Bluetooth: Mesh: initialisation delay after disabling CONFIG_BT_DEBUG_LOG

It is found that we have to have enable CONFIG_BT_DEBUG_LOG=y
then only Mesh initialization happens within second otherwise it takes around 10+ seconds. This bug has introduced after latest new logging subsystem.
To Reproduce

flash samples/boards/nrf52/mesh/onoff_level_lighting_vnd_app in nRF52840_pca10056
with CONFIG_BT_DEBUG_LOG=n (it is by default disable as per current prj.conf)
Provision & configure it using nRFMesh App
Reset the Board & see device serial terminal

Here NODE takes 10+ seconds to print "Mesh initialized"
It will be good if we could avoid all type of DEBUG LOGs, so that we could avoid that 1 seconds delay as well as to improve the performance. DEBUG log is important only for development with actual product developers may want to disable it.

OK

@jhedberg
I think

git revert 4d94257162b22f37104e9f85238ed7c3486c5a1c

has no effect....still Mesh initialization takes some time.


Updating package.json version to 1.0.0

https://github.com/18F/cg-style/releases/tag/untagged-09fd74524e81ca959f28

Nice, looks good to me!


DNS CNAME Alias

Is it possible to do DNS Alias with WinAcme? I want to use a cloudflare domain I have as the Alias domain (i.e. provide a cloudflare API token to Winacme which is then used to authorize the certificate on multiple other domains).
I can't work out how to combine the DNS and the Cloudflare script to achieve this. I also want to do it from the command line.
I've read the documentation, but I think I need to combine some scripts. Sorry, quite new to this.

Yes it's possible. If you create a CNAME in your DNS win-acme will detect it and ask Cloudflare (or any other DNS plugin) to update the alias host name instead of the original one. So no, you don't need any scripting, and you don't need to explicitly specify that you're going to use an alias.

oh that's amazing! Is the cname "_acme-challenge"?
i.e. on external domain I make "_acme-challenge.domain.com" and give it a value of "_acme-challenge.REALdomain.com" and then this will use the API key against domain.com to make a certificate for REALdomain.com?

It works the other way around actually. If you want a certificate for realdomain.com, _acme-challenge.realdomain.com should point to your secondary domain, for example _acme-challenge.domain.com (but might also be abc.domain.com, Let's Encrypt doesn't really care). When processing the validation for realdomain.com, win-acme will see the CNAME and ask Cloudflare to update _acme-challenge.domain.com (or abc.domain.com) and you should get your certificate then.

ok, so I'm making progress but still not quite working. WHen I run this with the parameters it tries to update the zone the website will use rather than the alias zone. It's as if it's not adhering / seeing the _acme-challenge cname.
Do I need to make any records on the domain that I want to use for validation? I assume the client does that?
Really appreciate your help on this, thank you. If it would be easier for me to send you the actual domains on private message just let me know how. Thanks you.

Edit: Do I need to make _acme-challenge under every subdomain? e.g. _acme-challenge.www.domain.com and _acme-challenge.secure.domain.com

Every subdomain will be validated seperately, so yes.

Do I need to make any records on the domain that I want to use for validation?

No, that's done by the validation plugin.


Add Wasm projects

Pre-submission checklist:
Please check each of these after submitting your pull request:

[x] Are you only including a repo_url if your project is 100% open source? If so, you need to pick the single best GitHub repository for your project, not a GitHub organization.
[x] Is your project closed source or, if it is open source, does your project have at least 300 GitHub stars?
[x] Have you picked the single best (existing) category for your project?
[x] Does it follow the other guidelines from the new entries section?
[x] Have you added your SVG to hosted_logos and referenced it there?
[x] Does your logo clearly state the name of the project/product and follow the other logo guidelines?
[x] Does your project/product name match the text on the logo?
[x] Have you verified that the Crunchbase data for your organization is correct (including headquarters and LinkedIn)?
[ ] ~30 minutes after opening the pull request, the CNCF-Bot will post the URL for your staging server. Have you confirmed that it looks good to you and then added a comment to the PR saying "LGTM"?

My commit does't involve with logos of Pyodidie, KubeService Stack, and Sermant. Could someone tell me how to fix these errors? Thanks.
3:16:46 PM: FATAL: No cached entry, and Pyodide has issues with logo: pyodide.svg, This logo cannot be autocropped because of an unusual interaction with its viewbox. Please find a different logo or convert again from the original to SVG.
3:16:46 PM: FATAL: No cached entry, and KubeService Stack has issues with logo: kubeservice-stack.svg, This logo cannot be autocropped because of an unusual interaction with its viewbox. Please find a different logo or convert again from the original to SVG.
3:16:46 PM: FATAL: No cached entry, and Sermant has issues with logo: sermant.svg, SVG file embeds a png. Please use a pure svg file

Hi @castrojo,
can you assist me with this matter? Should I delete my branch to create a new pull request or is there another solution?
I'm planning to cover more Wasm projects this week. Thank you for your help.


[Removal]:

Hotspot Name
Chilly Hazelnut Tiger
Hotspot b58 Address
11xutHRRXTJ9AjqASJvzQDWL64EtkjK33NUPEfJXA4JiKT75Wi5
Discord Handle
MrBeinert #4595
Hotspot Manufacturer
Browan MerryIoT
Removal Reason
First, I do not know, if my hotspot is in this list, although I see Denylist reappearing in dashboard logs. Yesterday antenna was changed from 8dBi to 5,8dBi and network connection was changed from WiFi to Ethernet through PoE, obviously internal IP changed as well.
Modifications
Yes
Extra forwarders
No
Extra antennas
No
Additional Information
I hope someone could help. I ahve tried so many times without results. First, I am not a programmer, just medium level IT user, I do not know, if my hotspot is in this denylist, although I see Denylist reappearing and mentioned in dashboard logs. Yesterday antenna was changed from 8dBi to 5,8dBi and network connection was changed from WiFi to Ethernet through PoE, obviously internal IP changed as well. Not before, and not now is the hotspot witnessing or get witnessed by others, but the virtual server is set up in router as well as DHCP MAC adress binding to IP.

ChillyHazelnutTigerLog.pdf
.

Its  not on the denylist.


Problem with coverage on docker containers

We recently moved our pipeline from running on a VM to running on a docker container. After the move we started to have the below error.
Failed to parse result files: System.IO.DirectoryNotFoundException: Could not find a part of the path '/home/dockeragent/persistent_space/_work/1/s/test-output.xml'.
   at Interop.ThrowExceptionForIoErrno(ErrorInfo errorInfo, String path, Boolean isDirectory, Func`2 errorRewriter)
   at Microsoft.Win32.SafeHandles.SafeFileHandle.Open(String path, OpenFlags flags, Int32 mode)
   at System.IO.FileStream.OpenHandle(FileMode mode, FileShare share, FileOptions options)
   at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options)
   at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize)
   at System.Xml.XmlDownloadManager.GetStream(Uri uri, ICredentials credentials, IWebProxy proxy, RequestCachePolicy cachePolicy)
   at System.Xml.XmlUrlResolver.GetEntity(Uri absoluteUri, String role, Type ofObjectToReturn)
   at System.Xml.XmlTextReaderImpl.FinishInitUriString()
   at System.Xml.XmlTextReaderImpl..ctor(String uriStr, XmlReaderSettings settings, XmlParserContext context, XmlResolver uriResolver)
   at System.Xml.XmlReaderSettings.CreateReader(String inputUri, XmlParserContext inputContext)
   at System.Xml.XmlReader.Create(String inputUri, XmlReaderSettings settings)
   at Microsoft.TeamFoundation.TestClient.PublishTestResults.NUnitResultParser.ParseTestResultFile(TestRunContext runContext, String filePath)
   at Microsoft.TeamFoundation.TestClient.PublishTestResults.NUnitResultParser.<>c__DisplayClass1_0.<ParseTestResultFiles>b__0(String file)
   at System.Linq.Enumerable.SelectListIterator`2.MoveNext()
   at System.Linq.Enumerable.WhereEnumerableIterator`1.ToList()
   at Microsoft.TeamFoundation.TestClient.PublishTestResults.NUnitResultParser.ParseTestResultFiles(TestRunContext runContext, IList`1 resultFilePaths)
   at Microsoft.VisualStudio.Services.Agent.Worker.TestResults.Parser.ParseFiles(IExecutionContext executionContext, TestRunContext testRunContext, List`1 testResultsFiles, ITestResultParser testResultParser) in /home/vsts/work/1/s/src/Agent.Worker/TestResults/Parser.cs:line 57
##[warning]Failed to inline CSS styles in coverage reports. Error: [Errno 2] No such file or directory: '//home/dockeragent/persistent_space/_work/1/s/htmlcov'
Reading code coverage summary from '//home/dockeragent/persistent_space/_work/1/s/coverage.xml'
##[error]Unable to process command '##vso[codecoverage.publish codecoveragetool=Cobertura;summaryfile=//home/dockeragent/persistent_space/_work/1/s/coverage.xml;reportdirectory=//home/dockeragent/persistent_space/_work/1/s/htmlcov;]' successfully. Please reference documentation (http://go.microsoft.com/fwlink/?LinkId=817296)
##[error]File '//home/dockeragent/persistent_space/_work/1/s/coverage.xml' does not exist or is not accessible.

- generated Nunit xml file: /host/home/dockeragent/persistent_space/_work/1/s/test-output.xml -
- generated xml file: /host/home/dockeragent/persistent_space/_work/1/s/junit/test-results.xml -

---------- coverage: platform linux, python 3.8.10-final-0 -----------
Coverage HTML written to dir htmlcov
Coverage XML written to file /host/home/dockeragent/persistent_space/_work/1/s/coverage.xml

================ 834 passed, 208 skipped in 1681.84s (0:28:01) =================
Async Command Start: Publish test results
Async Command End: Publish test results
Finishing: Run tests with coverage

Needless to say, the files are there but it looks they are generate afterwards?
We were able to solve this by adding the flag --no-docker-discovery but now no coverage is uploaded (for some reason) and this is the output we are getting.
Skipping uploading of test results because --no-docker-discovery set.
Skipping uploading of coverage data.

- generated Nunit xml file: /host/home/dockeragent/persistent_space/_work/1/s/test-output.xml -
- generated xml file: /host/home/dockeragent/persistent_space/_work/1/s/junit/test-results.xml -

---------- coverage: platform linux, python 3.8.10-final-0 -----------
Coverage HTML written to dir htmlcov
Coverage XML written to file /host/home/dockeragent/persistent_space/_work/1/s/coverage.xml

================ 834 passed, 208 skipped in 1662.15s (0:27:42) =================
Finishing: Run tests with coverage

Any idea on what is going on and how we can fix it?

+1


Failed to create instance for type 'TestLiteDb.Program+Employee' from assembly

Hello here is again my small test program which is not working. Failign with following
Exception: Failed to create instance for type 'TestLiteDb.Program+Employee' from assembly
Stack Trace:
at LiteDB.Reflection.CreateInstance(Type type)
at LiteDB.BsonMapper.Deserialize(Type type, BsonValue value)
at LiteDB.BsonMapper.ToObject[T](BsonDocument doc)
at LiteDB.LiteCollection`1.d__27.MoveNext()
at TestLiteDb.Program.Main(String[] args) in d:\OneDrive\Edu\C#\TestLiteDb\TestLiteDb\Program.cs:line 54
at System.AppDomain._nExecuteAssembly(RuntimeAssembly assembly, String[] args)
at System.AppDomain.ExecuteAssembly(String assemblyFile, Evidence assemblySecurity, String[] args)
at Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly()
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
        [Serializable]
        public class Employee {
            [BsonId]
            public string EmployeeID { get; set; }
            public string FirstName { get; set; }
            public string LastName { get; set; }
            public List<string> Objects { get; set; }
            public byte[] Bytearray { get; set; }
        }

 using (var db = new LiteDatabase(@"filename=D:\LiteDb\MyData.db;journal=false")) {
                // Get a collection (or create, if not exits)
                var col = db.GetCollection<Employee>("customers");
                var timer = new Stopwatch();
                timer.Start();
                foreach (var index in Enumerable.Range(1, 10000)) {
                    var emp = new Employee() {
                        EmployeeID = "wyu" + index,
                        FirstName = "one",
                        LastName = "two",
                        //Bytearray = new byte[1 * 1000 * 1000]
                    };
                     col.Insert(emp);
                }
                var de = col.FindAll();

                foreach (var dd in de) { // Fails HERE
                    Console.Write(dd.EmployeeID);
                }

                timer.Stop();
                Console.WriteLine("Time taken {0} ms", timer.ElapsedMilliseconds);
            }
            Console.ReadKey();

I made the same example, using VS2015, Windows 10 x64 and works fine. I try using .NET 4, 4.5, 4,5.2 and all works fine (using LiteDB 1.0.3 from NuGet).
Time taken 3780 ms

This data file already exists?
Witch your windows/.NET version?
Did you try get source and run all Unit tests? Are working for you?

Hmm interesting. I have been runnign locally using a different project. You can try out my .sln from here http://1drv.ms/1PWBU18

aah ha found the problem, if I keep the class as internal class then it fails if I move the class out of the main class then it works. So its a bug ?

It's - classes must be public. It's not a bug, but to use IL fast instance classes must be public. Take a look on https://github.com/mbdavid/LiteDB/wiki/Object-Mapping

Sorry missed that. Thanks


Bad Gateway. 502 Error Code

The problem
I've tried local IP, hostname (homeassistant and hassio) as service IP.
I've added <IP_ADDRESS>/24 to trusted_proxies
I've configured external url for home assistant
Here is CF config

What version of Cloudflared has the issue?
4.1.1
What was the last working version of Cloudflared?
No response
What type of installation are you running?
Home Assistant OS
Add-on YAML Configuration
external_hostname: homeassistant.***
additional_hosts:
  - hostname: plex.***
    service: https://<IP_ADDRESS>:32400
  - hostname: bitwarden.***
    service: https://<IP_ADDRESS>:7277
tunnel_name: personal-homelab
log_level: debug
tunnel_token: *********

Anything in the logs that might be useful for us?
HomeAssistant Logs:
2023-04-13 13:35:27.500 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/aiohttp/web_protocol.py", line 332, in data_received
    messages, upgraded, tail = self._request_parser.feed_data(data)
  File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Invalid method encountered'"

Addon Logs:
2023-04-13T11:38:03Z ERR  error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: tls: first record does not look like a TLS handshake" cfRay=7b736ba8d88191e4-FRA ingressRule=0 originService=https://<IP_ADDRESS>:8123
2023-04-13T11:38:03Z ERR Request failed error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: tls: first record does not look like a TLS handshake" connIndex=0 dest=https://homeassistant.*****/favicon.ico ip=<IP_ADDRESS> type=http

Steps to reproduce the issue
Just follow the documentation
Additional information
services stored in additional_hosts works fine

There are a few things that stand out about your configuration that can lead to a problem.

You use both the configuration options of the add-on for a local tunnel, and the tunnel_token which is used for a remote managed tunnel and causes all other configuration options to be ignored. So you should first consider which type of connection you want to use. Take a look here.
You have configured the additional_hosts in the add-on and also the homeassistant service in the CF dashboard with https. The error messages seem to indicate that at least HA is not reachable via https, maybe that could already fix your problem.
You have added <IP_ADDRESS>/24 to the proxied hosts as linked in the instructions, however in the remote managed tunnel UI you are calling a local IP from your home network, this could in context (depending on network configuration) cause the proxy IP not to work. You would probably need to add <IP_ADDRESS>/32. Alternatively you can simply add homeassistant:8123 instead of the IP in the service call.

In general, I would recommend reading the information in the add-on for the documentation of the local managed tunnel as well as the information on the remote managed tunnel and deciding on one of the two.

Since it is not a bug, I am moving the issue to the discussions.


The first 3 Apis

New apis for Finding all the apps , finding a simple app and adding new apps to the array

done via #35


Add a hangman Game Project

Sir did you merge?
On Mon, 31 Oct 2022, 1:59 pm Sandeep Suman, @.***>
wrote:

Closed #89 https://github.com/SandeepKrSuman/project-gallery/issues/89
as completed via #91
https://github.com/SandeepKrSuman/project-gallery/pull/91.
—
Reply to this email directly, view it on GitHub
https://github.com/SandeepKrSuman/project-gallery/issues/89#event-7702026103,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWYGH7UBXX4PFVO7TACN2CTWF57PBANCNFSM6AAAAAARSKQGXU
.
You are receiving this because you were assigned.Message ID:
@.***
com>

✅ successfully merged in #91


Cannot run iptables when connected to this pod

[Enter feedback here]
Just wondering why I am unable to run iptables on the host
k logs pod/node-debugger-aks-systempool-x-vmss000001-ngwhn -n default
root@aks-systempool-x-vmss000001:/# iptables -S
iptables v1.6.1: can't initialize iptables table `filter': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.
root@aks-systempool-x-vmss000001:/# exit

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

ID: 3b81a147-db1c-b92f-88d1-6dd0991a72fe
Version Independent ID: f5a2c949-498f-5848-d89c-031d1a757120
Content: SSH into Azure Kubernetes Service (AKS) cluster nodes - Azure Kubernetes Service
Content Source: articles/aks/ssh.md
Service: container-service
GitHub Login: @mlearned
Microsoft Alias: mlearned

@rscottwatson thank you for your question. You are facing this issue because although kubectl debug starts a privileged container on your node it does not add NET_ADMIN capability to the container's security context. As a workaround, I have used  the kubectl-exec tool to SSH to the AKS node(s).
Steps I followed:

Install kubectl-exec
Replace SYS_PTRACE with NET_ADMIN in spec.containers[].securityContext.capabilities.add[] in the OVERRIDES variable in /usr/local/bin/kubectl-exec. Following is an illustration of the change made.
Before:

  ...
  #nsenter JSON overrrides
  OVERRIDES="$(cat <<EOT
  {
    "spec": {
      "nodeName": "$NODE",
      "hostPID": true,
      "containers": [
        {
          "securityContext": {
            "privileged": true
            "capabilities": {
               "add": [ "SYS_PTRACE" ]
          },
  ...

After:
  ...
  #nsenter JSON overrrides
  OVERRIDES="$(cat <<EOT
  {
    "spec": {
      "nodeName": "$NODE",
      "hostPID": true,
      "containers": [
        {
          "securityContext": {
            "privileged": true,
            "capabilities": {
               "add": [ "NET_ADMIN" ]
            }
          },
  ...

Run kubectl-exec

Hope this helps!


[WIP] testing doc-builder git action

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


Double startup on error

When starting my app without first starting keycloak I noticed an odd behavior:
mikael@SURFACE9PRO:~/projects/elivery/stack/runtime$ npm start

><EMAIL_ADDRESS>start
> plt-runtime start

[11:54:29.037] INFO (auth/25745): Typescript compilation completed successfully.
[11:54:29.077] INFO (auth/25745): OpenID discovery started for http://localhost:8080/realms/elivery-b2c/.well-known/openid-configuration
[11:54:29.087] WARN (auth/25745): OpenID discovery error #1 Error: connect ECONNREFUSED <IP_ADDRESS>:8080
[11:54:30.909] WARN (auth/25745): OpenID discovery error #2 Error: connect ECONNREFUSED <IP_ADDRESS>:8080
[11:54:34.191] WARN (auth/25745): OpenID discovery error #3 Error: connect ECONNREFUSED <IP_ADDRESS>:8080
[11:54:38.829] ERROR (auth/25745): Plugin did not start in time: 'platformaticService'. You may have forgotten to call 'done' function or to resolve a Promise
    err: {
      "type": "FastifyError",
      "message": "Plugin did not start in time: 'platformaticService'. You may have forgotten to call 'done' function or to resolve a Promise",
      "stack":
          FastifyError: Plugin did not start in time: 'platformaticService'. You may have forgotten to call 'done' function or to resolve a Promise
              at Timeout._onTimeout (/home/mikael/projects/elivery/stack/runtime/node_modules/avvio/lib/plugin.js:112:31)
              at listOnTimeout (node:internal/timers:573:17)
              at process.processTimers (node:internal/timers:514:7)
      "code": "AVV_ERR_PLUGIN_EXEC_TIMEOUT",
      "name": "FastifyError",
      "statusCode": 500
    }
Runtime exited before startup was completed, restarting
[11:54:40.244] INFO (auth/25745): Typescript compilation completed successfully.
[11:54:40.288] INFO (auth/25745): OpenID discovery started for http://localhost:8080/realms/elivery-b2c/.well-known/openid-configuration
[11:54:40.299] WARN (auth/25745): OpenID discovery error #1 Error: connect ECONNREFUSED <IP_ADDRESS>:8080
[11:54:41.407] INFO (auth/25745): Typescript compilation completed successfully.
[11:54:41.448] INFO (auth/25745): OpenID discovery started for http://localhost:8080/realms/elivery-b2c/.well-known/openid-configuration
[11:54:41.456] WARN (auth/25745): OpenID discovery error #1 Error: connect ECONNREFUSED <IP_ADDRESS>:8080
[11:54:42.185] WARN (auth/25745): OpenID discovery error #2 Error: connect ECONNREFUSED <IP_ADDRESS>:8080
[11:54:42.651] WARN (auth/25745): OpenID discovery error #2 Error: connect ECONNREFUSED <IP_ADDRESS>:8080
[11:54:44.802] WARN (auth/25745): OpenID discovery error #3 Error: connect ECONNREFUSED <IP_ADDRESS>:8080
[11:54:45.114] WARN (auth/25745): OpenID discovery error #3 Error: connect ECONNREFUSED <IP_ADDRESS>:8080
[11:54:50.052] ERROR (auth/25745): Plugin did not start in time: 'platformaticService'. You may have forgotten to call 'done' function or to resolve a Promise
    err: {
      "type": "FastifyError",
      "message": "Plugin did not start in time: 'platformaticService'. You may have forgotten to call 'done' function or to resolve a Promise",
      "stack":
          FastifyError: Plugin did not start in time: 'platformaticService'. You may have forgotten to call 'done' function or to resolve a Promise
              at Timeout._onTimeout (/home/mikael/projects/elivery/stack/runtime/node_modules/avvio/lib/plugin.js:112:31)
              at listOnTimeout (node:internal/timers:573:17)
              at process.processTimers (node:internal/timers:514:7)
      "code": "AVV_ERR_PLUGIN_EXEC_TIMEOUT",
      "name": "FastifyError",
      "statusCode": 500
    }
[11:54:50.429] WARN (auth/25745): OpenID discovery error #4 Error: connect ECONNREFUSED <IP_ADDRESS>:8080
FATAL ERROR: v8::FromJust Maybe value is Nothing
----- Native stack trace -----

 1: 0xca5580 node::Abort() [node]
 2: 0xb78101 node::OOMErrorHandler(char const*, v8::OOMDetails const&) [node]
 3: 0xecb5d0 v8::api_internal::FromJustIsNothing() [node]
 4: 0xd99e0d  [node]
 5: 0xc1bc48 node::Environment::RunAndClearNativeImmediates(bool) [node]
 6: 0xc1c6f6  [node]
 7: 0x188ae53  [node]
 8: 0x189f8cb  [node]
 9: 0x188bb77 uv_run [node]
10: 0xbbbb83 node::SpinEventLoopInternal(node::Environment*) [node]
11: 0xda020e node::worker::Worker::Run() [node]
12: 0xda05f9  [node]
13: 0x7f7c1e8cbac3  [/lib/x86_64-linux-gnu/libc.so.6]
14: 0x7f7c1e95d850  [/lib/x86_64-linux-gnu/libc.so.6]
Aborted

Getting an error after 3 retries is expected, but as you can see a second attempt is done and it looks like there are two instances of the app starting the second time.
I'm also not used to see a v8 stack dump at the end.

Now plt automatically restart in case of an error. What should not happen is the OOM.
What version of node are you using?

I'll take a look at the multiple restartsz

This error is still present in 1.36.1 with node v20.11.1, but it works fine in node v20.12.2
mikael@SURFACE9PRO:~/projects/elivery/stack/runtime$ npm start

><EMAIL_ADDRESS>start
> plt-runtime start

[14:49:43.134] INFO (auth/2331): Typescript compilation completed successfully.
[14:49:43.279] INFO (auth/2331): OpenID discovery started for http://localhost:8080/realms/elivery-b2c/.well-known/openid-configuration
[14:49:43.291] WARN (auth/2331): OpenID discovery error #1 Error: connect ECONNREFUSED <IP_ADDRESS>:8080
[14:49:45.252] WARN (auth/2331): OpenID discovery error #2 Error: connect ECONNREFUSED <IP_ADDRESS>:8080
[14:49:47.478] WARN (auth/2331): OpenID discovery error #3 Error: connect ECONNREFUSED <IP_ADDRESS>:8080
[14:49:52.755] ERROR (auth/2331): Plugin did not start in time: 'platformaticService'. You may have forgotten to call 'done' function or to resolve a Promise
    err: {
      "type": "FastifyError",
      "message": "Plugin did not start in time: 'platformaticService'. You may have forgotten to call 'done' function or to resolve a Promise",
      "stack":
          FastifyError: Plugin did not start in time: 'platformaticService'. You may have forgotten to call 'done' function or to resolve a Promise
              at Timeout._onTimeout (/home/mikael/projects/elivery/stack/runtime/node_modules/avvio/lib/plugin.js:112:31)
              at listOnTimeout (node:internal/timers:573:17)
              at process.processTimers (node:internal/timers:514:7)
      "code": "AVV_ERR_PLUGIN_EXEC_TIMEOUT",
      "name": "FastifyError",
      "statusCode": 500
    }
Runtime exited before startup was completed, restarting
[14:49:55.096] INFO (auth/2331): Typescript compilation completed successfully.
[14:49:55.185] INFO (auth/2331): OpenID discovery started for http://localhost:8080/realms/elivery-b2c/.well-known/openid-configuration
[14:49:55.208] WARN (auth/2331): OpenID discovery error #1 Error: connect ECONNREFUSED <IP_ADDRESS>:8080
[14:49:56.235] INFO (auth/2331): Typescript compilation completed successfully.
[14:49:56.298] INFO (auth/2331): OpenID discovery started for http://localhost:8080/realms/elivery-b2c/.well-known/openid-configuration
[14:49:56.309] WARN (auth/2331): OpenID discovery error #1 Error: connect ECONNREFUSED <IP_ADDRESS>:8080
[14:49:57.173] WARN (auth/2331): OpenID discovery error #2 Error: connect ECONNREFUSED <IP_ADDRESS>:8080
[14:49:57.851] WARN (auth/2331): OpenID discovery error #2 Error: connect ECONNREFUSED <IP_ADDRESS>:8080
[14:49:59.643] WARN (auth/2331): OpenID discovery error #3 Error: connect ECONNREFUSED <IP_ADDRESS>:8080
[14:50:00.244] WARN (auth/2331): OpenID discovery error #3 Error: connect ECONNREFUSED <IP_ADDRESS>:8080
[14:50:04.741] ERROR (auth/2331): Plugin did not start in time: 'platformaticService'. You may have forgotten to call 'done' function or to resolve a Promise
    err: {
      "type": "FastifyError",
      "message": "Plugin did not start in time: 'platformaticService'. You may have forgotten to call 'done' function or to resolve a Promise",
      "stack":
          FastifyError: Plugin did not start in time: 'platformaticService'. You may have forgotten to call 'done' function or to resolve a Promise
              at Timeout._onTimeout (/home/mikael/projects/elivery/stack/runtime/node_modules/avvio/lib/plugin.js:112:31)
              at listOnTimeout (node:internal/timers:573:17)
              at process.processTimers (node:internal/timers:514:7)
      "code": "AVV_ERR_PLUGIN_EXEC_TIMEOUT",
      "name": "FastifyError",
      "statusCode": 500
    }
[14:50:05.809] ERROR (auth/2331): Plugin did not start in time: 'platformaticService'. You may have forgotten to call 'done' function or to resolve a Promise
    err: {
      "type": "FastifyError",
      "message": "Plugin did not start in time: 'platformaticService'. You may have forgotten to call 'done' function or to resolve a Promise",
      "stack":
          FastifyError: Plugin did not start in time: 'platformaticService'. You may have forgotten to call 'done' function or to resolve a Promise
              at Timeout._onTimeout (/home/mikael/projects/elivery/stack/runtime/node_modules/avvio/lib/plugin.js:112:31)
              at listOnTimeout (node:internal/timers:573:17)
              at process.processTimers (node:internal/timers:514:7)
      "code": "AVV_ERR_PLUGIN_EXEC_TIMEOUT",
      "name": "FastifyError",
      "statusCode": 500
    }

The stack dump is gone (yay!)
The double-instance-on-restart is still there as you can see from the duplicate OpenID discovery error #1/#2/#3 during the second start
Since upgrading node fixed it I think it's best to keep it closed. Just wanted to add more info for posterity


DE Update. Extension is fully translated in German

4 Commits in total [Listed Below]
Issue With The Idea: https://github.com/YunzheZJU/holo-schedule/issues/64
Followed the steps given in the issue. All file changes and commits are viewable below or in my profile or in the issue. No need to link everything again here.
Because the owner made me a own branch, i will pull request it over there, will be happily awaiting when its in the master branch

I want to say sorry because I missed a file to modify which may result in lacking of time related translations. It is recomended to include these changes to properly display the time and use your locales.

Will do, thanks. How does that work? Should i just push it to my branch again and do a new pull request?

Okay so i pushed all the changes. Hope that works out. Im super happy to contribute a small thing here. Let me know if there's any other changes.
Im not a complete noob with git but im not sure how this works exactly. Can you take over the changes in the master branch without me making a new Pull Request?

Good job and we can check them in the 'Changes' tab in this page. Most of my suggestions have been resolved.
I have set the target branch of this pr to master and will do a 'squash merge' after everything is fine. This means all your commits would be merged into one on the master, with the author set to your name.
I think you must be a multi-language talent! I sincerely appreciate your contributions!

Super Cool! Thanks. Im always down to contribute to stuff that i like and im able to.

Thank you! One small thing is that There seems to be one comment from me left untouched in README.md, would you please have a check?

Done, sorry didn't see that. 'De' has been changed to 'Deutsch' everywhere now. I accidently oversaw it in the english readme

I have tested your branch locally and it behaves just like what I expect. 👍 I'll merge it as long as the minor things above are resolved.

Ill wait for the final push, because i don't see what you mean there [https://github.com/YunzheZJU/holo-schedule/pull/65#discussion_r614204605]
added a screenshot from my editor

Done bro, let me know if there is anything else :D

Done bro, let me know if there is anything else :D

Thank you again for your great contribution in this project's internationalization. I've never thought anyone would be interested in this work and you made me think of all the things I've done as valuable.
Since everything in this thread have been resolved, I'll squash and merge this pull-request into master. It's quite kind of you to discuss patiently and I'm looking forward to your future contribution. See you again!
Have a nice day!


Create SECURITY.md

hello,
it is important for our company that we have a list of safety related issues. this is required for iso 27001 8.28

thanks


feat(k8s/advanced-deployment): allow standard users to see and use advanced deployment feature

Close EE-446

Close https://github.com/portainer/portainer/issues/5179


Project thread update bot sends requests for updates for projects that aren't started

Description

See this notification: https://github.com/WordPress/openverse/issues/2344#issuecomment-1581694253
The project is neither started nor has it even existed for 14 days.
Fix
Fix the check for the project status and add a check for project age to ensure that it's even old enough (and was actually started long enough ago) to require a reminder.

@sarayourfriend the project has the In RFC status (perhaps erroneously) so the only issue is checking the project date. I'll get a PR up now!

Ah! It didn't have anything else filled out (lead, dates, etc) and I didn't even check the status on the project board, apologies.


lynx: add patch for CVE-2021-38165

Co-authored-by: nixinator<EMAIL_ADDRESS>Co-authored-by: John Bargman<EMAIL_ADDRESS>
Motivation for this change
Fixes the security vulnerability in Lynx that resulted in this meltdown on the mailing list. Code was audited by @DarthPJB
https://lists.nongnu.org/archive/html/lynx-dev/2021-08/msg00007.html
Patch Source: https://git.alpinelinux.org/aports/tree/main/lynx/CVE-2021-38165.patch
Things done

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

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

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

[x] Fits CONTRIBUTING.md.

lists.nongnu.org/archive/html/lynx-dev/2021-08/msg00007.html

Referencing the mail with the patch you didn't use is confusing. Please add the correct reference.

You seem to have added unrelated commits.

I have rebased with the suggested changes so far and added co-authorship to mweinelt. Thanks for the guidance!

@ofborg build lynx


Replace hashicorp/go-version due to license

In the e2e tests we use https://github.com/hashicorp/go-version which is
a fine package but whose license is not auto-allowed by CNCF.
In order to be as much friendly as possible with CNCF, we should replace
this dependency with something with a auto-allowed license, like
https://github.com/aquasecurity/go-version.
See issue #83

/lgtm
/approve


App reports bug

What happened?
Boundary error:
Error: Non-negative timestamp expected
Steps to reproduce

step one...
step two...

What OS are you seeing the problem on?
Window
Relevant log output
Boundary error:
Error: Non-negative timestamp expected
App Version: vibe 2.6.6
Commit Hash: 8244a16
Arch: x86_64
Platform: windows
Kernel Version: 10.0.26100
OS: windows
OS Version: 10.0.26100
Cuda Version: n/a
Models: ggml-medium.bin
Default Model: "C:\\Users\\baba7\\AppData\\Local\\github.com.thewh1teagle.vibe\\ggml-medium.bin"
Cargo features: vulkan

{
    "avx": {
        "enabled": true,
        "support": true
    },
    "avx2": {
        "enabled": true,
        "support": true
    },
    "f16c": {
        "enabled": true,
        "support": true
    },
    "fma": {
        "enabled": true,
        "support": true
    }
}

Thanks for report! looks duplicate of https://github.com/thewh1teagle/vibe/issues/408


Networking metrics to add to Prometheus

To add:

Number of records in the storage.
Number of active iterative queries.
Number of active RPC queries for which we're waiting for an answer.

I re-purposed this issued as a more generic "networking metrics to add" rather than Kademlia-specific.

cc https://github.com/libp2p/rust-libp2p/issues/1701


When refactoring code give the ability to create new files and folders from the suggested code

Given I am refactoring code.
When the suggestion is to create new classes
And the user approves the suggestions.
Then the new classes are created in an appropriate folder, namespace and file.

Duplicate of #45


Added new ticket api

Resolved issues:
resolves #2484
Description of changes:
Added new apis to request session tickets.
Call-outs:
s2n has an s2n_add_overflow function, but it is only for uint32_t numbers so I could not use it.
Testing:
Unit tests.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Tests are failing because of current codebuild issues


Bump rxdart version

Is there a reason why rxdart version is semi-pinned? If not, can it be upgraded to 0.28.0? It's preventing me from using a newer version of custom_lint.

Would that work? https://github.com/braverhealth/phoenix-socket-dart/pull/95

Yes, it should. Thank you very much!

Saw you merged the pr; do you mind doing a point release?

Done!

I'm writing this for posterity...I made a mistake with this issue, stemming from a misunderstanding of pre-1.0.0 Semantic Versioning. ^0.27.0 is not the same as ">=0.27.0 <1.0.0", so the version range that was there previously may be more appropriate, as ^0.27.0 doesn't fix my issue of compatibility with rxdart version 0.28.0, so I had to do a dependency override anyway.


Missing prefix for Vodafone Uganda and Equitel Kenya

Uganda (+256) Vodafone - http://mynumber.vodafone.co.ug - Prefix: 0723
Kenya (+254) Equitel - http://www.businessdailyafrica.com/Corporate-News/-/539550/2486734/-/vbubydz/-/index.html - Prefix: 0763

Thank you for your mail
Please see phone number parser demo
https://rawgit.com/googlei18n/libphonenumber/master/javascript/i18n/phonenumbers/demo-compiled.html
For the Uganda case, I entered
+256723123456 it returned as a valid number
or<PHONE_NUMBER> with country code UG also works
Result
Parsing Result:
{"country_code":256,"national_number":723123456,"raw_input":"0723123456","country_code_source":20,"preferred_domestic_carrier_code":""}
Validation Results:
Result from isPossibleNumber(): true
Result from isValidNumber(): true
Result from isValidNumberForRegion(): true
Phone Number region: UG
Result from getNumberType(): MOBILE
Formatting Results:
E164 format: +256723123456
Original format: 0723 123456
National format: 0723 123456
International format: +256 723 123456
Out-of-country format from US: 011<PHONE_NUMBER>56
Out-of-country format from Switzerland: 00<PHONE_NUMBER>56
AsYouTypeFormatter Results
Char entered: 0 Output: 0
Char entered: 7 Output: 07
Char entered: 2 Output: 072
Char entered: 3 Output: 0723
Char entered: 1 Output: 0723 1
Char entered: 2 Output: 0723 12
Char entered: 3 Output: 0723 123
Char entered: 4 Output: 0723 1234
Char entered: 5 Output: 0723 12345
Char entered: 6 Output: 0723 123456
===================================
For Kenya also the demo is passing the range as valid, using the number
+254763123456
Result
Parsing Result:
{"country_code":254,"national_number":763123456,"raw_input":"+254763123456","country_code_source":1,"preferred_domestic_carrier_code":""}
Validation Results:
Result from isPossibleNumber(): true
Result from isValidNumber(): true
Phone Number region: KE
Result from getNumberType(): MOBILE
Formatting Results:
E164 format: +254763123456
Original format: +254 763 123456
National format: 0763 123456
International format: +254 763 123456
Out-of-country format from US: 011<PHONE_NUMBER>56
Out-of-country format from Switzerland: 00<PHONE_NUMBER>56
AsYouTypeFormatter Results
Char entered: + Output: +
Char entered: 2 Output: +2
Char entered: 5 Output: +25
Char entered: 4 Output: +254
Char entered: 7 Output: +254 7
Char entered: 6 Output: +254 76
Char entered: 3 Output: +254 763
Char entered: 1 Output: +254 763 1
Char entered: 2 Output: +254 763 12
Char entered: 3 Output: +254 763 123
Char entered: 4 Output: +254 763 1234
Char entered: 5 Output: +254 763 12345
Char entered: 6 Output: +254 763 123456
Thanks
Brendan
On 5 June 2015 at 09:48, Charles Kithika<EMAIL_ADDRESS>wrote:

Uganda (+256) Vodafone - http://mynumber.vodafone.co.ug - Prefix: 0723
Kenya (+254) Equitel -
http://www.businessdailyafrica.com/Corporate-News/-/539550/2486734/-/vbubydz/-/index.html

Prefix: 0763

—
Reply to this email directly or view it on GitHub
https://github.com/googlei18n/libphonenumber/issues/712.

--
Brendan Marry | Google International Product Manager EMEA |
<EMAIL_ADDRESS>| +41 79 763 37 13
This email may be confidential or privileged.  If you received this
communication by mistake, please don't forward it to anyone else, please
erase all copies and attachments, and please let me know that it went to
the wrong person.  Thanks.


Support Pull-to-Refresh on the News sections

It's really useful to check news updates with pull-to-refresh.
Relates to #97

So why it's closed now again?

It's fixed and already in the master.

Nice! Thanks! Quite good reason to close issue :)

:)


[ENH] IPython Notebook representations of MNE objects

Add HTML rendering of the MNE objects using _repr_html_ method.
TODO list:

[x] Info #6846 #9161

[x] BaseRaw #9161 #9172

[ ] Epochs

[ ] Evoked

[ ] SourceEstimate

I took the liberty to add SourceEstimate to the list, too :)

This is cool! :)


Bug: Pull request comment box CSS is hiding upload attachment

This is not a bug. The extension removes the button because you can also just use drag and drop. I was not the one making the decision, but I also don't have a problem with it. Duplicate of #1191.

@shroudedcode Oops, sorry about the dup! Sorry I searched for issues via "attachment" and "image" keywords and those issues didn't come up.


Watchdog Test timer test fix

Need to wait for the watchdog object to get created on watchdog timer injection

fixed.


Use fedoraproject published EC2 images

Previously a very complex, manual, and failure-prone import_images stage was required to bring raw images into EC2.  Primarily this was necessary because beta images aren't published on EC2 by the fedoraproject.  However, since the original implementation, CI operations against rawhide have largely supplanted the need to support testing against the beta images.  This means the 'import_images' stage can be completely dropped, and the 'base_images' stage can simply source images (including rawhide if necessary) published by the Fedora project.

[ ] Test images in podman CI to confirm Debian pasta apparmor fix

Looks like this works for x86_64 and arm64.  Rawhide support in EC2 is a possibility as well (though not currently needed).  Leaving this as a draft until the big question can be answered: "Do/Will we ever need Beta Fedora CI VMs in EC2"?
The alternative is migrating the import_images stage to use Packer for only a small reduction in complexity.

If I'm understanding this PR correctly, don't you also need to remove all the IMPORT_IMG_SFX and import_images stuff from Makefile?

don't you also need to remove all the

Oh, I thought I had.  Maybe I missed committing it or something.  In either case, my main quandary is knowing if we really will never again need to incorporate beta CI VM images.  If so, I can move this simplification forward.  If not, then I need to take the work for my Jira card in another direction.  Perhaps this is something I should bring to the team.

Force-push: Commit almost lost Makefile changes.

Once again, I recommend .git/hooks/pre-push:
#!/bin/bash
#
# 2024-01-25 esm
#

# FIXME: figure out if this is a PR push or a tag push
#
imgsfx=$(<IMG_SFX)

imgsfx_history=.imgsfx.history
if [[ -e $imgsfx_history ]]; then
    if grep -q "$imgsfx" $imgsfx_history; then
        echo "FATAL: $imgsfx has already been used" >&2
        echo "Please rerun 'make IMG_SFX'" >&2
        exit 1
    fi
fi

echo $imgsfx >>$imgsfx_history

Sorry for not being clear, this is an experimental PR.  It's far from perfect on purpose, I just wanted to see if it was possible to pickup the fedoraproject published AMIs.

You're pre-push hook is a neat hack, I wonder if it could be made to work with pre-commit (the app)?  Either way, it would be nice if it were in the repo. (and README) so everyone knows to use it.  I had completely forgotten about it.

I wonder if it could be made to work with pre-commit

Oh! Actually that's not very hard at all, just a bit of yaml and some minor script changes.  Opened https://github.com/containers/automation_images/pull/364

20240701t155130z-f40f39d13
20240620t153000z-f40f39d13 ⇑ (built in #361)

debian
prior-fedora
fedora
fedora-aws
rawhide

kernel
6.9.7-1
6.9.6-100
6.9.7-200
6.9.6-200
6.8.5-301

6.8.12-1 ⇑
6.9.4-100 ⇑
6.9.5-200 ⇑
6.9.4-200 ⇑

grub2-common
2.12-2
2.06-121
2.06-123
2.06-123
2.06-123

2.06-120 ⇑

aardvark-dns
1.4.0-6
1.11.0-1
1.11.0-1
1.11.0-1
1.11.0-1

1.4.0-5.1 ⇑

buildah
1.33.7+ds1-1
1.36.0-1
1.36.0-1
1.36.0-1
1.36.0-1

1.35.4-1 ⇑

1.35.4-1 ⇑

container-selinux
?
2.232.1-1
2.232.1-1
2.232.1-1
2.232.1-1

2.231.0-1 ⇑

docker-ce
5:27.0.3-1~debian.12~bookworm
?
?
?
?

5:26.1.4-1~debian.12~bookworm ⇑

golang
2:1.22~3
1.21.11-1
1.22.4-1
1.22.4-1
1.22.4-4

1.22.4-3 ⇑

passt
2024-06-24
2024-06-07
2024-06-24
2024-06-24
2024-06-24

2024-06-07 ⇑
2024-05-10 ⇑
2024-06-07 ⇑
2024-06-07 ⇑
2024-06-07 ⇑

systemd
256.1-2
254.13-1
255.8-1
255.8-1
256.1-3

256.1-1 ⇑

255.7-1 ⇑
255.7-1 ⇑

Great, thanks.  Hopefully the new passt (pasta?) package will resolve the old apparmor problem.  Giving it a try in https://github.com/containers/podman/pull/23157

@cevich is this ready to merge? We have a lot of auto-imgs PRs in flight, and I would very much like to get this in, then my local-registry PRs, then the Windows one.

is this ready to merge?

I guess?  I s'pose https://github.com/containers/podman/pull/23157 does show all the Debian tests passing.  Since you feel strongly that the PM MacOS failure is a flake, I guess this can go in?  I'll un-draft it and let you merge in the order you feel appropriate.


asyncComputed

Have you tried vue-async-computed ? It is incredibly awesome, because it allows asynchronous computed properties. Among other things, this makes it incredibly easy to source your Vue data from AJAX calls. I will try to convince you that this feature is SO good, that it is worthy of including in Vue's core instead of being relegated to this lowly plugin.
Code sample
Here's an example application that uses two properties to seamlessly interact with the server. Actions are "dispatched" by setting properties. (I clump mine in a object called "active".) This flags them as dirty, causing Vue to automatically re-compute any async properties that depend on that property.
Here, $vm.active.lang is a read-write property containing the current language. The $vm.i18n property contains all the i18n strings. Changing $vm.active.lang causes Vue to pull the appropriate language file from the server and update the text on the page. Is that simple or what?
<template>
  <p>{{i18n.hello}}, {{CurrentUser.name}}!</p>
</template>

<script>
const Ajax = (url, opts) => window.fetch(url, opts).then((response) => response.json())

let App = new Vue({
  el: '#app',
  data () {
    return {
      active: {
        lang: 'en'
      }
    }
  },
  asyncComputed: {
    i18n () {
      return Ajax('/lang/' + this.active.lang)
    },
    CurrentUser () {
      return Ajax('/logged_in_user.json', {credentials: 'include'})
    }
  }
})
</script>

I also left in some code that fetches the current user from the server so we can greet the user by name.
How will it make current work-arounds straightforward?
Right now, it requires conceiving the idea of "async properties", searching the web to see if someone has done it, and then using this plugin. But I really think it is extremely elegant and intuitive, and having it baked into Vue's core and documented in the Vue guide would encourage more people to think, "Oh, this is a really great way to get data from my server into Vue" and would simplify a lot of people's spaghetti code, which would make the world a better place.
What potential bugs and edge cases does it help to avoid?
Many beginners (and even experts) still have not fully committed to using a Flux-architecture framework, or are dealing with horrendous legacy applications and "vueifying" pieces of it as we go. But it is well established that this unidirectional data flow from server to client is a great idea and simplifies state management and reduces spaghetti code. Adding native support for asynchronous properties would enable and promotes a very simple, declarative unidirectional server-to-client data flow that has the advantage of being easily injected into existing legacy code without having to learn a new framework.
I'm sure there are other uses for asynchronous computed properties too (dispatching a long-running task to a WebWorker comes to mind) but I've only used it for AJAX so that's the example I've used.

I like the idea... maybe we can simply make normal computed accept returning a Promise.

As long as that doesn't break existing code, I'm all for fewer keywords/names to remember.

@HerringtonDarkholme very good points. After thinking about it, I almost think all these issues you mentioned would be better solved with Rx...
With vue-rx the original example can be written as (simplified for the sake of discussion):
new Vue({
  data: {
    lang: 'en'
  },
  subscriptions () {
    return {
      i18n: this.$watchAsObservable('lang')
        .switchMap(lang => Rx.Observable.fromPromise(fetch('/lang/' + lang)))
        .startWith({
           // default i18n settings...
        })
    }
  }
})

The Rx version is obviously more verbose than the simple Promise version, but here we get almost everything @HerringtonDarkholme listed: default value, throttling and side-effect subscriptions (which in most cases eliminate the need for detecting when the Promise resolves).
If fetching is commonly used, with a little helper the above can be further simplified:
// long name just to precisely describe what it does
Vue.prototype.$reactivelyFetchAsObservable = function (urlOrGetter) {
  return this
    .$watchAsObservable(urlOrGetter)
    .switchMap(url => Rx.Observable.fromPromise(fetch(url))
}

new Vue({
  data: {
    lang: 'en'
  },
  subscriptions () {
    return {
      i18n: this.$reactivelyFetchAsObservable(() => {
        return 'lang/' + this.lang
      })
    }
  }
})

To sum up, I think while the async computed pattern is simple and elegant for the basic use case, it may not be sufficient to deal with the full scale complexity of async operations. While we can shoehorn the async computed pattern to deal with these cases one by one, at that stage you'd probably be better off just going with Rx.
So unfortunately, I'm closing this. Note this is not saying that this is a bad idea - I think it's still a good idea to let the vue-async-computed evolve on its own and maybe land on a good balance, but it's probably not the best idea to do that in core.

To get the example above to work properly you have to add a .pluck('newValue') after the $watchAsObservable.
Vue.prototype.$reactivelyFetchAsObservable = function (urlOrGetter) {
  return this
    .$watchAsObservable(urlOrGetter)
    .pluck('newValue')
    .switchMap(url => Rx.Observable.fromPromise(fetch(url))
}

It's a very common case to have dependent properties, for instance:
Dropdown A.
Dropdown B which values depends on selected value of dropdown A
Input C which might be defaulted based on selected value of Dropdown B.
Now imagine that all these dependent values are retrieved from async calls from rest API.
I can't use computed anymore since they are all asynchronous. And yes, I can implement it with rxjs, but that's not as trivial as the computed way.
While I was learning vue, that was one of the first issues I was trying to solve and when I found this solution, I couldn't understand it. After a few days I came back to this very same issue and now with more knowledge of ReactiveX I can understand the solution.
OK, my point is:
Shouldn't we have a computed style way to solve this very common problem? It would be less verbose, more readable and it won't require additional knowledge.
Probably that's not for vue core library, but it might be in vue-rx, or even in this third party library using vue-rx behind the scenes. It could provide a really elegant way to solve this problem.

A quick search on GitHub. https://github.com/foxbenjaminfox/vue-async-computed
Use it on your own risk.

Sorry, probably I wasn't clear enough, but that library was the one that I first found and it made me wondering why such scenario wasn't handled in a similar way in vue core or any official vue library. I was expecting that at some point a similar solution would be in vue or any of its official libraries.

Please refer to https://github.com/vuejs/vue/issues/6004#issuecomment-312404196
We strive to keep API surface small.

why such scenario wasn't handled in a similar way in vue core or any official vue library

asyncComputed can be implemented in user land without hack. It isn't hard for users to use it in existing projects.
I would also argue that a half-baked asyncComputed wouldn't suffice users' need.  Fully implementing it might introduces no simpler concepts nor smaller code size for async computed than for RX and its vue binding.

Drive-by impressions:
Coming over from Aurelia and Durandal I've found this to be bizarre. I expected it to just work.
Surely updating data from API responses queried based on user input is a common use-case for computed properties.
Would the cache of a computed not be desired in these types of uses? Why would you be forced to re-roll all these features from scratch when you have a structure which updates based on input  and caches the results until they change again (exactly what you need for an async query)?

Your use case might be done without async at all. Probably you can store value in another field and defining one computed property to extract value.

Seen a few suggestions to use a hook once at startup to fill data. In contrast to my experience where most use-cases for these types of updating properties are the other way around. You're often querying small sets out of much larger data-sets which would be impractical to load at startup.

After reading this discussion I went for RXjs to try out the async computed subscriptions: https://github.com/cpietsch/harvest/blob/master/src/components/Dashboard.vue#L211
When handling 2 or more async properties you have to use mergeMap().

+1 for a native solution

how can user declare a default value when promise is not resolved?

computed: {
  syncProperty () { return 'foo' },
  promisedProperty () { return Promise.resolve('foo') }, // default is undefined
  promisedPropertyWithDefault: {
    value () { return Promise.resolve('foo') },
    default: 'bar'
  },
  async asyncProperty () { return await Promise.resolve('foo') },
  asyncPropertyWithDefault: {
    async value () { return await Promise.resolve('foo') },
    default: 'bar'
  }
}

should vue support a builtin throttle promise to handle events like keychange, mousemove?

even if a promise-based implementation of throttled events makes sense in particular use cases, imho it's tangential to the main use case, which is asynchronously fetching data. way to go: provide a core implementation with this in mind, then see what other clever and unexpected (but semantically correct) uses people find for it

should vue support a builtin callback when certain promise is resolved?

can you provide a scenario where this is necessary - as opposed to normal vue-agnostic use of promises?

how to inspect whether the async property is resolving or resolved?

default value + callback on resolve is good enough for the core minimal use case
overall vue-async-computed is a step in the right direction, and core support for this would be a major step forward, seeing how promises and async/await are now a core part of our language workflow

In my @tozd/vue-observer-utils package I have $await helper with a very simple (basic) implementation:
const awaitResultsMap = new WeakMap();

function $await(promise) {
  if (!awaitResultsMap.has(options.key)) {
    const dep = new Vue.util.Dep();
    dep.depend();
    promise.then((result) => {
      awaitResultsMap.set(options.key, result);
      dep.notify();
    });
  }
  return awaitResultsMap.get(options.key);
};

It works pretty well to bridge Promises and reactivity in Vue.

@yyx990803 The package is mature enough now to merge into the core, yeah?

Also curious if your views have changed on this since your last review of the approach?

Same, being able to use async computed would be useful...
What about it?

just use watch instead of computed
const searchQuery = ref('');
watch(searchQuery, runSearch);

async function runSearch() {
  return await apiCall();
}

@aryehbeitz Are you sure watch calls wait runSearch() internally? I do not think so.


MenuItem children are vertically centered with parent instead of top-aligned [11-preview6]

Describe the bug
Seems to be a regression with vertical alignment when moving from 11-preview5 to 11-preview6 / nightly. Horizontal alignment seems correct.
To Reproduce

Create project with Mvvm template, use FluentTheme (default).
Use this XAML in MainWindow.axaml:

<Grid RowDefinitions="auto,*">
    <Menu>
        <MenuItem Header="First">
            <MenuItem Header="First.A" />
            <MenuItem Header="First.B">
                <MenuItem Header="First.B.1" />
                <MenuItem Header="First.B.2" />
                <MenuItem Header="First.B.3" />
                <MenuItem Header="First.B.4" />
                <MenuItem Header="First.B.5" />
                <MenuItem Header="First.B.6" />
            </MenuItem>
            <MenuItem Header="First.C" />
        </MenuItem>
        <MenuItem Header="Second">
            <MenuItem Header="Second.A" />
            <MenuItem Header="Second.B" />
        </MenuItem>
    </Menu>
</Grid>

Run app and check menu.
Upgrade app to preview6 and re-check menu.

Screenshots
11-preview5 shows expected alignment:

11-preview6 (and 11.0.999-cibuild0032155-beta nightly) shows vertical centering on parent for child items:

Desktop (please complete the following information):

OS: Win10
Version 11-preview5 -> 11-preview6 / 11.0.999-cibuild0032155-beta

Additional context
Horizontal alignment, while ok with only FluentTheme here, also suffers from horizontal centering in FluentAvalonia in 2-preview6. I will post an additional issue over there.

Related to #10662


Missing trailing "," Predicting_bike_sharing_data.ipynb

Latest version of Predicting_bike_sharing_data.ipynb - commit "94e0c2e" has missing comma on line 137 resulting in invalid JSON error.

Issue is now resolved with
https://github.com/udacity/deep-learning-v2-pytorch/commit/5dcb0a826081a49229e1a5d63f5b9e728917357c


All running Visual Studio code instances shutdown all at once

I'm currently working on a relatively heavy project. project has at least 15 uServices ( all in nodejs) a angular5 front. all instances are opened using visual studio code. usually when I start working on angular side suddenly all running instances are shutdown. I wonder is it a bug or some thing is wrong with my machine by the way.
Thanks.

VSCode Version: 1.22.2
OS Version: Win 10.0.17134.1 (x64)
CPU: CoreI7 2600k - 3.4GHz
RAM: 32GB DDR3

Steps to Reproduce:

Running all instances.
Nodemon and ng serve are running in VSCode terminal.
Working on angular cause all processes to shutdown.

Does this issue occur when all extensions are disabled? Yes

Just a brief update.

I run node uServices out of VSCode terminal. Still the problem exists. So it has nothing to to with terminal.
Also i like to mention it has nothing to do with Angular. because this time it was happened during working with NodeJs side.
I wonder is it because of many instances running?
One very important thing that I've forget to mention. It was happening earlier during working with PhpStorm and WebStorm. Both of them had this problem. I even format and install a fresh new OS for this. but still it's there... .

@miladelecancy could you close all windows and see if it reproduces when you launch the first window using code --verbose --disable-extensions? If the close does happen could you check the terminal for output on the close event?

OK @Tyriar . It seems other VSC instances are sending their output to first initiated one. by the way it's first output: ( there was no closing at startup phase).
[20700:0530/115336.220:WARNING:dns_config_service_win.cc(661)] Failed to read DnsConfig.
[main 11:53:36 AM] Starting VS Code
[main 11:53:36 AM] from: m:\Apps\Code\Microsoft VS Code\resources\app
[main 11:53:36 AM] args: { _: [],
help: false,
h: false,
version: false,
v: false,
wait: false,
w: false,
diff: false,
d: false,
add: false,
a: false,
goto: false,
g: false,
'new-window': false,
n: false,
'unity-launch': false,
'reuse-window': false,
r: false,
'open-url': false,
performance: false,
p: false,
'prof-startup': false,
verbose: true,
logExtensionHostCommunication: false,
'disable-extensions': true,
disableExtensions: true,
'list-extensions': false,
'show-versions': false,
nolazy: false,
issue: false,
'skip-getting-started': false,
'skip-release-notes': false,
'sticky-quickopen': false,
'disable-restore-windows': false,
'disable-telemetry': false,
'disable-updates': false,
'disable-crash-reporter': false,
'skip-add-to-recently-opened': false,
status: false,
s: false,
'file-write': false,
'file-chmod': false }
[main 11:53:36 AM] Resolving machine identifier...
[main 11:53:36 AM] Resolved machine identifier: 8ef49aebf1b3c60da09cb79ad446c100fbcb7600610ce0351932b450c01a0185
[main 11:53:36 AM] update#setState idle
[20700:0530/115338.222:INFO:CONSOLE(1305)] "%cTRACE", source: file:///M:/Apps/Code/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js (1305)
[main 11:53:38 AM] windowsService#whenSharedProcessReady
[20700:0530/115338.255:INFO:CONSOLE(1305)] "%cTRACE", source: file:///M:/Apps/Code/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js (1305)
[20700:0530/115338.271:INFO:CONSOLE(1305)] "%cTRACE", source: file:///M:/Apps/Code/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js (1305)
[main 11:53:38 AM] windowsService#startCrashReporter
[main 11:53:38 AM] windowsService#setRepresentedFilename 1
[20700:0530/115338.695:INFO:CONSOLE(1305)] "%cTRACE", source: file:///M:/Apps/Code/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js (1305)
[main 11:53:38 AM] IPC#vscode-workbenchLoaded
[20700:0530/115338.992:INFO:CONSOLE(1305)] "%cTRACE", source: file:///M:/Apps/Code/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js (1305)
[20700:0530/115339.314:INFO:CONSOLE(1305)] "%cTRACE", source: file:///M:/Apps/Code/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js (1305)
[main 11:53:39 AM] IPC#vscode:broadcast vscode:changeColorTheme {"id":"vs-dark vscode-theme-defaults-themes-dark_plus-json","background":"#505050"}
[main 11:53:39 AM] windowsService#isFocused 1
[20700:0530/115341.222:WARNING:dns_config_service_win.cc(661)] Failed to read DnsConfig.
[20700:0530/115341.718:INFO:CONSOLE(1305)] "%cTRACE", source: file:///M:/Apps/Code/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js (1305)
[20700:0530/115343.396:INFO:CONSOLE(260)] "%c[Extension Host] %crejected promise not handled within 1 second %c(at Timeout._onTimeout (m:\Apps\Code\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:700:9))", source: file:///M:/Apps/Code/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js (260)
[20700:0530/115343.396:INFO:CONSOLE(1306)] "%c  ERR", source: file:///M:/Apps/Code/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js (1306)
[20700:0530/115346.225:WARNING:dns_config_service_win.cc(661)] Failed to read DnsConfig.
[20700:0530/115351.226:WARNING:dns_config_service_win.cc(661)] Failed to read DnsConfig.
[20700:0530/115353.419:INFO:CONSOLE(20)] "ApplicationInsights:Sender", source: M:\Apps\Code\Microsoft VS Code\resources\app\node_modules.asar\applicationinsights\Library\Logging.js (20)
[20700:0530/115356.230:WARNING:dns_config_service_win.cc(661)] Failed to read DnsConfig.
[20700:0530/115401.233:WARNING:dns_config_service_win.cc(661)] Failed to read DnsConfig.
[20700:0530/115406.236:WARNING:dns_config_service_win.cc(661)] Failed to read DnsConfig.
[main 11:54:06 AM] update#checkForUpdates, state =  idle
[main 11:54:06 AM] update#setState checking for updates
[main 11:54:06 AM] RequestService#request https://vscode-update.azurewebsites.net/api/update/win32-x64/stable/3aeede733d9a3098f7b4bdc1f66b63b0f48c1ef9
[main 11:54:06 AM] Error: net::ERR_INTERNET_DISCONNECTED
[main 11:54:06 AM] update#setState idle
[20700:0530/115411.239:WARNING:dns_config_service_win.cc(661)] Failed to read DnsConfig.
[20700:0530/115416.242:WARNING:dns_config_service_win.cc(661)] Failed to read DnsConfig.
[20700:0530/115417.577:INFO:CONSOLE(79)] "Uncaught Error: ENOENT: no such file or directory, scandir 'C:\Users\m\AppData\Roaming\Code\clp'
Error: ENOENT: no such file or directory, scandir 'C:\Users\m\AppData\Roaming\Code\clp'", source: file:///M:/Apps/Code/Microsoft VS Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js (79)
[20700:0530/115421.245:WARNING:dns_config_service_win.cc(661)] Failed to read DnsConfig.
[20700:0530/115421.679:INFO:CONSOLE(20)] "ApplicationInsights:Sender", source: M:\Apps\Code\Microsoft VS Code\resources\app\node_modules.asar\applicationinsights\Library\Logging.js (20)
[20700:0530/115426.248:WARNING:dns_config_service_win.cc(661)] Failed to read DnsConfig.
[20700:0530/115431.251:WARNING:dns_config_service_win.cc(661)] Failed to read DnsConfig.
[20700:0530/115436.256:WARNING:dns_config_service_win.cc(661)] Failed to read DnsConfig.
[20700:0530/115441.259:WARNING:dns_config_service_win.cc(661)] Failed to read DnsConfig.
[20700:0530/115446.262:WARNING:dns_config_service_win.cc(661)] Failed to read DnsConfig.
[20700:0530/115451.265:WARNING:dns_config_service_win.cc(661)] Failed to read DnsConfig.
[20700:0530/115456.268:WARNING:dns_config_service_win.cc(661)] Failed to read DnsConfig.
[20700:0530/115501.271:WARNING:dns_config_service_win.cc(661)] Failed to read DnsConfig.
[20700:0530/115506.273:WARNING:dns_config_service_win.cc(661)] Failed to read DnsConfig.
[20700:0530/115511.275:WARNING:dns_config_service_win.cc(661)] Failed to read DnsConfig.
[20700:0530/115516.278:WARNING:dns_config_service_win.cc(661)] Failed to read DnsConfig.
[20700:0530/115521.280:WARNING:dns_config_service_win.cc(661)] Failed to read DnsConfig.
[20700:0530/115526.283:WARNING:dns_config_service_win.cc(661)] Failed to read DnsConfig.
[20700:0530/115531.286:WARNING:dns_config_service_win.cc(661)] Failed to read DnsConfig.
[20700:0530/115536.288:WARNING:dns_config_service_win.cc(661)] Failed to read DnsConfig.
[20700:0530/115541.290:WARNING:dns_config_service_win.cc(661)] Failed to read DnsConfig.
[20700:0530/115546.293:WARNING:dns_config_service_win.cc(661)] Failed to read DnsConfig.
I have added your code to a little script to run whole instances at once like so:
const logger = fs.createWriteStream('logger.log');
dirs.forEach(dir => {
exec('code . --verbose --disable-extensions', {cwd: dir} ,(err, stdOut, stderr) => {
logger.write(stdOut);
});
});
Because it's logging on first instance so I hope there will be no problem with logger output.
I hope to capture the error there with this logger.
Thanks.

Appears to be related to localization.

@miladelecancy couple of questions:

do you have a language pack installed. If so which one
is this your correct user directory: C:\Users\m or is it truncated ?

I looked through our code and we create the C:\Users\m\AppData\Roaming\Code\clp directory in our main code (first thing executed) and if it fails we fall back to the English build in translation. @miladelecancy does that directory exist for you?

OK good. no it's not existed.

@sandy081 can you think of any code that runs in the shared process and tries to access the cache directory for language packs (e.g. AppData\Roaming\Code\clp).

Regarding https://github.com/Microsoft/vscode/issues/50763#issuecomment-393452868: good to hear that it doesn't crash anymore. But executing something in an external terminal compared to an internal one is unrelated in terms of translation.
The internal terminal has some native code which I think could crash a VS Code instance.

@dbaeumer It seems there is code that access clp cache directory here.
This is some language pack cache cleaner in shared process which you should be aware of I supposed.

@sandy081 thanks a lot. That is even my code :-(

To verify:

delete the LP cache directory. Under Windows it is ${Home}\AppData\Roaming\Code\clp

start code with --verbose from a terminal

ensure that no exception like

Error: ENOENT: no such file or directory, scandir 'C:\Users\m\AppData\Roaming\Code\clp'", source: file:///M:/Apps/Code/Microsoft VS Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js (79)

is printed to the console.


How to change activity alert state from fired to resolved

I understand that Activity alerts are stateless in nature and do not get resolve on their own. But what to do with alerts having condition as fired, i do not see any option in the portal to change its condition from fired to resolved. How to deal with alerts which are not valid anymore but still showing condition as fired?

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

ID: fc8041df-11b1-fbd4-5369-f8b02468c79d
Version Independent ID: fa0bbb7a-2a9c-7b49-d1c7-0d8419c9c4b0
Content: Types of Azure Monitor Alerts - Azure Monitor
Content Source: articles/azure-monitor/alerts/alerts-types.md
Service: azure-monitor
Sub-service: alerts
GitHub Login: @AbbyMSFT
Microsoft Alias: abbyweisberg

Hi,
@AbbyMSFT  have a question. I can change user response but no action group is fired so my external system is not aware of that and still thinks that issue is open, so need to close things manually in multiple places. Is it possible to somehow have a notification about user response changes?

Yes, changing user response is not impacting the alert state, this is currently the situation for all our alerts.

I am currently struggling with the similar way. I understand that "Change User Response" does not affect alert's state, but how to detect it? I am trying to integrate Azure Alerts with Opsgenie and user response is an important thing to propagate through webhook payload. If its not possible, I understand it, but detecting response change would be a step forward. Also, I understand that alert state "Resolved" cannot be done by human? If its true, this should be possible to change. One way or another, if I am not able to change alert's state nor resolve the alert, it makes things more complicated.


Add basic automated testing using GitHub Actions

This should ensure us that out plugin works on plain WIndows servers.

Write some simple tests to check if WinFFI/HKPD returns (at least) some values.
Activate CI on GitHub actions, and run tests on Windows Servers.

Add a simple test to check if this can take all kinds of records.

Add a simple test to check if this can take all kinds of records at 8c11c22.

@daipom  I set up GitHub Actions in a5b1bb5c to execute that test automatically.
You can check that CI is working in the "Actions" tab:
https://github.com/fluent-plugins-nursery/fluent-plugin-windows-exporter/runs/4579188195

@fujimotos Thank you! I can check CI is working.

Let's mark this ticket as done.

Talking about WIndows Server 2022, it seems that Fluentd fails to install
on that platform.
https://github.com/fluent-plugins-nursery/fluent-plugin-windows-exporter/actions/runs/1600910542
We need to fix this issue in the upstream project first, in order to enable our
testing on WinServer 2022.


Irregular shape of BEV

Hi @kashyap7x , thanks for your wonderful work on NEAT. I would like to ask regarding the blobby nature of BEV output as compared to other BEV methods like LSS or Fiery, where BEV of vehicles is quite sharp. Can you tell some pointers on how we can improve this irregular vehicle bev coming in NEAT?

Thanks

Hello!
Since the BEV segmentation was an auxiliary task, we did not focus on improving its sharpness in the paper. Some ideas which I think could help include using multi-resolution feature grids instead of simple feature vectors for conditioning, a better initialization of the attention weights than uniform (using information about the camera matrix), and removing future points from the semantics to simplify the task. Another simple thing to try would be tuning the weights of the semantic loss, and maybe setting class-specific weights.
In addition, implicit semantic segmentation has progressed significantly since early 2021, and some ideas from current state-of-the-art papers could be incorporated to sharpen the NEAT semantics, e.g.,

Panoptic Neural Fields: A Semantic Object-Aware Neural Scene Representation
Semantic Scene Completion using Local Deep Implicit Functions on LiDAR Data


Doesn't take MySQL Port into account

Hello,
I tried to install tinyissue onto a server with a MySQL Server on port 3307 instead of 3306, tinyissue has no option for a MySQL port :-1:

This project looks dead.


Optimized reads

A few comments on the new commit, but it LGTM and I'll re-review after the rebase!

/lgtm


Updated README.adoc

List of installers didn't get parsed as actual list, fixed formatting

@RickvdP Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@RickvdP Thank you for signing the Contributor License Agreement!

Thanks!


Colab pro error Interpolation

https://colab.research.google.com/github/AhabbscienceStudioPak/DAIN/blob/master/DAIN_Colab.ipynb#scrollTo=LH7EmLT2gA4l
colab PRO assign GPU
name, driver_version, memory.total [MiB]
Tesla V100-SXM2-16GB, 418.67, 16130 MiB
#interpolation
/content/DAIN
revise the unique id to a random numer 91876
Namespace(SAVED_MODEL=None, alpha=[0.0, 1.0], arg='./model_weights/91876-Thu-Sep-03-17-38/args.txt', batch_size=1, channels=3, ctx_lr_coe=1.0, datasetName='Vimeo_90K_interp', datasetPath='', dataset_split=97, debug=False, depth_lr_coe=0.001, dtype=<class 'torch.cuda.FloatTensor'>, end_frame=137, epsilon=1e-06, factor=0.2, filter_lr_coe=1.0, filter_size=4, flow_lr_coe=0.01, force=False, frame_input_dir='/content/DAIN/input_frames', frame_output_dir='/content/DAIN/output_frames', log='./model_weights/91876-Thu-Sep-03-17-38/log.txt', lr=0.002, netName='DAIN_slowmotion', no_date=False, numEpoch=100, occ_lr_coe=1.0, patience=5, rectify_lr=0.001, save_path='./model_weights/91876-Thu-Sep-03-17-38', save_which=1, seed=1, start_frame=1, time_step=0.2997002997002997, uid=None, use_cuda=True, use_cudnn=1, weight_decay=0, workers=8)
cudnn is used
Interpolate 2 frames
error in correlation_forward_cuda_kernel: no kernel image is available for execution on the device
Warning: Legacy autograd function with non-static forward method is deprecated and will be removed in 1.3. Please use new-style autograd function with static forward method. (Example: https://pytorch.org/docs/stable/autograd.html#torch.autograd.Function) (THPFunction_do_forward at /pytorch/torch/csrc/autograd/python_function.cpp:622)
Traceback (most recent call last):
File "colab_interpolate.py", line 112, in
y_s, offset, filter = model(torch.stack((X0, X1),dim = 0))
File "/usr/local/lib/python3.6/dist-packages/torch/nn/modules/module.py", line 532, in call
result = self.forward(*input, **kwargs)
File "/content/DAIN/networks/DAIN_slowmotion.py", line 148, in forward
self.forward_flownets(self.flownets, cur_offset_input, time_offsets=time_offsets),
File "/content/DAIN/networks/DAIN_slowmotion.py", line 212, in forward_flownets
temp = model(input)  # this is a single direction motion results, but not a bidirectional one
File "/usr/local/lib/python3.6/dist-packages/torch/nn/modules/module.py", line 532, in call
result = self.forward(*input, **kwargs)
File "/content/DAIN/PWCNet/PWCNet.py", line 221, in forward
corr6 = self.corr(c16, c26)
File "/usr/local/lib/python3.6/dist-packages/torch/nn/modules/module.py", line 532, in call
result = self.forward(*input, kwargs)
File "/content/DAIN/PWCNet/correlation_package_pytorch1_0/correlation.py", line 59, in forward
result = CorrelationFunction(self.pad_size, self.kernel_size, self.max_displacement,self.stride1, self.stride2, self.corr_multiply)(input1, input2)
File "/content/DAIN/PWCNet/correlation_package_pytorch1_0/correlation.py", line 27, in forward
self.pad_size, self.kernel_size, self.max_displacement,self.stride1, self.stride2, self.corr_multiply)
RuntimeError: CUDA call failed (correlation_forward_cuda at correlation_cuda.cc:80)
frame #0: c10::Error::Error(c10::SourceLocation, std::string const&) + 0x33 (0x7fc469e26193 in /usr/local/lib/python3.6/dist-packages/torch/lib/libc10.so)
frame #1: correlation_forward_cuda(at::Tensor&, at::Tensor&, at::Tensor&, at::Tensor&, at::Tensor&, int, int, int, int, int, int) + 0x628 (0x7fc46625ab38 in /usr/local/lib/python3.6/dist-packages/correlation_cuda-0.0.0-py3.6-linux-x86_64.egg/correlation_cuda.cpython-36m-x86_64-linux-gnu.so)
frame #2:  + 0x1bd4a (0x7fc46626ad4a in /usr/local/lib/python3.6/dist-packages/correlation_cuda-0.0.0-py3.6-linux-x86_64.egg/correlation_cuda.cpython-36m-x86_64-linux-gnu.so)
frame #3:  + 0x18890 (0x7fc466267890 in /usr/local/lib/python3.6/dist-packages/correlation_cuda-0.0.0-py3.6-linux-x86_64.egg/correlation_cuda.cpython-36m-x86_64-linux-gnu.so)
frame #4: python3() [0x50a7f5]

frame #7: python3() [0x594b01]
frame #9: THPFunction_do_forward(THPFunction, _object) + 0x4ac (0x7fc4b2e37d4c in /usr/local/lib/python3.6/dist-packages/torch/lib/libtorch_python.so)
frame #11: python3() [0x54ac61]
frame #13: python3() [0x50a783]
frame #16: python3() [0x594b01]
frame #19: python3() [0x507f24]
frame #21: python3() [0x594b01]
frame #22: python3() [0x54ac61]
frame #24: python3() [0x50a783]
frame #26: python3() [0x507f24]
frame #28: python3() [0x594b01]
frame #31: python3() [0x507f24]
frame #33: python3() [0x594b01]
frame #34: python3() [0x54ac61]
frame #36: python3() [0x50a783]
frame #38: python3() [0x507f24]
frame #39: python3() [0x509c50]
frame #40: python3() [0x50a64d]
frame #42: python3() [0x507f24]
frame #44: python3() [0x594b01]
frame #47: python3() [0x507f24]
frame #49: python3() [0x594b01]
frame #50: python3() [0x54ac61]
frame #52: python3() [0x50a783]
frame #54: python3() [0x507f24]
frame #56: python3() [0x634dd2]
frame #61: __libc_start_main + 0xe7 (0x7fc4be047b97 in /lib/x86_64-linux-gnu/libc.so.6)
please tell me how to deal with the error?

I have the same problem.

Hi there! You seem to be using an old version of the colab file. I believe that also the repository has changed minor things about the interpolation so if I was in your situation, I'd give it a try with the new version. You can find it here: https://github.com/baowenbo/DAIN/blob/master/Colab_DAIN.ipynb

: https://github.com/baowenbo/DAIN/blob/master/Colab_DAIN.ipynb
Using this Colab, an error occurred in the fps detection block,
and Google drive was successfully connected.
sorry for my English, I'm using a translator

cp: cannot stat '/content/gdrive/My Drive//content/gdrive/My': No such file or directory
cp: cannot stat 'Drive/Pexels': No such file or directory
cp: cannot stat 'Videos': No such file or directory
cp: cannot stat '2759484.mp4': No such file or directory

CalledProcessError                        Traceback (most recent call last)
 in ()
1 # Detecting FPS of input file.
----> 2 get_ipython().magic('shell yes | cp -f /content/gdrive/My\ Drive/{INPUT_FILEPATH} /content/DAIN/')
3
4 import os
5 filename = os.path.basename(INPUT_FILEPATH)
3 frames
/usr/local/lib/python3.6/dist-packages/google/colab/_system_commands.py in check_returncode(self)
136     if self.returncode:
137       raise subprocess.CalledProcessError(
--> 138           returncode=self.returncode, cmd=self.args, output=self.output)
139
140   def repr_pretty(self, p, cycle):  # pylint:disable=unused-argument
CalledProcessError: Command 'yes | cp -f /content/gdrive/My\ Drive//content/gdrive/My Drive/Pexels Videos 2759484.mp4 /content/DAIN/' returned non-zero exit status 1.

@AlexU225 Hi, the error is simply that it's not finding the file path. See the error you got:
cp: cannot stat '/content/gdrive/My Drive//content/gdrive/My': No such file or directory
cp: cannot stat 'Drive/Pexels': No such file or directory
cp: cannot stat 'Videos': No such file or directory
cp: cannot stat '2759484.mp4': No such file or directory
So, in parameters, instead of /content/gdrive/My Drive/Pexels... you should use Pexels...

Thank you for your advice! But now there is an error in this block
File "/usr/local/lib/python3.6/dist-packages/torch/nn/modules/module.py", line 532, in call
result = self.forward(*input, **kwargs)
File "/usr/local/lib/python3.6/dist-packages/torch/nn/modules/conv.py", line 345, in forward
return self.conv2d_forward(input, self.weight)
File "/usr/local/lib/python3.6/dist-packages/torch/nn/modules/conv.py", line 342, in conv2d_forward
self.padding, self.dilation, self.groups)
RuntimeError: cuDNN error: CUDNN_STATUS_NOT_SUPPORTED. This error may appear if you passed in a non-contiguous input.

Hey @AlexU225 I'm glad you made it that far! Unfortunately, I cannot help you there. That seems like a problem with the image processing itself.

I have same problem with Tesla V100-SXM2-16GB,but P100-PCIE-16GB is work.
RuntimeError: CUDA call failed (correlation_forward_cuda at correlation_cuda.cc:80)
I tried to use new version,but it still happened.
please tell me how to deal with the error?

Hello,
I have the same problem as @niuhuojian also with the Tesla V100-SXM2-16GB. Which I am using on Google Colab.
Here I get the following error when running the notebook from: https://github.com/baowenbo/DAIN/blob/master/Colab_DAIN.ipynb

I tried already some things to fix it.
using different combinations of Cuda, gcc and torch versions . (Cuda 9.0, gcc 6.5,  torch 1.0.0/Cuda 9.0, gcc 6.5,  torch 1.1.0/ Cuda 9.0, gcc 4.8, torch, pytorch 0.4.1 /Cuda 10.0 gcc 7.5, torch 1.4/Cuda 10.1 gcc 7.5, torch 1.6.)
But non of them worked for me.
I also tried to use the solution from from CyFeng16 from issue#44 in but this also seems to stop working.
When I use Cuda 9.0 with gcc-4.8 g++-4.8 which used to work around 4 month ago. This one as well as some of the other combinations gave me the FilterInterpolation Module error from the my_packages folder. see below:
...
Traceback (most recent call last):
File "train.py", line 15, in
import networks
File "/content/DAIN/networks/init.py", line 1, in
from .DAIN import DAIN
File "/content/DAIN/networks/DAIN.py", line 4, in
from my_package.FilterInterpolation import  FilterInterpolationModule
File "/content/DAIN/my_package/FilterInterpolation/init.py", line 1, in
from .FilterInterpolationModule import *
File "/content/DAIN/my_package/FilterInterpolation/FilterInterpolationModule.py", line 6, in
from .FilterInterpolationLayer import FilterInterpolationLayer,WeightLayer, PixelValueLayer,PixelWeightLayer,ReliableWeightLayer
File "/content/DAIN/my_package/FilterInterpolation/FilterInterpolationLayer.py", line 4, in
import filterinterpolation_cuda as my_lib
ModuleNotFoundError: No module named 'filterinterpolation_cuda'
I am slowly running out of ideas to fix that. Does anyone have a working notebook, or an idea what else I could try to do?
That would be great!

Hi there, I think that's caused by the building process of DAIN packages
ModuleNotFoundError: No module named 'filterinterpolation_cuda'
This means the "filterinterpolation_cuda" package is not installed. Did you run build.sh?
Since you have V100 with the compute compatibility of 7.0, you should uncomment the line
# '-gencode', 'arch=compute_70,code=sm_70',
at DAIN/my_package/compiler_args.py. Then run the build.sh at my_package and PWCNet.
AD. For eaiser installation and usage, refer to iBobbyTS/VFIN, this is kind of like a Video interpolation toolkit, of cause DAIN is in it. I have a colab notebook and you can store the whole built VFIN in drive, every time you only need to extract the files to Colab Runtime and you can start using it.

I have same problem with Tesla V100-SXM2-16GB,
RuntimeError: CUDA call failed (correlation_forward_cuda at correlation_cuda.cc:80).
niuhuojian said that  P100-PCIE-16GB works, unfortunately I can't specify which GPU should be used .
The only reason to stack with this version becouse intrigued the ability to specify random output FPS (60fps)

I uncommented '-gencode', 'arch=compute_70,code=sm_70' in the compiler_args.py and switched to !pip install torch==1.0.0 torchvision==0.2.1 as  TaoTeCha suggested in another post https://github.com/baowenbo/DAIN/issues/117#issuecomment-725081412
The colab is working with a V100 now

Any chance to make Windows binary?