build my  model on my own data set

i read the post and understand that the network will be for feature extraction (is this right ?)
i want to make model on my own data set
when i read the blog post i understand that the steps to generate my network is
1- prepare my data set using tensor flow
for example i will use below code to prepare data set
import cv2

# Use a custom OpenCV function to read the image, instead of the standard
# TensorFlow `tf.read_file()` operation.
def _read_py_function(filename, label):
  image_decoded = cv2.imread(filename.decode(), cv2.IMREAD_GRAYSCALE)
  return image_decoded, label

# Use standard TensorFlow operations to resize the image to a fixed shape.
def _resize_function(image_decoded, label):
  image_decoded.set_shape([None, None, None])
  image_resized = tf.image.resize_images(image_decoded, [28, 28])
  return image_resized, label

filenames = ["/var/data/image1.jpg", "/var/data/image2.jpg", ...]
labels = [0, 37, 29, 1, ...]

dataset = tf.data.Dataset.from_tensor_slices((filenames, labels))
dataset = dataset.map(
    lambda filename, label: tuple(tf.py_func(
        _read_py_function, [filename, label], [tf.uint8, label.dtype])))
dataset = dataset.map(_resize_function)

2- then i will pass this data set to train.py as arg
but what i can't understand is params file (i don't know what is the values inside it )
and also will the code generate model for me ?and after that i can send image to that model  and the model will recognize it
i am bit confused can you help me to understand and make model on my own data set
thanks in advance
i appreciate your help

You can use your own model, but just the triplet loss I defined.
See #18 for a discussion on how to use the loss with Keras.


Backlog size calculation errors can result in unlimited messages being produced

Describe the bug
Backlogs are sets of unacknowledged messages for a topic that have been stored by bookies even if not consumed. But in fact, if the topic has not been consumed, you can produce unlimited messages.
https://github.com/apache/pulsar/blob/be7b24f9f8aa67b2235e523485249aef8d2a611a/managed-ledger/src/main/java/org/apache/bookkeeper/mledger/impl/ManagedLedgerImpl.java#L921-L926
To Reproduce
Set a limited BaclogQuotaSize to produce unlimited messages without consuming.
Expected behavior
Limited production message

fixed in #4936


Dynamic NFTs

Dynamic NFTs
Grant category
Please select one:
Open source maintenance
Description
I want to develop a smart contract that allows for dynamic updating of NFT metadata. This contract would also act as a baseline standard for all future projects to implement dynamic NFT metadata as well.
Problem statement

Target audience
The target audience for this is projects who want to have dynamic updating of NFT metadata. For example, this smart contract would allow for updating metadata when a common goal is reached in a community, when a user strikes an achievement or performs some action, when a certain on-chain fundraising goal or other on-chain trigger is met, when an NFT is resold, etc.

Evidence for the need
There are projects in need of figuring out how to solve this issue but there is no standard or common place to seek this type of behavior in a contract. Further, by moving beyond a standard NFT model with locked metadata, projects are unlocking additional potential use cases for their assets and community.

Proposed solution
I will design a smart contract, similar to the accepted ExampleNFT contract, that allows for dynamic updating of NFT metadata by exposing an ability to do this by an Admin in the contract.
Impact

In what ways does this benefit the broader Flow developer ecosystem?
It will allow entities such as Dapper/Flow to have a common way to solve this dynamic issue across their projects, as well as other Cadence developers to see how to update NFT metadata dynamically in a contract.

Milestones and funding

Milestone
Deliverables
Timeline
Risks
USD proposal

0 - Technical
Smart Contract, Transactions, Scripts
3 days
-
2500

1 - Adoption
A GitHub repository with detailed explanation on how to adopt this standard and use it as an Admin in your community, including a step by step walkthrough of what actions you'd have to take. A blog that defines dynamic NFTs and describes their importance, with a guide explaining how to spin up a dynamic collection on Flow.
1 week
-
1500

2 - Maintenance and Support
Assistance supporting implementation of smart contract, availability to answer questions regarding the contract, transactions, setup, and other relevant subjects, resolution of bug fixes
3 months
-
1000

Team

Name
Role
Bio
Contact

Jacob Tucker
Smart Contract Developer
Founder of Emerald City DAO
<EMAIL_ADDRESS>

thanks for the submission @jacob-tucker. we'll review and get back to you soon

Hey @jacob-tucker, thanks for your patience!  Just wanted to let you know that we've accepted this submission and will be following up via email with next steps.  Thanks!

Hey @jacob-tucker, thanks for the update!  Will review the two items from Milestone 2!
In terms of Milestone 3/maintenance, please follow back up at the end of the period with an update as we're expecting that you'll continue to address issues as they arise wrt the contracts/repo.  Thanks!

Hey @chrisackermann! Just following up at the end of the period to claim Milestone #3

Hey @jacob-tucker!  Marking Milestone 3 as accepted and closing out this particular grant.  Thanks so much!


bug: boost activating when empty

Describe the bug
Boost is activating when the boost bar is empty
To Reproduce

Empty the boost bar
Keep tapping boost
Camera shake & exhaust animation activated

Expected behavior
When boost is empty camera shake & exhaust animation should not be activated

camera shake could be removed if nitro is empty, but the boost exhaust ani is is really short as usual with nitro. I would let coz in real life behaves as same way if you do not have fuel anymore got last short pulls from engine.


Incomplete Ubuntu 22.04 UEFI instructions lead to broken network support

ZFSBootMenu build source
Release EFI
ZFSBootMenu version
2.3.0
Boot environment distribution
Ubuntu 22.04
Problem description
Following the instructions for setting up an Ubuntu 22.04 boot environment doesn't account for important differences between what debootstrap installs and what the search-engine-visible distro docs assume will have been installed by the regular installer.
Most notably:

It just assumes that debootstrap or the ubuntu-desktop metapackage will set up DHCP... which is untrue.
If you add in Managing Redundant ESPs with mdraid, "Depending on the distribution, additional setup may be required to assemble the mdraid array on boot. Consult your distribution's documentation for more information." is inadequate because debootstrap doesn't install the mdadm package but the Ubuntu docs assume it'll have been installed by default by the regular install ISO.  For that one, I had to just guess my way to fixing that.

