Something's wrong with your github repo!

Hey!  A clean git clone of your repo has unstaged changes which is breaking some things (including npm install).
:) 0 marguerite @ marguerite-1127 in ~/software
|  | $ g clone git@github.com:ariya/esprima.git
Cloning into 'esprima'...
remote: Counting objects: 14542, done.
remote: Compressing objects: 100% (15/15), done.
remote: Total 14542 (delta 2), reused 0 (delta 0), pack-reused 14524
Receiving objects: 100% (14542/14542), 47.79 MiB | 8.10 MiB/s, done.
Resolving deltas: 100% (9747/9747), done.
Checking connectivity... done.

:) 0 marguerite @ marguerite-1127 in ~/software
|  | $ cd esprima/

:) 0 marguerite @ marguerite-1127 in ~/software/esprima
| master | $ g st
 M test/fixtures/JSX/multiline-crlf-text.js
 M test/fixtures/comment/migrated_0011.js
 M test/fixtures/expression/primary/literal/string/migrated_0017.js
 M test/fixtures/invalid-syntax/migrated_0153.js
 M test/fixtures/invalid-syntax/migrated_0155.js
 M test/fixtures/invalid-syntax/migrated_0159.js

Coworker has pointed me at http://stackoverflow.com/questions/12205846/git-shows-random-files-as-modified-after-clone-cant-discard-them which seems to be compatible with the latest master commit

noticed in upstream repo: https://github.com/jquery/esprima/issues/1672

This seems to have been fixed with https://github.com/ariya/esprima/commit/e2e87cedeb17b4184bee9c1a0386074614dabf56


Run remote command after sync.

This PR adds the ability to run a remote command after syncing. It runs the configured command if remoteExecOnUpload is true.
See #13 and I also needed it to run a kind of "publish" script to compile my source.
NOTE: i don't know CoffeScript language. Feel free to modify the code and sorry if there's something weird in there.

Thank for your PR. Eventually I decided to write "Trigger" to run commands in different conditions in 0.7.0. For instance, compile coffeescript to javascript only when coffeescript files modified, and also put static files to cdn or other behaviours defined in .sync-config.cson

Hi all
Is this PR included in current version ? I need to use it; I tried to add remoteExecOnUpload and cmds in config but it didn't fired the command. Did I miss something ?
Thanks

@brunetton Per READme.md section Trigger, add "trigger" to your config file
Sample
trigger:
    "*": [
        "echo \'Every time you\\'ll see me\'"
    ]
    "coffee": [
        "echo Compile coffeescript to js ..."
        "mkdir -p js"
        "coffee -b --output js/ --compile coffee/"
        "ls js/|xargs -I@ echo \\t@"
    ]
    "sass/style.sass": [
        "echo Compile sass to css ..."
        "mkdir -p css"
        "sass --update sass:css"
    ]

You can also refer to the "SSH ControlMaster" part.

Thank you, I don't know how I missed it in Readme.
Le 5 juil. 2016 8:36 PM, "dingjie"<EMAIL_ADDRESS>a écrit :

@brunetton https://github.com/brunetton Per READme.md
https://github.com/dingjie/atom-sync/blob/master/README.md section
Trigger, add "trigger" to your config file
Sample
trigger:
"*": [
"echo 'Every time you\'ll see me'"
]
"coffee": [
"echo Compile coffeescript to js ..."
"mkdir -p js"
"coffee -b --output js/ --compile coffee/"
"ls js/|xargs -I@ echo \t@"
]
"sass/style.sass": [
"echo Compile sass to css ..."
"mkdir -p css"
"sass --update sass:css"
]
You can also refer to the "SSH ControlMaster" part.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dingjie/atom-sync/pull/28#issuecomment-230564225, or mute
the thread
https://github.com/notifications/unsubscribe/AAFRMkctfhocR-4faQHzhdjGLSIZZrIcks5qSqQ0gaJpZM4Hc95N
.


JSON should not preserve invalid decimal

Per customer report:

"Incorrect representation of certain decimal numbers in JSON format #188 - If a resource is created with a numeric field with value of '.5' (without quotes), the JSON representation of this resource should have the numeric field as '0.5' (without quotes). This is in accordance with the JSON specification (https://tools.ietf.org/html/rfc8259#section-6).
The actual behavior is that SmileCDR preserves the source format and thus generates an incorrect JSON. An example resource on the public server:
https://try.smilecdr.com:8000/MedicationRequest/json-test-1?_format=json"

Actual Behaviour:
When the parser is parsing a resource like the one listed above, it sees "value": .5, and preserves it exactly.
Expected Behaviour:
The parser should report this issue to the parser error handler, and:

If the LenientErrorHandler is in use, it should auto correct the value to 0.5 in order to be valid and a warning message should be logged
If the strict error handler is in use, the parse should fail

Please start by reproducing this issue via a test in JsonParserR4Test. Once this is fixed, please verify that the same behaviour happens when using the XmlParser.

@jamesagnew I wrote the simple test and it surprisingly passed. If I set the value to .5 for the MedicationRequest the parser shows me 0.5 as expected behavior. I am not sure but looks like the HSSC is using DSTU3 because JSON example in the ticket looks different, I’ve tried to run the test for JsonParserDstu3 as well and it also passes.
This is my test:
@Test
public void testEncodedResourceWithIncorrectRepresentationOfDecimalNumber() {
MedicationRequest mr = new MedicationRequest();
Dosage.DosageDoseAndRateComponent component = new Dosage.DosageDoseAndRateComponent();
component.setDose(new SimpleQuantity()
.setValue(.5)
.setUnit("{tablet}")
.setSystem("http://unitsofmeasure.org")
.setCode("{tablet}"));
Dosage dosage = new Dosage();
dosage.addDoseAndRate(component);
mr.addDosageInstruction(dosage);
String encoded = ourCtx.newJsonParser().setPrettyPrint(true).encodeResourceToString(mr);
ourLog.info(encoded);
mr = ourCtx.newJsonParser().parseResource(MedicationRequest.class, encoded);
assertEquals(BigDecimal.valueOf(0.5), mr.getDosageInstructionFirstRep().getDoseAndRateFirstRep().getDoseQuantity().getValue());
}
4:29
this is result of pretty print:
"resourceType": "MedicationRequest",
"dosageInstruction": [
{
"doseAndRate": [
{
"doseQuantity": {
"value": 0.5,
"unit": "{tablet}",
"system": "http://unitsofmeasure.org",
"code": "{tablet}"
}
}
]
}
]
}

James response:

in java, .5 and 0.5 are equivalent
this is an issue with string processing, not with java source parsing

You need to pass a string to the parser, not a java object

This test doesn't work in R4 class, only in DSTU3. I see the issue now, thank you. Just for your information, I've created the test in DSTU3.


Map POI search results should support a full results view

Similar to the Spotify full search results, the Custom Map search results screen should have a similar full results page. The suggestions sidebar in ID5 now only shows a single line.

Fixed with 058f0ad and refined by 990d6f7 and ab927b0


Add extension test infra with a simple initial page extractor test.

Is the third time the charm? Probably.

I think the prettify change I landed in between creating the PR and getting approval is causing auto-merge issues. I think I've got my master sorted out so it's able to merge with the upstream now, and theorize that means this will also be ok now.

LGTM, but still looks like conflicts. I muddled a situation once like this before (maybe?), let me know if you want to pair up on this once you're online.


Create DockerFile / docker-compose

Acceptance criteria:

[ ] DockerFile
[ ] docker-compose w/ SQLite

I'd say let's try to use postgres inside the docker-compose since we'll probably deploy somewhere which uses postgres

Issue updated from SQLite to Postgres.

submitted a PR for this


further reduce the libguestfs-tools image size

Libguestfs-tools image is quite huge and it slows down the build and
push process. Further shrink the image.
Signed-off-by: Alice Frosi<EMAIL_ADDRESS>
What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

None

/lgtm
/approve

/retest


YoutubeResolveStrategy | Getting link

It's getting stuck in YoutubeResolveStrategy | Getting link for 5 minutes then it adds the song to the playlist and 1 more minute for the bot to join the channel and start playing song
I have FFmpeg and youtube-dl installed (and yes i tried reinstalling both and restarting my computer nothing worked)

Are you on 1.6

Yes

I'd just say you're box is too slow. Making nadeko work properly seems imposible on free aws tier.


fix consonant clusters

I have added some fixes which address #50 .

[x] Move unused files in /etc/ to etc/archive/
[x] Add some fixes to pre-nasalized stops
[x]  Add some fixes for y/j

I tried to keep the impact as minimal as possible, by adding as much phonological context as possible. I have also focused on the clusters that seemed most drastic (C>4). With the added changes, I think we could start the release. But it would be great if you could double-check on the changes and their implications @tihomirrangelov . I have also tagged @SimonGreenhill and @antipodite to have more eyes.

Awesome, thanks for your help with this @tihomirrangelov !

@FredericBlum -- can you add Timo's changes to the main abvd lexibank https://github.com/lexibank/abvd dataset too please? the languages are the same (as for the abvd_philippines)

The CLTS-mapping over there seems to work differently, since there is no orthography profile file. So I don't think adding the changes is possible. I'll have to leave that to the ABVD team I guess.


[Gallery] Homepage gallery bottom text

Text above "View gallery" button should read "Visit gallery for more inspiration"
Firefly:

Franklin:

Fixed : https://main--firefly--adobecom.hlx.live/


Roll back poh

Note: I consider this solution controversial. This PR is intended to aid a discussion on the right way to fix this issue.
Problem
Nodes that respect grace ticks kind of get screwed by missing out on their leader slots
Summary of Changes
Roll back PoH to the start of a leader's set of slots once it determines it is time to be leader.

Rather than this route, I think we should remove grace ticks entirely and just observe which shreds we've received from the previous leader (maybe gossip votes too?) to decide whether to delay our block a bit


[Feature] Align snapshot and checkpoint in split enumerator and source

Search before asking

[X] I searched in the issues and found nothing similar.

Motivation
subtask for #1105 , @liming30 I create this issue for alignment between split enumerator and source reader, please feel free to create subtask for it.
Solution
No response
Anything else?
No response
Are you willing to submit a PR?

[ ] I'm willing to submit a PR!

@JingsongLi @FangYongs I have added related tests, please review it if you have time.


Add commands prefix

Changed hardcoded commands to use variable prefix #22

