Can't install pip update

Issue Type: Bug
PS D:\OneDrive\Programs> python -m pip install --upgrade pip
Collecting pip
Using cached https://files.pythonhosted.org/packages/54/0c/d01aa759fdc501a58f431eb594a17495f15b88da142ce14b5845662c13f3/pip-20.0.2-py2.py3-none-any.whl
Installing collected packages: pip
Found existing installation: pip 19.2.3
Uninstalling pip-19.2.3:
ERROR: Could not install packages due to an EnvironmentError: [WinError 5] Access is denied: 'c:\program files\python38\lib\site-packages\pip-19.2.3.dist-info\entry_points.txt'
Consider using the --user option or check the permissions.
WARNING: You are using pip version 19.2.3, however version 20.0.2 is available.
You should consider upgrading via the 'python -m pip install --upgrade pip' command.
Extension version: 2020.3.71659
VS Code version: Code 1.44.1 (a9f8623ec050e5f0b44cc8ce8204a1455884749f, 2020-04-11T01:48:12.622Z)
OS version: Windows_NT x64 10.0.18363

This does not look like an extension issue. you will run into the same problem if you run this in a terminal outside of VS Code. As the warning states if you add --user it should work.
PS: Please follow our code of conduct when posting issues.


Intervals with duration 0

I just ran into some weird behavior in Praat when editing an interval tier and think I traced it back to an interval with duration 0 (at the place where no boundary is displayed in the screenshot); would it make sense to disallow Intervals with duration 0? Could be done by modifying the check at https://github.com/kylebgorman/textgrid/blob/master/textgrid/textgrid.py#L173.

It's not clear to me from that picture what the problem is. Is it that you
expect a vertical blue line at the right side of the yellow interval?
If this is just a Praat rendering bug, but Praat is okay with
zero-duration intervals, I'd be inclined to leave it as is. That is,
there's nothing illformed about the TextGrid, it's just that Praat (some
versions, on some platforms) misrenders it.
If however this is a reflection of the fact that Praat (sorta) disallows
zero-duration intervals, then I'd be glad to accept a patch at that point.
Can we determine which it is?
On Thu, Dec 29, 2016 at 8:02 AM, Christian Brodbeck <
<EMAIL_ADDRESS>wrote:

I just ran into some weird behavior in Praat when editing an interval tier
and think I traced it back to an interval with duration 0 (at the place
where no boundary is displayed in the screenshot); would it make sense to
disallow Intervals with duration 0? Could be done by modifying the check at
https://github.com/kylebgorman/textgrid/blob/master/textgrid/textgrid.py#
L173.
[image: screen shot 2016-12-29 at 2 00 10 pm]
https://cloud.githubusercontent.com/assets/145771/21544439/25d0ba1a-cdcf-11e6-9230-45fa98d9c34f.png
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/kylebgorman/textgrid/issues/15, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJuOY3LezuenG9VcZ34OA63KoZ9ggWDks5rM69ZgaJpZM4LXkWu
.

Is it that you expect a vertical blue line at the right side of the yellow interval?

Yes, also:

The invisible boundary can't be moved.
if I add a new boundary in the area after the invisible boundary and save the textgrid, the resulting TextGrid file can not be opened by Praat anymore, giving the error below.

These suggest to me that this is something that is not intended to happen...

Okay, I find that convincing, let's rule it out. Are you up to creating a
PR that prevents creation of such a tier (presumably by raising an
exception)?
On Thu, Dec 29, 2016 at 5:13 PM, Christian Brodbeck <
<EMAIL_ADDRESS>wrote:

Is it that you expect a vertical blue line at the right side of the yellow
interval?
Yes, also:

The invisible boundary can't be moved.
if I add a new boundary in the area after the invisible boundary and
save the textgrid, the resulting TextGrid file can not be opened by Praat
anymore, giving the error below.

These suggest to me that this is something that is not intended to
happen...
[image: screen shot 2016-12-29 at 11 11 12 pm]
https://cloud.githubusercontent.com/assets/145771/21555845/1c835d12-ce1c-11e6-922e-dec0de5c1d37.png
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/kylebgorman/textgrid/issues/15#issuecomment-269701784,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJuOVSnf9Cr7EeYm6TQUKVsTjEM7VMbks5rNDCagaJpZM4LXkWu
.

Yes I will create a PR, thanks!


Optout modernise tests

test by explicitly following a trail of inputs and the consequent routing rather than always setting the user start state

@imsickofmaps @gsvr please review

:+1:


unpublish nimcalcal, calendar

my packages are outdated and unmaintained.

I would prefer if you state in your repo that your package is unmantained. Let others use them if they wish.

Well once published, others may depend on it. Nimble needs to fork all packages or we need some other mechanism.

The packages are no longer usable and I won't fix them. So let them disappear from the published package list.

It's better to give people something to fix than to make the package disappear completely.

One advantage of unpublishing: the names of the retired packages can be used to publish better alternatives.
Your concerns about disappearing packages are valid.
But for my packages:

i now think it was a mistake to publish them
it really doesn't matter if they are no longer visible in nimbles package list

So please merge my PR.


WIP: Add initial datamodel for Traffic Sign Plan.

Add Traffic Control application with basic Admin-model and API for Traffic Sign Plan.

Codecov Report

Merging #1 into master will increase coverage by 7.82%.
The diff coverage is 78.3%.

@@            Coverage Diff             @@
##           master       #1      +/-   ##
==========================================
+ Coverage      65%   72.82%   +7.82%
==========================================
  Files           7       14       +7
  Lines          80      184     +104
  Branches        7       10       +3
==========================================
+ Hits           52      134      +82
- Misses         24       46      +22
  Partials        4        4

Impacted Files
Coverage Δ

traffic_control/apps.py
0% <0%> (ø)

city-infrastructure-platform/urls.py
0% <0%> (ø)
:arrow_up:

users/apps.py
0% <0%> (ø)

traffic_control/api.py
0% <0%> (ø)

users/models.py
100% <100%> (ø)

traffic_control/admin.py
100% <100%> (ø)

city-infrastructure-platform/settings.py
84.21% <100%> (+0.28%)
:arrow_up:

users/admin.py
100% <100%> (ø)

traffic_control/models.py
98.21% <98.21%> (ø)

... and 6 more

Continue to review full report at Codecov.

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

Looks good to me :+1: :shipit:


build: update to Nx 15.0.0 and misc dependencies

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

[ ] The commit message follows our guidelines: https://github.com/analogjs/analog/blob/main/CONTRIBUTING.md#-commit-message-guidelines
[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe: update package version

Which package are you modifying?

[ ] vite-angular-plugin
[ ] astro-angular
[ ] create-analog

What is the current behavior?

Issue Number: N/A
What is the new behavior?
1.update package version
2.run command "nx migrate latest # same as nx migrate @nrwl/workspace@latest"
3.run command "yarn nx migrate --run-migrations"
only @nrwl/angular package use v14.6.4 not latest version
because v14.7.18 v14.8.4 v15.0.0 not work to run build now (without code change)

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

@himyjan I'd rather not upgrade yet than have a mix of some dependencies that are still on an older version.


build error: toolchain not available

When trying to build v0.12.2, I get the following error:
go: downloading go1.22 (linux/arm)
go: download go1.22 for linux/arm: toolchain not available

After some googling, I found a solution:
diff --git a/go.mod b/go.mod
index 89b0302..1fff6b3 100644
--- a/go.mod
+++ b/go.mod
@@ -1,6 +1,6 @@
 module github.com/beeper/bridge-manager

-go 1.22
+go 1.22.0

 require (
        github.com/AlecAivazis/survey/v2 v2.3.7

Note: I know next to nothing about go, so I don't know if this is a proper solution for all platforms, an error on go side, change of versioning, or just a weird hack.


Runtime.getAssets()['asset'].path gives filename instead of full path.

Runtime.getAssets()['asset'].path should give the full path of the asset.  Within twilio functions it would be something like this:
/var/task/files/xxxxxxxx
In twilio-run it would just return 'asset'.

Thanks! I'll try to fix this issue this week. I'm happy to merge another PR from you though :) Thank you for the contribution!

This has been fixed and will be pushed with the next version


Update MSRV to 1.63

Hmm, the msrv job is failing, but I don't quite understand why.

Woo! With enough elbow grease, got it working

Ok, should be good now.


Setting to include passed tests in report | Use testsuite filename if testcase misses it

add new setting allowing to include passed tests as notice

FIX https://github.com/mikepenz/action-junit-report/issues/42

use testsuite file name in case testcase does not specify one

FIX https://github.com/mikepenz/action-junit-report/issues/401

I think there's one more piece that's needed. In the logs, I can see the XML has been processed, but then I don't see any annotations:
 /__w/proj/proj/test/config.js:1 | TESTING mocha-junit-reporter with Github Actions.

I believe the issue is that the absolute path needs to be stripped out so only the relative-to-repo-root path remains.
I expect it's normal for the "working directory" to be the repo root. So stripping the absolute path to current working directory should do the trick.

@markstos added the related change, if you could please re-run it :)

Thanks for the update. I know see the file path has been truncated from an absolute path to /test/config.js, but I still don't see the annotation. Should it be test/config.js instead with the leading "/" also stripped?

@markstos thank you, added the stripping of the last / too

It worked! The one area for improvement is the formatting of the annotation:

Notice how it repeats the absolute path name in red. I'm not sure if that can be changed, but that path doesn't need to be there at all. If it does need to stay, perhaps it can also be relative and there should be a space after the file name and before the test caes name.

Here's a commit that removes the file name from the the title. But from looking at the code and the test suite, it was quite intentionally there, so I presume it makes sense with other kind of Junit output:
https://github.com/RideAmigosCorp/action-junit-report/commit/16afe4fd45dece0c3cd116437b3faacb64b99a1a
That formatting question is a separate issue. The issue here with processing a "file" attribute appears correct and complete and the formatting issue can be addressed separately. An option could be used to include the file name in the title or not.

@markstos thank you for the feedback.
I am having an idea for an option which would make that much more flexible. Will see tomorrow if I'll find time to implement it prior to doing the next release.


Limit max number of session that can be multiplex via same ssh sessions.

Limit max number of session that can be multiplex via same ssh session.
SSH server has default max limit of 10 which normally shouldn't be a problem,
but in the use case of net-scp it can reach limit very fast and thus resulting
in unexpected error this is misleading with vague SCP error.
In our use case where test-kitchen is running against multiple components against
few set of computes with same user e.g. oneops using ssh key.  This can cause
the connection to bump against the default limit really fast.  Ideal fix would
probably involve relaxing this limit to allow net-scp multiplex more connections
over the same session.
This temporary fix will slow down net-scp as it's now only allow to multiplex only
single connection per session to avoid running into the max limit.

Closing this as this doesn't solve the issue completely.  Switching to different method with additional PR.


Maximize brightness toggle

Add a feature to maximize brightness to aid drawing.
Add a button to the lower-left corner of the canvas that would be used to temporarily maximize brightness. The button should have 2 states:

Inactive: use default screen brightness (tap to activate)
Active: use max screen brightness (tap to deactivate)

I'm going to give this feature a shot

