Reading an external voltage Heltec WiFi LoRa 32 V3

I am trying to read an external battery voltage. The web interface refers to pin 34. I assumed this might mean GPIO 34 (pin 11 on the Heltec Wifi LoRa V3). However, this does not appear to be the correct pin. on this board. Any suggestions?

you can use any unused pin for external voltage measurement.
i dont have all the pins in my head to recommend you one, the pin34 was just for lora32v2.1 board and you can use anyone you find free and it should work
compare the pinouts used with the available for each board (condering not using gps, lora, oled pins of the board)

wait!
this pin recommendation is for igate firmware, not for tracker...   so I would need to generate code for external voltage measurement (outside the one from the internal battery readings)

This is on an iGate - not a tracker.

Moved to igate section.


Commit the wallet state to disk when the ClientStateFile is dropped

Closes #277.

Looks like a trivial conflict?

Yup! Just wanted to make sure those two lines ended up in the right order (they happened to).


If I add the "ion-slides" in "ion-content" or "div", the slides are not in visible.

Ionic version:  (check one with "x")
[ ] 1.x (For Ionic 1.x issues, please use https://github.com/driftyco/ionic-v1)
[ ] 2.x
[x] 3.2.1
I'm submitting a ...  (check one with "x")
[x] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:

If I add the "ion-slides" in "ion-content" or "div", the slides are not in visible.
Expected behavior:

Have the slides inside ionic-content visible.
Steps to reproduce:
http://plnkr.co/edit/Mejtst3RDiJqCLISYzhH?p=preview
Related code:
<ion-content >
  <ion-slides pager>

    <ion-slide style="background-color: green">
      <ion-content>

Slide 1: Inside content is not visible

      </ion-content>
    </ion-slide>

    <ion-slide style="background-color: blue">

Slide 2

    </ion-slide>

    <ion-slide style="background-color: red">

Slide 3

    </ion-slide>

  </ion-slides>
</ion-content>

Hello thanks for opening an issue with us. It looks like plunker is down at the moment, but i will check this once it comes back up.

Hello @mediaon , in the latest chrome your plunker works fine for me. Because of this I am going to close this issue for now but please feel free to open a new issue if you are still running into this issue.


Delay in transcription

When the speech time is long and words are continuous, delay goes little bit higher. The model runs on Nvidia T4 GPU. Should I consider upgrading my GPU model or any idea about it?

@alpcansoydas we havent tested it on a T4 yet.
Consider using a smaller size model and see if the issue persists.


Check previous writen profiles during rotation

should_rotate() should check previous saved loggers, load and add to previous one or create new logger.

I don't think this an issue. We should not load data back since you might have two writers, and there's no way for us to handle a race condition.
A better solution is to use session ID/session timestamp in the file name when users don't specify a filename_template.
The default template should be profiles.$start_time-$end_time_exclusive.$session_time.bin
Example: profiles.2021-03-16T00:00:00.000Z_2021-03-17T00:00:00.000Z.2021-03-26T23:01:15.765Z


[Bug] Rating on product listing page does not mach rating on product page

Current behavior
On product listing page all items are rated the same - 5 stars even if the product rating on product card is different.
Expected behavior
The product rating on the product list page should be the same as the rating for this product on the product page.
Steps to reproduce the issue

go to any category page
choose one product
check the number of stars it has and click on it
check the number of stars it has
see the error

Can you handle fixing this bug by yourself?

[ ] YES
[ ] NO

Environment details
https://capybara.storefrontcloud.io/
Additional information

related https://github.com/DivanteLtd/vsf-capybara/issues/27 stars values are hardcoded, that is why it looks different.
TODO:

test module https://github.com/DivanteLtd/magento2-review-api/blob/develop/docs/api-specs.md
add to payload rating value

@gibkigonzo  Do not quite understand, they will remain fixed?

@ArieRym if you want to have reviews then yes you need to install this plugin. But rating is not added to payload


chore: update @chainsafe/blst dependency

0.2.9 has nodejs v20 support and is otherwise exactly the same

:tada: This PR is included in v1.9.0 :tada:


Add security headers

I want to merge this change because...

Screenshots

Pull Request Checklist

[ ] All visible strings are translated with proper context.
[ ] All data-formatting is locale-aware (dates, numbers, and so on).
[ ] The changes are tested.
[ ] The code is documented (docstrings, project documentation).
[ ] Changes are mentioned in the changelog.

Test Environment Config

API_URI=https://qa.staging.saleor.cloud/graphql/

Task linked: SALEOR-4293 Add security headers to vercel deployments


Add pictureInPictureWindow to enterpictureinpicture event

@mounirlamouri Where do you think we should add resize event listener for pipWindow?
Context: https://github.com/WICG/picture-in-picture/pull/84

I'm basically wondering if we should advocate for the pattern below:
async function onButtonClick() {
  myButton.disabled = false;
  await video.requestPictureInPicture();
  myButton.disabled = false;
}

let pipWindow;

video.addEventListener('enterpictureinpicture', function(event) {
  // Video entered PiP.
  pipWindow = event.pictureInPictureWindow;
  pipWindow.addEventListener('resize', onResizePictureInPictureWindow);
});

video.addEventListener('leavepictureinpicture', function() {
  // Video left PiP.
  pipWindow.removeEventListener('resize', onResizePictureInPictureWindow);
});

function onResizePictureInPictureWindow(event) {
  const pipWindow = event.target;
  // TODO: Update video dimension based on pipWindow.width and pipWindow.height
}

I'm a bit confused. The title, the first comment and the example/code change do not quite match.
I will assume the title is due to this being a follow-up of #84. Regarding the first comment, PictureInPictureWindow already has a resize event so I'm guessing the question is mostly about what pattern we should recommend? I think that we should recommend the pattern that you have in the second comment. I think it's worth clarifying why this is a better pattern and mention auto-PIP being handled.

Thanks @mounirlamouri!


Modify the link of dynamically allocating 2D array in README.md

Hi Liao,
I modify a link in README
Maybe you can check it again.
Thanks

Thank you. :heart:


[Feature request] Verify PDF certificate signature

The tool lets you create signatures with certificates but there is currently no way to verify them.
An elegant solution would be to include such a functionality within the reader.

If you're referring to checking if the certificate is trusted or not, then it wouldn't be possible since some certificates are self signed. Everything else should definitely be achievable though.

True, but an option would be to include an optional custom trust store file like a NSS certificate database.
When this is not included it could use the mozilla one for example and only verify official certificates.

This seems similar to https://github.com/JakubMelka/PDF4QT/issues/161
Maybe OCSP based revocation checking instead of trusting would be a better option.

I found this tool called mupdf and it has the abilites to do so.


Undo buffers

What's this PR do?
Adds document buffers to Parallax IDE to allow for file specific undo/redo.
Where should the reviewer start?
Pull this branch.
npm run build
How should this be manually tested?
Create a few test files. Add text to each. Click back and forth between files to test undo. Undo should not leave the active file.
Try to create new files and delete files. Be sure undo/redo is behaving as you would expect.
Any background context you want to provide?
A few interesting cases needed to be dealt with in order to integrate CodeMirror document buffers with the existing file system. The buffer system itself is relatively straight forward. Each time the user navigates to a file, a new buffer is generated if it does not already exist and swapped into the editor. If it does exist, the document is pulled from the buffer in memory. However at all times, the workspace is updating content in the editor regardless of what buffer is present. This created some timing challenges. I needed to have the buffer document present in the background but ignore changes that would impact the undo history. This is what the allowUpdate logic accounts for in the editor index.js file.
Another timing issue presented itself on initial startup of the editor. Our current implementation has the first file loaded into the workspace before the CodeMirror instance actually exists. I had to code a special case for that in the file store.
Much of the case off coding could be avoided if files were loaded directly into a CodeMirror document. However that would involve a rework of the background file interaction system. That  might be worth the effort to lower complexity of this buffer implementation and future work that deals with projects/file system behavior.
What are the relevant tickets?
Closes #69

@drquinn Wow, awesome!  I'm excited by this enhancement to fix a strange behavior, and your behind-the-scenes explanation is greatly appreciated!

@PropGit glad it helps :)


Appstudio update test-component-pac-azqo

Pipelines as Code configuration proposal

Pipelines as Code CI/test-component-pac-azqo-on-pull-request has failed.

StatusDurationName

✅ Succeeded
8 seconds
appstudio-init

✅ Succeeded
17 seconds
clone-repository

✅ Succeeded
16 seconds
sast-snyk-check

✅ Succeeded
15 seconds
appstudio-configure-build

❌ Failed
19 seconds
build-container

✅ Succeeded
8 seconds
show-summary

Failure reasontask build-container has the status "Failed":
2023/01/19 13:37:50 Skipping step because a previous step failed

Pipelines as Code CI/test-component-pac-azqo-on-pull-request has failed.

StatusDurationName

✅ Succeeded
8 seconds
appstudio-init

✅ Succeeded
17 seconds
clone-repository

✅ Succeeded
16 seconds
sast-snyk-check

✅ Succeeded
15 seconds
appstudio-configure-build

❌ Failed
19 seconds
build-container

✅ Succeeded
8 seconds
show-summary

Failure reasontask build-container has the status "Failed":
2023/01/19 13:37:50 Skipping step because a previous step failed


message edit: Removed unused message_edit_forms from DOM

We now handle the removal of the message_edit_form within message_edit.end()
When a user edits a particular message and chooses to either close or save the edit -- message_edit.end() will immediately clear the message_edit_form from the DOM
This is a fix to the request, found in  #14151, for the cleanup of unnecessary message_edit_forms found in the DOM

This is great, thanks for the nice PR!  It happened to race with @YashRE42 fixing this in #14569, so I'm closing this without merging, but nicely done :).


Incorrect status / "Updating" in Homekit

Hey renssies,
first of all thanks a lot for this great plug-in!
I've followed your tutorial to install factually everything works fine. The only bug I encounter is that the status of the motor blinds is not reported back to homekit somehow. After clicking the button in the home app the blinds start to move, then the blind icon switches to a loading wheel and says "updating".  Same when I ask Siri through homepod to close the blinds, the blinds start to move, but then siri  says "sorry, I did not hear back from your device".
Any idea how to fix that?

Can you share the logs from Homebridge, it looks like something is going wrong in your specific case.

Sure thing. When booting homebridge on the Pi  I getthis:
[26/5/2021, 7:23:27 pm] [am43-blinds] Stopped searching for AM43 Blinds, found 1 devices (node:1900) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'writeAsync' of null     at AM43Device.sendCommandAsync (/usr/lib/node_modules/homebridge-am43-blinds/lib/AM43Device.js:343:44)     at AM43Device.updatePositionAsync (/usr/lib/node_modules/homebridge-am43-blinds/lib/AM43Device.js:299:16)     at AM43Device.prepareAsync (/usr/lib/node_modules/homebridge-am43-blinds/lib/AM43Device.js:204:16)     at Noble.<anonymous> (/usr/lib/node_modules/homebridge-am43-blinds/lib/AM43Platform.js:136:16)     at runNextTicks (internal/process/task_queues.js:58:5)     at processTimers (internal/timers.js:494:9) (Use node --trace-warnings ...to show where the warning was created) (node:1900) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag--unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 3) (node:1900) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