Hi @3t8, thank you for your contribution, but it looks like this issue was assigned to @techsnap just a few minutes ago :(
I will have to close this PR, as this was not assigned to you. The next time you start to work on a PR, make sure to leave a comment on the issue, so you can be assigned to the issue.


Autoindent line does not work on editor.action.insertLineAfter

VSCode Version: 1.7.1
OS Version: MacOs Sierra

Steps to Reproduce:
On this situation :

if i press CMD+RightArrow then Enter i got :

But if i directly hit CMD+Enter, it trigger the editor.action.insertLineAfter which give me :

And it does not trigger the auto-indentation for the previous line. Which reduce the interest of this command.

@jrieken I believe @DavidBabel wishes that cmd+enter should trigger format on type.

@alexandrudima exactly


Apache configuration improvements

Verify configuration with httpd -t
Some minor editing of option descriptions
Make Event MPM the default on v2.4

@edolstra any objections? The config check can be turned off and Event is good starting with kernel 2.6...

Did you try PHP with mpm? It's a different setup, I guess this is going to break every php deployment.

Hmm I see, mod_php is threadsafe nowadays but extensions may not be... http://serverfault.com/questions/383526/how-do-i-select-which-apache-mpm-to-use
So I propose we force the event model to be prefork when mod_php is enabled?

@wmertens no it's just completely different. mpm event is similar to how you setup nginx with php using fpm and external servers. It doesn't use mod_php.

@lethalman if one is not using mod_php there is no problem, that works fine
with event and worker…
On Tue, Aug 25, 2015, 10:43 lethalman<EMAIL_ADDRESS>wrote:

@wmertens https://github.com/wmertens no it's just completely
different. mpm event is similar to how you setup nginx with php using fpm
and external servers. It doesn't use mod_php.
—
Reply to this email directly or view it on GitHub
https://github.com/NixOS/nixpkgs/pull/9435#issuecomment-134524953.

--
Wout.
(typed on mobile, excuse terseness)

Here's how PHP should be configured on Apache v2.4: http://wiki.apache.org/httpd/PHP-FPM
I think enabling PHP on the service should configure that instead of mod_php.

I just realized that choosing the MPM module based on the version rebuilds the man pages when changing the package version so I took that out again.
@edolstra the test now works when the user doesn't exist yet, good catch :)

Yeah we should definitely go for using php-fpm only and ditch mod_php if possible. PHP internals has thought about deprecating mod_php but it sadly still is used too often to get rid of it.. I'll have a look at freshening up the fpm module to be configurable in a more human-friendly way soon and try to get support for that into apache by flicking over a simple switch.

Note that we used to check the Apache configuration file, but we got rid of it because it was too much trouble: 4a95f8996b11ca9876e24a37d4b521925a1c33bf

Another reason for having an out… looks like I need to fix ssl key testing
in sandbox :-)
On Wed, Aug 26, 2015, 11:00 Eelco Dolstra<EMAIL_ADDRESS>wrote:

Note that we used to check the Apache configuration file, but we got rid
of it because it was too much trouble: 4a95f89
https://github.com/NixOS/nixpkgs/commit/4a95f8996b11ca9876e24a37d4b521925a1c33bf
—
Reply to this email directly or view it on GitHub
https://github.com/NixOS/nixpkgs/pull/9435#issuecomment-134905047.

--
Wout.
(typed on mobile, excuse terseness)

(triage) @wmertens status?

Hmm totally forgot about this one. IIRC the problem was that when testing the configuration it needed to access the network for verifying SSL certificates. I suppose that could be fixed by stripping them out before testing, or at least filter out errors due to SSL certificates.
Problem is that I'm not using Apache at the moment. Anybody up for completing this?

It is indeed too bothersome to have this.


