Large datasets in R / Nvidia H100s cause unexpected memory overflow error

We are encountering an issue training on H100s in R that occurs only after the dataset exceeds a certain degree of size. The interesting part is the stack trace ... clearly the data set we're building is nowhere near the 80GB of VRAM in the GPU, but it attempts to allocate some obscene amount of memory that alludes to some kind of integer overflow in the memory allocation.
I'll note that this does not happen when I use an identical environment with A100 GPUs instead.
I'm at a loss for how to debug this further, so any help would be greatly appreciated!

OS: Rocky 9.1
Driver Version: 530.30.02
CUDA Version: 12.1
R Version: 4.2.3
XGBoost Version: 1.7.6, also reproduced on 2.0 nightly build

Reproducible code:
require(xgboost)

params <- list(
    tree_method="gpu_hist",
    eta=0.01,
    max_depth=4
)

# The below code runs fine with n=2e6, but fails with n=3e6
n <- 3e6
X <- matrix(rnorm(1000 * n), ncol=1000)
y <- rnorm(n)
wt <- runif(n)
dmat <- xgb.DMatrix(X, label=y, weight=wt)
bst <- xgb.train(params, dmat, nround=100, watchlist=list(train=dmat), verbose=TRUE, print_every_n=10)

Resulting Stacktrace:
  [18:33:59] ../src/tree/updater_gpu_hist.cu:802: Exception in gpu_hist: [18:33:59] ../src/c_api/../data/../common/device_helpers.cuh:431: Memory allocation error on worker 0: Caching allocator
- Free memory:<PHONE_NUMBER>0
- Requested memory:<PHONE_NUMBER>3698093311

