pythonPackages.backports-entry-points-selectable: 1.0.4 -> 1.1.0

Fixes test failures against python3Packages.importlib-metadat-4.6.4
(failure introduced in ef870b8 "python3Packages.importlib-metadata: 4.0.1 -> 4.6.4").

We are trying to get rid of backprots-entry-points-selectable, see #123573. Will rebase the PR shortly.

Aha, sounds good. Abandoning the PR.

Updated that PR, hopefully we can get it merged this time :)


Parse error for (string): {}

Hello, first of all, thank you very much for this plugin 👍
The parser fails to understand syntax like this:
command: test: {
	for t in tests {
		(t.name): {
			print: cli.Print & {
				text: "testing \(t.name)"
			}
		}
	}
}

Per an exchange with @jansorg on CUE slack, the missing piece in the puzzle here is an update in the CUE spec for dynamic fields: https://github.com/cue-lang/cue/issues/2267

Thanks a lot @myitcv! I've updated the plugin and I can confirm this issue has been fixed.

Wonderful, @stefanprodan! Thanks @jansorg for the fix.

This is still an issue as soon as you add another prefix
metadata: (k): v

@fionera Thanks! I'd rather wait for the official grammar at https://github.com/cue-lang/cue/issues/2267 before I attempt again to guess what the grammar is supposed to be.

Version 0.10.0 should fix this. It'll be available soon on the Marketplace.


Implement predict_linear function in PromQL

What problem does the new feature solve?
predict_linear is a function that predicts the future value. It's based on simple linear regression just like deriv()
What does the feature do?
Implement the predict_linear function: predict_linear(v range-vector, t scalar)
Implementation challenges
unlike other range functions, predict_linear accepts one extra parameter t to specify the time. #[range_fn] util macro doesn't support this format thus we need to implement the entire structure manually. A similar case is the idelta under promql/functions/idelta.rs.

cc @haohuaijin for who implemented the deriv() function. This is a bit more challenging than deriv(). Would you like to take this?

Sure, I'm happy to take it. @waynexia

Closed by #1362


How to replace JetStreamOutgoingMessageMetadata?

#243 deleted the JetStreamOutgoingMessageMetadata class and there seems to be no easy replacement.
I used to use it to pass a subtopic when sending messages to nats:
  @Override
  protected org.eclipse.microprofile.reactive.messaging.Message<T> createMessage(Event upstreamEvent, T messagePayload) {
    Map<String, List<String>> headers = new HashMap<>();
    createHeaders(upstreamEvent, (name, value) -> headers.put(name, List.of(value)));
    JetStreamOutgoingMessageMetadata metadata =
        JetStreamOutgoingMessageMetadata.of(
            upstreamEvent.getIdAsText(), headers, subtopic(upstreamEvent));
    return org.eclipse.microprofile.reactive.messaging.Message.of(messagePayload, org.eclipse.microprofile.reactive.messaging.Metadata.of(metadata));
  }

How can I achieve the equivalent now? I cannot upgrade to 3.17.5 because of that.

Sorry please have a look at 3.17.6 where I have reimplemented the support for subtopics. JetStreamOutgoingMessageMetadata is renamed to SubscribeMessageMetadata. Sorry for the inconvenience


"Command can't have itself as a dependency" floods console with SSIL enabled and set to Very Low

Tested versions
4.3 dev3 stable.
Description
After updating my godot project from 4.2.0, this error began flooding the output, both in editor and in-game.

System information
Windows 11 - Godot 4.3.0dev3 - Forward+ renderer, using Vulkan - Nvidia GTX 1650, Intel i5 9300H Cpu, 8GB of Ram
Issue description
After updating my godot project from 4.2.0, this error began flooding the output, both in editor and in-game.
I did not change any setting after updating, and did delete the .godot folder and reopened the project in an attempt to rectify the issue.

E 0:00:18:0789   _add_command_to_graph: Command can't have itself as a dependency.
  <C++ Error>    Condition "!resource_has_parent" is true.
  <C++ Source>   servers/rendering/rendering_device_graph.cpp:464 @ _add_command_to_graph()

From my testing, this error occurs when SSIL is enabled in a WorldEnvironment node, with it's quality set to Very Low in project settings.
Steps to reproduce

Add a world environment node with a new environment
Enable SSIL in the environment
Go to project settings with advanced settings enabled.
Under Environment in project settings, set the SSIL quality to Very Low

Minimal reproduction project (MRP)
mrp.zip

After further testing, this also occurs with SSAO.

cc @DarioSamo

This is one of two possibilities:

The graph validation is erroneous.
SSIL at low had undefined behavior due to using textures in some way (e.g. overlapping slices).
I'll review during the week which of those two that is, but I felt it was worth pointing out we can start running into situations where it's just exposing existing bugs (we had a few of those when the graph was added).

interesting. Looking forward to a fix for this, as Very Low and Low don't really have a visible difference but do have a performance difference.

After further testing, this also occurs with SSAO.

I missed this comment, I can reproduce this as well. Guessing it's a similar issue.

