updateHostsFile.py:: revert encoding

@funilrys @StevenBlack please apply this revert cause final PR #520 after lastest changes unable download from somewherewhocares.org.
This PR revert encoding section to WORKING for me code.
Regards
Tomasz

Looks like Travis CI freak out LIKE after lastest changes with #520

STOP I did those change for a reason .... Let me review it personally once back home @StevenBlack. I tested #520 over 4 networks 2 countries (France amd Germany) and 5 computers (32 bits and 64 bits) so I do not understand this.
Also not that this reversion is really bad cause this do nit respect original file structure if we have more that 1 '#' at the end of a line.
Plus there is a reason that I check for tabulation before space.

@StevenBlack just give a quick look at the tests and they explain my changes by themselves ...

@funilrys it's all-good.  I'm not reverting anything 😄.
Just need to figure out what's up with this one provider.

@StevenBlack @funilrys when I using final code (not reverted) then I cannot download from somweherewhocares and hphosts.
After revert this, downloading and creating hosts file went fine, so don't be angry at me.

I was not angry it's just the morning out of town because of personal reason 😅 sorry if I offensed you @FadeMind ...
What do you got as exception ? 🤔

[fademind@manjaro hosts]$ python updateHostsFile.py -a -n
Traceback (most recent call last):
  File "updateHostsFile.py", line 1485, in <module>
    main()
  File "updateHostsFile.py", line 192, in main
    merge_file = create_initial_file()
  File "updateHostsFile.py", line 652, in create_initial_file
    write_data(merge_file, curFile.read())
  File "/usr/lib/python3.6/codecs.py", line 321, in decode
    (result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xf1 in position 17997931: invalid continuation byte

Then the problem is not the function you're reverting ...

Previous post is basic of final code (merged in #520 ) When I revert decode to Your first commit in #520, then all is good.

@funilrys  SIMPLE 😆
Changing at 1165 to
for separator in [' ', '\t']:

resolved issue.
CC @StevenBlack  @funilrys

Please take a look at the tests ... That doesn't resolve anything ...

Okay I'm back home let me check everything ...

I used original file and switch to for separator in [' ', '\t']:
and all went fine:
[fademind@manjaro ~]$ cat ~/bin/uhf
#!/usr/bin/env bash
cd $HOME/GitHub/mnjpkgbuilds/00-HSTS.EXT/
python updateHostsFile.py -a -c -r -f

[fademind@manjaro ~]$ uhf
Updating source data/add.Risk from https://raw.githubusercontent.com/FadeMind/hosts.extras/master/add.Risk/hosts
Updating source data/someonewhocares.org from http://someonewhocares.org/hosts/zero/hosts
Updating source data/CoinBlockerLists from https://raw.githubusercontent.com/ZeroDot1/CoinBlockerLists/master/hosts_browser
Updating source data/adaway.org from https://raw.githubusercontent.com/AdAway/adaway.github.io/master/hosts.txt
Updating source data/tyzbit from https://raw.githubusercontent.com/tyzbit/hosts/master/data/tyzbit/hosts
Updating source data/StevenBlack from https://raw.githubusercontent.com/StevenBlack/hosts/master/data/StevenBlack/hosts
Updating source data/add.2o7Net from https://raw.githubusercontent.com/FadeMind/hosts.extras/master/add.2o7Net/hosts
Updating source data/UncheckyAds from https://raw.githubusercontent.com/FadeMind/hosts.extras/master/UncheckyAds/hosts
Updating source data/mvps.org from http://winhelp2002.mvps.org/hosts.txt
Updating source data/add.Dead from https://raw.githubusercontent.com/FadeMind/hosts.extras/master/add.Dead/hosts
Updating source data/yoyo.org from https://pgl.yoyo.org/adservers/serverlist.php?hostformat=hosts&mimetype=plaintext&useip=<IP_ADDRESS>
Updating source data/KADhosts from https://raw.githubusercontent.com/azet12/KADhosts/master/KADhosts.txt
Updating source data/Badd-Boyz-Hosts from https://raw.githubusercontent.com/mitchellkrogza/Badd-Boyz-Hosts/master/hosts
Updating source data/malwaredomainlist.com from http://www.malwaredomainlist.com/hostslist/hosts.txt
Updating source data/Spotify-Ad-free from https://raw.githubusercontent.com/CHEF-KOCH/Spotify-Ad-free/master/Spotifynulled.txt
Updating source data/CoinBlockerList from https://raw.githubusercontent.com/ZeroDot1/CoinBlockerLists/master/hosts_browser
Updating source data/add.Spam from https://raw.githubusercontent.com/FadeMind/hosts.extras/master/add.Spam/hosts
==><IP_ADDRESS> <IP_ADDRESS><==
==><IP_ADDRESS> <IP_ADDRESS><==
==><IP_ADDRESS> <IP_ADDRESS><==
==><IP_ADDRESS> <IP_ADDRESS><==
==><IP_ADDRESS> <IP_ADDRESS><==
==><IP_ADDRESS> <IP_ADDRESS><==
==><IP_ADDRESS> <IP_ADDRESS><==
Success! The hosts file has been saved in folder
It contains 55,549 unique entries.
Moving the file requires administrative privileges. You might need to enter your password.
Flushing the DNS cache to utilize new hosts file...
Flushing the DNS cache requires administrative privileges. You might need to enter your password.
Flushing the DNS cache by restarting NetworkManager.service succeeded
Flushing the DNS cache by restarting dnsmasq.service succeeded
Flushing the DNS cache by restarting NetworkManager.service succeeded
Flushing the DNS cache by restarting dnsmasq.service succeeded

Yup @FadeMind but we are in a global environment ... if the tests are not passed then it's almost sure that it will fail for everybody if we merge this ...

BUT See here: https://github.com/StevenBlack/hosts/pull/520/commits
![screenshot_20180304_095324](https://user-images.githubusercontent.com/9846948/36943903-e6513fac-1f91-11e8-9695-44a8fc04031f.png
Your lastest commits failed (I only revert/switch this part of code).
@StevenBlack merged this code anyway. Seems to be little switch letters and marks for working fine.

@FadeMind Please take a look the test itself ... it's a Travis CI issue : https://travis-ci.org/StevenBlack/hosts/jobs/348731441

The command "eval git fetch origin +refs/pull/520/merge: " failed. Retrying, 2 of 3.
fatal: Couldn't find remote ref refs/pull/520/merge
The command "eval git fetch origin +refs/pull/520/merge: " failed. Retrying, 3 of 3.
fatal: Couldn't find remote ref refs/pull/520/merge
The command "eval git fetch origin +refs/pull/520/merge: " failed 3 times.
The command "git fetch origin +refs/pull/520/merge:" failed and exited with 128 during .
Your build has been stopped.
/Users/travis/.travis/job_stages: line 166: shell_session_update: command not found

So, thats why is happen.

@FadeMind yes all of those merge issues are by Travis CI ... It did not even start the local code tests ...

Anyway
Diff is trivial:

Works fine for my end.
@StevenBlack please review, test and apply if you like. Thanks for patient ;)

The issue is not about that ...
The real issue is a line like
<IP_ADDRESS>(space)domain(tablulation(s) and spaces)# comments`

I'm writing the fix right now... will send PR before the end of the day ...

@funilrys so, closing this PR now?? :>

To clarify @FadeMind If we apply your patch, the day we encounter
<IP_ADDRESS>(tabulations)domain(spaces)# comments`

We will have the same issue but in the other way so I may have to refactor that function cause I did not even think about that as I did not write the tests for your case...

@StevenBlack @funilrys  closing this PR cause #527 pending...


Use shared_ptr holder for Problem

@B1ueber2y Without this fix, the following code results in a segfault for me:
ba = pycolmap.BundleAdjuster()
pb = ba.problem
del pb

The shared pointer returned by BundleAdjuster.problem is lost if pyceres.Problem is not declared to use the shared pointer holder.

Nice catch. Indeed, this should be fixed.


chore: create a new page directory for speakers (WEB-41) #87

I have updated the react component so that it coincide with others


Lotus 1.6

On this PR:

Update to lotus v1.6
Add Exec transactions parameters parser.
/block endpoint: Add detection of 'creation & funding' of a multisig account when calling the Exec method on the init actor.

is our CI testnet down?
go test -race ./rosetta/tests
--- FAIL: TestNetworkList (0.00s)
    rosetta_test.go:46: Failed to get NetworkList: Post "http://localhost:8081/network/list": dial tcp <IP_ADDRESS>:8081: connect: connection refused


[ pt ] Layout HTML page

[ ] header -> title, motivational quote
[ ]  aside -> born date input, life expectancy in years
[ ]  aside -> indicators
[ ]  section -> main grid
[ ]  footer -> give me an star on GitHUb and other links
[ ] Give the page minimal style


Autoscrolling options appear on print

Describe the bug
When printing within Firefox, the Autoscrolling add-on options are appended.
To Reproduce
Steps to reproduce the behavior:

Navigate to menu > Print
Preview displays Autoscrolling add-on options page appended to end of document

Expected behavior
Autoscrolling add-on options page should not appear on any webpage print previews, unless that is the page one is intending on printing.
Screenshots
Google.pdf
Desktop (please complete the following information):

OS: Windows 10 Enterprise
Browser Firefox 63.0.3
Version: 1.5.9

Additional context
Add any other context about the problem here.

https://stackoverflow.com/questions/355313/how-do-i-hide-an-element-when-printing-a-web-page

@ukozdan
I will take the bugfix in next release 1.5.10.
Relase date: TBA

@ukozdan
I released a new version which is fixed above the bug. 👍
https://addons.mozilla.org/ja/firefox/addon/autoscrolling/


Add JS dependency licenses

Closes #124.
For now, I went with the latest versions of these licenses I could find, but I can switch to trying to match the versions of these dependencies that Empress is currently using (I'm cool with either approach).
Also sorry for the silence lately! I hope I can get back to helping out more with Empress.

Thanks so much @fedarko!

No problem! I forgot to mention this in the commit message, but as you probably noticed I based the structure of the DEPENDENCY_LICENSES file on the LICENSE.md file in Emperor :)

:shipit:


overview: swap highscore with playground

Playground is the more important feature, highscore can be places a bit more in the back
(maybe add events to check my hypothesis?)

done, events added


Type assertion only works if one type is completely assignable to the other

interface Foo {
    a?: string;
    b: string;
}
<Foo>{ a: undefined } // Neither type is assignable to the other

This happens because with respect to property a, Foo is the winner, but with respect to property b, the object literal is the winner (because b is missing). I think what the user expects is for us to mix and match the direction of assignability at all levels of nesting. So if each property is assignable in either direction, the check passes for that property. If the check passes for all the properties, the type assertion is allowed.
This would require work in the spec to add a new symmetric relation "is assignable to or from", which applies itself appropriately to nested types and other nested constructs.

Per issue #2441, we can use this for equality comparisons too.

I don't think we should fix this issue. I think the fix is too costly and complex, and I don't think the issue is serious enough to warrant it.
@mhegazy @ahejlsberg Do you agree?

I agree, I think we can close this one.


TouchRipple breaks when elements are using transform:scale due to incorrect usage of measuring units

[x] I have searched the issues of this repository and believe that this is not a duplicate.
[X] The issue is present in the latest release.

Current Behavior 😯
When elements are inside a transform:scale, both the center ripple and the event origin ripple have incorrect positioning. When scaled up/down, the center ripples are off-center, and the event origin ripples are in incorrect positions as well.
Expected Behavior 🤔
The position of ripple shouldn't change based on scale.
Steps to Reproduce 🕹
Steps:

Put a transform:scale(0.5) style on an outer element.
Click button
Watch it ripple out from a wrong position

Context 🔦
It's a visual bug because you are using incorrect measurement systems. Fix line 202 of TouchRipple.js: If you use ele.clientWidth and ele.clientHeight instead of ele.getBoundingClientRect() it will fix the center ripple issue, e z p z.
The touch ripple issue is there because event position you're using to detect touch origin is using a different measurement system than the ele.getBoundingClientRect() function. You just have to use correct measurement system.
Your Environment 🌎
All environments. You can see this on the react-material-ui demo page as well.

The topic made me think of #20839, but this is different

@E4 I can't find a way to solve the problem. Any idea of a simple solution? Happy to close is as "won't fix" otherwise, it's probably not something we should care about.
Otherwise, we can remove code with this simplification:
diff --git a/packages/material-ui/src/ButtonBase/TouchRipple.js b/packages/material-ui/src/ButtonBase/TouchRipple.js
index a5febe759..c8dc06bfb 100644
--- a/packages/material-ui/src/ButtonBase/TouchRipple.js
+++ b/packages/material-ui/src/ButtonBase/TouchRipple.js
@@ -198,9 +198,9 @@ const TouchRipple = React.forwardRef(function TouchRipple(props, ref) {
         }
       } else {
         const sizeX =
-          Math.max(Math.abs((element ? element.clientWidth : 0) - rippleX), rippleX) * 2 + 2;
+          Math.max(Math.abs(rect.width - rippleX), rippleX) * 2 + 2;
         const sizeY =
-          Math.max(Math.abs((element ? element.clientHeight : 0) - rippleY), rippleY) * 2 + 2;
+          Math.max(Math.abs(rect.height - rippleY), rippleY) * 2 + 2;
         rippleSize = Math.sqrt(sizeX ** 2 + sizeY ** 2);
       }

Running into this as well. New to MUI, is there a workaround @E4 @oliviertassinari is there a workaround you could suggest?

Still a problem, if you have a workaround, i will take it ! Thanks in advance

Having this issue on our project as well.  This bug is very visible to our users, so it would be great if this can be re-opened and re-investigated.


Not encoding data in the secret AWS SQS

In the documentation, in https://keda.sh/docs/2.0/scalers/aws-sqs/ its mentioned to store AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY directly without encoding, this works with KEDA. But if I want to use the same secret say with a POD by injecting the secret data and use as env variable as mentioned here, due to default behavior it tries to decode the secret data. This causes inconsistency since we are not encoding the key and secret.
Expected Behavior
To be consistent with Kubernetes practices
Actual Behavior
Not consistent with Kubernetes practices

I'm updating the docs as this should not be the case: https://github.com/kedacore/keda-docs/pull/263
Can you share what you are seeing at runtime or is this purely when reading the docs?

@tomkerkhove its working for us. The problem was from our side earlier we creating secrets using YAML, when created secret from file it worked. Thanks for the quick support!!


fix(service): update vercel api paths

We work with the Vercel API at work as a partner of theirs. They move fast and often have many versions in flight at once haha.
The paths you had configured weren't working anymore. These seemed to do the trick for me :+1:

Thx. Seems good to me drop teamId. But I see v11 of Get a Single Deployment in official vercel docs.

Okay I've removed the teamId stuff from a few more places then, and also updated the readme a bit.
I'm relatively new to strapi and this was the first plugin i'd tried to use. I wasn't aware at first that you can create all those directories under /admin/src/.. in order to customize the frontend yourself. Took me a while to figure out haha so I added a little not here in the readme for future newbies.

Could this be merged @f3l1x  ?

Bumped v0.0.5. Thank you


Add media query breakpoints

We need some of these to be standard so maybe it would be good to add them here?

This is a normalizer, the browsers apply default colors to elements. That's why we put the colors here, I think browsers don't apply media queries to unstyled elements. So I don't think we need to define the breakpoints here.

ok - that makes sense - I just figured it would be part of the base style variables


fix text in card course

Great job! Is it possible that instead of the three dots there it will be two rows of text?

Done


Update process.sh

fixed #18 when "docker kill keepalived",  file "/var/run/keepalived.pid" still existed, so the container cannot start.

Hello,
thanks for the pull request. This would fit better in startup.sh script.
Something like
rm -f /var/run/keepalived.pid || true

so the script don't fail if the paid file doesn't exist

closed by #39


Add Health Check Command to NSX plugin

The NSX plugin does not support the HeathCheckCommand. Instead it fakes a PingCommand as a call tot he control cluster status API.
However, we have seen in production that the management server will sometimes find the NSX controller to be behind on ping and that will trigger a HealthCheckCommand which will return with an unsupported command answer.
Once this happens the controller is put into Alert state and will not recover until the management sever is restarted.
In addition, during the investigation, there will be a null pointer exception due tot he fact that the NSX controllers do not live in a pod.
This PR tries to address those two issues.

closing since this should not target master


As a developer, I want only a specific amount of cheeps to be shown to the client

Acceptance Criteria:

Must not return all the cheeps.
A GET request to the specific number of page shall return only that page to the client.
A GET request with no query parameter for a page shall per default return the first page.

til 1. b


Need for an attribute which will force serialization of Datetime properties to ISO regardless of Datetime.Kind

Before I go too far, I want to emphasize, that this is not a bug. This is a request for a feature that would allow me as the developer to force the serialization of System.Datetime to UTC-ISO  (e.g. 2013-01-20T23:00:00Z) regardless of the DateTime.Kind on a property by property basis.
In short, I am proposing a new attribute which will have the same effect as DateTimeZoneHandling.Utc but on a per property basis.
Source/destination types
// Put the types you are serializing or deserializing here
        public class DemoClass
        {
            public string FirstName { get; set; }

            public DateTime DateOfBirthUtc { get; set; }
        }

Source/destination JSON

{
  "FirstName": "some name",
  "DateOfBirthUtc": "2020-06-05T17:19:43.0436834+01:00"
}

Expected behavior
I was expecting to find some way to force the serialization to produce ISO 2020-06-05T16:19:43.0436834Z
Actual behavior
The DateTime was serialized to 2020-06-05T17:19:43.0436834+01:00
Steps to reproduce
// Your calls to Newtonsoft.Json here

            var j = new DemoClass
            {
                DateOfBirthUtc = DateTime.SpecifyKind(DateTime.Now, DateTimeKind.Unspecified)
            };

var json = Newtonsoft.Json.JsonConvert.SerializeObject(j);

This sort of thing is best asked on stackoverflow.com

Hi @bartelink
I was going to but then I am nervous that SFO might shutdown the question under the pretext that the question is too "subjective" or "seeking an opinion".

OK, but you have a genuine need to solve a problem.
First question is whether there is any way to solve that, which is 100% what SO is for.
The subjective bit (whether the overall set of solutions suggest an in-the-box change to the library is warranted in order to enable a cleaner solution) is much easier to consider given a problem (as you've clearly outlined in your question) and one or more solutions.

I'd venture it's in line with a need I outlined in https://github.com/JamesNK/Newtonsoft.Json/issues/1827 / https://github.com/JamesNK/Newtonsoft.Json/issues/2039 - the fact that got studiously ignored suggests to me
a) it's likely not a trivial thing to implement support for overriding policies in this way (the brief scan I did at the time didnt make it look like the code is structured in such a way that such a hook can be added easily)
b) there's no desire to add such features to this lib as we're officially supposed to be in a System.Text.Json world now


Restyled version of AVX with asm2plan9s and asmfmt

Travis is having build issues on OSX, closing this PR.


React native isn't accepting .keystore files.

Need to use .jks extension

Need to use .jks extension

I don't think this is the case. We also create the template with a default .keystore file:
https://github.com/facebook/react-native/blob/main/template/android/app/debug.keystore
What is the problem you faced?

Closing as stale, since there was no reply form the author for months.


Project has no git tags

There are 9 releases on NPM, and none of them have associated tags in git. I did some quick looking through the commit history and I think this is where the versions on NPM line up:

1.0.2: b4ae734
1.0.1: bcacec0
1.0.0: 8cf0109
0.2.2: d99abe2
0.2.1: 898abc2
0.2.0: 19f0c2c
0.1.3: 84ec739
0.1.2: b504bcb
0.1.1: a75efdc
0.1.0: 6370a0d

@joshfriend @	jeffj
Sound good, guys. Thanks a lot. I will create those tags shortly.

As I was unable to link older commits to the release, I did releases only for 1.0.3 and 1.1.0 versions. Though, I feel like these are the only mature ones.


No Content-type found in the mock response

Mock response doesn’t have Content-type in the header , even if we configure it in the mock response.
"response": {
              "status": 200,
               “headers”: {
                    “Content-type” : “application/json”
               },
              "body": —response body—
}

@arunvelusamyd  - Content-type is part of Response Headers and not available as a separate entity. Checkout Readme file as below

test case response should as below -
"response": {
"status": 200,
"headers":{
“Content-type” : “application/json”
},
"body": —response body—
}
Let us know if you still face any issue

Seems like, @arunvelusamyd is fixing this in branch ISS-212-mock-response-content-type (work in progress).
For time being, we can proceed with the PR and unblock Mr Arun. 👍
Note:
1)
This repo https://github.com/authorjapps/api-mock-maker supports all things around mocking and very flexible n easy to create mocks. Also uses JSON DSLs.
We should try to use this for our mocking if we can maintain the mocks separately.
2)
If not, then we can integrate the above code into core module i.e. situations where we want the test-cases to have the mocks in the same JSON file(good for Integration Testing for a Dev-Build or commit-build in Jenkins) as earlier steps. The drawback in this approach is the test-cases become verbose for end-to-end testing as we don't need mocks for black-box testing.
Hence both have merits and pain, let's support both approaches going forward.
Let's do it in a separate ticket 👍 .

