Multiplication of two-dimensional and three-dimensional tensors

There is a two dimensional tensor a[m,n], and a three dimensional tensor b[k,n,h]. What API should I use to multiply two dimensional tensors by three dimensional tensors to get a three dimensional tensor c[k,m,h] ?
Actually I can got it by:
import tensorflow as tf
import tensorly as tl
x=tf.constant([[[1,2],[3,7],[8,9]],
[[4,5],[6,10],[11,12]]],tf.float32)
a=tf.constant([[-0.70711,0.57735],
[0.0000,0.57735],
[0.70711,0.57735]])
reshape_A = tf.reshape(x, [2,6])
re = tf.reshape( tf.matmul(a, reshape_A), [3, 3, 2])
with tf.Session() as sess:
print(sess.run(re))
re=re.eval()
But is there an easier way?

@goljx This question is better asked on StackOverflow since it is not a bug or feature request. There is also a larger community that reads questions there.If you think we've misinterpreted a bug, please comment again with a clear explanation, as well as all of the information requested in the issue template. Thanks!

@goljx This question is better asked on StackOverflow since it is not a bug or feature request. There is also a larger community that reads questions there.If you think we've misinterpreted a bug, please comment again with a clear explanation, as well as all of the information requested in the issue template. Thanks!

@goljx Automatically closing due to lack of recent activity. Please update the issue when new information becomes available, and we will reopen the issue. Thanks!


test 002

Thanks for reporting - this issue is under review. This is a Microsoft Internal DevOps Bug ID # 359187

Thanks for reporting - this issue is under review. This is a Microsoft Internal DevOps Bug ID # 359187


Recursive import blocks webpack build without error

I accidentally created a module that references itself. While elm-make prints a clear error message, webpack will stall without any feedback. I had to fall back to elm-make to figure out the issue.

Can you provide an example?

Simple stupid mistake: I did a refactoring and left the original module name, creating a module that imports itself: https://github.com/tilmans/elm-ui-toolkit-clip-info-example/blob/master/ui/src/views/clip-info/HAL.elm
In the ui subdirectory run:
elm-make src/views/clip-info/ClipInfo.elm:
Your dependencies form a cycle:

  ┌─────┐
  │    HAL
  └─────┘

You may need to move some values to a new module to get rid of the cycle.

webpack --progress:
 66% 17/18 build modules

@tilmans this should be fixed on 4.0.0. Can you try it out?

closing as no response and I think it's fixed


unrecognized binary sections: ['_settings_handlers_area']

FAILED: bbc_microbit/samples/bluetooth/mesh/sample.bluetooth.mesh has unrecognized binary sections: ['_settings_handlers_area']
FAILED: bbc_microbit/samples/bluetooth/mesh_demo/sample.bluetooth.mesh_demo has unrecognized binary sections: ['_settings_handlers_area']
FAILED: nrf51_pca10028/tests/bluetooth/mesh_shell/bluetooth.mesh_shell has unrecognized binary sections: ['_settings_handlers_area']
FAILED: nrf52840_pca10056/samples/boards/nrf52/mesh/onoff-app/sample.bluetooth.mesh.onoff has unrecognized binary sections: ['_settings_handlers_area']
FAILED: nrf52840_pca10056/samples/boards/nrf52/mesh/onoff_level_lighting_vnd_app/sample.bluetooth.mesh.onoff_level_lighting_vnd has unrecognized binary sections: ['_settings_handlers_area']
FAILED: nrf52840_pca10056/tests/bluetooth/shell/bluetooth.shell has unrecognized binary sections: ['_settings_handlers_area']
FAILED: qemu_cortex_m3/samples/bluetooth/peripheral/sample.bluetooth.peripheral has unrecognized binary sections: ['_settings_handlers_area']
FAILED: qemu_cortex_m3/samples/bluetooth/peripheral_dis/sample.bluetooth.peripheral_dis has unrecognized binary sections: ['_settings_handlers_area']
FAILED: qemu_cortex_m3/samples/bluetooth/peripheral_hids/sample.bluetooth.peripheral_hids has unrecognized binary sections: ['_settings_handlers_area']
FAILED: qemu_x86/samples/bluetooth/mesh/sample.bluetooth.mesh has unrecognized binary sections: ['_settings_handlers_area']
FAILED: qemu_x86/samples/bluetooth/mesh_demo/sample.bluetooth.mesh_demo has unrecognized binary sections: ['_settings_handlers_area']
FAILED: qemu_x86/samples/bluetooth/peripheral/sample.bluetooth.peripheral has unrecognized binary sections: ['_settings_handlers_area']
FAILED: qemu_x86/samples/bluetooth/peripheral_dis/sample.bluetooth.peripheral_dis has unrecognized binary sections: ['_settings_handlers_area']
FAILED: qemu_x86/samples/bluetooth/peripheral_hids/sample.bluetooth.peripheral_hids has unrecognized binary sections: ['_settings_handlers_area']
FAILED: qemu_x86/tests/bluetooth/mesh_shell/bluetooth.mesh_shell has unrecognized binary sections: ['_settings_handlers_area']
FAILED: qemu_x86/tests/bluetooth/shell/bluetooth.shell has unrecognized binary sections: ['_settings_handlers_area']
FAILED: reel_board/samples/boards/reel_board/mesh_badge/sample.board.reel_board.mesh_badge has unrecognized binary sections: ['_settings_handlers_area']

Seeing this in sanitycheck output on master branch.

@Vudentz is this related to the “iterable” stuff?

It seems like this area was introduced by commit c20ff1150f717d79374997ed3b429b2449d2c3b8

If I understand this right, all that's needed is for the new section to be added to the right array in scripts/sanitycheck

@jhedberg, do you mind if I would rename the _bt_settings_area in scripts/sanitycheck to _settings_handlers_area ?

@jhedberg, do you mind if I would rename the _bt_settings_area in scripts/sanitycheck to _settings_handlers_area ?

@Laczen yes that's fine with me - there are no more users of _bt_settings_area, right?

@jhedberg, the area is not even there anymore.
@andrewboie, I am not a user of sanitycheck, but there has been a change in the storage of settings_handlers. Could you try in line 911 of scripts/sanitycheck to replace "_bt_settings_area" to "_settings_handlers_area". Thanks.

Fixed by #17500


New version: opentrack.opentrack version 2023.3.0

Pull request has been created with komac v2.2.0 :rocket:
Microsoft Reviewers: Open in CodeFlow

Hi @vikingnope,
This manifest removes Apps and Features entries that are present in previous PR versions. These entries should be added to this version, to maintain version matching, and prevent the 'upgrade always available' situation with this package.
(Automated response - build 876.)

As for the ProductCode where do I get it from?


Deploying issue

I'm trying to deploy this website using netlify. The build command that I used was - vuepress build docs and publish directory - docs/.vuepress/dist. According to the logs, everything seems to be fine, and it also gets built. Although, when I click on the link, the desired output is far from what gets built.
What gets built:
The url of the deployed website: https://blissful-jennings-dfa804.netlify.app
I tried running it locally, there seems to be no problem there at all.
After running locally:
Should I use some other command for deploying it? Or, is there something else that I'm missing?
Link to my repository: https://github.com/ananditavishnoi/my-blogsite

If you are building and pushing locally, you can refer to my files package.json and deploy.sh, and then run the command npm run deploy.

If you are building and pushing locally, you can refer to my files package.json and deploy.sh, and then run the command npm run deploy.

@zpj80231 I wanted to do this on Netlify. Is there a way to do this on any of the hosting platforms?

@zpj80231 I wanted to do this on Netlify. Is there a way to do this on any of the hosting platforms?


How to run regression

Inside testrunner if we have multiple testsuite and if we run using runSVUnit -s questa command then it will run all unit test template inside all testsuite.

@Gopalsuthar2308 How do we assign the testrunner? And can we have multiple testrunners?


uv__threadpool_cleanup non-op on Windows?

In Node.js, it looks like we've had a long standing bug when running threadpool jobs. See https://github.com/nodejs/node/pull/35021 for discussion. Calling uv_library_shutdown() resolves the problem on non-Windows systems by ensuring that threadpool jobs are shutdown properly. However, I notice that uv__threadpool_cleanup() is currently a non-op on _WIN32 and it's not entirely clear why.
Removing the #ifndef _WIN guards in uv__threadpool_cleanup() fixes the bug for me locally (Windows 10, VS19). I can open a PR but before I do I wanted to see if there was a specific reason the function was a made a non-op.
/cc @bnoordhuis @cjihrig @addaleax

c8abb29f68abf64bacf2dc5a483eedab84b52428 changed this in 2014, but since we’re using __attribute__((destructor)) on uv_library_shutdown(), I’m assuming that this isn’t being automatically run on Windows anyway.
I think just removing the #ifdef should be fine.

https://github.com/libuv/libuv/commit/c8abb29f68abf64bacf2dc5a483eedab84b52428 is one of two commits from https://github.com/joyent/libuv/pull/1381.

@addaleax :

I think just removing the #ifdef should be fine.

Yeah, not seeing anything in local testing that would suggest otherwise. I'll get a PR opened.


Consolidate persistent data in a sensible way

We currently have the ~/.amm file, which contains the command history in a crazy ad-hoc syntax. Soon we'll be adding cached bytecode (https://github.com/lihaoyi/Ammonite/issues/95), and cached dependency resolution (https://github.com/lihaoyi/Ammonite/issues/100) and no doubt more things in the future.
We need to figure out a more structured way of doing this (make ~./amm JSON? YAML? A folder with flat files? SQLite?) that won't become a huge mess in future.

I'd say make it a ~/.ammonite folder. I would write out the full name so it is easy to see which application created the folder. Having a directory structure inside won't make a mess I think. Something like this:
.ammonite
  cache
    ivy
      jarfile.jar
      jarfile2.jar
    scripts
      block1.class
      block2.class
  history
  user_settings

We can can store caches in single files too. If we use a directory structure backwards compatibility wouldn't be hard to solve either.

Sounds reasonable. Ivy jars I don't think we should copy; we just need to cache the path to the file since they'll all be cached in the ~/.ivy folder anyway, maybe with a hash. If the jar disappears, or doesn't match the hash, we can ask Ivy to re-download it.
I think the other plain-text-code data can live in YAML files, because their block notation would make the text both very easy to human-read (no escaping!), very easy to human/machine edit, and very easy to machine-append (so we don't need to re-write the entire history file or ivy-resolution file each time we add a new entry).

@laci37 do you want to pick this up as well and take a first pass at it? You're going to need it as part of https://github.com/lihaoyi/Ammonite/issues/95 anyway to put your class-files somewhere

Okay, I'll get started.

Thanks to @laci37 we now have a ~/.ammonite/ folder which currently contains:

history
ivycache.json
predef.scala

And lots of room to add more stuff. Even though we don't yet have proper concurrency semantics, I'm going to call this closed


OBJ 3D mesh import failure on windows with different files

Operating system or device:
Windows 10 and Godot 2.0 stable 64 bits binary (23/02/2016)
Issue description (what happened, and what was expected):
When I try to import an OBJ file as a 3D mesh into the scene, the importer fails
Steps to reproduce:
Import either RTS Orc Banner or RTS ORC Lumberjack model from https://shop.bitgem3d.com/collections/free-3d-models (it's free).
Link to minimal example project (optional but very welcome):

sorry dude, will not register to a site in order to test a model. Please directly link the model here and will reopen the issue.


fix: select: options change not reacting properly when value is an object

SUMMARY:

Adds object prop to SelectOption
Updates onOptionsChange callback to return values string array and its options object array
Updates unit tests to account for the newly added options argument returned by the onOptionsChange callback

GITHUB ISSUE (Open Source Contributors)
https://github.com/EightfoldAI/octuple/issues/562
JIRA TASK (Eightfold Employees Only):
ENG-46082
CHANGE TYPE:

[X] Bugfix Pull Request
[ ] Feature Pull Request

TEST COVERAGE:

[ ] Tests for this change already exist
[X] I have added unittests for this change

TEST PLAN:
Pull the PR branch and run yarn and yarn storybook. Verify the Select stories behave as expected.

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@045ba0e). Click here to learn what that means.
Patch has no changes to coverable lines.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #570   +/-   ##
=======================================
  Coverage        ?   84.96%
