Add as_dict() function to print configuration

As discussed with @r39132.
Also moves two methods for getting dynamic options (env vars & commands) into their own functions in case we want to reuse them in the future.

Is it normal for landscape-bot to report on cli.py, since I didn't touch that file?

Coverage decreased (-0.1%) to 66.258% when pulling 32b6ea32619cb76491d36c4e25c576dd44ef3407 on jlowin:extend-config into 58df89f32ee46690e45923e698b71c9f6c7bffe4 on airbnb:master.

I think it's because you haven't rebased.

Coverage decreased (-0.3%) to 66.104% when pulling 9f1c9f81ccab9a03393257e966336502d31b5cb8 on jlowin:extend-config into 7a632e2ed81c442510c2785464519c32182edfe3 on airbnb:master.

Coverage decreased (-1.1%) to 65.266% when pulling 9f1c9f81ccab9a03393257e966336502d31b5cb8 on jlowin:extend-config into 7a632e2ed81c442510c2785464519c32182edfe3 on airbnb:master.

Coverage decreased (-0.3%) to 66.104% when pulling dd1877c7fc13dedccd89ea00fc983b32d2689f51 on jlowin:extend-config into 7a632e2ed81c442510c2785464519c32182edfe3 on airbnb:master.

@mistercrunch I'm not very familiar with coveralls, is there anything I can do about the failure here? It's saying none of the new code is tested but of course it is in the unit test.

Coveralls isn't happy because the new code you wrote isn't covered by tests and overall brings the coverage of the repository down. You should write a unit test that calls the method.
Landscape is reporting 14 things to lint as well. I think we should have PR authors fix most if not all of those. We can change the policy and specify rules we want to skip in .landscape.yml
You can disregard the complexity warnings (too many statements, or too many local variables) where you  didn't generate the complexity, though refactoring out some complexity is nice to do while you're in there.
I picked the landscape rules based on where I'd like to the repo to go towards, we could have a committer conversation if people disagree with some of these rules.

Ahhh, I'm dumb. I thought putting a file in the tests folder was enough to run the tests -- but I think it needs to be imported as well. Making that adjustment now, which should satisfy coveralls, because the method is definitely well tested!

Coverage increased (+0.1%) to 66.476% when pulling 940d788ca2c7499db481cce015c67610ad6176a0 on jlowin:extend-config into b95e26c795d9897fe9af3a4c38f77a9821309d01 on airbnb:master.

Coveralls and landscape are great, it just takes a bit of getting used to. Please take a look at the landscape link that says "14 new problems were found " and fix the things you think are reasonable.
I personally like PEP8 and would like to enforce it. Maybe not all PRs need to be 100% perfect but we should make sure that they leave the repo in a better state.

Coverage increased (+0.09%) to 66.472% when pulling 44c49ba0b5b2f4880662d7bb610f6d95c85ed9fa on jlowin:extend-config into b95e26c795d9897fe9af3a4c38f77a9821309d01 on airbnb:master.

One last nitpick ;-) please squash your commits and then let's merge!

@bolkedebruin do you prefer unit tests squashed with the functional code, or two commits (one for functionality, one for tests)

Coverage increased (+0.1%) to 66.552% when pulling a296cca03b88518d72cda2072be276c4e83c779c on jlowin:extend-config into 1db892b36d789d34facbb78e92c74dd3d34d4ee2 on airbnb:master.

@bolkedebruin all set.


Refactor build system to support Modrinth tweaks [v2]

After experimenting with this in #123, helpful insight from @wagyourtail which highlighted fundamental flaws in that initial approach, and plenty of assistance from @Juuxel in understanding loom's quirks, I'm ready to open this draft and begin iterating towards something we can call "done".
Note: until #130 is resolved, I'll avoid implementing the modrinth-specific tooltips.
Alternatively, we could write a config entry transformer which provides a different tooltip depending on the variant.
TODO

[x] Build an additional modrinth "variant" for each platform.
[x] Provide a run config for the variant.
[x] Build different metadata (mods.toml, fabric.mod.json) for each variant.
[x] Write a "normal" and "modrinth" service provider.
[x] Have each variant depend on the appropriate Service Provider implementation.
[x] Have config tooltips/descriptions be different for each variant:
[x] Add a VariantTooltip annotation where count can be declared for each variant.
[x] Write a config entry gui transformer similar to the default Tooltip transformer.
[ ] Ensure production builds work correctly.
[ ] Refactor the forge/fabric variant-specific gradle code into a shared "variant" plugin.

This PR supersedes #123.

@hashalite this is ready for review.
The first 6 commits are cherry-picked from #122. This PRs actual changes are from c0e936965fe2167f9c8717c0d60a3ddb6454e508 onward.
I ended up going with a fairly simple VariantTooltip AutoConfig GUI transformer so that this PR isn't blocked by #130. This also lessens the need for #130.
I'm a little unhappy with how much duplicated code there is across forge/build.gradle & fabric/build.gradle. This could be improved by introducing a custom gradle plugin that handles the variant stuff.
That said, the PR is technically complete, so I figured I'd ask for your thoughts & review.

Hey, thanks again for putting in the effort to do this. The number of branches was really getting out of hand :)
When running from my IDE, everything appears to work flawlessly. However, the jars produced all crash with varying errors when launched externally. Here are the errors I received:
fabric:
https://pastebin.com/mGDs7Hp5
fabric-modrinth:
https://pastebin.com/YBPYA5AJ
forge:
https://pastebin.com/XKtYHHP1
forge-modrinth:
https://pastebin.com/zXcWENGn
Could I be doing something incorrectly? I am simply running gradle :fabric:build and gradle :forge:build

Oops, knew I should've checked prod builds...
Looks like I'm not shadowing the dependencies correctly so some stuff is missing from the jar;
Variant is missing for normal builds and the freecam classes seem to be missing for modrinth builds.
I'll look into it when I get chance, but should be fairly simple 🤞
In the mean time any other questions or review points are welcome 😅

@hashalite the latest force-push should fix everything. :crossed_fingers:

shadowJarTask needed to use both the main & variant source sets
shadowJarTask needed to use the jar manifest that loom adds to the normal jar task.
Needed to explicitly shadow :variant:api because it being a dependency of the implementation wasn't enough for it to get shadowed.

I also dropped the Behavior class for now. That refactor felt a little out-of-scope for this PR and also kinda half-baked.

Another thing: it seems like the access widener for renderShadows is not working in the production builds. It crashes with the following error when Freecam is toggled:
java.lang.IllegalAccessError: class net.minecraft.client.renderer.entity.EntityRenderer tried to access private field net.minecraft.client.renderer.entity.EntityRenderDispatcher.f_114368_

Good catch.
Is that just forge or fabric too? Normal and Modrinth variants?
Fabric should just use the AccessWidener, but for forge it's supposed to be translated into Access transformer syntax.

It appears to happen with all versions except the regular forge build, strangely

One other nit-picky request: is there any way we could stop the empty freecam--<IP_ADDRESS>+1.x.x and freecam--<IP_ADDRESS>+1.x.x-sources jars from being generated in the root build directory when :build is run? They don't appear to be necessary (correct me if I'm wrong)

I have just migrated the project over to official mappings, hopefully the conflicts will not be too difficult to resolve

it seems like the access widener not working in the production builds. It crashes when Freecam is toggled
It appears to happen with all versions except the regular forge build, strangely

That is strange... I'll investigate shortly. May have to ask in the architectury discord again.

is there any way we could stop the empty [root project] jars from being generated when :build is run?

Yes, was planning to do this actually.  tasks.jar.enabled = false should work, just need to check it won't break subprojects running their tasks too.

I have just migrated the project over to official mappings, hopefully the conflicts will not be too difficult to resolve

Should just be able to do ./gradlew migrateMappings –mappings "net.mojang.minecraft:mappings:1.20.4" on each commit.
Might make a PR adding a Parchment layer to the mappings, if you don't beat me to it. Would be nice to have the javadocs & parameter names.
Should just be add their maven & then:
mappings loom.layered() {
    officialMojangMappings()
    parchment("org.parchmentmc.data:parchment-1.20.2:2023.12.10@zip")
}

Hopefully their 1.12.2 layer (latest) still works ok on 1.12.4 🤞

it seems like the access widener not working in the production builds. It crashes when Freecam is toggled
It appears to happen with all versions except the regular forge build, strangely

Figured out the issue, but still unclear on the solution.
There's two things going on here.
Fabric
On fabric, architectury is supposed to add the accessWidener entry in architectury.common.json to fabric.mod.json, however because we're building the mod metadata in :metadata now, this doesn't happen.
Forge
On forge, Architectury is supposed to remove all AccessWideners from the build and use their content to generate a META-INF/accesstransformer.cfg. This is happening, but only for the default build variant. Architectury doesn't know about our modrinth build.

This should be all fixed now. I've tested the modrinth variant in both forge & fabric. Toggling works normally.
I still need to rebase this on main & fix conflicts, however I'm running into issues with migrateMappings... Not sure if its a loom bug or an issue on my end: https://github.com/architectury/architectury-loom/issues/188

I'm running into issues with migrateMappings... Not sure if its a loom bug or an issue on my end

I think it may be an issue on your end, I was able to run the same command yesterday without issue

Strange. Just tried a second machine - same issue. Wiping cache doesn't help either.
Maybe OS specific? Might try in a VM if I get chance :thinking:
If  migrateMappings still works for you, you could push a commit  to this branch converting to 1.20.2 mappings. I should be able to use that as a reference for a manual rebase.

If migrateMappings still works for you, you could push a commit to this branch converting to 1.20.2 mappings

Done! Although the mixins still need to be fixed since they aren't migrated automatically

If migrateMappings still works for you, you could push a commit to this branch converting to 1.20.2 mappings

Done!

Thanks. The rebase ended up being simpler than I was expecting. The mappings only really affected ConfigExtensions (Text -> Component).
1.20.4 forge dev runs are still broken, so its harder to test this PR now, but it was working fine before rebase so should be ok... Only seen one mention of a similar issue in the architectury discord, so other people may be unaffected :thinking:
Tested prod builds again, everything seems to be working.

The rebase ended up being simpler than I was expecting.

Glad to hear it!
Will test further and get merged asap.
Thanks again, and merry xmas!

Thanks again, and merry xmas!

Merry Christmas to you too :christmas_tree:


⚠ Bofrost.at has degraded performance

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

HTTP code: 200
Response time: 3079 ms

Resolved: Bofrost.at performance has improved in 650f743 after 6 minutes.


Fix for binary glTFs storing CRN and KTX textures

Bug report and fix from the forum, with some modifications: https://groups.google.com/forum/#!topic/cesium-dev/02M8ho6hONo.

@lilleyse thanks for the pull request!
I noticed that a file in ThirdParty/ or Source/ThirdParty/ has been added or modified. Please verify that it has a section in LICENSE.md and that its license information is up to date with this new version.  Once you do, please confirm by commenting on this pull request.
I am a bot who helps you make Cesium awesome! Thanks again.

Does this need new unit tests?

Improved the tests a bit. They were able to pass before because the default texture was being used.

