RE3 - Absolute Silence In Room 207 (Press Street)

Version
3.0.9 (4d8d5d6)
Seed
R730-BATR-ZJ4EFM0K2GU007BA5771TKMNMKUAEXZZZZZ
Scenario
RE 3 (Jill)
Player Character
Nemesis
What happened?
I believe track MAIN01 would be the original music for this area. It was swapped for main2a.sap from RE2, but the area plays no music.

Other areas that swapped with a different RE2 track like the brain sucker attack at the construction site (203), does play music.

I am not sure if I can investigate this issue, as I do not get the same randomized music selection when trying this seed.


Implement some way the specify contract version

Describe the bug
The substrate target needs a contract version (semver) to be included in the metadata. Right now this is always just set to "0.0.1" and there is no way for the dev to set this directly, which means you need to edit the metadata file manually after compilation.
In ink!, this version comes from the Cargo.toml project file, which obv. does not exist for solidity contracts, so this needs some brainstorming on possible solutions. Existing ideas are to provide it in the .sol source file directly somehow (for example within a doc comment) or to simply add a CLI flag like --contract-version X.X.X for the substrate target.
To Reproduce
Expected behavior
There is some (documented) way to let the compiler know the contract version. It should work for all targets, as this might be an issue for other targets as well.

Related: #1084


Hasura GraphQL Backend

Would love to see a version of backend with Hasura GraphQL. The frontend integration can be done with React + Apollo Client.

@praveenweb I plan to do it in the near future.

Hello, as we are moving most of current discussion to Github Dicussions, feel free to open a discussion there : https://github.com/gothinkster/realworld/discussions/categories/ideas


Conditionally rebuild artifacts from watch

Currently, all artifacts are rebuilt after one source file changes, and changes during the build and deploy pipeline are ignored.

Instead of triggering a build on the first change event, we could wait for say 500ms and trigger a build only if no event has been received since.
Then we need to decide if a build should be interrupted in a change event occurs after it's started.

@r2d4 This should be fixed now, right?


Format Exception

I am having problems with format exception on following Cookie:
ISAWPLB{21B8A963-08B8-4182-BB62-95CD0CEEE9DC}={68CF861A-E382-45D6-BC7C-9FFB87B95834};
I am not an Administrator to the Website which Cookies I need, so I can not change format.
However I desperately need this Plugin to read the httponly cookies. But thanks to the exception I can not access them.
Any way around this?

Unfortunately, I don't have time to check it now.
Feel free to fork the library and provide PR.

Unfortunately, I don't have time to check it now.
Feel free to fork the library and provide PR.

@albatrosify Is the issue still happen?

Close, no activity


Best practise for contributing

Is there any guide for GVM2 contributing?
I'm trying to setup GVM_ROOT=/path/to/my-forked-rep/gvm2.git in order to create new features, however I'm getting the error:
ERROR: Looks like the .git directory is present. Please reinstall GVM.
Any advises, hints?

Hi @markeissler , any recommendation about it?

Is there any guide for GVM2 contributing?

Not yet. I still have some functionality upgrades planned.

ERROR: Looks like the .git directory is present. Please reinstall GVM.

Is this a new install or are you upgrading GVM? Try renaming the .git file to .git.bak.

Is this a new install or are you upgrading GVM? Try renaming the .git file to .git.bak.

I trying to use the gvm2 cloned repository from GitHub, in order to create modifications under git control, as usual ... For that I am pointing the environment variable GVM_ROOT to this local cloned repository, I mean:
export GVM_ROOT=/home/user/dev/gvm2  ==> cloned repository from GitHub
If I move .git to .git.bak, I can not use the git commands.
Probably the best way to create modifications to GVM2 is working directly with the installed GVM2, I mean working directly with the folder installed by GVM2 ($HOME/.gvm), and copy these modifications to the cloned git repository.

Sorry for the late response. The installer isn't ideal right now and the whole moving of .git to .git.bak is a task performed in the original installer. Actually, the original GVM will actually check for and rename .git to .git.bak every time a gvm command is run (IIRC).
While it's convenient to modify the in-use GVM2 it could also be problematic. One thing you might have to do is re-source the GVM commands whenever you make changes:
source "$HOME/.gvm/scripts/gvm"

Perhaps a better strategy for you would be to make changes in the running GVM2 and then copy those changes into a proper GVM2 repo (in another directory) if the changes are successful to what you want.
One of the ways that I develop is using a VM or docker container to avoid side effects that may be present in my own environment. The final test, of course, is the CI environment.

As I close this I just want to leave this final note: it is highly likely that when I replace the gvm installer that I will move to a system where GVM2 is no longer installed via git but is instead installed as a package (tar) download. This will make updating simpler and at the same time remove unneeded commit histories from user machines.


ARMA: Signal processing for peaks

Issue Description
The ARMA can currently handle a wide variety of input signals.
One it is poorly suited for, however, is intermittent periodic peaks (for example, a relatively flat signal with a singular spike every 25 entries), especially if the peak widths are small (1-2 entries).
In order to capture this punctuating effect, additional development is needed in the ARMA signal processing methods.
Furthermore, the ARMA should probably be renamed to StochasticSignalProcessingHistory or something, since it is expanding beyond just the ARMA algorithm.
This is a high-priority task due to needs in HYBRID program milestones this year.

For Change Control Board: Issue Review
This review should occur before any development is performed as a response to this issue.

[x] 1. Is it tagged with a type: defect or task?
[x] 2. Is it tagged with a priority: critical, normal or minor?
[x] 3. If it will impact requirements or requirements tests, is it tagged with requirements?
[x] 4. If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
[x] 5. Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)

For Change Control Board: Issue Closure
This review should occur when the issue is imminently going to be closed.

[ ] 1. If the issue is a defect, is the defect fixed?
[ ] 2. If the issue is a defect, is the defect tested for in the regression test system?  (If not explain why not.)
[ ] 3. If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
[ ] 4. If the issue is a defect, does it impact the latest release branch? If yes, is there any issue tagged with release (create if needed)?
[ ] 5. If the issue is being closed without a pull request, has an explanation of why it is being closed been provided?

In a discussion with @JiaZhou-PU, we came up with an idea for handling the peak behavior, somewhat similar to the zero-filtering but with less discarded data:
For training the data:

Split the data into values below and above an arbitrary level (ideally to pick out peaks). This could be split multiple times for multiple bands of peaks, with one band including the residual noise.
For each band not including the no-peak band:

Record the periodicity of the peaks in this band, making a PDF of them for future sampling.
Collapse the parts of the signal containing no information (non-peak portions).
Use FFT to discover the applicable peak transform to a user-given coverage.
Removing the FFT from the band signal, use the ARMA to train the residual noise in this band.
Store the trained ARMA, FFT properties, period histogram, and filter masks for use during sample generation.

For evaluating the data:

For each peak-containing band:

Sample the ARMA to create "noise" for the peaks
Add the Fourier data from the FFT to create full peaks
For each filtered original location of the peaks:

Sample from the period history to determine the location of the next peak
Insert the portion of the peak signal corresponding to each peak into the signal

We found some potential concerns with this process (peak widths, ARMA p and q, appropriate FFT coverage levels) but it should be a good start to addressing this issue.

archived


[Feature][doc] Modify the document markdown display style

Modify the document Display style is abnormal

link address:
https://github.com/apache/incubator-dolphinscheduler-website/blob/master/docs/zh-cn/1.3.1/user_doc/configuration-file.md
https://github.com/apache/incubator-dolphinscheduler-website/blob/master/docs/zh-cn/1.3.2/user_doc/configuration-file.md
https://github.com/apache/incubator-dolphinscheduler-website/blob/master/docs/zh-cn/1.3.3/user_doc/configuration-file.md
https://github.com/apache/incubator-dolphinscheduler-website/blob/master/docs/zh-cn/1.3.4/user_doc/configuration-file.md

@CalvinKirs  You can assigned me.

@CalvinKirs  You can assigned me.

Assign it to me so I can familiarize myself with the PR process


Mojave support

Is there anything preventing SAP from using 5.1 to enable Mojave compilation?
// swift-tools-version:5.2

Some of the property wrapper initializers crash the Swift 5.1 compiler — it may be possible to work around this, but I haven't found a strategy yet.

Part of me wants to push because command-line utilities are one of the most basic and least OS release-sensitive things we build and part of me doesn't want to cause you more work. It seems wrong that writing simple effective cmdline utils aren't backward compatible.

@erica that sounds more like an argument for Swift to have matured decades ago, rather than a reason to have this particular library support Mojave

@erica so did you fix this issue or will talk me about plan for it?


Ui revamp archermalmo

archer malmo update to the ping pong UI. Mostly html and css changes with a few js updates. Still working on a few things including:

further tightening of the layout for all pages
creating a new view for the add/edit check screen
if we have time we are also going to look at adding some CSS preprocessing.

These changes look good. I will merge this when I finish the incident stuff I'm working on!


TickLabels not aligned with grid

I would like to have the tickLabels aligned vertically on the left of the ticks. This seems to be the default behavior in the examples from docs, but does not happen in my case. Instead they are aligned below the ticks for some reason. Adjusting offsetY or padding does not seem to do the trick.

Sample code:
        <VictoryChart
          data={sampleData}
          width={WINDOW_WIDTH-32}
          height={200}
          domain={{ y: [0, 7]}}
          padding={{top: 25, left: 25}}
          theme={VictoryTheme.material}>
          <VictoryAxis
            tickLabelComponent={<VictoryLabel textAnchor="start" />}
            dependentAxis={true}
            style={{
              axis: {
                stroke: "none",
                strokeWidth: 0.5
              },
              axisLabel: {
                fontSize: 20,
              },
              grid: {
                strokeDasharray: "",
                strokeWidth: 0.5,
                strokeOpacity: 0.25,
                fill: "#fff",
              },
              ticks: {
                padding: 0,
                stroke: 'red',
              },
              tickLabels: {
                fill: '#fff',
                fontSize: 8,
                fontFamily: 'open-sans-light',
              }
            }}
          />
          <VictoryLine
            style={{
              data: {
                stroke: "#fff"
              },
              parent: {
                border: "1px solid #fff"
              }
            }}
            data={sampleData}
          />
          <VictoryScatter
            style={{
              data: { stroke: "#fff", fill: "#fff", strokeWidth: 3 },
              parent: { border: "1px solid #fff" }
            }}
            data={sampleData}
          />
        </VictoryChart>

Any idea why is this happening? I am using v0.17.0

In fact I just tried to copy-paste code from docs here: http://formidable.com/open-source/victory/docs/victory-line/#domainpadding and the results are not the same:
Left is my app, right is the docs (ignore the background color difference):

HI @Elijen. There is an issue with text placement that occurs when your version of victory-native is used with an incompatible version of react-native-svg. Please check the version requirements.

