Unable to install MsBuild on a docker image

Output of docker version:
Client:
 Version:      1.12.0-dev
 API version:  1.24
 Go version:   go1.5.3
 Git commit:   2b97201
 Built:        Tue Apr 26 23:51:36 2016
 OS/Arch:      windows/amd64

Server:
 Version:      1.12.0-dev
 API version:  1.24
 Go version:   go1.5.3
 Git commit:   2b97201
 Built:        Tue Apr 26 23:51:36 2016
 OS/Arch:      windows/amd64

Output of docker info:
Containers: 17
 Running: 0
 Paused: 0
 Stopped: 17
Images: 14
Server Version: 1.12.0-dev
Storage Driver: windowsfilter
 Windows:
Logging Driver: json-file
Plugins:
 Volume: local
 Network: nat null
Kernel Version: 10.0 14300 (14300.1000.amd64fre.rs1_release_svc.160324-1723)
Operating System: Windows Server 2016 Standard Technical Preview 5
OSType: windows
Architecture: x86_64
CPUs: 1
Total Memory: 1.331 GiB
Name: WIN-JIT6DOCS89Q
ID: FLJW:WKG6:IZFM:SHLY:NYPV:BUG3:MIWD:XIFR:2AD4:MD77:T3DM:THDE
Docker Root Dir: C:\ProgramData\docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Insecure Registries:
 <IP_ADDRESS>/8

Additional environment details (AWS, VirtualBox, physical, etc.):
Windows Server 2016 TP5 running in Hyper-V
Steps to reproduce the issue:

RUN nuget install MSBuild.Microsoft.VisualStudio.Web.targets in the Dockerfile
docker build .

Describe the results you received:
Successfully installed 'MSBuild.Microsoft.VisualStudio.Web.targets <IP_ADDRESS>' to C:
hcsshim::ImportLayer failed in Win32: The filename or extension is too long. (0xce) layerId=\?\C:\ProgramData\docker\windowsfilter\6972759b516ea4c61df51460b112fe5aad72c5d3cccba3505692cd580bc967cc flavour=1 folder=C:\Windows\TEMP\hcs190795884
Describe the results you expected:
I expected the install to complete normally, however, it crashes with this message (that tells that MSBuild was installed, but it is not).
Additional information you deem important (e.g. issue happens only occasionally):
It seems to me to be a 32-bit problem, but the Windows Server 2016 TP5 is supposed to be 64-bit and docker is supposed to be 64-bit. I'm using the microsoft/iis base image in the docker file (is that 64 bit?)

I just rebooted the computer after having tried a few things and now it works...

Let me close this issue then, but let us know if you're seeing this issue again

ok ;)


"unable to parse invalid" message seen when upgrading 1.1.x -> 1.3.3

I'm seeing errors upgrading to Marathon 1.3.3 from Marathon 1.1.x. Looks like a data migration case isn't handled properly.
Right here, we expect that marathonTaskStatus exists:
https://github.com/mesosphere/marathon/blob/v1.3.3/src/main/scala/mesosphere/marathon/core/task/tracker/impl/TaskSerializer.scala#L50
However, that field didn't exist in Marathon 1.1.x. If I call getMarathonTaskStatus on a 1.1.x proto buf task, I get Invalid
res68: MarathonTask.MarathonTaskStatus = Invalid

which is status ID 0 (null object, null value)
res70: Int = 0

I have opened a WIP merge request which helped migrate the data. It can be a lot more sophisticated but it worked for my case. There are a lot of cases it doesn't handle, unfortunately, and I am not sure how to best handle those.
https://github.com/mesosphere/marathon/pull/4598

Sorry that this isn't in Phabricator. I don't appear to have access. https://phabricator.mesosphere.com/project/view/1/

Should be fixed in 1.3.4


static property doesn't work with @select decorator and HMR

This is a...

[ ] feature request
[x ] bug report
[ ] usage question

What toolchain are you using for transpilation/bundling?

[ ] @angular/cli
[ ] Custom @ngTools/webpack
[ ] Raw ngc
[ ] SystemJS
[ ] Rollup
[x ] Other

Environment
NodeJS Version: 7.5.0
Typescript Version: 2.1.5
Angular Version: 4.0.1
@angular-redux/store version: 6.4.2
@angular/cli version: (if applicable)
OS: MacOS El Capitan
Link to repo showing the issus
(optional, but helps a lot)
Expected Behaviour:
component: @select() stuff$
template: {{stuff$ | async}} one-way binding should work after hot-reloading with HMR
Actual Behaviour:
one way binding doesn't work after hot-reloading
this.stuff$ = ngRedux.select('stuff') does work as intended
Stack Trace/Error Message:
Nothing
Additional Notes:
(optional) My boilerplate is a slightly modified https://github.com/AngularClass/angular-starter.git
This bug was also reproduced on this boilerplate as-is, with HMR enabled (npm run start:hmr)

