Docs don't match implementation

Per the README file:

value is the value of the data in the element, represented as a number or a string. Integers stored in 6 bytes or less are represented as numbers, and longer integers are represented as hexadecimal text strings.

As well:

Elements with the Block and SimpleBlock types get special treatment. They have these additional members:

payload is the coded information in the element, stored in a Uint8Array.
track is an unsigned integer indicating the payload's track.
keyframe is a Boolean value set to true if the payload starts an I frame (SimpleBlocks only).
discardable is a Boolean value showing the value of the element's Discardable flag. (SimpleBlocks only).

And, the value member shows the block's Timecode value.

Neither of these seem to be the case when I actually utilize the library:

Looking at the source code for the EBML Decoder, there's no evidence that it's even trying to set these values. Was this a pipe dream feature that just wasn't implemented, or is it sitting on another branch somewhere?

The current example.js from master gives me this:
[ 'tag',
  { tag: 35,
    tagStr: 'a3',
    type: 'b',
    name: 'SimpleBlock',
    start: 12105,
    end: 12112,
    dataSize: 5,
    data: <Buffer 82 00 0d 80 0a>,
    track: 2,
    value: 13,
    keyframe: true,
    discardable: false,
    payload: <Buffer 0a> } ]
[ 'tag',
  { tag: 35,
    tagStr: 'a3',
    type: 'b',
    name: 'SimpleBlock',
    start: 12112,
    end: 12147,
    dataSize: 33,
    data: <Buffer 81 00 21 00 f1 02 00 05 10 a4 00 18 00 18 58 2f f4 00 08 80 04 33 5f ad 72 4c e2 f8 60 a0 8d 02 00>,
    track: 1,
    value: 33,
    keyframe: false,
    discardable: false,
    payload: <Buffer f1 02 00 05 10 a4 00 18 00 18 58 2f f4 00 08 80 04 33 5f ad 72 4c e2 f8 60 a0 8d 02 00> } ]

The readme you quoted is from master, but master isn't released on npm yet (will be as 3.0).
I guess that might explain the differences?
We (or me) really should have done a better job at making clear that the current master isn't released yet. Sorry for the trouble.

I'll take a looksee at the updated docs for the updated ebml decoder. Might be over the coming weekend.

Still having the issue right?

The npm package at https://www.npmjs.com/package/ebml is not yet updated to the May 3 commits made here. If you use the npm package, you should use its README.md for documentation.


V1beta2

https://github.com/open-cluster-management/backlog/issues/9124

/retest

/retest

/retest

/retest


fix qwen-vl failed with FSDP

this PR search attribute from the original module if the attribute is missing in the FSDP wrapper module.

Should we also change the self.model to self._module in fsdp.py, spmd_fsdp.py, pp/pipeline.py, dp.py

@yitongh good idea, I will do that in the next PR.


Fervo case study - final review before asking Fervo for feedback

Incorporated latest comments into input file.

Closed in favor of https://github.com/NREL/GEOPHIRES-X/pull/220


Interested in Bazel for JS?

Hey there, I'm a lead for Bazel and noticed your https://github.com/google/perfetto/blob/master/ui/build.js is fairly bespoke. Would you be interested in a minimal PR illustrating some part of that build process written as BUILD files?

Hey @alexeagle,
I'm the person who wrote the initial version of build.js
I can give you a quick answer to the bespoke part: the bespoke build.js is mainly due to:

Due to the (sad) way the JS ecosystem works, the only way to have fast incremental builds is to mount a pipeline of processes (tsc compiler,  rollup bundler, scss transpiler) in --watch mode and keep them alive, so each process consumes live updates form the previous one in the pipeline. Unlike what happens in C/C++/Java, trying to handle incremental builds as "re-invoke the compile from scratch" leads to 10x slower incremental builds.

What happens in that build.js that some of the compilation pipeline stages is handled by the various processes running in --watch mode. In turn they re-trigger (via fsnotify) portions of the build.js file that reacts to those changes. So You'd need a mixture of "external processes that do things in reaction to files changing " and "build rules being retriggered when their inputs change"

Livereload feature, to detect fs changes in the final dist folder and turning them into HTTP events for the livereload client

The fact that we have nodejs already bundled as a dependency, because it's needed to build anyways (And it can be downloaded as a standalone executable without any complex installation)

If we ended up in something bazel-based that handled only full compilations, without the process pipeline in --watch mode, that would be completely uninteresting for me an my team.
Our initial UI build was based on GN+ninja (which I adore) and we moved away precisely for the reasons mentioned above:
Here's my skepticism about bazel:

I am not sure it can handle case 1 (general build systems are not a good fit for keeping processes around indefinitely while at the same time re-triggering rules on change)
In any case I'd need some dedicated JS file for the http server + livereload
I suspect even if it worked we'd end up with more lines of code/rules to maintain, with the extra burden for our deves of having to understand two languages/tools, not one

But I'm happy to be proven wrong
Primiano

use tools which don't suffer that slow startup time, for example we recommend using https://swc.rs/ to transpile .ts -> .js

Sorry we are not going to move away from the official typescript compiler. That is beyond a build system discussion and generally is going to move us on our smaller tech island. Not going there.

use tools which don't suffer that slow startup time

If this was the premise, then I'd argue: why not just GN+Ninja? What does Bazel buy? Ironically, one of the things I found irritating about bazel is the startup time of each bazel invocation :D

I agree about adding another build tool being a maintenance burden but I saw you do already have Bazel BUILD files in the repo

Those files are auto-generated from our GN files (which is the source of truth). 99% of the times nobody in the team has to think about bazel, only about GN.

My interest here was in possibly building perfetto into Bazel itself to make it more convenient to view traces.

This does not follow to me. How is changing the perfetto buildsystem going to improve its convenience of trave vieweing? Can you expand?


Disable Windows Defender in Lab 2

Should probably mention to disable Windows defender in lab 2 as Windows defender detects and quarantines bad.exe

ah yep I did that way before so forgot about it, thanks!

seems to be resolved.


Use the top left corner 'white space' for displaying information

Describe the bug
Use the top left empty space to tell the name of the utility and the build date, I also added the Q to exit since currently that's the only way to exit (I don't know if that is the best place for it, could live on the right side of the top bar). When you are searching within the utility only esc will work, which would be nice if it was supported as an exit method for consistency's sake.
Expected behavior
Use the available screen real estate better
Screenshots
Quick mockup: (in compat mode since I have no icons)

https://github.com/ChrisTitusTech/linutil/issues/285 was added and the bottom dynamic list shows shortcuts


fix gcc compilation in linux

tweak to fix the compiler complaining about a reuse of the variable index

Thank you!


Introduce booster-doctor --- kore-rcp-booster abort analysis tool

@geo2a Can you please provide an update on this PR?

@yale-vinson I was sidetracked by a number of urgent issues in haskell-backend (resolved now). The tool works locally, but I need to iron-our some things and provide adequate documentation and a simple integration tests. I'm continuing to work on this PR and expect to push new changes by tomorrow.


🚀 Binary Frameworks for tree-sitter parsers

Current Situation
Currently all tree-sitter parsers are fetched from source every time Swift Package Manager resolves dependencies. This can easily take a couple of minutes even with a good internet connection. This also applies to the CodeEdit repo.
Proposal
Since Languages usually don't need to be updated very often, they could be bundled as pre-built *.xcframework binaries in an extra repository. This would also include the CodeLanguage class. By doing so the fetching occurs only from a single Swift Package which in turn hugely benefits package resolution.
Further Information
Once there are additional languages or updates to existing ones, it's as simple as running a script to re-build the frameworks.
I know this sounds like a lot of overhead but I think in the long term this will pay off since waiting for packages to fetch/resolve on a daily basis definitely adds up.
I'm curious what you guys think about this!

Closed with #86


Update requirements.txt

The recent versions of setuptools raise the Error "AttributeError: module 'setuptools._distutils' has no attribute 'version'". This version is required specifically to fix that error.
Module fire is required to create LMDB dataset

Thank you for your pull request. However, I am going to reject this for the following reasons:

The setuptools issue has already been patched. Dependency is also optional, hence not included in requirements.txt.
requirements.txt currently contains all the dependencies for running the scripts used for training, evaluation, and tuning. The scripts provided in tools/ depend on other packages (e.g. mmocr) that are not critical in training or running the model. To minimize the packages pulled during installation, these dependencies are excluded.


message view: Message header offset

Originally reported in chat here.

It looks like just the uppermost message header is being shifted 15 or so pixels to the right. Refreshing removes the offset. I'm not sure how to reproduce.

@zulipbot add "area: message view"

@zulipbot add "bug"

@jackrzhang can you tell us the window size at which you got this issue?

The screenshot is from my MacBook, which has a width of 1440px in CSS. It's possible that resizing the window is a factor in reproducing the bug.

I try playing around with this but couldn't reproduce the bug.

Looks like the same bug as #9199.

This is likely the same bug as #9199; the compose box also has the same offset.
Interestingly, the screenshot in #9199 shows a shift to the left, while the screenshot above shows a shift to the right


Urbit does not work on BashOnWindows, but it works on real Ubuntu.

A brief description

Urbit does not connect on WSL even though it works fine on Ubuntu.

Expected results

Urbit should have connected to the network after installing. Instead it has a stack overflow.

 The same thing happened both times.

Steps / All commands required to reproduce the error from a brand new installation

Follow the Urbit installation instructions to build from the source: https://urbit.org/docs/using/install/
Use Urbit version 0.4.4. https://github.com/urbit/urbit/archive/v0.4.4.tar.gz

Strace of the failing command

No commands fail. It just doesn't connect.

Required packages and commands to install

All of these are listed under https://urbit.org/docs/using/install/
For Ubuntu:  sudo apt-get install libgmp3-dev libsigsegv-dev openssl libssl-dev libncurses5-dev make exuberant-ctags automake autoconf libtool g++ ragel cmake re2c libcurl4-gnutls-dev
If you have a problem with uv.h, do: sudo apt install libuv-dev
If that doesn't work, build and install libuv from the source: https://github.com/libuv/libuv
I'm just a user, not a dev on this project.
Urbit is open source networking software currently made for macOS, BSDs, and Linux. The Urbit development team can be reached through the following links:
https://urbit.org/stream/
https://twitter.com/urbit_
https://github.com/urbit
https://www.reddit.com/r/urbit/

Hi @EricGrahamMacEachern , thanks for posting!  Urbit is already discussed on #1667 .  Could you take a look and see whether that report looks like the same failure mode as you are seeing?
If you think your failure is different -- I know you say that no command is failing, but could you include an strace of the command that is failing to connect?

Sorry for the duplicate post. I will stick to the older thread.
https://github.com/Microsoft/BashOnWindows/issues/1667

Thanks @aseering for all the help with the triage.
@EricGrahamMacEachern - No problem, and, thanks for the post and using WSL!


CFE incorrectly removes secondary IP addresses from AWS ENI's when VIP is in traffic group 1

Do you already have an issue opened with F5 support?
No
Description
In a previous version of CFE we enforced the use of traffic group None for VIP's that are intended to failover between AZ's in AWS. However now we see this unwanted behavior when using CFE:

