Bugs parsing the try!() macro

This code from serde causes red underlining in VS Code even though rustc is fine with it:
        match try!(self.next_key_seed(kseed)) {
            Some(key) => {
                let value = try!(self.next_value_seed(vseed));
                Ok(Some((key, value)))
            }
            None => Ok(None),
        }

As of 5c3ccc55082838524f695ffe40138fd8e805db70.

So try! is deprecated in the 2015 edition, but serde uses #[allow(deprecated)]. We probably don't take that into account.

Yeah, that's tricky. Ideally, we should add editions to the parser, but that requires some design work. In the meantime, I'd be fine with just contextually parsing try as a macro if it is followed by !, this should be a relatively isolated "fix" to the parser.

I think this is working now:


Collector launched fine - test app and web do not.

Description
Keep getting timeouts on the test app and web start scripts; after the collector started fine.   It used to work, not sure what went wrong...any help would be appreciated.  Thanks.
Environment
Mac 10.11.6
Apache Maven 3.3.9
Pinpoint - Latest Release (2016/11/21)

Hi tatonki1
Each module log saved in  {$PINPOINT_HOME}/quickstart/logs.
Please post module log which not working.
thanks.


[PPP-4459] Use of Vulnerable Component: org.eclipse.paho:org.eclipse.…

…paho.client.mqttv3: CVE-2019-11777

Dependency management moved to the parent POM.
Removing exclusions since this artifact has no dependencies.

This is a series of PRs, see https://github.com/pentaho/maven-parent-poms/pull/202 for details.

:x: Build failed in 1m 12s
Build command:
mvn clean verify -B -e -Daudit -amd -pl \
assemblies/core/lib,assemblies/lib,plugins/streaming/impls/mqtt

:exclamation: No tests found!
Errors:
Filtered log (click to expand)

script returned exit code 1

:information_source:  This is an automatic message

:white_check_mark: Build finished in 3m 42s
Build command:
mvn clean verify -B -e -Daudit -amd -pl \
assemblies/core/lib,assemblies/lib,plugins/streaming/impls/mqtt

:ok_hand: All tests passed!
Tests run: 40, Failures: 0, Skipped: 0    Test Results

:information_source:  This is an automatic message

Done!


Add missing .ts extension in application.js example

Description 📖
In the latest Vite, the default falls to .js, therefore .ts needs to be explicitly specified.
The Fix 🔨
By updating the example to include the .ts file extension

Hi Ostap!
This is not necessary, as the helper is provided by Vite Ruby explicitly for this purpose, and will add the .ts extension.


Extend system requirements to older versions of macOS

Our Save to Pocket extension says that it requires macOS 10.14 or later. However, Safari 12 can run on previous versions of macOS.
This ticket is to extend support to previous versions. See this slack thread for more info.

This is an old ticket, and most likely no longer applies given the available versions of MacOS and Safari. Closing.


Updated the content for the terms page for GDPR

What is the context of this PR?
Updated content for static page for GDPR compliance.
How to review
Check the content is correct and formatted correctly.

Smart quotes have been added and also missing string has been added.
General code improvements should be done as part of another ticket I believe as a general improvement to templates/CSS.

@armstrongb Are you able to approve the branch?

LGTM


Doc - Create subnet with a delegation is the same as Create subnet

File: themes/default/content/docs/reference/pkg/azure-native/network/subnet.md
Could you change code example for section "Create subnet with a delegation", because it doesn't explain how make a delegation.
It's the same code as "Create subnet" example
thanks a lot

It looks like the upstream example from which this is derived doesn't actually pass any parameters for delegation. I've filed https://github.com/Azure/azure-rest-api-specs/issues/14936


Set program initial day based on local TZ, not UTC

Problem: When using this theme over here in the America/Los_Angeles time zone (GMT-8 / GMT-9), for a 2-day event, during the event on the first day, the program page defaulted to showing the 2nd day. And on the 2nd day of the event, the program went back to showing the 1st day.
Tracing the problem down, it looks like the JS Date API doesn't provide good functions for converting between UTC and local time zones well. The code in program.js was taking the user's days' strings, which are representing local time zone days, instantiating a Date in JS (which only creates a UTC time zone date), and then compares the day part to the user's JS runtime's current Date instance's day part.
This issue probably doesn't manifest for people whose time zone is close enough to GMT / UTC.
Solution:
Treat the user provided day string from the program as the day in the local time zone. Construct an analogous string in the user's JS runtime and then do string comparison. This works around JS's lack of time zone support in the Date API to compare 2 "local dates" (dates that are not representing an absolute time pinned to the UTC time zone).