I'm assuming you are using the built-in Bluetooth of the Raspberry Pi and you followed the instructions as mentioned here: https://github.com/renssies/homebridge-am43-blinds#installation
If so, then it might be a range issue. The Raspberry Pi's built-in Bluetooth has a terrible range.
Try installing a USB Bluetooth 4.0 adapter in the Pi and disabling the built-in Bluetooth. You can see this issue for compatible adapters: https://github.com/renssies/homebridge-am43-blinds/issues/29#issuecomment-798449516

Thanks!
I placed it next to the blind using a power bank, but it did not really help it seems
d finite number and received "undefined" (undefined). See https://git.io/JtMGR for more info. (node:3482) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'on' of undefined     at AM43Device.setBlindsControlCharacteristic (/usr/lib/node_modules/homebridge-am43-blinds/lib/AM43Device.js:91:38)     at AM43Device.connectAsync (/usr/lib/node_modules/homebridge-am43-blinds/lib/AM43Device.js:223:10)     at AM43Device.prepareAsync (/usr/lib/node_modules/homebridge-am43-blinds/lib/AM43Device.js:202:7) (node:3482) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict(see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 12) (node:3482) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'on' of undefined     at AM43Device.setBlindsControlCharacteristic (/usr/lib/node_modules/homebridge-am43-blinds/lib/AM43Device.js:91:38)     at AM43Device.connectAsync (/usr/lib/node_modules/homebridge-am43-blinds/lib/AM43Device.js:223:10)     at AM43Device.sendCommandAsync (/usr/lib/node_modules/homebridge-am43-blinds/lib/AM43Device.js:320:7)     at AM43Device.updatePositionAsync (/usr/lib/node_modules/homebridge-am43-blinds/lib/AM43Device.js:299:5) (node:3482) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag--unhandled-rejections=strict(see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 13) (node:3482) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'on' of undefined     at AM43Device.setBlindsControlCharacteristic (/usr/lib/node_modules/homebridge-am43-blinds/lib/AM43Device.js:91:38)     at AM43Device.connectAsync (/usr/lib/node_modules/homebridge-am43-blinds/lib/AM43Device.js:223:10)     at AM43Device.sendCommandAsync (/usr/lib/node_modules/homebridge-am43-blinds/lib/AM43Device.js:320:7)     at AM43Device.updateBatteryStatusAsync (/usr/lib/node_modules/homebridge-am43-blinds/lib/AM43Device.js:305:5) (node:3482) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag--unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 14)

I will reinstall homebridge to see if it helps, and also ordered a bluetooth dongle.  Will  keep you posted!

I get similar issues, it usually recovers though so I've not been too worried about it. I've seen the blind position as reported by HomeKit jump around backwards and forwards like there's some sort of out of order issue in dealing with the messages from the blinds. Haven't really looked into it since it remains stable & usable, if a bit jittery in the HomeKit status.

Have now completely reinstalled my Pi, homebridge and this plugin, using a new bluetooth USB dongle (CSR8510 chipset, which is plug and play).
On first sight, it seems that the updating issue in homebridge is resolved now. Yet, the plugin throws a couple of errors into the log:
`[01/06/2021, 18:24:29] [am43-blinds] Stopped searching for AM43 Blinds, found 1 devices
(node:1946) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'writeAsync' of null
at AM43Device.sendCommandAsync (/usr/local/lib/node_modules/homebridge-am43-blinds/lib/AM43Device.js:343:44)
at AM43Device.updatePositionAsync (/usr/local/lib/node_modules/homebridge-am43-blinds/lib/AM43Device.js:299:16)
at CurrentPosition. (/usr/local/lib/node_modules/homebridge-am43-blinds/lib/AM43Platform.js:461:32)
at CurrentPosition.emit (events.js:376:20)
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/dist/lib/Characteristic.js:733:43
at new Promise (:null:null)
at CurrentPosition. (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/dist/lib/Characteristic.js:731:47)
at step (/usr/local/lib/node_modules/homebridge/node_modules/tslib/tslib.js:143:27)
at Object.next (/usr/local/lib/node_modules/homebridge/node_modules/tslib/tslib.js:124:57)
at /usr/local/lib/node_modules/homebridge/node_modules/tslib/tslib.js:117:75
at new Promise (:null:null)
at Object.__awaiter (/usr/local/lib/node_modules/homebridge/node_modules/tslib/tslib.js:113:16)
at CurrentPosition.Characteristic.handleGetRequest (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/dist/lib/Characteristic.js:656:24)
at Bridge. (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/dist/lib/Accessory.js:1298:54)
at step (/usr/local/lib/node_modules/homebridge/node_modules/tslib/tslib.js:143:27)
at Object.next (/usr/local/lib/node_modules/homebridge/node_modules/tslib/tslib.js:124:57)
at /usr/local/lib/node_modules/homebridge/node_modules/tslib/tslib.js:117:75
at new Promise (:null:null)
at Object.__awaiter (/usr/local/lib/node_modules/homebridge/node_modules/tslib/tslib.js:113:16)
at Bridge.Accessory.handleCharacteristicRead (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/dist/lib/Accessory.js:1275:24)
at _loop_1 (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/dist/lib/Accessory.js:1235:20)
at Bridge.Accessory.handleGetCharacteristics (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/dist/lib/Accessory.js:1263:17)
at HAPServer.emit (events.js:376:20)
at HAPServer.handleCharacteristics (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/dist/lib/HAPServer.js:718:18)
at IncomingMessage. (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/dist/lib/HAPServer.js:286:21)
at IncomingMessage.emit (events.js:388:22)
at endReadableNT (internal/streams/readable.js:1336:12)
at processTicksAndRejections (internal/process/task_queues.js:82:21)
(Use node --trace-warnings ... to show where the warning was created)
(node:1946) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 10)
(node:1946) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.`

Ok, so changing hap_interaction_timeout to 0 solved for me the "not responding issue", however battery drains very fast.
Just for my understanding:  If I put said variable to say 60 seconds, what happens after? How will the connection be re-established?

hap_interaction_timeout is suppose to mean that X seconds after you interacted with the accessory it disconnects the bluetooth connection.
So let's say hap_interaction_timeout is 60, that means that after opening or closing the blind with HomeKit it disconnects after 60 seconds. As soon as you interact with it again it should attempt to reconnect and send the open/close command.
However it is a tiny bit buggy and I'm missing the skills to improve it.


Use APP_ID as defined in properties

The "APPLICATION_ID" property is not always defined when setupIndexes is called. This fixes a NullPointerException when that happens.

https://ocd.appscale.com:8080/job/Daily Build/3902/


Find address function

Haven't update test cases 👎

Coverage decreased (-1.2%) to 90.714% when pulling 74a6160f9cba78b1eb8e2cab13b6df33a7d6a632 on mavistoh:FindAddress into 8e6b05042a32aa65d69b817c73ffbc4efaff2bf9 on CS2103T-T17-B3:master.

Coverage decreased (-1.2%) to 90.714% when pulling 83b431b080d29c3073a69adb96036c821e0fa739 on mavistoh:FindAddress into 8e6b05042a32aa65d69b817c73ffbc4efaff2bf9 on CS2103T-T17-B3:master.


Support for postgresql

Hi!
This looks like a great idea ! Any chance you can provide postgresql support as well?
Thanks in advance !

Thanks for the kind words @legovaer
Will put this in the backlog.
It would be awesome if you could share the version of the DB you are using, Home assistant recorder config and even some of the data! This would help me test your specific case :)


Add new playground prototype

This adds a new version of the playground add web/new_playground.html. It doesn't support the new layouts for Flutter or show analyzer issues yet.

closes #1224

@RedBrogdon PTAL


Added MaterialProgressBar to InflationInterceptor

If the MaterialProgressBar is used instead of AestheticProgressBar, ensure that it still gets themed via Aesthetic.

I think this would kind of ruin the purpose of using MaterialProgressBar in your apps, since there is some special logic that goes into the MaterialProgressBar class related to drawables, padding, etc.
https://github.com/DreaminginCodeZH/MaterialProgressBar/blob/master/library/src/main/java/me/zhanghai/android/materialprogressbar/MaterialProgressBar.java

'AestheticProgressBar' inherits from 'MaterialProgressBar', so you don't lose any of that.
All this does is, if you happen to already be using 'MaterialProgressBar' somewhere in your xml, you don't have to change it to 'AestheticProgressBar' in order to have it themed by aesthetic (just like regular 'ProgressBar'.
This actually happened to me and I was confused for a while about why my 'MaterialProgressBar' wasn't being themed.


set noindex and nofollow for archived branch 0.26

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind user-interface

/kind content

/kind translation

/kind event

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area blog

/area documentation

/area community

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: vjjmiras
Once this PR has been reviewed and has the lgtm label, please assign leogr for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: 3ed59a7f142d522f96bd5a9ba51a6ce06f33ed75

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: Issif, vjjmiras
Once this PR has been reviewed and has the lgtm label, please assign leogr for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: Issif, vjjmiras
Once this PR has been reviewed and has the lgtm label, please assign leogr for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


standAlone and jobServer execution in configuration

Description
Two execution modes, standAlone and JobServer
Reviewer
@danielcsant
Test
All passed

Please add User documentation about JobServer configuration

Implemented in another PR


Improvements for Adding to IPFS via Context Menu

(Closes #579)
I played a bit with the concept from #579 and it is not enough to change the order.
Instead we should have clear, separate labels for each context. So far I've added a separate menu item for adding link destination and kept common label for images,videos and audio as "Add This Object to IPFS".
Screenshot below illustrates the most extreme case is when you select part of a page and then click on an image that is also a link (so you get actions for all those contexts):

@alanshaw  @olizilla  would appreciate quick review of "Add ... to IPFS" menu  labels, do they sound ok or awkward? How we could improve it to make English locale better?

More thoughts:

What does "add link" do?
Unless there's a good reason to not keep the filename I'd have just a single option for "Add object..." which keeps the filename

Ad https://github.com/ipfs-shipyard/ipfs-companion/pull/585#pullrequestreview-156694580) Good ideas. It is possible to provide different label for image, video and audio, so I did just that (see screenshot below).
Ad 1) It executes addFromURL using href from <a> tag that was context-clicked
Ad 2) There are cases when users want raw CID, but I agree it should not be the default. Removed it for now, will think how to re-introduce it.