Awesome!


Add service manual team to users

We want to be able to SSH into CI.

Why do you need ssh access to these machines rather than via the Jenkins UI?

We wanted to be able to boot a rails console to do some debugging for a build failure that we couldn't replicate in development. The build output wasn't enough at the time..

Hi @djsd123. Does ^^ make sense?


Fix jsdoc comment for UNITS

Currently, the UNITS constant is not exported in the TypeScript declaration file since it is not annotated with the appropriate jsdoc comment. This Pull Request adds the jsdoc comment to fix the problem.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Pull Request Test Coverage Report for Build 191

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 184:
0.0%

Covered Lines:
363

Relevant Lines:
363

💛  - Coveralls


Move all the IQueryable extension methods into the root namespace

I think it makes Marten just a tad easier to use if all the user facing extension methods are in the root namespace.

I'll clean that later on today.

@nieve You might wanna put that off for now. I know there's a biggish PR coming from @CoreyKaylor relatively soon that might cause some ugly merge conflicts with that.

@jeremydmiller thanks for the heads up. Will wait with it then.

I'm getting this now. Doing some housecleaning this morning.


add staticHeight option

This is useful with the float option when one wants the grid to not automatically size down when moving items. Would have liked to have a similar option for width, but from the looks of it, width already never changes.

Coverage decreased (-0.01%) to 70.514% when pulling 78f3cab28fe968bf768d561bae24b7ff9c03ce82 on silverwind:fixed-size-grid into fa4f2d0d076120f380f475eb71cbc585c4e4197b on troolee:develop.

I fear I have to close it, it's not really complete. I have a branch that fixes some of the issues, but it's not really complete (one issue is that the collision check can place items outside the fixed height). Maybe I'll get this in a more complete state later.


Micro Switch Implementation

sunfounder example: https://docs.sunfounder.com/projects/raphael-kit/en/latest/python/2.1.2_micro_switch_python.html

[x] Implement Helper
[x] Implement Controller
[x] Add to application.yml
[x] Write Javadoc comments

Closed by PR #234. Need to create an issue for micro switch documentation.


Unable to replicate results for Mistral-7B-Instruct-0.3

Hi
Thanks for the awesome work!
I am trying to evaluate Mistral-7B-Instruct-v0.3 https://huggingface.co/mistralai/Mistral-7B-Instruct-v0.3 using the same prompt as GPT-4 with temp=0.7, max tokens=500. However, I see that the response error rate is quite high (>90%) as the model does NOT predict in JSON format or repeats the input prompt. I also experimented with lower temperature and adding penalty for repetition but that didn't help. Could you clarify if you used the same prompt for evaluating open-source models like Mistral-7B-Instruct (Table 5)?

Hi
Thanks for the awesome work! I am trying to evaluate Mistral-7B-Instruct-v0.3 https://huggingface.co/mistralai/Mistral-7B-Instruct-v0.3 using the same prompt as GPT-4 with temp=0.7, max tokens=500. However, I see that the response error rate is quite high (>90%) as the model does NOT predict in JSON format or repeats the input prompt. I also experimented with lower temperature and adding penalty for repetition but that didn't help. Could you clarify if you used the same prompt for evaluating open-source models like Mistral-7B-Instruct (Table 5)?

Hi,
Thank you for your feedback and your efforts in replicating our experiments.
In our experiments, we used Together AI’s services with a max token limit of 512 and a temperature setting of 0.7. The prompts we used are consistent with those provided on our GitHub repository. We replicated the experiments on the Mind2Web-live test set yesterday and found that the results were closely aligned with those reported in our paper.
Could you please check if there are any discrepancies in other parameters or settings? What data are you using for eval? It’s also possible that the model's performance might vary based on the specific setup or the instance accessed during your tests.
Looking forward to hearing from you to resolve this issue!

Thanks for the info! I am trying to do inference by loading a model locally on GPU. I will recheck my generation parameters to make sure they match with together.ai config. I am using Mind2Web-live test set for evaluation using a linux instance in US.

It is resolved now. Turns out I was using greedy decoding instead of sampling.


Implement getAccountData

Implement Iota.get_account_data which loads all addresses, transfers and account balance information.
See https://github.com/iotaledger/iota.lib.js#getaccountdata for more information.

Scheduled for release: v1.1.1


BridgingState Service

I recently noticed that each accessory I expose through my homebridge platform plugins contains a BridgingState service, in addition to the AccessoryInformation service and service(s) I created myself.  It's kind of hidden: neither the iOS built-in Home app nor Eve show this service, but Matthias' Home app does (when viewing the accessory under Home), as does HMCatalog.  This service seems to be added by HAP-NodeJS in addBridgeAccessory().
I have some questions about this:

Has this service been added recently?  Or did I just not notice it earlier?
Why do I need this service?  The (also bridged) accessories exposed by the Philips Hue bridge don't contain this service.
Is there a way to prevent this service from being created, or alternatively, to remove this service?  Reason I'm asking: my HomeKit configuration has become too large for iCloud syncing and I'm looking for ways to save space (obviously without losing functionality).

Thanks,
Erik.

This service was discovered in iOS 9.3 which allows bridge to provide extra information about a bridged accessory to HomeKit. HAP-NodeJS has been adding that service to bridged accessories for a while already.
The service allows bridge to report category, reachability of a bridged accessory. My guess is that Apple hasn't officially publish this service to manufacturer so they can't use it.
No. Are you sure you are having sync problem because the home data blob is too large? 1MB is a lot for home data...

Thanks @KhaosT

I wouldn't know how to measure it, so I cannot be sure, but I do have circumstantial evidence: My "production" Home has 113 accesories, 14 rooms, 9 groups, 14 scenes, 8 rules.  I use a "test" Home on the same iCloud account when developing/testing my plugins with a difference instance of homebridge.  When that instance provides more than a dozen accessories, iCloud sync stalls: changes to the HomeKit configuration are only visible on the device where you made them.  When I change the test homekit configuration, reducing the number of accessories, HomeKit sync resumes.  I regularly delete and re-create the test Home, hoping that cleans up any mess I make during testing.

Breakdown of the accesories:

Philips Hue gen2 bridge bridging 39 lights;
Homebridge with homebridge-hue plugin, bridging 75 accessories (lights, switches, sensors);
Homebridge with homebridge-zp pluging, bridging 4 sonos zones;
2x Elgato Eve Energy

I could use a different iCloud account for testing, but I only have one AppleTV and one iPad, so I wouldn't be able to test rules.
I pretty much installed smart lights and Hue motion sensors throughout my home, so I don't expect the Hue environment to grow.  However, after winning the lottery ;-), I want to install a smart thermostat, with smart radiotor valves (honeywell or tado or something like that), a couple of door sensors, and maybe a smart lock. Enough to hit the limit, I'm afraid.

Sorry to bumb this, @KhaosT, but I think we're really running into the CKRecord limit.  The BridgingState service isn't mentioned in the HAP spec, nor are any of its characteristics...

Yeah, I believe this service is removed from iOS 10.2 and HomeKit no longer use any information provided by this service. I think I will make changes to hap-nodejs to no longer automatically add this service to bridged accessories.

But I may not be able to push changes until this weekend... Internet connection at Yellowstone is terrible 😝

No problem, and many thanks.  I hope you enjoy Yellowstone despite the lousy internet connection.

Should be addressed with v0.4.26

Thanks, Tian!


Massive code cleanup

I used IntelliJ IDEA's code analysis feature to help find warnings and bugs, and manually went through fixing them. The only warnings I let IDEA fix automatically were unused imports and most redundant casts.
ItemStacks have been converted to use ItemStack.EMPTY instead of null, to conform to new standards.
Annotations have been added to a LOT of the code to help devs determine when null can and can't be used, however they're nowhere near all-encompassing.
The inheritance of the BlockAdvancedBipropellantRocketMotor class was rearranged to prevent a potential mis-classification of them as monopropellant motors.
Vague fields and variables have been renamed where I found them, such as i -> itemStack or obj -> spaceObject. This excludes math variables that seemed intentionally named, and standardized names like loop control variables.
Lang files have been cleaned up to the best of my ability, but the non-en_US languages still have a lot of missing translation keys. Probably best for someone who speaks those languages to add the translations, rather than me with Google Translate.
There were some recipes that had invalid json, so I fixed them. This resulted in a few of the recipes changing slightly.
This commit should fix a lot of NPEs, though I didn't get them all.
Next Steps:
I highly recommend one of the original devs merge this and also run the source through their own IDE's code analysis, since there are still a lot of warnings I couldn't or didn't fix, and a large amount of them could be or turn into bugs.
The ItemStack changes affected some API methods. Mods developed against Advanced Rocketry should use builds containing this commit in the future, to prevent them from sending null ItemStacks. I did still split any changes to method names and prototypes into a separate branch that can be merged or ignored.
This commit requires a sister-commit for libVulpes, since the ItemStack refactoring affected methods there too.

So I'm going to close this and ask you to run it against my NTR branch and not against the main one at this moment, as that has a significant amount of changes.

Leaving my comments to the code here so I can easily copy them to the next PR.


Native modules were not rebuilt during package when webpack template is used

[x] I have read the contribution documentation for this project.
[x] I agree to follow the code of conduct that this project follows, as appropriate.
[x] I have searched the issue tracker for an issue that matches the one I want to file, without success.

Please describe your issue:
The issue is that this loader @marshallofsound/webpack-asset-relocator-loader relocates .node files before they get rebuilt.
npx create-electron-app my-new-app --template=webpack
cd my-new-app
npm i nan-hello-world

edit main.js by adding the following:
const helloworld = require('nan-hello-world');
console.log(helloworld.say())

Run npm run package without npm start
npm run package

When trying to open the packaged app, electron will warn that the native module was compiled against different version using NODE_MODULE_VERSION 64 instead of the required 73.
However, if you run the following
npm un nan-hello-world && npm i nan-hello-world
npm start
# close the app then run
npm run package

The app will run fine because the npm start has already rebuilt the module. @marshallofsound/webpack-asset-relocator-loader is relocating the rebuilt version of the .node files.
To get around this issue with CI tools, I need to manually run
npx electron-rebuild

before running package/make so that the correct .node files are being packed.

I"m seeing the same thing (i think).  I have two native modules, but windows terminal output on appveyor shows this.
019-08-04T10:44:25.119Z electron-rebuild rebuilding with args: C:\T\electron-packager\win32-x64\app-win32-x64\resources\app 6.0.0 x64 [] false https://electronjs.org/headers [ 'prod', 'optional' ] false 2019-08-04T10:44:25.119Z electron-rebuild identified prod deps: Set {}


Can someone help write me a config?

I need the config to do this
I tried writing one myself, but failed miserably after 12 attempts.

We can't do anything without API documentation.

we'll, that practically is the api, it returns the image as url, in a json object

That's the response, not the request. We can't do anything without knowing how the request is done.

No, that is the request, that is exactly what you send to the server

with file being the file

the request is the image, the response is just url

Is the backend behind that site Pxl? From a quick look around it seems so.

Maybe 😉

that's not helping..

(that means yes)

