x/tools/gopls: missing direct requirements also listed in go.mod diagnostics

What version of Go are you using (go version)?

$ go version
go version devel +71218dbc40 Wed Jul 22 21:31:19 2020 +0000 linux/amd64
$ go list -m golang.org/x/tools
golang.org/x/tools v0.0.0-20200729041821-df70183b1872
$ go list -m golang.org/x/tools/gopls
golang.org/x/tools/gopls v0.0.0-20200729041821-df70183b1872

Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE="on"
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/myitcv/.cache/go-build"
GOENV="/home/myitcv/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/myitcv/gostuff/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/myitcv/gostuff"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/home/myitcv/gos"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/home/myitcv/gos/pkg/tool/linux_amd64"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/myitcv/gostuff/src/github.com/myitcv/govim/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build466676480=/tmp/go-build -gno-record-gcc-switches"

What did you do?
CL 243218 added diagnostics to go.mod file where indirect requirements are missing. Quoting from the commit message:
Some modules may need to be added to the go.mod without being associated
with an import statement. In such cases, we show the missing module
diagnostic on the whole go.mod file. This isn't ideal, but mapping to
the full require statement isn't that simple, and this is an easy enough
starting point. The code in mod_tidy.go is becoming more unwieldy - I
think I will clean it up in a follow-up.

However we are seeing non-indirect requirements being reported as go.mod diagnostics in the scenario_tempmodfile/modfile_changes govim test.
--- FAIL: TestScripts (1.54s)
    main_test.go:77: using gopls at "/tmp/gobin-gopls-installdir340246205/gopls"
    --- FAIL: TestScripts/scenario_tempmodfile (0.04s)
        --- FAIL: TestScripts/scenario_tempmodfile/modfile_changes (10.62s)
            testscript.go:382:
                # A simple test that verifies we get a diagnostic for imports
                # that are missing from our go.mod file (0.000s)
                # Open main.go and save to ensure we are actually doing something via gopls (0.339s)
                # Sleep because we don't have an event we are waiting for (5.000s)
                # Verify that there have been no changes to go.mod (0.000s)
                # Verify that we diagnostics for the import in main.go that can't
                # be satisfied by the go.mod on disk (4.939s)
                > vimexprwait errors.golden GOVIMTest_getqflist()
                [stderr]
                 [
                   {
                -    "bufname": "go.mod",
                -    "col": 1,
                -    "lnum": 1,
                -    "module": "",
                -    "nr": 0,
                -    "pattern": "",
                -    "text": "example.com/blah is not in your go.mod file",
                -    "type": "",
                -    "valid": 1,
                -    "vcol": 0
                -  },
                -  {
                     "bufname": "main.go",
                     "col": 8,
                     "lnum": 3,
                     "module": "",
                     "nr": 0,
                     "pattern": "",
                     "text": "example.com/blah is not in your go.mod file",
                     "type": "",
                     "valid": 1,
                     "vcol": 0
                   }
                 ]
                [exit status 1]
                FAIL: testdata/scenario_tempmodfile/modfile_changes.txt:20: unexpected command failure
FAIL

What did you expect to see?
Only missing indirect requirements to be listed as go.mod diagnostics.
What did you see instead?
Missing direct requirements being listed twice: once in the file where they are imported, and secondly in the go.mod file.

cc @stamblerre @findleyr
FYI @leitzler

Hm, this is actually my intention, but it wasn't supposed to happen in this CL. https://golang.org/cl/244610 is meant to add this behavior. I'll look into the bug.

Ah if this is ultimately intended, perhaps not worth worrying about?

It's going into the release so we should fix it before it does. But yes, in general, the plan is to show those diagnostics in the future.


Canvas rendering breaks link direction

If the canvas rendering plugin is installed the show link direction plugin breaks. The option panel is still there but regardless of what you choose, no direction is indicated. Disabling canvas render fixes the issue.

they're known to not be compatible. no fix is practical

not able to find where the drawing changes with canvas plugin, but could something like this be used to get some functionality? https://developer.mozilla.org/en-US/docs/Web/API/CanvasRenderingContext2D/lineDashOffset


oUnit is considered on transition to ounit2

From the docs I see that you say to install ounit. OUnit2 seems to recommend now to use ounit2 for the install, and also use ounit2 rather than oUnit on the dune file (as per OUnit github)
A related issue seems to be:
https://github.com/exercism/ocaml/issues/364

I think this was solved by this PR.

Indeed. Closing


insert into set not supported

Which version of ShardingSphere did you use?
4.0.0-RC
Which project did you use? Sharding-JDBC or Sharding-Proxy?
Sharding-JDBC
Expected behavior
Using SQL grammar：insert into set
Actual behavior
return error
Reason analyze (If you can)
sharding does not support
Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc.
mybatis:
<sharding:inline-strategy id="orderTableStrategy" sharding-column="order_id" algorithm-expression="t_order$->{order_id % 2}" />
    <sharding:data-source id="shardingDataSource">
        <sharding:sharding-rule data-source-names="ds0">
            <sharding:table-rules>
                <sharding:table-rule logic-table="t_order" actual-data-nodes="ds0.t_order$->{0..2}" table-strategy-ref="orderTableStrategy"/>
            </sharding:table-rules>
        </sharding:sharding-rule>
    </sharding:data-source>

mapper:
    <sql id="set">
        `username`=#{username}
    </sql>
    <insert id="add" parameterType="java.lang.String">
        insert  into user
        <set>
            <include refid="set"/>
        </set>
    </insert>

return error:
### Error updating database.  Cause: java.sql.SQLException: Parameter index out of range (1 > number of parameters, which is 0).
### The error may involve com.tuya.springmvc.repository.UserRepository.add-Inline
### The error occurred while setting parameters
### SQL: insert  into user          SET `username`=?
### Cause: java.sql.SQLException: Parameter index out of range (1 > number of parameters, which is 0).
; SQL []; Parameter index out of range (1 > number of parameters, which is 0).; nested exception is java.sql.SQLException: Parameter index out of range (1 > number of parameters, which is 0).] with root cause
 java.sql.SQLException: Parameter index out of range (1 > number of parameters, which is 0).

table user has no sharding， Share a database with the t_order table，but insert into t_order was success

What is your version? We don't have version 4.0.0-RC

What is your version? We don't have version 4.0.0-RC

Sorry! is 4.0.0-RC1

What is your version? We don't have version 4.0.0-RC

update to 4.0.0-RC2 is ok


Add alwaysUseActiveTerminal setting #123

Solves #123
What problem did you solve?
Currently, only command R: Run Selection/Line in Active Terminal works for terminals other than the R Interactive terminal. This PR adds a setting r.alwaysUseActiveTerminal (false by default). When this setting is enabled, all commands (R: Run Source, R: Preview Dataframe, R: Knit Rmd etc.) are sent to the active terminal. This allows SSH users etc. to access the full functionality of this extension.
Screenshot
Before this PR, both R: Run Selection/Line and R: Preview Dataframe would have opened a new R Interactive terminal.

Notes
I needed to create the function chooseTerminalAndSendText outside activate in extension.ts so that it could be exported for use in preview.ts. I decided to put it in rTerminal.ts. I moved the associated terminal choosing/sending functions in there, because they couldn't be exported while inside activate either. I created a separate commit just for moving these functions, to make it easier to compare the changes.
Command R: Run Selection/Line in Active Terminal is probably redundant now, but I left it in there so that this PR doesn't remove any functionality.

@andycraig Thank you for a lot of work!
I could not find any problem and other tasks that I should do (e.g. Refactoring, Running the tslint, Make a Readme).
So, I will publish this version soon.

@Ikuyadeu Happy to hear that :) Thank you!


Automator: update<EMAIL_ADDRESS>in<EMAIL_ADDRESS>

Generated by Automator - 2024-12-04T18:05:54+00:00

@istio-testing: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests_istio_release-1.24
e6af77ec09d66414e3112032db6199ba888e1e1a
link
true
/test unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

/test unit-tests


The application cannot be scheduled normally

  Warning  FailedScheduling  40s   hwameistor-scheduler  0/3 nodes are available: 1 node(s) didn't match Pod's node affinity/selector, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }, 3 node(s) didn't match pod affinity rules. preemption: 0/3 nodes are available: 3 Preemption is not helpful for scheduling.

time="2024-04-22T09:36:00Z" level=debug msg="adding associated LV(capacity:<PHONE_NUMBER>) to pool LocalStorage_PoolHDD, current 1 volume(s)" Module=Scheduler/Resources
time="2024-04-22T09:36:00Z" level=debug msg="Adding a candidate" Module=Scheduler/Resources node=k8s-master total=2
time="2024-04-22T09:36:00Z" level=debug msg="Adding a candidate" Module=Scheduler/Resources node=k8s-node2 total=1
time="2024-04-22T09:36:00Z" level=debug msg="Adding a candidate" Module=Scheduler/Resources node=k8s-node1 total=0
time="2024-04-22T09:36:00Z" level=debug msg="matchable node candidates" Module=Scheduler candidates="k8s-master,k8s-node2,k8s-node1" vols=
time="2024-04-22T09:36:00Z" level=debug msg="Filtered in the node" node=k8s-node2 pod=nginx-local-storage-lvm-949bbbcc5-wkn77
I0422 09:36:00.002272       1 scheduler.go:351] "Unable to schedule pod; no fit; waiting" pod="default/nginx-local-storage-lvm-949bbbcc5-wkn77" err="0/3 nodes are available: 1 node(s) didn't match Pod's node affinity/selector, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }, 3 node(s) didn't match pod affinity rules. preemption: 0/3 nodes are available: 3 Preemption is not helpful for scheduling."
time="2024-04-22T09:36:00Z" level=debug msg="Added a Pod" Module=Scheduler/Resources name=nginx-local-storage-lvm-949bbbcc5-wkn77 namespace=default

      restartPolicy: Always
      affinity:
        nodeAffinity:
          requiredDuringSchedulingIgnoredDuringExecution:
            nodeSelectorTerms:
            - matchExpressions:
              - key: kubernetes.io/hostname
                operator: In
                values:
                - k8s-node1
                - k8s-node2
        podAffinity:
          requiredDuringSchedulingIgnoredDuringExecution:
          - labelSelector:
              matchExpressions:
              - key: app
                operator: In
                values:
                - hwameistor-local-storage
            topologyKey: "kubernetes.io/hostname"

