JSONFunction / Slash escape / JDK 1.5

JSONFunction class for value as a hack to not surround it with quotes
Only escape "/" slash after a "<" bracket, because it is allowed
JDK 1.5

Hi,
as long as no Java 7 features are needed I would suggest to compile on Java 1.5.
I have implemented a small hack which is required by (see the new test):
https://github.com/apache/wicket
Also as of http://stackoverflow.com/questions/1580647/json-why-are-forward-slashes-escaped slashes are allowed, but only escaped right after a "<" bracket. There reason is that you can't place them into a script-tag without.

https://issues.apache.org/jira/browse/WICKET-6287

@klopfdreh

Wicket 1.5 does not use JSON.org. We started using it from 6.0.0, i.e. it should be compiled with target 1.6.
JsonFunction is not in JSON specs. As mentioned at https://github.com/apache/wicket/blob/ce66c242ad83266a4f5c01363b4b446138b054e9/wicket-core/src/main/java/org/apache/wicket/ajax/json/README#L9 all Json** (in contrast to JSON**) classes are developed for Wicket's needs in addition.

If the lib also compiles with JDK 1.5 why not use this instead of 1.6 - it covers even more Apps using 1.5 currently
I am going to rename it back and change the build in hack back to JsonFunction - it is just a hack to let JSONStringer not surround the value with quotes

If someone still uses Java 5 for whatever reasons I'm pretty sure that (s)he won't want to change the JSON lib just for the fun :-)

Regarding support for java 1.5, I would rather not go that far. For one thing, my Java compiler warns me about that and I prefer to avoid warnings.

OK. I have incorporated the Java level change (but only to 1.6) and the </ escaping since I think that nobody can mind those changes. I did those as separate commits to make them more clear.
The function non-quoting is still not clear to me. Can you merge my changes so far into your code so that we can look at the differences more clearly?
And can you say a bit more about the intent? Is it to have a special purpose hack so that if the value of an object is a class with JSONFunction in the name that quotes will not be used for toString? No change on deserialization?

Hi,
first of all - thanks for your fast response! - 1.6 is also fine for Apache Wicket and if you get compiler warnings we should avoid it.
Regarding the JSONFunction:
This is only a separate behavior in case that the values class name contains JSONFunction* and causes them not to be surrounded by quotes. I wrote a test case for that:

Check out master branch and let me know if this meets your needs.
Once you give the word, I will push a new release.

Hi @tdunning - yes looks good to me. I just saw that the method "string" is private - so no need to implement one without the second parameter.
Thank you!

Release is done.  Look for version 1.2 on central in a few hours.

Thank you! 👍


How to recreate this configuration using Vite?

Hi! The case study is really insightful and I would love to see similar approach in Vite in action, however, I have not enough time and knowledge to create such config by myself. Is there any chance that some of you might include vite version of this repo? Maybe other build tools would also be beneficial?

@WikKam Thanks for your interest in this project!
Unfortunately, I have no knowledge of Vite or other bundlers and I doubt that any of them is as configurable as Webpack is (Vite might be an exception).
Please keep in mind that Vite might only benefit you during development, while it will harm you in production build times:
https://storybook.js.org/blog/storybook-performance-from-webpack-to-vite
Nevertheless, I will keep this issue open in hope that someday someone will be able to configure most (if not all) of this project in Vite.

@WikKam
The project was migrated to Rspack, which is far superior to anything out there.
Cloudflare Pages now takes 1.5s to build this app. With Webpack it took 12.7s.
#10


How can i import into a plain html file?

Recently i need it to import this component into a non react project, like a simple html page, how can i do this? It's possible? I've been tryin' to import UMD file generated, but it does not work.

If you want to add into simple HTML page;

Clone this project.
Run npm install/ yarn then npm start/ yarn start
After successful start, run npm build. This will create a build folder with CSS & JS folder.
Copy these files into your HTML page, and add a div with ID anywhere in the code, for example:

And import all the CSS & JS.
This will add chat widget into your simple HTML page.

Hi @juzejunior, I don't think you can actually use a react component in a non-react project, sorry - you will have to look for plain javascript solutions or perhaps find a jquery based library to rely on. Good luck!


should keep path / activity when memory can't keep app open

When the RAM memory is not able to maintain a flutter application, it restarts in its entirety, that is, if it is on route B it returns to route A, while in a native app it stays on route B.
I don't want the path to be saved when I close the app manually, but I want it to be saved when I return to the app and the RAM can't keep the app open.
https://user-images.githubusercontent.com/85927029/149370772-8d608b6d-c387-456d-88d3-07a0894bc2a6.mp4
The code is simple, it is nothing more than a button that opens another route

@edsonISA
I think this is related to State restoration wherein the application state isn't maintained in situations like when the app is over memory. The same issue is raised here https://github.com/flutter/flutter/issues/84193. You can follow-up in it for further updates.
Closing this as a duplicate. If you disagree, write in comments and I'll reopen it.

@edsonISA Creo que esto está relacionado con la restauración del estado en el que el estado de la aplicación no se mantiene en situaciones como cuando la aplicación tiene demasiada memoria. Aquí se plantea el mismo problema #84193 . Puede hacer un seguimiento en él para obtener más actualizaciones. Cerrando esto como un duplicado. Si no está de acuerdo, escriba en los comentarios y lo reabriré.

yes, it's a duplicate, it speaks exactly the same


add support for overlapping marks

This addresses issue #34 - while remaining backwards compatible.
There are still two TODO items open open:

[ ] the test currently fails, I think because there is a yChange attr on one of the documents. I'm not sure what the intention behind yChange is, so I'm not sure what the right way is to fix this
[ ] the current solution breaks YXmlText.toString because it doesn't handle arrays. I think we should add support for this directly in yjs, but want to make sure the solution I'm implementing here is a right approach.

The first TODO is an open issue I think

the test currently fails, I think because there is a yChange attr on one of the documents. I'm not sure what the intention behind yChange is, so I'm not sure what the right way is to fix this

Check: https://github.com/yjs/y-prosemirror/issues/77 and https://github.com/yjs/y-prosemirror/issues/51

Since ychange  is lost in the conversion between prosemirror and ydoc, perhaps we should test the marks directly? https://github.com/yjs/y-prosemirror/blob/7a3afbc0d8de35bc01bd63bfc9911318c115c4f7/src/plugins/sync-plugin.js#L961

Hey @dmonad, I know it's an old PR, but could you please let us know if this is the right direction to take for supporting overlapping ProseMirror marks?

@YousefED @dmonad

I know it's an old PR, but could you please let us know if this is the right direction to take for supporting overlapping ProseMirror marks?

+1


[DISCUSSION] Captcha

Hey everyone,
It seems that indeed and others have caught on to scraping and have taken action to stop it.
We can integrate web-driven scraping but this is not easily automated or tested.
I think this may be a serious problem for this tool in general, the regexes we have built still work, but captcha is catching the scrapers very easily, after under a hundred jobs or so.
Does anyone have any ideas to help with this issue?

One option is that we go the route of a web-driven scraper, perhaps this tool could be made into some kind of browser extension?

Another option is to forgo scraping detailed job information entirely, but this will significantly degrade the matching and data quality.

I tried using  this code from geohot a couple of years back, I never got it to work.  its's not practical code, just a doodle.
https://github.com/geohot/lolrecaptcha
https://www.blackhat.com/docs/asia-16/materials/asia-16-Sivakorn-Im-Not-a-Human-Breaking-the-Google-reCAPTCHA-wp.pdf

off topic a bit. In the future, incase someone finds a solution to this.
How to run JobFunnel and avoid Google(Youtube) captcha.
It started this year Jan 2021, Google and YouTube keeps asking me to solve captcha. This was funny at first; then it gets annoying every 3 hours now when I'm learning or looking solutions to a problem.
I have no outgoing traffic on my machine. The firewall is doing its job. The only automation tool I have running is JobFunnel.
I can't clear cookies either; it will just make it worse when I google something.

Maybe it could pick from a list of proxies? Would probably get rid of the captcha all together.

yeah I get dinged pretty quick nowadays, I figure i'm on their $hit list :laughing:
Not a bad idea around the proxies, that would be an interesting feature, I'll create a little feature-stub for this.

yeah I get dinged pretty quick nowadays, I figure i'm on their $hit list 😆
Not a bad idea around the proxies, that would be an interesting feature, I'll create a little feature-stub for this.

for proxies I have used https://github.com/TheSpeedX/PROXY-List ,mainly for  mega.io limiting upload and downloads.
https://github.com/tonikelope/megabasterd.git , MBD has a feature where it picks the next proxy once it gets throttle; it triggers the next proxy in the list. I haven't used  proxies on JobFunnel yet. Can't wait to try it out if I get block.
P.s.. Youtube still gives me captcha once a week now.  It was every 4 hours since December 2020, now it's once a week. I think they are outsourcing machine learning labels to me.

Based on this discussion, we will move forwards with #145


Avoid needless recalculation in RetryPolicy functions

Don't recompute unnecessarily (e.g. iterateDelay, fibonacciBackoff)

@stacycurl Looking into using something like scalaz.State to avoid recalculation on things like iterateDelay and fibonacciBackoff, any ideas on how it should it be woven in? Seems like the memoization can either be client-side, where they just pass in a memoized function with something like scalaz.Memo, or we can replace Int => Option[FiniteDuration] with something like [S]Int => Option[(S, FiniteDuration)]
Not entirely sure how well this will work out since different functions will have different memoization strategies.. e.g. fibonacci may want a Map[BigInt, BigInt] (http://tonymorris.github.io/blog/posts/memoisation-with-state-using-scala/) but iterateDelay just needs a FiniteDuration to track the previous state. Then there's ones that don't need any state like exponentialBackoff.. so it'd just be ().
The key bit is here.


Move to use <IP_ADDRESS> for network listeners by default in some cases

Description:
Move to use <IP_ADDRESS> for the network listen interface of the collector by default on Windows and Linux installers, as well as Chocolatey

I don't believe we've advertised this as an upcoming change and wonder about a smoother transition using feature flags and the internal settings mechanism.
The failing TestWindowsIISInstrumentation test shows that the health check extension is arguably a bad candidate for this change since its use is catered for external clients.

We're just changing some of the default values of the installers and not the software itself, so we can probably not do this work with feature flags. We could make a warning log appear advertising this upcoming change as a separate PR.
I guess I will need to check the best way to address the health check failure. For now I think the best approach is to configure the health check to bind to <IP_ADDRESS> to keep the test working.

I guess I will need to check the best way to address the health check failure. For now I think the best approach is to configure the health check to bind to <IP_ADDRESS> to keep the test working.

You can try updating the installation command for the -network_interface "<IP_ADDRESS>" option.

Yes, I pushed this as result. Thanks for the help :)

