Merge monaco-jsonrpc and vscode-ws-jsonrpc into new sub package

This resolves #367.
Releases will continue as vscode-ws-jsonrpc. I am currently unable to do a dev release. That will change latest on Monday. 🙂

dev version is now available:
https://www.npmjs.com/package/vscode-ws-jsonrpc/v/0.5.0-dev.0

Btw, What about releasing a 1.0.0?

Yes, that makes sense. I wanted to compare the real npm package contents before doing a next release. I need to verify I did change the content accidentally.


New sampler interface.

Although I think there is still room for discussion except for I commented (ex: It took me a little time to understand how sample_relative method should I use, but I couldn't point it out because I don't have the idea more understandable.), It looks this sampler provides enough functionalities to write GPEI sampler. Good job @sile :+1:


Disable/hide button when not viewing Github repository

Another feature idea!

That, I don't know how to do. I was thinking of graying the icon, but I don't know how to do either :-(


docs: Fix toArrayBuffer example in Frame Processor Guide

What
This PR fixes an issue on the Frame Processor page in the guide which shows an ArrayBuffer being indexed directly without first creating a view into the buffer with a Uint8Array.
Before:

After:

Changes
Updates the toArrayBuffer example on the Frame Processor guide page to match the correct example on the function's API documentation page

Tested on
Firefox

Related issues
N/A

Amazing thank you!


[gh387] Tweak the Request test, eager load the app on CI

Close https://github.com/nimblehq/rails-templates/issues/gh387
What happened 👀
1/ Eager load the APP on CI -> Slack discussion
Insight 📝
1/

2/ Refactor the Github workflow naming a bit
I was a bit confused with the Github workflow naming so I adjusted it a bit, now it looks like

Proof Of Work 📹
On the file changes tab

The formatting and rspec config changes could have been done in separate chore pull requests 🙈 Otherwise, the change is good 👍

@olivierobert I removed the Request test in https://github.com/nimblehq/rails-templates/pull/388/commits/023ed000f2ba888b9ab8f274ed49f18fe0e35308, will move it to the separate PR


Exception: Google Maps API key over requests limit.

2016-08-16 16:51:45,993 [       cli] [INFO] PokemonGO Bot v1.0
2016-08-16 16:51:45,996 [       cli] [INFO] Configuration initialized
2016-08-16 16:51:46,020 [PokemonGoBot] [INFO] [set_start_location] Setting start location.
Traceback (most recent call last):
File "C:\Users\user\bot\pokecli.py", line 609, in
main()
File "C:\Users\user\bot\pokecli.py", line 149, in main
raise Exception("Google Maps API key over requests limit.")
Exception: Google Maps API key over requests limit.
2016-08-16 16:51:50,198 [       cli] [INFO] PokemonGO Bot v1.0
2016-08-16 16:51:50,214 [       cli] [INFO] Configuration initialized
2016-08-16 16:51:50,230 [PokemonGoBot] [INFO] [set_start_location] Setting start location.
Traceback (most recent call last):
File "C:\Users\user\bot\pokecli.py", line 609, in
main()
File "C:\Users\user\bot\pokecli.py", line 149, in main
raise Exception("Google Maps API key over requests limit.")
Exception: Google Maps API key over requests limit.
any one know how to fix this error?

This just means that you have exceeded your 2,500 API request limit quota set by Google. You have to pay a subscription fee to get a higher limit. Each day this resets, so you should be fine in 24 hours. But, if you want to continue botting just remove the Google API key. You should be fine, but just add it back tomorrow.

i am not using google api key :\


Feature/dispatcher

Merge feature branch into dev

@jbagga,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by .NET Foundation. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot


Prevent re-render of whole DOM on set_state

Options would be to only render the section of the dom tree below where state changes or go full on reconciliation algorithm.


including ability to read phase3A neuropixel arrays

With the latest version of spikeinterface the ability for probe interface to read the metadata from phase3A neuropixel arrays (documented by Bill Karsh here) was lost. I have added a section to the code in order to allow these files to be read once again.

Hi.
Thanks for the patch.
Do you have a meta file we could include here in the test folder and run some tests on it ?
@alejoe91 : could you also check.

@rtraghavan it would be great if you have a test file! So we can include it the tests!
Note that we are planning to make a release on Friday, so let us know if you can provide a file by then :)
In that case we'll include this in the release!

@rtraghavan we are merging for the new release, but it would be great if you can provide a test file to implement some tests.
#138

Regarding request for a test file. Here you go.
test_file_g0_t0.imec.ap.meta.txt

Hi thanks for the file.
How can we know from the file that it is a imDatPrb_type=2018 ?
In your patch youd did [_,imDatPrb_type,num_contact] = list(map(int, headers[1:].split(','))).
But I think this imDatPrb_type is not the good one (3 in  the file).
So you hard coded the 2018 but this look like quite a bit unsafe we could have other case with other logic, no ?

The only way to know from the file that it was a phase 3a probe is that the length of the first entry of the imroTbl is 3. That middle number references one of four options that imec 3a probes were offered. My choice of 2018 referenced the last year of those probes being offered. One could also flag it as 58, the hexadecimal conversion for 3a, as 3.0 should probably be reserved for newly introduced 3.0 4 shank probes. As far as I understand, the difference in options is not of consequence to the parser, as the intersite spacing was similar. From Juvainett et al. 2019
Probe options 1 and 3 are passive and contain 384 (5 mm long shank) and 960 sites (10 mm long shank), respectively. Probe
options 2 and 4 are active and contain 384 (5 mm long shank) and 966 sites (10 mm long shank), respectively. To make the code clear and less unsafe,  I push an update that reads the header's length, flags the file as a 3a probe, and then breaks things up by option. I'll need to contact Bill Karsh to ask him, for example, meta files beyond 3a option 3, which is what I deal with most regularly. However, I can push that change immediately.


Fix several broken python packages

Motivation for this change
qutip takes 2 hours to run tests... what would be a better way? Otherwise full test suite enabled on broken packages and all tests pass.
Things done

[X] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

Notify maintainers
cc @

I opened an issue with qutip asking what would be the recommended subset of tests to run such that we can have it complete a build in around 10 minutes. https://github.com/qutip/qutip/issues/1147.

Any progress on this? It looks like qutip moved testing to pytest and have a faster subset of tests that can be run.

Any update on that? I would need qutip.

discordpy qutip and sparse have already been bumped, not sure about the other two

What do you mean by bumped? You mean removed from nixpkgs? If yes any idea why? I'm thinking to bring qutip back.

bumped means updated or brought attention to
they have not been removed
also, this PR is very old by python standards. We should probably close

this has conflicts with most packages. going to close


Rename Person to Food Items and Update delete command

Codecov Report

Merging #44 (2143a46) into master (5906c25) will decrease coverage by 0.11%.
The diff coverage is 85.00%.

@@             Coverage Diff              @@
##             master      #44      +/-   ##
============================================
- Coverage     70.36%   70.24%   -0.12%
  Complexity      376      376
============================================
  Files            70       70
  Lines          1208     1210       +2
  Branches        113      114       +1
============================================
  Hits            850      850
- Misses          319      320       +1
- Partials         39       40       +1

Impacted Files
Coverage Δ

src/main/java/seedu/address/MainApp.java
0.00% <0.00%> (ø)

...java/seedu/address/logic/commands/FindCommand.java
100.00% <ø> (ø)

...a/seedu/address/logic/parser/AddCommandParser.java
100.00% <ø> (ø)

.../seedu/address/logic/parser/FindCommandParser.java
100.00% <ø> (ø)

...in/java/seedu/address/logic/parser/ParserUtil.java
88.46% <ø> (ø)

src/main/java/seedu/address/model/Calorie.java
55.00% <0.00%> (-6.12%)
:arrow_down:

src/main/java/seedu/address/model/Model.java
100.00% <ø> (ø)

...rc/main/java/seedu/address/model/ModelManager.java
100.00% <ø> (ø)

src/main/java/seedu/address/model/food/Food.java
93.75% <ø> (ø)

src/main/java/seedu/address/model/food/Name.java
80.00% <ø> (ø)

... and 15 more

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


initial version of fully working helloworld example

please see line 12. any better solution? thanks

i left my comment on line 11, we can just remove my TODO and add an explanation for defining a flag like that there, or solve the underlying issue inside xain, whichever is best

my TODO comment got merged into master, which is not very clean, should i open a new PR to fix that?


Correct use of Gyroscope Plugin?

Hi There,
Thanks for releasing this library.  It has been a joy to work with so far!
One issue I ran into is this: the Gyroscope plugin (which supports mobile device orientation controls) does not seem to be working as expected.  My app is building correctly, but the plugin is not visible or working on mobile.
Here is a minimal reproduction: https://codesandbox.io/s/react-photo-sphere-gyroscope-plugin-test-klupfk?file=/src/App.js
And here is my code:
import React from "react";
import {
  ReactPhotoSphereViewer,
  GyroscopePlugin
} from "react-photo-sphere-viewer";

function PhotoSphere() {
  const photoSphereRef = React.useRef();

  const plugins = [GyroscopePlugin];

  return (

      <ReactPhotoSphereViewer
        ref={photoSphereRef}
        src={"./bourke-pano.jpg"}
        height={"60vh"}
        width={"100%"}
        plugins={plugins}
      ></ReactPhotoSphereViewer>

  );
}

export default function App() {
  return (

Hello CodeSandbox

Start editing to see some magic happen!

      <PhotoSphere />

  );
}

The gyroscope feature should be available on mobile, but doesn't seem to be.
Please let me know if I should be doing anything differently.
Thanks!

Hello! thanks for your issue. Now I'll check this issue to figure it out

With the current implementation, you have to provide the navbar manually, e.g. navbar={['gyroscope']}

Ok, this is working well! I close

With the current implementation, you have to provide the navbar manually, e.g. navbar={['gyroscope']}

Thank you man!

With the current implementation, you have to provide the navbar manually, e.g. navbar={['gyroscope']}

