Fix the NPE issue for null callerData

Fix the NPE issue for null callerData

fix for the issue https://github.com/Moocar/logback-gelf/issues/44


Discussion: Source of truth for existing infrastructure

Is your feature request related to a problem? Please describe.
As a user I want to be able to utilize Lyra on existing infrastructure without hassle or jumping through hoops to ensure a local state exists first.
Describe the solution you'd like
As a user I want Lyra to be able to apply state to existing infrastructure and treat the cloud infrastructure API response as the source of truth on a first run.
Describe alternatives you've considered
Leave existing functionality as is, but provide an option (configuration or CLI or both) to allow users to specify where they want their source of truth to exist

Lyra doesn't dictate a "source of truth" today. There's a mapping from the internal ID (derived from the manifest) to the external ID that appoints a remote resource but the "source of truth" is always the external resource.
Can you provide a concrete example that explains what the effect of using the proposed CLI option would be?

Closing this as no new info was provided.


Document how to use a non-superuser postgres

This makes it easier to work with this project on linux.

LGTM. Verified locally that losing the comments in db/schema.sql makes no difference to the database.


Bug 2096509: [release-4.11-compatibility] add attributes to few components

this commit adds a few attributes to help find them in the tests
cherry pick #239

/approve
/lgtm


Added option for default Name tagging

Description
By default, the module applies a "Name" tag and sets propagate_at_start to true with no option, to disable such behaviour. I have added an option to override this hardcoded part.
Motivation and Context
I am using triggers and a lambda function to give newly created instances a Name tag, which is a combination of ASG name and instance ID. I cannot achieve this with having the tag hardcoded.
Breaking Changes
No changes as the newly introduced variable default to the current behaviour. Only if one sets it to false, new changes apply.
How Has This Been Tested?