If you rebase, the installer tests will probably fail since it is expecting "<IP_ADDRESS>" by default , and the custom test uses "<IP_ADDRESS>".  We can probably just swap those in the tests.

We'll also need to remember to update https://github.com/splunk/public-o11y-docs/blob/main/gdi/opentelemetry/install-linux.rst?plain=1#L220 and https://github.com/splunk/public-o11y-docs/blob/main/gdi/opentelemetry/install-windows.rst?plain=1#L182 when these changes are released.

Re docs - sure. @aurbiztondo-splunk as heads up

We're just changing some of the default values of the installers and not the software itself, so we can probably not do this work with feature flags. We could make a warning log appear advertising this upcoming change as a separate PR.

I'm suggesting another approach based on the content of these changes. Having to manage the ip in multiple places adds some complexity to expected behavior and considering its use is only in the default agent and gateway configs that the settings/main evaluate it could happen there. imo we <IP_ADDRESS> would only be applicable for agent installations and default to it in gateway mode is potentially entirely breaking.

From our discussions. the approach to revise this approach advocates to be mindful of adopting different modes of operation for the collector, which approach the problem holistically:

Agent
Gateway
Custom
We currently don't have a good way to identify how the collector was started. We run with a custom mode always. We also don't identify anywhere in our installation if we picked agent or gateway during install, except for the config file name we pick.

I like this approach as an evolution of how we shape and distribute the collector to make it easier on everyone to know how things work, with an authoritative approach where we know for a fact that running as gateway is matching an exact configuration and reduces pain levels for customers who can live with defaults.
Right now, however, we're not there, and we have to contend with good defaults for our "custom" mode which is set initially by our installer.
The proposition then boils down right now to heuristics, which may help but also burden ourselves with complexity or edge cases. The proposition is that if we identify the collector is running with an exact match to the gateway configuration file location, our settings defaults then should change to be set to <IP_ADDRESS>.
This proposition contradicts this PR as we set the environment variable value during installation to a fixed value, which we set to <IP_ADDRESS> for specific installation methods that reflect most likely an agent deployment on a host.
We can approach this in 2 ways:
We can expose the default value during installation to be decided based on prior prompts and choose <IP_ADDRESS> or <IP_ADDRESS> as defaults based on whether the user wants a gateway or agent mode.
We can decide to leave this environment variable unset during installation and apply a default mindfully based on file location.
Both approaches have their merits. I would personally like to pick the one that doesn't bind us in a particular mode of operation.
If we set the environment variable explicitly, we can offer a clear contract to our users. However, we are then beholden to this approach moving forward.
If we set the default based on file location, we are placing ourselves in a more flimsy place, as the file location maybe not always reflect that we are working with a gateway mode, but we reduce our commitment.
I propose we do the following:

Add a log at startup with the value picked in settings.go so we don't have a hard time debugging this later with customers.
Add code towards moving to <IP_ADDRESS> when the gateway location is used.
During installation, do not set the default env var value if none is provided.

Add a log at startup with the value picked in settings.go so we don't have a hard time debugging this later with customers.
Add code towards moving to <IP_ADDRESS> when the gateway location is used.
During installation, do not set the default env var value if none is provided.

👍

We currently don't have a good way to identify how the collector was started.

Though not necessarily "good" we do know the config and config content but I'm not sure what deductions or end state we'd want to have. Having the desired config resolve to agent_config.yaml or gateway_config.yaml seems an adequate mechanism to determine what value to set the env var to. I would advise that we always set a value if not set directly for continuity and to avoid requiring a (arbitrary?) constant name for the env var to be usable.

I would advise that we always set a value if not set directly for continuity and to avoid requiring a (arbitrary?) constant name for the env var to be usable.

We can still exercise the env var and set it with an empty value so it's reserved and documented in the customer configuration.


Legion ?

Hello
I see the last patch mentioning Legion and demon hunters.
Is that addon not for vanilla anymore ?
Should i NOT upgrade it ?

Hey @Bifidus ,
ChatSuey is still for vanilla! The reference to Demon Hunters is related to a color name you can use with the markdown links addon. For example, you could write [Thunderfury](item:19019){demonhunter} and you would get a purple item link. The "demonhunter" color name has always been in Chatsuey, but it used to be a green color, as that was the color originally proposed by Blizzard for Demon Hunters before Legion was released.
You can read more about how the Markdown Links addon works and see a reference of all the usable colors at the project website.
I'll have to see if I can re-word the release notes to make things more clear.

Ok, thank you for your answer.


getting-started edits

Some thoughts for making "Getting Started" a little easier to "get started" from, maybe? Take what you like here!
Also your call: We'd typically use the "z" form of words like internationalization, but up to you.

size-limit report 📦

Path
Size

/index.html
13.05 KB (+0.01% 🔺)