{
    "name": "squaddy",
    "target": "https://i.squaddy.xyz/api/upload",
    "format": "multipart-form-data",
    "body": [
        {
            "_Content-Type" :"/%contenttype/",
            "filename": "/image.%format/",
            "name": "file",
            "body": "/%imagedata"
        }
    ],
    "return": ".url"
}

Should be it.

thanks

are you sure about that? There's no upload token or user, and file isn't being sent either

Right. Add ?user=USER&upload-token=TOKEN to the end of the target url

oh, I probably should've mentioned, for some reason, those aren't headers, they're in the body

Well, not according to the sharex autogen

https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers
https://en.wikipedia.org/wiki/URL#Syntax
ShareX' arguments are actually just query string components.

You seem new to this Sunburnt. Although your problem seems to be resolved for the most part, I still feel like you can learn about common etiquette.
This is the Github Issues section. There's one for each repo. People with specific rights within the repo may moderate this part. Usually, these are developers. This section is mainly to provide support from the devs. When the ask you a question, you answer it. You don't put "Maybe ;)". Another thing is you're going to have to provide us with more. Error logs if you have an error, your backend receiving code, etc. Nobody can help you if you're sending stuff that won't help. You send a picture of the response which gave us absolutely nothing. When asked about your backend, you didn't give an answer. The guy giving support just made a lucky guess about your situation.
Bottom-line, you would be wise to help us help you by providing more information, and acting better than that.

I think you'll find I'm not new to this. The whole thing about the emoji? This is a Screenshotting program, not the US Nuclear Launch Codes. And I didn't send the response, I sent the request. That was exactly what you had to send to the server.

What kind of person do you take me for?  Why would I send the response. Common sense.


Optimize outputs accumulating for SegmentTermsEnum and IntersectTermsEnum

Description
Previous talk is too long to track so i opened a new PR to make a summery here. More details are available in https://github.com/apache/lucene/pull/12661.
After merging of https://github.com/apache/lucene/pull/12631, we found a regression for term-dictionary-related tasks like PKLookup, Fuzzy ... After some digging I suspect that the regression is caused by  more Outputs#add and Outputs#read on reading side, as the 'MSB VLong output format' making FST sharing more output prefix. The difference of calling times of Outputs#add and Outputs#read is shown below:
| LSB VLong | MSB VLong | diff
-- | -- | -- | --
Outputs#read times | 116097 | 149803 | 29.03%
Outputs#add times | 144 | 111568 | 77377.78%
Solution
This patch tries to do two optimizations to get back the speed:

Instead of combining all outputs into single one, this patch collect all BytesRefs into an array and build a DataInput view over it, reducing the cost of objects construction and memory copy.
Instead of copying bytes into floor data, this patch directly uses the last output as floor data. Floor data is guaranteed continuous in single arc because we can not have two same fp encoded before floor data.

Benchmark

Both run 30 JVM round and 50 tasks per JVM:

Comparing to after merging of https://github.com/apache/lucene/pull/12631
BaseLine ( After merging of https://github.com/apache/lucene/pull/12631 )

$ git log
Write MSB VLong for better outputs sharing in block tree index (#12631)
DeletedTerms#clear should reset ByteBlockPool (#12630)

Candidate

$ git log
Optimize output accumulating
Write MSB VLong for better outputs sharing in block tree index
DeletedTerms#clear should reset ByteBlockPool

                            TaskQPS baseline      StdDevQPS my_modified_version      StdDev                Pct diff p-value
                   OrHighNotHigh      166.79      (4.5%)      165.12      (4.3%)   -1.0% (  -9% -    8%) 0.376
                    OrHighNotLow      258.47      (4.3%)      256.46      (3.3%)   -0.8% (  -7% -    7%) 0.430
            HighIntervalsOrdered        0.38      (3.3%)        0.38      (3.1%)   -0.8% (  -6% -    5%) 0.359
                 LowSloppyPhrase        1.64      (3.4%)        1.63      (4.9%)   -0.7% (  -8% -    7%) 0.544
                   OrNotHighHigh      150.83      (5.1%)      149.86      (4.4%)   -0.6% (  -9% -    9%) 0.597
                HighSloppyPhrase        3.67      (3.3%)        3.64      (3.6%)   -0.6% (  -7% -    6%) 0.470
                         Prefix3       67.16      (4.3%)       66.78      (2.8%)   -0.6% (  -7% -    6%) 0.543
                    OrNotHighMed      135.65      (4.4%)      134.95      (3.7%)   -0.5% (  -8% -    7%) 0.620
                    OrNotHighLow      257.14      (2.0%)      255.85      (1.7%)   -0.5% (  -4% -    3%) 0.291
                     AndHighHigh       19.33      (2.8%)       19.25      (2.2%)   -0.4% (  -5% -    4%) 0.517
                    OrHighNotMed      128.51      (5.3%)      128.06      (4.2%)   -0.3% (  -9% -    9%) 0.778
                 MedSloppyPhrase        9.56      (3.6%)        9.54      (3.8%)   -0.3% (  -7% -    7%) 0.788
                      OrHighHigh       13.23      (3.3%)       13.20      (3.2%)   -0.2% (  -6% -    6%) 0.801
                       OrHighLow      199.40      (1.9%)      199.18      (1.7%)   -0.1% (  -3% -    3%) 0.812
                        Wildcard       69.22      (2.7%)       69.19      (1.9%)   -0.0% (  -4% -    4%) 0.952
                      AndHighMed       42.14      (3.7%)       42.14      (2.9%)    0.0% (  -6% -    6%) 0.993
                    HighSpanNear        7.00      (3.1%)        7.00      (3.1%)    0.1% (  -5% -    6%) 0.945
                          Fuzzy1       44.05      (1.8%)       44.08      (1.7%)    0.1% (  -3% -    3%) 0.872
                       OrHighMed       38.54      (2.6%)       38.59      (3.2%)    0.1% (  -5% -    6%) 0.871
                         Respell       28.40      (2.2%)       28.45      (2.2%)    0.2% (  -4% -    4%) 0.790
                     LowSpanNear        4.23      (1.7%)        4.24      (1.5%)    0.2% (  -2% -    3%) 0.580
             MedIntervalsOrdered        3.47      (6.6%)        3.49      (7.3%)    0.3% ( -12% -   15%) 0.856
             LowIntervalsOrdered        2.76      (4.3%)        2.77      (5.0%)    0.4% (  -8% -   10%) 0.761
                          Fuzzy2       35.28      (1.6%)       35.42      (1.6%)    0.4% (  -2% -    3%) 0.325
                      HighPhrase       38.91      (2.6%)       39.07      (2.5%)    0.4% (  -4% -    5%) 0.532
                         MedTerm      248.39      (4.2%)      249.48      (4.2%)    0.4% (  -7% -    9%) 0.685
                       LowPhrase       26.44      (2.0%)       26.57      (2.3%)    0.5% (  -3% -    4%) 0.385
                       MedPhrase        9.51      (2.3%)        9.57      (2.6%)    0.6% (  -4% -    5%) 0.365
                      AndHighLow      338.26      (3.0%)      340.61      (2.6%)    0.7% (  -4% -    6%) 0.339
                         LowTerm      242.60      (4.5%)      244.38      (4.8%)    0.7% (  -8% -   10%) 0.545
                     MedSpanNear        1.11      (1.4%)        1.12      (1.5%)    0.8% (  -2% -    3%) 0.042
                        HighTerm      230.63      (3.8%)      233.01      (4.6%)    1.0% (  -7% -    9%) 0.339
                        PKLookup      100.76      (2.9%)      105.17      (3.2%)    4.4% (  -1% -   10%) 0.000

Comparing to before merging of https://github.com/apache/lucene/pull/12631
BaseLine ( Before merging of https://github.com/apache/lucene/pull/12631 )

$ git log
DeletedTerms#clear should reset ByteBlockPool

Candidate

$ git log
Optimize output accumulating
Write MSB VLong for better outputs sharing in block tree index
DeletedTerms#clear should reset ByteBlockPool

(Not sure why seeing tiny speed up for Orxxx tasks. I suspect it is a noise)
                            TaskQPS baseline      StdDevQPS my_modified_version      StdDev                Pct diff p-value
             MedIntervalsOrdered        3.50      (7.9%)        3.43      (7.4%)   -2.2% ( -16% -   14%) 0.269
                        Wildcard       70.27      (2.9%)       69.22      (2.2%)   -1.5% (  -6% -    3%) 0.023
            HighIntervalsOrdered        0.38      (4.0%)        0.37      (4.0%)   -1.3% (  -8% -    6%) 0.194
             LowIntervalsOrdered        2.78      (5.3%)        2.75      (5.2%)   -1.1% ( -10% -    9%) 0.417
                         Prefix3       66.95      (4.3%)       66.25      (3.1%)   -1.0% (  -8% -    6%) 0.282
                         LowTerm      246.48      (8.3%)      244.15      (6.8%)   -0.9% ( -14% -   15%) 0.631
                       MedPhrase        9.57      (3.6%)        9.50      (3.1%)   -0.8% (  -7% -    6%) 0.366
                HighSloppyPhrase        3.63      (3.5%)        3.62      (3.8%)   -0.3% (  -7% -    7%) 0.761
                      HighPhrase       39.07      (3.5%)       38.96      (3.3%)   -0.3% (  -6% -    6%) 0.749
                        PKLookup      105.27      (2.8%)      105.13      (3.0%)   -0.1% (  -5% -    5%) 0.859
                 MedSloppyPhrase        9.49      (3.2%)        9.48      (3.9%)   -0.1% (  -6% -    7%) 0.920
                         Respell       28.45      (2.6%)       28.46      (2.2%)    0.0% (  -4% -    5%) 0.957
                 LowSloppyPhrase        1.63      (5.0%)        1.63      (5.6%)    0.1% (  -9% -   11%) 0.929
                       LowPhrase       26.31      (3.3%)       26.36      (2.1%)    0.2% (  -5% -    5%) 0.782
                          Fuzzy1       43.71      (1.3%)       43.82      (1.7%)    0.3% (  -2% -    3%) 0.509
                   OrHighNotHigh      164.97      (3.7%)      165.40      (4.4%)    0.3% (  -7% -    8%) 0.806
                     AndHighHigh       19.17      (2.1%)       19.23      (2.3%)    0.3% (  -3% -    4%) 0.569
                     MedSpanNear        1.11      (2.0%)        1.12      (2.0%)    0.6% (  -3% -    4%) 0.266
                      AndHighLow      338.06      (2.1%)      340.30      (1.9%)    0.7% (  -3% -    4%) 0.196
                     LowSpanNear        4.20      (2.4%)        4.23      (2.1%)    0.7% (  -3% -    5%) 0.194
                      OrHighHigh       13.15      (4.0%)       13.26      (4.5%)    0.8% (  -7% -    9%) 0.454
                   OrNotHighHigh      148.59      (3.9%)      149.94      (5.1%)    0.9% (  -7% -   10%) 0.442
                        HighTerm      229.24      (3.7%)      231.60      (4.2%)    1.0% (  -6% -    9%) 0.314
                    HighSpanNear        6.94      (3.3%)        7.01      (3.6%)    1.1% (  -5% -    8%) 0.224
                    OrHighNotMed      126.33      (4.3%)      127.74      (4.9%)    1.1% (  -7% -   10%) 0.343
                    OrHighNotLow      254.19      (3.1%)      257.19      (3.9%)    1.2% (  -5% -    8%) 0.200
                      AndHighMed       41.35      (5.0%)       42.00      (3.2%)    1.6% (  -6% -   10%) 0.148
                          Fuzzy2       34.61      (1.8%)       35.34      (2.1%)    2.1% (  -1% -    6%) 0.000
                       OrHighMed       37.84      (5.8%)       38.65      (4.2%)    2.1% (  -7% -   12%) 0.107
                    OrNotHighLow      248.52      (2.8%)      254.75      (2.5%)    2.5% (  -2% -    7%) 0.000
                       OrHighLow      193.81      (2.3%)      200.07      (2.5%)    3.2% (  -1% -    8%) 0.000
                    OrNotHighMed      130.29      (3.6%)      134.66      (4.7%)    3.4% (  -4% -   12%) 0.002
                         MedTerm      241.15      (3.8%)      249.46      (4.5%)    3.4% (  -4% -   12%) 0.001

I'll try to review the latest PR soon -- thanks @gf2121.

Thanks for review @mikemccand !

but some head scratching -- hard to remember how these two crazy iterators work.

Agree that this is head scratching... I make a chart to try to explain this better.

Thanks for review and great suggestions @mikemccand !

you want to merge and backport to 9.x?

Yes. I'll merge and backport this this.

Hi @mikemccand @jpountz !
The newest nightly benchmark shows we get back some speed for PKLookUp, but still not as good as the performance before the merge of  https://github.com/apache/lucene/pull/12631.
This result is not quite same as what i saw locally, but reasonable for me as we do more Outputs#read anyway.
Since we are preparing for the release of 9.9.0. I'm not sure if it is an acceptable trade-off now. Should we backport this or revert https://github.com/apache/lucene/pull/12631?  I'd appreciate your suggestions :)

I don't think we should revert #12631 -- that one was a nice disk space improvement, and the PKLookup performance is quite noisy -- going up or down by just as much when we upgrade JDKs or switch to Panama MMap impl.  Thanks @gf2121.

+1 to not reverting #12631. The fact that our terms index used to not share prefixes properly was a bug, I'm glad it's fixed even though it may make performance slightly slower because more nodes have non-empty outputs to contribute.
FWIW it looks like your change did not only help PKLookup, but possibly also CountTerm, Respell, Fuzzy1 and Fuzzy2.


Update README with Denas links

Signed-off-by: Xue, Chendi<EMAIL_ADDRESS>

@Jian-Zhang , update README links


CI stuff

Fixes #2033

Run unit tests + postgres on circle for outside PRs
Skip other integration tests on circle for outside PRs
Set an actual condition in AZP to skip running secure tests
build wheels after we pass tests

I think we also want to set circle CI's build-wheels job as required for all PRs on the github project, so third-party PRs won't look like they're ready to merge without the tests. (See #2098 for an example)

I think we also want to set circle CI's build-wheels job as required for all PRs on the github project, so third-party PRs won't look like they're ready to merge without the tests. (See #2098 for an example)

I might be missing it, but is there an example of this in #2098?

Huh - I guess when I closed that PR without merging it removed the checks! When I get the branch working right for real tests I'll re-open that PR.

@drewbanin I've opened a new demo PR, #2100 - you can see the results there.


Fix panics caused by misaligned pointer dereferences in "Double Faults" & "Introduction to Paging"

EDIT 2023-05-31:
I just noticed that post 8 is affected by this as well (as already discussed in #1215) and applied the same fix there.

In the "Double Faults" post, the following code is given as an example:
// trigger a page fault
unsafe {
    *(0xdeadbeef as *mut u64) = 42;
};

Dereferencing 0xdeadbeef as any type larger than u8 is undefined behavior, and a recently merged PR for Rust added runtime debug assertions for this.
Thus, instead of the desired effects, the above code panics with the message 'misaligned pointer dereference: address must be a multiple of 0x8 but is 0xdeadbeef'.
Fortunately, the author chose the value 42 such that it fits in an u8, facilitating an easy fix without the need to invent another funny address that would additionally be 8-byte aligned ;)
The English blog text does not mention the type of the pointer so I assume that neither do the translations.

without the need to invent another funny address that would additionally be 8-byte aligned ;)

abad1dea is 4-byte aligned.


implement varying precision per token

Acceptance criteria

[ ] Index precision for different currencies through runtime call:  ormlAssetRegistry.metadata(currencyId).decimals
[ ] Edit services to support dynamic precision

To be clarified:

@offerijns: Will every currency have two precisions (short for amounts and long for prices/yields)? If so, can you pls specify the dynamic decimals per currency?

The precision for the balances in each pool, for both currency amounts and tranche token amounts, are alwasy based on the decimals of the pool currency. This can be retrieved using ormlAssetRegistry.metadata(currencyId).decimals.
The precision for prices/yields is fixed at 27.


Request: mksh

Hi, would it be possible to install mksh shell at hashbang? Thanks!

Hi!
We are currently fixing over a few things when it comes to our ability to deploy changes (actually, running mockups of the servers in which we can run an install, and get the corresponding shell-etc commits).
Once this is fixed, I will happily install mksh; the version available in Debian Jessie is v50d-5, is that fine?

We are currently fixing over a few things when it comes to our ability
to deploy changes (actually, running mockups of the servers in which
we can run an install, and get the corresponding shell-etc commits).
Once this is fixed, I will happily install mksh; the version
available in Debian Jessie is v50d-5, is that fine?

Thanks for reply.  This version looks quite old, but I think it's OK.
Thanks again! ☺

If you want, you can send a PR to use the version from jessie-backports (54-2~bpo8+1).

If you want, you can send a PR to use the version from jessie-backports (54-2~bpo8+1).

Could you point me out to the place in the repo where this is
configured/declared?

Sure!
On Debian systems, this is configured in /etc/apt/preferences.d.
Feel free to copy what the file for mosh does, for instance.

@rqcy Sorry this took forever, but mksh is now installed from backports.


PS help!

OSSU does not have a policy for including political statements in the curriculum. OSSU notes that the United Nations has passed Resolution 2728 characterized by the UN News Service as "Gaza: Security Council passes resolution demanding ‘an immediate ceasefire’ during Ramadan".


GH-21429: [GLib] Add GArrowDenseUnionArrayBuilder

Rationale for this change
It's a missing binding.
What changes are included in this PR?
Add arrow::DenseUnionBuilder binding and related features.
Are these changes tested?
Yes.
Are there any user-facing changes?
Yes.
This PR includes breaking changes to public APIs.

Closes: #21429

+1


Add Dry::Validation::PredicateSet and BuiltIn

Relies on https://github.com/dryrb/dry-container/pull/7 but could be done without if necessary

Sweet. Can we just merge in the singleton feature and push a release of dry-container?

I updated it to work with the freshly released dry-container which includes merge interface and switched back to non-singleton registration.


Service Request edit API

Edit API for service requests.
This is a WIP as it depends on #12907
@miq-bot add_label wip, enhancement, api
@miq-bot assign @abellotti

@miq-bot remove_label wip

LGTM!! :+1:


Rename crate to tauri-mobile

Rename crate to tauri-mobile but keep lib name to cargo-mobile

Why do we need to keep the lib name as cargo-mobile? IMO the cargo- prefix is nicer for Cargo subcommand projects, which is not the case of the library itself.

Changing name will also require bin crates to fix a lot of paths. I can still update them if you want lib name be tauri-mobile too.


After upgrade from 1.7.5 to 1.7.6 node fails to start

I'm using the docker container.
I have a running and synced node on 1.7.5 and simply incrementing the version to 1.7.6 makes the node fail to start. Reviving it by downgrading is possible.
Relevant log message:
failed to load latest version: version of store dao mismatch root store's version; expected 11551808 got 0; new stores should be added using StoreUpgrades

looks like I was too early with the upgrade. a few blocks later and I was able to run the node with the upgraded version.


Adsk Contrib - Improve the FileRules behaviour for some limit cases

Signed-off-by: Patrick Hodoul<EMAIL_ADDRESS>The file rules behaviour for some limit cases was not enough documented, and not consistent between the two types of file rules. The pull request fixes these two aspects. When creating or updating a file rule, a null or empty string for file name pattern, file extension pattern or regular expression now fail (by throwing an exception), and the public header is updated accordingly.

As usual this is a notice that we will merge next week (i.e. Monday or Tuesday), if there are no discussions on this pull request.


dspy watsonx

NameError                                 Traceback (most recent call last)
Cell In[20], line 2
1 import dspy
----> 2 lm = dspy.Watsonx(model="mistralai/mixtral-8x7b-instruct-v01", project_id = PROJECT_ID,
3 credentials = CREDENTIALS)
4 dspy.configure(lm=lm)
File ~/Documents/Assets/Dspytest/dsp/lib/python3.11/site-packages/dsp/modules/watsonx.py:65, in Watsonx.init(self, model, credentials, project_id, **kwargs)
53 self.model_type = "instruct"
54 self.kwargs = {
55     "temperature": 0,
56     "decoding_method": "greedy",
(...)
62     **kwargs,
63 }
---> 65 self.client = Model(
66     model_id=self.model,
67     params=self.kwargs,
68     credentials=self.credentials,
69     project_id=self.project_id,
70 )
72 self.history: list[dict[str, Any]] = []
NameError: name 'Model' is not defined
I get this error enven after installing ibm-watsonx-ai

Hi @shashanka300
Can you try running the import locally from the Watson module's import logic? This should be working locally for the module to work.
import ibm_watsonx_ai  # noqa: F401
from ibm_watsonx_ai.foundation_models import Model

Also, I recommend using the latest dspy.LM client over dspy.Watsonx (which will be deprecated in upcoming DSPy releases). dspy.LM uses LiteLLM which supports WatsonX so you can just do something like dspy.LM(model="watsonx/...", other_watsonX_params..... Feel free to check out the migration notebook for more details!

hi @arnavsinghvi11
Have tried this before i posted the bug report.
Unfortunately that dosen't work either.

currently i am using it with litellm backend


CI: Conformance AWS-CNI: invalid apiVersion "client.authentication.k8s.io/v1alpha1"

CI failure
Looks like Conformance AWS-CNI is failing. Sounds related to an issue with API version when trying to apply aws-k8s-cni.yaml
Run kubectl apply -f https://raw.githubusercontent.com/aws/amazon-vpc-cni-k8s/v1.7.10/config/v1.7/aws-k8s-cni.yaml
  kubectl apply -f https://raw.githubusercontent.com/aws/amazon-vpc-cni-k8s/v1.7.10/config/v1.7/aws-k8s-cni.yaml
  shell: /usr/bin/bash -e {0}
  env:
    clusterName: cilium-cilium-2281100119
    region: us-east-2
    cilium_cli_version: v0.11.4
    check_url: https://github.com/cilium/cilium/actions/runs/2281100119
    eksctl_version: v0.94.0
    AWS_DEFAULT_REGION: us-east-2
    AWS_REGION: us-east-2
    AWS_ACCESS_KEY_ID: ***
    AWS_SECRET_ACCESS_KEY: ***
error: exec plugin: invalid apiVersion "client.authentication.k8s.io/v1alpha1"
Error: Process completed with exit code 1.

The job failing can be found here:
https://github.com/cilium/cilium/runs/6321086188?check_suite_focus=true
The pull request related:
https://github.com/cilium/cilium/pull/19712

May be related to:

https://github.com/aws/aws-cli/issues/6920

Looks like ConformanceEKS (ci-eks)  is failing with the same kind of issue:
Run cilium hubble port-forward&
  cilium hubble port-forward&
  sleep 10s
  [[ $(pgrep -f "cilium.*hubble.*port-forward|kubectl.*port-forward.*hubble-relay" | wc -l) == 2 ]]
  shell: /usr/bin/bash -e {0}
  env:
    clusterName: cilium-cilium-2281100124
    region: us-east-2
    cilium_cli_version: v0.11.4
    check_url: https://github.com/cilium/cilium/actions/runs/2281100124
    eksctl_version: v0.94.0
    AWS_DEFAULT_REGION: us-east-2
    AWS_REGION: us-east-2
    AWS_ACCESS_KEY_ID: ***
    AWS_SECRET_ACCESS_KEY: ***
Unable to parse the provided version "-ci:92b8ed61a0202af38fb254c4228f96d7a982a8e2", assuming v1.11.3 for ConfigMap compatibility

❌ Unable to execute "kubectl port-forward -n kube-system svc/hubble-relay --address <IP_ADDRESS> --address :: 4245:80":
 error: exec plugin: invalid apiVersion "client.authentication.k8s.io/v1alpha1"

Error: Unable to port forward: unable to execute "kubectl port-forward -n kube-system svc/hubble-relay --address <IP_ADDRESS> --address :: 4245:80": exit status 1
Error: Process completed with exit code 1.

https://github.com/cilium/cilium/runs/6321086363?check_suite_focus=true

this could be fixed by https://github.com/cilium/cilium/pull/19716

Fixed now, e.g. latest run from master is green: https://github.com/cilium/cilium/actions/runs/2298983995.


'*' symbols are not supported when configuring schema and query file paths in Graphql config (graphql.config.yaml) file

Description:

'*' symbols are not supported when configuring schema and query file paths in Graphql config (graphql.config.yaml) file
Suggested Labels:

Suggested Assignees:

Affected Product Version:
OS, DB, other environment details and versions:
Steps to reproduce:
Related Issues:

Workaround
We need to provide a document name when configuring the config file for each document we provide. The '*' symbol is not supported currently. The document name is used as the generated client name. You can see that the following works when we provide a document name in the config file.
Before and after client generation when providing a single document with name:

Before and after client generation when providing multiple documents with names:


Validate 2024 PDF layout using production standard

We need to validate our implementation of the 2024 layout against a production standard:

https://github.com/metanorma/mn-samples-iso-private/blob/main/reference-docs/19152-1_2024.pdf

This is a private copy.

Our implementation of the 2024 layout looks differently:

page margins

rendered PDF

production standard

header font-size

rendered PDF (0.5pt smaller font)

production standard

copyright font-size

rendered PDF

production standard

main text font-size

rendered PDF

production standard

last page footer

rendered PDF

production standard

Our PDF layout was updated in https://github.com/metanorma/metanorma-iso/issues/1079 based on the provided PDF example 2024-iso-new-pdf-layout.pdf "Sample of layout for an International Standard (cover page, back page and internal centered layout)".
@ronaldtse to further actions I have to know exactly - what is the correct PDF - in this issue or in https://github.com/metanorma/metanorma-iso/issues/1079?
Note: the PDF from the initial posts opens in the Chrome browser only. Adobe Acrobat opens it and closes immediately, also Foxit Reader and PDF-XChange Viewer. So I have to repair it somehow.

Adobe Acrobat opens it and closes immediately

I'm seeing the same issue too. I can open it in macOS Preview however.
It is very likely that their "design spec" and implemented production PDF are slightly different.

To check the whole document I'll encode it in adoc.

one numbered Note

rendered PDF:

production PDF:

The rendered PDF is correct. From https://www.iso.org/sites/directives/current/part2/index.xhtml#_idTextAnchor340:

24.3 Numbering and subdivision
Within a given clause or subclause, notes shall be numbered sequentially. The numbering restarts at each new subdivision. A single note in a subdivision shall not be numbered.

ordered list numbering - alphabetic vs. arabic:

rendered PDF:

production PDF:

From https://www.metanorma.org/author/topics/blocks/lists/#general-2:

different font size of Note:

rendered PDF (a bit smaller):

production PDF:

wrong baseline when list text contains superscripted text

rendered PDF:

there isn't footnotes separator (51mm horizontal line) in the rendered PDF

indents between footnotes:

rendered PDF:

production PDF:

There is the identical entry in the Normative references and Bibliography:

therefore different identifiers should be used in the adoc:
[bibliography]
== Normative references

* [[[ISO19103,ISO 19103]]], _Geographic information -- Conceptual schema language_
...

[bibliography]
== Bibliography

* [[[ISO19103bib,ISO 19103]]], _Geographic information -- Conceptual schema language_
,..

[ ] Source color link:

rendered PDF:

production PDF:

[ ] Example (numbered vs. unnumbered) alignment:

rendered PDF:

production PDF:

[ ] dash after modified:

rendered PDF en dash (U+2013):

production PDF em dash (U+2014):

Presentation XML contains en dash:
</xref>, modified
 – Note 1 to entry removed.]</termsource>

[ ] different vertical indents between the definition list items, need increase a bit

[ ] text with indent

rendered PDF:

production PDF:

Note: I don't know how to achieve it.

[ ] space before table name

rendered PDF:

production PDF:

[ ] table footer top border

[ ] space between footnotes

rendered PDF

production PDF

[ ] space after table

rendered PDF:

production PDF:

[ ] reference from Annex A sub-clause to another sub-clause

rendered PDF:

production PDF:

[ ] reference from Annex A sub-clause to main section sub-clause

rendered PDF

production PDF

[ ] table cell borders

rendered PDF:

production PDF:

@Intelligent2013 can you help file issues for @opoudjis for those he needs to fix? Thanks.

[ ] smallcap font-size

rendered PDF

production PDF

[ ] references to the Bibliography items

rendered PDF:

production PDF

[ ] comma between bibliography references

rendered PDF:

production PDF:

Adoc markup:
<<ref10>>,<<ref15>>

[ ] text with indent

rendered PDF:

production PDF:

This issue can be solved via css: [css text-indent:7mm]#*1) CoreClassConformant*#.
Rendered PDF:

[ ] reference to the standard

rendered PDF

production PDF

ISO XSLT updated for PDF layout 2024.
Only one issue remains: https://github.com/metanorma/metanorma-iso/issues/1141
On hold.

Done.


pipewire-pulse: Do not try to execute pactl(1)

The program is not in pipewire-pulse.service's PATH, so it always fails
to execute it.
I have no clue as to why this would be needed or wanted, but sound just
works with pipewire (and KDE/Plasma) on NixOS.
Noticed by looking at journalctl -p 0..4:
Jun 14 17:16:39 <hostname> pipewire-pulse[9091]: pw.conf: execvp error 'pactl': No such file or directory

@jtojnar @Kranzes @jansol

Duplicate of #173160


improving hi/lo id generation

Don't issue concurrent requests for new hi values.
see #411
@Sanne @cescoffier  does this look right to you guys?

@Sanne if you don't respond I'm going to just merge it ;-)

