fix: update to latest API's

Major breaking change to the pattern of how pathtracer works so this was updated. To long to detail but most of the handling is now internal to the pathtracer.
Most of THIS API still works but some things moved.
Depreciated using the word renderer as it confuses with the default renderer, instead use pathtracer
Some options removed as now handled by three and DREI
Three updated to 168 R3F to 8.17.8
All other libraries updated to latest
Major version bumped to 1.1.0

Would it be a good idea to work on a v1.0 branch on the main repo?

So the version in the package was 1.0
Or do you mean like a larger more featured release version?

Latest release is 0.1.1
https://github.com/pmndrs/react-three-gpu-pathtracer/blob/3542ddb69c46a80d31f5f92234121a80c5ee294b/package/package.json#L2-L4
If you can update it to use latest three, r3f and pathtracer, as well as clean up any API issues I might have left behind, we can release it as a major.
My initial work was meant to be POC and experimental

This updates everything to @latest as of 9-26-2024 including three, r3f, drei, and three-gpu-pathtracer.
It's very simple and the hook exposes the pathtracer which has the same core functionality.
There are more features like special lights, cameras, and materials supported by three-gpu-pathtracer that could potentially be wrapped as JSX components but honestly they arent needed 99% of the time.
As this wasn't a major library we dont really have to worry about some of the breaking changes that came from upstream like removal of frames, needing to update certain things etc.
As a general starting point though I think this works so if that's ok with you I think we can 1.0 this and all those other bells and whistles we'll add as feature releases.

LMK what you think when you get the chance. I'm using a version of this in a project and will use the official version once updated.
Also, most of the issues are resolved by using the latest apis..

Yeah I’m in favor of merging this and releasing a minor.
I think a full release version of this library should also abstract the  lights and camera that pathtracer gives us.
Give me a bit, I’ll merge pull and make a release. Thank you Dennis!

By the way does this also address some of the open issues?

By the way does this also address some of the open issues?

Most of them.
Most of them are related to batchedGeometries issues which we dont use anymore

Can you please edit the PR disc to include “closes #xxx” so that whatever issues it closes get closed when we merge?


Feature/gpu

added a NoTrigger trigger, which stores all events without applying selection
added a radioactive generator, to simulate radioactive decays in the detector water and / or in the PMT glass
added the possibility to simulate several primary particles in each event (this allows to simulate pile up of independent radioactive decays)
finally, added few scripts in sample-root-scripts/ to produce plots from the output

Thanks for your work, @federiconova! Just a couple of things before I can start to review this. First, I noticed that some old code, like vis.mac, is included here even though it's been removed in the current development branch. Second, we usually try and keep our pull requests to be code that addresses single issues. This helps me/anyone else who is looking over the pull request because it is easier to review and catch any mistakes when the code is all dealing with a single topic. It also helps the other developers and users because they can see the changes go in incrementally and if there is a bug that gets introduced, it's a bit easier to track down.
So, I would suggest the following: check out a clean copy of WCSim (this will also help clean up your commit history) and split this pull request into a few smaller pull requests. I would do three pull requests: one for the addition of a NoTrigger trigger, one for the addition of the radioactive generator, and one for the addition for several primary particles to be simulated in an event. Then, the scripts to analyze the output could either be it's own (fourth) pull request or could be included as a part of one of the above three pull requests if it is specific to one of those issues. Does that make sense?


missing items in tables

see e.g. https://grocerist.github.io/grocerist-app/karyes.html
only three rows are displayed although in baserow we have 22 rows (https://baserow.acdh-dev.oeaw.ac.at/database/275/table/1520/5680)
please check the other map/table views as well

I see all 22 rows (15 on the first page and the rest on the second)

just tried on all browsers and it looks fine, where did you have this issue?

looks like some caching issue on my side; sorry for the hassle


{Resources/resources] Fixed TagCount value property

Related to issue 845
PTAL @amarzavery @vivsriaus @TianoMS
This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[ ] The title of the PR is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[ ] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[ ] If applicable, the PR references the bug/issue that it fixes.
[ ] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[ ] I have read the contribution guidelines.
[ ] My spec meets the review criteria:

[ ] The spec conforms to the Swagger 2.0 specification.
[ ] Validation errors from the Linter extension for VS Code have all been fixed for this spec. (Note: for large, previously checked in specs, there will likely be many errors shown. Please contact our team so we can set a timeframe for fixing these errors if your PR is not going to address them).
[ ] The spec follows the patterns described in the Swagger good patterns document unless the service API makes this impossible.

The change looks good to me.

Agreed, changes look good. Just checking the internal process for merging a change that has a breaking change (since switching a data type of a property is a breaking change for some generated libraries - thus the breaking change label was applied). I believe the different language SDK owners are supposed to give a thumbs up after they have decided if they need to bump versions their libraries.

@johanste Thanks for pointing out. I double checked on it, and it's indeed a breaking change. Today in our SDKs we generate this property as String type. If we change it it's going to be Int type. This would potentially break applications that use our SDKs.
Given that, we'll have to update our api-version if we want to make this change. Suggestion is to postpone this change to our next api-version update. @mcardosos let me know if you have any concern.

Assuming that the resource provider is currently returning a number and not a string, you shouldn't have to update the API version. What may have to be updated, though is the major version of the client management library. Not all breaking changes from the REST API perspective are breaking for generated client libraries. And some changes to the swagger document (even if they are correcting the description of the REST API for a given endpoint) are breaking to the client library. It is complicated :)
On the other hand, if the proposal is to also make a server side change to change the type of the returned data, then, yes, the API version would have to be bumped.

Service is returning a number currently. I think I get your point. We don't need to update API version, but we need to update the major version of client libraries. My question is, we automatically generate some of the client SDKs once this swagger spec is updated, is that a problem?

Thanks for merging :)

 https://github.com/Azure/azure-sdk-for-python/pull/955

No modification for NodeJS

 https://github.com/Azure/azure-sdk-for-ruby/pull/653


Broken Quicksave Icon

Don't know when this happened exactly, but the 3 mixtape.moe links used for the icon save button (the one where you simply hover over a picture and not when you actually click on it) are broken. I believe mixtape.moe had some issues in the past week that were "resolved", but the links are still broken. The picture still saves when you click on it but it stays as a gray square. I was wondering if it would be possible to reupload them to a different site or something. Thanks in advance.

"Fixed" by removing the icon completetly. It was added in pull #2. Too complex to maintain for what it's worth.
Sorry for the slow updates.


Add view for timeline

