Not able to load the project page for a very long time and after it loads creating workloads get stuck in "saving..."

**Rancher versions: 2.0 Build from master
Steps to Reproduce:
Had a 3 node cluster with few projects and  namespace.
Also had few workloads deployed in the projects.
After a while , loading the project page starts taking a very long time .
In my case it takes up to a minute or sometimes more.
And eventually when  project page loads up, creating workloads get stuck in "saving..."  state for a long time.
Even this succeeds eventually and workload gets created.

project-stuck.tar.gz

Tested with latest build from master.
Have not seen this issue with project page taking a long time when testing in a set up with lot of clusters.
Closing this issue for now.
If i encounter this problem again will log another issue with more details.


Auto correct using cookstyle

Description
Autocorrect using cookstyle

merged in by https://github.com/sous-chefs/mongodb/pull/230


Remove parameter "UseGetTargetResource"

Remove parameter "UseGetTargetResource" on all Get-DSCBlock calls.
Fix #96

This change is

Any feedback on this? @NikCharlebois

Actually I just saw you fixed this yourself in 67a17d86a6340e15cb4c49ff6efc6e1d1a3a77e3, gonna close this pull request. Thanks for your continued investment in this script and the whole DSC.Reverse stuff, it rocks! 🥇


Fix query and link for featured autor (on homepage)

Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[x] I have updated the CHANGELOG
[x] I have requested at least 1 reviewer for this PR
[ ] I have made corresponding changes to the documentation

Just please check that renderless components do work before merging :)


Backport #8847 into Chef 14: Added support to provide additional options to bundle install

Added option to skip gem metadata installation
Added test cases for gem installer

Signed-off-by: Amol Shinde<EMAIL_ADDRESS>
Description
Cherrypick in the commit from #8847
Related Issue
We're backporting this in hopes it can help us work around #8753
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Chore (non-breaking change that does not add functionality or fix an issue)

Checklist:

[X] I have read the CONTRIBUTING document.
[ ] I have run the pre-merge tests locally and they pass.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.
[X] All commits have been signed-off for the Developer Certificate of Origin.

Looks like the errors are something up with the Windows configuration, unrelated to this PR.


Add support for async/await

https://github.com/facebookincubator/create-react-app/pull/327

sorry my fault, it works


nameplate castbars aren't styled

Styling them before they're shown doesn't work, or there is a blizzard func updating the style that should probably be hooked

Seems to work fine when "Always Show Nameplates" is enabled. Means the bug is probably caused by combat lockdown - check the taint logs

Problem was the event NAME_PLATE_UNIT_ADDED overwriting styling. Fires when a nameplate is repurposed for a new unit


Mobface ( character edit screen) bug

The game zooms to the character's gut in the character edit screen when you try to alter the face, or give him a hat or whatever.
Is there a fix?

That's an issue of https://github.com/ThirteenAG/WidescreenFixesPack, SilentPatch does not introduce it.

That's an issue of https://github.com/ThirteenAG/WidescreenFixesPack, SilentPatch does not introduce it.

Installing both silentpatch and the widescreen fix fixed the issue. Thanks


How to install use lets encrypt on OVH VPS

Hi,
I have a vps at OVH with url vps#####.ovh.net and I want to add ssl to it using lets encryot but I keep getting the error that OVH has many domains already. How can I walk around this?
Also, how can I secure my mail, ftp and plesk install too.
I am using CentOS 6 if that helps

This is a problem with OVH and lets encrypt's rate limits. By default LE will only perl 20 new certs per domain per week. OVH should talk to LE and have those limits increased. It is not related to Plesk or the extension.


Xcode 10 Building frameworks failing

Building frameworks with Xcode 10 is not working for me.
Using v1.0.0.

Possibly related to: https://github.com/CocoaPods/CocoaPods/issues/7857

I was able to reproduce the error in this project: cocoapods-rome-xcode-10-toolchain-problem-demo

@BasThomas can you try this out? https://github.com/CocoaPods/CocoaPods/compare/master...Ruenzuo:update_symroot

Hey @Ruenzuo — I can still reproduce it in your branch.
I did some more digging and found out that this really is an issue with the new build system. The error build input file cannot be found is there because of the new build system optimizations, and re-running Rome after setting the generated Pods.xcodeproj's build system to the old one, it works.
I can also see that at the time of these failures the module.modulemap file is actually there, but probably just not in time for Xcode to pick it up.

Thanks for checking.

re-running Rome after setting the generated Pods.xcodeproj's build system to the old one, it works.

How did you do this? With the Xcode UI?
Also, you might want to drop your findings on the CocoaPods issue so more people is aware of the workaround for now.

This has been fixed in the build system by Apple in Xcode 10 beta 6.


Update CryptoTest to use git ssh

The CryptoTest is using http to git clone the https://github.com/rh-openjdk/CryptoTest.git repo. As git on z/OS doesn't support https, only ssh. We would like to update it to ssh.
Related PR: https://github.com/adoptium/aqa-tests/pull/4327

fyi @sophia-guo


[#1711] feat(server): Introduce the reconfigurable conf

What changes were proposed in this pull request?
Introduce the reconfigurable conf for server or other componts.
Why are the changes needed?
Fix: #1711
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Unit tests.

I drafted this impl, please take a look. @jerqi

I drafted this impl, please take a look. @jerqi

gentle ping @jerqi

I drafted this impl, please take a look. @jerqi

gentle ping @jerqi

ping again

Codecov Report
Attention: Patch coverage is 66.25000% with 27 lines in your changes are missing coverage. Please review.

Project coverage is 53.47%. Comparing base (6f6d35a) to head (ce5230a).
Report is 27 commits behind head on master.

Files
Patch %
Lines

...ache/uniffle/common/ReconfigurableConfManager.java
65.78%
24 Missing and 2 partials :warning:

.../java/org/apache/uniffle/server/ShuffleServer.java
0.00%
1 Missing :warning:

Additional details and impacted files
@@             Coverage Diff              @@
##             master    #1712      +/-   ##
============================================
- Coverage     54.86%   53.47%   -1.39%
+ Complexity     2358     2346      -12
============================================
  Files           368      368
  Lines         16379    16698     +319
  Branches       1504     1516      +12
============================================
- Hits           8986     8929      -57
- Misses         6862     7259     +397
+ Partials        531      510      -21

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

Merged. Thanks @jerqi review


ERROR: This installation is not supported on 32 bit platforms.

Hi @stv0g ,
Thanks for you work but I'm stuck with 2024.1 version:
 > [installer 6/6] RUN cd $(basename Vivado_Lab_Lin_2024.1_0522_2023.tar.gz .tar.gz) &&     ./xsetup --confirm  --agree XilinxEULA,3rdPartyEULA         --batch Install         --edition "Vivado Lab Edition (Standalone)"      --location /installed:
0.355 This is a fresh install.
0.362 ERROR: This installation is not supported on 32 bit platforms.

But the rpi is 64bits:
bruce@raspberrypi:~/xilinx-hw-server-docker $ uname -a
Linux raspberrypi 6.6.47+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.6.47-1+rpt1 (2024-09-02) aarch64 GNU/Linux
bruce@raspberrypi:~/xilinx-hw-server-docker $ uname -m
aarch64

I have probably miss something but i'm quiet lost :(
Do you have any tips ?
Thanks!

Hi @NsTrmb,
Could you provide a bit more context?

Where do you build the Docker image?
Have you setup the binfmt_misc user-space emulation using QEmu as mentioned in the README?

See: Enable QEmu userspace emulation at system startup)

Please note that only Vivado versions v2021.2 and v2020.1 have been tested.
I think, that in the past we have always built the Docker images on an x86_64 system, and only ran the final container on an arm64 system using binfmt_misc.

Sorry for the missing context, I just call build.sh on the target, rpi aarch64.
I will make a try to build on x86_64 and run the container on the target. I also keep in touch if the same is possible with 2024.1.
Thanks a lot for the support.

Hi @stv0g,
Everything is ok now with 2024.1 version.
Sorry for trouble and thanks again for the support.

Hi @stv0g,
Everything is ok now with 2024.1 version.
Sorry for trouble and thanks again for the support.


all-england can be broken during deploy

If PPU savings are imported before measures are recomputed, the all-england page breaks because it tries to find MeasureGlobal objects with a month corresponding to the latest ImportLog with category='ppu'.

I had a look to see if this was something that could be easily and quickly fixed, but it doesn't look like it is. What we want is to take the minimum of the latest PPU date and the latest measure date. But there's no category in the ImportLog that represents the measures having finished importing. We could try to get that date from the MeasureValue table, but that would only tell us that some measure had finished importing, not that all measures had. And that would mean we would get an inaccurate total savings figure which would then be cached.
I think the most straightforward fix would be to create a new ImportLog event measures after all the measures have finished re-importing.


WIP: Community engagement guidelines

Creating a ticket to start drafting guidelines for Community Support Volunteers ("CSVs" - both community helpers and Mattermost, Inc. staff) helping to manage Bugs, Feature Ideas and Troubleshooting support.
In discussing specific procedures in this ticket my hope is to develop a set of principles to offer consistent, effective management of community responses.
My hope is to get this thread to three or four responses then create a doc for it. Here's a start:
Niche help
We should avoid requests on niche scenarios which aren't core what Mattermost is designed to do, particularly when they require deep technical analysis.
Example:

Asking how to create a buyer/seller marketplace using Mattermost

Our principles (which would be moved to a top section) could be:

Niche scenarios have a smaller audience, and it naturally takes longer to find interested parties to discover and discuss. CSVs jumping in too early, takes away the opportunity for new community members interested in the topic to make a contribution.

Help with deep niche scenarios takes time and energy away from helping with more common trouble shooting requests and from making contributions to the product itself, whether designing, implementing, testing or refining more popular features,

Niche help requests should:
a) Be encouraged to move to the forum under Developer Discussion (or just move it if it's already on the forum)
b) Add a response welcoming non-CSVs to respond
Thanks for your question. I don't believe the scenario you're requesting is currently supported. I'm moving this topic to Developer Discussion category to see if there are members of the developer community who might have advice.

Thanks, @it33! I believe this ask is covered by the Community section in the Handbook: https://handbook.mattermost.com/contributors/contributors. I'm tagging @aspleenic for visibility as there may be some new content that can be added or content that's already under consideration. @aspleenic, let me know if I can help with anything!