@boygirl Thanks, I am using Expo and it indeed seems they are using a wrong react-native-svg version.

@Elijen yeah, I think they may still be on<EMAIL_ADDRESS>Depending on what you need from victory-native you could use<EMAIL_ADDRESS>with expo


Watermelon stomach

Watermelon stomach
Gastric antral vascular ectasia (GAVE)
Gastric antral vascular ectasia (GAVE) is a [rare disorder that causes severe acute gastrointestinal bleeding. Also known as watermelon stomach, due to its endoscopic appearance,  this condition is marked by dilated capillaries localized to the antrum that give the appearance of watermelon streaks. The dilated vessels render the affected areas more susceptible to bleeding. Even though the cause is still unknown. The number of cases in the general population is not known but is rare.  It occurs in about 4% of non-variceal upper GI bleedings and 6% of upper GI bleeds in patients with liver cirrhosis. The exact cause is unknown; however, it is often associated with several conditions such as cirrhosis and autoimmune diseases,  systemic sclerosis, and CREST syndrome. GAVE has become a distinct entity with established co-morbid conditions. Treatment can be done with endoscopic coagulation of the lesions.
https://www.sciencedirect.com/science/article/pii/S2210261222007209
https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8110233/
https://www.sages.org/wiki/gastric-antral-vascular-ectasia/
Parent term: Rare hemorrhagic disorder
Thank you, Gioconda

Hi Gioconda,
This term already exists in Mondo:
MONDO:0006767
Was your intention to request a new term?
Thanks,
Nicole

Hi Nicole!  I am very sorry I was not clear.  I was trying to find out why this one is not tagged as rare in MONDO (I see it in GARD but not in Orphanet) and the literature does support it is rare.
I apologize for the confusion. Thank you, Gioconda

Sounds good! @sabrinatoro could you please add a rare tag?


HEADER cells are placed in an organized fashion

I wrote a tcl proc in the detailed place tcl script which loops through all cells with a specific name and place them semi-stacked on top of each other based off a row option given. The parameters I gave to this proc to place the HEADER cells is "10" and "HEADER".
I also removed useless pauses in the script. There were several time.sleep() which seem to serve no purpose and add 11 seconds to each complete run of tempsense gen.
Let me know if I need to make any changes. The changes I made in this PR were tested using Obed's fork.

@lulu9312 Can you try this on the LDO as well.


created traefik tls file for prod and block tls 1.0 and 1.1

Adds a second tls.yml file for production sites so that prod and dev can have separate options.
Also sets the minimum TLS version for production to 1.2 in order to block TLS 1.0 and 1.1 on production sites.
To test this, there should be no change to dev sites, but spinning up a production site with this PR should cause TLS 1.0 and 1.1 to be disabled. You can test it using something like https://www.ssllabs.com/ssltest/index.html

Looks like Traefik automatically blocks TLS 1.0 and 1.1 in newer versions, but this might still be worth merging for anyone who wants to be able to edit other traefik options in production.
We could also use this to specify the cipher suites for increased security, which may be worth setting as a default.

Also specifying the cipher suites used. I based this on a scan using SSL Labs.
The last two ciphers show as weak, but were needed for supporting older versions of Safari and IE


Immediate retry instead of delayed

Removed FailCollector and all its related stuff
Removed PrivateEvents.CRITICAL_ERROR and its handler in BrowserRunner
Added InsistentSuiteRunner - wrapper for RegularSuiteRunner which decorates it with retry logic.
BrowserAgent now will be created for each SuiteRunner and will never return same session twice

@sipayRT @eGavr @tormozz48 @SevInf
В двух словах че сделал: просто снес логику про ретраи с уровня  верхнего раннера, до враппера над SuiteRunner'ом.
Из 700 строк где-то 550 - это тесты

Coverage decreased (-0.1%) to 83.729% when pulling 5a64552d7acd95b8efe1067e451dce6b6369fc01 on feature/immediate.retry into 3eae59032adefcacb23a45a38222a33517ba54e4 on master.

Coverage decreased (-0.1%) to 83.729% when pulling 5a64552d7acd95b8efe1067e451dce6b6369fc01 on feature/immediate.retry into 3eae59032adefcacb23a45a38222a33517ba54e4 on master.

Coverage decreased (-0.1%) to 83.87% when pulling 2fcb35d6685dbb2d903130ad5a95a92713632be2 on feature/immediate.retry into 4ca84e54d04c1bb1f86afffa9a6e633ec5a30262 on master.

Coverage decreased (-0.1%) to 83.87% when pulling 2fcb35d6685dbb2d903130ad5a95a92713632be2 on feature/immediate.retry into 4ca84e54d04c1bb1f86afffa9a6e633ec5a30262 on master.

Coverage decreased (-0.1%) to 83.87% when pulling 75eee0ee09891272a15622edcf4969877aef103f on feature/immediate.retry into 4ca84e54d04c1bb1f86afffa9a6e633ec5a30262 on master.

Coverage decreased (-1.2%) to 82.797% when pulling b595f7a6c786e117680ba4bccbfd8a9bade7890d on feature/immediate.retry into 4ca84e54d04c1bb1f86afffa9a6e633ec5a30262 on master.


Get|Set-AtpPolicyForO365 -EnableSafeLinksForWebAccessCompanion <$True|$False?

It appears that you cannot set the EnableSafeLinksForWebAccessCompanion property when using Set-AtpPolicyForO365. I have one tenant that has this set to $True somehow and the rest I'm seeing it's $False. Where does this property map to when using the Web UI and can this switch be added so that we can manage it?

https://github.com/MicrosoftDocs/office-docs-powershell/commit/f8ac0ea19347127f6e60d12c592134b7a54b3743
I see this states it is for internal use but it doesn't explain why one tenant is true and the other is false. Does this switch tie to some UI element but not available via PowerShell?

@officedocsbot assign @yogkumgit

@CraigUpic Thank you very much for posting this issue. Considering the nature of the issue, it is advised that please open a service ticket in your tenant and follow with them for the resolution. If you wish to know how to open the service ticket, please follow this link:            https://docs.microsoft.com/office365/admin/contact-support-for-business-products
We will be very happy if you can share the outcome or resolution with us. We will certainly update this documentation with that valuable information. Thanks again, for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.

@officedocsbot close


fix(sqlx-cli): do not clean sqlx during prepare

Description
Fix cargo sqlx prepare --workspace running cargo clean -p sqlx unnecessarily.
See https://github.com/launchbadge/sqlx/issues/2785
This should be a non-breaking change. It shouldn't affect in-workspace dependencies that happen to be named sqlx either.
How to test or review this PR

Checkout this branch and install sqlx-cli.

cargo install -f --path ./sqlx-cli

Run cargo sqlx prepare --workspace in a project with crates that use query! macros.

The timing difference is quite significant in a larger workspace, saves 43 seconds on an incremental build.
BEFORE:
$ time cargo sqlx prepare --database-url "postgresql://postgres:password@localhost/example" --workspace -- --all-targets --all-features
    Cleaning [=============================] 1/1: sqlx, 0 files/folders cleaned
...
    Finished dev [unoptimized + debuginfo] target(s) in 19.83s
query data written to .sqlx in the workspace root; please check this into version control
make sqlx-prepare  80.33s user 28.84s system 138% cpu 1:18.64 total

AFTER (this PR, note there is no cleaning step):
$ time cargo sqlx prepare --database-url "postgresql://postgres:password@localhost/example" --workspace -- --all-targets --all-features
...
    Finished dev [unoptimized + debuginfo] target(s) in 15.88s
query data written to .sqlx in the workspace root; please check this into version control
make sqlx-prepare  36.71s user 13.13s system 260% cpu 19.155 total

The unit test is failing because it checks that the sqlx dependency is marked to be cleaned. This seems unintentional, as the original PR for that test mentioned sqlx was intended to be ignored: https://github.com/launchbadge/sqlx/pull/1802#issuecomment-1099801198

The only reason we clean anything in the first place is it seems like the only surefire way to force a recompile so that the proc macros actually execute. If you have any thoughts there, we could get rid of the cleaning entirely.

Would the fix maybe be just cleaning workspace crates? Or just the current crate?

Ignoring non-workspace crates seems fine to me. Those should be prepared separately.

@cycraig sorry for such a long delay on getting back to this, I tend to forget about PRs when they get pushed to the second page. Out of sight, out of mind and all that.
What do you think of this:

cargo sqlx prepare: clean all workspace crates that depend on sqlx
cargo sqlx prepare --all: clean all crates in graph that depend on sqlx

One thought is we could parse dep-info to know when a crate uses the macros. If you call env!() or option_env!() in a crate, it records in the dep-info that you have a dependency on that environment variable. We wouldn't even need to be able to parse the dep-info format in case it changes; we could just search for the environment variable name if it's unique enough. We could start with the crates that depend on sqlx and use this to filter.
It would be possible to trigger recompiles with this directly, e.g. by emitting something like option_env!("SQLX_RECOMPILE_TRIGGER") and setting that to a unique string every time cargo sqlx prepare is run. I remember trying that before but at some point I abandoned that approach, I think because it triggered a rebuild when the compiler was run without it and that got annoying. I also vaguely recall that it wasn't all that reliable.

At the end of the day, my concern is that cargo sqlx prepare should do what most people are going to expect it to do.
From a Cargo perspective, I suppose cargo sqlx prepare should be expected to prepare only the current crate, and cargo sqlx prepare --workspace obviously would do workspace crates. In this way, the mental model could be that it casts the smallest net possible, and then there are flags to widen that net.
But that has a couple problems:

The constant friction from having to remember to specify --workspace in more complex projects.
The lack of a clear winner for a flag to say "prepare all crates in the graph that might need it".

You make a good point that --all is a little too ambiguous, but 5 alternatives and I'm not enamored with any of them except maybe --all-deps.

Instead, we could approach it from the other direction: cargo sqlx prepare casts the broadest net necessary by default, and then we have flags to narrow that scope:

cargo sqlx prepare re-runs the macros for all crates in the graph that last ran them in online mode (I have an idea of how to select for this; see below)
cargo sqlx prepare --workspace restricts to just workspace crates

For most use-cases, this case and the previous case are equivalent.

cargo sqlx prepare -p <pkgspec...>  to prepare specific crates.

While thinking about this, it occurred to me, "well duh, why don't we use files?" We can create them in the macros if they don't exist and use include_bytes!() in the output (or proc_macro::tracked_path::path() if/when it's stable) to add them to the watch list.
We can get all the selectivity we really need with three include_bytes!() per macro invocation:

<target directory>/sqlx/recompile-all

Emitted by all macro invocations

<target directory>/sqlx/recompile-workspace

Emitted by macro invocations from workspace crates only

