How to reject e-mail addresses with UTF-8 characters in the local part?

zend-validator 2.9.0 used to reject e-mail addresses with utf-8 characters in the local part (e.g. å or ö). As of zend-validator 2.10.0, such e-mail addresses seem to be considered valid. We are using postmark to send e-mails, which throws an exception at such e-mail addresses. Is there a way to configure Zend\Validator\EmailAddress to reject these e-mail addresses?

Originally posted by @aimfeld at https://github.com/zendframework/zend-validator/issues/224

As a workaround, I have extended the EmailAddress validator like this:
class EmailAddress extends \Zend\Validator\EmailAddress
{
    protected function validateInternationalizedLocalPart($localPart)
    {
        return false;
    }
}

This seems to work. Is there any better way to handle this?

Originally posted by @aimfeld at https://github.com/zendframework/zend-validator/issues/224#issuecomment-378541345

Have same problem: Amazon SES allow only 7-bit ASCII characters in local part of e-mail Amazon SES API Docs.
I'm not sure if your workaround is best solution, i would prefer flag to be able switch between those utf-8 characters.

Originally posted by @Buzka91 at https://github.com/zendframework/zend-validator/issues/224#issuecomment-396524445


Bug: /update-profile accidentally sent AP Delete for 16 web users

4df76d0db7b87cabbd714039546c05b3221169be introduced a nasty bug: for anyone who clicked the 🔁 (update profile) button on their user page, BF deleted their bridged profiles instead. Ugh. Really bad!
This was later fixed in<PHONE_NUMBER>8e8224ca2b11d0f0f4e207a496fa1a, along with a test that should have been there in the first place and would have caught this. Bridgy Fed has decent test coverage, 93% right now, but clearly not good enough!
During the window that this bug was live, it hit 19 accounts, all web sites. Of those, only one was active, ie had ever bridged a post: @tantek, tantek.com.
I was able to recover and recreate the bridged Bluesky profiles, including their followers. I was also able to restore the bridged fediverse profiles by sending new Create activities to them for his actor manually, and later Undos for the original Deletes, but the followers there didn't come back. Their instances severed those following relationships, and recreating the profiles didn't restore them. Catastrophic. 😭
I can see which of those followers haven't re-followed since then, so I'm going to manually DM them from<EMAIL_ADDRESS>to tell them what happened and nudge them to re-follow, with text that @tantek wrote. (We've been discussing this on and off in https://chat.indieweb.org/dev.)

@tantek posted about this: https://tantek.com/2024/287/t1/fediverse-unfollow-bridgyfed-bug

We're sending DMs to @tantek's followers who hadn't already refollowed to tell them what happened and nudge them to follow again. Here's the code:
t = Web.get_by_id('tantek.com')
followers = Follower.query(Follower.to == t.key).fetch()
users = [u for u in ndb.get_multi(f.from_ for f in followers) if u and not u.status]
active_f = [f for f in followers if f.status == 'active' and f.updated < datetime.datetime(2024, 9, 22, 13, 9, 39)]
users = {u.key: u for u in users}

import dms

text = """\
Admin notice: this account (<a<EMAIL_ADDRESS>was accidentally deleted recently due to a bug in its fediverse provider, which resulted in other fediverse servers removing its followers, including you. We've now restored the account, so feel free to re-follow at your discretion. Sorry for the inconvenience!

[This one-time DM sent by Bridgy Fed on behalf of <a<EMAIL_ADDRESS>Bridgy Fed accounts do not yet support receiving DMs.]"""

for i, f in enumerate(active_f):
  print(i, user.key.id())
  user = users.get(f.from_)
  if not user or not user.obj or not user.obj.as2:
     print('skipping!')
     continue
  target = user.target_for(user.obj, shared=False)
  id = f'https://fed.brid.gy/tantek.com#delete-bug-dm-{i}'
  dm = Object(id=id, source_protocol='web', our_as1={
    'objectType': 'activity',
    'verb': 'post',
    'id': id,
    'actor': 'https://fed.brid.gy/tantek.com',
    'object': {
        'objectType': 'note',
        'id': f'{id}-obj',
        'author': 'https://fed.brid.gy/tantek.com',
        'content': text,
        'tags': [{
            'objectType': 'mention',
            'url': user.key.id(),
        }],
        'to': [user.key.id()],
        'published': util.now().isoformat(),
    },
    'to': [user.key.id()],
  })
  dm.put()
  try:
    activitypub.signed_post(target, data=ActivityPub.convert(dm, from_user=t), from_user=t)
  except BaseException as err:
    print(err)

  # can't use this, it sends from bot user
  # dms.maybe_send(from_proto=Web, to_user=user, text=text)

How it looks to me as a user of Ivory on Mastodon.
Nice idea, I'm already following Tantek again though, so I probably didn't need to get this.
Curious how well it actually works.

Thanks @mattl! And interesting! I tried to exclude users who'd already re-followed, but I guess I didn't try hard enough.

@tantek posted about this: https://tantek.com/2024/287/t1/fediverse-unfollow-bridgyfed-bug

This one helped me understanding that the mistake was genuine (and not a takeover). Thanks.

It wasn't clear to me that the message was sent on tantek's behalf with his consent or knowledge, which made it somewhat weird.
Screenshot of the message on mastodon.social:

@zcorpan hah, funny. I can understand that. @tantek and I did do it together. My first draft of the text was much more in his voice - "Hi! My fediverse provider had a bug recently..." - but he preferred the current text instead, since he couldn't receive or send replies to it.


Clarify initial setup steps

The plugin has just an average rating at https://plugins.jetbrains.com/plugin/8143-cppcheck/reviews.
It seems most of them stem from the documentation for the initial setup being confusing. We need to figure out what confuses people and improve the documentation accordingly. Maybe even rewrite it from scratch.

Agreed. For what it's worth, most of the poor ratings came before I made the landing page a lot more clear. But overall, if the plugin better guided a user through what they needed to do (such that you didn't really need to refer to docs) that would probably be best.
When I initially wrote this plugin I was new to IntelliJ plugins and wrote this one based on an existing Cpplint plugin that followed a similar usage flow. I think this workflow could definitely be improved with some more digging into what IntelliJ offers (years later).

I am planning on making the configuration regarding the --language= option a bit easier for 1.6.0 by handling it internally.
The enhanced error balloon should probably also help in some situations.
I also have a document ready which covers most of the known issues in detail as well as offering some workaround. That should hopefully resolve some user issues as well. While I was writing that I actually thought of lots of things which resulted in those past few issues I added.
I am still not sure how to integrate it with the plugin description for the CLion repository though.


PROD-200/hi-fi-designs

Waiting for other devs to finish modals for claim and reveal.
https://github.com/user-attachments/assets/03c1d5a1-2e1e-4144-ad11-90b3bdc281ac

@Yihwan @marvinmarnold everything is implemented except reveal and claim deck. Because those modals are in development so I am waiting for other devs to finish it first.

@Yihwan @marvinmarnold everything is implemented except reveal and claim deck. Because those modals are in development so I am waiting for other devs to finish it first.

i noticed that some campaigns that have decks to reveal are showing decks with "wait to start" – assuming that is what this above comment is referring to and eventually the decks shoul dhave "reveal" ctas


fix: improve jsonRPC error UX for eth1 + execution

Motivation
Manage the state transition for the eth1 provider to log the errors with right context.
Description

Refactor the JSONRPCClient to allow events
Updated the Execution Engine to use the events of rpc client
Used the same pattern for the Eth1Provider as well

Closes #4348
Steps to test or reproduce

Run all tests

The log format does not change. it still shows the error exactly like before.
Sep-28 11:36:04.057[eth1]            error: Error updating eth1 chain cache  Request to https://lodestar-mainnetrpc.chainsafe.i failed, reason: getaddrinfo ENOTFOUND

The only change would be the error will be shown once connection have any issue.

can we have the "eth1 communication restored/online" etc kind of messages like how you did in the engine when state changes

Sep-28 15:40:16.247[eth1]            error: Eth1Provider caused error state=OFFLINE, lastErrorAt=undefined Request to http://<IP_ADDRESS>:8080 failed, reason: connect ECONNREFUSED <IP_ADDRESS>:8080

Sep-28 15:40:27.889[eth1]             info: Eth1Provider is back online oldState=OFFLINE, newState=ONLINE

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


Risky Repository Name

Hi, great work you got here!
Just a quick reminder to maybe change the name of the repository to something unrelated to Minecraft unless you've made sure Microsoft is fine with it. I had a project of a web-based Minecraft two years ago too, but when it got too much attention, Microsoft struck it down with a DMCA copyright strike... I spent six months on this project only to see it taken down simply because Microsoft wasn't happy with the name "mc", and said that I was using texture packs related to Minecraft, I was devastated. Also, Microsoft also claimed that I was "fishing for real Minecraft accounts", even though my project was nowhere deployed online. So you might want to watch out for that aspect too.
In conclusion, I'm here to congratulate you on the good work you've put into this, and also to remind you that maybe it's not a good idea to keep the name "Minecraft" as the project name. If you don't agree with me, feel free to close this issue! :raised_hands:

You' re right, but hmm... what name

Maybe webmc

Ok changed :)

changed :)

BTW, maybe also swap out the textures

On top of that, the download is being advertised with copyrighted Minecraft imagery and textures, acting as the backdrop to the site, without Microsoft’s consent or authorization. This is not an action protected by any fair use doctrine.

That was from my DMCA takedown notice.


Instructions to set up symbols

I don't deem to have to speaker or arrow symbols shown in the gif.

Would be nice to have some instructions on how to get the full effect.
Details
Terminals: st, alacritty
Font: JetBrainsMono Nerd Font
Version: latest main branch
Platform: Arch linux

Awesome I just pulled the latest and it seems to have fixed it for me. Thanks!


make @Ref optional for in file reference

If a variable cannot be resolved, it should automatically be tried to be resolved using the @Ref method. If this is possible, it should be used.

I thought this improvement was easy to implement. By using NodeJS scripts, the detection of the referenced response is not directly possible. Triggering the Reference Error and recognizing the name based on the error message would be possible, but it doesn't feel good. One would require a specific language and message. Additionally one would couple two more or less independent modules. Overall, I find the benefit too small for these obstacles.


Categorical coloring not honored when category filters in place

Context

Making a categorically colored map of political donors
each donor should get a color according to the party of the donation
parties have specific "known" colors, so they should not get swapped around, regardless of what the filter is doing

Steps to Reproduce

Make a categorical coloring
Add a categorical widget
change the filter in the widget
see if the legend and the map continue to respect your initial categorical coloring

Conservatives should be Blue, everyone knows that :) and the "By Value" coloring specifies it, too.

Autostyling is a WIP. Product team is fixing bugs and adding widget customization. This issue is expected to be fixed really soon. :-)


Terminal cient?

why desktop when it is TUI

oh yea you are right... thanks for pointing it out!

Fixed with https://github.com/darylhjd/mangadesk/commit/21e985fa14138736cb1816155026119d72e7d44b

good job on this one, wanna connect? discord: Ilya Revenko#4742

thanks! i don't use discord that much most of the time but sure :)


Remove flush operations to prevent excessive segment creation in Milvus

Typically, this method is called once all the data is ingested. You are advised not to call this method frequently since it could generate a lot of tiny segments and lead to unstable problems.

I found that the flush operation is time-consuming, and frequent flush operations result in the creation of many segments, which can impact performance. This also increases the pressure during the compaction process.

Thanks!


Different result from get_steady_states in case of a 2D sweep depending on sampling rate in the same linear range

I get different number of solution branches from get_steady_states in the case of a 2D sweep if I change the sampling number (eg, going from LinRange(-0.25, 0.25, 80) to LinRange(-0.25, 0.25, 81) ) even when I sweep the parameter between the same values. The bug does not appear in HarmonicBalance v0.6.4, but it appears in HarmonicBalance v0.8.0
Expected behavior
The number of solution branches should have remained the same in both cases. The error does not happen when I am working with a positive [0,0.25] or a negative [-0.25,0] range, but only when I am working with a negative to positive range [-0.25,0.25].
Minimal Reproducible Example
using HarmonicBalance
@variables ω0,γ,ω,α,F₁,m,δ, t,x(t), T;
natural_equation =  d(x,t,2) +γ*d(x,t) + ω0^2*x + α*x^3;
factor = γ^2/4;
factor /= γ^2/4 + δ^2;
forces_new =  F₁*cos(ω*t) - factor*F₁*m*cos(ω*t);
diffEOM_new = DifferentialEquation(natural_equation + forces_new, x);
add_harmonic!(diffEOM_new, x, [ω]);
averagediffEOM_new = get_harmonic_equations(diffEOM_new);
fixed = (F₁=>0.02,α => 1.0,γ=>0.025,ω0=>1.,ω=>1.1)
swept = (m=> LinRange(0.0,1.0,50), δ => LinRange(-0.25, 0.25, 80)); #here, try LinRange(-0.25, 0.25, 81)
res2D = get_steady_states(averagediffEOM_new, swept, fixed);
plot_phase_diagram(res2D)