He is on PTO, today.
I suppose we can merge it. We already have a test somewhere for this isn't it?

We already have a test somewhere for this isn't it?

Well, I suppose lot of tests will fail if this doesn't work

He is on PTO, today.
I suppose we can merge it. We already have a test somewhere for this isn't it?

Yeah, and I know something useful is being tested there, because I had to struggle more than I expected to get the tests to pass when making this change. (I had not originally considered that there could be more queued id requests than the block size.)
What we don't have is any tests for "concurrent" streams. But I'm totally not going to try adding them right now.

Sounds good to me


Add .mailmap: reauthorize @zdroid commits

Refs #29685.

I'm not a fan of this, how are we going to determine what email addresses can be linked? We have over 1100 contributors, are we going to allow them all to add addresses to this list?
CC @XhmikosR

Judging from the previous discussion: by request, and no (answers to your questions). mailmap is supposed to link only the written emails, not the others.

I'm not a fan of this, how are we going to determine what email addresses can be linked? We have over 1100 contributors, are we going to allow them all to add addresses to this list?

Not really. Just for the cases there's a discrepancy.

@MartijnCuppens It's quite an extraordinary case though. The stats say I have 148 merged PRs out of 202 closed.  Many PRs were merged manually aswell, so the number of "merged PRs" should be higher.
Considering GitHub's merge system in the past created a merge commit for every merge, those ~150 commits actually constitute 300 commits in repo's history, which is ~1.6% out of all commits. The percentage is even higher for v3 commits only.

Merge commits don't count IIRC.
On Tue, Dec 17, 2019, 23:29 Zlatan Vasović<EMAIL_ADDRESS>wrote:

@MartijnCuppens https://github.com/MartijnCuppens It's quite an
extraordinary case though. The stats say I have 148 merged PRs
https://github.com/twbs/bootstrap/pulls?utf8=✓&q=is%3Apr+is%3Amerged+author%3Azdroid
out of 202 closed
https://github.com/twbs/bootstrap/pulls?utf8=✓&q=is%3Apr+author%3Azdroid.
Many PRs were merged manually aswell, so the number of "merged PRs" should
be higher.
Considering GitHub's merge system in the past created a merge commit for
every merge, those ~150 commits actually constitute 300 commits in repo's
history, which is ~1.6% out of all commits. The percentage is even higher
for v3 commits only.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/twbs/bootstrap/pull/29859?email_source=notifications&email_token=AACVLNIWUOSIWZDWUTEPZILQZFADDA5CNFSM4J3ADWXKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHEAOJI#issuecomment-566757157,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACVLNNPMM7SKJINOXUI2SLQZFADDANCNFSM4J3ADWXA
.

Maybe you're right, I'm definitely not sure about that point. Still doesn't change the general point.

What i said and also v3 differs from v4 and master branches. I don't think
github counts commits outside the main branch
On Tue, Dec 17, 2019, 23:33 Zlatan Vasović<EMAIL_ADDRESS>wrote:

Maybe you're right, I'm definitely not sure about that point. Still
doesn't change the general point.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/twbs/bootstrap/pull/29859?email_source=notifications&email_token=AACVLNKT6RZANWQKKEUEVA3QZFARPA5CNFSM4J3ADWXKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHEAZEI#issuecomment-566758545,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACVLNL3QHTPIITYLHZ3XYLQZFARPANCNFSM4J3ADWXA
.

Isn't this something that GitHub can address with multiple email addresses in account settings?