$OUT_DIR/sqlx-recompile

Unique path for every crate, but the file will only exist for ones that touch macros.

The contents of these files is irrelevant; I'd probably make it a timestamp. In release mode, they should be optimized out anyway.
What cargo sqlx prepare would then do is update the appropriate file(s) (change its contents and update its mtime) for a given selection:

cargo sqlx prepare would touch <target>/sqlx/recompile-all;
cargo sqlx prepare --workspace would touch <target>/sqlx/recompile-workspace;
cargo sqlx prepare -p <pkgspec>... would touch $OUT_DIR/sqlx-recompile for each matched package;

then run cargo check for the same specification. This should pretty reliably trigger recompilation, and only for the relevant crates. This would also keep incremental compilation artifacts which would otherwise be discarded with the cleaning approach.
What do you think?

@cycraig have you seen my last comment?

The constant friction from having to remember to specify --workspace in more complex projects.

The --workspace flag is usually added to a Makefile/CICD pipeline once and forgotten about, so I don't think it's a significant pain point. Such projects typically need -- --all-targets --all-features too, which would not change with the proposed solution.

why don't we use files?

I'm hesitant to encourage another filesystem-based solution given the friction some developers experience with non-standard directories, e.g. https://github.com/launchbadge/sqlx/issues/1706, https://github.com/launchbadge/sqlx/issues/2395. Just saying there will likely be some teething issues.

We can create them in the macros if they don't exist and use include_bytes!() in the output (or proc_macro::tracked_path::path() if/when it's stable) to add them to the watch list. [...] The contents of these files is irrelevant; I'd probably make it a timestamp. In release mode, they should be optimized out anyway.

It would be nice to benchmark the impact of include_bytes!(), if that's the only implementation option currently. The content may be negligible, but it would be nice to confirm the file handling and including bytes for hundreds to thousands of queries doesn't negatively impact developer experience.
It also sounds a bit like invoked.timestamp. Not sure if there's any extra insight to be gained from looking at how fingerprints work.
https://doc.rust-lang.org/nightly/nightly-rustc/cargo/core/compiler/fingerprint/index.html#fingerprint-files

An invoked.timestamp file whose filesystem mtime is updated every time the Unit is built. This is used for capturing the time when the build starts, to detect if files are changed in the middle of the build. See below for more details.

This should pretty reliably trigger recompilation, and only for the relevant crates. This would also keep incremental compilation artifacts which would otherwise be discarded with the cleaning approach.

Thoughts: avoiding cleaning dependencies was the initial issue in this PR, and doing that with no manual configuration is certainly attractive, assuming the approach works reliably. I'm just a bit risk averse to potentially introducing a "cure worse than the disease" for a speedup of cargo sqlx prepare.
Excluding sqlx from the clean step in sqlx prepare, as done in this PR, is an easy 1-line change that would benefit all sqlx users, with no drawbacks that I know of. That commit could be merged independently (removing the --all flag commit) while the more robust solution to avoid unnecessarily cleaning other dependencies that use sqlx (pgvector etc.) is implemented. Unfortunately I'm not currently in a position to contribute.

You make a good point. I've accepted the change as-is.


tf.reshape fails for Tensor with valid shape parameter

I don't know if my problem is truly a bug with TensorFlow, but I think it is. My problem is that tf.reshape(x, shape=(sequence_length, 4)) fails even when x is a tensor and the shape provided is valid. Reshape returns the following error: TypeError: List of Tensors when single Tensor expected
Some background: I have a number of CSVs that I converted to SequenceExamples and stored as TFRecords to use to train dynamic RNNs. The length of each sequence can vary. I can successfully read the SequenceExamples using parse_single_sequence_example, which returns a tensor of shape (?,) for each of my four feature tensors and each of my four label tensors. I then stack the four feature tensors to create x with shape (?, 4) and type <class 'tensorflow.python.framework.ops.Tensor'>. I create a similar tensor of labels y with shape (?, 4) and type <class 'tensorflow.python.framework.ops.Tensor'>. Everything is good.
Then, I'd like to create minibatches based on similar length sequences using tf.contrib.training.bucket_by_sequence_length, but if I pass in input_length=x.shape[0], I receive the following error: ValueError: Cannot convert an unknown Dimension to a Tensor: ?. Since I know the sequence length when creating the SequenceExamples, I modified my code to add the sequence length (an integer) as a context feature. Then, when I read my features and labels, I try to reshape them as follows:
        sequence_length = context_parsed['length']
        tf.reshape(x, shape=(sequence_length, 4))

where sequence_length has type <class 'tensorflow.python.framework.ops.Tensor'> and shape (). This raises the following error: TypeError: List of Tensors when single Tensor expected. However, x is a Tensor, not a list of Tensors. This is why I think there may be a bug in TensorFlow's tf.reshape() function.
My TensorFlow version: TensorFlow version: v1.2.0-rc0-24-g94484aa 1.2.0-rc1
If it helps, I could post one of my .tfrecord files and the code necessary to create this error.

I'd suggest first asking on StackOverflow, because I strongly suspect you are constructing things with a small mistake. I'd suggest posting full code of a reproducible example, and try to make it as small of an example as possible. Can you reproduce it without tfrecord to remove that variable. Breaking the problem into smaller pieces like this will likely make it clearer.  Please use the template in the future. Closing for now.


Update h2 sync scripts

This updates the http2 sync scripts to reflect the change from corefx to runtime.
These updates were already checked into runtime several weeks ago.
https://github.com/dotnet/runtime/commit/e90b018a3b9f8f1df910a6c41522eaa860c753ac#diff-304f89275bebf5246bd7d395f2bae195

/azp run


Update to CAPI 1.8

/kind feature
Describe the solution you'd like
Update to CAPI 1.8 and bump all related dependencies.

This means we need to update controller-runtime. I suggest aligning with capi and use version 0.19.
Unfortunately we use controller-runtime 0.17.x at the moment. Version 0.18 introduced typed (generic) functions, and the transition is not trivial.
Related: https://kubernetes.slack.com/archives/C02MRBMN00Z/p1713976216050739
I am working on it.


Crates giving stone as a prize along with the actual prize

https://hastebin.com/ubehodapij.bash
My file is basically the same as the default one but the player gets given stone as well as their prize. This happens even when I've removed items and give the prize using commands instead.

The prize is set to give prot4 armour pieces and instead gives the player prot4 stone. The same thing happened with the demo config - cheap helmet is a p1, aqua affinity 1 block of stone.

CC version and MC server version?
/version crazycrates


working with mxnet=1.3.1, upgrading numpy version from 1.14.5 to 1.17.1 causes memory issues

I am working on Ubuntu 18.04.2 LTS machine, with  mxnet==1.3.1 and numpy==1.14.5 installed.
Upgrading numpy version from 1.14.5 to 1.17.1 causes severe memory issues.
#data is from type mxnet.ndarray.NDArray
data = data.asnumpy()
data2 = data.copy()
the code takes significantly more memory with  numpy==1.17.1 than it does with  numpy==1.14.5,
which causes my program to crash from memory overflow.
upgrading mxnet from version 1.3.1 to 1.5.0 makes no difference.
can you please advice?

So this only happens with numpy arrays that originate from mxnet?

Yes.
On Mon, Mar 16, 2020, 20:34 Leonard Lausen<EMAIL_ADDRESS>wrote:

So this only happens with numpy arrays that originate from mxnet?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/apache/incubator-mxnet/issues/17847#issuecomment-599696673,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALRJMNJQHXCJ6I2UXWKRIDDRHZWKHANCNFSM4LMKRANQ
.


Make the dca learning rate accessible from scanpy.

scanpy currently does not allow to select the dca learning rate.
This can create convergence issues (for example dca diverges 60% of the time on Tabula Muris when trained on CPU, but oddly enough converges when trained on GPU)

Makes sense, thank you!


Password Reset Request Failure

Go to User/pass login screen, enter valid User Name and click Forgot password?.
URL changes to <CorrectFQDN>/s/resetPasswordRequest, showing blank white screen and no email is received.

Work around:   Reset your password via the User screen.

Replaced by https://github.com/gchq/stroom/issues/4008


[rpc] Add createauxblock and submitauxblock back to RPC

Fixes #2630

Adds Namecoin's createauxblock and submitauxblock RPC methods back to allow easier integration for mining pools that wish to reuse existing implementations of Namecoin/Bitcoin merge mining. I pulled this in from the WIP at michilumin@1c5b9b3, and fixed it up where needed:

Fixed issue with erroneously moved LOCK from getauxblock - the lock was moved outside of the function call
Disabled mining of witness tx as done for getauxblock
Fixed indentation, increasing readability and fixing warnings (from compiler)
Follow Dogecoin API for target instead of _target - to keep at least the baseline consistent with itself
Removed personal comments / annotations - they didn't add anything that git blame doesn't do.
(added a bit more body to the commit message)
Full changes can be seen by doing a git range-diff 1c5b9b3...c2532d3

Did some further cleanup to rpc/mining.cpp and made getauxblock a little easier to read by indenting the creation routine - this should help with review by making the comparison of each creation function easier.
Implements extensive testing for createauxblock and submitauxblock methods without defaulting to these new methods in all tests (getauxblock is still the most reliable method we have right now.)
Cherry-picked the diff with btccom@f4b613b as part of this PR because while writing the tests, it turned out that all the address parameter to createauxblock was doing was creating a race condition to populate the cache unless only one address was used, so I now consider that to be a must-have.

I will propose a solution to supporting _target instead of target fields in all 3 auxpow methods separately, as that may see some discussion and should not hold this up.

ACK!


New Main App design

📒 Decision
This PR will introduce new Main App design as well as the change from NSTableView to NSCollectionView.
Why do I select NSCollectionView than NSTableView
After preliminary experiment, our NSTableView has many limitations which we have to overcome by doing tricks if we would like to implement 100% new design.
Here is the list of reasons:

Shadow underneath of cell

I tried to support Shadow in TimeEntryCell (NSTableView), but it turns out that the shadow of one cell will overlap with next cell -> The shadows is darker in top and bottom, but less in left and right.
NSCollectionView is capable of adding DecorationView, which is underneath of each section, so it's pretty easy to draw a shadows without messing with another section.

Header

NSTableView doesn't support native Header, so currently, we have both same class (TimeEntryCellWithHeader and TimeEntryCell)
NSCollectionView officially supports Header as a supplement view. So it's easier to implement TimeEntryHeader and TimeEntryCell separately.
Additionally, it's easier to implement the collapsible section because TimeEntryHeader is different view.

TimeEntryCell

TimeEntryCell is now separated with Header, so there is no duplicated code / design if comparing to old solution (NSTableView)

Section Inset

