Current git commands set a too high version compatibility limit (>= 2.28)

Hello,
According to
https://github.com/raxod502/straight.el/blob/5541697ceee7e7ba937eddebba44f1e8e8af6a4f/straight.el#L2485
and this comment https://github.com/hlissner/doom-emacs/issues/5088#issuecomment-847249596
straight is currently setting a hard limit on the version of git that’s in the PATH in order to operate. Literally Almost (21.04 has 2.30, sorry for being hyperbolic) no Ubuntu is compatible (>= 2.28), and while I’d agree that it’s really a Canonical issue at that point, it cuts off a very large part of potential users :(

I'll have to look over our git usage to see what we're using and if we can easily substitute those commands for something backwards compatible.
A solution on the user end for the time being is to grab git from the git-core ppa:
https://launchpad.net/~git-core/+archive/ubuntu/ppa

I didn’t think about looking for PPAs, it seems it’s the easiest way to get going. Personally I don’t really mind if compatibility options are added or not, it’s probably code one would not like to maintain; therefore just having the PPA for now would be enough for me. Then again, I don’t use Ubuntu
Thanks for your work on straight either way!

I suspect that this will be an easy fix. We can't have introduced this dependency too long ago, or I would have noticed already! (I'm running Ubuntu 20.04.)
Git has added a lot of alias options recently to make the commands more intuitive, so I guess going forward we should just double-check to make sure we're not using one of them when adding VC code.

Here's a list of the current git commands and the options we're using:

Sub-command
Options

branch
-m -r

checkout
-B

clean
-ffd

clone
–branch –depth –no-checkout –no-single-branch –no-tags –origin –single-branch

config
–get –file

describe
–short –match –abbrev

fetch
–depth –no-tags

log
–format=%h %s

ls-files
–unmerged

merge
–abort –ff-only

merge-base
–is-ancestor

rebase
–abort

remote show
–master

reset
–hard

rev-parse
-q –verify –abbrev-ref –symbolic-full-name –git-dir

show
-s –format=%d %h %cs

stash push
–include-untracked

stash save
–include-untracked

status
–short

submodule update
–init –recursive

I think most of these look they will work for relatively older versions of git
(The only one I see off the top of my head that I remember being added "recently" was the --no-tags option for git clone, but even that was years ago.)
If anyone notices anything that looks like it forces a high version requirement let me know.

#776 has been merged into "develop". I think that should remove the >=2.28 restriction. @gagbo: Testing appreciated if you have time.
Thanks.


RPC Parser - Parsing default value from a function parameter is broken

Bug Report
In the RPC InterfaceParser, parsing default value from a function parameter in rpc_base.py is broken because the value at params["default_value"] always gets overwritten with None. The root of the issue seems to be that the _parse_function_param() function tries to parse the default value from the attrib dictionary, however the attrib dictionary is always empty because _parse_param_base_item() does not add any items to the attrib dictionary.

Closing with the merge of #286


How to delete message in a stream ?

Hi,
Simple question,
There is no way in zulip to remove a message in a stream ?

That's correct.  You can always delete the message content if you like.  Depending on what you're trying to do, this may be a duplicate of https://github.com/zulip/zulip/issues/135


Update request: typst 0.11.1 → 0.12.0

Package name: typst
Latest released version: 0.12.0

Current version on the unstable channel: 0.11.1
Current version on the stable/release channel: 0.11.1

[x] Checked the nixpkgs pull requests

Notify maintainers

@drupol @figsoda @kanashimia

Note for maintainers: Please tag this issue in your PR.

Add a :+1: reaction to issues you find important.

https://github.com/NixOS/nixpkgs/pull/349652 resolves this issue


UI: replace navigation arrows by dots

Advanced settings are now hidden until you find these two little arrows at the top left corner.
It may be better to use dots like these:

In my opinion, it becomes a little more obvious that there are additional settings here.

Hello! That's actually a great idea! It can even be used for other things that I'd like to implement later, such as statistics. I'll see what I can do this weekend!

My work here is done.
Commits:

https://github.com/Ryzzzen/manaflux/commit/b6208bd84c942e341ecfb549bb788258b8abc4a4
https://github.com/Ryzzzen/manaflux/commit/2e397b693614c831d1822c038f49dd1a614e0d72

Feel free to re-open this issue if you think of ways to improve the dots!


kv: expose mdbx SafeNoSync and OptSyncPeriod options

for https://github.com/ledgerwatch/erigon/pull/3656

@AskAlexSharov if we wanna backport this to stable, should I make a PR against Stable branch?

@battlmonstr not capitalized one: stable
Also FYI:

erigon stable using erigon-lib stable
erigon devel using erigon-lib main
:-)

Also: erigon's PR need merge before erigon-lib's PR (just because merge to Erigon may take a while, other devs need a chance to start their new branches at any time).

Also: erigon's PR need merge before erigon-lib's PR (just because merge to Erigon may take a while, other devs need a chance to start their new branches at any time).

What should I put in the erigon's go.mod then? A commit sha of this unfinished work? The reasoning is not clear to me.


How to use it on Windows?

Windows user here, is there a chance to use it?

You can't use Tz::named() and Tz::local() on Windows. But if you already have a copy of the tz database somewhere, you can read the file into memory and then use Tz::parse().


Broken Links in README

The bold/italics links are broken.
Open Voice OS running on Docker or Podman
What is Open Voice OS?
How does it work with Docker or Podman?
Supported architectures and tags
Architectures
Hardware tested on
Operating systems (64-bit version) tested on
How to build these images
Arguments
Image alternatives
Message bus
Listener
TTS (Text-to-Speech) and STT (Speech-to-Text)

Fixed :+1:


Move from NFD hook usage to NFD feature-file usage

Intel device plugins for kubernetes, particularly GPU and SGX initcontainers, should align with the NFD hooks becoming deprecated. Ref https://github.com/kubernetes-sigs/node-feature-discovery/issues/855
NFD feature-files can be used instead of binary hooks. Potentially a sidecar container which produces the NFD feature-file would work. The possibility of cleaning up the feature-file at plugin Pod deletion time should be investigated. The current initcontainer-based hook-approach leaves the hosts polluted even after the plugin is removed, since there is no cleanup currently.

The current initcontainer-based hook-approach leaves the hosts polluted even after the plugin is removed, since there is no cleanup currently.

NFD hook will fail if there are no GPUs exposed by the kernel, so it will not provide labels to nfd-worker. nfd-worker always checks all sources before sending update to nfd-master, and that update replaces all earlier labels for given node. I.e. use of NFD hooks is not a labeling problem, it will "just" fill nfd-worker log with failure warnings, and is otherwise icky.
With feature files, you do need to remove the file [1] when GPU plugin goes down, in case all Intel GPUs get removed from node, and (another) GPU plugin instance won't be there to update the feature file. This is trivial though, as k8s sends termination signal to containers before forcefully terminating them, and you can specify in pod spec how long grace period you need for termination.
[1] I have ticket for NFD to automate feature files life-cycle handling (add expiration date): https://github.com/kubernetes-sigs/node-feature-discovery/issues/857

dropped sgx label due to #1392

Hooks are now disabled by default in NFD upstream: https://github.com/kubernetes-sigs/node-feature-discovery/pull/1182
That change will be part of next (v0.14) NFD release.


Update to leaflet 1.9.3

i was about to make the same PR, however it looks like the repo is no longer maintained or watched by the author since the last time something happened is in 2016... however, still is a useful and great plugin!


Use of this in a fat arrow function

This code :
this.c = 1

f = () =>
  a=`this`.c
  b=`this.c`
  a is b

alert f()

is translated to :
var f,
  _this = this;

this.c = 1;

f = function() {
  var a, b;
  a = _this.c;
  b = this.c;
  return a === b;
};

alert(f());

Is this correct ?
I thought instead of :
a = _this.c;
b = this.c;

we would have :
a = this.c;
b = this.c;

I'm afraid I can't tell what you're writing if you don't format your code... But this seems to be working properly.

Gross. Just use a closure.  I don't know where people are picking this up.
 this.c = 1

 f = do (that = this) => =>
   a = this.c
   b = that.c
   a is b

 alert f()

This has been brought up before, but I can't find it. It's a duplicate, but I'll leave it open until we have a reference to the original issue.

Related: #1230, #2131, 981db17b8f718be9437d20ced9b0dd2408ae57ed

Thank you for the answer.
You are right, I was to fast on opening the issue without using the preview !
I was dealing with a callback function defined with a fat arrow but binded to another object by the caller.
That's where I tried to use the Embedded Javascript option and found something that appeared stranged to me.
Finally I reorganized my code, it's simpler with no possible ambiguity.

@jashkenas: we still don't have a link to the original issue, and this is still technically a valid bug. `this` should compile to this, not _this. Since I don't want this to get lost, I'm re-opening it for now.

Thanks -- I wasn't following the original problem.


Rename CSS class to avoid conflicts

The class .card is a very common class name (used for example by Bootstrap), so by using a more unique name we can avoid having default styles applied unintentionally.

Thank you, LGTM :)
Will bump the version shortly


Fix a broken link

Updates the Go SDK link to point to the top level of the repo. (It currently 404s.)

Closing as I didn't realize the issue was just that go.dev hadn't generated pages yet. Requested those and expect this will resolve on its own.


Fancy Zones Randomly Hides Windows Out of View

Microsoft PowerToys version
0.60.1
Running as admin

[ ] Yes

Area(s) with issue?
FancyZones
Steps to reproduce
Reproducing the problem is a bit difficult as it occurs randomly. I have seen two conditions.

A window is completely hidden (usually one that you are switching to/from a lot, with Alt+Tab) and clicking on it in the taskbar does nothing. In this condition the active window can be hovered over in the task bar, right clicked and maximized to show the window. Subsequently restoring the window hides it again. If Move is selected from the right click menu, the cursor is positioned at the top left of the screen, but the window cannot be moved.
The second condition is very similar but the window is made tiny, only the icon, minimize, restore, maximize and close are shown and the window is moved to the top left corner of the display. In this condition the window my be resized by dragging its edges then snapped back to a zone.

In most cases to fix the issue, the window must be closed (right click menu in the task bar or killed in task manager). After relaunching the windows is typically visible again.
✔ Expected Behavior
Should not hide the window.
❌ Actual Behavior
Windows are hidden and/or made tiny.
Other Software
Windows 11, build 22000.795, experience Windows Feature Experience Pack 1000.22000.795.0

Are you still experiencing this issue? /needinfo