In both cases, the problem comes down to "ZFSBootMenu guides the user through an install process that omits steps/packages the distro docs assume will have been performed/installed by the more traditional install procedure".
As a result, I followed some third-party instructions for adding networking to a debootstrap install that involved systemd-networkd, but it left me with a machine that can see the outside world, but anything else on the same LAN gives "No route to host" when trying to reach it (WTF? You're on the same subnet, DHCPed from the same server!) so I'm stuck preparing to manually diff my Kubuntu CD install'd laptop's /etc against my ZFSBootMenu instruction'd desktop's /etc to figure out how Canonical expects DHCPed networking to work in 22.04.
Steps to reproduce

Follow the  instructions at https://docs.zfsbootmenu.org/en/v2.3.x/guides/ubuntu/jammy-uefi.html
Once rebooted into the new environment, try running sudo apt-get update or anything else that requires an active network connection.

Our guides are intended as overviews to illustrate the disk layout and expected by ZFSBootMenu and to provide an environment capable of building ZFSBootMenu images on the local host. They are not intended to provide comprehensive coverage of the installation process of every distribution.
We assume that users following our guides will have the basic Linux and Unix system administration abilities necessary to configure their environments as they see fit. Hence, in the Ubuntu guides, we note that "[a]ny additional software should be selected and installed at this point." User judgment is expected.
We happily welcome pull requests to refine the language or improve clarity of our guides, although there is some line that demarcates "refinement" and "providing remedial introduction", which is out of scope.
In the meantime, we do not consider this a bug.

If it's not meant to go that far, then why does it mention "Any additional software should be selected and installed at this point. For a normal desktop experience, install the ubuntu-desktop meta package."?
I think "For a normal desktop experience, install the ubuntu-desktop meta package." is a bug, since doing so does not result in a normal desktop experience but gives readers the impression that it will.

Also, for anyone who finds this via search engine, here are the two differences I found:

debootstrap doesn't create the /etc/netplan/01-network-manager-all.yaml  file that the regular *buntu installer does. It's supposed to contain the following:
# Let NetworkManager manage all devices on this system
network:
  version: 2
  renderer: NetworkManager

That'll get you networking but...

Something about the debootstrap install flow pulled in firewalld when the regular 22.04 LTS installer didn't, which was stacking up with my usual UFW and causing all sorts of confusing problems. Just remove one of them and ask the other to flush and rebuild things. (eg. sudo ufw reload)

dba12663f4ec3facfb6e72f04666f001bc02f7ad

That works. Thanks.


Tree Building exercise in F# has nonsense readme

From the readme:

The ID number is always
between 0 (inclusive) and the length of the record list (exclusive). No record
has a parent ID lower than its own ID and no record, except the root record,
has a parent ID that's equal to its own ID.

These sentences are both false and violated in the tests. Maybe the design changed and someone forgot to update the readme? Currently the root node has a parent id of -1.
The root node, and at least one child of the root, must have "a parent ID lower than its own ID".

Would you be interested in creating a PR to fix this?

@ErikSchierboom for clarification is the issue:

The F# implementation is not compliant with the spec
The spec is not correct in x-common here:
https://github.com/exercism/x-common/blob/9a0cc1b96f2f9c8f7614f1337d8f58bd05a939b9/exercises/tree-building/description.md

I can do that later today.
On Dec 16, 2016 7:22 AM, "Erik Schierboom"<EMAIL_ADDRESS>wrote:
Would you be interested in creating a PR to fix this?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/exercism/xfsharp/issues/250#issuecomment-267592874,
or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABP-zHuhgp0OhJhIkLRxdM3a_z8bjNJGks5rIpCigaJpZM4LPKfT
.

@robkeim It's number 1: the F# implementation is not correct.
@cowlike Perfect! For this exercise, you actually have to edit two files:

Example.fs: the default "good" implementation.
TreeBuilding.fs: the starting "bad" point.

Wait what?! The spec makes no sense to me unless the root node has the
highest ID, which is just bizarre. IMO, the root should be have ID 0 and
build up from there, meaning the parent ID is always lower.
Doing it the other way is confusing. It would make more sense to just fix
the spec to match the supposedly working version.
On Dec 16, 2016 8:22 AM, "Erik Schierboom"<EMAIL_ADDRESS>wrote:
@robkeim https://github.com/robkeim It's number 1: the F# implementation
is not correct.
@cowlike https://github.com/cowlike Perfect! For this exercise, you
actually have to edit two files:

Example.fs
https://github.com/exercism/xfsharp/blob/master/exercises/tree-building/Example.fs:
the default "good" implementation.
TreeBuilding.fs
https://github.com/exercism/xfsharp/blob/master/exercises/tree-building/TreeBuilding.fs:
the starting "bad" point.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/exercism/xfsharp/issues/250#issuecomment-267603960,
or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABP-zFomR-R1MCkUxIrQ1E8zq1oZh2sRks5rIp6KgaJpZM4LPKfT
.

@cowlike - The way that I read the spec is the way that you described it here:

IMO, the root should be have ID 0 and
build up from there, meaning the parent ID is always lower.

Maybe the fact that there is a negative in the spec makes it confusing to understand?

No record has a parent ID lower than its own ID

This implies that "all records have an ID larger than their parents"
It doesn't call out explicitly that the root node has to be zero it can be implied from the first part:

The ID number is always between 0 (inclusive) and the length of the record list (exclusive).

@cowlike Is this more clear? This is what I understood from reading the above spec

The ID number is always between 0 (inclusive) and the length of the record list (exclusive)
The root ID has the value 0 and is the only record to have a parent ID equal to its own ID
All other records have a parent ID lower than their own ID

No record has a parent ID lower than its own ID
This implies that "all records have an ID larger than their parents"
=========
I think you need to recheck your logic. This is the nonsense part. It
actually implies that every parent ID is >= the record ID.
On Dec 16, 2016 9:00 AM, "Rob Keim"<EMAIL_ADDRESS>wrote:
@cowlike https://github.com/cowlike - The way that I read the spec is the
way that you described it here:
IMO, the root should be have ID 0 and
build up from there, meaning the parent ID is always lower.
Maybe the fact that there is a negative in the spec makes it confusing to
understand?
No record has a parent ID lower than its own ID
This implies that "all records have an ID larger than their parents"
It doesn't call out explicitly that the root node has to be zero it can be
implied from the first part:
The ID number is always between 0 (inclusive) and the length of the record
list (exclusive).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/exercism/xfsharp/issues/250#issuecomment-267612395,
or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABP-zHPhMk-zup8_ZxOCITNOB3EUshvaks5rIqelgaJpZM4LPKfT
.

This formulation is fine except that allowing the -1 to stay for the root
parent means you only need to fix the broken spec, which had other errors
as well (see last email)
On Dec 16, 2016 9:07 AM, "Rob Keim"<EMAIL_ADDRESS>wrote:

@cowlike https://github.com/cowlike Is this more clear? This is what I
understood from reading the above spec

The ID number is always between 0 (inclusive) and the length of the
record list (exclusive)
The root ID has the value 0 and is the only record to have a parent
ID equal to its own ID
All other records have a parent ID lower than their own ID

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/exercism/xfsharp/issues/250#issuecomment-267613860,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABP-zBI8Y6DfcYDKW00Vd3-TrMneHSyBks5rIqksgaJpZM4LPKfT
.

@cowlike I've create a PR to reword the exercise's description and added a sample tree. The exercise explicitly says that the root node's parent is equal to its own ID, which is of course there to make the refactoring slightly more difficult. We should thus modify our tests and example implementations.

Thanks @ErikSchierboom I just left one small comment on the PR, but other than that it's definitely much more explicit with the sample!

Thanks @ErikSchierboom. At first I thought this was just a matter of clearing up the readme, since the existing code and tests works as is. However, it has turned into a far bigger problem of rewriting everything about it: readme, tests, implementation, example.
The rewrite of the numbering part is now logically coherent. The readme also said the existing code is working (and it is, by definition since it passes the test) and your job is to refactor it. The very meaning of refactoring is to change the structure of the code such that the existing behavior is maintained, verified by ensuring you don't break the tests.
May I ask why you chose to rewrite all the code instead of just fixing the readme to match the existing code? Starting the root with a negative parent ID is an equally valid way to construct the tree. Is this really intended to be a refactoring or a total rewrite of the "overall poor first attempt"? I'm sorry but I have to pass on any sort of PR because it's not clear what the goal is here.

One more point: if this exercise is more intended to be something like "this code is horrible, the design sucks and the poorly designed tests measure concrete implementation details instead of the desired abstract properties, so rewrite it from scratch" then it should probably say that more clearly as well.

The main reason why I chose a rewrite is to not force the other language track implementing this exercise (Go) to also change their implementations. As I see, it was just an error on my part where I did not correctly implement the exercise. Changing the readme to fix our implementation and thereby breaking some else's seemed to me the wrong way to go.
Also, I think the current requirement is a little more challenging. If the root node had a parent ID of -1, the implementation would be simpler. Now people have to consider the exception.
You can of course do a complete rewrite, but you could also try to refactor bit by bit. That's entirely up to the person doing the exercise, so I wouldn't want to force people any way.

Ok, I see now. Perhaps the exercise should be pulled from the FSharp section until it is fixed. As it is now, it is completely wrong since the tests don't match the spec and therefore this is not a refactoring, by definition. So what you're asking for is new tests against the corrected spec, a good implementation of the code, and some horrible (but correct) implementation amenable to refactoring. Is that right?

That is indeed what I'm suggesting. I can try to fix this within the next couple of days.

I think the tests should verify the properties of the abstraction and not the implementation details such as the children of a branch being in a list. Perhaps export three functions:

isBranch : 'a Tree -> bool
isLeaf : 'a Tree -> bool
children : 'a Tree -> 'a Tree list

Then testing the length of the children list or something. I'm thinking of something like this (which I believe I'll write):
type Tree<'a> = Leaf of 'a | Branch of 'a * 'a Tree list
let children (Branch (_, ch)) = ch //unsafe
//write some code
Branch ((0,0), []) |> children  //= 0
Branch
    ((0,0),
        [
            Branch ((1,0), [Leaf (2,1); Leaf (4,1)]);
            Branch ((3,0), [Leaf (6,3)]);
            Branch ((5,0), [])
        ])
    |> children |> List.length  // = 3

@cowlike That sounds like a good idea. We should probably better map the properties to tests and not test the implementation. For now, I've created a PR to fix the current issue, so at least the exercise is in sync with the problem description.

It's not at all what was requested but I wrote a solution that implements rose trees, or at least that was my intention! I decided to use Option rather than exceptions as well and I think they are under-utilized from what I'm seeing so far. I have no idea if this is what you were thinking or not but I wanted to have some fun with it. Maybe it can be of some use while you're changing things around.

Thanks for posting it! I'll definitely have a look at it. I really like your suggestion to define the tests such that the user is free to implement the tree however he/she wants.

@cowlike With #280 merged, we now have an implementation-agnostic test.

That's really nice work, Erik!


Add missing feature flag (bolt9)

Codecov Report

Merging #24 (2194178) into master (0063e2c) will increase coverage by 0.1%.
The diff coverage is 37.5%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff            @@
##           master     #24     +/-   ##
========================================
+ Coverage    35.1%   35.2%   +0.1%
========================================
  Files          17      17
  Lines        1841    1889     +48
========================================
+ Hits          647     665     +18
- Misses       1194    1224     +30

Impacted Files
Coverage Δ

lnp2p/src/bolt/bolt9.rs
50.0% <37.5%> (-2.7%)
:arrow_down:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


UndocumentedSchemaSectionError

I'm using drf_spectacular and Django oscar with auto-generated schema, while running test cases with
@staticmethod
def assertResponse(response: Response, **kwargs) -> None:
  """helper to run validate_response and pass kwargs to it"""
  schema_tester.validate_response(response=response, **kwargs)