Hi i'm trying to use Stereo Plugins by this way: navbar={['gyroscope', 'stereo']} but it's not working, any idea for it.

Hi!

This example with gyroscope and stereo is working in my Android phone

Thank you Elius, i checked and it worked fine on Android, but on my Iphone got the error, i guess this error is caused by some policy on Iphone.

Hi! Are you shure that you are running the last version of the library? I
remember that this was an issue in the main library, solved in the current
release.
Il mer 15 feb 2023, 03:16 nguyenvd-3 @.***> ha scritto:

Thank you Elius, i checked and it worked fine on Android, but on my Iphone
got the error, i guess this error is caused by some policy on Iphone.
[image: WhatsApp Image 2023-02-15 at 09 03 33]
https://user-images.githubusercontent.com/55442292/218909780-5da5bf56-d0ee-4457-a497-fde170bcc00f.jpeg
—
Reply to this email directly, view it on GitHub
https://github.com/Elius94/react-photo-sphere-viewer/issues/12#issuecomment-1430656157,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADRXUU3BUHE4VERK6M4BHWLWXQ36VANCNFSM6AAAAAASR7FDLY
.
You are receiving this because you modified the open/close state.Message
ID: @.***>


Any idea how to add Turkish language to apache superset?

Any idea how to add Turkish language to apache superset?

You can also join the Superset Slack #translations channel to get additional help.


Cluster enhancements

added support for scan commands (incl. ScanParams) in JedisCluster.java by sending scan command to Master nodes (only) and merge answers using multiple threads.
fixed bug/type for hscan, sscan and zscan commands in JedisCluster.java
added support for ScanParams for hscan, sscan and zscan in JedisCluster.java and ShardedJedis.java
added/fixed test case for new and changed hscan, sscan, zscan commands and for added scan command
added missing test case for blpop and brpop

@roirex At first, thanks for your effort!
Btw, any cluster enhancements are now in branch, 'cluster-revised'.
PR is here, https://github.com/xetorthio/jedis/pull/671, and we're in progress of reviewing.
In that PR, we removed implementation of BasicCommands from JedisCluster, so some of your enhancements are no longer valid in current.
And empty ip in "cluster nodes" never means localhost.
Please refer https://github.com/antirez/redis/issues/1848, and https://github.com/xetorthio/jedis/issues/699, and https://github.com/HeartSaVioR/jedis/commit/0f472c97a27da62c86444a1c72e599fdb81edf83
So finally, your changeset has invalid implementations, so I'll close this PR.
Please refer 'cluster-revised' branch and apply your effort. Thanks!

Thanks for your feedback. I'll redo my effort in cluster-revised.
However I don't follow you when you say "we removed implementation of BasicCommands from JedisCluster, so some of your enhancements are no longer valid in current."
Which ones? If I look in BasicCommands I don't see any of the methods I have changed brpop, blpop, zscan, hscan, sscan and scan.

@roirex Oh, sorry. scan is in MultiKeyCommands.
Btw, in https://github.com/xetorthio/jedis/pull/687 I removed non-target multi-keys (actually no keys) commands, so my changeset and your PR will be conflicted.
We're discussing about handling non-target commands, and I think we should remove these.
Please refer https://github.com/xetorthio/jedis/issues/764


WildFly Runtime ->no war package content be deployed if deploy to root

Plugin name and version
Maven Plugin for Azure Web Apps: 1.4.2-SNAPSHOT

Plugin configuration in your pom.xml
Take V1 as example:
...
<build>
    <finalName>webapp0</finalName>
    <plugins>
         <plugin>
            <groupId>com.microsoft.azure</groupId>
            <artifactId>azure-webapp-maven-plugin</artifactId>
            <version>1.4.2-SNAPSHOT</version>
            <configuration>
               <!-- Web App information -->
               <resourceGroup>warwebapp1</resourceGroup>
               <appName>warwebapp1</appName>
               <region>westeurope</region>
               <pricingTier>S1</pricingTier>

               <!-- Runtime Stack specified by Docker container image -->
               <containerSettings>
                  <imageName>shrishrirang/wildfly:latest</imageName>
               </containerSettings>
               <deploymentType>war</deploymentType>

            </configuration>
         </plugin>
    </plugins>
  </build>
...

Expected behavior
The war package content be deployed
Actual behavior
After deployment, no war package content be deployed to root, the root url always show as below:

Steps to reproduce the problem

Prepare a webapp maven project with neweast maven plugin version
Set the pom file as above
Run "mvn clean package"
Run "mvn azure-webapp:deploy"
Access the web site

I have do more investigation. I verified the issue #1, yesterday V1 can stable repro, but very strange it cannot be reproduced today. After I updating the deployment config of V2 pom file, now V2 also works fine.
So the issue not repro now, closed this issue.


Search for 'Bot' in Azure Portal should put Azure Bot in first (vs 3rd) place

When searching for 'Bot', the Azure Web App bot comes first in the list- this one is incompatible with Composer and should be replaced by Azure Bot -> Azure Bot should be in first place.
(I know this should be in the Azure ADO but github tends to get more traction & response).

Hi Marieke.  I agree with the idea here, but as you say above, this is not the right place for this issue, especially as the service folks are not very active in GitHub. Please instead start a thread with Andrea and I and we can take it from there.

I started a thread @mareekuh


ValueError: heights cannot be None.

Hello again,
I am facing a new error with simple character calculation which did not occur before I updated Momepy through pip to fix the tessellation-based block issue:
What am I doing wrong this time? I never wrote 'heighs' with an S but it pops up that way
Thank you

