[CPU] Retire CPUDoubleTilingPadExpert pipeline.

Remove the expert and related methods.
Rename setMatmulNoPadRootConfig to setMatmulRootConfig
Replace preset CPUDoubleTilingPadExpert compilation_info with CPUDoubleTilingExpert`
Delete e2e_matmul_nondt_f32_small_no_padding test suite. It was added when we was enabling pad expert.
Inline getNoPadTilingExpert because it is only used by setMatmulRootConfig.

Awesome! Thanks for the cleanup! Is it possible to preserve the lit tests with a non padding configuration instead of removing them?

I think that should be covered by other test suite? Though some of them are disabled because of https://github.com/openxla/iree/issues/15800 ..


Feature/issue 129 add autoupdate for pre commit

GitHub Issue: #129
Description
This change adds an autoupdate schedule for pre-commit CI.
PR Acceptance Checklist

[n/a] Unit tests added/updated and passing.
[n/a] Integration testing
[x] CHANGELOG.md updated
[n/a] Documentation updated (if needed).

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 14.92%. Comparing base (b399fad) to head (8ccea12).

Additional details and impacted files
@@           Coverage Diff            @@
##           develop     #132   +/-   ##
========================================
  Coverage    14.92%   14.92%
========================================
  Files            4        4
  Lines          134      134
========================================
  Hits            20       20
  Misses         114      114

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


"Native review for TheSeamau5/elm-loop"

I'd like to be able to add my elm-loop library to the list of packages. I've seen a lot of complaints about the lack of loops and tail call optimization in Elm. Initially, I made a wrapper on top of trampolines, but then people started worrying about the performance overhead of trampolines, so I made this. It's just a wrapper on top of for-loops and while-loops where the input is cloned into a temporary variable and then that temporary variable is updated by a given function until some given condition is met.
The simple examples to use it are as follows :
-- Iterate 10 times given initial value of 0 and
-- increment that initial value by 1 each time
-- This is equivalent to saying add 1 ten times to 0
counter1 = iterate 10 0 ((+) 1) -- 10

-- This says, loop while the counter is less than or equal to 10
-- given an initial counter value of 0
-- and we update the counter each time by incrementing it
counter2 =
   loopWhile (\{counter} -> counter <= 10)
             {counter = 0}
             (\{counter} -> {counter = counter + 1}

-- {counter = 10}

-- If you don't want to get the whole record and want to
-- filter out the result of the counter, you can use
counter3 =
    loopWhileWithResult (\{counter} -> counter <= 10)
                        {counter = 0}
                        (\{counter} -> {counter = counter + 1})
                        .counter
-- 10

The initial state is clone, so no worries about immutability. If you notice any bugs or anything weird, please tell me on the issue tracker for elm-loop.
But, yeah, since this wraps for-loops and while-loops, I need to make it a Native Library.

@TheSeamau5 do you still want this reviewed, now that tail-call optimisation is coming soon?

No, I'll just close it.

Thanks for looking through these @Apanatshka! :D And thanks @TheSeamau5 for your patience on this, excited to finally release TCO :)


Update layout to use CDN for favicon

Instead of using an local asset for the favicon, this PR points the Heroku CDN which serves the favicon for many other Heroku properties. The main idea is behind this change is to keep the favicon up-to-date on identity and centralize the location of the favicon for future changes.

cc @itchymutt

LGTM! 👍

thanks @dmcinnes !


Dependencies upgrade

This is to partially fix, short term, #252
Shrinkrapping all the nested dependencies seems a bit of a voodoo practice, but it is not uncommon.
Summary here:

node-dir "0.1.9" =>  "0.1.12",
npm "3.8.8" => "3.10.2",
tar.gz "0.1.1" => "1.0.5"

Nested deps upgraded to latest version because of vulnerabilities:

uglify-js * => "2.6.2",
minimatch * => "3.0.2"

PS - Targz has breaking changes. This means both Registry and CLI need to be in sync so this will require a minor version upgrade.

hi @matteofigus LGTM I also managed to fetch the repo and run all the tests; everything is green!

I am going to merge and delete this branch alright?
-Mattia

Sure go for it @mattiaerre


Slider multiple range jumps width when min value is not 0

Describe the bug
Hi, i have setup a multiple slider for select a range of years (from to)
<vue-slider       v-model="dataTimeModel"       :min="1500"       :max="2019"       :min-range="1500"       :max-range="2019"       :tooltip="'always'"       :tooltipPlacement="'bottom'"       :order="true"       :marks="marks"     />
when it loads, everything is perfect, but when i click to move the slider, it jumps to width -200% and position of dot goes to outside the screen
here is the fiddle reproduction of the error
https://jsfiddle.net/rd5j4fu8/2/
Additional context
When i change the minimum value to 0, everything goes well, but because i want to start from 1500, then it brakes
Environment (If you feel unrelated, please delete the block)

Vue version: [v2.6.10]
Component Version: [v3.0.33]

never mind, i miss understood the usage of min-range/max-range., so it was my mistake in configuration, thank you very much for this great component though, very very usefull and powerful! 👍

never mind, i miss understood the usage of min-range/max-range., so it was my mistake in configuration, thank you very much for this great component though, very very usefull and powerful! 👍

It would be more helpful if you would share what was the exact mistake in your configuration and showing how did you fixed it.


Phase 3: Gear Effects

New datamined raid gear
https://www.wowhead.com/classic/news/sunken-temple-raid-loot-in-datamining-phase-3-season-of-discovery-338288
New datamined Blood Moon gear
https://www.wowhead.com/classic/news/blood-moon-pvp-rewards-phase-3-datamining-season-of-discovery-338290
Weapons

[x] Shadowblade
[x] Hookfang Shanker
[x] Flurry Axe
[x] Hammer of the Northern Wind
[x] Hanzo Sword
[x] Bloodrazor
[x] Firebreather
[x] Vilerend Slicer
[x] Thrash Blade
[x] Joonho's Mercy
[x] Blade of Eternal Darkness
[x] Satyr's Lash
[ ] Fist of Stone
[ ] Serpent Slicer
[ ] Searing Needle
[ ] The Hand of Antu'sul
[ ] Shortsword of Vengeance
[ ] Gryphon Rider's Stormhammer
[ ] Gutwrencher
[ ] Bloodletter Scalpel
[ ] Linken's Sword of Mastery
[x] Cobra Fang Claw
[x] Serpent's Striker

Added in https://github.com/wowsims/sod/pull/533 with a 5% proc chance (same as Mekkatorque's). Need to verify chance

[x] Ritualist's Hammer (Druid Only)

Just a stronger Bloodbark Crusher

[x] Gurubashi Pit Fighter's Bow (Hunter Only)

Just a stronger Bloodlash Bow

[ ] Bloodthirst Crossbow (Hunter Only)
[ ] Dragon's Cry

Trinkets
Raid Trinkets

[ ] Chain Essence of Eranikus
[x] Zila Gular (Warlock Only)
[ ] Atal'ai Blood Ceremony

No clue what this does. It's a 1-minute channel and summons an object

[ ] Atal'ai Blood Ritual Badge
[x] Atal'ai Blood Ritual Charm
[ ] Atal'ai Blood Ritual Medallion
[ ] Nightmare Resonance Crystal

Spell hard to tell what exactly this does. Includes a server-side script

Darkmoon Cards
https://www.wowhead.com/classic/news/phase-3-datamined-darkmoon-faire-trinkets-season-of-discovery-338285

[ ] Darkmoon Card: Overgrowth

Basically Revitalize but with a 5% proc chance Overgrowth

[x] Darkmoon Card: Decay

Wowhead lists a 100% proc chance at the moment but this is most likely wrong based on the tooltip
Updated with a 35% proc chance and 200ms ICD (maybe just on spell cast and not ticks but unsure)

[ ] Darkmoon Card: Sandstorm

Wowhead lists a 100% proc chance at the moment but this is most likely wrong based on the tooltip

[x] Darkmoon Card: Torment

No combat effect so nothing to do for this one

Not to do

[x] Atal'alarion's Enchanted Boulder

Seems to turn the user into a large troll Spell with no discernible combat effect

[x] Lledra's Inanimator

Seems to cause the player to hide in a barrel with no discernible combat effect

[x] Unorthodox Hex Stick

Seems to turn the character into a worm with no discernible combat effect

[x] Witch Doctor's Hex Stick

Seems to make the character stealthier while in ST but with no discernible combat effect

Armor

[x] Phase 3 Tier Bonuses

https://github.com/wowsims/sod/issues/515

[x] Phase 3 Crafted Armor

Shoulders added in https://github.com/wowsims/sod/pull/519

Other

[ ] Libram of Draconic Destruction (Paladin)
[x] Totem of Fiery Precision (Shaman)
[x] Serpent's Ascension set bonus

Combination of Serpent's Striker and https://www.wowhead.com/classic/item=220588/cobra-fang-claw

Incomplete Phase 2 Gear

[x] Gyromatic Experiment 420b

Battle Squawk buff added in https://github.com/wowsims/sod/pull/470. Maybe we could just implement the trinket to trigger the aura?

[x] Domesticated Attack Chicken

Two items I noticed the on-hit effect doesn't show up in the damage breakdown:
Shadowblade
Hookfang Shanker

Added Flurry Axe to the list

Some more - All of these have some damage effect component or resource / debuff they apply, and the sim does not have those damage sources in the results. This is pretty much "any weapon with a proc in p3" I could find.
Hammer of the Northern Wind
Hanzo Sword
Bloodrazor
Firebreather
Vilerend Slicer
Thrash Blade -> Unsure on this one, could not see any Extra Attack events in the Log tab of results
Joonho's Mercy
Blade of Eternal Darkness
Satyr's Lash
Fist of Stone -> Resource tab shows no mana gained, but I was testing on rogue so it may just not do that
Serpent Slicer
Searing Needle
The Hand of Antu'sul
Shortsword of Vengeance
Gryphon Rider's Stormhammer
Gutwrencher
Bloodletter Scalpel
Linken's Sword of Mastery

Thanks @Lisonna ! Added all of those. I verified the two you weren't sure about were in fact not implemented

Forgot to mention the raid fist weapons
Cobra Fang Claw
Serpent's Striker

Cobra Fang Claw is added in #529.

Serpent's Striker is added in #533.

Serpent's Ascension set bonus
Ritualist's Hammer (Druid Only)
Gurubashi Pit Fighter's Bow (Hunter Only)
all added in https://github.com/wowsims/sod/pull/534

Dragon's Cry

Roar of the Guardian is added in #545

Added the first 10 non-implemented ones in https://github.com/wowsims/sod/pull/591 (Shadowblade up to Satyr's Lash)

And the remaining ones, but for Dragon's Cry in https://github.com/wowsims/sod/pull/596

Adding the following in https://github.com/wowsims/sod/pull/651

Dragon's Cry
Atal'ai Blood Ritual Badge
Atal'ai Blood Ritual Medallion
Libram of Draconic Destruction


development server

Describe the bug
Having issues with getting my development server to function. Surely it is an easy fix.
I simply tried npm start to set up my development server but I keep getting a json file not found error but I have a Json package. I am sure I am over thinking it but a brand new set of eyes would help. At this point the project should at show up in the development server and display the bare bones with no errors. I am pretty sure when I started the project it had a development server...any help would be great. Too far into the project to ditch it. Thanks again!
Link to the blitz that caused the error
https://stackblitz.com/edit/node-jd7clw?file=frontend%2Fsrc%2FControllers%2FbugController.js,frontend%2Fsrc%2FApp.js
Steps to reproduce
none
Expected behavior
dev server with Login: username box and password
Parity with Local

[X] I have run the project in my local machine and I could not reproduce the issue.

Screenshots
none
Platform
Browser name  = Chrome
Full version  = <IP_ADDRESS>
Major version = 103
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (X11; CrOS x86_64 14816.131.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
performance.memory = {
  "totalJSHeapSize": 158018059,
  "usedJSHeapSize": 148362183,
  "jsHeapSizeLimit":<PHONE_NUMBER>
}
Hash = 8dd2e1d89f7d2e6b43a2b4af08588e58ffd9a2ea

Additional context
none

Hi @futuremillionaire14.
Looking at your project I found a couple issues:

Your package.json and code are in a subfolder named frontend. Because of that, StackBlitz is not finding a package.json at the root of the project and will not try to install npm dependencies or run a start command (which would be npm start for this project).
On top of that, your package.json file is actually named package.json , with a trailing space. So it's technically not named package.json, and not recognized by tools.

These Terminal commands seem to work in your project:
cd frontend
mv 'package.json ' 'package.json'
npm install
npm start

After that, webpack seems to start in development mode correctly, but there are still some errors in your code:

One file is importing a module that doesn't exist.
You're trying to use ReactDOM.render from 'react-dom/client' but that render method doesn't exist. I think you might have code intended for React 16 or 17, but might be trying to use it with React 18, and the exports have changed in React 18.

Thank you very much for your thorough response Florens. I am still somewhat
of a novice at coding so any feedback helps.
Have a great day!
All the best
On Mon, Jan 9, 2023 at 1:58 PM Florens Verschelde @.***>
wrote:

Hi @futuremillionaire14 https://github.com/futuremillionaire14.
Looking at your project I found a couple issues:

Your package.json and code are in a subfolder named frontend.
Because of that, StackBlitz is not finding a package.json at the root
of the project and will not try to install npm dependencies or run a start
command (which would be npm start for this project).
On top of that, your package.json file is actually named package.json
, with a trailing space. So it's technically not named package.json,
and not recognized by tools.

These Terminal commands seem to work in your project:
cd frontend
mv 'package.json ' 'package.json'
npm install
npm start
After that, webpack seems to start in development mode correctly, but
there are still some errors in your code:

One file is importing a module that doesn't exist.
You're trying to use ReactDOM.render from 'react-dom/client' but
that render method doesn't exist. I think you might have code intended
for React 16 or 17, but might be trying to use it with React 18, and the
exports have changed in React 18.

—
Reply to this email directly, view it on GitHub
https://github.com/stackblitz/webcontainer-core/issues/936#issuecomment-1376132580,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A4UMI3SAZH2HRJWB2EDMWHTWRRNVLANCNFSM6AAAAAATVWDBKI
.
You are receiving this because you were mentioned.Message ID:
@.***>

Actually a couple of more things for you. Bare with me, I am a novice at this. Do you think my code is salvageable? Or should I scrap it and start again. I am incorporating the things you mentioned but I am still having issues. I don't want really want to start over.
Thank you for your patience.


flyctl: 0.2.40 -> 0.2.46

Description of changes
https://github.com/superfly/flyctl/compare/v0.2.40...v0.2.46
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

@superherointj thanks for the meta update


Not working with Next JS version (0.1.11)

I have tried this version with our application  give this error

Please suggest what i can do . while 0.15 version orold only pdf view cause problem with my code.

facing same issue, can someone plesase help?

Same issue

nextjs@15 solved this issue


Delete ocp user and only use individual accounts

For helpdesk analysts, we can create a group for adding/editing publications, but not for managing jobs.
I should just double check that nothing depends on the ocp user.

I've deleted the ocp user, and created Viewer and Contributor groups, documented in admin guide.


Make the module a single file module and add more documentation

What do you think of plopping all the code into a single file, enet.jai, so that its a single file module? This would make searching the code easier since you can just Ctrl-f and find everything rather than needing to do some multi-file search thing.  Its also nice to have as few tabs as possible related to other peoples code, currently when I work on networking stuff in my game I have a few tabs dedicated to just this module.
A separate point: there are a bunch of comments in the C repo which would be helpful to have here, what do you think about bringing them over? If we did the single file thing in a way which closely mirrors the positioning of functions in the C repository (https://github.com/zpl-c/enet) then even if we didn't port the documentation it would be easy to compare this code with theirs, this was a helpful thing to do when I was debugging the peer_reset function in an earlier PR. My preference would be do the single file thing as well as port the documentation though.
I am open to doing both of the above, I'm just checking how you feel about them before putting the work in :)

I originally split it up so that if someone wanted to find all the public peer procedures, then they could open up the file. But on the other hand, everything is prefixed with peer_ or host_ so maybe it's not that big of a deal search-wise. It also keeps the internal procedures for the context close by, so it might make it easier see what's in module scope and what's in public scope when looking at the code because the files are smaller so you don't have to scroll far up and see if this procedure is under a #scope_module.
It is nice to have single file modules though, like when I was bug hunting with the zpl-c code, it's nice to have a single tab and do a search. I would be okay with putting it into one file

Ah great :) I've been away for a few weeks so been very out of the loop with the jai/enet stuff
I guess we can close this issue now


Finalize all ADRs

Task

Write ADRs for any decisions made during this sprint

Deliverables

ADR docs

Size Estimation: Medium (2-4 hours)

Completed.


Explosion SFX juicing + higher persistence

About the PR

this PR does 3 main things:

reduces the volume of metalbreak.ogg generally as well as the destruction volumes of many items in the game, notably tiles/lights/pipes/tables etc. there was a huge issue with explosions where these sounds would super overpower the actual explosion sound, which i wanted to mitigate. the explosion sound volume also isn't lowered anymore
triples the persistence of explosions from 0.3 to 1.0 seconds -- i felt that bombs which iterated all of their tiles in a tick or two faded away way too fast and it's better to see the visuals for a little longer. i tried 1.5-2 seconds but it felt really weird for small bombs. maybe in the future try scaling this with intensity.
adds in small explosion sounds as well as far explosion sounds! small plays at ~relatively small explosions (minibomb or less) and far explosions play outside of a certain radius of the explosion for people outside of the audio range of the bomb normally but who should be aware it happened. not grid-based, just radius based right now since i didnt see any reason not to. audio range of these effects was also changed but shouldn't be noticeable to players, the base audio range was just way overtuned

Why / Balance

feels nicer. far explosion sfx is pretty. small explosion sfx is nice. its good to be able toa ctually hear the explosion instead of METALBREAK.OGG x100. its still kind of an issue with big bombs but really we need a more holistic solution like dynamically tuning down sound sources that are just playing the same sound
Technical details

Media

[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

close & big explosion
https://github.com/space-wizards/space-station-14/assets/19853115/6d1816d2-c3df-46d7-90e5-b430eadea33f
close & small explosion
https://github.com/space-wizards/space-station-14/assets/19853115/7e224090-41b9-499b-816b-55ebb5da430d
far & big explosion
https://github.com/space-wizards/space-station-14/assets/19853115/3ff6eec6-5ac3-4489-856e-4d8391b4b908
far & small explosion
https://github.com/space-wizards/space-station-14/assets/19853115/88bbadd6-6e37-47a7-9301-d1619870c786
Breaking changes

Changelog

:cl:

add: Explosion visuals now last slightly longer
add: You will now hear a reverbed explosion sound effect for explosions that are far away from you
add: Smaller explosions now make a distinct sound compared to larger ones

should be noted that its possible for the close & far explosion sounds to both play for specific sizes and distances but i opted not to fix it because it actually just sounds cool

WOW this sounds really cool


go get errors

go get github.com/ceph/go-ceph
github.com/ceph/go-ceph/rbd
/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/librbd.so: undefined reference to NSS_CMSMessage_ContentLevel' /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/librbd.so: undefined reference toNSS_CMSDigestContext_Update'
/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/librbd.so: undefined reference to PORT_SetError' /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/librbd.so: undefined reference toNSS_CMSSignerInfo_GetSignerCommonName'
/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/librbd.so: undefined reference to PK11_CipherOp' /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/librbd.so: undefined reference toNSS_CMSDecoder_Start'
/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/librbd.so: undefined reference to NSS_CMSSignedData_VerifySignerInfo' /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/librbd.so: undefined reference toNSS_CMSSignedData_ImportCerts'
/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/librbd.so: undefined reference to PORT_Free' /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/librbd.so: undefined reference toPK11_ParamFromIV'
/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/librbd.so: undefined reference to PK11_FreeSlot' /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/librbd.so: undefined reference toCERT_GetDefaultCertDB'
/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/librbd.so: undefined reference to NSS_ShutdownContext' /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/librbd.so: undefined reference toPK11_CreateContextBySymKey'
/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/librbd.so: undefined reference to PK11_DestroyContext' /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/librbd.so: undefined reference toPK11_ImportSymKey'
/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/librbd.so: undefined reference to NSS_CMSDecoder_Update' /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/librbd.so: undefined reference toPK11_FreeSymKey'
/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/librbd.so: undefined reference to NSS_CMSSignedData_GetSignerInfo' /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/librbd.so: undefined reference toNSS_CMSSignedData_HasDigests'
/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/librbd.so: undefined reference to PORT_NewArena' /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/librbd.so: undefined reference toNSS_CMSContentInfo_GetContentTypeTag'
/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/librbd.so: undefined reference to NSS_CMSMessage_Destroy' /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/librbd.so: undefined reference toNSS_InitContext'
/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/librbd.so: undefined reference to NSS_CMSSignedData_VerifyCertsOnly' /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/librbd.so: undefined reference toNSS_CMSMessage_ContentLevelCount'
/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/librbd.so: undefined reference to NSS_CMSContentInfo_GetContent' /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/librbd.so: undefined reference toNSS_CMSDigestContext_FinishMultiple'
/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/librbd.so: undefined reference to NSS_CMSDecoder_Cancel' /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/librbd.so: undefined reference toNSS_CMSSignerInfo_GetVerificationStatus'
/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/librbd.so: undefined reference to PK11_DigestFinal' /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/librbd.so: undefined reference toNSS_CMSDigestContext_StartMultiple'
/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/librbd.so: undefined reference to NSS_CMSUtil_VerificationStatusToString' /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/librbd.so: undefined reference toNSS_CMSSignedData_SetDigests'
/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/librbd.so: undefined reference to PR_GetError' /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/librbd.so: undefined reference toNSS_CMSMessage_GetContent'
/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/librbd.so: undefined reference to PORT_FreeArena' /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/librbd.so: undefined reference toNSS_CMSSignedData_SignerInfoCount'
/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/librbd.so: undefined reference to SECITEM_FreeItem' /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/librbd.so: undefined reference toPK11_GetBestSlot'
/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/librbd.so: undefined reference to NSS_CMSDecoder_Finish' /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/librbd.so: undefined reference toSECMOD_RestartModules'
/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/librbd.so: undefined reference to `NSS_CMSSignedData_GetDigestAlgs'
collect2: error: ld returned 1 exit status