Add org.w3/PerformanceNavigationTiming/jsonschema/1-0-0 close (#1294)

Add PerformanceNavigationTiming schema which aims to model values from the Navigation timing specification.
close (#1294)

@jethron The fixes for server timing are up and we have added a mitigation for the negative values bugs (minimum values). If you think it is fine, I will be adding this on #1258

Added on #1258


Proposed 0.32.0-rc2

[Current coverage][cc-pull] is 69.79%

Merging [#1754][cc-pull] into [develop][cc-base-branch] will increase coverage by 0.38%

@@            develop      #1754   diff @@
==========================================
  Files           856        857      +1
  Lines         62543      67573   +5030
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits          43411      47163   +3752
- Misses        19132      20410   +1278
  Partials          0          0

[][cc-pull]

Powered by Codecov. Last updated by [5dd8f28...138cadc][cc-compare]
[cc-base-branch]: https://codecov.io/gh/ripple/rippled/branch/develop?src=pr
[cc-compare]: https://codecov.io/gh/ripple/rippled/compare/5dd8f282905c70d92790fde3f1d384e43c925ff3...138cadc01cf82f124f81f826943cbae328ece97d
[cc-pull]: https://codecov.io/gh/ripple/rippled/pull/1754?src=pr


Cisco Meraki Events via REST API overutilization and data duplication

Hi team
I understand that this connector is in preview but we are facing an issue and would like to report it.
We are seeing the getOrganizationConfigurationChanges running ~21000 times per hour
This is resulting in excess data being logged in ASimWebSessionLogs table
We are also seeing changes from are being retrieved by the connector using the getOrganizationConfigurationChanges function are duplicated thousands of times in the ASimAuditEventLogs table.
Please can we get some help with this - I will likely need to disconnect the connector.
Thank you

Hi @shaunyb93,
Thanks for flagging this issue, we will investigate this issue and get back to you with some updates by 26 June 2024. Thanks!

@v-rusraut has there been any progress on this issue?
Thanks

Hi @shaunyb93, Sorry for delay in response. Just want to know, after clicking on disconnect button, the connector status still show as connected? Did you tried it to disconnect the connector by that option? -

Thanks!

Hi, Yes I have disconnected the connector as it does not work properly.
We need to understand this part of my request before we reconnect it:
We are seeing the getOrganizationConfigurationChanges running ~21000 times per hour
This is resulting in excess data being logged in ASimWebSessionLogs table
We are also seeing changes from are being retrieved by the connector using the getOrganizationConfigurationChanges function are duplicated thousands of times in the ASimAuditEventLogs table.
Thanks
Shaun

Any update here?
Thanks

Hey @shaunyb93, Still checking this issue with team, need some more time to investigate on it. Thanks!

In 24 hours the connector has called the meraki dashboard 700,000 times. It is causing other applications to rate-limit.

It is causing rate limiting both with itself and with other applications:

In the last 24 hours some records (not all) have been duplicated tens of thousands of times.

This application is not ready for production and needs to be investigated why the duplicates are occurring, I think your timestamping process probably isn't working as expected in the codeless connector.

Several events have also been duplicated tens if not hundreds of thousands of times (this is the exact same event with the exact same timestamp, not multiple similar events)

This needs to be addressed, it is costing us a large amount of wasted ingestion money and this connector is not ready for production, it appears its method of timestamping when the last events had arrived is not operating correctly

@JustinGrote Somewhat relieved that someone else is seeing the same issue. We had to disconnect the connector as it was just going crazy with duplication. The connector is marked as being in a preview state so I presume some bugs are expected but it seems really difficult to get any focus on a fix - 2 months and counting on this ticket...

Hi @JustinGrote and @shaunyb93, We are connecting with our concern team for this issue, and once we get any update from team, we will notify you. Thanks!

@shaunyb93 agreed, I tried to develop a codeless connector but they are such black boxes it's impossible to see what's going on, so I've been authoring an Azure Function to do this same thing instead.

Hi @shaunyb93 / @JustinGrote, We have received the response from our concern team for this issue, to verify the duplication, checking with you while requesting the API directly (using tool: Postman) with adding same definitions as mentioned into data connector like Time, as a result did you get the data duplication? Could you please check on this and let us know, so we can share this update with our team.
Connector API link-https://github.com/Azure/Azure-Sentinel/blob/master/Solutions/Cisco Meraki Events via REST API/Data Connectors/CiscoMerakiMultiRule_ccp/dataConnectorPoller.json
And to investigate on this issue our team required some access (like environment access) for which we are not authorized to provide. Kindly requesting you to raise support ticket in azure portal, so our support engineer can share the required information and access to the team.
Please let us know once if you raise support ticket case so we can close this issue from GitHub and this issue investigation and track will continue by our support team.
Thanks!

No duplication from the API, in fact I made my own Azure Function to ingest this same data and it works just fine with no deduplication and vastly less API calls.

@JustinGrote, Thanks for the response. We have shared this update to concern team.
@shaunyb93  / @JustinGrote, Please let us know once you open a support case. Thanks!

@v-sudkharat can you advise which team we should be raising this with? last time I tried to raise a support case for a Sentinel connector issue, Microsoft (the developer) advised they cannot assist and just point fingers at Cisco...

@v-amolpatil is the one who committed the solution, and has been doing other OMS/AMA migrations in his recent commit history.

Team, we would also like to report experiencing this issue as well. We are seeing 700,000+ requests a day which causes rate limiting issues with the Meraki REST API. Is there an eta on resolution regarding this bug? We are going to have to stop using the data connector until a bug fix is applied as its impacting other apps that are using the Meraki REST API.

Hi @shaunyb93 / @JustinGrote / @mferrellen, Please raise a support case with Data Collection team, so the ticket get transfer to our concern team. Thanks!

Hi @shaunyb93, Could you please confirm did you raise a support case? Thanks!

@v-sudkharat yes
MSFT SR#2408230030007650

Just found this thread and unhappy to report we're seeing the same thing after just setting this up this morning.
@JustinGrote - Any chance you could share that Azure function? I'd love to use that to tide us over until the connector can be fixed.

@Nico-WA I'm exploring with my company on that but it's currently company IP unfortunately. It also does a lot more than just the 3 categories the connector uses, it parses network events for wireless logons, 802.1x logons, eap logons, nbar blocks, cf blocks, and formats them all into ASIM using a DCR, and checkpoints the last log ingested into a blob so that future checks are resumed from that date.
Works great and far less API calls with no duplicate records. In an hour it was only ~800 or so API calls, and any rate limiting issues we were seing have completely disappeared.

@JustinGrote - Ah, got it. I understand. I may dive into that rabbit hole to do it from scratch. Fun! But I do hope the connector gets resolved sooner rather than later.

Thanks @shaunyb93 for open the case.

Hi everyone,
glad i've found something about this connector. I also experience the mentioned issue:
Thats roughly 24 hours running the Data-Connector

I have a question:
I am just interested in Security related Events like IDS and File Scanned. How do i configure the Connector just to poll those instead flooding me with Configuration-Changes? Is everything configured with the Functions "ASim*_CiscoMerakiV**"? I don't get it. Its a blackbox for me without any documentation

@Weeman257 it uses the new codeless connectors format and the code is on their Github, sadly the codeless connector (which uses the user agent SCUBA which I assume is a MS codename) is very black-box.
The only thing you could potentially do here is modify the data collection rule it uses and change the transformKQL to only    collect what you want. Note that if a transform rule filters more than 50% of the logs, anything above that it filters you still get billed for.

@JustinGrote Thats why i wanted to modify the queries instead of the Collection Rules :D to only pay for what i want to have. Sad story... So we have to wait on the fix for the duplicate injestion

Literally just got off the phone with Microsoft support about this - sad to report that it doesn't look like they've really even looked into the  issue at the moment so wouldn't hold breath on a fix... again, the connector is in a preview state so doubt any priority will be applied to fixing it

I will add some pressure :P

If worse comes to worst I'll discuss with my company for publishing our offering as a marketplace one for a reasonable fee, it works really well.

Hi @JustinGrote / @shaunyb93 / @Weeman257,
Apologies for the delay in response.
Our concern team has fixed this issue and raised the PR with corrections, the changes will get reflected in upcoming solution version.
we will notify you once the new solution version gets published into the content hub.
Thanks!

@v-sudkharat are you referring to this PR https://github.com/Azure/Azure-Sentinel/pull/11195 or something internal?

@JustinGrote, Yes,
@shaunyb93 / @Weeman257 / @JustinGrote. The solution has been live now, Kindly update your solution and let us know if your issue gets resolve.
Note: Please delete the existing data connector and then do the fresh installation/ update. Thanks!

Hi @shaunyb93, Could you please confirm the update resolves your issue?

@shaunyb93 , Thanks!
Closing this issue. If you still need support for this issue, feel free to re-open it any time. Thank you for your co-operation.

Hi everyone, i still have duplicates:

One Addition: The Connector maxes out the Calls per Second (10 per second) which leads to a response code of the meraki api (Code [429)]

@Weeman257 have you updated the solution and redeployed the connector as requested by @v-sudkharat ?

Per looking at the PR, that only fixes one of the log sources that I see. We developed our own connector and aren't wasting any more time on this one, until such time it's proven to be functional.


autoComplete (filter forward based on inlined answer Options)

Is your feature request related to a problem? Please describe.
For a selection list where there are many options, be able to filter forward to narrow down the option to select
Describe the solution you'd like

Implement an autoComplete item control from the FHIR specification. This provides the ability to provide filter foward based on a set of inlined answer options (initially).
Future iterations will provide support for referenced valueSets

Describe alternatives you've considered
None
Additional context
To be added

@aditya-07 , estimated effort for this issue is 5 days.

@aditya-07 and I had a discussion today. We will be using a drop down list and chips (https://material.io/components/chips) and will focus on multiple choice questions to begin with.

@jingtang10 @aditya-07 Here is a mock for the basic filter forward scenario. For this scenario there is just 1 option selected.
For multiple options, this should align with the design for the multi-select drop down in issue #216. We should align the design for these. I'll take an action here

As discussed, let's stick with the filter forward with multiple chips as per your POC @aditya-07 . Looks awesome. Thanks

@fredhersch Do you have a questionnaire against which we can test the changes?


Tweaks

Hello. I've been interested in reading my own snss & indexeddb data out, to better track my own activity over time.
I found a couple modest tweaks that I needed to make use of this library. Please let me know if there's anything I can do to help get some or all of these changes merged in.

Thanks for the fast comments, much appreciated! I've tried to bring things closer in line to what you've said.
I really like that we can avoid doing the get_blob_info lookup twice now, which was kind of expensive ("goodness me this is a slow way of doing things,").
I don't really know much about python packaging/library situations to be honest. On Debian my system had all these libraries available (except win32), except the the system python3-pycryptodome gets installed installed as Cryptodome not Crypto.  I wouldn't know what to do to try to do to create some kind of virtual env where I could safely install python packages without affecting my whole system. The changes I made are reverted out, so there's both a record of what someone needs to do, while not affecting the current behavior.


fix: functions4 hint

Closes #68

This item belongs to payment request #19A990 on OnlyDust:

from shramee to enitrat
14 items included
$500 for 1 day of work


Update npm-shrinkwrap.json with new hubot-stackstorm

Also includes updates to unrelated dependencies. I'm not sure if this is normal, expected, or acceptable. 😕

Yeah, there is a way to regenerate shrinkwrap with minimal changes, not all possible deps. Otherwise that diff will break things.

The babel-eslint package has somehow snuck into packages.json, and subsequently into this npm-shrinkwrap.json when I updated it. I'm pretty sure that babel-eslint should go in the devDependencies section instead. That should (I think) drastically reduce the size of this diff once I regenerate npm-shrinkwrap.json.
@armab @LindsayHill @m4dcoder Any objections?

Yeah, finally found #104 where we documented npm-shrinkwrap update process with minimal diff.


Root Trans of  FBX

Hi, thanks for your work.
If I didn't make a mistake, the smpl_trans should be the transform of pelvis. However, when I import the FBX file in Unreal Engine, the pelvis transform become the transform of root, which is between the foot of the character. So something strange is happening when squating down like this:
录屏 06-03-23 19:45:19.webm
Can you give me a hand on that?

Same issue with me. If anybody has a clue, the assistance would be invaluable.

Hi, thanks for your work.
If I didn't make a mistake, the smpl_trans should be the transform of pelvis. However, when I import the FBX file in Unreal Engine, the pelvis transform become the transform of root, which is between the foot of the character. So something strange is happening when squating down like this: 录屏 06-03-23 19:45:19.webm
Can you give me a hand on that?

The same issue with me, have you solved the problem?


Resolution booklet

See #127 for some more info. Please move conversation of this topic here from now on.
Copied ToDo:

[ ] Integration into project
[ ] Test if logo image is loaded correctly
[ ] Print and check the layout

I have done some refactoring but there can still be done a lot, e.g. refactor redundant resolution creation while taking care of special booklet features like (forum becomes sponsor, "General Assembly" becomes forum, no cosponsors are printed, ID of Resolution is printed on the outer head, each resolution is put into a \begin{resolution} ... \end{resolution} environment

merging and doing UI for this in another PR


Supporting k8s version

Hi,
According to your docs, the Camunda helm chart is supporting the following k8s version:

Kubernetes >= 1.20+

Does it mean it supports all k8s version that is bigger than 1.20, including 1.20, or does it not include 1.20?
Thanks

It includes 1.20. Did you encountered any issues?

No, I wasn't sure by the documentation, just want to validate.
Thanks


possible CMarkerPalette::UpdatePaletteContents() logic error

The code for CMarkerPalette::UpdatePaletteContents() looks strange to me.  I think it is intending to remember the current selected marker group, update the palette content, and then re-select the previously remembered marker group.  However, it looks to me like the logic has a bug.  I think the current code actually re-selects the combo-box index which is numerically equal to the marker group index, rather than the combo-box index whose item data contains the marker group index.
In other words, I think CMarkerPalette::UpdatePaletteContents() should look slightly more like CTrayPalette::UpdatePaletteContents().
Or am I confused?

I think the current code actually re-selects the combo-box index which is numerically equal to the marker group index, rather than the combo-box index whose item data contains the marker group index. .... Or am I confused?

You are correct but it turns out that the combo index is equal to the marker index due to a call to CMarkerPalette::LoadMarkerNameList() method. It sets them to be identical.
However, that then begs the question: why store the group index at all?
I believe I was planning for sorting the combo alphabetically or allowing users to set the order rather than showing them in GameBox created order. (The same is true for piece name combos and tile name combos.) It always annoyed me that the combo box order is fixed by the creation order. It's kind of a loose end in the implementation.
With that in mind--you're correct that this would then be a bug. If you'd like to correct the code I would appreciate it!
-Dale

I need to correct this a bit:

I believe I was planning for sorting the combo alphabetically or allowing users...

After stepping through the code changes I discovered that the combo boxes are already sorted alphabetically due to the CBS_SORT flag when the control was created in OnCreate. This means the group numbers stored in the combo items are not necessarily the same as the item's index in the box.
So that makes your original observation true that it's a definite bug.
-Dale

Code checked in.
Closing issue since it wasn't closed automatically. PR's need to be associated with the issue for that to happen.
-Dale


feat: support embellishments and non-punctuation delimiters

Previously, it couldn't attach arguments for macros whose argspec

involves embellishments e{_}, E{^}{default},
or non-punctuation delimiters such as r^_

This PR adds support for it. The second use-case may be marginal, I initially tried to make embellishments work, then realized that the same code would enable the second feature and unifies some codes.
Since a single embellishment argspec can represent multiple arguments, such as in e{^_} where each token ^ and _ would represents 2 arguments,
gobbleSingleArguments signature was changed to return Ast.Arguments | Ast.Arguments[] | null.
Currently, this just puts embellishment tokens as openMark in Ast. Would it be preferable to have a new separate property for embellishments?
Next goal would be to support/test macro expansions for such arguments. Once it's done, I'd like to work on #24.
Please take a look and provide comments, and feel free to make your own changes!

Thanks for the contribution!
It looks like you have some tests failing...
Here are some thoughts:

It would be really nice not to change the signature of gobbleSingleArgument, but I cannot think of a good way around it. One possibility is to change it to always return [] | null
I think more of the existing infrastructure can be reused. The algorithm for e{x} should be very similar to tx m. I think you can reuse the algorithms for grabbing those arguments. A possible idea for e{xyz} is that you keep a record of whether x,y,z has been captured. If one of them has been, you can re-call the function with y,z (or whatever hasn't yet been captured). This could potentially result in a way to keep gobbleSingleArgument returning a singleton. If it always returned the first argument it could gobble, then gobbleArgument would know that on a type=="embellishment" argument, it would need to call until nothing was gobbled. Then then it could rearrange the argument list to appear in the order specified by the oringinal macro spec.
It would be nice to keep e{^} consistent with the parsing of ^. Currently ^ parses as a macro with escapeToken == "^". I think it's reasonable to parse e{x} as

{
                    "type": "argument",
                    "content": [
              {
                    "type": "macro",
                    "content": "^",
                    "escapeToken": "",
                    "args": [
                        {
                            "type": "argument",
                            "content": [
                                {
                                    "type": "string",
                                    "content": "2"
                                }
                            ],
                            "openMark": "{",
                            "closeMark": "}"
                        }
                    ]
                }
                ]
                openMark: "",
                closeMark: ""

That solution is not exactly elegant, though...

Regarding re-using existing algorithm for t
I wasn't aware that optionalToken shares similar traits. However, the way I see it is the other way around: Parsing optionalToken should use the new infrastructure findBracePositions.
A convoluted example, but the current algorithm for t can't correctly figure out arguments for the following:
\NewDocumentCommand{\asdf}{ t^ r__ }{\IfBooleanTF{#1}{123}{456} #2}
\asdf^_789_

It should be expanded to 123 789.
I will fix this and include it as a test case.
Signature of gobbleSingleArgument
One idea I have thought was to artificially decompose e{^-_} into e{^} e{-} e{_}. However it seemed that signatures are intimately tied to the raw .tex source and ArgSpec is assumed to be a faithful representation of it, there is even a warning https://github.com/siefkenj/unified-latex/blob/f2b8c107aed4c7ae585ebbd832ef9085cee35a46/packages/unified-latex-util-argspec/README.md?plain=1#L30

A possible idea for e{xyz} is that you keep a record of whether x,y,z has been captured. If one of them has been, you can re-call the function with y,z (or whatever hasn't yet been captured). This could potentially result in a way to keep gobbleSingleArgument returning a singleton

It seems doable, but then the caller of gobbleSingleArgument should maintain some kind of state, about the embellishment tokens we have matched, its index and so on. Such a logic would then go inside the body of gobbleArguments, but it doesn't look like the right place for that logic..
If you prefer to have its return type Ast.Arguments[] | null, then I'll refactor that.

I think the real issue with changing e{xy} to e{x} e{y} is that, I believe that e{xy} allows x/y to occur in either order, where e{x} e{y} would not.
The mutation warning is just that: a warning against mutating. However, if you create a new ArgSpec or make a deep copy and mutate the deep copy, it will be fine.
I'm leaning more towards making gobbleSingleArgument no return an array and moving some looping logic into gobbleArgument.

I think the real issue with changing e{xy} to e{x} e{y} is that, I believe that e{xy} allows x/y to occur in either order, where e{x} e{y} would not.

I wasn't aware of that! Thank you for pointing it out. I've updated code to implement this behavior.
Now given with this order-agnostic behavior of embellishment, moving the looping logic to gobbleArguments feels slightly more natural. However it's still annoying to pass around matched embellishment token and its index between gobbleArguments and gobbleSingleArgument, so I kept the signature in the end.
Also I've added a test for \asdf^_789_ as promised.

FYI, I just merged #45 which switches the tests to vitest. They might run successfully on your computer now :-)

until also manifests the same issue as optionalToken, so I went on to fix that as well :)
If you look at the code, it should be obvious where I am going. We will be able to handle another edge case: #46.
How does it look? What's your thought on gobbleSingleArgument? Also could you elaborate more on escapeToken == "^" (if this is still an issue)?

Thanks for this! I left a few comments. Also, please run Prettier on all modified files.
I'd still like to move some of the complexity to gobbleArguments and have gobbleSingleArugment only return one thing rather than an array.

I've added eslint and added curly rule which enforces statements in if ...  else to be enclosed in a separate block.
I couldn't find a prettier config, and I doubt it's being consistently used in codes in this repository, for example prettier seems to have some peculiar rules for trailing commas and it is not consistently enforced.
I've tried to add one that matches the overall coding style of the repository. It revealed some obvious "error"s (in the sense of prettier's) whose fix was trivial.

Thanks for the linter updates! Let me know when this is ready for another review :-)

Refactored gobbleSingleArgument. I don't really like the additional complexity introduced by artificially separating logic into two places, but I guess I can live with it. Now gobbleArguments always create a structuredClone of the argSpec because gobbleSingleArgument may mutate it. It may as well check for spec.type === 'embellishment' and create a clone only in that case, but I wanted to make gobbleArgument agnostic to individual argspec types.

Also I think the current tsconfig is somewhat faulty,
cd packages/unified-latex
npm run build

fails with TS errors which shouldn't be an error, and describe and expect isn't resolved in vscode.

Also I think the current tsconfig is somewhat faulty,
cd packages/unified-latex
npm run build

fails with TS errors which shouldn't be an error, and describe and expect isn't resolved in vscode.

Did you do a general build first? If you haven't built the dependencies, it will fail.
I have vitest/global listed in tsconfig.build.json. That is supposed to explain to typescript that describe and it, etc.. all exist. I don't know why it doesn't work...

Turned out that doing a general build fixes the issue with npm run build. It initially failed, so I fixed some type errors in structured-clone that were causing the issue.
Regarding tsconfig, tsconfig.build.json explicitly excludes any test files, and any other tsconfig inherits from it, so IDE think test files are not part of the project and doesn't see vitest/global defined in tsconfig while trying to resolve types.
IMO, tsconfig.build.json should inherit from tsconfig.json, and excluding test files should be done only in tsconfig.build.json file. Each package directory should contain two tsconfig.build.json and tsconfig.json, and npm run build command should invoke tsc with tsc -b tsconfig.build.json. I'm not confident that I'll be able to change every relevant part, so it'd be nice if you could fix it :)

IMO, tsconfig.build.json should inherit from tsconfig.json, and excluding test files should be done only in tsconfig.build.json file. Each package directory should contain two tsconfig.build.json and tsconfig.json, and npm run build command should invoke tsc with tsc -b tsconfig.build.json. I'm not confident that I'll be able to change every relevant part, so it'd be nice if you could fix it :)

Could you do a separate PR that shows what you're talking about in a couple of the workspaces? The tsconfig business is really a pain and I've been trying to figure out how to get it right for a long time...
Alternatively, importing describe, it and friends in each test file will get rid of the typescript warnings.

I would prefer to recreate it on each call rather than mutate it.
On September 17, 2023 10:12:05 AM PDT, Sean Lee @.***> wrote:

@theseanl commented on this pull request.

         if (currPos < nodes.length) {

            currPos++;
        }
        break;
    }

   case "embellishment": {

       // Split tokens into single characters

       const tokens = normalizeEmbellishmentTokens(

           argSpec.embellishmentTokens

       );

       argSpec.embellishmentTokens = tokens; // ArgSpec is mutated here

So for example, are you OK with mutating it in gobbleArguments function? What exactly is the goal you want by not mutating it here?
--
Reply to this email directly or view it on GitHub:
https://github.com/siefkenj/unified-latex/pull/42#discussion_r1328119277
You are receiving this because you commented.
Message ID: @.***>
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Agreed. Can you just make it throw an error for now if it encounters a group and we can fix it in another PR
On September 17, 2023 10:10:19 AM PDT, Sean Lee @.***> wrote:

@theseanl commented on this pull request.

 type: "embellishment";

embellishmentTokens: string[];

embellishmentTokens: (Group | string)[];

Group here is for $e{{x}{y}}$. I agree with you that this should be fixed at pegjs level alongside with https://github.com/siefkenj/unified-latex/issues/46. But working on pegjs would broaden the scope of this pr too much, I'd prefer to fix it in another PR.
--
Reply to this email directly or view it on GitHub:
https://github.com/siefkenj/unified-latex/pull/42#discussion_r1328119056
You are receiving this because you commented.
Message ID: @.***>
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

@theseanl Were you planning on finishing the last changes?

I need to eventually get it done, because it is needed for my other works, but I've been rather busy and less motivated to refactor an already working code to meet a goalpost that keeps moving. Conceptual distinction of singleton and multiple objects feel artificial to me, I even think that such a tendency may be influenced by one's linguistic backgrounds.. I'd be ok if you take over and address the points you've mentioned in reviews. I'll try to find some time within a few weeks.

@theseanl Thanks for your hard work! I have fixed the last of the issues. I couldn't figure out how to get pushing to your branch working, so I created PR #57 You can either pull from that branch, or I can close this PR and merge #57 instead.

Thank you for picking up the slack!


addStream not working on Demo (https://rtcmulticonnection.herokuapp.com/demos/addStream-in-Chat-room.html)

Error :
NotSupportedError: removeStream not yet implemented
connection.peers[p].peer.removeStream(stream);
How to fix it!!! Thank You!

the removeStream is not yet supported in firefox,
you can overcome this issue by wrapping all this to:
if(DetectRTC.browser.name != "Firefox"){ connection.peers[p].peer.removeStream(stream); }
you will have to also to add at the top <script src="https://cdn.webrtc-experiment.com/DetectRTC.js"> </script>

Yeah! Thanks! But The project run on FireFox, so How to fix!!!
Thank you very much!


yield keywords in unity webRequest

I currently need to hook the sendWebRequest method in Unity, and I can successfully execute the hook. However, I'm unable to retrieve the return value because it utilizes the yield return keyword. I'm uncertain about how to achieve this within the context of the IL2CPP-Frida-Bridge.

because I want to send http request and get the response,so I hook unity's webRequest


Add support for individual skos:Concept

This one I am not completely convinced, as FOOPS is aimed at vocabularies (groups of terms).
Semantic artefacts like http://vocab.nerc.ac.uk/collection/A05/current/EV_OXY/ may also get some an assessment. In this case this is a single skos:Concept.

Example: http://vocab.nerc.ac.uk/collection/A05/current/EV_OXY/

http://vocab.nerc.ac.uk/collection/A05/current/EV_NUTS/


Ionic Stacked Label

I'm submitting a ...  (check one with "x")
[ ] bug report => search github for a similar issue or PR before submitting
[x] feature request
[ ] support request

Current behavior

Currently the only option for Ionic Labels (according to the documentation anyway) is the fixed label type by default, with the label on the left and the input on the right on the same line.
Expected behavior

Ionic provides a "stacked" label component that puts the label above the input component. To make an input stacked you just add "stacked" inside the ion-label component.
https://ionicframework.com/docs/api/components/input/Input/
Is there a way to do this by specifying template options?

we're working on the new ionic version (V4) which appear that the stacked input  has been changed into position that accept 'inline' | 'fixed' | 'stacked' | 'floating' value.
@DrakeWitt  are you interested to work on this feature ?

Ah, if Ionic 4 is changing the API I can wait until then.

the v4 is already supported (version 5.0.0-beta.0 of ngx-formly) and we can add this feature that's why I've asked you if you're willing to contribute on it, it shouldn't be difficult, just adding the following code on all ionic label fields would do the job:
<ion-label [position]="to.labelPosition">{{ to.label }}</ion-label>

This is documented? how can I set the floating label for example? thanks.

This is documented? how can I set the floating label for example? thanks.

+1

This is documented? how can I set the floating label for example? thanks.

by passing labelPosition which accept the following value: 'inline' | 'fixed' | 'stacked' | 'floating'
here is a working example: see https://stackblitz.com/edit/angular-tvcdsx
Note: we'll focus on a proper doc after V6 (so not anytime soon), we've provided a bunch of examples that shows all major features that formly offers and for UI such as ionic I encourage you to check the source code for more advanced usage.

Does this work with version 3.1.0?  How to get it working? We have an app that still uses angular 5, so version 3.1 is the suggested version for formly.

Use labelPosition in the templateOptions of the desired field.

I tried
labelPosition: 'stacked'
like this:
{
fieldGroupClassName: 'display-flex',
fieldGroup: [
{
className: 'flex-2',
type: 'input',
key: 'street',
templateOptions: {
label: 'Street',
labelPosition:'stacked'
},
},
It does not seem to have any impact when using angular 5 / ngx-formly
3.1.0 with Ionic.
Any thing that I am missing?
On Sun, Sep 15, 2019 at 8:52 PM vicebtx<EMAIL_ADDRESS>wrote:

Use labelPosition in the templateOptions of the desired field.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ngx-formly/ngx-formly/issues/1092?email_source=notifications&email_token=AAANMXK52HQDJI63QJ6SPATQJZHMBA5CNFSM4FOEEN2KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6XS55I#issuecomment-531574517,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAANMXMVMGH6NGCFKI5NTPTQJZHMBANCNFSM4FOEEN2A
.

@mj6uc this option not available in v3, instead create a custom wrapper which overrides the default wrapper and adds the desired option.
1- custom wrapper
import { Component, ViewChild, ViewContainerRef } from '@angular/core';
import { FieldWrapper } from '@ngx-formly/core';

@Component({ ... })
export class IonicWrapperFormField extends FieldWrapper {
  @ViewChild('fieldComponent', { read: ViewContainerRef }) fieldComponent: ViewContainerRef;
}

2- declare the new wrapper through the NgModule declaration:
@NgModule({
  imports: [
    FormlyModule.forRoot({
      wrappers: [
        { name: 'form-field', component: IonicWrapperFormField },
      ],
    }),
  ],
})
export class FormlyIonicModule {
}


compiled successfully， but call error！

[root@rdsdev sqlchat]# pnpm dev

sqlchat@ dev /home/app/sqlchat
next dev

warn  - Port 3000 is in use, trying 3001 instead.
ready - started server on <IP_ADDRESS>:3001, url: http://localhost:3001
info  - Loaded env from /home/app/sqlchat/.env
event - compiled client and server successfully in 6.7s (184 modules)
wait  - compiling /_error (client and server)...
event - compiled client and server successfully in 1863 ms (185 modules)
warn  - Fast Refresh had to perform a full reload. Read more: https://nextjs.org/docs/messages/fast-refresh-reload
wait  - compiling / (client and server)...
event - compiled client and server successfully in 3s (2906 modules)
wait  - compiling /api/chat (client and server)...
event - compiled successfully in 514 ms (66 modules)
error - pages/api/chat.ts (11:23) @ fetch
error - fetch failed
9 | const handler = async (req: NextRequest) => {
10 |   const reqBody = await req.json();

11 |   const rawRes = await fetch(https://api.openai.com/v1/chat/completions, {
|                       ^
12 |     headers: {
13 |       "Content-Type": "application/json",
14 |       Authorization: Bearer ${openAIApiKey},

Please check your network environment to see if you can access the OpenAI API.

curl success！ping not success！
[root@rdsdev ~]# curl https://api.openai.com/v1/chat/completions
{
"error": {
"message": "You didn't provide an API key. You need to provide your API key in an Authorization header using Bearer auth (i.e. Authorization: Bearer YOUR_KEY), or as the password field (with blank username) if you're accessing the API from your browser and are prompted for a username and password. You can obtain an API key from https://platform.openai.com/account/api-keys.",
"type": "invalid_request_error",
"param": null,
"code": null
}
}
[root@rdsdev ~]#
[root@rdsdev ~]# ping api.openai.com
PING api.openai.com (<IP_ADDRESS>) 56(84) bytes of data.

Please check your network environment to see if you can access the OpenAI API.
ping api.openai.com

curl success！ping not success！
[root@rdsdev ~]# curl https://api.openai.com/v1/chat/completions
{
"error": {
"message": "You didn't provide an API key. You need to provide your API key in an Authorization header using Bearer auth (i.e. Authorization: Bearer YOUR_KEY), or as the password field (with blank username) if you're accessing the API from your browser and are prompted for a username and password. You can obtain an API key from https://platform.openai.com/account/api-keys.",
"type": "invalid_request_error",
"param": null,
"code": null
}
}
[root@rdsdev ~]#
[root@rdsdev ~]# ping api.openai.com
PING api.openai.com (<IP_ADDRESS>) 56(84) bytes of data.
[root@rdsdev ~]# node -v
v17.2.0
[root@rdsdev ~]# pnpm -v
6.11.0

How do I manage to do that?

We have provided configuring the OpenAI API key and endpoint in the settings dialog. Please configure your OpenAI configuration and try it again.

I have same issue, and tried to clear all data in the setting dialog. Issue still there.

I have same issue, and tried to clear all data in the setting dialog. Issue still there.

Also use postman to check if my network problem. But it seems not.

@fxgeoffrey 遇到一样的问题，.env里，还有前端界面设置里，都换成了自己的key，也还是不行，然后确定终端里是可以科学上网的！

Check if your chat gpt api key had expired for free trail $18. https://platform.openai.com/account/usage

同样的问题，科学上网正常，node中无法请求。怀疑是next框架层面的原因


Cursor starts at column 2

Description
When opening a file with the telescope-file-browser plugin, whether through a keymap or when opening a directory with Neovim, the cursors start at column 2.
Neovim version
NVIM v0.9.4
Build type: Release
LuaJIT 2.1.1692716794

Operating system and version
WSL2 - Debian GNU/Linux 12 (bookworm)
Steps to reproduce

nvim .
<leader>f (my keybinding)

Expected behavior
Cursor starts at column 1.
Actual behavior
Cursor starts at column 2.

(Sorry I couldn't upload screen record our internet speed is crawling)
Minimal config
vim.g.mapleader = " "
vim.g.maplocalleader = " "
vim.keymap.set({ "n", "v" }, "<Space>", "<Nop>", { noremap = true, silent = true })

local lazypath = vim.fn.stdpath("data") .. "/lazy/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
  vim.fn.system({
    "git",
    "clone",
    "--filter=blob:none",
    "https://github.com/folke/lazy.nvim.git",
    "--branch=stable", -- latest stable release
    lazypath,
  })
end
vim.opt.rtp:prepend(lazypath)

local plugins = {
  {
    "nvim-telescope/telescope-file-browser.nvim",
    dependencies = {
      "nvim-telescope/telescope.nvim",
      "nvim-lua/plenary.nvim",
    },
    config = function()
      extensions = {
        file_browser = {
          theme = "dropdown",
          grouped = true,
          hidden = true,
          hijack_netrw = true,
          git_status = true,
          prompt_path = true,
          initial_mode = "normal",
          previewer = false,
          mappings = {
            i = { ["<C-o>"] = false },
            n = { ["<o>"] = false },
          },
        },
      },

    pcall(require("telescope").load_extension, "file_browser")

    vim.api.nvim_set_keymap( 'n', '<leader>f', ':Telescope file_browser path=%:p:h select_buffer=true<CR>', { desc = '[F]ile Browser' })

    end
  },
}

require("lazy").setup(plugins, {})

Hey, thanks for the report.
I think this is an issue we're tracking in upstream telescope. The action where using in telescope-file-browser is from upstream so I don't think this is unique to this telescope extension.
https://github.com/nvim-telescope/telescope.nvim/issues/2319
That said, do you experience this every time you open the file?

That said, do you experience this every time you open the file?

Yes, but I only experience it when using telescope-file-browser.

@jamestrew
Based on what I observe throughout my day, it appears that this issue only occurs when you are in Telescope's normal mode (i.e., when exiting insert mode within Telescope) and then enter a file. This weird cursor behavior doesn't seem to manifest when entering a file in Telescope without exiting insert mode.

Ok yeah you're right it's a normal mode issue. It also happens with :Telescope find_files for me.
It's definitely an upstream issue that we're tracking so I'll close this one.


Cancelation not working with useSuspenseQuery

Describe the bug
Hello,
I have implemented cancelation in my project, but it does not seem to work when working with Suspense and useSuspenseQuery / useSuspenseQueries hooks.
I have tested with useQuery and it works perfectly.
I don't see any mention in the documentation that the cancelation does not work with suspense, and don't see at first sight any reason it would be impossible to cancel queries when working with Suspense.
Thanks for the library which is really cool :)
Your minimal, reproducible example
https://stackblitz.com/edit/vitejs-vite-5dtu8c?file=src%2FApp.tsx
Steps to reproduce

Click on the increment button that will simulate multiple call to get the person information for the id: count
See in the console that there is no log concerning the cancelation of the request

ps: it's also possible to simulate the unmounting of the component while a request is running (it does not cancelled the request too)
Expected behavior
I expect that running queries are cancelled
How often does this bug happen?
Every time
Screenshots or Videos
Cancelation working with useQuery:
https://github.com/user-attachments/assets/c8c19efe-343b-4104-8240-087639701147
Cancelation not working with useSuspenseQuery:
https://github.com/user-attachments/assets/d6747dbc-a709-44db-957c-14f0dee5c973
Platform

OS: Mac OS 14.6.1
Browser: Chrome 127.0.6533.100

Tanstack Query adapter
react-query
TanStack Query version
5.51.23
TypeScript version
5.5.4
Additional context
No response

Hm, I think I know why that's the case: We only trigger a cancelation as soon as the last observer unsubscribes. But with suspense, the observer never subscribes in the first place, because we throw the promise to react before that happens in useSyncExternalStore.
I need to think about if that's even possible or if it's a known limitation that it doesn't work with suspense.

after discussing this on twitter, I don't think there is a good way to solve this:
https://x.com/phry/status/1825828334502113295
We can mark it as a known limitation in the docs. Would you like to contribute that?

Hey Dominik
Thank you for the exploration and the explanation of the problem.
I can definitely contribute by marking it as a known limitation in the documentation :)


Segmentation fault

Could any body help me to solve this bug? I have submitted it for a few days without any response.
K3S_TOKEN=b8bf0cff5d98326199fb9aa974f5c01c /usr/local/bin/k3s server -v 5 --cluster-init
I0919 21:04:07.650001    2630 interface.go:400] Looking for default routes with IPv4 addresses
I0919 21:04:07.650179    2630 interface.go:408] Default route transits interface "eth0"
I0919 21:04:07.650335    2630 interface.go:208] Interface eth0 is up
I0919 21:04:07.650431    2630 interface.go:256] Interface "eth0" has 2 addresses :[<IP_ADDRESS>/24 fe80::216:3eff:fe2e:74db/64].
I0919 21:04:07.650509    2630 interface.go:223] Checking addr  <IP_ADDRESS>/24.
I0919 21:04:07.650565    2630 interface.go:230] IP found <IP_ADDRESS>
I0919 21:04:07.650621    2630 interface.go:262] Found valid IPv4 address <IP_ADDRESS> for interface "eth0".
I0919 21:04:07.650675    2630 interface.go:414] Found active IP <IP_ADDRESS>
I0919 21:04:07.650746    2630 services.go:51] Setting service IP to "<IP_ADDRESS>" (read-write).
INFO[2020-09-19T21:04:07.650829983+08:00] Starting k3s v1.18.8+k3s1 (6b595318)
I0919 21:04:07.669288    2630 services.go:51] Setting service IP to "<IP_ADDRESS>" (read-write).
I0919 21:04:07.670665    2630 interface.go:400] Looking for default routes with IPv4 addresses
I0919 21:04:07.670685    2630 interface.go:408] Default route transits interface "eth0"
I0919 21:04:07.670762    2630 interface.go:208] Interface eth0 is up
I0919 21:04:07.670832    2630 interface.go:256] Interface "eth0" has 2 addresses :[<IP_ADDRESS>/24 fe80::216:3eff:fe2e:74db/64].
I0919 21:04:07.670880    2630 interface.go:223] Checking addr  <IP_ADDRESS>/24.
I0919 21:04:07.670894    2630 interface.go:230] IP found <IP_ADDRESS>
I0919 21:04:07.670904    2630 interface.go:262] Found valid IPv4 address <IP_ADDRESS> for interface "eth0".
I0919 21:04:07.670916    2630 interface.go:414] Found active IP <IP_ADDRESS>
Segmentation fault