Thanks for looking into this and proposing a solution. Indeed, the template is struggling with timezone, not only for showing the correct date in the program but also for the live indications as someone noticed already earlier (see #32).
I decided now to properly fix it by using UTC timestamps everywhere and calculating these timestamps correctly based on the local timezone (or overwritten via site.conference.tz property). This simplifies a lot, and so I also got rid of the "using the current date and setting the time to midnight" inside program.js. As you pointed out correctly, this approach was flawed. You can find the fixed implementation as version 3.6.6 already part of main.
As such, the proposed changes here are no longer required. Thank you anyway!

Thanks for the update, and also thanks for the other work that was done already to fix the problems.


[nitro-protocol] Overhaul docs website

Putting this here to track progress and generate deploy previews.
I suspect this link will not stay up to date with this branch:
https://5eb42d9abcf4b6dfc27313b1--nitro-protocol.netlify.app
(quirk of our current build/deploy pipeline -- you can an up to date link by looking in circle logs under release-pull-request  )
Refs
https://openzeppelin.com/contracts/ <- a great example to model our site after

Latest deploy preview at https://5ecd36de2396fe1470c237a7--nitro-protocol.netlify.app/

Latest preview at https://5ed534131c8448eb0c32794b--nitro-protocol.netlify.app

Latest deploy preview at https://5ed79469a3cd237555499ae3--nitro-protocol.netlify.app


Update systemd-resolved script for Ubuntu 20.04

Systemd is also available on Ubuntu 20.04. The updates will allow the provisioning script to run.

Thanks @mirkop-mattr! How did you test this? I guess we should explitity add Ubuntu 20.04 as a target to our tests and Packer templates.

Thanks @mirkop-mattr! How did you test this? I guess we should explitity add Ubuntu 20.04 as a target to our tests and Packer templates.

Apologies I can try to run the tests tomorrow. I have actually build a Ubuntu 20.04 AMI myself, but with a packer template that did not include 16.04 anymore and looked slightly different. So yes it is probably a good idea to run the testsuite.

@mirkop-mattr okay as part of this PR I think we also need to include examples + tests for Ubuntu 20.04 otherwise there's no way for our automated test suite to continually validate that this change works correctly. Are you able to add Ubuntu 20.04 to the Packer templates and tests?
Alternatively, you could also try another approach here: https://github.com/hashicorp/terraform-aws-consul/pull/197/files#diff-6c605a7da1f7d7fe7888c86e0165164c3a93d4059ac17be4e64c6cfbe6dc341bR85 that somehow works on all Ubuntu versions greater than 18.04. That way we won't have to explicitly list each distribution. Note: I'm assuming that's probably a bit more difficult than what I've proposed above.

Doh, race condition! Looks like I duplicated @robmorgan's comments. Sorry about that 😁

Thanks for the feedback! Do you want me to update the circle ci configuration as well?

@mirkop-mattr okay as part of this PR I think we also need to include examples + tests for Ubuntu 20.04 otherwise there's no way for our automated test suite to continually validate that this change works correctly. Are you able to add Ubuntu 20.04 to the Packer templates and tests?
Alternatively, you could also try another approach here: https://github.com/hashicorp/terraform-aws-consul/pull/197/files#diff-6c605a7da1f7d7fe7888c86e0165164c3a93d4059ac17be4e64c6cfbe6dc341bR85 that somehow works on all Ubuntu versions greater than 18.04. That way we won't have to explicitly list each distribution. Note: I'm assuming that's probably a bit more difficult than what I've proposed above.

Do you have any suggestions for another approach? I could check if the system we are running on is using systemd.

Any updates on merging this?

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement
Learn more about why HashiCorp requires a CLA and what the CLA includes

Mirko Pluhar seems not to be a GitHub user.
You need a GitHub account to be able to sign the CLA. If you already have a GitHub account, please add the email address used for this commit to your account.
Have you signed the CLA already but the status is still pending? Recheck it.

@mirkop-mattr , can you sign that CLA?

Any chance we can kick off the signing of the CLA again? I have changed email addresses for this account. Or shall I raise a new PR?

I don't see any way to do it other than a new PR. Thx!

Closing this and raising https://github.com/hashicorp/terraform-aws-consul/pull/217 using different github account.


Request to add an endpoint that lists semesters for which data is available

Would be nice if there were an endpoint that lists all the semesters for which there is course data is available (eg. Fall 2022, Summer 2022, Spring 2022, …, J-Term 2021, Fall 2020) so that front end devs don’t have to hard code the semesters or make assumptions like “X term schedule will be always available starting in Y month” or “only schedules from the past Z semesters are available.”
I’m also curious to know how does the /current/current endpoint determines the current semester now? Is it just comparing the current date with some hard-coded dates like 9/1 or is it doing something fancier like scraping the academic calendar?

Hey! /current/current just outputs hardcoded stuff, nothing advanced. I'm planning on adding something like what you suggested to the /info endpoint of schedge v2, v1 likely will not have this functionality, as it's quite a bit harder to add with the current architecture.

Got it. Thank you!

This has been implemented in Schedge v2, but hasn't been released yet. Will update here when the release happens.

This has been released; Schedge v2 isn't fully ready for use, but the API is documented (poorly) at https://nyu.a1liu.com/api/#/paths/~1api~1terms/get , if you'd like to start using it.

Thanks a lot! I noticed that some schools like Stern, Tisch, and Tandon now have their undergraduate and graduate departments all under the same school but CAS/GSAS and Steinhardt still have two different schools each, one for undergraduate and one for graduate departments. Is this change intentional from v1, where undergraduate and graduate schools are all separate?

Yeah. It's due to the new scraping source, they don't make a distinction between grad and undergrad in the new NYU website for those schools. How high priority is the distinction for your app?

Oh that makes sense. I just want to be able to differentiate grad and undergrad schools, similar to how Bobcat Search used to worked. I am relying on the v1 /school endpoint for that right now, which works mostly fine.
Upon some digging, I realized that a NYU_CLS_WRK_ACAD_CAREER$16$ field was set to UGRD in the POST request when “Undergraduate” is selected from the “Academic Career” drop down menu on the left of sis.nyu.edu. The value for “Graduate” is GRAD and apparently there are a lot more academic careers than just grad vs undergrad…

Maybe this field can be set when just scraping subjects? However sometimes the web page redirects back before the request finishes for some reason. Not sure how this might impact the scraping process. I am also comfortable with just using v1 for schools and subjects so no need to rush this at all.

Okay it is actually trivial for me to reverse engineer the school and school codes from what the v2 endpoint returns on the client side. No need for changes now.


Using the "request" API to be able to use "replays" API to be able to parse .dem file.. ?

Hello,
I'm learning to parse demo files. And I've been using the replays API with a match ID to get the "replay_salt" to get the .dem file.
That works well but I've noticed I can't use the "replays" API on some recent matches. I'm guessing it's because the match is not parsed yet?
If I manually request (from webpage) for a match to be parsed, I can get the proper answer from the "replays" API.
But I don't quite get how I can use the API to request a match to be parsed, and I don't understand how the track the parsing process from API. (https://docs.opendota.com/#tag/request) Can I get an example of how to use it?
Is there another way for me to get the replay_salt of a match without odota parsing it first?

@cbt13 did you ever find an example of how to download the .dem file of a replay?

@cbt13 did you ever find an example of how to download the .dem file of a replay?

I did, yes, by relying on another API. But I also know there is another way to do it, I just don't know how.
I used this iirc, been a long time since I used this;
https://docs.opendota.com/#tag/replays


When defining DCR for syslog collection using AMA I am unable to select Account or Namespace.

I have a workspace defined for Sentinel, and another one for random QA resources, and neither are showing up in the popup and the search will yield no results.
Azure documentation issue guidance
Thanks for opening an issue in the Azure technical documentation repository.
We use GitHub issues as the primary channel for customer and community feedback about the Azure documentation.
Creating an issue
We prefer that you create documentation feedback issues using the Feedback link on the published article - the feedback control on the doc page creates an issue that contains all the article details so you can focus on the feedback part.
You can also create a feedback issue here in the repo. If you do this, please make sure your issue lists:

[ ] The relevant Azure service or technology.
[ ] A link to the published documentation article that you have feedback about.
[ ] Clear, specific feedback that the author can act on.

Pull requests and article contributions
If you know the change that is needed in an article, we encourage you to submit the changes directly using a pull request. If the change is large, or if you want to contribute an entire article, follow these guidelines:

[ ] Don't surprise us with a big pull request or a pull request with a new article! Submit an issue that describes the details of the proposed large change or new article.
[ ] Include the service or technology area.

We'll route the issue to the appropriate content team for review and discussion.
Tech support and product feedback
If you would like to contact Microsoft about other things, such as product feedback or tech support, please review these guidelines:

If you need technical support using Azure, the paid and free support options are described here: https://azure.microsoft.com/support/options/.

Each article in the Azure technical documentation contains a product feedback button - it's best to submit product feedback directly from a relevant article. Otherwise, you can submit product feedback for most Azure products in the following product feedback forum: https://feedback.azure.com/d365community/forum/79b1327d-d925-ec11-b6e6-000d3a4f06a4.

I missed the part about creating the DCR in the same region.

@JAK-Insight Glad to know that you were able to self-resolve the issue. Let us know if you have any further questions with regards to this topic. Thanks.


refactor: remove circular dependency workaround

Related to #319

It just.. works?

Yes, because we removed the debouncing logic


Mockoon DOWN

🚨 Service Alert: Check the details below
Monitor Details

Monitor Name: Mockoon
Incident Status: TRIGGERED
Severity: critical
Monitor Status: DOWN
Monitor Health Checks: 1
Monitor Failure Threshold: 1

Actions

View Monitor

[start_datetime:1732941960] [end_datetime:1732928520]

The incident has been auto resolved
Total downtime: 106 minutes


BED with BayesFlow and Pytorch

Short tutorial/example. Feedback welcome!

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 49.70%. Comparing base (21d23b2) to head (b9c2b49).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##              dev     #199      +/-   ##
==========================================
- Coverage   52.16%   49.70%   -2.46%
==========================================
  Files         142      142
  Lines        3213     3213
==========================================
- Hits         1676     1597      -79
- Misses       1537     1616      +79

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

LGTM, thanks again!


systemtest: suppress kafka logs for successful tests

go test -v output is very noisy. Consider only emitting Kafka client logs if the test fails.

I was planning to change the logging level to info rather than debug. That'll reduce the verbosity.

That sounds good. I think I'd still prefer no logs if the test passes, but let's see how it looks.


Allow multiple @save_to decorators on the same function

Is your feature request related to a problem? Please describe.
I can add multiple @load_from decorators to the same function, it would make sense to me to also be able to add multiple @save_to decorators. For example, if I want to save the output of the function to both a data lake and also to a data warehouse.
Right now, if I try this, I get the following error:
InvalidDecoratorException: No saver class found for type: typing.Dict[str, typing.Any] specified by output type: typing.Dict[str, typing.Any] in node: save.clean_poster_history generated by function: clean_poster_history.

Describe the solution you'd like
Multiple @save_to decorators on the same function save the output of the function multiple times.
Describe alternatives you've considered
I now create functions which depend on the one I want to save like this.
@save_to.bigquery(table_name="poster_history")
def poster_history_bigquery(poster_history: ibis.Table) -> ibis.Table:
    return poster_history

Hey! Good catch. This is actually supported -- you'll have to use the target_ parameter https://hamilton.dagworks.io/en/latest/reference/decorators/save_to/.
A little unclear as to why, but it's a valid way of doing it!

Ah ok, thanks! By adding both target_ and output_name_ the error went away!

Ah ok, thanks! By adding both target_ and output_name_ the error went away!

Great! Let us know if there's a way to improve docs to make it clearer :)

Can't think of any way I think I just overlooked it. It could help to show a message saying that these arguments could help in cases where these errors occur and the node that causes the error starts with save.


add description to package.json

Add the description to package.json, so something shows up when I look at dependencies on github.

Thanks for catching that these were missing!


joker: 0.12.2 -> 0.12.4

Motivation for this change
Version bump
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[x] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Thanks for the review @gazally, and sorry for the delay in updating this. I've removed sum256dir in the postBuild step which seemed to be the correct place to do it, but since I'm not very experienced with nix please let me know if I should have done it another way.

This pull request has been mentioned on Nix community. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/49


[2.1]Add support new EC2 instance types for eks cluster

Related issue: https://github.com/rancher/rancher/issues/16626


Sorceress classes with Staticfield

Added Lightning Sorc, added StaticField to Blizzard and HydraOrb Sorc, adjusted Distance to Attack

No no no no, not merging this :D

One change per PR relating to the PR title
New builds in separate PRs as well, please!
If you plan to add static to sorceresses' builds other than nova, you need to take the range of the mob and static skill level into consideration as static doesn't have a large range with 1 base point in it.


[syn] Use latch-based register file in yosys

Add a technology map for latches (only works with nandgate45 library
at the moment)
Add a real latch-based clock gating cell
Update timing path reporting to differentiate between register and
latch paths
Update summary results in README to reflect the latch-based numbers,
plus add numbers for a micro-riscy-style (RV32EC) config

Signed-off-by: Tom Roberts<EMAIL_ADDRESS>

Note that the timing path groups changed as part of this PR to group all I/Os into in2reg, reg2out and in2out groups as I thought that was a bit simpler. Can change it back if anyone strongly prefers the original style.

Good plan - I'll increase the number to 1k


HTML comments in Markdown break HTML page generation

I noticed that if I use <!-- comment --> in markdown files used for the Manual, I get an error when building the whole page:
/Users/amed/Development/RxJSNext/node_modules/esdoc/node_modules/ice-cap/out/src/IceCap.js:339
              throw _iteratorError;
              ^

TypeError: Cannot read property '1' of null
Please report this to https://github.com/chjj/marked.
    at Object.sanitizer (/Users/amed/Development/RxJSNext/node_modules/esdoc/out/src/Publisher/Builder/util.js:92:44)
    at InlineLexer.output (/Users/amed/Development/RxJSNext/node_modules/esdoc/node_modules/marked/lib/marked.js:612:26)
    at Parser.tok (/Users/amed/Development/RxJSNext/node_modules/esdoc/node_modules/marked/lib/marked.js:1075:50)
    at Parser.parse (/Users/amed/Development/RxJSNext/node_modules/esdoc/node_modules/marked/lib/marked.js:935:17)
    at Function.Parser.parse (/Users/amed/Development/RxJSNext/node_modules/esdoc/node_modules/marked/lib/marked.js:922:17)
    at marked (/Users/amed/Development/RxJSNext/node_modules/esdoc/node_modules/marked/lib/marked.js:1218:19)
    at markdown (/Users/amed/Development/RxJSNext/node_modules/esdoc/out/src/Publisher/Builder/util.js:86:42)
    at ManualDocBuilder._convertMDToHTML (/Users/amed/Development/RxJSNext/node_modules/esdoc/out/src/Publisher/Builder/ManualDocBuilder.js:295:39)
    at /Users/amed/Development/RxJSNext/node_modules/esdoc/out/src/Publisher/Builder/ManualDocBuilder.js:212:30
    at /Users/amed/Development/RxJSNext/node_modules/esdoc/out/src/Publisher/Builder/ManualDocBuilder.js:228:13

We actually really need HTML comments because we run code in markdown using https://github.com/Widdershin/markdown-doctest, and sometimes we need to skip test for a particular code example, using the comment <!-- skip-example -->.

I released the v0.4.6 that fixes this bug.

Thanks for accepting PRs :)

@staltz @h13i32maru Guys, I run into this error with the latest esdoc. I have a <!-- comment --> in my project's README.md. Here is the output:
resolve: extends chain
resolve: necessary
resolve: access
resolve: unexported identifier
resolve: undocument identifier
resolve: duplication
resolve: ignore
resolve: link
resolve: markdown in description
resolve: test relation
output: badge.svg
output: identifiers.html

TypeError: Cannot read property '1' of null
Please report this to https://github.com/chjj/marked.
    at Object.sanitizer (/Users/guiguan/Documents/Projects/SBS/dbenvy-ci-controller/node_modules/esdoc/out/src/Publisher/Builder/util.js:89:46)
    at InlineLexer.output (/Users/guiguan/Documents/Projects/SBS/dbenvy-ci-controller/node_modules/marked/lib/marked.js:612:26)
    at Parser.tok (/Users/guiguan/Documents/Projects/SBS/dbenvy-ci-controller/node_modules/marked/lib/marked.js:1075:50)
    at Parser.parse (/Users/guiguan/Documents/Projects/SBS/dbenvy-ci-controller/node_modules/marked/lib/marked.js:935:17)
    at Function.Parser.parse (/Users/guiguan/Documents/Projects/SBS/dbenvy-ci-controller/node_modules/marked/lib/marked.js:922:17)
    at marked (/Users/guiguan/Documents/Projects/SBS/dbenvy-ci-controller/node_modules/marked/lib/marked.js:1219:19)
    at markdown (/Users/guiguan/Documents/Projects/SBS/dbenvy-ci-controller/node_modules/esdoc/out/src/Publisher/Builder/util.js:80:41)
    at IndexDocBuilder._buildIndexDoc (/Users/guiguan/Documents/Projects/SBS/dbenvy-ci-controller/node_modules/esdoc/out/src/Publisher/Builder/IndexDocBuilder.js:73:44)
    at IndexDocBuilder.exec (/Users/guiguan/Documents/Projects/SBS/dbenvy-ci-controller/node_modules/esdoc/out/src/Publisher/Builder/IndexDocBuilder.js:49:30)
    at publish (/Users/guiguan/Documents/Projects/SBS/dbenvy-ci-controller/node_modules/esdoc/out/src/Publisher/publish.js:146:58)

If I remove that comment in README.md, it works.


add autofocus

autofocus helps a lot

Not a big fan tbh, as it hijacks the keyboard. And on mobile, it shows the keyboard on load, which is very bad experience.
I guess listening on keyboard events would be a better option here.


Export queue and channel metrics

The image contains the MQ exporter built-in and Ive enabled by env. variable: MQ_ENABLE_METRICS true.
Queue manager returns global statistics. However, it does not return any channel or queue related metrics. We would like to moniotor few application queues, to better understand the load characteristic of planned integration. Is there a way to enable channel and queue related metrics?
PS. If you have any documentation of the MQ exporter metrics, configurtation, please share it as well.

Only queue manager-level metrics are exposed at the moment.  This is because we need to introduce a new mechanism to specify which individual queues and channels to monitor (MQ doesn't allow a wildcard subscription here, so we need to name specific queues).  Currently, if you want to do this, you can run your own metrics process, as per the mq-metric-samples

+1 would be a very useful feature

Only queue manager-level metrics are exposed at the moment. This is because we need to introduce a new mechanism to specify which individual queues and channels to monitor (MQ doesn't allow a wildcard subscription here, so we need to name specific queues). Currently, if you want to do this, you can run your own metrics process, as per the mq-metric-samples

@arthurbarr - Any updates on exposing queue metrics using prometheus?

:+1:


Invalid assemble list for x64

Hello Mithreindeir,
This is a very good product, thanks for you developing it.
Now I can't find the root cause, I faced the following disassemble code.
00:   4c 8d 44 24 20                    lea     r8, [rsp+0x00000020]
05:   49 83 00 01 4d                    add     qword [r9], 0x4d
0a:   8b 00                             mov     eax, dword [rax]

But I expected it as below, and it works as I expected.
00:   4c 8d 44 24 20                    lea     r8, [rsp+0x00000020]
05:   49 83 00 01                       add     qword [r8], 0x01
09:   4d 8b 00                          mov     r8, qword [r8]

What is wrong do you know?
Can you please advise me?
Thank you very much in advance.

Hello Mithreindeir,
I found it, but I don't know this modification is good or not.
Please check it?
First, in x64.ins:
8300 add Ev Ib

When reading 83 and 00, the stream goes to the next pointer.
But in this case, the part of 00 means a register number.
So, at x86.c:37
    n = trie_lookup(root, stream + iter, max - iter);
    iter += n->dist;

iter is moved to 2 bytes forward when 8300 is read becase n->dist is 2.
But in this case, it should be 1 byte only.
I don't know it is good by just replacing iter += n->dist by ++iter for all cases,
but for almost all cases it seems to be good.
What is it should be?


PowerShell tab font issue with light vs dark theme

Describe the bug
PowerShell tab font issue with light vs dark theme
To Reproduce
Steps to reproduce the behavior:

Setup Browser to light theme
Go to Deploy
Look at white area next to Bash. Can't see PowerShell tab (Color white)

Expected behavior
Need PowerShell to show in same font color as Bash and other tabs.
Additional context
Note, that when a release don't contain the ps1 script for postdeploy. The font is grey and disabled.

Created a new branch and fixed the code. The font was defaulting to white and now changed to none. Thus working for both light and dark themes.


Add RPM spec file for building on RHEL7

Tested on CentOS 7.1

@gmarkey Thank you. We will have a detailed look into this starting next year, ok? (because in germany we got public holiday).
@arnecls Can you take over?

Sure. One thing I have to note is that /Contrib was meant to be used for other things. Maybe we should create a new folder for these kind of things.
I will wrap my head around this in the next days.

The files can now be found in /dist


Added saml service provider DELETE functionality

Added REST endpoint for saml service provider DELETE method
Signed-off-by: Raymond<EMAIL_ADDRESS>

Changes Unknown when pulling 2ea969a653f7a22d7ce3372703bcc03ee30b5b34 on GESoftware-CF:feature/saml_service_provider_delete into ** on cloudfoundry:develop**.

Changes Unknown when pulling 2ea969a653f7a22d7ce3372703bcc03ee30b5b34 on GESoftware-CF:feature/saml_service_provider_delete into ** on cloudfoundry:develop**.

This was already implemented in develop branch, hence the compile error.  See https://github.com/cloudfoundry/uaa/commit/427a19753366ca4096c6adb713cfced708e9ad57#diff-f2cc228a4784cab137de8cfdcdd5d9da
I will move the 2nd commit in a separate pull request.

Change was implemented after the pull request opened, resulting in this being overwritten.

Change was implemented after the pull request opened, resulting in this being overwritten.
Refer to Sanjeev's comment. See 427a197#diff-f2cc228a4784cab137de8cfdcdd5d9da


Incomplete seasons

It appears that some seasons are incomplete.

import urllib.request
import json

league = "bl3"
year = 2022
match_day = 5

contents = urllib.request.urlopen(
    f"http://www.openligadb.de/api/getmatchdata/{league}/{year}/{match_day}"
).read()
data = json.loads(contents)
data

yields an empty list.
Incomplete seasons should be excluded, since they don't provide useful performance statistics.

Fixed with https://github.com/Diadochokinetic/AK-Tippspiel/commit/4c093bed4721bc5bb669b89ec7fa84b7837849e0


[WIP] Feature/shared type instance cache

The default implementation will use an shared cache for all fast adapter instances
Its now possible to implement an own caching solution for the type instances

Im not sure if the default implementation should be static in this case.


Window splitting logic seems wrong

This is mostly a discussion of the function split-window-sensibly. Right now, it's logic can be roughtly summarized as follows.

Can we split vertically, if so split vertically.
Otherwise, can we split horizontally, if so do so.
If the window is the only window, try splitting vertically.

I think this logic is backwards. As far as I'm concerned, splitting vertically is always permissible, as the worst case of less vertical space can be overcome easily by vertical scrolling. However horizontal scrolling is not, as we want to keep a minimum horizontal size for windows so things don't get squished.
Therefore, I think cases 1. and 2. should be swapped.

Here's an el-patch that seems to do what I want:
(el-patch-defun split-window-sensibly (&optional window)
  "Split WINDOW in a way suitable for `display-buffer'.
WINDOW defaults to the currently selected window.
If `split-height-threshold' specifies an integer, WINDOW is at
least `split-height-threshold' lines tall and can be split
vertically, split WINDOW into two windows one above the other and
return the lower window.  Otherwise, if `split-width-threshold'
specifies an integer, WINDOW is at least `split-width-threshold'
columns wide and can be split horizontally, split WINDOW into two
windows side by side and return the window on the right.  If this
can't be done either and WINDOW is the only window on its frame,
try to split WINDOW vertically disregarding any value specified
by `split-height-threshold'.  If that succeeds, return the lower
window.  Return nil otherwise.

By default `display-buffer' routines call this function to split
the largest or least recently used window.  To change the default
customize the option `split-window-preferred-function'.

You can enforce this function to not split WINDOW horizontally,
by setting (or binding) the variable `split-width-threshold' to
nil.  If, in addition, you set `split-height-threshold' to zero,
chances increase that this function does split WINDOW vertically.

In order to not split WINDOW vertically, set (or bind) the
variable `split-height-threshold' to nil.  Additionally, you can
set `split-width-threshold' to zero to make a horizontal split
more likely to occur.

Have a look at the function `window-splittable-p' if you want to
know how `split-window-sensibly' determines whether WINDOW can be
split."
  (let ((window (or window (selected-window))))
    (or (el-patch-swap
          (and (window-splittable-p window)
               ;; Split window vertically.
               (with-selected-window window
                 (split-window-below)))
          (and (window-splittable-p window t)
               ;; Split window horizontally.
               (with-selected-window window
                 (split-window-right))))
        (el-patch-swap
          (and (window-splittable-p window t)
               ;; Split window horizontally.
               (with-selected-window window
                 (split-window-right)))
          (and (window-splittable-p window)
               ;; Split window vertically.
               (with-selected-window window
                 (split-window-below))))
        (and (eq window (frame-root-window (window-frame window)))
             (not (window-minibuffer-p window))
             ;; If WINDOW is the only window on its frame and is not the
             ;; minibuffer window, try to split it vertically disregarding
             ;; the value of `split-height-threshold'.
             (let ((split-height-threshold 0))
               (when (window-splittable-p window)
                 (with-selected-window window
                   (split-window-below))))))))