NSTableView is impossible to support section inset, since every row will render sequently or we have to do many tricks, which I'm totally discouraged.
NSCollectionView officially support section inset from NSCollectionViewFlowLayout.

Left/right top and left/right bottom corners

NSTableView cell is super difficult to support Left/Right Top corner in the first cell in section and left/right bottom for the last cell in section.
By introducing the DecorationView, it's super easy, because we only have to round 4 corners.

Row / Section data structure

If we look around the design, it easily recognize that the pattern of EntryTimeList must be section-based list.
NSCollectionView support section by default. Otherwise, NSTableView isn't

Collapsible Section

If we have TimeEntryHeader, it's straightforward to implement collapsible Section, since the header view and the cell are different.
NSCollectionView do section very well, not NSTableView.

=> I made decision to move on our old list to NSCollectionView, so we could respect our design and easier to implement new feature.

🕶 Types of changes
Breaking change (fix or feature that would cause existing functionality to change)
🤯 List of changes

[x] Drop out NSTableView and adopt NSCollectionView for Time Entry List
[x] Support TimeEntryCell, TimeEntryHeader
[x] Implement new design for TimeEntryCell and header
[x] Introduce Decoration View for shadows and corners.
[x] Drag and drop
[x] Migrate all old logic to new one
[x] Support Dark-mode and complex hover state for cell
[x] Introduce TimeEntryDataSource, which is responsible for categorize the array of TimeEntryItem to section-based structure.
[x] Remove unnecessary code from NSTableView

Known-issue

[x] Keydown func is conflicted with didSelectedItem (fixed with
https://github.com/toggl/toggldesktop/pull/2831/commits/7c0f11be5ba28318f2fd46644fdd94a82c4c07a7)
[ ] Differ - DeepDiff doesn't support section-based diff.
[x] Image of cell during dragging doesn't work with Darkmode (Background of cell is white color)
[x] Strange jump after closing the Popover

👫 Relationships
Close #2813
🔎 Review hints

Double check all logics

Skeleton

Fixed the conflict successfully, pls make sure you guys check out the branch from origin 👍

Basically, this PR is ready for reviewing (except Diff func, it should be separate ticket) 👍

On first load the listing is not rendered correctly. Lines between rows are from side to side and the hover color is also larger than the list. After a reload it looks ok again.

After app start it is not possible to edit running entry.
Scenario:

Start app
continue an entry from past
Try to click on an entry to edit it
Nothing happens
The app fails at this spot in TimeEntryListViewController.m
https://github.com/toggl/toggldesktop/blob/cb7a324984b9ebd1811aab13189c7df955d6b4e8/src/ui/osx/TogglDesktop/TimeEntryListViewController.m#L244

clickedIndexPath is nil when triggered from timer

[ ] When editing the date of the time entry the popup does not point to the correct time entry row after edit.
[ ] App always shows billable icon in entry item (even when billable is false)
[ ] When deleting the last item of the day I got error

Fatal error: Index out of range

Probably removing section is not handled correctly
in let sectionItem = sections[section]
extension TimeEntryDatasource: NSCollectionViewDataSource, NSCollectionViewDelegate, NSCollectionViewDelegateFlowLayout {

    func numberOfSections(in collectionView: NSCollectionView) -> Int {
        return sections.count
    }

    func collectionView(_ collectionView: NSCollectionView,
                        numberOfItemsInSection section: Int) -> Int {
        let sectionItem = sections[section]
        if sectionItem.isOpen {
            return sectionItem.entries.count
        }
        return 0
    }

[ ] Unsunced icon missing from entry item

Unsynced icon missing from entry item
This icon intended to support in "New design of System Message" (https://github.com/toggl/toggldesktop/pull/2837).

On first load the listing is not rendered correctly. Lines between rows are from side to side and the hover color is also larger than the list. After a reload it looks ok again.

I couldn't reproduce this issue, do you remember how to trigger that? I tried to open TimeEntryList after logging, start/stop (no running entry), start/stop with running entry, but I couldn't 🤔

After app start it is not possible to edit running entry.

This one too, it seems that both issues were gone.
Additionally, I fixed couple bugs above and leave comment about the "Error icon in Time Entry Cell".

It's ready for reviewing in second round @IndrekV, please make sure remove your current branch and checkout the feature/design-app-window from origin, because I rebased in order to resolve the conflict from master 👍

After app start it is not possible to edit running entry.

This is still broken. I'll add gif to demonstrate the issue. When I move the mouse over the running entry when it runs I click on it multiple times to start editing.

Scenario:

Start app (with no running time entry)
continue an entry from past
Try to click on the running entry to edit it
Nothing happens
The app fails at this spot in TimeEntryListViewController.m
https://github.com/toggl/toggldesktop/blob/cb7a324984b9ebd1811aab13189c7df955d6b4e8/src/ui/osx/TogglDesktop/TimeEntryListViewController.m#L244

clickedIndexPath is nil when triggered from timer

Also can we not make the login page background image be visible as the scrollbar background.

Jep the last commit fixed the edit popup opening issue. Good Job!

Tested out keyboard shortcuts in the listing view and some functionalities are not working properly.
All keyboard shortcut logic in mac is described in the bottom of the article here: https://support.toggl.com/desktop-apps/toggl-desktop-for-mac

[ ] Pressing SPACE will not start the selected entry from the list
[ ] Moving up in entries list. When the selection goes from one day to another it will jump to the first item of the section. It should be the last item of the day to make it smooth.

@NghiaTranUIT I want your feedback on https://github.com/toggl/toggldesktop/pull/2831/commits/f97f93bb89e2f7bc1cdc5eee28d98c37a7e0cb1f
I had to use a variable to store the last selected indexPath because for some reason the collectionView inside the shouldSelectItemsAt was always NULL and had no info about selected indexes.

One more issue that occurred.

[ ] When you delete an item in list the selection is not update to the previous item. The list does not have a selected item anymore. It should probably be handled in setFirstRowAsSelected method inside TimeEntryCollectionView

When you delete an item in list the selection is not update to the previous item. The list does not have a selected item anymore. It should probably be handled in setFirstRowAsSelected method inside TimeEntryCollectionView

I fixed it in
https://github.com/toggl/toggldesktop/pull/2831/commits/0259004db2b80d6fbc2eee4345edeac168d2afc3. However, after re-selecting the previous cell, the CollectionView isReloading and lost the current selection.

I like the improved solution for moving up in the list. Good job @NghiaTranUIT

Opening and closing groups with keyboard (pressing LEF/RIGHT) loses selected item highlight. On both cases the selected item should remain the same as before the action.

List sections rendering issues. It's same issue I noted before https://github.com/toggl/toggldesktop/pull/2831#issuecomment-471495721
It seems that with updates to the listing structure the loading of the margins is broken.
In the gif I click on grouped items to open and close the group. When all scrollbar is shown or hidden the rendering breaks. Sometimes is rerenders and fixes the issue in few seconds. If you resize the window it also re-renders and fixes it.

Another point. The background color of selected item and the subitems in group are the same, they should differ a bit so that user understands when they are highlighting the grouped subitem. I suggest we make the subitems a bit lighter (in dark mode) than the unselected item.

This
https://github.com/toggl/toggldesktop/pull/2831/commits/478fb5270bb5fc5fa65a9e8c95a2ef9d060aa648 fix the UI issue from https://github.com/toggl/toggldesktop/pull/2831#issuecomment-473281341.

@IndrekV All bugs are gone 🥇 It's ready for next review phrase 😍
When you're happy with it. Please let me know, I will squash some unnecessary commits before merging. Then I will continue to rebase next PR to make it clean and reviewable.

Change-logs (from last review)

Fix jump bug
Lighter background for selected Sub-Item cell
Keyboard func works (move up/down and delete (re-select cell after deleting))
Scroller bar UI issue

Good Job! @NghiaTranUIT


Rename ExpectViolation to ExpectOffense

I'd like to upstream this to RuboCop soon!

Drops dependency on concord
Drops dependency on anima
Drops dependency on adamantium

See also bbatsov/rubocop#3905

@dgollahon WDYT? I'd be open to a PR that makes the classes a bit bigger if you are interested but I personally don't want to do that right now 😆.

@dgollahon WDYT?

I think the renaming makes sense. Why'd you decide to remove the dev dependencies? Was it for moving to rubocop? Because otherwise I think having lightweight dev dependencies is pretty harmless.

I'd be open to a PR that makes the classes a bit bigger if you are interested

WDYM?
If you're talking about general changes to this, I think one of the biggest things to do would be to make error messages more reasonable (maybe using some rspec features would be helpful?). It can be a bit frustrating to debug some cases.

@dgollahon yeah I'm trying to eventually upstream this to RuboCop. See bbatsov/rubocop#3905. That is the reason for the rename and the dev dependency removal.

I'd be open to a PR that makes the classes a bit bigger if you are interested
WDYM?

If you're talking about general changes to this, I think one of the biggest things to do would be to make error messages more reasonable (maybe using some rspec features would be helpful?). It can be a bit frustrating to debug some cases.

Well I figured that you'd probably agree this has "tiny class syndrome." Was just preempting discussion about reducing that

Well I figured that you'd probably agree this has "tiny class syndrome." Was just preempting discussion about reducing that

Ah, yeah. Since this wasn't new code or a directed refactor I didn't really think nitpicking the implementation was terribly important. The object could probably be improved but that doesn't have to be done right now.


A certain PDF is not rendered only on iOS

The attached PDF is not rendered properly only on iOS. It's OK for other platforms.
Attach (recommended) or Link to PDF file here:
not-rendered-properly-on-iphone.pdf
Configuration:

Web browser and its version:
Chrome, Safari

Operating system and its version:
iOS 13.3.1

PDF.js version:
v1.9.426
v2.2.228

Is a browser extension:
No

Steps to reproduce the problem:

Open and render the attached file by PDF.js on iOS

What is the expected behavior? (add screenshot)
The file should be rendered like this:

What went wrong? (add screenshot)
Nothing is drawn on iOS
This screen shot is the demo on iOS with the PDF.

Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension):
None
Added on 2020-03-05:
We got this right result in 7 minutes after opening the file.

We got a right result in 7 minutes after opening the file. I added a scrrenshot.

The attached PDF is not rendered properly only on iOS. It's OK for other platforms.

That clearly suggests a platform/browser bug (e.g. canvas-related), rather than a PDF.js one, and as such it's unfortunately very difficult to see that it's actionable/fixable here; hence I'd suggest closing this issue.


go: verifying<EMAIL_ADDRESS>checksum mismatch

Hi All,
I am trying to build a go-micro service and continually get the following error:
go: verifying<EMAIL_ADDRESS>checksum mismatch
I have seen posts which suggest to use Go modules and version 1.13. I have both and still get the error.
I have tried replacing the etcd import using replace go.etcd.io/etcd v3.3.17+incompatible => github.com/etcd-io/etcd v0.0.0-20190603181807-35a67024f680
I have tried to update the dependencies and clean the modules cache but cannot resolve this issue. Any suggestions?
Best
Chris

What is your workflow?
export GO111MODULE=on

go get github.com/micro/go-micro

Does this not work? If you apply the -u flag it will attempt to update dependencies and usually this is where things fail.

Hey Asim,
Thanks for getting back to me and sorry about the delay replying.
I fixed the problem. Basically I had an old version of go as a base image in the Dockerfile. Once I updated to 1.13.0 and turned GOModules on the build worked.
Thanks
Chris


feat: use jwt_access_token for new api (in development)

Checklist:

[x] I have read and followed the contribution guidelines.
[x] I have read and followed the how to open a pull request guide.
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

This is part of the work needed to allow the new api to a) authenticate users and b) accept requests from users that the old api authenticated.
I focused on two things in this PR