👍 nice!
How about "Add Linked Content to IPFS" instead of "Add Link Destination to IPFS"?

What do "copy canonical" and "copy public gateway" do in this context? I assume they refer to the page not the selection, but it's not clear.
I think it'd be easier to reason about if it was

Add selection to IPFS
Copy page CID bafy...
Copy page IPFS url https://ipfs.io/...

I've restored option to get "raw CID"  as "Copy Direct CID" (it resolves IPFS/IPNS path to raw CID)
Note: until Page Actions are redesigned in #587  the same action labels are used in popu-menus:

Context Menu
Page Action (Firefox only)
Browser Action

How does this look?
@olizilla  yes, that one was an extreme edge case, usually it is page or image.
Depending on what is clicked, "Copy" actions will look for base URL in this order:

image|video|audio (if clicked on any instead of  page)
link (if clicked on any instead of a page)
page

Do you think we should have separate labels for each context?

ERH GERD, SORRY I PRESSED THE UPDATE BRANCH BUTTON ACCIDENTALLY.
revoke my permissions at once.
😿

anyhoo
ETOOMANYOPTIONS.
Is it possible to add the entire selection to IPFS regardless of what's in it? Could it always be "Add selection to IPFS" even if it's images and text?
"Direct CID" is tricky, as direct doesn't mean anything in this context. I think its more intuitive if we tell the user what the CID will be for (page, selection).

I would not put truncated values in menus, it does not tell much and makes them look cluttered.

It might be a terrible idea, as it could make them look cluttered, but I mildly disagree that it wouldn't tell the user much. Showing what they'll get is really helpful if you don't know what a CID is, or what "canonical" means.


Description does not match what is available in reality.

Hi kaarins,
something must be wrong because if I follow this description, there is no menu or link as described in paragraph 5.
I hope you can verify and correct this. Or did I find a future feature? ;-)
Cheers, Harry.

Dokumentdetails
⚠ Bearbeiten Sie diesen Abschnitt nicht. Er ist für die Verknüpfung von docs.microsoft.com zum GitHub-Artikel erforderlich.

ID: 0293eda0-8476-a578-fe89-8320208e03bc
Version Independent ID: 8077916b-34d4-4bfa-a77f-e577249f99ab
Content: Ändern Sie die externe Freigabe Einstellung für einen Benutzer OneDrive
Content Source: OneDrive/user-external-sharing-settings.md
Service: one-drive
GitHub Login: @kaarins
Microsoft Alias: kaarins

@DaKarli Thank you for this feedback
It sounds like you might have stumbled on a potential bug. So that we can get this documented and addressed promptly I would like to have you open a Support case. Support can document this and has more resources to handle potential bugs.
Here is a quick video on opening a ticket: https://www.youtube.com/watch?v=puuOy0sEg1Y
If you don't mind please keep us posted here on the resolution and I really want to get this information you are discovering back into the docs.


fix(locales): fix typos in French translation

I don't understand French, so I can't judge which tranlastaion is better.
If @Fl0wyn and @Elliot67 reach an agreement (@Elliot67 approve the changes), I will merge this PR.

I think it's ok with the new changes from @Elliot67
We corrected each other

@Fl0wyn OK, could you please commit the changes suggested by @Elliot67 ?

Merged. Thank you for your contribution


Improve explanation of part 2 of the bank app project.

Part 2 bank project unclear and difficult to follow course instructions
I am currently using this course to teach some students some introduction to web development. Part 2 has been trouble for all of them regarding these issues. I help them figure it out in class but it will be much better to bring these to the general public.

The instructions on setting up the bank API are not clearly written. I will love to indicate that they need to clone the project, navigate to the 7-bank-project/api folder and run npm install and npm start there.
Bank API setup instruction link
I will also like to indicate to them that they need two terminals running for both servers. One for the bank API and then the other for the actual bank code they were already writing up until part 2. npx lite-server for the bank app, and npm install for the bank API.
Part 2 bank project app

These two additions will make this particular section of the course easier to follow along. If its okay, I can create a pull request for these changes.

hi @nsoseka - thank you so much for your feedback. Indeed, these lessons are both important to understand and pretty complicated, so I'd love for you to PR a clarification!
Also, I'd love to know where you are teaching. Can you reach out? I'm<EMAIL_ADDRESS>- thank you again!

@jlooper Thanks for the prompt reply. I just submitted a PR for this issue.
PR link
Will reach out to you. Thanks lots


MongoDB: Inconsistent column data: Failed to convert ... error on invalid data in properties does not mention affected field (and other useful information)

When reading from a model that has incompatible data in a property in a collection compared to what is defined for the field in the model, you currently get an error message like this:
Message: Error in Prisma Client request:
Invalid `prisma.inspections.findMany()` invocation:

  Inconsistent column data: Failed to convert '""' to 'Int'.

Query:
{
  "modelName": "inspections",
  "operation": "findMany",
  "args": {
    "take": 100,
    "skip": 0,
    "select": {
...
    }
  }
}

This error message is suboptimal in multiple ways:

Uses database terminology column instead of Prisma (or MongoDB) terminology field
Does not mention the affected field (number or zip in this case)

Additionally the error message could link to a docs page that explain how to solve this (Probably: either update all data in the field to the defined type [how?], or set the field to Json so it can accept all types [and then still update the data to be able to switch to a better type]).

I have similar issue with serverless & serverless-webpack-prisma
{
    "errorType": "Runtime.UnhandledPromiseRejection",
    "errorMessage": "Error: \nInvalid `a.prisma.post.findMany()` invocation in\n/var/task/index.js:1:9000\n\n→ 1 (()=>\n  Inconsistent column data: Malformed ObjectID: invalid character 'r' was found at index 1 in the provided hex string: \"drafts\".",
    "reason": {
        "errorType": "Error",
        "errorMessage": "\nInvalid `a.prisma.post.findMany()` invocation in\n/var/task/index.js:1:9000\n\n→ 1 (()=>\n  Inconsistent column data: Malformed ObjectID: invalid character 'r' was found at index 1 in the provided hex string: \"drafts\".",
        "code": "P2023",
        "clientVersion": "3.14.0",
        "meta": {
            "message": "Malformed ObjectID: invalid character 'r' was found at index 1 in the provided hex string: \"drafts\"."
        },
        "stack": [
            "Error: ",
            "Invalid `a.prisma.post.findMany()` invocation in",
            "/var/task/index.js:1:9000",
            "",
            "→ 1 (()=>",
            "  Inconsistent column data: Malformed ObjectID: invalid character 'r' was found at index 1 in the provided hex string: \"drafts\".",
            "    at Object.request (/var/task/node_modules/@prisma/client/runtime/index.js:45405:15)"
        ]
    },
    "promise": {},
    "stack": [
        "Runtime.UnhandledPromiseRejection: Error: ",
        "Invalid `a.prisma.post.findMany()` invocation in",
        "/var/task/index.js:1:9000",
        "",
        "→ 1 (()=>",
        "  Inconsistent column data: Malformed ObjectID: invalid character 'r' was found at index 1 in the provided hex string: \"drafts\".",
        "    at process.<anonymous> (/var/runtime/index.js:35:15)",
        "    at process.emit (events.js:314:20)",
        "    at processPromiseRejections (internal/process/promises.js:209:33)",
        "    at processTicksAndRejections (internal/process/task_queues.js:98:32)"
    ]
}

Your error is different @softmarshmallow - please open a new issue. Make sure to include the schema of this post model so we can understand waht might be going on. Thanks.


Support for Edge on Windows Containers for automated UI testing

Request from User Voice: https://windowsserver.uservoice.com/forums/304624-containers/suggestions/34081195-edge
Need Edge in a container for automated UI testing

Sorry for not making any comments on this.
This is still in our backlog so we'll close the issue for now. We're open to requests in case customers want to see this implemented.

as aoto tester,I want to see this implemented.
I want to create many type of  windows test envionment as docker images.


Minor typo in weight_initialization.ipynb

Section: General rule for setting weights.
Current copy: "The general rule for setting the weights in a neural network is to be close to zero without being too small. A good pracitce is to start your weights in the range..."
Issue: 'pracitce' --> practice.

Fixed the typos.


[Feature]: Admin panel

Resolves #19

[X] Logs in Admin Panel
[X] Restart bot
[X] Force upload patrons to VRChat
[x] Export full patron list
[x] Fix tests
[x] Reset specified user
[x] Override specified user
[x] Add confirm messages
[x] Update tests for new messages & buttons

Yup seems to work as expected


requirement: R4, Read the assembly language representation of LLVM IR

Marked as future ambition, closing for now. See the following comment for further information.

Superseded by #167.


Create a GitHub release for each action release

Must make sure this release is not marked as latest or else it will interfere with the CLI bundle releases also included in this repo.
See https://cli.github.com/manual/gh_release_create
Merge / deployment checklist

[ ] Confirm this change is backwards compatible with existing workflows.
[ ] Confirm the readme has been updated if necessary.
[ ] Confirm the changelog has been updated if necessary.

Here is a release created using the workflow: https://github.com/aeisenberg/codeql-action/releases
Here is the run that created it: https://github.com/aeisenberg/codeql-action/actions/runs/11267116373/job/31331695828


Avatars does not load on project edit page

problem occurs because link_to_avatar_with_params is not used:
https://github.com/noisy/steemprojects.com/blob/master/profiles/models.py#L267

Looks like it is fixed.


Net::HTTP adapter doesn't automatically decompress like the real Net::HTTP does

In Ruby 1.9+ Net::HTTP automatically handles gzip and deflate decompression. In the Faraday ecosystem FaradayMiddleware::Gzip is/was a popular way to handle for HTTP clients that don't have built-in support. While working on a gem to remove this middleware from the dependencies (and unblock the Faraday 1.0 -> 2.0 upgrade) I noticed the WebMock adapter behaves differently than the actual Net::HTTP implementation.
The 'real' Net::HTTP#readbody calls #read_body_0. This calls #inflater which wraps the socket to transparently decompress if need be (if not the socket is passed through as-is), the socket is read from and written to the destination buffer. Since WebMock adapter extends the created Net::HTTPResponse object and overrides #readbody, none of this happens inside the test suite for a stubbed response.
I poked at creating a PR but I'm getting a bit lost in what the best place would be (so the next part is rubber ducking myself 😄) to put a fix in:

The adapter instantiates Net::HTTPResponse directly but doesn't set the @socket instance variable (normally done via .reading_body), so WebMockHTTPResponse can't just delegate to #inflate.
It looks like StubSocket is supposed to stand in for Net::BufferedIO as a socket (which wraps OpenSSL::SSL::SSLSocket, which wraps TCPSocket), but it's missing stuff (eg #read_all) for it to work when used by the deflater.
WebMockHTTPResponse could get a slimmed down version of the original #inflate but that feels like a suboptimal way of going about things?