Start polling immediately option when toggle is specified

Suggestion:  provide an option to start polling immediately even when a toggle is provided.   The current behavior is to poll immediately when a toggle is not present, but wait for the toggle when the toggle option is used.
This would support the use case where we want to start polling immediately on page load but provide the user the capability to toggle the polling OFF.  Thanks for your consideration.

Hey, @vanboom. This issue got resolved in the new 2.1.8 version. Let me know if it works for you.
Cheers 🍻


Parsing and stopcmd dont work

Both configparsing and stopcmd dont work with wings.

The config psrsing works fine. The config parse configuration will be sent to wings without any modifications. E.g the server.properties parsing works just fine

as i posted it allready in discord, is the file parsing nor working

configfile:
[/Script/AstroColony.EHServerSubsystem]
ServerPassword={{server.build.env.SRV_PW}}
Seed={{server.build.env.SEED}}
MapName={{server.build.env.MAP_NAME}}
MaxPlayers={{server.build.env.MAX_PLAYERS}}
SavegameName={{server.build.env.MAP_NAME}}
ShouldLoadLatestSavegame={{server.build.env.LOAD_SAVE}}
AdminList={{server.build.env.ADMINS}}
SharedTechnologies={{server.build.env.SHARED_TECH}}
OxygenConsumption={{server.build.env.OXYGEN}}
FreeConstruction={{server.build.env.FREE_CONSTRUCT}}
AutosaveInterval={{server.build.env.AUTOSAVE_INT}}
AutosavesCount={{server.build.env.AUTOSAVE_COUNT}}

parsing:
{
    "/AstroColony/Saved/Config/LinuxServer/ServerSettings.ini": {
        "parser": "file",
        "find": {
            "ServerPassword=": "ServerPassword={{server.build.env.SRV_PW}}",
            "Seed=": "Seed={{server.build.env.SEED}}",
            "MapName=": "MapName={{server.build.env.MAP_NAME}}",
            "MaxPlayers=": "MaxPlayers={{server.build.env.MAX_PLAYERS}}",
            "SavegameName=": "SavegameName={{server.build.env.MAP_NAME}}",
            "ShouldLoadLatestSavegame=": "ShouldLoadLatestSavegame={{server.build.env.LOAD_SAVE}}",
            "AdminList=": "AdminList={{server.build.env.ADMINS}}",
            "SharedTechnologies=": "SharedTechnologies={{server.build.env.SHARED_TECH}}",
            "OxygenConsumption=": "OxygenConsumption={{server.build.env.OXYGEN}}",
            "FreeConstruction=": "FreeConstruction={{server.build.env.FREE_CONSTRUCT}}",
            "AutosaveInterval=": "AutosaveInterval={{server.build.env.AUTOSAVE_INT}}",
            "AutosavesCount=": "AutosavesCount={{server.build.env.AUTOSAVE_COUNT}}"
        }
    }
}