Please don't open duplicate issues.


"Failed to create terminal for task func: extensions install" after Ctrl + c

I'm running into errors with VS Code tasks whenever I use Ctrl + c to kill a running task. (This is with the upcoming TypeScript .vscode configurations)
Steps:

Create new TypeScript function app
Add TypeScript function (ex: HttpTrigger)
Press F5
At this point, everything is ok (see Figure 1)
Press Ctrl + c and then enter to kill the tasks that were running
Press F5
Errors appear (see Figure 2 and 3) and console output from another attempt:

[2019-02-21 16:48:49.724] [renderer1] [info] standard startup
[2019-02-21 16:53:18.725] [renderer1] [error] Cannot read property 'group' of undefined: TypeError: Cannot read property 'group' of undefined
    at e.createTerminal (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:3315:135)
    at l (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:3309:58)
    at new Promise (<anonymous>)
    at e.executeInTerminal (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:3309:19)
    at file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:3305:667
    at process._tickCallback (internal/process/next_tick.js:68:7)

Figure 1: Running Azure Functions!

Figure 2: Errors on second try

Figure 3:

Yeah I can repro this with "ctrl+c". But just FYI you can workaround this by using either the detach button at the top of VS Code (button on the right pictured here):

Or if you hit the trash can on the task here:

Those seem to work fine for me.

This must've been fixed in VS Code. No longer repros for me - testing on 1.33.1


Spell Check - "th" to "the"

Loving this new initiative.  Hope to add something more meaning full some day :)

Thank you again @asadrefai! 🫶🏻


Watsonx not found in Quarkus Tools for vscode

I'm using vscode and when I search for the Langchain4j extension in Quarkus (using Quarkus Tools) I don't find watsonx in the list.

I am pretty sure you need to add the extension metadata to https://github.com/quarkusio/quarkus-extension-catalog/tree/main/extensions (in the same way the others are added)

quarkusio/quarkus-extension-catalog#113

Merged, thanks!
I don't remember how often the registry is checked, but it should be available pretty soon


While running the app i got this error

/E:/flutter/.pub-cache/hosted/pub.dartlang.org/country_pickers-1.3.0/lib/utils/my_alert_dialog.dart:139:36: Error: Method not found: 'ButtonTheme.bar'.
children.add(new ButtonTheme.bar(
^^^
FAILURE: Build failed with an exception.

Where:
Script 'E:\flutter\packages\flutter_tools\gradle\flutter.gradle' line: 1035

What went wrong:
Execution failed for task ':app:compileFlutterBuildDebug'.

Process 'command 'E:\flutter\bin\flutter.bat'' finished with non-zero exit value 1

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 1m 6s
Exception: Gradle task assembleDebug failed with exit code 1

I solved it-
In your pubspec.yaml file
change the package
from
country_pickers: ^1.3.0
To
country_pickers: ^2.0.0


[CONTINT-3310] Increase the Redis app verbosity

What does this PR do?
Increase the redis application verbosity.
Which scenarios this will impact?

aws/eks
aws/kind

Motivation
With the default log level, redis logs things only at startup and not at each request.
The problem is that, if the fake intake restarts in the middle of the tests, after redis pods have started, the tests will never find any redis logs from the fake intake client anymore.
In order to be more resilient to fake intake restarts, it’s better to be sure that the source of logs that are asserted are producing a continuous flow of logs.
Additional Notes

/merge


Fix logInspector for PyQt5 5.15.7

Since the python dependency version is not locked in setup.py,  the pip install logInspector/ will always install the latest version python dependency . This commit will fix logInspector for the current latest PyQt5 5.15.7.
I suggest we lock the python dependency version.

@AchmadFathoni thanks for the PR. We will review soon.


Add boilerplate for WG14 (the C language)

As-is it doesn't support paper numbers. Their URL scheme seems simple enough: it's all at http://www.open-std.org/jtc1/sc22/wg14/www/docs/

Why is the default highlighting language C++?
C seems to be supported, according to http://pygments.org/docs/lexers/#lexers-for-c-c-languages

Why is the default highlighting language C++?

Because I copy pasta'd from the C++ boilerplate 😁
Fixed here: https://github.com/tabatkins/bikeshed/pull/1215


"Exec format error" on installation of rtl_433

I tried installing this on HA, but when I start the addon, I just see this line flooding my logs:
./run: line 63: /usr/local/bin/rtl_433: cannot execute binary file: Exec format error

HA information:
Home Assistant OS 6.3
supervisor-2021.09.0
core-2021.9.5
OS version 5.10.17-v7

That's quite odd. That's the error you'd get when trying to run a Arm binary on an x86 CPU or vice versa. Sometimes you'll see it with multi-arch Docker images, where Docker is dumb and runs the wrong thing... but that's not the case here, since HA add-ons don't use multi-arch, they have specific images built for each arch.
What hardware are you running HA on?

I'm on armv7l, it's a Pi 3B+

The build for that arch looks fine, as does the image on Docker Hub. I'll have to spin up one of my old Pi 3 to test it and see why it's pulling the wrong image, or why it's building the wrong exec format. I've got a bit going on for the next week or two, so sadly it'll be a bit before I can look more. I think it might be an issue with the container being used with the build.

I changed the Dockerfile to use an arch-specific builder. Can you test out the latest version and let me know if that resolved the exec error?

Yes, that resolves the error. Thank you!


Add bevy_dylib to force dynamic linking of bevy

This easily improve compilation time by 2x.
Fixes #791
TODO

[ ] Mention bevy_dylib in docs.

Tip: You may want to review with git show --color-moved=dimmed-zebra to show moved code grey instead of red+green.

Ah, the docs live in a separate repo: https://github.com/bevyengine/bevy-website/blob/master/content/learn/book/getting-started/setup/_index.md
Should I make a PR or should I wait for this PR to be merged?

Feel free to make a pr whenever. We'll hold off on merging it until the next release (which will be in about a month) so there's no real time pressure.

First: this is super awesome :heart:
I have a proposal for a slight tweak to the crate structure, which allows for a better/clearer UX:

leave the current bevy crate in the root folder
add a bevy_internal crate, which pulls all of the crates together / defines the prelude (aka what the bevy crate does on the master branch)
the bevy crate re-exports the contents of bevy_internal. it also does the use bevy_dylib trick, but only if the dynamic feature is enabled. bevy_dylib would be an optional dependency.

This allows consumers of the bevy crate and examples to just import bevy stuff normally (without worrying about dylib tricks). If they want to force dynamic linking, they just need to do cargo run --features bevy/dynamic (for consumers) or cargo run --features dynamic (for examples). The default cargo run will  exclude bevy_dylib from the build tree and build "statically"
I implemented this on my branch here: https://github.com/cart/bevy/tree/bevy_dylib
There are two downsides / caveats:

for some reason this breaks imports in our proc macros (but only for examples). i'm trying to fix this now.
we need to duplicate feature declarations: once in bevy and once in bevy_internal. i think the extra boilerplate is worth it

If we can fix (1) and you don't find any "gotchas" in this approach, I think I'll just push the changes to this pr's branch.
Thoughts?

I think I can fix (1) by making our proc_macro import inference a little smarter. I think using find-crate instead of proc-macro-crate will give me the tools i need.

That approach looks better indeed.

Wow this plays nicely with the new ECS changes on master. The same example that could iterative compile (with dynamic linking) in 0.59 seconds now compiles in 0.43 seconds.

Hold up, whats up with all the refactoring when #![cfg_attr(feature = "dynamic", crate_type = "dylib")] could've been used at lib.rs root? Would've accomplished the same thing without the refactor.

Cargo passes --crate-type lib, so I don't think #![cfg_attr(feature = "dynamic", crate_type = "dylib")] would work.

But, that one of the 3 ways that the documentation says will work to change a crate type into dylib.

--crate-type=dylib
#![crate_type = "dylib"]
crate-type = "dylib" in Cargo.toml under [lib]
rustc -C target-feature=-crt-static foo.rs

The first 3 which are essentially the same thing, just overriding each other. Cargo shouldn't pass --crate-type lib by default. Internally a lib is default. Everything else will override it unless you actually pass in --crate-type lib manually.

rustc -C target-feature=-crt-static foo.rs
RUSTFLAGS='-C target-feature=-crt-static' cargo build

These only control if the C standard library is statically linked or dynamically. Dynamically is the default for pretty much everything except musl.

crate-type = "dylib" in Cargo.toml under [lib]

You can't edit the Cargo.toml of dependencies.

So I am not exactly too certain why bevy needs to have it as a feature when you can tell the compiler directly.

The problem is that while you can tell it the compilet directly, you can't tell it cargo directly. When you use cargo, you can't override the crate type of arbitrary crates from your project. You can only set the crate type of your own project, which has to be an executable if you want to actually run your game.

However, it is important to note that both the crate_type and crate_name attributes have no effect whatsoever when using Cargo, the Rust package manager. Since Cargo is used for the majority of Rust projects, this means real-world uses of crate_type and crate_name are relatively limited.
Just read that from: https://doc.rust-lang.org/beta/rust-by-example/attribute/crate.html. Weird that in their other reference seems to say otherwise. Anyways, yeah, makes sense.


HARVESTER: delete unuse file & fix bug

link
https://github.com/harvester/harvester/issues/1067
https://github.com/harvester/harvester/issues/1064

LGTM


How to delete  the measurements on microscopy? [Feature Request]

What feature or change would you like to see made?
Right click to show the delete option
Why should we prioritize this feature?
It's so important.

I think we should add this

Closing in favor of https://github.com/OHIF/Viewers/issues/3950


Support for Python 2.6

Python 2.6 has reached its end of life long ago, but RHEL 6 / CentOS 6 still ship it.
Support for Python 2.6 won't be too much of a hassle, but will greatly simplify the life of developers who are forced to use "enterprise" distros :)

@knaperek this pull request was so perfect, so I have no chance not to merge it =)
I'm using it for a years to show to people the example how good pull requests should looks like.


Fix call methods for the ccpi plugins regularisation toolkit

All of the regularisers that are not TV have a wrong implementations of the __call__ method.
These should be deleted and  Not implemented error will be raised

I think that it should be sufficient to remove the definition (override) in the derived class. If no implementation is given the base class method will be called, which already raises NotImplementedError

If we use raise NotImplementedError then none of the algorithms will run because objective at the iteration=0 must be computed. I suggest to return 0. plus a warning message.

We agreed to return float nan and a warning.


fix(vmalert): discover vmalertmanagers

Fixes: #702

Upon further thinking and reading, I'm not sure it will fix the linked issue. However, it definitely does address some problematic assumptions made by the original filtering code. There are a few scenarios where it will do the complete wrong thing, which isn't ideal.

Upon further thinking and reading, I'm not sure it will fix the linked issue. However, it definitely does address some problematic assumptions made by the original filtering code. There are a few scenarios where it will do the complete wrong thing, which isn't ideal.

Thanks for the pr!
Can you add some scenarios that could be wrong for the origin code in the test file?

@Haleygo Will do.


feat: support for blockDuration

[ ] Add prop blockDuration based upon this wiki from node-rate-limiter-flexible

+1. Would love to manage how long the ban is for


Spec compliance: Int vs Int32

This may be a little bit picky, but the spec says that Ints are 32-bit integers. Haskell's Int type, used here, is at least a signed 30-bit integer, probably due to tagged pointer representation. (Although on my system it's a 64-bit int, and I suppose this is quite common).
For full spec compliance, the API could be changed to use Int32 from Data.Int everywhere. This might make things a little bit uglier because you would have to use Int32 everywhere, and I'm not sure about GHC implementation details but maybe Int32 is boxed on 32-bit platforms due to not being able to use the 30-bit optimization trick. Or it could be argued that this is not worth the trouble.