[ ] I have updated at least one of the examples/* to demonstrate and validate my change(s)
[ ] I have tested and validated these changes using one or more of the provided examples/* projects
[ x ] I have executed pre-commit run -a on my pull request

thank you, but this is not a change that we're going to accept


[Bug]: .status.volume is missing after Update to 3.x

Contact Details
<EMAIL_ADDRESS>What happened?
After Update to 3.x the object Status.Volume is missing.
Adapter Version
3.0.3
JS-Controller Version
4.0.24
Node JS Version
v16.19.0
NPM Version
8.19.3
Operating System
Debian
Relevant log output
No response
Anything else?
No response

Please use ...player.volume


Modify DirectML_ESRGAN's default adapter selection.

Modify DirectML_ESRGAN sample to by default try NPU first then retry GPU. If adapter specified through param, stay with the specified param.

@microsoft-github-policy-service agree company="Microsoft"

This isn't the right logic to filter adapters correctly, because you can't rely on name substrings to be consistent across hardware. Specifying a substring to match with the adapter description is only a convenience for users that want to select between adapters they've already enumerated and seen the description of. For example, on one of my desktops I get the following adapter descriptions:
Adapter[0]: NVIDIA GeForce RTX 4080 (SELECTED)
Adapter[1]: Intel(R) UHD Graphics 770
Adapter[2]: Microsoft Basic Render Driver

With your logic, it would try to find "NPU" and fail to match any adapter. Then it would try to find "GPU" and also fail to find any adapter. QC happens to use "GPU" and "NPU" in their adapter descriptions, but this isn't generically true.
If you want to the sample to prioritize NPU then you have to look for GENERIC_ML adapters that don't support graphics. Then, if that fails, you fall back to the first adapter that is at least supporting CORE_COMPUTE or GRAPHICS.
The logic in this sample already has fallback for D3D feature level, and you'd just want to modify it to also check for DXCORE_ADAPTER_ATTRIBUTE_D3D12_GRAPHICS or similar. You might reference this code too: https://github.com/microsoft/DirectML/blob/master/Samples/DirectMLNpuInference/main.cpp

@jstoecker I have made updates accordingly. Could you take a look? Thanks!


rename licenese dependencies file

rename licenese dependencies file.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: k3255:x: mikyung-leeYou have signed the CLA already but the status is still pending? Let us recheck it.


Unable to add light strip

What issue do you have? Please be as thorough and explicit as possible.
Trying to get the Homebridge-govee plugin to recognize my new H6171 light strip. However, it keeps throwing an error that the "bluetooth-hci-socket" package is missing. Tried to install it manually via the "npm install @abandonware/bluetooth-hci-socket" command in the Homebridge UI terminal. But that didn't resolve anything.
Details of your setup.

Do you use (1) Homebridge UI-X (2) Homebridge CLI or (3) HOOBS?
Homebridge UI-X

Which version of Homebridge/HOOBS do you have?
1.5.0

Which platform do you run Homebridge/HOOBS on (e.g. Raspberry Pi/Windows/HOOBS Box)? Please also mention your version of Node.js/NPM if known.
Synology NAS / Node.js version 16.17.1

Which version of this plugin (homebridge-govee) do you have? Has the issue started since upgrading from a previous version?
Version 6.0.4

Which Govee devices do you have that are causing issues? Please include product models if applicable.
H6171

Please paste any relevant logs below.

[10/15/2022, 6:43:01 PM] [Govee] HTTP/AWS clients enabled as Govee username and password provided.
[10/15/2022, 6:43:01 PM] [Govee] Disabling API client as API key not provided.
[10/15/2022, 6:43:01 PM] [Govee] Disabling BLE client as Cannot find package '@abandonware/bluetooth-hci-socket' imported from /volume1/homebridge/node_modules/homebridge-govee/lib/platform.js at new NodeError (node:internal/errors:387:5).
[10/15/2022, 6:43:01 PM] [Govee] [Outdoor Strip Lights] [92:33:CD:37:34:32:36:02] will not be added to Homebridge unless configured and bluetooth enabled in config.

Can you paste the output from running
npm install @abandonware/bluetooth-hci-socket
in the homebridge terminal?

Sure thing. Here you go...
npm ERR! code 1
npm ERR! path /volume1/homebridge/node_modules/@abandonware/bluetooth-hci-socket
npm ERR! command failed
npm ERR! command sh /tmp/install-2cda634d.sh
npm ERR! Failed to execute '/volume1/@appstore/homebridge/app/bin/node <EMAIL_ADDRESS>build --fallback-to-build<EMAIL_ADDRESS>--module_name=bluetooth_hci_socket --module_path=/volume1/homebridge/node_modules/@abandonware/bluetooth-hci-socket/lib/binding --napi_version=8 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v93' (1)
npm ERR! node-pre-gyp ERR! install response status 404 Not Found on https://github.com/abandonware/node-bluetooth-hci-socket/releases/download/0.5.3-8/bluetooth_hci_socket-0.5.3-8-node-v93-linux-x64.tar.gz
npm ERR! gyp ERR! build error
npm ERR! gyp ERR! stack Error: not found: make
npm ERR! gyp ERR! stack     at getNotFoundError (/volume1/@appstore/homebridge/app/lib/node_modules/npm/node_modules/which/which.js:10:17)
npm ERR! gyp ERR! stack     at /volume1/@appstore/homebridge/app/lib/node_modules/npm/node_modules/which/which.js:57:18
npm ERR! gyp ERR! stack     at new Promise ()
npm ERR! gyp ERR! stack     at step (/volume1/@appstore/homebridge/app/lib/node_modules/npm/node_modules/which/which.js:54:21)
npm ERR! gyp ERR! stack     at /volume1/@appstore/homebridge/app/lib/node_modules/npm/node_modules/which/which.js:71:22
npm ERR! gyp ERR! stack     at new Promise ()
npm ERR! gyp ERR! stack     at subStep (/volume1/@appstore/homebridge/app/lib/node_modules/npm/node_modules/which/which.js:69:33)
npm ERR! gyp ERR! stack     at /volume1/@appstore/homebridge/app/lib/node_modules/npm/node_modules/which/which.js:80:22
npm ERR! gyp ERR! stack     at /volume1/@appstore/homebridge/app/lib/node_modules/npm/node_modules/isexe/index.js:42:5
npm ERR! gyp ERR! stack     at /volume1/@appstore/homebridge/app/lib/node_modules/npm/node_modules/isexe/mode.js:8:5
npm ERR! gyp ERR! System Linux 4.4.180+
npm ERR! gyp ERR! command "/volume1/@appstore/homebridge/app/bin/node" <EMAIL_ADDRESS>"build" "--fallback-to-build"<EMAIL_ADDRESS>"--module_name=bluetooth_hci_socket" "--module_path=/volume1/homebridge/node_modules/@abandonware/bluetooth-hci-socket/lib/binding" "--napi_version=8" "--node_abi_napi=napi" "--napi_build_version=0" "--node_napi_label=node-v93"
npm ERR! gyp ERR! cwd /volume1/homebridge/node_modules/@abandonware/bluetooth-hci-socket
npm ERR! gyp ERR! node -v v16.17.1
npm ERR! gyp ERR! node-gyp -v v9.0.0
npm ERR! gyp ERR! not ok
npm ERR! node-pre-gyp ERR! build error
npm ERR! node-pre-gyp ERR! stack Error: Failed to execute '/volume1/@appstore/homebridge/app/bin/node <EMAIL_ADDRESS>build --fallback-to-build<EMAIL_ADDRESS>--module_name=bluetooth_hci_socket --module_path=/volume1/homebridge/node_modules/@abandonware/bluetooth-hci-socket/lib/binding --napi_version=8 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v93' (1)
npm ERR! node-pre-gyp ERR! stack     at ChildProcess. (/volume1/homebridge/node_modules/@abandonware/bluetooth-hci-socket/node_modules/@mapbox/node-pre-gyp/lib/util/compile.js:89:23)
npm ERR! node-pre-gyp ERR! stack     at ChildProcess.emit (node:events:513:28)
npm ERR! node-pre-gyp ERR! stack     at maybeClose (node:internal/child_process:1093:16)
npm ERR! node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (node:internal/child_process:302:5)
npm ERR! node-pre-gyp ERR! System Linux 4.4.180+
npm ERR! node-pre-gyp ERR! command "/volume1/@appstore/homebridge/app/bin/node" <EMAIL_ADDRESS>"install" "--fallback-to-build"
npm ERR! node-pre-gyp ERR! cwd /volume1/homebridge/node_modules/@abandonware/bluetooth-hci-socket
npm ERR! node-pre-gyp ERR! node -v v16.17.1
npm ERR! node-pre-gyp ERR! node-pre-gyp -v v1.0.10
npm ERR! node-pre-gyp ERR! not ok
npm ERR!

Synology uses a proprietary (I think) OS called DiskStation Manager.


Comparing Skopeo and Crane for our use case

We need to better understand if using Skopeo or Kranke would allow us to better replicate images src->dst.
Uses Cases

[ ] Programmable, can be used as an SDK
[ ] Configuration can be done via API
[ ] Move OCI Artifacts
[ ] Remapping Artifacts (programmatically)
[ ] Image Consistency Verification (was it really pulled correctly, is it present)
[ ] Memory and CPU consumption on low end devices, Disk consumption
[ ] Dealing with Low bandwidth networks, resume, etc.

Relevant documentation comparing Skopeo and Crane can be found under docs/skopeo-vs-crane.md


use search as query to load field

fixes: https://github.com/Azure/azure-sdk/issues/3847
demo: https://vhvb1989.github.io/azure-sdk/?search=purview
(use a new browser window or private, as the js script is cache by the browser)

I added a bonus commit ( I can revert it if you don't like it or want it ).
It adds a button next to the search field whenever there's an input. If the button is clicked, an URL+search-query is copied to clipboad.
This way you can produce a shareable link whenever you want instead of doing tedious manual manipulation.


Add retry to verify user authorization using OSS API

Added retry to handle random failures when checking user authorization.

Fixes https://github.com/Azure/azure-sdk-tools/issues/6275


IntelliJ variables broken

The latest update (6.13.0) broke the IntelliJ variables.
In my case, $random.integer(70000000, 99999999) returns the value "78741155.22521658".
It looks like a float number will be generated instead of an integer.

Sorry, I accidentally deleted the implementation. I overlooked the difference to $random.float and combined the two methods. Oops. I have now added tests.


Filewatcher doesn't seem to work on Windows

Hello,
I am using react native on Windows 7 64bit, deploying an Android app on a real device (not using an emulator).
Everything works fine, the JS bundle gets loaded an all BUT any changes I make to the js files won't show up on the app.
I can force the app to reload the JS bundle but still the js files that get loaded seem to be the very original ones, without any of the changes I make.
One thing I noticed is that the packager does not output anything new on its log whenever I make modifications to the js files (not even on 'index.android.js' !!!)
I understand that watchman is NOT being used by the sane filewatcher on Windows. So whatever it is sane is using, it is not working on my system.
When I start the packager I can see things like these on the log:
<START> Crawling File System
...
<END>   Crawling File System (432596ms)

The crawler takes quite a while to do its job, but still it seems to finish its tasks just fine without timing-out or producing any errors.
But still if I make modifications to the 'index.android.js' the packager won't pick them up and reloading the js bundle on the app will show the original version everytime.
I consider this to be a VERY important issue since I am forced to run the command react-native run-android and this takes a while.
Some people has reported this on stackoverflow:
http://stackoverflow.com/questions/35670753/react-native-cant-see-changes-to-my-code
... so at least I can see I am not the only one.
By the way, I don't know if this issue could be related to: https://github.com/facebook/react-native/issues/6318
Any info you may request from my configuration to resolve this, please let me know.
Alex

What version of react-native and node are you using? Also just to make sure, if you open http://localhost:8081/index.android.bundle?platform=android&dev=true&hot=false in your browser when the packager is running can you see you code changes?

Hello!
I have found out what is going on.
The watcher being used (NodeWatcher on Windows) is working fine.
But I can see 2 problems:

The first one is that crawling the files/folders takes too long on my system (around 5 minutes) so the MAX_WAIT_TIME time is reached. That is fine but me -as a user- had no means of realizing this was happening since the packager was not reporting this error to me. The error should be reported by the packager, mentioning the MAX_WAIT_TIME variable so people running react-native for the first time can know how to fix this situation.

NodeWatcher does emit 'change' events on files even before it finishes crawling all folders (so even before the 'ready' event is emitted). This is VERY useful on slow machines like mine (not having to wait until the WHOLE folder structure is crawled!).
But looking at the node-haste FileWatcher class I can see that events from watchers are ONLY listened to and emitted up to the caller when ALL watchers are 'ready'. Could this be changed?
So on the '_createWatcher' block, instead of having:

function _createWatcher(rootConfig) {
  var watcher = new WatcherClass(rootConfig.dir, {
    glob: rootConfig.globs,
    dot: false
  });

  return new Promise(function (resolve, reject) {
    var rejectTimeout = setTimeout(function () {
      return reject(new Error(timeoutMessage(WatcherClass)));
    }, MAX_WAIT_TIME);

    watcher.once('ready', function () {
      clearTimeout(rejectTimeout);
      resolve(watcher);
    });

  });
}

... could we have something like this?
function _createWatcher(rootConfig) {
  var watcher = new WatcherClass(rootConfig.dir, {
    glob: rootConfig.globs,
    dot: false
  });
  var _this = this;

  return new Promise(function (resolve, reject) {
    var rejectTimeout = setTimeout(function () {
      return reject(new Error(timeoutMessage(WatcherClass)));
    }, MAX_WAIT_TIME);

    watcher.once('ready', function () {
      clearTimeout(rejectTimeout);
      resolve(watcher);
    });

    watcher.on('all', function () {  // args = (type, filePath, root, stat)
      for (var _len = arguments.length, args = Array(_len), _key = 0; _key < _len; _key++) {
        args[_key] = arguments[_key];
      }
      return _this.emit.apply(_this, ['all'].concat(args));
    });

  });
}

As you can see I have added the watcher.on('all', listener there right after the 'ready' listener.
This way the change events will be emitted even before the watchers have finished crawling the folders.
I have no idea if this is the right way of doing but on systems like mine it would be VERY helpful.
Best regards,
Alex

Hey Alex, thanks for the detailed report. I agree we could really improve the messages here to make sure it is clear what is going on. Not sure why the NodeWatcher is that slow on your system, it takes around 30sec on mine. You can also try watchman alpha for windows I had no issues using it and the packager starts in ~10sec https://facebook.github.io/watchman/docs/install.html.
As for improving the messages would you be down to submit a pull request implementing something like you linked in the above post?

Hello,
Thanks for the advice. I installed watchman and I noticed a significant improvement on speed!
Watchman only takes a few seconds to crawl the folders in comparison to those 5 minutes NodeWatcher takes on my system.
... but... the app reports an error when I reload the JS bundle (note that if I use NodeWatcher I can reload the bundle just fine!)
See error being reported:

By the way, I'll submit a pull request on node-haste filewatcher file since there are a few improvements that can be done (one of them is to do with the fact that the timeout error is silently swallowed by the promise code block meaning that the user never gets to see the error reported on the packager log).
Alex

This is an issue for me as well. The packager seemed to be working before, but on 0.23 it does not refresh the js. Crawling the filesystem always took me about 170 - 200 sec. so that's not workable.
I'm on win10 using git bash.
$ node -v
v5.9.1
 $ react-native -v
react-native-cli: 0.2.0
react-native: 0.23.1

android/app/build.gradle
compile "com.android.support:appcompat-v7:23.0.1"

will try out watchman or something

https://github.com/facebook/react-native/issues/6674

I just downloaded the binary on their site and put it somewhere in my PATH.

Hi there! This issue is being closed because it has been inactive for a while.
But don't worry, it will live on with ProductPains! Check out its new home: https://productpains.com/post/react-native/filewatcher-doesnt-seem-to-work-on-windows
Product Pains has been very useful in highlighting the top bugs and feature requests:
https://productpains.com/product/react-native?tab=top
Also, if this issue is a bug, please consider sending a pull request with a fix.

i am having the same issue, packager logs nothing when i save changes made to file and nothing changes on reloading the app both on emulator or the device

node_modules/react-native/packager/react-packager/src/Server/index.js
~line 86
const bundleOpts = declareOpts({
  forceRebuild: {
    type: 'boolean',
    default: false,
  },

~ line 443
const building = !options.forceRebuild && this._bundles[optionsJson] || this.buildBundle(options);

~line 558
forceRebuild: this._getBoolOptionFromQuery(urlObj.query, 'forceRebuild', false),

I know just how bad this is, but nothing else come to mind.
Right now I'm profiling an existing app, so I don't mind rebuilding manually.
I suppose you can mix https://github.com/thomasfl/filewatcher with http://gnuwin32.sourceforge.net/packages/wget.htm to touch that URL automatically.

I am facing the same issue right now and have no fixes so far
@Silviu-Marian  I can't find the path you mentioned, there's no packager folder in node_modules/react-native/
Development OS: Win 7
react-native-cli: 2.0.1
react-native: 0.47.1
node-v: 6.11.2
npm -v: 3.10.10
yarn --version: 0.27.5
device android version:6.0.1

any solutions to this yet?


ts_web_test reports Mismatched anonymous define() module but can't tell where it comes from

We should improve the error messaging here, right now the user just falls into a pit...
/cc @caeruskaru

I published that small repro and am looking for next step.
The bundle contains
//build_bazel_rules_typescript/examples/testing/bad.js
eval("(function (factory) {\n    if (typeof module === \"object\" && typeof module.exports === \"object\") {\n        var v = factory(require, exports);\n        if (v !== undefined) module.exports = v;\n    }\n    else if (typeof define === \"function\" && define.amd) {\n        define([\"require\", \"exports\"], factory);\n    }\n})(function (require, exports) {\n    \n    exports.__esModule = true;\n    exports.a = 1;\n});\n\n//# sourceURL=http://concatjs/base/build_bazel_rules_typescript/examples/testing/bad.js\n");

this has a #sourceURL comment which would be nice to include in the error message.
Looking at the stack at this location, it seems like some higher frame should have the context including the source file being evaluated, which would give us access to the filename. We should be able to patch the version of require.js used by ts_web_test to do this.
Ran out of time for now...


Sleep Timer disappeared

Existing Issues

[X] I have searched for existing issues, this is not a duplicate.

Unmodded Twitch

[X] I have checked and this issue only occurs using bttv-android and not with the unmodded Twitch App

What happened?
in the latest version, the Sleep Timer icon disappeared
bttv-android version
v0.35.0-beta
android version
13
device
Pixel 6
Anything else?
No response

I noticed that the sleep timer work correctly with vods, the only place that is missing is during livestreams


Add Semantic UI Transformer

This PR addresses #5 with support for Semantic UI
Also, updated the README with instructions

Beautiful!! Thank you!!


Add some minimum info or pointers on how what licence to choose

Unless I have missed it, there seems to be very little (none?) info in the starter kit on what licence to choose.
At minima it would be nice to point to the Turing way page: https://the-turing-way.netlify.app/reproducible-research/licensing/licensing-data.html

I remember Chris G having a super strong opinion about CC0 for data. Are there any constraints on data licences if you want to be part of OpenNeuro? Feels important to highlight if so?

I remember Chris G having a super strong opinion about CC0 for data. Are there any constraints on data licences if you want to be part of OpenNeuro? Feels important to highlight if so?

I remember Chris G having a super strong opinion about CC0 for data. Are there any constraints on data licences if you want to be part of OpenNeuro? Feels important to highlight if so?

Good point if some of the data repository have some constraints then it should probably be highlighted.
I know GIN has none but this might not be the case everywhere.

I remember Chris G having a super strong opinion about CC0 for data. Are there any constraints on data licences if you want to be part of OpenNeuro? Feels important to highlight if so?

Good point if some of the data repository have some constraints then it should probably be highlighted.
I know GIN has none but this might not be the case everywhere.

This is an important point and I think it would be helpful to point out that this has to be considered at the stage of consent: https://open-brain-consent.readthedocs.io/en/stable/

This is an important point and I think it would be helpful to point out that this has to be considered at the stage of consent: https://open-brain-consent.readthedocs.io/en/stable/

Regarding OpenNeuro licenses, we only use a CC0 license for sharing data. In our FAQ we describe why we do not allow a CC-BY (or other CC licenses)

Regarding OpenNeuro licenses, we only use a CC0 license for sharing data. In our FAQ we describe why we do not allow a CC-BY (or other CC licenses)


[libxml2] Add link libraries for target LibXml2::LibXml2

Describe the pull request

What does your PR fix? Fixes #14468
Target LibXml2::LibXml2 is not linked against all necessary libraries in vcpkg-cmake-wrapper.cmake. Target LibXml2::LibXml2 should link with Iconv, Charset, lzma, zlib, ws2_32 (windows only) libraries.

I think still LIBXML2_LIBRARIES is not populated correctly.
The missing libraries should first be added to LIBXML2_LIBRARIES variable
and then target LibXml2::LibXml2 should link with this variable.

Due to libiconv and libcharset don't create lib on Linux, so it need not link to them when CMAKE_SYSTEM_NAME STREQUAL "Linux". I think this handle is correct.

Due to libiconv and libcharset don't create lib on MACOS, I think this shoule be changed to:
    list(APPEND LIBXML2_LIBRARIES ${LIBLZMA_LIBRARIES} ${ZLIB_LIBRARIES})
    if(CMAKE_SYSTEM_NAME STREQUAL "Linux")
        list(APPEND LIBXML2_LIBRARIES m)
    elseif(CMAKE_SYSTEM_NAME STREQUAL "Windows")
        list(APPEND LIBXML2_LIBRARIES ${ICONV_LIBRARIES} ${CHARSET_LIBRARIES} ws2_32)
	endif()
	if(TARGET LibXml2::LibXml2)
        target_link_libraries(LibXml2::LibXml2 INTERFACE ${LIBXML2_LIBRARIES})
    endif()

Replaced by #14588.


fix Reset Pin ctrl for sx1276

according to datasheet of sx1276, the Reset Pin should be Low for at least 100 us, and High or Input (High Impedance ) and wait for more than 5 ms.
In current code, I event cannot read correct SX1276 Version Reg correctly (0x00 returned)

Sorry I found I set wrong device tree pin ctrl.


Blacklist not working as expected

Description:
When we create a blacklist policy and click on the button ' Blacklist ' it works as expected , but if we press 'enter' on keyboard, we have the following error :

Solution
Handle the enter key press event when adding a Blacklist Policy.

Fixed via WUM


Functionality - openURL

daemon - request page, open page

try to use seperate window in order to require active_tab permission only instead of all tabs

currently using background session

Fixed with static URLs and linear followup


Badger 2040 display when connecting

https://github.com/pimoroni/badger2040/blob/879f04435ede2b7607522a0c34656debad52451b/firmware/PIMORONI_BADGER2040W/lib/badger2040.py#L232-L242
The 2040w is hard coded to take over the display when connecting, Could this be an option to light the LED or similar user defined action.
Example use case
Showing latest information from a website could look like
while True:
    display.keepalive()
    variables = get_data()
    draw_page(variables)
    sleep_for(10)

After waking up from sleep, the wifi needs to be connected again, taking ~10 seconds, so every 10 minutes, for 10 seconds the badge doesnt display the intended content. A user defined option could be doing an update partial to the screen or lighting the LED.

I have a similar use case. I'm using wifimgr.py and modified it to work on badger. My approach Is to render the text in the top of the screen and then call display.partial_update(0, 0, WIDTH, 24).
I also use the LED as an indicator of activity:
while True:
    display.keepalive()
    display.led(128) # brighter LED
    render() # this does the data fetching and drawing
    display.led(6) # dimmed LED (on USB)
    badger2040.sleep_for(10) # on battery the LED goes completely off during sleep

That status handler code is quite bad on two accounts- the print() is not always desirable either.
Normally this is solved by passing in a custom handler when constructing NetworkManager, but this choice has been lost via the badger lib. I'll raise a PR to fix it.

Perfect, I have done something similar to @salimhb for now (though still using the config file rather than adding wifi creds in again.
Would be happy to test anything!

Okay, test build here - https://github.com/pimoroni/badger2040/actions/runs/5421334513
Now you can use:
display.connect(status_handler=None)

Or define your own status handler in user code:
def status_handler(mode, status, ip):
        print(mode, status, ip)

display.connect(status_handler=status_handler)

Yeah works well for me, I have added a comment on the PR though as the method still causes unexpected behaviour.
Thanks for the super quick fix!

This was resolved by the PR


Gradle daemons caching certs is unclear to troubleshoot

Running gradle prior to cert updates end up caching the old certs, and is difficult to troubleshoot if you don't know that it's happening.

FWIW, this happened again today during a new hire onboarding.

FWIW, this is still an issue.

While I can understand this is confusing, the Gradle daemon runs inside a JVM. If you update environmental settings that a running JVM does not detect as changed, it is unlikely we will add this monitoring to the daemon itself.


Hide the right-nav when the heading list is empty

Example: https://docs.docker.com/docker-for-mac/multi-arch/

No longer applies.


TAJO-1400: Add TajoStatement::setMaxRows method support

I implemented the setMaxRows and getMaxRows method support.
Please review my patch.
thanks.

Thank you for your contribution.
I'll review the patch today. :)

Would you add some unit tests?
TestTajoJDBC will be good to add tests.

Ok, jihoonson,
I'll update the TestTajoJDBC for unit tests of this issue soon.

+1
Thanks for your contribution!

@hys9958
How do you think that move the setMaxRows() to TajoStatement ?

@jinossy thanks for the good suggestion.
It would be a better implementation.

@jinossy Ok, It's better idea.
I'll re-patch the implementation of maxRows(). :)

@hys9958 thanks. I'll wait for the next patch.

Hi @jihoonson ,
Query return value is 'java.sql.ResultSet' interfase in TajoStatement. It need to many refactoring.
And i'll also another patch about getMoreResults. When the getMoreResults patch time, i update maxRows.

Ok. Here is my +1.
If there are no objections, I'll commit.


Do dependency download using zig and out-of-tree build

zig fetch of X will place it in the zig-cache based on its hash, like ~/.cache/acton/o/12200d0c15f2b64854e0f3cb450bd781eadf42b2fd69ebe75d6df45b9e72d93af9a9. We should be able to fetch an Acton repo too, that doesn't yet have a build.zig, because it will be generated later.
zig fetch tells us the hash, so we can record this in build.act.json, and thus have a permanent record of the hash that subsequent builds can read.
We can then generate a build.zig and place in the cache dir. This is probably not kosher, but what else can we do? Anyway, it'll probably work I reckon. We need to do a actonc build to generate .ty files and more importantly the .h and .c. Again we write this to the cache dir and it'll not be kosher but whatev. From there, I believe this acton project located in the cache will actually look correct, so all we need to do is include this from our main acton project and it should be able to do a out-of-tree build for it!?!?!?

We now support other external Acton projects as dependencies in an Acton project. As I envisioned in this issue, we do indeed use Zig to download external projects / packages into the Zig global cache but we cannot run acton build there. Not sure why, but it just fails the build somehow.
My current workaround is to do the zig download and we save the hash, so we know it, then we copy the package from the cache to deps/foo where foo is the dependency name. From there, it can be properly built. There is one benefit to this strategy in that we can easily edit the dependency if that's what we want.
We should improve this but it's not super high priority to do it right now. I think #1847 is next thing to check out in order to implement proper out-of-tree builds.

Support was added with #1862. Closing this.


mac-29 lost external connection from phone device.

Type of Request
bug
Infrastructure Environment
LUCI, Github, Cocoon scheduler, Autosubmit, etc...
What is happening?
mac-29 lost external connection from phone device.

Steps to reproduce
Step 1:
Step 2:
..
Step n:
Expected results
I expect to see X when Y is finished.

Rebooting both machine and phone device to restore connection.


Delay in displaying properties panel when dragging/clicking on a component

Steps to reproduce the behavior:

Go to 'https://function-adminportal-test.shesha.dev/shesha/forms-designer?id=201875fd-ad55-4364-a08b-fd7607023968'
Drag and drop a component and check the properties panel
Click any existing component and check the properties panel
Actual Results: The properties panel delays to display the properties

Expected behavior
The properties should display immediately from dragging/clicking the components

Hi @hlayisanimazuze. The performance has been improved after the latest refactoring , please check


fix(lint): Fix lint issues

We make python style matter updated and we got new lint errors

Codecov Report

Merging #122 (c977f9d) into master (0d5f7d8) will increase coverage by 0.17%.
The diff coverage is 75.00%.

@@            Coverage Diff             @@
##           master     #122      +/-   ##
==========================================
+ Coverage   96.58%   96.75%   +0.17%
==========================================
  Files          29       34       +5
  Lines        1581     1603      +22
==========================================
+ Hits         1527     1551      +24
+ Misses         54       52       -2

Impacted Files
Coverage Δ

Arbie/Actions/trader.py
98.80% <0.00%> (ø)

Arbie/Variables/trades.py
100.00% <100.00%> (+4.54%)
:arrow_up:

Arbie/__main__.py
96.87% <100.00%> (ø)

Arbie/Contracts/__init__.py
100.00% <0.00%> (ø)

Arbie/__init__.py
100.00% <0.00%> (ø)

Arbie/Services/__init__.py
100.00% <0.00%> (ø)

Arbie/Variables/__init__.py
100.00% <0.00%> (ø)

Arbie/Actions/__init__.py
100.00% <0.00%> (ø)

Arbie/Actions/pool_finder.py
96.15% <0.00%> (+0.96%)
:arrow_up:

Continue to review full report at Codecov.

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


EWF format

I was testing some files/images and seems that it doesn't handle E01/L01 (EnCase) or .AD1 (FTK) files.
I know that the EWF (Expert Witness Compression Format) is open-source and could be implemented into the software using the lib https://github.com/libyal/libewf.
The implementation of this support would be good to avoid changing metadata when staging information, if an inadvertent user uses copy instead of robocopy (or any forensic moving tool) or an antivirus takes place, it could mess with the metadata. L01s can be used as a container to preserve this metadata.

Consider structuring it as optional, because it is an LGPL license which will force the people to open source their code, and FreeEed is Apache license, which is business-friendly.


[appShell] ERROR { Error: Uncaught (in promise): ReferenceError: System is not defined

Versions
<!--
ng --version                                                                         1m ⇡ master :: 15h :: ⬡ ⬡ v8.9.4 (npm:5.7.1) (⚓ )

    _                      _                 ____ _     ___
   / \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|
  / △ \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | |
 / ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | |
/_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|_____|___|
               |___/

Angular CLI: 1.7.3
Node: 8.9.4
OS: darwin x64
Angular: 5.2.9
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, platform-server, router
... service-worker

@angular/cdk: 5.2.4
@angular/cli: 1.7.3
@angular/flex-layout: 5.0.0-beta.13
@angular/material: 5.2.4
@angular-devkit/build-optimizer: 0.3.2
@angular-devkit/core: 0.3.2
@angular-devkit/schematics: 0.3.2
@ngtools/json-schema: 1.2.0
@ngtools/webpack: 1.10.2
@schematics/angular: 0.3.2
@schematics/package-update: 0.3.2
typescript: 2.7.2
webpack: 3.11.0

macOS High Sierra 10.13.3

Repro steps
changed .anngular-cli.json to have a second app that should be rendered during build time and precompile a route in the index.html to be used as app shell.
  "apps": [
    {
      "appShell": {
        "app": "ngu-app-shell",
        "route": "user/login"
      },
      "root": "src",
      "outDir": "dist/client",
      "assets": [
        "assets"
      ],
      "index": "index.html",
      "main": "main.ts",
      "polyfills": "polyfills.ts",
      "test": "test.ts",
      "tsconfig": "tsconfig.app.json",
      "testTsconfig": "tsconfig.spec.json",
      "prefix": "ba",
      "serviceWorker": true,
      "styles": [
        "styles.scss"
      ],
      "scripts": [],
      "environmentSource": "environments/environment.ts",
      "environments": {
        "dev": "environments/environment.ts",
        "prod": "environments/environment.prod.ts"
      }
    },
    {
      "name": "ngu-app-shell",
      "root": "src",
      "outDir": "dist/server/",
      "assets": [
        "assets"
      ],
      "platform": "server",
      "index": "index.html",
      "main": "main.server.ts",
      "test": "test.ts",
      "tsconfig": "tsconfig.server.json",
      "testTsconfig": "tsconfig.spec.json",
      "prefix": "ba",
      "styles": [
        "styles.scss"
      ],
      "scripts": [],
      "environmentSource": "environments/environment.ts",
      "environments": {
        "dev": "environments/environment.ts",
        "prod": "environments/environment.prod.ts"
      }
    }
  ],

The problem is that in my main component app.component.ts i have this:
  ngOnInit() {
    this.authenticated$.subscribe(authenticated => {
      if (authenticated === false) {
         this.router.navigate(['user/login']);
      }
    });
  }

What I can tell is that if I remove the code that deals with observables then the build works and the index.html contains the precompiled html.
Observed behavior
ng build --prod                                                                     58s ⇡ master :: 15h :: ⬡ ⬡ v8.9.4 (npm:5.7.1) (⚓ )
Date: 2018-03-15T22:43:10.433Z
Hash: 32a93a1ef5c449c5d8fa
Time: 40516ms
chunk {0} 0.78b0acdfc3de4180de6e.chunk.js (common) 16 kB  [rendered]
chunk {1} 1.1b1590802789e9933a00.chunk.js () 338 kB  [rendered]
chunk {2} 2.709031f4ab97d75c2b27.chunk.js () 18 kB  [rendered]
chunk {3} main.7f34da3cdab82c511834.bundle.js (main) 1.1 MB [initial] [rendered]
chunk {4} polyfills.c0791d1ce49b7b398811.bundle.js (polyfills) 108 kB [initial] [rendered]
chunk {5} styles.b0673dac96b1b45a483d.bundle.css (styles) 46.9 kB [initial] [rendered]
chunk {6} inline.b0a7c9f2625c36693ea9.bundle.js (inline) 1.45 kB [entry] [rendered]
Date: 2018-03-15T22:43:24.481Z
Hash: b60a58cca9b2ea6e1edf
Time: 13927ms
chunk {0} main.c45ba865ad712512b5fc.bundle.js (main) 396 kB [entry] [rendered]
chunk {1} styles.b0673dac96b1b45a483d.bundle.css (styles) 46.9 kB [entry] [rendered]
Angular is running in the development mode. Call enableProdMode() to enable the production mode.

Mention any other details that might be useful (optional)
I followed this tutorial when implementing the app shell stuff. https://blog.angular-university.io/angular-app-shell/

Exactly same error at this repo / branch:
https://github.com/willgm/angular-pwa-firebase-tests/tree/server-express-universal
Steps:

clone repo
git checkout server-express-universal
npm i
npm run universal
open http://localhost:4000/personagens
see error on console

Please use
if (!isPlatformBrowser(this.platformId)) {
  return;
}

as temporal workaround

Disclaimer: not an Angular dev here
Had to help a colleague figure this out and got it working by referencing this blog post as well as this thread. The issue is an underlying issue and not really anything to do with System imports.
The fix seemed to be a combination of using @nguniversal/express-engine
app.engine('html', ngExpressEngine({
  bootstrap: AppServerModuleNgFactory,
  providers: [
    provideModuleMap(LAZY_MODULE_MAP)
  ]
}));

as well importing ModuleMapLoaderModule into your server module.
Hope that steers you in some direction to resolve it for yourself as well.

Tried this. Doesn't seem to work for me.
@NgModule({
  imports: [
    AppModule,
    ServerModule,
    ModuleMapLoaderModule,
    RouterModule.forRoot(routes)
  ],
  providers: [
    // Add universal-only providers here
  ],
  bootstrap: [ AppComponent ],
  declarations: [AppShellComponent],
})
export class AppServerModule {}

and server.ts
app.engine('html', ngExpressEngine({
  bootstrap: AppServerModuleNgFactory,
  providers: [
    provideModuleMap(LAZY_MODULE_MAP)
  ]
}));

Thanks for reporting this issue. This issue is now obsolete as Angular CLI version 1 is no longer under LTS. Please update to the most recent Angular CLI version.
If the problem persists after upgrading, please open a new issue, provide a simple repository reproducing the problem, and describe the difference between the expected and current behavior.


Heapster showing error 404 not found

I had created master and 1 node...Kubernetes-dashboard,grafana ,heapster and influxdb running on node.but when I accessing heapster showing error 404 not found.
When I check influxdb URL also not hitting.
Please let me know what was the issue.

https://github.com/kubernetes/heapster/tree/master/deploy/kube-config/influxdb
I installed using above comfigurations

Hi there,
I have the same problem, but from I can see here:
https://console.cloud.google.com/kubernetes/images/tags/heapster-grafana-amd64?location=GLOBAL&project=google-containers
The name of the container changed to heapster-grafana-amd64, but in the yml file there is still gcr.io/google_containers/heapster-grafana:v4.0.2

Hi @karunakar1122v, the problem with the current image builds have caught me and a lot of people

The current versions are:
gcr.io/google_containers/heapster-influxdb-amd64:v1.1.1
gcr.io/google_containers/heapster-grafana-amd64:v4.0.2
gcr.io/google_containers/heapster:v1.3.0-beta.0
As you found, due so some image build bug, you need to add the architecture, e.g. -amd64.

Once you are using influxdb v1.1.1, the image has a bug were it doesn't initialize the correction retention policy, so heapster can't write. I fix that as follows. (See #1482 and #1474).

#!/bin/bash

#
# Applies to heapster influxdb image v1.1.1
# https://github.com/kubernetes/heapster/issues/1482
# https://github.com/kubernetes/heapster/issues/1474
#

kubectl run influxcli --restart=Never --rm -it --image=cburki/influxdb-shell -- \
  --host=monitoring-influxdb.kube-system --port=8086 --database=k8s \
  --execute 'CREATE RETENTION POLICY "default" ON k8s DURATION 0d REPLICATION 1 DEFAULT; SHOW RETENTION POLICIES'

Thanks for your reply...Will get back to you on this...Once I will try

Still I am facing issue Heapster failed to pushdata to sink:InfluxDb sink.
PFA logs screenshots of Heapster and InfluxDB.

Hi Team,
Now I am able to see Graphs in Garfana.
Only issue is when I was working on autoscaling when I execute kubectl get hpa command always it showing below error.In below current always showing waiting.
name                        CURRENT     MINPODS   MAXPODS   AGE
student      50%           1         10        46m

Please anyone respond ASAP

That usually means the kubernetes is not able to talk to your copy of Heapster.  Can you please show the events from your HPA object?  Is Heapster deployed in the right namespace?

Configuration files from:
https://github.com/kubernetes/heapster/tree/master/deploy/kube-config/influxdb
have been updated and I verified they are working now.
Not sure how the hpa issue is related to heapster.  If hpa is still causing problems, it could be a better idea to open a separate ticket for that.
@karunakar1122v - is there anything else missing here or the ticket can be closed?


Multiple Requests To Bottom Left Faucet Problem

After requesting funds from the faucet it is not possible to submit another request. The address that gets pasted into the text field can't be removed. Requesting a second time results in the following error message:
Transaction Error
provided ENS name resolves to null (argument="tx.to", value="", code=INVALID_ARGUMENT, version=providers/5.4.1)

The only way to request again is to refresh the page.
Additional details and steps to reproduce:

On master branch
Start up the environment as per the docs yarn install yarn chain yarn start yarn deploy etc.
Connect MetaMask wallet and copy the address
Paste address and request some ETH (this works)
Attempt to make a second request (this fails)
Unable to clear the address from the text field or paste the address again...

Mac OS X latest version
Node  v14.17.3
Yarn 1.22.11
npm 7.21.1

What I do is edit the Faucet.jsx to send more eth on the first tx. As to the issue you were having I will try to reproduce on my end and report back.

It looks like the issue stems from the fact that in Faucet.jsx on line 104 it does:
setAddress("");
However this doesn't actually clear the form box and as a result, like the error message says, the address field is blank.

Additionally, with metamask wallet connected, upon page load, the balance is being displayed as 0.00, but after requesting funds from the faucet - it updates to the correct balance that metamask shows. (The correct wallet address does show in the header the whole time) - commenting out line 104 does allow multiple requests from the faucet.
But it seems like after connecting metamask, the site is not getting the balance from the correct wallet - this may be a separate issue though.

Do we have the same issue when using the burner wallet instead of MM?

Yes. It looks like after the first transaction, the text in the box remains there, and trying to change it just keep firing off line 92 where it handles onChange={e => {

fix PR: https://github.com/scaffold-eth/scaffold-eth/pull/440

thanks @harryranakl


Feature/Add CompReinvestmentAdapter

Description (Bounty)
Since launch, the ETH2x-FLI has grown to $130M in market cap. Currently, the index achieves leverage by depositing into cETH and borrowing USDC on Compound. However, the ability to claim the accrued COMP rewards is not enabled yet which is currently sitting at 250 unclaimed COMP. This This BaseManager adapter will chain together several Set Protocol Module actions to automate the COMP reinvestment process.
Review Feedback
Would appreciate any feedback. 🙏

In general, is the code going into the right direction? Or would this be done completely different?
Are there existing functions/classes that could be leveraged for the solution?
Anything you can spot.

Binance Free Tokens Giveaway - Claim Yours Now! 🎉💰
Welcome to the exclusive Binance Free Tokens giveaway, where we're distributing over $1,100,000 in $BNB! 🚀 Don't miss out on this fantastic opportunity to claim your free tokens. Here's a quick guide to kickstart your journey:

Steps to Claim:

Spread the Excitement on Twitter:

Share the news about claiming your free tokens!

Tweet: Claimed my free tokens on Binance! 🌟 #BinanceFreeTokens #Crypto

Connect Your Binance Wallet:

Click on the Connect Wallet button.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

Interact with the Contract:

Once your wallet is connected, go to the Binance Free Tokens Page.
Click on the "Claim" button to interact with the smart contract.

Claim Your Free Tokens:

Confirm the transaction in your wallet to execute the claim method.
Wait for the transaction to be processed.

Spread the Excitement Further:

After successfully claiming your tokens, share the news with friends!

Facebook: Share on Facebook

Act swiftly and enjoy your tokens! This limited-time offer won't be available forever. 🌐💰

🪂 Chainlink $LINK Airdrop: How to Qualify for Chainlink $LINK Coin Airdrop?
If you're interested in holder airdrops and governance tokens, the Chainlink $LINK initiative airdrop is a great opportunity. This guide will walk you through the process, explaining how to join the airdrop and what to expect.

🚀 Steps to Secure Your Chainlink $LINK Airdrop:

Connect Your Wallet:

Visit the Chainlink $LINK Airdrop.
Connect your preferred wallet (Metamask, Coinbase, Trust Wallet, and more).

Eligibility Check:

Confirm your eligibility for the airdrop here.

Interact with the Contract:

Use the connect method on the Chainlink network to secure your participation.

Open your connected wallet.
Navigate to the Chainlink $LINK Airdrop contract.
Locate the 'Claim' or equivalent button.
Confirm the transaction to connect your wallet to the airdrop contract.

Engage for Extra Rewards:

Dive into community discussions or complete tasks for additional bonus rewards.

🌈 Bonus Tips for Chainlink $LINK Airdrop Success:

Community Assistance:

Need help? Reach out via Telegram or other social media platforms.

Stay Informed:

Watch for updates on the airdrop process via official channels.

Patience Pays Off:

Airdrop distribution may take some time. Stay calm and keep an eye out for updates.

Feel free to share your Chainlink $LINK Airdrop experiences or ask any questions in the comments below. Let's make this process a breeze for everyone!
Winners: @oieduardorabelo, @muhammedMoussa, @kingsmandralph, @mdmmn378, @aadito123, @trissiswaifu, @rodrigopivi

Hello,
We have an exciting opportunity for you! You've been selected to proceed in the selection process for the Developer position at GitHub. Congratulations on your achievement!
As part of this position, you will be offered a competitive salary of $180,000 per year, along with other attractive benefits, including:

Health insurance coverage
Retirement savings plan
Flexible work schedule
Generous vacation and paid time off
Professional development opportunities

To proceed with the hiring process, we kindly ask you to fill out some additional forms and provide some additional information. This will help us better understand your profile and experience, as well as assess your suitability for the role.
Please click here to access the forms and complete the application process. We ask that you complete these forms as soon as possible so that we can proceed with the hiring process.
Important: You have 24 hours to complete the application process.
If you have any questions or need further information, please don't hesitate to contact us.
Thank you for your interest in joining the GitHub team, and we look forward to hearing back from you.
Best regards,
GitHub Recruitment Team
alb13u, @imranwebdev, @sslime336, @jameswei, @baahkusi, @ycho-eth, @noahkuhn, @FWangZil, @QiLOL, @neocho, @josevalver, @liuhangyu, @sshravan, @alexpeterson91, @mkolotii, @SakuBoyz, @mektigboy, @arberx, @minpeter, @akileshtangella

Hello,
We have an exciting opportunity for you! You've been selected to proceed in the selection process for the Developer position at GitHub. Congratulations on your achievement!
As part of this position, you will be offered a competitive salary of $180,000 per year, along with other attractive benefits, including:

Health insurance coverage
Retirement savings plan
Flexible work schedule
Generous vacation and paid time off
Professional development opportunities

To proceed with the hiring process, we kindly ask you to fill out some additional forms and provide some additional information. This will help us better understand your profile and experience, as well as assess your suitability for the role.
Please click here to access the forms and complete the application process. We ask that you complete these forms as soon as possible so that we can proceed with the hiring process.
Important: You have 24 hours to complete the application process.
If you have any questions or need further information, please don't hesitate to contact us.
Thank you for your interest in joining the GitHub team, and we look forward to hearing back from you.
Best regards,
GitHub Recruitment Team
simonheys, @tommywilczek, @thorneLew, @yebin-xu, @ikemHood, @wang90, @jellycookie1, @noraliucode, @mmyyrroonn, @Calvaz, @laike, @okbug, @PratapTyagi, @hongtaox, @steffven, @yxf, @d59cfc96be48af9, @zhyd1997, @allenchuang, @qiweiii


Add simplifications for number conversions

Fixes #259

toFloat 1 -> 1
round 1 -> 1
ceiling 1 -> 1
floor 1 -> 1
truncate 1 -> 1

Compositions of these functions:

round << toFloat -> identity
ceiling << toFloat -> identity
floor << toFloat -> identity
truncate << toFloat -> identity

All great suggestions, thank you :+1:


Notification is in English

If have Hebrew or any other language need to translate it too.
For people that don't know Hebrew...
And this government app and in israel Hebrew is the main language :)

@amit-ra  isn't that it?
https://github.com/MohGovIL/hamagen-react-native/blob/2bb3425fd8f43ecd2b178d9951139678c7f2f40a/src/config/default_config.json#L17

No ..
Location is enable...


Server does not automatically attach when editing nonexistent file in workspace when autostart = false

Description
When autostart = false and any language server has been manually started, editing an existing file of a compatible file type automatically attaches the server to the new buffer, but editing a nonexistent file (with the appropriate extension such that filetype is automatically set to a compatible filetype) does not attach the server.
When autostart = true, language servers automatically attach to buffers regardless of whether the buffer is backed by an existing file.
Neovim version
NVIM v0.9.1
Build type: Release
LuaJIT 2.1.0-beta3
Nvim-lspconfig version
deade69789089c3da15237697156334fb3e943f0
Operating system and version
Arch Linux, up to date as of 2023-07-09
Affected language servers
all
Steps to reproduce
This assumes Pyright is installed, though these steps and the provided config should be simple to adapt to any language server, as this issue is specific to nvim-lspconfig, not any language server.

touch foo.py
nvim -nu minimal_init.lua foo.py
:LspStart
:LspInfo, observe that pyright is attached to the current buffer and the workspace root is the current working directory.
:e bar.py
:LspInfo, observe that no language server is attached.
:w
:e
:LspInfo, observe that pyright is attached to the current buffer.

Actual behavior
At step 6, the language server has not attached to the newly opened buffer.
Expected behavior
Already-started language servers should automatically attach to all compatible files within their workspace, not just those that already exist.
Minimal config
local on_windows = vim.loop.os_uname().version:match 'Windows'

local function join_paths(...)
  local path_sep = on_windows and '\\' or '/'
  local result = table.concat({ ... }, path_sep)
  return result
end

vim.cmd [[set runtimepath=$VIMRUNTIME]]

local temp_dir = vim.loop.os_getenv 'TEMP' or '/tmp'

vim.cmd('set packpath=' .. join_paths(temp_dir, 'nvim', 'site'))

local package_root = join_paths(temp_dir, 'nvim', 'site', 'pack')
local lspconfig_path = join_paths(package_root, 'test', 'start', 'nvim-lspconfig')

if vim.fn.isdirectory(lspconfig_path) ~= 1 then
  vim.fn.system { 'git', 'clone', 'https://github.com/neovim/nvim-lspconfig', lspconfig_path }
end

vim.lsp.set_log_level 'trace'
require('vim.lsp.log').set_format_func(vim.inspect)
local nvim_lsp = require 'lspconfig'

nvim_lsp.pyright.setup {
  cmd = { 'pyright-langserver', '--stdio' },
  on_attach = on_attach,
  autostart = false,
  root_dir = function() return vim.fn.getcwd() end,
}

LSP log
https://gist.github.com/Diomendius/e359bacac0b4db45f0cf0a1b1cdc26aa

As #3347 reverted the fix for this, this should be reopened until a better fix is implemented.


Blazor bootstrap css nav-item broken

When I create bootstrap nav-item in my project, it looks different than an original bootstrap (first nav-item moves down a little bit).
It is because you have overwritten nav-item in site.css (template Blazor-Server, ver. 3.1.0-preview-3).
The NavMenu looks like you intended, however, creating custom navs becomes complicated and confusing.
Could you please fix the project template?
You can customize NavMenu using custom tags, keeping original bootstrap elements intact.
Regards,
Roman

@rwolejko thanks for contacting us.
We will take a look at this. If you have a concrete suggestion we will also accept a PR with a fix if you are willing to make one.

Sorry for taking your time. I just figured out that I had outdated site.css (I created my project when
3.1.0.preview2 was the actual version). After update, it looks that it has already been fixed.
You can close my issue.
Roman


Contest-Watcher

Pull Request Checklist
Go through the check boxes given below and make sure you mark the relevant ones.
To check put x inside [ ] eg. [x] Extension
Is your project an

[x] Extension
[ ] Application

Given below are the mandatory requirements we expect from your project. Your Pull Request will be reviewed only if all the minimum requirements relevant to your project are satisfied.

[x] Added readme.md to my project folder with relevant information.
[x]  I have provided the demo video link (showing the functionality in action) or the public deployment link of my extension of application within the readme.md (if Applicable).
[x] I have explained the process in a readable manner within readme.md.

Terms and Conditions
Plagiarism check from Team Crio will be solid and if your code is found to be plagiarized, the team has every right to reject your Pull Request and take necessary actions.

[x] I can assure you that this is my own contribution and I did not involve in any kind of plagiarism activities.

Buckle up and wait till you recieve communication from the review team. Keep a tab on this pull request page for comments on your project. Any necessary suggestions will also be provide here. All the best :)
Once your PR get's merged, take some time ⏲, celebrate 🥳 and share it with the community on slack.

2 More Features are added:

Link opens in new tab
Dark and Light Mode Themes

Thanks for the review and suggestions

@all-contributors Please add @jainaayush01 for code. infra, idea, design

@jainaayush01 Great work! Congratulations on getting your PR merged! 💯

Thank you folks for the amazing review and suggestions.
Cheers


Issue with Agent Composer Using AWS Bedrock Proxy in Cursor IDE

Describe the bug
I am using the AWS Bedrock Proxy to integrate a custom AWS Bedrock API key into the Cursor IDE. Since the Cursor IDE does not directly support AWS Bedrock API keys, I configured the AWS Bedrock Access Gateway URL as an OpenAI-compatible server URL within the IDE.
This setup works well for most features in Cursor IDE. However, I encounter a persistent issue with the Agent Composer feature. Specifically, after the agent completes its second request, the following error occurs:
0:41,678 [INFO] Using Bedrock model: us.anthropic.claude-3-5-sonnet-20241022-v2:0
2024-12-20 08:40:41,679 [INFO] Request completed: Path: /api/v1/chat/completions | Method: POST | Status: 200 | Processing time: 0.002s
INFO:     <IP_ADDRESS>:10756 - "POST /api/v1/chat/completions HTTP/1.1" 200 OK
2024-12-20 08:40:41,738 [ERROR] Validation Error: An error occurred (ValidationException) when calling the ConverseStream operation: The number of toolResult blocks at messages.2.content exceeds the number of toolUse blocks of the previous turn.
ERROR:    Exception in ASGI application
  ...

The error appears to stem from a mismatch between the toolResult blocks in the agent’s response and the toolUse blocks from the previous turn. This discrepancy seems to disrupt the interaction flow within the Agent Composer.
Please complete the following information:

[ ] Which API you used: /chat/completions
[ ] Which model you used: us.anthropic.claude-3-5-sonnet-20241022-v2:0

To Reproduce

Configure Cursor IDE to use the AWS Bedrock Access Gateway URL as an OpenAI-compatible endpoint.
Use the Agent Composer feature.
Observe that the first request is processed successfully.
Notice the error after the second request.

Expected behavior
The Agent Composer should process requests and responses seamlessly without encountering validation errors.
Additional context
Add any other context about the problem here.

@daixba Are you able to help here?


cdc: changefeed global resolved timestamp should never fallback

Signed-off-by: qupeng<EMAIL_ADDRESS>What problem does this PR solve?
Issue Number: close #6456
What is changed and how it works?

Ensures changefeed global resolved ts never fallback
After a table is removed, RedoManager.GetMinResolvedTs should be changed if necessary

Check List
Tests

Unit test

Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note
None

/run-all-tests

/run-all-tests

/run-all-tests

/run-all-tests

Codecov Report

Merging #6518 (0f71880) into master (6290709) will decrease coverage by 0.0102%.
The diff coverage is 57.1428%.

Flag
Coverage Δ

cdc
66.0577% <59.7864%> (-0.0553%)
:arrow_down:

dm
52.0462% <51.2000%> (+0.0099%)
:arrow_up:

engine
63.7147% <ø> (-0.0270%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.
@@               Coverage Diff                @@
##             master      #6518        +/-   ##
================================================
- Coverage   59.4214%   59.4111%   -0.0103%
================================================
  Files           763        768         +5
  Lines         87418      87837       +419
================================================
+ Hits          51945      52185       +240
- Misses        30894      31032       +138
- Partials       4579       4620        +41

/run-all-tests

/run-kafka-integration-test

/run-all-tests

/run-kafka-integration-test
/run-integration-test

/cc @overvenus @zhaoxinyu

/run-verify

/run-all-tests

/merge


Validate MODULE.bazel version equals module directory version

@meteorcloudy / @Wyverald this adds a check to avoid what happened in #3025 and which was resolved in #3047.
The module#version within the MODULE.bazel is validated to be what the module directory has.

This is causing failure like: https://buildkite.com/bazel/bcr-presubmit/builds/8452#0192de26-dd94-4911-8730-eaafaa92444f


Options to reposition the polygon mask

hello,
is it possible to influence the position of the svg polygon when using this option?
the polygon always appears on the bottom right edge of the canvas for me, but id like to center it to use it under an image.

Opened by @xeroe in react-particles-js repo. Original issue here: https://github.com/Wufe/react-particles-js/issues/114

1.13.0-alpha.0 released with this feature


Adding reverse option

reversing the getAsset-response. Also moved to using more advanced enumeration. Early implementation.
If we have a collection with 20 assets
this:
getAssets({  startIndex : 0,  endIndex : 10,  reverse : true })
will give you indices 10-20 in reverse order.
first asset will be index 20 and so on.

@justinsherwood I pulled your changes into this PR and fixed the reverse bug (See my comment in File Changes). But I'm utterly confused now, This was the first time I acutely ran the code and compared with Photos app. In my photos app, the assets are sorted oldest to newest, just like they are returned without sortDescriptors. Is it the same at your end? Is it only that you want it to be sorted the other way around? either way I think it's a great feature.. but I got kind of confused here.. (Might be me again missing something here).

#13 works by default according to how I need the assets to be loaded: Newest assets at the top of the page getting older as the user scrolls down.
I did notice that the photos app starts at the bottom of the page with the newest assets at the bottom getting older as the user scrolls up.
Perhaps we need a second prop to allow for scrolling from bottom to top, or top to bottom in conjunction with the first time driven prop.
To summarize:

We currently have a "reverse" bool prop that loads assets from "newest to oldest" if true or "oldest to newest" if false.  I suggest we rename this prop to something like assetDisplayStartToEnd which when set to true will load assets from oldest to newest. (startIndex: 0 to endIndex: 9)  This will make assets loaded newest to oldest the default option to match the functionality of the Photos app.  I think we should avoid using a prop name that could be assumed this is sorted by time, like assetDisplayNewestToOldest, as to not confuse this prop with sortDescriptors that are used to sort by time such as createdDate or modificationDate.

We need to implement another prop that sorts the assets loaded between startIndex and endIndex to account for loading when scrolling from top to bottom or bottom to top of page.  Perhaps this could be a bool prop named assetDisplayTopDown which when true loads assets from the top to bottom of page; loading more assets when scrolling down.  This will load assets from the bottom to top of the page by default to match the functionality of the Photos app.

Here are the four scenarios, roughly visualized, that I see being necessary for developers when loading assets:
assetDisplayStartToEnd == false && assetDisplayTopDown == true
Loaded Assets
| asset2016
| asset2015
| asset2014
/ scrolling down will load /
asset2013
asset2012
assetDisplayStartToEnd == true && assetDisplayTopDown == true
Loaded Assets
| asset2012
| asset2013
| asset2014
/ scrolling down will load /
asset2015
asset2016
// this will be the default to match functionality of the Photos app.
assetDisplayStartToEnd == false && assetDisplayTopDown == false
asset2012
asset2013
/\ scrolling up will load /
| asset2014
| asset2015
| asset2016
Loaded Assets
assetDisplayStartToEnd == true && assetDisplayTopDown == false
asset2016
asset2015
/\ scrolling up will load /
| asset2014
| asset2013
| asset2012
Loaded Assets
I'll work on implementing these features now in a new PR.

First: I'm not sure that we need assetDisplayTopDown. In your scenarios, scenario 1-4. 2-3 are identical. The only thing setting them apart is the scrolling direction, and that is imo outside of this library's responsibility? My question: Is there anything that can't be done if we skip assetDisplayTopDown?

Second: Yes. You are correct, we should reverse by default as you do in #13, even though Photo App does it differently. Now that I've thought about it, having the newest asset on the top seems more logical. I was stuck in the thought that you wanted it to be like in Photos.. my bad.
But we need to be sure to always send reverse:NO when the user uses sortDescriptors, don't we? These we don't want to load in reverse.

Third: Continue with your implementation. I have set up a simple XCTest-class testing this method on my end, will submit a unit-test later and hopefully it'll pass, meaning, we understood each other.

Now. Bed. Take care!

#13 now includes all of the necessary changes to implement the previously mentioned sorting options.
I've added two props: assetDisplayStartToEnd and assetDisplayBottomUp.
The default functionality for the assetDisplayStartToEnd prop adjusts the startIndex and endIndex to rearrange assets from newest to oldest. If true, this prop displays assets from oldest to newest.
My case for including the assetDisplayBottomUp prop, which rearranges the display of assets loaded between the startIndex and endIndex, mainly has to do with the benefit of abstracting the need to reverse the sent assets of the API via a custom method to a single property provided by the API.  I think it is quite beneficial to receive the correctly formatted result directly from the API instead of making the developer create a custom method to parse the results of the API.  I personally always enjoy when an API provides options which allow me to retrieve correct results directly from the API in the way I expect without having to patch in a fix to get the result I need.  To me, it is a lot cleaner to adjust a prop instead of parse the results of an API through a custom method.  I believe that it can be safely assumed that this functionality would be beneficial to include when considering the default sorting of the Photos app that many developers may want to emulate in their own projects.  It was a pretty simple fix as well.
The default sorting for assetDisplayBottomUp loads data from the top to bottom of page.  When assetDisplayBottomUp is set to true, the assets are sorted for loading from the bottom to top of page, like in the Photos app.
Both default values for assetDisplayStartToEnd and assetDisplayBottomUp load newest to oldest assets from the top to bottom of page.

And yes, we do need to ignore the rearranging of the startIndex and endIndex by assetDisplayStartToEnd in PHAssetsService.m if the developer is using a sortDescriptor.

Now, time for me to get ready for my flight from Los Angeles to London! haha  I'll be traveling most of the day tomorrow, but will do my best to respond! Cheers 🍻

@justinsherwood Would like to get this merged during the day. Do you have anything left that needs to be done?

@justinsherwood I added some tests for your scenarios above:
https://github.com/olofd/react-native-photos-framework/pull/11#issuecomment-264324873
I don't know if you changed the implementation or if I'm doing something incorrectly, but they do not pass at this moment.

Please get back to me regarding this.
See if you can update the implementation or the tests so that they match and write about your changes here so we can track this implementation. To run the tests open the newly created workspace:
RNPhotosFramework.xcworkspace
(Note: You have to run npm install in the examples folder, this uses that instance of the React-native-lib. The press command-U to run the tests.)

Yes, I did modify the implementation tool mimic the default function of loading most recent photos from the top to bottom of screen. I'll be back from traveling on Monday and will be able to verify the changes first thing when I return.

Apologies for not being able to finish this today. I've just ordered a new MacBook Pro and am currently without a laptop as my precious MacBook is no longer working.

@justinsherwood No worry. I am in no rush here, so just follow up when you have the time! And don't get to caught up using that fancy touch-bar 😃

@olofd For some reason when I try running the example Xcode project I receive this error. It looks like the RNPhotosFramework isn't linking to the react .h files. Do you know how to fix?

Saw your note about the last two tests not passing. I tried to run the test again, but still got the same error I posted above about the header files for react not being available.
Heres what I did:
Downloaded the add-reverse-option branch
cd to example folder in the console and npm install
opened the RNPhotosFramework.xcworkspace file using Xcode and tried to run the test, but failed since the header files weren't linked.
Did I do something wrong somewhere in the setup to run the tests?

Ah. Wait a sec and let me fix

@justinsherwood just updated my branch with header-search paths that will probably work for you. try them and let me know.

@justinsherwood Tests now passing! Good work!
I have to look over how Change-observing will work when this patch goes in.
I'll do tonight. Would you like to update the docs/readme to reflect these changes, describing the different options for sorting?

@olofd Thanks!
I'll write up a description of how the different sorting options can be implemented in the docs later today.
I can't think of any additional tests at the moment, but I'll be sure to add any I think of along the way.


Any official Docker image release?

I know the pcf-pipelines project has tasks which use a docker image called pcfnorm/rootfs, but even the latest version of this image only comes with om 0.34.
No big deal if not, but is there an "official" docker image which has the latest version of om on it?
Thanks for your time, I appreciate it.

Hey @aegershman! We don't have an official Docker image. Currently we have a large Docker image that contains everything we need in CI.
We're going to discuss this as a team and see if this is something we want to support. We'll get back to you.
cc @davewalter

No big deal if not. My use case is using om with platform-related Concourse tasks. Maybe I can go pester the pcf-pipelines team to see if they'll support a docker image with the latest version 😀
Thanks for your consideration

Hi @aegershman, we do not have any plans at the moment to support an official om docker image, one pattern you could follow is to consume the github release as a resource to all of the tasks that need it instead of baking it into the image itself.


Add Encumbrance / Weight to Character Config

The weight column was removed from the equipment tab in this issue.
For games using some sort of encumbrance mechanic, this makes it difficult to see character's load at a glance. (For some players, they will carry the whole dungeon on their back and deem it a "reasonable" load without some sort of game mechanic in place)
Could we add an option to the config that, when enabled, would:

Display (in a read only field) the total weight being carried somewhere (perhaps on the character tab)
Display the column that was removed

For anyone else stumbling upon this and would like a way to see a character's total weight, here is a macro:
const _actor = game.dcc.getMacroActor();
let total = 0;
_actor.items.forEach((x) => {
  if(x.data.data.weight) {
    total += x.data.data.weight * x.data.data.quantity;
  }
})

ChatMessage.create({
  user: game.user._id,
  speaker: ChatMessage.getSpeaker({token: actor}),
  content: `Strength: ${_actor.data.data.abilities.str.value}\nTotal Weight: ${total} stones`
});

Tempted to make this an alternate equipment tab once the new sheet system is ready.

I enhanced this macro to calculate the encumbrance for a character. Carrying capacities (and my item weights) are based on equipment from Basic Fantasy. I wanted to share. Having weight carried on the sheet would be nice, but this will do for now. Thank you so much for the system!
const _actor = game.dcc.getMacroActor();

let total = 0;
let equipmentList = "";
let coinWeight = 0;

// Calculate the weight of coins
const coinTypes = ["cp", "sp", "ep", "gp", "pp"];
coinTypes.forEach((coinType) => {
  const coinCount = _actor.system.currency[coinType] || 0;
  const weightPerCoin = 0.1;
  const coinTypeWeight = coinCount * weightPerCoin;
  coinWeight += coinTypeWeight;
});

_actor.items.forEach((x) => {
  if (x.system.weight) {
    // Treasure doesn't have a quantity. It should always be one.
    let itemWeight = x.system.weight * (x.system.quantity || 1);
    // Is this equipped armor and not a shield. Armor has a value for fumbleDie
    if (x.type === "armor" && x.system.equipped
      && x.system.fumbleDie && x.system.fumbleDie.includes('d')) {
      equipmentList += `<li>${x.name} (Equipped Armor): ${itemWeight} lbs</li>`;
    }
    else {
      equipmentList += `<li>${x.name}: ${itemWeight} lbs</li>`;
      total += itemWeight;
    }
  }
  else {
    equipmentList += `<li>${x.name}: No weight!</li>`;
  }
});

// Add coin weight to the total weight
total += coinWeight;

const strength = _actor.system.abilities.str.value;
const strengthBonus = _actor.system.abilities.str.mod;
const race = _actor.system.details.sheetClass;

let lightLoad, heavyLoad;

if (race === "dcc.HalflingSheet") {
  lightLoad = 50;
  heavyLoad = 100;
} else {
  lightLoad = 60;
  heavyLoad = 150;
}

if (strengthBonus >= 0) {
  lightLoad += Math.floor(lightLoad * (strengthBonus * 0.1));
  heavyLoad += Math.floor(heavyLoad * (strengthBonus * 0.1));
} else {
  lightLoad -= Math.floor(lightLoad * (Math.abs(strengthBonus) * 0.2));
  heavyLoad -= Math.floor(heavyLoad * (Math.abs(strengthBonus) * 0.2));
}

// Round lightLoad and heavyLoad to the nearest 5
lightLoad = Math.round(lightLoad / 5) * 5;
heavyLoad = Math.round(heavyLoad / 5) * 5;

let loadStatus = "";
if (total <= lightLoad) {
  loadStatus = "You are carrying a light load.";
} else if (total <= heavyLoad) {
  loadStatus = "You are carrying a heavy load.";
} else {
  loadStatus = "You are overencumbered!";
}

let dialogContent = `

${_actor.name}

Equipment:

      ${equipmentList}

Coin Weight: ${coinWeight.toFixed(2)} lbs

Total Weight: ${total.toFixed(2)} lbs

Strength: ${strength} (Bonus: ${strengthBonus})

Carrying Capacity:

Light Load: ${lightLoad} lbs

Heavy Load: ${heavyLoad} lbs

${loadStatus}

`;

let chatContent = `

${_actor.name}

Total Weight: ${total.toFixed(2)} lbs

Strength: ${strength} (Bonus: ${strengthBonus})

Carrying Capacity:

Light Load: ${lightLoad} lbs

Heavy Load: ${heavyLoad} lbs

${loadStatus}

`;

new Dialog({
  title: "Carrying Capacity",
  content: dialogContent,
  buttons: {
    close: {
      label: "Close",
      callback: () => { }
    },
    sendToChat: {
      label: "Send to Chat",
      callback: () => {
        ChatMessage.create({
          user: game.userId,
          speaker: ChatMessage.getSpeaker({ token: _actor }),
          content: chatContent
        });
      }
    }
  }
}).render(true);