And i have this with every imported egg.
Also stopcmd. You can use ^C or ^^C; both dont work and server stucks on shutdown

Dont use server.env thingy. You can use the the env without any prefix. Also maybe the path to the config file might not work as it seems to be an absolute path

Dont use server.env thingy. You can use the the env without any prefix. Also maybe the path to the config file might not work as it seems to be an absolute path

same result with the variable only.
As you see, does the parser work, but its not filled out

Here with variables only
[/Script/AstroColony.EHServerSubsystem]
ServerPassword={{SRV_PW}}
Seed={{SEED}}
MapName={{MAP_NAME}}
MaxPlayers={{MAX_PLAYERS}}
SavegameName={{MAP_NAME}}
ShouldLoadLatestSavegame={{LOAD_SAVE}}
AdminList={{ADMINS}}
SharedTechnologies={{SHARED_TECH}}
OxygenConsumption={{OXYGEN}}
FreeConstruction={{FREE_CONSTRUCT}}
AutosaveInterval={{AUTOSAVE_INT}}
AutosavesCount={{AUTOSAVE_COUNT}}

Do you mind sharing the image file so i can do tests with it?

Do you mind sharing the image file so i can do tests with it?

when i'm Back Home, i'll send it to you

@Marcel-Baumgartner
https://github.com/gameservertech/moonlight-images/tree/main/steamcmd/AstroColony

Oki. I see what you mean. Thats definitely a problem. The thing is a dont want to spend time fixing a stage of moonlight which is obsolete soon. You could put the config parsing in a startup script for now. If you dont want to continue making images until v2 has released or i fixed that i can totally understand you ^^

Ohh now i see it too :D the content are not stored :D

I dont know where the problem is exactly and debugging would take time. Time which i can use to improve the v2 config parsing. So i dont think it makes sense to fix it now

Its fine for me; i will update them, when its fixed

Fixed in v2  :3


fix: export QueryClientConfig interface

Export QueryClientConfig interface, so it can be easily reused in wrapper libraries

:tada: This PR is included in version 3.34.9 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 4.0.0-alpha.8 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Concurrency Control in DBMS

TConcurrency Control in DBMS
Introduction
Concurrency control is a process of managing simultaneous operations on the database without having them interfere with one another. The concurrency control that every transaction will have some isolation which means as the transaction is getting executed nothing parallel with other transaction and the transaction effect will remain permanent and durable on the database as if the transaction has gotten executed solo, so there is no interference between transactions execution.
There are different types of concurrency control techniques that are used to achieve isolation. Those techniques are Lock-Base, Time-Stampe, Multiversion-Concurrency, Validation Concurrency, Snapshot Isolation, Multiple Granularity. These are used to ensure serializability of schedules
Key takeaways
What are the 3-5 most important things the reader should understand or be able to do after reading this article?
Use this area to get your ideas down on the bulk of your article or tutorial.
Article quality
In this tutorial, we are going to be taking a deep dive looking into concurrency control,  types of locks, and strategies. Its completely beginner-friendly advantages.
References
https://databasemanagement.fandom.com/wiki/Concurrency_Control

Ensure that you fill all areas in the topic form before submitting it for approval. Thanks


Add end time?

Hey man
Great work with the add on!
Is it possible to add the end time of load shedding to the start time?
Can call it "Next Schedule" instead of Next Start for example
e.g. Next Schedule: 8:00am - 10:30am
Or add another line to show the end time. I think it's useful to show the end time as well not just the start time, and I know it is returned in the same string from the Eskom API.
Also is it possible for you to format the time from the ISO format to a more normal format? Just going on the screenshots here, but glancing at the code looks like it might already be formatted?
Thanks!

If your area is supported, then the schedule data is available in the attributes as can be seen below.

You can use this data to build your own sensors and panels in Home Assistant.
You can also change the formatting as you want it in Home Assistant.
The examples in the readme are just examples.
I've tweaked my own panels a bit after using it for a while, so I'll update the examples which you can use as reference if you don't know how to do it.

Awesome, thanks!

On 13 May 2022, at 09:52, Werner Pieterson @.***> wrote:

If your area is supported, then the schedule data is available in the attributes as can be seen below.
You can use this data to build your own sensors and panels in Home Assistant.
You can also change the formatting as you want it in Home Assistant.
The examples in the readme are just examples.
I've tweaked my own panels a bit after using it for a while, so I'll update the examples which you can use as reference if you don't know how to do it.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.


[GUI] Report does not have the identification of  device

Identify the device in the report.

Affected version: v0.5.0-alpha.1

Fixed in v0.5.0-rc.1


New-BcNuGetPackage - issue with generated dependencies in .nuspec

PLEASE DO NOT INCLUDE ANY PASSWORDS OR TOKENS IN YOUR ISSUE!!!
Describe the issue
when using New-BcNuGetPackage, and the app.json file contains a dependency to an appsource app.
The created .nuget package will contain
<dependencies>
  <dependency id="PUBLISHER.appname.c660d68a-f693-46df-b383-96c8769e2634" version="<IP_ADDRESS>" />
  <dependency id="Microsoft.Application" version="<IP_ADDRESS>" />
  <dependency id="Microsoft.Platform" version="24.0.24140.0" />
</dependencies>

while the microsoft feed for appsource symbols
https://dynamicssmb2.visualstudio.com/DynamicsBCPublicFeeds/_artifacts/feed/AppSourceSymbols
publishes packages with the following format
PUBLISHER.appname.symbols.c660d68a-f693-46df-b383-96c8769e2634
When using the generated nuget package in another project as dependency with the paket tool, it gives an error for not finding the dependency on the provided feeds.
Scripts used to create container and cause the issue
 $package = New-BcNuGetPackage -appfile $(System.DefaultWorkingDirectory)\$(Build.Repository.Name)_$(Build.BuildNumber).app -destinationFolder "$(System.DefaultWorkingDirectory)\nuget"

Full output of scripts
Create NuGet package
AppFile:
C:\agent\_work\112\s\xyz_xyz_Core_24.2024.1205.4202.app
NUSPEC file:
<?xml version="1.0" encoding="utf-8"?>
<package xmlns="[http://schemas.microsoft.com/packaging/2010/07/nuspec.xsd">](http://schemas.microsoft.com/packaging/2010/07/nuspec.xsd%22%3E)
    <metadata>
        <id>xyz.xyz.eebbf853-41a8-439c-9bee-da760802f82b</id>
        <version>24.2024.1205.4202</version>
        <title>xyz</title>
        <description>xyz</description>
        <authors>xyz</authors>
        <dependencies>
            <dependency id="PUBLISHER.appname.c660d68a-f693-46df-b383-96c8769e2634" version="<IP_ADDRESS>" />
            <dependency id="Microsoft.Application" version="<IP_ADDRESS>" />
            <dependency id="Microsoft.Platform" version="24.0.24140.0" />
        </dependencies>
    </metadata>
    <files>
        <file src="xyz_xyz_Core_24.2024.1205.4202.app" target="xyz_xyz_Core_24.2024.1205.4202.app" />
    </files>
</package>
Successfully created NuGet package (Size: 120Kb)
Preparing NuGet Package for submission
Submitting NuGet package

Could you add a parameter to New-BcNuGetPackage that uses Get-BcNuGetPackageId to buid the package ID, that would add .symbols to the name of the packageIDtemplate?
https://github.com/microsoft/navcontainerhelper/blob/main/NuGet/New-BcNuGetPackage.ps1
I tried with adding .symbols to the name of the dependency in app.json but the . gets stripped by  $nname = [nuGetFeed]::Normalize($name) :)
thanks!

You define the dependencyIdTemplate, which by default is:
[string] $dependencyIdTemplate = '{publisher}.{name}.{id}',

but... IMO normal nuget packages should have normal dependencies (not symbols) and symbols nuget packages should have symbols dependencies.

@DevHarmonize
I agree that symbol package should have dependency on symbol packages only and full package only on full packages.
For the tools like Paket and Nuget, when creating list of dependencies to download, it must be decided first, if you want to download symbols only or full packages. Based on that, the dependency names must be correctly created/resolved. When having dependency on AppSource app,   you can download symbol packages and use the MS public feed for the packages. Then you can use them to compile your app. But if you need to deploy the packages to environment, you need full packages, thus you will need to have access to some feed including the full packages of the AppSource apps. This must be provided by the publisher.
It means, everytime you need first to decide if you need full or symbols packages. Based on that different sources and package names will be used. Never mix both.


Can't run code using hydrogen or change the settings

Hydrogen doesn't exist in the packages tap in the navigation bar although I have it installed on my laptop and I have been working with it a long time ago but recently it just doesn't work!

@SaharAlaaQutb Have you tried some of the steps outlined in the troubleshooting guide: https://nteract.gitbooks.io/hydrogen/content/docs/Troubleshooting.html?


clean up dependencies for effortless installation of DomainLab

Can you please provide a more detailed description of this task?
What does 'effortless installation' refer to? Both through cloning the repo and using pip, the installation was straightforward and did not lead to any dependency-related issues for me.

If that is the case, we could leave it, I mentioned this issue since you once told me you had difficulties installing it.

Yes, but I think it was more connected to some pip issue. Tried it in a new container and works now


fix: add missing expect_ids/no_expect_ids

Certain tests that check for a specific status code do not contain expect_ids or no_expect_ids. This pr aims to address that, so that if these tests are not being ran against a specific server, the test can still be used to check if the rule matches or not.

I don't think that works. If status is 400, then no rule will be found in the log that matches. If status was not 400, then the test will already fail, regardless of the log contents.
I don't really understand what you are trying to achieve. Could you try to explain your usecase?

Essentially we've developed a WAF and are transpiling core rule set to our WAF language. To ensure that the rules are correctly transpiled we are also transpiling the tests to test if the rules work.
One of the things we've come across is tests that are tied to a particular rule but aren't actually testing if the rule matches or not but are testing the underlying web server. Initially we thought that maybe still crs may match on the rule but that isn't the case as you've highlighted.
Would it make sense to separate these tests out as tests that are specifically for the web server and not crs itself?

Tests where we check the status code for failure and not for a matching rule in the log are the only way to test the behaviour for that rule for certain backends. As you say, different backends behave differently, which is why we've come up with the concept of "platform overrides". Under https://github.com/coreruleset/coreruleset/tree/main/tests/regression you'll find multiple "override" files that we use to adapt our tests to different backends. Our tests target httpd by default.
Overrides work by supplying them to go-ftw via the --overrides flag. Whatever we specify for the override replaces the assertions of the original rule.

Ok no worries, makes sense


how to goto fullscreen when click the item of the recyclerview?

how to goto fullscreen when click the item of the recyclerview?

Hi, thanks. I thought about that, but it is not in scope now. You can manually setup the item click event (see facebook sample) and save/restore the playback timestamp in new fullscreen Activity too, remember to use startAciticyForResult so you can obtain the playback state back to original list.
I want to add a better transition (like Youtube), but it is not in the priority list now.

Hi Eneim,
Is this implemented or on the plan right now?


move to observe instead of observeChanges

Related to #195.
This should allow for transformed documents, but not only the collection transform but also cursor transform.
Also removed the need to find the index of changes by looking through the whole collection.
Not sure about it performace-wise.
@Urigo You have a good scenario for checking the performance of this vs observeChanges?