I'm a bit behind on the state of HMR with Angular (I use it a lot with React). When you say "'@select` doesn't work" can you clarify? You mean you stop getting updates?

@SethDavenport That's basically it, no updates are received after HMR

OK - I'll try and get to this next week.

Yeah so I can reproduce the issue - and it's likely because for performance / memory reasons @select causes a reference to the NgRedux instance to be cached. If HMR results in a new store instance being created, the @selects are still holding onto the old instance and don't fire when the new store changes.  Looking into how this can be improved.


Updated readme to include CentOS/RHEL/Fedora UnixODBC package name

Updated README.rst to include UnixODBC package name for Red Hat-based distributions.

Codecov Report

Merging #37 into master will not change coverage.
The diff coverage is n/a.


tests: add schema validation unit tests

Follow up PR after #167.

I have read the CLA Document and I hereby sign the CLA

@arys-splunk Just fyi, UI code is now segregated into another repo: https://github.com/splunk/addonfactory-ucc-base-ui.

:tada: This PR is included in version 4.5.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Review: optimize unused parameters

More careful identification and removal of params (input and output) that
are both unused in the shader and not connected downstream.  Previously,
this analysis could be foiled by init ops, which would make it look like
the params were used, and thus the params would not be culled.

LGTM


Error after leaving product page and upload page

What

Some fine tuning needed indeed.

@teolemon beyond that bug, is the new barcode scanner ok in your tests?

Some behaviours have changed in the carrousel.
I'm not completely sure whether that's a bug or a feature.

restarting the app starts at the welcome screen
I lost all my carousel cards once but I haven't been able to reproduce it

Otherwise it seems to be working fine.

@teolemon Strictly about this issue:

I haven't been able to reproduce it lately, but I think I saw it while developing
The red snackbar is ours - we don't have to display it, and we could put a sentry call instead if needed
I'm not sure we can do that much with that "already started" exception - we already check our "is started?" flag, and the way things are coded in kotlin, I suspect that we can always get a "bad luck concurrence exception" (no await there)
That said, I'm about to put an additional controller.isStarting test, which should make the occurrence of the exception less likely

restarting the app starts at the welcome screen

I believe the hot restart would put you back to the start anyway - wasn't it the case before? The hot reload stays on the same page.

I lost all my carousel cards once but I haven't been able to reproduce it

Could that be that it there were debug/release versions and that your previous app version was uninstalled?

I guess I will reopen. We will need broad testing, including on REDMI devices.


horizontal bar, top value is always missing

The green value on top is always hidden, I tried most of the properties but I can't seem to show it.
Is there any way to show it?

have you try LabelPosition.outside ?
Pada tanggal Rab, 27 Jul 2022 pukul 21.16 dro-dev @.***>
menulis:

[image: Screenshot 2022-07-27 at 16 15 52]
https://user-images.githubusercontent.com/70333416/181270069-19df820b-2b32-4f18-a9f3-4f8c3ecdb84f.png
The green value on top is always hidden, I tried most of the properties
but I can't seem to show it.
Is there any way to show it?
—
Reply to this email directly, view it on GitHub
https://github.com/indratrisnar/d_chart/issues/4, or unsubscribe
https://github.com/notifications/unsubscribe-auth/APTLYD43BRA53WCDVTPDC53VWFAFJANCNFSM54ZY735Q
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

sorry, i mean have you try LabelPositio.auto
so it can be outside or inside automatically. when space available to show
label
Pada tanggal Kam, 28 Jul 2022 pukul 08.30 Indra Trisna <
@.***> menulis:

have you try LabelPosition.outside ?
Pada tanggal Rab, 27 Jul 2022 pukul 21.16 dro-dev <
@.***> menulis:

[image: Screenshot 2022-07-27 at 16 15 52]
https://user-images.githubusercontent.com/70333416/181270069-19df820b-2b32-4f18-a9f3-4f8c3ecdb84f.png
The green value on top is always hidden, I tried most of the properties
but I can't seem to show it.
Is there any way to show it?
—
Reply to this email directly, view it on GitHub
https://github.com/indratrisnar/d_chart/issues/4, or unsubscribe
https://github.com/notifications/unsubscribe-auth/APTLYD43BRA53WCDVTPDC53VWFAFJANCNFSM54ZY735Q
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Container logs wont show.

Do you want to request a feature or report a bug?
Bug
What did you do?
Tried to view the BaGet logs with the command:
docker logs  -f
What did you expect to see?
ongoing logs of my operations.
What did you see instead?

The goal was to test nuget.org caching, but that way i found that i cant see any logs.
Is this a known issue?
Cant find any useful information regards the WARN message.
Thank a lot.

P.S
Not sure that this warn is concrete.
There are no logs by definition?

container logs just fine with debug/info level logging.

Thank you @smazurov,
If you dont mind, can you explain how to achieve this log level?

I set it in a appsettings.json  I think you can also achieve it with env vars but I don't have a concrete example, documentation might.

@rong0312 You can update the logging level to Debug in two places:

In the appsettings.json file here
In Docker, By appending Logging__LogLevel__Default=Debug to the baget.env file


pathlib change for object_detection/utils.py

Checklist
GitHub

[ ] I've given this PR a concise, self-descriptive, and meaningful title
[ ] I've linked relevant issues in the PR body
[ ] I've applied the relevant labels to this PR
[ ] I've assigned a reviewer

PR contents

[ ] I've consulted ivadomed's internal developer documentation to ensure my contribution is in line with any relevant design decisions
[ ] I've added relevant tests for my contribution
[ ] I've updated the relevant documentation for my changes, including argparse descriptions, docstrings, and ReadTheDocs tutorial pages

Description

Linked issues

resolves 872

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

5 of 11 (45.45%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 70.109%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

ivadomed/object_detection/utils.py
5
11
45.45%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
4114

Relevant Lines:
5868

💛  - Coveralls


fix: modify rbush package import

Fixes #11473

Hi, I've created https://github.com/mourner/rbush/pull/114 to transpile ES6 features except import/ export in the rbush module. Currently the package specifies module: 'index.js', index.js includes ES6 syntax such as class which is what prompted #10385.
If https://github.com/mourner/rbush/pull/114 is merged then we shouldn't need any changes in OpenLayers but we will gain IE11 support.

If https://github.com/mourner/rbush/pull/114 is merged then we shouldn't need any changes in OpenLayers but we will gain IE11 support.

This is obsolete now that we don't support IE any more and ship untranspiled modules.


xml serialization issue fix

Fixed root element deserialization as per the given document example.
Fixed theme style enum values.

Thanks for raising this PR.  You will notice a few changes - the .NET version does not use the same config as its Java counterpart which is why the initial configuration was setup differently.  I have included the config files as part of this PR and will update the documentation to point to the correct configs.


Thanks! And a few ideas

Thanks very much for this useful GUI! I really hate the keyboard combo because it's hard to find in the dark. (The Lenovo Thinkpad method of Fn+Spacebar is a much better design!) Just a few observations and ideas.
I generally just want to turn the backlight on and off. The GUI has "Turn Off keyboard backlight", which makes sense, but it would also be nice to have a top-level menu item for "Turn ON keyboard backlight" to the default white color, without having to go into the "Mono Color" menu.
Related to this, do you have any thoughts or ideas on this issue?
https://github.com/pobrn/ite8291r3-ctl/issues/13
I would find it very useful if this GUI could also support lightbar control via the tuxedo_keyboard module. I find the Tuxedo Control Center too bloated and intrusive. For now I'm using two systemd services to disable the keyboard backlight and the lightbar by default on bootup:
/etc/systemd/system/off-backlight.service
[Unit]

Description=Turn off NUC9 laptop keyboard backlight at startup

[Service]

Type=oneshot
ExecStart=ite8291r3-ctl off

[Install]

WantedBy=multi-user.target

cat /etc/systemd/system/off-lightbar.service
[Unit]
Description=Turn off the NUC9 lightbar at startup
After=multi-user.target

[Service]
Type=oneshot
ExecStart=/usr/bin/bash -c "/usr/bin/echo 0 > /sys/class/leds/lightbar_rgb\:1\:status/brightness"
ExecStart=/usr/bin/bash -c "/usr/bin/echo 0 > /sys/class/leds/lightbar_rgb\:2\:status/brightness"
ExecStart=/usr/bin/bash -c "/usr/bin/echo 0 > /sys/class/leds/lightbar_rgb\:3\:status/brightness"
RemainAfterExit=true
StandardOutput=journal

[Install]
WantedBy=multi-user.target

I generally find the lightbar to be useless, but I can think of one practical use for it: I'm used to old Thinkpads with their status LED that indicated hard disk activity. Would it be possible to make the lightbar flash or turn on to a specific color to indicate different rates of disk I/O?
Thanks a lot!

you could insert a script in your service or use a crontab and add something like this :
disk_usage= 'iostat | grep nvme1n1 | cut -c 42-45'
if [disk_usage -gt 300]
then
  echo 20 > /sys/devices/platform/tuxedo_keyboard/leds/lightbar_rgb:2:status/brightness
  if [disk_usage -gt 900]
     then
       echo 40 > /sys/devices/platform/tuxedo_keyboard/leds/lightbar_rgb:2:statu/brightness
      fi
else
echo 0 > /sys/devices/platform/tuxedo_keyboard/leds/lightbar_rgb:2:status/brightness
fi

if [disk_usage -gt 1500]
     then
echo 20 > /sys/devices/platform/tuxedo_keyboard/leds/lightbar_rgb:1:status/brightness
else
echo 0 > /sys/devices/platform/tuxedo_keyboard/leds/lightbar_rgb:1:status/brightnes
fi

for sure this as too be looped every 10 sec on smething like that

Very cool! Thanks a lot for the idea.

@yuky2020 That's a good idea. Maybe it would look good to map the values to plasma or inferno colormap (in matplotlib) after some gamma corrections. Or similar... Actually, after switching to Nvme SSD from HDD, I stopped worrying about I/O utilitization. Addition to that, I connected a script to udev battery events and turning off lightbar if the power adapter is disconnected. But I will add this as a recommendation into the Readme. Thanks for the suggestion.
@geckolinux I am happy that it was useful. Thanks for your feedback. I can make it "Turn On/Off" and will act as a toggle. So, this way would keep the UI smaller.

I have added this feature with 4c35b31 . Now it looks better, I think

I may add lightbar control with animation, IO utilization, mono color option, if the lightbar is detected. I will be adding this to the ToDo section.

Fantastic, thanks so much @salihmarangoz !

after switching to Nvme SSD from HDD, I stopped worrying about I/O utilitization. Addition to that, I connected a script to udev battery events and turning off lightbar if the power adapter is disconnected.

Yes, it's not quite as necessary as it used to be. I just tend to use it as a sign that something is going wrong with the system, with my old Thinkpad whenever I saw the disk LED flash really fast or stay on solid it would usually mean a crash or hard lockup was coming.

Thanks again for the latest improvements.
It looks like a little bit more logic needs to be added to the On/Off toggle. As I mentioned, I turn the keyboard off with a Systemd service at boot that runs ite8291r3-ctl off . From there, the GUI On/Off toggle doesn't work and the Fn+F6/F7 keys don't either until I first select a Mono Color in the GUI. After that it all starts working as expected, and the GUI toggle can be used interchangeably with the Fn keys.

Oh yes, it needs some modifications such as persistent states. I am thinking about using the ideas from https://github.com/nalim/ite8291r3-gui . If you have time I welcome pull requests. I will start updating the project after 2 or 3 weeks. But that update will be really big :)

Great, no rush! I'm a pretty bad coder, I can just barely trace my way through existing code. :confounded:  :smiley:  I really do appreciate this utility, it makes a huge difference in everyday usability.
Not specific to your GUI, but I'm still trying to figure out this keyboard backlight, it really seems to have a mind of its own. I usually leave it turned off, but it seems that if I leave the laptop untouched for a while with the screen turned off via power management and then return that the keyboard backlight turns on again. Same for resuming from suspend. But it all feels very random.

Yeah, suspend is a bit problem for now. nalim solved it by setting up systemd services and persistent state memory. I just need some time to check them. When I find time to do it, it will work across reboots and sleep/wake states.
Actually, I did a quick and dirty implementation. I hope I will find a sweet spot between implementing good features and refactoring the old code.

Ah, good to know that there are still options for improvement.
And what about the keyboard backlight turning on after simply touching the trackpad after it's been sitting for a while? I can't figure out why it does that or what controls that.

This may be related to sleep/awake problems. I disabled sleep features on my laptop so it works perfectly. This may be related to other modules as well, different hardwares different problems. It would be better to discuss about it after the updates.


added name to servlet

Step 1 and 2 of Week 3 STEP Tutorial

changed name on servlet to see if it is working
modified index.html and script.js to use fetch() to request content from server and added on index.html
Demonstration: First on index.html then on data
https://drive.google.com/file/d/1pumvWullB4y7jor0m399gcWK3Xs4AHIU/view?usp=sharing

see demonstration link above on github description

Just a quick note, if you still plan on adding more commits to a PR, you should leave the PR as a draft instead of adding us as reviewers quite yet. That way Nick and I can wait until you're ready for us to review it and add comments!


fix sharegpt tool support

@winglian When trying to preprocess glaive sharegpt dataset I came across this issue as well and observed that the tool role parameter in the prompters and strategy would never get used. What is the reason for taking back and closing this commit, since I think it is very much needed?
My actual issue though is that in /src/axolotl/prompt_strategies/init.py  it would always in line 28 after returning the func, run into "ModuleNotFoundError" which I could not debug. Any ideas what could be happening?


[Select] Override MenuProps default props

Hello,
I need to override some default classes and props for my application, however it seems that it's not working very well for nested component.
I want to override the default props of MenuProps object inside the Select component, so I tried to do something like this:
MuiSelect: {
        autoWidth: true,
        variant:   "outlined",

        MenuProps: {
          anchorOrigin: {
            vertical:   "top",
            horizontal: "right",
          },
          transformOrigin: {
            vertical:   "top",
            horizontal: "right",
          },
        },
      },

The autoWidth and variant props are applied, but the nested object MenuProps isn't, do you know if I have done something wrong ?
My Mui-version is 4.7.2

Please provide a full reproduction test case. This would help a lot 👷 .
A live example would be perfect. This codesandbox.io template may be a good starting point. Thank you!

Ok my bad, I think I figured out what my problem was, my component was declared like so:
<Select
          className={classes.inputField}
          value={selectedValue}
          onChange={(event: any) => setSelectedValue(event.target.value)}
          MenuProps={{
           classes: {
             paper: classes.paperClass
          }
        }}
        >
          <MenuItem value={1}>Item #1</MenuItem>
          <MenuItem value={2}>Item #2</MenuItem>
          <MenuItem value={3}>Item #3</MenuItem>
          <MenuItem value={4}>Item #4</MenuItem>
          <MenuItem value={5}>Item #5</MenuItem>
        </Select>

But by declaring some props inside this MenuProps object, it seems that the component doesn't search for props overrides in theme ?
I want to achieve this because I need to set a marginTop on the paper class in order to get the result in the Sandbox below
Here is a sandbox:
https://codesandbox.io/s/amazing-voice-r8zez?fontsize=14&hidenavigation=1&theme=dark
If you uncomment the MenuProps declaration in the App component, default props overridden in theme won't be applied anymore, what I expected is that if I define props manually, they should override the default props overridden, but it doesn't seem to be the case.

We don't deep merge the default props with the provided props. Should we? 🤔

I can keep the workaround of setting inline styles for my component, I just wanted to know if I was doing something wrong, it's the first time I need to customize a theme like this.

I'm not sure we should change the behavior. I think that it's more intuitive to have it behave like regular default props.


Update Cypress tests to assert delete in ServingRuntimeList

Closes: RHOAIENG-3838
Description
This PR aims to update existing cypress tests on ServingRuntimeList.cy.ts to test the delete functionality for model servers
How Has This Been Tested?
npm run test
Test Impact

Request review criteria:

Self checklist (all need to be checked):

[x] The developer has manually tested the changes and verified that the changes work
[x] Commits have been squashed into descriptive, self-contained units of work (e.g. 'WIP' and 'Implements feedback' style messages have been removed)
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has added tests or explained why testing cannot be added (unit or cypress tests for related changes)

If you have UI changes:

[ ] Included any necessary screenshots or gifs if it was a UI change.
[ ] Included tags to the UX team if it was a UI/UX change (find relevant UX in the SMEs section).

After the PR is posted & before it merges:

[ ] The developer has tested their solution on a cluster by using the image produced by the PR to main

@ashley-o0o Can you please review the checklist in the PR's description?

/lgtm

/retest


Add ES6 Template Literals sample

reviewer: @jeffposnick

Reviewed.

Addressed comments. Thanks for reviewing!

:+1:


Sidekiq: Job arguments to CDMDEXER::TransformWorker do not serialize to JSON safely...

Descriptive summary
Running the bundle exec rake umedia:index:harvest rake task returns a flurry of these deprecation warnings:
WARN: Job arguments to CDMDEXER::LoadWorker do not serialize to JSON safely. This will raise an error in
Sidekiq 7.0. See https://github.com/mperham/sidekiq/wiki/Best-Practices or raise an error today
by calling `Sidekiq.strict_args!` during Sidekiq initialization.

Expected behavior
We should be able to run cleanly without deprecations. Investigate and resolve.

Most likely this is caused by symbolic keys passed to ETLWorker in its config hash. We need to dig through everywhere especially the solr url is accessed and allow it to work with a string rather than a symbol
   CDMDEXER::ETLWorker.perform_async(
      solr_config: { url: args.fetch(:solr_url) },
      oai_endpoint: args.fetch(:oai_endpoint),
      cdm_endpoint: args.fetch(:cdm_endpoint),
      set_spec: args[:set_spec] != '""' ? args[:set_spec] : nil,
      batch_size: args.fetch(:batch_size, 10),
      max_compounds: args.fetch(:max_compounds, 10)
    )

This also extends to TransformWorker, where it is passed a list of field_mappings which are not a pure hash. When loading those from yaml and passing them in via rails config settings, the array of mappings contains Config objects rather than a plain hash (as you get if you load from yaml manually) so a bit more is needed to cast it all to Hash and then stringify keys.


Update the staking pool stake page colours and skin tones (Light Mode)

📄 Context
Here are the staking pool's stake page changes on colour, skin tones and fonts in Light mode to comply with the new Cartesi brand. The application's structure did not change, only the look and feel.
PS: Refer to the parent of this issue for references.
PS²: Don't worry about the header and footer, because that is addressed in a separate issue #82
📈 Subtasks
Overall

[x] Make sure the fonts are applied correctly based on the Figma description. i.e.  Where to use each font and what size and weight to be applied.
[x] Make sure the components are round, like the design. We're transitioning from a squared-based design to a round one.

Page sessions

[x] For the page header area:

[x] Apply the new colours and font changes for the backlink.
[x] Check if it is necessary to apply the new colours for the address information.
[x] Check if applying the new colours for the icon when connected as Pool Manager.
[x] Apply the correct colours and tones to the navigation tabs.
[x] Apply changes for the breadcrumbs as per design specs.
[x] When the wallet is disconnected: apply the colours and tones to the Staking in a few steps block. i.e. Icons, the text has the correct font and sizes applied to it.
[x] With wallet connected; For the wallet balance and pool allowance, apply the new colours/fonts to it. Include the warning messages using the support system colours as per design.

[x] Apply design changes to the stake instruction/disclaimer. PS: You may need to clear your localStorage to see it.
[x] Apply the colours changes to the following modals:

[x] Allowance Modal
[x] Deposit Modal
[x] Stake Modal
[x] Unstake Modal
[x] Withdraw Modal

[x] Use the support colour system for the TransactionBanner blocks for.

[x]  Allowance action
[x]  Deposit action
[x]  Stake action
[x]  Unstake action
[x]  Withdrawal action

[x] For the overall Staking area

[x] Apply support system colours for any notification/warning message.
[x] Apply new colours and fonts on the info banner that displays while the deposit is maturing.
[x] Apply new colours and fonts to the deposit button.
[x] Apply new colours and fonts for the Your Pool Balance  card.
[x] Apply new colours and fonts for the Your staked balance  card

[x] Apply updates for my staking activities area

[x]  Apply new colours and font changes for the icons and copy when there is no activity.
[x]  Apply new colours and font changes for the activity items.

[ ] Add here any extra tasks you see fit [Optional]

🎯 Definition of Done

[x] Staking pool's stake page matches the design specs on Figma for Light mode.

@nevendyulgerov,
I saw the original PR #116 was closed and not merged. Is the changes somewhere else?


Origin/personal/ranku/v2handlebars

Added basic support for Plan of treatment section.

I tried it using the sample C-CDA_R2-1_CCD.xml.cda and the template ccd.hbs, and the output results only add the following information. I'm not sure if some other information was missing like "activity" and "title"...
{
      "fullUrl": "urn:uuid:e26977b5-f78a-3411-a8e4-ebeac9011dc4",
      "resource": {
        "resourceType": "CarePlan",
        "id": "e26977b5-f78a-3411-a8e4-ebeac9011dc4",
        "status": "active",
        "intent": "plan",
        "subject": {
          "reference": "Patient/2745d583-e3d1-3f88-8b21-7b59adb60779"
        }
      },
      "request": {
        "method": "PUT",
        "url": "CarePlan/e26977b5-f78a-3411-a8e4-ebeac9011dc4"
      }
    },

Closing this PR to re-write plan of treatment section and submit later.


Remove SolutionsWeb Applications that are no longer needed

Currently there are web applications in the c:\inetpub\wwwroot\SolutionsWeb\Apps folder that should no longer be accessed using the direct URL to the application. i.e. http://hostname/SolutionsWeb/Apps/Templates/StoryTellingAccordion/
We need to find these deprecated items and not include them in future releases.

I am closing this issue since it is not valid for the new dev server..


Clark County Download Site - CSV Format

Clark County has requested the test results to be in csv format.
Steps to follow:

Create csv schema for Clark County, OH
Update org file to reflect csv format

Moving HL7 to CSV.  Jorge will work on this today. Will then resubmit files

@Adrian-Brewster @anshulkumar-usds Submitted settings changes to prod this morning.

Converted to csv on 12/27.


How to set the "lang" attribute programatically? In a +page.server.ts for example

Describe the problem
Hello 👋
If I have a blog where each article can be in a different language, the recomended version on how to handle the lang attribute falls short.
This is because I only know what language the page is when I load the article (in the +page.server.ts), but the transformPageChunk already returned.
This problem is very annoying bc if not done right, on some Androids Google will just translate the site without asking (is a opt out) just based on this lang attribute. And Google translate is very bad at translating.
Describe the proposed solution
Using <svelte:head> to modify the <html> tag. Like a <svelte:html>.
Alternatives considered
Run transformPageChunk in a load function.
Importance
would make my life easier
Additional Information
Other people with the same problem:

https://github.com/sveltejs/kit/issues/5508
https://github.com/sveltejs/kit/issues/3091#issuecomment-1541880297

Another potential solution would be to add a %sveltekit.lang% the same way as %sveltekit.head% or %sveltekit.body%

you posted here about the same problem already. https://github.com/opral/inlang-paraglide-js/issues/134
converting to discussion as this is not an issue with sveltekit itself but rather a question about an unusual arcitecture.


Recording failed

describe：The live broadcast is normal, the recording of the live broadcast is unsuccessful, and the stream is pushed to the srs server through rtmp, and then the pull stream also fails. all black
Pictures from the live broadcast

Recording failed
failed to access template
http://egress-composite.livekit.io/?layout=speaker-dark&url=ws%3A%2F%2F<IP_ADDRESS>%3A7880&token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJleHAiOjE2NTY2Njc2MTYsImlzcyI6IkFQSVBqeFk3bmNjWnpFbyIsIm5iZiI6MTY1NjU4MTIxNiwic3ViIjoiRUdfN2JtcUFtaDRyd0NmIiwidmlkZW8iOnsiY2FuUHVibGlzaCI6ZmFsc2UsImNhblB1Ymxpc2hEYXRhIjpmYWxzZSwiY2FuU3Vic2NyaWJlIjp0cnVlLCJoaWRkZW4iOnRydWUsInJlY29yZGVyIjp0cnVlLCJyb29tIjoidGVzdDU1NTU1Iiwicm9vbUpvaW4iOnRydWV9fQ.QJq8DGj1EuspVkOC2l5Z_R1vyrhb4vF5XGPkK-K9UdM

The resulting recorded live video is a black screen

Why is there no audio and video  recorded?
livekit-serve log
2022-06-30T09:23:45.782Z	INFO	livekit	service/wire_gen.go:168	using multi-node routing via redis	{"sentinel": false, "addr": "redis:6379"}
2022-06-30T09:23:45.869Z	INFO	livekit	service/server.go:197	starting LiveKit server	{"addr": ":7880", "nodeID": "ND_198vKAkb", "nodeIP": "<IP_ADDRESS>", "version": "1.1.0", "rtc.portTCP": 7881, "rtc.portUDP": 7882}
2022-06-30T09:26:13.826Z	INFO	livekit	service/rtcservice.go:211	new client WS connected	{"room": "test55555", "participant": "kkk", "connID": "CO_K5rPBGek3GSD", "roomID": "RM_UcB9Z8T3HLUx"}
2022-06-30T09:26:13.839Z	INFO	livekit	rtc/room.go:276	new participant joined	{"room": "test55555", "roomID": "RM_UcB9Z8T3HLUx", "pID": "PA_KzcBVYzNCB65", "participant": "kkk", "protocol": 7, "options": {"AutoSubscribe":true}}
2022-06-30T09:26:14.575Z	INFO	livekit	rtc/participant.go:1104	mediaTrack published	{"room": "test55555", "roomID": "RM_UcB9Z8T3HLUx", "participant": "kkk", "pID": "PA_KzcBVYzNCB65", "kind": "audio", "trackID": "TR_AMy9nDFrSrwmvQ", "rid": "", "SSRC": 449006131}
2022-06-30T09:26:14.985Z	INFO	livekit	buffer/buffer.go:187	REMB not supported, RTCP feedback will not be generated	{"room": "test55555", "roomID": "RM_UcB9Z8T3HLUx", "participant": "kkk", "pID": "PA_KzcBVYzNCB65", "trackID": "TR_VCVJYtHm7zXuQ9", "mime": "video/vp8", "layer": 0}
2022-06-30T09:26:14.986Z	INFO	livekit	rtc/participant.go:1104	mediaTrack published	{"room": "test55555", "roomID": "RM_UcB9Z8T3HLUx", "participant": "kkk", "pID": "PA_KzcBVYzNCB65", "kind": "video", "trackID": "TR_VCVJYtHm7zXuQ9", "rid": "q", "SSRC":<PHONE_NUMBER>}
2022-06-30T09:26:14.991Z	INFO	livekit	buffer/buffer.go:187	REMB not supported, RTCP feedback will not be generated	{"room": "test55555", "roomID": "RM_UcB9Z8T3HLUx", "participant": "kkk", "pID": "PA_KzcBVYzNCB65", "trackID": "TR_VCVJYtHm7zXuQ9", "mime": "video/vp8", "layer": 1}
2022-06-30T09:26:14.991Z	INFO	livekit	rtc/participant.go:1104	mediaTrack published	{"room": "test55555", "roomID": "RM_UcB9Z8T3HLUx", "participant": "kkk", "pID": "PA_KzcBVYzNCB65", "kind": "video", "trackID": "TR_VCVJYtHm7zXuQ9", "rid": "h", "SSRC":<PHONE_NUMBER>}
2022-06-30T09:26:15.259Z	INFO	livekit	buffer/buffer.go:187	REMB not supported, RTCP feedback will not be generated	{"room": "test55555", "roomID": "RM_UcB9Z8T3HLUx", "participant": "kkk", "pID": "PA_KzcBVYzNCB65", "trackID": "TR_VCVJYtHm7zXuQ9", "mime": "video/vp8", "layer": 2}
2022-06-30T09:26:15.259Z	INFO	livekit	rtc/participant.go:1104	mediaTrack published	{"room": "test55555", "roomID": "RM_UcB9Z8T3HLUx", "participant": "kkk", "pID": "PA_KzcBVYzNCB65", "kind": "video", "trackID": "TR_VCVJYtHm7zXuQ9", "rid": "f", "SSRC":<PHONE_NUMBER>}
2022-06-30T09:30:19.776Z	INFO	livekit	buffer/buffer.go:187	REMB not supported, RTCP feedback will not be generated	{"room": "test55555", "roomID": "RM_UcB9Z8T3HLUx", "participant": "kkk", "pID": "PA_KzcBVYzNCB65", "trackID": "TR_VShXseUVXrvSCg", "mime": "video/vp8", "layer": 0}
2022-06-30T09:30:19.779Z	INFO	livekit	rtc/participant.go:1104	mediaTrack published	{"room": "test55555", "roomID": "RM_UcB9Z8T3HLUx", "participant": "kkk", "pID": "PA_KzcBVYzNCB65", "kind": "video", "trackID": "TR_VShXseUVXrvSCg", "rid": "q", "SSRC": 30706227}
2022-06-30T09:30:19.804Z	INFO	livekit	buffer/buffer.go:187	REMB not supported, RTCP feedback will not be generated	{"room": "test55555", "roomID": "RM_UcB9Z8T3HLUx", "participant": "kkk", "pID": "PA_KzcBVYzNCB65", "trackID": "TR_VShXseUVXrvSCg", "mime": "video/vp8", "layer": 1}
2022-06-30T09:30:19.804Z	INFO	livekit	rtc/participant.go:1104	mediaTrack published	{"room": "test55555", "roomID": "RM_UcB9Z8T3HLUx", "participant": "kkk", "pID": "PA_KzcBVYzNCB65", "kind": "video", "trackID": "TR_VShXseUVXrvSCg", "rid": "h", "SSRC":<PHONE_NUMBER>}

egress log
+ pulseaudio -D --verbose --exit-idle-time=-1 --system --disallow-exit
W: [pulseaudio] main.c: Running in system mode, but --disallow-module-loading not set.
N: [pulseaudio] main.c: Running in system mode, forcibly disabling SHM mode.
I: [pulseaudio] main.c: Daemon startup successful.
+ exec egress
{"level":"info","ts":1656581025.7347176,"logger":"egress","caller":"server/main.go:169","msg":"connecting to redis","nodeID":"NE_ZHF2QFBm6utJ","addr":"redis:6379"}
{"level":"debug","ts":1656581025.7416909,"logger":"egress","caller":"service/service.go:65","msg":"starting service","nodeID":"NE_ZHF2QFBm6utJ"}
{"level":"debug","ts":1656581025.7469819,"logger":"egress","caller":"service/service.go:95","msg":"service ready","nodeID":"NE_ZHF2QFBm6utJ"}
{"level":"debug","ts":1656581216.8710685,"logger":"egress","caller":"service/service.go:161","msg":"request received","nodeID":"NE_ZHF2QFBm6utJ","egressID":"EG_7bmqAmh4rwCf","requestID":"RPC_iEYWtigsfV9C","senderID":"ND_198vKAkb"}
{"level":"debug","ts":1656581216.8711743,"logger":"egress","caller":"sysload/cpu.go:154","msg":"cpu request","nodeID":"NE_ZHF2QFBm6utJ","accepted":true,"availableCPUs":5.8860103626943,"numCPUs":6}
{"level":"info","ts":1656581216.8722072,"logger":"egress","caller":"service/service.go:204","msg":"request accepted","nodeID":"NE_ZHF2QFBm6utJ","egressID":"EG_7bmqAmh4rwCf","requestID":"RPC_iEYWtigsfV9C","senderID":"ND_198vKAkb"}
{"level":"debug","ts":1656581216.872407,"logger":"egress","caller":"params/params.go:591","msg":"writing to file","nodeID":"NE_ZHF2QFBm6utJ","egressID":"EG_7bmqAmh4rwCf","filename":"/EG_7bmqAmh4rwCf/caumoo23k1kc0evptlug.mp4"}
{"level":"debug","ts":1656581216.911763,"logger":"egress","caller":"server/main.go:119","msg":"handler launched","nodeID":"NE_RQnq7gc7hkAD"}
{"level":"info","ts":1656581216.912395,"logger":"egress","caller":"server/main.go:169","msg":"connecting to redis","nodeID":"NE_RQnq7gc7hkAD","addr":"redis:6379"}
{"level":"debug","ts":1656581216.9191887,"logger":"egress","caller":"params/params.go:591","msg":"writing to file","nodeID":"NE_RQnq7gc7hkAD","egressID":"EG_7bmqAmh4rwCf","filename":"/EG_7bmqAmh4rwCf/caumoo23k1kc0evptlug.mp4"}
{"level":"debug","ts":1656581216.9376624,"logger":"egress","caller":"source/web.go:114","msg":"launching xvfb","nodeID":"NE_RQnq7gc7hkAD","egressID":"EG_7bmqAmh4rwCf","display":":2125642851","dims":"1920x1080x24"}
{"level":"debug","ts":1656581216.9416354,"logger":"egress","caller":"source/web.go:128","msg":"launching chrome","nodeID":"NE_RQnq7gc7hkAD","egressID":"EG_7bmqAmh4rwCf","url":"https://egress-composite.livekit.io?layout=speaker-dark&url=ws%3A%2F%2F<IP_ADDRESS>%3A7880&token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJleHAiOjE2NTY2Njc2MTYsImlzcyI6IkFQSVBqeFk3bmNjWnpFbyIsIm5iZiI6MTY1NjU4MTIxNiwic3ViIjoiRUdfN2JtcUFtaDRyd0NmIiwidmlkZW8iOnsiY2FuUHVibGlzaCI6ZmFsc2UsImNhblB1Ymxpc2hEYXRhIjpmYWxzZSwiY2FuU3Vic2NyaWJlIjp0cnVlLCJoaWRkZW4iOnRydWUsInJlY29yZGVyIjp0cnVlLCJyb29tIjoidGVzdDU1NTU1Iiwicm9vbUpvaW4iOnRydWV9fQ.QJq8DGj1EuspVkOC2l5Z_R1vyrhb4vF5XGPkK-K9UdM"}
{"level":"debug","ts":1656581221.595888,"logger":"egress","caller":"source/web.go:212","msg":"chrome log: START_RECORDING","nodeID":"NE_RQnq7gc7hkAD","egressID":"EG_7bmqAmh4rwCf"}
{"level":"debug","ts":1656581221.6350396,"logger":"egress","caller":"pipeline/pipeline.go:639","msg":"[src] STREAM-STATUS - Stream status from mp4mux0: A new thread needs to be created","nodeID":"NE_RQnq7gc7hkAD","egressID":"EG_7bmqAmh4rwCf"}
{"level":"debug","ts":1656581221.6352065,"logger":"egress","caller":"pipeline/pipeline.go:639","msg":"[src] STREAM-STATUS - Stream status from queue0: A new thread needs to be created","nodeID":"NE_RQnq7gc7hkAD","egressID":"EG_7bmqAmh4rwCf"}
{"level":"debug","ts":1656581221.6352396,"logger":"egress","caller":"pipeline/pipeline.go:639","msg":"[src] STREAM-STATUS - Stream status from mp4mux0: A thread has entered its loop function","nodeID":"NE_RQnq7gc7hkAD","egressID":"EG_7bmqAmh4rwCf"}
{"level":"debug","ts":1656581221.6352954,"logger":"egress","caller":"pipeline/pipeline.go:639","msg":"[src] STREAM-STATUS - Stream status from queue0: A thread has entered its loop function","nodeID":"NE_RQnq7gc7hkAD","egressID":"EG_7bmqAmh4rwCf"}
{"level":"debug","ts":1656581221.6353571,"logger":"egress","caller":"pipeline/pipeline.go:639","msg":"[src] STREAM-STATUS - Stream status from queue1: A new thread needs to be created","nodeID":"NE_RQnq7gc7hkAD","egressID":"EG_7bmqAmh4rwCf"}
{"level":"debug","ts":1656581221.6354356,"logger":"egress","caller":"pipeline/pipeline.go:639","msg":"[src] STREAM-STATUS - Stream status from queue1: A thread has entered its loop function","nodeID":"NE_RQnq7gc7hkAD","egressID":"EG_7bmqAmh4rwCf"}
{"level":"debug","ts":1656581221.635546,"logger":"egress","caller":"pipeline/pipeline.go:639","msg":"[src] STREAM-STATUS - Stream status from ximagesrc0: A new thread needs to be created","nodeID":"NE_RQnq7gc7hkAD","egressID":"EG_7bmqAmh4rwCf"}
{"level":"debug","ts":1656581221.635617,"logger":"egress","caller":"pipeline/pipeline.go:639","msg":"[src] STREAM-STATUS - Stream status from pulsesrc0: A new thread needs to be created","nodeID":"NE_RQnq7gc7hkAD","egressID":"EG_7bmqAmh4rwCf"}
{"level":"debug","ts":1656581221.6356897,"logger":"egress","caller":"pipeline/pipeline.go:639","msg":"[pipeline] NEW-CLOCK - Got a new clock","nodeID":"NE_RQnq7gc7hkAD","egressID":"EG_7bmqAmh4rwCf"}
{"level":"debug","ts":1656581221.6357462,"logger":"egress","caller":"pipeline/pipeline.go:639","msg":"[src] STREAM-STATUS - Stream status from ximagesrc0: A thread has entered its loop function","nodeID":"NE_RQnq7gc7hkAD","egressID":"EG_7bmqAmh4rwCf"}
{"level":"debug","ts":1656581221.6359053,"logger":"egress","caller":"pipeline/pipeline.go:639","msg":"[src] STREAM-STATUS - Stream status from pulsesrc0: A thread has entered its loop function","nodeID":"NE_RQnq7gc7hkAD","egressID":"EG_7bmqAmh4rwCf"}
{"level":"debug","ts":1656581221.638062,"logger":"egress","caller":"pipeline/pipeline.go:639","msg":"[audiosrcringbuffer0] STREAM-STATUS - Stream status from pulsesrc0: A thread has entered its loop function","nodeID":"NE_RQnq7gc7hkAD","egressID":"EG_7bmqAmh4rwCf"}
{"level":"debug","ts":1656581221.638899,"logger":"egress","caller":"pipeline/pipeline.go:639","msg":"[pulsesrc0] LATENCY - Element's latency has changed","nodeID":"NE_RQnq7gc7hkAD","egressID":"EG_7bmqAmh4rwCf"}
{"level":"debug","ts":1656581221.6448984,"logger":"egress","caller":"pipeline/pipeline.go:639","msg":"[x264enc0] LATENCY - Element's latency has changed","nodeID":"NE_RQnq7gc7hkAD","egressID":"EG_7bmqAmh4rwCf"}
{"level":"debug","ts":1656581223.7135222,"logger":"egress","caller":"pipeline/pipeline.go:639","msg":"[pipeline] STREAM-START - Pipeline stream is starting","nodeID":"NE_RQnq7gc7hkAD","egressID":"EG_7bmqAmh4rwCf"}
{"level":"debug","ts":1656581223.7136822,"logger":"egress","caller":"pipeline/pipeline.go:639","msg":"[pipeline] ASYNC-DONE - Async task completed","nodeID":"NE_RQnq7gc7hkAD","egressID":"EG_7bmqAmh4rwCf"}
{"level":"info","ts":1656581223.71529,"logger":"egress","caller":"service/handler.go:129","msg":"egress updated","nodeID":"NE_RQnq7gc7hkAD","egressID":"EG_7bmqAmh4rwCf","status":"EGRESS_ACTIVE"}
{"level":"debug","ts":1656581289.708992,"logger":"egress","caller":"service/handler.go:81","msg":"handling request","nodeID":"NE_RQnq7gc7hkAD","egressID":"EG_7bmqAmh4rwCf","requestID":"RPC_hVsiKhqkvFeM"}
{"level":"info","ts":1656581289.7090523,"logger":"egress","caller":"service/handler.go:129","msg":"egress updated","nodeID":"NE_RQnq7gc7hkAD","egressID":"EG_7bmqAmh4rwCf","status":"EGRESS_ENDING"}
{"level":"debug","ts":1656581289.70937,"logger":"egress","caller":"pipeline/pipeline.go:476","msg":"sending EOS to pipeline","nodeID":"NE_RQnq7gc7hkAD","egressID":"EG_7bmqAmh4rwCf"}
{"level":"debug","ts":1656581289.7114043,"logger":"egress","caller":"service/handler.go:147","msg":"request handled","nodeID":"NE_RQnq7gc7hkAD","egressID":"EG_7bmqAmh4rwCf","requestID":"RPC_hVsiKhqkvFeM","senderID":"ND_198vKAkb"}
{"level":"debug","ts":1656581289.7149282,"logger":"egress","caller":"pipeline/pipeline.go:560","msg":"EOS received, stopping pipeline","nodeID":"NE_RQnq7gc7hkAD","egressID":"EG_7bmqAmh4rwCf"}
{"level":"debug","ts":1656581289.733569,"logger":"egress","caller":"pipeline/pipeline.go:677","msg":"pipeline stopped","nodeID":"NE_RQnq7gc7hkAD","egressID":"EG_7bmqAmh4rwCf"}
{"level":"debug","ts":1656581289.8023732,"logger":"egress","caller":"pipeline/pipeline.go:291","msg":"uploading to s3","nodeID":"NE_RQnq7gc7hkAD","egressID":"EG_7bmqAmh4rwCf"}
{"level":"debug","ts":1656581290.8030593,"logger":"egress","caller":"pipeline/pipeline.go:258","msg":"removing temporary directory","nodeID":"NE_RQnq7gc7hkAD","egressID":"EG_7bmqAmh4rwCf","path":"/EG_7bmqAmh4rwCf/"}
{"level":"info","ts":1656581290.8035176,"logger":"egress","caller":"service/handler.go:127","msg":"egress completed","nodeID":"NE_RQnq7gc7hkAD","egressID":"EG_7bmqAmh4rwCf"}

Hi nelsonkit,
I found that your livekit server ip is <IP_ADDRESS> and it is internal IP,so the template script may be cannot access it base on error : chrome show it net connect timeout.
I guess there are two reasons:
The first one is the template script cannot access the internal ip , so you can use public ip if you already deploy the server to internet.
The  second one is you may use insecure ws protocol but the "insecure" is true in your egress config or your egress server cannot touth the livekit?
Please show your deploy environment detail and networks about them and the config files of livekit, egress.

Because I am running locally. <IP_ADDRESS>, <IP_ADDRESS> and container ip have been tried, the results are the same
It is also described in the documentation
https://docs.livekit.io/deploy/egress/

livekit.yaml
port: 7880
log_level: info
rtc:
    udp_port: 7882
    tcp_port: 7881
    port_range_start: 50000
    port_range_end: 60000
    use_external_ip: false
keys:
    APIhrekMBfMsKXB: ***
logging:
    json: false
    level: info
redis:
    address: redis:6379
    username: ""
    password: ""
    db: 0

egress config.yaml
log_level: debug
api_key: ****
api_secret: ****
ws_url: ws://<IP_ADDRESS>:7880
insecure: true
redis:
    address: redis:6379
    username: ""
    password: ""
    db: 0

hi @nelsonkti ,
I think this guide used only egree runing in mac/windows local and livekit server running in docker container, if your egree running in docker at local too. You should set "insecure" as false and try it again.
Thanks
Tom Xiong

The document is works well for me.
My environment is wsl2 and docker desktop at windows 11. And I had a local IP address which the corp DHCP assigned. It is <IP_ADDRESS>.
I try to ping host.docker.internal and it return the IP is <IP_ADDRESS> too.
xionggang@DESKTOP-5HGRQV2:~/egress$ ping host.docker.internal
PING host.docker.internal (<IP_ADDRESS>) 56(84) bytes of data.
64 bytes from host.docker.internal (<IP_ADDRESS>): icmp_seq=1 ttl=127 time=0.272 ms
64 bytes from host.docker.internal (<IP_ADDRESS>): icmp_seq=2 ttl=127 time=0.270 ms
64 bytes from host.docker.internal (<IP_ADDRESS>): icmp_seq=3 ttl=127 time=0.202 ms
64 bytes from host.docker.internal (<IP_ADDRESS>): icmp_seq=4 ttl=127 time=0.229 ms
64 bytes from host.docker.internal (<IP_ADDRESS>): icmp_seq=5 ttl=127 time=0.197 ms
64 bytes from host.docker.internal (<IP_ADDRESS>): icmp_seq=6 ttl=127 time=0.301 ms
64 bytes from host.docker.internal (<IP_ADDRESS>): icmp_seq=7 ttl=127 time=0.215 ms
^C
--- host.docker.internal ping statistics ---
7 packets transmitted, 7 received, 0% packet loss, time 6231ms
rtt min/avg/max/mdev = 0.197/0.240/0.301/0.037 ms

And my egree configuration file like below:
ws_url: ws://<IP_ADDRESS>:7880
...
insecure: true

And I used the livekit-cli command to start egress record:
xionggang@DESKTOP-5HGRQV2:~/egress$ livekit-cli start-room-composite-egress --api-key **** --api-secret ****** --request request.json

The request.json :
{
  "room_name": "****",
  "file": {
    "file_type": "MP4",
    "filepath": "/out/data/room-composite-1.mp4"
  }
}

The logs of egress at below:
{"level":"debug","ts":1657528676.7642732,"logger":"egress","caller":"params/params.go:591","msg":"writing to file","nodeID":"NE_qSP4UmsaVy9r","egressID":"EG_LXWS2nRSAPmK","filename":"/out/data/room-composite-1.mp4"}
{"level":"debug","ts":1657528676.7742138,"logger":"egress","caller":"source/web.go:114","msg":"launching xvfb","nodeID":"NE_qSP4UmsaVy9r","egressID":"EG_LXWS2nRSAPmK","display":":1922107087","dims":"1920x1080x24"}
{"level":"debug","ts":1657528676.774687,"logger":"egress","caller":"source/web.go:128","msg":"launching chrome","nodeID":"NE_qSP4UmsaVy9r","egressID":"EG_LXWS2nRSAPmK","url":"https://egress-composite.livekit.io?layout=&url=ws%3A%2F%2F<IP_ADDRESS>%3A7880&token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJleHAiOjE2NTc2MTUwNzYsImlzcyI6IkFQSXFpOXpHTEJWVHNlUSIsIm5iZiI6MTY1NzUyODY3Niwic3ViIjoiRUdfTFhXUzJuUlNBUG1LIiwidmlkZW8iOnsiY2FuUHVibGlzaCI6ZmFsc2UsImNhblB1Ymxpc2hEYXRhIjpmYWxzZSwiY2FuU3Vic2NyaWJlIjp0cnVlLCJoaWRkZW4iOnRydWUsInJlY29yZGVyIjp0cnVlLCJyb29tIjoic3RhcmstdG93ZXIiLCJyb29tSm9pbiI6dHJ1ZX19.orkoIARcOfF9Z1tLv4NPnv9PsHDTA5aXBwuuekJF-V0"}
{"level":"debug","ts":1657528698.1769161,"logger":"egress","caller":"source/web.go:212","msg":"chrome log: START_RECORDING","nodeID":"NE_qSP4UmsaVy9r","egressID":"EG_LXWS2nRSAPmK"}
{"level":"debug","ts":1657528698.224754,"logger":"egress","caller":"pipeline/pipeline.go:639","msg":"[src] STREAM-STATUS - Stream status from mp4mux0: A new thread needs to be created","nodeID":"NE_qSP4UmsaVy9r","egressID":"EG_LXWS2nRSAPmK"}
{"level":"debug","ts":1657528698.225099,"logger":"egress","caller":"pipeline/pipeline.go:639","msg":"[src] STREAM-STATUS - Stream status from mp4mux0: A thread has entered its loop function","nodeID":"NE_qSP4UmsaVy9r","egressID":"EG_LXWS2nRSAPmK"}
{"level":"debug","ts":1657528698.2251437,"logger":"egress","caller":"pipeline/pipeline.go:639","msg":"[src] STREAM-STATUS - Stream status from queue0: A new thread needs to be created","nodeID":"NE_qSP4UmsaVy9r","egressID":"EG_LXWS2nRSAPmK"}
{"level":"debug","ts":1657528698.2251945,"logger":"egress","caller":"pipeline/pipeline.go:639","msg":"[src] STREAM-STATUS - Stream status from queue1: A new thread needs to be created","nodeID":"NE_qSP4UmsaVy9r","egressID":"EG_LXWS2nRSAPmK"}
{"level":"debug","ts":1657528698.2252765,"logger":"egress","caller":"pipeline/pipeline.go:639","msg":"[src] STREAM-STATUS - Stream status from queue0: A thread has entered its loop function","nodeID":"NE_qSP4UmsaVy9r","egressID":"EG_LXWS2nRSAPmK"}
{"level":"debug","ts":1657528698.2253146,"logger":"egress","caller":"pipeline/pipeline.go:639","msg":"[src] STREAM-STATUS - Stream status from queue1: A thread has entered its loop function","nodeID":"NE_qSP4UmsaVy9r","egressID":"EG_LXWS2nRSAPmK"}
{"level":"debug","ts":1657528698.225399,"logger":"egress","caller":"pipeline/pipeline.go:639","msg":"[src] STREAM-STATUS - Stream status from ximagesrc0: A new thread needs to be created","nodeID":"NE_qSP4UmsaVy9r","egressID":"EG_LXWS2nRSAPmK"}
{"level":"debug","ts":1657528698.2254605,"logger":"egress","caller":"pipeline/pipeline.go:639","msg":"[src] STREAM-STATUS - Stream status from ximagesrc0: A thread has entered its loop function","nodeID":"NE_qSP4UmsaVy9r","egressID":"EG_LXWS2nRSAPmK"}
{"level":"debug","ts":1657528698.225499,"logger":"egress","caller":"pipeline/pipeline.go:639","msg":"[src] STREAM-STATUS - Stream status from pulsesrc0: A new thread needs to be created","nodeID":"NE_qSP4UmsaVy9r","egressID":"EG_LXWS2nRSAPmK"}
{"level":"debug","ts":1657528698.2255712,"logger":"egress","caller":"pipeline/pipeline.go:639","msg":"[src] STREAM-STATUS - Stream status from pulsesrc0: A thread has entered its loop function","nodeID":"NE_qSP4UmsaVy9r","egressID":"EG_LXWS2nRSAPmK"}
{"level":"debug","ts":1657528698.2256262,"logger":"egress","caller":"pipeline/pipeline.go:639","msg":"[pipeline] NEW-CLOCK - Got a new clock","nodeID":"NE_qSP4UmsaVy9r","egressID":"EG_LXWS2nRSAPmK"}
{"level":"debug","ts":1657528698.2280595,"logger":"egress","caller":"pipeline/pipeline.go:639","msg":"[audiosrcringbuffer0] STREAM-STATUS - Stream status from pulsesrc0: A thread has entered its loop function","nodeID":"NE_qSP4UmsaVy9r","egressID":"EG_LXWS2nRSAPmK"}
{"level":"debug","ts":1657528698.2281253,"logger":"egress","caller":"pipeline/pipeline.go:639","msg":"[pulsesrc0] LATENCY - Element's latency has changed","nodeID":"NE_qSP4UmsaVy9r","egressID":"EG_LXWS2nRSAPmK"}
{"level":"debug","ts":1657528698.2313313,"logger":"egress","caller":"pipeline/pipeline.go:639","msg":"[x264enc0] LATENCY - Element's latency has changed","nodeID":"NE_qSP4UmsaVy9r","egressID":"EG_LXWS2nRSAPmK"}
{"level":"debug","ts":1657528700.4918742,"logger":"egress","caller":"pipeline/pipeline.go:639","msg":"[pipeline] STREAM-START - Pipeline stream is starting","nodeID":"NE_qSP4UmsaVy9r","egressID":"EG_LXWS2nRSAPmK"}
{"level":"debug","ts":1657528700.492743,"logger":"egress","caller":"pipeline/pipeline.go:639","msg":"[pipeline] ASYNC-DONE - Async task completed","nodeID":"NE_qSP4UmsaVy9r","egressID":"EG_LXWS2nRSAPmK"}
{"level":"info","ts":1657528700.4932716,"logger":"egress","caller":"service/handler.go:129","msg":"egress updated","nodeID":"NE_qSP4UmsaVy9r","egressID":"EG_LXWS2nRSAPmK","status":"EGRESS_ACTIVE"}
{"level":"debug","ts":1657528838.0291975,"logger":"egress","caller":"service/handler.go:81","msg":"handling request","nodeID":"NE_qSP4UmsaVy9r","egressID":"EG_LXWS2nRSAPmK","requestID":"RPC_DaTXLstiMrGZ"}
{"level":"info","ts":1657528838.0292625,"logger":"egress","caller":"service/handler.go:129","msg":"egress updated","nodeID":"NE_qSP4UmsaVy9r","egressID":"EG_LXWS2nRSAPmK","status":"EGRESS_ENDING"}
{"level":"debug","ts":1657528838.0326715,"logger":"egress","caller":"pipeline/pipeline.go:476","msg":"sending EOS to pipeline","nodeID":"NE_qSP4UmsaVy9r","egressID":"EG_LXWS2nRSAPmK"}
{"level":"debug","ts":1657528838.0358543,"logger":"egress","caller":"service/handler.go:147","msg":"request handled","nodeID":"NE_qSP4UmsaVy9r","egressID":"EG_LXWS2nRSAPmK","requestID":"RPC_DaTXLstiMrGZ","senderID":"ND_b06c5OrD"}
{"level":"debug","ts":1657528838.9775455,"logger":"egress","caller":"pipeline/pipeline.go:560","msg":"EOS received, stopping pipeline","nodeID":"NE_qSP4UmsaVy9r","egressID":"EG_LXWS2nRSAPmK"}
{"level":"debug","ts":1657528838.9822376,"logger":"egress","caller":"pipeline/pipeline.go:677","msg":"pipeline stopped","nodeID":"NE_qSP4UmsaVy9r","egressID":"EG_LXWS2nRSAPmK"}
{"level":"info","ts":1657528839.0376534,"logger":"egress","caller":"service/handler.go:127","msg":"egress completed","nodeID":"NE_qSP4UmsaVy9r","egressID":"EG_LXWS2nRSAPmK"}

@nelsonkti , I think you have to confirm the livekit IP of your environment first.

@nelsonkti

I also got the error message from template url, but it is not same with your. I can see the "connection timeout" and I got "ws is not secured" but it works well for me.

You can see that the recording is not？

@nelsonkti
Yes, I follow the document and got the same result like you:
xionggang@DESKTOP-5HGRQV2:~/egress$ docker run -it --rm alpine nslookup host.docker.internal
Unable to find image 'alpine:latest' locally
latest: Pulling from library/alpine
2408cc74d12b: Already exists
Digest: sha256:686d8c9dfa6f3ccfc8230bc3178d23f84eeaf7e457f36f271ab1acc53015037c
Status: Downloaded newer image for alpine:latest
Server:         <IP_ADDRESS>
Address:        <IP_ADDRESS>:53

Non-authoritative answer:

Non-authoritative answer:
Name:   xionggang@DESKTOP-5HGRQV2:~/egress$ docker run -it --rm alpine nslookup host.docker.internal
Unable to find image 'alpine:latest' locally
latest: Pulling from library/alpine
2408cc74d12b: Already exists
Digest: sha256:686d8c9dfa6f3ccfc8230bc3178d23f84eeaf7e457f36f271ab1acc53015037c
Status: Downloaded newer image for alpine:latest
Server:         <IP_ADDRESS>
Address:        <IP_ADDRESS>:53

Non-authoritative answer:

Non-authoritative answer:
Name:   host.docker.internal
Address: <IP_ADDRESS>
Address: <IP_ADDRESS>

But it may be wrong for the ip of your host address. Please ping host.docker.internal and get the result as ws_url to retry.
I don't know why it is different result of docker container of nslookup and ping of wsl.  The ip <IP_ADDRESS> is not reached in my environment too.

@tomxiong
Yours is also not recorded, maybe there is a bug.
As described in the document, the mac's ip is generally <IP_ADDRESS>.

@tomxiong
Your error has nothing to do with live recording. Your error is because the website uses https. Therefore, an error occurs when you record. You can use Google Chrome to open the incognito window and re-request.

@frostbyte73
Can you guide me?

@nelsonkti your egress is not connecting to your livekit server (you will see a participant identity starting with EG_ in the server logs). How did you launch the livekit server? For the local egress instructions, it assumes your server is not using docker


Error Protocol Error Target Closed  with many type of reason

Steps to reproduce
it is an error occurs with probability, with the following script we can always see it
repro demo:
https://github.com/rawbin-/puppeteer-test/blob/master/protocol-error-target-closed-repo.js
node protocol-error-target-closed-repo.js
Tell us about your environment:

Puppeteer version: 2.0.0/2.1.1/3.0.0
Platform / OS version: CentOS/MacOS 10.15.3 (19D76)
URLs (if applicable):  https://github.com/rawbin-/puppeteer-test/blob/master/protocol-error-target-closed-repo.js
Node.js version: 12.14

What steps will reproduce the problem?
node protocol-error-target-closed-repo.js
Please include code that reproduces the issue.
https://github.com/rawbin-/puppeteer-test/blob/master/protocol-error-target-closed-repo.js
What is the expected result?
no Protocol error
What happens instead?
different exception occurs from time to time
Error: Protocol error (Emulation.setDeviceMetricsOverride): Target closed.
Error: Protocol error (Target.setAutoAttach): Target closed.
Error: Protocol error (Page.setLifecycleEventsEnabled): Target closed.
Error: Protocol error (Target.setAutoAttach): Target closed.
Error: Protocol error (Log.enable): Target closed.
Error: Protocol error (Performance.enable): Target closed.
Error: Protocol error (Page.enable): Target closed.
Error: Protocol error (Target.attachToTarget): No target with given id found
Error: Protocol error (Page.getFrameTree): Target closed.
Error: Protocol error (Emulation.setTouchEmulationEnabled): Target closed.
Protocol error (Emulation.setDeviceMetricsOverride): Session closed. Most likely the page has been closed.

more detail：
    try{
        openPages = await broswer.pages(); // here throws differents exceptions
    }catch (e) {
        // console.warn(broswer.isConnected(),broswer,broswer.target(),broswer.wsEndpoint())
        console.warn('get pages failed:',e)
        await broswer.close();
        process.exit(1)
        return
    }

i'm facing the same issue here.
i run a simple service and running a headless chromium to render a simple poster. i guess it caused by memory used up.
here's the error stack:
Error: Protocol error (Emulation.setDeviceMetricsOverride): Session closed. Most likely the page has been closed.
      at CDPSession.send (/node_modules/puppeteer/lib/Connection.js:180:29)
      at EmulationManager.emulateViewport (/node_modules/puppeteer/lib/EmulationManager.js:41:20)
      at Page.setViewport (/node_modules/puppeteer/lib/Page.js:763:54)
      at Page. (/node_modules/puppeteer/lib/helper.js:111:23)
      at handleTask (/poster-gen/src/generator.js:73:6)
      at Promise (/poster-gen/src/generator.js:105:7)
      at new Promise ()
      at htmlToImage (/poster-gen/src/generator.js:101:10)
      at Object.generate (/poster-gen/src/generator.js:195:28)
      at handler (/poster-gen/src/fission-poster.js:21:35)
    -- ASYNC --
      at Page. (/node_modules/puppeteer/lib/helper.js:110:27)
      at handleTask (/poster-gen/src/generator.js:73:6)
      at Promise (/poster-gen/src/generator.js:105:7)
      at new Promise ()
      at htmlToImage (/poster-gen/src/generator.js:101:10)
      at Object.generate (/poster-gen/src/generator.js:195:28)
      at handler (/poster-gen/src/fission-poster.js:21:35)
      at process._tickCallback (internal/process/next_tick.js:68:7)

Any updates on this? We're experiencing the same issue ⬆

Any updates on this issue? We are experiencing the same error a few times for one crawling.

Same issue here, ran into it Today- Jun 28th. Any updates?

Same issue here, any updates?

How can I fix this? Puppetter keeps crashing when I call it from inside a loop. Each call makes:
 const browser = await puppeteer.launch({
      headless: true,
      args: ['--no-sandbox', '--disable-setuid-sandbox', '--use-gl=egl'],
    })```

