After attaching furigana, ebook is unreadable

I downloaded That Time I Got Reincarnated as a Slime from syosetsu using WebNovelCrawler and tried uploading it to the webapp. At first I tried uploading the epub directly, but that results in Error during conversion, so then I tried uploading it as a zip and I was able to download a converted epub file. However, opening that file in Calibre results this error, indicating its not a properly formatted epub file:
calibre, version 5.27.0
ERROR: Loading book failed: Failed to open the book at C:\Users\timot\Documents\Calibre Library\Unknown\furiganalysed slime (85)\furiganalysed slime - Unknown.epub. Click "Show details" for more info.

Failed to convert book: C:\Users\timot\Documents\Calibre Library\Unknown\furiganalysed slime (85)\furiganalysed slime - Unknown.epub with error:
WARNING: Epub doesn't contain a valid mimetype declaration
InputFormatPlugin: EPUB Input running
on C:\Users\timot\Documents\Calibre Library\Unknown\furiganalysed slime (85)\furiganalysed slime - Unknown.epub
Failed to run pipe worker with command: from calibre.srv.render_book import viewer_main; viewer_main()
Traceback (most recent call last):
  File "calibre\ebooks\metadata\epub.py", line 99, in __init__
  File "calibre\ebooks\metadata\epub.py", line 153, in open
  File "calibre\utils\zipfile.py", line 1006, in read
  File "calibre\utils\zipfile.py", line 1034, in open
  File "calibre\utils\zipfile.py", line 995, in getinfo
KeyError: "There is no item named 'META-INF/container.xml' in the archive"

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "calibre\customize\ui.py", line 433, in get_file_type_metadata
  File "calibre\customize\builtins.py", line 169, in get_metadata
  File "calibre\ebooks\metadata\epub.py", line 238, in get_quick_metadata
  File "calibre\ebooks\metadata\epub.py", line 217, in get_metadata
  File "calibre\ebooks\metadata\epub.py", line 165, in get_zip_reader
  File "calibre\ebooks\metadata\epub.py", line 148, in __init__
  File "calibre\ebooks\metadata\epub.py", line 102, in __init__
calibre.ebooks.metadata.epub.EPubException: missing OCF container.xml file
Traceback (most recent call last):
  File "calibre\ebooks\conversion\plugins\epub_input.py", line 241, in find_opf
FileNotFoundError: [Errno 2] No such file or directory: 'META-INF/container.xml'
Traceback (most recent call last):
  File "runpy.py", line 194, in _run_module_as_main
  File "runpy.py", line 87, in _run_code
  File "site.py", line 82, in <module>
  File "site.py", line 77, in main
  File "site.py", line 49, in run_entry_point
  File "calibre\utils\ipc\worker.py", line 197, in main
  File "<string>", line 1, in <module>
  File "calibre\srv\render_book.py", line 824, in viewer_main
  File "calibre\srv\render_book.py", line 815, in render_for_viewer
  File "calibre\srv\render_book.py", line 792, in render
  File "calibre\ebooks\oeb\iterator\book.py", line 63, in extract_book
  File "calibre\customize\conversion.py", line 245, in __call__
  File "calibre\ebooks\conversion\plugins\epub_input.py", line 281, in convert
ValueError: C:\Users\timot\Documents\Calibre Library\Unknown\furiganalysed slime (85)\furiganalysed slime - Unknown.epub is not a valid EPUB file (could not find opf)

I also tried downloading the conversion as 1 text file, but it downloaded an empty text file. Any thoughts?

