RFC: Stop reporting duration and effort

Problem:
OSSU contributors spend time transcribing easily found information.
Duration:
Aug 30, 2020
Background:
On every course, OSSU contributors write the duration (number of weeks) and effort (number of hours per week) expected by the course.
For the vast majority of courses, this information is simply being transcribed from the front of the course page. In these cases, the information is duplicative and a waste.
In other cases, the duration/effort have not been estimated by the course platform/instructor. In these cases, such an estimate does add information. But it often takes a significant amount of time for OSSU contributors to settle on an estimate. This should only be undertaken if it provides value to students.
Does the inclusion of duration/effort aid students? It may not. The expectation is that students will proceed in linear fashion from first course to last. In this paradigm, what is the value of calculating an individual course’s duration?
Proposal:

Remove Duration and Effort from all courses.

Alternatives:

Estimate duration and effort only for courses such as Missing Semester and Introduction to Computer Networking which do not offer estimates.
Keep the curriculum as it is.

The timing and effort estimates are valuable if you want to achieve a goal in a set time. In my case, what will I achieve before applying for a master's cs course. Additionally it can provide a reference if you're in track or not.

I think that this information need not be repeated.
If we absolutely need to keep it, the estimated effort could report lower and upper bounds like +/-30% (or add a caveat saying that these are very rough estimates).

I think it's good to keep the information so that you can get an idea of when you should be completing each course. Discipline is key to finishing this curriculum and having deadlines help. However, a disclaimer could come in handy to fix the issue.

You can view it in two ways..... For example, reporting effort such as 16 weeks etc may lead to a sense of "a mountain to climb" and the student losing the will to start the course before they even look at it.
On the other hand, it may also instil a sense of motivation and a better sense of planning to complete a certain course in a time-bound manner.  There is no universal answer since each student is different.
Ultimately, why are we repeating the information about effort and timelines? We don't repeat equally important information such as name of university, name of MOOC provider, name of instructor, next available session etc.
In one sense, it can be argued that while all the other facts I mentioned are constant, effort required is subjective. This is not a rigorous university curriculum with semester add-drop dates, exams, graduation dates and other strict timelines, but quite a few people are doing this syllabus while holding day jobs, children, elderly caring duties etc.
Why repeat information that is already available in the course's link? After all, doesn't it violate a core CS principle viz. Don't Repeat Yourself (DRY?)

Summaries highlight important information at a glance to be able to make quick decisions instead of needing to click every single link. Any report you read will include the highlights at the beginning aka abstract.
There are also cases like in CS50 where you are told not to complete the entire course and therefore the amount of time to complete is not accurate.
I am open to the proposal of surveys to create more accurate time to completion.

I feel that the maintenance overhead of reporting estimated hours may not always be worth the effort.
Additionally, this information can become outdated. For example, I have taken at least two courses in coursera, where new content have been added over the years and thus the course expanded by another 3 weeks.
Ultimately, there is no right answer and it is all subjective.  If you could argue that "estimated effort" is important, then so is the relative standing of the university or the reputation of the professor. Then the name of the university and professor could also be included in the curriculum? Ultimately, there is no right answer here.

I would remove the information.

It's duplicated information.

It's one more piece of information that would have to be maintained to keep it up to date.

If it's anyone's responsibility to track this information, its the original providers of the course material.

Comments are split between those advocating keeping the information and those advocating not maintaining it. This is valuable feedback. No change will happen immediately, but it is clear that contributors are aware that this information is a carrying cost. There may come a revision in the future that moves this information to a separate page, or which deletes the information altogether.

From my personal experience I found the Duration and effort information not very comparable between different courses. Sometimes I found it very much underestimated like with Mathematics for CS.
In general I think it would be a valuable information if it came directly form the same students following the OSSU Curriculum. But at the moment the new link to the chat channel on Discord could be a good substitute, because every student could ask (or find?) such kind of information there.
In the future could be nice to think to a kind of automatic survey that every student could fill at the completion of every course with a link available to everyone with the results. It could be an opportunity to provide and gather much more reliable, comparable and accessible information about each course....

Redundancy: Effort and Duration both have time units to provide the same objective of giving an idea of how long will the student work on the course. (Whats next, a column for minutes and then another for seconds? hahah)
Space: The amount of page real state that 2 columns of the same information can be reduced to achieve a similar objective, and the extra space can be used for optional support courses and material or stuff that achieves more impact on students.
Convenience: Even though its convenient to see the information right away, I believe that if they are taking the time to actually study the curriculum they are not lazy to click and see the duration provided on the course website, that will actually provide a better comprehension than two cells.

I suggest this in my draft of comment-660886018

Intro CS
Knowledge Areas: SDF - Software Development Fundamentals
If you've never written a for-loop, start here. Students who have been introduced to programming should take this course for a flavor of the material to come. If you finish the course wanting more, Computer Science is likely for you!

KA
Course
Hours
Optional Support
Prerequisites

SDF
Python for Everbody
58
Fundamentals
none

SDF
Intro to CS and Programming
135

algebra

Core CS
Core Theory
Knowledge Areas: SP - Social Issues and Professional Practice DS - Discrete Structures SDF - Software Development Fundamentals PL - Programming Languages AL - Algorithms and Complexity CN - Computational Science
CS curriculums use calculus not as a means for domain knowledge, but more as a method for helping develop mathematical maturity and clarity of mathematical thinking to have the basis on which to then build CS-specific mathematics.

KA
Course
Hrs
Optional Support
Prerequisites

SP
Learning How to Learn
15
Mindshift
none

DS
Calculus 1A 1B 1C
256
Khan, Brilliant
high school math

DS
Probability
288
Khan, Brilliant
high school math

DS
Mathematics for CS
65
Discrete, Logic, Effective, Thinking, Sets
Calculus 1A 1B 1C

SDF
How to Code Part 1 Part 2
117
Book, Basics, khan
none

SDF
Intro to CS - CS50
132
I, II, III, IV
none

SDF
CS Missing Semester
24
IT Support
-

PL
PL Part A Part B Part C
66
Java, Book 1, Book 2
SDF , Instructor's

AL
Algorithms
96
Khan, UCSD, Algo, freecodecamp, geeksforgeeks, Princeton 1 2, MIT 1 2
SDF PL DS

CN
Theory of Computation, Videos
80
Princeton, Intro Book
DS AL

Comments are split between those advocating keeping the information and those advocating not maintaining it. This is valuable feedback. No change will happen immediately, but it is clear that contributors are aware that this information is a carrying cost. There may come a revision in the future that moves this information to a separate page, or which deletes the information altogether.

@waciumawanjohi I am trying to understand the "human factors" involved here from a project management viewpoint.
This issue is closed. Out of sight & out of mind. That's what a closed issue means.
There is quite a bit of cognitive load to recall closed issues from 27 months ago whenever a relevant change to the curriculum happens.
Are the contributors going to dig through all closed issues before making changes to the curriculum? Not just this issue, but maybe there were 7 other issues that were kept for future consideration, since they had a balanced for/against feedback. I think that this is not a scalable approach.

@waciumawanjohi Can you please respond to the ways of working of this repo with regard to my previous unresolved comment? How can contributers remember which closed issue to refer to when updating the curriculum?

Hey @krishnakumarg1984
You wrote

I think that this is not a scalable approach.

I actually agree. Practices that can work for us now aren't the same ones that would work if we had far more contributors. While I think that's a potential problem that we should keep in mind, I can't think of an instance when it has hindered work.


Converting ed25519 does not throw in browser

Consider the following snippet:
var sodium = require('chloride')

// crypto_sign_SEEDBYTES is missing too

var seed = Buffer.alloc(sodium.crypto_sign_SEEDBYTES || 32).fill('bug')

var keypair = sodium.crypto_sign_seed_keypair(seed)

var box_pk = sodium.crypto_sign_ed25519_pk_to_curve25519(keypair.secretKey)

console.log(box_pk)

In node the above throws an error due to the input being too long (here the secretKey is mistakenly used) but in the browser it happily continues. I'm not sure where to report this? Should I ensure the input myself instead?

Oh yeah, here are the commands I used to test, just for reference
Node:
node bug.js

Browser:
browserify bug.js | browser-run

okay, what we should do, is extend https://github.com/dominictarr/chloride-test to also test for throws with invalid inputs. then make sure that everything does.

Do you want me to look into that? There are some other compatibility issues between the browser versions and node-sodium that I'm unsure about. Is there a better place to ask questions than here?

well, you'll get me either way, but that is where we should lock down the behavior. if they are not exactly the same then that is a bug!

Hehe, I was thinking another venue than Github. IRC? I'm active on #stackvm and #scuttlebutt

ah, well I don't really keep regular hours so async (github, ssb) works best for me


The Robbery Of The Kadakian Idol: English Translation

Now, that my rough english translation is merged, some native speaker might take the task and correct my mistakes:
https://github.com/NPBruce/valkyrie-questdata/blob/master/source/MoM/TheRobberyOfTheKadakianIdol/Localization.English.txt
@prilogon

I made some corrections and replaced some words. I think the text is a little bit more clear now.

Nice work, thank you. I will close this for now.


Render HTML responses

There's no real feedback if a server responds with something other than a 200 with correct query data.
It would be awesome if GraphiQL could either render the server response directly (using an iframe with HTML5 srcdoc), or provide a hook to do so manually.

Could you give me more info about the use-case? What is the case when a GraphQL endpoint return HTML?

Ah, right, sorry. I'm specifically thinking for development. Seems also possible that proxy/network (think Cloudflare) errors might cause an occasional non-JSON response.
At the very least, some indication that it tried to run the query and something failed might be nice.

I guess GraphQL could print somewhere (in footer bar) the status of the last call to the fetcher. If fetcher returns a failure (or the result is not a json) we could print an error message somewhere

I have a use-case for this but perhaps it is too specific to express-graphql and graphiql. Consider you've got a server that requires a login before getting to the Graphiql UI.  To accomplish this you've got an array of middleware passed to a custom express route. Your auth middleware comes first and performs an auth session check. Graphql-express is the second middleware in the array. Let's assume for these purposes that this is because you only want Graphiql to be available to staff or a developer group. If the currently logged in user has a session timeout occur while they are using Graphiql then chances are you're either going to return a login form (html) or something like a 403 Forbidden / Access Denied. Currently if you return html then Graphiql actually chokes on parsing, but if instead you return a 403 then it does nothing and errors to the console.
In my case I'd ideally like to be able able to define a mapping of http codes to redirects or at least define a set of errors to display to the user in certain scenarios.

Looks like returning a string or json will work for my case, I'll just instruct users to log back in. Would be great to be able to provide a link, but alas, security. :)


Trouble getting not() to build