buildings['sdbAre']` = mm.Area(buildings).series
buildings['sdbVol'] = mm.Volume(buildings, 'height', 'sdbAre').series
buildings['sdbPer'] = mm.Perimeter(buildings).series
buildings['sdbCoA'] = mm.CourtyardArea(buildings, 'sdbAre').series

buildings['ssbFoF'] = mm.FormFactor(buildings, 'sdbVol', 'sdbAre').series
buildings['ssbVFR'] = mm.VolumeFacadeRatio(buildings, 'height', 'sdbVol', 'sdbPer').series
buildings['ssbCCo'] = mm.CircularCompactness(buildings, 'sdbAre').series
buildings['ssbCor'] = mm.Corners(buildings, verbose=False).series
buildings['ssbSqu'] = mm.Squareness(buildings, verbose=False).series
buildings['ssbERI'] = mm.EquivalentRectangularIndex(buildings, 'sdbAre', 'sdbPer').series
buildings['ssbElo'] = mm.Elongation(buildings).series

---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
Input In [4], in <cell line: 6>()
      3 buildings['sdbPer'] = mm.Perimeter(buildings).series
      4 buildings['sdbCoA'] = mm.CourtyardArea(buildings, 'sdbAre').series
----> 6 buildings['ssbFoF'] = mm.FormFactor(buildings, 'sdbVol', 'sdbAre').series
      7 buildings['ssbVFR'] = mm.VolumeFacadeRatio(buildings, 'height', 'sdbVol', 'sdbPer').series
      8 buildings['ssbCCo'] = mm.CircularCompactness(buildings, 'sdbAre').series

File ~\miniconda3\lib\site-packages\momepy\shape.py:105, in FormFactor.__init__(self, gdf, volumes, areas, heights)
    103 def __init__(self, gdf, volumes, areas=None, heights=None):
    104     if heights is None:
--> 105         raise ValueError("`heights` cannot be None.")
    106         # TODO: this shouldn't be needed but it would be a breaking change now.
    107         # remove during the functional refactor
    108     self.gdf = gdf

ValueError: `heights` cannot be None.

Just do
buildings['ssbFoF'] = mm.FormFactor(buildings, 'sdbVol', 'sdbAre', heights='height').series

That should temporarily fix it. I have a To-do task in the code here to clean it up. It was caused by https://github.com/pysal/momepy/pull/330 that is a bit messed up now.


ad param to setTargetingForAst()

Issue:
Currently when someone calls pbjs.setTargetingForAst(), it automatically pulls all the adUnits.  You cannot specifically ask to set the targeting for certain adUnits, like we can for the pbjs.setTargetingForGPTAsync(). We need to add the ability to choose specific adUnits to the setTargetingForAst() call.
Solution Added:
Allow user to pass an array of adUnitCodes to the setTargetingForAst() function so that it only provides the targeting data for those listed adUnits.
Maintain support that calling setTargetingForAst() without any values pulls the targeting data for all adUnits.

@jeanstemp - I think the wording here is a little awkward... can you smith it a bit?


Abilty for record strings as Plain text.

I have old and new versions of snmprec:
Old version record string values as plain text.
snmprec --agent-udpv4-endpoint=x.x.x.x --start-oid=<IP_ADDRESS>.2.1 --stop-oid=<IP_ADDRESS>.2.1.1 --output-file=aix.snmprec
old (0.2.4):
<IP_ADDRESS>.<IP_ADDRESS>.0|4|AIX su0506 3 5 00C6E81B4C00
<IP_ADDRESS>.<IP_ADDRESS>.0|6|<IP_ADDRESS>.4.1.8<IP_ADDRESS>
<IP_ADDRESS>.<IP_ADDRESS>.0|67|1399875231
<EMAIL_ADDRESS><IP_ADDRESS>.<IP_ADDRESS>.0|4|su0506
<IP_ADDRESS>.<IP_ADDRESS>.0|4|CDC Brno

new (0.3.1):
<IP_ADDRESS>.<IP_ADDRESS>.0|4x|414958207375303530362033203520303043364538314234433030
<IP_ADDRESS>.<IP_ADDRESS>.0|6|<IP_ADDRESS>.4.1.8<IP_ADDRESS>
<IP_ADDRESS>.<IP_ADDRESS>.0|67|1399644038
<IP_ADDRESS>.<IP_ADDRESS>.0|4x|706f73746d6173746572407277652d73657276696365732e637a
<IP_ADDRESS>.<IP_ADDRESS>.0|4|su0506
<IP_ADDRESS>.<IP_ADDRESS>.0|4x|4344432042726e6f

For devel purposes I prefer to use Plain strings (4) instead hex (4x).
Please add ability (command line argument) for force decode hex strings to plain in snmprec command.

Just a quick note that I'm working on the feature you've proposed. The idea is to escape non-printables while leaving ASCII as-is.

Nice, will wait this.
Thanks!

@landy2005 SFR ?

@0x003e what?

It's me to blame. Sorry, I started working on the feature discussed here, but got distracted and have not finished it yet.
But I promise to get it done. ;-)

@landy2005 You are welcome to test this implementation. Let me know if it is LGTM so I could merge & release.

Seems as fine for datafile.py conversion.
But for snmprec.py I think should used this logic:
STRING store as 4 or 4e (if escape chars exist)
HEX-STRING always store as 4x format.
What I mean.. currently datafile.py --escaped-strings convert all hex strings into escaped (also if this oid really hex string).. such entries less readable as escaped than as hex :)
diff example for conversion
< <IP_ADDRESS>.4.1.26<IP_ADDRESS>.2.0|4e|\x07\xe1\x0b\x11\x0f\x06\x05\x00+\x01\x00
---
> <IP_ADDRESS>.4.1.26<IP_ADDRESS>.2.0|4x|07e10b110f0605002b0100

< <IP_ADDRESS>.4.1.26<IP_ADDRESS>.1.1.0|4e|\nK\x01\x05
---
> <IP_ADDRESS>.4.1.26<IP_ADDRESS>.1.1.0|4x|0a4b0105

I am not sure I understand your point. How do you define HEX-STRING? Mind you, escapes only happen for non-printables.
Here are the cases we presently deal with:

fully printable ascii always remains as such

string with a non-printable char(s):

default mode: fully hexified
escaped mode:  non-printables are hex-escape, printable remain as-is

WDIT?

yah, forget it, I was wrong.
But my "idea" if 90-100% of string is non-printable (as in my diff example) - use 4x..

Merged. Thank you!


Fix WebPage.assertIsNotOpen(Openable, Object...)

WebPage.assertIsNotOpen is not working, it asserts that a page is open not the other way around

Thanks! I'll release it ASAP with the new selenium version out there.


Do not track paper trail model versions when creating resources

Do we really need to track changes when we create resources? I think we should skip the costs to track changes and only do this on update / destroy. https://github.com/airblade/paper_trail/tree/v3.0.9#choosing-lifecycle-events-to-monitor
See subject.rb and the create action in new relic.

keeping this open, can speed up create end points for a few resources.

closing as we don't use paper trail versioning anymore.


Sads offline deployment files

Tested locally for some reason I needed to configure Node Port locally, need to confirm by testing with stage.
Site should be accessible via "sads-offline/", we have kept the "sads/" as is.
What has been done is copy the sads and content into sads-offline directory and reconfigured the naming. Included sads-offline in the ingress-policy and ingress files along with configuring the argocd directory with the sads-offline directory and content.

@RyanKelvinFord you're about to cross the finishing line with your arms raised in triumph :-)
the only thing left to do before merging is to update the k8s image w/ the latest image @souayb released.
@souayb can you confirm this is the image we should use:

ghcr.io/souayb/sads_offline:v0.1.2

I think we are good to go now.


Potential Security Issue w/ changing IPs

Hi,
I've been logged into the Loopring.io wallet on my brave browser, through the brave browser's native wallet.  I left myself logged in for more than a day, and I wasn't notified that I'd been logged out.  However, for this test, I moved locations and connected to a different network.  Then I made an attempt to cancel my order.  It said that I successfully cancelled my order.
Then I tried to place an order, as the cancel button still remained even though the popup had said that it had successfully cancelled the order.  It said it could not cancel the order, which is fine, except that the order was still showing on the website.
I reloaded the page, and was asked to log in again.  I logged in, on this new IP, and the order had indeed cancelled.
I think this means that even though I'd not been online (my laptop was suspended) for more than a day, and I changed locations, I was still able to execute a cancel order instead of having been logged out after some kind of auto time-out function, or IP change.  It could be a security issue, but at the very least, I think that there should be some time-out function for your logins, if possible, especially if the IP has changed.
Hope this helps.  Really a smooth experience otherwise!

I'd quote this thread for your proposal. https://security.stackexchange.com/questions/220364/log-user-out-after-change-of-ip-address
With Loopring, there is no backend verification of user credentials; the so call password is used solely on the client-side to derive an EdDSA keypair to signing offchain requests. When you log in, we re-generate the key-pair and compare the public key with the one you put on the Ethereum block through the account registration or password resets. Your private key never leaves the dapp local storage during your active session.
In other words, there is nothing a middle man can do, such as intercepting-then-fake-your requests (remember all requests will have to sign with your client-side EdDSA private key, and our backend use the public-key for verification).

Thank you for the reply.  It's definitely comforting reading about how the pk stays on the local storage.  Appreciate the time behind your response.  I think it could be a good one for an AMA or public forum.

Closed the issue


Internet is expensive!

FYI

Internet Gateway (IGW) allows instances with public IPs to access the internet.
NAT Gateway (NGW) allows instances with no public IPs to access the internet.

Issue
All ECS instances do not have public IPs as they are in awsvpc mode to support service integration with API Gateway.
So we need NAT Gateway (private subnet) with Internet Gateway (public subnet) to connect to external databases.

but

Should we consider using AWS database solution or a container database instead?
Let's monitor the usage for a couple of days before we make any final decision.

50cents per api call HAHAHAHA I think hosting an AWS database will not be cheap either.. Maybe I should have let leyi set up the free tier 😢 Anyways since the services are going to be in ECS, i'm ok with a container database, just a bit more hassle to populate and maintain 2 different environments

I see... Unfortunately, but we need to switch databases. As AWS ElasticCache is likely to be even more expensive, I think the alternative for Redis server will be a container database? Did I understand correctly? I don't mind maintaining 2 database in different environments, as we don't have the choice haha.

Yes, lets do that for redis..

Found the culprit (ECR) and managed to resolve it with VPC Endpoint. Normal traffic to our database shouldn't cost much and fargate tasks now cost more instead, so migrating to a container DB isn't necessary anymore I guess.

Case closed.


Publish newest version

Hi Sebastian,
Thanks for the nice reporter. Is the version 0.4-SNAPSHOT already on maven?  Or is there an alternative way to get this version working in my SBT project?
Thanks for your help.
Cheers,
Felix

Hi Felix,
I am glad you like it.
I will try to release 0.4 this evening🤞. I have already tried to publish 0.2 and 0.3 but encounter some issue during the process.

I have published 0.4 to sonatype. Everything is fine except package is not yet available from maven central. I hope synchronization will occur in a few hours.

@don41382 you can get the reporter 0.4: I have released it on maven central (https://search.maven.org/artifact/io.github.seblm/sbt-json-scalatest-reporter/0.4)

Yes, it's there! Thanks for the super quick response! Appreciate it!


Cancel drag when the the draggable item loses focus

Currently, when dragging using the keyboard, the item remains active even when focusing out of it. It leads to several issues that can't be solved at the userland.
I tried implementing a custom sensor, but the current design doesn't allow for extension (note the ts-ignore):
/**
 * A custom keyboard sensor cancels the drag when moving the focus out of the draggable element.
 */
class CustomKeyboardSensor extends KeyboardSensor {
    private readonly sensorProps: SensorProps<SensorOptions>;

    constructor(props: KeyboardSensorProps) {
        super(props);

        this.sensorProps = props;

        this.handleDragCancel = this.handleDragCancel.bind(this);

        this.attachSensor();
    }

    private attachSensor(): void {
        this.sensorProps.event.target?.addEventListener('blur', this.handleDragCancel);
    }

    private detachSensor(): void {
        this.sensorProps.event.target?.removeEventListener('blur', this.handleDragCancel);
    }

    private handleDragCancel(): void {
        // There's no other way to notify the parent class to clean up the state.
        // @ts-ignore
        this.detach();
        this.detachSensor();
        this.sensorProps.onCancel();
    }
}

Even ignoring the error, other issues arise. For example, using the CustomKeyboardSensor, when pressing enter to finish dragging, DND kit announces the event as a cancel operation. Even worse, after calling the onCancel callback, in response to a click outside, the item steals the focus back, so you need to click twice to move the focus away from the item.

Would love assistance on this as well. If a non keyboard user accidentally gets into a keyboard drag state, the app will feel like it is broken since they cant cancel the drag by clicking elsewhere.
One thought would be to build a combination sensor that taps into both keyboard and click events?

For what it's worth, here's something hacky I did that seems to be working fine and not running into the issues mentioned above. Note also that in my application I am using handleEnd instead of handleCancel.
export class CustomKeyboardSensor extends KeyboardSensor {
    constructor(props: KeyboardSensorProps) {
        super(props);

        const handleEnd = (this as any).handleEnd.bind(this);
        const detach = (this as any).detach.bind(this);

        props.activeNode.activatorNode.current?.addEventListener("blur", handleEnd);

        // hack: override the detach method to also remove the blur event
        (this as any).detach = () => {
            detach();
            props.activeNode.activatorNode.current?.removeEventListener("blur", handleEnd);
        };
    }
}

Just chiming in here. After trying all of these methods and not being completely happy with them, I have come up with react-only, slightly hacky solution that will not break on updates to the keyboard sensor.
The methodology is to store a render key that can be used to force a remount of the sortable container when blur events are captured inside of it. See code below (note I have omitted everything but the code that pertains to this solution).
export default function SortableContainer {

	/**
	 * Initialize render key state. This will be used to force
	 * a remount of the component, clearing its internal state.
	 */
	const [renderKey, setRenderKey] = useState<number>(0);

	/**
	 * Initialize keyboard active state.
	 */
	const [isKeyboardActive, setIsKeyboardActive] = useState<boolean>(false);

	/**
	 * Set keyboard active to true on the sensor's `onActivation` callback.
	 * Bonus: set "Tab" as a drag end (or cancel) trigger.
	 */
	const keyboardSensor = useSensor(KeyboardSensor, {
		// ...
		onActivation: () => setIsKeyboardActive(true),
		keyboardCodes: {
			end: ["Space", "Enter", "Tab"],
		},
	});

	const sensors = useSensors(keyboardSensor);

	/**
	 * Drag ended, set keyboard active to false.
	 */
	const handleDragEnd = useCallback(() => {
		// ...
		setIsKeyboardActive(false);
	}, []);

	/**
	 * Drag cancelled, set keyboard active to false.
	 */
	const handleDragCancel = useCallback(() => {
		// ...
		setIsKeyboardActive(false);
	}, []);

	/**
	 * On blur capture (any blur inside the target element), augment
	 * the render key, which will forces a remount of the container.
	 */
	const handleBlurCapture = useCallback(() => {
		if (isKeyboardActive) {
			// ...
			setRenderKey(key => (key + 1));
		}
	}, [isKeyboardActive]);

	return (
		<div
		{/* ... */}
		key={`SortableContainer-${renderKey}`}
		onBlurCapture={handleBlurCapture}>
			<DndContext
			{/* ... */}
			onDragEnd={handleDragEnd}
			onDragCancel={handleDragCancel}>
				{/* ... */}
			</DndContext>
		</div>
	);
}

See my answer here for how I implemented a pretty solid fix to this, including typescript support.


Links for API broken

On tensorflow website the links for API are broken on this page.

@Arafatk I think that is fixed in 0.8. https://www.tensorflow.org/versions/r0.8/api_docs/cc/index.html

@hunkim  Thanks.


Choice cue and water delivered outside of odor site

I am detecting instances where the choice cue is delivered following a stop OUTSIDE of an odor site.
I am seeing this in the data after I run the analysis (there is the possibility that there is an error on the analysis, but nothing obvious so far and I double-checked). I also got the impression that I saw it happen online, while running the mice.
Generally it happens more frequently at the end of sessions.
This is an example in time

And the same session in space

I have the suspicion that I might be something about the grace distance threshold or something of sorts.
The specific session I am showing here is 754579_20240905T131137

I think the bug here is something else. Are you sure data is correctly aligned? Because the animal did not stop in the first site...

I can see a situation where the animal stops in the inter-site and this can occur, I am actually surprised we did not observe this earlier.

I think I had seen it sporadically before but really rarely and I thought it was something off in my analysis. Now I am seeing it really regularly with this batch.


Address Naming Convention for Entire Project

Is this a bug report or feature request? (choose one): Feature request

Kubernetes Version (output of kubectl version): Any
Helm Client and Tiller Versions (output of helm version): Any
Development or Deployment Environment?: Development
Release Tag or Master:
Expected Behavior: Proper naming convention for entire project
What Actually Happened:
How to Reproduce the Issue (as minimally as possible):
Any Additional Comments:

I can pick this up

@renmak one other thing you could do while performing this sweeping change across all of the charts, is capturing issue #207 as well, but the links are stale. @intlabs can you update the links with what you want @renmak to update (example: intended vs. current).

@v1k0d3n @alanmeadows
Can you guys provide more information on this feature/issue? Need to understand what needs to be done here. thanks

@renmak, this would involve finding a "standard" name to use for common fields/types across all charts. As @v1k0d3n mentioned, #207 captures standardizing the node label names.  There may be other fields/types that multiple charts use that could be standardized as well.

@wilkers-steve Ah i see. K Then let me first start with #207 and will focus on other fields/types later on. Thanks for clarification.

@alanmeadows @intlabs @v1k0d3n
I was reviewing values.yaml of neutron and notice that how we define labels is not consistent with other charts.

Neutron's nested labels
labels:
ovs:
node_selector_key: openvswitch
node_selector_value: enabled
agent:
dhcp:
control_node_selector_key: openstack-control-plane
control_node_selector_value: enabled
...
Other charts
labels:
control_node_selector_key: openstack-control-plane
control_node_selector_value: enabled

Is this something we need to address?

Just to share update. As part of Issue #207 (PR #302) code change, i have updated Nova's values.yaml to align with Neutron. We will create other issues for charts that also needs naming standardization.

Following charts (value.yaml) needs to be updated to align with Nova and Neutron.
A) For these charts, Labels needs to be separated (just like replicas) to achieve parity with Nova & Neutron

Cinder
replicas:
api: 1
volume: 1
scheduler: 1

labels:
node_selector_key: openstack-control-plane
node_selector_value: enabled
Similarly these charts also needs to be updated: Ceph, Glance, Heat

@v1k0d3n @alanmeadows @wilkers-steve
Created a new issue for above charts #326


Installation problem

I have the problem with installation. I follow all steps from readme, but I got this error:
'MobileVLCKit/MobileVLCKit.h' file not found in RCTVLCPlayer.m
I downloaded this MobileVLCKit framework:
MobileVLCKit-3.0-pre-20180822-0635.tar.xz          22-Aug-2018 06:05    269M
Anyone has the same problem?

xuyuanzhou, thank you for the your reply.
I imported MobileVLCKit in vlcKit folder, and my Frameworks folder looks like this.

Thank you xuyuanzhou,
your answer helps me., that was my problem.


google_mobile_ads 5.2.0 not compatible with cocoa pod IronSourceAdMobAdapter (= <IP_ADDRESS>)

Plugin Version

plugin version: google_mobile_ads: 5.2.0
platform: iOS
Steps to Reproduce

Run flutter create bug.
Update the files as follows:
flutter dependencies in pubspec.yaml:

google_mobile_ads: ^5.2.0
ironsource_mediation: ^3.0.0

Pod dependencies in ios/Podfile:
pod 'IronSourceSDK','<IP_ADDRESS>'
pod 'IronSourceAdMobAdapter','<IP_ADDRESS>'

within folder ios, run pod update.

Expected results: run without error
Actual results:

Analyzing dependencies
[!] CocoaPods could not find compatible versions for pod "Google-Mobile-Ads-SDK":
  In Podfile:
    IronSourceAdMobAdapter (= <IP_ADDRESS>) was resolved to <IP_ADDRESS>, which depends on
      Google-Mobile-Ads-SDK (= 11.11.0)

    google_mobile_ads (from `.symlinks/plugins/google_mobile_ads/ios`) was resolved to 5.2.0, which depends on
      Google-Mobile-Ads-SDK (~> 11.10.0)

Logs
flutter run --verbose
[        ]
[  +76 ms] Found plugin google_mobile_ads at /Users/lpc49/.pub-cache/hosted/pub.dev/google_mobile_ads-5.2.0/
[  +13 ms] Found plugin ironsource_mediation at /Users/lpc49/.pub-cache/hosted/pub.dev/ironsource_mediation-3.0.0/
[  +87 ms] Found plugin webview_flutter at /Users/lpc49/.pub-cache/hosted/pub.dev/webview_flutter-4.9.0/
[   +2 ms] Found plugin webview_flutter_android at /Users/lpc49/.pub-cache/hosted/pub.dev/webview_flutter_android-3.16.9/
[   +5 ms] Found plugin webview_flutter_wkwebview at /Users/lpc49/.pub-cache/hosted/pub.dev/webview_flutter_wkwebview-3.16.2/
[  +37 ms] executing: which pod
[  +24 ms] executing: pod --version
[+1939 ms] 1.16.2
[   +2 ms] Running pod install...
[+1920 ms] Running pod install... (completed in 1,900ms)
[        ] CocoaPods' output:
           ↳
[        ]       Preparing

               Analyzing dependencies

               Inspecting targets to integrate
                 Using `ARCHS` setting to build architectures of target `Pods-Runner`: (``)

               Fetching external sources
               -> Fetching podspec for `Flutter` from `Flutter`
               -> Fetching podspec for `google_mobile_ads` from `.symlinks/plugins/google_mobile_ads/ios`
               -> Fetching podspec for `ironsource_mediation` from `.symlinks/plugins/ironsource_mediation/ios`
               -> Fetching podspec for `webview_flutter_wkwebview` from `.symlinks/plugins/webview_flutter_wkwebview/darwin`

               Resolving dependencies of `Podfile`
                 CDN: trunk Relative path: CocoaPods-version.yml exists! Returning local because checking is only performed in repo update
                 CDN: trunk Relative path: all_pods_versions_7_7_b.txt exists! Returning local because checking is only performed in repo update
                 CDN: trunk Relative path: Specs/7/7/b/IronSourceSDK/<IP_ADDRESS>/IronSourceSDK.podspec.json exists! Returning local because checking is only performed in repo update
                 CDN: trunk Relative path: all_pods_versions_c_1_5.txt exists! Returning local because checking is only performed in repo update
                 CDN: trunk Relative path: Specs/c/1/5/IronSourceAdMobAdapter/<IP_ADDRESS>/IronSourceAdMobAdapter.podspec.json exists! Returning local because checking is only performed in repo update
                 CDN: trunk Relative path: all_pods_versions_5_9_a.txt exists! Returning local because checking is only performed in repo update
                 CDN: trunk Relative path: Specs/5/9/a/Google-Mobile-Ads-SDK/11.12.0/Google-Mobile-Ads-SDK.podspec.json exists! Returning local because checking is only performed in repo update
                 CDN: trunk Relative path: all_pods_versions_4_2_c.txt exists! Returning local because checking is only performed in repo update
                 CDN: trunk Relative path: Specs/4/2/c/FlutterMacOS/3.16.0/FlutterMacOS.podspec.json exists! Returning local because checking is only performed in repo update
                 CDN: trunk Relative path: Specs/7/7/b/IronSourceSDK/<IP_ADDRESS>/IronSourceSDK.podspec.json exists! Returning local because checking is only performed in repo update
                 CDN: trunk Relative path: Specs/c/1/5/IronSourceAdMobAdapter/<IP_ADDRESS>/IronSourceAdMobAdapter.podspec.json exists! Returning local because checking is only performed in repo update
                 CDN: trunk Relative path: Specs/7/7/b/IronSourceSDK/<IP_ADDRESS>/IronSourceSDK.podspec.json exists! Returning local because checking is only performed in repo update
                 CDN: trunk Relative path: Specs/5/9/a/Google-Mobile-Ads-SDK/11.10.0/Google-Mobile-Ads-SDK.podspec.json exists! Returning local because checking is only performed in repo update
                 CDN: trunk Relative path: all_pods_versions_7_e_f.txt exists! Returning local because checking is only performed in repo update
                 CDN: trunk Relative path: Specs/7/e/f/GoogleUserMessagingPlatform/2.7.0/GoogleUserMessagingPlatform.podspec.json exists! Returning local because checking is only performed in repo update
                 CDN: trunk Relative path: Specs/5/9/a/Google-Mobile-Ads-SDK/11.11.0/Google-Mobile-Ads-SDK.podspec.json exists! Returning local because checking is only performed in repo update
               [!] CocoaPods could not find compatible versions for pod "Google-Mobile-Ads-SDK":
                 In Podfile:
                   IronSourceAdMobAdapter (= <IP_ADDRESS>) was resolved to <IP_ADDRESS>, which depends on
                     Google-Mobile-Ads-SDK (= 11.11.0)

                   google_mobile_ads (from `.symlinks/plugins/google_mobile_ads/ios`) was resolved to 5.2.0, which depends on
                     Google-Mobile-Ads-SDK (~> 11.10.0)

               /Users/lpc49/.rvm/rubies/ruby-3.3.3/lib/ruby/gems/3.3.0/gems/molinillo-0.8.0/lib/molinillo/resolution.rb:317:in `raise_error_unless_state'
               /Users/lpc49/.rvm/rubies/ruby-3.3.3/lib/ruby/gems/3.3.0/gems/molinillo-0.8.0/lib/molinillo/resolution.rb:299:in `block in unwind_for_conflict'
               <internal:kernel>:90:in `tap'
               /Users/lpc49/.rvm/rubies/ruby-3.3.3/lib/ruby/gems/3.3.0/gems/molinillo-0.8.0/lib/molinillo/resolution.rb:297:in `unwind_for_conflict'
               /Users/lpc49/.rvm/rubies/ruby-3.3.3/lib/ruby/gems/3.3.0/gems/molinillo-0.8.0/lib/molinillo/resolution.rb:700:in `attempt_to_filter_existing_spec'
               /Users/lpc49/.rvm/rubies/ruby-3.3.3/lib/ruby/gems/3.3.0/gems/molinillo-0.8.0/lib/molinillo/resolution.rb:672:in `attempt_to_activate'
               /Users/lpc49/.rvm/rubies/ruby-3.3.3/lib/ruby/gems/3.3.0/gems/molinillo-0.8.0/lib/molinillo/resolution.rb:254:in `process_topmost_state'
               /Users/lpc49/.rvm/rubies/ruby-3.3.3/lib/ruby/gems/3.3.0/gems/molinillo-0.8.0/lib/molinillo/resolution.rb:182:in `resolve'
               /Users/lpc49/.rvm/rubies/ruby-3.3.3/lib/ruby/gems/3.3.0/gems/molinillo-0.8.0/lib/molinillo/resolver.rb:43:in `resolve'
               /Users/lpc49/.rvm/rubies/ruby-3.3.3/lib/ruby/gems/3.3.0/gems/cocoapods-1.16.2/lib/cocoapods/resolver.rb:94:in `resolve'
               /Users/lpc49/.rvm/rubies/ruby-3.3.3/lib/ruby/gems/3.3.0/gems/cocoapods-1.16.2/lib/cocoapods/installer/analyzer.rb:1082:in `block in resolve_dependencies'
               /Users/lpc49/.rvm/rubies/ruby-3.3.3/lib/ruby/gems/3.3.0/gems/cocoapods-1.16.2/lib/cocoapods/user_interface.rb:64:in `section'
               /Users/lpc49/.rvm/rubies/ruby-3.3.3/lib/ruby/gems/3.3.0/gems/cocoapods-1.16.2/lib/cocoapods/installer/analyzer.rb:1080:in `resolve_dependencies'
               /Users/lpc49/.rvm/rubies/ruby-3.3.3/lib/ruby/gems/3.3.0/gems/cocoapods-1.16.2/lib/cocoapods/installer/analyzer.rb:125:in `analyze'
               /Users/lpc49/.rvm/rubies/ruby-3.3.3/lib/ruby/gems/3.3.0/gems/cocoapods-1.16.2/lib/cocoapods/installer.rb:422:in `analyze'
               /Users/lpc49/.rvm/rubies/ruby-3.3.3/lib/ruby/gems/3.3.0/gems/cocoapods-1.16.2/lib/cocoapods/installer.rb:244:in `block in resolve_dependencies'
               /Users/lpc49/.rvm/rubies/ruby-3.3.3/lib/ruby/gems/3.3.0/gems/cocoapods-1.16.2/lib/cocoapods/user_interface.rb:64:in `section'
               /Users/lpc49/.rvm/rubies/ruby-3.3.3/lib/ruby/gems/3.3.0/gems/cocoapods-1.16.2/lib/cocoapods/installer.rb:243:in `resolve_dependencies'
               /Users/lpc49/.rvm/rubies/ruby-3.3.3/lib/ruby/gems/3.3.0/gems/cocoapods-1.16.2/lib/cocoapods/installer.rb:162:in `install!'
               /Users/lpc49/.rvm/rubies/ruby-3.3.3/lib/ruby/gems/3.3.0/gems/cocoapods-1.16.2/lib/cocoapods/command/install.rb:52:in `run'
               /Users/lpc49/.rvm/rubies/ruby-3.3.3/lib/ruby/gems/3.3.0/gems/claide-1.1.0/lib/claide/command.rb:334:in `run'
               /Users/lpc49/.rvm/rubies/ruby-3.3.3/lib/ruby/gems/3.3.0/gems/cocoapods-1.16.2/lib/cocoapods/command.rb:52:in `run'
               /Users/lpc49/.rvm/rubies/ruby-3.3.3/lib/ruby/gems/3.3.0/gems/cocoapods-1.16.2/bin/pod:55:in `<top (required)>'
               /Users/lpc49/.rvm/rubies/ruby-3.3.3/bin/pod:25:in `load'
               /Users/lpc49/.rvm/rubies/ruby-3.3.3/bin/pod:25:in `<main>'
               /Users/lpc49/.rvm/gems/ruby-3.3.3/bin/ruby_executable_hooks:22:in `eval'
               /Users/lpc49/.rvm/gems/ruby-3.3.3/bin/ruby_executable_hooks:22:in `<main>'