Stack trace:
  [bt] (0) ~/rlib/xgboost/libs/xgboost.so(+0x58c8a3) [0x7fe50c06c8a3]
  [bt] (1) ~/rlib/xgboost/libs/xgboost.so(dh::detail::ThrowOOMError(std::string const&, unsigned long)+0x381) [0x7fe50c071db1]
  [bt] (2) ~/rlib/xgboost/libs/xgboost.so(+0x59b984) [0x7fe50c07b984]
  [bt] (3) ~/rlib/xgboost/libs/xgboost.so(thrust::detail::normal_iterator<thrust::device_ptr<float> > thrust::cuda_cub::inclusive_scan_by_key<thrust::detail::execute_with_allocator<dh::detail::XGBCachingDeviceAllocatorImpl<char>&, thrust::cuda_cub::execute_on_stream_base>, thrust::detail::normal_iterator<thrust::device_ptr<xgboost::

Enter a frame number, or 0 to exit

1: xgb.train(params, dmat, nround = 100, watchlist = list(train = dmat), verbose = TRUE, print_every_n = 10)
2: xgb.iter.update(bst$handle, dtrain, iteration - 1, obj)

Thank you for raising the issue, let me debug this next week.

Interesting, I couldn't reproduce it in other setups either. Will try to access a h100 instance.

Reproduced on h100. Will debug it.

thrust::inclusive_scan_by_key is overflowing due to size larger than INT_MAX.


fix(@angular-devkit/build-angular): IE11 errors when using scripts an…

…d differential loading
Invert the builds so that es2015 scripts output don't override the es5 version.
Fixes #14777

Seems like 3rdpartylicenses.txt increased by 11.08KB.

caretaker: the size increase in licenses is expected because now it includes all licenses used in es5 bundles, including the extra polyfills.

@alan-agius4 - Can you fix the size test. The size change seems ok.

AFAIK, the size check will be fixed automaticlly once the PR gets merged.


c++ errors while building erizoAPI after update node

Hi, i am trying to nstallErizo script and got such errors:
In file included from ../OneToManyProcessor.h:9:0,
from ../WebRtcConnection.h:7,
from ../addon.cc:5:
../ExternalInput.h:16:46: error: expected class-name before ‘{’ token
class ExternalInput: public node::ObjectWrap {
^
../ExternalInput.h:29:42: error: ‘Arguments’ in namespace ‘v8’ does not name a type
static v8::Handlev8::Value New(const v8::Arguments& args);
^
../ExternalInput.h:29:57: error: ISO C++ forbids declaration of ‘args’ with no type [-fpermissive]
static v8::Handlev8::Value New(const v8::Arguments& args);
^
../ExternalInput.h:34:44: error: ‘Arguments’ in namespace ‘v8’ does not name a type
static v8::Handlev8::Value close(const v8::Arguments& args);
^
../ExternalInput.h:34:59: error: ISO C++ forbids declaration of ‘args’ with no type [-fpermissive]
static v8::Handlev8::Value close(const v8::Arguments& args);
... etc
gyp ERR! build error
gyp ERR! stack Error: make failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/lib/node_modules/node-gyp/lib/build.js:276:23)
gyp ERR! stack     at emitTwo (events.js:88:13)
gyp ERR! stack     at ChildProcess.emit (events.js:173:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:201:12)
gyp ERR! System Linux 3.19.0-39-generic
gyp ERR! command "/usr/local/bin/node" "/usr/bin/node-gyp" "rebuild"
gyp ERR! cwd /var/www/virt-chat.my/node_server/licode/erizoAPI
gyp ERR! node -v v5.2.0
gyp ERR! node-gyp -v v3.2.1
gyp ERR! not ok

Licode support only node v0.10

Do you have plans to support higher versions?

Any news about it?

We migrated erizoAPI to NAN so you should at least be able to compile erizoAPI. We still ship with node v0.10 atm and can't give you a timeframe for library updates, sorry.


Check for mandatory elements in the model structure.

Reported by cbertsch on 8 Jan 2017 08:06 UTC
The FMI Compliance Checker 2.0.3 does currently not check for mandatory elements of the model structure in the modeldescription.xml
p.58 of the FMI 2.0 Standard: Outputs: Ordered list of all outputs, in other words a list of ScalarVariable indices where every corresponding ScalarVariable must have causality = "output" (and every variable with causality=”output” must be listed here).
Currently it is not checked, if the "outputs" are present in model structure. If the outputs are defined in the model structure, it is not checked, if the provided index really corresponds to an output. It is not checked if defined dependencies follow the rules defined on p. 61 of the FMI 2.0 standard.
E.g. instead of  the following modeldescription.xml (part)
...

<ModelVariables>
  <ScalarVariable name="a_" valueReference="0" causality="input" variability="continuous" initial="approx">
    <Real start="1"/>
  </ScalarVariable>
  <ScalarVariable name="b_" valueReference="1" causality="input" variability="continuous" initial="approx">
    <Real start="2"/>
  </ScalarVariable>
  <ScalarVariable name="c_" valueReference="2" causality="output" variability="continuous" initial="calculated">
    <Real />
  </ScalarVariable>
</ModelVariables>

<ModelStructure>
  <Outputs>
    <Unknown index="3" dependencies="1 2"/>
  </Outputs>
</ModelStructure>

...

also
<ModelStructure>
</ModelStructure>

or
<ModelStructure>
  <Outputs>
    <Unknown index="1" dependencies="2 3"/>
  </Outputs>
</ModelStructure>

are accepted by the current compliance checker.
The same as for outputs is also true for the derivatives.

Migrated-From: https://trac.fmi-standard.org/ticket/400

Comment by cbertsch on 3 May 2017 19:36 UTC
Additionally, the compliance checker currently does not check, if initial unkwnowns are defined according to p.60 of the FMI 2.0 specification (e.g. for varibles causality = "output" and (initial="approx" or "calculated")


Android build failing on windows due to missing NDK installation

Bug description
When I am trying to build unity for android platform. It involves two phases. First I try to export the android code and then I build the android APK. During the second phase I get the error regarding the ndk.
This is my workflow:
      - name: Build Unity
        uses<EMAIL_ADDRESS>        env:
          UNITY_EMAIL: ${{ secrets.UNITY_USERNAME }}
          UNITY_PASSWORD: ${{ secrets.UNITY_PASSWORD }}
          UNITY_SERIAL: ${{ secrets.UNITY_PRO_SERIAL_KEY }}
        with:
          unityVersion: 2020.3.42f1
          targetPlatform: Android
          projectPath: andromeda
          buildName: myracle
          buildsPath: andromeda/Builds
          buildMethod: UnityBuilderAction.Build.DoBuildAndroidLibrary
          customImage: unityci/editor:windows-2020.3.42f1-android-3.0.0

      - name: Get current time
        uses<EMAIL_ADDRESS>        id: current-time
        with:
          format: YYYYWd

      - name: Build the Staging apk for Distribution
        working-directory: ./myracle
        run: flutter build apk --target=lib/main_staging.dart --flavor=staging --release --build-number=${{ steps.current-time.outputs.formattedTime }}
        env:
          ANDROID_KEYSTORE_PASSWORD_MYRACLE_STAGING: ${{ secrets.ANDROID_KEYSTORE_PASSPHRASE_STAGING }}

It fails during the Build the Staging apk for Distribution steps with this error
WARNING: [Processor] Library 'C:\a\myracle-andromeda\myracle-andromeda\myracle\android\unityLibrary\libs\androidx_core_1.3.0.jar' contains references to both AndroidX and old support library. This seems like the library is partially migrated. Jetifier will try to rewrite the library anyway.
 Example of androidX reference: 'androidx/versionedparcelable/VersionedParcel'
 Example of support library reference: 'android/support/v4/app/RemoteActionCompatParcelizer'
Note: C:\a\myracle-andromeda\myracle-andromeda\myracle\android\unityLibrary\src\main\java\com\unity3d\player\UnityPlayerActivity.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
[CXX1102] Location specified by ndk.dir (C:/UnityEditor/2020.3.42f1/Editor/Data/PlaybackEngines/AndroidPlayer/NDK) did not contain a valid NDK and couldn't be used

FAILURE: Build failed with an exception.

* Where:
Build file 'C:\a\myracle-andromeda\myracle-andromeda\myracle\android\unityLibrary\build.gradle' line: 87

* What went wrong:
Execution failed for task ':unityLibrary:BuildIl2CppTask'.
> NDK is not installed

You can see the full logs here
Expected behavior
I should be able to build the android APK
Additional details
Building on Windows 8 core for android with unity version 2020.3.42lf.
I am also using flutter for android and iOS development

I think I am facing the same issue as what @danyow was facing here

This is happening because the unity builder step runs inside of a container. The step afterwards is running on the host which doesn't have the tooling installed. Looking at the issue you referenced it seems to be the same issue. You'd need to find a way to point it to the host's NDK or somehow run the build inside the container with the build tools installed (likely a custom container). As such this isn't a bug with the action, it just inherently runs this way.

@AndrewKahr can please help me with running my other steps in the same container, any info is really appreciated.


official support for ComfyUI please

This project is awesome. Can we get official support for ComfyUI please?

@ShenZhang-Shin what can I do to help you setup ComfyUI?

https://github.com/blepping/comfyui_jankhidiffusion
This reproduction for comfyui is good.


Test sending-email feature

Based on #2013, developed in https://github.com/fractal-analytics-platform/fractal-server/tree/2013-feature-request-inform-admin-when-user-signs-up.
Minimal example of SMTP container: docker run --name=mailhog -p 2525:1025 -p 8025:8025 mailhog/mailhog
Minimal example of reading email curl http://localhost:8025/api/v2/messages
Minimal example of sending email

import smtplib

sender = "sender@localhost"
recipient =<EMAIL_ADDRESS>password = "fakepassword"

with smtplib.SMTP("localhost", 2525) as server:
    server.set_debuglevel(1)
    server.ehlo()
    # server.starttls()   # This fails on mailhog
    server.login(
        sender,
        password=password,
        initial_response_ok=True,
    )
    server.sendmail(
        from_addr=sender,
        to_addrs=recipient,
        msg="\nMessage contents",
    )

Expected behavior

Before any login, there is no email
After the first oauth login, there is one email
After the second oauth login, there is still only one email

closed by #2151


"Certificate has expired" when activating the Expo schema

Description of the bug
There is a known issue related to certificates in the newer vscode. This might result in the following error:

Workarounds
There are currently two workarounds to avoid this issue, until vscode fixes the issue. After applying either of the workarounds, simply restart your vscode and the error should be gone.
From the vscode team
Currently, the recommended workaround from the vscode team would be to add "http.systemCertificates": false in your configuration. This would avoid the faulty root certificate and successfully pull in the schema.
After the schema was activated successfully, you can remove this option. We cache the schema to minimize the API calls.
With the Expo schema cache
If you aren't comfortable with disabling the system certificates, you can work around this issue by pre-populating the schema cache. This would be required for every major Expo SDK version your project(s) use.
$ expo init ./temporary --template expo-template-blank@44
$ cd temporary
$ expo doctor
$ cd ..
$ npx rimraf temporary

This creates an empty project using Expo SDK 44, we only need to execute $ expo doctor inside of that to download the Expo schema outside vscode. After you execute this, the schema is written to:

If you use other SDK versions, you can replace 44 with any major version you use.

# Linux
~/.cache/expo/schema-44.0.0.json

# MacOS
~/.expo/cache/schema-44.0.0.json

# Windows
%AppData%\Local\Expo\schema-44.0.0.json

Additional context

https://github.com/expo/vscode-expo/issues/81
https://github.com/expo/vscode-expo/issues/67
https://github.com/microsoft/vscode/pull/137241
https://github.com/microsoft/vscode/issues/136787
https://github.com/microsoft/vscode/issues/138132

Fixed in vscode versions 1.66+


fixes to build minivm on linux

This PR fixes the new-cg branch to do the following 4 things.

Use stdarg.h for the stdarg stuff in common/buffer.h
Remove two SPALL_FORCEINLINEs that break on linux
Use int formats in inttypes.h where needed.
Wrap default/case that decl's variables.
Use the_type_t blah[0] instead of the_type_t name[] for union of flexable array members.

Thanks for giving it a look.

thanks


Outdated documentation in the architecture pdf

The section "Extension Lifecyle" contains outdated API calls:
https://esri.github.io/cityengine-sdk/arcgis_prt_architecture.pdf
The version query functions have changed to getVersionMajor/Minor.

Fixed


Add Ray Wunderlich/David Okun tutorials to the Kitura Tutorials page

Added the new Tutorials made by David Okun to the page, and also added a card effect to the items to make them a little easier to distinguish. Also introduces new sections, with Spotlight and Backend Tutorials being the first to be added.
The idea I have in mind is that as tutorials are added, we can create new sections to put the tutorials in to keep a coherent list. The use case would be "I want to use Stencil" so they would go to our Stencil section on the Tutorials page.


Force Report Author to Choose a Milestone/Task or Acknowledge a Milestone/Task was not Addressed

Force report authors to either (1) choose one or more milestones/tasks for the engagement or (2) acknowledge milestones/tasks were not addressed during the engagement with the principal(s).
@gjvoosten @VassilIordanov Any ideas on how this could look? The business owners would like suggestions.
Business owners want to identify which engagements do not support the effort.
Reference item 107

I suggest that when a user is submitting a report without any poams PoAMs, a message appears stating something like:
"You are about to submit a report that does not reference any PoAM. In order to submit your report, you are required to acknowledge that the engagement did not address a PoAM"
With 2 buttons below:
"I acknowledge no PoAM" and "Keep editing report"

@VassilIordanov That's a good suggestion.  The absence of a PoAM assigned to a report will indicate the report author acknowledged not having a PoAM.

It was communicated by the users that this feature is desirable.
It also fits in the discussion of having both errors and warnings associated with actions on a page.
In this case, not having a referenced tasks should result in:

a warning (should not prevent a save action, but will prevent a submit)
an error (should prevent a submit, unless acknowledged)
an error (should prevent an approve, unless acknowledged)
not sure what to do with the acknowledged state, maybe we can get away with not persisting it anywhere.


Source link support

Is your feature request related to a problem? Please describe.
While debugging, even though Visual Studio added decompilation support, it seems Visual Studio does not want to step into the internals of the DataSync libraries.
Describe the solution you'd like
Support for https://github.com/dotnet/sourcelink so that Visual Studio automatically can find and debug the source code of the DataSync libraries
Describe alternatives you've considered
Using https://github.com/RicoSuter/DNT with switch-to-projects to manually include the source code to step through the code.
Additional context
Add any other context or screenshots about the feature request here.

I have not used sourcelink, but the instructions seem pretty straight forward.  Will try and get this in for the next milestone.

Wow, that’s fast! Great, thank you!


Blood graph

Looks good to me. The option to generate a trace could be a dynamic switch instead of compile-time, but I think how it is now is consistent with our other tracers.


Trouble converting to hex

related: #246
I think I'm totally misunderstanding something here. I can't figure out how to convert colors defined in OKLCH to hex. It seems to me this should do it, but it just ignores the requested format (no matter which format I try).
new Color('oklch', [0.5, 0.17, 60], 1).toGamut({space: 'srgb'}).toString({format: 'hex'})
>> "oklch(50.183% 0.12747 52.941)"

Using the to() function instead works for most formats, but not for hex:
new Color('oklch', [0.5, 0.17, 60], 1).toGamut({space: 'srgb'}).to('hsl').toString();
>> "hsl(29.068 100% 30.171%)"

new Color('oklch', [0.5, 0.17, 60], 1).toGamut({space: 'srgb'}).to('hex').toString();
>> Uncaught TypeError: No color space found with id = "hex"

I've tried a number of other approaches, both with and without a toGamut() call, but I think I'm fundamentally misunderstanding something about how or when the library converts between color spaces or something.

okay, this works:
new Color('oklch(50% 0.17 60)').toGamut({space: 'srgb'}).to('srgb').toString({format: 'hex'})
>> "#9a4b00"

I think I needed to map the gamut, then convert to srgb color space before I can format as hex. Am I understanding that correctly?
This issue can probably be closed

Your original example should work with the dev branch, which will soon be v0.6.0. Could you try it and let us know if it doesn’t?

do I need to pull down the repo and compile to access that, or is there a bundled version available somewhere for quicker access?

You can just import directly from the colorjs.io website as described here, that always uses the dev branch: https://colorjs.io/get/

When's the release? Format is indeed broken in 0.5.2 and using the CDN import works great.

When's the release? Format is indeed broken in 0.5.2 and using the CDN import works great. It'd be great if I can install pre-release versions via npm too, the suggested way doesn't work for me.

Hopefully very soon. #537 has the most up to date information on this.

I would like to point out the hex output can produce a shorthand hex (length of 3 instead of 6) if the notation allows it to be presented that way, which are not allowed on color input types.
Perhaps the .toFormat() method would benefit from an option to explicitly produce shorthand of longhand notations of outputs.
Otherwise users could benefit from a snippet like this:
const longhex = '#123'.split('').map(v=>v+v).join('').slice(1);


Fix mobile money collection type mismatch

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.

Files
Coverage Δ

...lections/operations/get_mobile_money_collection.rs
88.09% <ø> (ø)

src/collections/types/mobile_money_collection.rs
100.00% <ø> (+33.33%)
:arrow_up:


Update documentation on how to write a new extension

Documentation is sparse and needs to be improved

Hey! Is this issue  , still open? I would like to work over documentation. Can you direct me?

@shankarseal Can you check and close this issue if it is done now that #430 is merged?


Support for glossary

Hi! Well first of all, thank you for this project, it is absolutely amazing.
I have a feature request that would be a great add to typst in my opnion: a glossary system (as in LaTeX). Here's an example of how I would imagine it within typst:
#glossary(
   term(DLL, DLLs)[A Dynamic-link library (DLL) is Microsoft's implementation of the shared library concept in the Microsoft Windows operating systems.],
   term(compiler, compilers)[In computing, a compiler is a computer program that translates computer code written in one programming language (the source language) into another language (the target language).],
   alias(dynamic-link library, dynamic-link libraries, DLL) // same as DLL for reference
)

You can build the #term(DLL, plural) by using a #term(compiler). #term(compiler, plural, capitalize) are great tools.

#print_glossary(title: "My custom glossary")

Of course, there's probably a better syntax, easier to use but that's just to show the idea.
Basically, you could:

define your terms with their singular/plural forms.
define aliases (for acronyms for example).
use your terms in your text. A reference to the definition in the glossary would be automatically added. The glossary would also automatically know the page indexes of every occurrences of its terms.
print the glossary (terms and their definitions) with some options (for example, display the page index where the terms are used, custom title, etc).

If someone is interested, waiting for the official feature, I “implemented” a somewhat hacky (and probably slow for large documents) glossary system in Typst that allows to write words definitions in a YAML file. It then automatically adds a link to every occurrence of your glossary words.
Here’s the 4 functions I use :
// Generate a regex that matches all the words in glossary named filename
#let glossaryWords(filename) = {
  let pipeList = "(?i:" // Match case insensitively
  for word in yaml(filename).keys() {
    pipeList += "\b" + word + "\b|" // Stop at word boundaries to not match inside other words
  }
  return regex(pipeList.slice(0, pipeList.len()-1) + ")") // Remove trailing pipe & close parenthesis
}

// Return the position of the word word in the glossary filename as dictionaries don’t implement find-like methods
#let glossaryPosition(filename, word) = {
  let count = 0
  for key in yaml(filename).keys() {
    count += 1
    if lower(key) == lower(word) {return count} // Search case-insensitively by lowering everything
  }
  assert(false, message: word + " not found in glossary but matched in regex") // Debug
}

// For a given word and glossary file, return the word augmented with a link to the glossary
#let glossaryShow(filename, word) = {
  word = repr(word)
  word = word.trim(regex("\s|\[|\]")) // Trim brackets generated by repr() and whitespaces
  return {
    show link: set text(size: 9pt)
    show link: set underline(stroke: 0pt) // I didn’t succeed to disable previous show-set
    // Insert an invisible char into the word to prevent show from looping on itself
    word.first() + "" + word.slice(1) // Unicode empty character
    link(label("glossary"), "(" + str(glossaryPosition(filename, word)) + ")"); " "
  }
}

