text:
ci: update what version of emsdk is used to compile

fix #23
You may want to migrate to https://hub.docker.com/r/emscripten/emsdk but I thought it best not to make such a large change to resolve this issue.

You can't just set version to "latest". One day there will be a breaking change in emscripten, and this will just break highsjs. You have to set it to a version you tested and you know works.

Doesn't the next few lines test that the build was successfully and works as expected?
If there's a major update to emsdk that break highs, those tests should prevent a broken build from being released and report the issue. When that happens, it will just require another small update to the build process to either pin to an older version of emsdk or to make the necessary updates.
This allows future releases of highs to use the latest features and bugfixes of emsdk as they become available without any developer overhead.
Pinning to a specific version all the time doesn't seem ideal...

Yes, the problem is less with releasing a broken build (which could still happen), and more with requiring more maintenance work. We want to be able to update emscripten and highs independently.

Should be sorted now

adding ln -s /emsdk/upstream/emscripten /usr/share/emscripten should be enough to let cmake find emscripten

authors: RebeccaStevens lovasoa

repo: lovasoa/highs-js


text:
Create a PNG, the height cannot > 200000

Are you using the latest version? Is the version currently in use as reported by npm ls sharp the same as the latest version as reported by npm view sharp dist-tags.latest?
0.26.3
What are the steps to reproduce?
const LIMIT_INPUT_PIXELS = 177610406400

sharp({
            limitInputPixels: LIMIT_INPUT_PIXELS,
            create: {
              width: 2250,
              height: 201000, // cannot > 200000
              channels: 3,
              background: { r: 255, g: 255, b: 255 }
            }
          })
            .toFile(`./tmp.png`, function(err) {
    console.log(err)
  })

No error report but image is corrupted/unused.
What is the expected behaviour?
Creat image success
Are you able to provide a minimal, standalone code sample, without other dependencies, that demonstrates this problem?
Are you able to provide a sample image that helps explain the problem?
What is the output of running npx envinfo --binaries --system?

Hi, this example works for me locally on Linux, albeit rather slowly. When dealing with such large PNG files you might want to lower the compressionLevel setting.
https://sharp.pixelplumbing.com/api-output#png
My best guess would be that you're running out of memory. The example image is 2250 x 201000 x 3 bytes, around 1.4GB, when held uncompressed in RAM.

Hi, this example works for me locally on Linux, albeit rather slowly. When dealing with such large PNG files you might want to lower the compressionLevel setting.
https://sharp.pixelplumbing.com/api-output#png
My best guess would be that you're running out of memory. The example image is 2250 x 201000 x 3 bytes, around 1.4GB, when held uncompressed in RAM.

@lovell My system is MacOS Big Sur 11.1 with 16GB RAM. I guess other limitation in unknown place.
I'm building a tool for webpage screenshot, some pages are really height.

@lovell My system is MacOS Big Sur 11.1 with 16GB RAM. I guess other limitation in unknown place.
I'm building a tool for webpage screenshot, some pages are really height.

@mclxly Were you able to make any progress with this? The prebuilt binaries provided in the next release of sharp should offer faster PNG output - see https://github.com/lovell/sharp/issues/2604

v0.28.1 is now available with improved PNG compression performance. Are you able to test to see if it has helped?

@lovell no lucky, same error.
await sharp({
                  limitInputPixels: LIMIT_INPUT_PIXELS,
                  create: {
                    width: 1000,
                    height: 200000,
                    channels: 3,
                    background: { r: 255, g: 1, b: 255 }
                  }
                })
                  .toFile(`./job_tmp.png`)
// no problem here

                    height: 200100,
// can't open it

When you say "can't open it", what tool(s) are you using? Here's the output from the above code when I run it locally, which displays correctly in Chrome and Firefox:
https://user-images.githubusercontent.com/210965/113830428-83edb800-977e-11eb-95fb-4a0614365c56.png

Sorry, you are right, it can be opened by Chrome.
It can't open with default preview tool on macOS Big Sur.

source: gharchive/issue

authors: lovell mclxly

repo: lovell/sharp

license_type: permissive

license_source: github-api


text:
[rtl/dv] Fixes for Cadence Xcelium 20.09.001 compile and run. Regress…