/_astro/*.js
16.51 KB (0%)

/_astro/*.css
9.02 KB (0%)


Display player's current activity (e.g., domain, boss)

Check and display the player current activity such as in the menus, domain, bosses, abyss, dialogues, TCG, etc...

Still needs some tweaks


Is there a way to use this with multicontrolnet in A1111

i wanted to know if there is a way for us to use your controlnet model over SD v1.5 or similar architecture based models and add glyph controlnet on top of that. (similar to how multicontrolnet is being used right now). Please let us know if it is possible or not, and if so , how can one go about implementing it?
Thanks

@yukang123 @guidongnan Please help to answer the question.

Hi @ghpkishore, thanks for your questions!
Since our GlyphControl framework is mainly based on the ControlNet. It is possible to transfer our controlnet model onto other stable diffusion models. To do so, it is necessary to extract the model parameters of ControlNet part (i.e., glyph controlnet in our scenario) from the released checkpoints as the ControlNet v1.1 does.  Then you could use these parameters as one type of control to use onto other SD models.
Although it is doable, I could not gaurantee the outcomes. Since our model was trained based on SD v2.0, it may bring differences while using other SD models.  Besides, the effects of combining our glyph controlnet with other controlnet models using canny maps or segmentation maps, are still worth exploring.

Hi @yukang123
Thanks for your response. Appreciate it. You mentioned it is possible to get the extract the controlnet part of the model out. Can you help me with the script which I need to use for it to work. Also I saw from the checkpoints on HF that they are roughly 6.67 GB and wanted to know how big would be the extracted controlnet.
I agree that it is trained on V2 and hence might not work well with other models, but I am willing to try.
My goal is to get a .pth file similar to controlnet v1.1 models (https://huggingface.co/lllyasviel/ControlNet-v1-1/tree/main) so that I can directly run it with the existing controlnet webui from A1111. This is the note from the controlnet repo owner for using custom models:

Note: If you download models elsewhere, please make sure that yaml file names and model files names are same. Please manually rename all yaml files if you download from other sources. (Some models like "shuffle" needs the yaml file so that we know the outputs of ControlNet should pass a global average pooling before injecting to SD U-Nets.)

Request you to let me know how to proceed. Thanks

The basic way is to load the entire the model and only save the parts related to the controlnet part. You could get referrence about how to load the model from the inference.py and cldm/cldm.py, and try to save the model parameters related to ControlNet (probably self.control_model in the cldm.py).
The whole procedure is simple to implement. You could try to extract the parameters and compare with the released controlnet v1.1 models.

@yukang123 thanks. There is this script: https://github.com/Mikubill/sd-webui-controlnet/blob/main/extract_controlnet.py
Would this be able to extract the controlnet. If you think there is a possibility, then I will do so. Thanks

I think it would be very helpful for extraction. But I still suggest that you should read the codes first in case of some errors during extractions.
In general, the script you mentioned should be fine.


DO NOT MERGE Upgrade to Scala 2.10.7 and 2.11.12

Depends on #3182. Will need to be rebased on top of it once it's merged.

Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/4359/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/5865/
Test FAILed.

One of our tests fails on the JVM on 2.10.7 and 2.11.12. It's a regression in scalac/JVM: https://github.com/scala/bug/issues/10609
I'll assume away that test on those versions.

Updated.

Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/4361/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/5868/
Test PASSed.


Inventory changes don't save

I got the first armour piece, but it doesn't stay equipped (tried brave and safari). After each match I check and its reset, or every time I refresh the page. Not sure if its working or not in game
What is the drop rate of other NFT's? Got this one from killing the first boss. I killed the next 3 in that match, and have killed another ~10 in subsequent matches and not dropped anything else

got a drop after ~25 boss kills, can ignore that bit

Hi, @simonmcl thank for the feedback!
As for equipment - that's the way it was meant to be by design by the reason of equip management complexity in terms of multiple accounts and multiple browsers. This game mostly is a Tezos Unity SDK showcase, therefore sometimes we've been looking for compromises between dev speed and feature presence. However, it's one of the most requested features, we will implement it when we get a chance.
As for drop in a nutshell - when you kill a boss you have a chance (~1% from first level boss and linearly increasing to ~3.9% from 30 level boss) that this boss will drop a token.
If you're in with a chance, you will receive one of this tokens with probability mentioned in a big table in a game docs.


Invalid API key

Describe the bug
created user using cli comand as a result api key is generated, use this api key to configure the SDK. getting status code 401 Invalid API key
Endpoint:  /worksapces
Method: GET
To Reproduce
Steps to reproduce the behavior:
1.To create the user, run the following from src/whyhow_api/cli/:
2. Run Command python admin.py create-user --email  --openai-key
3. why_how api key is generated
4.  use this api key to configure the SDK.
Screenshots

Thanks @MuhammadNomanIqbal, can you confirm that you see this API key in your user collection in MongoDB? Can you also confirm that you can hit the Atlas endpoint from your IP?

Hey @MuhammadNomanIqbal, fyi we just pushed a new version of the src/whyhow_api/cli/admin.py script. Could you try pulling the latest and try recreating the db + collections + indexes with this new script and see if that works better for you?
Re: Knowledge Graph Studio UI - we charge for the frontend, so this is not available open source.


Not getting any reply when trying to Upload a extension.

I have tried too many times to upload a extension in my developer account, i have field the form which has to be field before upload of extension for permission, Its been more than 5 Months I am trying but i am not getting the proper support Please help me with this, This page is not help full for that

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

ID: 1037a28d-7cd5-66dc-9826-1e626fa6e74b
Version Independent ID: f90b56a3-db51-eeea-707c-0c30e81b4749
Content: Extensions - Microsoft Edge Development
Content Source: microsoft-edge/extensions.md
Product: microsoft-edge
GitHub Login: @abbycar
Microsoft Alias: abigailc

@AdityaSaurabhbxr, is the upload itself failing? Or were you able to successfully submit it to the store and still waiting to see if it was accepted?

@erikadoyle Thanks For the reply,
upload itself failing. I am not able to upload I have followed the entire process listed on the web.

Windows developer support should be able to help. You might find an answer in the community forums, and if not, you can file a ticket from the Contact Us link.


Add support for GenerateFloatTypes, for use with cunn.

Add support for GenerateFloatTypes, for use with cunn.

Thanks Greg!


[BUG] logical::operator[] is broken

The following code:
mask[i] = true;

compiles but silently doesn't work.

This is a side-effect of the operator[] for lookup. I'll add a proper =delete where it should

This is a side-effect of the operator[] for lookup. I'll add a proper =delete where it should


Sometimes you press enter and the rear window will scroll to another position

Issue Type: Feature Request
Sometimes you press enter and the rear window will scroll to another position
VS Code version: Code - Insiders 1.35.0-insider (6ac87465f297a9068bf767f45d6f372fc5697de9, 2019-05-17T17:48:07.036Z)
OS version: Windows_NT x64 10.0.17763

/needsMoreInfo


Added File organizer script

Description
Added file organizer script
Fixes #1705

Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
[x] Documentation Update

Checklist:

[x] My code follows the style guidelines(Clean Code) of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have created a helpful and easy to understand README.md
[x] My documentation follows Template for README.md
[x] I have added the project meta data in the PR template.
[x] I have created the requirements.txt file if needed.

Project Metadata
If there is no-file/nothing to fill the below fields with, then type: none
Example: If no requirements.txt needed/present, then type none in Requirments.
Category:

[ ] Calculators
[ ] AI/ML
[x] Scrappers
[ ] Social_Media
[ ] PDF
[ ] Image_Processing
[ ] Video_Processing
[ ] Games
[ ] Networking
[ ] OS_Utilities
[ ] Automation
[ ] Cryptography
[ ] Computer_Vision
[ ] Fun
[ ] Others

Title:  File organizer script
Folder: File Organizer Script
Script: file_organizer.py
Contributor:  Abhinavcode13
Description:
A File Organizer script is a program or script that automates the process of organizing files within a directory or multiple directories. It helps in managing and arranging files based on specific criteria, such as file type, date, name, or any custom rules.
The purpose of a File Organizer script is to bring structure and order to a cluttered file system by grouping files into appropriate folders or directories. This can improve file organization, make it easier to find and access files, and enhance overall file management

hey @1e9abhi1e10 @avinashkranjan please check this PR
thanks


New PR to test SignCLA at 2019-04-02 00:27:17.640338428 -0400 EDT m=+4.589531062

Body of PR

unsigned-fail-staging: test succeeded


Revert "update enterprise cookbook to 0.7.0."

Reverts chef/omnibus-supermarket#26

Build is currently broken do this an upstream issue in enterprise-chef-common.  Reverting this pull request until that upstream change is fixed.

:+1:


Roll engine 9a17d8e45197..1235439830ae (10 commits)

git@github.com:flutter/engine.git/compare/9a17d8e45197...1235439830ae
git log 9a17d8e45197..1235439830ae --no-merges --oneline
2019-08-30<EMAIL_ADDRESS>Roll src/third_party/dart 1573f4e877..fd48ea3432 (16 commits)
2019-08-30<EMAIL_ADDRESS>last flutter web sync: cc38319841 (flutter/engine#11732)
2019-08-29<EMAIL_ADDRESS>Roll src/third_party/dart 05c28c6115..1573f4e877 (14 commits)
2019-08-29<EMAIL_ADDRESS>Roll src/third_party/skia 3783375c4d41..165ca3f85b7a (8 commits) (flutter/engine#11725)
2019-08-29<EMAIL_ADDRESS>Quote the font family name whenever setting the font-family property. (flutter/engine#11722)
2019-08-29<EMAIL_ADDRESS>Revert "Notify framework to clear input connection when app is backgrounded (#35054) (#9498)" (flutter/engine#11720)
2019-08-29<EMAIL_ADDRESS>Return a JSON value for the Skia channel (flutter/engine#11717)
2019-08-29<EMAIL_ADDRESS>Android 10+ View.setSystemGestureExclusionRects (flutter/engine#11441)
2019-08-29<EMAIL_ADDRESS>Roll src/third_party/dart 35382f9b14..05c28c6115 (flutter/engine#11702)
2019-08-29<EMAIL_ADDRESS>Roll src/third_party/skia ca8b07cf8a59..3783375c4d41 (2 commits) (flutter/engine#11712)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

Luci is green for the relevant commit, going to close this again.

Commit queue failed; closing this roll.


No dependencies on React Native Web

Tested with the example repo, tried to port the behavior from react-native-web over as much as possible.

looks perfect, we will test it a bit more and merge it.


[Branch-2.10][Broker] Make PersistentTopicsBase#internalGetPartitionedMetadata async

Motivation
I am releasing 2.10.3. This PR needs to release on 2.10.3, but it has some conflict with branch 2.10. So I open a PR to resolve these conflicts.
Modifications
Cherry-pick https://github.com/apache/pulsar/pull/14153
Verifying this change

[ ] Make sure that the change passes the CI checks.

(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

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

Does this pull request potentially affect one of the following parts:
If the box was checked, please highlight the changes

[ ] Dependencies (add or upgrade a dependency)
[ ] The public API
[ ] The schema
[ ] The default values of configurations
[ ] The threading model
[ ] The binary protocol
[ ] The REST endpoints
[ ] The admin CLI options
[ ] Anything that affects deployment

Documentation

[ ] doc
[ ] doc-required
[x] doc-not-needed
[ ] doc-complete

You've got to write the motivation to describe why we need to cherry-pick this PR. :)

You've got to write the motivation to describe why we need to cherry-pick this PR. :)
@mattisonchao Thanks for your point out. This PR needs to release on 2.10.3, so we need to cherry-pick it to branch-2.10.


Wordpress Input Validation

Description
The Input validation for Wordpress is not working correctly.
Name, Username
Only the min and max characters validation is applied but spaces, special characters are allowed and starting the name with a numeric value is allowed while it shouldn't.

Select Gateway Node
Basic Url validation should be added to this field

Country

Country Field should only accept alphabetical characters and spaces.

Farm Name

Should have the same constraints as the farm name field in the dashboard

No special characters except for - and _
Min 3 characters, max 40
Only alphabetic and numeric characters are allowed. no spaces.

Veified on devnet.

The name and username validation was fixed and now it only accepts alphanumeric values and can only start with a alphabetical value. and the Deploy button is disabled when there's a validation error.

Farm Name/Country/gateway fields were decided to remain the same since the values are listed below and no validation is needed for these fields.


⚠ Bofrost.be has degraded performance

In 732d5db, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1120 ms

Resolved: Bofrost.be performance has improved in 47392f4 after 22 minutes.


(Re)Surface the mlbox

This got lost in the shuffle while reorging the just files and toolboxes:
https://github.com/ublue-os/bluefin/blob/main/dx/usr/share/ublue-os/distrobox/pytorch-nvidia.ini
Maybe we should org this, vanilla pytorch and tensorflow in one just snippet with a selector?

Personally I use something like this for ml right now, since the pytorch image is huuge and sometimes I just want cuda
[mlbox-pytorch]
image=nvcr.io/nvidia/pytorch:24.03-py3
additional_packages="git nvtop btop"
init_hooks="pip3 install huggingface_hub tokenizers sentencepience transformers accelerate datasets peft bitsandbytes"
#pre-init-hooks="/init_script.sh"
nvidia=true
pull=true
root=false

[mlbox-cuda]
image=nvidia/cuda:12.4.1-devel-ubuntu22.04
additional_packages="git nvtop btop"
init_hooks="pip3 install huggingface_hub tokenizers sentencepience transformers accelerate datasets peft bitsandbytes"
#pre-init-hooks="/init_script.sh"
nvidia=true
pull=true
root=false

where should those lines go?

I'm using this now, got tired of writing anything else than mlbox, and added some typical packages I use.
[mlbox]
image=nvcr.io/nvidia/pytorch:24.03-py3
additional_packages="git git-lfs"
additional_packages="zsh zsh-antigen fzf findutils unzip strace ripgrep"
additional_packages="net-tools nmap openssl rclone rsync rclone"
additional_packages="make cmake clang clang-tools gcc jq"
additional_packages="nvtop neovim tmux htop iftop iotop"
init_hooks="pip3 install huggingface_hub tokenizers sentencepiece transformers accelerate datasets peft bitsandbytes poetry"
nvidia=true
pull=true
root=false

[mlbox-cuda]
image=nvidia/cuda:12.4.1-devel-ubuntu22.04
nvidia=true
pull=true
root=false
init=true

It should be added in
/etc/distrobox/distrobox.ini

I just managed to get a ROCm container working. If I may suggest adding this flavor as well:
[mlbox-rocm]
image=rocm/dev-ubuntu-22.04
additional_packages="git"
pre_init_hooks="mkdir /piptmp && TMPDIR=/piptmp pip3 install torch torchvision torchaudio --index-url https://download.pytorch.org/whl/rocm6.0"
init_hooks="pip3 install matplotlib huggingface_hub tokenizers transformers accelerate datasets peft bitsandbytes"
nvidia=true
pull=false
root=false


fix beam search - use correct states/contexts/features when creating …

…new beam
With this PR, results now match results from translate.lua from OpenNMT. It had been noted that these results don't match with a beam size greater than 1. This was due to incorrect creation of a new beam in the decoding steps.
In addition to creating the beam properly, I also added a few efficiencies: using a beam size of 1 on the first decoding step, and a smaller beam size on the step following when EOS is reached, plus a more efficient search on getting the next word for the hypotheses.

Thank you! I found the -save_beam_to option in translate.lua useful to verify that CTranslate is working the same way, with the same scores at each step, and added such an output in CTranslate while developing.


ci: Add job for publishing collection to Galaxy on new tag

microsoft-sql-2.5.1.tar.gz
Example collection artifact that I got from a test run

@richm WDYT? Please review only the first commit. The second commit is to run tests here.
I will need to add this to our .github automation.


Write to file

For anyone looking, for example for the generate_source macro, in order to write to file you can change line 77 in generate_source.sql ({{ log(joined, info=True) }}) to {{ print(joined) }} and then run:
dbt -q run-operation your_codegen_operation > file.yaml

This is a dupe of https://github.com/dbt-labs/dbt-codegen/issues/56

Yes but the other issue is very hard to find as its name is taken from the solution and not from the problem, so I just wanted to put this one here so the solution is easily discoverable.


anbox: unstable-2019-11-15 -> unstable-2020-11-29

Motivation for this change
Update to unbreak after gcc10 / binutils 2.34 update
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
[ ] other Linux distributions

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

Result of nixpkgs-review pr 108351 1

1 package built:

anbox

Result of nixpkgs-review pr 108351 1

1 package built:

anbox

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/324

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/324

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 108351 run on x86_64-linux 1

1 package built:

anbox

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 108351 run on x86_64-linux 1

1 package built:

anbox

Hi @SuperSandro2000, could this PR be merged?

Hi @SuperSandro2000, could this PR be merged?

You can also use https://github.com/timokau/marvin-mk2/blob/master/USAGE.md to help your PR to be merged.

You can also use https://github.com/timokau/marvin-mk2/blob/master/USAGE.md to help your PR to be merged.

/marvin opt-in
/status needs_merger

/marvin opt-in
/status needs_merger

You need to use needs_reviewer, someone else uses needs_merger.
/status needs_merger

You need to use needs_reviewer, someone else uses needs_merger.
/status needs_merger


Access Rails route helpers from Hyperloop

The ideal would be to access Rails route helpers verbatim just as you would in backend views or helpers. But the routing code is pretty tangled so I think it won't be possible to run it directly on the frontend without effort.
A workaround is to add .erb to component files and interpolate the route on the backend with static placeholder values, then gsub in real values on the frontend.
First, make it easier to access route helpers:
# config/initializers/routes.rb
class Routes
  include Singleton
  include Rails.application.routes.url_helpers

  def self.method_missing(name, *args, &block)
    if instance.respond_to?(name)
      instance.send(name, *args, &block)
    else
      super
    end
  end

  def self.respond_to_missing?(name, include_all = false)
    instance.respond_to?(name, include_all)
  end
end

Then in your ApplicationComponent add this helper to do the substitution:
class ApplicationComponent < Hyperloop::Component
  def rails_route(route, *positional, **named)
    route = route.split("/").reverse.join("/")
    positional.each_with_index do |replacement, i|
      route = route.sub(i.to_s, replacement.to_s)
    end
    named.each do |key, replacement|
      route = route.sub(key.to_s, replacement.to_s)
    end
    "/" + route.split("/").reverse.join("/")
  end
end

And finally use the mechanism in your components:
class CommentLink < ApplicationComponent
  param :comment

  render do
    A(href: rails_route(
      "<%= Routes.user_posts_comments_path(0, 1, "xyz") %>",
      User.current.id, params.comment.post.id, xyz: params.comment.id
    )) { "View Comment" }
  end
end

Using positional arguments is the easiest, but if your route contains numbers it won't work so explicitly name your arguments with placeholders that won't clash. The above example shows both.

I'm closing this, and moving it hyper-config, and also requesting documentation copy the good solution proposed above.


add in some background info about FW

Now that we've published blog posts about Finicky Whiskers, it would be great to tie them together so that folks who play the game can learn more.
I'd like to add in a subtle prompt like:

What is Finicky Whiskers? See what happens beneath the surface of 'The World's Most Adorable Manual Load Generator'

and link it to https://www.fermyon.com/blog/finicky-whiskers-part-1-intro

Absolutely!!!

The current version has the footer overlaying the buttons:

I think it's caused by this: https://github.com/fermyon/finicky-whiskers/pull/36

What do we want to do for this one?  Shall I deploy the earlier version to prod -- or are we looking at a fix prior to next week's conference?

Yeah it's on my list, need to fix it as soon as possible. Perhaps moving the banner to the top (above the progress bar) to avoid overlaps
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: Vaughn Dice @.>
Sent: Friday, June 17, 2022 8:27:26 AM
To: fermyon/finicky-whiskers @.>
Cc: Ronan Flynn-Curran @.>; Author @.>
Subject: Re: [fermyon/finicky-whiskers] add in some background info about FW (Issue #33)
What do we want to do for this one? Shall I deploy the earlier version to prod -- or are we looking at a fix prior to next week's conference?
—
Reply to this email directly, view it on GitHubhttps://github.com/fermyon/finicky-whiskers/issues/33#issuecomment-1158985177, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAFHQ4UPZSXNU4CJS5DFR3DVPSKN5ANCNFSM5YNZRZZA.
You are receiving this because you authored the thread.Message ID: @.***>


Invoke tasks

Add invoke tasks for running tests.
Also extracts dev-specific readme to doc/development.md.

@sc0tts this should be resolved by either creating a new VM (PR soon) or by updating your conda environment to include pyfakefs (mamba env update -n seaice_ecdr -f /home/vagrant/pm_tb_data/environment.yml)


Check that he upper-triangular from chol_factor by doing  np.triu(scl.cho_factor(Quu)) is the same as chol_solvers

In GitLab by @cmastalli on Apr 16, 2019, 17:58
The chol_solvers could take the alternative decomposition

In GitLab by @cmastalli on Jul 18, 2019, 17:31
We're moving to the c++ implementation. This isn't any more relevant

In GitLab by @cmastalli on Jul 18, 2019, 17:31
closed


[sw/sca] Optimize/Clean up code of batch modes in sca serial files

Description
This issue is related to https://github.com/lowRISC/opentitan/pull/17416
@jadephilipoom made some good points on the batch mode implementation in the ecc256_keygen_serial.c file, which are also valid to each batch mode implementation in the other serial files. Hence, these suggested modifications should be applied to every serial file.
The points are:

To fully comply with the style guide.
To remove the global key/message/seed/etc. arrays, which store all values from each batch, and instead allocate enough stack memory locally for a single key/message/seed/etc. value. If we then directly process each single value this would allow us to remove the maximum number of traces per batch and also the second for-loop.
To use memcpy(num_traces, data, data_len) instead of num_traces = read_32(data) . This is safer.

We just discussed in the SCA WG meeting, that this shouldn't be further investigated, and that the code should remain as it is. The proposed code changes cause to much "fake leakage", which makes analysis too difficult.
According to @vrozic this behavior was already observed for KAMC, which is the reason, why the code was changed to the current state in the first place.
Therefore, I'll close this issue.

However, I'd still like to see the other two points addressed as a follow-up to #17416, primarily so that coding style is consistent across the repo

Agree! Sorry, I overlooked that.


Support for passing/returning path expressions

Hey there!
Would it be possible to support passing a compiled expression to Warpath.query? We have a use case where we have a limited set of paths that we query over and over again on different data, and compiling the path only once would save us a ton of computation time.
Also, it would be great to be able to pass an option to return the compiled path from Warpath.query, instead of stringifying it with Warpath.Element.Path.bracketify. We want to use the returned path to then patch the term, and not having to re-compile the path would also make it easier to handle that case.
On a higher level, support for patching the term, instead of just querying it (the way that https://github.com/ostrovok-team/ejsonpath does), would be even better. But probably q lot more work.
Cheers and thanks for the great library 👍

https://github.com/Cleidiano/warpath/pull/28

Hi @jonasschmidt,
Add support to compiled expression make total sense, I'am very happy that you opened up a PR.
Currently I'am refactoring the parser grammar that could reflect in the Expression token names handled by Warpath, it's almost ready, but it need some adjust yet.
After the refactoring finish I think that support a option to return compiled expression path could be addressed.
I will keep your PR open until the refactoring is finished, this features will be  released on version 0.3.0.
Cheers.

Alright, that sounds good 👍

Return a path token where added at #50, and will be included in the next release. About support for patching I not sure if the Warpath will support this, currently the work is to make the Api stable and add missing features that is part of jsonpath.


Improve some typing in test_runner

Fixes some types, and replaces deprecated types.

I find pyright to be a lot more useful than mypy.

The fact that mypy passes on my machine, but not CI is very annoying :'(.

Almost all the regression test file changes you see in this PR are a result of me being blind and not reading the logs correctly. I think I'll probably reformat the commit message at the time of merge to say something a little more generic.

Can we enforce using the same style for type annotation everywhere with ruff / mypy? (for example using dict instead of Dict)
Otherwise, I'm afraid, the codebase will be more inconsistent.

https://docs.astral.sh/ruff/rules/deprecated-import/. I detect these issues with pyright. I would assume that mypy as this support?
I can open an additional PR to fix it everywhere, or do it as a precursor PR. What would you prefer?

I can open an additional PR to fix it everywhere, or do it as a precursor PR. What would you prefer?

It would be nice to open another PR with enabled checks and applying fixes to make sure we keep this code consistent.
Thank you!

See https://github.com/neondatabase/neon/pull/9349


Update Download Links - New Version of ODC

I know this should be a PR...  A new version of ODC was released - in addition we would prefer users to download the CLI from the github release rather than bintray due to bandwidth restrictions.
Please update:
https://github.com/dependency-check/azuredevops/blob/7580de253ae592e894d8fb8bb7bc97bc77887839/build/data-cache/data-cache.sh#L9
To point to the GitHub release to avoid capacity issues at bintray:
curl -sLo ./dependency-check-$VERSION-release.zip https://github.com/jeremylong/DependencyCheck/releases/download/v$VERSION/dependency-check-$VERSION-release.zip"

Additionally, update:
https://github.com/dependency-check/azuredevops/blob/360d647327c719d592888a15f0ba25b204fe3d96/src/Tasks/dependency-check-build-task/dependency-check-build-task.ps1#L119-L120
To:
Invoke-WebRequest "https://github.com/jeremylong/DependencyCheck/releases/download/v6.0.2/dependency-check-6.0.2-release.zip" -OutFile "dependency-check-6.0.2-release.zip"
Expand-Archive -Path dependency-check-6.0.2-release.zip -DestinationPath . -Force

@jeremylong , any timeline for when we can upgrade our task with this fix? All of our Dependency checker tasks are failing with a 403 because of this.

Working on it. Azure went down yesterday, which made it difficult to build / test. Should be today sometime.

Even after adding the lines for DependencyCheck v6.0.2, still getting the 403 ,forbidden error

I'm going to need the full scan output to trouble shoot this.

Working on it. Azure went down yesterday, which made it difficult to build / test. Should be today sometime.

Works now. Thanks for the quick turnaround.

today i am getting [ERROR] Error generating the report for RFPM-V2.0-UI-Dependency-Check
2020-09-30T04:54:10.5266725Z Dependency Check completed with exit code -12. Please suggest


Implement new ODE Monitor Action to monitor ODE Occurrences with a client callback function.

New ODE Action to monitor all ODE Occurrences as reported by the parent ODE Trigger. The Action will call a client provided monitor-callback function with a pointer to a structure of ODE occurrence information.
Four new sub-structures used to pass specific ODE occurrence information
/**
 * @struct dsl_ode_occurrence_source_info
 * @brief Video Source information for the ODE Occurrence provided to the
 * client on callback.
 */