@mdo The Google account associated with my previous email has been permanently deleted. I did try adding it to my GitHub account after your comment, and it seems my commits (such as https://github.com/twbs/bootstrap/pull/15477/commits/576230b92ae5a082eb8e058dc2fab7c67c99bd19) got properly recognized. I'd still give this time since my name isn't in contributors yet. May it be a problem with my email being impossible to verify (since it's deleted)?

I'm personally not even sure if this will fix your issues. Because like I said before, the v3-dev branch is quite different from the master branch thus GitHub won't count the commits to that branch.
I'd suggest that you contact GitHub support first. I don't mind having this patch since it's the standard way, I just want to do it if it's really useful in your case since you are the only one who brought this issue up.

@XhmikosR Thanks for the tip, I'll contact GitHub support about this.

GitHub support confirmed email doesn't have to be verified, and all or at least most of my commits reappeared.
I'm closing this, thanks @mdo for the helpful suggestion.


I'm trying to run a mysql container with the followind cmd:
rkt --insecure-options=image run docker://mysql --set-env=MYSQL_ROOT_PASSWORD=password --set-env=MYSQL_USER=admin --set-env=MYSQL_DATABASE=wordpress

What did you see instead?
image: using image from local store for image name coreos.com/rkt/stage1-coreos:1.0.0
image: using image from local store for url docker://mysql
networking: loading networks from /etc/rkt/net.d
networking: loading network default with type ptp
stage1: warning: no volume specified for mount point "volume-var-lib-mysql", implicitly creating an "empty" volume. This volume will be removed when the pod is garbage-collected.
[ 7583.929682] docker-entrypoint.sh[4]: Initializing database
[ 7584.761196] docker-entrypoint.sh[4]: 2016-04-28T15:40:43.024732Z 0 [Warning] InnoDB: New log files created, LSN=45790
[ 7585.004077] docker-entrypoint.sh[4]: 2016-04-28T15:40:43.267625Z 0 [Warning] InnoDB: Creating foreign key constraint system tables.
[ 7585.069176] docker-entrypoint.sh[4]: 2016-04-28T15:40:43.332727Z 0 [Warning] No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: 915a9457-0d57-11e6-945b-ea1cce63c1d3.
[ 7585.072071] docker-entrypoint.sh[4]: 2016-04-28T15:40:43.335639Z 0 [Warning] Gtid table is not ready to be used. Table 'mysql.gtid_executed' cannot be opened.
[ 7585.072497] docker-entrypoint.sh[4]: 2016-04-28T15:40:43.336068Z 1 [Warning] root@localhost is created with an empty password ! Please consider switching off the --initialize-insecure option.
[ 7586.024520] docker-entrypoint.sh[4]: 2016-04-28T15:40:44.288058Z 1 [Warning] 'user' entry 'root@localhost' ignored in --skip-name-resolve mode.
[ 7586.024779] docker-entrypoint.sh[4]: 2016-04-28T15:40:44.288096Z 1 [Warning] 'user' entry 'mysql.sys@localhost' ignored in --skip-name-resolve mode.
[ 7586.024923] docker-entrypoint.sh[4]: 2016-04-28T15:40:44.288112Z 1 [Warning] 'db' entry 'sys mysql.sys@localhost' ignored in --skip-name-resolve mode.
[ 7586.025100] docker-entrypoint.sh[4]: 2016-04-28T15:40:44.288123Z 1 [Warning] 'proxies_priv' entry '@ root@localhost' ignored in --skip-name-resolve mode.
[ 7586.025249] docker-entrypoint.sh[4]: 2016-04-28T15:40:44.288155Z 1 [Warning] 'tables_priv' entry 'sys_config mysql.sys@localhost' ignored in --skip-name-resolve mode.
[ 7587.969125] docker-entrypoint.sh[4]: Database initialized
[ 7587.972375] docker-entrypoint.sh[4]: MySQL init process in progress...
[ 7588.155131] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.416704Z 0 [Note] mysqld (mysqld 5.7.12) starting as process 38 ...
[ 7588.156341] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.419909Z 0 [Note] InnoDB: PUNCH HOLE support available
[ 7588.156513] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.419935Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
[ 7588.156718] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.419939Z 0 [Note] InnoDB: Uses event mutexes
[ 7588.156959] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.419943Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
[ 7588.157184] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.419946Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.8
[ 7588.157393] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.419949Z 0 [Note] InnoDB: Using Linux native AIO
[ 7588.157605] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.420208Z 0 [Note] InnoDB: Number of pools: 1
[ 7588.157827] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.420309Z 0 [Note] InnoDB: Using CPU crc32 instructions
[ 7588.164713] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.428270Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
[ 7588.174062] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.437620Z 0 [Note] InnoDB: Completed initialization of buffer pool
[ 7588.175815] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.439389Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
[ 7588.187477] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.451031Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
[ 7588.196396] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.459972Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
[ 7588.196717] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.460038Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
[ 7588.248393] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.511954Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
[ 7588.249187] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.512753Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
[ 7588.249493] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.512768Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
[ 7588.249866] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.513453Z 0 [Note] InnoDB: Waiting for purge to start
[ 7588.300352] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.563924Z 0 [Note] InnoDB: 5.7.12 started; log sequence number 2522067
[ 7588.300643] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.564216Z 0 [Note] Plugin 'FEDERATED' is disabled.
[ 7588.300942] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.564527Z 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
[ 7588.302103] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.565681Z 0 [Warning] Failed to set up SSL because of the following SSL library error: SSL context is not usable without certificate and private key
[ 7588.302368] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.565704Z 0 [ERROR] Could not create unix socket lock file /var/run/mysqld/mysqld.sock.lock.
[ 7588.302535] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.565709Z 0 [ERROR] Unable to setup unix socket lock file.
[ 7588.302694] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.565711Z 0 [ERROR] Aborting
[ 7588.302854] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.565717Z 0 [Note] Binlog end
[ 7588.303117] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.566696Z 0 [Note] Shutting down plugin 'ngram'
[ 7588.303365] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.566708Z 0 [Note] Shutting down plugin 'BLACKHOLE'
[ 7588.303598] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.566712Z 0 [Note] Shutting down plugin 'partition'
[ 7588.303824] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.566714Z 0 [Note] Shutting down plugin 'ARCHIVE'
[ 7588.304067] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.566717Z 0 [Note] Shutting down plugin 'MEMORY'
[ 7588.304309] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.566720Z 0 [Note] Shutting down plugin 'INNODB_SYS_VIRTUAL'
[ 7588.304529] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.566722Z 0 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
[ 7588.304684] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.566725Z 0 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
[ 7588.304837] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.566727Z 0 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
[ 7588.304990] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.566729Z 0 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
[ 7588.305167] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.566731Z 0 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
[ 7588.305323] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.566733Z 0 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
[ 7588.305474] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.566735Z 0 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
[ 7588.305625] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.566738Z 0 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
[ 7588.305778] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.566740Z 0 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
[ 7588.305930] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.566742Z 0 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
[ 7588.306102] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.566744Z 0 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
[ 7588.306259] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.566746Z 0 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
[ 7588.306414] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.566749Z 0 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
[ 7588.306566] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.566785Z 0 [Note] Shutting down plugin 'INNODB_FT_DELETED'
[ 7588.306717] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.566837Z 0 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
[ 7588.306867] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.566841Z 0 [Note] Shutting down plugin 'INNODB_METRICS'
[ 7588.307018] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.566843Z 0 [Note] Shutting down plugin 'INNODB_TEMP_TABLE_INFO'
[ 7588.307190] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.566845Z 0 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
[ 7588.307343] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.566848Z 0 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
[ 7588.307501] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.566850Z 0 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
[ 7588.307657] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.566853Z 0 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
[ 7588.307810] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.566855Z 0 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
[ 7588.307959] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.566857Z 0 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
[ 7588.308132] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.566859Z 0 [Note] Shutting down plugin 'INNODB_CMPMEM'
[ 7588.308298] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.566862Z 0 [Note] Shutting down plugin 'INNODB_CMP_RESET'
[ 7588.308453] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.566864Z 0 [Note] Shutting down plugin 'INNODB_CMP'
[ 7588.308602] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.566866Z 0 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
[ 7588.308752] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.566868Z 0 [Note] Shutting down plugin 'INNODB_LOCKS'
[ 7588.308906] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.566870Z 0 [Note] Shutting down plugin 'INNODB_TRX'
[ 7588.309127] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.566872Z 0 [Note] Shutting down plugin 'InnoDB'
[ 7588.309282] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.568032Z 0 [Note] InnoDB: Buffer pool(s) load completed at 160428 15:40:46
[ 7588.309537] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.572916Z 0 [Note] InnoDB: FTS optimize thread exiting.
[ 7588.309770] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.573203Z 0 [Note] InnoDB: Starting shutdown...
[ 7588.409959] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.673508Z 0 [Note] InnoDB: Dumping buffer pool(s) to /var/lib/mysql/ib_buffer_pool
[ 7588.410453] docker-entrypoint.sh[4]: 2016-04-28T15:40:46.673733Z 0 [Note] InnoDB: Buffer pool(s) dump completed at 160428 15:40:46
[ 7588.976571] docker-entrypoint.sh[4]: MySQL init process in progress...
[ 7589.925001] docker-entrypoint.sh[4]: 2016-04-28T15:40:48.188536Z 0 [Note] InnoDB: Shutdown completed; log sequence number 2522086
[ 7589.926594] docker-entrypoint.sh[4]: 2016-04-28T15:40:48.190149Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
[ 7589.926756] docker-entrypoint.sh[4]: 2016-04-28T15:40:48.190166Z 0 [Note] Shutting down plugin 'MyISAM'
[ 7589.926896] docker-entrypoint.sh[4]: 2016-04-28T15:40:48.190180Z 0 [Note] Shutting down plugin 'MRG_MYISAM'
[ 7589.927034] docker-entrypoint.sh[4]: 2016-04-28T15:40:48.190184Z 0 [Note] Shutting down plugin 'CSV'
[ 7589.927188] docker-entrypoint.sh[4]: 2016-04-28T15:40:48.190187Z 0 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
[ 7589.927328] docker-entrypoint.sh[4]: 2016-04-28T15:40:48.190224Z 0 [Note] Shutting down plugin 'sha256_password'
[ 7589.927461] docker-entrypoint.sh[4]: 2016-04-28T15:40:48.190227Z 0 [Note] Shutting down plugin 'mysql_native_password'
[ 7589.927592] docker-entrypoint.sh[4]: 2016-04-28T15:40:48.190350Z 0 [Note] Shutting down plugin 'binlog'
[ 7589.927726] docker-entrypoint.sh[4]: 2016-04-28T15:40:48.190446Z 0 [Note] mysqld: Shutdown complete
[ 7589.980339] docker-entrypoint.sh[4]: MySQL init process in progress...
[ 7590.984126] docker-entrypoint.sh[4]: MySQL init process in progress...
[ 7591.987864] docker-entrypoint.sh[4]: MySQL init process in progress...
[ 7592.991856] docker-entrypoint.sh[4]: MySQL init process in progress...
[ 7593.995730] docker-entrypoint.sh[4]: MySQL init process in progress...
[ 7594.999690] docker-entrypoint.sh[4]: MySQL init process in progress...
[ 7596.003822] docker-entrypoint.sh[4]: MySQL init process in progress...
[ 7597.007871] docker-entrypoint.sh[4]: MySQL init process in progress...
[ 7598.012008] docker-entrypoint.sh[4]: MySQL init process in progress...
[ 7599.015854] docker-entrypoint.sh[4]: MySQL init process in progress...
[ 7600.019924] docker-entrypoint.sh[4]: MySQL init process in progress...
[ 7601.023864] docker-entrypoint.sh[4]: MySQL init process in progress...
[ 7602.027888] docker-entrypoint.sh[4]: MySQL init process in progress...
[ 7603.031841] docker-entrypoint.sh[4]: MySQL init process in progress...
[ 7604.035692] docker-entrypoint.sh[4]: MySQL init process in progress...
[ 7605.039442] docker-entrypoint.sh[4]: MySQL init process in progress...
[ 7606.043436] docker-entrypoint.sh[4]: MySQL init process in progress...
[ 7607.047344] docker-entrypoint.sh[4]: MySQL init process in progress...
[ 7608.051257] docker-entrypoint.sh[4]: MySQL init process in progress...
[ 7609.055218] docker-entrypoint.sh[4]: MySQL init process in progress...
[ 7610.059155] docker-entrypoint.sh[4]: MySQL init process in progress...
[ 7611.063082] docker-entrypoint.sh[4]: MySQL init process in progress...
[ 7612.067124] docker-entrypoint.sh[4]: MySQL init process in progress...
[ 7613.070941] docker-entrypoint.sh[4]: MySQL init process in progress...
[ 7614.074973] docker-entrypoint.sh[4]: MySQL init process in progress...
[ 7615.078929] docker-entrypoint.sh[4]: MySQL init process in progress...
[ 7616.082853] docker-entrypoint.sh[4]: MySQL init process in progress...
[ 7617.086964] docker-entrypoint.sh[4]: MySQL init process in progress...
[ 7618.090957] docker-entrypoint.sh[4]: MySQL init process in progress...
[ 7619.091823] docker-entrypoint.sh[4]: MySQL init process failed.

I just tried that with rkt v1.5.0 and it worked for me. Can you try the latest rkt version?

ping?

Moving to v1+

@ltagliamonte It works for me in rkt 1.8 & 1.9.1 I'm closing this issue, feel free to re-open it if you are able to reproduce it with the latest rkt version.

After running mysql rkt, how to use another container through the JDBC interface to connect Mysql, JDBC URL should be how to write?


update javadocs and remove unused variables

updated javadocs from Storage component to fit coding standards and removed some unused variables.

Codecov Report

Merging #223 (64ad030) into master (a3dd98e) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #223   +/-   ##
=========================================
  Coverage     81.54%   81.54%
  Complexity      638      638
=========================================
  Files            95       95
  Lines          1766     1766
  Branches        183      183
=========================================
  Hits           1440     1440
  Misses          255      255
  Partials         71       71

Impacted Files
Coverage Δ
Complexity Δ

...java/seedu/address/storage/JsonGradPadStorage.java
100.00% <ø> (ø)
8.00 <0.00> (ø)

...va/seedu/address/storage/JsonUserPrefsStorage.java
100.00% <ø> (ø)
5.00 <0.00> (ø)

Continue to review full report at Codecov.

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


Feature: Limit Similar Scripts by script type (Teensyville/Regular)

On the script page (eg https://botc-scripts.azurewebsites.net/script/60) there is a tab which shows similar scripts. When the user views similar scripts for a Teensyville script they are shown full-size regular scripts as well as Teensyville scripts. This can be useful for if someone wants to find a similar theme for a larger game, but not for finding similarly themed Teensyville scripts.
I suggest adding an option to allow the user to filter similar scripts to Teensyville, Regular or All Scripts

I've added separate lists for Full and Teensy scripts.


eks IRSA for authentication

is EKS IRSA possible for authentication to aws-api instead of using static credentials?

Everything that worked via normal terraform command would work with this controller because it just uses HashiCorp's TFExec to directly execute the Terraform binary and other provider binaries inside the container. Please let me know if you got any error.

But it's going to be a handy feature indeed!

ref: https://docs.aws.amazon.com/eks/latest/userguide/iam-roles-for-service-accounts.html

@haarchri This is currently possible by annotating the service account used by the Terraform controller.
If you installed the controller following the quickstart guide from the README then the following should work (substituting the appropriate ROLE_ARN):
kubectl -n flux-system serviceaccount default eks.amazon.com/role-arn=ROLE_ARN
Just ensure the trust policy on the role lines up with the namespace/service account and it should work.


Move from date-io to luxon

We're planning on moving from luxon depending on the calendar library we'll use

@menna-mostafa did we reach a decision?

We agreed that we will stick with date-fns


Update blender & docker manifests

Salvaging https://github.com/princeton-vl/infinigen/pull/252

Hello, im going to include this commit in an upcoming patch that will turn on pypi publishing in CI by default, with some other changes.
I cherrypicked this commit into my branch but it only shows up as myself and @lalalune . Is there a better way to include it that credits everyone? I could edit in a co-authored-by with your id but I couldnt find the email. Ideal way would be to merge this PR into some misc branch I suppose. Open to suggestions.

You can use
Co-Authored-By: "K. S. Ernest (iFire) Lee"<EMAIL_ADDRESS>

Can be salvaged but closing.


What is the purpose of --save when installation of any package

My assumption is that --save is just for running locally in development case.
But when we package the solution, i.e deploy is to prod , the package which we installed using --save is not taken ?

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

ID: 9f5a35c2-9914-fc67-1550-15d4f63c918c
Version Independent ID: 8418c398-1a93-622d-4df8-84c866fef67f
Content: Add jQueryUI Accordion to your SharePoint client-side web part
Content Source: docs/spfx/web-parts/get-started/add-jqueryui-accordion-to-web-part.md
Service: unspecified
GitHub Login: @spdevdocs
Microsoft Alias: spdevdocs

No. --save comes from NPM and means that the package you're about to install well be added to the package.json. If you do it without it, the package will just be installed, but not be added to the package.json.

So if I add a package without - - save and now I move the solution to other environment and run npm install, so in that case the packages will not be installed right?
Npm - - save helps me to install all packages

That was the case indeed with older versions of npm. Starting from v5 (which is the default for the current version of Node - v8), npm automatically saves each package in the package.json file and the generated package-lock.json file.

Docs updated accordingly, so closing this one as there's no mention of --save anymore as they have been updated to match npm v5 version.

Hello there, not sure if the version Vesa mentioned hasn't made it's way to the public, but the section: "Install jQuery and jQuery UI NPM Packages", still has --save in most steps. Maybe worth checking.


You cannot call a method on a null-valued expression.

Continues from: Lability #376
Win7SP1 machines configures normally, and is fully functional, but when I try to use LegacyNetworking components I'm getting "You cannot call a method on a null-valued expression."
Including log, and Cfg.ps1 with cfgdata.psd1
bootstrap.log
Resources.zip

@OsaPL Quick question - are you sure that the NIC is called Ethernet and not Local Area Connection (or similar)?

Anyways, thanks a lot now it works perfectly. :)


HTTP_METHOD=nohttps requires CERT_NAME set to work in some cases

This might just be something to add to the documentation...
I have a wildcard certificate used by a couple virtual hosts which require https (redirect).
When I went to spin up a new virtual host which requires that only http be used (HTTP_METHOD=nohttps) I was surprised to find that I ended up getting a 503. The virtual host
I was attempting to spin up also matched the wildcard certificate which as far as I can tell is what
causes the issue.
The issue can be easily fixed by adding CERT_NAME=<invalid cert name> but it wasn't documented that this would work and it wasn't obvious.
I think it's a bug that a valid cert overrules the HTTP_METHOD=nohttps.

You should provide the /etc/nginx/certs/default.crt and /etc/nginx/certs/default.key files. With those attempts to query that nohttps vhost will be answered with HTTP status code 500.
The relevant part in the documentation is § How SSL Support Works:

The default behavior for the proxy when port 80 and 443 are exposed is as follows:

If a container has a usable cert, port 80 will redirect to 443 for that container so that HTTPS is always preferred when available.
If the container does not have a usable cert, a 503 will be returned.

Note that in the latter case, a browser may get an connection error as no certificate is available to establish a connection. A self-signed or generic cert named default.crt and default.key will allow a client browser to make a SSL connection (likely w/ a warning) and subsequently receive a 503.

(and yes the README says 503, but the actual code is 500 in the nginx conf - #767)

This should have been fixed by #2186


CATT - add 'close' command to stop casting

Hi there,
First, thank you for this very useful project!
I started using it to cast video stream from Motion-Project and it works flawlessly! It utilizes cast_site option of CATT.
I did not discovered option how to stop casting. Issuing command stop do not close running app on chromecast. So if there is no already solution, I would propose to develop/add new command close and this command should close running app/casting session on chromecast, the similar way as voice command stop casting does.
Thanks!

Hmm, yeah, I was looking for this yesterday as well. I thought we had implemented the kill command but it looks like we haven't, though stop eventually stops the app for me.
I agree we should implement this.

I'm not sure I understand this discussion: https://github.com/skorokithakis/catt/blob/a4b578c4937265345ec7e6274b2c668ca0d3fc44/catt/controllers.py#L510
I've never experienced the stop cmd NOT killing the running app. Steps to reproduce?

I feel embarrassed as I can't reproduce behavior I observed earlier. Just checked on Google Chromecast and on Google Nest Hub and issuing command stop closes casting session opened with cast_site. Sorry for creating confusion. I'll close the issue.

No problem!


Make Gradle plugin custom task 'ResolveTask' cacheable

Enh: enable caching of Gradle custom task with type 'ResolveTask' - remove compatibility to Gradle versions prior to 3.2

@frantuma a friendly reminder to have a look at this PR. thx
P.S.
Could you give me some description of how to become an official contribution member?

Do you know whom besides @frantuma could be pinged to have a look at this PR? I am looking forward to have this integrated soon in one of the next releases. thx
P.S.
@webron thanks for the fast response. Is the link to How to contribute the guide you are talking about?

@bronogard another thing to add to the to do list, heh, update the wiki. I was referring to https://github.com/swagger-api/.github/blob/master/CONTRIBUTING.md though.
Right now we're overloaded with requests so it's not that you're being ignored, but rather that we have to prioritize the efforts. And yes, I realize that's where the benefit of adding additional maintainers comes in, which is why we're trying to find the right way to do this, but I have no ETA for it.

@webron thanks for the clarification.
The thought of being somehow ignored certainly crossed my mind. ;(
Could you give me some ETA when I can expect a review of this PR? thx

@bronogard eventually merged #3321 which includes and replaces this PR. Thanks a lot for your contribution!

@webron when do you release a new version in general and what are the criteria (e.g. number of merged PullRequests)? thx

@bronogard At the moment, we don't have well defined criteria.


compilation problems

Describe your bug here.
When I tried to compile the latest version of the source code of 11/29 I got this error

Command Prompt/Terminal logs (if existing)
No response
Are you modding a build from source or with Lua?
Source
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
no, nothing

https://github.com/ShadowMario/FNF-PsychEngine/issues/1419#issuecomment-980794707


Add node 9, 10, 11 to Circle test suite

Run the existing test suite against other node versions

Does #1057 solve this?

@kkalavantavanich I merged your PR, but tests are failing on Node 12. Any thoughts?

I am trying to resolve that. Seems the resolved gRPC version is not compatible with node12.

@jaredpalmer #1058 should fix that.

Seems the build is passing on Node 12 but failing on Node 9. I will try to investigate if I have time, which will probably be in 2 - 3 days.

@jaredpalmer  I am unable to reproduce the bug shown in CircleCI. Can you trigger a run on Node 9 to see if it is a problem by chance with CircleCI for that last build?

Just rechecking things and seems that everything is up and running now. Should this issue be closed?

there is a problem with windows tests, jest can't find the tests on windows, any ideas?
 I can see only node9 failing on CircleCI.

@kkalavantavanich https://github.com/jaredpalmer/razzle/pull/1210/checks?check_run_id=509343331
it can't find tests on windows 10 with node 10 and 12, and there is a problem with windows and node 8, it has connectivity issues

Seems like it fails on a lot of branches though... I am suspicious of the file glob in jest.config.json
"testMatch": [
    "<rootDir>/tests/**/?(*.)(spec|test).(ts|js)?(x)"
  ]

Seems like it might not be windows compatible.

Might be related: https://github.com/facebook/jest/issues/7914

I found this: https://github.com/facebook/jest/issues/7914#issuecomment-464352069
I have a windows machine I will test and tell you the results here.

Fixed, closing


Denoise blurry image ?

With the current implementation, is it possible to simply denoise a blurry image and not generate an image from raw white noise ? If it is possible, how can I do that ?

You can try to add gausian noise to the blurry image before sampling, so it thinks that something is there


JWT.encode({"exp": 10}, "secret")

This seems to be not working. I am using gem 'jwt', ~> 1.2.0
Error Message
SyntaxError: (irb):3: syntax error, unexpected ':'
JWT.encode({"exp": 10}, "ssss" )

This syntax is supported only by the latest ruby versions:
JWT.encode({"exp": 10}, "ssss" )

Try this syntax instead:
JWT.encode({"exp" => 10}, "ssss")

Thanks that syntax worked perfectly!


prepare mainnet deploy

Codecov Report

Merging #78 (80dd3e2) into master (a1bf2c0) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #78   +/-   ##
=======================================
  Coverage   86.51%   86.51%
=======================================
  Files          35       35
  Lines        2129     2129
  Branches      313      313
=======================================
  Hits         1842     1842
  Misses        287      287

Impacted Files
Coverage Δ

contracts/PowerIndexPool.sol
93.84% <ø> (ø)

Continue to review full report at Codecov.

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


Adjoint command not working in TUI API in 23R1

🔍 Before submitting the issue

[X] I have searched among the existing issues
[X] I am using a Python virtual environment

🐞 Description of the bug
This TUI command works:
/adjoint/geometry/parameterize-and-explore/design-conditions/create "fixed-walls-constraint" "test"
This TUI API command does not work:
session.solver.tui.adjoint.geometry.parameterize_and_explore.design_conditions.create("fixed-walls-constraint","test")
It prints the following error:
Create new condition
Type options: ("fixed-walls-constraint" "bounded-by-plane" "bounded-by-surfaces" "prescribed-profile" "rotation" "translation" "scaling" "rigid-body" "compound")

Error: eval: unbound variable
Error Object: fixed-walls-constraint
Invalid string.

Error: eval: unbound variable
Error Object: test
Invalid string.

📝 Steps to reproduce
Run above script with any case.
💻 Which operating system are you using?

Hi @mkundu1 . Yes that works! Is this a bug or a feature?

This is limitation, documented here.


Modify top comment in zh.toml

Currently, the comment in i18n/zh.toml says that the i18n strings are for English. This PR changes the wording to make it more clear that it's for Chinese.

/lgtm

/approve


RC1 Dependencies fail to deploy to Azure

I'm deploying my RC1 project from Bitbucket to Azure through Continuous Integration. The project was built off of DNX 4.5.1 RC1 libraries and I had a successful deployment back in March.
A recent code change failed to deploy and I haven't been able to track down why quite yet. When I look into the log (attached) it appears that after all my prepublish actions complete, I get an error about some RC2 library references failing to load. The odd thing is that the libraries in question aren't even specified in my project.json file.
 Unable to resolve dependency Microsoft.Extensions.Caching.Abstractions 1.0.0-rc2-final
  Unable to resolve dependency Microsoft.Extensions.DependencyInjection.Abstractions 1.0.0-rc2-final
  Unable to resolve dependency Microsoft.Extensions.Options 1.0.0-rc2-final
  Unable to resolve dependency Microsoft.Extensions.Caching.Abstractions 1.0.0-rc2-final
  Unable to resolve dependency Microsoft.Extensions.DependencyInjection.Abstractions 1.0.0-rc2-final
  Unable to resolve dependency Microsoft.Extensions.Options 1.0.0-rc2-final

I found a recent StackOverflow post regarding the issue and noted that I'm already using a custom deploy script so I can run my EF migration commands. The only difference I see between the recommended script and mine is that I'm using x86 instead of x64, there is my custom EF code, and that the recommended script no longer checks for POST_DEPLOY commands to execute.
Would any of those factors be an issue? I was going to update my app service to use x64 and make those small tweaks to the script, but it was recommended I open a case anyway. I'm attaching my deploy log and my custom deploy script if it helps.
deploy_cmd.txt
deploy_test_fail.txt

I wonder if there is some dnu/NuGet issue not directly related to Kudu here. Looking at your output, it looks like the restore is getting some RC2 packages, e.g.
GET https://api.nuget.org/v3-flatcontainer/microsoft.extensions.caching.memory/1.0.0-rc2-final/microsoft.extensions.caching.memory.1.0.0-rc2-final.nupkg

To isolate, I'd suggest manually running that very same dnu restore command on your local machine, and see if you also end up with some RC2 packages.

I will do that and let you know. For what it is worth, these are the packages in my project.json file:
"EntityFramework.Commands": "7.0.0-rc1-final",
    "EntityFramework.Core": "7.0.0-rc1-final",
    "EntityFramework.MicrosoftSqlServer": "7.0.0-rc1-final",
    "Microsoft.AspNet.Authentication.Cookies": "1.0.0-rc1-final",
    "Microsoft.AspNet.Authentication.OpenIdConnect": "1.0.0-rc1-final",
    "Microsoft.AspNet.Diagnostics": "1.0.0-rc1-final",
    "Microsoft.AspNet.IISPlatformHandler": "1.0.0-rc1-final",
    "Microsoft.AspNet.Mvc": "6.0.0-rc1-final",
    "Microsoft.AspNet.Mvc.TagHelpers": "6.0.0-rc1-final",
    "Microsoft.AspNet.Server.Kestrel": "1.0.0-rc1-final",
    "Microsoft.AspNet.StaticFiles": "1.0.0-rc1-final",
    "Microsoft.AspNet.Tooling.Razor": "1.0.0-rc1-final",
    "Microsoft.AspNet.Http": "1.0.0-rc1-final",
    "Microsoft.Extensions.Configuration.FileProviderExtensions": "1.0.0-rc1-final",
    "Microsoft.Extensions.Configuration.Json": "1.0.0-rc1-final",
    "Microsoft.Extensions.Configuration.UserSecrets": "1.0.0-rc1-final",
    "Microsoft.Extensions.Logging": "1.0.0-rc1-final",
    "Microsoft.Extensions.Logging.Console": "1.0.0-rc1-final",
    "Microsoft.Extensions.Logging.Debug": "1.0.0-rc1-final",
    "Microsoft.Framework.ConfigurationModel": "1.0.0-beta2",
    "Microsoft.VisualStudio.Web.BrowserLink.Loader": "14.0.0-rc1-final",
    "WindowsAzure.Storage": "6.2.2-preview",
    "Microsoft.AspNet.Session": "1.0.0-*",
    "Microsoft.Extensions.Caching.Memory": "1.0.0-*",
    "OpenXmlPowerTools": "4.1.3",
    "DocumentFormat.OpenXml": "2.5.0",
    "WindowsAzure.MediaServices": "3.5.2",
    "WindowsAzure.MediaServices.Extensions": "3.3.0",
    "Microsoft.Azure.Search": "1.0.1-preview",
    "NReco.VideoConverter": "1.0.8",
    "Microsoft.Owin": "2.0.2",
    "Microsoft.Owin.Security": "2.0.2",
    "Microsoft.Owin.Security.Cookies": "2.0.2",
    "Microsoft.ApplicationInsights.AspNet": "1.0.0-beta8"

I wonder if maybe the OpenXML or VideoConverter libraries would be the culprit, but I don't know how they would be looking specifically for the rc2 libraries as dependencies

Closing for now. We can reactivate if something points at a Kudu specific issue.

Just as followup to this in case it gets stumbled upon, the issue at hand was with my 1.0.0-* dependencies. Since they were "open" on the version, they were attempting to grab rc2 dependencies which were incompatible. Once I changed these to a fixed RC1, things resolved themselves. I was unable to update to RC2 because some of my other libraries were incompatible.


Configure end-point probe-time,retry values etc from kube-loxilb

Is your feature request related to a problem? Please describe.
Currently, some values needed to configure end-points like probing timer and retry values need to be manually configured using loxicmd. Otherwise the default values in loxilb are used which may not be suitable for everyone.
Describe the solution you'd like
When using kube-loxilb, one should be able to specify default values using some annotation
Describe alternatives you've considered
N/A
Additional context
N/A

The support has been added.  The service can be configured with the following annotations -
apiVersion: v1
kind: Service
metadata:
  name: iperf-service
  annotations:
    loxilb.io/lbmode: "fullnat"
    loxilb.io/liveness: "yes"
    loxilb.io/probetimeout: "10"
    loxilb.io/proberetries: "2"
spec:
  externalTrafficPolicy: Local
  loadBalancerClass: loxilb.io/loxilb
  selector:
    what: the
  ports:
    - port: 55001
      targetPort: 5001
  type: LoadBalancer

In the above example, there will be two retries in interval of 10 seconds before considering the end-point as inoperative.


Fix weighted routing stats version

Signed-off-by: Anshu Agarwal<EMAIL_ADDRESS>
Description
This PR fixes weighted routing stats version. Currently, the version is set to CURRENT but should be 2_6
Issues Resolved
[List any issues this PR will resolve]
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[ ] Commits are signed per the DCO using --signoff
[ ] Commit changes are listed out in CHANGELOG.md file (See: Changelog)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@Bukhtawar how come we are merging pull request with failing checks? the main is broken now :(

The main was broken due to BWC(know reason) which is due to the sequence of backports and main branch commit which was addressed in backport PR

The main was broken due to BWC(know reason) which is due to the sequence of backports and main branch commit which was addressed in backport PR

I think we should never merge pull requests with failing check, the process would still require 2 pull requests (2.x goes first, main goes second) but smoother for other people (IMHO)

100%