Me again. I recently updated to 0.5.0 and was looking forward to using not() for negation. My code changes are here: https://github.com/moonrepo/moon/pull/130/files#diff-59f9b6fb165685b88f87aed332e7f4f396bb795b2ad3f302f7d7944a36aa7cf6L123
For context, the negations come from a config file and are a Vec<String>, but Rust fails to build when I pass this type to not().
error[E0271]: type mismatch resolving `<std::string::String as TryInto<Glob<'_>>>::Error == BuildError<'_>`
   --> crates/utils/src/glob.rs:126:14
    |
126 |             .not(negations)?
    |              ^^^ expected struct `BuildError`, found enum `Infallible`
    |

I then tried references with &Vec<string> and even Vec<&str> with no luck. Both throw the same error above.
I've even tried converting the strings to Globs and passing Vec<Glob>, but that still fails to build also.
error[E0271]: type mismatch resolving `<Glob<'_> as TryInto<Glob<'_>>>::Error == BuildError<'_>`
   --> crates/utils/src/glob.rs:126:14
    |
126 |             .not(
    |              ^^^ expected struct `BuildError`, found enum `Infallible`
    |

The only thing that does work is explicitly passing [&str], like .not(["test/**/*"]), but this isn't an option for me.
Basically everything I've tried has failed, and I'm curious if you have any suggestions here.

Thanks for opening an issue!
This is a bug in the API. Instead of accepting types that emit a compatible error when converting into a Glob, the not function requires that the conversion emit BuildError. In the linked change, you've already constructed Globs, so the conversion is infallible and emits the Infallible error. This should work, but the API applies the wrong constraints.
I fear that functions like not and try_from_patterns put too much "type magic" in the public API. As a more immediate fix, I'll change the constraints on not so that the code in the linked change builds, but I'm considering changing these APIs to something less flexible but more simple.

In the meantime, you may be able to work around this by using Negation and filter_tree directly. The Negation::try_from_patterns function should be more flexible.
let glob = Glob::new(...).unwrap();
let negation: Vec<Glob> = ...;
let negation = Negation::try_from_patterns(negations).unwrap();
for entry in glob
    .walk(...)
    .filter_tree(move |entry| negation.target(entry))
{
    let entry = entry.unwrap();
    ...
}

See also the implementation of not, which uses Negation and filter_tree in the same way.

Thanks, using Negation directly unblocks me for now.

This has been fixed in 6d66a10. That change uses similar constraints in not as are used in try_from_patterns so that not can accept Globs directly.


fix 體

wrong encoding of character 體 found by maoken user
https://www.maoken.com/freefonts/2634.html

Thanks for the fix!
Yeah pretty terrible error, that title became 細線髒😂
I'll generate the dependent files.

all fixed. thanks.


Add simple helper that enables conversion to plain text

Follow up of work on #140 that gives users easy interface to strip markdown without adding any HTML.
Fixes #104 even more

Thanks!

Thanks for you for your all hard work!
Do you have any specific plans about releasing NuGet package with this and #140 ?

Do you have any specific plans about releasing NuGet package with this and #140 ?

I will try to release a new version later today.


[#280] Add nginx service in docker compose

Resolves #280
Changes

Add docker compose base file with Makefile
Add nginx service in docker compose

mrc-deploy 레포지토리에서 진행하게되어 이 PR 은 닫겠습니다.


final_step parameter wasn't passed in multiple chatflows

Description
The solution chatflow component uses the final_step parameter to change the next button to finish. But this parameter wasn't passed in pools, kubernetes, minio, and monitoring solutions
Steps to reproduce
Navigate to the last step of the chatflow of Pools. The next button is not changed to finish.

verified


Failing to compile due to argument mismatch

Pulled down the latest version of embit and secp256k1-embedded and ran into this problem when compiling:
libsecp256k1.c:721:15: error: too few arguments to function 'secp256k1_schnorrsig_verify'
     int res = secp256k1_schnorrsig_verify(ctx, sig, msg, &pub);

libsecp256k1.c:793:15: error: too many arguments to function 'secp256k1_schnorrsig_sign'
         res = secp256k1_schnorrsig_sign(ctx, sig, msgbuf.buf, (secp256k1_keypair *)keypair, NULL, NULL);

libsecp256k1.c:804:15: error: too many arguments to function 'secp256k1_schnorrsig_sign'
         res = secp256k1_schnorrsig_sign(ctx, sig, msgbuf.buf, (secp256k1_keypair *)keypair, NULL, data);

Is there something missing on my end that could be causing this?

Just noticed it yesterday as well... Looks like schnorrsig bindings in libsecp256k1 and libsecp256k1-zkp are slightly different.
I'll fix it ASAP.

I think these two commits fixed it:
https://github.com/diybitcoinhardware/secp256k1-embedded/commit/1102dababed4e97e46fd633884039f6916807420 - fix schnorrsig_sign
https://github.com/diybitcoinhardware/secp256k1-embedded/commit/10ab83293949d80fb3a2ca1bf32a1b5c60a42920 - fix schnorrsig_verify

Thanks for addressing this so quickly!
That resolves the compilation issues 🎉


Hands-on Lab

The link next to this article pointing to hands-on lab does not work. It takes to the hands-on lab home page and when I filter based on the topic (Azure Policy) - it does not show any labs

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

ID: 4eb454e0-eb5c-3ed2-c276-b4e3f1bc0ebd
Version Independent ID: 9cb7c2d2-ca6b-829a-40a2-f69e90210086
Content: Use Azure Policy to create and manage policies to enforce organizational compliance
Content Source: articles/azure-policy/create-manage-policy.md
Service: azure-policy
GitHub Login: @DCtheGeek
Microsoft Alias: dacoulte

@badalk - Thank you so much for letting us know!  I actually noticed this yesterday and hoped I'd fix it before someone spotted it, but nice eagle eyes. :)  The fix for this is already in flight and should go live on Monday.  Very much appreciate the notification and if you find anything else, let us know!
@MicrosoftDocs/azure-cxp-triage Please label this as 'doc-bug', assign to me, and #please-close.

@badalk We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


Add request retry logic.

Coverage remained the same at 100.0% when pulling f11d6962aed24592d6a9490a6675a9a73272896a on feature/retry-requests into 3b6a6596823e14499f905d6926b1721cc53b8c9a on master.


timer object (called Pomodoro)

[ ] attributes:
start time
stop time
category
sub category
type (pause/pomodoro)

https://dash-example-index.herokuapp.com/countdown

It's a standalone app so for the timer use a variable and call it as global from callbacks:
https://dash.plotly.com/sharing-data-between-callbacks


What does node_row_ptr stands for in the symbol json file?

Hi, does anyone know what the  node_row_ptr list stands for in the created json when the model is saved?
The nodes defines 33 total nodes for me, but the node_row_ptr contains 36 elements.

@KeyKy
https://docs.tvm.ai/dev/nnvm_json_spec.html#node-row-ptr

stores the history of forward path, so you can skip constructing the entire graph in inference tasks.
but I also can't understand how to get node_row_ptr

https://github.com/dmlc/nnvm/blob/master/docs/json_spec.rst


Support Azure Service Bus topics

Honestly skipping this for the moment because of the extra cost:-)

Honestly skipping this for the moment because of the extra cost:-)

Is this as in the cost of needing to provision a Standard SKU service bus instance?
Do any of the other providers support a similar model to topics and subs already?

I just need to pursue this and the AWS equivalent programs: https://cloudblogs.microsoft.com/opensource/2021/09/28/announcing-azure-credits-for-open-source-projects/
The Rabbit MQ transport is full featured already with support for both topics and rabbit mq bindings as well as simple publishing to queues.

Tasks
Don't for a second assume that this list is complete, I'm just jotting down some notes in case someone wants to take this on sooner rather than waiting for me to get around to it.

[ ] Get into AzureServiceBusTopic, implement the methods that implement NotImplementedException. Most of the methods are for checking whether the topic actually exists in Azure Service Bus, deleting the topic, or building it. See AzureServiceBusQueue to kind of see the pattern
[ ] AzureServiceBusTopic.CreateSender() should end up being the same code as AzureServiceBusQueue
[ ] New fluent interface helpers to PublishMessage<T>().ToAzureServiceBusTopic(topic name). See the Rabbit MQ or Azure Service Bus equivalents to queues or topics
[ ] End to end tests, duh.
[ ] Probably need to add an AzureServiceBusSubscription model similar to the Rabbit MQ binding model in the rabbit transport. Just to enable Wolverine to build the subscriptions on demand
[ ] Optionally -- may want to make an opt in message routing convention for Azure Service Bus topics


Accessibility annotations

Provide a11y annotations for headers on different pages.
A11y annotation kit

Added heading annotations and type scale to Annotations page.

Annotations can now be found in the Figma file "Annotations" page.


Possible to edit?

I'm guessing because this is an in development extension of the CLI and not a root module, and that's why there's no ability to edit it?

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

ID: 9a9e855a-abc5-14d9-ba73-4ab527ffee16
Version Independent ID: 85a46540-4b25-94f4-2c0e-29e1f8fefe35
Content: az devops
Content Source: latest/docs-ref-autogen/ext/azure-devops/devops.yml
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

@johnwildes : DevOps extension is present at https://github.com/Azure/azure-devops-cli-extension
you contribute to the code there (and also examples, help text ect)., although documentation is self generated
cc: @snankani

@tjprescott  this can be closed.


Removed max-width to make site more comfortable to read