getting an UndocumentedSchemaSectionError,
example URL : '/api/storefront/{version}/addresses/'
Error message is
Error
 Traceback (most recent call last):
   File "/usr/local/lib/python3.9/site-packages/openapi_tester/schema_tester.py", line 86, in get_key_value
     return schema[key]
 KeyError: '/api/storefront/{version}/addresses/'

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/opt/project/tests/storefront_api/tests_address.py", line 193, in test_address_listing
    self.assertResponse(response=response)
  File "/opt/project/tests/utils.py", line 208, in assertResponse
    schema_tester.validate_response(response=response, **kwargs)
  File "/usr/local/lib/python3.9/site-packages/openapi_tester/schema_tester.py", line 382, in validate_response
    response_schema = self.get_response_schema_section(response)
  File "/usr/local/lib/python3.9/site-packages/openapi_tester/schema_tester.py", line 125, in get_response_schema_section
    route_object = self.get_key_value(
  File "/usr/local/lib/python3.9/site-packages/openapi_tester/schema_tester.py", line 88, in get_key_value
    raise UndocumentedSchemaSectionError(
openapi_tester.exceptions.UndocumentedSchemaSectionError: Error: Unsuccessfully tried to index the OpenAPI schema by `/api/storefront/{version}/addresses/`.

Undocumented route /api/storefront/{version}/addresses/.

Documented routes: `
```

yes it is.
['/api/storefront/{version}/order/{order_number}/payments/airpay/check/', '/api/dashboard/{version}/media/', '/api/admin/{version}/products/{upc}/', '/api/dashboard/{version}/components/{pk}/', '/api/storefront/{version}/contact-us/', '/api/storefront/{version}/addresses/']

yeah sure, will do that

I'm going to temporarily close this. Feel free to ping me when you get a chance to open a PR and I'll re-open 🙂


Update README

There is a type error in:
import com.getcapacitor.community.firebasecrashlytic.FirebaseCrashlytics;
It should be:
import com.getcapacitor.community.firebasecrashlytics.FirebaseCrashlytics;

Hi again. Fix typo in Readme
FirebaseCrashlytic.crash({
message: "This is a crash message: Capacitor is awesome! 😃",
});
To
FirebaseCrashlytics.crash({
message: "This is a crash message: Capacitor is awesome! 😃",
});

This isn't fixed in README

This isn't fixed in README


Unreal Editor Fatal Error when using digital twin in Carla 0.9.15

We need more info, platform, version or branch, and more

Windows 10, version 0.9.15.
when following the digital twin tutorial and the onroad editor, the engine returns a fatal error after inputting a url from Open Street Maps and clicking generate map

Try latest dev version, it should be fixed

the version used was built from source only yesterday

Which is the url you are trying? Which is the crash log?

CarlaUE4_4.log
this was the crash log from one of the crashes

That log does not show any crash. I suggest you two things.
First MapName and osmname must be without any spaces. Otherwise it wont' work fine.
Second. Delete Saved folder inside Unreal/CarlaUE4/ and execute again. Saved folder will be autogenerated share it with me

UE4CC-Windows-608820F54C89A65156178A8E5635797B_0000.zip

that was from another attempt this morning

There does not appear any crash issues.  I feel like you are not in latest dev version of code. I got it working right now. Or maybe your PC specs are not good enough to generate big map

Ok, do I need to do a full rebuild from scratch to be able to access the latest dev code or is there a way to update?

Go to repo folder with console and do a git pull
then, git clean -fdx and then make launch

There does not appear any crash issues. I feel like you are not in latest dev version of code. I got it working right now. Or maybe your PC specs are not good enough to generate big map

Me too, I manually selected a small map,but crash when config. This is the carla-dev branch, need help, thanks!

There does not appear any crash issues. I feel like you are not in latest dev version of code. I got it working right now. Or maybe your PC specs are not good enough to generate big map

Me too, I manually selected a small map,but crash when config. This is the carla-dev branch, need help, thanks!

same way and same question with u

Excuse me, I would like to know what the best system configuration is, such as memory, CPU, and GPU. @Blyron

Thanks for that, The map size that I was trying to generate wasn't that big, maybe 20x20m but I will try again with the new code

Hi，I want to know if it worked in the end. I've encountered the same problem as well, with exactly the same log.


Get ip in kind

Describe the bug
Sometimes, running liqo in kind, discovery component advertises on LAN wrong ip. For example if the correct IP is 172.18.0.x it advertises 192.168.200.x
To Reproduce
Run liqo installer in kind cluster

hi @aleoli, does #190 affect also this?

Yes, as @alacuku told me, it is working fine on kind now. But I would keep this issue to remember me to do deeper tests on it


Documentation: "How to Contribute" manual

Currently, there is no way for persons new to the TypeScript/Node.js/React.js ecosystem to setup/contribute.
We may need a policy on the following:

How to set up locally
Branch Organization
How to report Bugs
How to Get in Touch
How to propose a change/feature
How to send a pull a request
How to write tests/run tests
Development workflow

Hi @kanarelo
Thanks for brining it up. This makes total sense. Do you have a template or starting point in mind?

@raminious Although, it doesn't have to be very comprehensive, we can improve it with time.
I like the following examples:

https://reactjs.org/docs/how-to-contribute.html
https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md#pull-request-guidelines
https://github.com/donnemartin/dev-setup
https://docs.github.com/en/developers/apps/getting-started-with-apps/setting-up-your-development-environment-to-create-a-github-app


Log line formatting proposal

This is a proposal for a new log line format that is easier for humans to read while still allowing deterministic machine parsing. It is inspired heavily by the glog log line format.
Both these log lines represent the same event:
Current
{"timestamp":"1521035101.769078493","source":"perm-monitor","message":"perm-monitor.query-probe.run.has-assigned-permission.failed-to-find-permissions","log_level":2,"data":{"actor.id":"query-probe","actor.issuer":"system","error":"rpc error: code = DeadlineExceeded desc = context deadline exceeded","session":"2.8089732.1"}}

Proposed
E0316 00:06:52.769078493 perm-monitor[4124] 2.8089732.1 perm-monitor.query-probe.run.has-assigned-permission.failed-to-find-permissions {"actor.id":"query-probe","actor.issuer":"system","error":"rpc error: code = DeadlineExceeded desc = context deadline exceeded"}

This line contains, in order:

Error/Debug/Info
Date
Time
Component Name
PID
Session
Message
Data

It is shorter than the old format.
The notable differences between the old and the new format are:

Log levels are represented as letters rather than slightly magical numbers. In order to keep the information density high this is a single letter. It's at the start of the line so that you can grep for all the errors in a log file by searching for letters at the start of the line. This wouldn't be possible elsewhere in the line due to occurrences of D, I, and E will be common in the rest of line.

The year is removed from the date because it's rare that logs are useful for over 365 days.

The time and date are in a lexicographical  order such that you could combine two log files together with sort -k 1.

The PID is included because it is a short, useful identifier which can be used to distinguish between multiple worker processes and can be used to see if a process restarted.

Only data is left in the JSON because it contains "untrusted" input. This means that this format will have similar performance to the existing logger. If we want to radically improve the performance then we need to remove the JSON completely and restructure the Data data structure to eliminate allocations and copying.

What do you think?

E0316 kind of looks like an error code to me. I had no idea what it was until I read that the numbers indicate a date.
Hmm, to be honest I'm not sure showing a date and time is even necessary. I kind of like how Logrus instead shows "seconds since start" which more easily gives you an idea of the timing between log lines. I think if you care about precise dates/times you're probably already using rsyslog and/or a log sink like PaperTrail which tracks that for you and lets you do fancy temporal filters.
For the data, could we show it as something like a=b c=d e="f !special chars"? Curlies and quotes are annoying to deal with since some regex engines escape them, some don't, and they're special characters in the shell. We can probably trust the key to not contain untrusted stuff, but we can just JSON encode either if they contain funny characters (or spaces). Grepping for user=vito or or build=1 something would be nicer to type than '"user": ?"vito" (because who can remember whether there's a space after the : or not).

E0316 kind of looks like an error code to me. I had no idea what it was until I read that the numbers indicate a date.

Yeah, that got me too. For what it's worth, that format is taken from glog.

Hmm, to be honest I'm not sure showing a date and time is even necessary. I kind of like how Logrus instead shows "seconds since start" which more easily gives you an idea of the timing between log lines. I think if you care about precise dates/times you're probably already using rsyslog and/or a log sink like PaperTrail which tracks that for you and lets you do fancy temporal filters.

One of the things I like about Zap is that it has a development and production mode. What if we added the colors and timestamps in development mode and removed the timestamps (or altered their format to be time since start) in production logs? That way you wouldn't get the duplication of the timestamps when viewing them in syslog.

For the data, could we show it as something like a=b c=d e="f !special chars"? Curlies and quotes are annoying to deal with since some regex engines escape them, some don't, and they're special characters in the shell. We can probably trust the key to not contain untrusted stuff, but we can just JSON encode either if they contain funny characters (or spaces). Grepping for user=vito or or build=1 something would be nicer to type than '"user": ?"vito" (because who can remember whether there's a space after the : or not).

In principle, I much prefer the format you propose. Unfortunately, based on the performance experiments I did, the time to emit a log line nearly doubles if you scan it to see if there are unprintable characters and escape them.
I think there are two things we could do:

Separate the data elements with tabs and put the onus on the developer to avoid logging a tab or newline. I think these characters should be rare enough that this is reasonable.

Ask the developer to escape the strings when they declare them so we don't need to do the work each time we emit a log line.

e.g.
logger.Error("failed-to-flail", err, lager.String("key", "bad++\n\tvalue"), lager.Int("count", 5))

I've got some ideas for some performance improvements using DaTa StRuCtUrEs if we can turn data into a list rather than a map.

One of the things I like about Zap is that it has a development and production mode. What if we added the colors and timestamps in development mode and removed the timestamps (or altered their format to be time since start) in production logs? That way you wouldn't get the duplication of the timestamps when viewing them in syslog.