@rzane it seems your work in https://github.com/bblimke/webmock/pull/992 would get us to a place where @socket is actually set 🙌
Then I'd be running into the same "StubSocket isn't a very convincing stub of a socket" problem you mentioned in https://github.com/bblimke/webmock/issues/999#issuecomment-1224350696 - I wonder if using a (subclass of) StringIO instead would make sense? It looks like we could remove directly setting the body ivar and the rest - like decompression - should just work?

Unfortunately #992 was reverted. There were a few problems with that PR. But yes, it sounds like that might work.


[FEA] Allow rapids_test to be used without CUDAToolkit

Is your feature request related to a problem? Please describe.
rapids_test_init() calls find_package(CUDAToolKit REQUIRED) if it does not find a generate_resource_spec executable at exactly <build-dir>/rapids-cmake/generate_resource_spec
Obviously this doesn't work so well on cpu-only builds.
Describe the solution you'd like
Provide a way of disabling this check, or provide an option USE_GPU OFF. Ideally we could simply do
include(path/to/rapids-test.cmake)

rapids_test_init(ENABLE_GPU OFF)

Describe alternatives you've considered
Currently, we work around this by spoofing the file like so
include(${rapids-cmake-dir}/test/detail/default_names.cmake)

set(patch_file "${CMAKE_CURRENT_SOURCE_DIR}/cmake/patches/generate_resource_spec.diff")
set(eval_file ${rapids-cmake-dir}/test/detail/generate_resource_spec.cpp)
set(eval_exe ${CMAKE_CURRENT_BINARY_DIR}/rapids-cmake/${rapids_test_generate_exe_name})

message("-- Patching ${eval_file}")
find_program(PATCH NAMES patch REQUIRED)
execute_process(
  COMMAND ${PATCH} --unified ${eval_file} --input=${patch_file} --ignore-whitespace --quiet
  TIMEOUT 15
  COMMAND_ERROR_IS_FATAL ANY
)

# Compile the (now patched) resource spec generator, and place the result where rapids
# expects to find it. try_compile() is a bit of a misnomer here -- this compilation MUST
# succeed, as rapids_test_init() below will fail if it doesn't
try_compile(
  SUCCEEDED
  SOURCES ${eval_file}
  COPY_FILE ${eval_exe}
  OUTPUT_VARIABLE compile_ret
)

if(NOT SUCCEEDED)
  message(FATAL_ERROR "Failed to compile patched resource spec generator for rapids_cmake_test(): ${compile_ret}" )
endif()

where generate_resource_spec.diff is
--- ./generate_resource_spec.cpp
+++ ./generate_resource_spec.cpp
@@ -14,7 +14,6 @@
  * limitations under the License.
  */

-#include <cuda_runtime_api.h>

 #include <iostream>
 #include <string>