Are these CI failures related?
  Core/sampleTerrain
    ✗ queries heights from Small Terrain
	Expected undefined to be greater than 5000.
	    at Specs/Core/sampleTerrainSpec.js:42:41
	    at Promise.then (Source/ThirdParty/when.js:196:34)
	    at Source/ThirdParty/when.js:297:13
	    at processQueue (Source/ThirdParty/when.js:647:4)
	    at _resolve (Source/ThirdParty/when.js:333:4)
	Expected undefined to be less than 10000.
	    at Specs/Core/sampleTerrainSpec.js:43:41
	    at Promise.then (Source/ThirdParty/when.js:196:34)
	    at Source/ThirdParty/when.js:297:13
	    at processQueue (Source/ThirdParty/when.js:647:4)
	    at _resolve (Source/ThirdParty/when.js:333:4)
	Expected undefined to be greater than 5000.
	    at Specs/Core/sampleTerrainSpec.js:44:41
	    at Promise.then (Source/ThirdParty/when.js:196:34)
	    at Source/ThirdParty/when.js:297:13
	    at processQueue (Source/ThirdParty/when.js:647:4)
	    at _resolve (Source/ThirdParty/when.js:333:4)
	Expected undefined to be less than 10000.
	    at Specs/Core/sampleTerrainSpec.js:45:41
	    at Promise.then (Source/ThirdParty/when.js:196:34)
	    at Source/ThirdParty/when.js:297:13
	    at processQueue (Source/ThirdParty/when.js:647:4)
	    at _resolve (Source/ThirdParty/when.js:333:4)

https://travis-ci.org/AnalyticalGraphicsInc/cesium/builds/266571774?utm_source=github_status&utm_medium=notification

It also fails on master locally, so not related.

Congratulations on closing the issue! I found these Cesium forum links in the comments above:

https://groups.google.com/forum/#!topic/cesium-dev/02M8ho6hONo

If this issue affects any of these threads, please post a comment like the following:

The issue at https://github.com/AnalyticalGraphicsInc/cesium/pull/5753 has just been closed and may resolve your issue. Look for the change in the next stable release of Cesium!
Or get it now in the master branch on GitHub https://github.com/AnalyticalGraphicsInc/cesium

I am a bot who helps development running smoothly! Have a great day.


From network B to network A everything is ok, but from A to B only ping and traceroute work

I have a very specific problem:
Network A (external network: <IP_ADDRESS>/24) and network B (my home network: <IP_ADDRESS>/24) are connected via two peers (2x Raspberry Pi 4) via Netbird. I can access all clients on external network A from my home network B. The peer in network A routes all requests correctly to the clients in the network and I can access the WebUI of various clients in this network.
If I am now connected over Wifi to network A and want to access devices located in home network B, only ping and traceroute commands works. The routing etc. all seems to work, because I can ping the devices and traceroute to the devices also works. But I still can't establish an SSH connection to clients in network B, no matter which target device I have. I also cannot access the WebUI from any client in network B. But as i said, ping and traceroute are always working.
Maybe my problem is related to this:
https://github.com/netbirdio/netbird/issues/743
Peers:
Network A - <IP_ADDRESS>
Network B - <IP_ADDRESS>

Traceroute from Network B to Network A:
❯ traceroute <IP_ADDRESS>
traceroute to <IP_ADDRESS> (<IP_ADDRESS>), 64 hops max, 40 byte packets
 1  <IP_ADDRESS> (<IP_ADDRESS>)  3.522 ms  2.179 ms  2.177 ms
 2  <IP_ADDRESS> (<IP_ADDRESS>)  2.513 ms  3.283 ms  2.551 ms
 3  <IP_ADDRESS> (<IP_ADDRESS>)  81.484 ms  68.183 ms  63.558 ms

Traceroute from Network A to Network B:
❯ traceroute <IP_ADDRESS>
traceroute to <IP_ADDRESS> (<IP_ADDRESS>), 64 hops max, 40 byte packets
 1  router.asus.com (<IP_ADDRESS>)  4.142 ms  2.159 ms  1.905 ms
 2  raspberry-extern (<IP_ADDRESS>)  1.924 ms  2.262 ms  1.659 ms
 3  <IP_ADDRESS> (<IP_ADDRESS>)  59.853 ms  75.364 ms  64.368 ms

Pings with zero paket loss
❯ ping -c 100 <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>): 56 data bytes
64 bytes from <IP_ADDRESS>: icmp_seq=0 ttl=62 time=63.984 ms
...
64 bytes from <IP_ADDRESS>: icmp_seq=95 ttl=62 time=84.316 ms
64 bytes from <IP_ADDRESS>: icmp_seq=96 ttl=62 time=62.566 ms
64 bytes from <IP_ADDRESS>: icmp_seq=97 ttl=62 time=78.672 ms
64 bytes from <IP_ADDRESS>: icmp_seq=98 ttl=62 time=111.832 ms
64 bytes from <IP_ADDRESS>: icmp_seq=99 ttl=62 time=87.197 ms

--- <IP_ADDRESS> ping statistics ---
100 packets transmitted, 100 packets received, 0.0% packet loss