typedef struct _dsl_ode_occurrence_source_info
{
    /**
     * @brief unique source id for this ODE occurrence.
     */
    uint source_id;

    /**
     * @brief the location of the frame in the batch for this ODE occurrence
     */
    uint batch_id;

    /**
     * @brief pad or port index of the Gst-streammux plugin for this ODE occurrence
     */
    uint pad_index;

    /**
     * @brief current frame number of the source for this ODE occurrence.
     */
    uint frame_num;

    /**
     * @brief width of the frame at input to Gst-streammux for this ODE occurrence.
     */
    uint frame_width;

    /**
     * @brief height of the frame at input to Gst-streammux for this ODE occurrence.
     */
    uint frame_height;

    /**
     * @brief true if inference was done on the frame for this ODE occurrence.
     */
    boolean inference_done;

} dsl_ode_occurrence_source_info;

/**
 * @struct dsl_ode_occurrence_object_info
 * @brief Detected Object information for the ODE Occurrence provided to the
 * client on callback.
 */
typedef struct _dsl_ode_occurrence_object_info
{
    /**
     * @brief class id for the detected object
     */
    uint class_id;

    /**
     * @brief unique id of the inference component that generated the object data.
     */
    uint inference_component_id;

    /**
     * @brief unique tracking id as assigned by the multi-object-tracker (MOT)
     */
    uint tracking_id;

    /**
     * @brief unique label for the detected object
     */
    const wchar_t* label;

    /**
     * @brief current "time in frame" if tracked - Persistence and Cross Triggers
     */
    uint persistence;

    /**
     * @brief direction of the Object if line cross event - Cross Trigger only.
     */
    uint direction;

    /**
     * @brief inference confidence as calculated by the last detector.
     */
    float inference_confidence;

    /**
     * @brief tracker confidence if current frame was not inferred on.
     */
    float tracker_confidence;

    /**
     * @brief the Object's bounding box left coordinate in pixels.
     */
    uint left;

    /**
     * @brief the Object's bounding box top coordinate in pixels.
     */
    uint top;

    /**
     * @brief the Object's bounding box width in pixels.
     */
    uint width;

    /**
     * @brief the Object's bounding box height in pixels.
     */
    uint height;

} dsl_ode_occurrence_object_info;

