ConcurrentCompilationError if calls .watch several times

Bug report

What is the current behavior?
it doesnt throw error if I call register watch once
  var webpack = require('webpack');
  var webpackConfig = require('./webpack.config');
  var compiler = webpack(
    {
      target: 'node',
      mode: 'production',

      output: {
        filename: "output.js",
      },

      entry: './entry.js'
    }
  );

  compiler.watch({
    aggregateTimeout: 300,
    poll: undefined
  }, (err, stats) => {
    if (err) return console.error(err)
    if (!stats.hasErrors()) {
      console.log('1')
    } else {
      console.log('2')
    }
  })

# entry.js
console.log('hello from entry.js')

it throws error
 ✘  ~/projects/webpack-hot-middleware/example   ConcurrentCompilationError ●  node server.js
[20:56:23.785] [ERROR]  ConcurrentCompilationError: You ran Webpack twice. Each instance only supports a single concurrent compilation at a time.
    at Compiler.watch (/home/srghma/projects/webpack-hot-middleware/example/node_modules/webpack/lib/Compiler.js:319:19)
    at /home/srghma/projects/webpack-hot-middleware/example/server.js:54:12
    at Object.<anonymous> (/home/srghma/projects/webpack-hot-middleware/example/server.js:65:3)
    at Module._compile (internal/modules/cjs/loader.js:1151:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1171:10)
    at Module.load (internal/modules/cjs/loader.js:1000:32)
    at Function.Module._load (internal/modules/cjs/loader.js:899:14)
    at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:71:12)
    at internal/main/run_main_module.js:17:47
[20:56:23.790] [LOG]    Listening on {"address":"::","family":"IPv6","port":1616}
[20:56:24.205] [LOG]    2

if I call .watch twice
  var webpack = require('webpack');
  var webpackConfig = require('./webpack.config');
  var compiler = webpack(
    {
      target: 'node',
      mode: 'production',

      output: {
        filename: "output.js",
      },

      entry: './entry.js'
    }
  );

  compiler.watch({
    aggregateTimeout: 300,
    poll: undefined
  }, (err, stats) => {
    if (err) return console.error(err)
    if (!stats.hasErrors()) {
      console.log('1')
    } else {
      console.log('2')
    }
  })

  compiler.watch({
    aggregateTimeout: 300,
    poll: undefined
  }, (err, stats) => {
    if (err) return console.error(err)
    if (!stats.hasErrors()) {
      console.log('3')
    } else {
      console.log('4')
    }
  })

What is the expected behavior?
I can register .watch as much as I want
this is especially annoying when using webpack-dev-middleware, I cannot register new watch because there is already watch registered
https://github.com/webpack/webpack-dev-middleware/blob/e400f57a0c577fa543a7b716ed2bed7c1d5adceb/src/index.js#L60

Other relevant information:
webpack version:  5.0.0-beta.13 and 4
Node.js version: v13.8.0
Operating System: linux
Additional tools: none

Because you can run webpack twice, you should use:
compiler.watch(options, (err, stats) => {
  compiler.watch(options, (err, stats) => {});
})

this is especially annoying when using webpack-dev-middleware, I cannot register new watch because there is already watch registered

Please provide full configuration

@evilebottnawi updated

The error says: You can't call watch twice. Don't do that. After the first watch it's already watching, why do you want to call it twice...

Because I think this example https://github.com/alexmingoia/pux-starter-app/blob/f29ac097dbfca9ac36805e1b50ce4568afc2fb0e/webpack.config.client.js#L117 was working with old versions of webpack-dev-middleware
(Now I have to use https://github.com/webpack/webpack-dev-middleware#waituntilvalidcallback )
But why shouldn't I be able to register several watchers

watch doesn't register a watcher callback. It starts watching of the Compiler. It was never working correctly only the error message is new. You can attach additional listeners when the build is done with compiler.hooks.done.tap("YourPlugin", stats => {})

This is ok for me too, thx )


Add google analytics

Questions:

do we need to have all of our future projects on the same domain to compare data between them?

Get the key from GAnalytics when signed in with cot gmail acct.


Issues to enable DMA for SweRV

Hi,
I am trying to enable DMA for SweRV. I did following changes in testbench/tb_top.sv
1.added following signal
logic [31:0] dma_haddr;
logic [2:0] dma_hburst;
logic [3:0] dma_hprot;
logic [2:0] dma_hsize;
logic [1:0] dma_htrans;
logic dma_hmastlock;
logic dma_hwrite;
wire dma_hresp_out;