=======================================
  Files           ?      791
  Lines           ?    16920
  Branches        ?     5947
=======================================
  Hits            ?    14376
  Misses          ?     2478
  Partials        ?       66

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Support simple transitivity on join predicate pushdown

For query:
select t1.id, t1.value, t2.value
from t1
left join t2 on t1.id = t2.id
where t1.id > 1

We infer new  predicate t2.id > 1 and pushdown it to t2 Scannode.

select t1.id, t1.value, t2.value
from t1
right join t2 on t1.id = t2.id
where t2.id > 1

I think this query is also can be pushed down?

@chaoyli Of course. we could support right join and full out join. But inner join and left join are more common, and this PR has been tested in MeiTuan prod env two years. So I think we could merge this PR firstly, and then support  right join and full out join later.


modal button alignment

As can be seen in the lovely gifs of @MJochim the modal button alignment seems to be off by a few pixels (see close button here: https://github.com/IPS-LMU/EMU-webApp/blob/master/app/manual/GeneralUsage/pics/zoomHierarchy.gif)

happens as soons as the button's caption uses multiple lines


Add type parameter to global search results

related to https://github.com/globalfund/data-explorer-client/pull/5

:tada: This PR is included in version 1.1.0-develop.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

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


Final Integrated Code Documentation

Documentation for final integrated code with steps that can be taken care of in the future.

Please hold approval pending edits from @Mayank52455 - he has some stuff to add

Merged with #54


Null Object Reference

Describe your bug here.
 I TRIED to use PowerShell to create a log for the game but that didn't work! On Windows 7 it worked... Fine, to say the least. Most things were replaced by black boxes and the game crashed right before Stress, which ironically caused me a lot of "stress" as i was putting all my shit in OneDrive preparing to update to Windows 10. When i did, the game not only did it not work on Stress (obvious shit), the game didn't work. AT ALL. I configured my compatibility settings, ran it as admin and even troubleshooted the problem. Nope. It came up with something saying it was "incompatible". I'm redownloading the game for the 124th time this day.
Also, when i try to run the game through the zip file itself it gives the same error but when i close the game it says that files were modified or new ones were created.
Is this fixable, or do i have a shitty pc? A helpful answer would be appreciated. Thanks.
Ignore the first question below, didn't know what to put.
Command Prompt/Terminal logs (if existing)
No response
Are you modding a build from source or with Lua?
Source
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.

No


Add files via upload

Updated image to match current portal.
Resolves : MicrosoftDocs/112155

This image will be used in PR#112335

Hi @PatAltimore thank you for your feedback. You are correct, I have been using the GitHub UI to make changes to the files. Thank you for pointing the alternate approaches to edit multiple files in a go.
Hi @Court72, I do not see an option to update the file name. When I try to edit the uploaded file, I see the edit option greyed out. Please refer the below image.

Apologies if I am looking in the wrong place to make this name change.
Best regards,
Leela Rajesh.

Hi @leelarajesh-sayana. The PR review isn't able to offer technical authoring support. I'd try opening this PR in the private repo instead.
If you need help getting set up to work in the private repo, see Get started contributing to the Microsoft Learn platform.

Hi @LeelaRajesh-Sayana,
You can try using the GitHub VS Code editor in the browser. Just change .com to .dev in your PR URL and the editor launches. You should be able to rename the file in the editor. https://docs.github.com/en/codespaces/the-githubdev-web-based-editor.

#sign-off

Hi @Court72,
It looks like @LeelaRajesh-Sayana was able to rename the image. I can't sign off for some reason. This is okay to merge. Once this is merged, I'll sign off on https://github.com/MicrosoftDocs/azure-docs/pull/112335.
Thanks,
Pat

@PatAltimore @LeelaRajesh-Sayana - looks good. i've made a suggestion in https://github.com/MicrosoftDocs/azure-docs/pull/112335 that should be accepted after this PR is merged.


CIV-13272 Stop RPA for Judgment by Admission against Defendant LR/LIP

JIRA link (if applicable)
CIV-13272
Change description
Stop RPA for Judgment by Admission against Defendant LR/LIP
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[x] No


Different HomeKit sensor

Maybe use another HomeKit sensor like Occupancy?
Currently, with the contact sensor, it's hard to know whether the host is up or not.

Personally I don’t agree with this. Ability to ping an IP address seems to me much more related to a contact sensor than to an occupancy sensor.
If you want this change I’d be happy if  you submit a PR which provides the ability to configure whether the plugin exposes a contact sensor or occupancy sensor.


Support automatic check for unexpected exception

In my tests with Catch2, I would expect everything in test case to be checked for exceptions. If anything outside of REQUIRE_THROWS / CHECK_THROWS throws an exception, I consider it a failed test, and I want to get a message about which section / line caused the exception.
It seems Snitch doesn't support this scenario currently. For example
#define SNITCH_IMPLEMENTATION
#include "snitch_all.hpp"

#include <exception>

void command1() {}
void command2() {}
void command3() {throw std::runtime_error("error");}

TEST_CASE("commands") {
	SECTION("command 1") {
		command1();
	}
	SECTION("command 2") {
		command2();
	}
	SECTION("command 3") {
		command3();
	}
}

outputs:
starting a with snitch v1.1.1.e557246
==========================================
failed: running test case "commands"
          at <snitch internal>:0
          unhandled std::exception caught; message: whoops
==========================================
error: some tests failed (1 out of 1 test cases, 0 assertions, 9.610000e-05 seconds)

Only if I wrap command3() in REQUIRE_NOTHROW, will I get a nice error message. But wrapping every command in every test in macro is unfeasible.
Am I missing something, or is this a necessary tradeoff for smaller footprint?

Maybe generating the try block at SECTION level, and reporting section which has thrown, would be a big improvement. Possibly opt-in.

The branch nothrow_test contains the changes required to implement this feature -- still need to check the performance and test it.

Here is the performance impact (using the benchmark setup from the README):

Debug
before
after

Build framework
3.8s
3.8s

Build tests
68s
87s

Build all
71s
92s

Run tests
38ms
65ms

Library size
7.7MB
7.7MB

Executable size
35.3MB
40.4MB

Release
before
after

Build framework
4.9s
4.9s

Build tests
144s
201s

Build all
149s
206s

Run tests
29ms
26ms

Library size
1.3MB
1.3MB

Executable size
9.9MB
13.2MB

Ouch:

Binary size: +14% in debug, +33% in release.
Compilation time of the base library: unchanged.
Compilation time of the test code: +28% in debug, +39% in release.

Based on the above, I would say this is either a no-go, or it has to be configurable.
We could also consider your proposed alternative or only implementing this in SECTION(). The benchmark doesn't use SECTION() at all, so we won't see any impact there, and it will be a bit artificial. Still, it's fair to assume that there will be far fewer SECTION() than there should be CHECK() in any test code base.

I haven't tested this yet, but if I understand it correctly, this adds try blocks only to CHECK_*() macros. There's no way to portably report exact source of exception thrown inside TEST_CASE, but outside of CHECK/REQUIRE macro. For exceptions thrown outside of macros, user will still get only the test case name.
In that case, considering the speed/size impact, I think adding try blocks to SECTIONs could be overall better solution. You can at least narrow down the source of exception to section, not entire test_case, and it works for all exceptions (not just those in CHECK() macros). Could still be opt-in, just to be sure, since there's no good way to measure its impact.

I haven't tested this yet, but if I understand it correctly, this adds try blocks only to CHECK_*() macros. There's no way to portably report exact source of exception thrown inside TEST_CASE, but outside of CHECK/REQUIRE macro. For exceptions thrown outside of macros, user will still get only the test case name.

That is correct.

In that case, considering the speed/size impact, I think adding try blocks to SECTIONs could be overall better solution. You can at least narrow down the source of exception to section, not entire test_case, and it works for all exceptions (not just those in CHECK() macros). Could still be opt-in, just to be sure, since there's no good way to measure its impact.

I think that's a decent compromise. I can use the snitch self tests as a benchmark; these do use sections. It won't be as good a benchmark as the one above (where the tested code is very simple and cheap to compile, so we know the compilation time is mostly driven by the testing framework). But it's better than nothing.

One thing I still need to check: the test branch I created uses a macro to add the catch (...) { ... } block wherever it is needed, but the body of the catch is repeated verbatim (inline) everywhere. This may be a major component in the performance hit. I'd like to try putting the body of the catch inside a function instead, and see what happens.
(this would also enable adding a customizable exception handler later with little effort)

Debug
before
after

Build framework
3.8s
3.9s

Build tests
68s
71s

Build all
71s
75s

Run tests
38ms
50ms

Library size
7.7MB
7.6MB

Executable size
35.3MB
36.1MB

Release
before
after

Build framework
4.9s
5.0s

Build tests
144s
155s

Build all
149s
160s

Run tests
29ms
26ms

Library size
1.3MB
1.3MB

Executable size
9.9MB
10.5MB

It is indeed substantially better:

Binary size: +2% in debug, +6% in release.
Compilation time of the base library: unchanged.
Compilation time of the test code: +4% in debug, +8% in release.
Run time of the test code: same as before.

Definitely worth considering as this level.

Also note: adding try/catch in SECTION isn't feasible, because we'd need it to be of the form SECTION_BEGIN  (for try) and SECTION_END (for catch). But actually it isn't necessary; when an unexpected exception is thrown, we know what SECTION we're in (the test registry keeps track of it for us), and in fact the name of the current section is already displayed in the error message today:
int some_function() {
    throw std::runtime_error("nope");
}

TEST_CASE("test") {
    SECTION("section 1") {
        CHECK(some_function() == 2);
    }
}

Result:
failed: running test case "test"
          in section "section 1"
          at /home/tests/test.cpp:5
          std::exception thrown; message: nope

The only issue, I guess, is that the line number points to the test case declaration, and not the section. That would be fairly easy to change, if it desirable. But anyway, there's no need to add try/catch blocks there; we have all the information we need already.
This make me think; perhaps we can get even smaller overhead on catching exceptions inside CHECK(...), if instead of adding try/catch blocks, we simply record the current file/line and let the exception propagate up... I'll try that.

After a bit of refactoring, I managed to get this to work with almost zero net overhead (it did add a bit of overhead, but the refactoring was enough to gain back most of it by simplifying the assertion reporting functions).

Debug
before
after

Build framework
3.8s
3.8s

Build tests
68s
68s

Build all
71s
72s

Run tests
38ms
42ms

Library size
7.7MB
7.6MB

Executable size
35.3MB
35.7MB

Release
before
after

Build framework
4.9s
5.0s

Build tests
144s
145s

Build all
149s
150s

Run tests
29ms
26ms

Library size
1.3MB
1.3MB

Executable size
9.9MB
10.0MB

So I think this can be enabled all the time. PR to follow.

IMO it sounds better than current state. But, IMO, separate messages are the main point - to clearly distinct between cases when we know the reported location is known to be more/less exact, and when we know the location is just "somewhere inside code block starting at reported location". I would consider separate messages an advantage.
I don't have definitive opinion on this though, would be interested in other people's thoughts. If you don't feel convinced if tgus us a good idea, feel free to ignore it.

Ok, I'll have a think about how we can best express this in the event API.

I pushed an attempt at this. In summary:

If the exception happens inside a CHECK(...), the message will say "somewhere in check at file:line"
If the exception happens outside a CHECK(...) but inside a SECTION(...), the message will say "somewhere in section at file:line"
Else, the message will say "somewhere in test case at file:line"

Sounds good, thanks a lot.

Completed in https://github.com/snitch-org/snitch/pull/151. Thanks for the suggestion!


<!-- Unable to find the controller for path /api/login_check. The route is wrongly configured. (404 Not Found)

Unable to find the controller for path "/api/login_check". The route is wrongly configured. (404 Not Found)
Hey guys, i have this error when i try test the jwt implementation. I followed exactly the getting start from documentation and i have it as result.
Symfony 6.
And it's not the content type, I've tested it.
Someone have the same problem?

Thanks a lot!! Thats it!.


abstracted doc ids using enums

I removed the magic doc id numbers and moved them to an enum so that they could be better documented to understand what the code is doing.
If there are better names for the doc ids please feel free to change them

I've just found the single use of from_query_id with the same id.
Should both of these be put under the same function which abstracts which of the two fields it uses?
Do you expect this to stay as a single edge case?

The two uses of the same query_id is in fetch_thread_images, which should probably be refactored in a way that this doesn't happen, so I expect that to stay as a single edge case.
In general, thanks for the PR, but I'm not a big fan of the change. I recently removed the ReqUrl enum, see #433, because it really just added extra indirection. I'll keep the PR open for now, so that you, or someone else, may change my mind 😉.

I can understand the reasoning for removing the ReqUrl enum, given the extra indirection hides the actual url which gives some context, however in this case the indirection serves useful in giving meaning to magic numbers that newcomers to the code won't understand without implicit knowledge (that isn't documented anywhere).
Since you mention it, maybe I'll make some more commits refactoring the case mentioned for this pr to happen.
However I remember that there was a table of ids before, which now seems to have disappeared and thus the number of id's reduced. Am I remembering this correctly? And if so, maybe the real refactoring work should be done on removing the dependency on these ids if possible?