[   +9 ms] Error: Error running pod install
[   +4 ms] "flutter run" took 24,082ms.

flutter analyze
Analyzing ios...
No issues found! (ran in 0.7s)

flutter doctor -v:
[✓] Flutter (Channel stable, 3.24.5, on macOS 14.7.1 23H222 darwin-x64, locale en-US)
    • Flutter version 3.24.5 on channel stable at /Users/lpc49/development/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision dec2ee5c1f (17 hours ago), 2024-11-13 11:13:06 -0800
    • Engine revision a18df97ca5
    • Dart version 3.5.4
    • DevTools version 2.37.3

[✗] Android toolchain - develop for Android devices
    ✗ Unable to locate Android SDK.
      Install Android Studio from: https://developer.android.com/studio/index.html
      On first launch it will assist you in installing the Android SDK components.
      (or visit https://flutter.dev/to/macos-android-setup for detailed instructions).
      If the Android SDK has been installed to a custom location, please use
      `flutter config --android-sdk` to update to that location.

[✓] Xcode - develop for iOS and macOS (Xcode 15.4)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 15F31d
    • CocoaPods version 1.16.2

[✗] Chrome - develop for the web (Cannot find Chrome executable at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome)
    ! Cannot find Chrome. Try setting CHROME_EXECUTABLE to a Chrome executable.

[!] Android Studio (not installed)
    • Android Studio not found; download from https://developer.android.com/studio/index.html
      (or visit https://flutter.dev/to/macos-android-setup for detailed instructions).

[✓] VS Code (version 1.95.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.100.0

[✓] Connected device (2 available)
    • iPhone (mobile) •XXXXX • ios        • iOS 15.8.3 19H386
    • macOS (desktop)          • macos                                    • darwin-x64 • macOS 14.7.1 23H222 darwin-x64

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 3 categories.

What I tried (did not solve the issue):

flutter clean, flutter pub get, flutter upgrade, delete Pod.lock file, pod deintegrate, pod install --repo-update
explicitly set platform :ios, '13.0' within Podfile
explicitly downgrading IronSourceSDK and IronSourceAdMobAdapter to earlier versions within Podfile

Hi @lpc49, it's possible that not all adapters will be compatible with our release. If you need to update the iOS SDK for your case, you are able to so in the podspec to 11.11.0.

Thank you @malandr2 !
FYI While I wait for the next release as a proper solution, the workaround you suggested in a prior message (updating the version directly in the podspec file) seems to work for me as a temporary solution.
Best
Lucien


SSH-Option "Close All Channels" - Try cooperative close first

The "Close All Channels" option in den SSH menus calls the script:
https://github.com/raspiblitz/raspiblitz/blob/dev/home.admin/BBcloseAllChannels.sh
But it just does a "force close" .. to try/offer a "Cooperative Close" first would be more economic aof course.

@TrezorHannes  Tested the merged PR .. looks like if I choose "Cooperative Close" it will still ask on every channel point if I want to close Unilaterally (forced closed) - see:

So depending on state of channels (active, etc) it might ask for different things.

Oh no, just figured --force has a different purpose in closechannel vs closeallchannels.
I will need to get back to the drawing board. There are two options to consider:
lncli closeallchannels
   --force                  ask for confirmation once before attempting to close existing channels
   -s, --skip_confirmation  Skip the confirmation prompt and close all channels immediately

So force is not even force-closing, it'll just ask for confirmation once, and then closing all: active as coop, inactive as force-close.
skip_confirmation does what it says, no confirmation needed at all and closes all immediately.
I'm pondering whether we should revert the PR, the original script does what it should do, my apologies.
Wdyt?

Yes I reverted back to the old script for now. It was quite some years back since I implemented it and not often testing it, so the details were also not present at my side. This was a good refresher.


feat(cart): add state to each cart item to indicate if it is new, mutating, etc

PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: https://github.com/graycoreio/daffodil/blob/master/CONTRIBUTING.md#commit
[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?
[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

Does this PR introduce a breaking change?
[ ] Yes
[x] No

Other information
If a second DaffCartItemAdd (or DaffCartitemUpdate etc) action is dispatched before the debounce timer is complete, the debounce timer will reset to the DaffCartItemStateDebounceTimer. When the debounce timer does hit zero, all cart item states will be reset to "Default". This is to avoid edge cases and complex logic around updating and adding different items in quick succession. I think if we try to manage individually concurrent cart item request states (instead of grouping all concurrent requests together into a single debounce timer), we'll end up with bugs and much more complex code. The only downside to grouping all the concurrent requests into a single debounce timer is that a cart item state can last longer than 4 seconds, since the debounce timer resets whenever another cart item request is made. I don't think this is a big deal though, since people don't usually edit cart items like mad and I don't think it will make much difference in terms of user experience.

ready for review

You should deprecate the original items selector and facade field.

I deprecated the selector, but the facade field will be used in the future. It just needs to be pointed at the cart item entity selector instead

I deprecated the selector, but the facade field will be used in the future. It just needs to be pointed at the cart item entity selector instead

Sounds good, can you make that change now or add a TODO for it?

I deprecated the selector, but the facade field will be used in the future. It just needs to be pointed at the cart item entity selector instead

Sounds good, can you make that change now or add a TODO for it?

I made a TODO. I want to do it when we make the decision about whether or not the cart.items part of the state will be trimmed out or not.


_feed_dict_fn

Hi,

I suspect there is a error in _feed_dict_fn.
Why don't you save used sample indexes? They could be repeated when you call _feed_dict_fn() again in the same epoch.
sample = random.randint(0, self.X.shape[0] - 1)
inp[i, :] = self.X[sample, :]

It is not an epoch but only one step for one batch.
for step in xrange(steps):
feed_dict = feed_dict_fn()
global_step, loss, _ = sess.run([self.global_step, self.loss, self.trainer], feed_dict=feed_dict)

I think, it must be something like this:
for step in xrange(steps):
for i in xrange(X.shape[0]/batch_size):
feed_dict = feed_dict_fn()
global_step, loss, _ = sess.run([self.global_step, self.loss, self.trainer], feed_dict=feed_dict)
Am I right? Or I have an incorrect guess?

Here are some opinions of mine. For the first question, I think in "sgd" each batch is random sampled so the _ffed_dict_fn() should be repeated called. I agree with you in the second question.

In general, I agree that epochs should be used and non-repeated data, but right now it is indeed just trains specified a number of randomly sampled batches.
If somebody has time to implement a proper sampler for epochs (e.g. generate random indexes to sample into batches and then run over them) - I'll greatly appreciate the help! :)

I will have time to implement it if somebody adds me to contributors :) maybe it'll be a little help with my future migration to Google :))

@makseq Feel free as part of your PR add yourself to CONTRIBUTORS and AUTHORS files. I though personally like this page a lot - https://github.com/google/skflow/graphs/contributors
PS. Let me know if you are interested in referral to G :)

Ok, thank you a lot. I will do it on holidays :)

Solved by @makseq in #b14b86c Thanks!


feat: Add setValue with function setter for useMMKVObject

Actually you are right, we need to use instanceof Function because it might be a non-callable function object as well.


operator hazelcast-platform-operator (5.13.0)

/pipeline restart operator-hosted-pipeline

/pipeline restart operator-release-pipeline


Ignore the Layout export for Head if possible

I love this module, it unlocked my progress, thanks a lot for creating it!
Considering that the Layout Export is now a thing, it took me a long time to figure out why a bunch of my scripts and scroll restoration logic kept ending up in the <head>. Once I got acquainted with the hack I figured out that it was because my Layout contains them, so Head inherits them as well.
The problem with this trap is that it can take a while to figure out that something bad happened at all, so my question is — is there a way to modify the hack to ignore the Layout export just for Head? Ideally I'd like to keep using Layout as if the hack isn't there 🙁

The solution is as simple as modifying Remix context to exclude the Layout export. I'll send a PR.

@silvenon I really appreciate your work on this library and it has saved us. Regarding the Layout Export on the documentation it talks about addressing FUOC by use of the component. Is this library still needed now that this is a feature?


Find a safer safe math

intsafe.h is apparently included in the SDK but is cumbersome and somewhat gross.
For instance, it always returns an HRESULT.
But the bigger problem is that it's neither constexpr nor noexcept which makes an issue when combined with the extended rollout of cppcorechecks through audit mode.
This issue represents switching over to a more modern safe math class.
https://github.com/dcleblanc/SafeInt/blob/master/SafeInt.hpp is the candidate that I found as most likely at this moment.

I'd like to note that a number of the places I've seen "safe math" functions used in the VT code, that's actually not the behavior we need. If something overflows, what you often want is for the result to be clamped rather than having it fail. I've seen the same sort of problems with the safe conversion functions (e.g. UIntToShort), where clamping would be preferable to failure.
So before we start replacing everything with a new library, it may be worth auditing the existing safe math usage to see if that's really the behavior we want.

I'd like to note that a number of the places I've seen "safe math" functions used in the VT code, that's actually not the behavior we need. If something overflows, what you often want is for the result to be clamped rather than having it fail. I've seen the same sort of problems with the safe conversion functions (e.g. UIntToShort), where clamping would be preferable to failure.
So before we start replacing everything with a new library, it may be worth auditing the existing safe math usage to see if that's really the behavior we want.

Good input. I'm trying to discern if that should be a separate effort from this one or all in the same.

@j4james, I think that should be the same effort as this one or that we should add some functions when settling on a safe math library.
I think we could make some templates like the ones in SafeInt.hpp above that are basically like add_clamped that will try to use the add safe math and on failure, just clamp it to the std::numeric_limits().max value. And then walk through the VT adapters and use that instead of the incorrect safemath usages.

For clamped (aka "saturation-") arithmetics not much can be found that's written in C++ and readily available. (…apart from the first result on Google of course - StefanHamminga's library.)
But we probably should actually use saturation arithmetic in more places just like @j4james said.
Arguably the best option I'm personally aware of is Chrome's base/numerics library btw (BSD license).

The Chrome one looks interesting but it would probably take some adaptation to get it into a format we could consume. @DHowett-MSFT, opinion?
I'm still mostly inclined to just use the MSVC-related SafeInt with some til templates to provide clamping.

@miniksa SafeInt truly looks amazing and it’s a good choice regardless. The reason I mentioned the Chromium one is because proper saturation arithmetic is of course just as annoying to implement as e.g. SafeInt itself (since in both cases you need to carefully check for overflows even in case of e.g. 64-Bit multiplications).
I suppose it’s quite likely that we‘ll never hit such corner cases though and the use of "some til templates" (e.g. only supporting <32 Bit Arithmetic) will be enough for a long time to come. 🙂

A couple of points I wanted to make regarding this issue...

I believe everything in the conhost coordinate system uses shorts. And as far as VT inputs go, parameters should never be larger than an unsigned short at most (DEC only supported up to 16384, and both VTE and Xterm clamp their parameters at 65535). Performing safe math on these values should really not require anything more than an intermediate int that clamps down to a short on exit.
I don't know how much we care about performance, but I'd hate for us to double the size of the code, and half the speed, just so we can handle some theoretically pure situation where all the inputs are 64-bit integers.

It's difficult to say how feasible this is without evaluating all the use cases, but it would be really great if this library was largely transparent in terms of usage. The code would be a lot more readable, and easier to review, if we could write something like a = b + c (where one or more of the variables are some safeint/clampedint type), instead of having to do something like int a = 0; AddClamped(b, c, &a).

SafeInt.h above contains both mechanisms of operation. It contains a templated type that can be used to create variables of type SafeInt where a = b + c works and it also contains the other mechanism template for SafeAdd<T, U, V>(a, b, &c).
I would imagine what we would do is create til::ClampInt<T> and/or til::ClampAdd<T, U, V> that uses the SafeInt.h templates to do the underlying math and clamp to std::numeric_limits<T>().max() or min() should it exceed boundary conditions.
Yes, most of the conhost system uses shorts. I did want to expand those to larger values to some degree internally such that we could address a more "limitless" backing buffer size in the future because it's been a big request in the past. But perhaps it's still reasonable to maintain that VT only applies to SHORT limits.
Generally speaking, I'm fine if the VT stuff would use til::ClampInt<SHORT> going forward. Does that sound reasonable, @j4james?

Though, glancing at the saturating math library from @lhecker, maybe I should just run it through our licensing process to see if we could just be approved to use that... that sounds easier.
Then maybe we include both SafeInt.h for regular safe math and  for saturating math.

@miniksa I wrote a saturating integer class a long time ago and extracted parts of the logic into a Gist.
It's pretty minimalistic that way and should cover the 80/20 rule. 😄 You may feel free to copy that shabby code if you ever want to. 🙂
…Although the more I look at the Chromium library the more I'm convinced I might even use it for myself in the future. The only thing that I'd change is that CheckedNumeric doesn't throw but rather abort()s the process.

@miniksa From a cursory look at the SafeInt lib, I don't think using something like ClampInt<short> would be any better than ClampInt<int32_t>, because it would still end up having to clamp after every operation. I was hoping that could be avoided by having the internal representation be of a higher precision than the clamp range.
But I'm probably fixating on performance issues that aren't really a big deal. The most important thing for me is readability, and it sounds like that is not a problem for any of these libs.

@j4james, not having to clamp after every operation but finally clamping on the transition is part of why I was trying to use size_t everywhere. I was reasonably sure that it would be big enough to hold anything and we could just clamp once at the function boundary, if necessary.
I don't think any of these will drastically ruin performance. If it does, we can optimize after we fix the problem at hand.

The problem with size_t is it's unsigned, and you typically need the intermediate value of a calculation to be signed, so it can easily clamp to zero if it goes negative. That means the first thing I tend to do with a size_t is narrow_cast it to an int. That used to be safe when the parameters where short, but that isn't the case anymore.
Anyway, if we can fix all of that just by changing a few variable types to ClampInt, or something along those lines, then I'll be a happy camper.

happy clamper

@lhecker, @j4james, as of right now, I'm liking the "lift the chromium numerics library" option the best because it provides a consistent and unified way of handling all of these math problems.
I'm looking into the best way we can include it into our repository and transition to it. I think it will handle all of our concerns.


adds testing for MarketContractFactoryChainLink

Description
adds testing for MarketContractFactoryChainLink
Checklist

[x] Linter status: 100% pass
[x] Changes don't break existing behavior
[x] Tests coverage hasn't decreased

Affected core subsystem(s)
tests
Refers/Fixes
fixes #132

Pull Request Test Coverage Report for Build 563

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.7%) to 57.427%