/**
 * @struct _dsl_ode_occurrence_accumulative_info
 * @brief Accumulative ODE Occurrence metrics provided to the
 * client on callback.
 */
typedef struct _dsl_ode_occurrence_accumulative_info
{
    /**
     * @brief the total number of object detection occurrences for the
     * frame-level ODE occurrence - Count, New-High, New-Low Triggers
     * or from an ODE accumulator.
     */
    uint occurrences_total;

    /**
     * @brief the number of Line-Cross ODE occurrences in the "in-direction".
     * Requires an ODE Cross-Trigger with ODE Accumulator
     */
    uint occurrences_in;

    /**
     * @brief the number of Line-Cross ODE occurrences in the "out-direction".
     * Requires an ODE Cross-Trigger with ODE Accumulator
     */
    uint occurrences_out;

} dsl_ode_occurrence_accumulative_info;

/**
 * @struct dsl_ode_occurrence_criteria_info
 * @brief ODE Trigger Criteria used for the ODE Occurrence.
 */
typedef struct _dsl_ode_occurrence_criteria_info
{
    /**
     * @brief class id filter for ODE occurrence
     */
    uint class_id;

    /**
     * @brief inference id filter for ODE occurrence
     */
    uint inference_component_id;

    /**
     * @brief the minimum inference confidence to trigger an ODE occurrence.
     */
    float min_inference_confidence;

    /**
     * @brief the minimum tracker confidence to trigger an ODE occurrence.
     */
    float min_tracker_confidence;

    /**
     * @brief inference must be performed to trigger an ODE occurrence.
     */
    boolean inference_done_only;

    /**
     * @brief the minimum bounding box width to trigger an ODE occurrence.
     */
    uint min_width;

    /**
     * @brief the minimum bounding box height to trigger an ODE occurrence.
     */
    uint min_height;

    /**
     * @brief the maximum bounding box width to trigger an ODE occurrence.
     */
    uint max_width;

    /**
     * @brief the maximum bounding box height to trigger an ODE occurrence.
     */
    uint max_height;

    /**
     * @brief the interval for checking for an ODE occurrence.
     */
    uint interval;

} dsl_ode_occurrence_criteria_info;

Top level structure passed to the client on callback
/**
 * @struct dsl_ode_occurrence_info
 * @brief ODE Occurrence information provided to the client on callback
 */
typedef struct _dsl_ode_occurrence_info
{
    /**
     * @brief the unique name of the ODE Trigger that triggered the occurrence
     */
    const wchar_t* trigger_name;

    /**
     * @brief unique occurrence Id for this occurrence.
     */
    uint64_t unique_ode_id;

    /**
     * @brief Network Time for this event.
     */
    uint64_t ntp_timestamp;

    /**
     * @brief Video Source information this ODE Occurrence
     */
    dsl_ode_occurrence_source_info source_info;

    /**
     * @brief true if the ODE occurrence information is for a specific object,
     * false for frame-level multi-object events. (absence, new-high count, etc.).
     */
    boolean is_object_occurrence;

    // NOTE: object_info and accumulative_info are mutually exclusive
    // determined by the boolean is_object_occurrence flag above.

    /**
     * @brief Object information if object_occurrence == true
     */
    dsl_ode_occurrence_object_info object_info;

    /**
     * @brief Accumulative information if object_occurrence == false
     */
    dsl_ode_occurrence_accumulative_info accumulative_info;

    /**
     * @brief Trigger Criteria information for this ODE occurrence.
     */
    dsl_ode_occurrence_criteria_info criteria_info;

} dsl_ode_occurrence_info;

New Client Callback function for the ODE Monitor Action
/**
 * @brief Callback typedef for a client ODE occurrence monitor function.
 * Once registered by calling dsl_ode_action_monitor_new, the function will be called
 * on ODE occurrence with all occurrence information using the dsl_ode_occurrence_info
 * structure.
 * @param[in] occurrence_info occurrence information on ODE occurrence.
 * @param[in] client_data opaque pointer to client's user data
 */
typedef void (*dsl_ode_monitor_occurrence_cb)(dsl_ode_occurrence_info* occurrence_info,
    void* client_data);

New Constructor for the ODE Monitor Action
/**
 * @brief Creates a uniquely named Monitor ODE Action.
 * @param[in] name unique name for the Monitor ODE Action.
 * @param[in] client_monitor function to call on ODE occurrence.
 * @param[in] client_data opaue pointer to client's user data, returned on callback.
 * @return DSL_RESULT_SUCCESS on success, one of DSL_RESULT_ODE_ACTION_RESULT otherwise.
 */
DslReturnType dsl_ode_action_monitor_new(const wchar_t* name,
    dsl_ode_monitor_occurrence_cb client_monitor, void* client_data);

complete - merged into v0.24.alpha


bluebones has issues with 'ae'

It respects neither the ligature nor the ae version of names like "Aether Rift". It needs to at least support the modern spells. This is probably (?) because magiccards.info hasn't switched off the ligature yet.

The proximate cause is that the initial data generated to run the bluebones proxy service has no printings for Aether Rift and similar:
'aether rift' => array(
),
'armored guardian' => array(
'inv' => 22263,
'invasion' => 22263,
'default' => 22263,
),

Fixed. Was an issue in the generator code using the ligature string from mci and the non-ligature string from mtgjson and finding them not equal.


♻ Update the breadcrumb links to be relative instead of absolute

Cc: @adamcogan @tombui99
Hi @bradystroud
Pain
As per https://github.com/SSWConsulting/SSW.CodeAuditor/issues/417
CodeAuditor is catching many errors because the breadcrumbs paths on SSW.Rules are absolute
Tasks

[ ] Make the breadcrumbs links relative

Figure: All errors in the same line (breadcrumb)
Thanks!

CC: @bradystroud
It looks like the breadcrumbs are already relative.

Hey @tombui99
Based on the latest report, this problem is still apprearing on CodeAuditor (same line 834 for all pages)
Maybe I missinterpreted the cause here...

Can you investigate what's causing these errors and a potential fix?

Hi @BrookJeynes
cc @tiagov8 @bradystroud
From the latest scans on SSW Rules, I still see this error being reported in some places
See https://codeauditor.com/htmlhint/7a8ea4b6-6942-4a43-f848-b7a4d66d8797?displayMode=1

Can you have a look and fix them

Thanks a lot!
Tom

Closing as per the latest scan there are no more detections - https://codeauditor.com/htmlhint/366f7bbc-d964-45e0-9eb3-f0c1a00c0037?displayMode=1


fix:users are able to save global config-maps/secrets for a app without saving deployment templates via API

Description
Users are able to save global config-maps/ secrets for a app without saving deployment templates via API
Fixes #1767
How Has This Been Tested?
All tests are performed locally
Checklist:

[x] The title of the PR states what changed and the related issues number (used for the release note).
[ ] Does this PR requires documentation updates?
[ ] I've updated documentation as required by this PR.
[ ] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[ ] I have tested it for all user roles.
[x] I have added all the required unit/api test cases.