@@ -27,7 +26,6 @@

 struct gpu {
   gpu(int i) : id{i} {};
-  gpu(int i, const cudaDeviceProp& prop) : id{i}, memory{prop.totalGlobalMem}, slots{100} {}
   int id        = 0;
   size_t memory = 0;
   int slots     = 0;
@@ -47,17 +45,8 @@
 int main()
 {
   std::vector<gpu> gpus;
-  int nDevices = 0;
-  cudaGetDeviceCount(&nDevices);
-  if (nDevices == 0) {
-    gpus.emplace_back(0);
-  } else {
-    for (int i = 0; i < nDevices; ++i) {
-      cudaDeviceProp prop;
-      cudaGetDeviceProperties(&prop, i);
-      gpus.emplace_back(i, prop);
-    }
-  }
+
+  gpus.emplace_back(0);

   version v{1, 0};
   std::cout << "{\n";

The entire purpose of rapids_test_init ( https://docs.rapids.ai/api/rapids-cmake/stable/command/rapids_test_init/ ) and related commands is GPU resource management for tests. For this to work we want the CUDA toolkit installed ( no need for actual gpu ).
What functionality of rapids_test are you looking for that isn't provided by CMake's add_test for no builds on machines without the CUDA Toolkit?

What functionality of rapids_test are you looking for that isn't provided by CMake's add_test for no builds on machines without the CUDA Toolkit?

rapids_test_install_relocatable(). Specifically, our CI requires us to build tests/executables on one runner, then execute on another runner. We could not easily make this work using default CMake machinery.
I am sure it can be done (case in point, rapids_test_install_relocatable()), but rapids_test() ended up being the most ergonomic solution.

@Jacobfaib Does https://github.com/rapidsai/rapids-cmake/pull/480 resolve this issue for you


BUG 2101660: Fix RBD failover

This includes upstream PR's https://github.com/ceph/ceph-csi/pull/3206 and https://github.com/ceph/ceph-csi/pull/3216

/lgtm


Add client side

Pull Request
Jira Ticket
https://leasy-project.atlassian.net/browse/LME-1
Description
This PR sets up the foundational structure for the "Leasy (Learning Made Easy)" client-side application using Next.js. It includes initial configurations, global styles, essential components, and project documentation to establish a solid starting point for further development.
Related Issue
Checklist
Please ensure that your pull request meets the following criteria:

[ ] All new and existing tests pass (if needed)
[x] Documentation has been updated (if applicable)

#skipreview


refactor: default providers

What this PR changes/adds
Cleanup default providers following the documentation guidelines
Why it does that
Project structure review
Further notes

Put default services in dedicated default extensions
Removed DidStore as it wasn't used

Linked Issue(s)
Closes #1812
Checklist

[ ] added appropriate tests?
[x] performed checkstyle check locally?
[x] added/updated copyright headers?
[x] documented public classes/methods?
[ ] added/updated relevant documentation?
[x] assigned appropriate label? (exclude from changelog with label no-changelog)
[x] formatted title correctly? (take a look at the CONTRIBUTING and styleguide for details)

Codecov Report

Merging #1974 (c839aea) into main (e25e01a) will decrease coverage by 0.02%.
The diff coverage is 54.28%.

@@            Coverage Diff             @@
##             main    #1974      +/-   ##
==========================================
- Coverage   62.93%   62.91%   -0.03%
==========================================
  Files         784      786       +2
  Lines       16635    16599      -36
  Branches     1081     1078       -3
==========================================
- Hits        10470    10443      -27
+ Misses       5714     5706       -8
+ Partials      451      450       -1

Impacted Files
Coverage Δ

...ore/controlplane/DefaultControlPlaneExtension.java
0.00% <0.00%> (ø)

.../catalog/cache/FederatedCatalogCacheExtension.java
100.00% <ø> (ø)

...ataspaceconnector/api/DefaultApiCoreExtension.java
0.00% <0.00%> (ø)

...connector/azure/cosmos/DefaultCosmosExtension.java
0.00% <0.00%> (ø)

...aceconnector/iam/did/IdentityDidCoreExtension.java
0.00% <ø> (ø)

...dataplane/sync/DataPlaneTransferSyncExtension.java
0.00% <ø> (ø)

...ne/sync/DefaultDataPlaneTransferSyncExtension.java
0.00% <0.00%> (ø)

.../transfer/provision/http/HttpWebhookExtension.java
82.75% <ø> (-1.12%)
:arrow_down:

.../dataspaceconnector/core/DefaultCoreExtension.java
55.55% <55.55%> (ø)

...atalog/cache/DefaultFederatedCatalogExtension.java
75.00% <75.00%> (ø)

... and 3 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

Awesome!


Remove "/sso" from embed urls

"/sso/" is no longer needed in embed urls and it is not best practice to include "/sso". "/embed/sso" redirects to "/embed".

Looks fine to me @mslovich.  Do you need someone to merge this for you or do you have the necessary permissions yourself?

@jbandhauer - you were correct.  I don't have merge permission on this repo.
Thanks!


Component does not resize after loading new json in parent scope

Steps to reproduce:

Enter page where directive is used with option for edition available
Click on edit button
Click on cancel button
In parent scope change value of the object passed to the directive - to the longer or shorter.

As a result view of editor does not resize to conform to the new content. It is not problematic if you load shorter json. In case of longer one it results in situation in which you cannot see whole value.

@darul75
At evening I will prepare PR which you can review afterwards.

Yes it will be great I knew some issues were still there for edition so I appreciate you collaboration and work


Error:

Hello there, hope you are doing well!
I have a strange issue. I am running HammerTIme, BuildPiecesCustomized, and many other mods (everything is built from Thunderstore with R2Modman, including those with custom build hammers). I ran into a weird issue where the Clutter mod by Plumga on Thunderstore (among others) will no longer be added as a category and not show up in the HammerTime config file when it did before. (Clutter will show up in the HammerTime config if I make a new mod profile with R2modman so I know Clutter still works with HammerTime). In the log, it says there is an error:
[Warning: HammerTime.Config] Config 'Enable Hammer' for _ClutterPieceTable not found
It does this for another mod called PlantIt as well. Oddly, it started after I was editing bpcsave files from the BuildPiecesCustomized mod (was messing with the category number for a couple build pieces). I also noticed that the issue started right when I removed two building piece mods as well (removing their categories from the vanilla hammer - those mods were RavenwoodDwarvenKingdoms by JamesJonesTV, and RavenwoodPieces by JamesJonesTV).
Is there any way I can fix this? I already tried to delete the HammerTime config file while the game was not running (one file called "com.maxsch.valheim.HammerTime.cfg"), run the game again, and look at the new config file and Clutter and others are still not in the HammerTIme config list. I also tried uninstalling the entire mod, and reinstalling it, and it is not detecting several mods like Clutter anymore. Has no issue finding it on another new mod profile though.
errors.txt
I uploaded a photo of one of the errors, as well as an Errors log (there are several "index" errors that all started right when HammerTime started losing access to mods in it's config file.)
Huge thank you for the help if you have time! Trying to save the mod profile.

Please send the full log. Also the HammerTime warnings aren't inside the file you send.
However, whatever mod is causing the first PieceTable error, is likely the reason for the issue. Unfortunately, it's hard to tell which mod is causing it.


LyncConnector Export script bug

Hi, I found a script bug in Lync Connector Export script.
Error during export was:

It turns out there's an extra single quotation mark on line 465 in the export script that gives the error (highlighted):

Thanks Henrik. I've checked in the fixed script. I'll close this issue now.


add serialization to regions for json formatted catalog

supports new region versions e.g., QuadTreeRegion
added region comparison using to_dict method in regions

Codecov Report

Merging #138 (dac5f0f) into master (065ae2d) will increase coverage by 0.18%.
The diff coverage is 54.54%.

@@            Coverage Diff             @@
##           master     #138      +/-   ##
==========================================
+ Coverage   56.88%   57.07%   +0.18%
==========================================
  Files          19       19
  Lines        3157     3189      +32
  Branches      457      464       +7
==========================================
+ Hits         1796     1820      +24
- Misses       1250     1252       +2
- Partials      111      117       +6

Impacted Files
Coverage Δ

csep/core/regions.py
53.94% <45.45%> (+1.73%)
:arrow_up:

csep/core/catalogs.py
60.18% <72.72%> (+0.18%)
: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 065ae2d...dac5f0f. Read the comment docs.


libStorage 0.4.0-rc4

This patch updates the libStorage dependency to 0.4.0-rc4.

Current coverage is 12.80% (diff: 100%)

Merging #692 into release/0.7.0 will increase coverage by 5.34%

@@           release/0.7.0       #692   diff @@
===============================================
  Files                 21         13      -8
  Lines               2574       1460   -1114
  Methods                0          0
  Messages               0          0
  Branches               0          0
===============================================
- Hits                 192        187      -5
+ Misses              2365       1261   -1104
+ Partials              17         12      -5

Powered by Codecov. Last update ec5963e...0d0035f


Create mas-oidc-client crate

Based on: #482.
Library that allows to interact as an RP with an OIDC OP.
It's currently very WIP, but it's possible to register a client, get an access token and refresh.
The oidc-client-cli example has been tested against a MAS instance running locally in a container (which is why currently the https validation is disabled), although the logout command doesn't work because it's not supported by MAS yet.
Todo:

[x] Share as much types and logic with the other crates as possible.
[x] Resolve the TODOs in the code.
[x] Supported flows: authorization code, client credentials.
[x] Follow the security best practices.
[x] Improve docs.
[x] Tests.

It passes most of the OpenID Connect Core Client Tests in the OpenID Foundation conformance suite, except for those features that are not supported:

Aggregated and distributed Claims
WebFinger discovery
Requesting UserInfo with the access token in the body of the request

It was also tested against the servers from the OIDC Playground. All endpoints implemented in the client and supported by the servers worked for:

MAS
Keycloak (authentication method must be client_secret_basic otherwise the PAR fails)
Auth0

This should be ready for review now :crossed_fingers:

I've started looking at it, it overhaul looks good, but I'm not 100% sold on the API design.
The idea of having one Client structure which holds the whole state and takes care of HTTP calls is not very flexible. This assumes that for one provider, we ever have one client registration/set of client credentials and one logged in session.

I've been heavily influenced by what we do for matrix-rust-sdk. We just create one Client per session (iirc, that's what the appservice crate does).
I can understand that it's not ideal for the server part but I'm not sure what the API would look like. A bunch of static methods that take all the necessary parameters as input and make the request?

Ok now it only has the standalone functions and I think it's enough for this PR.
I'll add the new API in another PR after this is merged.

@sandhose this is ready for review again :wink:


Modular player/controller/world data structure

The game should allow for:
*Player to switch from one ship to another
*any ship controlled by Player can also be controlled by an AI
*Player ship to Warp to multiple areas on a nodal 'galaxy map'

ship switching, at least in its basic form, has been added.

warping around the galaxy map, in a basic form, has been added.

All but the AI has been implemented.
AI will be left for another issue..


(chore): bump proc-macro2 1.0.5x -> 1.0.65

Changes

Fixes #428
Bumps proc-macro2 to version 1.0.65

Notes
As proc-macro2 is an internal dependency, meaning it is a dependency required indirectly, the only way to bump it is to directly edit Cargo.lock.
This is safe, HOWEVER, blindly running cargo update/add MAY revert these changes in the near-ish future, so be aware of that :)

PR superseded by #430.


Method argument probes / visualizations

Probing method arguments would provide immediate context for a method. Either this is enabled by default for every method that has at least one probe, or users should be able to explicitly probe arguments.

Fixed in 1ba710182b5599aa3fb0acf2cce7f94523df24b2


SyntaxError: invalid regexp group in Firefox

I have some issue using the package with Firefox. Everything works fine with Chrome and Edge. I use Webpack and Babel to compile my code.
Environment details

OS: Linux Ubuntu
Node.js version: v10.16.3
npm version: 6.9.0
@google-cloud/dialogflow version: 2
Firefox 77.0.1

Steps to reproduce
My code is as below:
const dialogflow = require('@google-cloud/dialogflow');
const uuid4 = require('uuid4');
const json = require('./keyfile.json');
const { JWT } = require('google-auth-library');

async function askBot(query) {
              const client = new JWT(
                json.client_email,
                null,
                json.private_key,
                [
                  'https://www.googleapis.com/auth/cloud-platform',
                  'https://www.googleapis.com/auth/dialogflow'
                ]
              );
              const url = `https://dialogflow.googleapis.com/v2/projects/${json.project_id}/agent/sessions/${session_id}:detectIntent`;

              const data = {
                "queryInput": {
                  "text": {
                    "languageCode": "en",
                    "text": query
                  }
                }
              };
              const res = await client.request({url: url, method: 'POST', data: data});

              respond(res.data.queryResult.fulfillmentText);
            }

My Webpack config
const path = require('path');
const webpack = require("webpack");
const UglifyJsPlugin = require('uglifyjs-webpack-plugin');

module.exports = {

  optimization: {
    minimize: true,
    minimizer: [new UglifyJsPlugin({
      test: /\.js(\?.*)?$/i,
    })],
  },

  entry: [
          './js/index.js',
  ],

  plugins: [
    new webpack.ProvidePlugin({
      $: "jquery",
      jquery: "jQuery",
      "window.jQuery": "jquery"
    }),
  ],

  output: {
    path: path.resolve(__dirname, 'js'),
    filename: 'dialogflow.js',
    publicPath: '/',
  },

  mode: 'development',
  module: {
    rules: [
      {
        test: /\.js$/,
        exclude: /(node_modules|bower_components)/,
        use: {
          loader: 'babel-loader',
        }
      }
    ]
  },
  node: {
    fs: 'empty',
    child_process : 'empty',
    net : 'empty',
    tls: 'empty',
  }
};

And .babelrc
{
    "presets": [
          [
              "@babel/preset-env",
              {
                  "useBuiltIns": "usage",
                  "debug":true,
                  "corejs": 3,
              }
          ],
      ],
      "plugins": [
          [
              "@babel/plugin-transform-template-literals",
              {
                "loose": true
              }
          ],
          "transform-modern-regexp",
      ]
  }

@marast78 Could you share your error log?

@munkhuushmgl below I've pasted a console log (I've had to set up a fake URL :ok: )
SyntaxError: invalid regexp group dialogflow.js:1:1
    js https://fakedomain.pl/modules/custom/pku_dialogflow/js/dialogflow.js?v=8.7.3:1625
    o https://fakedomain.pl/modules/custom/pku_dialogflow/js/dialogflow.js?v=8.7.3:1
    <anonimowa> webpack:///./node_modules/google-gax/build/src/fallback.js?:32
    js https://fakedomain.pl/modules/custom/pku_dialogflow/js/dialogflow.js?v=8.7.3:1561
    o https://fakedomain.pl/modules/custom/pku_dialogflow/js/dialogflow.js?v=8.7.3:1
    <anonimowa> webpack:///./node_modules/@google-cloud/dialogflow/build/src/v2/agents_client.js?:20
    <anonimowa> webpack:///./node_modules/@google-cloud/dialogflow/build/src/v2/agents_client.js?:1115
    js https://fakedomain.pl/modules/custom/pku_dialogflow/js/dialogflow.js?v=8.7.3:33
    o https://fakedomain.pl/modules/custom/pku_dialogflow/js/dialogflow.js?v=8.7.3:1
    <anonimowa> webpack:///./node_modules/@google-cloud/dialogflow/build/src/v2/index.js?:20
    js https://fakedomain.pl/modules/custom/pku_dialogflow/js/dialogflow.js?v=8.7.3:65
    o https://fakedomain.pl/modules/custom/pku_dialogflow/js/dialogflow.js?v=8.7.3:1
    <anonimowa> webpack:///./node_modules/@google-cloud/dialogflow/build/src/index.js?:20
    js https://fakedomain.pl/modules/custom/pku_dialogflow/js/dialogflow.js?v=8.7.3:29
    o https://fakedomain.pl/modules/custom/pku_dialogflow/js/dialogflow.js?v=8.7.3:1
    <anonimowa> webpack:///./js/dialogflow-chatbot.js?:66
    js https://fakedomain.pl/modules/custom/pku_dialogflow/js/dialogflow.js?v=8.7.3:5
    o https://fakedomain.pl/modules/custom/pku_dialogflow/js/dialogflow.js?v=8.7.3:1
    <anonimowa> webpack:///./js/index.js?:3
    js https://fakedomain.pl/modules/custom/pku_dialogflow/js/dialogflow.js?v=8.7.3:13
    o https://fakedomain.pl/modules/custom/pku_dialogflow/js/dialogflow.js?v=8.7.3:1
    <anonimowa> webpack:///multi_./js/index.js?:1
    0 https://fakedomain.pl/modules/custom/pku_dialogflow/js/dialogflow.js?v=8.7.3:3009
    o https://fakedomain.pl/modules/custom/pku_dialogflow/js/dialogflow.js?v=8.7.3:1
    <anonimowa> https://fakedomain.pl/modules/custom/pku_dialogflow/js/dialogflow.js?v=8.7.3:1
    <anonimowa> https://fakedomain.pl/modules/custom/pku_dialogflow/js/dialogflow.js?v=8.7.3:1

Hmm, I am guessing this is something has to do with Firefox not supporting some regex function that you are using.
Have you got a chance to look at these answers?
https://github.com/sindresorhus/ip-regex/issues/24#issuecomment-408477416
https://stackoverflow.com/questions/55774080/firefox-gives-syntaxerror-invalid-regexp-group

@munkhuushmgl I've read above too and much more other answers. I don't use any regex in my code. As I guess it is used in google-gax which is used by @google-cloud.

@marast78 I will ask the product team about supported browsers and usage of regex

Hi folks,
We don't officially support any browsers in this library, but we try to make it work (in a fallback mode - with no streaming calls and OAuth2 instead of service account files).
I don't have Firefox installed locally, would you @marast78 please help me by pointing me to a failing regex in google-gax? (even a screenshot would work) I'm pretty sure I will be able to rewrite it to make everyone happy.
(if it's hard to point to a specific regex, it will take longer for us to debug the problem (but I'll still do my best here).
Thank you!

@alexander-fenster I will try to help you in this case. Perhaps at the weekend, I will find some time for it :+1:

@alexander-fenster I can confirm that in version 78.0.1 it works fine, so it seems like Firefox developers fixed this issue. I think we can close this issue.

Thank you for checking @marast78!


Add AQUA_TLS_VERIFY Environment Variable

Signed-off-by: Mohammad Fahim Abrar<EMAIL_ADDRESS>

Is this fixed everywhere? I still note many references to hard-coded TLS set to off.
Of course the vendor folder is not relevant, but all the others are spread between registry and notification definitions (where sensitive credentials are being passed). It appears that the environment variable is not being respected in those places?
`
terraform-provider-aquasec git:(main) ✗ grep -rinoI "InsecureSkipVerify: true"
vendor/github.com/parnurzeal/gorequest/gorequest.go:598:InsecureSkipVerify: true
client/registries.go:48:InsecureSkipVerify: true
client/registries.go:75:InsecureSkipVerify: true
client/registries.go:100:InsecureSkipVerify: true
client/registries.go:119:InsecureSkipVerify: true
client/registries.go:134:InsecureSkipVerify: true
client/notifications.go:32:InsecureSkipVerify: true
client/notifications.go:52:InsecureSkipVerify: true
client/notifications.go:71:InsecureSkipVerify: true
client/notifications.go:97:InsecureSkipVerify: true
client/enforcers.go:86:InsecureSkipVerify: true
client/enforcers.go:113:InsecureSkipVerify: true
client/enforcers.go:137:InsecureSkipVerify: true
client/enforcers.go:158:InsecureSkipVerify: true
client/enforcers.go:174:InsecureSkipVerify: true
`


qt wallet periodically request all outputs.

It is an issue with miner wallet that has 300k outputs.

required updates from mwc-wallet


Use Sass Bootstrap by default

Please discuss over at https://discourse.roots.io/t/switch-to-bootstrap-sass-as-the-default/3617.

shipping in the morning :eyes:

:eyes:


Update DEFAULT_DAEDALUS_BRANCH for osx

Not sure if master is the best option, but it is better than cardano-sl-0.4.
Please let me know if you'd prefer a different branch as default.
PS: I also made the script executable (u+x).

Thanks! this will be removed in https://github.com/input-output-hk/daedalus/pull/789


docs(agents-kit): extend version numbers. clarifiy standard versions.

Description
Address issues that have come up in the QG4.
Pre-review checks
Please ensure to do as many of the following checks as possible, before asking for committer review:

[x] Copyright and license header are present on all affected files

@maximilianong this PR contains/confirms the final version numbers for CX 23.12 Would be nice, if we could merge it before the 8th of Dec ;-)