creating fastify plugins to create and verify jwt_access_tokens
updating the mock login that's used in development and testing

The follow up PR(s) will

use OpenID Connect to authenticate users (i.e. implement the old api's authentication flow in the new api)
reduce the db usage by re-using req.user in the handlers, rather than fetching the user record twice
update mobile-login to use req.user not req.session.user, since we don't have sessions.
probably refactor a fair bit (names in particular)

Finally some design choices to bear in mind

There's a small bug fix: the api handles the case where the user record is missing, but the jwt_access_token still exists (i.e. they were signed in on two devices and deleted their account)
The cookie jwt_access_token and the access token encoded within it expire at different times. We should fix this post-MVP
When redirecting the user I dropped query params i.e. if the referrer is www.fcc.org/thing/?what=is, it'll send you back to www.fcc.org/thing/. This seemed more sensible, since we probably don't want to keep any old flash messages after redirecting, but it is a change.

Thanks for the review, @moT01. Working with the redirection helpers made me realise just how much they need to be updated, but I'll hold of until your PRs are in. Much as I want to fix it here!
Anyways, let me know if I missed anything.


[swift-reflection-dump] Make ObjC interoperability configurable.

This addresses a FIXME in the code. This allows running swift-reflection-dump on macOS to dump the contents of an ELF binary.

I just realized I also need to thread this through makeReflectionContextForObjectFiles will update the patch soon.

Updated.

@swift-ci test and merge


print a warning when the trace file is missing rather than wait

Description

Testing Instructions

#8904  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @arlyon and the rest of your teammates on  Graphite


[Docs] Regarding HMR?

It says for hmr we need to comment these lines
mix
    .options({
        hmrOptions: {
            port: '3030',
        },

I am confused as I think we should uncomment for hmr isn't it ?
From docs
IMPORTANT NOTE: Due to laravel mix limitations, when using hmr,
you need to comment lines 3-to-7 inside webpack.mix.js in order for it to work correctly. Don't forget to uncomment them back when building without hot module replacement.

That's for an older version of laravel-mix. You don't need to comment anything. I updated the readme.

Yea same thought :)


Invoke-ServiceFabricEncryptText should use LocalMachine as -StoreLocation

The document suggests use -StoreLocation CurrentUser in Invoke-ServiceFabricEncryptText, which causes an error:
`Invoke-ServiceFabricEncryptText : Exception from HRESULT: 0x80071C57
At line:1 char:1
Invoke-ServiceFabricEncryptText -CertStore -CertThumbprint "311FCFA7C ...

CategoryInfo          : NotSpecified: (:) [Invoke-ServiceFabricEncryptText], COMException
FullyQualifiedErrorId : InvokeEncryptTextErrorId,Microsoft.ServiceFabric.Powershell.InvokeEncryptText`

Use LocalMachine will be success.

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

ID: 15436b0f-9b50-269f-7cab-36740b1f862c
Version Independent ID: 050deec3-d788-1d80-b826-f8ad644ed112
Content: Manage Azure Service Fabric application secrets
Content Source: articles/service-fabric/service-fabric-application-secret-management.md
Service: service-fabric
GitHub Login: @vturecek
Microsoft Alias: vturecek

Thanks for the feedback! We are currently investigating and will update you shortly.

@mazong1123  I have assigned the issue to the content author to investigate further and update the document as appropriate.


Question: case when we want explicite schema delegation and integration with prisma-binding

Hello,
Question, please:
On a note on prisma-binding read-me: Unless you explicitly want to use schema delegation we recommend to use Prisma client to build a GraphQL server. I see your are taking the whole thing to a new level with nexus and nexus prisma.
What about the case when we want explicite schema delegation? Can we use nexus-prisma and/or nexus wirth prisma-binding?

Got a response from a comment on nexus blog article.
"GraphQL Nexus is a GraphQL schema construction library that is independent from Prisma. There's no need to migrate to it if you're currently using a different approach (such as SDL-first based on graphql-tools). That being said, we're working on a plugin that will enable a nice integration of Nexus and the Prisma client, we'll publish a blog post about it very soon."
source: https://www.prisma.io/blog/introducing-graphql-nexus-code-first-graphql-server-development-ll6s1yy5cxl5

@AMO-MTSY I am not really sure the reply answers your question.
I have the exact same question, ie. what if I want to use the prisma binding, ie the old (legacy?!) SD) instead of the new prisma client in combination with nexus-prisma?
The "old SDK" is way more useful and optimized for usage in situations where you want to forward queries/mutations "as is" with some additional pre-processing (ex setting default arguments, or locking down values for specific arguments to the user session).
Besides that, another drawback shows up when fetching nested relationships (one of the most powerful Prisma features), which is not optimized with the new prisma client as well as it is by using the prisma bindings in combination with fragments.
Let's take this as an example data model:
type Ship { title: String, user: User! }
type User { ships: [Ship!]! }

Say you want to fetch all users and their related ships after you have whitelisted the "users" (or usersConnection) query with nexus-prisma. What will happen is that this will issue a query for the list of ships (ie client.users()) and then an additional query/request for fetching the ships for each user in that list!
I actually really do not understand what is the reasoning for using the prisma-client versus the prisma binding in the nexus-prisma package which is even officially recommended to be used for building graphql server clients that are typically proxying requests to prisma with some pre/post processing logic.


loop.run_in_executor should be a coroutine

Since base_events.BaseEventLoop.run_in_executor returns a Future object, a caller can call it with yield from/await. However, the result of the call is not a coroutine since asyncio.iscoroutine(loop.run_in_executor(...)) returns False.
It matters when one wants to use run_in_executor() in a task, such as:
loop.create_task(loop.run_in_executor(...))
In this case, an exception is raised immediatly (AssertionError), while the task is effectively running in the executor.
This patch propose to make loop.run_in_executor() be an actual coroutine function (and be tested).
I believe that returning a Future and document the function as a coroutine used to be done quite often, maybe this should be fixed elsewhere too.
An alternative solution would be to change the documentation, explain why it can not be used with loop.create_task() and should be used with loop.ensure_future() instead.

There are too many places inside asyncio where coroutine is technically a regular function returning Future instance.
I think it's perfectly fine.
If you want to make doc update -- you are welcome.

I don't think it's perfectly fine: it creates an inconsistency between coroutines and other awaitable objects which leads to confusion for the user and subtle bugs.
Most of the time, loop.create_task() and ensure_future()/async() are presented as similar, but loop.create_task() can handle coroutines and not other awaitable objects. If this difference of semantics is enforced on purpose (coroutines and tasks imply work to be done, while a future only represents a result), I think the implementation of asyncio has to be consistent with this semantic.
There are subtle differences between a function returning a future and a coroutine. For instance, a coroutine is executed only when awaited on (i.e. next(coro)), while a function returning a future is executed when invoked. In the case of loop.run_in_executor(), work starts on a thread (that's a pretty significant side effect) even if the loop never runs.

You've really got this backwards. The most general concept here is not the Task but the Future (which is a base class of Task). If you have either a coroutine or a Future and you want a unified API, you should call ensure_future(), not create_task(). If you already have a Future there's no point in trying to wrap it into a Task, nor to try to make a coroutine into it -- that's backwards.
There is no philosophical difference between Task/coroutine and Future in the way you assume.
If you really have a use case where it matters to you that the action doesn't get started until the loop runs (which seems suspicious to me) you will have to implement this in some other way.


What are the shortcuts on Mac?

⌘+K ⌘+G

Oh, thank you can we add to the docs?

Thank you for the feedback @benedikt-buchert sincerely much appreciated!
You can also just type any extension name in the Keyboard Shortcuts Editor relative was nice enough to link above; just fyi. That way you can also see if there are not default keybinds applied and you can add/edit one.


Cookie policy popoup

Not sure where to post the issue, so feel free to relocate.
Some games, published and hosted on PlayCanvas servers, but launched via iFrame on other platforms, have a cookie policy popup appearing each time a game is launched ("By clicking Accept All Cookies".... etc.). The issue is with the platforms that do not store local cookies, like iMessaging in-app games. As a result, the popup is shown every time the game is started no matter the answer given. Is there a way to disable the popup by force, e.g. some URL param?
Edit:
This was not the case until recently. Not sure what changed.

Moving to Editor. @vkalpias @marialai is there anything we can do about this?


Fix typo and delete unnecessary spaces

typo: Github -> GitHub
delete unnecessary spaces: As Markdown syntax, there was a large amount of half-width spaces that did not affect the display, so I deleted it

@changeworld : Thanks for your contribution! The author, @CelesteDG, has been notified to review your proposed change.

Verified editorial fix and layout in GitHub.


quick proposal of fake driver for testing

🔗 Linked issue
https://github.com/adonisjs/core/discussions/3833
❓ Type of change

[ ] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[x] ✨ New feature (a non-breaking change that adds functionality)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description
Created an extra driver with an in memory limiter to be able to test without redis/db's setup
So ideally in your .env.test you'll have the limiter driver on "fake" (or in the config) and it should work as any other driver.
📝 Checklist

[x] I have linked an issue or discussion.
[ ] I have updated the documentation accordingly.

one small caveat is that the response of the remaining is negative in the fake.test.spec but I think this is a bug and I already created a ticket for that in the other project.

I think, we should opt for the existing fakes API and add a Limiter.fake() method that switch to the memory driver and calling Limiter.restore() restores to the original set of drivers.

I think, we should opt for the existing fakes API and add a Limiter.fake() method that switch to the memory driver and calling Limiter.restore() restores to the original set of drivers.

I agree was trying to figure out how it was done in the other addons, will try to change it when I have some time. I'll try to just add the in memory driver here and i'll create an other pull request for the one with the fake api.

fyi @thetutlage they accepted my pr for the issue with the negative remaining, I'll update the dependency here as well. (https://github.com/animir/node-rate-limiter-flexible/issues/172)


Remove libvirt-bin from the installed pkgs in ceph-common

This package is un-needed on the ceph node and will turn on IP forwarding if it is running.

ok to test

This isn't really going to be touched by CI, so we need testing on this outside of CI.

Just manually tested it with and without my PR. It goes from IP forwarding on to IP Forwarding off appropriately.

Ceph isn't enabled in CI. Merging this.


Reloadium experienced a fatal error and has to quit.

Describe the bug*
A clear and concise description of what the bug is.
C:\Users\test\Documents\python_code\gitlab_code\venv\Scripts\python.exe" -m reloadium_launcher pydev_proxy "C:/Program Files/JetBrains/PyCharm Community Edition 2022.1/plugins/python-ce/helpers/pydev/pydevd.py" --multiprocess --client <IP_ADDRESS> --port 50448 --file "C:\Users\test\Documents\python_code\gitlab_code\test\Main.py"
Connected to pydev debugger (build 231.9011.38)
■■■■■■■■■■■■■■■
Reloadium 1.1.1
■■■■■■■■■■■■■■■
If you like this project consider becoming a sponsor or giving a star at https://github.com/reloadware/reloadium
Reloadium experienced a fatal error and has to quit.
Please submit a github issue to let us know at https://github.com/reloadware/reloadium
Process finished with exit code 1

python environment
Python 3.10.4 (tags/v3.10.4:9d38120, Mar 23 2022, 23:13:41) [MSC v.1929 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.

but i can esay to use in another test project like this

The first Main.py is startup python file for a big  project

How can I print more information to determine what the cause is?

@gengchaogit It should be RW_DEBUG=True not TRUE.

Oh,Thanks! here is the debug log.....
■■■■■■■■■■■■■■■
Reloadium 1.1.1
■■■■■■■■■■■■■■■
If you like this project consider becoming a sponsor or giving a star at https://github.com/reloadware/reloadium
Traceback (most recent call last):
File "C:\Users\test.reloadium\package\3.10\reloadium\corium\ll1llll11111llllIl1l1.py", line 169, in l1lll11ll1ll111lIl1l1
File "D:\a\reloadware\reloadware\reload\package_obfuscated_\reloadium\fast\lll1111l111l11llIl1l1.py", line 81, in exec_module
File "D:\a\reloadware\reloadware\reload\package_obfuscated_\reloadium\fast\l1ll1l1111l1ll1lIl1l1\l11ll11ll11l1l1lIl1l1.py", line 561, in ll1l11lllll111l1Il1l1
File "D:\a\reloadware\reloadware\reload\package_obfuscated_\reloadium\fast\l1ll1l1111l1ll1lIl1l1\l11ll11ll11l1l1lIl1l1.py", line 583, in lllllllllllll111Il1l1
File "C:\Users\test.reloadium\package\3.10\reloadium\corium\l11ll1l1l1lll111Il1l1.py", line 27, in l1llll111ll11l1lIl1l1
File "C:\Program Files\Python\lib\pathlib.py", line 1133, in read_text
return f.read()
File "C:\Program Files\Python\lib\codecs.py", line 322, in decode
(result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xa3 in position 5719: invalid start byte
Reloadium experienced a fatal error and has to quit.
Please submit a github issue to let us know at https://github.com/reloadware/reloadium
Process finished with exit code 1

In fact, I did not report any errors when using the debug feature that comes with pycharm

the full path like that C:\Users\test\OneDrive - Company\Documents\python_code\gitlab_code
Tt's that OneDrive - Company issue?  The path contains space.

Tested, not the space issue.

Debug to here

next will show error

the data print below
Add attributes to simplify introspection
sr.data_encoding = data_encoding
sr.file_encoding = file_encoding
return sr

Helpers for codec lookup
def getencoder(encoding):
""" Lookup up the codec for the given encoding and return
    its encoder function.

    Raises a LookupError in case the encoding cannot be found.

"""
return lookup(encoding).encode

def getdecoder(encoding):
""" Lookup up the codec for the given encoding and return
    its decoder function.

    Raises a LookupError in case the encoding cannot be found.

"""
return lookup(encoding).decode

def getincrementalencoder(encoding):
""" Lookup up the codec for the given encoding and return
    its IncrementalEncoder class or factory function.

    Raises a LookupError in case the encoding cannot be found
    or the codecs doesn't provide an incremental encoder.

"""
encoder = lookup(encoding).incrementalencoder
if encoder is None:
    raise LookupError(encoding)
return encoder

def getincrementaldecoder(encoding):
""" Lookup up the codec for the given encoding and return
    its IncrementalDecoder class or factory function.

    Raises a LookupError in case the encoding cannot be found
    or the codecs doesn't provide an incremental decoder.

"""
decoder = lookup(encoding).incrementaldecoder
if decoder is None:
    raise LookupError(encoding)
return decoder

def getreader(encoding):
""" Lookup up the codec for the given encoding and return
    its StreamReader class or factory function.

    Raises a LookupError in case the encoding cannot be found.

"""
return lookup(encoding).streamreader

def getwriter(encoding):
""" Lookup up the codec for the given encoding and return
    its StreamWriter class or factory function.

    Raises a LookupError in case the encoding cannot be found.

"""
return lookup(encoding).streamwriter

def iterencode(iterator, encoding, errors='strict', **kwargs):
"""
Encoding iterator.
Encodes the input strings from the iterator using an IncrementalEncoder.

errors and kwargs are passed through to the IncrementalEncoder
constructor.
"""
encoder = getincrementalencoder(encoding)(errors, **kwargs)
for input in iterator:
    output = encoder.encode(input)
    if output:
        yield output
output = encoder.encode("", True)
if output:
    yield output

def iterdecode(iterator, encoding, errors='strict', **kwargs):
"""
Decoding iterator.
Decodes the input strings from the iterator using an IncrementalDecoder.

errors and kwargs are passed through to the IncrementalDecoder
constructor.
"""
decoder = getincrementaldecoder(encoding)(errors, **kwargs)
for input in iterator:
    output = decoder.decode(input)
    if output:
        yield output
output = decoder.decode(b"", True)
if output:
    yield output

Helpers for charmap-based codecs
def make_identity_dict(rng):
""" make_identity_dict(rng) -> dict

    Return a dictionary where elements of the rng sequence are
    mapped to themselves.

"""
return {i:i for i in rng}

def make_encoding_map(decoding_map):
""" Creates an encoding map from a decoding map.

    If a target mapping in the decoding map occurs multiple
    times, then that target is mapped to None (undefined mapping),
    causing an exception when encountered by the charmap codec
    during translation.

    One example where this happens is cp875.py which decodes
    multiple character to \\u001a.

"""
m = {}
for k,v in decoding_map.items():
    if not v in m:
        m[v] = k
    else:
        m[v] = None
return m

error handlers
try:
strict_errors = lookup_error("strict")
ignore_errors = lookup_error("ignore")
replace_errors = lookup_error("replace")
xmlcharrefreplace_errors = lookup_error("xmlcharrefreplace")
backslashreplace_errors = lookup_error("backslashreplace")
namereplace_errors = lookup_error("namereplace")
except LookupError:
# In --disable-unicode builds, these error handler are missing
strict_errors = None
ignore_errors = None
replace_errors = None
xmlcharrefreplace_errors = None
backslashreplace_errors = None
namereplace_errors = None
Tell modulefinder that using codecs probably needs the encodings
package
_false = 0
if _false:
import encodings
Tests
if name == 'main':
# Make stdout translate Latin-1 output into UTF-8 output
sys.stdout = EncodedFile(sys.stdout, 'latin-1', 'utf-8')

# Have stdin translate Latin-1 input into UTF-8 input
sys.stdin = EncodedFile(sys.stdin, 'utf-8', 'latin-1')

It seems like your file is under different than utf-8 encoding.
Could you please check what encoding is used for the file that fails?

Fixed in Reloadium 1.2.0 and PyCharm plugin 1.2.0

oh, thanks!


Update gpsctl.conf.default

Corrected missing # in section [gpsctl].

The setting "refer beidou to glonass if both enabled = no" is the default.
Commenting it out makes no diffence whatsover.


[Bug] RayServe: Old ray clusters not being deleted cause a failure in new deployments

Search before asking

[X] I searched the issues and found no similar issues.

KubeRay Component
ray-operator
What happened + What you expected to happen
I am unsure how this happened, but it seems that the ray-operator can't delete old clusters and this causes subsequent service updates to fail.
When updating the docker image, the operator seems to trigger a new raycluster deployment by creating a redis cleanup job that fails:
$ kubectl logs -n search-backend search-backend-raycluster-gpq8m-redis-cleanup-9lcjr
[2024-03-25 11:19:46,941 I 1 1] redis_context.cc:478: Resolve Redis address to <IP_ADDRESS>
[2024-03-25 11:19:46,941 I 1 1] redis_context.cc:364: Attempting to connect to address <IP_ADDRESS>:6379.
[2024-03-25 11:19:46,941 I 1 1] redis_context.cc:364: Attempting to connect to address redis:6379.
[2024-03-25 11:19:46,943 I 1 1] redis_context.cc:532: Redis cluster leader is <IP_ADDRESS>:6379
[2024-03-25 11:19:46,944 I 1 1] redis_context.cc:478: Resolve Redis address to <IP_ADDRESS>
[2024-03-25 11:19:46,944 I 1 1] redis_context.cc:364: Attempting to connect to address <IP_ADDRESS>:6379.
[2024-03-25 11:19:46,944 I 1 1] redis_context.cc:364: Attempting to connect to address redis:6379.
[2024-03-25 11:19:46,947 I 1 1] redis_context.cc:532: Redis cluster leader is <IP_ADDRESS>:6379
[2024-03-25 11:19:46,947 E 1 1] _raylet.cpp:926: Failed to delete 446d6c17-4426-49aa-bf5b-980bc479eecc

By listing the ray clusters I see there is a new ray cluster that never manages to start:
$ kubectl get raycluster -n search-backend
NAME                              DESIRED WORKERS   AVAILABLE WORKERS   STATUS   AGE
search-backend-raycluster-gpq8m                                                  22h
search-backend-raycluster-nqsbl   1                 1                   ready    6d15h

The ray operator logs the following in a loop (truncated for readability):
$ kubectl logs -n search-backend kuberay-operator-search-fd5cd76d7-qxg2x
(...)
2024-03-26T09:24:56.333Z	INFO	controllers.RayService	Reconciling the cluster component.	{"ServiceName": "search-backend/search-backend"}
2024-03-26T09:24:56.334Z	DEBUG	controllers.RayService	createRayClusterInstance	{"rayClusterInstanceName": "search-backend-raycluster-gpq8m"}
2024-03-26T09:24:56.334Z	DEBUG	controllers.RayService	Ray cluster already exists, config changes. Need to recreate. Delete the pending one now.	{"key": "search-backend/search-backend-raycluster-gpq8m", "rayClusterInstance.Spec": {"headGroupSpec":{"rayStartParams":{"dashboard-host":"<IP_ADDRESS>","num-cpus":"0"},"template":{"metadata":{"creationTimestamp":nu (...TRUNCATED)
2024-03-26T09:24:56.364Z	INFO	controllers.RayService	Done reconcileRayCluster update status, enter next loop to create new ray cluster.	{"ServiceName": "search-backend/search-backend"}

Even if I delete the whole rayservice in kubernetes, the redis deployment and manually delete the kuberay-operator. These rayclusters are never deleted. After recreating the resources the clusters start to pile up:
$ kubectl get raycluster
NAME                              DESIRED WORKERS   AVAILABLE WORKERS   STATUS   AGE
search-backend-raycluster-gpq8m                                                  2d6h
search-backend-raycluster-n292x   1                 1                   ready    15m
search-backend-raycluster-nqsbl   1                 1                   ready    7d23h

but only the newest cluster seems to have a cluster head:
$ kubectl get pods
NAME                                                      READY   STATUS    RESTARTS   AGE
earch-backend-raycluster-n292x-worker-cpu-process-zts5d   1/1     Running   0          21m
kuberay-operator-search-fd5cd76d7-fl7pr                   1/1     Running   0          23m
redis-76c84bbfbc-qrm2x                                    1/1     Running   0          23m
search-backend-raycluster-n292x-head-hjzpp                2/2     Running   0          22m

Reproduction script
I couldn't find a reproduction script for this behavior, and I am unsure how the system ended up in this state.
Anything else
No response
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

After deleting and recreating the cluster I haven't been able to reproduce this anymore.


datamodel-codegen fix

should help fix some of the codegen issues seen when bumping the version of datamodel-codegen for pydantic v2 compatibility

Awesome, thanks - seems to fix it trying to write a models.py file instead of the dir!


Archived state for a room is not well-defined, and state delta requirement seems unimplemented and cumbersome for clients

Link to problem area:
https://matrix.org/docs/spec/client_server/latest#get-matrix-client-r0-sync
Issue
invite_state for invited room says that:

If the client joins the room then the current state will be given as a delta against the archived state not the invite_state.

A room is apparently in archived state when it has membership "leave" but /forgot hasn't been called on it yet (which only the client that calls /forget can known about fwiw). This doesn't seem to be explicitly explained anywhere in the spec.
Also, are server implementations actually serving this delta? It's somewhat annoying for clients to implement keeping state around for any left room, given that they can't know if any other device has called /forget on it.
It seems like an uncommon case to optimize, and was probably introduced before lazy loading members was a thing. If it is not relevant anymore, perhaps it can be removed?

Synapse seems to at least send most of the state, when you rejoin a room. Conduit also does that currently.

Synapse will apparently send the full room state

Imo; change the spec to send full room state with each each invite/rejoin, this de-complicates client implementations/state (instead of having to accommodate all state of all actions in the past ad infinitum)
This'd probably require an MSC, though, it is technically a spec change, even if it's the alignment of spec to synapse.

This'd probably require an MSC, though, it is technically a spec change, even if it's the alignment of spec to synapse.

In cases like this, where there is good evidence that Synapse's behaviour predates the words in the spec, we generally argue that it's simply a bug in the spec that needs fixing.


invalid_grant: The refresh token is invalid or expired.

Hi,
I'm using using server flow to get the access token and refresh token,
I saved both access token and refresh token.
When i call the refreshToken method, i get this error: invalid_grant: The refresh token is invalid or expired..
What should i do so the refresh token is not expired or get updated?
Thnkas

Are you specifying the scopes correctly:
https://developer.constantcontact.com/api_guide/scopes.html
I seem to remember something about grants, but it was a while back.  Also I just changed something recently in the auth code.  Roll back to the previous version (24.2 I think) and see if that works.
Let me know what you find.

I didn't specify the scopes.
based on your docs, if we didn't specify the scopes, then it will use all scopes wight?

Do you try rolling back to the previous version?
I think it defaults to all scopes, but I seem to remember something about
grants. Maybe that is OAuth stuff. That seems right to me now. Was a long
time ago I got this working so I tend to forget the how it works part.
Grants is definitely OAuth, which my library should handle. Will look again
tomorrow.
On Tue, Mar 5, 2024, 10:34 PM yonghan79 @.***> wrote:

I didn't specify the scopes.
based on your docs, if we didn't specify the scopes, then it will use all
scopes wight?
—
Reply to this email directly, view it on GitHub
https://github.com/phpfui/ConstantContact/issues/19#issuecomment-1980018608,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABYW6S4IRA6U4OEZCQILZELYW2FFLAVCNFSM6AAAAABEHTAJZCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBQGAYTQNRQHA
.
You are receiving this because you commented.Message ID:
@.***>

Not yet, I haven't rolled back the version yet.
I will wait for your info regarding the grant. Thanks you.

Yes, confirmed grant types are part of OAuth.  Also it looks like the code is no longer working for my website.  I need to investigate why, but could be a setting issue on my side.
So please do try a rollback to the previous version and let me know if that works for you.  I suspect that is the issue.  There will be an update to the library for sure in the next week, but it would help to have your experience on the previous version.

I was able to retest the older version of the library and the newer version. They both seem to work, but I would do your own testing.
See issue #17 for other ideas on getting and refreshing the tokens.  I think the problem may actually be what the error message says, is that the refresh token is invalid.  Have you tried to access an API endpoint other than refresh? If that works, your main token is OK and the refresh token should be good.
I am going to add another Constant Contact feature to my website and will update the library if I find any other issues.

I have add a debug code to get the refresh token last error message to see when the token becomes empty, and it appears after around 3 days, the refresh token expired or becomes invalid.
i was using the rotating instead of long live token.
Could that be the cause?

i will try the long live refresh token to see if it still return empty token after several days.
i will let you know the result.

I did a lot of testing on my own site and things seem to be working correctly.  I did fix one minor issue with next() if the API returned an error that would cause multiple extra requests.

I am closing this issue as I think it was a configuration issue.  Open another issue if needed.


Backport 2.7: Fix the default port number in usage

Description
Backport of #2368 to mbedtls-2.7
Status
READY

PR is approved, and passing all CI tests apart from the 'merge' job due to a conflict in the ChangeLog, therefore approving the PR for merge.


Set max curve radius in BIG_BLOCK_SEQUENCE

Hello,
I noticed that the curves generated by BIG_BLOCK_SEQUENCE are very tight. Would it be possible to set the maximum curve radius?

We didn't expose that API. The Curve block has a class parameter PARAMETER_SPACE specifying which space the parameters should be sampled. You can check its configuration at metadrive/component/pg_space/BlockParameterSpace.

Is there any better way to generate a map then? Neither the MapGenerateMethod.PG_MAP_FILE type nor the map json file aren't really documented.

Ideally, there should be something like a map editor. But we don't have it yet even if our backend supporters various map generation. The most user-friendly APIs are the ScenarioMap and ScenarioBlock which allow constructing a map from a list of map features including lane center lines/solid lines/dashed lines/crosswalks/sidewalks and so on. It has been used to construct the Waymo Map, nuScenes map, SUMO map, and OpenDrive map before. So it has a good compatibility. Or you can refer to the multi-agent environments where the maps are generated by combining several blocks manually.


Add ETDRK4 fourth-order time-stepping for stiff PDEs

The Kassam and Trefethen classic uses a contour integral to stabilize coefficients in the scheme (Eq (2.5)), but I just added more efficient Taylor expansions near the numerical instability.
The Taylor expansions require about 18 coefficients in double precision, but the contour integral requires at least 32 calls to exp (and uses complex numbers), so this is unequivocally better.
Implementing the scheme should now be straightforward.

I should add the caveat that the Taylor expansions would only be useful for diagonal operators in the linear part of the splitting u_t = Lu + N(u), while the contour method allows more general operators.

Similar to what I said in the other thread: why not use rational expansion of the exponential?  The issue with contour integrals is that you need to know where the spectrum of the operator is
Sent from my iPhone

On 18 Dec 2015, at 11:56, Richard Mikael Slevinsky<EMAIL_ADDRESS>wrote:
I should add the caveat that the Taylor expansions would only be useful for diagonal operators in the linear part of the splitting u_t = Lu + N(u), while the contour method allows more general operators.
—
Reply to this email directly or view it on GitHub.

Sorry, perhaps the more pertinent issue to ApproxFun is that rangespace(L) == domainspace(L) so that it's sensible to define operator functions by their formal power series.

For Taylor series then yes
But Taylor series for exponential seems like a bad idea: exp(-x) has lots of cancellation for large x, and operators have infinite spectrum.  Only way to do Taylor series then is to restrict the stepsize based on length of solution.  This works..but is very much counter to approxfun mentality of doing things in inf dimensions
Sent from my iPhone

On 18 Dec 2015, at 23:08, Richard Mikael Slevinsky<EMAIL_ADDRESS>wrote:
Sorry, perhaps the more pertinent issue to ApproxFun is that rangespace(L) == domainspace(L) so that it's sensible to define operator functions by their formal power series.
—
Reply to this email directly or view it on GitHub.

Plus applying an operator and inverting an operator are both O(n) operations, so it's not obvious Taylor series is faster (all about constant in front)
Sent from my iPhone

On 18 Dec 2015, at 23:08, Richard Mikael Slevinsky<EMAIL_ADDRESS>wrote:
Sorry, perhaps the more pertinent issue to ApproxFun is that rangespace(L) == domainspace(L) so that it's sensible to define operator functions by their formal power series.
—
Reply to this email directly or view it on GitHub.

Padé approximants are also defined for f satisfying a formal power series.

Many of the important nonlinear PDEs have L diagonal anyways.

Only for periodic bcs, which are pretty boring.

On 18 Dec 2015, at 11:25 PM, Richard Mikael Slevinsky<EMAIL_ADDRESS>wrote:
Many of the important nonlinear PDEs have L diagonal anyways.
—
Reply to this email directly or view it on GitHub https://github.com/ApproxFun/ApproxFun.jl/issues/286#issuecomment-165766932.

Looks like a scaling-and-squaring argument could be considered. Neat to know that all the Padé approximants are known for the phi functions (section 4.5 of this thesis).
My original interest was in boring periodic boundary conditions, in which case the best and fastest way to stabilize the scheme (in my opinion and specifically in Julia where writing your own special functions is practical) is with sufficiently accurate Taylor series near the origin and the actual expression sufficiently far away. This is correct because element-wise == matrix-valued functions for diagonal matrices and operators.
Symplectic integrators may be more natural for integrable systems, but this would require solving nonlinear equations for Funs, ugh.

Another approach would be generalized eigendecomposition for operators.

For self adjoint yes (the work with Marcus allows this).  For general differential operators with boundary conditions I'm not so sure...I suppose you could calculate the Schur decomposition which would reduce the problem to upper triangular operators.
Sent from my iPhone

On 21 Dec 2015, at 07:24, Richard Mikael Slevinsky<EMAIL_ADDRESS>wrote:
Another approach would be generalized eigendecomposition for operators.
—
Reply to this email directly or view it on GitHub.

Probably operator exponentials are only practical for diagonal L. Otherwise, linear complexity in space is lost (and a simpler discretization or scheme should've been chosen).

I don't understand:  rational approximation and contour integration methods both still have linear complexity.
Sent from my iPhone

On 22 Dec 2015, at 22:46, Richard Mikael Slevinsky<EMAIL_ADDRESS>wrote:
Probably operator exponentials are only practical for diagonal L. Otherwise, linear complexity in space is lost (and a simpler discretization or scheme should've been chosen).
—
Reply to this email directly or view it on GitHub.

you're right. EDIT: undo.

There is an ETDRK4 method and two examples with periodic boundary conditions: Burgers' equation and Kuramoto-Sivashinsky equation.


remove max concurrent streams default

We added max concurrent streams default when Envoy's default value was 100. Now it has been increased https://www.envoyproxy.io/docs/envoy/latest/api-v3/config/core/v3/protocol.proto#envoy-v3-api-msg-config-core-v3-http2protocoloptions - so it is better to default it to Envoy rather than our own number.
This PR fixes it.

[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[X] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

did it change just recently or also in older versions?


[ERROR]: lack of the trailing comma after the last argument of function call in golang code snippets

Is there an existing issue for this?

[X] I have searched the existing issues.

Issue
Some golang code snippets in the doc have syntax error, for example:
The chapter "Create a partition", the code snippet for golang is
err := milvusClient.CreatePartition(
  context.Background(),
  "book",
  "novel" // <- lack of the trailing comma
)
if err != nil {
  log.Fatal("failed to create partition:", err.Error())
}

to be correct, it should be like
err := milvusClient.CreatePartition(
  context.Background(),
  "book",
  "novel", // trailing comma added
)
if err != nil {
  log.Fatal("failed to create partition:", err.Error())
}

Suggestion
No response
Anything else?
No response

pull request #2305 fixed this issue


Styling appears differently when running locally vs deployed to netlify

See the images below. The first is from localhost where everything looks as expected. The second is deployed to Netlify using the one-click option.

I have the same issue that I'd like to figure out how to solve.
The smaller fonts/tighter UI is not so much of a problem but the horizontal scrollbar that appears in the navbar is quite inconvenient.
And unfortunately the "uglier" version is the deployed one instead of the locally served site.

@JacobWrenn @Gioele-Bencivenga I applied this PR to my fork and it solved my styling issues: https://github.com/netlify-templates/one-click-hugo-cms/pull/742

@kwuite thanks, found it a short while ago and worked a charm!

Solved in #742


Nullpointer when starting Exhibitor

WARNING: Prefs file removed in background /root/.java/.userPrefs/prefs.xml
INFO  com.netflix.exhibitor.core.activity.ActivityLog  Attempting to stop instance [ActivityQueue-0]
INFO  com.netflix.exhibitor.core.activity.ActivityLog  Attempting to start/restart ZooKeeper [ActivityQueue-0]
INFO  com.netflix.exhibitor.core.activity.ActivityLog  jps didn't find instance - assuming ZK is not running [ActivityQueue-0]
INFO  com.netflix.exhibitor.core.activity.ActivityLog  Starting in standalone mode [ActivityQueue-0]
ERROR com.netflix.exhibitor.core.activity.ActivityLog  Monitoring instance [ActivityQueue-0]
java.lang.NullPointerException
	at com.netflix.exhibitor.core.processes.StandardProcessOperations.prepConfigFile(StandardProcessOperations.java:161)
	at com.netflix.exhibitor.core.processes.StandardProcessOperations.startInstance(StandardProcessOperations.java:109)
	at com.netflix.exhibitor.core.state.KillRunningInstance.completed(KillRunningInstance.java:41)
	at com.netflix.exhibitor.core.activity.ActivityQueue$1.run(ActivityQueue.java:127)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)

This only applies to 1.5.3 because of change https://github.com/Netflix/exhibitor/commit/571986231453dbd663a0217d3400821bee59f162

Fixed for next release

I'm still seeing this NPE in version 1.5.4, even with a null check. Has this really been fixed? Thanks.

Sorry - I'll try to get 1.5.5 out by the end of the week.


version 0.23.1 not available

Describe the bug
Despite its release almost a month ago, I am unable to pip install the 0.23.1 version.
To Reproduce
PyPI

This was an oversight, sorry. I'll get it up by the end of the week.

It seems like v0.23.1 and v0.23.2 are still not available?
ERROR: Could not find a version that satisfies the requirement tableauserverclient==v0.23.2 (from versions: 0.1, 0.2, 0.3, 0.4, 0.4.1, 0.5, 0.5.1, 0.6, 0.6.1, 0.6.3, 0.7, 0.8, 0.8.1, 0.9, 0.9.31.post0.dev1, 0.10, 0.11, 0.12, 0.13, 0.14.0, 0.14.1, 0.15.0, 0.16.0, 0.17.0, 0.18.0, 0.19.0, 0.21.post0.dev4, 0.22, 0.23)
ERROR: No matching distribution found for tableauserverclient==v0.23.2

@jacalata do you have an update on when 0.23.1 will be pushed to PyPi, as it currently only has 0.23 (which is also missing the final .X)?

@thesuperzapper @DrMaphuse @TrimPeachu thanks for your patience - we had some issues with the publishing flow, but it's fixed now. You should be able to install v0.23.4 from PyPI: https://pypi.org/project/tableauserverclient/


EnderIO Zoo - No Such Method Error

Issue Description:
When someone join on server that reproduce the error, and server closes automatically.

Affected Versions:

EnderIO: 5.0.46
EnderCore: 0.5.59
Minecraft: 1.12.2
Forge: <IP_ADDRESS>38
SpongeForge? yes
Optifine? yes
Server

Your most recent log file where the issue was present:
https://pastebin.com/k6wKa7ss

Full crash report please

Here go.
crash-2019-08-01_10.27.23-server.txt

That's a kettle issue, you need to talk to them as I have no idea what's happening there.

Alright, i will talk with him. Thanks.


[Bug] max_token is too large

Describe the bug
When I used the new gpt-3.5-turbo-1106 model with the updated default max_token value of 8192, I just sent "Hello", I encountered the following error:
{
  "error": {
    "message": "max_tokens is too large: 8192. This model supports at most 4096 completion tokens, whereas you provided 8192.",
    "type": "invalid_request_error",
    "param": "max_tokens",
    "code": null
  }
}

Which is strange because the new model should support 16k. The same thing happens with gpt-4-1106-preview. However, when I use the older version gpt-3.5-turbo-16k, it works flawlessly without any errors. But when I use gpt-4, I just sent "Hello", I get this error:
{
  "error": {
    "message": "This model's maximum context length is 8192 tokens. However, you requested 8256 tokens (64 in the messages, 8192 in the completion). Please reduce the length of the messages or completion.",
    "type": "invalid_request_error",
    "param": "messages",
    "code": "context_length_exceeded"
  }
}

Deployment

[ ] Docker
[x] Vercel
[ ] Server

+1

+1

same problem ， any one can help

fixed

Please check the discussion https://github.com/Yidadaa/ChatGPT-Next-Web/discussions/3208.


Remove all specific staff to the separate files (better plugins)

The best method to fix this issue is to use plugin architecture.
What I mean "specific"? As I reviewed the code I can divide it into 2 groups:

MediaSDK project staff (for example build options)
Architecture`s personal staff (who said that number of stages should be hard-coded?!)

@azhogov
I think the logic of stage should be closer to pynt`s task?
http://rags.github.io/pynt/
In opposite it should be as stage in gitlab?
I try to find use-case of current stage logic in non-buildbot systems...


HNSW post parameter

First off, thank you for your amazing effort in developing the nmslib.
I've previously used Annoy for some ANN searching, but I'm trying out the HNSW graph now because of its improved performance.
Unfortunately, although your documentation is very clear and comprehensive, it doesn't seem to mention the post parameter for the HNSW graph.
Judging from the erikbern/ann-benchmarks code, setting post to either 0 or 2 has a big influence on the ef parameter. How should I interpret the post parameter to tune it for optimal performance at a high recall?

Hello @bittremieux, thank you for the kind words!
The post=2 adds an additional post-processing step to symmetrize the index. It is not documented yet in nmslib and do not presented in the paper on HNSW. In short, two indexes is build with different order of the data(direct and reverse), with following union of the produced connections. It does not affect directly the query time parameters, such as ef.
On overall, it leads to a roughly twice as long construction time, while in the end adding extra search performance at high recalls (up to several tens of percent in tests on 1M sift at ~0.999 recall, the gain smaller for less recall). So if you want to get maximum performance at search you should use post=2.

Ok great, thank you for the explanation.

We will sure update the docs in some of the upcoming releases.
Thanks!


Automatically set disableHttps when --route is set to http

Came out of: https://github.com/obsidiansystems/obelisk/issues/305

Perhaps we shouldn't have a --disableHttps flag at all. We can tell from the route that you want https can't we?

If the route is mandatory, then yes, but some people may want to just set the host and omit the route.
From memory, the route is a mandatory argument, so you are right.

Yes the route is mandatory.

I'm hesitant about this feature because of a case where someone accidentally specifies http when they meant https.


fix: type hints on BaseConfig

Change Summary
Just added SchemaExtraCallable when TYPE_CHECKING is False to make sure typing.get_type_hints does not crash.
Related issue number
closes #1614
Checklist

[ ] Unit tests for the changes exist
[ ] Tests pass on CI and coverage remains at 100%
[ ] Documentation reflects the changes where applicable
[ ] changes/<pull request or issue id>-<github username>.md file added describing change
(see changes/README.md for details)

great, thank you.

Thank you @PrettyWood!


Link to other schemas from attributes list?

When a schema A references another schema B for one of its properties, schema B will be exploded and each of its attributes will be listed in the attributes table of A. Should we additionally link to the schema, so that the user can explore its description and links?
Issue #216 relates to this.

Sounds good. If we link, I guess you could even argue the exploding is not needed, but the duplication is kind of handy. In any event, the link seems like it would be a welcome addition. Thanks!

I think it's worthwhile to keep the exploded overview. Having to jump around the docs means more context switching, and a lot of the times, just knowing the fields is enough.
I'll work on a PR to add the links.

Cool, sounds good, thanks!