text:
pkg, supernode: cleanup code based on static check warning

Signed-off-by: hwdef hwdef97@gmail.com

Ⅰ. Describe what this PR did
cleanup code based on static check warning
Ⅱ. Does this pull request fix one issue?

NONE
Ⅲ. Why don't you add test cases (unit test/integration test)? (你真的觉得不需要加测试吗？)
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report

Merging #969 into master will decrease coverage by <.01%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master     #969      +/-   ##
==========================================
- Coverage   46.48%   46.48%   -0.01%
==========================================
  Files         116      116
  Lines        6908     6906       -2
==========================================
- Hits         3211     3210       -1
+ Misses       3440     3438       -2
- Partials      257      258       +1

Impacted Files
Coverage Δ

supernode/daemon/mgr/cdn/cdn_gc.go
0% <0%> (ø)
:arrow_up:

supernode/daemon/mgr/cdn/reporter.go
8.64% <0%> (ø)
:arrow_up:

supernode/daemon/mgr/cdn/manager.go
20% <0%> (ø)
:arrow_up:

supernode/daemon/mgr/scheduler/manager.go
21.91% <0%> (-0.69%)
:arrow_down:

Continue to review full report at Codecov.

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

LGTM

@hwdef  Where do you find the static check warning? Can you add this feature into our ci?

@yeya24
I use staticcheck.
And I found @SataQiu already added this feature into ci. #809

authors: allencloud codecov-io hwdef yeya24


text:
Comment on agenda items

As a Citizen,
I want to comment on agenda items,
so that My Elected Official and everyone else know what I think about them.

Acceptance criteria:

Any registered user is able to comment on an agenda item.

Acceptance tests:

Navigate to an agenda item on an open meeting as an unregistered user.
Comment on an item - you should be prompted to signup or login.
Try again as a registered user without selecting "pro" or "con"
You should see confirmation that you posted a comment. You should be prompted to share. The border box should be grey if you didn't vote.
Now navigate to a different agenda item.
Vote on it. You should be prompted to comment.
Add a comment.
You should see confirmation that your comment is posted. You should be prompted to share.

source: gharchive/issue

repo: drew-moore/civ-sandbox

license: MIT

license_type: permissive

license_source: github-api


text:
Error while updating ionic cli to 2.1.18 from 2.1.17

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules\ionic\node_modules\chokidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.0.15: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN In ionic@2.1.18 replacing bundled version of cross-spawn with cross-spawn@4.0.2
npm WARN In ionic@2.1.18 replacing bundled version of semver with semver@4.2.0
npm WARN In ionic@2.1.18 replacing bundled version of mime-types with mime-types@2.0.14
npm WARN In ionic@2.1.18 replacing bundled version of form-data with form-data@0.2.0
npm WARN In ionic@2.1.18 replacing bundled version of request with request@2.51.0
npm WARN In ionic@2.1.18 replacing bundled version of ionic-app-lib with ionic-app-lib@2.1.9
npm ERR! Windows_NT 10.0.14393
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Users\Swapnil\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js" "install" "-g" "ionic@2.1.18"
npm ERR! node v4.6.0
npm ERR! npm  v3.10.8
npm ERR! path C:\Users\Swapnil\AppData\Roaming\npm\node_modules.staging\ansi-9c6e29df
npm ERR! code ENOENT
npm ERR! errno -4058
npm ERR! syscall rename
npm ERR! enoent ENOENT: no such file or directory, rename 'C:\Users\Swapnil\AppData\Roaming\npm\node_modules.staging\ansi-9c6e29df' -> 'C:\Users\Swapnil\AppData\Roaming\npm\node_modules\ionic\node_modules\cordova-lib\node_modules\ansi'
npm ERR! enoent ENOENT: no such file or directory, rename 'C:\Users\Swapnil\AppData\Roaming\npm\node_modules.staging\ansi-9c6e29df' -> 'C:\Users\Swapnil\AppData\Roaming\npm\node_modules\ionic\node_modules\cordova-lib\node_modules\ansi'
npm ERR! enoent This is most likely not a problem with npm itself
npm ERR! enoent and is related to npm not being able to find a file.
npm ERR! enoent
npm ERR! Please include the following file with any support request:
npm ERR!     C:\WINDOWS\system32\npm-debug.log
npm ERR! code 1

duplicate of #1805

I am facing same problem.
please respond how to fix it.

repo: driftyco/ionic-cli

license: mit

license_source: bigquery


text:
bug: TypeError: Cannot read property 'index' of undefin