hwameistor-local-storage-8rsr9                             2/2     Running            6 (6h29m ago)     3d2h   <IP_ADDRESS>   k8s-node1    <none>           <none>            app=hwameistor-local-storage,controller-revision-hash=84bc64d556,pod-template-generation=1
hwameistor-local-storage-csi-controller-6f4f98bccc-9rxtr   6/6     Running            77 (6h28m ago)    3d2h   <IP_ADDRESS>    k8s-master   <none>           <none>            app=hwameistor-local-storage-csi-controller,pod-template-hash=6f4f98bccc
hwameistor-local-storage-k5t85                             2/2     Running            6 (6h29m ago)     3d2h   <IP_ADDRESS>   k8s-node2    <none>           <none>            app=hwameistor-local-storage,controller-revision-hash=84bc64d556,pod-template-generation=1
hwameistor-local-storage-mb7t6                             2/2     Running            6 (6h29m ago)     3d2h   <IP_ADDRESS>    k8s-master   <none>           <none>            app=hwameistor-local-storage,controller-revision-hash=84bc64d556,pod-template-generation=1

Affinity configured incorrectly


InternVL deploy

I have completed the generation of the engine according to the tutorial, is there a relevant example tutorial for the next deployment.

In addition, when making the visual encoder engine, I found that the pre-processing class of the image is pulled from the hf website initialization information, which seems not very friendly, why not directly use the local configuration file for initialization

@sunnyqgg could u plz take a look on this question?


Disallow private fields without leading _

Time to fix this old TODO: https://github.com/angular/ts2dart/blob/6f3bbd896e7e712049eb4f2403e67f59932cf697/lib/declaration.ts#L426

What about this pattern:
// Base and Child in the same file (Dart has library level private members)
class Base {
  _internalProp;
}

class Child extends Base {
  foo() {
    this._internalProp;
  }
}

We have some of those in the form component.
What would be the best solution here ?

keep the current behavior (do not enforce private for _names),
allow protected,
rename _internalProp to internalProp

None of those solutions are great:

_var would not be accessible outside of the current library in Dart (which === current file in Ng2)
protected members would be accessible from child classes in other files in TS. Only in the current file for Dart
Everything is public so we can access everything from everywhere. Bad for encapsulation and for documentation (ie what is the class API) ?

@vicb
I think option 2 makes the most sense. Since _internalProp has a leading underscore already then you are already susceptible to the problem of option 2.
I think it makes sense to allow protected and enforce a leading underscore for protected fields.

I am adding a config option for this in ts2dart, in https://github.com/angular/ts2dart/pull/284
It defaults to false, so we can release ts2dart to angular without breaking the build, then someone needs to make the angular changes to comply with this restriction before we turn on the enforcement.


Git clone authentication not working on Linux

Testing #23305
Version 1.11.0-insider
Commit 6ae8c1506669fd579da1da92108b7db86d019bc6
Date 2017-03-29T08:21:59.122Z
Linux Elementary OS Freya

run the git clone command
enter https://monacotools.visualstudio.com/DefaultCollection/Monaco/_git/AMDLoader as URL
no authentication dialog showing up

#23474

not no authentication dialog in
Version 1.11.0-insider
Commit 4e89f9dca2febed9e3635d7eb4931d2226c2ffe2
Date 2017-03-31T11:08:37.071Z

Sorry, my fault. It works.


Trigger prod release release-0.21.3

Description of changes:
Trigger prod cli release-0.21.3
Testing (if applicable):
Documentation added/planned (if applicable):
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/test eks-anywhere-production-eks-a-release-presubmit


Feature/fix isse 35

I am well aware that this is a very experimental and tricky implementation.
Just as you also mentioned in https://github.com/zlargon/google-tts/issues/33. google provided a new API.
version 0.0.6 is also provisional and will probably not be available any time someday.
Here's my idea

For backward compatibility, tts is a async function returns url
Make a temporary httpd because the new API provides audio data(audio/mpeg) and does not provide any mp3 url
This httpd shuts down once it receives a request
httpd listens with an unused TCP port and the external ip of the running server

I don't want you to merge this PR soon, but I'd love to hear your ideas!

Coverage remained the same at 100.0% when pulling f7e9a3f8d1c0a668a417f3dee91945fe692b720a on freddiefujiwara:feature/fix-isse-35 into 031b0d63958f1abf62b743d96d43c60248f270f9 on zlargon:master.

Hi @freddiefujiwara, thank you for your PR. I prefer to have different way to implement the new Google TTS API into this library.
I do realize there is no simple way to generate the audio URL by the base64 text, and it's awesome to see you're trying to solve it in this PR. However, it seems that your solution will consume too many computer resources to find an available port and launch a temporary server for each request, especially when handling a large number of requests concurrently.
I would prefer to keep the library simple and general. So, I decide to implement the new Google TTS API in version 2.0.0 and let users decide whether audio URL or Base64 text is the best way for their use cases. (Audio URL has not been removed from this library yet because we don't know whether Google TTS will keep or remove the original API. We can just keep it until Google officially remove original API.)
You can find more details about version 2.0.0 at README and CHANGELOG.
Thanks.


Associated hazard not showing on control.php

Only for controls which are linked to consequences.

They now show, but there are duplicates.


Do not output attribute information when unparsing TermLike

When pretty-printing a TermLike, the term attributes are serialized into text and in-lined into the unparsed Kore term, leading to results like this one:
    Could not infer the equation requirement:
        /* Spa */
        \equals{SortBool{}, _}(
            /* T Fn D Spa */
            Lbl'Unds-LT-'Int'Unds'{}(
                /* T Fn D Spa */
                Lblf'LParUndsRParUnds'TEST'Unds'Int'Unds'Int{}(
                    /* T Fn D Sfa */ ConfigVarI:SortInt{}
                ),
                /* T Fn D Sfa Cl */ \dv{SortInt{}}("0")
            ),
            /* T Fn D Sfa Cl */ \dv{SortBool{}}("true")
        )

I'd argue that we do not care as much about the exact attributes of TermLikes anymore today. Therefore I propose to remove the attributes, leading to a much cleaner log output:
    Could not infer the equation requirement:
        \equals{SortBool{}, _}(
            Lbl'Unds-LT-'Int'Unds'{}(
                Lblf'LParUndsRParUnds'TEST'Unds'Int'Unds'Int{}(
                    ConfigVarI:SortInt{}
                ),
                \dv{SortInt{}}("0")
            ),
            \dv{SortBool{}}("true")
        )

The integration tests fail, but I will fix them once we have decided if we want this merged.

Looks good, tho you will have to likely update a lot of integration golden files

:heavy_plus_sign: Yes. As suggested on slack:
13 hours ago
Maybe sed -i -e 's,/\*[^*]*\*/,,g' -e '/^ *$/d' <EXPECTED_OUTPUT_FILES> in the integration tests?


fix: grpcx balancer unbalanced  when using nacos registry.

@cococolanosugar Any updates?

@cococolanosugar Any updates??

Closed as long time inactivity.


Update Documentation: Using Activity Files

Restructure the documentation
Add KML, KMZ and Simra CSV to Supported file formats
How to set up directories
File tree visualisation
Link to WebUI Uploader as a user-friendly method to add more activities
Explain how to make changes to files and Scan New Activities
Explaining the basics of metadata and naming in simple terms
Link to Advanced Metadata Extraction page (keeping this page simple for newcomers)

Thank you for improving the documentation during the night!
I just have one minor comment: The top-level heading (#) is reserved for the title, everything below needs to be at least ##. I've fixed that in another commit.


Add change Command to Seamlessly Transition Between Tasks

Adding a new change command that allows users to end the current task and immediately start the next one, streamlining the transition process between tasks.

Added and will be in next release


Running codemod.py without any params results in an error

It also seems to cause this for a few other seemingly ok inputs.

$ codemod.py
Searching for first instance...
Traceback (most recent call last):
File "/usr/local/bin/codemod.py", line 853, in
run_interactive(**options)
File "/usr/local/bin/codemod.py", line 129, in run_interactive
for patch in suggestions:
File "/usr/local/bin/codemod.py", line 357, in generate_patches
path_list = Query._walk_directory(self.root_directory)
File "/usr/local/bin/codemod.py", line 395, in _walk_directory
for root, dirs, files in os.walk(root_directory)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/os.py", line 276, in walk
names = listdir(top)
TypeError: coercing to Unicode: need string or buffer, NoneType found

Thanks for the report! :+1:
We could definitely use some tests around the command-line interface.

This should have been fixed by #51. Can you confirm, @jayanthm? :dart:

@modocache Fixed!


docs: fix some style issues of the documentation

:tada: This PR is included in version 1.4.3 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


pulseaudio module leaks connections

This probably won't affect too many people, but an unrelated problem with my setup has exposed this.
In my case, I have a display that keeps disconnecting/reconnecting while in standby. This results in waybar constantly removing and recreating bars on that display, and adding new pulseaudio connections, sadly without removing the old ones. This becomes noticeable when applications suddenly can't output any sound, and logs reveal pulseaudio rejecting new connections because the limit of 64 concurrent connections has been reached.

I think I've fixed this but not very sure: https://github.com/lilydjwg/Waybar/tree/fixpa. Would you give it a try?

I think I've fixed this but not very sure: https://github.com/lilydjwg/Waybar/tree/fixpa. Would you give it a try?

Looks good, running it now.

So far so good!

Great, I didn't encounter any issue either. I've opened a pull request.


One-time DNS lookup using 1M domain list and large selector list

Yush G, [2024-03-26 07:02]
I'm also wondering if this is a good idea to one time DNS lookup on Alexa top million: https://github.com/vavkamil/dkimsc4n/blob/master/dkim_selectors.lst
Yush G, [2024-03-26 07:02]
Then selectors that match can be cached and continue to cron
Yush G, [2024-03-26 07:03]
I'm just worried that we might get selectors that aren't actually used
Yush G, [2024-03-26 07:03]
But that way we can get a ton of domains
Yush G, [2024-03-26 07:03]
We can also expand the list with our selectors maybe
Olof, [2024-03-26 07:05]
might be an idea, it will be 2 billion calls though :) yes you are right, it may also give us many selectors that are not used
Yush G, [2024-03-26 07:11]
Well it'll be a one time call, it can be distributed over a week or whatever lol
Yush G, [2024-03-26 07:12]
I wonder if we should benchmark it with the domains we do have?
Yush G, [2024-03-26 07:12]
And check what the diff would be
Olof, [2024-03-26 07:14]
yep, that should be quite easy,
can also use just a random subset of the domains or the selectors or both, and extrapolate an estimation

ok i have an idea. what if we mark all of these found ones as "?" or something, meaning that we don't know if emails are actively being sent with it. but the ones that we currently have in the database that are added via gmail are fully verified?

Yes, that's a good idea, then we have the option in the future to handle them separately.

I'm doing some tests now. On average I'm finding about 1 new unseen DKIM selector per 1 domain from the 1M-list (using the "majestic_million.csv" list from https://github.com/PeterDaveHello/top-1m-domains?tab=readme-ov-file . The Alexa backup seems to be taken down).
With a speed of about 10 dns lookups per second, the whole thing will take 3 years :)
So it would need some optimization (e.g. narrow down the lists, run parallel jobs).

LMFAO well we definitely don't have time for 3 years. I'd recommend writing in python and using modal.com, it should fit under the free plan.

Hehe, yes 3 years is bit long :) But now I have moved to python and modal.com: https://github.com/zkemail/registry.prove.email/blob/onetime-dns/util/dsp_onetime_batch.py
This far, with modal.com, I have managed to speed it up to around 6000 DNS lookups per second, which means the whole process would take 3 days, which is a bit more acceptable.
An estimation of expected number of new domain/selector pairs: I found 8019 pairs for the first 5433 domains from the list. So if the frequency stays about the same for the rest of the list, that would be almost 1.5 million new pairs to the database.