Similarly, floats are supposed to be double precision floats.

Hi. thank you for contributing! I sent invitation to you for this project
it seems not so terrible to replace it with Int32, but I will propose that we wait, anyway it is not so hard to implement.

for about 4 years there are no more reactions about it, I think I can close.


Blog page design tweaks

PROPOSAL

Minor tweaks to the design of the blog page. This page meets guidelines for F22 minor rebrand.

CHANGELOG

Removed shadows bc too jarring
Re-added stroke from initial design
Cards turn gray in dark mode

This is change #7 of my big update to prepare for next semester's codebase.

IT DOESNT WORK ON MY GALAXY FOLD

IT DOESNT WORK ON MY GALAXY FOLD

imagine having a fold KEKW

https://user-images.githubusercontent.com/8981287/160302348-34e56422-df3d-4dca-83b1-ae146dff4c4f.mp4

also i cant see the blog due to https://github.com/EthanThatOneKid/acmcsuf.com/issues/407

@mikeploythai can you fix https://github.com/EthanThatOneKid/acmcsuf.com/issues/267 too

@mikeploythai can you fix #267 too

ok

LGTM! This seems to resolve #407.

https://acm-csuf-site-git-mike-blog-design-tweak-ethanthatonekid.vercel.app/blog no it doesnt