// Display the words of the glossary with their definition & their eventual web links
#let glossary(filename, title: "Glossary") = {
  let data = yaml(filename)
  // let labelCount = 0
  if data.len() > 0 [
    #heading(title, numbering: none) #label("glossary")

  ]
  for (word, info) in data {
    [/ #word: #info.definition\ → #if "link" in info {link(info.link)}]
    // label("glo" + str(labelCount)) // Try to link words to their specific definition
    // labelCount += 1
  }
}

I then use this line to “enable” the linking of glossary words (so you probably want to place it before your content)
show glossaryWords("glossary.yml"): word => glossaryShow("glossary.yml", word)

And this line to print the actual glossary (generally at the end of the document)
glossary("glossary.yml")

Here’s an example of a glossary.yml file
# Termes techniques dont je parle dans mon rapport de stage au LCPQ
orm:
  definition: Tool to represent relational data as programming language objects
  link: https://fr.wikipedia.org/wiki/Mapping_objet-relationnel

parser:
  definition: Tool that transform a string of text into a tree
  link: https://fr.wikipedia.org/wiki/Analyse_syntaxique

Hope it can help.

I am in the opinion that we should experiment with different ideas in packages, and eventually have a built-in (preferably blazing fast 🚀) option, much like we are doing with tables at the moment.