extend ci

extracting the useful bits from #5
@LoyVanBeek FYI

this fails with the expected failure
@LoyVanBeek  is currently investigating this in #7


fix: rostest melodic import error

This PR fixes the several issues happens your PR. @Kanazawanaoaki
If this change is OK for you, please manually merge this branch by
git merge {whatever-ishida-remote-name}/fix/rostest_melodic

If you don't set whatever-ishida-remote-name yet, please do
git remote add h-ishida https://github.com/HiroIshida/mohou_ros
git fetch h-ishida

to reflect my branch to your local.
fix tf2 import error in gazebo
https://github.com/HiroIshida/mohou_ros/pull/34/commits/f82b70b2fe1e76764daf55d0a388dc9af2534e7f
the problem can be circumvented by changing the shebang from python2 to python3
use https://github.com/HiroIshida/gazebo_ros_pkgs/tree/tmp/fix_shebang_to_python3
And added the modified repository to the rosinstall.melodic file as a source dependency and build it
fix rostest not found problem
https://github.com/HiroIshida/mohou_ros/pull/34/commits/33b0e4d48f641dfc1c1e65194a8f3bcc382f52dd
When comparing the python path by python -c "import sys; print(sys.path)", it seems that somehow in the github action, /opt/ros/melodic/lib/python2.7/dist-packages cannot be found, although that can be found in docker container for melodic. As a ad-hoc workaround, I manualy add the path and export PYTHONPATH
the comparison
https://github.com/HiroIshida/mohou_ros/pull/34/commits/a3ecedda827d37bd5dc8e0559cf0e31d6a989bce
In github action
2022-08-02T15:25:59.7021993Z ['', '/home/runner/work/catkin_ws/devel/lib/python3/dist-packages', '/opt/ros/melodic/lib/python3/dist-packages', '/usr/lib/python36.zip', '/usr/lib/python3.6', '/usr/lib/python3.6/lib-dynload', '/home/runner/.local/lib/python3.6/site-packages', '/usr/local/lib/python3.6/dist-packages', '/usr/lib/python3/dist-packages']

In docker container
h-ishida@419ba90f624e:~/catkin_ws/src/gazebo_ros_pkgs$ python3 -c "import sys; print(sys.path)"
['', '/home/h-ishida/catkin_ws/devel/lib/python3/dist-packages', '/opt/ros/melodic/lib/python3/dist-packages', '/opt/ros/melodic/lib/python2.7/dist-packages', '/usr/lib/python36.zip', '/usr/lib/python3.6', '/usr/lib/python3.6/lib-dynload', '/home/h-ishida/.local/lib/python3.6/site-packages', '/home/h-ishida/catkin_ws/src/scikit-robot', '/usr/local/lib/python3.6/dist-packages', '/home/h-ishida/catkin_ws/src/mohou_ros', '/usr/lib/python3/dist-packages']

The difference is that on the github action, somehome opt/ros/melodic/lib/python2.7/dist-packages is not included in sys.path
Fix SVD error
https://github.com/HiroIshida/mohou_ros/pull/34/commits/812169714ae59f397512b3e125c73066cd6dc71d
This fix is bit out of the target of the PR, but I fixed the issue by not augmenting the LSTM dataset.

Thank you very much for your detailed explanation.
Considerations for rostest not found problem
I added python -c "import sys; print(sys.path)" to the original test/rostest_executor branch to check the python path.
in https://github.com/HiroIshida/mohou_ros/pull/35/commits/0ebbf50efc402ce02d5d962e247c105e6b8c3ba4 github action's result
['', '/opt/ros/melodic/lib/python2.7/dist-packages', '/usr/lib/python36.zip', '/usr/lib/python3.6', '/usr/lib/python3.6/lib-dynload', '/home/runner/.local/lib/python3.6/site-packages', '/usr/local/lib/python3.6/dist-packages', '/usr/lib/python3/dist-packages']

in https://github.com/HiroIshida/mohou_ros/pull/35/commits/8041faa8a044e3194bbe0632c553286960c511d5 github action's result
['', '/opt/ros/melodic/lib/python3/dist-packages', '/usr/lib/python36.zip', '/usr/lib/python3.6', '/usr/lib/python3.6/lib-dynload', '/home/runner/.local/lib/python3.6/site-packages', '/usr/local/lib/python3.6/dist-packages', '/usr/lib/python3/dist-packages']

It seems that the path disappears when python3 is configured in github actions, and this problem seems to occur in both catkin_make and catkin build.


Update plugin to support Drone 0.5

Code changes to support running plugin in a Drone 0.5 environment.

@tboerger Just curious if you had time if you'd mind to review this for me.  😄


If an en passant leads to check for the side playing the move, it doesnt prevent it.

Lazy to fix it so will do later if I have time

Fixed it:D


Question: Installing without nodejs dependency

I was wondering if there was a way to use this cookbook without the nodejs dependency. I'm using the nvm cookbook to install node and would like to install pm2 for the version of node I designated there. Any ideas?

It isn't possible at it is, but it should be trivial to have a feature guard to enable/disable the installation of node system wise.
Let me get #20 merged first (because it heavily changes the way the runtime and node packages are installed) and I'll have a stab at this.

Amazing! Thanks @miguelcnf


Migrate multiselect into design system

Changes

Migrates the multiselect to the design system from the cf.gov repo.
Replaces Event mixin with EventObserver and refactors code so that components that use AtomicComponent and those that don't can both use the same event API. This changes on to addEventListener, off to removeEventListener, and trigger to dispatchEvent.
Adds getRegisteredEvents method to EventObserver to satisfy test that checks what events are registered.
Migrates dom-events and dom-traverse utilities into design system.

Testing

gulp test should pass.
In the PR preview, components > Dropdowns and multiselects page should have an error-free, functioning multiselect.

Screenshots

These PRs should go in first:

https://github.com/cfpb/design-system/pull/1095
https://github.com/cfpb/design-system/pull/1094


Incorrect gas estimation causing OutOfGas error

Overview
When sending transactions for the precompile pallet-parachain-staking, gas estimation is not working for some calls. We also realized that gas estimation is incorrect for other pallets as well, as described here.
Details
When sending the delegate action using Remix + Metamask, the pallet-evm raises an OutOfGas error, as shown in the PolkadotJS UI:

However, when performing the same action using web3 libraries, the issue does not occur. Setting a fixed amount of gas allows the process to work fine. The problem is that Metamask sets the gas amount by retrieving the value from a previous call to eth_estimateGas. The estimation returned for the delegation call is 101433, but the actual gas consumption for delegation is 220440. As a result, when using Metamask, the gas value is lower than the actual gas used, causing the call to run out of gas and resulting in the OutOfGas error from pallet-evm.
The workaround is to set a sufficiently high fixed gas amount to ensure the transaction does not run out of gas during execution.
A brief investigation revealed that Moonbeam forked all EVM-related projects and introduced the concept of storage growth related to gas, as described here. Further investigation is needed to determine whether the discrepancies in estimation are due to this.
Other calls that ran out of gas:

delegateWithAutoCompound
delegatorBondMore
scheduleDelegatorBondLess
scheduleRevokeDelegation
cancelDelegationRequest
executeDelegationRequest
candidateBondMore
executeCandidateBondLess
goOnline
goOffline

Environment

Frontier version: branch polkadot-v1.11.0

Expected Behavior
As a Metamask (or any web3 tool) user, I want to perform all EVM actions using the gas value obtained from estimation, without needing to set a fixed value to prevent running out of gas. Standard online tools should work out of the box.

This has also become an issue for pallet-evm on the Neuroweb parachain after updating Frontier from branch polkadot-v0.9.40 to branch polkadot-v1.11.0.
On older version it was working just fine, so this bug was introduced with one of the reworks for gas estimation that I see happened.

#1257 fix the issue. It was included in polkadot-v1.12.0

This PR fixes some issues with eth_estimateGas, you can try to see if it solves the problem.
It is in polkadot-v1.12.0

@zjb0807 but this PR is included on the polkadot-v1.11.0 branch?

This issue seems to have a major impact. Basic user interactions (e.g. sending ERC20 tokens through Metamask) are mostly non-operational. From a user perspective, the tokens will seem locked and unusable, and this definitely requires an escalation.
Apart from an (urgent) fix to this, I suggest an e2e test be created with at least one major wallet which is added into the CI/CD pipeline.

This PR fixes some issues with eth_estimateGas, you can try to see if it solves the problem. It is in polkadot-v1.12.0

@zjb0807 I have upgraded to stable2407 as polkadot-v1.12.0 brings some errors. The estimation problem still persists, as you can see in this test. It can be seen that the estimated value is still lower than the 220440 gas needed..
Any idea what is going on here?