Environment (please complete the following information):

Output of using Pkg; Pkg.status()

HarmonicBalance v0.8.0

Output of versioninfo()

Julia Version 1.9.3

Hey Soumya. Should the last term in natural_equation be cubed?

Oh hey, sorry about that. Must've left it out while copying. Yes, it should be cubed

Hey Soumya,
The problem seems to be solved if you use the total_degree solver in get_steady_states by adding the kwarg method=:total_degree.  This is because by default we use method=:warmup, where we first try to find all branches with a simpler warmup exercise and then do the complete homotopy. However, if some roots slip through the cracks in the warmup, they will also not appear in the final solutions. In general, I recommend doing a :total_degree (use some threads to make it faster). We probably should make :total_degree default and recommend :warmup when performance is important for, for example, larger resolution 2d sweeps.
using HarmonicBalance

@variables ω0, γ, ω, α, F₁, m, δ, t, x(t);
natural_equation = d(x, t, 2) + γ * d(x, t) + ω0^2 * x + α * x^3;
factor = γ^2 / 4;
factor /= γ^2 / 4 + δ^2;
forces_new = F₁ * cos(ω * t) - factor * F₁ * m * cos(ω * t);
diffEOM_new = DifferentialEquation(natural_equation + forces_new, x);
add_harmonic!(diffEOM_new, x, [ω]);
averagediffEOM_new = get_harmonic_equations(diffEOM_new);
fixed = (F₁ => 0.02, α => 1.0, γ => 0.025, ω0 => 1.0, ω => 1.1)
swept = (m => range(0.0, 1.0, 50), δ => range(-0.25, 0.25, 80)); #here, try LinRange(-0.25, 0.25, 81)

res2D = get_steady_states(averagediffEOM_new, swept, fixed, method=:total_degree)
plot_phase_diagram(res2D)

I am confused why it did work on v1.6.4 on your side. Because, I had the same "bug" on v1.6.4. It would also surprise me, as that part of the code did note change at all.
It could be this line:
https://github.com/NonlinearOscillations/HarmonicBalance.jl/blob/25fd0ae1657f4af9f61c425fe5497192ba5569e0/src/solve_homotopy.jl#L256C3-L256C74
 complex_pert = [1E-2 * issubset(p, keys(sweep))*randn(ComplexF64) for p in problem.parameters]

I will look into it

I cannot seem to replicate it working on 1.6.4

Hey Soumya, this is now resolved on the master branch. The issue shouldn't be there anymore   in next version :)


Kafka cluster

Hi, does this image support Kafka cluster? It means that running multiple broker at the same cluster. I do not see any place where can set the configuration for it.
Thanks.

+1

For everyone interested, see #21

Hello - I've started work on updating this image to support proper Zookeeper and Kafka clustering - see #25. #21 is good for testing, but is a different objective (that is multiple brokers in one container, as opposed to a true multi-container kafka cluster).


Rename NSOutputStream to OutputStream

Bring NSOutputStream in line with InputStream (and change some missed NSInputStream → InputStream in comments as well)

@swift-ci Please test

Looks like TestURLSession.test_downloadTaskWithURL hung again 😬
Will re-run test when this CI job times out; hopefully the next won't hang
(Tested manually on RAD but want to verify with environment in CI)

@swift-ci Please test


Miss-leading Docker backend documentation

Two Different ways of running inside of Docker-Compose syntax
Problem encountered, when switched to "new" syntax, none of the options were applied, when using docker-compose up, docker-compose up --scale... etc.. Since docker giving warning that deploy labels will be ignored.

External network problem:
When stack has multiple networks setting label to the external name only works. All attempts to link to current stack's networks and have services accessible failed. Since it selects the random network.

There is a need to further clarify and explain two different ways of running traefik with docker bundle, and just regular docker-compose with service definition.  It affects how docker networks are being named and how compose file are read.
The issue is silent for networks until there is scenario where multiple are used.
Docker Image: Traefik 1.5.4
Version: 17.12.0-ce-win47 (15139)
Channel: stable

What does this PR do?
Documentation change for Docker backend
Motivation
Ran in to the issue when deploying.
More

[x] Added/updated documentation

is using traefik.docker.network the same as using networks ?
services:
  whoami:
    networks:
      - web
networks:
  web:
    external:
      name: traefik_webgateway

@revolunet You can use traefik.docker.network=web or traefik.docker.network=traefik_webgateway both work


Make landing page responsive

Make the page responsive so it looks good and is usable on devices of varying screen sizes (smartphones, tablets, HD monitors, etc).

hey @arujjval  please assign me this issue

Sure. Good luck!


Update Booking Form (1)

As a user I want to fill in my details in a booking form so that I can book an appointment quick and easily at Hope Again.
Acceptance Criteria
A/C 1: My required information is submitted.
Implementation Notes
Note 1: Add fields to input care givers details.
Note 2: Ensure that the mandatory fields have a asterisk next to it and that there is a note that explains what the asterisk means.
Note 3: Add How Admission Works info on the same page as the form
Note 4: Use anchor links to link to the menu bar.

@Nishka-Kisten Ensure that the book a Screening form has validations.


Crash ValueError: min() arg is an empty sequence

To recreate:
Put map seed to 25, play and move up until you get crash.

It not longer crashes (1cf72e4). However, the game lags when you get close to the trapped enemies.

Lag will be fixed in #27.


Clean up traefik boot failure

If user not deploying to a freshly provisioned server, there may be cases where traefik fails to initially boot.
For example, if there's an exisitng container binded to port 80, mrsk traefik boot  will create but not run a new traefik container, which will disrupt successive traefik boots (container name already exists).
This commit aims to clean up the initial traefik boot. If it cannot, it'll raise an exception for user to investigate and fix their docker environment.
Afterwards, they should be able to deploy as usual, and mrsk will take care of cleaning up any orphaned traefik container.
Fixes #217

Should be covered by https://github.com/mrsked/mrsk/pull/414


Reduce precision on external pool incentives

If dust is added to external incentives, it appears that it shows up on the pools themselves. I imagine this isn't the ideal behavior; I ended up just adding more SCRT to even it out.

@delivan can we set it to no decimals? or would that be too complicated due to decimals?

IMO 6 decimal places of precision is preferred, even if it's .000000; could make the digits after the decimal a bit smaller to aid in readability.

@JeremyParish69  I disagree, I think setting it to 0 decimals displayed makes more sense for external incentives. Why show that many decimals split over so many epochs? It doesn't add anything to the experience, but actively makes the UI noisier.

I think decimals on this UI can cause users misunderstand the actual bonus amount. Reducing its size is also a good solution but it's still likely to mislead users and I think decimals isn't important for total bonus amount. So I'm gonna change to no decimals soon.


Allows for use within webpack

The initial factory function is attempting to import a new instance of jquery before checking for a  globally defined one. If you have a globally defined jquery and you are building within a webpack environment it will import a new instance of jquery and miss the one you are using. So now we are checking for globals first instead of trying to import first.

Q
A

Bug fix?
yes

New feature?
no

BC breaks?
no

Related tickets

License
MIT

Ping @acrobat

@acrobat, @vsn4ik could you please check?

@vsn4ik you approved this change, but can you also merge it please?

Can we get some traction on this please?

Trying again one year later ...

@acrobat, @vsn4ik could you please check?

Please merge!

is there a way we can keep merge this?


Up Less than a second

why swarm happens "Up Less than a second" problem ?
docker -H xxx ps
 "/data/buzzExtractor   4 weeks ago         Up 4 weeks                                  wx-buzz-spider07/extractor14
 "/data/buzzExtractor   4 weeks ago         Up 4 weeks                                  wx-buzz-spider07/extractor13
 "/data/buzzExtractor   4 weeks ago         Up Less than a second                       wx-buzz-spider06/extractor12
 "/data/buzzExtractor   4 weeks ago         Up Less than a second                       wx-buzz-spider06/extractor11
 "/data/buzzExtractor   4 weeks ago         Up 4 weeks                                  wx-buzz-spider05/extractor10
 "/data/buzzExtractor   4 weeks ago         Up 4 weeks                                  wx-buzz-spider05/extractor09
 "/data/buzzExtractor   4 weeks ago         Up 4 weeks                                  wx-buzz-spider04/extractor08
 "/data/buzzExtractor   4 weeks ago         Up 4 weeks                                  wx-buzz-spider04/extractor07
 "/data/buzzExtractor   4 weeks ago         Up 4 weeks                                  wx-buzz-spider03/extractor06
 "/data/buzzExtractor   4 weeks ago         Up 4 weeks                                  wx-buzz-spider03/extractor05
 "/data/buzzExtractor   4 weeks ago         Up 4 weeks                                  wx-buzz-spider02/extractor04
 "/data/buzzExtractor   4 weeks ago         Up Less than a second                       wx-buzz-spider02/extractor03
 "/data/buzzExtractor   4 weeks ago         Up 4 weeks                                  wx-buzz-spider01/extractor02
 "/data/buzzExtractor   4 weeks ago         Up 4 weeks                                  wx-buzz-spider01/extractor01

@rfyiamcool Are these containers up all the time? Have you looked at their logs? What is docker -H xxx version?

Closing due to lack of activity. Please reopen if you wish to continue discussing it.


Fuzzy matching issue in find_filename

Issue
The find_filename function in the editblock coder has a fuzzy matching issue that causes it to consider files with similar names but different extensions as the same file. Specifically, when searching for a filename, the function considers app.controller.ts and app.controller.spec.ts as the same file.
This issue causes problems when trying to write unit tests, as the function will not create a separate spec file and instead add the test to the end of the controller file.
Version and model info
Model: llama3.1-70B diff

I understand the current workaround, but I was hoping that Aider could automatically create a new file when I ask it to write to a non-existent file. This would be more in line with the model's capabilities and would make the interaction more user-friendly.

As mentioned in the doc, LLMs are prone to overly focusing on the info in their context. If you don't make the blank file for them, they will often ignore your explicit request to make a new file.

But the llm side is ok as i said the problem is from fuzzy marching with some minor changes to find filename function i did fix it but my solution is not general so i did decide to not send pull request

I'm going to close this issue for now, but feel free to add a comment here and I will re-open. Or feel free to file a new issue any time.


Hacktoberfest 2021 theme

Hacktoberfest 2021 start soon, so I would like to make a new app theme according to site of Hacktoberfest

I could also contribute to this!

That's great!! make sure to clone the latest code from the repo itself and contribute! 🌟

Thanks for your contributions guys!!
Special thanks to @harshndroid
Counting your contributions really valuable to the project. I would like to invite you as a maintainer of this project.
If interested, do let me know and also feel free to connect with me on LinkedIn


Steam Api For Send Trade Offer

Hello , i need Api For Send Trade Offer Please Help me ,

what's json_tradeoffer ?


ncnn: 20220721 -> 20220729

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/Tencent/ncnn/releases.
meta.description for ncnn is: "ncnn is a high-performance neural network inference framework optimized for the mobile platform"
meta.homepage for ncnn is: "https://github.com/Tencent/ncnn"
meta.changelog for ncnn is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 20220729 with grep in /nix/store/p0mxxqv7hli7cy57klnn29341qj3745l-ncnn-20220729
found 20220729 in filename of file in /nix/store/p0mxxqv7hli7cy57klnn29341qj3745l-ncnn-20220729

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath
ncnn
realesrgan-ncnn-vulkan

Instructions to test this update (click to expand)

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

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

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

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

2 packages built:

ncnn
realesrgan-ncnn-vulkan

Maintainer pings
cc @TilCreator for testing.

