openapi: fix the swagger file

Signed-off-by: Miguel Duarte Barroso<EMAIL_ADDRESS>
What this PR does / why we need it:
Somehow, the swagger file is not up to date, which causes the CI test pull-kubevirt-generate to fail.
Check the following failures for examples:

https://prow.apps.ovirt.org/view/gcs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/4035/pull-kubevirt-generate/1303231357811429376
https://prow.apps.ovirt.org/view/gcs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/4131/pull-kubevirt-generate/1303004615326830595
...

Release note:

NONE

/cc @phoracek

/lgtm
Champion

/hold
I think that it is a bug in the generation code.
@xpivarc was looking into it this morning.

There seems to be an issue in generating of swagger. Openapi is generated correctly but openapispec sometimes replace our Patch with k8s one...

There seems to be an issue in generating of swagger. Openapi is generated correctly but openapispec sometimes replace our Patch with k8s one...
I hadn't time to look for a root cause.

Is there anything I can help you with ? All my stuff is blocking on this.

/retest

I hadn't time to look for a root cause.

could this just be a weird timing issue between merging the golang 1.13.4 update, the corresponding openapi related fix, and the patch pr?

@davidvossel that sounds possible.
I believe that we need both Patch types... as one of them(the k8s one) is used in operations related to standard patching of objects. (patch vm,vmi,...) and our Patch is used inside Kubevirt properties... The generating somehow non-predictable choose one of them(its possible that we have a conflict here and this will not be possible to overcome). The whole logic is in openapispec.go if anybody have a bw to look at it(I probably find time tomorrow evening).

I believe that we need both Patch types... as one of them(the k8s one) is used in operations related to standard patching of objects. (patch vm,vmi,...) and our Patch is used inside Kubevirt properties..

oh no... so we overloaded the term patch.
@ashleyschuett maybe we should alter our side so we don't collide with k8s here. what do you think?  We can still change our API since your patch PR hasn't made it into an official kubevirt release yet.

I believe that we need both Patch types... as one of them(the k8s one) is used in operations related to standard patching of objects. (patch vm,vmi,...) and our Patch is used inside Kubevirt properties..

oh no... so we overloaded the term patch.
@ashleyschuett maybe we should alter our side so we don't collide with k8s here. what do you think? We can still change our API since your patch PR hasn't made it into an official kubevirt release yet.

I checked the PR introducing our Patch, it was based upon the fix of openapi. It is still possible that it is the root cause since its random and this PR was merged only 2 days ago. (will try repeatedly run it on this commit to see if its root cause)
Note: Ashley is out of the office for couple of days :)

Are you referring to this PR: https://github.com/kubevirt/kubevirt/pull/3612 ?
If so, I found it causing other flakiness on CI and constantly failing tests locally: https://prow.apps.ovirt.org/view/gcs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/4141/pull-kubevirt-check-tests-for-flakes/1303426394306383872#1:build-log.txt%3A20934

Are you referring to this PR: #3612 ?
If so, I found it causing other flakiness on CI and constantly failing tests locally: https://prow.apps.ovirt.org/view/gcs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/4141/pull-kubevirt-check-tests-for-flakes/1303426394306383872#1:build-log.txt%3A20934

Yes, why do you think so?

Are you referring to this PR: #3612 ?
If so, I found it causing other flakiness on CI and constantly failing tests locally: https://prow.apps.ovirt.org/view/gcs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/4141/pull-kubevirt-check-tests-for-flakes/1303426394306383872#1:build-log.txt%3A20934

Yes, why do you think so?

I bisected the failure as described here, without that PR everything works, with it locally it fails and on CI it is flaky.

/hold
Seems we'll be focusing on #4143 instead.

/hold
Seems we'll be focusing on #4143 instead.

Indeed, rerunning several times might generate a diff like this PR suggests, but might as well revert it, its flaky.

Abandoning in lieu of #4154 .


[refactor / possible bug] worker synchronizer to reply back for available batches

Section 1
Currently when we request from the worker synchronizer to synchronize a batch (PrimaryWorkerMessage::Synchronize)  it will first check in storage whether the batch is already there.

If not , it will ask from other worker peers to fetch. Primary will be notified about the fetched batch id once the peer worker has sent it
If yes, it will basically do nothing about it. It probably assumes that since it has been found in storage then the batch has been received by a peer worker and the primary will be notified anyways via the processor will handle it . Now if for some reason this notification message from worker --> primary has not been successfully processed for some reason, there is no mechanism to re-trigger and there will be no way for the primary to get notified about the batch availability - although the batch is in worker.

Section 2
The above case (2) can create deadlock situations. In DevNet we have recently seen an issue with the payload synchronization in the recent incident where I believe is an artifact of the above behaviour. The scenario is the following:
We assume that we have two validators, (A) & (B).