Totals

Change from base Build 556:
0.7%

Covered Lines:
375

Relevant Lines:
607

💛  - Coveralls


how add Tailwind

how i can add Tailwind in playground?
the only way I found is to insert this code into the vue component:
const tailwindScript = document.createElement('script')
tailwindScript.setAttribute('src', 'https://cdn.tailwindcss.com')
document.head.appendChild(tailwindScript)

but is there a way to run this code by default before starting the sandbox?

You can pass a prop previewOptions to the Repl component.
<Repl :preview-options="{ headHTML: '<script ... />' }" />


[border-agent] add api to start/stop border agent

are these APIs used for testing only?

are these APIs used for testing only?

No, they will be used to terminate active secure connections when requested by user of the device. See discussion here: https://github.com/openthread/openthread/pull/10672#discussion_r1768950903

are these APIs used for testing only?

No, they will be used to terminate active secure connections when requested by user of the device. See discussion here: #10672 (comment)

Is otBorderAgentClearEphemeralKey() sufficient for terminating the epskc-based session? Perhaps we don't need to add an API with its scope beyond the requirement.

The otBorderAgentClearEphemeralKey() does not terminate an ePSKc-based session, as explained in its API documentation:
/**
 * Cancels the ephemeral key that is in use.
 *
 * Requires `OPENTHREAD_CONFIG_BORDER_AGENT_EPHEMERAL_KEY_ENABLE`.
 *
 * Can be used to cancel a previously set ephemeral key before it times out. If the Border Agent is not running or
 * there is no ephemeral key in use, calling this function has no effect.
 *
 * If a commissioner is connected using the ephemeral key and is currently active, calling this function does not
 * change its state. In this case the `otBorderAgentIsEphemeralKeyActive()` will continue to return `TRUE` until the
 * commissioner disconnects, or the ephemeral key timeout expires.
 *
 * @param[in] aInstance   The OpenThread instance.
 *
 */