ncnn is not building for me anymore.
error: builder for '/nix/store/m4i7p1wdmy0ynawdqbpwgwj9g7qq0dph-ncnn-20220729.drv' failed with exit code 1;
       last 10 log lines:
       >   The following imported targets are referenced, but are missing:
       >   SPIRV-Tools-opt
       > Call Stack (most recent call first):
       >   /nix/store/g42wrfayn2pjk85x793aibw07s7hyqvg-glslang-<IP_ADDRESS>/lib/cmake/OSDependentTargets.cmake:5 (include)
       >   CMakeLists.txt:481 (include)
       >
       >
       > -- Configuring incomplete, errors occurred!
       > See also "/build/source/build/CMakeFiles/CMakeOutput.log".
       > See also "/build/source/build/CMakeFiles/CMakeError.log".
       For full logs, run 'nix log /nix/store/m4i7p1wdmy0ynawdqbpwgwj9g7qq0dph-ncnn-20220729.drv'.
error: 1 dependencies of derivation '/nix/store/j5il26rpfrh0fgy84xfidlqmx104g87y-Real-ESRGAN-ncnn-vulkan-<IP_ADDRESS>.drv' failed to build

Tagging maintainers: @TilCreator


Update fs2-io to 3.1.3

Updates co.fs2:fs2-io from 3.1.1 to 3.1.3.
GitHub Release Notes - Changelog - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "co.fs2", artifactId = "fs2-io" } ]

labels: library-update, semver-patch

Codecov Report

Merging #273 (fa4a201) into master (507a275) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #273   +/-   ##
=======================================
  Coverage   84.61%   84.61%
=======================================
  Files          35       35
  Lines         221      221
  Branches       10       10
=======================================
  Hits          187      187
  Misses         34       34

Flag
Coverage Δ

unittests
84.61% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 507a275...fa4a201. Read the comment docs.


Added UNIs to attributes_requiring_redeploy

Closes #249
Summary
Added uni_a and uni_z to attributes_requiring_redeploy
Local Tests
Updated local test test_expected_requiring_redeploy_attributes() adding uni_a and uni_z to expected values.
End-to-End Tests
e2e tests on PR #201

@Alopalao just to confirm that was intentional in the changelog, is this fix expected to land as a patch for 2022.3.1 or unreleased? If it needs to land as 2022.3.1, we'll also need to bump the version in the kytos.json file.

Yep, I was just following the naming criteria from previous versions. Changing it back.


Convert submissionfile from test to spec

Thanks for feedback, I made some changes as requested.

@jenachoi I meant that you could actually just delete all of those tests that were redundant.

oh oops I see, I'll delete them


add hotgym data for NuPIC example

[x] @rhyolight here is the full example file from hotgym
[x] the windowing seems to cause problems, I'd suggest disabling for now until we need it in online monitoring PR (eg anomalies don't highlight with it, probably should add UI control so users can choose, as the hotgym example gets truncated too, ...)
[x] fixed the "fixed 2 rows skipped in header" for non-OPF files
[x] fix/workaround problem with OPF files having a reset field (causes nonmonotonic timestamps)

Fixes #10
Fixes #70

@jefffohl this is ready for your review. Functionality is complete. Resolves a couple of issues.
But if you have already a PR in progress, this can wait, or I'll help you resolving the merge conflicts..

@rhyolight this branch is ready to test, if you wanna give it a shot.

@breznak where exactly did you get that data file? The predictions look bad.

Chart looks good to me :+1:

where exactly did you get that data file? The predictions look bad.

Thanks. [discussed on chat, the file is from "official nupic" hotgym example.]

Thanks @breznak - can you explain how windowing is causing problems?

@jefffohl

can you explain how windowing is causing problems?

it is not, actually. I've tried to cross that out in the PR description, the problem was caused by the reset fields, which is fixed as a part of the PR.

:+1: Looks good @breznak. Thanks!
One thing that really needs updates is the notifications system. We have a lot of user feedback to show now that tell the user how the app is interpreting the data. I am starting to think we need a scrolling console or something similar in the UI. Having all the alerts pile up the way they are now is not working well. We should probably have that addressed before release v1.0


Is the integration of presence within Teams and outlook is resolved?

Is the integration of presence within Teams and outlook is resolved?

@konikagupta thank you for submitting feedback.
I think the best way forward is if you open a service ticket in your tenant so this can get resolved ASAP. Based on the outcome let me know if it is something that can be called out in the docs.
Please follow this link to contact support for business products:https://docs.microsoft.com/office365/admin/contact-support-for-business-products
Please keep us posted here on the resolution so we can feed whatever information you discover into the content.


Migrate build-app.py from closurebuilder.py

Use of closurebuilder.py is deprecated now that the Closure compiler
handles the dependencies on its own, thus this patch removes the call to
closurebuilder.py to produce the compressed js output.
I was kind of annoyed by the warning messages saying:
third-party/build/closurebuilder.py: Closure Compiler now natively understands and orders Closure dependencies and
is prefererred over using this script for performing JavaScript compilation.

Please migrate your codebase.

so I put this patch together.
The second commit switches from ECMASCRIPT5 to ECMASCRIPT6 since
this is necessary for some third party libraries.
The new build process works however, it slows down compilation noticeably.
This may have to do with the dependency mode.
I'm a real beginner with the Closure library and build process so I may have messed
things up. :-)

Actually, it doesn't work in all cases. I must investigate that. I'm closing this PR for now.


Add Netlify Functions Context to Netlify Adapter

Netlify Functions' Handler type[1] has a context argument that the adapter currently drops.  The context contains useful information that Endpoints may want to have access to, namely auth information[2].  This PR passes that context down to Endpoints via app. Doing this has been discussed previously in https://github.com/sveltejs/kit/issues/1249, including one person patching something roughly equivalent to this change into their local repo.
[1] https://github.com/netlify/functions/blob/efcf21eb6c969c73d165e01b00f33b53f3e150b5/src/function/handler.ts#L11
[2] https://docs.netlify.com/functions/functions-and-identity/
Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

[x] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
[x] This message body should clearly illustrate what problems it solves.
[ ] Ideally, include a test that fails without this PR but passes with it.

Tests

[x] Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

[x] If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpx changeset and following the prompts. All changesets should be patch until SvelteKit 1.0

I would expect some change to https://github.com/sveltejs/kit/blob/master/packages/adapter-netlify/README.md to document this

I would expect some change to https://github.com/sveltejs/kit/blob/master/packages/adapter-netlify/README.md to document this

Done.


Tidy 404 Not Found error page

Note if you find any non-blocking defects whilst reviewing these changes, those could well make Good First Issues.

current
proposed

/lgtm

I might well revisit https://github.com/kubernetes/website/pull/23753#discussion_r486363764, probably after this merges if that's OK?

The changes improve the current "404" page.
/approve


Padding & margins inconsistent between Bootstrap Elements

I'd like to better understand whether the existing v4 margin and padding classes as well as hx, p, etc. elements are going to remain the same or be adjusted at some point. The reason I ask is because it's practically impossible to get a content section with equal whitespace if a user is allowed to make any determination of which tags get used. This was the case with v3 as well. I'd love to see some consistency or at least better understand the reasoning behind these things.
In v4, it looks like the following is the case:

h1-h6 tags have their top-margin removed altogether. Is the assumption that each developer will set their own margins in their project? I can't imagine not wanting any top margin on hx tags, although I'd prefer they were consistent across all hx tags.
h1-h3? tags have 8px bottom margin while p tags have 16px bottom margin. What is the reasoning on this? Wouldn't it be better to have them the same? 8px is pretty short and 16px is pretty tall.
The new padding and margin classes end up being 16px, 32px, and 48px. Those don't align with the bottom margins above.

So there is no way to get a content area with equal whitespace on all sides without completely overriding everything.
In addition, containers and rows have 15px of whitespace, but gutter margins are 35px (although I get this probably has more to do with math than for the above items). Regardless, it really complicates things with trying to get consistent horizontal and vertical spacing.
In v3, things were/are still out of alignment:

h1-h3 tags have a top-margin of 22px and a bottom margin of 11px.
h4-h6 tags have a top-margin of 11px and a bottom margin of 11px.
p tags have a bottom margin of 11px.

Let me provide an example. Let's say we just want equal top and bottom "whitespace". We'll forget about horizontal space for now. The new margin and padding classes don't allow us to deal with the 8px bottom margin of hx tags at all.
I haven't completely thought through the perfect answer for this. Probably something like all hx tags having 16px top margin and 8px margin. Have all p and other tags have 8px bottom margin (or at least some consistent value). That way we could at least adjust the bottom whitespace of the div itself to get an even 16px on top and bottom. Of course we could then increase the whitespace on all sides of the div to get to other multiples, like 32px.
At any rate, I figured you guys were either still thinking this through and open to changes or had a really good explanation for why the values are set the way they are.

Sorry, quick correction:  BSv4a2 sets p-*-2 at 1.5rems which is 24px. But the discussion remains the same. Why not 8px, 16px, 24px (and up) or 16px, 32px, 48px? If BS3.x had padding and margins, I would think it should have been 11px, 22px, and 33px based on the hx and p tag margins.

I believe this has been dealt with here. https://github.com/twbs/bootstrap/issues/18490

@guylepage3 I'd say that issue is a tad different since it was only regarding utility classes.
CC: @mdo

Correct, my request / question isn't about responsive classes at all. I had read that other post. I'm not asking for any lines of CSS to be added. I'm just hoping to get the existing padding and margin classes to align with the basic element margins (hx, p, etc.) or vice versa. People are going to need to be able to line up their content in columns  easily and have content blocks with equal whitespace on them.

h1-h6 tags have their top-margin removed altogether. Is the assumption that each developer will set their own margins in their project? I can't imagine not wanting any top margin on hx tags, although I'd prefer they were consistent across all hx tags.

v4-dev/scss/_reboot.scss:

We nuke the top margin [of <h1>-<h6>] for easier control within type scales as it avoids margin collapsing.

Ok, so I understand from this article what you are talking about with collapsing margins. This article provides a very simple way to deal with it in a consistent fashion. In a nutshell, either always use top margin or bottom margin, never both. But the key to it is that those margins need to be consistent across all elements. Since it appears that you prefer to use bottom margin, then bottom margin should always be 8px or 16px, not a mixture with hx tags have 8px and p tags having 16px. Or something in between like 12px would probably be better as visually 8px is a bit too small and 16px is a bit too large. But I'm not really trying to say what it should be, I'm simply asking for it to be consistent.
So to lay out one possible scenario:

font base = 16px (this is what v4 has)
line spacing = 1.5 (this is what v4 has)
bottom margin = 12px (v4 mixes 8px and 16px)
padding and margin classes: --1 = 12px; --2 = 24px; --3 = 36px (v4 is 16px, 24px, and 48px)

So to get, let's say 24px equal whitespace on any column, regardless of what html tag they start with or end with... we can simply set padding: 24px 24px 12px 24px. No extremely complicated CSS is needed to try to determine what the first-child and last-child are to try to adjust the padding.
I suggest making the padding and margin classes align with the element margins, so that people can also use those to alter the whitespace and keep it equal if they want while just using the built-in classes. So for example if they want 36px equal whitespace on all sides, they can use: p-x-3 p-t-3 p-b-2.

Here is the article reference: Single-direction margin declarations

Think the defaults are looking good but I've definitely run into the vertical rhythm situation described above. Can we add two new variables for the margin-bottoms in the reboot that default to 1rem and 0.5rem?

Can anyone enumerate which elements / classes can utilize the spacing classes?  I've tried .m-*-0 and .p-*-0 on the .col-*-* but it does not have any effect.

The margin-bottoms should actually use the $spacer-y setting to allow a consistent vertical spacing.

So for example if they want 36px equal whitespace on all sides, they can use: p-x-3 p-t-3 p-b-2.

@timnicholson I really like this idea.

Closing since there are no planned changes here and spacer utilities provide a good level of control for changing the defaults.


Godep update

@mikedanese @gmarek @bprashanth
This is a monster.  Lets get it in ASAP so I don't have to rebase.
Please review the code changes part, the godep commit is pretty much pro-forma.

ci failure...

Ok, tests are now green on my workstation.
--brendan

LGTM


Fix usage of deprecated database field emailtemplate.oncreated

This field hasn't been populated since 2015, but was still being read from. Any "created"-type close reasons created since then will have been reporting incorrectly - thankfully that list is zero in production.

Codecov Report

Merging #612 into bantools will decrease coverage by 0.00%.
The diff coverage is 0.00%.

@@              Coverage Diff              @@
##             bantools    #612      +/-   ##
=============================================
- Coverage        5.25%   5.25%   -0.01%
  Complexity       2318    2318
=============================================
  Files             173     173
  Lines           11471   11473       +2
=============================================
  Hits              603     603
- Misses          10868   10870       +2