Maybe they should just be toggled via flags? Development vs production is a bit opinionated terminology since someone may want to omit the timestamps in production because their logs are going to something that does timestamps for them (like rsyslog or systemd's log stack, etc).
Come to think of it, I think those systems also have structures in place for the component and pid, so in many cases those could be redundant. In the interest of maximum prettiness it may be worth considering omitting those, too (or more flags). The current Lager format already doesn't include the pid and it doesn't seem like anyone's complained. Showing the component is also fairly redundant since everyone has it at the start of their messages anyway. (Which is kind of weird! Lager has a notion of a component/system but to construct a Logger you have to give it a string, which ends up at the start of every. single. message. anyway. Maybe we should fix that in v2?)

In principle, I much prefer the format you propose. Unfortunately, based on the performance experiments I did, the time to emit a log line nearly doubles if you scan it to see if there are unprintable characters and escape them.

Fair. I guess I'm not sure what the target user is for this new format. For Concourse's use case in https://github.com/concourse/bin/issues/38 I don't really care about performance that much since it'll almost never be the bottleneck, but if we're considering this as a new default format for Lager I could see why performance would be a concern.

All things considered, I guess I'm saying Logrus' log format is pretty much ideal, lol. I was gonna mock one up but it turned out to just be exactly what theirs is.

Closing this out due to inactivity. Sounds like we need some actual user feedback and research to make these ideas actionable.


add python script to get translated tag from other

As some guy translated danbooru tags to chinese, I have written a script to add translated tags to danbooru_cn.csv

Hi, I don't really want to add a web ripper to the repo, so I suggest you create a gist for it instead.
You can also post the translated file and the python script or link to the gist in #23 for example.
I prefer this method since it keeps translation files optional.

oh thank you!!!


Fixed crash from direct property access causing nullpointer

closes #544

would it make sense to just initialize forgero on the first access to it if it's still null? And then later when the planned initialization step comes, just skip all steps that were already made

This section handles a very obscure compatability with another mod, so making sure that this runs after mainline Forgero initialization is not important.
Ideally I would implement the Main Forgero resource loading pipeline into an event based api that was executed at a later stage, so that other mods could tap into it as well. But that's for another task.
Initializing the pipeline from the compat module could possibly cause a world of trouble, so I am not too interested in testing that out right now.
Also see #545 to track the proper solution for this problem


Can't build project in VS 2017 because of Microsoft.Build.Tasks.v15.0.dll missing

Brief Description
Title says most. I'm not able to build my project which includes CppSharp as nuget package.
Error is that Microsoft.Build.Tasks.v15.0.dll is missing. What am I doing wrong? Did I missed something? MS Build tools are installed for default on my computer.
Happens on Window with latest version of CppSharp 0.86 using VS 2017

I think this is related to https://github.com/baseclass/Contrib.Nuget/issues/32.

Ironically I already did that before but had some issues. Now I'm sure it's the correct workaround. thanks for reference!

You have to installed correct Windows Driver Kit [ WDK ].
Refer Link Below :
https://docs.microsoft.com/en-us/windows-hardware/drivers/other-wdk-downloads
For my case it was
Targeted versions of Windows | Edition(s) of Visual Studio
 Windows 10, version 1709     | Visual Studio Enterprise 2017
https://go.microsoft.com/fwlink/p/?linkid=859232
After installing correct WDK 10.0.16299.15, file got created at correct location
C:\Program Files (x86)\Windows Kits\10\build\bin\Microsoft.DriverKit.Build.Tasks.15.0.dll
C:\Program Files (x86)\Windows Kits\10\build\bin\Microsoft.DriverKit.Build.Tasks.PackageVerifier.15.0.dll


Allow for customizing the set of context graphs that are displayed for a particular dataset/scenario

Currently there is no way to filter out context graphs that are unrelated to a particular scenario. We have special comparison scenarios defined, and there are certain comparison graphs that are only relevant for one specific scenario, so we should be able to configure this.
(This is being split out from #539.  See that issue for more background.)

I've added an optional method to the ComparisonDatasetOptions interface, which allows for overriding the default behavior.
export interface ComparisonDatasetOptions {
  // ...

  /**
   * An optional function that allows for customizing the set of context graphs
   * that are shown for a given dataset and scenario.  By default, all graphs in
   * which the dataset appears will be shown, but if a custom function is provided,
   * it can return a different set of graphs (for example, to omit graphs that are
   * not relevant under the given scenario).
   */
  contextGraphIdsForDataset?: (dataset: ComparisonDataset, scenario: ComparisonScenario) => BundleGraphId[]
}


Examples: Fix queryParams with namedParams

These tests clearly should be refactored, though I’d like to get this fix in, in advance of a more involved refactor that ships most of the responsibility away from this function. Maybe we can even eliminate at least one of these cases in the meantime.
Deploy blocker.

Messages

:book:
:sparkles: Thanks for your contribution to Shields, @paulmelnikow!

  Generated by :no_entry_sign: dangerJS


Upgrade dependency versions

Specifically important is the upgrade of github.com/mattn/go-isatty, because the older v0.0.3 was broken for WASM compilation.
I know you don't want to maintain this library anymore, but it's so useful! This is a small fix, I hope you can merge and release a new version of your library! Thank you!

Sounds good, let's do it :) Can you also call please go mod tidy and go mod vendor ? We vendor the dependencies and I want to make sure it's up-to-date.

Done!

Thank you @tliron

Cut a new release with these changes: https://github.com/fatih/color/releases/tag/v1.9.0


Support HELMET

Description
Added HELMET to evaluation. HELMET is a comprehensive evaluation benchmark for long-context language models with application-centric tasks. It covers seven different categories: Retrieval-augmented Generation, Passage Re-ranking, Generation with Citations, ICL, Long-document QA, Summarization, and Synthetic Recall. These datasets are complemented with controllable length and robust evaluation.
Details and instructions for running the benchmark are in HELMET/README.md.
Paper link.
Issues
n/a
Type of change
List the type of change like below. Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds new functionality)
[ ] Breaking change (fix or feature that would break existing design and interface)

Dependencies
n/a
Tests
Describe the tests that you ran to verify your changes.
To test running the HELMET benchmark, we use python eval.py --config configs/icl.yaml in the HELMET directory.
We also tested the whole suite with bash scripts/run_eval.sh.

please fix the pre-commit.ci issues


Bug: MQTT entity name starts with the device name in your config - HA 2023.8

Hi,
There was a change about MQTT naming for HA Core 2023.8 about not having device name in entity name. It seems HASS agent uses device name in the entity name, for example:
2023-08-01 07:48:57.836 WARNING (MainThread) [homeassistant.components.mqtt.mixins] MQTT entity name starts with the device name in your config {'availability_topic': 'homeassistant/sensor/ANTO/availability', 'icon': 'mdi:webcam', 'unique_id': '1004c0a3-9f4c-4cf3-95ba-2a91843c225f', 'device': {'identifiers': ['hass.agent-ANTO'], 'manufacturer': 'LAB02 Research', 'model': 'Microsoft Windows NT 10.0.19045.0', 'name': 'ANTO', 'sw_version': '2022.14.0', 'connections': []}, 'name': 'ANTO_HP_webcamactive', 'state_topic': 'homeassistant/binary_sensor/ANTO/ANTO_webcamactive/state', 'payload_off': 'OFF', 'payload_on': 'ON', 'payload_available': 'online', 'force_update': False, 'availability_mode': 'latest', 'enabled_by_default': True, 'payload_not_available': 'offline', 'encoding': 'utf-8', 'qos': 0}, this is not expected. Please correct your configuration. The device name prefix will be stripped off the entity name and becomes '_webcamactive'

All the mqtt entites generated by HASS agent generate this log.

Ive read the post from HA regrading this but im not really getting it fully. Saw your post ImSkully so im asking here.
If i understand correclty, is Hass.Agent not going to work after 2024.2.0 if Hass.Agent isnt updated to comply with this before that?

it sounds like it wont break HASS agent, but rather duplicate the device name according to Frenck
It already removed the device name from the friendly name on my system, but it has not changed the entity itself.

same messages here:
MQTT entity name starts with the device name in your config {'availability_topic': 'homeassistant/sensor/XXXXXXXX/availability', 'icon': 'mdi:battery-high', 'unique_id': 'XXXXXXXX_battery_charge_remaining', 'device': {'identifiers': ['hass.agent-XXXXXXXX'], 'manufacturer': 'LAB02 Research', 'model': 'Microsoft Windows NT 10.0.19045.0', 'name': 'XXXXXXXX', 'sw_version': '2022.14.0', 'connections': []}, 'name': 'XXXXXXXX_battery Charge Remaining', 'state_topic': 'homeassistant/sensor/XXXXXXXX/XXXXXXXX_battery/XXXXXXXX_battery_charge_remaining/state', 'force_update': False, 'encoding': 'utf-8', 'qos': 0, 'payload_available': 'online', 'payload_not_available': 'offline', 'enabled_by_default': True, 'availability_mode': 'latest'}, this is not expected. Please correct your configuration. The device name prefix will be stripped off the entity name and becomes '_battery Charge Remaining'

This should not be a breaking change when it does come into effect in 2024.2 so the deprecation warning is safe to ignore for HASS.Agent users.
It would be good to perhaps have the option to change the broadcasted entity name for sensors in the same way entity IDs can be provided.

Excuse me, for me this is a breaking change ...
or what am i doing wrong ??
What can I do ? Thanks.

@heilingbrunner Your issue is unrelated to that warning.

@heilingbrunner looks like these are AhoyDTU warnings, refer to the issue over there: https://github.com/lumapu/ahoy/issues/1066

The easiest way to fix this is to do it yourself. You need to manually rename all of your sensor names to remove the device name from the sensor name:

Screenshot

So it should look like this:

Screenshot

Restart Home Assistant and the warning caused by HASS.Agent entities should disappear. Or another way is to ignore it and wait until someone creates a PR, and it will be merged.

I also tried to rename all the sensors and commands but it failed in an unexpected way.
If you have multiple computers set with the same names for the sensors and commands, you get a unique_id error in the Home Assistant logs and the duplicates are not shown.

Renaming the names will/can break the entity ids - sensor. within HA as with the current discovery payload, HA is creating entity IDs base on the name. You can leave it for now as it's only a deprecation warning.
A PR is in the works to address this.

I also tried to rename all the sensors and commands but it failed in an unexpected way.
If you have multiple computers set with the same names for the sensors and commands, you get a unique_id error in the Home Assistant logs and the duplicates are not listed and never show up. I ended up having to rename everything with the device name again and live with the repair warning.

Same here, the disk sensor failed and only one pf the machines with hass agent showed disk c. Also decided to go back and rename with devicename.

I renamed my buttons and sensors in HASS Agent removing the device name from them and problem solved.

Alternative if you have more than 1 instance of the Agent deployed would be to change the sensor names somewhat so that they do not contain the device name yet still be unique across the Agent instances.

I moved the device name to the end of command name and sensor names.  Seems to be OK so far.

Fixed in 2.0.1 and up.

For anyone following this and was confused as I was (subscribed to the issue but not activly following the project), there's a fork under the hass-agent that's had some ongoing development since this repo/org appears to be dormant.

Fixed in 2.0.1 and up.

Which "2.0.1"?
Latest release according to https://github.com/LAB02-Research/HASS.Agent/releases still is this:

It's a joke or do I miss some GitHub mechanisms here?
I ran into the very same issue after updating HA almost ONE YEAR after this issue arrised for the first time (HA 2023.8) - and there still is no fix in a stable HASS agent release? Are you kidding?

As I have more than one client running HASS agent, just removing the device name in hass agent sensor config is not a solution.
Maybe switching to the maintained fork as mentioned in https://github.com/LAB02-Research/HASS.Agent/issues/337#issuecomment-1985050154 is a proper future-proof "solution"...

Fixed in 2.0.1 and up.

Which "2.0.1"?
Latest release according to https://github.com/LAB02-Research/HASS.Agent/releases still is this:

It's a joke or do I miss some GitHub mechanisms here?
I ran into the very same issue after updating HA almost ONE YEAR after this issue arrised for the first time (HA 2023.8) - and there still is no fix in a stable HASS agent release? Are you kidding?

As I have more than one client running HASS agent, just removing the device name in hass agent sensor config is not a solution.
Maybe switching to the maintained fork as mentioned in #337 (comment) is a proper future-proof "solution"...

They are referring to the fork
https://github.com/hass-agent/hass.agent

I know and I have now switched all my clients to that forked version. Event it's "only" the client component (HA integrations like HASS.Agent can stay untouched according to https://www.hass-agent.io/latest/getting-started/installation/#migration-from-pre-200) it was a lot of work to remove the duplicates of these sensors:

batterie_charge_remaining
batterie_charge_remaining_percentage
batterie_charge_status
batterie_full_charge_lifetime
batterie_powerline_status
speicher_total_disk_count

...which are not all existing sensors, so in MQTT plenty of topics still exist with the old devicename_sensorname setup and only those listed above got a new topic name deviceUniqueID_sensorname.
Wondering what about all the remaining ones?
Not sure what the forked version did on this. I can only see when editing existing sensors which have a device name in its name, it gives an information - that's it.

I'll check if HA will continue to complain - I think so...

I know and I have now switched all my clients to that forked version. Event it's "only" the client component (HA integrations like HASS.Agent can stay untouched according to https://www.hass-agent.io/latest/getting-started/installation/#migration-from-pre-200) it was a lot of work to remove the duplicates of these sensors:

batterie_charge_remaining
batterie_charge_remaining_percentage
batterie_charge_status
batterie_full_charge_lifetime
batterie_powerline_status
speicher_total_disk_count

...which are not all existing sensors, so in MQTT plenty of topics still exist with the old devicename_sensorname setup and only those listed above got a new topic name deviceUniqueID_sensorname.
Wondering what about all the remaining ones?
Not sure what the forked version did on this. I can only see when editing existing sensors which have a device name in its name, it gives an information - that's it.
I'll check if HA will continue to complain - I think so...

Oh my goodness, I didn't realize some people were paying for this free tool! Please dev team, fix this huge problem that is disrupting this paying customer's life ASAP!!! He pays for this, so he can demand the resolution of bugs quickly and completely! Return to work NOW and fix it!!!!

I don't see why one would post such non-contributing rubbish to a factual report.
I'd recommend the mods to mute your post as it contributes absolutely nothing. Have a great day.

Have you not been listening?
There are no mods.
This repository is dead.
This topic is closed.
The picture above is inaccurate, you are actually flogging a dead horse.

Yes I got that. Seems to be an invitation for some folks (like @pabloaugusto) to behave like in the wild west. I'm out of here.

Yes I got that. Seems to be an invitation for some folks (like @pabloaugusto) to behave like in the wild west. I'm out of here.

Free cry airdrop! EnJOY yourself


Add RTL8188EU Kernel Driver

I got some USB-WiFi sticks using the rtl8188eu kernel driver, this seems not to be activated.
I've read about some more dongles using this driver.

This is a staging driver, that is likely the reason. Staging sometimes contains funny stuff, both regarding stability as well as sometimes also due to unclean licensing. We would have to do a careful evaluation first.

I've scanned the code and checked the history - seems it's uncontroversial progressing well towards being moved out of staging. Two questions, though:

did anyone test it's stability over our 4.19 kernel already (via a custom image)?
where do we get any potentially needed firmware from?

I did a simple test by just adding CONFIG_RTL8188EU=m to iot2050_defconfig_extra.cfg. This was not solving the problem.  Don't know if this step is enough?
There is also a description  how to install the firmware for this dongle, but therefore the kernel headers are needed.

I suspect you are missing a firmware for the device. Check the kernel logs.
That description is rather old. That git repos was a work of a repo of the kernel developer who is working on the staging driver. So at least with 5.10, we should have good chances that things will work this way.

May 25 13:41:39 iot2050-debian kernel: [ 4554.048938] usb 1-1.1: new high-speed USB device number 7 using xhci-hcd
May 25 13:41:39 iot2050-debian kernel: [ 4554.153215] usb 1-1.1: New USB device found, idVendor=2001, idProduct=331b, bcdDevice= 0.00
May 25 13:41:39 iot2050-debian kernel: [ 4554.161578] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
May 25 13:41:39 iot2050-debian kernel: [ 4554.168903] usb 1-1.1: Manufacturer: Realtek
May 25 13:41:39 iot2050-debian kernel: [ 4554.173276] usb 1-1.1: SerialNumber: A0A3F014A874
That's all from the kernel logs.

Yeah, you are missing https://github.com/torvalds/linux/commit/5f74a8cbb38d10615ed46bc3e37d9a4c9af8045a - added only to 5.0.

Can I integrate that somehow in my build?
Or do I need to wait until we have kernel 5.x?

I don't think we will easily be able to identify and backport needed patches for this device to the 4.19 kernel anymore.
So, for now you could

build latest firmware and image with :kas/opt/upstream.yml
install that new firmware (keep a programmer in reach in case this goes wrong)
boot the new image

Latest master (only works with rebuilt/reflashed firmware) should allow this now. But we still won't set CONFIG_STAGING by default.
Upstream is now working on R8188EU, so maybe a kernel release somewhere next year will have this fully integrated.


Improve Specificity in Instructions & Documentation. "App location" is ambiguous

From the UI:

Enter the location of your application code.  For example, '/' represents the root of your app...

What does this mean?  What is "root of your app"?  Do you mean "root of your source code repository"? Or the root of the directory I currently have open (which might not be the repo root)?  Or the path to the app at run-time? On the server file system or in the URL?
From the docs:

The app location is where the project app code lives. For example, if the src folder exists in the app folder, then the value app should be entered.

The docs add more confusion than explanation.

if the src folder exists in the app folder, then the value app should be entered

What?  Why would it not be /app/src ?  Is /src going to be implicitly added to whatever path I enter?

This setting is the location that the Static Web Apps GitHub Action will attempt to build your app. If you're working with a npm or yarn based project with a single package.json, this setting should be set to the directory containing your package.json (typically the root /).
A common case where you might need to set the app location to something other than the root would be a monorepo. Example: assuming your app is at /apps/my-app and /apps/my-app/package.json is the package.json location, then you would enter /apps/my-app.
Hope I was able to provide some clarity. We're working on improving the wording within the extension and on the documentation as we understand it's confusing.


TE: Support v1.8 - current main

Fixes https://github.com/Lightning-AI/lightning-thunder/issues/499
Verified that the tests pass on v1.6 (stable), v1.7 and v1.8 (current main).
Tested with test_transformer_engine_executor.py and test_ddp.py -k transformer

cc: @IvanYashchuk

We don't need to do this in this PR, but after merging, should we bump the -latest to TE 1.8?

The CI doesn't have a job for TE - it is tracked in https://github.com/Lightning-AI/lightning-thunder/issues/196


tslib_1 is not defined

TypeScript Version:  nightly (2.5.0-dev.201xxxxx)
Code
tsconfig.json
{
  "compilerOptions": {
    "target": "es5",
    "module": "commonjs",
    "lib": [
      "dom",
      "dom.iterable",
      "es6"
    ],
    "importHelpers": true,
    "noUnusedLocals": true,
    "declaration": true,
    "sourceMap": true,
    "outDir": "./lib",
    "rootDir": "./src",
    "strict": true,
    "noImplicitAny": true,
    "strictNullChecks": true,
    "noImplicitReturns": true,
    "typeRoots": [
      "node_modules/@types",
      "typings"
    ],
    "experimentalDecorators": true
  }
}

// A *self-contained* demonstration of the problem follows...
// Test this by running `tsc` on the command-line, rather than through another build tool such as Gulp, Webpack, etc.

Expected behavior:
Code run without error.
Actual behavior:
I got an error Error: Error: Evaluation failed: ReferenceError: tslib_1 is not defined. I don't have reproduction code, But I think it's because of tslib. I have install tslib and set "importHelpers": true to tsconfig.json file. Am I missing something?
The Error
Exception has occurred: Error
Error: Error: Evaluation failed: ReferenceError: tslib_1 is not defined
    at <anonymous>:1:16
    at <anonymous>:24:35
    at <anonymous>:1:16
    at <anonymous>:24:35
    at Shopee.<anonymous> (path/index.ts:51:13)
    at step (path/node_modules/tslib/tslib.js:122:27)
    at Object.throw (path/node_modules/tslib/tslib.js:103:57)
    at rejected (path/node_modules/tslib/tslib.js:94:69)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:188:7)

