Adding users/self/media/liked

I added the ability to get the media liked by the authenticated user.
That was my need, I have no idea whether it's of any use in any other use case, so feel free to not pull if you don't think it's of general interest.

Damn, wrong branch. I did your instructions honest.


nice work ,thank you

hey jussihi
do you have DISCORD or email address ?
so that i think you could teach me on some project

he wont he is lonewolf :D

Ohh..  It's ok , and can you resolve my problem ? Do U have DISCORD or ... ?

I won't give any personal support, and the github issue pages are meant to point code defects of the code so they could be fixed. This is not a "how to compile with VS" newbie forum. I personally hate it when it is being misused.

thank god! lol


feat(controller): Apply Warehouse Git subscription path filters to all CommitSelectionStrategy types

Fixes #1896

@maksimstankevic this looks great. Only nit is that this comment might not be relevant anymore since there's no early return for this selection strategy.
https://github.com/akuity/kargo/blob/fbea61f1384cc226922f2b6657f0fa27bd1fbdf2/internal/controller/warehouses/git.go#L175C3-L177C13


How to delete file from storage?

storage handling delete files ??
const FirebaseStack = new Firestack();
const del = FirebaseStack.storage.ref(/users/${uid}/${imageName});
del.delete();

Delete file has been implemented on my v3 fork: https://github.com/Salakar/react-native-firestack


AMAROC-768 add heigh cloud flag and allow NSC

DRAFT: Add high clouds Flag

Add a high clouds flag to data in case we discard more hits above MSA than MAX_HITS_OKTA0
Set NSC instead of NCD in case the above flag is True when we create the METAR message.

Checklists:

[x] New code includes dedicated tests.
[x] New code has been linted.
[x] New code follows the project's style.
[x] New code is compatible with the 3-Clause BSD license.
[x] CHANGELOG has been updated.
[x] AUTHORS has been updated.
[x] Copyright years in module docstrings have been updated.

Looks good @regDaniel. I think a small tweak is needed to handle the case when there is a significant layer (or more) in the region between the MSA and the MSA + Delta MSA

absolutely. good catch, thanks! I'll take your suggestions and will think about how to best implement it.

Hi @fpavogt , thanks a lot for your review! I implemented the search for layers in buffer along your suggestions and added a test. Could you double-check if it's fine?


Rx.NET reactive or what ever?

Hi I'm bit confused,
because I have find this Rx.NET,  I think is official one from Microsoft
but this is the same?
https://www.nuget.org/packages/Rx-Main/2.3.0-beta2... it's the same as this?
which is the latest release? I like reactive and I'd like to learn more but why 2 libs?
and where is the nuget package...?
thanks

nobody can answer? I know is nubie question maybe...

Yes, https://www.nuget.org/packages/Rx-Main is the offical Reactive Extensions release.
2.2.5 is the latest stable version, 2.3.0-beta2 is the latest prerelease version

ok thanks :+1:

There is no active development anymore? 6 months ago latest commit.
What for future versions? Is IObservable and IObserver the only thing that is left?

@GeertVL I can't speak for the team, but we're looking to give this project a bit of a reboot in the coming weeks. Once we have something to announce, you'll hear about it!

Can we close this issue.

@shiftkey @bartdesmet would love to know what is happening with regard the IRP work demoed almost a year ago?  @LeeCampbell I'd be ok with closing the issue but opening a general project update needed; reference this issue given @shiftkey comment above ;) just my 2p worth

@shiftkey @bartdesmet any announcement yet that I missed? or any roadmap publishment? Can we help? You could close this issue if we know where this project is going.

Please see the announcement here: http://www.dotnetfoundation.org/blog/rx-net-welcome

Thank you. Great news!


Correlate a Toast with the one which has Just Hidden

It would be good if the onHidden callback passed a parameter enabling the executing code to identify which Toast was being hidden.
Currently, there's no way to correlate a toast that is hiding/hidden.
In the scenario I am facing, I am pushing each message into a MessageBoard at the top of the page as the onHidden handler fires.
But they may hide in a different order that that in which they are launched.
For example, a user may hover over one Toast, meaning that a Toast which came after it hides before it.
This messes up the order in which messages are added to the message board.
As a work around, I'm now adding them to the board as the Toast is launched. But it would be more elegant to add it when the Toast disappears.
Cheers

Have you tried looking at the code on the demo page. There is a black/gray bar in the bottomif you click on it you'll see what they call glimpse.  This javascript file has some features which may help you for example
    toastr.subscribe(receiveToasts);

    function receiveToasts(args) {
        var data = args;
        !rendered ? preexistingToasts.push(data) : write(data);
    }

By subscribing a function to the toast it'll trigger on completion. I have my doubts if this works onclick though.
The code in the function pushes the toast to the preexistingToasts when its not being rendered anymore. I hope this hint can help you achieve your goal (this isn't a complete tutorial i suggest reading and understanding the code in the javascript file).


AVRO-1987 Add @deprecated tag to getConverion method

As part of AVRO-1972 a typo was fixed.
To inform the users of the same, a @Deprecated tag has been added to the incorrect function name.

Thanks for doing this change, @spacharya.
Could you add the new renamed method as well? (The idea is to have the new method in the same time we deprecate the old one so the consumers will have time to rewrite they code to use the new one before we remove the old in the next major release.)
The message for the deprecated method shall point to the correctly named one.

Thanks @gszadovszky .
I have made the changes.

Thanks, @spacharya.
+1

Sorry, @spacharya, but I've stolen the opportunity to push this one yourself. :) Congrats for the committership, BTW.
I've committed to 1.8.


"Hârtop" is listed in the drop-down menu

Description:
"Hârtop" is listed in the drop-down menu alongside its corresponding county according to the law
Precondition:
The website is up an running.

Step 1
Type "Hârtop" in the search bar.

Expected results
The location is listed in the drop-down menu as "Comuna Hârtop, SUCEAVA".


vulkan - 4.0 dev - shaders sometimes fail to compile

Godot version: Godot vulkan branch
OS/device including version: Arch Linux/Manjaro
Issue description: I have noticed on different levels of my game some shaders will fail to compile, while on other levels I load the shader will compile fine.
Typically the editor seems to suffer this problem far less, ie. if I open my level to edit it seems far less likely to fail.
Steps to reproduce:
Minimal reproduction project:
I have some sample C++ material here that seems to fail to compile rather a lot
https://drive.google.com/file/d/19onSdZR23YJfLb4yvXqralKUX_tsj8qF/view?usp=sharing
The compile error I get:
At: servers/visual/rasterizer_rd/shader_rd.cpp:346.
    ERROR: _compile_variant: Failed parse:
    ERROR: 0:355: 'location' : overlapping use of location 11
    ERROR: 1 compilation errors.  No code generated.

the problematic line it is complaining about:
varying float 	vertex_height;

@supagu Is the issue still valid in the newest master?

Hey @KoBeWi I unfortunately don't have time to look at this issue any time soon. I will check again next year when I hopefully have some time to get back to working on my game.

So it can be assumed the issue is fixed by that time. Comment if you can still reproduce.


Could you release a new version?

It's been quite a while since you released a new version. Could you release a new version?

Done, thanks for the bump :)


allow defining a list of allowed superusers

About this change - What it does
Introduces the aiven.pg_security_agent_reserved_roles config option. A comma separated list of roles that are allowed to be assigned the superuser property can be defined. Trying to grant superuser to any role not in the list, regardless of the 'context' (elevated or extension install) will be denied.
Why this way
Adds more flexibility in being able to grant superuser to some trusted roles by default, but denying this in other contexts.

@staaldraad This seems reasonable to me - in my original testing I didn't have an ext on hand that utilised pg_user, apologies.

🎉 the original fix was/is good. Took me a while to figure out what was going on, not until realising that pg_user was common between the two failing exts and reading source for system views did it all click together.


Allow non-floating point samples to return floating point averages

This allows non-floating point stat values to yield floating point averages when sampling them.
related to #1533

Current coverage is 40.08% (diff: 0.00%)

Merging #2064 into master will increase coverage by 0.02%

@@             master      #2064   diff @@
==========================================
  Files          1581       1581
  Lines         54489      54514    +25
  Methods       10741      10745     +4
  Messages          0          0
  Branches       7453       7456     +3
==========================================
+ Hits          21832      21854    +22
- Misses        32657      32660     +3
  Partials          0          0

Powered by Codecov. Last update d8266e2...00103dc


Adding_doc_for_bridging

This document provides an overview of the bonding mechanism using a Polygon LP-token and of the design enabling that

@mariapiamo please add that doc reference in the main README in the bridging section.


🐛 unable to delete valkyrie resource with slug

Summary
if a user deletes a slug resource from the UI, it says it was successful, but it doesn't get removed from the works index page. Then when you click on it, it errors out saying that the work is not found.
Is this slug related?
Acceptance Criteria

[ ] A user should be able to delete works

Screenshots or Video
Testing Instructions
Notes
related

#714

Per LaRita,
"Unable to delete a work because of an issue with the find_parents query, which uses find_inverse_relationships_by query. It cycles through all services to be sure to find all parents and fails on the ActiveFedora part, so I’m trying to figure out how to do the overrides appropriately."

todo
update hyku's hyrax.
update the knapsack's hyku

dupe of https://github.com/scientist-softserv/adventist_knapsack/issues/732 ?


feat(FX-3239): Pill component enhancement and stories

The type of this PR is: Enhancement

This PR resolves FX-3239
Description

PR Checklist (tick all before merging)

[x] I have included screenshots or videos to illustrate my changes, or I have not changed anything that impacts the UI.
[x] I have tested my changes on iOS and Android.
[x] I have added tests for my changes, or my changes don't require testing, or I have included a link to a separate Jira ticket covering the tests.
[x] I have added a feature flag, or my changes don't require a feature flag. (How do I add one?)
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added an app state migration, or my changes do not require one. (What are migrations?)
[x] I have added a changelog entry below or my changes do not require one.

Changelog updates
Changelog updates

Cross-platform user-facing changes

iOS user-facing changes

Android user-facing changes

Dev changes

Enhanced Pill component with variants and active props and added to storybook - gkartalis

This PR contains the following changes:

Dev changes (Enhanced Pill component with variants and active props and added to storybook - gkartalis)

  Generated by :no_entry_sign: dangerJS against b84ed8aec2b93d74888f3a6d2e49caf111cb8e4e

Special thanks for adding it to storybook


Upgrade node-sass to 4.5.3 for supporting Node 8

Coverage remained the same at 86.093% when pulling ccd19869ecbc00934ef01621bfb2ba477897dae6 on feature/upgrade-node-sass into 195f34bdb173cba8fd9b62be1b77e6d664512860 on master.


fix: Clear Message in New Conversation

Description
Clears input box and message content when "New Conversation" button is pressed, enhancing user experience and providing a cleaner interface.
This PR fixes #61
Testing
Tested thoroughly to ensure consistent clearing of input content.

wonderful @Arindam200 thank you for knocking these issues out!!! super helpful

wonderful @Arindam200 thank you for knocking these issues out!!! super helpful

Thanks, Jordan! I'm currently Working on another assigned Issue!


Set default meal choice and t-shirt to unset

I think it would be helpful for ordering if we knew how many tickets holders have actually bothered to select a meal choice and a t-shirt size. Now they default to omnivore and large, respectively, so the numbers for those are almost certainly too high.
If we default them to unset instead, we would know.