Impacted Files
Coverage Δ
Complexity Δ

includes/API/Actions/CountAction.php
0.00% <0.00%> (ø)
6.00 <0.00> (ø)

includes/DataObjects/Request.php
6.76% <0.00%> (ø)
37.00 <0.00> (ø)

includes/Pages/Statistics/StatsTopCreators.php
0.00% <0.00%> (ø)
2.00 <0.00> (ø)

includes/Pages/Statistics/StatsUsers.php
0.00% <0.00%> (ø)
9.00 <0.00> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9f07e0c...56180b3. Read the comment docs.

Merge blocked on #574

Codecov Report

Merging #612 (56180b3) into master (2e796f9) will increase coverage by 0.07%.
The diff coverage is 0.00%.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2e796f9...127542e. Read the comment docs.


fixes ios 9.3 non clickable issue

Can you please explain what this change does?
How can adding a no-op event handler to touchstart resolve #96?

closing as no further explanation provided.


Ready for publish. Fixes #189

Pull Request Description:
(Description in grammatically correct, complete sentences)
New Pull Request Checklist:

[x] Reviewed contributing guidelines.
[x] good commit messages
[x] Github issue added, if it exists.
[x] Added an entry to the Changelog.
[x] All tests passing: run npm test.
[x] New component tests include ember-a11y-testing to test accessibility.

@Samsinite I believe that is partially why we are doing a beta release and not a normal release. We will talk about how to address this in the next sprint planning. I know we also had been talking about contextual forms which may effect this.

@jweakley maybe just go ahead and do it... It's really annoying @Samsinite and I don't think it'd take too long and it would be good practice.

I opened an issue for Sam's feedback: https://github.com/wildland/ember-bootstrap-controls/issues/215

Thanks, yeah it has been bothering me. If we don't follow conventions, than they don't mean anything :)


Update content/zh/docs/concepts/services-networking/ingress.md

Update zh docs to release-1.18
Fixed #20668 as well

Good job!
/lgtm


Bumping quickwit's version to 0.6.5-dev

We won’t release a 0.6.5 on this branch. Maybe 0.7.0-dev ?

Discussed offline.


ORC-842: Remove newKey from StringHashTableDictionary

What changes were proposed in this pull request?
When adding keys to StringHashTableDictionary, do not copy data into intermediate container.
Why are the changes needed?
Performance.
How was this patch tested?
No changes to functionality. Use existing unit tests. Existing unit test was updated to use new internal mechanism for testing.

Under the covers, Text#hashcode uses WritableComparator.hashBytes.  If we remove the dependency on Hadoop, this will have to change, but preserves current functionality for now.

@pgaref  Thanks for pinging. Changes LGTM, and +1 for non-hadoop hashcode method.

Changed to no longer use Hadoop for hash code implementation.

Passes locally but looks like something is failing with a build download:
[  6%] Performing download step (download, verify and extract) for 'protobuf_ep'
CMake Error at protobuf_ep-stamp/protobuf_ep-download-RELWITHDEBINFO.cmake:49 (message):

Thank you all! This is now merged to main


Improve build process with dirt check

Description of the PR

Update Makefile to include dirty target
The reason for this check is that if generate produces a different file from what is the source tree, this will catch it.

PR Checklist

[x] All commits have a Developer Certificate of Origin (DCO) -- they are generated using -s flag to git commit.
[ ] All new changes are covered by tests
[ ] If GraphQL schema is changed, make generate has been run
[ ] If collectsub protobuf has been changed, make proto has been run
[ ] All CI checks are passing (tests and formatting)
[ ] All dependent PRs have already been merged

if that is the case i think this check should be part of generate check, if not i'm not sure it would guarantee the ordering of generate then dirty.

if that is the case i think this check should be part of generate check, if not i'm not sure it would guarantee the ordering of generate then dirty.

It is usually done before the build. I can move it to that.

make generated_up_to-date does a similar thing
https://github.com/guacsec/guac/blob/main/Makefile#L50-L53
It is used a few times in workflows, ex: https://github.com/guacsec/guac/blob/main/.github/workflows/ci.yaml#L113-L114
Looks like that one will fail on any extra files, while this diff one will only fail on changes to existing files. I'm not sure we need both, but also don't know which way to go.

yea i have a dirty branch almost always, so i think only for the CI case are my thoughts. In that case +1 to @jeffmendoza 's comment where i think we already have that check.

make generated_up_to-date does a similar thing https://github.com/guacsec/guac/blob/main/Makefile#L50-L53 It is used a few times in workflows, ex: https://github.com/guacsec/guac/blob/main/.github/workflows/ci.yaml#L113-L114
Looks like that one will fail on any extra files, while this diff one will only fail on changes to existing files. I'm not sure we need both, but also don't know which way to go.

I'll close this.


Poorly worded description.

One of the paragraphs starts with "Data binding automates this job, and renders the event handlers unnecessary. (The events are still necessary, however, because the data-binding infrastructure uses them.)"
Well, are they necessary or not?

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

ID: f255d152-0e9d-92dd-e1ca-0efc335f98dd
Version Independent ID: 5c7dfe7c-1696-17f2-e07d-266a170a06a0
Content: Xamarin.Forms Data Binding - Xamarin
Content Source: docs/xamarin-forms/app-fundamentals/data-binding/index.md
Product: xamarin
Technology: xamarin-forms
GitHub Login: @davidbritch
Microsoft Alias: dabritch

Hi @Entiat
The text is accurate, but clearly confusing. Data binding renders the event handlers unnecessary, but under the hood events are used.
I've updated the text in a PR that will go live later.


Weird dragging behaviour if value for slidesPerGroup is a string

Clear and concise description of the problem
If the value for slidesPerGroup for whatever reason is a string instead of an integer, the slider becomes somewhat unusable.
See the following example: https://codesandbox.io/p/sandbox/swiper-pagination-forked-hv54q2?file=/index.html:78,27
If you try to drag beyond the second "group" (slides 3-4), the slider will return to the second group. Using the bullets to go to the third group will also produce weird behaviour, when trying to drag further.
Interestingly, the same behaviour is not happening when the value for slidesPerView is a string. So slidesPerView is a bit more robust already?
Suggested solution
Apply the same king of sanitising on slidesPerGroup as is applied on slidesPerView
Alternative
No response
Additional context
No response
Validations

[X] Follow our Code of Conduct
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

Would you like to open a PR for this feature?

[ ] I'm willing to open a PR

Docs clearly says It must be a number https://swiperjs.com/swiper-api#param-slidesPerGroup

Fair enough, why not make Swiper more robust though? 🤷♂


Implement prev_call for sv callset

Waiting for a ticket to be sure... but I think this is on the right track!

@hanars I just left a comment on the ticket concerning overlapping vs identical.  Are we still ok?


Improvement for k8s.io/docs/concepts/overview/components/

Service Controller definition is not given any where in this page

https://k8s.io/docs/concepts/overview/components/ doesn't list all the controllers; that's intentional.
I did have a go at adding this (https://github.com/kubernetes/website/pull/15374) but it's quite a lot of work to document all the controllers built in to Kubernetes. If / when we add that documentation, it'd be appropriate for https://k8s.io/docs/concepts/overview/components/ to link there.

/language en


[9.x] Revert "[9.x] Update psr/log version" and fix properly

Reverts laravel/framework#38852.

What does removing the string|Stringable types fix?

Lots of libs still only support v1 and breaking v1 support is silly. When we can easily support everything, we should.

We can also clearly see most people still use v1:

Fair enough, even though I'm more on the "let's push the community forward" line of thinking (by making Laravel 9 support psr log v2 and v3 instead of all three major versions). For v1 there's still Laravel <=8.

I don't agree that's a good approach here. We can certainly recommend people v3, but until everyone gets caught up, we just needlessly stopping people from upgrading. Maybe once v3 is up to 30% of the downloads, we could reconsider, maybe for Laravel 10.

For me scarifying the type strictness to allow backward compatibility with v1 and v2 is fine, but I proposed this change because I got interface incompatibility PHP errors when using PHP 8.1 and psr/log 3, I will check if it's now working but if you just revert the previous change we likely have the incompatibility again.

This is not a straight up revert. It fixes compatibility with v3, without breaking v1 and v2.

Oh I see you reverted the param type but not the return type so it's both covariant and contravariant.

Yeh. :)


bugfix: fix the improper usage of version package

Signed-off-by: Bruce Ma<EMAIL_ADDRESS>
What type of PR is this?
/bugfix
What this PR does / why we need it:
fix the improper usage of version package, which is causing unexpected results in version comparison.
Which issue(s) this PR fixes:

NONE
Special notes for your reviewer:

/assign @dixudx

Codecov Report

Merging #523 (662877a) into main (d0ca5eb) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #523   +/-   ##
=======================================
  Coverage   13.10%   13.10%
=======================================
  Files          65       65
  Lines        7079     7079
=======================================
  Hits          928      928
  Misses       6073     6073
  Partials       78       78

Impacted Files
Coverage Δ

...hub.com/clusternet/clusternet/pkg/utils/version.go
100.00% <0.00%> (ø)

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


Fix typo in BulkWriteError.hashCode()

This fixes small error in com.mongodb.bulk.BulkWriteError.hashCode() (index field was effectively not used in hash code), which was introduced during parent class extraction.

Thanks @Powerrr!


Issuing credits

Issue 50000 credits to @gardenenigma

 Follow up
On Sunday, 10-Mar-24 06:26:54 UTC by Gov4Git dev
Issued 50000 credits to member @gardenenigma.


Make first identity user configurable

Currently the first user of identity is per default set to demo:demo. We should make this configurable via the values file.

fixed with #273


Patch keyError in #2027

Solves ´KeyError´ occurrence in #2027.
Adds Try/Except statement to find keyerror and return to old code if the keyerror is triggered.

That's not the solution. Look at the metadata.

The same information as in the original PR, #2026, can be fetched from the 'currentTradingPeriod' key in the metadata. The metadata from the code that triggered the KeyError,
dat = yf.Ticker('0001.HK')
dat.history(start=1719763200, end=1720540800, interval='30m', prepost=True)

will have the same format as most other stocks.
I don't know if Yahoo Finance may give differently formated metadata for the ´'currentTradingPeriod'´ key.

Just add 2 unit tests: one with prepost=False, other with True. Then rebase to dev branch #1084


README + docs + tests

Update README
Update docs with new optimizer module
New tests

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 67.85%. Comparing base (468cd95) to head (3cddb29).

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #77      +/-   ##
==========================================
+ Coverage   61.95%   67.85%   +5.90%
==========================================
  Files          98       98
  Lines        2389     2389
==========================================
+ Hits         1480     1621     +141
+ Misses        909      768     -141

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Add priority info

Based on this user story: "As a realtor with many client contacts, I want to be able to sort my client contacts based on priority (time, importance, etc.)"

Closed by #119, #120.


Add initial databases

On a second look, I was unable to parse the json file. There seems to be a formatting issue in the json file. The ], at the end of version_range is not expected and should be replaced with } at every occurrence. @ProgHaj  Could you please take a look? Thanks.


Added support for partial parsing

These are the finishing touches before we disable batching on the
C# client and on the server. We're changing the IHubProtocol interface to
modify the input buffer with what was consumed. We're also changing it
to parse a single message at a time to be match what output writing does.
Removes ToArray() in the optimistic case where things fit into a single buffer (for the most part)

TODO:

~Run benchmarks to see if this API change helps or hurts. There are alternate patterns we can try if this hurts.~
Add some tests for multiple buffers (we have nice helper for this in Common that I can import). This isn't really important until we disable buffering.

Baseline:
             Method |          Input | HubProtocol |        Mean |      Error |     StdDev |        Op/s |  Gen 0 |  Gen 1 | Allocated |