I was not able to repro in the latest version. It is possible that the page gets closed/shut down by the browser for whatever reason, in that case you can get those errors. Please re-open with a recent repro if it's still an issue.

Try to turn off headless mode to see if the page closed or crashed accidentally.


Using exact-match search returns an empty matches

Describe the bug
When use exact match ('keyword), the filtering is correct, however matches is an empty array.
Version
5.1.0
Is this a regression?
No. 3.6.2 doesn't have this feature.
🔬Minimal Reproduction
https://runkit.com/embed/5fp4feoxcwz2
const Fuse = require("fuse.js");
const objects = [{ title: 'Authors of "Fuse Proof of Concept"' }];

const fuse = new Fuse(objects, {
  includeMatches: true,
  useExtendedSearch: true,
  keys: ["title"],
});

console.log(fuse.search("'fuse"));
// → [{item: {title: "Authors of \"Fuse Proof of Concept\""}, matches: [], refIndex: 0}]

console.log(fuse.search("fuse"));
// → [{"item":{"title":"Authors of \"Fuse Proof of Concept\""},"refIndex":0,"matches":[{"indices":[[1,1],[6,6],[9,9],[12,15]],"value":"Authors of \"Fuse Proof of Concept\"","key":"title"}]}]

Fixed in v5.2.0-apha.*.


Best way to print out the attention weights

Hi,
should I use tensor board? Is there a flag I'm missing?
Thanks, Tal

@talbaumel Look at the instructions under "Visualize your output" in the README here; leads to this visualizer tool.

Thank you 👍


SPXCrossover doesn't work with number of variables > 1

Hi. I did several tests with different numbers of variables and the following always happens:
For example, number of variables = 3 (and number of bits = 8)
Parent 0
[True, True, True, False, False, True, False, False]
[False, True, False, True, False, False, False, True]
[False, False, True, False, True, True, True, False]
Parent 1
[True, False, True, True, True, False, False, False]
[False, True, True, True, True, True, True, False]
[False, True, False, True, False, True, True, False]
Offspring 0
[True, True, True, True, True, False, False, False]
[False, True, True, True, True, True, True, False]
[False, True, False, True, False, True, True, False]
Offspring 1
[True, False, True, False, False, True, False, False]
[False, True, False, True, False, False, False, True]
[False, False, True, False, True, True, True, False]
Values in bold: Parent 0 and Parent 1 contribute in the first variable of Offspring 0 (Same idea for Offspring 1)
Values in italics: Then the other variables of Parent 0 go to Offspring 1 without any changes.
I would expect that the same logic for creating the first variable applies to others. Is this correct or am I wrong?

Hi.
The SPXCrossover assumes that all the variables lead to a single bit string (i.e., the bit strings of all the variables are concatenated). Taking this into account, the example you include seems to work as expected.

Hi.
The SPXCrossover assumes that all the variables lead to a single bit string (i.e., the bit strings of all the variables are concatenated). Taking this into account, the example you include seems to work as expected.

Thank you for the quick answer, now it's very clear to me. Thank you very much again and great project!


css location support absolute and fixed

Hello,
I see there is currently a class called "position-absolute" but there are no classes like: "top: 0", "left: 0", "right: 0" ... I think there should be support classes Support for "position-absolute" and "position-fixed"
For example:
.top-0
.top-25
.top-50
The same goes for bottom, left, and right
Thanks

I could see us adding those 0 values as classes (e.g., .top-0), but I don't see us adding any other values. Rest of the suggested ones here feel too random.

This looks something like Tailwind utility classes. Having support for common values like top-auto would also be good along with that.

Added in #31280


fix: not updating when window scrolled

The rendering is not updated when the window is scrolled while the cursor is fixed (can be reproduces using <C-y>, <C-e>, zz, zt, zb to scroll the window). This leaves new elements that becomes visible in current window undecorated.
To fix this simply add 'WinScrolled' event to the updating events.

Thank you!


:recycle:x.x.x: Refactor queryKeys

Codecov Report

Merging #1405 (079cc54) into main (dc346f2) will not change coverage.
The diff coverage is 100.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff            @@
##              main     #1405   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           11        12    +1
  Lines           51        47    -4
  Branches         1         1
=========================================
- Hits            51        47    -4

Impacted Files
Coverage Δ

src/ui/domain/item/Items/Items.tsx
100.00% <100.00%> (ø)

src/ui/domain/item/Items/hook/items.hook.ts
100.00% <100.00%> (ø)

src/ui/domain/item/detail/ItemView/ItemView.tsx
100.00% <100.00%> (ø)

.../domain/item/detail/ItemView/hook/itemView.hook.ts
100.00% <100.00%> (ø)

...domain/item/detail/common/hook/fetch/fetch.hook.ts
100.00% <100.00%> (ø)

src/ui/general/Button/Button.tsx
100.00% <100.00%> (ø)

src/ui/general/form/Input/Input.tsx
100.00% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


I am interested in using your game on my website. Could you add a license file like the MIT one in this pull request so I know how you want your software used?

Oh! Sorry for late replying. Glad to see you like it. I need to query the author :)
@AlephAlpha what license do you want for your Mathematica2048?