Indeed. The defaults are making t-shirt and catering count estimates hard.

I'll work on this one.

What's the flow? Should this be close when dev/ep2020 gets merged to master, or should it be closed now?

Issues get closed when merged - it's preferrable to include a fixes #number or closes #number so that the issue gets closed automatically, but it's not obligatory. Regarding branches, we don't use a master branch, we just use a different default branch per year, so dev/ep2020 for the upcoming year.


Cannot launch web extension using basic 'yo code' steps

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.64.2 (Universal) Commit: f80445acd5a3dadef24aa209168452a3d97cc326
OS Version: Mac OS Monterey 12.2.1 (21D62)
Chromium Version (launched by VSCode): 94.0.4595.0 (Developer Build)
Chrome Version (available on machine): 98.0.4758.102 (Official Build)

Steps to Reproduce:

Create a web extension using the recommended steps

yo code
New Web Extension
Any name
Accept all defaults
npm
Open with code

In VSCode, launch with "Run Web Extension"

Result: a desktop instance is launched

On the terminal, run npm run run-in-browser

Result: after downloading and unpacking the VS Code Insiders, Chromium on port 3000 shows up but the page is blank. Looking at the Console View of the Developer Tools, there are 71 errors and 13 warnings. Here's the first few lines of the terminal's output

❯ npm run run-in-browser

><EMAIL_ADDRESS>run-in-browser
> vscode-test-web --browserType=chromium --extensionDevelopmentPath=. .

@vscode/test-web: 0.0.15
(node:46699) [DEP0147] DeprecationWarning: In future versions of Node.js, fs.rmdir(path, { recursive: true }) will be removed.  Web extension can also run on the desktop. See https://code.visualstudio.com/api/extension-guides/web-extensions#test-your-web-extension-in-vs-code-running-on-desktop

Please update the dev dependency @vscode/test-web to the latest: "@vscode/test-web": "^0.0.22",

(I'm updating the generator)

Thank you for the quick reply and for all the amazing work you guys are doing on both VSCode and TypeScript.

A suggestion if I may: for my web extension I have actually created two launchers ("Run Desktop" and "Run Web") because some people are not too comfortable with npm.

It works!!!

If creating two launchers is not ideal for the sample, perhaps renaming the existing one to "Run on Desktop"...

@m-paternostro Our debugging currently only works when running on the desktop. That's why we only have that as launch config.


test: add code snippets for using bigframes.ml

Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

[ ] Make sure to open an issue as a bug/issue before writing your code!  That way we can discuss the change, evaluate designs, and agree on the general idea
[ ] Ensure the tests and linter pass
[ ] Code coverage does not decrease (if any source code was changed)
[ ] Appropriate docs were updated (if necessary)

Fixes #<issue_number_goes_here> 🦕

The code snippets here are prepared for the content of "Use BigQuery DataFrames" page.
Content: https://docs.google.com/document/d/1N5mbfoTh63SwTRFkqs-j9m_2WIykDKHPKAECvKScDSg/edit#heading=h.nq1i22bqeo4y


Support more scenarios that lead to the policy-server deployment to be updated

Right now the policy-server deployment is restarted only when a policy is added/removed/updated.
We should also cover the following cases:

The user wants to change the number of replicas of the policy-server Deployment
The policy-server image to be used is changed

The latter point is really important, because we need to perform a "clean rollout" of the policy-server deployment in order to update to a more recent version of its image.

Closing, this is a duplicate of https://github.com/kubewarden/kubewarden-controller/issues/38


Cookie not being sent with resource requests

We have a use case in which when we loading a page in the webview, it itself does many resource requests and these resource requests require the cookie to be sent with them. Currently, react-native-webview can only intercept the URLs on new page load and not for the resource requests sent by the page itself.
Proposed solution
We can use a map to keep the record of the "authority name" of the URL and the cookie for it. We get this data from the header in the source prop. We can then override the shouldInterceptRequest callback in the RNCWebViewClient to intercept and send the cookie according to the "authority name". This will send the cookie with the resource requests which are sent by the page which we loaded.
I can raise a PR for this.

Same here having issue in getting cookie pass into request header for subsequent pages load.


Feature request: Option to calculate delta and the delta of the delta

Now the mfcc uses 12 coefficients? Is it possible to calculate also the delta so the coefficients can get to double or triple the amount to have more accurate matching results?
We need to implement Rung Kutta method for this.  I am not an expert in programming. Is this doable? Or is the performance hit too high?
https://joinerda.github.io/Solving-ODEs-in-Unity/
What are your thoughts?

Sorry for the very late reply.
I would like to explore the option of calculating the DMFCC in multiple frames and adding it behind the current MFCC. In that case, it will have 2N+1 dimensional features, where MFCC is N dimensional and DMCC is N+1 dimensional. Currently, N=12 is fixed, so I will consider adjusting this as well.

I could try to clean up the code I now have and do a pull request. Not sure when I have time.

My previous code for calculating DMFCC was not working correctly. I wanted to start a new try. If you have any draft/ideas to share please let me know.
Meanwhile I found there are options for burst compile to improve speed in cost of precision. Did you test these?
[BurstCompile(FloatMode = FloatMode.Fast)]

and
[BurstCompile(FloatPrecision = FloatPrecision.High)]

Hi @hecomi ,
I think I am quite far along to deploy delta calculation. I will make a draft pull request so you could have a look. I hope to have Tuesday some time to make the pull request and add a demo video.
I don't have a solution for the changed profile that needs 26 array length. I had this in my previous code. But it did give some errors (memory leaks) with the different length of profiles.

Quick test. Still some memory leaks to tackle
https://github.com/hecomi/uLipSync/assets/4112111/ca0e295d-dc1f-4fe1-802d-4b5f324a53a1

every time I create in runtime a new phoneme I get this error:
A Native Collection has not been disposed, resulting in a memory leak. Enable Full StackTraces to get more details.

I shall push the pull request

Memory leaks were solved. Forgot to dispose an offset buffer for managing the memory in the buffer with melcepstrum data.
Pull request created #44


Regent: error 298 from privileges of subtask

Hi,
I have some generated tasks (from rexpr) with (for the real code) generated privileges.
For this dummy case, the rexpr in question is created with this function
function symmetric_interaction_count_kernel(part1, part2, r2)
local kernel = rquote
  var nonfield = part2.i2
  part1.interactions = part1.interactions + 1
  part2.interactions = part2.interactions + 1
  if(part1.core_part_space.mass > 0.01) then
    part1.i2 = part1.i2 - 1
    part1.i3 = part1.i3 + 2
    part1.i4 = false
    part1.i5 = int1d(83)
    part1.i6 = part1.interactions * 2 + part1.i6
--    nonfield = nonfield + 3
--    part1.i3 = nonfield
  end
end
return kernel
end

The code computes the following privileges:
reads(part1.{interactions,i2,i3,i4,i5,i6,core_part_space}, part2.{i2,interactions}
writes(part1.{interactions,i2,i3,i4,i5,i6}, part2.{interactions})

The tasks are generated are run over some (disjoint) partition of the main region, as an optimised version of:
local task run_symmetric_pairwise_task_code( particles: region(ispace(int1d), part), cell_space : partition(disjoint, particles , ispace(int3d)), config : region(ispace(int1d), config_type))
where ... do
  for cell1 in cell_space.colors do
    for cefll2 in cell_space.colors do
      if(cell1 ~= cell2) then
        do_task(cell_space[cell1], cell_space[cell2], config)
      end
    end
  end
end

The parent task's privileges for this rexpr case are:
where reads(particles.{interactions,i2,i3,i4,i5,i6,core_part_space}, particles.core_part_space, config), writes(particles.{interactions,i2,i3,i4,i5,i6}) do

The do_task code loops over all of cell1 and performs the rexpr with "all "of cell2. I know for sure that cell1 and cell2 are never the same, so the same region is never passed to do_task (which would be illegal).
When I run the code with the computed privileges, it fails and gives this error:
[0 - 7f80f8a9a780]    0.036590 {5}{runtime}: [error 298] LEGION ERROR: Parent task run_symmetric_pairwise_task_code (ID 57) of task pairwise_task (ID 61) does not have a region requirement for region (1,1,1) as a parent of child task's region requirement index 2 (from file /home/aidan/Legion/legion/runtime/legion/legion_tasks.cc:1872)
For more information see:
http://legion.stanford.edu/messages/error_code.html#error_code_298

I can remove the error in one of two ways, both which allow the code to run correctly:
Change the parent task's privileges to
where reads(particles, config), writes(particles) do

Alternatively, I can do do_task's privileges to include

writes(part2.{interactions, i2})

Now from the rexpr its clear to me that the write to i2 is not needed, and Regent doesn't believe it should be either for its own checking.
Is there something I'm missing in my understanding of the privileges/region accesses required here? I'll try to create a mini example code in the mean time that reproduces the problem.

I created a mini case (I assume smaller is possible but I wanted to duplicate the syntax as much as possible in case it was needed) showing the problem. It can be fixed by uncommenting the end of line 37 (even though that shouldn't be required, as parts2.i2
is not written to by the task) and attached it here:
replica.txt

I haven't read the code too deeply, but this is probably an instance of https://github.com/StanfordLegion/legion/issues/289. Please read that issue and see if it makes sense of what you're seeing.
If it doesn't prevent any parallelism, the easy thing to do here is to over-approximate the privileges so they don't get split at the parent task.

Yeah I think it is the same issue - I think if I understand that correctly I can do the following with the generated priveleges (at least it worked for the replica code).
If I have
child_task( parts1, parts2)
where
reads(parts1.[read1]), reads(parts2.[read2]), writes(parts1.[write1]), writes(parts2.[write2]) do
...
end

Then I just need to apply all 4 clauses in the parent task too right? Which then shouldn't need over-approximating, just potentially repeated subclauses on the parent, i.e.:
task parent(particles, partition_name) where
reads(particles.[read1]), reads(particles.[read2]), writes(particles.[write1]), writes(particles.[write2]) then
...
end

At least my understanding is the parent task needs to have greater or equal privileges to the child task anyway - does that make sense for the context of #289?

If the parent task is inner then it probably isn't an issue for it to require more privileges than strictly necessary. Legion will permit it to execute before the data is ready (because of inner) and, assuming you have virtual instances, will need to perform an analysis of the child tasks regardless.
I think your new case still looks like #289 to me. Fundamentally it's about getting to a point where the child privileges overlap the parent in some way where a field is read-write in the parent but read-only in the child in such a way that the grouping of one isn't a subset of the other.
Let me know if you're still having issues with this.

I'll have a look into inner tasks at some point, for now I'd worked around this by changing the parent tasks into rquote and embedding them in the main task, but not clear if this may present scalability issues in the future.

If your parent tasks are issuing index launches across the whole machine, then this is actually the recommended way to do it. Generally speaking inner tasks are a programming convenience but not necessarily better for performance.

I'm not sure they will be index launches entirely, probably i should do an index launch and the conditional launch in separate loops which I'll bear in mind.

@LonelyCat124 is this still an issue for you? I think part of this was a duplicate, so if the practical consequences are resolved, I'm inclined to close this.

No longer an issue- I just don't use inner tasks and generate rquotes instead.


Ruby example information

Leo is a dangerous example in the main repository.
Of course good but require 'tdlib-ruby' Not cool! In my opinion it is better to open the module.
This is not an example.
https://github.com/tdlib/td/blob/master/example/ruby/example.rb
Here is a sample of how to make examples:
https://github.com/tdlib/td/blob/master/example/python/tdjson_example.py
This example is safe:
https://github.com/tdlib/td/blob/master/example/go/main.go
But in it it is necessary to supplement the functional https://github.com/tdlib/td/blob/master/example/python/tdjson_example.py
Not for ordinary people who want to try the interface:
https://github.com/tdlib/td/blob/master/example/csharp/TdExample.cs
Have you checked tdlib-ruby? (even this can not. at any time the author can bring to this level an extraneous code. eg: while true do end).
Examples for Android?
Examples for Javascript in the browser?
Examples for WebAssembly?
I did not think at all that it could pass into your prod...In this case, you can classify examples by authors.
It is generally better to bring this part into a separate repository. Create something like google play. Organize something like a code review in it.  Perhaps many will want to share examples of implementation.
In the examples folder, there is no structuring.
Regards

Yes, you are right in both cases. That will be covered in README.md for these examples.
I've added both examples, because to have any example is better than to have nothing. I've seen a lot of misunderstanding that TDLib can be used only from C++ (or Java). So they primary purpose is to show that TDLib can be used from any programming language.

I agree with you, but it's time to discuss in README.
Examples for Android?
Examples for Javascript in the browser?
Examples for WebAssembly?

Using the example for javascript and webassembly, you show the real class.

Initially, it was necessary to focus on emscripten. The rest itself would have turned out.


Refector uploadPDF()

uploadPDF() and uploadEPUB() are essentially the same function, but don't have the same functionality. Added equivalent features to uploadPDF().

added parentId parameter
added id parameter
updated docs

Can you merge this one also please?

Would LOVE to see this make into master.
Is there anything I can do to help?

@cvburgess I have included thoses changes into my fork, plus a fix of reMarkable API url.
https://github.com/Ogdentrod/reMarkable-typescript/pull/26#issuecomment-860181625

LGTM, thank you for your contribution!


Missing qlcplus-fixtureeditor.exe from QLC+ 5.0.0 Beta 3

Uninstalled QLC+ 4.13
Downloaded and installed QLC+ 5.0.0 Beta 3
Installation folder is by default C:\QLC+5
Once installation is complete, Folder "Q Light Controller Plus" is created in the Start Menu Programs with in it :
a shortcut "Q Light Controller Plus" witch point to : C:\QLC+5\qlcplus-qml.exe
and another shortcut "C:\Program Files\QLC+\qlcplus-fixtureeditor.exe" that does not exist !
If you search for "qlcplus-fixtureeditor.exe" in C:\QLC+5, the file is missing too.
Last thing, if you want to uninstall QLC+, it's not listed in Parameters / Installed applications : You need to click on the file "uninstall.exe" on the QLC+ Folder.
Hardware : Dell Inspiron 16 plus 7630 / I i7-13620H / 16Go DDR5 / SSD Crucial T500 2To
Soft : Windows 11 23H2 Build 22631.3593

Are you serious?


feat: Consistent probability sampler

Implements the TraceState: Probability Sampling spec and the associated TraceState Handling spec.
Note: these will probably move to an -experimental or -unstable SDK extension gem.
TODO:

[ ] Sampler composition rules
[ ] Statistical test requirements

Funny that GH interprets every comment as an independent review. Also, I should have just clicked 'start a review' but oh well.
So overall it looks pretty good to me - I think the TODO about the testing stuff is a definite must. I was mostly able to follow the spec and it looks like it does what it's supposed to but I don't think I grasp it well enough to be able to spot problems without running tests on it.
Not sure how we'd do the composition stuff. Do we even have support for composite samplers? I don't see anything in the SDK spec about that in general ... 🤔

I mentioned in a few comments above: I'm in the process of refactoring this based on insights gleaned from reading the Go implementation. 🤞 it'll be more efficient and easier to read & understand ("obviously correct" rather than "not obviously wrong"). I hope to have that pushed up today, or early next week at the latest.

@ahayworth I pushed up the refactor. This is good for another 👀 . Still needs tests & 🤔 about composition.

I'm going to propose implementing (or porting the Go implementation of) the statistical tests in a subsequent PR.
I haven't seen an implementation of the composition rules and I'm inclined to ignore that part of the spec for now.
@ahayworth would you mind taking another 👀 at this before I 🚢 ?

Thanks @robertlaurin ❤


Ordering of in-app messages

Hi,
I have a question regarding ordering of in-app messages sent to a user. The docs mention that in-app messages are stored in a queue, which would imply a first in, first out (FIFO) behavior.
Let's say I send three in-app messages to user A, in the following order: M1, M2, M3.
If I then do this: IterableAPI.inAppManager.getMessages().first, which message would that be? The one that the user received first (M1), or the last one sent (M3)?
Thanks
Viktor

Hi @vrutberg  The messages should arrive in the order they were sent. So in your case it should be M1. Having said that I remember there being a discussion about it and I believe we fixed the issue. Are you noticing anything different?
If you are seeing a bug, please let us know the version of SDK that you are testing on.

Thanks for clarifying @tapashmajumder, that is also what I was expecting. We're seeing different behaviors on our iOS and Android apps -- but it could be because of different implementations in our apps. In the iOS app we manually display the in-app messages using IterableAPI.inAppManager.getMessages(), whereas in the Android app we let the SDK handle it for us.
I think we'll manage to sort it out. Thanks again!


Interpreter.Use allows blank import paths

This is more of a question, "Should Yaegi behave this way?" But I experienced it as a bug, so I'm entering this as a bug report. #1102 introduced a breaking change to Interpreter.Use: previously, an entry like "pkg": reflect.ValueOf(...) would add a package named pkg with an import path of pkg. Now, to get the same effect, the entry should be "pkg/pkg": ....

Issue: Post-#1102, if I Interpreter.Use(interp.Exports{"pkg": ...}), the importPath of the resulting entry is ".".
Question: Does it ever make sense for importPath to be "."?
Solution?: Interpreter.Use panics if importPath == "."

I'm using Yaegi to implement a simple scripting language, so I'm restricting what can be imported:
package main

import (
	"reflect"
	"github.com/traefik/yaegi/interp"
	"github.com/traefik/yaegi/stdlib"
)

func main() {
	api := map[string]reflect.Value{ ... }

	I := interp.New()
	I.Use(interp.Exports{
		"fmt":   stdlib.Symbols["fmt"],
		"customPkg": api,
		// ...
	})

	// keys of I.binPkg = "", "."
}

importPath set to "." makes no sense. Panic in that case is one option, another is to silently ignore the entry (instead of adding a key ".").  Or let Use to return an error, at the cost of an API change. We should probably do that while we can (before bump to v1). This part is error prone for the user, and a feedback from the function would be useful here.

@mvertes I would prefer some form of error. In effect, currently this silently ignores the issue, because it adds a useless entry. If this instead returned an error or panicked, I quickly would have noticed what I did wrong.
Personally, I prefer returning an error, because that allows for other errors in the future, and now is better than post v1. If you want to offload the effort, I would be happy to submit a PR. LMK

Yes, go ahead.
Thank you @firelizzard18

Fixed by 1df5dc2


az role definition create propagation delay

az feedback auto-generates most of the information requested below, as of CLI version 2.0.62

Describe the bug
Running az role definition list returned mixed results right after creating a role using az role definition create:
Its as if the API requests reach different replicas in the backend, and they are out of sync.
Is there a way to wait/block on the replication to finish, so all the following requests will be consistent?
To Reproduce
$ az role definition create --role-definition @role.json
$ az role definition list --query '[?roleName=='\''TestCustomRol'\'']' --scope /providers/Microsoft.Management/managementGroups/devgroup
[]
$ az role definition list --query '[?roleName=='\''TestCustomRol'\'']' --scope /providers/Microsoft.Management/managementGroups/devgroup
[]
az role definition list --query '[?roleName=='\''TestCustomRol'\'']' --scope /providers/Microsoft.Management/managementGroups/devgroup
[
  {
    ...
  ]
]
$ az role definition list --query '[?roleName=='\''TestCustomRol'\'']' --scope /providers/Microsoft.Management/managementGroups/devgroup
[]