Hehe, yes 3 years is bit long :) But now I have moved to python and modal.com: https://github.com/zkemail/registry.prove.email/blob/onetime-dns/util/dsp_onetime_batch.py
This far, with modal.com, I have managed to speed it up to around 6000 DNS lookups per second, which means the whole process would take 3 days, which is a bit more acceptable.
An estimation of expected number of new domain/selector pairs: I found 8019 pairs for the first 5433 domains from the list. So if the frequency stays about the same for the rest of the list, that would be almost 1.5 million new pairs to the database.

Sounds good. What is the projected cost? If it's more than the $100 of free credit or whatever, let me know and I'll give you the keys to my account.

Sounds good. What is the projected cost?

I tried a sparse run, with every 1000th domain in the list, and that consumed $0.36 of the credits, which gives a projected cost of $360 for the full list, so it's not super cheap. But it might be possible to lower it further, I'll keep working on it.

If it's more than the $100 of free credit or whatever, let me know and I'll give you the keys to my account.

I got $30 of free credits when signing up, so yes we probably need more credits.
Any opinion on which domains list we should use? Right now I'm using the "Majestic" list from https://github.com/PeterDaveHello/top-1m-domains?tab=readme-ov-file

And an update on the estimated number of new domain/selector pairs: 0.5 million is a better estimation, based on running with every 1000th domain, (The 1.5 million was from when just running from the top of the list).

found this one with some common selectors and selector name patterns
https://github.com/ryancdotorg/dkimscan/blob/master/dkimscan.pl#L310

@Divide-By-0 Here are some statistics
There are 2686 unique selectors in our datbase. Here they are listed by frequency: selector_frequencies.txt
The overlap between our unique selectors and dkim_selectors.lst is quite small, only 112 selectors in common
My suggestion is to merge the following three:

all selectors that occur more than once in our db
all selectors in  dkim_selectors.lst
all hard-coded selectors from here: https://github.com/ryancdotorg/dkimscan/blob/master/dkimscan.pl#L310

into one static file. Then we get a file with ~2300 selectors (15% more than dkim_selectors.lst).
I tried this merged file with a sparse run, and got about 12% more pairs than with only dkim_selectors.lst.
Some more statistics if you're interested:
selector_statistics_summary.txt
unique_selectors_excluding_hashes.txt
intersection between dkim_selectors.lst and unique_selectors_excluding_hashes.txt

tools added here: https://github.com/zkemail/registry.prove.email/commit/50f18c29da73dde4c9ef0a0b65bf9c82b0f77575


Few errors (probably on startup of the julia server)

Both errors appeared right after the loading icon in the bottom right corner disappeared which showed up when i hit ctrl+shift+enter at the end of my jl file.
First one is this:
TypeError: non-boolean (Void) used in boolean context
 in filter! at array.jl:919
 in dirs at C:\Users\necka\.julia\v0.5\CodeTools\src\module.jl:21
 in __dirsnearby#6__ at C:\Users\necka\.julia\v0.5\CodeTools\src\module.jl:41
 [inlined code] from tuple.jl:8
 in __dirsnearby#6__ at C:\Users\necka\.julia\v0.5\CodeTools\src\module.jl:48
 [inlined code] from tuple.jl:8
 in find_include at C:\Users\necka\.julia\v0.5\CodeTools\src\module.jl:79
 in filemodule at C:\Users\necka\.julia\v0.5\CodeTools\src\module.jl:90
 [inlined code] from dict.jl:723
 in modulenames at C:\Users\necka\.julia\v0.5\Atom\src\eval.jl:9
 in anonymous at C:\Users\necka\.julia\v0.5\Atom\src\eval.jl:23
 [inlined code] from dict.jl:723
 in handlemsg at C:\Users\necka\.julia\v0.5\Atom\src\comm.jl:63
 [inlined code] from C:\Users\necka\.julia\v0.5\Atom\src\comm.jl:18
 in anonymous at task.jl:63

Second one is this:
TypeError: non-boolean (Void) used in boolean context
 in yieldto at task.jl:77
 in wait at task.jl:358
 in wait at task.jl:277
 in wait at task.jl:114
 [inlined code] from C:\Users\necka\.julia\v0.5\Lazy\src\dynamic.jl:69
 in anonymous at C:\Users\necka\.julia\v0.5\Atom\src\eval.jl:66
 [inlined code] from dict.jl:723
 in handlemsg at C:\Users\necka\.julia\v0.5\Atom\src\comm.jl:63
 [inlined code] from C:\Users\necka\.julia\v0.5\Atom\src\comm.jl:18
 in anonymous at task.jl:63

Are you on the master branches of all relevant packages?
Also, is this specific to julia 0.5? Just asking because I don't see these errors on stable julia.

since i always only used update or checkout on raw package names i assume i'm on master branches.
And yeah it's the 0.5.0-dev+1526 version.

Can you do Pkg.checkout("CodeTools")? This looks a lot like #25, and should be fixed on CodeTools master.

And finally I'm sorry that i wasted your time...
It now works flawlessly!

No worries! Glad you got it working.
Enjoy!


Control the root link height instead of the CoM

We decided to add a flag for switching between the control of the CoM height  and root link height

This PR is closed in favour of #93


[AMORO-3308][Bugfix]: get signature check error when upload catalog config files

Why are the changes needed?
Close #3308.
Brief change log
The upload method was implemented additionally and did not use the default config. This bugfix adds the header 'X-Request-Source': 'Web' to the upload method.
How was this patch tested?

Thanks for the quick fix. @mansonliwh


i signup and give me this error Doctype html error

cannot signup show this error ... Docttype html see image in the link..
copy link and past in the search bar and click enter......
https://drive.google.com/file/d/1wxOLX3pfe7Ccnt32o1FP4SK3e0BsSmsZ/view?usp=sharing

@prabhakar267

Is this because the Heroku app is not up? https://project-travel-mate.herokuapp.com/api/

Can you please tell me how to resolve the doctype error...the app shows html code in the snackbar after clicking on sign up

Same error... How to solve... Plzz anyone help... @ritesh-pandey @Swati4star @prabhakar267

Does anyone know how to fix this error? Can Someone help ?

Please solve this is issue


ui-guage is missing  different types

Description
The original dashboad guage has the level, compass and donut types. Howeevr, the new one is missing these and they come in quite handy in visualizations/simulations
Epic/Story
No response
Have you provided an initial effort estimate for this issue?
I am no FlowFuse team member

Compass: https://discourse.nodered.org/t/add-compass-mode-to-db2-gauge-widget/85806

Oh nice, level?

UI level example: https://discourse.nodered.org/t/dashboard-2-0-is-now-generally-available/84913/43?u=joepavitt

Thanks!

Updated versions of all of them:
https://discourse.nodered.org/t/gauges-for-dashboard-2-0-made-with-ui-template/85955/2


deployments: add some basic tests for npm package

It happened that we had an empty abis/mainnet folder - which caused a broken npm release. The test here would prevent something like this in the future.
@istankovic - running the test out of the make npm-package would stop the release of pytest errors out, right?

I also think we should maybe change the circleCI conf:
https://github.com/beamer-bridge/beamer/blob/deployments/add_tests_for_deployment/.circleci/workflows.yml#L324
Instead of creating the package only when we have modified artifacts or abi, we maybe should run the make npm-package all the time - this way it would detect if something in the pipeline(generate-abi.py for example) is broken?

I also think we should maybe change the circleCI conf:
https://github.com/beamer-bridge/beamer/blob/deployments/add_tests_for_deployment/.circleci/workflows.yml#L324
Instead of creating the package only when we have modified artifacts or abi, we maybe should run the make npm-package all the time - this way it would detect if something in the pipeline(generate-abi.py for example) is broken?

That is a very good point, yes. :+1:
Whenever the backend is changed, we should run the "build and test" job and if the artifacts are changed, we additionally should also run the "publish" part.

I've moved the code for the npm package to a separate directory and added a step in the workflow to execute the test.
The test generates a package, installs it and we compare whether the expected abis are there (we determine that based on the contract names in the artifacts) and we also check whether all artifacts have been copied to the artifacts folder of the package.

Could you please remove commit 5ab9ccf86914fdd2d6c6c7572f58049b385ec0ba from this PR? It's not necessary anymore.

Commit f108275cbf83dce89aec0635cde183e19bae1eef has message
deployments: add some basic tests for npm package

which is wrong, because that commit is about updating the CircleCI workflow.

@manuelwedler @GabrielBuragev could you also please take a look at this PR?
I am afraid I don't know enough about JS things.

Nitpick: the commit message of the first commit:
deployments: move npm packaage to separate folder

We’ve moved the code that generates the package to a separate folder and added some basic tests for whether the package generated contains the expected files.

deployments: wrong files copied

mentions "wrong files copied", not sure what that is about, probably a remnant of a rebase, but would be nice to remove it.
Also note the typo in packaage in the first line.
Aside from that, looks pretty good! (Note that I left the JS part to @GabrielBuragev and/or @manuelwedler).

Isn't that the way to write it? :D


Updated README

Updated the README.md file with development steps

@Such6 pls. reference the issue

Do you want images to be removed, or it looks fine now


Remove file headers

[QA] Remove file header (DocBlock comments)

Thanks @ghostwriter!
I'll rebase and merge locally as-is :+1:


zh-hk language owner

Summary by CodeRabbit

New Features

Added support for Chinese (Hong Kong) language.
Introduced a new language leader for Chinese (Hong Kong).

Please review this PR

@swonge Are you interested in being the language leader for zh-hk?

Yes
On Friday 7 June 2024 at 13:59:14 GMT-7, Michael Hansen @.***> wrote:
@swonge Are you interested in being the language leader for zh-hk?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

Yes On Friday 7 June 2024 at 13:59:14 GMT-7, Michael Hansen @.> wrote: @swonge Are you interested in being the language leader for zh-hk? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.>

Yes, I am.

OK, great! The process to become a language leader is to submit at least two small PR's for your language with translations. If everything looks good, I will add you as a leader in a separate PR.
I'm closing this PR for now; please message me when you have your two translation PR's ready. Thanks again :+1:

hi Synesthesiam,
Actually I did, I have couple of PR but no one response to those