Looks fine.
Have you checked the 2 scenarios of the issue?
also, please make sure this works as well:
https://github.com/Urigo/meteor-angular-socially/issues/12


"not enough resource" should be more specific

Too many questions like "not enough resource, what exactly is not enough?" ...

I haven't checked the code of resource package, maybe I can enhance this after that, or maybe @jschwinger23 can do this if available...

我来


Remove metric kind "Observer"

Remove metric kind "Observer" when all new metric kind will be implemented

this was already removed in https://github.com/open-telemetry/opentelemetry-js/pull/1137


[bug]: Cannot install npx shadcn@latest add sidebar-07

Describe the bug

Affected component/components
sidebar
How to reproduce
npx shadcn@latest add sidebar-07
Codesandbox/StackBlitz link
No response
Logs
No response
System Info
windowns 11

Before submitting

[X] I've made research efforts and searched the documentation
[X] I've searched for existing issues

Did you run the npx<EMAIL_ADDRESS>before ?
Maybe you modified the path or name of the .cc then, and that is the reason that the file cannot be found now.
I think 2 methods that you can give them a try.

Delete the file components.json which includes the former path of your style files, and run the npx<EMAIL_ADDRESS>again to refresh the configuration.
If you don't wanna run it again, navigate to the components.json and modify the path of the error file shown in your screenshot

Hope it will help, good luck!

The error you're encountering is because the global.css file is not present in the specified path.
Please ensure that the global.css file exists in the following path:
C:\Users\welington.carlos\projetos\gateway-front\app\styles\global.css


Update README.md

I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=ru
Description of changes:

"WARN Variable specified_key not found in /en/compute/concepts/instance-groups/variables-in-the-template.md\nWARN Variable unknown_key not found in /en/compute/concepts/instance-groups/variables-in-the-template.md\nWARN Variable unknown_key not found in /en/compute/concepts/instance-groups/variables-in-the-template.md\nWARN Variable specified_key not found in /en/compute/concepts/instance-groups/variables-in-the-template.md\nWARN Variable unknown_key not found in /en/compute/concepts/instance-groups/variables-in-the-template.md\nWARN Variable unknown_key not found in /en/compute/concepts/instance-groups/variables-in-the-template.md\nWARN Variable label not found in /en/monitoring/concepts/querying.md\nWARN Variable host not found in /en/monitoring/concepts/visualization/dashboard.md\nWARN Variable myparm not found in /en/monitoring/concepts/visualization/dashboard.md\nWARN Variable label not found in /en/monitoring/concepts/querying.md\nWARN Variable isotime | clean_resource_name not found in /en/solutions/infrastructure-management/packer-quickstart.md\nWARN Variable isotime | clean_resource_name not found in /en/solutions/infrastructure-management/packer-quickstart.md\nWARN Variable .TablePathPrefix not found in /en/ydb/sdk/index.md\nWARN Variable ydb-cli not found in /en/ydb/quickstart/examples-ydb-cli.md\nWARN Variable ydb-cli not found in /en/ydb/quickstart/examples-ydb-cli.md\nWARN Variable ydb-cli not found in /en/ydb/quickstart/examples-ydb-cli.md\nWARN Variable ydb-cli not found in /en/ydb/quickstart/examples-ydb-cli.md\nWARN Variable ydb-cli not found in /en/ydb/quickstart/examples-ydb-cli.md\nWARN Variable .TablePathPrefix not found in /en/ydb/sdk/index.md\nWARN Variable ydb-cli not found in /en/ydb/maintenance/backup_and_recovery.md\nWARN Variable label not found in /ru/monitoring/concepts/querying.md\nWARN Variable host not found in /ru/monitoring/concepts/visualization/dashboard.md\nWARN Variable myparm not found in /ru/monitoring/concepts/visualization/dashboard.md\nWARN Variable label not found in /ru/monitoring/concepts/querying.md\nWARN Variable isotime | clean_resource_name not found in /ru/solutions/infrastructure-management/packer-quickstart.md\nWARN Variable isotime | clean_resource_name not found in /ru/solutions/infrastructure-management/packer-quickstart.md\nWARN Variable .TablePathPrefix not found in /ru/ydb/sdk/index.md\nWARN Variable .TablePathPrefix not found in /ru/ydb/sdk/index.md\nBuild time: 73873.284ms\n"

"Source are stored: \nhttps://storage.yandexcloud.net/nanov94-os/yfm-fc7ea68a-ecd2-4fe8-9d89-5fe8eda48b7f/en/index.html,\nhttps://storage.yandexcloud.net/nanov94-os/yfm-fc7ea68a-ecd2-4fe8-9d89-5fe8eda48b7f/ru/index.html"

"\n\n\n"


Is it possible to use GeoJSON and Vector tiles?

Thank you for your amazing work!

For GeoJSON, your implementation of TileStreamProvider can fetch the relevant tile in a geoJSON file.
All you need is a library or custom code to deal with that kind of file.
Regarding vector tiles, you need a renderer to convert a vector tile into an image. The TileStreamProvider is expected to return a InputStream of an image. Again, you will need a library for that.

Ok nice, thank you for the info


refactor error handling for projects

[ ] I added an entry to CHANGELOG.md if knowledge of this change could be valuable to users.

Here is a brief summary of what I did:

 Automatische Umwandlung von Postgres-Errors in unser Error-Enum entfernen und sinnvolle Fehlermeldungen bauen

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

304 of 313 (97.12%)  changed or added relevant lines in 7 files are covered.
11 unchanged lines in 8 files lost coverage.
Overall coverage increased (+0.01%) to 89.94%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

services/src/projects/postgres_projectdb.rs
116
118
98.31%

services/src/pro/projects/postgres_projectdb.rs
137
144
95.14%

Files with Coverage Reduction
New Missed Lines
%

services/src/datasets/create_from_workflow.rs
1
93.57%

services/src/handlers/datasets.rs
1
94.96%

services/src/pro/contexts/mod.rs
1
63.57%

services/src/pro/handlers/users.rs
1
96.76%

services/src/pro/quota/mod.rs
1
93.9%

services/src/handlers/layers.rs
2
87.12%

services/src/handlers/wcs.rs
2
88.28%

services/src/pro/contexts/postgres.rs
2
97.33%

Totals

Change from base Build<PHONE_NUMBER>:
0.01%

Covered Lines:
106449

Relevant Lines:
118356

💛  - Coveralls


twc kills node red

Hi,
if got these exit several times:
Aug 23 20:56:44 smarthome node-red[28675]: 23 Aug 20:56:44 - [red] Uncaught Exception:
Aug 23 20:56:44 smarthome node-red[28675]: 23 Aug 20:56:44 - TypeError: Cannot read property 'data' of undefined
Aug 23 20:56:44 smarthome node-red[28675]:     at /mnt/dietpi_userdata/node-red/node_modules/node-red-contrib-twc-weather/pws-current.js:60:40
Aug 23 20:56:44 smarthome node-red[28675]:     at runMicrotasks ()
Aug 23 20:56:44 smarthome node-red[28675]:     at processTicksAndRejections (node:internal/process/task_queues:94:5)
Aug 23 20:56:44 smarthome systemd[1]: node-red.service: Main process exited, code=exited, status=1/FAILURE
Aug 23 20:56:44 smarthome systemd[1]: node-red.service: Failed with result 'exit-code'.
Ive  got no Idea why this happens.

Hi @daniceguy1612  - Can you provide some additional information about how you were calling the PWS Observations node?
What version of Node-RED are you running?  What version of node-red-contrib-twc-weather ?
Line 60 is the console.log() call in the catch()
          try {
            const response = await axios.get('https://api.weather.com/v2/pws/observations/current?stationId=' + curStationId +'&format=json&units='+msg.twcparams.units+'&apiKey='+apiKey);
            //console.log(response.data)
            msg.payload = response.data;
            node.send(msg);
          } catch (error) {
            console.log(error.response.data);
            //console.log(error.response.status);
            node.warn(error.response.data);
            node.send(msg);
          }