Sorry for the delayed response. I've been a bit busy lately. I believe the issue you're encountering is due to missing something in the runtime during the upgrade. I took a quick look at your repo, https://github.com/freeverseio/laos/blob/main/runtime/laos/src/apis.rs, and noticed that the EVM call and create differ from the Frontier template node. You can check it here: https://github.com/polkadot-evm/frontier/blob/stable2407/template/runtime/src/lib.rs#L786-L864. You can revise them and then give it another attempt.
Tips: While upgrading the polkadot-sdk, you need to review all the changes that occur instead of relying solely on the compile results.

@boundless-forest that was exactly the problem. It is working now, even with the polkadot-v1.11.0 version. Thank you so much!


Related issue 90 feat: add focus when search field was opened

https://github.com/StaticMania/keep-react/issues/90 Focus on search input when modal open, improving ux. Add a ref on TextInput to focus.

Hey @gfpaiva,
Big thanks for adding the auto-focus feature to our keep-react project! 🚀 Your contribution is awesome and enhances the user experience. We appreciate your dedication!
If you have more ideas, Please share with us. Looking forward to more collaborations!
Cheers,
@Arifulislam5577


this.msalBroadcastService.inProgress$ subscribe event called twice

Core Library
MSAL.js v2 (@azure/msal-browser)
Core Library Version
2.14.1
Wrapper Library
MSAL Angular (@azure/msal-angular)
Wrapper Library Version
2.0.0
Public or Confidential Client?
Public
Description
Inside subscribe of  this.msalBroadcastService.inProgress$, I am calling my API code.
but this subscribe event is always called two times when user logs in. Please suggest how should I avoid twice/duplicate calls?
this.msalBroadcastService.inProgress$
.pipe(
filter((status: InteractionStatus) => status === InteractionStatus.None),
takeUntil(this.onDestroy$)
)
.subscribe(() => {
this.checkAndSetActiveAccount();
});
Error Message
No response
Msal Logs
No response
MSAL Configuration
NA

Relevant Code Snippets
ngOnInit() {
    this._logger.logMessage('Inside init');
    this.isIframe = window !== window.parent && !window.opener;

    this.notifyService.getPerksOfficeID.subscribe(value => {
      this.perksOfficeID = value || EaStore.getValue('perksOfficeID');
      this._logger.logMessage('OfficeID from Perks: ' + this.perksOfficeID);
    });

    this.msalBroadcastService.msalSubject$
    .pipe(
      filter((msg: EventMessage) => msg.eventType === EventType.LOGIN_SUCCESS || msg.eventType === EventType.ACQUIRE_TOKEN_SUCCESS),
      takeUntil(this._onDestroy$)
    )
    .subscribe((result) => {
      this._logger.logMessage('On Login success ' + result);
      const payload = result.payload as AuthenticationResult;
      this.msalService.instance.setActiveAccount(payload.account);
    });

    this.msalBroadcastService.inProgress$
      .pipe(
        filter((status: InteractionStatus) => status === InteractionStatus.None),
        takeUntil(this.onDestroy$)
      )
      .subscribe(() => {
        this.checkAndSetActiveAccount();
      });
  }

Reproduction Steps

Login to you app
enter user id and pwd
At this point subscribe event of  this.msalBroadcastService.inProgress$ is called twice

Expected Behavior
subscribe event of  this.msalBroadcastService.inProgress$ should be called only once
Identity Provider
Azure AD / MSA
Browsers Affected (Select all that apply)
Chrome, Edge
Regression
No response
Source
External (Customer)

@SGeorge007 Can you provide your configuration (how you are setting up your app in app.module.ts) and also provide verbose logs showing where the two calls are happening?


Scope of "Replicate"

Replicated tables exist in ASA, not sure why the page says "REPLICATE only applies to Parallel Data Warehouse."

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

ID: adf0e9a7-a1d8-aa28-5806-9bc25dd280ba
Version Independent ID: 85f18545-84c2-f810-a70e-74ea8b4a0d3d
Content: sys.pdw_table_distribution_properties (Transact-SQL) - SQL Server
Content Source: docs/relational-databases/system-catalog-views/sys-pdw-table-distribution-properties-transact-sql.md
Product: sql
Technology: data-warehouse
GitHub Login: @ronortloff
Microsoft Alias: rortloff

thanks for the feedback.  this is fixed in pr13085.

#please-close


[#33] fix tests

Updated tests to work with the updated pydantic models.

@Maurier Most changes in this PR are related to tests. There is only minor changes to schema models. If you can review the schema model changes that would be great.

@Maurier I assume it's ready for your approval.


Rating count doesn't appear on thumbnails anymore

As said in the title, I have the rating count to be always visible on the video thumbnails, but now suddenly they all show 0 likes and 0 dislikes, even though the videos clearly have likes and dislikes.
ex:

Seems like the rating data from the gdata request doesn't exist. Wonder if it will reappear or if it will be forever gone.
The request YouTube Center makes:
https://gdata.youtube.com/feeds/api/videos/{VIDEO_ID}?v=2&alt=json
Here's an example:
https://gdata.youtube.com/feeds/api/videos/cv8msHbqaFE?v=2&alt=json

Switching to V3 fixes this issue. An option have been created to use V3 in the settings where you also can use your own API.

@YePpHa gdata v2 is supposedly deprecated as per the last year's announcement, now only v3 exists. Will the quota limits be sufficient for this kind of software application?

So the bug is fixed in a new version? is is released?

I'm sorry, where can I find the option to switch to v3? thanks a lot.

found it in general settings. works like a charm.

@Yonezpt True, but you can still use the v2 API somewhat. Though, they did remove the rating statistics yesterday and later they might remove other things too.
I have looked at the graph for today's requests and the quota limit seems to be sufficient for the time being. Today, there has been a total of ~400,000 requests out of 50,000,000. If the quota becomes an issue users can use their own API keys or I might look into increasing the quota.
Here's a little screenshot with a graph and stuff:

Another measure to take if the quota doesn't suffice, would be to change the default to only load the rating data on hover.


Define specifics of prototype workflow

We need an area (specified as a bounding box) that has several (say, 15) NPN stations which are covered by more than one MODIS and Daymet pixels.
Furthermore, we need:

One (or more) species or family of interest
List of variables/bands/products of interest from MODIS and DayMet.

dataset: rnpn
functional_type: "Deciduous broadleaf"  # multiple species
phenophase: [371,373]  # breaking leaf buds (371,373)
years: [2007, 2018]
area:
  name: Washington # 500km boundingbox centered at latitude: 47.751076 and longitude: -120.740135
  bbox: [-124.08406940413612,45.50277198520317,-117.39620059586387,49.99938001479683]

See https://github.com/phenology/springtime/blob/main/src/springtime/recipes/model_comparison_usecase.yaml


When Command Bar is opened, it behaves as a modal dialog and anything under it is not clickable.

Describe the bug

See sample app at \scratch2\scratch\rnichols\CommandBarFlyout.zip that repros the same issue trivially with WebView.  WebView doesn’t react at all to input while the flyout is up – including mouse hover.
Steps to reproduce the bug

Steps to reproduce the behavior:

Go to '...'
Click on '....'

Expected behavior

Screenshots

Version Info

NuGet package version:

Windows 10 version
Saw the problem?

Insider Build (xxxxx)

October 2018 Update (17763)

April 2018 Update (17134)

Fall Creators Update (16299)

Creators Update (15063)

Anniversary Update (14393)

Device form factor
Saw the problem?

Desktop

Mobile

Xbox

Surface Hub

IoT

Additional context

@alanlai-ms - the behavior you describe is by design to help constrain the area of user input (open CommandBar also traps keyboard focus). You're right that CommandBar is a bit of a strange hybrid - not quite light dismiss (can't be dismissed by clicking outside it) and not fully modal (will close on pressing Escape). We generally expect CommandBar to be closed the majority of the time, which eliminates this input-blocking behavior. Do you have a specific scenario that's making CommandBar's default behavior painful?

@YuliKl , when people right click on an app, Let say OneNote and the Context Menu is opened.
At this state, user found out that the command they want is not actually in the Context Menu but in the Ribbon.
They click "once" on the actual button on the ribbon and fully expect it to trigger the action.
It doesn't.
Now user requires 2 clicks, 1st to dismiss CommandBarflyout 2nd click finally triggers the action from ribbon.

I think generally when context menu is opened, user expect clicking on a different area, and input would fall thru.

Light dismiss swallows the first click. Meaning, when a light dismiss menu or flyout is open, clicking outside the menu/flyout dismisses it but the click does not pass through to the underlying UI. Users need one click for the light dismiss and a second to activate the UI. The purpose of this mechanism is to reduce accidental activations and ensure that light dismiss clicks feel safe to users. There's more discussion about light dismiss in our docs.
For scenarios where single-click-to-dismiss-and-activate are critical, you can use the OverlayInputPassThroughElement property. Although this property is on FlyoutBase and I believe isn't available for CommandBar's overflow menu.

Maybe the CommandBarFlyout shouldn't be a light dismiss surface then if light dismiss surface is defined that way?
Reason

CommandBarFlyout, to a user is just a context menu, and in a context menu, say if you try in Window Explorer, when it is opened and you click somewhere else, that click registers as click

The concept of CommandBarFlyout isn't new, it has been around in Office Win 32 apps. In those apps, when the menu is opened and you click somewhere else, that click registers as click.

CommandBarFlyout, to a user is just a context menu, and in a context menu, say if you try in Window Explorer, when it is opened and you click somewhere else, that click registers as click

Yes, and that's a pain.. to close a context menu i must always be careful to click on an 'empty space', otherwise i can trigger an action that i don't want.
I think that light dismiss is a correct and modern paradigm, also most of the user came from mobile&web experiences where it's the norm.
But if the developer wants to turn-off the feature it should be possibile.

What web experiences you are referring to where it's the norm?
On chrome, when I right click and then left click somewhere else, that 1st left click registers as click.
Going to ignore mobile (ios/Android) as we are using a mouse here and those are touch/pen devices.

What web experiences you are referring to where it's the norm?

Here in github when you open a 'command prompt' (eg: click the '...' in the top right of this message) and click to dismiss the click is 'swallowed'.
I see this pattern used a lot (ok, is not the 'norm') because i think that is simpler, it doesn't require a 'conscious' effort to close (the quantity of empty space is not the problem, the problem is that you must 'search' for it).
But if you want this feature turned-off the framework should let you, in this i'm with you.
And then let an A/B test decide what your users prefer ;) .

The problem with letting the developer decide whether a light-dismiss click gets swallowed or passes through is that the user doesn't know what to expect. We don't provide any affordances for the user to know whether their click is safe or they need to search for empty spaces in order to dismiss the menu. So to avoid user confusion, Xaml framework implemented the point of view that light dismiss layers swallow the first click.
@alanlai-ms - if you feel strongly that the Xaml light dismiss behavior needs to be changed, please open a new issue and include the justification.


DopePunks Club