Thanks, @justinegeffen - I'll take a look and incorporate this into the existing doc


Parse setup keyword arg for testitems to include a shared test setup …

…module

@quinnj I just pushed a commit here that merges the two functions, and I fixed the tests. I'm going to merge once CI passes, it should be much easier then to continue in the other parts if this is just on main with the git submodule stuff.

Great timing! I was about to sit down and do it, so that sounds great.

Once this is merged we still need some tests for the new @testsetup stuff, but I think that can come in a later PR.


COUNT(*) query is not smart when used with LIMIT

Having a catalog on top of Kafka, I tried these two scenarios:
Doing a pure select with a where clause returns in about 2 seconds.
presto:default> select * from requests where country = 'US' limit 10;
However, changing that to a count takes a very long time to complete.
presto:default> select count(*) from requests where country= 'US' limit 10;
It makes sense for presto to try and do a "full scan" in case there are less items than the limit specified. However, I think it could be smarter in the cases that a select query would return more result than the limit count.

Actually, Presto's behavior makes sense. The LIMIT operator simply controls the number of rows returned. As count returns only one row, it is logically consistent that Presto would do the entire computation.

@shezarkhani
select count(*) from (select id from requests where country= 'US' limit 10) should behave like you want.

As explained by @raghavsethi, this is expected SQL behavior. Closing.


0.9.1

possible changes and fixes #15, #17, #18

I will likely be able to test this in the next 2 days and will let you know how it goes.

thx, this helps a lot.
i think it needs much more work to make the usage of many workers and proxies stable.

Hi Ecoron
Here's a full log of a run with the latest commit ( b08e83f0545c39ec740bf475968fd79fa8823b72 ) and 99 proxies.  Hope this helps.
http://magicdata.eu/public/2017-09-14 08:28:44_log.txt

thx for testing and sharing. a lot of helpfull informations.
i will focus on it in 0.9.2 and try to solve this challenge.


Optimize decodePolygon

It's one of the hot spots on many apps, sometimes even the main one.
I think that it could be optimized by removing the usage of the temporal vertices and normals arrays.

Closed by https://github.com/CartoDB/carto-vl/pull/799.

Please, close the issue when the fix comes to master

Right! Closing now by https://github.com/CartoDB/carto-vl/pull/791


Character position problem with respect to the rectangle

Hi I just started using Model-viewer and it's great. I have encountered only one problem at the moment and I don't know how to fix it. It happens to me only with a couple of super Mario bros models taken from sketchfab, while with other models always taken from sketchfab they work great. The problem is that when I view in ar the rectangle sits well on the floor, but the model displays very tall. His shadow is placed well on the floor but the character is not. And I have no way to get it down, because the (placement) rectangle is already on the ground. How can I change this problem? Thanks in advance.
It should be noted that before viewing in ar mode, then viewing on the browser, it works well and can be seen very well. The character is on the ground obviously attached to his shadow. The problem only happens when I view in ar mode

Good evening, can someone please help me? It's my 5 year old son's birthday in two days and I wanted to surprise him. But this very character with this animation, has this problem.
https://sketchfab.com/3d-models/star-dance-18c123dd557749b982baf0a2103f728d


Fixed typo in PicoMotorDriver.py

Typo found on line 87 of PicoMotorDriver.py corrected

Merged - Thanks.


Fix fp8 quantization script.

What does this PR do?
Fix fp8 quantization script.
Test Plan
sh run_quantize_checkpoint.sh localhost fp8 /home/yll/fp8_test/ /home/yll/fp8_test/quantized_2 /home/yll/fp8_test/tokenizer.model 1 1

Sources
Please link relevant resources if necessary.
Before submitting

[ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[ ] Ran pre-commit to handle lint / formatting issues.
[ ] Read the contributor guideline,
Pull Request section?
[ ] Updated relevant documentation.
[ ] Wrote necessary unit or integration tests.

uh oh pre-commit is failing
https://github.com/meta-llama/llama-stack/blob/main/CONTRIBUTING.md#pre-commit-hooks


Proposal and docs for changes to snapshot layout

This functions as both a proposal for how the snapshot tarballs should
be structured, as well as documentation for that structure.
Places with a "NOTE:" section are places where changes are proposed.

@kensimon I have some screenshots that I think makes this info easier to digest, e.g. see below for /plugins structure:

Once the structure is nailed down, let me know if you think these are helpful to incorporate. I can push them onto this branch if that's easiest.
^also, will we be unzipping nested tarballs?

Sure, screenshots would be awesome.  Up to you if you want to put them before or after we merge... I think so long as it's clear the document is a work-in-progress we can merge early and often on this one.
The tar-within-tar problem will be fixed in a separate PR, I think we can update the documentation then, although I don't think the docs will have to change.  Reason being: I think the fix for plugins that send tarfiles will be to implicitly extract them before putting them in the main tarball... that way, for someone consuming a sonobuoy snapshot, they'll never see a nested tarball in the first place (thus it's probably fine that the docs don't mention them.)

Makes sense! (re the tar-within-tar)
Screenshots added, feel free to edit.

@timothysc if you're happy with this, feel free to approve (or just merge), I think we can iterate more if there's feedback. I have another PR that implements these changes too, but I'll wait for us to have a consensus on this first.

@kensimon Let give this some time for other folks and I'll send out an email too.

@kensimon or @abiogenesis-now feel free to rebase then merge.

FYI added the snapshot file to the docs table-of-contents


DUOS-586[risk=med] Add Get Collections For Researcher

Addresses DUOS-586
PR adds an endpoint for researchers to fetch all collections created by them (ideally for the ResearcherConsole). PR also introduces a new service method and DatasetDAO method for dataset retrieval and attachment to the Collection. The service method in particular will be expanded on with future PRs when role considerations come into play. Other additions include tests and Swagger doc updates.
Have you read CONTRIBUTING.md lately? If not, do that first.

Label PR with a Jira ticket number and include a link to the ticket
Label PR with a security risk modifier [no, low, medium, high]
PR describes scope of changes
Get a minimum of one thumbs worth of review, preferably two if enough team members are available
Get PO sign-off for all non-trivial UI or workflow changes
Verify all tests go green
Test this change deployed correctly and works on dev environment after deployment

I've updated the PR so that it adds DarCollectionResource and DarCollectionService to ConsentApplication, as well as switch out all of the DatasetDTO references with DataSet within the DarCollection code scope.


Add support for web-submission of Slack import requests

Now that Slack import is working well and stable, we should allow users to submit Slack import requests on the web.  Here's how they should work:

We add a new page /import/slack (which we'll eventually link to from /new) which has instructions and where users can provide: (subdomain, token, uploaded Slack export tarball).
For v1, it just stores the uploaded data and calls mail_admins() to notify administrators to do a manual import.  And serves the user a page letting them know the import is in progress.
Later versions can do some or all of the actual export process, but right now I want to keep that process manual so that it can be supervised.
Stylistically, the page can look kinda like /new.

https://zulipchat.com/help/import-data-from-slack is a useful reference for understanding this issue.

@zulipbot claim

@hackerkid we should do some planning for this.  I think the main blocker for doing it is having an appropriate upload library, which you've worked on but hasn't been merged; I'm going to look at that next.


Add private property to configuration

Add private property to project properties.
Required by https://github.com/python-poetry/poetry/pull/2322

If we go the route of toml.poetry.build (or toml.poetry.build.config) for #26, we might as well have a toml.poetry.publish (or toml.poetry.publish.config) to configure the publishing aspects of Poetry that are inherent to the project.
However, this begs the question: should it be integrated in poetry-core since the publishing part is not part of it?

We have a bit of duplication in core and poetry. We should probably discuss how to consolidate it such that poetry code builds on top of core. But, I agree, we should introduce publish session within poetry and not core. Unless ofcourse we move the entire configuration schema to core.

#26 has been merged in but this has sat stale since. Hoping to see python-poetry/poetry#2322 merged so #1537 can be closed out. Any updates?


feature request: Add option to include folders with package.json

I'd like to put virtually anything that smells like a project folder in the list.  Right now that means including folders with package.json but I might even come up with better ideas.
I will need to do the other cache feature first or my load time will get ridiculous.
If you haven't noticed, I use git-projects all the time.  Simple idea but it really works for me.  I used to use one that required me to keep an edited list up-to-date but that was a PITA.

P.S. See https://discuss.atom.io/t/shout-out-for-git-projects/15202

Thanks for the shout out!
I think we used to use the same package, and keeping the list of projects updated was really annoying. That's why I decided to create git-projects. Now I'm not sure I understand this request. You would like to be able to list other projects than the ones containing a .git? That seems like a good idea, but I think it would be kind of out of scope.

You would like to be able to list other projects than the ones containing a .git?

I admit I don't have many projects that aren't on git.  If I know there will never be a remote repo then I only use git for archiving,  I think I will have more git-less projects now that I use live-archive for archiving.

I think it would be kind of out of scope.

I have noticed that our use cases are a bit different. The first symptom was wanting multiple root folders.  The second was wanting to open always in dev mode.  Now I see some new diffs.  E.G.the cache isn't needed for a normal number of projects so that's another diff. It will be bloating things a bit and there will be a trade-off of speed when bringing it up versus slowness the rest of the time like load time.
I've given thoughts to a fork..
Cons ....

It would split the user base
It would confuse users because it would be hard to tell which to use.
I would feel guilty for stealing your code
We wouldn't have the synergy of bouncing ideas
we would have duplication of efforts

Pros ...

I could use my coding style (it's a pain to remember to use yours)
There would be fewer confusing settings for users.
I could customize it more to my liking.
It would help assuage my OCD
Would have more project count to brag about (grin)
I wouldn't pressure you to do it my way (I get pushy)

Of course you would get prominent credit.  I can't decide. It;s a toss-up.  I will leave the decision totally up to you.

Thanks for the shout out!

Aarrggh.  I accidentally had a link to one of my projects instead of your.  I just fixed it.

I have no plans to do a PR in the near future.


Improve theme-switch examples

I think stylist is honestly brilliant. Kudos. There isn't exactly an abundance of resources for Yew styling right now, so I'm just happy to see a great library in the space.
One of the more involved features of stylist is themeing.
I was able to largely get the theme-switch examples working in my project with only some minor headaches. But I'd really love to see it be documented better and simplified.
I'm wondering if PRs would be accepted - because I'd be happy to contribute.
As of now, some ideas I would contribute to a PR:

Documenting the examples. There are no comments/docs anywhere, leaving users to 'reverse engineer'.
Explain why one might use the context example over the hook for themeing on the examples' respective README's (One thing I was scratching my head at first).

And here's what I'd possibly simplify:

Remove the use of one_cell::sync::Lazy and yew::html::ImplicitClone. They are optimizations made and deserve to be either 1) documented or 2) removed as needless to the point of an example.
I'd rather see 2.

I'm wondering if PRs would be accepted - because I'd be happy to contribute.

Pull requests are always welcome.
We should eventually expand our documentation and include tutorials.
I haven't had time to add documentation to explain how to actually use the library.

Explain why one might use the context example over the hook for themeing on the examples' respective README's (One thing I was scratching my head at first).

There is not an official preference on whether you should use hooks or styled_component.
Some people may prefer hooks over procedural macro as it involves less magic.
The -context naming might not be the best choice here as -hooks example also uses context and -context also uses hooks (to read theme). The difference is that -hooks uses use_style! hook and -context uses styled_component procedural example.

Will work on a PR for this in the week. Thanks for clarifications here.


GitHub workflow which to schedule generation of stats

Add GitHub workflow to generate stats yearly and on manual trigger when required
It is scheduled to run on 15th and 25th of October every year.
resolves #1

This is amazing. Thanks!
Can you please help me understand why are we running it twice? Is it because of the ticket #4 raised by you?

Running twice in the sense 15th and 25th October? I did it to make sure that even Google doesn't release the archive by 15th, here it updates at least by 25th. I do not know the exact date, so I was just precautious. If it is unnecessary, I shall remove change it. Please suggest the date on which the script needs to be run.


InstallApkAction rework

Remove deprecated AvdSelector and DeviceChooserImpl -> new submenu with list of connected devices and direct install to device action


Skip merging source files to a single destination file

Convert html templates to angular template cache without merging the output together to a single dest file. Output files respect the original folder structure and name of source src files. This behavior is turned off by default and could be turned on by setting merge: true in the options.

Dunno if you may be interested in #137...

@aaani can you please add a test for this scenario? Thanks!

@underscorebrody: Added a test. Thanks.

@aaani This looks good, just needs a rebase

@underscorebrody done!

 I think because you put a merge commit into it. Can you back out the merge commit? That ought to fix the weirdness.

Sorry about that @underscorebrody. Does it look ok now?

Yup looks good!

This is fantastic work!  Great job!


Html tags have been encoded

@micahgodbolt The commit  3acd7d22ec0538eed7205ef33a6d90588b9344c6 just encode the html tags and break the page。
see: https://github.com/Microsoft/frontend-bootcamp/blob/master/step1-02/demo/index.html#L107

These are encoded so they can be passed into a codepen embed


Improve performance of pulse.Schedule

Summary
Address #2817. This PR improves the run time of the example code given in #2817 from 34s (273s) to 1.5s (6.6s) by improving the implementation of TimeslotCollection.merged() and Schedule.__init__().
Details and comments
The bottleneck was in the reconstruction of TimeslotCollection in the constructor of Schedule. This PR improves the performance of Schedule.__init__() by improving the implementation of TimeslotCollection.merged() and using it in Schedule.__init__().

Yes, unless users intentionally enable the option check_overlap=False. But even so I have to admit current this PR changes current interface. I understand this PR should not include any interface change and focus only on performance improvement. I'll try to tweak more to improve performance without changing interface.

Now this PR is updated not to allow invalid schedule again, while it still improves performance as shown in the top comment.

I LOVE the type hint fixes. However, please make separate PRs next time 🙏 One PR for type hints, one for "Improve performance of pulse.Schedule". Makes the life of the review much easier

Based on the discussion on this PR, #2870 is going to fix the issue #2817 more completely. Thank you, @taalexander. This PR should be closed if #2870 is merged.

Closed since #2870 is merged.


amplify.store() examples in the docs is not working

Doc link : http://amplifyjs.com/api/store/
Results are not showing in fiddle result window

Try this Fiddle.
I'm seeing a console error that the external resources (amplify.core, amplify.store) have an improper MIME type. In the above Fiddle I updated the paths for those to use RawGit instead of Git directly.


Fix line category

Coverage decreased (-0.5%) to 84.109% when pulling 5d493424afbc8737d1773da3101e5aa1c082f5b0 on fix-line_category into aad2b531cc5fe558ffb5abd4ea9fcd8f753c1ea4 on master.


It should be  ./node_modules/.bin/webdriver-manager

Please update the readme file to use the command  ./node_modules/.bin/webdriver-manager

Also please update  ./node_modules/.bin/gulp

No, it's because you are not running this modules globally.


[Enhancement] Values as variables

Have a central spot to host values as variables. This way, if you want to change the value of spacing, you could do it in one spot; rather than tediously changing all occurrences through your document.
For example:

small = 8
medium = 16
large = 32

Then using them with the variables, instead of [8 16], it would [small medium]
That way, changing the value of medium to be '20'; simply change it in the centralised place.

I love the variable idea. For now, I am using the Rename-it plugin to make this work by doing a find and replace of "[8" or "16]" with the new value.
Read more here:
https://rodi01.github.io/RenameIt/


Discussion: Should app specific IndexedDB queries be in luminary-shared or not?

Discussed in standup meeting 2024/07/12:

Generic queries (e.g. using generic TS types) belongs in the shared lib
App specific queries need to live in the app where it is used.


Change versioning scheme

Project uses a reverse date version scheme (year.month.date). This was a bad practice I had inherited from a company I worked at at the time.
The version scheme should be updated to Major.Minor.Patch so that it updates correctly in NPM.

Actually, I was mistaken. I already am using the correct versioning scheme.


Is it necessary to re-hydrate an aggregate to check it exists in a repository?

eventsourcing.application.Repository.__contains__ reconstructs the complete history of an aggregate to answer whether the aggregate exists in the repository or not.
Since the repository is not able to delete an aggregate, could it make sense to limit the aggregate events fetching to the initial event to improve performance?
Basically applying the following patch:
diff --git a/eventsourcing/application.py b/eventsourcing/application.py
index 08abc52e..85a46b52 100644
--- a/eventsourcing/application.py
+++ b/eventsourcing/application.py
@@ -384,7 +384,7 @@ class Repository:
         Tests to see if an aggregate exists in the repository.
         """
         try:
-            self.get(aggregate_id=item)
+            self.get(aggregate_id=item, version=1)
         except AggregateNotFound:
             return False
         else:

My use-case is to rely on aggregate in self.repository liberally in my application, assuming the aggregate would not get hydrated for nothing if it is present in the repository.

Good question @bibz, as always!
It's done this way because an aggregate might define a "deleted" event that has a mutate() method that returns None.
If you know you don't have any such things in your domain model, and you want to use the in operator, then I would suggest overriding the Repository method and instead just see if it can get one stored event from the recorder? And don't bother running it through a projection, or using the mapper to convert to a domain event? That's likely the fastest thing to do? :-)

Aha! Thanks for bringing the mutation behaviour into the light, I didn't think about using it that way.
Then it is clear we need the default behaviour, as usual you are two steps ahead!

@johnbywater it was, of course, as easy as you made it look.
I implemented a quick subclass at https://git.sr.ht/~docbibi/pyeventsourcing-contrib/commit/ea7b85ea7caaa5c644df370c1557e40f068e7c65. Will add tests and move on.

You probably know already, there's a section in the docs about "discarded" events. I just separated it out under a new heading:
https://eventsourcing.readthedocs.io/en/latest/topics/domain.html#discarded-events


convert the script and sets pages to php for security - script page

it works -  but there are some php left over that still comes in and all other functions don't work - will fix later

fixed the function issue - now just the leftover characters when unlocked

^ that commit worked, so this issue is complete


Fixes: #204, Categories bar goes out of screen

The categories bar  was not responsive,
-> Added a Shadcn component to keep default tabs selection with responsiveness
https://github.com/code100x/daily-code/assets/77314004/7f84f843-4194-4613-a098-539cc1fd2e01

Someone has already solved this.
You're free to solve the issue on your own, but please avoid raising a PR if there is already a PR which is going to be merged. (ref #205)
It gets difficult for the maintainers if there a lot of duplicate PRs.


not working with laravel mongodb

I am using Jenssegers laravel mongodb package
https://github.com/jenssegers/laravel-mongodb/
On importing data through model, no mappings are created.
and search also doesnt gives any result
please help
User Model
`
protected $fillable = [
    'name', 'email', 'password',
];
protected $hidden = [
    'password', 'remember_token',
];
protected $dates = [
    'updated_at',
    'created_at'
];

`
scout.php
`
'driver' => env('SCOUT_DRIVER', 'elasticsearch'),

'prefix' => env('SCOUT_PREFIX', ''),

'queue' => false,

'elasticsearch' => [
    'index' => env('ELASTICSEARCH_INDEX', 'laravel'),
    'hosts' => [
        env('ELASTICSEARCH_HOST', 'http://<IP_ADDRESS>'),
    ],
],

`

was it fixed? I'm having the same problem in Laravel v5.4.19, jenssegers/mongodb v3.2.2 and laravel-scout-elastic 3.0.2


[addon-info] Story source incorrect when using static class properties

Example component:
const Section = ({ children }) =>
{ children }
;

class Panel extends Component {
  static Section = Section;

  render() {
    return
{ this.props.children }
;
  }
};

The story:
storiesOf('Test', module)
  .addWithInfo(
    'with some info',
    () => <Panel><Panel.Section>Hey</Panel.Section></Panel>
  );

Rendered info:

As you can see,
 should be <Panel.Section />. I'm working on a pretty large component lib that uses these 'nested' components pretty frequently, would be nice to find a fix 😢

@jonambas try:
const Section = ({ children }) =>
{ children }
;
Section.displayName = 'Panel.Section';
...

@shilman 👍  Thanks, that did it

Great, closing for now!


cmd/go: do not allow the main module to replace (to or from) itself

What version of Go are you using (go version)?

$ go version
go version go1.13 darwin/amd64

This problem is also seen on Linux using go1.12.3

$ go version
go version go1.12.3 linux/amd64

And on Mac with the tip branch

$ gotip version
go version devel +fe2ed50 Thu Sep 19 16:26:58 2019 +0000 darwin/amd64

Does this issue reproduce with the latest release?
Yes.
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/rselph/Library/Caches/go-build"
GOENV="/Users/rselph/Library/Application Support/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GONOPROXY=""
GONOSUMDB=""
GOOS="darwin"
GOPATH="/Users/rselph/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/opt/local/lib/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/opt/local/lib/go/pkg/tool/darwin_amd64"
GCCGO="gccgo"
AR="ar"
CC="/usr/bin/clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/4w/6dmz_gmd6fj_qy_nwdwclg8c0000gp/T/go-build675848548=/tmp/go-build -gno-record-gcc-switches -fno-common"
GOROOT/bin/go version: go version go1.13 darwin/amd64
GOROOT/bin/go tool compile -V: compile version go1.13
uname -v: Darwin Kernel Version 18.7.0: Tue Aug 20 16:57:14 PDT 2019; root:xnu-4903.271.2~2/RELEASE_X86_64
ProductName:	Mac OS X
ProductVersion:	10.14.6
BuildVersion:	18G95
lldb --version: lldb-1<IP_ADDRESS>
  Swift-5.0

What did you do?
Option A:
$ git clone https://github.com/rselph-tibco/go-unstable-mods.git
$ cd go-unstable-mods
$ git checkout start_here
$ git switch -c new_branch
$ ./run.sh

The  git repository will be updated with the results of each step.  Optionally, comment out the git
commands to simply produce the error without recording results along the way.
This is equivalent to:

Start with the contents of the attached file
go-unstable-mods-start_here.tar.gz
Set GOPATH and GOCACHE to point at empty directories
From the sample1 directory run go mod tidy
From the sample2 directory run go mod tidy
From the sample2 directory run go install ./...
From the sample1 directory run go install ./...
Repeat the last step indefinitely

At this point, sample1/go.mod will never stabilize.
What did you expect to see?
go.mod should stabilize when the build is given the same inputs over and over.
What did you see instead?
go.mod eventually oscillates between two states, preventing -mod readonly from ever working, and wreaking
havoc with source control.

I took a quick look at this, need to investigate further though.
The first go install ./... command in sample1 removes a bunch of requirements from go.mod. The only reason that would happen is if the requirements are implied or redundant with some transitive requirement. Since each module is replacing itself and requiring the other module at an invalid version, I think sample1 is seeing its own go.mod file as a go.mod in a different version of sample1, so it sees its own requirements as redundant.
As I said, need to investigate further, but this seems like a strange edge case of replace. We should forbid modules from replacing themselves without specifying a version.

Thanks for taking a look.  If I understand you correctly, a workaround might be to specify the versions of sample1 and sample2 in the replace statements.  That's certainly something I can try.  I'm worried about the implications, though, since what I'm modeling is two modules under active development locally.  Would I need to increment the versions each time the source changes to deal with cache issues?

I’m not quite following this example, but why  are the modules replacing themselves?
Regarding:

what I'm modeling is two modules under active development locally. Would I need to increment the versions each time the source changes to deal with cache issues?

Again, I am not quite be following the example, but I think you shouldn’t need to specify versions if you are doing local replaces of modules that are being locally developed.
This FAQ has an example:
https://github.com/golang/go/wiki/Modules#can-i-work-entirely-outside-of-vcs-on-my-local-filesystem
Sorry for the quick comment, and sorry if it is not helpful.

@rselph-tibco, it should be very rare for a module to need to replace itself, since the main module itself is always considered higher-precedence than any explicit version of its own path.
The only reason I can think of for a module to replace itself would be if some other interdependent module depends on an invalid version of it, in which case it should suffice to replace the invalid version with a valid one.
In the rare case in which you are developing two entirely new modules from scratch, #33370 may be relevant.

Hi, thanks for all the comments.  I arrived at the models replacing themselves only because without it, I get this when building one module or the other (in this case, sample2):
go install ./...
++++++++++++++++++++++++++
go<EMAIL_ADDRESS>requires
<EMAIL_ADDRESS>unrecognized import path "foo.com/me/sample2" (https fetch: Get https://foo.com/me/sample2?go-get=1: dial tcp <IP_ADDRESS>:443: connect: connection refused)

BTW, I just verified that adding version v0.0.0-00010101000000-000000000000 explicitly to the replace directives didn't change the behavior with 1.13 or tip.  But I agree @bcmills, that #33370 sounds related.

BTW, I just verified that adding version v0.0.0-00010101000000-000000000000 explicitly to the replace directives didn't change the behavior with 1.13 or tip.

Yeah, that's not surprising: it makes go mod tidy think that the dependency on the zero-version module (via sample2) provides all of the same requirements as the main module, and thus the main module's requirements are irrelevant.
So it removes those requirements from the main module, but because of the replace directive that also removes the transitive requirements upon which the removal relied.
The core of the problem is that the module system assumes that versions are immutable, but replace directives make them mutable — and, in this case, the replace directive actually performs the mutation itself.
Probably that implies that we should also not allow the target of the replace directive to be the directory containing the main module.

The corrected version of this example, I think, is to replace v0.0.0-[…] with a directory containing only an empty go.mod file:
replace foo.com/me/sample1 v0.0.0-00010101000000-000000000000 => ./empty-sample1

The two diagnostic fixes we can make for this are:

[ ] Emit an error if the main module contains a replace directive that matches its own path and version.
[ ] Emit an error if the main module contains a replace directive that resolves to the filesystem directory containing its own go.mod file.

It looks like the empty directory trick works.  I'll give this a try in our actual build environment.  Thanks.

@bcmills Hi, i want to take this task, if that's ok. Am i correct, that we want to make it impossible to replace module with it current version? Or we just want to notify user about that and allow him to force that behavior?

Was pointed to this issue and advised to add my data point here, in case it's related.
I'm concerned that it is practically impossible to develop Go modules in some cases without Internet access; or, in the best case with Internet access, without kind of a hacky commit to a remote server.
In developing Caddy 2 extensions, there arose a situation where two repos created a Go module cycle: https://gist.github.com/mholt/e0a14049026840e480f57c1f601f9d86 -- but not a package import cycle, so the program still compiled. Note that both modules use replace to pin local versions of each other.
There are two modules in play here: caddy/v2 and tls.dns. Both modules depended on each other, but tls.dns was still being developed only locally -- was not published yet. (No GOPATH; using only module mode.) The caddy/v2 module contained the main package which imported a library package in tls.dns.
However, all the go tool commands failed in the tls.dns workspace, including every time I tried to save in my editor (VS Code) because the save actions would never finish. Since I could not go build in tls.dns, I went to caddy/v2 and ran go build there, sure enough I was able to see the functionality from tls.dns that I had written (but which was not properly formatted or tested, because no go commands worked there).
Basically, it became impossible to be productive on my new Go module without another, already-published module to import and build it. There was no way for me to continue working on tls.dns in isolation.
@heschik advised me to push a commit to the tls.dns remote -- any commit, even one that just added a README. Which I did. That was enough to give me a commit hash which I could then do go get github.com/caddyserver/tls.dns@20832cb8a8269804599ed2ebb5918c04afb9c9c4 in the caddy/v2 repo. And magically, I was able to continue development in the tls.dns repo! The go command started working again, to my relief... but...
A few things strike me as odd/concerning/buggy/unintuitive in this situation:

Impossible to locally develop a new Go module in isolation
Impossible to be productive with a new Go module without Internet access
Pushing a dummy commit to a remote was a necessary prerequisite (requires Internet access)
After doing that (only possible with Internet access), changing go.mod in another Go module (caddy/v2) is what fixed the go command in the current development module (tls.dns).

It would be nice if these problems could be addressed soon.
The root of the complexity here is that the main module must always be the selected version of itself. It cannot be replaced with anything else, and since it has no explicit version, its effective version must be interpreted to be higher than any other version of the same module path.
Since the main module cannot be replaced with anything else, the replace directive for an older version of the main module must name some explicit version: it cannot be versionless.
One solution, as you found, is to push an empty commit and name that version.
However, another is to decide on the version that names the initial tls.dns commit ahead of time (for example, v0.1.0) and name that explicitly in the caddy/v2 go.mod file, and have tls.dns replace that specific version instead of using a wildcard: https://play.golang.org/p/t1z25zEembm
#33370 is very relevant to this use-case, but as noted in https://github.com/golang/go/issues/33370#issuecomment-542377792, we probably shouldn't be writing out at explicit require at all if the latest version of an unresolved dependency is the subject of a replace directive.

I think there is still a need for this ability. It may be that #33370 also would meet the need, I'm not sure. But here's the situation I'm facing, which was the basis for the reproducer I created for #39570 :
Module "foo" exists, and has a dependency on module "bar". Those modules are being simultaneously developed, and in fact the only real reason they're not the same module is that "bar" is closed-source code, requiring it to be in a separate repository.
Because they're effectively the "same module", of course they have circular dependencies. And because they're both in development, the only correct way to build them is to have them both checked out into separate directories and use "replace" directive to point at each other.
Now, when building an executable in "foo", it finds "bar" correctly. However, "bar" imports other packages in "foo". Since only "foo"'s go.mod's "replace" directives are used in the build, this means foo/go.mod must have a "replace" directive for itself so that bar's code can compile.
This actually works today, except for the issue mentioned in #39570 that "go mod tidy" gets confused by the situation and erases some necessary entries in go.mod.
As a side note: "foo" is not a module in the sense that it is ever expected any other code in the world will import foo. It's a module because it wants to use go.mod to define its own dependencies. So there will likely never be any "releases" of foo, nor should Go require us to figure out how to "release" foo such that "bar" can depend on an explicit version.
As I said, I can't tell whether #33370 would fix this or not. If it allows us to build "foo" in such a way that "bar" resolves "foo" to the same directory containing the local "foo" code (and does so in such a way that "go mod tidy" doesn't break "go build -mod=readonly"), then that would be just fine.

I want to clarify a couple points of discussion.
The problem
This issue happens because it appears to the go command that the content main module's directory (in the directory where build commands are run) is also the content of a released version of the same module in the dependency graph.
This breaks some invariants. It appears to the go command that requirements in the main go.mod file are redundant since they're implied by another dependency (the module that the main module directory is replacing), so they get removed.
The workflow
This tends to come up when people are developing two or more modules that depend on each other, and it's not practical to release versions of those modules. There are several use cases for this: releasing new versions concurrently; developing offline; projects with separate open
/ closed parts.
The problem is triggered with a line like this (where example.com/a is the main module):
replace example.com/a => .

Instead, use this (where ../empty is a path to a directory containing a go.mod file with no requirements):
replace example.com/a => ../empty

To elaborate:

Suppose example.com/a and example.com/b are modules that depend on each other. They are developed offline and have not been pushed anywhere yet.
There needs to be an explicit requirement between the modules to express the dependency; go mod tidy and other commands will try to add a requirement if one is not present, and this will fail because the modules aren't available.

If #33370 is implemented, this requirement won't be necessary, and it won't be added automatically.

Requirements can be on fake versions though, and we can replace fake versions with local directories.
The main module's directory can't serve as a replacement, but we can replace fake versions of the main module a directory containing a go.mod file with no requirements.

A full example (you can extract with txtar).
-- example.com/a/go.mod --
module example.com/a

go 1.15

// require example.com/b at a fake version. Any version will do.
// We need the requirement so 'go mod tidy' doesn't try to add it.
require example.com/b v0.0.0-fake

// replace all versions of b with the directory where b is developed.
replace example.com/b => ../b

// replace all versions of this module with an empty directory.
// example.com/b requires example.com/a at a fake version, so we need
// to replace that with *something* to prevent it from being looked up.
//
// This replacement is only used active when example.com/a is the main module,
// and the main module will be chosen over any other version of the same
// same module, so packages will be loaded from here, not ../../empty.
replace example.com/a => ../../empty

-- example.com/a/a1/a1.go --
package a1

import _ "example.com/b/b1"

-- example.com/a/a2/a2.go --
package a2

-- example.com/b/go.mod --
module example.com/b

go 1.15

require example.com/a v0.0.0-fake

replace example.com/a => ../a

replace example.com/b => ../../empty

-- example.com/b/b1/b1.go --
package b1

-- example.com/b/b2/b2.go --
package b2

import _ "example.com/a/a1"

-- empty/go.mod --
module empty

go 1.15

// This directory serves as a replacement for non-existent versions of the
// "main" module. It contains no packages, and only the go.mod file is loaded.
// It has no dependencies.

You can run go build ./... or go mod tidy in either module without changing its go.mod.
Changes needed
When the main module's directory serves as a replacement, the go command can't safely remove seemingly redundant requirements from go.mod. It should report an error with a clear message when this happens. It should probably hint that a directory with an empty go.mod file should be used instead.
This still doesn't give us a very intuitive workflow. Some improvements are planned already:

#33370 - If a module is needed and is replaced but not required, the go command will just the replacement without trying to add a requirement.
#36460 - Lazy module loading may reduce the need for replacement. That would only benefit 1.16+ modules though.

Some other ideas (brainstorming):
In replace, we could interpret the version none as an empty module with no requirements.
replace example.com/a => none

Or perhaps, we could just do that when all versions of the main module are replaced with the main module's directory.
replace example.com/a => .

We could perhaps also just ignore the selected version of the main module when matching replace directives. (We never did precisely nail down the semantics of those — see #26344.)

But that wouldn't solve the problem of replacing to the main module's directory, which we still can't allow (and which I can't justify silently ignoring).

I will try out the "empty" workaround, thank you for the suggestion.
I still don't understand why the (annoying but seemingly intuitive) solution of "replace example.com/a => ." must be disallowed. It means "use the content of . for all imports of all versions of example.com/a", which is the same semantics as any other replace statement. The "empty" workaround is much less obvious, since it means "use the content of ../empty for all imports of all versions example.com/a (except don't really do that because you already know example.com/a exists in the current directory)".
I'm sure the difficulty in implementing this comes down to needing to special-case that situation, since go's logic for resolving modules and transitive dependencies and saving them in go.mod is a little hairy. But from a usability perspective, from the outside looking in, it feels much more direct.


refactor: (more) code cleanup

Bye bye unused code.
Also closes #35 and closes #36.

No idea why CI (Linux) fails, when it obviously works fine on my machine. :shrug:


Browser does not proceed after MQTT setup

Hi First of all big thank you for the homie. That is what i have been looking for. I was running ESPEasy for a while but seems like it is highly unreliable. My issue with Homie currently is I am having trouble saving config at MQTT setup point. Even I click Next the browser does not move.
I have tried https://community.openhab.org/t/framework-homie-for-esp8266/8674/37
and re-uploaded https://github.com/marvinroger/homie-esp8266/blob/develop/examples/IteadSonoff/IteadSonoff.ino
I can see in serial monitor everything is working until MQTT setup after entering all the information it does not move to the next stage. Am I missing something?
I have tried on Safari, Chrome, Firefox and Internet Explorer all same result. Please help

What version of homie-esp8266 are you using? Which configurator do you use? (the URL?)

homie-esp8266 ---> v1.5.0 from https://github.com/marvinroger/homie-esp8266/releases/tag/v1.5.0
URL - http://marvinroger.github.io/homie-esp8266/

Can you post a screenshot of the interface at the moment it fails?

After you asked which version homie I downloaded develop version from githubhttps://github.com/marvinroger/homie-esp8266 uploaded and it passed MQTT section. Configuration saved but after reboot it is not connecting to my AP to go live.

Screenshot of Serial monitor and MQTT.fx after reboot nothing is happening and I have my AP connected device list is open as well but nothing popping up ATM.
Thanks for you help,

Don't mix the v2 and the configurator of the v1. Try again with the v1.5.0 and send a screenshot of the filled MQTT so I can reproduce.

Will do and let you know

Don't mix the v2 and the configurator of the v1. Try again with the v1.5.0 and send a screenshot of the filled MQTT so I can reproduce.

What you mean by don't mix v2 and configurator of v1? V2 does not require configurator? How do I upload configuration in v2?

I got it working... The only thing I have done different was to unhook from serial connection and left it as standalone and I started to see messages in MQTT.fx and then it just a matter of time till i figured out from your great explanation about convention.

Appreciate your help and hats off to you for great project keep it up. Looks way stable than ESPEasy. If i run into problem will let you know.

After you flash a sketch, you have to power cycle your device so that reboots can work. This is a known esp8266/Arduino issue.
Glad you like it! Please open an issue on the homie-esp8266 repo next time. :wink:


[BUG] sqlalchemy can't load GINO dialects from entry_points.txt

Investigative information

Timestamp: 2020-05-29 09:48:00.842
Function App name:  qa-notifications-eus-func
Function name(s) (as appropriate): queue_send_notification
Core Tools version: 3.0.2534-1

Repro steps
Publish an async function that uses GINO and service bus trigger on consumption plan.
pip install --target="./.python_packages/lib/site-packages" -r requirements.txt
func azure functionapp publish qa-notifications-eus-func --no-build

Expected behavior
The function works stably.
Actual behavior
The function works fine right after the deployment, but after some time it begins to raise an exception:
Result: Failure Exception: NoSuchModuleError: Can't load plugin: sqlalchemy.dialects:postgresql.asyncpg
Stack: File "/azure-functions-host/workers/python/3.7/LINUX/X64/azure_functions_worker/dispatcher.py", line 311, in
_handle__invocation_request call_result = await fi.func(**args)
File "/home/site/wwwroot/queue_send_notification/__init__.py", line 19,
in main await process_notification(deserialized)
File "/home/site/wwwroot/shared/notifications/__init__.py", line 30, in
process_notification await _send_email_notification(notification, emails)
File "/home/site/wwwroot/shared/notifications/__init__.py", line 42, in
_send_email_notification await get_db_engine()
File "/home/site/wwwroot/shared/db.py", line 26, in get_db_engine bind = await
create_engine(dsn)
File "/home/site/wwwroot/.python_packages/lib/site-packages/gino/strategies.
py", line 33, in create dialect_cls = u.get_dialect()
File "/home/site/wwwroot/.python_packages/lib/site-packages/sqlalchemy/engine/
url.py", line 189, in get_dialect entrypoint = self._get_entrypoint()
File "/home/site/wwwroot/.python_packages/lib/site-packages/sqlalchemy/engine/
url.py", line 172, in _get_entrypoint cls = registry.load(name)
File "/home/site/wwwroot/.python_packages/lib/site-packages/sqlalchemy/util/
langhelpers.py", line 268, in load "Can't load plugin: %s:%s" % (self.group, name)

Known workarounds
Register sqlalchemy dialects by the code:
from sqlalchemy.dialects import registry
registry.register("asyncpg", "gino.dialects.asyncpg", "AsyncpgDialect")
registry.register("postgresql.asyncpg", "gino.dialects.asyncpg", "AsyncpgDialect")

Contents of the requirements.txt file:
gino==1.0.0
sqlalchemy-utils==0.36.5
azure-servicebus==0.50.2
sendgrid==6.3.1
psycopg2-binary==2.8.5
marshmallow==3.5.0
aiohttp==3.6.2

Related information
https://github.com/python-gino/gino/issues/238
I've tried adding setuptools>=39.2.0 to requirements.txt, but it didn't help.

Can you please check if your app ends up using something in the /tmp folder as in is the app "stateful"  and hence if you are running the app for some time and we allocate a new container - the app might loose that state and hence you might be getting the errors after some time. If that is the case you might want to use the Azure File integration so that you can store your state there.


Raspberry PICO 2040 and TinyUSB

After uploading the sketch to the RP2040, the RP2040 presents itself as a USB to Serial (TinyUSB Serial).
If I start USBview I can see the following..
Device Descriptor:
bcdUSB:             0x0200
bDeviceClass:         0xEF
bDeviceSubClass:      0x02
bDeviceProtocol:      0x01
bMaxPacketSize0:      0x40 (64)
idVendor:           0x1B1C
idProduct:          0x1C1A
bcdDevice:          0x0100
iManufacturer:        0x01
iProduct:             0x02
0x0409: "Lighting Node PRO"
iSerialNumber:        0x03
0x0409: "FB66DF55421900F5"
bNumConfigurations:   0x01
But i can also see in usbview
Interface Descriptor:
bInterfaceNumber:     0x00
bAlternateSetting:    0x00
bNumEndpoints:        0x01
bInterfaceClass:      0x02
bInterfaceSubClass:   0x02
bInterfaceProtocol:   0x00
iInterface:           0x04
0x0409: "TinyUSB Serial"
System (please complete the following information):

OS: [e.g. Windows 7 and10]
Board: [e.g. RP2040]
Device: [e.g. TinyUSB (Corsair Lightning Node pro)]
Version of IDE: [e.g. Arduino IDE 1.8.19]
Version of CLP: [e.g. 0.15.0]
Version of CLP Boards: [e.g. 0.3.1]
Sketch: [e.g. TinyUSB]

I have added the 6 files for the RP2040 and #elif defined(ARDUINO_ARCH_RP2040) / #include statements in [led_sysdefs.h] and [platforms.h]

@Spegs21 can you help here?

The CDC endpoint is not disabled in the code and it will be visible along side the HID endpoint. It should not affect the operation of the device. It is needed to be able to upload to the Pico without manually entering the bootloader.
Is the device not visible in iCue?

No, The device is not visible in ICue / device manager.
Only "TinyUSB Serial" is visible in device manager.
When i first programmed the rp2040 and when the sketch was uploaded i could see "Lightning node pro" as a device. But when windows has searched for driver only "TinyUSB Serial" is displayed.

@MakerVejby Have you me any changes to the sketch? Have you used this board or a different board as a different Corsair device through this library on your PC? Sometimes iCue won't show the device without a restart because the device ID it remembers is for a different device.

I have only used this board for this program. I have not made any changes in the code.
I have programmed one Arduino Pro Micro and that one works like a charm.
I have tried to reboot the computer but it didn't hel.

Of course not! :-) That would be a easy fix.

The CDC endpoint is not disabled in the code and it will be visible along side the HID endpoint. It should not affect the operation of the device. It is needed to be able to upload to the Pico without manually entering the bootloader.
Is the device not visible in iCue?

@MakerVejby It doesn't look like the support for entering the bootloader with the serial trigger is implemented in the Pico core. Adafruit has this working for their SAMD boards though.
I compiled and uploaded the TinyUSB sketch to my Pico through the Arduino IDE and it is working fine. Can you enable verbose output during compilation in the IDE preferences and post the build log here?

Please see txt file
Compile.txt

When i try to change serial according to the example i only get "'CorsairLightingProtocolHID' does not name a type; did you mean 'CorsairLightingProtocolSerial'?"

@MakerVejby You need to pass the serial number to the CorsairLightingProtocolTinyUSBHID constructor not add the CorsairLightingProtocolHID constructor. I just said you do it in the same way.

@Spegs21 Sorry, My bad. I was to eager to get it to work on the RP2040.
I have changed the code so it's correct now. But no success.
I've tried the RP2040 on two other computer that have newly installed windows 10 and 7 and the latest Icue.
But still the same. It won't show up in Icue as a device. I have tried with new serial and new device id.

@MakerVejby can you enable debug logging in iCue and export the logs after plugging in the device then post the zip file here?

@MakerVejby I just noticed your idProduct is incorrect.
idProduct: 0x1C1A
Did you change some of the files? This should be 0x0C0B

Well, look at that! Now it's working! Show's up as a Corsair Node Pro! Don't remember changing the PID but when i look at the files on github they differs from my files. So i must say that the file has been altered here.
Thank you for all the support!


Update iot-hub-devguide-sdks.md

Modified links to repos for the various service/device SDKs

Hi @rjmiller, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

It looks like you're a Microsoft contributor (Randy Miller). If you're full-time, we DON'T require a Contribution License Agreement. If you are a vendor, please DO sign the electronic Contribution License Agreement. It will take 2 minutes and there's no faxing! https://cla.microsoft.com.

TTYL, MSBOT;

@rjmiller : Thanks for your contribution to the Azure documentation! The author, @dominicbetts, has been notified to review your proposed change.

#sign-off
@rjmiller - thanks for this.


Operate First - updating files, adding README, and creating GitHub workflow

This PR makes the following changes:

[x] Updates the generated yaml files given the latest Helm chart
[x] Adds a README to document how to generate yaml files
[x] Creates a GitHub workflow to automate the creation of a PR to the Operate First repo on each release of Fybrik

@roee88 I updated the GitHub workflow with the correct APP_ID and APP_PRIVATE_KEY and tested it in my master branch.
I am removing all the yaml files as a part of the workflow with rm fybrik-repo/samples/operate-first/*.yaml


Fix support for python 3 and python 2

Fixes bug in python3: "the JSON object must be str, not 'bytes', there will be no impact to python2.

Hello @aroncds, thank you for the PR.
Do you mind fix the tests ?

Hi @aroncds, if you need any help fixing the tests, just let me know.

Hello @mbodock,  this week I will correct. I checked that the FakeResponse class used for the test, does not have the json method, I will check the best solution.


Build.js errors with Raw.html not found?

when i run build.js i get this error
parsing Volume 6
parsing Volume 7
parsing Volume 8
parsing Volume 8.5 Side Stories
parsing Volume 9
parsing Volume 10
parsing Volume 11
parsing Volume 12
parsing Volume 13
parsing Volume 13.5 Side Stories
parsing Volume 14
parsing Volume 15
parsing Volume 16 - Edited MTL
parsing Volume 17 - Edited MTL
parsing Volume 18 - Edited MTL
parsing Volume 19 - Edited MTL
parsing Volume 20 - Edited MTL
skipping Volume 21 - In Progress
parsing Special Booklet 1
node:internal/process/promises:288
            triggerUncaughtException(err, true /* fromPromise */);
            ^

[Error: ENOENT: no such file or directory, open '/home/runner/work/tensurafan.github.io/tensurafan.github.io/ln/v6/raw.html'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: '/home/runner/work/tensurafan.github.io/tensurafan.github.io/ln/v6/raw.html'
}

hmm... odd. will look into this. can you try again by running npm run build from the root of the project? it might be because you're running it from a weird directory. might help. otherwise, I'd need to seriously debug this somehow.

Ah Right, I just remembered! A while back, we migrated away from using an NPM build command into a Python build setup to take advantage of markdown features and streamline edits, updates, deployment, etc. I'll have to ask @VoxelCubes what the new build setup is.

The previous build process using the raw.html files was deprecated. You don't need a build step, any changes to files outside the ln folder will simply update live. You can run a local slime reader with npm start from the project root directory. You'll be able to find it at localhost:9001 then.

So I talked to @VoxelCubes and it seems that the current most up to date builder script does not exist in this repo as it is a pile of spaghetti. According to vox: "I haven't released it because it's a bit finnicky due to markdown not being a specification per-se, every plain text file is valid markdown, so someone using it will always find a way to break it and I just don't wanna deal with that. Also, lots of slime-specific stuff just hard coded, so I either try to make this accommodating to other properties or it just stays as the slime tool."
If you want to run the server locally, you can use npm start unfortunately, the only one who can actually build the app is vox right now. That said, if you want to submit a change, you can just update the corrisponding markdown file and vox will re-build it. If you want to addapt the slime reader for another series, I can probs help and adapt the original build.js to the new task.

Changes to volume sources in the ln/sources markdown files are welcome in a merge request, no modifications to auto-generated html in the ln folder can be accepted.


.NET SDK support for Management policies in Azure storage account.

I am using .NET SDK to create blob containers on the fly and it's not feasible to set policy manually or CLI/PowerShell every time a container is created using SDK. There should be a configuration during creation APIs in SDK to support the same, I didn't find any documentation for the same or is it being developed? Can someone from team help me into this?

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

ID: 7f84b325-33af-86ab-749e-faec2e01a1f3
Version Independent ID: 87036460-df59-9239-680d-29c68a0490bb
Content: az storage account management-policy
Content Source: src/azure-cli/azure/cli/command_modules/storage/_help.py
Service: storage
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

@hem-sharma  this is Azure CLI repo, please create an issue in PowerShell repo. Thanks


group_members:enforce:true lead to deletion of users from SAML SSO

We have SAML SSO configured at our company root level with about 400 ish users. eg:  https://gitlab.com/company_root
Current Behaviour
By trying to link another group to this root level as group member eg:
projects_and_groups:
  "company_root/*":
    group_members:
      enforce: true
      groups:
        company_root/groups/another_group:
          group_access: 40

The user_before which fetch from https://github.com/gitlabform/gitlabform/blob/f96efbe89ad4ae707a5d55ff476be825b8bb16d2/gitlabform/processors/group/group_members_processor.py#L175  seems to have all users from SAML SSO.
and then with enforce: true it basically go deleting all those SAML SSO users from group https://github.com/gitlabform/gitlabform/blob/f96efbe89ad4ae707a5d55ff476be825b8bb16d2/gitlabform/processors/group/group_members_processor.py#L266-L268
Suggested Behaviour
SAML SSO users should not be included in these when enforce as this will cause destructive results by deleting the membership link for those SAML SSO users. The SAML user still exists in Gitlab but it will need to be re-auth to create the membership again and they will also be removed as project/group members as well and need to be assigned back after re-auth.

I might not be understanding the intended setup.
From your sample config, it seems you're trying to share a subgroup with a parent group? Can that even be done in GitLab? For example: adding  company_root/groups/another_group as members to the company_root group? Even if it can be done, that means members of another_group will also be member of groups because of inheritance from company_root group. It doesn't quite make sense to me.
Aside from the above confusion, how is the SAML configured for company_root group? It's not in the sample config. Is that being done manually? If yes, enforce key shouldn't be used or should be set to false (default). That would apply to any other config where enforce key is supported. Purpose of enforce key is to make sure the setup in gitlab matches the config.

oh I forgot to mention that have user groups only hierarchy built under the path  company_root/groups and we set that group with group_members:inherit:false  so it won't be inheriting group we link at company_root.
and, Yes we could make company_root/groups/directors for example and link it at company_root and all projects under our company org will then have this company_root/groups/directors as a group member, this is working as expected in GitLab.
The company_root is the only place having SAML SSO configured.
May be if we can add additional note into that group_members:enforce:true doc that if you have SAML SSO configured on such group the users will be unlinked and probably not what you wanted etc that might help etc.

oh I forgot to mention that have we user groups only hierarchy built under the path company_root/groups and we set that group with group_members:inherit:false so it won't be inheriting group we link at company_root.

I think there are some misunderstanding going on. The group_members:inherit:false is a feature of gitlabform; not from gitlab. The inherit: false config that you can use in gitlabform is simply used for preparing effective config that gitlabform will use. It allows you to break configuration inheritance of gitlabform. Again, it's not a feature of gitlab. Please see the docs for details: https://gitlabform.github.io/gitlabform/reference/#breaking-inheritance

Yes we could make company_root/groups/directors for example and link it at company_root

You're right! I just tried it and gitlab does allow adding subgroup as a member to an ancestor group. I'm not really sure why that's allowed and what the use case for it either. But, users in the directors group will also have access to company_root/groups because of membership interitance by gitlab. There aren't any "inheritance breaking" setting as far as I know. There's actually an open issue for it in gitlab: https://gitlab.com/gitlab-org/gitlab/-/issues/383662

May be if we can add additional note into that group_members:enforce:true doc that if you have SAML SSO configured on such group the users will be unlinked

Yeah, that makes sense. Please consider contributing to the docs.
Another option is possibly enhance the usage of enforce. Maybe it shouldn't be applied to the users that are added via SAML linking. @TimKnight-DWP - what do you think?

I think there are some misunderstanding going on. The group_members:inherit:false is a feature of gitlabform; not from gitlab. The inherit: false config that you can use in gitlabform is simply used for preparing effective config that gitlabform will use. It allows you to break configuration inheritance of gitlabform. Again, it's not a feature of gitlab. Please see the docs for details: https://gitlabform.github.io/gitlabform/reference/#breaking-inheritance

Yes, You're right it will have been inherited from root company_group anyway but since we link the with Maintainer role not Owner it won't have permission to manage groups and so still ok for us.
However, This is another point actually, the current usage of <section>:inherit:false needed to be put at subgroup(path) and basically if we don't want it to be inherit at all then that means we need to keep adding this <section>:inherit:false into every possible subgroup which is kinda tedious and can not cover new subgroup that will be created in the future. For certain section where inheritance also take place in Gitlab (eg: group_members, CI/CD variables etc), Shouldn't there is some kind of flag to set at it's own level and prevent inheritance from happening altogether? current inherit seems to indicate parent inheritance right? can we add something like child_inherit to do this? so in this case I would be able to set group_members:child_inherit:false at company_root level config without having to bother with subgroup paths at all since for group members they're inherit by Gitlab anyway?

gitlabform is designed using configuration hierarchy pattern. Config defined in parent level is applied to the child level resources (projects or groups) by first generating an effective configuration for each of them.  Please see the docs for details: https://gitlabform.github.io/gitlabform/reference/#configuration-hierarchy
The inherit:false feature allows preventing the top level config being used at the child level. What you're looking for is a separate feature request, although I think child_inherit: false is kinda confusing. Maybe something like pass_down: <true | false> or a better keyword. Anyways, I can see it complimenting the inherit: <true | false>. We should create a separate issue for it. Will you be able to contribute this feature?


What happens with the message if the service fails?

Hi, i have a doubt.
What happens with the rabbitmq message if the service fails for some reason? There is any way of process the message again? Or yet, after a specific number of tries the messages goes to the dead letter queue? There is any way to control or do that is Nameko? If not, you guys have a plan to implement this in the future?
Thanks.

The AMQP entrypoints (@rpc, @event_handler and @consume) all guarantee "at least once" delivery. This is the case because they acknowledge the message only after it's been processed -- i.e. after the service method exits.
If the connection to the broker is lost (if the service crashes, for example, or any other reason) any outstanding "un-ack'd" messages go back to being "ready", meaning they can be processed by another consumer. This is where "at least once" comes from -- the message will be picked up by a second worker, but there's no way to know whether it was successfully processed by the first worker or not.
Messages are acknowledged when the worker completes, irrespective of whether the worker returned a normal response or raised an exception. The @event_handler and @consume entrypoints have an additional requeue_on_error flag; if this is set, messages resulting in worker exceptions are requeued. This is sometimes useful but can be dangerous if you don't combine it with checks to make sure messages don't end up in an infinite loop.
RabbitMQ unfortunately does not support the "max deliveries" message property, but you can implement something like it yourself.
This kind of question is better suited to the mailing list. If you have followup questions please ask them there, and I'll close this issue.


x/tools/gopls: support server-side fuzzy matching

What version of Go are you using (go version)?

$ go version
go version devel +44c9354c5a Fri Jun 21 05:21:30 2019 +0000 linux/amd64
$ go list -m golang.org/x/tools
golang.org/x/tools v0.0.0-20190620191750-1fa568393b23
$ go list -m golang.org/x/tools/gopls
golang.org/x/tools/gopls v0.0.0-20190620191750-1fa568393b23

Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE="on"
GOARCH="amd64"
GOBIN="/home/myitcv/gostuff/src/github.com/myitcv/govim/cmd/govim/.bin"
GOCACHE="/home/myitcv/.cache/go-build"
GOENV="/home/myitcv/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/myitcv/gostuff"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/home/myitcv/gos"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/home/myitcv/gos/pkg/tool/linux_amd64"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/myitcv/gostuff/src/github.com/myitcv/govim/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build615872690=/tmp/go-build -gno-record-gcc-switches"

What did you do?
Raising this following a conversation with @muirrn and @ianthehat
There are a variety of approaches to deciding what completion candidates to offer:

fuzzy match
case insensitive
something very vogue like an AI or ML based approach
...

We ultimately, however, need a way for users to configure which method they want.
Whilst there will likely be necessary discussion on what is the most sensible default, this issue is a request to make the option configurable.
The same option could also define the behaviour of functions like https://github.com/golang/go/issues/32749, for example

cc @stamblerre @ianthehat

In our discussion @muirrn suggested that the current default method is such that a lowercase partial pattern implies case insensitive candidate selection. However I don't think I'm seeing this:
package main

type S struct{}

func (s *S) Help() {}

func main() {
	var s *S
	s.h
}

Trying to complete s.h results in no completion candidates. If instead this is changed to s.H and completion attempted, Help is correctly returned as the single candidate.
Which seems to suggest that candidate selection is case sensitive.

Sorry @myitcv, I was talking specifically about the un-merged fuzzy matching logic. Currently gopls has no matching logic at all, it is always an exact prefix match. Editors however can fetch all the candidates when you type s. and then have smart filtering as you continue to type.

Sorry @myitcv, I was talking specifically about the un-merged fuzzy matching logic. Currently gopls has no matching logic at all, it is always an exact prefix match

Thanks for clarifying.

Editors however can fetch all the candidates when you type s. and then have smart filtering as you continue to type.

This is exactly why I don't think this logic belongs in editors. Because qualified identifier/selector-based completions are only part of the picture. But also because presumably the editors need to keep asking for completion candidates because they can't know when to stop? At which point, gopls might as well do the fuzzy matching bit?
Would this not also give us consistency across editors?
Apologies if part of the reason we're talking past each other here is a difference between the different editor approaches here. My experience is only Vim.

qualified identifier/selector-based completions are only part of the picture.

I think VSCode works the same for unqualified completions. If you haven't typed anything yet you can manually trigger a completion, or once you type your first character it will fetch the completions and then filter in the editor as you continue typing. Emacs works similarly by default, but LSP completions in Emacs do not currently support fuzzy matching.

presumably the editors need to keep asking for completion candidates

VSCode does not refetch candidates as long as you are still typing in the same identifier. Emacs works the same way normally, but currently it refetches candidates after every keystroke to work around a previous bug.
But, I think we are in agreement in regards to who should be doing the matching. Server side matching should give a better (faster, more consistent) experience overall. The downside is it pushes the various matching preferences/options from the editor into gopls (i.e. gopls might not support the matching/completion options you are used to in your editor).
If you want to try out server side fuzzy matching (as well as deep completions) you can use this branch https://github.com/muirrn/tools/tree/lsp-fuzzy (just rebased on master). Then if you complete something like "conBack" it will complete to "context.Background()".

But, I think we are in agreement in regards to who should be doing the matching.

Yes, indeed.

The downside is it pushes the various matching preferences/options from the editor into gopls

I think it forces the editor (plugin) to map between the two, yes, and tie the two together from the user's perspective. But I don't see that as a problem: editor (plugins) are already having to do this sort of mapping in any case with LSP concepts.
And it should be relatively easy to add additional strategies to the gopls side, if we find a gap.

If you want to try out server side fuzzy matching.... This also works for "deep" completing into structs

I'm very keen to give this a try and see how my brain maps to it! Will try and find some time to do so. Thanks again for your work experimenting with this.

I agree that we definitely need fuzzy matching on the server side in gopls (in progress, I'll be adding a fuzzy matching library soon). My worry with it is the same issue of "mapping" between gopls and the editor, particularly VSCode. If there are differences between the VSCode fuzzy matching and the gopls fuzzy matching, it might make for a confusing experience for VSCode users.

My worry with it is the same issue of "mapping" between gopls and the editor, particularly VSCode

There are other editors out there 😉
This was exactly my point above. If, for any given editor, we find a gap/difference in the strategy expected, we can fill that with an alternate implementation within gopls, driven by config.
I don't think we can try and cover all bases for all editors with a single default.

Sorry, I totally phrased that incorrectly. I said VSCode specifically because it's the only editor I knew about that does the fuzzy matching.
There is also a way to force the client to use gopls fuzzy matching - by setting isIncomplete to true in the completion results. That forces the client to ask gopls for completions on every keystroke rather than a single time as VSCode currently does. That might be a reasonable approach to start with, since it's basically what every non-VSCode editor does.

@muirrn - the work in https://go-review.googlesource.com/c/tools/+/190099 looks great.
Is it worth leaving this issue open pending making the option for fuzzy matching independent of deep completions?

Oops, forgot to tag this issue.
I think we should keep this open until fuzzy matching is "released" (i.e. enabled by default, perhaps with a config flag to disable).
On that note, I've been assuming that everyone wants fuzzy matching, but that sounds like a silly assumption. We need to gather feedback on use cases to disable fuzzy matching, and also detailed feedback on sub-optimal results from the fuzzy algorithm. Maybe we can gather that feedback on this issue as well?

@myitcv can you kindly try out fuzzy matching on master and see if you think it satisfies this issue?

@muirrn - sure will. Currently blocked on https://github.com/golang/go/issues/33647 but I'll try and do some manual testing to side step that.

@muirrn - the options for disabling deep completions and fuzzy matching appear to work, thank you. For now, deep completions and fuzzy matching are enabled by default for govim users (pending https://github.com/myitcv/govim/issues/321)
I've just raised https://github.com/myitcv/govim/issues/490 to investigate adding support in govim for the gopls server-side fuzzy matching.
If you are happy that server-side fuzzy matching is working, then please do close this issue :)
Thanks for working on this!

Thanks for testing it out!

please do close this issue

I think this issue can be closed now, but I don't have the power to do it myself :)


Invalid call. Nonexistent function 'tile_get_texture' in base 'ImageTexture'.

Hi, I tried using this add on but hit this error message for nonexistent function. I'm using the 0.2 version from the asset library for GODOT v2.1.2.

It looks like you put a texture where a tile map should be. Try making Border Textures  null. (Border Textures is optional so you can delete it)

Ah okay, yes I now see the difference between textures and texture here. I should be able to make good use of this plug in. Thx.


Update classify_image.js

Output top 5 predict results instead of 1.

The output top-5 loop seems to be a bit dumb, can we do something like sort and output top-5?

fixed.


Responsive logging

What is the expected enhancement?
From #719 and #723 we should be able to configure responsive logging depending of the environment where we are. DEBUG for development, WARNING for production and so on.
More info here: https://docs.djangoproject.com/en/4.2/howto/logging/
Little example provided:
"level": os.getenv("DJANGO_LOG_LEVEL", "WARNING")

I will start working on this.


Wrong sample provided in doc and missing info.

Issue 1
The sample output given for the Test validation response payload is {"ValidationResponse":"512d38b6-c7b8-40c8-89fe-f46f9e9622b6"}. Even in the screenshot it shows this exact response. However, that does not work in practice. It should be {"validationResponse":"512d38b6-c7b8-40c8-89fe-f46f9e9622b6"}, where the 'v' in "ValidationResponse" is small.
Issue 2
No where in the document it mentions that Azure also sends aeg-event-type header which is set to SubscriptionValidation for validation requests and to Notification for actual events. Without these the payloads are not accepted by Sample azure-event-grid-viewer by Microsoft.

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

ID: cc8ec210-042d-e1e3-eebc-8c0ef5921d7a
Version Independent ID: 7e27c3bc-60ed-064c-9639-1a9b9b79a6a8
Content: Receive events from Azure Event Grid to an HTTP endpoint - Azure Event Grid
Content Source: articles/event-grid/receive-events.md
Service: event-grid
GitHub Login: @spelluru
Microsoft Alias: spelluru

@applegrew  Thank you for your feedback! We will review and update as appropriate.

@applegrew  Thanks for reporting this item! I have updated the doc and it will be published soon. We appreciate the feedback!
For your second question I have already reached out to the author @spelluru. He will look into it.
We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.

For issue #2, I have already added the Message Headers section to the article:
https://docs.microsoft.com/en-us/azure/event-grid/receive-events#message-headers


Check that all files exist before starting

It's a pain, particularly with the CEMS data, to get partway through and realize the files you need aren't in the datastore. This verify_input_files function checks that they're all present before starting.

Pull Request Test Coverage Report for Build 168

1 of 46 (2.17%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.8%) to 64.505%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pudl/init.py
1
46
2.17%

Totals

Change from base Build 167:
-0.8%

Covered Lines:
2377

Relevant Lines:
3685

💛  - Coveralls


Tweak expand fn

Commit #1: Make expand fn more robust--handle empty/null/undefined better, add tests
Commit #2: Update sinon API call due to deprecation of "reset" fn
Commit #3: clean up some debug output

Coverage increased (+0.09%) to 97.959% when pulling 8838d627745589f1b608776e96f4ee8c4f8c4fe4 on tweak-expand-fn into 13328ae443bd12a3658fd29c14a97ee238c8e787 on master.


fix(listing management): fix the listings not updating within the gri…

Fixes this issue: After you edit/delete a listing, the Listing Management table view doesn't seem to be updating at all until a hard refresh occurs. The tabs on the left side also need a hard refresh to update.

Numbers in the left side bar update after deleting listings from grid view 👍

:+1:


Willow add num_uniq_individuals_call_or_text

Adds a column with the number of unique individuals with any communication with the individual over time

Hi, this change is causing the documentation build to fail (https://readthedocs.org/projects/forest-docs/builds/21979017/), so your changes are not showing up (https://forest.beiwe.org/en/latest/#id1). Please fix, thanks!


Styling: Song details

Song details page should look like the design of Joost,
We want to see information about the current song and be able to control it.
In the future we want to add Artist information on this page aswell.

We did, we still need to fine-tune it for the last iteration. But it looks really good! It's more and more alive


convert question how to keep  video conversion

How to ensure the output of video conversion is adaptively scaled while hard setting 16X9

Thanks for your question @lgb861213. You can control how to scale you video input to the output by using the setting Scaling behavior in AWS Elemental MediaConvert. The default setting is "Fit with padding".
Please review the Video Scaling section in the MediaConvert User guide: https://docs.aws.amazon.com/mediaconvert/latest/ug/video-scaling.html

Feel free to re-open with an update or additional questions


UserState in AdapterExtensions.UseState should not be required

The AdapterExtensions.UseState() method introduced by the adaptive refactorings takes a conversation state and a user state parameters, conversation state is required for dialogs but userstate should not be required (may developers don't use user state),
This extension method and the UserStorage extension methods are new from Adaptive and I am not clear on the implications of not setting UserState.

@tomlm is working on a PR now. Closing by lunch.


Add a dropdown button with two options "Light Theme" and "Dark Theme"

@mariobehling  @championswimmer  @juslee  Solved here  #251

Merged , Closing this :)


Website contents

closes #7885
also updates dipy intersphinx redirect to current release (problem still exists), and removes a spurious dash in the CZI entry of the funders box.

Thanks @drammock !


Remove incorrect tooltips in Appearance pref panel

This is a minor fix-up. The Preferences/Appearance panel option for Transparent/Hidden titlebar erroneously had the tooltips for the auto-updater preference. I'm guessing someone copy-and-pasted the checkbox button from the updater pref when the titlebar pref was implemented. All I did was delete the incorrect tooltips and Xcode labels. FWIW, the tooltip used to say...

MacVim will automatically download and install updates without prompting. The updated version will be used the next time MacVim starts.

...when you hovered over the Transparent/Hidden titlebar checkbox options. Now it doesn't show a tooltip at all.

Looks good. Thanks!


 %
                   (self._mock_name or 'mock'))
>           raise AssertionError(msg)
E           AssertionError: Expected 'barcode_reader' to have been called.

/nix/store/al6g1zbk8li6p8mcyp0h60d08jaahf8c-python3-3.10.9/lib/python3.10/unittest/mock.py:898: AssertionError
----------------------------- Captured stderr call -----------------------------
[2023-01-02 08:45:26,070] [WARNING] [paperless.barcodes] Falling back to pdf2image because:
[2023-01-02 08:45:26,074] [WARNING] [paperless.barcodes] Exception during barcode scanning: Unable to get page count. Is poppler installed and in PATH?
------------------------------ Captured log call -------------------------------
DEBUG    paperless.barcodes:barcodes.py:71 Detected mime type: application/pdf
WARNING  paperless.barcodes:barcodes.py:171 Falling back to pdf2image because:
WARNING  paperless.barcodes:barcodes.py:181 Exception during barcode scanning: Unable to get page count. Is poppler installed and in PATH?

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

@erikarvstedt I'm looking into that ATM

@erikarvstedt I fixed it in this PR, as paperless-ngx fails without the first fix, anyway.
The nixOS test timeout was due to a race condition in the startup of the celery worker. The celery scheduler first runs the migration scripts (in preStart) and isn't available to the worker yet. The worker fails and after reaching the restart Limit of 5, it will not be restarted. This causes the documents to not be consumed and the curl call to timeout.
The fix was rather easy then. I added a line with after in the systemd module which fixes the race condition.

@erikarvstedt thanks! I applied the fixup.


PSPKI <IP_ADDRESS> does not auto-load

Been trying to manually install PSPKI in an offline environment.
I place the module-files inside a PSPKI folder under C:\Program Files\WindowsPowershell\Modules and expect to be able to run commands using powershell, but the module is not available.
I CAN Import-Module PSPKI and it is listed under Get-Module -ListAvailable.
Tests with version <IP_ADDRESS> show it works as intended.

I'm not responsible for module autoload. If you can execute commands after Import-Module PSPKI, then module is installed correctly. Autoload depends on PowerShell version. On some versions, the module is autoloaded, on others not.

Ok! Thanks for your quick response! Running powershell 5.0 and will look into autoloading when my certificate templates are up and running.


styles in actionsheet not effect in android

I'm trying to change style in actionsheet but it not effect at all
          <ActionSheet
                        ref={o => this.ActionSheet = o}
                        options={options}
                        cancelButtonIndex={2}
                        onPress={(index) => { this._imagePick(index) }}
                        styles={{messageBox: { height: 60 },body:{backgroundColor:'red'}}}
                        />

the backgroundcolor style stay white

same here I try to add the border and nothing happens

As a workaround, you can copy the entire styles from: https://github.com/beefe/react-native-actionsheet/blob/master/lib/styles.js and customize it by your needs

actionsheet styles are working fine, you have to target right element of stylesheet. for example if you want to change background color target body
body: {
backgroundColor: '#e5e5e5'
},
follow link mentioned by @rtrufin above to see which element to target while customising styles for action sheet

I faced the same issue but then i noticed that i was not importing the action sheet correctly. Make sure you import it like:
import {ActionSheetCustom as ActionSheet} from 'react-native-actionsheet';
Above worked for me.

@TayyabaAslam3317 by using
import {ActionSheetCustom as ActionSheet} from 'react-native-actionsheet';
My application got stuck while opening the actionsheet most of the times, any help?