Type: bug
Platform: all
Version : 1.0.0-rc.0
I haven't found a way to reproduce systemically the issue. That's why no codepen is available.
But I managed to get the crash on ios, android and desktop
TypeError: Cannot read property 'index' of undefined
    at Object.IonicModule.factory.register (http://localhost:8100/lib/ionic/js/ionic.bundle.js:42182:44)
    at IonicModule.controller.self.register (http://localhost:8100/lib/ionic/js/ionic.bundle.js:47153:38)
    at updateView (http://localhost:8100/lib/ionic/js/ionic.bundle.js:52331:23)
    at http://localhost:8100/lib/ionic/js/ionic.bundle.js:52308:11
    at Scope.$get.Scope.$broadcast (http://localhost:8100/lib/ionic/js/ionic.bundle.js:22639:28)
    at $state.transitionTo.$state.transition.resolved.then.$state.transition (http://localhost:8100/lib/ionic/js/ionic.bundle.js:40109:22)
    at processQueue (http://localhost:8100/lib/ionic/js/ionic.bundle.js:21108:27)
    at http://localhost:8100/lib/ionic/js/ionic.bundle.js:21124:27
    at Scope.$get.Scope.$eval (http://localhost:8100/lib/ionic/js/ionic.bundle.js:22320:28)
    at Scope.$get.Scope.$digest (http://localhost:8100/lib/ionic/js/ionic.bundle.js:22136:31) undefined

The actual line in code is this one
hist.cursor = viewHistory.currentView.index;
Somehow, currentView is null and the index property is called resulting in the TypeError mentioned above.

Greetings @msevestre!
My sensors indicate that I require more information in order to assist you.

Can you provide a detailed description of this issue?
How would a robot go about replicating this issue?
On which platform does this happen occur? (iOS, Android, all, etc.)
On which platform versions does this occur? (Android 4.2, iOS 8, all, etc.)
Is this an issue with the Ionic Framework or Ionic CLI?

Additionally, providing a codepen that replicates the issue is extremely helpful.
If you wish to get help using the framework itself, I recommended visiting the forum, where many humans will be able to offer wisdom and advice.
Thank you for allowing me to assist you.

Dear @Ionitron,
If only your sensors were a bit more up-to-date, you would see that I mentioned in the text of the very issue that I was not able to replicate the issue for a robot like you.
The issue is there for sure, but appearing only occasionally.
If I find a step by step workflow allowing you to reproduce the bug, I will for sure create a codepen replicating the issue

Can you provide a detailed description of this issue?

Navigating in the application, I suddenly get the error described above. I have also attached the stack trace

How would a robot go about replicating this issue?

If I can figure how a human can replicate the issue, then I am pretty sure that  I'll be able to answer that question

On which platform does this happen occur? (iOS, Android, all, etc.)

ALL (this was also mentioned in the issue... these sensors of yours definitely need some tune up)

On which platform versions does this occur? (Android 4.2, iOS 8, all, etc.)

Android 4.2, ios 7 and ios8. Chrome . I haven't tried anything else

Is this an issue with the Ionic Framework or Ionic CLI?

Ionic framework. I have also highlighted the actual line of code causing the bug

Sorry, but if we can't reproduce the issue, we can't really fix it.  We haven't seen it in any our tests, so it's likely there's an edge case in your app that we don't yet cover.  Can you offer us any more info? Does your state config use resolves? Can you share your code with us so we can set up breakpoints? We need more info.

I experienced this same bug as well.  Produced the exact same call stack. It happened when I clicked a Tab Button. After correcting some bugs with Angular-Cache, I refreshed and haven't seen it ever since.
So yeah, @perrygovier there's no way to fix something you can't replicate. Just wanted to share my own experience because it may have nothing to do with ionic in particular.

Greetings @msevestre!
My sensors indicate a reply was requested, but we have not received one yet, I am using my robot powers to close this issue. However, if you are still experiencing this issue, please feel free to reopen it by creating a new issue, and include any examples or necessary information.
Thank you for allowing me to assist you.

Greetings @msevestre!
My sensors indicate a reply was requested, but we have not received one yet, I am using my robot powers to close this issue. However, if you are still experiencing this issue, please feel free to reopen it by creating a new issue, and include any examples or necessary information.
Thank you for allowing me to assist you.

the bug has disappeared completely. Thanks

I got a similar, also rarely reproducable error:
TypeError: Cannot read property 'index' of undefined
    at Object.register (ionic.bundle.js:51373)
    at self.register (ionic.bundle.js:56692)
    at updateView (ionic.bundle.js:62357)
    at ionic.bundle.js:62334
    at Scope.$broadcast (ionic.bundle.js:29477)
    at $state.transition.resolved.then.$state.transition (ionic.bundle.js:49321)
    at processQueue (ionic.bundle.js:27879)
    at ionic.bundle.js:27895
    at Scope.$eval (ionic.bundle.js:29158)
    at Scope.$digest (ionic.bundle.js:28969)(anonymous function) @

ionic.bundle.js:25642(anonymous function) @ ionic.bundle.js:22421Scope.$broadcast @
ionic.bundle.js:29479$state.transition.resolved.then.$state.transition @
ionic.bundle.js:49321processQueue @ ionic.bundle.js:27879(anonymous function) @
ionic.bundle.js:27895Scope.$eval @ ionic.bundle.js:29158Scope.$digest @
ionic.bundle.js:28969Scope.$apply @ ionic.bundle.js:29263(anonymous function) @
ionic.bundle.js:25398eventHandler @ ionic.bundle.js:16583triggerMouseEvent @
ionic.bundle.js:2948tapClick @ ionic.bundle.js:2937tapTouchEnd @ ionic.bundle.js:3064

My setup contains some views, one side-menu pointing to the views, and a tab control on one of the views.
I get this issue rarely - but sometimes when i navigate between the views using the sidemenu.
Interestingly: When the error occurs once, it seems to get fired every time I switch views, until I reload the app.

@Screeze +1
I don't use resolves

I get this error, too, occasionally.
hist.cursor = viewHistory.currentView.index;
Trying to replicate is proving to be hard.

I have exactly the same problem on Ionic 1.3.1
ionic.bundle.js:26794 TypeError: Cannot read property 'viewId' of undefined
    at Object.register (http://localhost:8100/lib/ionic/js/ionic.bundle.js:54185:30)
    at self.register (http://localhost:8100/lib/ionic/js/ionic.bundle.js:59708:38)
    at updateView (http://localhost:8100/lib/ionic/js/ionic.bundle.js:65398:23)
    at http://localhost:8100/lib/ionic/js/ionic.bundle.js:65375:11
    at Scope.$broadcast (http://localhost:8100/lib/ionic/js/ionic.bundle.js:30718:28)
    at $state.transition.resolved.then.$state.transition (http://localhost:8100/lib/ionic/js/ionic.bundle.js:52157:22)
    at processQueue (http://localhost:8100/lib/ionic/js/ionic.bundle.js:29127:28)
    at http://localhost:8100/lib/ionic/js/ionic.bundle.js:29143:27
    at Scope.$eval (http://localhost:8100/lib/ionic/js/ionic.bundle.js:30395:28)
    at Scope.$digest (http://localhost:8100/lib/ionic/js/ionic.bundle.js:30211:31) undefined

It happens when I quickly click on tab links, I'm wondering if I'm not triggering two state changes at the same time?

authors: Ionitron Screeze blablapolicja corey-garvin msevestre odytrice perrygovier thibaultponcelet

repo: driftyco/ionic


text:
300ms delay on sidemenu swipe?

I have to swipe quite slowly to make the sidemenu appear. So the question is, is there a 300ms delay on this drag? I'm testing on Android 2.3.

Greetings @brauliobo!
My sensors indicate that you need to update your issue through our custom issue form. We are now requiring all issues to be submitted this way, to ensure that we have all of the information necessary to fix them as quickly as possible.
Click Here To Update Your Issue
I will have no choice but to close this issue if it is not resubmitted through the form. Please fill out the rest of the form, so that I may use my friendly robot powers to assist you.
Thank you!

Android 2.3 is no longer supported. There is no 300ms delay, but we require two touchmove events to determine gesture direction before we can know if the user is scrolling or opening the side menu, which happen pretty infrequently on 2.3.

@perrygovier but the strange thing is that with slider I can do very fast movements and it works. could you please indicate where in the code I can patch? I've tried without success.
cc @viniciuscb

authors: Ionitron brauliobo perrygovier


text:
v2 - Ion-input problems

Hi,
i have 2 problems with ion-input.
First the tabindex gets not only set on the wrapped input but also on the ion-input.
These 2 (redundant) tabindex's break form navigation in browsers.
second the angular form validation classes are not set on the wrapped input field, therefore
form validation is not working at all

Hello, thanks for opening an issue with us! Would you be able to provide a plunker that demonstrates this issue? Thanks for using Ionic!

Hello! As it seems it has been a while since there was any activity on this issue i will be closing it for now. Feel free to comment if you are still running into this issue. Thanks for using Ionic!

just because i don't provide a plunkr in time, does not mean you have a bug here

as you can see in this plunkr:
http://plnkr.co/edit/KwRq17cclcrGIM3EMd8y?p=preview
the tabindex gets set on the ion-input tag AND on the input, it should only be on the input.
This is important for ProgesiveWebApp with tab/keyboard support

+1

I confirmed the tabindex is an issue still. However, the form classes should be getting set correctly on ion-item, ion-input and input.

authors: brandyscarney jgw96 nickwinger penrillian-chrisa


text:
Cordova 5 compatibility

I am considering to migrate to Cordova 5 but I have doubts about compatibility issues with Ionic, ngCordova and cordova plugins
Is ngCordova fully compatible with cordova 5?

Yes, ionic and ngcordova are compatible with cordova5.

ok thank u! 👍

authors: anasmithiam mhartington

repo: driftyco/ng-cordova


text:
Correct link to BLE plugin

Edited the link to the BLE plugin that is actually referenced in the ng-cordova source code:
//  install   :   cordova plugin add https://github.com/don/cordova-plugin-ble-central#:/plugin
//  link      :   https://github.com/don/cordova-plugin-ble-central

See Issue #665

Thank you!

source: gharchive/pull-request

authors: dwimberger gortok


text:
Pico W example error linking

I am trying to get the example running on a Pico W, using the instuctions here: https://book.drogue.io/drogue-device/dev/examples/rp2040/pico-w/app/README.html
I am using the "Running with UF2 image" instuctions, and am getting an error on step 3
PS C:\GITRoot\drogue-device\examples\rp2040\pico-w\app> cargo build --release
   Compiling rp2040-pico-w v0.1.0 (C:\GITRoot\drogue-device\examples\rp2040\pico-w\app)
error: linking with `rust-lld` failed: exit code: 1
  |
  = note: "rust-lld" "-flavor" "gnu" "C:\\Users\\Gilbert\\AppData\\Local\\Temp\\rustcknm8GI\\symbols.o" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\rp2040_pico_w-4901ca84cba3eb70.rp2040_pico_w.e1835cce-cgu.0.rcgu.o" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\rp2040_pico_w-4901ca84cba3eb70.rp2040_pico_w.e1835cce-cgu.1.rcgu.o" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\rp2040_pico_w-4901ca84cba3eb70.rp2040_pico_w.e1835cce-cgu.10.rcgu.o" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\rp2040_pico_w-4901ca84cba3eb70.rp2040_pico_w.e1835cce-cgu.11.rcgu.o" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\rp2040_pico_w-4901ca84cba3eb70.rp2040_pico_w.e1835cce-cgu.12.rcgu.o" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\rp2040_pico_w-4901ca84cba3eb70.rp2040_pico_w.e1835cce-cgu.13.rcgu.o" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\rp2040_pico_w-4901ca84cba3eb70.rp2040_pico_w.e1835cce-cgu.14.rcgu.o" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\rp2040_pico_w-4901ca84cba3eb70.rp2040_pico_w.e1835cce-cgu.15.rcgu.o" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\rp2040_pico_w-4901ca84cba3eb70.rp2040_pico_w.e1835cce-cgu.2.rcgu.o" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\rp2040_pico_w-4901ca84cba3eb70.rp2040_pico_w.e1835cce-cgu.3.rcgu.o" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\rp2040_pico_w-4901ca84cba3eb70.rp2040_pico_w.e1835cce-cgu.4.rcgu.o" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\rp2040_pico_w-4901ca84cba3eb70.rp2040_pico_w.e1835cce-cgu.5.rcgu.o" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\rp2040_pico_w-4901ca84cba3eb70.rp2040_pico_w.e1835cce-cgu.6.rcgu.o" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\rp2040_pico_w-4901ca84cba3eb70.rp2040_pico_w.e1835cce-cgu.7.rcgu.o" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\rp2040_pico_w-4901ca84cba3eb70.rp2040_pico_w.e1835cce-cgu.8.rcgu.o" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\rp2040_pico_w-4901ca84cba3eb70.rp2040_pico_w.e1835cce-cgu.9.rcgu.o" "--as-needed" "-L" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps" "-L" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\release\\deps" "-L" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\build\\rp2040-pico-w-78cc776101c1d519\\out" "-L" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\build\\cortex-m-7bcea78665f1282c\\out" "-L" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\build\\cortex-m-rt-a6d3bfd8a9140011\\out" "-L" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\build\\defmt-c50f544e84b25453\\out" "-L" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\build\\embassy-rp-da2508194ddd4bc7\\out" "-L" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\build\\rp2040-pac2-93954b094293253f\\out" "-L" "C:\\Users\\Gilbert\\.rustup\\toolchains\\nightly-2023-02-07-x86_64-pc-windows-msvc\\lib\\rustlib\\thumbv6m-none-eabi\\lib" "-Bstatic" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libembassy_boot_rp-3b8b1b98056898f6.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libserde_json_core-8de27e85733a083a.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libryu-9273cabd98c5b5ec.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libcyw43-fd98b42ede813140.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libnum_enum-eb7f19c44c112c4c.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libcortex_m_rt-27c0a11f7ef31675.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libembassy_usb_logger-c223e127e73dd37f.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\liblog-515917fd7e895b99.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libembassy_usb-8cc0b6e8fb29b6d9.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libusbd_hid-7bddb39af41de508.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libusb_device-668fc9d89a4b396a.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libssmarshal-e24ee174b9cc5922.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libencode_unicode-cda6f2ee663585ca.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libembassy_net_driver_channel-7ce0e155af83d465.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libpanic_probe-2201b8d54e38b3b0.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libembassy_rp-3f07cbb5472bbfac.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libembedded_hal_nb-7c8dc5d0c0eecf02.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\librp2040_pac2-5aeb5d87d9b66b0c.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libembassy_usb_driver-62af0156296510c7.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libembassy_futures-07462db31eea6cf9.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libembassy_cortex_m-7e833fa7853f48a3.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libcortex_m-4a1efc5894d96eda.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libvolatile_register-5397e4c54c66d382.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libvcell-cc695925722ec002.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libbare_metal-19182d66d9d57fca.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libembassy_net-8231b1e3837ae3d1.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libembassy_hal_common-ac156deafc98c0a2.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libnum_traits-a0b286fd76d7eb0c.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libsmoltcp-6bea5b56a754692f.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libmanaged-4d92a2b7cf6f7148.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libembassy_net_driver-e450a8e9ac8805bd.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libembassy_executor-26761d05ccfa2e2d.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libstatic_cell-581f11d4bed0c685.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libatomic_polyfill-eb54b7f80b021395.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libdrogue_device-a9382a2ef1dd0521.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libserde_cbor-d42d296ffae5e068.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libhalf-1bf4418e56556a3d.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libembassy_lora-0e21e299e6872480.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\liblorawan_device-85ca4de1d1cbbdcd.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\liblorawan-e7ce636a378ceed1.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libcmac-15e53291953fd8ae.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libdbl-6ddf2c9f47890198.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libcrypto_mac-951ee3e19f97344c.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libaes-a4819aebeda7f41c.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libaes_soft-a20d761dd1d2794a.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libcipher-3b698eadf6ea90b8.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libreqwless-b28d4f1581dfb09a.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libhex-20365b9949cdb4c6.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libhttparse-c891f178b881d018.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libbase64-bc814efff231f37a.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\librand_chacha-f2504b87d3f23c99.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libppv_lite86-3807ff4d3764d24a.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libnourl-1bf9b3ea0ff80307.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libembedded_tls-5e7189251689931c.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libp256-cee64eb3760cdf95.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libelliptic_curve-9622674f37a4cd65.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libsec1-0d6732b07fd5c174.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libder-9450bbd03f3b5ba7.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libconst_oid-38187427b5b086bd.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libbase16ct-becb22a71342cf81.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libhkdf-4531b668dfb547a3.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libhmac-523b96487a29db4e.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libgroup-050f9e720ce9c797.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libff-04eb6ca35c2417e3.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libcrypto_bigint-afd77ec569cb9424.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libzeroize-77f944e326c4dec1.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libsha2-2cbe9de206567393.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libdigest-0c5e7c5d97600609.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libblock_buffer-71451b236ccee4b7.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libaes_gcm-34bdf003663608dd.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libctr-581e3deb11bc69af.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libghash-6c3952a0e554fd7c.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libpolyval-2255f25cf28edec5.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libopaque_debug-358f5df949a17581.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libuniversal_hash-7333fda156453330.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libsubtle-ec6767d7e1a33b59.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libaes-e8955f6301c2bc7b.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libcfg_if-45ba975d0123ce3a.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libcipher-b6b37ba361dfb4dc.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libinout-d6baa9a5d8e688e0.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libaead-d0d87dabdd13cf16.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libcrypto_common-7a17e2fbb6416bee.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libgeneric_array-0200c28daa1c32b8.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libtypenum-dba814c1846b1a07.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\librand_core-c8a2ca5a4899dc36.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libembassy_time-4f0e7de31241e230.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libembedded_nal_async-c87c1fcac880ae7d.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libno_std_net-d7453722a35b6a86.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libembedded_nal-4e222a2e7565179c.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libno_std_net-2d41bb9545ba1e1f.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libembedded_update-cba816db6179ec43.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libfutures-1ad573b1d5088525.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libpostcard-0ace07cd6fbe384a.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libcobs-b7a611e5f9a2155f.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libserde-734109e47c326acd.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libembassy_embedded_hal-46d730a5d32d7218.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libembassy_sync-d9dcc67bbbc25b5e.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libfutures_util-6da3ee8b17c5a919.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libpin_project_lite-f4faa528038e2075.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libfutures_sink-a63fed04297963e2.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libfutures_task-5925c71374172cb9.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libpin_utils-1d5b75e921cab79b.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libfutures_core-4dd02731fc55c1ce.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libembedded_io-f4b9fc3d4b13bb39.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libheapless-e9c68ec21764af24.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libstable_deref_trait-9abf8ac45dde5995.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libatomic_polyfill-d36699f44c1bc909.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libhash32-4a37903663766a69.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libbyteorder-29ece460041ffc24.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libembedded_hal-2c731d20d9702cf7.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libvoid-9a8a18c9c6f04e76.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libnb-534500f77780a0cc.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libnb-085fa83dbad38f87.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libembassy_boot-c27f564eac7d81a3.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libsignature-7e59badf5219036d.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libembedded_storage_async-33857e4f6ab952fc.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libembedded_storage-be7b8abdd54ae634.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libembedded_hal_async-dd7e6c3f73fae0d2.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libembedded_hal-f66c27e7a9e80743.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libdefmt_rtt-f4d1e9ad9840027e.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libcritical_section-aece1a46de4da6c9.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libcritical_section-e884e0d6a2eaf54a.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libbare_metal-56942ed6ffb41e48.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libdefmt-f242fb94b4100761.rlib" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\libbitflags-fde50d0f756b751d.rlib" "C:\\Users\\Gilbert\\.rustup\\toolchains\\nightly-2023-02-07-x86_64-pc-windows-msvc\\lib\\rustlib\\thumbv6m-none-eabi\\lib\\librustc_std_workspace_core-ccb7dfa5e4c7fdc1.rlib" "C:\\Users\\Gilbert\\.rustup\\toolchains\\nightly-2023-02-07-x86_64-pc-windows-msvc\\lib\\rustlib\\thumbv6m-none-eabi\\lib\\libcore-afe3b1261452b8cb.rlib" "C:\\Users\\Gilbert\\.rustup\\toolchains\\nightly-2023-02-07-x86_64-pc-windows-msvc\\lib\\rustlib\\thumbv6m-none-eabi\\lib\\libcompiler_builtins-ba54ad513026d051.rlib" "-Bdynamic" "--eh-frame-hdr" "-znoexecstack" "-L" "C:\\Users\\Gilbert\\.rustup\\toolchains\\nightly-2023-02-07-x86_64-pc-windows-msvc\\lib\\rustlib\\thumbv6m-none-eabi\\lib" "-o" "C:\\GITRoot\\drogue-device\\examples\\rp2040\\pico-w\\app\\target\\thumbv6m-none-eabi\\release\\deps\\rp2040_pico_w-4901ca84cba3eb70" "--gc-sections" "-O1" "--nmagic" "-Tlink.x" "-Tdefmt.x"
  = note: rust-lld: warning: section type mismatch for .uninit.defmt-rtt.BUFFER
          >>> C:\GITRoot\drogue-device\examples\rp2040\pico-w\app\target\thumbv6m-none-eabi\release\deps\libdefmt_rtt-f4d1e9ad9840027e.rlib(defmt_rtt-f4d1e9ad9840027e.defmt_rtt.9049a59a-cgu.0.rcgu.o):(.uninit.defmt-rtt.BUFFER): SHT_PROGBITS
          >>> output section .uninit: SHT_NOBITS

          rust-lld: warning: section type mismatch for .got
          >>> <internal>:(.got): SHT_PROGBITS
          >>> output section .got: SHT_NOBITS

          rust-lld: warning: section type mismatch for .got.plt
          >>> <internal>:(.got.plt): SHT_PROGBITS
          >>> output section .got: SHT_NOBITS

          rust-lld: warning: section type mismatch for .got
          >>> <internal>:(.got): SHT_PROGBITS
          >>> output section .got: SHT_NOBITS

          rust-lld: error: section '.rodata' will not fit in region 'FLASH': overflowed by 98005 bytes
          rust-lld: error: section '.rodata' will not fit in region 'FLASH': overflowed by 102757 bytes
          rust-lld: error: section '.rodata' will not fit in region 'FLASH': overflowed by 102776 bytes
          rust-lld: error: section '.rodata' will not fit in region 'FLASH': overflowed by 102786 bytes
          rust-lld: error: section '.rodata' will not fit in region 'FLASH': overflowed by 102798 bytes
          rust-lld: error: section '.rodata' will not fit in region 'FLASH': overflowed by 102816 bytes
          rust-lld: error: section '.rodata' will not fit in region 'FLASH': overflowed by 102840 bytes
          rust-lld: error: section '.rodata' will not fit in region 'FLASH': overflowed by 102865 bytes
          rust-lld: error: section '.rodata' will not fit in region 'FLASH': overflowed by 102876 bytes
          rust-lld: error: section '.rodata' will not fit in region 'FLASH': overflowed by 102879 bytes
          rust-lld: error: section '.rodata' will not fit in region 'FLASH': overflowed by 102888 bytes
          rust-lld: error: section '.rodata' will not fit in region 'FLASH': overflowed by 102904 bytes
          rust-lld: error: section '.rodata' will not fit in region 'FLASH': overflowed by 102928 bytes
          rust-lld: error: section '.rodata' will not fit in region 'FLASH': overflowed by 102936 bytes
          rust-lld: error: section '.rodata' will not fit in region 'FLASH': overflowed by 102949 bytes
          rust-lld: error: section '.rodata' will not fit in region 'FLASH': overflowed by 102980 bytes
          rust-lld: error: section '.rodata' will not fit in region 'FLASH': overflowed by 103003 bytes
          rust-lld: error: section '.rodata' will not fit in region 'FLASH': overflowed by 103012 bytes
          rust-lld: error: section '.rodata' will not fit in region 'FLASH': overflowed by 103040 bytes
          rust-lld: error: section '.rodata' will not fit in region 'FLASH': overflowed by 103056 bytes
          rust-lld: error: too many errors emitted, stopping now (use --error-limit=0 to see all errors)

error: could not compile `rp2040-pico-w` due to previous error

It looks like the wifi binary has increased in size. Could you try to make the following changes to the memory.x file?
-  FLASH                             : ORIGIN = 0x10007000, LENGTH = 512K
-  DFU                               : ORIGIN = 0x10087000, LENGTH = 516K
+  FLASH                             : ORIGIN = 0x10007000, LENGTH = 768K
+  DFU                               : ORIGIN = 0x100c7000, LENGTH = 772K

Thanks for that. Changing the memory.x file as suggested got it to build, but it's not running correctly.
I have figured out this line is never completing:
let (net_device, mut control, runner) = cyw43::new(state, pwr, spi, fw).await;

The example is using a slightly outdated cyw43 driver. You might have a better chance if you try the wifi examples from embassy and adapt them to your need:
https://github.com/embassy-rs/embassy/tree/main/examples/rp
https://github.com/embassy-rs/embassy/blob/main/examples/rp/src/bin/wifi_blinky.rs

authors: gilbertbw lulf

repo: drogue-iot/drogue-device


text:
[feature]Add gotify notification support

What's changed?
[feature]Add gotify notification support
#1552
Checklist

[x]  I hereby agree to the terms of the HertzBeat CLA
[ ]  I have read the Contributing Guide
[ ]  I have written the necessary doc or comment.
[ ]  I have added the necessary unit tests and all cases have passed.

Add or update API

[ ] I have added the necessary e2e tests and all cases have passed.

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿

repo: dromara/hertzbeat


text:
Deprecate Makefile

Currently the Makefile assumes that GOPATH is set to a single directory, instead there could be multiple directories it could be set to concatenated with :
https://github.com/drone/drone/blob/master/Makefile#L49
Can the GOPATH be replaced with anything that works also for this case? Thanks!

I'm re-naming the issue. I think the ideal solution would be to make drone go gettable so that we don't need a makefile or scripts that rely on the GOPATH for the build process.

I would suggest fileb0x instead of bindata :)

@tboerger Good suggestion https://github.com/UnnoTed/fileb0x

I'm using https://github.com/gobuffalo/packr lately. Just to put it on the list too.

Thanks, I will definitely check out packr and filebox for drone-ui 😄
For drone/drone we actually don't store any binary assets. They are all text assets related to database queries, migration and templates. So I'm using https://github.com/bradrydzewski/togo
This is a tool of my own creation that handles embedding plain text files as plain text (strings) and generating the relevant template, migration, sql code. This is an example of what generated template code looks like, for those interested:
package template

import "html/template"

// list of embedded template files.
var files = []struct {
	name string
	data string
}{
	{
		name: "en.tmpl",
		data: en,
	}, {
		name: "es.tmpl",
		data: es,
	},
}

// T exposes the embedded templates.
var T *template.Template

func init() {
	T = template.New("_").Funcs(funcMap)
	for _, file := range files {
		T = template.Must(
			T.New(file.name).Parse(file.data),
		)
	}
}

//
// embedded template files.
//

// files/en.tmpl

var en = `<html>
<body>
Hello world
</body>
</html>
`

// files/es.tmpl

var es = `<html>
<body>
Hola Mundo
</body>
</html>
`

merged #2040

authors: appleboy bradrydzewski metalmatze mrueg tboerger

repo: drone/drone


text:
Verification & Validation bug fixes

https://issues.jboss.org/browse/GUVNOR-2632
https://issues.jboss.org/browse/GUVNOR-2631
Few bug fixes and some clean up that hopefully makes the tests easier to read.

@karreiro @manstis When ever you have time, this could use a review.

@manstis Made the base class abstract.

+1 to merge. Thanks @Rikkola

authors: Rikkola manstis

repo: droolsjbpm/drools-wb


text:
Don't report turtle tests as skipped

reporting the thousands of generated tests
as skipped skews the overall "skipped tests"
statistics which is very bad

before the change 25k tests were reported as skipped

turtle tests can be executed using specific property, e.g.
mvn clean test -DrunTurtleTests

Backport of #837.

+1

authors: baldimir psiroky

repo: droolsjbpm/drools


text:
Dictionary leaves out common words

The dictionary oddly leaves out common words like "cow" (tho "cows" seems to be in the dictionary). I recommend including a much broader dictionary step. I would imagine that actual password cracking techniques will go through words in order of assumed commonality. This vastly overestimates the security of passwords that contain words this dictionary set doesn't happen to contain. It would be best to contain a more realistic set of dictionary words.

Yeah, the "English Wikipedia" word list is weird. What dictionary do you think should be used instead?

Well, a list like one of the following might be ideal:

https://github.com/first20hours/google-10000-english
https://www.ef.edu/english-resources/english-vocabulary/top-3000-words/

Well, a list like one of the following might be ideal:

https://github.com/first20hours/google-10000-english
https://www.ef.edu/english-resources/english-vocabulary/top-3000-words/

authors: fresheneesz laughinghan

repo: dropbox/zxcvbn


text:
Security issue

What would be a secure email alias to report a security issue?
Note: would be a nice to set a security policy

@pwntester Thank you very much for raising this issue! 👍
We've added our security policy to this project:
https://github.com/dropwizard/dropwizard/security/policy
Please send your message to dropwizard.committers+security@gmail.com and we'll respond as fast as possible.

Nice, thank you!

authors: joschi pwntester

repo: dropwizard/dropwizard


text:
Graceful Shutdown stops Jetty server

I'm trying to gracefully shutdown my app on TERM signal.
So far my code look like:
public class ServerApplication extends Application<ServerConfiguration> {
    public static void main(String[] args) throws Exception {

        ServerApplication application = new ServerApplication();
        application.run(args);

        Runtime.getRuntime().addShutdownHook(new Thread("SHUTDOWN_HOOK") {
            @Override
            public void run() {
                System.out.println("!!! application is shutting down !!!");
                application.delayShutdown();
                application.stop();
                System.out.println("<---------- Shutdown complete ---------->");
            }
        });
    }

the delayShutdown method will set a boolean to false and sleep for N seconds, i'm doing this in order to make the readiness endpoint of my app fail so that Kubernetes will stop sending traffic to my container.
The code get correctly executed but I've found out that as soon the TERM signal is received Jetty will close the socket and all in new requests will fail and I don't want this, I need for the server to be fully available until the sleep ends.
Running a while true loop with a test curl on TERM will get me:
curl: (7) Failed to connect to localhost port 80: Connection refused
curl: (7) Failed to connect to localhost port 80: Connection refused
curl: (7) Failed to connect to localhost port 80: Connection refused
curl: (7) Failed to connect to localhost port 80: Connection refused

I've tried shutdownGracePeriod with no luck:
server:
  shutdownGracePeriod: 90s

Would really appreciate the community help on this matter, Thank you!

Hi @ltagliamonte-dd
What you are describing is very similar to one of the features that the dropwizard-health library provides.
It configures a delayed shutdown handler with a shutdown wait period. Once Jetty receives the signal to shutdown, the delayed shutdown handler (which is registered as the first handler) is triggered and it immediately sets the app's health status to false and then goes to sleep for the duration of the wait period. During this time, your app instance's health check would be returning an unhealthy status to calls to the /health-check endpoint. Because this is the first shutdown handler, then the rest of Jetty's shutdown process hasn't been triggered yet, so requests should continue to be accepted and processed. The wait period should be configured to be long enough to allow for your app instance to no longer be deemed healthy and to allow for it to finish processing any remaining requests. Once the wait period expires, the shutdown handler wakes up and returns, which allows Jetty to continue the rest of its shutdown process.
You can see the lines of code where the HealthCheckBundle registers the shutdown handler below.
https://github.com/dropwizard/dropwizard-health/blob/master/src/main/java/io/dropwizard/health/core/HealthCheckBundle.java#L79-L84
Does that help?

Thank you @pstackle !!
Will look into this!! Really appreciated.

authors: ltagliamonte-dd pstackle


text:
[Question] Conditionally inject modules

My Component and and application file are getting very large and the same code base serves multiple brands. We want to conditionally inject modules depending on certain config. Is there any way to do this.
Our current code base looks something like this.
public class SupportPortalApplication extends Application<SupportPortalConfiguration> {
...
  private void initializeComponent() {
      if (component == null) {
          component = DaggerSupportPortalComponent.builder()
                  .moduleOne(new ModuleOne())
                  .moduleTwo(new ModuleTwo())
                  .moduleThree(new ModuleThree())
                  .build();
      }
  }

  private void registerEndpoints(Environment environment) {
      environment.jersey().register(component.getResourceModule1());
      environment.jersey().register(component.getResourceModule2());
      environment.jersey().register(component.getResourceModule3());
  }
...
}

@Singleton
@Component(modules = {ModuleOne.class, ModuleTwo.class, ModuleThree.class})
public interface SupportPortalComponent {

    ModuleOne getModuleOne();
    ModuleTwo getModuleTwo();
    ModuleThree getModuleThree();

}

I want to be able to conditionally load module three, along with its routes. It is easy to just remove the  .moduleThree(new ModuleThree()) from the initializeComponent function conditionally but I would need a way to remove it as a module in the SupportPortalComponent. Is there any way to do this?
DropwizardVersion: "1.3.5"
DaggerVersion:"2.29.1"

@joschi Thanks, we are trying. It is a very big project at the moment. Trying to clean it up now.


text:
Project start fails after update to 1.18.0 with custom Dockerfile

Diagnostic: https://gist.github.com/pminf/42da8afc08a62ddf8461a112c0e8fe57

Describe the bug
After updating to 1.18.0 I'm unable to start any of my existing projects. They all fail with
Failed to start foo: container failed to become healthy: err=container /ddev-foo is unhealthy: phpstatus: FAILED /var/www/html: OK mailhog: FAILED

There seems to be a problem with apache:
[pid 1946] (13)Permission denied: AH00023: Couldn't create the mpm-accept mutex (file /var/lock/apache2/mpm-accept-0.1946)
(13)Permission denied: could not create accept mutex

If I'm switching the webserver-type from apache-fpm to nginx-fpm it's starting without problems.
To Reproduce
I'm able to reproduce it in a clean quickstart project (steps: https://ddev.readthedocs.io/en/stable/users/cli-usage/#php-project-quickstart) plus a custom Dockerfile (attached). The Dockerfile seems to make the difference because without it ddev does start without failure.
Expected behavior
Just start within seconds as usual.
Version and configuration information

Host computer OS and Version: Microsoft Windows 10 Pro (Version 10.0.19043 Build 19043) with WSL2 and Ubuntu 20.04
Docker Desktop version: 4.0.1
ddev version information:

DDEV version    v1.18.0
 architecture    amd64
 db              drud/ddev-dbserver-mariadb-10.3:v1.18.0
 dba             phpmyadmin:5
 ddev-ssh-agent  drud/ddev-ssh-agent:v1.18.0
 docker          20.10.8
 docker-compose  1.29.2
 mutagen         0.12.0-beta7
 os              linux
 router          drud/ddev-router:v1.18.0
 web             drud/ddev-webserver:v1.18.0

config.yaml contents for the misbehaving project (the part before the comments):

name: foo
type: php
docroot: web
php_version: "7.4"
webserver_type: apache-fpm
router_http_port: "80"
router_https_port: "443"
xdebug_enabled: false
additional_hostnames: []
additional_fqdns: []
mariadb_version: "10.2"
mysql_version: ""
provider: default
use_dns_when_possible: true
composer_version: "1"

Do you have any custom configuration (nginx, php, mysql) in the .ddev folder? If so, have you tried without them?
Dockerfile (it's working fine without it):

# You can copy this Dockerfile.example to Dockerfile to add configuration
# or packages or anything else to your webimage
ARG BASE_IMAGE=drud/ddev-webserver
FROM $BASE_IMAGE
RUN apt-get update

# basics
RUN apt-get install -y openssl curl dirmngr gnupg2

# basics
RUN apt-get install -y \
    openssl \
    curl \
    dirmngr \
    gnupg2 \
    locales \
    python3-pip

# install RVM, Ruby, and Bundler
# https://stackoverflow.com/questions/61787926/how-can-i-get-sass-compass-into-the-ddev-web-container
RUN apt-get update
RUN DEBIAN_FRONTEND=noninteractive apt-get install -y -o Dpkg::Options::="--force-confold" --no-install-recommends --no-install-suggests build-essential ruby-full rubygems
RUN gem install compass

# Install frontend development tools
RUN npm install grunt grunt-cli \
 && npm install -g \
    grunt \
    grunt-cli \
    gulp

# German locales
RUN sed -i -e 's/# de_DE.UTF-8 UTF-8/de_DE.UTF-8 UTF-8/' /etc/locale.gen \
 && echo 'LANG="de_DE.UTF-8"' > /etc/default/locale \
 && dpkg-reconfigure --frontend=noninteractive locales \
 && update-locale LANG=de_DE.UTF-8
ENV LANG de_DE.UTF-8

# Install Python modules
RUN apt-get install -y \
    python3-pip
RUN pip3 install paramiko

Thanks for chasing this. Looks like we'll have to add something to your Dockerfile.
With a normal apache-fpm, I see this
$ ls -ltd /var/lock/apache2
drwxr-xr-x 2 rfay dialout 4096 Sep 28 08:11 /var/lock/apache2

Yours will obviously have your own user.
Apparently something about your setup is changing that?
You can likely ddev ssh even though it's not becoming healthy and poke around.

The problem is that something you've installed has changed the ownership of /var/lock/apache2 to www-data.
The easiest workaround is probably to add to your Dockerfile chmod 777 /var/lock/apache2. That's not completely correct but probably doesn't matter for this situation.

Thanks for the workaround.
I've reduced the Dockerfile to
ARG BASE_IMAGE=drud/ddev-webserver
FROM $BASE_IMAGE
RUN apt-get update

# basics
RUN apt-get install -y python3-pip

Without the installation of python3-pip it's starting. Don't know how this could be related to apache.

BTW, you'll want to change your "basics" line to use the recommended
RUN DEBIAN_FRONTEND=noninteractive apt-get install -y -o Dpkg::Options::="--force-confold" --no-install-recommends --no-install-suggests
And the first "basics" line is completely redundant - you do all those again with the second one.

Without the installation of python3-pip it's starting. Don't know how this could be related to apache.

Pretty weird. Anyway, you can change the perms and it will work out.
What about if you install something other than python3-pip? Is that the only package that does it?

What about if you install something other than python3-pip? Is that the only package that does it?
I've tested openssl and it does no harm. Seems to be related to python3-pip.

You can likely ddev ssh even though it's not becoming healthy and poke around.

Unfortunately not. SSH fails
Project is stopped.

Glad you're doing OK with it. The way I was getting in there was <ctrl>-c right after the container was started and ddev ssh right then. We could also have turned off the healthcheck.

Here's a working, simplified and updated Dockerfile. It works for me on amd64 Linux, but not on M1 arm64.
ARG BASE_IMAGE
FROM $BASE_IMAGE

# install RVM, Ruby, and Bundler
# https://stackoverflow.com/questions/61787926/how-can-i-get-sass-compass-into-the-ddev-web-container
RUN apt-get update
RUN DEBIAN_FRONTEND=noninteractive apt-get install -y -o Dpkg::Options::="--force-confold" --no-install-recommends --no-install-suggests \
  build-essential \
  ruby-full \
  rubygems \
  openssl \
  curl \
  dirmngr \
  gnupg2 \
  locales \
  python3-pip

RUN gem install compass

# Install frontend development tools
RUN npm install grunt grunt-cli \
 && npm install -g \
    grunt \
    grunt-cli \
    gulp

# German locales
RUN sed -i -e 's/# de_DE.UTF-8 UTF-8/de_DE.UTF-8 UTF-8/' /etc/locale.gen \
 && echo 'LANG="de_DE.UTF-8"' > /etc/default/locale \
 && dpkg-reconfigure --frontend=noninteractive locales \
 && update-locale LANG=de_DE.UTF-8
ENV LANG de_DE.UTF-8

# Install Python modules
RUN pip3 install paramiko

Using this, the /var/lock/apache2 isn't disrupted by whatever was happening.
Note that paramiko does not claim to run on python3 though, http://www.paramiko.org/ - and python2 has been removed from Debian 11 Bullseye.

Oh, I was going to ask why you were having to do that stuff with the locale, since all locales are already installed.
You should be able to just add to your .ddev/config.yaml
web_environment:
- LANG=de_DE.UTF-8

and that should be it. Not sure what the other stuff is you're doing there.

Thank you for optimizing the docker file. I'm not sure if we were aware of the existing locals and the web environment setting. I will talk back to my team mates and check git history.
You can close this ticket by now although I'm still wondering why we hadn't this issue with our custom docker file and ddev 1.17.0.

Yeah, that's pretty odd that v1.18 changed something. And of course I know how things grow over time.
I do think the paramiko being python2 might have had something to do with it, or who knows.

It appears that the base image changed from Debian Buster to Debian Bullseye. We're getting some errors for missing versions (e.g. wkhtmltopdf, which changed from 0.12.5-1 to 0.12.6-1).

The change is listed under caveats for alpha4, alpha3 and alpha2, but is absent in the final release notes.

Thanks so much @mootari - Edited the release notes.  Let me know if you need trouble chasing your particular situation.

All good here, we "fixed" it by adding echo "deb http://deb.debian.org/debian buster main" >> /etc/apt/sources.list :)

authors: mootari pminf rfay

repo: drud/ddev


text:
Support .mysql files for import along with related files, fixes #812, fixes #516

The Problem/Issue/Bug:
OP #812 and #516: People who use backup_migrate like to use .mysql files and the related items. This PR just allows us to import those and their variants as if they were .sql files.
Manual Testing Instructions:
Download a mysql file, maybe from a backup_migrate instance. Use ddev  import-db on it, verify.
Automated Testing Overview:
This adds all variants to TestDevImportDB()
Related Issue Link(s):
#812, #516
Release/Deployment notes:

I'm actually having a few issues with this.

The default export of backup migrate is actually .mysql.gz. I attempt to use gunzip on the command line but I get that the file is "not in gzip format".
When I tell backup_migrate to export a .mysql file, it does so successfully. However, if I already had a DB before, it doesn't appear to bring in the node table. However, this seems to be an issue with backup migrate, which is odd. I'll need to pull a different DB to test with to verify that the import happens correclty and this oddity is more on an incorrect export from backup migrate.

Hmm, the tests do mysql.gz, mysql, mysql.tar.gz, etc. You shouldn't have to unzip. But gzip should let you.
It may be that backup_migrate does not do a "drop table" before bringing stuff in (you can look inside your export).  I think we should be dropping the db on import:  https://github.com/drud/ddev/issues/810 - very important IMO

authors: rfay rickmanelius


text:
fix dimension exclusion

use dimension exclusion list specified in the parseSpec

If my search is correct, this would make only the Kafka firehose factories and IngestSegment use the dimension exclusions. If this PR is really to fix dimension exclusions, then please take a look at the other firehose factories that come stock with druid (or stock extensions) and add their handling as needed.

can we add tests, I remember we had similar problems with excluding timestamp / metrics columns in the regular indexing spec that haunted us for some time. See DataSchemaTest

Can we please add a unit test? Also, I think protobuf parser probably doesn't use dimension exclusions either and probably should at some point

adding a unit test was not trivial due to guice injections and dependency on indexing service modules, have added an integration-test for reIngestion to verify the fix and ingestSegmentFirehose.

protobufParser uses mapParser under the hood, so dimensionExclusions are good there

authors: drcrallen fjy nishantmonu51 xvrl

repo: druid-io/druid


text:
Possible bug in plugin-css with typography tokens

Hello,
I came across an issue with typography tokens today:
So "d.font.display" is an alias for the base typography token "o.font.10".
Both are $type typography.
For some reason, the output of plugin-css breaks up the reference "var(--o-font-10)" letter by letter.
  --d-font-display-0: v;
  --d-font-display-1: a;
  --d-font-display-2: r;
  --d-font-display-3: (;
  --d-font-display-4: `-;`
  --d-font-display-5: -;
  --d-font-display-6: o;
  --d-font-display-7: -;
  --d-font-display-8: f;
  --d-font-display-9: o;
  --d-font-display-10: n;
  --d-font-display-11: t;
  --d-font-display-12: -;
  --d-font-display-13: 1;
  --d-font-display-14: 0;
  --d-font-display-15: );

The same happens to all my typography tokens.
Is this a known bug? Thank you and keep up the amazing work!
Torsten

Here's an input JSON the bug can be replicated with - the token "fontalias" gets transformed into 15 css custom properties.
{
  "bodyText": {
    "$type": "typography",
    "$value": {
      "fontFamily": ["Helvetica", "-system-ui", "sans-serif"],
      "fontSize": "1.5rem",
      "fontStyle": "normal",
      "fontWeight": 400,
      "letterSpacing": 0,
      "lineHeight": 1.5,
      "textTransform": "none"
    }
  },
  "fontalias": {
    "$type": "typography",
    "$value": "{bodyText}"
  }
}

Awesome bug report, and great recreation! Found the issue very easily, and will be pushing a fix to @cobalt-ui/plugin-css. As far as I can tell, this is only a bug in the CSS plugin, but please let me know if it crops up again 🙂

Thank you so much for the quick fix! However, I'm afraid the issue is still popping up in mode-output. Since I can't reopen this one, I'm opening a new issue for it - hope that's ok.

authors: drwpow torstendaeges

repo: drwpow/cobalt-ui


text:
Add lazily evaluated settings

This adds lazily evaluated default settings, with the following API:
class App
  extend Dry::Configurable

  setting :db_adapter, 'postgres'
  setting :db_user, 'root'
  setting :db_password, ''
  setting :db_host, '127.0.0.1'
  setting :db_port, '127.0.0.1'
  setting :db_name, 'development'
  # This \/ \/
  setting :dsn do |config|
    "#{config.db_adapter}://#{config.db_user}:#{config.db_password}@#{config.db_host}:#{config.db_port}/#{config.db_name}"
  end
end

Passing a block with an arity of 0 will still create a nested config as it did before, note that this implementation does not give nested configs access to parent configs, i.e.
class App
  extend Dry::Configurable

  setting :database do
    setting :adapter, 'postgres'
    setting :user, 'root'
    setting :password, ''
    setting :host, '127.0.0.1'
    setting :port, '127.0.0.1'
    setting :name, 'development'
    # This only has access to "sibling" config values, i.e.
    # adapter, user, password, host, port and name
    # it does not have access to any other configs
    setting :dsn do |config|
      "#{config.db_adapter}://#{config.db_user}:#{config.db_password}@#{config.db_host}:#{config.db_port}/#{config.db_name}"
    end
  end

  setting :other_stuff do
    setting :blah
  end
end

This is not working for me, Return nil always. Here's my code:
class App
  extend Dry::Configurable

  setting :api_username
  setting :api_password
  setting :merchant_account
  setting(:environment, ActiveSupport::StringInquirer.new('test')) { |value| ActiveSupport::StringInquirer.new(value.to_s) }
  setting :endpoint do |config|
    "value"
  end
end

#=> App.config.endpoint
#=> nil

What might be going on wrong here? I'm on 0.7.0 of gem.

authors: AMHOL jasdeepsingh

repo: dry-rb/dry-configurable


text:
attempt adding music and sequencing tutorial.

Name of Resource
Music
Description
Porting over my Google docs on music insertion so it's in one place
Which Generation (4/5/Universal)?
Universal
Notes
I don't want to assert anything I submit as final, so feel free to make changes or ask me to edit stuff if need be

Guide looked good, but I merged it early to fix some formatting issues with the <br/> and <u>. The <u> you can do with _ in Markdown.

authors: PlatinumMaster minigameroom


text:
Threading

Features that I'd like to implement that require multiple threads:

[x] proper autorefresh

currently achieved by polling; should use watchdog instead

[ ] controlling termpdf from other programs

navigation without leaving vim
adding citation to current page of document without leaving vim
support for synctex

[ ] opening new files in a running instance of termpdf

view thread busy loops with 100% cpu usage on linux, each instance of termpdf pegging a core completely.
I don't have a mac to test if the same problem happens there.
$ sudo py-spy dump --pid 171809
...
Python v3.9.1 (/usr/bin/python3.9)

Thread 171809 (idle)
    _shutdown (threading.py:1428)
Thread 171813 (idle)
    watch_for_file_change (termpdf.py:1490)
    run (threading.py:892)
    _bootstrap_inner (threading.py:954)
    _bootstrap (threading.py:912)
Thread 171814 (active)
    view (termpdf.py:1530)
    run (threading.py:892)
    _bootstrap_inner (threading.py:954)
    _bootstrap (threading.py:912)
$ sudo py-spy top --pid 171809
...
GIL: 3.00%, Active: 104.00%, Threads: 3

  %Own   %Total  OwnTime  TotalTime  Function (filename:line)
 97.00%  97.00%   11.70s    11.70s   view (termpdf.py:1530)
  4.00%   4.00%   0.380s    0.380s   _shutdown (threading.py:1428)
  3.00%   3.00%   0.170s    0.300s   view (termpdf.py:1529)
  0.00%   0.00%   0.130s    0.130s   is_set (threading.py:531)
  0.00%   0.00%   0.050s    0.050s   watch_for_file_change (termpdf.py:1490)
  0.00% 100.00%   0.000s    12.05s   _bootstrap (threading.py:912)
  0.00% 100.00%   0.000s    12.05s   run (threading.py:892)
  0.00% 100.00%   0.000s    12.05s   _bootstrap_inner (threading.py:954)

It is possible to make the busy loop by removing scr.stdscr.nodelay(True) but that breaks the file_change detection or autorefresh. I have settled on a very small change of waiting on file_change in the loop of view (termpdf.py:1530)
while key == -1 and not file_change.isSet():
    file_change.wait(0.5)
    key = scr.stdscr.getch()

With this change I see cpu usage of a few percent at most, the thread running view idle, not active.
$ sudo py-spy dump --pid 171656
...
Python v3.9.1 (/usr/bin/python3.9)

Thread 171656 (idle)
    _shutdown (threading.py:1428)
Thread 171658 (idle)
    watch_for_file_change (termpdf.py:1490)
    run (threading.py:892)
    _bootstrap_inner (threading.py:954)
    _bootstrap (threading.py:912)
Thread 171659 (idle)
    wait (threading.py:316)
    wait (threading.py:574)
    view (termpdf.py:1530)
    run (threading.py:892)
    _bootstrap_inner (threading.py:954)
    _bootstrap (threading.py:912)

A few notes:

Adding a wait is the smallest change I could make the reduce the cpu usage without rewriting a lot of code
I haven't tried to tune the wait time
Thankfully this change is small enough it's not much of a maintenance burden if the bug is very specific to my setup :-)

view thread busy loops with 100% cpu usage on linux, each instance of termpdf pegging a core completely.
I don't have a mac to test if the same problem happens there.
$ sudo py-spy dump --pid 171809
...
Python v3.9.1 (/usr/bin/python3.9)

Thread 171809 (idle)
    _shutdown (threading.py:1428)
Thread 171813 (idle)
    watch_for_file_change (termpdf.py:1490)
    run (threading.py:892)
    _bootstrap_inner (threading.py:954)
    _bootstrap (threading.py:912)
Thread 171814 (active)
    view (termpdf.py:1530)
    run (threading.py:892)
    _bootstrap_inner (threading.py:954)
    _bootstrap (threading.py:912)
$ sudo py-spy top --pid 171809
...
GIL: 3.00%, Active: 104.00%, Threads: 3

  %Own   %Total  OwnTime  TotalTime  Function (filename:line)
 97.00%  97.00%   11.70s    11.70s   view (termpdf.py:1530)
  4.00%   4.00%   0.380s    0.380s   _shutdown (threading.py:1428)
  3.00%   3.00%   0.170s    0.300s   view (termpdf.py:1529)
  0.00%   0.00%   0.130s    0.130s   is_set (threading.py:531)
  0.00%   0.00%   0.050s    0.050s   watch_for_file_change (termpdf.py:1490)
  0.00% 100.00%   0.000s    12.05s   _bootstrap (threading.py:912)
  0.00% 100.00%   0.000s    12.05s   run (threading.py:892)
  0.00% 100.00%   0.000s    12.05s   _bootstrap_inner (threading.py:954)

It is possible to make the busy loop by removing scr.stdscr.nodelay(True) but that breaks the file_change detection or autorefresh. I have settled on a very small change of waiting on file_change in the loop of view (termpdf.py:1530)
while key == -1 and not file_change.isSet():
    file_change.wait(0.5)
    key = scr.stdscr.getch()

With this change I see cpu usage of a few percent at most, the thread running view idle, not active.
$ sudo py-spy dump --pid 171656
...
Python v3.9.1 (/usr/bin/python3.9)

Thread 171656 (idle)
    _shutdown (threading.py:1428)
Thread 171658 (idle)
    watch_for_file_change (termpdf.py:1490)
    run (threading.py:892)
    _bootstrap_inner (threading.py:954)
    _bootstrap (threading.py:912)
Thread 171659 (idle)
    wait (threading.py:316)
    wait (threading.py:574)
    view (termpdf.py:1530)
    run (threading.py:892)
    _bootstrap_inner (threading.py:954)
    _bootstrap (threading.py:912)

A few notes:

Adding a wait is the smallest change I could make the reduce the cpu usage without rewriting a lot of code
I haven't tried to tune the wait time
Thankfully this change is small enough it's not much of a maintenance burden if the bug is very specific to my setup :-)

authors: dsanson jaeheum


text:
Issues with Depends on

In the following Example:
Disks:
  Disks:
    - DiskId: 2
      DiskIdType: Number
      DriveLetter: F
      PartitionStyle: GPT
      FSFormat: NTFS

FilesAndFolders:
  Items:
    - DestinationPath: F:\ReleaseA\Admin
      Type: Directory
      Ensure: Present
      DependsOn: '[Disk]2'

DependsOn: '[Disk]2' Throws an error and the resource seems to be malformed?  Perhaps this is just user error?

Well, using 'DependsOn' is an issue at the moment. I have solved that but the solution is not yet public. I should have some time to in the evening to write a detailed description of the solution.

The short answer though is that it should either be handled by the composites for DependsOn within a composite, or the DependsOn should be at the Composite level for dependencies between composites.
So I assume it's more of a CommonTasks issue.

No, @gaelcolas, unfortunately it is more a DSC issue doing too many checks on the format if the DependsOn value. I need to go back in the commit history of one of the projects to find the details.
And the more complex the config data gets, the more you need to make dependencies between individual resources defined in different composites.

authors: Br4v3St4rr gaelcolas raandree

repo: dsccommunity/DscWorkshop


text:
Sockets and also Armor

I don't see any base items for armor.  Maybe I missed it, but I couldn't find it.  Also giving items the maximum number of sockets seems to be difficult.  Normal phase blade will start out at 3 (because it's item level 1 by default, but if you change the item level to 99 then the maximum sockets is 5 not 6

agreed with OP. I cant create base weapons with more than 3 sockets :(

Same with war staff
item level 24
max sockets 6
when you save it only have 5 sockets

#101

authors: AmishApplesauce Clintie-The-GIT ryancrunchi spg-stany


text:
Improve Web Vitals Score

https://lighthouse-dot-webdotdevsite.appspot.com//lh/html?url=https%3A%2F%2Fhacknitr.tech

Hey @ankitkumarsamota121 @CIPHERTron
All images based fixes are done. Look for other remaining ones and do
New Report: https://lighthouse-dot-webdotdevsite.appspot.com//lh/html?url=https%3A%2F%2Fhacknitr.tech

We have a good score on the desktop now. We need to work on the mobile score
Have to give a try for PWA and AMP to see if it helps by any chance

We have a good score on the desktop now. We need to work on the mobile score
Have to give a try for PWA and AMP to see if it helps by any chance

repo: dscnitrourkela/project-kiwi


text:
[Feature] Track cumulative number of tests results for each day

Is it possible to display the time series of the cumulative of test results on each day. This will contextualise the positives cases. For example if they are slowing down because the number of test are also slowing down i.e backlog?
The graph can look just like the confirmed cases graph. Just for one to see if the decrease is due to the decrease in test results..per day.

Hey @rendanim we have been working on that, just updated the front page.

Fantastic! Thanks.

authors: rendanim vukosim


text:
Support CPython 3.10, drop CPython 3.5

The final release is expected very soon (2021-10-04)

Number of downloads for Python 3.5 is very low, should be safe to remove it soon.
The majority of users seems to use 3.7 or 3.8.

Is there something I can do to help publish 3.10?

I think it would be nice to not use the python version as part of the pypi wheel tag, e.g. replace cp39-cp39 with py3. Right now when a new version of Python is released, users get a very old version of opendssdirect. This is what happens when I remove the dependency dss_python from opendssdirect:
Installing collected packages: OpenDSSDirect.py
  Attempting uninstall: OpenDSSDirect.py
    Found existing installation: OpenDSSDirect.py 0.2.14
    Uninstalling OpenDSSDirect.py-0.2.14:
      Successfully uninstalled OpenDSSDirect.py-0.2.14
  Running setup.py develop for OpenDSSDirect.py
Successfully installed OpenDSSDirect.py-0.6.1

For what it is worth, I downloaded the 3.9 wheel and renamed the file to dss_python-0.10.7.post1-py3-none-macosx_10_9_x86_64.whl, and it worked in 3.10.

I guess just adding wheels for the released versions shouldn't present any issues. Just remember that we can't replace the wheels without incrementing the version tag.

For what it is worth, I downloaded the 3.9 wheel and renamed the file to dss_python-0.10.7.post1-py3-none-macosx_10_9_x86_64.whl, and it worked in 3.10.

We can't rely on that. The CPython limited API would allow that for CFFI and remove the requirement of building separate wheels -- https://github.com/dss-extensions/dss_python/issues/24 -- but Cython still doesn't support it.
We could consider separating the compiled parts of DSS Python into separate modules -- one for the DSS C-API libraries, one for the CFFI backend, one for the Cython backend (this would be good for conda-forge too) -- and use whatever backend is available during import time. Using the limited API, the CFFI backend would be future-proof for a while.
Yet another option is to add a proper source release for DSS Python that downloads the Pascal binaries and builds everything locally. I never did that because nobody asked so far.
I should finally have more time starting next week (big project ending). I'll send you an email regarding lots of changes that need be integrated soon for the next DSS C-API (a lot besides what's in the master branch there). Probably doesn't make sense to launch the new version during the holiday season, but an alpha or beta would be useful to start testing things.

I guess just adding wheels for the released versions shouldn't present any issues.

Great! This works for me. I wonder if there’s some automated way of doing it for releases.
I think a source release would be good but I’m hesitant because people will have a frustrating experience if things don’t work. But also, right now pip silently downloading a older version of OpenDSSDirect is frustrating too. I wish pip / conda said something like “latest version is XXX, but installing YYY because of these constraints”.
I’m also making some helper classes for OpenDSSDirect that should make it easier to get data in a format that user expect. I’ll make a PR and tag you for review.

I'm also interested in this.  I'm attempting to build dss_python with the latest github version of dss_capi.  I'd be happy to contribute a PR for that if there's any interest.  Is there?

For what it is worth, I downloaded the 3.9 wheel and renamed the file to dss_python-0.10.7.post1-py3-none-macosx_10_9_x86_64.whl, and it worked in 3.10.

@kdheepak Good news: the extension modules were all built with Py_LIMITED_API, including the Windows ones. CFFI turned that on a couple of releases ago.
I downloaded the files (Py 3.9, 64-bit for Windows, Linux and macOS), edited the metadata (at least the WHEEL  file needs to be updated, but updating METADATA and RECORD is good too), renamed the .whls, uploaded them to TestPyPI, and tested them just to be sure. Since everything seems to work, I uploaded to the main PyPI.

I wonder if there’s some automated way of doing it for releases.

I didn't find any specific tool for that, but certainly looks like it could be automated without too much trouble.

I'm attempting to build dss_python with the latest github version of dss_capi. I'd be happy to contribute a PR for that if there's any interest. Is there?

@beroset I can merge some of my local changes for DSS Python and prepare a preview release for the latest public version of DSS C-API.
I'll keep working a bit on finishing my local work on DSS C-API during the holidays. A lot of code has been rewritten, so I might just squash nearly everything before pushing the code and preparing another pre-release for more extensive testing.

Sounds good to me.  Let me know if I can be of any help with this.

Happy New Year!
I just uploaded that first pre-release at https://pypi.org/project/dss-python/0.12.0a1/#files
These use Py_LIMITED_API as before but with the correct options during setup ( --py-limited-api cp36), so a single wheel per platform should work fine from Python 3.6 up to 3.10. For ARM (32 and 64-bit), for the time being, I'm building locally, everything else was migrated to GitHub Actions.
If Cython doesn't work with Py_LIMITED_API yet, it could be worth to create a separate package just for the future Cython backend and keep it optional.
For Anaconda, it seems Python 3.10 support is not there yet, but conda-forge seems OK. conda-build (and boa) is slow (>20 min) and error-prone, so I left the builds disabled. It might be worth adding Actions workflows to handle each platform separately, but I'm fine with building the packages locally when a stable release is ready.

Happy New Year!
I just uploaded that first pre-release at https://pypi.org/project/dss-python/0.12.0a1/#files
These use Py_LIMITED_API as before but with the correct options during setup ( --py-limited-api cp36), so a single wheel per platform should work fine from Python 3.6 up to 3.10. For ARM (32 and 64-bit), for the time being, I'm building locally, everything else was migrated to GitHub Actions.
If Cython doesn't work with Py_LIMITED_API yet, it could be worth to create a separate package just for the future Cython backend and keep it optional.
For Anaconda, it seems Python 3.10 support is not there yet, but conda-forge seems OK. conda-build (and boa) is slow (>20 min) and error-prone, so I left the builds disabled. It might be worth adding Actions workflows to handle each platform separately, but I'm fine with building the packages locally when a stable release is ready.

authors: PMeira beroset kdheepak


text:
Fix log bug in client tool

Fix log bug in client tool.
this close #158

Please describe the detail of this PR, thanks.

authors: MrKingHH jovany-wang

repo: dst-project/dst


text:
[Client] investigate client OOM issue on huge XMark schema

looks like results too many results were fetched in one batch;
thrown in VVM plugin?

not reproducible any more. gone with improvements around ResultCursor.

repo: dsukhoroslov/bagri


text:
🛑 AutosUsados Site is down

In 492c05f, AutosUsados Site (http://www.autosusados.cl/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: AutosUsados Site is back up in 8e637fd.


text:
Dtm grpc java sdk

初始化grpc sdk 项目，添加了 saga grpc 调用。

是否可以不单独开个子项目，把这个集成到dtm-java和dtm-spring中呢。

我调整看看

调整完了，看一下这样是否比较合理一些

authors: groot-guo horseLk

repo: dtm-labs/dtmcli-java


text:
输入是发音单元和音符，未对颤音进行建模

推理时颤音对应的地方，机器声严重；所以输入还应该加入f0曲线对颤音进行建模；

添加基音编码和位置编码，颤音问题解决


text:
Feature：etcd as configuration center

将etcd 作为配置中心:
配置获取策略：
默认拉取etcd中的数据，当etcd 中不存在数据时，将配置文件的数据同步到etcd当中。
已实现功能：
etcd作为配置存储，更新，初始化配置文件到etcd 中。
还需要实现功能点：
存储到etcd中的key value 键值对的粒度根据情况再划分小一些；
接入etcd 的watch 机制 和加入对应的 key value 的version 进行相关版本匹配；
将此方案的配置替换现有实现中的配置加载策略

@春少

authors: dongzl liu-song

repo: dubbogo/arana


text:
"Stateful session" support

This is a broad, open-ended question. When I'm using a tool like ht with an API that requires authentication and several headers, I find myself struggling to manage that state. My best answer is I set environment variables that I use in the URL for the authentication, frequently go back in the shell history to edit URLs etc. If there is a cookie needed it's even more complicated. Same goes for setting non-standard headers.
GUI tools like Insomnia allow managing this in projects which reduces this pain, but requires using a GUI for a task that's (in my experience) a better fit for the terminal.
So here is my question. Is there a reasonable way to implement some kind support for stateful sessions in ht, that's perhaps applied and mutated automatically when found in the current dir? (a bit like a browser). For example:
# .ht.session
base_url: "https://my-test-api.com/api
headers:
  Content-Type: "application/json"
  X-My-Specific-Header: "That value"

auth:
  token: "Bearer d2h5IHdvdWxkIHlvdSB0YWtlIHRoZSB0aW1lIHRvIGRlY29kZSB0aGlz"

and then used like:
$ ht get /v2/user
Using .ht.session
... dump user json ...

The above a very raw demonstration that hopefully communicates the idea - not the concrete proposal itself.
There is of course a fine balance between explicitness and ease of use. Hiding too much information can lead to surprising behavior. But I still feel there could be a reasonable middle ground. Any thoughts?

What you're describing seems to be HTTPie's  --session flag which will be soon supported in ht  😃. See https://github.com/ducaale/ht/pull/25
# make a request and saves any custom headers, auth, and response cookies in `./session.json`
ht --session=./session.json httpbin.org/json x-secret-key:1235678

# include custom headers, auth, and cookies from `session.json` in the next request
ht --session=./session.json httpbin.org/get

oh wow TIL. Thanks! I think this can be closed then.

authors: ducaale sztomi

repo: ducaale/ht


text:
[Feature request] - Add support for UNLOGGED

I'm not sure if this is the right place for it, or if this should go to the main repo. Please advice.
I'm looking to import huge amounts of data from parquet to postgres via duckdb. This seems like the perfect tool for the job. I was looking to see if there's a way that I could use unlogged tables (Unlogged tables disable WAL to significantly improve write speeds).
I tried the following snippets to no avail:
INSTALL postgres;
SET pg_debug_show_queries=true;
SET pg_pages_per_task=10000;
ATTACH 'dbname=mydb' AS mydb (TYPE postgres);
DROP TABLE IF EXISTS mydb.userdata1;
CREATE UNLOGGED TABLE mydb.userdata1 AS FROM (SELECT * FROM 'foo.parquet' LIMIT 0);

However, it seems to simply ignore the UNLOGGED keyword. Is there any possibility to "escape out" to execute native postgresql? I'm happy to do ALTER TABLE ... SET UNLOGGED via native postgresql query as well.
Thanks

Thanks for the suggestion!
I have thought about adding support for a postgres_execute function that allows you to execute arbitrary SQL within Postgres, would that work for you?
e.g.:
CALL postgres_execute('mydb', 'ALTER TABLE userdata1 SET UNLOGGED');

That would absolutely work fine, and very much in line with what I was hoping/expecting. It would not be practical for duckdb to expose every single SQL feature. Where there are gaps between the different SQL dialects, going down to native SQL would be absolutely perfect.

Implemented in https://github.com/duckdb/postgres_scanner/pull/193

authors: Mytherin ketan-mck


text:
Migrate to sorted PPs

Task/Issue URL:
Description
Stacked PR migrating existing plugins to sorted plugins
Steps to test this PR
Smoke test que parts of the app with sorted plugins

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

develop

#4155

#4156   👈

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @aitorvs and the rest of your teammates on  Graphite

repo: duckduckgo/Android


text:
GHA: Notify Mattermost

Task/Issue URL:
Description
Steps to test this PR
Feature 1

[ ]
[ ]

UI changes

Before
After

!(Upload before screenshot)
(Upload after screenshot)

#5274  👈
develop

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @malmstein and the rest of your teammates on  Graphite


text:
Repo item (video) record does not render correctly in item list

Repo item (video) record does not render correctly in item list

Resolved.  i element was not properly closed for the video icon

repo: dulibrarytech/exhibits-backend


text:
When an email with attachment is send, it keeps on creating duplicate emails in "Email messages"

Hi,
When I send a mail with attachment and when I check the "Email messages" section on cyphon, I could see duplicate emails created twice every minute with the same subject name.

I have uploaded the SS, I there a possible solution for this issue?

Hi @sajeeshgit, this can happen when the Celery task is not able to empty the inbox before the next task interval starts. Try increasing the interval in your config/cyphon/settings/base.py file to see if that resolves the issue, e.g.:
CELERYBEAT_SCHEDULE = {
    'get-new-mail': {
        'task': 'tasks.get_new_mail',
        'schedule': timedelta(seconds=60)
    },
    ...
}

@lhadjchikh thank you for the response, I solved the issue by deleting the mail with attachment at the source; reason for doing this was I want the mail fetch intervals as minimum as possible.

Ok. You might want to double check your settings, though, to make sure the attachment was allowed:

``

authors: lhadjchikh sajeeshgit

repo: dunbarcyber/cyphondock


text:
Test don't run through on branch main on Windows

  test\Spec\LocallyClosed.hs:49:57:
  1) All examples are locally closed, All examples are locally closed., Examples in examples/icfp\ParsimoniousFilter.duo are locally closed, Could not load examples.
       DEFAULTFILELOC:1:1-1:1
       Other error: Wrong module declaration: Found declaration ICFP.ParsimoniousFilter in module icfp.ParsimoniousFilter

  To rerun use: --match "/All examples are locally closed/All examples are locally closed./Examples in examples/icfp\\ParsimoniousFilter.duo are locally closed/Could not load examples./"

  test\Spec\LocallyClosed.hs:49:57:
  2) All examples are locally closed, All examples are locally closed., Examples in examples/icfp\Icfp22example.duo are locally closed, Could not load examples.
       DEFAULTFILELOC:1:1-1:1
       Other error: Wrong module declaration: Found declaration ICFP.Icfp22example in module icfp.Icfp22example

  To rerun use: --match "/All examples are locally closed/All examples are locally closed./Examples in examples/icfp\\Icfp22example.duo are locally closed/Could not load examples./"

  test\Spec\TypeInferenceExamples.hs:30:37:
  3) ExampleSpec, All the programs in the "test/Counterexamples/" folder can be parsed., The counterexample test/Counterexamples/subsumption\CE_056a.duo can be parsed, Can be parsed
       predicate failed on: Left (ErrOther (SomeOtherError <loc> "Wrong module declaration: Found declaration Subsumption.CE_056a in module subsumption.CE_056a\n") :| [])

  To rerun use: --match "/ExampleSpec/All the programs in the \"test/Counterexamples/\" folder can be parsed./The counterexample test/Counterexamples/subsumption\\CE_056a.duo can be parsed/Can be parsed/"

  test\Spec\TypeInferenceExamples.hs:30:37:
  4) ExampleSpec, All the programs in the "test/Counterexamples/" folder can be parsed., The counterexample test/Counterexamples/subsumption\CE_056b.duo can be parsed, Can be parsed
       predicate failed on: Left (ErrOther (SomeOtherError <loc> "Wrong module declaration: Found declaration Subsumption.CE_056b in module subsumption.CE_056b\n") :| [])

  To rerun use: --match "/ExampleSpec/All the programs in the \"test/Counterexamples/\" folder can be parsed./The counterexample test/Counterexamples/subsumption\\CE_056b.duo can be parsed/Can be parsed/"

  test\Spec\TypeInferenceExamples.hs:30:37:
  5) ExampleSpec, All the programs in the "test/Counterexamples/" folder can be parsed., The counterexample test/Counterexamples/subsumption\CE_056c.duo can be parsed, Can be parsed
       predicate failed on: Left (ErrOther (SomeOtherError <loc> "Wrong module declaration: Found declaration Subsumption.CE_056c in module subsumption.CE_056c\n") :| [])

  To rerun use: --match "/ExampleSpec/All the programs in the \"test/Counterexamples/\" folder can be parsed./The counterexample test/Counterexamples/subsumption\\CE_056c.duo can be parsed/Can be parsed/"

  test\Spec\TypeInferenceExamples.hs:30:37:
  6) ExampleSpec, All the programs in the "test/Counterexamples/" folder can be parsed., The counterexample test/Counterexamples/subsumption\CE_056d.duo can be parsed, Can be parsed
       predicate failed on: Left (ErrOther (SomeOtherError <loc> "Wrong module declaration: Found declaration Subsumption.CE_056d in module subsumption.CE_056d\n") :| [])

  To rerun use: --match "/ExampleSpec/All the programs in the \"test/Counterexamples/\" folder can be parsed./The counterexample test/Counterexamples/subsumption\\CE_056d.duo can be parsed/Can be parsed/"

  test\Spec\TypeInferenceExamples.hs:30:37:
  7) ExampleSpec, All the programs in the "test/Counterexamples/" folder can be parsed., The counterexample test/Counterexamples/subsumption\CE_056e.duo can be parsed, Can be parsed
       predicate failed on: Left (ErrOther (SomeOtherError <loc> "Wrong module declaration: Found declaration Subsumption.CE_056e in module subsumption.CE_056e\n") :| [])

  To rerun use: --match "/ExampleSpec/All the programs in the \"test/Counterexamples/\" folder can be parsed./The counterexample test/Counterexamples/subsumption\\CE_056e.duo can be parsed/Can be parsed/"

  test\Spec\TypeInferenceExamples.hs:30:37:
  8) ExampleSpec, All the programs in the "test/Counterexamples/" folder can be parsed., The counterexample test/Counterexamples/subsumption\CE_056f.duo can be parsed, Can be parsed
       predicate failed on: Left (ErrOther (SomeOtherError <loc> "Wrong module declaration: Found declaration Subsumption.CE_056f in module subsumption.CE_056f\n") :| [])

  To rerun use: --match "/ExampleSpec/All the programs in the \"test/Counterexamples/\" folder can be parsed./The counterexample test/Counterexamples/subsumption\\CE_056f.duo can be parsed/Can be parsed/"

  test\Spec\Prettyprinter.hs:40:25:
  9) Prettyprinted work again, All the examples in the "examples/" folder can be parsed after prettyprinting., The example examples/icfp\ParsimoniousFilter.duo can be parsed after prettyprinting., Can be parsed again.
       DEFAULTFILELOC:1:1-1:1
       Other error: Wrong module declaration: Found declaration ICFP.ParsimoniousFilter in module icfp.ParsimoniousFilter

  To rerun use: --match "/Prettyprinted work again/All the examples in the \"examples/\" folder can be parsed after prettyprinting./The example examples/icfp\\ParsimoniousFilter.duo can be parsed after prettyprinting./Can be parsed again./"

  test\Spec\Prettyprinter.hs:40:25:
  10) Prettyprinted work again, All the examples in the "examples/" folder can be parsed after prettyprinting., The example examples/icfp\Icfp22example.duo can be parsed after prettyprinting., Can be parsed again.
       DEFAULTFILELOC:1:1-1:1
       Other error: Wrong module declaration: Found declaration ICFP.Icfp22example in module icfp.Icfp22example

  To rerun use: --match "/Prettyprinted work again/All the examples in the \"examples/\" folder can be parsed after prettyprinting./The example examples/icfp\\Icfp22example.duo can be parsed after prettyprinting./Can be parsed again./"

Randomized with seed 1251141567

Finished in 0.8428 seconds
552 examples, 10 failures

The problem is case insensitivity on Windows. The ICFP.Foo path gets normalized to icfp.Foo on Windows, and this is incompatible with the module ICFP.Foo declaration in the file.

@skingo You know best which line of code to modify :)

authors: BinderDavid construxting

repo: duo-lang/duo-lang


text:
🛑 Mention Robot is down

In 15ff209, Mention Robot (https://backend.isbotdown.com/bots/mentionrobot) was down:

HTTP code: 200
Response time: 117 ms

Resolved: Mention Robot is back up in 809a98c.

repo: durof/status


text:
🛑 Mention Test Bot is down

In 791e945, Mention Test Bot (https://backend.isbotdown.com/bots/mentiontestbot) was down:

HTTP code: 200
Response time: 116 ms

Resolved: Mention Test Bot is back up in 1e154a5.


text:
🛑 Mention Bot is down

In db320a8, Mention Bot (https://backend.isbotdown.com/bots/mentionbot) was down:

HTTP code: 200
Response time: 155 ms

Resolved: Mention Bot is back up in 7c60c28.


text:
🛑 Mention Robot is down

In b75746d, Mention Robot (https://backend.isbotdown.com/bots/mentionrobot) was down:

HTTP code: 200
Response time: 154 ms

Resolved: Mention Robot is back up in 544e3d3.


text:
🛑 Mention Robot is down

In 2306bca, Mention Robot (https://backend.isbotdown.com/bots/mentionrobot) was down:

HTTP code: 200
Response time: 161 ms

Resolved: Mention Robot is back up in 1aec10f after 1 hour, 22 minutes.


text:
🛑 Mention Robot is down

In 5e03fd5, Mention Robot (https://backend.isbotdown.com/bots/mentionrobot) was down:

HTTP code: 200
Response time: 155 ms

Resolved: Mention Robot is back up in d57ec16 after 1 hour, 18 minutes.


text:
🛑 Mention Test Bot is down

In 131bdff, Mention Test Bot (https://backend.isbotdown.com/bots/mentiontestbot) was down:

HTTP code: 200
Response time: 86 ms

Resolved: Mention Test Bot is back up in 648aa01.


text:
🛑 Mention Bot is down

In c75c416, Mention Bot (https://backend.isbotdown.com/bots/mentionbot) was down:

HTTP code: 200
Response time: 89 ms

Resolved: Mention Bot is back up in 7281169 after 2 hours, 46 minutes.


text:
🛑 Mention Test Bot is down

In bab45e9, Mention Test Bot (https://backend.isbotdown.com/bots/mentiontestbot) was down:

HTTP code: 200
Response time: 86 ms

Resolved: Mention Test Bot is back up in d6c175e after 1 hour, 36 minutes.


text:
Something just broke

I have problem i tried to reinstall league but it doesnt works...
Help me pls!

Looks like something broke mid update. Network maybe. Either way this will fix it.
https://github.com/dustinblackman/Championify/blob/master/FAQ.md#the-app-opens-with-a-white-box-infinite-loops-i-just-see-the-background-or-nothing-happens

authors: TimeToFlash dustinblackman

repo: dustinblackman/Championify


text:
Cleanup gulp output

Is there any way to have this kind of messages removed from the output when you run gulp analyze?
ESLint found no problems in 1 file

Obviously you only want this in case there is no problem.

Looked over the docs at gulp-eslint and didn't see anything obvious to ignore that. There is a reporter option to consolidate found no problems in all files to a single line.
Might be worth filing a feature request over there.

Apparently this comes from the eslint-path-formatter project (see https://github.com/Bartvds/eslint-path-formatter/blob/master/index.js#L212). Thanks for helping.

authors: dustinspecker verheyenkoen

repo: dustinspecker/generator-ng-poly


text:
什么时候支持TypeScript或者提供d.ts文件

什么时候支持TypeScript或者提供d.ts文件

@LeungManwei 其实 dva 现在已经支持 ts 了，因为底层使用的工具 atool-build 已经支持了，跟 dva 本身无关系，所以如果你要使用，参照 typescript 的官网说明（你既然要用，你肯定也清楚的）直接使用即可，只不过现在还没有对应的demo

@nikogu 跑起来是没啥问题，就是引用的时候提示缺少库，又不象手动写d.ts文件~。然后是，现在是刚刚准备把现有项目由es6+redux+antd转成ts+dva+antd这样子，但是ts是刚接触所以不太懂。有没有其他的办法解决缺少库这个提示问题呢。

@LeungManwei 看看提示信息呢

@nikogu 提示信息就是 " Cannot find module 'dva'. "

@LeungManwei 我稍后添加个 demo 好了

还有就是less文件的引入。。。也会提示这个问题。

@nikogu 好的，thx

@LeungManwei https://github.com/dvajs/dva/tree/add-ts-example/examples/count-ts 可以先看下

@nikogu thx，我研究看下

@LeungManwei 后续会给dva 添加 index.d.ts文件，就直接用 typings 安装即可，现在还没搞

同样期待 index.d.ts 这样, 这用在webstorm 上自动提示太有用了.

希望能有个完整的demo

已在 dva@1.1 支持，脚手架：https://github.com/sorrycc/dva-boilerplate-typescript 。

authors: LeungManwei nikogu sorrycc wenzhihong2003 zihuxinyu

repo: dvajs/dva