@SnowOnion WTFPL

@jpbida WTFPL :)

Haha, that is the first time I've seen that license. Even has a wikipedia
page. Thanks!
On Thu, Feb 16, 2017 at 6:26 PM, SnowOnion<EMAIL_ADDRESS>wrote:

@jpbida https://github.com/jpbida WTFPL :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/SnowOnion/Mathematica2048/pull/1#issuecomment-280530915,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGrFLPXmZJEX-jnyWrQ3Aci7cka81Z4ks5rdQVQgaJpZM4L3bqL
.


Update to 1.21

Hey, thank you for using the Ping Wheel-Plugin!
I've tested the plugin with @LukenSkyne and everything seems to be working as intended in every version between 1.18.2 and 1.21!
Can you please further describe your issue?

Hey, I'm sorry, I just realized I made a mistake on my own.


I need "required" validation message for each child-field of Object-field

@Collection = Collection = new Meteor.Collection("test")
Collection.attachSchema new SimpleSchema
  object1:
    type: Object
  "object1.field":
    type: String
    min: 3
if (Meteor.isServer)
  Collection.remove({})
  Collection.insert
    object1: field: "test"
if (Meteor.isClient)
  Template.form.helpers
    "data": ->
      Collection.findOne()

template(name="form")
  //- if delete value from field and submit:
  //- 1) I see validation message: "Object1 is required" (but not "field is required")
  //- +quickForm collection="Collection" type="update" doc=data
  //- 2) if to use autoForm then I dont see any messages (but min-validation works fine)
  +autoForm collection="Collection" type="update" doc=data
    +afQuickField name="object1.field"
    button(type="submit") Submit