Hi @jupiturliu thanks for this report. I've been on vacation and can look at this now. How did you install Ceph (e.g. source, stable/dev?), and had you previously installed Ceph and/or go-ceph on the same machine? Since go-ceph just links against the C libraries, this doesn't appear to be a go-ceph issue, but it might be related to a missing library path.

Hi @noahdesu Happy new year. thanks for your reply. I am actually compiling the ceph by myself. Here is the scripts I created to compile Ceph @ https://github.com/omnicube/utils/blob/master/ceph_compiling.sh
I developed several features inside of Ceph. I just want to have a quick try with any example written in go. I do installed librbd and librados2 library. What else do I need to install? By the way, I am using Ubuntu 14.04.
thanks,
James

It seems like Ceph was compiled against libnss but that libnss (or a different version) was used when compiling go-ceph. I'll try to confirm this bug. Have you tried to compile go-ceph against Ceph installed from pre-built packages?

@noahdesu I did not get a chance to try pre-built ceph package. I will find a machine to have a try tonight if allowed.

@noahdesu with standard Ceph release,I  did not get this error.

Ok thanks for the update, that's good news. I looked at your script that compiles Ceph. Would you mind sending me the parameters you are using for configure? I built from source recently and everything worked for me so I am having a little trouble reproducing this. Can you compile other programs against librados or librbd? One thing that you might want to check is that cgo can find libnss. Perhaps libnss is installed in a path that cgo won't look for automatically.