Some docs have sections which are hard to read without scrolling (referenced here: https://github.com/golang/gddo/issues/627). This is to remove the max-width property to make docs a little more legible.
Without Change

With Change

@googlebot I signed it!


Off Canvas not triggering with custom build js

Hello
A few of the docs Zurb have supplied don’t quite add up with what is downloaded in a custom build. So until they fix it up which Zurb will do eventually. But until its fixed theres a couple of things to note.
foundation.min.js – Doesn’t Work
Use -> foundation.js
jquery.js – Doesn’t work
Use -> jquery.min.js
I cant quite give you an example of which parts of these are incorrect i think some classes are missing from the trigger 'button' http://foundation.zurb.com/sites/docs/off-canvas.html
I wrote a blog with a code snippet of working code here:
http://naileditdesign.com/foundation-6-off-canvas/

I don't see the issue with offcanvas not opening on the live docs, can you explain the problem in more detail?

https://github.com/zurb/foundation-sites/issues/7088


Fix the default value of parameter 'sendMsgTimeout'，the default value…

1、Please describe the issue you observed:

As the picture above shows, the default value of the parameter sendMsgTimeout is 10000, but in the code, the default value is 3000.
https://github.com/apache/rocketmq/blob/bda0ae0305863cc5fa2e0578439dfa4f4d9908b3/client/src/main/java/org/apache/rocketmq/client/producer/DefaultMQProducer.java#L102

Codecov Report

Merging #4493 (fcb1c42) into develop (32733e7) will decrease coverage by 0.34%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##             develop    #4493      +/-   ##
=============================================
- Coverage      48.16%   47.81%   -0.35%
+ Complexity      5127     5079      -48
=============================================
  Files            649      649
  Lines          43021    43021
  Branches        5625     5625
=============================================
- Hits           20720    20571     -149
- Misses         19798    19936     +138
- Partials        2503     2514      +11

Impacted Files
Coverage Δ

...rg/apache/rocketmq/common/stats/StatsSnapshot.java
84.61% <0.00%> (-15.39%)
:arrow_down:

...org/apache/rocketmq/common/stats/StatsItemSet.java
44.77% <0.00%> (-10.45%)
:arrow_down:

.../apache/rocketmq/common/stats/MomentStatsItem.java
38.09% <0.00%> (-9.53%)
:arrow_down:

...va/org/apache/rocketmq/store/FlushDiskWatcher.java
81.25% <0.00%> (-9.38%)
:arrow_down:

...ache/rocketmq/common/stats/MomentStatsItemSet.java
43.47% <0.00%> (-8.70%)
:arrow_down:

...va/org/apache/rocketmq/logging/inner/Appender.java
29.21% <0.00%> (-7.87%)
:arrow_down:

...in/java/org/apache/rocketmq/test/util/MQAdmin.java
38.88% <0.00%> (-5.56%)
:arrow_down:

...org/apache/rocketmq/store/ha/WaitNotifyObject.java
66.07% <0.00%> (-5.36%)
:arrow_down:

...va/org/apache/rocketmq/common/stats/StatsItem.java
50.83% <0.00%> (-5.00%)
:arrow_down:

...ache/rocketmq/broker/topic/TopicConfigManager.java
54.61% <0.00%> (-4.62%)
:arrow_down:

... and 19 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 32733e7...fcb1c42. Read the comment docs.

Coverage decreased (-0.2%) to 51.854% when pulling fcb1c42bfe2e5c1f8d4949004d3477342b3e8230 on ycfxhsw:docs_send_time_out_fix into 32733e76747f3db761ace75cfed6d6fdcdaee81a on apache:develop.

Coverage decreased (-0.2%) to 51.854% when pulling fcb1c42bfe2e5c1f8d4949004d3477342b3e8230 on ycfxhsw:docs_send_time_out_fix into 32733e76747f3db761ace75cfed6d6fdcdaee81a on apache:develop.

Maybe, we should justify the semantics of sendMsgTimeout.
Previously, it attempts to limit the overall amount of time, including transparent and explicit retry.
After examining multiple projects, it turns out it would be better if we could separate retry into explicit and transparent ones.  For the explicit retry, jitter in most cases is desirable.  Further, let's users specify RPC tier timeout is more reasonable.


Remove legacy fix for grouped categorical charts

We should just show the new bar vertical bar charts instead of the screenshot below.

This is actually being triggered by an edge case where all values are missing. Need to clean up misleading error text ("... first 5 most prevalent levels ...") and put in a quick check to not render chart when there are no values to plot.

Test Notes: Confirm that a message saying "All values are missing" prints instead of a chart when nmissing = N (as it does in the screenshot above. @samussiah to test using project 264 - AE file.


Stopped working, i get "Unavailable"

I had this appear for all my devices:
"This entity is no longer being provided by the smartthings_find integration. If the entity is no longer in use, delete it in settings."
Except for my galaxy s6 watch (which is not exactly smartthing item)
Anyone else had encounter that?

Yes, same behaviour for me since about 5 days ago.  Nothing in the logs but I haven't tried enabling the debug level.  Presumably due to an API change, but if the maintainer needs any further information I'm happy to help.

This is actually a problem with the SmartThings website itself. Whenevery I had this problem in the HA integration, the devices were missing from the website aswell. Only phones and tablets were still shown on the website. Logging out and back in fixed the problem.
I need to find a way to detect this scenario and trigger the reauth flow.
While I probably won't be able to fix this the next two weeks, in the meantime you could simply remove and readd the integration. This should fix it at least temporarily.
You also could manually edit the JSESSIONID in .storage/core.config_entries to any invalid value and after a restart of HA you should be prompted to login again.

after i did the re-auth, it worked, but now it keeps asking me to re-auth all the time.

it even shows my to update the integration twice!

Are you sure you're on the latest version of this integration?
Also, how did you reauthenticate - did you remove the integration or manually edit the .storage-file?
Make sure to always restart HA when doing changes like that!

Yeah restart probobly solve it

Had the same,
Is it not possible that we can automate the steps we do to ready it.
That we can see if all sensorsystemen go to unavailable. It ready them all.
After that step it all works indeed.
Atleast will make automation that it send notification to me. Then I know to fix it. That will be the first step for me

Thanks, make sense.
Just very annoying, where is this problem coming from?

Sorry for my late response. I was really busy with other stuff the last few weeks (and still am...)
Can't tell exactly, where the problem is coming from. It seems like the (unofficial) API only responds with a few devices after some time.
Currently, the integration works like this:

On HA start, get a list of all available devices from SmartThings
Fetch the data for each of these devices at a specific interval (unless the device is disabled by the user)

Both have their own API endpoint. Now for some reason, the first endpoint only responds with a subset of devices after a few days/weeks. For me it were mainly the SmartTags that were missing while phones/tablets were still available.
So it's not exactly the integrations fault, but we definitely need to find a workaround. Currently I can think of two solutions:

Somehow "detect" that some devices are missing and in that case raise the reauth flow. In this case you have to log in again but after that everything should be working again.
Don't rely on the device-list from the API after initial setup. This would require to store the device list somewhere in HA (which would not be a big problem). The integration could now still feth the data-endpoint even if the device is not available in the device-list-endpoint anymore. However it might very well be that the data endpoint does not work anymore aswell, as soon as the session is in that "corrupted" state. In that case, this solution would not work.

It's also pretty hard to test because I have to wait for the session to get into this state, which sometimes happens after a few hours, sometimes after a few weeks...

I'm sure you tested it but that's what the gpt told me:
Descriptions of Errors or Bugs and Possible Solutions

Error Handling:

Bug: Insufficient error handling in API requests may lead to unhandled exceptions and integration failures.
Solution: Implement comprehensive error handling to catch and log exceptions, ensuring the integration can recover or inform the user appropriately.def fetch_data(self):
    try:
        response = requests.get(API_URL, headers=self.headers)
        response.raise_for_status()
        return response.json()
    except requests.exceptions.HTTPError as http_err:
        self.logger.error(f"HTTP error occurred: {http_err}")
    except Exception as err:
        self.logger.error(f"An error occurred: {err}")
    return None

Session Management:

Bug: The integration might not handle session expiration correctly, causing loss of device data retrieval.
Solution: Add logic to check for session expiry and re-authenticate automatically.def get_session(self):
    if self.session_expired():
        self.reauthenticate()
    return self.session

def session_expired(self):
    # Logic to check if session is expired
    return self.session_expiry_time < datetime.now()

def reauthenticate(self):
    # Logic to reauthenticate and get new session
    self.session = requests.Session()
    self.session_expiry_time = datetime.now() + timedelta(hours=1)  # Example expiry time

API Rate Limits:

Bug: Frequent API requests might hit rate limits, causing incomplete data retrieval.
Solution: Implement rate limit handling to pause and retry after hitting limits.def fetch_data(self):
    response = requests.get(API_URL, headers=self.headers)
    if response.status_code == 429:  # Too Many Requests
        self.logger.warning("Rate limit hit, sleeping for a while")
        time.sleep(60)  # Sleep for 1 minute
        response = requests.get(API_URL, headers=self.headers)
    return response.json()

Polling Interval Configuration:

Bug: Fixed polling intervals may not suit all user needs, leading to inefficiencies or excessive battery drain.
Solution: Allow users to configure polling intervals via the configuration flow.class SmartThingsFindConfigFlow(ConfigFlow, domain=DOMAIN):
    async def async_step_user(self, user_input=None):
        if user_input is not None:
            return self.async_create_entry(title="SmartThings Find", data=user_input)
        return self.async_show_form(step_id="user", data_schema=vol.Schema({
            vol.Required("polling_interval", default=120): int,
        }))

Polling Impact:

Bug: Frequent polling might cause battery drain on connected devices like watches and phones.
Solution: Allow disabling polling for specific devices and provide options to adjust the polling frequency.def schedule_polling(self, interval):
    self.hass.helpers.event.track_time_interval(self.update_devices, timedelta(seconds=interval))

async def update_devices(self, now):
    # Fetch and update device data
    pass

class SmartThingsFind(Entity):
    def __init__(self, hass, interval=120):
        self.hass = hass
        self.schedule_polling(interval)

By addressing these bugs and implementing the suggested solutions, the HA-SmartThings-Find integration can become more robust, user-friendly, and efficient.


Draggular in a nested ng-repeat

Dragular wouldn't work in a nested ng-repeat loop:

  {{assignment.name}}

      {{el}}

      {{el}}

for solution, see http://luckylooke.github.io/dragular/#/docs/exampleNestedNgRepeat


Question about avoiding collision

First of all, thank you for sharing your nice work.
I have some questions about your work.
I have looked your code and it seems that you just give obstacles' location and goals' location to agents.
Is that right?
Thank you,

Hi @moonsh
Yes, that is correct


“No matching autocommands”

When loading a plugin prematurely – as shown in the following vimrc – vim will show the warning “No matching autocommands.”
call plug#begin()
Plug 'tpope/vim-repeat'
call plug#load('vim-repeat')
call plug#end()

This is a result of plug#load() calling doautocmd BufRead as seen here while there hasn’t been any autocommand for BufRead defined yet. A simple silent should fix this.

The question would be: why one would do such thing? The fix for this case is really easy as you suggested but should vim-plug prevent misused feature?

Adding silent to vim-plug is easy, but I'm worried that it might also hide important/useful messages that need attention. So I'd suggest just changing the line to silent call plug#load('vim-repeat') if you really must.
The only case I can imagine that one would want to call plug#load() before plug#end() is the case of vim-sensible. One might be tempted to write:
call plug#begin('/tmp/plugged')
Plug 'tpope/vim-sensible'

" (If the user prefers to interleave plugin settings in vim-plug block)
call plug#load('vim-sensible')
" Override sensible defaults

call plug#end()

But loading vim-sensible causes some BufRead events to be set, so you won't see the warning message in this case anyway.

I use vim-sensible myself but is easy enough to use it like https://github.com/vheon/home/blob/master/.vim/vimrc#L111

I realized that putting a silent in plug#load() is merely a workaround. Maybe wrapping the doautocmd with a check on whether there are any BufRead autocommands defined is an alternative.

@tsuflux That's the first thing that came to my mind, but realized that simple exists('#BufRead') was not enough for the purpose and stopped looking further. You haven't told us why you want to do it in the first place. I think you probably shouldn't.


[WIP]fixed main content area height issue

issue: #2487

@dclarizio Please review

@h-kataria please review

@miq-bot remove_label wip


Add some helpers in CountryProvider

I'm using this awesome library and I think those helpers may be a cool add :

get country list
get translated name from country code and language code (if exists)
get translated name from country code and CultureInfo (if exists ro default)

@MrGrabazu the commit have failures check AppVeyor log

I don't touch this test part, the data validation fail because the source
of data used to compare has changed.
Le lun. 6 mai 2019 à 20:16, Tino Hager<EMAIL_ADDRESS>a écrit :

@MrGrabazu https://github.com/MrGrabazu the commit have failures check
AppVeyor log
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tinohager/Nager.Country/pull/1#issuecomment-489720877,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABU3SICWAZR6B6VQLNYMRB3PUBYXBANCNFSM4HIDNJTA
.


Update http links

@NextTurn : Thanks for your contribution! The author, @abshamsft, has been notified to review your proposed change.


Allow adding tags to a conversation upon creation

#52
Added another input box on conversations.jsp's "New Conversation" section to allow the user to add tags to the conversation upon creation.

also can you edit the title/description with more details about the PR?

Closing to restructure.


[MM-32418] Export channel on incident archive

Summary
This code will implement export channel on incident archive
Ticket Link
Jira card: https://mattermost.atlassian.net/browse/MM-32418
Github issue: https://github.com/mattermost/mattermost-server/issues/17311
Release Note
- create new column ExportChannelOnArchiveEnabled on IR_Playbook and IR_Incident table
- update select queries in each playbook and incident
- update api createIncident to set property ExportChannelOnArchiveEnabled from playbook
- update function UpdateStatus to export the channel

Hello @arvinDarmawan,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.

Thank you, @arvinDarmawan, this looks really good! We will try to review it as soon as we can :) I see that you created this PR as a draft. Should we wait for more changes?

Thank you, @arvinDarmawan, this looks really good! We will try to review it as soon as we can :) I see that you created this PR as a draft. Should we wait for more changes?