The strange thing:
I can successfully run a curl command in the cli of my peer in network A to a Client in Network B, but when i run the same command on my Mac Book, which is connected to Network A too, i get this (it's stuck and never finishes):
❯ curl -kv <IP_ADDRESS>
*   Trying <IP_ADDRESS>:80...
* Connected to <IP_ADDRESS> (<IP_ADDRESS>) port 80
> GET / HTTP/1.1
> Host: <IP_ADDRESS>
> User-Agent: curl/8.4.0
> Accept: */*
>

Are you using NetBird Cloud?
No i'm using a self-hosted Netbird server.
NetBird version
I've installed everything today, so i have the newest version.
NetBird status -d output:
Peers detail:
 raspberry-intern.netbird.selfhosted:
  NetBird IP: <IP_ADDRESS>
  Public key: <>
  Status: Connected
  -- detail --
  Connection type: Relayed
  Direct: true
  ICE candidate (Local/Remote): host/relay
  ICE candidate endpoints (Local/Remote): <IP_ADDRESS>:51820/<>:51820
  Last connection update: 2024-04-05 14:37:12
  Last WireGuard handshake: 2024-04-05 19:28:50
  Transfer status (received/sent) 77.9 KiB/105.7 KiB
  Quantum resistance: false
  Routes: <IP_ADDRESS>/24
  Latency: 74.996393ms

Daemon version: 0.27.1
CLI version: 0.27.1
Management: Connected to https://domain.com:443
Signal: Connected to https://domain.com:443
Relays:
  [stun:domain.com:3478] is Available
  [turn:domain.com:3478?transport=udp] is Available
Nameservers:
FQDN: raspberry-extern.netbird.selfhosted
NetBird IP: <IP_ADDRESS>/16
Interface type: Kernel
Quantum resistance: false
Routes: -
Peers count: 1/1 Connected

As I understand the problem @ https://github.com/netbirdio/netbird/issues/1370, the pings from A to B don't work there at all, do they?
But all pings work for me without any problems, just as I wrote. But when i try to load the WebUI or try the ssh connection from my network A to network B, for example, it never successfully "finish" loading.
As I just read @ https://github.com/netbirdio/netbird/issues/743, there seems to be a problem with the MTU size. One of my networks is connected to internet via 4G router and the other via cable (DOCIS3.1 cable modem). This is exactly how one of my networks is connected, which is why I suspect that I have the same problem.

No problem, thank's anyway!
I will try that https://github.com/netbirdio/netbird/issues/1370#issuecomment-1855001191
I have already applied this configuration to both of my Raspberry Pi 4 devices, which I believe is why all ping requests are successful:
iptables -I FORWARD -o wt0 -j ACCEPT
iptables -t nat -I POSTROUTING -o wt0 -j MASQUERADE

but i did not this and  i think i don't have 'br-lan' (or do i have to check that when i'm home and have time)?
iptables -I FORWARD -o br-lan -j ACCEPT

It seems to be working now. I can't say exactly what the problem was, but I have set up two new Raspberry Pi's, as these are the two that will ultimately be used.
But I won't be able to say for sure for another 1-2 weeks, once everything has been installed at the destination.


MaxDeltaTime

I am half way through the game and i have not experienced slow loading yet.
BUT i use MaxDeltaTime=0 the moment i updated inis from ur git with MaxDeltaTime=3 i get massive frames skips during recording.
Also on side note, left trigg+right trigg+start +sel (or just start) has no effect in my game what so ever.
Using Logitech Rumblepad 2 it doesnt have xinput.
Nvidia gtx 950 and bandicam.latest

I see, I just sort of assumed the game didn't even support DirectInput like 99% of JRPGs ;)
I can fix this in a later version.

its working flawlessly,not like pesky xbox gamepads which disobey to work on ffx :P

Is your controller the one with the numbered buttons?
I may need your help testing something. I've gotten a rudimentary DirectInput wrapper up and running, but I only did a mapping for PS3/PS4 controllers --> XInput button layout. I don't know what numbers your controller fires off (in Joy.cpl) for these functions.
What I have for PS4 controllers is this:
Square = 1
Cross = 2
Circle = 3
Triangle = 4
L1 = 5
R1 = 6
L2 = 7
R2 = 8
Select = 9
Start = 10
L3 = 11
R3 = 12

I'd like to confirm the general layout is the same on generic gamepads as well.

Sorry it took so long, just got home
http://imgur.com/prUZs67
this is button mapping

Everything is working as intended.
Although i still cannot record properly with "default" maxdeltatime=3
game starts hanging for second-two constantly.
maxdelta=0 is still working without issues for me tho
intel 2500k and nvidia gtx950

Things should be working as intended now, I've opted to turn the MaxDeltaTime fix off after doing testing on my laptop's AMD and Intel GPUs.


Misaligned exception messages

Overview
A few exception messages appear misaligned:

https://github.com/yu-iskw/dbt-unittest/blob/0.1.1/macros/assert_in.sql
https://github.com/yu-iskw/dbt-unittest/blob/0.1.1/macros/assert_false.sql
https://github.com/yu-iskw/dbt-unittest/blob/0.1.1/macros/assert_is_not_none.sql
https://github.com/yu-iskw/dbt-unittest/blob/0.1.1/macros/assert_not_equals.sql
https://github.com/yu-iskw/dbt-unittest/blob/0.1.1/macros/assert_list_equals.sql
https://github.com/yu-iskw/dbt-unittest/blob/0.1.1/macros/assert_dict_equals.sql

Are you willing to contribute the resolution?
Yep, submitting it shortly 😎

The patch has been released at v0.2.0. Thank you!
https://github.com/yu-iskw/dbt-unittest/releases/tag/v0.2.0

🎉
You are welcome. Thanks for publishing the handy macros in this package.


Hyperlinks to Bibliography does not work

Consider the following
toplevel.adoc (snippet of full toplevel document)
[chapter]
= Section title

include::aFile.adoc[]

[chapter]
= Bibliography

include::bib.adoc[]

aFile.adoc (the included section)
== A file
with text
== and this reference
* <<TestRef,Test reference text>>

bib.adoc (the included bibliography)
ifdef::backend-epub3[]
== Bibliography
endif::backend-epub3[]
[bibliography]
== Bib Section
- [[[TestRef]]] ysb33r. https://github.com/asciidoctor/asciidoctor-epub3

When rendered the TestRef will show up as a hyperlink, but when clicked will not move the document to the bibliography section

When rendered the TestRef will show up as a hyperlink, but when clicked will not move the document to the bibliography section

This link is supposed to allow you to jump between the bibliography entry and the first reference to it. However, if there are no references to it, the link is broken. A link should only be created if there's a corresponding reference to jump to.

Is this resolved? I was able to reproduce this buggy behavior under the new build:
13:33 $ asciidoctor-epub3 -v
Asciidoctor EPUB3 1.5.0.alpha.7 using Asciidoctor 1.5.5 [http://asciidoctor.org]
Runtime Environment (ruby 2.4.1p111 (2017-03-22 revision 58053) [x86_64-darwin16]) (lc:UTF-8 fs:UTF-8 in:- ex:UTF-8)
13:33 $ asciidoctor-epub3 -D . toplevel.adoc
/usr/local/lib/ruby/gems/2.4.0/gems/nokogiri-<IP_ADDRESS>/lib/nokogiri/xml/document.rb:44: warning: constant ::Fixnum is deprecated
asciidoctor: WARNING: aFile.adoc: invalid reference to unknown local anchor (or valid bibref): TestRef

@neontapir there are two cases here and only one of them was fixed. First, the link to the bibliography entry can't be validated (the case to which you are referring). That's a problem that stems from Asciidoctor core not cataloging these references. Second, the link from the bibliography entry back to the source wasn't working before. That's the side that got resolved. But even with the warning, the jumps should still work (as the warning message hints).
So we still have work to do. However, everything that needs to be done here is done. The change needs to happen in core. That's https://github.com/asciidoctor/asciidoctor/issues/560.

I'll try to get that into 1.5.6 or 1.5.7.


Always display document number when available

Currently showing the document number (column docID in s_order_documents) in the order documents tab in the backend is specifically disabled for document type 4 (correction of invoice). Shopware doesn't even generate it by default for this type, but a plugin like Pickware might want to.
With this PR it is simply displayed when it's present, which doesn't change Shopwares default behavior but allows to generate/display it if wanted.

Dear Contributor,
Thank you for your contribution to Shopware. We value your engagement.
Unfortunately we have to close all existing Pull Requests.
This is due to the new Shopware 5 Major Release and a restructuring of the branch names.
If your contribution is still relevant for Shopware 5, a new pull request is highly appreciated.
We are very sorry for this inconvenience.
Greetings from the Shopware Team.


MAILER SMTP DON'T WORKING

"EMAIL SEND FAILED"
SMTP Mailer 1.2.1 not send email.
I have investigated in log server, but I find no trace of any errors.
A disaster Dolphin 7.2.1

I've just checked SMTP Mailer in Dolphin 7.2.1 it is working. Actually we have no changes in it so it should work as before. I would suggest to recheck you SMTP Mailer settings.
If you still have problem please post in forums:
https://www.boonex.com/forums/


Newflasher stocks on MacOS Ventura with M1

Hi, another M1 issue again...
I've self-built Newflasher with the following makefile modifications.
ifeq ($(OS),Darwin)
CFLAGS+= -I/opt/homebrew/Cellar/libusb/1.0.26/include/libusb-1.0 -L /opt/homebrew/Cellar/libusb/1.0.26/lib
LIBS+=-lusb-1.0
endif

Build process was successful. However, it seems that it gets stuck while running. More specifically, it stuck after the dump trim area selection, no matter which option I give.
Here is a complete log:
> ./newflasher
--------------------------------------------------------
            newflasher v55 by Munjeni @ 2017/2020
--------------------------------------------------------

Determining available free space:

  Available space to caller    = 17602452 MB
  Total space on current drive = 194008576 MB
  Free space on drive          = 17602452 MB

Device properties:
        bus number: 0
         port path: 1 (from root hub)
             speed: 480 Mbit/s (USB HighSpeed)

Reading device descriptor:
            length: 18
      device class: 0
               S/N: 0
           VID:PID: 0xFCE:0xB00B
         bcdDevice: 0x100
   iMan:iProd:iSer: 1:2:0
          nb confs: 1

Reading configuration descriptors:
             nb interfaces: 1
              interface[0]: id = 0
interface[0].altsetting[0]: num endpoints = 2
   Class.SubClass.Protocol: 0xFF 0x42 0x3
       endpoint[0].address: 0x81
           max packet size: 0x200
          polling interval: 0x0
       endpoint[1].address: 0x01
           max packet size: 0x200
          polling interval: 0x1

Set configuration: succed.

Claiming interface 0: succed.

Reading string descriptors:
   String (0x01): "Google"
   String (0x02): "Android"

Do you want to keep userdata? Type 'y' and press ENTER to confirm, or type 'n' to erase userdata.
y

Reboot mode at the end of flashing:
  type 'a' for reboot to android, type 'f' for reboot to fastboot, type 's' for reboot to same mode, type 'p' for poweroff, and press ENTER.
s

Optional step! Type 'y' and press ENTER if you want dump trim area, or type 'n' and press ENTER to skip.
Do in mind this doesn't dump drm key since sake authentifiction is need for that! But it is recommend to have dump in case hard brick!
y

Ah sorry seems that it was because my device got stuck. Fastboot commands didn't work either. It worked after rebooting. Closing this issue. BTW thanks for your great work!


"Cannot connect to remote host" while trying to connect to DB with PHPStorm

I tried connecting PHPStorm to a project DB like I did many other times with warden; I followed the guide but I keep getting the error "Cannot connect to remote host"  while setting up the SSH Tunnel;
I also tried connecting to it from the CLI:
$ sudo ssh<EMAIL_ADDRESS>-p 2222
<EMAIL_ADDRESS>Permission denied (publickey,keyboard-interactive).
I can post a more verbose error message from the terminal if needed
Am I missing some step here? All the other services work correctly, as well as PHPmyadmin

Hello @adexandros !
To connect to the ssh tunnel, you should use 'user' as the ssh username.
https://rewardenv.readthedocs.io/en/latest/configuration/db.html

Hi @janosmiko , I posted the wrong example code but initially I tried with user and that didn't work either; this is my PHPStrom setup:

Could you show me the output of reward svc ps and ls -lah ~/.reward/tunnel.
Also could you try to connect with ssh -i ~/.reward/tunnel/ssh_key -l user -p 2222 tunnel.reward.test

~/projects/ba/hanes-eagle$ reward svc ps
   Name                 Command               State                      Ports
--------------------------------------------------------------------------------------------------
dnsmasq      /bin/sh -c  echo "$REWARD_ ...   Up      <IP_ADDRESS>:53->53/udp
elastichq    supervisord -c /etc/superv ...   Up      5000/tcp
mailhog      MailHog                          Up      1025/tcp, 8025/tcp
phpmyadmin   /docker-entrypoint.sh apac ...   Up      80/tcp
portainer    /portainer                       Up      8000/tcp, 9000/tcp
traefik      /entrypoint.sh traefik           Up      <IP_ADDRESS>:443->443/tcp, <IP_ADDRESS>:80->80/tcp
tunnel       /entry.sh /usr/sbin/sshd - ...   Up      <IP_ADDRESS>:2222->22/tcp

ls -lah ~/.reward/tunnel
ls: cannot access '/home/adexandros/.reward/tunnel': No such file or directory

$ ssh -i ~/.reward/tunnel/ssh_key -l user -p 2222 tunnel.reward.test
Warning: Identity file /home/adexandros/.reward/tunnel/ssh_key not accessible: No such file or directory.
<EMAIL_ADDRESS>Permission denied (publickey,keyboard-interactive).

I guess it cannot find the folder since reward is installed on windows? Should I copy the folder from window to inside WSL2?

The command $ ssh -i ~/.reward/tunnel/ssh_key -l user -p 2222 tunnel.reward.test works if executed from Windows Powershell

Could you try to configure PHPStorm SSH Authentication type to use "Key Pair" and browse the ssh key from your default Windows home?
Something like c:\Users\yourname\.reward\tunnel\ssh_key

Hi @janosmiko , that actually worked and I can connect to the database perfectly 👍🏻
I got 2 more questions if you are able to answer:

Is there a way to pass directly arguments too reward db connect ? for example when making install scripts that needs to send command for DB operations.
When I use the global service phpmyadmin, how can I connect to the different available projects DBs? When I use just user/pass I am only able to access the DB of the first project I started basically; if I put a server name like _db_1 I am not able to log in

Hi @adexandros !
Pass args directly to reward db connect
Yes it's possible.
You can use bash's double dash scheme "--". This is going to terminate reward's command line options and the rest is going to be passed as arguments.
So if you call reward db connect -- asd qwe then the part after double dash (asd qwe) will be passed directly to mysql command inside the container.
From mysql manual:
-e, --execute=name  Execute command and quit. (Disables --force and history
file.)
So we can use -- -e to run commands directly by mysql. Please note that in this case bash will try to handle the special characters so you will have to escape quotes, double quotes, semicolons and maybe more.
$ reward db connect -- -e \"show databases\;\"
+--------------------+
| Database           |
+--------------------+
| information_schema |
| magento            |
+--------------------+

$ reward db connect -- -e \"select table_name from information_schema.tables where table_schema=\'magento\' order by table_name limit 5\;\"
+-----------------------------------+
| table_name                        |
+-----------------------------------+
| adminnotification_inbox           |
| admin_analytics_usage_version_log |
| admin_passwords                   |
| admin_system_messages             |
| admin_user                        |
+-----------------------------------+

An idea to keep you code cleaner would be to use bash variables here. An important thing here as well if you just assign a command to a bash variable that's not going to have the trailing double quotes (see the first example):
# This is not going to work:
$ MYSQL_CMD="select table_name from information_schema.tables where table_schema='magento' order by table_name limit 5;"

$ echo $MYSQL_CMD
select table_name from information_schema.tables where table_schema='magento' order by table_name limit 5;

# But this will work:
$ MYSQL_CMD="\"select table_name from information_schema.tables where table_schema='magento' order by table_name limit 5;\""

$ echo $MYSQL_CMD
"select table_name from information_schema.tables where table_schema='magento' order by table_name limit 5;"
^ -- note the quotes are part of the variable here

# This will also work:
$ MYSQL_CMD=$(cat <<"EOF"
"select table_name from information_schema.tables where table_schema='magento' order by table_name limit 5;"
EOF
)

$ echo $MYSQL_CMD
"select table_name from information_schema.tables where table_schema='magento' order by table_name limit 5;"

$ reward db connect -- -e $MYSQL_CMD
+-----------------------------------+
| table_name                        |
+-----------------------------------+
| adminnotification_inbox           |
| admin_analytics_usage_version_log |
| admin_passwords                   |
| admin_system_messages             |
| admin_user                        |
+-----------------------------------+

On your second question
You can check the "hostname" of your db container by running reward env ps db.
reward env ps db
 Name                Command               State    Ports
-----------------------------------------------------------
m2_db_1   docker-entrypoint.sh mysql ...   Up      3306/tcp

And you should be able to use this name (for me its m2_db_1).
Please make sure your phpmyadmin container is connected to the environment's container network.
To list the networks your phpmyadmin container is joined you can run the following command:
docker inspect --format='{{range $key, $value := .NetworkSettings.Networks}}{{$key}} {{end}}' phpmyadmin

I updated the documentation, hopefully now makes more sense:
https://rewardenv.readthedocs.io/en/latest/usage.html
https://rewardenv.readthedocs.io/en/latest/configuration/db.html

Hi @janosmiko , that's great news and information; I run the command to check which network phpmyadmin is connected to and it only list one of my projects; how do I add another one to it? is this something that needs to be done for each new project created?

Well that's interesting.
When you run reward env up reward should connect phpmyadmin to the environment's network.
Could you try to run reward env down and then reward env up?
If you enable debug mode, you should see something like this:

Thanks that did the trick 👍🏻


removed tableName prop

Closes #1
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

holding off merging till GitHub stops having incidents 🙄

holding off merging till GitHub stops having incidents 🙄


Hose Crash in 0.1.0 on MC 1.10.2

Just placed a hose randomly in the world. Rest should be in the pastebin.
http://pastebin.com/fVxG5Bsx

I cannot reproduce this. Does this happen all the time?

Even though I cannot reproduce it someone else also reported it. I added a test for this so next version should fix this


feat(project): adds command to update project owner

Description

:tada: This PR is included in version 7.5.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


A282953159619251 tests refactoring

This change is

Coverage increased (+1.3%) to 91.099% when pulling 20581f2c8b1d83aa83516188f1d61d980fb06bca on yarsanich:a282953159619251_tests_refactoring into 69becf54ed37fd9feac44aa32486ec4c20fc6e49 on openprocurement:a282953159619251_tests_refactoring.


Single auth check for authorized resource filtering

Fixes #4813
Changes the AuthorizationUtils.filterAuthorizedResources() method and SupervisorResource to prevent multiple authorization checks being performed on requests (See https://github.com/druid-io/druid/pull/4816#pullrequestreview-63229983 for context).

@nishantmonu51
Hm, I don't know how to setup tests like SupervisorResourceTest with the servlet filters that would be used in a real environment (like PreResponseAuthorizationCheckFilter), any ideas there?


Catch all quota errors

🔴 change privacy from within BUILDER  (403 error console)
🔴 change privacy from modal dialog within BUILDER  (403 error console)
🔴 change privacy from dashboard  (generic modal error + 403 in console)
🔴 duplicate a dataset from dashboard (modal with unknown error and no text, can't be closed + 403 in console)
🔴 create empty dataset -> error 400 in the console
🔴 add layer from new layer in BUILDER
💚 drag and drop .carto
💚 drag and drop table
💚 from dataset view -> duplicate
💚 from dataset view -> create from query
💚 sync from data library

Good job @alrocar! This is perfect.


Bug: galleries not loading on mobile

Not sure if actually a bug or an issue with iOS 13 Beta 1
Actual bug, not just related to  iOS 13 Beta 1. Can be reproduced in Safari, Chrome, and Firefox web inspectors.
Note: Does not affect mobile landscape view, only vertical. Not sure what changed that introduced this.

Fixed in #69


Fix kubelet-preferred-address-types set incorrectly

Fixes https://bugs.launchpad.net/charm-kubernetes-master/+bug/1826397
@johnsca should be able to vouch for this as a fix for kubectl logs failing on openstack.
Some additional evidence: kubelet-preferred-address-types in the Kubernetes code is defined using StringSliceVar. Kubernetes uses Cobra, which uses pflag, which documents StringSliceVar here. No brackets.

LGTM +1


[FEATURE REQUEST] Ability to execute custom functions.

EG:
{
"cmake-build": "mkdir build && cd build && cmake ../ && $$findExecutableToExecute"
}

So when it reaches the $$finExecutableToExecute it will run a function that looks for an executable and returns the executable path.

When you add a project the project has the option to add a custom command,
Even using the variables that already exist, you could reach the result you expect, but maybe if you are more explicit with the new function, program it this weekend and add it to the new_features branch.

How does the project thing work? I need to define a new project in json for every new one I create? It appears to me to be mapped directly to the directory.

It is related to a directory, but you could make a pr with what you want, I check it if it is a good idea I add it


Implement SDL Parsing/Printing Support

This PR implements basic support for parsing of GraphQL Schema Definition Language (support was already implemented for the Executable Definition Language of course ) as defined by the graphql-js reference implementation.
Support for parsing of SDL may be at odds with this librarie's goal of improved type-saftey (over the graphql-js implementation and other schema-driven GraphQL API implementation approaches) however I believe it is worth including support here as SDL parsing is a useful feature to have outside of building type-safe GraphQL API implementations. Both the EDL and SDL are tied very closely together so (I think) it makes sense to co-locate in a single package.
In any case, another option is to break this parser support out into a separate reason-graphql-parser package (seems like the Rust folks did this with graphql-rust/graphql-parser) - let me know what you think.
Great work on this library, I learned a lot about lexers, parsers, and ReasonML (haven't worked with any before, so feel free to wreck me on the review ;) ) 👍
Todo:

[ ] Support type system extensions (i.e extend)
[ ] Support directives on ENUM_VALUE's
[ ] Support description's on all type definitions (right now only supported on fieldDefinitions as it was straightforward to add support w/o many modifications to the parser)
[ ] Implement validations as defined in the graphql-js reference implementation

@timkendall Wow! huge contribution! I will take a deep look later as I am traveling right now. What prompted you to contribute to SDL parsing?

Sweet, thanks!
I'm interested in SDL parsing with ReasonML as I am working on a project that generates full GraphQL API's from directive-decorated (using Apollo's Federation Spec) type definitions (like Prisma, AppSync, FaunaDB).
Currently we have this portion (the "compiler" portion) of the project written in TypeScript. Interested in using ReasonML instead however to achieve cleaner code (variants and patten matching lend themselves very nicely to compiler logic) and faster runtime (using ReasonML native compilation) as we are exposing this functionality via a Node-backed CLI interface who's startup time is egregious.

@timkendall Do you want me to review this asap or should I wait for the checklist to complete?

Ha I was going to message you. I think this PR is big enough on its own and was planning on submitting follow up PRs to address the checklist. I'll remove the checklist and you can review 👍


added device.id to AgentResource

host.id is being mapped to a System.ID https://github.com/elastic/apm-server/blob/01a12f2b3ebfa78c2186270eb4771c6ff1d7a27b/model/system.go
which doesn't get mapped to any fields in ES. This PR adds device.id as a temporary fix.

:green_heart: Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Build Cause: Pull request #40 opened

Start Time: 2021-06-16T20:21:02.182+0000

Duration: 6 min 54 sec

Commit: f73e7352c55b3f57d8cb67ad8bd836e7beb9e429

Trends :test_tube:


feat: participant ID from/to IRI mapper

WHAT
Implements a tractusx specific participantID from/to IRI mapper
https://github.com/eclipse-edc/Connector/issues/3930
WHY
dsp compliance

Is 1107 for "ID from/to IRI mapper" closed by below pull request?
===> https://github.com/eclipse-edc/Connector/pull/3932

Is 1107 for "ID from/to IRI mapper" closed by below pull request? ===> eclipse-edc/Connector#3932

I think the issue here is to implement the mapper for T-X, as the ID used in catena are not IRI (they are simple BPN) and that goes against the ODRL ontology (assigner and assignee are subtypes of Party)


Code cov integration

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@fa62706). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main       #4   +/-   ##
=======================================
  Coverage        ?   90.74%
=======================================
  Files           ?        2
  Lines           ?      108
  Branches        ?        0
=======================================
  Hits            ?       98
  Misses          ?        5
  Partials        ?        5

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 fa62706...0adcb29. Read the comment docs.


Investigate usage of modified intrinsics with await

Per discussion:

Promise = class MyPromise extends Promise {} ; async function foo() {} - is the Promise returned by foo() a MyPromise? Or is it the original, now mostly-otherwise-inaccessible Promise?
await foo; Under what circumstances does this call .then on the object, thus Promise#then (which may be modified)? If I modify Promise.prototype.then, should that be called when await foo, or not? What if I delete the constructor property on foo?

The use cases I'm thinking of are:

I should be able to modify the global Promise in such a way as its impossible for users to ever retrieve the original (I do this now with RegExp and Number, for example, in the es6-shim), and await and async functions should work with the modified global.
I think I should be able to modify Promise.prototype.then such that await foo will always invoke my replacement function.

Or is it the original, now mostly-otherwise-inaccessible Promise?

This makes the most sense to me, consider people doing Promise = ... with a non valid Promise implementation in a library, it shouldn't break other unrelated code.

If I modify Promise.prototype.then, should that be called when await foo?

Most likely yes, though that's an esoteric case that I don't expect to be an issue anyway.

I should be able to modify the global Promise in such a way as its impossible for users to ever retrieve the original.

Why? I don't understand why this is desirable. You can modify the original Promise by changing its then but overriding it completely sounds like it would be problematic. This is kind of like modifying Function.prototype.apply, risky.

I think I should be able to modify Promise.prototype.then such that await foo will always invoke my replacement function.

This sounds OK, but again, why? I'm not sure I understand the use cases here.

Very interesting questions. Currently, most Promise implemented in browsers non-completely spec-complaint. ES7 changes Promise behavior - adds unhandled rejection tracking to the spec. Something else can be changed in the future. For getting correct Promise behavior, it should be polyfilled - patched, wrapped or completely replaced.

That's a very good point, for the very least it should delegate to then if it was overridden

The sole use cases I'm asking about is for libraries like es6-shim, es7-shim, core-js, etc, which attempt to fix environmental gaps or breakage (every single environment has ES5 compliance errors, still, for example).

I don't think the spec should cater to people who are overriding globals but not overriding their accompanying syntax. In other words, if you want to use a version of Promise that is not implemented by your JS engine, then you should use a version of async/await that is not implemented by your engine. Even more explicitly: if you're using the shim, also use a transpiler. (And you probably want to override every web API that returns a promise while you're at it, because those also don't use overridden globals.)

The es-shims are only concerned with the language, not with browsers - certainly shims for those would need to use the global Promise.
The es6-shim already handles RegExp and Number by modifying the [[Prototype]] of the original constructor, and presumably it would work the same with async and Promise.
This issue is to simply decide how it should be spec'ed.
For what it's worth, the spec always caters to people who are overriding globals, whether they override their accompanying syntax or not - that's why most things are configurable, even if they're not writable or enumerable, like Symbol.toStringTag on builtins or RegExp on the global object. The same ethos will inevitably apply here - this is a use case the spec and the committee continually insist on preserving, and as such, this particular spec will need to do the same.

async functions must not use any overridden global.Promise to create their return value, and await syntax must not use any overridden Promise.resolve to resolve its argument. The spec does not cater to overridden builtins, and I'm very surprised you've gotten that mistaken impression. Thinking the configurability of properties has anything to do with how syntax generates objects betrays a fundamental misunderstanding of ES.
RegExp literals don't return overridden RegExp constructor instances. Number or Boolean literals, when wrapped, don't use overridden global.Number or global.Boolean. The `${string} string conversion does not use overridden global.String to perform string conversion. I could go on, but hopefully I don't have to. This is pretty basic stuff.

You're totally right - but if I modify the [[Prototype]] chain of the builtin RegExp, and then RegExp = OverriddenRegExp, /a/g instanceof OverriddenRegExp returns true. That's how the es6-shim allows new RegExp(/a/g, 'i') to work. If the same will be possible with Promise and async/await, then I'm content.

Oh, for sure, I don't see how it would even be possible to prevent that.

The one remaining question though is that even if it's the native Promise.resolve, would it still call an overridden Promise.prototype.then? If so, that gives me the mechanism to intervene in the syntax. If not, then I can't override the constructor, just the prototype methods.
I'm specifically looking at http://www.ecma-international.org/ecma-262/6.0/#sec-promise-executor step 8, which leads to http://www.ecma-international.org/ecma-262/6.0/#sec-createresolvingfunctions step 2, which leads to http://www.ecma-international.org/ecma-262/6.0/#sec-promise-resolve-functions step 8, which does a [[Get]] of "then" on the promise value. If I've modified Promise.prototype.then on the builtin Promise, then surely this is what will be called by await, per http://www.ecma-international.org/ecma-262/6.0/index.html#sec-newpromisecapability step 6 which leads to http://www.ecma-international.org/ecma-262/6.0/index.html#sec-promise-executor step 8?

Changes to %Promise% and %PromisePrototype% should not affect async function and await semantics, although the standard built-in Promise.resolve does do a [[Get]] for the awaited promise's then since it could be any foreign thenable. If you await a native promise, Promise.prototype.then will be invoked.

If you await a native promise, Promise.prototype.then will be invoked.

Yes I think this is the most consistent behavior. You delegate to Promise.prototype.then but if someone swaps out the global Promise object async functions still return an instance of the original.

It won't use .then unless you also override .constructor, since otherwise IsPromise will be true and it will do a pass-through.

This is a difference between Promise.resolve and the Promise Resolve Function. Async function await uses the latter and does the equivalent of var p = new Promise(extractor); extractor.resolve(awaitedValue); return p;, and this codepath should always invoke .then on the awaited value. I think this is the appropriate semantics.

Great! So that means that returning from an async function returns an original Promise even if the global is modified, and await invokes Promise.prototype.then even if it has been modified.
Similarly, if I do something along the lines of:
var OriginalPromise = Promise;
var MiddleMan = function () {};
Object.setPrototypeOf(OriginalPromise, MiddleMan);
MiddleMan.prototype = OriginalPromise.prototype;
OriginalPromise.prototype.constructor = MiddleMan;
Promise = MiddleMan;

then var promise = (async function () {}()); promise instanceof OriginalPromise && promise instanceof MiddleMan should both be true, even though Promise is no longer user-accessible. This is how the es6-shim currently overrides Number and RegExp, even though both are produced by syntactic literals. (I wrote this code off the top of my head so corrections to it aren't necessary or desired).
I'm going to close this since this has answered my original question perfectly.

Yeah, I believe it should work fine for your use case. You can try in Edge if you have a windows machine ;)


fixed oauth in mopidy ytmusic setup command

The current version of this plugin (with your changes) doesn't work for creating a brand new auth.json file - the call for YTMusic(filepath) isn't correct anymore - thus, any new user would have issues. This change fixes that issue and mopidy ytmusic setup or sudo mopidyctl ytmusic setup work fine again creating a correct file. I changed the default name of the file to oauth.json to prevent overwriting of the old auth file for people who still have and use it.
Also removed the upper boundary of pytube version because it collides with current version 15.0.0 and there are no changes preventing the code from working as is.

Thanks for the PR. Haven't used the package in a bit, but glad to see there's still a community around it

Thanks @jmcdo29.  When you get a chance would you be able to create a new release? I'll update the arch package to pull from the release when it's ready.

@kmac all right, new release has been made


Incorrect Routing when a configuration exists with query param wildcard

Ocelot now matches routes incorrectly.
This started breaking between versions 22.0.1 and 23.0.0.
If I have two configurations -
{
  "Routes": [
    {
      "DownstreamHostAndPorts": [
        {
          "Host": "{Endpoint1}"
        }
      ],
      "DownstreamPathTemplate": "/api/v1/abc?{everything}",
      "DownstreamScheme": "https",
      "UpstreamPathTemplate": "/api/v1/abc?{everything}"
    },
    {
      "DownstreamHostAndPorts": [
        {
          "Host": "{Endpoint2}"
        }
      ],
      "DownstreamPathTemplate": "/api/v1/{everything}",
      "DownstreamScheme": "https",
      "UpstreamPathTemplate": "/api/v1/abc2/{everything}"
    }
  ]
}

Now if I initiate a call with /api/v1/abc2/apple?isRequired=1
Expected Route: {Endpoint2}/api/v1/apple?isRequired=1
Actually Routes to: {Endpoint1}/api/v1/abc?isRequired=1"
Similar issue reported in: Originally posted by @Burgyn in https://github.com/ThreeMammals/Ocelot/discussions/2065

Duplicate of #2064

Thanks for reporting this! Are you C# developer?

Thanks for reporting this! Are you C# developer?

Thanks, Yes C# developer.

Could you look into the issue by debugging the solution and examining Ocelot's code when you have some spare time, please?
I am currently swamped with tasks for the v23.3 Hotfixes. I anticipate an open PR that will shed light on the issue, which I suspect might be related to a Regex problem.

This is also happening for Scopes. If I have two routes where the first is a wildcard for the second, the scopes assigned to the wildcard route allows me to access the second one and not viceversa

Hello Raffaele,
Why did you delete your comment from issue #2132?
Please be aware that using wildcards is not supported in Ocelot templates
or placeholders.
If you encounter any unusual behavior with special characters, please let
us know.

@lelloz0 Hello Raffaele, Why did you delete your comment from issue #2132? Please be aware that using wildcards is not supported in Ocelot templates or placeholders. If you encounter any unusual behavior with special characters, please let us know.

I realized the issue is indeed somewhere else and not related to the wildcards. Thanks for the follow up!

@pwshfan, okay, we will concentrate on the originally reported bug. Feel free to report any issues, but please create new ones.

@int0x81, welcome to your assignment!


[8.x] Added oneOrFail() alias for sole()

I like the functionality of sole() but I also like consistency.
All other QueryBuilder methods that are able to throw an error end with OrFail()
If you prefer singleOrFail #35928

Thanks for your pull request to Laravel!
Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.
If possible, please consider releasing your code as a package so that the community can still take advantage of your contributions!
If you feel absolutely certain that this code corrects a bug in the framework, please "@" mention me in a follow-up comment with further explanation so that GitHub will send me a notification of your response.

Thanks for your pull request to Laravel!
Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.
If possible, please consider releasing your code as a package so that the community can still take advantage of your contributions!
If you feel absolutely certain that this code corrects a bug in the framework, please "@" mention me in a follow-up comment with further explanation so that GitHub will send me a notification of your response.


How to make 2d pose estimation output .npy?

Hello.
I want to run in the wild data using inference. but I don't know how to make 2d pose estimation output (.npy file).
According to what I understand, For making npy file, I should use h36m2Dpose.py or annotate_2D.p, right?
Can you explain how?
thank you.

Closing inactive issues. Re-open if you have further questions.


[Nextcloud] Can you mount an NTFS external HDD through localdisks:?

Nextcloud

name: NTFS support
title: 'Can you mount an NTFS external HDD through localdisks:?'
labels: 'Question'
Can you mount an NTFS external HDD through localdisks: to a Powered USB hub attached to a RPi4? I have a media drive that is full of Pictures/Tv Shows/Movies that I would like to make accessible on my local network. It does work through the networkdisks: option but its currently plugged into a windows machine that sleep after 10 minutes and therefore becomes inaccessible.
I originally intended to use the SAMBANAS addon but that doesn't play nice with Windows formatted HDD apparently.
Great Addon btw, cheers!

Hi, indeed it uses the same mount system so it won't work to mount NTFS drives. This topic was also discussed here : https://github.com/alexbelgium/hassio-addons/issues/235

Support could have been added

Support could have been added

Sorry, do you mean you have added it?

Yes indeed, but not sure it works. It is in the latest pushed version

Yes indeed, but not sure it works. It is in the latest pushed version ; I don't have a NTFS drive to test

Ok thanks. I will try it and let you know


require from Browserify in v0.11.0 from NPM is broken

Hi,
After the update to v0.11.0, installing from NPM is broken.
Error: Cannot find module '../core/Common' from '/Users/laustdeleuran/Sites/revelator-website/node_modules/matter-js/build'

The error seems to come from line 46-52 in /build/matter.js. Those files are not included in the NPM build.
For now, I'm rolling back to v0.11.0.

Looking closer at the built file, the files are included (e.g. Vertices on line 7654), but for some reason my Gulp / Babel build chokes on it. It works fine with v0.10.0.

Can't reproduce this when doing:
npm i matter-js --save
node
> require('matter-js')
{ name: 'matter-js',
  version: '0.11.0',
  uses: [],
  used: [],
  use: [Function],
  before: [Function],
  after: [Function],
...

Does this work for you?
I suspect the issue might be to do with change 0cb1d83.
Basically I changed main from the source to a browserify built UMD module, which should work fine everywhere?
Does anybody know why this might cause issues?

@liabru Weird, I'm using Browserify (on ES6 with import syntax) myself, so not sure why it chokes on this. But still, I suspect you're right in where the error originates. I'm still getting the error even when I remove the babelify transform and use the require syntax.
Requiring matter-js directly in the node command line works fine. Not sure what is going on. :/

I bumped into this issue a few days ago as well, thought there was something wrong with my local setup. Ended up just loading from CDN for the time being.
Definitely only happens with Browserify, because for some reason Browserify tries to parse the require-calls in the built version that is specified as the main file for Matter.
Following the StackOverflow answer to the issue at hand, this is relevant:

The module you want to use should be built with the standalone option. That option is intended for creating a file that can be loaded by other module systems (including browserify itself, node.js, requirejs, etc.)

Should probably build the distributed file with --standalone Matter?

@codeclown it already is built using standalone. I'm guessing the issue comes when trying to bundle an already browserified module due to it parsing the require calls when it really shouldn't. It's probably why webpack uses __webpack_require__ instead. So I'll look into switching I think.

There is something fishy about this, because a package built with standalone should not cause issues like this. I don't have time to inspect if it's a bug in Browserify or an issue with how Matter is built right now, but will try to at some point.

From the browserify docs regarding standalone:

Note that in standalone mode the require() calls from the original source will still be around, which >may trip up AMD loaders scanning for require() calls. You can remove these calls with derequire:

$ npm install -g derequire
$ browserify main.js --standalone Foo | derequire > bundle.js

So looks like this is a known issue with browserify?

Apparently so. Maybe package.json should not point to the compiled file?
  "main": "src/module/main.js"

Won't the solution listed in your comment solve the problem @liabru? Webpack is great, but if there's a fix already available, it seems like something that could wait.

You could probably hook up derequire to gulp so it would be taken care of, no?
If this is something you'd consider, I could also contribute a pull request.

Apparently so. Maybe package.json should not point to the compiled file?

I decided it's better to point it at a file a browser can use too, as that's the primary target. This is what lodash does for example. Also, the build does some automated replacement stuff (e.g. versioning) that is crucial to the new plugin system, which will fail if main just points at the raw source.

Won't the solution listed in your comment solve the problem @liabru? Webpack is great, but if there's a fix already available, it seems like something that could wait.

Exactly, the first thing I'll try is adding derequire to the build step.

I just pushed 0.11.1 which uses derequire, can you try it out and tell me if it's solved?

Yes, errors are gone.


data: lux5h

@lux5h so basically once you create a PR using a branch and someone suggests changes, you can commit the changes to the same branch and they will reflect here in the PR. I noticed you created a new PR with the changes, try committing them to the same branch next time, Thanks!

PR

Thank you! will keep in mind from next time.


colpickHide skips the onHide callback

Closing the color picker with colpickHide doesn't call the onHide callback.

Thanks for the contribution!


Updated the Readme file with the new logo

referenced from issue #1216

Pull Request Test Coverage Report for Build 2165

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.2%) to 99.755%

Totals

Change from base Build 2163:
0.2%

Covered Lines:
1630

Relevant Lines:
1634

💛  - Coveralls


Command parser

We need module that will understand input commands, check their correctness and parse them

Finished (second comment. first comment is our project entirely)


Memory Leak (v-if in combination with click on HTMLElement)

Vue version
3.5.12
Link to minimal reproduction
https://play.vuejs.org/#eNrtVctOwzAQ/BXjCyDRVFDgUNKKh4pUDoCg6gUj1Kbb4DaxLXsTiqr+O2tHDTmg/gBVLt6dncl4D+M1vzEmKgvgXR67xEqDzAEWpi+UzI22yNbMwpxt2NzqnB3S6KFQQiVaOWTSjaWT0wxYz08doS3gWKi4XUmRCBUIuckmCFQxFk8LRK3YdZLJZNkTvClxUBeC90c6Tak7bg3v43bFCnr+I52ZLBmZwIlUYFnZkvOmGPH9VP2//ggcNmT20B7aQ/8bituUIXSK242EotLhd+aPb3W8vLO1J+QTm0rVQm267PTSrK6E2oSwCwR+wtERZS7TaOG0okQNLMETnRuZgX0yKCk2Be9Weh6bZJn+egg9H54n237yCcnyj/7CrXxP8GcLDmxJSVdjSP4AK3jw+ggrOtdgrmeFz8Ud4As4nRXeYzV2W6gZ2W7MBbfD8C5IlY7cYIWg3PZS3qif3IR5wemtuNtx9V+7neg88GiftMWPEqzXpAV2oovo9IxvfgBBk0Pk
Steps to reproduce
Prerequisites:
open DevTools and Performance Monitor
First Test (no leak)

watch the initial number of DOM-Nodes inside the performance monitor
click the Toggle V-IF button multiple times. The number of DomNodes will increase. Manually collecting the Garbage will reduce the DomNodes to the initial count

Second Test (with leak)

refresh page
watch initial number of DomNodes again
click Toggle V-IF button again several times, but each time the list of test buttons appears, click on a test button and then on the V-IF toggle again.
clean the memory manually. →  The number of DomNodes no longer falls back to the initial value

Does Vue save the reference to the last clicked dom element and thus prevents the memory from being cleaned up?
What is expected?
The number of DomNodes after manually calling the GC should be the same as before
What is actually happening?
Some DomNodes are prevent from GC
System Info
No response
Any additional comments?
No response

Strictly speaking, this is not considered a memory leak because the number of detached elements does not continuously grow. When the component is unmounted, the elements can be properly released.
a workaround see https://github.com/vuejs/core/issues/5256#issuecomment-1173891407

Thanks for the fast response.
as mentioned in  https://github.com/vuejs/core/issues/5256#issuecomment-1173891407 i adjusted my vite.config.ts of my test project to:
// https://vite.dev/config/
export default defineConfig({
  plugins: [
    // vue(),
    vue({ template: { compilerOptions: { hoistStatic: false } } }),
  ],
  resolve: {
    alias: {
      '@': fileURLToPath(new URL('./src', import.meta.url)),
    },
  },
})

the problem still occurs. the same applies to the larger client project I am currently working on

I can't reproduce it with hoistStatic: false.
https://github.com/user-attachments/assets/09285eaf-d266-4665-9b2c-f927a8bb7c66

Sorry i cant provida a video for the bug atm.
Only clicking the Toggle V-IF button does not trigger the bug. You have to click one Test-Button each time the test buttons are mounted using the toggle V-IF button.

init (click toggle):

test-buttons appear. click any test button

click toggle again to hide the test-buttons

Step 2 is the important one. Repeating those 3 steps multiple time leads to the detached elements

it is a duplicate of #12306

That really seems to be it. Thanks for the help. I hope they fix it soon!


[bounty] move the macos lib linking from pre_build.js to build.rs

we currently do some hacks in pre_build.js to link the apple native OCR lib and it should happen in build.rs of vision crate which would make things more smooth for everyone and simpler to build & install
related issue one user is facing when building from source:

/bounty 50

we currently do some hacks in pre_build.js to link the apple native OCR lib and it should happen in build.rs of vision crate which would make things more smooth for everyone and simpler to build & install
related issue one user is facing when building from source:

/bounty 50

@louis030195 This cannot be done in the Vision crate because that crate is built before we build the screenpipe CLI, and this dylib hack depends on the screenpipe cli executable being present.
However it could be done in the tauri app crate build.rs: https://github.com/mediar-ai/screenpipe/blob/main/screenpipe-app-tauri/src-tauri/build.rs
Tell me what you think.


Add settledAt to Transaction Search response object

General information

SDK/Library version: 2.91.0
Environment: Sandbox
Language, language version, and OS: java 1.8.0_181 on MacOS 10.14.3

Issue description
When I search for transactions, I'm interested in the settledAt time. Why are createdAt and updatedAt times exposed but not settledAt?
Alternatively, if I do a search for transactions and one of my request conditions is settledAt().lessThanOrEqualTo(cal), is it safe to assume that the result transactions I get back are ALWAYS settled and updatedAt time actually reflects settledAt? If not, please consider exposing settledAt time in the transaction response object.

Hi @codeniko, to determine when a transaction was settled, check the response object's status history. It contains events with details such as the timestamp a transaction received the Settled status.


Add description for a FOLDER. Is that possible?

Through the "Docs" tab we can document the methods, but it would be really cool if we could put a description in a folder that contains several methods.
For example, if my workspace is divided in 3 folders:

Admin
Client
Auth

When I click on Admin option, from left menu, is there any way to add a description like image shows?

Theoretically, the Insomnia export file does contain a description field for folders too but there's no way (that I know of) to make changes to it. The documenter does have support for folder descriptions but until there's a way to edit the descriptions from within Insomnia, the only way you can achieve this is by editing the file directly.
To be fair, folders don't have their own view in Insomnia, so specifying descriptions for them would be useless for Insomnia anyway because there's no way to view them.
Perhaps @develohpanda could enlighten us more about this?

Looks like the editing descriptions was never added in even though the model was updated (as part of https://github.com/Kong/insomnia/pull/252 and subsequent PRs).
The context menus for folders and requests are very different, and the method of renaming is also different. Folder -> context menu -> rename -> modal, Request -> double click.
Descriptions for a Request are currently in the request settings modal. Given the interaction patterns for Request and Folders are already different, perhaps the same description UX can be introduced to the Folder Rename modal?

I just noticed that a workspace has a workspace settings view, containing workspace name and description. Request also has a request settings view, with name and description. We can probably do something similar for the folder rename view, updating it to "folder settings" with a name and description.

Main code folder


Confusing warning for low-sample-size runs

Summary:
When running Stan programs with low sample sizes (under 300 samples,) Stan returns a (confusing/spurious?) warning regarding the warmup.
Description:
When running an analysis with a sample size under 300, the following warning is generated;
WARNING: The initial buffer, adaptation window, and terminal buffer overflow the total number of warmup iterations.
Defaulting to a 15%/75%/10% partition, {List of used valuesfor each}
Reproducible Steps:
In R, run;
library(rstan)
stanmodelcode <- "
data {
int<lower=0> N;
real y[N];
}

parameters {
real mu;
}

model {
target += normal_lpdf(mu | 0, 10);
target += normal_lpdf(y  | mu, 1);
}
"

y = rnorm(20)
dat = list(N = 20, y = y);
fit = stan(model_code = stanmodelcode, model_name = "example",
            data = dat, iter = 290, chains = 3, sample_file = 'norm.csv',
            verbose = TRUE)

Current Output:
SAMPLING FOR MODEL 'example' NOW (CHAIN 1).
WARNING: The initial buffer, adaptation window, and terminal buffer
         overflow the total number of warmup iterations.
         Defaulting to a 15%/75%/10% partition,
           init_buffer = 21
           adapt_window = 110
           term_buffer = 14

Chain 1, Iteration:   1 / 290 [  0%]  (Warmup)
{etc. - Runs fine}

Expected Output:
No warning, or perhaps;
WARNING: The number of warmup iterations is below the recommended amount.

Additional Information
This error message occurs even when you specify the number of the buffers and window to rstan;
fit <- stan(model_code = stanmodelcode, model_name = "example",
            data = dat, iter = 200, chains = 1,
            control=list(c(adapt_init_buffer=10, adapt_term_buffer=10, adapt_window=10)),verbose =TRUE)

Current Version:
v2.12.0

I agree that would be a better warning message.
As an aside, we try to separate usage of "sample" and "draw", with a single sample being made up of multiple draws.

Add another message that "warmup is less than the recommended minimum 150 iterations" and then continue to dump a more detailed message that indicates it's just detail.


Assets file project.assets.json not found.

I imported the project exactly as I downloaded it from this repository, and I'm getting this error when I try to run it:
1>C:\Program Files\dotnet\sdk\7.0.306\Sdks\Microsoft.NET.Sdk\targets\Microsoft.PackageDependencyResolution.targets(266,5): error NETSDK1004: Assets file 'C:\Users\User\Desktop\Other programs\Chess-Challenge\Chess-Challenge-main\Chess-Challenge-main\Chess-Challenge\obj\project.assets.json' not found. Run a NuGet package restore to generate this file.

For context, C:\Users\User\Desktop\Other programs\Chess-Challenge\Chess-Challenge-main\Chess-Challenge-main\Chess-Challenge is the folder I have the project in.

Hi, can you try running dotnet restore in your command line?

That fixed it! Thanks!


CASM-4368: Implement prototype to delete cray-product-catalog data from main and sub cm for a particular product version

Summary and Scope
Summarize what has changed. Explain why this PR is necessary. What is impacted? Is this a new feature, critical bug fix, etc?
Is this change backwards incompatible, backwards compatible, or a backwards compatible bugfix?
Issues and Related PRs
List and characterize relationship to Jira/Github issues and other pull requests. Be sure to list dependencies.

Resolves [issue id](issue link)
Change will also be needed in <insert branch name here>
Future work required by [issue id](issue link)
Documentation changes required in [issue id](issue link)
Merge with/before/after <insert PR URL here>

Testing
List the environments in which these changes were tested.
Tested on:

<development system>
Local development environment
Virtual Shasta

Test description:
How were the changes tested and success verified? If schema changes were part of this change, how were those handled in your upgrade/downgrade testing?

Were the install/upgrade-based validation checks/tests run (goss tests/install-validation doc)?
Were continuous integration tests run? If not, why?
Was upgrade tested? If not, why?
Was downgrade tested? If not, why?
Were new tests (or test issues/Jiras) created for this change?

Risks and Mitigations
Are there known issues with these changes? Any other special considerations?
Pull Request Checklist

[ ] Target branch correct
[ ] Testing is appropriate and complete, if applicable
[ ] Is a new version being released? Update https://github.com/Cray-HPE/cray-product-catalog/wiki/CSM-Compatibility-Matrix
[ ] HPC Product Announcement prepared, if applicable

This had update_catalog.py changes as well so created new branch from develop so that only delete changes will be available


feat: capacity to persist volumes with custom StorageClass for MongoDB Helm chart

This PR kinda fixes the regression introduced by the MongoDB module refactoring with PR https://github.com/aneoconsulting/ArmoniK.Infra/pull/140 .
It gives back to the user the possibility to use custom persistent volume for the table storage by defining a custom storage class with the four following options inside the persistent_volume  variable :

storage_provisionner
reclaim_policy
volume_binding_mode
parameters (extra-parameters actually)

This PR also gives the possibility for the user to use the default values created by Helm by providing the module the value {} for the persistent_volume  variable.
Finally this PR adds the possibility to disable persistence by giving the null value for the persistent_volume variable.
WARNING : We strongly advice you to keep the reclaim_policy option to its default value (Delete). It is because the credentials used to connect to the database are stored in volumes that are generated at each deployment. You have to know that when performing dynamic volume provisioning, Kubernetes assigns the first fitted volume it finds for a pod requesting volume. Which means that if you retain your volumes upon destroying, subsesquent deployments will use volumes from a former deployment, and thus you won't be able to authenticate to MongoDB as Terraform won't be able to retrieve the data from the  former deployment in which the credentials in-use were created, and thus will pass inoperant credentials environment variables to the Helm chart.
WARNING : Disabling persistence causes data to be lost when a MongoDB pod crashes or when the StatefulSet monitoring the MongoDB pods somehow downscales.

I think we could rename the variable persistent_volume to persistence.

I think we should distinguish retention for persistent volume claims and retention for persistent volumes.


"as" + gerund-participial clause: is the clause PredComp or Comp?

As "is the prepositional analogue of the verb be" (p. 636), so it normally licenses a PredComp. But I am not sure about

I regard the solution as being satisfactory.

where being is explicit. Is the being-satisfactory clause just a Comp and satisfactory is the PredComp within it?

I'd say that just as he's being difficult doesn't have being difficult as a PredComp, nor should as being difficult.


Issue when i try authz

/usr/lib/ruby/1.8/net/http.rb:560:in `initialize': getaddrinfo: Name or service not known (SocketError)
i use my own host , linke this:
twurl authorize -u myname -p passwd --consumer-key Xdhr9Hz7DOw --consumer-secret 2TnM  -H https://baga3.org/b3tt/t/

Closing for age / inability to repro - please open a new issue if this still occurs with 0.9.3


Add golint test to CI

Before merging this PR, we need the PR #168 that adds support for golint with the revive package.
This action will highlight golint issues as the ones described in the issue #169.
This is PR is part of the effort for testing the code quality, as describe in the issue https://github.com/sustainable-computing-io/kepler/issues/161
Signed-off-by: Marcelo Amaral<EMAIL_ADDRESS>

@rootfs maybe we should first fix the lint errors (as in issue #169) before enabling this test here?

all the issues linter discovered, looks exciting!

cool! let's have another PR to fixes the issues.


Make SearchParameters initializer public

Addresses Issue: #94
Summary
This fixes an issue where the SearchParameters could be modified from outside the library.
By making the initializer public, the SearchParameters can be configured individually.
Discussion
I am not sure whether tests are necessary in this case, as this is a very simple fix changing only one line.

bors merge

bors merge


Reduce dependency on proxyquire

The next step in our transition into TypeScript is to move towards es6 style modules.  This helps ensure the d.ts is rich, and gives us a lot of the type safety we're looking for.
While trying this out, I ran into a roadblock with our usage of proxyquire in the tests.  Proxyquire depends on the ability to globally mutate the behavior of a function on a given module.  With es modules...  this isn't really possible anymore without some sort of DI abstraction.
In most cases, it didn't feel like the use of complete module overriding was needed.  Would it be possible to rewrite some of the tests so they do mocking at the network (nock) or file system level instead of the module level?  While it does mean running more unrelated code in unit tests, it would significantly reduce test complexity, and give more weight to end to end scenarios.
Looking for help with this one :) @stephenplusplus @callmehiphop

Welp, this is a tricky one. I'm not sure about this module, but applying this thought forward to our others, proxyquire is used for much more than blocking network requests. For example, we make sure the methods were properly promisified (this is done through our common module), and much more-- here's just one example from the first file I picked to show an example: https://github.com/googleapis/nodejs-storage/blob/fb88bd16b25e80962e630a300632d0d15817682c/test/file.js#L118-L125

Stubbing gcs-resumable-upload allows us to see that we are passing the correct user options to the third party module
Stubbing hash-stream-validation allows us to fake hashing validation failures and successes, to see if our code reacts properly

I'm definitely open to new testing strategies (like, if you read my bullet points above and were like, "Oh, that's terrible-- the right way to do that is ____"). If mocking modules is correct, however, and proxyquire simply isn't compatible with es modules, is there another solution we can look at?

I totally hear what you're saying.  I spent a few hours yesterday trying to work around this, and it uh... wasn't exactly fun  😂The mocking you're doing makes a lot of sense 👍
I think was running into problems because I was trying to just directly export functions instead of using an object instance.  I was specifically looking at util.ts.  Let me take a shot at using an es6 class, and exporting an instance of the class instead of directly exporting the functions.  After sleeping on it, I suspect that would let proxyquire keep on proxyquiring.

With all of the files converted over to es modules, I think we've done what we needed to do here.


New Subspecies taxon name is not properly parsed during post-processing

Jan can confirm: New subspecies is not marked with 'new subspecies' flag.

Fixed in the GREL code.

The issue is deeper than the GREL script in that NHMA names having been entered via the taxonomic ID rather than the auto-suggest name do not get a taxonspid number assigned, and that trips up the GREL script.

Commit: https://github.com/NHMDenmark/Mass-Digitizer/commit/c2719c61aa4307807b1085adf1e9fa111da722d9

I think the correct commit for the original issue is https://github.com/NHMDenmark/Mass-Digitizer/commit/357e1c0eabb53241e7269925a2a59e7e0be2162e


Determine feasibility of requiring containerD for Windows

Research if Windows customers need Docker or are willing to use containerD for service mesh

containerD
Docker

Confirmed that Windows Containers does utilize containerD for runtime.


Pip Installation fails - Double requirement given: numpy

nd2 version: 0.2.2
Python version: 3.8.10
Operating System: Ubuntu 20.x

Description
Can not install nd2 package using simple PIP
What I Did
pip install nd2[legacy]
$pip install nd2[legacy]
Collecting nd2[legacy]
  Using cached nd2-0.2.2.tar.gz (5.4 MB)
  Installing build dependencies ... error
  ERROR: Command errored out with exit status 1:
   command: /usr/bin/python3 /usr/lib/python3/dist-packages/pip install --ignore-installed --no-user --prefix /tmp/pip-build-env-mbhnace4/overlay --no-warn-script-location --no-binary :none: --only-binary :none: -i https://pypi.org/simple -- setuptools wheel cython numpy 'numpy==1.14.5; python_version=='"'"'3.7'"'"'' 'numpy==1.17.3; python_version=='"'"'3.8'"'"'' 'numpy==1.19.3; python_version=='"'"'3.9'"'"'' 'numpy==1.21.3; python_version=='"'"'3.10'"'"''
       cwd: None
  Complete output (2 lines):
  Ignoring numpy: markers 'python_version == "3.7"' don't match your environment
  ERROR: Double requirement given: numpy==1.17.3 (already in numpy, name='numpy')
  ----------------------------------------
ERROR: Command errored out with exit status 1: /usr/bin/python3 /usr/lib/python3/dist-packages/pip install --ignore-installed --no-user --prefix /tmp/pip-build-env-mbhnace4/overlay --no-warn-script-location --no-binary :none: --only-binary :none: -i https://pypi.org/simple -- setuptools wheel cython numpy 'numpy==1.14.5; python_version=='"'"'3.7'"'"'' 'numpy==1.17.3; python_version=='"'"'3.8'"'"'' 'numpy==1.19.3; python_version=='"'"'3.9'"'"'' 'numpy==1.21.3; python_version=='"'"'3.10'"'"'' Check the logs for full command output.

$ pip list | grep numpy
numpy                       1.22.3

Ah interesting!  Thanks for reporting, until I have time to debug, please try a conda install for now (from the conda-forge channel)

Thanks for looking into this.. for now.. i could unblock by using --no-build-isolation but no idea of consequences.

Also useful to know.  Thank you

Hi, I tried to reproduce the issue in Ubuntu and it just works. Could you make sure you're using the latest version of setuptools by running pip install -U setuptools?

@SachidanandAlle, please also try pip install -U pip and let me know how it goes for you

@SachidanandAlle, I have a feeling that if a pip upgrade didn't do it for you, then the last release v0.2.5 will do it.  I'm going to close this, but feel free to reopen if you can reproduce

pip install -U setuptools

This solves the problem. Thanks for looking into this


handle NAs in memory correction

closes #22
This PR fixes the issue where all subsequent values would be NA when all values for one sample were NA. The fix: Always use the last non-NA delta true prev in the calculation.
@thomas-muench If you agree with the changes proposed in this PR, please merge the PR and delete the branch fix_na_in_mem_corr.

@twollnik Thanks for the proposed changes; this does what we agreed on. I will merge the PR.


Draw collaboration diagram from picture for UC_1_1

bomberman/docs/tmp/IMG_20170202_203851.jpg

Moved to bomberman


Feature request: Skip group code when --help is set

To enhance the user experience it would really be better if I could switch off invoking the group script when --help is specified on the child.
The idea here is that the following should NOT print hello world.  And desirably, this should also turn off parsing main()'s argument validation as well.
Let's say a user invokes this on the shell:
my-cli some-command --help

And the cli command looks something like this:
import click

@click.group
def main() -> None:
    print("hello world")

@main.command()
def some_command() -> None:
    ...

if __name__ == "__main__":
    main()

This should NOT print "hello world"
The problem
There are multiple actions you might want to perform to make way for the underlying command.  Eg:

searching for a configuration file
configuring logging or output
opening a connection to a database

But this conflicts with the general use case of specifying --help which, to most users, means "just print some help text".
I particularly run into this when the group loads configuration and the configuration file is supposed to be in the current directory or it's parent.  In that case it is right for the group to fail when it finds no configuration.  Except that makes requesting help fail unexpectedly when you don't happen to be in the right directory.
Even if I could detect the command's --help from the group and bypass configuration setup, there would still be times when help would fail if, for example they didn't provide a mandatory option.
That is, most users would not expect there to be a semantic difference between:
some-group --conf /foo/bar some-command --help

and
some-group some-command --help

Both should be expected to just print the some-command help.
I realise this might undermin a designed structure of click.

See multiple previous discussions about this, this is not possible given Click's extremely dynamic nature.

Strange. I'd have thought it might be possible by adding an option to delay the execution of the group function until just before the validation and execution of the command.

@davidism Has something ever been considered around giving an option to delay the execution (invoke()) of a group (MultuCommand) until the child command is ready for it?  If enabled, such an option would knowingly surrender some of the dynamic behaviour of click` but allow the child command to determine when and if the group function executed.
My initial test draft suggested that this might be relatively easy and clean to implement.. I'm not claiming to have checked every edge case.
... That is to say, if I spent more time on this and submitted as a PR, would the idea have any chance of getting accepted?

I've closed this as not planned to indicate that I don't plan to add it.

@davidism okay that's a shame. It seemed you were closing it as impossible rather than unwilling.
Thanks anyway.

"It's a shame you're unwilling to accept any given suggestion that would add complexity to the library and maintenance of it" is not a kind thing to say. Please avoid leaving that sort of comment in the future.

@davidism please don't misquote me that is unkind. I simply said "it's a shame". In this instance I have three separate use cases for this. It would have been very helpful. It is that it won't get implemented. That doesn't mean I don't respect your decision, just expressing disappointment.


Live Lambda in VPC with AppSync

I've not been successful in getting Live mode to work with Lambdas in a VPC since the migration to AppSync.
I've created a VPC Interface for AppSync, and I can see the connection is successful from the bridge lambda.
The issue comes when publishing the message onto AppSync. My logs show the message is never received in AppSync, but I get no error in the bridge.
The only error is the eventual timeout when it receives no response within 3 seconds.
So essentially:

The bridge can connect to AppSync via the VPC interface
I do not see the published message in AppSync when the lambda is invoked via the runtime api.

Any ideas what this could be?

does your lambda have internet access?

No it does not. Does it need Internet Access? It has private vpc link to AppSync.


Error with merge_select or map update syntax in subquery

Environment

Elixir version (elixir -v): Elixir 1.9.0 (compiled with Erlang/OTP 22)
Database and version (PostgreSQL 9.4, MongoDB 3.2, etc.): Any
Ecto version (mix deps): 3.1.7 and master
Database adapter and version (mix deps): Any
Operating system: Linux

Current behavior
from(
	subquery(
		from(p in Post)
		|> select_merge([p], %{ extra_field: p.title + p.text })
	)
)

When trying to execute a query like this (or even just run Ecto.Query.Planner.plan on it) I get the following error:
     ** (Ecto.SubQueryError) the following exception happened when compiling a subquery.

         ** (KeyError) key :extra_field not found in: %Ecto.Query.SubqueryTest.Post{__meta__: #Ecto.Schema.Metadata<:built, "posts">, comments: #Ecto.Association.NotLoaded<association :comments is not loaded>, id: {:value, Custom.Permalink}, text: {:value, :string}, title: {:value, :string}}

     The subquery originated from the following query:

     from p0 in subquery(from p0 in Ecto.Query.SubqueryTest.Post,
       select: merge(p0, %{extra_field: p0.title + p0.text}))

Here is a PR with the failing test: #3128.
If I remove a layer of subquery like this, I do not get an error:
from(p in Post)
|> select_merge([p], %{ extra_field: p.title + p.text })

If instead of using select_merge I manually enumerate every field from the schema in a map, I do not get an error. This is the workaround I'm settling with for now:
from(
	subquery(
		from(p in Post)
		|> select([p], %{
			id: p.id,
			title: p.title,
			text: p.text,
			extra_field: p.title + p.text
		})
	)
)

A different error happens if I use select with map update syntax in a subquery instead of select_merge: select([p], %{ p | extra_field: p.title + p.text }). This may be a different issue, but I thought I had to mention this.
Expected behavior
Ecto allows for select_merge (and map update syntax) in subquery or throws a better error.

Ok, I made a small research …
The story begins here:
https://github.com/elixir-ecto/ecto/blob/052a9eb4985fdf678362d20ec1f1aba3bc7cfd16/lib/ecto/query/planner.ex#L263-L287
As you can see in this part there is nested call to subquery_select/3. In this we are checking if there are 2 different structs (which is not our use case). The important part of this check is that we all those cases:

2 maps
map + struct
struct + map

1st point is also not our use case as its later pattern-matched in another function clausule.
Our use case is any of 2nd or 3rd point. In both cases we have expr (after such nested call) set to {:%, [], [struct, {:%{}, [], fields}]} .
Now please take a look at 2nd quoted code part:
https://github.com/elixir-ecto/ecto/blob/052a9eb4985fdf678362d20ec1f1aba3bc7cfd16/lib/ecto/query/planner.ex#L1222-L1226
After collecting keyword we are forcing to create struct or raise!
Here is an hidden exception:
%KeyError{
  key: :extra_field,
  message: nil,
  term: %Ecto.Query.SubqueryTest.Post{
    __meta__: #Ecto.Schema.Metadata<:built, "posts">,
    comments: #Ecto.Association.NotLoaded<association :comments is not loaded>,
    id: {:value, Custom.Permalink},
    text: {:value, :string},
    title: {:value, :string}
  }
}

and here is a __STACKTRACE__:
[
  {:maps, :update,
   [
     :extra_field,
     {:value, :any},
     %Ecto.Query.SubqueryTest.Post{
       __meta__: #Ecto.Schema.Metadata<:built, "posts">,
       comments: #Ecto.Association.NotLoaded<association :comments is not loaded>,
       id: {:value, Custom.Permalink},
       text: {:value, :string},
       title: {:value, :string}
     }
   ], []},
  {Ecto.Query.SubqueryTest.Post, :"-__struct__/1-fun-0-", 2,
   [file: 'test/ecto/query/subquery_test.exs', line: 26]},
  {Enum, :"-reduce/3-lists^foldl/2-0-", 3, [file: 'lib/enum.ex', line: 1948]},
  {Kernel, :struct!, 2, [file: 'lib/kernel.ex', line: 2147]},
  {Ecto.Query.Planner, :collect_fields, 5,
   [file: 'lib/ecto/query/planner.ex', line: 1224]},
  {Ecto.Query.Planner, :subquery_select, 2,
   [file: 'lib/ecto/query/planner.ex', line: 274]},
  {Ecto.Query.Planner, :plan_source, 3,
   [file: 'lib/ecto/query/planner.ex', line: 233]},
  {Ecto.Query.Planner, :plan_from, 2,
   [file: 'lib/ecto/query/planner.ex', line: 224]},
  {Ecto.Query.Planner, :plan_sources, 2,
   [file: 'lib/ecto/query/planner.ex', line: 213]},
  {Ecto.Query.Planner, :plan, 3, [file: 'lib/ecto/query/planner.ex', line: 198]},
  {Ecto.Query.SubqueryTest, :normalize_with_params, 2,
   [file: 'test/ecto/query/subquery_test.exs', line: 42]},
  {Ecto.Query.SubqueryTest, :normalize, 2,
   [file: 'test/ecto/query/subquery_test.exs', line: 38]},
  {Ecto.Query.SubqueryTest,
   :"test normalize: merges subqueries schema fields with map fields", 1,
   [file: 'test/ecto/query/subquery_test.exs', line: 292]},
  {ExUnit.Runner, :exec_test, 1, [file: 'lib/ex_unit/runner.ex', line: 355]},
  {:timer, :tc, 1, [file: 'timer.erl', line: 166]},
  {ExUnit.Runner, :"-spawn_test_monitor/4-fun-1-", 4,
   [file: 'lib/ex_unit/runner.ex', line: 306]}
]

You can confirm it by replacing this line:
https://github.com/elixir-ecto/ecto/blob/052a9eb4985fdf678362d20ec1f1aba3bc7cfd16/lib/ecto/query/planner.ex#L237
with this code:
      e -> IO.inspect(e); IO.inspect(__STACKTRACE__); raise Ecto.SubQueryError, query: query, exception: e

I'm not following ecto source code, so I'm not sure in which place exactly is bug, so here are 2 my propositions:

expr in 1st code quote is wrong and therefore we are using bad function clausule for such use case.
I did not take a look at all of them, but I saw other clausule which worked on AST for maps. The only downside is that we would always return map regardless if we are merging with only struct keys or with extra keys. While it should work I'm not sure if it's not a breaking change.

The bug is in 2nd code quote and code should be changed there.
I'm not sure about it, because other code may use this clausule too.

@josevalim I could take a deeper look a bit later and share my thoughts if you wish.

@josevalim I know that lots of people are busy around logger topic, but there is no response for about week (to my reply) and more than month (for this issue at all). As said at end I'm not sure which of those 2 points is correct. If I would get a hint of what is expected here then I would be able to make a PR for that, but since I'm not familiar with planner I'm not sure which way of code change would be best in this case.

Hi @Eiji7! In this case, just a ping would have sufficed, because what most likely happened is that I just missed your comment. And regarding the issue as a whole, I didn't comment because I didn't have time to investigate it.
BUT you did have time, which is fantastic and very appreciated, so my reply is below.
In a nutshell, I think the error is correct. We can't select_merge a field that doesn't exist into a Post struct, because then the Post would become invalid. So subquery is behaving as expected! The question is why from(p in Post) |> select_merge([p], %{ extra_field: p.title + p.text }), without the subquery, is not raising. And it may be raising after all, it just happens that it raises only when the query is executed (it is a deferred check).

So I did a check and the regular query does raise when executed:
  1) test from: subqueries with select source (Ecto.Integration.SubQueryTest)
     integration_test/sql/subquery.exs:9
     ** (ArgumentError) struct %Ecto.Integration.Post{__meta__: #Ecto.Schema.Metadata<:loaded, "posts">, author: #Ecto.Association.NotLoaded<association :author is not loaded>, author_id: nil, bid: nil, comments: #Ecto.Association.NotLoaded<association :comments is not loaded>, comments_authors: #Ecto.Association.NotLoaded<association :comments_authors is not loaded>, comments_authors_permalinks: #Ecto.Association.NotLoaded<association :comments_authors_permalinks is not loaded>, constraint_users: #Ecto.Association.NotLoaded<association :constraint_users is not loaded>, cost: nil, counter: nil, id: 8, inserted_at: ~N[2019-11-02 09:40:16], intensities: nil, intensity: nil, links: nil, meta: nil, permalink: #Ecto.Association.NotLoaded<association :permalink is not loaded>, post_user_composite_pk: #Ecto.Association.NotLoaded<association :post_user_composite_pk is not loaded>, posted: nil, public: true, temp: "temp", text: "hello", title: nil, unique_users: #Ecto.Association.NotLoaded<association :unique_users is not loaded>, update_permalink: #Ecto.Association.NotLoaded<association :update_permalink is not loaded>, updated_at: ~N[2019-11-02 09:40:16], users: #Ecto.Association.NotLoaded<association :users is not loaded>, users_comments: #Ecto.Association.NotLoaded<association :users_comments is not loaded>, uuid: "612ffe3b-3e25-4d34-ba5f-bda390551a71", visits: nil} does not have the key :extra_field
     code: |> TestRepo.all

So everything is behaving as expected. The reason we can do the compile checking for subquery is that subqueries only allow a limited set of expressions. select is more generic, so we check when executing.
The solution is to return a tuple or a map with both post and extra_field keys.
Thanks @futpib for reporting and the failing test and thanks @Eiji7 for the investigation.


Add documentation demonstrating usage of new TrialResult for common tasks

This issues seems pretty outdated. One thing I did wonder as a follow on is do we have a notebook or guide on all the different simulation techniques one can use in Cirq (each of which can produce their own ***TrialResult objects) ?

I vote that we close this issue since this is quite outdated.  We can open a new issue if there are specific things that we want to document.