void otBorderAgentClearEphemeralKey(otInstance *aInstance);

One argument is to change the behavior of ClearEphemeralKey() and/or add a new parameter to it, but this would create backward compatibility issues. Adding new `otBorderAgentStart()/Stop() APIs avoids backward compatibility concerns.
Furthermore, these new APIs can be helpful in other situations, allowing control over when a device can act as a Border Agent. I was somewhat surprised that these were not already available.

One argument is to change the behavior of ClearEphemeralKey() and/or add a new parameter to it, but this would create backward compatibility issues. Adding new `otBorderAgentStart()/Stop() APIs avoids backward compatibility concerns.

I think changing the behavior of ClearEphemeralKey() without changing the api surface could be fine given the ephemeral key feature is quite new, usage of the apis are most likely still in development phase. Regardless if this is changed, these pair of new apis could still be useful:

Furthermore, these new APIs can be helpful in other situations, allowing control over when a device can act as a Border Agent. I was somewhat surprised that these were not already available.

The apis can be used to control border agent feature when AIL becomes available/unavailable. And in the future if multiple epskc sessions are supported, the new apis can be used to terminate all sessions instead of a single one.

Furthermore, these new APIs can be helpful in other situations, allowing control over when a device can act as a Border Agent. I was somewhat surprised that these were not already available.