Expected behavior
What we want to is to wait until the role is synced and ready for use; how can we do that?

The result of az role definition list comes from ARM service and Azure CLI just returns it as-is.
Does it eventually return the same result?

Eventually yes, but it takes time.
I understand that its a backend issue, because I guess there's no github repository for the API service, so I reported the issue here; can you find the PM/dev responsible for it and let him know of this issue?

can you find the PM/dev responsible for it and let him know of this issue?

@dagoroz, could you help take a look?

Hi @jiasli, do you have an updated on this for us?

ARM service team should take a look

the usual propagation delay is around 5 minutes
the absolute worse we've seen is 30 minutes but this is quite an uncommon scenario.

As @dagoroz suggested, this is the designed behavior of ARM, and affects all client tools like Azure CLI, Azure PowerShell, SDKs, we will close this issue.


Generate sitemap

Cross your fingers that it works with the /app folder

One way to do this is to open a custom endpoint in Payload that returns only an array of url strings per collection BUT since we're using GraphQL on the front-end, there is no need for this because we can build a query that does the exact same thing. Then using data, we can build the sitemap dynamically.

I used next-sitemap to accomplish this. It's done! 👍

I saw that, looks easy. Just a manual process but that's fine for us!

I added a postbuild command so at least it builds when the site deploys ☠


[Live-Site]: Remove kick out option for host

Description
As a part of this story, we will be removing the kickout features for the host. So, that no one can kick out hosts.
AC

The Kickout icon will be removed for the host
For other peers, the kick-out icon should be visible

UX
https://www.figma.com/file/2VtPGJH61Qp0iarkKW6KTO/Live-Site-Detailed-Designs?node-id=0-1&t=HZJjG29OV7RhnusD-0

Verified in staging. It's working fine.
https://github.com/Real-Dev-Squad/website-www/assets/40385118/bff29c6a-900c-4a23-b06a-179800651f59


[bug] Some styles don't animate

Some styles don't animate, for example borderRadius and backgroundColor. I have tried the @tamagui/animations-reanimated and @tamagui/animations-react-native drivers on both expo and next.

Do you have code ?

Same issue. Code:
tamagui.config.ts
import { createAnimations } from '@tamagui/animations-react-native';
import { createFont, createTamagui } from '@tamagui/core';
import { shorthands } from '@tamagui/shorthands';

import { themes } from './themes';
import { tokens } from './tokens';
const interFont = createFont({
    family: 'Inter, Helvetica, Arial, sans-serif',
    size: {
        1: 12,
        2: 14,
        3: 15,
        4: 18,
    },
    lineHeight: {
        1: 17,
        2: 22,
        3: 25,
    },
    weight: {
        4: 300,
        6: 600,
    },
    letterSpacing: {
        4: 0,
        8: -1,
    },
});

const animations = createAnimations({
    fast: {
        damping: 20,
        mass: 1.2,
        stiffness: 250,
    },
    medium: {
        damping: 10,
        mass: 0.9,
        stiffness: 100,
    },
    slow: {
        damping: 20,
        stiffness: 60,
    },
});