I remember that there was a table of ids before
Hmm, don't recall that, but I may be mistaken.

And true, having the ids in an enum does communicate the meaning of them more clearly, but it also means that you now have to look elsewhere to see the actual ID. And if you want to update it (which does happen quite frequently), you'll now have to go to a separate file, verify that the ID is only used the place you're editing, and then change it.
If the issue is that they're hard to understand, then indirection isn't the solution IMHO - a comment would be better, or perhaps some focused documentation in _graphql.from_doc_id?


Store error pages locally

I've stumbled on a bit of a quirk.
When 404/503 pages are generated they, of course, save to S3. This creates two problems when we encounter badly behaved bots.
Firstly, the 404 becomes relatively slow to load as it requires a round trip to AWS to pull the content. Not a big problem for the odd hit, but starts impacting availability when you have hundreds of hits per minute from a bad bot.
I've worked around this issue by blocking the problem URL in .htaccess, but then it automatically fetches the local error-404.html, which isn't updated.
I suspect 503s will do the same - returning an outdated error-503.html.
Ideally, these two files would bypass S3 and just be stored locally. Given it's only a few bytes I'm happy to store them locally, and there's substantial benefits to doing so.
Is there any way to do this now? Does it make sense to build this in?

The problem might be though that the local system is read only, so where would you store them locally? In the temp folder?

This would be related to #40
You would need to configure the Generated Asset Handler to write to the local file system instead of S3. Example would be -
SilverStripe\Assets\Storage\GeneratedAssetHandler:
    class: SilverStripe\Assets\Flysystem\GeneratedAssets
    properties:
      Filesystem: '%$League\Flysystem\Filesystem.localpublic'

Note then any random generated asset will write locally then.  Not sure what all else this would affect, like whether generating alternate images within your templateswith the helper functions would then write locally instead of s3 or not.  Right now we do this specifically for TinyMCE but TinyMCE has its own AssetHandler Config - https://github.com/silverstripe/silverstripe-s3/blob/ec39ebaa1d8b9370e667ae6d777081447cb8258b/_config/tinymce.yml#L17
Ideally would be great if the silverstripe/errorpage module would provide that functionality as well but right now it just uses the default configured GeneratedAssetHandler for SS.  You could extend ErrorPage and overwrite the get_asset_handler function to return a custom configured handler like TinyMCE is using.

The problem might be though that the local system is read only, so where would you store them locally? In the temp folder?

Absolutely - if there's a way to bake it into this addon then it should be configurable. Off by default makes sense. It's probably not a major issue, for example, if you're hosting the site on EC2 in the same region as the S3 instance. In my case the site is in New Zealand and the files are in Australia, so that's quite a bit of added latency (compared to local disk access, at least). In my instance I do have write access - purely using S3 because the site has many GB of attachments and disk space in NZ is expensive.

You would need to configure the Generated Asset Handler to write to the local file system instead of S3.

OK, this makes sense. I guess I'll test this out. For my purposes it's probably not a big deal if there's local images etc. - it's mainly uploaded PDFs I'm trying to offload

You could extend ErrorPage and overwrite the get_asset_handler function to return a custom configured handler like TinyMCE is using.

This might be the way, certainly in terms of making it configurable so it works in every use case rather than just my one. I'll explore this option too.


Seems it does not support self-exe rar archives

It would be nice if it could support self-exe rar archives.

Good idea. Any help with this would be great.


Jared/readme sub module

@ldanzinger Ready for review. Thank you!
Let me know what you think on these changes referencing the toolkit.

Should be good to go.

updates samples readme to give instructions on the proper location for the toolkit as it's needed for individual samples.


Blog_Page Added

Looks good to me! Next feature that we can add here is to retrieve blogs from database.


Adding Git And Github Content

Description 📜
Adding Git and Github Content on Python Domain

Adding some Content like what is git and GitHub and adding some pictures for better understanding.

[ ] Au#dio (Should be in mp3 format Includes speech clarity, Concise ,Low distortion)
[ ] Vi#deo (Animations, screen-recordings, presentations and regular explanatory films are all possibilties etc)
[x ] Documentation (Content Creation in the form of codes or tutorials)
[ x] Pictures about Git and Github Comparision

Domain of Contribution 📊

[ ] Android Dev #(Flutter)
[ ] Android Dev #(Java)
[ ] Android Dev #(Kotlin)
[ ] Backend Dev #(Java)
[ ] Backend Dev #(.NET)
[ ] Backend Dev #(PHP)
[ ] Backend Dev #(Python)
[ ] C/#CPP
[ ] Competitive #Programming
[ ] Cyber #Security
[ ] DS#A
[ ] Data#base
[ ] Datascience with #Python
[ ] Datascience with #R
[ ] Frontend Dev #HTML/CSS/JS
[ ] Frontend Dev #React/Angular/Vue
[ ] Go#lang
[ ] Interview #Prep
[ ] Java_#Domain
[ ] Java#Script
[ ] ME#RN
[ ] Machine #Learning
[ ] Open #Source
[x ] Python_Domain
[ ] Ru#st
[ ] Statis#tics
[ ] UI/#UX

Checklist ✅

[x ] I follow Contributing Guidelines & Code of conduct of this project.
[x ] I have performed a self-review of my own code or work.
[x ] I have commented my code, particularly in hard-to-understand areas.
[x ] My changes generates no new warnings.
[ ] I'm GWOC'21 contributor

Screenshots / Gif (Optional) 📸

@adityabisoi Close this pr


Rename healthcare employee to facility role in CSV Uploader

Remove repurposed field to now convey a person's role in a given facility.
This only changes the CSV uploader, which was lagging behind the GraphQL schema.

Good catch, fixed!


Fix potential github action smells

Hey! 🙂
I want to contribute the following changes to your workflow:

Avoid uploading artifacts on forks
Use 'if' for upload-artifact action
Avoid uploading artifacts on forks
Run tests on multiple OS's

(These changes are part of a research Study at TU Delft looking at GitHub Action Smells. Find out more)

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

Hi @ceddy4395
Thanks for your PR 🙌🏼
I have one question: I'm not sure I understand the reason behind "Run tests on multiple OS's", could you explain why running on [ubuntu-latest, ubuntu-20.04] instead of only ubuntu-latest would be better?

Hi @Jolg42
The reasoning behind this smell is that during testing, differences in OS's in terms of default installed dependencies etc. should be taken into account.
I'm interested to hear your thoughts!

@ceddy4395 Got it.
Could you revert the runs-on: ${{matrix.os}} changes?
Why?
On main we have ~ 206 jobs
https://github.com/prisma/prisma/actions/runs/8891585684/usage
With your changes I see ~380 jobs
https://github.com/prisma/prisma/actions/runs/8831591209/usage?pr=23965
So this is a massive increase in the number of jobs, and it looks like it did not catch any bug.
This means every new PR and merge to main will trigger all these additional jobs "for nothing", so I see this as a waste of time and resources. It also increases the number of things a developer needs to look after and probably more false positive as flaky tests might show up more often.
In the end, I don't see these as useful at the moment personally.
Note that we have some specific tests in https://github.com/prisma/ecosystem-tests/ for a lot of things.
Example: the docker tests on different OSes https://github.com/prisma/ecosystem-tests/tree/dev/docker


vector.get() doesn't seem to work anymore?

Hi all,
For some reason vector.get() doesn't work for me anymore. I use version 0.4.4 (April 12, 2015).
Any ideas?
Grtz,
Hans Willem

Sorry, wrong place to post this. Can't seem to delete my post? Also sorry for that. I'll close the issue.


When I try to run hikari, it returns this error (yesterday it worked fine, today I didn't modify the code at all and when I ran it didn't work)

Steps to reproduce

Install Visual Studio Code + Python
Set up virtual enviorment
Make python file
Install hikari and hikari-lightbulb
Paste

import hikari
import lightbulb

bot = lightbulb.BotApp(
    token="tokensnotheresoIdontgetmybotkilled",
    intents= hikari.Intents.all
)

@bot.listen(hikari.StartedEvent)
async def started(event):
    print("bot has started")