Sending the EPUB should work, but apparently something made the parsing code crash.
furiganalyse_1  | ERROR:root:Error while processing /tmp/furiganalysed_uploads/tmphddoa9qh/slime.epub: Traceback (most recent call last):
furiganalyse_1  |   File "/workdir/furiganalyse/app.py", line 58, in get_post_upload_file
furiganalyse_1  |     main(
furiganalyse_1  |   File "/workdir/furiganalyse/__main__.py", line 33, in main
furiganalyse_1  |     process_epub_file(unzipped_input_fpath, furigana_mode, writing_mode, output_format)
furiganalyse_1  |   File "/workdir/furiganalyse/epub_format.py", line 20, in process_epub_file
furiganalyse_1  |     tree = process_html(html_filepath, mode)
furiganalyse_1  |   File "/workdir/furiganalyse/parsing.py", line 15, in process_html
furiganalyse_1  |     process_tree(tree, mode)
furiganalyse_1  |   File "/workdir/furiganalyse/parsing.py", line 31, in process_tree
furiganalyse_1  |     process_head(p)
furiganalyse_1  |   File "/workdir/furiganalyse/parsing.py", line 97, in process_head
furiganalyse_1  |     head, children, tail = create_parsed_furigana_html(text)
furiganalyse_1  |   File "/workdir/furiganalyse/parsing.py", line 132, in create_parsed_furigana_html
furiganalyse_1  |     new_text = create_furigana_html(text)
furiganalyse_1  |   File "/usr/local/lib/python3.8/site-packages/furigana/furigana.py", line 173, in create_furigana_html
furiganalyse_1  |     for pair in split_furigana(text):
furiganalyse_1  |   File "/usr/local/lib/python3.8/site-packages/furigana/furigana.py", line 136, in split_furigana
furiganalyse_1  |     texts = parse_node(node)
furiganalyse_1  |   File "/usr/local/lib/python3.8/site-packages/furigana/furigana.py", line 164, in parse_node
furiganalyse_1  |     return split_okurigana(origin, hiragana)
furiganalyse_1  |   File "/usr/local/lib/python3.8/site-packages/furigana/furigana.py", line 43, in split_okurigana
furiganalyse_1  |     logging.debug(f'Taking care non kanji parts. i={i}, j={j} ("{text[i]}" / "{hiragana[j]}")')
furiganalyse_1  | IndexError: string index out of range

Can you send me your EPUB file please? I will further investigate.

I uploaded it here: https://www.file.io/O8qW/download/SNRRczKIvvK3

Thank you. I've fixed the issue fixed, you can try again.


test: disable spi-available-local.swift and spi-available-swift-module.swift while investigating

rdar://91325474

Force-merging to clear macOS PR tests.


nuget package v 3.50.3 dll is version as 3.50.0 instead of .3

Autofixture 3.50.3 dll is not versioned correctly.

Compared to 3.50.2 dll

I had to adjust my app.config to reflect this:
<dependentAssembly>         <assemblyIdentity name="Ploeh.AutoFixture" publicKeyToken="b24654c590009d4f" culture="neutral" />         <bindingRedirect oldVersion="<IP_ADDRESS>-<IP_ADDRESS>" newVersion="<IP_ADDRESS>" />       </dependentAssembly>

Thanks for reporting the issue. Actually, that is an intentional change as the patch should not be a part of the AssemblyVersion. The previous version which had incorrect versioning and it has been fixed. Please refer to the mentioned PR for more detail.
This "anomaly" will be normalized as soon as we release the next minor update (so the version will be <IP_ADDRESS>)
Usually that change should not be an issue and it's quite strange why you need the assembly version redirects in your solution. Did you update the AutoFixture assemblies partially (e.g you updated the AutoFixture, but kept the previous version of the AutoFixture.xUnit2)? If so, what is the reason and why update of all the assemblies is not an option?

The reason why this even came up is because I use a visual studio plugin test coverage tool called ncrunch.  Whenever ncrunch would try to execute my tests, it would throw an exception and not execute any of my tests.
System.InvalidCastException: Unable to cast object of type 'Xunit.Sdk.ReflectionAssemblyInfo' to type 'Xunit.Abstractions.IAssemblyInfo'.
So when I eventually determined that this was the cause, I felt obliged to report an issue.

Could you confirm that you have upgraded all the AutoFixture related assemblies in your solution? It looks like this is the reason.
If that is not the case, could attach a simple project which demonstrates the issue, so I could have a look? I have teammates with NCrunch 3 installed, so I could check that on my side just out of curiosity. It looks quite weird O_o
In any case, it's great that you reported the issue and a way to solve it - somebody else could find it. Next minor update should fix this issue completely, so let's keep everything as is.

Great! And what about a sample of project where the issue is reproducible? It that possible to provide it?
Thanks.

your last response said if not autofixture 3.50.3 and my project is using 3.50.3, so i thought that it met the condition to not provide a sample and i dont know what sample project to provide.

Thanks for the reply. In this case I'll close the issue as no action seems to be required as there is a workaround till the next minor release.


Windows reset to default rotation during closing animation on rotated montior

Steps to reproduce:

Open a window on a rotated monitor
Close window

Expected outcome: The window should close with the same rotation that was applied to it during the rest of its lifespan.
Noted outcome: Upon closing a window, it rotates back to the default rotation of the monitor during the closing animation.
This creates particular problems when taking an area selection screenshot on a rotated monitor because the area selection graphic rotates into the screenshot area right as the screenshot is taken.
Example:

What you are describing is a layer surface and not a window. At any rate, fixed in 86be6c3884033e35bf3efef4ba705d3be72cbe87


Support for custom tables names

Currently, the history table name is hardcoded (APP_historicalMODEL).
This pull request add support for custom tables names by adding a
db_history_table option.
As Django reject all unknown option in Meta inner class, I've added an
History inner class to store this option (and possibly others future
options).
class Organization(models.Model):
    name    = models.CharField(_('Organization or Name'), max_length=25)
    address = models.CharField(_('Address'), max_length=250)
    zipcode = models.CharField(_('Postal code'), max_length=10, null=True)
    city    = models.CharField(_('City'), max_length=50)
    country = models.CharField(_('Country'), max_length=2, \
                choices=COUNTRIES_CHOICES)
    history = HistoricalRecords()

    def __str__(self):
        return self.name

    class History:
        db_history_table = 'organizations_history'

    class Meta:
        db_table = 'organizations'

@jleroy: This is pretty cool... I like the idea of allowing the history table name to be overriden.
Previously we've been allowing configuration as parameters to both HistoricalRecords and register(). What do you think of moving this option there as well? One big advantage is the table name for historical models of 3rd party libraries could be defined through a parameter to register(), which might be possible  easily through the inner class configuration scheme.

@macro1 : Done.
Example using HistoricalRecords():
class Organization(models.Model):
    name    = models.CharField(_('Organization or Name'), max_length=25)
    address = models.CharField(_('Address'), max_length=250)
    zipcode = models.CharField(_('Postal code'), max_length=10, null=True)
    city    = models.CharField(_('City'), max_length=50)
    country = models.CharField(_('Country'), max_length=2, \
                choices=COUNTRIES_CHOICES)
    history = HistoricalRecords(table_name='organizations_history')

    def __str__(self):
        return self.name

    class Meta:
        db_table = 'organizations'

Example using register():
class Organization(models.Model):
    name    = models.CharField(_('Organization or Name'), max_length=25)
    address = models.CharField(_('Address'), max_length=250)
    zipcode = models.CharField(_('Postal code'), max_length=10, null=True)
    city    = models.CharField(_('City'), max_length=50)
    country = models.CharField(_('Country'), max_length=2, \
                choices=COUNTRIES_CHOICES)

    def __str__(self):
        return self.name

    class Meta:
        db_table = 'organizations'

register(table_name='organizations_history')

Documentation added.


Update validation

Adding a line about e2e tests passing on a CDK cluster.
Partially fixes https://github.com/kubernetes/website/issues/7464

This change is

/approve
/lgtm


Crash + "Something went wrong."

Microsoft PowerToys version
<IP_ADDRESS>
Installation method
GitHub
Running as admin
Yes
Area(s) with issue?
General
Steps to reproduce
I opened OBS while Discord was open.  That's all I did.
✔ Expected Behavior
I expected nothing to happen at all, and for PowerToys to run happily in the background.
❌ Actual Behavior
My graphics card crashed.  Windows told me "Something went wrong." and asked me to file a bug report.  This is the error I received:
Version: <IP_ADDRESS>
OS Version: Microsoft Windows NT 10.0.19045.0
IntPtr Length: 8
x64: True
Date: 2024-06-04 15:23:46
Exception:
System.Runtime.InteropServices.COMException (0x80263001): {Desktop composition is disabled} The operation could not be completed because desktop composition is disabled. (0x80263001)
at Standard.NativeMethods.DwmExtendFrameIntoClientArea(IntPtr hwnd, MARGINS& pMarInset)
at System.Windows.Shell.WindowChromeWorker._ExtendGlassFrame()
at System.Windows.Shell.WindowChromeWorker._UpdateFrameState(Boolean force)
at System.Windows.Shell.WindowChromeWorker._HandleDwmCompositionChanged(WM uMsg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at System.Windows.Shell.WindowChromeWorker._WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at System.Windows.Interop.HwndSource.PublicHooksFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
Other Software
Discord stable 298544 (3e1b662) Host 1.0.9147 x64 (48263) Build Override: N/A Windows 10 64-bit (10.0.19045)
OBS 30.1.2
Radeon RX 480 (drivers up to date)
I fully suspect the issue is with my graphics card and not with PowerToys, but since it asked me to submit a bug report, here it is.

Hi, I had the same issue this morning at logon after hibernate.
it never happens before on previous versions even if I hibernate my computer every evening.

/dup https://github.com/microsoft/PowerToys/issues/31226


PHP 8.4

The PHP-8.3 branch has been created for PHP 8.3, meaning that master is now what will become PHP 8.4. It would be great if we were able to use 8.3 to reference nightly builds (until PHP 8.3.0 has been released, of course) of PHP 8.3 and 8.4 to reference nightly builds of PHP 8.4.

@sebastianbergmann
In php-version input 8.4 should work now and install a build from the master branch, 8.3 will now install a build from the PHP-8.3 branch of php/php-src.


Sforce-Auto-Assign in Header of REST

Salesforce changed default behavior of REST call if Cases are changed. If changes are done in Inspector there is not send the Sforce-Auto-Assign Value in the header of the REST-Call. So Assigement Rules are executed every time. But normaly before the assignement rules where not firered every time.
So the Inspector should send  Sforce-Auto-Assign with value FALSE or be configure able to switch it on/off.
https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/headers_autoassign.htm
https://help.salesforce.com/s/articleView?id=000390059&type=1

In inspect.js line 150 it would be
sfConn.rest(recordUrl, { method: "PATCH", body: record, headers: {"Sforce-Auto-Assign" : false} }).then(() => {

Hi @SfdxDieter ,
Good catch 👏  !
I'll probably implement a variable in localStorage to let users define custom headers in create and update rest callout from show all data view.
I'll post updates here !

Hi @SfdxDieter ,
You can test the header customisation by checking out this branch locally and follow this how to.
I'll test this does not bring regressions on the create updates for a while locally, if everything is good I'll merge it into releaseCandidate (next release branch).
Let me know if you need assistance !

After the first test, where it does not worked, I get "Uncaught SyntaxError: Unexpected token 'export'" in the plugin an it does not start any more.

Currently I see a lot off errors. I can see that the parameter is used. But it does not work as exspected. I will check it.

@SfdxDieter
Have you disabled the extension from the chrome web store after installing the legacy version ?

Please change line 36 to
this.headerCallout = JSON.parse( localStorage.getItem("createUpdateRestCalloutHeaders") ? localStorage.getItem("createUpdateRestCalloutHeaders") : "{}");
then it works. (I cann't push to git)
I get 2 kind of errors in the plugin
Warning: Each child in an array or iterator should have a unique "key" prop. Check the render method of AllDataSelection. See https://fb.me/react-warning-keys for more information. in div (created by AllDataSelection) in AllDataSelection (created by AllDataBoxSObject) in div (created by AllDataBoxSObject) in AllDataBoxSObject (created by AllDataBox) in div (created by AllDataBox) in AllDataBox (created by App) in div (created by App) in div (created by App) in App
and
Uncaught SyntaxError: Unexpected token 'export'

When using npm run chrome-dev-build the manifest.json is changed. The links.js is added

if I remove after the build the links.js again and upload it to chrome the token export error does not appear

Adding a new option to set the custom header

Will be available in beta version probably next week


[NETBEANS-586]: NPE findUsages

Without nb-javac, workingCopy.getTrees().getTree(c) returns null for nested anonymous class constructor. Added null check.
This change is to avoid:
java.lang.NullPointerException
at org.netbeans.modules.refactoring.java.plugins.FindUsagesVisitor.visitNewClass(FindUsagesVisitor.java:402)
at org.netbeans.modules.refactoring.java.plugins.FindUsagesVisitor.visitNewClass(FindUsagesVisitor.java:54)
at jdk.compiler/com.sun.tools.javac.tree.JCTree$JCNewClass.accept(JCTree.java:1711)
at jdk.compiler/com.sun.source.util.TreePathScanner.scan(TreePathScanner.java:82)
at jdk.compiler/com.sun.source.util.TreeScanner.scan(TreeScanner.java:105)
at jdk.compiler/com.sun.source.util.TreeScanner.scanAndReduce(TreeScanner.java:113)
at jdk.compiler/com.sun.source.util.TreeScanner.visitMethodInvocation(TreeScanner.java

So, this will mean some usages won't be found (more or less silently), which does not feel right. I tried a few simple cases (including the platform/core.multitabs), although on a dev build of JDK 12, and didn't see the problem. So I wonder what is the reproducible testcase, so that we can find out what's the issue.
I believe it should be possible to re-write the search for the constructor to only work over trees (basically, do classTree.getMembers() and search for the constructor); it might be tricky to determine which of the members is the constructor, but should be possible. (TreeUtilities.isSynthetic in the worst case). Besides for potentially fixing this bug, it might also be somewhat faster.

It's reproducible for nested anonymous class constructor
Like in AbstractTabDisplayer:
fullPathListener = new ChangeListener() {
@Override
public void stateChanged( ChangeEvent e ) {
SwingUtilities.invokeLater(new Runnable() {
@Override
public void run() {
updateFullPath();
}
});
}
};
[exec] FindUsages cannot resolve
[exec] class  implements Runnable {
[exec]
[exec]     () {
[exec]         super();
[exec]     }
[exec]
[exec]     @Override()
[exec]     public void run() {
[exec]         updateFullPath();
[exec]     }
[exec] } ()
This is not reproducible with jdk-12.
I can try the suggested alternative approach.

Hi Jan, Modified code as suggested. Since issue is only reproducible using jdk, didn't add test as tests use nb-javac. Also not sure when addUsages on line 402 gets called. So here we are inside anonymous class constructor(generated), workingCopy.getTreeUtilities().isSynthetic(superCall) is always true. The exact reproducible code is below: Find usages for constructor A() fails with npe without this change:
public class Test {
void m() {
Runnable r = new Runnable() {
public void run() {
B b = new B() {
void test() {
System.out.println("testB");
}
};
}
};
}
class A {
public A() {
}
void test() {
}
}
class B extends A {
}
}

Thanks Jan, Merging.


Do not set DYLD_LIBRARY_PATH to point the installed toolchain/sdk on macOS.

This has not been a good idea since Swift started shipping in the OS.
The OS runtime is the one we would like Swift scripts to use. Using the installed toolchain can potentially cause sync issues.
Continue setting this variable in other UNIX toolchains, because there is no runtime shipped in the OS there.
Resolves rdar://78951185

@swift-ci please test


added calculation and test for natural log of left denominator term o…

…f LR in Bolck et al. (natural log of num2 in R script)

PR closed since it is covered by PR #91


Unused constructor

I have removed unused constructor from the code. This constructor was declared but never used by any class. I removed this constructor and code is smooth.

Actually, the refactoring is not ok. You are removing the constructor that is needed by the UI framework. It is never called in Java code, but the web-framework calls it implicitly.


Cleaning up unused repo labels

This is a...

[ ] Feature Request
[ ] Bug Report
[x] Doc process improvement

Problem:
There are currently 154 repo labels in this repo. Most of them receive no use (no issues or PRs assigned ever) and don't provide much help for assigning subject matter experts to content creation or reviews. Labels are more confusing than helpful, and don't reflect how SIG Docs actually applies labels to issues and PRs.
Proposed Solution:
Winnow the repo labels to include only labels that reflect the actual K8s docs process.
Page to Update:
https://github.com/kubernetes/kubernetes.github.io/labels

Repo labels as of 9/7/17, as returned by this gist:
Repo labels
Actionable
area/admin
area/api
area/apiserver
area/app-config-deployment
area/batch
area/build-release
area/cadvisor
area/clientlib
area/cloudprovider
area/controller-manager
area/daemonset
area/deployment
area/devexp
area/dns
area/docker
area/downward-api
area/ecosystem
area/etcd
area/example
area/example/cassandra
area/extensibility
area/HA
area/hw-accelerators
area/images-registry
area/introspection
area/isolation
area/kube-proxy
area/kubectl
area/kubelet
area/kubelet-api
area/logging
area/monitoring
area/node-e2e
area/nodecontroller
area/os/coreos
area/os/fedora
area/os/gci
area/os/ubuntu
area/platform/aws
area/platform/azure
area/platform/gce
area/platform/gke
area/platform/mesos
area/platform/vagrant
area/platform/vsphere
area/reliability
area/rkt
area/security
area/stateful-apps
area/swagger
area/system-requirement
area/test
area/test-infra
area/ui
area/upgrade
area/upward-api
area/usability
area/volumes
Automation
Bounty
cherrypick-approved
cherrypick-candidate
cla: human-approved
cla: no
cla: yes
CN LGTM
CN Review: Open Issues
cncf-cla: no
cncf-cla: yes
Code Under Development
do-not-merge
Docs LGTM
Docs Review: Open Issues
keep-open
kind/api-change
kind/bug
kind/cleanup
kind/design
kind/documentation
kind/enhancement
kind/feature
kind/flake
kind/friction
kind/mesos-flake
kind/new-api
kind/postmortem
kind/support
kind/technical-debt
kind/velocity-improvement
kind/workaround-removal
lgtm
Needs Clarification
Needs CN Review
Needs Docs Review
Needs Tech Review
Needs UX Review
needs-ok-to-merge
needs-rebase
ok-to-merge
P1
P2
P3
release-note
release-note-action-required
release-note-experimental
release-note-label-needed
release-note-none
Responsive
retest-not-required
retest-not-required-docs-only
sig/api-machinery
sig/apps
sig/auth
sig/autoscaling
sig/aws
sig/cli
sig/cluster-lifecycle
sig/cluster-ops
sig/contributor-experience
sig/federation
sig/instrumentation
sig/network
sig/node
sig/onprem
sig/openstack
sig/rktnetes
sig/scalability
sig/scheduling
sig/service-catalog
sig/storage
sig/testing
sig/ui
sig/windows
size/L
size/M
size/S
size/XL
size/XS
size/XXL
team/api
team/cluster
team/control-plane
team/gke
team/heptio
team/huawei
team/mesosphere
team/none
team/redhat
team/release-infra
team/ux
Tech Review LGTM
Tech Review: Open Issues
Website Feature Request

[Work in Progress]
Based on use and freshness, I'm removing the following labels:

Label
Reason

area/*
Maximum of 2 issues assigned per area

Automation
13 issues, last update January 2017

Bounty
No issues

cherrypick-approved
No issues

cherrypick-candidate
No issues

cla: human-approved
No issues

Code Under Development
Isn't it always? 😉

keep-open
No issues, better to signify in title or OP

@Bradamant3 @steveperry-53 👋 Currently there are five labels related to release notes:
release-note
release-note-action-required
release-note-experimental
release-note-label-needed
release-note-none

Before I remove them, I'd like your feedback about whether it makes sense to:
a. Remove them all
b. Remove none of them
c. Keep one label (release-note?)
None of them have any issues assigned.  Let me know! 🙇

@Bradamant3 Bumping for visibility. 🙇
/cc @chenopis for visibility

I'm specifically not removing labels for size/* yet: kubernetes/features has a script that auto-assigns size/*, and I'd like to see if it's worth implementing for docs.

OK, it's done. The number of labels is down to 30:
Current list of repo labels
Actionable
cla: no
cla: yes
CN LGTM
CN Review: Open Issues
cncf-cla: no
cncf-cla: yes
do-not-merge
Docs LGTM
Docs Review: Open Issues
lgtm
Needs Clarification
Needs CN Review
Needs Docs Review
Needs Tech Review
Needs UX Review
P1
P2
P3
size/L
size/M
size/S
size/XL
size/XS
size/XXL
team/heptio
team/katacoda
Tech Review LGTM
Tech Review: Open Issues
Website Feature Request


japan 9.2.0 n3ds files incompatible

upon using the supplied files for the system specified.
A 'too few titles found' error is given from sysdownloader

Incorrect hash map, again. I fixed it here.
@Plailect: I assume you have all firmware packs. Could you please check the other hash maps as well?
Also, the mega.nz mirror of 9.2.0-20J(Full)_n3DS.zip is down.

Fixed both of these

@Plailect I am still running into this issue with what I think is the latest. Do you know if perhaps the torrent/mega links haven't been updated?

Use latest sysDowngrader
On Thu, Sep 22, 2016, 9:35 PM Matt Laser<EMAIL_ADDRESS>wrote:

@Plailect https://github.com/Plailect I am still running into this
issue with what I think is the latest. Do you know if perhaps the
torrent/mega links haven't been updated?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Plailect/Guide/issues/430#issuecomment-249077835, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AQMWNmW60u7Xy_Y3eYlQNMACNcaUMU3Iks5qsyzXgaJpZM4JwrV6
.


Automate testing of examples

This is a placeholder task to work on automatic testing of deployments.

Let's use #67 to track, thank you!


ARROW-3836: [C++] Add PREFIX, EXTRA_LINK_LIBS, DEPENDENCIES to ADD_ARROW_BENCHMARK

Also removed some of the functions we had that were working around our lack of these arguments

+1. Appveyor build failure is the gflags thing


[SPARK-16003] SerializationDebugger runs into infinite loop

What changes were proposed in this pull request?
This fixes SerializationDebugger to not recurse forever when writeReplace returns an object of the same class, which is the case for at least the SQLMetrics class.
See also the OpenJDK unit tests on the behavior of recursive writeReplace():
https://github.com/openjdk-mirror/jdk7u-jdk/blob/f4d80957e89a19a29bb9f9807d2a28351ed7f7df/test/java/io/Serializable/nestedReplace/NestedReplace.java
cc @davies @cloud-fan
How was this patch tested?
Unit tests for SerializationDebugger.

Test build #60956 has started for PR 13814 at commit 3237c27.

Test build #60956 has finished for PR 13814 at commit 3237c27.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/60956/
Test PASSed.

LGTM

What's the error message looks like in the case of unserializable object (for example, Iterator in scala 2.10)?

LGTM

@davies the message looks ok to me:
Caused by: java.io.NotSerializableException: scala.collection.Iterator$$anon$13
Serialization stack:

	at org.apache.spark.serializer.SerializationDebugger$.improveException(SerializationDebugger.scala:40)
	at org.apache.spark.serializer.JavaSerializationStream.writeObject(JavaSerializer.scala:46)
	at org.apache.spark.serializer.JavaSerializerInstance.serialize(JavaSerializer.scala:100)
	at org.apache.spark.util.ClosureCleaner$.ensureSerializable(ClosureCleaner.scala:295)
	... 44 more

Looks good, merging this into master and 2.0 branch.


⚠ Bofrost.at has degraded performance

In 8ea5d06, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1248 ms

Resolved: Bofrost.at performance has improved in d8024da after 11 minutes.


kustomization CRD for BaaS

The docs currently mention how to setup a backup schedule with restic.
We use kustomize to manage our k8s deployments & overlays
Is there any intend to publish an open source kustomization CRD for apiVersion: backup.appuio.ch/v1alpha1? It would be especially useful when having multiple S3 buckets so that I could define a variable per OCP project with the correct bucket name in it.
Currently I need to overwrite the whole object in every project:
apiVersion: backup.appuio.ch/v1alpha1
kind: Schedule
metadata:
  name: backup-pods
spec:
  backend:
    s3:
      bucket: XXX # This is now for every OCP project different

This could be simplified (with the help of a CRD) to a single base config:
apiVersion: backup.appuio.ch/v1alpha1
kind: Schedule
metadata:
  name: backup-pods
spec:
  backend:
    s3:
      bucket: $(BUCKET_NAME)

Hi Marc
Sorry it took long for an answer.
We started heavily developing on K8up again and have soon a new release ready.
In the current (unreleased) master branch we have a Kustomize setup now: https://github.com/vshn/k8up/tree/master/config/crd/apiextensions.k8s.io. (use v1 for K8s 1.16+ and v1beta1 for K8s <= 1.15 like Openshift 3.11)
However, we aren't quite there yet. But is this going into the direction you imagined?

Absolutely. Thx!

Absolutely. Thx!


[Accessibility]A11y_VSCode_ViewDebug_ScreenReader: Screenreader does not read the necessary headings on the screen.

Environment Details:
VSCode Version : 1.24.0
OS Version : Win10
Additional Details:
MAS Violated : MAS 1.3.1
ScreenReader Versions : NVDA2018.1.1 / JAWS18.0.5038
Repro Steps:

Launch VS Code while NVDA/JAWS is ON.
Navigate to Activity Bar and select "View Debug "(Cntrl+Shift+D) button.
Navigate to complementary landmark -"View Debug " section and read the content "View Debug" using basic navigation.

Actual:
Screenreader does not read the content "View Debug" as appopriate heading which is so.
Same issue has been observed with JAWS.
Expected:
Screenreader should read- "View Debug" as heading with appropriate heading level.
Recommendations:
Add appropriate native heading level tag to the content "View Debug".
or,
Refer below link which is repository of bug fixes code snippets:
https://microsoft.sharepoint.com/teams/msenable/mas/pages/browse-fixes.aspx
User Impact:
The screenreader users will not be able to know the appropriate headings present on the screen.
MAS Reference:
MAS 1.3.1 - https://microsoft.sharepoint.com/teams/msenable/_layouts/15/WopiFrame.aspx?sourcedoc={54f28d1f-a2d1-4dcd-84e1-5c9b87e8aba4}
Attachment for Reference:
A11y_VSCode_ViewDebug_ScreenReader_Headings.pptx
Does this issue occur when all extensions are disabled?: Yes

Dup of https://github.com/Microsoft/vscode/issues/51760


editing group id not working

Hi,
I'm trying to make changes to excalidraw so that I can edit the groupIds value in the side panel. I'm opening this PR just for discussion, could someone help me how to do it right please?


esp32s3 USB0 register block issues

I'm playing around with possibly implementing an embassy-usb driver for esp32s3, and while doing so I noticed a few things that look like typos or transcription errors in the esp32s3 SVD file (an also in the esp32s2 one too).

The EPDISn field in the USB0.DIEPCTLn registers aren't named consistently: endpoints 0,1,2,4, and 6 call this D_EPDISN while endpoints 3 and 5 call this DI_EPDISn.  (using a DI_ prefix instead of D_)

The EPDISn fields in the USB0.DOEPCTLn registers appear to be listed as read-only.  This seems likely wrong?  The tinyusb esp code does set these fields, and the Synopsys USB docs provided for STMicro chips does document that these fields need to be set to disable OUT endpoints.  (As far as I could tell Espressif only provides minimal high level documentation for their USB cores, so I'm going off STMicro docs).

It's unfortunate that the USB0 FIFO ranges aren't listed in the SVD.  It looks like the existing blocking (non-embassy) USB drivers end up accessing the FIFO by manually computing the address from the start of the USB0 register block.  (reg_block + 0x1000 + fifo_num * 0x1000)

As an aside, the fact that all of the endpoint registers (DIEPCTLn, DOEPCTLn, DIEPINTn, DOEPINTn, etc) have different types for each endpoint makes the code much more awkward to use.  The endpoint 0 registers are slightly different from the others, but it would be nice if endpoints 1 through 5 all used the same types.
Also, very minor, but I wonder if the USB0.GINTSTS.RXFLVI name was a typo in the SVD and should have been RXFLVL instead?

Also, the MPS field looks incorrect in USB0.DIEPCTLn.  I believe this should be bits 0:2 in diepctl0, but bits 0:10 in diepctl1 through diepctl6.  However, it is listed as just 2 bits wide for all endpoints.
The DOEPCTLn registers to appear to be correct.

I guess there are two separate aspects to this issue:

obvious bugs that could be fixed with minimal changes (e.g., incorrect field bit widths, fields not being marked read-write)
re-organization for easier use in Rust (e.g., changing all the endpoint registers to use the same type, and renaming their fields to be consistent, possibly turning them into an array)

I'm not sure how much appetite there is to do the larger cleanup.  From a cursory search I didn't really see any downstream crates that seem to be using the USB0 register block much, so it possibly wouldn't disrupt too many things downstream.  That said, I'm not sure how much you want to avoid deviating from the base SVD.
If we did clean things up I would suggest:

Changing the DIEPTX1-4 registers to all use the same type, and turning them into an array
Changing all of the device endpoint registers (DIEPCTLn, DIEPINTn, etc) to use the same type for endpoints 1-6.  It would be nice group the endpoint registers into a sub-structure, and then make this into an array, as is done for the in_ep_reg and out_ep_reg fields of usb_dev_t in the soc/usb_struct.h files in the ESP-IDF.
I haven't used the host-side registers as much, bit it looks like there are a number of host-side registers that could use the same treatment (e.g., HCINT0-7, HCTSIZ0-7, HCDMA0-7, ...)

Thanks for the issue @simpkins! We very much have an appetite to do the cleanup, particularly in this case where there isn't a driver to update. It's much nicer write drivers when the PAC is in a good spot.
We really appreciate the PR, and any subsequent PRs you may file (the clean up suggestions look good to me!). Most of the Rust team will be on vacation till next week, and we'll get to reviewing your PR then :).

Oh and seeing as you're interested in async USB in the end, cc: @dominazzz and https://github.com/embassy-rs/embassy/issues/2494.
I also have a personal use for async USB coming up, so I'd be more than happy to help the both of you work through the issues :).

Thanks for the feedback.  I've got some code that is close to working (I think) for using embassy-usb on esp32s3; I'll try to make some more progress on it in the next few days and then upload it to github.  It isn't really based on the embassy-stm32 implementation--I looked at how they did some stuff, but it is largely from scratch with a few different design choices.  (I also looked at how tinyusb does things, plus the STMicro documentation, given that Espressif docs cite an NDA and don't include USB register documentation.)
I'll try to make a few more pull requests with SVD patches when I have made more progress.
Having a combined embassy-usb-driver implementation for both STM32 and ESP32 chips would be nice in the long run.  That said, I think it would take quite a bit of refactoring to make this work with esp-pacs--the USB0 API exposed by esp-pacs is rather different than the one used by the embassy-stm32 ral, even though the register block layout is nearly the same.
As an aside, I did notice one more SVD bug: the PKTCNT fields in DOEPTSIZn is listed as just 1 bit, while I believe it should be 10 bits in endpoints 1-6.  (At least, it's 10 bits in the STMicro docs.)

Closed via https://github.com/esp-rs/esp-pacs/pull/213


[FEATURE] Increase story limit

Description
Currently, the story feature only let us post one story at a time. I want to increase its limit to 5.
Screenshots
No response
Additional information
No response
Record

[X] I agree to follow this project's Code of Conduct
[X] I have checked the existing issues
[X] I'm a GSSoC'23 contributor
[X] I want to work on this issue

combine this with delete story issue

Okay, thanks.


Phinx cannot create indexes concurrently for postgres databases

There is no way to perform query which create index concurrently because phinx runs queries in transaction.
So migration have to has option to performs without transaction. For example, check this option in Phinx\Migration\Manager\Environment::executeMigration

Maybe indexes should be done outside of the transaction instead?

Sure. And phinx has to provide ability to do this.

Is there any workaround for this by now?

Closing due to lack of activity or out of scope. If there is new interest, please open a PR.


reduce max memory (#10775)

fixes the build break issue.

We chatted about this offline with Ken; merging in now.

Coverage decreased (-0.005%) to 34.258% when pulling 8f2293b56b500380697d28136068563bfb0b7921 on alanren/fix-build-break into b6be7f12189dc5e91b7cd34b0f497f8fd28c9910 on release/1.19.


meow dependency has vulnerability

  Low             Prototype Pollution
  Package         yargs-parser
  Patched in      >=13.1.2 <14.0.0 || >=15.0.1 <16.0.0 || >=18.1.2
  Dependency of   graphqlviz [dev]
  Path            graphqlviz > meow > yargs-parser
  More info       https://npmjs.com/advisories/1500

meow fixed their dependency a while ago, but you're on an older version presumable because moving from 5.0.0 to 6.0.0 was a breaking change.

This PR has been opened since June.  Is this project dead?


Outpost capture is not implemented

Linked PRs

gh-61

After capture, a pop window /frame should change to the army frame where the user picks how many troops to send

I'll get to work on the start of implementing this

I've implemented that. Waiting on API support.

I believe I've already implemented the backend for this.

I could not find the required API methods @ItsNeil17

Alright then, we'll do it later. I'm working on adding the websockets at the moment. Please check out feat/frontend and work on it if you can @Owen-Griffin.
As discussed with our plan, the resource bar will be at y=0, let me know if you need help.

okay!


Ids must be an object

I'm completely lost on this.
Why am I getting this error? I want ids to definitely be an array but simple schema is erroring out that is has to be an object with check()
How do I make simple schema and meteor support this?
type: Object
ids: Array[4]
0: "6Z2kL8vqqi5JmcDZh"
1: "LmMJrjZCpnwNqkRtD"
2: "LXmfgR623k8K94Zsy"
3: "6Z2kL8vqqi5JmcDZh"

check(room, Schema.pick('name', 'type', 'type.ids.$')); ends up returning Ids must be an object [400]
Schema:
  'type.ids': {
    type: Array,

  },
  'type.ids.$': {
    type: String
  },

It should work if you add 'type.ids' to pick


Collections with HLG must always implement dask_layers

Without __dask_layers__, HighLevelGraph.from_collections will produce a broken layer dependency graph and things will fall apart down the line. This makes me deduce that none of our users should have the use case in production, so I think it should be safe not to have a deprecation cycle here.

test failure unrelated - see https://github.com/dask/dask/issues/8549

Ah - maybe this + #8550 makes windows pass? Am I getting that right?


Add RdataString() to all types already implementing RR interface

Needed a way to gather the rdata as a string minus the header string for a RR, and the only way to really do it for most RRs would be to chop off the header string after calling RR.String(). This PR adds RR.RdataString() so we get it directly, and RR.String() behaves the same in all cases.

Codecov Report

Merging #1035 into master will increase coverage by 0.01%.
The diff coverage is 57.97%.

@@            Coverage Diff             @@
##           master    #1035      +/-   ##
==========================================
+ Coverage   54.92%   54.94%   +0.01%
==========================================
  Files          41       41
  Lines        9869    10012     +143
==========================================
+ Hits         5421     5501      +80
- Misses       3425     3486      +61
- Partials     1023     1025       +2

Impacted Files
Coverage Δ

edns.go
27.56% <0%> (-0.18%)
:arrow_down:

dns.go
60% <0%> (-1.54%)
:arrow_down:

tsig.go
40.46% <0%> (-0.38%)
:arrow_down:

privaterr.go
72.54% <100%> (+2.33%)
:arrow_up:

types.go
70.84% <59.33%> (-4.22%)
: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 9b7437f...a6d2f41. Read the comment docs.

This might be what your looking for https://godoc.org/github.com/miekg/dns#Field (not super ideal api, but will get the job done)

@miekg That's not a solution. Just see https://github.com/miekg/dns/pull/1035/files#diff-e871404fd69cab40521d6b2178847cf7R913-R955 or many other types in there with complex RdataString implementations.

@miekg Can you check this out again?

@UmanShahzad "Needed a way to gather the rdata as a string minus the header string for a RR," Can you explain why you need this?

@tmthrgd We were loading rdata strings from CZDS/Verisign zonefiles into a db and doing some analysis.

@UmanShahzad Not all the records actually have well formed ‘rdata strings’ and some are simply for presentation and subject to change. Without knowing more it sounds like something like JSON encoding the record structs would be more appropriate and stable.


Discussion: forkJoin completing early if any source completes without value

The current behavior as described in a marble test:
    it('should complete early if any of source is empty and completes before than others', () => {
      rxTestScheduler.run(({ hot, expectObservable }) => {
        const e1 = forkJoin({
          foo: hot('      --a--b--c--d--|'),
          bar: hot('      (b|)'),
          baz: hot('      ---------|'),
        });
        const expected = '---------|';

        expectObservable(e1).toBe(expected);
      });
    });

Thoughts:
This seems like it should be an known error type of some sort. Like an EmptyError or the like. Instead, the result completes as if everything is "okay" but doesn't provide a value. It's certainly detectable... but it's a bit of nuance I'd wager most people don't know. And it seems like an exceptional case.
Proposal:
Have forkJoin emit an error of EmptyError if a provided source completes without emitting a value.

Core team agreement: This should be an EmptyError. Unfortunately, that is a breaking change, and will have to wait for version 8.

forkJoin semantics for the dictionary form make early termination handling a bit less intuitive.  For version 8, is it possible to have alternative behavior in which the dictionary entry for completed-without-emitting sources is undefined, with other entries populated?

@supercargo you can accomplish what you're asking right now like so:
forkJoin(sources.map(defaultIfEmpty(undefined)))

example here

@benlesh Good point, and thanks for pointing out some higher order functions that can fill the gap, but map isn't available if sources is an object rather than an array, but maybe that's a JS/TS language issue and not something for RXJS to solve.
Anyway, my point is that requiring non-empty observables for the array form makes sense since the input and output need to be tuples of the same arity.  However, missing values (or keys) in objects is more natural, which is why I had a read-the-docs moment with forkJoin object form.  Either way, I'm glad to see the EmptyError will help highlight these situations.


Noir Contracts: What's the purpose of pack_arguments?

fn call_public_function<ARGS_COUNT>(
        &mut self,
        contract_address: Field,
        function_selector: Field,
        args: [Field; ARGS_COUNT]
    ) -> PublicCallStackItem {
        let args_hash = hash_args(args);
        assert(args_hash == arguments::pack_arguments(args));
        self.call_public_function_with_packed_args(contract_address, function_selector, args_hash)
    }

#[oracle(packArguments)]
fn pack_arguments_oracle<N>(_args: [Field; N]) -> Field {}

unconstrained fn pack_arguments<N>(args: [Field; N]) -> Field {
    pack_arguments_oracle(args)
}

Is the line assert(args_hash == arguments::pack_arguments(args)); intended to be a simple internal check, to cause an early error, or is intended to lay down a proper constraint?
My concern is that this doesn't constrain anything, because the packing is being done in typescript and not in noir.
@sirasistant (for when you're back next week), maybe I'm misunderstanding the intention?

As you said It's just an early fail sanity check. The packArguments oracle sends some arguments to the simulator for storing for later use, such as a nested call. It returns the hash that typescript believes those arguments have. In the contract we match it with the args_hash that we calculate to fail early if the simulator miscalculated the hash of the arguments. So in summary:

The purpose of pack_arguments is allowing contracts to make the simulator remember the preimage of some args_hash for later use
The constrain on the result of pack_arguments is just a sanity check

I wonder if (as a non-urgent, future enhancement), we rename pack_arguments to store_arguments or retain_arguments, to make the purpose clearer.
Maybe we also add a separate oracle to perform the args_hash check in typescript land, instead of having the line assert(args_hash == arguments::pack_arguments(args));.
Would assert(args_hash == arguments::pack_arguments(args)); ever catch an error, given we have the line let args_hash = hash_args(args); before it?

I wonder if (as a non-urgent, future enhancement), we rename pack_arguments to store_arguments or retain_arguments, to make the purpose clearer.
Sounds good!

Would assert(args_hash == arguments::pack_arguments(args)); ever catch an error, given we have the line let args_hash = hash_args(args); before it?

In case the typescript is hashing the parameters the wrong way yes, it should catch it, since hash_args() is a noir function that will do the hashing inside the circuit and the return of pack_arguments is the typescript hash


Explore PyArrow table value sorting expectations (and possible changes)

From #174:

I found that duckdb==0.10.1 entails lowered determinism for joined data result value sorting. We previously have relied on PyArrow to consistently sort all columns and their values for testing - this appears to also be potentially in need of adjustment. As a result, I've added SQL ORDER BY ALL (which orders all values in all columns from left to right) to one test which consistently failed with comparisons. As a to-do, we should explore why PyArrow is unable to perform the same level of data organization for testing and possibly raise an issue with that project if the results aren't in alignment with the design. Alternatively, moving to ORDER BY ALL or some parallel may be necessary to address the existing PyArrow-based data sorting for testing (otherwise we may sporadically see issues over time).

Thinking on this more and exploring a bit, outlining thoughts and findings so far below. This appeared again in #181, so I'm focusing on figuring out more of the reasons why this might occur
When this happens, the following appear to be consistent patterns:

Python version: Any (despite initially appearing after python==3.12 work in #174)
DuckDB version duckdb==0.10.1
PyArrow version pyarrow==15.0.2
Input data: occurs with SQLite data from NF1 project used for testing purposes (link)
Parsl config: occurs with both HTE (multiprocess'ed) and TPE (multithreaded) Parsl configuration.
Pytest tests: appears in newly added or modified tests only (existing tests don't seem to exhibit the same behavior).
The behavior is different each time: the values appear to be slightly different and in different amounts each test run.

As a quick check I tried verifying that PyArrow sorting works the way it should. It seems that it does properly sort all values by all columns when implemented the way it is in CytoTable tests. See here for code demonstrating this.
I feel there are several other possibilities for what's occurring which I'll work through in order to verify what's happening.

DuckDB is inconsistently reading Parquet datasets (lists of files treated as a single table).
DuckDB is inconsistently joining multiple Parquet datasets
DuckDB threads are somehow causing challenges when used within multiple Parsl threads or processes on the same machine (perhaps overlapping one another or operating in a way that is unsafe).
Parsl threads or processes are causing challenges with task completions associated with DuckDB or PyArrow work.


Action "Create Todo" successfully creates object but returns 500

API Endpoint
POST /todos
Problem
// src/service/TodoService.cpp

auto result = dbResult->fetch<oatpp::Vector<oatpp::Object<TodoDto>>>();

result.size() // = 0

// Should be N, where N is the number of rows in the database.

Working branch for issue
breaking

This bug was solved in #3


Screen Resolution change

Y axis is fixed on ubuntu 17.10
windows does not fit on screen.
consider option to modify screen resolution on user end
it's just far too big

@sibaar this issue is fixed. Just yet to be released

Should clarify that I'm having problems on Y axis. Height, not width.

@sibaar this issue is now fixed here https://github.com/ifedapoolarewaju/igdm/releases/tag/v2.4.0


Replace an occurrence of stdgates.qasm with stdgates.inc

In another PR We are adding behavior around stdgates.inc to the spec, and the name of the file is fixed. The appearance of include "stdgates.qasm" here is confusing because it looks like it is including the standard library declarations, but in fact is not.

See #517

Any opinions on a release note here? I could do one of

Add the no-release-note tag
Write a release note

Hmmm. I'm inclined to write one. Before this change the spec might give someone the impression that .qasm was officially sanctioned. I actually was led astray by it and hardcoded it in the rust parser. Someone might misremember that the spec at one time sanctioned .qasm but now does not.

@hodgestar Thanks for approving earlier. I thought a release note might be in order, so I added one.


Update Exchange-Teams-interact.md

confirmed a while ago with Joao Loureiro.

@JohanFreelancer9 Copy editing is needed for this PR. Thanks.


Update cats-effect, cats-effect-laws to 3.2.3

Updates

org.typelevel:cats-effect
org.typelevel:cats-effect-laws

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

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel" } ]

labels: library-update, semver-patch

Codecov Report

Merging #530 (6a7c3d5) into main (903506c) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #530   +/-   ##
=======================================
  Coverage   90.10%   90.10%
=======================================
  Files          15       15
  Lines         758      758
  Branches       43       40    -3
=======================================
  Hits          683      683
  Misses         75       75

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 903506c...6a7c3d5. Read the comment docs.


Allow rounding

Is there currently any way to enable the round feature of animejs?
For example https://www.npmjs.com/package/animejs#dom-attributes
anime({
  targets: input,
  value: 1000 // Animate the input value to 1000
  round: 1 // Remove decimals by rounding the value
});

sorry for the delay in responding.
I'll take a look at this attribute, thank you.
But for now you can use the formatValue prop to do this


The model definition  different from the actual latest export model definition

The model definition in the documentation is different from the actual latest export model definition.

@noueh : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Note that publishing in this repository is suspended until Tuesday, May 25. Merging will resume Tuesday. Authors can still review and sign off on PRs in the interim. Thanks.

Thanks for the PR! But actually the script on this page is correct for "General (compact)" domain. I think it's better if we add a note to describe 1) this page is for "general (compact)" domain and 2) visit https://github.com/Azure-Samples/customvision-export-samples for other domains.

@shonohs , Thank you for pointing that out. I understand. Please edit it that way.
On github, there are two options, "TensorFlow (Frozen Graph)" or "TensorFlow (Saved Model)".
The export screen in the Custom Vison portal does not offer this option.
Could you please also add a note explaining which should choose?

created #76090.
Also added a footnote about Frozen Graph to the README of the sample code repo.

@shonohs Should I merge the existing changes here?

@PatrickFarley Please merge #76090, and close #75667 without merging.


Testcontainer build using Dockerfile hangs on WSL 2 based engine if the Dockerfile directory contains .dockerignore

The command used:
const buildContext =
const container = await GenericContainer.fromDockerfile(buildContext).build();
It hangs and never finishes.
Tested on Windows 10:

Docker Desktop v4.0.1(Engine: 20.10.8) with WSL2/Hyper-V engine enabled
WSL 2 distro Ubuntu
Passes if running on pure Linux VM (tested on RHEL)

Hi @armen-ch, could you please share the log output (run with DEBUG=testcontainers* env variable)?

Hi @cristianrgreco,
Here you go:
Pact: Securities Provider Interface expected by Watchlist Provider verification
testcontainers DEBUG Creating new Docker instance +0ms
Building microservice docker container...
testcontainers DEBUG Creating new Reaper for session: 058a390c608c2c3e5b65ba092df0e9c7 +43ms
testcontainers INFO  Docker host strategy OUTSIDE_CONTAINER: localhost +4ms
testcontainers DEBUG Executing Docker credential provider: docker-credential-desktop.exe +4ms
testcontainers DEBUG System diagnostics: {
testcontainers   "node": {
testcontainers     "version": "v14.18.0",
testcontainers     "architecture": "x64",
testcontainers     "platform": "linux"
testcontainers   },
testcontainers   "docker": {
testcontainers     "serverVersion": "20.10.8",
testcontainers     "operatingSystem": "Docker Desktop",
testcontainers     "operatingSystemType": "linux",
testcontainers     "architecture": "x86_64",
testcontainers     "cpus": 8,
testcontainers     "memory":<PHONE_NUMBER>0
testcontainers   },
testcontainers   "dockerCompose": {
testcontainers     "version": "1.29.2"
testcontainers   }
testcontainers } +1s
testcontainers DEBUG Docker credential provider exited with code: 0 +2s
testcontainers DEBUG Docker credential provider found auth config for https://index.docker.io/v1/ +0ms
testcontainers DEBUG Found applicable registry auth locator for registry "https://index.docker.io/v1/": CredsStore +0ms
testcontainers DEBUG Not pulling image as it already exists: testcontainers/ryuk:0.3.2 +8ms
testcontainers INFO  Creating container for image: testcontainers/ryuk:0.3.2 +4ms
testcontainers INFO  Starting container testcontainers/ryuk:0.3.2 with ID: 239a06dbb36471308418c05dc7dda33f5855d869d7c35f8157776ebef0b6c01a +830ms
testcontainers:containers TRACE 239a06dbb36471308418c05dc7dda33f5855d869d7c35f8157776ebef0b6c01a: 2021/11/18 10:42:05 Pinging Docker... +0ms
testcontainers:containers TRACE 239a06dbb36471308418c05dc7dda33f5855d869d7c35f8157776ebef0b6c01a: 2021/11/18 10:42:05 Docker daemon is available! +0ms
testcontainers:containers TRACE 239a06dbb36471308418c05dc7dda33f5855d869d7c35f8157776ebef0b6c01a: 2021/11/18 10:42:05 Starting on port 8080... +0ms
testcontainers:containers TRACE 239a06dbb36471308418c05dc7dda33f5855d869d7c35f8157776ebef0b6c01a: 2021/11/18 10:42:05 Started! +0ms
testcontainers DEBUG Waiting for container to be ready: 239a06dbb36471308418c05dc7dda33f5855d869d7c35f8157776ebef0b6c01a +940ms
testcontainers DEBUG Waiting for host port 21790 for 239a06dbb36471308418c05dc7dda33f5855d869d7c35f8157776ebef0b6c01a +1ms
testcontainers DEBUG Waiting for internal port 8080 for 239a06dbb36471308418c05dc7dda33f5855d869d7c35f8157776ebef0b6c01a +2ms
testcontainers DEBUG Host port 21790 ready for 239a06dbb36471308418c05dc7dda33f5855d869d7c35f8157776ebef0b6c01a +12ms
testcontainers:containers TRACE 239a06dbb36471308418c05dc7dda33f5855d869d7c35f8157776ebef0b6c01a: 2021/11/18 10:42:05 New client connected: <IP_ADDRESS>:49044 +31ms
testcontainers:containers TRACE 239a06dbb36471308418c05dc7dda33f5855d869d7c35f8157776ebef0b6c01a: 2021/11/18 10:42:05 Received the first connection +0ms
testcontainers:containers TRACE 239a06dbb36471308418c05dc7dda33f5855d869d7c35f8157776ebef0b6c01a: 2021/11/18 10:42:05 EOF +1ms
testcontainers:containers TRACE 239a06dbb36471308418c05dc7dda33f5855d869d7c35f8157776ebef0b6c01a: 2021/11/18 10:42:05 Client disconnected: <IP_ADDRESS>:49044 +0ms
testcontainers:containers TRACE 239a06dbb36471308418c05dc7dda33f5855d869d7c35f8157776ebef0b6c01a: 2021/11/18 10:42:06 New client connected: <IP_ADDRESS>:34037 +1s
testcontainers:containers TRACE 239a06dbb36471308418c05dc7dda33f5855d869d7c35f8157776ebef0b6c01a: 2021/11/18 10:42:06 EOF +0ms
testcontainers:containers TRACE 239a06dbb36471308418c05dc7dda33f5855d869d7c35f8157776ebef0b6c01a: 2021/11/18 10:42:06 Client disconnected: <IP_ADDRESS>:34037 +0ms
testcontainers DEBUG Internal port 8080 ready for 239a06dbb36471308418c05dc7dda33f5855d869d7c35f8157776ebef0b6c01a +1s
testcontainers INFO  Container is ready +0ms
testcontainers DEBUG Connecting to Reaper 239a06dbb36471308418c05dc7dda33f5855d869d7c35f8157776ebef0b6c01a on localhost:21790 +1ms
testcontainers DEBUG Connected to Reaper 239a06dbb36471308418c05dc7dda33f5855d869d7c35f8157776ebef0b6c01a +1ms
testcontainers DEBUG Preparing to build Dockerfile: /home/achuljyan/workspace/testcontainers-node/fixtures/docker/docker/Dockerfile +0ms
testcontainers DEBUG Re-using cached auth for registry https://index.docker.io/v1/ +2ms
testcontainers INFO  Building image '5e6c359dcb2c952ae217d248a52bdda4:9f3985f50a60c54f326c1d491abbb6b5' with context '/home/achuljyan/workspace/testcontainers-node/fixtures/docker/docker' +1ms
testcontainers:containers TRACE 239a06dbb36471308418c05dc7dda33f5855d869d7c35f8157776ebef0b6c01a: 2021/11/18 10:42:06 New client connected: <IP_ADDRESS>:49050 +152ms
testcontainers:containers TRACE 239a06dbb36471308418c05dc7dda33f5855d869d7c35f8157776ebef0b6c01a: 2021/11/18 10:42:06 Adding {"label":{"org.testcontainers.session-id=058a390c608c2c3e5b65ba092df0e9c7":true}} +0ms
It stops at this point. Once I remove .dockerignore and rerun the script with command it builds image successfully.
Thanks

Thanks @armen-ch, and could you please also share the .dockerignore file contents? I don't have access to a Windows machine too often so just want to get as much info as I can :slightly_smiling_face:

Hi @cristianrgreco,
It looks like you got right to the point :).
node_modules
npm-debug.log
Dockerfile
*.md
cfg

"Dockerfile" is the reason. If I delete it, the build passes through. Hopefully the fix will be pretty easy.
Thank you!

@armen-ch Fixed in 7.23.2, thanks for raising!

Hi,
@cristianrgreco I believe the fix is not bulletproof - you can't expect the Dockerfile name to appear there "as is" - it might be *.Dockerfile or completely missing if ignoring everything except for specific files:
*
!src

I think it's better to add the Dockerfile explicitly to the tar after adding the context. wdyt?

I actually see we are not supporting the full syntax of .dockerignore like negative (!) matches - this should be mentioned in the docs I believe.

Thanks for raising those 2 points @SBD580, they've both been addressed in 8.6.0

Awesome! Thank you for taking this and this entire wonderful lib!


Can I use aminal as an in-process terminal emulator?

Is your feature request related to a problem? Please describe.
Similar to #118, is aminal embeddable? This is a separate issue, because I want to embed the terminal emulation part of aminal within a command-line tool. I do not want to use the windowed GUI (because I want my tool to be run within terminal/cmd).
Describe the solution you'd like
My goal is to have a cross-platform command-line tool that uses aminal for terminal emulation (like GNU screen, or tmux) with a custom transport layer.
Question 1, can I use aminal with a custom transport layer? Question 2, can I embed aminal within a command-line tool?
Describe alternatives you've considered
I've looked at using GNU screen, but A) it's not cross plaform and B) I don't know how to make it work with my custom transport, without all kinds of gymnastics.
Additional context
I am working on a specialized tool that more or less connects to a console on a remote device via a TCP/IP tunnel. I would like to use aminal as a front-end to this tunneled console. My transport protocol is very non-standard and I can guarantee that I won't be able to find existing tools for this.

Hi - I made a simple terminal widget as part of the gowid project, available at https://github.com/gcla/gowid. On the README is an example of a very simple terminal application that embeds this widget - a poor man's tmux. I'm not wholeheartedly recommending it, and if aminal was embeddable, I would absolutely try to connect it to gowid instead and replace what I did, but for now, it might be useful for you. My golang implementation is plagiarized from urwid's original python terminal widget - http://urwid.org/. It's VT220++, and vttest seems to render correctly. One user reported some problems with the display of wider runes like Chinese characters, and there's a branch called widerunes that fixes some of these issues. Looking forward to aminal's progress!

Closed due to complete rewrite as part of bringing the project back to life, please create a new issue if still relevant. Thank you!


Allow j2objc built libraries to link to other Gradle native libraries.

Note the other libraries could be C[++], Objective-C[++], etc.

LGTM

LGTM with minor comments. Ping me back if you question any of my feedback.

done all, unit tests pass, merging


Release in packagist

As the basic development is finished, it's time to publish it on packagist and use it in tongqu. Someone need to register a packagist account and release this lib...
@at15 @Bluemit

@ComMouse leave it to you /w\

@at15 https://packagist.org/search/?q=dyweb

@ComMouse yeah, I got the account.

https://packagist.org/packages/dyweb/redis-cache The webhook should be working now

Thx. =w=


Device support

Does the developer will make the jalbreak compatible with iphone 7 with ios 10.2 or he will not
And if he cant is there any way to jailbreak my iphone 7 ?

#162 yes look on r/jailbreak
On 29 jan. 2017 23:59 +0100, mohammadabumoosa<EMAIL_ADDRESS>wrote:

Does the developer will make the jalbreak compatible with iphone 7 with ios 10.2 or he will not
And if he cant is there any way to jailbreak my iphone 7 ?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Feature Request : CRD creation prior Rancher Launch

It would be nice to create CRDs prior Rancher Launch.
Usage Example:

Create Rancher CRD ./rancher --setup-only
Create Admin User
Create Ldap Config
Start Rancher ./rancher

Right now, Rancher ensure that CRDs are present before registering routes and starting the Rancher API. There is many ways to create CRD prior Rancher Launch :

Add a command to generate CRD
Add flag --setup-only and exit(0) after app.go:99
etc.

The first option can be nice... but we should also add a new flag --skip-crd-creation because assertion are slow.
The second option is already implemented in my company so I can create a PR but... mounting routes and stop execution is not really a good design :/.
What do you think?

If you need to create Rancher CRD's before Rancher launch (for example, if you want to configure rancher in a GitOps way) and put them in an helm v3 package crds/rancher.crds... you can use the following script (thx @synehan)
#!/bin/bash

RANCHER_VERSION=$1

RANCHER_REPO_URL=https://releases.rancher.com/server-charts/latest

BASEDIR=$(dirname "$0")
cd $BASEDIR

# Pre Checks

if ! command -v rancher &> /dev/null
then
    echo "rancher could not be found"
    exit 1
fi

if ! command -v kind &> /dev/null
then
    echo "kind could not be found"
    exit 1
fi

if [ "$RANCHER_VERSION" = "" ]
then
    echo "rancher version not provided. please provide the rancher version as an argument to this script"
    exit 2
fi

kind create cluster --image kindest/node:v1.19.4 --name rancher-crd

if [ $? != 0 ]
then
    echo "kind cluster creation failed"
    delete_kind
    exit 3
fi

delete_kind () {
    kind delete cluster --name rancher-crd
}

##############################
### Cert-manager installation
##############################

# Install the CustomResourceDefinition resources separately
kubectl apply --validate=false -f https://github.com/jetstack/cert-manager/releases/download/v1.0.4/cert-manager.crds.yaml

# **Important:**
# If you are running Kubernetes v1.15 or below, you
# will need to add the `--validate=false` flag to your
# kubectl apply command, or else you will receive a
# validation error relating to the
# x-kubernetes-preserve-unknown-fields field in
# cert-manager’s CustomResourceDefinition resources.
# This is a benign error and occurs due to the way kubectl
# performs resource validation.

# Create the namespace for cert-manager
kubectl create namespace cert-manager

# Add the Jetstack Helm repository
helm repo add r-j-crd https://charts.jetstack.io

# Update your local Helm chart repository cache
helm repo update

# Install the cert-manager Helm chart
helm install \
  cert-manager r-j-crd/cert-manager \
  --namespace cert-manager \
  --version v1.0.4 --wait

# Cleanup temporary helm repository
helm repo remove r-j-crd

# Check if Cert-manager is working
kubectl wait --for=condition=available -n cert-manager deployment cert-manager

if [ $? != 0 ]
then
    echo "cert-manager was not correctly deployed"
    delete_kind
    exit 3
fi

# Add Rancher Helm Repository
helm repo add r-l-crd $RANCHER_REPO_URL

# Create Rancher namespace
kubectl create namespace cattle-system

# install rancher
helm install rancher r-l-crd/rancher \
  --namespace cattle-system \
  --set hostname=rancher.my.org \
  --version $RANCHER_VERSION --wait

# Add Rancher Helm Repository
helm repo remove r-l-crd

# Check if rancher is working
kubectl wait --for=condition=available -n cattle-system deployment rancher

if [ $? != 0 ]
then
    echo "rancher was not correctly deployed"
    delete_kind
    exit 3
fi

true > ../crds/crd.yaml; for i in $(kubectl get crd -o name | grep management.cattle.io); do echo '---' >> ../crds/crd.yaml; kubectl get $i -o yaml | yq d - status | yq d - metadata.annotations | yq d - metadata.creationTimestamp | yq d - metadata.generation | yq d - metadata.resourceVersion | yq d - metadata.selfLink | yq d - metadata.uid | yq d - metadata.managedFields >> ../crds/crd.yaml; done

delete_kind

If you need to create Rancher CRD's before Rancher launch (for example, if you want to configure rancher in a GitOps way) and put them in an helm v3 package crds/rancher.crds... you can use the following script (thx @synehan)
#!/bin/bash

RANCHER_VERSION=$1

RANCHER_REPO_URL=https://releases.rancher.com/server-charts/latest

BASEDIR=$(dirname "$0")
cd $BASEDIR

# Pre Checks

if ! command -v rancher &> /dev/null
then
    echo "rancher could not be found"
    exit 1
fi

if ! command -v kind &> /dev/null
then
    echo "kind could not be found"
    exit 1
fi

if [ "$RANCHER_VERSION" = "" ]
then
    echo "rancher version not provided. please provide the rancher version as an argument to this script"
    exit 2
fi

kind create cluster --image kindest/node:v1.19.4 --name rancher-crd

if [ $? != 0 ]
then
    echo "kind cluster creation failed"
    delete_kind
    exit 3
fi

delete_kind () {
    kind delete cluster --name rancher-crd
}

##############################
### Cert-manager installation
##############################

# Install the CustomResourceDefinition resources separately
kubectl apply --validate=false -f https://github.com/jetstack/cert-manager/releases/download/v1.0.4/cert-manager.crds.yaml

# **Important:**
# If you are running Kubernetes v1.15 or below, you
# will need to add the `--validate=false` flag to your
# kubectl apply command, or else you will receive a
# validation error relating to the
# x-kubernetes-preserve-unknown-fields field in
# cert-manager’s CustomResourceDefinition resources.
# This is a benign error and occurs due to the way kubectl
# performs resource validation.

# Create the namespace for cert-manager
kubectl create namespace cert-manager

# Add the Jetstack Helm repository
helm repo add r-j-crd https://charts.jetstack.io

# Update your local Helm chart repository cache
helm repo update

# Install the cert-manager Helm chart
helm install \
  cert-manager r-j-crd/cert-manager \
  --namespace cert-manager \
  --version v1.0.4 --wait

# Cleanup temporary helm repository
helm repo remove r-j-crd

# Check if Cert-manager is working
kubectl wait --for=condition=available -n cert-manager deployment cert-manager

if [ $? != 0 ]
then
    echo "cert-manager was not correctly deployed"
    delete_kind
    exit 3
fi

# Add Rancher Helm Repository
helm repo add r-l-crd $RANCHER_REPO_URL

# Create Rancher namespace
kubectl create namespace cattle-system

# install rancher
helm install rancher r-l-crd/rancher \
  --namespace cattle-system \
  --set hostname=rancher.my.org \
  --version $RANCHER_VERSION --wait

# Add Rancher Helm Repository
helm repo remove r-l-crd

# Check if rancher is working
kubectl wait --for=condition=available -n cattle-system deployment rancher

if [ $? != 0 ]
then
    echo "rancher was not correctly deployed"
    delete_kind
    exit 3
fi

true > ../crds/crd.yaml; for i in $(kubectl get crd -o name | grep management.cattle.io); do echo '---' >> ../crds/crd.yaml; kubectl get $i -o yaml | yq d - status | yq d - metadata.annotations | yq d - metadata.creationTimestamp | yq d - metadata.generation | yq d - metadata.resourceVersion | yq d - metadata.selfLink | yq d - metadata.uid | yq d - metadata.managedFields >> ../crds/crd.yaml; done

delete_kind


google-batch provider and preemptible job support

Hi, I'm using the latest dsub (0.4.12) to submit some GPU jobs through google-batch. The jobs get submitted, scheduled and run just fine, however they are run on standard instances rather than spot even though I specify --preemptible in my dsub call. Any idea why this might be happening? Is the batch provider not passing through the spot flag, or is the Google Batch API not honoring it?
Here's my call, for the record:
dsub --provider google-batch --project {project} --regions us-east1 --machine-type g2-standard-8 --accelerator-type nvidia-l4 --accelerator-count 1 --preemptible --image {image} --boot-disk-size 100 --retries 0 --wait --service-account {service_account} --name {name_str}

Hi @jacekzkominek !
In the 0.4.12 release, the preemptible flag value is not wired through. It is going to be in the 0.4.13 release. Our target is to push this out next week.
-Matt

Got it, thank you @mbookman very much for a prompt response, and I'm looking forward to 0.4.13!

Hi @jacekzkominek,
We just released v0.4.13 which includes support for preemptible (spot) instances with the google-batch provider.
When you get the chance, can you verify if it resolves your issues?

@wnojopra , sure thing, just submitted a test job and the GCP Batch web interface shows it scheduled to run on a Spot instance, so I think everything works well now, thank you!


rubocop: simple syntax changes

This fixes some rubocop errors. These ones are adjusting whitespace and changing CGI::unescape x to CGI.unescape(x).
In combination with the other PRs I'm submitting, it should result in CI passing. CI won't be passing in its entirety without all of the PRs being merged. This is in multiple PRs because you may not want parts of it, so only take the ones, or just the commits, which are desired.

Closing this to re-create it in a way that results in CircleCI running on it.


UR5 not working correctly

The UR5 seems not to be simulated correctly. It's the only robot that shakes directly after start. While with the others I can execute trajectories, with the UR5 this doesn't work.

probably a duplicate of #11

Is there a workaround? Can we use the E-series model as a reference, or are the controls significantly different?

As of https://github.com/UniversalRobots/Universal_Robots_ROS2_Description/pull/127, this should no longer be an issue. I created #57 to remove the out-of-date note in the README.

@RobertWilbrandt I am new to this. Do I still need to use this repo and combine it with https://github.com/UniversalRobots/Universal_Robots_ROS2_Description repo ?
or is the ros2 Description a new "working" version of the gazebo simulation ?

This repo uses the robot models from ur_robot_description (see here). You don't have to do anything extra for this.
You would normally create a new description and simulation package for adding more external components to the arm. In the description you would instantiate the ur xacro macro and then add your custom urdf / xacro to it. We are currently working on a tutorial here, you can take a look if it is useful to you in its current form already.
Feel free to open a new issue if there are problems with this.


Ability to specify which dimension should be enforced: width or height

The enforceBoundary option is nice, but unless your image is the same aspect ratio as your viewport, part of your image is going to get cropped when you're zoomed all the way out.
There has been some interest in only enforcing one of the dimensions so the entire image can fit when zoomed out.
I can see this going one of two ways.  Either specify which dimension to enforce, or just enforce one automatically.  So if the image is taller than it is wide, we enforce the height restriction.  And vice versa.

Is it possible to enforce a rule where the cropped image isn't a perfect circle Example: "Oval shape" as it is possible to specify that in the viewport during cropping but the result returns a perfect circle which isn't in the same dimension as the viewport during cropping.

Unfortunately no.  I don't think it'd be too difficult though.
Feel free to tinker around and submit a PR, I'd love to merge it in.

On croppie.js line  979,  I changed a few things, added ctx.scale(1,2) and changed the arc arguments but only the top of the image is returned as an oval shape, the bottom of the image isn't. Pardon me for asking but what could be causing this issue? Thanks
ctx.scale(1,2);             ctx.beginPath();             ctx.arc(outWidth / 2, outHeight / 2, outWidth *0.7 , 0, Math.PI * 2, true);             ctx.closePath();

Ok, so after some work around within a busy schedule, I was able to get the oval shape but with the top cut off, which is the shape that I wanted  using this
ctx.fillStyle = '#fff';  ctx.globalCompositeOperation = 'destination-in'; ctx.scale(1,2);  ctx.beginPath();  ctx.arc(outWidth / 2, (outHeight/4)-5, (outHeight/4)+5, 0, Math.PI * 2, true);  ctx.closePath(); ctx.fill();
Another issue that I faced was that with some devices like android and Iphones, the original orientation wasn't set to portrait. I enabled ExIF which caused the final cropped image to be out of orientation and cropped the wrong portion of the image. So i disabled ExIf and used useragent detection to preset the orientation (might be a bit tacky but I'm so pressed for time at this point).
Also, the final image is zoomed in when displayed.
Don't know if this information will be useful but will just leave this here.

@thedustinsmith any news about this issue?
https://github.com/Foliotek/Croppie/issues/328


get list of paired devices in my app

Great work! can you please let me know is it possible to show the list of paired devices in my app screen? just want to show the list of paired devices those have been paired from my app. Thanks

You can remove the filter from centralManager.scanForPeripherals and that will show all advertising devices. You'll have to save all the results and connect them to your UI.


match up the values to the planned alignment

there are some items in the listing that do not follow the below value guidelines
0.25
0.30
0.50
0.60
0.75
these will need to be updated.

due to the crafting recipe values this just doesn't really fit anymore.


only enable pread/pwrite for linux. fixes #533 and fixes #532

The optimization meant for Linux breaks the FreeBSD and Mac OS X builds. This should fix it.

Coverage remained the same at 68.639% when pulling bd9ec0844c970f42c252068e061abb04c4064f3e on basvanbeek:master into 788c147ad744c8c86676ab4025bd2a3413f9bcf0 on mattn:master.

Thank you


[Iceberg] AWS Glue Job Runner

Add a one-click AWS Glue Job Runner that exposes a simplified singular CLI command for creating, configuring, and running an AWS Glue for Ray job against an Iceberg catalog with an integrated local or PyPi build of DeltaCAT.
As part of this story, we also want to ensure that we can read Iceberg tables into both Daft Dataframes and Ray Datasets within our Glue Job.

Daft integration depends on first resolving https://github.com/ray-project/deltacat/issues/170.


release Woodwork v0.15.0

The release instructions are here:

https://github.com/alteryx/woodwork/blob/main/release.md

Because the repo was transitioned to use pyprojet.toml and setup.cfg, for this release it would be good to do a test release on test.pypi.org before performing the real release. The test release for Featuretools after this transition revealed a few issues that needed to be addressed first.

Merged with https://github.com/alteryx/woodwork/pull/1359


How to get the output through the streaming server in edge TPU

Regarding the example file pose_camera.py, I would like to get some advice to get the video output using streaming server like the example here: https://coral.withgoogle.com/docs/dev-board/camera/#using-a-streaming-server. Not sure how to get this out.

You mean you want to stream the results of PoseNet out like the quoted streaming example ? That feature isn't supported in tis pose net example out of the box, so you'd need to port over the streaming-relevant parts of the code from the streaming server example.


Change errors to use thiserror

[ ] Change the error implementation to use thiserror crate

related: https://github.com/0xPolygonMiden/miden-node/issues/62

thiserror doesn't support no-std

That's going to change when the error_in_core feature stabilizes.
In the meantime, we should use this fork. I've introduced it in my assembler changes (hope to have those pushed tonight/tomorrow).

That's going to change when the error_in_core feature stabilizes.

Hopefully, this will happen soon - but also I think the timing of this is rather unpredictable.

In the meantime, we should use this fork. I've introduced it in my assembler changes (hope to have those pushed tonight/tomorrow).

Seems like this crate was published just yesterday? I'd be hesitant to use such a new dependency (we try to minimize the number of dependencies in general, and when required use more stable and well-known dependencies). How critical is this to the assembler changes?

I mean, we can fork thiserror ourselves and make the same changes - with code gen of the Error trait disabled for no_std, so this isn't a question of it being a new crate or something, we're talking about the same crate in practical terms. I would have actually done that myself, but someone helpfully did it already, hence why I'm recommending we use it in the meantime.
I'm conservative about dependencies, more so than most I think, typically preferring to write something myself unless there are well established options that meet my other picky criteria, so I don't generally recommend a crate unless I believe it meets the bar for inclusion by a fair margin.
In any case, I didn't think the question was whether we should start using thiserror or not, but when. There isn't a good reason to wait for stabilization of error_in_core, dtolnay is doing so because it is easier for them to maintain the crate, i.e. they don't want to publish a temporary workaround like the linked fork. We don't have the same constraints, so it's really a matter of whether we can benefit from it before that happens, and that seems like a clear yes to me.
That said, I'd suggest waiting to see what my changes look like, and evaluate in that context, since we may not have any other stuff in the works that needs it just yet and this will provide some useful comparison.

with code gen of the Error trait disabled for no_std, so this isn't a question of it being a new crate or something, we're talking about the same crate in practical terms.

Right - this is more of a general principal which I think is important specifically for crypto-related projects where supply-chain attacks are a very real risk. So, I try to keep the number of external dependencies to an absolute minimum and only use very well-known dependencies.

we can fork thiserror ourselves and make the same changes

We we do want to use this error, I would probably prefer this route. No need to do anything different for the PR you are working on, but we should probably follow it up with our own fork and then we can use it in all other repos as well.

Currently, we have our own forks of thiserror and miette dependencies which support no-std. Once relevant features in core get stabilized and these crates are updates to make use of them, we should move the dependencies to the canonical crates.

The 1.81 release looks like it will contain the stabilized error_in_core trait, and there is a draft PR in thiserror that implements the necessary changes there, but I'm not sure exactly how soon after 1.81 releases we can expect the thiserror release to drop, but probably pretty quickly afterwards, we can certainly update our fork to be the same changes so we're aligned with upstream.
For miette, we'll need to maintain a fork for awhile. I'm planning to spend some time reworking miden-diagnostics to basically take over the role of that dependency (by exporting a mostly-equivalent API, with the source management stuff integrated more natively into it, so we can move that out of miden-core). While miette is great for what it does, there are some aspects of it I don't like, and it isn't designed to be no-std compatible (I had to hack it in to our fork). The parts I do mostly like, are the rendering of diagnostics, the IntoDiagnostic, Diagnostic, and WrapErr traits, Report, and some of the conveniences like the diagnostic! and miette! macros - but I don't like any of the source management stuff it does, which is not well-suited to an environment where multiple sources are being worked on simultaneously (there is no way to tell the Report printer how to map a source span to a specific source file, it expects that you bind the relevant source file to the Report, but you can have diagnostics with spans in multiple files, and it is extremely awkward to handle this (I hacked together the RelatedLabel type to make this work, but it is not convenient to use).
Anyway, brain dumping this here for when we get to this, there isn't too much required to implement what I described above, so when I have some time to get to it, I'll do so.


error  erb [not found] when generating new component

Steps to reproduce
❯ rails g component HelloWorld                                                        Node 16.13.1 Ruby 3.0.3
      create  app/components/hello_world_component.rb
      invoke  test_unit
      create    test/components/hello_world_component_test.rb
       error  erb [not found]

also
❯ rails g component HelloWorld --template-engine erb                             took 4s Node 16.13.1 Ruby 3.0.3
      create  app/components/hello_world_component.rb
      invoke  test_unit
      create    test/components/hello_world_component_test.rb
       error  erb [not found]

BUT if i use the template engine as slim it works:
❯ rails g component HelloWorld --template-engine slim                            took 4s Node 16.13.1 Ruby 3.0.3
      create  app/components/hello_world_component.rb
      invoke  test_unit
      create    test/components/hello_world_component_test.rb
      invoke  slim
      create    app/components/hello_world_component.html.slim

Expected behavior
When generating a new component, I expect an erb template to be generated
Actual behavior

System configuration
7.0.1
Ruby version:
3.0.3
Gem version:
2.48

Did you resolve this?  I am seeing the same issue.

Same problem here.

@jasper502 @theonlyriddle Which version of ViewComponent are you using?
@dylandechant would you mind explaining how you solved your issue? Thanks!


Exception: Second auth step failed.

hi,
client.Authenticate().Wait();
seems not to work, i get this error:
Exception: Second auth step failed.

Hi @ThomasGugler,
I've found such problem a few weeks ago before I left for vacation. There is some change in Garmin Connect login process (probably new redirect/session issue). I need to solve this too cause some of my services stopped working :(, so I hope I'll fix is ASAP.
Regards,
Marek

hi
are there any news from your side?
i tried to debug but was not able to fix the bug :/


Update trove classifiers and python_requires to reflect supported Python versions

The future belongs to pyproject.toml. I guess it's still worth updating the existing code first.

While I agree, it might need a bit more discussion before doing it. One could be tempted to use Poetry, hatch or PDM when doing so... I leave it up to the maintainers to voice their preferences.

Example of things that need to be reworked if we change to pyproject.toml: the test suite calls setup.py directly:
https://github.com/namespace-ee/django-datadog-logger/blob/c90df5b5a6ab8223bc81145839e1e8517485a704/Makefile#L53-L54


Jsonrpc authentication via http headers

https://github.com/paritytech/jsonrpsee/issues/1370#issuecomment-2264694729
Follow-up and see it this works.

It works. Working on a PR.

It's possible, but requires bunch of work in various parts of the system, backward compatibility changes etc. so I'm going to drop it for now. I leave #5811 as a reference.


Instrument Factories in Tests

Currently in the Daml-Finance test suite, the tests create instruments directly thusly bypassing their related Factory. In order to make the tests closer to how the library is expected to be used, update the tests to use their related Factory instead.

This only pertains to end-to-end tests, unit tests can (and should) take shortcuts. To be revisited as part of separating unit from e2e tests.

Our current implementation to solve https://github.com/digital-asset/daml-finance/issues/753 requires the use of a factory in order to work (and be tested in the repo). I have changed it for the Callable Bond test, and the code did not get that much more complicated. It is also in a test util function, so the code is being reused for all callable bonds. @georg-da I would suggest changing this for the other dynamic instruments as well, what do you think?

This has now been implemented for the dynamic instruments.

This has now been implemented for all remaining instruments


Update task on person edit

closes https://github.com/AY2223S1-CS2103T-F12-2/tp/issues/179

Codecov Report
Base: 59.63% // Head: 59.55% // Decreases project coverage by -0.07% :warning:

Coverage data is based on head (ba712a6) compared to base (95e006c).
Patch coverage: 0.00% of modified lines in pull request are covered.

Additional details and impacted files
@@             Coverage Diff              @@
##             master     #185      +/-   ##
============================================
- Coverage     59.63%   59.55%   -0.08%
  Complexity      600      600
============================================
  Files           112      112
  Lines          2326     2329       +3
  Branches        283      284       +1
============================================
  Hits           1387     1387
- Misses          825      827       +2
- Partials        114      115       +1

Impacted Files
Coverage Δ

...java/seedu/address/logic/commands/EditCommand.java
86.84% <0.00%> (-3.57%)
:arrow_down:

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.


An hr element appears at the bottom of pages when using a non-default theme

The  doesn't appear in the documentation I generate locally.
This seems to occur on every theme I tried, and also on other project pages with non-default themes.
Examples:
http://readthedocs.org/docs/pysensors/en/latest/
http://readthedocs.org/docs/django-chartit/en/latest/
http://readthedocs.org/docs/little-books-of-r/en/latest/
http://readthedocs.org/docs/webmynd-forge/en/latest/

This is from here:
https://github.com/rtfd/readthedocs.org/blob/master/readthedocs/templates/sphinx/layout.html#L50
Don't remember exactly why we did this. I think it was to seperate the RTD
content from the users content. Though this is a hacky and not great
solution.
We can probably safely remove it.
2011/11/8 Bastien Lonard <
<EMAIL_ADDRESS>
The  doesn't appear in the documentation I generate locally.
This seems to occur on every theme I tried, and also on other project
pages with non-default themes.
Examples:
http://readthedocs.org/docs/pysensors/en/latest/
http://readthedocs.org/docs/django-chartit/en/latest/
http://readthedocs.org/docs/little-books-of-r/en/latest/
http://readthedocs.org/docs/webmynd-forge/en/latest/

Reply to this email directly or view it on GitHub:
https://github.com/rtfd/readthedocs.org/issues/137

--
Eric Holscher
Engineer at Urban Airship in Portland, Or
http://ericholscher.com


Fix replicate job loading non-persisted files

Fix an bug introduced in https://github.com/Alluxio/alluxio/pull/13146, causing setReplication command to fail when data has not been persisted.

Codecov Report

Merging #13362 (43a622b) into master (e18198d) will decrease coverage by 26.48%.
The diff coverage is 0.00%.

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


Modified README.md

Hey there

Hey there !!

Hey there !!

Hey there !!

Performance report:

Performance report:

Performance report:

Performance report:
![images](https://raw.githubusercontent.com/jumaffre/metrics-devops/metrics-devops/metrics-devops/image2019-07-23 10%3A18%3A57.508186.png
Have a look before merging :eyes:)

Performance report:

Have a look before merging :eyes:

Performance report:

Have a look before merging :bar_chart: :eyes: :thumbsup:

Performance report:

Have a look before merging :bar_chart: :eyes: :thumbsup:

Performance report:

Have a look before merging :bar_chart: :eyes: :thumbsup:

Performance report:

Have a look before merging :bar_chart: :eyes: :thumbsup:

Performance report:

Have a look before merging :bar_chart: :eyes: :thumbsup:

Performance report:

Have a look before merging :bar_chart: :eyes: :thumbsup:

Performance report:

Have a look before merging :bar_chart: :eyes: :thumbsup:


How handle Unix signals?

For example, we might want a server to gracefully shutdown when it receives a SIGTERM, or a command-line tool to stop processing input if it receives a SIGINT. Here’s how to handle signals in skynet ?

You can write a C service to register signals by posix C api  (sigaction, etc) . Mark signal in a global variable, and use a timer in the C service to check this global variable, and send a skynet message to other service to handle it.
No official way to handle signals in skynet now.
ps. logger service can handle SIGHUP now, see

https://github.com/cloudwu/skynet/blob/master/skynet-src/skynet_start.c#L248-L253
https://github.com/cloudwu/skynet/blob/master/skynet-src/skynet_start.c#L113-L126


Using Eyedropper on color in second monitor crashed

Godot version
3.2.3 stable
System information
Pop_OS 22.04, GLES3, X11, Gnome
Issue description
When in the editor theme settings using the eyedropper on a color in a second display crashes Godot, tested twice and both times had to be killed by system monitor.
Steps to reproduce

start a project (I did this on a brand new project but I don't think it matters)
go to the editor settings and then the theme category
change color (I tested with base and accent) and select eyedropper
move mouse to second monitor, at this point it has already crashed, but attempting to select a color proves it.

This kills the engine and attempting to alt-f4 brings up the "Exit the editor?" dialogue, which is also unresponsive
Minimal reproduction project
Unneeded as it can be done on a brand new project

Duplicate of #55003 ?

3.2.3 stable

Godot 3.2.x is not supported for bug fixes anymore, so please upgrade to 3.4.4 and check if the issue still occurs there.


problems w/ new project

There are a few problems creating a new project from scratch:

If there is no python 3.7, I get errors like this:

make check-types
[NoPythonVersion]: No Python interpreter matching python3.7 is found.
make: *** [Makefile:52: check-types] Error 1

the template should prompt for the range of python versions we want

After the project was created, I updated pyproject.toml like this:
requires-python = ">=3.8,<3.12"
keywords = []
dynamic = ["version"]
classifiers = [
    "Development Status :: 4 - Beta",
    "Intended Audience :: Developers",
    "Programming Language :: Python",
    "Programming Language :: Python :: 3",
    "Programming Language :: Python :: 3 :: Only",
    "Programming Language :: Python :: 3.8",
    "Programming Language :: Python :: 3.9",
    "Programming Language :: Python :: 3.10",
    "Programming Language :: Python :: 3.11",
    "Topic :: Documentation",
    "Topic :: Software Development",
    "Topic :: Utilities",
    "Typing :: Typed",
]

After this, I get errors like this:

make check
[NoPythonVersion]: No python is found meeting the requirement python >=3.8,<3.12
make: *** [Makefile:43: check] Error 1

Where is this version check coming from?

Looking at pdm-multirun, I wonder whether the Makefile should set PDM_MULTIRUN_VERSIONS

I tried it manually:
pdm multirun -i 3.11 duty check-types
Traceback (most recent call last):
  File "/home/nfr/.local/bin/duty", line 5, in <module>
    from duty.cli import main
ModuleNotFoundError: No module named 'duty'

This is surprising because I see in pyproject.toml the following:
[tool.pdm.dev-dependencies]
duty = ["duty>=0.10"]

Any suggestions on addressing these problems?

Hello, thanks for your interest in my template :slightly_smiling_face:

If there is no python 3.7, I get errors like this:

The documentation is not up-to-date, you can indeed set PDM_MULTIRUN_VERSIONS yourself to define the versions you want to use. You are also responsible for installing and making available the selected Python versions, through pyenv for example.

After this, I get errors like this:

That must come from PDM. It's usually not a good idea to set an upper bound limit to your required Python version, unless you absolutely know your code won't work on Python 3.12.

I tried it manually: ... No module named 'duty'

That's probably because dependency were not installed for Python 3.11.
Make sure to define the select available Python versions and to run make setup, for example:
PDM_MULTIRUN_VERSIONS="3.8 3.9 3.10 3.11" make setup

I'll add a documentation label :sli

Documentation updated.


feat: add apiserver_admission_webhook_request_total metric

What does this PR do?

This PR adds a new kubernetes metric: apiserver_admission_webhook_request_total
More details: https://kubernetes.io/docs/reference/instrumentation/metrics/
This metric was created in the kubernetes 1.23 version: https://github.com/kubernetes/kubernetes/pull/103162
Fix: https://github.com/DataDog/integrations-core/issues/17689
Motivation

This metric is missing in the Datadog Kubernetes integration.
Additional Notes

Review checklist (to be filled by reviewers)

[x] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[x] Changelog entries must be created for modifications to shipped code
[ ] Add the qa/skip-qa label if the PR doesn't need to be tested during QA.
[ ] If you need to backport this PR to another branch, you can add the backport/<branch-name> label to the PR and it will automatically open a backport PR once this one is merged

@FlorentClarret I don't understand what is wrong with the tests. Can you help me?

Would anyone be able to help me with this PR?
@Kyle-Neale, @jmeunier28, @dkirov-dd or someone else?


VMIX Device

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
This PR adds support for controlling the vMix software.

Nice!

merged into #158


Documentation page with side bar (Work in progress)

Proposal to modify the existing layout to look something like below.

More changes to make it look like

Closing this as after the testing for text based browsers and accessibility the current site design is much easier to navigate and read.

Closing this as after the testing for text based browsers and accessibility the current site design is much easier to navigate and read.