Maybe related #17192.

@rohmanhm please provide self-contained reproduction of the issue.

@mhegazy I don't get any error when running tsc. The error just appears when runtime or debugging.
Should I import tslib package into my .ts file?
Before I got this error, I got error undefined __awaiter then I enable importHelpers to true after that I got error tslib_1 is not defined. I have installed tslib package as dependencies, but nothing happens.

Should I import tslib package into my .ts file?

No, an import should be generated for you.
see var tslib_1 = require("tslib"); below.

c:\test\18039>type a.ts
export async function f() {
    return 0;
}

c:\test\18039>type tsconfig.json
{
  "compilerOptions": {
    "target": "es5",
    "module": "commonjs",
    "lib": [
      "dom",
      "dom.iterable",
      "es6"
    ],
    "importHelpers": true,
    "noUnusedLocals": true,
    "declaration": true,
    "sourceMap": true,
    "outDir": "./lib",
    "rootDir": "./",
    "strict": true,
    "noImplicitAny": true,
    "strictNullChecks": true,
    "noImplicitReturns": true,
    "typeRoots": [
      "node_modules/@types",
      "typings"
    ],
    "experimentalDecorators": true
  }
}

c:\test\18039>tsc --v
Version 2.5.1-insiders.20170825

c:\test\18039>tsc