update zh-hk translation for lock_hass, scene_hass, script_hass - https://github.com/home-assistant/intents/pull/1853
zh-hk translation - https://github.com/home-assistant/intents/pull/1853
zh-hk script_Hass - https://github.com/home-assistant/intents/pull/1222
zh-hk scene_Hass - https://github.com/home-assistant/intents/pull/1219
zh-hk - lock_Hass - https://github.com/home-assistant/intents/pull/1217

OK, great! The process to become a language leader is to submit at least two small PR's for your language with translations. If everything looks good, I will add you as a leader in a separate PR.
I'm closing this PR for now; please message me when you have your two translation PR's ready. Thanks again 👍

hi Synesthesiam,
Thanks for your response
Actually I did, I have couple of PR but no one response to those
update zh-hk translation for lock_hass, scene_hass, script_hass - https://github.com/home-assistant/intents/pull/1853
zh-hk translation - https://github.com/home-assistant/intents/pull/1853
zh-hk script_Hass - https://github.com/home-assistant/intents/pull/1222
zh-hk scene_Hass - https://github.com/home-assistant/intents/pull/1219
zh-hk - lock_Hass - https://github.com/home-assistant/intents/pull/1217
if you look up "zh-hk" from pull request search, you should see my work, seem no one pay attention to my PRs


linux environment script to help build

Ah that's cool. This seems like magic

this helps linux users setup a linux-specific build environment

I can't test this for a while sooo you let me know when it's good to merge lol

ok. This will make it easier too to switch between different builds.
example:
if you add a new environment file like:
env/your_cool_new_sketch.env
and inside this file is
export SKETCH=way-cooler-examples/CoolestSketchEver/CoolestSketchEver.ino
and run
source env/your_cool_new_sketch.env
make clean
make

It will build the sketch located in: way-cooler-examples/CoolestSketchEver/CoolestSketchEver.ino
Same applies to any other variable in the Makefile, e.g. BOARD, HTTP_ADDR, UPLOAD_PORT, etc

should i merge this?


Added Remove-GSUserPhone function

I found that the .NET library was sending
{ "phones": [] }
instead of:
{ "phones": null }
which resulted in the phone object not being deleted. may have something to do with this issues
I wrote a function which sends the latter fragment of JSON to get the desired outcome.

Hey @mattwoolnough - Going to close this out in favor of adding the functionality into Update-GSUser by passing $null as the property value. Should be getting a release shortly, along with your Relations PR as well!


Zip files Async not working?

Steps to reproduce

Create http get request.
set AllowSynchronousIO to false
Start zip json data and pdf docs
Only use async methods to run the code.

Expected behavior
Return a zipped file
Actual behavior
You can se it crash on PutNextEntryAsync and/or finnishAsync.
Looks like PutNextEntryAsync  calls Finish() and not FinnishAsync()
Exception:
Exception has occurred: CLR/System.InvalidOperationException
Exception thrown: 'System.InvalidOperationException' in System.Private.CoreLib.dll: 'Synchronous operations are disallowed. Call WriteAsync or set AllowSynchronousIO to true instead.'

Version of SharpZipLib
1.4.1
Obtained from (only keep the relevant lines)

Package installed using NuGet

Yeah, this is caused by the following line:
https://github.com/icsharpcode/SharpZipLib/blob/cdd0931e3c476faaf829963b2567619431c871bb/src/ICSharpCode.SharpZipLib/Zip/ZipOutputStream.cs#L608
It shouldn't be called inside WriteEntryFooter, but rather in the CloseEntry(Async) methods.


Missing ethereum RPC calls make redux-devtools fail