export const config = createTamagui({
    themes,
    tokens,
    shorthands,
    fonts: {
        heading: interFont,
        body: interFont,
    },
    animations,
});

Component to animate:
const InputFrame = styled(Stack, {
    name: 'Input',
    focusable: true,
    flexDirection: 'row',
    animation: 'slow',
    borderColor: '$borderColor',
    borderBottomWidth: 1,
    focusStyle: {
        borderColor: '$borderColorFocus',
    },
    variants: {
        invalid: {
            true: {
                borderColor: '$borderErrorColor',
                focusStyle: {
                    borderColor: '$borderErrorColorFocus',
                },
            },
        },
    },
});

Any updates on this?!

I'm wondering the same

@TheEhsanSarshar this would be a great one for you to pick up if you have some time, I think we can start with just animations-react-native since reanimated is going to get an update soon to move over to Moti as the backend.

@natew Ok sure

I'm having a similar issue with the height not animating. backgroundColor is animating fine.
Is it related to this issue?
I'm using @tamagui/animations-react-native to create the animations.
Here's my component:
export function ListEntry() {
  const [isOpen, setIsOpen] = useState(false);

  useEffect(() => {
    setTimeout(() => {
      setIsOpen(!isOpen);
    }, 2000);
  }, [isOpen]);

  return (
    <View
      p="$2"
      jc="center"
      bg={isOpen ? "slateblue" : "tomato"}
      h={isOpen ? "$5" : "$3"}
      animation="lazy"
    >
      <Paragraph>Hello World</Paragraph>
    </View>
  );
}

The most reliable animation driver I have used is the react-native driver. @tamagui/animations-react-native
This is the case even for the web / nextjs platform, which I find strange. I would have thought that the css driver would have been more reliable.

I have an issue when animating height using both @tamagui/animations-react-native and @tamagui/animations-moti.
Here's the relevant source code:
tamagui.config.ts
import { createAnimations } from "@tamagui/animations-{moti/react-native}" // neither work for height
...

const animations = createAnimations({
  bouncy: {
    type: 'spring',
    damping: 10,
    mass: 0.9,
    stiffness: 100,
  },
  lazy: {
    type: 'spring',
    damping: 20,
    stiffness: 60,
  },
  quick: {
    type: 'spring',
    damping: 20,
    mass: 1.2,
    stiffness: 250,
  },

});
...
const config = createTamagui({
   animations,
   ...
});

