CentOS7 Cannot initialize a headless EGL display.

File "src/train.py", line 14, in
from env import make_env
File "/home/wjg/code/src/env.py", line 5, in
from dm_control import suite
File "/home/wjg/anaconda3/envs/tdmpc/lib/python3.8/site-packages/dm_control/suite/init.py", line 24, in
from dm_control.suite import acrobot
File "/home/wjg/anaconda3/envs/tdmpc/lib/python3.8/site-packages/dm_control/suite/acrobot.py", line 20, in
from dm_control import mujoco
File "/home/wjg/anaconda3/envs/tdmpc/lib/python3.8/site-packages/dm_control/mujoco/init.py", line 18, in
from dm_control.mujoco.engine import action_spec
File "/home/wjg/anaconda3/envs/tdmpc/lib/python3.8/site-packages/dm_control/mujoco/engine.py", line 41, in
from dm_control import _render
File "/home/wjg/anaconda3/envs/tdmpc/lib/python3.8/site-packages/dm_control/_render/init.py", line 67, in
Renderer = import_func()  # pylint: disable=invalid-name
File "/home/wjg/anaconda3/envs/tdmpc/lib/python3.8/site-packages/dm_control/_render/init.py", line 36, in _import_egl
from dm_control._render.pyopengl.egl_renderer import EGLContext
File "/home/wjg/anaconda3/envs/tdmpc/lib/python3.8/site-packages/dm_control/_render/pyopengl/egl_renderer.py", line 75, in
raise ImportError('Cannot initialize a headless EGL display.')
ImportError: Cannot initialize a headless EGL display.
Is this due to the system?

I got it!

I can set the os.environ['MUJOCO_GL'] = 'glfw' ,but it's so slowly.
Did there have other method to acclerate ?

Can you tell us what GPU is present on your system?

Hi @945716994, thanks for reaching out!

NVIDIA A100

Is it a server or workstation grade A100?
Also, is it in Multi-Instance GPU (MIG) mode?

Hi @945716994, thanks for reaching out!

NVIDIA A100

Is it a server or workstation grade A100? Also, is it in Multi-Instance GPU (MIG) mode?

Hi @claudiofantacci ,is a server and not in MIG,we have four A100 on server.

Hi, @945716994 I also encountered this problem in ubuntu, how did you solve it later, can you tell me, thank you for your early reply.

I have the same problem, I was using my school's service featured with A100. And I found I cannot install the package egl and osmesa needed below.
sudo apt-get install libnvidia-gl-440-server

Because it's an LFS system, I cannot install any packages outside the module loading system.
Do you know how I can tackle this problem? I really appreciate any help you can provide.


Material TextField mask behavior

Currently we cannot apply the MaskedBehavior to the TextField component. Are there any plans to create similar functionality in the future?

up


Create an optimisation module

This would house the get_optimiser, apply_updates, (possibly) get_args. get_param_spec can probably be deprecated too.

Also a good chance to work on #5

Could also be used to automate the optax optim.update stuff

Implemented in 0.3.0


Core Views in NFTView

This is a spin-off ticket originating from #74. Please review its comment history for deeper context about what this ticket is for
A central theme of discussion many of us have brought up is what views should be "required" to be implemented in order to say that a collection has implemented Flow's metadata standard. While individual collections can define their own views, a central set of what some of us have called "core" views
What are core views for?
 That is.. marketplaces, wallets, and applications should be able to use the NFTView as a central source to obtain information about an item both to transact with and to display.
Current Proposed Core Views