I came up with following solution for my simple use-case:
glossary.typ
#let glossary(filename) = {
  let terms = yaml(filename)

  for (id, info) in terms {
    [/ #info.term: #info.definition #label(id)]
  }
}

#let term(label, body) = {
  link(
    label,
    underline(
      stroke: (paint: black, cap: "round", thickness: 1pt, dash: "dotted"),
      evade: true,
      offset: 2pt,
      body
    )
  )
}

glossary.yaml
tls:
  term: TLS
  definition: >-
    TLS stands for Transport Layer Security.
    It's a cryptographic protocol that ensures secure communication over a computer network,
    typically the internet. TLS is the successor to the older Secure Sockets Layer (SSL) protocol,
    although the term "SSL" is often used colloquially to refer to both SSL and TLS protocols.

main.typ
#import "glossary.typ": glossary, term

== Glossary

#glossary("glossary.yaml")

== Content

Some content to refer to #term(<tls>, "TLS")

There are now multiple packages for this, so I'll close this: https://typst.app/universe/search?q=glossary

@gfauredev Do you think we can sort the glossary? I'm aiming on creating a glossary which looks something like the following, although I don't need it to be this fancy with different colours and whatnot.

@gfauredev Do you think we can sort the glossary?

Glossarium already sorts alphabetically the glossary entries. However, I think you might have to tweak it a bit to display the first letters as headers.

@gfauredev Do you think we can sort the glossary?

Glossarium already sorts alphabetically the glossary entries. However, I think you might have to tweak it a bit to display the first letters as headers and the hyphens as separators.

If I read the documentation correctly, I'd have to manually reference the words. Can this be automated like in your example?

@gfauredev Do you think we can sort the glossary?

Glossarium already sorts alphabetically the glossary entries. However, I think you might have to tweak it a bit to display the first letters as headers and the hyphens as separators.

Can we just use https://typst.app/docs/reference/model/terms and glossary will be automatically created and styled accordingly? If not, what's the purpose of terms and what's the difference with glossary?

terms is not intended for an automatic glossary, it's just a lists of terms and descriptions. Similar to an HTML/LaTeX description list. An automatic glossary might internally turns into a terms list.


CloneWeak trait, and impl on tuples, Option and Vec of handles

Objective

Lately I'm weak cloning a lot of things, which can be a pain as the default clone impl on things will just clone

Solution

Add a new trait CloneWeak with just a clone_weak function
Impl it for Handle<T> and HandleUntyped
Impl it for Option<H: CloneWeak>, Vec<H: CloneWeak> and tuples
if someone else find that interesting, I would love to have a derive macro #[derive(CloneWeak)] that would clone_weak things when possible, or simply clone otherwise (not completely sure it's possible without specialisation though...)

Probably could also implement it for Rc/Arc since they have versions in the std lib. Makes sense to do so too.

I like this, but agree with James that we should impl this for Rc, Arc and Weak.

I'm curious to see what the motivating use cases are for this before committing to a new abstraction.

Probably could also implement it for Rc/Arc since they have versions in the std lib. Makes sense to do so too.

I'm not sure I see the point of using a reference counting wrapper to a handle which is a reference counting pointer?
In the case of Rc, the clone impl is using some unsafe code, and I think what it would do is not immediately obvious: would it clone it and return a weak pointer to it (from rust, not the weak handle from Bevy)

I'm curious to see what the motivating use cases are for this before committing to a new abstraction.

I'm often keeping handles in resources and reuse them in systems. As a strong handle is kept in the resource, I can weak clone them everywhere. That can be painful as soon as I have wrapper types, as I need to keep a reference to the original resource till the actual point of use if I don't clone them first.

I'm not sure I see the point of using a reference counting wrapper to a handle which is a reference counting pointer?

For me, the goal would be to be able to use something like an impl CloneWeak function argument, and then be able to work with this generically, regardless of what type of weakly clonable object it is.

This feels like a lot of extra generated code for what amounts to a pretty niche use case. My personal take is that this should be a 3rd party clone_weak crate. If that gets a lot of adoption / becomes a common pattern in Bevy code I'd feel more inclined to include this. But given that this is the first time it has come up, I don't want to rush into it.


Added log to the list of options

Don't merge, pls. I'll test before.

Done

hello, thank you for the pull request, successfully merged 👍
Also, wanted to let you know, I'm planning to push updates to npm in a day or few, not right now.

this is ok, I need this feature just locally for testing.


home-assistant-custom-components.homematicip_local: 1.73.0 -> 1.75.0

Diff: https://github.com/danielperna84/custom_homematic/compare/refs/tags/1.73.0...1.75.0
Changelog: https://github.com/danielperna84/custom_homematic/blob/1.75.0/changelog.md

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

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

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 365459

x86_64-linux

:white_check_mark: 5 packages built:

home-assistant-custom-components.homematicip_local
python312Packages.hahomematic
python312Packages.hahomematic.dist
python313Packages.hahomematic
python313Packages.hahomematic.dist


next: Accept operations with offerID array

I wrote a mesos framework for mesos 0.25.0 on mesos-go master branch.
Now I'm trying use the next branch for mesos 0.28.0 because of  v1 Scheduler HTTP API.
On mesos 0.25.0, when you kill a running task, mesos master will offer the resource used by that task immediately. If my scheduler is holding the resource with the same slaveId, then I have two offers with one slaveId now (in different offerId). With method AcceptOffers (in master branch), I can request reserve/launch operations with these two offer to avoid resource fragments or let the big task (require the resources more than any of those two offers) go.
In the next branch, I find there is a method OfferWithOperations that allow me to request operations on only one offerId. BTW, I find acceptBuilder support request operations array with offer array. Is there an other way for me to request operations on the offerId array that with the same slaveId? Or is there anything I can do.
Thx.

@athlum You can try to write
once := sync.Once{}
for _, offid := range selectedOffMap {
once.Do(func() {
OfferWithOperations(offid, taskinfo1)
})
OfferWithOperations(offid)
}
@jdef I think this is  bad

Thanks for the feedback!! Sounds like the convenience funcs aren't that
convenient for your use case.
That said, is anything stopping you from manually constructing the Call the
way that you need it? All the requisite protos are publicly exposed.
On Tue, Jun 14, 2016 at 7:44 AM, wangwei<EMAIL_ADDRESS>wrote:

@athlum https://github.com/athlum You can try to write
once := sync.Once{}
for _, offid := range selectedOffMap {
once.Do(func() {
OfferWithOperations(offid, taskinfo1)
})
OfferWithOperations(offid)
}
@jdef https://github.com/jdef I think this is bad
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mesos/mesos-go/issues/249#issuecomment-225856694, or mute
the thread
https://github.com/notifications/unsubscribe/ACPVLEEgBwavFh7tl47qL-KJQ8JASqxoks5qLpQRgaJpZM4I1Loo
.