inscriptions.json & meta.json for inclusion via pull request. Apologies if this isn't quite right yet. I'm willing to make any amendments required. Thanks

Hi, looks like there may be a problem with this.
How do I find out what to do next?
It would be really useful to know whether this pull request is in a queue.
Thanks!

close pr. reason: invalid id (wrong id / too short). please hand in a pull request including id metadata. Thank you for your understanding.

Thanks Chris, I think I've corrected the problem. Just having an issue creating a new pull request. I keep being sent to this page: https://github.com/ordinals-wallet/ordinals-collections/compare
Any pointers on how I resubmit please?


Node SSR: List js

Is there .a way to get list to run in node, server side, and emit only html?
(else I'll do it w/ http://stackoverflow.com/questions/12708394/how-to-auto-bind-collection-from-html-form-using-node-js-express-framework
and w/ https://www.npmjs.com/package/cheerio )

Not that I'm aware of and it's not something I plan to support at the momen :/


Feature/case custom errors

Description of Change

When trying to create or update a case with an invalid assignee or subject will now result in a custom error
Updating a case with a name that already exists will result in a custom error. (This error was already present for create_case() but I made the logic shared with the update_case() method).

Issues Resolved
n/a
Testing Procedure
Call the update_case() or create_case() with invalid assignee or subject or duplicate name (update only) and witness the custom errors.
PR Checklist
Did you remember to do the below?

[x] Add unit tests to verify this change
[x] Add an entry to CHANGELOG.md describing this change
[n/a] Add docstrings for any new public parameters / methods / classes

I'd like to hold off on testing until after the next release


NextJS deployement failed: [ERROR]: {"code":"7","message":"No ssrResources.json file"}

Before opening, please confirm:

[X] I have checked to see if my question is addressed in the FAQ.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

App Id
d10qoyiwa3p4ur
AWS Region
ap-south-1
Amplify Hosting feature
Build settings, Deployments
Describe the bug
I've a couple of Next JS application deployed on AWS amplify with separate AWS profiles, and all of them started failing 2 days ago (i.e, 2nd Nov, 2022). Surprisingly, the already deployed branches, if re-deployed, are being re-deployed fine but any new branch when deployed, gets failed in the "Deploy" part of the deployment. Provision and Build phases do succeed though.
My guesses are NextJS version update might be an issue, currently we're using NextJS version 12 and in the package.json, I've restricted the version to 12. My applications currently aren't having SSG components/pages.

********* IMAGE OF DEPLOYMENTS ERRORS ARE ATTACHED ************
Expected behavior
The Next JS app should be deployed successfully because it doesn't have any errors in the build phase
Reproduction steps

Create a Next JS application
Deploy it on AWS amplify
Amplify shoes an error on the Deployment phase

Build Settings
No response
Log output

# Put your logs below this line

2022-11-04T06:51:00 [INFO]: Beginning deployment for application d10qoyiwa3p4ur, branch:feature/FM-69-auth-module, buildId<PHONE_NUMBER>
2022-11-04T06:51:01 [INFO]: Cannot find any generated SSR resources to deploy. If you intend for your app to be SSR, please check your app Service Role permissions. Otherwise, please check out our docs on how to setup your app to be detected as SSG (https://docs.aws.amazon.com/amplify/latest/userguide/server-side-rendering-amplify.html#deploy-nextjs-app)
2022-11-04T06:51:01 [ERROR]: {"code":"7","message":"No ssrResources.json file"}

Additional information

Hi @Hamza141999 👋🏽 it looks like your app is not being detected as using the Next.js framework. You can fix this by running this AWS CLI command:
aws amplify update-branch --app-id <APP_ID> --branch-name <BRANCH_NAME> --framework 'Next.js - SSR' --region <REGION>
Please note that this command updates the framework for one branch; you will have to run this command for any branch that you're experiencing this behavior with. Usually customers run into this error when they were previously using SSG. Was this app recently switched from SSG to SSR?

Hey @hloriana, thank you for replying. No it wasn't actually. Quite surprisingly when I merge a PR of a branch into already deployed branches, they get deployed fine, but whenever i'm trying to deploy a new branch, it gets failed somehow. So the issue arrises only in the newly deployed branches, the old ones get deployed with changes just fine.
There were no changes made in terms of the web app being switched from SSR to SSG or vice-versa

Hi @Hamza141999 thank you for providing further details regarding this bug. We are still working on root causing why Amplify is not detecting new branches as SSR in your apps and will update you once we have further information.
Have you tried running the update-app command I recommended to work around this behavior? This should resolve the issue for you while we continue to investigate.

Hi, we are facing the same issue which prevent us to deploy any new branch on Amplify...
Nothing was changed recently in the configuration. Is it something related to the new version of Next released?

@hloriana any updates with the issue?

@hloriana i tried running the update command u asked me to, but weirdly so, it threw an error saying app not found with the app-id I typed in. I attached the image of the log so you may review it

@Hamza141999 Maybe double check your appId. I can successfully run that command.
@hloriana This is what I've tried without any success.

run the update-app command successfully, the CLI returns among other info "framework": "Next.js - SSR".
Created and set a new Amplify service role.
Forking and deploying other branches.
Pinning amplify at 9.1.0
Tried tons of different amplify.yml. I've read amplify does magic stuff with guessing the framework (.next artifacts.baseDirectory combined with the build commands in package.json)

Any more ideas?

Hi @jbreemhaar 👋🏽 apologies for this inconvenience. Can you provide your App ID as well? We are continuing to investigate this behavior and are working to find a resolution for this issue. Unfortunately we cannot reproduce this issue so any additional information you may have around when this behavior started for you or any significant app changes made to your app around the time this started will be helpful as well.

Hi @hloriana! AppId is deu8uyp1wcls7.
So my temp fix for now is to remove SSR stuff from my next app, and build it as a SSG app. The error being thrown ("No ssrResources.json file) might be kind of off, because you'd expect something being wrong with a SSR build but Amplify seems to be expecting an SSG build. There seems to be no way to force Amplify to recognise it as SSR.
I'm able to have it running as SSG as my previous "normal" setup and the yarn workspaces setup. I'd really like to have SSG running again though :)
This problem started occurring 5 days ago. This has been the first "real" error occurred though, I've been trying to move into a monorepo/workspaces setup since november 1st and noticed my changes weren't being deployed. Which is not that weird, since I've probably misconfigured tons of stuff in that process.


Sticky table of contents with heading highlighting

Work in progress sticky table of contents with active heading highlighting. I've tried everything I can think of but can't get it to work on reloads. The IntersectionObserver seems to stop calling its callback function a few seconds into the rendering of a new page - can't work out why. If anyone gets a chance to have a look at this it would be much appreciated!
Works on first load:
https://github.com/user-attachments/assets/624cabba-b9b5-477b-b2a9-7f41fba2e9d9
Stops working (either immediately or after a few seconds) on reload or page changes: (video also shows a themeswitcher issue)
https://github.com/user-attachments/assets/9ebf809d-c339-41fa-b835-459177ead5d7


Link on promotiles are not working when "Use link label as title" is chosen

This is also affecting pages where we have used promotiles, e.g. the careers page, which is one of our most visited and important pages. Also tested at the top of this page: https://studiov3-global-development-equinor-web-sites-dev.c2.radix.equinor.com/global-development/desk/topicContent;d0b57050-7f22-434d-97b3-ceb8324719e1
Private Zenhub Image

Duplicate of #1919


Remove all events from engine

Description
Removes the ChannelUpdated event from the engine and thus stops the engine from being an EventEmitter.
This means the engine is a simple request/response model that is much easier to deal with.
This causes the directly funded chain test to fail, so it has been skipped for now and will be re-enabled after the chain service is removed from the engine. (See https://github.com/statechannels/statechannels/issues/3548, https://github.com/statechannels/statechannels/issues/3549 )

Checklist:
Code quality

[x] I have written clear commit messages
[x] I have performed a self-review of my own code
[x] This change does not have an unduly wide scope
[x] I have separated logic changes from refactor changes (formatting, renames, etc.)
[x] I have commented my code wherever necessary (can be 0)
[ ] I have added tests that prove my fix is effective or that my feature works, if necessary

Project management

[x] I have applied the appropriate labels
[ ] I have linked to all relevant issues (can be 0)
[ ] I have linked to all dependent issues (can be 0)
[ ] I have assigned myself to this PR
[x] I have chosen the appropriate pipeline on zenhub for the linked issue

@andrewgordstewart I'm going to merge this into my feature branch. It's starting to get stale and I think I've addressed most of the concerns?

Sounds good!


Permit identity provider (name or id) in CognitoAuth.getCognitoConstants()

Are you up for pull requests?  I would like to specify an Identity name or id in the getCognitoConstants() method and have the user skip the identity provider selection process (cognito hosted UI) and instead make sure the  /authorize endpoint routes directly to a specified identity_provider login as detailed in the authorization endpoin docs.
It would probably be one line of code really in that method as well as the method that builds the FQDN.

Thanks for the comment. You can go ahead to send a pull request. We will later review your added code and decide to merge or not.

#22 should already solve this.

Thanks!


kiss: switch to blake3 checksums

As discussed in kiss-community/repo#100 and #39, we seem to be in favor of switching to blake3.
The following changes are made:

All newly generated checksums are blake3
The user is prompted to generate blake3 checksums if sha256 sums are present (maybe this should be automatic)
For installed packages, we can fall back to sha256 to check etcsums

This includes a name change of the checksums and etcsums files -- I'm not sure of any better way to detect whether sha256 sums are in use, as blake3 sums are the same length.
Feedback is appreciated

ping @illiliti @git-bruh @ehawkvu

https://libera.irclog.whitequark.org/kisslinux/2022-09-16#32978437;

LGTM. We can reclaim 32-byte hash later after some reasonable time.

Before this is merged, do we really want the package manager to die if it detects the wrong type? Otherwise it looks good to me too

Could we not simply keep the filename and check if it's b3 or sha, and then after a while drop the Sha code? I still don't like changing the name...

Before this is merged, do we really want the package manager to die if it detects the wrong type?

What should it do instead?

Could we not simply keep the filename and check if it's b3 or sha, and then after a while drop the Sha code? I still don't like changing the name...

Yes, this is what the latest commit does. At first, I wasn't sure how to tell the difference, but @illiliti suggested changing the digest message length of the b3 sums.

Before this is merged, do we really want the package manager to die if it detects the wrong type?

What should it do instead?

I think a warning would suffice.

I think a warning would suffice.

I'm not sure it will. Unless the verification takes exceptionally long, the warning would be on screen for a second or two. The quicker we can move everyone over to blake3, the better.

@ioraff That's fair - did you have a hard deadline in mind for the switch to blake3 (when we stop passing the -l 33 to bsum)?

Not really. Probably once all of the repos that are in wide use switch over