The PR will now fix both SSIL and SSAO. Feel free to point out any more of these issues you run into, it seems the behavior changes quite a bit depending on the quality of these algorithms sometimes so the graph might end up exposing some of the undefined behavior it was doing.

The PR will now fix both SSIL and SSAO. Feel free to point out any more of these issues you run into, it seems the behavior of these algorithms changes quite a bit depending on the quality so the graph might end up exposing some of the undefined behavior it was doing.

Alright, thank you. Will check out the PR later today when I have the time

@DarioSamo Tested the PR, can confirm that the issue is fixed. Another issue ended up appearing when I opened the PR but I don't think that one requires a github issue opened. Thanks so much for the help!

Will leave this issue opened until the PR gets merged (I think thats how things move around here? I don't create issues often)


[question] Will pull requests get merged and status of tye

Hi,
I've been using Tye for the past year and really like it. I've been using it in a few projects and am interested in seeing this project succeeding in its goals. There are a few things that cause me concern however, and I'd like to know what the maintainers' plans are for Tye.
One thing that causes me concern is that I've been trying to getting simple improvements merged for over 8 months now, first in #916 and then in #1153, but sadly no maintainer has taken the time to review the changes. There are also a number of other pull requests that contain useful features or improvements which would make Tye even better.
I've also noticed that the (what I believe to be the) original maintainers seem to have left the project behind ( 072de978b7d2882c3433e37e5f1c8349b622bb98 ) and that since ~0.7 no changes were made to Tye other than a few improvements in the APIs used by the VS code extension.
My questions are:

Is this project actively maintained?
Will this project still be around in a year or two?

As far as I am aware this is the best tool for developing and running a microservice application locally. I am grateful for it's existence and the time people have put into it and I would really like to keep using Tye.

I agree. I've been using Tye a lot the past year and I would really like it (or something similar to exist).
For me personally, I don't care much about the different integrations (Kubernetes, dapr, automatic service discovery etc). But I really appreciate tye run. Based on a tye.yaml where our applications are defined, I can mix and match and choose what I want to run (Docker containers, dotnet processes etc) simply by specifying different tags.
The one thing that I really miss and was hoping for, is the possibility to start/stop/restart individual services. Where Tye runs more like a deamon in the background, keeping track of it all.
I don't know that there are other tools available that lets you do this easily? Any advice would be appreciated if they exist. I have been thinking about forking Tye, keep the things that I like and add the things that I miss. But as always, my amount of spare time works against me 😊
Hoping for some kind of announcement (positive or negative)!

@ikkentim, looks like David just approved your outstanding PR, which I think supersedes the other one that you closed. Thanks for your contributions!
@jooooel, we are happy to hear you find Tye useful and we are working hard to get some of the top issues resolved. Would you please open a separate issue for your idea of being able to start/stop/restart individual services? That way we can see if others have the same need and prioritize it appropriately. Also, have you tried the --watch flag which will restart services that have had changes made to them?

@BigMorty Thanks for getting back to us, sounds like Tye hasn't been totally buried then 😉
I've actually opened an issue regarding start/stop already, and I did a little PoC just to get a feel for how Tye works and what it would take. My solution works, but I think it would be better to go towards more of a "deamon" approach as I mentioned.
I've tried to use --watch, but due to the nature of the codebase I use, it doesn't really perform well when doing changes in common libs (lot's of things restart and hangs VS for me).


Feature Request: Random string from a list

Hello:
Can you add a function when given a slice of strings, will return one of them at random? Suppose the new function signature looks like String(stringList ...string) string. Then, one of the strings in the given list is returned at random.
Here is an example invocation:
myString := randomdata.String("foo", "bar", "baz")

Thank you,
Evan McClure

That looks like it could be useful. Do you have a usage example and can you open a PR?


remove rzmanta host configs....

...when no longer needed, which I think is now.

@white238 this issue can be closed, correct? If so, please do.

I guess "and"'s don't when you say you close a PR in the comments.


add: added minimap in canvas

Fixes #59
Describe the changes you have made in this PR -
Added minimap in canvas.
Screenshots of the changes (If any) -
https://user-images.githubusercontent.com/96587705/223432792-d01dbdbd-286c-451a-b954-d94c6eda8078.mp4

@devartstar can you review this?


remove _select_fields

remove _select_fields

Update the database model by removing serializing query results, or it will conflict with our routes which already include the serialization work.
Update related tests.


Script fails if run from a folder with spaces in the name

Reported on Reddit:
https://www.reddit.com/r/exchangeserver/comments/40ujp8/first_beta_of_exchange_analyzer_is_available/
Have not repro'ed yet.

Fix is to escape spaces in the path:
        $command = "$($MyDir)\Tests\$($Test).ps1" -replace ' ','` '
        $testresult = Invoke-Expression -Command $command

But given repeated use of $MyDir it may be better to do that once right at the start.
$myDir = Split-Path -Parent $MyInvocation.MyCommand.Path

Replace with
$myDir = $PSScriptRoot -replace ' ','` '

Second option breaks other cmdlets like Test-Path, so fix will need to be first option - escape the spaces in command path prior to running Invoke-Expression.

Fix has been merged to development branch for inclusion in next release.


lntest/node: persist network subscription state across restarts

In this PR, we modify the test harness to persist the state of prior subscription events across restarts. @offerm discovered that the testSwitchCircuitPersistence fails probabilistically, depending on which node established the connection after a restart.
The test only seemed to fail whenever the restarted node connects successfully. Since a topology update is ignored if we detect a duplicate, after restarting this event will not be replayed to any SubscribeChannelGraph clients.
Thus after a restart, a node would not deliver another event, even though it had already seen the channel. In our testing harness, we currently wipe the state of subscriptions during restart, since the maps for tracking prior updates were not tied to the HarnessNode struct. The fix is then to keep these indexes on the HarnessNode, instead of in the local scope of the subscription client, that way the client can "remember" updates it received prior.
Resolves #1496 and closes #1730.

Hi @cfromknecht Happy to help.
I'm not sure how this PR solves the problem. Can you please explain.
I think this is an implementation problem and not a test infrastructure issue.

The test you reproduced fails because Bob doesn't report knowing about his own channel with Alice, which is created before the restart. Thus the graph subscription is delivered before Bob is restarted. After a restart, we won't send out a duplicate for the same channel, so the test reports that Bob doesn't know about the channel. This is fixed by having the test remember that Bob received the update before shutting down.

Could it also be that #1730 didn't recreate the actual scenario, but instead triggers a similar error in the integration tests?

As there was no restart in the test previously

#1730 recreate the same problem.
What do you mean by "no restart in the test setup"?

#1730 adds a restart right after making the Alice->Bob channel, which causes the test to lose state about what events it's already received. This restart is not present in master, so I'm suggesting the root cause may be different

#1730 recreates the same error, which doesn't necessarily mean it reproduces the same issue

1730 reproduce the error, not the exact scenario.
I have seen this happened in a few tests.
Also explained in #1496 the reason for it.
This is a code problem and not a test problem. I can easily reproduce it manually.

Are you able to reproduce it without a restart?

I can try to reproduce the exact same scenario of #1496 if you like.
Note that I added a restart to make sure the connection between Alice and Bob will be created in the problematic direction. Without this restart, the direction of the connection is random (may be from a previous test) and you will see the problem only from time to time (when the connection direction is problematic). This is why it is so challenging to reproduce.

Also note that when the test is starting Alice and Bob are already connected (and sometimes have a channel between them).
I can probably reproduce it by placing the restart in the test prior to the fail one.  There are many restarts of Bob and Alice and if the test starts when the connection is in the wrong direction, it will fail (even without a restart)

I moved the restart to the very top of the test, and now the tests passes reliably. Can you confirm that this happens for you?

Will try to do tomorrow. Need some sleep time. Late here.

fwiw, i ran this test 300 times in isolation and it never failed. perhaps it is triggered by entering some state in the prior test?

@cfromknecht I Played with the test a bit and here are my conclusions:

I couldn't work on #1493 error (pointed from #1496) - The logs are already lost.

moving the port and restart to the top of the test will not fail the test. The reason is that at the top of the test there is no channel between Alice and Bob. After the restart nor Alice nor Bob attempt to restore the connection between them. When the test setup the channel between Alice and Bob, Alice will use the "new" port to connect to Bob and there will be no issue.

Running the test testSwitchCircuitPersistence with port and restart produces a failure every time, even if running in an isolated environment (single test).

Managed to reproduce the same problem also in testSwitchOfflineDelivery (that was easy since these 2 tests are basically the same up to the point of failure).

The EnsureConnected has no impact related to the problem. I removed it from the{ setport, restart, ensureconnected} block and the failure is still here.

Removing the block few lines down (see PR) to let Alice<->Bob channel setup complete made no difference.

@offerm

I couldn't work on #1493 error (pointed from #1496) - The logs are already lost.

Yeah unfortunately they get cut off for Alice and Bob towards the end

The EnsureConnected has no impact related to the problem. I removed it from the{ setport, restart, ensureconnected} block and the failure is still here.

This makes sense, Bob should try to establish a persistent connection on start up with the last known address.

Running the test testSwitchCircuitPersistence with port and restart produces a failure every time, even if running in an isolated environment (single test).

The reason is that at the top of the test there is no channel between Alice and Bob

Removing the block few lines down (see PR) to let Alice<->Bob channel setup complete made no difference.

Right, though these are caused by what i'm pointing out in this PR. If a channel is created before restarting Bob, then bob.WaitForNetworkOpen will lose all state about prior events and those updates won't come through after the restart as they would be duplicates.
By making those carry over across restarts, this PR proves that all notifications are getting delivered, even with the restart in place. I'm saying the test framework would need modification in order to properly check if channels were opened withRestartNode as placed, aka, anywhere between creating Alice->Bob and bob.WaitForNetworkOpen. With such a fix, placing a restart there does not trigger any bugs because we are properly tracking updates before and after the restart.

@cfromknecht I understand better now. Thanks
I didn't get it that WaitForNetworkOpen is not checking with the node but relies on the test infrastructure.  Did you consider to replace it with describegraph rpc call? The graph should be similar for all nodes hence easy to check with the current implementation.
I would also consider to add a check at the begining of the test[s] to make sure that the network is according to the state we think it is. I have seen cases when channels are left open accross tests and causing failures like htlc mismatch (we count 5 htlcs in all channels not just the test channel).
Anyway, once this is merged I will try to play with the tests again.  I think this is not the only problem that causes this test to fail randomly.  I'm also spending some time on #1632 which failed in the same test but for a different reason.  Looks really bad. You may want to have a look, specially at Alice's log:

2018-07-24 11:01:54.636 [ERR] LTND: unable to lookup witness: no witnesses
2018-07-24 11:01:54.636 [ERR] LTND: unable to lookup witness: no witnesses
2018-07-24 11:01:54.636 [ERR] LTND: unable to lookup witness: no witnesses
2018-07-24 11:01:54.636 [ERR] LTND: unable to lookup witness: no witnesses
2018-07-24 11:01:54.636 [ERR] LTND: unable to lookup witness: no witnesses

I will update #1632 if/when I have findings.
Thanks for your help!
Somehow related, I suggest you give attention to #1588

Promoting to P2, as this will resolve some flake issues we are seeing.
Should be ready for merge after a rebase! (and one more LGTM)

@halseth rebased!


Handshake occurs on each connection

When using serve and connect, repeated requests result in multiple handshakes, even when both the client and server settings have a session manager set. Why is TLS session not being resumed?
Code excerpts:
clientSettings :: Credential -> IO ClientSettings
clientSettings cred = do
    mgr <- newSessionManager defaultConfig
    let shared = doShared { sharedSessionManager = mgr, ...}
         cparams = (defaultParamsClient addr empty){ clientShared = shared }
         initSettings = makeClientSettings ("foo","bar") (Credentials [cred]) mempty
    return $ updateClientParams (const cparams) initSettings

serverSettings :: Credential -> IO ServerSettings
serverSettings (cert, _) = do
    mgr <- newSessionManager defaultConfig
    let shared = doShared { sharedSessionManager = mgr, ...}
          sParams = def { serverShared = shared }
          initSettings = makeServerSettings cred Nothing
    return $ updateServerParams (const sparams) initSettings

startServer cred = do
  sets<- serverSettings cred
  serve
        sets
        (Host ipaddr)
        (show port)
        (\(ctx,_) -> consume ctx)

clientSend cred msg = do
  sets <- clientSettings cred
  connect sets (Host destAddr) (show destPort) $ \(ctx,_) -> send ctx msg

Each call to clientSend results in a new TLS handshake.

@crockeea sorry I didn't reply before, but I missed the notification from GitHub.
I'll take a look at this as soon as possible.

bump

Hi! I think there were some recent changes in the 'tls' library that may
help with this issue. I'll take a look as soon as possible :)
On Fri, Jul 26, 2019, 21:07 crockeea<EMAIL_ADDRESS>wrote:

bump
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/k0001/network-simple-tls/issues/14?email_source=notifications&email_token=AAAAZZWUAIKXSNNVTDKZTK3QBM4NLA5CNFSM4G4QXJYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD25KI5Q#issuecomment-515548278,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAAZZXNRK6P5ZMWEDVIASLQBM4NLANCNFSM4G4QXJYA
.

This has been implemented in network-simple-tls-0.4.
Which, by the way, makes so minor but breaking changes to the API types https://hackage.haskell.org/package/network-simple-tls-0.4/changelog


[WIP] *(cdc): try unified DML library

What problem does this PR solve?

Issue Number: ref #3242
What is changed and how it works?
Check List
Tests

Unit test
Integration test
Manual test (add detailed scripts or steps below)
No code

Code changes

Has exported function/method change
Has exported variable/fields change
Has interface methods change
Has persistent data change

Side effects

Possible performance regression
Increased code complexity
Breaking backward compatibility

Related changes

Need to cherry-pick to the release branch
Need to update the documentation
Need to update key monitor metrics in both TiCDC document and official document

Release note
`None`.

/run-dm-integration-test

/run-integration-test

/run-integration-test

/run-integration-test

CDC's integration test passed https://ci2.pingcap.net/blue/organizations/jenkins/cdc_ghpr_integration_test/detail/cdc_ghpr_integration_test/9573/pipeline
I'll refine the code and unit tests soon

/run-integration-test

/run-integration-test

/run-integration-test

/run-integration-test

/run-integration-test

/run-verify

/cc @liuzix @amyangfei @maxshuang @hi-rustin
I'll check and remove some TODO comment soon and I think it's OK to review currently

Now I think in this PR it's too late to convert RowChangedEvent into the strcuture of library, at least it should be moved prior to causality. A good place maybe dispatchAndExecTxns. I'll work on it later.

/hold

replaced by https://github.com/pingcap/tiflow/pull/7548


USB CDC detect dis-/connect Events (IDFGH-6065)

Currently, there are are no dis-/connect events for usb cdc. Checking DTR/RTS is not a reliable way to detect usb dis-/connects, since many tools, including esptool.py, make non-standard use of them. This means there is no definite, unambiguous way to differentiate a dtr/rts toggle from a dis-/connect. Hence any call to tinyusb_cdcacm_write_flush(...) while the USB is disconnected, silently hangs. Using a timeout isn't a reliable solution, because it still causes hangs until the timeout is triggered, which would require very small values for it, but there are cases where larger timeouts are necessary under the assumption that the usb is still connected. Hence timeouts are also not a reliable/unambiguous way to detect USB disconnects.
Optionally, an additional esp-idf function that when called, returns a value that indicates USB connection status, would be a good idea.

Linking the related upstream issue: https://github.com/hathach/tinyusb/issues/482

TinyUSB does provide disconnect events for USB... the issue is simply that esp additions to CDC-ACM don't pass these on. One can manually register for those events though, look into components/tinyusb/tinyusb/usbd.c.

got the same issue. I found unplugging event in usbd.c, but it never trigged.

Upon closer inspection of usbd.c, and seeing the line 583:

if (tud_suspend_cb) tud_suspend_cb(...);

I realize why defining tud_suspend_cb works as a solution. Further testing also revealed DCD_EVENT_UNPLUGGED is never triggered because of reasons you mentioned above. The first time I looked at the code in the past, I just assumed since they are there, they get triggered. I see now this assumption was false. thx for the tip. Still, recieving DCD_EVENT_SUSPEND and DCD_EVENT_BUS_RESET are close and useful enough. But there is no assignable callback for it, so something like:

if (tud_reset_cb) tud_suspend_cb(...);

would also be useful. Also, as a suggestion for the future when unifying the callback system, wouldn't the default event loop be ideal for this purpose? thx anyways. I'll close this for now since it contains enough information for others to move forward and prevent unwanted blocking when the usb cable is unplugged.

I was investigating the same thing these days. I found checking tud_cdc_n_connected reflects the correct state of whether the CDC port has been opened or not.


Works: Subject and genre tags

The problem: We think that...
Subjects and genres are not clear that they are tag-like
Therefore we hypothesize that...
If we make them more taggy, more people will use them as search aids
As measured by...
The amount of following the tags from work pages will increase
Acceptance criteria: we are right if...
TBD

Done by @davidpmccormick and moved on board, so closing here.


SAA-1582: Migrate activity location user description rather than the location code

Fixes the following:

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

Project coverage is 86.91%. Comparing base (0934e64) to head (8c2ad85).

Additional details and impacted files
@@             Coverage Diff              @@
##               main     #834      +/-   ##
============================================
- Coverage     86.91%   86.91%   -0.01%
  Complexity     3575     3575
============================================
  Files           369      369
  Lines         12489    12484       -5
  Branches       1033     1033
============================================
- Hits          10855    10850       -5
  Misses         1165     1165
  Partials        469      469

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


support login

i find the project https://github.com/linweiyuan/go-chatgpt-api can support login api。

this project had support?

Hi. I won't support it here because of rate limits (~20 accounts per 10 minutes)
You can find my reverse engineering of auth here: https://github.com/acheong08/OpenAIAuth (No cloudflare no matter the IP)


non alphanumeric node types

I'm pretty new with rust but I have plenty experience with other languages AST and I'm noticing that, if I iterate descendants directly using children property, for the following code:
pub type __darwin_size_t = ::std::os::raw::c_ulong;

The following ast is generated:
{"type":"source_file","children":[{"type":"type_item","children":[
  {"type":"visibility_modifier","children":
    [{"type":"pub"}]},{"type":"type"},{"type":"type_identifier"},{"type":"="},{"type":"scoped_type_identifier","children":[{"type":"scoped_identifier","children":
 [{"type":"scoped_identifier","children":[{"type":"scoped_identifier","children":
    [{"type":"::"},{"type":"identifier"}]},{"type":"::"},{"type":"identifier"}]},{"type":"::"},
    {"type":"identifier"}]},{"type":"::"},{"type":"type_identifier"}]},{"type":";"}]}]}

And as you can notice there are node for which their types are are ':', '=', '::', ';'
Is this OK? I read that a convention is to ignore types starting with underscore, so in this case is not clear if I should ignore or is an issue.
IMO these nodes are not ignorable since they add important semantics to the program and  I would be loosing information or if not I think without these it will be harder to figure it out.
Again, I'm completely new in rust syntax but in other language they tend to name these kind of node Tokens, like ColonToken. In TypeScript there is even one called "DotDotDotToken" or "OpenTagGreaterThanToken".
Thanks, and sorry if I'm completely wrong about this and is not an issue at all, great project!

there are nodes for which their types are ':', '=', '::', ';'
Is this OK?

Yeah, that's the expected behavior. A token with type: "::" represents (as you might guess) the :: token. This section of the docs might be helpful.
In particular, nodes have a property called named that indicates whether they were given a name in the grammar or not. Most often, nodes that represent simple tokens like :: are not named, and their type property corresponds directly to their string value.

Is this OK? I read that a convention is to ignore types starting with underscore,

That concept isn't relevant to you if you're using a parser. That's an API when you're defining a grammar: you can mark named rules as private if you prefix their names with an underscore. Then they will not show up in the tree at all.
An example of that is the _declaration_statement rule in the Rust grammar. It is used in the grammar for grouping and parsing purposes, but notice that you did not see it in your syntax tree. Does that make sense?

An example of that is the _declaration_statement rule in the Rust grammar. It is used in the grammar for grouping and parsing purposes, but notice that you did not see it in your syntax tree. Does that make sense?

Yes it does, and is more comfortable than long syntax kind names. Sorry I mess that in the docs and
. Now I'm seeing seeing the same pattern in other  languages.
Recently I was playing a lot with antlr4 and ported to  JS and normalized the output of node visitors to build ASTs. This is WIL (just a couple of weeks old, but has many languages  "AST parsers":
https://cancerberosgx.github.io/demos/univac/playground/
As you said in the docs, I had to post process the output given by node visitors (which is the only way to extract something similar to an AST) and remove nodes matched by auxiliary grammar rules[0]
Grammars were taken from antlr4 grammars project https://github.com/antlr/grammars-v4 . I think that, although those are not designed to generate AST, it could be very helpful for a first approximation. Some of them are taken from official projects / compilers / interpreters and don't need much post processing to deliver an acceptable AST or at least good starting points for new parsers.
Will play a bit more with this library and see if something is missing here that I can contribute with. I think grammars for R and smalltalk are official.
BTW, I wonder if this project has any preference on languages? For example, antlrs  have grammars for things like assembler, makefiles, UTF, unicode, sass, less, and very old languages like logo, basic, fortran. cobol, or things like SQL/graphQl...
Thank you !
[0]  --  see redundantTypes have the types I removed for each lang


calicoctl shows "unknown" for ASN.

On a standard kubeadm install using Calico v3.0
{code}
ubuntu@casey-crc-kubeadm-kubeadm-master:~$ calicoctl get nodes -o wide
NAME                               ASN         IPV4             IPV6
casey-crc-kubeadm-kubeadm-master   (unknown)   <IP_ADDRESS>/32
casey-crc-kubeadm-kubeadm-node-0   (unknown)   <IP_ADDRESS>/32
{/code}
Expected Behavior

ASN shows up as "unknown" when it should really show up as the global ASN, or something that indicates it's inherited from the global ASN.
Current Behavior

Shows up as unknown.
Possible Solution

Steps to Reproduce (for bugs)

Context

Your Environment

Calico version
Orchestrator version (e.g. kubernetes, mesos, rkt):
Operating System and version:
Link to your project (optional):

@caseydavenport is this related to the phenomenon I am seeing on my three clusters?
On the dev cluster I sort of installed Calico manually and it shows this:
kvm336:~# calicoctl get bgpconfig
NAME      LOGSEVERITY   MESHENABLED   ASNUMBER
default   Info          true          64512

kvm336:~# calicoctl get nodes -o wide
NAME     ASN       IPV4            IPV6
kvm335   (64512)   <IP_ADDRESS>/24
kvm336   (64512)   <IP_ADDRESS>/24
kvm337   (64512)   <IP_ADDRESS>/24
kvm338   (64512)   <IP_ADDRESS>/24

So, there is a default bgpconfig.
But on two other clusters, I just removed the old canal config and applied the pure calico-node config and there is not default bgpconfig and no ASN shown:
s239:~# calicoctl get bgpconfig
NAME   LOGSEVERITY   MESHENABLED   ASNUMBER

s239:~# calicoctl get nodes -o wide
NAME     ASN         IPV4             IPV6
h1355    (unknown)   <IP_ADDRESS>/24
h504     (unknown)   <IP_ADDRESS>/24
h5345    (unknown)   <IP_ADDRESS>/24
kvm334   (unknown)   <IP_ADDRESS>/24
s234     (unknown)   <IP_ADDRESS>/24
s237     (unknown)   <IP_ADDRESS>/24
s238     (unknown)   <IP_ADDRESS>/24
s239     (unknown)   <IP_ADDRESS>/24

Am I "missing" the defautl bgpconfig, or is this only cosmetic?

Nevermind, I found these docs and added a default bgpconfig manually, and now the display seems correct.

@towolf yeah, the problem here is that there is a default written into the code, and a default that can be set clusterwide.
calicoctl doesn't display a value when the code default is in use, but will show a value when a BGP config has been explicitly set.

Fixed!


add setLocation function for fbsimctl

add setLocation function for fbsimctl, such as:
./fbsimctl xx-xxxx-xxxx-xxx-xxxxx setLocation 46 116

Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, please sign up at https://code.facebook.com/cla - and if you have received this in error or have any questions, please drop us a line at<EMAIL_ADDRESS>Thanks!

Logic looks sounds, mostly indentation and naming that needs fixing.


Handle overflow in toolbars

Our toolbars currently just hide any overflow, so toolbar items become completely inaccessible.
Scrollbars don't really make sense in a toolbar, so I think we should instead move the invisible items into a drop-down menu. BlueprintJs provides this component, which seems like it would provide the exact kind of functionality we would want here: https://blueprintjs.com/docs/#core/components/overflow-list

👍 agreed this has been a long-outstanding gap. ExtJS had a similar approach where overflow items would trigger a little V menu button.

That overflow list looks pretty awesome -- can we just use that?

Finally got round to wrapping up the branch I started on this last week:
https://github.com/xh/hoist-react/pull/1719
https://github.com/xh/toolbox/pull/369


Fix async method lacks await warning

This PR fixes the following warning during building:
App.razor(51,35): warning CS1998: This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread. [/bin/staticsites/ss-oryx/app-int/NCrontabTester.csproj]

Build seems to be failing due to missing API token.

I guess when a pull request is made from a forked repo, the Azure Static Web App action doesn't pick up the secrets.
The change has been merged in.


getSecureRandomNumber will return min - 1 for big numbers

I've didn't encountered this problem in real life. But I would like to report it anyway
Problem
This code throws an exeception for bits size more than 53. But actually it should throw bit size more than 31
Why?
Because bits manipulations with JS number are restricted by 32 bit integer type. Left operand cast to integer happens every time when "|", "&" or "^" is applied to it.
for (let bits = 30; bits < 40; ++bits) {
    console.log(bits, (Math.pow(2, bits) - 1) & (Math.pow(2, bits) - 1))
}

So for a big number this code will return min-1
numberValue = numberValue & mask; // Truncate = -1
if (numberValue >= range) {
  continue;
}
return min + numberValue; // min + (-1)

getSecureRandomBytes(bitsNeeded) I think should be called from bytesNeeded, because we iterate only first bytesNeeded elements


Clickhouse client results in groups – what does it mean?

I sometimes get results for a query run via clickhouse-client separated in groups

I was just curious what does it mean? Why are there multiple blocks with results?

Yes, blocks. Try:
select number from numbers(10);
select number from numbers(10) settings max_block_size=1;
select number from numbers(10) settings max_block_size=1 format PrettyCompactMonoBlock;

Oh I see. Thanks for quick response!


fix(ingressclass): somewhat duplicates #377 / fixes #499

What does this PR do?
Fixes #499
Motivation
https://github.com/traefik/traefik-helm-chart/pull/337#issuecomment-942111555
More

[X] Yes, I updated the chart version

Additional Notes
should test

This PR is not applicable in this current state.
@faust64 If you have the time, you can refresh it, take @ddtmachado  comments into account and re-open it.

Really? I've been refreshing that PR, and the parent one, for over a year.
If you want something from it, go ahead. I'm done here.

@faust64 Sorry, I didn't mean to offend you.
I see that you have opened multiple PRs in the past and I understand.
=> I'll prioritize your PRs and try to merge them.


updating the extra file with CR/LF changes

This was a weird issue. The file kept showing up as modified but the diff did not show any difference. Turns out it was the CR. The file must have been edited in a Windows app and so all of the LFs got changed to CRs: The issue is here: https://github.com/git-lfs/git-lfs/issues/1544. Basic the file gets modified by git bash whenever you sync to master.  Checked in the version with LF endings so this will stop happening.


Add VACUUM: Bloat - Insufficient VACUUM Frequency check

UnnecessaryTableGrowth uses a similar pattern as MissingIndex.
The docs doesn't have the solution section as it's in dynamic guidance generated in app side.

Applied reviews, ready for another 👀

Gonna actually merge this as the app side will be merged too. We can always come back and update if we want to.


Javascript File uses a Global view variable

Currently, the arcGisJsInterop.js file uses a global view variable to keep track of the map view.
https://github.com/dymaptic/dy-blazor-api-core/blob/98de2d7d0fa6c6e00317a0f636c4497156497718/src/dymaptic.Blazor.GIS.API.Core/wwwroot/arcGisJsInterop.js#L4
I believe that this makes it so that we can't have multiple map views, it is also kind of just asking for trouble I think (having a global variable for this). Can we make this so the reference is just passed back and forth for each function that needs it? Basically can we make all of these functions truly functional and not have any global mutation?

It is still effectively global though, it's more like a static instance.
I like this Guid idea. Could we centralize this even more and have an dyObjects dictionary and a couple of methods to get/set/delete them? I'm thinking since we are using Guids we could store all the objects in the same dictionary, and then in any JS interop code, we can get the object out of that central repository. That way we don't have to have different dictionaries for every type of object we need to store.

It is still effectively global though, it's more like a static instance.
Yes, that's true, it's static, can't have multiple instances.
Does dyObjects make more sense than separate views, graphics, etc.? I feel like named collections would be more clear, and I can only imagine a small handful of them.

I was leaning towards dyObjects as a generic solution for this problem. So that we don't have to create another list, etc. when some new item comes along. We can build a set of utility functions on the JS and C# (or maybe classes) side to handle all this and then we just call that/extend the correct base class and we magically have a connection between the C# object and the JS object.
If we do it as separate lists, we'll have to write code for each one, so I guess I'm asking if we can do this in a generic way that would be useful in the future, both for this API, but also just building blazor apps?

There is a lot of Blazor development that requires little to no JavaScript at all, and even more where object references would not need to be kept. This API is somewhat unique in that regards. Still, I will tinker around with a unified dictionary and see what I come up with for this.


Is access to mutable stateSession thread-safe?

Coordination methods will (most likely) be called from different threads. Therefore all access to mutable variables – like stateSession – should be properly guarded. Maybe change stateSession to an AtomicReference?

Sorry, I didn't notice the @volatile ;-)


Cannot pull docker image simplcommerce/nightly-build

Since 26.10 I can't pull simplcommerce/nightly-build image via docker.
STR:

run "docker run --name simplsite -d -p 5000:80 --link simpldb:simpldb simplcommerce/nightly-build"

Actual result:
Error received -
"C:\Program Files\Docker\Docker\Resources\bin\docker.exe: Error response from daemon: pull access denied for simplcommerce/nightly-build, repository does not exist or may require 'docker login'."

So I have tried with simplcommerce/ci-build and this works for me.
As I understand you should update documentation.

Updated http://docs.simplcommerce.com/en/latest/getting-started/
@ViacheslavMelnichenko  is that where you saw?


Transaction Net Usage Is Too High: 136 > 0

Hi,
It's been a while since I've used this wallet. Can someone please explain to me how to change my usage limit step by step? I need to send my EOS to an exchange.
Thanks!

Why is my net like this?

Seems this is not an EOSIO code issue. Probably want to discuss in https://eosio.stackexchange.com/

gotcha, appreciate the direction!


Fix some spelling issues in admin docs

This patch fixes some spelling mistakes in all the admin related docs.

This change is

@madhuri-rai07 needs rebase, needs CLA signing.

Please sign the CLA :)


UpdateCoordinator not honoring "start from" setting for code slot sensors

In your debug logs do you see anything that says something like Finished fetching keymaster data in 0.004 seconds (success: True) ?
If not, that'd be why they're unavailable.

Yes, but it´s pulling the wrong keyslots?
I have configured 5 slots from keyslot 10 and up, while debug shows that keymaster pulls 1-5
2021-11-02 16:50:38 DEBUG (MainThread) [custom_components.keymaster] Finished fetching keymaster data in 0.001 seconds (success: True)
2021-11-02 16:50:43 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 1 value: xxxxx
2021-11-02 16:50:43 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 2 value: xxxxx
2021-11-02 16:50:43 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 3 not enabled
2021-11-02 16:50:43 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 4 not enabled
2021-11-02 16:50:43 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 5 value: xxxxx
2021-11-02 16:50:43 DEBUG (MainThread) [custom_components.keymaster] Finished fetching keymaster data in 0.001 seconds (success: True)

Originally posted by @labanx in https://github.com/FutureTense/keymaster/issues/228#issuecomment-957940432

Updating this bug report, since there is a bit of info spread all over now.
Tested with pullrequest 250, the difference is that Keymaster stopped pulling the wrong slots (according to the debug log)
2021-11-03 15:35:46 DEBUG (MainThread) [custom_components.keymaster] Finished fetching keymaster data in 0.000 seconds (success: True)
2021-11-03 15:35:51 DEBUG (MainThread) [custom_components.keymaster] Finished fetching keymaster data in 0.000 seconds (success: True)
2021-11-03 15:35:56 DEBUG (MainThread) [custom_components.keymaster] Finished fetching keymaster data in 0.000 seconds (success: True)
2021-11-03 15:36:01 DEBUG (MainThread) [custom_components.keymaster] Finished fetching keymaster data in 0.000 seconds (success: True)

Compared to it pulling the first 5 slots before the patch
2021-11-02 16:50:38 DEBUG (MainThread) [custom_components.keymaster] Finished fetching keymaster data in 0.001 seconds (success: True)
2021-11-02 16:50:43 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 1 value: xxxxx
2021-11-02 16:50:43 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 2 value: xxxxx
2021-11-02 16:50:43 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 3 not enabled
2021-11-02 16:50:43 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 4 not enabled
2021-11-02 16:50:43 DEBUG (MainThread) [custom_components.keymaster] DEBUG: Code slot 5 value: xxxxx
2021-11-02 16:50:43 DEBUG (MainThread) [custom_components.keymaster] Finished fetching keymaster data in 0.001 seconds (success: True)

Some part of Keymaster is working  however, if i manually run the automations the pin get applied.
Please note that keymaster is not able to verify that the pin has been applied, so it seems to be related to pulling of the keyslots?

Zwave-js debug logs
2021-11-03T16:11:40.762Z DRIVER » [Node 031] [REQ] [SendDataBridge]
                                  │ source node id:   1
                                  │ transmit options: 0x25
                                  │ route:            0, 0, 0, 0
                                  │ callback id:      86
                                  └─[SecurityCCCommandEncapsulation]
                                    │ nonce id: 146
                                    └─[UserCodeCCSet]
                                        user id:   12
                                        id status: Enabled
                                        user code: 77668877

You can also see that the code slots are failing in HA