thoughts re: #250?

Thanks jdef, that's cool.


Support for pluralsight broken

Please follow the guide below

You will be asked some questions and requested to provide some information, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your issue (like that [x])
Use Preview tab to see how your issue will actually look like

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2017.03.07. If it's not read this FAQ entry and update. Issues with outdated version will be rejected.

[x ] I've verified and I assure that I'm running youtube-dl 2017.03.07

Before submitting an issue make sure you have:

[x ] At least skimmed through README and most notably FAQ and BUGS sections
[x ] Searched the bugtracker for similar issues including closed ones

What is the purpose of your issue?

[ x] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

The following sections concretize particular purposed issues, you can erase any section (the contents between triple ---) not applicable to your issue

If the purpose of this issue is a bug report, site support request or you are not completely sure provide the full verbose output as follows:
Add -v flag to your command line you run youtube-dl with, copy the whole output and insert it here. It should look similar to one below (replace it with your log inserted between triple ```):
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['https://app.pluralsight.com/library/courses/developing-dotnet-microsoft-azure-getting-started', '-o', 'E:\\pluralsight\\Pluralsight Downloader\\%(playlist)s/%(chapter_number)s - %(chapter)s/%(playlist_index)s.%(title)s.%(ext)s', '-u', 'PRIVATE', '-p', 'PRIVATE', '-v']
[debug] Encodings: locale cp1252, fs mbcs, out cp437, pref cp1252
[debug] youtube-dl version 2017.03.07
[debug] Python version 3.4.4 - Windows-10-10.0.14393
[debug] exe versions: ffmpeg N-83454-g3aae1ef, ffprobe N-83454-g3aae1ef
[debug] Proxy map: {}
[pluralsight:course] developing-dotnet-microsoft-azure-getting-started: Downloading course JSON
[download] Downloading playlist: Developing with .NET on Microsoft Azure - Getting Started
[pluralsight:course] playlist Developing with .NET on Microsoft Azure - Getting Started: Collected 67 video ids (downloading 67 of them)
[download] Downloading video 1 of 67
[pluralsight] Downloading login page
[pluralsight] Logging in as xxxxx
ERROR: Unable to log in; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpvin3ute2\build\youtube_dl\YoutubeDL.py", line 761, in extract_info
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpvin3ute2\build\youtube_dl\extractor\common.py", line 426, in extract
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpvin3ute2\build\youtube_dl\extractor\common.py", line 384, in initialize
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpvin3ute2\build\youtube_dl\extractor\pluralsight.py", line 60, in _real_initialize
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpvin3ute2\build\youtube_dl\extractor\pluralsight.py", line 100, in _login
youtube_dl.utils.ExtractorError: Unable to log in; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

If the purpose of this issue is a site support request please provide all kinds of example URLs support for which should be included (replace following example URLs by yours):

Single video: https://www.youtube.com/watch?v=BaW_jenozKc
Single video: https://youtu.be/BaW_jenozKc
Playlist: https://www.youtube.com/playlist?list=PL4lCao7KL_QFVb7Iudeipvc2BCavECqzc

Note that youtube-dl does not support sites dedicated to copyright infringement. In order for site support request to be accepted all provided example URLs should not violate any copyrights.

Description of your issue, suggested solution and other information
Explanation of your issue in arbitrary form goes here. Please make sure the description is worded well enough to be understood. Provide as much context and examples as possible.
If work on your issue requires account credentials please provide them or explain how one can obtain them.

https://github.com/rg3/youtube-dl/issues/12345#issuecomment-284054428


enter passcode page

by using this method "window.plugins.touchid.verifyFingerprintWithCustomPasswordFallback" , i am not getting the default enter passcode page after clicking on "Enter Password" button (i am not getting any default screen), whereas by using the method "window.plugins.touchid.verifyFingerprint" i will get the default passcode page, can you please suggest why this is happening.

Because that's what's meant by 'With Custom Password Fallback'?

so, while clicking on enter password button where i will type my password if no screen is there.
i am getting error code as -3 if i press on enter password,  the expected scenario is while typing the correct password only he will be able to enter inside the app. what should i do?

Add a custom password screen yourself.


can any one explain what is stationaryRadius 😊 ?

+1

"Stationary radius in meters. When stopped, the minimum distance the device must move beyond the stationary location for aggressive background-tracking to engage."

@maq0n not that much clear


"Create Mobile service" window should be closed when user presses Esc Key

Environment: Windows/IntelliJ14
Steps:
Right click on mobile services.
Click create service.
Create Mobile service window will open.
Press Esc, it should close the current window.

This issue if fixed and the functionality is working as expected in the latest build.


Graphql key as number with GraphQLJSON

Good day,
I use GraphQLJSON because I found we have fields in a NoSLQ database named like "90-100", meaning they are numbers and Graphql does not allow numbers as keys.
Question is, GraphQLJSON allows me to retrieve the saved data, but does not allow me to simply do the same in a GraphQLInputObjectType.
Is there a way to get a JSON as a input so I can skip that?
Thanks a lot for the help and the package creation! :)

GraphQLJSON works just fine as an input object.

input type rather


Removed non-containerized stuff from the CI pipeline.

Which issue this PR addresses:
Fixes : ARO-10581
What this PR does / why we need it:
This PR removes all non-containerized components from the CI pipeline as part of the effort to fully containerize and streamline the pipeline. By eliminating these non-containerized stages, the pipeline becomes more efficient, easier to maintain, and consistent with best practices for modern CI/CD workflows.
Test plan for issue:

Verified that all non-containerized stages are removed.
Pipeline was tested using containerized components to ensure all stages complete successfully.

Is there any documentation that needs to be updated for this PR?
N/A
How do you know this will function as expected in production?
N/A

/azp run ci, e2e

/azp run ci,e2e


fix source map broken

Must return the sourcemap to vite, otherwise it would broke the sourcemap when debugging.
There is no default value for dts. It is always false if there is no config. But the document says its default value is isPackageExists('typescript').

#278 fix here.

219 issue still open.
So this pull request didn't help?


fix: drop Host header in https outcall request

Having the Host header seems to cause problem with https outcalls using http/2, which is currently the case.
It is best to remove this setting from examples because many people (me included) would copy them and later have a hard time figuring out what could be the problem if something goes wrong.

@ninegua seems like you need to resolve some conflicts first 😅


Update desktop notifications docs link

Both UWP and desktop apps use the same docs link now (once the Microsoft docs update goes live which should go live alongside the blog)

Fixes #
Docs for Toolkit PR #
What changes to the docs does this PR provide?

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

[ ] Correctly picked the right branch to base the change off (master for new features, live for typos/improvements)
[ ] For new pages, used the provided template
[ ] For new features, added an entry in the Table of Contents
[ ] Ran against a spell and grammar checker
[ ] Contains NO breaking changes

Other information

Docs Build status updates of commit eb58705:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/notifications/NotificationsOverview.md
:warning:Warning
View
Details

docs/notifications/NotificationsOverview.md

Line 22, Column 1: [Warning-alt-text-bad-value] Alt text 'LiveTile' is the same as the image file name. This redundancy adds no value for users of screen readers. For accessibility, add more descriptive alt text.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Unable to disable the input fields and buttons after importing keys from external apps

Description:
Unable to disable all the input fields and update button in the UI after importing keys from an external app since the Keys and Key manager payloads do not provide a flag for this purpose.

This issue is fixed in carbon-apimgt master branch with PR https://github.com/wso2/carbon-apimgt/commit/2c8d038e37a51b1e82bf7a8985c51b6f56391271


Modcat 7

MODCAT-7: Created the service that returns the index with the corresponding constraints
and the service that returns a list of all indexes belonging to such category

Mi dici un indice che ha una struttura corposa? Per farlo vedere nella demo
On 12/12/17 16:06, carmentrazza wrote:

MODCAT-7: Created the service that returns the index with the
corresponding constraints
and the service that returns a list of all indexes belonging to such
category

    You can view, comment on, or merge this pull request online at:

https://github.com/atcult/mod-cataloging/pull/3
    Commit Summary

MODCAT-7: Created the service that returns the index with the
corresponding constraints and the service that returns a list of
all indexes belonging to such category

MODCAT-7: Created the service that returns the index with the
corresponding constraints and the service that returns a list of
all indexes belonging to such category

MODCAT-7: Created the service that returns the index with the
corresponding constraints and the service that returns a list of
all indexes belonging to such category

MODCAT-7: Created the service that returns the index with the
corresponding constraints and the service that returns a list of
all indexes belonging to such category

MODCAT-7: Created the service that returns the index with the
corresponding constraints and the service that returns a list of
all indexes belonging to such category

MODCAT-7: Created the service that returns the index with the
corresponding constraints and the service that returns a list of
all indexes belonging to such category

MODCAT-7: Created the service that returns the index with the
corresponding constraints and the service that returns a list of
all indexes belonging to such category
File Changes

M raml/indexes.raml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-0 (9)

M raml/schemas/index.json
https://github.com/atcult/mod-cataloging/pull/3/files#diff-1 (14)

M
src/main/java/org/folio/cataloging/bean/searching/AdvancedSearchBean.java
https://github.com/atcult/mod-cataloging/pull/3/files#diff-2 (6)

M src/main/java/org/folio/cataloging/dao/DAOCodeTable.java
https://github.com/atcult/mod-cataloging/pull/3/files#diff-3 (18)

M src/main/java/org/folio/cataloging/dao/DAOIndexList.java
https://github.com/atcult/mod-cataloging/pull/3/files#diff-4 (75)

M src/main/java/org/folio/cataloging/dao/DAOSearchIndex.java
https://github.com/atcult/mod-cataloging/pull/3/files#diff-5 (179)

M
src/main/java/org/folio/cataloging/dao/persistence/IndexMain.java
https://github.com/atcult/mod-cataloging/pull/3/files#diff-6 (4)

R
src/main/java/org/folio/cataloging/dao/persistence/IndexSub.java
https://github.com/atcult/mod-cataloging/pull/3/files#diff-7 (406)

M
src/main/java/org/folio/cataloging/integration/StorageService.java
https://github.com/atcult/mod-cataloging/pull/3/files#diff-8 (49)

M src/main/java/org/folio/rest/impl/IndexesAPI.java
https://github.com/atcult/mod-cataloging/pull/3/files#diff-9 (68)

M src/main/resources/hibernate.cfg.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-10 (170)

M
src/main/resources/org/folio/cataloging/dao/persistence/AUT.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-11 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/BND_CPY.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-12 (4)

M
src/main/resources/org/folio/cataloging/dao/persistence/BRWR.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-13 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/BRWR_CMCTN.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-14 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/BRWR_FINE.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-15 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/BRWR_FINE_PAYMT.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-16 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/BRWR_NTE.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-17 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/BRWR_PSTL_ADR.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-18 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/CAS_CSTMR.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-19 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/CAS_ESITO_IMPORT.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-20 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/CAS_FILTRI_MIGRAZIONE.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-21 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/CAS_FLTR_IMP.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-22 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/CAS_FLTR_IMP_SPOT.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-23 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/CIRTN_HLD.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-24 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/CIRT_ITM.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-25 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/CIR_INVTRY_LGL.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-26 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/CIR_INVTRY_LGL_SRCH.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-27 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/CIR_INVTRY_PHSCL.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-28 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/CIR_INVTRY_SRCH.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-29 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/CLCTN_CST_RULE.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-30 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/CLCTN_CST_RULE_RECORD.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-31 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/CLCTN_MST_CSTMR.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-32 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/CLCTN_MST_HRCY.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-33 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/CLCTN_MST_RULE.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-34 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/CLCTN_MST_RULE_RECORD.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-35 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/CLCTN_MST_RULE_REL.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-36 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/CLCTN_PUBL_HRCY.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-37 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/CLCTN_RULE_TMP.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-38 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/CLCTN_TMP.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-39 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/CLSTN.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-40 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/CNTL_NBR.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-41 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/CPY_HLD.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-42 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/CPY_HLD_DTL.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-43 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/CPY_ID.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-44 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/DSCRD_CPY.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-45 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/HDG_URI.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-46 (20)

M
src/main/resources/org/folio/cataloging/dao/persistence/HLDG_NTE.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-47 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/HLD_ARCH.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-48 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/HLD_RCALL_QUEUE.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-49 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/IDX_LIST.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-50 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/INDEX_SUB_LIST.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-51 (4)

M
src/main/resources/org/folio/cataloging/dao/persistence/INVTRY.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-52 (16)

M
src/main/resources/org/folio/cataloging/dao/persistence/INVTRY_DSCRD_CPY.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-53 (16)

M
src/main/resources/org/folio/cataloging/dao/persistence/LCTN.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-54 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/LCTN_ISOLANG_VW.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-55 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/LCTN_VW.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-56 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/LIB.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-57 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/LIB_DTE_CLSE.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-58 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/LIB_FINE_PLCY.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-59 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/LIB_HOLD_PLCY.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-60 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/LIB_HRS_OPRTN.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-61 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/LIB_LOAN_PLCY.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-62 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/LIB_OVRD_PLCY.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-63 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/LIB_TME_HLD_PLCY.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-64 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/LOAN.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-65 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/LOAN_ARCH.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-66 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/LOAN_DTL.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-67 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/LOAN_INTER_BRNCH.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-68 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/LOAN_INTER_LIB.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-69 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/LOAN_IN_TRNST_PLCY.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-70 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/LV_DATABASE.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-71 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/LV_GROUP.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-72 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/LV_USER.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-73 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/LV_USER_COMMUNICATION.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-74 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/LV_USER_DATABASE.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-75 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/LV_USER_GROUP.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-76 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/LV_USER_POSTAL_ADDRESS.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-77 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/NME_HDG.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-78 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/NME_NME_TTL_REF.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-79 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/NME_REF.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-80 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/NME_TO_TTL_REF.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-81 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/NME_TTL_REF.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-82 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/OPEN_SUITE_RELEASE.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-83 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/ORG.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-84 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/ORG_HRCHY.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-85 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/ORG_NME.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-86 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/PRSN.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-87 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/PUBL_CDE.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-88 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/PUBL_HDG.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-89 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/PUBL_REF.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-90 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/SBJCT_HDG.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-91 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/SBJCT_REF.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-92 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/SBJCT_TRM_TYP.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-93 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/SHLF_LIST.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-94 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/SHLF_LIST_ACS_PNT.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-95 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/SMRY_HLDG.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-96 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/STD_NTE_ACS_PNT.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-97 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/S_AUT_MARC_IND_DB_CRLTN.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-98 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/S_AUT_MARC_TAG_VLDTN.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-99 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/S_AUT_TAG_MARC_DSPLY.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-100 (6)

M
src/main/resources/org/folio/cataloging/dao/persistence/S_BIB_MARC_IND_DB_CRLTN.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-101 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/S_BIB_MARC_TAG_VLDTN.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-102 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/S_BIB_TAG_MARC_DSPLY.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-103 (6)

M
src/main/resources/org/folio/cataloging/dao/persistence/S_CAS_CACHE.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-104 (16)

M
src/main/resources/org/folio/cataloging/dao/persistence/S_LCK_TBL.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-105 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/S_LOAN_STATS.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-106 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/S_MSG.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-107 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/S_MSG_CIRC.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-108 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/S_NXT_NBR.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-109 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/S_ORDR_NAMES.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-110 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/S_OVRD_NTC.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-111 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/S_PATCH_HISTORY.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-112 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/S_RDA_TAG_MARC_DSPLY.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-113 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/S_RLTSP_RCPCL.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-114 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/S_SRCH_SRT_RSLTS.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-115 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/S_SRT_CRTRIA_DTL.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-116 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/S_SYS_GLBL_VRBL.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-117 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/TAG_GRP_MODEL.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-118 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/TAG_MODEL.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-119 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/THS_ATRIB.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-120 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/THS_HDG.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-121 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/THS_NTE.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-122 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/THS_REF.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-123 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/TTL_HDG.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-124 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/TTL_HLD.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-125 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/TTL_HLD_DTL.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-126 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/TTL_NME_TTL_REF.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-127 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/TTL_REF.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-128 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/TYP_REC_MTRL.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-129 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_ADR_PROV_TRTRY_STATE.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-130 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_APLTN_AUTH_LVL_CDE.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-131 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_AUT_BLNGL_USG.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-132 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_AUT_CLSTN_FNCTN.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-133 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_AUT_CLSTN_TYP.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-134 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_AUT_CNTL_NBR_TYP.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-135 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_AUT_CONF_MTG.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-136 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_AUT_CTLGG_RLE.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-137 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_AUT_CTLGG_SRC.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-138 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_AUT_DSPLY_FRMT.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-139 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_AUT_ENCDG_LVL.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-140 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_AUT_GOVT_AGNCY.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-141 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_AUT_HDG_SRC.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-142 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_AUT_HDG_STUS.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-143 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_AUT_HDR.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-144 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_AUT_MAIN_ADD_ENTRY.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-145 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_AUT_NON_UNQ_NME.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-146 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_AUT_NTE_GRP_TYP.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-147 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_AUT_NTE_TYP.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-148 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_AUT_REC_MDFTN.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-149 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_AUT_REC_RVSN.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-150 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_AUT_REC_STUS.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-151 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_AUT_REC_TYP.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-152 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_AUT_REF_HDG_TYP.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-153 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_AUT_REF_STUS.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-154 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_AUT_RMNZT_SCHM.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-155 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_AUT_SBJCT_DSCTR.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-156 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_AUT_SBJCT_ENTRY.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-157 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_AUT_SBJCT_HDG_TYP.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-158 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_AUT_SBJCT_SYS.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-159 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_AUT_SHLF_LIST_FNCTN.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-160 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_AUT_SHLF_LIST_TYP.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-161 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_AUT_SRS_ENTRY.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-162 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_AUT_SRS_NBRG.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-163 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_AUT_SRS_TYP.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-164 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_AUT_SUB_DIV_TYP.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-165 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_AUT_TAG_CAT.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-166 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_BIB_DSPLY_FRMT.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-167 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_BIB_HDR.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-168 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_BIB_NTE_GRP_TYP.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-169 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_BIB_NTE_TYP.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-170 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_BIB_TAG_CAT.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-171 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_BOOK_BGPHY.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-172 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_BOOK_FTSCT.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-173 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_BOOK_IDX_AVBTY.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-174 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_BOOK_ILSTN.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-175 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_BOOK_LTRY_FORM_TYP.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-176 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_BOOK_TYP_CDE.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-177 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_BRWR_TYP.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-178 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_CAS_ACTV_SPOT.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-179 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_CAS_CURCY_TYP.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-180 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_CAS_DIG_LEVEL_TYP.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-181 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_CAS_DIG_TYP.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-182 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_CAS_FLTR.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-183 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_CAS_FONTI.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-184 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_CAS_ITEM_SAL_TYP.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-185 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_CAS_LEVEL_TYP.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-186 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_CAS_MDR_FGL.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-187 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_CAS_MNGRL_LVL_TYP.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-188 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_CAS_SAL_TYP.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-189 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_CAS_SDIV_GEOG_TYP.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-190 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_CAS_SDIV_PRTC_TYP.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-191 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_CAS_SDIV_TMPL_TYP.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-192 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_CAS_STND_NTE_SUB_TYP.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-193 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_CAS_STND_NTE_TYP.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-194 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_CF_ANTSRC.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-195 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_CF_CLR.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-196 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_CF_DMNSN.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-197 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_CF_FF.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-198 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_CF_FORM_OF_ITM.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-199 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_CF_LOC.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-200 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_CF_QAT.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-201 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_CF_RQ.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-202 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_CF_SMD.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-203 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_CLCTN.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-204 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_CLCTN_CST.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-205 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_CLCTN_CST_ARCH.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-206 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_CLCTN_CST_TYP.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-207 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_CLCTN_MST.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-208 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_CLCTN_MST_TYP.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-209 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_CLCTN_PUBL.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-210 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_CLCTN_PUBL_LVL_TYP.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-211 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_CLCTN_PUBL_TYP.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-212 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_CLCTN_TYP.hbm
(2).xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-213 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_CLCTN_TYP.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-214 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_CLSTN_FNCTN.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-215 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_CLSTN_TYP.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-216 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_CMPTR_FIL_TYP.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-217 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_CMPTR_TRGT_AUDNC.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-218 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_CNTCT_CMCTN_MDM_TYP.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-219 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_CNTL_NBR_FNCTN.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-220 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_CNTL_NBR_TYP.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-221 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_CNTL_NBR_VLDTN.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-222 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_CONF_PBLTN.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-223 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_CRTGC_FRMT.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-224 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_CRTGC_IDX_AVBTY.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-225 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_CRTGC_MRDN.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-226 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_CRTGC_MTRL.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-227 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_CRTGC_NRTV_TXT.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-228 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_CRTGC_PRJTN.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-229 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_CRTGC_RLF.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-230 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_CRTGC_TYP_CDE.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-231 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_DFLT_TRSLTN_NTE.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-232 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_DSCRD_TYP.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-233 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_DSC_CNVTN.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-234 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_DUAL_REF.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-235 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_DWY_TYP.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-236 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_FILES_HRCY.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-237 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_FORMAT_REC.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-238 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_FORM_OF_ITM.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-239 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_FRBR.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-240 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_GEOG_AREA.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-241 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_GLB_CLR.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-242 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_GLB_PHSCL_MDM.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-243 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_GLB_RPDTN_TYP.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-244 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_GLB_SMD.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-245 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_GMD.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-246 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_GOVT_PBLTN.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-247 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_HLDG_1ST_IND.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-248 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_HLDG_2ND_IND.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-249 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_HLDG_LVL_OF_DTL.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-250 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_HLDG_NTE_ISOLANG_VW.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-251 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_HLDG_NTE_VW.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-252 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_HLDG_RTNTN.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-253 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_HLDG_SBCPT_STUS.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-254 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_HLDG_SRS_TRMT.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-255 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_HLDG_STUS.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-256 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_HLDG_STUS_TYP.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-257 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_HLD_RCALL_QUEUE_TYP.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-258 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_ILL.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-259 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_ILL_SERV.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-260 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_INPT_SRC.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-261 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_ITM_BIB_LVL.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-262 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_ITM_CCS.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-263 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_ITM_CNTL_TYP.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-264 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_ITM_DSCTV_CTLG.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-265 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_ITM_DSPLY.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-266 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_ITM_DSPLY_FRMT.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-267 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_ITM_DTE_TYP.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-268 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_ITM_ENCDG_LVL.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-269 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_ITM_LNK_REC.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-270 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_ITM_REC_STUS.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-271 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_ITM_REC_TYP.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-272 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_ITM_RPLMT_STUS.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-273 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_ITM_TRLTN.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-274 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_KIT_SMD.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-275 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_LANG.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-276 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_LANG_OF_ACS_PNT.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-277 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_LANG_OF_ACS_PNT_SBJCT.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-278 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_LANG_OF_IDXG.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-279 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_LANG_OF_IDXG_LANG.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-280 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_LANG_PRFNC.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-281 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_LIB_LOAN_TYP.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-282 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_LOAN_ACTVTY.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-283 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_LOAN_PRD.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-284 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_LOAN_STATS_TYP.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-285 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_MAD_CNDTN_MTRL_TYP.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-286 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_MAD_CNDTN_TYP.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-287 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_MAD_CNSTC_MSR_TYP.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-288 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_MAD_CNSTC_PRC_TYP.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-289 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_MAD_DGTL_RSC_TYP.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-290 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_MAD_EPC_TYP.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-291 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_MAD_FST_TYP.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-292 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_MAD_GNRC_NTE_TYP.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-293 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_MAD_ITM_LVL.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-294 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_MAD_NME_TYP_AND_SUB_TYP.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-295 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_MAD_NMRTN_TYP.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-296 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_MAD_NTE_TYP.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-297 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_MAD_RLTR_TRM_CDE.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-298 (2)

M
src/main/resources/org/folio/cataloging/dao/persistence/T_MAD_SPRT_TYP.hbm.xml
https://github.com/atcult/mod-cataloging/pull/3/files#diff-299 (2)
Patch Links:

https://github.com/atcult/mod-cataloging/pull/3.patch

https://github.com/atcult/mod-cataloging/pull/3.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/atcult/mod-cataloging/pull/3, or mute the thread
https://github.com/notifications/unsubscribe-auth/AHOA4GdtHdZw5JuSyL87n2FJAm0z59Ceks5s_paMgaJpZM4Q_HbI.

--
Andrea Gazzarini
/Founder,//CEO/
+39 349 513 86 25
<EMAIL_ADDRESS>SpazioCodice
/"We believe that writing software should be fun and easy"/
/http://www.spaziocodice.com
//
Via Don Luigi Sturzo, 3
01030 Vallerano (VT)
Tel. +39 0761 1916790
<EMAIL_ADDRESS>/


contrib/pi_examples's Makefile is missing lib nsync.a

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): No
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Raspbian Stretch
TensorFlow installed from (source or binary): source (not installed)
TensorFlow version (use command below): 1.8.0rc1
Python version: -
Bazel version (if compiling from source): -
GCC/Compiler version (if compiling from source): 4.8
CUDA/cuDNN version: -
GPU model and memory: -
Exact command to reproduce: follow instructions here: https://github.com/tensorflow/tensorflow/tree/master/tensorflow/contrib/pi_examples

Describe the problem
Attempting to build the sample with make will fail in the linking stage with an undefined reference to nsync::nsync_cv_signal(nsync::nsync_cv_s_*)'. Adding -Ltensorflow/contrib/makefile/downloads/nsync/builds/default.linux.c++11toLDFLAGS(taken from the env var TARGET_NSYNC_LIB) and-l:nsync.atoLIBS` fixes the problem.
So far I hardcoded the paths, so I can't really make a PR (and I'm not experienced enough with shell scripts / makefiles to propose a decent fix).