@authorjapps  - I don't think we need to fix anything here. Whenever any REST api respond then content comes either part of Header or Body section. Then why do we need to created new entity apart from header/body.
Not sure if I am missing any other information or didn't understand what you are fixing.

@aghorpade
Sorry, it was typo. It was part of response headers. Update my comment.

PR has been merged. This will be available in 1.3.4

Released now.
<dependency>
  <groupId>org.jsmart</groupId>
  <artifactId>zerocode-tdd</artifactId>
  <version>1.3.4</version>
</dependency>

Maven Link: https://search.maven.org/artifact/org.jsmart/zerocode-tdd/1.3.4/jar


Does the react-vertical-timeline-component doesn't work in latest next.js?

"use client";
import React from "react";
import SectionHeading from "./section-heading";
import { VerticalTimeline, VerticalTimelineElement }  from 'react-vertical-timeline-component';
import 'react-vertical-timeline-component/style.min.css';
import { experiencesData } from "@/lib/data";
import { useSectionInView } from "@/lib/hooks";
import { useTheme } from "@/context/theme-context";
export default function Experience() {
const { ref } = useSectionInView("Experience");
const { theme } = useTheme();
return (

My experience

{experiencesData.map((item, index) => (
<React.Fragment key={index}>
<VerticalTimelineElement
contentStyle={{
background:
theme === "light" ? "#f3f4f6" : "rgba(255, 255, 255, 0.05)",
boxShadow: "none",
border: "1px solid rgba(0, 0, 0, 0.05)",
textAlign: "left",
padding: "1.3rem 2rem",
}}
contentArrowStyle={{
borderRight:
theme === "light"
? "0.4rem solid #9ca3af"
: "0.4rem solid rgba(255, 255, 255, 0.5)",
}}
date={item.date}
icon={item.icon}
iconStyle={{
background:
theme === "light" ? "white" : "rgba(255, 255, 255, 0.15)",
fontSize: "1.5rem",
}}
>
{item.title}
{item.location}

{item.description}

</React.Fragment>
))}

);
}
That's the code itself, please help me if you had the same issue, thank you