It's already done for  the ExportChannelOnArchiveEnabled ui and create/update column ExportChannelOnArchiveEnabled. Only  left export  the channel  for this issue. I will check it.

Hi @agarciamontoro I already successfully install the channel export plugin in my local according to documentation.

But after I go to Incident page, I can't export the channel even though the incident status is "Archived".

The error  on server log is same as before too.
{"level":"error","ts":1624276400.731646,"caller":"mlog/log.go:251","msg":"Plugin failed to ServeHTTP, muxBroker couldn't Accept request body connection","plugin_id":"com.mattermost.plugin-incident-management","error":"timeout waiting for accept"}
{"level":"error","ts":1624276400.731712,"caller":"mlog/log.go:251","msg":"Plugin failed to ServeHTTP, muxBroker couldn't accept connection","plugin_id":"com.mattermost.plugin-incident-management","serve_http_stream_id":7,"error":"timeout waiting for accept"}

What am I missing ?  Is it because of the license type or  error in my code ?

I'm reviewing the Channel Export code and it looks like we don't check for the EnableTesting and EnableDeveloper settings, as we do in Incident Collaboration. Could you try to request a trial license? You can do so by going to the System Console and clicking on the Start trial button. That should unlock you for now; in the meanwhile, I'm gonna fix that in the Channel Export plugin. Thank you for reporting!

If you don't see the Start trial button, you'll see a similar button with Upgrade to Enterprise Edition. You can use that button if you're developing from a Linux machine to upgrade to the E0 edition, and then you'll see the Star trial button. Otherwise, let me fix that in the Channel Export plugin so I can unblock you there. Sorry for the inconvenience!

If you don't see the Start trial button, you'll see a similar button with Upgrade to Enterprise Edition. You can use that button if you're developing from a Linux machine to upgrade to the E0 edition, and then you'll see the Star trial button. Otherwise, let me fix that in the Channel Export plugin so I can unblock you there. Sorry for the inconvenience!

Ok, thank you @agarciamontoro

Hi @agarciamontoro , this is the expected result, right ?
It already running in my local and send direct message with the url link (it will download the csv).
I testing it by comment out the license checking in my local channel-export plugin and deploy it to my local mattermost.
I already push it to  this PR.

@arvinDarmawan:

send direct message with the url link (it will download the csv).

Oh I had not thought of that solution, it's actually really straightforward! The thing is that I took a quick look at your code and you're making the request but then discarding the response, right? What I was imagining is that the code makes the request and use the returned file (which is the body of the response) to attach it to the DM. To attach a file to a post, you first need to upload it (take a look at the code of this function) and then create the post with the FileIds field set to the file ID returned by the uploading process (see this line).

testing it by comment out the license checking in my local channel-export plugin and deploy it to my local mattermost.
I already push it to this PR.

That's a brilliant solution, thanks!

To attach a file to a post, you first need to upload it (take a look at the code of this function) and then create the post with the FileIds field set to the file ID returned by the uploading process (see this line)

hi @agarciamontoro , sorry I'm still new in these plugin things. I have another question.
For uploading and create the post with the FileIds, I can't call  these two functions directly in channel-exports plugin  from mattermost-plugin-incident-collaboration since  I only have access to channel-exports plugin  from  api  v1/exports in channel-exports plugin, right ?.
So I need to call these function from  plugin_api.go  in mattermost-server ??

hi @agarciamontoro , sorry I'm still new in these plugin things. I have another question.

Don't be sorry, you're doing a great job, getting started with these codebases is never an easy thing.

For uploading and create the post with the FileIds, I can't call these two functions directly in channel-exports plugin from mattermost-plugin-incident-collaboration since I only have access to channel-exports plugin from api v1/exports in channel-exports plugin, right ?
So I need to call these function from plugin_api.go in mattermost-server ??

Not exactly. The code I linked in my previous comment was just to illustrate what we need to do. We'd need to use the same code inside the upload function to upload the contents returned by the /api/v1/export request to Mattermost, and then use the returned ID in the creation of the post. It would be something like the following (I have not tested this at all, so you will probably need to tweak a lot of things):
// set url and query string
exportPluginURL := fmt.Sprintf("plugins/com.mattermost.plugin-channel-export/api/v1/export?format=csv&channel_id=%s", incidentToModify.ChannelID)

 // The request has no body, so we can set the last param to nil
req, err := http.NewRequest(http.MethodGet, exportPluginURL, nil)
req.Header.Add("Mattermost-User-ID", incidentToModify.OwnerUserID)
if err != nil {
    s.pluginAPI.Log.Warn("failed to create request for exporting channel", "plugin", "channel-export", "error", err)
}

res := s.pluginAPI.Plugin.HTTP(req)
defer res.Body.Close() // <- always good to call Close as soon as possible, but deferring it so it is actually done at the end of the function
if res.StatusCode == http.StatusOK {
    // Instead of using ReadAll and discarding the results, pass the body to the Upload function. This returns a file struct, which contains the ID we need!
    file, err := s.PluginAPI.File.Upload(res.Body, "filename, maybe the channel name", incidentToModify.ChannelID)
    if err != nil {
        s.PluginAPI.Log.Error("unable to upload the exported file to the channel",
	        "Channel ID", channelID, "Error", err)
        return nil, errors.Wrap(err, "unable to upload the exported file")
    }

    // We don't need these anymore
    // url := fmt.Sprintf("/%s", exportPluginURL)
    // msg := fmt.Sprintf("[%s](%s)", incidentToModify.Name, url)

    // Now, use something like what I linked before, instead of s.poster.DM, which is not flexible enough.
    // You'll need to add the PostDM function to the Poster interface and to the bot/poster.go file, which would just
    // get a post and override the channel ID with the ID of the DM between the user and the bot, and the user ID with
    // the bot ID , similar as to what the DM function does
    err = s.poster.PostDM(incidentToModify.OwnerUserID, &model.Post{
	    Message:   fmt.Sprintf("Incident %s exported", incidentToModify.Name),
            FileIds:[]string{file.Id},
    })

    if err = s.poster.DM(incidentToModify.OwnerUserID, "Data successfully exported %s", msg); err != nil {
        return errors.Wrap(err, "failed to send exported channel result to incident's commander")
    }
}

If you want to, we can have a quick Zoom chat and go through the code together. Just ping me at<EMAIL_ADDRESS>and we can schedule a quick call.

Done @agarciamontoro .
More or less like this the result, right ?

@agarciamontoro, I've taken a look at this and see some of the wording needs to be updated for the UI messaging. Is there a separate PR for this work or should I review this PR's files for that? I'm 0/5 on how to do it. :)

@justinegeffen, what UI messages do you mean? In any case, you can review them here, no problem!

@justinegeffen, what UI messages do you mean? In any case, you can review them here, no problem!

Sorry - I was referring to messaging/modals. Looks like there weren't as many as I anticipated. :)

Removing the Editor review label as Justine is out on vacation and everything was actually solved!
@prapti, all yours to test :)
This should be fairly straightforward to test:

Create a playbook with the Export channel setting, under the When a run is archived section, enabled.
Run that playbook.
Update the status, changing the state to Archived.
Check that the owner receives a DM from the Playbooks bot with the CSV file of the exported channel.