@bot.command
@lightbulb.command("ping","says pong")
@lightbulb.implements(lightbulb.SlashCommand)
async def ping(ctx):
    await ctx.respond("pong!")

bot.run()

Expected result
Bot should've run and be able to do a slash command
Actual result
(env) PS D:\Important Program\DiscordBot> & "d:/Important Program/DiscordBot/env/Scripts/python.exe" "d:/Important Program/DiscordBot/bot.py"

  oooo         o8o  oooo                            o8o       å…‰ 2.0.0.dev112 [a02498e1]
  `888         `"'  `888                            `"'       © 2021-present davfsa - MIT license
   888 .oo.   oooo   888  oooo   .oooo.   oooo d8b oooo       interpreter:   CPython 3.10.8
   888P"Y88b  `888   888 .8P'   `P  )88b  `888""8P `888       running on:    AMD64 Windows 10
   888   888   888   888888.     .oP"888   888      888       installed at:  D:\Important Program\DiscordBot\env\lib\site-packages\hikari
   888   888   888   888 `88b.  d8(  888   888      888       documentation: https://hikari-py.dev/hikari
  o888o o888o o888o o888o o888o `Y888""8o d888b    o888o      support:       https://discord.gg/Jx4cNGG

Thank you for using lightbulb!
I 2022-11-15 20:30:03,725 hikari.bot: you can start 1000 sessions before the next window which starts at 2022-11-15 20:30:03.725538-05:00; planning to start 1 session...
E 2022-11-15 20:30:03,876 hikari.gateway.0: encountered some unhandled error
Traceback (most recent call last):
  File "D:\Important Program\DiscordBot\env\lib\site-packages\hikari\impl\shard.py", line 874, in _keep_alive
    lifetime_tasks = await self._connect()
  File "D:\Important Program\DiscordBot\env\lib\site-packages\hikari\impl\shard.py", line 824, in _connect
    await self._send_json(
  File "D:\Important Program\DiscordBot\env\lib\site-packages\hikari\impl\shard.py", line 567, in _send_json
    await self._ws.send_json(data)
  File "D:\Important Program\DiscordBot\env\lib\site-packages\hikari\impl\shard.py", line 196, in send_json
    pl = data_binding.dump_json(data)
  File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.10_3.10.2288.0_x64__qbz5n2kfra8p0\lib\json\__init__.py", line 231, in dumps
    return _default_encoder.encode(obj)
  File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.10_3.10.2288.0_x64__qbz5n2kfra8p0\lib\json\encoder.py", line 199, in encode
    chunks = self.iterencode(o, _one_shot=True)
  File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.10_3.10.2288.0_x64__qbz5n2kfra8p0\lib\json\encoder.py", line 257, in iterencode
    return _iterencode(o, 0)
  File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.10_3.10.2288.0_x64__qbz5n2kfra8p0\lib\json\encoder.py", line 179, in default
    raise TypeError(f'Object of type {o.__class__.__name__} '
TypeError: Object of type function is not JSON serializable
I 2022-11-15 20:30:04,177 hikari.bot: bot requested to shut down
I 2022-11-15 20:30:04,178 hikari.bot: bot shut down successfully
I 2022-11-15 20:30:04,179 hikari.bot: successfully terminated
Traceback (most recent call last):
  File "d:\Important Program\DiscordBot\bot.py", line 19, in <module>
    bot.run()
  File "D:\Important Program\DiscordBot\env\lib\site-packages\hikari\impl\bot.py", line 783, in run
    loop.run_until_complete(
  File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.10_3.10.2288.0_x64__qbz5n2kfra8p0\lib\asyncio\base_events.py", line 649, in run_until_complete
    return future.result()
  File "D:\Important Program\DiscordBot\env\lib\site-packages\hikari\impl\bot.py", line 968, in start
    await aio.first_completed(self._closing_event.wait(), gather)
  File "D:\Important Program\DiscordBot\env\lib\site-packages\hikari\internal\aio.py", line 137, in first_completed
    await next(iterator)
  File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.10_3.10.2288.0_x64__qbz5n2kfra8p0\lib\asyncio\tasks.py", line 571, in _wait_for_one
    return f.result()  # May raise f.exception().
  File "D:\Important Program\DiscordBot\env\lib\site-packages\hikari\impl\bot.py", line 1257, in _start_one_shard
    await new_shard.start()
  File "D:\Important Program\DiscordBot\env\lib\site-packages\hikari\impl\shard.py", line 624, in start
    await aio.first_completed(self._handshake_event.wait(), asyncio.shield(keep_alive_task))
  File "D:\Important Program\DiscordBot\env\lib\site-packages\hikari\internal\aio.py", line 137, in first_completed
    await next(iterator)
  File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.10_3.10.2288.0_x64__qbz5n2kfra8p0\lib\asyncio\tasks.py", line 571, in _wait_for_one
    return f.result()  # May raise f.exception().
  File "D:\Important Program\DiscordBot\env\lib\site-packages\hikari\impl\shard.py", line 874, in _keep_alive
    lifetime_tasks = await self._connect()
  File "D:\Important Program\DiscordBot\env\lib\site-packages\hikari\impl\shard.py", line 824, in _connect
    await self._send_json(
  File "D:\Important Program\DiscordBot\env\lib\site-packages\hikari\impl\shard.py", line 567, in _send_json
    await self._ws.send_json(data)
  File "D:\Important Program\DiscordBot\env\lib\site-packages\hikari\impl\shard.py", line 196, in send_json
    pl = data_binding.dump_json(data)
  File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.10_3.10.2288.0_x64__qbz5n2kfra8p0\lib\json\__init__.py", line 231, in dumps
    return _default_encoder.encode(obj)
  File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.10_3.10.2288.0_x64__qbz5n2kfra8p0\lib\json\encoder.py", line 199, in encode
    chunks = self.iterencode(o, _one_shot=True)
  File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.10_3.10.2288.0_x64__qbz5n2kfra8p0\lib\json\encoder.py", line 257, in iterencode
    return _iterencode(o, 0)
  File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.10_3.10.2288.0_x64__qbz5n2kfra8p0\lib\json\encoder.py", line 179, in default
    raise TypeError(f'Object of type {o.__class__.__name__} '
TypeError: Object of type function is not JSON serializable
E 2022-11-15 20:30:04,223 asyncio: Task exception was never retrieved
future: <Task finished name='heartbeat (shard 0)' coro=<GatewayShardImpl._heartbeat() done, defined at D:\Important Program\DiscordBot\env\lib\site-packages\hikari\impl\shard.py:675> exception=AssertionError()>
Traceback (most recent call last):
  File "D:\Important Program\DiscordBot\env\lib\site-packages\hikari\impl\shard.py", line 690, in _heartbeat
    await self._send_heartbeat()
  File "D:\Important Program\DiscordBot\env\lib\site-packages\hikari\impl\shard.py", line 672, in _send_heartbeat
    await self._send_json({_OP: _HEARTBEAT, _D: self._seq}, priority=True)
  File "D:\Important Program\DiscordBot\env\lib\site-packages\hikari\impl\shard.py", line 566, in _send_json
    assert self._ws is not None
AssertionError
E 2022-11-15 20:30:04,225 asyncio: Task exception was never retrieved
future: <Task finished name='poll events (shard 0)' coro=<GatewayShardImpl._poll_events() done, defined at D:\Important Program\DiscordBot\env\lib\site-packages\hikari\impl\shard.py:694> exception=AssertionError()>
Traceback (most recent call last):
  File "D:\Important Program\DiscordBot\env\lib\site-packages\hikari\impl\shard.py", line 695, in _poll_events
    assert self._ws is not

System info
hikari (2.0.0.dev112) [a02498e1]
located at D:\Important Program\DiscordBot\env\lib\site-packages\hikari
CPython 3.10.8 MSC v.1933 64 bit (AMD64)
Windows DESKTOP-CGUU963 10 10.0.19044 AMD64 Intel64 Family 6 Model 158 Stepping 10, GenuineIntel

Further info
No response
Checklist

[X] I have made sure to remove ANY sensitive information (bot token, passwords, credentials, personal details, etc.).
[x] I have searched the issue tracker and have made sure it's not a duplicate. If it is a follow up of another issue, I have specified it.

Can confirm this bug ^

This is just a typo leading to a nasty error because you ended up passing a function as the intents. Will close as NAB


Escape plus sign in the username

Apparently I was able to create Google account (not email) which has + in the username. And to get master token for it, + should be replaced with %2B.
Fixes #260

haha what de heck is this google thing... :D nice find and fix thou! Thanks


Fixed typo which was referring to 'imports' section and not 'setup'

I noticed that there is a v minor typo in the testing guide.  The second code block for app/banner.component.spec.ts duplicates the '(imports)' text

I signed it!

Good catch! I have a large number of changes stacked up in pr #2396 so I've incorporated this one in that PR.


[BUG] Improve the logo sizing the moksh text is not visible

@akshitagupta15june please assign this issue to me under GSSoC'23.

ok

Please assign it to me @akshitagupta15june  mam , I am just 6 min late.


Angular 12 support

Update library to support Angular 12

:tada: This issue has been resolved in version 1.1.0-next.1 :tada:
The release is available on:

v1.1.0-next.1
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 1.1.0 :tada:
The release is available on:

v1.1.0
GitHub release

Your semantic-release bot :package::rocket:

@blalasaadri maybe take a look at this repo for Angular 12 support

@blalasaadri maybe take a look at this repo for Angular 12 support

Thanks for the tip, I'll check it out.


 lang attribute conflict with inserted Tumblr code

Tumblr prepends the following code to all served pages:
<!DOCTYPE html>
<script>var __pbpa = true;</script><script>var translated_warning_string = 'Warning: Never enter your Tumblr password unless \u201chttps://www.tumblr.com/login\u201d\x0ais the address in your web browser.\x0a\x0aYou should also see a green \u201cTumblr, Inc.\u201d identification in the address bar.\x0a\x0aSpammers and other bad guys use fake forms to steal passwords.\x0a\x0aTumblr will never ask you to log in from a user\u2019s blog.\x0a\x0aAre you absolutely sure you want to continue?';</script><script type="text/javascript" language="javascript" src="http://assets.tumblr.com/assets/scripts/pre_tumblelog.js?_v=a3e5e7f1b487e101133066aadcff3cde"></script>

...Before the <html> tag. I've heard browsers deal with code like this by sighing and constructing a set of "phantom" <html> and <head> tags. Clearly it's not too much of a problem, as Tumblr has been serving pages forever, but I'm concerned that the software and APIs that rely on the lang attribute may get tripped up on this.
Possible options include stuffing the language in a <meta>, which seems like it could work while flouting validation. (Of course, the inserted script automatically screws that up anyway.) I only worry about its deprecation.
Using the DOM inspector in Chrome & Firefox doesn't show anything too amiss... but am I missing something?

Turns out the HTML spec allows for this tomfoolery.


Add "toggle ray" button to toggle features panel

Overview
Adds a button to turn the hand ray behavior on and off. The hand ray will toggle between default (on if not near a grabbable), and AlwaysOff.

Changes

Fixes: #6087
Add new script for calling SDK functions for enabling / disabling rays. Not adding any new SDK functionality, so don't think this needs tests.
Added a button visual for toggling rays (added by Yoon)

Verification
Verified by testing in editor.

This optional section is a place where you can detail the specific type of verification
you want from reviewers. For example, if you want reviewers to checkout the PR locally
and validate the functionality of specific scenarios, provide instructions
on the specific scenarios and what you want verified.
If there are specific areas of concern or question feel free to highlight them here so
that reviewers can watch out for those issues.
As a reviewer, it is possible to check out this change locally by using the following
commands (substituting {PR_ID} with the ID of this pull request):
git fetch origin pull/{PR_ID}/head:name_of_local_branch
git checkout name_of_local_branch

/azp run

/azp run mrtk_docs

/azp run


Implement user impersonation feature season

Rabbit season

Failed Test
Failure Summary
Logs

[chromium] should display the about us section correctly.
The "About" section was not displayed within the expected time, and the title was also not displayed.
Logs ↗

Test_RateLimitExceeded
failure_message: Failedfailure_text: === RUN   Test_RateLimitExceeded    api_test.go:11: Rate limit exceeded--- FAIL: Test_RateLimitExceeded (...
Logs ↗

Flaky Test
Failure Summary
Logs

[chromium] should login with credentials correctly correctly.
The login request to the server failed with a 404 Not Found error.
Logs ↗

[chromium] should display user profile information correctly.
The user profile information was not displayed correctly, as the element 'User ID: eli3cruz' was not found.
Logs ↗

[chromium] should display error message for invalid login correctly.
The expected HTTP status code 401 was not received, instead a function was returned.
Logs ↗

[chromium] should return list of users correctly.
The API call to get the list of users failed with a 404 Not Found error.
Logs ↗

View Full Report ↗ ⋅ Docs


 So I cleaned up all references to them and deleted any code for handling them.
The diff is mostly find-replace of blender_shader_sockets for blender_shader_sockets_or_texture_slots or deindenting after deleting an if branch.

@scurest : can you please rebase it?

Rebased.


Add post: Quietly re-opening the service to new claim submissions in July and August

 Why we experimented with quietly re-opening the claim window at the end of July DH


set up automated deployment from dev into a dev site,  and automatic releases on GitHub

For example, the dev site could be https://scadnano.org/dev, or https://dev.scadnano.org.
This will help us to keep the stable version more stable with less frequent updates (still involving merging dev into master), while still allowing people to test new features who do not want to install Dart and run a local scadnano server.
We should also do automated releases on the dev branch, so that people using the dev branch can see what features have been introduced.
This should be accompanied by a workflow where we make new branches for implementing most new features/bugfixes, which are then merged into dev with a pull request.

This looks as though it might be impossible to do with GitHub pages as the host:
https://github.community/t/can-i-publish-multiple-branches-of-a-repository-on-github-pages/10314

An idea I can think of is configuring the github-pages workflow to checkout master branch, and build into a build folder, and then checkout the dev branch and build into the build/dev folder. Then serve build on gh-pages.

The idea should be that only the dev branch is deployed to the dev server when changes are committed to dev, leaving master alone. So these should be two separate GitHub actions, one triggered by committing to master, and the other triggered by committing to dev.

I think we can do this with just one workflow because if a change is commited to dev, then the action would rebuild both master and dev anyways. The master build wouldn't change, but the dev build would, so effectively, only the dev build is changed. So the idea for one workflow is we always build both master and dev whenever either branches are pushed.
Nevertheless, the idea of having two workflows is also nice to avoid excessive rebuilding, so that would be accomplished as follows:

A new workflow should be added, titled something like gh-pages-dev which checks out dev branch and gh-pages branch , builds into gh-pages-repo/dev, and deploys it.

The current gh-pages workflow should be modifed so that it checks out gh-pages branch and master branch, builds into gh-pages-repo, and deploys it. Currently, the workflow does not pull from gh-pages branch and just overwrites whatever is currently deployed. This will no longer work because we need to preserve the dev subdirectory.

I think I see. So the idea is that deployment is always done from gh-pages to the GitHib pages site. But when the workflow is the dev branch workflow, only the dev/ subdirectory is being modified. So after it is deployed to the GitHub pages site, it won't change what is shown at https://scadnano.org, only what is at https://scadnano.org/dev

builds into gh-pages-repo/dev, and deploys it.

Did you mean to say "builds into gh-pages/dev, and deploys it."? What's gh-pages-repo?

I used gh-pages-repo to designate the name of the temporary repository for which the gh-pages branch is cloned in. I wanted to distinguish the branch name from the repository name since there isn't a repository named gh-pages, but yes, the idea you have is essentially what I had in mind. Inside the repository for the gh-pages branch, there would be a dev subdirectory where all the builds for dev would go to.

I can try manually building dev into the gh-pages branch and see if this idea can work.

Alright here it is: https://scadnano.org/dev/

Great, I'll try it out on my next commit. Thanks!

I merged changes from another branch into dev a few minutes ago, but it appears that the gh-pages deployment didn't happen (you can see the last deployment was yesterday):
https://github.com/UC-Davis-molecular-computing/scadnano/actions?query=workflow%3A"github+pages"

Somehow, the dev website is up: https://scadnano.org/dev/
But it does not have changes that I just implemented in the latest merge into dev. For example, in the dev branch, you can now right-click on helices in the side view to bring up their context menu (same as in the main view). But on https://scadnano.org/dev/, right-clicking on helices in the side view still just brings up the default browser context menu.

There shouldn't be a deployment. I haven't set up the workflow yet :)
I'm surprised dev is still up. Perhaps the master gh-pages workflow doesn't need to change then, and I can just focus on setting up the gh-pages-dev workflow

Because of issues with cd in bash script, I had to tweak the method slightly, but the result is the same. The dev branch will deploy in a dev subdirectory.
The change is that rather than having two directories dev-repo and gh-pages-repo, the directories are nested:
dev-repo and dev-repo/gh-pages-repo. Then, the action builds into dev-repo/gh-pages-repo/dev before serving gh-pages-repo/
The same idea applies to deploying master, using master-repo instead of dev-repo.

Thanks!
I'm a bit confused by some of the terms.

Because of issues with cd in bash script

Which bash script is this? I see that https://github.com/UC-Davis-molecular-computing/scadnano/blob/dev/.github/workflows/gh-pages-dev.yml has bash commands in it. I suppose that turns into some bash script when the action executes? (Even though the bash script itself is not a file in one of our repos)

the directories are nested: dev-repo and dev-repo/gh-pages-repo

Where are these directories exactly? I see gh-pages-repo referenced here:
https://github.com/UC-Davis-molecular-computing/scadnano/blob/dev/.github/workflows/gh-pages-dev.yml#L19
Although I'm not exactly sure where it is a directory. Is this a directory that temporarily exists while the GitHub Action is executing?

Which bash script is this? I see that https://github.com/UC-Davis-molecular-computing/scadnano/blob/dev/.github/workflows/gh-pages-dev.yml has bash commands in it. I suppose that turns into some bash script when the action executes? (Even though the bash script itself is not a file in one of our repos)

Ah yes, my bad, I used the term "bash script" when because the issue I was having was similar to that if you try to run cd in a bash script. I don't know if a github action is a bash script exactly.

Although I'm not exactly sure where it is a directory. Is this a directory that temporarily exists while the GitHub Action is executing?

Yes, those directories are temporary directories created by the Github action.

Closed in PR #342


Update wokwi-7segment.md

the segment default is  anode(positive side)。

Thanks!
I understand that the existing text needs some improvement, so draw more attention to the "common" attribute. @ishotjr, can you please take this one?


No progress bar is shown when downloading an interface

When "Download Interface" is selected there is no indication that the interface is being downloaded other than the small progress bar under the launcher's app icon in the taskbar:

It might be beneficial to display a progress bar in the launcher as well. Perhaps in place of the "Download Interface" button.

It appears that this issue is related to the broken client download URLs. Fixed in PR #39.


🐛 Fix android didChangeAppLifecycleState infinite looping when request permission

Fix android didChangeAppLifecycleState infinite looping when request permission.
Solution refer to: https://github.com/Baseflow/flutter-geolocator/issues/1056

Would be better if we can use Completer here.

In this case, does Completer still needed?

The Completer still stands out IMO.

Updated to use Completer. Thanks.

I'd also want to request the screen recordings which can tell the actual behavior difference.

During an actual test, I realized that the prompt won't show if you are already inside the picker, so the permission requests always end immediately. If the permission is denied, you will never enter the picker.


dev: remove the container from Katana

Describe the enhancement request
Currently, in your testing, we start a mocked mongo DB that we store in the Katana instance running. This allows us to keep it 'static which otherwise causes the container to be stopped when the instance is dropped.
A cleaner approach could be to have a function which allows to start a container on a port (so something like start_container_with_mongo(port: u16), enclose the container in a Box and leak the box in order to keep the container running for the duration of the testing.
TBD is this approach works and allows for cleaner code.

What is the status of this?

I think the current implementation is better tbh


Create guidelines in Readme for getting started in the project

Currently the readme doesn't cover how to get started with Prisma, a new database and adding your own GitHub app. This needs to be added so that we can make it easier for contributors getting started.
Bonus: This would be great as it's own page on the site too, and we will create a separate issue after we complete the guide.
So we need to document:

The required .env variables

DATABASE_URL
GITHUB_ID
GITHUB_SECRET
NEXTAUTH_URL (this could be included by default)

Creating a new database (and getting a connection string) - Either a docker image or Supabase is handy.
How to setup the tables in database  npx prisma db push.
Setting up a new GitHub app (getting the GITHUB_ID and a GITHUB_SECRET).

I'll take this since I should hopefully know best on how to get the project running 😂

Adding images that I might need for the guide on getting GITHUB_ID and GITHUB_SECRET values.


Fix broken untrusted CLI calls in client

Fix untrusted calls in client that tried to use trusted keystore instead of untrusted one
This was introduced in a previous refactoring, as part of
https://github.com/Polkadex-Substrate/polkadexTEE-worker/pull/30
Resolves #82

I believe I was wrong. In the case of PDEX we need to supply the beneficiary owner and proxy signature (which are in untrusted keystore) to the rpc api.
So, probably we shouldn't have a trusted keystore at all, but rather use the same for onchain and gateway
The intention of the trusted subcommand was to clearly separate confidential offchain stuff (where we have the same function calls, but targeted at offchain stf, like transfer) from publicly visible onchain stuff. In our case, this distinction  may not be neccessary.
Anyway, this can be left for later refactoring. I approve this PR

The reason for the refactoring were the new RPC calls and their respective CLI commands for Polkadex. I saw there was a lot of duplicated code, but failed to understand there was this clear distinction between trusted and untrusted calls. So we ended up with less duplicated code, but all the commands used the trusted keystore. This should be rectified by this PR.
However, this also means that the untrusted commands use some functions that are in /stf/*. Either we have some common place to share these functions (maybe /stf/* is not the right place?) or we accept that we duplicate quite a bit of code, which is problematic imho.
For Polkadex we have both, trusted and untrusted calls. What Bigna did in https://github.com/Polkadex-Substrate/polkadexTEE-worker/pull/86 are all on the untrusted side. The RPC calls (place_order, cancel_order, withdraw, get_balance) are on the trusted side. Is that correct @brenzi ?

well, for PolkaDEX, trusted could probably be dropped. We should only distinguish direct and indirect calls, which doesn't exactly map to trusted / untrusted

I opened an issue for this improvement, @brenzi : https://github.com/Polkadex-Substrate/polkadexTEE-worker/issues/90


Time to live feature

Just implemented it for my purposes. Look on test1 - it's self-explainable ))
https://github.com/inferrna/memoize

Very nice! Let me take a look :)

I like it a lot and would definitely accept a pull request for this feature. Just one favor I'd ask for -- could you write a sentence or two about this feature in the README?

After some thoughts I decided that using seconds as ttl is not rusty-way at all. And created another version - please, look also at ttl_as_duration branch where Duration is using instead of just seconds. If you ok with it, I'll create pull request with updated Readme.

yes, looks good. Viscerally I liked SecondsToLive, but thinking that some applications may prefer sub-second TTLs, this is probably best.

#2 has been merged and version 0.1.5 published to crates.io.


Store accounts into different subdirectories

Instead of all accounts JSON files going into the same accounts/ directory, create each account file into a subdirectory accounts/<givenName>/<domain>/<xyz>/, with:

xyz being the lowercased first three letters of the username.
domain being the domain name for the user's email.
givenName being the user's givenName, lowercased (either facebook or email in our use-case).

Example file: ClotildeL5.json
{
  "email"<EMAIL_ADDRESS>  "givenName": "Facebook",
  "middleName": "10202848354846732",
  "surname"<EMAIL_ADDRESS>  "username": "ClotildeL5"
}

It should be store in directory accounts/facebook/email-not-provided.local/clo/ directory.

please check if it's done then we bump version and get it works as required

added some more tweaks to handle properly default application name and also use application name via script argument
so this task should be marked as done


Upgrade GH core to 1.0-pre4

There is a huge delay for MapMatchingTest when switching from 1.0-pre3 to pre4
There seems to be a problem in MapMatching.createVirtualEdgesMap. Is this due to https://github.com/graphhopper/graphhopper/pull/1751 ? Maybe traverseToClosestRealAdj is too slow now or some infinite/recursive loop without end?

There seems to be a problem

Is there (only) a performance problem or also some problem with correctness ?

It just does not finish. So either very slow or some infinite loop.

It could be traverseToClosestRealAdj that is now somehow stuck in infinite recursion

I'll  have a look.

Yes there appears infinite recursion in traverseToClosestRealAdj and yes this is caused by #1751. But rather than saying this got broken in #1751 I would argue the pattern used in this method is just not supported by our (graph) API for traversing the graph. This only worked prior to #1751 because of the way the QueryGraph  edge iterator was implemented, but with #1751 this does not work anymore and it never worked for the (non-query/standard) graph. Take a look at this example using a plain GraphHopperStorage:
 @Test
    public void recursionDoesNotWorkForEdgeExplorers() {
        //
        // 4-0-1-2
        //     |
        //     3
        EncodingManager em = EncodingManager.create("car");
        FlagEncoder encoder = em.fetchEdgeEncoders().get(0);
        GraphHopperStorage graph = new GraphHopperStorage(new RAMDirectory(),
                em, false, new GraphExtension.NoOpExtension()).create(100);
        graph.edge(0, 4, 10, false);
        graph.edge(0, 1, 10, false);
        graph.edge(1, 2, 10, false);
        graph.edge(1, 3, 10, false);
        EdgeExplorer explorer = graph.createEdgeExplorer(DefaultEdgeFilter.outEdges(encoder));
        // iter0 iterates edges at node 0
        EdgeIterator iter0 = explorer.setBaseNode(0);
        iter0.next();
        assertEquals("1 0-1", iter0.toString());
        // we are not done iterating all edges at 0, but now we create 'another' (NOT) iterator that iterates edges at node 1
        EdgeIterator iter1 = explorer.setBaseNode(iter0.getAdjNode());
        iter1.next();
        // cool!
        assertEquals("3 1-3", iter1.toString());
        // ok now lets get back to iter0 again and retrieve the next edge, its "0 0-4", right ?
        iter0.next();
        // ouch! its not
        System.out.println(iter0);
        // iter0 and iter1 are independent right ?
        assertNotSame("NO THEY ARE NOT", iter0, iter1);
    }

The problem is that the EdgeExplorer basically returns itself (and NOT some kind of fresh iterator object) when we call setBaseNode. So after the second time calling setBaseNode the previous iterator (iter0) is more or less invalid (should not be used anymore, or actually it is just the same object as iter1!. In fact iter0/1 is also the same object as the explorer!.


Symfony 5.3.9

Coverage increased (+0.1%) to 96.383% when pulling 3700a046c46bff3b0c93ded277fe940aee8f57e4 on symfony-5.3.9 into 0c105b4fa336d60e996475e5df8a98c18c658d9a on master.


Update r-base to 4.2.0

Checklist

[X] Used a personal fork of the feedstock to propose changes
[X] Bumped the build number (if the version is unchanged)
[X] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Ah sorry missed the duplicate pull request here https://github.com/conda-forge/r-base-feedstock/pull/205


Image optimization

Images often represent the majority of bytes downloaded on a web page, so image
optimization can often be a notable performance improvement for large scale web app.
I'm going to open a PR where I added image-loader to compress images in the Webpack process: https://github.com/mxstbr/react-boilerplate/compare/master...soundsgood-co:image-optimization?expand=1
In my implementation, images optimization is done both in development and production mode.
So my question is, do you think it is a good idea as it allows us to see how images are compressed during our development process and potentially adjust settings or do you think it could slowdown things too much and it's better to compress images only for production?

I'd think it is best to have the compression on both production and development in case there is an degradation of the images.
Can you define "slowdown things too much" - does the compression take a while?

I have only tested it on a very small app and there is no impacts.
I also think it is better to have compression in development but I was wondering if it could be a drawback for a larger app.

Done by the great @Ndpnt in #518!


Functions with deactivated blocks may not be executed correctly in the simulation

Describe the bug
Functions with deactivated blocks will not fully be executed or get skipped in the simulation.
The only exception is, if the deactivated block is at the end of the function. In that case the function will be executed as expected. (Without the last deactivated block) If you deactivate multiple blocks at the end the bug will yet occur.
Most of the time when the bug occurs, the function will be skipped and the rest of the program will be executed normally. Sometimes though, the blocks before the deactivated block will be executed normally, but all blocks after the deactivated one will be skipped.
To Reproduce

Select any robot with a simulation
Create a new program with a function, that has at least 2 blocks in it.
Deactivate a block in function that is not the last block of the function.
Run the program in the simulation.
The function will be skipped.

Expected behavior
The function will fully executed and only the deactivated blocks will be skipped.
Screenshots

See #215


Documentation / missing info

I wasn't able to find the parsing option "attachComment" in the Esprima documentation - only found it through a third party's issue list as a request to make use of it.
Is there a more up to date version of the docs? If so, website should probably point to it, else docs need updating!
Thanks.

Our documentation needs an overhaul, particularly for the upcoming 3.x series. Meanwhile, I'll check in a quick mention of this particular option.


Improve coverage

New PR to track further test coverage improvements

@fanwgwg Could you help improve coverage for these UI classes?

CompletedTasksPanel.java
UiManager.java


Auto download toolchain in test project

Downloads jdk 17 toolchain if it's not setup locally.
Only for toolchain test

I haven't dig deep into that issue. But I'm curious about the root cause. Do you have more information?

AFAIK Gradle will not download JDKs automatically if it can't find them.  It recommends some 3rd party plugins for this: https://docs.gradle.org/current/userguide/toolchains.html#sec:provisioning
It's possible to install JDKs manually and have Gradle recognise them but I've had issues with this on Windows as I think it requires windows registry settings to point it to the JDK locations.  I could be wrong on this.
The CI azure pipeline specifies jdk 17 and since Gradle is running on that it can find JDK 17.  I imagine if the CI build moved to JDK 21 then this test would fail.  This PR should fix that issue although the CI checks may take slightly longer to run.

I see.
Instead of adding this 3rd party plugin. What about limit the related test cases to only run on java 17 using the annotation @EnabledOnJre({JRE.JAVA_17})?

I'm easy - whichever you prefer

Thank you @Arthurm1!


Can .webp be added?

Unfortunately, images in *.webp format are not supported. Can this be added?

Hi @peterprokurist - I am not sure what you mean, for me it works fine.
I just opened this image https://www.gstatic.com/webp/gallery/1.webp, copied and pasted it without any issue in Foundry.
What are you trying to do exactly?


Implement scheduled task pattern for FastHotStuffEventLoop timers

Current dependencies on/for this PR:

feature/proof-of-stake

PR #649

PR #648

PR #650

PR #654

PR #656   👈

This comment was auto-generated by Graphite.


Signing Device with Vault details: Not showing any NFC scan option.

https://github.com/bithyve/bitcoin-keeper/assets/62699947/eda78176-90c7-4a89-9c63-54c2b851ddf0

This should show something like this.

Still there is no NFC scan option when we click 'proceed'.
Tested on keeper app v 1.1.9(281)

Verified this issue on keeper app v 1.1.11(296)


caching OSM Layer in Xamarin Forms

Does anyone has an example of caching an OSM layer in a xamarin forms app?
I want to intercept the tile loading and want to use a cached tile (if available in the cache and if not expired) or else I want to download the tile from OSM and save it into my cache.
Or can anyone guide me into the right direction howto do this?

There has been a recent PR that uses caching of the tile layers. The purpose of this MR has been for testing but it can probably help you as well. https://github.com/Mapsui/Mapsui/pull/1530. These changes are in master and you probably work with 3.x so it will not work one on one.

You could do something like this:
BruTile.Cache.FileCache fc = new FileCache(...);
BruTile.Predefined.KnownTileSources.Create(KnownTileSource.OpenStreetMap, persistentCache: fc);


Update missing fonts

Add two missing fonts from the newest bundle.js

The array length must be increased to 68 (here)

Sorry, I wrote that when I was half asleep rofl


Circular dependencies

These prevent at least Rollup from compiling for web in a way that works
Circular dependency: node_modules/msgpack-lite/lib/bufferish.js -> node_modules/msgpack-lite/lib/bufferish-array.js -> node_modules/msgpack-lite/lib/bufferish.js
Circular dependency: node_modules/msgpack-lite/lib/bufferish.js -> node_modules/msgpack-lite/lib/bufferish-array.js -> commonjs-proxy:/Users/Corey/Documents/workspace/mkr/node_modules/msgpack-lite/lib/bufferish.js -> node_modules/msgpack-lite/lib/bufferish.js
Circular dependency: node_modules/msgpack-lite/lib/bufferish.js -> node_modules/msgpack-lite/lib/bufferish-buffer.js -> node_modules/msgpack-lite/lib/bufferish.js
Circular dependency: node_modules/msgpack-lite/lib/bufferish.js -> node_modules/msgpack-lite/lib/bufferish-uint8array.js -> node_modules/msgpack-lite/lib/bufferish.js
Circular dependency: node_modules/msgpack-lite/lib/bufferish.js -> node_modules/msgpack-lite/lib/bufferish-proto.js -> node_modules/msgpack-lite/lib/bufferish.js
Circular dependency: node_modules/msgpack-lite/lib/encode.js -> node_modules/msgpack-lite/lib/encode-buffer.js -> node_modules/msgpack-lite/lib/write-core.js -> node_modules/msgpack-lite/lib/ext-packer.js -> node_modules/msgpack-lite/lib/encode.js
Circular dependency: node_modules/msgpack-lite/lib/encode.js -> node_modules/msgpack-lite/lib/encode-buffer.js -> node_modules/msgpack-lite/lib/write-core.js -> node_modules/msgpack-lite/lib/ext-packer.js -> commonjs-proxy:/Users/Corey/Documents/workspace/mkr/node_modules/msgpack-lite/lib/encode.js -> node_modules/msgpack-lite/lib/encode.js
Circular dependency: node_modules/msgpack-lite/lib/decode.js -> node_modules/msgpack-lite/lib/decode-buffer.js -> node_modules/msgpack-lite/lib/read-core.js -> node_modules/msgpack-lite/lib/ext-unpacker.js -> node_modules/msgpack-lite/lib/decode.js
Circular dependency: node_modules/msgpack-lite/lib/decode.js -> node_modules/msgpack-lite/lib/decode-buffer.js -> node_modules/msgpack-lite/lib/read-core.js -> node_modules/msgpack-lite/lib/ext-unpacker.js -> commonjs-proxy:/Users/Corey/Documents/workspace/mkr/node_modules/msgpack-lite/lib/decode.js -> node_modules/msgpack-lite/lib/decode.js

@acoreyj
Let me know the command to reproduce the message above.
I have never faced the problem on compiling it with browserify though.

@kawanet
I don't have a simple reproduction setup. Basically if you compile a project with rollup you will see this printout. You can see more about it here and here.
I'm using rollup to build a bundle that requires fortune-indexeddb which requires msgpack-lite.
Yup it does work with the way browserify, what I ended up doing is creating a browserify bundle of fortune-indexeddb and include that. This may be more of an issue of fortune-indexeddb not including a bundled distribution.
Not sure what would be for you to do other than switching everything to javascript modules.
Although is there a reason that your browser field in the package.json doesn't just point to the bundle in dist?

It's simple:
// bufferish-array.js
var Bufferish = require("./bufferish");

// bufferish.js
var BufferArray = exports.Array = require("./bufferish-array");

Here's the circle. Pretty nasty one.


Build 2.07 290, the wallet type covered wallets

Fixed in https://github.com/AlphaWallet/alpha-wallet-ios/pull/1272.
Will be in TestFlight


Major changes for upcoming 2.0 release

@pgobriensap fyi I made the remote dev branch equivalent to main branch (destructive measure because I made a mistake earlier when rebasing dev with main branch) and this PR moves everything from our devAuthoringIntegration branch on top of the dev (equivalent to main) branch. I say this because you have to through away your local dev branch then.

@pgobriensap I'd do rebase and merge in ca 1 hour unless I hear from you otherwise.

Looks good to me! Thanks for the heads up on the dev branch rebasing.


Release Report Introduction

Write up the introduction for the release plan
An overview of the project, purpose/motivation (i.e. the problem you are trying to solve), targeted users. You can take this information from your project proposal.

Expected delivery date:

November 4 to 5


Support for config client.toml

$ fxcored config client.toml
Error: couldn't get the value for the key: client.toml, error:  unknown configuration key: "client.toml"

$ fxcored config -h
...
Available Commands:
  app.toml    Create or query an `.fxcore/config/apptoml` file
  config.toml Create or query an `.fxcore/config/config.toml` file
...

Is it possible to you add support for "client.toml" configuration file, such as changing the default "chain-id"?

There are some differences for client.toml
use fxcored config to query client.toml information
user fxcored config chain-id fxcore Modify chain-id


create account: include TLA when checking availability

This fixes false positives when checking account availability.

@vgrichina @Patrick1904
There is a problem with this change because now it's not checking account availability properly on Send Money and Recover using Seed Phrase pages. You can fix it by passing 'accountId' to SendMoneyFirstStep and RecoverAccountSeedPhraseForm component, but the idea for AccountFormAccountId was that it will check for both:

if accountId is available for creating
it accountId exists
without additional changes for parent components.

So I think here:
https://github.com/nearprotocol/near-wallet/blob/master/src/components/accounts/AccountFormAccountId.js#L66
it should still check account for value, and also this change:
https://github.com/nearprotocol/near-wallet/blob/master/src/components/accounts/CreateAccount.js#L37
should be moved to handleChangeAccountId in AccountFormAccountId component. If you need to handle it for Create Account situation only you can use type prop.

@vgrichina @Patrick1904
Or maybe adding ACCOUNT_ID_SUFFIX should be moved to checkNewAccount and createNewAccount in wallet.js?

@marcinbodnar great catch! Agree that we can re-think. Added a temp fix now.


Operation which depends on the network operation

Hello!
I have one more error with operations usage
So I have an operation which download data and then another operation parse this data.
But sometimes I have a crash on parsing data cause the data to parse is nil. It seems that sometimes parsing operation starts earlier than the downloading operation finishes. Is it a possibility to find out the reason of such crash? Or may be you can tell me why so by looking at my code?
class GetAndSaveAuthorOperation: GroupOperation {
    init(guid: String, context: NSManagedObjectContext) {
        let url = NSURL(string: GET_AUTHOR_SERVLET_URL)!
        let authorRequest = NSMutableURLRequest(URL: url)
        authorRequest.HTTPMethod = "POST"
        authorRequest.HTTPBody = String("\(POST_PARAM_GUID)=\(guid)").dataUsingEncoding(NSUTF8StringEncoding)

        let downloadAuthor = DownloadDataOperation(request: authorRequest)

        let parseAuthor = ParseAuthorOperation(mainContext: context)
        parseAuthor.injectResultFromDependency(downloadAuthor)

        super.init(operations: [parseAuthor, downloadAuthor])
    }
}

class DownloadDataOperation: GroupOperation, ResultOperationType {
    let request: NSMutableURLRequest
    private(set) var result: NSData?

    init(request: NSMutableURLRequest) {
        self.request = request

        super.init(operations: [])

        let task = NSURLSession.sharedSession().dataTaskWithRequest(request) { data, response, error in
            if let error = error {
                print("Can't download! Cause ...")
            }
            else {
                self.result = data
            }
        }

        let taskOperation = URLSessionTaskOperation(task: task)
        self.addOperation(taskOperation)
    }
}

class ParseAuthorOperation: Operation, AutomaticInjectionOperationType {
    var requirement: NSData?

    let mainContext: NSManagedObjectContext
    var privateContext: NSManagedObjectContext!

    init(mainContext: NSManagedObjectContext) {
        self.mainContext = mainContext

        super.init()
    }

    override func execute() {
        guard !cancelled else { return }

        self.privateContext = NSManagedObjectContext(concurrencyType: .PrivateQueueConcurrencyType)
        self.privateContext.parentContext = self.mainContext

        do {
            /// Here I have a crash sometimes, cause requirement is nil
            let wrappedJson = try NSJSONSerialization.JSONObjectWithData(requirement!, options: .MutableLeaves) as? Dictionary<String, AnyObject>

            if let author = wrappedJson?[JSON_PARAM_DATA] as? [String: AnyObject] {
                parse(author)
            } else {
                print("cant unwrap author json")
            }
            finish()
        } catch let jsonError as NSError {
            print("ParseAuthorOperation error")
            finish()
        }
    }

Well, this is because the NSURLSessionTask operation has an async callback - but there is no inherent dependency here between this and the containing group. When that block is invoked is undefined with respect to the state of the operation. You might want to look at NetworkOperation or writing your own wrapper.


Remove automatic daemon deployment

Goals
Move to all self-serve daemons
Implementation
No longer deploy new daemons with releases
(we can manually shut down the running instances and then they won't get restarted on deploy)

Glad to see these go away.


Storage amount incorrect

I only see 4GB of storage in my Pi's 32GB SanDisk card. Can you make a 16 or 24 GB version just for 32GB sd cards?

same I have the same issue

Check out issue #111.


Link to Additional Page

Hi!
Before Updating the Bootstrap Template i was able to Link all Pictures on the Frontpage to an Additonal Page.
The Code was
');`
But now it seems this has been completly changed. Can you please help me out?
Thanks

That code is just an anchor link. Where did you put it, and more importantly: how?

After this right behind
          $('#last10items .carousel-inner').append('

Ah, the carousel example. Well, that's because that example now uses background images. You could use captions or try to make it work with linked images.

Okay... Thanks for that information, but i guess i have no clue how to get this done ;)

If updated the example on the demo and the wiki, it now shows a button link to the gallery instead of the current picture's filename.
I guess that's more useful.

Awesome! Thank you!


the anchor point position of HingeJoint  bug

rp3d::Transform t;
mBody->addCollisionShape(pShape, t, rp3d::decimal(mass));
//create hingeJoint
....
//if( t.getPosition() != rp3d::Vector3::zero())
//{
// the hingeJoint's anchor point position is wrong! I have tested it.
// May you fixed the bug?  thank you!
//}

In the code you posted, at the first line you create a transform with zero position, then you add a collision shape to the body using this transform but you never update the "t" transform. Therefore, this transform  will always have zero position for the rest of your code.
Is there some code that you have not posted where you update the "t" transform at some point ? Moreover, you say that the hingeJoint's anchor position is wrong talking about t.getPosition() but why would t.getPosition() be the anchor position ? "t" is a transform representing the initial relative position of your collision shape w.r.t the body. It is not the anchor position.
Maybe you could also post the hinge joint creation code ?

//create static rigid body
rp3d::Transform t(rp3d::Vector3(0,0,0), rp3d::Quaternion::identity);
rp3d::RigidBody* mStaticBody = m_pWorld->createRigidBody(t);
mStaticBody->setType(rp3d::BodyType::STATIC);
//create dynamic rigid body, initial position is Vector3(0,0,0), init Orientation is Quaternion(0,0,0,1)
rp3d::RigidBody* mDynBody = m_pWorld->createRigidBody(t);
mDynBody->setType(rp3d::BodyType::DYNAMIC);
mDynBody->enableGravity(true);
//add shapes for dynamic rigid body
rp3d::Vector3 halfExtend(0.5,0.5, 0.5);
rp3d::BoxShape* pShape = new rp3d::BoxShape(halfExtend);
rp3d::Transform relative(rp3d::Vector3(1,0,0), rp3d::Quaternion::identity);
rp3d::ProxyShape* proxyShape = mDynBody->addCollisionShape(pShape, relative, rp3d::decimal(50));
//create HingeJoint
rp3d::HingeJointInfo jointInfo(mStaticBody, mDynBody, rp3d::Vector3(-1,0,0), rp3d::Vector3(0,0,1));
m_pWorld->createJoint(jointInfo);
The result of HingeJoint simulation is wrong.    May you  debug the code?  thank u.

rp3d::Transform relative(rp3d::Vector3(0,0,0), rp3d::Quaternion::identity);
when relative Transform is identity, HingeJoint simulation is right.
I have used your physics engine  doing a project.   I write  a lot of test demo to test your engine. believe me it is a bug,   and in my project, we must use this feature( relative is not identity).

if(t.getPosition() != rp3d::Vector3::zero()).   this is not code,  just a word I express.( if transform is not identity the bug appear.).  so just look at this code.
//create static rigid body
rp3d::Transform t(rp3d::Vector3(0,0,0), rp3d::Quaternion::identity);
rp3d::RigidBody* mStaticBody = m_pWorld->createRigidBody(t);
mStaticBody->setType(rp3d::BodyType::STATIC);
//create dynamic rigid body, initial position is Vector3(0,0,0), init Orientation is Quaternion(0,0,0,1)
rp3d::RigidBody* mDynBody = m_pWorld->createRigidBody(t);
mDynBody->setType(rp3d::BodyType::DYNAMIC);
mDynBody->enableGravity(true);
//add shapes for dynamic rigid body
rp3d::Vector3 halfExtend(0.5,0.5, 0.5);
rp3d::BoxShape* pShape = new rp3d::BoxShape(halfExtend);
rp3d::Transform relative(rp3d::Vector3(1,0,0), rp3d::Quaternion::identity);
rp3d::ProxyShape* proxyShape = mDynBody->addCollisionShape(pShape, relative, rp3d::decimal(50));
//create HingeJoint
rp3d::HingeJointInfo jointInfo(mStaticBody, mDynBody, rp3d::Vector3(-1,0,0), rp3d::Vector3(0,0,1));
m_pWorld->createJoint(jointInfo);
the simulation result in graph,  the hinged joint not rot around anchor position, it rot around between anchor position and Dynamic rigidbody.

I am sorry for my English.    Just test the code above,  I think you may extends your demo cube class to receive the shape transform.  and also modify the synchronization code to graph.  then it will easy to reappear the bug.


Fix the issue of instance creation failure

…values. The auth_token should not be sent in the response. It should be removed from the dict. Instance creation was failing because it was trying to delete same auth_token key twice. Fixed the same.

What this PR does / why we need it: Instance creation fails with KeyError for auth_token.
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #77
Special notes for your reviewer: @himanshuvar @wisererik
Release note:

Codecov Report

Merging #78 into master will increase coverage by 0.04%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #78      +/-   ##
==========================================
+ Coverage   39.12%   39.16%   +0.04%
==========================================
  Files          13       13
  Lines         887      886       -1
  Branches       91       91
==========================================
  Hits          347      347
+ Misses        517      516       -1
  Partials       23       23

Impacted Files
Coverage Δ

orchestration/api/instances.py
22.06% <ø> (+0.1%)
:arrow_up:


Compiler warnings on temp storage

BlockScan storage variable causes warnings:
__shared__ typename cub::BlockScan<int, X_THREADS> temp_storage;
warning: shared memory variable with non-empty constructor or destructor (potential race between threads)

This looks like a typo -- did you mean to use cub::BlockScan<...>::TempStorage? https://www.godbolt.org/z/8h5T93


Properties estimatedAvailableDateTime and quantities in plannedQuantities should be changed to required.

Property plannedQuantities  is optional in CheckAvailabilityOfSellerProductById and CheckAvailabilityOfCustomerArticleById.
It doesn't make sense supplying plannedQuantities without also specifying properties estimatedAvailableDateTime and quantities.
Therefore should Properties estimatedAvailableDateTime and quantities in plannedQuantities be changed to required.

Done within https://github.com/papinet/papiNet-API/commit/a87eaac286d7e9bf3297cd9f10f844e4236068d8.


Feature/v2 ivo

Changed IBAN
Adds RequireMemberTest

Only tests for isValid and getRequiredMembers

Looks very nice. Thanks Ivo! :)


Minor findings in installation, startup and usage of EMBArk

Describe the bug
During the installation the following errors came:

Starting EMBArk displays these issues:

Uploading a firmware file works fine but the path looks like this:

The progress bar did not go to 100% but the san has been finished:

I was able to reproduce this issue more times. I know the scan is finished when the fan slows down in the computer but the progress bar does not go to 100%.
I entered these parameters for the scan:

but the report contains these:

It would be very useful to show real version numbers and proper data in the report, because if I have more scans difficult to check the real versions if the data is incomplete.
To Reproduce
Steps to reproduce the behavior:

EMBArk installation (default mode)
Start EMBArk: sudo ./run-server.sh
Use the firmware available here:
https://cyberforat.squat.net/openwrt/binary_images/linksys_official/WRT54GS_3.17.4_US_code.zip
See error

Expected behavior
Please fix the errors if posible.
Screenshots
Attached above.
Desktop (please complete the following information):

OS: Ubuntu 22.04.1 LTS Desktop

I checked the same on Kali 2022.3.
During the EMBArk installation there were these warnings:

I use a brand new workstation with 11th gen i7 CPU with latest BIOS but I got this more times:

and the final one:

Usage of EMBArk:
Same fakepath as on Ubuntu and on Kali:

The progress bar also stopped again but the scan has been finished for sure:

and the final report is incomplete:

OS: Kali 2022.3
VMware Workstation Pro 16

Hi torabi,
the uploader and the reporter problem are there for anti code-injection stuff.
They will eventually be back to working as expected.
The progress-bar overhaul is on the TODO-list. It has some design flaws at the moment.
the warnings etc in #53

pipenv warnings are related to this https://github.com/pypa/pipenv/issues/5208

pipenv warnings are related to this pypa/pipenv#5208

Thank you for the resource. We have such warnings in multiple areas in EMBA.

Hello Benedikt,
I checked today the upload and reporting in EMBArk and I have these info:

I added these parameters:

and I got this back:

The final report would be important I think because the user would store only the html pages of the scans.
Could you check it on your side please? Thank you.

@torabi12 please open a new ticket for better tracking
Thank you


Reason Required max char limit

Hi,
First of all really great job with the tool, we love it. can the reason required bumped unto 256 please ? it does say in the documentation that 100 is the max.
Thank you
Sunil

You can change the maximum by using a configuration profile.

`Key: ReasonMaxLength
Available for: Privileges 1.5.3 and later.
Value: Integer
Note: This must be a positive value below 100.
If the ReasonRequired key's value is set to true, this optional key specifies the maximum number of characters the user can enter as the reason for becoming an admin. If not set, the value defaults to 100.
If a value of greater than 100 is specified or if the ReasonMaxLength key is set to a value less than or equal to the value set for the ReasonMinLength key's value, the value of the ReasonMaxLength key is set to the default value of 100.`

Could you please explain why the 100 character limit it not sufficient for your environment? Thanks.


About CSS and javascript limitation

Your project seems really good but I wanted to ask; why is there a limitation towards JS and CSS? Because I would like to implement leaflet.js, survey.js and Jquery UI.
So is there a way to remove that limitation? Because I can't find a documentation

There is no limitation, one can add those javascript libraries to Flaskex if you wish.


I can't generate on a second request

Hello, I'm using the lib in a project, but I can generate the normal pdf in the first request, but if I make a second request, it doesn't call, it just waits, so I can get another request, I have to rebuild the api, does anyone know how to solve this?

how about this
https://github.com/rdvojmoc/DinkToPdf/issues/119

public void ConfigureServices(IServiceCollection services)
{
// Add converter to DI
services.AddSingleton(typeof(IConverter), new SynchronizedConverter(new PdfTools()));
}
i think, this is your issues

I'm having the same issue, has anyone solved this problem?
I already add this code
builder.Services.AddSingleton(typeof(IConverter), new SynchronizedConverter(new PdfTools()));

and also I already add load library manually
string libraryPath = "";
if (RuntimeInformation.IsOSPlatform(OSPlatform.Windows))
{
    // Load .dll for Windows
    libraryPath = "libwkhtmltox.dll";
}
else if (RuntimeInformation.IsOSPlatform(OSPlatform.Linux))
{
    // Load .so for Linux
    libraryPath = "libwkhtmltox.so";
}
else if (RuntimeInformation.IsOSPlatform(OSPlatform.OSX))
{
    // Load .dylib for macOS
    libraryPath = "libwkhtmltox.sylib";
}

var loadContext = new CustomAssemblyLoadContext();
var fullpath = Path.Combine(Directory.GetCurrentDirectory(), libraryPath);
IntPtr libraryHandle = loadContext.LoadUnmanagedLibrary(Path.Combine(Directory.GetCurrentDirectory(), libraryPath));
// Pastikan library berhasil dimuat
if (libraryHandle == IntPtr.Zero)
{
    Console.WriteLine("Failed to load the library.");
    return;
}

Console.WriteLine("Library loaded successfully.");

var builder = WebApplication.CreateBuilder(args);

but the problem still same, the second request response properly, I suspect libwkhtmltox is still stuck in the process, as we know we use external library here, and it do not managed properly by dotnet core.
So is there anyone already solve this problem?
btw I user docker linux here

same on maui windows app


[DOCFIX] Add the memory overhead of rm/unmount/sync in the doc

What changes are proposed in this pull request?
This adds the recent perf evaluation results of rm/unmount command and sync to the doc.
Why are the changes needed?
This adds how to make a good memory estimation, and the recommended command to perform the operation.
Does this PR introduce any user facing changes?
Users should look at the updated doc to use the memory most efficiently.

alluxio-bot, merge this please

@Xenorith could you help cherry-picking this to 2.8? Thx!

alluxio-bot, cherry-pick this to branch-2.8 please

alluxio-bot, cherry-pick this to branch-2.8 please


Tool Not working in Arc 10.5 for HERE processing

ID is not the expected data type. Pretty much sums it up

I had the same problem. In our case the tool we put created to process the RDF files from HERE was based on an earlier ArcGIS version than we used for running the street data processing tool. If we looked at the field type in the earlier ArcGIS version it was integer, but when we looked at it using the later ArcGIS version it appeared as double. Updating our processing routine to use 10.5 fixed the issue for us.

I'm going to close this issue, since it sounds like the issue was resolved, at least for one user, and since there has been no activity here since 2017.  A few ArcGIS Pro version of the HERE tool is now available; if you run into problems with that tool, please open a new issue.


UnicodeDecodeError

Reported via irc (#openmw on freenode).
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xcf in position 140: invalid continuation byte" File "./omwllf.py", line 485, in <module>

File "./omwllf.py", line 41, in parseString

Platform info:
Up-To_date Arch.
LC_ADDRESS=C
LC_COLLATE=C
LC_CTYPE=en_US.UTF-8
LC_IDENTIFICATION=C
LC_MEASUREMENT=C
LC_MESSAGES=C
LC_MONETARY=C
LC_NAME=C
LC_NUMERIC=C
LC_PAPER=C
LC_TELEPHONE=C
LC_TIME=C

Probably during processing of Robert's Bodies.

The mod in question has a bunch of non-ascii, non-unicode stuff in the mod description field. The python default behavior for bytes.decode() involves throwing exceptions on non-compliant strings.
I've updated to parse only ascii, and to ignore non-compliant characters, which should fix this.


Add loader support for custom cursors

We rely on a framework that references custom cursors. Without this trivial change, we are unable to serve the app:

ERROR in<EMAIL_ADDRESS>Module parse failed<EMAIL_ADDRESS>Unexpected character '' (1:0)
You may need an appropriate loader to handle this file type.

I signed it!