------------------- |--------------- |------------ |------------:|-----------:|-----------:|------------:|-------:|-------:|----------:|
  ReadSingleMessage |   FewArguments |        Json |  2,209.2 ns |  29.370 ns |  26.035 ns |   452,660.9 | 0.0343 |      - |    1120 B |
  ReadSingleMessage |   FewArguments |     MsgPack |  1,483.3 ns |  23.293 ns |  21.788 ns |   674,178.7 | 0.0248 |      - |     832 B |
  ReadSingleMessage | LargeArguments |        Json | 84,852.6 ns | 350.418 ns | 273.583 ns |    11,785.1 | 1.8311 |      - |   59016 B |
  ReadSingleMessage | LargeArguments |     MsgPack | 11,470.6 ns |  98.080 ns |  86.946 ns |    87,179.1 | 1.4038 | 0.0610 |   41688 B |
  ReadSingleMessage |  ManyArguments |        Json |  3,876.9 ns |  69.640 ns |  58.153 ns |   257,935.1 | 0.0534 |      - |    1680 B |
  ReadSingleMessage |  ManyArguments |     MsgPack |  2,983.5 ns |  54.243 ns |  50.739 ns |   335,179.1 | 0.0381 |      - |    1296 B |
  ReadSingleMessage |    NoArguments |        Json |  1,130.0 ns |  10.981 ns |   9.734 ns |   884,923.8 | 0.0229 |      - |     744 B |
  ReadSingleMessage |    NoArguments |     MsgPack |    471.7 ns |   5.856 ns |   4.890 ns | 2,119,972.0 | 0.0134 |      - |     440 B |

PR
             Method |          Input | HubProtocol |        Mean |        Error |       StdDev |        Op/s |  Gen 0 |  Gen 1 | Allocated |
------------------- |--------------- |------------ |------------:|-------------:|-------------:|------------:|-------:|-------:|----------:|
  ReadSingleMessage |   FewArguments |        Json |  2,292.1 ns |    37.037 ns |    34.644 ns |   436,285.5 | 0.0305 |      - |    1024 B |
  ReadSingleMessage |   FewArguments |     MsgPack |  1,536.4 ns |    10.784 ns |     9.560 ns |   650,869.1 | 0.0229 |      - |     736 B |
  ReadSingleMessage | LargeArguments |        Json | 85,141.1 ns | 1,078.927 ns |   900.953 ns |    11,745.2 | 1.9531 |      - |   58920 B |
  ReadSingleMessage | LargeArguments |     MsgPack | 11,789.1 ns |   157.994 ns |   140.057 ns |    84,824.2 | 1.4038 | 0.0610 |   41592 B |
  ReadSingleMessage |  ManyArguments |        Json |  4,016.4 ns |    78.962 ns |    69.998 ns |   248,976.4 | 0.0458 |      - |    1584 B |
  ReadSingleMessage |  ManyArguments |     MsgPack |  3,154.0 ns |    33.661 ns |    29.840 ns |   317,054.2 | 0.0381 |      - |    1200 B |
  ReadSingleMessage |    NoArguments |        Json |  1,184.8 ns |    23.713 ns |    21.021 ns |   844,039.7 | 0.0191 |      - |     648 B |
  ReadSingleMessage |    NoArguments |     MsgPack |    567.2 ns |     6.209 ns |     5.808 ns | 1,763,059.7 | 0.0105 |      - |     344 B |

It's slower and allocates less 😄.

Before
             Method |          Input | HubProtocol |         Mean |        Error |       StdDev |        Op/s |  Gen 0 | Allocated |
------------------- |--------------- |------------ |-------------:|-------------:|-------------:|------------:|-------:|----------:|
  ReadSingleMessage |   FewArguments |        Json |   2,676.2 ns |    57.837 ns |    71.029 ns |   373,665.3 | 0.0076 |    1120 B |
 WriteSingleMessage |   FewArguments |        Json |   2,990.4 ns |    73.083 ns |   212.028 ns |   334,402.1 | 0.0648 |    6608 B |
  ReadSingleMessage |   FewArguments |     MsgPack |   1,496.2 ns |    26.538 ns |    24.823 ns |   668,378.8 | 0.0076 |     832 B |
 WriteSingleMessage |   FewArguments |     MsgPack |   1,513.8 ns |    35.312 ns |    45.915 ns |   660,609.0 | 0.0134 |    1224 B |
  ReadSingleMessage | LargeArguments |        Json | 105,269.2 ns | 2,046.561 ns | 2,935.116 ns |     9,499.5 | 0.4883 |   59016 B |
 WriteSingleMessage | LargeArguments |        Json |  73,056.8 ns | 1,433.446 ns | 1,650.758 ns |    13,688.0 | 0.8545 |   94952 B |
  ReadSingleMessage | LargeArguments |     MsgPack |  13,042.7 ns |   259.305 ns |   574.602 ns |    76,671.5 | 0.4272 |   41688 B |
 WriteSingleMessage | LargeArguments |     MsgPack |  34,038.5 ns |   900.969 ns | 2,656.528 ns |    29,378.5 | 1.1597 |  113944 B |
  ReadSingleMessage |  ManyArguments |        Json |   4,189.6 ns |    54.910 ns |    45.852 ns |   238,683.7 | 0.0153 |    1680 B |
 WriteSingleMessage |  ManyArguments |        Json |   4,763.7 ns |    95.121 ns |   240.382 ns |   209,921.9 | 0.0839 |    7864 B |
  ReadSingleMessage |  ManyArguments |     MsgPack |   2,732.0 ns |    53.246 ns |    71.082 ns |   366,029.5 | 0.0114 |    1296 B |
 WriteSingleMessage |  ManyArguments |     MsgPack |   2,764.3 ns |    53.836 ns |    86.935 ns |   361,752.2 | 0.0114 |    1496 B |
  ReadSingleMessage |    NoArguments |        Json |   1,151.6 ns |    22.893 ns |    36.968 ns |   868,386.3 | 0.0076 |     744 B |
 WriteSingleMessage |    NoArguments |        Json |   1,795.6 ns |    58.759 ns |   172.329 ns |   556,914.5 | 0.0648 |    6176 B |
  ReadSingleMessage |    NoArguments |     MsgPack |     403.2 ns |     7.942 ns |     9.753 ns | 2,480,351.1 | 0.0048 |     440 B |
 WriteSingleMessage |    NoArguments |     MsgPack |     647.7 ns |    12.991 ns |    29.322 ns | 1,543,914.9 | 0.0095 |     976 B |

After

	         Method |          Input | HubProtocol |         Mean |       Error |      StdDev |        Op/s |  Gen 0 |  Gen 1 | Allocated |
------------------- |--------------- |------------ |-------------:|------------:|------------:|------------:|-------:|-------:|----------:|
  ReadSingleMessage |   FewArguments |        Json |   2,769.2 ns |    55.71 ns |    74.37 ns |   361,111.8 | 0.0076 |      - |    1024 B |
 WriteSingleMessage |   FewArguments |        Json |   2,857.5 ns |    56.91 ns |   160.51 ns |   349,960.0 | 0.0687 |      - |    6608 B |
  ReadSingleMessage |   FewArguments |     MsgPack |   1,562.9 ns |    31.14 ns |    47.56 ns |   639,842.4 | 0.0076 |      - |     736 B |
 WriteSingleMessage |   FewArguments |     MsgPack |   1,456.1 ns |    30.03 ns |    54.15 ns |   686,783.2 | 0.0134 |      - |    1224 B |
  ReadSingleMessage | LargeArguments |        Json | 105,728.8 ns | 2,087.19 ns | 3,370.42 ns |     9,458.2 | 0.4883 |      - |   58920 B |
 WriteSingleMessage | LargeArguments |        Json |  73,448.6 ns | 1,454.68 ns | 2,349.04 ns |    13,615.0 | 0.8545 |      - |   94952 B |
  ReadSingleMessage | LargeArguments |     MsgPack |  13,256.6 ns |   262.96 ns |   692.73 ns |    75,434.1 | 0.4425 |      - |   41592 B |
 WriteSingleMessage | LargeArguments |     MsgPack |  34,021.8 ns |   811.35 ns | 2,392.28 ns |    29,392.9 | 1.2207 | 0.0610 |  113944 B |
  ReadSingleMessage |  ManyArguments |        Json |   4,361.4 ns |    85.34 ns |    94.86 ns |   229,285.4 | 0.0153 |      - |    1584 B |
 WriteSingleMessage |  ManyArguments |        Json |   4,747.4 ns |    94.88 ns |   258.12 ns |   210,640.9 | 0.0839 |      - |    7864 B |
  ReadSingleMessage |  ManyArguments |     MsgPack |   3,115.1 ns |    62.05 ns |   100.20 ns |   321,013.5 | 0.0114 |      - |    1200 B |
 WriteSingleMessage |  ManyArguments |     MsgPack |   2,550.1 ns |    48.91 ns |    54.36 ns |   392,137.1 | 0.0153 |      - |    1496 B |
  ReadSingleMessage |    NoArguments |        Json |   1,181.2 ns |    13.90 ns |    11.60 ns |   846,575.1 | 0.0057 |      - |     648 B |
 WriteSingleMessage |    NoArguments |        Json |   1,770.6 ns |    38.19 ns |   112.01 ns |   564,770.7 | 0.0648 |      - |    6176 B |
  ReadSingleMessage |    NoArguments |     MsgPack |     517.8 ns |    10.33 ns |    26.67 ns | 1,931,337.4 | 0.0038 |      - |     344 B |
 WriteSingleMessage |    NoArguments |     MsgPack |     661.3 ns |    13.12 ns |    31.44 ns | 1,512,119.3 | 0.0105 |      - |     976 B |

Reads got a little slower

I think we're going to have to live with this performance hit. The microbenchmark highlights the difference between ROMemory and ROSequence

Hmmm, broke it 😄


RefreshTokenStore does not save updated JsonCode

When refresh token is updated, JsonCode needs to be updated too, because it contains LifeTime property that can be extended.

Wrong repo?

You are right, sorry. I'll move this to the correct repository.


Exception in thread Thread-1 from latest update to werkzeug 0.11

On werkzeug release notes it says Devserver no longer requires SSL module to be installed, but there's no mention any incompatibility problems that might arise because of that. I'm not even sure if that's causing the issue but it's the only thing that mentions ssl.
For some reason after updating from 0.10 to 0.11 I can't run my flask python code with werkzeug.
Startup Code:
context = ssl.SSLContext(ssl.PROTOCOL_SSLv23)
context.load_cert_chain('xxx.crt', 'xxx.key')
app.run(host='<IP_ADDRESS>', port=5000, ssl_context=context)

# app is a flask application wrapper that basically wraps run_simple
Exception Information:
INFO:app:Scheduler Started
WARNING:werkzeug: * Debugger is active!
INFO:werkzeug: * Debugger pin code: xxx-xxx-xxx
Exception in thread Thread-1:
Traceback (most recent call last):
  File "/.../python/2.7.10_2/Frameworks/Python.framework/Versions/2.7/lib/python2.7/threading.py", line 810, in __bootstrap_inner
    self.run()
  File "/.../python/2.7.10_2/Frameworks/Python.framework/Versions/2.7/lib/python2.7/threading.py", line 763, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/.../venv/lib/python2.7/site-packages/werkzeug/serving.py", line 646, in inner
    fd=fd).serve_forever()
  File "/.../venv/lib/python2.7/site-packages/werkzeug/serving.py", line 550, in make_server
    passthrough_errors, ssl_context, fd=fd)
  File "/.../venv/lib/python2.7/site-packages/werkzeug/serving.py", line 479, in __init__
    server_side=True)
  File "/.../python/2.7.10_2/Frameworks/Python.framework/Versions/2.7/lib/python2.7/ssl.py", line 352, in wrap_socket
    _context=self)
  File "/.../python/2.7.10_2/Frameworks/Python.framework/Versions/2.7/lib/python2.7/ssl.py", line 537, in __init__
    socket.__init__(self, _sock=sock._sock)
AttributeError: '_socket.socket' object has no attribute '_sock'

The changelog entry is unrelated to this.  The problem you are encountering was a regression that was caused by changes in the internal socket handling code in the server.  This is fixed in 0.11.2.  The commit that fixes it is 83c61916c584ef42ad7e67894853fde5ba8b9ad0.

Thanks!

@mitsuhiko
I'm still getting the same issue on 0.11.2

Are you sure that is the same traceback? Can you please provide exact information of environment, python version and everything that can help to track this down.

@mitsuhiko
In terms of the environment, pretty much described above, but I'm using Python 2.7.10 with a virtualenv. I'm running a huge flask application and the startup script has basically the code above.
context = ssl.SSLContext(ssl.PROTOCOL_SSLv23)
context.load_cert_chain('xxx.crt', 'xxx.key')
app.run(host='<IP_ADDRESS>', port=5000, ssl_context=context, threaded=False)