Display - "How do I show this NFT?"
ExternalURL - "Where did this NFT come from/how do I make backlinks to this NFT's project?"
Medias - "What is the full image/animation of this NFT? Are there multiple ways to show it?"
Traits (In PR at #97) - "What data exists on this NFT? What is its Body, Head, Background, Hometown, etc? How do I show this data?"

Possible missing pieces

NftCollectionData - "How should I store this NFT?"
TokenURI - Some collections like TopShot have data that exists off-chain. Ideally we can mark how to obtain that extra data or at least note that what an application has could be incomplete

I'm not sure about NftCollectionData, I've flip-flopped on it a few times. TokenURI I think has its place given that some prominent projects are already split, so we know that we will need to handle that.
If anything else is missing, please chime in! The ideal is that we settle on these core views and then we can create a factory method or some kind of helper on the MetadataStandards contract that builds this for you. Then, a collection can just delegate to the factory for building the NftView and it can be practically for free for collection owners to include.

cc @psiemens @bjartek @bluesign

NFTCollectionView and Editions?

NFTCollectionView and Editions?

Editions I'm unsure of. Does it belong on the top-level? Or should we instead encourage collection owners to make that into a trait?

Just a few ideas.  It would be nice if the json in TokenURI follows the same schema used in the views. Then you can use them interchangeably or merge them in case of split data projects.
A timestamp could be useful too, so you can check which metadata set is newer (on-chain vs TokenURI).

A timestamp could be useful too, so you can check which metadata set is newer (on-chain vs TokenURI).

This sounds like a trait to me, by the way

@spacepluk I'd like to keep this discussion focused on views as opposed to things that up-end the entire standard.  If you'd like, please reach out to me in twitter or discord and let's figure it out there? Happy to discuss and then summarize here instead of lots of back and forth on this ticket. I don't want folks shut out from anything, but at the same time a TokenURI taking the entire view's format would split the standard in two. In my opinion, that isn't what this meant to be, but I'm happy to discuss in-depth as needed to get a better idea

I would suggest
Collection Data Collection Display Royalties

Royalties makes sense!
I think the others do as well, but I feel a little weirder about it for some reason. Wouldn't I already know Collection Data/Display by nature of having the item itself? Does it make more sense for some kind of roll-up Collection view just like we are proposing an NftView?

The use case that comes to mind is a central registry. What if you want to setup a collection for someone but don't have an actual NFT yet?

Sync'd with @bshahid331 yesterday about the CollectionDisplay need, it looks like we will need that view specifically because of some collections putting all their NFTs into one place while representing them as different collection on their sites. Because of that possibility, an NFT needs to be able to tell you the collection (NOTE: not resource collection) that it belongs to. As in, is this a BALLERZ or a SNEAKERZ nft? How do I show each one?
I am good with adding it, we have a need and there isn't really another option given the tools we have at our disposal right now

@joshuahannan this one as well should be good


Use axios in place of vue-resource

Since vue-resource is retiring (https://medium.com/the-vue-point/retiring-vue-resource-871a82880af4#.lu29ki141), thought this might be a logical next step to get this template up to par.
I've forked the repo and will submit this back as a PR if you're good with that.
I'll even set Vue.prototype.$http = axios to minimize disruption.

Thanks again!

Sure thing! I guess this might also close #5 as well since the WebAPI sample is now working.


Cannot access gated repo for url https://huggingface.co/api/models/meta-llama/Llama-2-7b-chat-hf. Repo model meta-llama/Llama-2-7b-chat-hf is gated. You must be authenticated to access it.

System Info
Using a private or gated model
You have the option to utilize the HUGGING_FACE_HUB_TOKEN environment variable for configuring the token employed by text-generation-inference. This allows you to gain access to protected resources.
For example, if you want to serve the gated Llama V2 model variants:
Go to https://huggingface.co/settings/tokens
Copy your cli READ token
Export HUGGING_FACE_HUB_TOKEN=
or with Docker:
model=meta-llama/Llama-2-7b-chat-hf
volume=$PWD/data # share a volume with the Docker container to avoid downloading weights every run
token=
docker run --gpus all --shm-size 1g -e HUGGING_FACE_HUB_TOKEN=$token -p 8080:80 -v $volume:/data ghcr.io/huggingface/text-generation-inference:1.0.0 --model-id $model
Information

[X] Docker
[X] The CLI directly

Tasks

[X] An officially supported command
[ ] My own modifications

Reproduction
Using a private or gated model
You have the option to utilize the HUGGING_FACE_HUB_TOKEN environment variable for configuring the token employed by text-generation-inference. This allows you to gain access to protected resources.
For example, if you want to serve the gated Llama V2 model variants:
Go to https://huggingface.co/settings/tokens
Copy your cli READ token
Export HUGGING_FACE_HUB_TOKEN=
or with Docker:
model=meta-llama/Llama-2-7b-chat-hf
volume=$PWD/data # share a volume with the Docker container to avoid downloading weights every run
token=
docker run --gpus all --shm-size 1g -e HUGGING_FACE_HUB_TOKEN=$token -p 8080:80 -v $volume:/data ghcr.io/huggingface/text-generation-inference:1.0.0 --model-id $model
Expected behavior
The docker image should be modified to use either cli auth or to work with the api key

It seems, you are exporting env variable with name HUGGING_FACE_HUB_TOKEN and using token in docker run cmd.
Try running these commands,
model=meta-llama/Llama-2-7b-chat-hf
volume=$PWD/data # share a volume with the Docker container to avoid downloading weights every run
token="<your-hf-read-token>"

docker run --gpus all --shm-size 1g -e HUGGING_FACE_HUB_TOKEN=$token -p 8080:80 -v $volume:/data ghcr.io/huggingface/text-generation-inference:1.0.0 --model-id $model

The docker image should be modified to use either cli auth or to work with the api key

That means that you need to mount a specific location containing the token file.
In production settings, using an env variable being mounted from secrets should be the preferred solution IMHO.
In any case we're not going to change the behavior of the docker (the raw cli will read the token properly since it has access to all the disk)

Excuse me, I have a question, when i Filled out the form at the end of the "Expand to review and Access" section and then i was rejected, and I didn't find out how to apply again


QX-3771 fix regression of QX-3770 print resolution

During the merge of v3.1.81 our print resolution fix was conflicted and I forgot to go back and re-add it. Here we're adding it back in.

wrong target branch.


Chat bubbles not over head

Chat bubbles not appearing over the speakers head. Makes it hard to see who is talking. Play on 2560x1440.

I know you marked this as fixed, but I cannot see chat bubbles over NPCs speaking in a cutscene... for instance the quest in Silverpine where you have to hide in a closet to listen to a worgen conversation. I can't see any of what they are saying.


Random Battle: Update Cradily, Cacturne

Reject Seed Bomb with Giga Drain.
Switch Cacturne's Doubles set to fully Physical.

Change it to hasMove['gigadrain'] && setupType !== 'Physical'.

Ahhh yes, I forgot Cradily has Curse


Improvement: please increase font size to Body input (Editor view = text input)

Please increase font size to Body input (Editor view = text input)
Versions
App: 10.0.3
Platform: 5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36
Steps to reproduce

Open ARC
Switch to 'Body' tab
Change Editor view to 'Test input'
Type anything to the input
Observed: Input font is too small, uncomfortable to read - See the screenshot
Expected: (?) The font is bigger

Hi,
Thank you for issue report. Sorry about that. This is obvious bug with styling. I'm on it.


Tree Implementation

It will help beginner to clear their concept of trees, I have made this codes more readiable and concise.

do let me know please about it.


Support for running nixos tests in containers, instead of VM

Running tests in containers would be much faster than running in VMs. This is not for everything, but should work just fine for most of the services. systemd-nspawn could be used for containers. If this would be supported i would be more eager to write tests.

Can this be closed since it is very similar to #5241?

Yes.


Menu doesnt show

On the newest update, whenever i click on a tower the menu doesnt show up anymore! It was working for me before and works whenever I use the older versions but I want to use the never version for the button that allows me to change from custom to original ui.

send log, go to one of the modding discords if you dont know what that is

Same

i think log:


"Fatal error on SSL transport" when exiting python script

Package Name: azure-eventhub-checkpointstoreblob-aio
Package Version: 1.1.4
Operating System: MacOs 10.15.7
Python Version: 3.9.1

Describe the bug
Error is occurring after exiting python program :

Fatal error on SSL transport
protocol: <asyncio.sslproto.SSLProtocol object at 0x7faedb601f70>
transport: <_SelectorSocketTransport closing fd=22>
Traceback (most recent call last):
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/asyncio/selector_events.py", line 918, in write
n = self._sock.send(data)
OSError: [Errno 9] Bad file descriptor

To Reproduce
Steps to reproduce the behavior:
Minimal repro :
import asyncio
import time
import atexit

from azure.eventhub.aio import EventHubConsumerClient
from azure.eventhub.extensions.checkpointstoreblobaio import BlobCheckpointStore

def end_process():
    time.sleep(4)

atexit.register(end_process)

# note : fill in blob_account_url, container_name, credential here
checkpoint_store = BlobCheckpointStore(
        blob_account_url="",
        container_name="",
        credential="")

# note : fill in endpoint
client = EventHubConsumerClient.from_connection_string("Endpoint=", consumer_group="$Default", checkpoint_store=checkpoint_store)

async def on_event_batch(partition_context, reports):
    print("processing events")
    await partition_context.update_checkpoint()

async def main():
    task = asyncio.ensure_future(
        client.receive_batch(
            on_event_batch=on_event_batch,
            starting_position=-1,
            max_wait_time=60,
            max_batch_size=200
        )
    )

    while(True):
        await asyncio.sleep(30)
        task.cancel()
        break;

async def close():
    await client.close()
    await checkpoint_store.close()

if __name__ == '__main__':
    try:
        asyncio.run(main())
        asyncio.run(close())

    except Exception as e:
        atexit._run_exitfuncs()
        raise(e)

    atexit._run_exitfuncs()

Expected behavior
Error should not occur
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

Thanks for the feedback, we’ll investigate asap.

hey @rjohnsonrxr, I am able to reproduce the issue on windows which gave me more information on the error:
Fatal error on SSL transport
protocol: <asyncio.sslproto.SSLProtocol object at 0x00000170FC06A608>
transport: <_SelectorSocketTransport closing fd=440>
Traceback (most recent call last):
  File "..\envs\env37\lib\asyncio\selector_events.py", line 870, in write
    n = self._sock.send(data)
OSError: [WinError 10038] An operation was attempted on something that is not a socket

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "..\envs\env37\lib\asyncio\sslproto.py", line 680, in _process_write_backlog
    self._transport.write(chunk)
  File "..\envs\env37\lib\asyncio\selector_events.py", line 874, in write
    self._fatal_error(exc, 'Fatal write error on socket transport')
  File "..\envs\env37\lib\asyncio\selector_events.py", line 683, in _fatal_error
    self._force_close(exc)
  File "..\envs\env37\lib\asyncio\selector_events.py", line 695, in _force_close
    self._loop.call_soon(self._call_connection_lost, exc)
  File "..\envs\env37\lib\asyncio\base_events.py", line 691, in call_soon
    self._check_closed()
  File "..\envs\env37\lib\asyncio\base_events.py", line 479, in _check_closed
    raise RuntimeError('Event loop is closed')
RuntimeError: Event loop is closed

Process finished with exit code 0

according to the doc of asyncio.run:

This function always creates a new event loop and closes it at the end. It should be used as a main entry point for asyncio programs, and should ideally only be called once.

So I think it's because the underlying ssl obj is hooked with one asyncio loop in the first asyncio.run, and the loop get closed after the running which leads to the second call find that the previous loop hooked with the ssl obj is already closed.
To bypass it, you could use the same loop to run those two method, so your code could be like:
if __name__ == '__main__':
    try:
        loop = asyncio.get_event_loop()
        loop.run_until_complete(main())  # same loop
        loop.run_until_complete(close())  # same loop
    except Exception as e:
        atexit._run_exitfuncs()
        raise(e)

    atexit._run_exitfuncs()

Please let me whether it works for you or you need any other help.


Should continue after an import problem ?

Trying to import with attachments but it dies at this point:
fetching attachment from Trello API, path =  https://api.trello.com/1/cards/{redacted}/attachments/{redacted}/download/
status =  404
authenticated POST with file upload to https://{redacted}/api/cards/{redacted}/attachments
Error: authenticated POST failed, status code = 422, code = E_UNPROCESSABLE_ENTITY, problems = undefined
at authenticatedPostFileUpload (file:///home/ubuntu/trello2planka/src/planka/client.js:89:15)
It seems that it could catch errors like that and just ignore those attachments and keep going.  I find it odd that the initial line for the download has no filename after it, it seems in the log the other ones do have one and maybe that is part of the problem?

Hi, yes this seems something like #27 .
Good point, the whole tool lacks error recovery completely: In the importer there are lots of dependent calls to planka (like cards inside a list inside a board, etc.) where just ignoring an error didn't make a lot of sense to me, because most of the following calls would just fail anyway too. And then maybe the calls of the next undependent item wouldn't, and it would end up in a mess. (But granted, it also does if it panics right away.)
As for trello-fetched items, this might make less sense, I see the point.
However I won't be able to refactor anything in this tool any time soon. Of course for your case as a quickfix, if you don't care about these kind of attachments, you can wrap the call in a try/catch, which you probably already did anyway.


Analyzer suggestions too locked in with parser recoveries "type selection"

In pkg/analysis_server/test/services/completion/dart/extension_member_contributor_test.dart there's a test - test_identifier_matches - like this:
extension E<T extends num> on List<T> {
  bool a(int b, int c) {}
  int get b => 0;
  set c(int d) {}
}
void f(List<int> l) {
  l.a^
}

Currently the l.a parses like a method and one gets the suggestions the test expect (a, b, c).
If I create a new test looking like this instead, though:

  @soloTest
  Future<void> test_identifier_matches2() async {
    addTestSource('''
extension E<T extends num> on List<T> {
  bool a(int b, int c) {}
  int get b => 0;
  set c(int d) {}
}
void f(List<int> l) {
  l.a^
  print(l.b);
}
''');
    await computeSuggestions();
    throw suggestions.map((e) => e.completion).toList();
    assertSuggestMethod('a', null, 'bool', defaultArgListString: 'b, c');
    assertSuggestGetter('b', 'int');
    assertSuggestSetter('c');
  }

The l.a part parses as a field (because the parser sees l.a print) and one gets no suggestions (and the test would fail even if it didn't throw to easily see the suggestions).
Equivalently, if the recovery in the parser was to change on the first example (which I have a CL that does) we get into the same situation as in example 2, i.e. no suggestions.
Could we make the analyzer less dependent on which bucket the parser puts stuff in, when we're in a recovery scenario?
/cc @bwilkerson

I don't think that's possible. The reason I say that is the following. The parser, together with the AstBuilder, has to make some guess as to the structure of the code, and that structure is encoded in an AST. The code completion engine uses the produced AST structure to guess at what the user intends to type next and to suggest those guesses to the user. The tests are highly dependent on the AST structure because the completion engine is highly dependent on that structure. I don't know of any way to decouple the completion engine from the AST structure, so I don't think we can decouple the tests.
That said, the purpose of the tests is to ensure that code completion suggestions are what we expect them to be when the analyzer is given a plausible piece of source code. A couple of things fall out of that.
First, if there is a test case where completion isn't producing the correct suggestions (as the one you included above), then we should capture that in a test case and fix the completion engine so that it works.
Second, if the parser needs to change the way it's recovering in order to do a better job, and if doing so causes a test to start failing, then we should do one of two thing. Either (a) we find a test case that will produce the same structure without those changes and proactively fix the completion engine so that when the changes are applied completion isn't regressed, or (b) we mark the test with @FailingTest and open an issue to update the completion engine to correctly handle the new structure. I'd prefer the first, but it takes longer and I recognize that it might not always be practical.

I get that this is not an easy ask :)
What I was thinking was that perhaps - when, lets say a statement - contains errors, the analyzer could try to amend that source-code in a few ways and re-run the parser, see if it got different results, and then possibly include that in suggestions.
In example 1 recovery becomes l.a; (currently) but could also be (with change (that I've now modified though)) l.a <synthetic identifier>;.
In example 2 recovery becomes l.a print; (and (l.b);).
In both cases the synthetic token(s) could indicate a position (or approximate position) where stuff could be different, so one could perhaps try making the parser look at

l.a;
l.a(
l.a <identifier>
l.a[
l.a =
l.a; print
l.a( print
...
(naturally the variations one could come up with here are endless, but maybe we could pick some good ones).

Alternatively --- and maybe that would be better --- the parser should have a mode to actively go down several paths. In this case choose both that something was a method call and that it was a variable declaration for instance...
All of this would naturally require that the analyzer could actually use this information --- actually have "alternative ASTs" in memory.

What I was thinking was that perhaps - when, lets say a statement - contains errors, the analyzer could try to amend that source-code in a few ways and re-run the parser, see if it got different results, and then possibly include that in suggestions.

That's definitely an interesting idea. Performance is the biggest obstacle I can think of. I'm not sure we could do that within the 100 ms window we have for code completion (and we actually need to be much lower because of the time it takes to serialize and deserialize the suggestions as we send them to the client).

In example 1 recovery becomes l.a; (currently) but could also be (with change (that I've now modified though)) l.a <synthetic identifier>;.

The current recovery seems better to me. I think that the principle we want to follow is to add (or remove) the smallest number of tokens necessary in order to produce valid code (except in cases where it would be "obvious" to a human reader that something else is more appropriate. The code l.a; is valid and only requires adding one token, so it seems like the better way to recover. The second case isn't valid Dart, so I don't even know how we'd represent that in the AST.

In example 2 recovery becomes l.a print; (and (l.b);).

In the second case I'd much rather recover by adding a semicolon just like in the first case:
void f(List<int> l) {
  l.a;
  print(l.b);
}

Again, it's a single token change, which is ideal for recovery.

Alternatively --- and maybe that would be better --- the parser should have a mode to actively go down several paths. In this case choose both that something was a method call and that it was a variable declaration for instance...

That's also an interesting idea, but I'm again concerned by the performance implications. I think that doing that would effectively require the analyzer to analyze all of the alternate paths. It might be interesting to do some thought experiments, but I'm also wondering what impact that would have on the UX. Would we report all the diagnostics along all the possible permutations, or would we choose the "best" option (for some definition of "best") and report only that one. Would that produce predictable behavior, or would the analyzer appear to vacillate after each character that a user typed?
However, all that aside, I think the better short term solution is to allow the parser to look farther ahead in order to determine the best recovery. In the second example, that might look like assuming that there was a semicolon after l.a and seeing whether the following tokens look like a statement. If they do, then insert the semicolon. If not, then try the next most likely option.

What I was thinking was that perhaps - when, lets say a statement - contains errors, the analyzer could try to amend that source-code in a few ways and re-run the parser, see if it got different results, and then possibly include that in suggestions.

That's definitely an interesting idea. Performance is the biggest obstacle I can think of. I'm not sure we could do that within the 100 ms window we have for code completion (and we actually need to be much lower because of the time it takes to serialize and deserialize the suggestions as we send them to the client).

Right. One option could be to say that as long as there are a low number of errors (say the general case being that the program is correct, the user starts typing and the program temporarily - in the one statement - becomes incorrect, but the rest of the program stays correct) this could be the standard modus operandi, i.e. it's calculated before asking for completion. Then when the user asks for completion the data is already there. Sure, the Analyzer has to look through more data, but would that be too much data you think?

In example 1 recovery becomes l.a; (currently) but could also be (with change (that I've now modified though)) l.a <synthetic identifier>;.

The current recovery seems better to me. I think that the principle we want to follow is to add (or remove) the smallest number of tokens necessary in order to produce valid code (except in cases where it would be "obvious" to a human reader that something else is more appropriate. The code l.a; is valid and only requires adding one token, so it seems like the better way to recover. The second case isn't valid Dart, so I don't even know how we'd represent that in the AST.

While it's probably a fine rule-of-thumb to add the smallest number of tokens (e.g. when we are to judge a recovery) it's not vary usable when actually doing recovery. Without trying out lots of different options we don't know which will produce the smallest amount --- and quite possibly we need to do that before even knowing we're doing recovery which would be quite bad. (I see the double standard as that's the same argument you made for not doing variations in the analyzer which I tried argue above that we should basically just ignore).
Also, the second case is syntactically perfectly valid dart up to the point of recovery: l.a print is a variable called print of type a from an import prefixed with l.
Another - quite frankly good recovery - could have been something like l.a print(l.b <synthetic identifier>) {} -- that would have accepted as much as possible before starting to do recovery... (a good example, btw, how we're making a sort of recovery decision when we're still not doing recovery).

In example 2 recovery becomes l.a print; (and (l.b);).

In the second case I'd much rather recover by adding a semicolon just like in the first case:
void f(List<int> l) {
  l.a;
  print(l.b);
}

Again, it's a single token change, which is ideal for recovery.

Alternatively --- and maybe that would be better --- the parser should have a mode to actively go down several paths. In this case choose both that something was a method call and that it was a variable declaration for instance...

That's also an interesting idea, but I'm again concerned by the performance implications. I think that doing that would effectively require the analyzer to analyze all of the alternate paths. It might be interesting to do some thought experiments, but I'm also wondering what impact that would have on the UX. Would we report all the diagnostics along all the possible permutations, or would we choose the "best" option (for some definition of "best") and report only that one. Would that produce predictable behavior, or would the analyzer appear to vacillate after each character that a user typed?

To me this is just a variation of the analyzer creating the variations itself (i.e. the first suggested thing) --- and it doesn't have to be used for diagnostics. It could be used for suggestions only.
Again I wouldn't want it to do this on all paths --- just on the path with errors in it. And again probably only when there's a small number of errors.

However, all that aside, I think the better short term solution is to allow the parser to look farther ahead in order to determine the best recovery. In the second example, that might look like assuming that there was a semicolon after l.a and seeing whether the following tokens look like a statement. If they do, then insert the semicolon. If not, then try the next most likely option.

As I've indicated above I don't think that's plausible. We're basically making a decision while still on the "happy path". For valid code the decision would be correct and we don't yet know that we're not.

I'll start by pointing out that we've gotten a little off topic. This started with a request for the tests to not be as dependent on the produced AST, and has morphed into a discussion of how to perform recovery. I'm not opposed to discussing how to best recover from errors, but I think my original response (that completion is inherently dependent on the way recovery works) is still valid no matter how we recover.

... it's calculated before asking for completion. Then when the user asks for completion the data is already there.

Generally speaking that won't happen. My understanding is that most of the time completion is requested implicitly by typing some triggering character such as a period. Server is first told that the period was typed and that's followed almost immediately by a completion request. We basically have to include the time to re-analyze the code in the time it takes to respond to a completion request.

Sure, the Analyzer has to look through more data, but would that be too much data you think?

That depends, in part, on how much more data there is to look at. But if we assume that we can generally produce completion results in 30 ms when looking at a single AST, it would presumably take 3 times as long to look at 3 alternate ways of parsing the section in which completion is being requested. I think that would cause us to miss our 100 ms window too often.

While it's probably a fine rule-of-thumb to add the smallest number of tokens (e.g. when we are to judge a recovery) it's not vary usable when actually doing recovery. Without trying out lots of different options we don't know which will produce the smallest amount --- and quite possibly we need to do that before even knowing we're doing recovery which would be quite bad.

We definitely don't want to do any extra work before we know that we need to recover from an error. I think we're both agreed on that point.
I also agree that we don't want to try lots of different options in order to produce the absolute minimal number of token changes from the original source. I would instead suggest that we want the recovery code to greedily (as in no backtracking) use heuristics to choose how to recover in each situation, and that the choice of heuristics should be guided by several principles, one of which is to add or remove the smallest number of tokens necessary to produce valid code. Another principle would be to recover as often as possible in the way a human reader would.

Also, the second case is syntactically perfectly valid dart up to the point of recovery: l.a print is a variable called print of type a from an import prefixed with l.

You're right. I was looking at the code from the point of view of a human reader rather than from the parser's point of view. Both are important; the parser can't start doing recovery until it knows without doubt that there's a problem, which unfortunately in this case is well past the point where recovery would ideally be done.

Another - quite frankly good recovery - could have been something like l.a print(l.b <synthetic identifier>) {} -- that would have accepted as much as possible before starting to do recovery... (a good example, btw, how we're making a sort of recovery decision when we're still not doing recovery).

Actually, I think we start recovery the moment we get past l.a print(l.b. At that point we know that the right paren isn't valid and we have to decide what to do.
If I had my preference we'd have a parser that could look both backward and forward and see that the problem was the missing semicolon after l.a, but it can't actually do that at the moment and I'm not proposing that we should make that change (now or probably ever).
Given that the parser can't un-parse any of the input and that it's already committed to parsing this as a local function declaration, I think that adding the synthetic identifier is probably the best solution. I would, however, suggest one minor change: parse it as l.a print(l.b <synthetic identifier>);. Even though it isn't valid for a local function declaration to have an empty body, it more closely matches the input.


Updated 1st para as ext user in cpp-extensions.md

Hi Code RealTime team,
can you please review these changes?

Closing the PR


Crash on newly cloned git version of Godot

To test out Godot for the first time, I created a new project, placed some 2D nodes, and wrote a player script.
Having one Node2D, with a player script and the default texture for the sprite worked fine, I could run around.
When I set the scene up so that there was a root node, with two child nodes, one being the previous player and the new one being a copy, without the player script (I did this to test raycasting), it crashes every time.
I'm on Ubuntu 15 64bit
This is my script
extends Node2D

var velocity
var acceleration
var top_speed
var mass
var g_acc
var friction_co

func _ready():
    set_process(true)
    velocity = Vector2(0,0)
    acceleration = 1000
    top_speed = 560
    mass = 80
    g_acc = 9.82
func _process(dt):
    var horizontal = 0
    if (Input.is_action_pressed("move_right")):
        horizontal += 1
    if (Input.is_action_pressed("move_left")):
        horizontal -= 1
    if (horizontal == 0):
        friction_co = 1.2
    else:
        friction_co = 0.18
    var current_position = get_pos()
    var new_position = current_position
    var prev_velocity = velocity
    velocity.x += horizontal * acceleration * dt
    var vel_mag = velocity.length()
    if (vel_mag > top_speed):
        velocity = prev_velocity
    var direction = velocity.normalized()
    var surf_norm = Vector2(0, -1)
    var gravity_dir = Vector2(0, 1)
    var gravity = gravity_dir * mass * g_acc * dt
    var space_state = get_world_2d().get_direct_space_state()
    var ray_result = space_state.intersect_ray(current_position, new_position)
    if (not ray_result.empty()):
        velocity = Vector2(0,0)
    else:
        var friction = -direction * friction_co * gravity.y
        velocity += friction
        new_position += velocity * dt
        set_pos(new_position)

This was the terminal output
OPENING: /home/ian/workspace/godot_test (::home::ian::workspace::godot_test)
freed code id 1
ian@tux-station:~/source/godot/bin$ VBoxContainer: 136,100
ERROR: get_edited_scene_root: Index current_edited_scene out of size (edited_scene.size()).
   At: tools/editor/editor_data.cpp:598.
ERROR: get_edited_scene_root: Index current_edited_scene out of size (edited_scene.size()).
   At: tools/editor/editor_data.cpp:598.
ERROR: add_child: Can't add child, already has a parent
   At: scene/main/node.cpp:740.
ERROR: add_child: Can't add child, already has a parent
   At: scene/main/node.cpp:740.
bind toptions
ERROR: get_edited_scene_root: Index current_edited_scene out of size (edited_scene.size()).
   At: tools/editor/editor_data.cpp:598.
ERROR: grab_focus: Condition ' !is_inside_tree() ' is true.
   At: scene/gui/control.cpp:2218.
ERROR: grab_focus: Condition ' !is_inside_tree() ' is true.
   At: scene/gui/control.cpp:2218.
ERROR: set_current_tab: Index p_current out of size (get_tab_count()).
   At: scene/gui/tabs.cpp:625.
settings changed
ERROR IN: /icon.png
ERROR: _get_modified_time: Method/Function Failed, returning: 0
   At: drivers/unix/file_access_unix.cpp:236.
ERROR IN: /new_scene.scn
ERROR: _get_modified_time: Method/Function Failed, returning: 0
   At: drivers/unix/file_access_unix.cpp:236.
ERROR IN: /player_gd.res
ERROR: _get_modified_time: Method/Function Failed, returning: 0
   At: drivers/unix/file_access_unix.cpp:236.
ERROR IN: /player_script.res
ERROR: _get_modified_time: Method/Function Failed, returning: 0
   At: drivers/unix/file_access_unix.cpp:236.
ERROR: create: Condition ' Math::is_nan(p_aabb.size.x) ' is true. returned: 0
   At: core/math/octree.h:827.
ERROR: create: Condition ' Math::is_nan(p_aabb.size.x) ' is true. returned: 0
   At: core/math/octree.h:827.
ERROR: create: Condition ' Math::is_nan(p_aabb.size.x) ' is true. returned: 0
   At: core/math/octree.h:827.
ERROR: create: Condition ' Math::is_nan(p_aabb.size.x) ' is true. returned: 0
   At: core/math/octree.h:827.
ERROR: create: Condition ' Math::is_nan(p_aabb.size.x) ' is true. returned: 0
   At: core/math/octree.h:827.
ERROR: create: Condition ' Math::is_nan(p_aabb.size.x) ' is true. returned: 0
   At: core/math/octree.h:827.
freed code id 3
freed code id 5
freed code id 4
freed code id 6
freed code id 2
ERROR: set_stream_peer: Condition ' p_peer.is_null() ' is true.
   At: core/io/packet_peer.cpp:246.
freed code id 1

This is a very broad description and may be a lot of things. Could you try to narrow the bug and/or provide a sample project (as a zip file or as a GitHub repository)?

Please make an example project

@Smilex ping

Sorry. Forgot all about this.
I tried to recreate this, and I got it to happen the first time. But since it crashed, I wanted to do it a second time to save it, and that's when I noticed that I had loaded script from other files that were actually projects or something.
There was no crash when I didn't do that.

@Smilex so, this can be closed?

@techtonik I don't know. I don't know how you want Godot to work, all I can say is that I didn't like it working that way. I couldn't figure out which files to open, and Godot crashes if you do it incorrectly

if you can post a project that crashes We´ll be glad to take a look at it
and fix it
On Fri, Feb 26, 2016 at 10:19 AM, Ian T. Jacobsen<EMAIL_ADDRESS>wrote:

@techtonik https://github.com/techtonik I don't know. I don't know how
you want Godot to work, all I can say is that I didn't like it working that
way. I couldn't figure out which files to open, and Godot crashes if you do
it incorrectly
—
Reply to this email directly or view it on GitHub
https://github.com/godotengine/godot/issues/3103#issuecomment-189269288.

Just create two projects, and in one of the projects reference a project file as a script for any object, and run.

Could you be more specific? What is the second project used for? Do you create a scene in the first project, do you save it, what node do you use as root node, what node do you attach the script to, etc.?
The steps you gave are very broad and are what Godot users do all the time when using Godot, so if that was triggering reproducible crashes every time, we'd know about it and it would have been fixed by now :) So it's likely that you are doing something much more specific than what you just described.

But I can't give you the specific project, because it crashes without saving, so I have to set it up again everytime. And everytime It's the same thing. One root node (Node type), two child nodes (Node type), each with a sprite and collision box.
I try to add the above script as the script for one of them, but when I get the file browser window, it shows me scenes or projects or something, where I was expecting scripts. I pick one of them.
I run the thing, it crashes. I've tried this several times now. I can't do it again for sometime, because I've installed Windows and haven't fixed Grub yet

@Smilex the most obvious way is to not forget all steps being made in the specific order is to record a screencast with something like https://github.com/cessen/recordscreen

If there is no way to reliably reproduce this issue (doesn't matter the version), I think it should be closed.

@Smilex close it?


Updated update #7 firmware builds

@JohanFreelancer9 Copy editing is needed for this PR. Thanks.

@JohanFreelancer9 Copy editing is needed for this PR. Thanks.


Security error

I have a solution with 1 MDA, 13 cloud flows, and 77 tables amongst other items in the solution.  As I generate the documentation for the solution it fails with the error below.  It seems to generate the flows but as it documents the tables in dataverse it stops part way through.  Please let me know if you need more information

if this helps at all the last entity written to the word document is
Team(Team)
with a blank Primary Column and blank Description

Code fix has been added, will be included in the next release (sometime this month)

Just realised that this is still open. New release is out, and this has been fixed (details in https://github.com/modery/PowerDocu.Common/commit/7ce2075aa08b3ee986c878d22d233f88a5168714). Closing issue now


Simple Payload - Cross Platform

Testing Simple Payload across iOS and Android implementations to ensure both are identical.

Test completed - Ready for merge to develop


Introduce ZPM support

To ease installation and versions management

I was going to ask exactly the same thing but @evshvarov beat me :-)


Option "recovery mode" does not exist in the schema  for onedrive backup

Hi,
I have been running Onedrive for a couple of weeks now, and I just noticed that my supervisor is showing below error message every couple minutes or so:
23-03-23 15:17:53 WARNING (MainThread) [supervisor.addons.options] Option 'recovery_mode' does not exist in the schema for OneDrive Backup (de91e161_hassio_onedrive_backup)

I am running the latest version of Onedrive Backup, in which the recovery mode has been removed. so I do understand the error message.
However is/can there something (be) done to fix this error from showing, either on my installation or by the next update?
(I notice glances is also showing an error...

Hi,
This is a side effect of the removal of the recovery_mode config option. Since you upgraded it keeps the old config.
You can just go to the addo nconfiguration , click the 3 dots at the top right and choose "edit yaml" and just remove the line from the config and you should be good to go with no more warnings.

I did suspect something like that, just didn't know where to find it.
Thanks for pointing me where to fix it.


I am getting an empty panel when symbols are located

I've been using the symbol locator plugin for zeplin for some time, but since the last update of the software, the plugin is not displaying any results of symbols it may or may not have found, just an empty panel. I get a message when no symbol is found, but it seems it has stopped displaying the list of symbols located when it has located some.

I can also confirm I am having this issue :(

I too am having this issue at least since Sketch v96.1

Same is here on 98.3

Yup me too. Sketch Version 99.1 (178462)


#296 | @willwillman | debug currentPackagePath

Appears that the currentPackagePath and jestBinPath does not account for the possibility of certain mono-repos where sub packages share a node_modules directory in the root.
this PR allows the user to use a jestPathFromWorkspace setting to adjust where the runner looks for jest executable

Salutations
What's an example structure this is trying to fix?
You were discussing changeDirectoryToWorkspaceRoot as true in #296, maybe it's an idea to change how the debug behaves when this is set to true, rather than introducing a new configuration? Hard to say without a reproduction 👍


Remember scroll position so page doesn't jump after resizing textarea

$('textarea') was removed because we should autogrow heights of all textareas in the page.

I'd suggest to attach a screenshot or screen capture video for these types of UI changes to help reviewers get how they look afterward.

I'd suggest to attach a screenshot or screen capture video for these types of UI changes to help reviewers get how they look afterward.

I usually would, but this is fixing a bug that otherwise causes page scrolls to top. Also added bug description in the top comment.

Thanks for uploading the videos, I can visualize the change now. How do you think if we make the textarea is scrollable with a fixed threshold size (like this comment box) instead of keep increasing its size per its content? It might simplify the way we handle the textarea. Your call to choose which one to go.

This seems to be a low use area. Also I think showing everything is helpful to our users so they don't have to scroll up or down.


[WIP] docker/install: Support rootless

Add support for running a rootless daemon. Currently only Linux host is supported.

https://github.com/docker/actions-toolkit/actions/runs/11687682100/job/32546382492?pr=485#step:10:198
  + echo rootlesskit needs to be installed
  rootlesskit needs to be installed
  + exit 1

Missing rootlesskit?

It lost the PATH when sudoing as a non-root user.

Might need sudo -E

Ready for review @crazy-max


Page flipping feature

Previously discussed on #71 and #83 but they're wrong place to discuss about the feature.

Mmm, I'm checking the code of the page_flip plugin and found the code:
https://github.com/shivbo96/page_flip/blob/ff82dd1d3bf6693daa193447c1832d4e42c2f16e/lib/src/builders/builder.dart#L36-L47
  void _captureImage(Duration timeStamp, int index) async {
    if (_boundaryKey.currentContext == null) return;
    await Future.delayed(const Duration(milliseconds: 100));
    if (mounted) {
      final boundary = _boundaryKey.currentContext!.findRenderObject()!
          as RenderRepaintBoundary;
      final image = await boundary.toImage();
      setState(() {
        imageData[index] = image.clone();
      });
    }
  }

https://github.com/shivbo96/page_flip/blob/ff82dd1d3bf6693daa193447c1832d4e42c2f16e/lib/src/builders/builder.dart#L65-L69
        if (value == widget.pageIndex || (value == (widget.pageIndex + 1))) {
            WidgetsBinding.instance.addPostFrameCallback(
              (timeStamp) => _captureImage(timeStamp, currentPageIndex.value),
            );
          }

Basically, the plugin's behavior is unpredictable. It assumes certain delay on capturing page image.
And, further more, on the top of the code, there are several undesired global variables:
https://github.com/shivbo96/page_flip/blob/ff82dd1d3bf6693daa193447c1832d4e42c2f16e/lib/src/builders/builder.dart#L8-L11
Map<int, ui.Image?> imageData = {};
ValueNotifier<int> currentPage = ValueNotifier(-1);
ValueNotifier<Widget> currentWidget = ValueNotifier(Container());
ValueNotifier<int> currentPageIndex = ValueNotifier(0);

I think the code quality of the plugin is terrible. I think you should not use it.

Anyway, PdfViewer widget won't support page flipping. It is not designed to do so and also technically impossible.
So the possible solution is to use PdfPageView with some page flipping technology... But page_flip is not good. It is completely broken and it could not be work with PdfPageView (it's not the fault of PdfPageView).

Anyway, PdfViewer widget won't support page flipping. It is not designed to do so and also technically impossible.
So the possible solution is to use PdfPageView with some page flipping technology... But page_flip is not good. It is completely broken and it could not be work with PdfPageView (it's not the fault of PdfPageView).

Thank you for your response and guidance. I've noticed the same issue with the plug-in as when I used it with pdf_render: the quality of the PDF becomes very low to the extent that the content becomes unreadable. Additionally, there's no zoom functionality, and even if you implement it, the usability is not as good as what I've experienced with PdfViewer in pdfrx. Such a use case is what my readers will enjoy.
If you can by any chance suggest any plug-in for a quick win which will produce good effects like the desired flip, it would be very helpful while we wait for a native solution for pdfrx.
Thank you.

Hello @espresso3389, could you kindly take a look at this: https://github.com/jmolins/flutboard. What they've done is quite similar to what we want, except the flipping mechanism is vertical. However, that is an easy task to implement.
Upon inspecting the actual code, which handles the flipping, I noticed its not redrawing the pages as images on the screen, so I'm certain the quality can be retained. Now, the problem lies in being able to integrate it with pdfrx and enable pinch-to-zoom seamlessly, similar to what PdfViewer does.

@reddeath1
Frankly speaking, I don't plan to implement such (actually I don't know what) feature. It is partially because I don't understand your goal. I never think page-flipping and zooming are getting along well. Do you have any realistic sketch?

Mmm, I'm just a OSS plugin developer and don't want to evaluate any such app. Futhermore, don't show your private info. on GitHub. It's public. If you show me something, please record the screen and share it here.

Mmm, I'm just a OSS plugin developer and don't want to evaluate any such app. Futhermore, don't show your private info. on GitHub. It's public. If you show me something, please record the screen and share it here.

Sorry... here the gif.

Hi @espresso3389 I m back to this feature, do you think now it's time to kinder try and add this feature to this great plugin.?
Thank you again.


[BUG] Plugin build with OpenSearch 2.1.0 fails at random with: Could not GET 'https://d1nvenhzbhpy0q.cloudfront.net/snapshots/lucene/org/apache/lucene/lucene-queries/9.2.0-snapshot-ba8c3a8/lucene-queries-9.2.0-snapshot-ba8c3a8.jar'.             > peer not authenticated

Describe the bug
Local builds of k-NN plugin fail at random after switching to core OpenSearch 2.1.0 in scope of this PR https://github.com/opensearch-project/k-NN/pull/411. Part of the change was adding gradle plugin 'opensearch.repositories' as part of main k-NN gradle build script.
Exception
> Could not resolve all files for configuration ':compileClasspath'.
   > Could not download lucene-analysis-common-9.2.0-snapshot-ba8c3a8.jar (org.apache.lucene:lucene-analysis-common:9.2.0-snapshot-ba8c3a8)
      > Could not get resource 'https://d1nvenhzbhpy0q.cloudfront.net/snapshots/lucene/org/apache/lucene/lucene-analysis-common/9.2.0-snapshot-ba8c3a8/lucene-analysis-common-9.2.0-snapshot-ba8c3a8.jar'.
         > Could not GET 'https://d1nvenhzbhpy0q.cloudfront.net/snapshots/lucene/org/apache/lucene/lucene-analysis-common/9.2.0-snapshot-ba8c3a8/lucene-analysis-common-9.2.0-snapshot-ba8c3a8.jar'.
            > peer not authenticated
   > Could not download lucene-queries-9.2.0-snapshot-ba8c3a8.jar (org.apache.lucene:lucene-queries:9.2.0-snapshot-ba8c3a8)
      > Could not get resource 'https://d1nvenhzbhpy0q.cloudfront.net/snapshots/lucene/org/apache/lucene/lucene-queries/9.2.0-snapshot-ba8c3a8/lucene-queries-9.2.0-snapshot-ba8c3a8.jar'.
         > Could not GET 'https://d1nvenhzbhpy0q.cloudfront.net/snapshots/lucene/org/apache/lucene/lucene-queries/9.2.0-snapshot-ba8c3a8/lucene-queries-9.2.0-snapshot-ba8c3a8.jar'.
            > peer not authenticated

To Reproduce

Get the latest k-NN main from https://github.com/opensearch-project/k-NN.git
Run any complex build task like ./gradlew integTests. At random (about 75% for me) you'll get exception mentioned above. After running exact same task again it works fine and build passes.

Additional context
Running local build from corporate laptop after joining corp network with VPN. Haven't seen such behavior with OpenSearch 2.0.0

Ran into this issue as well. Was using JDK 11. Switched to JDK 17 and stopped seeing it.


NIFI-9434: Added bulletin to alert FileSystemRepository backpressure

Thank you for submitting a contribution to Apache NiFi.
Please provide a short description of the PR here:
Description of PR
https://issues.apache.org/jira/browse/NIFI-9434
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[x] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[x] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[x] Has your PR been rebased against the latest commit within the target branch (typically main)?

[x] Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not squash or use --force when pushing to allow for clean monitoring of changes.

For code changes:

[ ] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[ ] Have you written or updated unit tests to verify your changes?
[ ] Have you verified that the full build is successful on JDK 8?
[ ] Have you verified that the full build is successful on JDK 11?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check GitHub Actions CI for build issues and submit an update to your PR as soon as possible.

Thanks @Lehel44 this is a good improvement. Was able to verify behavior and all works well. +1 will merge to main!


Remove incubating from pom files

What is this PR for?
Remove incubating term from pom files
Questions:

Does the licenses files need update? No
Is there breaking changes for older versions? No
Does this needs documentation? No

LGTM 👍

LGTM

LGTM

LGTM

Just one curious question.
When is the incubator- been removed from the github mirror ? So we can have github.com/apache/zeppelin ?

LGTM

LGTM

Merging this if no more discussion.


1.21.4 neoforge?

any plans for update this wonderfull mod on 1.21.4 neoforge?

Version updates will come, I do not track them with issues


Support incremental builds

Currently gym builds an archive. Building archives is not incremental (it basically doesn't care about the derivedData). Building and uploading feature builds while developing locally can take quite some time. The whole app is built from ground up as it seems to me.
Would it be possible to support incremental builds?

In gym what's the point of the clean option when building to archives which isn't incremental anyways? :)

Hi @hfossli this isn't a currently supported use case. We will track it as a feature request. Thanks!

Perfect!


test: improve performance of createFullTransform util

Introduce a virtual filesystem to createFullTransform util
Mock pkg.name during transformation
Avoid compilation of on-disk project as much as possible

hey so i pulled down your branch to have a look - honestly everything looks great! if we can just rename some variables so its more obvious we aren't using fs would be fantastic.
other than that would be awesome to see how we can use the real source for the project instead of hardcoding a mock - but we can probably figure that out later than now.
if you want to update variables lmk - else i'm happy to merge this and make changes later :)

hey so i pulled down your branch to have a look - honestly everything looks great! if we can just rename some variables so its more obvious we aren't using fs would be fantastic.

Glad you like it

other than that would be awesome to see how we can use the real source for the project instead of hardcoding a mock - but we can probably figure that out later than now.

There is tradeoff between faithfulness and performance here - maybe we can have specific (slow) tests that do that?

if you want to update variables lmk - else i'm happy to merge this and make changes later :)

Will rename the variables.

hey what's your twitter? let's stay connected on there :) would love to talk to you about how i can do things better with ts transformers etc too.

hey what's your twitter? let's stay connected on there :) would love to talk to you about how i can do things better with ts transformers etc too.

Unfortunately I deleted my twitter handle 1-2 years ago - but you can find me e.g. on node-tooling.slack.com.

hmm actions aren't running for your branch 🤔


GSD Request

--- GSD JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from  to before v4.9.300",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=7889b38a7f21ed19314f83194622b195d328465c"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "7889b38a7f21ed19314f83194622b195d328465c",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "Bluetooth: refactor malicious adv data check\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v4.9.300 by commit 7889b38a7f21ed19314f83194622b195d328465c. For more details please see the references link."
}
--- GSD JSON ---

This issue has been assigned GSD-2022-1000078


Readme update for virtualenv

I used virtuelenv to install all required python-dependencies for HoloClean. There was no documentation for this procedure in the README. Installation with virtualenv was successful, so I want to add it to the README file.
Benefit
Setup with virtualenv is documented.
Cost
Low - couple of minutes

Done with PR #246


Connectivity for Ardell path 12 is missing from production SCKAN

Things appear fine for ilxtr:neuron-type-aacar-12 on SCKAN's staging endpoint (https://scicrunch.org/api/1/sparc-scigraph) but not production (https://scicrunch.org/api/1/sckan-scigraph), and comparing the returned result sets shows missing data.
A query from staging on August 18 has connectivity for this path, and then, according to @tgbugs on Slack on August 25:

I have done the zenodo DOI release for the 2020-08-19 release that is currently on the sparc-scigraph staging endpoint and would like to proceed to switch the sckan-scigraph over to that as well, are there any objections to doing that at this point? This will become our next stable release.

And following our approval:

sckan-scigraph is running the new version,

so why doesn't production have what was on staging??
Differences in result sets:
--- stage.json	2022-09-06 20:19:14.000000000 +1200
+++ prod.json	2022-09-06 20:20:13.000000000 +1200
@@ -66,16 +66,6 @@
             'isDefinedBy': ['https://apinatomy.org/uris/models/ard-arm-cardiac'],
             'owlType': ['Annotation']
         },
-        'obj': 'aacar:dc-sn-pulart_12_lnk_1',
-        'pred': 'apinatomy:nextChainStartLevels',
-        'sub': 'aacar:dc-sn-icg_12_lnk_1'
-    },
-    {
-        'meta':
-        {
-            'isDefinedBy': ['https://apinatomy.org/uris/models/ard-arm-cardiac'],
-            'owlType': ['Annotation']
-        },
         'obj': 'aacar:A61',
         'pred': 'apinatomy:endsIn',
         'sub': 'aacar:ac-sn-icg_12_lnk_1'
@@ -166,16 +156,6 @@
             'isDefinedBy': ['https://apinatomy.org/uris/models/ard-arm-cardiac'],
             'owlType': ['Annotation']
         },
-        'obj': 'aacar:dc-sn-aorta_12_lnk_1',
-        'pred': 'apinatomy:nextChainStartLevels',
-        'sub': 'aacar:dc-sn-icg_12_lnk_1'
-    },
-    {
-        'meta':
-        {
-            'isDefinedBy': ['https://apinatomy.org/uris/models/ard-arm-cardiac'],
-            'owlType': ['Annotation']
-        },
         'obj': 'SAO:420754792',
         'pred': 'apinatomy:inheritedExternal',
         'sub': 'aacar:dc-sn-mcg_12_lyph_1'
@@ -435,16 +415,6 @@
             'isDefinedBy': ['https://apinatomy.org/uris/models/ard-arm-cardiac'],
             'owlType': ['Annotation']
         },
-        'obj': 'aacar:dc-sn-aorta_12_lnk_1',
-        'pred': 'apinatomy:nextChainStartLevels',
-        'sub': 'aacar:dc-sn-mcg_12_lnk_1'
-    },
-    {
-        'meta':
-        {
-            'isDefinedBy': ['https://apinatomy.org/uris/models/ard-arm-cardiac'],
-            'owlType': ['Annotation']
-        },
         'obj': 'aacar:dc-sn-icg_12_lnk_1',
         'pred': 'apinatomy:sourceOf',
         'sub': 'aacar:ns185'
@@ -465,16 +435,6 @@
             'isDefinedBy': ['https://apinatomy.org/uris/models/ard-arm-cardiac'],
             'owlType': ['Annotation']
         },
-        'obj': 'aacar:dc-sn-pulart_12_lnk_1',
-        'pred': 'apinatomy:nextChainStartLevels',
-        'sub': 'aacar:dc-sn-mcg_12_lnk_1'
-    },
-    {
-        'meta':
-        {
-            'isDefinedBy': ['https://apinatomy.org/uris/models/ard-arm-cardiac'],
-            'owlType': ['Annotation']
-        },
         'obj': 'aacar:A62',
         'pred': 'apinatomy:endsIn',
         'sub': 'aacar:ac-sn-mcg_12_lnk_1'
@@ -1463,7 +1423,7 @@
         }
     },
     {
-        'id': 'aacar:dc-sn-aorta_12_lnk_1',
+        'id': 'aacar:ac-sn-icg_12_lnk_1',
         'lbl': None,
         'meta':
         {
@@ -1477,7 +1437,7 @@
         }
     },
     {
-        'id': 'aacar:ac-sn-icg_12_lnk_1',
+        'id': 'aacar:dc-sn-aorta_12_lnk_1',
         'lbl': None,
         'meta':
         {

What results do you get when you run the ontology timestamp queries against prod and staging?

@dbrnz - What specific query that you were running on the endpoint

@jgrethe it turns out that neru-5 was still being used for production. All is fine with neru-6, so closing the issue.


Default select values

Very useful plugin. Thank you for that ;)
Is there by chance anyway to set default values for the columns and operators select fields ?

I want this feature too. Dear author, please update this useful package.

Want that too!


Please update build

Can you update build? Current build doesn't work on IntelliJ Community Edition 2016.1 cause this bug -> #19

Or you can provide command to make a jar from source files.
Cheers.

Well be updating the plugin in the coming months and distributing it on the
proper plugin repository in the IDE.
On Wed, Jun 22, 2016, 5:59 AM Artem Garkusha<EMAIL_ADDRESS>wrote:

Or you can provide command to make a jar from source files.
Cheers.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/square/dagger-intellij-plugin/issues/21#issuecomment-227698241,
or mute the thread
https://github.com/notifications/unsubscribe/AAEEER4rHGAha2kzqJ6t629ju2iO9neOks5qOQdogaJpZM4I2KXO
.

hello

@UndeRus @GarkushaArtem I have built the latest version using IntelliJ 2016.2 CE and Java 8, the binaries are available on my fork.
I am not going to open a PR for that, though. I suspect the plugin needs to be compiled with less strict settings (Java 7?).

I have a crash when using with Android Studio 2.2.2
Build #AI-145.3360264, built on October 18, 2016
JRE: 1.8.0_76-release-b03 amd64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
StackTrace attached
DaggerPluginCrashMsg.txt


Interesting

Thanks for answering these questions.

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

ID: 5f6bd837-63e3-8bcd-9743-425e6da4a9b8
Version Independent ID: 944bd5e0-a52f-0a4c-362b-68701f03c8d8
Content: Administering Power BI - frequently asked questions (FAQ) - Power BI
Content Source: powerbi-docs/service-admin-faq.md
Service: powerbi
GitHub Login: @mgblythe
Microsoft Alias: mblythe

Closing test issue


toggleFindInSelection can only be triggered by keyboard, but not mouse click

Issue Type: Bug
1.Using shortcut Ctrl+F to open search bar.
2.Enter the string to search for.
3.There are 17 results I find.
4.After click toggleFindInSelection on search bar with mouse, there is only 1 result left.
5.Then, I try to click toggleFindInSelection again on seach bar with mouse, but there is still 1 result left, it should be 17 results.
6.Finally, I try to use shortcut Alt+L to trigger it, and it give me 17 results
I can turn on toggleFindInSelection by both mouse click and shortcut Alt+L, but can turn off toggleFindInSelection only by shortcut Alt+L.
VS Code version: Code 1.31.1 (1b8e8302e405050205e69b59abb3559592bb9e60, 2019-02-12T02:20:54.427Z)
OS version: Windows_NT x64 10.0.17134

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz (4 x 2400)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: enabledsurface_synchronization: enabled_onvideo_decode: enabledwebgl: enabledwebgl2: enabled

Memory (System)
7.87GB (3.82GB free)

Process Argv
C:\Users\KEN\AppData\Local\Temp\scp06517\pmst113.php

Screen Reader
no

VM
0%

Extensions (7)

Extension
Author (truncated)
Version

vscode-database
baj
2.0.0

xml
Dot
2.4.0

php-debug
fel
1.12.6

php-intellisense
fel
2.3.10

vscode-mysql
for
0.3.0

vscode-language-pack-zh-hant
MS-
1.31.4

snippet-creator
nik
0.0.5

(1 theme extensions excluded)

@slumder I can't reproduce this issue in latest Insiders anymore, can you help confirm it ?

Close as lack of enough information to help troubleshoot. We can reopen whenever we have good reproduce steps.


Code Cleanup

Some areas of the bot need some housekeeping. The music and the user data need their own modules on the frontend. They should only be called when needed (following the commands structure).
Quotes also need this but that entire system needs a rewrite. It will likely need its own page as well.

Closed due to Glimesh ending


Update jumpcloud SAML role to SSO role

We switch to using AWS SSO and removed SAML integration therefore
the SAML roles are gone.  We replace with the AWS generated SSO role.
We need to hard code the value because the SSO role is created by
the organizations account where AWS SSO runs.

merging to fix the build.


Report Widgets accessing other layer's field

In the report widgets, is it possible to have fields from other layers? If so, how can I do that?
Thanks,

@jkyoungchoi I provided an example that might be helpful to you in my response to issue #99


Attention Transfer

Added the code for Forward Hook Manager (for extracting intermediate layers) in distill.py
Added the code for Distillation via Attention Transfer
Attention Transfer was working correctly on Cifar10 dataset for WideResNet (consider adding this to models). However, the AttentionTransfer class doesn't include code for automatically selecting the optimizer (it can be fixed at a later stage when various optimizers and schedulers are available in BaseAlgorithm)

@aryamaanthakur can you also add an experiment notebook in this branch that shows how attention transfer works. See the notebook from @rishabh-16 in the dev. it is still to be improved, but we need a clean notebook explaining how attention transfer can be done.
Once you have added it to this branch, I will add more comments.

@dkgupta90 , @aryamaanthakur already has a notebook. Lets not push another.

@aryamaanthakur is this PR still valid?

No, closing this.


Slightly better settings

That's already cool. No more terminal for hiding status bar item. And for "Paste by Default" setting.
Native status bar icon hiding (respecting old showInStatusBar setting)

Drag it away from status bar holding Command until you see a cross.
Let it go.

To recover the icon, open Maccy when it's already running.

showInStatusBar still exists. And still, unlike the native function, it requires a relaunch.
The new (quick, and native) statusItem.isVisible will inherit showInStatusBar state.

Paste by Default preference,
Info about other settings with How to button leading to #customization

Realised that it's hard to make slider and input right here, in the menu.
Would be cool, but it's over my level. Just have no time to learn it for now.

Fn+Ctrl+Backspace shortcut for Clear menu item

Thanks for a new PR, but that's not what I had in mind. Sorry if that was not clear from my previous comment:

Can you open 1 PR with menu bar icon removal? I'll be able to just merge it and make a new release.
For the preferences, I would still like to have them implemented altogether. I'm not asking you to do this and I don't know when I'll have time to work on it, but I don't want to merge partially-implemented preferences submenu.

Would you mind if I amend your commit to only include removal of menu icon and merge it?

My apologies this took so long, but I wanted to improve the solution and update the configuration whenever icon is dragged away or app is restarted. This is now merged in e72b50ff75b7fcd7095e5528b2377575c3ecff08.


some pod energy not reported

Describe the bug
A clear and concise description of what the bug is.
Ubuntu env (kind running on a Ubuntu host)
# cat /proc/18005/cgroup
1:cpuacct:/
0::/system.slice/docker-3f3488e110e93031b1528ecfb2bc5332eae24cf8e578b38e660755c894768196.scope/kubelet.slice/kubelet-kubepods.slice/kubelet-kubepods-podd59c0a68_38a6_49a9_8228_f58bde917e74.slice/cri-containerd-dc39c4066a25edda33a0c58d85a96cf27bbb7d3d429a9a7e3f243e9c3507c1b8.scope

but in logs

pid 18005 cgroup 0 cmd kindnetd

2022/09/20 01:30:32 failed to resolve pod for cGroup ID 0: failed to open cgroup description file for pid 18005: open /proc/18005/cgroup: no such file or directory, set podName=system_processes

there is no pod info in final output

energy from pod (1 processes): name: local-path-provisioner-9cd9bd544-whx5v namespace: local-path-storage
        cgrouppid: 0 pid: 1891 comm: uwsgi
        ePkg (mJ): 14 (14) (eCore: 14 (14) eDram: 176 (176) eUncore: 0 (0)) eGPU (mJ): 0 (0) eOther (mJ): 0 (0)
        eDyn (mJ): 0 (0)
        avgFreq: 0.00
        CPUTime:  0 (0)
        counters: map[cache_miss:0 (0) cpu_cycles:0 (0) cpu_instr:0 (0)]
        cgroupfs: map[]
        kubelets: map[container_cpu_usage_seconds_total:0 (437) container_memory_working_set_bytes:0 (10362880)]

energy from pod (140 processes): name: system_processes namespace: system
        cgrouppid: 0 pid: 1319 comm: kcs-term
        ePkg (mJ): 14 (6023) (eCore: 14 (6023) eDram: 176 (78436) eUncore: 0 (0)) eGPU (mJ): 0 (0) eOther (mJ): 0 (0)
        eDyn (mJ): 0 (0)
        avgFreq: 0.00
        CPUTime:  246000<PHONE_NUMBER>62387)
        counters: map[cache_miss:0 (0) cpu_cycles:0 (0) cpu_instr:0 (0)]
        cgroupfs: map[]
        kubelets: map[container_cpu_usage_seconds_total:1 (47506) container_memory_working_set_bytes:266240<PHONE_NUMBER>)]

energy from pod (2 processes): name: coredns-6d4b75cb6d-5kzhk namespace: kube-system
        cgrouppid: 0 pid: 2127 comm: python3
        ePkg (mJ): 14 (6023) (eCore: 14 (6023) eDram: 176 (78436) eUncore: 0 (0)) eGPU (mJ): 0 (0) eOther (mJ): 0 (0)
        eDyn (mJ): 0 (0)
        avgFreq: 0.00
        CPUTime:  1005 (307397)
        counters: map[cache_miss:0 (0) cpu_cycles:0 (0) cpu_instr:0 (0)]
        cgroupfs: map[]
        kubelets: map[container_cpu_usage_seconds_total:0 (2658) container_memory_working_set_bytes:0 (19816448)]

energy from pod (1 processes): name: kube-controller-manager-kind-control-plane namespace: kube-system
        cgrouppid: 0 pid: 688 comm: multipathd
        ePkg (mJ): 14 (6023) (eCore: 14 (6023) eDram: 176 (78436) eUncore: 0 (0)) eGPU (mJ): 0 (0) eOther (mJ): 0 (0)
        eDyn (mJ): 0 (0)
        avgFreq: 0.00
        counters: map[cache_miss:0 (0) cpu_cycles:0 (0) cpu_instr:0 (0)]
        cgroupfs: map[]
        kubelets: map[container_cpu_usage_seconds_total:0 (15764) container_memory_working_set_bytes:0 (52715520)]

node energy (mJ):
        ePkg: 53 (eCore: 53 eDram: 701 eUncore: 0) eGPU: 0 eOther: 0

To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

I suspect kindnetd is in a different pid namespace (i.e. pid 18005, seen by kepler ebpf may be different when kepler userspace runtime reads from its /proc namespace).

ok, I might need some guide on how the pod energy is actually calculated
I know we have ebpf, we have cgroup data, what's the formula to do the calcuation?
e.g some record should be in cgroup data first then find corresponding record in ebpf?
@rootfs

the current formula uses ratio based method. If enabled, there is also a model based dynamic power estimate
You'll find the energy calculation is done here on the pods

some record should be in cgroup data first then find corresponding record in ebpf?

ebpf gets the info associated with the running process: cgroup id, pid, cpu runtime, perf counters, etc. This info is coupled with userspace info collected from sysfs and feed into the energy estimate formula to get the pod energy.

indeed, previously I used
BM => VM => docker (kind) => k8s
now I switched to
BM => VM => k8s
it's much better now, will check all the links you provided, thanks


[Improve][File-Connector] Support write fixed/timestamp as int96 of parquet

Purpose of this pull request
[File-Connector] Support write fixed/timestamp as int96 of parquet
Does this PR introduce any user-facing change?
Add new config items of sink
sink {
    LocalFile {
        ...
        parquet_avro_write_timestamp_as_int96 = true
        parquet_avro_write_fixed_as_int96 = ["f1", "f2", "f3"]
   }
}

How was this patch tested?
Added
Check list

[ ] If any new Jar binary package adding in your PR, please add License Notice according
New License Guide
[x] If necessary, please update the documentation to describe the new feature. https://github.com/apache/seatunnel/tree/dev/docs
[ ] If you are contributing the connector code, please check that the following files are updated:

Update change log that in connector document. For more details you can refer to connector-v2
Update plugin-mapping.properties and add new connector information in it
Update the pom file of seatunnel-dist

[ ] Update the release-note.

cc @Hisoka-X @TyrantLucifer @wuchunfu ci is passed


Does not compile. embedded_hal API changed

unresolved import `embedded_hal::delay::blocking`

Path which would resolve in alpha v7 but is not working properly in alpha v9
Consider using an exact version specifier like this:
embedded_hal = "=1.0.0-alpha.7"

ahh yeeah we should fix (and probably also upgrade) that... for now fixing the version in your top level crate should sort it out?

Yeah just wanted to let you guys know ^.^


add sample for table cell coloring

https://github.com/abap2UI5/abap2UI5/issues/1551

cool, thanks 😎


sort dirs and files separately

sorting should always keep sorted directories on top

It is already sorting the directories and files separately.

if we take everything as equivalent item that would be correct. We have to answer the question if we want to set a new viewpoint or believe the other tools do it better. e.g. nautilus shows first dirs then files. We could also invent a new kind of grouping, all the old tools are on a 1:1 translation path of something before theire introduction.


fix: remove redundant param from endpoint

The v1/modules/:module_id/keys endpoint can accept only two query params (used and operatorIndex) that it uses to filter keys from the output. But previously public interface of this endpoint incorrectly stated that it also can accept the moduleAddresses param. It doesn't make sense, because module ID is specified in the :module_id URL param for this endpoint.
Now the moduleAddresses search param has been removed from the public interface of the endpoint.

UPD.
Remove unnecessary moduleAddresses query param from all endpoints where it was declared, but not used. These endpoints are:
/v1/modules/keys
/v1/modules/:module_id/keys
v1/modules/:module_id/operators/keys


fix: prevent unnecessary layout saves

Pull request checklist:

[x] CHANGELOG.md was updated, if applicable

Description
BaseWindow is forcing delayed layout save
at every resizeEvent
https://github.com/Chatterino/chatterino2/blob/22bd78e3b3dd6721db5f75d3456e3876185f0f3d/src/widgets/BaseWindow.cpp#L543
and moveEvent
https://github.com/Chatterino/chatterino2/blob/22bd78e3b3dd6721db5f75d3456e3876185f0f3d/src/widgets/BaseWindow.cpp#L575
TooltipWidget and other subclasses unnecessarily triggers both of above.
PR adds new BaseWindow flag DisableLayoutSave to fix that
Tested movement and resizing of tooltips (after preview images load) and everything works as expected.

turned out to be quite a few windows/popups.
not sure if its better to keep current Disable approach, or change it to Enable and only pick these we want to save (mostly splits/notebook stuff + emote popup)


pCMA Control - Data Mgmt

Control Register

Data   Management

X

DM12
Enterprise data   follow standard data architecture models

Moved to MVG. Closing this ticket here.


Browser buttons don't respond to clicks

I was trying to test out the fix to #4, but the auto refresh button didn't seem to do anything when I clicked it. Upon further investigation, I noticed that none of the browser buttons seem to be responding to my clicks. (The menu, refresh, and back buttons don't do anything when I click them.)
The only button that seems to respond to my clicks is the globe itself in the upper-left, which responds by hiding the url bar.
In-page buttons are not affected by this bug.
Atom Version: 0.177.0
System: Microsoft Windows 8.1

That is really broken.  Will fix right now.  I have got to get some spec
tests going.
On Sun, Feb 8, 2015 at 8:35 PM, Andrew Meyer<EMAIL_ADDRESS>wrote:

I was trying to test out the fix to #4
https://github.com/mark-hahn/web-browser/issues/4, but the auto refresh
button didn't seem to do anything when I clicked it. Upon further
investigation, I noticed that none of the browser buttons seem to be
responding to my clicks. (The menu, refresh, and back buttons don't do
anything when I click them.)
The only button that seems to respond to my clicks is the globe itself in
the upper-left, which responds by hiding the url bar.
In-page buttons are not affected by this bug.
Atom Version: 0.177.0
System: Microsoft Windows 8.1
—
Reply to this email directly or view it on GitHub
https://github.com/mark-hahn/web-browser/issues/29.

fixed in 1.1.4
Sorry and thanks.  I released it with a bunch of important commented out for debugging.

Stuff was commented out? Ha. That's a new one for me. :smirk:
Yeah, some tests (and maybe a Travis build) would probably be helpful at this point. :laughing:


Add support for multipart subscriptions

This is a new protocol created by Apollo (and supported by Apollo Client)
TODO

[ ] Add support for this in all HTTP integrations that support subscriptions
[ ] Make sure that the returned responses is actually being streamed
[x] Send a ping every 5 seconds (an empty {} is enough)
[x] Add a proper way to check if an operation is a subscription in our Async HTTP View
[ ] Return proper error when trying to run a subscription and it's not supported

Protocol docs: https://www.apollographql.com/docs/router/executing-operations/subscription-multipart-protocol/

one thing I'm not sure about this is handling client closing the connections 🤔

/pre-release

/pre-release

Pre-release
:wave:
Releasing commit [52b2f2d467660baa99cc0b5f55ad1a83f740b8b9] to PyPi as pre-release! :package:

Pre-release
:wave:
Pre-release 0.210.0.dev.1697796691 [52b2f2d467660baa99cc0b5f55ad1a83f740b8b9] has been released on PyPi! :rocket:
You can try it by doing:
poetry add strawberry-graphql==0.210.0.dev.1697796691

/pre-release

/pre-release

Apollo Federation Subgraph Compatibility Results

Federation 1 SupportFederation 2 Support

_service🟢@key (single)🟢@key (multi)🟢@key (composite)🟢repeatable @key🟢@requires🟢@provides🟢federated tracing🔲@link🟢@shareable🟢@tag🟢@override🟢@inaccessible🟢@composeDirective🟢@interfaceObject🟢

Learn more:

Apollo Federation Subgraph Specification
Compatibility Tests

Thanks for adding the RELEASE.md file!

Here's a preview of the changelog:

This release adds support for multipart subscriptions in almost all*
integrations!
Multipart subcriptions
are a new protocol from Apollo GraphQL, built on the
Incremental Delivery over HTTP spec,
which is also used for @defer and @stream.
The main advantage of this protocol is that when using the Apollo Client
libraries you don't need to install any additional dependency, but in future
this feature will make it easier for us to implement @defer and @stream
Also, this means that you don't need to use Django Channels for subscription,
since this protocol is based on HTTP we don't need to use websockets.

Flask, Chalice and the sync Django integration don't support this yet.

Here's the tweet text:
🆕 Release (next) is out! Thanks to @patrick91 for the PR 👏

Get it here 👉 https://beta.strawberry.rocks/release/(next)

🔥


Abolish UnboxedBool stack representation

Abolish UnboxedBool in favour of Vanilla. We now always use {0, 1} for Bool values, since they never get dereferenced, and GC avoids visiting everything that is not in the dynamic heap (e.g. small constants, pointers into the first page etc.)
Resolves #2906.

@nomeata I am confident that we didn't use non-0/1 values in UnboxedBool, since the only places these originate from are the lit and primitive predicates. We don't cast e.g. Nat16 to Bool ever.


fix: issue #387 Out of range value for column 'total_sent'

agora_1     | 2021-07-26 08:33:22,317 Info [boa1xrval7gwhjz4k9raqukcnv2n4rl4fxt74m2y9eay6l5mqdf4gntnzhhscrh] - Accepted transaction: Inputs (1): 0x80d1...7a63:0x5963...d49a toolsdev_1  | AutoSend: Status = true; Hash = 0xdb5bab6ea84412960209b57fa1630a5216af9a4b8eedf7c47cee486e2b23af3eddedfbe9dc6c66d6d197f1c8b1d1ab4e8d10de7da6a52edd0e1faa4c177d88f2 stoa_1      | (node:26) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 231) stoa_1      | (node:26) UnhandledPromiseRejectionWarning: Error: Out of range value for column 'total_received' at row 1 stoa_1      |     at Packet.asError (/stoa/bin/node_modules/mysql2/lib/packets/packet.js:712:17) stoa_1      |     at Query.execute (/stoa/bin/node_modules/mysql2/lib/commands/command.js:28:26) stoa_1      |     at Connection.handlePacket (/stoa/bin/node_modules/mysql2/lib/connection.js:425:32) stoa_1      |     at PacketParser.onPacket (/stoa/bin/node_modules/mysql2/lib/connection.js:75:12) stoa_1      |     at PacketParser.executeStart (/stoa/bin/node_modules/mysql2/lib/packet_parser.js:75:16) stoa_1      |     at Socket.<anonymous> (/stoa/bin/node_modules/mysql2/lib/connection.js:82:25) stoa_1      |     at Socket.emit (events.js:315:20) stoa_1      |     at Socket.EventEmitter.emit (domain.js:467:12) stoa_1      |     at addChunk (internal/streams/readable.js:309:12) stoa_1      |     at readableAddChunk (internal/streams/readable.js:284:9) stoa_1      | (node:26) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 232)

Error: Out of range value for column 'total_received' at row 1


compose chart for desktop in intelliJ IDEA

Please help me for add implementation for compose chart desktop in my project intelliJ.
I want to add charts(bar & pie) to compose desktop project.

@momeni1367 this is supporting desktop

Hey @momeni1367, Can you please help me with how to add this lib in compose desktop?


No SQL mode in web console

Added 'No SQL mode' in the web console where all data retrieved from the server is through sending GET requests to Druid APIs instead of running SQL queries, just like the legacy consoles
No SQL mode is enabled when the broker for SQL query is down
Client-side workaround to fix https://github.com/apache/incubator-druid/issues/7498 until Druid SQL returns servers which have no data

Made a quick note on the wording of the notice and I think it is good otherwise. 👍 once my comment above is addressed.


Rendered month in Blog

I have found a bug in the Blog module displaying the published date. I cannot detect any errors in the Dutch translation.
The Blog date format is set '01 januari 2016' (Dutch translation). The rendered month is not correct. For example:
januari  > januariuari
februari > februariruari
juni     > junii
november > novemberember
december > decemberember

For myself I found a solution by editing '\inc\modules\blog\Admin.php'. I changed the 'dateformats' section in four places as follows:
[
    'value' => 'd M Y',
    'name'  => '01 '.$this->lang('jan').' 2016'
],
...
[
    'value' => 'd M Y, H:i',
    'name'  => '01 '.$this->lang('jan').' 2016, 12:00'
],

So I removed an 'x' four times and with that the reference to the translation that is apparently only needed in the Polish language.


Refactor structures.py

Refactor lapsepy/journal/structures.py as it has a very sloppy look.

Hi, I'd like to work on this.


Create C++ Program to Find All Roots of a Quadratic Equation

I have created a c++ program for calculating roots of quadratic equations

@2001IshuPatel Add the program in program folder with proper file extension


esp32-c3: Add support to RNG peripheral

Summary
Add support to RNG peripheral
Impact
Only ESP32-C3
Testing
ESP32C3-Devkitc

@xiaoxiang781216 / @Ouss4 please merge it


Initial wip overridable context implementation

Adds #4

Some comments on the current status:

Shallow merge (spread)
Typed as closely to the original React Context type as possible (see OverridableContext)
Untested! Pushed to discuss

@transitive-bullshit I got to go rn, but let me know how do you like this approach so far. I haven't checked the notion example yet (will do when I resume work here). Have a good one!

Gonna work on this a little more. To keep things moving forward:

Gonna rework the implementation to make it specific to the use case, with custom types :+1:
Should we re-export the consumer (as with your notion-x example)?
I understand that the merging algorithm from the notion-x example is deleting properties if the overrides explicitly declare them with undefined value. Do we want this behavior here too? Besides that, the merging would otherwise be shallow, is that ok?
Do we want to deep merge instead? If that's the case, should it be in a case-by-case basis or just a generic lodash/merge kind of thing?
If it is case-by-case, what cases are there?
Do we need to merge with the defaults everytime, or would it suffice with the initial context defaults? (I think it probably would)

Let me know your thoughts @transitive-bullshit

My answer to all of your questions is KISS. 😄
Let's just get it working with the simplest solution possible & then we can always improve over time.

Notes:

Now the exports are TwitterContextProvider and useTwitterContext (renamed from useTwitter for consistency).
Both tweetAstMap and swrOptions are being shallowly merged (not the context value!).

I think this should be enough for now! If this looks ok for you I can move on to:

Testing

Manual (should I use the example for this?)
Unit (is it worth testing this independently or is it / could it be covered by a more general test?)

Using it where it makes sense (haven't checked it yet)

Lemme know @transitive-bullshit

This looks awesome, @DaniGuardiola 🙏
I'll respond in-depth soon.

Also, make sure that npm run test passes. It's set up to run through travis-ci for this, but my travis acct is past its free OSS limit (shame on travis-ci) https://travis-ci.com/github/transitive-bullshit/react-static-tweets

Lemme know when you think this is good to go @DaniGuardiola — no rush :)

@transitive-bullshit I will come back to this soon :+1:

Hey @transitive-bullshit, I'm not being able to run the tests. Here's the full log:
dani ~/projects/open-source/react-static-tweets partial-context $ yarn test
yarn run v1.22.5
$ run-s build
$ run-s clean
$ del packages/*/build
$ tsc --build tsconfig.json
$ run-s test:*
$ lerna run test
lerna notice cli v3.22.1
lerna info Executing command in 1 package: "yarn run test"
lerna ERR! yarn run test exited 1 in 'static-tweets'
lerna ERR! yarn run test stdout:
$ ava -v 'build/cjs/**/*.test.js'

  ✖ Couldn’t find any files to test

info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

lerna ERR! yarn run test stderr:
error Command failed with exit code 1.

lerna ERR! yarn run test exited 1 in 'static-tweets'
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
ERROR: "test:unit" exited with 1.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

I don't know if I'm missing something, let me know if that's the case, or if you can repro otherwise.

Thanks @DaniGuardiola 💯 Published as v0.3.0.
I fixed the test issue locally btw.

@transitive-bullshit Awesome! I'll keep working on other issues these days.


[Question] How to Configure Backup RPCs

I’m looking for example config for set up backup RPCs in eRPC.
Here’s the scenario:

I have 1 self-hosted node and 1 pay-as-you-go node (e.g. QuickNode).
The goal is to use the self-hosted node as the primary and only fall back to the pay-as-you-go node(backup node) if the primary goes down.

Could you share an example or provide instructions on how to configure this setup?

@Planxnx there are 2 ways to control fallback behavior for such purpose:

To use the upstream.scoreMultipliers to make your self-hosted node always the preferred on request-level (first try that node and if request fails immediately retry on others) https://docs.erpc.cloud/config/projects/upstreams#customizing-scores--priorities

In this method all upstreams are always available but starts from your own nodes.

Is to use network.selectionPolicy as described here: https://docs.erpc.cloud/config/projects/selection-policies

In summary if you assign group: fallback to any of your upstreams a "default" selection policy is activated where it exclude these fallback nodes and ONLY add them if other upstreams (you self-hosted node) are down.
In this method runs on some interval  (5 minutes) and decides which upstreams to have active or disable completely. I recommend to use this one with caution and proper testing.
If you need any further help or question feel free to post here or join the telegram group: https://t.me/erpc_cloud


Regarding the issue of labelcol

May I ask if I want to replace the label of the dataset with my own, and only need to match a black image of the same size according to the original image size? I didn't see anything else in the black picture

Hi, actually these labels are not pure black, the foreground regions are with very small values, so it seems that they are all black.

Thank you for your answer. I am not familiar enough with the GlaS dataset.