Customer deploys our CFT in AWS for HA across AZ's.
Customer configures 2x VIPs in BIG-IP, one in each AZ. Because they are not intimate with our CFE requirements, they put these VIP's in traffic-group-1 which is default when using the GUI.
Customer configures secondary IP addresses on her ENI's in AWS to match the VIP configuration.
Customer configures an EIP with the correct tags so that this EIP is associated/re-associated with her 2x secondary IP addresses configured in Step 3. Everything is configured correctly except the VIPs are in Traffic Group 1, not None.
Customer tests failover. Because she has not created her VIP's in traffic group None, CFE does not perform failover successfully, and further it deletes the secondary IP addresses she had created for her VIPs.

Environment information
For bugs, enter the following information:

Cloud Failover Extension Version: 1.7
BIG-IP version: unknown
Cloud provider: AWS when failover is set up across AZ's with 1x EIP and 2x VIPs.

Severity Level
For bugs, enter the bug severity level. Do not set any labels.
Severity: 3

Thanks for reporting this issue. We are tracking this bug internally with ID AUTOSDK-534.

@shyawnkarim  you asked me for a qkview but the customer is using an eval key and is unable to open a support case and provide a qkview - sorry about that.

@mikeoleary thanks for checking.


Revert "use keystore"

Reverts classapp/react-native-sensitive-info#14

Reverting will prevent breaking changes for now, but we will use this contribution later.

Reverting will prevent breaking changes for now, but we will use this contribution later.


Does the API still work with Azure DevOps Server 2019

Hi,
Does the API still works with VS2019 and Azure DevOps Server 2019? I am quite confused after reading this page and this article: https://devblogs.microsoft.com/devops/announcing-the-deprecation-of-the-wit-and-test-client-om-at-jan-1-2020-2/
So, can we upgrade to 2019 first and replace the API by the REST calls afterwards?
Thank you!

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

ID: 58fa4b52-1f5c-11c5-329b-2526613833fa
Version Independent ID: 6d1fb152-1612-a0ec-06fc-4ea2e2135541
Content: Deprecation of the Work Item Tracking (WIT) and Test Client OM - Azure DevOps
Content Source: docs/integrate/concepts/wit-client-om-deprecation.md
Product: devops
Technology: devops-agile
GitHub Login: @KathrynEE
Microsoft Alias: liho

@StavroulaSsi  Thank you for the question.
The SOAP calls should still be functional, though no longer supported, and you will have issues trying to use Visual Studio against functionality marked obsolete, see this post, so I would avoid upgrading the DLLs until you are ready to migrate.
Assigning this to the author for further confirmation.

Thanks for your question. It looks like your question isn't an issue with the documentation, but an issue or question specific to your implementation or a bug in the product itself.
For help with a specific task, here are a couple of options where you might consider asking your question:

Azure DevOps on Stack Overflow
Azure DevOps Support Bot

If you've encountered an issue with the product itself, to make sure it gets in front of the right people, please submit your bug here.
If you have an idea for improving the product, please submit your idea here.


Delivery property "PartitionKey" can be only static?

Hi,

I would like to use custom delivery property "PartitionKey" to be able to properly route my events from Event Grid to Event Hub. But I'm not sure if it's correct that the Header Type should be only "Static". Shouldn't it be possible to specify dynamic value to be able to load partition key from event data (using JsonPath).

There is a typo "ParitionKey" on a page.

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

ID: 5f32336a-5f00-e6bb-36c0-868055edc8c7
Version Independent ID: 5bce8fca-ca60-935d-151c-2fc027163515
Content: Azure Event Grid - Set custom headers on delivered events - Azure Event Grid
Content Source: articles/event-grid/delivery-properties.md
Service: event-grid
GitHub Login: @spelluru
Microsoft Alias: spelluru

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

@JosefPihrt Unfortunately as of now you cannot specify the PartitionKey as the dynamic value for the Delivery Properties of your event grid subscription. As of now it only supports the Static value type.
If you try to specify the dynamic value, then you will get the error while saving it.

Error:

For your first concern - The document calls out correctly that as of now it only supports static value.
For your second issue thanks for pointing out the typo ParitionKey. I have updated the document and it will be published soon.
Let me know if you have any queries or concerns.

@JosefPihrt My bad and thanks for your response. There was bug in the portal due to which I have observed this behavior and the team will be fixing the portal issue. Yes you are correct and I will update the doc as PartitionKey support both static and dynamic values.

@JosefPihrt I have updated the doc and it will be published soon. We appreciate the feedback!


compile with jdk 1.6/1.7

otherwise plugin might not be executable on some machines...

fixed with help from @aalmiray (idea taken from griffon-build)


Blacklist subreddits

gives you the option to blacklist subreddits:
Add the subreddits you want to blacklist in /src/blacklisted_subreddits.txt , one per line.

nice, but should we write subreddits as r/(Subreddit) or just (Subreddit)?

I agree that it would be more clear for users that you do not want to put r/ in front of the subreddit names if it isn't logged with r/

i updated the learn.py so that it used with open(), and I put some instructions in the blacklisted_subreddits.txt. Ideally I (or someone else if they get to it before me) would update the readme eventually.

The stuff in the blacklist.txt will be interpreted as subreddits, that should be removed. Or it should have a character in front of them that signifies it is not an actual subreddit. That does, however, need to be implemented too. Is there any way I can propose changes to a pull request that isn't mine?

Oh and it might be better to put the loading of the blacklisted subreddits in utils.py, but maybe this is better as you wouldn't need to restart the bot every time you want to add another subreddit to that list. (sorry for the notification spam)

Does it really matter that it gets interpreted as a subreddit though? It's only two lines.

Not necessarily, but it is bad practice. Plus the worldnews does matter as that is a subreddit. But that might even be better to leave in as you get banned super quickly for posting on there with the bot.

Well the "worldnews" was used as an example, so naturally you'd delete that one if you don't want it blacklisted, but I get what you mean. Also I picked worldnews because you get banned so easily.

I went ahead and added this in 86b1236


Change docker-compose.yml env vars to $vars