@abtink The APIs didn't exist because border agent service is auto managed. It's automatically started and stopped, so I didn't see it necessary to expose APIs for upper layer to control its lifecycle. If we do expose APIs, it may cause unexpected behavior.

I think changing the behavior of ClearEphemeralKey() without changing the api surface could be fine given the ephemeral key feature is quite new, usage of the apis are most likely still in development phase.

I agree with extending the behavior, considering the intention the API was called by the upper layer.

The apis can be used to control border agent feature when AIL becomes available/unavailable. And in the future if multiple epskc sessions are supported, the new apis can be used to terminate all sessions instead of a single one.

If we do want to terminate all sessions, we can add a more specific API like otBorderAgentTerminateAllSessions(). We don't need a start API, right?

I think changing the behavior of ClearEphemeralKey() without changing the API surface could be fine given the ephemeral key feature is quite new, usage of the APIs are most likely still in development phase.

I understand the desire to potentially improve an API, but I strongly advise against such an approach.

These APIs may already be used by other vendors who are also working to integrate the credential-sharing function into their products.
Regardless of how recent an API is, we cannot and should not set a precedent of allowing changes without clear justification and indications. This can lead to hard-to-debug issues and bugs.

The general guidelines are:

Do not change any existing public APIs unless we have a very strong justification.
If we do have a strong justification, we should ensure the change is significant enough (e.g., adding a new argument or even a complete rename) so that any code using the old API format fails at compile time, allowing developers to detect and update their code.

Even with these guidelines in place, there are still risks associated with changing existing APIs.
One example from earlier is https://github.com/openthread/openthread/pull/3199 where otIp6NewMessage() was modified from:
otMessage *otIp6NewMessage(otInstance *aInstance, bool aLinkSecurityEnabled);

to
otMessage *otIp6NewMessage(otInstance *aInstance, const otMessageSettings *aSettings);

This was considered a safe change as the argument type was changed from a bool aLinkSecurityEnabled to a pointer const otMessageSettings *. However, issues arose where the code using otIp6NewMessage(aInstance, FALSE) was treated as otIp6NewMessage(aInstance, 0), and 0 was interpreted as a NULL pointer, as if aSettings was set to NULL. This led to some nasty hard-to-debug issues and bugs.

The APIs didn't exist because border agent service is auto managed. It's automatically started and stopped, so I didn't see it necessary to expose APIs for upper layer to control its lifecycle.

We could have stopped border agent when AIL becomes unavailable and start it when available. When there is no AIL, there is no point leaving the border agent running and keep a port open for connections.

This was considered a safe change as the argument type was changed from a bool aLinkSecurityEnabled to a pointer const otMessageSettings *. However, issues arose where the code using otIp6NewMessage(aInstance, FALSE) was treated as otIp6NewMessage(aInstance, 0), and 0 was interpreted as a NULL pointer, as if aSettings was set to NULL. This led to some nasty hard-to-debug issues and bugs.

Instead of changing the existing API, shall we add a new API otBorderAgentClearEphemeralKeyAndDisconnect()?

Instead of changing the existing API, shall we add a new API otBorderAgentClearEphemeralKeyAndDisconnect()?

I think a new api for disconnecting active secure sessions sounds good, maybe it doesn't have to be specific to clearing ephemeral key, as we may also want to disconnect an active pskc session to allow activating a new ephemeral key.

Closing this PR as it's replaced by https://github.com/openthread/openthread/pull/10754


Fix the hacky_dev_image_build invoke task

What does this PR do?
Fix the hacky_dev_image_build invoke task.
Motivation
Since the merge of the single agent binary PR #19280, this target was broken when used with --process-agent because the invocation of inv process-agent was rebuilding the single agent binary without the proper -DPython3_ROOT_DIR=… and -DPython3_FIND_STRATEGY=LOCATION build parameter that are required to make the agent binary look for the python library at the expected location inside the docker image.
Additional Notes
Supersedes #22672.
Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

Reviewer's Checklist

[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[ ] Adequate QA/testing plan information is provided. Except if the qa/skip-qa label, with required either qa/done or qa/no-code-change labels, are applied.
[ ] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
[ ] If applicable, the config template has been updated.

/merge


fix: Grape Instrumentation handle status code symbol

Context
ever since grape 1.7.0 grape endpoints can return status codes as rack status code symbols,
these symbols are then converted into integers by Grape::Middleware::Error.
In event_handler we make the assumption that exception status would be an integer, which since grape 1.7.0 is incorrect.
Changes:
we are converting symbols to integers using utility function. This function is basically a copy-pasta of Rack::Utils.status_code done so that we don't need to add rack as a dependency.
The only change is if the status_code is not valid the status code is assumed to be 0.

Looks like there are failing tests: https://github.com/open-telemetry/opentelemetry-ruby-contrib/actions/runs/4852574508/jobs/8647749969?pr=448


Improve libsodium dependency

This gem uses rbnacl which is a wrapper around libsodium for doing the crypto stuff. Since this is an external dependency which makes CI tests and installation harder I decided to use the wrapped rbnacl gem alternative rbnacl-libsodium instead of relying on the availability of the library for now.
Since this is a possible attack vector and some might want to use their own libsodiumboth variations should be possible. Default should be own, fallback to wrapped.
Commits:

https://github.com/thorsteneckel/threema/commit/9b521f8ee6ea7a1f1d3198ede1ec95ad8aeaee50
https://github.com/thorsteneckel/threema/commit/ef8b73a1c14aa808320feaf9d5deefe4f9a1401f

I guess this can be closed after #15

Right! Thanks for looking out 👀


MOON-164: Adds tests for new Dropdown and Menu features

JIRA

https://jira.jahia.org/browse/MOON-164
Description

Added react testing library and associated packages
Converts tests in Dropdown and Menu to react testing library and added tests for new features
Added isHtml prop with default value false back into list for Typography to fix DOM errors

We haven't 100% of the component tested. Is it something we want to achieve?
Dropdown features not tested for now:

The size small or medium
The icon
handleOpenMenu
handleSelect
handleCloseMenu
handleKeyPress

We haven't 100% of the component tested. Is it something we want to achieve?
Dropdown features not tested for now:

The size small or medium
The icon
handleOpenMenu
handleSelect
handleCloseMenu
handleKeyPress

As these weren't already tested, I left them out but it could be good to test them in the future. I'll create a Moonstone ticket so that we can remember to do it.


First chapter

It's basic factory for creating chapter pages. For now it creates few buttons, chapter story and draggable images.

I think we are nearly ready to go with this now. It is probably one of the most complex parts of our App. =)


