Wrong Word-Confidence for specific input

Before you submit an issue, please review the guidelines for this repository.
Please report an issue only for a BUG, not for asking questions.
Note that it will be much easier for us to fix the issue if a test case that
reproduces the problem is provided. Ideally this test case should not have any
external dependencies. Provide a copy of the image or link to files for the test case.
Please delete this text and fill in the template below.

Environment
Tesseract Version:
tesseract v<IP_ADDRESS>20510, 32-Bit
leptonica-1.78.0
libgif 5.1.4 : libjpeg 8d (libjpeg-turbo 1.5.3) : libpng 1.6.34 : libtiff 4.0.9 : zlib 1.2.11 : libwebp 0.6.1 : libopenjp2 2.3.0
Found SSE4.1
Found libarchive 3.5.0 zlib/1.2.11 liblzma/5.2.3 bz2lib/1.0.6 liblz4/1.7.5 libzstd/1.4.5
Found libcurl/7.77.0-DEV Schannel zlib/1.2.11 zstd/1.4.5 libidn2/2.0.4 nghttp2/1.31.0
Platform:
Microsoft Windows 10 Enterprise, Version 10.0.19045 Build 19045, 64-Bit
Current Behavior:

Wrong Word-Confidence for input file "NOK.jpg".
Correct Word-Confidence for input file "OK.jpg" (image is almost identical with "NOK.jpg"
See attached input-, hocr- and own log- files

Expected Behavior:
Correct Word-Confidence
Suggested Fix:

hocr_NOK.txt
hocr_OK.txt

please use the latest code where reporting issue

Command lines:
tesseract.exe NOK.bmp hocr_NOK --tessdata-dir tessdata --psm 6 -l deu -c tessedit_create_hocr=1 -c hocr_font_info=0
tesseract.exe OK.bmp hocr_OK --tessdata-dir tessdata --psm 6 -l deu -c tessedit_create_hocr=1 -c hocr_font_info=0

I got different result with 'tesseract nok.jpg nok -l deu hocr'
nok.hocr.txt

I tested with original BMP-File, but could not upload it, so its converted to JPG.
With the attached PNG-file same result as original BMP-File.
tesseract.exe NOK.png hocr_NOK --tessdata-dir tessdata --psm 6 -l deu -c tessedit_create_hocr=1 -c hocr_font_info=0

The wrong symbol "A" in word "BAK" is not the problem, i can live with that. But the whole word "BAK" has confidende 0.
See attached Log (from my  application).

The result should be "BKK", so a smaller confidence for "BAK" seems to be okay. Maybe it should not be 0, but at least lower than in the second case. The "K" is not recognized correctly in the first image because its quality in that image is less good.

The wrong result comes from using the "deu" model which is not so good and therefore has problems with the low quality "K". The model "script/Latin" gives a better result.

Also tried with newest 64-Bit Windows version 5.3.0 from UB Mannheim.
Small difference, sasically same result, but in hocr output the word confidence is 0 (in 32-Bit its 1):
64-Bit: x_wconf 0
32-Bit: x_wconf 1
Finally issue is solved with:
tesseract.exe NOK.png hocr_NOK --tessdata-dir tessdata --psm 6 -l deu+script/Latin hocr

The word confidence is the lowest confidence among all symbols in a word.
Anyway, a symbol confidence of 0.00 is bug.

A symbol confidence of 0 looks odd.
It should be interpreted as: "It's looks like there is a symbol there. It's hard to tell what is the symbol, but here my best guess".

The word confidence is the lowest confidence among all symbols in a word.

This doesn't appear to be true any more. Mean seems to be more logical than Min for this.
https://github.com/tesseract-ocr/tesseract/blob/67438fad8b851f7e514924e64cee89789f425cf9/src/ccmain/ltrresultiterator.cpp#L135-L145

I'm not sure that there isn't something suspicous going on here. Consider this following snippet from an Internet Archive book which has a wconf of 90 and a mean symbol confidence of ~99.

       F
       L
       E
       U
       R
       S

while it's certainly possible to have a word confidence lower than the individual character confidences, as a matter of principle (although not for Tesseract?), it looks improbable in this case.

I've deleted my previous (potentially misleading) replies. Researching more...


I don't see Video or Calls options in WhatsApp on Franz

WhatsApp Windows app shows Chat, Video and Voice calls but WhatsApp in Franz only shows Chats
Anyone else have an issue like this?
Windows 10 PC
Windows WhatsApp
Franz v 5.8.0-beta.1

@jtscloudservices https://getferdi.com/

@jtscloudservices https://getferdi.com/

Will take a look. Thanks for that

@jtscloudservices https://getferdi.com/

Thanks but looks exactly like Franz and does not include Calls. Will continue to test Ferdi anyway. Thanks for the suggestion


sercret disabling capabilities

Add the capability to disable secret handling for cloud.conf file, in order to get creds from host volume

/ok-to-test


Deals not loading, import failing.

We are investigating issues loading deals, and importing deals into Autovance.

We've identified the issue and are actively working to correct it.

We are seeing recovery and are actively monitoring the health of the system.

We've seen full recovery, and are continuing to monitor the system for any further issues.


[svplugins/collect_nvsearch] Facillitate proxy server to enhance privacy

Refer to

https://www.browserstack.com/guide/set-proxy-in-selenium
https://surpassing.tistory.com/917
https://tytybro.github.io/tip/2022/03/11/tip_selenium/
https://www.geeksforgeeks.org/how-to-use-xpath-with-beautifulsoup/

Remove scrapy

Replace debug msg to CUI progress bar

[svload/pandas_plugins/search_api] Chage NVR KIN date from regdate to logdate

Prevent IndexError if there is no HTTPS proxies
Remove test code


[Feat]: Implementation of Docker Containerization for the Application

Feature Description
Docker Containerization
Provide a detailed description of the feature
Description:
Proposal: Docker Containerization Implementation
Objective:
Implement Docker containerization to streamline deployment, enhance scalability, and improve portability across different environments.
Benefits:
Streamlined Deployment: Consistent deployment across platforms reduces issues.
Improved Portability: Facilitates migration between environments.
Simplified Maintenance: Easier management and updates without system impact.
Put here any screenshots or videos (optional)
No response
By submitting this issue, you agree to

[X] I agree to follow this project's Code of Conduct
[X] I’ve read all the issues in the issue section, and this feature has not been proposed yet.

Other Information

[ ] I'm a GSSoC '24 Extended contributor
[X] I'm a Hacktoberfest '24 contributor
[X] I am willing to work on this feature (optional)

Hey @maniyaom can you assign this to me?? And please add hactoberfest and hacktoberfest-accepted label on this issue!!


Doesn't work with images

When copying images, they get stored as plain text so you can't for example copy a screenshot then paste it into an image editor.

I can copy from Firefox into GIMP with no problems.
I faced a problem, however, on X11 clients that do not support the MULTIPLE target, like xclip (xclipd needs that the clipboard source supports the MULTIPLE target).
What are the clipboard source application (the one you Ctrl-C) and the clipboard destination application (the one you Ctrl-V)?

Using xclip with the image/png target to copy, pasting into Discord and GIMP both did not work.

Yeah, as I supposed: xclip.
It lacks support for the MULTIPLE target.
There's an issue there for that.
If copying images works between other applications (say from Firefox to GIMP) but not from xclip, then that's not a bug on xclipd side, but on xclip's. (Although they are named alike, those projects are not related).
I can make a workaround for clients that does not support the MULTIPLE target, but that's a hack. The optimal solution is to all X11 clients engaging into the clipboard selection mechanism to implement the ICCCM selection protocol.

Copying does work between applications, guess I'll close this then. Any recommendations for an xclip alternative?

Copying does work between applications, guess I'll close this then. Any recommendations for an xclip alternative?

The only X11 clients that work as source and destination for the clipboard are xclip and xsel.
xsel, however, seems to not support targets provided by the user.
I want to expand xclipd in the future with two more commands, one for writing into the clipboard, and the other for reading from the clipboard, thus providing replacements for xclip -in and xclip -out. Those commands will implement the full ICCCM specification, and thus work with other programs.
However, I have implemented into xclipd a solution to work with xclip and other clients which do not fully implement the ICCCM specification. More information in the commit message.

Works now, thanks!

Hi, xclipd  is now included with a few other utilities, two of which, xclipin and xclipout can replace xclip -in and xclip -out commands.
xclipd still works with not fully ICCCM-compliant applications such as xclip.


Creating a Compliance Collaboration network

New to GitHub
Required to join as part of the course.
Look exciting
Testing to see how this might work


Updating to latest quick-sip api.

This is untested as I have no clue how to test it against an unreleased version of quick-sip or how to test yo against an unreleased version of this.

@kentmw  - is this good to go?  quick-sip 0.1.2 is released.

+2 if it works :)


BUG right click event also triggers left click event sometimes with doors

So i made lots of weapons on my server where you shoot with right click and reload with left click. But when you right click on doors and on chests you clear the rest of the script so that doors and chest can be used wihout shooting yourself.
Here is the script, i shortened it down.
http://hastebin.com/ujumetagah.xml
So I placed a door and a chest to test it. With chests there is no problem, but with doors in about 1-3% of the tests instead of the right click event the left cklick event was triggered and people started to reload their weapons.
Could you take a look at that?

btw I am using Spigot 1.8.3 and latest Denizen Dev Build but i had this problem before the update, too.

Okay.
/what/.

How is the status in this one?

Did you never see my reply above?

I logged bug #1042 that may be related to this...Does your right-click event have code in it that uses animate? Does it only occur when your players have something in their hand?


Only run coveralls once, not for each python version in matrix

Currently, coverage/coveralls is running once for each version of python in the matrix.  This seems like overkill.  More over, for some reason, only the first one worked on merge of the branch.
https://github.com/CNERG/learn-maintenance/actions/runs/2907420994

It looks like all the invocation of coveralls are working now, but we still only need to run it once


Tutorial on writing basic specs in Quint

Especially meant to be an introduction to explaining actions.

I believe this is now covered in #510. Another tutorial is scheduled in #522


New header field: license short id

Added header element: single line license short id
init.vim / vimrc:
let g:header_field_license_id = 'BSD-3-Clause'
let g:header_max_size = 8
Result:
#!/usr/bin/env python
# -*- coding: utf-8 -*-
# File              : path/to/something.py
# License           : BSD-3-Clause
# Author            : user<EMAIL_ADDRESS># Date              : 01.01.2017
# Last Modified Date: 02.03.2018
# Last Modified By  : user<EMAIL_ADDRESS>

I will accept it after checking stability. Thank you


Temporal api

fix #2783
Temporal is relatively big, so I want to check if I'm doing it correctly, before adding all of them. I currently only added Temporal.PlainDate and Temporal.Duration.
My specific questions:

Are doc comments ok? I cherry picked and copy pasted them from official docs, so they are js-centeric and low quality for wasm bindgen propose. And they don't have mdn links because there are no mdn page yet. If comments are not deal breaker, they can be omitted and added when mdn pages become appear.
Some functions pass their parameter into some type from's method. Should we use the type in rust side signature, or JsValue is prefered? And similarly some functions are weirdly polymorphic, should we limit the function to its meaningful usage and select proper type?
I added (copy pasted) an entire temporal polyfill in the tests, is it fine? It can be removed when support lands in node, I think.
I putted temporal module in its own file, is there any reason that all js_sys crate is in a single file?
static_method_of doesn't accept ["Temporal", "Duration"] and simple Duration doesn't work (it thinks Duration is in top level), so I added them with js_namespace. From docs functions added in this way should go under Temporal, but they are under their own type. I believe some action is needed here, but I don't know what action.
There is a new js_sys_unstable_apis cfg, so some change in CI testing is probably needed. Or we should go with the same web_sys_unstable_apis?

It should be complete now if I didn't miss anything. I removed the polyfill (so tests are now no-op because no platform currently implemented it) and my problem with static_method_of is solved (it accepts an additional js_namespace)

Thanks!


Add quotes

#Activities done

created new repo called Gitflow-test
Created a branch dev and gave it a default power on GitHub.
Created add quotes branch and added new files to it.
Created a new pull request with dev and Add-quotes branch

comments:

It was nice to try out gitflow.


nntrainer tensor filter data transpose bug

NNTrainer transposes the dimension obtained from nnstreamer but does not transpose the data.
This is a BUG and needs quick resolve.

:octocat: cibot: Thank you for posting issue #695. The person in charge will reply soon.


DocsArchive-<IP_ADDRESS>Auto archive content

Auto archive content from https://github.com/OPS-E2E-PPE/docs-archive-test

Docs Build status updates of commit c0e0f51:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error]

Cannot sync git repo to specified commit because branch Archive_master_2019-09-30-07-09-01 has been deleted or has been force pushed: fatal: Couldn't find remote ref Archive_master_2019-09-30-07-09-01

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Dev maps

Added distance to coast feature

redid changes in a separate file to avoid issues with json merging


Raster jank when displaying many svgs even if wrap ScalableImageWidget with RepaintBoundary and set isComplex to true

I have tried wrapping ScalableImageWidget with RepaintBoundary and setting isComplex to true, but I still encounter raster jank. The raster thread takes longer than 16ms per frame. Is there any way I can improve this performance issue? Or is it a problem with the library or a Flutter issue?
Reproduction
https://github.com/zhuscat/svg_test
Video
tested on release mode
https://github.com/user-attachments/assets/5db18e3e-9dea-48be-8116-f547bc42312d
Env
$ flutter doctor

Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.24.0, on macOS 14.0 23A344 darwin-arm64, locale zh-Hans-CN)
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 15.0)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2023.1)
[✓] VS Code (version 1.92.0)
[✓] Connected device (4 available)

Short of me debugging your application, there's no way for me to know.  I'm sure there's some way you could improve your app's performance, but it's not really my place to figure that out for you.  Try making changes so that it doesn't need to re-render the complex SVG during animation.


GSSOC 2021 Toggle kth bit from right (bit manipulation)

This program would aim at toggling kth bit from right using bitwise operations.
Motivation
This problem could be done by using xor and shift bitwise operator. It would strengthen the basic concepts.
May I start working on this issue in C++. I am GSSOC'21 Participant.

@anushkrishnav please assign me.

@mansi-9 Hi, I assigned you. Happy Coding!😊

Thank you!!!

Awesome @ankitaggarwal23


Update documentation of CI/CD pipeline process

[ ] Update documentation describing the CI/CD pipeline and all processes (build, deploy, package, roll back, release with tags, etc)

Specifically, update existing documentation to support multiple environments and all processes

Updated the document. Initial version of the document is v0.0 since the deployment process and the rollback process has changed since we did the proof of concept in a single environment with the startkit.
https://drive.google.com/file/d/1S1TGjWAuRn-XaIaJ_BHl82MoNiwXChep/view?usp=sharing


How to use upload plugin and  integration with another jquery script

I'm not familiar with jquery at all. I have no idea how to add the upload plugin and make it work. Any help would be appreciated.
Also, this plugin, http://qwertypants.github.io/jQuery-Word-and-Character-Counter-Plugin/, is supposed to append a div, but it ends up inside the Trumbowyg text area (at the bottom) and doesn't work. Any idea how I can still use it?

@rtcunningham1 for your second question I've create an issue in plugin repo at jQuery-Word-and-Character-Counter-Plugin

Thanks. I don't know what all that stuff means but I appreciate the help.

@rtcunningham1 plugin was updated. Now you can use it with Trumbowyg.
Just add a
 for counter and use another selector for plugin init. Something like this:
// Init editor
var editor = $('#form_review').trumbowyg({
	lang: 'ru',
	removeformatPasted: true,
	btns: [ 'formatting', '|', 'btnGrp-design', '|', 'btnGrp-justify', '|', 'btnGrp-lists', '|', 'viewHTML' ]
});
// Init counter
$('.trumbowyg-editor').counter({ // this is a class from the div with contenteditable="true"
	append: false,
	target: '#word-counter'
});
<textarea id="form_review"></textarea>

PS! Be aware when you setup prefix option. You need to update selectors.

@Globulopolis Thanks for the help. Things moved faster than I expected.

Seems to be resolved

nice, but if i want to put 2 or more?

@Fer-Marival you mean multiple editors on one page?
If yes - use loop.


data item related to microbiome detection

Describe the bug
no Plasmodium by microscopy
Definition: a data item that is the specified output of a microscopy assay that has a sample of blood as specified input and indicates that the sample does not contain Plasmodium
Is it a child of EUPATH_0027009 'presence of Plasmodium in blood by microscopy assay'?
Shall indicate sample type in the label, such as 'no Plasmodium in blood by microscopy'
parasite species information
Definition: A data item of which parasite species detected in a blood specimen.
Parent: 'presence of organism in specimen'
Value of 'presence of organism in specimen' should be boolean.
So, I think 1). the parent of the term is not correct. 2). The label should be improved, such as 'parasite species in blood datum'

parasite species information
New label: Plasmodium species in blood by microscopy datum
New definition: A Plasmodium in blood by microscopy datum that specifies the species detected.
New subclass: Plasmodium in blood by microscopy datum
no Plasmodium by microscopy
New label: no Plasmodium in blood by microscopy
New definition: A Plasmodium in blood by microscopy datum that specifies that no Plasmodium was detected.
New subclass: Plasmodium in blood by microscopy datum

related issue: https://github.com/VEuPathDB-ontology/VEuPathDB-ontology/issues/480

The labels and definitions look good to me. But it might be better after discuss the design patterns of organism detection data.


How do you see the delta between two Pipfile.lock files?

I just pipenv update my project and would like to know exactly what packages have been updated.
What is the recommand way to do that?
What I would expect to
I would expect something like this exist:
$ pipenv diff Pipfile1.lock Pipfile2.lock
> The following packages changed:
package1: old: 6.20, new: 6.21
package2: old: 3.2, new: 3.3

As Pipfile.lock file is really easy to parse (JSON), I would not be surprised if something like this already exist and I just missed it.
What I tried so far

Making a unix diff between the old Pipfile.lock and the new one does not really work, because you don't see the name of the package that changes in the output.
Running pipenv graph before running pipenv update and saving the output to a file, for comparing them later. It kind of works, but the whole process is a bit complicated. Plus, if you forget to save the result of pipenv graph before updating, it's too late.

EDIT
I made a very simple script to handle that: https://gist.github.com/ddahan/215472a4aa1805160aba0a77902e40da
Usage example:
$ /usr/local/bin/python3.6 pipenvdiff.py Pipfile.inprod.lock Pipfile.current.lock

django-cors-headers: 2.3.0 -> 2.4.0
django-extensions: 2.0.7 -> 2.1.0
faker: 0.8.16 -> 0.8.17
ipython: 6.4.0 -> 6.5.0
lxml: 4.2.3 -> 4.2.4
openpyxl: 2.5.4 -> 2.5.5
parso: 0.3.0 -> 0.3.1
stripe: 1.84.1 -> 2.4.0

By the way, I was thinking that making the tool would be shorter than getting an answer, so here is the very simple Python script I made for that: https://gist.github.com/ddahan/215472a4aa1805160aba0a77902e40da

There is also pipenv update --outdated, but that only applies for top-level dependencies (i.e. those you specify in Pipfile).
This is definitely intriguing, and I can definitely find use of this in my own workflow 🤔 Something like pipenv update --dry-run might be good as well[1]; it can do the whole locking process, but instead of writing to Pipfile.lock, it can show a list to indicate what entries in Pipfile.lock would change.
[1]: This option is already present, but the current behaviour is identical to --outdated.

@uranusjr But even with pipenv update --outdated, since you update your Pipfile.lock after running the command, you have no guarantee that your new Pipfile.lock will contain exactly what was listed in pipenv update --outdated output.
For me, the only way to be 100% sure of the installed packages are to compare the Pipfile.lock files.
For now, I'm happy with my simple script, but I hope this could be integrated in pipenv project.

would be great to have a version of this script that leverages git to list the changes.

I believe most folks check their Pipfile.lock into source control and see the deltas on PRs.


Make SplatComposer respect dtype

Closes #235.

Codecov Report

Merging #236 into master will decrease coverage by 0.03%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #236      +/-   ##
==========================================
- Coverage   88.59%   88.56%   -0.04%
==========================================
  Files          16       16
  Lines        1771     1775       +4
==========================================
+ Hits         1569     1572       +3
- Misses        202      203       +1

Impacted Files
Coverage Δ

hybrid/utils.py
76.59% <100.00%> (+0.68%)
:arrow_up:

hybrid/flow.py
92.79% <0.00%> (-0.28%)
:arrow_down:

Continue to review full report at Codecov.

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


[Master] Admin pods left behind causing SmokeTest run failure