Tried to reproduce this using current devel branch and I can't. Everything seems to work fine.


ability to delete custom event and/or visits

add a button above the table to delete visits that reference the event

add a button to the header to delete the event + visits that reference it


Modify serverless.yml to be Lambda only, not Lambda@Edge

Just wondering if there is an easy quick configuration change somewhere to modify the plugin to push to a Lambda instead of Lambda@Edge? My site doesn't need to be used outside of the region I'm in.

@michaelcuneo it's not clear what you'd hope to achieve what that? This plugin is specifically for supporting CloudFront's integration with Lambda@Edge. If you need to do something else, then you probably just need to use Serverless Framework (or other, CDK, etc) features, and don't need this plugin.


Document kubectl syntax/usage conventions

I'm thinking of something like api-conventions.md, but for kubectl. It should at least cover the general command patterns, common arguments, and typical output.
Example topics to cover:

Ways in which objects can be specified
Commands are lowercase, w/ dashes for multiple words
Resource kinds are all lowercase rather than camelcase, no hyphens
The difference between get and describe

If not too long, the overall kubectl.md could be a reasonable place to put the text.
cc @smarterclayton @jlowdermilk @ghodss

Another thing that we had discussed:

Explicitly specify the api-version flag when using -o template, so that the command does not break when the default api version used by kubectl is updated.