random_component.tsx
function RandomComponent() {
const [openMenu, setOpenMenu] = useState<boolean>(false); // I trigger it on a button press
...
<AnimatePresence>
                {
                    openMenu && <YStack
                        enterStyle={{
                            height: 0,
                            // opacity: 0,     opacity and scale work
                            // scale: 0
                        }}
                        exitStyle={{
                            height: 0,           opacity and scale work
                            // opacity: 0,
                            // scale: 0
                        }}
                        zi={1} animation="quick"
                        position="absolute" right="$3" top="$6" w="$6" height={500} br="$6"
                        backgroundColor="#222"
                    >

                    </YStack>
                }
                </AnimatePresence>
                ...


[rlgl] Remove GLEW library dependency (if possible)

In order to reduce raylib external dependencies, OpenGL extensions loading library GLEW could be replaced by a lightweight alternative to load only OpenGL 3.3 Core profile required extensions.
Related functions [rlgl.c]:
void rlglInit(void);

Some alternatives have been already tested: glad and glLoadGen. Those libraries generate custom headers to be included in the project with only the required functionality.
glad seems the most interesting alternative but it's not working (neither glLoadGen), #include <windows.h> must be removed due to conflicts with raylib, but glad compiles anyway... When running any example, it crashes.

After further investigation and testing, I realized a couple of things.
Extensions initialization should be moved from rlgl.c to core.c function InitDisplay(), just below function call glfwMakeContextCurrent(window).
That way, all required GL functions will be loaded before InitGraphics().
I confirm omitting #include <windows.h> on glad.h breaks the program (despite compilation with no complaints).

Issue solved on commit https://github.com/raysan5/raylib/commit/4e57bd1f18996990546920f2242a58894c6cec81
Thanks to @Dav1dde directions, GLEW was finally replaced by GLAD (Check https://github.com/Dav1dde/glad/issues/42).
GLEW alternative has also been maintained in the code (temporaly) while checking some weird behaviours on gDEBugger profiler.


proposal: generic should infer type from variable definition

hope go could support infer generic type from variable type
func main() {
	var x Person = get() // to replace var x = get[Person]()
	fmt.Println(x)
}

func get[T any]() T {
	var x T
	return x
}

I suppose this would be a little bit like way that the language handles untyped constants, in that the type of the function would be inferred based on how the function call expression is used.  But there would be a big difference, which is that untyped constants have a default type, but here the "default type" would be a compiler error.
I'm concerned that the rules for when the type is inferred would be unclear to the person reading the program.  People already get confused about untyped constants.
In any case putting this on hold for later consideration after we have more experience with generics.

And generic parameter should can be infer lazily.
For example:
m := NewHashMap[int, int]()
m.Put(1, 2)

can write as:
m := NewHashMap() // currently type parameter is not set.
m.Put(1, 2) // type parameter set to (int, int)

@leaxoy That seems very different to me, and should be a separate issue, not this one.  Thanks.

While this is on hold, I'd like to give my two cents on this one:
I don't want type inference to get too smart, and IMO nobody should wish for this. When we'll start having big projects using generics, or complex libraries with functions having a certain number of type parameters, differing in subtle ways, interacting with each other etc... it'll become more and more difficult to read generic code, up to the point where (and that is already the case in a number of languages) it'll be necessary to know a tremendous part of the codebase to know what types you're actually dealing with, their constraints and such. So I left a thumb down, not because I think this is bad in itself, I just feel like it goes against Go's philosophy.

For the following g and f:
func f[T any]() (x T) { return }
func g[T any](x ...T) { return }

On the call side, because the current type inference is only limited based on function arguments, we can infer g from the return type of f:
g(f[int]()) // OK

But not the vise versa:
g[int](f()) // ERROR: cannot infer T

This seems OK initially since it applies the philosophy of "there is only one way of doing something". However, whenever we trying to do something with ..., it feels so much wierd (am I the only person?):
g(f[int](), f[int](), f[int](), f[int](), f[int]()) // OK
g[int](f(), f(), f(), f(), f())                     // ERROR: cannot infer T

One must write the first style rather than the second. Was there a particular example (similar to other known limitations caused by particular examples) to prevent this during the design cycle of 1.18's generics?

I'm concerned that the rules for when the type is inferred would be unclear to the person reading the program.

My experience so far with type inference is that the rule is:
"Sometimes it works and I'm happy. Sometimes it doesn't work, and I sigh and write out the type."
In any case, the specific case given in the OP is quite clear cut: the type is explicitly named as part of the declaration. Another quite clear cut case (which is the one that brought me here today) is struct literals, where the return type can be inferred from the struct field type.
I suspect that listing and handling just the "obvious" cases would provide a lot of ergonomic support, without complicating the actual rules too much.

Some simple wrapper types, such as Result[T] or Optional[T], would definitely benefit from being able to tell the type from context. For example, currently if there was an Optional[T] type, you'd have to use it something like this:
type Optional[T any] struct {
  v T
  ok bool
}

func Some[T any](v T) Optional[T] { return Optional[T]{v: v, ok: true} }
func None[T any]() Optional[T] { return Optional[T]{} }

func Example(cond bool) Optional[string] {
  if !cond {
    return None[string]() // Not the most ergonomic.
  }
  return Some(someString()) // Much nicer.
}

It would be a very nice improvement to be able to just do return None() when the type is obvious from the context like this.

How far would this go? How about this?

I don't think that's necessary, at least not right now. It could certainly be considered later, but it seems like a lot of complication for a much smaller benefit. I don't know for sure how complicated it would really be, though. It may be possible for the type checker to introduce a temporary type that it can slot in for x, then when it gets to an actual type check, like when assigning x to y, it can see that x has this special fake type and do the inference there, propagating it back to the original assignment. I'm not sure how viable that is, though.
Also, the repeat() function in your second example doesn't work. The make argument shadows the built-in make(), but you call both in the function. But that being said, that seems less complicated to me than the previous example. The usage of repeat() as an argument to Write() means that byte can be inferred for T right there, and then it just becomes byte throughout the implementation of repeat(). I could be wrong, though.

How far would this go? How about this?

I don't think that's necessary, at least not right now. It could certainly be considered later, but it seems like a lot of complication for a much smaller benefit. I don't know for sure how complicated it would really be, though. It may be possible for the type checker to introduce a temporary type that it can slot in for x, then when it gets to an actual type check, like when assigning x to y, it can see that x has this special fake type and do the inference there, propagating it back to the original assignment. I'm not sure how viable that is, though.

It's definitely viable (Rust does this kind of thing) but not necessarily desirable.

But even then, things get tricky I think:

This seems less complicated to me than the previous example. The usage of repeat() as an argument to Write() means that byte can be inferred for T right there, and then it just becomes byte throughout the implementation of repeat(). I could be wrong, though.

Yeah, I think it should work (if type inference by LHS type is to work), but specifying the rules might not be that straightforward.

As an aside, the make argument shadows the built-in make(), but you call both in the function.

Good catch. Fixed by editing.

I think a single statement is a good natural boundary. So
return None()

would work because None can use the type of the return to fill in the blank but
x := None()
return x

would fail because there's not enough information on the x := None() line.

I think what's certain here is that for an inferred type, it would have to coalesce into a concrete type before it can be used in a concrete way. You pass generically-constrained param to a function that isn't generic, it's a compile-fail. You pass it to a function that is generic, but is constrained differently than the param, it's a compile-fail.
Meanwhile, I agree with the logic on the hold. I do want this long-term, because I DO GET generics, but I also know that this is a common point of confusion.

Here's an attempt at a more concise formulation of this proposal, at least as how I understand it:
If a generic function is called and the result is used in an assignment (*) to a typed variable, the type of the variable is used for type inference if the function's result type depends on a type parameter. If a function returns multiple results, the same applies for each result.
(*) For the purpose of this proposal, initialization expressions (to fully typed variables) in variable declarations, assignments to redeclared (and thus fully typed) variables in short variable declarations, returning results to function result parameters, and passing values to functions in function calls are all considered assignments where this form of type inference will be applicable.
This form of inference can be viewed as a generalization of #59338: instead of considering the type of the function, we consider the type(s) of the function results for inference.
Some examples:
func f[P any]() P { ... }
var x int = f()  // ok, infers P = int (type of x is int)
x = f()          // ok, also infers P = int (type of x is int)
var y = f()      // not ok, y doesn't have a type yet, so P cannot be inferred

func g[P, Q any]() (P, Q) { ... }
var u, v float64 = g()  // ok, infers P = Q = float64
x, v = g()              // ok, infers P = int, Q = float64
z, v := g[string]       // ok, P = int (provided), z is int, Q = float64, inferred from v
a, b := g[int]          // not ok, b doesn't have a type yet, so Q cannot be inferred

func h[T any](x, y T) { ... }
h(g[string]())  // ok, T = string, inferred from 1st result of g, Q = string, inferred from y which has type T = string

The h example is a situation where type arguments of both g and h are inferred. This is possible in principle but may be too complicated in practice. It's also not clear what happens if g itself is called with another generic function result, and g is then used as an argument for h, etc. We will need to determine where to draw the line, to keep code and implementation complexity in line.

Removing this from hold as it is a natural extension of #59338. Also, for better understanding we have prototyped the implementation for simple forms such as the x = f() example above in the dev repo (disabled by default).
For an idea of what's possible in the prototype see $GOROOT/src/internal/types/testdata/examples/inference2.go at tip.

(*) For the purpose of this proposal, initialization expressions (to fully typed variables) in variable declarations, assignments to redeclared (and thus fully typed) variables in short variable declarations, returning results to function result parameters, and passing values to functions in function calls are all considered assignments where this form of type inference will be applicable.

One more: Sending the result to a channel.

z, v := g[string]       // ok, P = int (provided), z is int, Q = float64, inferred from v

I guess that should be z, v := g[int].

@DeedleFake For now I think we may want to constrain this to a limited set of "assignments". Once we add sending results to a channel, we (probably) also need to add setting a map element or providing a map key. Then the question is what about indexing (do we infer an int?), etc. In the cases of channels and maps we have clearly defined types and so it makes sense to include those, but let's do this in a separate round, ounce we are happy with this in the first place.

The primary issue with this proposal is that in general, type-inference is not easily localized anymore to a single ("flat") assignment/function call. Consider:
func f[P any](x P) P { return x }

var x float64 = f(f(f(0)))

The return type P of the outermost call of f is inferred from the assignment, i.e., P is float. That informs f's argument type, which in turn determines the result type and argument type of the middle f call, and then the innermost f call. The type of 0 will then be inferred to be float64.
In general, this nesting can be arbitrarily deep, with many different generic functions at various instantiation levels. While type inference should be able to infer types in cases like these, our current type checkers are not organized in a way that makes such an approach easily feasible: type checking essentially happens recursively, bottom-up. To make this more general inference work, expressions will need to be type-checked "as a whole" which likely will require significant re-engineering of the type checker.
Putting back on proposal-hold for now.

[#58650] solved the problem, should close now

Solved?

Is this issue really "solved"? My understanding was that https://github.com/golang/go/issues/58650 does not implement this; it just makes this easier to implement.
Also, a small modification of the code from the top of this issue does not compile in the playground, not even with the version set to "Go dev branch". https://go.dev/play/p/ry-w07CKoct?v=gotip

This issue is not solved. See this comment for details. Leaving on hold.

I meet the same problem.
I use this pattern to pass variable options.
type Container[T any] struct {
	name  string
	items map[*T]struct{}

	a interface{}
	b interface{}
	c interface{}
}

func (c *Container[T]) Add(item *T) { c.items[item] = struct{}{} }

// ... and so on

// I use type ContainerOption to configure the Container.
type ContainerOption[T any] func(*Container[T])

func WithName[T any](name string) ContainerOption[T] { return func(c *Container[T]) { c.name = name } }
func WithA[T any](a any) ContainerOption[T]          { return func(c *Container[T]) { c.a = a } }
func WithB[T any](b any) ContainerOption[T]          { return func(c *Container[T]) { c.b = b } }
func WithC[T any](c any) ContainerOption[T]          { return func(c *Container[T]) { c.c = c } }

func NewContainer[T any](opts ...ContainerOption[T]) bool {
	c := &Container[T]{
		items: make(map[*T]struct{}),
	}
	for _, opt := range opts {
		opt(c)
	}
	return true
}

func main() {
	// the "int" is not meaningful for this statement and it looks very strange.
	NewContainer(WithName[int]("TestContainer"), WithA[int]("bar"), WithB[int]("foo"), WithC[int]("baz"))

	// why not:
	// NewContainer[int](WithName("TestContainer"), WithA("bar"), WithB("foo"), WithC("baz"))
}


Issue 41

Address #41

To run just the iao import:
sudo ./run.sh make imports/iao_import.owl

trying to ammend remove step:
robot remove --input modules/intermediate/nutritional_components_framework_CHEBI_AP.owl --prefix "CDNO:http://purl.obolibrary.org/obo/CDNO_" --term-file templates/include/NCF_includes.txt --term-file templates/include/RO_includes.txt --term-file templates/include/PO_includes.txt --term-file templates/include/IAO_includes.txt --term-file templates/include/PATO_includes.txt --select complement --select classes --signature true annotate --ontology-iri "http://purl.obolibrary.org/obo/cdno/modules/nutritional_components_framework_full.owl" --version-iri "http://purl.obolibrary.org/obo/cdno/modules/nutritional_components_framework_full.owl" --output modules/nutritional_components_framework_full.owl

This could work but there are some steps to think about, could also just try to add a small template with the AP from IAO with the definiton asserted instead of trying to import IAO and merge it in.

This was fixed by just adding to the cdno-edit.owl.


Add "back" button functionality into Rank the Research Tutorial

This observation was pointed out by multiple PEP members upon review of the 0.7.0 beta. Either add a "back" button into the AJAX that is presenting the tutorial at present or modify the tutorial in such a way so as to not change the behavior of the web browser back button.

Other additions that have been requested (perhaps spawn separate issues):

Add progress indicator (e.g. 5 / 10 question when you're on the 5th question)
Add ability to defer vote on a question to a later time
(Maybe) Shorten the tutorial to 3-5 questions

My hesitation about making too many changes to this is that data completion seems to suggest that the current format is working in our favor. If you check from the admin dashboard, there's only one member who has started the research topic tutorial and not finished. The questions presented during this process have a much higher number of votes (currently 180 compared to 50 and below), which was the goal when we first designed this layout.
I definitely see the concern for not being able to use the 'back' button to return to previous questions, and the current progress indicator could show 5/10 as well as 50%. I can make the changes to the indicator, but I think restructuring the urls, at this point, is outside of the scope of v9, as the index and show pages took precedence

Data completion rates remain remarkably high, closing for now.


No Transmitted nor Downlink

Hello,
I set up a RAK7258 as a dataonly hotspot.  It is registered and visible on explorer.helium.com, I use a Dragino LGT92 GPS tracker (registered on console.helium.com) next to it: I only see received data and uplink, no transmited nor dowlink at all.
Can someone guide me - no more debugging idea ...
Thanks

@Kame160
Which LNS has your LGT92 registered?
Do you have logs from gateway-rs?

@Kame160 I'm going to close this due to lack of activity. If you still have issues let us know


restic serve integration test doesn't pass with b2 backend

Originally from https://github.com/restic/restic/pull/1657#issuecomment-373650708
This tests fails quite consistently
                --- FAIL: TestBackendRESTExternalServer (95.50s)
                    --- FAIL: TestBackendRESTExternalServer/TestBackend (23.50s)
                        tests.go:782: wrong number of IDs returned: want 4, got 3

Apparently the test is indicating that there is a missing key returned from the delayedList function.
Looking at that function I'm wondering if there might be some sort of eventual consistency thing going on as that function seems to collect up as many list entries as it can, rather than just returning the last list which had the desired entry in it.

@fd0 wrote:
I've managed to reproduce it while writing debug logs for restic and rclone, see here:
rclone-log.txt
restic-log.txt
Restic was started like this:
$ cd internal/backend/rest
$ RESTIC_TEST_REST_REPOSITORY=rest:http://localhost:8080/ DEBUG_FILES=*.go go test -tags debug -v -run External/TestBackend
and rclone:
rclone --verbose=2 --dump-bodies --dump-headers serve restic b2:restic-test-an/test-rest-ext/

Maybe you can see something. What I discovered so far was: restic creates and deletes the file c3ab8ff1 a few times, among others in the data/ directory. At the end it tries to list all files in data/, and did not find the file:
    tests.go:787: wrong number of IDs returned: want 4, got 3
              want:
              [c3ab8ff1 248d6a61 cc5d46bd 4e54d2c7]
              got:
            [248d6a61 4e54d2c7 cc5d46bd]

It was found before and for other file types. So, a file/key is missing, instead of one additional key.
I can see in the rclone log file that listing the subdirs of data/ returns only three dirs, 24, 4e, and cc. So the last upload did maybe not succeed? It looks like rclone told restic it did succeed...
Any idea what's going on?

I ran the tests again
rclone-test1.log
restic-test1.log
Here are the rclone transaction logs for the missing file /keys/c3ab8ff13720e8ad9047dd39466b3c8974e592c2fa383d4a3960714caef0c4f2
   2529:2018/03/22 12:00:36 DEBUG : B2 bucket rclone-test1 path restic/: HEAD /keys/c3ab8ff13720e8ad9047dd39466b3c8974e592c2fa383d4a3960714caef0c4f2
   2556:2018/03/22 12:00:38 DEBUG : keys/c3ab8ff13720e8ad9047dd39466b3c8974e592c2fa383d4a3960714caef0c4f2: Head request error: object not found

   2557:2018/03/22 12:00:38 DEBUG : B2 bucket rclone-test1 path restic/: HEAD /keys/c3ab8ff13720e8ad9047dd39466b3c8974e592c2fa383d4a3960714caef0c4f2
   2584:2018/03/22 12:00:39 DEBUG : keys/c3ab8ff13720e8ad9047dd39466b3c8974e592c2fa383d4a3960714caef0c4f2: Head request error: object not found

   2585:2018/03/22 12:00:39 DEBUG : B2 bucket rclone-test1 path restic/: GET /keys/c3ab8ff13720e8ad9047dd39466b3c8974e592c2fa383d4a3960714caef0c4f2
   2612:2018/03/22 12:00:41 DEBUG : keys/c3ab8ff13720e8ad9047dd39466b3c8974e592c2fa383d4a3960714caef0c4f2: Get request error: object not found

   2613:2018/03/22 12:00:41 DEBUG : B2 bucket rclone-test1 path restic/: HEAD /keys/c3ab8ff13720e8ad9047dd39466b3c8974e592c2fa383d4a3960714caef0c4f2
   2640:2018/03/22 12:00:42 DEBUG : keys/c3ab8ff13720e8ad9047dd39466b3c8974e592c2fa383d4a3960714caef0c4f2: Head request error: object not found

   2977:2018/03/22 12:00:59 DEBUG : B2 bucket rclone-test1 path restic/: POST /keys/c3ab8ff13720e8ad9047dd39466b3c8974e592c2fa383d4a3960714caef0c4f2
   2987:X-Bz-File-Name: restic/keys/c3ab8ff13720e8ad9047dd39466b3c8974e592c2fa383d4a3960714caef0c4f2
   3013:  "fileName": "restic/keys/c3ab8ff13720e8ad9047dd39466b3c8974e592c2fa383d4a3960714caef0c4f2",

   3017:2018/03/22 12:01:00 DEBUG : B2 bucket rclone-test1 path restic/: GET /keys/c3ab8ff13720e8ad9047dd39466b3c8974e592c2fa383d4a3960714caef0c4f2
   3050:      "fileName": "restic/keys/c3ab8ff13720e8ad9047dd39466b3c8974e592c2fa383d4a3960714caef0c4f2",
   3055:  "nextFileName": "restic/keys/c3ab8ff13720e8ad9047dd39466b3c8974e592c2fa383d4a3960714caef0c4f2 "
   3078:X-Bz-File-Name: restic/keys/c3ab8ff13720e8ad9047dd39466b3c8974e592c2fa383d4a3960714caef0c4f2

   3084:2018/03/22 12:01:01 DEBUG : B2 bucket rclone-test1 path restic/: GET /keys/c3ab8ff13720e8ad9047dd39466b3c8974e592c2fa383d4a3960714caef0c4f2
   3117:      "fileName": "restic/keys/c3ab8ff13720e8ad9047dd39466b3c8974e592c2fa383d4a3960714caef0c4f2",
   3122:  "nextFileName": "restic/keys/c3ab8ff13720e8ad9047dd39466b3c8974e592c2fa383d4a3960714caef0c4f2 "
   3146:X-Bz-File-Name: restic/keys/c3ab8ff13720e8ad9047dd39466b3c8974e592c2fa383d4a3960714caef0c4f2

   3677:2018/03/22 12:01:07 DEBUG : B2 bucket rclone-test1 path restic/: DELETE /keys/c3ab8ff13720e8ad9047dd39466b3c8974e592c2fa383d4a3960714caef0c4f2
   3710:      "fileName": "restic/keys/c3ab8ff13720e8ad9047dd39466b3c8974e592c2fa383d4a3960714caef0c4f2",
   3715:  "nextFileName": "restic/keys/c3ab8ff13720e8ad9047dd39466b3c8974e592c2fa383d4a3960714caef0c4f2 "
   3746:  "fileName": "restic/keys/c3ab8ff13720e8ad9047dd39466b3c8974e592c2fa383d4a3960714caef0c4f2",

   3751:2018/03/22 12:01:08 DEBUG : B2 bucket rclone-test1 path restic/: HEAD /keys/c3ab8ff13720e8ad9047dd39466b3c8974e592c2fa383d4a3960714caef0c4f2
   3792:2018/03/22 12:01:08 DEBUG : keys/c3ab8ff13720e8ad9047dd39466b3c8974e592c2fa383d4a3960714caef0c4f2: Head request error: object not found

   3793:2018/03/22 12:01:08 DEBUG : B2 bucket rclone-test1 path restic/: HEAD /keys/c3ab8ff13720e8ad9047dd39466b3c8974e592c2fa383d4a3960714caef0c4f2
   3834:2018/03/22 12:01:08 DEBUG : keys/c3ab8ff13720e8ad9047dd39466b3c8974e592c2fa383d4a3960714caef0c4f2: Head request error: object not found

   3835:2018/03/22 12:01:08 DEBUG : B2 bucket rclone-test1 path restic/: POST /keys/c3ab8ff13720e8ad9047dd39466b3c8974e592c2fa383d4a3960714caef0c4f2
   3845:X-Bz-File-Name: restic/keys/c3ab8ff13720e8ad9047dd39466b3c8974e592c2fa383d4a3960714caef0c4f2
   3871:  "fileName": "restic/keys/c3ab8ff13720e8ad9047dd39466b3c8974e592c2fa383d4a3960714caef0c4f2",
   This gets a 200 OK request

We then get the following list attempts none of which have the file in.

2018/03/22 12:01:09 DEBUG : B2 bucket rclone-test1 path restic/: GET /keys/
2018/03/22 12:01:09 DEBUG : B2 bucket rclone-test1 path restic/: GET /keys/
2018/03/22 12:01:10 DEBUG : keys: list request
2018/03/22 12:01:11 DEBUG : keys: list request

And listing the bucket some time afterwards we get this - the file still isn't there
$ rclone ls b2:rclone-test1/restic/
       56 keys/248d6a61d20638b8e5c026930c3e6039a33ce45964ff2167f6ecedd419db06c1
       13 keys/4e54d2c721cbdb730f01b10b62dec622962b36966ec685880effa63d71c808f2
        7 keys/cc5d46bdb4991c6eae3eb739c9c8a7a46fe9654fab79c47b4fe48383b5b25e1c

Using rclone ls -vv --dump bodies --b2-versions b2:rclone-test1/restic/keys we can see the versions of the file.
versions-dump.txt
This shows the first few versions, but the important thing to notice is that the first one is "hide" meaning the file doesn't exist as far as normal listings are concerned.
    {
      "action": "hide",
      "contentLength": 0,
      "contentSha1": null,
      "contentType": null,
      "fileId": "4_z7fd2ed1360fdeb1b6f180e1b_f113b11b34fc82730_d20180322_m120108_c001_v0001041_t0012",
      "fileInfo": {},
      "fileName": "restic/keys/c3ab8ff13720e8ad9047dd39466b3c8974e592c2fa383d4a3960714caef0c4f2",
      "size": 0,
      "uploadTimestamp":<PHONE_NUMBER>000
    },
    {
      "action": "upload",
      "contentLength": 6,
      "contentSha1": "8843d7f92416211de9ebb963ff4ce28125932878",
      "contentType": "application/octet-stream",
      "fileId": "4_z7fd2ed1360fdeb1b6f180e1b_f109c0d3cfc62b6fa_d20180322_m120108_c001_v0001103_t0000",
      "fileInfo": {
        "src_last_modified_millis": "1521720068601"
      },
      "fileName": "restic/keys/c3ab8ff13720e8ad9047dd39466b3c8974e592c2fa383d4a3960714caef0c4f2",
      "size": 6,
      "uploadTimestamp":<PHONE_NUMBER>000
    },
    {
      "action": "upload",
      "contentLength": 6,
      "contentSha1": "8843d7f92416211de9ebb963ff4ce28125932878",
      "contentType": "application/octet-stream",
      "fileId": "4_z7fd2ed1360fdeb1b6f180e1b_f109c0d3cfc62b6b7_d20180322_m120100_c001_v0001103_t0000",
      "fileInfo": {
        "src_last_modified_millis": "1521720059255"
      },
      "fileName": "restic/keys/c3ab8ff13720e8ad9047dd39466b3c8974e592c2fa383d4a3960714caef0c4f2",
      "size": 6,
      "uploadTimestamp":<PHONE_NUMBER>000
    },

So what it looks like to me is that B2 somehow swapped over the order of the hide and the upload because they came in quick succession.
I managed to verify this with the attached script
b2-test2.sh.txt
Run a serve restic in one window
rclone -vv serve restic b2:rclone-test1/restic

Then run the attached script.  Sooner or later it will produce this
...
should not exist
OK
OK
should exist
OK
OK
should not exist
OK
OK
should exist
Bad response: HTTP/1.1 404 Not Found
Accept-Ranges: bytes
Content-Type: text/plain; charset=utf-8
Server: rclone/v1.40-009-g5ba5be9b
X-Content-Type-Options: nosniff
Date: Thu, 22 Mar 2018 14:38:09 GMT
Content-Length: 10

Not Found in listing: []

And verifying that there is no file
$ rclone ls b2:rclone-test1/restic
$

So this definitely seems like a bug in b2.
--hard-delete works around the problem.
I tried replacing the upload with
    curl -X POST -d "$(date -Ins)" http://localhost:8080/test_file

To upload a constantly changing file and I could not reproduce the problem
So it seems to be a problem with uploading and deleting the same file in quick sucession.

According to my contact at Backblaze this is expected behaviour.

The sorting of the files is by time, to the second.  Ties are broken by file ID, which is basically random from the point of view of the client.   If the hiding and uploading happen in the same second, the order is arbitrary. And hiding is the same as uploading (a hide marker) ...

It is very unlikely a user will upload and hide the same file in quick succession (within a second to trigger the issue), so I don't think we need to fix this in rclone.
We could put a work-around in the restic unit tests - sleeping for 1 second in the right places would fix it.

Ah, thanks for digging into this issue! I'll change the backend tests in restic to use files with different names (that's more realistic anyway). I've added https://github.com/restic/restic/issues/1685 to track this.

Fine with me, we'll track this over at restic.


Update reducer_decks.js

added again charCodeAt(),  lastIndexOf(), localeCompare(),replace(),search(),slice(),split(), substring(), toLocaleLowerCase(),toLocaleUpperCase()` built-in methods. I edited the file in github. just comment if the problem earlier still persists! ~~

@tomy8910 looks great. Thanks!


Build wasm32 via Nix

Codecov Report
Base: 72.46% // Head: 71.69% // Decreases project coverage by -0.77% :warning:

Coverage data is based on head (e071343) compared to base (a5e39eb).
 Consider uploading reports for the commit a0ac418 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #624      +/-   ##
==========================================
- Coverage   72.46%   71.69%   -0.78%
==========================================
  Files          85       85
  Lines       11553    11678     +125
==========================================
  Hits         8372     8372
- Misses       3181     3306     +125

Impacted Files
Coverage Δ

client/cli/src/bin/mint-rpc-client.rs
3.44% <0.00%> (-4.25%)
:arrow_down:

fedimint/src/lib.rs
82.37% <0.00%> (-0.34%)
:arrow_down:

client/cli/src/main.rs
0.23% <0.00%> (-0.08%)
:arrow_down:

fedimint/src/net/peers.rs
92.96% <0.00%> (+0.26%)
:arrow_up:

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

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


Use tpm2-software TSS implementation, and xaptum-tpm's nvram utils

This PR builds this project against the tpm2-software implementation of the TPM TSS2 (rather than the xaptum-tpm implementation). As part of this, this also removes the implementation of TPM NVRAM utilities from this library and uses the (essentially identical) ones from xaptum-tpm (and also the definitions of certain constant handle values, which were also duplicated between here and xaptum-tpm).
This includes:

Building a local installation of the tpm2-software TSS in Travis-CI builds
Building the xtt project against this new TSS

In addition to the CMake changes, this requires a few changes to type names in xtt (e.g. TPM_HANDLE -> TPM2_HANDLE)
The new cmake/ scripts are copies from the same ones used in xaptum-tpm and ecdaa, for finding the TSS2 libraries

Building xtt against v1.0.0 of ecdaa

Because this new ecdaa also builds against the tpm2-software TSS

Removing the tpm/[nvram,handles] files
Updating some names of nvram-related things for the xaptum-tpm version (e.g. XTT_ prefix becomes XTPM_ prefix)

NOTE: This currently hardcodes the xaptum-tpm version installed in Travis to a temporary branch that incorporates multiple feature branches (that are currently under review). Once those xaptum-tpm PRs are merged, and before this PR is, I'll change that to build a master branch xaptum-tpm.

Now that the xaptum-tpm changes have been merged, and a new release cut, I've updated this branch to use the new xaptum-tpm release


General fixes

Fix for some duplicated code, debug print, inputs and defaults. This will reorder node inputs so apologies this may break older workflows.

reverted changes to the optional/required inputs so nothing breaks.


Fix revelation of wrong pre-images after re-enrollment

There was a critical bug when EnrollmentManager reveals pre-images in the case when a validator re-enrolls before the validator cycle ends. In the previous code, we reset pre-images while creating new Enrollment, which means that the pre-images of the current cycle have been replaced with a new set of pre-images. So I make the populate function only generate the initial random seed for enrollment. After being a validator for the new cycle, the populate generates the whole pre-images for the new cycle.
Relates #1079

I'm not entirely sure I understand what the reported issue was about. Maybe @Geod24 can help reviewing this.

@linked0 explained the problem to me yesterday. The issue is that, now that we accept Enrollment when an Enrollment is still active, we end up resetting the pre-image too early. See this code:
https://github.com/bpfkorea/agora/blob/952cd01b14778d5ca5e34c049c8217c59037614f/source/agora/consensus/EnrollmentManager.d#L268-L293
As soon as addValidator is performed, we consume the pre-image. If we try to access it later on, we'll get its pre-image.
However, this doesn't seem like the right solution. The way the cache works is fine, we should just not consume that early.

However, this doesn't seem like the right solution. The way the cache works is fine, we should just not consume that early.
Also, this is lacking a test.

@Geod24 I will research the right solution, but If you have one in your mind already, could you share it with me? And I will add a unit test for that.

auto next_images = PreImageCache(this.preimages.data.length,
this.preimages.interval);
next_images.reset(this.seeds.byStride[$ - 1 - this.index]);
return next_images[$ - 1];

@Geod24 and I discussed what it should be. Unfortunately, we should calculate the first pre-image from the next cycle's seed because the pre-image is a pre-image of the seed of the current cycle.
I added a unit test for not consuming pre-images before being a validator.


Added support for ppc64le

Built and tested on a testsystem with ppc64le arch. Works great - keep up the great work!

awesome; thanks @neikei !


add an API to change log level for a module or globally

zap supports swapping log level during runtime, in many cases DEBUG log will make it obvious what is the problem but it will also spam as hell even if there is no problem.
it is beneficial to have such API, as debugging by looking at metrics is less accessible for people

[ ] implement endpoint on DebugService.ChangeLogLevel(module string, level string) error
make sure that explicit "*" changes default log level, otherwise change only requested log level. error if requested module is not registered, or level is unknown
[ ] pass loggers initialized in node/node.go to DebugService

@kacpersaw could you please use closes:  if there is a relevant issue


method io.netty.util.concurrent.DefaultPromise#cancel/isDone violates contract?

Expected behavior
According the contract from method java.util.concurrent.Future#cancel :

After this method returns, subsequent calls to isDone will always return true.

the console should print true
Actual behavior
console print false
Steps to reproduce
please use following reproducer code
Minimal yet complete reproducer code (or URL to code)
import io.netty.util.concurrent.GlobalEventExecutor;
import io.netty.util.concurrent.Promise;

public class DefaultPromiseIsDoneTest {

    private final Promise<?> defaultPromise = GlobalEventExecutor.INSTANCE.newPromise();

    public static void main(String args[]) {
        DefaultPromiseIsDoneTest main = new DefaultPromiseIsDoneTest();
        main.isDoneTest();
    }

    private void isDoneTest() {
        defaultPromise.setUncancellable();
        defaultPromise.cancel(false);
        boolean isDone = defaultPromise.isDone();
        System.out.println(isDone);
    }
}

Netty version
4.1.21
JVM version (e.g. java -version)
1.8
OS version (e.g. uname -a)
MacOS
Does  Netty change the contract inherited from java.util.concurrent.Future#cancel?
There is a discussion about this in stackoverflow:
https://stackoverflow.com/questions/30140463/future-cancel-method-documentation

friendly pinging...
@normanmaurer @trustin @Scottmitch

@laosijikaichele yes I think you are right but there is not much we can do without breaking users until we do a new major release.  Let me add it to the todo list.

https://github.com/netty/netty/issues/5430#issuecomment-365854227


Add python 3.9 suport for Watchdog.isAlive()

Fixes #12109
Status
in development
Description
Define Watchdog.isAlive() so it supports python 3.7 and 3.9
Is it backward compatible (if not, which system it affects?)
<YES | NO | MAYBE>
Related issue:
https://github.com/dmwm/WMCore/issues/11978

For more context, the following unit test fails with:
https://cmssdt.cern.ch/dmwm-jenkins/view/WMCore Docker/job/WMCore-Unittest-Baseline-khurtado2/37/testReport/junit/Runtime_t/RuntimeTest/testB_EmulatorTest/
  File "/usr/lib64/python3.9/unittest/case.py", line 59, in testPartExecutor
    yield
  File "/usr/lib64/python3.9/unittest/case.py", line 592, in run
    self._callTestMethod(testMethod)
  File "/usr/lib64/python3.9/unittest/case.py", line 550, in _callTestMethod
    method()
  File "/home/cmsbld/WMCore/test/python/WMCore_t/Misc_t/Runtime_t.py", line 412, in testB_EmulatorTest
    self.runJobs(workload=workload)
  File "/home/cmsbld/WMCore/test/python/WMCore_t/Misc_t/Runtime_t.py", line 317, in runJobs
    miniStartup(thisDir=taskDir)
  File "/home/cmsbld/WMCore/test/python/WMCore_t/Misc_t/Runtime_t.py", line 76, in miniStartup
    if monitor.isAlive():
'Watchdog' object has no attribute 'isAlive'

This PR should fix this issue


add new feture like page slider beneath book, also keyboard arrow forward and backword buton should work

@Gul7333  What you mean by "slider"? You mean like a bullets ●○●●● list?

I mean slider like user. can slider the slider for fast page scroll
By input slider type range in html
And also keyboard arror forward button and backword button should work....
Further if we can use pdf directly it will be awesome

@Gul7333 I have no plans in supporting PDF-to-HTML, since beyond the scope and complexity of this demo (but I'll research).
I'm still unsure what do you mean by "slider user fast slide"
Regarding bullets and prev/next buttons, isn't that also outside of scope? Since that can be achieved easily with just a bit of JavaScriptand by using
Element.style.setProperty("--c", desiredIndex)

I mean there should be input range below the book, which user can slide ,

And also I don't know how can I make page flip on clicking keyboard forward and backward arrow buttons

Range slider is not a common UI for sliders, galleries, carousels. Also rande slider should never be used for accurate values. Read https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/range - specifically the second paragraph.
On how to animate to a desired index it's described in the readme.md file
elBook.style.setProperty("--c", index);

And here is a demo with keyboard arrow navigation: https://jsfiddle.net/419oqe56/


An error occurred while trying to restore packages: The specific file path, file name or both are too long.

@Chowdhury3320 - this is the docs repo and primarily used to track docs related feedback and bugs. For product-related feedback - file an issue in our Home repo


Formatter align defpackage exports and uses

In a defpackage form, the :use and :export clauses should align the children.
This,
(defpackage :pkg
  (:export :a
           :b
  )

Instead of
(defpackage :pkg
  (:export :a
       :b
  )

Fixed, but maybe not correctly. Always aligns :use and :exports forms now, which may not be correct.


Add Agola Manager cli commands

Currently the /import, /export and /maintenance api are implemented by Runservice and Configstore.
I would like add cli commands to call this apis
I think the best way is to add a new agolamanager package because we don't need some agola flags, for example --gateway-url and --token

@alessandro-sorint These are temporary api that should be removed and implemented in a better way. It'll depend on the work I'm doing on removing the datamanager and etcd. So hold on.

I think the best way is to add a new agolamanager package because we don't need some agola flags, for example --gateway-url and --token

It'll be better to use the same command and don't make these options global.

@alessandro-sorint These are temporary api that should be removed and implemented in a better way. It'll depend on the work I'm doing on removing the datamanager and etcd. So hold on.

Thanks @sgotti I wait you finish to remove the datamanager


WIP: expose PF-based resources

Noticing weird SetAutoNaming interaction with @iwahbe - new resources based on PF do not yet support auto naming a runtime until pulumi/pulumi-terraform-bridge#917 is done but as written the schema-time SetAutonaming call works and makes their required "name" properties optional. The warning is elided due to incorrect check.
Could move resource definitions around so that SetAutoNaming does not apply to them.
Wondering if this is a blocker for releasing an update, can we release with a required "name" property and then relax to optional for the new resources?

Getting closer to passing checks, now need to regenerate the SDKs.

@t0yv0 With regards to https://github.com/pulumi/pulumi-aws/actions/runs/4745234484/jobs/8428050038?pr=2464. We have seen some weirdness with this resource before: https://github.com/pulumi/pulumi-aws/pull/2461#discussion_r1169296239
CC @kpitzen

Oof. SO this is non-deterministic?

I also have a Diff on schema.json for sdk/java/src/main/java/com/pulumi/aws/cognito/IdentityPoolRoleAttachment.java - that must be why, checking up on this.

Interesting. We finally get to a place where it's running acceptance tests. Seeing a lot of this:
Diagnostics:
[411](https://github.com/pulumi/pulumi-aws/actions/runs/4747040603/jobs/8450477430#step:23:417)
    aws:elasticloadbalancingv2:LoadBalancer (test):
[412](https://github.com/pulumi/pulumi-aws/actions/runs/4747040603/jobs/8450477430#step:23:418)
      error: Resource type 'aws:elasticloadbalancingv2/loadBalancer:LoadBalancer' not found.
[413](https://github.com/pulumi/pulumi-aws/actions/runs/4747040603/jobs/8450477430#step:23:419)

[414](https://github.com/pulumi/pulumi-aws/actions/runs/4747040603/jobs/8450477430#step:23:420)
    pulumi:pulumi:Stack (alb-legacy-py-p-it-fv-az254-2-alb-new-py-d1204a7c):
[415](https://github.com/pulumi/pulumi-aws/actions/runs/4747040603/jobs/8450477430#step:23:421)
      warning: LoadBalancer is deprecated: aws.elasticloadbalancingv2.LoadBalancer has been deprecated in favor of aws.lb.LoadBalancer
[416](https://github.com/pulumi/pulumi-aws/actions/runs/4747040603/jobs/8450477430#step:23:422)

Is this PR still relevant?

Is this PR still relevant?

I believe it was rendered unnecessary by https://github.com/pulumi/pulumi-aws/pull/2557.


Feature: display color on the overview page to indicate whether the instance is live/dead (when reconnecting - connecting)

Now displaying coloured RSS indicator based on state of the connection, and tag to indicate how was the device configured, IP, VRM, or UPNP.


Bug with rating

Great lib! Thanks!
But there is small bug. When you set rounded number as rating (in example 3.0 ) then BaseRatingBar shows three filled stars without others empty stars.
Simple workaround is to set rating with float numbers 2.99 in example

Hello @Sirelon ,
Thank you so much!!! Your workaround totally resolve this bug!
Do you know why this bug happened? I have no idea to resolve this problem in a good way several weeks.

Hi @ome450901
Nope. I shortly take a look in the code, but cannot find any strange behaviour.
And for now I noticed one new bug, which cannot be fixed with such workaround.
The bug occurs when RatingBar inside ScrollView. When I choose rating, then I tap to edit text (which on scrollview too) then opens keyboard, and scrollview simply scroll down to the edit text. And after this action RatingBar shows only selected stars..
I think it is related bug with first one.. In a free time I will take a look and maybe could fix it.

I think it bug on PartilalView.setPartialFilled(float rating)
I will debug it later.

Hello @Sirelon ,
I was found that @senlsy has already provided a solution in issue #15 , and it solve this bug too.
I will check the code to find out why this bug happened, maybe you can take a look with that comment too!
Thanks again for helping me debugging this issue!


Incorrect subdomain in config results in panic

To repro:

Configure the subdomain as, e.g., turbothelp.zendesk.com (instead of just turbothelp as it should be)

select * from zendesk user

rror: rpc error: code = Internal desc = hydrate function listUser failed with panic runtime error: invalid memory address or nil pointer dereference (SQLSTATE HV000)
This was the motivation for https://github.com/turbot/steampipe-plugin-zendesk/pull/25/files

@judell Thanks for checking this out. We will look into it.

@judell I guess the informational fix you have added is good enough to address the issue of confusion, whether to provide turbothelp.zendesk.com vs turbothelp. Zendesk API itself takes the subdomain name not the fully qualified subdomain name. We can discuss with @cbruno10 whether we should handle this in the code or we just continue as it is.


ARROW-15625: [C++] Convert underscore to hyphen in example executable names

@github-actions crossbow submit -g nightly

I didn't see related failure in nightly jobs. Though I expect example-cpp-minimal-build-static should pass.


[GR Phase 3] Step 3 - navigation, default data, logic and API call to save it

Design doc section: https://docs.google.com/document/d/1Y4P7G9h0Easjcea7wyk52gKrNB9o1yTjpmJFYkrHDW4/edit?tab=t.0#bookmark=id.o63v6yk67yf5

Implementation is on going. Waiting on more details regarding one of the fields and implementation of the API.
Apart from that, step 2 logic (https://github.com/Expensify/App/issues/50898) has to be implemented so we can fully test this issue

I will be OOO from 21.12 - 06.01. Latest update for this issue:

new picklist has been added
testing recordings have been added
It is still waiting on https://github.com/Expensify/App/pull/52812 to get merged, however it is rebased with latest changes and was kept up to date
BE update is still needed - Data send in Step 2 has to be saved somewhere in onyx. At the moment it's not and we cannot access the bankAccountID returned from Step 2. It should be saved inside reimbursementAccount together with all the data saved in Steps 1 & 2. I believe only minor changes will be needed - reading default values when user goes back to this step

https://github.com/Expensify/App/pull/52812 is now merge. We can continue with your draft PR when you're back @MrMuzyk


Current Internet protocol is disabled, for some reason

According to RFC 8200, published by IETF in July 2017, Internet Protocol version 6 (IPv6, in short) is the current standard for establising connectivity between hosts on the Internet. For some reason, this project disables this protocol and that leads to a number of different issues that negatively impacts every user's experience by requiring unnecessary processing power thus increasing latency times and overall responsiveness of a critical service on a network which is DNS.
This is a very simplified explanation of the whole issue but it's self explanatory. IPv6 is not a feature, its absense is a bug and needs to be addressed ASAP.

I know what IPv6 is and what it does.
The first thing you need to learn is to say thank you for quality free projects.


Update requirements

https://pulpito-ng.ceph.com/runs/zack-2023-12-27_19:01:15-orch:cephadm:smoke-main-distro-default-smithi
https://pulpito-ng.ceph.com/runs/zack-2023-12-27_19:30:58-smoke-main-distro-default-smithi

This has changed a lot recently, and there's tons of noise from my force-pushes. I'm going to close this and reopen a new PR for this branch.


Session:get_bind() does no longer support joining an external session

I'm trying to implement the pattern described in Joining a Session into an External Transaction (such as for test suites) with Flask-SQLAlchemy 3.0 and Pytest. This used to work in Flask-SQLAlchemy 2.x and is documented here.

E       [parameters: ('john',)]
E       (Background on this error at: https://sqlalche.me/e/14/gkpj)

../../.pyenv/versions/3.11.1/envs/example/lib/python3.11/site-packages/sqlalchemy/engine/default.py:736: IntegrityError
=========================================================================================================== short test summary info ===========================================================================================================
FAILED tests.py::test_two - sqlalchemy.exc.IntegrityError: (sqlite3.IntegrityError) UNIQUE constraint failed: user.username
========================================================================================================= 1 failed, 1
passed in 0.60s ===

It seems that the engine is used instead of the provided connection, thus breaking the isolation. However, SQLAlchemy's implementation in Session:get_bind() seems to handle this case:
        elif not self.__binds and self.bind:
            # simplest and most common case, we have a bind and no
            # per-mapper/table binds, we're done
            return self.bind

The sample code works with the (hackish) MySession class that loosely follows the implementation of SQLAlchemy. Enable it via the commented line: factory = sessionmaker(class_=MySession, db=db, bind=connection) to see the difference.
Environment:

Python version: 3.11.1
Flask-SQLAlchemy version: 3.0.3
SQLAlchemy version: 2.0.2 or 1.4.46

However, SQLAlchemy's implementation in Session:get_bind() seems to handle this case

We don't handle binds in the same way, so we can't add that same logic. We support looking up binds by the bind key on the model/table/metadata handling the query. If nothing else, your example only supports overriding one connection, not multiple binds.

The sample code works with the (hackish) MySession class

That's fine, if you have a way to make the tests work the way you need, use that. Using SQLAlchemy's plain Session is fine as well, you can even populate its binds argument with the appropriate connection for each model.
In general, if you want the behavior of the regular Session, use that. You're not required to use Flask-SQLAlchemy's Session class if you don't want it's behavior.

That said, there's probably some way to override db.engines to use your own mapping of connections. This probably isn't working, but the idea would be:
@pytest.fixture
def db(app, monkeypatch):
    with app.app_context():
        engines = db_.engines

    cleanup = []

    for key, engine in engines.items():
        c = engine.connect()
        t = c.begin()
        monkeypatch.setattr(engines, key, c)
        cleanup.append((c, t))

    yield db_

    for c, t in cleanup:
        t.rollback()
        c.close()

Tangential to the issue you're asking about, the following code is wrong and will cause your tests to break in other ways:
@pytest.fixture(scope="session")
def db(app):
    with app.app_context():
        db_.create_all()
        yield db_
        db_.drop_all()

You should not push an app context for the entire duration of an individual test or the entire test session. Instead, push it only during the moments you need it.
    with app.app_context():
        db.create_all()

    yield db

    with app.app_context():
        db.drop_all()

Thanks a lot for the hint regarding yield db with regards to the app context and the implementation suggestions. I'll take a look at you suggested implementation using db.engines.


Changed BaseSimulation:start to log grid to verbose instead of info

Per #19, changes grid to log to log.v instead of log.info.

Thanks for this, we decided to just delete the line, would you mind doing that here?
Just working on our pipeline for accepting pull requests so there may be some surprising delay in accepting this one-liner :-)

Closes #19


Can't undo TileMap bucket tool

Godot version
8932b55
System information
W10
Issue description
This is probably known issue, but the new tile editor doesn't support undo for bucket tool. I looked into it and it's not like it's unimplemented. It's just bugged. You can undo bucket erase and bucket replace. But if you fill empty area with tiles, then you can't undo. I looked into the code and noticed these lines:
https://github.com/godotengine/godot/blob/8932b55011126b06315ed544a0bc1f715ec37dd8/editor/plugins/tiles/tile_map_editor.cpp#L1216-L1219
When you compare them with the lines above:
https://github.com/godotengine/godot/blob/8932b55011126b06315ed544a0bc1f715ec37dd8/editor/plugins/tiles/tile_map_editor.cpp#L1205-L1206
The undo and redo seem to be swapped, but they do work correctly. Also there's this commit_action(false) that basically means the fill isn't executed here. I know where the changes are done, but I have no idea what is wrong and why would it break only in case of filling empty space ;_;
This bug is rather frustrating, so it would be nice to have it addressed soon >_>
Steps to reproduce

Add TileMap
Fill some empty area
Try undo :(

Minimal reproduction project
No response

These two lines should be removed for the bucket tool:
if (!erase_button->is_pressed() && E->get().source_id == TileSet::INVALID_SOURCE) {
   continue;
}

Depending on whether the release executes the action or not, the drag_modified map contains either the previous or the new cells. In the bucket case, it contains the previous cells, while for the rect tool, it contains the new cell. This explains the difference between the two.
If you want it quick, feel free to open a PR for the fix. Otherwise I'll include it in my next PR to implement TileMap layers.


Updates download md5, zip patched for v1.1.9 API

We had a small update to our C++/Java API, all rolled into the zip but requires an update to the checksum

Thanks!


node.js manifests/params.pp & manifests/init.pp should support Scientific Linux

I am using Scientific Linux 6.4, which is a derivative of Red Hat Enterprise Linux and is similar to CentOS. SL is used extensively at research labs and higher-education institutions.
I was attempting to install Puppet Labs Razor onto a Scientific Linux 6.4 box, and the install failed with the following error. I posted the error to the puppet-razor mailing-list, and they recommended that I file a bug here [1].
root@sl6:~ # puppet apply /etc/puppet/modules/razor/tests/init.pp
Class nodejs does not support Scientific at /etc/puppet/modules/nodejs/manifests/params.pp:55 on node sl6.example.gov

It appears that node.js does not support Scientific Linux:
root@sl6:~ # puppet apply /etc/puppet/modules/nodejs/tests/init.pp
Class nodejs does not support Scientific at /etc/puppet/modules/nodejs/manifests/params.pp:55 on node sl6.example.gov

Please update nodejs to support Scientific Linux.
[1] https://groups.google.com/forum/#!topic/puppet-razor/bJIz1Fs7r7k

Scientific Linux should work, but I haven't tested and can only base this opinion on unscientific evidence.


Ensure OSB input validation is applied to avoid code injection security vulnerabilities

Expected behavior
As an osb-cmdb operator

in order to ensure the underlying cmdb is secured
I need to be sure that malicious OSB data input can not be injected into the cmdb (e.g. shadowing an existing space, escape define quotas, ...)

Observed behavior
Currently, insecure input data (OSB service instance id) can potentially be injected as space name, service instance name
https://github.com/orange-cloudfoundry/osb-cmdb-spike/blob/08390cef44622db08e11adc95ae8d4b2110bc6a2/spring-cloud-app-broker-core/src/main/java/org/springframework/cloud/appbroker/extensions/targets/SpacePerServiceDefinition.java#L38-L41
https://github.com/orange-cloudfoundry/osb-cmdb-spike/blob/08390cef44622db08e11adc95ae8d4b2110bc6a2/spring-cloud-app-broker-core/src/main/java/org/springframework/cloud/appbroker/extensions/targets/ServiceInstanceGuidSuffix.java#L32-L37
and in SCAB as app hostnames
https://github.com/orange-cloudfoundry/osb-cmdb-spike/blob/08390cef44622db08e11adc95ae8d4b2110bc6a2/spring-cloud-app-broker-core/src/main/java/org/springframework/cloud/appbroker/extensions/targets/SpacePerServiceInstance.java#L34-L36
Affected release
Reproduced on version 0.4.0

Fixed in 1.0.0:

space name come from service definition name loaded from catalog
service instance ids

are truncated to max CF service instance size (not sure this is useful though since CAPI would reject it anyway)
are not injected in scab host names, since there are no more scab apps

Additionally, forged service instance guid, service binding guids are detected and rejected.
See related acceptance tests
https://github.com/orange-cloudfoundry/osb-cmdb-spike/blob/67f7cdd3cd1e707ede5c7f31d015053a4f86a268/spring-cloud-app-broker-acceptance-tests/src/test/java/org/springframework/cloud/appbroker/acceptance/CreateDeleteInstanceWithBackingServiceKeysAcceptanceTest.java#L176-L187
See impl notes https://github.com/orange-cloudfoundry/osb-cmdb-spike/blob/v1.0.0/osb-cmdb/docs/impl-notes/v10-redesign.md
See sample code for DSI
https://github.com/orange-cloudfoundry/osb-cmdb-spike/blob/67f7cdd3cd1e707ede5c7f31d015053a4f86a268/osb-cmdb/src/main/java/com/orange/oss/osbcmdb/serviceinstance/OsbCmdbServiceInstance.java#L179-L190