port mapping
// DMA Slave
//---------------------------------------------------------------
.dma_haddr ('0) replaced with ( dma_haddr ),
.dma_hburst ('0) replaced with ( dma_hburst ),
.dma_hmastlock ('0) replaced with ( dma_hmastlock),
.dma_hprot ('0) replaced with ( dma_hprot ),
.dma_hsize ('0) replaced with ( dma_hsize),
.dma_htrans ('0) replaced with ( dma_htrans),
.dma_hwrite ('0) replaced with ( dma_hwrite ),
.dma_hwdata ('0) replaced with ( dma_hwdata ),
.dma_hrdata          ( dma_hrdata    ),
.dma_hresp          (dma_out)   replaced with   ( dma_hresp_out   ),
.dma_hsel            ( 1'b1            ),
.dma_hreadyin        ( dma_hready_out  ),
.dma_hreadyout       ( dma_hready_out  ),

added instance
ahb_sif o_ahb_dma (

.HWDATA(dma_hwdata),
.HCLK(core_clk),
.HSEL(1'b1),
.HPROT(dma_hprot),
.HWRITE(dma_hwrite),
.HTRANS(dma_htrans),
.HSIZE(dma_hsize),
.HREADY(dma_hready),
.HRESETn(reset_l),
.HADDR(dma_haddr),
.HBURST(dma_hburst),

.HREADYOUT(dma_hready),
.HRESP(dma_hresp),
.HRDATA(dma_hrdata)

);

I have DMA controller (master) to drive read or write requests into ICCM/DCCM
after all , ran verilator and got hello world but DMA is not enable as ICCM and DCCM donot getting any data.
Here is GTKwave for reference

Please help me, to enable DMA for SweRV
Thanks & Regards
Rajoo

Hi Rajoo,
Looking a your waveform, I notice a couple of things:

Your dma_bus_clk_en is 0. This should be 1 to enable the DMA bus interface clocking. See the PRM for details on how the clock enables control clock ratios. A 0 effectively disables the clock.

I do not see any DMA read/swrite initiated in the portion of the waveform shown. Your testbench bfm/DMA master must initiate read/write sequences on the bus. The core is a slave and will respond.

-Ajay

Hi Ajay,
I set dma_bus_clk_en to 1 as you suggested (also referred  PRM) but DMA is not enable.
Here snapshot of DMA master signal.

Thanks & Regards
Rajoo

Please show me a snapshot of waveform where your testbench  AHB master is initiating a read or write on the dma* AHB bus (assuming you are using the AHB flavor of the interface and not AXI).
The DMA port is a slave port and an external agent has to initiate the activity.

Hi Ajay,
Please find snapshot of AHB master initiating a read or write on the dma AHB bus.

Previously there is no code in testbench to initiating a read or write on the dma AHB bus.
so added following code in testbench as I mentioned in my issue post.

Thanks & Regards
Rajoo

Hi,
I am trying to enable DMA for SweRV. Inside design , there is a DMA controller which work as master for DMA.
if anybody enable DMA , Please help me to enable it.
Thanks & Regards
Rajoo

Hi Rajoo,
The SweRV core has a DMA slave port, not a DMA master port. You need an external master to pull/push data from/to the core.
Ajay

Hi , if we want to use the iccm ，Can I simply edit the link file， And let the cpu core to automatically download the code from external rom/ram/flash, is that possible, if we do not have the dma master design, but we still want to run code in iccm


Image analysis fails after "building cache" and only prints "killed"

Hi,
I'm not able to analyze a pretty big image (~30GB). The output is:
Image Source: docker://myImage
Fetching image... (this can take a while for large images)
Analyzing image...
Building cache...
Killed
Is there an option to get more details why it fails? I have enough disk space, I think that should't be a problem.
Thank you.

+1

@mark2185 No, unfortunately not. I also have not tried to reproduce it with another image.

same problem as yours
dive a 4GB image and got self Killed

I encountered this error today. ~45 GB image, unfortunately not public :-(
My machine has 64 GB of memory, and after reading your question regarding memory, I brought up Resource Monitor (I'm running docker in WSL2 on Windows 10) -- and watched it chew through all remaining memory.
Some context: this image contains an entire development environment with lots of tools installed.  I wanted to use dive so I could see what each layer (RUN command) adds... in hopes that I could find a common base to be refactored into a multi stage build.
Which leads me to my question...
I suspect that finding a way to use less memory will be hard (if not impossible). In leiu of that, would you consider a feature that let one specify the "Last  layers" to be analyzed by dive? That would help my use case, at least :-)
I could optimize my HUGE docker image, say, 10 layers at a time.
Thanks for making dive!

I encountered this error today. ~45 GB image, unfortunately not public :-(
My machine has 64 GB of memory, and after reading your question regarding memory, I brought up Resource Monitor (I'm running docker in WSL2 on Windows 10) -- and watched it chew through all remaining memory.
Some context: this image contains an entire development environment with lots of tools installed.  I wanted to use dive so I could see what each layer (RUN command) adds... in hopes that I could find a common base to be refactored into a multi stage build.
Which leads me to my question...
I suspect that finding a way to use less memory will be hard (if not impossible). In leiu of that, would you consider a feature that let one specify the "Last n layers" to be analyzed by dive? That would help my use case, at least :-)
I could optimize my HUGE docker image, say, 10 layers at a time.
Thanks for making dive!

+1 same here.
Cannot analyze image based on windows Server Core (5G) - telling me :
" path error at layer index Index(0-47:48): unable to add ......"
So maybe a feature to analyze only X top numbers of layers (I won't optimize microsoft layers.....)
Thx.


Consider adding a minimal Dockerfile extending rstudio/plumber

One of the great things about plumber is how easy it is to get starting with testing to deploy it using the rstudio/plumber Docker image.
For valve, it would make a lot of sense to give an example of a minimal dockerfile extending the rstudio/plumber image with valve.

This is a great idea! I'll work on that.
Would you expect a single vignette / article would suffice? Or would there need to be a template Dockerfile incuded with an R package for it?

How is this article?
https://valve.josiahparry.com/articles/using-valve-with-docker

Amazing! I fixed some typos in a PR #7

Thank you!


Add retina logo for Mac

Describe the bug
Add a retina logo for Mac.
To Reproduce
Steps to reproduce the behavior:

Cmd + Tab

Expected behavior
Retina logo for Mac.
Screenshots

Altair

Version 2.1.5 (<IP_ADDRESS>70)

Desktop (please complete the following information):

OS: Macos 10.14.4
Browser: Google Chrome
Version: 73.0

👍


support control connect pool size ?

see title, thank u.

No, this library doesn't implement connection pool.


Migrate to null safety

Any plans to support null safety?

done
blue_thermal_printer 1.1.2

nice!


Use tfoot for pager component

I think it's better to use tfoot element for pagingContent.
Now if use bootstrap styling like this: "table table-striped table-hover" pager also will apply it.

Thanks for submitting this issue and I realize it's been quite some time since you posted but with the new architecture, we recommend doing this sort of thing through customization options or as a plugin. 👍


Handle ERROR_DIRECTORY when calling FindFirstFileExA

If a directory referenced by .ninja_deps has changed to a regular file
since the last build, FindFirstFileExA will return ERROR_DIRECTORY.
Fixes #2159

Is this on track to be merged, or do I need to do something?

Thanks for the input! I've added a test. The "Linux / build-with-python" failure looks unrelated ("apt update" failed). Is there some way to re-trigger the checks that failed?

Only maintainers can trigger a rebuild without a new commit.
you can change the commit hash and force-push, i suppose.

Ping? This is fixing a real problem.

👍  Happening here as well
Administrator@EC2AMAZ-VJT82A0 MINGW64 ~/Desktop/ELECTRONS/20.0.3/src/electron (v20.0.3)
$ e build
Running "ninja.exe -j 200 electron" in C:\Users\Administrator\Desktop\ELECTRONS\20.0.3\src\out\RELEASE-20.0.3
ninja: error: FindFirstFileExA(../../buildtools/third_party/libc++/trunk/include/__string): The directory name is invalid.

ERROR Error: Command failed: ninja.exe -j 200 electron
    at checkExecSyncError (node:child_process:828:11)
    at Object.execFileSync (node:child_process:866:15)
    at Object.depotExecFileSync [as execFileSync] (C:\Users\Administrator\.electron_build_tools\src\utils\depot-tools.js:125:23)
    at runNinja (C:\Users\Administrator\.electron_build_tools\src\e-build.js:60:9)
    at Command.<anonymous> (C:\Users\Administrator\.electron_build_tools\src\e-build.js:121:7)
    at Command.listener [as _actionHandler] (C:\Users\Administrator\.electron_build_tools\node_modules\commander\lib\command.js:480:17)
    at C:\Users\Administrator\.electron_build_tools\node_modules\commander\lib\command.js:1234:65
    at Command._chainOrCall (C:\Users\Administrator\.electron_build_tools\node_modules\commander\lib\command.js:1151:12)
    at Command._parseCommand (C:\Users\Administrator\.electron_build_tools\node_modules\commander\lib\command.js:1234:27)
    at Command.parse (C:\Users\Administrator\.electron_build_tools\node_modules\commander\lib\command.js:889:10)

We're going to hit this again in Chromium as we pull in https://github.com/llvm/llvm-project/commit/2d52c6bfae801b016dd3627b8c0e7c4a99405549 where libc++ is changing __tuple from a file to a directory (it's the reverse that triggers this bug, but buildbots and developers will hit it as they go back and forth across that change).


setEpoch(): unix time (convert internally to y2k) and no 100-yr offset

Untested in software or hardware.
This should provide the offset required to make the datum for setEpoch() be 01/01/1970 instead of 01/01/2000, as is expected both from its own documentation and from the way much of the rest of this library works (even if the DS3231 itself zeros out at 01/01/2000).
Tagging relevant folks: @hasenradball @IowaDave @bill-ba @leslieadams57
And issue #53
And this PR: https://github.com/NorthernWidget/DS3231/pull/60
I'm still not sure if tm_wday and tm_mon need their +1s. Going to look at the differences between the C++ library and the DS3231 data sheet at some point after this, and add any changes as needed to this PR.

Should we make so defined tests?
Feeding some specific values for the Epoch and check the data?

@awickert you have done every needed change right?

Defined tests would be great.
I am not sure if I have done every needed change; see my notes on tm_wday and tm_mon.
Unfortunately, I will not have any hardware with me for at least one more week, so I cannot perform a hardware test of this code. I have not yet tried to compile, but can.

Hi Andy,
Iam actually not sure was was going wrong with the actual implementation, because I used the actual lib and tried compare the time from ESP8266 and the time from DS3231 and this are the same.
see here:

Or do I anything wrong?

In the ESP8266 it refers to the following time libs:
strftime
Were for example:
Weekday as a decimal number with Sunday as 0 (0-6)

During Testing I missed the following member function:
dayOfTheWeek()
Was this not implemented i the past?

@awickert Hi Andy,
I think I got the issue now correctly:

the ESP8266 uses a time.hwhich refers to the data of 1970.
The AVR Lib refers to a different time.h which uses time of 2000.

Let us make these things clear.
I will try to figure out a optimal solution.
What do you think?
And waht about the missing member function dayOfWeek()?

My idea is to make a simple sketch which runs on ESP8266 and Arduino, feeding a defined UnixTimestamp to the setEpoch function and read out the time from DS3231.
The results schouls be the same then.
Thats wat i would do.

My thoughts, in summary:

There are two platforms that use different epochs, and so we should find a way to accommodate them. We can do this by:

Adding an option that we pass to the function, which should default to the value used on Arduino/AVR
Creating a method to detect the hardware internally

dayOfTheWeek is implemented in the header only, and is fundamentally unimportant here.
We should systematically find out which libraries are 0- or 1- indexed and how this compares to the data sheets.
Then, fix these if needed
In the end, we can write a test sketch

Sound good?

Hi,
just for clarification.
I cannot see the definition of  dayOfTheWeek.

Thus I would check then all data also the output of DayOfTheWeek.

@awickert @hasenradball : I really appreciate the attention being given to this issue. I can help with testing. This morning (in Iowa) I will prepare a short test sketch and run it on both AVR and 8266. Perhaps I'll test it with a SAMD Arduino also. My next post in this PR will provide the sketch and the results.

This thread includes mention of the DateTime::dayOfTheWeek() method also. May I offer an observation? These comments are fresh in mind after drafting documentation for the DateTime object.
DateTime objects have no Century property. I suspect the practical range of dates for DateTime objects may be limited to those between 01 January 2000 and 31 December 2099, for two reasons.

Year is implemented as 00-99 even though it is declared as type uint16_t in the class.

The constructor, DateTime::(uint32_t: t), does indeed expect the parameter to represent time since 01 January 1970 GMT; however, it then adjusts the number of seconds to represent time since 01 January 2000.

The constructor does this by subtracting the constant, #define SECONDS_FROM_1970_TO_2000 946684800, prior to parsing the value into the various different properties of date and time.
Conversely, the DateTime::unixtime() method reverses the process by adding the same constant immediately prior to returning the result.

@IowaDave
Great I am also working on a preparing an sketch.

Thanks, both.
A request: Could we leave the dayOfTheWeek question for another thread, and in general, open new threads for new topics? Feel free to open one and reference the discussion here.

Hi Togheter,
with my gist I can check now the output of:

the DS3231 class itself
the RTC class
the content of the struct tm of the refernced lib time.h

The result using the offset Correction for the ESP8266 shows the following result:

Next Step is to check the output of Arduino Nano.

If I remove the 2000 Correction AND the 100 year offset. I get the following results on the ESP8266.

The Question I have is...
why does the function Serial.print(Clock.getYear(), DEC); returns value >100?

Thanks, both.
A request: Could we leave the dayOfTheWeek question for another thread, and in general, open new threads for new topics? Feel free to open one and reference the discussion here.

@awickert
sure let us first fix the main issue of this PR.
Wen can the dayOfWeek issue in an other topic.

I want to share an additional information:

tm_year -> gives year since 1900 => so the offset by 100 is fine ==> setYear(tmnow.tm_year - 100U);
tm_wday -> gives [0-6] => DS3231 uses [1-7] => so this is also fine ==> setDoW(tmnow.tm_wday + 1U);
tm_mon -> gives [0-11] => DS3231 used [1-12] => so this is also fine ==> setMonth(tmnow.tm_mon + 1U);

So in addition to the point with ESP8266
The function setEpoch is fine with this implementation, as it is in the repo.

Now the question is whats going wrong?
I wil now check this implementation on the Arduino Nano.

...and additionally can the complainers give their sketch what they did?

I feel unsure of where things stand regarding a test sketch.  Begging your pardon for possible redundancy, I have one to offer, along with results from testing on AVR (Arduino Nano ATmega328P). Will post results for 8266 and Arduino Zero soon.
GMT Time and Date:
12:25:00 P.M. 08/07/2022 =<PHONE_NUMBER>, according to https://unixtime.org/.
DS3231 Result with AVR:
12:25:0 P.M. 8/6/52
The Century Bit is clear.
DS3231 Epoch:<PHONE_NUMBER> // = RTClib:now().unixtime();
GMT Epoch:<PHONE_NUMBER>
The two epoch values do not agree.
Here is the sketch. It's a great big paste job. Sorry I am not up to speed on all things Github. What is a gist?
/* Worked Example
 * Suppose a web site tells you that the "epoch" time
 * at 12:25:00 p.m. GMT on August 7, 2022 was<PHONE_NUMBER>.
 */

// import the library
 #include <DS3231.h>

// instantiate a DS3231 object
DS3231 myRTC;

// declre some variables for the various time parameters
byte mySecond, myMinute, myHour, myDoW, myDate, myMonth, myYear;
bool hpm, Century, h12;
DateTime myEpoch;

// Initialize a (unsigned long) variable to contain the epoch time.
time_t epochGMT =<PHONE_NUMBER>UL;

void setup() {

  Wire.begin();
  Serial.begin(9600);
  while (!Serial);
  Serial.println();

  // Set the hour mode on the DS3231
  // (best to do this before setting the time)
  myRTC.setClockMode(true); // 12-hour mode

  // Set the time on the DS3231
  myRTC.setEpoch(epochGMT);

  // Retrieve the time parameters
  // from the DS3231
  mySecond = myRTC.getSecond();
  myMinute = myRTC.getMinute();
  myHour = myRTC.getHour( h12, hpm );
  myDoW = myRTC.getDoW();
  myDate = myRTC.getDate();
  myMonth = myRTC.getMonth( Century );
  myYear = myRTC.getYear();
  myEpoch = RTClib::now();

  // Display the GMT time and date
  Serial.println("GMT Time and Date:");
  Serial.println("12:25:00 P.M. 08/07/2022\n");

  // Print the values obtained from DS3231
  Serial.println("DS3231 Result:");
  Serial.print(myHour);
  Serial.print(":");
  Serial.print(myMinute);
  Serial.print(":");
  Serial.print(mySecond);
  Serial.print(" ");
  if (h12) {
    if (hpm) {
      Serial.print("P.M. ");
    } else {
      Serial.print("A.M. ");
    }
  }
  Serial.print(myMonth);
  Serial.print("/");
  Serial.print(myDate);
  Serial.print("/");
  Serial.println(myYear);
  Serial.print("The Century Bit is ");
  if (Century) {
    Serial.println("set.");
  } else {
    Serial.println("clear.");
  }
  Serial.print("DS3231 Epoch: ");
  Serial.println(myEpoch.unixtime(), DEC);
  Serial.print("GMT Epoch:    ");
  Serial.println(epochGMT, DEC);
  Serial.print("The two epoch values ");
  if (myEpoch.unixtime() == epochGMT) {
    Serial.println("agree.");
  } else {
    Serial.println("do not agree.");
  }

}

void loop() {
  // put your main code here, to run repeatedly:

}

@IowaDave see the link for the gist :-)
https://gist.github.com/hasenradball/4d6a9ea9fa596e9d21bcb93658c6fd4c

Hi all,
see here my results for the AVR (Aduino Nano):

@awickert @IowaDave
I could now present a fix for this Issue.
It is a Bugfix for the AVR platform.
See my results:

Remark:
the differences in weekday is fine because the DS3231 has the range [1-7] and the time.h lib ranges from [0-6].
My Proposed Solution:

I will  pull the corrected code, only changes inside the setEpoch()
I will additionally provide a new example for testing this.

Additionally this is the corrected setEpoch function:
// setEpoch function gives the epoch as parameter and feeds the RTC
// epoch = UnixTime and starts at 01.01.1970 00:00:00
// HINT: => the AVR time.h Lib is based on the year 2000
void DS3231::setEpoch(time_t epoch, bool flag_localtime) {
#if defined (__AVR__)
	epoch -= SECONDS_FROM_1970_TO_2000;
#endif
	struct tm tmnow;
	if (flag_localtime) {
		localtime_r(&epoch, &tmnow);
	}
	else {
		gmtime_r(&epoch, &tmnow);
	}
	setSecond(tmnow.tm_sec);
	setMinute(tmnow.tm_min);
	setHour(tmnow.tm_hour);
	setDoW(tmnow.tm_wday + 1U);
	setDate(tmnow.tm_mday);
	setMonth(tmnow.tm_mon + 1U);
	setYear(tmnow.tm_year - 100U);
}

Give me some hint how to proceed.
Thanks for all
:+1

The proposed bugfix obtains a correct result in the DS3231 now, for the test code I offered earlier today, when run on an AVR.
The parameter for "localtime" seems to make no difference in the result of the new function.  This does not surprise me, as the DS3231 makes no provision for time zones. Perhaps we do not need that parameter at all?
We still see a discrepancy between the Epoch uploaded to the DS3231 compared with the unixtime() obtained from a DateTime created with the RTClib::now() method.

GMT Time and Date:
12:25:00 P.M. 08/07/2022
Testing with 'localtime' flag = false.
DS3231 Result:
12:25:0 P.M. 8/7/22
The Century Bit is clear.
DS3231 Epoch:<PHONE_NUMBER>
GMT Epoch:<PHONE_NUMBER>
The two epoch values do not agree.

GMT Time and Date:
12:25:00 P.M. 08/07/2022
Testing with 'localtime' flag = true.
DS3231 Result:
12:25:0 P.M. 8/7/22
The Century Bit is clear.
DS3231 Epoch:<PHONE_NUMBER>
GMT Epoch:<PHONE_NUMBER>
The two epoch values do not agree.

To clarify labeling in the previous post, "DS3231 Epoch" refers to a derived value. The settings entered into the DS3231 by the setEpoch() method are immediately retrieved into a DateTime by the RTClib::now() method. Then a value is derived from that DateTime using its unixtime() method. The derived value is labeled "DS3231 Epoch".
It's clear that an Epoch timestamp does not survive the voyage into the DS3231 then back out again through a DateTime.

@IowaDave on which System did you test this?
I assume on the Arduino, right?
The arduino has no timezone information too.
Yes your post about localtime could lead to such a behaviour on the Arduino.
Because the localtime is used to store the „localtime“ directly into the DS3231, which allows you to use your local time on the any device connected to your DS3231.
But this works when the microcontoller has info about the timezone (to be able to use localtime) like the esp8266, IF time was synchronized successfully.
This function was not able before I introduced the setEpoch method.
Please test it on the ESP8266, i used it since many month.
best regards
Frank

The previous test was done with an AVR-based Arduino Nano, having an ATmega328P MPU.
In this post I provide results from testing on an 8266 board, as requested.
The results obtained in the DS3231 appear to be correct.
No difference is seen between the two values of the 'localtime' parameter; (false) and (true) lead to identical results.
The input "GMT Epoch" and the output result of RTClib::now().unixtime(); remain unequal. This difference was  observed with the AVR-based test, also.

Testing with 8266
Lolin Wemos D1 Mini Clone
Arduino IDE 1.8.15
August 16, 2022

GMT Time and Date:
12:25:00 P.M. 08/07/2022
Testing with 'localtime' flag = true.
DS3231 Result:
12:25:0 P.M. 8/7/22
The Century Bit is clear.
DS3231 Epoch:<PHONE_NUMBER>
GMT Epoch:<PHONE_NUMBER>
The two epoch values do not agree.

GMT Time and Date:
12:25:00 P.M. 08/07/2022
Testing with 'localtime' flag = false.
DS3231 Result:
12:25:0 P.M. 8/7/22
The Century Bit is clear.
DS3231 Epoch:<PHONE_NUMBER>
GMT Epoch:<PHONE_NUMBER>
The two epoch values do not agree.

I will not in a position to work on this issue the remainder of today. I will come back to it tomorrow (Wednesday) morning, Iowa (USA) time, which is GMT - 5 hours.  In other words, it will be after Noon in Greenwich, England.
Relax. We will figure this out. Thanks to all for contributing thoughts and solutions!
David

Hi David as I tried to mention, the localtime flag will work on the ESp8266 if the internal clock of the ESP8266 was syncronized successfully.
You had to use configTime(...) and all that stuff so that the internal RTC ist synched with the NTPserver,
Then it has the information about the TimeZone and up to now the localtime flag makes a difference.

@IowaDave @awickert
I had a look to your second complain  -> the Epoch does not fit together.
I has to do with the following code.
// UNIX time: IS CORRECT ONLY WHEN SET TO UTC!!!
uint32_t DateTime::unixtime(void) const {
  uint32_t t;
  uint16_t days = date2days(yOff, m, d);
  t = time2long(days, hh, mm, ss);
  t += SECONDS_FROM_1970_TO_2000;  // seconds from 1970 to 2000

  return t;
}

If there is a issue that the epoch does not fit together it must have to do with the following function:
time2long() or date2days.
Because the values stored in the DS3231 are then based on 01.01.2000, in all cases now, right?
And coming back to UnixTime we had to add the constant SECONDS_FROM_1970_TO_2000, so the issue has to come by these functions.

@awickert @IowaDave
Maybe thats the point !!!
// number of days since 2000/01/01, valid for 2001..2099
static uint16_t date2days(uint16_t y, uint8_t m, uint8_t d) {
    if (y >= 2000)
        y -= 2000;
    uint16_t days = d;
    for (uint8_t i = 1; i < m; ++i)
        days += pgm_read_byte(daysInMonth + i - 1);
    if (m > 2 && isleapYear(y))
        ++days;
    return days + 365 * y + (y + 3) / 4 - 1;
}

Here is the calculation of 365 * y, but in general we calculate it as 365.25F * y

You bring good eyes to the aid of our cause. Thank you!
At the very least, it makes sense to reconsider the calculation algorithm
going from date+time to an integer number of seconds.
I have an approach in mind to obtain an accurate result using only integer
arithmetic.
Let us work on this. I'll share a working example within the next day or
two. Will look forward also to seeing what you might choose to share.
With appreciation,
David
On Wed, Aug 17, 2022 at 7:03 AM Hasenradball @.***>
wrote:

@awickert https://github.com/awickert @IowaDave
https://github.com/IowaDave
Maybe thats the point !!!
// number of days since 2000/01/01, valid for 2001..2099
static uint16_t date2days(uint16_t y, uint8_t m, uint8_t d) {
if (y >= 2000)
y -= 2000;
uint16_t days = d;
for (uint8_t i = 1; i < m; ++i)
days += pgm_read_byte(daysInMonth + i - 1);
if (m > 2 && isleapYear(y))
++days;
return days + 365 * y + (y + 3) / 4 - 1;
}
Here is the calculation of 365 * y, but in general we calculate it as 365.25F

y

—
Reply to this email directly, view it on GitHub
https://github.com/NorthernWidget/DS3231/pull/65#issuecomment-1217919576,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIOVVUDL4DDSAYFMU3CYUO3VZTIK3ANCNFSM56TMML3A
.
You are receiving this because you were mentioned.Message ID:
@.***>

I have a solution for calculating unixtime() correctly. The following code has been tested with success on both AVR and 8266.
Specific date and time values are entered individually, corrresponding to a Unix Timestamp of<PHONE_NUMBER>.
A function recombines the individual date and time values into a calculated "unixtime" value.
The result agrees with the Unix Timestamp that we started with.
Comments on the code, offered for discussion:

It uses only integer arithmetic. AVR and ESP8266 CPUs can have very fast and code-efficient integer multiplication opcodes but both of them lack a hardware Floating Point Unit. Using integer math avoids the need to import a software floating-point library into the program flash memory.
The approach is simply to begin with SECONDS_FROM_1970_TO_2000, then progressively add seconds for the years, months, days, hours, minutes and seconds since January 1, 2000.
Comments in the code describe each successive step.
The code uses two arrays of integer constants as lookup tables. One array is for leap years, the other for non-leap years. This approach bypasses calculation of days in months. Instead, the number of days in the year prior to the current month is obtained directly from the relevant array.
I placed the arrays in program (flash) memory. They occupy 52 bytes. My hunch is that the code to implement floating-point calculations, including
Determining leap year is a simple integer division. This is appropriate for "year" values stored in a DateTime because that value is actually a two-digit offset from 2000, that is, 00 to 99, only. Understanding this allows the code to omit a call to the isleapYear() function.
IMHO the DateTime class should be modified as follows:

Add a uint32_t property for unixtime to the protected list
Implement the calculation of that unixtime property in the constructors. It probably should be defined as a private function that returns a uint32_t, then call it from the constructor.
Redefine the DateTime::unixtime() method. Have it simply return the protected unixtime property. Doing this should not break existing code because both the parameter list (empty) and the return value (uint32_t, or time_t) would remain the same.

The code listing follows:

#define SECONDS_FROM_1970_TO_2000 946684800UL
#define SECONDS_IN_YEAR 31536000UL
#define SECONDS_IN_DAY 86400UL

const PROGMEM uint16_t normalYear[] =
  // days in the year prior to the current month
  {
      0, // to be ignored
      0, // January
     31, // February
     59, // March
     90, // April
    120, // May
    151, // June
    181, // July
    212, // August
    243, // September
    273, // October
    304, // November
    334, // December
  };

const PROGMEM uint16_t leapYear[] =
  // days in the year prior to the current month
  {
      0, // to be ignored
      0, // January
     31, // February
     60, // March
     91, // April
    121, // May
    152, // June
    182, // July
    213, // August
    244, // September
    274, // October
    305, // November
    335, // December
  };

// set up a struct to mimic a DateTime
struct DateLike{
  uint16_t year;
  uint8_t month;
  uint8_t day;
  uint8_t hour;
  uint8_t minute;
  uint8_t second;
  uint32_t epochTime;
  void calculateEpoch();
};

/* Define a function to Calculate the epoch timestamp.
 * Note: found it necessary to cast all interim calculations
 * to be type uiint32_t in order to ensure the compiler
 * does not use 16-bit arithmetic.
 */

void DateLike::calculateEpoch() {
  // begin with seconds prior to January 1, 2000
  epochTime = SECONDS_FROM_1970_TO_2000;
  // add seconds for whole years since 2000
  // will add leap days after this
  epochTime += (uint32_t) year * SECONDS_IN_YEAR;
  // Leap days = (year / 4) + 1
  // because 2000 was a leap year
  // add seconds for leap days
  epochTime += (( (uint32_t) year / 4) + 1) * SECONDS_IN_DAY;

  /* The procedure to add seconds for whole months
   *  prior to the current month is as follows:
   *   - ascertain whether current year is a leap year
   *   - fetch number of days from relevant array
   *   - multiply by SECONDS_IN_DAY
   */

   if ( (year % 4) == 0 ) {
     // it is a leap year
     epochTime += (uint32_t)
       pgm_read_word_near(leapYear + (uint32_t) month)
       * SECONDS_IN_DAY;
   } else {
    // it is not a leap year
     epochTime += (uint32_t)
       pgm_read_word_near(normalYear + (uint32_t) month)
       * SECONDS_IN_DAY;
   }

   // add seconds for whole days in month
   epochTime += ( (uint32_t) day - 1) * SECONDS_IN_DAY;

   // add seconds for hour, minute and second
   epochTime +=
      (uint32_t) hour * 3600
     + (uint32_t) minute * 60
     + (uint32_t) second;
}

// declare a datelike container
DateLike myDate;

void setup() {

  Serial.begin(9600);
  while (!Serial);
  Serial.println();

  // initialize the values of myDate
  // corresponding to Unix Timestamp<PHONE_NUMBER>
  myDate.year = 22;
  myDate.month = 8;
  myDate.day = 7;
  myDate.hour = 12;
  myDate.minute = 25;
  myDate.second = 0;
  // calculate the unix timestamp
  myDate.calculateEpoch();

  // print the result
  Serial.println(myDate.epochTime, DEC);

  // Correct output would equal<PHONE_NUMBER>

}

void loop() {
  // nothing to see here; move along...

}

Dear Frank,
Thank you for your kind words.
To your questions:

Did I examine the existing functions? Not much. Your investigation gave us a good clue.
uint64_t? I am not smart enough to address that question.
Yes I studied the leap year rules. For DateTime we are concerned with years 2000 through 2099, only. "Evenly-divisible-by-four" is the only relevant rule during this range of years. 2000 was a leap year because evenly divisible by 400. The next time the "400" rule will apply is in the year 2400.
I work with Arduino IDE, only, and almost exclusively with AVR microcontrollers.

I shall work toward a PR proposing changes to the DateTime object.
Appreciatively,
David

@awickert , @hasenradball   I will soon submit a PR for DateTime addressing a few issues (unsuitable types, possible mis-counting of leap days) that could have bugged results under certain circumstances. Then we can continue discussion of DateTime in that PR. But for now, please allow me to address a question here. Is the design goal for DateTime to focus exclusively on the years 2000 through 2099?
Thanks

@IowaDave @awickert
Hi Dave,
for the Issue with the difference between ESP8266 and AVR Platform I made a PR regarding the setEpoch() function.
To answer your question, I am 48 years old now and I don't know if I will reach the year 2099 so devil-may-care.
But if we wil spent mor time in this topic I have to dig more in detail into the HW of the DS3231.
Have a nice weekend.
best regards
frank

@awickert @IowaDave
Hi both, I would appreciate if the PR #66 could be accepted and merged, to fix the issue with platform AVR.
It was tested on ESP8266 and AVR.

Resuming work on this library as of 05 Sept 2022. It is a holiday in the U.S., so I can devote the whole day. Intend to evaluate both this PR #65 by @awickert and PR #66 by @hasenradball with the intent to resolve both PRs today.

Oops, closed before recording the reason why. Reopening to do that.

Closing this PR #65 because PR #66 incorporates #65 while adding an architecture check to make it work with both AVR and ESP8266. Issues addressed by this #65 are resolved by #66.


add controller to snippetsFilter status

Proposed changes
Write a clear and concise description that helps reviewers understand the purpose and impact of your changes. Use the
following format:
Problem: Users want to ensure controller name is added when condition is added to SnippetsFilter.
Solution: Modify the SnippetsFilterStatus to include controller name writing status.
Testing: Unit tests
Manual Testing with two installations of NGF using different controllers
k describe snippetsfilters.gateway.nginx.org access-control
Name:         access-control
Namespace:    default
Labels:       <none>
Annotations:  <none>
API Version:  gateway.nginx.org/v1alpha1
Kind:         SnippetsFilter
Metadata:
  Creation Timestamp:  2024-09-18T16:05:05Z
  Generation:          2
  Resource Version:    599427
  UID:                 0da2968d-396e-4677-bf5f-b17be5ca4e12
Spec:
  Snippets:
    Context:  http
    Value:    limit_req_zone $binary_remote_addr zone=myzone:10m rate=1r/s;
    Context:  http.server.location
    Value:    limit_req zone=myzone burst=3;
Status:
  Controllers:
    Conditions:
      Last Transition Time:  2024-09-18T20:42:58Z
      Message:               SnippetsFilter is accepted
      Observed Generation:   2
      Reason:                Accepted
      Status:                True
      Type:                  Accepted
    Controller Name:         gateway.nginx.org/nginx-gateway-controller
    Conditions:
      Last Transition Time:  2024-09-18T20:43:20Z
      Message:               SnippetsFilter is accepted
      Observed Generation:   2
      Reason:                Accepted
      Status:                True
      Type:                  Accepted
    Controller Name:         gateway.nginx.org/nginx-gateway-controller-2
Events:                      <none>
sa.choudhary@N9939CQ4P0 ~ %

Please focus on (optional): If you any specific areas where you would like reviewers to focus their attention or provide
specific feedback, add them here.
Closes #ISSUE
Checklist
Before creating a PR, run through this checklist and mark each as complete.

[x] I have read the CONTRIBUTING doc
[x] I have added tests that prove my fix is effective or that my feature works
[x] I have checked that all unit tests pass after adding my changes
[x] I have updated necessary documentation
[x] I have rebased my branch onto main
[x] I will ensure my PR is targeting the main branch and pulling from my branch from my own fork

Release notes
If this PR introduces a change that affects users and needs to be mentioned in the release notes,
please add a brief note that summarizes the change.

@salonichf5 did you manually test this?

@salonichf5 did you manually test this?

working on it :)

LGTM!
Just make sure to follow Kate's comment and add the issue number to the PR.


Configuration compatibility with MIT implementation

Trying to use a .net core application in a linux container against existing kerberos infrastructure.
Most documentation for apps in that situation indicate the need for using keytab files and rely on the MIT command line tools to set everything up.
The kdc information is in the /etc/krb5.conf.
It seems that  the ASPNetCore team also uses that for their Negotiate mechanism. It would be nice if Kerberos.Net also did.
KerberosClient should provide an initialization mechanism that consumes the same krb5.conf.
I am going to be doing this in my client right now but with some guidance I could contribute whatever I do if wanted.
Thx

Configuration support has been added in client and some KDC bits.


Does not work with latest yazi 0.3.3

It appears the code has not been updated for new API's

i can confirm it works on 0.3.3.
❯ yazi --version
Yazi 0.3.3 (7c445ce 2024-09-04)

❯ eza --version
eza - A modern, maintained replacement for ls
v0.20.8 [+git]
https://github.com/eza-community/eza

can you browse to the eza-preview folder and confirm the files are there?

Here is a PR that fixes this issue:
https://github.com/sharklasers996/eza-preview.yazi/pull/11
In the meantime you can use my fork: https://github.com/ahkohd/eza-preview.yazi

Great. Thanks. That works.
On Wed, Nov 20, 2024, at 13:23, Victor Aremu wrote:

Here is a PR that fixes this issue:
#11 https://github.com/sharklasers996/eza-preview.yazi/pull/11
In the meantime you can use my fork: https://github.com/ahkohd/eza-preview.yazi
—
Reply to this email directly, view it on GitHub https://github.com/sharklasers996/eza-preview.yazi/issues/8#issuecomment-2489567415, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALLYYRLLA754SGA7AKFZHQT2BT4TLAVCNFSM6AAAAABRSGBNEOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBZGU3DONBRGU.
You are receiving this because you authored the thread.Message ID: @.***>

I have added default level support, and you can now set key binds to increment and decrement tree levels.
https://github.com/ahkohd/eza-preview.yazi/tree/feature-level

Thanks. But changing the level to 1 or 3 seems to have no effect. Whatever I set it to I see the tree.
On Thu, Nov 21, 2024, at 00:58, Victor Aremu wrote:

I have added default level support, and you can now set key binds to increment and decrement tree levels.
https://github.com/ahkohd/eza-preview.yazi/tree/feature-level
—
Reply to this email directly, view it on GitHub https://github.com/sharklasers996/eza-preview.yazi/issues/8#issuecomment-2490426705, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALLYYRM3OJQXEMMTXZS4SOT2BWOB7AVCNFSM6AAAAABRSGBNEOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJQGQZDMNZQGU.
You are receiving this because you authored the thread.Message ID: @.***>

Thanks. But changing the level to 1 or 3 seems to have no effect. Whatever I set it to I see the tree.
…
On Thu, Nov 21, 2024, at 00:58, Victor Aremu wrote: I have added default level support, and you can now set key binds to increment and decrement tree levels. https://github.com/ahkohd/eza-preview.yazi/tree/feature-level — Reply to this email directly, view it on GitHub <#8 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALLYYRM3OJQXEMMTXZS4SOT2BWOB7AVCNFSM6AAAAABRSGBNEOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJQGQZDMNZQGU. You are receiving this because you authored the thread.Message ID: @.***>

yes this is expected if you set level to 1 you see a tree with level 1.

do you mean you don't want to see the tree by default?

I do see the tree by default. I just thought setting the level in my yazi init.lua would change the default.
On Thu, Nov 21, 2024, at 07:25, Victor Aremu wrote:

do you mean you don't want to see the tree by default?
—
Reply to this email directly, view it on GitHub https://github.com/sharklasers996/eza-preview.yazi/issues/8#issuecomment-2491531128, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALLYYRIBWO7KCDFW7MXDUJD2BX3N3AVCNFSM6AAAAABRSGBNEOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJRGUZTCMJSHA.
You are receiving this because you authored the thread.Message ID: @.***>

It works for me! are you sure you are using the feature-level or feature-level-symlinks branch?

It works for me! are you sure you are using the feature-level or feature-level-symlinks branch?

I set the level to 1:

And it only shows 1 level:

Sorry. I misunderstood how this works. Now I understand and it's great!
On Thu, Nov 21, 2024, at 07:39, Victor Aremu wrote:

It works for me! are you sure you are using the feature-level or feature-level-symlinks branch?
maybe pull changes, your local may be outdated

—
Reply to this email directly, view it on GitHub https://github.com/sharklasers996/eza-preview.yazi/issues/8#issuecomment-2491570921, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALLYYROO2UVZDK3QL5LB5VD2BX5DVAVCNFSM6AAAAABRSGBNEOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJRGU3TAOJSGE.
You are receiving this because you authored the thread.Message ID: @.***>

Can you send me a link please.
On Thu, Nov 21, 2024, at 08:32, Victor Aremu wrote:

Sorry. I misunderstood how this works. Now I understand and it's great!
… <#>
On Thu, Nov 21, 2024, at 07:39, Victor Aremu wrote: > > It works for me! are you sure you are using the feature-level or feature-level-symlinks branch? > maybe pull changes, your local may be outdated > — Reply to this email directly, view it on GitHub <#8 (comment) https://github.com/sharklasers996/eza-preview.yazi/issues/8#issuecomment-2491570921>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALLYYROO2UVZDK3QL5LB5VD2BX5DVAVCNFSM6AAAAABRSGBNEOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJRGU3TAOJSGE. You are receiving this because you authored the thread.Message ID: @.***>

Cool. Perhaps try out the feature-level-symlinks branch, which has the option to follow symlinks and deference!
—
Reply to this email directly, view it on GitHub https://github.com/sharklasers996/eza-preview.yazi/issues/8#issuecomment-2491716486, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALLYYRPFENQ55DWDNYOUBW32BYDKZAVCNFSM6AAAAABRSGBNEOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJRG4YTMNBYGY.
You are receiving this because you authored the thread.Message ID: @.***>

Can you send me a link please.
…
On Thu, Nov 21, 2024, at 08:32, Victor Aremu wrote: > > Sorry. I misunderstood how this works. Now I understand and it's great! > … <#> > On Thu, Nov 21, 2024, at 07:39, Victor Aremu wrote: > > It works for me! are you sure you are using the feature-level or feature-level-symlinks branch? > maybe pull changes, your local may be outdated > — Reply to this email directly, view it on GitHub <#8 (comment) <#8 (comment)>>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALLYYROO2UVZDK3QL5LB5VD2BX5DVAVCNFSM6AAAAABRSGBNEOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJRGU3TAOJSGE. You are receiving this because you authored the thread.Message ID: @.> > Cool. Perhaps try out the feature-level-symlinks branch, which has the option to follow symlinks and deference! — Reply to this email directly, view it on GitHub <#8 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALLYYRPFENQ55DWDNYOUBW32BYDKZAVCNFSM6AAAAABRSGBNEOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJRG4YTMNBYGY. You are receiving this because you authored the thread.Message ID: @.>

Here https://github.com/ahkohd/eza-preview.yazi/tree/feature-level-symlinks

I get error 1 when pressing $.
Also I notice another issue.
Let's say I have a tree with 2 levels. If I expand both and then expand again thinking there might be another level of course the display does not change. But if I then decrease the level nothing happens either since it seem the plugin thinks I'm one level down. I need to hit decrease a second time to decrease the level on the screen. I hope I'm explaining this clearly. To see what I'm talking about increase the level a bunch of times on a directory past where it actually shows on the screen. Then decrease.
On Thu, Nov 21, 2024, at 11:17, Victor Aremu wrote:

Can you send me a link please.
… <#>
On Thu, Nov 21, 2024, at 08:32, Victor Aremu wrote: > > Sorry. I misunderstood how this works. Now I understand and it's great! > … <#> > On Thu, Nov 21, 2024, at 07:39, Victor Aremu wrote: > > It works for me! are you sure you are using the feature-level or feature-level-symlinks branch? > maybe pull changes, your local may be outdated > — Reply to this email directly, view it on GitHub <#8 https://github.com/sharklasers996/eza-preview.yazi/issues/8 (comment) <#8 (comment) https://github.com/sharklasers996/eza-preview.yazi/issues/8#issuecomment-2491570921>>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALLYYROO2UVZDK3QL5LB5VD2BX5DVAVCNFSM6AAAAABRSGBNEOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJRGU3TAOJSGE. You are receiving this because you authored the thread.Message ID: @.> > Cool. Perhaps try out the feature-level-symlinks branch, which has the option to follow symlinks and deference! — Reply to this email directly, view it on GitHub <#8 (comment) https://github.com/sharklasers996/eza-preview.yazi/issues/8#issuecomment-2491716486>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALLYYRPFENQ55DWDNYOUBW32BYDKZAVCNFSM6AAAAABRSGBNEOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJRG4YTMNBYGY. You are receiving this because you authored the thread.Message ID: @.>

Here https://github.com/ahkohd/eza-preview.yazi/tree/feature-level-symlinks
—
Reply to this email directly, view it on GitHub https://github.com/sharklasers996/eza-preview.yazi/issues/8#issuecomment-2492064904, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALLYYRIB7JPMK4J35AESXP32BYWTXAVCNFSM6AAAAABRSGBNEOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJSGA3DIOJQGQ.
You are receiving this because you authored the thread.Message ID: @.***>

Let's say I have a tree with 2 levels. If I expand both and then expand again thinking there might be another level of course the display does not change. But if I then decrease the level nothing happens either since it seem the plugin thinks I'm one level down. I need to hit decrease a second time to decrease the level on the screen. I hope I'm explaining this clearly. To see what I'm talking about increase the level a bunch of times on a directory past where it actually shows on the screen. Then decrease.

Can you share a screenshot of the error you're encountering? I'm not experiencing issues using $ to toggle follow symlinks.
Regarding the level issue, it's not a big deal. Ideally, we want to avoid incrementing when we reach a directory's maximum depth. However, this requires us to traverse the directory recursively in advance to determine its depth and prevent going beyond it. It's not worth solving this (that is more computation; this is what we are trying to avoid by setting a level); over-incrementing is not a problem. One possible solution is to display a level counter in the top right corner so you're informed, but I don't like that idea. I want to see my tree!

Understood about the decrease/increase of depth. I guess not worth doing. As for a screenshot, for some reason the screen capture on my Chromebook does not capture the box. It's a red box in the upper right-hand corner of the yazi pane. The box border has "Eza-preview" and inside the box there is a 1.
…
On Thu, Nov 21, 2024, at 11:17, Victor Aremu wrote: > > Can you send me a link please. > … <#> > On Thu, Nov 21, 2024, at 08:32, Victor Aremu wrote: > > Sorry. I misunderstood how this works. Now I understand and it's great! > … <#> > On Thu, Nov 21, 2024, at 07:39, Victor Aremu wrote: > > It works for me! are you sure you are using the feature-level or feature-level-symlinks branch? > maybe pull changes, your local may be outdated > — Reply to this email directly, view it on GitHub <#8 <#8> (comment) <#8 (comment) <#8 (comment)>>>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALLYYROO2UVZDK3QL5LB5VD2BX5DVAVCNFSM6AAAAABRSGBNEOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJRGU3TAOJSGE. You are receiving this because you authored the thread.Message ID: @.> > Cool. Perhaps try out the feature-level-symlinks branch, which has the option to follow symlinks and deference! — Reply to this email directly, view it on GitHub <#8 (comment) <#8 (comment)>>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALLYYRPFENQ55DWDNYOUBW32BYDKZAVCNFSM6AAAAABRSGBNEOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJRG4YTMNBYGY. You are receiving this because you authored the thread.Message ID: @.> > Here https://github.com/ahkohd/eza-preview.yazi/tree/feature-level-symlinks — Reply to this email directly, view it on GitHub <#8 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALLYYRIB7JPMK4J35AESXP32BYWTXAVCNFSM6AAAAABRSGBNEOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJSGA3DIOJQGQ. You are receiving this because you authored the thread.Message ID: @.***>

Can you share your Yazi log? It's in your home dir, .local/state/yazi/yazi.log

yazi.log

yazi.log

Thank you.
I have observed the error logs and noticed two distinct errors recorded related to the plugin:

  2024-10-20T13:22:42.444355Z ERROR yazi_plugin::isolate::peek: CallbackError { traceback: "stack traceback:\n\t[C]: in field 'parse'\n\t[string \"eza-preview\"]:89: in function <[string \"eza-preview\"]:28>", cause: BadArgument { to: None, pos: 1, name: None, cause: FromLuaConversionError { from: "userdata", to: "string", message: Some("expected string or number") } } }

  2024-11-21T15:00:55.521773Z ERROR yazi_plugin::isolate::peek: runtime error: [string "eza-preview"]:68: attempt to index a nil value
stack traceback:
	[string "eza-preview"]:68: in function <[string "eza-preview"]:67>
    at yazi-plugin/src/isolate/peek.rs:65

However, the line numbers do not match what I have here: https://github.com/ahkohd/eza-preview.yazi/blob/feature-level-symlinks/init.lua
Can you confirm whether you've been using the latest updates from that branch? Please either pull the updates or verify that the newest commit is current. If you haven't pulled the updates, please do so. You can also delete this log on your computer to create a fresh log for gathering information the next time you encounter that issue.

I found the issue.. I was using eza 0.18. The --follow-symlinks option was not available in that version. Only in version 0.20. I installed that version and now all is working well.

cool l better update the docs as well, thanks!

I found the issue.. I was using eza 0.18. The --follow-symlinks option was not available in that version. Only in version 0.20. I installed that version and now all is working well.

cool l better update the docs as well, thanks!

I found the issue.. I was using eza 0.18. The --follow-symlinks option was not available in that version. Only in version 0.20. I installed that version and now all is working well.

updated the PR #13

version 0.20 is quite new. Sorry for the bother.
On Thu, Nov 21, 2024, at 15:41, Victor Aremu wrote:

cool l better update the docs as well, thanks!

I found the issue.. I was using eza 0.18. The --follow-symlinks option was not available in that version. Only in version 0.20. I installed that version and now all is working well.

updated the PR #13 https://github.com/sharklasers996/eza-preview.yazi/pull/13
—
Reply to this email directly, view it on GitHub https://github.com/sharklasers996/eza-preview.yazi/issues/8#issuecomment-2492574453, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALLYYRNZG6CHNU5TWHXOD4L2BZVSNAVCNFSM6AAAAABRSGBNEOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJSGU3TINBVGM.
You are receiving this because you authored the thread.Message ID: @.***>

version 0.20 is quite new. Sorry for the bother.
…
On Thu, Nov 21, 2024, at 15:41, Victor Aremu wrote: > cool l better update the docs as well, thanks! > >> I found the issue.. I was using eza 0.18. The --follow-symlinks option was not available in that version. Only in version 0.20. I installed that version and now all is working well. >> updated the PR #13 <#13> — Reply to this email directly, view it on GitHub <#8 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALLYYRNZG6CHNU5TWHXOD4L2BZVSNAVCNFSM6AAAAABRSGBNEOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJSGU3TINBVGM. You are receiving this because you authored the thread.Message ID: @.***>

I'm on v0.20.8 running nixos-unstable-small channel

I'm on v0.20.7 [+git] on Linux Mint on my desktop and Debian 12 on my Chromebook.
On Thu, Nov 21, 2024, at 15:59, Victor Aremu wrote:

version 0.20 is quite new. Sorry for the bother.
… <#>
On Thu, Nov 21, 2024, at 15:41, Victor Aremu wrote: > cool l better update the docs as well, thanks! > >> I found the issue.. I was using eza 0.18. The --follow-symlinks option was not available in that version. Only in version 0.20. I installed that version and now all is working well. >> updated the PR #13 https://github.com/sharklasers996/eza-preview.yazi/pull/13 <#13 https://github.com/sharklasers996/eza-preview.yazi/pull/13> — Reply to this email directly, view it on GitHub <#8 (comment) https://github.com/sharklasers996/eza-preview.yazi/issues/8#issuecomment-2492574453>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALLYYRNZG6CHNU5TWHXOD4L2BZVSNAVCNFSM6AAAAABRSGBNEOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJSGU3TINBVGM. You are receiving this because you authored the thread.Message ID: @.***>

I'm on v0.20.8 running nixos-unstable-small channel
—
Reply to this email directly, view it on GitHub https://github.com/sharklasers996/eza-preview.yazi/issues/8#issuecomment-2492593310, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALLYYRNG5DUW67CNET2TXMT2BZXULAVCNFSM6AAAAABRSGBNEOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJSGU4TGMZRGA.
You are receiving this because you authored the thread.Message ID: @.***>

More API changes and I get this with the latest nightly:

The message stays for awhile, then disappears and the plugin works.

More API changes and I get this with the latest nightly:

The message stays for awhile, then disappears and the plugin works.

I'll look into it.

I played around a bit and I think this fixes it... a diff between the old init.lu and one that does not generate an error:
-function M:entry(args)

local arg = args[1]
+function M:entry(jobs)

local arg = jobs.args[1]

On Sun, Dec 1, 2024, at 09:49, Victor Aremu wrote:

More API changes and I get this with the latest nightly:
image.png (view on web) https://github.com/user-attachments/assets/4e4e10b1-fa95-49bf-bc08-4f8e5870ec98
The message stays for awhile, then disappears and the plugin works.

I'll look into it.
—
Reply to this email directly, view it on GitHub https://github.com/sharklasers996/eza-preview.yazi/issues/8#issuecomment-2510147590, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALLYYRJSH2FZYHVBSI7IL4D2DND3BAVCNFSM6AAAAABRSGBNEOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMJQGE2DONJZGA.
You are receiving this because you authored the thread.Message ID: @.***>

Thanks. Great plugin. Can't live without it!

Thanks. Great plugin. Can't live without it!

same!

Nope. I thought it did, but not.

Looks like all the keymaps don't work. Must need the new API changes.

Looks like all the keymaps don't work. Must need the new API changes.

okay, I will start working on it.

Do I just merge to main or wait a little?

I have Yazi 0.3.3 (37292ad 2024-11-28) and it does not work with that since it's before the API changes. The API changes are in preparation for version 0.4. So I would not merge it with the master.
On Sun, Dec 1, 2024, at 14:38, Victor Aremu wrote:

Do I just merge to main or wait a little?
—
Reply to this email directly, view it on GitHub https://github.com/sharklasers996/eza-preview.yazi/issues/8#issuecomment-2510283264, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALLYYRKQKNDDY77WPFMEN5D2DOFWNAVCNFSM6AAAAABRSGBNEOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMJQGI4DGMRWGQ.
You are receiving this because you authored the thread.Message ID: @.***>

okay then, I will keep the nightly branch! Where all future breaking changes will be fixed.

Thanks for the quick work on this.
On Sun, Dec 1, 2024, at 15:20, Victor Aremu wrote:

okay then, I will keep the nightly branch! Where all future breaking changes will be fixed.
—
Reply to this email directly, view it on GitHub https://github.com/sharklasers996/eza-preview.yazi/issues/8#issuecomment-2510298502, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALLYYRNXYZU734JH4L2FSTL2DOKSVAVCNFSM6AAAAABRSGBNEOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMJQGI4TQNJQGI.
You are receiving this because you authored the thread.Message ID: @.***>

Just noticed it does not display for symlinks as before and keymaps still don't work.
On Sun, Dec 1, 2024, at 15:23, Bert wrote:

Thanks for the quick work on this.
On Sun, Dec 1, 2024, at 15:20, Victor Aremu wrote:

okay then, I will keep the nightly branch! Where all future breaking changes will be fixed.
—
Reply to this email directly, view it on GitHub https://github.com/sharklasers996/eza-preview.yazi/issues/8#issuecomment-2510298502, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALLYYRNXYZU734JH4L2FSTL2DOKSVAVCNFSM6AAAAABRSGBNEOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMJQGI4TQNJQGI.
You are receiving this because you authored the thread.Message ID: @.***>

Just noticed it does not display for symlinks as before and keymaps still don't work.
…
On Sun, Dec 1, 2024, at 15:23, Bert wrote: Thanks for the quick work on this. On Sun, Dec 1, 2024, at 15:20, Victor Aremu wrote: > > > okay then, I will keep the nightly branch! Where all future breaking changes will be fixed. > > > > — > Reply to this email directly, view it on GitHub <#8 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALLYYRNXYZU734JH4L2FSTL2DOKSVAVCNFSM6AAAAABRSGBNEOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMJQGI4TQNJQGI. > You are receiving this because you authored the thread.Message ID: @.***> > >

did you update your keymaps.toml?

Missed that. Updated and it works, but E does  not toggle eza-preview. Is there a change there too?

Missed that. Updated and it works, but E does not toggle eza-preview. Is there a change there too?

oh! I did no test that, let me check it!

Also, how can I have eza-preview start with symlinks enabled?

Also, how can I have eza-preview start with symlinks enabled?

configure it.

In my init.lua in my yazi directory I have:
require("eza-preview"):setup({
level = 2, -- default level: 3
})

Missed that. Updated and it works, but E does not toggle eza-preview. Is there a change there too?

This is now fixed, pull new changes.

In my init.lua in my yazi directory I have:
require("eza-preview"):setup({ level = 2, -- default level: 3 })

Perfect. Thanks.
On Sun, Dec 1, 2024, at 16:11, Victor Aremu wrote:

In my init.lua in my yazi directory I have:
require("eza-preview"):setup({ level = 2, -- default level: 3 })

image.png (view on web) https://github.com/user-attachments/assets/98e3ee43-cca4-45eb-8a04-f858f71cd53d
—
Reply to this email directly, view it on GitHub https://github.com/sharklasers996/eza-preview.yazi/issues/8#issuecomment-2510321722, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALLYYRPNZ252PP2BBMVZ6ZL2DOQTRAVCNFSM6AAAAABRSGBNEOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMJQGMZDCNZSGI.
You are receiving this because you authored the thread.Message ID: @.***>


report any WT phenotypes with no "knockdown" or "overexpression" in logs

https://github.com/pombase/curation/issues/851

"knockdown" or "overexpression"

We have 613 genotypes with an allele with the expression recorded as "Not assayed or wild type".
And 6 as "Ectopic".
How do they fit in?

Note to self, query for allele and expression where the expression level isn't "Overexpression" OR "Knockdown".
And 6 as "Ectopic".

With WT alleles?

With WT alleles?

Yep, I queried for WT alleles only.  Sorry I wasn't clear.

OK, it's know of weird that we have so many because we don't curate WT unless the expression is changed?
Can you give us the list?

OK, it's kind of weird that we have so many because we don't curate WT unless the expression is changed?

Most (maybe all, I haven't checked) are from multi-allele or multi-locus genotypes:

https://www.pombase.org/genotype/tor2%2B(wild_type)-expression-not_assayed_or_wild_type_tor2delta
https://www.pombase.org/genotype/tor2%2B(wild_type)-expression-not_assayed_or_wild_type__tor2-HTHdelta-710-734-partial_amino_acid_deletion-expression-not_assayed_or_wild_type

OK I think most of these are heterozygous diplouits where one WT copy is retained. In  all of these cases we can assume WT expression  for the WT alleles.
If we take these away how many are left?

If we take these away how many are left?

After removing the diploids there are 80 WT alleles that are "Not assayed or wild type".  From a quick look most of them look like they are part of multi locus genotypes:

https://www.pombase.org/genotype/slp1%2B(wild_type)-expression-not_assayed_or_wild_type__slp1-mr63-A131P,F132T-amino_acid_mutation-expression-not_assayed_or_wild_type
https://www.pombase.org/genotype/rtf1%2B(wild_type)-expression-not_assayed_or_wild_type__rtf1-R346*-R346*-partial_amino_acid_deletion-expression-not_assayed_or_wild_type

And there are 11 alleles that are "Not assayed or wild type" in a single allele haploid genotype.  These links will work today only.   These links will work today only. I'm happy to update the table later if needed.
name	uniquename
SPAC1B9.03c+	https://www.pombase.org/allele/SPAC1B9.03c:allele-2
SPBC609.01+	https://www.pombase.org/allele/SPBC609.01:allele-2
brf1+	https://www.pombase.org/allele/SPBC13E7.10c:allele-2
cdc18+	https://www.pombase.org/allele/SPBC14C8.07c:allele-17
cnd1+	https://www.pombase.org/allele/SPBC776.13:allele-14
hht1+	https://www.pombase.org/allele/SPAC1834.04:allele-2
mug65+	https://www.pombase.org/allele/SPAC1296.04:allele-2
peg1+	https://www.pombase.org/allele/SPAC3G9.12:allele-2
pmo25+	https://www.pombase.org/allele/SPAC1834.06c:allele-4
pob1+	https://www.pombase.org/allele/SPBC1289.04c:allele-3
teb1+	https://www.pombase.org/allele/SPAC13G7.10:allele-2

Most of these come from the same publication https://www.pombase.org/reference/PMID:29735745
And a couple are used in rescue experiments, in diploid genotypes with a deletion of the same gene, like https://www.pombase.org/genotype/brf1%2B(wild_type)-expression-not_assayed_or_wild_type_brf1delta

The ones that come from this paper https://www.pombase.org/reference/PMID:29735745 are actually promoter swapped WT alleles for which the expression level is either the same as with the endogenous promoter or not assayed.

Maybe we can just dleete the ones that are not diploids. Do they capture anything useful?

Looks like these alleles have no useful annotations.
https://www.pombase.org/genotype/SPAC1B9.03c%2B(wild_type)-expression-not_assayed_or_wild_type
https://www.pombase.org/genotype/SPBC609.01%2B(wild_type)-expression-not_assayed_or_wild_type
https://www.pombase.org/genotype/brf1%2B(wild_type)-expression-not_assayed_or_wild_type
https://www.pombase.org/genotype/cnd1%2B(wild_type)-expression-not_assayed_or_wild_type
https://www.pombase.org/genotype/peg1%2B(wild_type)-expression-not_assayed_or_wild_type
https://www.pombase.org/genotype/pmo25%2B(wild_type)-expression-not_assayed_or_wild_type
https://www.pombase.org/genotype/pob1%2B(wild_type)-expression-not_assayed_or_wild_type
https://www.pombase.org/genotype/teb1%2B(wild_type)-expression-not_assayed_or_wild_type
I have to look at these papers/sessions for the other haploid alleles.
https://www.pombase.org/reference/PMID:9303312
https://www.pombase.org/reference/PMID:32152323
https://www.pombase.org/reference/PMID:36095128

For this allele https://www.pombase.org/genotype/cdc18%2B(wild_type)-expression-not_assayed_or_wild_type, I fixed some annotations relating to the level of WT RNA of cdc18.
The last annotation to this genotype describes an effect of HU treatment on MBF complex assembly in WT cells.

The last annotation to this genotype describes an effect of HU treatment on MBF complex assembly in WT cells.

Yeah that can go...

This one https://www.pombase.org/genotype/hht1%2B(wild_type)-expression-not_assayed_or_wild_type captures a phenotype of having hht1 expressed by the hht2 promoter, with the effect on expression not assayed

And this one https://www.pombase.org/genotype/mug65%2B(wild_type)-expression-not_assayed_or_wild_type captures the retention of an intron of mug65 in WT cells at high temperature

And this one https://www.pombase.org/genotype/mug65%2B(wild_type)-expression-not_assayed_or_wild_type captures the retention of an intron of mug65 in WT cells at high temperature
deleted!

Updated table from latest Chado, with working links:

name
uniquename

SPAC1B9.03c+
https://www.pombase.org/allele/SPAC1B9.03c:allele-2

SPBC609.01+
https://www.pombase.org/allele/SPBC609.01:allele-2

brf1+
https://www.pombase.org/allele/SPBC13E7.10c:allele-2

cnd1+
https://www.pombase.org/allele/SPBC776.13:allele-3

hht1+
https://www.pombase.org/allele/SPAC1834.04:allele-8

peg1+
https://www.pombase.org/allele/SPAC3G9.12:allele-2

pmo25+
https://www.pombase.org/allele/SPAC1834.06c:allele-3

pob1+
https://www.pombase.org/allele/SPBC1289.04c:allele-2

teb1+
https://www.pombase.org/allele/SPAC13G7.10:allele-2

Updated table from latest Chado, with working links:
name	uniquename
SPAC1B9.03c+	https://www.pombase.org/allele/SPAC1B9.03c:allele-2
SPBC609.01+	https://www.pombase.org/allele/SPBC609.01:allele-2
brf1+	https://www.pombase.org/allele/SPBC13E7.10c:allele-2
cnd1+	https://www.pombase.org/allele/SPBC776.13:allele-3
hht1+	https://www.pombase.org/allele/SPAC1834.04:allele-8
peg1+	https://www.pombase.org/allele/SPAC3G9.12:allele-2
pmo25+	https://www.pombase.org/allele/SPAC1834.06c:allele-3
pob1+	https://www.pombase.org/allele/SPBC1289.04c:allele-2
teb1+	https://www.pombase.org/allele/SPAC13G7.10:allele-2

I think the hht1 allele is the only one of these that captures a real phenotype. The ones from this publication https://www.pombase.org/reference/PMID:29735745 all seem pretty useless to me.

Updated table from latest Chado, with working links:

I've add a new log file for this.  Look for a file ending in .chado_checks.single_wt_allele_with_wild_type_expression:
https://curation.pombase.org/dumps/builds/pombase-build-2024-07-25/logs/log.2024-07-24-18-51-33.chado_checks.single_wt_allele_with_wild_type_expression

OK, remove those from https://www.pombase.org/reference/PMID:29735745
does hht1 have different expression?

OK, remove those from https://www.pombase.org/reference/PMID:29735745

That's done now. I only left the cnd1 promoter swap allele in the session as I just realised that it is used in a genetic interaction with another mutation.

does hht1 have different expression?

The promoter swapping affects the dynamics of Hht1 expression during germination.

@PCarme  can close yes?

Yes, this can be closed


Improve documentation

Add more publicly documented classes, parameters, demos, example snippets.
Classes to document:

Evaluator.debug & OperationDebugData
Evaluator.evaluateHierarchy
Operation & OperationGroup
GridMaterial
PointsHelper, HalfEdgeHelper, EdgesHelper, TriangleSetsHelper

Hi @gkjohnson, do you want to create a documentation like the three-mesh-bvh README.md file?

Yeah that would be perfect - the docs that are there should already be structured a bit similarly in this project, too. Hopefully the documentation structure is self-explanatory but if feel free to ask questions!

Ok I try, let's see what I can do 😊


query did not execute

Hello,
I was trying to implement this on my project but the query was not execute and i get all result for related resource.
trait ClienteWithMyPostTrait
{
public static function myPostQuery(NovaRequest $request, $query, $model)
{
return $query->where('id', 1);
}
This part never run, i implemented like
CustomRelationshipField::make('My post', 'myPost', Post::class)
Thanks.

did you include the trait:
use CustomRelationshipFieldTrait;

?

Hello,
Thanks for your reply,
Yes, i dit it.
use App\Traits\ClienteWithMyPostTrait;
use DigitalCreative\CustomRelationshipField\CustomRelationshipField;
class Cliente extends Resource
{
use HasTabs, HasActionsInTabs;
use CustomRelationshipFieldTrait;
use ClienteWithMyPostTrait;
/**
 * The model the resource corresponds to.
 *
 * @var string
 */
public static $model = \App\Models\Cliente::class;

+1

any update on this?


add method to check if stream can hold more data

[ ] Need to figure out how to test.

Regarding the DATA case, I think in the future we could change send_body() to not check the capacity and not slice the input buffer at all (so the frame header's length field will just be the full input buffer length), and then simply expect the application to do the right thing and write the remaining bytes once the stream becomes writable (applications should be doing this already anyway to avoid dropping data, but they don't have to do it), this way the capacity check would fall to the transport layer. The send_headers() case would still require "atomic" writes though.
Another idea would be to have a stream_send_atomic() method that either writes all data, or none of it, but that would require copying h3 headers/data into a single buffer, unless this is implemented in multiple steps ("start atomic send" -> "write data" -> "write data" -> ... -> "end atomic send"), but that API would be much more complicated than what this PR does.

I think this PR is a good compromise for how the h3 layer operates today - later changes will need some rethinks. For instance, send_headers() already (without this) is going to have problems when we come around to needing to emit QPACK encoder stream instructions too.


Add timeutil files and some metrics

Adding util files for time functions and some metrics.

You may add rocksplicator as the reviewer for future PRs.


Add base for upstream subcommand

Missing features

[ ] if gcc-patch-dev isn't checked out already, the program fails - make sure to fetch the reference first or find it differently
[ ] Needs a lot of cleaning up

The subcommand can now properly push the branch it creates and create a pull-request from it.
We also need to think of the following:

[ ] Improve the PR's message
[ ] Figure out a nice way to report the commits which should not be upstreamed due to staging

For some reason the created PRs have the wrong amount of commits - despite gerris only cherry-picking ~180 commits for https://github.com/CohenArthur/gccrs/pull/15, github shows a ~3600 commits big PR, and git rev-list prepare-2023-04-07-1680856144480195..gcc-patch-dev | wc -l shows ~840 commits. Not sure what's going on and will investigate

I think it might be easier to just do the git part in a separate shell script... this is incredibly annoying


.DS_Store file in 4.1.3 dist zip file at getbootstrap.com

Operating system and version: MacOS 10.13.6

Browser and version: Firefox 63.0.1

[Reduced test case]

Download https://github.com/twbs/bootstrap/releases/download/v4.1.3/bootstrap-4.1.3-dist.zip
Unzip bootstrap-4.1.3-dist.zip

Issue: .DS_Store file made its way into the dist zip file

Archive:  bootstrap-4.1.3-dist.zip
   creating: css/
  inflating: css/bootstrap.min.css
  inflating: css/.DS_Store
  ....

Already fixed in v4-dev.

Same in yarnpkg:
<EMAIL_ADDRESS>dist/.DS_Store
dist/css/.DS_Store

Like I said it's already fixed in v4-dev.
https://github.com/twbs/bootstrap/pull/27013


Add host-local-values

Port the host-local-value feature from SkyDNS. Querying for
local.dns. returns data that is specific for this CoreDNS
instance.

Hmm, code is getting hideous, not sure I want this....


removeChild

I noticed that old nodes cannot be removed, looking at source that appears right 😄
The source I am running is here: https://github.com/virtualstate/x/blob/main/packages/deno/src/example.ts
[~/src/virtualstate/x]$ deno run --import-map=packages/deno/import-map-local.json --allow-net packages/deno/lib/example.js

Hello Async World!
{
  "id": 1,
  "name": "Leanne Graham",
  "username": "Bret",
  "email"<EMAIL_ADDRESS>  "address": {
    "street": "Kulas Light",
    "suite": "Apt. 556",
    "city": "Gwenborough",
    "zipcode": "92998-3874",
    "geo": {
      "lat": "-37.3159",
      "lng": "81.1496"
    }
  },
  "phone": "1-770-736-8031 x56442",
  "website": "hildegard.org",
  "company": {
    "name": "Romaguera-Crona",
    "catchPhrase": "Multi-layered client-server neural-net",
    "bs": "harness real-time e-markets"
  }
}

Loading

[~/src/virtualstate/x]$ node -r isomorphic-fetch packages/deno/lib/jsdom.js
true

Hello Async World!
{
  "id": 1,
  "name": "Leanne Graham",
  "username": "Bret",
  "email"<EMAIL_ADDRESS>  "address": {
    "street": "Kulas Light",
    "suite": "Apt. 556",
    "city": "Gwenborough",
    "zipcode": "92998-3874",
    "geo": {
      "lat": "-37.3159",
      "lng": "81.1496"
    }
  },
  "phone": "1-770-736-8031 x56442",
  "website": "hildegard.org",
  "company": {
    "name": "Romaguera-Crona",
    "catchPhrase": "Multi-layered client-server neural-net",
    "bs": "harness real-time e-markets"
  }
}

Is there some work around I can do for this? For example can I just clear all the nodes children at once and rebuild them each time?

I noticed that old nodes cannot be removed, looking at source that appears right smile
@fabiancook you can already remove children with child.remove(), but yeah I'll implement this too

And with this, deno renders as expected.


How can I set the "javascript.suggestionActions.enabled" option?

I am trying to disable one annoying feature in typescript-language-server, but the only instructions I can find are for VSCode and coc.vim. I tried adding this option like this:
lspconfig.typescript.setup {
  on_attach = function(client, bufnr)
  -- ...
  end,
  settings = {
    javascript = {
      suggestionActions = {
        enabled = false,
      },
    },
    typescript = {
      suggestionActions = {
        enabled = false,
      },
    },
  },
}

…which didn't change anything. Am I doing something wrong?

coc uses a wrapper around tsserver, we have to use theia, which doesn't expose this option (see https://github.com/theia-ide/typescript-language-server/issues/166#issuecomment-728827433)


scotch-no-pthread: rebuild bottles

Same as #66, pr-pull failure seems to be https://github.com/Homebrew/brew/issues/15049.


docs: update GetCurrentDataCommitment comment

Overview
Closes https://github.com/celestiaorg/celestia-app/issues/1710

The CI is still not starting. I'll keep investigating

Closed and reopened to see if that would re-trigger the CI

Codecov Report

Merging #1712 (2811564) into main (5a7a9d6) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1712   +/-   ##
=======================================
  Coverage   52.02%   52.02%
=======================================
  Files          93       93
  Lines        6053     6053
=======================================
  Hits         3149     3149
  Misses       2580     2580
  Partials      324      324

Impacted Files
Coverage Δ

x/qgb/keeper/keeper_data_commitment.go
53.16% <ø> (ø)


[BUG]: Does not locate models on local ollama

How are you running AnythingLLM?
AnythingLLM desktop app
What happened?

I can use ollama locally using wsl
I can access it using the URL
Yet, Anything will not present model options
Are there known steps to reproduce?
No response

<IP_ADDRESS>
You have <IP_ADDRESS> typed in

Thanks for finding that error in my report.
I took that pic as I was trying to work around.
Here is the one with <IP_ADDRESS>
(I also tried localhost, the host IP, and several other things)

How do I reopen this?

Note:
I turned off firewall as well as allowed all access for the app


Remove json tag in NetworkConnect.EndpointConfig

Not necessary and docker follows camel case convention for json variables

Signed-off-by: Alessandro Boch<EMAIL_ADDRESS>

LGTM


Cache directory is not writable

Thanks for this extension.
I get this error:
Cannot put TLD list to cache file /xxxxx/vendor/layershifter/tld-extract/src/../cache/.tld_set, check writes rights on directory of file
So, I should change permission cache directory in vendor that this is not good job.
I suggest modify code for check permission and writable with is_writable() and if don't have permission, try to change with chmod(). or more better solution is auto created cache directory with mkdir('cache', 0777); command.

Hi, @NabiKAZ
You use setCacheFile method before parse. For example:
Extract::setCacheFile('/path/to/your/dir/cache.file');
Extract::setCacheFile(__DIR__ . '/cache/tld.file');
Is it a solution for your problem?

It's not bad, but I thinks, About a code, all thing must be works well in default. So better is for improve code, check this issue in the code.

Yes, It's reasonable 	proposal. I'll think about it.

Hi, @NabiKAZ
Part of package that works with database was separated to TLDDatabase package. It's use background update, so it removes much headache :smile:
TLDDatabase will be used in 1.0 version.


About Download Datasets and Pre-trained Models

Could you please provide  Datasets and Pre-trained Models in google drive? I download them very slowly through wget，and usually cause download failure due to interruption.
Thanks!

I meet the same question. Could you tell me how do you solve it?


docs: add documentation for component states

Preflight Checklist

[x] I have read the Contributing Guidelines for this project.
[x] I agree to follow the Code of Conduct that this project adheres to.
[x] I have searched the pull request tracker for a Pull Request (PR) that matches the one I want to submit, without success.

Issue
This PR Closes #
Pull request checklist
Please check if your PR fulfills the following requirements:

[ ] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been reviewed and added / updated if needed (for bug fixes / features)
[ ] Build (npm run build) was run locally and any changes were pushed
[ ] Lint (npm run lint) has passed locally and any fixes were made for failures

Changes
Changes in this pull request:
Add documentation for component states
Browsers
I tested the build on the following browsers:

[ ] Firefox Desktop
[ ] Chrome Desktop
[ ] Safari Desktop
[ ] Firefox Mobile
[ ] Chrome Mobile
[ ] Safari Mobile
[ ] Opera
[ ] Brave

Pull request type

Please check the type of change your PR introduces:

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[x] Documentation content changes
[ ] Other (please describe):

Does this introduce a breaking change?

[ ] Yes
[x] No

Other information

Mentions

@lyne-design-system/core

Codecov Report

Merging #1112 (29dc5bc) into master (00a8ef9) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 29dc5bc differs from pull request most recent head 1b28d57. Consider uploading reports for the commit 1b28d57 to get more accurate results

@@           Coverage Diff           @@
##           master    #1112   +/-   ##
=======================================
  Coverage   60.45%   60.45%
=======================================
  Files          46       46
  Lines        1502     1502
  Branches      401      401
=======================================
  Hits          908      908
  Misses        533      533
  Partials       61       61

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


Recognize hostnames in xenrt.log and improve CI test

For xenrt.log, improve the pattern to detect hostnames as well.
While we are at it, improve the logic of test.sh to cope with newer lnav.

Thanks!


Fix typo

IPSec -> IPsec

@msmbaldwin
Can you review the proposed changes?
IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team


Missing details about HA on SQL Hyperscale

The article is missing details of high availability on Azure SQL DB Hyperscale tier.

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

ID: 15036ef6-9c0b-044e-d600-b9f90f039720
Version Independent ID: 6fe5cd14-a1ad-e183-a048-d72686abb969
Content: High availability - Azure SQL Database service
Content Source: articles/sql-database/sql-database-high-availability.md
Service: sql-database
Sub-service: high-availability
GitHub Login: @jovanpop-msft
Microsoft Alias: sashan

@juho-hanhimaki Thank you for the feedback.
We are reviewing the content and will get back to you shortly.

@juho-hanhimaki This issue is being assigned to the content author to evaluate and update as appropriate.

any status update on HA for Hyperscale tier?

@vlad-kozlov Is there something specific you are looking for in the documentation pertaining to High Availability? Much of the Hyperscale service is resilient but the document you have filed this issue under does not include any details. The Hyperscale FAQ document does have an entry that touches upon this subject: For high availability, do I need to provision additional compute nodes

In Hyperscale databases, the resiliency is provided at the storage level. You only need one replica to provide resiliency. When the compute replica is down, a new replica is created automatically with no data loss.

However, if there’s only one replica, it may take some time to build the local cache in the new replica after failover. During the cache rebuild phase, the database fetches data directly from the page servers, resulting in degraded IOPS and query performance.

For mission-critical apps that require high availability, you should provision at least 2 compute nodes including the primary compute node (default). That way there is a hot-standby available in the case of a failover.

Please provide some clarification as to what is desired or what information is missing. Thank you!

@stevestein For awareness.

@Mike-Ubezzi-MSFT @stevestein
I agree that these information should be here, but currently all hyper scale related info are placed on a single page HS HA is here: https://docs.microsoft.com/en-us/azure/sql-database/sql-database-service-tier-hyperscale#database-high-availability-in-hyperscale
Maybe you should contact @denzilribeiro to check what is the plan with moving info from that page to other parts of documentation.

Dimitri who is working on the backup stuff too.

From: Jovan Popovic (MSFT<EMAIL_ADDRESS>Sent: Friday, October 11, 2019 9:56 AM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: Denzil Ribeiro<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] Missing details about HA on SQL Hyperscale (#32251)
@Mike-Ubezzi-MSFThttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMike-Ubezzi-MSFT&data=02|01|denzilr%40microsoft.com|0e03e03e700a4a2d833308d74e5b1fe2|72f988bf86f141af91ab2d7cd011db47|1|0|637064025598854729&sdata=0EBHLuGdHCrl0kRladMOfHBhZkL9rsB%2BYDJbwFYXmY4%3D&reserved=0 @stevesteinhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fstevestein&data=02|01|denzilr%40microsoft.com|0e03e03e700a4a2d833308d74e5b1fe2|72f988bf86f141af91ab2d7cd011db47|1|0|637064025598864737&sdata=yVcCZx5wR%2FLlOax%2BmZYBABIGauAcX311pOZTI0FMHsw%3D&reserved=0
I agree that these information should be here, but currently all hyper scale related info are placed on a single page HS HA is here: https://docs.microsoft.com/en-us/azure/sql-database/sql-database-service-tier-hyperscale#database-high-availability-in-hyperscalehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fsql-database%2Fsql-database-service-tier-hyperscale%23database-high-availability-in-hyperscale&data=02|01|denzilr%40microsoft.com|0e03e03e700a4a2d833308d74e5b1fe2|72f988bf86f141af91ab2d7cd011db47|1|0|637064025598864737&sdata=hdvK%2BtzVBWjGO%2BHQvozyvVnVjg3%2ByWGSJMB4vDFBmkw%3D&reserved=0
Maybe you should contact @denzilribeirohttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdenzilribeiro&data=02|01|denzilr%40microsoft.com|0e03e03e700a4a2d833308d74e5b1fe2|72f988bf86f141af91ab2d7cd011db47|1|0|637064025598874744&sdata=NEnfQCPpozzNJvA%2FKuoswxyEdHsDa2gr%2F26Q%2BJ2z4fM%3D&reserved=0 to check what is the plan with moving info from that page to other parts of documentation.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F32251%3Femail_source%3Dnotifications%26email_token%3DAC72ZVCLA4DG6ZCVNCDNP3TQOCHXZA5CNFSM4HQCOLX2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBAIEQA%23issuecomment-541098560&data=02|01|denzilr%40microsoft.com|0e03e03e700a4a2d833308d74e5b1fe2|72f988bf86f141af91ab2d7cd011db47|1|0|637064025598874744&sdata=AlQ37ukC4Qw8%2FNoc8FHk60KTiTGXPd7FT7IFHvVxFWw%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAC72ZVAUOWE7HCBB4PPATWLQOCHXZANCNFSM4HQCOLXQ&data=02|01|denzilr%40microsoft.com|0e03e03e700a4a2d833308d74e5b1fe2|72f988bf86f141af91ab2d7cd011db47|1|0|637064025598874744&sdata=RImwkymhumt6ytRHRIQC9i%2BiDccfkCQGcxgt1Rau2fg%3D&reserved=0.

#please-close


Control the width?

Is there a way to control the width of the box? I want a sleeker looking box.
Thanks.

Ach. Nevermind, I just realized its probably like a bar chart - and it is. Thanks for the great library BTW.

yes, internally it is based on the Bar Controller from Chart.js.
see
https://github.com/chartjs/Chart.js/blob/master/src/controllers/controller.bar.js#L244-L259
But it could also be a useful extension for Chart.js itself


ERROR: no CUDA-capable device is detected

Hi everyone,
I'm newbie at Torch programming and I'm trying to do this tutorial: https://github.com/soumith/cvpr2015/blob/master/Deep Learning with Torch.ipynb
My problems start when I arrive at the CUDA Tensors paragraph; in particular, I've written in the file "example.lua" this code:

require 'cutorch';
a = a:cuda()
b = b:cuda()
c = c:cuda()
c:mm(a,b) -- done on GPU

When I do "th example.lua", I receive this error:

THCudaCheck FAIL file=/tmp/luarocks_cutorch-scm-1-9319/cutorch/lib/THC/THCGeneral.c line=16 error=38 : no CUDA-capable device is detected
/home/USER/torch/install/bin/luajit: /home/USER/torch/install/share/lua/5.1/trepl/init.lua:384: cuda runtime error (38) : no CUDA-capable device is detected at /tmp/luarocks_cutorch-scm-1-9319/cutorch/lib/THC/THCGeneral.c:16
stack traceback:
[C]: in function 'error'
/home/USER/torch/install/share/lua/5.1/trepl/init.lua:384: in function 'require'
example.lua:1: in main chunk
[C]: in function 'dofile'
...USER/torch/install/lib/luarocks/rocks/trepl/scm-1/bin/th:145: in main chunk
[C]: at 0x00406670

I've already try many solutions, but no-one works for me... Please, help me!
Thanks.
UPDATE: I'm using Ubuntu 64 bit virtualized on Mac OS X El Capitan with Parallels Desktop 10.

I think you posted the bug in the wrong place, maybe https://github.com/torch/torch7/issues


District Codes

Where to get the district codes from?

@anisingh62  For 45+ Keep Min Age As 45 and Max As 100.
Star the Repo if it helps!

#20 Added the district codes in a markdown file. Sorted by state and district names.


Empty functions sometimes reappears

Add a vtkActor. Click ApplyProperties twice in the Module Information input tab so that the function appears and reappears. Give the vtkActor a name in the module information window. Notice how the ApplyProperties function reappears. This is probably because the input change are not saved before doing the name change. The name change might trigger a pipeline_changed signal that resets the inputs.

TODO: disallow/warn when creating a port with 0 parameters.


change sections to divs as per bootstrap 4 in rails-conf workshop

Resolves #001
Description

Type of change

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to not work as expected)
This change requires a documentation update
Documentation update

How Has This Been Tested?

Screenshots

Hello @Boucherie !
Can you update your description to use the Issue number you're resolving? Thank you!


SMTPD_PORT env var does not set port

Describe the bug
The documentation states:

Configuration is handled through properties in the config of the fixture and are initially set from environment variables:

But when set the variable SMTPD_PORT in my dockerfile via:
ENV SMTPD_PORT="555"

and then print out the value of smtpd.config.port via:
def test_sendmail(smtpd):
    logging.info(os.environ['SMTPD_HOST'])
    logging.info(os.environ['SMTPD_PORT'])
    logging.info(smtpd.config.host)
    logging.info(smtpd.config.port)

I get
INFO     root:test.py:201 xxx
INFO     root:test.py:202 555
INFO     root:test.py:203 xxx
INFO     root:test.py:204 43341

In summary, the content of SMTPD_PORT is ignored and a random free port is used instead.
To Reproduce
Set the env var SMTPD_PORT before launching the script.
Launch the script
Expected behavior
The port specified in SMTPD_PORT should be used instead of a random free port.
Environment (please complete the following information):

Docker image: python:3.11-slim
smtpdfix==0.5.2

Additional context
Add any other context about the problem here.

Hi @chrisg89,
Thanks for taking the time to report this bug.
I won't have time to work on it until the weekend, but will try to get to it then. If in the meantime you want to submit a PR fixing the issue I'd be happy to review and publish a release.


Submenu: Meter with variable increments

We already have a working meter submenu, but the increments are currently fixed. In order for the submenu to be usable for things like font size selectors, we'll need varying increments. This can probably be best achieved by dividing the circle up into sections and assigning step intervals to each section. Dividing the circle up into for example four slices, the user should be able to define a submenu with the following markers:
000° - 0
090° - 12
180° - 36
270° - 72

closed via https://github.com/CatalystCode/radial-menu/pull/55