Is this still happening on your end, @jaasonw?

it does but i still want #267 fixed first

[12:57 PM] moike: Okok go ahead and close 426, 415, 414, 413, and 406

que paso


web3j version update

The version of web3j that the ATs use is old. However updating it to latest (4.8.4) broke some ATs:
https://app.circleci.com/pipelines/github/hyperledger/besu/8042/workflows/f87fc4e8-7e94-4cdd-b16f-641c2b737bb3/jobs/40545
I tried 4.6.0 and the rlp test passed but the other 3 still fail with the same errors. This requires some investigation.
https://github.com/web3j/web3j/releases

It doesn't look like these are still failing - did we fix the problem?

maybe it needs to line up with web3js quorum?

Hopefully updated correctly https://github.com/hyperledger/besu/pull/2616 the tests were failing because the behaviour has changed in web3j to throw a TransactionException when (!receipt.isStatusOK())


Make sure notifications is built correctly while passing ci checks

Signed-off-by: Peter Zhu<EMAIL_ADDRESS>Description
Make sure notifications is built correctly while passing ci checks
Issues Resolved
#1950
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #1959 (0213302) into main (c9b3a51) will increase coverage by 5.53%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##               main     #1959      +/-   ##
=============================================
+ Coverage     94.46%   100.00%   +5.53%
=============================================
  Files           179         6     -173
  Lines          3649       105    -3544
  Branches         29        19      -10
=============================================
- Hits           3447       105    -3342
+ Misses          196         0     -196
+ Partials          6         0       -6

Impacted Files
Coverage Δ

...sts/jenkins/jobs/DetectTestDockerAgent_Jenkinsfile

...est_workflow/bwc_test/bwc_test_suite_opensearch.py

src/test_workflow/bwc_test/bwc_test_suite.py

src/system/config_file.py

src/manifests_workflow/component_opensearch.py

src/test_workflow/test_args_path_validator.py

src/ci_workflow/ci_check_list.py

...rkflow/integ_test/service_opensearch_dashboards.py

src/run_build.py

src/build_workflow/build_artifact_checks.py

... and 163 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c9b3a51...0213302. Read the comment docs.

This looks wrong to me. Both declarations run gradle in the notifications folder because working_directory is set to notifications in both. So it's built twice and output from the same build.sh is produced. The manifest will not have both notifications-core and notifications. The only difference is the CI check.


Need to review the documentation for 12.06.00 release.

The documentation needs to be reviewed for the 12.06.00 release.

Updated the documentation.  Close the issue.


Added extra high priority

I added an extra high priority.
Reason: The prefetching of images was called to too often when the app tries to display images with high priority.
Now I added an extra queue for the jobs with extra priority which always runs.
In case an operation in the new queue is running the "normal" queue is suspended as long as the high priority queue contains no more element.

@chdi please isolate the fix you are trying to make. Right now this PR is trying to add a Pod KVOController and make other changes

Closing, based on the current state of the PR and the lack of response.


Is the source code for Live Share available in this repo, to try it early?

Just curious if I can build VSCode myself, to try Live Share. Thanks!

+1
We are debating writing the same functionality into a vscode/atom fork so it would be quite nice to know this work is already available for us.

This is the repo for live share:
https://github.com/MicrosoftDocs/live-share

@kaburkett that is only the docs.

Hi!
Live Share is still in its infancy and the source is highly volatile right now. Because of this, we are not ready to release the code, accept external contributions, and more importantly we are not ready to solidify any APIs on which you could build.
So for now, we are focused on releasing updates to Live Share rapidly, enabling folks to kick the tires with the latest bits and to help validate the scenarios.
Live Share is an extension to VS Code, so for the time being please do file issues here: https://github.com/MicrosoftDocs/live-share and as the service matures we'll be in a better position to move to an open development model, like we have with VS Code.
Thanks for understanding our current state and hopefully this gives you enough insight into where we want to go.
//cc: @lostintangent


zero pad DHE public key in ServerKeyExchange message for interop

Some versions of the Microsoft TLS stack have problems when the DHE public key
is encoded with fewer bytes than the DHE prime.
There's some public acknowledgement of the bug at these links:
https://connect.microsoft.com/IE/feedback/details/1253526/tls-serverkeyexchange-with-1024-dhe-may-encode-dh-y-as-127-bytes-breaking-internet-explorer-11
https://connect.microsoft.com/IE/feedback/details/1104905/wininet-calculation-of-mac-in-tls-handshake-intermittently-fails-for-dhe-rsa-key-exchange
This encoding issue also causes the same errors with 2048-bit DHE, if the
public key is encoded in fewer than 256 bytes and includes the TLS stack on
Windows Phone 8.x.
Pull request against master, but can be easily backported to 1.0.2 and 1.0.1 (if eligible), in those versions the logic is in ssl/s3_srvr.c and the added lines could be copied as-is.

I'm not sure why that test (70-test_sslrecords, "In context empty records test") is failing; I can't reproduce it on my mac, even when i ran the test in a loop for several minutes; and this change shouldn't affect that test at all, since it's negotiating a cipher without DHE.

As far as I can see, they fixed it.  Why do we need to add something to be compatible?

They fixed it in recent builds of Windows 10 (including Windows 10 for phones). For Windows Phone 8.1, they have not issued an update, most of the devices running WP 8.1 are unable to be upgraded to Windows 10, and there are tens of millions of these devices in the wild.
I don't know if Microsoft has made a fix for this on older versions of desktop Windows. I can do some research into that, if the desktop numbers would be more convincing.
I had previously worked around this by hooking the DHE callbacks and regenerating keys when they would encode to fewer bytes than the prime, but the callbacks changed in 1.0.1r, and this is a cleaner fix, and having it in upstream will benefit the many users who are using the Microsoft stack and are unable to upgrade.

FWIW, we do this in BoringSSL. An older version of yaSSL also has issues here. I don't have very good numbers since we ended up getting this mixed up with a ton of other confounding factors (we didn't even realize this was what we were seeing at first), but I believe it was the cause of a small but noticeable fraction of connection errors in Chrome.
(Search for the paragraph that says 'DHE' in this message.)
Spec-wise, TLS doesn't say much useful about the encoding of DHE public keys. There is something to be said for zero-padding being more Correct since crypto encodings really ought to be fixed width. (Then again, the final Z value is not zero-padded. It should have been, but so it goes.)

I do agree that it's underspecified. I guess there is always a possibility that some other implementation is going to have a problem with it being padded, but then I think there are already enough implementations that do pad it so that it won't be a problem in practice.
So I think we should fix this.

Note that Chrome isn't doing DHE anymore, so our experience isn't that indicative. Unfortunately this all happened as we getting rid of it anyway. But, yeah, I think this is the more compatible option and would be surprised if anything rejected it.

I'm working on updating the pull request to address the comments, and also rebase to current; sorry for any interim weirdness.

+1

commit 78a01b3 pushed, thanks!