⚠ Roblox TextFilter Api has degraded performance

In 7ad0f4a, Roblox TextFilter Api (https://textfilter.roblox.com) experienced degraded performance:

HTTP code: 200
Response time: 2933 ms

Resolved: Roblox TextFilter Api performance has improved in b9700f7.


Unable to pass bitrate to Media Recorder API on Safari

Tested on:
Safari: ver. 16.1 (186<IP_ADDRESS>.12)
Chrome: 107.0.5304.110 (Official Build) (arm64)
So my firm relies on RecordRTC for our video recording app. We noticed that the files being recorded on Safari were much larger than than those on Chrome due to having almost 5 times the bitrate. Upon further investigation, we narrowed the issue down to:

Safari as of yet not supporting webm (18 Nov, 2022)

This throws an error

Which is caught by the following statement

try {
       mediaRecorder = new MediaRecorder(mediaStream, recorderHints);
       // reset
       config.mimeType = recorderHints.mimeType;

    } catch (e) {
      // chrome-based fallback
      mediaRecorder = new MediaRecorder(mediaStream);
}

Thus, the specified bitrate isn't passed to the Media Recorder API and default bitrate is selected. This behaviour can be observed in the live demo website as well.

해당 문제는 ios 15.x 버전(아마도 그 이하 버전들)에서 발생하는 문제입니다. 나는 여러 시도를 했지만, 해결법을 찾지는 못했습니다. 그냥 ios 버전을 17.x로 올리니까 해결이 되었습니다. 아마도 16.x버전으로 올려도 해결이 될 수 있을 겁니다. 사용자들에게 ios 버전을 업그레이드 하라고 메세지를 띄우는 것이 현명합니다.

Tested on: Safari: ver. 16.1 (186<IP_ADDRESS>.12) Chrome: 107.0.5304.110 (Official Build) (arm64)
So my firm relies on RecordRTC for our video recording app. We noticed that the files being recorded on Safari were much larger than than those on Chrome due to having almost 5 times the bitrate. Upon further investigation, we narrowed the issue down to:

Safari as of yet not supporting webm (18 Nov, 2022)

This throws an error

Which is caught by the following statement

try {
       mediaRecorder = new MediaRecorder(mediaStream, recorderHints);
       // reset
       config.mimeType = recorderHints.mimeType;

    } catch (e) {
      // chrome-based fallback
      mediaRecorder = new MediaRecorder(mediaStream);
}

Thus, the specified bitrate isn't passed to the Media Recorder API and default bitrate is selected. This behaviour can be observed in the live demo website as well.

Did you find any solution for this issue?


[feature request] http module request path variables binding!

Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (go version)?
1.7.1
The http module is easy to build an web app with the http.Handler.
With the param *http.Request we can get a full list of request info.
But in most apps. We should get variable from path string.
For example:
localhost:3000/user/lily/app/1
can use user and id to bind lily and 1
we can just use http.HandleFunc("/user/{user}/app/{id}", list) to archive here.
Please consider this for simplify the process of build a web app.
Thanks!!

There are dozens of http routers/muxes on Github. I don't foresee us adding a competing one in the standard library since we already include a minimal one. Having two would be crowded.


Do not trigger deployment on molecule related change

We may modify molecule config or zuul job from time to time. Such
changes shouldn't trigger a full deployment, since it doesn't affect it
in any way.
As a pull request owner and reviewers, I checked that:

[X] Appropriate testing is done and actually running

/approve
/lgtm

recheck


Add setting to prevent sleep while music is playing.

When a lot of Windows systems sleep, they disable audio output either because the computer is locking or because their audio routes with their HDMI connection. Can there be a setting that keeps Windows from sleeping or turning off the display while music is actively playing in GPMDP? I believe that when you are using the web player in Google Chrome it is able to prevent the computer from sleeping/locking. Thanks!
OS:
Microsoft Windows 10 64-bit Build 14393
Issue Descriptions:
Computer sleeps when playing audio.
Steps to Reproduce:
N/A, dependent on Windows settings.

Just to be clear, this would stop the device from turning off the display entirely.  It wouldn't be implementing the background audio feature found on some Surface Pro and other windows devices.

Yes, that is correct. Just a checkbox with something along the lines of "Prevent this device from entering sleep mode while audio is playing."
Chrome already does this passively with YouTube and GPM; so it would be a nice option to have on GPMDP.

If anyone wants to tackle this all you have to do is add another ToggleableOption to a settings page somewhere and use the powerSaveBlocker in the main process 👍


[NIFI-2781] use npm to install bower

…ources in nifi-web-ui and nifi-jolt-transform-json-ui

Reviewing...

Thanks @scottyaslan! This looks good and addressed the build issues I was seeing in my Windows VM. Also verified offline build.
This has been merged to master.


Missing first class pydantic objects support by XMLOutputParser

Checked other resources

[X] I added a very descriptive title to this issue.
[X] I searched the LangChain documentation with the integrated search.
[X] I used the GitHub search to find a similar question and didn't find it.
[X] I am sure that this is a bug in LangChain rather than my code.

Example Code
Take the following Pydantic class:
from langchain_core.pydantic_v1 import BaseModel, Field

class Joke(BaseModel):
    setup: str = Field(description="question to set up a joke")
    punchline: str = Field(description="answer to resolve the joke")

When used with JsonOutputParser we can generate pydantic schema as follows:-
from langchain_core.output_parsers import JsonOutputParser
instructions = JsonOutputParser(pydantic_object=Joke).get_format_instructions()

Error Message and Stack Trace (if applicable)
No response
Description
The given example steps are not replicable with XMLOutputParser. Although it does have the tags field, there is no way to pass the pydantic object directly. Passing JSON schema can result in transient errors in generated outputs.
Ideally an XML schema or something similar should be injected, which would be dynamically generated from the Pydantic object.
System Info
System Information

OS:  Linux
OS Version:  #18~22.04.1-Ubuntu SMP Wed Jan 10 22:54:16 UTC 2024
Python Version:  3.10.12 (main, Nov 20 2023, 15:14:05) [GCC 11.4.0]

Package Information

langchain_core: 0.1.25
langchain: 0.1.8
langchain_community: 0.0.21
langsmith: 0.1.5
langchainhub: 0.1.14

Packages not installed (Not Necessarily a Problem)
The following packages were not found:

langgraph
langserve

Looks like there is no more langchain_core.pydantic_v1 :(


Does not compiles td-swift-2

A lot of compilation errors: "Operator implementation without matching operator declaration"
in places like this - case let .Success(value): return value <^> self

Compiles fine and tests pass over here in both Xcode 7 b3 and b4.
Perhaps you might be more specific with what you've tried so far, what you've tried it on, etc.

My bet is that you didn't run bin/setup, and so it hasn't pulled down the Runes source. We need to be more explicit about that in the readme and contributing guide.

you are using operator operator <^> a lot and it defined as
public func >>- <A, B>(a: Decoded, f: A -> Decoded) -> Decoded {
return a.flatMap(f)
}
it's ok, but no such thing as - infix operator <^> which was declared within Runes lib, but you removed the Runes from podspec dependencies. Why?

I went into this fairly in-depth in the PR that removed Runes as a framework dependency.
Regardless, this isn't an issue. If you run bin/setup, you will get the operator definitions for <^>, <*>, >>-, etc.

Just realized you're using CocoaPods. We haven't cut a CocoaPods release for Swift 2.0 yet, because it isn't finalized. We'd rather that you didn't point at a WIP branch as a dependency.


Сondition can be split between sections, which breaks the parsing

What happened? What is the problem?
In case of pg_auto_failover.spec or xorgxrdp.spec begin of condition remains in main package section while %endif goes to sub-package. So you get IndexError when trying to parse it.
from specfile import Specfile
with Specfile("xorgxrdp.spec") as specfile:
    with specfile.sections() as sections:
        for section in sections:
            if "package" in section.name:
                with specfile.tags(section) as tags:
                    for tag in tags:
                        print(tag.name)

  File "/usr/lib64/python3.9/site-packages/specfile/context_management.py", line 133, in __call__
    self.values[key] = next(self.generators[key])
  File "/usr/lib64/python3.9/site-packages/specfile/specfile.py", line 273, in tags
    tags = Tags.parse(section, context=self)
  File "/usr/lib64/python3.9/site-packages/specfile/tags.py", line 497, in parse
    lines = process_conditions(list(section), macro_definitions, context)
  File "/usr/lib64/python3.9/site-packages/specfile/conditions.py", line 119, in process_conditions
    result.append((line, branches[-2]))
IndexError: list index out of range

What did you expect to happen?
No errors.
May be process conditions before splitting to sections?
Example URL(s)
No response
Steps to reproduce
1. get xorgxrdp.spec
2. try to get package glamor tags
3. IndexError: list index out of range

Workaround

[ ] There is an existing workaround that can be used until this issue is fixed.

Participation

[ ] I am willing to submit a pull request for this issue. (Packit team is happy to help!)

Thanks for the report. This is basically the same issue as https://github.com/packit/specfile/issues/231, but I didn't realize it affects also parsing. Let me think about how to fix this.


An indicator of the accident push, Push Gateway How can the police?

I use a metric Push Gateway When I stopped, I realized how to police it? For example, a statistical service requests when this accident DOWN business machine, but pushgateway becomes 0, 0 but may be normal, so I can not judge whether this target is outside stopped

I'm sorry, I'm not sure I understand your question. Could you try formulating it again?

The Pushgateway is explicitly not an aggregator, but rather a metrics cache. It does not have a statsd-like semantics. The metrics pushed are exactly the same as you would present for scraping in a permanently running program.
Because the index is cached, when a stop push abnormalities, and how the alarm.

@juliusv The Pushgateway is explicitly not an aggregator, but rather a metrics cache. It does not have a statsd-like semantics. The metrics pushed are exactly the same as you would present for scraping in a permanently running program.
Because the index is cached, when a stop push abnormalities, and how the alarm.

Ok, that all makes sense, except that I still don't understand what you mean with "when a stop push abnormalities, and how the alarm."
I guess you want to alert on something - but on what? When the pushgateway is down? Or when a job stops pushing to the pushgateway? Or when a job pushes certain data to the pushgateway? What do you mean with "abnormalities"?

@juliusv  thank you ,I mean, when a job pushes certain data to the pushgateway

As long as your job is pushing data correctly to the pushgateway, you can alert on the resulting time series just like if it they were scraped directly from a target.
Do you have a concrete example? What metric do you want to alert on?

thank you @juliusv I being the first to use other alternative methods


Document case-sensitivity of input parameters (state keys, pubsub topics)

Provide explicit guidance for API input parameters for things like state keys or pubsub topics

This is ready for review in docs. @msfussell can you take a look? We need to get this into .11


Add snapshot name argument

what
This adds the ability to restore redis to snapshots created using the AWS implementation of backups for this service.
why
Need a way to restore redis to from snapshots.
references
Relates to #96

/rebuild-readme

/rebuild-readme

LGTM, just one thing need to fix

LGTM, just one thing need to fix

/test all

/test all


Feature/watcher notifications

Auto-adds discussion / post creator as a watcher if feature is enabled
Sends notification email to watchers when a new post is added

Thoughts on including the "features" in the config, but commented out by default?

@tomirons do you see any issues with this PR that I may have missed?


nltk.draw.pos-concordance(), mentioned on website, does not exist

From website ( http://nltk.googlecode.com/svn/trunk/doc/howto/corpus.html#tagged-corpora ):
:::
Use nltk.draw.pos-concordance() to access a GUI for searching tagged corpora.

Not quite sure I understood precisely, since I don't know whether "source tree" includes (web) documentation. Which of the following scenarios holds?
(1) The website gave the wrong command and needs to be changed (if so, it still hasn't been).
(2) The NLTK source code needed to be changed, and has been.
(3) Both of the above.
I still get an error (with version 2.0b9; haven't downloaded anything new) when I type "nltk.app.pos_concordance()" rather than "nltk.draw.pos_concordance()":
In [4]: import nltk.app
In [5]: nltk.app.pos_concordance()
AttributeError                            Traceback (most recent call last)
C:\Windows\system32<ipython-input-5-19538d4bb016> in ()
----> 1 nltk.app.pos_concordance()
AttributeError: 'module' object has no attribute 'pos_concordance'


require flit_core in pyproject.toml instead of flit?

Hi - I've been working on getting this working under buildroot, which doesn't install the full 'flit' package by default, and one thing that was blocking was that the pyproject.toml file requires "flit" in build_system instead of "flit_core".
The build works properly if this is changed to be in accordance with the usual pyproject.toml mechanism (see https://packaging.python.org/en/latest/guides/writing-pyproject-toml/ ), though I haven't run tests beyond our use of it.
I'm happy to send a PR but this seemed awfully small for one. :)  but LMK what's easiest for you.
Thanks for providing this, btw - very useful to have these models!

happy to review pr for this 🙏

Thank you! (Sorry I didn't get a PR to you before you did it yourself, was fighting a lot of fires in our buildroot update unrelated to geojson)


"Priority Document" outlining areas of greatest need for Node.js ecosystem

I'd like to help out in the Node ecosystem in some capacity and I'm wondering if there is a document somewhere that outlines the areas of the ecosystem/codebase/etc where the most help is needed. If this document exists, please direct me to it.
The closest thing I was able to find was Node Todo but it's not ideal for the scenario I'm imagining for a few reasons:

It's very generic. It essentially encourages looking through "random" issues (i.e. no organization by area of expertise, etc.).
In order to be useful, it relies on people being vigilant about labeling issues.
There's no sense of relative level of importance, and I assume even among issues labeled "help wanted" some are more critical than others.
It only pertains to the main nodejs/node repo

If a document like I've described doesn't yet exist, here's my case for it and some thoughts and ideas.
Motivation
The reason I raised this issue in this particular repo is because I think this document would mesh really well with the mentorship program for on-boarding people who want to become regular/frequent contributors.
Encouraging specialization
It would allow them to pick an area to specialize in early on. When you're talking about 6 month duration for mentorship and potentially someone with lots of extra free-time, I think specialization can provide a big productivity boost compared to working on random pre-existing issues. I realize the plan is for the mentor and mentee to work together on a goal, but I can imagine certain mentor/mentee pairings where the mentee has a lot more free time to work than the mentor has time to actively provide guidance, so it'd be useful if there were some form of over-arching guidance (like the proposed document) for what to work on when you either can't or don't want to work on the agreed-upon goal on a given day.
Raising awareness of choices
Some people may come with an existing idea of what they want to work on. Others, like myself, are indifferent about what they work on as long as it's both within their skill-level and they have the needed domain-specific knowledge (or none is required). Generally I just want to be a "force multiplier" and work on whatever will be most appreciated and move the ecosystem along the most per unit of effort.
Even for people who have an idea of what they want to work on, and especially for the others, a document like this might alert someone to an area of interest they hadn't thought of. As a specific example, someone may not have thought of helping out with a Working Group, and aren't likely to have that idea looking through issues in the nodejs/node repo.
As an aside on Working Groups: After watching just a few various WG meetings on YouTube, it seems to me there is a high level of need for new members in multiple WGs. Due to the organization of the Contribute page, this isn't made clear in my opinion. Only four words are dedicated to WG participation.
Potential concerns
Upfront effort
This isn't an "all-or-nothing" situation, but more of a "get-out-what-you-put-in" deal. At a minimum this document could be drawn up in 5 minutes by someone with overall knowledge of the ecosystem's needs. It could just start out as something like the top level sections I describe below with a description or link to the current single highest priority item for each section. It could then potentially evolve over time.
Upkeep/maintenance
I don't think this document necessarily needs to entail a lot of maintenance. There wouldn't be much harm in it being out of date, and as areas of need change or are identified, it'd be quick and simple to modify the list. A minute or two spent updating the document could potentially lead to an outpouring of volunteers to help with a specific priority (A way to subscribe to updates may be useful).
Additionally, some portions of the list could potentially be automated. This could be as simple as linking to specific issue searches like Node Todo does.
Document structure
Top level sections
These would be based on types of contributions. For example:

sublists are just for clarification, not necessarily actual sections

Contribute to Code

Add new features
Improve existing code

Contribute to Documentation

Update/improve the Node API docs
Create/improve "process documents", README files, etc. across all repos
Work on translations

Contribute to Repo Maintenance

Triage/label GitHub Issues/PRs

Contribute Time

Become a mentor
Join WGs as a member
Become an Observer at WG meetings
Offer unofficial assistance within the WG/Repo (like an intern or "gopher")

Ranked subsections
Within the top level sections, specific areas of need could be ranked by greatest need (most understaffed, code that's blocking progress, etc.). These need not be comprehensive. At a minimum, just add things to a section as it becomes clear they are high-priority.
Contribute to Code
Areas of the codebase or modules that most need addressing. This could be as simple as a hand-edited list with a "hard-coded" priority level or as sophisticated as an SPA that uses the GitHub API to dynamically adjust this section based on something like aggregate count of labels on issues/PRs: <module-name> && ("High-Priority" || "Critical").
Contribute to Documentation
Both above approaches could potentially be used but hand-edited is probably best. Also it doesn't necessarily need to be super specific like specific documents (although that could be useful). It could just be a list of repo names to denote repos that have sub-par documentation or need help cleaning up or reviewing specific process documents, etc.
Contribute to Repo Maintenance
Probably just a ranked list of repo names. Similar to above, this could be automated using the GitHub API at some point, listing the number of open Issues and open PRs for each repo, although this isn't necessary.
Contribute Time
This section may need to be organized differently from the others and will probably be edited by hand. It may also not necessarily be ranked. Maybe a list of repos, and the types of help currently needed (possibly a matrix)?
Metrics
These things would be useful throughout the document. Most could also make good use of hyperlinks.

Repo name
Priority level

Low/Medium/High/Critical (or maybe color-coded?)
Items that become low priority could also be removed

Relevant person(s) to contact for more info
Icon/emoji denotations

Specific domain-knowledge required (Note contact person/mentor in table if applicable)
Low-hanging fruit (beginner friendly)
Recently added/updated

Conclusion
I see this document being especially useful in conjunction with the mentorship program, but it's likely to be useful to new/existing contributors outside the program too (in case it doesn't fit with this program's goals). For instance, I could see such a document being linked to from the Contribute page.

Incidentally, creating this "document" as an SPA may be a cool mentor/mentee(group?) goal and would give mentees a good high-level understanding of the Node.js ecosystem, especially if you had them interact with representatives from some WGs/repos in the ecosystem to get input on their needs. This could include an "Admin" backend to the frontend to make editing the list easier, etc.

That's all the ideas I've got for now. Sorry for such a long post and I appreciate you taking the time to read it. I have no direct experience with contributing to the Node.js ecosystem as of yet so if this whole thing is totally off-base or infeasible for some reason feel free to close this issue. :)

@MylesBorins You seem to be involved in a lot of different areas of the Node.js ecosystem so maybe you'd know this.. was there a more appropriate place to raise this issue?

@detrohutt Thanks for writing this up in great detail.
The mentorship program is in need of these "areas" to be identified in order for us to guide mentees on contributions areas of shared interest.
This initiative is bigger than the mentorship's scope, I believe this could be an initiative under the community committee, If you can attend today's meeting hopefully we'll have time to discuss this (the agenda is super full but this is definitely worth discussing).
https://github.com/nodejs/community-committee/issues/300

@Bamieh Thanks for taking the time to read it! I'd be more than happy to attend today's meeting. Do I need to be officially invited or added to an Observers list for this meeting (I know that's the process for the Modules WG) or do I just join when the link shows up?

@detrohutt you're welcome to join when the link shows up

@Bamieh Sorry I missed the commcomm meeting today. I'll be present at the Mentorship WG meeting tomorrow. Also we made some forward progress on the conceptualization of the priority document in the Security WG meeting today. I'll be opening an issue with commcomm about potentially creating a repo for the document where WG's can raise issues for things they want added/modified. Also I'll be opening an issue with the nodejs.org repo to see if they think the website is an appropriate location for the document.

Ping @codeekage

If it helps at all, here are the stock answers I give when people ask where help is most needed:

Windows parity. We have a much higher percentage of Windows users than Windows developers on the project, and Windows tends to lag a bit in terms of attention when tests start failing and stuff like that.

Documentation. Unfortunately, people often think of this as an "easy" thing. I'm not talking about fixing a typo here and adding a sentence there. I'm talking about looking at the docs holistically and making them a joy to use.

Website UX. There's an effort to redesign the website, but the website would greatly benefit from continuous UX attention.

Build. Know devops and cloud? Great! The only other thing you need is to earn the trust of the current maintainers of the project. You can do that by contributing elsewhere and/or participating in a non-member capacity on the build repo. This is basically all about making the CI server be vastly more reliable than it currently is.

Release. This requires even more trust than Build so you have to work up to it, but it's somewhere that we need more people because our current process burns out people quickly if they can't do it for a month and then take two months off or something.

Automation. Less of a problem than it once was now that there's an automation team, but still, there's lots to be done there.

As far as looking at stuff in Node.js core that needs attention, it's going to vary from person to person  but my top three would be: Windows parity (again), crypto, libuv.
It's not that we don't have people working on these things. We do, and they're great. But I find these are the areas that I have the most difficulty getting timely help because the small number of experts in those areas tend to have lots going on.
Going the other direction, a big meta-ish thing someone can help with: Finding a way to make GitHub notifications manageable for all.

@Trott, could we get volunteers from this small group who are experts to be on the Mentorship Team as mentors?
If we could find a way to develop folks in these areas that need more help and an urgent assistance, which actually gives the Mentorship Team a more focused purpose and also a medium to helping mentees too, then that will be super great.
I will also love if you could drop the links to this repos and probably WG champions to see how we could collaborate and make the ecosystem more Awesome.

Going the other direction, a big meta-ish thing someone can help with: Finding a way to make GitHub notifications manageable for all.

This is a big one for me as well. I'd love to use something like https://github.com/octobox/octobox but the permissions are a blocker for it as far as I know. The next best solution I can think of is either setting up something that prettily displays GitHub email notifications that are forwarded to it or loading the GitHub notifications page and apply custom scripts/styles in an Electron app or something.

@Trott Those are great, thank you! I was struggling to get things moving quickly enough to have actionable items ready for the June 1st Mentorship trial run, so these can probably serve as starting points for projects for the "beta testers" to start work on.
If they're already short on time I imagine asking them to mentor people may not be feasible, but I agree with @codeekage that if any of the people knowledgeable in these areas are interested in mentoring, they'd be a great addition/advantage to the initiative.
@bnb I like those ideas. I'd be willing discuss them in more depth in another issue or privately, and possibly try to rough out some initial implementation of something.

Build and release are huge areas that need help as well
On Mon, May 21, 2018, 8:37 PM A.J. Roberts<EMAIL_ADDRESS>wrote:

@Trott https://github.com/Trott Those are great, thank you! I was
struggling to get things moving quickly enough to have actionable items
ready for the June 1st Mentorship trial run, so these can probably serve as
starting points for projects for the "beta testers" to start work on.
If they're already short on time I imagine asking them to mentor people
may not be feasible, but I agree with @codeekage
https://github.com/codeekage that if any of the people knowledgeable in
these areas are interested in mentoring, they'd be a great
addition/advantage to the initiative.
@bnb https://github.com/bnb I like those ideas. I'd be willing discuss
them in more depth in another issue or privately, and possibly try to rough
out some initial implementation of something.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nodejs/mentorship/issues/38#issuecomment-390826711,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAecV0kKgFGovw4N9VUXK3DXVhpcRZ6vks5t013egaJpZM4TpwJ9
.

Taking notes on this... Really hope collaborators from all round the nodejs project could contribute on this.
Have a collection of collaborators as mentors to help with onboarding.

@Trott, could we get volunteers from this small group who are experts to be on the Mentorship Team as mentors?

@codeekage You mean Windows parity, crypto, and libuv? I can't speak for other people's time, but I guess I can leave a ping here: @nodejs/platform-windows @nodejs/crypto @nodejs/libuv

What about debugging, stacktrack, logging in production?

RE Diagnostics, we're looking at establishing a list "strategic initiatives", each with a designated "champion" to help organize & drive.   See diagnostics/issues/185.
If someone wants to get involved, best thing is to look through issues, find something interesting, and ping on it.  Alternatively, attend the working group meetings (generally bi-weekly, but next one will probably be 2018-06-13 due to collab summit), or reach out to me directly & I can help direct.
And, yes, we'd love to have more ppl involved & doing work. :)

Yep, the diag working group is quite active and I'm sure some of us would be quite happy to be mentors. I volunteer myself, at the least.

Going to remove the cc-agenda label for now, since it's been on since May 3rd and has been discussed to some extent. If there's further things that need to be discussed at the CommComm level, please don't hesitate to add it back 🙌

@bnb Actually I'd like to have some further discussion on https://github.com/nodejs/community-committee/issues/322 but didn't bother trying to get that added to the agenda since I figured it more or less fell under this issue since it was already on the agenda.

@bnb as far as I know, I don't have the ability to add labels to things.

Gotcha. I'll add that issue to the agenda, then 😅

crypto, and libuv

Sorry, missed the ping.  Speaking for myself, I don't have time to extensively mentor others; not beyond what I already do on the bug tracker(s).


Improve tensor operators

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 99.32%. Comparing base (f47a43a) to head (9bb864c).
Report is 216 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #111      +/-   ##
==========================================
+ Coverage   99.23%   99.32%   +0.08%
==========================================
  Files         175      189      +14
  Lines       39928    40752     +824
==========================================
+ Hits        39623    40476     +853
+ Misses        305      276      -29

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


Added step in CD workflow to add a tag when publishing a new DEV version (needed for cocoapod)

Description
In the current CD workflow, a new dev version is built and published for each new commit in master branch. However, this would only release the "maven" artefacts. For project using cocoapod, the new release would not be available since it requires that a tag is added on github.
This adds an extra step to properly create and push the tag.
Motivation and Context
The usual flow was manually create a tag each time a new releases was needed. Now it is automatic.
Types of changes

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

As a stretch goal we could also properly publish versions to CocoaPods repository. We would have to validate the podspec with pod spec lint and publish it with pod trunk push.


TCP backlog

2017-06-14T04:57:00.630562455Z 1:M 14 Jun 04:57:00.630 # WARNING: The TCP
backlog setting of 511 cannot be enforced because
/proc/sys/net/core/somaxconn is set to the lower value of 128.
I'm try fixing on image, but the read-only will be a problem in this case. I'll investigating more.

It's just warning, but If you need more connection backlogs:
Docker has --sysctl option which might be useful. And you could try sysctl -w net.core.somaxconn=65535 command in the entrypoint.


Unable to import highlight.js

It seems that I cannot import package "highlight.js" ... I suspect that bundler thinks of it as a javascript file.

Thanks!
I will check it

@tomitrescak
just made a test and everything works
npm install highlightjs -S
code in app.ts
import * as highlightjs from 'highlightjs';
import  'highlightjs/styles/default.css';
highlightjs.initHighlightingOnLoad();

code in index.html

#include <iostream>

int main(int argc, char *argv[]) {

  /* An annoying "Hello World" example */
  for (auto i = 0; i < 0xFFFF; i++)
    cout << "Hello, World!" << endl;

  char c = '\n';
  unordered_map <string, vector<string> > m;
  m["key"] = "\\\\"; // this is an error

  return -2e3 + 12l;
}

result

Hmm, no idea then, I keep receiving 'cannot find package 'highlight.js' ... I will work on it and report back. I'll close it for now then.

@tomitrescak  clean the cache :)


Sanity check for URLs doesn't give obvious error message

The sanity check for URLs (e.g. post_install) works, but it isn't obvious from the message what went wrong - all it displays is the HTTP error code. It could also print the URL and a comment about sanity checking.
    elif resource_type == 'URL':
        scheme = urlparse(resource_value).scheme
        if scheme == 's3':
            pass
        else:
            try:
                urllib.request.urlopen(resource_value)
            except urllib.error.HTTPError as e:
                print(e.code)
                sys.exit(1)
            except urllib.error.URLError as e:
                print(e.args)
                sys.exit(1)

Issue is fixed : https://github.com/awslabs/cfncluster/commit/3fc182a4d6e55d0601f03a9f0fc669d0fd80d8e7


Place uris from index

I've run this locally, together with the app version pulled here https://github.com/usaybia/srophe-eXist-app/pull/37
Seems to basically work fine, except that there is no main title (h1) for the place on the place detail/record page. The headword does show up in Browse though.
Is this because it's supposed to grab an English headword with @xml:lang='en' as I see is sometimes defined in places.xqm? These headwords are labeled "en-x-lhom". I could change them to just "en" but I would prefer to have the headword display starts-with(@xml:lang, 'en-') or equivalent.

@nathangibson I will make an issue for the english language headwords. I will port it back to Syriaca.org (in fact I think it exists for persons, but not places already).


Add "Send/Use Current Time" Check Box to Message Simulator

Add a "Send/Use Current Time" check box to the MessageSimulator to indicate that the simulated time used in messages should be based off the current date-time.
The date/time attribute/tag to be used is "datetimesubmitted" If it exists update it, otherwise add it.
datetimesubmitted = Now()
Another future option (when/if datetimesubmitted is valid/real data): When the simulator starts - the first datetimesubmitted encountered in the xml file = StartTime; then datetimesubmitted = datetimesubmitted - (Start Time) + Now()

The first part of this issue is resolved in a0b95ce3dff31c714270beb3c2dfe1bd3dadc61e . There is now a list of fields that can be checked on to override those fields' values with the current time in UTC.
I'm punting the second part of this issue. It is sufficiently complex to deserve its own issue, #49, which we can resolve at a later time.

Verified


Adding DELETE for image sets that have no devices using them.

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes # (issue)
Type of change
What is it?

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Documentation update
[ ] Tests update
[ ] Refactor

Checklist:

[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[X] I run make pre-commit to check fmt/vet/lint/test-no-fdo

Writing tests now.
Looking for early feedback on this draft.
The plan for future PR's is to create routes for getting all device ids for an Image and an Image Set.

Tests have been added, the code is ready for review

@AaronH88 please update path.yaml with the new endpoint


feat(layout): add menu support to header

Add support for menus in Layout header

:rocket: PR was released in v1.8.0 :rocket:

:rocket: PR was released in v1.8.0 :rocket:

:rocket: PR was released in v1.8.0 :rocket:

:rocket: PR was released in v1.8.0 :rocket:

:rocket: PR was released in v1.8.0 :rocket:

:rocket: PR was released in v1.8.0 :rocket:

:rocket: PR was released in v1.8.0 :rocket:

@avkvirtru Agreed, this will be something that we need to refactor, most likely.
It seems Abacus' design doesn't match the multi link design:


DRAFT First version

I'm particularly not sure about the slim manager flow. I implemented the core methods according based on following requirement;

find_available_slims: query for all slims available in a specified ontology, returning name and definition.
Show_slim_contents: list names and IDs of all terms in slim.

I plan to keep record of every slim that is queried in a SlimManager object as a list of Slim. I cannot decide whether to build that list once at the start, retrieving all the slim from Ubergraph, or build up the list as the user queries the slim in each ontology. I go with the second approach for now.
An example flow can be seen in below;

User callsget_slim_list with 'Cell Ontology' to retrieve slims in CL
Slim list initialized with name and description of the slims, without slim members. Not sure if we also retrieve the members with this method. Would it be a waste to attempt retrieving all those terms that might not even be used?
User checks the slim list and pick one slim, and retrieves slim content using the slim name with get_slim_members. It populates the Term list in the Slim list within SlimManager object
Then, minimal_slim_enrichment and full_slim_enrichment is called with a list of slim names from previous step. Content of the slims are retrieved from the Slim list within SlimManager object. Does this approach make sense or should we retrieve the slim members each time we use the enrichment methods?

Does this approach make sense or should we retrieve the slim members each time we use the enrichment methods?

I think performance will be fine whatever approach you take.  The decision is whether to manage complexity in code or directly in queries  - probably best to base this decision on which approach is easiest to understand/debug.
In this case I think the simplest approach might be to write  SPARQL queries that reference the slim directly.  That way there is no need to caches lists of members.

Looking at the workflow above - I wasn't expecting users to pull lists of terms and then plug them in to queries. The slim_encrichment methods take a list of slim names - not a list of term names.

It takes a list of slim name not the members. It retrieves the member list from cached SlimManager object, thought.


help please with a concat issue

I have a virtualization scheme for a "daily" time series of a projected netcdf, with a problem at concatenation that I have isolated one element at steps 1716:1718.  Other ranges in the sequence concatenate without problem, but there are other problem elements later in the sequence that I haven't pinned yet.
(I say "daily" because it is mixed, starting at every two days, moving to every day, and then with a ~21ish day gap in the sequence - these are filled with dummy files that do not have the primary variable NO7_ICECON, and I've flushed those out from the set already).
here's the error message for the whole set
vds = xarray.concat(vd0, dim = 'time', coords = 'minimal', compat = 'override')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/srv/conda/envs/notebook/lib/python3.12/site-packages/xarray/core/concat.py", line 277, in concat
    return _dataset_concat(
           ^^^^^^^^^^^^^^^^
  File "/srv/conda/envs/notebook/lib/python3.12/site-packages/xarray/core/concat.py", line 674, in _dataset_concat
    combined_var = reindex_variables(
                   ^^^^^^^^^^^^^^^^^^
  File "/srv/conda/envs/notebook/lib/python3.12/site-packages/xarray/core/alignment.py", line 79, in reindex_variables
    new_var = var._getitem_with_mask(indxr, fill_value=fill_value_)
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/srv/conda/envs/notebook/lib/python3.12/site-packages/xarray/core/variable.py", line 851, in _getitem_with_mask
    data = indexing.apply_indexer(indexable, actual_indexer)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/srv/conda/envs/notebook/lib/python3.12/site-packages/xarray/core/indexing.py", line 1031, in apply_indexer
    return indexable.oindex[indexer]
           ~~~~~~~~~~~~~~~~^^^^^^^^^
  File "/srv/conda/envs/notebook/lib/python3.12/site-packages/xarray/core/indexing.py", line 369, in __getitem__
    return self.getter(key)
           ^^^^^^^^^^^^^^^^
  File "/srv/conda/envs/notebook/lib/python3.12/site-packages/xarray/core/indexing.py", line 1508, in _oindex_get
    return self.array[key]
           ~~~~~~~~~~^^^^^
  File "/home/mdsumner/.local/lib/python3.12/site-packages/virtualizarr/manifests/array.py", line 233, in __getitem__
    raise NotImplementedError(f"Doesn't support slicing with {indexer}")
NotImplementedError: Doesn't support slicing with (array([ 0,  1,  2, ..., -1, -1, -1]), slice(None, None, None), slice(None, None, None))

those were opened with
open_virtual_dataset(filepath, indexes = {},
                              loadable_variables=['x', 'y', 'time', 'crs'],
                              decode_times = True, reader_options={'storage_options': creds})

the first problem instance is 1717 as we see here:
 vd0[1716:1718],
([<xarray.Dataset> Size: 110kB
Dimensions:     (time: 1, y: 332, x: 316)
Coordinates:
  * x           (x) float64 3kB -3.938e+06 -3.912e+06 ... 3.912e+06 3.938e+06
  * y           (y) float64 3kB 4.338e+06 4.312e+06 ... -3.912e+06 -3.938e+06
  * time        (time) datetime64[ns] 8B 1987-08-20
Data variables:
    N07_ICECON  (time, y, x) uint8 105kB ManifestArray<shape=(1, 332, 316), d...
    crs         |S1 1B ...
Attributes: (12/49)
    Conventions:               CF-1.6, ACDD-1.3
    acknowledgment:            These data are produced by the NASA Cryospheri...
    cdm_data_type:             grid
    citation:                  DiGirolamo, N. E., C. L. Parkinson, D. J. Cava...
    contributor_name:          Nicolo E. DiGirolamo, Claire Parkinson, Per Gl...
    contributor_role:          project_scientist, project_scientist, project_...
    ...                        ...
    summary:                   This data set is generated from brightness tem...
    time_coverage_duration:    1987-08-20T00:00P1D
    time_coverage_end:         1987-08-20 23:59.99
    time_coverage_resolution:  P1D
    time_coverage_start:       1987-08-20 00:00.00
    title:                     Sea Ice Concentrations from Nimbus-7 SMMR and ...,

<xarray.Dataset> Size: 110kB
Dimensions:     (time: 1, y: 332, x: 316)
Coordinates:
  * x           (x) float64 3kB -3.938e+06 -3.912e+06 ... 3.912e+06 3.938e+06
  * y           (y) float64 3kB 4.338e+06 4.312e+06 ... -3.912e+06 -3.938e+06
  * time        (time) datetime64[ns] 8B 1987-08-21
Data variables:
    F08_ICECON  (time, y, x) uint8 105kB ManifestArray<shape=(1, 332, 316), d...
    crs         |S1 1B ...
Attributes: (12/49)
    Conventions:               CF-1.6, ACDD-1.3
    acknowledgment:            These data are produced by the NASA Cryospheri...
    cdm_data_type:             grid
    citation:                  DiGirolamo, N. E., C. L. Parkinson, D. J. Cava...
    contributor_name:          Nicolo E. DiGirolamo, Claire Parkinson, Per Gl...
    contributor_role:          project_scientist, project_scientist, project_...
    ...                        ...
    summary:                   This data set is generated from brightness tem...
    time_coverage_duration:    1987-08-21T00:00P1D
    time_coverage_end:         1987-08-21 23:59.99
    time_coverage_resolution:  P1D
    time_coverage_start:       1987-08-21 00:00.00
    title:                     Sea Ice Concentrations from Nimbus-7 SMMR and ...],)

when we concatenate it fails
xarray.concat(vd0[1716:1718], dim = 'time', coords = 'minimal', compat = 'override')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/srv/conda/envs/notebook/lib/python3.12/site-packages/xarray/core/concat.py", line 277, in concat
    return _dataset_concat(
           ^^^^^^^^^^^^^^^^
  File "/srv/conda/envs/notebook/lib/python3.12/site-packages/xarray/core/concat.py", line 674, in _dataset_concat
    combined_var = reindex_variables(
                   ^^^^^^^^^^^^^^^^^^
  File "/srv/conda/envs/notebook/lib/python3.12/site-packages/xarray/core/alignment.py", line 79, in reindex_variables
    new_var = var._getitem_with_mask(indxr, fill_value=fill_value_)
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/srv/conda/envs/notebook/lib/python3.12/site-packages/xarray/core/variable.py", line 851, in _getitem_with_mask
    data = indexing.apply_indexer(indexable, actual_indexer)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/srv/conda/envs/notebook/lib/python3.12/site-packages/xarray/core/indexing.py", line 1031, in apply_indexer
    return indexable.oindex[indexer]
           ~~~~~~~~~~~~~~~~^^^^^^^^^
  File "/srv/conda/envs/notebook/lib/python3.12/site-packages/xarray/core/indexing.py", line 369, in __getitem__
    return self.getter(key)
           ^^^^^^^^^^^^^^^^
  File "/srv/conda/envs/notebook/lib/python3.12/site-packages/xarray/core/indexing.py", line 1508, in _oindex_get
    return self.array[key]
           ~~~~~~~~~~^^^^^
  File "/home/mdsumner/.local/lib/python3.12/site-packages/virtualizarr/manifests/array.py", line 233, in __getitem__
    raise NotImplementedError(f"Doesn't support slicing with {indexer}")
NotImplementedError: Doesn't support slicing with (array([ 0, -1]), slice(None, None, None), slice(None, None, None))

and other sequences like [0:1500] or [1718:1720] work fine.
The full workflow is here if that's needed, it should be reproducible and easy to run apart from obtaining n for the available cpus (which I'm sure there's a better style generally - with 24 cpus it runs within ~4min - ((Hobart TAS<->Perth WA))).
from virtualizarr import open_virtual_dataset
import pyarrow.parquet
import fsspec
import os
import dask.multiprocessing
import xarray

parquetfile = "https://projects.pawsey.org.au/idea-objects/idea-objects.parquet"

n = int(os.environ["SLURM_JOB_CPUS_PER_NODE"])

dask.config.set(scheduler='processes', num_workers = n)

bucket = 'idea-10.5067-mpyg15waa4wx'
## dataset = 'nsidc25ksouth'
aws_credentials = {"endpoint_url": "https://projects.pawsey.org.au",  "anon": True}

with fsspec.open(parquetfile) as f:
    s3table = pyarrow.parquet.read_table(f, filters=[('Bucket','==', bucket)])

nclist = s3table.to_pandas().Key.tolist()
nc = [f's3://{bucket}/{nc0}' for nc0 in nclist]
nc.sort()

## return None if the file is a dummy containter
def open_virtual(filepath, creds):
  ds = open_virtual_dataset(filepath, indexes = {},
                              loadable_variables=['x', 'y', 'time', 'crs'],
                              decode_times = True, reader_options={'storage_options': creds})
  if len(ds.keys()) > 1:
    return(ds)
  else:
    return(None)

vdd = [
  dask.delayed(open_virtual)(filepath, aws_credentials)
  for filepath in nc]

vd = dask.compute(vdd)

## flush out the dummy slices (we gave None from the virtualization step)
vd0 = [x for x in vd[0] if x is not None]

## BAP unfortunately
vds = xarray.concat(vd0, dim = 'time', coords = 'minimal', compat = 'override')

Thanks!!  Appreciate any pointers this represents quite a lot of slow progress for me, other datasets have been unproblematic.

I think this is because you have some corrupted files in that dataset: they are missing the N07_ICECON variable – or at least, that's what I got while trying to reproduce, your output shows that you appear to have a slightly different issue where one of the variables is called F08_ICECON while the other is N07_ICECON.
To get that to work you might have to split the urls by the variable in the dataset, concat datasets with common variables, then merge the concatenated datasets together using xr.merge (this is what xr.combine_* is supposed to do, but I don't know if that works already).
Obviously, if the files are truly corrupted all you can do is trying to fix or skip them.

Oh! Sorry, entirely about the different name ... I had been aware of that in the past. Thanks for the advice on how to deal with it!

I might just

fun stuff, so these files can have 0, 1, 2, or 3 variables of that form "{code}_ICECON", and I only want one. I'll have to rejig how this gets done and prefilter for a preferred var (when one exists), I think.   I wonder if I should establish all of them as vzarrs, and then look at normalizing, so maybe I should just be combine(ing).
I might ask more widely on discourse, it's really multiple datasets with the capacity to pick one consistent time series across overlapping eras. I'm stuck on what's a good way forward, I don't want to publish a changed dataset, just give access to low-expertise users to "ok data" over the longest possible time range. (but maybe I should rewrite entirely to a Zarr given that I'm not interested in fidelity to the complexities of the current netcdfs).


unboxing without struct

While most of the time the struct mapping approach is fine, I am wondering whether there is also a way to use Unbox without. Similar to what SwiftyJSON or JASON allows you to do. Basically allowing to use the Unboxer directly somehow.

Hi @tcurdt, you can use the cusom Unboxing API for this. This enables you to get direct access to an Unboxer, to perform whatever operations you want together with it.
See Unboxer.performCustomUnboxingWithDictionary/Array for more information :)

Thanks! Would be great to add an example to the readme though.

@tcurdt, there's already a section about the custom unboxing API with a code example in the README :) Check the section titled Custom unboxing.

Doh! I guess I just didn't expect that to hid behind "custom unboxing" and/or Unboxer.performCustomUnboxingWithDictionary. Anyway! Thanks!


[Feature] Don't use hive partition file cache when executing "insert into target_table select from hive table"

What type of PR is this：

[ ] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #
For "insert into target_table select from hive_table" in StarRocks, the query result may not be correct if the cached file information for the Hive partition has expired. This can cause incorrect data to be inserted. This error will occur after the user side appends the file to the existing partition. To prevent this issue, we disabled the Hive metadata cache when the hiveTable is used as a queryRelation in the insert statement.
Problem Summary(Required) ：

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[ ] I have checked the version labels which the pr will be auto backported to target branch

[ ] 3.0
[ ] 2.5
[ ] 2.4
[ ] 2.3

[FE PR Coverage Check]
:heart_eyes: pass : 30 / 34 (88.24%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/connector/RemoteFileOperations.java
3
5
60.00%
[52, 60]

:large_blue_circle:
com/starrocks/connector/CachingRemoteFileIO.java
5
7
71.43%
[116, 117]

:large_blue_circle:
com/starrocks/connector/hive/HiveMetadata.java
4
4
100.00%
[]

:large_blue_circle:
com/starrocks/catalog/HiveTable.java
6
6
100.00%
[]

:large_blue_circle:
com/starrocks/sql/analyzer/InsertAnalyzer.java
3
3
100.00%
[]

:large_blue_circle:
com/starrocks/sql/analyzer/AnalyzerUtils.java
9
9
100.00%
[]

[FE PR Coverage Check]
:heart_eyes: pass : 30 / 36 (83.33%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/connector/CachingRemoteFileIO.java
2
7
28.57%
[76, 115, 116, 117, 119]

:large_blue_circle:
com/starrocks/connector/RemoteFileOperations.java
4
5
80.00%
[60]

:large_blue_circle:
com/starrocks/connector/hive/HiveMetadata.java
4
4
100.00%
[]

:large_blue_circle:
com/starrocks/catalog/HiveTable.java
6
6
100.00%
[]

:large_blue_circle:
com/starrocks/sql/analyzer/InsertAnalyzer.java
4
4
100.00%
[]

:large_blue_circle:
com/starrocks/sql/analyzer/AnalyzerUtils.java
10
10
100.00%
[]

How about the cached partition names? it may be invalid for insert

How about the cached partition names? it may be invalid for insert

If a partition doesn't exist, it will throw partition path not found error exception. This pr is mainly to prevent users from importing wrong partition data, and the user is not aware of the wrong data after being imported.

[FE PR Coverage Check]
:disappointed: fail : 31 / 46 (67.39%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/connector/hive/IHiveMetastore.java
0
1
00.00%
[76]

:large_blue_circle:
com/starrocks/connector/hive/CachingHiveMetastore.java
1
9
11.11%
[210, 211, 212, 509, 510, 511, 513, 515]

:large_blue_circle:
com/starrocks/connector/CachingRemoteFileIO.java
2
7
28.57%
[76, 115, 116, 117, 119]

:large_blue_circle:
com/starrocks/connector/RemoteFileOperations.java
4
5
80.00%
[60]

:large_blue_circle:
com/starrocks/connector/hive/HiveMetadata.java
4
4
100.00%
[]

:large_blue_circle:
com/starrocks/catalog/HiveTable.java
6
6
100.00%
[]

:large_blue_circle:
com/starrocks/sql/analyzer/InsertAnalyzer.java
4
4
100.00%
[]

:large_blue_circle:
com/starrocks/sql/analyzer/AnalyzerUtils.java
10
10
100.00%
[]

[FE PR Coverage Check]
:disappointed: fail : 34 / 52 (65.38%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/connector/hive/IHiveMetastore.java
0
1
00.00%
[76]

:large_blue_circle:
com/starrocks/connector/hive/CachingHiveMetastore.java
1
9
11.11%
[210, 211, 212, 509, 510, 511, 513, 515]

:large_blue_circle:
com/starrocks/connector/CachingRemoteFileIO.java
2
7
28.57%
[76, 115, 116, 117, 119]

:large_blue_circle:
com/starrocks/qe/SessionVariable.java
2
4
50.00%
[1181, 1182]

:large_blue_circle:
com/starrocks/connector/RemoteFileOperations.java
4
5
80.00%
[60]

:large_blue_circle:
com/starrocks/catalog/HiveTable.java
7
8
87.50%
[166]

:large_blue_circle:
com/starrocks/connector/hive/HiveMetadata.java
4
4
100.00%
[]

:large_blue_circle:
com/starrocks/sql/analyzer/InsertAnalyzer.java
4
4
100.00%
[]

:large_blue_circle:
com/starrocks/sql/analyzer/AnalyzerUtils.java
10
10
100.00%
[]


the speed problem

Why is it slow to deploy the program to the graphics card, and even reports an error saying that the version is too old, after I have installed the corresponding environment (torch1.4.0, python3.6, scikit-learn0.21.1)? However, other versions of torch load quickly on the graphics card, but an error occurs at the step of "loss1.backward". Have you encountered a similar problem before?

Hi @luojing1030 and thank you for your question. Since our project is mainly based on the official code of DTFD-MIL, running the code also require the use of PyTorch 1.4.0 as the official one does. There are comments in the official code mentioning that change the sequence of loss backward can solve this problem in newer PyTorch versions (which can be found here), but we are not sure whether will that affect the performance.

Thank you for your help, and also thank you for simplifying the code for the convenience of others.


Roll Flutter Engine from 2be41c6d0152 to 06ac179ed48c (1 revision)

https://github.com/flutter/engine/compare/2be41c6d0152...06ac179ed48c
2023-03-02<EMAIL_ADDRESS>Remove PlatformConfiguration and ViewConfiguration (flutter/engine#40012)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC jsimmons@google.com,rmistry<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


Some other omissions: handshake, auth

Hey there! Thanks for taking the time to actually write these errata - finally having an official reference for these is great. 👍
Handshake
An omission from the RTMP spec that I do not see addressed is the handshake: the original RTMP spec says to send random bytes and then return a copy of the received random bytes from the other side (I simplified a little for sake of brevity), while in reality the handshake hides an additional verification that you're connected to a "genuine" Adobe server/client. If this verification fails, H264 capabilities are disabled (at least by the official flash client versions I've personally tested - but this is all many years ago and testing it again today is... painfully complicated, to say the least).
Considering that...

Flash player has effectively gone the way of the dodo, leaving only "non-official" player implementations in actual use (which usually ignore this verification - but not always).
The verification process is now public knowledge (the algorithm is easily found with a little searching in unofficial places, and also part of many open source media server implementations)

... I think it would be worthwhile to actually note this algorithm and the effect it had/has on playback in Flash Player in these errata, or at the very least to include some wording that the returned handshake data should never be checked for integrity (being an actual echo of the sent data; since it may not be). And perhaps - if verification is implemented at all - discourage checking for success, since limiting the use of H264 in this day and age seems a little moot.
Auth
Another omission is the username/password authentication mechanism. Specifically, the method when the server may return an error message with a description field containing ?authmod=adobe, which seems to be the "official" way to handle username/password authentication and has de-facto become the standard in the industry as far as I'm aware (I think there exists only one alternative, which is not in widespread use).
In particular, I'd like to see a note that the description field does not make use of the usual query param encoding for regular URLs. The + symbol should not be decoded to space (common practice for URL params), but instead used as-is. Considering base64 encoding is used in these fields and the + symbol is part of the base64 character set, I'd say this is an important detail.

re the handshake: i intentionally didn't say anything about the cryptographic handshake, and in fact that was what i was referring to in the Introduction section where i say

It does not address private or undocumented extensions for which interoperation is not desired by the extending parties.

i helped create the cryptographic handshake, so i have inside information that interoperation was "not desired by the extending parties". it would not be appropriate for me to describe it in any way.
i'll try to think of the best way, using BCP 14 terms, to describe how endpoints that don't care about this should ignore it.
for interoperation with Flash Player or AIR, if you want to use H.264, you can just use RTMFP instead, since H.264 is not restricted with that transport. :)
re auth: i'll check to see what Adobe Media Server does when it wants a username/password and you don't or give it the wrong one. as far as the protocol is concerned, it should be sufficient to describe that connect can take additional parameters of any types, that they can be strings, some servers might interpret them as usernames and passwords, and an auth failure should be like any other connect failure resulting in an _error and an appropriate code. anything in the description (from a protocol level) shouldn't be considered as anything other than informative and implementation-specific. i'll think about what's most appropriate to clarify here.
also see my companion RTMP Family URI Schemes doc section on userinfo.

regarding auth: the authmod=adobe stuff is not part of RTMP nor even part of a stock Adobe Media Server installation; it is part of application-specific Adobe Primetime behavior and the "authentication module". see https://helpx.adobe.com/primetime/packagers/live_packager_getting_started.pdf and search for authmod for an explanation of this application-specific authentication protocol. note too that Flash Player and AIR won't deal with this protocol automatically; the connection rejections and further auth handshaking must all be done in ActionScript.
however, reading how this module works (and how it uses query parameters in the RTMP URI) is pushing me to update the description of the app property in the connect command's Command Object. Flash Player and AIR include any URI query parameters in the app property, but my description currently just says to include the URI's path minus any leading slash. the next rev (coming shortly) will bring the description in line with Flash Player/AIR behavior, since it's probably required to implement Primetime auth.

updated. please see

handshake
app
optional user arguments

(though the Primetime auth method you referred to appears to use URI query parameters and not optional user arguments to the connect command; however, that needed to be addressed anyway)

i also added a section on Authentication that links to the Primetime Live Packager document, and gives examples of other ways of doing authentication.

Yeah, those additions help a lot in making this more complete, thanks. 👍
Interoperation not being desired at the time was fairly obvious to me, as the way everything works (and explicitly isn't described) makes it clear this was an attempt to lock out non-Adobe software vendors from using more modern codecs and thus gain an advantage over them. I just figured as the algorithm is both public knowledge now and no longer serves a practical purpose today (since Flash is dead and all... plus H264 is hardly "modern" anymore) it might be neat to memorialize it here in some way.
The change to be prepared for handshake mismatches like this covers everything that is still relevant today, so I'll let it rest. 😉


BUG: bounded L-BFGS-B doesn't work with a scalar.

Describe your issue.
The  following example worked with 1.7.*, but not with version 1.8. @tylerjereddy, this needs to be fixed before the final release of 1.8.0. I have a PR incoming.
Reproducing Code Example
import numpy as np
from scipy.optimize import minimize, rosen

def f(x):
    return np.sum(x**2)

x0 = 17
res = minimize(f, x0, bounds=[(-100, 100)], method='L-BFGS-B')

Error message
---------------------------------------------------------------------------
IndexError                                Traceback (most recent call last)
/var/folders/m8/gwtcncws12jf60xw5n6knwnw0000gn/T/ipykernel_92447/1079589486.py in <module>
      6
      7 x0 = 17
----> 8 res = minimize(f, x0, bounds=[(-100, 100)], method='L-BFGS-B')
      9 print(res)

~/Documents/Andy/programming/scipy/scipy/optimize/_minimize.py in minimize(fun, x0, args, method, jac, hess, hessp, bounds, constraints, tol, callback, options)
    664                                                        x_fixed, min_dim=2,
    665                                                        remove=1)
--> 666         bounds = standardize_bounds(bounds, x0, meth)
    667
    668     if meth == 'nelder-mead':

~/Documents/Andy/programming/scipy/scipy/optimize/_minimize.py in standardize_bounds(bounds, x0, meth)
    927     elif meth in ('l-bfgs-b', 'tnc', 'slsqp', 'old'):
    928         if isinstance(bounds, Bounds):
--> 929             bounds = new_bounds_to_old(bounds.lb, bounds.ub, x0.shape[0])
    930     return bounds
    931

IndexError: tuple index out of range

SciPy/NumPy/Python version information
1.8.dev

The reason this occurs is because there's new machinery to filter out bounds that are equal in 1.8.0. This machinery does a round trip with old-new-old bounds. The round trip fails when x is not an array.
>>> x0 = 17
>>> x0 = np.asarray(17)    # occurs at the start of minimize
>>> print(x0)
array(17)
>>> x0.shape
()
>>> x0.shape([0])    # occurs when converting new bounds back to old
---------------------------------------------------------------------------
IndexError                                Traceback (most recent call last)
/var/folders/m8/gwtcncws12jf60xw5n6knwnw0000gn/T/ipykernel_95548/835018037.py in <module>
----> 1 x0.shape[0]

IndexError: tuple index out of range

I confirmed that this was working in 1.7.3, but doesn't work in 1.8.0.dev.

x0 = np.asarray(17)    # occurs at the start of minimize

Could this become

x0 = np.atleast1d(17)    # occurs at the start of minimize

?

@mdhaber , see #15229


Support error message in responses with status != 500

By test example
mockyeah.get('/wondrous', { status: 422 }); will return a response with code 422.
However, when I set
mockyeah.get('/wondrous', { status: 422, message: "MYERRORCODE" }); mockyeah won't start.
Error message:
Error: Response option(s) invalid. Options must include one of the following: fixture, filePath, html, json, text, status, headers, raw, latency, type
at validateResponse (/home/sebastian/legolas/frontend/node_modules/mockyeah/app/lib/RouteResolver.js:42:11)
Our backend will return 422 but with several error codes in the field message. Therefore for us at least, it is necessary to be able to define this field

Are you expecting message to be a property in a JSON response? i.e.
mockyeah.get('/wondrous', { status: 422, json: { message: "MYERRORCODE" }});

Thanks, it worked! (blush)


Added A New Game Alphabet Clicker

PR Description 📜
Please include summary related to the issue you have fixed and describe your PR in brief over here by specifying the issue number on which you were working below
Fixes #3368

Mark the task you have completed ✅

[x] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I have followed proper naming convention showed in CONTRIBUTING GUIDELINE
[x] I have added screenshot for website preview in assets/images
[x] I have added entries for my game in main README.md
[x] I have added README.md in my folder
[x] I have added working video of the game in README.md (optional)
[x] I have specified the respective issue number for which I have requested the new game.

Add your screenshots(Optional) 📸

Thank you soo much for contributing to our repository 💗

Thank you @MohanaSrinivas ,for creating the PR and contributing to our GameZone 💗
Review team will review the PR and will reach out to you soon! 😇
Make sure that you have marked all the tasks that you are done with ✅.
Thank you for your patience! 😀

@kunjgit I have Changed Changes That You Are Requested Once Review It

@MohanaSrinivas you are not following proper guidelines make sure you are following all of them and make PR again!

Thank you  @MohanaSrinivas , for your valuable time and contribution in our GameZone 💗.
It’s our GameZone, so Let’s build this GameZone altogether !!🤝
Hoping to see you soon with another PR again 😇
Wishing you all the best for your journey into Open Source🚀


Fix failing type interference for floating point literal

WIP - currently just a new failing test!
https://github.com/rust-analyzer/rust-analyzer/issues/1592

Just a quick note: you don't need to go that route to test this. You can simply use the "Show syntax tree" command in VS Code.

The lexer decides that 42f64 is an integer literal here: https://github.com/rust-lang/rust/blob/master/src/librustc_lexer/src/lib.rs#L419

LGTM, but the test should be moved to infer. It could also use a mark

Thanks. I've moved the test to infer, but marks don't seem to work here as the test and the code under test are in different crates (ra_hir and ra_syntax respectively).

bors r+
Thanks!


Fixed: #23 - Added a CONTRIBUTING.md file

Added a CONTRIBUTING.md file
Referred this file. https://github.com/99xt/serverless-dynamodb-local/blob/v1/CONTRIBUTING.md
Added the general gitter channel as the gitter channel since i couldn't find the gitter channel of this project.
if there is a dedicated gitter channel for this project please comment.
@rehrumesh  please review

@isuruAb
merge this branch with the latest source to get the test cases passing.


[Finder] Vodka url error for address

Summary
Vodka url error for address
https://finder.terra.money/vodka/account/terra1wg2mlrxdmnnkkykgqg4znky86nyrtc45q336yv
Expected
Account page for Vodka is displayed successfully.
Environments

Chain: soju
OS: Windows 10

Reproduce

Open 'Station' app > Sign in
Select 'Vodka' chain
Click on address link
Confirm the url

https://finder.terra.money/`vodka-0001` is correct


Dealing with environment variables

How to deal with "undefined" variables, that are loaded by nextflow.config or exist in the environment?

Is there a way to silence these errors? If so it would be nice to have a quick fix above for ignoring that error at a line basis.

Implicit environment variables like this will not be supported in the future because it is impossible to tell between an environment variable and a regular variable. We may add some alternative syntax in the future, but for now you can do System.getenv(REF_ROOT) to avoid the error
https://nextflow.io/docs/latest/vscode.html#excluded-syntax


doc: adding external declars to rule sets

Going off the syntax for removing a rule from a rule set, this seems to be the syntax for adding an aesop rule about an imported declaration to a rule set. If I'm wrong, please let me know what the preferred method is (if there is one). Also minor edits for distinguishing the 'adding/removing' sections of the README.

Thank you very much! I've changed the wording a bit; if the new version wouldn't have addressed your initial question, please feel free to reopen.


Dell LightFx feature request

Hello, this is a request for you to potentially add support for older LightFx devices (M1710, M1730, 720 H2c, 630i, etc)

Model: Dell XPS M1730
Model details: 3 16-colour lighting zones (left speaker, right speaker, touchpad), 2 dimmable lid wings and dimmable keyboard lighting
OS: Windows 7 Ultimate x64 SP1 7601, Windows 10 21H2

However, I did run into an issue collecting data for you. On these devices, lighting appears to be controlled over SMBus, not USB.
Dell XPS M1730 Wistron DS1 Siberia 06248-SC Rev SC.pdf
Here I have attached a datasheet for the model, on page 37 you'll find the controller information.
Is there anything I can do to help you implement this? Thank you for reading!

Oh, it's funny. Like Aurora R6/7.
You know, controlling hardware directly is a hard task under Windows - M$ don't like open source developers, so i was forced to use clean rootkit code to run unsigned driver.
Good news are Dell lazy too (developing drivers isn't so cheap and fast), so they expose some interfaces into ACPI and WMI.
We need to look for it using BIOS dump.


Various code quality improvements and added TODOs for suggestions for security and code quality

Various code quality improvements and added TODOs for suggestions for security and code quality

Thank you for working on this, James. Please make the corrections requested, and re-submit the pull request.


feat(pkg/client,pkg/config):tm config

What this PR does:
Implement tm config
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
None

Codecov Report

Merging #398 (d1ca24b) into master (c3cd13b) will increase coverage by 0.55%.
The diff coverage is 7.14%.

:exclamation: Current head d1ca24b differs from pull request most recent head 6ebb2d3.  Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


TypeError occurs when I change 'this'

<EMAIL_ADDRESS>node v8.11.1
macOS
ES6/7

What is the problem?
This code:
  const logger = winston.createLogger({
    transports: [new winston.transports.Console()]
  })
  Promise.reject('test reject')
    .catch(logger.error)

causes an error:
UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'write' of undefined

What do you expect to happen instead?

Other information
The code worked well with winston@2. I expect logger.info.call(undefined, 'test') has to log a message.
I suggest to save somewhere an object reference and use this value rather than this in log/[level] methods.

It seems this issue has been fixed in master.

 No errors in master.
Thank you!


Enable some lints

I'm going to close this since it hasn't been touched for a while, to get it off our review queue. Please don't hesitate to reopen it if you have a chance to get back to it. Thanks!

no problem, I forgot this PR during my vacations.


Add JEST linting rules

Facebook/Jest provides their own ESlint plugin for Jest
https://github.com/facebook/jest/tree/master/packages/eslint-plugin-jest

Thank you!


python310Packages.etils: init at 0.6.0

Description of changes
Adds https://github.com/google/etils.
Initial motivation is that this is a dependency of jax>=0.3.14. This is a dependency of https://github.com/NixOS/nixpkgs/pull/183051.
Note: the derivation was contributed by @mweinelt (commit)

Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

@ofborg build python310Packages.etils

tests are failing. Please fix them.

tests are failing. Please fix them.

I think this is because jax is currently broken on master: https://github.com/NixOS/nixpkgs/issues/183173. I can bump this when the jax issue is resolved.

Just merged https://github.com/NixOS/nixpkgs/pull/185078 to fix jax. If you rebase on top of that I think you should be good to go now!

@ofborg build python310Packages.etils

Fails to build because tensorflow fails to build.

Fails to build because tensorflow fails to build.

Opened https://github.com/NixOS/nixpkgs/issues/185273

Maybe we should just merge this with tests disabled to unblock this PR, and then come back and re-enable tests once tensorflow is fixed?

Maybe we should just merge this with tests disabled to unblock this PR, and then come back and re-enable tests once tensorflow is fixed?

@samuela that sounds good to me. I went ahead and pushed a version with the tests disabled in case we decide to go ahead and merge.

Result of nixpkgs-review pr 183052 run on x86_64-linux 1

2 packages built:

python310Packages.etils
python39Packages.etils

Thanks @mcwitt ! This should help unblock us with the JAX upgrade and then we can come back and re-enable tests once that becomes possible


The .bin files

Have a discussion about if the .bin files are needed in the repo as they are quite large.

The bin files are essential for using the model since they contain the configuration, weights, and tokenizer in the expected format. We restructure the repo to group these files so the user can handle them all together instead of searching for each file separately.


Auto fill event address in task creation process

While creating an event, being able to quickly put in the event address in from main page would be great.  Having to put in the address  for all the events can be time consuming if the event is at the same single location.  Could it auto grab the event address as a default for every task under that event unless changed at that time?

What does 'from main page' in event creation refer to? Campaign Address?
Also it sounds like their is a requirement to default address of event from campaign and task from campaign?
Is that right @schuback @OhMcGoo ? If so seperate issues can be created for both

This functionality now exists


modestga: cannot start a new process

Happens when running test_estimation_basic_parallel() on Windows 10 with FMPy.
ERROR: test_estimation_basic_parallel (modestpy.test.test_estimation.TestEstimation)
Will use default methods ('MODESTGA', 'PS')
----------------------------------------------------------------------
Traceback (most recent call last):
  File "d:\code\modest-py\modestpy\test\test_estimation.py", line 86, in test_estimation_basic_parallel
    estimates = session.estimate()
  File "d:\code\modest-py\modestpy\estimation.py", line 299, in estimate
    m_estimates = m_inst.estimate()
  File "d:\code\modest-py\modestpy\estim\ga_parallel\ga_parallel.py", line 309, in estimate
    out = minimize(
  File "D:\code\modest-py\venv\lib\site-packages\modestga\ga.py", line 166, in minimize
    p.start()
  File "c:\users\krzys\appdata\local\programs\python\python38\lib\multiprocessing\process.py", line 121, in start
    self._popen = self._Popen(self)
  File "c:\users\krzys\appdata\local\programs\python\python38\lib\multiprocessing\context.py", line 224, in _Popen
    return _default_context.get_context().Process._Popen(process_obj)
  File "c:\users\krzys\appdata\local\programs\python\python38\lib\multiprocessing\context.py", line 326, in _Popen
    return Popen(process_obj)
  File "c:\users\krzys\appdata\local\programs\python\python38\lib\multiprocessing\popen_spawn_win32.py", line 45, in __init__
    prep_data = spawn.get_preparation_data(process_obj._name)
  File "c:\users\krzys\appdata\local\programs\python\python38\lib\multiprocessing\spawn.py", line 154, in get_preparation_data
    _check_not_importing_main()
  File "c:\users\krzys\appdata\local\programs\python\python38\lib\multiprocessing\spawn.py", line 134, in _check_not_importing_main
    raise RuntimeError('''
RuntimeError:
        An attempt has been made to start a new process before the
        current process has finished its bootstrapping phase.

        This probably means that you are not using fork to start your
        child processes and you have forgotten to use the proper idiom
        in the main module:

            if __name__ == '__main__':
                freeze_support()
                ...

        The "freeze_support()" line can be omitted if the program
        is not going to be frozen to produce an executable.

Solved: https://github.com/sdu-cfei/modest-py/commit/4e001c42f63125a318feb0db6a27d7a82439008c


fix the readme

because this is a semi-clone.

ill keep this going to the master branch, its getting messy like this.


Update @gov.au/core dependency for the form component

Thanks @petrillek for raising this :)

Happy to help.


Ftrack: Fix 'rolback' typo

Brief description
Fix typo in ftrack event sync with rolback to rollback.
Testing notes:
It's hard to test as it happens only on crash of sync.

Duplicate of https://github.com/ynput/OpenPype/pull/4322


catch function parsing error

I am returning a promise from context.runAsync function and I am not able to use .then property on the returned promise. Upon doing console.log on the promise, I see -
{"\"catch\"": [Function "catch"], "finally": [Function finally], "then": [Function then]}

Upon doing console.log on the promise, I see -

what's the error?


Store the commitment as pre-image in the validator table

Since the random_seed is actually a pre-image (the first one),
store it as such in the ValidatorSet.
This has the nice effect of automatically fixing issue 694,
since addPreimage now checks the distance when a new
PreImageInfo is added.

merge at will


Intellisense support for dataclasses

I have been developing in VSCode in python>3.7.
Dataclasses were introduced in version 3.7 as part of the standard library, due to vast usage of classes for models definitions (Classes that simply hold data).
In python versions prior to 3.7, the best practice was:
3.7 > Python
class Example(object):
  def __init__(self, a:int, b: str):
    self._a = a
    self._b = b

  @property
  def a(self):
    return self._a

  @property
  def b(self):
    return self._b

Python >= 3.7
Now, in python versions after to 3.7, the best practice is:
@dataclass
class DataclassExample:
  a: int
  b: str

As you can see, In python > 3.7 the models definition is much easier and the code is more clean.
Im sure dataclasses will be widely used in the following years and versions of Python.
the intellisense for classes which are wrapped with the dataclass decorator doesn't work at all.
I didn't have any autocompletion for the fields nor for the base classes's fields. These are the classes i work with, modify, store in the database. I rely heavily on dataclasses and i think the world is going towards them, becasue it's so much more real-world problem and the code is much more clean.
Thanks for your time if you read it this far,
I think it's pretty simple to implement the intellisense for dataclasses. What do you think?

@avilum, thanks for getting in touch with us.  We'll be taking a look as soon as we can.

@avilum, this seems like a reasonable request.  We'll have to see how feasible it is.  Sometimes things that seem "pretty simple to implement" turn out to be not-so-simple. :smile:
Regardless, this is something that will have to be handled by the Python language server (or Jedi).  I'm sending this issue over to that project.  If you want this functionality in Jedi then I recommend opening an issue on that project.  Also, keep in mind that each of these projects (Python extension, language server, Jedi) is open-source and you are welcome to fork it and create a PR with an implementation for this.


Support stacks with different AWS account

Dan listed out two uses cases for this:

Stack Cleanup Webhook (Github => Lambda)

when feat branches are deleted in github, this lambda goes out and tears down the associated enviroment. This can be across two AWS accounts. Sandbox (DEV envs) and Prod (RC envs)
In order for that Lambda to have permissions, I need to have already created a Role in the Sandbox account it can assume in order to delete stacks in that account.

Cross-Account-Site Lambda@Edges

we have an Edge lambda that is used on all our sites both dev (AWS account 1) and prod (AWS account 2) this lambda needs access to that site’s bucket to access it’s routing file. This access is given via that site’s bucket policy.
I wasn’t sure if I could easily give a cross-account role access in a bucket policy so we create duplicate Lambda@Edge functions in both sandbox and production accounts as well as roles.

Ashish also shared some reasonings:

Deploy only apps that are affected, because Cfn will take decades to generate the changeset.
Ensure that an affected service / account / region doesn't impact another.
Separate free-tier and limits per account.
simpler dev onboarding, create account via sso, clone service repo, deploy.
separation of data from infra, i.e. separate xray, s3, dynamodb, rds accounts, helps a lot if looking into getting compliant.
most importantly, seed could deploy in parallel and probably figure out a deploy pattern in case of a monorepo.

The separation of data from infra seems trivial but is an amazing point because it allows separation of data (can't access all data together to make sense of it). If designed well, this would inherently make any service idempotent i.e. the underlying data layer wouldn't matter. The single-table per app approach would move into a single table per service approach. Also, decoupled apps would help in decoupling teams, reducing blast-radius on failures, etc.

Requests:

Dan https://serverless-stack.slack.com/archives/C01JG3B20RY/p1639060811159700?thread_ts=1638989201.132200&cid=C01JG3B20RY
Austin & Edward https://serverless-stack.slack.com/archives/C01HQQVC8TH/p1654100600194559
Ashish https://discord.com/channels/983865673656705025/985224097342582865/1014310900464881766

We are transition this repo to https://github.com/sst/v2 and are closing this issue for now. If it is still relevant please reopen it there - sorry for the trouble