A redux app that uses the redux-devtool chrome extension will fail to initialize.
bootstrap 60141db…:777 Error: Error: RPC method eth_protocolVersion not supported.
    at GethApiDouble.handleRequest (/Users/person/Documents/ethereum/github/testrpc/lib/subproviders/geth_api_double.js:58:16)
    at next (/Users/person/Documents/ethereum/github/testrpc/node_modules/web3-provider-engine/index.js:95:18)
    at SolcSubprovider.handleRequest (/Users/person/Documents/ethereum/github/testrpc/node_modules/web3-provider-engine/subproviders/solc.js:28:7)
    at next (/Users/person/Documents/ethereum/github/testrpc/node_modules/web3-provider-engine/index.js:95:18)
    at VmSubprovider.handleRequest (/Users/person/Documents/ethereum/github/testrpc/node_modules/web3-provider-engine/subproviders/vm.js:40:12)
    at next (/Users/person/Documents/ethereum/github/testrpc/node_modules/web3-provider-engine/index.js:95:18)
    at GethDefaults.handleRequest (/Users/person/Documents/ethereum/github/testrpc/lib/subproviders/gethdefaults.js:17:12)
    at next (/Users/person/Documents/ethereum/github/testrpc/node_modules/web3-provider-engine/index.js:95:18)
    at FilterSubprovider.handleRequest (/Users/person/Documents/ethereum/github/testrpc/node_modules/web3-provider-engine/subproviders/filters.js:87:7)
    at next (/Users/person/Documents/ethereum/github/testrpc/node_modules/web3-provider-engine/index.js:95:18)
    at GethApiDouble.handleRequest (/Users/person/Documents/ethereum/github/testrpc/lib/subproviders/geth_api_double.js:58:16)
    at next (/Users/person/Documents/ethereum/github/testrpc/node_modules/web3-provider-engine/index.js:95:18)
    at SolcSubprovider.handleRequest (/Users/person/Documents/ethereum/github/testrpc/node_modules/web3-provider-engine/subproviders/solc.js:28:7)
    at next (/Users/person/Documents/ethereum/github/testrpc/node_modules/web3-provider-engine/index.js:95:18)
    at VmSubprovider.handleRequest (/Users/person/Documents/ethereum/github/testrpc/node_modules/web3-provider-engine/subproviders/vm.js:40:12)
    at next (/Users/person/Documents/ethereum/github/testrpc/node_modules/web3-provider-engine/index.js:95:18)
    at GethDefaults.handleRequest (/Users/person/Documents/ethereum/github/testrpc/lib/subproviders/gethdefaults.js:17:12)
    at next (/Users/person/Documents/ethereum/github/testrpc/node_modules/web3-provider-engine/index.js:95:18)
    at FilterSubprovider.handleRequest (/Users/person/Documents/ethereum/github/testrpc/node_modules/web3-provider-engine/subproviders/filters.js:87:7)
    at next (/Users/person/Documents/ethereum/github/testrpc/node_modules/web3-provider-engine/index.js:95:18)
    at Object.InvalidResponse (http://<IP_ADDRESS>:3000/app.60141dbe412a57b568e1.js:18775:16)
    at RequestManager.send (http://<IP_ADDRESS>:3000/app.60141dbe412a57b568e1.js:104221:22)
    at Eth.get [as protocolVersion] (http://<IP_ADDRESS>:3000/app.60141dbe412a57b568e1.js:15727:62)
    at derez (<anonymous>:2:5795)
    at derez (<anonymous>:2:5787)
    at derez (<anonymous>:2:5787)
    at derez (<anonymous>:2:5787)
    at derez (<anonymous>:2:5787)
    at Object.decycle (<anonymous>:2:5824)
    at Object.e.stringify (<anonymous>:1:9180)

Redux devtool iterates over the web3.eth object and wraps all the functions. Because testrpc does not implement every rpc call, the error occurs.
Expected Behavior

If you have truffle, webpack, redux, and redux-devtool, the page should load and redux-devtool should be visible.

Current Behavior

When loading the page with redux-devtools, the page outputs errors and does not render page.

Possible Solution

From what I can see, testrpc is missing the rpc call eth_protocolVersion and therefor fails.
implement the following methods to make it work:

eth_protocolVersion
personal_listAccounts
bzz_hive
bzz_info
ssh_version

Steps to Reproduce (for bugs)

create front end project with react-redux
add truffle to project
start webpack server
go to page and notice how page does not render, and errors are visible in the console.

Context

Basically, our front-end cannot use the redux-devtools to help facilitate development. I have to revert to console.logs rather than use a tool for debugging.
Your Environment

Version used:
Environment name and version (e.g. PHP 5.4 on nginx 1.9.1):
Server type and version:
Operating System and version:
Link to your project:

OSX el capitan
Chrome 60.0.3080.0
Node 7.9.0
truffle 3.2.1
redux-devtools chrome extension v2.14.0

This also happens with VueJs. It calls all the methods of web3 on different occasions, not only for the devtools, and it results in an error

Hi there. Thanks for submitting this issue. I'm not sure I follow exactly what's happening. The failure you posted shows that the TestRPC doesn't support eth_protocolVersion (which is true, but it will have a stub very soon). That said, why would redux-devtools expose this error? redux-devtools isn't affiliated with Ethereum, so it has to be your code (or some library you use) that calls this request. Is that correct?

I think is because,  sometimes,  these Javascript frameworks just call all the functions of Javascript object (web3 in this case) for their internal workings.
Since web3 had the protocolVersion function it is being carried by the framework at some point, and throws an exception.
So, it is indeed, to some extent, not to fault of testrpc, but it would not be an issue if testrpc didn't threw for actual web3 methods.

To me  console.log('Deployed is -'+JSON.stringify( deployedecrecTest)); line throws me the error, If I doesnt use JSON.stringify, it prints out [object object]. I'm using testrpc+truffle+web3.

@tcoulter What @JoseOspina said is correct. My pull request for a while ago worked but now has conflicts with 4.0.0. I think i have to update ganache-core instead.

@sogoiii Don't worry about ganache-core. I'll get your PR in today.

This has been included in the latest version of the TestRPC. See the release notes here: https://github.com/ethereumjs/testrpc/releases
Thanks!

Hi I run into the same problem today. As I am trying to assign "web3" object into the state tree, redux dev tool throws like this:
Uncaught Error: Invalid JSON RPC response: undefined
    at Object.InvalidResponse (inpage.js:14300)
    at s.send (inpage.js:14300)
    at r.coinbase (inpage.js:14300)
    at derez (<anonymous>:2:6079)
    at derez (<anonymous>:2:6072)
    at derez (<anonymous>:2:6072)
    at derez (<anonymous>:2:6072)
    at derez (<anonymous>:2:6072)
    at derez (<anonymous>:2:6072)
    at derez (<anonymous>:2:6072)
    at derez (<anonymous>:2:6072)
    at derez (<anonymous>:2:6072)
    at derez (<anonymous>:2:6072)
    at derez (<anonymous>:2:6072)
    at Object.decycle (<anonymous>:2:6109)
    at Object.e.stringify (<anonymous>:1:9197)
    at tryCatchStringify (<anonymous>:1:18852)
    at stringify (<anonymous>:1:18960)
    at toContentScript (<anonymous>:1:20255)
    at relay (<anonymous>:1:28996)
    at <anonymous>:2:114
    at invokeFunc (<anonymous>:2:24146)
    at leadingEdge (<anonymous>:2:24223)
    at debounced (<anonymous>:2:24803)
    at Object.onMessage (<anonymous>:1:30252)
    at <anonymous>:1:21010
    at Array.forEach (<anonymous>)
    at handleMessages (<anonymous>:1:20945)


[Accelerate] Each Training step takes an absurd amount of time

Training a VQ-VAE-2 on Kaggle's GPU - when I start training on a full epoch, each iteration (i.e each step/pass on a single batch) takes around 5 mins on GPU. GPU usage is negligible, yet it does occupy all VRAM as CUDA should 🤷
This is my training function:-
def train(loader, val_loader, scheduler):
    accelerator = Accelerator(fp16=False, cpu=args.cpu_run)
    device = accelerator.device

    #initializing the model
    model = VQVAE(in_channel=3, channel=128, n_res_block=args.res_blocks,
                  n_res_channel=args.res_channel,
                  embed_dim=args.embed_dim, n_embed=args.n_embed,
                  decay=args.decay).to(device)

    optimizer = optim.Adam(model.parameters(), lr=args.lr)

    accelerator.print(summary(model, (args.batch_size, 3, args.size, args.size)))
    accelerator.print(model) #vanilla pytorch summary

    model, optimizer, loader, val_loader = accelerator.prepare(model, optimizer, loader, val_loader)
    loader, val_loader = tqdm(loader), tqdm(val_loader)

    criterion = nn.MSELoss()

    latent_loss_weight = 0.25
    latent_loss_beta_list = torch.linspace(0, latent_loss_weight, 20)

    sample_size = 20

    mse_sum = 0
    mse_n = 0
    val_mse_sum, val_mse_n, beta_index = 0, 0, 0 #init beta index

    with wandb.init(project=args.wandb_project_name, config=args.__dict__, save_code=True, name=args.run_name, magic=True):
        for epoch in range(args.epoch):
            #Starting Epoch loops
            model.train()
            for i, (img, label) in enumerate(loader):
                img = img.to(device)

                out, latent_loss = model(img)
                recon_loss = criterion(out, img)
                latent_loss = latent_loss.mean()

                beta_index = epoch  #for consistency
                if beta_index >= 24:
                    beta_index = latent_loss_beta_list[-1]

                loss = recon_loss + latent_loss_beta_list[beta_index] * latent_loss

                model.zero_grad(set_to_none=True)

                accelerator.backward(loss) #added loss to backprop

                if scheduler is not None:
                    scheduler.step()

                torch.nn.utils.clip_grad_norm_(model.parameters(), args.gradclip) #grad clipping

                optimizer.step()

                mse_sum += recon_loss.item() * img.shape[0]
                mse_n += img.shape[0]

                lr = optimizer.param_groups[0]['lr']

                wandb.log({"epoch": epoch+1, "mse": recon_loss.item(),
                            "latent_loss": latent_loss.item(), "avg_mse": (mse_sum / mse_n),
                            "lr": lr})

                if i % 25 == 0:
                    accelerator.print({"epoch": epoch+1, "mse": recon_loss.item(),
                        "latent_loss": latent_loss.item(), "avg_mse": (mse_sum/ mse_n),
                        "lr": lr})

                #Performing Validation and loggign out images
                if epoch % 2 == 0:   #i % 100 == 0
                    model.eval()

                    #--------------VALIDATION------------------
                    for i, (img, label) in enumerate(val_loader):
                        img.to(device)
                        model.to(device)

                        with torch.no_grad():
                            out, latent_loss = model(img)

                        val_recon_loss = criterion(out, img)
                        val_latent_loss = latent_loss.mean()
                        val_loss = recon_loss + latent_loss_beta_list[beta_index] * latent_loss

                        val_mse_sum += recon_loss.item() * img.shape[0]
                        val_mse_n += img.shape[0]

                    wandb.log({"epoch": epoch+1, "val_mse": val_recon_loss.item(),
                            "val_latent_loss": val_latent_loss.item(), "val_avg_mse": (val_mse_sum/ val_mse_n),
                            "lr": lr})

                    accelerator.print({"epoch": epoch+1, "val_mse": val_recon_loss.item(),
                            "val_latent_loss": val_latent_loss.item(), "val_avg_mse": (val_mse_sum/ val_mse_n),
                            "lr": lr})

                    model.train()

            #Saving the model checkpoints every epoch
            if epoch % 10 == 0:
                model.eval()

                sample = img[:sample_size]

                with torch.no_grad():
                    out, _ = model(sample)

                utils.save_image(
                    torch.cat([sample, out], 0),
                    f'/kaggle/working/samples/{str(epoch + 1).zfill(5)}_{str(i).zfill(5)}.png',
                    nrow=sample_size,
                    normalize=True,
                    range=(-1, 1),
                )

                wandb.log({f"{epoch+1}_Samples" : [wandb.Image(img) for img in torch.cat( [sample, out], 0) ]})
                accelerator.save(model.state_dict(), f'checkpoint/vqvae_{str(epoch + 1).zfill(3)}.pt')
                model.train()

            print(f'\n---EPOCH {epoch} CCOMPLETED---\n')

I don't see how tensor shapes are changing at all - so things should work relatively smoother.
Validation on around 15,000 images is relatively fine I suppose,
 98%|████████████████████████████████████████▎| 116/118 [07:37<00:04,  2.48s/it]

Though I'd expected it to be much, much faster.
But training,
2%|▌                                 | 31/1783 [2:37:49<145:33:55, 299.11s/it]
{'epoch': 1, 'val_mse': 0.07451071590185165, 'val_latent_loss': 0.03670966625213623, 'val_avg_mse': 0.13713628306023537, 'lr': 0.0001}

is pretty slow. Any ideas why computations are being offloaded to CPU while the graph is clearly being built on GPU?
Also,
parser.add_argument('--cpu-run', type=bool, default=False)

my CPU run arg is set to False by default, so at least I am not overriding GPU computation 🤷♂

It seems you're running on one GPU only, so what speed does the same code run without using Accelerate?

A non-Accelerate vanilla implementation on a single P100 performs nearly 10 epochs ~ 12 hours (no validation) which roughly comes about ~2.42 seconds/step on average. I suppose it's using CPU here, but that doesn't make sense if the graph is being built on GPU and CUDA reserves all GPU memory too?

Weird that it changes so much when it's kind of the same. Random though, is torch_xla installed in the environment event when not using TPUs?

Nope. Can confirm a ModuleNotFoundError when importing

I will try printing the device variable to confirm whether its indeed using GPU - or is there some bug with the argparsing but apart from that, I don't really see what else would affect computations like that 🤷

USING DEVICE: cuda		ARGS @ CPU_RUN: False

Definitely using CPU, just computations aren't being run on it

If you're not using mixed precision or DeepSpeed, accelerator.backward(loss) is exactly like doing loss.backward(). Could you try replacing the lines and see if the slowdown persists?
To check if it's a data bottleneck cause by Accelerate, could you try to not send the train_dataloader to the Accelerator.prepare method and see if it fixes the training speed?

Removed dataloader from prepare, some tiny differences in speed but nothing major - GPU is still idle most of the time.
Same with loss.backward() - not really any tangible impacts. The whole thing is a mystery; why using backward slows down Accelerate soo drastically is beyond me. 🤷♂
I suppose I can send you the repo+colab in some time, if I am not able to figure out the problem?

Sure.
Could you also print accelerator.state to make sure there is not some weird thing going on?

Accelerator State: Distributed environment: NO
Num processes: 1
Process index: 0
Local process index: 0
Device: cuda
Use FP16 precision: False

I am currently going to revamp my entire training loop by making the train function train only for a single epoch, using another external function with a loop to interface and run the train and seeing whether that improves anything - because apart from a bug in Accelerate the only thing I can think of is my loop 🤔

Revamped my training loop, for reference its something like this:-
def exec(epochs, loader, val_loader, model, optimizer, scheduler, device):
  for i in range(epochs):
    train(i, loader, val_loader, model, optimizer, scheduler, device)
    torch.save(model.state_dict(), f'checkpoint/vqvae_{str(i + 1).zfill(3)}.pt')

where I use notebook_launcher(exec) to launch the training. Very weirdly, training works fine IFF validation snippet is removed:-
              if epoch > 0 and epoch % 2 == 0:
                  model.eval()

                  #--------------VALIDATION------------------
                  for i, (img, label) in enumerate(val_loader):
                      img = img.to(device)

                      with torch.no_grad():
                          out, latent_loss = model(img)

                      val_recon_loss = criterion(out, img)
                      val_latent_loss = latent_loss.mean()

                      val_mse_sum += recon_loss.item() * img.shape[0]
                      val_mse_n += img.shape[0]

                  print({"epoch": epoch+1, "val_mse": val_recon_loss.item(),
                          "val_latent_loss": val_latent_loss.item(), "val_avg_mse": (val_mse_sum/ val_mse_n),
                          "lr": lr})

                  model.train()

I have absolutely no idea why training becomes so slow if I validate - which is concerning because I really don't want to overfit

Uh, I can't say I have seen something like this before. It's really weird! Is the validation dataloader passed to accelerator.prepare? Also is model.train() called before the train function? Might be a side effect of the last line otherwise.

Hmm... It seems I might have a clue to the situation. for the validation loop, the first thing it triggers is validation due to modulo %
if epoch % 2 == 0:

#WHICH CAN BE FIXED SIMPLY BY
if epoch > 0 and epoch % 2 == 0:

What I would guess is that perhaps, when the first few steps are taken Accelerate is performing some sort of optimizations and compilations of the computation graph....? But for some reason, validating right, in the beginning, breaks something essential for Accelerate leading to broken ops for backproppping 🤷♂
Pretty sure it's wrong, but I suppose you get the general idea 😉

BTW as an aside, have you ever encountered free() invalid size when training on TPU? seems like a memory problem, but RAM usage is barely 10% when the error kicks in and execution stops. I may be doing something wrong on my end though (maybe autocast is not supposed to be there for TPU?) so might have to check....

That is very very weird. There is no reason validating first would change anything, especially in a non-distributed env. With no distributed training and mixed precision deactivated, Accelerate really only calls the regular PyTorch lines of the training loop, so there is no reason for any difference with PyTorch :-(
For TPUs there shouldn't be any autocast in your code, this is not supported.

I was trying to test it for more than a few epochs, but ran out of GPU time and am trying to use TPU - but have this weird error:-

  0%|                                                  | 0/3565 [00:00<?, ?it/s]
  0%|                                                   | 0/235 [00:00<?, ?it/s]free(): invalid size

This is my code BTW if you might wanna take a look.
AFAIK running TPU should be as simple as installing the client and running the script 🤷 Its a TPUv3_8 from kaggle so has more than enough memory 🤔 any ideas?

I have never encountered that error. Are you sure the model is supported on TPU? Some models do operations that are not supported by PyTorch XLA.

it's just a VQ-VAE, so the Conv Layers should be supported in any case (perhaps the quantization process mightn't be) - but I don't see why problems can arise as various other similar models have been run on TPUs in the past 🤷
As for the validation, I can confirm not computing it early on leads to a normal training loop (tested on about 4 epochs) so perhaps one could put some sort of a reminder/disclaimer in the ReadMe to advise people accidentally doing this?


Rewrite modules tab

Contains
Small changes for GameDetailsScreen. Includes highlighting for invalid modules (version from manifest.json isn't in user's classpath).
How to test
After release of V2 we increased Core version from 2.0.0-SNAPSHOT to 2.0.1-SNAPSHOT.
Basically, you need old save with previous version. In this case when you'll open the screen, you should see highlighted "Core Content" module on Modules tab and warning in description.

Hooray Jenkins reported success with all tests good!

Tests out 👍
I think we could still distinguish between modules missing (red, no info available) vs wrong version (yellow, list what we have) but that can be done later. Maybe a backlog card?
At present a non-existing module (just add a gibberish one into the save manifest) results in a logged error but no indication in the game details that there's a problem (the module gets listed in the overview, but not on the module tab)


Is there a way not to show traceback?

It takes to much space in console, can I turn off it?

Hey, could you send me an example please to replicate the bug?

Sorry I can't but as I see it is simple timeout error when site proxy/site didn't responde some time.
net/http: request canceled (Client.Timeout exceeded while awaiting headers)
Get "https://api-v2.rtfkt.com/api/users/address": write tcp <IP_ADDRESS>:51943-><IP_ADDRESS>:31112: i/o timeout

Not sure if this is exactly what you mean, but you can catch the errors.
Here is an example:
from tls_client.exceptions import TLSClientExeption
import tls_client

session = tls_client.Session(
    client_identifier="chrome_107"
)

try:
    res = session.get(
        "http://www.google.com:81/",
        timeout_seconds=1
    )
except TLSClientExeption as e:
    print(f"TLS Client Error: {e}")

Sorry I can't but as I see it is simple timeout error when site proxy/site didn't responde some time.
net/http: request canceled (Client.Timeout exceeded while awaiting headers)
Get "https://api-v2.rtfkt.com/api/users/address": write tcp <IP_ADDRESS>:51943-><IP_ADDRESS>:31112: i/o timeout

I've a similar issue, sometimes with the proxies I get randomly i/o timeout

Sorry I can't but as I see it is simple timeout error when site proxy/site didn't responde some time.
net/http: request canceled (Client.Timeout exceeded while awaiting headers)
Get "https://api-v2.rtfkt.com/api/users/address": write tcp <IP_ADDRESS>:51943-><IP_ADDRESS>:31112: i/o timeout

I've a similar issue, sometimes with the proxies I get randomly i/o timeout

I'm not sure, but this seems to have solved my problem https://github.com/FlorianREGAZ/Python-Tls-Client/issues/9#issuecomment-1320968519

Sorry I can't but as I see it is simple timeout error when site proxy/site didn't responde some time.
net/http: request canceled (Client.Timeout exceeded while awaiting headers)
Get "https://api-v2.rtfkt.com/api/users/address": write tcp <IP_ADDRESS>:51943-><IP_ADDRESS>:31112: i/o timeout

I've a similar issue, sometimes with the proxies I get randomly i/o timeout

I'm not sure, but this seems to have solved my problem https://github.com/FlorianREGAZ/Python-Tls-Client/issues/9#issuecomment-1320968519

The timeout or the try exception?

TLSClientExeption

I mean catching TLSClientExeption error. It doesn't show any extra logs

Ok thank you, but the timeout issue persist at this point 😔 I got randomly tcp i/o timeout with proxies, also with a huge timeout value


User search results ignore single characters

This is likely for performance but hopefully it could be made slightly less restrictive. That would help those of us who often forget our colleagues' full names.
Only first name matched:

Expected result one keystroke later:

This is somewhat related to #1078.

I'm not entirely sure what you're suggesting. If we don't tokenise the displayName with ngrams but wish to query it, the user would have to search for exact maches. For example:
There is a user with displayName "Simon Gaeremynck. If we don't use the ngram tokenizer but rather the simple tokenizer, that name would get tokenized into simon and gaeremynck. If I were to then do a search for Simon G I would get all the resources that have simon as a token. The G-bit would be irrelevant as it doesn't match any token. To clarify that last piece, assume there are 2 other users called "Simon Doe" and "Simon Echo". When querying for "Simon G" those users would have the exact same score as the "Simon Gaeremynck" document.
Or am I just being dense and misunderstanding?

@simong the suggestion is to just add something like an edgengram analyzer on the display_name document field (without having a whitespace tokenizer), and include the display_name field in the fulltext queries. This is in contrast to just doing fulltext search on q_high+q_low, now we could do it on display_name+q_high+q_low, and you would get a "boost-able" hit on display_name in the scenario given above "Shweta G"

Done, attached some code. Assigning to @nicolaasmatthijs for review

Back to @simong for follow-up

Added a test-case. Back to @nicolaasmatthijs

Changes Unknown when pulling b2048377e94c84d192ef93b2440d5fbd45570ca4 on simong:1092-displayname-search into ** on oaeproject:master**.

Followed up and merged.


draft: Prevent lots of empty inline snapshots with --force-update-snapshots without --accept

I realize what you mean in the prior comment. Currently running with --accept is kinda painful. I'm not sure how common that is, but would be nice to fix.
Had a go for 30 mins, need to run, but pushing an initial effort and a pointer to the thing that needs fixing

OK, I think I understand the underlying problem here. In a test like:
assert_snapshot!("test", @r#test#");

The macro invocation only sees the test value; it doesn't know about the r#...#
insta can't find out about the r#...#, only cargo-insta, because only cargo-insta has the rust parser
We need to compare the full r#...# to correctly decide whether a snapshot requires updating when --force-update-snapshots is passed, and we need to do that with insta only
Unless we can run matches_fully correctly, we default to creating pending snapshots for snapshots which don't need updating, which is what the existing master does

A couple of ideas, none are great:

Have --force-update-snapshots accept by default. This is reasonable UX — it's generally something folks are not running on every loop, but rather an occasional clean-up.

Currently, running --force-update-snapshots --accept is a reasonable experience — it prints a few too many names of snapshots it's updating, but that's the only cost.
It also sounds like that's what it's doing already, or we could pick a new name --force-accept if we wanted

Revert https://github.com/mitsuhiko/insta/pull/569, give up on force-updating inline snapshots.
Offer some additional option; --force-update-inline-snapshots. This would be a shame.

My current thinking is to revert #569, and then default to --force-update-snapshots accepting over a couple of versions.

I think this is broadly fixed in #581


TP

Hi,
Is there a native way for issuing a sell signal without actually setting a short advice in strategy?( or the other way around)
I mean can I set a target profit for an advice?

*make a note when you buy and after this check if the candle price moves above your TP target. If so signal a sell.
I'm looking for the syntax for this action, can you pls give me an example on how to do exactly that?

here is an example: https://gist.github.com/askmike/0419e212ca70f595f30bffa65a201080
This works great but note:

once the TP triggers Gekko will execute using limit orders, with no guarantee at what price you'll execute.
This assumes you're going to buy close to the candle advice price. This is not guaranteed. Read this for more info: #2556 - you can use the experimental onTrade API to get the actual execution price, but in most cases (in liquid markets) there shouldn't be a big need.


[labs/ssr] Inline source in source maps

Fixes #2645
tsconfig was missing inlineSources option for labs/ssr package.
Alternative fix would be to actually include the source ts files in the npm package. Since this package is meant for server/node use only, would that potentially be preferable?
Will stick with inline sourcemap to be consistent with the rest of our packages.

@justinfagnani I want to double check if inlining source here is the preferable way. You've mentioned here https://github.com/lit/lit.dev/issues/872#issuecomment-1168046720 that we choose to not publish ts files. Is that also the case for packages like labs/ssr that are meant to be used in the server/node, and potentially in deno as well?

Per offline discussion, we'll go with inlining sources for now as strict improvement for the current issue and re-evaluate whether we want to switch to publishing ts source files down the line.


Fix spelling errors on comparison page

These were preventing some details from showing
for Yugabyte.

This change is


What is "[-]calg library: http://c-algorithms.sourceforge.net" trying to tell me?

I've installed pybloomfilter using pip, on a linux machine running python 2.7.15.  When I do "import pybloomfilter", i get this message on the console as my python exits:
[-]calg library: http://c-algorithms.sourceforge.net
Trying to figure out what this message means.
(1) Is this message coming from the pybloomfilter module or is it coming from somewhere in the guts of python?
(2) Is it trying to tell me it needs some module related to that sourceforge URL? Usually if a module is missing python gives me a traceback showing me where the exception occurred. But here I get no traceback, just the cryptic message above.

Apparently the pip install has problems. See
https://stackoverflow.com/questions/16174663/python-calg-library-in-windows-x64
I was able to solve the problem just like the stackoverflow gy did -- by installing with setup.py.
I noticed that pip said the version was 1.0, while the release tarball I got here is version 0.3.12. Is it possible that the pip package is unrelated to this repo?


KNN submission 2

The main differences between my KNN Submission 1 and KNN Submission 2 are:

In submission 2 I use a KNearestNeighborsRegressor to predict PE in records where there is no data. This gives me much more data with which to train the classifier.
In submission 1 I excluded the CROSS H CATTLE well from the training set, but in submission 2 I include it.
In submission 1 I excluded records where PHIND was greater than 40%, but in submission 2 I leave those records in the training set, in case rugose hole is an issue in the validation wells.
In submission 2 I basically did a bootstrapped grid search to optimize the n_neighbors parameter.

Hi Dan, thank you for this... it gets 0.495, so a bit down on before.

Thanks, Matt. That's disappointing! I am surprised that the score is so low given that my LOGO tests are performing really well. I would think that since my n_neighbors parameter is pretty high that I would not be over-determining, but in any case it appears that my KNN efforts are not generalizing very well.


genmodules.py: reformat according to PEP8 using Black

Use the Black tool with its default settings, reformat the script.

Thanks @amilonenv  looks good to me


fix v1 trap varBinds

Work around to correctly forward v1 TRAP varBinds

Let me merge this patch and do a followup so we have this resolved.


bug: java.util.concurrent.ExecutionException: org.eclipse.lsp4j.jsonrpc.ResponseErrorException: current user subscription  (...)

Plugin version: 5.3.27
IDE version: PY-233.13763.11
Stacktrace:
java.util.concurrent.ExecutionException: org.eclipse.lsp4j.jsonrpc.ResponseErrorException: current user subscription data not found

Error: current user subscription data not found
    at /snapshot/dist/agent.js
    at extractDataOrError (/snapshot/dist/agent.js)
    at /snapshot/dist/agent.js
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async /snapshot/dist/agent.js
	at java.base/java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:396)
	at java.base/java.util.concurrent.CompletableFuture.get(CompletableFuture.java:2073)
	at com.sourcegraph.cody.initialization.EndOfTrialNotificationScheduler.lambda$1$lambda$0(EndOfTrialNotificationScheduler.kt:44)
	at com.sourcegraph.cody.agent.CodyAgentService$Companion.withAgentRestartIfNeeded$lambda$1(CodyAgentService.kt:134)
	at com.intellij.openapi.application.impl.ApplicationImpl$2.run(ApplicationImpl.java:249)
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
	at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1$1.run(Executors.java:702)
	at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1$1.run(Executors.java:699)
	at java.base/java.security.AccessController.doPrivileged(AccessController.java:399)
	at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1.run(Executors.java:699)
	at java.base/java.lang.Thread.run(Thread.java:840)
Caused by: org.eclipse.lsp4j.jsonrpc.ResponseErrorException: current user subscription data not found

Error: current user subscription data not found
    at /snapshot/dist/agent.js
    at extractDataOrError (/snapshot/dist/agent.js)
    at /snapshot/dist/agent.js
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async /snapshot/dist/agent.js
	at org.eclipse.lsp4j.jsonrpc.RemoteEndpoint.handleResponse(RemoteEndpoint.java:209)
	at org.eclipse.lsp4j.jsonrpc.RemoteEndpoint.consume(RemoteEndpoint.java:193)
	at org.eclipse.lsp4j.jsonrpc.json.StreamMessageProducer.handleMessage(StreamMessageProducer.java:194)
	at org.eclipse.lsp4j.jsonrpc.json.StreamMessageProducer.listen(StreamMessageProducer.java:94)
	at org.eclipse.lsp4j.jsonrpc.json.ConcurrentMessageProcessor.run(ConcurrentMessageProcessor.java:113)
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
	... 1 more

hello @infantesromeroadrian 👋 we are sorry you are experiencing this issue 🙇 we are working on fixing it 🔧
I am closing this issue since we have a wrapper issue: https://github.com/sourcegraph/jetbrains/issues/681
We hope to release the fix within a week. I kindly ask you for some patience 🙏


Plugin does not work

Authentification is successful and a token comes in, but when sending a wav file, the answer is Error 403 Forbidden.
Real device with Android 7.1

How to fix?

The 403 would be coming back from the service, so that's likely unrelated to the error in the block you identified above.
What's the exception?  Is the audio length maybe exceeding the bounds of an Int32?  Can you provide a reproduction project?
You may want to try v2.0.0 as there were a few things fixed, but nothing specific to the issue you're experiencing.

Closing since it's been almost a month with no further details.  Feel free to reopen if you think there's a legit issue here and you can let me know how to reproduce it.


Improve node bundle

Export Palindrom as default export from node bundle,
exclude node_modules from node bundle

Let's discuss and implement de-bundling as a separate issue. Merging


Unable to use Simple.OData.Client in ASP.NET MVC application

I tried to do a simple example from Getting Started tutorial using MVC application. Here is the action method of a controller:
public ActionResult Index()
{
    var client = new ODataClient("http://packages.nuget.org/v1/FeedService.svc/");
    var packages = client.FindEntries("Packages?$filter=Title eq 'Simple.OData.Client'");

    return View();
}

After "client.FindEntries" is fired application is hanging with no response.
I also checked the behaviour in Console application with the same code (first two lines of the action method above) and it turned out that it works fine without any problems getting results from a remote endpoint.
Could you check please what the problem is?

I'm still uable to use it :(
I tried with simple example
public ActionResult Index()
{
ODataClient client = new ODataClient("http://localhost:55500/Dev/");
var languages = client.For().FindEntriesAsync().result;
        return View();
    }

Before executing and getting all languages it goes to return View() :(
and I do not get any data , please help me.

You have to wrap that client call inside a task.
var client = new ODataClient("http://localhost:6025/odata");
                 var res = Task.Run(async () =>

                {

                    var list =

                       await client.For<QueryableCustomer>()

                           .Filter(x => x.CustomerID == 10)

                           .FindEntriesAsync();

                    return list.FirstOrDefault();

                }).GetAwaiter().GetResult();

Thsnks,
Naresh
On Mar 31, 2015 5:44 AM, "ashuthinks"<EMAIL_ADDRESS>wrote:

I'm still uable to use it :(
I tried with simple example
public ActionResult Index()
{
ODataClient client = new ODataClient("http://localhost:55500/Dev/");
var languages = client.For().FindEntriesAsync().result;
    return View();
}

Before executing and getting all languages it goes to return View() :(
and I do not get any data , please help me.
—
Reply to this email directly or view it on GitHub
https://github.com/object/Simple.OData.Client/issues/24#issuecomment-88038133
.

Hi I try to use the Simple OData but I get error
var client = new ODataClient("http://packages.nuget.org/v1/FeedService.svc/");
var packages = await client.FindEntriesAsync("Packages?$filter=Title eq 'Simple.OData.Client'");
foreach (var package in packages)
{
Console.WriteLine(package["Title"]);
}
Here is the errro that I get
Error	1	The 'await' operator can only be used within an async method. Consider marking this method with the 'async' modifier and changing its return type to 'Task'.


Improved the Contact-Us page& submit button

issue #281
https://user-images.githubusercontent.com/94471189/185907828-7fc64181-2fa0-4e91-9c1b-144d71fea9d5.mp4

Background is too pinkish and doen't looks professional. Can you change it?
__        Summary: 🛠 This code needs a fix

Sure!

https://github.com/Susmita-Dey/Sukoon/pull/90 🙂

@Vanshiii203 Are you doing this for the second time?
__
  Summary: :question: I have a question

@Vanshiii203 Are you doing this for the second time?
__        Summary: ❓ I have a question

Yes, after my PR #90 was merged, there was another PR that was merged for this page(currently present) which did not have proper effects and transitions for the button.

@Vanshiii203 oh ok

@Susmita-Dey

@Susmita-Dey
I am not able to see the changes on the website, but on my system they work fine. Is this happening because of the broken code?
On Website-

On my system-


Add OpenSSF Best Practices Badge to README

/easycla

/easycla

@jmertic , unfortunately due to merge restrictions, this branch cannot be merged without first rebasing, and the auto-rebase tool is failing due to a missing EasyCLA status check -- are you able to rebase yourself?


ion-slides option cannot config paginationType

ion-slides in ionic 1.2.4
cannot config paginationType in options
$scope.options = {
    speed: 1000,
    pagination: '.swiper-pagination',
    paginationType: 'fraction'
  }

it alway to use bullets type

Thanks for submitting an issue with us! As this is more of a question you will be able to get a better answer over at our forum (https://forum.ionicframework.com/) or our slack channel (http://ionicworldwide.herokuapp.com/). Thanks again!


Update to go 1.19

What is missing?
Almost everyone in our team develops with go1.19 already, so forcing go.mod to have something older while actually compiling with it just feels silly. Also, go 1.19 is already few months old so it shouldn't pose any serious stability issues anymore.
At the same time, update operator-sdk to 1.25.1 (to keep up with the go 1.19) and to keep up with that, update to Kubernetes 1.25.
Why do we need it?
Environment

K8ssandra Operator version:
Insert image tag or Git SHA here

Anything else we need to know?:

I'm taking this because I need to upgrade cass-operator for #776, and the new version uses 1.19.


upgrade nerfacc to 0.3.x with CUB accel

White -- nerfacc 0.3.x.
Blue -- nerfacc 0.2.x.
nerfacc 0.3.x uses CUB to accelerate the accumulation (both fwd and bwd) when available (cuda toolkit >= 11.5). Test rays / secs got ~10% speed up. For some reason the training speed is slightly slower with nerfacc 0.3.x, which needs to be further investigated.
Note the CUB acceleration is more noticeable when the #samples per ray is less, so the gap for test rays / secs got larger when converge. But it's unclear what's the reason of the slow down during training.

The quality is numerically the same as before.


Fetch project applications based on a list of rounds

Requirements:
We will temporarily continue to have static data but instead of fetching the projects json file directly we need to fetch projects that applied to a list of rounds, the ones from GG19.
Out of scope:

having data that updates live during the rounds
having live data from any other round not in GG19

Design sketch:

select a list of round contract addresses
for each round fetch the applications file (https://indexer-production.fly.dev/data/424/rounds/0x1488817b0137CA16F35D72A5F2A7c095c1Ec9166/applications.json)
filter only accepted applications (status: APPROVED)
verify that application.metadata.metadata.project already contains the same data we have in the original project file
export the project data + other fields that we will use for filters and sorting

id
projectId (which is the keccak256 of chainId, projectRegistryAddress, projectNumber)
amountUSD
votes
roundId

merge the applications from all the rounds in one single file

Continued in #18


A great project, the source code author worked hard.

Changing "face_parsing" and "face_tracking" to the algorithms "Segment Anything" and "Track Anything", that were just released this year will git greatly improve the effect.
https://github.com/Fictionarry/ER-NeRF/assets/74521932/3549d467-22fd-41b2-9ce2-a247c920cd48

Please clarify.
My training video is about digital people.
Because I am relatively lazy, I didn't go to find a model to shoot on my own.

May I ask how the "Track Anything" model fits into 3DMM modeling and generates the transformation matrix

the "Track Anything" is different from 3DMM face tracker, so I think it can not replace the face tracker

And in the NeRF training process, only the face frame and the lower half area frame are actually used.


feat: added minimal development yaml

Description
Added a development-minimal file and adjsuted normal development.yaml file
Fixes #1232
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?

development-minimal is tested for a couple of hours and by @amine-amaach
development.yaml is not tested yet (@DaruZero can you do that?, just try to install it, check whether all containers start up and then check whether the ACL thing works #1232 and whether an anonymous user can access all data (target: he should be))

Codecov Report

Merging #1233 (2ae7ecd) into main (461ad07) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1233   +/-   ##
=======================================
  Coverage   12.69%   12.69%
=======================================
  Files          29       29
  Lines        8135     8135
=======================================
  Hits         1033     1033
  Misses       7030     7030
  Partials       72       72

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

Please take over @DaruZero!


redo(ticdc): use uuid in s3 log file to avoid name conflict

What problem does this PR solve?
Issue Number: ref #5486
What is changed and how it works?

If multiple redo log files contain event with the same commit-ts, the file name will be conflict and lead to data loss
Since the unix timestamp is used as random filename and no other practical use, we simplify add a uuid into redo log file name.
Move github.com/pingcap/tiflow/engine/pkg/uuid package to github.com/pingcap/tiflow/pkg/uuid

Check List
Tests

Unit test
Integration test

Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note
Add uuid suffix to redo log file name to prevent name conflict, which may cause data loss.

/run-all-tests

/run-all-tests

/run-all-tests

/merge

/merge

/run-verify


fix: Adding environment variable

what

Setting environment variable AWS_EC2_METADATA_DISABLED: true as a solution

why

github actions is unable to push artifacts to s3 because of an error with the awscli.

references

https://github.com/aws/aws-cli/issues/5234#issuecomment-705831465
related to https://github.com/cloudposse/terraform-aws-ses-lambda-forwarder/issues/13

/test all


runtime: GODEBUG gctrace bug with time ran on Mac

What version of Go are you using (go version)?
go version go1.9rc2 darwin/amd64
Does this issue reproduce with the latest release?
Yes, only in 1.9 and since beta.
What operating system and processor architecture are you using (go env)?
GOARCH="amd64"
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"

macOS Sierra  Version 10.12.6

What did you do?
Using this program:
https://github.com/ardanlabs/gotraining/tree/master/topics/go/profiling/project
Build the code and run it using:
$ GODEBUG=gctrace=1 ./project > /dev/null
Then open the browser and run a search. Be sure to check the three boxes for cnn, bbc and nyt and you get some results.
http://localhost:5000/search
This will produce a gctrace immediately.
What did you expect to see?
gc 1 @1.186s 0%: 0.092+0.47+0.038 ms clock, 0.37+0.15/0.81/1.8+0.15 ms cpu, 4->4->1 MB, 5 MB goal, 8 P
What did you see instead?
gc 1 @18446653480.186s 0%: 0.092+0.47+0.038 ms clock, 0.37+0.15/0.81/1.8+0.15 ms cpu, 4->4->1 MB, 5 MB goal, 8 P

cc @aclements

It took me some work, but I was able to reproduce this on a gomote
git checkout go1.9rc2
VM=$(gomote create darwin-amd64-10_12)
gomote push $VM
gomote ssh $VM
cd $GOROOT/src
./make.bash
cd ../bin
PATH=$PWD:$PATH
go get -d github.com/ardanlabs/gotraining/topics/go/profiling/project
cd $GOPATH/src/github.com/ardanlabs/gotraining/topics/go/profiling/project
go build
GODEBUG=gctrace=1 ./project > /dev/null

In another terminal:
gomote ssh $VM
curl -d cnn=on -d nyt=on -d bbc=on -d term=test http://localhost:5000/search

Ah, the problem is we have two different time bases in the runtime as of e4371fb179ad69cbd057f2430120843948e09f2f. That commit made nanotime() return a value relative to runtime.startNano. However, runtime.main does runtimeInitTime = nanotime() before runtime_init(), which sets startNano = nanotime(). The gctrace times are computed as nanotime() - runtimeInitTime, so when the time base changes, this no longer makes sense.

Re-opening for cherry-pick to Go 1.9.1

Is this worth cherry picking?  It seems a very minor problem.

Rick and I pretty frequently ask people for gctrace output when debugging performance issues. This could make that harder to interpret. It's also a simple fix, so I think whenever 1.9.1 happens we might as well include it.

I am teaching this stuff and now that 1.9 has been released, this bug makes things difficult for training. So please consider getting this in sooner rather then later.

On Aug 25, 2017, at 1:35 PM, Austin Clements<EMAIL_ADDRESS>wrote:
Rick and I pretty frequently ask people for gctrace output when debugging performance issues. This could make that harder to interpret. It's also a simple fix, so I think whenever 1.9.1 happens we might as well include it.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/golang/go/issues/21554#issuecomment-324987574, or mute the thread https://github.com/notifications/unsubscribe-auth/ACLKRcnSRKERiW9tx1J2gDcoFouGe2Bgks5sbwXHgaJpZM4O-kOz.

OK for Go 1.9.2.

go1.9.2 has been packaged and includes:

CL 58690

The release is posted at golang.org/dl.
— golang.org/x/build/cmd/releasebot, Oct 26 21:09:07 UTC

Just tried it out on darwin and it looks good!  Thank You.
Is there anyway this can get fixed as well for 1.9? It is broken on both darwin and linux.
https://github.com/golang/go/issues/21697

@ardan-bkennedy, this isn't really the place to ask about the other issue. If you're interested in having #21697 fixed in 1.9, you should argue that on that issue (and understand that whether or not the fix gets backported also depends on the risk involved in the actual fix).

New to all this so thanks for laying out the policy I am supposed to follow. It won’t happen again.


ERR_CERT_AUTHORITY_INVALID

Is anyone else seeing this error on HTTPS endpoints after upgrading to Chrome 58? It appears that Chrome has stopped accepting self-signed certificates. It only accepts insecure certificates on localhost by turning on this flag
chrome://flags/#allow-insecure-localhost

Does this mean pow is no longer usable on localhost via the HTTPS protocol?

Same problem here. See https://github.com/webpack/webpack-dev-server/issues/854.
And see my question at Super User if you're using Chrome on Ubuntu.


answers all questions from assignment 2 and 3

What changes are you trying to make? (e.g. Adding or removing code, refactoring existing code, adding reports)
What did you learn from the changes you have made?
Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
How were these changes tested?
A reference to a related issue in your repository (if applicable)
Checklist

[ ] I can confirm that my changes are working as intended

A2: Complete
Q4, in order to get the correct RSME of roughly 3.18, consider using "mean_squared_error" over "np_mean".

A3 complete


because of prior anticipation, support requires only doc and style tw…

…eaks
Signed-off-by: sklump<EMAIL_ADDRESS>

Codecov Report

Merging #457 into master will not change coverage.
The diff coverage is n/a.


PixIV Support

I'd love to see Pix IV support added to the downloader. It's one of the best sources for original art content online, NSFW and otherwise

See #738 (also partially #917).
I'll be closing this as duplicate, but if you have any info about the API, or if you want to describe your use-case on Pixiv (searching by tag, searching users, downloading users artworks, etc.), please do comment on #738 👍


Does Kong provides portal for consumer to view analytics and other information regarding the Api usages?

Hi,
We have seen Kong provides the Admin and Developer portal, But does it provide the Portal for a consumer to view the analytics and usage of API they consumed?
Appreciate your help.
Thanks,
Keyur

Github issues are reserved for bug reports, please.
For questions about features and functionality, like your question, please post in Kong Nation.


[GLUTEN-1632][CH]Daily Update Clickhouse Version (20230716)

Auto commit by gluten daily build, please check the build status and merge it if it's green.

HI @lwz9103 do we need to keep some old PRs (2353, 2335 and others)?
Not sure whether we can add a dependabot to automically check version bump-up?

Compatible with current gluten


Feature: Case insensitive search on String fields

Looking at the commit history, I'm not sure what happened and what made it so messed up (like showing commits that were supposed to be already merged etc.), but the actual diff looks ok. (It looks like commits I made earlier, but then I deleted the repo after messed up rebase and started fresh.. somehow they survived).
This PR implements case insensitive searching on String fields. Since Prisma 2.8.0 and newer, the API exposes a mode property on StringFilter and StringNullableFilter, that lets the user specify if he wants to filter by default (which corresponds to the database collation and its default sorting/filtering) or insensitive (this is reflected in an enum added in that version):
enum QueryMode {
   default,
   insensitive
}

I updated the getFilters() function to check if the user's Prisma version supports this functionality (checks for the existence of the enum in introspection query, and if the string filters are actually using the enum), and if yes, considers all String filters as case insensitive. If the user has <= 2.7.0 Prisma, it reverts back to the original pseudo-case insensitive implementation.
Also, with this update, I have to treat StringFilter and StringNullableFilter differently from their Nested* variants, because Nested variants don't have the mode property (but those input objects are always nested inside the original String filters which do have them, so I guess the information is propagated into its nested filters).
Because the test schema already is running on sufficient Prisma version, I had to update old tests so it expects the proper where object.
I also moved some logic into its own functions, so a bit of refactoring.
As always, open to suggestion and feedback 🙂

@macrozone
I apologize for reminding you, but have you had any time to take a look at this? 🙂 Or is there anything you'd like me to change?

@macrozone
I apologize for reminding you, but have you had any time to take a look at this? 🙂 Or is there anything you'd like me to change?

looks fine, but commit history seems odd.
I don't want to get too picky with commits, but maybe try to rebase it:
git rebase -i origin/master
shows you an "interactive" rebase. If you are using vscode you can also configure it as a git tool (https://stackoverflow.com/questions/30024353/how-to-use-visual-studio-code-as-default-editor-for-git), that helps a bit to get used to it, in particular if you are not familiar with vim.
its also possible to squash the pull request into one commit directly here in github.
basically the commit should show what has been added relative to the main branch. E.g. "fix string filter, refactor" should not appear in the log as you fixed your own change.
i guess the one commit should be:
feat: string fields use case insensitive mode if available

Yes, I tried rebasing in the previous PR, but I think I messed up somehow so I decided to backup the changed files, delete entire fork and start over. How the commits survived when I forked the repo clean and started over, I have no idea. Also, doesn't the fact that it's already pushed on origin (my fork)?

ok, ill fix it myself then

I'm sorry for the trouble and thank you for merging. I'll try to fix it next time so it's less problems for you.

no worries, i just tried the "merge and squash" feature of github, that did the job. :-)
getting used to rebasing is still something that i would recommend!

Will try to educate myself, I usually tried to avoid it because I've heard of horror stories when rebase went very wrong 😄

:tada: This PR is included in version 4.2.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

Will try to educate myself, I usually tried to avoid it because I've heard of horror stories when rebase went very wrong 😄

true, it can go very wrong ;-) thats why its good to practise.
I also thought for a long time that its not worth the effort and merging was simpler and better. But after getting use to it, i think it helps you to be more aware of the changes you do and be more clear about these changes. It requires more discipline, but it also teaches you more discipline.
The challenge i had was, that merging and rebases take a different perspective. Usually you rebase, when the main branch is ahead of where you started your branch. Merging in this case just takes any new change in the main branch and merges it into your current branch (and leaving a commit). With rebasing, you switch the perspective. you start with the main branch and try to re-apply your changes on that, as if the main branch wasn't ahead of your branch.
The difference gets obvious when there are some conflicts, notoriously the meaning of "their" changes and "our" changes are swapped if you compare rebasing to the main branch and merging in the main branch, that can be confusing.
The "dangerous" aspect is, that rebasing needs a force push. thats the one aspect i also do not like. force push means that you discard any changes on the remote and replace them with your changes. This can go wrong on branches where multiple people are working on, so in general never force push on the main branch, this is usually disabled on github and gitlab for this reason.

:tada: This PR is included in version 6.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


DRAFT - feat/188195

DRAFT - Checking I don't have 200 files changed

Could we stick the 'retry' on error work in this @Zac-AND-Digital ?


Update Docker base images

Upgrade:

Prometheus 2.31.0 -> 2.31.1 changelog
Jaeger 1.27.0 -> 1.29.0 changelog 1.28.0, 1.29.0
Red Hat UBI 8.4 -> 8.5
UBI Toolset 1.15.14-3 -> 1.15.14-18

Running full test suite on https://github.com/couchbaselabs/observability/actions/runs/1572150268