reopen the page with Link block, it will focus on Link block automatically

Describe the bug
reopen the page with Link block, it will focus on Link block automatically
To Reproduce
https://www.loom.com/share/b77ccefe2a5d4fcdb106f7d03c4af5cc
Expected behavior
No response
Additional context
No response
Logs/tracebacks
No response

Actually it is an auto focus problem.


refactor: multiple code improvements

Ensure super().init() calls in class constructors
Fix incorrect types
Delete unused code
Fix typos

okay, I'll update it tomorrow

@tobitege i've submitted the adjustments, please let me know if there are any issues.


Time sort with offset/fetch without retraction

Thanks for contributing to Apache Flink. Before you open your pull request, please take the following check list into consideration.
If your changes take all of the items into account, feel free to open your pull request. For more information and/or questions please refer to the How To Contribute guide.
In addition to going through the list, please provide a meaningful description of your changes.

[x ] General

The pull request references the related JIRA issue ("[FLINK-XXX] Jira title text")
The pull request addresses only one issue
Each commit in the PR has a meaningful commit message (including the JIRA id)

[x ] Documentation

Documentation has been added for new functionality
Old documentation affected by the pull request has been updated
JavaDoc for public methods has been added

[x ] Tests & Build

Functionality added by the pull request is covered by tests
mvn clean verify has been executed successfully locally or a Travis build has passed

@fhueske ,@wuchong
As mentioned in PR #4263 I re-implemented the offset/fetch support for *time without retraction. You can find things in this PR. In principle things should be easy to follow as it is similar with what we already have.
Please let me know what you think

Hi @rtudoran, thanks for updating the PR.
I had a brief look at it and as I said before, I don't think we need additional ProcessFunctions for any of the ORDER BY *time ASC OFFSET x FETCH y cases. All cases (proctime and rowtime) can be implemented by extending the current functions for ORDER BY.
All we have to do is to

add a counter for OFFSET and not emit the first x rows (counter should be stored as state)
add a counter for FETCH and not emit more than y rows (counter should be stored as state).

If OFFSET or FETCH are not required, we can set x and/or y to -1 and ignore the counters.
Once we have extended the current ProcessFunctions, we can also remove the additional methods in DataStreamSort and SortUtil because we always translate to the same ProcessFunction just with different values for offset and fetch. So we only have to extend the current methods in DataStreamSort and SortUtil to set the correct values for offset and fetch (either the values from the query or -1 if not used) to the updated ProcessFunctions.
That should simplify the PR and require much less changes and code.
Let me know what you think,
Fabian

@fhueske
I did not understood initially that this is your suggestion. What you propose has the advantage that it is easy to maintain (as we consolidate the whole functionality) and a slight disadvantage that you have a couple of useless checks in some scenarios (e.g., you would still check the fetch condition even if you would have only offset or just the plain sorting). If this tiny performance price to pay is ok ...than clearly we can consolidate the implementation.
Nevertheless, even if this is the case i would still propose we keep the ProcTimeIdentitySortProcessFunction
This is for the scenario where you have the order by simply on the time (and no other field). In the case of simple sort we only had an identity map function to pass the events. For the case of offset/fetch we can either extend that or keep one different implementation that adds the state counters for offset/fetch. I propose we keep this later implementation.

@fhueske
Also - i do not understand why you would need to keep the counters for offset/fetch as states?
Assuming we have in the buffer state with events for proctime T values (1, 2, 3, 4, 5)
You want to emit them with offset 2 and fetch 2 (hence values 3 and 4)
So you will have the onTimer function when proctime moved and you can trigger computation for time T (i.e. at T+1)
The basic logic after you sort is that you go through the 5 elements and count the offset and then the fetch
for(int i=0; i< inputs.size; i++) {
offsetCounter++;
if(offsetCounter > offset && fetchCounter<fetch) {
out.collect(inputs(i))
fetchCounter++;
}
}
...you would then update the states at the end
What is the point here to memorize the fetchCounter and offsetCounter?
If a failure happen meanwhile you would anyway restore the whole list of the 5 elements and restart the logic (i.e., from the beginning of the function).
It is not like you do a state update at every iteration to pick in case of a failure from let's say line 5 when the value of counter was at a certain value

@fhueske ,@wuchong
I updated the PR. Please have a look

@fhueske
Hi, I saw your remark for "If a query specifies ORDER BY ... FETCH x ROWS ONLY, then the query must emit exactly x rows (given that the result has at least x rows) and not x rows for the same sort key"
To some extend we had this discussion before when we started this topic. Yes - offset/fetch refer to global/absolute values - there must be 5 elements emitted overall if we have offset 1 and fetch 5. However, as you are saying it is not particularly useful if we enable this for the stream. Take 5 elements and then do not emit anything. This was the reason why the conclusion of the initial discussions on this topic was to have the mandatory orderby time...and then basically the restrictions of offset/fetch will re-apply for each timestamp. That was also the reason why we were retracting the previously emitted results and send the updated results.
Hence if you want to write a sql query over the stream to take the top 5 results based on some sort you would write
Select * from stream1  Order by rowtime, field1 Limit 5
...this would  ensure that at moment 1 you get the top 5 results
...then at moment 2 you get an update that these 5 results are not relevant anymore (as time changed) and you get the top 5 results relevant at that moment.
Please reconsider this. I think this is the behavior that we need (and the one we discussed that is compatible with SQL semantics ... and also relevant). Without this and just having a function that selects at some point x results and then does nothing (or skips y results and then nothing for the rest of the existence)...i do not see the relevance. While, with this syntax or some similar syntax...we would still need to support such functionality also via SQL.

Hi @rtudoran,
I had the impression that your main motivation was to fill the syntactic gaps of SQL on streams and not so much to support certain kinds of use cases.
The semantics of a SQL query are given by the SQL specification and not up for discussion. If you want to support a certain behavior, we need to see how this can be expressed in standard-compliant SQL and then think about the implementation. The semantics of ORDER BY rowtime ASC FETCH 10 ROWS ONLY are given and will return the ten first (first because they have the lowest timestamp) result rows.
However, I think what you are trying to achieve is represented by ORDER BY rowtime DESC FETCH 10 ROWS ONLY. This query returns the ten last (last because they have the highest timestamp) rows of the result. Obviously, we need retraction to handle this case, because the ten last rows will change over time. ORDER BY rowtime DESC OFFSET 10 is also not very useful, because it holds back the 10 last result rows. However, we could support it to fill the gap in the syntax and execute the query instead of saying "Sorry, can't do that".
So the question now is, how do we proceed with this PR? Do we want to add the ORDER BY rowtime ASC OFFSET / FETCH functionality as simple additions to the existing operators (as I said I think it can be done with very few lines if we do some refactoring) to fill the syntactic gap or not?
Regardless of whether we add this or not, we should work on the ORDER BY rowtime DESC OFFEST / FETCH case.
What do you think?

@fhueske
Thanks for the remarks/clarification.
I am fine with taking an approach to tackle both scenarios (also the simple addons you suggest but also having the actual useful code).
Hence i would propose that the code developed with retraction support for ORDER BY rowtime ASC FETCH/OFFSET  we use it for  "ORDER BY rowtime DESC offset/FETCH.  Do you agree with this?
I can add then in another PR/update also the code you intend to use for the ASC case with the simple modifications.
Putting this aside there is another issue with LIMIT x. The intended behavior of LIMIT is to limit the number of results considered at a point. The way it is translated by Calcite is similar with FETCH. Basically at the moment of conversion you do not see any difference between
ORDER BY rowtime ASC FETCH 10 ROWS ONLY and ORDER BY rowtime LIMIT 10.
How should we handle this situation?

OK @rtudoran, that sounds good to me.
 If it has the right semantics for ORDER BY *time DESC FETCH x, please open a new PR and I'll be happy to review it.
Regarding ORDER BY *time ASC OFFSET / FETCH, I'd modify this PR according to the comments.
I didn't understand the issue with LIMIT yet. Why is LIMIT 10 not equivalent to FETCH FIRST 10 ROWS ONLY? Both should return 10 rows, right? Aside from this question, I think if Calcite parses and translates LIMIT as FETCH the right way to change the behavior would be to fix it in Calcite.

@fhueske
I have updated the PR.
Based on the previous discussions i have:

integrated the support for offset and fetch when time is ascending as you suggested (having a counter within the process function that will restrict the output)
add back the implementation for offset and fetch with retraction and bind this for queries that would have time descending. It is important to remark that the way i intended to enable this behavior is that at every new time unit the offset/fetch restriction will be reapplied from scratch. That means that in an example such as (getting the first 2 elements):
t1: event 1, event 2, event 3 => output is event 1 and event 2
t2: event 4 => output is retract (events 1&2) emit event 4


Throw an error if shaders fail to compile or program fails to link

Currently, if GL shader compilation or program linking fails, nothing happens (and the user would have to figure out that they need to add a call to layer.getShaderCompileErrors() and log the output).  Instead, we should fail early and in an obvious way when either shader compilation fails or program linking fails.

Hey, sorry to be late on this! This was something I also considered, but what happened was that Firefox would sometimes report compilation "errors" even on a working shader. See: https://github.com/openlayers/openlayers/pull/10261
I've checked again, and it seems to work fine in Firefox now: https://deploy-preview-11886--ol-site.netlify.app/examples/heatmap-earthquakes.html
So, all good! Thanks @tschaub!

Hey, sorry to be late on this! This was something I also considered, but what happened was that Firefox would sometimes report compilation "errors" even on a working shader. See: https://github.com/openlayers/openlayers/pull/10261
I've checked again, and it seems to work fine in Firefox now: https://deploy-preview-11886--ol-site.netlify.app/examples/heatmap-earthquakes.html
So, all good! Thanks @tschaub!


Update de.json with fixed strings

Fixed several grammatical errors and a few more "Google" translated strings.

Thank you for the update!


Introducing HIP 42 vote

I worked with @anthonyra to set up this HIP vote.
DeWi has retained wallets for the sake of voting.
Note to @danielcolinjames - we slightly modified the {description} rendering via this PR to support carriage returns via the json. Open to your input on the choice to do this.


[Feature/Idea]: Support Environment

What would you like to see changed/added?
Can't use variables given by the env entry.
Following does not show the given TEST_ENV variable:
- uses: vedantmgoyal9/setup-wsl2@main
- name: run wsl demo
    env:
      TEST_ENV: Foobar
    run: |
      env
    shell: wsl-run {0}

hello, it is a bit tricky to get environment variables defined for the current step from github workflow. i have asked people who are familiar with github actions to get some help! just posting this so you know that work on this is in progress 👍🏻

That has nothing to do with GHA, it is just normal WSL behavior: https://github.com/Vampire/setup-wsl/discussions/9

Thanks to Vampire, I did as described and it works.
@vedantmgoyal9 It would be great if you mention how to use environments in your readme or set a link to https://devblogs.microsoft.com/commandline/share-environment-vars-between-wsl-and-windows/.
Thx for this GHA.

@Michel73 can you please check the new readme? i've added an example in the readme :)

@Michel73 can you please check the new readme? i've updated the example :)

Yes, it's perfect. Thx.


ConnectionError: Couldn't reach https://www.dropbox.com/s/zts98j4vkqtsns6/aclImdb_v2.tar?dl=1