I am running the brokered.SmokeTests locally.  Occasionally tests are failing owing to an orphaned admin pod that belonged to a deleted addresspace.
The issue is a defect in Fabric8 kubernetes-client 4.6.2 on the code path when deleting deployments using a selector (io.enmasse.controller.common.KubernetesHelper#deleteResourcesNotIn).  Internally io.fabric8.kubernetes.client.dsl.internal.DeploymentOperationsImpl.DeploymentReaper#reap first scales the deployment to 0 then goes on to delete the replicaset.  The race is between the Kubernetes runtime actioning the scaling of the pods to zero and the deletion of the replicaset.
In the unlucky case, the replicaset is deleted before the pods are terminated.  As the replicaset delete is made without a delete propagation or orphanDependents false (the delete propagation / orphanDependents wishes from the API are not propagated) , the pods are left behind.
This issue does not exist in a released EnMasse version.

I suspect that this is the same issue.  https://github.com/fabric8io/kubernetes-client/issues/1859


Add compression

Based on header flags compress/decompress json

Looks like there is already compression middleware here
app.UseResponseCompression();


Enhance docs for the "non SSR" rendering case of the main.ts

The main.ts does not seem to be different for having SSR active or not


Foundry, EIP 1559 Not Support

[ Foundry Smartcontract ]
Description
Trying to deploy smartcontract using Foundry but EIP-1559 Not Support
Your environment

OS and version : Ubuntu
The version of the Polygon Edge : v0.6.0 - v0.6.1

Steps to reproduce
forge update
forge create --contracts <path/contracts> \
--rpc-url <localhostRPC> \
--private-key <priv-key> \
--constructor-args:Contract

Expected behavior
Successful Deployed
Logs Foundry
Foundry EIP-1559 Not Support

Hi @avenbreaks ,
Unfortunately, Edge doesn't support EIP-1559.


[Bug?]: Issue: cant find graphql API

What's not working?
Issue: cant find graphql API
How do we reproduce the bug?
Cant find the graphql api
What's your environment? (If it applies)
No response
Are you interested in working on this?

[X] I'm interested in working on this

@pullflow-ai where can i find info about the graphql api ?


How to foreach each pixel color?

Hello, not a lot to go on here but did you see raw to access raw pixel data? #934 may help too here.

Will assume this helped, please re-open with more information if not.


Enabling the plugin prevents archivesspace from starting with JRuby error

Error message from log
You're seeing this error because you use JRuby::Rack::ErrorApp::ShowStatus.
Configuration:  RHEL 7.4, Apache 2.4.6, php 5.6.33, MySQL 5.6.39, archivesspace 2.3.1, header and style customizations in plugins/local/public

Hi,
There should have been an actual error (like: Bundler could not find compatible versions for gem "method_source":  etc..)  I can't diagnose the problem  immediately with the information provided.  Also: please confirm what version of the plugin you are using.
Thanks!

Bobbi,
Thanks for replying to my issue.  Here is what I am seeing as the actual error:
Could not find gem 'rubyXL (= 3.1.0) java' in any of the gem sources listed in your Gemfile or available on this machine.
from /opt/ArchivesSpace/archivesspace/gems/gems/bundler-1.12.5/lib/bundler/resolver.rb:356:in block in verify_gemfile_dependencies_are_found!'         from org/jruby/RubyArray.java:1734:in each'
from /opt/ArchivesSpace/archivesspace/gems/gems/bundler-1.12.5/lib/bundler/resolver.rb:331:in verify_gemfile_dependencies_are_found!'         from /opt/ArchivesSpace/archivesspace/gems/gems/bundler-1.12.5/lib/bundler/resolver.rb:200:in start'
from /opt/ArchivesSpace/archivesspace/gems/gems/bundler-1.12.5/lib/bundler/resolver.rb:184:in resolve'         from /opt/ArchivesSpace/archivesspace/gems/gems/bundler-1.12.5/lib/bundler/definition.rb:200:in resolve'
from /opt/ArchivesSpace/archivesspace/gems/gems/bundler-1.12.5/lib/bundler/definition.rb:140:in specs'         from /opt/ArchivesSpace/archivesspace/gems/gems/bundler-1.12.5/lib/bundler/definition.rb:185:in specs_for'
from /opt/ArchivesSpace/archivesspace/gems/gems/bundler-1.12.5/lib/bundler/definition.rb:174:in requested_specs'         from /opt/ArchivesSpace/archivesspace/gems/gems/bundler-1.12.5/lib/bundler/environment.rb:19:in requested_specs'
from /opt/ArchivesSpace/archivesspace/gems/gems/bundler-1.12.5/lib/bundler/runtime.rb:14:in setup'         from /opt/ArchivesSpace/archivesspace/gems/gems/bundler-1.12.5/lib/bundler.rb:95:in setup'
from /opt/ArchivesSpace/archivesspace/gems/gems/bundler-1.12.5/lib/bundler/setup.rb:19:in <main>'         from org/jruby/RubyKernel.java:961:in require'
from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:133:in require'         from /opt/ArchivesSpace/archivesspace/data/tmp/jetty-<IP_ADDRESS>-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:1:in <main>'
from org/jruby/RubyKernel.java:961:in require'         from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55:in require'
from /opt/ArchivesSpace/archivesspace/data/tmp/jetty-<IP_ADDRESS>-8089-backend.war--any-/webapp/WEB-INF/app/main.rb:1:in block in (root)'         from org/jruby/RubyBasicObject.java:1687:in instance_eval'
from /opt/ArchivesSpace/archivesspace/data/tmp/jetty-<IP_ADDRESS>-8089-backend.war--any-/webapp/WEB-INF/config.ru:1:in (root)'         from /opt/ArchivesSpace/archivesspace/data/tmp/jetty-<IP_ADDRESS>-8089-backend.war-_-any-/webapp/WEB-INF/config.ru:4:in <main>'
from launcher/launcher.rb:92:in start_server'         from launcher/launcher.rb:157:in main'
from launcher/launcher.rb:261:in `<main>'
We are running v 2.1.2 of the plugin and Aspace 2.3.1
Hope this helps!
Thanks,
Steve
From: Bobbi Fox at Harvard LTS<EMAIL_ADDRESS>Sent: Friday, March 16, 2018 1:51 PM
To: harvard-library/aspace-import-excel<EMAIL_ADDRESS>Cc: Williamson, Steven C<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [harvard-library/aspace-import-excel] Enabling the plugin prevents archivesspace from starting with JRuby error (#24)
Hi,
There should have been an actual error (like: Bundler could not find compatible versions for gem "method_source": etc..) I can't diagnose the problem immediately with the information provided. Also: please confirm what version of the plugin you are using.
Thanks!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/harvard-library/aspace-import-excel/issues/24#issuecomment-373793481, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Af4mISBmSa81o7jUGRulM1Im78Mt9FF9ks5te_tvgaJpZM4StwwK.

Hi, Steve, thanks for getting back to me.
I'm not a complete expert on ArchivesSpace compiling, but it looks like you didn't run the
the scripts/initialize-plugin script?
for Linux, that's scripts/initialize-plugin.sh aspace-import-excel
for Windows, that's scripts/initialize-plugin.bat aspace-import-excel
That should have installed the RubyXL on your server.
Is it possible that you ran the initialize-plugin, but got errors?

No, but it’s very possible I never ran the initialize plugin script.  Senior moments are starting to occur more frequently.
Thanks for your help and pointing me in the right direction.  That solved the problem and all seems to be working.  It always helps to follow the directions. ☺
Steve
From: Bobbi Fox at Harvard LTS<EMAIL_ADDRESS>Sent: Monday, March 19, 2018 11:45 AM
To: harvard-library/aspace-import-excel<EMAIL_ADDRESS>Cc: Williamson, Steven C<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [harvard-library/aspace-import-excel] Enabling the plugin prevents archivesspace from starting with JRuby error (#24)
Hi, Steve, thanks for getting back to me.
I'm not a complete expert on ArchivesSpace compiling, but it looks like you didn't run the
the scripts/initialize-plugin script?
for Linux, that's scripts/initialize-plugin.sh aspace-import-excel
for Windows, that's scripts/initialize-plugin.bat aspace-import-excel
That should have installed the RubyXL on your server.
Is it possible that you ran the initialize-plugin, but got errors?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/harvard-library/aspace-import-excel/issues/24#issuecomment-374259117, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Af4mIUmVPLExEeEYWqRz5hn2tSqc-SdRks5tf9JpgaJpZM4StwwK.

Glad to hear it's working now!  I'll close out the issue.
Cheers,
Bobbi


Convert communication q_due_date to user's TZ

https://www.pivotaltracker.com/story/show/151540337

modified questionnaire_due_date for LR-generated Communication emails, to convert from UTC to the user's TZ (as that may modify the due date by +/- 1), if user TZ is set
added tests for questionnaire_due_date (without and with user TZ)

added new setdate param to bless_with_basics(), to make sure we can test a time where converting to another timezone would affect the day

@pbugni Should the intervention_strategies fix be part of this PR? Or should we go ahead and get this change in, then add that separately?

@OptimusRhine fair - let's file as a separate issue.  Merging.


Added SPM support

Yes, this project seems pretty dead as it hasn't been updated in years, but if you're still using it, and want SPM support, I've added it.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Andy Johns seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

please merge


add static file paths option

Added the ability to specify paths to static files that will be added to the kodata.
This can be useful, for example, for adding migrations and configs that are in different folders, so as not to add everything to the kodata folder.
Support glob syntax.

Hey, first of all, thanks for this contribution!
In general when I've used ko and needed to get files in to kodata that aren't already, I just symlink them -- ln -s static/ kodata/static/. ko chases those symlinks* at build time to put them into the tar layer. Is there a reason symlinks aren't appropriate in your use case? We might just want to document this convention better, so folks know it's possible and supported.
I'm a little worried about the semantics of supporting multiple static file paths. The rules around evaluation order and who wins can get difficult to implement, and more importantly difficult to document and test. I'm also not sure of the use case for this, but I'm interested to hear more. This would also be supported by the symlink flow, AFAIK, since you could ln -s a kodata/a and ln -s b kodata/b, and even have more control over how those paths are mapped into the kodata directory. I admit I've never done it though, so it may still be confusing in practice.
(*except on Windows where there's a bug)

Exatly because of windows, since most of our team's development machines are on windows - we're not able to use symlinks.
Also, the way it is achieved via symlinks - you have to do it again and again on separate machines and within CI pipeline, if done via config - it is way more obvious and robust.
There is no worries on my side about semantics, tbh -  globs treated relative to main, files can be overwritten, copying evaluated in defenition order.

Exatly because of windows, since most of our team's development machines are on windows - we're not able to use symlinks.

I'd like to understand the issue with symlinks on Windows more before we build such a workaround for it. That's not to say we won't go the direction of this PR, just that I'd like to give symlinks on Windows another shot and see if we can support it after all.
For instance, is the issue that running ko on Windows to build a linux/amd64 image doesn't support symlinks? That sounds like your issue, right? Or is it that running ko from a Linux machine to build windows/amd64 images doesn't work?
The symlink-skipping logic was added in https://github.com/ko-build/ko/pull/374/ which added support for cross-compiling linux->windows, but it sounds like the real issue is just running ko on Windows. Understanding the issue more may help us fix it once and for all.

Also, the way it is achieved via symlinks - you have to do it again and again on separate machines and within CI pipeline, if done via config - it is way more obvious, robust, and, again, crossplatform.

Symlinks are just special files, which get committed to your repo (example), so there shouldn't be any need for any setup on each CI run.

There is no worries on my side about semantics, tbh -  globs treated relative to main, files can be overwritten, copying evaluated in defenition order.

That's all well and good, but your conception of the semantics may not match someone else's idea, leading to surprises, so we'd need to document it thoroughly, and add examples and tests for lots of different cases.
Adding this functionality may also lead to future feature requests to let folks change those semantics, because we've opened the door. Symlinks are (despite their issues on Windows...) fairly standard and well-known. You can inspect them to see exactly where they point. They're version-controlled files in the repo.
Again, I'm not saying we won't support some form of a flag that lets you override kodata -- and thanks again for submitting a PR, which makes it easier to tell roughly how much work would be needed, and where -- but I think there's more we need to discuss and investigate before merging this.

And a followup: I've just tested a change that removes the special symlink handling code for Windows images, and runs the e2e test for it on a Windows CI runner, and it passes: https://github.com/imjasonh/ko/actions/runs/3321410053/jobs/5489018396
So perhaps symlinks on Windows do work? If it turns out they do, would this be a suitable solution to your issue?

Main issue was with ko not following symlinks on windows, second - i havent tried symlinks on windows for many years since that had to be an absolute path, therefore i said that it is not usable between machhines.
I really dont like to have ko's configuration smeared over repo, configuration via placing symlinks in separate folder with specific name (configuration it is) is worse opportunity than having it within build config.

Additional example - we have single project structure for our microservices. Since need of maintaining kodata directory we either have to put migrations and base config-file to kodata folder which is counterintuitive, or to maintain {number-of-microservices} kodata directories with symlinks inside, wheras using yaml inheritance it could be done with a singular config.

globs are not less standatd and well known that symlinks, imo🙃 (for windows users, most likely, symlinks are less know wood than glob patterns)

Main issue was with ko not following symlinks on windows, second - i havent tried symlinks on windows for many years
...
So i'd rather say that symlinks on Windows are broken as a whole.

That's unfortunate. Windows' inconsistent/broken support for symlinks is pushing me toward having this supported in another way.

I really dont like to have ko's configuration smeared over repo, configuration via placing symlinks in separate folder with specific name (configuration it is) is worse opportunity than having it within build config.

Additional example - we have single project structure for our microservices. Since need of maintaining kodata directory we either have to put migrations and base config-file to kodata folder which is counterintuitive, or to maintain {number-of-microservices} kodata directories with symlinks inside, wheras using yaml inheritance it could be done with a singular config.

That's also a compelling argument. It's not so bad when there's 1-2 package mains in a repo, but it gets unwieldy when there are many symlinking their kodatas to the same places.
However, the fact that staticFilePaths can also be configured in YAML in this PR means there's yet another dimension of documentation and testing needed -- what happens when a build has staticFilePaths configured in YAML, and ko is also invoked with the --static-file-paths flag? Should the flag override completely, or append to the YAML's paths? I don't have a strong preference for the answer, just that whatever it is gets thorough tests and documentation and examples.

globs are not less standatd and well known that symlinks, imo🙃 (for windows users, most likely, symlinks are less know wood than glob patterns)

Simple globs are well defined, e.g., filepath.Glob, but it may open the door for requests for "extended globs", e.g., path/foo/**/bar.*, which are not specified well at all, and aren't supported in Go stdlib. We may just want to support simple directories at first, rather than trying to support globs.
Is your use case satisfied by having one --static-file-path value? This would simplify the problem space quite a bit, and make it easier to accept the change. It would also give us room to add support for multiple values in the future, based on usage and demand.

Our use case, unfortunately for you proposal contains both file and directory have to be collected with following semantics of service
- some-other-folders-with-static/
- migrations/
- config.yml
- main.go

some-other-folders-with-static is inconsistent between services, but nonetheless they're exist.
About the duality of definition, if i would do it - i'd made CLI parameters to be extend config file or strip the ability of passing cli parameter at all.

@imjasonh Hey! What do you think about our case? I suggest to strip the ability of passing cli parameter to simplify the problem.


Highlight delimited documentation comments /** */

Issue Type: Feature Request
According to the C♯ specification, there's a delimited documentation comment syntax, and VS Code supports this (eg, Intellisense).
However, the XML in delimited documentation comments such as
/**
<summary>
	Filler
</summary>
*/

is not getting syntax highlighting that single line comment syntax such as
/// <summary>
/// 	Filler
/// </summary>

is getting.
Can this be added?
Extension version: 1.18.0-beta7
VS Code version: Code 1.31.1 (1b8e8302e405050205e69b59abb3559592bb9e60, 2019-02-12T02:20:54.427Z)
OS version: Windows_NT x64 10.0.17763

Moved to https://github.com/dotnet/csharp-tmLanguage/issues/151


Published testimony counter

Summary
A fix for the view testimony pagination summary. Closes #1361.
Adds a call to firestore in the profile page to get the number published testimony of the user
/users/${profileprops.id}/publishedtestimony
this is necessary because the usePublishedTestimonyListing hook which we use returns the testimony page by page, without a total.
Screenshots

# Known issues
It's possible that this action should be refactored as part of usePublishedTestimonyListing or another hook.
Steps to test/reproduce

Go to a profile page
See the summary of testimony pages -- eg viewing 21-30 of 45
Page through the testimony and see if the numbers are correct

I mostly think the PR is great and would otherwise approve and merge but I had an odd wrinkle:
on my test org account:
http://localhost:3000/profile?id=8P5Ar8NyAcNEVJMTexezXvRbept2
I got this:

where Array of Actually Displayed Testimony is a console.log of "testimony" per ln 35 of ProfilePage\ProfilePage.tsx
and Total User Pub Testimony is a console.log of (per ln 50) publishedTestimony.size
sure enough, 10 individual testimonies are Actually Displayed, while my counter read 1-10 out of 11

when I hit the >> button per the above image, I get this:

Thanks @mertbagt !!!!
Looks like the snapshot from the users publishedTestimony collection was returning & counting undefined documents along with the actual documents.
I used a query on the collectionGroup where(id === profileId)  instead and that seems to behave as expected.

:rocket:


Fix pitch data overhangs in freq domain

Just noticed that the data pitch labels are wrong. Many beginnings and endings of the pitch seem to overhang like in the picture below. This is totally unacceptable and very possibly the cause of the poor raw pitch accuracy of around 80%.

Fix that!
Check:

labels in the original dataset
data preprocessing when creating the gset dataset

After the initial review of the original data sets my conclusion is that the dataset is really bad or at least the pitch values are. Every ending is indeed seen noted as falling down in pitch, even though such fall isn't audible in the recordings (not even those with the separated strings). This means that the dataset needs to have those endings cut manually or have all the pitch tracking redone with a better method, perhaps with the original penn?

There must be a problem with the data processing, the nodes that are so much below the other ones do not exist in the labeled data:

Some data seems to be missing, this is indeed missing as it is present in the audio. The next step is to write a program printing the original data labels over the STFT image. I don't see any other way than comparing what was there originally with what I got after preprocessing.

This is already slightly better, got rid of putting 'zeros' into the almost raw data, it seems that all the overhangs are still there, but at least not the most ridiculous ones, again file 05_BN3-119-G_solo_mic.wav.

It could be possible to slighly help with deleting the unwanted values with plotly!
https://plotly.com/python/v3/selection-events/?_gl=1*1fq1w1w*_ga*MTI0MDkzODAyNy4xNzA1NDM5MTky*_ga_6G7EE0JNSC*MTcwNjgyNTcxNi4zLjEuMTcwNjgyODM2NC41MS4wLjA.

I was really hoping that midi would help with seeing where the proper parts of the node end, sadly that is not the case.
Anyway, midi is now printed on top of the spectrogram and pitch data. The next step is to try to fix the endings of the pitch notes with some kind of a simple algorithm.
This is what the plot looks like now:

Another small break through. Resampling was obviously the issue! To get rid of unwanted fields in strange spots that were not in the original data it was enough to disable resampling for sampling rates that divide the GuitarSet native sampling rate of 44100 Hz without a remainder - that leaves the 11025, 22050 sampling rates without the need to resample.


Fix for https://github.com/autonomio/talos/issues/263

Hello @JohanMollevik! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file talos/metrics/entropy.py:

Line 42:61: E225 missing whitespace around operator
Line 42:80: E501 line too long (90 > 79 characters)
Line 48:63: E225 missing whitespace around operator
Line 48:80: E501 line too long (93 > 79 characters)

Pull Request Test Coverage Report for Build 427

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 90.056%

Totals

Change from base Build 424:
0.0%

Covered Lines:
1123

Relevant Lines:
1247

💛  - Coveralls

Pull Request Test Coverage Report for Build 427

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 90.056%

Totals

Change from base Build 424:
0.0%

Covered Lines:
1123

Relevant Lines:
1247

💛  - Coveralls

Pull Request Test Coverage Report for Build 427

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 90.056%

Totals

Change from base Build 424:
0.0%

Covered Lines:
1123

Relevant Lines:
1247

💛  - Coveralls

Related with #268

This had been since then fixed, so closing here.


Nogoods: Fix index of head

I recently realized that we (nearly?) always use NoGood.headFirst whenever we create nogoods with head. We could simplify our nogoods such that the head (if present) is always at a fixed index. This would make some things easier (for example there is a TODO in DependencyDrivenHeuristic asking for that).
But it might make other things harder...
Currently, nogoods are sorted, so it is not guaranteed that the head will remain at index 0.
👍 or 👎 ?

Good question, I'd like to add another one: do we need NoGood IDs? My original concern was that we need some way to identify identical nogoods in order to avoid adding the same nogood twice to the solver. If I am not mistaken, this functionality, however, is never used since all relevant code uses NoGood.equals (which in turn requires that the literals of the NoGood are sorted).
What are the things that might get harder if the head is at a fixed position?
Note that we still need an indicator for whether that position is a head or not (and this must be checked by NoGood.equals. More than half of our nogoods have no head, so it should not make less efficient with them.

Indeed, I also asked myself why we keep IDs today ...
If I remember correctly, this was intended so that grounder and solver may exchange information about particular nogoods. For example, the solver might tell the grounder to forget nogoods. If they do not have IDs, then we would need another trick here.
So the sorting in the constructor is there to speed up equality checks? In this, we might as well argue that the head is a special literal anyway. We can check it explicitly in equals and still keep the sort order for body literals.

bcba2a0 part of #83  ✨

Landed with #83


[Feature Request] Screenshot Helper Granularity Options

I love Screenshot Helper as it helps me figure out what world I was in when I took a photo, but I hate that it also is sort of privacy invasive as it exposes everyone who was in the instance at the time. I'd love to be able to keep the World ID data but not the players in the instance.

True. I feel like I thought of this when I first implemented it but then forgot about it. I'll prob add options for it soon


unsorted keys in ng-repeat "(key, value) in myMap"

Hi team,
Don't know is that a feature or bug, but in all Angular versions until 1.4.0 keys were sorted alphabetically, but not in 1.4.0/1.4.1
div ng-repeat="(key, value) in myMap">    {{ key }}
Check a plunker:
http://plnkr.co/edit/J0ctwgN2jLOH98LCNegx?p=preview

This is a (documented) breaking change in v1.4 (which has been requested for quite zealously: #6210).


How to  set dynamic match cost during the training process?

Hello, if I want to make the regression cost of the bounding box gradually increase during the training process, how could I do it?
That's mean How could I get the current and total num of epochs during the training process and calculate  the regression cost when match the sample and predictions.

The iteration and epoch information are in the runner https://github.com/open-mmlab/mmcv/blob/f4167fe1e3d106cd641708d269ddbff568393437/mmcv/runner/base_runner.py#L131,
and https://github.com/open-mmlab/mmcv/blob/master/mmcv/runner/epoch_based_runner.py
You can pass the information into model, them pass them to the match cost.


Release v1.1.1-rc2

Version changes:

UI: v1.1.1-rc2
Installer: v1.1.1-rc2
Deps

kubevirt: 0.54.0-1504<IP_ADDRESS> (patched version)
support-bundle-kit image: v0.0.12

Upgrade matrix: minimum v1.0.3

Codecov Report

:exclamation: No coverage uploaded for pull request base (v1.1@1faf275). Click here to learn what that means.
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##             v1.1    #3177   +/-   ##
=======================================
  Coverage        ?   19.38%
=======================================
  Files           ?       59
  Lines           ?     6227
  Branches        ?        0
=======================================
  Hits            ?     1207
  Misses          ?     4894
  Partials        ?      126

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Fix C/C++ grammar to allow symbols and spaces in path

Had issues with spaces in the path when running C/C++ scripts. This should allow spaces and symbols in the path, though filenames with ' won't work and would still need to be escaped.

Awesome, thanks.


Clarify use of Device Credentials for Azure Virtual Desktop

The NOTE section regarding User vs Device credentials and its reference to Azure Virtual Desktop support is misleading.  Updated the note with a link to specify that Device Credential is only supported for MULTI-SESSION host pools, with a link for reference, and User Credential is still supported for personal host pools.

Learn Build status updates of commit 3914956:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

windows/client-management/enroll-a-windows-10-device-automatically-using-group-policy.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
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.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Thanks @cameron-doherty for the contribution! I've merged this PR 👍


Provide Dockerfile for thin-edge.io to run within containers

Is your feature request related to a problem? Please describe.
Many gateways only provide the possibility to use containers since they hardly relay on standard libraries and do not want them to be changed. There is currently no provided official Dockerfile for running the thin-edge.io within an container.
Describe the solution you'd like
A Dockerfile that provided the possibility to build an image for thin-edge.io that directly brings all features and functionalities.
Maybe provide the container also on Docker hub as well.
Describe alternatives you've considered
Native installation is in several gateways and use cases not possible. Building up an own Dockerfile partly worked since some of the processes can not be automized.

Good Point, #505 states a request to get rid of systemd dependency, which would be also meaningful for this issue as docker containers typically are/should not be equipped with systemd.

There is a first step in that direction https://github.com/thin-edge/thin-edge.io_examples/pull/23 with all the daemons in a single container using alpine and without systemd.
We still have to work so thin-edge can  be deployed over several Docker containers for mosquitto, the mapper and the agent.
However, there is no plan to support these docker images.

Relates to #1563

The tedge-demo-container project has been created to provide a "everything and the kitchensink" approach to getting thin-edge.io running in a systemd environment to simulate running on a real device (without requiring a real device).


Bluesky: truncate string values to length limits

Lexicons can include length limits for some fields, eg 300 graphemes for app.bsky.feed.post text. The relay (or AppView?) checks length limits in record validation and drops records if any fields are over their limit. We need to handle this in bluesky.to/from_as1.
Ideally we'd bundle the lexicons themselves and look up and use per-field length limits automatically. Not sure I want to go that far though. Alternatively we could do this in lexrpc, with an option to truncate values that are too long.

granary already has lexrpc as a dependency! So I did this in both places.


Expose read functionality from Adapter through Struct interface

I've made this pull request as it is a small change and might be a good change. Code generation was fixed for both languages (Java and Kotlin) as well.
Similarly as Adapter#write() was exposed, I'm exposing it Adapter#read() as well.
This is a small change and not necessarily a valid case.
Looking forward to your feedback.
Thank you!

Does my suggestion above work for you?  Please let me know, so we can close this issue (assuming it works).

Since I haven't heard back in three weeks, I'm going to assume that your needs are now met and close the PR.  Please re-open if that's not the case.  Thanks!


Fixed syntax in code example

https://wintercms.com/docs/database/traits#custom-error-messages

Thanks @WebVPF!


Improve readability of the Episode overview

The overview at the start of an episode is really hard to read in desktop mode when the episode menu is expanded. If Expand All Solutions was moved to another location, so that the Overview can utilise the entire parent div, I think this would improve it by a lot.

Alternatively, you could set the child divs in the Overview to be rows rather than columns, so that they are always stacked vertically rather than horizontally. But that will not look great when the episode menu is collapsed.
In terms of suggestions to where the expand all solutions could be, I think it could fit in the Episode menu or right below the Overview. I also think it could benefit from getting some styling, like being a button or something.

Thank you for opening this and providing suggestions, @drmowinckels.
This is part of a broader sticky issue that currently exists in https://github.com/carpentries/varnish/issues/83, https://github.com/carpentries/sandpaper/issues/299, and https://github.com/carpentries/workbench/discussions/10#discussioncomment-2938302
We are still running a bit of a backlog at the moment, so it may take some time for this to get resolved.

Sorry for missing other places where this is mentioned.
I'm pretty naive to lua filters, so I cant really grasp it completely, but from the code here I think I get the gist of what is going on.
So, if Objectives and Questions are set as bootstrap cards, could you not have them in a row div, and have them wrap on top of each other when needed through bootstrap columns of even a flex container?
I think doing that, and moving the expansion to its own "row" would make the behaviour of that block much neater.
That being said, I can see its a finicky one to solve.

right-o! I tried in incognito and the overview is looking so much better! Much more like yours. I still think the questions section should have a little more space, but its not like it was at all. I try to figure out which specific extension might be doing it and get back to you.

I've been looking at this again, and there's some interesting behaviour related to the .card-title font sizing. At font-size 24px, the default, I see the reported behaviour.
However, upon reducing the .card-title font-size to 22px, the problem goes away:

This makes me wonder that it's a screen resolution vs browser window size font scaling issue rather than a particular class or CSS property messing with anything. Looking at varnish's overview.scss it seems that the .card-title font-size is fixed. Could a solution be to use the $font-sizes sass map to automatically scale heading text (https://getbootstrap.com/docs/5.0/utilities/text/#maps)?

Fixed with https://github.com/carpentries/varnish/pull/109


Enable not starting views in navigation integrations

What does this PR do?
Enable to drop views in navigation integrations.
For react-navigation, the implementation is quite straightforward.
For react-native-navigation I had to change the approach as we were stopping all the views that were removed from the hierarchy. In reality there is no need for this, as views are stopped when a new one is started.
By keeping this behaviour we could have an issue in the following scenario:

user is on screen with key A
user goes to another screen that is dropped from the predicate
user goes back

the screen is removed from the hierarchy, so it DdRum.stopView is called
if the 2nd screen had a different key than the 1st, DdRum.stopView will silently fail (I think)
if they had the same key, we stop the first View and now no view is registered

I also implemented stopping views when going in background for react-native-navigation.
This new implementation also solves the (very small) memory leak that was in the previous implementation.
Motivation
Add support for not starting views in navigation integrations
Review checklist (to be filled by reviewers)

[x] Feature or bugfix MUST have appropriate tests
[x] Make sure you discussed the feature or bugfix with the maintaining team in an Issue
[x] Make sure each commit and the PR mention the Issue number (cf the CONTRIBUTING doc)
[x] If this PR is auto-generated, please make sure also to manually update the code related to the change

TODO: prevent the first app state listener to trigger an error as no view is set -> maybe set lastView to something of different shape


Feature- makefile

Create makefile
Description
To create a makefile so that the code running becomes simpler
Resources
https://www.geeksforgeeks.org/how-to-use-make-utility-to-build-c-projects/

** Bounty points alloted : 40 **
Any further improvements along with bug fixes will be given brownie points. If the
contributor
sees any further improvements that can be done to this project, raise an issue.

Kindly assign me this issue

I really want to work on this issue, can you please assign it to me?

can i be assigned to this issue?

Sure!

yo can i work on this


Encountering 403 (Forbidden) Error even using latest version of Bloxstrap

Acknowledgement of preliminary instructions

[X] I have read the preliminary instructions, and I am certain that my problem has not already been addressed.
[X] I have thoroughly looked through the available Wiki articles and could not find a solution to my problem.
[X] I am using the latest version of Bloxstrap.
[ ] I did not answer truthfully to all the above checkboxes.

What problem did you encounter?
This issue should be fixed with downloading latest version but it doesn't so i guess it might be a bugs of the programs itself and only me encountered this?

Bloxstrap Log
2024-10-03T17:55:02Z [App::OnStartup] Starting Bloxstrap v2.7.0
2024-10-03T17:55:02Z [App::OnStartup] Compiled Wednesday, 10 July 2024 at 1:03:19 AM from commit a7d2a2c3d5af7137804416ba4e5fbdd27bd10f1e (tag/v2.7.0)
2024-10-03T17:55:02Z [App::OnStartup] Loaded from %UserProfile%\Downloads\Bloxstrap-v2.7.0.exe
2024-10-03T17:55:02Z [LaunchSettings::Parse] Parsing launch arguments
2024-10-03T17:55:02Z [LaunchSettings::Parse] No launch arguments to parse
2024-10-03T17:55:02Z [JsonManager::Load] Loading from %UserProfile%\AppData\Local\Bloxstrap\Settings.json...
2024-10-03T17:55:02Z [JsonManager::Load] Loaded successfully!
2024-10-03T17:55:02Z [JsonManager::Load] Loading from %UserProfile%\AppData\Local\Bloxstrap\State.json...
2024-10-03T17:55:02Z [JsonManager::Load] Loaded successfully!
2024-10-03T17:55:02Z [JsonManager<Dictionary2>::Load] Loading from %UserProfile%\AppData\Local\Bloxstrap\Modifications\ClientSettings\ClientAppSettings.json... 2024-10-03T17:55:02Z [JsonManager<Dictionary2>::Load] Loaded successfully!
2024-10-03T17:55:02Z [FastFlagManager::SetValue] Changing of 'FFlagHandleAltEnterFullscreenManually' from 'False' to 'False' is pending
2024-10-03T17:55:02Z [RobloxDeployment::TestConnection.https://setup.rbxcdn.com] Connecting...
2024-10-03T17:55:02Z [HttpClientLoggingHandler::ProcessRequest] GET https://setup.rbxcdn.com/version
2024-10-03T17:55:02Z [RobloxDeployment::InitializeConnectivity] Testing connectivity...
2024-10-03T17:55:03Z [HttpClientLoggingHandler::ProcessResponse] 200 OK https://setup.rbxcdn.com/version
2024-10-03T17:55:03Z [RobloxDeployment::InitializeConnectivity] Got https://setup.rbxcdn.com as the optimal base URL
2024-10-03T17:55:03Z [Logger::Initialize] Initializing at %UserProfile%\AppData\Local\Bloxstrap\Logs\Bloxstrap_25671003T175503Z.log
2024-10-03T17:55:03Z [Logger::Initialize] Finished initializing!
2024-10-03T17:55:03Z [NotifyIconWrapper::NotifyIconWrapper] Initializing notification area icon
2024-10-03T17:55:04Z [App::OnStartup] Initializing bootstrapper
2024-10-03T17:55:04Z [App::OnStartup] Initializing bootstrapper dialog
2024-10-03T17:55:04Z [Bootstrapper::Run] Running bootstrapper
2024-10-03T17:55:04Z [Bootstrapper::Run] Performing connectivity check...
2024-10-03T17:55:04Z [Bootstrapper::SetStatus] Connecting to Roblox...
2024-10-03T17:55:04Z [RobloxDeployment::GetInfo] Getting deploy info for channel LIVE (extraInformation=False)
2024-10-03T17:55:04Z [HttpClientLoggingHandler::ProcessRequest] GET https://clientsettingscdn.roblox.com/v2/client-version/WindowsPlayer/channel/LIVE
2024-10-03T17:55:04Z [HttpClientLoggingHandler::ProcessResponse] 200 OK https://clientsettingscdn.roblox.com/v2/client-version/WindowsPlayer/channel/LIVE
2024-10-03T17:55:04Z [Bootstrapper::Run] Connectivity check finished
2024-10-03T17:55:04Z [Bootstrapper::CheckForUpdates] Checking for updates...
2024-10-03T17:55:04Z [HttpClientLoggingHandler::ProcessRequest] GET https://api.github.com/repos/pizzaboxer/bloxstrap/releases/latest
2024-10-03T17:55:05Z [HttpClientLoggingHandler::ProcessResponse] 200 OK https://api.github.com/repos/pizzaboxer/bloxstrap/releases/latest
2024-10-03T17:55:05Z [Bootstrapper::CheckForUpdates] No updates found
2024-10-03T17:55:05Z [RobloxDeployment::GetInfo] Getting deploy info for channel zassetcacheinitprod (extraInformation=False)
2024-10-03T17:55:05Z [HttpClientLoggingHandler::ProcessRequest] GET https://clientsettingscdn.roblox.com/v2/client-version/WindowsPlayer/channel/zassetcacheinitprod
2024-10-03T17:55:05Z [HttpClientLoggingHandler::ProcessResponse] 200 OK https://clientsettingscdn.roblox.com/v2/client-version/WindowsPlayer/channel/zassetcacheinitprod
2024-10-03T17:55:05Z [RobloxDeployment::GetInfo] Getting deploy info for channel LIVE (extraInformation=False)
2024-10-03T17:55:05Z [RobloxDeployment::GetInfo] Deploy information is cached
2024-10-03T17:55:05Z [RobloxFastFlags::Fetch.PCClientBootstrapper.zassetcacheinitprod] Fetching fast flags
2024-10-03T17:55:05Z [HttpClientLoggingHandler::ProcessRequest] GET https://clientsettingscdn.roblox.com/v2/settings/application/PCClientBootstrapper/bucket/zassetcacheinitprod
2024-10-03T17:55:05Z [HttpClientLoggingHandler::ProcessResponse] 200 OK https://clientsettingscdn.roblox.com/v2/settings/application/PCClientBootstrapper/bucket/zassetcacheinitprod
2024-10-03T17:55:05Z [HttpClientLoggingHandler::ProcessRequest] GET https://setup.rbxcdn.com/channel/common/version-72ed2b2ad9e5447f-rbxPkgManifest.txt
2024-10-03T17:55:05Z [HttpClientLoggingHandler::ProcessResponse] 403 Forbidden https://setup.rbxcdn.com/channel/common/version-72ed2b2ad9e5447f-rbxPkgManifest.txt
2024-10-03T17:55:05Z [App::OnStartup] Bootstrapper task has finished
2024-10-03T17:55:05Z [NotifyIconWrapper::Dispose] Disposing NotifyIcon
2024-10-03T17:55:05Z [App::OnStartup] An exception occurred when running the bootstrapper
2024-10-03T17:55:05Z [App::OnStartup] System.AggregateException: One or more errors occurred. (Response status code does not indicate success: 403 (Forbidden).)
---> System.Net.Http.HttpRequestException: Response status code does not indicate success: 403 (Forbidden).
at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode()
at System.Net.Http.HttpClient.GetStringAsyncCore(HttpRequestMessage request, CancellationToken cancellationToken)
at Bloxstrap.Models.Manifest.PackageManifest.Get(String versionGuid)
at Bloxstrap.Bootstrapper.CheckLatestVersion()
at Bloxstrap.Bootstrapper.Run()
at Bloxstrap.Bootstrapper.Run()
at Bloxstrap.App.<>c__DisplayClass38_0.<b__0>d.MoveNext()
--- End of inner exception stack trace ---
2024-10-03T18:04:12Z [App::Terminate] Terminating with exit code 1603 (ERROR_INSTALL_FAILURE)
2024-10-03T18:04:12Z [JsonManager::Save] Saving to %UserProfile%\AppData\Local\Bloxstrap\Settings.json...
2024-10-03T18:04:12Z [JsonManager::Save] Save complete!
2024-10-03T18:04:12Z [JsonManager::Save] Saving to %UserProfile%\AppData\Local\Bloxstrap\State.json...
2024-10-03T18:04:12Z [JsonManager::Save] Save complete!

Read. Other. Posts. I'm begging you. Please. Just do it. Save us time. PLEASE.


support jest.config.js

Describe the bug
react-scripts doesn't support jest.config.js?  Seems more like a bug than a feature request.
I wanted to have all my tests, including my e2e (using protractor) tests in the tests folder, but I can't because I can't exclude the e2e tests in my jest.config.js.  That's besides the point though, jest configuration should be the same as jest.

Does this  help?

I don't see anything there regarding excluding tests, other than using xit.  I'm looking for a jest way of excluding tests.

You can use a tool such as craco for this, consider this example: https://github.com/gsoft-inc/craco/tree/master/recipes/use-a-jest-config-file


Will atomic operations be supported here long-term?

Hey @lindyhopchris, appreciate all your hard work on this (and the previous version as well). Was curious if the atomic operations extension to the spec (https://jsonapi.org/ext/atomic/) is on the radar as this gets built out? Poked around a bit and wasn't seeing anything mentioned, so thought I'd ask. I'm contemplating a long-term stack migration a client may need so thinking through our options there.
Thanks!

Hi! Thanks for flagging that up, I hadn't realised that they'd actually published that as an extension.
So the short answer is yes, because I have production APIs where that functionality would be exceptionally useful.
The longer answer is it slightly fills me with dread because I've just spent a considerable amount of time sorting out the new package, and issues are already starting to build up! I'm going to need help going forward to add significant functionality like that extension, so my question for you would be - if it's important for you to add, is it something you'd be able to collaborate on?
The only problem I foresee with it, is I've just moved all the validation to Laravel form requests, to make things more Laravel-y, which is a change I wanted to make because some of the feedback on the previous version was that it had too steep a learning curve.
The problem with those operations is we'd need to validate each operation in turn... which means access to the validation rules for a resource. Which are currently in a form request, which Laravel automatically validates when resolving from the container. So we'd probably have to extract the validators to a separate class again.

So the short answer is yes, because I have production APIs where that functionality would be exceptionally useful.

Understood and same.

The longer answer is it slightly fills me with dread because I've just spent a considerable amount of time sorting out the new package, and issues are already starting to build up! I'm going to need help going forward to add significant functionality like that extension, so my question for you would be - if it's important for you to add, is it something you'd be able to collaborate on?

Fully understood on it filling you with dread, it's going to take some work to revamp things to account for the new wrinkles that adds. As far as something I'd be able to collaborate on, I would very much like to, but although there are needs for it on various client projects, none of our clients currently have a burning need for it and things are busy enough at the moment that I'm afraid I don't have the time to give this the focused attention it would take to collaborate on 😢

@acorncom no problem. I can definitely commit to doing atomic operations at some point in the future, just can't guarantee when.
Out of interest, you mentioned when opening the issue that you're thinking through options. What other options are you looking at?

@lindyhopchris I know you've stated that you cannot guarantee when you might be able to deliver atomic operations, but figured I'd ask since your last post was back in Feb. Is this on your radar/likely to be delivered in the foreseeable?
We've got a situation where I think atomic operations is the answer. I probably have a solution but it has drawbacks that I'd rather avoid (goes against spec/naming conventions are broken, etc.)
Thanks!

@BenWalters thanks for your question. I'm also keen to use atomic operations. However, as my open source time is pretty limited at the moment, I'm only planning to implement them once they have definitely been added to the spec - i.e. JSON:API 1.1 is tagged.
Basically I don't want to spend the time dev'ing it for it to then be modified before being tagged. Even if I dev it, I wouldn't want to tag this package with it until it was tagged in the spec. Hope that makes sense!
FYI it will be quite a big refactoring. This is because I went with Laravel form requests when implementing this package, as I wanted to use standard Laravel conventions as much as possible. The problem is that couples create and update operations to the HTTP request. So basically, I'm going to have to separate that out to implement atomic operations.
I'll be keen to do the work once they tag JSON:API 1.1, but I just can't afford to spend the time doing it when I don't know when they are going to tag atomic operations.

In the mean time, I've put together a really hacky controller that can be used to implement a subset of the atomic:operations spec.
https://gist.github.com/Westie/9dbdc82468c25dc4567e6d89f75036d7

Update on this: JSON:API v1.1 has now been tagged, with the Atomic Operations extension in it.
It is a priority for me to add this to Laravel JSON:API - I need to use it in production applications as much as everyone else here who is keen to use it! Plus also "How do I do multiple operations in a single request?" is probably the most frequently asked question on Slack!
I need to be honest about my time at the moment - that really is the limiting factor! I've moved to a job in an organisation that doesn't use JSON:API, so I have no work time on this package. So anything that needs doing is entirely in my free time (though will still happen as my personal projects all use JSON:API).
Atomic Operations is a big refactor - because of the currently coupling of the implementation to Laravel form requests.
So TLDR: I will get to this, please be patient and understanding 🙏

@lindyhopchris appreciate your afford towards making this beautiful package.

I was thinking about this. I realize it's not an efficient way to solve the problem, but, couldn't the following be possible:

When an atomic request is received, only parse the top level schema (Just the JSONAPI schema)
Divide the request into sub-requests for each atomic operation
Fire off each request (From Laravel to Laravel), to which Laravel could process the individual request's Schema correctly
Stitch the responses together
return the overall response.

Again, definitely not an efficient way to solve this problem, but I think it could work.

I would never fire a request from a Laravel app to the same Laravel app. It's an indication of bad design - i.e. indicates code is too closely coupled to an HTTP request, which is the problem with have here due to the use of Laravel form requests.
I have actually implemented most of the code changes required, I just need to finish a few things, then package them up as an alpha release. The big remaining thing to do is update the docs and write an upgrade guide (which is required as no one will be able to do the upgrade without a guide).

I appreciate this is taking time, but it's a huge change with limited open source time - so just need some patience, but it's definitely coming.

@DellanX also worth mentioning the other reason we just can't send a Laravel request for each operation is the Atomic Operation extension specifies that all the operations must be atomic... i.e. if one fails, all of them fail. I.e. they are transactional across all of them. That couldn't be guaranteed if you were sending an HTTP request within the app for each operation in the original request.

To clarify, I don't have any need for atomics at this time. Your repo has made life for me a thousand times easier, so I was hoping to give back, and thought it could be a much simpler workaround rather than refactoring the package.
I do agree, HTTP requests is an awful way to implement this, and as you said, it wouldn't be able to achieve the specification.

ah no problem, thanks for the suggestion - was just explaining why refactoring is a better option from my perspective.
I've going to sort out Laravel 11 support on the current version later this week, then look at the final admin for the first alpha release after that, so this has now got back to the top of my todo list!

@lindyhopchris Thank you for the update regarding the development of this feature. We would love to be part of the Alpha testing of the Atomic Operations extension.
Please let me know when we can start using Atomic Operations extension.

@lindyhopchris Hello, is there a branch accessible for us to review the implementation? We're eager to contribute and collaborate towards getting this operational.

So on the lower-level packages, the next branch contain the changes for the next major release.
On the main package (this one), there's a working branch here:
https://github.com/laravel-json-api/laravel/compare/develop...feature/core-v5
That's not a stable branch, I'm using it just to prove things are working (or not) and track down bugs. Not all the tests are passing, which working through the failing tests is my priority.
It hasn't got Atomic Operations in it yet. However it has 100% of the changes required to unblock Atomic Operations. So my plan is to fix the remaining tests - the tests are right, the failures indicate regressions that I need to fix. Then I'd be ready for an alpha release (will need to write an upgrade guide). Then I drop in Atomic Operations.
The main change is I've had to remove all the Form Requests so that we're decoupled from HTTP requests. That unlocks Atomic Operations, where we'd need to run one-to-many JSON:API operations (whereas previously an operation was tied directly to a Form Request).
This has been a very significant rewrite, which is why this is taking long (made worse by limited Open Source time, though I'm starting to pick stuff back up again now).
One of the really nice benefits is that validation is now on the fields in the schema which works a treat. I'm also introducing PHP attributes to the schemas. Both changes for me are 🎉
Here's a flavour of the new world:
namespace App\JsonApi\V1\Posts;

use App\Models\Post;
use Illuminate\Http\Request;
use Illuminate\Validation\Rule;
use LaravelJsonApi\Core\Schema\Attributes\Model;
use LaravelJsonApi\Eloquent\Fields\DateTime;
use LaravelJsonApi\Eloquent\Fields\ID;
use LaravelJsonApi\Eloquent\Fields\Relations\BelongsTo;
use LaravelJsonApi\Eloquent\Fields\Relations\BelongsToMany;
use LaravelJsonApi\Eloquent\Fields\Relations\HasMany;
use LaravelJsonApi\Eloquent\Fields\Relations\MorphToMany;
use LaravelJsonApi\Eloquent\Fields\SoftDelete;
use LaravelJsonApi\Eloquent\Fields\Str;
use LaravelJsonApi\Eloquent\Filters\OnlyTrashed;
use LaravelJsonApi\Eloquent\Filters\Scope;
use LaravelJsonApi\Eloquent\Filters\Where;
use LaravelJsonApi\Eloquent\Filters\WhereIdIn;
use LaravelJsonApi\Eloquent\Pagination\PagePagination;
use LaravelJsonApi\Eloquent\Schema;
use LaravelJsonApi\Eloquent\SoftDeletes;

#[Model(Post::class)]
class PostSchema extends Schema
{
    use SoftDeletes;

    /**
     * @inheritDoc
     */
    public function fields(): array
    {
        return [
            ID::make(),
            BelongsTo::make('author')->type('users')->readOnly(),
            HasMany::make('comments')->canCount()->readOnly(),
            Str::make('content')->rules('required'),
            DateTime::make('createdAt')->sortable()->readOnly(),
            SoftDelete::make('deletedAt')->sortable(),
            MorphToMany::make('media', [
                BelongsToMany::make('images'),
                BelongsToMany::make('videos'),
            ])->canCount(),
            DateTime::make('publishedAt')->sortable(),
            Str::make('slug')
                ->rules('required')
                ->creationRules(Rule::unique('posts'))
                ->updateRules(fn($r, Post $model) => Rule::unique('posts')->ignore($model)),
            Str::make('synopsis')->rules('required'),
            BelongsToMany::make('tags')->canCount()->mustValidate(),
            Str::make('title')->sortable()->rules('required'),
            DateTime::make('updatedAt')->sortable()->readOnly(),
        ];
    }

    /**
     * @inheritDoc
     */
    public function filters(): array
    {
        return [
            WhereIdIn::make($this)->delimiter(',')->onlyToMany(),
            Scope::make('published', 'wherePublished')->asBoolean(),
            Where::make('slug')->singular()->rules('string'),
            OnlyTrashed::make('trashed'),
        ];
    }

    /**
     * @inheritDoc
     */
    public function pagination(): PagePagination
    {
        return PagePagination::make()
            ->withoutNestedMeta()
            ->withMaxPerPage(200);
    }
}

Any further thoughts on first-party documentation solution?

Yes it's still the plan to add that, but it is further down the track. I can't put a date on it yet.

Any idea on how you are thinking of approaching it?

@glennjacobs primarily curiosity or would you have OSS time to help push things along?

@lindyhopchris the above looks great. is helping sort through failing tests / regressions something you want help with if those of us interested have time or would that slow you down?

I think that would slow me down.
I'm starting to pick things back up, though I'm currently dealing with the backlog of things people have raised with the current version. Particularly as some people have been kind enough to submit PRs, so want to ensure the code they've taken the time putting together actually gets out.
To start to put more transparency around what's going on, and just how complex and big things are, I've created a Project Kanban board. I'll be filling it out with the things I need to do for this next major version, but also pulling in anything I want to prioritise on the current version. Here's the link:
https://github.com/orgs/laravel-json-api/projects/1

@lindyhopchris looks like that project isn't visible publicly at the moment?

thanks, should be public now.


Critical CVEs found in 9.7.0

Which version and edition of Flyway are you using?
9.7.0
Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin)
Docker image
Which database are you using? (Type & version)
Postgres 14
Which operating system are you using?
OS in base image of flyway container
Wanted to report these critical CVEs which got picked up by our internal security scan tooling.
sqlite3-3.23.1
flyway/drivers/sqlite-jdbc-3.34.0.jar
org/sqlite/native/DragonFlyBSD/x86_64/libsqlitejdbc.so

https://nvd.nist.gov/vuln/detail/CVE-2019-19646
https://nvd.nist.gov/vuln/detail/CVE-2019-8457
sqlite3
flyway/drivers/sqlite-jdbc-3.34.0.jar
org/sqlite/native/FreeBSD/x86_64/libsqlitejdbc.so

https://nvd.nist.gov/vuln/detail/CVE-2021-20223
https://nvd.nist.gov/vuln/detail/CVE-2020-35527

Thanks for letting us know.
Nothing has come up on our own internal security scans, and these CVEs only seem to affect versions before 3.34, which is the version we ship with Flyway so it shouldn't be affected.

I found one as well but not critical and not in the docker image, https://github.com/flyway/flyway/issues/3562

Thanks @engvalla. We're aware of that one and it should be fixed in the next Flyway release.

Thanks for confirming. Looks like whatever tooling we're using needs some work... :)

Thanks for letting us know.
Nothing has come up on our own internal security scans, and these CVEs only seem to affect versions before 3.34, which is the version we ship with Flyway so it shouldn't be affected.

Thanks for confirming. Looks like whatever tooling we're using needs some work... :)


(Manage Bower Packages) is no longer available

(Manage client-side libraries) is the new command according to the announcement:
https://blogs.msdn.microsoft.com/webdev/2018/08/31/library-manager-release-in-15-8/
The suggestion is to remove this article because there is already an article about LibMan and also many resources are talking about bower as officially dead or is dying since 2016. It even has no Wikipedia page except in German

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

ID: cd636ce2-7f47-77e4-e12c-461bd6951c65
Version Independent ID: 86160014-970f-5662-a446-308fd4c1b331
Content: Manage client-side packages with Bower in ASP.NET Core
Content Source: aspnetcore/client-side/bower.md
Product: aspnet-core
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

@madskristensen @raquelsa can I delete Manage client-side packages with Bower in ASP.NET Core


child-observation depends on monkey patching MutationObserver

I'm submitting a bug report

Library Version:
master

Browser:
all

Current behavior:
As can be seen here:
https://github.com/aurelia/templating/blob/master/src/child-observation.js#L160
MutationObserver returned by DOM.createMutationObserver(onChildChange); is being patched, by adding observer.binders = [];
Later it is expected here:
https://github.com/aurelia/templating/blob/master/src/child-observation.js#L67
That the callback's observer contains the binders array.
This is not always the case, and error of the type "Uncaught TypeError: Cannot read property 'length' of undefined" are thrown.
In my use case, aurelia is used as an application inside an Angular application which uses Zone.js. Zone.js wraps the original MutationObserver. So when new MutationObserver() is called a wrapped instance by Zone.js is returned. To this instance .binders is added by aurelia. But in onChildChange() the observer is a different constructor (the browsers original) which does not contain the binders causing the errors.
Expected/desired behavior:
All should work event if window.MutationObserver is not the native browsers constructor.
child observation should not rely on monkey patching window.MutationObserver.

Well, Zones are a pretty nasty hack to begin with. I'm not sure how much we can do. The standard way to associate data is either to add a property like we have already, or use a Map/WeakMap. But Map/WeakMap will have the same issue if the instance is actually difference since the key equality check will fail. Does Zones provide an API to unwrap the instance and get the original? That would probably enable a solution.

Thank you for the quick response!
@EisenbergEffect  I totally agree with you regarding Zones, In our case we unfortunately do not have other choice.
Regarding unwrapping the instance, I believe: window[window.Zone.__symbol__("MutationObserver")] should do the trick based on:
https://github.com/angular/angular/issues/26948
window[window.Zone.__symbol__("WebKitMutationObserver")] works for webkit as well.
So if a fix could be applied to https://github.com/aurelia/pal-browser/blob/master/src/dom.js#L41
It would be great!

@genadis If you already know what could be applied to fix Zone, why couldn't you do this:
// main.ts
import { DOM } from 'aurelia-framework';

DOM.createMutationObserver = (...args) => {
  return new window[window.Zone.__symbol__("MutationObserver")](...args);
}

@bigopon thank you fo the suggestion.
Our aurelia application is used in different environments the one with Zone.js is only one of them.
Solution that works for us is in bootstrap code to have:
import { PLATFORM, DOM } from 'aurelia-pal';
import { bootstrap } from 'aurelia-bootstrapper';

bootstrap((aurelia: Aurelia) => {
   aurelia.use.basicConfiguration();

  DOM.createMutationObserver = (...args) => {
    const global = window as any;
    let observerConst;
    if (global.Zone && global.Zone.__symbol__) {
      observerConst = global[global.Zone.__symbol__('MutationObserver')] || global[global.Zone.__symbol__('WebKitMutationObserver')];
    }
    return new (observerConst || global.MutationObserver || global.WebKitMutationObserver)(...args);
  }
   // ....
}

Setting the DOM.createMutationObserver after the bootstrap is important because the DOM object is not setup prior to that.
If you are not planning to add this fix, I guess this issue might help others.
Thanks

Angular is popular, so making Aurelia work seamlessly with it is desirable. But I'd be hesitant to add this. There's no guarantee that Angular would use Zone forever and there's no guarantee that Zone would stay that way forever (extremely speaking only, but I hope it's clear how uneasy one would feel adding something so specific to Angular/Zone into our modules). What we could do is to add a section in our doc, about Angular integration, for this particular use case.
About your applications, if you don't want to use Aurelia bootstrapper module, you can do this:
import { initialize } from 'aurelia-history-browser';

initialize();

// here DOM.createMutationObserver is ready
DOM.createMutationObserver = ...


[datadog_checks_dev] update doc about style checker only works for Python 3.6+

What does this PR do?
Add precision about style checker requirement: Python 3.6+ is required.
Motivation
The style checker fail due to black. It requires Python 3.6+.
The following error happen when using Python 3.5.
ERROR: Could not find a version that satisfies the requirement black (from versions: none)
ERROR: No matching distribution found for black

More info: https://github.com/ambv/black/issues/439#issuecomment-411429907
Additional Notes
Should we update the requirements listed here to avoid style checker not working due to Python3.x version below 3.6 ?
https://github.com/DataDog/integrations-core/blame/master/datadog_checks_dev/README.md#L16
Review checklist (to be filled by reviewers)

[ ] PR title must be written as a CHANGELOG entry (see why)
[ ] Files changes must correspond to the primary purpose of the PR as described in the title (small unrelated changes should have their own PR)
[ ] PR must have changelog/ and integration/ labels attached
[ ] Feature or bugfix must have tests
[ ] Git history must be clean
[ ] If PR adds a configuration option, it must be added to the configuration file.

Yes, update the REDME

Might as well say 3.7

Just updated datadog_checks_dev/README.md:

Updated Python version
Added a prerequisite section that's aligned with https://github.com/DataDog/integrations-core/blame/8d55b9c/docs/dev/new_check_howto.md#L20-L25

Ok to leave Python 3.6+ as comment in datadog_checks_dev/datadog_checks/dev/plugin/tox.py, since that's what black requires?

Thanks!
This too https://github.com/DataDog/integrations-core/blob/master/docs/datadog_checks_dev.cli.rst

Sure. datadog_checks_dev.cli.rst updated.


[Service Bus] Remove use of dedupe flag in rollup

This issue is track investigation and efforts on re-appearance of de-dupe issue that was caught as part of work on Service Bus' management API feature
Goal is to try and not have rollup use this flag before we ship the feature

@mikeharder @KarishmaGhiya
In PR https://github.com/Azure/azure-sdk-for-js/pull/4922/files#diff-eb16709e5d35de0b13886e760c91041d
@bterlson and I took a look at this and we see that the actual package versions were not getting updated if not already updated in the lock file.
For instance, in current issue, buffer remained at 5.4.0 and not updated to 5.4.3 which was what caused this issue.
Filed https://github.com/Azure/azure-sdk-for-js/issues/6025 to help avoid such misses in future

Closed with https://github.com/Azure/azure-sdk-for-js/pull/6027


refactor: load proving keys and reduce wasm binary size

References https://github.com/penumbra-zone/penumbra/issues/2712. A new LazyProvingKey type is introduced to represent the proving keys. The limitation with the former Lazy type was that Lazy::new() expects a closure. This ultimately creates a tight coupling in the declaration of a lazy variable and its initialization. The LazyProvingKey enables this separation based on conditional features.
This will further reduce the wasm binary size to only include the verification keys, originally from ~90MB to a few MB.

This will further reduce the wasm binary size to only include the verification keys, originally from ~90MB to a few MB.

Nice!!!!

@TalDerei This looks great! I added another commit that merges the check-ID behavior from the existing load_proving_keys method so that we know that proving keys are always loaded with the correct values, if they're loaded at all.


samples: subsys: canbus: canopen: objdict: CO_OD.h is not normally made.

Describe the bug
The CO_OD.h file is not created normally in the Object Dictionary Editor v0.8-0-gb60f4b version. (CO_OD.h: #define CO_NO_TS     1)
To Reproduce
Steps to reproduce the behavior:

Run the Object Dictionary Editor v0.8-0-gb60f4b program.
Open the eds file provided by the canopen sample.
Create a CO_OD.c , CO_OD.h, xml file without any further changes, and save the eds file.
Place the generated CO_OD.c , CO_OD.h, and xml files in the canopen/objdict folder.
cmake -DBOARD=stm32l433 .. (canopen/build)
west flash

Expected behavior
(Unbuilt header files created by the editor program)
CO_OD.h: #define CO_NO_TS     1

(Header file for normal build)
CO_OD.h: #define CO_NO_TIME     1

Screenshots or console output

Environment (please complete the following information):

OS: Linux(Ubuntu 18.04)
Toolchain: Zephyr SDK 0.11.1

Additional context
I wanted to create CO_OD.c, CO_OD.h, xml files directly by opening the eds file provided by the zipper canopen sample with object logic editor.
Download the editor program from (https://github.com/robincornelius/libedssharp/releases.)
We opened the editor program to create CO_OD.c, CO_OD.h, and xml files without any additional changes.
However, an error occurred during the build because CO_NO_TIME was not defined in the CO_OD.h file.
Looking in the header file,I suspected that the
#define CO_NO_TS      1

was created incorrectly due to the difference in the version of the editor.
I wonder if there is anything else that needs to be set up in the editor program in order to be normally generated from CO_OD.h to #define CO_NO_TIME    1 or if it is due to version differences.

@wngur300 You need to use a version of libedssharp, that matches the version of CANopenNode used. This is not specific to Zephyr.

To clarify, this is v0.8 of libedssharp (the latest released version). See https://github.com/robincornelius/libedssharp/releases/tag/v0.8

@wngur300 You need to use a version of libedssharp, that matches the version of CANopenNode used. This is not specific to Zephyr.

v0.8-7-g2e53bbc is not found at https://github.com/robincornelius/libedssharp/releases and appears to be downloadable until version v0.8-0-gb60f4. Can you tell me where I can download the version of v0.8-7-g2e53bbc? Can't I get it for free?

v0.8-7-g2e53bbc is not found at https://github.com/robincornelius/libedssharp/releases and appears to be downloadable until version v0.8-0-gb60f4. Can you tell me where I can download the version of v0.8-7-g2e53bbc? Can't I get it for free?

To resolve the above issue, you will need at least https://github.com/robincornelius/libedssharp/commit/07ac8191e64067547f6c21774b5089ad03a465c2 (or just manually edit the generated file to use CO_NO_TIME.

v0.8-7-g2e53bbc is not found at https://github.com/robincornelius/libedssharp/releases and appears to be downloadable until version v0.8-0-gb60f4. Can you tell me where I can download the version of v0.8-7-g2e53bbc? Can't I get it for free?

To resolve the above issue, you will need at least robincornelius/libedssharp@07ac819 (or just manually edit the generated file to use CO_NO_TIME.

Thank you!

Closing as resolved.

For reference (and Linux users), the latest auto-build that has this problem fixed can be downloaded from: https://github.com/robincornelius/libedssharp/raw/gh-pages/build/OpenEDSEditor-latest.zip

Actually the latest version of OpenEDSEditor is also not compatible, so I opened https://github.com/zephyrproject-rtos/zephyr/issues/33149 to clarify and find a solution.


[BugFix][Frontend] Use LoRA tokenizer in OpenAI APIs

Currently the LoRA tokenizers aren't used in the OpenAI APIs, meaning the behaviour won't be correct if adapters are used that have custom added tokens. This PR includes changes to address that. It mostly replaces #3512.
More work is needed to address remaining inconsistencies in tokenization behaviour between the OpenAI front-end and standalone LLMEngine/AsyncLLMEngine use, including:

Standalone cases don't honor truncation and add_special_tokens request parameters
OpenAI API cases don't make use of TokenizerGroups for possible parallelization of tokenization

as well as some other inefficiencies.
But these are to be addressed in follow-on PRs.

@dtrifiro FYI

If possible, try to add a test case to verify whether the OpenAI-compatible server can apply the correct chat template.

Thanks @DarkLight1337, yes test is forthcoming.

We can merge after the test case is added.

@DarkLight1337 tests now added! and there were a lot of merge conflicts to resolve :sweat_smile:

The error occurs because the tokenizer is passed to the lru_cache from _image_token_str function, so we need to remove the lru_cache. To compensate, can a ``cached_property` be added to the cached tokenizer so that we can avoid decoding the image token each time?

Thanks @DarkLight1337! I pushed a fix before I read your comment, hopefully this should be ok too.


[FLINK-14641][docs] Fix description of metric fullRestarts

What is the purpose of the change
The metric fullRestarts counts both full restarts and fine grained restarts since 1.9.2.
This PR is to update the metric description doc accordingly.
Brief change log

Fixed descriptions doc of metric fullRestarts

Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

@zentol would you take another look of this PR?
The comment is addressed and the tests pass now.


Upgrade to Stackage LTS 12.0

This fixes #329. Or it should, at least.

If we can get the windows build working again that would be awesome.  But still seems to be failing, not sure what the issue is.

I'm not entirely sure why it failed either. I definitely expected it to succeed, but CI makes fools of us all.

AIUI, we'd need to use either GHC 8.6.n or 8.4.4 to fix AppVeyor. So this is blocked on 8.6.2 being released (since 8.6.1 has a horrible bug) and then Stackage upgrading. (Or we could build our own snapshot as a hack, I guess.)

@quasicomputational so lts-12.16 which uses GHC 8.4.4 should work then?
@tfausak can you try if upgrading to lts-12.16 help?

Somehow it's even less happy with LTS 12.16 than it was with LTS 12.0. 🤔

Fixed on master.