+1. In theory it could be expanded to cli-conventions.md, though I think kubectl operates quite differently than most of our other daemons. But it still may be wise for it to cover other command-line tools besides kubectl, like simplegen, podex, etc.

VERB and VERB NOUN, not NOUN VERB. We may need to reconsider kubectl config.

That being said, if you have sets of functionality that are distinct, sometimes it's nice to keep them separate (treat kubectl config like kubectl-config).

On May 13, 2015, at 7:43 PM, Brian Grant<EMAIL_ADDRESS>wrote:
VERB and VERB NOUN, not NOUN VERB. We may need to reconsider kubectl config.
—
Reply to this email directly or view it on GitHub.

 Human output formats may change.

Errors output to stderr rather than (or in addition to) glog: #9357

cc @JanetKuo

More output conventions:

the ability to specify labels as columns using -L #9876
AGE of every object #10008
-o wide for wide get output #10491
human-understandable output from mutations (create/update/delete) by default: resource/name verbed #5906
-o name for mutations to output just resource/name #5906

We also want conventions for:

Showing what a mutation would do, without doing it, aka --dry-run
Showing what a mutation did, by automatically getting the current object
Printing or describing (#4471) a local object rather than one fetched from the server

All of these should be orthogonal to output format (default, wide, json, yaml, template).


MonteCarloMultiGPU SYCL Migration

Description
MonteCarloMultiGPU Application Migration from CUDA to SYCL
Checklist
Administrative

[X] Review sample design with the appropriate Domain Expert: <Choudary, Chekuri; Krishnappa, Rakshith>
[ ] If you have any new dependencies/binaries, inform the oneAPI Code Samples Project Manager

Code Development

[X] Implement coding guidelines and ensure code quality. see wiki for details
[X] Adhere to readme template
[X] Enforce format via clang-format config file
[X] Adhere to sample.json specification. https://github.com/oneapi-src/oneAPI-samples/wiki/sample-json-specification
[X] Ensure/create CI test configurations for sample (ciTests field) https://github.com/oneapi-src/oneAPI-samples/wiki/sample-json-ci-test-object
[X] Run jsonlint on sample.json to verify json syntax. www.jsonlint.com

Security and Legal

[ ] OSPDT Approval (see Project Manager for assistance)
[X] Compile using the following compiler flags and fix any warnings, the falgs are: "/Wall -Wformat-security -Werror=format-security"
[ ] Bandit Scans (Python only)
[ ] Virus scan

Review

[X] Review DPC++ code with Paul Peterseon. (GitHub User: pmpeter1)
[X] Review readme with Tom Lenth(@tomlenth) and/or Project Manager
[X] Tested using Dev Cloud when applicable

@ishaghosh27 @jkinsky Can one of you review the README?

@ManjulaChalla there is a .ipynk_checkpoint folder which has to be removed, also check of any others: 01_sycl_dpct_output/Common/.ipynb_checkpoints/helper_cuda-checkpoint.h

@ManjulaChalla there is a .ipynk_checkpoint folder which has to be removed, also check of any others: 01_sycl_dpct_output/Common/.ipynb_checkpoints/helper_cuda-checkpoint.h

Removed .ipynb_checkpoints folder.


DRAFT: Skip sriovnetworknodestate updates when a mellanox device is present

mstconfig in the current form returns an error when running in kernel lockdown mode.
Until it's fixed, we must skip on mellanox nic when lockdown mode is on.
An error in the sriov node policy will be reported if the user creates a policy using a mellanox device

/cc @adrianchiris @moshe010

@adrianchiris @moshe010 @Mmduh-483  could you take a look at the Mellanox plugin change?
We will need this workaround until kernel or driver part can handle it nicely.

@zshi-redhat can you please review / approve this ?

With current patch, I think it will still fail when calling generic plugin Apply, is that the case in your testing? Because we only skip the processing in mellanox plugin, not in generic plugin. For example, if the required numVfs > configured numVfs, then it would fail to configure numVfs.

Do you mean something like this:
PR96
this would make the generic plugin fail whenever we have mellanox devices in spec an lockdown mode is on.

With current patch, I think it will still fail when calling generic plugin Apply, is that the case in your testing? Because we only skip the processing in mellanox plugin, not in generic plugin. For example, if the required numVfs > configured numVfs, then it would fail to configure numVfs.

Do you mean something like this:
PR96
this would make the generic plugin fail whenever we have mellanox devices in spec an lockdown mode is on.

Yes, this PR checks kernel lockdown mode in the mellanox plugin, not in generic_plugin. but generic_plugin will always be called, isn't it?

With current patch, I think it will still fail when calling generic plugin Apply, is that the case in your testing? Because we only skip the processing in mellanox plugin, not in generic plugin. For example, if the required numVfs > configured numVfs, then it would fail to configure numVfs.

Do you mean something like this:
PR96
this would make the generic plugin fail whenever we have mellanox devices in spec an lockdown mode is on.

Yes, this PR checks kernel lockdown mode in the mellanox plugin, not in generic_plugin. but generic_plugin will always be called, isn't it?

Yes, let me restore this piece of code to this patch. The code was removed due to earlier comments.

/lgtm

looks good, validated these policies on a node with secure boot enabled:
mlx only
----------
spec:
  dpConfigVersion: "4128765"
  interfaces:
  - linkType: eth
    name: eno1
    numVfs: 5
    pciAddress: "0000:19:00.0"
    vfGroups:
    - deviceType: netdevice
      policyName: test-mlxpolicy
      resourceName: mlxnic
      vfRange: 0-4
  lastSyncError: Mellanox device detected when in lockdown mode
  syncStatus: Failed

mlx + intel
----------------
 spec:
  dpConfigVersion: "4155515"
  interfaces:
  - linkType: eth
    name: ens2f0
    numVfs: 5
    pciAddress: 0000:5e:00.0
    vfGroups:
    - deviceType: netdevice
      policyName: test-intelnetpolicy
      resourceName: intelnetnic
      vfRange: 0-4
  - linkType: eth
    name: eno1
    numVfs: 5
    pciAddress: "0000:19:00.0"
    vfGroups:
    - deviceType: netdevice
      policyName: test-mlxpolicy
      resourceName: mlxnic
      vfRange: 0-4
  lastSyncError: Mellanox device detected when in lockdown mode
  syncStatus: InProgress

intel netdevice
--------------------
spec:
  dpConfigVersion: "4309505"
  interfaces:
  - linkType: eth
    name: ens2f0
    numVfs: 5
    pciAddress: 0000:5e:00.0
    vfGroups:
    - deviceType: netdevice
      policyName: test-intelnetpolicy
      resourceName: intelnetnic
      vfRange: 0-4
  - Vfs:
    - deviceID: 154c
      driver: iavf
      mac: b6:36:4d:f1:b2:5e
      mtu: 1500
      name: ens2f0v0
      pciAddress: 0000:5e:02.0
      vendor: "8086"
      vfID: 0
    - deviceID: 154c
      driver: iavf
      mac: 22:d7:d9:cd:ba:6a
      mtu: 1500
      name: ens2f0v1
      pciAddress: 0000:5e:02.1
      vendor: "8086"
      vfID: 1
    - deviceID: 154c
      driver: iavf
      mac: ca:d9:bf:d3:a5:a1
      mtu: 1500
      name: ens2f0v2
      pciAddress: 0000:5e:02.2
      vendor: "8086"
      vfID: 2
    - deviceID: 154c
      driver: iavf
      mac: 6a:5f:9e:3b:3e:5a
      mtu: 1500
      name: ens2f0v3
      pciAddress: 0000:5e:02.3
      vendor: "8086"
      vfID: 3
    - deviceID: 154c
      driver: iavf
      mac: 46:c0:e2:64:0a:f5
      mtu: 1500
      name: ens2f0v4
      pciAddress: 0000:5e:02.4
      vendor: "8086"
      vfID: 4
  syncStatus: Succeeded

intel vfio-pci
-----------------
spec:
  dpConfigVersion: "4313016"
  interfaces:
  - linkType: eth
    name: ens2f1
    numVfs: 5
    pciAddress: 0000:5e:00.1
    vfGroups:
    - deviceType: vfio-pci
      policyName: test-intelvfiopolicy
      resourceName: intelvfionic
      vfRange: 0-4
  - Vfs:
    - deviceID: 154c
      driver: vfio-pci
      pciAddress: 0000:5e:0a.0
      vendor: "8086"
      vfID: 0
    - deviceID: 154c
      driver: vfio-pci
      pciAddress: 0000:5e:0a.1
      vendor: "8086"
      vfID: 1
    - deviceID: 154c
      driver: vfio-pci
      pciAddress: 0000:5e:0a.2
      vendor: "8086"
      vfID: 2
    - deviceID: 154c
      driver: vfio-pci
      pciAddress: 0000:5e:0a.3
      vendor: "8086"
      vfID: 3
    - deviceID: 154c
      driver: vfio-pci
      pciAddress: 0000:5e:0a.4
      vendor: "8086"
      vfID: 4
  syncStatus: Succeeded

intel netdevice + vfio-pci
----------------------------------
spec:
  dpConfigVersion: "4323736"
  interfaces:
  - linkType: eth
    name: ens2f0
    numVfs: 5
    pciAddress: 0000:5e:00.0
    vfGroups:
    - deviceType: netdevice
      policyName: test-intelnetpolicy
      resourceName: intelnetnic
      vfRange: 0-4
  - linkType: eth
    name: ens2f1
    numVfs: 5
    pciAddress: 0000:5e:00.1
    vfGroups:
    - deviceType: vfio-pci
      policyName: test-intelvfiopolicy
      resourceName: intelvfionic
      vfRange: 0-4
  - Vfs:
    - deviceID: 154c
      driver: iavf
      mac: 4a:2c:01:9b:2a:5a
      mtu: 1500
      name: ens2f0v0
      pciAddress: 0000:5e:02.0
      vendor: "8086"
      vfID: 0
    - deviceID: 154c
      driver: iavf
      pciAddress: 0000:5e:02.1
      vendor: "8086"
      vfID: 1
    - deviceID: 154c
      driver: iavf
      mac: b6:25:0c:f3:48:da
      mtu: 1500
      name: ens2f0v2
      pciAddress: 0000:5e:02.2
      vendor: "8086"
      vfID: 2
    - deviceID: 154c
      driver: iavf
      mac: 3e:fd:5b:5b:7a:37
      mtu: 1500
      name: ens2f0v3
      pciAddress: 0000:5e:02.3
      vendor: "8086"
      vfID: 3
    - deviceID: 154c
      driver: iavf
      mac: 82:9e:bc:56:5b:bf
      mtu: 1500
      name: ens2f0v4
      pciAddress: 0000:5e:02.4
      vendor: "8086"
      vfID: 4
  - Vfs:
    - deviceID: 154c
      driver: vfio-pci
      pciAddress: 0000:5e:0a.0
      vendor: "8086"
      vfID: 0
    - deviceID: 154c
      driver: vfio-pci
      pciAddress: 0000:5e:0a.1
      vendor: "8086"
      vfID: 1
    - deviceID: 154c
      driver: vfio-pci
      pciAddress: 0000:5e:0a.2
      vendor: "8086"
      vfID: 2
    - deviceID: 154c
      driver: vfio-pci
      pciAddress: 0000:5e:0a.3
      vendor: "8086"
      vfID: 3
    - deviceID: 154c
      driver: vfio-pci
      pciAddress: 0000:5e:0a.4
      vendor: "8086"
      vfID: 4
  syncStatus: Succeeded

If the only limitation is mstconfig,
I think that theoretically we could support Mellanox NICs if mellanox plugin would result in a no-op on the NodeState Spec.
which basically means getting OnNodeStateChange to not rely on mstconfig
and Apply() to fail on kernel lockdown only if it has parameter that need changing.
This would allow sriov-network-operator to work with Mellanox NICs that have pre-configured firmware configurations as long as they dont conflict with NodeState.Spec.
this would imply the following changes:

Do not configure FW SR-IOV parameters if the configured MAX VFs is greater than requested in NodeState.spec
derive link type from the PF netdev and not Firmware config
derive max VF using /sys/class/net/<netdev>/device/sriov_totalvfs
only fail in Apply() if we ended up with firmware attributes that require change

downside would be a reduced UX in kernel lockdown.
That said I agree the most straightforward change would be to have mstconfig work in this mode.

we also use mstconfig in OnNodeStateChange, so it's invoked every time we hava a mlx in spec

we also use mstconfig in OnNodeStateChange, so it's invoked every time we hava a mlx in spec

@mmirecki i did not understand your comment, can you elaborate ?

@mmirecki do we have a bz link to the fix of mstflint? could we add it in the commit message?

@mmirecki do we have a bz link to the fix of mstflint? could we add it in the commit message?

https://bugzilla.redhat.com/show_bug.cgi?id=1939421
Adding to commit message

/lgtm

/lgtm


Cannot read property 'animatedLayers' of undefined on Chrome

Hello,
I am using sliderPro v1.2.2.
sliderPro initialization:
$('#gallery-slider').sliderPro({
arrows: true,
width: '100%',
height: '350',
autoplay: true,
autoplayDelay: 4000
});
This is the only occurrence of sliderPro usage in my project files.
It's causing the following error on chrome:
"Cannot read property 'animatedLayers' of undefined."
On firefox this is working fine.
Could you please help me? :)