Environment
Docker
How did you encounter the bug?
When trying to load this in Coolify (or a place where you can't edit the docker compose file), it breaks because of the hard-coded values. I think this should be updated so that it automatically references env vars.

i.e. VITE_CLICKHOUSE_URL=$VITE_CLICKHOUSE_URL
What did you expect?
Dynamic env vars
Actual Result
Static env vars
Browser
Chrome
Browser Version

Version

done!


Snappy repodata patch should apply to any dep

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

The diff is enourmous, thus I'm not posting it here but it is basically all over
-    "snappy >=1.1.10,<2.0a0"
+    "snappy >=1.1.10,<1.2.0a0"

There are some clang changes in the diff but these are to an unbound clangdev patch,

Uploaded as gist: https://gist.github.com/xhochy/0d5c4c28e384aa00032edf4f1fe56e07


demo_service with solo5 no response

Hi!
The demo_service doesn't seem to send any response back when I'm using solo5/ukvm.
I modified the port the service runs on and changed the config to skip dhcp and instead use <IP_ADDRESS> as a static ip from the get-go.
I had an issue before where sa_family_t had conflicting definitions, I solved that by commenting out your definition of it, could that have caused it?
From it's terminal it seems that everything is fine, but curl doesn't get the response back:
            |      ___|
  __|  _ \  |  _ \ __ \
\__ \ (   | | (   |  ) |
____/\___/ _|\___/____/
Solo5: Memory map: 512 MB addressable:
Solo5:     unused @ (0x0 - 0x200fff)
Solo5:       text @ (0x201000 - 0x403387)
Solo5:     rodata @ (0x403388 - 0x432c2f)
Solo5:       data @ (0x432c30 - 0x687d5f)
Solo5:       heap >= 0x688000 < stack < 0x20000000
                * Initializing Autoconf plugin
   [ Autoconf ] Running auto configure
    [ Netconf ] Configuring network
    [ Network ] Creating stack for Solo5Net on eth0 (MTU=1500)
      [ Inet4 ] Bringing up eth0 on CPU 0
      [ Inet4 ] Network configured (5e:d4:3e:96:0b:b4)
                IP: 		<IP_ADDRESS>
                Netmask: 	<IP_ADDRESS>
                Gateway: 	<IP_ADDRESS>
                DNS Server: 	<IP_ADDRESS>
    [ Netconf ] Configuration complete
   [ Autoconf ] Finished
================================================================================
 IncludeOS v0.12.0 (x86_64 / 64-bit)
 +--> Running [ IncludeOS minimal example ]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
*** Basic demo service started ***
<Service> TCP STATUS:
LISTENERS:
Local	Queued
<IP_ADDRESS>:8081	0

CONNECTIONS:
Proto	Recv	Send	In	Out	Local			Remote			State

<Service> @on_connect: Connection <IP_ADDRESS>:37366 successfully established.
<Service> @on_read: 78 bytes received.
<Service> Request:
GET / HTTP/1.1
Host: <IP_ADDRESS>:8081
User-Agent: curl/7.47.0
Accept: */*

<Service> Responding with 200 OK.
<Service> @on_write: 713 bytes written.

Also the connection doesn't end (since curl is waiting for a response):
CONNECTIONS:
Proto	Recv	Send	In	Out	Local			Remote			State
tcp4	 	 	 	 	<IP_ADDRESS>:8081		<IP_ADDRESS>:37366		ESTABLISHED

I wrote my own http server as well in C and that did the same, it seemed to accept the connection and even try to respond but neither curl nor wget got anything back.
QEMU works fine for both your and my function.
Does anyone have any idea what's happening?
(Also I'm using 0.12, since I had some nasty problems with even the most basic functions when using 0.13.)

I can confirm this issue also happens for me on v0.12. I'm getting ping and I do see http transmission with 200 OK from IncludeOS, but no output from curl, wget etc. Here's a tcpdump:
https://gist.github.com/alfred-bratterud/2f5fb96e8f0b7d6c598c806e29091cfa
@AndreasAakesson can you make sense of it?

The service is working (e.g. curl responds as expected) for me with v0.13. Would be nice to find the root cause though - and to know why this wasn't picked up by the solo5 test.

@Kuvesz can you live with #1990 for a little while? If so I think v0.13 would be the best solution - we'll help you get that working if you encounter issues. If you need C++ exceptions or v0.12 for other reasons I can try to have another look at that, otherwise I have #1990 in my scope for the HAL work I'm doing now.

Yes I can live with that, I'll post the errors with 0.13 in a different issue.


Dracula theme

This adds support for https://github.com/Mofiqul/dracula.nvim and https://github.com/dracula/vim that are afaik the two most popular implementations of the Dracula Theme

Annoyingly they are different in a few regards and if you are used to one switching to the other is a little hassle - so i propose to support them both.
Mofiqul

Official

Thanks for the PR, lgtm! Can you update the commit messages though to be Themes: Add XXX. Also, either in an extra commit or within each one (I don't care), can you add a release doc message. Feel free to link to your github profile. I also wrote a contributing.md for the future.

Should be tidied up now!

Thanks! Could you address that one comment about "dracula-nvim" naming and then its good to merge.

Wait err i think i missed something - which comment are you referring to? :eyes:

Hmm, should be a line comment. https://github.com/jordanisaacs/neovim-flake/pull/34#discussion_r1157867443

Ah I'm sorry. Still trying to figure out github's review UI which is very confusing. Didn't realize I had to not just add a comment but press the submit review in the corner. 🤷

I'm glad it wasn't just me who was blind :P


rpmmd: Remove old BaseURL compatability

This removes the JSON Marshal and Unmarshal for BaseURL compatability. Everything should be using the BaseURLs list by now since this was changes in January 2023 and according to the note was safe to remove after 3 releases.

This shouldn't break anything. Let's see what the tests say!


No fallback in circuit_drawer

The circuit_drawer falls back to _matplotlib_circuit_drawer when _latex_circuit_drawer fails with OSError. We should remove that fallback at some point.

Yep, I agree and that's the plan. Which is why we emit a deprecation warning right now if you run circuit_drawer without the output kwarg set. This was the deprecated previous default for circuit_drawer in 0.6.0. We will have to wait until we at least have this emit the deprecation warning in at least 1 release.
It does raise a larger question for me though which is what our deprecation policy should be on this kind of thing? I haven't seen it defined anywhere where we say that we wait X amount of time (whether in an actual unit of time, or a release count) from deprecation to removal. I think that's a separate larger discussion though, but something I think that will be good to define as a policy for the project.

I would like the output of the cirucit_drawer to be text (no dependencies by default).
We can have a visitation.set_defaults for interactive when we have it etc

Maybe visitation.set_defaults can also be used for handle the drawer options (see #1075). Opinions?

Did we decide on this @1ucian0 and @mtreinish I would like to make sure that we are moving away from fallbacks? If this is done let's close if it is getting worked on who is it assigned to.

This is basically done, we've deprecated the fallback as the default and as soon as 0.7 is out I'm going to push a patch up removing the fallback and switching to 'text' output by default for 0.8.

We can say that it's decided :)


Mic-5176/check creation time

Mic-5176/check creation time
Check whether environment is a week old and make a new on if it is

Category: Feature
JIRA issue: MIC-5176
Research reference:

Changes and notes
-check if environment is a week old and delete and remake environment if it is older than a week old
Verification and Testing

The feature LGTM. Did you / can you test this?


Why so constrained work area?

Hello,
Thank you very much for your tool. It is saving my life.
One thing that I don't understand is why have you limited the work area to just 640px. I have to hack the css to have a wider work area, which is essential to work comfortably.
Thanks and regards

@danielo515
Daniel, I'm happy to hear you find the tool useful!
I just set width to 80% of the body. Hope it is enough for comfortable work.
If you have better ideas on the topic - share your expectations or send pull request.
Regards,
Vladimir

Hello @vladminsky,
Thank you very much for such a fast fix. 80% is a perfect size for working comfortably.
Indeed I will give you my feedback on this topic and any other I find :smile:


Build error - A problem was found with the configuration of task ':app:lintAnalyzeDebug'

Hey guys, I am facing an issue when trying to build a project with ./gradlew build, on the android folder!
FAILURE:

Build failed with an exception.

What went wrong:

A problem was found with the configuration of task ':app:lintAnalyzeDebug' (type 'AndroidLintAnalysisTask').

- Gradle detected a problem with the following location: 'C:\Projetos\hph-services-app\android\app\build\intermediates\ReactNativeVectorIcons'.

Reason: Task ':app:lintAnalyzeDebug' uses this output of task ':app:copyReactNativeVectorIconFonts' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.

Possible solutions:

      1. Declare task ':app:copyReactNativeVectorIconFonts' as an input of ':app:lintAnalyzeDebug'.
      2. Declare an explicit dependency on ':app:copyReactNativeVectorIconFonts' from ':app:lintAnalyzeDebug' using Task#dependsOn.
      3. Declare an explicit dependency on ':app:copyReactNativeVectorIconFonts' from ':app:lintAnalyzeDebug' using Task#mustRunAfter.

I was trying to build on windows
------------------------------------------------------------
Gradle 8.0.1
------------------------------------------------------------

Build time:   2023-02-17 20:09:48 UTC
Revision:     68959bf76cef4d28c678f2e2085ee84e8647b77a

Kotlin:       1.8.10
Groovy:       3.0.13
Ant:          Apache Ant(TM) version 1.10.11 compiled on July 10 2021
JVM:          11.0.2 (Oracle Corporation 11.0.2+9)
OS:           Windows 10 10.0 amd64

"react-native-vector-icons": "^10.0.2",
"react-native": "0.72.6",

I saw some solutions here:
https://github.com/oblador/react-native-vector-icons/issues/1508
Solution:
Adding the following lines to node_modules/react-native-vector-icons/fonts.gradle
/**
 * Register font asset source folder
 */
android.sourceSets.main.assets.srcDirs += file("$buildDir/intermediates/ReactNativeVectorIcons")

/**
 * Task to copy icon font files
 */
afterEvaluate {
    def config = project.hasProperty("vectoricons") ? project.vectoricons : [];
    def iconFontsDir = config.iconFontsDir ?: "../../node_modules/react-native-vector-icons/Fonts";
    def iconFontNames = config.iconFontNames ?: [ "*.ttf" ];

    def fontCopyTask = tasks.create(
        name: "copyReactNativeVectorIconFonts",
        type: Copy) {
        description = "copy vector icon fonts."
        into "$buildDir/intermediates/ReactNativeVectorIcons/fonts"

        iconFontNames.each { fontName ->
            from(iconFontsDir) {
                include(fontName)
            }
        }
    }

    android.applicationVariants.all { def variant ->
        def targetName = variant.name.capitalize()

        def generateAssetsTask = tasks.findByName("generate${targetName}Assets")
        generateAssetsTask.dependsOn(fontCopyTask)

        def lintVitalAnalyzeTask = tasks.findByName("lintVitalAnalyze${targetName}")
        lintVitalAnalyzeTask?.dependsOn(fontCopyTask)

        // add this: --------------------->
        def lintAnalyzeTask = tasks.findByName("lintAnalyze${targetName}")
        lintAnalyzeTask?.dependsOn(fontCopyTask)
    }
}

Check the two lines after // add this: --------------------->
@oblador
The error is similar to https://github.com/oblador/react-native-vector-icons/issues/1508 but this time with task lintAnalyzeTask

@leonardo-coutinho-dev Thanks for this fix! I was experiencing the same error after upgrading from react native 0.71.3 to  0.73.2 and the proposed solution fixes the build for me.

I had same issues followed by another ones, I had to add 3 new dependency configurations (cheaper and faster solution is to downgrade gradle as of some version it requires explicit/implicit dependency between tasks declarations, there is a probability where other tools and tasks will give similar problems in the future):
android.applicationVariants.all { def variant ->
    def targetName = variant.name.capitalize()

    def lintVitalAnalyzeTask = tasks.findByName("lintVitalAnalyze${targetName}")
    if (lintVitalAnalyzeTask) {
        lintVitalAnalyzeTask.dependsOn(fontCopyTask)
    }

    def generateAssetsTask = tasks.findByName("generate${targetName}Assets")
    if (generateAssetsTask) {
        generateAssetsTask.dependsOn(fontCopyTask)
    }

///// New declarations
    def generateReportModelTask = tasks.findByName("generate${targetName}LintReportModel")
    if (generateReportModelTask) {
        generateReportModelTask.dependsOn(fontCopyTask)
    }

    def lintAnalyzeDebugTask = tasks.findByName("lintAnalyze${targetName}")
    if (lintAnalyzeDebugTask) {
        lintAnalyzeDebugTask.dependsOn(fontCopyTask)
    }

    def generateReleaseLintVitalReportModelTask = tasks.findByName("generate${targetName}LintVitalReportModel")
    if (generateReleaseLintVitalReportModelTask) {
        generateReleaseLintVitalReportModelTask.dependsOn(fontCopyTask)
    }
}

My project package configuration:
`
I'm using gradle version 8.5
"dependencies": {
"@react-navigation/bottom-tabs": "^6.5.11",
"@react-navigation/native": "^6.1.9",
"@react-navigation/native-stack": "^6.9.17",
"@rneui/themed": "^4.0.0-rc.8",
"metro-react-native-babel-transformer": "^0.77.0",
"node-sass": "^9.0.0",
"react": "18.2.0",
"react-native": "0.73.2",
"react-native-keychain": "^8.1.2",
"react-native-maps": "^1.10.2",
"react-native-safe-area-context": "^4.8.2",
"react-native-sass-transformer": "^2.0.0",
"react-native-screens": "^3.29.0",
"react-native-vector-icons": "^10.0.3"
},
"devDependencies": {
"@babel/core": "^7.20.0",
"@babel/preset-env": "^7.20.0",
"@babel/runtime": "^7.20.0",
"@react-native/babel-preset": "0.73.19",
"@react-native/eslint-config": "0.73.2",
"@react-native/metro-config": "0.73.3",
"@react-native/typescript-config": "0.73.1",
"@types/react": "^18.2.6",
"@types/react-test-renderer": "^18.0.0",
"babel-jest": "^29.6.3",
"eslint": "^8.19.0",
"jest": "^29.6.3",
"prettier": "2.8.8",
"react-test-renderer": "18.2.0",
"typescript": "5.0.4"
},
"engines": {
"node": ">=18"
}
}
`

The same issue here on RN 0.72.4
There is a PR that I believe will solve this here.
Can we not have it merged in, please?

It worked on RN 0.74.0
just add  at  \node_modules\react-native-vector-icons\fonts.gradle
if (lintVitalAnalyzeTask) {
        lintVitalAnalyzeTask.dependsOn(fontCopyTask)
        }

+        def generateReportTask = tasks.findByName("generate${targetName}LintVitalReportModel")
+      if (generateReportTask) {
+            generateReportTask.dependsOn(fontCopyTask)
+      }

        def generateAssetsTask = tasks.findByName("generate${targetName}Assets")
        generateAssetsTask.dependsOn(fontCopyTask)

It worked on RN 0.74.0 just add at \node_modules\react-native-vector-icons\fonts.gradle
if (lintVitalAnalyzeTask) {
        lintVitalAnalyzeTask.dependsOn(fontCopyTask)
        }

+        def generateReportTask = tasks.findByName("generate${targetName}LintVitalReportModel")
+      if (generateReportTask) {
+            generateReportTask.dependsOn(fontCopyTask)
+      }

        def generateAssetsTask = tasks.findByName("generate${targetName}Assets")
        generateAssetsTask.dependsOn(fontCopyTask)

thank you so much, its work perfectly

It worked on RN 0.74.0 just add at \node_modules\react-native-vector-icons\fonts.gradle
if (lintVitalAnalyzeTask) {
        lintVitalAnalyzeTask.dependsOn(fontCopyTask)
        }

+        def generateReportTask = tasks.findByName("generate${targetName}LintVitalReportModel")
+      if (generateReportTask) {
+            generateReportTask.dependsOn(fontCopyTask)
+      }

        def generateAssetsTask = tasks.findByName("generate${targetName}Assets")
        generateAssetsTask.dependsOn(fontCopyTask)

thanks a lot. its work perfectly

in there any solution without added some codes to \node_modules\react-native-vector-icons\fonts.gradle?

Will be fixed in upcoming release by #1648


Cant make forever log options work

Hi im trying to add forever log options in my forever options. But it seems to not be working.
This is my install line:
sudo forever-service install serialReader --script serialReader.js -f " -watchDirectory /home/pi/Code/arduino-plant-reader -w -l readerLog.log -a"
Also, is there a reason to use both watchDirectory and -w? Wouldnt -w just work alone?

Can you post your /etc/init.d/serialReader? And are you using latest version of forever-service?

Could you try to run the command without -l option since forever-service overrides that option and stores all logs in /var/log/{service}.log file, I am not sure on -w and --watchDirectory together, I think I picked up example from somewhere and I have been able to successfully use it in my project so haven't tried to further investigate that.

Ok but you are using it together?
I usually just use -w when i launch forever from the directory im in. But how does that work when you use the service? Does it launch from /etc/init.d/ folder?

forever-service will change to the same directory from which you run forever-service install cmd before invoking forever command, so if -w works from that directory it should work.

-w works, but how would .foreverignore work?
Since it runs from same folder and all it works normally?


Error with Angular 5 and 4.1.2

I just installed the latest version of this module and I'm getting the following error when I ran ng serve:

MY_PATH/node_modules/ngx-uploader/index.ts is not pa
rt of the compilation output. Please check the other error messages for details.
at AngularCompilerPlugin.getCompiledFile (/MY_PATH/node_modules/@ngtools/webp
ack/src/angular_compiler_plugin.js:629:23)
at plugin.done.then (/MY_PATH/node_modules/@ngtools/webpack/src/loader.js:467
:39)
at
at process._tickCallback (internal/process/next_tick.js:188:7)

what version of angular-cli are you running? cannot reproduce on latest one 1.5.0.

did you imported module as
import { NgUploaderModule } from 'ngx-uploader';

I'm using the latest also.
ng -v:
Angular CLI: 1.5.0
Node: 8.4.0
OS: darwin x64
Angular: 5.0.0
... animations, common, compiler, compiler-cli, core, forms
... http, platform-browser, platform-browser-dynamic, router

@angular/cli: 1.5.0
@angular-devkit/build-optimizer: 0.0.32
@angular-devkit/core: 0.0.20
@angular-devkit/schematics: 0.0.35
@ngtools/json-schema: 1.1.0
@ngtools/webpack: 1.8.0
@schematics/angular: 0.1.2
typescript: 2.4.2
webpack: 3.8.1

And I'm importing the module this way import { NgUploaderModule } from 'ngx-uploader';.

I am appending sample project. Both ng serve and ng serve --aot works as expected.
proj.zip

Try with
import { NgUploaderModule } from 'ngx-uploader/ngx-uploader';

@rafaelss95 could you please check the sample project from @jkuri?
Thank you!

This is an angular-cli issue, try adding MY_PATH/node_modules/ngx-uploader/index.ts to tsconfig.json under include:
{
    "include": [
        /* Your project files' glob, "src/**/*.ts" etc. */,
        "node_modules/ngx-uploader/index.ts"
    ]
}

Just ran into this using<EMAIL_ADDRESS>in a project w/ the following specs:
`Angular CLI: 1.6.3
Node: 9.2.0
OS: darwin x64
Angular: 5.1.2
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router, service-worker
@angular/cli: 1.6.3
@angular/flex-layout: 2.0.0-beta.12
@angular/tsc-wrapped: 4.4.6
@angular-devkit/build-optimizer: 0.0.36
@angular-devkit/core: 0.0.22
@angular-devkit/schematics: 0.0.42
@ngtools/json-schema: 1.1.0
@ngtools/webpack: 1.9.3
@schematics/angular: 0.1.11
@schematics/schematics: 0.0.11
typescript-formatter: 7.0.1
typescript: 2.6.2
webpack: 3.10.0`
Downgrading typescript to 2.5.3 and issue is no longer observed. This was not incredibly surprising as TS 2.6.x is not yet officially support for angular. I see from above that @rafaelss95 is not using unsupported TS so his issue was likely resolved by addressing as suggested by @mdhanju  or @mjurczyk - just wanted to post this in case anyone else finds their way to this page looking for answers.


"ShareCartPC"

There is a reference to "ShareCartPC" on this page.  I can find no reference to it anywhere else on the internet!  Please help me understand the reference?
Ross

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

ID: 91ca58bd-f279-7739-0140-c4bd56784768
Version Independent ID: 1d2ecc90-58a3-6bcd-84ae-ef04d7a3b7b4
Content: Policy CSP - Update - Windows Client Management
Content Source: windows/client-management/mdm/policy-csp-update.md
Product: w10
Technology: windows
GitHub Login: @Dansimp
Microsoft Alias: dansimp

It's a typo. It should be SharedPC CSP.

This description has been updated.


Callbacks don't work

Hello,
I'm trying to implement your code in my project. Checking and setting permissions works fine. However, the callbacks don't seem to work.
Here's a part of my code:
UniAndroidPermission.RequestPremission (AndroidPermission.WRITE_EXTERNAL_STORAGE, () => {
    Debug.Log("Set permission");
}, () => {
    Debug.Log("Don't set permission");
});

After I get the Android popup asking for permissions, I click Accept or Deny, but the Debug.Log() statements are never executed. Also, the OnPermit() and NotPermit() methods in UniAndroidPermission.cs are never called.
Am I doing something wrong? Can you help me out?

Ah, nevermind. I forgot to add the prefab to the scene. Everything works. Thanks!


support npm link for reinstall-packages

Oops. Don't know what fail messages mean:

The command "(mkdir /tmp/urchin && cd /tmp/urchin && curl -s "$(curl -s https://registry.npmjs.com/urchin | grep -Eo '"tarball":\s*"[^"]+"' | tail -n 1 | awk -F" '{ print $4 }')" -O && tar -x -f urchin*)" failed and exited with 56 during .

Does test/slow/nvm reinstall-packages/test-npmlink/index.js need +x file permissions? (the web UI doesn't tell me if it has it or not)
As for that specific failure, it might have been a fluke - I restarted it, and hopefully it will pass this time, or at least have a more helpful error message.

All passed!
So it means I already added +x :)

The job log is still showing the same failure even tho it's marked as a pass - I'm investigating.

@hax this is awesome. Thanks for doing this!
I believe the only remaining holes for reinstall-packages-from are:

packages originally installed from git
packages that weren't installed at all
possibly packages that are installed from private registries.


fix: typos

Description
fix typos in docs

@GoodDaisy can you run make generate and push the changes? This would fix generated files error, thanks

@GoodDaisy can you run make generate and push the changes? This would fix generated files error, thanks

I ran make generate and found that docs/cli/zetacored files were auto-generated, so I had to reverted them.


Triggers for farmer and policy makers actions

Hello everyone,
Our group has 3 questions about the event that should urge people to interact with the system.
Firstly, we know that policy makers should be able to identify well and poorly performing farmers. Should it be whenever they want ? (so even when farmers haven't finished their harvest) Or should it be once a year, semester,... ?
Likewise, should farmers be able to release production data whenever they want or on regular times (every month, semester,...) ?
Finally, for help request, is it the farmer that autonomously asks for it ? Or the system that identified that he was badly performing ? (independantly of the policy maker identification of poorly performing farmers)

The positive and negative deviance I think should be based on long-term trends and hence once a year would be good. But this is also based on the frequency and granularity of the data that you use. For example, some datasets might be updating every day (like weather) whereas others like soil parameters may be changing not as often. So the analysis should consider this.
Regarding farmer sharing their data, it is important that they share production and other data of interest as often as regularly as possible. Ideally throughout the cropping season.
First policy maker can identify poorly performing farms and then understand why they are performing not as well as their peers, then provide targeted advisory.


session timeout

How do I increase the session time for user logged in , so that user donot need to login for certain period of time

No such thing as session timeout?  Then why after a period of inactivity in the main mail browsing screen does it suddenly kick me to the login window and make me enter my password again?  @govindak  I don't see why you gave up so easily!

Did you see this option?

@ervee Yup, that's exactly what I was looking for, but oddly Google sent me to this page and made me think it didn't exist. :-)  Thanks!

You're welcome :+1:


Tutorial navigation going through footer: again!

The tutorial navigation is going through the footer again. Turns out the margins were just a temporary solution.

It's now a billion times worse:

ok, ill fix it

Good. Made a new pure CSS list group for the tutorials. It seems to be fixed.


v8 new Permissions(FileSet::getGlobal()); error

Using v8 with a custom block I get this error:
{"error":{"message":"Call to undefined method Concrete\Core\File\Set\Set::getPermissionObjectIdentifier
()"},"errors":["Call to undefined method Concrete\Core\File\Set\Set::getPermissionObjectIdentifier
()"]}
when using this code:
$fp = new Permissions(FileSet::getGlobal()); $tp = new Permissions();
        'concrete5': {
            filemanager: <?php   echo $fp->canAccessFileManager()?>,
            sitemap: <?php   echo $tp->canAccessSitemap()?>,
            lightbox: false
        },`

legacy code does not give the same error:
use Concrete\Core\Legacy\FilePermissions; use Concrete\Core\Legacy\TaskPermission; $fp = FilePermissions::getGlobal(); $tp = new TaskPermission();
        'concrete5': {
            filemanager: <?php   echo $fp->canAccessFileManager()?>,
            sitemap: <?php   echo $tp->canAccessSitemap()?>,
            lightbox: false
        },`

In v 5.7, the new method $fp = new Permissions(FileSet::getGlobal()); $tp = new Permissions(); does not throw an error.
I can see that some of the 5.8 core blocks (e.g. FAQ) use the legacy method for permissions, and the legacy method works for our block in 5.8; however, when our last theme was reviewed by the PRB, we were told not to use deprecated code and reference was given to this document:
http://documentation.concrete5.org/developers/appendix/deprecated-code-reference-ongoing
So, apologies for my ignorance, but I don't know if this is a bug, or that things have changed in v 5.8, and I should check the permissions differently.

This has been fixed.


Settings Setter causes a softlock in the middle of a song selection menu fade animation on 1.29.1

Describe the bug
In 1.29.1, the game will softlock after finishing 2 maps that ask to change settings. The Settings Setter menu is barely visible, and the song selection menu is slightly more transparent than normal.
1.29.1 simulates the full back button animation after pressing either Accept or Decline. In 1.28, the song selection menu instantly snaps back.
To Reproduce
Steps to reproduce the behavior:

Play any 2 maps that ask to change settings
Accept or decline the changes each time
Softlock

Expected behavior
Not a softlock
Additional context
2<IP_ADDRESS>.22.25.log

This is caused by an incompatibility with GottaGoFast, this is fixed in https://github.com/Aeroluna/Heck/commit/2c0dc3db83b32d0604b0c08e8679a1ae0c48f74d and will be included with the next upload

Any update on this? There's been no updates to the mod on BeatMods for 1.29.1, but 1.31 is receiving updates.

The fix is implemented in the 1.31 release, uploads for older game versions do not get approved on beatmods so it is not possible for me to backport the fix.


Looking for an optional feature to support more than one role

This works great but does not satisfy the condition when a user has more than one role. I have been trying to figure out a way to adapt this by prompting the user to select a role but I am having issues due to the asynchronous nature of the script.
For example, my roles array actually has these roles:
0 '144343243434:role/SSO_ReadOnlyUser'
1 '842741343440:role/SSO_SB1_GlobalAdmin'
2 '263434343266:role/SSO-DT1-ReadOnly'
I would like to request such a feature be added or if you could point me in the right direction on where the script needs to be modified. Thanks!

Multiple profiles are supported in the usual AWS CLI way with the --profile flag. From the docs:
$ aws configure --profile foo
$ aws-azure-login --configure --profile foo

Hey DT - Thanks for the prompt response!
Azure AD supports custom role assignment for AWS, so now a SAML token can have multiple roles listed in the attribute statement.  Here is an example of what the role claim looks like when custom roles are used and multiple roles are assigned to a user:
           <Attribute Name="https://aws.amazon.com/SAML/Attributes/Role">
<AttributeValue>arn:aws:iam::295478307378:role/SSO_ReadOnlyUser,arn:aws:iam::295478307378:saml-provider/WAAD</AttributeValue>
<AttributeValue>arn:aws:iam::143074478378:role/SSO_CwReadOnly,arn:aws:iam::143074478378:saml-provider/WAAD</AttributeValue>

In the login.js script, you extract the role claim value with the following line:
const roleAndPrincipal = saml("Attribute[Name='https://aws.amazon.com/SAML/Attributes/Role']").text();
However, when multiple roles are defined, the string being returned is 'arn:aws:iam::295478307378:role/SSO_ReadOnlyUser,arn:aws:iam::295478307378:saml-provider/WAADarn:aws:iam::143074478378:role/SSO_CwReadOnly,arn:aws:iam::143074478378:saml-provider/WAAD', so when the string is split, it ends up as:
            roleArn = arn:aws:iam::295478307378:role/SSO_ReadOnlyUser

principalArn =  arn:aws:iam::295478307378:saml-provider/WAADarn:aws:iam::143074478378:role/SSO_CwReadOnly
This results in only the first role ARN being available to the user, and the principal ARN being incorrect.  Playing around with the code, we can pull the individual roles out into an array by replacing the above code with something along the lines of:  (pardon the grammar, I'm not familiar with jscript)
            var roles = [];
            saml("Attribute[Name='https://aws.amazon.com/SAML/Attributes/Role']").children().each(function(i, xmlItem){
                            roles.push(xmlItem.childNodes[0].data);
            });

Our problem is that we have no idea how to stop the script execution, prompt the user, and wait for the user to select a role, before continuing on. Any help would be greatly appreciated.  We are very thankful for your work on this, we were almost dead in the water before finding your work.  Here is our work in progress:
            var roles = [];
            console.log("Select a Role:");
            saml("Attribute[Name='https://aws.amazon.com/SAML/Attributes/Role']").children().each(function(i, xmlItem){
                            roles.push(xmlItem.childNodes[0].data);
                            console.log(i, xmlItem.childNodes[0].data.split(",")[0].split("::")[1]);
            });

            var roleSelection
            if(roles.length > 1){
                            inquirer.prompt([{
                                            name: "roleSelection",
                                            message: "Selection:"
                            }])
            }else{
                            roleSelection = 0
            }

            const roleAndPrincipal = roles[roleSelection];

Got it. It's an easy fix. I just published v0.2.0 with support for multiple role attributes. Give it a whirl and let me know if it works for you.

This will work! only thing is the arrow keys are not working to change roles. Is there another mechanism I can try?

That's odd. You tried the up and down arrow keys? It's just using the standard inquirer list prompt. There is a raw list prompt type that uses numeric input for the choice...

I figured it out. It seems to be an issue with Gitbash on windows. When I use the standard windows command prompt, it works just fine!

Awesome. Glad it works!


Style Transfer Jitter

I'm experimenting with the pre-trained style-transfer model with little success.
Why can I only get good results from the animations you provided for your demo (and the files in the xia_mocap folder)?  Clips edited from the mocap_bfa folder, and other animations we retargeted to the CMU skeleton don't work.  They produce extremely jittery content, as if the style translated into noise.
The attached video shows typical results.  This is what happens when I apply a short walking section of one of the mocab_bfa files as style (left) and content (right) to 7 of the animations in the test_data folder.
Is there any special animation preprocessing required, or assumptions about world location/movement direction?  Are there inconsistencies in the BVH content between sources that we need to be aware of?
Thank you.
https://user-images.githubusercontent.com/91757660/136633913-a84d043f-b04c-4cd3-97aa-2ea02bab56af.mp4

We haven't trained it on our own data yet because we have trouble getting our animations into the BVH format.  We are looking instead to bypass this step.  In the meantime I've experimented with training the model on subsets of the xia dataset to see what happens.  This seems to work ok even on content animations the model was not trained on.  So I'm still unsure why the results are jittery when they are.  Perhaps there are incompatibilities with the animation representation.  Even the BFA animation data they used seems to have an issue in this respect.
When I say "It is still useful to style transfer using content and style animations the system is trained with to fill in combinations that were never captured." I'm referring to experiments I performed on the xia dataset they trained the pre-trained network provided with the code.  In the video below I transferred each of the demo animations onto each of the others to create a style transfer matrix.  The results are pretty good for locomotion.
https://user-images.githubusercontent.com/91757660/139739993-ce91dbe5-1373-4445-8f8e-136f51c8cc3a.mp4


[Doc-Command Summary-view] Command summary shows wrong command format

[Doc-Command Summary-view] Command summary shows wrong command format
severity: Low
Suggestion: view -x <recipe number from list>
Originally posted by @pyk595 in https://github.com/AY2122S2-CS2103T-T17-2/tp/issues/240#issuecomment-1092930918

Fixed in #256


Update Meta “authors”

Automatically generated by Netlify CMS

👷 Deploy Preview for e-commerce-nest processing.

Name
Link

🔨 Latest commit
5a9a13dd65312dadae5760ea0620406b8ae53a36

🔍 Latest deploy log
https://app.netlify.com/sites/e-commerce-nest/deploys/63c24825bc547a00086026d8


Update dependencies

Coverage remained the same at 100.0% when pulling 2f19013b73e0378f7f0700ded283c92e9d2b5305 on chore-update-deps into 93009c6737b23f06eda7203874493a8c935d4e91 on master.

Coverage remained the same at 100.0% when pulling 2f19013b73e0378f7f0700ded283c92e9d2b5305 on chore-update-deps into 93009c6737b23f06eda7203874493a8c935d4e91 on master.

Coverage remained the same at 100.0% when pulling 2f19013b73e0378f7f0700ded283c92e9d2b5305 on chore-update-deps into 93009c6737b23f06eda7203874493a8c935d4e91 on master.


Update the BRCA Exchange paragraph

Updating the paragraph on BRCA Exchange's implementation of VRS

Sorry for the delay @melissacline !


Missing VisitorGroups functionality

When I run sample project and login to EpiServer as<EMAIL_ADDRESS>I don't see any sign of Visitor groups (even though EPiServer.VisitorGroupsCriteriaPack is installed, so I assume "regular" visitor groups should work as well).
I don't see:

"Visitor groups" item in the top navigation menu
"personalize" option when trying to edit item in the content area
"personalized content" as a option in TinyMCE editor

Is there any reason for that ?

@tomaszmadeyski try setting the OptimizeForDelivery option to false when configuring the ContentDeliveryAPI
services                 .ConfigureForExternalTemplates()                 .Configure<ExternalApplicationOptions>(o => o.OptimizeForDelivery = false);

Great, that does the trick, thank you!
Are you aware of any reason why this is not enabled by default? In other words: are Visitor Groups fully supported in ContentDeveliveryAPI ?


[SUPPORT] Insert/Upsert in 0.10.1 is slow compared to 0.8.0

Hello,
Trying to upgrade hdfs based table to hudi 0.10.1 from 0.8.0. We cannot upgrade to 0.11.1 yet. Noticed a big performance hit with Insert/Upsert.
Insert in 0.8.0 - 5.7 min
Insert in 0.10.1 - 12 min
Upsert in 0.8.0 - 27min
Upsert in 0.10.1 - 66min
The writer config we use is here - https://github.com/apache/hudi/issues/5741
Is this is a known issue? Is there any additional setting we need to use in 0.10.1?
Here is the screenshots for Upsert:

Thanks,
Bindu

cc @nsivabalan , i have some impression that we have fixed the performance regression, do you remember which patch ?

Insert in 0.8.0 - 5.7 min
Insert in 0.10.1 - 12 min
Insert in 0.11.1 - 5.7 min
Upsert in 0.8.0 - 27min
Upsert in 0.10.1 - 66min
Upsert is 0.11.1 - 42.5min
Using
.option("hoodie.metadata.index.bloom.filter.enable", "true")
.option("hoodie.metadata.index.column.stats.enable", "true")
.option("hoodie.index.type", "BLOOM")

@bkosuru for 0.11.1, could you turn off column stats and bloom filter in metadata table and see if that helps bring the write latency on par?

@yihua I will test when I get a chance. But since insert is performing well in 0.11.1 we will upgrade to 0.11.1
upsert usecase is rare for us.
You can change the priority to minor. Thanks

cc @nsivabalan , i have some impression that we have fixed the performance regression, do you remember which patch ?

seems to be related to #4012, which is fixed in 0.11.0

yes, we have made quite few fixes around perf in 0.12. Can you wait for couple of days and give 0.12 a try. Highly recommend if you are looking for better performance.

@bkosuru : we have made lot of fixes around perf in 0.12 on both read and write side.
can you try 0.12 and let us know what you see. please disable bloom filter and column stats.
Try w/ and w/ enabling metadata as well. curious to know how this fares.

@bkosuru : we have made lot of fixes around perf in 0.12 on both read and write side. can you try 0.12 and let us know what you see. please disable bloom filter and column stats. Try w/ and w/ enabling metadata as well. curious to know how this fares.

@bkosuru would you mind re-do the benchmark using 0.12.1 ? would like to verify if perf gaps are resolved.

This will take me a while to setup and test. I will do it when time permits. Thanks!

@bkosuru Did updating to latest version improved the performance? Do you still need help on this?


drivers: gpio_nrfx: Correct the way the callbacks are fired

Add additional masking of the pins with fired callback triggers
against the currently enabled callbacks, in order to not call
handlers for callbacks that got disabled in some other callback
handlers that were called in the same ISR execution.
Fixes #15119.

Rebased on master in order to restart CI, as it failed in a strange way which does not seem to be related to the changes introduced by this PR.

@pdunaj , @pizi-nordic please review

@Mierunski could you tell if this patch needs to be back-ported to 1.14? At least, the bug is reported before the 1.14 release, AFAICS...

It should be back-ported in my opinion


keep-at-least parameter accounts only versions marked for deletion, not all versions

In my opinion, this is not that behavior what user expects to see.

We are creating tasks: https://github.com/snok/container-retention-policy/blob/main/main.py#L431C19-L443
Remove versions from list marked for deletion: https://github.com/snok/container-retention-policy/blob/main/main.py#L446-L449

You're saying we're keeping too many images, when some tags are filtered out?

When i'm reading the name of param "keep-at-least", i expect that all of images will be accounted in this number, not only marked for deletion. So yes, correct, too many images. May be it is better to rename this param or make effect of this parameter more predictable.

Would you like to contribute a fix? Sounds like we could change the counting a little, and maybe have two iterations over the set of images, and it should be possible to make this work as you assumed.

https://github.com/snok/container-retention-policy/pull/68
Here is it

The change in #68 has created a regression, it caused us to delete 25 images that would otherwise not be deleted. Here's the CI action run the day after the release of v2.1.3.
Our configuration is:
image-names: conduit
cut-off: 1 week ago UTC
 account-type: org
 org-name: ConduitIO
 keep-at-least: 5
 token: ${{ secrets.NIGHTLY_BUILD_GH_TOKEN }}
 filter-tags: '*-nightly*'

Given filter-tags I would expect only nightly tags to be touched, but that was not the case.

Both a fix and a failsafe would be welcome. I'm unavailable for the next few days, but if anyone is able to put together either, I'll make sure they're reviewed and merged asap :+1:

Hi everyone,
I'm closing in on a fix for most of the open issues, and after reviewing all of our settings I'm not really seeing the benefit of a keep-at-least argument for this action (after a rewrite). Could you help me understand what the benefit of this setting is to you? 🙏
A bit of necessary context:

A container registry can only assign a tag to one package version. Once you upload a new latest, the old loses ownership of that tag.
The keep-at-least setting does not protect against untagged package versions being deleted.

Reasons keep-at-least no longer seems useful

If you want package versions attached to docker tags to not be deleted, there is an argument called untagged-only (will be renamed to tag-selection) which will allow you to keep all package versions with tags (if you never, e.g., want latest to be deleted).
In the rewrite we will have better support for filtering on which package names and/or image tags to keep and which to delete.

After the rewrite, you will be able to specify something like:
    --account snok \
    --tag-selection both \  # untagged + tagged
    --image-names "container-retention-policy* !foo"  \
    --image-tags "!latest !test-1*" \
    --cut-off 1w \

Where specifically the latest tag and any test-1-* (where * is a wildcard) tag is protected.
So keep-at-least seems like an imprecise (and redundant) way of going about keeping your tagged images. Do you agree with this, or do you have a use-case that would not be satisfied by this new API. All feedback is appreciated 🙇

@lovromazgon, your problem will be addressed in the new release 👍 Sorry about that.

I'll describe our use case in Conduit. We cut nightly releases every night, that include creating a docker image among other assets. Nightlies are only relevant for a short period of time, if we want to try out or showcase a feature we're working on, maybe testing regressions, performance improvements etc. We don't want to keep them around for too long, so we use this action to clean up older nightlies.
Now, in our case we have a regular nightly release schedule, so we know exactly how many releases happened in a timespan. Specifying cut-off or keep-at-least is essentially the same in our case. That said, I imagine there are projects that don't trigger releases based on a schedule but rather cut a release based on other irregular events (e.g. pushes to main). In that case, you might not know how many releases happened in a certain timespan, but you might want to keep at least the last X releases, even if they are order. To illustrate a more specific example, when people go on vacation and no releases are cut, you might still want to keep the last X releases. Would this still be possible?
Once again, to be clear, I personally don't care about this functionality, as cut-off already scratches our itch, I'm just speculating that keep-at-least might still have a place.

This issue has been fixed in the v3 release 👍 Sorry for the delay!
The migration guide for v3 is included in the release post 👍 If you run into any issues, please share them in the issue opened for tracking the v3 release ☺


JBPM-4903 - ContextualSearch register search per perspective

+1 (as already on 6.4x)

master: b2f8bd62109ca574aa6560847afdad7955620329


PowerToys shortcut guide

Description of the new feature / enhancement
It would be very useful to have a single page listing all of the configured keyboard shortcuts for PowerToys - ideally added to the existing Shortcut Guide (which currently shows the most common Windows shortcuts, not the PowerToys extensions)
Scenario when this would be used?
I can remember that there is a PowerToy to do something, but not what the command is to get there, so I then have to go into the main window to find the toy and reveal the shortcut to access it.
Supporting information
No response

Thanks for your message. This is a Duplicate of an other issue. Additional comments may be added there. /dup #15405
Besides: would adding the shortcuts to the existing fly-out be sufficient?


add readme file for simon game

add something about simon game

hey @Ornate2345 Please assign this issue to me

Readme.md file is updated


Handle device host path on windows

Fixes: #4878
This was an amusingly-simple implementation, although I haven't thrown unit tests at it yet.
The integration test I did write isn't passing yet. >_<
I'm confident that the code that's there is working, because if I throw klass in instead of class, hcsshim reports the failure from the correct function, so it's getting through Containerd correctly and should have been passed on to HCS as well.
2022-03-03T19:00:09.9178287Z time="2022-03-03T18:59:13.839728300Z" level=error msg="StartContainer for \"f5f82caebc1a3a6984542cb1410dedadb275c5b72d4e312bc42cb9973f37e221\" failed" error="failed to create containerd task: failed to create shim task: specified device 5B45201D-F2F2-4F3B-85BB-30FF1F953599 has unsupported type klass: unknown"

So it's possible that either there's some other parameter which causes Windows to ignore the device spec, or my test is looking for the wrong thing. I'm thinking it's the latter, either the folder didn't mount for some reason, or I've just bungled the syntax itself.
My approach for the latter case will be to build a container with https://github.com/TBBle/dxdump in it, and hopefully I can see the difference between 'enabled' and 'not enabled' on the GitHub Actions hosts. (I can see it locally using docker run, but I don't know what the VMs will report... I'll find that out once I add CI to the dxdump repo)
Also, while this is draft, please ignore the big stack of changes to enable CRI Integration tests on GitHub Actions as suggested at https://github.com/containerd/containerd/issues/4878#issuecomment-814132549; I plan to break those out into a separate PR once I work out why the symlink tests are failing here, but not on the Windows Periodic builds.

Draft until:

[ ] Integration tests pass
[ ] Some unit tests written for the new functionality
[ ] CRI Integration test enablement for GitHub Actions moved into its own PR

For the record, the OCI Spec given to hcsshim looks correct:
2022-03-03T18:24:04.0338421Z time="2022-03-03T18:22:56.425307300Z" level=debug msg="Container \"4796028334528159a1b7364624eea56ae5df1046f85551187b0173b6ae387c6c\" spec: (*specs.Spec)(0xc000ea2300){Version:(string)1.0.2-dev Process:(*specs.Process)(0xc0011ea000){Terminal:(bool)false ConsoleSize:(*specs.Box)<nil> User:(specs.User){UID:(uint32)0 GID:(uint32)0 Umask:(*uint32)<nil> AdditionalGids:([]uint32)<nil> Username:(string)ContainerAdministrator} Args:([]string)[sh -c ls -ld /c/Windows/System32/HostDriverStore | grep FileRepository] CommandLine:(string) Env:([]string)[PATH=C:\\dig\\;C:\\bin;C:\\curl;C:\\Windows\\System32;C:\\Windows;C:\\Program Files\\PowerShell; ProgramFiles=C:\\Program Files LOCALAPPDATA=C:\\Users\\ContainerAdministrator\\AppData\\Local PSModuleAnalysisCachePath=C:\\Users\\ContainerAdministrator\\AppData\\Local\\Microsoft\\Windows\\PowerShell\\docker\\ModuleAnalysisCache PSCORE=C:\\Program Files\\PowerShell\\pwsh.exe] Cwd:(string)C:\\ Capabilities:(*specs.LinuxCapabilities)<nil> Rlimits:([]specs.POSIXRlimit)<nil> NoNewPrivileges:(bool)false ApparmorProfile:(string) OOMScoreAdj:(*int)<nil> SelinuxLabel:(string)} Root:(*specs.Root)<nil> Hostname:(string) Mounts:([]specs.Mount)<nil> Hooks:(*specs.Hooks)<nil> Annotations:(map[string]string)map[io.kubernetes.cri.container-type:container io.kubernetes.cri.sandbox-id:9623bd2ec3c65ed65b1aa77fa898ddb7e5275388c7ecf3773a687e6dc571bfdc io.kubernetes.cri.sandbox-namespace:windows-device-79b99ed9d20d573ad53171c8fef7f1f4e4613bb365b2ebb44f0ffb6907136385 io.kubernetes.cri.sandbox-name:sandbox io.kubernetes.cri.container-name:test-container io.kubernetes.cri.image-name:k8s.gcr.io/e2e-test-images/busybox:1.29-2 microsoft.com/hostprocess-container:false] Linux:(*specs.Linux)<nil> Solaris:(*specs.Solaris)<nil> Windows:(*specs.Windows)(0xc000698c00){LayerFolders:([]string)<nil> Devices:([]specs.WindowsDevice)[{ID:(string)5B45201D-F2F2-4F3B-85BB-30FF1F953599 IDType:(string)class}] Resources:(*specs.WindowsResources)<nil> CredentialSpec:(interface {})<nil> Servicing:(bool)false IgnoreFlushesDuringBoot:(bool)false HyperV:(*specs.WindowsHyperV)<nil> Network:(*specs.WindowsNetwork)(0xc000698c60){EndpointList:([]string)<nil> AllowUnqualifiedDNSQuery:(bool)false DNSSearchList:([]string)<nil> NetworkSharedContainerName:(string) NetworkNamespace:(string)cfbcad01-3189-450e-aac5-b09cc1f55796}} VM:(*specs.VM)<nil>}"

It has the correct Device entry, and doesn't enable Hyper-V, so I'm leaning heavily towards "Bungled the test". I might try and get containerd/CRI running on my local machine so I can explore the resulting container, and confirm if it actually did have the device mapped to it correctly.

Okay. CRI Integration test passed in https://github.com/containerd/containerd/actions/runs/1934414068. Even the symlink tests which have been failing before now... 😳

fyi @katiewasnothere @kevpar

Another stray thought: Since there isn't actually a spec for interpreting CRI Devices on Windows, perhaps we should limit it to only ://-separated because that's easier to distinguish. And maybe for Linux Sandbox device-mounts, introuce a new type rather than pinging off a POSIX path, although then containerd needs to understand more about the host_path than I'd hoped.
However, that would mean that Kubernetes users would have to use a different path for CRI-based runtimes compared to dockershim. I assume if there's a Docker-based CRI implementation, they've solved this in some way too (probably just passthrough host_path into /-splitting code in Docker), but I should poke around and find out.
I'm not aware of any other CRI implementations that would run on Windows, but would definitely welcome advice that such exists, particularly if they manage this already.

Based on my understanding of the discussions in https://github.com/containerd/containerd/pull/6618#discussion_r819881074 and https://github.com/containerd/containerd/pull/6618#discussion_r819875633, I've updated the implementation:

oci.WithWindowsDevice(IDType, ID) is called by splitting CRI's Device.HostPath by ://

class/X is special-cased to be class://X before the split, for dockershim/dockerd-cri compatibility.

oci.WithLCOWUVMDevice(path) is implemented but not currently called from CRI.

oci already supports LCOW in other ways, so this is just a feature-parity change for callers that wish to use this to trigger the existing in-UVM guest shim behaviour.

If we do end up needing to expose this via CRI (even if just for back-compat), then the low-level work is done.

The CRI-level tests allow for possible LinuxDevices, but currently every test case expects and ensures that none are created.

I don't think oci.WithDevices(devicePath, containerPath, permissions) is implementable with the same semantics as that API exposes on non-Windows, but I'm leaving the name unclaimed in case someone does determine a suitable semantic.
If this approach is merged, I'll probably put up a PR for docker to support --device X://Y syntax without filtering on IDType, which would also enable command-line --device to be used with this syntax for future IDTypes. (I was thinking this might be especially useful for docker build but it turns out that docker build doesn't take --device at all currently).

Just a heads up, I've been thinking about this but haven't had a chance to formalize my thoughts into words yet. Hoping to get back to this soon.

Regarding function naming, my view is that package oci (and other containerd packages) should ideally not lock support for creating containers for platform X behind build flags for platform X. For instance it should be possible to create a Linux container spec when compiling with GOOS=windows. This will make eventual support for LCOW (or even Windows containers on Linux) far easier.

I agree and have suffered from exactly that division myself; but looking at the current oci package, I felt that boat had well-and-truely sailed. Fixing this will be a bunch of work, because the oci package is the one that seems to have all the code that implements WithX by looking at the local host system environment, e.g. oci.WithDevices.
I wasn't aware of the sandbox API, and it does make LCOW a more-interesting topic, particularly because my initial reaction to the concept is that in this context, you'd end up with a UVM per sandbox, making the UVM structure a much higher-level construct and hence the current OCI abstraction for LCOW goes out-the-window, if we start treating the "LC" as normal containers, and the "OW" becomes the sandbox, rather than "LC" being Spec.Linux and OW being Spec.Windows.
And writing this up, I realised that oci.WithWindowsDevice does not need to be in the _windows.go, as it's not doing anything platform-specific. I'll have to check that we have other things that manipulate Spec.Windows in the non-platform-specific code, but then I can avoid introducing at least one platform-divergence.

I'm good with this but will defer to the Windows folks for expertise. Thanks for the work!

Reading up on CDI (https://github.com/container-orchestrated-devices/container-device-interface), I'm doubly-glad I've gone with :// as a separator and didn't support class/ on the ctr command-line, as I suspect we'll at some future point want to distinguish CDI identifiers (DNSlabel/non-slash-string) on the ctr command-line.
We should never see CDI identifiers in APIs like CRI's Device.HostPath, as they are currently (as seem in #6654) coming in from CRI as annotations, and will eventually have their own slot in the CRI spec.

Not sure why CI failed. staticcheck is correct that on Windows, those functions always return an error... but I didn't change that, and this seems like idiomatic Go for that use-case. I guess it's not clear why it's only complaining now.

Not sure why CI failed. staticcheck is correct that on Windows, those functions always return an error... but I didn't change that, and this seems like idiomatic Go for that use-case. I guess it's not clear why it's only complaining now.

We've observed this on some other PRs as well. I have no idea how something like staticcheck can be inconsistent on the same piece of code.

My best guess is that there's a cached pass for that code in the cache, and for some reason it's getting a cache-miss and hence reanalysing it. That would suggest that running it on the code without any cache would always fail, and it needs some markup to except it.

My best guess is that there's a cached pass for that code in the cache, and for some reason it's getting a cache-miss here and hence reanalysing it. That would suggest that running it on the code without any cache would always fail, and it needs some markup to except it.

I was wondering if it could be cache related as well. I'll poke around a little and see what I can find out.

@TBBle @kevpar Can you take a look #6666? Once we have this change in main, we can rebase this PR to see whether we still have the lint issue or not.

Well, it passed the linter after rebasing on #6666 so either the issue was fixed in a new release, the flakiness has flaked in my favour this time, or it only fails if the commit hash has an odd number of 7's in it or something equally obscure.

This is a know issue.

Summarizing 1 Failure:

[Fail] [k8s.io] Streaming runtime should support streaming interfaces [It] runtime should support exec with tty=true and stdin=true [Conformance]
github.com/kubernetes-sigs/cri-tools/pkg/validate/streaming.go:203

Ran 32 of 39 Specs in 255.375 seconds
FAIL! -- 31 Passed | 1 Failed | 0 Pending | 7 Skipped

--- FAIL: TestCRISuite (255.40s)

I say ship it!


Empty state

Last night I was downtown and saw the Trolley pass by and thought I would check app functionality. When I opened it I saw the “No trolleys running” banner and was confused because I had just seen it. About 5s later it showed the trolley marker and the banner went away. This was confusing to a user.
I suggest we add some sort of “Searching for active Trolleys” loader state while we establish initial contact with the api. This would be clearer to the user. If I were impatient I may have closed the app before it connected thinking none were running.

Started a PR for this: https://github.com/codeforgreenville/trolley-tracker-ios-client/pull/32


travis-ci on a fork fails

The command "(cd tools && ./download.sh)" failed and exited with 127 during
Is there a write up on how to wire travis-ci to a fork?

Looks like it failed to download the .deb package. Could be for various reasons (i.e. non-authenticated calls to github API is limited). Can you re-trigger the build and see does it happen consistently or not?

Yes, the 3rd re-trigger worked.


Debian importer is  treating lots of non-cves like cves

>>> z = pickle.load(open('debi.pickle','rb'))
>>> for i in z :
...     if not i['cve_id'].startswith('CVE') :
...             print(i['cve_id'])
...
TEMP-0105562-0FE13B
TEMP-0582798-329FE7
TEMP-0000000-DEED53
TEMP-0000000-75B37A
TEMP-0000000-106DD8
TEMP-0774898-681A65
TEMP-0532740-DB1B64
TEMP-0000000-481246
TEMP-0579087-7F12A8
TEMP-0841257-B7CD60
........................

These are further dumped directly https://github.com/nexB/vulnerablecode/blob/c5c69a46f2476056158cfb87bdc304baabba5eba/vulnerabilities/data_dump.py#L38 . So basically we are having non-cve ids  in cve fields.
The debi.pickle was obtained by pickling https://github.com/nexB/vulnerablecode/blob/c5c69a46f2476056158cfb87bdc304baabba5eba/vulnerabilities/scraper/debian.py#L76

The bug is in extract_vulnerabilities() assuming that the object key in the JSON response always contains a CVE ID. Apparently Debian publishes advisories with temporary IDs when no CVE ID is available yet. The obvious next question then is how do those temporary IDs turn in to CVE IDs and how would we detect that and update our database accordingly?

https://deb.freexian.com/extended-lts/tracker/data/fake-names apparently these are automatically generated.

These names are not stable and can change when the database is updated, so they should not be used in external references.

Should we just ignore these vulnerabilities for now ?

Either we ignore them or we don't store the temp ID and hope the summary won't change so we can find the entry again when it needs to be updated with a CVE ID.

I think ignoring would be better instead of later finding them and adding CVE ID, because if in case it doesn't get CVE ID we will end up with garbage data.

Closed in favour of https://github.com/nexB/vulnerablecode/issues/300


running ant build throws error

I have a simple ant project i am trying to build with new docker jenkins installation and i see the same problem with non-dockerized local jenkins installation. On running the build i get following error in the end.
First time build. Skipping changelog.
[local-atg-build] $ ant -file build.xml
ERROR: command execution failed.Maybe you need to configure the job to choose one of your Ant installations?
Finished: FAILURE
I am guessing the ant plugin installed is not in path.
Issues and Contributing
Please note that only issues related to this Docker image will be addressed here.

If you have Docker related issues, please ask in the Docker user mailing list.
If you have Jenkins related issues, please ask in the Jenkins mailing lists.
If you are not sure, then this is probably not the place to create an issue and you should use any of the previously mentioned mailing lists.

If after going through the previous checklist you still think you should create an issue here please provide:
Docker commands that you execute
Actual result
Expected outcome
Have you tried a non-dockerized Jenkins and get the expected outcome?
Output of docker version
Other relevant information

ant is not installed by default in the image
https://github.com/jenkinsci/docker#installing-more-tools


Listen to all interfaces

Currently it only listens at localhost:3000
It would be good to access from different devices by localip:3000
I mean to access from devices same network <IP_ADDRESS> something like this

Hi,
use the advanced option to change the binding address. :+1:


Cannot find name 'describe'

[x] bug report

Angular CLI: 1.6.1
Node: 8.2.1
OS: win32 x64
Angular: 5.0.0
... animations, common, compiler, compiler-cli, core, forms
... http, platform-browser, platform-browser-dynamic, router
@angular/cdk: 2.0.0-beta.8
@angular/cli: 1.6.1
@angular/language-service: 4.3.2
@angular/material: 2.0.0-beta.8
@angular/platform-server: 5.1.1
@angular-devkit/build-optimizer: 0.0.36
@angular-devkit/core: 0.0.22
@angular-devkit/schematics: 0.0.42
@ngtools/json-schema: 1.1.0
@ngtools/webpack: 1.9.1
@schematics/angular: 0.1.11
@schematics/schematics: 0.0.11
typescript: 2.4.2
webpack: 3.8.1
Repro steps
Follow guide:
https://github.com/angular/angular-cli/wiki/stories-universal-rendering
Observed behavior
I run;
npm run build:ssr && npm run serve:ssr
dist/browser and dist/server are created, server.js is created but when command:
webpack --config webpack.server.config.js --progress --colors
is executed, then i get this error:
ERROR in D:\Test\trunk-angular5-universal\e2e\app.e2e-spec.ts[tsl] ERROR in D:\Test\trunk-angular5-universal\e2e\app.e2e-spec.ts(3,1) TS2304: Cannot find name 'describe'.
ERROR in D:\Test\trunk-angular5-universal\e2e\app.e2e-spec.ts[tsl] ERROR in D:\Test\trunk-angular5-universal\e2e\app.e2e-spec.ts(6,3) TS2304: Cannot find name 'beforeEach'.
ERROR in D:\Test\trunk-angular5-universal\e2e\app.e2e-spec.ts[tsl] ERROR in D:\Test\trunk-angular5-universal\e2e\app.e2e-spec.ts(10,3) TS2304: Cannot find name 'it'.
ERROR in D:\Test\trunk-angular5-universal\e2e\app.e2e-spec.ts[tsl] ERROR in D:\Test\trunk-angular5-universal\e2e\app.e2e-spec.ts(12,5) TS2304: Cannot find name 'expect'.
Desired behavior
No error
Mention any other details that might be useful (optional)
My package.json:
{
"name": "XXX",
"version": "0.0.0",
"license": "MIT",
"scripts": {
"ng": "ng",
"start": "ng serve",
"build": "ng build",
"test": "ng test",
"lint": "ng lint",
"e2e": "ng e2e",
"build:ssr": "npm run build:client-and-server-bundles && npm run webpack:server",
"serve:ssr": "node dist/server.js",
"build:client-and-server-bundles": "ng build --prod && ng build --prod --app 1 --output-hashing=false",
"webpack:server": "webpack --config webpack.server.config.js --progress --colors"
},
"private": true,
"dependencies": {
"@agm/core": "1.0.0-beta.2",
"@agm/js-marker-clusterer": "1.0.0-beta.1",
"@angular/animations": "5.0.0",
"@angular/cdk": "2.0.0-beta.8",
"@angular/common": "5.0.0",
"@angular/compiler": "5.0.0",
"@angular/core": "5.0.0",
"@angular/forms": "5.0.0",
"@angular/http": "5.0.0",
"@angular/material": "2.0.0-beta.8",
"@angular/platform-browser": "5.0.0",
"@angular/platform-browser-dynamic": "5.0.0",
"@angular/platform-server": "5.1.1",
"@angular/router": "5.0.0",
"@covalent/core": "1.0.0-beta.5-1",
"@nguniversal/module-map-ngfactory-loader": "5.0.0-beta.5",
"@satispay/web-button-factory": "1.0.4",
"@types/angular": "1.6.28",
"@types/node": "6.0.88",
"braintree-web": "3.22.2",
"braintree-web-drop-in": "1.8.0",
"classlist.js": "1.1.20150312",
"core-js": "2.4.1",
"enhanced-resolve": "3.3.0",
"hammerjs": "2.0.8",
"js-marker-clusterer": "1.0.0",
"lory.js": "2.3.3",
"md5": "2.2.1",
"moment": "2.18.1",
"ng2-cookies": "1.0.12",
"ng2-responsive": "0.8.4",
"ng2-scroll-to-el": "1.0.0",
"paypal-checkout": "4.0.133",
"rxjs": "5.5.2",
"sass-loader": "6.0.6",
"ts-loader": "3.2.0",
"web-animations-js": "2.3.1",
"zone.js": "0.8.16"
},
"devDependencies": {
"@angular/cli": "1.6.1",
"@angular/compiler-cli": "5.0.0",
"@angular/language-service": "4.3.2",
"@types/jasmine": "2.5.45",
"@types/node": "6.0.88",
"codelyzer": "3.0.1",
"jasmine-core": "2.6.4",
"jasmine-spec-reporter": "4.1.1",
"karma": "1.7.0",
"karma-chrome-launcher": "2.1.1",
"karma-cli": "1.0.1",
"karma-coverage-istanbul-reporter": "1.3.0",
"karma-jasmine": "1.1.0",
"karma-jasmine-html-reporter": "0.2.2",
"ngx-swiper-wrapper": "5.1.0",
"protractor": "5.1.2",
"ts-node": "3.0.6",
"tslint": "5.3.2",
"typescript": "2.4.2",
"webpack": "3.8.1"
}
}

Could you provide a reproduction git repo we could clone? Seems like your tsconfig might be missing types.

Hi Hans
This is my tsconfig:
{
"compileOnSave": false,
"compilerOptions": {
"outDir": "./dist/out-tsc",
"baseUrl": "src",
"sourceMap": true,
"declaration": false,
"moduleResolution": "node",
"emitDecoratorMetadata": true,
"experimentalDecorators": true,
"target": "es5",
"types": [ "node" ],
"typeRoots": [
"node_modules/@types"
],
"lib": [
"es2016",
"dom"
]
}
}

is there any other info I can give to you, maybe other configuration files or similar?
thanks

for ts2 just do a npm install --save-dev @types/jasmine
Then in the tsconfig have a
"typeRoots": [
"node_modules/@types"
],

Is there a more proper solution to this other than the import {} from 'jasmine' work-around?  I'm having these same issues with an angular project which was previously working fine, but now displays the above errors when running ng serve
I have documented my issue on Stack Overflow

@strommj I don't know if this helps you but I encountered the same problem (typescript service claims there is no 'describe', 'beforeeach' etc even after I checked the @types). ng test was also not locating or executing any tests in my projects. After upgrading my local angular/cli (6.1.5) and global angular/cli (6.2.8) to latest (7.1.4), the errors disappear. Not entirely sure what is happening, but I think the versions can cause confusions.

Thanks @meysamsahragard , did npm install --save-dev<EMAIL_ADDRESS>and it worked

Thanks @meysamsahragard , did npm install --save-dev<EMAIL_ADDRESS>and it worked
Hi @GeoffMahugu. I'm glad that your problem has been resolved.


Null pointer in etcd.go

Is this a BUG REPORT or FEATURE REQUEST?:

/kind bug

What happened:
Null pointer in function CreateHost in file etcd.go when try to get the value of host.Id.
What you expected to happen:
There should not be null pointer
How to reproduce it (as minimally and precisely as possible):
Create replication with no hosts
Anything else we need to know?:
CreateHost would be called by [drcontroller.go]doAttach.
doAttach would check the host list, if there is no host, doAttach would create a host for [etcd.go]CreateHost. But the new created host have no base model, so when [etcd.go]CreateHost try to get the value of host.BaseModel.id, it would meet the null pointer.
Environment:

Hotpot(release/branch) version:
OS (e.g. from /etc/os-release):
Kernel (e.g. uname -a):
Install tools:
Others:

Has been fixed in PR #1119


Binary for Windows?

H there,
Is it possible for you to create a binary for Windows?

Hi @chaoscreater ,
You mean like an .exe?

@paololazzari - Yep

That's not possible as far as I know

How is it not possible? Isn't this just a wrapper for the terraform binary? The terraform binary works on Windows. The code just needs to be tweaked to work on Windows.
It's fine if you don't want to work on it because it's too much effort, but saying that it's not possible just doesn't make any sense.

I thought you were asking whether terraform-repl could be compiled into an .exe
If you're asking about a powershell implementation of terraform-repl, then yes that is possible

yes, if it can be run in Powershell on Windows then it'll be good.


Is there any chromium for arm64 linux lambda?

Is there any chromium for arm64 linux lambda?

not yet https://github.com/aws/aws-lambda-base-images/issues/59 is blocking


ARROW-6174: [C++] Validate chunks in ChunkedArray::Validate. Fix validation of sliced ListArray, values null checks

Validate for ListArray was checking the length of the values buffer against the last offset. When we call Array::Slice, the child values buffer actually is not modified (maybe it should be?) so this invariant is broken. The main thing that matters is that the values buffer is at least as large as the last offset.
Changes validation checks to only assert that values buffer (buffer index 1) is non-null when the length is non-zero. I know that the null values buffer is a controversial topic, but we have code throughout that handles this case so I don't know that we can surely say that such arrays are invalid

Otherwise I think that validating chunks in ChunkedArray::Validate is a good idea.

Travis-CI: https://travis-ci.org/wesm/arrow/builds/574662117


Bank precompile get balances

Describe your changes and provide context
This adds in a bank precompile query functionality to allow for fetching all balances for an account address
Testing performed to validate your change
Unit test updated

Codecov Report
Attention: Patch coverage is 66.66667% with 9 lines in your changes are missing coverage. Please review.

Project coverage is 60.29%. Comparing base (e8d0ce4) to head (fb4775c).

Additional details and impacted files

@@            Coverage Diff             @@
##            seiv2    #1533      +/-   ##
==========================================
- Coverage   60.45%   60.29%   -0.17%
==========================================
  Files         365      365
  Lines       25836    25863      +27
==========================================
- Hits        15620    15594      -26
- Misses       9225     9277      +52
- Partials      991      992       +1

Files
Coverage Δ

precompiles/bank/bank.go
56.11% <66.66%> (+1.35%)
:arrow_up:

... and 1 file with indirect coverage changes


Update all contraceptive matrices to reflect sexual debut restriction

Since merging PR #157 we need to update our contraceptive matrices to reflect the new restriction to agents who have sexually debuted. @mzimmermann-IDM is this possible? We likely won't have it perfectly aligned, because of the five year retrospective (i.e. some women will have sexually debuted during that retrospective period) but I think that will be a small % of respondents.

@mzimmermann-IDM  and @aaslinur - can you also work together to generate a new Ethiopia matrix?

Yep, I have this on my to do list so can work on Ethiopia as well! @aaslinur, let me know if you are doing anything differently for Ethiopia that I should know about.

Yep, I have this on my to do list so can work on Ethiopia as well! @aaslinur, let me know if you are doing anything differently for Ethiopia that I should know about.

Thanks, Marita! That sounds great. I will follow up with you on where things are with the Ethiopia calibration as you are working on this.


Settings: add button to show open source license

closes #436

Text wrapping should be fixed so that incorrect line breaks are removed. See how it is presented on android.

Line breaks should be removed from license and allow label wrap manually.
Here’s a screenshot from dcrandroid.


Crate will not start on Windows if not installed on C:

CrateDB version:
1.0.1
JVM version:
1.8.0_51
OS version / environment description:
Windows 10 Professional x64
Problem description:
I downloaded and expanded the tarball to D:\Crate. The only change made to crate.yml was to add a cluster name.
Running crate.bat results in error: \Crate\Crate-1.0.1/lib/crate-app-1.0.1.jar was unexpected at this time.
Moving the Crate folder to C:\Crate resolved the problem.

hi @tellezb thanks for reporting. we'll have a look!

@tellezb we are not able to reproduce the issue. Tested with Win 8.1 / 10 like you can see in the screen. Can you show us the console output / log output of your start procedure?

Well, we seem to be unable to reproduce now. Wondering if we had a folder with insufficient privileges last time. Fresh setup on the secondary drive seems fine now...


Automated generation of swagger + "fancy" API documentation

Setup some sort of automated job that runs for each commit and generates swagger and fancy API docs.

This might be a little weird if we're using gh-pages (#2).  On commit a job that runs and writes a commit?
we'll have to be careful to not get caught in a loop haha.
Just food for thought for the task-taker.  It still sounds like a good/theright solution to me, we just need to be mindful.

Yeah we might need a docs repo or something


refactor: Move translations to the openedx Transifex project

This tries to get us in line with OEP-58 and using openedx-translations / Atlas to manage the translation files. It's very likely going to require some iteration to get everything working correctly, but we can't do that until this lands since we need to get some actual translation files in Transifex to work with. So consider this part one of at least two.
Will need https://github.com/openedx/openedx-translations/pull/1834 to land to be functional as well, so I'm awaiting feedback on that before merging.
Partially solves: https://github.com/openedx/tutor-contrib-aspects/issues/435

@Ian2012 made a couple of changes based on feedback and to fix tests. Want to take another look?

Amazing! Thanks for pushing on this front :)


Handle case when Sidekiq::Testing is disabled

Connected with #40
Make the have_delayed_job matcher handle the case when the Sidekiq::Testing is disabled (the jobs are enqueued in redis)

Closing this as it would require a large rebase and probably a complete rework


Cannot start the project

Describe the bug
When I try to start the project on Android (real device or emulator) I get:
Process: dev.robingenz.capacitorjs.demo.firebaseplugins, PID: 6450
java.lang.RuntimeException: Unable to start activity ComponentInfo{dev.robingenz.capacitorjs.demo.firebaseplugins/dev.robingenz.capacitorjs.demo.firebaseplugins.MainActivity}: java.lang.IllegalStateException: Default FirebaseApp is not initialized in this process dev.robingenz.capacitorjs.demo.firebaseplugins. Make sure to call FirebaseApp.initializeApp(Context) first.

To Reproduce
Steps to reproduce the behavior:

Follow the instructions to start Android
In Logcat the above error appears

Expected behavior
App runs with no error

You need to add the Firebase Configuration files. I updated the Getting Started section.


Ordering of examples is confusing

The order of the functions should respect the order of the statement on line 103.

Any chance of this getting merged? Not that I'm in a rush to see it in production but it would be nice to get it off my list of open PRs @orta lol

I don't have write access I'm afraid