and that's the appearance

I had the same issue, here is the solution. Refer to this link
https://github.com/stephane-monnot/react-vertical-timeline/issues/166#issuecomment-1748525782

I have also faced this problem and it fixed when I use  visible={true} in VerticalTimelineElement

Thanks so much, Appreciate it bro
Sel, 28 Nov 2023 pukul 20.39 Shirshakkandel @.***>
menulis:

image.png (view on web)
https://github.com/stephane-monnot/react-vertical-timeline/assets/64880594/cbd3be56-8772-4efb-b977-3e1b2d704a49
Yes, i have seen it and fixed it by using inView which is true only when
the experience section is in view.
—
Reply to this email directly, view it on GitHub
https://github.com/stephane-monnot/react-vertical-timeline/issues/171#issuecomment-1829866868,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BD6VY7ZJBKBU3HEIP7IFQ3TYGXSQDAVCNFSM6AAAAAA72TTGU6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRZHA3DMOBWHA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Do we only could host once (for free) in vercel like in github , or we
could host it all the time we need?
Sel, 28 Nov 2023 pukul 20.39 Shirshakkandel @.***>
menulis:

image.png (view on web)
https://github.com/stephane-monnot/react-vertical-timeline/assets/64880594/cbd3be56-8772-4efb-b977-3e1b2d704a49
Yes, i have seen it and fixed it by using inView which is true only when
the experience section is in view.
—
Reply to this email directly, view it on GitHub
https://github.com/stephane-monnot/react-vertical-timeline/issues/171#issuecomment-1829866868,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BD6VY7ZJBKBU3HEIP7IFQ3TYGXSQDAVCNFSM6AAAAAA72TTGU6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRZHA3DMOBWHA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Hello everyone And I have most likely found a solution to this problem!!!!! If you use a typescript, then this comment is for you! Since a javascript is used in the react-vertical-timeline-component folder, and you import a javascript into a typescript, you naturally get an error! Therefore, either you need to recreate the project and use the javascript there, or use other typescript-compatible libraries!

I noticed that the line color also does not show up until another small change shows up and then it shows up momentarily. Anyone faced a similar issue?

I noticed that the line color also does not show up until another small change shows up and then it shows up momentarily. Anyone faced a similar issue?

check z-index in css, and send me a file in github if you don't figure it out, I'll try to help

It needs to be updated to be compatible with Next.js v14.. Downgrading to next.js 13.4.8 and the animations work as expected

 Yes, i have seen it and fixed it by using inView which is true only when the experience section is in view.
` //lib\hooks.ts import { useEffect } from "react"; import { useInView } from "react-intersection-observer";
import { useActiveSectionContext } from "@/context/active-section-context"; import type { SectionName } from "./types";
export function useSectionInView(sectionName: SectionName, threshold = 0.5) { const { ref, inView } = useInView({ threshold: 0.5, }); const { setActiveSection, timeOfLastClick } = useActiveSectionContext();
useEffect(() => { if (inView && Date.now() - timeOfLastClick > 1000) { setActiveSection(sectionName); } }, [inView, setActiveSection]); return { ref, inView, }; } `

This works, but I found that if I navigate away from that section, the timeline is no longer visible. How to make the animation play only once with this implementation?

@jeromeSH26  an easy fix for this would be to parse in additional prop in your VerticalTimeline  element like so:
<VerticalTimeline lineColor="">

And set --line-color under global.css like so:
html {
    --line-color: #fff;
}

This would remove the warning

with nextjs14, got also a warning in the console : app-index.js:34 Warning: Extra attributes from the server: style
this comes as soon as you add a in your page (client site)
seems some code as to be reviewed to be full compliant with Nextjs14. Unfortunatly

with nextjs14, got also a warning in the console : app-index.js:34 Warning: Extra attributes from the server: style
this comes as soon as you add a in your page (client site)
seems some code as to be reviewed to be full compliant with Nextjs14. Unfortunatly

This warning message indicates that there are some extra attributes on the HTML element that Next.js received from the server that it does not recognize. These attributes are added by various browser extensions, plugins, or toolbars that modify the HTML of the page.
This is usually caused by an extension passing these extra attributes with your code when it is executed on the browser trying to interact with the UI, this creates a mismatch between what was rendered on the server and what is rendered on the client.
In your case, the attributes data-new-gr-c-s-check-loaded, data-gr-ext-installed, and cz-shortcut-listen are likely being added by one or more browser extensions that are installed in your browser. These attributes are not recognized by Next.js, which is why it is warning you about them.
You can suppress hydration warnings by setting suppressHydrationWarning to true in the opening tag in which these attributes are being added:

@Shirshakkandel Thank you! I was having an odd issue where my dev server instance wasn't showing my vertical-timeline-element elements, but in my vercel deployed instance of the same codebase was and couldn't figure it out until I tried visible={true} and it fixed it like a charm. Still have no idea how my vercel deployment showed these elements though.

 Yes, i have seen it and fixed it by using inView which is true only when the experience section is in view.
` //lib\hooks.ts import { useEffect } from "react"; import { useInView } from "react-intersection-observer";
import { useActiveSectionContext } from "@/context/active-section-context"; import type { SectionName } from "./types";
export function useSectionInView(sectionName: SectionName, threshold = 0.5) { const { ref, inView } = useInView({ threshold: 0.5, }); const { setActiveSection, timeOfLastClick } = useActiveSectionContext();
useEffect(() => { if (inView && Date.now() - timeOfLastClick > 1000) { setActiveSection(sectionName); } }, [inView, setActiveSection]); return { ref, inView, }; } `

Bro Me and You, We are following the same tutorial from ByteGrad💀

 Yes, i have seen it and fixed it by using inView which is true only when the experience section is in view.
//lib\hooks.ts import { useEffect } from "react"; import { useInView } from "react-intersection-observer"; import { useActiveSectionContext } from "@/context/active-section-context"; import type { SectionName } from "./types"; export function useSectionInView(sectionName: SectionName, threshold = 0.5) { const { ref, inView } = useInView({ threshold: 0.5, }); const { setActiveSection, timeOfLastClick } = useActiveSectionContext(); useEffect(() => { if (inView && Date.now() - timeOfLastClick > 1000) { setActiveSection(sectionName); } }, [inView, setActiveSection]); return { ref, inView, }; }

This works, but I found that if I navigate away from that section, the timeline is no longer visible. How to make the animation play only once with this implementation?

Hey dude there are more elegant ways around this but here is what I came up with:
const [hasAnimated, setHasAnimated] = useState(false);
useEffect(() => {     if (inView && !hasAnimated) {       setHasAnimated(true);     }   }, [inView]);
visible={hasAnimated ? true : inView}

I also faced the same error recently. What I did  ? :
I reinstalled the package by running npm i react-vertical-timeline-component.
I added the following code:

My Education & experience

          {experiencesData.map((item, index) => (

 visible={true} <------  // will show your data
                contentStyle={{
                  boxShadow: "none",

I did a small workaround to fix this problem and keep the cool animation, take a look at my code if you wish :) hope it helps!
https://github.com/roby-codes/robert-kovacs-portfolio/blob/master/src/components/experience.tsx
https://github.com/roby-codes/robert-kovacs-portfolio/blob/master/src/components/vertical-element.tsx

If you don't want to downgrade your next.js version and you're seeing the typescript error, you could bypass the error for deployment by giving the component an 'any' type as a temporary solution:

it is only showing to one side while it should be like this

I'm using vertical-timeline-component for my next.js 14 portfolio site

the image for the icon is not fitting into the icon, i'm getting it as

help me to fix this.
import React from "react";
import styled from "styled-components";
import { VerticalTimelineElement } from "react-vertical-timeline-component";
const Top = styled.div  width: 100%;   display: flex;   max-width: 100%;   gap: 12px;;
const Image = styled.img`
height: 50px;
border-radius: 10px;
margin-top: 4px;
@media only screen and (max-width: 768px) {
height: 40px;
}
; const Body = styled.div
width: 100%;
display: flex;
flex-direction: column;
`;
const Name = styled.div`
font-size: 18px;
font-weight: 600px;
color: ${({ theme }) => theme.text_primary + 99};
@media only screen and (max-width: 768px) {
font-size: 14px;
}
; const Degree = styled.div
font-size: 14px;
font-weight: 500px;
color: ${({ theme }) => theme.text_secondary + 99};
@media only screen and (max-width: 768px) {
font-size: 12px;
}
; const Date = styled.div
font-size: 12px;
font-weight: 400px;
color: ${({ theme }) => theme.text_secondary + 80};
@media only screen and (max-width: 768px) {
font-size: 10px;
}
; const Grade = styled.div
font-size: 14px;
font-weight: 500;
color: ${({ theme }) => theme.text_secondary + 99};
@media only screen and (max-width: 768px) {
font-size: 12px;
}
`;
const Description = styled.div  width: 100%;   font-size: 15px;   font-weight: 400;   color: ${({ theme }) => theme.text_primary + 99};   margin-bottom: 10px;   @media only screen and (max-width: 768px) {     font-size: 12px;   };
const Span = styled.div``;
const EducationCard = ( {education}: {education: any} ) => {
return (
<VerticalTimelineElement
visible={true}
icon={

}
contentStyle={{
display: "flex",
flexDirection: "column",
gap: "12px",
background: "#1d1836",
color: "#fff",
boxShadow: "rgba(23, 92, 230, 0.15) 0px 4px 24px",
backgroundColor: "rgba(17, 25, 40, 0.83)",
border: "1px solid rgba(255, 255, 255, 0.125)",
borderRadius: "6px",
}}
contentArrowStyle={{
borderRight: "7px solid  rgba(255, 255, 255, 0.3)",
}}
date={education.date}
>

{education.school}
{education.degree}
{education.date}

Grade :
{education.grade}

{education.desc}

);
}
export default EducationCard

Hello guys, for people who are doing the portfolio project from ByteGrad or want to use this pkg with nextjs 14.2.5 I solved it by copy pasting the components into my own project and using the latest dependencies versions of ("react-intersection-observer": "^9.13.0") and ("classnames": "^2.5.1"), after doing that and fixing type issues with typescript I could use it normally without any extra code. I created a folder in components and put everything related to this pkg there:

Then in the project I'm using it normally.
"use client";

import SectionHeading from "./section-heading";
import { experiencesData } from "@/lib/data";
import { Fragment } from "react";
import { useActiveSectionInView } from "@/lib/hooks";
import VerticalTimeline from "./VerticalTimeline/VerticalTimeline";
import VerticalTimelineElement from "./VerticalTimeline/VerticalTimelineElement";

export default function Experience() {
    const { ref } = useActiveSectionInView("Experience", 0.4);

    return (

            <SectionHeading>My experience</SectionHeading>
            <VerticalTimeline lineColor="">
                {experiencesData.map((item, index) => (
                    <Fragment key={index}>
                        <VerticalTimelineElement
                            contentStyle={{
                                background: "#f3f4f6",
                                boxShadow: "none",
                                border: "1px solid rgba(0,0,0,0.05)",
                                textAlign: "left",
                                padding: "1.3rem 2rem",
                            }}
                            contentArrowStyle={{
                                borderRight: "0.4rem solid #9ca3af",
                            }}
                            date={item.date}
                            icon={item.icon}
                            iconStyle={{
                                background: "white",
                                fontSize: "1.5rem",
                            }}
                        >

                                {item.title}

{item.location}

                                {item.description}

                        </VerticalTimelineElement>
                    </Fragment>
                ))}
            </VerticalTimeline>

    );
}

If someone is interested, just check out the code on my portfolio repo.
Unfortunately I don't know really how to contribute to fix this issue but from my understanding probably updating react-intersection-observer to version 9 could solve it.


Fix serverless installation mode link

What this PR does / why we need it:
Fix the wrong link of serverless installation
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Release note:

NONE

Thanks @panli889 !
/lgtm
/approve


Feature/tuya panel health sdk

Description
Initialize tuya-panel-health-sdk
Added 4 new health components and corresponding examples
Progess
BarPercent
ScrollRuler
UnLockButton
Add 1 hooks and provide examples
useCountDown
Package

[ ] tuya-panel-animation-sdk
[ ] tuya-panel-api
[ ] tuya-panel-electrician-sdk
[ ] tuya-panel-ipc-sdk
[ ] tuya-panel-lamp-sdk
[ ] tuya-panel-lock-sdk
[ ] tuya-panel-robot-sdk
[x] tuya-panel-health-sdk

Type of change
Please select the relevant option.

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

Codecov Report

Merging #65 (28dbc49) into main (1750094) will increase coverage by 2.71%.
The diff coverage is 76.82%.

@@            Coverage Diff             @@
##             main      #65      +/-   ##
==========================================
+ Coverage   56.51%   59.22%   +2.71%
==========================================
  Files         129      140      +11
  Lines        4721     5322     +601
  Branches     1101     1222     +121
==========================================
+ Hits         2668     3152     +484
- Misses       2051     2167     +116
- Partials        2        3       +1

Impacted Files
Coverage Δ

...l-health-sdk/src/components/unLockButton/index.tsx
64.28% <64.28%> (ø)

...el-health-sdk/src/components/scrollRuler/index.tsx
71.42% <71.42%> (ø)

.../components/unLockButton/AnimatedCircleProgess.tsx
72.72% <72.72%> (ø)

...nel-health-sdk/src/components/barPercent/index.tsx
78.57% <78.57%> (ø)

...-panel-health-sdk/src/components/progess/index.tsx
93.33% <93.33%> (ø)

...a-panel-health-sdk/src/components/progess/style.ts
100.00% <100.00%> (ø)

packages/tuya-panel-api/src/index.ts
100.00% <0.00%> (ø)

...way-sdk/src/components/topbarWithArc/i18n/index.ts

...gateway-sdk/src/components/topbarWithArc/index.tsx

packages/tuya-panel-api/src/gateway/relation.ts
50.00% <0.00%> (ø)

... and 14 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 1750094...28dbc49. Read the comment docs.

@baohuse commit 记录看起来是不对的，建议检查下 Changes 是不是有别的包的记录。

@youngjuning 貌似是拉取远程跟本地时出现了冲突，解决完commit，增加的
commit 28dbc49fcc357302e8efba3721d361e487938d1e
Author: xl.yang<EMAIL_ADDRESS>Merge branch 'feature/tuya-panel-health-sdk' of https://github.com/tuya/tuya-panel-sdk into feature/tuya-panel-health-sdk
# Conflicts:
#       README.md
#       example/src/config/index.js
#       example/src/scenes/Gateway/index.js
#       package.json
#       packages/tuya-panel-animation-sdk/src/components/particle/__tests__/__snapshots__/particle.test.js.snap

commit bda0a6aee1d614550b08c68568222d68bc3761b4
Author: xl.yang<EMAIL_ADDRESS>Date:   Wed Jul 28 20:53:22 2021 +0800
feat: add progess component


Pop-up message/warning when trying to open large files...

It would be helpful if Atom would show a pop-up message requesting confirmation upon opening large files.
I'm sure that I'm not the only one that has accidentally clicked on a very large file (mp3, mp4, etc) and watched Atom nearly halt while trying to load it.
Ideally, Atom would read the file size of the item to open and would pop-up a confirmation request for any file past a certain size.
Thank you!

Duplicate issue, even though I can't find the other one atm.

Atom 1.5.4 throws out a message that the file is too large and processing it would end in a slow Atom.
What kind of file do you try to parse?
What is your atom version?

Thanks for the suggestion! This looks like a duplicate of https://github.com/atom/atom/issues/10086 though, so I'm going to close this out in favor of that issue.


Perception on pull requests

Reviewing #311, I realize that I have a different perception of pull requests then e.g. @leotrs.
Like in the updated contribution guideline #311 a pull request could look like this:

Running locally all pytest from the main manim/ folder
Including black autoformation
update the docstrings
strongly preferred that you include tests that accompany them in your PR
your proposed changes are as general as  possible

As a new contributor, I would feel very intimidated by this.
And also as a developer, I find this workflow a bit too much for a first presentation of an idea.
One person once said to me:
"It's better to have a good idea that is poorly presented,
then to have a poor idea that is well presented."
With this in mind, I want to say, that the upper workflow would be in theory very good, but in practice not so easy to handle.
I suggest, that the first presentation of an idea, so the first commit to a new pull request should be as easy as possible, even if that means that the pull request is not complete.
That means no docstrings, not as general as possible (making things as general as possible can take a lot of time!), and no tests you have to include. To clarify: It is appreciated if you do so, but it is should not be mandatory.
Then, after the first look from other devs, which find this idea good, one can start to add docstrings, generalize the code, maybe add tests, etc.
Additional to this:
When working on new things, I work with some minimal examples, that won't be useful for the final repo, but are very useful for trying this new feature.
Should these examples be added to a pull request?
My idea would be: Yes because then other devs have the chance to test this feature easily.
Before merging, these examples could be removed again.

I COMPLETELY agree with

And also as a developer, I find this workflow a bit too much for a first presentation of an idea.

But, still, tests and docs are and should be mandatory. That's what will keep manim still safe for contributing.

I suggest, that the first presentation of an idea, so the first commit to a new pull request should be as easy as possible, even if that means that the pull request is not complete.

So yes, for a presentation of an idea, this is absolutely super. I'm sure we will have a lot more contributions than we would if we restrict that much PR from the beginning.
But I'm not very experienced with open source stuff and even less a professional dev.

Hi @kolibril13, thank you for sharing your thoughts on this issue. We certainly want to be as welcoming as possible.

Running locally all pytest from the main manim/ folder
Including black autoformation
update the docstrings
strongly preferred that you include tests that accompany them in your PR
your proposed changes are as general as possible

All of these are standard requirements to contribute to big open source projects. Emphasis on "big" here. Manim is currently used by dozens (hundreds?) of people, and in the future I would love to reach thousands, if not tens of thousands more. As developers, we are responsible to not include in the library something that may interfere with the user experience, workflow, and productivity. For example, Microsoft cannot ship PowerPoint with bugs or without testing, NumPy cannot accept computational errors, and matplotlib cannot ship functions that render incorrectly. All of these must be well formatted, documented, and tested. In our case, we are responsible for not shipping code that may interfere with an educator's deadlines when producing class materials using manim. Perhaps we are not quite there yet, but if we ever want to see manim used by more and more people, we must strive to ship stable software.

As a new contributor, I would feel very intimidated by this.

I understand where you're coming from, but unfortunately there is a trade-off to be made here, and I personally fall on the side of caution. We cannot ship software that breaks users' experience.

And also as a developer, I find this workflow a bit too much for a first presentation of an idea.

A PR is not meant to be the first presentation of an idea. A PR is a "Pull Request", which means "my idea is ready, implemented, tested, and stable, and is ready to be reviewed by the rest of the developers". For the first presentation of an idea, or a feature request, you should open an issue.

One person once said to me:
"It's better to have a good idea that is poorly presented,
then to have a poor idea that is well presented."

This is a very interesting philosophy. Like I said above, the way to present an idea is through issues (or discord, chat, email, etc). PRs have a functional role that is far beyond "presenting" an idea.

I suggest, that the first presentation of an idea, so the first commit to a new pull request should be as easy as possible, even if that means that the pull request is not complete.

As said above, a great way of introducing an idea to the dev team is through an issue. See for example what I did recently in #293.

That means no docstrings, not as general as possible (making things as general as possible can take a lot of time!), and no tests you have to include. To clarify: It is appreciated if you do so, but it is should not be mandatory.

Unfortunately, without documentation, it will be hard for the dev team to know what's going on in a new PR. One thing you have to be mindful of is that everyone here is a volunteer, and asking a volunteer to spend more time than they are willing or able is generally considered inconsiderate and even rude. You can think of a PR as turning in your homework. If you present a badly formatted, illegible, unorganized document, in the best case scenario, you are asking your teacher to spend way more time than necessary to grade it.

Then, after the first look from other devs, which find this idea good, one can start to add docstrings, generalize the code, maybe add tests, etc.

This can already be done by marking a PR as a draft. You are right in that a PR doesn't need to be 100% perfect to be submitted or reviewed, and it can be under ongoing development as well. But in order to be merged, it should be documented/tested/general (at least somewhat).

When working on new things, I work with some minimal examples, that won't be useful for the final repo, but are very useful for trying this new feature.
Should these examples be added to a pull request?
My idea would be: Yes because then other devs have the chance to test this feature easily.
Before merging, these examples could be removed again.

You can add/remove anything you want while the PR is under development or marked as a draft. But make sure to add a big warning saying "this file is not mean to be merged". (I would much rather that they don't be committed because they will remain in the git history, but hey as long as they aren't merged that's fine too I guess.) Remember, when you deem a PR to be "ready for merging", it must be ready to be used by dozens/hundreds/thousands of other people. We do not want to ship unnecessary/unstable/illegible stuff.
NOTE: I'm grasping for words here, but don't take me too seriously here. I do not think that each PR must be totally perfect, and I do not think that devs are necessarily like teachers to contributors and PRs are homework -- we're all learning together here. What I mean to say in general is that well-crafted PRs are, in a way, a show of respect and care for the community, and also a way to simplify the devs' lives by a ton. If you have an idea that is not 100% tested/documented/implemented, that's what issues and discord and draft PRs are for, and I think we can say we are doing a great job at welcoming these type of contributions as well.
Final word: use your best judgment when contributing, and keep in mind that with each issue/PR/conversation you are asking a volunteer to spend some of their time on your idea. As a quick example, I've already spent 30min today dealing with open issues, and that's time that I don't spend writing my dissertation. If you find a dev with time to spare, then that's awesome. If not, then the responsibility is on you to convince the dev team to merge your changes, and the dev team should be allowed to reserve merging rights to PRs that are legible/tested/documented/general/stable/etc.

After reading my own text again, I think the current language I'm proposing in contributing.md might be a bit inflexible. We can perhaps add some language to reflect the fact that PRs don't have to be 100% perfect, but the more complete they are, the easier it will be for devs to review and the faster they will get merged. I do stand by everything I said in this thread tho.

@leotrs thank you a lot for taking your time and writing such an in-depth view on pull requests.
This is my first bigger Open-Source project and had the idea that pull request are more like a playground where you can tinker together on half-finished ideas so that they might maybe become a part of the main branch in the end.
I was not aware that they are meant to be tested/documented/implemented properly from the beginning, and want to apologize that this was not the case in some of my previous pull requests. Discussing half prepared ideas in issues instead sounds good.

Manim is currently used by dozens (hundreds?) of people, and in the future, I would love to reach thousands, if not tens of thousands more

This is a really inspiring and visionary thought. I see that with this vision it makes a lot of sense to pay attention to maintain the code properly.
To the preparation of code:
Maybe we could make a script that helps to prepare the repo for making a pull request without too many manual steps, something like
import os
from pathlib import Path

path = Path.cwd().parent

os.system(f"black {path}")
os.system("pytest")

This is my first bigger Open-Source project and had the idea that pull request are more like a playground where you can tinker together on half-finished ideas so that they might maybe become a part of the main branch in the end. I was not aware that they are meant to be tested/documented/implemented properly from the beginning, and want to apologize that this was not the case in some of my previous pull requests. Discussing half prepared ideas in issues instead sounds good.

To be completely fair, what I am advocating for is for us to steer into a "big FOSS project model". Up to now, we haven't been following the instructions I laid out to a tee. So there's no need to apologize at all! Like I said, you can PR whatever you want, but its state will determine how long it will take for it to be ultimately merged.
Also, on the topic of tinkering: your own fork and other (non-master) branches are exactly suitable for this purpose. The main repo's master branch should be kept for code that is ready to be shipped to all users. (Again, I'm advocating that we start doing this, I'm not saying that this is how it's always been.)

Maybe we could make a script that helps to prepare the repo for making a pull request without too many manual steps

If you think this is a feature that will be appreciated by most users, feel free to start an issue or PR ;) I personally think this is unnecessary since there are only two manual steps (black and testing) that this script would be replacing. So instead of executing two things, you have to execute one thing. Not much of a difference. But I don't make unilateral decisions, so please feel free to open an issue to hear what the rest of the team thinks.


301-palooza

opening this issue to loop @jdotpz in. We need to collect a list of AALLLLLLL the pages that are changing location and ALLLLLLL the new pages that replace them.
JP, how would you like that information delivered?

Morse code would be fine.  If you don't know morse that well, you can feel free to put it in this issue and let me know when.
We should set this site up on Cloudfront one day.

it's going to essentially be every page on the site. does a spreadsheet make more sense or ??? and it'll be probably tomorrow by EOD.

Here's where we're at now:
http://opennews.org/fellowships/ -> http://opennews.org/what/fellowships/
http://opennews.org/fellowships/info.html -> http://opennews.org/what/fellowships/info.html
http://opennews.org/fellowships/community.html -> http://opennews.org/what/fellowships/community.html
http://opennews.org/fellowships/faq.html -> http://opennews.org/what/fellowships/faq.html
http://opennews.org/hackdays.html -> http://opennews.org/what/community/eventsupport.html
http://opennews.org/code.html -> http://opennews.org/what/community/eventsupport.html
http://opennews.org/source.html -> http://opennews.org/what/community/source.html
http://opennews.org/srccon.html -> http://opennews.org/what/conferences/srccon.html
http://opennews.org/newspartners.html -> http://opennews.org/getinvolved/newspartners.html
http://opennews.org/partnerguidelines.html -> http://opennews.org/what/fellowships/partnerguidelines.html
http://opennews.org/getinvolved.html -> http://opennews.org/getinvolved/

just a note that these may change significantly before the end of the night.

I'll count on it!  Tomorrow, we'll setup the redirects on staging to test,
and then just search/replace the domain names.
On Thu, Jan 15, 2015 at 9:44 PM, sinker<EMAIL_ADDRESS>wrote:

just a note that these may change significantly before the end of the
night.
—
Reply to this email directly or view it on GitHub
https://github.com/mozilla/mozilla-opennews/issues/201#issuecomment-70204444
.

OK, I did a big move and now we no longer have .html after all our pages (see #226) as a result, the pages listed above are incorrect. I made a spreadsheet:
https://docs.google.com/spreadsheets/d/19-HqXTPe3nqDBWxVv5P-FSkwuQScsK3fZdpVomXn5Us/edit?usp=sharing

Alright I'll get cooking here.
On Friday, January 16, 2015, sinker<EMAIL_ADDRESS>wrote:

OK, I did a big move and now we no longer have .html after all our pages
(see #226 https://github.com/mozilla/mozilla-opennews/pull/226) as a
result, the pages listed above are incorrect. I made a spreadsheet:
https://docs.google.com/spreadsheets/d/19-HqXTPe3nqDBWxVv5P-FSkwuQScsK3fZdpVomXn5Us/edit?usp=sharing
—
Reply to this email directly or view it on GitHub
https://github.com/mozilla/mozilla-opennews/issues/201#issuecomment-70225338
.

OK, all the redirects are up.


Launch script does not work on MacOS

The launch script uses bash v4 variable handling which is not available on MacOS.
Lines 48 and 69 in launch.sh need to be changed to use tr instead of ${VAR^}

Current:
if [[ "${SETUP^}" == "Y" ]] || [[ -z $SETUP ]]; then
...
if [[ "${BUILD^^}" == "YES" ]]; then

should be:
if [[ "$(echo $SETUP | tr '[:lower:]' '[:upper:]' )" == "Y" ]] || [[ -z $SETUP ]]; then
...
if [[ "$(echo $BUILD | tr '[:lower:]' '[:upper:]' )" == "YES" ]]; then


Typing gets laggy (UI hangs for split seconds) when using this extension

Type: Bug
I absolutely love this extension and can't live without it.
But I noticed that I very consistently have lags in typing when using it (the UI will freeze for split seconds while typing). I don't know what the reproduction steps are, but I used the Extension Bisect tool to identify that this only happens when the extension is active (and very consistently) and never when the extension is deactivated.
Extension version: 0.2.8
VS Code version: Code 1.77.3 (704ed70d4fd1c6bd6342c436f1ede30d1cff4710, 2023-04-12T09:41:48.638Z)
OS version: Darwin arm64 22.3.0
Modes:
Sandboxed: Yes

System Info

Item
Value

CPUs
Apple M1 Pro (10 x 24)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
7, 7, 7

Memory (System)
32.00GB (0.09GB free)

Process Argv
--crash-reporter-id 9d8b3555-0016-4d38-9abf-4a1f6545cfc7

Screen Reader
no

VM
0%

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263cf:30335440
vscorecescf:30445987
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593cf:30376535
pythonvs932:30410667
cppdebug:30492333
vsclangdf:30486550
c4g48928:30535728
dsvsc012:30540252
pynewext54:30695312
azure-dev_surveyone:30548225
nodejswelcome1:30587005
3biah626:30602489
pyind779:30671433
89544117:30613380
pythonsymbol12:30671437
a9j8j154:30646983
vsctsb:30705553
functionswalk:30687959
pythonms35:30701012
pythonfmttextcf:30716743

I'm also facing this. I suspected it had to do with this extension since it was the only recent I had added. I see the slowness the most when VSCode runs Prettier upon me saving the file.

@felixfbecker We have a lot to improve there, I still don't know about a specific thing with a significant performance impact.
Any help in measuring and solving this problem will be appreciated 🙏🏼
@rdsedmundo I'm pretty sure it isn't related, the extension is not involved in file saving. it's just adding new diagnostics when TypeScript creates his diagnostics.

It is, I disabled and the error is gone. I did a bisect as the author suggest, it's definitely this extension the culprit.

@yoavbls  Given it blocks the UI, it leads me to believe that this must be happening in VS Code, since the extension runs in the extension host worker. So the only thing I can think of is that the amount (or frequency) of data the extension is giving VS Code overloads the UI process (or there is some inefficient code in VS Code).
I'd probably go at this by using the Devtools in VS Code to capture a perf profile while it is happening and see where the CPU is spending its time.

Yes, the extension is nice, but it totally kills VS Code.

@rdsedmundo It's weird. It shouldn't affect the file saves. Do you see something that could cause it?
@felixfbecker that is a good idea. If someone wants to make some performance tests and spot the weak spots/functions that take the longest times to run it would be helpful.
I will investigate it deeper after the migration to a monorepo is completed

I haven't run into any performance issues yet, but haven't used the extension very much. Perhaps a short term solution for people running into this issue could be to have the extension run in a different process. Adding this to your settings.json should allow for the extension to use the second extension host process.
"extensions.experimental.affinity": {
    "yoavbls.pretty-ts-errors": 1,
},

I will second this, vscode has been very sluggish lately with this extension. I've disabled it for now. This extension has been a MAJOR help with the ts errors for newer devs on my team, hope these issues can get resolved. Wish I had more free time to help.

v0.5 just published with a new caching mechanism 🕺🏼
Try it out, it should solve these performance issues
https://github.com/yoavbls/pretty-ts-errors/releases/tag/v0.5.0

I'm facing similar performance problems today (never had them before), disabling / enabling the extension does fix / enable the issue.
I really like this extension so that's why I'm reporting it here
Extension version: 0.5.2
VS Code Version: 1.85.1 (Universal) Commit: 0ee08df0cf4527e40edc9aa28f4b5bd38bbff2b2 Date: 2023-12-13T09:48:06.308Z (1 wk ago)
Electron: 25.9.7
ElectronBuildId: 25551756
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: <IP_ADDRESS>-electron.0
OS: Darwin arm64 22.1.0
System infos: M1 MBP 32Go RAM

After more research, it seems the performance issue is due to the "typescript.tsserver.experimental.enableProjectDiagnostics": true experimental feature. There is an ongoing bug where node_modules files get analysed by the typescript server and the found errors are reported in the Problems tab even when node_modules are excluded in the tsconfig.json.
I'm guessing that pretty-ts-errors is ran on all encountered problems which is a lot in this case.


Failure to use AttributeByKeyValues successfully

Hi all,
I'm testing out the AttributeByKeyValues tool and I'm having difficulty getting it to work. I created a new GDB with the latest toolbox (from today). It only has a few feature classes in it and I only added one feature to the CartographicLines feature class -- a cross section. I populated the "Symbol" field to use as my Key field. This is my first question -- is it okay to NOT use LType or SType?
Here's what my KeyValueFile TXT file looks like:
CartographicLines
Symbol|Type|Label
Cross section, A-A'|Cross section|A-A'
And here's the message I'm getting:
**Executing: AttributeByKeyValues "G:\Shared drives\UGS_Editorial_GIS\GeMS\Training\20210225_GIS_1\uGeMS_GoshenPass.gdb" "G:\Shared drives\UGS_Editorial_GIS\GeMS\Training\20210225_GIS_1\KeyValueFile_GoshenPass_delimTXT_test.txt" true
Start Time: Thu Mar 11 17:37:07 2021
Running script AttributeByKeyValues...
GeMS_AttributeByKeyValues_Arc10.py, version of 7 March 2021
Forcing the overwriting of existing fields
[u'MapUnitPolys', u'ContactsAndFaults', u'CartographicLines', u'GenericPoints']
['\xef\xbb\xbfCartographicLines']
CartographicLines
Failed script AttributeByKeyValues...
Traceback (most recent call last):
File "G:\Shared drives\UGS_GeMS\GeMS_Reference\Scripts\Toolset\gems-tools-arcmap-master\Scripts\GeMS_AttributeByKeyValues_Arc10.py", line 89, in
addMsgAndPrint('  ' + fClass + ' not in ' + gdb + "\" + finalfds)
UnicodeDecodeError: 'ascii' codec can't decode byte 0xef in position 2: ordinal not in range(128)
Failed to execute (AttributeByKeyValues).
Failed at Thu Mar 11 17:37:21 2021 (Elapsed Time: 13.50 seconds)**
I've run the script several times with different feature classes and slight changes to the Key Value File and now, this new GDB. I've tried it with the overwrite option on and off, in ArcCatalog, in ArcMap editing, and in ArcMap without an edit session started. I'm afraid I'm missing a requirement for this script but am not sure what it is.
Any guidance would be great! Thanks for your help!

Hi Rosemary,
First, the name of the field with the un-parsed feature attributes is meant to be something not defined by GeMS, such as the examples of LTYPE, PTYPE, or STYPE. Using Symbol is odd to me unless you are also using a style file with a symbol called 'Cross section, A-A'. That said, I think the tool should still work. It should still read the content of Symbol and then populate the other two fields based on the value found there.
Second, it looks to me like the tool is parsing your KeyValue text file and finding CartographicLines but then is not finding that feature class in the gdb Are those two names exactly alike?

Hi and thanks for your help!
We are, indeed, using a style file with the symbol called "Cross section, A-A'" because it fits well with our already-existing schema. It'd be great if the tool will work without having to add another field like LTYPE, PTYPE, or STYPE. But we'll do what we have to do.
I hadn't noticed that second version of the Cartographic lines feature class; is that actually a feature class or some kind of data table or something? When I look at my GDB in Catalog, I only see one version of the feature class and it's called "CartographicLines" so I'm a bit bewildered. A screenshot of my GDB in ArcCatalog:

I thought it might have something to do with the fact that I'm working on the Google Drive (aka File Stream) so I copied all of my data (not the toolbox, mind you) over to my desktop and still get the following error:
Running script AttributeByKeyValues...
  GeMS_AttributeByKeyValues_Arc10.py, version of 7 March 2021
Forcing the overwriting of existing fields
[u'MapUnitPolys', u'ContactsAndFaults', u'GeologicLines', u'CartographicLines', u'MapUnitLines', u'MapUnitPoints', u'GenericPoints', u'OrientationPoints', u'CartographicPoints']
['\xef\xbb\xbfCartographicLines', '', '', '', '', '']
Failed script AttributeByKeyValues...

Traceback (most recent call last):
  File "G:\Shared drives\UGS_GeMS\GeMS_Reference\Scripts\Toolset\gems-tools-arcmap-master\Scripts\GeMS_AttributeByKeyValues_Arc10.py", line 104, in <module>
    if len(vals) <> numMFields:
NameError: name 'numMFields' is not defined

Failed to execute (AttributeByKeyValues).
Failed at Mon Mar 15 15:39:23 2021 (Elapsed Time: 8.24 seconds)

I wonder if it has something to do with how I've created my TXT file. I created everything in Excel and set my default delimiter to "pipe". Then, I saved the table as a CSV which was easily opened as a text document and saved. Is there a better process?

Sorry! I just noticed that '\xef\xbb\xbfCartographicLines' is not part of the list above it of feature classes from the gdb. That is being reported during a listing of the names of feature classes found in the key values text file and, looking around a bit more, it looks like Excel has exported the CSV file as UTF8 with BOM (Byte Order Mark(s)) at the beginning of the file (the hex characters), which is making it difficult for the python print function to print the string to the screen.
We should write code to find and accommodate this, but in the meantime, try exporting from Excel where you explicitly set the encoding to 'UTF-8'. About one-third down on this page is an explanation.
If that doesn't work, try re-creating the file from scratch in notepad or notepad++.

I just re-created your key value text file in Excel and looked at the resulting encoding as reported by Notepad++ after three different exports:

Using Save As > CSV UTF-8 from the drop-down list resulted in a file with UTF-8 BOM encoding
Using Save As > CSV gave me a UTF-8 file with no BOM and
Using Save As > More options > Tools > Web Options > Encoding > Save this document as > Unicode UTF-8 gave me a file in UTF-8  with no BOM.

So, the short explanation here is you should be able to use the second option (unless there is some kind of default setting that overrides that)

Thanks again, it looks like that made a difference (I was using option 1). Now I'm getting a different error that reads as follows:
Executing: AttributeByKeyValues "G:\Shared drives\UGS_Editorial_GIS\GeMS\Training\20210225_GIS_1\uGeMS_M286DM_GoshenPass.gdb" "G:\Shared drives\UGS_Editorial_GIS\GeMS\Training\20210225_GIS_1\KeyValueFile_GoshenPass_delim_noBOMsTXT.txt" true
Start Time: Mon Mar 15 17:46:27 2021
Running script AttributeByKeyValues...
  GeMS_AttributeByKeyValues_Arc10.py, version of 7 March 2021
Forcing the overwriting of existing fields
[u'MapUnitPolys', u'ContactsAndFaults', u'GeologicLines', u'CartographicLines', u'MapUnitLines', u'MapUnitPoints', u'GenericPoints', u'OrientationPoints', u'CartographicPoints']
['CartographicLines', '', '', '', '', '']
Failed script AttributeByKeyValues...

Traceback (most recent call last):
  File "G:\Shared drives\UGS_GeMS\GeMS_Reference\Scripts\Toolset\gems-tools-arcmap-master\Scripts\GeMS_AttributeByKeyValues_Arc10.py", line 104, in <module>
    if len(vals) <> numMFields:
NameError: name 'numMFields' is not defined

Failed to execute (AttributeByKeyValues).
Failed at Mon Mar 15 17:46:38 2021 (Elapsed Time: 10.70 seconds)

I could be wrong but I think it's because my Excel to CSV to TXT added a bunch of extra pipes to make up for blank columns (for the feature classes that don't have as many fields). Is this some kind of default in Excel? Should I find and replace extra ones somehow? See my screen shot below:

I deleted the extra pipes at the end of the lines as well as between each feature class. I also discovered hundreds of extra lines at the end -- just 5 pipes row after row.
The script worked perfectly!!
However, I feel like I am missing something in the process of developing my KVF in Excel that makes it not create or produce these extra rows and pipes. Is there something I'm doing wrong? Is there a quick and easy fix or will it require a manual removal?
Thanks again for your help!

If you are missing something, I don't think it's that much. You are finding the limitations of using Excel to edit a text file and I don't know Excel well enough to give you any suggestions. Personally, I would edit the file in a text editor. Notepad++ is my favorite.
Sounds like you are on your way. Can we close this issue?

Sounds good. Thanks again for your help!


VRS and JRS calculation off at end of date range?

https://powerofus.force.com/0D58000001s3g4u
Olivier Wiener (Association Alzheimer Genève)
While testing Job Recurrence Schedules and Volunteer Recurrence Schedules, I've a strange bug. We have created two JRS (every tuesday from feb 3rd to jun 30th 2 hours duration till June 30th and every tuesday from feb 4rd to jun 24th 3 hours duration till june 24th). It creates 43 volunteer shifts.
Then we create the VRS. To do this, we use the "Copy Schedule From" and modify the start date so that it match exactly the one of the respective JRS.
The odd thing is that while I have 43 volunteer shifts, I only have 41 volunteer hours (we are missing the last one of each JRS ie jun 24th and jun30th). Of course the last two volunteer shifts are blank for "Total Volunteers" and the "#of volunteers still needed" is equal to 1. Any idea ?

fixed for release 3.76


Merge or close bump/snyk pull requests

I created a separate SNYK branch to merge in and test the seven snyk branches one at a time, all of them were able to build after fixing merge conflicts.

I was expecting to see a bunch of updates to web/package.json, pom.xml files across the Java projects, and Dockerfile... For example, snyk-fix-732... makes a change to this Dockerfile. I don't see this change in this PR. Any idea why?


iox-#447 fix seg fault in roudi

Signed-off-by: Christian Eltzschig<EMAIL_ADDRESS>Pre-Review Checklist for the PR Author

[x] Branch follows the naming format (iox-#123-this-is-a-branch)
[x] Commits messages are according to this guideline

[x] Commit messages have the issue ID (iox-#123 commit text)
[x] Commit messages are signed (git commit -s)
[x] Commit author matches Eclipse Contributor Agreement (and ECA is signed)

[x] Update the PR title

Follow the same conventions as for commit messages
Link to the relevant issue

[x] Relevant issues are linked
[x] Add sensible notes for the reviewer
[x] All checks have passed
[x] Assign PR to reviewer

Notes for Reviewer

Checklist for the PR Reviewer

[x] Commits are properly organized and messages are according to the guideline
[x] Code according to our coding style and naming conventions
[ ] Unit tests have been written for new behavior
[x] Public API changes are documented via doxygen
[x] Copyright owner are updated in the changed files
[x] PR title describes the changes

Post-review Checklist for the PR Author

[ ] All open points are addressed and tracked via issues

Post-review Checklist for the Eclipse Committer

[ ] All checkboxes in the PR checklist are checked or crossed out
[ ] Merge

References

Closes #447

Integrationtests with RouDi needs to be written, already addressed here: https://github.com/eclipse/iceoryx/issues/378


astutil.DeleteNamedImport could replace most of the de-duplication code

Package astutil has a DeleteNamedImport function, which looks like it could be used to replace most of the de-duplication code in this command.
https://godoc.org/golang.org/x/tools/go/ast/astutil#DeleteNamedImport

Along with astutil.Add[Named]Import.


Fixed a path to the source file in the template to use an attribute value

When install as system wide, the source file path is fixed to /usr/local/src/nvm/nvm.sh. But there is the appropriate value to use in the attribute file.

Thanks for making this configurable! Merged.


Using GeoEXT2 store for Layer tree

First of all I want to highlight the background of this issue. Previously I opened the same issue but someone closed my issue that this is not the right place but as I didn't get any reply from anywhere including the users of mailing list I am opening this issue again.
I want to create a layer tree like the one given in the below example.
https://iris.gov.gr/SoilServices/danger.html
The example finely works when i implement the same on my own system it doesn't work and I don't know much about the complexities of GeoEXT.
I am writing my code here below and the error that I get.
Here is the code for the Store:
var store = Ext.create('Ext.data.TreeStore', {
model: 'GeoExt.data.LayerTreeModel',
root: {
text: "Root",
expanded: true,
children: [
{
text: "Θεματικοί Χάρτες",
leaf: false,
expanded: true,
children: [
{
text: sppsq.name,
layer: sppsq,
leaf: true,
checked: false,
children: [],
nodeType: "gx_overlaylayercontainer"
},
{
text: elecag.name,
layer: elecag,
leaf: true,
checked: false,
children: [],
nodeType: "gx_overlaylayercontainer"
},
]
},
{
plugins: [{
ptype: 'gx_baselayercontainer',
loader: {store: mapPanel.layers} // BASE "REFERENCE" LAYERS FROM arcticMapPanel
}],
expanded: true,
text: 'Υπόβαθρα'
}
]
}
});
Below is the code for tree:
_var tree = Ext.create('GeoExt.tree.Panel', {
border: true,
region: "west",
title: "Επίπεδα",
width: 290,
split: true,
collapsible: true,
collapseMode: "mini",
autoScroll: true,
store: store,
rootVisible: false,
lines: false,
listeners: {
checkchange: {
fn: function (record, checked, opts) {
record.data.layer.setVisibility(checked)
}
}
}
}
);
Error Got:
too much recursion
http://cdn.sencha.com/ext/gpl/5.1.0/build/ext-all-debug.js
Line 1759

Please do not open multiple issues on the same topic.
As stated in your first issue #395 this is not the right platform for such a question. The "issues"-section here in github is only for reporting software bugs in GeoExt itself.
Furthermore I repeated to your question on the mailinglist, so no need for another issue.
If we discover that this is related to a bug in GeoExt2 itself, we can re-open #395 .


chore: upgrade eslint

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


Changed default stopsignal from SIGTERM to SIGINT

Changed the stopsignal to SIGINT, to ensure the database data is always synced to disk, even if clients do not cooperate.
For Details see https://github.com/docker-library/postgres/issues/714

I've updated this per the discussion in #714, especially to add it to all versions/variants, and to add a long-form comment explaining the rationale and pointing to the upstream documentation that's informed our choice (and can further inform users whose use case/constraints warrant making a different choice).
(We should probably add something similar to the image description once this lands.)


CASMINST-6233 get CFS configs for specific management node types

Description
Get CFS configs for specific management node types

Checklist

[x] If I added any command snippets, the steps they belong to follow the prompt conventions (see example).
[x] If I added a new directory, I also updated .github/CODEOWNERS with the corresponding team in Cray-HPE.
[x] My commits or Pull-Request Title contain my JIRA information, or I do not have a JIRA.

/backport release/1.4


Content :: Import JapanFocus Data

The API is ready
The Requests need to be sent here
http://japanfocus.org/site/list_xml
We accept the following  parameters :
'start' - start number
'limit' - request limit
'start_id' - id bigger than
'end_id' -id smaller than
'publication_date_start' - start publication date
'publication_date_end' -end publication date
The Parameters have to be sent over POST or GET.
System response is delivered in XML format

Okay so you'll probably have to write a script in python to do this. I like to use the python library scrapy. You can see an example of a scrapy script I wrote here. If you look at the JSON string that it creates, in context of the Adding Data to the Archive on our wiki (very last section), then it will hopefully make a bit of sense. Google scrapy for all the documentation, it's pretty accessible. You're pulling data out of a page, and then going to the next page, and repeat.
So you use that URL from EJ's original comment, plus parameters, to get a list of specific articles.
For example, http://japanfocus.org/site/list_xml?start_id=0&end_id=4070 gives you all the articles with ids 0 to 4070, but unfortunately it doesn't show all of them. If you download scrapy (it's a python library), then open a python shell and run scrapy shell "http://japanfocus.org/site/list_xml?start_id=0&end_id=4070" (you need quotes around the url now because of the symbols), and then type len(sel.xpath('//element')), you can see that it only outputs 30 at a time. Servers often impose limits like this because they don't want to get stuck returning 10,000 articles if that's what you ask for. So your script will have to "crawl," since we can't get all the items on one page.
It looks like the IDs only go up to ~4200, since http://japanfocus.org/site/list_xml?start_id=4300&end_id=500000 gives you no articles. And it seems like there aren't really any articles with IDs less than 1500 - see http://japanfocus.org/site/list_xml?start_id=0&end_id=1500 just gives info about JapanFocus.
Crawling is what my script does on the very last line of the xml_spider.py in the first link I gave you: yield Request(nextFileLink, callback = self.parse). I made my nextFileLink with resumption token stuff specific to that particular API, but for yours, you can probably just build the next file link by increasing the start_id and the end_id in the url both by 30. So you can start with http://japanfocus.org/site/list_xml?start_id=1500&end_id=1530, (or 1530 and 1560 since it doesnt look like theres anything between 1500-1530) and increase both by 30 each time, and you terminate when you're out of items.
When you right-click and inspect element, you will see the HTML tags that specify what each piece of the article is, and these tags are what you'll want to use in scrapy, so that you can put the right pieces of data in the right places in your ultimate JSON string. Also, you'll want to make sure your browser is displaying the text in UTF-8 encoding for the Japanese characters to display correctly.


Remove spurious "0" from info/data response and add UTRAnnotator VEP plugin

Requirements

Filling out the template is required. Any pull request that does not include enough information to be reviewed in a timely manner may be closed at the maintainers' discretion;
Review the contributing guidelines for this repository; remember in particular:

do not modify code without testing for regression
provide simple unit tests to test the changes
the PR must not fail unit testing
if you're adding/updating documentation of an endpoint, make sure you add/update the necessary parameters to the (template) configuration files in the ensembl-rest_private repo

Description
Remove spurious "0" from info/data releases array response
and
A new plugin was added to VEP_Plugins, UTRAnnotator. This is for Ensembl release e!109
Should be merged after https://github.com/Ensembl/ensembl-rest_private/pull/126 is merged.
Use case
info/data endpoint is returning "0" as part of the response because of duplication of meta table in two different bacteria dbs. Perl API modifies the species name by suffixing original name with a number but, other attributes such as release is undefined due to which rest server is considering the undefined release and returning "0" as part of releases array response.
and
Plugin functionality available through REST.
Benefits
info/data returns the correct response
Possible Drawbacks
If applicable, describe any possible undesirable consequence of the changes.
Testing
note to submitters and reviewers: documentation-only changes may reflect
changes in other repos that can result in new or different output from
REST endpoints. In turn, these may require new tests or changes to existing tests.
Have you added/modified unit tests to test the changes?
If so, do the tests pass/fail?
Have you run the entire test suite and no regression was detected?
Changelog
Are you changing the functionality of an endpoint? If so, please give a one line summary for the public facing changelog.
[/info/data] Remove spurious "0" from info/data releases array response.
[/vep/:species/hgvs/] new plugin option added: UTRAnnotator
[/vep/:species/id/] new plugin option added: UTRAnnotator
[/vep/:species/region/] new plugin option added: UTRAnnotator

Coverage increased (+0.01%) to 44.432% when pulling 4a1f7654c27b924a34ebc25e3f866728c34d7ca6 on bugfix/ignore-undefined-release into cf8457163df365ddb9a1a5259183773495da65e6 on release/109.


mask_matching_filtering_threshold not set in cellpose segmentation

Hi,
Within the legacy branch, in the config.yml if the CytosolSegmentationCellpose section is missing a match_masks or filtering_threshold_mask_matching value, match_masks now defaults to True, but a value for self.mask_matching_filtering_threshold is never set.
https://github.com/MannLabs/scPortrait/blob/fc6f25b8ec8cff73e1bf4acc8512e84927707451/src/scportrait/pipeline/workflows.py#L530-L547
This later causes an AttributeError here:
https://github.com/MannLabs/scPortrait/blob/fc6f25b8ec8cff73e1bf4acc8512e84927707451/src/scportrait/pipeline/workflows.py#L1522-L1528
[21/11/2024 01:52:58] Segmenting nucleus using the following model: nuclei
[21/11/2024 13:30:44] Segmenting cytosol using the following model: cyto2
Traceback (most recent call last):
  File "/nemo/stp/hts/working/scott/projects/20240918_dan_tedescoLab_slides/project.py", line 39, in <module>
    project.segment()
  File "/nemo/stp/hts/working/scott/code/scPortrait/src/scportrait/pipeline/project.py", line 752, in segment
    self.segmentation_f(self.input_image, *args, **kwargs)
  File "/nemo/stp/hts/working/scott/code/scPortrait/src/scportrait/pipeline/base.py", line 204, in __call__
    if callable(process):
  File "/nemo/stp/hts/working/scott/code/scPortrait/src/scportrait/pipeline/workflows.py", line 1579, in process
    self.cellpose_segmentation(input_image)
  File "/nemo/stp/hts/working/scott/code/scPortrait/src/scportrait/pipeline/workflows.py", line 1525, in cellpose_segmentation
    filtering_threshold=self.mask_matching_filtering_threshold,
AttributeError: 'CytosolSegmentationCellpose' object has no attribute 'mask_matching_filtering_threshold'

If you like I could submit a pull request where _check_for_mask_matching_filtering() also sets a default parameter for mask_matching_filtering_threshold if match_masks isn't present in the config?

Thanks for catching this. A PR would be amazing :-)

https://github.com/MannLabs/scPortrait/pull/115


Better message for publications with no annotations

All annotation pages have the text "Annotations from this publication:" after the details, even if there are no annotations.  eg. https://www.pombase.org/reference/PMID:27677791
Change to something better like: "This publication has no annotations in PomBase because ..."
Reasons for no annotations:

not curatable
no annotations in the paper
not curated yet

anything else?
Note to self: we need to pass the "canto_triage_status" from Chado to the web code so the web code knows if the paper is Curatable.

If it has to "know" the triage status anyway, maybe the pub page should use a couple of them to indicate some of the reasons for no annotations. Specifically, I suggest

methods paper
review

because each covers a fairly big chunk of the total uncuratable pubs (762 and 1126 respectively), and users might be interested in knowing if a particular paper is in one of those categories.

I started to type the same somewhere in another window a while ago....but got side-tracked...
I think we should avoid "not curatable"
For papers which are identified as "curatable" but not yet curated we should   have a message
that the paper has not yet been curated....

Yeah, different words will sound nicer than "not curatable". But I'm inclined to lump most of the subtypes of "uncuratable publications" rather than list every triage category.
Message ideas:
This publication has no annotations in PomBase because ...

it is a review.
it is a methods paper.
curators have found no annotatable gene-specific data in it.
it hasn't been curated yet. (Please contact us if you want to contribute annotations for this paper.)

Note to self: we need to pass the "canto_triage_status" from Chado to the web code so the web
code knows if the paper is Curatable.

I've done that now so any changes to the messages on the publication papers should be straight forward.

Notes from call:

ignore untriaged pubs; they don't even get a page
any annotation (Canto, tab-delimited files, contig files, etc.) takes precedence over the "no annotations" options
"it hasn't been curated yet" = anything triaged curatable, but without approved session
"... found no annotatable ..." = (uncuratable BUT NOT (review OR methods)) AND (approved session with no annotations)

super ;)

ignore untriaged pubs; they don't even get a page

Currently untriaged publication do get pages on the main site.  I'll fix that.

Currently untriaged publication do get pages on the main site. I'll fix that.

I've fixed that for tomorrow night's load.
While testing, I found a publication in Chado that doesn't appear to have been through Canto:
https://www.pombase.org/reference/PMID:17287513
It also doesn't seem to be a pombe paper.  Very odd.  I'll investigate how it ended up in Chado.

presumably a typo
chromosome1.contig:FT                   valproic acid; db_xref=PMID:17287513; date=20100917"
chromosome1.contig:FT                   valproic acid; db_xref=PMID:17287513; date=20100917"
chromosome2.contig:FT                   valproic acid; db_xref=PMID:17287513; date=20100917"

presumably a typo
chromosome1.contig:FT valproic acid; db_xref=PMID:17287513; date=20100917"

PMID:17287531 is in Chado too and also has some annotation for apm1.

Valproic acid affects membrane trafficking and cell-wall integrity in fission yeast.
Miyatake M, Kuno T, Kita A, Katsura K, Takegawa K, Uno S, Nabata T, Sugiura R.
Genetics. 2007 Apr;175(4):1695-705. Epub 2007 Feb 7.
PMID: 17287531
will fix

The publication pages now show sensible messages when there is no annotation.


ModPE.ShowTipMessage() not work

BlockLauncher Version: 1.12.7
MinecraftPE Version : 0.14.2

It's a known issue. MCPE bug

Fixed, sort of. (Reimplemented showTipMessage with my own code since MCPE's code doesn't work)


Http streaming client

Is it possible to write a http streaming client using React?
I have an application which connects to a server and the connection remains open and data is passed through that stream

Is it possible to write a http streaming client using React?

Are you looking for https://github.com/reactphp/http-client? :)

I believe this has been answered, so I'm closing this for now. Please come back with more details if this problem persists and we can reopen this :+1:


duplicity: <IP_ADDRESS> -> <IP_ADDRESS>

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/duplicity/versions.
meta.description for duplicity is: '"Encrypted bandwidth-efficient backup using the rsync algorithm"'.

Checks done (click to expand)

built on NixOS
/nix/store/s4dw0gd8hj3baphqfyc6vz8n83z5ardb-duplicity-<IP_ADDRESS>/bin/duplicity passed the binary check.
/nix/store/s4dw0gd8hj3baphqfyc6vz8n83z5ardb-duplicity-<IP_ADDRESS>/bin/rdiffdir passed the binary check.
Warning: no invocation of /nix/store/s4dw0gd8hj3baphqfyc6vz8n83z5ardb-duplicity-<IP_ADDRESS>/bin/.duplicity-wrapped had a zero exit code or showed the expected version
/nix/store/s4dw0gd8hj3baphqfyc6vz8n83z5ardb-duplicity-<IP_ADDRESS>/bin/..rdiffdir-wrapped-wrapped passed the binary check.
/nix/store/s4dw0gd8hj3baphqfyc6vz8n83z5ardb-duplicity-<IP_ADDRESS>/bin/.rdiffdir-wrapped passed the binary check.
Warning: no invocation of /nix/store/s4dw0gd8hj3baphqfyc6vz8n83z5ardb-duplicity-<IP_ADDRESS>/bin/...duplicity-wrapped-wrapped-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/s4dw0gd8hj3baphqfyc6vz8n83z5ardb-duplicity-<IP_ADDRESS>/bin/..duplicity-wrapped-wrapped had a zero exit code or showed the expected version
4 of 7 passed binary check by having a zero exit code.
4 of 7 passed binary check by having the new version present in output.
found <IP_ADDRESS> with grep in /nix/store/s4dw0gd8hj3baphqfyc6vz8n83z5ardb-duplicity-<IP_ADDRESS>
directory tree listing: https://gist.github.com/c18fb8a699880c6c45f52492671b2338
du listing: https://gist.github.com/4435cf3cb9ecf75677f070a52812d38d

Outpath report (click to expand)

Outpath difference report
11 total rebuild paths
3 package rebuilds
3 x86_64-linux rebuilds
3 i686-linux rebuilds
2 x86_64-darwin rebuilds
3 aarch64-linux rebuilds
First ten rebuilds by attrpath
deja-dup
duplicity
duply

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/s4dw0gd8hj3baphqfyc6vz8n83z5ardb-duplicity-<IP_ADDRESS> \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A duplicity https://github.com/r-ryantm/nixpkgs/archive/a481218df3b553de2ccd169db9e7561dcf3747fd.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/s4dw0gd8hj3baphqfyc6vz8n83z5ardb-duplicity-<IP_ADDRESS>
ls -la /nix/store/s4dw0gd8hj3baphqfyc6vz8n83z5ardb-duplicity-<IP_ADDRESS>/bin

cc @peti for testing.

Success on x86_64-linux (full log)
Attempted: duplicity
Partial log (click to expand)
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/w4zag1fi5ndg0r7kj3gx42jm25pdy2dj-duplicity-<IP_ADDRESS>
shrinking /nix/store/w4zag1fi5ndg0r7kj3gx42jm25pdy2dj-duplicity-<IP_ADDRESS>/lib/python2.7/site-packages/duplicity/_librsync.so
gzipping man pages under /nix/store/w4zag1fi5ndg0r7kj3gx42jm25pdy2dj-duplicity-<IP_ADDRESS>/share/man/
strip is /nix/store/vcc4svb8gy29g4pam2zja6llkbcwsyiq-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/w4zag1fi5ndg0r7kj3gx42jm25pdy2dj-duplicity-<IP_ADDRESS>/lib  /nix/store/w4zag1fi5ndg0r7kj3gx42jm25pdy2dj-duplicity-<IP_ADDRESS>/bin
patching script interpreter paths in /nix/store/w4zag1fi5ndg0r7kj3gx42jm25pdy2dj-duplicity-<IP_ADDRESS>
checking for references to /build in /nix/store/w4zag1fi5ndg0r7kj3gx42jm25pdy2dj-duplicity-<IP_ADDRESS>...
wrapping `/nix/store/w4zag1fi5ndg0r7kj3gx42jm25pdy2dj-duplicity-<IP_ADDRESS>/bin/..duplicity-wrapped-wrapped'...
wrapping `/nix/store/w4zag1fi5ndg0r7kj3gx42jm25pdy2dj-duplicity-<IP_ADDRESS>/bin/.rdiffdir-wrapped'...

Success on x86_64-darwin (full log)
Attempted: duplicity
Partial log (click to expand)
wrapping `/nix/store/m34caw478k1bq6v6k4qz6nivp2q0incp-duplicity-<IP_ADDRESS>/bin/rdiffdir'...
glibPreFixupPhase
post-installation fixup
gzipping man pages under /nix/store/m34caw478k1bq6v6k4qz6nivp2q0incp-duplicity-<IP_ADDRESS>/share/man/
strip is /nix/store/g5r4apl0za012ffs6ladinwa5w0m1l3k-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/m34caw478k1bq6v6k4qz6nivp2q0incp-duplicity-<IP_ADDRESS>/lib  /nix/store/m34caw478k1bq6v6k4qz6nivp2q0incp-duplicity-<IP_ADDRESS>/bin
patching script interpreter paths in /nix/store/m34caw478k1bq6v6k4qz6nivp2q0incp-duplicity-<IP_ADDRESS>
wrapping `/nix/store/m34caw478k1bq6v6k4qz6nivp2q0incp-duplicity-<IP_ADDRESS>/bin/..duplicity-wrapped-wrapped'...
wrapping `/nix/store/m34caw478k1bq6v6k4qz6nivp2q0incp-duplicity-<IP_ADDRESS>/bin/.rdiffdir-wrapped'...
/nix/store/m34caw478k1bq6v6k4qz6nivp2q0incp-duplicity-<IP_ADDRESS>

Success on aarch64-linux (full log)
Attempted: duplicity
Partial log (click to expand)
shrinking RPATHs of ELF executables and libraries in /nix/store/6dla0f8cn3vynar2jzsn33nrf0fdv1fs-duplicity-<IP_ADDRESS>
shrinking /nix/store/6dla0f8cn3vynar2jzsn33nrf0fdv1fs-duplicity-<IP_ADDRESS>/lib/python2.7/site-packages/duplicity/_librsync.so
gzipping man pages under /nix/store/6dla0f8cn3vynar2jzsn33nrf0fdv1fs-duplicity-<IP_ADDRESS>/share/man/
strip is /nix/store/p9akxn2sfy4wkhqdqa3li97pc6jaz3r1-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/6dla0f8cn3vynar2jzsn33nrf0fdv1fs-duplicity-<IP_ADDRESS>/lib  /nix/store/6dla0f8cn3vynar2jzsn33nrf0fdv1fs-duplicity-<IP_ADDRESS>/bin
patching script interpreter paths in /nix/store/6dla0f8cn3vynar2jzsn33nrf0fdv1fs-duplicity-<IP_ADDRESS>
checking for references to /build in /nix/store/6dla0f8cn3vynar2jzsn33nrf0fdv1fs-duplicity-<IP_ADDRESS>...
wrapping `/nix/store/6dla0f8cn3vynar2jzsn33nrf0fdv1fs-duplicity-<IP_ADDRESS>/bin/.rdiffdir-wrapped'...
wrapping `/nix/store/6dla0f8cn3vynar2jzsn33nrf0fdv1fs-duplicity-<IP_ADDRESS>/bin/..duplicity-wrapped-wrapped'...
/nix/store/6dla0f8cn3vynar2jzsn33nrf0fdv1fs-duplicity-<IP_ADDRESS>


Kibana TSVB to support scripted fields

TSVB is now not supporting scripted fields in OpenSearch latest version. Is that possible to add in this new feature?

@seanneumann any inputs on this issue?


⚠ SceneTime has degraded performance

In 3b591b8, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 3193 ms

Resolved: SceneTime performance has improved in f16c51e.


community:Updating Konko Integration

Description
This PR introduces update to Konko Integration with LlamaIndex.

Konko's Completion Endpoint Addition: Integration of completion endpoint to utilize a new set of models hosted on Konko.
Updated Documentation: Added jupyter notebook to reflect these new changes, providing clear guidance on utilizing the new features and ensuring seamless integration.

Type of Change
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[x] Added new notebook (that tests end-to-end)

Suggested Checklist:

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] I have added Google Colab support for the newly added notebooks.
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] I ran make format; make lint to appease the lint gods

@hatianzhang Thank you for reviewing and approving this integration! Just a quick question, when can we expect this PR to be merged.