(I took Matt's plus-one to include the compile-time fix to move the variable)

Thanks all; would you like to see a PR against 1.0.2 for this?

Yes, please


Enhancing the Community discussion

Is your feature request related to a problem? Please describe.
The current Community Discussion section could be improved to boost user engagement and make conversations more accessible. Enhancements could include better organization of discussion threads, improved search functionality, or adding features like tagging and notifications for updates in discussions users follow. This would create a more interactive and supportive community environment
Describe the solution you'd like.
No response
Describe alternatives you've considered.
No response
Additional context.
No response
Show us the magic with screenshots

Checklist

[X] I have checked the Existing Issues
[X] I have read the Contributing Guidelines
[X] I want to work on this issue. (optional)

check the deployment properly please


XSS works, but OR does not work, gives an error DevToolsActivePort file doesn't exist)

Hello
When using the tool, i'm getting errors for the OR section (see image)

But the strange part is, the XSS section is working fine

Hello,
We’ve encountered this issue before. For now, please try running it as a non root user.
Best regards,
Haq


code clean up

replaced if/else constructs with switches
replaced foreach loops
added log entries
fixed order in static fields
switched comparisons of Strings to not generate null pointers

Nik, please rebase your changes on top of master instead of merging them into your branch.


User agent does not persist across windows

Meta
Poltergeist Version:
1.15.0
Expected Behavior
After calling capybara_session.driver.add_headers('User-Agent' => 'foo'), I would expect all subsequent requests within that session to have User-Agent set to foo, even if there are new windows created during that session.
Actual Behavior
The headers are only set in the initial window. Thus, if a new window is opened, either by clicking a link with _target=blank or by explicitly opening a new window, the user agent reverts back to the default PhantomJS agent.
Steps to reproduce
capybara_session = Capybara::Session.new(:poltergeist)
capybara_session.driver.add_headers('User-Agent' => 'foo')
capybara_session.visit 'http://whatsmyuseragent.org/'
puts capybara_session.find('.user-agent').text
# => foo
capybara_session.switch_to_window capybara_session.open_new_window
capybara_session.visit 'http://whatsmyuseragent.org/'
puts capybara_session.find('.user-agent').text
# => Mozilla/5.0 (Unknown; Linux x86_64) AppleWebKit/538.1 (KHTML, like Gecko) PhantomJS/2.1.1 Safari/538.1

1.15.0 is slightly outdated - does this still happen on 1.17.0 ? and what version of PhantomJS are you using?

@twalpole Yes, it still happens in master. I'm running PhantomJS 2.1.1 (but this doesn't seem to be a PhantomJS bug).
Check out PR #916 above.

Closed via PR #916


Cluster manager fails to find correct bridgeIP when using alternative docker bridge IP range (bip)

Rancher Version:  1.1.0-dev4 (latest)
Docker Version: 1.10.3 (problematic behavior is similar on version 1.11.2)
OS and where are the hosts located?: Ubuntu 14/04 + onsite vmware
Setup Details: HA rancher
Environment Type: Cattle
Steps to Reproduce:

Configure docker daemon with the --bip=cidr option to manually specify the ip range used by dockers default bridge network. (This was necessary for me to avoid a conflict with an existing internal network) For example, put the following in /etc/default/docker and restart docker:
DOCKER_OPTS="--bip=<IP_ADDRESS>/24"

Follow Rancher Documentation on setting up Rancher on multiple nodes

Launch the HA script (rancher-ha.sh) and observe output of docker logs -f rancher-ha

Results:
rancher-ha can't get past starting the agent:
level=info msg="Can not launch agent right now: Server not available at http://<IP_ADDRESS>:18080/ping:" component=service

Expected:
The URL to ping should be: http://<IP_ADDRESS>:18080/ping instead of http://<IP_ADDRESS>:18080/ping.
Why this is happening:
The GetBridgeIP function from cluster-manager calls the docker API and fetches the Subnet field from IPAM/Config. It then adds one to this network address to determine what is the hosts IP.
Unfortunately, when specifying the --bip option for docker daemon, the "Subnet" is no longer a network address, but the IP specified in --bip. (It is not possible to specify a range, you need to specify the IP address the bridge is to use).
This can be also be witnessed from the output of docker network inspect:
When specifiying --bip:
    "IPAM": {
        "Driver": "default",
        "Options": null,
        "Config": [
            {
                "Subnet": "<IP_ADDRESS>/16",
                "Gateway": "<IP_ADDRESS>"
            }
        ]
    }

With the default configuration:
    "IPAM": {
        "Driver": "default",
        "Options": null,
        "Config": [
            {
                "Subnet": "<IP_ADDRESS>/16"
            }
        ]
    },

Workaround: Manually set up the docker bridge using bridge-utils (or OS configuration files) and configure docker daemon with the --bridge= option to use it.
Proposal for fix: Perhaps it is a good idea to query the rancher-ha-parent container directly instead of passing through the docker hosts bridge IP, as container IP address can be determined correctly?

I have the same issue here:
/usr/bin/docker daemon --selinux-enabled -H tcp://<IP_ADDRESS>:4243 -H unix:///var/run/docker.sock -G dockerroot --bip=<IP_ADDRESS>/24 --storage-driver devicemapper --storage-opt dm.fs=xfs --storage-opt dm.thinpooldev=/dev/mapper/VG02-docker--pool --storage-opt dm.use_deferred_removal=true
time="2016-07-27T13:44:41Z" level=info msg="Can not launch agent right now: Server not available at http://<IP_ADDRESS>:18080/ping:" component=service
curl <IP_ADDRESS>:18080/ping
pong
A fix for this problem would be appreciated.

+1 for fix

Fix will be in v1.2.0-pre2-rc6

@janeczku : Verified with v1.2.0-pre3-rc1.  As mentioned above, in /etc/default/docker I set
DOCKER_OPTS="--bip=<IP_ADDRESS>/24" and did a docker restart on the hosts. Did not see the issue when running rancher-ha.sh. The HA cluster was set up correctly. I added hosts to the default env and I was able to add services and the docker inspect showed the IP addresses within the allowed range.
       "Networks": {
                "bridge": {
                    "IPAMConfig": null,
                    "Links": null,
                    "Aliases": null,
                    "NetworkID": "3394923709ba21071b7f4dc3a54af951ecce40877710a95009a2bd98527e680a",
                    "EndpointID": "70f21c4c31362db723476e6b2715fc4ce1214fdbed2f78dbea5877a2c500d8c3",
                    "Gateway": "<IP_ADDRESS>",
                    "IPAddress": "<IP_ADDRESS>",
                    "IPPrefixLen": 24,
                    "IPv6Gateway": "",
                    "GlobalIPv6Address": "",
                    "GlobalIPv6PrefixLen": 0,
                    "MacAddress": "02:02:1f:ac:9f:58"
                }

Is there any other verification required?

@soumyalj Being able to setup HA successfully with  --bip option used verified the fix.


Upload file get time out response

When I run the project and try to upload file, I get the Time-out response
`
Could not create share link. Missing file: D:\PycharmProjects\GraphRAG-Local-UI-main\venv\Lib\site-packages\gradio\frpc_windows_amd64_v0.2.
Please check your internet connection. This can happen if your antivirus software blocks the download of this file. You can install manually by following these steps:

Download this file: https://cdn-media.huggingface.co/frpc-gradio-0.2/frpc_windows_amd64.exe
Rename the downloaded file to: frpc_windows_amd64_v0.2
Move the file to this location: D:\PycharmProjects\GraphRAG-Local-UI-main\venv\Lib\site-packages\gradio
2024-07-24 14:07:41,904 - INFO - HTTP Request: POST http://<IP_ADDRESS>:7860/api/predict "HTTP/1.1 504 Gateway Time-out"
2024-07-24 14:07:48,154 - INFO - HTTP Request: POST http://<IP_ADDRESS>:7860/reset "HTTP/1.1 504 Gateway Time-out"`

可以参考这个：https://github.com/gradio-app/gradio/issues/3498#issuecomment-1651038942

frpc_windows_amd64的问题已经解决了，主要是一直会报
2024-07-24 16:06:44,139 - INFO - HTTP Request: POST http://<IP_ADDRESS>:7860/api/predict "HTTP/1.1 504 Gateway Time-out"
2024-07-24 16:06:52,332 - INFO - HTTP Request: POST http://<IP_ADDRESS>:7860/reset "HTTP/1.1 504 Gateway Time-out"
不知道要怎么解决

可以参考这个：gradio-app/gradio#3498 (comment)
2024-07-24 16:06:44,139 - INFO - HTTP Request: POST http://<IP_ADDRESS>:7860/api/predict "HTTP/1.1 504 Gateway Time-out"
2024-07-24 16:06:52,332 - INFO - HTTP Request: POST http://<IP_ADDRESS>:7860/reset "HTTP/1.1 504 Gateway Time-out"

主要是这两个Time out不知道如何处理


tests, skip migration killer test on kind ipv6 provider

The test is relatively new and very flaky, causing CI to stall merges.
Current effort is to support dual stack on proper k8s
provider, so this one will be skipped.
See https://github.com/kubevirt/kubevirt/issues/4086
Signed-off-by: Or Shoval<EMAIL_ADDRESS>None

/assign @phoracek

Merging this one manually because this failure is blocking other PRs from being automatically merged and it's failing on an un-related flake.


API Tokens seem to fail after initial session times out

Rancher Versions:
Server: 1.4.1
Using AzureAD, account based API tokens fail after the initial session times out. We need to verify that when an api key is used that we can create new sessions with the backend.

Thanks for opening an issue @cloudnautique. I'm still trying to find a 100% reliable way to reproduce this issue, but if there are any further details I can provide please just let me know.

One further update to this -- I think there is another level of complexity here.
It seems that this is related to the API key being created under a User vs Local User. Going to continue working on a reliable way to reproduce the issue.

@kelchm - hello, I can't currently reproduce your issue.  So a couple of things might help me.

When the API key is created, what "kind" of user is creating and using the API key (is it a Admin or User)?
What type of API key are you using?  It is a Account API key or a Environment key?
Does it always fail on the same API call?
I'm not sure the difference between a "User" vs "Local user"?

@tfiduccia

When the API key is created, what "kind" of user is creating and using the API key (is it a Admin or User)?

The user is an admin.

What type of API key are you using? It is a Account API key or a Environment key?

I am creating an account API key that is used for multiple environments.

Does it always fail on the same API call?

Yes, but admittedly I have not tested other rancher commands extensively. The error message I receive when running rancher up ... is: time="2017-03-20T12:46:46Z" level=fatal msg="Failed to read project: Failed to find the current environment"

I'm not sure the difference between a "User" vs "Local user"?

This seems to be the root of the issue... I've noticed when adding a user to an environment that the user can either be added as a 'User' (IE: a user from Azure AD) or as a 'Local User' (IE: a user NOT from Azure AD). I have not had a recurrence of this bug since adding the 'local' version of this user to each of the environments.
Please let me know if you have any other questions.

It looks like before you enabled AzureAD, you enabled Local Authentication and added a few accounts.  Switching authentications is not suggested and they don't mix.    If you do switch.. you have to completely remove/delete all the users from previous authentication method and restart.
If you are using any other authentication method besides Local, you should not (and shouldn't be able to) add user's that are outside.

@tfiduccia, I did in fact enable local auth before switching to Azure AD.
FWIW, the GUI makes no mention of there being issues between switching between authentication methods (IE: disable local auth, then enable Azure AD.) I'd argue that the current design encourages that user to quickly switch authentication via the GUI. At the very least there could be a warning presented when disabling auth that specific actions need to be taken before switching to another authentication type.

@kelchm - We do have multiple issues already been entered surrounding this area.  But the warning is not a bad idea.  I do know that at some point we have talked about support for multiple authentication types.  For now, I'm going to go ahead and close this and will talk about the warning with the developers.  Thanks!