I'm glad I searched again for timeline plugins, since I really like this way this one works.  Is there any way to add a view for this so the dynamic timeline functionality is available in a view tab instead of a note?  A big reason I would prefer to use a view is to have a dynamic timeline without having dataview javascript enabled.
I assume a map view might be able to use frontmatter fields as start and end dates, type field for the event type (period, point, etc).
It would also be very nice if it had a filter that can follow the active note in a way like interactive map view uses a placeholder variable in the filter (https://github.com/esm7/obsidian-map-view?tab=readme-ov-file#follow-active-note).
This might be a lot more work than I think it is though.

Funnily enough, before release Chronos started out as a new-leaf view as opposed to inline!
It's definitely possible. I will need to think about UX for enabling both options

A big reason I would prefer to use a view is to have a dynamic timeline without having dataview javascript enabled

Would a separate view achieve this?

Is there a reason you're opposed to using data view?

Not data view per se, but having dataviewjs enabled seems like it could be a significant security issue that might be highly targeted since it is likely widespread.  I know any exploit would depend on what I put in the vault (either pasting note content or writing script to download things from the internet), but as I work in security I regularly see that sort of "the user would have to intentionally run something" happen on accident more often than I like.

Gotcha
My next project is to make Chronos an SDK outside of obsidian so timelines are portable anywhere. That would allow devs to implement it wherever wanted

That is great.  Thank you for all the work you put into this!


feat: complete overhaul of web user interface

I apologize for this very large PR. I started fixing a few things and got carried away... The alternative splitting this into dozens of little changes might be easier to review but overall more work. To boost confidence in this PR, I added many new tests and increased coverage to over 90% (see below).
Anyway, here's the new and improved Ux and some screenshots below.
Best to just start Verdaccio and give it a try 😀
User Interface
NEW COMPONENTS

Split Link into two components: Link (MUI) + LinkExternal (href, img)
Add Keywords component used on Home and Version pages
Add Person component used for Author, Maintainers, and Contributors

LOGIN

Perform check of minimum username and password length only when submitting form
Fix cancel button for login popup
Fix login menu overlapping toolbar

HEADER

Adjust header and footer alignment so all content has same left and right margin/padding
Add option to Logo component for showing hover text
Add "logoDark" config option to display alternate logo in dark mode
Fix title background of popups in dark mode
Removed duplicate RegistryInfoDialog component

FOOTER

Add Canadian flag to "Made with Love"
Show Verdaccio version in footer only when hovering over logo (less screen clutter)

SEARCH

Increase width of package description in AutoComplete drop-down
Remove HTML tags and markdown links from package description

PACKAGE LIST

Use Keywords component instead of custom tags
Replace "Published on ..." with "Published ... ago" and datetime shown on hover
Fix color when hovering over package in light mode
Fix size of file size and license icons

README

Changed highlight.js styles to github and github-dark themes which fit better to Verdaccio colors
Fix highlight code in dark mode

VERSIONS

Wrap Versions with Card component to match Readme and Dependencies
Show count of dist tags and versions

UPLINKS

Add "showUplinks" config option to hide Uplinks tab completely (useful if running a purely local registry)
Wrap Uplinks with Card component to match Readme and Dependencies
Add link to www.npmjs.com/package/{name} for npm uplinks.
Note: We could make this a config like and make it available for any uplink server.uplinks:
  npmjs:
    web: https://www.npmjs.com/package/{name}

Show full date of uplink fetch on hover over "x days ago" (same as for versions)

SIDEBAR

Add Keywords section
Add "Latest" option to install popover menu (i.e. no version)
Show "Yarn modern" option in install popover menu only if yarn is included in pkgManager config
Change the install popover menu to be in line with heading and pop to left side
Change "Lastest Distribution" to "Distribution" (since stats are for other versions, too)
Adjust icon alignment: remove margin from Icons, add margin to component usage where necessary
Align version detail and sidebar margins
Refactored CopyToClipboard replacing document.execute('copy') which is deprecated
Fix color when hovering over action buttons

RAWVIEWER

Use theme matching light/dark mode
Enable clipboard
Change title from "View manifest" to "Manifest of {package}"
Allow longer strings before collapsing

Behind the scenes
STORE

Refactor api routes to use enum

UTILS

Consolidated Distribution/utils.ts into utils/utils.ts
Output size in Bytes without decimals and kB, MB, etc with one decimal place (instead of two)
Refactor web routes to use enum

TESTING

Added 60 tests for many components and functions (before 154, now 214 tests)
Increased test coverage from 82.3% to 90%, several components with 100% coverage
Fix console.error, Warning: Each child in a list should have a unique "key" prop.
Fix console.error, MUI: The children component of the Tooltip is not forwarding its props correctly.
Fix console.error, Warning: An update to LoginDialog inside a test was not wrapped in act(...).
Replaced some non-Ascii spaces with regular spaces
Adjust test to reflect keywords being shown in sidebar
Adjust snapshots to new padding/margins
Fixed failures when using async/waitFor and mocking useParams
Fix parameter order calling getGlobalInstall

LINT

Rename react/jsx-sort-default-props (deprecated) to react/sort-default-props.

Screenshots
Light Mode

Dark Mode

@mbtools still working on it

Amazing! I'm happy that you like it and I hope others will do, too.
PS: The project I mentioned is on its way (https://abappm.com/). Still some details to figure out but it's trending towards a go-live😄


Release 2.52.0

:tada: This PR is included in version 2.52.0 :tada:
The release is available on:

GitHub release
v2.52.0

Your semantic-release bot :package::rocket:


How to download the app?

Hello!
I was so excited to find this app! But I can’t seem to open it. Help! I’ve downloaded the zip file on my Apple SE phone, but what do I do next?
Thanks so much,
Hope

Hi Hope,
Unfortunately this is not an iPhone app, so you won’t be able to use it on
your iPhone. It only works on macOS.
Ben
On Sat, 27 Jun 2020 at 10:43, esperanza730<EMAIL_ADDRESS>wrote:

Hello!
I was so excited to find this app! But I can’t seem to open it. Help! I’ve
downloaded the zip file on my Apple SE phone, but what do I do next?
Thanks so much,
Hope
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/benwithjamin/Derailleur/issues/2, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABJ4I6DIQMNFFFOJJLGYOLDRYYVVXANCNFSM4OKEAFUA
.

Got it. Thanks for the quick response! 😊


Modbus RTU communications Using RS-232. No response, CRC exception codes.

ModbusMaster version
2.0.1
Arduino IDE version
1.8.19
Arduino Hardware
Arduino DUE | Processor: AT91SAM3X8E
Platform Details
Windows 10 | Release Version: 21H2

Scenario:
Attempting to communicate with the GS2-11P0 VFD by Automation Direct. Using RTU Modbus with RS-232 on Serial1 port with a MAX3232 RS-232 Transceiver. I am sending stuff, however not getting anything in response from the VFD.
Steps to Reproduce:
I used the "Basic" example code which I adjusted from Serial to Serial1 port, and adjusted the address to 1 to write and read holding registers in the VFD
Expected Result:
I am expecting a response on the Rx line which I am not getting at all.
Actual Result:
Currently getting exception code E0 (when printing 'result' using writeMultipleRegisters(0, 2); function) and E3 (when printing 'result' using the readHoldingRegisters(2, 6); function). However the address on the VFD is configured by the user manually, which I did and it is certainly set to 01. I also configured the baud rate on the VFD as well as parity/stop bit configuration. Will attach some photos from the datasheet and RS-232 Oscilloscope captures of the command I am attempting to do.
I have result printed to the Arduino IDE serial monitor.
#include <ModbusMaster.h>

// instantiate ModbusMaster object
ModbusMaster node;

void setup()
{
  // use Serial (port 1); initialize Modbus communication baud rate
  Serial1.begin(19200);

  // use Serial (port 0); to initialize the serial monitor for  debugging
  Serial.begin(9600);

  // communicate with Modbus slave ID 1 over Serial (port 1)
  node.begin(1, Serial1);
}

void loop()
{
  static uint32_t i;
  uint8_t j, result;
  uint16_t data[6];

  i++;

  // set word 0 of TX buffer to least-significant word of counter (bits 15..0)
  node.setTransmitBuffer(0, lowWord(i));

  // set word 1 of TX buffer to most-significant word of counter (bits 31..16)
  node.setTransmitBuffer(1, highWord(i));

  // slave: write TX buffer to (2) 16-bit registers starting at register 0
  result = node.writeMultipleRegisters(0, 2);
  Serial.println(result);

  // slave: read (6) 16-bit registers starting at register 2 to RX buffer
  result = node.readHoldingRegisters(2, 6);
  Serial.println(result);
  // do something with data if read is successful
  if (result == node.ku8MBSuccess)
  {
    for (j = 0; j < 6; j++)
    {
      data[j] = node.getResponseBuffer(j);
      Serial.println(data[j]);
    }
  }
  delay(5000);
}

Yellow = Tx to the VFD, Blue = Rx from the VFD

From VFD Datasheet - CMD Message for reading Holding Registers in the VFD

The CRC appears to be the issue.

So I did make some progress. I changed the addresses around, removed the write to register part and am now getting something.
Message Sent (Tx)

Response Received (Rx)

This is good that I am at least getting some responses, however I am still getting the E0 exception code, as well as the timeout E2 exception code.
Here is the code that I adjusted the original post code to.
#include <ModbusMaster.h>

// instantiate ModbusMaster object
ModbusMaster node;

void setup()
{
  // use Serial (port 1); initialize Modbus communication baud rate
  Serial1.begin(19200, SERIAL_8O1);

  // use Serial (port 0); to initialize the serial monitor for  debugging
  Serial.begin(9600);

  // communicate with Modbus slave ID 1 over Serial (port 1)
  node.begin(2, Serial1);
}

void loop()
{
  static uint32_t i;
  uint8_t j, result;
  uint16_t data[6];

  i++;

  // set word 0 of TX buffer to least-significant word of counter (bits 15..0)
  node.setTransmitBuffer(0, lowWord(i));

  // set word 1 of TX buffer to most-significant word of counter (bits 31..16)
  node.setTransmitBuffer(1, highWord(i));

  // slave: read (6) 16-bit registers starting at register 2 to RX buffer
  result = node.readHoldingRegisters(4432, 6);
  Serial.println(result);

  // do something with data if read is successful
  if (result == node.ku8MBSuccess)
  {
    for (j = 0; j < 6; j++)
    {
      data[j] = node.getResponseBuffer(j);
      Serial.println(data[j]);
    }
  }
  delay(5000);
}

The exception codes from printing 'Result' change every 5 sec between the E0 and E2 error code with this code. Sometimes doing E2 for 3-6 messages, then a random E0, then back to E2 typically.

Amending last comment - Noticed an error code on the VFD display which said cE02 which was an illegal address code (from GS2-11P0) because I made slight mistake and used octal register address as the value in the code (the 4432 address) which should've been 2330 (decimal for the hex 091A - address I wanted).
Once changed I got a different response that was more extensive, and appears to be more realistic, however I got empty data for the following registers which I thought was odd.
Now getting exception code E3, E2, AND E0. Mostly E3 with sprinkles of E2 and E0 every so often per 5 seconds.
Message

Response

I am now successfully controlling the GS2-11P0 VFD using the code I have below:
//-------------------------------------------------------------------------------------------------------------------------------
//  FILENAME: VFD_Control
//  PURPOSE:  This program was designed specifically for controlling the GS2-11P0 variable frequency drive (VFD) made by Automation Direct.
//
//  HISTORY:
//  Rev.    Date        Author            Comment
//  ------------------------------------------------------------------------------------------------------------------
//  0.1     5/19/2022   Chase Lewis       Initial draft, first test just to get control over the VFD and prove that I can control the frequency as well as
//                                        start/stop function.

#include <ModbusMaster.h>

ModbusMaster node;                          // instantiate ModbusMaster object - renamed as "node"
byte i;

void setup()
{
  Serial1.begin(19200, SERIAL_8O1);         // use Serial (port 1); initialize Modbus communication baud rate
  Serial.begin(19200);                      // use Serial (port 0); initialize the serial monitor for debugging exception codes

  // Modbus assigned to Serial port
  node.begin(1, Serial1);                   // Communicate with Modbus slave ID 1 over Serial (port 1)
  delay(5000);                              // Delay for disconnecting/connecting VFD
  Serial.println("Start");                  // Beginning program loop.
}

void loop()
{
  uint8_t j, result;
  uint16_t data[6];

  // set word 0 of TX buffer to least-significant word of counter (bits 15..0)
  //node.setTransmitBuffer(0, u16ShiftRegister);
  vfdBegin(40);                                           // Start VFD, frequency @ 40 Hz
  Serial.println("40 Hz - 60 Seconds");
  delay(60000);                                           // Wait 60 seconds

  updateFreq(30);                                         // Update VFD frequency, frequency @ 30 Hz
  Serial.println("30 Hz - 60 Seconds");
  delay(60000);                                           // Hold for 60 seconds

  updateFreq(20);                                         // Update VFD frequency, frequency @ 20 Hz - Hold for 100 seconds.
  Serial.println("20 Hz - 60 Seconds");
  delay(60000);                                           // Hold for 60 seconds

  vfdStop();                                              // Stop VFD
  Serial.println("Stop - Wait 100 Seconds");
  delay(120000);                                          // Wait 120 seconds
}

void vfdBegin(uint16_t frequency)
{
  node.writeSingleRegister(2330, (frequency * 10));       // Write to address 2330 (HEX - 091A) - Freq Control | frequency * 10 | 600 = 60.0 Hz
  delay(1000);                                            // Wait 1 second
  node.writeSingleRegister(2331, 1);                      // Write to address 2331 (HEX - 091B) - RUN Command | 1 = RUN, 0 = Stop
}

void updateFreq(uint16_t frequency)
{
  node.writeSingleRegister(2330, (frequency * 10));       // Update address 2330 (HEX - 091A) - Freq Control | frequency(ex. 60) * 10 | 600 = 60.0 Hz
}

void vfdStop()
{
  node.writeSingleRegister(2331, 0);                      // Write to address 2331 (HEX - 091B) - RUN Command | 1 = RUN, 0 = Stop
}

The write single register for my vfdBegin() function should be changed to writeMultipleRegisters... will do that later.
Anyways hopes this helps someone. P.S. Was getting successful oscilliscope messages.


Keep track of rows that were ignored because they hit the max attempt limit

Currently if a row fails to be processed 5 times it will be ignored for all future attempts. Logging in https://github.com/Azure/azure-functions-sql-extension/pull/1103 is being added to tell when this happens, but it would be even better to have some way of knowing exactly what rows were ignored (we can't log that information since it contains customer content).
The lease table contains this information (row keys and attempt count), but currently this is cleared once we update the last sync version in the BuildUpdateTablesPostInvocation method.
This is done so that while that version of the row is ignored forever, we will still try to process further changes in the row (in case whatever issue that caused the original failures was fixed).
But doing this means it's difficult to know what rows cause problems and easily track/reprocess those rows. Keeping a historical record of rows that failed to be processed can be hugely beneficial for auditing purposes - similar to the Dead letter queue that the service bus binding implements.

Branch with work I started to simply not cleanup the leases table, but then found out that we still need to do that or we'll ignore the row forever - even if a new change comes in (which potentially could fix the issue).
https://github.com/Azure/azure-functions-sql-extension/tree/chgagnon/noFailedRowCleanup


Return first available transcript if there is no language match

Return first available transcript if there is no match to the provided language code

Hi @RobinXL!
Thank you for your contribution!
However, I am unfortunately not really in favour of this change as this introduces an undesirable default behaviour. When a user requests a specific language the model should not just return some random other language (and even worse) without the user knowing. For example, if you were to build a english dataset with this module, you wouldn't want any other languages to end up in there.
If you have a use case where you don't care about the language, you can still easily implement your desired behaviour using the list_transcripts API.


Improves error message when super is called outside of constructor

Q
A

Bug fix?
no

Breaking change?
no

New feature?
no

Deprecations?
no

Spec compliancy?
no

Tests added/pass?
yes

License
MIT

This PR improves the error message thrown when super() is used outside of the constructor method.
Many developers coming from Java background use the name of the class itself as the constructor method name. Also sometimes the developers make a typo like constructr or contructor and wonder what is the issue. This message would help them in understanding the issue and fix it faster.
Opened a PR on babel here to make sure that the tests pass there as well when this PR is merged

"and has no typos", doesn't seem necessary to me, I'l merge without that part

What about:

Found super() inside method construtor, it is only valid inside a class constructor.

We moved the previous 7.0 branch to be master now, and master is now 6.x


is there is away to add initial data for the generated form?

Hello, thank you very much for using the plugin, currently it cannot be initialized with any value, but we will take it into account for the new version that will be available from January.


Gaps in Log data accompanied by screen flash - Priority 2

Summary: Identify and fix cause for spontaneous all-off.
Description: Occasionally there is a flash on the arena screen (flash meaning the LEDs turn off for about ~20 ms). The log of this data then shows an accompanying ~20 ms gap in all data, including timestamps. This happens in any context, whether a trial is being run in a particular mode or whether the screens are just running an all-on command. We have been unable to recreate any particular circumstance in which this happens. Running the same code on different days will result in different frequency, but it does inevitably happen on occasion.

Maybe the delay is a short version of the issue #57, although there the "all on" command is delayed by seconds.

Based on the suggestion received via email, the following code was used for testing:
function gapsInLogXLSX(testCase)
    testCase.panelsController.setRootDirectory("C:\matlabroot\G4");
    testCase.panelsController.setControlMode(1);
    rsps = [];
    runTime = [];
    seqTime = [];
    for ii=1:400
        testCase.panelsController.startLog()
        testCase.panelsController.setPatternID(ii);
        testCase.panelsController.setPatternFunctionID(ii);
        testCase.panelsController.setPositionX(ii);
        startTime = tic;
        rsp = testCase.panelsController.startDisplay(23);
        seqComplete = toc(startTime);
        rsps = [rsps; rsp];
        runTime = [runTime; 23];
        seqTime = [seqTime; seqComplete];
        testCase.panelsController.stopLog();
    end
    T = table(rsps, runTime, seqTime);
    writetable(T, "gapsInLog.xlsx", "Sheet", "gaps")
end

With G4 Host version 237 the following metrics were produced:

Threshold
Fails run 1
Fails run 2
Fails run 3

0.02s
1%
1%
1%

0.01s
1.5%
1%
1%

0.008s
2.75%
1.75%
1.25%

0.005s
40.5%
34.75%
26.75%

G4 Host version 239 was suggested as a solution to this issue. Similar metrics for this version looks like this:

Threshold
Fails run 1

0.02s
1%

0.01s
1.5%

0.008s
2%

0.005s
29.5%

After the first iteration of the test the above summary suggests that there are roughly the same amount of issues happening, so version v239 doesn't seem to fix the issue.

Looking into the issue a bit more in depth:
The gapsInLog.xlsx file generated from the script above can be used to identify the trials where the gaps occur. For example, the attached file shows a slowed down response for the 396th trial of around 2,319s (compared to the median of around 2.304).

I then looked into the TDMS-log files of that trial, specifically the *_Frame_Time.tdms. There I calculated the difference between two successive frames and plotted the value. In general, a difference of 2000µs is expected (for 500Hz FPS), but in this specific example the frame takes 18000µs.

In other cases of the same test I have seen gaps as big s 50000µs

...or 42000µs

Since the total number of trials above the threshold hasn't changed between version 237 and 239, the assumption is that v239 doesn't fix the issue.

For the tests before I had used a wrong combination of pattern and arena configuration (4x12 pattern, 3x12 arena).
Configured correctly, the issue seems to become less frequent on my setup. I ran 3 full experiments with v239 and only in one of them I found the error using the same strategy (inside 05-03-2022_15-03-43-46_Frame_Time.tdms and 05-03-2022_15-03-57-29_Frame_Time.tdms of gapsInLog-v239-test9.zip ):
 and

After updating the G4 Host to v240, I ran two tests, both produced the same type of errors.
For gapsInLog-v240-test1 one example for an error is inside 05-12-2022_15-03-31-16_Frame_Time.tdms around the timestamp 200332765.
For gapsInLog-v240-test2 there are 9 errors within 28 frames (timestamp 50192333 to 50270332) in 05-12-2022_17-05-28-35_Frame_Time.tdms.

Response via email:

Looking at the first set of v240 data, it showed an error interval of 108-109 runs again and I also didn't see any dequeue error.  I ran the test 7 times (2800 total scans) on my PC without an issue so this is difficult to debug. I have to come up with some more debug utilities to help me isolate this issue.

Via email:

Can you run this tester for about an hour or so whenever you have some time and take a screenshot of the front panel at the end?

if this happens only 3 times during a 66 hour interval, then we can live with the problem.
If it happens several times during a 20min experiment (as it does for the test scripts), then this would ruin a lot of valuable experiments.
Blank frames (or even delayed frames) are not an option for our experiments, they ruin data as well. For an increasing number of our experiment we are using electrophysiology and rely on continuous delivery of stimuli -- any small deviation from the 2ms frame length might look like a false signal in our measurements. I just wanted to give you this as an explanation why we are so persistent on getting this issue fixed now -- or at least understand why we are seeing them on some of our setups so we can avoid the same problem on others.

To confirm that the error might get fixed with v243, I reran the test with v240 and I was still able to replicate the issue, for example in gapInLogs-v240-test11, 08-01-2022_10-10-56-56_Frame_Time:

After the upgrade to v243 (linked above) I still see a similar error (gapsInLog-v243-test03, 08-01-2022_14-02-12-20_Frame_Time)

even several times within 400 trials (gapsInLog-v243-test03, 08-01-2022_14-02-32-08_Frame_Time)

Can you go into the configuration file and change the  GS16 Buffer Size (Stream) to 20000 and try it again?

I ran it a few times with the increased GS16 Buffer size and did not see the same problem. That's great.
For my understanding: What are the side effects of this change. What exactly are the expected changes in the timing?

So this tells me that host software will occasionally have a blip where it prevents the next frames from being pushed into the buffer in time. This is probably due to windows being a non RT OS. Increasing the buffer size helps mitigate this moments because there are more frames in the buffer giving it enough time to recover.  The issue with increasing the buffer size is higher latency for closed operations because the buffer needs to be emptied out before the new frames reach the arena.  20000 may be on the high end so you may be able to lower that. Each frame is around 2000 elements for GS=16.  I may have to think of an alternative way to do this if the closed loop latency is too long.

Yesterday's measurements were promising, but I ran another test this morning while being at a meeting. I just came back and saw errors in at least 10 of the 400 trials (test gapsInLog-v243-test07).
Its not quantified at this point, but my impression is that the larger buffer also increases the length of the error once it occurs. Would that make sense?
in 08-05-2022_09-09-32-37_Frame_Time:

in 08-05-2022_09-09-45-30_Frame_Time:

in 08-05-2022_09-09-45-43_Frame_Time:

in 08-05-2022_09-09-45-52_Frame_Time:

in 08-05-2022_09-09-46-51_Frame_Time:

in 08-05-2022_09-09-55-18_Frame_Time:

in 08-05-2022_09-09-55-22_Frame_Time:

in 08-05-2022_09-09-55-40_Frame_Time:

in 08-05-2022_09-09-55-45_Frame_Time:

in 08-05-2022_09-09-55-58_Frame_Time:

It is possible and likely that I miss errors in the other trials since I am not actually parsing all the tdms files but instead use an imprecise pre-selection of trials that I actually look at. So this might only be the tip of the iceberg and I might have missed some errors in the previous trials.
Let me know if I should run other tests...

Tried to move frame data to the FPGA for more reliable frame outputs, but insufficient space on FPGA to store all the data. Will try running the software in 64-bit LabVIEW to see if any performance is more reliable.
Do you know if C-state is enabled in your BIOS? When C-state is enabled, it can affect performance of PCIe slots.

Has this been resolved with the latest releases?

@floesche Has this issue been resolved?


Add public initializer of HTTPRequest

It is unable to instantiate the struct from external packages unless the public initializer is explicitly  provided.

Hi @takebayashi . The lack of public initialiser for HTTPRequest is currently deliberate.
The API design is such that a server receives a HTTPRequest and is provided with a HTTPResponseWriter with which to create a response. The client API (when its added) should be the mirror image of that: using a HTTPRequestWriter to create the request and receiving back a formed HTTPResponse.
How are you looking to use HTTPRequest?

@seabaylea
If we try to create a custom implementation of HTTPServing we probably need to initialize HTTPRequest directly.
Isn't it intended HTTPServing to be implemented in custom classes?

@seabaylea - Last question was to you.

@takebayashi No, this is supposed to be a concrete implementation. Not a set of protocols you can plug different backends into (and I suggest to drop remaining protocols, see #85).
However, if you want to do an own custom implementation, you can just create an own API compatible HTTP module. See the Apache one for an example: https://github.com/modswift/http/tree/implementation/mod_swift-0.1.0
P.S. A public initialiser would still be useful I think, but for other reasons (e.g. a basic client implementation which we could easily add to this HTTP module). But that would be a different Issue I think :-)

I'm going to close this as yes, the aim is to move towards a single concrete implementation of the API.

I got it. thank you for answering.


compute closure classes eagerly after resolution

We currently compute closure classes to represent closures lazily. However, as the type inferrer looks at each closure, we end up computing all closure classes anyway. It would be cleaner to have a clear point, e.g. directly after resolution, where these are computed. This would for instance allow the computation of reflectable members to include closure classes directly, rather than adding them later in an ad-hoc fashion.

I believe we've done so since we migrated to the CFE.


Build python with no dependencies

Python builds should have no dependencies on external libraries, the whole thing should be statically linked into a single, self-contained executable.

According to Building Python Statically at python.org, this involves compiling as:
$ ./configure LDFLAGS=”-static” --disable-shared
$ make LDFLAGS=”-static” LINKFORSHARED=” ”

However, I tried those flags and get:
configure: WARNING: you should use --build, --host, --target
configure: WARNING: invalid host type: ./configure
checking build system type... Invalid configuration `./configure': machine `./configure' not recognized
configure: error: /bin/bash ./config.sub ./configure failed

... so something is still missing.
We probably need to add a copy of Setup.local (which is basically empty) and copying this into the repo after checking out the version wanted. This should include the keyword *static* on a line by itself, at the very least.

I've started a branch for this. As of 498593f116988fcdc38cb6548055354420339d0a this is not yet working.
With the Setup.local added and building with the flags indicated above, I get the following error:
checking whether the C compiler works... no
configure: error: in `/root/cpython':
configure: error: C compiler cannot create executables
See `config.log' for more details

The referenced config.log is attached as config.log.txt. Need to analyze.
config.log.txt

D'oh! Looks like I had curly quotes in the build script (copy/paste without checking). It's building now.

As of 53f181958441893958e7e9fa3ce2a9d61ec4238c this now appears to build statically, but it's not yet tested in a stand-alone container.

Fixed with 77b5afa7bed57c0098faa0b1c233f0deb37cd779


#[knuffel(child)] field: Option<T>

Just like #[knuffel(child)] field: bool maps the presence/absence of field to true/false,
I expect #[knuffel(child)] field: Option<T> for T withDecode (without Decode) to map the presence/absence of field { ..t } (field t) to Some(t)/None where t : T.
Currently we get this error in some cases:
error[E0277]: the trait bound std::option::Option<T>: Decode<S> is not satisfied.

field modes of T
Option<T>

all fields are property
DOESN’T WORK

all fields are children
WORKS

#[derive(Debug, knuffel::Decode)]
struct SomeDocument {
    #[knuffel(child)]
    field: Option<Node>,
}

#[derive(Debug, knuffel::Decode)]
struct Node {
}

Works for me, by yielding:
SomeDocument {
    field: None,
}

On an empty document and:
SomeDocument {
    field: Some(
        Node,
    ),
}

On document field.
The core thing here is that we don't implement Decode or Option, I think because of orphan rules (but I'm not sure, long time I didn't try that). But we use syntatic Option<x> in derive to find out this thing. So std::option::Option<T> or something like that doesn't work.
Or do you mean it doesn't work on generics?

Yes, childs can't be scalars without unwrap. If you have any ideas of where add some hint to the doc where it's visible for new users, feel free to post a PR.
I don't think we can improve the the error reporting, though. Because we only know that String is std::str::String on typecheck (after macro expansion). We could add a warning on some of the names that are typically scalars, like String, but warnings only work on nightly Rust. So let's wait until they stabilize.


Misc fixes and a couple tests

This fixes a couple issues I've found on macOS:

Setting and then retrieving a secret didn't work until after a few ms... apparently this was because secrets that are not "saved to lastpass" yet have a date time in the output of lpass ls. I modified the regex to include this.
Even though we were routing errors in the error stream to /dev/null I still would see the text Error: Can't find the account (or something like that). To fix that, I routed all streams to output and handled errors accordingly
$BSTR = [System.Runtime.InteropServices.Marshal]::SecureStringToBSTR($Secret.$k) etc... didn't work on macOS... like it would only return the first character of the secret... very odd... to fix this I use [System.Net.NetworkCredential]::new("", $Secret.NoteType).Password

This also adds a couple tests I stole from Steve's KeyChain vault... some are disabled for now. But we can bring those back in time...
@itfranck interested in reviewing?

@TylerLeonhardt See my comments.
Using redirect stream everywhere also disable the login prompt and empty secret get returned.
I had this issue too while doing the original PR and this is why I ended up adding the redirect stream only for the Show call within Set-Secret.

my tests aren't looking good after that last change:
❯❯❯ ./build.ps1 -Test

Starting discovery in 1 files.
Discovery finished in 16ms.
Error: Could not find specified account(s).
WARNING: Querying the secret tests/8c148c24-711e-4795-abba-902ccd07261a produced an unexpected result of $Null
Error: Could not find specified account(s).
Error: Could not find specified account(s).
WARNING: Querying the secret tests/f52be38a-3917-4429-8840-b3314a6eebec produced an unexpected result of $Null
Error: Could not find specified account(s).
Error: Could not find specified account(s).
WARNING: Querying the secret tests/15798b20-1cfc-4187-a34a-e7abba4a6d85 produced an unexpected result of $Null
Error: Could not find specified account(s).
Error: Could not find specified account(s).
WARNING: Querying the secret tests/692e4c58-d005-4e73-95bb-6c28b584c773 produced an unexpected result of $Null

@TylerLeonhardt I don't have this issue (Windows  / WSL)  but it look clear that the error suppression do not work as expected on your environment (Mac? Linux?)
The error is never redirected 2>&1  and therefore is displayed.
It causes the warning to be displayed since $res is $null instead of containing either the secret name or the redirected error.
I can't reproduce that specific issue on my end though :(
Looks like this is a good starting point : https://github.com/PowerShell/PowerShell/issues/4002
If there's a different way to write the redirect for Mac to make it work, we could then combine that and a OS check and apply the proper redirect.
$IsMacOS
$IsLinux
$IsWindows

If you can find a proper redirect that work for your OS type, then I can test it on Windows end and we can either implement the globally correct redirect (if any) or on a "per OS"  basis.

I'll give it a go on my stream today. https://www.twitch.tv/TylerLeonhardt ~30min from now

@itfranck ok so here's what I changed:

we now always do 2>&1
we throw the wellknown exception (part of SecretManagement contract I guess) called PasswordRequiredException when the user is not logged in
I added a test for that ^

I wish these tests could be in a CI but that requires more tinkering.

I'll commit back to this branch later this evening.
I found 2 issues in Get-ComplexSecret .
I also want to test an edge case regarding NoteType parameter that I might or might not be a problem with the error suppression.

I wish these tests could be in a CI but that requires more tinkering.

Do you know any way to automate the login of the user ?
We'd need to be able to type in automatically the password.

:(

@itfranck if we ignore errors do we want to include them in the output stream or not?

check my last commit, that makes all the Error's go away... however, the test still fails so something broke wrt PSCredentials.

@itfranck if we ignore errors do we want to include them in the output stream or not?

check my last commit, that makes all the Error's go away... however, the test still fails so something broke wrt PSCredentials.
Oh yeah. Oops. That -not was very important 😊

Does that work for you ?
        $secret.Password | ConvertFrom-SecureString -AsPlainText | Should -BeExactly $secretText

I ran the test and had an error too there but switching that line for :
[pscredential]::new('myUser', $secret.Password).GetNetworkCredential().Password

resolved the issue for me.
For me (Using PS 5.1 for module development), your statement gave me the gibberish secure string in plain text but still as a secure string (bunch of 0 and 1)

Looks like the test failure was a fluke. It's working for me now!


Max Profit/Loss values are zeros

What do you want to display for Max profit and Loss?
we have plenty of room to show 9 decimal places
we could use the numeric tooltip

WE can either show up to 9 decimals or do something like this:
Max Profit ................  0.000.. Eth
Max Loss ..................  0.9999 Eth

Lets show upto 8 decimals since we have room. Also with the quantity. I made these changes already because there was scentific notation showing. You can test that tix and see what you think. We can also use the ellipse if we want to go that direction. It would add some complexity because of all the variations we have, like coloring red if max profit is negative.

Just confirming we would only show up to 8 decimal if it was a tiny number with many zeros in the decimal....like 0.00000007
If not we display 4 decimals

True, is that the behavior you are currently seeing on sneakpreview?
I made the changes witht the scenific notation issue.

Yes...currently shows 4 for everything unless its a tiny number with many zeros in front then it shows up to 8......Which is what I want it to do
This looks to be working correctly so I am closing


Pipewire backend: use pipewire thread lock

Fixes #3047.
I haven't encountered any issues since adopting these locks. Calling https://github.com/hrdl-github/Waybar/blob/74773885c6166d190a294ad945b1f1d4d5f007ec/src/util/pipewire/pipewire_backend.cpp#L81 without locking causes the warning described in https://github.com/Alexays/Waybar/issues/3047#issue-2196726500. I am less certain whether the lock in the constructor is required.

Thanks!


Time not set from defaultDate

new SingleDateAndTimePickerDialog.Builder(this)
.bottomSheet()
.curved()
.listener(.....)
.defaultDate(toDate)
.displayDays(false)
.displayHours(true)
.displayMinutes(true)
.display();
picker always start with current time, not from "toDate"

same for me
defaultDate not setting it for picker

The same issue.
When locale in AM/PM format defaultDate works good.
When locale in 24 format it doesn't set defaultDate correctly. For example, it is 13:14 now but it set time to 01:14.


Firefox 113: Animated AVIF

https://bugzilla.mozilla.org/show_bug.cgi?id=1825580#c2

Allow animated AVIF (AVIS) to ride the trains to release

https://hg.mozilla.org/integration/autoland/rev/9c82a5d7a367

milestone	113.0a1

The test is once more tricky because it was @IS_NIGHTLY_BUILD@ before, but hey, it's animated and I managed to catch it:

EDIT:
Ah, WPT also has a test: https://wpt.fyi/results/avif?label=experimental&label=master&aligned=

Thanks!


ethereum.base_types.MAX_VALUE isn't a real constant

The rendered documentation is showing MAX_VALUE, but that constant isn't defined in the source code.

We've migrated off of Sphinx to https://github.com/samwilsn/docc so this isn't an issue any more.


Align format

Move detailed explaination to Purpose column and remove inline code
format to align with other rows

@lightcici : Thanks for your contribution! The author, @gewarren, has been notified to review your proposed change.

@lightcici : Thanks for your contribution! The author, @gewarren, has been notified to review your proposed change.

Microsoft authors of articles need to make updates through the private repository so the updates can be staged and validated by the current validation rules. After you review staging and fix all validation issues, you can add the sign-off comment to let the PR reviewers know the updates are ready to be merged.It's easy to access the private repo version of your articles in GitHub. Just add -pr to the URL, as follows:
Public repo URL: https://github.com/Microsoft/azure-docs/blob/master/articles/azure-portal-overview.md
Private repo URL: https://github.com/Microsoft/azure-docs-pr/blob/master/articles/azure-portal-overview.md
We have closed this pull request. Please resubmit the updates through the private repo. If you need perms to the private repo, see the contributor guide instructions


odd behaviour on port binding

Hello, I noticed an issue after migrating my whole infrastructure to docker 1.7.1 on debian jessie.
It occurs on our physical hosts
root@myhost:myname $ uname -a
Linux myhost.com 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1+deb8u3 (2015-08-04) x86_64 GNU/Linux

root@myhost:myname $ docker version
Client version: 1.7.1
Client API version: 1.19
Go version (client): go1.4.2
Git commit (client): 786b29d
OS/Arch (client): linux/amd64
Server version: 1.7.1
Server API version: 1.19
Go version (server): go1.4.2
Git commit (server): 786b29d
OS/Arch (server): linux/amd64

root@myhost:myname $ docker -D info
Containers: 18
Images: 343
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 1000
 Dirperm1 Supported: true
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 3.16.0-4-amd64
Operating System: Debian GNU/Linux 8 (jessie)
CPUs: 8
Total Memory: 31.39 GiB
Name: myhost.com
ID: 6SWU:2K33:5PRM:SW4R:O6XU:Y3SK:SBQN:O3HY:7W77:HHPR:NZ73:ZYE2
WARNING: No memory limit support
WARNING: No swap limit support

In this issue, it clearly seems that docker doesn't clean some DNAT rules on container stop :
root@myhost:myname $ iptables-save |grep -i 5123
-A DOCKER ! -i docker0 -p tcp -m tcp --dport 5123 -j DNAT --to-destination <IP_ADDRESS>:5000
-A DOCKER ! -i docker0 -p tcp -m tcp --dport 5123 -j DNAT --to-destination <IP_ADDRESS>:5000
root@myhost:myname $ ping <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.
From <IP_ADDRESS> icmp_seq=1 Destination Host Unreachable
From <IP_ADDRESS> icmp_seq=2 Destination Host Unreachable
^C
--- <IP_ADDRESS> ping statistics ---
3 packets transmitted, 0 received, +2 errors, 100% packet loss, time 2000ms

### The container is not running, so it's normal

root@myhost:myname $ iptables-save > temp
root@myhost:myname $ vim temp # Here i remove the first DNAT rule
root@myhost:myname $ iptables-restore <temp
root@myhost:myname $ iptables-save |grep -i 5123
-A DOCKER ! -i docker0 -p tcp -m tcp --dport 5123 -j DNAT --to-destination <IP_ADDRESS>:5000

After this workaround, my container gets the trafic that it should have.

Hi!
Please read this important information about creating issues.
If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
This is an automated, informational response.
Thank you.
For more information about reporting issues, see https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
uname -a:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

Can you try on docker 1.8?
This is probably fixed.

1.8.2 is in pre-production as we speak, I'll update the thread if it fixes the issue

The issue seems to be fixed


RecursionError: maximum recursion depth exceeded

I get a recursion error. See error and json recursion_error.zip

The master branch looks to work already, then I just created the version 2.3.0, can you confirm that's working?

Yes, this is working. Thanks! 👍


CTRL+Scroll UP to first tab will also force screen to zoom in.

Title. Don't scroll zoom the screen when trying to ctrl+scroll at end or first stash.

Duplicate of #146


Allow host to limit read/write of guest

I haven't been accepted into the VS Live Share yet. I was hoping to live stream some content on twitch and would like the audience to be able to browse around about the folder structure and look at files.
But I do not want them changing the files unless I am pairing with that guest.
Does Live Share support a model of read-only and writable sharing with guests?

Hey @paulkling! Good to hear from you!  Out of curiosity is what is described in #55 (Allow hosts to share read-only access to a project) what you are thinking about?  The social coding / twitch scenario is really interesting.  Or were you looking for more granular access (like only certain files/folders are read-only)?

Yes the first comment on #55 I think would be good. I could see granular access but that may get out of control.
One other thing I would be worried about while sharing with twitch is leaking my environment variables. Something that has access codes for Azure, AWS, or something like that. One thing to share with someone you "trust" totally another thing for twitch random person.

Yes, agreed, I could see how that would be a big problem.  Would #52 be what you are thinking there?  Also, out of curiosity, if we simply hid anything in .gitignore from view, would that address the need or do you think you'd need to be able to be able to specify other "globs" as well (say in a vslsconfig.json file)?
If #52 and #55 cover it, I'd like to close this one as a dupe in favor of those. In fact, I'd love it if you'd up vote (thumbs up reaction) #55 and #52 since this helps us prioritize assuming these make sense - comments welcome too.  This is great feedback.
That work?

Perfect


Investigate why deploy WF ran for external contributor

See https://github.com/elan-ev/tobira/pull/229#issuecomment-878533718
I did not expect the deploy WF to run for this PR. After all we have this check:
https://github.com/elan-ev/tobira/blob/35bfb94526773238aa514920ac2923124cead6d7/.github/workflows/deploy.yml#L12-L17
So either the check is buggy or I was the actor. But why? I need to investigate that at some point.

Doesn't data is pulled from the context the workflow is run it?
        github.actor == 'LukasKalbertodt' ||
        github.actor == 'JulianKniephoff' ||
        github.actor == 'lkiesow'

That context should be the default branch of this repository. So, I think, the workflow is only run if one of these is the author of the last commit on the default branch.


whereBetween does not select correct date range

I have records like shown below
  {

  "_id": "562f18d16f6fc97c0b00002a",
"sg_message_id": "sendgrid_internal_message_id",
"email"<EMAIL_ADDRESS>"timestamp":<PHONE_NUMBER>,
"ip": "<IP_ADDRESS>",
"smtp-id"<EMAIL_ADDRESS>"event": "click",
"userToken": "2ddcweb136jaykumarp",
"created_at": "2015-10-20 06:25:21",
"updated_at": "2015-10-20 06:25:21"
  }

When I use whereBetween it does not given correct data
the code is as below:
$input = Request::input();
$startDate = new MongoDate(strtotime($input['startDate']));  // 2015-10-16
$endDate = new MongoDate(strtotime($input['endDate']));  //2015-10-23
EmailEvents::whereBetween('created_at',array($startDate, $endDate))->get();

Actual Result: The data I get is from date 2015-10-16 to less than 2015-10-23 like in above example
Expected result : Data with date 2015-10-16 to  2015-10-23
If the value of created_at field is 2015-10-23  00:00:00 then the result shows that record
but if it is like 2015-10-23 12:00:45 it does not show.
Looking for your positive reply

i same


[FEATURE] Ability to rename files downloaded from input_urls

It would be really nice if we had the ability to rename the downloaded files from input_urls. If two of your input urls are "swagger.json", it will conflicts. It also impact the generated class name.

Hi @frederikstonge , good idea, if you really have such issue - I will add ability to do this.

Well, right now, I just copy/paste the whole swagger.json into a local file with the desired name. If the feature was available, I would use it, but it's not mandatory.

@frederikstonge  you can implement it if you want :D
You need just do the next in generator_options.dart
@JsonKey(defaultValue: [])
  List<String> inputUrls;

replace to
@JsonKey(defaultValue: [])
  List<InputUrlModel> inputUrls;

class InputUrlModel { // should be serializable
String url;
String? fileName; // should be not mandatory
}

Something like this. Then you will be able to set
input_urls:
  url: "url/to/file.json"
  fileName: "file_renamed.json"

Hi @Vovanella95 ,
Just working through adding this feature, just wanted to double check about the g2.dart files, what's the process of re-generating it, or are they renamed to g2 because they are actually manually made/updated (there's a comment at the top saying it's generated).
Cheers.
Boz.


e2e test for multiport services

This is a partial fix for #6020. Now, I have to write an integration test for repacking the endpoint subsets.

Tim's rather busy now. Maybe someone from Warsaw can take it?

Replaced by #8177 (this one was closed by mistake - wasn't merged)

@marekbiskup can you maybe consider #8230 - proposal is to move DNS tests out of this test, which somewhat weakens this test, specifically in multi-port.  I have not processed this PR fully - would be nice if these two PRs together did not reduce coverage (much).  @vishh

LGTM. Just a few nits.

@thockin
Is it enough if I update the multiport service test so that it verifies that it's possible to connect to the service ports?

LGTM. please rebase

e2e tests are green

Thanks for the change.


Made a plugin

Just wanted to add it to the repo. It's an equation grapher, it graphs y=x type equations.

Interesting stuff, thanks!


microfetch: 0.4.1 -> 0.4.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for microfetch is: Microscopic fetch script in Rust, for NixOS systems
meta.homepage for microfetch is: https://github.com/NotAShelf/microfetch
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.4.2 with grep in /nix/store/nnbl812r0gxhp97b4rgi5di3xp5xp0jj-microfetch-0.4.2
found 0.4.2 in filename of file in /nix/store/nnbl812r0gxhp97b4rgi5di3xp5xp0jj-microfetch-0.4.2

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

microfetch

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/nnbl812r0gxhp97b4rgi5di3xp5xp0jj-microfetch-0.4.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A microfetch https://github.com/r-ryantm/nixpkgs/archive/da3fc64e1a2b4291a11905a833740f70214e8c7d.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/da3fc64e1a2b4291a11905a833740f70214e8c7d#microfetch

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/nnbl812r0gxhp97b4rgi5di3xp5xp0jj-microfetch-0.4.2
ls -la /nix/store/nnbl812r0gxhp97b4rgi5di3xp5xp0jj-microfetch-0.4.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review

x86_64-linux

:white_check_mark: 1 package built:

microfetch

Maintainer pings
cc @nydragon @NotAShelf for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

I was waiting for this PR, cheers.

On an unrelated note, @nydragon would you be interested in updating the nixpkgs derivation for microfetch to use mold as we do in the flake package?

On an unrelated note, @nydragon would you be interested in updating the nixpkgs derivation for microfetch to use mold as we do in the flake package?

I feel a little strange about this request: if it is not necessary, we can just stick to what we provide by default. Why should use mold?

It is indeed not necessary, I just wanted to know if they'd be interested. Mold is a neat project :)


Example with addClass, removeClass and toggleClass

Would you be so kind provide some simple examples for saving a class and toggling a class please?
like some basic JQuey functions addClass, removeClass and toggleClass.
Or even better if there is pure JS example for those type of common usage?

What on earth does that have to do with localStorage or sessionStorage? store2 is not for manipulating DOM elements.

its for interfacing with localStorage is it not?
So Im asking if could show an  example on how to use store2 to save in local storage something like a class toggle etc. What am I missing? why such response like you just fell off the couch?  what was so appalling about my question?

localStorage is for saving text, not DOM element states. They are so unrelated that an example won't teach anyone anything relevant to this library. It is not an issue with the store2 library. And i saw you cross-posted on marcuswestin's store library. This sort of thing belongs on stackoverflow, not here.
I can give you an example like where you do something like
store('classFooOnElementBar', true) on some action, then look for that on page load like so $bar.toggleClass('foo', store('classFooOnElementBar')), but i don't use jQuery much lately and i don't see what the point of such a thing is.


Add documentation on data availability

Since the preprint doesn't mention data availability (AFAICT), perhaps you could include something about that in the README?
It would also be really cool if any tabular data could be added directly to the repo to make it possible to directly reproduce the following figures/tables using just the Docker image:

Figure 3b
Figure 6
Supplementary Table 1
Supplementary Table 2
Supplemental Figure 2

In theory, it supposed to be uploaded to our lab website: https://dosenbachlab.wustl.edu/data (probably on Openneuro) but it hasn't yet...
I'll try to talk with someone from my former lab about it when I get the chance.


Non-negative byte following CODE_NEG_INT8 is decoded successfully

There is an inconsistency between OCaml implementation and this one in how negative "one-byte" integers are decoded.
According to the documentation, negative integers >= 0x80 should be encoded as the CODE_NEG_INT8 (0xff) byte followed by lower 8 bits of the integer. That means that in encoded sequence the second byte will always have 7th (most significant) bit set to 1, and therefore sequence like [0xff, x] where x <= 0x7f should never occur. Janestreet's implementation therefore rejects such sequence (e.g. Read_error Neg_int8 <pos>, code reference), while this one just returns non-negative value for such case.
In addition to the janestreet/bin-prot being the reference implementation, decode-encode roundtrip should be self-consistent, and in this case it is not, as encode(decode([0xff, 0x00])) == [0x00].

Thanks @LaurentMazare . BTW, there are some other cases with integer decoding that need to be investigated against OCaml bin_prot. I'm going to do that anyway, so please expect more to come )


Enhancement request: hash as atribute for fetchsvn

Most of fetchers are using hash as possible hash parameter, but fetchsvn is not.

See also the discussion in https://github.com/NixOS/nixpkgs/pull/79987.


Include prompt_id into langchain models

Thank you for including prompt_id in the generate function, which has resolved 50% of my issues!
Can you please also include this in the langchain GenAIModel class?
i.e. instead of
import { GenAIModel } from '@ibm-generative-ai/node-sdk/langchain';

const model = new GenAIModel({
  modelId: 'bigscience/bloom',
  stream: true,
  parameters: {},
  configuration: {
    apiKey: 'pak-.....',
  },
});

so we can use
import { GenAIModel } from '@ibm-generative-ai/node-sdk/langchain';

const model = new GenAIModel({
  prompt_id: 'abc123',
  stream: true,
  configuration: {
    apiKey: 'pak-.....',
  },
});

https://github.com/IBM/ibm-generative-ai-node-sdk/blob/main/src/langchain/llm.ts

Sure, I will personally include it and release it tomorrow.

Released in 1.2.1


Add a test for MACE-MP-0 phonon flow with dispersion=True

Summary of Changes
Closes #1652.
Checklist

[ ] I have read the "Guidelines" section of the contributing guide. Don't lie! 😉
[ ] My PR is on a custom branch and is not named main.
[ ] I have used black, isort, and ruff as described in the style guide.
[ ] I have added relevant, comprehensive unit tests.

Notes

Your PR will likely not be merged without proper and thorough tests.
If you are an external contributor, you will see a comment from @buildbot-princeton. This is solely for the maintainers.
When your code is ready for review, ping one of the active maintainers.

@tomdemeyere: merging this and closing your issue. I decided to do a small workaround since it ultimately made more sense.


update copyright to Sermant Authors

What type of PR is this?
Doc
What this PR does / why we need it?
Update the copyright owner to Sermant Authors. This change better reflects the nature of the project and the efforts of contributors.
Which issue(s) this PR fixes？
Fixes #1495
Does this PR introduce a user-facing change?
No

Checklist

[x] Make sure there is a GitHub_issue related with this PR before you start working on it.
[x] Make sure you have squashed your change to one single commit.
[ ] GitHub Actions works fine in this PR.

no need to change this


HOTFIX: Updates to correct version in lockfile

As the title says: the lockfile version was incorrect. This PR bumps it to 1.4.9

@George-cl let's merge and push to master so that's in sync


Integration with Django ORM

Hi Val Huber, I really like your project but was wondering if in addition to SQLAlchemy DjangoORM could be supported as well. We use Django extensively and having a rule engine would be amazing.

Thanks!
My email is @.*** @.***>, if you’d like to discuss.
Best,
Val

On Jun 5, 2023, at 1:02 PM, Nima Mazloumi @.***> wrote:
Hi Val Huber, I really like your project but was wondering if in addition to SQLAlchemy DjangoORM could be supported as well. We use Django extensively and having a rule engine would be amazing.
—
Reply to this email directly, view it on GitHub https://github.com/valhuber/LogicBank/issues/13, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABKSG35W2C6ROL6LQKFD5CDXJY3NLANCNFSM6AAAAAAY3N4FKI.
You are receiving this because you are subscribed to this thread.

I think my email address was masked - check your linkedIn

On Jun 5, 2023, at 1:02 PM, Nima Mazloumi @.***> wrote:
Hi Val Huber, I really like your project but was wondering if in addition to SQLAlchemy DjangoORM could be supported as well. We use Django extensively and having a rule engine would be amazing.
—
Reply to this email directly, view it on GitHub https://github.com/valhuber/LogicBank/issues/13, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABKSG35W2C6ROL6LQKFD5CDXJY3NLANCNFSM6AAAAAAY3N4FKI.
You are receiving this because you are subscribed to this thread.


A wild defineComponent() Warning appears!

I'm following a video tutorial to get started into Vue.js, and everything was fun and games until a few hours ago, when this warning became appearing all over my files that features a "export default {" entry:
[{
"resource": "/c:/Users/kasin/Documents/Extra/VueJS/hakurei-asobi/src/components/Task.vue",
"owner": "generated_diagnostic_collection_name#0",
"severity": 4,
"message": "Component options are wraped by defineComponent() internally to support intellisense on IDE for backward compatible, but this is an hacking which lead to this component type inconsistent with same script code on .js / .ts. Recommended wrap component options by Vue.extends() or defineComponent(). Or you can configure \"experimentalShamefullySupportOptionsApi\": true / false in \"vueCompilerOptions\" property in tsconfig / jsconfig to disable this warning.",
"source": "volar",
"startLineNumber": 6,
"startColumn": 16,
"endLineNumber": 6,
"endColumn": 16
}]
Here's a screenshot of the VSCode screen:

I don't know whether this is easily reproducible or not, I just created the simplest vue project, without even TypeScript suport in the options (I guess), so if anyone need more info, just let me know to help you help me.

I honestly don't know why would volar add a default option like this. This is instantly confusing, suddenly all the components was showing warnings and it took me a bit until I understood what is the problem. Also the option name is kinda offensive I guess, because why would it be shamefull to support Options API? New vue developers start with Options API, its in all the courses on the internet.

Same issue for me, I installed Vue and this warning appears... Any solutions ? I have pure Vue 2 with vuetify plugin

This is terrible. Volar is the official recommended extension for VS Code + Vue 3. Volar is literally shaming the Options API, which is fully supported syntax. This error should not appear!

You can try to use vetur and turn off volar，and then restart vscode

how can i turn off volar pls

You can try to use vetur and turn off volar，and then restart vscode

Thank u it works !!

It also mitigates the warning by adding the following property in your jsconfig.json:
"vueCompilerOptions": {
"experimentalShamefullySupportOptionsApi": true
}
I don't know why we should get this warning by default, since it seems to be some kind of internal API issue (at least for me), and not something wrong with my code. Was there a change on Vue standards that I don't know of?

Sorry for the misnomer, I just realized that "Shamefully support options API"  is incorrect meaning.
Volar cannot support intellisense for component options without defineComponent() / Vue.extend(), so Volar have to wrapped component options by defineComponent() internally with this option. But of course this is not shameful. I think this case is similar to the trade-off of pnpm hoist packages, so I reference to --shamefully-hoist option of pnpm to named the option.
This option is default enabled with warning in 0.34.12 to backward compatible for projects that migrate from Vetur. I will rollback to default disable and fix option words in next version.

I have this error in a Nuxt2/Vue2 projet.
Also I don't have a jsconfig or tsconfig file, why can't I disable this in the Volar VS Code settings ?

I have this error in a Nuxt2/Vue2 projet.

Any solution por nuxt2/vue2?

@mrleblanc101 Warning has been removed, please update to v0.34.14.


Allow reading expandedText attribute

Just recently found this library, and it does precisely what we need in one of our projects at work. Good stuff!
However, we need to be able to measure the height of the expanded text, so it would be useful to us if the expandedText attribute was open for reading. I've changed the implementation to allow that, and thought this might be useful for someone else 🙂
Any feedback on this is greatly appreciated! Thank you in advance 👍

Thanks for your feedback and your contribution! 👍
It will be in the next version.


version control (git) ignored

.git directory is not considered, and it's not possible to use version control when connected to remote directory

Mounted repository is not recognized.
Git output is:
git rev-parse --show-toplevel fatal: Not a git repository (or any of the parent directories): .git.
Using vscode on windows 10 with git repository on virtualbox ubuntu vm.

I have the same issue.

I don't think it's possible. As I understand things, native git support in VSCode works by issuing commands to a standard git client executable, which has no way of seeing the remote server that RemoteFS is making visible to VSCode via the FileSystemProvider interface.
I did some brief tests using Mountain Duck to make remote files appear to my machine as though they're local. Then both VSCode and git can treat them as local, and things seem to work.

I have the same problem. Is there any chance to do something about it?


Please add a license

Thanks for the wonderful work. Is it possible to add a LICENSE file in the root so I can use it in a commercial product?

This not enough?
https://github.com/Versent/redux-crud/blob/master/package.json#L34
Do you need a LICENSE.md ?

I mean a LICENSE file (without md extension)
I see many open source libraries contain this file.

Done


[Snyk] Upgrade standard-version from 9.1.0 to 9.1.1

Snyk has created this PR to upgrade standard-version from 9.1.0 to 9.1.1.

:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 1 version ahead of your current version.
The recommended version was released 21 days ago, on 2021-02-17.

The recommended version fixes:

Severity
Issue
PriorityScore (*)
Exploit Maturity

Remote Code Execution (RCE) SNYK-JS-HANDLEBARS-1056767
387/1000  Why? Proof of Concept exploit, CVSS 5.6
Proof of Concept

(*) Note that the real score may have changed since the PR was raised.

Release notes

Package name: standard-version

9.1.1 - 2021-02-17Bug Fixes

deps: update dependency conventional-recommended-bump to v6.1.0 (#695) (65dd070)
deps: update dependency yargs to v16 (#660) (f6a7430)

9.1.0 - 2020-12-30Features

support custom updater as object as well as path (#630) (55bbde8)

Bug Fixes

deps: update dependency conventional-changelog to v3.1.24 (#677) (cc45036)
deps: update dependency conventional-changelog-conventionalcommits to v4.5.0 (#678) (6317d36)
deps: update dependency conventional-recommended-bump to v6.0.11 (#679) (360789a)
deps: update dependency find-up to v5 (#651) (df8db83)

    from standard-version GitHub release notes

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Pull Request Test Coverage Report for Build 641567772

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 621414072:
0.0%

Covered Lines:
106

Relevant Lines:
106

💛  - Coveralls


proposal: x/website: add dark (night) theme

Please read https://developer.mozilla.org/en-US/docs/Web/CSS/@media/prefers-color-scheme
I can do it if you approve me.

@andybons

This is a substantial amount of work. In design, implementation, and testing. We would not want to force dark mode users to only see the dark mode version, so we’d want a toggle.
@vitaly-zdanevich when you say you can do it, which parts are you planning to do?

@andybons it looks like not difficult task for me, and I believe that this is important accessibility feature. I hope that I can do all parts of it. So, if you approve it, and you think that we need explicit toggle also - maybe we can start with this toggle design. What is the appropriate position? At the bottom of every page? At the top? In some preferences screen?

In "Material" style, with label Dark theme at the left? Maybe not blue but gray.

Or maybe as a link, where text will be Dark mode off and Dark mode on:

We would not want to force dark mode users to only see the dark mode version, so we’d want a toggle.

If the user doesn't want to see dark mode, then they can change the setting in their user agent or operating system. Adding a toggle on the website seems redundant.

@jayschwa I disagree. It’s not clear what user expectations are across the web with regard to this.

White theme is default on macOS and Firefox - if user manually changed it to dark - maybe he will not like to see that most of websites still white.
Screenshot from Firefox under Ubuntu:

Also Chromium from 73 became dark automatically if user switch dark mode inside operating system.

Dark mode, as a feature on the web, is very new. As I said above, we don’t have a thorough understanding of user expectations yet. I don’t think we can entertain this without a toggle.

Ok, so - I do not know your rules how you make decisions. We need to wait for other members to vote? For me this is not important - with or without toggle, I can implement both variants.

Before deciding about the toggle, should we decide whether we want a dark mode at all?
I've read https://developer.mozilla.org/en-US/docs/Web/CSS/@media/prefers-color-scheme, but nothing there says every website must have a dark mode.

We need dark mode for two reasons:

Because of sensitive eyes phenomena. For many people (including me) it is hurts to stairs at toxic WHITE. Especially at night, low-light conditions.

Save the battery.

Android 10 also have system wide dark theme for the same reasons. I remember that in this year (or in 2018, I do not remember) Google at Android conference said that this is recommended to have optional dark theme for every app.
And with this new prefers-color-scheme - if user agent says that he prefers dark mode - why we should ignore that?

On Android most apps have their own settings like

Dark mode on
Dark mode off
System defaults

Would this be an option for a website as well? So instead of a toggle implementing a spinner?
The default one should then respect the operation defaults (or browser defaults) - not sure about the specification 😅.

What if we just make the web site gray on gray? Then it will work equally well in both modes.

More seriously, it seems like the web as a whole needs to figure out what the expectation is for default-white web sites (which is most of them, right?). In general we have a lot of web design work that goes into the pages, so it's not like we can just make up some hex codes and add a switch. Having two modes doubles the design work and adds complexity.
Let's wait on doing anything on this until more sites have figured out what to do. For example, google.com is still white in dark mode. If that changes, then I'd be more inclined to look into what golang.org should do.

Just going to leave this here:
https://twitter.com/pbakaus/status/1189057074925191168?s=09
Don't be that web site 😉
On Wed, Oct 9, 2019, 7:35 PM Russ Cox<EMAIL_ADDRESS>wrote:

More seriously, it seems like the web as a whole needs to figure out what
the expectation is for default-white web sites (which is most of them,
right?). In general we have a lot of web design work that goes into the
pages, so it's not like we can just make up some hex codes and add a
switch. Having two modes doubles the design work and adds complexity.
Let's wait on doing anything on this until more sites have figured out
what to do. For example, google.com is still white in dark mode. If that
changes, then I'd be more inclined to look into what golang.org should do.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/golang/go/issues/34601?email_source=notifications&email_token=ACOBQ65434LHEQORH4KRURDQNYI7RA5CNFSM4I3USUDKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAYV7PI#issuecomment-540106685,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACOBQ62UMEW4O3U3P2K72O3QNYI7RANCNFSM4I3USUDA
.

My pull request to gobyexample.com with optional dark theme through prefers-color-scheme.

Google testing dark mode

Wow, I got official dark theme for Google!

@vitaly-zdanevich please keep this issue on topic

It's almost 2 1/2 years later, taking off hold for reconsideration.

The web team has looked into this as part of a larger redesign and has the work pending. I don't think this needs further discussion.

Based on the discussion above, this proposal seems like a likely accept.
— rsc for the proposal review group

No change in consensus, so accepted. 🎉
This issue now tracks the work of implementing the proposal.
— rsc for the proposal review group

Try out the dark theme today on go.dev. We'll leave this issue open for minor issues discovered post launch.


feat(cli): Update Kamel bind step index in properties to start at 1 instead of 0

fixes #2586
Motivation
The kamel bind command  uses 0 index start for the definition of step properties :
kamel bind ... --step my-step-1 --step my-step-2 -p step-0.my-key=value1 -p step-1.my-key=value2

Having an index start at 1 is more user friendly :
kamel bind ... --step my-step-1 --step my-step-2 -p step-1.my-key=value1 -p step-2.my-key=value2

Modifications

Modify the transformation from command to spec for steps in biding command code
Add a unit test on step values

Release Note
feat(cli): Update Kamel bind step index in properties to start at 1 instead of 0

Thanks for your contribution!!


Using .withNetwork() and .withNetworkAliases() on the same container leads to two network interfaces

Expected Behaviour
Running the following code should produce only a single interface in the log (ignoring the loopback)
import { Network, GenericContainer } from 'testcontainers'

const network = await new Network().start();
const container = await new GenericContainer("alpine")
  .withNetwork(network)
  .withNetworkAliases('foo')
  .withCommand(['sleep', '10'])
  .start();

const networkIpAddress = container.getIpAddress(network.getName());
console.log((await container.exec(['sh', '-c', 'ip a 2>&1'])).output.trim())
await container.stop()

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet <IP_ADDRESS>/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2766: eth0@if2767: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue state UP
    link/ether 02:42:c0:a8:20:02 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/20 brd <IP_ADDRESS> scope global eth0
       valid_lft forever preferred_lft forever

Actual Behaviour
The code above actually leaves two interfaces
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet <IP_ADDRESS>/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2761: eth1@if2762: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue state UP
    link/ether 02:42:ac:11:00:07 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/16 brd <IP_ADDRESS> scope global eth1
       valid_lft forever preferred_lft forever
2763: eth0@if2764: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue state UP
    link/ether 02:42:ac:1d:00:02 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/16 brd <IP_ADDRESS> scope global eth0
       valid_lft forever preferred_lft forever

Testcontainer Logs
The culprit seems to be this line of code: https://github.com/testcontainers/testcontainers-node/blob/main/packages/testcontainers/src/generic-container/generic-container.ts#L95
This class fixes the issue, but breaks DNS:
class SingleInterface extends GenericContainer {
  startContainer (client) {
    this.hostConfig.NetworkMode = this.networkMode
    return super.startContainer(client)
  }
}

If this is not a bug, what problems am I likely to run into trying to use this class as a workaround?
Steps to Reproduce
Run the aforementioned code
Environment Information

Operating System: Fedora 40
Docker Version: 27.1.1
Node version: v18.20.3
Testcontainers version: 10.11.0

It is worth noting that removing the alias leaves only a single interface

Further investigation into the Docker API and there is a way to supply the aliases at creation time which fixes the DNS issue.
https://docs.docker.com/engine/api/v1.37/#tag/Container/operation/ContainerCreate
class SingleInterface extends GenericContainer {
  startContainer (client) {
    this.hostConfig.NetworkMode = this.networkMode
    this.createOpts.NetworkingConfig = {
      EndpointsConfig: {
        [this.networkMode]: { Aliases: this.networkAliases }
      }
    }
    return super.startContainer(client)
  }
}

Hi @david-mohr, out of curiosity what issue is it causing having 2 network interfaces in the container?

When running concurrent tests that involve clustering, it will sometimes form a cluster across the bridge interface, meaning that we don't get proper test isolation and/or flaky results due to data leaking between tests. Not sure if there is any impact on name resolution.

I have been back through our tests and while unexpected, it is not causing any real issues for us except where we are attempting to manipulate routing or iptables. The class I shared above addresses the issue in those cases.


"extra" data is truncated for medium-sized strings such as a full stack trace

Platform
Flutter Mobile
Obfuscation
Enabled
Debug Info
Enabled
Doctor
unrelated
Version
https://github.com/fzyzcjy/sentry-dart
Steps to Reproduce
Putting medium-sized string in extra field. In my case, it is just a full stack trace (see screenshot below for an example)
I have checked https://github.com/getsentry/sentry-dart/blob/main/dart/lib/src/sentry_options.dart but seems no option.
Expected Result
see it
Actual Result
truncated. For example:

Are you willing to submit a PR?
Yes

@fzyzcjy is this truncated in the UI? If so, this should be moved to https://github.com/getsentry/sentry
You can always open the raw JSON in the sentry UI for copying the whole thing.

No, the raw JSON seems truncated: https://rzzsdxx.sentry.io/api/0/projects/xx/xx/events/xxxxx/json/

can you try setting it to event.contexts instead?

Will it have a larger limit? Indeed, I would appreciate it if I could know where those limits are documented.
Attachments look good, but I hope it can be viewed directly in the webpage, instead of having to download them ;)

@fzyzcjy you can preview some attachment types directly in the UI, just use the right format and extension when creating the attachment, a txt would do.
I am checking internally if we have the char limits documented somewhere.

Thanks!

I am checking internally if we have the char limits documented somewhere.

Looking forward to the reply

Thanks for the info! I have not tried it, but if it is "a even smaller bag size" then I will not bother to try ;)

https://github.com/getsentry/relay/issues/2110 is the issue to document all the fields, as of now, I will close this issue.
And for the original problem, let's keep discussing on https://github.com/getsentry/sentry-dart/issues/1429 since ideally you don't need to attach the stack trace as additional data, and attachments is an alternative if you really want.

Thank you!


Bump ruby to version 2.7.1

Bump ruby version. Resolves issue #1590

Hey @edumoreira1506 this looks great! Would you also mind putting in a PR on the partner application upgrading its version of ruby as well? We like to try and keep them in sync.

Sure @seanmarcia !

Opened @seanmarcia Here


[German translation]: Remove 'Beitragsarten' and fix some minor stuff

[X] Have you followed the contributing guidelines?
[X] Have you explained what your changes do, and why they add value to the Guides?

Please note: we will close your PR without comment if you do not check the boxes above and provide ALL requested information.

This should fix minor typos and some translations as the following:

Rephrase sentence containing "Beitragsarten" (which itself is a 1:1 translation of "types of contributions" - this sounds weird in German)
Use "einen Pull Request" instead of "ein Pull Request" as it seems to be more common
Remove unnecessary dots & commas

Hello, how can you help me? My account is broken

How is you 😘😘😘😘


AH: 503 Server Error...

Hi,
When making calls to AH I now get: 503 Server Error: Service Unavailable for url: https://ms.ah.nl/create-anonymous-member-token?client=appie-anonymous
Do others experience this also?
The server it self is reachable via ping.
Does anyone have a solution for this?
Thanks in advance!

I have the same issue, it's unfortunate. Hopefully, it's temporary..

The same here. Still getting this error.

Hi @sander102907  and @kirikorneev. Albert Heijn has modified the API that is used for authentication.
The new endpoint is: https://api.ah.nl/mobile-auth/v1/auth/token/anonymous
If you can give me some time I will incorporate this into the library to make it available again.

I have just released version 0.7 which fixes the issues you are experiencing. If still issues please let me know. I will also look in implementing the Albert Heijn "bonus" endpoints.

@bartmachielsen
Thanks a lot for fixing this, I really appreciate it since I use it every day!!


[SPARK-46299][DOCS] Make spark.deploy.recovery* docs up-to-date

What changes were proposed in this pull request?
This PR aims to update Spark Standalone cluster recovery configurations.
Why are the changes needed?
We need to document

#44173
#44129
#44113

Does this PR introduce any user-facing change?
No.
How was this patch tested?
Manual review.
Was this patch authored or co-authored using generative AI tooling?
No.

Thank you, @HyukjinKwon !

I verified this manually when I attached the screenshot. Let me merge this~


Integration

@Majd-Atyyat @Abeer-Yahya , please review the pull request and let me know if something went wrong


Dropdown not getting trigged on button click with React/ReactDOM versions 17+

The AddToCalendar component is not opening on button click for React and ReactDOM versions past 17.0.0. The click event is still being registered but the actual dropdown is not being toggled.
Keep in mind, I have also tried to activate the dropdown by holding its "open" configuration via state and manipulating the component's optionsOpen prop to no avail. Mounting separate AddToCalendar components with true/false optionsOpen props based on state has not worked, either.
The most recent React/ReactDOM version to work with this package at this point appears to be 16.14.0.

same here

Refer to #62 for a fix

Refer to #62 for a fix

I don't believe this will be merged soon. There are PRs since 2018 :(
I have already switched to different package because can't wait - for the others you can try
@culturehq/add-to-calendar
https://www.npmjs.com/package/@culturehq/add-to-calendar
Pretty similar and easy to use.

I don't believe this will be merged soon. There are PRs since 2018 :(
I have already switched to different package because can't wait - for the others you can try
@culturehq/add-to-calendar
https://www.npmjs.com/package/@culturehq/add-to-calendar
Pretty similar and easy to use.

I don't believe this will be merged soon. There are PRs since 2018 :(
I have already switched to different package because can't wait - for the others you can try
@culturehq/add-to-calendar
https://www.npmjs.com/package/@culturehq/add-to-calendar
Pretty similar and easy to use.

I don't believe this will be merged soon. There are PRs since 2018 :(
I have already switched to different package because can't wait - for the others you can try
@culturehq/add-to-calendar
https://www.npmjs.com/package/@culturehq/add-to-calendar
Pretty similar and easy to use.

@jasonsalzman i would be willing to maintain this project and get some PRs merged if you'd like help.

@jasonsalzman i would be willing to maintain this project and get some PRs merged if you'd like help.

@jasonsalzman want to use this but seems like you aren't letting people keep it alive? :/

@haveaguess I switched to https://www.npmjs.com/package/@culturehq/add-to-calendar 😞

Thanks, took a look but seems a shame as this has a bunch of unit tests and
props that other project doesn't so would end up having to wait for that to
mature.
There are 1.2k people using this and a bunch of decent PRs waiting for be
merged.
On Tue, Feb 2, 2021 at 3:50 PM Ethan Setnik<EMAIL_ADDRESS>wrote:

@haveaguess https://github.com/haveaguess I switched to
https://www.npmjs.com/package/@culturehq/add-to-calendar 😞
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jasonsalzman/react-add-to-calendar/issues/65#issuecomment-771731934,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAU6PP2LDKZ4FXMKX3RV3DS5ANLTANCNFSM4UNZ3P7A
.

@haveaguess beware of #61. I had to change to @culturehq/add-to-calendar due to this bug.

Oh ok, painful, any PRs waiting for that? Maybe I can just merge them in? 😔

@jasonsalzman help 🙏 otherwise @haveaguess will have many sleepless nights and his boi won't have a dad for few days 😬😬

Oh ok, painful, any PRs waiting for that? Maybe I can just merge them in? 😔

I didn't figure out the issue, but it's working in @culturehq/add-to-calendar so I guess whatever they are doing could be backported to this repo.

Ics file downloaded for me in chrome when clicking Outlook button but
outlook.com has a time format bug that I can see was fixed in
@culturehq/add-to-calendar in 2020
I'm thinking I'll probably fork and take this repo forward, would you be
interested in helping maintain?
On Wed, Feb 3, 2021 at 3:55 PM Ethan Setnik<EMAIL_ADDRESS>wrote:

Oh ok, painful, any PRs waiting for that? Maybe I can just merge them in?
😔
I didn't figure out the issue, but it's working in
@culturehq/add-to-calendar so I guess whatever they are doing could be
backported to this repo.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jasonsalzman/react-add-to-calendar/issues/65#issuecomment-772614385,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAU6PO7MC67BLGHUUPMPSLS5FWYZANCNFSM4UNZ3P7A
.

Ics file downloaded for me in chrome when clicking Outlook button but
outlook.com has a time format bug that I can see was fixed in
@culturehq/add-to-calendar in 2020

@haveaguess ok. It didn't work for me in chrome or safari using this package.

I'm thinking I'll probably fork and take this repo forward, would you be
interested in helping maintain?

Sorry, can't commit to it as we no longer use it.

We ended up moving to
https://www.npmjs.com/package/@culturehq/add-to-calendar
..and forking it to build in multi-line HTML support for descriptions, HTML in ICS, and recipient pre-population for google/outlook :
https://github.com/connect4app/add-to-calendar
It's pretty rough at the moment but we hope to find time to clean it up and PR some changes back in