Test cases failing for all PRs

Instructions
Fix broken test cases
Problem
The following 3/4 test cases are always failing: send-transaction.test.ts, send-script.test.ts, deploy-contract.test.ts
Steps to Reproduce
Run test cases

Acceptance Criteria
Ensure that all test cases are running as expected and succeed on the latest stable version of vscode-cadence.
Context
This issue is effecting every PR.

I got all end-to-end tests passing locally. However, for some reason Github action runners are not able to execute the flow-cli in the same docker container.


Transform regex is missing upercase letters

Thanks for your work. We currently are evaluating the usage of keycloakify but see some errors.
Currently the transform of resource paths fails because the regex is only using lowercase letters for the replace matching.
Our tooling outputs something like this Ai=Nt.p+"static/media/start-meeting-ill.... thus the replace only matches t.p+"static leading to a replacement to Nwindow... which will obviously fail.
If you agree that a simple fix would be to add upper case letters, I can probably offer a patch

Hi @valkum,
It should be fixed now.  (v4.8.4)
Thanks for reporting.


Bug fix for EOL separators in ircii on Linux

Per https://tools.ietf.org/html/rfc1459 section 2.3.1 the message separators are ether CR or LF or any combination of them silently ignoring multiples. The fix alters the split regex to account for this (bug found using ircii client on Linux).

:+1:


fix: warn on missing optional peer deps during build

Description

Closes https://github.com/vitejs/vite/issues/15733

I wrote my findings in https://github.com/vitejs/vite/issues/15733#issuecomment-1913868095 and it seems reasonable to treat this case similar to node builtin warning on non-ssr build https://github.com/vitejs/vite/pull/12616
The node builtin warning happens during resolveId hook, but for missing peer dep, I added a warning during load hook since it looks simpler to implement in this way and probably there's no substantial difference for users.
I haven't added a test but verified manually on playground by:
(actually playground build seems to fail currently because of this line. I commented this out before running build command below)
https://github.com/vitejs/vite/blob/c9d03eb8235960082523bb8d670205a3cfffecc2/playground/optimize-deps/vite.config.js#L6-L7
$ pnpm -C playground/optimize-deps build

><EMAIL_ADDRESS>build /home/hiroshi/code/others/vite/playground/optimize-deps
> vite build

...
[plugin:vite:resolve] Could not resolve "foobar/baz" imported by "@vitejs/test-dep-with-optional-peer-dep-submodule". Is it installed?
[plugin:vite:resolve] Could not resolve "foobar" imported by "@vitejs/test-dep-with-optional-peer-dep". Is it installed?
...

What is the purpose of this pull request?

[x] Bug fix
[ ] New Feature
[ ] Documentation update
[ ] Other

Before submitting the PR, please make sure you do the following

[x] Read the Contributing Guidelines, especially the Pull Request Guidelines.
[x] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[ ] Update the corresponding documentation if needed.
[ ] Ideally, include relevant tests that fail without this PR but pass with it.

Hmm, It looks like load-time warning still shows up even if optional dep import is tree-shaken completely. I checked this by commenting out callPeerDep here and there is still a warning Could not resolve "foobar" ...:
https://github.com/vitejs/vite/blob/c9d03eb8235960082523bb8d670205a3cfffecc2/playground/optimize-deps/index.html#L206-L214
This means that the warning will likely to make false-positive, so this approach is probably not good (even though it works somewhat similar to current node builtin warning).
I would love to hear what others think.

This looks like a good addition to me, but yeah the false warnings are not quite ideal. It might be related to https://github.com/vitejs/vite/issues/14145 and https://github.com/vitejs/vite/issues/14102 perhaps.
I'm not sure if it's easy to fix those, but I suppose one other way to fix this is to inject a warning in runtime instead (adjacent to export default {}) and make sure they still get treeshaken still.

Let me close this for now as I haven't looked into this for a while.


[Question] Related Barcode Generator- in Word Layout - RDLC Layout

Hi,
we have found we can encode data to barcode, we have followed below link , But that is not working.
https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-report-add-barcodes
Can you Explain how we can use the barcodes in Saas Environment
Regards,
Srinivas

Can you ask specific questions?

Hi,
i have created Report to show my barcode in report,
report 50100 ItemBarcodeReport
{
UsageCategory = ReportsAndAnalysis;
ApplicationArea = All;
DefaultLayout = RDLC;
Caption = 'Item Barcode';
RDLCLayout = './ItemBarcode.rdl';
dataset
{
    dataitem(Items; Item)
    {
        DataItemTableView = sorting("No.");
        RequestFilterFields = "No.";

        column(No_; "No.")
        {

        }
        column(Description; Description)
        {

        }
        column(Barcode; BarcodeTxt)
        {

        }
        trigger OnAfterGetRecord()
        var
            BarcodeSymbology: Enum "Barcode Symbology";
            BarcodeFontProvider: Interface "Barcode Font Provider";
            BarcodeString: Text;
        begin
            BarcodeFontProvider := Enum::"Barcode Font Provider"::IDAutomation1D;
            BarcodeSymbology := Enum::"Barcode Symbology"::Code39;
            BarcodeString := 'AGGGHB78777HGJKK';
            BarcodeFontProvider.ValidateInput(BarcodeString, BarcodeSymbology);
            BarcodeTxt := BarcodeFontProvider.EncodeFont(BarcodeString, BarcodeSymbology);
        end;

    }
}
var
    BarcodeTxt: Text;

}
we have not done anything in rdlc , as we see the above code will encode string to barcode, But when we see output of the report it's showing string only.
am missing anything here? Please explain.
thanks!
Regards
srinivas

Any Update on this?

@JesperSchulz - can you help?

I'm afraid, GitHub issues aren't the right tool to get answers to general questions. The community doesn't look through issues to answer them, and the development team at Microsoft doesn't have capacity to support the entire community on this platform.
Try posting your question to the following resources instead:
Business Central Community
mibuso forum
Dynamics User Group
Yammer is also a great place to get help of issues of this sort!
This GitHub repository handles issues with extending published apps, and extensibility in general, for the latest release of Business Central.


Oshawa Ont death related incident

Someone has requested help on a data project:
Submission notes
Previous death linked to the same house on Durham 28 Road Oshawa, Ontario.
Location
Oshawa Ont
How to help
Leave a comment if you'd like to help. Do you have ideas, questions, or need any more information to get started?

Our response:
You requested some information from Oshawa—this is in Ontario, Canada, correct? Our database only covers the United States, but it looks like you can request death investigation results from this website: https://www.ontario.ca/page/death-investigations
You can get the forms either:

by contacting your regional office
emailing<EMAIL_ADDRESS>
Hopefully that’s helpful. Good luck in your search!


Support configuring the scroll behavior of CollectionView#reveal()

Feature description
Currently, CollectionView#reveal() will scroll the minimal amount required to make an item visible on Android and the item will be put in the center of the view on iOS. For some UIs, like the fast scroll feature of Android's RecyclerView, one would prefer to put the revealed item on the top of the view:

Image source: https://stackoverflow.com/questions/31261437/how-to-create-material-design-like-custom-scrollbar-with-numbers-and-alphabets-b
Proposed solution
reveal() should provide a parameter to configure whether the revealed item should be shown e.g. on the top, in the center of the view or if the view should scroll the minimal distance required to show the item.

On the Android side the method androidx.recyclerview.widget.LinearLayoutManager#scrollToPositionWithOffset could be used. It is not smooth scrolling but an instance jump. It allows to specify an offset in pixels to the original target position.

Scroll position is configurable on iOS. Currently we use "centered".
Possible values: https://developer.apple.com/documentation/uikit/uicollectionviewscrollposition?language=objc#


Clean up tests for 13.04.00 formal release

All automated tests need to be reviewed in preparation for the formal 13.04.00 release.

I ran all the tests and added issues for outstanding problems.  A small number of tests need additional attention.  I fixed issues with specific tests.  The review turned up issues parsing date/time strings that were due to trying to handle new formats.
I also cleaned up the general file structure for tests. The following folders levels are unneeded and make paths longer to the point of not fitting on DVD backups:

test/regression - just test is sufficient
test/regression/commands/general - just test/commands is sufficient

The new feature to exclude tests suites also allows tagging some tests with @testSuite so that they can be ignored.   This allows automated testing to focus on the features in the general product.  Obsolete tests can be retained for awhile to help with implementing other tests but can be removed in the future.  Consequently, active tests confirm software features and any broken tests are listed in issues and need attention.
Making the above changes will break the examples links in user documentation for all versions of documentation.  However, the tests will be simpler to understand, explain, and maintain.  Most users should be using the "latest" software and documentation, which will be consistent with the upcoming release.
I committed the changes.  Close this issue.


event_count metric missing because adapter creates its own CloudEvents client instead of using Knative's

The adapter constructor receives a CloudEvents client from Knative:
https://github.com/triggermesh/triggermesh/blob/1804c1441d2331349eafa719d6cd7c2790a818df/pkg/flow/adapter/transformation/handler.go#L73
However, this client is discarded and a new one is created:
https://github.com/triggermesh/triggermesh/blob/1804c1441d2331349eafa719d6cd7c2790a818df/pkg/flow/adapter/transformation/handler.go#L126
As a result, the transformation_event_count (dispatched events) metric isn't published via the metrics exporter.

For posterity: it works 🎉