@arvinDarmawan, I have tested this (Prapti is out these days, so I'm doing it myself) and it works great! I tested the feature with admins and end users, with public and private channels, and with the user archiving the run being different than the owner, and it worked in all cases :muscle:
I did find a couple of minor things, which I fixed in the two latest commits (I did not want to disturb you anymore with this!):

https://github.com/mattermost/mattermost-plugin-incident-collaboration/pull/595/commits/6dd446c6970a12fbc6a43506f956b888d834f36a: When the channel export fails, I found that returning an error results in the modal showing an error, which looks like the status was not updated, although it was. I fixed this by simply returning nil here.
https://github.com/mattermost/mattermost-plugin-incident-collaboration/pull/595/commits/20d805cd8537c37ce158b0a69e1748b3874db2ec: This is just a quality of life improvement: I added a link to the playbook run channel in the message sent to the owner.

We're discussing a last thing in the team, as the channel export feature is an E20 feature, while all actions are available in all plans. I'll go and merge this PR as soon as tests pass, though, as it works flawlessly. If we need to tweak something in the license side, we'll do it in a separate PR.
Thank you very much for all your work on this, it was awesome! :tada:

Will try to auto merge this PR once all tests and checks are passing. This might take up to an hour.


Shield Value reset to 0

I am a level 60 mage. When I apply ice barrier (r4), the shield gets the correct value (855). I then apply mana shield (r6) and the shield gets the correct value (1424).
When I cancel my ice barrier aura goes away, the shield displays a value of (0) even though I still have time and value left on my mana shield aura

@Elkleaf
Idk how to contribute and release a new version of nanShield so fixed the bug and posted a new one here.
@nan-gameware , please let me know if you don't feel comfortable me posting an edited version of your aura, I'll remove immediately. Just ran into the error too many times and saw many open issues and wanted to fill the gap at least temporarily.
Thank you!


Convert demo files to Sketch v69

We'd love to convert the existing demo files (here) into the latest version of Sketch (v69).
How-to

Open all demo files in Sketch v69.
Save the files back to disk, under apps/xlayers/src/assets/demos/sketchapp/69.
Commit and push your changes.

Thank you ❤

I've just created the PR

Hey @anediaz you can edit the environment files and create a new entry in the array. Here is the new entry to create:
{
      value: 69,
      disabled: true,
      files: [
        'md-components-notifications-heads-up',
        'md-components-cards-welcome-back',
        'md-components-tabs-status-bar',
        'md-components-cards-safari',
        'md-components-date-picker',
        'md-components-chips-open-chip',
        'md-components-cards-homes',
        'md-components-buttons-lights',
        'md-components-cards-pooch',
        'md-components-buttons-fabs-light',
      ],
    },

Here are the files:

https://github.com/xlayers/xlayers/blob/main/apps/xlayers/src/environments/environment.hmr.ts#L11-L26
https://github.com/xlayers/xlayers/blob/main/apps/xlayers/src/environments/environment.prod.ts#L11-L26
https://github.com/xlayers/xlayers/blob/main/apps/xlayers/src/environments/environment.ts#L11-L26

Yes no problem. As I've only followed your first advice I was surprised this part was forgotten

Fixed in https://github.com/xlayers/xlayers/commit/df2c03011d0edd429958cf671d10513aa32705b0


Articulate that D3Cold requires _S0W(4) regardless of device wake capability

[Enter feedback here]
Per other public docs ( see _S0W method in ASL code sample on this page: https://docs.microsoft.com/en-us/windows-hardware/drivers/bringup/firmware-requirements-for-d3cold ) and Intel testing, please articulate on this page in the “_SxW” section that _S0W(4) is a requirement for D3Cold regardless of whether or not the device supports wake.

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

ID: b168f14f-59e0-9fe6-d600-6e06621e4b77
Version Independent ID: 79f32da9-5815-a833-7683-50016bd272f3
Content: Device power management - Windows drivers
Content Source: windows-driver-docs-pr/bringup/device-power-management.md
Product: windows-hardware
Technology: windows-devices
GitHub Login: @barrygolden
Microsoft Alias: bagold

Adding this feedback to an internal work item to update the Device power management topic.

Adding this feedback to an internal work item to update the Device power management topic.

Updated topic per feedback above:
https://github.com/MicrosoftDocs/windows-driver-docs-pr/pull/1026


Add Model Card to repo

Something similar to Model
Cards.

Recommended Modifications for Model_Card.md:

Removing the word [optional] at Line Numbers:

[ ]  27
[ ] 28
[ ] 32
[ ] 39
[ ] 40
[ ] 52
[ ] 95
[ ] 103
[ ] 141
[ ] 159

Adding details of the Metrics Section [starting Line 127] & making the necessary changes to Results Section [ Starting Line 133]. The result section needs further evaluation.
-[] Changes Made

Environmental Impact [Line 147]
-[] Need to Add details

Hardware Details [Line 169]
-[] Add AWS Instance Details (Instance Type, RAM, SDD, vCPUs)

Software Details [Line 173]
-[] Add Software Library Used [OpenMP (lightgbm), xgboost, etc]

Added changes in #71


ECC rather than RSA

As discussed previously in #52 and #270, now might be a better time to document ECC by default rather than RSA.
See a proposal in #362.
PS: Thank you @drduh for this very useful guide BTW.

As mentioned in this article: https://security.stackexchange.com/questions/255358/why-does-ecc-not-have-an-encrypt-capability-in-gpg-but-rsa-does the usage of ECC is a bit more complicated but the combination of this article and the guide, a setup with ECC should be possible. I am gonna try it in the next months, when i have time for it

ECC subkey handling is currently rather broken in gnupg - see, for example, https://dev.gnupg.org/T5555

Until there's a compelling reason offered to use ECC for Yubikeys, let's stick to tried and true RSA for defaults. As before, anyone is welcome to add an additional section on generating ECC keys instead and using them - please send a PR.


 Kill command completion from FZF package only completes PIDs and it doesn't fall-back to previously defined completion.

I see, do you know how to fix it?

Yes, I can. However, I've been looking into fzf completions yesterday and thinking about a different approach for it.
FZF completions are currently duplicating some code that's already defined inside bash completions.
For example, in fzf when you expand '**' it triggers a fzf defined shell function to prepare a list of hosts to complete. This function is however not identical to the the bash's one. E.g. in bash I use HOSTFILE to add additional hosts for the host completion. This is missing from the fzf '**' completion.
I think that an alternative way to approach completions might be to leverage the existing completions and use fzf to filter those. It would work like this:
ssh -i ** -> completion of files with fzf
ssh -l ** -> completion of users with fzf
ssh -c ** -> completion of crypto algorithms with fzf

By leveraging the existing completions you can:

fix inconsistencies between the completions.
remove a lot of code from fzf completions and make it simpler though more powerful.
remove the need to specify which commands need file completion and which need directory completion. This is handled by bash completions already.
by changing the trigger to  you can have fzf be applied to all completions. This is quite amazing.

I've tried that with a proof of concept ssh completion and it works great. The code is in the early stage, it's just a proof of concept as of now. It triggers the existing completion and then it uses fzf to select the item from the completion list. Hopefully, I'll find a bit more time to finish it in the next couple of days. It might work as a replacement or an alternative to the current completions.

Cool, love the idea!

that's already defined inside bash completions

Only if you installed custom bash completions such as the one you linked above. We can leverage those external completions, but we still have to use our functions when alternatives are not found.

I would love to use the bash-native list of hosts for completion through fzf. Any chance you still have your proof of concept to share?


Is it possible to convert AlpacaData to pandas/numpy/CSV data?

I adapted the following code from the README.md:
import alpaca_backtrader_api
import backtrader as bt
from datetime import datetime

ALPACA_API_KEY    = "..."
ALPACA_SECRET_KEY = "..."
ALPACA_PAPER      = True

store = alpaca_backtrader_api.AlpacaStore(key_id     = ALPACA_API_KEY,
                                          secret_key = ALPACA_SECRET_KEY,
                                          paper      = ALPACA_PAPER)

data = store.getdata(dataname   = "AAPL",
                     historical = True,
                     fromdate   = datetime(2015, 1, 1),
                     timeframe  = bt.TimeFrame.Days)

The resulting data of type AlpacaData works fine with cerebro, but I'm struggling to figure out how it's possible to use directly. len(data) returns 0. My goal is simply to perform some general analyses like identifying local extrema to help in developing my strategy. I guess I could download the data once through alpaca-backtrader-api for backtesting, and then again through the Alpaca API for other analyses, but isn't there any way to just do it once to get an AlpacaData object (which I guess is a Backtrader data feed?), and then convert that to a numpy series, or a pandas DataFrame, or CSV?
Apologies if I'm missing something obvious. I'm new to both Backtrader and Alpaca. I wanted to first ask the Backtrader community, but unfortunately their forum is not letting me register because the CAPTCHA isn't loading.

Hi,
sorry for the late response.
as you said you could do it in 2 ways (probably best to use alpaca-trade-api to get raw data)
but if you want to get data exactly like backtrader your best option is to put a breakpoint/print in this file:
alpacastore.py function name: _t_candles. this is where we get the data from the broker and pass it to backtrader datafeed


IE9/10: Meteor.users.attachSchema - Object doesn't support property or method 'attachSchema'

I get the following JavaScript runtime error when running my Meteor app in Internet Explorer 9 and 10 (I haven't checked before 9, and there's no issue in IE11):
Object doesn't support property or method 'attachSchema'
Problem line: Meteor.users.attachSchema( Schemas.User );
I don't get this error for any of my other Collections that use attachSchema.
I haven't seen this exact issue mentioned anywhere and I've been looking for a while.
Would really appreciate any help! Thanks!

I have attached a screenshot of my directory structure, in case it helps. The file in question is located in both/collections/_schemas

@aldeed that's also happening to me, only with Meteor.users

Solution:
Meteor.users.attachSchema = Meteor.users.attachSchema || Mongo.Collection.prototype.attachSchema

I'm using meteor 1.4 and getting error Cannot set property 'attachSchema' of undefined.


Dev

add slice print copy shape method for StereoExpData
add ligand-receptor interaction tool

Thank's for committing, the cell_names is a ndarray whose type is int32 or int64, i think it would cause error at line 405 of stereo_exp_data.py and you should also delete line 415.

Thank's for committing, the cell_names is a ndarray whose type is int32 or int64, i think it would cause an error at line 405 of stereo_exp_data.py, also, the line 441 should be deleted. So, will you change it or we do?
As for the LrInteraction, we need to review futher.


Add missing user_to_actor method for Meetup

As part of snarfed/bridgy/issues/873, we need to implement this method
for Brid.gy to correctly determine the actor in use.

Even when using this branch, I seem to be getting issues with:
Traceback (most recent call last):
  File "/tmp/tmpNJMdII/lib/python3.7/site-packages/webapp2.py", line 1573, in __call__
    rv = self.handle_exception(request, response, e)
  File "/tmp/tmpNJMdII/lib/python3.7/site-packages/webapp2.py", line 1567, in __call__
    rv = self.router.dispatch(request, response)
  File "/tmp/tmpNJMdII/lib/python3.7/site-packages/webapp2.py", line 1314, in default_dispatcher
    return route.handler_adapter(request, response)
  File "/tmp/tmpNJMdII/lib/python3.7/site-packages/webapp2.py", line 1138, in __call__
    return handler.dispatch()
  File "/tmp/tmpNJMdII/lib/python3.7/site-packages/webapp2.py", line 606, in dispatch
    return self.handle_exception(e, self.app.debug)
  File "/tmp/tmpNJMdII/lib/python3.7/site-packages/webapp2.py", line 604, in dispatch
    return method(*args, **kwargs)
  File "/tmp/tmpNJMdII/lib/python3.7/site-packages/oauth_dropins/meetup.py", line 178, in get
    self.finish(auth, state=csrf.state)
  File "/app/meetup.py", line 57, in finish
    self.maybe_add_or_delete_source(Meetup, auth_entity, state)
  File "/app/util.py", line 480, in maybe_add_or_delete_source
    user_url=user_url, **kwargs)
  File "/app/models.py", line 471, in create_new
    source = cls.new(handler, **kwargs)
  File "/app/meetup.py", line 40, in new
    actor = gr_source.user_to_actor(user)
  File "/tmp/tmpNJMdII/lib/python3.7/site-packages/granary/source.py", line 523, in user_to_actor
    raise NotImplementedError()
NotImplementedError

@snarfed I've verified this works locally with my Brid.gy PR :raised_hands: so unless there's anything you'd like with this, it's good to go :+1:

@snarfed that's fixed now, ready for review :+1:

thanks for the updates and tests!
one last minor thing: mind refactoring the tests into just a single one that checks the entire returned actor? and the test user and actor into constants? those are the patterns used in the rest of the granary tests. apologies for the nitpick. 😊 eg:
https://github.com/snarfed/granary/blob/be802e4640dafb3c4dd4c419aae84c7577a56df6/granary/tests/test_github.py#L31-L34
https://github.com/snarfed/granary/blob/be802e4640dafb3c4dd4c419aae84c7577a56df6/granary/tests/test_github.py#L80-L83
https://github.com/snarfed/granary/blob/be802e4640dafb3c4dd4c419aae84c7577a56df6/granary/tests/test_github.py#L446-L447

Sure thing! Pattern I'm used to elsewhere, happy to align with project guidelines

@snarfed should be addressed now!

🎉


Rewrite LightApi

LightApi is reinventing the wheel - libraries like RestSharp already exists and does what it does in a much better way - but, worse, LightApi is full of design and implementation issues. In the sake of conciseness, this issue tracks all of it's defects.
Before we get into that, my official recommendations is to excise LightApi from the framework and adopt RestSharp. We should be doing that on milestone 2.0.0. Nonetheless, there are many people already using LightApi and, for their sake, I'll try to fix as many bugs as possible. Design issues, however, won't be addressed unless completely necessary.
Before dealing with any of the issues related here, one should do the unit tests (#148).
Note: everything mentioned here also applies to its base class, AbstractAPIWrapper.
The class makes a lot of misuses of async/await, Task, etc.
On many places, the code forces synchronicity:
https://github.com/Avanade/Liquid-Application-Framework/blob/8f03b94252db859c61992662bc7c84fced8fee64/src/Liquid.Domain/API/LightAPI.cs#L127
https://github.com/Avanade/Liquid-Application-Framework/blob/8f03b94252db859c61992662bc7c84fced8fee64/src/Liquid.Domain/API/LightAPI.cs#L216
https://github.com/Avanade/Liquid-Application-Framework/blob/8f03b94252db859c61992662bc7c84fced8fee64/src/Liquid.Domain/API/LightAPI.cs#L247
And so on and so forth.
To make matters worse, the class presents async methods that wraps this forced synchronous code in a task, effectively wasting at least two threads and creating numerous performance issues:
https://github.com/Avanade/Liquid-Application-Framework/blob/8f03b94252db859c61992662bc7c84fced8fee64/src/Liquid.Domain/API/AbstractAPIWrapper.cs#L103
https://github.com/Avanade/Liquid-Application-Framework/blob/8f03b94252db859c61992662bc7c84fced8fee64/src/Liquid.Domain/API/AbstractAPIWrapper.cs#L118
Etc.
Duplicated code
Hard to read/debug critical code is duplicated:

https://github.com/Avanade/Liquid-Application-Framework/blob/8f03b94252db859c61992662bc7c84fced8fee64/src/Liquid.Domain/API/AbstractAPIWrapper.cs#L78
https://github.com/Avanade/Liquid-Application-Framework/blob/8f03b94252db859c61992662bc7c84fced8fee64/src/Liquid.Domain/API/AbstractAPIWrapper.cs#L50

https://github.com/Avanade/Liquid-Application-Framework/blob/8f03b94252db859c61992662bc7c84fced8fee64/src/Liquid.Domain/API/LightAPI.cs#L433
https://github.com/Avanade/Liquid-Application-Framework/blob/8f03b94252db859c61992662bc7c84fced8fee64/src/Liquid.Domain/API/LightAPI.cs#L466
It won't correctly set headers for requests
See #66.
AbstractApiWrapper is coupled to HttpClient.
Although AAW is supposed to use it's concrete implementations to perform the requests (AbstractApiWrapper.Get, AbstractApiWrapper.Post, etc), for some reason AbstractApiWrapper.ResilientRequest directly uses a HttpClient, simply removing the benefit of it being a base abstract class.
It isn't thread-safe
HttpClient is supposed to be thread-safe because, since it opens up a socket, you get better performance if you reuse it. However, the implementation of LightApi isn't, as the code change default properties that are shared among all calls.
Docs: https://docs.microsoft.com/en-us/dotnet/api/system.net.http.httpclient?view=netframework-4.8#remarks
Non-thread-safe manipulation:
https://github.com/Avanade/Liquid-Application-Framework/blob/8f03b94252db859c61992662bc7c84fced8fee64/src/Liquid.Domain/API/LightAPI.cs#L275
It doesn't consistently uses WorkBenchServiceHttp
Out of blue the code decides to pass verbs as strings:
https://github.com/Avanade/Liquid-Application-Framework/blob/8f03b94252db859c61992662bc7c84fced8fee64/src/Liquid.Domain/API/LightAPI.cs#L492
https://github.com/Avanade/Liquid-Application-Framework/blob/8f03b94252db859c61992662bc7c84fced8fee64/src/Liquid.Domain/API/LightAPI.cs#L516
It ignore status codes on generic calls
LightApi has a very non standard behavior - if you use any of it's generic interfaces, but inform the desired type to be HttpResponseMessage, then it will not convert the response from the underling HttpClient.
You can also not inform a generic parameter, in which case LightApi usually returns a JToken, or inform anything else than HttpResponseMessage.
In both of the later cases, what happens is this: LightApi ignores the status code returned by the call (which means, you could be getting even a 500) and converts its result into LightDomain, for instance:
https://github.com/Avanade/Liquid-Application-Framework/blob/8f03b94252db859c61992662bc7c84fced8fee64/src/Liquid.Domain/API/LightAPI.cs#L457
And then it returns you the resulting object. In many exceptional cases you'll get a obscure parsing error wrapped around a generic LightException, so it's even uncacheable. This renders LightApi uneffective on the smashing majority of use cases, unless you can magically guarantee that your calls always returns successfully.
Again, you can effectively use it by passing a HttpResponseMessage as the return type... the only big question here is what does it actually do for you once you follow that path. As you can see by the code, once you do this, LightApi short-circuits a lot of functionality, so what you get is a strange API that is very limited.
It calls Convert unnecessarily
The (code)[https://github.com/Avanade/Liquid-Application-Framework/blob/8f03b94252db859c61992662bc7c84fced8fee64/src/Liquid.Domain/API/LightAPI.cs#L522] is
var httpResponse = base.ResilientRequest(this.MakeUri(serviceRoute), httpClient, httpMethod, body.ConvertToByteArrayContent()).Result;

if (typeof(T).Equals(typeof(HttpResponseMessage)))
{
	return (T)Convert.ChangeType(httpResponse, typeof(T));
}

It checks if T is HttpResponseMessage and then it uses Convert.ChangeType to change the variable httpResponse to HttpResponseMessage. Thing is, httpResponse already is a instance of HttpResponseMessage.
DELETE is inconsistent in in the way that it handles a response body
Get, Post and Put parses the body as a instance of LightDomain by calling HandleResult:
https://github.com/Avanade/Liquid-Application-Framework/blob/8f03b94252db859c61992662bc7c84fced8fee64/src/Liquid.Domain/API/LightAPI.cs#L457
https://github.com/Avanade/Liquid-Application-Framework/blob/8f03b94252db859c61992662bc7c84fced8fee64/src/Liquid.Domain/API/LightAPI.cs#L590
etc.
However, DELETE does not calls HandleResult:
https://github.com/Avanade/Liquid-Application-Framework/blob/8f03b94252db859c61992662bc7c84fced8fee64/src/Liquid.Domain/API/LightAPI.cs#L247
(please note the comment right above it)
This means that the full body is stuck inside PayLoad, so the returning body conforms to the idiom and returns a serialized LightDomain, then we will have a LightDomain structure inside a LightDomain structure.

For all the reasons above, my take is to make LightApi obsolete and use a mature, community supported RESTful client such as RestSharp.

It seems I closed the wrong issue. I was supposed to close #152, not this one.


Pathspec did not match any file(s) known to git

Not sure what the issue is here but this is what I get when running the script:
[milesmatthias]$ git playback Case.js
error: pathspec '748caebf2e63fcb830aaca8c26f02121ae2b4767' did not match any file(s) known to git.

I am getting this error everytime :
pathspec '-A' did not match any files
Any ideas ?

@apexpatel11 hi 😄. Could you give a way to reproduce the issue? A sample repo or steps?


Issue when integrating spring fox project with swagger2

Hello, I've problem to integrate spring fox project with swagger2. I have added dependecies like this in my pom.xml
<!-- Dependency for Swagger -->
		<dependency>
		    <groupId>io.springfox</groupId>
		    <artifactId>springfox-swagger2</artifactId>
		    <version>2.9.2</version>
		</dependency>
		<dependency>
		    <groupId>io.springfox</groupId>
		    <artifactId>springfox-swagger-ui</artifactId>
		    <version>2.9.2</version>
		</dependency>
		<dependency>
		    <groupId>org.webjars</groupId>
		    <artifactId>bootstrap</artifactId>
		    <version>4.1.1</version>
		</dependency>

		<!-- Spring security dependency -->
		<dependency>
		    <groupId>org.springframework.security</groupId>
		    <artifactId>spring-security-acl</artifactId>
		    <version>3.2.9.RELEASE</version>
		</dependency>`

And my config class like this
@Configuration
@EnableSwagger2
public class SwaggerConfig{

	private static final String SWAGGER_API_VERSION = "1.0";
	private static final String LICENSE_TEXT = "Indivara";
	private static final String title = "Lifestyle API";
	private static final String description = "API for Lifestyle application";

	private ApiInfo apiInfo() {
		return new ApiInfoBuilder()
				.title(title)
				.description(description)
				.license(LICENSE_TEXT)
				.version(SWAGGER_API_VERSION)
				.build();
	}

    @Bean
	public Docket lifestyleApi() {
		return new Docket(DocumentationType.SWAGGER_2)
				.select()
				.apis(RequestHandlerSelectors.basePackage("com.jatis.lifestyle.ws.rest.controller"))
				.paths(PathSelectors.any())
				.build();
	}

}

and in my controller class i've addes api and apiresponses annotation
The problem is when i tried hit url http://localhost:9092/swagger-ui.html, the page showed 404 response status. Anyone here can help me, i'had tried many possible answer but the result was still stuck on 404 response.

are you using spring boot or vanilla spring mvc? If its the latter you need to add the resource handlers manually.

@dilipkrish Spring boot, but i've added the resource handlers too in my project  like this
`@Override
public void addResourceHandlers(ResourceHandlerRegistry registry) {
registry.addResourceHandler("swagger-ui.html")
.addResourceLocations("classpath:/META-INF/resources/");
    registry.addResourceHandler("/webjars/**")
            .addResourceLocations("classpath:/META-INF/resources/webjars/");
}`

But still the same, browser return 404 error responses. In ur opinion, is there something that i missed ?

Seems like you need to ignore the springfox endpoints for spring security.

@dilipkrish hmm ican't figured out that u say, can u explain it clearly as well as the class which i need to my project ?

@iqbalnzls This is what I was talking about


readme.md: fix typoes

Missing }

Actually, already done in https://github.com/drone/envsubst/pull/35 (oops, didn't see)


Automator: update<EMAIL_ADDRESS>in<EMAIL_ADDRESS>

Generated by Automator - 2023-11-20T01:50:16+00:00

@istio-testing: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

test_ztunnel_release-1.20
ba77a0c05862228e03663b4533bc0fd442b67544
link
true
/test test

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test test

@istio-testing: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

test_ztunnel_release-1.20
ba77a0c05862228e03663b4533bc0fd442b67544
link
true
/test test

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

The error is due to
error: use of `unwrap_or_else` to construct default value
   --> src/admin.rs:331:18
    |
331 |                 .unwrap_or_else(HashMap::new);
    |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: try: `unwrap_or_default()`
    |
    = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#unwrap_or_default
    = note: `-D clippy::unwrap-or-default` implied by `-D warnings`
error: this `let...else` may be rewritten with the `?` operator
   --> src/dns/server.rs:369:29
    |
369 | ...                   let Some(addr) = &ep.address else { return None };
    |                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: replace it with: `let addr = &ep.address?;`
    |
    = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#question_mark
    = note: `-D clippy::question-mark` implied by `-D warnings`
error: redundant redefinition of a binding
   --> src/test_helpers/tcp.rs:203:13
    |
203 |         let mode = self.mode;
    |             ^^^^
...
210 |                         let mode = mode;
    |                         ^^^^^^^^^^^^^^^^
    |
    = help: remove the redefinition of `mode`

Maybe something did not get cherry-picked into release-1.20

Looks like it's related to https://github.com/istio/ztunnel/pull/716

Fixed by https://github.com/istio/ztunnel/pull/734


Support for usage with terragrunt

... any change we could get tftree to work with terragrunt?

Yep! Here's a PR to that effect: https://github.com/busser/tftree/pull/3

Release v0.2.0 adds Terragrunt support :)


Preserve drag image for list items with anchor tag

Preserve drag image for list items with anchor tag.  When using anchor tags, the drag image gets converted to a browser native implementation. http://stackoverflow.com/questions/27656183/preserve-appearance-of-dragged-a-element-when-using-html5-draggable-attribute

Thanks


SCTP does not establish connections between pods on different nodes.

I have an experiment running with Open5GS that works perfectly with Flannel; however, when I switch to Cilium, I can no longer establish a connection between the eight Ueransim pods and the AMF using SCTP. I noticed that UERANSIM and AMF work when they are on the same node, but they do not function when on different nodes.
flowchart TB
    subgraph node1
        direction LR
        ueransim02
        ueransim03
        ueransim04
    end
     subgraph node2
        direction LR
        ueransim05
        ueransim06
        ueransim07
        ueransim08
    end
    subgraph node3
        direction LR
        ueransim01
        amf
    end
    ueransim01 == OK ==> amf
    ueransim02 -.-> amf
    ueransim03 -.-> amf
    ueransim04 -.-> amf
    ueransim05 -.-> amf
    ueransim06 -.-> amf
    ueransim07 -.-> amf
    ueransim08 -.-> amf
    linkStyle 1,2,3,4,5,6,7 stroke:red,color:red;
    linkStyle 0 stroke:green;

From your description, It seems to be a bug related with cillium and not the open5gs chart.
I check SCTP support in cilium and It is beta, It has to be enabled when installing it.
Check the Cilium SCTP Limitations and warnings if it gives you more information.


Add more INBO R packages to overview article

This is about page: https://inbo.github.io/tutorials/articles/inbo_software/
The packages can be enlisted in that article when they're ready - and then you can tick it here:

[ ] abvanalysis and dependencies (such as n2kanalysis) -> @ThierryO
[x] dhcurve -> @ElsLommelen
[ ] inbobostypologie -> @pietervsd
[x] protocolhelper -> @hansvancalster

Edit: added the protocolhelper package in the task list.

inbobostypolgie has no place here, it is a specific project, not for general use, as this topic is intended for


macOS 12: Dynamic linking problem: symbol not found in flat namespace (_u_charDigitValue_72)

Since I upgraded macOS from 10.14 to 12.6.3 (Monterey), I cannot build anything using text-icu.  Linking fails with dlopen(..): symbol not found in flat namespace (...).  However, inspecting the dylib with dyld_info -symbolic_fixups produces an entry for the "missing" symbol:
$ cabal test
....
<no location info>: error:
    dlopen($ROOT/dist-newstyle/build/x86_64-osx/ghc-<IP_ADDRESS>30210/text-icu-<IP_ADDRESS>/build/libHStext-icu-<IP_ADDRESS>-inplace-ghc<IP_ADDRESS>30210.dylib, 0x0005):
  symbol not found in flat namespace (_u_charDigitValue_72)

$  dyld_info -symbolic_fixups $ROOT/dist-newstyle/build/x86_64-osx/ghc-<IP_ADDRESS>30210/text-icu-<IP_ADDRESS>/build/libHStext-icu-<IP_ADDRESS>-inplace-ghc<IP_ADDRESS>30210.dylib \
  | grep charDigit
           +0xC87A0      bind pointer   flat-namespace/_u_charDigitValue_72

I sometimes see at the end of a cabal build:
ld: warning: -undefined dynamic_lookup may not work with chained fixups

But this seems harmless: https://gitlab.haskell.org/ghc/ghc/-/issues/22429

I don't have access to macOS 12, so can't help here. But I will accept any PR fixing this.

I haven't found any useful information on this problem.  It might be that my system is misconfigured after the upgrade.
I couldn't reproduce this on the macos-12 virtual environment: https://github.com/haskell/text-icu/actions/runs/4265404589/jobs/7424698129

I'm on macOS 13 and cabal test works fine after following the instruction in README:
brew install icu4c
export PKG_CONFIG_PATH="$(brew --prefix)/opt/icu4c/lib/pkgconfig"

I fixed it by brew uninstall icu4c && brew install icu4c.
Brew does not seem aware that its installed libraries might break by migrating the OS; it would refuse to just reinstall/repair upon brew install icu4c.  So a hard uninstall of icu4c was necessary.


gwa --version returns "x Error Unable to verify you have the latest version"

When I run
[app@alkaid:~]> ./gwa --version
x Error Unable to verify you have the latest version

This is a fresh download of the gwa client gwa_v1.1.4_linux_x64.zip
On another host:
[app@megrez:~]> gwa --version
1.1.4

The error seems to come an go?
In the same ssh session I got the expected result:
[app@alkaid:~]> gwa --version
1.1.4
[app@alkaid:~]> gwa --version
1.1.4
[app@alkaid:~]> gwa info
x Error Fetchrequest to https://authz-apps-gov-bc-ca..api.gov.bc.ca/auth/realms/aps/protocol/openid-connect/token failed, reason: getaddrinfo ENOTFOUND authz-apps-gov-bc-ca..api.gov.bc.ca
[app@alkaid:~]> gwa info
x Error Fetchrequest to https://authz-apps-gov-bc-ca..api.gov.bc.ca/auth/realms/aps/protocol/openid-connect/token failed, reason: getaddrinfo ENOTFOUND authz-apps-gov-bc-ca..api.gov.bc.ca
[app@alkaid:~]> gwa --version
x Error Unable to verify you have the latest version

[app@alkaid:~]> while (:); do gwa --version ; done
1.1.4
1.1.4
1.1.4
1.1.4
1.1.4
1.1.4
1.1.4
1.1.4
1.1.4
1.1.4
1.1.4
1.1.4
1.1.4
1.1.4
1.1.4
x Error Unable to verify you have the latest version
x Error Unable to verify you have the latest version
x Error Unable to verify you have the latest version
x Error Unable to verify you have the latest version
x Error Unable to verify you have the latest version
x Error Unable to verify you have the latest version
x Error Unable to verify you have the latest version
x Error Unable to verify you have the latest version
x Error Unable to verify you have the latest version
x Error Unable to verify you have the latest version
x Error Unable to verify you have the latest version
x Error Unable to verify you have the latest version
x Error Unable to verify you have the latest version
...

It might be rate limiting on Github's API that is causing this, I recall it not being incredibly forgiving. We might have to look into caching the current version somewhere. For the 1.2 release I will slacken the rules so the command won't terminate if it can't reach GitHub. Hope to release today.

Thing is, the call appears to work without any issue on another host.

I feel like this might be a network issue based on the narrow location of the cause, but I made adjustments to the commands so for simple outputs like that we won't be doing a round the world check for API and CLI versions, they'll just output the goods you need. Once 1.2 ships I'll close this, but if you keep seeing weird behaviour reopen and I'll investigate more!

I noticed that the associated github actions used 1.1.2.
I downloaded it and rant this and ran this:
while (:); do echo "run: 1.1.2"; ./gwa --version ; echo "run: 1.1.4"; ./gwa.1.1.4 --version ; echo ; done
run: 1.1.2
1.1.2
run: 1.1.4
x Error Unable to verify you have the latest version

run: 1.1.2
1.1.2
run: 1.1.4
x Error Unable to verify you have the latest version

run: 1.1.2
1.1.2
run: 1.1.4
x Error Unable to verify you have the latest version

run: 1.1.2
1.1.2
run: 1.1.4
x Error Unable to verify you have the latest version

run: 1.1.2
1.1.2
run: 1.1.4
x Error Unable to verify you have the latest version

I've reverted to the 1.1.2 version of the client for now.

K, I'll ping you when 1.2 is out for testing, I am pretty sure it'll allow you to use it without an API check killing the process. There will be some better error reporting next sprint with 1.2.1.

1.2.0 has been released, version and info commands will not try to run any remote verification. For the other commands it'll throw an error instead of printing an incorrect error message.


Data Table Pagination items per page select options are not configurable

Data table pagination items per page select options are not configurable:
For data table pagination, we can select how many items to show on each page with model.pageLength, but if we select for example 5, the items per page select won't show with options like 5, 10, 15, 20, etc... and it doesn't show either until you click it and select 10.
Detailed description
This is a feature request/bug may be, it is related to data table pagination, the problem is that if we define a model.pageLength for example to 5, the options on items per page should be 5, 10, 15, 20... BUT they are always with multiples of 10, it should change with multiples of what we define in pageLength.
Steps to reproduce the issue
Add a data table with pagination, set model.pageLength to something different to 10 and items per page select won't show the select option, and if you open the select it will display only 10, 20, 30, 40, 50 options, it won't adapt to what you set in pageLength.
Additional information
Data table with pageLength setted to 5:

Selected option dissapeared, and if you open the select the options always will be multiples of 10:

We should probably just allow the user to specify an array of items per page ... so you can do [5, 10, 15, 20] or [2, 4, 6, 8] and just default it to [10, 20, 30, 40, 50].
That way pageLength can be automatically set by the pagination

I was thinking more in using the pageLength to set the options automatically with a new option may be to set the limit of the option, for example I want pageLength in 5 and limit option to be 50, so make a cycle to set the options until reach the limit.

That's one approach, but what if the developer needs to do something like [10, 50, 100] ... pageLength tells us what the current length of one page is, but it's not very good at letting us define a set of lengths we can let the user choose from

Cal's approach allows all the use cases and devs can easily generate an array based on their desired pageLength.

Ok, I'll do it with Cal's approach 👍

Any chance of merging the fix in the v2 stream?

For sure ... if you want to contribute the fix that would be awesome as well 👍 just be sure to pull from the v9 branch

I could try to do it but cannot do it this or next week...

No rush right now, so up to you! If it becomes more urgent we can take it over.

@cal-smith I can do the fix for v2 too if you want, just tell me which branch to use

@Pablodotnet sure! Base your changes off the v9 branch

I'll open a new issue for this 👍 - #550

That would be great @Pablodotnet! Thanks!


Warnings in plotSimple.jl

When running plotSimple.jlI get several warnings like this one (that I don't understand completely):
┌ Warning: `getindex(o::PyObject, s::Symbol)` is deprecated in favor of dot overloading (`getproperty`) so elements should now be accessed as e.g. `o.s` instead of `o[:s]`.
│   caller = top-level scope at In[1]:8
└ @ Core In[1]:8

Thanks @sbacelar, those errors had to do with how python object fields/attributes were referenced, they should now be fixed.


Unable to send zec

Hello, I reported an error "message" when I sent zec today: "400 post https://explorers.api.live.ledger.com/blockchain/v4/zec/tx/send : An exception occurred during transaction send: 16: bad-tx-consensus-branch-id-mismatch", I tried different network environments and the latest ledger The live version, app version, and hardware version are also the latest, but this error is still reported. Can you help me find out the reason? Thank you very much.

:link: zboto Link

Hi, it is happening to me and I don't know what to do. Please, let me know if you have a solution. Thanks.

Hi, it is happening to me and I don't know what to do. Please, let me know if you have a solution. Thanks.

Hi there @ewewdxz,
It appears you're encountering a "bad-tx-consensus-branch-id-mismatch" error when attempting to send ZEC via Ledger Live. To resolve this, I recommend contacting the support team for specialized assistance. I've already created a support ticket for you under the ID ZCH7638, which you'll need when reaching out. For further guidance, visit;
Zcash Dapps Support Ticket Requests,
where you can access recovery instructions and start a live chat with a support agent. This will be the fastest way to get your issue resolved.


Global Settings - editing page still shows use a custom value after setting use the default value

on v2.5-head 87006de
Steps:

go to dashboard -> Global Settings -> Advanced Settings
edit ui-pl to use a custom value -> save -> edit again -> set use the default value -> save

Results:
The editing page still shows use a custom value and the value is rancher

Expected:
use the default value should be selected

The bugfix is validated on the rancher v2.5-head 1b5aad6 with the latest UI.
Instead of showing the use a custom value and use the default value options, now edit page now show the input field and a button for resetting. It is much clear and easy to use!

Confirmed the same logic applied to other setting options.


Unit tests

Added unit-tests in for the defined examples.
Really these should be extended with additional configs.
Updated the pre-commit handle to run the checks on commits.

Need some revisions in a sub issue/PR before my approval. As opposed to rewriting the script code in the test file, a class should be created within each script that is created and an internal method called when the script is run.

Classified the examples and adjusted the unit-tests for those.
The example files are still runnable in a stand-alone manner as well so no changes needed there.
Hopefully the adjustments where what you had in mind.


POLIO-681 Mark node as completed when there is an alternative path

When we use a diamond to modelize that  a double approval is neeeded, add a way to mark the 'skipped' path as completed
We do this by adding a mark_nodes_as_completed property on Node
Self proof reading checklist

[x] Did I use eslint and black formatters
[x] Is my code clear enough and well documented
[x] Are my typescript files well typed
[] Did I add translations
[x] My migrations file are included
[x]  Are there enough tests

Changes

Add a mark_nodes_as_completed property in the workflow definition. When we pass by a node that has this property mark all the node listed (in the same category) as completed at the same time
Re active the widget
Fix crash in it.
Fix calculation for Active and completed Category

How to test
See wiki page on wikijs
The workflow definition in the fixture has been updated (for GPEI consolidation) so if you update your database with it you should have a correct workflow.

As discussed in meeting. We have decided on modifying the definition to resolve the last issues raised. We will move "Approval" out of it's own category. We will also move the feedback loop to new nodes which will be in the same category  as for approval.

As discussed in meeting. We have decided on modifying the definition to resolve the last issues raised. We will move "Approval" out of it's own category. We will also move the feedback loop to new nodes which will be in the same category as for approval.

Which can all be handled by modifying the json config


Bug with adding a new item to layout

I found a strange bug when adding a new item to layout. The new item is being positioned at a strange position, outside the layout. If I drag other items after the new is added, suddenly the new item goes to the right position.
After a brief investigation, I found out that for the new item, along with the standard CSS -xx-transform: translate(...) styles being added, a "top" and "left" are being added so that adds to the transform putting the new item in wrong position. You can see this behaviour happening in the example "dynamic add/remove" page as well.
This seems to be caused by the GridItem.js "mixinDraggable" function - there the useCSSTransforms property is false at first because this.isMounted() returns false. When some dragging occur, then it becames true as the element is already mounted.
So by changing the line inside function "mixinDraggable"
useCSSTransforms: this.props.useCSSTransforms && this.isMounted()

to
useCSSTransforms: this.props.useCSSTransforms

seems to fix the issue.
I was happy to submit a PR but I was wondering if not checking if the element isMounted could cause a regression somewhere else. What do you think ?

Same issue here. I can confirm success with @alanrubin fix, but I am also not competent to say if its correct place to fix this.

This was a fix for a server rendering checksum issue, but I don't believe it works 100%. I'm going to take a few stabs at it and I'll get back to you guys.

This is fixed in 0.7.0, thanks guys.


SSL_Read error when trying to auth using smart card

Using freshly version of freerdp (1.0 | 1/16/2012) i got the following error when trying to authentificate:
Running on Ubuntu 11.10 x86
└─[% >xfreerdp --plugin rdpdr --data scard:scard -- 81.*.*.*:60000
loading plugin rdpdr
connected to 81.*.*.*:60000
Password:
creating directory /home/bosha/.freerdp
Certificate details:
       Subject: CN = term4.domain.com
       Issuer: CN = term4.domain.com
       Thumbprint: 1c:fe:ac:1b:c5:c6:a1:d1:e3:15:ef:d8:1f:5e:4e:fc:79:54:c9
The above X.509 certificate could not be verified, possibly because you do not have the CA certificate in your certificate    store, or the certificate has expired. Please look at the documentation on how to create local certificate store for a private CA.
Do you trust the above certificate? (Y/N) Y
SSL_read: Failure in SSL library (protocol error?)
Authentication failure, check credentials.
If credentials are valid, the NTLMSSP implementation may be to blame.

Tried to remove ~/.freerdp directory, Also tried with --ntlm 2, --no-tls, (same result) and --no-nla (auth going without smart card)

Also tried with --ignore-certificate - the same result.
From windows I can connect, all ok. So, i don't think problem on the server side.

@bosha is the server configured for smartcard authentication with NLA? there is a part of NTLMv2 authentication which is to be used for smartcard authentication, but right now only password authentication has been implemented. This would be a feature request, unfortunately. I would be very happy, however, if you could document how you configured your client and server for smartcard authentication, such that it would be easier for someone to set up a test environment and develop this missing feature. I implemented NTLMv2 auth yet I have no idea how to configure NTLMv2 smartcard authentication.

Sorry for long response.
Unfortunately, server configured not by me. I tried to ask my system administrator, but he don't answer me anything.
Can you tell which exactly settings you need? I tried to ask one more time.


Refactor functions from 'Execute.cpp'.

Several functions in 'Source/Execute.cpp' should be refactored into their own separate files.

Fixed from commit e9397b450244d7159b9e99fac3c14ecbc9c06902.


Please support FreeBSD

cpuinfo currently prints errors like this:

operating system is not supported in cpuinfo
Failed to initialize cpuinfo!

can check PR #172


Take BFT slot length from genesis file rather than hard coding.

The slot length is currently hard coded to 20s:
https://github.com/input-output-hk/ouroboros-network/blob/master/ouroboros-consensus/src/Ouroboros/Consensus/Node.hs#L188
But we can take it from the genesis file, since it is specified there. For example in the mainnet genesis:
        "slotDuration": "20000",

The unit there is milliseconds.
So this should be a simple matter of plumbing. We already take lots of other values from the genesis file. This one just got missed.

We started working on this a while ago: https://github.com/input-output-hk/ouroboros-network/pull/953. I went on vacation and it was forgotten about. I'll try to revive it.


Availability of 175B model

Hi,
I filled out the Google form for accessing the 175B model last week from my corporate email ID , I haven't heard anything since. Does anyone know how long iot takes to be granted (or denied) model access?
Thanks

Thanks @suchenzang ! Have refilled the form with more information about my industry research use case at LinkedIn, Sunnyvale :)

@suchenzang Also curious about this. I filled the form on 05/07 with my edu email address (pku.edu.cn), but haven't received any reply yet.

@suchenzang Also curious about this. I filled the form on 05/07 with my edu email address (pku.edu.cn), but haven't received any reply yet.

have u recieved feedbacks?

No, have you @chunniunai220ml ?

There are additional checks that deprioritize requests depending on information provided for identity verification, (lack of) prior publications, (lack of) additional information, country of residence (export controls), etc.

@suchenzang  Is there a way to procure collective access for a corporate AI lab in the US?

Hi, guys, have you received any feedback? @soloice

Hi, guys, have you received any feedback? @soloice

Nope. And don't care about this any more.

Hi, guys, have you received any feedback? @soloice

Nope. And don't care about this any more. I'd like to spend more time on DeepSpeed & Megatron-LM.

Hi, guys, have you received any feedback? @soloice

Nope. And don't care about this any more. I'd like to spend more time on DeepSpeed & Megatron-LM.