Nagging Assignee @rohan100jain: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @rohan100jain: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @rohan100jain: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @rohan100jain: It has been 60 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @rohan100jain: It has been 75 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @rohan100jain: It has been 90 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @rohan100jain: It has been 90 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @petewarden: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @petewarden: It has been 35 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @petewarden: It has been 50 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @petewarden: It has been 65 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @petewarden: It has been 80 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @petewarden: It has been 95 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Automatically closing due to lack of recent activity. Please update the issue when new information becomes available, and we will reopen the issue. Thanks!


[QUESTION] How can I split my commands into different "command.py" files?

First check

[x] I used the GitHub search to find a similar issue and didn't find it.
[x] I searched the Typer documentation, with the integrated search.
[x] I already searched in Google "How to X in Typer" and didn't find any information.
[x] I already searched in Google "How to X in Click" and didn't find any information.

Description
I am just getting started with the library Typer for building CLI's. I apologize in advance if this issue has been raised more than once, but I could not find it on Google to help me with the correct implementation.
There are too many commands in my cli.py and I want to moved them to a separate folder “commands”, but I cannot figure out how to implement a dynamic loader for these commands in cli.py.
my_app/
 __init__.py
 commands/
       __init__.py
       command1.py
       command2.py
 cli.py

I want start by creating a class "Command" for each command with a single function "handle (**options)" that contains the functionality. But I am not sure if I am forming the class correctly. I want to make a class "AsyncCommand" because the command can be complex and can be properly decomposed into methods and encapsulated within one class
# a_test_command.py
from typer.core import TyperCommand
class AsyncCommand(TyperCommand):
    @staticmethod
    async def handle('a-test-command'):
        print('test_command')