Does this PR introduce a user-facing change?

Not a bug, as we have started integrating  CM/CS in jobs also, where deployment template is not present.


Organize the variable section

Make a provision to get an organized view of the variable section. Like display the top ten variable that raises a warning or missing value errors etc.. and then toggle to get details about more variables. This will be very helpful if the data set contains huge number of variables

hey there! I just discovered pandas-profiling and I'm so in love I want to help somehow.
can I try this one? (:


Remove image user

Checklist before submitting

[x] Did you read the contributor guide?
[ ] Did you update any affected documentation?
[ ] Did you write any tests to validate this change?

Description
Fixes #21
This PR will:

Make sure environment variables are setup correctly for both the root user and builder user within the image.
Run as the builder user within the container when launching --container_build with --docker_tool docker as a non-root user.
Run as the root user within the container when launching --container_build with --docker_tool docker as the root user.
Run as the root user within the container when launching --container_build with --docker_tool podman.
Cleans up the Dockerfiles some as well. Removing some unnecessary commands.
Moves the code for fixing conda environment files channels to container_build.py.

Review process to land

All tests and other checks must succeed.
At least one maintainer must review and approve.
If any  maintainer requests changes, they must be addressed.

It would be good if we can avoid call to _home_path at so many places by having a variable or an argument. Otherwise it looks good.

Yeah, that is a good idea. I created local variables for functions that called _home_path more than once.


Fix core integration tests (minor)

Add missing super.modifyConfigs() to BaseRequestTest (else test-case modfications of serverConfig are ignored). This fix doesn't appear to affect any existing tests, but it did break a test I was writing recently (later bypassed by inheriting from a superclass of BaseRequestTest rather than from a subclass). Future-proofing.
Fix a race condition in PlaintextAdminIntegrationTest (premature call to describeLogDirs() before all logDirs are created). This test case (testDescribeLogDirs()) fails 100% of the time on my Azure Linux VM.

First fix was verified via the subsequently modified test mentioned above (and by visual inspection), and second fixes the 100% failure rate on my VM.

  Discarding.


Subscriptions

Depends on #6
Introduces Subscriptions, which allow models to passively listen to side effects originating from the system.

Codecov Report

Merging #7 into master will decrease coverage by 28.98%.
The diff coverage is 41.17%.

@@             Coverage Diff             @@
##           master       #7       +/-   ##
===========================================
- Coverage     100%   71.01%   -28.99%
===========================================
  Files           4        6        +2
  Lines          35       69       +34
===========================================
+ Hits           35       49       +14
- Misses          0       20       +20

Impacted Files
Coverage Δ

Source/Subscription.swift
0% <0%> (ø)

Source/Model.swift
100% <100%> (ø)

Source/App.swift
77.77% <45.45%> (-22.23%)
:arrow_down:

Source/Processor.swift
68.42% <53.84%> (-31.58%)
:arrow_down:

Continue to review full report at Codecov.

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


Cannot flash firmware

Hello!
I cloned the repository and tried to perform the steps as documented in the section Building and flashing the application.

(make -j) was successful
Connected the board to the computer
Tried to flash the board; error message was:

arm-none-eabi-ld: Error: unable to disambiguate: -nostartfiles (did you mean --nostartfiles ?)
make: *** [Makefile:278: build/firmware.elf] Error 1

Is there a workaround to correct my mistake, please?
Thanks.

Hi @baqwas,
Could you check if you meet all requirements?
Also, could you write what your operating system and version are? Additional terminal output also would be helpful.

Hello @mmajchrzycki,
My mistake was that I did not realize that a specific version of Python was needed for the install to proceed to successful conclusion. That requirement was not documented anywhere. Several helpful folks pointed out that issue to me. I logged the issue without realizing this fact since I had used other variations of the utility from the same platform for over a year now (Ubuntu 21.04, 21.10 & 22.04). I'm closing the issue because I cannot retro on this specific platform and venv is not an option for me tactically. I hope to build another crash-and-burn platform where I will install venv and then explore various versions of Python as needed. Thanks for fielding the issue.
Kind regards.


Why radius?

I think there a typo, because documents written diameter
(integer $radius)
@method \Intervention\Image\Image circle(integer $radius, integer $x, integer $y, \Closure $callback = null)

https://github.com/Intervention/image/blob/master/src/Intervention/Image/Image.php#L14

https://github.com/Intervention/image/issues/265


Phosphor icons in Unicode

I have a question: will we be able to use Phosphor icons in Unicode to use them directly in CSS in the future? Let's say I want to add an icon before the text within a <div> using Unicode, will we have that option in the future like some other icon fonts like FontAwesome do?

Our @phosphor-icons/web library is implemented as an icon font. Though we don't have a dictionary of Unicode code points for each icon (duotone weight actually uses 2 code points), you can inspect the stylesheet of one of the weights to see what glyphs map to what code points.
From there, it's a matter of using one of our fonts in your <div>, and printing the right unicode character.
Unfortunately we don't support font ligatures any more, but it's something we're hoping to bring back.


bob:  verify ordering of actual/expected

In the Jasmine testing framework, it is convention to:
expect(actual).fn(expected)

But some test suites have the following:
expect(expected).fn(actual)

This causes the error messages to be confusing.
Please verify the bob exercise to make sure that the expectations are ordered correctly. If they are, then this can be closed.
This issue will help to close #111

got it

This one is OK and can be closed.

Grrrrrreat!


Added timestamp string def

Returns date & time as a string, useful to backup config files
prior to changing them with templates.

I'm not sure node is a good place for this to live. Node generally is used to get information about the node. You could perhaps stretch this a little and say its the current time on the node, like node.time or something of that nature.


Tips for debugging failed fetches?

I have not yet had success with fetch queries to my remote graphql server (Hasura). I'm getting a Cannot read property 'data' of undefined error, and after adding logging to the environment.js my best guess is that it's not even attempting to fetch since the logging isn't appearing. I'm not clear on the best way to debug this issue, and am hoping a solution here will help others.
My query is adapted straight from the documentation:
	import { query, graphql, AllUsers } from '$houdini';
	const { data } = query<AllUsers>(graphql`
		query AllUsers {
			kl_users {
				email
				uid
			}
		}
	`);

and the error is:
Cannot read property 'data' of undefined
TypeError: Cannot read property 'data' of undefined
    at Module.query (/$houdini/runtime/query.js:15:48)
    at Login.svelte:33:29
    at Object.$$render (<PATH>/node_modules/svelte/internal/index.js:1380:22)
    at eval (/src/lib/layout/Header.svelte:15:115)
    at Object.$$render (<PATH>/node_modules/svelte/internal/index.js:1380:22)
    at eval (<PATH>/src/routes/$layout.svelte:42:94)
    at Object.$$render (<PATH>/node_modules/svelte/internal/index.js:1380:22)
    at root.svelte:31:44
    at $$render (<PATH>/node_modules/svelte/internal/index.js:1380:22)
    at Object.render (<PATH>/node_modules/svelte/internal/index.js:1388:26)

Hey @thormuller!
It might help to understand what the generated load function looks like so you can add logs in the right spot to capture the information you are investigating. At the moment, the most reliable place to see this is one of the snapshot tests. The top snapshot is what is generated for the load function and the second snapshot is what's left behind of your component. If you want to just test that load is being called where/when you think it is, you can add a console.log in the constructor for RequestContext. You find a very similar file to the one in that link inside of $houdini/runtime/network.js.
It's probably worth mentioning, for anyone who finds this issue that the first request your application fires will get logged on your server, not in the browser console. Queries that fire after the first request will be sent from your browser and logged in the browser's console.

Brilliant, thanks for the tips. I'll give that a go.

The issue is with line 15 in query.js:
const initialValue = document.initialValue.data;
There is no initialValue on document which leads to the aforementioned error. Does that imply that something is off in the configuration somewhere? The document object in query.js looks like this:
{
  initialValue: undefined,
  variables: undefined,
  kind: 'HoudiniQuery',
  artifact: {
    name: 'AllUsers',
    kind: 'HoudiniQuery',
    hash: '3509969641628a2b17ad4cbc3c28a55b',
    raw: 'query AllUsers {\n  kl_users {\n    email\n    uid\n  }\n}\n',
    rootType: 'query_root',
    selection: { kl_users: [Object] }
  }
}

Hm, well getting that far means the load function didn't see an error in the response. It also means that the data field in the response is undefined Having a query with no value and no errors seems like something is going on with the requests to the server.
Are you seeing load invoked when you navigate to a route?
Regardless, we clearly need a better error message if query is invoked with an undefined initial value.

I'm not seeing the log message when I load the route with the query. I'd think the load would happen before the query was fired, but I see no evidence of it. The log is in network.js like so:
export class RequestContext {
    constructor(ctx) {
        console.log("network.js")
        this.continue = true;
        this.returnValue = {};
        this.context = ctx;
    }

Do you see anything if you add a log on the api side of resolving kl_users?
Is this the same repo you shared earlier? If so, mind pushing it up so I can take a closer look? I dont need access to a working API in order to see your problem so no need to worry about making that available

Thanks! Just pushed the latest up to that repo. I hope this proves useful for general purposes!

FYI, logging confirms the graphql api is not receiving any requests, while it is receiving Apollo requests from the same SvelteKit app just fine.

@thormuller I ran into something interseting while debugging this - if I change /src/routes/qry/index.svelte to look like
<script>
	import { query, graphql } from '$houdini';
	const { data } = query(graphql`
		query AllUsers {
			kitchenlab_users {
				email
				uid
			}
		}
	`);
</script>

{$data.kitchenlab_users.length}

Then I see the query being fired and a result is rendered. I'm going to keep poking at this to see if i can figure out the difference between this page the Login component but at least there is some progress.

Ah, I think i have found the problem. The loading documentation says that:

load only applies to components that define pages, not the components that they import.

So I think this means that, at the moment, query only functions in pages and layouts (ie, things that are inside of src/routes). This is definitely not intended - query should absolutely work the way you expected. I'll try to get something out in the coming days to support this

Aha, that makes sense. I can work around this in my situation. Again, many thanks for investigating my code–at least it seems like a useful case for future development. I'll stay tuned for how I can help this project as it blossoms!

No problem at all! I'm very excited to hear that at someone else is going to be using houdini - especially since you are clearly willing to opening tickets when you run into issues 😄
I'm currently trying to gather some people I can reach out to in order to validate PRs coming out. Would you mind if I tag you when I add support for query outside of pages/and layouts to test?

Absolutely! Happy to help.

Supporting queries outside pages is a must however svelte ssr in my understanding isn't async the only way to fetch is per load/preload i believe. What im curious about is what you will do for variables/function. Since there is no load in Components we will pass the variables directly to the query or what will/should it look like? Also this could be a good point to think about the api for variables. I don't know if i like the current approach.

@pixelmund - I agree that the current approach is kind of clunky. However, i'm not sure if there is an alternative. Definitely open to alternatives!
in order to get access to the page variables (so users can do something like pull a filter value from the url) the actual logic for computing the variable needs to be accessible in the module script where the actual network request happens. If the variables were just a static value, this wouldn't be a problem - the preprocessor could just copy the value up to the right script. Unfortunately that's too big of a limitation since a user could put all sorts of complicated in that function. That means that the preprocessor would be forced to hoist up any necessary logic to perform the computation. By forcing the user to define their variable function in the module context, we can guarantee that anything that the user used to compute their variables is also accessible to the load function without any complicated hoisting logic.

That makes completely sense to me. I can't think of another alternative, so explaining why it is like that would probably be the best decision right now.

@thormuller I think I have a working update to support query in a component outside of src/routes. Mind pulling down #95 and giving it a shot?


Enable Verilator in the RTL Simulation Flow for SweRV integration

I think this was where this was added? https://github.com/Lampro-Mellon/LM-RISCV-DV/pull/81

Yes, it was added there.


Remove branches from Repr::as_slice()

This change optimizes Repr::as_slice(), which is used e.g. in CompactStr::as_str().
This is done by replacing last_byte == HEAP_MASK || last_byte == STATIC_STR_MASK with last_byte >= HEAP_MASK, because we know that there can be no other case.
Also is self.last_byte() is called multiple times instead of using the "cached" value. This lets the optimzer decide whether to access the same variable again or use a register. And reassigning the variable pointer for the >= HEAP_MASK case is done immediately. Both changes together reduce the "percived" register pressure of the compiler, so it will be more eager to omit branches.

Amazing, thank you!


Fix https://issues.redhat.com/browse/MODCLUSTER-721

The fix removes the messup with the good mod_proxy default values.
upstream PR: https://github.com/modcluster/mod_proxy_cluster/pull/27

retest this please


Cant install Backpack 4.0 on Laravel 6.0

Bug report
New project on Laravel6 and following backpack doc, do composer require backpack/crud and composer try to install BP3.6, installation failed.
There is a way to install BP4.0 on L6.0, its stable? Or maybe BP3.6 on L6.0? Im starting a new project and want to be updated.
Thanks

Hi @rodrigouriarte05 ,
I've just pushed support for Laravel 6 in Backpack 3.6. The v4 branch will get it soon enough (later today).
Cheers!

Haha. Smooth :-)
Yes, you can go back to it looking like CoreUI (sidebar and header) by changing two config values in config/backpack/base.php:
    // Horizontal navbar classes. Helps make the admin panel look similar to your project's design.
-    'header_class' => 'app-header bg-transparent border-0 navbar position-relative',
+    'header_class' => 'app-header border-0 navbar position-relative',

    // Sidebar element classes.
-    'sidebar_class' => 'sidebar sidebar-pills sidebar-bg-transparent',
+    'sidebar_class' => 'sidebar',

The success/error/warning/info colors will still be Backstrap, though - we tweaked those a little bit. and how the inputs look. But I don't think those will be the thing people have a problem with, but the transparent sidebar and header. Which is... better in my opinion. Since it helps the design draw attention to the content, not the menus. But it's opinionated nonetheless, so expect plently of people will want to change it :-)