…ion has been run with these changes and (REGRESSION SUMMARY: 428 PASSED, 0 PASSED/FAILED, 2 FAILED)
Compile error 1: Fixed the following rtl compile error in ibex_cs_registers.sv
assign tselect_rdata = {'b0, tselect_q};
                          |

xmvlog: *E,NONOWD (/proj/riscv_ibex/users/paulok/lowRISC/ibex_1/rtl/ibex_cs_registers.sv,1288|30): Illegal use of a constant without an explicit width specification [4.1.14(IEEE)].
Compile error 2: Fixed the following DV compile error in ibex_mem_intf.sv
.data_req_o     (data_mem_vif.request ),
|
xmelab: *E,ICDCBA (./tb/core_ibex_tb_top.sv,89|14): Illegal combination of driver and output clockvar to variable 'request' detected (output clockvar found in clocking block at line 25 in file ./common/ibex_mem_intf_agent/ibex_mem_intf.sv).
Simulation probes: Fixed issue with probing in yaml for xrun and added licqueue.
Signed-off-by: Paul OKeeffe paul_okeeffe@crevinn.com

Any tips on how to re-create this problem? it seems to be coming from fusesoc.
Thanks
Paul

Wasnt exactly sure how to modify an existing pull request, so I submitted it as a new one.
Closing this now.

For next time, you can just force-push to the same branch. If you had https://github.com/PaulOKCrevinn/ibex as a remote called origin, it would just be git push -f origin HEAD:b_cadence_xcelium_20_09_001_compile_fixes. Assuming that you're on a local branch called b_cadence_xcelium_20_09_001_compile_fixes and your fork of Ibex is the default push remote, you can probably just run git push -f.

Thanks, I've noted this, I am a familiar with git but not a power user so still learning...

source: gharchive/pull-request

authors: PaulOKCrevinn rswarbrick

repo: lowRISC/ibex

license_source: bigquery


text:
NameError: name 'utils' is not defined

After updating (having not built the bistream in many weeks) I am back at the point where the bitstream builds (at commit b60aaa5f9a93c3e517b27446df1efe56902d62ee):
INFO: SUCCESS! FPGA xc7a200tsbg484-1 successfully programmed with bitstream lowrisc_systems_top_earlgrey_nexysvideo_0.1.bit.

but I can't seem to download the bitstream anymore:
$ fusesoc --cores-root . pgm lowrisc:systems:top_earlgrey_nexysvideo:0.1
WARNING: Unknown item formal in section Target
WARNING: Unknown item formal in section Target
Traceback (most recent call last):
  File "/usr/local/google/home/satnam/.local/bin/fusesoc", line 10, in <module>
    sys.exit(main())
  File "/usr/local/google/home/satnam/.local/lib/python3.7/site-packages/fusesoc/main.py", line 908, in main
    args.func(cm, args)
  File "/usr/local/google/home/satnam/.local/lib/python3.7/site-packages/fusesoc/main.py", line 109, in pgm
    None,
  File "/usr/local/google/home/satnam/.local/lib/python3.7/site-packages/fusesoc/main.py", line 490, in run_backend
    edam = utils.yaml_fread(eda_api_file)
NameError: name 'utils' is not defined

I went through all the documentation I could find to see if there was a tool I had not upgraded but can't immediately see what is going wrong here.
Has anyone else experienced this or got a suggestion for what I should investigate?
Many thanks.

That's indeed a bug in the latest version of fusesoc. You can work around it right now by changing /usr/local/google/home/satnam/.local/lib/python3.7/site-packages/fusesoc/main.py:490 to read fusesoc.utils.yaml_fread instead of utils.yaml_fread. I'll follow up with a patch tomorrow.

Well that worked (after also adding the import for fusesoc!
Version:    opentitan-snapshot-20191101-1-875-gb60aaa5f
Build Date: 2020-04-01, 14:51:04
Bootstrap requested, initialising HW...
                                       HW initialisation completed, waiting for SPI input...

Thank you very much for your quick response.

This is now fixed in fusesoc. Thanks for your bug report!

repo: lowRISC/opentitan


text:
[chip-test,si-val] chip_sw_sysrst_ctrl_combo_reset

Test point name
chip_sw_sysrst_ctrl_combo_reset
Host side component
None
OpenTitanTool infrastructure implemented
None
Silicon Validation (SiVal)
None
Emulation Targets

[ ] None
[ ] CW310
[ ] Hyperdebug + CW310

Contact person
@rswarbrick
Checklist
Please fill out this checklist as items are completed. Link to PRs and issues as appropriate.

[ ] Check if existing test covers most or all of this testpoint (if so, either extend said test to cover all points, or skip the next 3 checkboxes)
[ ] Device-side (C) component developed
[ ] Bazel build rules developed
[ ] Host-side component developed
[ ] HJSON test plan updated with test name (so it shows up in the dashboard)
[ ] Test added to dvsim nightly regression (and passing at time of checking)
[ ] For SiVal test cases, test is running relevant FPGA or silicon regression

Duplicate of #19858 ?

authors: pamaury rswarbrick


text:
[reggen] Adding index to register when there's only a single register

Currently in reggen where you have a multireg where the count isn't large enough that it needs to generate multiple registers it doesn't add an index to the register name when generating them. This causes an issue when trying to write something that uses the generated register definitions that is intended to work for any count.
As a concrete example in the padctrl DIF (currently in a PR so link is to my fork) PADCTRL_DIO_PADS0_REG_OFFSET is used and this becomes PADCTRL_DIO_PADS_REG_OFFSET depending upon the number of DIO pads:
https://github.com/GregAC/opentitan/blob/1b9ce558ddb0c440950525a890b1917773923576/sw/device/lib/dif/dif_padctrl.c#L64-L70
Fixing this in the C is a bit messy as it would require some #ifdef to determine if PADCTRL_DIO_PADS0_REG_OFFSET or PADCTRL_DIO_PADS_REG_OFFSET should be used.
Fixing this in reggen is easy enough, but disruptive, the python that does this is here:
https://github.com/lowRISC/opentitan/blob/7a98ea292907689b15bcb7897f7163b8e6508680/util/reggen/validate.py#L1140-L1152
However removing this behaviour alters various autogened headers which breaks existing code. This can be fixed but I wanted to see what people thought before I went and did this. Perhaps there's a reason to preserve this behaviour I haven't considered?
As an alternative we could have reggen generated some additional define that gives you the 'base offset' who's name doesn't change (which in the example above would be equal to PADCTRL_DIO_PADS0_REG_OFFSET/PADCTRL_DIO_PADS_REG_OFFSET), ultimately code that can work with any count will want some base it can then compute an appropriate offset to so referring to something like PADCTRL_DIO_PADS_REG_OFFSET_BASE (as opposed to something that's meant to be a specific register) may make more sense.

@eunchan @msfschaffner @tjaychen any thoughts?

Thanks for bringing this up @GregAC.
I do not know for sure, but I think the index omission in cases where all multireg fields fit within one physical register is only for aesthetical purposes.
Another place where this can cause issues is in our markdown documentation, where we sometimes reference registers by name (!!REGNAME). Those references can break as well if the name changes based on the count.
I do not have a strong preference here, and both of your solutions would work. But I think the first solution is a more holistic fix, as it would also fix the markdown register links.

ah yes i've noticed what you are describing and have definitely run into issues when i was tweaking the number of multiregs also.  I personally vote for consistency, so that even if it fits into register, I prefer to have the index.
I also really like your second suggestion of generating one without an index that links to the first.  That makes a lot of sense to me as well.

Do you want to pull in a few software folks to get their take?

I did flag it up on #software in slack plus I've pointed it out in my padctrl DIF PR. @silvestrst @lenary @gkelly @mcy anything to add?

Always including the index for multiregs makes sense to me.
If we do change this for multiregs, I'd prefer we didn't leave in the aliased name - given we can change this everywhere at once due to the monorepo, I think we should go ahead and do so.
There's already other parts of the generated regs header that are deprecated (the definitions that require a definition of <device><n>_BASE_ADDR), I'd prefer we weren't adding more deprecated definitions to that.

Ok I'd already had a go at making the change so I'm happy to do the PR for this.
Though it may not happen for a week or so, want to let this sit for a few days so there's a chance for someone to shout (so at least til Tuesday/Wednesday given various holidays) if they want to go another way, then I'll start the PR.

To be clearer about the alias: I only have a preference about the aliased C define. If you think an alias is helpful for the docs, I don't want to stop that being created.

@GregAC can this issue be updated / closed?

@GregAC it looks like this fix is still pending, right? do you have something that is ready to be pushed?

I don't have anything beyond what is in my first comment (that I can remember this is a rather old issue!).
Given this will change a bunch of auto-generated code it may cause significant churn in the software side of things. I can take a look but it's way down the priority list and someone else may be better placed to look at it.

Note that the doc aspect of this issue has been fixed with #9237 /#9237.
We ended up fixing the doc references to correctly infer if there is a multireg or not, since changing reggen to always append an index would at this point cause significant churn in RTL/DV/SW.
If this is not causing problems in DV/DIFs right now, we should consider putting this into the backlog.
@sriyerg @GregAC @timothytrippel @tjaychen WDYT?

Into backlog is fine with me. I can't remember what I was doing when this bugged me, but the size of the blast radius (and competing priorities) caused me to drop it then, too.
However, if we find ourselves in a situation where we'll have significantly more IP configurations in the future (which may need to be supported by a single driver), it might behoove us to revisit this.

Related issue: #16938

authors: GregAC a-will lenary msfschaffner tjaychen


text:
[bazel] cleanup opentitan_functest to promote code-reuse

A review comment in #11787 suggested the opentitan_functest rule could benefit from some refactoring to promote code reuse. This does so, and fixes #11805.
Note: this depends on #11835.

Can you rerun the mask rom tests? it looks like this made it fail in CI. Let me know if it looks like CI is misbehaving.

Can you rerun the mask rom tests? it looks like this made it fail in CI. Let me know if it looks like CI is misbehaving.

Fixed.

PR dependency merged.

authors: drewmacrae timothytrippel


text:
[rtl/rv_core_ibex] Fix RTL assertion for CDC

Increase upper bound for cycles to wait in IbexIcacheScrambleKeyRequestAfterFenceI_A.
Partially addresses #16689

This change goes in an RTL file, but it is really more of a DV issue, since the affected code is not synthesized.


text:
[reggen,clkmgr] Add flops to deglitch shadow storage error

Fixes #24592 on the earlgrey_1.0.0 release branch.

Superseded by https://github.com/lowRISC/opentitan/pull/24622. Closing.


text:
[doc] Add top_earlgrey-specific IP blocks to dashboard

Add a table with IP status under the top_earlgrey heading for all IP
blocks which are specific to top_earlgrey.

Good point, I updated the text to be clear about them being comportable as well.


text:
[csrng] Mubi updates

update csrng design and dv to use mubi types

ah i was doing them piecemeal just to ensure i don't majorly break
something and have no way to revert.
On Thu, Oct 14, 2021 at 2:29 PM mwbranstad @.***> wrote:

@.**** commented on this pull request.
In hw/ip/entropy_src/data/entropy_src.hjson
https://github.com/lowRISC/opentitan/pull/8659#discussion_r729355374:

@@ -132,15 +132,15 @@
name: "ENABLE",
mubi: true,
desc: '''

           Setting this field to 0xA will enable the ENTROPY_SRC module.

           Setting this field to kMuBi4True will enable the ENTROPY_SRC module.

Can EDN be also added into this PR, given its exactly the same topic?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/lowRISC/opentitan/pull/8659#discussion_r729355374,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAH2RSVLM2GZQJPZB4OFQOTUG5DTJANCNFSM5F6LEURQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

perfect, stages makes sense. Just didn't want to forget the EDN block that also had fields in it that serve as enables.

authors: mwbranstad tjaychen


text:
🛑 Neo Viewer is down

In 629b8fc, Neo Viewer (http://neoclinica.ddns.net) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Neo Viewer is back up in ba2410b after 10 minutes.

repo: lprone/upptime

license: MIT


text:
Update CI URLs to point to new caching infrastructure

Hello there!
This is an automated pull request submitted by @staticfloat to help package authors transition their Julia installation CI setups to the new binary provider URL.  Please take a look at this PR, and if there is a problem or it doesn't download correctly when CI runs, feel free to ping @staticfloat

Coverage remained the same at 97.823% when pulling ef7df3a9ed7c997912ae2dc4b4745cc99acd37a7 on staticfloat:updated_ci_url into 6b468204f314c9dcf19a54fefc5a8432fb82a5b1 on lruthotto:master.

authors: coveralls staticfloat

license: mit


text:
Quiz Exercises: Improve visibility of selected multiple choice answers

Checklist
General

[x] This is a small issue that I tested locally and was confirmed by another developer on a test server.
[x] Language: I followed the guidelines for inclusive, diversity-sensitive, and appreciative language.
[x] I chose a title conforming to the naming conventions for pull requests.

Client

[x] I followed the coding and design guidelines and ensured that the layout is responsive.
[x] Following the theming guidelines, I specified colors only in the theming variable files and checked that the changes look consistent in both the light and the dark theme.
[x] I documented the TypeScript code using JSDoc style.
[x] I added multiple screenshots/screencasts of my UI changes.

Motivation and Context

The selected options in multiple choice questions are currently not well visible. Students can only see whether or not a question is selected by looking at the checkmark on the right; however, you can select and deselect an option by clicking anywhere in it's box. This can also happen accidentally when the student tries to copy the text.
Fixes #6223.
Description

The background color of selected boxes will now be a transparentized version of the primary color (shade of blue). This will make it obvious that an option is selected. Additionally, there is a small scale animation on the box when an option is selected to enhance the visual feedback on clicks.
Steps for Testing

Prerequisites:

1 Student
1 Quiz Exercise with a Multiple Choice question

Participate in the multiple choice question
Select an option. The whole box should turn to a slight blue background. You should see a short scaling animation.
Deselect the option. The background color should disappear.
Finish the exercise.
When viewing your results, no hover, scaling or clicking effects should happen.

Exam Mode Testing

Prerequisites:

1 Student
1 Instructor
1 Exam with a Quiz Exercise with a Multiple Choice Question

Participate in the exam.
Go to the multiple choice question.
Verify steps 2 and 3 of the normal testing flow.
Hand in the exam. No results should be visible.
Hover the options without your mouse on the exam summary. It should show a "not-allowed" cursor icon.
You should not be able to interact with the answer options. No animations or color effects should occurr.
As instructor, go to the assessment page of the exam after it ended and evaluate the quizzes
As student, go to your exam summary after the results are published. You should see your results like normal. You should not be able to select or deselect options, nor should any color or scale effects appear.

Review Progress

Code Review

[ ] Review 1
[ ] Review 2

Manual Tests

[ ] Test 1
[ ] Test 2

Exam Mode Test

[ ] Test

Screenshots

Before:
https://user-images.githubusercontent.com/23171488/219411002-bd68d6a3-74b4-47fb-879e-f1df63f2938b.mov
After:
https://user-images.githubusercontent.com/23171488/219411087-bb24580b-b902-4112-9c8d-fa017e80d90f.mov

Codecov Report

Merging #6261 (03b7af4) into develop (b5be3ab) will increase coverage by 0.00%.
The diff coverage is n/a.

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

: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
Additional details and impacted files
@@            Coverage Diff             @@
##             develop    #6261   +/-   ##
==========================================
  Coverage      80.27%   80.28%
- Complexity     12909    12910    +1
==========================================
  Files           2286     2286
  Lines          88692    88692
  Branches       13103    13103
==========================================
+ Hits           71199    71204    +5
+ Misses          9744     9741    -3
+ Partials        7749     7747    -2

Impacted Files
Coverage Δ

...idebar/conversation-selection-sidebar.component.ts
89.33% <0.00%> (+0.66%)
:arrow_up:

...ice/scheduled/ParticipantScoreScheduleService.java
87.27% <0.00%> (+2.42%)
:arrow_up:

Flag
Coverage Δ

client
76.43% <ø> (+<0.01%)
:arrow_up:

server
84.56% <ø> (+<0.01%)
:arrow_up:

Continue to review full report at Codecov.

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

authors: bassner codecov-commenter


text:
(role/comcam-fp) add tcp_tweak profile for s3daemon

These are the parameters that KT requested for the lsstcam-dc Nodes.

Why is this different from the existing lhn profile?

just 2 parameters are different (net.ipv4.tcp_congestion_control & net.ipv4.tcp_slow_start_after_idle) you rather I keep the LHN and add another "profile" for these two parameters, or do I add this to the existing LHN profile? @jhoblitt

we should add these 2 parameters to the lhn profile, the rest is the same.

just 2 parameters are different (net.ipv4.tcp_congestion_control & net.ipv4.tcp_slow_start_after_idle) you rather I keep the LHN and add another "profile" for these two parameters, or do I add this to the existing LHN profile? @jhoblitt

I'd rather add those sysctls to the existing LHN profile as support USDF transfers is the intended function of that profile.

authors: cbarria csilva-cl jhoblitt

repo: lsst-it/lsst-control


text:
dtn proposal role

ls site and lsst org will be to invasive for Ampath's dtn, so I created this node role. Looking forward for comments (if I'm missing something or the role has to much on it). I'm also looking a way to disable foreman's org and site.

role seems good to me.

authors: csilva-cl hreinking

repo: lsst-it/lsst-itconf


text:
Real-esrgan taking more time than usual

Describe your environment

GPU: RTX 3090
VRAM: 24GB
CPU arch: [x86/arm]
OS: Linux
Python: Anaconda

Describe the bug
I have tried Real-esrgan on local system and on Replicate demo as well. Usually it is able to upscale 2x in 5-7 seconds. But when I am adding upscaling option in dream API, it is taking 13-15 seconds on average. This becomes a problem when the iteration count is above 3 as it takes a long while to give outputs.
Any idea what I am doing wrong?
My configuration for upscaling is:
gfpgan_strength = 0
upscale_factor = 2
upscale_strength = 0.75

@blessedcoolant, do you have any insights into why this is occurring?

Let me do some testing to see if I can repro this.

Is it tiling when the inference for real esrgan happens?

I don't see any tiling as such. It's just that the real esrgan is taking more time than stable diffusion for upscaling. Almost 13 seconds per image.. That too on a 3090 GPU. Which GPU did you use for the testing?

authors: blessedcoolant gvijqb lstein

repo: lstein/stable-diffusion


text:
🛑 Mirror-爬 is down

In f742416, Mirror-爬 (https://ncov.zhouym.tech/) was down:

HTTP code: 404
Response time: 1111 ms

Resolved: Mirror-鱼露 is back up in a0afc54.


text:
🛑 Mirror-爬 is down

In 4497248, Mirror-爬 (https://ncov.zhouym.tech/) was down:

HTTP code: 404
Response time: 1067 ms

Resolved: Mirror-鱼露 is back up in 55f77b8.


text:
🛑 Mirror-爬 is down

In 85ba252, Mirror-爬 (https://ncov.zhouym.tech/) was down:

HTTP code: 404
Response time: 1215 ms

Resolved: Mirror-鱼露 is back up in e86bc3a.


text:
🛑 Mirror-爬 is down

In ce5fb98, Mirror-爬 (https://ncov.zhouym.tech/) was down:

HTTP code: 404
Response time: 14518 ms

Resolved: Mirror-鱼露 is back up in 4ec31ba.


text:
🛑 Mirror-爬 is down

In 77faffe, Mirror-爬 (https://ncov.zhouym.tech/) was down:

HTTP code: 404
Response time: 1052 ms

Resolved: Mirror-鱼露 is back up in c2a6da0.


text:
Move project from Code::Blocks to VS Code

Create a project configuration for Visual Studio Code.

A minimal vscode project configuration (build and debug) for Windows, using mingw-w64, is now available.
Tasks for building a shared lib and a test program for the shared lib are still missing, but for now this will do.

repo: lszanata/cvector


text:
[SciComp] Finish Tasks in Old GitHub Project

Summary
Need to finish the lingering tasks I have in our old GitHub Project. This follows from #1 . See Enterprise #300 for the overview
Starting Tasks

[x] Finish/migrate Enterprise #281 - Update LTER Site Boundaries

Nearly done, leaving in current location

[x] Finish/migrate Enterprise #282 - Continue to Develop Python literacy

Still at start of task + limited content in non-top-level comment so migrating it
See #4

[x] Finish/migrate Enterprise #283 - Work through Advanced R book

Task likely a ways from done but progress reports aren't vital so migrating it
See #6

[x] Finish/migrate Enterprise #293 - Onboard Resilience WG

Nearly done plus small scope of task so leaving where it is)

[x] Finish/migrate Enterprise #294 - Onboard CAGED WG

Task set but can't start until after their initial onboarding so migrating it
See #5

[x] Finish/migrate Enterprise #298 - Write Data Bits Article

Task incomplete but can safely migrate / recap progress to this point so migrating it
See #7

Useful links

GitHub Enterprise Project (for NJL)

Migrations Done
Finished migrating the issues where I think that makes sense. The two I left alone are both nearly done and have significant information in the thread of comments so I'm leaving them where they're at (at least for now)

Site Boundaries Updated
LTER site boundary data product updated on EDI (see edi.1686.2)! That was my last task in old system so I'm closing this issue

repo: lter/scicomp


text:
🛑 Instagram is down

In 87bb666, Instagram (https://www.instagram.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Instagram is back up in e037c72.


text:
🛑 Secret Site is down

In 8d72a39, Secret Site ($SECRET_SITE) was down:

HTTP code: 0
Response time: 0 ms

completed

completed

repo: luandevpro/status


text:
Add TLS and PeerCertificates.

ValidatedCerts and other TLS fields requires additional work.
qtls/common seems to have most of the information that is needed.

Outdated after #1836.

authors: costinm marten-seemann

repo: lucas-clemente/quic-go


text:
Hide truncatedresult warnings

Part of the purpose of this module is to automatically handle truncated responses, so we should hide this warning if it happens.

Fun fact: errorformat=bc warnings don’t include a code, but they’re always in English and don’t use local interface messages. So I think we can actually reliably detect the warning: in any non-bc errorformat, we can look at the code (truncatedresult); if that’s not present, we check the message against a regex like /^This result was truncated because it would otherwise  ?be larger than the limit of .* bytes$/. (Apart from the extra space accidentally added in wikimedia/mediawiki@1c57794e371d74e1d88748de567a1c3358c3ad2e and removed again in wikimedia/mediawiki@f465c7feb49d2df42da009e732c1427a704f47f9, the message has been stable since it was introduced in wikimedia/mediawiki@d8a241f6a7a0b70b256e0fb1b51a8ab636ad07f2.)

Keep in mind, though, that currently this package nominally supports m3api all the way down to 0.1, which didn’t have warning support yet. So code defensively, or perhaps raise the peer dependency version.

Also, I’d say that not all the request-making methods should hide this warning. In particular, the “partial” methods don’t handle truncated responses (and don’t include the continuation in the return value, so the caller can’t really handle truncated responses correctly either), so I’d say those should continue to show the warning.

license: ISC


text:
Load faster

The code seems that the image loading method is slow.
For example, I think the code should load learning images in parallel.
Current:
https://github.com/lucidrains/denoising-diffusion-pytorch/blob/f900f40f14a7f24b8ef2145b2d2af221b46b4ecc/denoising_diffusion_pytorch/denoising_diffusion_pytorch.py#L601
After:
self.dl = cycle(data.DataLoader(self.ds, batch_size = train_batch_size, num_workers=os.cpu_count(), shuffle=True, pin_memory=True))
May I make an pull request?

Thank you for your coding.

repo: lucidrains/denoising-diffusion-pytorch


text:
🛑 Loxone is down

In 9f5cc46, Loxone (http://loxone.kerl.io) was down:

HTTP code: 502
Response time: 3371 ms

Resolved: Loxone is back up in b2459f6 after 1 minute.

repo: lucienkerl/status


text:
How to hide Prefix from /list ?

How to hide Prefix from /list ?

/list isn't a LuckPerms commands.
LP just provides prefix data to whatever plugin that asks for it, it doesn't actually add prefixes to any commands, messages, scoreboards, nicknames, whatever.

yes essentialsX

authors: BenjaminHoegh lucko

repo: lucko/LuckPerms


text:
Feature/update configuration

Improve project structure:

Change output path from web/ to public
Change default repository type to vcs
Remove github, bitbucket and gitlab entries for repository types
Add .sublime-project to gitignore
Update README with new structure information
Add Docker and Docker Compose installation info on README
Add info on README to run project with Docker
Update and improve docker-compose.yml
Add contributors entry

Hi and thanks for efforts. What the point of renaming /web to /public? It is common practice or convention?
Next version 3.0 will be based on Symfony micro kernel and we will follow Symfony convention, so it's clear why /web was choosen.

Hey @ramunasd !
Its just to know where is the public content. Different web servers use diferent paths. Nginx use /var/www/html, Apache use public_html, etc. Using web/ or public/ is indifferent because we need to configure root path on webserver. Or just mount it correctly inside a container.

Symfony best practices describes recommended and well known directory structure https://symfony.com/doc/current/best_practices/creating-the-project.html#structuring-the-application
cheers!

Directory renamed. Let's follow the Symfony.
We'll continue to support PHP < 7.0 ?
I think it's no needed because we are containerizing the app. I push PHP >= 7.1 to travis-ci can we do it?

Support for PHP <7.0 already dropped. Please take a look at upcoming version https://github.com/ludofleury/satisfy/releases/tag/3.0-rc1

Ok. I'll close this PR and reopen following patterns on branch 3.x

authors: hedcler ramunasd

repo: ludofleury/satisfy


text:
Training error with batch size 64 (two gpus)

The loss is unstable, and the error comes after 430 iters.
2018-12-17 13:55:45,716 SSD.trainer INFO: Train dataset size: 16551
2018-12-17 13:55:45,716 SSD.trainer INFO: Start training
2018-12-17 13:55:53,054 SSD.trainer INFO: Iter: 000010, Lr: 0.00069, Cost: 6.79s, Eta: 11:18:23, Loss: 16.110, Regression Loss 2.962, Classification Loss: 13.149
2018-12-17 13:55:59,009 SSD.trainer INFO: Iter: 000020, Lr: 0.00072, Cost: 5.54s, Eta: 10:35:03, Loss: 14.744, Regression Loss 2.703, Classification Loss: 12.041
2018-12-17 13:56:05,192 SSD.trainer INFO: Iter: 000030, Lr: 0.00074, Cost: 5.78s, Eta: 10:29:42, Loss: 13.971, Regression Loss 2.775, Classification Loss: 11.196
2018-12-17 13:56:11,117 SSD.trainer INFO: Iter: 000040, Lr: 0.00077, Cost: 5.54s, Eta: 10:20:49, Loss: 13.053, Regression Loss 2.877, Classification Loss: 10.176
2018-12-17 13:56:17,044 SSD.trainer INFO: Iter: 000050, Lr: 0.00080, Cost: 5.54s, Eta: 10:14:58, Loss: 11.377, Regression Loss 2.694, Classification Loss: 8.683
2018-12-17 13:56:22,996 SSD.trainer INFO: Iter: 000060, Lr: 0.00082, Cost: 5.57s, Eta: 10:11:33, Loss: 12.235, Regression Loss 2.856, Classification Loss: 9.379
2018-12-17 13:56:28,939 SSD.trainer INFO: Iter: 000070, Lr: 0.00085, Cost: 5.56s, Eta: 10:08:50, Loss: 9.304, Regression Loss 2.722, Classification Loss: 6.582
2018-12-17 13:56:34,890 SSD.trainer INFO: Iter: 000080, Lr: 0.00088, Cost: 5.57s, Eta: 10:06:57, Loss: 9.608, Regression Loss 2.600, Classification Loss: 7.008
2018-12-17 13:56:40,899 SSD.trainer INFO: Iter: 000090, Lr: 0.00090, Cost: 5.63s, Eta: 10:06:10, Loss: 9.044, Regression Loss 2.633, Classification Loss: 6.411
2018-12-17 13:56:46,872 SSD.trainer INFO: Iter: 000100, Lr: 0.00093, Cost: 5.59s, Eta: 10:05:02, Loss: 10.493, Regression Loss 2.597, Classification Loss: 7.896
2018-12-17 13:56:52,839 SSD.trainer INFO: Iter: 000110, Lr: 0.00096, Cost: 5.58s, Eta: 10:04:02, Loss: 9.837, Regression Loss 2.504, Classification Loss: 7.333
2018-12-17 13:56:58,813 SSD.trainer INFO: Iter: 000120, Lr: 0.00098, Cost: 5.59s, Eta: 10:03:18, Loss: 8.993, Regression Loss 2.577, Classification Loss: 6.416
2018-12-17 13:57:04,785 SSD.trainer INFO: Iter: 000130, Lr: 0.00101, Cost: 5.58s, Eta: 10:02:36, Loss: 9.234, Regression Loss 2.366, Classification Loss: 6.868
2018-12-17 13:57:10,782 SSD.trainer INFO: Iter: 000140, Lr: 0.00104, Cost: 5.61s, Eta: 10:02:12, Loss: 9.572, Regression Loss 2.397, Classification Loss: 7.175
2018-12-17 13:57:16,768 SSD.trainer INFO: Iter: 000150, Lr: 0.00106, Cost: 5.60s, Eta: 10:01:47, Loss: 10.361, Regression Loss 2.455, Classification Loss: 7.906
2018-12-17 13:57:22,772 SSD.trainer INFO: Iter: 000160, Lr: 0.00109, Cost: 5.62s, Eta: 10:01:32, Loss: 11.323, Regression Loss 2.497, Classification Loss: 8.826
2018-12-17 13:57:28,794 SSD.trainer INFO: Iter: 000170, Lr: 0.00112, Cost: 5.63s, Eta: 10:01:19, Loss: 11.311, Regression Loss 2.368, Classification Loss: 8.942
2018-12-17 13:57:34,801 SSD.trainer INFO: Iter: 000180, Lr: 0.00114, Cost: 5.62s, Eta: 10:01:07, Loss: 14.360, Regression Loss 2.493, Classification Loss: 11.866
2018-12-17 13:57:40,815 SSD.trainer INFO: Iter: 000190, Lr: 0.00117, Cost: 5.62s, Eta: 10:00:55, Loss: 9.740, Regression Loss 2.547, Classification Loss: 7.192
2018-12-17 13:57:46,815 SSD.trainer INFO: Iter: 000200, Lr: 0.00120, Cost: 5.61s, Eta: 10:00:42, Loss: 12.304, Regression Loss 2.444, Classification Loss: 9.860
2018-12-17 13:57:53,002 SSD.trainer INFO: Iter: 000210, Lr: 0.00122, Cost: 5.76s, Eta: 10:01:10, Loss: 9.891, Regression Loss 2.465, Classification Loss: 7.427
2018-12-17 13:57:59,044 SSD.trainer INFO: Iter: 000220, Lr: 0.00125, Cost: 5.66s, Eta: 10:01:18, Loss: 10.401, Regression Loss 2.495, Classification Loss: 7.905
2018-12-17 13:58:05,060 SSD.trainer INFO: Iter: 000230, Lr: 0.00128, Cost: 5.63s, Eta: 10:01:06, Loss: 9.791, Regression Loss 2.253, Classification Loss: 7.538
2018-12-17 13:58:11,072 SSD.trainer INFO: Iter: 000240, Lr: 0.00130, Cost: 5.63s, Eta: 10:00:55, Loss: 9.441, Regression Loss 2.396, Classification Loss: 7.045
2018-12-17 13:58:17,158 SSD.trainer INFO: Iter: 000250, Lr: 0.00133, Cost: 5.68s, Eta: 10:00:57, Loss: 8.072, Regression Loss 2.440, Classification Loss: 5.632
2018-12-17 13:58:23,013 SSD.trainer INFO: Iter: 000260, Lr: 0.00136, Cost: 5.47s, Eta: 10:00:13, Loss: 8.662, Regression Loss 2.442, Classification Loss: 6.221
2018-12-17 13:58:29,099 SSD.trainer INFO: Iter: 000270, Lr: 0.00138, Cost: 5.70s, Eta: 10:00:20, Loss: 8.421, Regression Loss 2.250, Classification Loss: 6.171
2018-12-17 13:58:35,208 SSD.trainer INFO: Iter: 000280, Lr: 0.00141, Cost: 5.72s, Eta: 10:00:30, Loss: 8.425, Regression Loss 2.143, Classification Loss: 6.281
2018-12-17 13:58:41,339 SSD.trainer INFO: Iter: 000290, Lr: 0.00144, Cost: 5.73s, Eta: 10:00:41, Loss: 9.016, Regression Loss 2.448, Classification Loss: 6.568
2018-12-17 13:58:47,479 SSD.trainer INFO: Iter: 000300, Lr: 0.00146, Cost: 5.74s, Eta: 10:00:57, Loss: 11.354, Regression Loss 2.215, Classification Loss: 9.139
2018-12-17 13:58:53,697 SSD.trainer INFO: Iter: 000310, Lr: 0.00149, Cost: 5.81s, Eta: 10:01:23, Loss: 12.369, Regression Loss 2.147, Classification Loss: 10.221
2018-12-17 13:58:59,810 SSD.trainer INFO: Iter: 000320, Lr: 0.00152, Cost: 5.72s, Eta: 10:01:33, Loss: 10.004, Regression Loss 2.278, Classification Loss: 7.726
2018-12-17 13:59:05,849 SSD.trainer INFO: Iter: 000330, Lr: 0.00154, Cost: 5.65s, Eta: 10:01:26, Loss: 7.794, Regression Loss 2.384, Classification Loss: 5.411
2018-12-17 13:59:11,847 SSD.trainer INFO: Iter: 000340, Lr: 0.00157, Cost: 5.61s, Eta: 10:01:11, Loss: 8.697, Regression Loss 2.366, Classification Loss: 6.331
2018-12-17 13:59:17,999 SSD.trainer INFO: Iter: 000350, Lr: 0.00160, Cost: 5.75s, Eta: 10:01:21, Loss: 12.521, Regression Loss 2.570, Classification Loss: 9.951
2018-12-17 13:59:24,357 SSD.trainer INFO: Iter: 000360, Lr: 0.00162, Cost: 5.98s, Eta: 10:02:10, Loss: 12.485, Regression Loss 2.474, Classification Loss: 10.012
2018-12-17 13:59:30,369 SSD.trainer INFO: Iter: 000370, Lr: 0.00165, Cost: 5.63s, Eta: 10:01:55, Loss: 12.791, Regression Loss 2.641, Classification Loss: 10.150
2018-12-17 13:59:36,477 SSD.trainer INFO: Iter: 000380, Lr: 0.00168, Cost: 5.73s, Eta: 10:01:59, Loss: 11.360, Regression Loss 2.661, Classification Loss: 8.699
2018-12-17 13:59:42,585 SSD.trainer INFO: Iter: 000390, Lr: 0.00170, Cost: 5.72s, Eta: 10:01:59, Loss: 11.183, Regression Loss 2.592, Classification Loss: 8.591
2018-12-17 13:59:48,701 SSD.trainer INFO: Iter: 000400, Lr: 0.00173, Cost: 5.72s, Eta: 10:01:59, Loss: 10.166, Regression Loss 2.575, Classification Loss: 7.590
2018-12-17 13:59:54,813 SSD.trainer INFO: Iter: 000410, Lr: 0.00176, Cost: 5.72s, Eta: 10:02:02, Loss: 17.562, Regression Loss 2.554, Classification Loss: 15.008
2018-12-17 14:00:00,942 SSD.trainer INFO: Iter: 000420, Lr: 0.00178, Cost: 5.74s, Eta: 10:02:05, Loss: 10.339, Regression Loss 2.592, Classification Loss: 7.747
2018-12-17 14:00:07,075 SSD.trainer INFO: Iter: 000430, Lr: 0.00181, Cost: 5.75s, Eta: 10:02:10, Loss: 28.599, Regression Loss 9.237, Classification Loss: 19.362
Traceback (most recent call last):
  File "train_ssd.py", line 139, in <module>
    main()
  File "train_ssd.py", line 130, in main
    model = train(cfg, args)
  File "train_ssd.py", line 76, in train
    return do_train(cfg, model, train_loader, optimizer, scheduler, criterion, device, args)
  File "/home/ycg/workspace/SSD/ssd/engine/trainer.py", line 78, in do_train
    regression_loss, classification_loss = criterion(confidence, locations, labels, boxes)
  File "/home/ycg/anaconda3/lib/python3.6/site-packages/torch/nn/modules/module.py", line 489, in __call__
    result = self.forward(*input, **kwargs)
  File "/home/ycg/workspace/SSD/ssd/modeling/multibox_loss.py", line 31, in forward
    mask = box_utils.hard_negative_mining(loss, labels, self.neg_pos_ratio)
  File "/home/ycg/workspace/SSD/ssd/utils/box_utils.py", line 123, in hard_negative_mining
    _, indexes = loss.sort(dim=1, descending=True)
RuntimeError: merge_sort: failed to synchronize: an illegal memory access was encountered
Traceback (most recent call last):
  File "train_ssd.py", line 139, in <module>
    main()
  File "train_ssd.py", line 130, in main
    model = train(cfg, args)
  File "train_ssd.py", line 76, in train
    return do_train(cfg, model, train_loader, optimizer, scheduler, criterion, device, args)
  File "/home/ycg/workspace/SSD/ssd/engine/trainer.py", line 78, in do_train
    regression_loss, classification_loss = criterion(confidence, locations, labels, boxes)
  File "/home/ycg/anaconda3/lib/python3.6/site-packages/torch/nn/modules/module.py", line 489, in __call__
    result = self.forward(*input, **kwargs)
  File "/home/ycg/workspace/SSD/ssd/modeling/multibox_loss.py", line 31, in forward
    mask = box_utils.hard_negative_mining(loss, labels, self.neg_pos_ratio)
  File "/home/ycg/workspace/SSD/ssd/utils/box_utils.py", line 123, in hard_negative_mining
    _, indexes = loss.sort(dim=1, descending=True)
RuntimeError: merge_sort: failed to synchronize: an illegal memory access was encountered
terminate called without an active exception
terminate called without an active exception

When I set a longer warm-up iterations, the error seem not occur

The sort method failed due to NaN numbers. This may be a bug: https://github.com/pytorch/pytorch/issues/14335 .
Two ways to solve :

use a smaller learning rate.
Described in the forums by Jinserk Baik

Yeah, longer warm-up iterations or smaller warm-up factor may also help.

authors: LightToYang lufficc

repo: lufficc/SSD


text:
[orchestrator] Invalid transaction bug

When transaction is invalid. The promise is not resolved and the main thread is stuck.

Solved

repo: luguslabs/archipel


text:
built in or externally packaged lua scripts

would be great to include some useful lua scripts out of the box. in particular, http://stackoverflow.com/a/27561399/927092
could also be a package called ioredis-extensions or something!

make sense. I prefer to create an externally package to include these scripts since it's easy to use them without increasing complexity to ioredis itself:
var Redis = require('ioredis');
var redis = new Redis();
require('ioredis-extensions')(redis);

Yup. That would be awesome!

I actually developed recently a set of tools for easy usage of lua scripts within node.js. Basically I take a lua script, and output a javascript module that can be easily used with ioredis or any other redis client: redis-lua2js, gulp-redis-lua2js, node-hook-redis-lua, and some standalone lua commands using those tools: redis-pdel. Maybe these can help solve this issue?

authors: jonathanong luin perrin4869

repo: luin/ioredis


text:
Update dict.py to check if dictionary key exists

Ensure dictionary key exists to support common .get() method with default when not existing. Current code throws keyerror even when using a smd.get('non-exist-key', 'default_value')

I am going to re-open this as a new PR to remove a now irrelevant commit.

repo: luizalabs/shared-memory-dict


text:
Redis cluster mode password verification failed

When using the cluster mode, when the -a parameter is used in the main command, and a certain instance of the cluster is successfully connected, if an instance switch occurs, the newly created instance does not automatically use the master password for authorization and the application is interrupted.

yes，I just debug t Yes, I just checked it with Debug, and the best optimization can be done in this way.

close this PR


text:
[bug] 当文档较长时，且分散插入了多个画板(board)时，下载会丢失画板中的内容。

如题，该问题可以通过，文档从头到尾挨个点击画板内容的方式确保内容不被丢失，但是长文档时很麻烦，不知道是否能够优化一下，万分感谢！

目前还没有找到比较好的解决方案。不过你可以将文档滚动至底部，确保每个画板均显示（无需点击），然后再开始下载。这种方式相比挨个点击画板内容，稍微好一些。

ok，我先这样使用吧，谢谢回复~


text:
🛑 Rothcoaching Challenges is down

In 28f0139, Rothcoaching Challenges (https://rothcoaching-challenges.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Rothcoaching Challenges is back up in b3d2f51.

repo: lukas-hablitzel/upptime


text:
Cursorline highlight gets stuck

https://user-images.githubusercontent.com/8026227/125154638-43973f00-e19e-11eb-81d6-4a606b035801.mp4

duplicate of #59

authors: drzel lukas-reineke


text:
eslint

Description

add eslint

Notes
s/getState/useState

as per mentioned in #3

@lukashala merge ?

@jbouhier I have some bigger plans with this state management. I'm doing some rewrites, so I will keep it for now, if you don't mind.

authors: jbouhier lukashala mattiaerre

repo: lukashala/react-simply


text:
Infinite loop

I managed to make an infinite reorder loop (while I keep the mouse button pressed) in "Connected lists" (the left list).

Can you explain this more or attach a video.

authors: lukasoppermann vporton


text:
theme with k8s plugin

Thanks @lukesampson

Cool

authors: itscaro lukesampson

repo: lukesampson/pshazz

license: unlicense


text:
altair@2.3.5: download via aria2 failed

Download: 10/15 20:49:42 [ERROR] CUID#8 - Download aborted. URI=https://github.com/imolorhe/altair/releases/download/v2.3.5/altair_2.3.5_win.exe#/dl.7z
Download: Exception: [AbstractCommand.cc:351] errorCode=3 URI=https://github.com/imolorhe/altair/releases/download/v2.3.5/altair_2.3.5_win.exe
Download:   -> [HttpSkipResponseCommand.cc:219] errorCode=3 Resource not found
Download: Download Results:
Download: gid   |stat|avg speed  |path/URI
Download: ======+====+===========+=======================================================
Download: 0c1366|ERR |       0B/s|C:/Users/Mingpeng/scoop/cache/altair#2.3.5#https_github.com_imolorhe_altair_releases_download_v2.3.5_altair_2.3.5_win.exe_dl.7z
Download: Status Legend:
Download: (ERR):error occurred.
Download: aria2 will resume download if the transfer is restarted.
Download: If there are any errors, then see the log file. See '-l' option in help/man page for details.
ERROR Download failed! (Error 3) Resource was not found
ERROR https://github.com/imolorhe/altair/releases/download/v2.3.5/altair_2.3.5_win.exe#/dl.7z
referer=https://github.com/imolorhe/altair/releases/download/v2.3.5/altair_2.3.5_win.exe#/
dir=C:\Users\Mingpeng\scoop\cache
out=altair#2.3.5#https_github.com_imolorhe_altair_releases_download_v2.3.5_altair_2.3.5_win.exe_dl.7z
ERROR & 'C:\Users\Mingpeng\scoop\apps\aria2\current\aria2c.exe' --input-file='C:\Users\Mingpeng\scoop\cache\altair.txt' --user-agent='Scoop/1.0 (+http://scoop.sh/) PowerShell/5.1 (Windows NT 10.0; Win64; x64; Desktop)' --allow-overwrite=true --auto-file-renaming=false --retry-wait=2 --split=5 --max-connection-per-server=5 --min-split-size=5M --console-log-level=warn --enable-color=false --no-conf=true --follow-metalink=true --metalink-preferred-protocol=https --min-tls-version=TLSv1.2 --stop-with-process=3976 --continue

Hey @r15ch13 sorry about the package name change. Unfortunately it's going to be changed back to the original naming in v2.3.6, so that might break again. 😞

No problem :smile:
Just create a PR when you have released the new version :grin:

authors: imolorhe r15ch13 tryyoung

repo: lukesampson/scoop-extras

license: Unlicense


text:
Notepad++: fix au

https://github.com/lukesampson/scoop-extras/issues/2308

Let's wait for https://github.com/notepad-plus-plus/notepad-plus-plus/issues/6192 to be fixed.

There are two new releases until then... Please merge this and I'll open another pr when https available.


text:
Module 2 /  Block 5 / Day - 2 code review

Great looking code and Good UI. 👍

Please your dist folder does not have the latest version of your code, Please try to update it.
Also the link to the live demo in your ReadMe file is broken.
In your fetchData function, you can don't really need to specify the GET, method for a get request because that's the default

Acknowledgements

No Linters errors 👍
Good github flows 💯
Clean and readable code 🥇

Optional
Kindy create new variable and add these api url. This can reduce code repetition.
https://github.com/lukman155/leaderboard/blob/30aba0968deb280b36816ff166fef092c8438109/src/index.js#L14-L25


text:
Autoloading issues

Hello again!
I'm having some issues with the autoloading. Primarily when deploying the code.
I like to put my related tests inside my domains (a command for generating tests would be great by the way), but that generates problems with the autoloading. The tests are only autoloaded when composer includes dev dependencies. But since theddd:cache command touches all files in the domain directory, this generates problems because the base test case is not autoloaded and thus I get this error: Class "Tests\TestCase" not found when running ddd:cache.
I created a repo where I demonstrate this problem here: https://github.com/pelmered/laravel-test-ddd
Just clone, run composer install --no-dev and then run ddd:cache to reproduce the problem.
I have also had problems with some other things, for example the migrations from babenkoivan/elastic-migrations. That package creates migrations with the same file format as the default Laravel migrations, but they also include a class name so they are not PSR autoload compliant. Here is how they look. When autoloading or  running ddd:cache these files are included several times and therefore gives this kind of error: Cannot declare class CreateUsersIndex, because the name is already in use. I created a PR there to use anonymous classes, just like Laravels migrations, here.
As you can see, this is a general problem that probably needs to be addressed in this package in some way.
What do you think is the best way forward? Let me know if I can be of assistance.
Other than this, I'm happy to report that it worked very well in our application and that the transition was very smooth to start using the autoload provided in this package.

Hello again!
I'm having some issues with the autoloading. Primarily when deploying the code.
I like to put my related tests inside my domains (a command for generating tests would be great by the way), but that generates problems with the autoloading. The tests are only autoloaded when composer includes dev dependencies. But since theddd:cache command touches all files in the domain directory, this generates problems because the base test case is not autoloaded and thus I get this error: Class "Tests\TestCase" not found when running ddd:cache.
I created a repo where I demonstrate this problem here: https://github.com/pelmered/laravel-test-ddd Just clone, run composer install --no-dev and then run ddd:cache to reproduce the problem.

Ah, so is it a matter where ddd autoloading should be ignoring the test directory if there is one? And therefore be able to configure a designated domain test folder to ignore. Or more generally, maybe a configurable ddd.autoload.ignore.

I have also had problems with some other things, for example the migrations from babenkoivan/elastic-migrations. That package creates migrations with the same file format as the default Laravel migrations, but they also include a class name so they are not PSR autoload compliant. Here is how they look. When autoloading or running ddd:cache these files are included several times and therefore gives this kind of error: Cannot declare class CreateUsersIndex, because the name is already in use. I created a PR there to use anonymous classes, just like Laravels migrations, here.
As you can see, this is a general problem that probably needs to be addressed in this package in some way. What do you think is the best way forward? Let me know if I can be of assistance.

I see, I remember this kind of behaviour back when Laravel wasn't using anonymous classes yet for migrations. That being said, are you generating migrations inside the domain layer then, hence why it gets picked up by ddd:cache?

Other than this, I'm happy to report that it worked very well in our application and that the transition was very smooth to start using the autoload provided in this package.

Ah, so is it a matter where ddd autoloading should be ignoring the test directory if there is one? And therefore be able to configure a designated domain test folder to ignore. Or more generally, maybe a configurable ddd.autoload.ignore.

Yes, some kind of general solution like an configurable ignore would be great. An array with paths inside each Domain(relative to domain root) that should be ignored would work. Something like this:
'ignore' => [
    'Tests',
    'Database/ElasticMigrations',
    'Any/Other/Folder/To/Ignore',
],

I did not see any support for this in Lody, but it should be possible to do this with a custom finder filter.

I see, I remember this kind of behaviour back when Laravel wasn't using anonymous classes yet for migrations. That being said, are you generating migrations inside the domain layer then, hence why it gets picked up by ddd:cache?

Yes, I like to put migrations, factories and seeders inside the domain they belong to. The ignore could be used to solve this as well 👍

I wonder if ddd:migration and ddd:test should be added at some point. In your case, you're generating domain migrations by way of the elastic-migrations package, I take it?
Being able to bundle in tests and migrations would make the domain fully portable and copy-paste-able from one app to another at that point.

I wonder if ddd:migration and ddd:test should be added at some point.

That would be great.
Even better of you could also add the flags for generating factories, migrations, tests, policies etc. to the ddd:model command. Like the default make:model command has. That was a function I missed yesterday when I made my first model using this package.

In your case, you're only generating domain migrations by way of the elastic-migrations package, I take it?

Yes, that package provides an elastic:make:migration command that I use.

Being able to bundle in tests and migrations would make the domain fully portable and copy-paste-able from one app to another at that point.

I'm working on a product company with a single Laravel project so that is not my primary reason, but if you are working with multiple projects I could imagine that would be would be very handy.

Yeah, the portable-domain scenario is well suited for those who build multiple apps for various clients (such as me).
I will work on these updates over the weekend.

Yeah, the portable-domain scenario is well suited for those who build multiple apps for various clients (such as me).
I will work on these updates over the weekend.

Great, thanks a lot!
I was able to filter out the tests using this code:
        return Lody::classesFromFinder(
            Finder::create()
                  ->files()
                  ->in($paths)
                  ->filter(function ($file) {
                      if (Str::startsWith(strstr($file->getRelativePathname(), '/'), '/Tests/')) {
                          return false;
                      }
                  }))
            ->isNotAbstract()
            ->isInstanceOf(Command::class)
            ->toArray();

So, something like that would work.
Another idea that I think would be great is support for something like this to provide your own filter callback like this in your service provider:
DDD::filterPathUsing(function ($file) {
    // Your custom callback
});

Then you could implement your own logic for this and not just and array of simple startsWith strings.

I created a repo where I demonstrate this problem here: https://github.com/pelmered/laravel-test-ddd
Just clone, run composer install --no-dev and then run ddd:cache to reproduce the problem.

I cloned the repo and ran composer install --no-dev, which yielded the following:

Everything works if I do a composer install without --no-dev, but then ddd:cache works and doesn't produce any error. What am I missing?

...however, I was able to simulate and reproduce it within the package tests, so I'll be able to move forward without the reproduction repo.

authors: JasperTey pelmered

repo: lunarstorm/laravel-ddd


text:
Consider cleaning up eslint-config-react-union

The boilerplate projects still contain some additional ESLint configuration in their .eslintrc files which could instead be moved to the eslint-config-react-union package.
In order to reduce maintenance and cognitive overhead, I suggest cleaning up the eslint-config-react-union package by removing most of the rules, using a known and popular config such as Airbnb or StandardJS and tweaking only some of the rules specific to React-union or Prettier.

Thank you for the issue. I agree with the need of updating a few rules (maybe add new). But I strongly disagree with adding another dependency in form of other solutions.
We are a team of experienced developers and we can develop our set of linting rules.

I don't see how being a team of experienced developers is an argument for developing and maintaining our own set of linting rules. It just creates unnecessary maintenance overhead. It would be much better if we instead focused on more important tasks and if we left the linting rules to someone else (with more resources).

If we adopt someones else linting rules it will bring overhead to learn them, modify them and maintain them with new versions.

Alright, but I'd like the individual .eslintrc files in boilerplates (and real-world projects) to be as clean as possible. Here are some sample rules:
module.exports = {
	root: true,
	extends: ['react-union'],
	globals: {
		__DEV__: true,
	},
	rules: {
		'import/no-extraneous-dependencies': [
			'error',
			{
				devDependencies: [
					'packages/**/*.test.js',
					'packages/**/*.stories.js',
					'testsSetup.js',
					'api/**/*',
				],
			},
		],
		// conflicts with prettier
		'react/jsx-max-props-per-line': 0,
		'max-len': 0,
		'space-before-function-paren': [
			'error',
			{
				anonymous: 'never',
				named: 'never',
				asyncArrow: 'always',
			},
		],
	},
};

We should definitely make sure that the Prettier integration is as seamless as possible and that they don't conflict (at least use eslint-config-prettier and eslint-plugin-prettier).

authors: aizerin tommmyy wafflepie

repo: lundegaard/react-union


text:
update cookie

保证默认cookie切换到安全cookie时值的正常性。

Thanks!

authors: lijunfeng lunny

repo: lunny/tango


text:
Add Muni, this moment

:oncoming_bus:

:hibiscus:

repo: luqmaan/awesome-transit


text:
I would like to add Saka Keys to my Google Chrome browser.

I have been using Saka Keys for Mozilla Firefox for many years.  I recently installed Google Chrome as an alternative browser.  I would like to install Saka Keys on Google Chrome, export my Saka Key settings from Firefox, and import those settings to Saka Keys in Chrome.
I noticed that the Saka Keys page does not exist for Google Chrome.  I read in a Github post from last year that it was taken down.
Is there any other way to get Saka Keys on Google Chrome, and a safe way that won't make my computer vulnerable to malware, etc.?

The developer instructions found here "https://key.saka.io/docs/developers/setup" worked for me here on Linux.

Looks like this addon hasn't been updated in 2.5 years. And I can't @ lusaka. Come on. You had this extension on Chrome. You have it on Firefox. Why can't you add it on Chrome again?  Find out why Chrome took it down, make the necessary adjustments, and put it back up!!! What's the point of creating and (not) maintaining an extension if the extension sites don't have your extension?
@eejdoowad
@brandonkal
@neilmacintyre
@gliptak
@rleppink
@t754
@pureooze
@yfdyh000
@AlliedEnvy
@Eckaaaaaat
@sempasha
@UnsolvedCypher
@alexherbo2
@UnicodingUnicorn
@edjroot
@daviddostal
@JingYenLoh
@patrickchin
@siemieniec
@kaylynb

Since it is open source, complaints aren't welcome. Anybody is able to contribute or even fork extension code.

Then allow me to try and get this taken off of the other extension sites like Firefox, etc. It's obvious you don't care. I tried searching 25 days ago on alternative means on how to install this extension, and as I mentioned in my original post 25 days ago all those methods were reported as leaving my computer vulnerable to malware. I asked politely in my original post, and never received a response from a contributor in a month. That was me being considerate and patient. I then @'d every contributor because, as I mentioned, lusaka can't be @'s and I don't know which contributors are the most active and most responsible for this extension. It only makes sense if I can't add the extension myself, and I can't get the extension back on the Chrome extension site, and I can't edit the extension, to try and find someone who can do these things. I'm sorry if my wording in my second post OFFENDED or TRIGGERED you, but we live in a sad time where people get that upset over "it shouldn't be hard and it shouldn't take much time for an experienced contributor to figure out why the extension was taken down and put it back up". You call me an entitled whiner, but you are whining even more than I am and you "go to" is to throw up a bunch of defensive virtue signaling instead and OBSTRUCTING. I mean all those people were @'d one time. One of them might have been able to solve the problem. Instead of letting them get @'d the one time out of 365 days a year, in maybe 10 freaking years, you deleted the @. So fine. You win. I can't deal with people like you. But hey, maybe I'll get this extension taken down from ALL websites online and then you never have to worry about ever getting @'d anymore. Because it doesn't matter right.  No one cares. It's obvious you don't.

repo: lusakasa/saka-key


text:
Auto-Restart doesn't work with ctrl-c on hanging example script

#30 helped with resetting when the host app dies.
However, I'm seeing another case where the device doesn't reset/cleanup on failure. To reproduce:

Run python3 example_run_landmarks_recognition.py. It should hang (see #32).
ctrl-c 2x
Run python3 example_run_landmarks_recognition.py or any other script. The script will fail to start with an error like below:

python3 test.py
Using Custom Calibration File: depthai.calib
Using Arguments= {'config_overwrite': None}
depthai.__version__ == 0.0.9a
depthai.__dev_version__ == 35018f82c3451287cc6661c04faa764a7a58b4bc
depthai: before xlink init;
Device Found name 1.2-
about to boot device with "cmd_file": /home/pi/Desktop/depthai-python-extras/depthai.cmd
not xlink success
depthai: Error initalizing xlink;
Error initializing device. Try to reset it.

This is not fixed on Master so closing the issue.

repo: luxonis/depthai


text:
[BUG] OAK-D Lite is being skipped on Ubuntu boot

Bug description
Device.getAllAvailableDevices() method skips connected via USB3 port camera and outputs the following warning message
skipping X_LINK_UNBOOTED device having name '1.4'

when first logged in to Ubuntu 20.04.
Additional information

auto-login is enabled,
script was added into autostart list by creating corresponding '.desktop' file under '~/.config/autostart/' directory with the following content:

[Desktop Entry]
Type=Application
Exec=gnome-terminal --window --maximize --working-directory="~/" -- /bin/bash -c "python3 script.py"
Hidden=false
NoDisplay=false
X-GNOME-Autostart-enabled=true
Comment[en_US]=App Autorunner
Comment=App Autorunner

adding 11 second delay before running the script didn't solve the problem,
re-running the script immediately resolves problem but it isn't preferable,
camera is being connected via 30ft USB cable

Expected behavior
Don't skip the device at first run.

@SergeyVasilyan does it work with a shorter cable, included with the device?

@themarpe Yes, but in my case 30ft cable is necessary.

Would it be possible to use one or several actively powered USB3-capable USB-hubs?

@SergeyVasilyan its likely a bad cable or out of spec one. One extra thing to try is to force USB2 mode, but given the error even USB2 isn't working as expected. This is otherwise out of scope for a software solution, and would recommend same as @brmarkus - to get a proper active / optical cable for such distances (or hubs)

@themarpe Today the issue occurred when using the short cable that comes with the Camera.

@SergeyVasilyan I'd have to gather more info - do you mind running with DEPTHAI_LEVEL=trace and post back the results.
In this case it likely goes down to XLink but we don't expose a means of pushing out those logs. I'll modify the library to do so

@themarpe  please find the log below:
[setupvars.sh] OpenVINO environment initialized

[2022-12-13 17:56:49.316] [debug] Python bindings - version: 2.17.3.1 from 2022-08-19 20:56:54 +0200 build: 2022-08-19 20:06:40 +0000
[2022-12-13 17:56:49.316] [debug] Library information - version: 2.17.3, commit: 41de567ea52443368224145b9e54a4f858abaeb8 from 2022-08-17 19:22:44 +0200, build: 2022-08-19 19:51:23 +0000
[2022-12-13 17:56:49.319] [debug] Initialize - finished
[2022-12-13 17:56:49.746] [debug] Resources - Archive 'depthai-bootloader-fwp-0.0.20.tar.xz' open: 23ms, archive read: 394ms
[2022-12-13 17:56:50.688] [debug] Resources - Archive 'depthai-device-fwp-602822fe9eaca68a72c666497dc4979b29291b3e.tar.xz' open: 4ms, archive read: 1366ms
[2022-12-13 17:56:51.855] [warning] skipping X_LINK_UNBOOTED device having name "1.4"

[DeviceInfo(name=3.1, mxid=14442C10A1E0AECE00, X_LINK_UNBOOTED, X_LINK_USB_VSC, X_LINK_MYRIAD_X, X_LINK_SUCCESS), DeviceInfo(name=3.2, mxid=14442C1051EDAECE00, X_LINK_UNBOOTED, X_LINK_USB_VSC, X_LINK_MYRIAD_X, X_LINK_SUCCESS)]

[2022-12-13 17:56:51.863] [debug] Device - OpenVINO version: 2021.4
[2022-12-13 17:56:52.705] [debug] Searching for booted device: DeviceInfo(name=3.1, mxid=14442C10A1E0AECE00, X_LINK_BOOTED, X_LINK_USB_VSC, X_LINK_MYRIAD_X, X_LINK_SUCCESS), name used as hint only
[2022-12-13 17:56:54.020] [trace] RPC: [1,1,10182484315255513117,[0]]
[2022-12-13 17:56:54.022] [trace] RPC: [1,1,5804304869041345055,[1.0]]
[2022-12-13 17:56:54.026] [trace] RPC: [1,1,2545553886520231446,null]
[2022-12-13 17:56:54.027] [trace] Log vector decoded, size: 3
[14442C10A1E0AECE00] [3.1] [43.011] [system] [info] Memory Usage - DDR: 0.12 / 340.93 MiB, CMX: 2.05 / 2.50 MiB, LeonOS Heap: 7.21 / 77.58 MiB, LeonRT Heap: 2.88 / 41.37 MiB
[14442C10A1E0AECE00] [3.1] [43.011] [system] [info] Temperatures - Average: 33.39 °C, CSS: 34.64 °C, MSS 33.21 °C, UPA: 32.73 °C, DSS: 32.97 °C
[14442C10A1E0AECE00] [3.1] [43.011] [system] [info] Cpu Usage - LeonOS 8.58%, LeonRT: 1.89%
[2022-12-13 17:56:54.027] [debug] Device about to be closed...
[2022-12-13 17:56:54.028] [debug] XLinkResetRemote of linkId: (0)
[2022-12-13 17:56:54.029] [debug] Log thread exception caught: Couldn't read data from stream: '__log' (X_LINK_ERROR)
[2022-12-13 17:56:54.029] [debug] Timesync thread exception caught: Couldn't read data from stream: '__timesync' (X_LINK_ERROR)
[2022-12-13 17:56:55.486] [debug] Device closed, 1458
[2022-12-13 17:56:55.487] [debug] Device - OpenVINO version: 2021.4
[2022-12-13 17:56:56.309] [debug] Searching for booted device: DeviceInfo(name=3.2, mxid=14442C1051EDAECE00, X_LINK_BOOTED, X_LINK_USB_VSC, X_LINK_MYRIAD_X, X_LINK_SUCCESS), name used as hint only
[2022-12-13 17:56:57.591] [trace] RPC: [1,1,10182484315255513117,[0]]
[2022-12-13 17:56:57.594] [trace] RPC: [1,1,5804304869041345055,[1.0]]
[2022-12-13 17:56:57.598] [trace] RPC: [1,1,2545553886520231446,null]
[2022-12-13 17:56:57.604] [trace] Log vector decoded, size: 3
[14442C1051EDAECE00] [3.2] [45.946] [system] [info] Memory Usage - DDR: 0.12 / 340.93 MiB, CMX: 2.05 / 2.50 MiB, LeonOS Heap: 7.21 / 77.58 MiB, LeonRT Heap: 2.88 / 41.37 MiB
[14442C1051EDAECE00] [3.2] [45.946] [system] [info] Temperatures - Average: 34.16 °C, CSS: 35.35 °C, MSS 33.69 °C, UPA: 33.69 °C, DSS: 33.93 °C
[14442C1051EDAECE00] [3.2] [45.946] [system] [info] Cpu Usage - LeonOS 8.53%, LeonRT: 1.87%
[2022-12-13 17:56:57.605] [debug] Device about to be closed...
[2022-12-13 17:56:58.344] [debug] Watchdog thread exception caught: Couldn't write data to stream: '__watchdog' (X_LINK_ERROR)
[2022-12-13 17:56:58.473] [debug] Log thread exception caught: Couldn't read data from stream: '__log' (X_LINK_ERROR)
[2022-12-13 17:56:58.474] [debug] Timesync thread exception caught: Couldn't read data from stream: '__timesync' (X_LINK_ERROR)
[2022-12-13 17:56:58.712] [debug] XLinkResetRemote of linkId: (0)
[2022-12-13 17:56:59.091] [debug] Device closed, 1486

Re-running the app once again

[DeviceInfo(name=3.1, mxid=14442C10A1E0AECE00, X_LINK_UNBOOTED, X_LINK_USB_VSC, X_LINK_MYRIAD_X, X_LINK_SUCCESS), DeviceInfo(name=1.4, mxid=18443010B1B5711200, X_LINK_UNBOOTED, X_LINK_USB_VSC, X_LINK_MYRIAD_X, X_LINK_SUCCESS), DeviceInfo(name=3.2, mxid=14442C1051EDAECE00, X_LINK_UNBOOTED, X_LINK_USB_VSC, X_LINK_MYRIAD_X, X_LINK_SUCCESS)]

@themarpe Hello. Any news related to the issue?

@SergeyVasilyan do you mind trying the latest library (2.19.1.0) or latest develop branch?

@themarpe  I did the upgrade of 'depthai' library to version 2.19.1.0 and the issue is still reproducible.

@themarpe Hello. Any news related to this issue?

authors: SergeyVasilyan brmarkus themarpe


text:
Remove --ignore-path from eslint config

We currently have --ignore-path set in the eslint hook for git commits. This forces eslint to ignore the .eslintignore file, which is the standard way of specifying files & folders you don't want to be linted.
I was trying to add .eslintignore to my repo and spent a while trying to figure out why my files were still being linted. It's unintuitive to have this flag set by default.
ps. we probably shouldn't be linting the .gitignore file either :P

Thanks for the awesome PR 👍  Could you do the same with the canary branch?

Totally! Sorry I wasn't aware you had two separate production branches.
I'll push a PR up when I have some extra time.

authors: BlakeBrown lvarayut

repo: lvarayut/relay-fullstack


text:
V7  Update

Please update lv_arduino to V7.01, when possible.
Thank you.

I'm waiting for final 7.0.1 release - 7.0.1-dev version is prepared in my repository. Only the first (and siplmest) example is checked because of my limited hardware availability.

Okay. The plan is to release at least a bugfix version every 2 weeks. So v7.0.1 is scheduled to 1 Jun.

@Pablo2048
What do you have to do to release a new Arduino version? If it's possible I can update lvgl's release script to apply some changes in this repo too.

I have to get the new version, check configuration if it's still valid, check at least the simplest example if it still works and if so I have to modify library.json and `library.properties' with new numbers. As I wrote here https://forum.lvgl.io/t/arduino-questions/2405/7?u=pablo2048 I hope that I'll do all this until end of this week.

Would you agree to automatically update library.json on patch releases?
They don't add new features or config options just fixes some bugs.

Okay, no problem with that...

Great! I'll update the script then.

New PR has been created. Can anybody test it (especially with the STM32 example) or should I merge it?


text:
Fix generated headers

The currently generated C file for custom fonts is missing a block at the top to set LV_LVGL_H_INCLUDE_SIMPLE conditionally as is done in the current image converter. This will fail to compile depending on how your include paths are set up as it does for me.
Fixes lvgl/lv_font_conv#116

Thank you!
@richardgazdik Could you update the font converter on our website?


text:
black window after un-minimizing

2022 build tools
win 11 x64
v9.1.1
When LvglWindowDesktopApplication is minimized and then un-minimized the window is black. When the app is then maximized the window recovers.
I also see #71 -- it seems to consume 100% of one of my cpu cores - the memory seems stable.
Thank you -
Scott
Nice project!

I need to do some reproduce work to fix the issue.
Kenji Mouri

Found a solution?

The window needs repainting in full when un-minimizing otherwise only dirty areas will be painted when called.
Maybe use WM_WINDOWPOSCHANGED or similar.

Found a solution?

authors: MouriNaruto VogelPapaFinn nikthefix sdicker8 shiweiping


text:
🛑 Hogwarts Server is down

In e980007, Hogwarts Server (https://hogwarts.liwenduan.com/check) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Hogwarts Server is back up in 7496049.

repo: lwdStudio/lwdStatus


text:
How to modify tls extensions?

Whether you can modify items in the extensions？How to modify?
I find the latest chrome is different in the extensions
But I don't know how to change

I'm also interested in this moment.
is it possible?

please. Can you share how did you complete this issue?

authors: CyberParadise phapntm wish-hiy

repo: lwthiker/curl-impersonate


text:
Docs: add notes on dependencies, fix links

Updates docs (README, INSTALL) with some notes on the required dependencies when using the artifacts outside of the build system.

BTW., at least on my end, on Debian-based systems I need to install nss-plugin-pem to fulfill the libnsspem.so requirement — libnss3 is not enough.

@lwthiker updated, but also please do see the note on nss-plugin-pem above.

curl tries to load both libnssckbi.so and libnsspem.so. Up until now with all my experimentation it was always enough to let it load libnssckbi.so alone. But I guess there are use cases where libnsspem.so is needed as well. I think if that's the case we should add it to the list of dependencies.

authors: lwthiker wrobelda


text:
Cannot create container

#11 Is pretty much an exact description of my issue, only a local build and not the demo server hosted on the website. Same build script always worked in the past so Im not sure the best place to start in determining the cause. Any suggestions?

Look at the output of lxd-demo-server or the lxd log

I'm sorry I meant to update but got sidetracked. I was able to run it successfully after going back to lxd 2.13 from 2.15 (2.14 had been skipped for unrelated issue) Furthermore, once it was up and running and I upgraded back to 2.15 it continued to work. Ive made the 2.13 the default in SharkLinux and the newest version is done via opt-in upgrade (with a notice to build the server first if its wanted on the system) Not my ideal solution but unfortunately too many pressing things right now to give this priority. I read somewhere about a change to the lxd client.. any chance thats a factor?

Nope, lxd-demo-server directly talks to the API, it doesn't use the command line client.

It is consistent anyway, in the same vm setting and install/build script  2.13 passed 5/5 and 2.15 went 0/5. Upgrading lxd afterwards didnt cause any harm. ill have to dig a bit when I have a chance and look a bit closer. Go ahead and close if you'd like

I can't seem to reproduce your problem:
root@lantea:~# snap install lxd
lxd 2.15 from 'canonical' installed
root@lantea:~# lxd init
Do you want to configure a new storage pool (yes/no) [default=yes]?
Name of the new storage pool [default=default]:
Name of the storage backend to use (dir, btrfs, zfs) [default=zfs]:
Create a new ZFS pool (yes/no) [default=yes]?
Would you like to use an existing block device (yes/no) [default=no]?
Size in GB of the new loop device (1GB minimum) [default=21GB]:
Would you like LXD to be available over the network (yes/no) [default=no]?
Would you like stale cached images to be updated automatically (yes/no) [default=yes]?
Would you like to create a new network bridge (yes/no) [default=yes]?
What should the new bridge be called [default=lxdbr0]?
What IPv4 address should be used (CIDR subnet notation, “auto” or “none”) [default=auto]?
What IPv6 address should be used (CIDR subnet notation, “auto” or “none”) [default=auto]?
LXD has been successfully configured.
root@lantea:~# snap install lxd-demo-server
lxd-demo-server git from 'stgraber' installed
root@lantea:~# snap connect lxd-demo-server:lxd lxd:lxd
lxd-demo-server git from 'stgraber' installed

I could then hit http://IP:8080 and get a working session.

Yea, you wouldnt. Doing the old method by building with go.

Ok, closing this for now as there's nothing obviously wrong with LXD or the demo server that I can work on fixing. If you can reproduce this, please attach the output of lxd-demo-server and the LXD log, one of the two should give more details on what's failing.

authors: Shark-Linux stgraber

repo: lxc/lxd-demo-server


text:
Container hangs when exiting from bash

Container hangs when some background job is triggered inside the container and then tried to exit from the container.
Running on Ubuntu 16.04
sudo lxc info lxd-cnt-1071
Name: lxd-cnt-1071
Architecture: x86_64
Created: 2016/06/17 18:52 UTC
Status: Running
Type: persistent
Profiles: default
Pid: 13994
Ips:
eth0:	inet	10.200.3.202	vethE6BH4L
eth0:	inet6	fe80::216:3eff:fedb:be32	vethE6BH4L
lo:	inet	127.0.0.1
lo:	inet6	::1
Resources:
Processes: 20
Disk usage:
root: 643.95MB
Memory usage:
Memory (current): 15.69MB
Memory (peak): 38.77MB
Network usage:
eth0:
Bytes received: 2.78kB
Bytes sent: 1.01kB
Packets received: 18
Packets sent: 10
lo:
Bytes received: 288 bytes
Bytes sent: 288 bytes
Packets received: 4
Packets sent: 4
Steps to reproduce:
sudo lxc exec lxd-cnt-1071 bash
root@lxd-cnt-1071:~# yes >& /dev/null &
[1] 347
root@lxd-cnt-1071:~# exit
exit
The Process is running in the background, but unable to close the terminal, it just hangs up.

Duplicate of #1677

repo: lxc/lxd


text:
How to write .yaml / .sh files to configure and deploy containers similarly to docker recipes (run commands upon container initiation)

How to deploy containers in a similar way to docker recipes.
For example how to:

specify all the container details (shared/mounted devices, network, etc)
specify what commands to run upon initial start

From doing research there appears to be an option to configure the containers using a yaml file: https://askubuntu.com/questions/617865/is-there-a-way-to-configure-lxd-containers-with-cloud-config-at-provision-time
The yaml file was also mentioned in this tutorial under the "Image metadata" heading: https://stgraber.org/2016/03/30/lxd-2-0-image-management-512/
Unfortunately that tutorial did not cover how to deploy the lxc containers using yaml files (and how to format the files).
The above are related to deploying lxd containers as mentioned here: https://stackoverflow.com/questions/44456522/how-to-automate-application-deployment-when-using-lxd-containers

I've noticed the documentation shows the configuration format: https://github.com/lxc/lxd/blob/master/doc/preseed.md
How to specify which commands to run when the container is first created and initiated?

You're welcome to script around "lxc exec" and the various "lxc file" commands. There is however no way in LXD to have it run the equivalent of a DockerFile. Most people will use their own deployment tools for such things, be it Ansible, Puppet, ...
To roll your own thing from a clean host, you could:

Use "lxd init --preseed" to setup the LXD daemon itself
Use "lxc init" rather than "lxc launch" to create the container without starting it
Use "lxc config edit" to apply a full container configuration in one shot (it reads yaml from stdin)
Then start the container and use "lxc exec" to run whatever you want inside of it

The yaml that's valid for "lxc config edit" is the same you'd see when doing "lxc config show" against an existing container.

authors: gregsifr stgraber


text:
do something nicer on setting/unsetting security.privileged

Right now, all this does is flip the bit in the DB. We should either: 1. ideally uidshift the whole fs when the bit is flipped or 2. fail to flip the bit after the fs is initialized so that people don't try and boot a container with e.g. files all owned by root or whatever.

And I guess this gets really complicated when you consider that profiles can affect this as well. Additionally, we should forbid changing this while the container is running (this also suggests a potential solution; remember the uid map the rootfs was created with, and compare it to the boot time uidmap, and if they're different, shift).

Right, so I think the best way to solve this is by:

Introduce a new volatile.last_state.idmap variable which contains a serialized version of our IdMap struct. This will be set every time the container starts.
If at startup, the value of volatile.last_state.idmap differs from the one we're now running with, we'll shift the rootfs.
Idmap on the container struct should also be changed to reflect the current container idmap (parsing volatile.last_state.idmap if set) rather than the next start idmap. This is required to ensure file pull/push uses the right uids/gids.


text:
Testsuite re-org & code style

This re-organizes the test/ directory in prevision for adding support
for the different backing stores.
This is solely about moving files around and updating the code style to
be consistent across all files, no change to the actual code is included
in this commit.
Signed-off-by: Stéphane Graber stgraber@ubuntu.com

I'm +1 on this, works for me, but I can't run the migration tests... @tych0 ?

the migration test fails here in the same way as it did before :)

To be honest, I'm not sure those have worked for a while. I'll take a look, but let's not block merging this on that.

Or, are they failing even when you don't have criu installed?

nah, without criu they pass fine, it's just the criu part which fails as it always did for me.

would be nice if we could get criu 1.7 in the archive and have the tests pass

authors: mikemccracken stgraber tych0


text:
Network: Use volatile VF MAC if VF has no automatic MAC set

Some SR-IOV NICs require setting an explicit VF MAC on the interface before being brought up it seems.
Fixes #8162

Testsuite passed

Testsuite passed

Needs to be updated to avoid potential MAC reuse/conflict issue.

@stgraber removed volatile saving, just using random MACs now as discussed.

authors: lxc-jenkins stgraber tomponline


text:
Update lxc cluster list to show roles instead of boolean database column

Closes #9233

This pull request didn't trigger Jenkins as its author isn't in the whitelist.
An organization member must perform one of the following:

To have this branch tested by Jenkins, use the "ok to test" command.
To have a one time test done, use the "test this please" command.

Those commands are simple Github comments of the format: "jenkins: COMMAND"

jenkins: test this please

@presztak thanks!

authors: lxc-jenkins presztak stgraber


text:
Please capture/return lxd container error logs within stack traces

TL;DR
Please clarify the cause of Failed to load config file errors.

Cheap/easy: "check your lxd container logs".
Harder but more friendly: "your config options are b0rked, here's the b0rk message..."

Version info

pylxd: 2.3.1
Docker OS: Ubuntu 20.04.6 LTS
Host OS: Ubuntu 20.04.5 LTS
LXD version, from snap: 4.0.9

Test case / Detail
from pylxd import Client
client = Client()
c = client.containers.get(name='some-container-you-already-created')
c.config = {'image.architecture': 'x86_64', 'image.description': 'Ubuntu 16.04 LTS server (20180126)', 'image.os': 'ubuntu', 'image.release': 'xenial', 'volatile.apply_template': 'create', 'volatile.base_image': 'f3c173f5595f57c5c8e457f85b20e3a8d62061f49953b38950e928d780d10871', 'volatile.idmap.base': '0', 'volatile.idmap.next': '[{"Isuid":true,"Isgid":false,"Hostid":1000000,"Nsid":0,"Maprange":1000000000},{"Isuid":false,"Isgid":true,"Hostid":1000000,"Nsid":0,"Maprange":1000000000}]', 'volatile.last_state.idmap': '[]', 'volatile.uuid': 'e3402349-6dc1-4b19-ae2c-6ec23cb72b46', 'security.privileged': 'false', 'security.nesting': 'true', 'limits.kernel.rtprio': '99', 'limits.cpu': '0-22,24-46', 'limits.memory': '128849018880', 'limits.memory.swap': 'false', 'raw.lxc': 'lxc.loglevel = 0'}
c.config.update(config)
c.save(wait=True)

The result is the following error:
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/opt/Env/armory-compute-node/lib/python3.8/site-packages/pylxd/models/_model.py", line 225, in save
    self.client.operations.wait_for_operation(response.json()["operation"])
  File "/opt/Env/armory-compute-node/lib/python3.8/site-packages/pylxd/models/operation.py", line 57, in wait_for_operation
    operation.wait()
  File "/opt/Env/armory-compute-node/lib/python3.8/site-packages/pylxd/models/operation.py", line 98, in wait
    raise exceptions.LXDAPIException(response)
pylxd.exceptions.LXDAPIException: Failed to load config file "/tmp/lxd_config_1152857147": loading config file for the container failed

What might actually be the cause of this error? Digging around on the system, I find my container logs, which reveal the real problem:
lxc 20230508160111.718 ERROR    confile - confile.c:set_config_unsupported_key:153 - Invalid argument - Unsupported config key "lxc.loglevel"
lxc 20230508160111.718 ERROR    parse - parse.c:lxc_file_for_each_line_mmap:129 - Failed to parse config file "/tmp/lxd_config_1152857147" at line "lxc.loglevel = 0"

Indeed, once I remove 'raw.lxc': 'lxc.loglevel = 0' from my config, c.save returns.

That would be a great addition! But at first we need to check the output of the LXD REST API in this case - do they give more information about an error 🤔?

authors: greenmoss sirkadirov

repo: lxc/pylxd


text:
No readline.pc in readline 6.2 and 7

Unfortunately, there is no readline.pc file for pkg-config in readline 6.2 and 7.0 (it doesn't seem to be a Fedora/RHEL-specific packaging problem, because Debian Stretch and Buster have exactly the same issue). Given the before mentioned readline versions are part of RHEL 7 and 8, lxi-tools 2.x (the command-line variant) can't be build anymore.

Right. Fixed in d55f9393388aff4b0c63b20f668c451e6c998465

Hopefully one day most/all libraries will carry a pkg-config.

Confirming, commit d55f9393388aff4b0c63b20f668c451e6c998465 builds on all active Fedora and RHEL releases on all architectures.

authors: lundmar robert-scheck

repo: lxi-tools/lxi-tools


text:
Cannot get this to work on demand

I cannot get this extension to work on a consistent basis.  Sometimes I do have vertical tabs but I damned if I know how they got there.  CTRL-E opens up Google search, not vertical tabs.  I can't find a way to access settings, if there are any, and I can't find any USEFUL documentation. A list of features with no indication of how to access them is pretty useless. This whole effort has caused me to waste hours this evening that I did not have to waste, and all I am left with for my effort is a high level of frustration and tabs that I can't see because I can't find a working app to help.
I was a Software/Firmware (embedded) Engineer for almost thirty years so I am not some lame inept user who can't program their way out a paper bag.  However, I have been unable to use this extension in a reasonable fashion.  Great idea, poor execution.

Sometimes I do have vertical tabs but I damned if I know how they got there.

The icon with the eyeballs to the right of the address bar serves as a toggle.  If this is not working then some other extension might be interfering.  Also note that tabs which were open before installing the extension will need to be reloaded.  (This generally applies to any extension which modifies the contents of a loaded tab.)

I can't find a way to access settings

Same way as every other extension (via the "Extensions" menu), or
chrome://extensions/?id=pddljdmihkpdfpkgmbhdomeeifpklgnm

A list of features with no indication of how to access them is pretty useless.

Instructions are on the home page of the repository...
https://github.com/lxieyang/vertical-tabs-chrome-extension
...and in the chrome web store
https://chrome.google.com/webstore/detail/vertical-tabs/pddljdmihkpdfpkgmbhdomeeifpklgnm
If you got this from any place else, uninstall or disable it immediately and report where you found it.

This whole effort has caused me to waste hours this evening that I did not have to waste

I am baffled by your description of this issue and have no problems here.  If refreshing tabs or restarting the browser does not help, can you try installing this extension in the Brave browser (a privacy-focused fork of Chrome) just to see if the issue persists.
https://brave.com/

repo: lxieyang/vertical-tabs-chrome-extension


text:
installs and uses python3 and pip3 on frontproxy service example

installs and uses python3 and pip3 to address Issue #1597
uses ppa:deadsnakes/ppa
fork build passed

Could also incorporate the instructions on https://github.com/docker-library/python/blob/master/3.5/jessie/Dockerfile, though this might be overkill. 😄

Is it possible to add CI for this regression so we don't break again?

We used to have example verification as part of CI but it got commented out due to CI times being too long and flakey. IMO we can live with this situation until we get a better CI that runs faster.

authors: htuch marcosrmendezthd mattklein123

repo: lyft/envoy


text:
求问：fit_ddp方法报ProcessExitedException: process 0 terminated with signal SIGSEGV错误

Ubuntu21.10，Python3.10.12，torchkeras-3.9.4，accelerate-0.23.0_dev0环境
fit_ddp()方法训练时没有问题，每次训练结束后，都会报：ProcessExitedException: process 0 terminated with signal SIGSEGV错误，请问是什么原因呀？

与accelerate有关的问题，请到accelerate仓库下寻求帮助。

收到！谢谢您的回复！
---原始邮件---
发件人: @.>
发送时间: 2023年9月6日(周三) 上午10:07
收件人: @.>;
抄送: @.@.>;
主题: Re: [lyhue1991/torchkeras] 求问：fit_ddp方法报ProcessExitedException: process 0 terminated with signal SIGSEGV错误 (Issue #60)
与accelerate有关的问题，请到accelerate仓库下寻求帮助。
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>


text:
ArgumentError in DeviseTokenAuth::ConfirmationsController#show

We have rails backend and backbone on the front-end. I am trying to use devise_token_auth to work with devise user authentications with tokens.
I have a form on the backbone for new user registration. I am creating a new record in User model and some other records and setting up proper relationships between users and internal objects such as organization etc..
Now users are getting confirmation email. When they click on the link, actual confirmation was successful on the rails side, but I am getting the following error on the backbone side.
I set the following in devise_token_auth.rb initializer file thinking that it needs confirm_succes_url, but it did not help.
  config.default_confirm_success_url = "http://medl.io"

confirmation url looks like this.
http://localhost:4000/auth/confirmation?config=&confirmation_token=ribwBQNszgcxRgrx-6w9

bad argument (expected URI object or URI string)

/Users/medlio/.rvm/rubies/ruby-2.1.2/lib/ruby/2.1.0/uri/common.rb:1234:in `URI'
/Users/medlio/.rvm/gems/ruby-2.1.2/bundler/gems/devise_token_auth-47e8848cf124/lib/devise_token_auth/url.rb:4:in `generate'
/Users/medlio/.rvm/gems/ruby-2.1.2/bundler/gems/devise_token_auth-47e8848cf124/app/models/devise_token_auth/concerns/user.rb:201:in `build_auth_url'
/Users/medlio/.rvm/gems/ruby-2.1.2/bundler/gems/devise_token_auth-47e8848cf124/app/controllers/devise_token_auth/confirmations_controller.rb:22:in `show'```

having the same issue

There might be a better solution or config setup that I'm missing, but I found adding the redirect_url worked for me.
I had generated the devise views myself.
Inside the confirmation link I added the redirect_url as a param.
app/views/devise/mailer/confirmation_email.erb
<%= link_to 'Confirm my account', confirmation_url(@resource, confirmation_token: @token, redirect_url: root_url) %>
This meant that the render didn't collapse when trying to get the redirect_url.

Seems to be a solution here/no activity. Closing for now.

authors: benbencj legolytics lexton zachfeldman

license: WTFPL


text:
configure() should not automatically try to authenticate on backend

It's not flexible enough. Instead it should (imo) only try to authenticate when developer/component requests it. This way configure() only set endpoint url and then redux-auth itself saves user (in any login action) to localStorage with token + token_expire_time.
Right now, redux-auth spams unnecessary authentification event on every page load, not to say it's not even working at this moment. And stubbing "saving" functionality is very hackish now (i try to use it with redux-persist).

@Fedcomp - redux-auth started as something that I needed for a specific project. I plan to make this more flexible and extensible with future releases. My first priority is to make it possible to bypass the backend authentication so that this can be used on native apps. The work on this is mostly finished - I'll release it as soon as I get the time.

This is a duplicate of #7.

It is complete different issues. In #7 you are asked for client side localstorage support. Here i ask to separate two actions, the configure() endpoint, and sending request to reauthenticate.
Right now configure() automatically send request and there's no way to prevent that automatic request.

@Fedcomp - the title of the issue is "Client-only (non-universal) support". In order to accomplish this, I will need to separate the configure and validate phases.
So you're right in that I shouldn't have called this issue a "duplicate". What I meant to say is that this issue will be resolved when #7 is resolved.

authors: Fedcomp lynndylanhurley

repo: lynndylanhurley/redux-auth