I'm using MAC OS X Mavericks (10.9) and python is installed via brew using:
brew install python --universal --framework
Here's the stack trace (I think it's exactly the same)
INFO:werkzeug: * Restarting with stat
INFO:apscheduler.scheduler:Scheduler started
WARNING:werkzeug: * Debugger is active!
INFO:werkzeug: * Debugger pin code: xxx-xxx-xxx
Exception in thread Thread-1:
Traceback (most recent call last):
  File "/.../python/2.7.10_2/Frameworks/Python.framework/Versions/2.7/lib/python2.7/threading.py", line 810, in __bootstrap_inner
    self.run()
  File "/.../python/2.7.10_2/Frameworks/Python.framework/Versions/2.7/lib/python2.7/threading.py", line 763, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/.../venv/lib/python2.7/site-packages/werkzeug/serving.py", line 653, in inner
    fd=fd).serve_forever()
  File "/.../venv/lib/python2.7/site-packages/werkzeug/serving.py", line 557, in make_server
    passthrough_errors, ssl_context, fd=fd)
  File "/.../venv/lib/python2.7/site-packages/werkzeug/serving.py", line 486, in __init__
    server_side=True)
  File "/.../python/2.7.10_2/Frameworks/Python.framework/Versions/2.7/lib/python2.7/ssl.py", line 352, in wrap_socket
    _context=self)
  File "/.../python/2.7.10_2/Frameworks/Python.framework/Versions/2.7/lib/python2.7/ssl.py", line 537, in __init__
    socket.__init__(self, _sock=sock._sock)
AttributeError: '_socket.socket' object has no attribute '_sock'

It works if I use gunicorn to startup the application instead of .run. Let me know if I can provide anything else that would be helpful. If I switch back to 0.10.4 it works.

I've also noticed exactly the same error on 0.11. But for me it helped to install 0.11.2. Thanks!

I'm running into the same issue trying to run a Flask server from within a Docker container. The container's python version is 2.7.10.
My flask code:
    context = ssl.SSLContext(ssl.PROTOCOL_SSLv23)
    context.load_cert_chain(os.environ['PATH_SSL_CERT'], os.environ['PATH_SSL_KEY'])
    app.run(ssl_context=context, host='<IP_ADDRESS>', debug = True, port = 2025)

The stack trace:
 * Restarting with stat
 * Debugger is active!
 * Debugger pin code: 247-483-355
Exception in thread Thread-1:
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/threading.py", line 810, in __bootstrap_inner
    self.run()
  File "/usr/local/lib/python2.7/threading.py", line 763, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/usr/local/lib/python2.7/site-packages/werkzeug/serving.py", line 653, in inner
    fd=fd).serve_forever()
  File "/usr/local/lib/python2.7/site-packages/werkzeug/serving.py", line 557, in make_server
    passthrough_errors, ssl_context, fd=fd)
  File "/usr/local/lib/python2.7/site-packages/werkzeug/serving.py", line 486, in __init__
    server_side=True)
  File "/usr/local/lib/python2.7/ssl.py", line 352, in wrap_socket
    _context=self)
  File "/usr/local/lib/python2.7/ssl.py", line 537, in __init__
    socket.__init__(self, _sock=sock._sock)
AttributeError: '_socket.socket' object has no attribute '_sock'

I'm experiencing the same issue with werkzeug 0.11.2, flask 0.10.1 and python 2.7.9 on Debian jessie.
Exception in thread Thread-1:
Traceback (most recent call last):
  File "/usr/lib/python2.7/threading.py", line 810, in __bootstrap_inner
    self.run()
  File "/usr/lib/python2.7/threading.py", line 763, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/usr/local/lib/python2.7/dist-packages/werkzeug/serving.py", line 653, in inner
    fd=fd).serve_forever()
  File "/usr/local/lib/python2.7/dist-packages/werkzeug/serving.py", line 557, in make_server
    passthrough_errors, ssl_context, fd=fd)
  File "/usr/local/lib/python2.7/dist-packages/werkzeug/serving.py", line 486, in __init__
    server_side=True)
  File "/usr/lib/python2.7/ssl.py", line 350, in wrap_socket
    _context=self)
  File "/usr/lib/python2.7/ssl.py", line 524, in __init__
    socket.__init__(self, _sock=sock._sock)
AttributeError: '_socket.socket' object has no attribute '_sock'

Also experiencing the same issue with same traceback, with Python 2.7.11 on CentOS 6.7, with Flask 0.10.1 and Werkzeug 0.11.2, using a virtualenv.

I'm also experiencing the same problem both on OS X 10.11.2 and Ubuntu 14.4.3 LTS. Here's the traceback and package info:
Error + Traceback
 * Restarting with stat
 * Debugger is active!
 * Debugger pin code: 257-405-669
Exception in thread Thread-1:
Traceback (most recent call last):
  File "/usr/local/lib/python2.7.10/lib/python2.7/threading.py", line 810, in __bootstrap_inner
    self.run()
  File "/usr/local/lib/python2.7.10/lib/python2.7/threading.py", line 763, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/srv/hubble/venv/lib/python2.7/site-packages/werkzeug/serving.py", line 653, in inner
    fd=fd).serve_forever()
  File "/srv/hubble/venv/lib/python2.7/site-packages/werkzeug/serving.py", line 557, in make_server
    passthrough_errors, ssl_context, fd=fd)
  File "/srv/hubble/venv/lib/python2.7/site-packages/werkzeug/serving.py", line 486, in __init__
    server_side=True)
  File "/usr/local/lib/python2.7.10/lib/python2.7/ssl.py", line 352, in wrap_socket
    _context=self)
  File "/usr/local/lib/python2.7.10/lib/python2.7/ssl.py", line 537, in __init__
    socket.__init__(self, _sock=sock._sock)
AttributeError: '_socket.socket' object has no attribute '_sock'

pip freeze output
cffi==1.4.1
cryptography==1.1.2
enum34==1.1.1
Flask==0.10
Flask-Uploads==0.2.0
idna==2.0
ipaddress==1.0.15
itsdangerous==0.24
Jinja2==2.8
MarkupSafe==0.23
pyasn1==0.1.9
pycparser==2.14
pyOpenSSL==0.15.1
six==1.10.0
Werkzeug==0.11.2
wheel==0.24.0

Setup code
#!venv/bin/python
from app import app
from flask import send_from_directory
import ssl

# Setup SSL certificate
# TO BE REMOVED IN PRODUCTION
context = ssl.SSLContext(ssl.PROTOCOL_TLSv1_2)
context.load_cert_chain(
	'/ssl-certs/cert.crt',
    '/ssl-certs/cert.key'
)

@app.route('/uploads/<path:path>')
def send_image(path):
	return send_from_directory('uploads', path)

# Debugging is enabled
# make sure this does
# not go into production
if __name__ == "__main__":
	app.run(
		host="<IP_ADDRESS>",
		port=int("5001"),
		debug=True,
		ssl_context=context
	)

I just pushed out a release which should fix this.

I can see it's merged with the master branch; safe to upgrade to 0.11.3 now?


Ability to interactively start and stop the profiler

I'm working on a patch for this (I added a com.insightfullogic.honest_profiler.core.control.Agent class with start/stop methods and a start=0|1 (defaults to 1) parameter for the agent).
I will send a pull request as soon as I finish writing the tests.

Fantastic - would be a great addition.

This is already implemented in PR #119


Succeeding with an LTFS format but not mounting. Suggestions?