@noahdesu  I just enabled rocksdb with ./configure --with-librocksdb-static. What kind of other programs I supposed to build. I do build fio with librbd support.  I am able to run the fio test with librbd engine against new ceph build.

@noahdesu I switched to another machine and tried to configure the ceph with like this one and see how it goes. ./configure --with-nss

@jupiturliu ok let me know how that goes. if that doesn't fix it, i will create post step-by-step instructions that works for me so you can compare and maybe we can narrow down where the problem is. thanks for  your patience.

@noahdesu
Just recompiled the code with ./configure --with-nss. I still did not get luck to make it work. Using ldd to check dependence of librbd that go-ceph rely on. I do see the my own build libraods was linked to librbd correctly.
ldd /usr/lib/librbd.so
linux-vdso.so.1 =>  (0x00007fff76ecb000)
librados.so.2 => /home/jamesliu/WorkSpace/ceph-install/lib/librados.so.2 (0x00007f8317a6a000)
libboost_thread.so.1.54.0 => /usr/lib/x86_64-linux-gnu/libboost_thread.so.1.54.0 (0x00007f8317839000)
libblkid.so.1 => /lib/x86_64-linux-gnu/libblkid.so.1 (0x00007f8317612000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f83173f4000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f83171ec000)
liblttng-ust.so.0 => /usr/lib/x86_64-linux-gnu/liblttng-ust.so.0 (0x00007f8316fa1000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f8316d9d000)
libboost_system.so.1.54.0 => /usr/lib/x86_64-linux-gnu/libboost_system.so.1.54.0 (0x00007f8316b99000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f8316894000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f831658e000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f83161c8000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f8315fb1000)
libcrypto++.so.9 => /usr/lib/libcrypto++.so.9 (0x00007f83158e6000)
libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x00007f83156e1000)
/lib64/ld-linux-x86-64.so.2 (0x00007f831c6de000)
liblttng-ust-tracepoint.so.0 => /usr/lib/x86_64-linux-gnu/liblttng-ust-tracepoint.so.0 (0x00007f83154c6000)
liburcu-bp.so.1 => /usr/lib/liburcu-bp.so.1 (0x00007f83152bf000)
liburcu-cds.so.1 => /usr/lib/liburcu-cds.so.1 (0x00007f83150b8000)
Whenever I removed my own built rados library in the library path and use standard one, everything works fine.
Pretty sure the problem come from ceph build.

Do you have multiple version of Ceph installed (e.g. one via a package
manager, and the one you built)? If so, does it work if you remove the one
that is installed via the package manager? It might be that there is cross
linking going on.
On Wed, Jan 6, 2016 at 5:10 PM, jupiturliu<EMAIL_ADDRESS>wrote:

@noahdesu https://github.com/noahdesu
Just recompiled the code with ./configure --with-nss. I still did not get
luck to make it work. Using ldd to check dependence of librbd that go-ceph
rely on. I do see the my own build libraods was linked to librbd correctly.
ldd /usr/lib/librbd.so
linux-vdso.so.1 => (0x00007fff76ecb000)
librados.so.2 => /home/jamesliu/WorkSpace/ceph-install/lib/librados.so.2
(0x00007f8317a6a000)
libboost_thread.so.1.54.0 =>
/usr/lib/x86_64-linux-gnu/libboost_thread.so.1.54.0 (0x00007f8317839000)
libblkid.so.1 => /lib/x86_64-linux-gnu/libblkid.so.1 (0x00007f8317612000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
(0x00007f83173f4000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f83171ec000)
liblttng-ust.so.0 => /usr/lib/x86_64-linux-gnu/liblttng-ust.so.0
(0x00007f8316fa1000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f8316d9d000)
libboost_system.so.1.54.0 =>
/usr/lib/x86_64-linux-gnu/libboost_system.so.1.54.0 (0x00007f8316b99000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6
(0x00007f8316894000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f831658e000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f83161c8000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f8315fb1000)
libcrypto++.so.9 => /usr/lib/libcrypto++.so.9 (0x00007f83158e6000)
libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x00007f83156e1000)
/lib64/ld-linux-x86-64.so.2 (0x00007f831c6de000)
liblttng-ust-tracepoint.so.0 =>
/usr/lib/x86_64-linux-gnu/liblttng-ust-tracepoint.so.0 (0x00007f83154c6000)
liburcu-bp.so.1 => /usr/lib/liburcu-bp.so.1 (0x00007f83152bf000)
liburcu-cds.so.1 => /usr/lib/liburcu-cds.so.1 (0x00007f83150b8000)
Whenever I removed my own built rados library in the library path and use
standard one, everything works fine.
Pretty sure the problem come from ceph build.
—
Reply to this email directly or view it on GitHub
https://github.com/ceph/go-ceph/issues/5#issuecomment-169514556.

@noahdesu It is likely, I will make sure the librbd and librados libary are from same sources. I will let you know soon.

Is this still an issue? I've not heard of this problem and haven't been able to reproduce it.

Hello, I'm automatically closing all issues filed prior to 2018 that have not been commented on recently. If this issue is still relevant to you please reopen the issue and restart the discussion. Thank you for your understanding.


[WIP] [Broken] Fixing parametricity for fixpoint

Please do not merge, the CI does not reflect the status of the PR.

@CohenCyril any news on this front?

@CohenCyril any news on this front?

no progress yet (just hours trials and errors that never succeeded because of the lack of debugging tools for De Brujin indices)

There's a printing function in extraction/test-suite/Test.v that could be migrated to Ast.term easily I guess. Just to be clear, you're debugging the implementation, not a proof about it, right? Also, a bit relatedly, @aa755 , we were trying to recall with @yforster what was the status of the Prop-parametricity work, you had the implementation in Coq but the proof on paper only, right?

The proof is on paper only, although I had sketched in Coq some cases of the lemma that says that substitution commutes with the translation. The Coq sketch was just to convince myself and not to claim as a contribution.


Exit with failure when cron classes can't be loaded

The runcrons command is meant to be run unattended, therefore when it can't run due to CRON_CLASSES being wrong, the exit status must be set to failure. Otherwise the only indication is the output, which is typically discarded by cron and similar tools.
The current behavior can lead to very dire effects of cron jobs not running with no failures recorded in CronJobLog.

Ping?

@koterpillar this makes sense and works for me 👍  Will add to PR for next version. Thanks!

Uncluttering my PRs.


Awkward workflow when a pipeline outputs incorrect data but doesn't fail. (Leads to people committing manually to an output repo)

Behavior
There is some reasonably confusing behavior that pops up if you commit manually to the output of a pipeline, where the output of that pipeline is the input to another pipeline.  Obviously, one might expect some weirdness here as it breaks some parentage and provenance things.
However, we should either disallow this type of manual commit or prevent the weirdness that results.  In particular, it seems like data that is manually committed to a pipeline's output disappears after that pipeline runs again "normally."
Steps to reproduce
Using the opencv demo, with the pipeline set up as follows:

Make the following three commits (one of which commits manually to the edges output of the edges pipeline):
➜  opencv git:(master) ✗ pachctl put-file images master -c -f liberty.jpg
➜  opencv git:(master) ✗ pachctl list-job
ID                                   OUTPUT COMMIT                            STARTED        DURATION           RESTART PROGRESS  DL UL STATE
04f61d86-37f9-4557-b864-6ea62ebf2b79 montage/fa51f7d39b14422ebc5d97b6f367bea5 50 seconds ago Less than a second 0       1 + 0 / 1 0B 0B success
cac0bbfb-b0f1-4361-bfe3-05800079f8ae edges/2bda1dd039e34ee49aa47eeb58ddf0b0   51 seconds ago 1 second           0       1 + 0 / 1 0B 0B success
➜  opencv git:(master) ✗ pachctl put-file edges master -c -f wrench.jpg
➜  opencv git:(master) ✗ pachctl list-job
ID                                   OUTPUT COMMIT                            STARTED            DURATION           RESTART PROGRESS  DL UL STATE
dcae456c-9225-4165-bb5c-99717fba5078 montage/aa7a0f1fe64a486a8a7ed5e35fffcdcc 4 seconds ago      Less than a second 0       1 + 0 / 1 0B 0B success
04f61d86-37f9-4557-b864-6ea62ebf2b79 montage/fa51f7d39b14422ebc5d97b6f367bea5 About a minute ago Less than a second 0       1 + 0 / 1 0B 0B success
cac0bbfb-b0f1-4361-bfe3-05800079f8ae edges/2bda1dd039e34ee49aa47eeb58ddf0b0   About a minute ago 1 second           0       1 + 0 / 1 0B 0B success
➜  opencv git:(master) ✗ pachctl put-file images master -c -f star_wars_kid.jpg
➜  opencv git:(master) ✗ pachctl list-job
ID                                   OUTPUT COMMIT                            STARTED            DURATION           RESTART PROGRESS  DL UL STATE
2e760b30-6b4d-468c-b719-df669e09a1fc montage/2f206dbbbc4c43d7a35b204b4ca32aac 9 seconds ago      Less than a second 0       1 + 0 / 1 0B 0B success
f2f3c790-eedd-4d93-824a-23fc883c1379 edges/c61260d4bd014960b27b84837a6ff2c4   10 seconds ago     Less than a second 0       1 + 1 / 2 0B 0B success
030f2676-ccb3-4662-9bf0-a532d0ae663d montage/678bbf77b0c64f50b93e61329b38b841 10 seconds ago     Less than a second 0       1 + 0 / 1 0B 0B success
dcae456c-9225-4165-bb5c-99717fba5078 montage/aa7a0f1fe64a486a8a7ed5e35fffcdcc 44 seconds ago     Less than a second 0       1 + 0 / 1 0B 0B success
04f61d86-37f9-4557-b864-6ea62ebf2b79 montage/fa51f7d39b14422ebc5d97b6f367bea5 About a minute ago Less than a second 0       1 + 0 / 1 0B 0B success
cac0bbfb-b0f1-4361-bfe3-05800079f8ae edges/2bda1dd039e34ee49aa47eeb58ddf0b0   About a minute ago 1 second           0       1 + 0 / 1 0B 0B success
➜  opencv git:(master) ✗

As can be seen, this results in four output commits in montage.  The four output commits look like the following:

Most of this makes sense in terms of non-transitive pipelines.  However, it is weird that the wrench disappears from the head of montage, and thus the head of edges:
➜  opencv git:(master) ✗ pachctl list-commit edges
REPO                ID                                 PARENT                             STARTED             DURATION             SIZE
edges               c61260d4bd014960b27b84837a6ff2c4   84eb3739aaa1410fac930bda8c340371   22 minutes ago      Less than a second   43.92KiB
edges               84eb3739aaa1410fac930bda8c340371   2bda1dd039e34ee49aa47eeb58ddf0b0   23 minutes ago      Less than a second   40.57KiB
edges               2bda1dd039e34ee49aa47eeb58ddf0b0   <none>                             24 minutes ago      Less than a second   22.22KiB
➜  opencv git:(master) ✗ pachctl list-file edges 2bda1dd039e34ee49aa47eeb58ddf0b0
NAME                TYPE                SIZE
liberty.png         file                22.22KiB
➜  opencv git:(master) ✗ pachctl list-file edges 84eb3739aaa1410fac930bda8c340371
NAME                TYPE                SIZE
liberty.png         file                22.22KiB
wrench.jpg          file                18.34KiB
➜  opencv git:(master) ✗ pachctl list-file edges c61260d4bd014960b27b84837a6ff2c4
NAME                TYPE                SIZE
liberty.png         file                22.22KiB
star_wars_kid.png   file                21.7KiB
➜  opencv git:(master) ✗

Talked about this offline with @JoeyZwicker. I think the easiest way to solve this is to prevent making commits to repos that don't have a provenant commit for each of the repo's provenant repos. That will make it substantially harder, although not impossible to commit directly to an output repo.

I've just discussed a workflow on Slack with @dwhitena where it would be useful to be able to manually commit to a repo that is normally the output of a pipeline, and then have downstream pipelines depending on that repo be triggered to run against those manually committed datums.
The issue is that we have a downstream pipeline run against an input repo vrt-dataset-rasters with a large number of datums (say 50,000) that have been generated by the upstream pipeline list-dataset-contents which fans out from one input datum.  The vrt-dataset-rasters pipeline ran successfully.  Subsequently, however, we discover that we need to re-run a few of those datums.    We obviously don't want to have to process all inputs to vrt-dataset-rasters again, and because the list-dataset-contents fans out we can't update its input to manipulate its output.  Therefore we copy the output datums that we're interested in reprocessing from list-dataset-contents and commit them to the master branch of that repo; we expect this to kick off  vrt-dataset-rasters to reprocess those new commits, only it doesn't.
The workaround I'm using after speaking to Daniel is to commit the datums for reprocessing to a new repo, and update the vrt-dataset-rasters pipeline to point to that instead of list-dataset-contents.  This works, but seems a bit more unwieldy in terms of workflow than it needs to be.  Unless I'm missing something...?

Committing to an output repo breaks a number of Pachyderms internal assumptions about how provenance works. That's the reason that it doesn't process the data, it has no provenance which Pachyderm uses to figure out what to process. The other big issue with committing to an output repo is that if new data comes into the input repo then the committed data is going to get overwritten which will lead to very confusing results. One fairly reasonable way to do this would be to have your pipeline take 2 inputs in a union, 1 being the output repo it already takes, the other being a side repo that you can commit raw data to. That way it'll be possible to easily add data.
Long term it would be nice if there was a way to force reprocessing on particular datums, it's not immediately obvious to me how that would work with our API but I think it should be possible to get it to work.

Thanks for the update @jdoliner and your suggestion for having the pipeline take to inputs in a union is a very good one - I'll go down that route!

Yeah, this cropped up again today in Slack:

still a little confused as to the best practice in the following scenario. Have a user trying to commit changes into the output of a pipeline stage b/c:

Dang, okay.  We caught an error in one of the files that we wanted to update.  The previous pipeline stage takes ~30 hours to run, and the way the glob patterns work from the initial repos would cause all of that to run again.  We were hoping to just manually fix and commit the file downstream so we wouldn't have to wait for all of the upstream pipelines to run again```

Does a manual commit to what is normally a pipeline-populated repository have to break assumptions around provenance? If one was looking for the provenance of something further downstream that depended on that manually-committed data, could the reporting/introspection tools be made to indicate that it traces back to a manual commit?
I'm not saying that isn't a ton of work, and it might not be at all worth it given what your goals for this tool are, but as an outsider it seems provenance-tracking need not be incompatible with this sort of workflow. After all, every commit to a top-level repository is a manual one.

@ClaytonJY manual commits to output repos break too many of our internal assumptions. Provenance is used to figure out which data should be processed together. For example if I have a DAG like this:
   B
  /  \
A     D
  \  /
   C

Pachyderm uses provenance to make sure that D will only process commits from C and B that came from the same commit to A. Without this you get a lot of user code which crashes because it expects to be able to match things between its 2 input commits. Worse, sometimes it gives wrong answers, such as numbers getting normalized to the [0,1] range and winding up outside the range because the max value you're using for normalization is the max value of a different commit. Allowing output commits would require, at the very least relaxing this safety, and possibly sacrificing it all together.
The other major issue with manually committing to output directories is that the data won't actually "stick". Output commits, unlike input commits, don't inherit content from their parents. Each time we build the commit from scratch by merging together the outputs of all the datums that were processed to create it. This is why deleting an upstream datum causes its output to disappear. If we wanted to be able to allow manual output commits and keep the ability to delete a datum we'd need someway to distinguish which data is actual "output" data and which data is "faux" output data so that we could preserve the latter and not preserve the prior. This opens up a whole can of worms, you could in theory have a file that's part real output and part faux output, you can get merge conflicts between the two.
So the tl;dr is that manual commits violate far too many of our assumptions to be workable. It's not so much the implementation work, although it would be a lot of work, but more the work required to figure out all of the corner cases in how the system should actually behave. I'm not fully convinced any amount of work would get us to a sensible set of semantics for manual output commits.

Closing in favor of #3773 which has a proposal for solving this type of issue.


Add MindMac - Feature-rich ChatGPT client for macOS

Hi @vitorgalvao, thank you for this great repo. I just added MindMac, a feature-rich ChatGPT client for macOS to use OpenAI API and other services. Please help to review this PR. Thanks!

Looks good. I can include the icon to the repo. Thank you.


Fix issue #529 Main-Class not found error in start-client.bat

Do other scripts face same problem?

I checked start-postBackClient.bat, start-server.bat, stop-postBackClient.bat, stop-server.bat for iotdb, and export-csv.bat, import-csv.bat, run-client.bat for iotdb-cli, they all executed normally.


change json schema version to fix unauthorised error

Fixes #421

Hooray Jenkins reported success with all tests good!


abcmidi: 2019.03.30 -> 2019.04.13

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/abcmidi/versions.
meta.description for abcmidi is: '"Utilities for converting between abc and MIDI"'.

Checks done (click to expand)

built on NixOS
/bin/sh passed the binary check.
1 of 1 passed binary check by having a zero exit code.
0 of 1 passed binary check by having the new version present in output.
directory tree listing: https://gist.github.com/dab1e551328d28b42948a07082922a81
du listing: https://gist.github.com/4e69b51a8d81e49ad7712a0ee44e8f90

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)
1 package rebuild(s)
1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
abcmidi

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/fsyfb7h9i2zrr38r18rrrz335a5s0las-abcMIDI-2019.04.13 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A abcmidi https://github.com/r-ryantm/nixpkgs/archive/e0716ed0edd940d55890484a52490fe3413ca1b9.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/fsyfb7h9i2zrr38r18rrrz335a5s0las-abcMIDI-2019.04.13
ls -la /nix/store/fsyfb7h9i2zrr38r18rrrz335a5s0las-abcMIDI-2019.04.13/bin

cc @dotlambda for testing.

I pushed ff26a24998eab85fd3083de9e44216c1fece9caf instead.


Update to cardano-api-<IP_ADDRESS> and cardano-cli

Description
Note, cardano-api-<IP_ADDRESS> doesn't exist yet, but will be published soon.
Checklist

[ ] Commit sequence broadly makes sense and commits have useful messages
[ ] New tests are added if needed and existing tests are updated.  These may include:

golden tests
property tests
roundtrip tests
integration tests
See Runnings tests for more details

[ ] Any changes are noted in the CHANGELOG.md for affected package
[ ] The version bounds in .cabal files are updated
[ ] CI passes. See note on CI.  The following CI checks are required:

[ ] Code is linted with hlint.  See .github/workflows/check-hlint.yml to get the hlint version
[ ] Code is formatted with stylish-haskell.  See .github/workflows/stylish-haskell.yml to get the stylish-haskell version
[ ] Code builds on Linux, MacOS and Windows for ghc-8.10.7 and ghc-9.2.7

[ ] Self-reviewed the diff

Note on CI
If your PR is from a fork, the necessary CI jobs won't trigger automatically for security reasons.
You will need to get someone with write privileges.  Please contact IOG node developers to do this
for you.

Currently, Hydra CI reports a compilation error for bech32-1.1.2. As a consequence of that error, the workbench shell can't be entered anymore.
On master the version seems to be resolved to bech32-1.1.3, which provides version bounds for its optparse-applicative dependency avoiding the compilation error.