Hi. That error is usually thrown when there are no slides inside the slider. If you're generating the content dynamically, check out the generated HTML and make sure that it's correct.
Cheers

Hi. Please try to call the slider's update method after you add the new images. You could also try to destroy the slider and reinstantiate it with the new images.
Best,
David


Non-degree credits breakdown

Rapo has the following categories

[x] other column for exhange students and some else
Jaottelu tehty Kurhilan kommentin perusteella:
2-5 non-degree
loput other non-degree
[x] possibilty for csv
[x] Bring studyright associated to credit into oodikone #4298
[ ] RAPO check

What should be shown in oodikone?

To be able to identify different non-degree studies (separate studies, open uni studies, specialisation studies etc) we need to save all study rights to sis-db and figure out how broken Oodikone is after that change.
All education types:
https://sis-helsinki-test.funidata.fi/kori/api/cached/codebooks/urn:code:education-type

When diffing, focus only on years starting from 2022
Separate non-degree into two based on some logic. Important is that vaihto-opiskelijat is in another column. Perhaps:lines 2,3,4,5 (from the rapo table above) in one, rest in another.

uudempi taulukko:


Release a standalone package

The current package in opam needs both js_of_ocaml and hardcaml (for the webdemo, I suppose). Apparently, the master version with dune needs neither of those. Would it be possible to release a new leaner opam package ?

