Consider latest released images for "dependency" images

When Freshmaker has to rebuild parent images that are not directly affected, it now detects if it can use the latest released image at the pull specification declared by the child image. If it can, this parent image is used instead of rebuilding the original parent image.
Resolves CLOUDWF-541

@lcarva @qixiang @gnaponie @apaplaus I refactored the PR to only consider the latest release of the same name and version after discussing this with Luiz. He had pointed out that using the pullspec of the parent image from the perspective of the child image is likely too aggressive. This is because maintainers may be more conservative when doing auto-rebuilds since there is more testing during a normal product release.

One minor comment, beside of that, it looks good to me.


Improve upfront deal workflow

Right now the contract workflow works for every edge case but it is not optimized for some common use cases. This is really bad for mainnet deals when gas is expensive. we have seen some users unhappy with the transaction costs even when they are necessary for a given pool

if there is no deallocation allowed and no purchase raise minimum but there is a vesting schedule we should be able to skip the settle transaction
if there is no deallocation allowed and no purchase raise minimum and there is also no vesting period, we can just exchange the tokens directly when they send the funds in. no need for settling or claiming.
if deallocation is allowed but there is no vesting period, we can exchange the tokens when settle is called

NOTE this will seriously impact the tests which is likely the majority of the work for this ticket. We will need more tests as well


-added a test to check the error from the issue 1820

…happen.

What kind of change does this PR introduce? (check at least one)

[ ] Bugfix
[ ] Feature
[ ] Code style update
[ ] Refactor
[ ] Build-related changes
[ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

[ ] Yes
[ ] No

If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:

[ ] It's submitted to the dev branch.
[ ] When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)
[ ] All tests are passing: https://github.com/vuejs/vue-test-utils/blob/dev/.github/CONTRIBUTING.md#development-setup
[ ] New/updated tests are included

If adding a new feature, the PR's description includes:

[ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

Thanks, I'll look at this today!

@lmiller1990 ok I added the extra check.

@lmiller1990  Dude I am in despair... I can't understand why the karma test are failing and the jest test not. They are almost the same test case. I really really have no idea.

The only test failing is the one using the router. This PR makes a change that specifically adds a check against RouterView on this line. I guess we broke something?
I will try taking a look at this on the weekend. I'd suspect if you comment out that check, the Karma tests will pass. That's the first thing I'm going to do - figure out if this failure is due to a change we made, or not.


CON-2490 input field are not in viewport

Coverage decreased (-0.001%) to 1.71% when pulling 639c1c064483c500efaf85746c09253c19cef362 on CON-2490-Input-field-are-not-in-viewport into 3ac69a28d42b9d5f64c271ac2277ba6675312600 on master.


Template error for docs

Going here http://localhost:8080/details/security yields this error:
template: check-details:18:33: executing "head" at <.JSON>: can't evaluate field JSON in type *dashboard.TemplateData
Version 0.1.3.

Hey @towolf, thanks for reporting this! It should be fixed in our latest release (0.1.4).


sdk endpoint and version

adding some settings on endpoint and updating the sdk for the current version

sorry but this PR will generates new issues
http://stackoverflow.com/questions/10415884/fb-init-has-already-been-called


[fix] gws schedule some issues

Coverage remained the same at 0.0% when pulling e6f2d15af27bf44aaa560a8a5015034b89c37887 on fix-gws-schedule into d51dd30f467d5d3aa1a012a14ee7798f55de1797 on master.


How to hook into errors when using .load()

When initializing analytics with,
const analytics = AnalyticsBrowser.load({ writeKey: '<YOUR_WRITE_KEY>' })

What happens if the loading fails? and how can we hook into that event so as to, for example, log the error?

@aryzing
Our recently introduced lazy loading API is the right way to do this!
import { AnalyticsBrowser } from "@segment/analytics-next";

export const analytics = new AnalyticsBrowser();

analytics.catch((err) => console.error("My Error", err));

// load analytics lazily
analytics.load({ writeKey: "MY_WRITE_KEY" });


don't use then to trigger querys

it prevents to be result of a promise since it's than evaluated.
by @rhys-vdw

fixed


Deprecated TIMESTAMP_MILLIS Parquet type is interpreted incorrectly

Describe the bug
I live in a painful world of ensuring three different SQL engines (Spark, Flink, Datafusion) interoperate via Parquet.
Spark is far behind on keeping up with Parquet spec. We configure it to write TIMESTAMP type as TIMESTAMP_MILLIS logical type, instead of the long-deprecated int96 it uses by default ... but TIMESTAMP_MILLIS is also deprecated in favor of TIMESTAMP(precision, isAdjustedToUtc).
Parquet spec prescribes that for backward compatibility TIMESTAMP_MILLIS should be interpreted as TimestampType (isAdjustedToUTC = true, unit = MILLIS), but this doesn't seem like what Datafusion is doing.
To Reproduce
Read a modern Parquet file with schema:
message x {
  REQUIRED INT64 system_time (TIMESTAMP(MILLIS,true));
}

observe field:
Field { name: "system_time", data_type: Timestamp(Millisecond, Some("UTC")), nullable: false, dict_id: 0, dict_is_ordered: false, metadata: {} }
Read an old Parquet file with schema:
message x {
  REQUIRED INT64 system_time (TIMESTAMP_MILLIS);
}

observe data frame field:
Field { name: "system_time", data_type: Timestamp(Millisecond, None), nullable: false, dict_id: 0, dict_is_ordered: false, metadata: {} }
TIMESTAMP_MILLIS gets incorrectly interpreted as naive/local timestamp.
Expected behavior
Because spec prescribes that TIMESTAMP_MILLIS should be interpreted as TIMESTAMP(MILLIS,true) I expected to see a timestamp with UTC timezone.
Additional context
No response

I traced this issue to the internals of parquet crate - will close and re-file in that repo.

Re-filed as https://github.com/apache/arrow-rs/issues/4308


Implement is_one and Inv for Complex.

Requires a new version of num-traits to be pushed.

This should be good with a bump to num-traits 0.2.1.

Should be working now

I repeat, now it should be working.

Thanks!
bors r+


popover background

is there an option for setting the background of popover?
i use it in my vue app,but i find out that i can only modify driver.css to change the background of popover.
thx.

Yes, there is stageBackground. Please have a look at the "API" section in readme


Add starter projects section, typescript-starter

(Also corrects the capitalization of a few headings to match the rest.)

good! thank you @bitjson !


Tests setup

Updates

travis config: Use new architecture with sudo: false
travis config: Add go 1.5 to build matrix
Update Makefile

make deps – builds dependencies
make alldeps – builds dependencies of package and tests
make updatedeps – will install package dependencies with update flag
make test – Runs tests with go vet
make ci – Runs tests for ci environment
make bench – Runs benchmark tests

Add badges to README

Vet issues

fixed: examples/appengine/hello.go:31: unreachable code

fixed: possible formatting directive in log call

Issues with tip version of golang
bugsnag_test.go:341: ExampleAutoNotify should return nothing
bugsnag_test.go:349: ExampleRecover should be niladic
bugsnag_test.go:407: ExampleNotify_details should be niladic
errors/error_test.go:78: ExampleErrorf should be niladic
errors/error_test.go:78: ExampleErrorf should return nothing
errors/error_test.go:85: ExampleNewError should return nothing
errors/error_test.go:85: ExampleNewError refers to unknown identifier: NewError
errors/error_test.go:90: ExampleNewError_skip refers to unknown identifier: NewError
errors/error_test.go:99: ExampleError_Stack should be niladic

I ran the example apps suite manually, everything looks good here. :+1:


Using ‘python3 setup.py test’ fails.

It does seem the ‘experiments’ folder is missing to execute:
running egg_info
writing pls.egg-info/PKG-INFO
writing dependency_links to pls.egg-info/dependency_links.txt
writing requirements to pls.egg-info/requires.txt
writing top-level names to pls.egg-info/top_level.txt
reading manifest file 'pls.egg-info/SOURCES.txt'
writing manifest file 'pls.egg-info/SOURCES.txt'
running build_ext
stars1
error: [Errno 2] No such file or directory: ‘~/PycharmProjects/pls/pls/workflows/../../experiments/stars/small0/PPO/seed1'

Maybe ‘Stars’ dependency is missing...

@GiuseppeMarra @wenchiyang Somehow the ‘experiments’ folder is missing in the repo. Please help! Thanks in advance.

Dear drags, thanks for your message. I just have made things runnable. Can you pull and try it out?

Dear Wen Chi, it required exactly the version 1.9.0 of pytorch, that I don’t have available. I guess something could be improved to work with the last update of pytorch…
Sorry for asking too much, but maybe it’s just a config matter…
Thanks in advance

The latest version of PyTorch might actually work! You can change it in setup.py and pip install again. I specify the exact versions for now because I don't have time yet to check if the latest versions of the dependencies work.

No Problem. Thanks for the info!
—
Andrés García-Camino
@.***

El 18 gen. 2024, a les 10:59, wenchiyang @.***> va escriure:
The latest version of PyTorch might actually work! You can change it in setup.py and pip install again. I specify the exact versions for now because I don't have time yet to check if the latest versions of the dependencies work.
—
Reply to this email directly, view it on GitHub https://github.com/wenchiyang/pls/issues/2#issuecomment-1898157944, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANS7YY7YINYZFKIGBY2EU43YPDXAVAVCNFSM6AAAAABBYDG7YCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJYGE2TOOJUGQ.
You are receiving this because you authored the thread.

Dear dragc, could you please resolve this problem? Thank you.


Could not get RemoteStartTransaction working

Hi, i have tried to start a remote transaction on this simulator, but it seems to not work or not be implemented,
i tried to send this message to the simulator,
[2,1524699488,"RemoteStartTransaction",{"idTag":"free-tag","connectorId":1}]
but it does not start the transaction when the CP is in Preparing or Available states.
This is the log that is dumped to the console when the CP receives the package:
Date time received : 2023-12-09T17:43:48Z
[  COM  ] - [2023-12-09T17:43:49] - ChargePoint.cpp:979 - RX : [2,1524699488,"RemoteStartTransaction",{"idTag":"free-tag","connectorId":1}]
[  COM  ] - [2023-12-09T17:43:49] - ChargePoint.cpp:986 - TX : [4, "", "ProtocolError", "", {}]

Note that the simulator works fine for authorizing with tags, but remote start seems to not be working, any tips?
Thanks!

Hi,
The simulator implements the RemoteStart/Stop requests.
It seems that the format of your request is not valid : the unique id in the RPC frame must be a string. Here it as a raw integer :<PHONE_NUMBER>.
The correct frame should be :
[2,"1524699488","RemoteStartTransaction",{"idTag":"free-tag","connectorId":1}]
Regards

You are correct, i wasn't aware of this, thanks alot!


Feature Request

Hello,
I am not sure if I am doing this in the right place but I figured I would give it a try. I was hoping to get a -y switch so that you specify yes you want to do the action. i.e. drive pull -y random_folder.
Regards,
Austin

Hello @viruscmd thank you for reporting this and welcome to drive.
So drive already has this with the option --no-prompt e.g
$ drive pull --no-prompt random_folder

In case you'd like an external command, like @CountryBumkin taught me in  https://github.com/odeke-em/drive/issues/125#issuecomment-86729928, you can do
$ yes | drive pull random_folder

Thanks I don't know how I missed that, I only spent twenty minutes looking at the help!

Cheers!


865 the hook needs to contain similar kwargs as the google providers

I have added the location parameter in the hook. I do think this needs to get upgraded to integrate the use_legacy_sql parameter, as well, but that change may not be so simple given it could change the requirements.txt.

rebase once the PR gets merged https://github.com/astronomer/astronomer-providers/pull/867
and mypy issue should be resolved

FYI: Look like google async lib have some issue with no us location https://github.com/apache/airflow/issues/29307

One of the errors, currently, is a permission issue. It would make sense that it's a region issue, but I haven't verified for sure, since it's not my service-account.
We should include this and just update the docs to reflect a possible issue with non-US locations.

Can we fix the failing tests as well.

I've gone ahead and removed the use_legacy_sql kwarg from this PR since it was failing the tests. I think it's best to open another issue for this, as the current issue with the location kwarg is breaking a DAG for a customer. I will open a new, much more broad issue for update the bigquery.py file to meet the current kwargs of the provider package.

Can you rebase the branch? There is mypy issues also


generate-diagnostics collision handling chokes if two or more collisions are markde "fixed"

The problem:
If handleCollisions finds two collisions that are both marked "fixed" (in the isFixed array), it silently allows both names to escape unaltered and leaving the collisions intact:
        for (var i = 0; i < collisionIndices.length; i++) {
            var collisionIndex = collisionIndices[i];

            if (isFixed[collisionIndex]) {
                // can't do anything about this name.
                continue;
            }

The code for handling isFixed and isCaseSensitive is dead code, so there's no way to trigger this problem, even with alternative input.  All names are treated as if they're not fixed, so it's completely unused.  Even so, we go through some effort to generate an n-sized array for the isFixed part:
        if (!isFixed) {
            isFixed = names.map(() => false)
        }

It seems like these snippets may have been copied and pasted (or cross-language ported) from another project.
Proposed solution:
Remove the isFixed-handling from processDiagnosticsMessages.ts altogether.  This would obviate the problem.  We could do the same with isCaseSensitive while we're at it.

Any improvements to this tool are welcome :smiley:

@CyrusNajmabadi might have some input regarding this; I remember there was some unused code which we determined that we might be using down the line.

These functions are useful, and i intend for them to be used when we start implementing things like "generateFunction/Method".
They were copied from the Roslyn codebase, and provide the same semantics.

If handleCollisions finds two collisions that are both marked "fixed" (in the isFixed array), it silently allows both names to escape unaltered and leaving the collisions intact:

Yes.  This is a feature.  The purpose of 'isFixed' is for the client to state explicitly that these names are correct and that they should not be affected.  However, the names should still be in the list of input as any collisions with non-fixed versions should cause the non-fixed name to be changed.

In light of the previous comment, this should be marked WONTFIX and closed, instead of "Accepting PRs", no?

yup. thanks.


Consider TLS support?

This project looks very interesting; I'm writing a CLI app that needs to serve one single request (for OAuth), and in principle I'd like to avoid having to spin up Tokio and go full async just for that, and Astra fits the bill. But of course I must have TLS, and whereas for a normal server I'd just use a reverse proxy I can't do that here. Would you be willing to offer built-in TLS?

It wouldn't hurt to put it behind a feature flag, and would make this project more useful, hopefully increasing number of people that can help maintain it.

The other option that was suggested is driving the hyper connections asynchronously, and only running user code on the blocking pool. That way we can offer TLS while avoiding the need for a reverse proxy (as it's essentially built-in).

Oh. Right I keep forgetting that astra is only using hyper logic, but actually doesn't run the executor at all (IIUC).
There seem to be 3 separate things here:

using hyper as a mature and well supported http stack (or not, going with something custom like tiny_http)
actually using async executor to achieve good network scalability
not having users suffer writting async code.

Right now the difference between tiny_http and astra seems to be mostly about custom http vs hyper. Other than this both are not driving async executor and downstream user doesn't write async code.
If astra was to drive its own executor it would be "as good as async frameworks, but without having to write async code". The price, I guess would be some extra bloat... I mean code, that it would probably pull from tokio, which is already a dependency anyway through hyper.
If I was a person that very much cares about minimal dependencies and "trust base", I would probably already go with tiny_http, because of that hyper + tokio "bloat".
In comparison:
~/git/tiny-http(master)$ cargo tree
tiny_http v0.12.0 (/home/casatta/git/tiny-http)
├── ascii v1.1.0
├── chunked_transfer v1.4.1
├── httpdate v1.0.3
└── log v0.4.20

The tokio_http mostly misses a framework around it that would have a better DX. Otherwise it seems in a way like "better astra than astra". hyper vs custom http handling code ... seems like a minor detail, especially if you're going minimal anyway.
If astra was to run the executor it could become "don't sacrifice almost any benefit of async IO, without having to deal with any of its problems". Which is appealing to me at least.

Actually, after looking a bit more into how the polling is handled (mio), maybe what astra is doing currently is perfectly sufficient.
BTW. Isn't Slowloris conquered by just having a total timeout on each connection, proportional to the size of the response? If peer is unable to consume the response on time, well sucks to be them.
The whole thing could also be dynamically adjusted. Timeouts would get more aggressive as the number of workers in use increases. If it's just a handfull of connections done by dialup model, fine, the server can keep sending things slowly. But if it looks like we're running short on resources, too bad, it might be an attack.

Slowloris attacks can also be performed by sending in a large number of partial requests, slowly sending in the headers, or the body. Hyper doesn't currently expose many internal timeout settings, but we can at least set read/write timeouts, and a http1 header timeout.

It would also be useful to expose a rate-limiting API that buffers requests before pushing it to the threadpool.


[Clipboard] getData implementation added

[Before] Clipboard.getData feature was not implemented
[After] Dart code below is able to gather system clipboard data:
      Future<ClipboardData?> d = Clipboard.getData(Clipboard.kTextPlain);
      void dataCallback(ClipboardData? d) {
        if (d != null) {
          String? text = d.text;
          if(text != null) {
            print("Clipboard data $text");
          }
        }
      }
      d.then(dataCallback);

[TODO] Need to consider adding some mechanism of synchronization of access to native cbhm API
to provide proper behaviour in case of multiple calls
Change related to PlatformChannel Clipboard.getData() part of https://github.sec.samsung.net/f-project/home/issues/35
https://github.sec.samsung.net/f-project/home/issues/35
Necessary dependency was added to tizen_tools with PR flutter-tizen/tizen_tools#8

Necessary dependency was added to tizen_tools with PR https://github.com/flutter-tizen/tizen_tools/pull/8

The CI build failed. Where can we find the cbhm.h header?

Sorry. I was not aware of the tizen_tools PR!

Tip: If you're using VS Code you can easily format your code by applying the following.

Enable "Format on Save" in the settings
Install the "C/C++" extension
Add "C_Cpp.clang_format_fallbackStyle": "Google" to the workspace settings

Thank you for your contribution!
As far as I can see the CBHM API is mobile-only, so probably the embedder with this change will not even load on non-mobile devices (e.g. watch) because libcbhm will not exist on those devices. I'm currently thinking about how to release different embedders for different profiles (mobile/wearable/tv/iot) and integrate with the flutter-tizen tool. The design is not fixed yet but it will use compiler switches like #ifdef TV_PROFILE. You will have to wait a while until it is implemented for your change to be merged. Otherwise you can suggest any other ways to deal with the problem!

Now #67 has been merged and you can guard any code that is for mobile only using #ifdef MOBILE_PROFILE or #if defined(MOBILE_PROFILE). Also you will have to change BUILD.gn as follows:
diff --git a/shell/platform/tizen/BUILD.gn b/shell/platform/tizen/BUILD.gn
index 1ea9bcf30..bb9837748 100644
--- a/shell/platform/tizen/BUILD.gn
+++ b/shell/platform/tizen/BUILD.gn
@@ -38,6 +38,7 @@ config("tizen_rootstrap_include_dirs") {
     "$custom_sysroot/usr/include",
     "$custom_sysroot/usr/include/appfw",
     "$custom_sysroot/usr/include/base",
+    "$custom_sysroot/usr/include/cbhm",
     "$custom_sysroot/usr/include/dlog",
     "$custom_sysroot/usr/include/ecore-1",
     "$custom_sysroot/usr/include/ecore-evas-1",
@@ -141,6 +142,10 @@ template("embedder_for_profile") {
       libs += [ "ecore_wl2" ]
     }

+    if (target_name == "mobile") {
+      libs += [ "cbhm" ]
+    }
+
     cflags_cc = [
       "-Wno-newline-eof",
       "-Wno-macro-redefined",

Unfortunately, implementation using public CBHM API has issue which disqualifies it as stable copy/paste support even on mobile only. In case of Flutter application using simple TextField in its UI:
TextField(
              decoration: InputDecoration(
                border: OutlineInputBorder(),
                hintText: 'Enter a search term',
              ),
            ),

, framework automatically calls Clipboard.getData() method during first run of application. According to my analysis and testing, in such case native API (cbhm_selection_get) does not trigger success callback (cbhm_selection_data_cb), nor return any error. Because current implementation is based on mutexes to protect accessing from different threads, this scenario causes a deadlock-like API state which always return error "Already processing in other thread" (because is_processing flag was not released in callback).  I've tried to workaround this problem, but my all ideas were very ugly hacks which also does not guarantee memory safety and proper API behaviours in all cases.
Because of above issue of native API, I think that it is better to not include this PR to final code.

I've prepared much simpler implementation https://github.com/flutter-tizen/engine/pull/76 which uses naive in-application clipboard. Please share your opinion.


scm-leader-transfer.robot not part of any acceptance test

What changes were proposed in this pull request?
(Please fill in changes proposed in this fix)
What is the link to the Apache JIRA
(Please create an issue in ASF JIRA before opening a pull request,
and you need to set the title of the pull request which starts with
the corresponding JIRA issue number. (e.g. HDDS-XXXX. Fix a typo in YYY.)
Please replace this section with the link to the Apache JIRA)
How was this patch tested?
(Please explain how this patch was tested. Ex: unit tests, manual tests)
(If this patch involves UI changes, please attach a screen-shot; otherwise, remove this)

@LZD-PratyushBhatt may I ask why you open PRs in your own fork?  CI checks are run for both push and pull_request events:
https://github.com/LZD-PratyushBhatt/ozone/actions/runs/6516926555 (push)
https://github.com/LZD-PratyushBhatt/ozone/actions/runs/6516933130 (PR)
I think the latter is not necessary.
Similarly, the same commit on multiple branches results in duplicate runs:
https://github.com/LZD-PratyushBhatt/ozone/actions/runs/6516931898 (push, same commit to another branch)
Workflows are resource-intensive, so it's better to minimize them.
(PRs against own fork are useful when you want to test CI workflow logic.)

Hi @adoroszlai , I guess non-committers dont have access to start the CI on the main repo, so I use this repo to create a PR internally and then check.

non-committers dont have access to start the CI on the main repo, so I use this repo to create a PR internally and then check.

My point is that you don't need to create a PR in your fork to trigger CI.  It is already triggered when you push to your fork.  Check https://github.com/LZD-PratyushBhatt/ozone/actions/workflows/post-commit.yml to confirm.


Broken links to v1.25 docs

This is a Bug Report

Problem:
https://v1-22.docs.kubernetes.io/docs/home/supported-doc-versions/
https://v1-23.docs.kubernetes.io/docs/home/supported-doc-versions/
https://v1-24.docs.kubernetes.io/docs/home/supported-doc-versions/
each have a link to the docs for Kubernetes v1.25; however, those links are broken.
This error was introduced as part of the v1.26 release.
Pages to Update:
https://v1-22.docs.kubernetes.io/docs/home/supported-doc-versions/
https://v1-23.docs.kubernetes.io/docs/home/supported-doc-versions/
https://v1-24.docs.kubernetes.io/docs/home/supported-doc-versions/
(however, the problem is in config.toml for the branches release-1.22, release-1.23 and release-1.24. I think that the Markdown in the supported doc versions page itself is fine.)
Additional Information:
/language en
/kind bug
/priority backlog
/triage accepted

The link in 1.22 doc: working

It goes to https://v1-25.docs.kubernetes.io/docs/home/supported-doc-versions/

The link in 1.22 doc: not working

it goes to https://v1-25.kubernetes.io/docs/home/supported-doc-versions/

The link in 1.24 doc: not working

it goes to https://v1-25.kubernetes.io/docs/home/supported-doc-versions/

For anyone that wants to work on this:
please notice the slight difference among those links.

Looks fixed
/close


Issue with log file cursor under Rails (and others?)

I'm seeing a constant problem with Foreman (sample app), where something in the background (classic case is Resque workers) which write to the Rails log cause on the first HTTP request, all log lines written to the file to be streamed via Foreman to the terminal.
This in itself isn't a /huge/ problem, except from the time it can take to catch up on millions of lines of logs, but that it also causes under iTerm2 (and others, I'm sure), broken escape codes, which in some cases put the terminal into Klingon (or, rather high-range unicode chars) or trigger it to display the print dialog (and pause), beep, clear the screen, etc, generally strange behavior.
I'm not really sure what the solution is, I'm not even completely sure how file cursors on logs work; or what foreman is doing to start Rails ( I assume it's actually /Rails/ which displays the log trace to Foreman, when something is written to it's logs behind the scenes.
I'm posting here, because this manifest most reliably and repeatably via Foreman, and because I suspect in a small project we'll be  able to have a more constructive discussion before taking it upstream to Rails.
Steps to reproduce:

Get the sample application
Start foreman
In another tab/term/panel: rails runner '1_000.times { |n| Widget.create!(:name => "Widget #{n}")}'
(observe nothing visible via the foreman output / logs)
open http://<IP_ADDRESS>:5000/widgets
Observe ~1000 log lines screaming past
Randomly, observe iTerm2's output breaking/etc

The same error is present in Rails, when using rails server; so this isn't exclusive to Foreman (and having written this ticket, and made the sample-app, I'm inclined to think I should have gone directly to rails/rails!)
I've mentioned iTerm2 a couple of times here; the issue being tracked upstream was [http://code.google.com/p/iterm2/issues/detail?id=352], in spite of the title of the ticket, please skim the comments, in the end log output displayed via Forman was show to have gotten out of sync, somehow, and escape codes, and parts of words, and colors were interleaved in the output, resulting in the erroneous codes.

Foreman will display to the terminal output anything written to stdout by the processes it launches.
The broken escape codes may be from the buffer getting read across an escape code boundary which causes part of the escape code to be on two different lines with the foreman header in between. I'll have to look into this and see how I can fix it. Patches definitely welcome if you want to take a shot at it as well.

@ddollar thanks for getting back to me about this, eventually iTerm2 included an "ignore session initiated printing" option, which cured my problem.
I think the further problem is with the Rails log file cursor, same steps to reproduce, and you see a lot of Rails streaming the log, even if it was from another process (that is rails runner vs. script server) - do you think that should be considered a bug? (That it catches-up the log on the next web request?)

foreman is not actually tailing the log, it's just displaying whatever rails displays on stdout so there's probably not much I can do

Resolving ancient bugs. Please reopen if this is still an issue.

It still happens, but I'm pretty sure it's something to do with Rails chasing the log's EOF on the next web request; which is annoying. I don't think I ever remembered to open the bug upstream with Rails. If/when I do, I'll drop a link here. Cheers.

Update here, I just watched Railscats #391 (pro) and noticed something interesting, Rails only flushes writes to the logfile when the next rack request is finishing, it's handled by the Rails::Rack::Logger middleware.
So the workaround for anyone else suffering is to set the log to autoflush on any background jobs. such as Resque workers/etc, and/or open an issue with Rails and share your feeling that middleware isn't an appropriate place to be flushing logfiles.


Read quay.io organization names from secrets

2 commits:

Read quay organization names from secrets instead of assuming that they are the same as the cilium github repo name.
Don't push to "-ci" repos from release / beta image workflows. CI image workflow already pushes to these repos with the same tags.

yeah sorry just realized my amazing sed commands didn't quite work as expected. updated the PR ✅

moving to draft. https://github.com/cilium/cilium/runs/8082527493?check_suite_focus=true is a legitimate failure 😿

/test

Did we set up QUAY_ORGANIZATION_DEV for cilium/cilium? Seeing GH actions fail in Wait for images to be available, as we now read from quay.io//cilium-ci:$tag instead of quay.io/cilium/cilium-ci:$tag.

i'm reverting the change https://github.com/cilium/cilium/pull/21153 😿 i'll come up with a better way to deal with this


postsubmits failing on istio webhook scripts not found

Error started within the last few days, potentially during release.
snippet
sh: 1: /home/bootstrap/go/src/istio.io/istio/install/kubernetes/webhook-create-signed-cert.sh: not found

prow example failure

The script was removed in https://github.com/istio/istio/pull/4612
@yusuoh was this replaced somewhere else in helm?

we may need to update https://github.com/istio/istio.github.io/pull/1132 too if this is changed

@cmluciano regarding https://github.com/istio/istio.github.io/pull/1132, 0.7 of the docs repo has not branched, so the patch is valid for 0.6/0.7.  @yusuoh 's work only applies to master as istio/istio branched several weeks ago, IIUC.
It will need to change for 0.8 I suspect.
Cheers
-steve

@linsun Yes. #4667 should fix this issue.


[Feature request] Support setting/getting colors from widgets in AppBar

Platforms
Android, iOS, Web
Description
It's possible to customize the color widget already (https://github.com/hm21/pro_image_editor/issues/70), but I'm wondering if there's a way to support setting and getting the current foreground and background colors for use in the AppBar widgets (like an icon for example).
Unlike the other text styles, it doesn't seem to work if getting and setting the text style from the AppBar.
Why
I'm trying to include all editing features in the top AppBar vs using buttons on the editor area or at the bottom bar.

I'm not sure if I understand you correctly, but you just want to change the color as an example to red, right? If so, you can do it in “configs/imageEditorTheme/nameFromEditor/appBarBackgroundColor”. A full example of how to change the theme can you checkout here.
I also released now version 4.0.0 which brings you more custom widgets which also allow you to directly access the current editor state in case you need to get/set something there.

@hm21 - sorry I didn't explain very well.
This is what I currently have:
https://github.com/hm21/pro_image_editor/assets/869261/83879c29-5172-40d4-a6e1-7f0dd86b5c53
What I would like to do is move the color selector I have into the AppBar and also add another color selector for the background color as well.
I tried before and the AppBar was unable to get the current color state. I'll try it with 4.0.x versions and see if I can get it working with the new system.

Not sure if I'm doing this right, but I tried using the new system and it doesn't seem to work:
StreamBuilder(
  stream: updateStream,
  builder: (context, snapshot) {
    return IconButton(
      icon: Icon(Icons.color_lens_outlined,
          color: textEditor.selectedTextStyle.color),
      onPressed: () {
        textEditor.setTextStyle(
          textEditor.selectedTextStyle.copyWith(
            color: Colors.red,
          ),
        );
      },
    );
  },
),

Where I pass through textEditor and updateStream from ReactiveCustomAppbar. Although I guess I shouldn't need to use a StreamBuilder now as that's what ReactiveCustomAppbar does?
Even so, the textEditor.selectedTextStyle.color does not seem to be reactive where as bold/underline does seem to be.

@hm21 just tagging you in case you missed this as it's a closed issue

Ah, my bad, I already closed this topic. I'm not sure what I set in the settings, but you can also reopen the issue, right? I will reopen the issue now, but feel free to reopen it in the post if your issue/future request is not resolved ;)
Anyway, I will take a closer look at your posts later when I find the time and answer you then.

No probs. I don't think I had permission to re-open :)

Ah, I got it. The main problem is that you update the color from the text style. The problem is because the user can change the background mode where the color can also be used as background color and not text color, we cannot set it that way. In the texteditor you will find the parameter primaryColor which will handle the color from the text or background depending on the background mode.
Anyway, you can call now colorChanged to change the color, which should fix it.
Your code with the streambuilder should still work when you call colorChanged. However, I recommend you to use the new way, which is a bit easier, and you don't need to wrap every icon in the appbar with the streambuilder anymore.
 customWidgets: ImageEditorCustomWidgets(
    textEditor: CustomWidgetsTextEditor(
      appBar: (textEditor, rebuildStream) {
        return ReactiveCustomAppbar(
          stream: rebuildStream,
          builder: (context) {
            return AppBar(
              title: const Text('Test'),
              actions: [
                IconButton(
                  icon: Icon(Icons.color_lens_outlined,
                      color: textEditor.selectedTextStyle.color),
                  onPressed: () {
                    textEditor.colorChanged(Colors.red);
                  },
                ),
                /// Other buttons...
              ],
            );
          },
        );
      },
    ),
  )

Please let me know if it didn't work by you.

Ahh thanks, yes what I was after was, I needed to use textEditor.primaryColor to fetch the color and textEditor.colorChanged() to set the color.
Would it be possible to have matching calls for the background color as well?

textEditor.backgroundColor
textEditor.backgroundColorChanged()

The problem is, by default you have multiple background modes, which means the primary color can be the text color or text background depending on the mode. If I add an option that sets the secondaryColor, it will destroy the background mode function because now it calculates the secondary color like below:
Color getContrastColor(Color color) {
  int d = color.computeLuminance() > 0.5 ? 0 : 255;

  return Color.fromARGB(color.alpha, d, d, d);
}

Anyway, in case you don't need multiple background modes and just want to set the color for foreground and background by yourself, you can now do it like below in version 4.0.4. Keep in mind that after you set a secondary color by yourself, it will always be used and not automatically calculated from the primary color.
///  It's no longer necessary to call `colorChanged`.
textEditor.primaryColor = color;
textEditor.secondaryColor = color;

Thanks! That works perfectly. Yes I plan to allow background color selection directly and also an opacity selector as well instead of the built-in background modes.

There seems to be one more minor bug/issue with this. secondaryColor can be set and takes effect in the layer. But when coming back into the text editor, it seems to reset itself to the default color again.
A bit hard to explain, here is a video. I set the background color to blue, which works fine, but when I come back in, the secondaryColor is set back to white again.
https://github.com/hm21/pro_image_editor/assets/869261/1a9ca7db-6630-4a8b-81b0-444de100ab37

Should also be fixed in version 4.0.5, but please let me know if this issue still exists by you.

Thanks, fixed!!


primary index not created when couchbase community edition is used

Hi,
primary index is not created when community edition is used:
    @ClassRule
    public static CouchbaseContainer container = initCouchbaseContainer();

    private static CouchbaseContainer initCouchbaseContainer() {
        CouchbaseContainer couchbaseContainer = new CouchbaseContainer("couchbase/server:community-6.0.0");
        couchbaseContainer.withClusterAdmin(CLUSTER_USER, PASSWORD);

        final UserSettings communityAdminUserSettings =
                UserSettings.build()
                        .password(PASSWORD)
                        .roles(Collections.singletonList(new UserRole("admin")));

        couchbaseContainer.withNewBucket(getDefaultBucketSettings(), communityAdminUserSettings);
        couchbaseContainer.start();
        return couchbaseContainer;
    }

    protected static BucketSettings getDefaultBucketSettings() {
        return DefaultBucketSettings.builder()
                .enableFlush(true)
                .name(BUCKET_NAME)
                .password(PASSWORD)
                .quota(100)
                .replicas(0)
                .type(BucketType.COUCHBASE)
                .build();
    }

I think the problem is that community edition does not support memory_optimized storage mode (configured in CouchbaseContainer):
 callCouchbaseRestAPI("/settings/indexes", "indexerThreads=0&logLevel=info&maxRollbackPoints=5&storageMode=memory_optimized");
Only forestdb is supported:
https://docs.couchbase.com/server/6.0/rest-api/post-settings-indexes.html
It would be nice if we could configure storage mode, for example:
withStorageMode(String storageMode)

+1 For this feature. I used container.callCouchbaseRestAPI("/settings/indexes", "indexerThreads=0&logLevel=info&maxRollbackPoints=5&storageMode=forestdb"); to be able to use community edition with this library.

As suggested by @martin8877, a PR to specify a storage mode sounds like a good idea. Contributions would be welcomed!


[Monitor] az monitor diagnostic-settings create -h

(env) vishrut@visshamac azure-cli (monitor) $ az monitor diagnostic-settings create -h

Command
    az monitor diagnostic-settings create: Create or update new diagnostic settings for the
    specified resource.

Arguments
    --location -l [Required]: Location. You can configure the default location using 'az configure
                              --defaults location=<location>'.
    --resource-id [Required]: The identifier of the resource.
    --logs                  : JSON encoded list of logs settings. Use @{file} to load from a file.
    --metrics               : JSON encoded list of metric settings. Use @{file} to load from a file.
    --name                  : Azure resource name.
    --service-bus-rule-id   : The service bus rule ID of the service bus namespace in which you
                              would like to have Event Hubs created for streaming Diagnostic Logs.
                              The rule ID is of the format: '{service bus resource
                              ID}/authorizationrules/{key name}'.
    --storage-account-id    : The resource ID of the storage account to which you would like to send
                              Diagnostic Logs.
    --tags                  : Resource tags.
    --workspace-id          : The workspace ID (resource ID of a Log Analytics workspace) for a Log
                              Analytics workspace to which you would like to send Diagnostic Logs.
                              Example: /subscriptions/4b9e8510-67ab-4e9a-95a9-e2f1e570ea9c/resourceG
                              roups/insights-integration/providers/Microsoft.OperationalInsights/wor
                              kspaces/viruela2.

CLI should accept Ids/name for parameters like workspace-id, storage-account-id, service-bus-rule-id and resource-id.
Why location is required parameter + do we need to expose --resource-group?
cc:
@tjprescott / @johnkemnetz

To recap:

[ ] replace foo-id parameters with foo
[ ] expose resource group parameter to support the name scenarios
[ ] resolve lingering issue with location. Hide and open Swagger bug if not needed.

(env) vishrut@mac azure-cli (monitor-2582) $ az monitor diagnostic-settings create -h

Command
    az monitor diagnostic-settings create: Creates diagnostic settings for the specified resource.

Arguments
    --resource-id [Required]: The identifier of the resource.
    --logs                  : JSON encoded list of logs settings. Use @{file} to load from a file.
    --metrics               : JSON encoded list of metric settings. Use @{file} to load from a file.
    --resource-group -g     : Name of the resource group.
    --storage-account       : Name or ID of the storage account to which you would like to send
                              Diagnostic Logs.
    --tags                  : Space separated tags in 'key[=value]' format. Use '' to clear existing
                              tags.
    --workspace             : Name or ID of the Log Analytics workspace to which you would like to
                              send Diagnostic Logs.

Service Bus Arguments
    --namespace             : Name or ID of the Service Bus namespace.
    --rule-name             : Name of the Service Bus authorization rule.


Columns resizing

It would be very convenient to be able to resize columns

Closing this one since the conversation is consolidated in #293.


Concurrency

Fix low-level concurrency issues for the FS backend. Need to write tests which will demonstrate the high-level issues (not very difficult) and fix them (not very difficult as well).

need to improve the HTTP backend to use the new Lock module

Still some issues when stress-testing the HTTP server:
$ ../test.native test HTTP.MEM 10
[..]
Unix.Unix_error(Unix.ECONNRESET, "read", "")

$ ./test.native test HTTP.MEM 11
[..]
Unix.Unix_error(Unix.ECONNRESET, "connect", "")


security: Certificate revocation is now supported via OSCP

PR: https://github.com/cockroachdb/cockroach/pull/53218
From release notes:

Certificate revocation is now supported via OSCP and the cluster setting security.ocsp.mode. This makes a call to the OCSP server on every connection attempt and may wait for up to value specified with the setting security.ocsp.timeout. [#53218][#53218] {% comment %}doc{% endcomment %}

https://cockroachlabs.atlassian.net/browse/CRDB-59

Addressed in https://github.com/cockroachdb/docs/pull/8495/


Add inputs_per_chunk=2 to recipe constructor

This PR implements the suggestion in https://github.com/pangeo-forge/noaa-coastwatch-geopolar-sst-feedstock/issues/2#issuecomment-1104167875.

Ok so we have the issue here where @pangeo-forge-bot doesn't actually get how to create recipe runs for merged feedstock PRs. I think it's worth my taking a moment to try to fix that now, before we move forward, because it would actually be informative to run a test of this recipe before merging.

/run recipe-test recipe_run_id=35

This dataset passes xr.testing.asser_identical when compared to the dataset reported in https://github.com/pangeo-forge/staged-recipes/pull/127#issuecomment-1098438284, which was previously approved by @rwegener2.
So I will now merge this PR, which will trigger a new production deployment, and allow us to see whether adding the inputs_per_chunk kwarg helps resolve the issue being tracked in #2.


create desktop-app

Description of change
This is a new product that we will use internally for vetting the communication system, testing out new approaches and white-box instrumentation hacking with Frida. It is using Tauri.
Type of change

[x] Enhancement (a non-breaking change which adds functionality)

How the change has been tested
Manually.
Change checklist

[x] I have followed the contribution guidelines for this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] New and existing unit tests pass locally with my changes

Really like how this app looks and works.

Hey @nothingismagick, do you intend to continue on this PR? Otherwise I would ask you to close it :)

sry, i think i won't get to it :(


Terminal (Hot Reload) and build (Loading)

Hot Reload
In this image, you can see the first 2 Hot Reloads worked. Then my file saved in the middle of typing which caused an error but recovered after the red X. After recovery the terminal will not show "Hot Reload Succeeded" unless I restart the build. But, most of the time, Hot Reload will work for a bit.

The real problem is Hot Reload will randomly stop working, and since the terminal is not updating It makes it difficult to understand why things are not updating.
Loading
Requesting a restart or running "dotnet watch run"

It says "Using launch settings from LaunchSettings.json". But if I open the browser it is still loading / building in the background, so I am not sure when it is ready.
Before .net 9 it was showing all the processes such as and restoring and building. But now it shows nothing and worse it doesn't show it is ready.

Did you fix the issue? If yes, what did you do to fix it?

Did you fix the issue? If yes, what did you do to fix it?

I am on another issue in the asp.net core community. They’re having issues with the hot reload.
The not showing loading / building in terminal issue, I am still having and haven’t created an issue for that.
It’s been a frustrating few days say the least. I am considering writing a blog / issue post on how .net 10 shouldn’t have any new features and just focus on tooling issues. They’re having last year has been filled with frustrating up and downs.

I agree, I just migrated a big project to .NET 9 because of some features we wanted to use.
I'm thinking of completely rolling back to .NET 8, only because the developer experience is absolutely terrible...
Hope this is fixed ASAP!


Release 0.22.1

Needed to do broken dockerfile when 0.22.0 was released

Release notes created: https://github.com/ponylang/ponylang.github.io/pull/285

windows package is up

Docker release image is up. Playground has updated.

debian and rpm packages are up

release notes published

thanks for playing folks.
i made a change to not download pcre from the rando internet every time that will be part of 0.22.2 which hopefully will go smoothly.


Revert "Give your portfolio a header"

Reverts Pranav-Nadapana/markdown-portfolio#2

close

My name is Pranav Naidu Nadapana Venkata
I am a DevOps engineer.
As I am a freshman, I am learning all the latest DevOps tools. I am keeping my pace up to the present trend technologies.


(ForumsTeam) fixes MicrosoftDocs/azure-docs#32807

Corrected the image urn

@Karishma-Tiwari-MSFT : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@RicksterCDN Can you please review this PR? Thanks :)

#sign-off

@Karishma-Tiwari-MSFT: I'm sorry - only the author of this article, @rickstercdn, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

@RicksterCDN Can you please review this PR? It is not getting merged without review.

that looks good to me - #sign-off


How can I set "header" and "footer" height?

I know this module uses "html-pdf", and it's default header height is 46mm, footer height is 28mm
How can I customize them?
I can't find any options for it.

This is my code

Hope this helps

@zulmarij thanks this solution worked perfectly. It should be noted that you can also pass footer here the same way:
ie:
{   ...   footer: {     height: '25px',     footer: '
this is a footer!
   } }


README.md for pytorch KFserving not clear

/kind bug
What steps did you take and what happened:
Followed the steps in https://github.com/kubeflow/kfserving/blob/master/docs/samples/pytorch/README.md to create a service for a pytorch model.
It was very unclear that the line
python -m pytorchserver --model_dir ./ --model_name pytorchmodel --model_class_name Net
meant that we had to manually install the pytorchserver module that is specified in this github repo
Also, this line is not clear:
Your ~/.kube/config should point to a cluster with KFServing installed.
I do not seem to have a ~/.kube/config file. And I get issues when running the following line:
CLUSTER_IP=$(kubectl -n istio-system get service $INGRESS_GATEWAY -o jsonpath='{.status.loadBalancer.ingress[0].ip}')
output:
CLUSTER_IP=$(kubectl -n istio-system get service $INGRESS_GATEWAY -o jsonpath='{.status.loadBalancer.ingress[0].ip}') Error from server (Forbidden): services "istio-ingressgateway" is forbidden: User "system:serviceaccount:kubeflow-ward-vandriessche:default-editor" cannot get resource "services" in API group "" in the namespace "istio-system"
What did you expect to happen:
Work off the bat when following the steps in the readme file.

@wardVD How do you access your kubeflow cluster and which kubeflow setup you are using?

@yuzisun I was wrongfully trying to set up the service from a jupyter notebook terminal from the Kubeflow UI.
However, when I reproduce the steps from a google cloud shell the command
kubectl apply -f pytorch.yaml didn't work until I ran this command
kubectl label namespace default serving.kubeflow.org/inferenceservice=enabled (which I found on this page, so maybe you can put a reference on the KFServing page as well)
I am currently still stuck trying to run
CLUSTER_IP=$(kubectl -n istio-system get service $INGRESS_GATEWAY -o jsonpath='{.status.loadBalancer.ingress[0].ip}') which returns an empty string.

Oh, and @yuzisun, I'm using vanilla Kubeflow.

@wardVD I think in your case it is not exposed as node port not load balancer, but I agree we should improve the doc to recover different cases.

@wardVD I have updated doc for the instruction for accessing the ingress, please take a look!


[Feature][Branch][RadioButton] Update test code

Description
Add test code for RadioButton
Related Issues
#51
Tests
I added the following tests:
Test render, onPress and props.
Coverage 100% completed.

/home/circleci/dooboo/src/components/shared/__tests__/RadioButton.test.tsx
  14:5   warning  'props' is assigned a value but never used                 @typescript-eslint/no-unused-vars
  14:12  warning  Unexpected any. Specify a different type                   @typescript-eslint/no-explicit-any
  76:7   error    Missing semicolon                                          semi
  79:1   error    Too many blank lines at the end of file. Max of 0 allowed  no-multiple-empty-lines

/home/circleci/dooboo/src/components/shared/__tests__/SearchInput.test.tsx
  3:20  warning  'act' is defined but never used  @typescript-eslint/no-unused-vars

✖ 22 problems (2 errors, 20 warnings)
  2 errors and 2 warnings potentially fixable with the `--fix` option.

Resolve semicolon and blank issue caught by lint test.

You need to make PR to feat/radio-button branch instead of master.


TileLayer and MVTLayer API audit

For #4317
Change List

Add data prop to TileLayer, make getTileData optional
Remove MVTLayer's urlTemplates prop, use data instead
Validate and deep-compare URL templates
Docs
Tests
Update website demos

Coverage increased (+0.1%) to 83.057% when pulling 6125c78a0765340bfec875e30da34b77eac2305a on x/api-audit into 4f70efb960ad50a7ef0afa6dd976da02ffe43666 on x/mvt-layer-rename.


[KIP] - K Bison parsers should not get stuck when passed an invalid file path

Motivation
When developing semantics which load code at runtime, it is very helpful to wire up a simple function involving the #system and #parseKORE hooks and the generated parser_PGM, e.g.,
syntax Pgm ::= loadFile(String) [function]
             | parseFile(KItem) [function]
// ---------------------------------------
rule loadFile(Path) => parseFile(#system("parser_PGM \"" +String Path +String "\""))
rule parseFile(#systemResult(0, Stdout, _)) => #parseKORE(Stdout)

The problem with the above code is that, if the string Path does not represent a valid file, parser_PGM will get stuck and the semantics will get stuck too.
Ideally, the parser program will return an error code and report a message on stderr when the file path passed in is invalid.
Documentation
K Bison generated parsers will return an error code and report an error on stderr when passed an invalid file path as their first argument.
Potential Alternatives/Work-arounds
As an alternative, one could try and write a wrapper script that tries to open the file and read its contents. This script can be designed to fail when the file path is invalid. Then this script could pass the file contents to the underlying parser_PGM.
Testing Approach
This could be tested by:

writing a simple semantics that does hot-code loading using the above approach
checking that the semantics does not get stuck when trying to run parser_PGM on an invalid file path --- it either terminates with 0 and stdout non-empty or a non-zero return code and stderr non-empty

Or simply running parser_PGM directly and seeing that we don't get stuck (not sure if the test harness supports this).

This is actually two different problems working together. The first is that the scanner doesn't report an error if a file doesn't exist. The second is that if all the buffers passed to flex are invalid, it reads from stdin by default and hangs until the user presses Ctrl-D. We need to reconfigure the generated flex scanner to solve both of these problems.


[HOLD] Dataset Media Fields

import fiftyone as fo
import fiftyone.utils.image as foui
import fiftyone.zoo as foz

dataset = foz.load_zoo_dataset("quickstart")

for i, sample in enumerate(dataset):
    sample["thumbnail"] = f"/Users/ben/data/thumbnails/quickstart-{i}.png"
    foui.transform_image(sample.filepath, sample.thumbnail, size=(64, -1))
    sample.save()

dataset.app_config.media_fields = ["filepath", "thumbnail"]
dataset.app_config.grid_media_field = "thumbnail"

session = fo.Session(dataset)

Issues

Resolves #1760

Questions?

How much validation should be done? E.g. when a media field is deleted. Should we validate grid_media_field is a media_field?
Are we extending these to the global app config as well? What if a dataset does not have the right shape?

Todo

Documentation

Following up on some questions from the PR description:
Q: Are we extending these to the global app config as well? What if a dataset does not have the right shape?
A: I don't think we should bring the new Dataset.app_config into the fiftyone.AppConfig (as pointed out, these new settings depend on the shape of the dataset and thus can't be global). Instead I think we should bring fiftyone.AppConfig into Dataset.app_config 🤗  There are some order of precedence details to get right
Q: How much validation should be done? E.g. when a media field is deleted. Should we validate grid_media_field is a media_field?
A: I think we should automatically handle deletion/renaming of a field that's included in media_fields, but, since we don't have a MediaField concept *only a StringField that may contain filepaths, but may also just contain "foo" and "bar"), we shouldn't attempt to validate that a media_fields choice is valid. Just wait for "invalid image" to appear in the App grid

Stale. Merged in to #1954


feat: include generated sources folder in the java sources list

This implementation had some issues, needs more investigation.


Update package.json

Set stylelint and stylelint-config-standard versions, because version 15 of stylelint is not compatible with grunt-stylelint.

@MasX Thanks


Delete IFluidSerializer from core-interfaces

IFluidSerializer is deprecated as of v0.55 (it was moved to shared-object-base). It can be removed in a few versions and after IFluidObject references to it are removed.

Rather than wait for IFluidObject to be removed entirely, can just delete IFluidSerializer property from it.


Quick Search is not working for even famous cities

I had been using hotkey for "Convert location to Geolocation" for a while now, and suddenly it stopped working for even famous cities.
Is there some reason behind it? I had updated the plugin today.

Which geocoding provider are you using, the default (OSM) or Google?

Found the issue, will release a fix in the next few hours.

Fixed.


fix(features): add some features for monocrate

Add io-compat and TLS-related features.

Is this PR adding features or fixing bugs?
We don't have a crate called "compio-feature"

It's not bugs but not new features neither. It's just some reexports and features forwarding.

@Berrysoft That’s new feature. New public API (include cargo feature) are features.

OK, I've changed the title and commit msg.


Fix compilation of C Media driver under visual studio

C version used in visual studio (C++ compiler) does not support VLA

I've pushed a change which is more in keeping with the Aeron codebase.


Update Dask/Spark Survey URL

We should update the form for users to request access to dask and spark version of featuretools to point to this url: https://forms.office.com/Pages/ShareFormPage.aspx?id=2TkvUj0wj0id66bXfx6v2BOWZ27M2npIiEDBPvpJ1ClUOE9MT0MyMloxQUtNVjlINVhMNlpONEc0SS4u&sharetoken=hKGLZZWSk3LfRFGhqxB9
We should also make it slightly more prominent to encourage more users to submit requests as we get closer to wrapping up an initial version of #783

@kmax12 Do you have any specific page/pages on which you want to have this info displayed? We can certainly make it more obvious on the current page, and was thinking that adding it to the Parallel Feature Computation page would make sense.
Anywhere else you were thinking?

i think those places are good. one thing i'd do would be to make it it's own section so it has a header and shows up in the TOC


[Bug] [Worker] duplicate execution shell script

Search before asking

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

What happened
version 3.2.0 ,when I execute shell script, sometimes shell will run twice, from ds log, we can find the evidence.

What you expected to happen
execute one time
How to reproduce
sometimes
Anything else
No response
Version
3.2.x
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

this result happen accidentally ,not it must happen，so i don'know how to repproduce,
I deploy it with k8s helm, 2 master， 3 worker, 1 api.     version is 3.2.0
i just create shell script to run datax program.

It seems ds run the script twice in one task.

How to reproduce this, please provide your cluster deployment info.

this result happen accidentally ,not it must happen，so i don'know how to reproduce,
I deploy it with k8s helm, 2 master， 3 worker, 1 api. version is 3.2.0
i just create shell script to run datax program.
It seems ds run the script twice in one task.

I find these three tasks have this problem , I suspect dependent task logic have bugs, ans these three tasks were invoked  at the same time nearly.


Error when running workflow for Filter, Plot and Explore Single-cell RNA-seq Data tutorial

When running the workflow published in the tutorial https://training.galaxyproject.org/training-material/topics/single-cell/tutorials/scrna-case_basic-pipeline/tutorial.html (with the published starting dataset) one of the last steps where it is renaming the clusters into cell types fails with:
Traceback (most recent call last):
  File "/drive/configs/tmpzfs90vu9", line 9, in <module>
    adata.rename_categories(
  File "/usr/local/lib/python3.9/site-packages/anndata/_core/anndata.py", line 1133, in rename_categories
    self.obs[key].cat.rename_categories(categories, inplace=True)
  File "/usr/local/lib/python3.9/site-packages/pandas/core/accessor.py", line 92, in f
    return self._delegate_method(name, *args, **kwargs)
  File "/usr/local/lib/python3.9/site-packages/pandas/core/arrays/categorical.py", line 2487, in _delegate_method
    res = method(*args, **kwargs)
  File "/usr/local/lib/python3.9/site-packages/pandas/core/arrays/categorical.py", line 920, in rename_categories
    cat.categories = new_categories
  File "/usr/local/lib/python3.9/site-packages/pandas/core/arrays/categorical.py", line 634, in categories
    raise ValueError(
ValueError: new categories need to have the same number of items as the old categories!

Most likely because there are more clusters than cell types being mentioned here:
adata.rename_categories(
    key='louvain',
    categories=['DP-M4', 'DP-M3', 'DP-M1', 'T-mat', 'DN', 'DP-L', 'DP-M2', 'Macrophages'])

Looking at markers, there are 9 clusters (0 to 8), however there are 8 cell types in the tutorial. This is running on singularity containers, so no modification in the environments. Maybe @nomadscientist can ping the workflow author?

In the newer run we see these clusters:

In the tutorial, we see these clusters:

So I suspect that:

From 0 to 4, everything seems very similar

Cluster 5 and 6 are swapped: Cluster 5 in the new one (first figure) is number 6 in the old one (second figure), and the opposite (6 new == 5 old).

New cluster 7 was a part of old cluster 3

Old cluster 7 == new cluster 8

So, besides ignoring point 3, I would say that new order is:
DP-M4,DP-M3,DP-M1,T-mat,DN,DP-M2,DP-L,Unknown,Macrophages

But maybe there are smaller filtering changes somewhere done differently between tutorial and final workflow.

ahhh have the tools been updated? Every time the tools update the filtering changes slightly
It's also possible that we updated the tutorial but didn't upload an up-to-date workflow in the last tutorial update
Either way, I'll look into it, thanks so much!

I ran the workflow file that is linked in the tutorial, I didn't run tools manually, which guarantees that the tool versions are the same.

which of these two did you run?

I got it from the tutorial page itself at the bottom:

Right, so this just got really weird.
I ran that workflow from within the Galaxy interface and it did work fine.
I also ran - just to check - the workflow from the screenshot I sent you (the updated workflow) and it also worked fine.
So... I'm stumped. Where are you running it? Is it possible it's calling slightly different tools?

I'm running on slurm with singularity, I suspect that usegalaxy.eu uses singularity as well. If not the reason might be down to that. When opening the workflow it never complained about missing versions, so it is using at least the version set on the workflow.

Hmm... ok, well, I guess it works on a public instance? Or maybe somehow the cluster calling sets a seed on the public instance it isn't on yours, because there are those ML tools in there that can vary, maybe?

I remember having a conversation with Malte many years ago where he was telling me that scanpy had no control on some random seeds from some underlying libraries for louvain or for UMAP, I can't remember. The side effect was that on different hardware, all things the same (and we are achieving that through versioning and singularity containers) you could get slightly different results. Maybe this is one case of that. So if you still get the same result on other hardware, I would leave it.

Cool - I'll close this but keep it in mind if people on other instances have a similar issue


Logrotate config invalid

The logrotate config based on the splunk_facl.j2 template created by the configure_facl.yml task seems to be invalid:
logrotate[685980]: error: splunk_facl:1 lines must begin with a keyword or a filename (possibly in double quotes)
logrotate[685980]: error: splunk_facl:5 unexpected }
logrotate[685980]: error: found error in file splunk_facl, skipping

I believe, the file /roles/splunk/templates/splunk_facl.j2 should be changed from :
    postrotate
        /usr/bin/setfacl -Rm u:{{ splunk_nix_user }}:rx /var/log
    endscript
}```

to

/var/log {
postrotate
/usr/bin/setfacl -Rm u:{{ splunk_nix_user }}:rx /var/log
endscript
}
Or something like that (but i don't have means to validate my assumption

The problem has to do with \r characters. Just replace them at least that fixed the issue for me.
tr -d '\r' < /etc/logrotate.d/splunk_facl> /etc/logrotate.d/splunk_facl

@JasperJuergensen Had the same issue and applied what you suggest to solve it ! Thanks again


'ng2-rickshaw' is not in the npm registry.

'ng2-rickshaw' is not in the npm registry.
Do u plan to publish soon?

@jbadeau Sorry i have no plan to publish please use git url for install temporary.
$ npm install --save git+https://github.com/daominhsangvn/ng2-rickshaw


[ISSUE apache#3059] fix start http-demo error caused by properties

Fixes #3059.
Motivation
Explain the content here.
Explain why you want to make the changes and what problem you're trying to solve.
Modifications
Describe the modifications you've done.
Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)
If a feature is not applicable for documentation, explain why?
If a feature is not documented yet in this PR, please create a followup issue for adding the documentation

checks failed may cased by anothor bug #3053，please merge the fix code as soon as possible so i can through the checks later.


Redemption result rework

new type for the result of redeem operation
added new fields to RedemptionEntry to match latest changes in the API
VoucherRedemptionContext can also take metadata

no chyba looks good :+1:


docs(ast): document more AST nodes

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#6000  👈
#5998
main

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

Join @DonIsaac and the rest of your teammates on  Graphite


Use symbols if possible for private properties on exposed objects

#172
Seeing whether this passes on Travis…

Tests look good.
@btford: can you take a look please?

Thanks @vicb. Just pushed some changes.

LGTM with a few comments. @btford ?

pls add fix #172 in the commit comment

Sure thing. Done.
(Is that so GH auto-closes the issue?)

Is that so GH auto-closes the issue?

Yep, that's it.

landed as f8a2be5ab889b3026774ea36cea4e385399a52df


Model training time and GPU detials

Hi, can the authors share the details of the GPU on which MVGFormer was trained and how long was the training time. Also, was the best model trained for 100 epochs?

Hi, we trained on 8 V100 GPUs, each with a batch size of 1, totaling a batch size of 8. The training process takes about a day. The best model was trained for 40 epochs.


DOC Fix link to test file for 6_human_scorers.md

Description

Fixing broken link.

Tests and Documentation

wonder why the link checker didn't find this...


Usage of the middleware can prevent static files to be served.

Dear maintainer of the django-tos package,
Thank you for your efforts in maintaining this package. It's much appreciated.
I have a question regarding its use in conjunction with serving static files through Django. I've noticed that it blocks the delivery of stylesheets, images, fonts, etc., which results in an unstyled Terms of Service page.
Is there a recommended way to handle this issue? I would greatly appreciate any guidance you can provide. For now, I just reimplemented the middleware. For now, I am extending the middleware to fast skip certain file types.
I understand that many users do not experience this issue as they serve their static files through a web server. However, I still believe that it could be desirable to have a "fast skip" rule for static and media files.
If this is something you would find useful, I would be happy to prepare a pull request to add this functionality. Please let me know if this is of interest to you.
Thank you again for your work on this package.
Best regards,
Benedikt

Hello,
What do you mean it's blocking stylesheets? Shouldn't be anything in here affecting static media.
Most people run collectstatic and serve the static media independetly via nginx or a CDN.

In our development environment, Django serves all files. However, the static and media files on the Terms of Service page are blocked by the UserAgreementMiddleware. It would be helpful if there was an easy way to bypass the check for files under STATIC_URL  and MEDIA_URL.

Are you using whitenoise (or something similar) to serve your static media in your production environment maybe?

So, did a little more digging.
In development, with the staticfiles app in INSTALLED_APPS, and when running runserver, django automatically excludes static media from running through the middleware.
So in dev via runserver, django doesn't run static files through the MIDDLEWARE.
Only way it should be blocking is if you're not running the django staticfiles middleware.
https://docs.djangoproject.com/en/dev/ref/contrib/staticfiles/#runserver
Also, in dev, it's common to add the staticfiles url for staticfiles routing:
https://docs.djangoproject.com/en/dev/ref/contrib/staticfiles/#static-file-development-view
Not sure if BOTH are required for serving locally, but everything i've ever worked on in Django has always had that url wired into an environment check.
So, I think this package is performing as intended, routing all requests through the middleware. Static media requests, as you mentioned, shouldn't be ran through django in prod.
In development, if configured right, this middleware shouldn't even be seeing static files.
My guess is there's some misconfiguration with how you have staticfiles set up locally that's causing the routing issue.
Gonna close for now as I don't think we need any code patch here related to this.


docker.io registry is not created

@l3r8yJ can you create a docker.io repository for bot app?

@h1alexbel give me 5 mins

@h1alexbel see

@l3r8yJ nice, thanks


Editor 6.1.0 - File tree

Hi!
Great to see the file tree back! Thanks!
However, the drag and drop linking does not work in raw mode, too (the banner appears at the bottom, but it has no effect). It works in document mode.
Also, Reveal in File Explorer has no effect on Win 7 64bit.
Thanks for all the hard work!

Ok, when you create a new file/folder, can you see that file/folder on the disk from your file manager?

After Save&Sync, I can see (but if I only Save, it's not yet visible).

@nagim @KINGSABRI This issue of file not shown on the disk will be fixed in next release.
I'm closing this issue since the drag and drop is the related to the behaviour of the markup toolbar (#98).

Reveal in File Explorer is still not working.

@nagim we are using shell. showItemInFolder  from electron, maybe it's related to https://github.com/electron/electron/issues/4349 or related to https://github.com/electron/electron/issues/6514
I'll investigate.

Great, thanks!


SDL window update

Based on #1171
Fixes #1169
cc @jplatte @Icefoxen

CI doesn't test it anyway at the moment...
@homu r+

:pushpin: Commit 72483e4 has been approved by kvark

:hourglass: Testing commit 72483e4 with merge 7ad6987...

v0.5 is published - https://crates.io/crates/gfx_window_sdl
It also re-exports some of the gfx_device_gl types for our convenience.

:broken_heart: Test failed - status

@homu r+

:pushpin: Commit cdc06fe has been approved by kvark

:hourglass: Testing commit cdc06fe with merge 911db3b...

:sunny: Test successful - status


Generated directive class name should have 'Directive' suffix

Version
$ ng --version
(node:20286) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
Could not start watchman; falling back to NodeWatcher for file system events.
Visit http://ember-cli.com/user-guide/#watchman for more info.
angular-cli: 1.0.0-beta.6
node: 6.2.1
os: linux x64

Repro steps
The following generate command produces a directive class name without the 'Directive' suffix.
$ ng g directive shared/directives/wrap-if
(node:20210) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
Could not start watchman; falling back to NodeWatcher for file system events.
Visit http://ember-cli.com/user-guide/#watchman for more info.
installing directive
  create src/app/shared/directives/wrap-if.directive.spec.ts
  create src/app/shared/directives/wrap-if.directive.ts

src/app/shared/directives/wrap-if.directive.ts
import { Directive } from '@angular/core';

@Directive({
  selector: '[wrap-if]'
})
export class WrapIf {

  constructor() {}

}

As per the styleguide,

Do append the symbol name with the suffix that it represents.
...
export class ValidationDirective

The generated class name should be WrapIfDirective.

@Brocco could you have a look please?

The associated spec file of the directive still imports the wrong directive name:
/* tslint:disable:no-unused-variable */

import { TestBed, async } from '@angular/core/testing';
import { HoverEvent } from './hover-event.directive';

describe('Directive: HoverEvent', () => {
  it('should create an instance', () => {
    let directive = new HoverEventDirective();
    expect(directive).toBeTruthy();
  });
});

Is this better suited to a new issue or can this one be re-opened?

What version are you using? ng version

$ ng version
Could not start watchman; falling back to NodeWatcher for file system events.
Visit http://ember-cli.com/user-guide/#watchman for more info.
angular-cli: 1.0.0-beta.15
node: 6.2.1
os: linux x64

Okay I'll reopen this and assign it to @brocco.

This has been resolved via PR #1940 and will be included in the next release


[ Doc ] Add doc for 'How to generate tflite for feature extractor'

. Add md file inclues 'how to genearte tflite for feature extractor'
. import_pb_to_tensorboard.py for tensorboard from frozen model.
. add some pics
Self evaluation:

Build test:	 [X]Passed [ ]Failed [ ]Skipped
Run test:	 [X]Passed [ ]Failed [ ]Skipped

Signed-off-by: jijoong.moon<EMAIL_ADDRESS>

:memo: TAOS-CI Version: 1.4.20191203. Thank you for submitting PR #555. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://nnsuite.mooo.com/.

:octocat: cibot: @jijoongmoon, **** does not include doxygen tags such as . You must include the doxygen tags in the source code at least.

:octocat: cibot: @jijoongmoon, You wrote code with incorrect doxygen statements. Please check a doxygen rule at http://github.com/nnsuite/TAOS-CI/blob/master/ci/doc/doxygen-documentation.md

We generate a report if there are dangerous coding constructs in your code. Please read http://nnsuite.mooo.com/nntrainer/ci/repo-workers/pr-checker/555-202009161740070.77136397361755-84d514c1269b284ce9995365a4502c5a7c4f05f4/report/pylint_result.txt.

:octocat: cibot: @jijoongmoon, One of the module of prebuild group is failed. If you want to get a hint to fix this issue, please go to https://github.com/nnstreamer/nntrainer/wiki/.

We generate a report if there are dangerous coding constructs in your code. Please read http://nnsuite.mooo.com/nntrainer/ci/repo-workers/pr-checker/555-202009161954570.81809711456299-a51d01f4c45c6b0d0829bdbd38e3c5cc367e75a9/report/pylint_result.txt.


Docs: Links to reference framework broken

The https://github.com/mesosphere/dcos-commons/blob/master/docs/tutorial.md page has multiple links to a "reference framework", which all do not work: https://github.com/mesosphere/sdk-reference-framework/ is a 404.

This issue is outdated, thus closing.


Use Object.keys instead of the pure js implementation in goog.object.getKeys

Add a new goog.object.ASSUME_NATIVE_FUNCTIONS define to activate it.
The default is still to use the native js implementation.
Object.keys browser support: http://kangax.github.io/compat-table/es5/#Object.keys

@fredj have you see micro-benchmarks comparing the performance of both approaches? Just curious.

No, I haven't

See http://jsperf.com/object-keys-vs-hasownproperty for a speed comparison

Is there a justifiable reason for this change?

Forgot about this pull request...
I don't need this anymore because I use Object.keys() directly (dropping support for IE < 8)


206 Partial Content requests raise/crash ERR_HTTP_TRAILER_INVALID

When piping audio files from S3 through Meteor-Files with interceptDownload() and serve() the server crashed on some files with ERR_HTTP_TRAILER_INVALID from https://github.com/nodejs/node/blob/d01a06a916efd30844e1e0a38e79dc0054fc4451/lib/_http_outgoing.js#L458-L460 (tested on node 12.6.1).
I think the reason for this is that on Status code 206 both Content-Range and Transfer-Encoding are set, and if I am not mistaken they conflict. If I understand the specs correctly those are not allowed to be used together:

https://developer.mozilla.org/en-US/docs/Web/HTTP/Range_requests#Comparison_to_chunked_Transfer-Encoding
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Trailer

        case '206':
          headers.Pragma               = 'private';
          headers.Trailer              = 'expires';
          headers['Transfer-Encoding'] = 'chunked';
          break;

https://github.com/VeliovGroup/Meteor-Files/blob/master/server.js#L242-L246
if (!http.response.headersSent) {
        http.response.setHeader('Content-Range', `bytes ${reqRange.start}-${reqRange.end}/${vRef.size}`);
      }

https://github.com/VeliovGroup/Meteor-Files/blob/master/server.js#L1840
My knowledge of HTTP headers is limited, hopefully, this gives you some clues @dr-dimitru .
My current workaround is to pass my own responseHeaders() without the case 206 part.

That's interesting, we basically stream audio content from GridFS via 206 and the slightlycustomized interceptDownload example from the wiki (customized for GridFSBucket) and we never ran into any of these errors. Not downgrading your issue, rather I am aware that Murphy's law will hit us, too.
Any hint how to reproduce this?

You must have a request including byte-ranges. This can be tested with an mp3 file (tested with a 3MB one)

The flag range is important here.
This should then

hit https://github.com/VeliovGroup/Meteor-Files/blob/master/server.js#L1729
and then https://github.com/VeliovGroup/Meteor-Files/blob/master/server.js#L1742
and in the end https://github.com/VeliovGroup/Meteor-Files/blob/master/server.js#L1840

The response should typically look like:

I observed this locally with minio and did not test this against AWS S3, but I doubt that this should change the result.
The second and all upcoming requests look like this then, notice that the range increases:

Though you won't see this as the server crashes in the first request.

Hope this helps, I reproduced the crash with this:
https://your.server/cdn/storage/ServiceFiles/kEXcy7pEbHw56v32E/stream/kEXcy7pEbHw56v32E.mp3 -i -H "Range: bytes=0-" --cookie "x_mtok=foo" --output foo.mp3

@jankapunkt If you're not able to reproduce this, I'll make a repro by tomorrow.

Thanks a lot I will check this out against our current builds

Small update, I am currently working on a reproduction, so far I could not get https://github.com/VeliovGroup/Meteor-Files-Demos/tree/master/demo-simplest-streaming to crash.

This seems to be caused in conjunction with Nginx, this comment helped a lot. I added proxy_http_version 1.1; to my location block like this:
    location /cdn/ {
        client_body_buffer_size 128k;

        proxy_pass http://app;
        proxy_redirect      off;
        proxy_set_header    Host              $host;
        proxy_set_header    X-Real-IP         $remote_addr;
        proxy_set_header    X-Forwarded-For   $proxy_add_x_forwarded_for;
        proxy_set_header    X-Forwarded-Proto $scheme;
        proxy_http_version 1.1;
    }

and the crash is gone. Nginx uses proxy_http_version 1.0; per default.
I still try to figure out what exactly happens here.

@dr-dimitru @jankapunkt
I am finally able to reproduce this with https://github.com/VeliovGroup/Meteor-Files/tree/master/demo-simplest-streaming. Run that project, grab the mp3 URL, and run the following (--http1.0 is important here!):
curl http://localhost:3001/cdn/storage/Sounds/foo/original/foo.mp3 -i -H "Range: bytes=0-500" -v --http1.0 > /dev/null
while
curl http://localhost:3001/cdn/storage/Sounds/foo/original/foo.mp3 -i -H "Range: bytes=0-500" -v --http1.1 > /dev/null does not fail.
This should mean that we can DOS Meteor-Files Servers now 🚨.
I think that https://github.com/VeliovGroup/Meteor-Files/blob/master/server.js#L242-L246 needs to cover https://github.com/VeliovGroup/Meteor-Files/blob/master/server.js#L1840 as well and set one of those headers, depending on the request e.g. if range requested or not.

Wow really great work @menelike

@menelike @jankapunkt thank you guys for investigation.

Fixed in the latest release;
Added memo into FAQ section


iteration bug with every and Lazy.range

Should be easier to understand with an example : http://jsfiddle.net/tkpqbst5/
Example
console.log('Without range');
var a = Lazy([0, 1, 2, 3, 4, 5]);
var r = Lazy([1000]);
console.log(a.toArray());
console.log(r.toArray());

var every = r.every(function(x) { console.log('Does a contains x?', a.contains(x)); return a.contains(x); } );

console.log('Every should be false since a does not contains x, every is: ', every);
console.log('');
console.log('With Range');
var a = Lazy([0, 1, 2, 3, 4, 5]);
var r = Lazy.range(1000, 1001);
console.log(a.toArray());
console.log(r.toArray());

var every = r.every(function(x) { console.log('Does a contains x?', a.contains(x)); return a.contains(x); } );

console.log('Every should be false since a does not contains x, every is: ', every);

Result
Without range
a: [0, 1, 2, 3, 4, 5]
r: [1000]
Does a contains x? false
Every should be false since a does not contains x, every is:  false

With Range
a: [0, 1, 2, 3, 4, 5]
r: [1000]
Does a contains x? false
Every should be false since a does not contains x, every is:  true

Ah, I see the issue here. It's actually related to the take implementation. Should be able to fix...


Geofences triggered only once

When I create a list of Geodences as on your example only the 1st event enter or exit is triggered until I reinitialize thE location client again, I used your exact sample code I don't have this issue with the older version of Google Play Services.
Is there something I need to tell the client after serving the 1st event on a geofence to continue listening?

Internal: 26816072

Hey shehabic,
How are you experiencing this? Mock or real locations?

This sample has been deprecated/archived (check README for more information on newer samples related to this technology).
As recommended by GitHub, we are closing all issues and pull requests.


Session.getTcpConnection passes null to ipaddr.isValid

Hitting "Pause on Caught Exceptions" brings up an "TypeError: Cannot read property of 'length' of null."
ipaddr.isValid(endpoint.address) -> looks like address is null.  Perhaps check?

Amazingly enough, this is ipaddr.js working as (apparently) intended.  ipaddr.isValid first calls IPv6.isValid, which calls IPv6.parser, which returns null if a parse fails.  IPv6.isValid then tries to construct an IPv6 object representing null, which throws this error.  IPv6.isValid catches the error, and returns false, so ipaddr.isValid calls IPv4.isValid, which returns true.

We could clean this up one day... ?

We can send them a pull request if it bothers you, but I'm not even sure that it's unintentional.


Feat: remove deprecation handling for 2.0.0

Closes https://github.com/aisingapore/PeekingDuck-Private/issues/114

Remove deprecation handling code for 2.0.0 release

input.recorded and input.live conversion
detect_ids conversion
run_config_yml fallback
peekingduck.nodes.node.AbstractNode conversion

Got the following error when running your feature branch on macOS, using numpy 1.23.2

Changes look ok, but got runtime error on macOS conda env as described in comment.

Merged PR #738 resolves this error.


Create a session feedback table

Overview
We want to create a feedback mechanism for our course sessions. We need to create a new model to store this feedback in.
Action Items

[ ] Create a branch
[ ] Ensure your local database is up to date and you have the application running locally.
[ ] Create a new entity in /src/entities called session-feedback. This entity will have 3 columns:

sessionFeedbackId
sessionId
feedbackTags
feedbackDescription

string
string (note that it should have a many (session-feedback.sessionId) to one (session.session Id) relationship )
Enum Array (see enum array example below)
string

enum FeedbackTags {
      RELATABLE = "relatable",
      USEFUL = "useful"
      INSPIRING = "inspiring",
      TOO_LONG = "too long",
      TOO_COMPLICATED = "too complicated"
      NOT_USEFUL = "not useful"
}

[ ] Following the instructions on the ReadMe to create a migration
[ ] Commit and push your changes and tag @eleanorreem

Resources

typeorm enum column types
Type ORM documentation on migrations
Stack overflow on enum array column types

Hi! Interested in taking this on. Can you assign it to me?

Hey @cmstrandwold thank you for your patience, you have been assigned!
Happy coding!

Hello, is this ticket still being worked on? If not, I would be interested in picking it up

Hey @ckirby19 thanks so much for your interest! Assigned 😄


System mouse cursors

Description
This PR adds the basic framework for the mouse cursor system. While only system cursors are supported for now, the APIs are designed with the consideration of asynchronously loaded cursors (image cursors).
With this PR:

Cursors are assigned to regions in a declarative way using data classes.
MouseRegion, RenderMouseRegion and MouseTrackerAnnotation have a new property MouseCursor cursor that can be used to customize mouse cursors of pointers that are hovering over the region.
Inkwell and a few other widgets also have a new parameter MouseCursor mouseCursor
Hidden cursor, uncontrolled cursor, and several system cursors are supported.

This PR is only the framework part of the system. Without the upcoming engine change, these changes won't take effect, but will not break existing apps either.
For more information about the design, see https://flutter.dev/go/system-mouse-cursor
Related Issues

Part of https://github.com/flutter/flutter/issues/31952

Tests
I added the following tests:

Many tests to the cursor aspect of MouseTracker
Test the cursor aspect of MouseRegion
Test MouseCursorController

Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I signed the CLA.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I updated/added relevant documentation (doc comments with ///).
[x] All existing and new tests are passing.
[x] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Did any tests fail when you ran them? Please read Handling breaking changes.

[x] No, no existing tests failed, so this is not a breaking change.
[ ] Yes, this is a breaking change. If not, delete the remainder of this section.

[ ] I wrote a design doc: https://flutter.dev/go/template Replace this with a link to your design doc's short link
[ ] I got input from the developer relations team, specifically from: Replace with the names of who gave advice
[ ] I wrote a migration guide: Replace with a link to your migration guide

The analyzer is unhappy.

@Hixie @goderbauer I made some major changes:

PreparedMouseCursor now has a protected method performActivate, which is overridden by subclasses. It replaces the is type-checks in MouseTracker.
The method calls are split into a MouseCursorController class, which only has static methods, such as activateSystemCursor, and is to be used by PreparedMouseCursor.performActivate.
The cursor part of MouseTracker is split into a mixin MouseTrackerCursorMixin. The original MouseTracker is renamed to BaseMouseTracker, whereas the one with all mixins is the new MouseTracker.

Can you take a look?

Avoiding the repaint for when cursors change adds a lot of complexibility. I am not sure if that's worth it, TBH. The repaint shouldn't be that expensive and I would image that when you need to change the cursor, you'd also be changing other aspects of the UI to "justify" the new cursor. For that, you'd have to do a repaint anyways...

@goderbauer Can you take a look at the new design, which I call "session-based":
Overview of design:

MouseCursor is an immutable class and stores data. Subclasses should override method createSession to create a MouseCursorSession object.
Every MouseCursor has a corresponding MouseCursorSession class, which represents the duration when a device displays a cursor, i.e. the tuple (device, cursor).
MouseCursorSession is a mutable class that stores states and provides methods activate and dispose to override. The activate will handle the method calls as well as resource fetching, caching, fallback cursors, etc.
MouseTrackerAnnotation stays const, and doesn't have listeners at all.
No more MouseTrackerRenderObjectMixin. RenderMouseRegion implements variable cursor by implementing MouseTrackerAnnotation.

Just adding myself to this so I can see when it's ready as we need it for our flutter project.
https://github.com/getcouragenow

I think the default behavior for this on web should be the cursor autochanges when it detects you are hovering a button, text, etc. Will this be the behavior for web or will it be necessary to add an extra widget on every clickable, text widget we want to show a different cursor on?
Many thanks for implementing this!

@goderbauer I think I've addressed all comments. Can you take a look again?

Besides the comments, I also changed SystemMouseCursor, instead of int shapeCode, it now uses String kind, suggested by Stuart for clarity. Let me know if it's considered inappropreate.


Object protocols without specialization

For #210.
Now all pyclass has a method registory for protocols:
impl pyo3::class::proto_methods::HasProtoRegistry for MyClass {
    fn registory() -> &'static pyo3::class::proto_methods::PyProtoRegistry {
        static REGISTRY: PyProtoRegistry = PyProtoRegistry::new();
        &REGISTRY
    }
}

, where PyProtoRegistory is a set of method tables:
#[doc(hidden)]
pub struct PyProtoRegistry {
    async_methods: AtomicPtr<PyAsyncMethods>,
    basic_methods: AtomicPtr<PyObjectMethods>,
    ...
}

.
Using the ctor crate, we insert some initialization codes for this registry.
For example, when we write this code:
#[pyproto]
impl PyObjectProtocol for MyClass {
    fn __hash__(&self) -> PyResult<isize> {
        Ok(self.val as isize)
    }
}

, (roughly) the following code is generated:
#[ctor]
fn __init_Object_2817873() {
    let mut table = pyo3::class::PyObjectMethods::default();
    table.set_hash::<MyClass>();
    <MyClass as pyo3::class::proto_methods::HasProtoRegistry>::registory().set_basic_methods(table);
}

One disadvantage of this solution is it needs redundant Box::new for some protocols(basic, iter, and so on). However, to keep PyProtoRegistry simple and small, I chose this design.
Unfortunately, some protocols are not yet tested.
TODO

[x] Add tests for async protocols

[x] Maybe we need to change the trait definition to make it work?

[x] Add tests for descr protocols
[x] Maybe need some more doc comments?

I forgot to mention that this PR has a breaking change. nb_bool is now moved under PyNumberProtocol from PyObjectProtocol.

Thank you for the review!

Let's fix the Send + Sync bounds in #948 rather than adding in this PR.

I accidentally pushed these changes when I was playing with them. I'll revert them.

Does it make the implementation much more complicated if we can keep this in the PyObjectProtocol?

I don't have any good solution now, unfortunately.

I don't have any good solution now, unfortunately.

:+1: ok. I have a half-baked idea but it's hard to write down as I haven't properly thought about it yet. I'll try to find time tomorrow evening to experiment with it whether it can help and explain it better then.

I have a half-baked idea but it's hard to write down as I haven't properly thought about it yet.

Thank you but wait for a bit...
I don't think most users know that __bool__ is classified as a part of Object protocols.
Thus I don't think it's worth doing if we need more codes to do so.

At last, I decided to move nb_bool under PyObjectProtocol again.
I don't think the code is very ugly but please check it.

It would also be good to add a test for #940 in this PR - if I read your implementation correctly I think that should already be solved by what you've done!

Added a test for __await__.
I was really confused by Python's async/await and noticed some things:

Returning Future from Rust is hard.
To return some value, we have to make StopIterException have the value.
But for now, I think this is sufficient for testing proc-macros.

OMG...

(Windows + Python3.8)

🍿🤓

I would be interested to hear what you think about how we could solve #844 with this new implementation.

I think we can reuse the same trick as __set/delitem__ for that, but maybe it should be done in another PR :thinking:

I think we can reuse the same trick as set/delitem for that, but maybe it should be done in another PR 🤔

I'm happy with that - this PR is already quite large 😄

Now I think this PR is ready.
Though I added more comments than usual, please point out what you think is unclear.

The test_await was failing for me locally (python3.6 from apt in virtualenv), this is the workaround I used to make them pass.
Traceback (most recent call last):
  File "<string>", line 12, in <module>
  File "/usr/lib/python3.6/asyncio/events.py", line 694, in get_event_loop
    return get_event_loop_policy().get_event_loop()
  File "/usr/lib/python3.6/asyncio/events.py", line 602, in get_event_loop
    % threading.current_thread().name)
RuntimeError: There is no current event loop in thread 'Dummy-1'.
test test_await ... FAILED

diff --git a/tests/test_dunder.rs b/tests/test_dunder.rs
index 67a66fb49..47f22fc91 100644
--- a/tests/test_dunder.rs
+++ b/tests/test_dunder.rs
@@ -612,7 +612,11 @@ async def main():
 # but we see still errors on Github actions...
 if sys.platform == "win32" and sys.version_info >= (3, 8, 0):
     asyncio.set_event_loop_policy(asyncio.WindowsSelectorEventLoopPolicy())
-loop = asyncio.get_event_loop()
+try:
+    loop = asyncio.get_event_loop()
+except RuntimeError: # RuntimeError: There is no current event loop in thread 'Dummy-1'.
+    loop = asyncio.new_event_loop()
+    asyncio.set_event_loop(loop)
 assert loop.run_until_complete(main()) is None
 loop.close()
 "#

@konstin
Thanks, I pushed the change based on your diff.

🎉


i am not able to zoom out.

Issue Type: Bug
i tried to zoom in by the following steps in visual studio code version-<IP_ADDRESS>
1.go to preference
2. go to setting.
3. Then i made the zoom from -1 to 100%.
4. Now i am not able to zoom out.

Did you use % in the value, like "100%"?

yes

@AbhilashaBaghel can you try without using the % character, it should just be a literal number.

I am not able to open it now. not getting popover in zoom mode to open preference settings

@AbhilashaBaghel you should be able to open the settings file directly and make that change. It is located in C:\Users\<name>\AppData\Roaming\Code\User\settings.json

thanks bpasero now it is coming fine. I am able to zoom out.


Update version to 2.1.0

Upgrade GeoAPI to <IP_ADDRESS>
Upgrade Azavea.Utilities.Common to 3.3.1
Upgrade Azavea.Open.DAO to 2.2.0
Add NUnit.Mocks 2.6.4

+1


Ruby support

I'd love to see support for Ruby's do..end blocks, which we use for multi-line closures the same way JS devs use {..}.
Also, I don't know if you've heard but apparently 1-2 people are noticing some excessive CPU usage... 😹

support for do..end blocks would be AWESOME.


Dynamic popup position

Date popup always opens at the bottom of field even when there's no space at the bottom. It should change its position at top or vice-versa.

Date popup always opens at the bottom of field even when there's no space at the bottom. It should change its position at top or vice-versa.

Yes facing same issue


script enhance

[ ]  srcipt should generate source file with question number and user name suffix

now script can auto generate folder of question, src and README XD

good job