thanks for your attention!
node red v 1.2.9
twc 0.4.1
Node.js  version: v15.13.0
in my pws-current.js is exactly what you post, what should i try?
heres my flow:
[{"id":"2bdd775d.9b8cb8","type":"tab","label":"Wetter","disabled":false,"info":""},{"id":"4118ba23.e1e234","type":"pws-observations","z":"2bdd775d.9b8cb8","name":"","stationid":"IOSCHE1","units":"m","apikey":"ba693fed.4c01f8","x":375,"y":120,"wires":[["8a74e813.b77cc8","8db68e90.e9147","fec0eea.eb7211","a13631a4.67eb9","bec5e8b1.234e18"]],"l":false},{"id":"86fc3eea.7823f","type":"ui_gauge","z":"2bdd775d.9b8cb8","name":"","group":"62acffe6.21fe7","order":4,"width":6,"height":3,"gtype":"gage","title":"Temperatur","label":"°C","format":"{{value}}","min":"-35","max":"40","colors":["#001eb3","#35ed5a","#ca3838"],"seg1":"-5","seg2":"25","x":1070,"y":20,"wires":[]},{"id":"fec0eea.eb7211","type":"debug","z":"2bdd775d.9b8cb8","name":"","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"payload","targetType":"msg","statusVal":"","statusType":"auto","x":430,"y":40,"wires":[]},{"id":"8a74e813.b77cc8","type":"change","z":"2bdd775d.9b8cb8","name":"Temperatur","rules":[{"t":"set","p":"payload","pt":"msg","to":"payload.observations[0].metric.temp","tot":"msg"}],"action":"","property":"","from":"","to":"","reg":false,"x":690,"y":60,"wires":[["86fc3eea.7823f","1c8320ac.ff1faf"]]},{"id":"8db68e90.e9147","type":"change","z":"2bdd775d.9b8cb8","name":"Niederschlag","rules":[{"t":"set","p":"payload","pt":"msg","to":"payload.observations[0].metric.precipTotal","tot":"msg"}],"action":"","property":"","from":"","to":"","reg":false,"x":690,"y":100,"wires":[["9aa55f59.1da7c"]]},{"id":"1563cf4e.fa8d21","type":"debug","z":"2bdd775d.9b8cb8","name":"","active":false,"tosidebar":true,"console":false,"tostatus":false,"complete":"false","statusVal":"","statusType":"auto","x":1090,"y":340,"wires":[]},{"id":"9aa55f59.1da7c","type":"ui_gauge","z":"2bdd775d.9b8cb8","name":"","group":"62acffe6.21fe7","order":6,"width":6,"height":3,"gtype":"wave","title":"Regen","label":"mm","format":"{{value}}","min":0,"max":"50","colors":["#00b500","#e6e600","#ca3838"],"seg1":"","seg2":"","x":1050,"y":100,"wires":[]},{"id":"a13631a4.67eb9","type":"change","z":"2bdd775d.9b8cb8","name":"Wind","rules":[{"t":"set","p":"payload","pt":"msg","to":"payload.observations[0].metric.windSpeed","tot":"msg"}],"action":"","property":"","from":"","to":"","reg":false,"x":670,"y":180,"wires":[["97baf1d5.7e78c","ef93ee2c.cd614"]]},{"id":"ef93ee2c.cd614","type":"ui_gauge","z":"2bdd775d.9b8cb8","name":"","group":"62acffe6.21fe7","order":8,"width":6,"height":3,"gtype":"compass","title":"Wind ","label":"km/h","format":"{{value}}","min":0,"max":"35","colors":["#00b500","#e6e600","#ca3838"],"seg1":"","seg2":"","x":1050,"y":180,"wires":[]},{"id":"92ad2057.1631f","type":"ui_button","z":"2bdd775d.9b8cb8","name":"","group":"62acffe6.21fe7","order":3,"width":2,"height":1,"passthru":false,"label":"Wetter","tooltip":"","color":"","bgcolor":"","icon":"wi-wu-cloudy","payload":"","payloadType":"date","topic":"","topicType":"str","x":35,"y":80,"wires":[["4118ba23.e1e234"]],"l":false},{"id":"97baf1d5.7e78c","type":"ui_chart","z":"2bdd775d.9b8cb8","name":"","group":"62acffe6.21fe7","order":9,"width":0,"height":0,"label":"Wind km/h","chartType":"line","legend":"false","xformat":"HH:mm","interpolate":"linear","nodata":"warte auf Daten","dot":false,"ymin":"","ymax":"","removeOlder":"24","removeOlderPoints":"","removeOlderUnit":"3600","cutout":0,"useOneColor":false,"useUTC":false,"colors":["#1f77b4","#aec7e8","#ff7f0e","#2ca02c","#98df8a","#d62728","#ff9896","#9467bd","#c5b0d5"],"outputs":1,"useDifferentColor":false,"x":1070,"y":220,"wires":[[]]},{"id":"a809ce7c.8ec05","type":"trigger","z":"2bdd775d.9b8cb8","name":"","op1":"","op2":"0","op1type":"date","op2type":"str","duration":"-5","extend":false,"overrideDelay":false,"units":"min","reset":"0","bytopic":"all","topic":"topic","outputs":1,"x":230,"y":160,"wires":[["4118ba23.e1e234"]]},{"id":"4ff21b4f.de6b74","type":"ui_slider","z":"2bdd775d.9b8cb8","name":"","label":"Auto","tooltip":"","group":"62acffe6.21fe7","order":1,"width":3,"height":1,"passthru":true,"outs":"end","topic":"topic","topicType":"msg","min":0,"max":"1","step":1,"x":70,"y":120,"wires":[["a809ce7c.8ec05"]]},{"id":"519cc84e.b15c68","type":"ui_chart","z":"2bdd775d.9b8cb8","name":"","group":"62acffe6.21fe7","order":7,"width":0,"height":0,"label":"Regen mm/h","chartType":"line","legend":"false","xformat":"HH:mm","interpolate":"linear","nodata":"warte auf Daten","dot":false,"ymin":"","ymax":"","removeOlder":"24","removeOlderPoints":"","removeOlderUnit":"3600","cutout":0,"useOneColor":false,"useUTC":false,"colors":["#1f77b4","#aec7e8","#ff7f0e","#2ca02c","#98df8a","#d62728","#ff9896","#9467bd","#c5b0d5"],"outputs":1,"useDifferentColor":false,"x":1070,"y":140,"wires":[[]]},{"id":"bec5e8b1.234e18","type":"change","z":"2bdd775d.9b8cb8","name":"Niederschlag","rules":[{"t":"set","p":"payload","pt":"msg","to":"payload.observations[0].metric.precipRate","tot":"msg"}],"action":"","property":"","from":"","to":"","reg":false,"x":690,"y":140,"wires":[["519cc84e.b15c68"]]},{"id":"1c8320ac.ff1faf","type":"ui_chart","z":"2bdd775d.9b8cb8","name":"","group":"62acffe6.21fe7","order":5,"width":0,"height":0,"label":"Temperaturverlauf","chartType":"line","legend":"false","xformat":"HH:mm","interpolate":"linear","nodata":"warte auf Daten","dot":false,"ymin":"","ymax":"","removeOlder":"24","removeOlderPoints":"","removeOlderUnit":"3600","cutout":0,"useOneColor":false,"useUTC":false,"colors":["#1f77b4","#aec7e8","#ff7f0e","#2ca02c","#98df8a","#d62728","#ff9896","#9467bd","#c5b0d5"],"outputs":1,"useDifferentColor":false,"x":1090,"y":60,"wires":[[]]},{"id":"ba693fed.4c01f8","type":"pwsapikey","name":"IOSCHE1"},{"id":"62acffe6.21fe7","type":"ui_group","name":"W1","tab":"81002e94.47829","order":1,"disp":false,"width":"6","collapse":false},{"id":"81002e94.47829","type":"ui_tab","name":"Wetter","icon":"wi-wu-clear","order":2,"disabled":false,"hidden":false}]

I will let your flow run for a while.  It seems to be working fine on my system.

It`s me again. Moved System from RPi to VM on QNAP NAS.
Still the same Probleme here. Any suggestions?
Apr 14 12:24:43 DietPi node-red[1608]: (Use `node --trace-deprecation ...` to show where the warning was created)
Apr 14 12:24:43 DietPi node-red[1608]: 14 Apr 12:24:43 - [info]
Apr 14 12:24:43 DietPi node-red[1608]: Willkommen bei Node-RED!
Apr 14 12:24:43 DietPi node-red[1608]: ===================
Apr 14 12:24:43 DietPi node-red[1608]: 14 Apr 12:24:43 - [info] Node-RED Version: v1.3.7
Apr 14 12:24:43 DietPi node-red[1608]: 14 Apr 12:24:43 - [info] Node.js  Version: v16.14.2
Apr 14 12:24:43 DietPi node-red[1608]: 14 Apr 12:24:43 - [info] Linux 5.10.0-13-amd64 x64 LE
Apr 14 12:24:44 DietPi node-red[1608]: 14 Apr 12:24:44 - [info] Paletten-Nodes werden geladen
Apr 14 12:24:45 DietPi node-red[1608]: 14 Apr 12:24:45 - [info] Dashboard version 3.1.6 started at /ui
Apr 14 12:24:45 DietPi node-red[1608]: 14 Apr 12:24:45 - [info] Einstellungsdatei: /mnt/dietpi_userdata/node-red/settings.js
Apr 14 12:24:45 DietPi node-red[1608]: 14 Apr 12:24:45 - [info] Kontextspeicher: default [module=memory]
Apr 14 12:24:45 DietPi node-red[1608]: 14 Apr 12:24:45 - [info] Benutzerverzeichnis: /mnt/dietpi_userdata/node-red
Apr 14 12:24:45 DietPi node-red[1608]: 14 Apr 12:24:45 - [warn] Projekte deaktiviert: editorTheme.projects.enabled=false
Apr 14 12:24:45 DietPi node-red[1608]: 14 Apr 12:24:45 - [info] Flow-Datei: /mnt/dietpi_userdata/node-red/flows_DietPi.json
Apr 14 12:24:45 DietPi node-red[1608]: 14 Apr 12:24:45 - [info] Server wird jetzt auf http://<IP_ADDRESS>:1880/ ausgeführt
Apr 14 12:24:45 DietPi node-red[1608]: 14 Apr 12:24:45 - [warn]
Apr 14 12:24:45 DietPi node-red[1608]: ---------------------------------------------------------------------
Apr 14 12:24:45 DietPi node-red[1608]: Die Datei mit den Flow-Berechtigungen wird mit einem vom System
Apr 14 12:24:45 DietPi node-red[1608]: generierten Schlüssel verschlüsselt.
Apr 14 12:24:45 DietPi node-red[1608]: Wenn der vom System generierte Schlüssel aus irgendeinem Grund
Apr 14 12:24:45 DietPi node-red[1608]: verloren geht, kann die Datei mit den Berechtigungen nicht
Apr 14 12:24:45 DietPi node-red[1608]: wiederhergestellt werden. Sie muss dann gelöscht und die
Apr 14 12:24:45 DietPi node-red[1608]: Berechtigungen müssen erneut eingestellt werden.
Apr 14 12:24:45 DietPi node-red[1608]: Es sollte ein eigener Schlüssel mit Hilfe der Option
Apr 14 12:24:45 DietPi node-red[1608]: 'credentialSecret' in der Einstellungsdatei vorgegeben werden.
Apr 14 12:24:45 DietPi node-red[1608]: Node-RED wird dann die Datei mit den Flow-Berechtigungen
Apr 14 12:24:45 DietPi node-red[1608]: bei der nächsten Übernahme (deploy) einer Änderung erneut
Apr 14 12:24:45 DietPi node-red[1608]: verschlüsseln.
Apr 14 12:24:45 DietPi node-red[1608]: ---------------------------------------------------------------------
Apr 14 12:24:46 DietPi node-red[1608]: 14 Apr 12:24:46 - [info] Flows werden gestartet
Apr 14 12:24:46 DietPi node-red[1608]: 14 Apr 12:24:46 - [info] Flows sind gestartet
Apr 14 12:24:46 DietPi node-red[1608]: 14 Apr 12:24:46 - [info] [mqtt-broker: MQTT Mosquitto] Verbindung zum Broker nodered@mqtt://<IP_ADDRESS>:1883 aufgebaut
Apr 16 08:24:27 DietPi node-red[1608]: 16 Apr 08:24:27 - [red] Uncaught Exception:
Apr 16 08:24:27 DietPi node-red[1608]: 16 Apr 08:24:27 - TypeError: Cannot read properties of undefined (reading 'data')
Apr 16 08:24:27 DietPi node-red[1608]:     at /mnt/dietpi_userdata/node-red/node_modules/node-red-contrib-twc-weather/pws-current.js:79:40
Apr 16 08:24:27 DietPi node-red[1608]:     at runMicrotasks (<anonymous>)
Apr 16 08:24:27 DietPi node-red[1608]:     at processTicksAndRejections (node:internal/process/task_queues:96:5)
Apr 16 08:24:27 DietPi systemd[1]: node-red.service: Main process exited, code=exited, status=1/FAILURE
Apr 16 08:24:27 DietPi systemd[1]: node-red.service: Failed with result 'exit-code'.
Apr 16 08:24:27 DietPi systemd[1]: node-red.service: Consumed 18min 5.866s CPU time.

Hi @daniceguy1612 -  I have deployed your example flow and will watch it over the next several hours / days.

@daniceguy1612 The flow has been running fine for 3 days.

Have you activated the Automatic Data reciving every Minute ? There is a Slider for it. The Error occours only when i collect the Data.

Yes, it's querying data every minute.

Can i do Something Else to find the Error? Activate deeper logging or Something?

Enable console logging.  In your ~/.node-red directory, edit your settings.js file. Change the logging > console > level to trace
    logging: {
        console: {
            // Level of logging to be recorded. Options are:
            // trace - record very detailed logging + debug + info + warn + error + fatal errors
            level: "trace"
        }

Mai 06 13:16:38 DietPi node-red[15645]: 6 May 13:16:38 - [red] Uncaught Exception:
Mai 06 13:16:38 DietPi node-red[15645]: 6 May 13:16:38 - TypeError: Cannot read properties of undefined (reading 'data')
Mai 06 13:16:38 DietPi node-red[15645]:     at /mnt/dietpi_userdata/node-red/node_modules/node-red-contrib-twc-weather/pws-current.js:79:40
Mai 06 13:16:38 DietPi node-red[15645]:     at runMicrotasks ()
Mai 06 13:16:38 DietPi node-red[15645]:     at processTicksAndRejections (node:internal/process/task_queues:96:5)
Mai 06 13:16:42 DietPi systemd[1]: node-red.service: Main process exited, code=exited, status=1/FAILURE
Mai 06 13:16:42 DietPi systemd[1]: node-red.service: Failed with result 'exit-code'.
Mai 06 13:16:42 DietPi systemd[1]: node-red.service: Consumed 33min 55.796s CPU time.

Fixed in<EMAIL_ADDRESS>release
npm install<EMAIL_ADDRESS>

Thank you very much!
I ve updated and we will see :) Can i donate for your work?

I'll keep this issue open until you report back.
I'm a weather nerd - enjoy. Buy me a Heineken next time I'm near Leiden.


Cells creating / reading folders are not run in the right order?

Sorry for the endless spam @tlienart. I did a big push today on ModernJuliaWorkflows, and a bug on the following PR is driving me crazy: https://github.com/modernjuliaworkflows/modernjuliaworkflows.github.io/pull/63
It happens on page 2 of the blog (sharing.md). There, I create a package called MyAwesomePackage with PkgTemplates.jl, and then I ]dev it into an environment called MyAwesomeProject. Both are local folders located at the root of the website, created on the fly (and added to .gitignore). In the ]dev step, Xranklin crashes because it can't seem to find the package folder.
I tried everything to make sure the cells run in the right order: ignoring the cache for the whole page, and even re-running both guilty cells with double symbols >> and ]]. Still the bug remains but only on CI: locally, it works like a charm.

By comparison, putting both calls in the same cell works in https://github.com/modernjuliaworkflows/modernjuliaworkflows.github.io/pull/64

OK this probably had something to do with my lack of use of sitepath and folderpath. Closing for now


UI issue: Disputing: disputing seems to never ends. Bonds just keep getting larger

UI issue: converting attoRep to attoRep makes for a really big number
disputing never ends event when timestamp is after Market's dispute window endTime.
I think the values are off by a factor. eventually market went to Awaiting Next Dispute Window, but the dispute bonds are in the millions.
reportingState: CrowdsourcingDispute
{
  "bondSizeOfNewStake": "29304302839965820312502076",
  "disputePacingOn": true,
  "disputeWindow": {
    "disputeRound": "11",
    "endTime":<PHONE_NUMBER>,
    "startTime":<PHONE_NUMBER>
  },
  "stakeCompletedTotal": "14652151419982910156251038",
  "stakes": [
    {
      "bondSizeCurrent": "14654970966796875000001824",
      "isInvalidOutcome": false,
      "isMalformedOutcome": false,
      "outcome": "5",
      "stakeCurrent": "0",
      "stakeRemaining": "14654970966796875000001824",
      "tentativeWinning": false
    },
    {
      "bondSizeCurrent": "0",
      "isInvalidOutcome": false,
      "isMalformedOutcome": false,
      "outcome": "4",
      "stakeCurrent": "0",
      "stakeRemaining": "0",
      "tentativeWinning": true
    },
    {
      "bondSizeCurrent": "29301628156738281250001328",
      "isInvalidOutcome": false,
      "isMalformedOutcome": false,
      "outcome": "3",
      "stakeCurrent": "0",
      "stakeRemaining": "29301628156738281250001328",
      "tentativeWinning": false
    },
    {
      "bondSizeCurrent": "29304175074462890625002040",
      "isInvalidOutcome": false,
      "isMalformedOutcome": false,
      "outcome": "2",
      "stakeCurrent": "0",
      "stakeRemaining": "29304175074462890625002040",
      "tentativeWinning": false
    },
    {
      "bondSizeCurrent": "29304285741882324218752074",
      "isInvalidOutcome": false,
      "isMalformedOutcome": false,
      "outcome": "1",
      "stakeCurrent": "0",
      "stakeRemaining": "29304285741882324218752074",
      "tentativeWinning": false
    },
    {
      "bondSizeCurrent": "29304302839965820312502076",
      "isInvalidOutcome": true,
      "isMalformedOutcome": false,
      "outcome": "0",
      "stakeCurrent": "0",
      "stakeRemaining": "29304302839965820312502076",
      "tentativeWinning": false
    }
  ]
}

closing


feat: implement new lavalink version (closes #86)

This will mark the 5th major version of Lavaclient!

Lavaclient v5 introduces 3 new packages to the NPM registry:

lavalink-protocol @effect/schema validation for the lavalink protocol
lavalink-api-client a type-safe api client for lavalink built on-top of protocol
lavalink-ws-client a type-safe ws client for lavalink built on-top of api-client and protocol

This means @lavaclient/types will be retired when v5 releases.

Docs still need to be finished and deployed to https://lavaclient.js.org, everything will probably be ready for publishing by then.


Compiles and runs, but why is intellisense marking it red?

I retargeted the solution to toolset v142. VS Enterprise 2019 version 16.7.0. In this project for example the red only appears in debug mode.

Did you upgrade the Windows SDK as well? What version are you using?
Did you do a full clean rebuild?
If I do the same, I see a few warnings in the DirectX Tool Kit in the Windows 10 SDK (19401) because DirectXTK uses /Wall that I've suppressed in the latest version of the library, but I don't see any other errors.

Thanks for the reply, it turns out that my errors had to do with Resharper plugin, clearing its cache resolved it.


Remove implicit wait for outstanding tasks at DFK shutdown.

In practice, this turned out to be awkward when, for example, ctrl-C
was pressed and parsl spent a long time waiting (or sometimes hung).
This commit intends that the same wait code is executed explicitly
at the place in the workflow code that the wait is desired (usually
the end). Ctrl-C and other abnormal exits will not cause this wait
to happen.

Also, as @benclifford points out, this needs a bit of documentation.


Character encoding

Well in my discord when receiving IRC message does not show Unicode characters, my encoding of my language is ISO-8859-1, even adding enconding in config. json.
I'm doing test using characters like á,é,ó, among others;
irc conf:
"ircOptions": { // Optional node-irc options
      "floodProtection": false, // On by default
      "floodProtectionDelay": 1000, // 500 by default
      "encoding": "ISO-8859-1"
},

Image of what is shown in discord

Hi marco, I'm having the same issue. Typing accented characters like á, é, í, ó & ú in IRC show on Discord as a, e, i, o & u. Have you found a solution?

Is this still an issue with discord-irc version 2.6.2?

Closing due to lack of info.


Add a job board in the Frontend development job boards folder

Hi, I'd like to add another job board in the /Frontend-Development/Job-Boards folder

jobboardsearch.com

Kindly permit to raise a PR. Thanks!

@Ryukemeister please go ahead and create the pr. Please make sure you mention/link this issue to the pr

Thank you!


StreamS3Object nifi processor

POC for a Nifi processor that can copy objects between S3 buckets without the need to write temporary files on the Nifi instance.

There seems to be one gitignore conflict. I just merged one PR from my branch to master. Will resolve this one and merge...Thanks

There seems to be one gitignore conflict. I just merged one PR from my branch to master. Will resolve this one and merge...Thanks

I just fixed it. Seems like there's no other conflicts.


Funny behavior resizing and relaunching the app

Hi there, first of all thanks for putting this together it's very cool. :-)
Now, maybe you have already noticed this but there's a weird issue when resizing the window, other than the "glitch" already mentioned.
Here I have a very sample test app with the sample code from Scott Hanselmann's post (https://www.hanselman.com/blog/Its2020AndItIsTimeForTextModeWithGuics.aspx).
So I add the code and run it with dotnet run and shows nicely:

Now, if I resize the screen I notice the "glitch" others have talked about and the display stays the same, but if I exit the app and relaunch it, now the window looks all messed up:

sometimes it looks REALLY messed up:

The app is fully functional, only the layout is ugly. I'm using Windows Terminal 1.2.2381.0
I have tested in a plain command prompt and here the problem doesn't happen, but I noticed that if I resize the app while it's running, upon closing it the window goes back to the initial size.
Not sure if this has already been mentioned elsewhere but here it goes just in case. :-)
Thanks again!
Kind regards.

Windows Terminal doesn't work well with GUI. It has to do with them himself and not with GUI, I think.

Be sure you are using the latest API too.

Windows Terminal does have bugs when resizing that we can't fix ourselves. However, they usually only occur WHILE resizing. I'm going to close this as 'wontfix'.


Bump to Dataproc 2.1

flink python and go load tests failing since Feb 5 (e.g. https://ci-beam.apache.org/view/LoadTests/job/beam_LoadTests_Python_ParDo_Flink_Batch/) because the preview version of DataProc 2.1 is no longer available. Bump to the released 2.1 version
Please add a meaningful description for your change here

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

Run Load Tests Python ParDo Flink Batch

Run Load Tests Python ParDo Flink Batch

test passed.
R: @riteshghorse


Event resize not working?

Even on the ui-calendar homepage, looks like events aren't being populated with the "fc-resizable" class, even though events are set to "editable: true."

So ui-calendar event resizing IS working but FullCalendar won't resize an event that doesn't have "allDay: true" applied to it.
FullCalendar.js (Line 5491)
var isResizable = !disableResizing && event.allDay && seg.isEnd && view.isEventResizable(event);
I'm not seeing that stipulation of allDay = true in the FullCalendar docs anywhere? Perhaps that would be a natural conclusion, but also seems to make sense that an otherwise "timed" event could be resized into an allDay(+) event.
Anyways, issue closed.


refactor: use injectable service and providers

The PR uses Angular way of using AppWriteService, this goes more in a way Angular Standard to inject the service.
The APP_INITIALIZER will be responsible for initializing the AppWrite service so instance is available before it is being used

Can someone check the API is giving some error or did i made some mistake
Cc: @brandonroberts

@santoshyadavdev if you're using the PR preview, you will most likely get a CORS error because the subdomain isn't added to the platforms for this project. What's the error?

@santoshyadavdev if you're using the PR preview, you will most likely get a CORS error because the subdomain isn't added to the platforms for this project. What's the error?

Yes it it CORS error.

@brandonroberts, once 0.14 is out, we should probably use the new wildcard hostname for these demo apps.

Yep, I was thinking the same thing


Remove obtain_from_generic from all classes

We now have .as<T> which does the job. Easy entrance task

Do you just want it deleted or replaced with anything? I can take this on and most likely be done by Monday should my schedule permit.

@Macr0Nerd remove the functions and wherever it is being used use the mentioned .as function

I’ll get on that ASAP!

@vigsterkr where could I find the .as? I just want to make sure I use it right

it's part of SGObject

@vigsterkr I apologize but I will not be able to help with the issue. I have had some things come up and i don't want to leave the issue where it goes unsolved.

Thanks for letting us know :D

Hi, I'm working on this. What would be the proper syntax for the meta examples? Neither of these work:
CombinedKernel learnt_kernel_combined = mmd.get_kernel().as<CombinedKernel>()
CombinedKernel learnt_kernel_combined = mmd.get_kernel().as_CombinedKernel()

The first statement is not valid syntax, the second spits out:
translate.TranslationFailure: 'Variable learnt_kernel_combined not initialised'

as_kernel, as_features, etc...

Not sure you need that in the example above though..... get/put work on the base class

Not sure you need that in the example above though..... get/put work on the base class

After removing all instances of obtain_from_generic there are only a few cases where it's being used. The meta examples is one of them. Are there additional changes I need to make before as_CombinedKernel can work as intended?

You would use as_kernel
But actually not even that as you can use get on the sgobject. What calls do you want to make on the object ?

But actually not even that as you can use get on the sgobject. What calls do you want to make on the object ?

That seems to have worked, thanks. I apologize for not being clear earlier. I was trying to fix these two files (the meta language files):
../examples/meta/src/statistical_testing/linear_time_maximum_mean_discrepancy.sg
../examples/meta/src/statistical_testing/quadratic_time_maximum_mean_discrepancy.sg

and your suggestion did the trick:
-CombinedKernel learnt_kernel_combined = CombinedKernel:obtain_from_generic(mmd.get_kernel())
+CombinedKernel learnt_kernel_combined = mmd.get_kernel()

That won’t compile I think you need to change the type to Kernel

Also see #4581 where I am refactoring some stuff related

you  in fact just exclude the meta example for statistical testing in this pr. I will be done with the other one soon and then you can rebate against it

That won’t compile I think you need to change the type to Kernel

How so? I made sure it compiled before I created the PR.

you can in fact just exclude the meta example for statistical testing in this pr. I will be done with the other one soon and then you can rebate against it

I will rebase and fix any conflicts after that, then.

You cannot implicitly convert CKernel* so CConbinedKernel* but your example effectively does that.
Make build_cpp_meta_examples should fail

Hi,
When you said remove " 'obtain_from_generic' from all classes " which classes are you referring to.
Preferably could you provide a link.
Thanks!

@neroangelo296 you can git grep obtain_from_generic

@vinx13 Thanks

Just to confirm, is this the change we're looking for?
CMKLClassification* CMKLClassification::obtain_from_generic(CMachine* machine)
{
     //code here
}

to
CMKLClassification* CMachine* machine
{
     //code here
}

@neroangelo296 you will replace  obtain_from_generic call with  .as<CMKLClassification>(), and finally remove obtain_from_generic definition

So its
CMKLClassification* .as<CKMLClassification>(CMachine* machine)

@neroangelo296 yes, as is a template method that we have already defined in https://github.com/shogun-toolbox/shogun/blob/9537f595679993bd56a833629cba832c97165c5c/src/shogun/base/SGObject.h#L668

I've made a pull request.
Thanks for putting up with me.


Determine approach for extracting tissue leaf ancestors from UBERON

Approach

Validate part-of is only relationship we're interesting in
Sanity check size of generated map
Review existing related functionality
Document in Filter by Metadata (v3) - Tech Spec

Filter by Metadata (v3) - Tech Spec (Filter by Tissue Ontology)
compute_orphan_tissues
compute_uberon_tissue_parts_graph


support Python PG client

as title.

Maybe related: https://github.com/singularity-data/risingwave/issues/2621

Maybe I can do this work in this week.

Maybe I can do this work.

Thanks! 🥰 Please self-assign it

Maybe I can do this work.

Thanks! 🥰 Please self-assign it

Only member can assign tasks :)

Related #3253

And I guess you mean psycopg2

I tested psycopg2 with some basic usage and it seemed to work 😄.


Txs list v2: History-Incoming tx: remove empty space in left top block on tx details

Title/Description
There is two much empty space under execution date , according to design the empty space should be removed
Environment

Browser: Chrome/MacOS
Safe: 0x1230B3d59858296A31053C1b8562Ecf89A2f888b
Wallet: MM
App Version: 2.20.0
Environment:

PR # https://pr1781--safereact.review.gnosisdev.com/rinkeby/app/#/safes/0x1230B3d59858296A31053C1b8562Ecf89A2f888b/transactions

Steps to reproduce

Go to safe 0x1230B3d59858296A31053C1b8562Ecf89A2f888b
Open History->incoming tx
Current result: There is too much empty space under execution date

Expected result

Screenshots

-->

fixed in e2b1b33 (#1781), pelase review when build finishes
Thanks!

Verified, It is fixed


Working with word replacement with confirmation

I have a question to the plugin users. How do you work with the word replacement with confirmation if you are using the plugin? VS Code replace function does not work on per-word basis https://github.com/vscode-neovim/vscode-neovim/issues/1036, the interactive replace from vim has this issue: https://github.com/vscode-neovim/vscode-neovim/issues/1149.
Do you use the mutli-cursor to replace just a couple word repetitions? If so how? Do you use a neovim plugin for it? Or is there something else I am missing?

Looks like the issue https://github.com/vscode-neovim/vscode-neovim/issues/1036 is fixed. That helps a lot :) Closing.


Install the TensorFlow-GPU and CUDA and CUDnn, but GPU not work when test.

System information

OS Platform and Distribution: Win10, X64
TensorFlow version: 1.15
Python version: 3.5
Installed using virtualenv? pip? conda?: pip install tensorflow_gpu-1.15.0-cp35-cp35m-win_amd64
CUDA/cuDNN version: 10.2/7.6.5
GPU model and memory: GTX1050

problem details
i use the Anaconda, the first i create a new environment which python version is 3.7 and TensorFlow-GPU is 2.1. and then i install the CUDA 10.2and CUDNN, 7.6.5, but when i test it, there is a error said can't find the cudart64_101.dll file, when i changed that file(cudart64_102.dll) its name to cudart64_101.dll, no error again, and when i run the follow code showing true
#code 1
import tensorflow as tf
print(tf.test.is_gpu_available())
and running that below code also show the GPU device log
#code 2
import tensorflow as tf
sess = tf.compat.v1.Session(config=tf.compat.v1.ConfigProto(log_device_placement=True))
all is going well on tensorflow 2.1 with GPU
but when i wanna to use tf-gpu 1.X, i install the tensorflow-gpu 1.15, with the same CUDA, CUDNN version, i made a copy of cudart64_101.dll and rename cudart_100.dll, when i run the above test code, the console shows no error, but show false in the code 1 and did not show GPU device info in code 2. i was wondering that if the CUDA/CUDNN version isn't fit the tensorflow-gpu version, is any error will show? i think there must be some error will be report. The problem is i don't know how to fix it because it didn't report error .
should i uninstall the CUDA 10.2 and CUDNN and install CUDA 10.0/10.1 but...
Any other info / logs
and when i import tensorflow in anaconda prompt , there is no warning or error, just shows
tensorflow/stream_executor/platform/default/http://dso_loader.cc:44] Successfully opened dynamic library cudart64_100.dll

TF 1.15 supports cuda 10.0 and cudnn >=7.4 . You have to roll back to cuda 10.0
Thank you.

THX, and i want to know if i roll back to CUDA 10.0, my another environment with tensorflow-gpu-2.1 can fit the CUDA 10.0? because i refer to the tensorflow.org only showing tensorflow-gpu-2.0 to CUDA 10.
Sorry, a little more question, someone told me that there can't exist tf-gpu or tf-cpu at the same time  in one environment, which means we should create two environments to manage tf-cpu and tf-gpu. is it true?
and a not related question, can i instal the CUDA10.2 & CUDA 10.0 in win 10?
why tf 1.5 can not support CUDA > =10.0 same as the CUDNN can > =7.4?
Really thanks for your reply.

Yes you can use TF 2.1 with cuda 10.0 as well. I will add TF 1.15 cuda info on the website.
You have to build TF from source for supporting cuda version other than the ones we already support.
This procedure is time consuming and often stressful for users. So we recommend installing tf using pip packages (pre built tf binaries). The only caveat here is that users have fix their environment as per our dependencies.
Having said that we do actively engage with the community and help as much as possible.
Thanks for using TF.

I have rolled back to cuda 10.0, TF-GPU 1.15 can work with gpu well, but TF 2.1 can't, like the bug like i put forwoard first in TF 1.5 once. i think i can solve this by downgrading to TF 2.0, is it right? but you said can use TF 2.1 with cuda 2.1, there must be something i did wrong in this process.
Building TF from source means i should do as https://www.tensorflow.org/install/source_windows? introduction or ...
Thanks for your active engagement sincerely.

ahh.. You are right for TF 2.1 you need cuda 10.1 (my apologies). Yes TF 2.0 supports cuda 10.0.
Sorry for the confusion.
See tested build configurations Thanks!

Fine,i felt i've solved my problem, thank you.


e2e token timeouts: remove the test that moved to CAO

/assign @sttts

/test e2e-upgrade

/retest

/lgtm
/approve


Correct bad attribute name

Replace incorrect reference to activatable_name with constructor_name

@DefaultRyan : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Implement backpressured stream in muxink

muxink currently has a backpressured sink implementation, but the stream counterpart is missing. Implement BackpressuredStream and write unit tests for it.

Implementation on my local branch, in commit https://github.com/georgepisaltu/casper-node/commit/61838156d05dd144f5699ab0181a782d00fc0e08. It will get merged along with the feat-muxink-integration rebase.


Phh... Just applied style is not removed

Select a text.
Click on toggle bold, italic, underline. The style is applied.
Click on toggle again. The styte is not removed.

Hm... strange but it starts working.


Python docstrings not ended

this line demonstrates that the end of the the docstring started here is not detected.
as result, the rest of the file is highlighted as docstring…

@flying-sheep Linguist only selects the appropriate grammar for highlighting. In the case of Python, it uses [this Atom bundle]https://github.com/atom/language-python). You should open an issue there ;)

You should open an issue there ;)

Yep, please report this issue upstream. We will automatically pick up the fix when it's made.

will do, thanks, and sorry for raising it here :relaxed:


Mod causes infinite storage in storage tanks

This usually happens on the top tank. See screenshot. If I add another tank on top, then this one would stop filling, and the new top tank would have infinite storage. Disabling this mod solves the issue and the tank stops filling.

Normally, I wouldn't mind this, but if dark fog blows that tank up, that's a LOT of oil gone to waste.

sorry for late to reply, will check it later, seems like a logic error in rewritten tank update function.


ILRepackSettings.Libs should be DirectoryPaths

When this was originally implemented, it wasn’t very obvious, but ILRepack’s /lib:<path> argument should actually be a directory, not a file.
This sheds a bit more light:
https://github.com/gluck/il-repack/blob/master/ILRepack/RepackOptions.cs#L221
This commit fixes up the ILRepackSettings.Libs to be the correct type.
This should fix #1720

@Redth  your changes have been merged, thanks for your contribution 👍


Change "Repair/Remove" to "Agree/Disagree"

This changes the default binary question choices from "Repair" and "Remove" to "Agree" and "Disagree".
There could be further improvement — for example, renaming binary questions from "numerical_response" to something like "binary_question" — but this is a useful and necessary immediate change for anyone redeploying.
Also, could still debate whether this should be "Yes"/"No" but going with this for now. cc #197.

We can use this improvement as a guide to updating from Agree/Disagree to Yes/No answers for survey questions @migurski