[Feature][Zeta][REST-API] Stop a running job.

close #4417

Purpose of this pull request

Check list

[ ] Code changed are covered with tests, or it does not need tests for reason:
[ ] If any new Jar binary package adding in your PR, please add License Notice according
New License Guide
[ ] If necessary, please update the documentation to describe the new feature. https://github.com/apache/seatunnel/tree/dev/docs
[ ] If you are contributing the connector code, please check that the following files are updated:

Update change log that in connector document. For more details you can refer to connector-v2
Update plugin-mapping.properties and add new connector information in it
Update the pom file of seatunnel-dist

[ ] Update the release-note.

I found that the status of CI was not synchronized. @Hisoka-X

 it will update per 15 minutes.

I see.


Update Roslyn to 3.7

Fixes https://github.com/dotnet/aspnetcore/issues/21253 and https://github.com/dotnet/aspnetcore/issues/21470.

I think you'll need to call remoteClient.TryRunRemoteAsync<JObject> instead of remoteClient.TryRunRemoteAsync<TagHelperResolutionResult> and then Deserialize.


Apsim failed when resetting soil water

System.Exception: Error in file: C:\Data\Master\01Data\ApsimxFiles\LucerneValidation.apsimx Simulation: Iversen12SowingDateSD1 ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.NullReferenceException: Object reference not set to an instance of an object.
   at Models.WaterModel.WaterBalance.set_SW(Double[] value) in C:\Data\ApsimX\ApsimXLatest\Models\Soils\WaterModel\WaterBalance.cs:line 240

the manager works when providing values directly to it. but not via factorial.

Example of setting the manager correctly in factor node.


redo(ticdc): return ErrStorageInitialize if the external storage initialization fails

What problem does this PR solve?

Issue Number: close #xxx
What is changed and how it works?

return ErrStorageInitialize if the external storage initialization fails
Use a smaller DefaultTimeout, since changefeed will be restart when meet error.

Check List
Tests

Unit test
Integration test
Manual test (add detailed scripts or steps below)
No code

Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note
`None`.

/retest

/retest


🔧 [Refactor] Send coin also with float

🔧 Refactor ticket

Sending coins API call must also accept a float and not a string.

fixed in commit: https://github.com/gradido/gradido/pull/273/commits/db33e2a2df0cadc34b2ef8203a141362f3b2ca0f
in pr 273


Problem for moment2

 psOut.distMoments.x /= distWeightSum;     psOut.distMoments.y = psOut.distMoments.x * psOut.distMoments.x;
the moment2 is calculated by the square of moment1,but it should be the mean of the square.

Light leaking is always introduced if just use Chebyshev's Inequality, I'm also finding a method to progress on light leaking but until now I can't find a good method. Maybe use other shadowmap's method like ESM can help it.


Remove serde_codegen dependency on syntex

As suggesting in #50.

Hey, Ralph! Thanks for your continued work here; as before, I really appreciate it.
I actually just pushed #53 which updates all of the dependencies and (hopefully) resolves a number of other issues. Going to close this in favor of that. Sorry about the timing!


Call WI's conversion from model to to JSONAPI and back using the WI's type