c:\test\18039>type lib\a.js
"use strict";
Object.defineProperty(exports, "__esModule", { value: true });
var tslib_1 = require("tslib");
function f() {
    return tslib_1.__awaiter(this, void 0, void 0, function () {
        return tslib_1.__generator(this, function (_a) {
            return [2 /*return*/, 0];
        });
    });
}
exports.f = f;
//# sourceMappingURL=a.js.map

Automatically closing this issue for housekeeping purposes. The issue labels indicate that it is unactionable at the moment or has already been addressed.


Responses with content-encoding:gzip and transfer-encoding:chunked fail

If you try to download a file from a server that has "content-encoding: gzip" and "transfer-encoding: chunked" you get a failure successfully decoding the content because empty strings get passed to the decoder after the last chunk is processed.
I have a tentative patch, but am having a tough time writing a unit test to go along with it since it seems that the httplib HTTPResponse object is the one responsible for handling the transfer-encoding:chunked .
My first attempts to fix it are here:
https://github.com/Ludovicus/urllib3/tree/issue_441
The debugging output there is not intended to be final!

---
There is a **[$15 open bounty](https://www.bountysource.com/issues/3643918-responses-with-content-encoding-gzip-and-transfer-encoding-chunked-fail?utm_campaign=plugin&utm_content=tracker%2F192525&utm_medium=issues&utm_source=github)** on this issue. Add to the bounty at [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F192525&utm_medium=issues&utm_source=github).

So here is a short demo of how I think I may have come up across this issue or a related one. In short, I'm seeing different behaviour bubble up to the requests python library based only on differing versions of urllib3 (10.1.3 seems to introduce the issue for me).
A test script (note that HOST and PATH have been substituted for actual host and path):
root@9173b88edbc6:/tmp# cat post_test.py
import requests
import httplib
import logging
import gzip
import StringIO

httplib.HTTPConnection.debuglevel = 1
logging.basicConfig()
logging.basicConfig()
logging.getLogger().setLevel(logging.DEBUG)

requests_log = logging.getLogger("requests.packages.urllib3")
requests_log.setLevel(logging.DEBUG)
requests_log.propagate = True

r = requests.post('http://HOST/PATH',data='{"ids": [32, 44, 200, 1, 10, 20, 68, 103, 126, 221, 51, 136]}')

print 'apparent encoding: {0}'.format(r.apparent_encoding)
print r.content

Here are some results:
root@9173b88edbc6:/tmp# pip install urllib3==1.10.2
Downloading/unpacking urllib3==1.10.2
  Downloading urllib3-1.10.2-py2-none-any.whl (77kB): 77kB downloaded
Installing collected packages: urllib3
  Found existing installation: urllib3 1.10.1
    Uninstalling urllib3:
      Successfully uninstalled urllib3
Successfully installed urllib3
Cleaning up...
root@9173b88edbc6:/tmp# python ./post_test.py
DEBUG:urllib3.util.retry:Converted retries value: 0 -> Retry(total=0, connect=None, read=None, redirect=0)
INFO:urllib3.connectionpool:Starting new HTTP connection (1): HOST
send: 'POST /PATH HTTP/1.1\r\nHost: HOST\r\nContent-Length: 61\r\nAccept-Encoding: gzip, deflate, compress\r\nAccept: */*\r\nUser-Agent: python-requests/2.2.1 CPython/2.7.6 Linux/3.14.1-031401-generic\r\n\r\n{"ids": [32, 44, 200, 1, 10, 20, 68, 103, 126, 221, 51, 136]}'
reply: 'HTTP/1.1 200 OK\r\n'
header: Server: nginx/1.6.2
header: Date: Wed, 29 Apr 2015 19:51:10 GMT
header: Content-Type: text/html
header: Transfer-Encoding: chunked
header: Connection: keep-alive
header: X-Powered-By: PHP/5.5.9-1ubuntu4.5
header: Content-Encoding: gzip
DEBUG:urllib3.connectionpool:"POST /PATH HTTP/1.1" 200 None
apparent encoding: ascii
[32,33,34,35,36,37,38,39,40,41,42,43,231,232,233,44,45,46,47,48,49,50,226,227,228,200,201,202,203,204,205,206,229,207,208,209,210,211,212,213,214,215,216,217,218,219,220,1,3,4,5,6,7,9,230,10,11,12,13,14,15,16,17,18,19,225,20,21,22,23,24,25,26,27,28,29,30,31,68,69,70,71,72,73,74,75,76,77,78,79,80,81,82,83,84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100,101,102,103,104,325,326,327,328,329,330,105,331,332,333,334,335,106,107,336,337,338,108,109,110,111,112,113,114,115,116,117,126,127,131,132,133,134,135,221,222,223,224,51,52,53,54,55,56,57,58,60,59,61,62,63,64,65,66,67,136,137,138,139,140,141,142,143,145,146,147,148,149,150,151,152,153,154,155,156,157,158,159,160,161,162,163,164,165,166,167,168,169,170,171,172,173,174,175,176,177,178,179,180,181,182,183,184,185,186,195,196,197,198,199]
root@9173b88edbc6:/tmp# pip install urllib3==1.10.3
Downloading/unpacking urllib3==1.10.3
  Downloading urllib3-1.10.3-py2-none-any.whl (78kB): 78kB downloaded
Installing collected packages: urllib3
  Found existing installation: urllib3 1.10.2
    Uninstalling urllib3:
      Successfully uninstalled urllib3
Successfully installed urllib3
Cleaning up...
root@9173b88edbc6:/tmp# python ./post_test.py
DEBUG:urllib3.util.retry:Converted retries value: 0 -> Retry(total=0, connect=None, read=None, redirect=0)
INFO:urllib3.connectionpool:Starting new HTTP connection (1): HOST
send: 'POST /PATH HTTP/1.1\r\nHost: HOST\r\nContent-Length: 61\r\nAccept-Encoding: gzip, deflate, compress\r\nAccept: */*\r\nUser-Agent: python-requests/2.2.1 CPython/2.7.6 Linux/3.14.1-031401-generic\r\n\r\n{"ids": [32, 44, 200, 1, 10, 20, 68, 103, 126, 221, 51, 136]}'
reply: 'HTTP/1.1 200 OK\r\n'
header: Server: nginx/1.6.2
header: Date: Wed, 29 Apr 2015 19:51:17 GMT
header: Content-Type: text/html
header: Transfer-Encoding: chunked
header: Connection: keep-alive
header: X-Powered-By: PHP/5.5.9-1ubuntu4.5
header: Content-Encoding: gzip
DEBUG:urllib3.connectionpool:"POST /PATH HTTP/1.1" 200 None
apparent encoding: None�0�ۍ
       ��������ƍ��A�
G���J��L��N���h

if I take the body of the failed request and parse as follows I'm able to get the expected output:
data = gzip.GzipFile('', 'rb', 9, StringIO.StringIO(r.content))
all = data.read()
print all

@d136o Can you check with the current master? I believe we've fixed this problem.

@Lukasa thanks for pointing that out. I cloned this repo and pip installed and the test script above ran with the more expected output. Thanks for the quick comment!

Yay, safe to close this issue?

Hurrah!
Alright, I consider this issue fixed. :grinning:

@Lukasa Btw looks like @Ludovicus wrote some tests for the issue: https://github.com/Ludovicus/urllib3/commit/edddf726c838cd428138541c34059f40576c7408
Worth merging them?

Maybe, but they might be a bit over complicated compared to writing a socket level test.
That said, if no-one volunteers to do that, it can't hurt!

I have a smaller patch at #606


Bug 1289718: Adding data breakpoint via Breakpoints Window results in..

.."When '0x0000000000000000' changes (4 bytes)" when input is an expression
Before:

After:

Will clean up extraneous comments

@gregg-miskelly, your understanding of the problem is correct. If the user inputs an expression other than an address, the corresponding address displayed is 0x0000000000000000. However, if the user inputs an address, the correct behavior is observed.
To address the return value from HostMarshal.GetDataBreakpointStringForIntPtr(), again, you are correct; if the user inputs "*test", the function returns "*test".
Thus, my current approach is to retrieve the address of the user-input expression if said expression is not an address; I use the return value of HostMarshal.GetDataBreakpointStringForIntPtr() to determine this.
Please let me know if you have any further questions. Thanks!

In addition to the above, here is what I messaged Charlie on May 20, 2021:

@gc46 Thanks! I think this is a bug in the VS UI. I sent you an email yesterday with where I think the bug is.

@gregg-miskelly - yep, I saw your email. Will look into it. Thank you again!

@gregg-miskelly, to follow up on your email regarding SetDataLocation() in dbgbp.cpp, I set a breakpoint at the line you highlighted and found the following:

location

DataFullName: null
DataExpression: 0x143bb73c L"test"
DataCount: 4

bstrDataExpression: 0x143bb73c L"test"
GetDebugger()->DoesCurrentStackFrameSupportMetric(metricDataBPAsString): true
currentLocation

DataFullName: null
DataExpression: null
DataCount: 4

updatedLocation

DataFullName: null
DataExpression: 0x13ee0944 L"test"
DataCount: 4

Notice that updatedLocation.DataFullName is null; I will investigate this. Furthermore, there is no need to modify the if-condition as DataExpression is already populated and correct. Thanks!


openapi_parser.errors.ParserError: Invalid schema type '['string']'

tmp.yaml.txt
Describe the bug
The YAML file we use fails to be parsed. I believe have tracked it down to:
type:
- string
The error is shown as:
File "/home/***/.local/lib/python3.10/site-packages/openapi_parser/builders/schema.py", line 135, in create
raise ParserError(f"Invalid schema type '{schema_type}'") from None
openapi_parser.errors.ParserError: Invalid schema type '['string']'
I'm quite confident that the YAML syntax is correct. We use it just fine and Swagger does not complain.
To Reproduce
Use attached YAML file and type:
python3
from openapi_parser import parse
all_parse = parse('tmp.yaml')
Expected behavior
No error parsing the file.
System details (please complete the following information):

OS: Kubuntu 22.04
OpenAPI / Swagger version 3.1.0
Python version 3.10.12

Additional context

Hey @asdfasdfasdfasdfasasdf, looks like you are using type field as array instead of plain value, it should be like others in your specs:
openapi: 3.1.0
info:
  version: unknown
  title: unknown
  description: unknown
servers:
  - url: https://localhost
    description: unknown
paths:
  /slots:
    get:
      operationId: getSlots
      tags:
        - backplane
      responses:
        "200":
          description: Successful operation
          content:
            application/json:
              schema:
                $ref: "#/components/schemas/slots"
components:
  schemas:
    slots:
      type: array
      items:
        $ref: "#/components/schemas/slot"
    object_create:
      type: object
      properties:
        id:
          type: integer
    slot:
      type: object
      properties:
        id:
          type: integer
        occupied:
          type: string
        enabled:
          type: boolean
        module:
          $ref: "#/components/schemas/slot_module"
    slot_module:
      type: object
      properties:
        serial:
          type: string # fixed line

Hi and thanks for your quick reply.
I'm no expert in YAML, trying to get a hang of it.
I believe that we use the "- string" to handle cases where it can be a string or null. In these cases it looks like
    slot_module:
      type: object
      properties:
        serial:
          type:
            - string
            - 'null'

But in the code attached to this ticket, we only have 1 member in the array.

I believe that we use the "- string" to handle cases where it can be a string or null. In these cases, it looks like

I see, but unfortunately, this is the wrong way of doing that in OpenAPI specs, you can check the details and example of a proper way of handling multiple types here in docs. Specifically in the Mixed Types section.

In Open API 3.1 it seems as if it is allowed: https://github.com/OAI/OpenAPI-Specification/issues/2244

@asdfasdfasdfasdfasasdf
Yeah, I think you're right, my bad. However, the problem is the current package supports only 3.0.* specs, so to solve that you can either roll your specs back to 3.0 or wait for the support of 3.1, but I cannot give you an exact deadline since I do not have enough time/support to deliver new big features right now.
By the way, feel free to contribute if you have some free time, I would be glad to help with that!

You are correct, this is part of version 3.1.
I would really like to help out but I'm afraid that my skills in both YAML and Python are way to low.
May I suggest that you add the supported Open API version to https://github.com/manchenkoff/openapi3-parser? Currently it says

A simple package to parse your OpenAPI 3 documents

but it would be nice if it stated 3.0.*.
Regards, Jonas

May I suggest that you add the supported Open API version to https://github.com/manchenkoff/openapi3-parser?

Yep, that would make sense! Will update readme 👍


[KAFKA-17475] feat(test/docker): set default image to eclipse-temurin:8

As title, we need eclipse-temurin:8, which as container awareness feature to prevent JVM OOM bugs.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

close due to #17520


disable the dates in the calendar

First of all thanks for this great library. I have been using this for the last two weeks but couldn't find a way to give styles to the calendar, as well as the way to disable the dates.
@paulhodel is there any way we can disable the dates and give some styles to the calendar with hiding the buttons provided with the calendar.

You can see all options of calendar of JExcel on https://bossanova.uk/jsuites/javascript-calendar/valid-range
and for style, use a file CSS for change color, position :
you have lot of class use for calendar : jcalendar, jcalendar-reset, jcalendar-confirm etc.
Use console developper of your JExcel for test and construct new theme CSS for calendar 😉

You can see this example on how to do that.
https://jexcel.net/v7/examples/javascript-calendar

@paulhodel @Guillaume-Bo, I tried with validRange: [ '2020-09-20', '2020-09-30' ] but no success. FYI  I am using jexcel where one of my column is of type calendar.
{
            type: 'calendar',
            title: 'Due Date',
            width: '250px',
            options: { format: 'DD-MM-YYYY' },
            name: 'endDate',
            validRange: [ '2020-09-20', '2020-09-30' ],
          },

Try
{
            type: 'calendar',
            title: 'Due Date',
            width: '250px',
            options: { format: 'DD-MM-YYYY', validRange: [ '2020-09-20', '2020-09-30' ]},
            name: 'endDate',
          },

yes, @Guillaume-Bo thank you so much, it's working fine now. :+1:

@Guillaume-Bo Is there any way we can hide the update button in the calendar ?

It would be better @Guillaume-Bo  if we can bring Reset and done button to the footer level. can we do that? But again thank you so very much for your response and appreciate your quick response.

it's not possible with this version of jSuites.
But you can override calendar for make as you want.
Download this file : https://github.com/paulhodel/jsuites/blob/master/src/calendar.js
And add this after file jsuites.js, and change code directory on calendar.js for make as you want 😉


Change readme summarizer content

Heading: Instant Readme Summarizer
Content: Grasp project details instantly. Our AI-driven summarizer condenses complex Readme files into concise overviews, helping you start contributing in minutes. How it works: Skip the manual work of digging through long Readme documents—get a precise summary of the setup and contribution guidelines in just one click.
Note: How it works should be on a new line, you can just use /n

I want to solve this issue can you please assign me?


Preflight Checklist

[X] I agree to follow the Code of Conduct that this project adheres to.
[X] I have searched the issue tracker for an issue that matches the one I want to file, without success.

Problem Description
流量表(iast_agent_method_pool)的id字段是int类型，像这种增量比较快的表(例如：iast_asset)是否应该使用bigint。
对应服务端代码中python字段也要相应调整。
Proposed Solution
建议排查所有可能数据量过大的数据表和相应的服务端字段类型。
Alternatives Considered
No response
Additional Information
No response

会在下个版本进行更新


Announcement

This repo is owned by the real gliz (me)
Join the discord server for questions https://discord.gg/Nj9Zs5VtFp

yay ur back

discord doesnt work

Discord expired

User was banned :(

I don't know where to post issues but the adding tokens thing isn't working, is it possible to fix it?

I don't understand how to use code. Can you give instructions somewhere.

I would love to but the people I've been giving the codes recently have been getting suspended

I don't understand how to use code. Can you give instructions somewhere.

I don't understand how to use code. Can you give instructions somewhere.

paste the code from the .js file in to this website:
https://skalman.github.io/UglifyJS-online/
it will minify the code. Paste this code into a bookmark with the prefix "javascript:" (ex. javascript:minified_code_goes_here)
click on the bookmark when you want to use it and it should work


Workflow never finishes - log errors loading files

Hi - when I try and run this I get the same errors each time…
Is there some way of loading the files manually - if so where should they sit?
Fetching 10 files:   0%|          | 0/10 [00:00<?, ?it/s]
Fetching 10 files:  10%|█         | 1/10 [00:00<00:05,  1.58it/s]
Fetching 10 files:  30%|███       | 3/10 [00:00<00:01,  4.53it/s]Error handling request
OSError: [Errno 5] Input/output error
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/data/miniconda3/pkgs/comfyui/lib/python3.10/site-packages/aiohttp/web_protocol.py", line 452, in _handle_request
resp = await request_handler(request)
File "/data/miniconda3/pkgs/comfyui/lib/python3.10/site-packages/aiohttp/web_app.py", line 543, in _handle
resp = await handler(request)
File "/data/miniconda3/pkgs/comfyui/lib/python3.10/site-packages/aiohttp/web_middlewares.py", line 114, in impl
return await handler(request)
File "/data/app/server.py", line 63, in cache_control
response: web.Response = await handler(request)
File "/data/app/server.py", line 141, in origin_only_middleware
response = await handler(request)
File "/data/app/server.py", line 75, in cors_middleware
response = await handler(request)
File "/data/app/custom_nodes/ComfyUI-Custom-Scripts/py/workflows.py", line 56, in save_workflow
with open(file, "w") as f:
OSError: [Errno 5] Input/output error
Error handling request
OSError: [Errno 5] Input/output error
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/data/miniconda3/pkgs/comfyui/lib/python3.10/site-packages/aiohttp/web_protocol.py", line 452, in _handle_request
resp = await request_handler(request)
File "/data/miniconda3/pkgs/comfyui/lib/python3.10/site-packages/aiohttp/web_app.py", line 543, in _handle
resp = await handler(request)
File "/data/miniconda3/pkgs/comfyui/lib/python3.10/site-packages/aiohttp/web_middlewares.py", line 114, in impl
return await handler(requ

If it helps anyone else - it was just the model.safetensor that wouldnt load whilst running - so I manually added it into the structure from the Hugginface repository. it goes in  /models/AIFSH/Shitao/OmniGen-v1/

I might have a similar issue, files keep loading but stuck there.
mine however didnt show error and not knowing what file is missing.
@adamreading which file you end up missing and did you solve it?

 I might have a similar issue, files keep loading but stuck there. mine however didnt show error and not knowing what file is missing. @adamreading which file you end up missing and did you solve it?

Just exactly what I mentioned above, for me it was the model.tensor 15gb main file from https://huggingface.co/Shitao/OmniGen-v1/tree/main


[JENKINS-31832] fixed job class hierarchy

This pull request broke authenticationToken (which is still functional in jenkins). https://groups.google.com/forum/#!topic/job-dsl-plugin/wQpbhPrafHY

Why the hell you removed the authjenticationToken? It is still avaible in jenkins pipeline job type?

Please restore the authenticationToken functionality in the jobDSL.


[Refactor] Break up Objects.cs

Objects.cs is a "catch-all" file that contains multiple unrelated class definitions
In this change, I removed Objects.cs and split up all of the definitions from that file into various other files. I did my best to group and place things appropriately.
This change has no functional differences, but I did change the namespace for at least one class, which could break other projects if they depend on it.
I didn't touch any of the code I moved around. (I'll save that for future changes 😈 )

This one has been a long time coming and will probably lead to conflicts with some of your other PRs. Going to attempt to make these merges as clean as possible but may need to cherry pick some  commits if I can't easily resolve them on github directly.

If the conflicts are just with my PRs, I'm happy to resolve them myself as well. I don't want to generate too much extra work for you! 😃


Fix invalid namespace error

Please update title and description.

Versions
v0.9.2
What did you do?
See references to this issue.
What did you expect to see?
Tests pass.
What did you see instead?
Tests are skipped.
Environment
https://github.com/FerretDB/FerretDB/actions/runs/4287706440/jobs/7468887085

This is for tigris handler right @w84thesun ?


Star channel not working

star channel are not working, I logged with hotstar premium account and played some movie it played fine, but while playing channel(star vijay),it show connect to jio network,
Is necessary to have jiofiber connection to play star channel or jiosim enough?
Or it will play in any network?

Add-on name: Jiotv&hotstar
Add-on version: 2.2.2&1.1.1
Kodi version: Kodi 19.3
Operating system version/name: Android 9
Using from country: India

Duplicate of #172


Linux aem and tailon services don't autostart after reboot

Ahmed, first thanks very much for laying the groundwork for something that looks to be very helpful.
I'm running the vm on macOS Mojave, with Ansible 2.7.9 (also tried 2.7.10), VirtualBox 6.0.4 (6.0.6 has vbguest plugin install issues), and Vagrant 2.2.4.  The three services you set up (author, publish, and tailon) don't autostart after reboot.  It might be an Ansible bug because there have been reports of this issue in the past with other services (e.g., nginx).  Wanted to verify you see the same issue with a fresh install before I dig any deeper, or if you already have a suggested workaround in place.  Everything is fine after starting the services manually though.

Yeah this appears to be a bug, the init scripts don't start on reboot. Opened #4 for it. Feel free to make the switch if you'd like. It wont be for a few days before I get to it.
I did notice it was not working before, but missed creating a bug!
A simple work around for now is to tag the tasks that run the systemd services then run ansible with only those tags after a reboot. See: https://docs.ansible.com/ansible/latest/user_guide/playbooks_tags.html


Refactor enc_ciphertext to return reference instead of copy

This PR updates the ShieldedOutput trait to return a reference from the enc_ciphertext method instead of a copy. This change was discussed and suggested in PR zcash/zcash_note_encryption#2 review.
Other minor changes:

Fix the comment for split_plaintext_at_memo.
Restore the original order of const definition to reduce PR diff.
Remove extra spaces in rust-toolchain.toml.
Remove unused constants COMPACT_NOTE_SIZE, NOTE_PLAINTEXT_SIZE, ENC_CIPHERTEXT_SIZE.
Updated CHANGELOG.md.

please replace changelog to
- **Breaking change:** removed the constants `COMPACT_NOTE_SIZE`,
  `NOTE_PLAINTEXT_SIZE`, and `ENC_CIPHERTEXT_SIZE` as they are now
  implementation spesific (located in `orchard` and `sapling-crypto` crates).
- Generalized the note plaintext size to support variable sizes by adding the
  abstract types `NotePlaintextBytes`, `NoteCiphertextBytes`,
  `CompactNotePlaintextBytes`, and `CompactNoteCiphertextBytes` to the `Domain`
  trait.
- Removed the separate `NotePlaintextBytes` type definition (as it is now an
  associated type).
- Added new `parse_note_plaintext_bytes`, `parse_note_ciphertext_bytes`, and
  `parse_compact_note_plaintext_bytes` methods to the `Domain` trait.
- Updated the `note_plaintext_bytes` method of the `Domain` trait to return the
  `NotePlaintextBytes` associated type.
- Updated the `encrypt_note_plaintext` method of `NoteEncryption` to return the
  `NoteCiphertextBytes` associated type of the `Domain` instead of the explicit
  array.
- Updated the `enc_ciphertext` method of the `ShieldedOutput` trait to return an
  `Option` of a reference instead of a copy.
- Added a new `note_bytes` module with helper trait and struct to deal with note
  bytes data with abstracted underlying array size.

Done.


Daily notes in multiple folders breaks the outline

My daily notes are not all in one folder, but instead are organised in a separate folder for each year; Daily/2020, Daily/2021, Daily/2022, Daily/2023, Daily/2024 etc.
The outline only works within a single folder. It breaks when I try to shift between January and the preceding December.
Can this be changed so the outline sees all files within the higher-level folder; "Daily"?

Thanks for using the plugin!
By "breaks outline" do you mean that you cannot use the left and right arrow icons to move the display period across years?
If so, as far as I have tried at hand, I have been able to move folders by year without any problems.
Could you please provide the following information?

If you mean that you cannot move across years, what is happening when you click on the arrow icon? No reaction? Does the view display disappear? Or something else? Does the console displayed by Ctrl+Shift+I show any errors?
Do you have the Daily Note core plugin enabled?

If so, what do you specify for the date format and folder, respectively?

Do you have the Periodic Notes plugin enabled? If so, what is the version?

If so, what do you specify for the date format and folder, respectively?

Any other information that might help us reproduce the problem?

Thanks for your quick response!
When I try to move across years by clicking the arrow icon I get the following error:

The Daily Note core plugin IS installed. These are the settings:

The Periodic Notes plugin is NOT installed.
My Daily Notes are stored in the following folder structure:

Hope this helps.

I see, if you specify Journal/2024 for new file location, only the notes in the folder will be treated as daily notes.
I think you can fix it by specifying Journal for New file location setting and YYYY/YYYY-MM-DD-ddd for Date format.
See also the Automatic subfolders section of the help page below.
https://help.obsidian.md/Plugins/Daily+notes

Thanks, that makes perfect sense, and I tried it and it worked.


Feature Request

Is there a method you can add that auto-fills the date of birth fields that some contests require?
Firefox stores the date you originally set for the field to auto-populate, it's a matter of clicking the field, dropping the field and clicking the stored date.
Here's a link to a contest that has a date of birth field requirement, for example.
https://gleam.io/MorB4/mobile-strike-4k-hdtv-contest
Thanks again for all your excellent work creating this script!

I don't believe I can interact with Firefox or Chrome's auto-complete features.  It's possible though to implement my own simple auto-complete feature just for the birthday input.
I like the idea, but I'm not sure when I'll get around to doing it.