I am having similar issues when installing the v4 beta on a clean install of laravel 6 running php 7.2. My packages folder looks like the one above.
The source code shows there are still css files and javascript files trying to be pulled from vendor/adminlte This is what my page looks like:

Experiencing the same (looks exactly like this screenshot). Tried upgrading 3.6 to 4 using the upgrade guide. AdminLTE is installed by composer for some reason. HTML looks like a hybrid 3.6/4 and I have no custom views.

@martijnb92 that's great! (that we can debug this now; not that you're having problems 😄  )
How about after a php artisan view:clear and php artisan cache:clear ?

Unfortunately that did not change anything. Also tried removing the whole vendor folder. Maybe it has something to do with de base/crud merge? backpack/base is also being installed by composer. Lastly I tried php artisan backpack:install but that didn’t help either, except that I got two new blade topbar left/right files.

Hmm.... can I please see your composer.json file?

{
"name": "laravel/laravel",
"type": "project",
"description": "The Laravel Framework.",
"keywords": [
"framework",
"laravel"
],
"license": "MIT",
"require": {
"php": "^7.2",
"backpack/crud": "v4.x-dev",
"barryvdh/laravel-dompdf": "^0.8.4",
"fideloper/proxy": "^4.0",
"laravel/framework": "^6.0",
"laravel/tinker": "^1.0"
},
"require-dev": {
"backpack/generators": "^1.2",
"beyondcode/laravel-dump-server": "^1.0",
"filp/whoops": "^2.0",
"fzaninotto/faker": "^1.4",
"laracasts/generators": "dev-master",
"mockery/mockery": "^1.0",
"nunomaduro/collision": "^2.0",
"phpunit/phpunit": "^7.0"
},
"config": {
"optimize-autoloader": true,
"preferred-install": "dist",
"sort-packages": true
},
"extra": {
"laravel": {
"dont-discover": []
}
},
"autoload": {
"psr-4": {
"App\": "app/"
},
"classmap": [
"database/seeds",
"database/factories"
]
},
"autoload-dev": {
"psr-4": {
"Tests\": "tests/"
}
},
"minimum-stability": "dev",
"prefer-stable": true,
"scripts": {
"post-autoload-dump": [
"Illuminate\Foundation\ComposerScripts::postAutoloadDump",
"@php artisan package:discover --ansi"
],
"post-root-package-install": [
"@php -r "file_exists('.env') || copy('.env.example', '.env');""
],
"post-create-project-cmd": [
"@php artisan key:generate --ansi"
],
"post-update-cmd": [
"@php artisan vendor:publish --provider='Backpack\CRUD\BackpackServiceProvider' --tag=public --force"
]
}
}

"backpack/generators": "^1.2"
Appears to be causing the trouble! :)

Exactly! Thanks a lot this back-and-forth @martijnb92 . I've updated the upgrade guide to mention that you also need "backpack/generators": "^2.0" in require-dev.
Cheers!

@tomsb just added more docs for changing the top menu and sidebar colors, for a different look & feel. Ended up documenting a few good examples too, with screenshots.

I just stumbled on this issue as well.. I did not realize Backpack 4 was still in Beta since there seems to be no obvious indication of this anywhere. Maybe I'm just blind but the only place I even see 'beta' is as part of these instructions
# Note during v4 beta - this might NOT have v4 support yet
composer require webfactor/laravel-generators --dev

Which lead to an error
@tabacitu Why not remove this line of instructions altogether since it just doesn't work at the moment?

Note that using "webfactor/laravel-generators": "dev-master" works as a result of https://github.com/webfactor/laravel-generators/commit/e325b434b8e199539ab1635fabbd85ee632037f3, so the instructions should be changed to
composer require webfactor/laravel-generators:dev-master --dev

@vesper8 v4 is not in beta right now - it's stable. Just forgot that notice since it was in beta (the beta docs have become the v4 docs). I've removed them like you suggested, you're right.
As far as I know, webfactor/laravel-generators does provide V4 support on dev-master, but the controllers aren't updated for v4, I'll make sure to spend some time and help the guys upgrade too. I do plan to improve how we generate things A LOT in the coming months.


Inclusion of license agreement if imported only

Hello guys,
your package is really very useful, but I'm not clear with the BSD 3-clauses license under the following conditions:

I have a script that import pyautogui package;
The folder containing ONLY the script is distributed in bytecode or by one of the python installers (eg pypi or wheel);
In the distribution there is no source code nor bytecode of pyautogui (but will be automatically downloaded by the installer or manually by the user before installing my script).

In this case, do I have to include your license agreement in my distribution?
Thanks for your support.

It's my understanding that if you're specifying pyautogui as a requirement in your package, but not copying the code into your codebase, then you aren't "redistributing" the package. You're just telling the user they need to install it (which their copy of pip usually handles automatically).


[Feature] Add support for input cache

See the description at this page.
Provide support for the input cache.

Available in release 2022-11-28


Terminal: integration tests do not run to completion on Windows

Steps:

Windows 10 (latest 1903 Build 18362.175)
fresh checkout and yarn install
run scripts\test-integration.bat