Describe the bug
I want to use this (https://huggingface.co/datasets/josianem/imdb) dataset therefore I am trying to load it using the following code:
dataset = load_dataset("josianem/imdb")

The dataset is not getting loaded and gives the error message as the following:
Traceback (most recent call last):
  File "sample.py", line 3, in <module>
    dataset = load_dataset("josianem/imdb")
  File "/home/saurav/.local/lib/python3.8/site-packages/datasets/load.py", line 1112, in load_dataset
    builder_instance.download_and_prepare(
  File "/home/saurav/.local/lib/python3.8/site-packages/datasets/builder.py", line 636, in download_and_prepare
    self._download_and_prepare(
  File "/home/saurav/.local/lib/python3.8/site-packages/datasets/builder.py", line 704, in _download_and_prepare
    split_generators = self._split_generators(dl_manager, **split_generators_kwargs)
  File "/home/saurav/.cache/huggingface/modules/datasets_modules/datasets/imdb/cc6ab4acab2799be15d5d217c24548b856156dafdc850165fdc4f2031f27ff2f/imdb.py", line 79, in _split_generators
    archive = dl_manager.download(_DOWNLOAD_URL)
  File "/home/saurav/.local/lib/python3.8/site-packages/datasets/utils/download_manager.py", line 196, in download
    downloaded_path_or_paths = map_nested(
  File "/home/saurav/.local/lib/python3.8/site-packages/datasets/utils/py_utils.py", line 197, in map_nested
    return function(data_struct)
  File "/home/saurav/.local/lib/python3.8/site-packages/datasets/utils/download_manager.py", line 217, in _download
    return cached_path(url_or_filename, download_config=download_config)
  File "/home/saurav/.local/lib/python3.8/site-packages/datasets/utils/file_utils.py", line 289, in cached_path
    output_path = get_from_cache(
  File "/home/saurav/.local/lib/python3.8/site-packages/datasets/utils/file_utils.py", line 606, in get_from_cache
    raise ConnectionError("Couldn't reach {}".format(url))
ConnectionError: Couldn't reach https://www.dropbox.com/s/zts98j4vkqtsns6/aclImdb_v2.tar?dl=1

Steps to reproduce the bug
You can reproduce the error by using the following code:
from datasets import load_dataset, load_metric

dataset = load_dataset("josianem/imdb")

Expected behavior
The dataset should get loaded (I am using this dataset for the first time so not much aware of the exact behavior).
Environment info

datasets version: 1.12.1
Platform: Linux-5.4.0-58-generic-x86_64-with-glibc2.29
Python version: 3.8.10
PyArrow version: 11.0.0

Thanks for reporting, @sauravtii.
Unfortunately, I'm not able to reproduce the issue:
In [1]: from datasets import load_dataset

In [2]: ds = load_dataset("josianem/imdb")

In [2]: ds
Out[2]:
DatasetDict({
    train: Dataset({
        features: ['text', 'label'],
        num_rows: 25799
    })
    test: Dataset({
        features: ['text', 'label'],
        num_rows: 25000
    })
    unsupervised: Dataset({
        features: ['text', 'label'],
        num_rows: 50000
    })
})

Could you please retry to load the dataset? Maybe there was a temporary connection issue to Dropbox.

I am facing another issue now
Traceback (most recent call last):
  File "sample.py", line 4, in <module>
    dataset = load_dataset("josianem/imdb")
  File "/home/saurav/.local/lib/python3.8/site-packages/datasets/load.py", line 1112, in load_dataset
    builder_instance.download_and_prepare(
  File "/home/saurav/.local/lib/python3.8/site-packages/datasets/builder.py", line 636, in download_and_prepare
    self._download_and_prepare(
  File "/home/saurav/.local/lib/python3.8/site-packages/datasets/builder.py", line 738, in _download_and_prepare
    verify_splits(self.info.splits, split_dict)
  File "/home/saurav/.local/lib/python3.8/site-packages/datasets/utils/info_utils.py", line 74, in verify_splits
    raise NonMatchingSplitsSizesError(str(bad_splits))
datasets.utils.info_utils.NonMatchingSplitsSizesError: [{'expected': SplitInfo(name='train', num_bytes=34501348, num_examples=25799, dataset_name='imdb'), 'recorded': SplitInfo(name='train', num_bytes=0, num_examples=0, dataset_name='imdb')}, {'expected': SplitInfo(name='test', num_bytes=32650697, num_examples=25000, dataset_name='imdb'), 'recorded': SplitInfo(name='test', num_bytes=0, num_examples=0, dataset_name='imdb')}, {'expected': SplitInfo(name='unsupervised', num_bytes=67106814, num_examples=50000, dataset_name='imdb'), 'recorded': SplitInfo(name='unsupervised', num_bytes=0, num_examples=0, dataset_name='imdb')}]

This is my code
from datasets import load_dataset, load_metric

dataset = load_dataset("josianem/imdb")

Your connection didn't work and you got an empty dataset (num_bytes=0, num_examples=0):
datasets.utils.info_utils.NonMatchingSplitsSizesError:
[
    {
        'expected': SplitInfo(name='train', num_bytes=34501348, num_examples=25799, dataset_name='imdb'),
        'recorded': SplitInfo(name='train', num_bytes=0, num_examples=0, dataset_name='imdb')
    },
    {
        'expected': SplitInfo(name='test', num_bytes=32650697, num_examples=25000, dataset_name='imdb'),
        'recorded': SplitInfo(name='test', num_bytes=0, num_examples=0, dataset_name='imdb')
    },
    {
        'expected': SplitInfo(name='unsupervised', num_bytes=67106814, num_examples=50000, dataset_name='imdb'),
        'recorded': SplitInfo(name='unsupervised', num_bytes=0, num_examples=0, dataset_name='imdb')
    }
]

Could you please try the link in your browser and see if it works? https://www.dropbox.com/s/zts98j4vkqtsns6/aclImdb_v2.tar?dl=1

If it does not work, you should contact the author of the dataset in their Community tab (https://huggingface.co/datasets/josianem/imdb/discussions) and inform them, so that they can host their data elsewhere, for example on the Hugging Face Hub itself

If the link works, you should try to load the dataset but forcing the re-download of the data files (so that the cache is refreshed with the actual data file), by passing download_mode="force_redownload":
dataset = load_dataset("josianem/imdb", download_mode="force_redownload")

After pasting the link in the browser, it did start the download so it seems that the link is working. But even after including the download_mode in my code I am facing the same issue:
Error:
Traceback (most recent call last):
  File "sample.py", line 4, in <module>
    dataset = load_dataset("josianem/imdb", download_mode="force_redownload")
  File "/home/saurav/.local/lib/python3.8/site-packages/datasets/load.py", line 1112, in load_dataset
    builder_instance.download_and_prepare(
  File "/home/saurav/.local/lib/python3.8/site-packages/datasets/builder.py", line 636, in download_and_prepare
    self._download_and_prepare(
  File "/home/saurav/.local/lib/python3.8/site-packages/datasets/builder.py", line 704, in _download_and_prepare
    split_generators = self._split_generators(dl_manager, **split_generators_kwargs)
  File "/home/saurav/.cache/huggingface/modules/datasets_modules/datasets/imdb/cc6ab4acab2799be15d5d217c24548b856156dafdc850165fdc4f2031f27ff2f/imdb.py", line 79, in _split_generators
    archive = dl_manager.download(_DOWNLOAD_URL)
  File "/home/saurav/.local/lib/python3.8/site-packages/datasets/utils/download_manager.py", line 196, in download
    downloaded_path_or_paths = map_nested(
  File "/home/saurav/.local/lib/python3.8/site-packages/datasets/utils/py_utils.py", line 197, in map_nested
    return function(data_struct)
  File "/home/saurav/.local/lib/python3.8/site-packages/datasets/utils/download_manager.py", line 217, in _download
    return cached_path(url_or_filename, download_config=download_config)
  File "/home/saurav/.local/lib/python3.8/site-packages/datasets/utils/file_utils.py", line 289, in cached_path
    output_path = get_from_cache(
  File "/home/saurav/.local/lib/python3.8/site-packages/datasets/utils/file_utils.py", line 606, in get_from_cache
    raise ConnectionError("Couldn't reach {}".format(url))
ConnectionError: Couldn't reach https://www.dropbox.com/s/zts98j4vkqtsns6/aclImdb_v2.tar?dl=1

My code:
from datasets import load_dataset, load_metric

dataset = load_dataset("josianem/imdb", download_mode="force_redownload")

That worked!! Thanks @albertvillanova : )
Downloading builder script: 100%|███████| 4.20k/4.20k [00:00<00:00, 6.69MB/s]
Downloading metadata: 100%|█████████████| 2.60k/2.60k [00:00<00:00, 3.41MB/s]
Downloading readme: 100%|███████████████| 7.52k/7.52k [00:00<00:00, 12.6MB/s]
Downloading and preparing dataset imdb/plain_text to /home/saurav/.cache/huggingface/datasets/josianem___imdb/plain_text/1.0.0/cc6ab4acab2799be15d5d217c24548b856156dafdc850165fdc4f2031f27ff2f...
Downloading data: 100%|███████████████████| 301M/301M [01:32<00:00, 3.25MB/s]
Dataset imdb downloaded and prepared to /home/saurav/.cache/huggingface/datasets/josianem___imdb/plain_text/1.0.0/cc6ab4acab2799be15d5d217c24548b856156dafdc850165fdc4f2031f27ff2f. Subsequent calls will reuse this data.
100%|█████████████████████████████████████████| 3/3 [00:00<00:00, 794.83it/s]

The code I used:
from datasets import load_dataset, load_metric

dataset = load_dataset("josianem/imdb", download_mode="force_redownload")

But when I remove download_mode="force_redownload" I get the same error. Any guess on that?


only set upid.Host and upid.Port if Host is unset

This commit checks if upid.Host is set in the http_transporter and sets it
to the value that it determines if unset.
The original problem was that I was trying to run a scheduler on <IP_ADDRESS> as
listening host and have OverrideHostname set, this should have led to the
master thinking that I was sending messages from HostnameOverride, instead the
http_transporter function listen(), mutated the upid.Host and the master would
always look up <IP_ADDRESS>.
The patch has been tested by running a scheduler against a Mesos cluster with
the scheduler bound to <IP_ADDRESS> and HostnameOverride in DriverConfig to an
external IP.
Thanks!

Thanks for the PR! Can you also write up a quick unit test?

@jdef Thanks! I added a simple test that covered my case, it's fairly simple though.

@jdef Thanks for the feedback! I've updated the tests to include a test where the upid host and port are empty. I think that should cover what I actually changed.
Thanks!

Minor doc error. Otherwise LGTM

Updated, thanks!


google storage public share url for object ?

Hello!
Thanks for minio, it works great. I have one question. When creating a bucket with
gceClient.MakeBucket("user-1234","public-read")
objects that are being PUT in that still has no default public URL, i have to enable it in the gce console. Any idea how to enable that by default ?
I tried adding, after looking into some google migration docs add a
r.req.Header.Set("x-goog-acl", "public-read") to the *Request when building the request in the s3 api go source file but to no avail  =(
Thanks!

gceClient.MakeBucket("user-1234","public-read")

It could be that the canned ACL's do not work properly for Google Cloud. Let me verify.

Thank you harshavardhana, the gc docs seems to indicate that there is a distinct difference between acl for the bucket and the individual objects which do not inherit the bucket setting if i understand it correctly. But every object is supposed to have ACL settings as well, hence i tried to add the header for every put request as well. But i think one would like to modify the entity to allUsers..however that might be the same as a pre-defined ACL "public-read".

Thank you harshavardhana, the gc docs seems to indicate that there is a distinct difference between acl for the bucket and the individual objects which do not inherit the bucket setting if i understand it correctly

Yes that is the right interpretation the reasoning is that we don't have an exposed API to add Object ACL's. We deliberately avoided this since 'minio' server inherits canned ACL's to all its objects.  It was done to simplify the ACL style.
We will discuss with in the team to see if we can achieve this.

Thank you harshavardhana, the gc docs seems to indicate that there is a distinct difference between acl for the bucket and the individual objects which do not inherit the bucket setting if i understand it correctly. But every object is supposed to have ACL settings as well, hence i tried to add the header for every put request as well. But i think one would like to modify the entity to allUsers..however that might be the same as a pre-defined ACL "public-read".

Another easier approach is to just use Presigned URLs you can definitely use mc share download <url>.

We decided to not implement Object ACL's, Presigned URL's serve the same purpose and are better.


Shrine::Error (storage :cache isn't registered on PdfUploader)

I've been struggling to figure out why I'm receiving this error on Heroku.
Shrine::Error (storage :cache isn't registered on PdfUploader)
initializer.rb
require "shrine"
require "shrine/storage/s3"

s3_options = {
  access_key_id:     ENV.fetch('AWS_ACCESS_KEY_ID'),
  secret_access_key: ENV.fetch('AWS_SECRET_ACCESS_KEY'),
  region:            ENV.fetch('AWS_REGION'),
  bucket:            ENV.fetch('AWS_BUCKET')
}

Shrine.storages = {
  cache: Shrine::Storage::S3.new(prefix: "cache", upload_options: {acl: "public-read"}, **s3_options),
  store: Shrine::Storage::S3.new(prefix: "store", upload_options: {acl: "public-read"}, **s3_options)
}

Shrine.plugin :activerecord
Shrine.plugin :direct_upload, presign: true

pdf_uploader.rb
class PdfUploader < Shrine
  plugin :determine_mime_type
  plugin :validation_helpers

  Attacher.validate do
    validate_mime_type_inclusion %w(image/jpeg image/png image/gif application/pdf), message: 'must be JPEG, PNG, GIF, or PDF'
  end
end

I'm able to upload to the cache folder in my AWS bucket directly from the DOM with jquery-file-upload and the route I've established for getting the presign URL:
  mount PdfUploader::UploadEndpoint => '/pdfs/upload'
However, when trying to submit my form and create my object in the db, I get the following error:
Shrine::Error (storage :cache isn't registered on PdfUploader)
Any thoughts or suggestions would be greatly appreciated.  Thanks!
PS - for what it's worth - everything works on my local ... this issue is just on Heroku

In the rails console on Heroku I can see that my PdfUploader.storages[:cache] returns nil, while the Shrine.storages[:cache] returns an instance of my AWS S3 storage cache.  Still don't understand why the uploader class is not inheriting this from the initializer.  Conversely, in my local, both PdfUploader.storages[:cache] and Shrine.storages[:cache] return the same object.

I will close this issue over the StackOverflow question, since as I commented there it's most likely that your pdf_uploader.rb somehow gets loaded before initializer.rb on Heroku.

Thanks for the quick reply!  I really appreciate your level of attention.  Sorry to duplicate my comments (as I've already posted this on StackOverflow) but I wanted to make sure I somehow relayed the following (as I'm still curious as to what you believe an ideal solution would be):
My uploader.rb file is within app/models. And it appears that with config.eager_load = true and config.cache_classes = true on Heroku my Classes within app are indeed loaded before the shrine initializer file is loaded (which is in config/initializers). And that is why my uploader never receives the storages. The only fix I've found is to include the following line in application.rb: require_relative './initializers/shrine' beneath Bundler.require(*Rails.groups)

@adamthede It's very unusual that Rails loads models before initializers, even when with config.eager_load = true and config.cache_classes = true, because I'm sure most of other Shrine users that use Rails have the same configuration for production, and this is the first time this problem got reported. I'm thinking there is likely some code that gets executed before your shrine.rb initializer which references the PdfUploader class, thus forcing it to load before the shrine.rb initializer 🤔

This issue deserves a better solution. What about creating a Config class?

@prem-prakash did you run into the problem too? It's a bit of mystery why it's happening, I wouldn't predict it. It would be useful to figure out exactly what's going on, if you have a reproduction and time to dig into it to try to figure it out.
Without knowing exactly what's going on, it's hard to say what would solve it, what kind of "config class" (If the problem is the uploader being loaded before the initializer... what if it's loaded before the "config class"?)
If the problem is really load order (for mysterious reasons), you could put your config in a class in your local ./lib (so Rails won't auto-load it), then have an initializer that requires it, and also require it at the top of your Uploader class(es). That would ensure it's always loaded when needed. But I personally wouldn't do something like that in my app without debugging to diagnose exactly what's going on... it may be just be a symptom of some other underlying problem that will cause other problems too (and not just with shrine), if your Rails app isn't loading expected initialization code.

(I wonder if it's related to "pre-forking", if you're using puma or passenger with such an option... but this is me just kind of guessing)

I tried to find out who is causing this problem, but I was not able, it is kind of hard debugging.
Is there a way to config my storages directly on the class that inherits from Shrine?

Yes, just call self.storages = ... inside the uploader definition.

Hi @janko sorry for the issue, I discoreved my local problem. It was a environment variable APP_ENV that overrides RAILS_ENV.
My initializer had a case...when for each environment normally used in Rails, but not this one set on APP_ENV, and thus my config never got loaded.

I ran into a similar problem working on a Rails engine, where config.cache_classes = true was causing any references to Shrine attachment code to fail. Also sounded potentially similar to https://github.com/shrinerb/shrine/issues/173.
I was able to determine that the initializers in the engine were loading after the rest of the classes in /app/models and /app/uploaders. I worked around this by moving the shrine configuration out the initializers folder and into /lib, then requiring the file in engine.rb.
module MyEngine
  class Engine < ::Rails::Engine
    config.before_configuration do
      require 'shrine'
    end
  end
end


InsertIgnore

Is InsertorIgnore possible with vuexorm axios? For example, If you have cities around the world as entities. Let's say you already have all have half the cities of the world pulled in from different queries.
Now you want to do an API call to get all the cities in North America. You will have duplicates of course. Is there a way to ignore these dupes instead of saving them?
Essentially InsertOrIgnore functionality?

Hello @muhzak Did you get solved this issue?
I have a similar case this function can help me a lot for improving my app


Fix inbox-reddit

First of all, a big thank you for the many scripts ideas you submit. I notified an error in the inbox-reddit.sh script about retrieving unread messages from our Reddit account.
Indeed, it frequently happened to have this error message:
./inbox-reddit.sh: line 6: [: : integer expression expected
I therefore took the trouble to find a solution and also to modify certain minor elements.

It looks like the best is to cherry pick your first commit.

You can encrypt the information but you put this in your curl request.
This means your GitHub-Token and your Reddit-Link are visible for every user in your process list.


Possible to delete data after index creation?

I was wondering whether it's possible to delete the actual data after the index is created, as a potential way to save memory footprint.  I'm not super familiar with the underlying algorithms, so apologies if the data already gets deleted or this is an otherwise silly question.
Thanks

Hi, data is needed.
PS: We should really think about implementing more memory efficient variants :-)

Ah alright  Yes I agree about more memory efficient variants -- something similar to Annoy's mmap functionality would be really wonderful. Thanks for the quick reply!

Yeah, I am actually thinking about mmap-ing data. This will be useful: https://github.com/searchivarius/nmslib/issues/133


Chrome beta

Reviewer:

Description:

Steps to test this PR:

Automated tests:

[ ] Unit tests
[ ] Integration tests

Reviewer Checklist:

[ ] Ensure the PR solves the problem
[ ] Review every line of code
[ ] Ensure the PR does no harm by testing the changes thoroughly
[ ] Get help if you're uncomfortable with any of the above!
[ ] Determine if there are any quick wins that improve the implementation

PR Author Checklist:

[ ] Get advice or leverage existing code
[ ] Agree on technical approach with reviewer (if the changes are nuanced)
[ ] Ensure that there is a testing strategy (and documented non-automated tests)
[ ] Ensure there is a documented monitoring strategy (if necessary)
[ ] Consider systems implications

@kzar closing this out, I think you have landed similar changes for this. I don't think we can use anything here.


Issues about resize ground-truth

During evaluation, shouldn't you resize the prediction to have the same size of ground-truth and compute these stats? I don't think change ground-truth is the correct thing to do ideally.

The authors of coco-stuff pre-scale images and annotations to 513x513 size for both training and evaluation of ResNet backbone DeepLab. You can change the lines below with ground-truth size of labels. Both have the same size.
https://github.com/kazuto1011/deeplab-pytorch/blob/6b395848753e6e3cdd04b1c1227b9e6581e34d4a/eval.py#L87-L89

Thanks for answering quick. I have contacted the authors. I'll leave this open till he replies.

Hi. I agree with @jason718 that the correct behavior is to resize the predictions to full image size and perform evaluation there. Note however that the COCO images are close in size to 513x513, so the effect of this should be quite small. To make the results 100% comparable we provide the COCO devkit, evaluation server and leaderboard so that you can exactly benchmark your method against the literature.


求解 在发送图片时  我发送成功了  屏幕不显示图片 但是点击图片 放大了有显示了 然后报错

报错内容: CGBitmapContextCreate: unsupported parameter combination: 8 integer bits/component; 32 bits/pixel; 3-component color space; kCGImageAlphaLast; 1120 bytes/row.
Aug 28 10:06:41<PHONE_NUMBER>3123962305deMac-mini.local ZZChatiPhone[1992] : CGContextConcatCTM: invalid context 0x0. This is a serious error. This application, or a library it uses, is using an invalid context  and is thereby contributing to an overall degradation of system stability and reliability. This notice is a courtesy: please fix this problem. It will become a fatal error in an upcoming update.
Aug 28 10:06:41<PHONE_NUMBER>3123962305deMac-mini.local ZZChatiPhone[1992] : CGContextSetInterpolationQuality: invalid context 0x0. This is a serious error. This application, or a library it uses, is using an invalid context  and is thereby contributing to an overall degradation of system stability and reliability. This notice is a courtesy: please fix this problem. It will become a fatal error in an upcoming update.
Aug 28 10:06:41<PHONE_NUMBER>3123962305deMac-mini.local ZZChatiPhone[1992] : CGContextDrawImage: invalid context 0x0. This is a serious error. This application, or a library it uses, is using an invalid context  and is thereby contributing to an overall degradation of system stability and reliability. This notice is a courtesy: please fix this problem. It will become a fatal error in an upcoming update.
Aug 28 10:06:41<PHONE_NUMBER>3123962305deMac-mini.local ZZChatiPhone[1992] : CGBitmapContextCreateImage: invalid context 0x0. This is a serious error. This application, or a library it uses, is using an invalid context  and is thereby contributing to an overall degradation of system stability and reliability. This notice is a courtesy: please fix this problem. It will become a fatal error in an upcoming update.
2015-08-28 10:06:43.103 ZZChatiPhone[1992:53269] -[ChatRoomMessageViewController multiMediaMessageDidSelectedOnMessage:atIndexPath:onMessageTableViewCell:] [Line 313] message : <UIImage: 0x7fbf829bf4b0>, {54.5, 54.5}

@zhang1104094894
这个应该是同一个问题


Proxy problem using HTTPS_PROXY environment variable

The variable seems to be in effect, because otherwise butler will show "Version check failed".
But the actual upload part doesn't work, it always fails.

Butler still does not support system proxy today.


[Bug] Reduce mean (tt.mean): Issues with non-tile aligned dims and default TILE_LAYOUT setup

Summary
Issues with reduce mean op when tensor dims aren't tile-dim aligned.
Repro instructions

Remove dim == 2 condition:

if dim == 2:
  pytest.skip("TTNN: Tensor layout bugs")

Run the following command:

pytest -svv pybuda/test/mlir/test_ops.py::test_mean

Details
Exact error msg:

Unable to reshape a tensor in TILE_LAYOUT to non-tile height and width! Please convert the tensor to ROW_MAJOR_LAYOUT first.

Lowered TTIR:
#any_device = #tt.operand_constraint<dram|l1|scalar|tile|any_device|any_device_tile>
#loc = loc("Mean":4294967295:0)
module @"tt-forge-graph" attributes {tt.system_desc = #tt.system_desc<[{arch = <wormhole_b0>, grid = 8x8, l1_size = 1048576, num_dram_channels = 12, dram_channel_size = 1048576, noc_l1_address_align_bytes = 16, pcie_address_align_bytes = 32, noc_dram_address_align_bytes = 32}], [0], [<pcie|host_mmio>], [<0, 0, 0, 0>]>} {
  func.func @forward(%arg0: tensor<1x41x41xf32> {ttir.name = "x"} loc("Mean":4294967295:0)) -> tensor<1x41x1xf32> {
    %0 = tensor.empty() : tensor<1x41x1xf32> loc(#loc3)
    %1 = "ttir.mean"(%arg0, %0) <{dim_arg = [-1 : i32], keep_dim = true, operand_constraints = [#any_device, #any_device]}> : (tensor<1x41x41xf32>, tensor<1x41x1xf32>) -> tensor<1x41x1xf32> loc(#loc3)
    return %1 : tensor<1x41x1xf32> loc(#loc2)
  } loc(#loc)
} loc(#loc)
#loc1 = loc("Mean":4294967295:35)
#loc2 = loc(unknown)
#loc3 = loc("reduce_avg_16"(#loc1))

Trace sample:
#l1_ = #tt.memory_space<l1>
#loc = loc("Mean":4294967295:0)
#system = #tt.memory_space<system>
#layout = #tt.layout<(d0, d1, d2) -> (d0 * 41 + d1, d2), undef, <1x1>, memref<41x41xf32, #system>>
#layout1 = #tt.layout<(d0, d1, d2) -> (d0 * 41 + d1, d2), undef, <8x8>, memref<6x1xf32, #system>>
#layout2 = #tt.layout<(d0, d1, d2) -> (d0 * 41 + d1, d2), undef, <8x8>, memref<6x6xf32, #l1_>>
#layout3 = #tt.layout<(d0, d1, d2) -> (d0 * 41 + d1, d2), undef, <8x8>, memref<6x1xf32, #l1_>>
module @"tt-forge-graph" attributes {tt.device = #tt.device<#tt.grid<8x8, (d0, d1) -> (0, d0, d1)>, [0]>, tt.system_desc = #tt.system_desc<[{arch = <wormhole_b0>, grid = 8x8, l1_size = 1048576, num_dram_channels = 12, dram_channel_size = 1048576, noc_l1_address_align_bytes = 16, pcie_address_align_bytes = 32, noc_dram_address_align_bytes = 32}], [0], [<pcie|host_mmio>], [<0, 0, 0, 0>]>} {
  func.func @forward(%arg0: tensor<1x41x41xf32, #layout> {ttir.name = "x"} loc("Mean":4294967295:0)) -> tensor<1x41x1xf32, #layout1> {
    %0 = "ttnn.open_device"() : () -> !tt.device<<#tt.grid<8x8, (d0, d1) -> (0, d0, d1)>, [0]>> loc(#loc)
    %1 = "ttnn.full"(%0) <{fillValue = 0.000000e+00 : f32}> : (!tt.device<<#tt.grid<8x8, (d0, d1) -> (0, d0, d1)>, [0]>>) -> tensor<1x41x41xf32, #layout2> loc(#loc3)
    %2 = "ttnn.to_memory_config"(%arg0, %1) : (tensor<1x41x41xf32, #layout>, tensor<1x41x41xf32, #layout2>) -> tensor<1x41x41xf32, #layout2> loc(#loc3)
    %3 = "ttnn.full"(%0) <{fillValue = 0.000000e+00 : f32}> : (!tt.device<<#tt.grid<8x8, (d0, d1) -> (0, d0, d1)>, [0]>>) -> tensor<1x41x1xf32, #layout3> loc(#loc3)
    %4 = "ttnn.mean"(%2, %3) <{dim_arg = [-1 : i32], keep_dim = true}> : (tensor<1x41x41xf32, #layout2>, tensor<1x41x1xf32, #layout3>) -> tensor<1x41x1xf32, #layout3> loc(#loc3)
    %5 = "ttnn.full"(%0) <{fillValue = 0.000000e+00 : f32}> : (!tt.device<<#tt.grid<8x8, (d0, d1) -> (0, d0, d1)>, [0]>>) -> tensor<1x41x1xf32, #layout1> loc(#loc2)
    %6 = "ttnn.to_memory_config"(%4, %5) : (tensor<1x41x1xf32, #layout3>, tensor<1x41x1xf32, #layout1>) -> tensor<1x41x1xf32, #layout1> loc(#loc2)
    "ttnn.close_device"(%0) : (!tt.device<<#tt.grid<8x8, (d0, d1) -> (0, d0, d1)>, [0]>>) -> () loc(#loc)
    return %6 : tensor<1x41x1xf32, #layout1> loc(#loc2)
  } loc(#loc)
} loc(#loc)
#loc1 = loc("Mean":4294967295:35)
#loc2 = loc(unknown)
#loc3 = loc("reduce_avg_16"(#loc1))

I looked at this, this is the bug in the the TTNN implementation of reduce op.
In the TTNN implementation of reduction op, there is a code that calculates the output tensor shape:
    std::vector<uint32_t> output_shape;
    std::vector<uint32_t> padded_output_shape;
    for (int axis = 0; axis < input_shape.size(); axis++) {
        if (std::find(dim.begin(), dim.end(), axis) != dim.end()) {
            if (keepdim) {
                output_shape.push_back(1);
                padded_output_shape.push_back(axis >= rank - 2 ? ttnn::TILE_SIZE : 1);
            }
        } else {
            output_shape.push_back(input_shape[axis]);
            padded_output_shape.push_back(input_shape[axis]);
        }
    }

The issue is in this line:
padded_output_shape.push_back(input_shape[axis]);
We iterate through all the dims of the tensor. When we encounter the dim that we are not reducing, we want to capture the non-padded and padded parts of the input shape, but we don't capture the padded part correctly because input_shape[axis] returns the unpadded part. Instead, we should retrieve something like this:
padded_output_shape.push_back(input_shape.value[axis]);

I see, thanks for the details @sdjordjevicTT!
As we're not sure when we'll get this one fixed, is it possible to have a workaround for it on the MLIR level? E.g. if reduce op supports ROW_MAJOR_LAYOUT does enforcing helps out? Or, can we push for explicit pad op that we'll help out here? E.g. to decompose reduce into pad + reduce + unpad set of opsops?
Let me know your thoughts! :))

I would like to understand the process of fixing this on the TTNN side before attempting any quick fixes. We need to investigate further what can be quickly fixed. You gave great ideas, and we can try those as quick workarounds.

I would like to understand the process of fixing this on the TTNN side before attempting any quick fixes. We need to investigate further what can be quickly fixed. You gave great ideas, and we can try those as quick workarounds.

Thanks for pushing this further @sdjordjevicTT! Let me know if you need any more details from my end on this one :)))

The fix is in tt-mlir, reduction ops are now working with non-tile-aligned dims.


Creating Metadata table that already exists

What version of Flyway are you using?
4.1.1
Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin, SBT plugin, ANT tasks)
Command-line
What database are you using (type & version)?
Postgresql 9.6.2
What operating system are you using?
Ubuntu and OS X (no difference for this issue)
What did you do?
(Please include the content causing the issue, any relevant configuration settings, and the command you ran)
Upgraded from Flyway 3.2.1 to 4.1.1
What did you expect to see?
Migrations working like before
What did you see instead?
Whenever Flyway sees a "SET ROLE" command in an SQL file it attempts to create the metadata table again. But since it already exists that causes the migration to fail.
With a .sql file containing only "SET ROLE common;" this is the result:
$ ./flyway migrate
Flyway 4.1.1 by Boxfuse

Database: jdbc:postgresql://localhost:5432/test (PostgreSQL 9.6)
Successfully validated 3 migrations (execution time 00:00.017s)
Current version of schema "public": 1.1.2
Migrating schema "public" to version 1.1.3 - init common
Creating Metadata table: "public"."schema_version"
ERROR:
Script failed
-------------
SQL State  : 42P07
Error Code : 0
Message    : ERROR: relation "schema_version" already exists
Line       : 17
Statement  : CREATE TABLE "public"."schema_version" (
    "installed_rank" INT NOT NULL,
    "version" VARCHAR(50),
    "description" VARCHAR(200) NOT NULL,
    "type" VARCHAR(20) NOT NULL,
    "script" VARCHAR(1000) NOT NULL,
    "checksum" INTEGER,
    "installed_by" VARCHAR(100) NOT NULL,
    "installed_on" TIMESTAMP NOT NULL DEFAULT now(),
    "execution_time" INTEGER NOT NULL,
    "success" BOOLEAN NOT NULL
) WITH (
  OIDS=FALSE
)

Could you include a small test case that reproduces the issue?

Sure. Empty database with a single migration V1_1_1__test.sql that looks like this
CREATE ROLE test LOGIN PASSWORD 'test';
SET ROLE test;


Move tulius’s pre final siege speech?

In tulius’s final speech he mentions “across this bridge”  then mentions the windhelm defences separately. he usually spawns in front of the windhelm war camp, I interpreted these lines in his speech as being one of 2 places.

That bridge to windhelm on the left

The walkway just outside Windhelm before the brick part right next to the stables (the catapults don’t reach there)

In tulius’s final speech he mentions “across this bridge” then mentions the windhelm defences separately. he usually spawns in front of the windhelm war camp, I interpreted these lines in his speech as being one of 2 places.

It's 2. (In regards to the catapults, that's still an open item. If you haven't noticed, the Imperial Camp catapults don't fire :(  )

If you haven't noticed, the Imperial Camp catapults don't fire :( )

Never noticed, but I was referring to the ones coming from windhelm their projectiles miss those locations


Fixing the broken cv and cv_url methods on bio_edition.

This broke when we changed attachments to attachment
https://github.com/biola/buweb-content-models/commit/0a9639a79d4eb8227aeb00aef86d76905d284722

+1


[PO-42] Simple mining startup

The goal of this PR is to add a simple way of unlock "mining" accounts in order to allow them to sign blocks.
unlockMinerAccount.sh
#!/bin/bash

server_and_port=$1 # http://<IP_ADDRESS>:8546
address=$2 # 0xedde8656c35fcb7126c61fc6e2673734425a72bf
password=$3 # 1234

echo $server_and_port $address $password

curl -X POST \
  "$server_and_port"/ \
  -H 'cache-control: no-cache' \
  -H 'content-type: application/json' \
  -d '{ "jsonrpc": "2.0", "method": "personal_unlockMinerAccount", "params": ["'$address'", "'$password'"], "id": 1}'

example of use:
./unlockMineAccount.sh http://<IP_ADDRESS>:8546 "0xedde8656c35fcb7126c61fc6e2673734425a72bf" "1234"

new PR target to: https://github.com/ntallar/mantis/pull/14

new PR target to: https://github.com/ntallar/mantis/pull/14


Use pyannote-audio for speaker diarization

Logic will be to combine Whisper + pyannote.audio based on timestamps to output something along the lines of:
Person A: Hi
Person B: Hello, how are you
Person A: I'm good, and you?
....

I am working on the same subject, you can find work done by Majdoddin here: https://github.com/Majdoddin/nlp
Not perfect but a good way to start. I ll push my solution when done

@remic33 Cool - any plans to build into Whisper Playground?


[AWS::Redshift::Cluster] Drift Detection issue for Classic property under AWS::Redshift::Cluster resource

There is an issue with this resource type whereby false-positive drift is reported for the Classic property. A similar ticket has been opened in the Cloudformation roadmap, but opening another here as this team is responsible for this resource type handler.
Will be happy to provide any further info as required.

Name of the resource
AWS::Redshift::Cluster
Issue Description
The Classic property for the AWS::Redshift::Cluster resource is marked as drifted when its value is specified as false.
Expected Behavior
The Classic property should be IN_SYNC or NOT_CHECKED status.
Observed Behavior
The Classic property is marked as REMOVE with
expected = false
actual = -

Test Cases
Steps to reproduce -

Create Stack using following template -

Resources:
    myCluster:
      Type: 'AWS::Redshift::Cluster'
      Properties:
        DBName: mydb
        MasterUsername: master
        MasterUserPassword: xxxxxxxxxx
        NodeType: ds2.xlarge
        ClusterType: single-node
        Classic: false

Run drift detection
View drift results

Retested and confirmed.
CDK v2.76.0
        key = kms.Key(self, "MyKey",
                      removal_policy=RemovalPolicy.DESTROY,
                      )

        cluster = CfnCluster(self, 'ClusterMitKmsId',
                             cluster_type='single-node',
                             db_name='dev',
                             master_username='bevelvoerder',
                             master_user_password='Wagw00rdEen',
                             node_type='dc2.large',
                             encrypted=True,
                             kms_key_id=key.key_id,
                             classic=True,
                             )
        cluster.apply_removal_policy(RemovalPolicy.DESTROY)

Expected
{
  "KmsKeyId": "xxxxxx-xxxx-xxxx-xxxx-xxxxxxxxx",
  "Encrypted": true,
  "NodeType": "dc2.large",
  "MasterUsername": "bevelvoerder",
  "DBName": "dev",
  "ClusterType": "single-node",
  "Classic": true
}

Actual
{
  "KmsKeyId": "arn:aws:kms:eu-central-1:00000000000:key/xxxxxxxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
  "Encrypted": true,
  "NodeType": "dc2.large",
  "MasterUsername": "bevelvoerder",
  "DBName": "dev",
  "ClusterType": "single-node"
}


Microsoft di and roslyn compiler

Using the Microsoft.Extensions.DependencyInjection apis to resolve dependencies

Removed ISparkServiceInitialize and ISparkServiceContainer (and it's implementation)
Constructor injection is used instead of auto-initializing properties
New IBatchCompiler interface so that we can use different compilers

~2x performance improvement when compiling views with Roslyn
CodeDom compilation can still be used at the moment (class marked as obsolete)
CodeDom marked as obsolete (as it will not generating code for .net core) and wrapped into #if NETFRAMEWORK block

I found a problem when using roslyn to compile the views: each time a view is compile an assembly is loaded into memory and never released. This means spark will eat up all the memory available and eventually OutOfMemoryException are thrown.

Good catch! I'll take a look again when you've found a workaround for this.
On Tue, 13 Feb 2024 at 11:00, Benjamin @.***> wrote:

I found a problem when using roslyn to compile the views: each time a view
is compile an assembly is loaded into memory and never released. This means
spark will eat up all the memory available and eventually
OutOfMemoryException are thrown.
—
Reply to this email directly, view it on GitHub
https://github.com/SparkViewEngine/spark/pull/77#issuecomment-1941214242,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABFDZJW4B5NUDTOOE24Z7DYTNBWNAVCNFSM6AAAAABCIVX6P2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNBRGIYTIMRUGI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

I can't think of a fix for .net framework. I think the best it to carry on using the non roslyn compiler.
For .net core loading the assemblies into a MetadataLoadContext might be an avenue to explore.

Is it worth going down the Source Generation route during compile time maybe?

Is it worth going down the Source Generation route during compile time maybe?

Definitely something worth exploring. It would be ideal to have the same options/behaviour as with MVC Razor (e.g. the choice to compile the views are build time (default) or to leave it for later at runtime).
I couldn't find any docs explaining how Microsoft does compile their razor views at build time...


clearTimeout() does not always work

Problem description
When calling clearTimeout() asynchronously, it does not always cancel timeouts. In the snippets below, about 1/3 of the setTimeout() callbacks will be called, although they have been scheduled in cleared timeouts.
See the second snippet for a more illustrative example of the issue that shows that some setTimeout() callbacks are executed even after their timeouts have been cleared.
Expected behavior
Timeouts must never be executed after clearTimeout() with their id is called.
Environment

Tabris.js version: starting from 3.0.0 to at least 3.5.0-dev.20200514
OS: iOS

Code snippet
Simple snippet
import 'tabris';

for (let i = 0; i < 3000; i++) {
  const timeout = setTimeout(() => console.error('unexpected callback call'), 1000);
  setTimeout(() => clearTimeout(timeout));
}

Verbose snippet
import 'tabris';

let taskId = 0;
const status = {};
for (let i = 0; i < 3000; i++) {
  taskId++;
  status[taskId] = 'scheduled';
  const timeout = setTimeout((id =>
    () => {
      let message = `Called task ${id}`;
      if (status[id] === 'canceled') {
        message += ' although it was canceled. clearTimeout does not work?'; // about 1/3 of the tasks
      } else if (status[id] === 'scheduled') {
        message += ' as expected, because it was scheduled and never canceled. clearTimeout called too late?'; // never
      }
      console.error(message);
    }
  )(taskId), 1000);
  setTimeout((id =>
    () => {
      clearTimeout(timeout);
      status[id] = 'canceled';
    }
  )(taskId), 0);
}

I tested both snippets, with the same results.
The first timer was scheduled at: 08:23:13.871 and invalidated at: 08:23:15.689.
15.689 - 13.871 = 1,818s
for loop used for scheduling timers is blocking the main loop for 1,8s. When clearTimeout is called it is too late for invalidation.
Assuming that timers are executed in the FIFO order (and it looks like that) the first one will always be called first - before the second one which invalidates the first one. Even if they are all delayed and they are because the main loop was blocked (UI not responsive and so on).
Log from the native bridge:
[08:23:13.871000][E][{ method = startTimer; }][{ properties = { delay = 1000; id = 1; repeat = 0; };}]
[08:23:13.871000][E][{ method = startTimer; }][{ properties = { delay = 0; id = 2; repeat = 0; };}]
[08:23:13.872000][E][{ method = startTimer; }][{ properties = { delay = 1000; id = 3; repeat = 0; };}]
[08:23:13.872000][E][{ method = startTimer; }][{ properties = { delay = 0; id = 4; repeat = 0; };}]
[08:23:13.872000][E][{ method = startTimer; }][{ properties = { delay = 1000; id = 5; repeat = 0; };}]
[08:23:13.872000][E][{ method = startTimer; }][{ properties = { delay = 0; id = 6; repeat = 0; };}]
(...)
[08:23:15.601000][E][{ method = startTimer; }][{ properties = { delay = 0; id = 5996; repeat = 0; };}]
[08:23:15.602000][E][{ method = startTimer; }][{ properties = { delay = 1000; id = 5997; repeat = 0; };}]
[08:23:15.602000][E][{ method = startTimer; }][{ properties = { delay = 0; id = 5998; repeat = 0; };}]
[08:23:15.602000][E][{ method = startTimer; }][{ properties = { delay = 1000; id = 5999; repeat = 0; };}]
[08:23:15.603000][E][{ method = startTimer; }][{ properties = { delay = 0; id = 6000; repeat = 0; };}]
(...)
[08:23:15.689000][E][{ method = cancelTimer; }][{ properties = { id = 1; };}]
[08:23:15.692000][E][{ method = cancelTimer; }][{ properties = { id = 3; };}]
[08:23:15.694000][E][{ method = cancelTimer; }][{ properties = { id = 5; };}]
[08:23:15.697000][E][{ method = cancelTimer; }][{ properties = { id = 7; };}]
...

In your snippets, you set up 3000 timers with 1s delay. Knowing that on my device it takes ~1,8s to set them up (main thread is blocked during that time) I changed the snippet so that it sets only 1500 times - and it worked as expected. Same when I set up 3000 timers but with longer timeout - set to 2s.

I found that this issue does not occur in 2.x, what essentially means that Tabris.js 2 has a higher performance in this test case. It took 0.809s to schedule timers. That is fast enough to invalidate them on time.
We should take a look why there is  such a difference between 2.x and 3.x in this case.


Z5: Export fails at the second time

Build 4011. After installing, export works properly. But only at first time. All the next exports of the same fails, ever after deleting better-bibtex.sqlite and better-bibtex folder. Uninstalling and installing BBT helps, but only for the first export.
I can export another collection, but also for the firs time, all the subsequent export of once exported collection fails.
ReportID: LEXA2B47 for the one of the collection, ID PWRU64TQ  for the second one.

Man that part of the code needs a thorough going through

Anyway, 4012 corrects the problem.


README.md English tweaks

English is a terrible language, I'm sorry that it's so weird and ill-formed.  As a speaker of at least two languages, you have my respect regardless.  I just thought I'd rephrase some of this language as a native speaker would.
I don't know exactly what is meant by

As your app's components will increase in size, it can be refactored to similar structure that implemented in - semantic-ui-react.

Do you mean that as the application grows then it can be refactored to a similar structure as the semantic-ui-react starter project?  I think that is what is meant.
🌻

Oh, great thanks for this PR :)
Yes, I mean that as the app grows then the structure of components folder could be refactored to the structure of semantic-ui-react: Addons, Views, etc.


COMPILE cfg file to npu model

Make ONE-vscode compile cfg file to npu model.

On UI, we can see cfg file and click the file with the right button and then we can choose compile to run compiling cfg file to npu model.

@Samsung/one-vscode is this done?

Currently, the part that directly calls onecc and execute cfg file has been implemented. However, the part that uses the installed toolchain has not been implemented. I will implement this part on this release.


Multiple Constructors require different syntax

Originally from here: https://github.com/fsharp/fsharp/issues/827
When adding constructors to to an F# class the required syntax changes, e.g. is different for the last constructor (for single parameter .ctors).
Repro steps
While the following code is valid…
type A (a : int option, b : string option) =
    new a = A (a, None)
    member __.X = ""

… adding another .ctor with one parameter in a similar fashion does not validate anymore:
type A (a : int option, b : string option) =
    new a = A (a, None)
    new b = A (None, b)
    member __.X = ""

The error on the = on the third line is: error FS0010: Unexpected symbol '=' in expression
Known workarounds
Parameters of the not-last .ctor must be wrapped in braces. For a yet bigger example this gives:
type A (a : int option, b : string option, c : float option) =
    new (a) = A (a, None, None)
    new (b) = A (None, b, None)
    new c = A (None, None, c)
    member __.X = ""

(Also omitting the first brace (in new (a)) does break the thing.)
Related information
Observed on Win 10 in VS and Ionide with latest releases installed.
Severity is most probably low.

Out of curiosity I was curious whether this happened in VS2015 as well. The error is a bit clearer (i.e., not on the equal-sign, but on the whole constructor), however still not very helpful:

The correct thing is always to use new (arg) = ....  Parentheses are required here.
My reply on fsharp/fsharp:
@ChrSteinert This is a parser thing where it is thinking new c is an expression, e.g. new Object(). In the first line it is not seen as ambiguous because there is no possibility of an expression at that point in the syntax (it's one of the only points where that's not possible).
We could give a warning since I can see how you could hit this. The warning would ask the user to write new (arg1, ... argN) in constructor definitions, always using parentheses.


Rules for Debian distribution

This PR adds the following:

java_deps rule which takes in java_binary and puts it together will all dependencies into a .tgz archive at directory java_deps_root. This is only meant for internal consumption of pkg_deb
deploy_deb macro which builds final .deb:

deploy_deb(
    name = "X"
)

Resulting Debian package will be called X, target to build it is //:X-deb

At one point, we need to make deploy_deb to actually deploy to a Debian repository, which we define in deployment.properties like so, right @vmax ?
debian.repository-url=https://a.url.to.a.debian.repository.com

@lolski this is right. currently deploy_deb only builds that deb


achcli Custom Validation

ACH Version
1.21.2
What were you trying to do?
I am looking to add Validation options when using achcli.
What did you expect to see?
I am expecting a command argument or similar to allow for custom validations.

That seems like a good improvement. I think command line flags are case-sensitive so -validation. allowUnorderedBatchNumbers would work but could only be specified in that exact case. I'm fine with that, but we could read a JSON config file as well.
{
  "validateOpts": {
    "allowUnorderedBatchNumbers": true
  }
}


Getting started - WiFi "not available" after password

I'm following the Getting started with your Brick docs for EV3 with Stretch.
I'm able to scan for WiFi networks, see mine, and select it, but by the time I'm done entering the password, the network is "not available". The network list will refresh, then I can select it again, but again it will apparently time out before I can get the password entered.
Is this in fact timing out? Any way I can past this issue?

I've tried this on a separate WiFi network with a shorter password (all lowercase and no symbols), and that works. My home WiFi network password is a mixture of upper and lower case and symbols, and I can't get that to work.

mmmm, Yes, Maybe in the past I had that issue. If you don´t type faster with the virtual keyboard, I recommend to plug an USB Keyboard to EV3 and type directly. In that way, you should not reach the timeout.
Cheers

Do you continue with the issue? @AlanKrueger


Filter draft brief responses from list

For this story on Pivotal.
The first 5 commits in the PR are included in this PR. This PR needs to be rebase on top of master once the other PR is merged to remove them, but only after this PR for a data migration has been merged.
Brief responses should only be listed if their status is published. This PR filters out the drafts before returning the list of responses.

Pull request closed as filtering out draft brief responses now contained in this pull request


Cannot link two tasks with watch mode

Hello everyone,
Is it possible to link up a compile task with a bundle rollup task ?
I would like to do these two things at once with "watch" attribute !

VSCode Version: 1.19.3
OS Version: Windows 10

This code doesn't seem to work
"version": "2.0.0",
"tasks": [
{
"label": "Buid",
"dependsOn": [
"Compile",
"Rollup"
],
"problemMatcher": []
},
{
"label": "Compile",
"type": "typescript",
"tsconfig": "tsconfig.client.json",
"problemMatcher": [
"$tsc"
]
},
{
"label": "Rollup",
"type": "shell",
"command": "./bundleUpClient.bat",
"args":[]
}
]

@Bawen34 if you want the rollup task to start when the compile task as finished a watching round then this is currently not possible. Is this what you try to achieve?

It would be the best case scenario...
How to do it without watch mode then?

unsubscrible
2018-02-06 22:45 GMT+08:00 Bawen34<EMAIL_ADDRESS>
Closed #42975 https://github.com/Microsoft/vscode/issues/42975.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/vscode/issues/42975#event-1460259717, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACCgkSI-Ghv3970l_GpXHoy5kZF8P4LQks5tSGVzgaJpZM4R5qnG
.

--
Justin.C.Zhang,
AI Engineer,
Cetc-Cloud.Inc.,
Important: This email is confidential and may be privileged. If you are not
the intended recipient, please delete it and notify us immediately; you
should not copy or use it for any purpose, nor disclose its contents to any
other person. Thank you.


[Bug] Make configurators hashable

Old approach generated hashable identifiers for configurators every time with different values and DiffableDataSource could recognise it like new data, but it was still the same data, so it led unnecessary update of cells on home screen.
This PR introduces another approach, which generates hash of configurators depending on the stored properties.

Hi, Thanks for the contribution. I looked through the code and it raised some questions. Would be great if you could address them 👍
I would also like to highlight that this PR is not passing our test coverage quality gate.

Thanks for your time reviewing this PR. Please have a look at my comments below.

@melloskitten could you please review it again? thanks

Hi @aleksandr-tikhonov thank you for answering my questions. There is still a typo left over. If you could fix that, I will give you my approval. cheers!

Hi @aleksandr-tikhonov thank you for answering my questions. There is still a typo left over. If you could fix that, I will give you my approval. cheers!

Besides comments from @melloskitten , I think it's good to go.

Hi @aleksandr-tikhonov thank you for answering my questions. There is still a typo left over. If you could fix that, I will give you my approval. cheers!

I fixed typo :)

Hi @aleksandr-tikhonov thank you for answering my questions. There is still a typo left over. If you could fix that, I will give you my approval. cheers!

I fixed typo :)

Thanks, Aleks. I approved it


Set a nicer title

Codecov Report

Merging #763 (e390839) into main (72cff19) will not change coverage.
Report is 2 commits behind head on main.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main      #763   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           86        86
  Lines         3316      3316
=========================================
  Hits          3316      3316

Files
Coverage Δ

policy/release/external_parameters.rego
100.00% <ø> (ø)


create notification for a new repo at the top

if the next top repo is not the same as the previous refresh, then create a notification!

This can be implemented with #19 too, but I missed it. :(
Will add in.

:+1:

closed with #19


Medieval Weapons Crash

Mod Name
Medieval Weapons
Mod Homepage
https://www.curseforge.com/minecraft/mc-mods/medievalweapons
Minecraft version
1.20.1
Describe the bug
The game crashes and says that it couldn't initialize client because of errors provided by Medieval Weapons
Steps to reproduce
1.Start Game with medieval weapons
2.Wait until it crashes
3.There you go!
Logs
Not Available
Additional context
I only have sinytra connector and forgified fabric with the mod

Confirmed to work on Forge 47.1.3 and Connector Beta 39


[DEV] Augment and Validate Project Date Data (Breaking Change)

Summary
Every project within projects.json that has a category of 'repo' has been given a date field called createdAt. Projects that had a field in the past called date have now been replaced with this new property: createdAt (breaking change)
Related Issues and MRs
Closing #23
What changed

Add a date for each project that has a category of "repo"
Update Project struct in validate.go. Date field is now required for all project categories.
date has become createdAt (breaking change)
Update CONTRIBUTING.md with data shape information.

Steps for reviewer

Pull changes

git checkout brian/date-validation

Set the currentBranch value on line 31 of validate.go to "main"
Run the validator on projects.json:

go run validate.go

Ensure all projects have a date field called createdAt
Ensure the meta data of the CreatedAt field is accurate within validate.go

Additional resources
N/A

Where did we end up with 301 redirects? I see the Twilio one is causing this to fail. It might be worth omitting this entry if there isn't a reasonable workaround.

Where did we end up with 301 redirects? I see the Twilio one is causing this to fail. It might be worth omitting this entry if there isn't a reasonable workaround.

I haven't been able to come up with a workaround. It may be best to remove this entry and later apply it back to the projects once we can resolve this issue.

Where did we end up with 301 redirects? I see the Twilio one is causing this to fail. It might be worth omitting this entry if there isn't a reasonable workaround.

Just fixed the error. It looks like the link was resolving to one that included: en-us. I replaced the URL with the revised one and our validation checks pass.

Thank you!


Are there plans to make a code generator?

Hi! Are you planning to implement code generation from a given AST? Or are there any other open source generators available?

Hi @akxcv! Could you give me a better example of the type of code generation you are looking for?
I had originally toyed with the idea of being able to serialize an arbitrary AST back to its code representation, but I quickly realized that the AST would have to largely avoid losing any kind of information during the parse (e.g. escaped characters, heredoc delimiters, etc.).
The usecase I had in mind there was for potentially linking back to the script source. I reached the conclusion that it would probably be better to track the source itself for diagnostic purposes (which hasn't been implemented yet) rather than try to rederive it.
That said, it could be possible to use a custom AST which carries extra bits of info, but I'm trying to get a better idea of what you're hoping to achieve before giving more advice!

Sorry, I think I'd forgotten the use case I had in mind. Or, perhaps, I felt I needed code generation for something, but I don't.
I think I'll close this issue for now and reopen it if needed.


updater: Don't create a new task when the old one can't be stopped

This corrects some problems with #1492. That PR avoided tasks getting
stuck in READY by continuing to start the new task if old one couldn't
be stopped. The problem with this is that the old task may have been
restarted due to a failure, which effectively causes that slot to get
updated to the latest version - so there would be two up-to-date tasks
running in that slot. The Docker 1.12 behavior, which is the correct
behavior, is to avoid creating a new task if the old one can't be
stopped.
Also, fix DelayStart to avoid waiting for oldTaskTimeout if no old task
was given.
Finally, change oldTaskTimeout to use a timer which is stopped when the
function returned, instead of a time.After which can leak a long-running
timer.
cc @dongluochen

Current coverage is 55.34% (diff: 40.00%)

Merging #1504 into master will decrease coverage by 0.05%

@@             master      #1504   diff @@
==========================================
  Files            82         82
  Lines         12914      12930    +16
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           7154       7156     +2
- Misses         4776       4781     +5
- Partials        984        993     +9

Powered by Codecov. Last update 31f6a0d...6b3d267

LGTM

LGTM


SSLHandshakeException using a Proxy Config

See:
https://groups.google.com/forum/#!topic/membrane-monitor/Q53ewuB6ZFg
Hi,
More news today.
I've try to make a test with a java core batch in the same context (same server, same proxy...) :
    public static void main(String[] args) throws Exception {

    CloseableHttpClient httpclient = HttpClients.createDefault();

    try {

    HttpHost target = new HttpHost("www.google.de", 443, "https");

    HttpHost proxy = new HttpHost("gateway.xxxx.zzzzz.net", 80, "http");

    RequestConfig config = RequestConfig.custom().setProxy(proxy).build();

    HttpGet request = new HttpGet("/");

    request.setConfig(config);

    CloseableHttpResponse response = httpclient.execute(target, request);

    try {

    System.out.println(response.getStatusLine());

    EntityUtils.consume(response.getEntity());

    }

    }

    }

--> It's work : HTTP/1.1 200 OK
If I switch "http" by "https" in this line
HttpHost proxy = new HttpHost("gateway.xxxx.zzzzz.net", 80, "https");

I get the same error than with membrane :
Exception in thread "main" javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake [...]

--> It's sounds like membrane try to access to my proxy server with HTTPS protocol instead HTTP.
Do you know how can I force membrane to access to my proxy with HTTP protocol ?
Best Regards.

Any update on a fix for this - I'm experiencing the same situation.  We are trying to reverse proxy from a local url (on membrane) to a public https service through a corporate web proxy "firewall"

I went ahead and implemented the proposed fix above, which is working for me in a client's locked down corporate network.    Attached is git diff/patch file with the changes.
enable_ssl_via_proxy_connect.diff.zip

Hi @malsmith-cs,
thanks for the patch. Could you generate a pull request based on your patch?

I could do that - should I post that against the latest master branch?  My changes were done against 4.0.19 because that is was "production" for us.  Either is fine with me.

@malsmith-cs I planned to implement support as described in my comment above. The tests are already completed. A little bit of refactoring in the core module is required to cleanly implement all 4 cases. Let me take the diff as a basis. Thanks!

@rrayst
Ok - even better, please use my diff/patch in any way you see fit.  Consider this my full and complete release of the code/changes.   I look forward to your final & test covered, changes!

Change set looks good to me.  You may need to consider the copy right block in this
https://docs.oracle.com/javase/7/docs/technotes/guides/security/jsse/samples/sockets/client/SSLSocketClientWithTunneling.java
It's open source but it should have a proper reference for the doTunnelHankshake function.

Thanks @malsmith-cs , you are absolutely correct.
Thanks for pushing us to finally merge a fix. :)

I have exactly the same issue here. When do you predict having a new binary release?

4.2.3 has been released.

Hi @rrayst , thanks for the quick reply, just checked membrane's download archive and I cannot find that version 4.2.3, the latest I can find is 4.2.2, can you send the link?
Archive: http://www.membrane-soa.org/downloads/archive/router-archive.htm

Hi @saraivamarco . Sorry, the homepage hasn't been updated yet. You can find the release on https://github.com/membrane/service-proxy/releases/tag/v4.2.3 .

@rrayst it works now! great! 👍


Docs as Code for source installation

Change Description

Problem: The source install procedure documentation is typically updated last, after changes to CI and EOSIO have happened.
Solution: Refactor CI scripts and pipelines to pull commands from documentation so we ensure updates are made to the docs before CI can pass. This causes all teams involved to be responsible for updating the docs, instead of only Developer Relations.
What these changes do:

Generation of tags (docker & anka) is done using every code block EXCEPT for the TEST block and any others wrapped in an "IGNORE" comment.

Why? We use CTEST and not make test in our scripts so we can split up the tests into individual jobs/steps.
We need to test everything that a community member would run. This is an improvement over how we currently generate tags since we only run the dependency install and don't test if they actually work or not. We can avoid filling up the registries with bad images.

$HOME/eosio is the new root. The commands will clone into $HOME/eosio/eos. However, all dependencies and eos binaries will end up in $HOME/eosio/install/(bin|lib|etc).

If users want to have more than one eosio installation on their system (common for BPs), they can modify the $EOSIO_LOCATION env from the instructions.
CDT and Contracts will also use $HOME/eosio/cdt & $HOME/eosio/install, etc. This allows for the creation of a new build script that will pull the install commands from the docs in a specific branch of each product/repo (eosio, cdt, contracts) and then install them in the right order for community members.

Code block rules/conversions:

The following are removed from all code blocks: grep -v -e '<!--' -e '-->' -e '```' -e '\#.*' -e '^$'
All code blocks in the MD files are wrapped with a comment like <!-- DAC CLONE --> or <!-- DAC BUILD -->, allowing our scripts to pull specific sections.
Anything inside of <!-- DAC IGNORE comments are ignored (like the test block)
Indented lines are executed together with the last non-indented line. This allows you to execute multiple commands in the same docker layer.

Dockerfile

Lines matching ^[ ].* (a space at the start of the line) are printed without any modification.
Lines starting with ^export.*=([^\s]+)$ are converted to have ENV before them so that they're available in the docker tag creation process and not a specific layer.

Mac SH script

Nothing :)

We tested that eosio.contracts works with the image generated from this: https://buildkite.com/EOSIO/eosio-dot-contracts/builds/991#_
Consensus Changes

[ ] Consensus Changes

API Changes

[ ] API Changes

Documentation Additions

[x] Documentation Additions

Renaming scripts from .sh to .md doesn't make them documentation.

Renaming scripts from .sh to .md doesn't make them documentation.

Would you be able to elaborate for me? I'm not sure I understand what you mean.

Decided to go a different direction.


Can't quit/abort game w/o saving

Also, ctrl-c is disabled.

Changed two debug commands to regular ones.  'Q' is to quit w/t saving.  'S' is to save (in the dungeon only).


Alternative outputs with different formats

References: #257, #383
The user should be able to specify a list of other elements (inputs, others?) that can be populated when the selected date changes, with formats that differ from the format option.  This would effectively be a list of "write-only" secondary outputs that would function in the same way as the main input/element.
A thought:
$('.datepicker').datepicker({
    format: "yyyy/mm/dd",
    outputs: {
        // <input type="hidden" class="otherinput" name="server-parseable-date">
        "mm-dd-yyyy": $('.otherinput'),
        //
New event on

        "MM d, yyyy": $('.title .date')
    }
});

Although it should have a properly descriptive option name -- ideas so far include "outputs", "alternatives", "secondaries", none of which really make me happy.

Is there any work started on this ?
Shouldn't https://github.com/eternicode/bootstrap-datepicker/issues/383#issuecomment-33832885 be the best approach for this case ?
Like in the changeDate event, return in the arguments (in plus with the default JS date object) a date object flavored with a format function ?


Are the latest non-rc releases really "pre-release"?

Releases recently all have the "pre-release" tag, for example https://github.com/k3s-io/k3s/releases/tag/v1.29.1%2Bk3s2
Is this intentional?
If not, I'd just like to say that this breaks various auto updates for Renovate.

Our process is to leave them as pre-release until our QA team finishes post-release checks. Once that is done, the pre-release flag will be cleared.

Alright, no issue then. Thanks for the prompt response.

What specifically does this break with Renovate? Do you have an open issue with that project?

No, Renovate won't pick up a "pre-release" update, which is the correct behaviour anyway.

Yes. Sounds like everything is working as designed?


⚠ Bofrost.lu has degraded performance

In b961018, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1015 ms

Resolved: Bofrost.lu performance has improved in 0a56d03.


Source for the website

This website is not developed by me. It is a modified version of a free template downloaded from https://colorlib.com/, as mentioned in the website footer. Therefore isn't mine to release.


Add Linux Package Manager Support

Problem

Currently the Extension only supports winget

Solution

Dynamically Check Which Linux Package Manager is Installed and Give Install option accordingly (Using command-exists)

Lines to Work on

const choices = [];
const choices = [];

I'll get this done.

@NotTahaAli Please test this branch for Windows and let me know if further changes are required.

Mismatch in Choices
if (choice === 'Install NASM Using Winget') {
const package_managers = ['winget','pacman', 'apt', 'yum', 'dnf', 'brew'];
options contain Install NASM Using winget, while trying to look for Install NASM Using Winget.

Please use commandExists instead of file check to accommodate various install directories as Linux package managers automatically add to default path
This can be found on many lines of enable.ts such as

if(existsSync('/usr/bin/nasm')){
if(existsSync('/usr/bin/nasm')){
And Others


[CAN'T REPRODUCE] Form stops displaying when creating shipping address

From #730 - smoke testing Dec 18 lib release
After creating a Shipping Address, (moving on to step 2: Shipping Method), I was not able to continue. When I wen't back to Step 1: Shipping Address, nothing appears and now I am stuck

Wasn't able to reproduce that behavior. Tried that on account with some shipping addresses defined and it worked there. On a fresh account, it also worked without problems.
I assume it happened, because of some connection problem, request failure. We can implement some retries, but it should be done in whole checkout, not only this step.

fixed as part of #1248 by tobias


[Components][Tooling] Define a gesture to mark a component as a "root" component

This component will only ever be prerrendered and will be used as the entry point for the entire application. When this is the case we will treat some aspects of the component differently. For example we will allow scripts to appear normally within the component without requiring suppress-error="BL9992"
@* Alternative 1 *@
@root
@* Alternative 2 *@
@prerrendered
@* Alternative 3: Rely on the <!DOCTYPE html> declaration at the beginning of the file *@
<!DOCTYPE html>
<html>
<head>
    <meta charset="utf-8" />
    <meta name="viewport" content="width=device-width">
    <title>Razor Components</title>
    <base href="/" />
    <link href="css/bootstrap/bootstrap.min.css" rel="stylesheet" />
    <link href="css/site.css" rel="stylesheet" />
</head>
<body>
    <app></app>
    <script src="_framework/components.server.js"></script>
</body>
</html>

Related: https://github.com/aspnet/AspNetCore/issues/7528

@rynowak Do you have any input in here?

What are the problems that need to be solved? Is it just the warning for scripts?
Like if you suppress the warning, is there anything blocking or wrong or bad?
OR is there a general problem where you need to be able to separate prerender-only content from dynamically-updating content?

It's essentially the scripts warning for now, but there are other tags that we should warn about on non-pre-rendered content. Some of which are <base>, <link>, <meta>, <title>, <head>, <body>, <html>.
In general pre-rendered content can be anything, non-pre-rendered content is more limited to things that go inside the <body> tag.
It can also be good to be able to mark a component as pre-rended only in order to provide better warning when it gets included in a non static context. Kind of like constexpr (do I get Ryan points for the C++ reference here?)

Also things like '~/' or accessing the HTTP context, etc.

We could probably change this https://github.com/aspnet/AspNetCore-Tooling/blob/master/src/Razor/src/Microsoft.AspNetCore.Razor.Language/Components/ComponentScriptTagPass.cs to be something more like ComponentsAllowedTagsPass or something similar.
We could introduce a couple of base classes

ComponentDocumentBase
StaticComponentBase

This way we cold have a gesture for 'root' components that is simply @inherits ComponentDocumentBase and a gesture for prerendered only content that is @inherits StaticComponentBase.

StaticComponentBase represents using a component as a partial and does a few things:

Disables the html, head, body, and doctype declaration tags.
Enables the `script, link, title, meta, base tags.
Our implementation makes HttpContext available through the base class as a cascading parameter (that we include when we call RenderComponentAsync())
Makes "~/" resolve to the app virtual path.
Disallows using bind, event handlers and other features inside this component that are not going to work.

DocumentComponentBase
Extends StaticComponentBase and enables the remaining tags

We pretty much do this now via <component> being able to render markers for both client and server-side root components.
As for the other things about <script> tags etc., it's not clear we'd want that now we've gone in different directions since this was first filed.
I'll close as I don't think this matches closely with our likely plans, but it could be reopened if I'm wrong!


Going forward and back in the browser loses position in the feed/tab

Describe the bug
I'm going through one of my feeds that I have pinned in the top tabs, clicking on some posts and going back to the feed. I've noticed that sometimes the app resets tab selection to the Following feed. I think I've found a way to reproduce this consistently.
To Reproduce
Steps to reproduce the behavior:

Select a tab in the top bar for one of the custom feeds that you have pinned.
Scroll down the feed a bit.
Click a post in the feed to go to the post details page.
Press "Back" in the browser to go back to the feed.
Now, press "Forward" in the browser to go to that post details page again.
And now press "Back" in the browser again.
You are now on the "Following" feed tab instead of the feed that you were on, and the feed will reload from the beginning when you select that tab again.

Expected behavior
If you select a post in the feed and then repeatedly do Back - Forward - Back - Forward etc., you should keep switching between the post details page and the feed page, keeping that feed tab selected and keeping the scroll position in the feed.
Details

Platform: macOS 12.6.8 (21G725), Safari 16.6 (176<IP_ADDRESS>.3, 17615)

Pretty sure we fixed this one a long time ago lol. But feel free to tell me if not.

@haileyok pretty sure this is still an issue. I think I've narrowed it down too. It only seems to happen when navigating Forward until there is no more forward navigation left.
 Then once I go back to the feed (either through pressing Back enough times or clicking Home in the sidebar) my scroll position is reset.
Should I open a new issue for this?

I did some digging and I think this might be bug 2 described here https://github.com/react-navigation/react-navigation/issues/10915.
Walking through it with a debugger I can see that React Navigation's history stack gets corrupted because the internal index is not incremented/decremented when using browser navigation (in this case the index will generally stay on the last item on the stack because of that, continuously overwriting it, which explains why it's that one specifically that generally triggers the reset).
I also saw #6534 so I looked at Expo Router's fork of React Navigation as well but I'm pretty sure that one still has the same bug (semi-related: https://github.com/expo/expo/issues/31747).

Came here to look if there's an existing bug for my scroll position on the following feed always resetting when I back out of a post then hit forward because I missed some detail in it, only to be scrolled to the top in the following feed when going back again... seems this is exactly it.
(Can't comment on the React side of things; I'm using Vue for development, but that got it's own share of navigation... "eccentricies"...)

Yeah that's definitely a known bug.


Woocommerce Inyegration

What is the motivation for adding / enhancing this feature?

What are the acceptance criteria

[ ] ...

Can you complete this feature request by yourself?

[ ] YES
[ No ] NO

Which Release Cycle state this refers to? Info for developer.
Pick one option.

[x] This is a normal feature request. This should be available on https://test.storefrontcloud.io and then after tests this can be added to next Vue Storefront version. In this case Developer should create branch from develop branch and create Pull Request 2. Feature / Improvement back to develop.
[ ] (Pick this option only if you're sure) This is an important improvement request for current Release Candidate version on https://next.storefrontcloud.io and should be placed in next RC version. In this case Developer should create branch from release branch and create Pull Request 3. Stabilisation fix back to release.
[ ] (Pick this option only if you're sure) This is a critical improvement request for current Stable version on https://demo.storefrontcloud.io and should be placed in next stable version. In this case Developer should create branch from hotfix or master branch and create Pull Request 4. Hotfix back to hotfix.

Additional information

Hi There! We do have a PoC of the integration: https://github.com/DivanteLtd/woocommerce2vuestorefront. However it's not actively maintained and no further works are planned


Backend based on syntax

I expected ALE respects vim syntax variable, but it seems it using only filetype instead. E.g. I have file with suffix "lst" and modeline # vi:syntax=conf and ALE tries to lint it as an asm file.

If you look at the documentation of :h 'syntax, it's more complex than just the filetype (even though it defaults to filetype). I'd suggest just using filetype instead and only using the syntax option when it becomes necessary (for example, loading multiple syntax rules).

@RyanSquared, sounds reasonable.


AKS creation Scale tab has been changed

Scale tab is replaced by Node pools tab, and they look a little different.
There is an Enable virtual nodes checkbox instead of the Virtual nodes switch.

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

ID: 183d8705-0563-9944-d779-774c8b828c39
Version Independent ID: 4e2f06e8-d918-b6fd-93c8-2fadf1bd31ed
Content: Create virtual nodes using the portal in Azure Kubernetes Services (AKS) - Azure Kubernetes Service
Content Source: articles/aks/virtual-nodes-portal.md
Service: container-service
GitHub Login: @mlearned
Microsoft Alias: mlearned

Thanks for the issue @felixtsem5 ,
I've assigned this issue to the author to take a look.

Thank you @felixtsem5 for the feedback.
The article has been updated to address your feedback.
#please-close


Cannot compile the project

Hi,
I have just cloned the project, went inside and ran the command from README:
cargo build --release

I get this:
error[E0642]: patterns aren't allowed in methods without bodies
   --> /home/radu/.cargo/registry/src/github.com-1ecc6299db9ec823/rustc-serialize-0.3.16/src/serialize.rs:145:45
    |
145 |                                             &f_name: &str,
    |                                             ^^^^^^^

My rust version:
rustc 1.27.1 (5f2b325f6 2018-07-07)

All good now


Unexpected Connection Failure. 0 android ripple emulator

When I debug the ToDoList_Cordova project on ripple (Nexus Galaxy) android emulator the browser with the emulator starts, the "device" is loaded and the landing page is shown except the items that came from Azure Mobile Services (the todolist table items), giving the error: "Unexpected Connection Failure".
First I supposed that the mobile services references are wrong but the strange thing is that the very same project debuged to Andoird Emulator works fine!!! So the thesis of wrong services references falls.
Does anybody has the same problem!?!

Having the same issue.


aws_health_event - no results

Describe the bug
aws_health_event - result is empty , but in aws console there are events planned and historical
Steampipe version (steampipe -v)
Steampipe v0.24.2
To reproduce
steampipe query " select * from aws_health_event ; "
returns empty
Expected behavior
expecting to see some results
Additional context
no additional info

Hi @weinerk, apologies for the snag!!
Could you please confirm if you are seeing the same issue with the latest plugin (v1.2.0) and the latest Steampipe CLI version (v1.0.1)?

Hello @weinerk ,
We haven’t received a response in a while, so we’re going to close this issue for now. If this is still a concern or if you have additional details to share, please don’t hesitate to reopen the issue, and we’ll be happy to assist you further.
Thank you for your understanding, and we appreciate your contributions!!


Wrong arrows direction on Processes tabs

Hi,
I think the arrows (little triangles) on User Processes section (like in attachment: green is like it should be (from System Monitor), red is wrong direction) should be the opposite way.
When sorting is set from highest to lowest, the triangle should point down and for lowest to highest, should be pointing up.

Hi,
Thanks for pointing it out. It will be fixed next release.

This has been fixed in the latest release.


Class 'Backpack\Generators\GeneratorsServiceProvider' not found

Bug report
Class 'Backpack\Generators\GeneratorsServiceProvider' not found
What I did:
Create a console command and downgrade php from 7.4 to 7.3 and executed the command in dockerfile
What I expected to happen:
The command would work
What happened:
it's error, Class 'Backpack\Generators\GeneratorsServiceProvider' not found in Application.php line 745
What I've already tried to fix it:
execute composer install and composer update
Backpack, Laravel, PHP, DB version:
4.1, 8.12, mysql 5.7

Hi @muflihfq, sorry for the delay, can you please tell us if you still have this issue?
Can you tell how to reproduce this?
You said you tried to execute the command in a docker file, is this issue only happening in docker?
Is it possible that docker is running on production mode, installing production dependencies only and since Backpack\Generators is installed on dev it is not being installed on your docker?

@muflihfq I'll close this one for now, I believe your issue was exactly the missing of the package in production.
If it's not, please reopen 👌


Telegraf config bug

"Copy to Clipboard" seems to be missing under step 2. It shows up for Samantha, but not on mine.

@caitlincroft do you happen to have any additional information regarding this bug? Which OS are you using? Which browser? I can't seem to recreate it locally

MacOS Mojave 10.14.6

@caitlincroft sorry for the delay on this. I can't seem to reproduce this bug - can you let me know if it's still an issue for you before closing this out?


To Compress or Not to Compress?

When deploying a website, we have to upload quite a few files. Should we compress the files, upload them, and uncompress them? Or simply upload them all uncompressed? Things to consider are both speed and size. It needs to be fast, but it also needs to be small to keep down the bandwidth usage.
Options

Compress
Upload All Without Compression

With async, we can concurrently upload files making that faster than compressing, uploading, and then decompressing again.


Stablize cylindrical chunks

Description
To find different chunks we would iterate over the entire rectangular area the chunks covered. This fixes that.
Fixes https://github.com/Snowiiii/Pumpkin/issues/379 and some edges cases where chunks are not removed from memory

Testing
Teleported far out and did not time out

Checklist
Things need to be done before this Pull Request can be merged.

[x] Code is well-formatted and adheres to project style guidelines: cargo fmt
[x] Code does not produce any clippy warnings: cargo clippy
[x] All unit tests pass: cargo test

LGTM.
Thanks @kralverde :+1:


Add accelerated networking and availability zones to RKE2/K3s machine pools

Addresses https://github.com/rancher/dashboard/issues/7182 and https://github.com/rancher/dashboard/issues/7180
Combining the two options into one PR to avoid merge conflicts
What was fixed, or what changes have occurred
Summary:

Added  accelerated networking (AN) to Azure node options in the Advanced section for RKE2/K3s cluster provisioning
Added an Availability Zone option for Azure nodes

You can have an Availability Set or Availability Zone, but not both
The Availability Zone dropdown menu may or may not have any options, depending on the selected region. For example, if you select westus as the location, the Availability Zone dropdown should be disabled and you should see a warning because that region doesn't support AZs. If you select westus2 as the location, the Availability Zone dropdown should have 1, 2 and 3 as options.

Accelerated Networking

When AN is enabled, the list of VM sizes should show that the VM sizes that don't support it are disabled.
When AN is enabled, the VM size dropdown should have a tooltip explaining why some options are disabled.
If you have AN disabled, then select a VM that does not support AN (such as BasicA0), then try enable AN, you should see an error that says the VM size is incompatible with AN. A warning also shows next to the VM size dropdown. The warning goes away if any other non-disabled VM is selected or if AN is turned off.

Availability Zones

Can select an AZ for a machine pool
Warn the user when the selected VM size is not in the selected region
Warn the user if they have selected availability zones, but that is not supported for the region or VM size

@mantis-toboggan-md This is ready for review since it's going to be in the next medium sized release after all. Note: The accelerated networking boolean is only expected to be persisted in today's version of v2.7-head due to a backend change today

Previously I had misunderstood - I thought this PR needed to use the original endpoint for VM sizes, but it needed to use V2. Sorry for the confusion on my part. I've updated it to use the V2 endpoint tested it locally using the latest 2.7-head. I believe it's working now.

I've updated it based on your comments and made a couple more small fixes as well. The VM size no longer disappears from the dropdown menu if the region is switched to a region where that size does not exist. And when the region is switched, a loading spinner shows instead of the VM size list while it is being fetched.