Ubuntu 24.04 on Dell PowerEdge R740; Dell PERC H830 12Gb RAID SAS HBA
MagStor standalone deck using IBM LTO9 drive.
installer@xxxxxx:~/git/ltfs$ sudo /usr/local/bin/mkltfs -f -d /dev/st0
LTFS15000I Starting mkltfs, LTFS version <IP_ADDRESS> (Prelim), log level 2.
LTFS15041I Launched by "/usr/local/bin/mkltfs -f -d /dev/st0".
LTFS15042I This binary is built for Linux (x86_64).
LTFS15043I GCC version is 13.2.0.
LTFS17087I Kernel version: Linux version 6.8.0-45-generic (buildd@lcy02-amd64-115) (x86_64-linux-gnu-gcc-13 (Ubuntu 13.2.0-23ubuntu4) 13.2.0, GNU ld (GNU Binutils for Ubuntu) 2.42) #45-Ubuntu SMP PREEMPT_DYNAMIC Fri Aug 30 12:02:04 UTC 2024 i386.
LTFS17089I Distribution: PRETTY_NAME="Ubuntu 24.04.1 LTS".
LTFS17089I Distribution: DISTRIB_ID=Ubuntu.
LTFS15003I Formatting device '/dev/st0'.
LTFS15004I LTFS volume blocksize: 524288.
LTFS15005I Index partition placement policy: None.
LTFS11337I Update index-dirty flag (1) - NO_BARCODE (0x0x5eda9ce50dc0).
LTFS17085I Plugin: Loading "sg" tape backend.
LTFS30209I Opening a device through sg-ibmtape driver (/dev/st0).
LTFS30250I Opened the SCSI tape device 0.0.0.-1 (/dev/st0).
LTFS30207I Vendor ID is IBM     .
LTFS30208I Product ID is ULTRIUM-HH9     .
LTFS30214I Firmware revision is Q9E1.
LTFS30215I Drive serial is<PHONE_NUMBER>.
LTFS30285I The reserved buffer size of /dev/st0 is 262144.
LTFS30294I Setting up timeout values from RSOC.
LTFS17160I Maximum device block size is 1048576.
LTFS11330I Loading cartridge.
LTFS30252I Logical block protection is disabled.
LTFS11332I Load successful.
LTFS17157I Changing the drive setting to write-anywhere mode.
LTFS15049I Checking the medium (load).
LTFS30252I Logical block protection is disabled.
LTFS15010I Creating data partition b on SCSI partition 1.
LTFS15011I Creating index partition a on SCSI partition 0.
LTFS17165I Resetting the medium's capacity proportion.
LTFS11097I Partitioning the medium.
LTFS30263I MODESELECT returns Mode Parameters Rounded (-20101) /dev/st0.
LTFS11100I Writing label to partition b.
LTFS11278I Writing index to partition b.
LTFS30205I READ_ATTR (0x8c) returns -20501.
LTFS30263I READ_ATTR returns Invalid Field in CDB (-20501) /dev/st0.
LTFS30233I Cannot read attribute (-20501).
LTFS11336I The attribute does not exist. Ignore the expected error.
LTFS17235I Writing index of NO_BARCODE to b (Reason: Format, 0 files)<PHONE_NUMBER>.
LTFS17236I Wrote index of NO_BARCODE (Gen = 1, Part = b, Pos = 5,<PHONE_NUMBER>).
LTFS11337I Update index-dirty flag (0) - NO_BARCODE (0x0x5eda9ce50dc0).
LTFS11100I Writing label to partition a.
LTFS11278I Writing index to partition a.
LTFS30205I READ_ATTR (0x8c) returns -20501.
LTFS30263I READ_ATTR returns Invalid Field in CDB (-20501) /dev/st0.
LTFS30233I Cannot read attribute (-20501).
LTFS11336I The attribute does not exist. Ignore the expected error.
LTFS17235I Writing index of NO_BARCODE to a (Reason: Format, 0 files)<PHONE_NUMBER>.
LTFS17236I Wrote index of NO_BARCODE (Gen = 1, Part = a, Pos = 5,<PHONE_NUMBER>).
LTFS15013I Volume UUID is: 396598ec-22e9-4914-b38e-e34202ef6cc2.
LTFS15019I Volume capacity is 11712 GB.
LTFS30252I Logical block protection is disabled.
LTFS15024I Medium formatted successfully.
installer@xxxxxx:~/git/ltfs$ sudo /usr/local/bin/ltfs -o devname=/dev/st0 /mnt/ltfs9
8fc7 LTFS14000I LTFS starting, LTFS version <IP_ADDRESS> (Prelim), log level 2.
8fc7 LTFS14058I LTFS Format Specification version 2.4.0.
8fc7 LTFS14104I Launched by "/usr/local/bin/ltfs -o devname=/dev/st0 /mnt/ltfs9".
8fc7 LTFS14105I This binary is built for Linux (x86_64).
8fc7 LTFS14106I GCC version is 13.2.0.
8fc7 LTFS17087I Kernel version: Linux version 6.8.0-45-generic (buildd@lcy02-amd64-115) (x86_64-linux-gnu-gcc-13 (Ubuntu 13.2.0-23ubuntu4) 13.2.0, GNU ld (GNU Binutils for Ubuntu) 2.42) #45-Ubuntu SMP PREEMPT_DYNAMIC Fri Aug 30 12:02:04 UTC 2024 i386.
8fc7 LTFS17089I Distribution: PRETTY_NAME="Ubuntu 24.04.1 LTS".
8fc7 LTFS17089I Distribution: DISTRIB_ID=Ubuntu.
8fc7 LTFS14063I Sync type is "time", Sync time is 300 sec.
8fc7 LTFS17085I Plugin: Loading "sg" tape backend.
8fc7 LTFS17085I Plugin: Loading "unified" iosched backend.
8fc7 LTFS14095I Set the tape device write-anywhere mode to avoid cartridge ejection.
8fc7 LTFS30209I Opening a device through sg-ibmtape driver (/dev/st0).
8fc7 LTFS30250I Opened the SCSI tape device 0.0.0.-1 (/dev/st0).
8fc7 LTFS30207I Vendor ID is IBM     .
8fc7 LTFS30208I Product ID is ULTRIUM-HH9     .
8fc7 LTFS30214I Firmware revision is Q9E1.
8fc7 LTFS30215I Drive serial is<PHONE_NUMBER>.
8fc7 LTFS30285I The reserved buffer size of /dev/st0 is 262144.
8fc7 LTFS30294I Setting up timeout values from RSOC.
8fc7 LTFS17160I Maximum device block size is 1048576.
8fc7 LTFS11330I Loading cartridge.
8fc7 LTFS30252I Logical block protection is disabled.
8fc7 LTFS11332I Load successful.
8fc7 LTFS17157I Changing the drive setting to write-anywhere mode.
8fc7 LTFS11005I Mounting the volume from device.
8fc7 LTFS30252I Logical block protection is disabled.
8fc7 LTFS30216W Length mismatch is detected. (Act = 4096, resid = 0, resid_sense = 4016).
8fc7 LTFS12049E Cannot read: backend call failed (-21716).
8fc7 LTFS11174E Cannot read ANSI label: read failed (-21716).
8fc7 LTFS11170E Failed to read label (-21716) from partition 0.
8fc7 LTFS11009E Cannot read volume: failed to read partition labels.
8fc7 LTFS14013E Cannot mount the volume from device.
8fc7 LTFS30252I Logical block protection is disabled.
For some info about the SAS HBA:
installer@xxxxxxx:~/git/ltfs$ sudo dmesg | grep -i sas
[    2.265820] megasas: 07.727.03.00-rc1
[    2.266216] megaraid_sas 0000:18:00.0: BAR:0x1  BAR's base_addr(phys):0x000000009de00000  mapped virt_addr:0x000000004d8a5ced
[    2.266222] megaraid_sas 0000:18:00.0: FW now in Ready state
[    2.266225] megaraid_sas 0000:18:00.0: 63 bit DMA mask and 32 bit consistent mask
[    2.266752] megaraid_sas 0000:18:00.0: firmware supports msix	: (96)
[    2.270079] megaraid_sas 0000:18:00.0: requested/available msix 89/89 poll_queue 0
[    2.270103] megaraid_sas 0000:18:00.0: current msix/online cpus	: (89/88)
[    2.270106] megaraid_sas 0000:18:00.0: RDPQ mode	: (disabled)
[    2.270110] megaraid_sas 0000:18:00.0: Current firmware supports maximum commands: 928	 LDIO threshold: 0
[    2.274525] megaraid_sas 0000:18:00.0: Performance mode :Latency (latency index = 1)
[    2.274530] megaraid_sas 0000:18:00.0: FW supports sync cache	: No
[    2.274535] megaraid_sas 0000:18:00.0: megasas_disable_intr_fusion is called outbound_intr_mask:0x40000009
[    2.322978] megaraid_sas 0000:18:00.0: FW provided supportMaxExtLDs: 1	max_lds: 240
[    2.322989] megaraid_sas 0000:18:00.0: controller type	: MR(2048MB)
[    2.322996] megaraid_sas 0000:18:00.0: Online Controller Reset(OCR)	: Enabled
[    2.323001] megaraid_sas 0000:18:00.0: Secure JBOD support	: No
[    2.323006] megaraid_sas 0000:18:00.0: NVMe passthru support	: No
[    2.323010] megaraid_sas 0000:18:00.0: FW provided TM TaskAbort/Reset timeou: 0 secs/0 secs
[    2.323016] megaraid_sas 0000:18:00.0: JBOD sequence map support	: No
[    2.323020] megaraid_sas 0000:18:00.0: PCI Lane Margining support	: No
[    2.787924] megaraid_sas 0000:18:00.0: megasas_enable_intr_fusion is called outbound_intr_mask:0x40000000
[    2.787936] megaraid_sas 0000:18:00.0: INIT adapter done
[    2.787941] megaraid_sas 0000:18:00.0: JBOD sequence map is disabled megasas_setup_jbod_map 5796
[    2.791588] megaraid_sas 0000:18:00.0: pci id		: (0x1000)/(0x005d)/(0x1028)/(0x1f41)
[    2.791602] megaraid_sas 0000:18:00.0: unevenspan support	: yes
[    2.791608] megaraid_sas 0000:18:00.0: firmware crash dump	: no
[    2.791613] megaraid_sas 0000:18:00.0: JBOD sequence map	: disabled
[    2.791891] megaraid_sas 0000:18:00.0: Max firmware commands: 927 shared with default hw_queues = 88 poll_queues 0
[    2.791900] scsi host6: Avago SAS based MegaRAID driver
[    2.793608] megaraid_sas 0000:3b:00.0: BAR:0x1  BAR's base_addr(phys):0x00000000ab100000  mapped virt_addr:0x000000000f440297
[    2.793621] megaraid_sas 0000:3b:00.0: FW now in Ready state
[    2.793626] megaraid_sas 0000:3b:00.0: 63 bit DMA mask and 32 bit consistent mask
[    2.794571] megaraid_sas 0000:3b:00.0: firmware supports msix	: (96)
[    2.800418] megaraid_sas 0000:3b:00.0: requested/available msix 89/89 poll_queue 0
[    2.800470] megaraid_sas 0000:3b:00.0: current msix/online cpus	: (89/88)
[    2.800476] megaraid_sas 0000:3b:00.0: RDPQ mode	: (disabled)
[    2.800482] megaraid_sas 0000:3b:00.0: Current firmware supports maximum commands: 928	 LDIO threshold: 0
[    2.805948] megaraid_sas 0000:3b:00.0: Performance mode :Latency (latency index = 1)
[    2.805953] megaraid_sas 0000:3b:00.0: FW supports sync cache	: No
[    2.805958] megaraid_sas 0000:3b:00.0: megasas_disable_intr_fusion is called outbound_intr_mask:0x40000009
[    2.870998] megaraid_sas 0000:3b:00.0: FW provided supportMaxExtLDs: 1	max_lds: 64
[    2.871008] megaraid_sas 0000:3b:00.0: controller type	: MR(2048MB)
[    2.871014] megaraid_sas 0000:3b:00.0: Online Controller Reset(OCR)	: Enabled
[    2.871019] megaraid_sas 0000:3b:00.0: Secure JBOD support	: No
[    2.871023] megaraid_sas 0000:3b:00.0: NVMe passthru support	: No
[    2.871027] megaraid_sas 0000:3b:00.0: FW provided TM TaskAbort/Reset timeou: 0 secs/0 secs
[    2.871032] megaraid_sas 0000:3b:00.0: JBOD sequence map support	: No
[    2.871036] megaraid_sas 0000:3b:00.0: PCI Lane Margining support	: No
[    2.896739] megaraid_sas 0000:3b:00.0: megasas_enable_intr_fusion is called outbound_intr_mask:0x40000000
[    2.896751] megaraid_sas 0000:3b:00.0: INIT adapter done
[    2.896756] megaraid_sas 0000:3b:00.0: JBOD sequence map is disabled megasas_setup_jbod_map 5796
[    2.902201] megaraid_sas 0000:3b:00.0: pci id		: (0x1000)/(0x005d)/(0x1028)/(0x1f47)
[    2.902210] megaraid_sas 0000:3b:00.0: unevenspan support	: yes
[    2.902215] megaraid_sas 0000:3b:00.0: firmware crash dump	: no
[    2.902219] megaraid_sas 0000:3b:00.0: JBOD sequence map	: disabled
[    2.902406] megaraid_sas 0000:3b:00.0: Max firmware commands: 927 shared with default hw_queues = 88 poll_queues 0
[    2.902414] scsi host15: Avago SAS based MegaRAID driver

Two things that I'd observed: should one be using /dev/sgxx rather than
/dev/stxx? I'm afraid LTFS uses sg backend, not st... Another thing is the
fact the tape was formatted as a 12TB one, and not 18TB. Is that correct?
Tulio Lazarini
Soli Deo Gloria
On Thu, 26 Sept 2024, 18:03 smccue2019, @.***> wrote:

Ubuntu 24.04 on Dell PowerEdge R740; Dell PERC H830 12Gb RAID SAS HBA
MagStor standalone deck using IBM LTO9 drive.
@.:~/git/ltfs$ sudo /usr/local/bin/mkltfs -f -d /dev/st0
LTFS15000I Starting mkltfs, LTFS version <IP_ADDRESS> (Prelim), log level 2.
LTFS15041I Launched by "/usr/local/bin/mkltfs -f -d /dev/st0".
LTFS15042I This binary is built for Linux (x86_64).
LTFS15043I GCC version is 13.2.0.
LTFS17087I Kernel version: Linux version 6.8.0-45-generic
@.) (x86_64-linux-gnu-gcc-13 (Ubuntu
13.2.0-23ubuntu4) 13.2.0, GNU ld (GNU Binutils for Ubuntu) 2.42) #45
https://github.com/LinearTapeFileSystem/ltfs/issues/45-Ubuntu SMP
PREEMPT_DYNAMIC Fri Aug 30 12:02:04 UTC 2024 i386.
LTFS17089I Distribution: PRETTY_NAME="Ubuntu 24.04.1 LTS".
LTFS17089I Distribution: DISTRIB_ID=Ubuntu.
LTFS15003I Formatting device '/dev/st0'.
LTFS15004I LTFS volume blocksize: 524288.
LTFS15005I Index partition placement policy: None.
LTFS11337I Update index-dirty flag (1) - NO_BARCODE (0x0x5eda9ce50dc0).
LTFS17085I Plugin: Loading "sg" tape backend.
LTFS30209I Opening a device through sg-ibmtape driver (/dev/st0).
LTFS30250I Opened the SCSI tape device 0.0.0.-1 (/dev/st0).
LTFS30207I Vendor ID is IBM .
LTFS30208I Product ID is ULTRIUM-HH9 .
LTFS30214I Firmware revision is Q9E1.
LTFS30215I Drive serial is<PHONE_NUMBER>.
LTFS30285I The reserved buffer size of /dev/st0 is 262144.
LTFS30294I Setting up timeout values from RSOC.
LTFS17160I Maximum device block size is 1048576.
LTFS11330I Loading cartridge.
LTFS30252I Logical block protection is disabled.
LTFS11332I Load successful.
LTFS17157I Changing the drive setting to write-anywhere mode.
LTFS15049I Checking the medium (load).
LTFS30252I Logical block protection is disabled.
LTFS15010I Creating data partition b on SCSI partition 1.
LTFS15011I Creating index partition a on SCSI partition 0.
LTFS17165I Resetting the medium's capacity proportion.
LTFS11097I Partitioning the medium.
LTFS30263I MODESELECT returns Mode Parameters Rounded (-20101) /dev/st0.
LTFS11100I Writing label to partition b.
LTFS11278I Writing index to partition b.
LTFS30205I READ_ATTR (0x8c) returns -20501.
LTFS30263I READ_ATTR returns Invalid Field in CDB (-20501) /dev/st0.
LTFS30233I Cannot read attribute (-20501).
LTFS11336I The attribute does not exist. Ignore the expected error.
LTFS17235I Writing index of NO_BARCODE to b (Reason: Format, 0 files)
1097004408.
LTFS17236I Wrote index of NO_BARCODE (Gen = 1, Part = b, Pos = 5,
1097004408).
LTFS11337I Update index-dirty flag (0) - NO_BARCODE (0x0x5eda9ce50dc0).
LTFS11100I Writing label to partition a.
LTFS11278I Writing index to partition a.
LTFS30205I READ_ATTR (0x8c) returns -20501.
LTFS30263I READ_ATTR returns Invalid Field in CDB (-20501) /dev/st0.
LTFS30233I Cannot read attribute (-20501).
LTFS11336I The attribute does not exist. Ignore the expected error.
LTFS17235I Writing index of NO_BARCODE to a (Reason: Format, 0 files)
1097004408.
LTFS17236I Wrote index of NO_BARCODE (Gen = 1, Part = a, Pos = 5,
1097004408).
LTFS15013I Volume UUID is: 396598ec-22e9-4914-b38e-e34202ef6cc2.
LTFS15019I Volume capacity is 11712 GB.
LTFS30252I Logical block protection is disabled.
LTFS15024I Medium formatted successfully.
@.:~/git/ltfs$ sudo /usr/local/bin/ltfs -o devname=/dev/st0
/mnt/ltfs9
8fc7 LTFS14000I LTFS starting, LTFS version <IP_ADDRESS> (Prelim), log level 2.
8fc7 LTFS14058I LTFS Format Specification version 2.4.0.
8fc7 LTFS14104I Launched by "/usr/local/bin/ltfs -o devname=/dev/st0
/mnt/ltfs9".
8fc7 LTFS14105I This binary is built for Linux (x86_64).
8fc7 LTFS14106I GCC version is 13.2.0.
8fc7 LTFS17087I Kernel version: Linux version 6.8.0-45-generic
@.) (x86_64-linux-gnu-gcc-13 (Ubuntu
13.2.0-23ubuntu4) 13.2.0, GNU ld (GNU Binutils for Ubuntu) 2.42) #45
https://github.com/LinearTapeFileSystem/ltfs/issues/45-Ubuntu SMP
PREEMPT_DYNAMIC Fri Aug 30 12:02:04 UTC 2024 i386.
8fc7 LTFS17089I Distribution: PRETTY_NAME="Ubuntu 24.04.1 LTS".
8fc7 LTFS17089I Distribution: DISTRIB_ID=Ubuntu.
8fc7 LTFS14063I Sync type is "time", Sync time is 300 sec.
8fc7 LTFS17085I Plugin: Loading "sg" tape backend.
8fc7 LTFS17085I Plugin: Loading "unified" iosched backend.
8fc7 LTFS14095I Set the tape device write-anywhere mode to avoid cartridge
ejection.
8fc7 LTFS30209I Opening a device through sg-ibmtape driver (/dev/st0).
8fc7 LTFS30250I Opened the SCSI tape device 0.0.0.-1 (/dev/st0).
8fc7 LTFS30207I Vendor ID is IBM .
8fc7 LTFS30208I Product ID is ULTRIUM-HH9 .
8fc7 LTFS30214I Firmware revision is Q9E1.
8fc7 LTFS30215I Drive serial is<PHONE_NUMBER>.
8fc7 LTFS30285I The reserved buffer size of /dev/st0 is 262144.
8fc7 LTFS30294I Setting up timeout values from RSOC.
8fc7 LTFS17160I Maximum device block size is 1048576.
8fc7 LTFS11330I Loading cartridge.
8fc7 LTFS30252I Logical block protection is disabled.
8fc7 LTFS11332I Load successful.
8fc7 LTFS17157I Changing the drive setting to write-anywhere mode.
8fc7 LTFS11005I Mounting the volume from device.
8fc7 LTFS30252I Logical block protection is disabled.
8fc7 LTFS30216W Length mismatch is detected. (Act = 4096, resid = 0,
resid_sense = 4016).
8fc7 LTFS12049E Cannot read: backend call failed (-21716).
8fc7 LTFS11174E Cannot read ANSI label: read failed (-21716).
8fc7 LTFS11170E Failed to read label (-21716) from partition 0.
8fc7 LTFS11009E Cannot read volume: failed to read partition labels.
8fc7 LTFS14013E Cannot mount the volume from device.
8fc7 LTFS30252I Logical block protection is disabled.
For some info about the SAS HBA:
@.***:~/git/ltfs$ sudo dmesg | grep -i sas
[ 2.265820] megasas: 07.727.03.00-rc1
[ 2.266216] megaraid_sas 0000:18:00.0: BAR:0x1 BAR's
base_addr(phys):0x000000009de00000 mapped virt_addr:0x000000004d8a5ced
[ 2.266222] megaraid_sas 0000:18:00.0: FW now in Ready state
[ 2.266225] megaraid_sas 0000:18:00.0: 63 bit DMA mask and 32 bit
consistent mask
[ 2.266752] megaraid_sas 0000:18:00.0: firmware supports msix : (96)
[ 2.270079] megaraid_sas 0000:18:00.0: requested/available msix 89/89
poll_queue 0
[ 2.270103] megaraid_sas 0000:18:00.0: current msix/online cpus : (89/88)
[ 2.270106] megaraid_sas 0000:18:00.0: RDPQ mode : (disabled)
[ 2.270110] megaraid_sas 0000:18:00.0: Current firmware supports maximum
commands: 928 LDIO threshold: 0
[ 2.274525] megaraid_sas 0000:18:00.0: Performance mode :Latency (latency
index = 1)
[ 2.274530] megaraid_sas 0000:18:00.0: FW supports sync cache : No
[ 2.274535] megaraid_sas 0000:18:00.0: megasas_disable_intr_fusion is
called outbound_intr_mask:0x40000009
[ 2.322978] megaraid_sas 0000:18:00.0: FW provided supportMaxExtLDs: 1
max_lds: 240
[ 2.322989] megaraid_sas 0000:18:00.0: controller type : MR(2048MB)
[ 2.322996] megaraid_sas 0000:18:00.0: Online Controller Reset(OCR) :
Enabled
[ 2.323001] megaraid_sas 0000:18:00.0: Secure JBOD support : No
[ 2.323006] megaraid_sas 0000:18:00.0: NVMe passthru support : No
[ 2.323010] megaraid_sas 0000:18:00.0: FW provided TM TaskAbort/Reset
timeou: 0 secs/0 secs
[ 2.323016] megaraid_sas 0000:18:00.0: JBOD sequence map support : No
[ 2.323020] megaraid_sas 0000:18:00.0: PCI Lane Margining support : No
[ 2.787924] megaraid_sas 0000:18:00.0: megasas_enable_intr_fusion is
called outbound_intr_mask:0x40000000
[ 2.787936] megaraid_sas 0000:18:00.0: INIT adapter done
[ 2.787941] megaraid_sas 0000:18:00.0: JBOD sequence map is disabled
megasas_setup_jbod_map 5796
[ 2.791588] megaraid_sas 0000:18:00.0: pci id :
(0x1000)/(0x005d)/(0x1028)/(0x1f41)
[ 2.791602] megaraid_sas 0000:18:00.0: unevenspan support : yes
[ 2.791608] megaraid_sas 0000:18:00.0: firmware crash dump : no
[ 2.791613] megaraid_sas 0000:18:00.0: JBOD sequence map : disabled
[ 2.791891] megaraid_sas 0000:18:00.0: Max firmware commands: 927 shared
with default hw_queues = 88 poll_queues 0
[ 2.791900] scsi host6: Avago SAS based MegaRAID driver
[ 2.793608] megaraid_sas 0000:3b:00.0: BAR:0x1 BAR's
base_addr(phys):0x00000000ab100000 mapped virt_addr:0x000000000f440297
[ 2.793621] megaraid_sas 0000:3b:00.0: FW now in Ready state
[ 2.793626] megaraid_sas 0000:3b:00.0: 63 bit DMA mask and 32 bit
consistent mask
[ 2.794571] megaraid_sas 0000:3b:00.0: firmware supports msix : (96)
[ 2.800418] megaraid_sas 0000:3b:00.0: requested/available msix 89/89
poll_queue 0
[ 2.800470] megaraid_sas 0000:3b:00.0: current msix/online cpus : (89/88)
[ 2.800476] megaraid_sas 0000:3b:00.0: RDPQ mode : (disabled)
[ 2.800482] megaraid_sas 0000:3b:00.0: Current firmware supports maximum
commands: 928 LDIO threshold: 0
[ 2.805948] megaraid_sas 0000:3b:00.0: Performance mode :Latency (latency
index = 1)
[ 2.805953] megaraid_sas 0000:3b:00.0: FW supports sync cache : No
[ 2.805958] megaraid_sas 0000:3b:00.0: megasas_disable_intr_fusion is
called outbound_intr_mask:0x40000009
[ 2.870998] megaraid_sas 0000:3b:00.0: FW provided supportMaxExtLDs: 1
max_lds: 64
[ 2.871008] megaraid_sas 0000:3b:00.0: controller type : MR(2048MB)
[ 2.871014] megaraid_sas 0000:3b:00.0: Online Controller Reset(OCR) :
Enabled
[ 2.871019] megaraid_sas 0000:3b:00.0: Secure JBOD support : No
[ 2.871023] megaraid_sas 0000:3b:00.0: NVMe passthru support : No
[ 2.871027] megaraid_sas 0000:3b:00.0: FW provided TM TaskAbort/Reset
timeou: 0 secs/0 secs
[ 2.871032] megaraid_sas 0000:3b:00.0: JBOD sequence map support : No
[ 2.871036] megaraid_sas 0000:3b:00.0: PCI Lane Margining support : No
[ 2.896739] megaraid_sas 0000:3b:00.0: megasas_enable_intr_fusion is
called outbound_intr_mask:0x40000000
[ 2.896751] megaraid_sas 0000:3b:00.0: INIT adapter done
[ 2.896756] megaraid_sas 0000:3b:00.0: JBOD sequence map is disabled
megasas_setup_jbod_map 5796
[ 2.902201] megaraid_sas 0000:3b:00.0: pci id :
(0x1000)/(0x005d)/(0x1028)/(0x1f47)
[ 2.902210] megaraid_sas 0000:3b:00.0: unevenspan support : yes
[ 2.902215] megaraid_sas 0000:3b:00.0: firmware crash dump : no
[ 2.902219] megaraid_sas 0000:3b:00.0: JBOD sequence map : disabled
[ 2.902406] megaraid_sas 0000:3b:00.0: Max firmware commands: 927 shared
with default hw_queues = 88 poll_queues 0
[ 2.902414] scsi host15: Avago SAS based MegaRAID driver
—
Reply to this email directly, view it on GitHub
https://github.com/LinearTapeFileSystem/ltfs/issues/483, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADAYKVBJ4XWAAAS4ZUOPYG3ZYRZC3AVCNFSM6AAAAABO525IC2VHI2DSMVQWIX3LMV43ASLTON2WKOZSGU2TCNJSG4ZDMOI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

I came to add that I had built the code adding switches "--enable-buggy-ifs --enable-lintape" to the configure call.
Hello, thank you for responding!
I believe the reflection of a 12TB volume is because my blank media is an LTO8 cartridge.
Per your suggestion I reran mkltfs and lfts using sg0. Same results and line by line messaging as resulted from using st0.
[I've come from CentOS where the st devices were used.]

It looks your HBA MegaRAID might not support transfer length count at all. I believe this HBA only supports block device, but supports RAID. But I'm not sure this supports streaming device correctly.
8fc7 LTFS11005I Mounting the volume from device.
8fc7 LTFS30252I Logical block protection is disabled.
8fc7 LTFS30216W Length mismatch is detected. (Act = 4096, resid = 0, resid_sense = 4016).

My recommendation is to use HBA that IBM says supported. Please visit the SSIC provided from IBM and choose a correct HBA.

Hi @TulioLazarini , Sorry for my missing something.
From the lines like below, I think --enable-buggy-ifs highly likely works as @smccue2019 said.
8fc7 LTFS30216W Length mismatch is detected. (Act = 4096, resid = 0, resid_sense = 4016).

See also, https://github.com/LinearTapeFileSystem/ltfs/issues/369#issuecomment-1951539217.


*.azmk8s.io is not correct for Firewall rules

A wildcard inside a name only reflects a single label and the wildcard can only be leftmost. While the actual API Server is on <uniqueid>.hcp.<region>.azmk8s.io.
Wildcard definition should be updated in the docs to .hcp..azmk8s.io

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

ID: a38439d0-0125-3445-1c0a-a03b940e315d
Version Independent ID: c6436a35-94b9-6396-3b13-9291f0a17b21
Content: Restrict egress traffic in Azure Kubernetes Service (AKS)
Content Source: articles/aks/limit-egress-traffic.md
Service: container-service
GitHub Login: @iainfoulds
Microsoft Alias: iainfou

Thanks for the feedback! We are currently investigating and will update you shortly.

After off-line discussions with PM team, product feedback or potential issues while this feature is in preview should be logged against the AKS project itself - https://github.com/azure/aks/issues. As changes are need in the docs, we'll update accordingly.
For now, @MicahMcKittrick-MSFT @Karishma-Tiwari-MSFT  #please-close