In this PR I've changed the signature of the controller/ConvertWorkItem and controller/ConvertWorkItems function. They now accept the work item type of the work item that is supposed to be converted. The type itself is not yet used but it will in a future PR.
This is needed to support generic fields (see #2070).

Codecov Report

Merging #2069 into master will decrease coverage by 0.09%.
The diff coverage is 52.74%.

@@            Coverage Diff            @@
##           master    #2069     +/-   ##
=========================================
- Coverage   67.17%   67.08%   -0.1%
=========================================
  Files         157      157
  Lines       14189    14255     +66
=========================================
+ Hits         9532     9563     +31
- Misses       3762     3780     +18
- Partials      895      912     +17

Impacted Files
Coverage Δ

controller/workitem.go
78.33% <50%> (-3.17%)
:arrow_down:

controller/work_item_link.go
83.53% <50%> (-1.94%)
:arrow_down:

controller/search.go
71.92% <50%> (-2.17%)
:arrow_down:

controller/workitems.go
80.43% <57.14%> (-2.52%)
:arrow_down:

controller/planner_backlog.go
66.3% <71.42%> (+0.02%)
:arrow_up:

remoteworkitem/scheduler.go
60.97% <0%> (+7.31%)
:arrow_up:

remoteworkitem/jira.go
100% <0%> (+25%)
:arrow_up:

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 b42020a...9c03db1. Read the comment docs.

@kwk snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-2069-4

@kwk snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-2069-5

@kwk snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-2069-6

@kwk snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-2069-7


Normalize file paths in LocalFileTransferImpl to all start with file://

Ensure that the paths passed to URI and java.nio.file.Path are full valid file URI's starting with file:// and not nothing or or only file: which could cause issues.

Coverage decreased (-0.1%) to 88.644% when pulling 1014264e22b66e754862e9690b7eff6314f54a0a on tgianos:normalizePaths into 2fbf2112675ceb80b1a8adb298a36899389ff03f on Netflix:master.

Coverage decreased (-0.1%) to 88.644% when pulling 8b35bbe31c7294740cc94fe6d681a3ec2bb7b733 on tgianos:normalizePaths into 2fbf2112675ceb80b1a8adb298a36899389ff03f on Netflix:master.


docs: fix typo in saas.md

Docs: Fix typo and remove gender specific pronoun
Other minor formatting changes applied.
Definition of Ready

[x] I am happy with the code
[x] Short description of the feature/issue is added in the pr description
[x] PR is linked to the corresponding user story
[x] Acceptance criteria are met
[x] All open todos and follow ups are defined in a new ticket and justified
[ ] Deviations from the acceptance criteria and design are agreed with the PO and documented.
[x] No debug or dead code
[x] My code has no repetitions
[x] Critical parts are tested automatically
[x] Where possible E2E tests are implemented
[x] Documentation/examples are up-to-date
[x] All non-functional requirements are met
[x] Functionality of the acceptance criteria is checked manually on the dev system.

Thanks for fixing the typos here and in #6694 @paustint :pray:
Please reach out to<EMAIL_ADDRESS>if you'd like to have a small gift. We will send you a form with details about your shirt size, for example.


UglifyJS breaks with new module syntax

I'm submitting a bug report
Webpack version:
2.1.0-beta.25
Please tell us about your environment:
Linux x64
Current behavior:
I took a working project using the old module syntax (loaders/loader/query) and replaced it with the new syntax (rules/use/options) and I get the following error:
SyntaxError: Unexpected character '' [main.min.js:5429,52]`
Note that replacing the syntax (only those three words) is the ONLY change made.  Using the old syntax does not yield this error.
Expected/desired behavior:
The bundle would be generated and minified as it is using the old syntax.

Language: [ES6/7 | ES5]

Some plugins look in the wrong place for their options, especially if they were using the wrong API that just happened to work. You might need to use { loader: 'loader-name-loader', query: JSON.stringify({ your: 'options' }) } in some cases :(

I'm not sure that I follow.  If I'm trying to use the new module syntax can you give me an example of a working UglifyJS configuration?
The relevant parts of my webpack configuration (using the new syntax) are as follows:
module: {
  rules: [
    {
      test: /\.jsx?$/,
      include: path.join(__dirname, 'src'),
      exclude: /node_modules/,
      use: 'babel',
      options: {
        babelrc: false,
        cacheDirectory: PLATFORM === 'win32' ? true : '/tmp/',
        "presets": [
          "react",
          ["es2015", { "modules": false }],
          "stage-0",
        ],
        env: {
          development: {
            "plugins": [
              ["react-transform", {
                "transforms": [{
                  "transform": "react-transform-hmr",
                  "imports": ["react"],
                  "locals": ["module"]
                }, {
                  "transform": "react-transform-catch-errors",
                  "imports": ["react", "redbox-react"]
                }]
              }],
              "transform-runtime",
              "add-module-exports",
              "transform-class-properties"
            ]
          },
          production: {
            "plugins": [
              "transform-runtime",
              "add-module-exports",
              "transform-class-properties"
            ]
          }
        }
      }
    }
  ]
},
plugins: [
  new webpack.LoaderOptionsPlugin({ minimize: true, debug: false }),
  new webpack.optimize.DedupePlugin(),
  new webpack.optimize.UglifyJsPlugin({
    compress: {
      warnings: false,
    },
    output: {
      comments: false,
    }
  })
]

Just to make sure, works you need able to provide an example of the previous loader syntax you were using?

The only changes were using the new syntax (loaders -> rules, loader -> use, and query -> options).  Once I change it back to the following everything works again:
module: {
  loaders: [
    {
      test: /\.jsx?$/,
      include: path.join(__dirname, 'src'),
      exclude: /node_modules/,
      loader: 'babel',
      query: {
        babelrc: false,
        cacheDirectory: PLATFORM === 'win32' ? true : '/tmp/',
        "presets": [
          "react",
          ["es2015", { "modules": false }],
          "stage-0",
        ],
        env: {
          development: {
            "plugins": [
              ["react-transform", {
                "transforms": [{
                  "transform": "react-transform-hmr",
                  "imports": ["react"],
                  "locals": ["module"]
                }, {
                  "transform": "react-transform-catch-errors",
                  "imports": ["react", "redbox-react"]
                }]
              }],
              "transform-runtime",
              "add-module-exports",
              "transform-class-properties"
            ]
          },
          production: {
            "plugins": [
              "transform-runtime",
              "add-module-exports",
              "transform-class-properties"
            ]
          }
        }
      }
    }
  ]
},
plugins: [
  new webpack.LoaderOptionsPlugin({ minimize: true, debug: false }),
  new webpack.optimize.DedupePlugin(),
  new webpack.optimize.UglifyJsPlugin({
    compress: {
      warnings: false,
    },
    output: {
      comments: false,
    }
  })
]

Thank you very much. This should help me narrow down where this big may be hiding. cc @hzoo

@Kovensky are you thinking babel-loader is the problem here? Maybe just a bump in loader-utils I'll check the version for that package.

@TheLarkInn tried using options instead of query: JSON.stringify everywhere in my config -- at least svg-url-loader ("parseQuery should get a string as first argument") still crashes, but I couldn't reproduce it with my other loaders (eslint-loader, babel-loader, svgo-loader, style-loader, css-loader).
I should note that the only loader that behaved correctly in the beta.23 flag day was css-loader. Everyone else would crash if I didn't provide settings as query: JSON.stringify(options). They are probably working better now because I have nuked my node_modules since then, but it's a good idea to bump the minimum loader-utils version everywhere. npm won't know it needs to update the loader-utils sub-dependency if the current version still satisfies semver.

Could you show us your repository?

@abouthiroppy Is that question directed to me?  If so, this particular repo is a private project for a client that I can't share, but I might be able to put together a test repo at some point.

@dlong500 Yes.
OK,  I investigated this problem but couldn't cause an error so will write test codes.
FYI: https://github.com/issue-verifier/webpack2.1.0-verification

I might be able to put together a test repo at some point.

Thank you.  I will try to write a test code:)
I may ask you some questions if I cannot cause a problem :bow:

I don't know if it has any significance, but as mentioned in my original post the syntax error references a backtick.  I am using backticks (ES6 template literals) in a few places, so it might be good to add them to a test.

I got it. Thanks.

@dlong500 Would you try this code?
    new webpack.LoaderOptionsPlugin({
      minimize: true,
      debug: false,
      options: {
        babel: {
          babelrc: false,
          cacheDirectory: PLATFORM === 'win32' ? true : '/tmp/',
          "presets": [
            "react",
            ["es2015", { "modules": false }],
            "stage-0",
          ],
          env: {
            development: {
              "plugins": [
                ["react-transform", {
                  "transforms": [{
                    "transform": "react-transform-hmr",
                    "imports": ["react"],
                    "locals": ["module"]
                  }, {
                    "transform": "react-transform-catch-errors",
                    "imports": ["react", "redbox-react"]
                  }]
                }],
                "transform-runtime",
                "add-module-exports",
                "transform-class-properties"
              ]
            },
            production: {
              "plugins": [
                "transform-runtime",
                "add-module-exports",
                "transform-class-properties"
              ]
            }
          }
        }
      }
    }),

Are you saying to move the entire options tree to the LoaderOptionsPlugin like as below?
module: {
  rules: [
    {
      test: /\.jsx?$/,
      include: path.join(__dirname, 'src'),
      exclude: /node_modules/,
      use: 'babel'
    }
  ]
},
plugins: [
  new webpack.LoaderOptionsPlugin({
    minimize: true,
    debug: false,
    options: {
      babel: {
        babelrc: false,
        cacheDirectory: PLATFORM === 'win32' ? true : '/tmp/',
        "presets": [
          "react",
          ["es2015", { "modules": false }],
          "stage-0",
        ],
        env: {
          development: {
            "plugins": [
              ["react-transform", {
                "transforms": [{
                  "transform": "react-transform-hmr",
                  "imports": ["react"],
                  "locals": ["module"]
                }, {
                  "transform": "react-transform-catch-errors",
                  "imports": ["react", "redbox-react"]
                }]
              }],
              "transform-runtime",
              "add-module-exports",
              "transform-class-properties"
            ]
          },
          production: {
            "plugins": [
              "transform-runtime",
              "add-module-exports",
              "transform-class-properties"
            ]
          }
        }
      }
    }
  }),
  new webpack.optimize.DedupePlugin(),
  new webpack.optimize.UglifyJsPlugin({
    compress: {
      warnings: false,
      unused: true,
      dead_code: true,
      drop_console: true,
    },
    output: {
      comments: false,
    }
  })
]

Because I tried that and it worked.  I'm still a bit confused about the whole LoaderOptionsPlugin in general.  I think it's supposed to allow us to pass certain options to multiple loaders, right?  But it isn't supposed to replace the ability to pass options within the module tree, right?

Did I provide what you needed?  Do you need me to do any other tests?

I'm getting this error as well :( http://stackoverflow.com/questions/43683156/error-in-app-bundle-js-from-uglifyjs-unexpected-token-punc
I'm using es6 import/export and only webpack-dev-server or webpack -d --watch will work.
As soon as I try to minify the code using webpack -p it errors out.

Also getting this - although just started looking into it

I am getting this error as well. This just started today (6/7/2017):

@thoughtassassin - Did you find any solution to above error?

@thoughtassassin @abhinav-singi I have the same issue. Any news on your front?

I have a similar issue with UglifyJs and some postcss plugins  .. :(


Chapter is not viewing

Source information
Readwn
Steps to reproduce
1.Search for Villain: The charm is too high, and the heroine misunderstood the beginning
2.In this novel chapter is not showing
3.but in web view it is available
Expected behavior
Most of the novel's chapter can be viewed
Actual behavior
Like this some of the novel's chapter can't be viewed
LNReader version
1.1.14
Android version
Android 11
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
[X] I have written a short but informative title.
[X] I have updated the app to version 1.1.12.
[X] I have updated all installed extensions.
[X] If this is an issue with the app itself, I should be opening an issue in the app repository.
[X] I will fill out all of the requested information in this form.

Able to reproduce with chapters ~56 and lower on mentioned novel.


Cleanup error handling code.

This change makes cluster to retry command only in 2 cases:

network error
MOVED/ASK error response

Previously it retried on all error replies such as:
-ERR unknown command 'foobar'
-WRONGTYPE Operation against a key holding the wrong kind of value

etc
I took a chance to speedup isMovedError since it is called more often now.

/cc @dim

LGTM


Edit teams in settings window

The users can now edit their configured teams in settings window. I only tested it on windows. I also did changes on the UI for adding teams, because I think on this way it's much clearer how to add a team and how to edit a team. This related to #3.
npm testran successfully except this prettify. I don't know if I got it right, but I called the command npm run prettifyand I doesn't get an error there.
Cheers

Found that prettify thing by myself. Did some weird jsx-code there.

I forgot to put an image there how my changes looks like.

I found out that when I first edit a team and them add a new one, that I still edit the last selected team. The problem were the states. Hope that I get it right now.

Thanks! Just curious, is it possible to move '+' button to near the 'Team' label? For example, right of the label. The button is far from the label, so I think the user can't notice the button when adding a new team.
@CarmDam Could you complete Mattermost CLA?

yes i will move the button next to the label when i'm back home.
I did the mattermost cla as MetalCar @CarmDam is also my account. it seems that i pushed my last commit with the wrong github account

@yuya-oc Is this OK? Or should I place the button nearer to the Teams-Headline?

Looks better. Could you try resizing into narrow width?

Do you mean resize the complete window? Like that?

Sorry for few description, more narrow. I want to know whether Bootstrap correctly layouts the button in too narrow window (like mobile devices).

Ah, now I understand what you want. Hope when i push my changes, that all is OK....first time I used bootstrap with reactJS

Thanks. That looks OK!
Please let me confirm, you haven't pushed the change yet, right?

Yep, i will push it now.

This seems not to work correctly on OS X

Does this build fix problems?

I have tested this build on OSX, and the problem is gone

Thanks, I will merge later.

Thanks @magicmonty, @yuya-oc!!


Error reading message when receiving replies not sent in response to pingrs requests

start another pinging tool
launch pingrs
"Error reading echo reply packet"

Closed by commit 50dc1660ef030de9027e982396c4789726472a49


Stats inconsistency between membership_healthy and cluster health_flags

Stats inconsistency between membership_healthy and cluster health_flags
Description:
A change between bacaa4cdcbf94a8b110b783ae5e72cd2947a8432...5da782c8503aa2664ceac1995628d161bbaa6441 resulted in number of hosts at Lyft falsely reporting membership_healthy values as 0. We are running 5da782c8503aa2664ceac1995628d161bbaa6441.
When looking at the health_flags for a particular service we get:
tallen@jobschedulernormal-production-iad-0a352b11f4f80d603:~$ envoy-clusters | grep dborchestrator | grep health_flags
dborchestrator::<IP_ADDRESS>:9211::health_flags::healthy

However, at the same time we also see:
tallen@jobschedulernormal-production-iad-0a352b11f4f80d603:~$ envoy-stats | grep cluster.dborchestrator.membership_healthy
cluster.dborchestrator.membership_healthy: 0

This might have to do with https://github.com/envoyproxy/envoy/pull/5009, but we're not 100% sure at the moment. We're currently still investigating.

cc @rgs1

@tonya11en does it eventually converge?

@tonya11en quick way to test if it's #5009 would be by setting:
      common_lb_config:
        update_merge_window: 0s

@tonya11en these stats might be helpful:
cluster_updated
cluster_updated_via_merge
update_merge_cancelled
update_out_of_merge_window

https://github.com/envoyproxy/envoy/blame/master/docs/root/configuration/cluster_manager/cluster_stats.rst#L22

I am also wondering if the cluster is being frequently added/removed/added via CDS? Because if a cluster is removed, we cancel pending updates. If it's then immediately added again and its endpoints are populated from existing ones (because they haven't been drained yet), they could be stale...

FYI I looked at this a little bit and I'm doubtful update merging has anything to do with this, as update merging only prevents updates from going to the workers, it doesn't prevent updates on the main thread, which is where the stats are computed, AFAICT.
I do wonder if this is somehow due to hot restart and the old process writing 0 into the stat or something like that. I would try a fresh start also and see if it works then.

it correlated with the deploy of https://github.com/envoyproxy/envoy/compare/bacaa4cdcbf94a8b110b783ae5e72cd2947a8432...5da782c8503aa2664ceac1995628d161bbaa6441. though if it is a hot restart bug i guess it it could be due to the previous deploy's diff.

Yeah based on that diff, cluster merging does look very suspicious, though I don't see how it could cause the stat discrepancy. Admittedly, I did not look at the code for very long and maybe I am missing something. If we have a host that repros, can we check whether it happens every time? Does it happen without hot restart? Does turning off merging fix it?

I can think of two ways for this bug to happen:

we are failing to fire the merged updates (we'd know if the above stats — cluster_updated_via_merge, etc — are not being incremented)
addMemberUpdateCb is called, but prioritySet().hostSetsPerPriority() is not up to date: https://github.com/envoyproxy/envoy/blob/master/source/common/upstream/upstream_impl.cc#L536

Also, we've only used merged updates with the subset LB, which will reconstruct the hostSetsPerPriority on every HC change:
https://github.com/envoyproxy/envoy/blob/master/source/common/upstream/subset_lb.cc#L254
If other LBs rely on seeing every HC change to keep hostSetsPerPriority up to date, things won't work...

I just checked back on that same box and the stats fixed themselves. Looking for another instance of this.

I'm going to go ahead and close this out. Please reopen if we think there is an issue here and we have some more info.


Merge with react-aad-msal?

Hey! I'm currently one of the owners of the react-aad-msal library, which is also a React wrapper around MSAL. I had a lot of the same frustrations which led me to try to write my own wrapper until I saw a few people already doing something similar.
Looks our projects mostly do the same thing, but while we're farther along with the MSAL integration, we're missing a few of the Azure B2C features you have. Would you be interested in helping to migrate the features over and combine libraries? We can probably do most of the work if you could help identify the feature gaps...
The official Identity team at Microsoft has it in their roadmap to build an official React wrapper for MSAL at an unspecified time next year, but I'm hoping if the community can fill the gap they'll accept our solution as a sanctioned library well before then.

Happy to help, and I work at Microsoft so happy to ask around internally to see what's going on?

Hi, this sounds like a good idea to me as I’ve been trying to find a way forward for this library - I really don’t have time to maintain it but people use it. Even those efforts have been sporadic as a result.
I will try and take a look at your framework in the next week or two.
Thanks for reaching out.

This sounds great. I assume a lot of the functionality is already there, but I can probably better document how to achieve some of the specific functionalities that are built into your library very well. And I will be maintaining our library for some time as my team uses it for a number of applications.


Invalid arguments: "timeout" must be a number

Connection timeout field displays the above error even when the input is a number (both integer and float raise this error)

Which db connector are you using?

SQLServer

Have you been able to reproduce this with the sample data provided.  For example if you click on the SQLServer connector and then click on Sample Credentials.  Are you able to reproduce this error?  Can you provide the information you used.  It would help us test to determine what the issue is

I think i didn't describe the error well. Let me try again:
I am trying to connect to an SQLServer which generally takes a while to load even with other clients. So Falcons default  connection timeout of 15000milliseconds is too short. I tried to change this field using increment arrow and manual input. Both approaches lead to the error "Invalid arguments: "timeout" must be a number".

@Edsase I can't reproduce this issue (I even tried to edit %userprofile%\.plotly\connector\connection.yaml manually).
What value of connectTimeout are you using?
Did you get to save the connection? Assuming that you are on windows, a list of saved connections can be found in %userprofile%\.plotly\connector\connection.yaml (this a text file that can be opened with notepad).

Closing since it can't be reproduced and there hasn't been any recent activity.


Add support + examples for Helm v3

Proposal
Even with issue #121 on its way maybe consider add documentation and support for Helm v3. They have removed tiller so there are fewer security concerns involved.
Background
I'm just getting started with Kubernetes, Helm, Maesh... there is so much to read, so much to learn. It's all a little bit overwhelming, tbh.

Yeah, just as mentioned in #296


Preonic doesn't seem to use keymaps folder, probably need to indicate a folder per type

actually, IMHO we can enforce a folder hierarchy. To me that would be the
logical thing to do -- convention over configuration, so to speak.
Keyboards can conform to the structure as needed. Just my opinion. :)
On 31 October 2015 at 11:16, Tom de Grunt<EMAIL_ADDRESS>wrote:

—
Reply to this email directly or view it on GitHub
https://github.com/ErgoDox-EZ/reactor/issues/1.

@jackhumbert Is there any reason preonic's keymaps are stored in extended_keymaps?

Sorry - that project hasn't been updated entirely! The whole Preonic project should be similar to the Planck's.

@jackhumbert Want me to open an issue on qmk for this?

Nah, but it should definitely follow the same form as the Planck - it'll
get changed over once we start getting Preonic PCBs in.
On Mon, Jan 4, 2016 at 9:54 AM, Tom de Grunt<EMAIL_ADDRESS>wrote:

@jackhumbert https://github.com/jackhumbert Want me to open an issue on
qmk for this?
—
Reply to this email directly or view it on GitHub
https://github.com/ErgoDox-EZ/reactor/issues/1#issuecomment-168697489.

Allright, thanks. Closing this.


🛑 Example: Broken Site is down

In 21fc583, Broken Site (https://thissitedoesnotexist.com/) was down:
HTTP code: 0
Response time: 0 ms

test


Precalibrated projective camera

Firstly, a great library - thanks!
Is there any update on using a pre-calibrated projection camera (OpenCV calibration) ?
My aim is to recover the pose - like solvePnP in OpenCV ideally (although I am aware that there may be some issues with OpenGL coordinate system orientation).
So given that I know the camera parameters (fx, fy, cx, cy) and have also (radially) undistorted the images before feeding them into the pipeline, I would think this is an easier problem to solve, than when the camera is uncalibrated?
Has anyone managed to achieve this? I am not quite sure how/where to insert my intrinsic camera parameters. Do I need to use Ceres? Any help appreciated!
Thanks

@Andyjk1406 Hello, I would like to ask whether this project can achieve data enhancement? That is, I enter the 3D face data, he can change a variety of expressions such as angry sadness? I see in the function seems to be able to achieve but did not find an example or use the method.
I am very sorry for asking a question that is not related to your question here, but I really do not know who to ask, thank you very much

I'm going to close this, as there isn't really an issue with the eos library. Both the approach with Ceres as well as the approach by Hu et al. work quite well, just require a bit of implementation.
Feel free to re-open if any issue remains.


fixes ntrimmer bug basepair output growing in size

Problem was empty reads were causing ntrimmer to set rcut 1 on empty sequence making Read::getLengthTrue return 0-1 or max size_t.

This still doesn't address the issue of how the empty reads are getting output.

@msettles I recommend we merge this before making the change preventing trimming of all bases.


Support for bookmark linkback type

Tangentially related to https://github.com/pfefferle/wordpress-semantic-linkbacks/issues/75, but it appears that "mention", "like", and "reply" are supported natively, but not "bookmark"?
So for example, the comment display will default to X "mentioned" post  or Y "liked" post on service z, But would/could it say X "bookmarked" this post, particularly if the originating post had u-bookmark-of? I would presume that it would potentially have semantic_linkbacks_type be "bookmark" rather than "mention" or "reply" perhaps? And then that this could potentially be edited if the sending post wasn't carrying the correct mf2 class?
Example: http://boffosocko.com/2017/01/27/my-reply-to-micro-blog-project-surges-past-65k-on-kickstarter-gains-backing-from-dreamhost-wordpress-tavern/#comment-33624 which is a bookmark of the post technically rather than a simple mention, so it would be nice if it output "X bookmarked this post" in the comments in a parallel way as mentions and likes.

The plugin is supporting bookmarks in general, but not the version @aaronpk is publishing them. Is there a list of best practices?

Well, aaronpk documents his implementation pretty well.

I checked. My branch identifies this correctly.

Should be addressed by #85

This can be closed now.


Animation doesn't loop on React Native Web

Animations don't seem to loop properly on React Native Web. They are only being played once.

Hi @sreuter,
This is happening because react-native-web doesn't have "native driver" support.
I added web support in v1.5.0, please give it a try. Keep in mind that without native driver support, all animations run on the JS thread. So you might want to use SpinKit instead for better performance.

Hi @sreuter,
This is happening because react-native-web doesn't have "native driver" support.
I added web support in v1.5.0, please give it a try. Keep in mind that without native driver support, all animations run on the JS thread. So you might want to use SpinKit instead for better performance.

Aaaand.. it works, you're incredible :) Thanks @tienphaw !

Aaaand.. it works, you're incredible :) Thanks @tienphaw !


Support Data Import/Export

It would be nice to have the ability to export and import data 'dumps' from localForage. This would allow an entire storage instance to be moved between different environments in a standardised format.
This would also be useful when using localForage in testing environments to pre-seed the store with known data, making it trivial to construct test scenarios from an application. It could also be useful in allowing applications to 'sync' a backup of their settings to a server (note that real-time sync and equivalents are out of scope of this feature request).
#115 touched on this, but never made any progress before it was closed.

The reason that would be annoying to implement is localforage doesn’t actually keep track of all of your data (eg the names of the databases you’ve made, keys, etc). If you knew each dB you could iterate through the keys and export the data as JSON though. I don’t think it’s a candidate for a core feature (it’s useful, but a bit niche).
But a plug-in/extension that implemented that would be cool, for sure.
I think we wouldn’t do it in the core library though. I’ll close it here but if someone made a library that did this I’d happily add it to the README :-)

Side note: we could add the repo to the localForage organisation for extra visibility if someone was happy to maintain it 😊


[Feat] SmartStart support + Wider support for frameworks

Diving into this package and I have to say you all are doing wonderful work!!!!
Any timeline on the SmartStart support?

Hi @georgeinva2004,
Thanks for the kind words - @AlCalzone  and the team are certainly grateful.
I have a task to complete some updates on this package, I haven't touched it in a while (other project involvements).
with that said - I have a Branch I am working on, and will aim to get Smart Start supported, before its release.
As for timescales - I can't commit anything at this time - Sorry, but rest assured its on my radar.

One more ask :)  Would you consider multi-targeting this to .net Standard 2.0 to allow it to be used with other .NET frameworks?

Sure,
My 3.0 release will hopefully see a variance on the supported frameworks.

@georgeinva2004
An update for you, progress is being made to retarget this project to more frameworks.
I will be targeting NET45 and netstandard2.0
This should give good coverage, I can't go below 4.5, as I use some of its API's
(and of course they exist in  netstandard2.0)
Watch this space 👍

This is fantastic!!!  Thanks for making these changes...

I took a peek at the V3 build.  Things are looking great.  Haven't tried the SmartStart functionality yet, but it looks like you've made lots of progress.   Hopefully, you find this helpful, but I took the liberty of adding support for ZWaveMulticastGroups to the V2 branch.  I'm attaching the changed files to this message.  It was very straight forward to do thanks to your very clean architecture
MulticastGroupFiles.zip
.

Hi @georgeinva2004
I am due to release V3 (and the Toolkit demo) in the next few days (Evan soon maybe) 😃
I will look at the source you supplied now and will transpose it to V3 👍

@georgeinva2004
I have used your work to include Multicast Support - but its tied to the controller.
When using ZWave JS in its native form - you obtain the Multicast group from the controller.
https://zwave-js.github.io/node-zwave-js/#/api/controller?id=getmulticastgroup
So we will follow that (below) - My aim is to stick as close as possible to the ZWave JS API - meaning documentation it provides, can be used for .NET
VirtualNode VN = _Driver.Controller.GetMulticastGroup(new int[] { 2,3,4,6,7});
VN.GetDefinedValueIDs();
VN.GetEndpointCount();
VN.SetValue();
VN.SupportsCCAPI();
VN.InvokeCCAPI();

Thanks for the contribution - and watch this space for a release 😅

Good point.  Thanks for fixing it...

@georgeinva2004
https://github.com/zwave-js/ZWaveJS.NET/tree/v3.0#network-toolkit-demo-application
I will be releasing V3 this evening 😬

V3.0.0 is now available via nuget
https://github.com/zwave-js/ZWaveJS.NET/releases
Toolkit demo is attached to the release on GitHub.


Does anybody have a devspace.yaml Go project example?

I guess the title is enough.
/kind feature

@kickthemooon thanks for creating this issue! We have an example golang project or if you want to see a real life project, you can take a look at https://github.com/loft-sh/vcluster or https://github.com/loft-sh/jspolicy that are both golang projects and use devspace


encoding into more than 8 bits

I would like to encode a value into 11 bits in a CAN frame. It seems like there is an overflow condition or something similar that is happening and I am not able to stuff these into required bits. Is there a limitation of this repo that would prevent me from encoding to more than 8 bits?

Hi, the library should definitely work for values over 8 bits, look at the tests. What case is not working for you? Could you provide an example?

Can I mark this issue al resolved?


Make IoVecBuf traits more generic

related: https://github.com/bytedance/monoio/issues/53

 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.

Sorry for late checking it because this PR not merged for very long and I used to ignore it...
Do you still have interesting in merging it? I think it is more generic to make bytes buffer as a B, we can use something like Bytes with this ability. But to keep it compatiable, maybe adding a default type Vec to B is better.
Sorry for no responding again. If you are interested, please reopen it or open another PR, thanks!


ARROW-12619: [Python] pyarrow sdist should not require git

There is a fallback_version configuration option for setuptools_scm which we don't use: https://github.com/pypa/setuptools_scm#configuration-parameters
Although this setting seems to have issues according to https://github.com/pypa/setuptools_scm/issues/549
We already have a workaround in setup.py for the functionality of the fallback_version option, but it is disabled for the case of sdist: https://github.com/apache/arrow/blob/master/python/setup.py#L529

@github-actions crossbow submit python-sdist wheel-*
Still need to verify this locally.

I'm updating the sdist build to check the tarball without git installed.

@github-actions crossbow submit python-sdist
This should test the produced source tarball in a git-less environment.

The produced artifacts are here https://github.com/ursacomputing/crossbow/releases/tag/actions-415-github-java-jars

The macOS wheel builds are failing due to network timeout.


fatal error: failed to place: placed 0 PLLs of 1 / 2

Hi there, hope this is the right place to post this issue.
I'm using the ice40 8k fpga and the toolchain described by @cliffordwolf.
In my project I'm using SB_IO (for bidirectional port pins on some SRAM) and SB_PLL blocks (for a fast DVID clock).
arachne-pnr fails with the above error, and the line in arachne-pnr that is failing is
https://github.com/cseed/arachne-pnr/blob/master/src/pcf.cc#L283
It is the first clause (D_IN_0 is connected) that is true and causing the fail.
I tried making an MVP to show the issue but removing unrelated parts of the project also 'fixed' it. So I have left the project as is and pushed my development branch: https://github.com/mattvenn/fpga-virtual-graf/tree/blackice
I'm a beginner with FPGAs, but my guess is that the PLL has limited options for its connectivity and these have already been used by other parts of the project. Is there a way to choose to instantiate the other PLL the 8k device has? Or am I completely wrong here.
If there is any other information needed please ask.

Hi @mattvenn
Could you please give me the exact part of the HDL code which fails and how to reproduce it?, I've followed your git repo but is hard for me to understand, in few minutes, all the work you have been done until now.
Also, this is a very useful way to catch the attention from someone else for look into your issue :)

I'll have another go at making something. The problem I had was when I
started removing 'unrelated' parts to make a simpler demo of the problem,
the problem would disappear as well. Which is why I posted a link to the
whole unwieldy repo - sorry.
Matt
On 25 June 2017 at 04:18, dh73<EMAIL_ADDRESS>wrote:

Hi @mattvenn https://github.com/mattvenn
Could you please give me the exact part of the HDL code which fails and
how to reproduce it?, I've followed your git repo but is hard for me to
understand, in few minutes, all the work you have been done until now.
Also, this is a very useful way to catch the attention from someone else
for look into your issue :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/cseed/arachne-pnr/issues/64#issuecomment-310877601,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAmtbOTcFean1Rt6YHg_hXMSVgLOwly8ks5sHcOTgaJpZM4NvyNO
.

--
Matthew Venn
web mattvenn.net twitter @matthewvenn https://twitter.com/matthewvenn

new thread on the mystorm forum implies this could actually be a hardware issue
https://forum.mystorm.uk/t/placement-conflict-between-sb-io-for-ram-and-pll/224

There is a whole range of things wrong with this design:

When a PLL is enabled than the two IO pins on the corresponding IO blocks can only be used as PLL inputs or output-only. (That's why those pins are used for the LEDs on the icoboard: LEDs are output-only.) This is the issue discussed on the mystorm forum.

When you drive a PLL from the neighboring IO PAD you need to use SB_PLL40_PAD, SB_PLL40_2_PAD, or SB_PLL40_2F_PAD, not one of the _CORE variants.

When you are using a _PAD PLL variant and you also need the source clock in the design, then you need to route the source clock through the PLL using the SB_PLL40_2_PAD primitive.

The following patch to the design makes make i2c.bin run through. Of course, the design won't really work because I had to disconnect DAT[3] from IO pin 128.
diff --git a/blackice.pcf b/blackice.pcf
index 61ccad6..b0623ec 100644
--- a/blackice.pcf
+++ b/blackice.pcf
@@ -131,7 +131,7 @@ set_io --warn-no-port ADR[17] 78
 set_io --warn-no-port DAT[0] 135
 set_io --warn-no-port DAT[1] 134
 set_io --warn-no-port DAT[2] 130
-set_io --warn-no-port DAT[3] 128
+#set_io --warn-no-port DAT[3] 128
 set_io --warn-no-port DAT[4] 125
 set_io --warn-no-port DAT[5] 124
 set_io --warn-no-port DAT[6] 122
@@ -150,7 +150,7 @@ set_io --warn-no-port RAMWE 120
 set_io --warn-no-port RAMCS 136

 ## Onboard 100Mhz oscillator
-set_io --warn-no-port clk 129
+set_io --warn-no-port clk_pin 129
 set_io --warn-no-port LED[0] 71 #LD4,!SS,p14_1
 set_io --warn-no-port LED[1] 67 #LD3,MISO,p14_2
 set_io --warn-no-port LED[2] 68 #LD2,MOSI,p14_3
diff --git a/i2c.v b/i2c.v
index f8d052c..bd33c04 100644
--- a/i2c.v
+++ b/i2c.v
@@ -4,7 +4,7 @@
 `define pll_fail2
 `define pll_fail3
 module top (
-	input  clk,
+	input  clk_pin,
 	output [0:3] LED,
     output pixartclk,
     output pixart_reset,
@@ -19,6 +19,7 @@ module top (
     output RAMCS,
     output [31:0] PMOD
 );
+    wire clk;

     reg cam_clk;
     reg i2c_start = 1;
@@ -47,9 +48,9 @@ module top (
     );
 `ifdef pll_fail3
     //PLL details http://www.latticesemi.com/view_document?document_id=47778
-    SB_PLL40_CORE #(
+    SB_PLL40_2_PAD #(
         .FEEDBACK_PATH("SIMPLE"),
-        .PLLOUT_SELECT("GENCLK"),
+        // .PLLOUT_SELECT("GENCLK"),
         .DIVR(4'b1001),
         .DIVF(7'b1100100),
         .DIVQ(3'b011),
@@ -58,8 +59,9 @@ module top (
 //        .LOCK(lock),
         .RESETB(1'b1),
         .BYPASS(1'b0),
-        .REFERENCECLK(clk),
-        .PLLOUTCORE(clkx5)
+        .PACKAGEPIN(clk_pin),
+        .PLLOUTCOREA(clk),
+        .PLLOUTCOREB(clkx5)
     );
 `endif
   wire clkx5;

Alternatively we use the PLL on the other side of the chip. In this case we have to route the clock through the chip. For this we leave the Verilog design unchanged and use the SB_PLL40_CORE primitive, but we have to get rid of the assignment for pin 49 because this pin can not be used as input pin when the PLL on the other side of the chip is active:
diff --git a/blackice.pcf b/blackice.pcf
index 61ccad6..5354cdf 100644
--- a/blackice.pcf
+++ b/blackice.pcf
@@ -141,7 +141,7 @@ set_io --warn-no-port DAT[9] 60
 set_io --warn-no-port DAT[10] 56
 set_io --warn-no-port DAT[11] 55
 set_io --warn-no-port DAT[12] 52
-set_io --warn-no-port DAT[13] 49
+# set_io --warn-no-port DAT[13] 49
 set_io --warn-no-port DAT[14] 48
 set_io --warn-no-port DAT[15] 47

Closing this issue because afaict there is nothing wrong with arachne-pnr here.

Thanks Clifford. I don't fully understand your comments above, but it appears to me that this means the mystorm board can't work with its on board SRAM and a PLL. This is because both PLLs use pins that are already used by the SRAM's IO pins.
Matt

Yes, this is correct. You could use one PLL and only use 15 RAM bits (or both PLLs and only use 14 RAM bits). But that might be pretty inconvenient for many applications..

Thank you Clifford.
On 23 August 2017 at 12:55, Clifford Wolf<EMAIL_ADDRESS>wrote:

Yes, this is correct. You could use one PLL and only use 15 RAM bits (or
both PLLs and only use 14 RAM bits). But that might be pretty inconvenient
for many applications..
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/cseed/arachne-pnr/issues/64#issuecomment-324294118,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAmtbF1ws5hYzM78WrG_TH63HOckUaF0ks5sbAUSgaJpZM4NvyNO
.

--
Matthew Venn
web mattvenn.net twitter @matthewvenn https://twitter.com/matthewvenn


Handle fractional mouse wheel movements

This fixes https://bugs.openmpt.org/view.php?id=1638

Closing due to a different solution being implemented in ea49fa2b563bf983c6fa4e0944e74a364d7a7977.


Create user/pass authentication that only allows admin users to perform actions

Completed by https://github.com/thiagoesteves/deployex/pull/49


WIP: MLServerPCPredictor

MLServerPCPredictor implements PowerConsumptionPredictor interface, backed by MLServer.
It sends requests to MLServer like:
curl http://localhost:8080/v2/models/model1/versions/v0.1.0/infer \
  -H "Content-Type: application/json" \
  -d '{"inputs":[{"name":"predict-prob","shape":[1,3],"datatype":"FP32","data":[[10.0,22.0,0.2]]}]}'

It parses responses from MLServer like:
{
  "model_name": "model1",
  "model_version": "v0.1.0",
  "id": "0dc429d2-bd02-404b-b624-a0fa628e451e",
  "parameters": {
    "content_type": null,
    "headers": null
  },
  "outputs": [
    {
      "name": "predict",
      "shape": [
        1,
        1
      ],
      "datatype": "FP64",
      "parameters": null,
      "data": [
        94.76267448501928
      ]
    }
  ]
}

Codecov Report

Merging #1 (cd58383) into main (e5b71aa) will decrease coverage by 3.33%.
The diff coverage is 34.78%.

@@            Coverage Diff             @@
##             main       #1      +/-   ##
==========================================
- Coverage   80.52%   77.19%   -3.34%
==========================================
  Files          12       12
  Lines         832      899      +67
==========================================
+ Hits          670      694      +24
- Misses        127      170      +43
  Partials       35       35

Impacted Files
Coverage Δ

pkg/estimator/predictor_pc.go
43.02% <34.78%> (-25.40%)
:arrow_down:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Run nightly tests to catch URL moves and out-of-date artifacts

I've configured the Travis job to rebuild master nightly.

I've configured the Travis job to rebuild master nightly.

Interesting. How/where did you do it? Is there a doc?

Also, will we notified if the nightly builds fail?

This should also help us catch the sdk breakages.

Go to the Travis page and open More options > Settings and look at the bottom for Cron Jobs.

close as not planned