Ideally, when starting cli.py, I want to check which modules are there and load them dynamically, leaving the cli.py file clean. But I do not understand at all how it is better and more correct to implement it.

Were you using subcommands already: https://typer.tiangolo.com/tutorial/subcommands/
or is your case different?

Yes, I figured it out, but I thought that me need to work with the class somehow differently than with a simple function, but there is no difference :)
But I still have a problem with how to organize the dynamic addition of the module, so as not to produce a lot of "app.add_typer (command)"
I mean something like:

Unless you mean to load commands based on argument supplied by the user, you could create for example dictionary in commands.__init__.py:
from .command1 import command1
from .command2 import command2

all_commands = {
    "command1": command1,
    "command2": command2,
}

and within your main.py or cli.py:
import typer

from commands import all_commands

app = typer.Typer()
for name, command in all_commands.items():
    app.add_typer(command, name=name)

I would advice against dynamically loading commands based on user's input because in case:
my-cli wrong-command

Typer would not load your command and help would probably be empty or you could get an error because it couldn't add not existing resource, forcing user to know what commands are available beforehand.

Actually you don't have to create a dictionary like this when you do pass a name for the subcommands, like:
import typer
command1 = typer.Typer(name="command1")

so instead of a dictionary a list would also do:
commands.__init__.py
from .command1 import command1
from .command2 import command2

all_commands = [
    command1,
    command2,
]

and in the main.py:
import typer

from .commands import all_commands

app = typer.Typer()
for sub_command in all_commands:
    app.add_typer(sub_command)

Thank you very much for your help.
File "/usr/local/lib/python3.7/site-packages/typer/main.py", line 347, in get_group_from_info
    for command_info in group_info.typer_instance.registered_commands:
AttributeError: module 'commands.healthcheck' has no attribute 'registered_commands'

My command module look like:
import typer
app = typer.Typer()

class Command:
    def __init__(self, *args):
        self.args = args

    @staticmethod
    @app.command()
    def handle():
        print('_' * 11)
        print('test_command')

if __name__ == "__main__":
    app()

The one who is stupid, gets stuck and never asks a question. :)
Could you add some more details?
I did run your code as a command and subcommand and it works for me.

Thanks again for your help, you really helped me)
I added 5 and 22 lines from your code and it helped