That seems reasonable.  I'll take a look in a couple of days.
On Sun, 4 Nov 2018, 12:40 Gabriel Radanne<EMAIL_ADDRESS>wrote:

The current package in opam needs both js_of_ocaml and hardcaml (for the
webdemo, I suppose). Apparently, the master version with dune needs neither
of those. Would it be possible to release a new leaner opam package ?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ujamjar/reedsolomon/issues/2, or mute the thread
https://github.com/notifications/unsubscribe-auth/AFqzI12vb4HiNBkdD12UR7cXXEZiyLb9ks5uruBagaJpZM4YNR4I
.

ocaml/opam-repository#12953


Update system testing for API server 1.6.4 (fixes #97)

This means we have to add RBAC for the anonymous user.  For a more
detailed explanation see
https://github.com/projectcalico/felix/commit/6e9f6d8e8a6b8ded7dec0dccba502bdd9891f06f.

Also fix mistaken use of a hardcoded IP address for the API
server (even though we also had the correct, dynamically determined IP
address to hand).

This should fix https://github.com/projectcalico/k8s-policy/issues/97

Indeed, and my local testing has just completely successfully.  (Oh, and Semaphore now too.)  @caseydavenport please could you review?


Update how-to-use document to provide information on conda env setup

This PR partially addressed #127; it updates the how-to-use document to address conda environment setup.

Thanks @clyne, I had a PR in the works for this (addressing #198) but you beat me to it.
This looks great except that the name of the environment is incorrect. You need to do
conda activate pythia-book-dev

not pythia-foundations.
Unless we are changing the name of our conda environment! Which might be a good idea.

Whoops. Good catch. Thanks. Fixed!

Hmm there are still several references to "activate pythia-foundations" in the text.
Should probably change to "activate pythia-book-dev"

Hmm there are still several references to "activate pythia-foundations" in the text.
Should probably change to "activate pythia-book-dev"

Indeed. Apparently the search function inside GitHub "file edit" doesn't work as I expected. I'm reasonably confident I've gotten them all now :-)

The "How to use this" book section is the first thing students will see when visiting the Pythia Foundations site. It assumes that they are novices and know nothing about Python environments, conda, etc. I'm afraid that telling a novice that they can figure out dependencies by inspection won't be very helpful if they don't know how to resolve the dependencies. Also, this setup method isn't foolproof; there can be issues with software versioning. Thoughts?

All true! I'm not suggesting that we provide detailed support for this "roll your own" approach. There is no need because we are already offering an easy option for beginners that "just works" (using our environment.yml file).
My comment is more meant for the adventurous type who wants to understand a little bit about how environments work, and their relationship with python code. Particularly if they are trying to adapt one of notebooks for their own application using just a few packages.
For example, I can imagine myself as a newcomer to python first following the instructions to create the all-inclusive environment, seeing that it works, but also seeing that it installed a very long list of stuff and wondering how much of that is really necessary.
Anyway I don't have strong feelings about it and not insisting on it. The adventurous type will usually figure these things out on their own.


Rendering scripts

Thank you for your excellent open-source work!
I noticed that 3D rendering script is listed as TODO. I am wondering if there are any plans to release this part of the code soon?😊

Hi, thank you for your interest in the project! Indeed this script was planned for a later release.
Do you have an idea of a possible timeline @rdecharette?


Install golangci-lint if needed

Signed-off-by: Kim Bao Long<EMAIL_ADDRESS>

@longkb the contribution is appreciated but we only accept patches here that we need to make containerd works as an embedded part of k3s. Consider submitting this upstream at https://github.com/containerd/containerd

@longkb the contribution is appreciated but we only accept patches here that we need to make containerd works as an embedded part of k3s. Consider submitting this upstream at https://github.com/containerd/containerd


api/resource.proto: inconsistency between comments and definition

There are some examples inside the proto itself (resource.proto) which adds some references to a non-existent name_descriptor field.
Furthermore, the AIP establishes the use of a type & pattern properties to define the metadata associated to a specific resource. The comments make a plan to use those in a different way by wrapping it on a custom property (name_descriptor) and make it repeatable.
Is it possible to clarify this? Thanks!
@noahdietz @lukesneeringer as you were the ones involved in the MR.

Yes, we have a name_descriptor field internally whose fate is currently not clear. I need to work on this. Thanks for pointing it out!

@lukesneeringer one interesting benefit from the "new way" is that it's fairly easy to do automatic validation of all the resource name references over the entities/request.
That is to say, take this as an example:
message House {
 ...
}

message User {
    option (google.api.resource) = {
        type: "mycompanty.com/User"
        name_descriptor: {
            pattern: "houses/{house}/users/{user}"
            parent_type: "mycompanty.com/Home"
            parent_name_extractor: "houses/{house}"
        }
    }
    string name = 1 [(google.api.resource_reference) = {
        type: "mycompany.com/User"
    }];
    string parent = 2; [(google.api.resource_reference) = {
        type: "mycompany.com/User"
    }];
}

If I wanted to create an automatic generator for validating that all the resource references in a message belong to the same house (tenant) It's easy to extract the parent from the name value (as we already definied a parent extractor) and then do a cross comparison between all resource_references. Easy peasy.
This kind of things is what the new way allows to do.
Just putting my 2 cents.

We too are hand-rolling a fair amount of code that we could generate given the additional metadata from the name_descriptor. @lukesneeringer Could you share some context on why the fate is unclear? Is there a better approach using the current metadata that can be documented?

I think the parent type annotation would also be very useful when generating standard gRPC methods, requests and responses for a resource.
@lukesneeringer Poke :smile_cat:

Hi @lukesneeringer, did you have a better idea if that fate was worth it or not during these years? Thanks!

Thanks for the update @hkdevandla!

I'm going to close this issue as we're tracking the feature request internally in b/165605440. Please feel free to re-open this issue.

@parthea did you resolved that internal feature request somehow? Curious if this is still a need or not on your side, it's on ours :D