Validator (A) worker creates a batch with the hypothetical hash kxmsamyzXZxRPc+C and forwards to primary
Validator (A) primary includes this to a header proposal. Let's assume that a certificate is produced, sequenced and even executed. For the execution we fetch the payload via the block_waiter which first checks if the payload is available via the block_synchronizer . The block_synchronizer sees that the header has been created by us (Validator A) and doesn't need to check the near store cache payload_store , but rather assumes the payload is already in worker - so the block_waiter can just continue and fetch the batch - all OK.
Now Validator (B) worker creates a batch with the exact same hash kxmsamyzXZxRPc+C - yes it happens currently in DevNet currently (since same transactions are posted) . Worker broadcasts the batch to the other workers and just waits for a quorum of them to reply back - once the quorum replies it even cancels the network handlers. Let's assume that because of that - or even some network glitch - Validator (A) hasn't received the batch.
Because Validator (A) hasn't received validator's B batch it will never initiate any process to forward the batch id to the primary node . So the batch id  kxmsamyzXZxRPc+C is still missing from the Validator (A) payload_store
Now Validator (B) creates a header -> certificate -> sequenced and needs to get executed. Validator (A) tries to execute the certificate which references to the batch id kxmsamyzXZxRPc+C . The block_synchronizer will check the payload_store for the batch availability (since it's not our header) . The batch is missing , so it will dictate its worker to synchronize it from the other worker peers.
Because of the current behaviour that described in Section 1 the primary will never manage to successfully get the notification about the payload availability as there is not way to re-trigger it.
Result: Validator (A) stops its execution and blocks forever

From the DevNet the bellow logs tell that story - well in a quite abstract way , but that's where I am oriented at:
Validator A

We see that Validator A it will indefinitely send via the block_synchronizer a request to its worker to sync the batch kxmsamyzXZxRPc+C.....
Validator B

We see that Validator B is managing to successfully progress and request the batch from its worker (see log line primary::block_waiter: Sending batch kxmsamyzXZxRPc+C request to worker id 0
Resolution
This PR attempts to resolve this issue by making the worker synchronizer reply back to primary immediately when a batch has been found available in store and not make any assumptions about other processes that might be running to notify the primary.
Also, an addition fix/improvement is made to ensure that the synchronizer will not send synchronization messages to other workers when a vector of missing batch ids is empty - we have also seen this happening in DevNet.
PS: Similar issue with the above can arise even when the worker restarts (so any pending requests from worker to primary are lost) or for some reason primary doesn't store the batch id in the payload_store
TODO

[ ] Follow up PR to store all the batch ids in the near cache payload_store in primary irrespective of wether "we" or an "other" primary has created. Will need to confirm we'll not break there some other assumptions - which I believe it won't

Thanks @akichidis this looks great, and it does cover an important edge case! I would simply ask for a test on the PayloadReceiver checking that sending twice the same (digest, worker_id) pair results in no errors (and the pair being written to the store). It sounds trite, but it would make it explicit that we do expect idempotent behavior from this component.
Nit: This risks invalidating the batches_received metric, and if we want to be really fancy we can increase the PayloadToken in the PayloadStore to reflect we are adding the same digest several times, but that's probably an overkill (and will be refactored away if we make authorities commit to batch rounds).

Very good point @huitseeker ! I've amended the PR with tests on the payload_receiver . Also enhanced the tests on the worker processor as well to ensure the idempotent behaviour there as well.

Nit: This risks invalidating the batches_received metric, and if we want to be really fancy we can increase the PayloadToken in the PayloadStore to reflect we are adding the same digest several times, but that's probably an overkill (and will be refactored away if we make authorities commit to batch rounds).

@huitseeker Ah yeah this could create some skew, but to be honest I don't expect to affect that much the grand scheme of things here (but current logging can confirm the expectation). Also as you said the refactoring to make the authorities commit to batch rounds will introduce several changes, so we can have a look as part of that - or after that.


adding Universidade Nove de Julho

@ViictrP I am sorry, the domain uninove.edu.br is removed from our trusted domains list because it was abused in the past. If you are the student of this school, please enroll to GitHub Student Developer Program. Then apply for JetBrains educational subscription with your GitHub account (GitHub tab at https://www.jetbrains.com/shop/eform/students).


Purge ReadFuture.

Part of #101
We don't need another class for just one test class. This way we can make SimpleFuture final and move this if wanted into the testing infrastructure.

@vanniktech LGTM, merge conflict though.


warnOnDeprecatedUsages

Question
I want to suppress the deprecated field warnings. I tried using warnOnDeprecatedUsages.set(false) but it did not work. Any suggestions on how to suppress the warnings?
apollo {     service("xyzzy") {         warnOnDeprecatedUsages.set(false)         failOnWarnings.set(false)     } }

Hi!
warnOnDeprecatedUsages is used to control whether the a warning will be logged at code generation time, if an operation uses a deprecated element. But regardless of this flag the generated code will include a @Deprecated annotation on deprecated fields, and using them in your code will generate a warning from the Kotlin compiler. There is currently no option to disable this.


fix component color

@xavijam could you take a look?
Fix: https://github.com/CartoDB/cartodb/issues/8173

no npm shrinkwrap?

pushed neno :)

:+1:


⚠ 한경주요지수-코스피200 has degraded performance

In 40562d6, 한경주요지수-코스피200 (https://markets.hankyung.com/indices/kospi200) experienced degraded performance:

HTTP code: 200
Response time: 15921 ms

Resolved: 한경주요지수-코스피200 performance has improved in abfaee5.


Fix issue that occurs when using bytes as secret key.

The Django secret key can and should be random bytes which may or may
not be decodable to UTF-8.

Current coverage is 77.01% (diff: 100%)

Merging #890 into master will increase coverage by 0.01%

@@             master       #890   diff @@
==========================================
  Files            30         30
  Lines          1635       1636     +1
  Methods           0          0
  Messages          0          0
  Branches        244        244
==========================================
+ Hits           1259       1260     +1
  Misses          302        302
  Partials         74         74

Powered by Codecov. Last update 3728860...05a4315

I don't think that SECRET_KEY is intended to be of type bytes.
The default, empty value is str, not bytes. The value generated by startproject is also str, not bytes.
https://docs.djangoproject.com/en/1.10/ref/settings/#std:setting-SECRET_KEY doesn't say anything about bytes.
If you look at the implementation of get_random_string, it assumes the opposite (in a rarely use code path).
In a 12-factor app it's a best practice to provide secrets via environment variables and random bytes (half of which are non-ASCII) aren't safe to pass via environment variables.
That said, it's best not to crash when SECRET_KEY contains bytes. That's a good change.
I don't see the point of randomizing the SECRET_KEY in the tests setting, what problem is this solving?

There is no default value for SECRET_KEY. If it's left out, Django will throw an error stating the SECRET_KEY is not set. Most of the code that requires the SECRET_KEY use it in methods that only accept it as bytes. For example, see django.utils.crypto (https://github.com/django/django/blob/master/django/utils/crypto.py). Setting the secret key shouldn't be limited to setting them via environment variables. In any case, the script has to fetch the SECRET_KEY from somewhere before placing it in an environment variable.
As for why I changed the SECRET_KEY in the tests, I found that changing the key was the best way to verify make_hash still works. Leaving out the changes to make_hash and setting the SECRET_KEY to a non-UTF-8 byte string would cause the tests to fail. Placing the changes to make_hash and SECRET_KEY causes all tests to pass without modification.

Was there any concern still about this change?

I don't see any explanation for the removal of the newline normalization. Maybe there's a good reason for that and I don't see it? Please explain.
Moving from force_text to force_bytes is certainly the right thing to do since hashlib expects bytes, and I agree that the crash should be fixed, even though I've never seen a SECRET_KEY consisting of bytes in the wild until now.

I must ask, why was the input to the hash being modified in the first place?
Note that replacing newlines with spaces gives you different hashes. For example...
In [1]: import hashlib
In [2]: hashlib.sha1(b'some long string').hexdigest()
Out[2]: '03058ae698770de83ff929f96773eadfc2b6aacc'
In [3]: hashlib.sha1(b'some\nlong\nstring').hexdigest()
Out[3]: 'b97515a2c115a9872a6e882202615c8c6ad41280'

The idea probably was that the SQL query would pass through a textarea or something where newlines might be changed from \n to \r\n or vice versa.
I've been thinking a bit, and modifying queries in the browser does not and should not work anyway. So I'm good with this change.

Can we just remove the randomization of the secret key in tests?
I really dislike randomness in tests, no matter the reason (except, of course, when testing a statistical process or something that explicitly deals with randomness).
I thought I said that earlier but I can't find that comment 😕

The new secret key is not random at all. It's a byte string of bytes with values 0 through 255 in sorted order.

Here is what that secret key is now.
In [1]: bytes(bytearray([i for i in range(256)]))
Out[1]: b'\x00\x01\x02\x03\x04\x05\x06\x07\x08\t\n\x0b\x0c\r\x0e\x0f\x10\x11\x12\x13\x14\x15\x16\x17\x18\x19\x1a\x1b\x1c\x1d\x1e\x1f !"#$%&\'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\\]^_`abcdefghijklmnopqrstuvwxyz{|}~\x7f\x80\x81\x82\x83\x84\x85\x86\x87\x88\x89\x8a\x8b\x8c\x8d\x8e\x8f\x90\x91\x92\x93\x94\x95\x96\x97\x98\x99\x9a\x9b\x9c\x9d\x9e\x9f\xa0\xa1\xa2\xa3\xa4\xa5\xa6\xa7\xa8\xa9\xaa\xab\xac\xad\xae\xaf\xb0\xb1\xb2\xb3\xb4\xb5\xb6\xb7\xb8\xb9\xba\xbb\xbc\xbd\xbe\xbf\xc0\xc1\xc2\xc3\xc4\xc5\xc6\xc7\xc8\xc9\xca\xcb\xcc\xcd\xce\xcf\xd0\xd1\xd2\xd3\xd4\xd5\xd6\xd7\xd8\xd9\xda\xdb\xdc\xdd\xde\xdf\xe0\xe1\xe2\xe3\xe4\xe5\xe6\xe7\xe8\xe9\xea\xeb\xec\xed\xee\xef\xf0\xf1\xf2\xf3\xf4\xf5\xf6\xf7\xf8\xf9\xfa\xfb\xfc\xfd\xfe\xff'

Ah, right, I had missed that change in your patch.
However, like I explained at length earlier, putting bytes in the SECRET_KEY still goes against Django's expectations and established practice.
There's even a ticket about it: https://code.djangoproject.com/ticket/24994.
The changes to the test settings in this PR are not only useless but also wrong.

I went ahead and merged your change with an added commit that reverts the SECRET_KEY change.
Thanks for your contribution!


[Spec] features for TV release

Code clean, add definition - features for TV release.
Signed-off-by: Jaeyun<EMAIL_ADDRESS>

:memo: TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #96. 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://ci.nnstreamer.ai/.

:octocat: cibot: @jaeyun-jung, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://ci.nnstreamer.ai/nnstreamer-edge/ci/repo-workers/pr-checker/96-202209261246060.95016002655029-b7a21a4287925a948b92883e5a14d73e745606fd/.

:octocat: cibot: @jaeyun-jung, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://ci.nnstreamer.ai/nnstreamer-edge/ci/repo-workers/pr-checker/96-202209261707330.57748007774353-b19e27f623b58fcb4622b79c5f4cd5025f1df3db/.


Get-MTUser Does Not Query Guest Users

The function Get-MTUser allows the type Guest as UserType. This value is never processed and the function is currently not able to query guest users. Instead a Get-mtuser -UserType Guest will return member users.
I will open a pull request that fixes this.

Fixed. Please retest with -preview module (or on main once published).


Includes and or mixins sometimes do not trigger changes in parents while watching

There are some weird issues with includes that have been addressed in other open issues. But I wanted to document another issue that has been a pain point for me, in that I think the includes are treated as orphaned modules, and when a change in an included template occurs, the cache is not correctly invalidated and webpack watch will only rebuild the module and not the containing chunk. - could be wrong about the specifics of what's going on here, but it requires stopping webpack watch and rebuilding the the bundles from scratch to get the changes from child includes to propagate into the parent chunks.
I don't think this is all scenarios, but definitely some. Also, I want to start using new persistent cache features and this makes me weary that those file changes won't bust the cache properly - although I haven't tested against this.

I published a similar package that fixes these problems for me as well as some of the other issues with this loader and predictable variable scoping with includes and mixins. Extremely similar to this.
https://www.npmjs.com/package/simple-pug-loader


[Bug]: Default value of an Input’s text is undefined

Is there an existing issue for this?

[X] I have searched the existing issues

Description
When defaultText isn’t set and user hasn’t focused on the input’s textarea, an input's text value is undefined, even upon reload.
Steps To Reproduce
loom video.
Steps to reproduce (in dev mode)

Drag and drop an Input widget
Inspect the unevaltree

Public Sample App
No response
Version
Cloud

@somangshu @sbalaji1192 if we do this change, is this a new version? Also @sbalaji1192 i need some help understanding how many users will be impacted by this. Can you triage this once?

@dilippitchika It's a very simple fix but it will impact people who are expecting the default value of the input widget to be undefined. So we should add a new version.
There is no way for us to know "how many" users will get impacted.

@dilippitchika Ignore my previous comment about introducing a new version. Making this change would not affect any app. so we should be fine with making the change on the same version of the input widget.

@iamrkcheers please have a discussion with @sbalaji1192 before picking this up

Stats

Stat
Values

Reach
827

Effort (months)
0.25


IGAPP-447: Additional field for feedback contact mail

This pull request belongs to an issue on our bugtracker.
You can find it there by looking for an issue with the key which is mentioned in the title of this pull request.
It starts with the keyword IGAPP.

Tested on Android :+1:

I think the red star is not necessary anymore as optional feedback is marked with (optional) :heavy_check_mark:
I think there could be a little padding between the feedback mail and the send button :heavy_check_mark:
I think the feedback mail input could be smaller in its height, currently it looks a little bit like a multi line input :heavy_check_mark:
Do you think you could add tests for some of the behavior even though there are probably none right now? :heavy_check_mark:
I think the feedback sent thanks message looked better without bold text. :heavy_check_mark:


counter-clockwise on safari inverts stroke and background

When viewing the page http://mathewbyrne.github.io/angular-progress-arc/ on Safari, the counter-clockwise-example has wrong colours.

I can confirm this happens in iOS8 and Safari for Mac. It does not actually happen on iOS7 from what I remember testing a few weeks ago.

Thanks, can definitely see the issue.  Safari must have broken this since I made it last year.  Will try and come up with a fix.


Warn if updated_at field for snapshot is not same datatype as what's returned in snapshot_get_time()

Description
There are 4 different semantics for timestamp datatypes - for simplicity let’s say 2 categories:

naive timestamp - no timezone information, no UTC offset “noon on january 1st, 2024”
aware timestamp - is aware of timezone

UTC offset like “-2 hours”;
specific named timezone “America/Los Angeles”;
absolute timestamp ltz uses your session timezone

One of the trickiest things that can happen within snapshots is when there are naive timestamps (rather than aware). In those cases, we need clear ways for the user to configure a "mutual agreement" with the dbt system how to interpret those timestamps when they are actively involved in the snapshot configuration.
Up until this point, the approach has been that naive timestamp must be UTC

there is no way to specify anything else
we don't document this
there's no warning if you supply a data type that's not a UTC timestamp

Some users may want to use an adjacent column that contains the relevant UTC offset or time zone (or configure the time zone globally for the dbt project (like this) or specifically for one model).
Example of snapshot - updated_at when using strategy=timestamp:
{% snapshot orders_snapshot %}

{{
    config(
      target_database='analytics',
      target_schema='snapshots',
      unique_key='id',

      strategy='timestamp',
      updated_at='updated_at_field'
    )
}}

select * from {{ source('jaffle_shop', 'orders') }}

{% endsnapshot %}

PROBLEM
When the initial snapshot occurs, the dbt_valid_from and dbt_valid_to columns inherit the data type of whatever you've provided for updated_at config (could be a date, could be a naive timestamp, etc.). But once a record is changed, dbt updates the dbt_valid_to column to snapshot_get_time() which returns (in snowflake) a timestamp_ntz data type in the UTC time zone. This is then implicitly converted to the original inherited data type, which can lead to incorrect data if their updated_at field is NOT timestamp_ntz data type in the UTC time zone (incorrect comparisons; may coerce timestamp differently than user expects).
Naive vs. aware timestamps in Snowflake:
https://docs.google.com/presentation/d/14qrx8YbnGnoP2FgnxSD5Z8fxcnoYq4DKRrfHBDanbfA/edit#slide=id.g20f6efbe802_0_34
SOLUTION
Let’s go with Idea 1 for now, maybe some magic in the future
Idea 1 - put burden of using correct data type on user:

go look up what data type updated_at field is, see if it’s compatible
if it’s not throw an warning (or error but that would be backwards incompatible, so would need to use a flag) to tell user to convert field to correct data type (adapter dependent)
updated_at already accepts a SQL statement [though we should add docs for this]:

    {% snapshot orders_snapshot %}

    {{
        config(
          target_database='analytics',
          target_schema='snapshots',
          unique_key='id',

          strategy='timestamp',
          updated_at='convert_timezone('UTC', updated_at_field),'YYYY-MM-DD HH24:MI:SS.FF3 TZHTZM')'
        )
    }}

    select * from {{ source('jaffle_shop', 'orders') }}

    {% endsnapshot %}

Idea 2 - magic stuff to automatically convert:

go look up what data type updated_at_field is, see if it’s compatible
based on what it is, automatically do the conversion to the correct data type (adapter dependent)

[Adding example from snapshot discussion]
Regarding the naïve timestamp approach.  I feel this is a pretty big problem because it can result in the wrong data being written.  In our case, we use Fivetran to load Snowflake.  We use a timestamp snapshot strategy with the _FIVETRAN_SYNCED column as the updated_at config.  We also include "where _fivetran_deleted = FALSE" on our snapshots so when the row is deleted in the source the snapshot will indicate the row is no longer valid.  The _FIVETRAN_SYNCED column is defined as a timestamp_tz and therefore when the initial snapshot occurs the dbt_valid_from and dbt_valid_to columns are also defined as timestamp_tz.  When a record is then deleted from the source, the dbt snapshots sets the dbt_valid_to column to snapshot_get_time().  Snapshot_get_time() however returns a timestamp_ntz data type in the UTC time zone.  This UTC time is then implicitly converted to a timestamp_tz which stores the UTC value and adds the time zone offset of the session, which in our case is currently -0500.  This time is now 5 hours in the future, which is not the correct time.
As mentioned I feel this a bug and should be addressed in dbt-core.  Some ideas.
- The snapshot should automatically convert the column specified in the updated_at config to timestamp_ntz.
○ This will result in the dbt_valid_from and dbt_valid_to column also being timestamp_ntz.
- The snapshot should be aware of the data type and as a result snapshot_get_time() should return that same data type.
- Return an error if the column specified in the updated_at config is anything but timestamp_ntz.
I realize some of these ideas are breaking changes so maybe a new snapshot strategy should be introduced that allows users to make the switch when ready.
Workarounds
- Manually convert the updated_at column to timestamp_ntz in the snapshot definition.
- Ensure every user performing the snapshot is configured in the UTC time zone.
- Utilize soft deletes in the source to avoid dbt using the hard delete snapshot logic.
○ This will require modifying downstream models so they account for the deleted flag.
- Override the snapshot_get_time() macro.
○ This is what we did.  More details below.
We found that overriding the snapshot_get_time() was the best work around for us.  I don't like the solution and it is a little risky but we changed the Snowflake  command to:
to_varchar(convert_timezone('UTC', current_timestamp()),'YYYY-MM-DD HH24:MI:SS.FF3 TZHTZM')
This converts the timestamp to a varchar which retains the offset information so when it is stored to timestamp_tz or timestamp_ltz the offset is correct.  When stored to a timestamp_ntz column it is also correct and in UTC because the offset is trimmed away.  As mentioned this is risky because I am not sure all the places snapshot_get_time() is used and changing the data type could be problematic.
Originally posted by @jvanpee in https://github.com/dbt-labs/dbt-core/discussions/7018#discussioncomment-6755127

I have confirmed updated_at already accepts a SQL statement:
{% snapshot orders_snapshot %}
    {{
        config(
          unique_key='id',
          strategy='timestamp',
          target_schema='dbt_ggoheen',
          updated_at='TO_TIMESTAMP_NTZ(date)'
        )
    }}

    select * from {{ source('raw', 'orders') }}
{% endsnapshot %}

There is differences on what is returned by snapshot_get_time() based on adapters:

snowflake returns a timestamp with no timezone
bigquery returns a timestamp in the timezone of your session

Here’s a comparison of the inconsistencies across adapters

Opened a new issue in dbt-labs/docs.getdbt.com: https://github.com/dbt-labs/docs.getdbt.com/issues/6012


Storage changes the order of parameters

When chains are stored, it seems that parameters are sorted lexicographically:
julia> chain = Chains(randn(500, 3, 4), [:σ, :k, :c])
Chains MCMC chain (500×3×4 Array{Float64, 3}):

Iterations        = 1:1:500
Number of chains  = 4
Samples per chain = 500
parameters        = σ, k, c

Summary Statistics
  parameters      mean       std   naive_se      mcse         ess      rhat
      Symbol   Float64   Float64    Float64   Float64     Float64   Float64

           σ   -0.0139    0.9927     0.0222    0.0230   2181.1151    1.0003
           k    0.0227    0.9978     0.0223    0.0250   1925.5822    1.0011
           c    0.0195    0.9956     0.0223    0.0245   2001.6224    0.9994
...

julia> h5open("an_hdf5_file.h5", "w") do f
         write(f, chain)
       end

julia> # ...and we can get it back
       chain = h5open("an_hdf5_file.h5", "r") do f
         read(f, Chains)
       end
Chains MCMC chain (500×3×4 Array{Float64, 3}):

Iterations        = 1:1:500
Number of chains  = 4
Samples per chain = 500
parameters        = c, k, σ

Summary Statistics
  parameters      mean       std   naive_se      mcse         ess      rhat
      Symbol   Float64   Float64    Float64   Float64     Float64   Float64

           c    0.0195    0.9956     0.0223    0.0245   2001.6224    0.9994
           k    0.0227    0.9978     0.0223    0.0250   1925.5822    1.0011
           σ   -0.0139    0.9927     0.0222    0.0230   2181.1151    1.0003
...

This is confusing: plot(chain) shows a different order when the chains are read back from disk. It also breaks post-processing code that assumes the original order.

Any chance to have the pull request that solves this issue merged soon in the repository? I am facing the same issue here and that is preventing me from using this package (which is, otherwise, very nice!).


Add heterogeneity

No need to merge the branches for now. Keep the heterogeneity changes on branch 'hetero'


Problem with https/tls configuration -

Hello, I have a problem with coniguration Twinny to using https/tls (i have ollama server with nginx)
On http (port 80) twinny is working.
This is my json with twinny config:
{
	"twinny.apiHostname": "ollama.example.com",
	"twinny.chatModelName": "llama2:7b",
	"twinny.fimModelName": "wizardcoder:7b-python",
	"twinny.fimApiPath": "/api/generate",
	"twinny.chatApiPath": "/v1/chat/completions",
	"workbench.settings.applyToAllProfiles": [
		"twinny.disableAutoSuggest"
	],
	"twinny.chatApiPort": 443,
	"twinny.fimApiPort": 443,
	"twinny.useTls": true
}

Nginx configuration:
server {
    listen 80;
    server_name example.com; # Change this to your domain name

    # Redirect HTTP to HTTPS
    return 301 https://$server_name$request_uri;
}

server {
    listen 443 ssl;
    server_name example.com; # Change this to your domain name

    # SSL configuration
    ssl_certificate /path/to/your/ssl/certificate.crt;
    ssl_certificate_key /path/to/your/ssl/privatekey.key;

    # Other SSL configurations like ssl_protocols, ssl_ciphers, etc. can be added here

    location / {
        proxy_pass http://localhost:3000;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection 'upgrade';
        proxy_set_header Host $host;
        proxy_cache_bypass $http_upgrade;
    }
}

This is a error that I have when i try run prompt

2024-03-04 10:22:35.714 [error] [Extension Host] Fetch error: TypeError: fetch failed
at Object.fetch (node:internal/deps/undici/undici:11576:11)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async e.streamResponse (c:\Users\adm_mjalmuzna.vscode\extensions\rjmacarthy.twinny-3.7.8\out\index.js:2:121574)

Desktop (please complete the following information):

OS: Windows 10
VS Code version: 1.87
Twinny version: 3.7.8

Hey, can you call your api using https without twinny extension?

Yes, calling using https via curl https://.. working correctly and return answer for prompt.

Please check developer tools in vscode when twinny runs and paste the log, thanks.

Hello I notice you're trying to use api.openai.com as your hostname which isn't currently supported.
Many thanks,

'api.openai.com' is only my dns server name.  We have local lan server with gpu hosting Ollama in our LAN.

Hey, sorry I am not actually sure in this case... @rcgtnick any advice, you seem to be the https/server expert! Many thanks.

@Marcinj21 Do you have access to your NGINX logs? If so, what is it logging when Twinny makes a request?

Logs from nginx debug when using Twinny on 443
twinny-nginx-debug.log
I also upload logs when using another extension for VSCode - Continue.dev.
Continue refers to the same server as Twinny over HTTPS, and it works.
continue-nginxdebug-logs.txt
This is my all nginx configuration:
nginx-config.txt

Based on peer closed connection in SSL handshake while SSL handshaking from your NGINX log, I'd say the client (the nodejs HTTP/HTTPS library) wasn't happy with the TLS negotiation. My next steps would be:

verifying that the client is actually trying to connect with HTTPS and not plain HTTP. Can you use tcpdump on the server or client?
verifying the HTTPS endpoint

Verifying client is attempting HTTPS connection
On the client, you could run this (if MacOS):
sudo tcpdump -nni en0 port 443 and host your.ollama.endpoint.com -s0 -A
or this (if linux):
sudo tcpdump -nni any port 443 and host your.ollama.endpoint.com -s0 -A
Or, on the server, you could run this:
sudo tcpdump -nni any port 443 and host <IP_ADDRESS> -s0 -A (where <IP_ADDRESS> is your IP)
Those will all show more or less the same data, so any of them work for this test.
The -A will cause tcpdump to print packet contents, so you can look for plain HTTP request headers. If you see anything you can actually read (like Authorization: or POST /...), the traffic is not encrypted and the issue is on the client.
Every time I experienced the symptom you are seeing, it's been that the client tried to connect to a TLS endpoint with plain HTTP, but it's worth verifying.
Verifying the HTTPS endpoint
You could also try using the openssl command to check the HTTPS endpoint:
openssl s_client -connect your.ollama.endpoint.com:443
That will try a TLS negotiation and let you know if it worked. I don't think this is it, since you were able to connect with curl, but you never know.

Stale


bpf/Makefile: add sparse to check target

For now just turn on all the warnings, but that can be changed later if
there is too many false positives.
Also moved non clang specific bits into seperate field since sparse
doesn't understand --target bpf.
Closes: #1025 (sparse checks for C-bpf code)
Signed-off-by: Alexander Alemayhu<EMAIL_ADDRESS>

The output looks something like this
Script started on Tue 25 Jul 2017 07:11:32 AM CEST
a@alemayhu:~/opt/og/src/github.com/scanf/cilium/bpf$ make check
sparse -Wsparse-all -Iinclude -I. -D__NR_CPUS__=8 -O2 *.c
lib/events.h:23:35: warning: symbol 'cilium_events' was not declared. Should it be static?
lib/maps.h:28:35: warning: symbol 'cilium_lxc' was not declared. Should it be static?
lib/maps.h:37:35: warning: symbol 'cilium_policy' was not declared. Should it be static?
lib/maps.h:46:35: warning: symbol 'cilium_reserved_policy' was not declared. Should it be static?
lib/maps.h:55:35: warning: symbol 'cilium_proxy4' was not declared. Should it be static?
lib/maps.h:63:35: warning: symbol 'cilium_proxy6' was not declared. Should it be static?
lib/maps.h:72:35: warning: symbol 'cilium_calls_111' was not declared. Should it be static?
lib/maps.h:83:35: warning: symbol 'tunnel_endpoint_map' was not declared. Should it be static?
lib/drop.h:42:48: error: incompatible types in comparison expression (different type sizes)
lib/drop.h:95:48: error: incompatible types in comparison expression (different type sizes)
lib/dbg.h:171:48: error: incompatible types in comparison expression (different type sizes)
lib/dbg.h:171:48: error: incompatible types in comparison expression (different type sizes)
lib/dbg.h:171:48: error: incompatible types in comparison expression (different type sizes)
lib/drop.h:42:48: error: incompatible types in comparison expression (different type sizes)
lib/drop.h:95:48: error: incompatible types in comparison expression (different type sizes)
lib/dbg.h:171:48: error: incompatible types in comparison expression (different type sizes)
lib/dbg.h:171:48: error: incompatible types in comparison expression (different type sizes)
lib/dbg.h:171:48: error: incompatible types in comparison expression (different type sizes)
lib/dbg.h:171:48: error: incompatible types in comparison expression (different type sizes)
lib/dbg.h:171:48: error: incompatible types in comparison expression (different type sizes)
lib/dbg.h:171:48: error: incompatible types in comparison expression (different type sizes)
lib/dbg.h:171:48: error: incompatible types in comparison expression (different type sizes)
lib/dbg.h:171:48: error: incompatible types in comparison expression (different type sizes)
lib/dbg.h:171:48: error: incompatible types in comparison expression (different type sizes)
lib/dbg.h:171:48: error: incompatible types in comparison expression (different type sizes)
lib/dbg.h:171:48: error: incompatible types in comparison expression (different type sizes)
lib/dbg.h:171:48: error: incompatible types in comparison expression (different type sizes)
lib/dbg.h:171:48: error: incompatible types in comparison expression (different type sizes)
lib/dbg.h:171:48: error: incompatible types in comparison expression (different type sizes)
lib/dbg.h:171:48: error: incompatible types in comparison expression (different type sizes)
lib/dbg.h:171:48: error: incompatible types in comparison expression (different type sizes)
lib/drop.h:42:48: error: incompatible types in comparison expression (different type sizes)
lib/drop.h:95:48: error: incompatible types in comparison expression (different type sizes)
lib/dbg.h:171:48: error: incompatible types in comparison expression (different type sizes)
lib/dbg.h:171:48: error: incompatible types in comparison expression (different type sizes)
lib/dbg.h:171:48: error: incompatible types in comparison expression (different type sizes)
lib/dbg.h:171:48: error: incompatible types in comparison expression (different type sizes)
lib/dbg.h:171:48: error: incompatible types in comparison expression (different type sizes)
lib/dbg.h:171:48: error: incompatible types in comparison expression (different type sizes)
lib/dbg.h:171:48: error: incompatible types in comparison expression (different type sizes)
lib/drop.h:42:48: error: incompatible types in comparison expression (different type sizes)
lib/drop.h:95:48: error: incompatible types in comparison expression (different type sizes)
lib/dbg.h:171:48: error: incompatible types in comparison expression (different type sizes)
lib/dbg.h:171:48: error: incompatible types in comparison expression (different type sizes)
lib/dbg.h:171:48: error: incompatible types in comparison expression (different type sizes)
lib/dbg.h:171:48: error: incompatible types in comparison expression (different type sizes)
lib/dbg.h:171:48: error: incompatible types in comparison expression (different type sizes)
lib/dbg.h:171:48: error: incompatible types in comparison expression (different type sizes)
lib/dbg.h:171:48: error: incompatible types in comparison expression (different type sizes)
clang -Iinclude -I. -D__NR_CPUS__=8 -O2 -target bpf -Wall -Werror -Wno-address-of-packed-member -Wno-unknown-warning-option --analyze *.c
[1mbpf_lxc.c:257:3:
[0;1;35mwarning:
[1mValue stored to 'ip6' is never read
                ip6 = data + ETH_HLEN;
[0;1;32m                ^     ~~~~~~~~~~~~~~~
[0m1 warning generated.
a@alemayhu:~/opt/og/src/github.com/scanf/cilium/bpf$ exit
Script done on Tue 25 Jul 2017 07:11:44 AM CEST

Looks good, we should add an issue for converting relevant u* types we have in BPF code over to __be*/__le* where appropriate (e.g. in checksum code), so that sparse can actually do type checking on them.

Looks good, we should add an issue for converting relevant __u* types we have in BPF code over to __be*/__le* where appropriate (e.g. in checksum code), so that sparse can actually do type checking on them.

Can you take care of this @scanf ?

Will do. Thanks.

Was expecting the tests to pass, but looks like kubernetes tests are flaky, https://jenkins.cilium.io/job/cilium/job/cilium/job/PR-1175/5/consoleText
[Runtime Tests] ==> cilium-master-build-PR-1175-5: Error: Unable to reach out daemon: Get http://%2Fvar%2Frun%2Fcilium%2Fcilium.sock/v1beta/healthz: dial unix /var/run/cilium/cilium.sock: connect: no such file or directory
[K8s multi node Tests] + code=404
[K8s multi node Tests] + '[' 404 -ne 403 ']'
[K8s multi node Tests] + abort 'Error: unexpected connection between frontend and backend. wanted HTTP 403, got: HTTP 404'
[K8s multi node Tests] ------------------------------------------------------------------------
[K8s multi node Tests]                           K8s Test Failed
[K8s multi node Tests] Error: unexpected connection between frontend and backend. wanted HTTP 403, got: HTTP 404
[K8s multi node Tests]
[K8s multi node Tests] ------------------------------------------------------------------------
[K8s multi node Tests] + set +x
[K8s multi node Tests] ------------------------------------------------------------------------
[K8s multi node Tests]                             Cilium logs

CI is functional again, we can rebase this on master to get a good CI run.


feat: process lightnode sale events

Related Github tickets

Closes https://github.com/VolumeFi/paloma/issues/1920

Background
We need pigeon to pick up on node sale events and report them to paloma. These events will come from compass, following the implementation in https://github.com/palomachain/compass-evm/pull/38. This PR adds support to read and relay those events.
Note: This uses dev16 branch as base since it builds on top of the renamed skyway calls.
Testing completed

[ ] test coverage exists or has been added/updated
[ ] tested in a private testnet

Breaking changes

[ ] I have checked my code for breaking changes

Should this go into dev16? We can bring it back to master instead if you'd like. I will have to rebase my changes anyway, but that way we decouple the node sale stuff from PF a bit more.

Should this go into dev16? We can bring it back to master instead if you'd like. I will have to rebase my changes anyway, but that way we decouple the node sale stuff from PF a bit more.

I think we should merge the current (after this PR) dev16 branch into master. The skyway rename changes are already in paloma master, so we need to update pigeon to stay compatible.
We can leave this PR into dev16 so it's easier to read, then merge everything to master, and push a new dev16 branch. The same we did on paloma. What do you think?


Taking way too long to post

I have noticed that once it passes the "Tik tok done loading file onto servers" phase, it gets stuck on a loop that will never come true until it times out. adding at line 611 and line 625 "
if page.locator(':has-text("100%")').is_visible():
uploaded = True
break
" causes the program to throw "ERROR UPLOADING: VIDEO HAS SAVED AS DRAFT BUT CANT UPLOAD" even though it is successfully uploaded, cutting time down to only about 30s to 1m, versus 5-10m of loops.

Please upgrade to version 3.3 and let me know if that has fixed the issue


[tool_crash] NoSuchMethodError: NoSuchMethodError: The getter 'dependencies' was called on null.Receiver: nullTried calling: dependencies

Command
flutter update-packages --force-upgrade

Steps to Reproduce

...
...
...

Logs
NoSuchMethodError: NoSuchMethodError: The getter 'dependencies' was called on null.
Receiver: null
Tried calling: dependencies
#0      Object.noSuchMethod (dart:core-patch/object_patch.dart:54:5)
#1      createTemporaryFlutterSdk (package:flutter_tools/src/commands/update_packages.dart:1457:60)
#2      UpdatePackagesCommand.runCommand (package:flutter_tools/src/commands/update_packages.dart:322:33)
#3      FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:1119:18)
<asynchronous suspension>
#4      FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:974:27)
<asynchronous suspension>
#5      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
<asynchronous suspension>
#6      AppContext.run (package:flutter_tools/src/base/context.dart:149:12)
<asynchronous suspension>
#7      CommandRunner.runCommand (package:args/command_runner.dart:197:13)
<asynchronous suspension>
#8      FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:264:9)
<asynchronous suspension>
#9      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
<asynchronous suspension>
#10     AppContext.run (package:flutter_tools/src/base/context.dart:149:12)
<asynchronous suspension>
#11     FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:220:5)
<asynchronous suspension>
#12     run.<anonymous closure>.<anonymous closure> (package:flutter_tools/runner.dart:63:9)
<asynchronous suspension>
#13     run.<anonymous closure> (package:flutter_tools/runner.dart:61:12)
<asynchronous suspension>

[✓] Flutter (Channel master, 1.24.0-8.0.pre.374, on Microsoft Windows [Version 10.0.17763.1577], locale zh-CN)
    • Flutter version 1.24.0-8.0.pre.374 at D:\软件\flutter_windows_v1.2.1-stable\flutter
    • Framework revision 183f0e797a (4 days ago), 2020-11-26 19:12:28 +0100
    • Engine revision 20caf54969
    • Dart version 2.12.0 (build 2.12.0-76.0.dev)
    • Pub download mirror https://pub.flutter-io.cn
    • Flutter download mirror https://storage.flutter-io.cn

[!] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    • Android SDK at C:\Users\yannanna\AppData\Local\Android\Sdk
    • Platform android-29, build-tools 29.0.2
    • ANDROID_HOME = C:\Users\yannanna\AppData\Local\Android\Sdk
    • ANDROID_SDK_ROOT = C:\Users\yannanna\AppData\Local\Android\Sdk
    • Java binary at: D:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b03)
    ! Some Android licenses not accepted.  To resolve this, run: flutter doctor --android-licenses

[✓] Android Studio (version 3.5)
    • Android Studio at D:\Program Files\Android\Android Studio
    • Flutter plugin version 39.0.3
    • Dart plugin version 191.8423
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b03)

[✓] VS Code (version 1.35.1)
    • VS Code at C:\Users\yannanna\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.4.1

[!] Connected device
    ! No devices available

! Doctor found issues in 2 categories.

Flutter Application Metadata
Type: app
Version: 1.1.4+15
Material: true
Android X: false
Module: false
Plugin: false
Android package: null
iOS bundle identifier: null
Creation channel: stable
Creation framework version: 7a4c33425ddd78c54aba07d86f3f9a4a0051769b

Hi @yannanna0920
Are you using build_runner or any package that depends on it?
https://github.com/dart-lang/build/issues/2569

@yannanna0920  unless you are planning to contribute a PR to flutter, you should not ever run that command - it can break your SDK. To update the dependencies of your package use flutter pub get.

Duplicate of https://github.com/flutter/flutter/issues/71876

@ yannanna0920 除非您打算为PR做出贡献，否则永远不要运行该命令-它会破坏您的SDK。要更新软件包的依赖关系，请使用flutter pub get。

Update path error resolved. Thank you

but still, I am getting this error:
Because every version of flutter_localizations from sdk depends on intl 0.17.0-nullsafety.2 and intl_translation >=0.17.7 depends on intl >=0.15.3 <0.17.0, flutter_localizations from sdk is incompatible with intl_translation >=0.17.7.
Because intl_utils >=1.6.3 <1.9.0 depends on intl_translation 0.17.10 and intl_utils >=1.9.0 depends on intl_translation 0.17.10+1, intl_utils >=1.6.3 requires intl_translation 0.17.10 or 0.17.10+1.
Thus, flutter_localizations from sdk is incompatible with intl_utils >=1.6.3.
So, because food_delivery_app depends on both flutter_localizations any from sdk and intl_utils ^1.8.0, version solving failed.
pub get failed (1; So, because food_delivery_app depends on both flutter_localizations any from sdk and intl_utils ^1.8.0, version solving failed.)

@digitpk This issue is closed, and it looks like you are having a different problem. Please file a new issue with full details.


[diagnostics] Emit a a note for optional conversion of raw pointers.

In CSDiag.cpp I previously added a helper, isCastToTypedPointer(), to emit an
diagnostics explaining how to migrate UnsafeRawPointer conversion. This commit
broadens that diagnostic to handle Optional.
rdar:27894255 [3.0 migration] Emit an additional note for conversion

@swift-ci smoke test.


Feature: Length of Title 7-13 words

Length of Title 7-13 words
Titles play an essential role in capturing the overall meaning of a paper. Previously published work investigating this question agrees that the title length can impact citation rates.
Pseudocode:

Reference:
https://www.natureindex.com/news-blog/five-features-highly-cited-scientific-article

Entire dataset:

Scatterplot:

Pearson r: (-0.0628756568735512, 5.097976127340466e-08)


reset error when submitting

📝 Description
when getting an error for first time, we need to clear the error when we want to submit again
🎥 Demo

Please add a video or an image of the behavior/changes

/lgtm

/retest


When inputs is used, turbo can't detect file content changes.

What version of Turborepo are you using?
1.2.9
What package manager are you using / does the bug impact?
pnpm
What operating system are you using?
Mac
Describe the Bug
When inputs is specified, the task will only rerun if it is your first change or you commit your change. If you change your file content again, the task will reuse cache and produce stale outputs.
Expected Behavior
turbo should always rerun the task if file content is changed.
To Reproduce

Create a turborepo

npx create-turbo

Add inputs to turbo.json

{
  "pipeline": {
    "build": {
      "dependsOn": [
        "^build"
      ],
      "outputs": [
        "dist/**",
        ".next/**"
      ],
      "inputs": [
        "pages/**",
        "next.config.js",
        "package.json",
        "tsconfig.json"
      ]
    },
    "lint": {
      "outputs": []
    },
    "dev": {
      "cache": false
    }
  }

Init git and commit changes.
Change /apps/web/pages/index.tsx

add console.log('123'). turbo could detect this change and rebuild
change file to console.log('456'). turbo couldn't detect this.

Thanks for the heads up, I'll take a look at this today.

i just noticed that the issue still occurs for me:
	"typedoc": {
			"cache": true,
			"inputs": ["src/**/*"],
			"outputs": ["documentation/**/*"]
		},

pnpm version: 7.2.1
turbo 1.3.1
when i am changing something (content of log, adding a function, ...) it replays the output from the cache.
any ideas what i am doing wrong?

I am using the latest v1.3.4 and am having this exact same problem.
Please re-open this issue.

@aiji42 @alexn-s
The actuall is problem here https://github.com/vercel/turborepo/issues/1241#issuecomment-1128145268
The latest version of turborepo can detect change now but you have to specify input "correctly".

@promer94 thank you. never would have looked for globs beeing the reason

@promer94
I don't use globbing and specify a single file as inputs.
{
  "$schema": "https://turborepo.org/schema.json",
  "baseBranch": "origin/main",
  "pipeline": {
    "prisma:generate": {
      "inputs": ["prisma/schema.prisma"],
      "outputs": ["node_modules/@generated/type-graphql/**", "node_modules/.prisma/**"]
    },

In this case, when that file is modified, a rerun is expected, but in fact it is restored from the cache and the changes are ignored.
If I don't specify inputss, it works as expected, but I only want to monitor one specific file for changes.
Is it not possible to specify a single file with its full path?

@promer94 I don't use globbing and specify a single file as inputs.
{
  "$schema": "https://turborepo.org/schema.json",
  "baseBranch": "origin/main",
  "pipeline": {
    "prisma:generate": {
      "inputs": ["prisma/schema.prisma"],
      "outputs": ["node_modules/@generated/type-graphql/**", "node_modules/.prisma/**"]
    },

In this case, when that file is modified, a rerun is expected, but in fact it is restored from the cache and the changes are ignored. If I don't specify inputs, it works as expected, but I only want to monitor one specific file for changes. Is it not possible to specify a single file with its full path?
[edited] I noticed this problem only in docker containers. Please disregard my question for the moment as it may be due to another issue.

I have also encountered this problem. Have you solved it?


Handling two recaptchas on same page

I'm having problems finding a solution for two recaptchas that are in two different components in the same page and have different methods runnig for their emitted onSuccess events.
If I run this.$recaptcha.getResponse() on any of them because of a form submit the onSuccess emitted event will run both of the AJAX in both of the components.
I tried using ref in each one of them, but I can't find a way to run the getResponse() so I dont have to call this.$recaptcha.getResponse() and instead call it like this.$refs.componentOneRecaptcha.getResponse() but it wont run at that level because there's no getResponse(). Is there any other smarter way to do this?

Did you find any workaround? I'm facing issues loading a V3 reCaptcha instance and a V2 in case V3 fails, I'm not able to load the second one.

Did you find any workaround? I'm facing issues loading a V3 reCaptcha instance and a V2 in case V3 fails, I'm not able to load the second one.

Did you find any workaround? I'm facing issues loading a V3 reCaptcha instance and a V2 in case V3 fails, I'm not able to load the second one.

Not yet :(

Did you find any workaround? I'm facing issues loading a V3 reCaptcha instance and a V2 in case V3 fails, I'm not able to load the second one.

Not yet :(

Finally I managed to solve it. I found it useless to place 2 recaptchas on the same page, instead I proposed to use V2 as fallback of V3. Or otherwise, if you want to prioritize the V2 functionality over the V3.
If one fails, you can override the recaptcha options accessing window.$nuxt.$recaptcha object, and there update the new values:
try {
      // captcha V3
      await window.$nuxt.$recaptcha.execute("login");
}
catch(e) {
      // trying V2
      window.$nuxt.$recaptcha.siteKey = process.env.RECAPTCHA_SITE_KEY_V2;
      window.$nuxt.$recaptcha.version = 2;
      window.$nuxt.$recaptcha.hideBadge = true;

      try {
            await window.$nuxt.$recaptcha.getResponse();
      }
      catch(e) {
            // both failed :(
      }
}

Hope it helps!

Finally I managed to solve it. I found it useless to place 2 recaptchas on the same page, instead I proposed to use V2 as fallback of V3. Or otherwise, if you want to prioritize the V2 functionality over the V3.
If one fails, you can override the recaptcha options accessing window.$nuxt.$recaptcha object, and there update the new values:
try {
      // captcha V3
      await window.$nuxt.$recaptcha.execute("login");
}
catch(e) {
      // trying V2
      window.$nuxt.$recaptcha.siteKey = process.env.RECAPTCHA_SITE_KEY_V2;
      window.$nuxt.$recaptcha.version = 2;
      window.$nuxt.$recaptcha.hideBadge = true;

      try {
            await window.$nuxt.$recaptcha.getResponse();
      }
      catch(e) {
            // both failed :(
      }
}

Hope it helps!

@joelfloressottile take a look at https://github.com/nuxt-community/recaptcha-module/pull/70, this PR enables switching the plugin configuration in runtime, so instead of having two instances of the same plugin, you could switch from one plugin settings to another, whenever you need it.

@joelfloressottile take a look at https://github.com/nuxt-community/recaptcha-module/pull/70, this PR enables switching the plugin configuration in runtime, so instead of having two instances of the same plugin, you could switch from one plugin settings to another, whenever you need it.

@joelfloressottile take a look at #70, this PR enables switching the plugin configuration in runtime, so instead of having two instances of the same plugin, you could switch from one plugin settings to another, whenever you need it.

I'll take a look. Thanks!

@joelfloressottile take a look at #70, this PR enables switching the plugin configuration in runtime, so instead of having two instances of the same plugin, you could switch from one plugin settings to another, whenever you need it.

I'll take a look. Thanks!


Colorama dependency

Hi Peter,
during checking the pip dependencies of EMBA on the new Kali Linux I found a conflicting dependency on colorama:
Warning!!! Possibly conflicting dependencies found:
* stacs==0.4.14
 - colorama [required: ==0.4.5, installed: 0.4.6]

Would it be possible to update the colorama dependency to 0.4.6 or is there a reason to stick on 0.4.5?
Best
Mike

Hey @m-1-k-3 ,
Good catch! I'll relax these pins to allow updates within the same major version for all dependencies. This should be published as part of 0.4.15 shortly.

Thank you very much ...

Release has been tagged, build should be available on PyPi within the next 30 minutes :)
https://github.com/stacscan/stacs/releases/tag/0.4.15
Thanks again for the report!


DRAFT: IBC Lite Implementation

Description

closes: #XXXX

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[ ] Targeted PR against the correct branch (see CONTRIBUTING.md).
[ ] Linked to GitHub issue with discussion and accepted design, OR link to spec that describes this work.
[ ] Code follows the module structure standards and Go style guide.
[ ] Wrote unit and integration tests.
[ ] Updated relevant documentation (docs/).
[ ] Added relevant godoc comments.
[ ] Provide a conventional commit message to follow the repository standards.
[ ] Include a descriptive changelog entry when appropriate. This may be left to the discretion of the PR reviewers. (e.g. chores should be omitted from changelog)
[ ] Re-reviewed Files changed in the GitHub PR explorer.
[ ] Review SonarCloud Report in the comment section below once CI passes.

Summary by CodeRabbit

New Features

Introduced support for sending and receiving packets over IBC channels.
Added methods for packet transmission, verification, and application logic.
Implemented LiteClientModule interface for counterparty information retrieval and membership verification.
Introduced LitePacketHandler interface for handling packet events.

Refactor

Moved RecvPacket, Acknowledgement, and Timeout methods to a new PacketMsg service in the IBC channel protocol.

Enhancements

Added function to compute hash for Packet struct properties.

Should we close this pr now since the feature branch has changed?


Can't sign in even user is valid

I tried to execute mutation
mutation signIn($email: AUTH_PROVIDER_EMAIL) {
  signinUser(email: $email) {
    token
  }
}

With this input
{
  "email": {
    "email"<EMAIL_ADDRESS>
  	"password": "$2a$10$2FS0b/VUibIDyfDu5ao5KOc26xFvgV/rcBaapAq1W8VC0xFuinC7e"
  }
}

But I always got response
{
  "data": null,
  "errors": [
    {
      "locations": [
        {
          "line": 33,
          "column": 3
        }
      ],
      "path": [
        "signinUser"
      ],
      "code": 3022,
      "message": "No user found with that information",
      "requestId": "eu-west-1:simple:ck2cqd1h903xf01881yhgg44j"
    }
  ]
}

Do I miss anything else?

Sorry, @ningo-agilityio, but you probably wrote this issue in the wrong repository. graphiql-online is just a tool, there is no API such as you mentioned implemented on it - perhaps you were looking at some fork, or something?


Specify "to_bytes" and "from_bytes"

In https://github.com/ethereum/eth2.0-specs/blob/v0.8.3/specs/core/0_beacon-chain.md#int_to_bytes
The int_to_bytes and bytes_to_int depend on Python implementation of to_bytes
def int_to_bytes(n: uint64, length: uint64) -> bytes:
    """
    Return the ``length``-byte serialization of ``n``.
    """
    return n.to_bytes(length, ENDIANNESS)

A description of what this method does should be added so that we don't have to look into the Python spec.

I'll handle this in the dev branch. Seems reasonable to add another line to the header comment to clarify

Fixed in #1401


Pattern matching like seneca?

Does Côte allow pattern matching events+payload of some sorts?
in seneca you can define services as such

//first service
seneca.add({cmd: 'salestax', country: 'US'}, handler)

// other service
seneca.add({cmd: 'salestax', country: 'DE'}, handler)

// client
seneca.act('cmd:salestax,net:100,country:DE', function (err, result) {
  console.log('DE: ' + result.total)
})
seneca.act('cmd:salestax,net:100,country:US,state:NY', function (err, result) {
  console.log('US,NY: ' + result.total)
})

It allows some nice decoupling, I was wondering how one would achieve such behavior in Côte?

I think pattern matching approach like this creates more ambiguity than it brings any real world benefit when it comes to scaling out the number of services.
cote doesn't support any pattern matching, however, you can use keys to achieve a similar result.
I think pattern matching approach like this creates more ambiguity than it brings any real world benefit when it comes to scaling out the number of services.
cote doesn't support any pattern matching, however, you can use keys to achieve a similar result.
salestax-us-service.js
const cote = require('cote')
const responder = new cote.Responder({ name: 'salestax-us responder', key: 'salestax-us' })
responder.on('salestax', handler)

salestax-de-service.js
const cote = require('cote')
const responder = new cote.Responder({ name: 'salestax-de responder', key: 'salestax-de' })
responder.on('salestax', handler)

client.js
const cote = require('cote')
const usRequester = new cote.Requester({ name: 'salestax-us client', key: 'salestax-us' })
const deRequester = new cote.Requester({ name: 'salestax-de client', key: 'salestax-de' })

const res1 = await deRequester.send({ type: 'salestax', net: 100 })
console.log(`DE: ${res.total}`)

const res2 = await usRequester.send({ type: 'salestax', net: 100, state: 'NY' })
console.log(`US,NY: ${res.total}`)

Thank you for your quick and detailed answer.
I'm not really convinced this solution scales as you would need to introduce as many responders as you would want to extend yours features. It also mean go back and modifying the client service each time you introduce a new service, which defeats decoupling.
Thanks for your time.


[Release-1.21] Node stuck at deletion due to finalizer - regression

Environmental Info:
K3s Version:

Node(s) CPU architecture, OS, and Version:

All types
Cluster Configuration:

Describe the bug:

Issue
Deletion of node is stuck due to presence of finalizer. This seems to be a regression
Steps to reproduce

Create a 3 node cluster
Verify nodes are Ready and pods are Running
Delete node3 using kubectl delete node
Deletion of a node is stuck, unless finalizer is removed.

--
    finalizers:
    - wrangler.cattle.io/managed-etcd-controller
    - wrangler.cattle.io/node
    labels:
--
          f:finalizers:
            .: {}
            v:"wrangler.cattle.io/managed-etcd-controller": {}
            v:"wrangler.cattle.io/node": {}

Expected behavior:
For node to be deleted
Actual behavior:
Node gets stuck

Validated using v1.21.4-rc1+k3s1
As this was an intermittent issue, I confirmed I could delete a node on 8 different clusters. None of them got stuck.


Search for attribute fails on elements missing the parameter

Setting parameter attribute to title or alt fails when there are elements with without the parameter.

Uncaught TypeError: Cannot read property 'toLowerCase' of undefined

Cause should be this line: https://github.com/vdw/HideSeek/blob/master/jquery.hideseek.js#L82

Hi,
just to note that by setting a custom attribute to configuration means that the html structure complies with that attribute, meaning if your custom attribute is the "alt" then the list items should have that attribute, otherwise the html structure is invalid.
Also, HideSeek can handle, without errors the empty attributes, but not the missing ones.
Anyway, I would really like to merge your request if you explain to me the situation where you have list items without the required attributes in order to evaluate the need of that request.
Thank you,
d

Hi Dimitris,
my short answer is: The search shouldn't break on missing optional arguments.
What I have in mind searching a whole document with different structure for sparse set values. Even if that is not the point of the library it's working great with text. I think the search wouldn't work with all children with the alt-attribute either but that's another point.
Even if your example is a well ordered list I wouldn't force the user to set empty values if there are only 5 of 1000 items with value.
On the other side I see your point with the structure having to fit the config. Even if I prefer to make the search more robust, I would throw more meaningful error messages in this case.
Have a nice day ;)

Hello Andy,
I understand that you have data that you can not "control", but generally speaking, as long as you are using a plugin, library or even a framework I believe that you have to conform to the requirements otherwise you get an error or wrong results (the error is preferable).
Anyway, your pull request is welcome and merged.
Thank you for your contribution,
d


android roadmap

Hello @godrm
Nice roadmap, I like it. thanks
would be any suggestion for android development?

i hope you make android development roadmap.

Also waiting for the two missing roadomap. Thanks


feat: updated the core structure of the github workflow file

Tasks description
Issues
Completed Issue(s)

Fixes #320

Related Issue(s)

Closes #317

Solution
Sub-Tasks

[ ] milestones or sub-task which needs to be coverted

Note to reviewers

[ ] Ran Tests locally
[ ] Checked Contribution's guidelines

need to get the path filtering


RAILS_ROOT error

When I try to do sms_fu.deliver on the rails console, I get the follow error:
"NameError: uninitialized constant RAILS_ROOT"
After checking around, it seems that RAILS_ROOT was deprecated to Rails_root but that change is already present in the master code on Github so I'm not sure why I'm still getting that error.

+1 same for me.


Simplify shell code path handling.

Codecov Report
Base: 23.67% // Head: 23.67% // No change to project coverage :thumbsup:

Coverage data is based on head (233ba0b) compared to base (2be5b5f).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##           stable     #451   +/-   ##
=======================================
  Coverage   23.67%   23.67%
=======================================
  Files          63       63
  Lines        5754     5754
  Branches      312      312
=======================================
  Hits         1362     1362
  Misses       4343     4343
  Partials       49       49

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


[Kafka source] Fix code formatting and Kinesis source

Description
Per title.
How was this PR tested?
make fmt
cargo build --all-features
make test-all

Actually, make test-all seems to be broken, at least for me t_t


bazel build fail

tag: v1.24.1
bazel build //source/exe:envoy-static -c dbg
DEBUG: Rule 'python3_10_x86_64-unknown-linux-gnu' indicated that a canonical reproducible form can be obtained by dropping arguments ["ignore_root_user_error"]
DEBUG: Repository python3_10_x86_64-unknown-linux-gnu instantiated at:
/usr/local/istio/envoy/v1.24.1/WORKSPACE:17:25: in
/usr/local/istio/envoy/v1.24.1/bazel/repositories_extra.bzl:17:31: in envoy_dependencies_extra
/root/.cache/bazel/_bazel_root/bb32e65b81b35253e03db1ebd8d556e6/external/rules_python/python/repositories.bzl:366:26: in python_register_toolchains
Repository rule python_repository defined at:
/root/.cache/bazel/_bazel_root/bb32e65b81b35253e03db1ebd8d556e6/external/rules_python/python/repositories.bzl:269:36: in
WARNING: Download from https://golang.org/dl/?mode=json&include=all failed: class java.io.IOException connect timed out
ERROR: /usr/local/istio/envoy/v1.24.1/source/common/common/BUILD:527:18: in cc_library rule //source/common/common:common_pch_libs: target '//bazel:disable_hot_restart_setting' is not visible from target '//source/common/common:common_pch_libs'. Check the visibility declaration of the former target if you think the dependency is legitimate
ERROR: /usr/local/istio/envoy/v1.24.1/source/common/common/BUILD:527:18: Analysis of target '//source/common/common:common_pch_libs' failed
ERROR: Analysis of target '//source/exe:envoy-static' failed; build aborted:
INFO: Elapsed time: 21.903s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (62 packages loaded, 1561 targets configured)

@Webster-Yang you were given a response regarding possible reasons for this on your original ticket (https://github.com/envoyproxy/envoy/issues/24464#issuecomment-1344271860)
please focus any discussion there


Tests runs outside of container

I have something like this in my
run:
  test: 'bash lib/some_script.bash && npm test'

And it makes run  npm test  at host, not at container

@nike-17 does this work?
run:
  test: 'bash -xc "lib/some_script.bash && npm test"'


logging: examples for every major function

Provide an example for every major function or method.

Fixed by ad5712971bbdaf7fdc85f9b6ab1bce82eadc9119.


Add confidence intervals to unwinding errors column

Also this adds the tooltip for the said column.
Tests: Unit tests
Bug: http://b/224757836

http://screenshot/ByctrdpKQKm2qzk

Everything else looks good.


Modifier Behavior

I'm playing around with changing styles in app and noticed the following behavior:
[<Extension>]
type MyExtensions =
    [<Extension>]
    static member inline firstStyle(this: WidgetBuilder<'msg, #IVisualElement>) =
          this.verticalOptions(LayoutOptions.Start)
              .horizontalOptions(LayoutOptions.Start)
              .backgroundColor(Color.Blue.ToFabColor())
              .margin(30.)

    [<Extension>]
    static member inline secondStyle(this: WidgetBuilder<'msg, #IVisualElement>) =
              this.margin(60.)

    [<Extension>]
    static member inline myStyle(this: WidgetBuilder<'msg, #IVisualElement>, styleID)=
        match styleID with
        | 1 -> match box this with
                | :? WidgetBuilder<'msg, IButton> ->
                    this.firstStyle()
                        .secondStyle()
                | _ -> this
        | 2 -> match box this with
                | :? WidgetBuilder<'msg, IButton> ->
                    this.verticalOptions(LayoutOptions.Start)
                        .horizontalOptions(LayoutOptions.Start)
                        .margin(80.)
                        .backgroundColor(Color.Green.ToFabColor())
                | _ ->
                    printfn "no valid IView found. Fall back to normal style"
                    this
        | _ ->
            printfn "no valid StyleID selected. Fall back to normal style"
            this

If I run the code like this, the button will show a margin of 60. when set to styleID 1 (so far so good). However, if  set to styleID 2, the margin is set to 0. (instead of the wished for 80.). All other properties (color, layoutOptions) show up correctly.
The same behavior applies to other properties (e.g. color).
This can easily be fixed by removing margin(30.) from firstStyle.
(https://github.com/reigam/Fab2Demo/tree/Implement_Styles)
P.s.: I realize that it probably is bad practice to set the same property twice (I wanted to see what happens, if I overwrite something) . I only bring this up, because the "buggy(?)" behavior shows up further down the line, and not with the property itself.

match box this with
| :? WidgetBuilder<'msg, IButton> ->

Quick question, why are you testing the type here?
If your style only applies to Button, you can directly write myStyle(this: WidgetBuilder<'msg, #IButton>, styleID)

I realize that it probably is bad practice to set the same property twice (I wanted to see what happens, if I overwrite something)

Yes, the new DSL was not done with setting a same property multiple times in mind. It will simply keep all values for the same property and apply them one after the other and replace the old value. But Fabulous doesn't guarantee the order of applying, so the result could be inconsistent.
It's a current shortcoming of the DSL.
A fix could be done, but we need to check the cost of overwriting existing values.
@twop How can we handle that?
I guess doing a lookup on each AddScalar would not be great. Maybe we can do a "deduplicate" pass on all attributes during Widget.Compile?

Quick question, why are you testing the type here? If your style only applies to Button, you can directly write myStyle(this: WidgetBuilder<'msg, #IButton>, styleID)

I shortened the code. The original plan was more like this:
        | 1 -> match box this with
                | :? WidgetBuilder<'msg, IButton> ->
                    this.firstStyleSharedProperties()
                        .firstStyleButtonSpecificProperties
                | :? WidgetBuilder<'msg, ILabel> ->
                    this.firstStyleSharedProperties()
                        .firstStyleLabelSpecificProperties
                | :? WidgetBuilder<'msg, IEntry> ->
                    this.firstStyleSharedProperties()
                        .firstStyleEntrySpecificProperties
                .....
                | _ -> this

There are probably better ways to go about this. I'm just playing around with the concept.

It's a current shortcoming of the DSL.
A fix could be done, but we need to check the cost of overwriting existing values.

Ok. Seems easy enough to avoid.

I guess doing a lookup on each AddScalar would not be great. Maybe we can do a deduplication pass on all attributes during Widget.Compile?

This is going to be on the hot path. However we can take the latest value in the diffing algorithm. It will slow down diffing but I assume not by much.
We can peek at the next attribute to see if it has the same key, if it does then just skip the current one and select the latest.
I can probably make it work in an evening, I was planning to do that initially but there were other "more important" things to tackle at the time :)

We can peek at the next attribute to see if it has the same key, if it does then just skip the current one and select the latest.

That would work because we keep the order of declaration (even with StackList) and sort by key, right?

right, and the sort is stable, meaning it preserves the order of elements with the same key

We now only keep the latest modifier value in case the same modifier is applied several times


What NMDC resources depend on the nmdc-schema?

When changes are made to the nmdc-schema, what systems could be broken?

And who should be notified?
Note: all breaking nmdc-schema changes require adding migration code to migration_recursion.py
@Shalsh23 @eecavanna please update or link this issue as you see fit

any workflow code
the nmdc-runtime

more?

When changes are made to the nmdc-schema, what systems could be broken?

nmdc-runtime is dependent upon the nmdc-schema Python package hosted on PyPI.
When a new version of that package is published to PyPI, nmdc-runtime doesn't automatically pull it. Instead, a developer of nmdc-runtime will—at some point—manually update that repo's requirements/main.in file (link) to reference the new version. Then, the next time the container images for nmdc-runtime are built, they will download and install that version of the nmdc-schema package from PyPI.

I have some ideas of things I think would make it so stakeholders can be promptly informed of when a new version of the nmdc-schema package gets published.

When you create a Release on GitHub, announce it on Slack (we could create a #releases channel)
Configure GitHub to automatically post something on Slack (we could create a #releases-bot channel) when a Release is created
Implement a Google Apps Script that polls the GitHub repository's Releases list and posts something on Slack when it notices a new Release
Same as (1), but for the PyPI page (or JSON/XML representation) of nmdc-schema
Same as (3), but for the PyPI page (or JSON/XML representation) of nmdc-schema


[YBUG.IO] Why is liquality not available?

Why is liquality not available?
Source url: https://live.sovryn.app/
Reported by:
Reported at: 14 Apr at 23:37 UTC
Location: US, Florida, Santa Rosa Beach
Browser: Chrome 89.0.4389.72
OS: macOS 11.1.0
Screen: 1440x900
Viewport: 1440x821
Screenshot:

For more details please visit report page on Ybug:
https://ybug.io/dashboard/reports/detail/nmfjs1vbq4stpxcnd8cq

It's disabled because it's not installed / enabled in the browser.


execute bazel build --config=darwin heron/... error

Hi guys!
I execute bazel build --config=darwin heron/... command error
INFO: From Building heron/spi/tests/java/network-utils_unittest.jar (1 files):
heron/spi/tests/java/com/twitter/heron/spi/common/NetworkUtilsTest.java:41: 错误: 无法访问AbstractCommonPowerMockRunner
@RunWith(PowerMockRunner.class)
^
找不到org.powermock.modules.junit4.common.internal.impl.AbstractCommonPowerMockRunner的类文件
heron/spi/tests/java/com/twitter/heron/spi/common/NetworkUtilsTest.java:216: 错误: 无法访问MemberModifier
PowerMockito.spy(NetworkUtils.class);
^
找不到org.powermock.api.support.membermodification.MemberModifier的类文件
2 个错误
BazelJavaBuilder threw exception: java compilation returned status ERROR
ERROR: /Users/jonathanwei/summary/GITRepository/heron/heron/spi/tests/java/BUILD:47:1: Java compilation in rule '//heron/spi/tests/java:network-utils_unittest' failed: java failed: error executing command external/local-jdk/bin/java -Xbootclasspath/p:external/bazel_tools/third_party/java/jdk/langtools/javac.jar -client -jar external/bazel_tools/tools/jdk/JavaBuilder_deploy.jar ... (remaining 1 argument(s) skipped): com.google.devtools.build.lib.shell.BadExitStatusException: Process exited with status 1.

Execute bazel build --config=darwin heron/... --verbose_failures command :
INFO: From Building heron/spi/tests/java/network-utils_unittest.jar (1 files):
heron/spi/tests/java/com/twitter/heron/spi/common/NetworkUtilsTest.java:41: 错误: 无法访问AbstractCommonPowerMockRunner
@RunWith(PowerMockRunner.class)
^
找不到org.powermock.modules.junit4.common.internal.impl.AbstractCommonPowerMockRunner的类文件
heron/spi/tests/java/com/twitter/heron/spi/common/NetworkUtilsTest.java:216: 错误: 无法访问MemberModifier
PowerMockito.spy(NetworkUtils.class);
^
找不到org.powermock.api.support.membermodification.MemberModifier的类文件
2 个错误
BazelJavaBuilder threw exception: java compilation returned status ERROR
ERROR: /Users/jonathanwei/summary/GITRepository/heron/heron/spi/tests/java/BUILD:47:1: Java compilation in rule '//heron/spi/tests/java:network-utils_unittest' failed: java failed: error executing command
(cd /private/var/tmp/_bazel_jonathanwei/f0e0d1fb1f89f02c31d3facf1d735668/heron &&
exec env -
external/local-jdk/bin/java -Xbootclasspath/p:external/bazel_tools/third_party/java/jdk/langtools/javac.jar -client -jar external/bazel_tools/tools/jdk/JavaBuilder_deploy.jar @bazel-out/local_darwin-fastbuild/bin/heron/spi/tests/java/network-utils_unittest.jar-2.params): com.google.devtools.build.lib.shell.BadExitStatusException: Process exited with status 1: java failed: error executing command
(cd /private/var/tmp/_bazel_jonathanwei/f0e0d1fb1f89f02c31d3facf1d735668/heron &&
exec env -
external/local-jdk/bin/java -Xbootclasspath/p:external/bazel_tools/third_party/java/jdk/langtools/javac.jar -client -jar external/bazel_tools/tools/jdk/JavaBuilder_deploy.jar @bazel-out/local_darwin-fastbuild/bin/heron/spi/tests/java/network-utils_unittest.jar-2.params): com.google.devtools.build.lib.shell.BadExitStatusException: Process exited with status 1.
INFO: Elapsed time: 4.737s, Critical Path: 4.08s.

@Jonathan-Wei the powermock java library is missing.
Can you check the dir bazel-bin/3rdparty/java and see if any powermock jars in it? Like the following
[tw-mbp-nlu java]$ ls | grep powermock
libpowermock-ijar.jar
libpowermock.jar
libpowermock.jar-2.params
libpowermock.jar_manifest_proto
libpowermock.jdeps

@Jonathan-Wei
I got the same problem.
Following change can fix this issue.
diff --git a/3rdparty/java/BUILD b/3rdparty/java/BUILD
index a3a3688..e3250f4 100644
--- a/3rdparty/java/BUILD
+++ b/3rdparty/java/BUILD
@@ -99,8 +99,10 @@ java_library(
     srcs = [ "Empty.java" ],
     exports = [
         "@powermock-api-mockito//jar",
+       "@powermock-api-support//jar",
         "@powermock-core//jar",
         "@powermock-module-junit4//jar",
+       "@powermock-module-junit4-common//jar",
     ],
     deps = [
         "@powermock-api-mockito//jar",

Great find @zhangzhonglai. Would you mind submitting a patch?

@billonahill
Yes. I'll try to do this.But I've never done this before. If there is something wrong, please tell me.

3Q!@zhangzhonglai @billonahill
Build success!

Great, glad it's working @Jonathan-Wei. Thanks for the patch @zhangzhonglai.


Specifying empty params (e.g. clusterOptions in profile) breaks with nf-validation 0.3.1

When running one of  the pipelines using nf-validation with 0.3.1 and specifying the UPPMAX profile, it fails with an error:
pontus@lalage:/tmp$ nextflow run nf-core/atacseq -r 2.1.1 -profile uppmax
N E X T F L O W  ~  version 23.04.2
Launching `https://github.com/nf-core/atacseq` [nostalgic_euler] DSL2 - revision: 415795d3c1 [2.1.1]
ERROR ~ JSONObject["project"] not found.

 -- Check script '/home/pontus/.nextflow/assets/nf-core/atacseq/main.nf' at line: 52 or see '.nextflow.log' file for more details
pontus@lalage:/tmp$

after some digging, it seems to me this is because the profile sets that up in params, although with a null value.
It looks to me that is enough to have it seen by nf-validation, but when nf-validation tries to report it (https://github.com/nextflow-io/nf-validation/blob/01a3131ab7fb2e8cc9e2c60dc97ac978b89b17fb/plugins/nf-validation/src/main/nextflow/validation/SchemaValidator.groovy#L315) it's not found in paramsJSON because that's based on the cleaned version (https://github.com/nextflow-io/nf-validation/blob/01a3131ab7fb2e8cc9e2c60dc97ac978b89b17fb/plugins/nf-validation/src/main/nextflow/validation/SchemaValidator.groovy#L271) which has removed anything evaluating to false.
A workaround (that makes sense) for now is to ignore the affected param, but this seems to be a bug that can be difficult to figure out and would be nice to have fixed.

And upon rechecking, this is probably the same as #48.

Closing as hopefully solved in #89, which I just merged. Shout if that's not the case, and thanks for reporting @pontus 🙏🏻


Parameterise Loadshedding Stage in Schedule Call

I see you made a note to parameterise the stage in your api call to get the schedule.
Can you advsie when you will be doing this or what I can tweak in your nodered flow to enable this.

I think I have solved it by replacing the stage no in the get url to {{{stage}}}


[Gssoc'21 ]Finding roots of a quadratic equation  in Python

Have you read the Contributing Guidelines on Pull Requests?
YEs
Description
I have added  a python code for finding of quadratic equation all you have to do is to pass the values of
a,b,c  of the equation of the form (ax^2  bx + c )
Checklist

[x] I've read the contribution guidelines.
[x] I've checked the issue list before deciding what to submit.
[ ] I've edited the README.md and link to my code.

Related Issues or Pull Requests
Fixex or closes : #5975

@ankitaggarwal23 i had already deleted that extra file there is only one file related to this PR
please reopen this


BeforeNavigate not firing on Shallow routing

Describe the bug
When you navigate shallowly to a page beforeNavigate will not work when you navigate away
Reproduction
The repo has 2 links, one which uses normal navigation to go to /bob and one which uses shallow navigation
if you go to /bob normally and navigates back, you see an alert. however if you go there shallowly and back you do not.
https://www.sveltelab.dev/6kwef9i2beei35f?login=true&files=.%2Fsrc%2Froutes%2F%2Bpage.svelte%2C.%2Fsrc%2Flib%2Fshallow.svelte%2C.%2Fsrc%2Froutes%2Fbob%2F%2Bpage.svelte
Logs
No logs relevant

System Info
Here is my output, but i think this is reproducible everywhere

  System:
    OS: macOS 15.0.1
    CPU: (10) arm64 Apple M1 Pro
    Memory: 443.39 MB / 32.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.13.0 - ~/.nvm/versions/node/v20.13.0/bin/node
    npm: 10.5.2 - ~/.nvm/versions/node/v20.13.0/bin/npm
    pnpm: 9.4.0 - ~/.nvm/versions/node/v20.13.0/bin/pnpm
  Browsers:
    Chrome: 130.0.6723.92
    Safari: 18.0.1
  npmPackages:
    @sveltejs/adapter-vercel: ^5.4.3 => 5.4.5
    @sveltejs/kit: ^2.7.3 => 2.6.4
    @sveltejs/vite-plugin-svelte: ^3.1.2 => 3.1.2
    svelte: ^4.2.17 => 4.2.19
    vite: ^5.4.6 => 5.4.6

Severity
annoyance  - with no viable workaround
Additional Information
In my concrete case we use shallow routing for forms within modals, and normally when you taint a form and tries to navigate away, we stop you to make sure you do not throw away your changes. However this breaks when navigating shallowly.
As far as i could tell the only workaround would be something like the following
<svelte:window
    on:popstate={(e) => {
        if (form_is_tainted) {
            history.pushState(null, '', window.location.href);
        }
    }} />

But this is discouraged because this conflicts with svelte kit router

Duplicate of #11776.


Simplify static error lookup code with macros

Issue # (if available):
Follow up on https://github.com/awslabs/s2n/pull/1276#issuecomment-557683999 in an attempt to DRY with less code.
Description of changes:
ERR_ENTRIES is a macro that takes another macro that unwraps it's entries (almost functional style).
I think it is also possible to push it one step further and use ERR_ENTRIES to build the enum entries in s2n_errno.h
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

:exclamation: No coverage uploaded for pull request head (simply_static_error_lookup@190369a). Click here to learn what that means.
The diff coverage is n/a.


[fix] use echo instead of node -e

It will fix install issues with yarn berry (v2)
Currently install is broken on yarn berry due to an error with node -e.
# This file contains the result of Yarn building a package (swiper@npm:5.2.0)
# Script name: postinstall

[eval]:1
console.log('u001b[35mu001b[1mLove Swiper? Support Vladimir's work by donating or pledging on patreon:u001b[22mu001b[39mn > u001b[32mhttps://patreon.com/vladimirkharlampidiu001b[0mn')
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

SyntaxError: missing ) after argument list
    at new Script (vm.js:86:7)
    at createScript (vm.js:268:10)
    at Object.runInThisContext (vm.js:316:10)
    at Object.<anonymous> ([eval]-wrapper:9:26)
    at Module._compile (internal/modules/cjs/loader.js:945:30)
    at evalScript (internal/process/execution.js:80:25)
    at internal/main/eval_string.js:23:3

Use echo instead of node is a better choice because you are not dependant of node eval implementation. It also fix the issue.
Result :

Does echo work correctly on Windows?

Created a little github action to test it and I can confirm that it works :)

Thanks!


Enhance CI

After #8, this became a command line tool shipping in the form of a Python package. This allowed us to:

Take advantage of documentation.

Move the use cookiecutter to the backstage so users forget about this tool.

Begin able to host multiple any kind of template: Python package, Fortran project...

[x] CI parametrization

This project is expected to growth, so the CI pipelines should be as much parametrized as possible. This will allow to easily modify workflows in the future. At the moment, although slightly parametrized, the last steps of the CI look like this:
https://github.com/pyansys/pyansys-template/blob/6aa45bff18c31bcfc1ff35b11bb686c141d32b15/.github/workflows/ci.yml#L99-L148
Notice that most of the logic is duplicated here. I'm pretty sure this can be simplified taking advantage of the include directive and declaring custom environment variables for each one of the matrix.build-system.

[x] Include coverage

Including code coverage is a "must have" in this project if we want to make sure that the ansys-templates CLI tool and the different available templates bake properly.

Code coverage was introduced in #18. In addition, the CI was parametrized again by splitting smoke and templates tests. Closing this...


add Application protection job duration in SPPMON Dashboard

Feature request : in  Grafana dashboard, under the protection job section there is no details on Protection job duration for MS-SQL jobs , although we have it for VM and DB2  .. is it possible to get it ?  same for other workload as well ( openshift , oracle , ...  )
Alternative would be a documentation section explaining how to build our own dashboards from the data you are collecting . I'd be happy to work with you to develop this.

Hello @daytoju,
I'm currently out of the office and will respond to any further questions at a later notice after 21.09.
You may easily add these panels as you wish, as long as it only uses existing data (check the "all job executions"-panel).
All job executions are collected, as they are available via the SPP catalog.
Steps to do so:

Find the VM backup or db2 panel in the section
Go on the dots/menu of the panel and select duplicate
in the new panel, go on edit
The job name is selected in the query, SQL style. You may change the selection to the job name of the ms-SQL job:

Please check the other panels for different values of the selection to get an idea of how it is selected
Grafana should, but not always does, provide a drop-down of existing values. You may check the "all job executions panel" for your required job-name value.
You may also use regex to select all jobs with a given prefix. A Regex requires slashes / before and after and the ~=sign set in the Grafana query. Please check the other queries; I think vm-jobs use a prefix.

if available, feel free to press the "migrate to new version" button on the right-hand side.
Move your query to a location of your desire; you may also re-size it.

Important note:
Once a new dashboard version is released, and you import it, your changes might be lost.
There is no routine for this process yet, but you can:

write down your changes to easily replicate them
Make the panel a library panel via the menu. This way, you might be able to retain it once the dashboard is overwritten. This process is untested!
Open a pull request to supply your newly changed dashboard as the new official version.

Another context:
SPPMon also tracks and shows MySQL backup data; however, as of Issue #76 , this data is disabled for normal execution, and the panel within Grafana is empty.
Please use the --fullLogs'flag on the --dailyand--all` execution to track these data again.
Be aware that more errors might occur during execution; however, they should (usually) not affect the data you're worried about.

Also, I'm up for writing another wiki page, I though I'd already added one about this topic, but it doesn't look like it.
However, my master's thesis is almost over and with it my time on this project will most likely end.
The wiki is written in markdown. If you have any suggestions, please feel free to share here or via slack.


Few improvements on OAuth2GenericAuthenticator

Is your suggestion related to an experience ? Please describe.
With this changes, OAuth2GenericAuthenticator cannot be registered as an IdP. It can be used as a base extension for other OAuth2 supported authenticators.

[ ] Since it is not a authenticator anymore, we can have it under OIDCAuthenticator repo and use it as the base authenticator for OIDCauthenticator
[ ] Refactor other authenticators such as GitHub, Facebook to use OAuth2Generic Authenticator as the base extension

Describe the improvement

Additional context

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


Change default display of nested enums

Description
Currently in Typst per default all levels of indentation use the arabic numbering. E.g.
+ First
  + second
  + third

renders to:
1. First
  1. second
  2. third

In LaTeX the first level is arabic ., the second level is alphabetic ) the third level is roman . and the fourth level is ALPHABETIC ..
I think it makes sense to display the different levels of nestedness differently and therefore propose to change the default in Typst and make it for example like in LaTeX.
Use Case
As a better default this would remove the need to include this in every template.

Disagree. This would mean the reader has to remember which level each numbering style corresponds to. If we do change the default, we should instead set enum.full: true.


Questions about fine-tuning ControlNet-Tile to achieve super-resolution

Hello, thank you for your great work on high-resolution image-to-3D generation!
I noticed that you utilized a ControlNet-Tile based on SD1.5 to achieve the first stage of super-resolution. I am curious about which data you used to fine-tune. It seems that fine-tuning a ControlNet usually needs data pairs (e.g. image-normal pair, image-depth pair, LR-HR pair).
Thank you :)

We use multiview high resolution and low resolution pairs. Multiview images comes from blender's rendering results for the objaverse dataset.

Thank you for your reply! Do you mean that rendering the Objaverse 3D dataset in two different resolutions (one is relatively high and another one is relatively low) in order to construct data pairs?

Yes, we use a (256,512) resolution pair for the first stage of super-resolution training, where the 256 resolution portion is augmented using downsampling to a random resolution and then upsampled back to 256, along with some random noise, to get a 256 resolution image with artifacts. This allows the super-resolution model at this step to correct some minor errors in generation.

@wukailu ,Hi, I want to ask some details about training controlnet-tile.
I tried to re-implement it using diffusers, finetuning the tile model, tiling 4-views to a sheet.
Data processing details:
low-resolution : render 256x256 resolution, make 4 views 256x256, get 512 x 512 image, then upsample to 1024 x 1024
high-resolution: render 512x512 resolution, make 4 views 512x512, get 1024 x 1024 image
Then I came across the color change problem, similar as mentioned in https://github.com/lllyasviel/ControlNet-v1-1-nightly/issues/125#issuecomment-2461268717
Could you please give some suggestions to solve the problem? Thank you.


Create tenant and Migration: DatabaseConnection create method not fire

After creating a new tenant, I tried to make a migration but the following error occurs: "Access denied for user '4-sale-beeso@localhost'.
I was looking in mysql and there's no user, no new database created before.
I follow this instruction: https://hyn.me/packages/multi-tenant
Can you tell me what I missed ?

@trinvh my apologies for the late reply, must have missed this in my activity feed.
How did you setup the queue runner? Is it running as root?

I've updated the documentation to reflect the latest 0.8.1 release. I've also updated the installer.

From my research and questions on #internals on larachat, the transaction is not committed when the observed model events are triggered. So if you system is a bit slowish, the queued job is fired before the database entries are generated, which causes that the job cannot create the database and webserver specific configurations.


Vanilla-fy DeepLabv3(+)

I noticed that the DeepLab ASPP has a hardcoded 50% dropout layer at the exit. I'm not sure whether this is mentioned in the original papers, but I think it should be exposed to the user.

Hi @DimitrisMantas! Thanks for the issue! I would appreciate this feature if you have the bandwidth to contribute 🤗


Exception when removing non-existing file

An exception when removing non-existing temporary files after the export process fails.

This issue has been fixed in current version 2.0.1.