←[0m    Terminal←[0m
    ←[32m  ΓêÜ←[0m←[90m sendText immediately after createTerminal should not throw←[0m
[3928:0618/115930.995:INFO:CONSOLE(139)] "%c  ERR", source: file:///C:/GitDevelopment/monaco/out/vs/platform/log/common/log.js (139)
    ←[32m  ΓêÜ←[0m←[90m onDidCloseTerminal event fires when terminal is disposed←[0m←[31m (237ms)←[0m
[3928:0618/115931.622:INFO:CONSOLE(139)] "%c  ERR", source: file:///C:/GitDevelopment/monaco/out/vs/platform/log/common/log.js (139)
    ←[32m  ΓêÜ←[0m←[90m processId immediately after createTerminal should fetch the pid←[0m←[31m (655ms)←[0m
    ←[32m  ΓêÜ←[0m←[90m name in constructor should set terminal.name←[0m
[3928:0618/115931.773:INFO:CONSOLE(139)] "%c  ERR", source: file:///C:/GitDevelopment/monaco/out/vs/platform/log/common/log.js (139)
    ←[32m  ΓêÜ←[0m←[90m onDidOpenTerminal should fire when a terminal is created←[0m←[31m (113ms)←[0m
    ←[32m  ΓêÜ←[0m←[90m createTerminalRenderer should fire onDidOpenTerminal and onDidCloseTerminal←[0m←[31m (115ms)←[0m
[3928:0618/115932.200:INFO:CONSOLE(139)] "%c  ERR", source: file:///C:/GitDevelopment/monaco/out/vs/platform/log/common/log.js (139)
[3928:0618/115932.690:INFO:CONSOLE(139)] "%c  ERR", source: file:///C:/GitDevelopment/monaco/out/vs/platform/log/common/log.js (139)
    ←[32m  ΓêÜ←[0m←[90m terminal renderers should get maximum dimensions set when shown←[0m←[31m (917ms)←[0m
    ←[32m  ΓêÜ←[0m←[90m TerminalRenderer.write should fire Terminal.onData←[0m←[31m (114ms)←[0m
    ←[32m  ΓêÜ←[0m←[90m Terminal.sendText should fire Terminal.onInput←[0m←[31m (116ms)←[0m
    ←[32m  ΓêÜ←[0m←[90m onDidChangeActiveTerminal should fire when new terminals are created←[0m←[33m (57ms)←[0m
[3928:0618/115933.723:INFO:CONSOLE(139)] "%c  ERR", source: file:///C:/GitDevelopment/monaco/out/vs/platform/log/common/log.js (139)
    ←[32m  ΓêÜ←[0m←[90m onDidChangeTerminalDimensions should fire when new terminals are created←[0m←[31m (998ms)←[0m
[3928:0618/115934.197:INFO:CONSOLE(139)] "%c  ERR", source: file:///C:/GitDevelopment/monaco/out/vs/platform/log/common/log.js (139)
rejected promise not handled within 1 second: TypeError: name.charCodeAt is not a function
stack trace: TypeError: name.charCodeAt is not a function
    at Object.get (c:\GitDevelopment\monaco\out\vs\workbench\services\extensions\common\file:\C:\GitDevelopment\monaco\src\vs\workbench\services\extensions\common\rpcProtocol.ts:184:31)
    at formatValue (util.js:545:28)
    at formatProperty (util.js:1194:11)
    at formatObject (util.js:900:17)
    at formatValue (util.js:808:14)
    at inspect (util.js:371:10)
    at new AssertionError (internal/assert.js:252:19)
    at innerFail (assert.js:83:9)
    at Function.equal (assert.js:364:5)
    at vscode_1.window.onDidChangeTerminalDimensions (C:\GitDevelopment\monaco\extensions\vscode-api-tests\src\singlefolder-tests\window.test.ts:703:12)
    at Emitter.fire (c:\GitDevelopment\monaco\out\vs\base\common\file:\C:\GitDevelopment\monaco\src\vs\base\common\event.ts:558:16)
    at define.$acceptTerminalDimensions._getTerminalByIdEventually.then.terminal (c:\GitDevelopment\monaco\out\vs\workbench\api\node\file:\C:\GitDevelopment\monaco\src\vs\workbench\api\node\extHostTerminalService.ts:396:42)
[main 2019-06-18T10:00:13.543Z] [VS Code]: detected unresponsive

This is bad enough that it seems to hang the window and then killing the process via Ctrl+C I see lots of conhost.exe consuming lots of CPU:

I had to comment them out: https://github.com/microsoft/vscode/commit/356440d72d7b93f61095eedea4ad4e20cef93a5e

Reproduced the hang with an extension:
vscode.window.createTerminal().dispose();

Might have just started happening if the CI machines updated to Windows 1903 which is rolling out to users now.

Root cause: https://github.com/microsoft/vscode/issues/76548, forcing winpty during tests could work around this.


Need a valid "redirect_uri" to get my access token

I'm following the procedure to get my access token, and the first dialog asks for three parameters including an URL, which isn't indicated in the instructions.
So could you please complete this URL for me ? (ie replace YOUR_REDIRECT_URI) ::
https://connect.deezer.com/oauth/auth.php?app_id=247082&redirect_uri=YOUR_REDIRECT_URI&perms=basic_access,email,manage_library
Thank you very much

Thank you @blackccpie & @hartmannn. I got Deezzy working with my account thanks to your exchanges here. =oD Been waiting a long time to use Deezer on my Raspberry Pis!

@tyrower : great, glad to hear that!

help me please, what exactly i should write in redirect -_- i tried on http://localhost:3000/, and its failed,tried on https://muz-project-gray.vercel.app/ and had the same( i tried with htttp, https, with no htttp\s ... same result ( ivalid redirect url and no deezer code :c


Bulk

Hi,
Your boilerplate works fine when I followed the steps in your readme.
But, unfortunately I can't use your boilerplat as is. So, I am just trying to get the browserify part of this work in my existing code base. I am getting a weird error in the _index.js file.
 Is there any other dependencies that I need to install to get buld-require working?
Can I use https://github.com/aseemk/requireDir instead of bulk-require?

I managed to fix this by using bulkify and brfs. Couldn't delete or close this issue ticket.


Add new section title in Settings page "When completing transcription"

Noting that all items in the Settings page are under a section title except the two toggle controls which both relates to actions to be performed when completing transcription, this PR is a proposal to add a section title "When completing transcription" for them.

Sorry I messed my git pull, only the 5 last commits of this PR are meant to be new.
Also if this is merged, then #93 should not be merged.

I changed a bit the design and added some missing translation.
I think you'll find this VSCode extension useful: i18n-ally
That's great improvement! now that section in settings is much more clear.
I'll merge it and it will be available in latest release binaries soon since I need to push small fixes to existing binaries :)
Thanks!


feat: update requiremnts for use with statamic v4

Test setup in .github/workflows/run-tests.yml needs to be extended/adjusted.


Compile error

I tried to compile the project, but got the following error
> Task :module:externalNativeBuildRelease FAILED
Build riru_il2cppdumper_armeabi-v7a
ninja: error: 'C:/Users/leo/tmp/Riru-Il2CppDumper/module/src/main/cpp/main.cpp', needed by 'CMakeFiles/riru_il2cppdumper.dir/main.cpp.o', missing and no known rule to make it

FAILURE: Build failed with an exception.

> * What went wrong:
> Execution failed for task ':module:externalNativeBuildRelease'.
> > Build command failed.
>   Error while executing process F:\leo\Android\Sdk\cmake\3.6.4111459\bin\cmake.exe with arguments {--build C:\Users\leo\tmp\Riru-Il2CppDumper\module\.cxx\cmake\release\armeabi-v7a --target riru_il2cppdumper}
>
>   ninja: error: 'C:/Users/leo/tmp/Riru-Il2CppDumper/module/src/main/cpp/main.cpp', needed by 'CMakeFiles/riru_il2cppdumper.dir/main.cpp.o', missing and no known rule to make it

I also encountered the same error.
How can I solve it?


Don't complain about modules and outFile options when emitDeclarationOnly is set.

Fixes #27117.

Thanks as usual Matt!


Fix BMS faulting while trying to charge due to missing heartbeats

Summary
BMS faults out when on bench due to missing heartbeats. This is annoying when we are trying to charge, since the accumulator is out of the car.

Moved to Jira.


fix: Queued segment looping until cleared manually

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Bug fix in the Queued (Next) Segment feature

What is the current behavior? (You can also link to an open issue here)
In various edge cases the queued segment starts looping infinitely (until cleared manually), or is queued an extra time.
Sample steps to reproduce the unwanted behavior:
Case 1:

Take a Part in segment A
Queue segment B
Set first part of Segment B as next
Queue Segment A twice
Take - Segment A will loop until manually unqueued

Case 2:

Take the first part in a segment (A) that has multiple parts
Queue a segment (B) that has only one part
Set as next segment B
Take - Segment A will loop until manually unqueued

Case 3:

Take the first part in a segment A, that has multiple parts
Queue segment B, that has only one part
Take, Take (reaching B) - B will be set as next once more

The causes of the issue: Wrong order of selecting next part and clearing nextSegmentId during a take. Not applying consumesNextSegmentId to reused partInstances. Not clearing nextSegmentId when user queues a segment while being on the last part of the current segment.

What is the new behavior (if this is a feature change)?
Queued segment no longer loops infinitely, nor is queued more times than expected.

Other information:

Status

[ ] Code documentation for the relevant parts in the code have been added/updated by the PR author
[x] The functionality has been tested by the PR author
[ ] The functionality has been tested by NRK

Codecov Report

Merging #620 (9390098) into release38 (77853ee) will increase coverage by 15.02%.
The diff coverage is n/a.

:exclamation: Current head 9390098 differs from pull request most recent head 6611844. Consider uploading reports for the commit 6611844 to get more accurate results

@@              Coverage Diff               @@
##           release38     #620       +/-   ##
==============================================
+ Coverage      67.43%   82.46%   +15.02%
==============================================
  Files            264       12      -252
  Lines          18429     1015    -17414
  Branches        4104      198     -3906
==============================================
- Hits           12428      837    -11591
+ Misses          5960      177     -5783
+ Partials          41        1       -40

Impacted Files
Coverage Δ

meteor/lib/lib.ts

meteor/lib/rundown/infinites.ts

meteor/server/api/playout/lib.ts

meteor/server/api/playout/lookahead/index.ts

meteor/server/api/playout/playout.ts

meteor/server/api/playout/take.ts

meteor/server/api/playout/timeline.ts

meteor/server/api/systemTime/systemTime.ts

meteor/server/api/userActions.ts

meteor/server/api/http.ts

... and 242 more

Continue to review full report at Codecov.

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

Thanks for this, @ianshade !
I was able to reproduce Case 2 and 3 locally, and verify that this PR does indeed fix them.
fyi: For Case 1, I wasn't able to reproduce the indefinitely looping segment (on our release38-branch). The Segment A is looped just once (as expected), then the next segment is Nexted.


404 Filter not works

Hi, I have several issues with Katana.
katana -u domain.com -o katana.txt -headless --no-sandbox -silent -jc -jsl -kf robotstxt,sitemapxml -cos feed,css,mailto -fdc 'status_code == 404' -proxy socks5://username:password@proxyhostname:port

I'm using this command, however, in the output file, there are many 404 links. But I used -fdc 'status_code == 404' to not show them.

When I use proxy, it's not finding any link at all. Only prints the domain.

When I use headless, my cpu is 100% all the time, and if it finds many links, I mean such as 100, then my vps will be down with 2 dedicated vcpu and 4 gb ram.

And, with the same command, katana gives me different results. For example, in one test, it shows me 10 links, In next test it gives me 50.

As you can see in the image, with same command, first it gave me 2 domains, then it gave me a lot.
katana version: 1.0.5
Thanks

Could you please try again with a longer timeout? -timeout


format and improve weighting editor

e.g. format the numbers to edit

addressed in latest 3.0 version
https://lineup.js.org/app/#soccer