Windows install runs into errors

after manual install instructions and
go build
I receive the following errors:
# github.com/jmorganca/ollama/readline
readline\readline.go:199:12: undefined: syscall.Kill
readline\readline.go:199:28: undefined: syscall.SIGSTOP

After messing with readline.go I just manage to get a .exe file that doesn't work
@deadcoder0904 or anyone who compiled on windows and got a working executable, could you describe how you did it?

i didn't try to install it. didn't do it manually either.

Did you use wsl on windows?

@csaben there was a change that added some unix specific system calls so the development build of windows broke. Just opened a fix.

Did you use wsl on windows?

no. couldn't get wsl working for sometime so i dropped it. dont know why i need it as terminal opens fast enough nowadays.


epinio logs myapp --staging should not show linkerd container logs

Right now it does:
...
🕞  [24ab9e2f3250887e-run-kbvbp-pod-8hfbw] linkerd-proxy 2021/06/23 09:33:11 Exiting...
🕞  [24ab9e2f3250887e-run-kbvbp-pod-8hfbw] place-tools 2021/06/23 09:33:00 Copied /ko-app/entrypoint to /tekton/tools/entrypoint
🕞  [24ab9e2f3250887e-run-kbvbp-pod-8hfbw] linkerd-init 2021/06/23 09:33:01 Tracing this script execution as [1624440781]
🕞  [24ab9e2f3250887e-run-kbvbp-pod-8hfbw] linkerd-init 2021/06/23 09:33:01 current state
🕞  [24ab9e2f3250887e-run-kbvbp-pod-8hfbw] linkerd-init ------------------------------------------------------------
🕞  [24ab9e2f3250887e-run-kbvbp-pod-8hfbw] linkerd-init 2021/06/23 09:33:01 :; iptables-save

...

Looks like it was only fixed for push https://github.com/epinio/epinio/blob/main/acceptance/apps_test.go#L93 and not for logs.

Isn't this going through the same server API ?

Confirmed. The output from logs --staging contains linkerd related lines, whereas the logs coming out of push do not, while they should ostensibly the same logs.

log --staging is cli/apps.go -> client AppLogs (with StageId) -> API StagingLogs -> ApplicationsController{}.Logs -> streamPodLogs -> application.Logs
push logs ... cli/push.go -> client Push -> client AppLogs (with stageId) -> API StagingLogs -> s.a
So. These are the same, or rather, should be.
:bulb: (I believe). The log system auto-attaches to the pods and their containers to stream logs, using various selectors.
I could believe, and theorize, that during push the linkerd sidecar containers are coming late to the game and are thus not attached to for logging. Then, when I run logs --staging later the sidecars exist (for some time) by then, thus are found by the selectors, and their logs are added to the stream.
Except ... The tailer is configured using
ExcludeContainerQuery: regexp.MustCompile("linkerd-(proxy|init)"),

... One difference. Push likely has follow set, thus StreamLogs.
On the other side log --staging is without follow ... FetchLogs.
That looks to be a difference in application.Logs
I have to delve more where/if that makes the difference.

Yes, that looks to be the difference.
StreamLogs sets up a Watch. This takes the ExcludeContainerQuery, and thus never reports the linkerd containers for logging.
See https://github.com/epinio/epinio/blob/main/helpers/kubernetes/tailer/setup.go#L108
FetchLogs OTH does not Watch at all. It simply iterates over all the Container for the selected pods.
See https://github.com/epinio/epinio/blob/main/helpers/kubernetes/tailer/setup.go#L76-L81
FetchLogs has to be rewritten to perform the same (Exclude)ContainerQuery checks as done by the Watch.


Do not log account passwords

In reviewing results of an execution, the ArcGISConfigure--Verbose.txt file has passwords logged to the file.  This is generally not a security best practice and logging passwords should be avoided.
Here is a sample (redacted):

[SERVER]:                            [[ArcGIS_Service_Account]ArcGIS_DataStore_RunAs_Account] RunAsAccount Username:- DOMAIN\USERNAME
[SERVER]:                            [[ArcGIS_Service_Account]ArcGIS_DataStore_RunAs_Account] Install Dir for ArcGIS Data Store is C:\Program Files\ArcGIS\DataStore
[SERVER]:                            [[ArcGIS_Service_Account]ArcGIS_DataStore_RunAs_Account] Just Checking : - /username DOMAIN\USERNAME /password "CLEAR_TEXT_PASSWORD"

@pfoppe this is an aberration. we will fix this in the upcoming release.

Thanks!

@scma-esrich FYI

@scma-esrich FYI

Thanks, @spitzerr. I already noticed that.

Please re-open.  I found another one on the data store upgrade at 10.7.1:
...
[<SERVERNAME>]:                            [[ArcGIS_DataStoreUpgrade]DataStoreConfigUpgrade] Retrieved server token successfully
[<SERVERNAME>]:                            [[ArcGIS_DataStoreUpgrade]DataStoreConfigUpgrade] Relational Replication Role - PRIMARY
[<SERVERNAME>]:                            [[ArcGIS_DataStoreUpgrade]DataStoreConfigUpgrade] relational
[<SERVERNAME>]:                            [[ArcGIS_DataStoreUpgrade]DataStoreConfigUpgrade] C:\Program Files\ArcGIS\DataStore\tools\configuredatastore.bat https://<SERVERNAME><DOMAIN>:6443/arcgis <PORTAL_ADMIN_ACCOUNT> <PORTAL_CLEAR_TEXT_PASSWORD> D:\ArcGISDataStore --stores relational
[<SERVERNAME>]:                            [[ArcGIS_DataStoreUpgrade]DataStoreConfigUpgrade] Output of execution:-
...

Thanks!

And Another...
[<SERVER>]:                            [[ArcGIS_Install]DataStoreUpgrade] Installing Software using installer at \\server\share\InstallMedia\Esri\10.7.1\ArcGISDataStore\setup.exe and arguments /qb USER_NAME=<USERNAME> PASSWORD=<PASSWORD>

And Another...
[<SERVER>]:                            [[ArcGIS_Install]ServerUpgrade] Installing Software using installer at \\server\share\InstallMedia\Esri\10.7.1\ArcGISServer\setup.exe and arguments /qb USER_NAME=<USERNAME> PASSWORD=<PASSWORD>

Fixed with v2.1.1!

I searched through the logs from a new v10.7.1 install with arcgis-powershell-dsc v2.1.1 and was unable to find any passwords being logged.  Thanks!


feat: ClientProvider.cache as an interface to support external cache (e.g. redis)

Describe the feature request
At present it looks like the client provider cache field is tightly coupled to the gocache.
If a user wants to also use an external/shared/distributed cache then this isn't possible.
It would be nice to allow more flexibility to the user in which caching solution they wish to use.
Why do you personally want this feature to be implemented?
to allow flexibility in choice of cache solution.
How long have you been using this project?
No response
Additional information
No response

@TwiN is this feature still a possibility?

@c-nv-s I had started working on the side a bit a few months ago, but this isn't really a priority for me at the moment.
Feel free to give a shot at implementing it yourself if you'd like.

I've pushed the work I currently have and included the work left to do, in case you or somebody else wants to try it to confirm that it fits your need(s).
https://github.com/TwiN/g8/pull/12

Thanks for this... so you just need to update the go.mod file then I can pull it and start using this?

@c-nv-s You should be able to use the master branch as a version in your go.mod, see https://stackoverflow.com/questions/56408476/how-can-i-get-master-branch-of-a-dependency-when-using-go-modules
I haven't had the opportunity to test it myself, hence why I haven't released it yet, but if you could give it a try, that'd be great.

@c-nv-s I've just release it in v2.0.0


Design the contact form and provide navigation

Hello rohan, can i work on this issue, please assign this issue to me , under the label of GSSoc

this has been done


Fix cyclic intersection inference

With the addition of optional keys inferred from chained values, cyclic scoped intersections are inferred as never (these worked prior to 2.0.0-rc.5).
It's unclear if it's a limitation of TS. I expect types like this are relatively rare in practice, so I'm willing to sacrifice them for chainable optionals/defaults. However, if it's possible to have both, that would be ideal!
Here are the removed tests that started failing that should be reenabled if this is fixed:
it("cyclic intersection", () => {
  const types = scope({
    a: { b: "b&a" },
    b: { a: "a&b" },
  }).export();
  attest(types).type.toString.snap(`Module<{
	a: { b: { a: { b: cyclic; a: cyclic }; b: cyclic } }
	b: { a: { b: { a: cyclic; b: cyclic }; a: cyclic } }
}>`);
});

it("intersect cyclic reference", () => {
  const types = scope({
    arf: {
      b: "bork",
    },
    bork: {
      c: "arf&bork",
    },
  }).export();
  attest(types.arf.infer).type.toString.snap(
    "{ b: { c: { b: cyclic; c: cyclic } } }"
  );
  attest(types.bork.infer).type.toString.snap(
    "{ c: { b: cyclic; c: cyclic } }"
  );

  const expectedCyclicJson =
    types.arf.internal.firstReferenceOfKindOrThrow("alias").json;

  attest(types.arf.json).snap({
    domain: "object",
    required: [
      {
        key: "b",
        value: {
          domain: "object",
          required: [
            {
              key: "c",
              value: expectedCyclicJson,
            },
          ],
        },
      },
    ],
  });
  const a = {} as typeof types.arf.infer;
  const b = { c: {} } as typeof types.bork.infer;
  a.b = b;
  b.c.b = b;
  b.c.c = b.c;

  attest(types.arf.description).snap("{ b: { c: arf&bork } }");
  attest(types.bork.description).snap("{ c: arf&bork }");

  attest(types.arf(a)).equals(a);
  attest(types.arf({ b: { c: {} } }).toString())
    .snap(`b.c.b must be an object (was missing)
b.c.c must be an object (was missing)`);

  attest(types.bork.json).snap({
    domain: "object",
    required: [
      {
        key: "c",
        value: expectedCyclicJson,
      },
    ],
  });
});

Nevermind, I found another solution.


:sparkles: Better way to register guild commands

Bot currently checks every single guild the client is registered to when getting guild commands. Bad obviously, think the best way to fix it is to let the user specify the guilds or something. I checked the discord docs and didn't see anything that would fix the issue.

Closed due to depreciation, thank you for your effort ♥


implements login --authType browser. solves #1979

I managed to finalize the new authentication method through a browser instance.
You can call it by using m365 login --authType browser
This authentication method will try to open a browser instance using the library open. After you successfully authenticate on Azure AD, the necessary authorizationCode operation is executed to retrieve the required tokens.
This approach is working well for all devices requiring conditional access and an interactive authentication.
Before pushing it to production ensure that http://localhost is added to the PnP Azure AD application.

You can test it using my dedicated Azure AD multi-tenant app using this command: m365 login --authType browser --appId f98c87e8-8b5e-41c7-9815-c97b10220d32

Coverage remained the same at 100.0% when pulling 65ebdadc697f3b862c102923d8327cfc78eb7c42 on plamber:main into 5dac8ec9ca4e1e83373c824cfd649b52a384891f on pnp:main.

Coverage remained the same at 100.0% when pulling 65ebdadc697f3b862c102923d8327cfc78eb7c42 on plamber:main into 5dac8ec9ca4e1e83373c824cfd649b52a384891f on pnp:main.

Awesome! Will review it asap! 👏

Awesome! Will review it asap! 👏

Merged manually. Thank you! 👏


TextureAtlas Slow Performance

Issue details
TextureAtlas objects take far too long to create. This is creating a major bottleneck in my application right now because I cannot add more characters until I resolve this problem.
An .atlas file with 500 lines and 4 associated images with dimensions less than 2048x2048 takes roughly 100-200 milliseconds. This needs to be improved as I am initializing roughly 20-24 atlases for a total overhead of 5000-7000 milliseconds.  Using a single atlas does not resolve the problem.
Reproduction steps/code
AssetManager manager = new AssetManager(new InternalFileHandleResolver());
manager.load("path/to/atlas", TextureAtlas.class);
manager.finishLoading();
Version of LibGDX and/or relevant dependencies
1.9.8
Stacktrace
None
Please select the affected platforms

[x] Android
[ ] iOS (robovm)
[ ] iOS (MOE)
[ ] HTML/GWT
[ ] Windows
[ ] Linux
[x] MacOS

Please attach a http://sscce.org/

20 x 2048 x 2048 x 4 = about 320 MB, are you sure the bottleneck is the 500 lines in Atlas file or the huge amount of texture ?

Why not use AtlasManager's asynchronous loading mechanism instead of calling finishLoading()? Do you really need all of those texture atlases immediately?

@MobiDevelop Yes I need the assets immediately. On initialization I draw a 'level' scene as the background while the end-user is authenticating. This provides a rich scene and a good first impression for the end-user. It would not be ideal to draw a 'loading' scene while the assets are being created asynchronously.

I see, well, reality is that things take time. Immediately loading 20 texture atlases with each having 4 images of 2048 x 2048 is absolutely going to take substantial time no matter how 'optimized' the reading portion is.

@MobiDevelop It's possible you're right but considering there hasn't been any changes, let alone optimizations, to the TextureAtlas class in years, it's likely some improvements can be made.

The expense is uploading to the gpu, not parsing atlas data.  If you can provide standalone tests that demonstrate an issue specific to TextureAtlas compared with say a purely native approach to uploading a bitmap then there is probably something we can do. But until that is presented, this is pretty much expected behavior when uploading many large textures all at once.

@JasonMacKeigan sorry i meant 320 MB of texture data to inflate and upload to GPU. 79 MB of compreed data files still huge compared to a 500 lines json file :-)

Upgrade or add atlas file?
On Mon, Jul 9, 2018, 5:01 AM JasonM<EMAIL_ADDRESS>wrote:

Issue details
TextureAtlas objects take far too long to create. This is creating a major
bottleneck in my application right now because I cannot add more characters
until I resolve this problem.
An .atlas file with 500 lines and 4 associated images with dimensions less
than 2048x2048 takes roughly 100-200 milliseconds. This needs to be
improved as I am initializing roughly 20-24 atlases for a total overhead of
5000-7000 milliseconds. Using a single atlas does not resolve the problem.
Reproduction steps/code
`
AssetManager manager = new AssetManager(new InternalFileHandleResolver());
manager.load("path/to/atlas", TextureAtlas.class);
manager.finishLoading();
`
Version of LibGDX and/or relevant dependencies
1.9.8
Stacktrace
None
Please select the affected platforms

Android
iOS (robovm)
iOS (MOE)
HTML/GWT
Windows
Linux
MacOS

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/libgdx/libgdx/issues/5302, or mute the thread
https://github.com/notifications/unsubscribe-auth/AlorWIBWqf1VrQgPHZFAS55NPRJBod2iks5uExwEgaJpZM4VHVP7
.

so many assets needs a loading screen. maybe show a simple loading screen to the authentication scene? thats the most obvious response. (Loading screen have existed for decades dude and for a reason)

@Lestat Just because it was done a decade ago, doesn't mean it was right. The last thing I want new end-users to do is wait for a loading screen to finish before they can access the game. I understand that there are limitations, however it is worth creating a discussion for. If it's not possible to reduce the time it takes then yes, I will ultimately have to load assets in the background while I concurrently draw a dummy loading screen.

Feel free to reopen if you can provide mode info for us to investigate, but currently marking this as non issue.


Improve behavior for queries with multiple pages

Some sitewise queries have very small number of results in a single page -- this can require many iterations to get valuable results.  With https://github.com/grafana/iot-sitewise-datasource/pull/29 we make multiple fronted requests to fill a graph.  These are mostly very small and fast:

Rather than working directly with the sitewise page size, we can/should aim to collect multiple pages before returning results.  This will have a few benefits

reduced overall response times (user experience)
better ability to cache results (new feature coming in enterprise/pro)
alerting will only work with the first result (unless we change the infra dramatically)

We could approach this in two ways, either:

Fill a consistent buffer size on the backend.  PRO: predictable
Collect results for an amount of time. PRO: keeps streaming experience.

Lets try both approaches and see what feels best.

good for now


Improve overview section of tutorials page

This PR improves the Overview section of  the tutorials page making it more informative about the contents of the tutorials.

@huan I have tried making the overview section of the tutorials page more informative. Let me know what you think.

Thank you very much for making the overview more informative!


feature request: accept string arguments?

I'm building a browser app. Since the keys and messages are buffers, they're a bit tricky to save in localStorage or JSON etc.
Rather than me (the application developer) have to build a serialization / deserialization strategy, could we automatically cast strings to buffers? i.e.
exports.sign = function (message, secretKey) {
  /* --- NEW BIT --- */
  if (typeof message === 'string') message = new Buffer(message, 'utf8')
  if (typeof secretKey === 'string') secretKey = new Buffer(secretKey, 'hex')
  /* --- ^^^^^^^ --- */
  var signature = alloc(sodium.crypto_sign_BYTES)
  sodium.crypto_sign_detached(signature, message, secretKey)
  return signature
}

That way I won't have to include const { Buffer } = require('buffer') in my webpack config, or however frontend works these days.
If you are OK with the idea I'll put in a PR.

Or should I just make a new wrapper module that uses strings for everything?

Feel free to PR that. This module is kinda high level anyway

gah wait now I can't decide whether it should use hex or base64 for the keys

Well you could check the length and know which it is. This function calculates the base64 length (bytes) => (bytes * 4 / 3 + 3) & ~3, this calculates the hex length (bytes) => bytes * 2 :) Though I don't like to have keys in strings, but that's just my opinion


Add Login button

close #713
Hi, I've successfully created a new login button, please check

Hi @PoorviShetty, merge conflicts are resolved, please check


dialogflow

First of all, thank you for developing the Wahticket application which has integrated Dialogflow. There are 2 questions and I hope you answer them :)

When a message comes in and I have selected the queue, in the ticket menu I can't see the message, is this related to dialogflow? because I haven't created any projects on dialogflow
In dialogflow, can you provide an example of the JsonContent? I am very unfamiliar with this matter and I hope you can provide examples and a little explanation of the flow.

Thank You

Hello! I'm glad to hear that this project is useful for you ;)
Firstly, whether the message appears in the menu or not has no relation to DialogFlow or the creation of a project. I believe it might be possible that you haven't added the queue to the user who is using it.
Regarding the JSON, there are 4 fields to be filled in. The first one is just the Name, which can be any string of your choice. The second one, Language, needs to be the language defined by you in your DialogFlow project. The third is the Project Name, which should be exactly the same as the name of the DialogFlow project. This name usually comes within the configuration JSON under the project_id field. I will send you an example of how this JSON looks:
{
  "type": "service_account",
  "project_id": "project-name",  // Project name I mentioned to be placed in the form
  "private_key_id": "KEYID",
  "private_key": "-----BEGIN PRIVATE KEY-----\nYOUR KEY\n-----END PRIVATE KEY-----\n",
  "client_email": "YOUR EMAIL",
  "client_id": "YOUR ID",
  "auth_uri": "https://accounts.google.com/o/oauth2/auth",
  "token_uri": "https://oauth2.googleapis.com/token",
  "auth_provider_x509_cert_url": "https://www.googleapis.com/oauth2/v1/certs",
  "client_x509_cert_url": "GOOGLE CERT URL"
}

To create this JSON with the Keys, it is necessary to go through a sequence of configurations on the Google site. I will leave a video for you to use as a reference: Google Service Account Setup Video.
I hope this helps, and feel free to ask if you have more questions!

I'm closing this issue due to inactivity.


Jupyterhub image build error

Trying the 9th release of the project image, my JH gave this error:

Steps to reproduce:

Go to https://jupyterhub-odh-jupyterhub.apps.odh-cl1.apps.os-climate.org/
Select AICoE OSC demo image

it seemed to create fine for me, can someone else confirm the same error?

i m not authorized to use the URL, sorry cant reproduce it.

it seemed to create fine for me, can someone else confirm the same error?

Could you please try again? We had to revert the image to an older version for a demo, maybe that's why it worked for you. Now the image is back to the latest, and broken version.

@HumairAK @harshad16 I tried building the image locally and it was built without any errors. However, when I ran it, the Jupyterhub instance on my localhost showed this site can't be reached. Probably because of the same reason...

@Shreyanand that seems to suggest an issue with the image and not an ops related issue, right? @4n4nd do you have any idea here?

yeah this is an issue with the image.
@harshad16 can confirm

I will check and re-confirm on this :+1:

Hey folks, so it seems that removing jupyter and jupyterlab from Pipfile/Pipfile.lock, and then building the image fixes this issue (tested only locally). I can update the Pipfile on the repo and re-release and see if it works.

@HumairAK @harshad16 I tried building the image locally and it was built without any errors. However, when I ran it, the Jupyterhub instance on my localhost showed this site can't be reached. Probably because of the same reason...

I have tried to build the image with no configuration change. and ran it on system it runs successfully.

Hey folks, so it seems that removing jupyter and jupyterlab from Pipfile/Pipfile.lock, and then building the image fixes this issue (tested only locally). I can update the Pipfile on the repo and re-release and see if it works.

very good point, why were these package installed explicitly?

very good point, why were these package installed explicitly?

IIRC while we were testing image build locally, one of the training notebooks wouldn't work until we had ipywidgets installed, which in turn required these packages. But I think for now we should be able to go without these included in Pipfile.

can we close this issue?

Do you folks think others would benefit from from these resolution steps in the future? If so can we get a small contribution to the JH docs runbook here: https://github.com/operate-first/apps/blob/master/docs/odh/jupyterhub/runbook.md ?  :smiley:

This link is now 404: https://github.com/operate-first/apps/blob/master/docs/odh/jupyterhub/runbook.md
Pretty sure that the notebook requiring ipywidgets is the (interactive) annotation tool.

The latest version of the image run without any errors.


feat(block): Created v5 Fulcrum /block endpoints in bch-api

PR related to this trello task --> https://trello.com/c/1LbZiins

:tada: This PR is included in version 1.38.0 :tada:
Your semantic-release bot :package::rocket:


Replace and delete Network ACL Entries

Hello,
Please find an implementation for ec2.delete_network_acl_entry and ec2.replace_network_acl_entry.
With tests.
Hope this helps.
Note: could you please give me some quick steps to build/run on Windows? Thanks.

Coverage increased (+0.01%) to 93.715% when pulling d1789624c4d283f547dcc4feb6bd7d49a642ae2f on JeromeBosman:master into af9c65c5cc929ccce52b6218b23662aac1d1ccb8 on spulec:master.

Looks great, thanks for your help!

np, would do more if I knew how to:

build the lib locally so I can deploy my fork
run the tests locally, so I don't use Travis to check my code is
working (which I did this afternoon)

I'm on Windows.
Jerome
On Sun, May 14, 2017 at 9:15 PM, Steve Pulec<EMAIL_ADDRESS>wrote:

Merged #940 https://github.com/spulec/moto/pull/940.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/spulec/moto/pull/940#event-1081392911, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AIGehwmo2owbMer3B3zx7y__y3SWQW6wks5r52DGgaJpZM4NaW8z
.

What happens after you git clone and run make init?

last lines of make init:
Installing collected packages: cookies, dicttoxml, pyaml, moto
Found existing installation: moto 0.4.31
Uninstalling moto-0.4.31:
Successfully uninstalled moto-0.4.31
Running setup.py develop for moto
Successfully installed cookies-2.2.1 dicttoxml-1.7.4 moto pyaml-16.12.2
On Sun, May 14, 2017 at 10:16 PM, Steve Pulec<EMAIL_ADDRESS>wrote:

What happens after you git clone and run make init?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/spulec/moto/pull/940#issuecomment-301340601, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AIGeh-Fa6zK-LVd4qzENbCb5DhozkClRks5r529FgaJpZM4NaW8z
.

ok, building & tests running locally
thanks for the hint
J
On Sun, May 14, 2017 at 11:28 PM, Jerome Bosman<EMAIL_ADDRESS>wrote:

last lines of make init:
Installing collected packages: cookies, dicttoxml, pyaml, moto
Found existing installation: moto 0.4.31
Uninstalling moto-0.4.31:
Successfully uninstalled moto-0.4.31
Running setup.py develop for moto
Successfully installed cookies-2.2.1 dicttoxml-1.7.4 moto pyaml-16.12.2
On Sun, May 14, 2017 at 10:16 PM, Steve Pulec<EMAIL_ADDRESS>wrote:

What happens after you git clone and run make init?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/spulec/moto/pull/940#issuecomment-301340601, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AIGeh-Fa6zK-LVd4qzENbCb5DhozkClRks5r529FgaJpZM4NaW8z
.


FT GCS should handle draining of node where head pod is scheduled

Search before asking

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

Description
If I have a TorchTrainer running, doing some work, and I drain the node where my head pod is running, nothing ever seems to actually recover. I've enabled FT GCS in KubeRay helm chart version v1.1.1 -- I have an external redis that has all the state in it, etc.
Is there truly no way to have my head pod, which is running on a spot node, survive being rescheduled? It doesn't seem like the head node can do any recovery whatsoever for jobs that were in the middle of training.
Use case
No response
Related issues
No response
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

Hi @abatilo, thank you for opening the issue. You may have some misunderstanding for GCS FT. You can read https://docs.ray.io/en/latest/cluster/kubernetes/user-guides/kuberay-gcs-ft.html#kuberay-gcs-ft for more details. Currently, the only use case of GCS FT is for Ray Serve high availability.

Thanks for responding @kevin85421. My original question still stands then. Is there no way to have the jobs running in progress survive after the Ray head gets restarted? I see that there's a way to resume a trainer from previous state but do I always have to re-submit that if the Ray head is gone?

My current understanding is that Ray Train provides some degree of fault tolerance.

If a Ray worker Pod crashes, Ray Train will launch new Ray tasks or actors, allowing the job to continue running.
If the Ray head crashes, the driver process, which is typically running on the Ray head of the Ray job, will also crash. Therefore, the Ray tasks or actors will also be garbage collected automatically. In most cases, Ray tasks or actors are fate-sharing with the driver process. Only detached actors do not share this fate with the driver.

In this case, users need to write the fault tolerance logic at the application level, specifically in their Ray Python script.if (checkpoint exists):
  read checkpoint
else:
  start from scratch

train the model

The long-running Ray job is currently on our roadmap of the next release. We are currently working on:

Retry mechanism in both RayJob CRD / ray job submit.
Best practice for checkpointing.

If you are interested in this topic, you can reach out to me on Ray Slack (my handle is 'Kai-Hsun Chen (ray team)'). We can discuss your requirements and ensure there are no feature gaps for your use cases.


Fix for  issue #46

Fixed the calculation on pressure for sensorTag firmware 0.89

@bChiquet thanks!
Closes #46.


Update to v3.7.0rc0

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

@conda-forge-admin, please rerender

Looks good, ...  no dependencies have changed since v3.6.1.
Thanks.  Unless I missed something altogether, I think that the recipe  is now the same as what I had yesterday, and should be good to go.


Add picnic grove capacities to picnic grove popups on map

If something in capacity column in picnicgroves table, add capacity value into picnic groves popup on map as follows:

Deer Grove Grove #5

Add:
Capacity: [from capacity column in picnicgroves table]

+++
Then to style, add .picnicgrove-capacity class to lines 333 & 334 in newguts.css
.trail-popup .trail-popup-line-named,.picnicgrove-capacity {     border-top: none;     padding: .5em .75em;     width: 80%; }
.trail-popup .trail-popup-line-named.trail-segment,.picnicgrove-capacity {     border-top: 1px solid #e3e3e1;     width: 100%; }
Visual:

This is now available on staging.
https://github.com/smartchicago/trailsy/commit/d4eb5216434ac975482e3770e20d6e94e29c9d0b

This is good to take live.

In production https://github.com/smartchicago/trailsy/commit/d92a30fdd57eb6d2e507f6b05593d196eb20fcb0


chore(buildpacks): update heroku-buildpack-nodejs to v89

See https://github.com/heroku/heroku-buildpack-nodejs/compare/v88...v89 and deis/deis#4976.

I tested this with the workflow-beta1 chart and example-nodejs-express.


One piece doesn't get all the episodes and it can't find the dubs for most of them even though 900+ exist

Describe the bug
One piece doesn't get all the episodes and it can't find the dubs for most of them even though 900+ exist
To Reproduce
Steps / command to reproduce the behavior:
./crunchy archive url/one-piece

Actually seems like it's crunchy roll maybe having issues and not the tool. As some of the episodes randomly are showing up without the audio.

This is partially an Crunchyroll issue. Over at r/Crunchyroll there are several complains about it... . Some episodes randomly aren't dubbed for some reason. But this only affect(ed) the download command, archive should work fine.

Fixed in v3.0.0. A warning is printed if a episode is detected which is missing dub even if it should have one.


Error when building portainer using Yarn

Hi!
I have built portainer images and had it working previously by cloning the repository and after making some changes using yarn. This is done on a Linux machine. The steps I follow are as follow:

git clone https://github.com/portainer/portainer.git
cd portainer
yarn
yarn start

Typically this would bring the portainer container right up, but after recently doing a git clone (to have a more recent version of portainer) I am presented with the below error when doing yarn start:
yarn run v1.13.0
$ grunt run-dev
Running "config:dev" (config) task
>> Configure 1 variable for current target.

Running "clean:app" (clean) task

Running "shell:buildBinary:linux:amd64" (shell) task
build/build_binary.sh: 6: build/build_binary.sh: go: not found
build/build_binary.sh: 7: build/build_binary.sh: go: not found
mv: cannot stat 'portainer': No such file or directory
Warning: Command failed: if [ -f dist/portainer ]; then echo "Portainer binary exists"; else build/build_binary.sh linux amd64; fi
build/build_binary.sh: 6: build/build_binary.sh: go: not found
build/build_binary.sh: 7: build/build_binary.sh: go: not found
mv: cannot stat 'portainer': No such file or directory
 Use --force to continue.

Aborted due to warnings.
error Command failed with exit code 6.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.```

I have rebuilt the VM and repeated this process to confirm that it is a repeatable problem.

Could someone please provide assistance with this?

Thanks!

Hi @javierma14
We recently updated our build system to leverage the local Go environment to build Portainer. This means that you now need to have Go (>= 1.11) installed on your machine.
See the latest docs https://portainer.readthedocs.io/en/latest/contribute.html

Hi @deviantony !
Thanks for the quick response.
I walked through the guide you provided and verified that I have the latest versions of Docker, node.js, Yarn, Golang. I am now receiving this error:
github.com/portainer/portainer (download)
created GOPATH=/home/admin/go; see 'go help gopath'
package github.com/portainer/portainer: no Go files in /home/admin/go/src/github.com/portainer/portainer
package github.com/portainer/portainer/bolt: cannot find package "github.com/portainer/portainer/bolt" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/bolt (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/bolt (from $GOPATH)
package github.com/portainer/portainer/cli: cannot find package "github.com/portainer/portainer/cli" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/cli (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/cli (from $GOPATH)
package github.com/portainer/portainer/cron: cannot find package "github.com/portainer/portainer/cron" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/cron (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/cron (from $GOPATH)
package github.com/portainer/portainer/crypto: cannot find package "github.com/portainer/portainer/crypto" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/crypto (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/crypto (from $GOPATH)
package github.com/portainer/portainer/docker: cannot find package "github.com/portainer/portainer/docker" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/docker (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/docker (from $GOPATH)
package github.com/portainer/portainer/exec: cannot find package "github.com/portainer/portainer/exec" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/exec (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/exec (from $GOPATH)
package github.com/portainer/portainer/filesystem: cannot find package "github.com/portainer/portainer/filesystem" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/filesystem (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/filesystem (from $GOPATH)
package github.com/portainer/portainer/git: cannot find package "github.com/portainer/portainer/git" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/git (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/git (from $GOPATH)
package github.com/portainer/portainer/http: cannot find package "github.com/portainer/portainer/http" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/http (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/http (from $GOPATH)
package github.com/portainer/portainer/http/client: cannot find package "github.com/portainer/portainer/http/client" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/http/client (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/http/client (from $GOPATH)
package github.com/portainer/portainer/jwt: cannot find package "github.com/portainer/portainer/jwt" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/jwt (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/jwt (from $GOPATH)
package github.com/portainer/portainer/ldap: cannot find package "github.com/portainer/portainer/ldap" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/ldap (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/ldap (from $GOPATH)
package github.com/portainer/portainer/libcompose: cannot find package "github.com/portainer/portainer/libcompose" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/libcompose (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/libcompose (from $GOPATH)
main.go:9:2: no Go files in /home/admin/go/src/github.com/portainer/portainer
main.go:10:2: cannot find package "github.com/portainer/portainer/bolt" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/bolt (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/bolt (from $GOPATH)
main.go:11:2: cannot find package "github.com/portainer/portainer/cli" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/cli (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/cli (from $GOPATH)
main.go:12:2: cannot find package "github.com/portainer/portainer/cron" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/cron (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/cron (from $GOPATH)
main.go:13:2: cannot find package "github.com/portainer/portainer/crypto" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/crypto (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/crypto (from $GOPATH)
main.go:14:2: cannot find package "github.com/portainer/portainer/docker" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/docker (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/docker (from $GOPATH)
main.go:15:2: cannot find package "github.com/portainer/portainer/exec" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/exec (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/exec (from $GOPATH)
main.go:16:2: cannot find package "github.com/portainer/portainer/filesystem" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/filesystem (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/filesystem (from $GOPATH)
main.go:17:2: cannot find package "github.com/portainer/portainer/git" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/git (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/git (from $GOPATH)
main.go:18:2: cannot find package "github.com/portainer/portainer/http" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/http (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/http (from $GOPATH)
main.go:19:2: cannot find package "github.com/portainer/portainer/http/client" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/http/client (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/http/client (from $GOPATH)
main.go:20:2: cannot find package "github.com/portainer/portainer/jwt" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/jwt (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/jwt (from $GOPATH)
main.go:21:2: cannot find package "github.com/portainer/portainer/ldap" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/ldap (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/ldap (from $GOPATH)
main.go:22:2: cannot find package "github.com/portainer/portainer/libcompose" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/libcompose (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/libcompose (from $GOPATH)
mv: cannot stat 'portainer': No such file or directory
 Use --force to continue.

Aborted due to warnings.
error Command failed with exit code 6.

I have tried doing yarn to build inside the go directory that is created as well as some other things to try to get it working. using --force does not really fix things.
What do you suggest?
Thanks again!

Woops, we've updated the instructions recently but the changes were not reflected on readthedocs, can you try these instructions: https://portainer.readthedocs.io/en/latest/contribute.html ?

Hey @deviantony Thanks again for the response, no luck with those instructions although I did notice that they were the same as the ones that I followed previously. The commands I am using are as follows:

git clone https://github.com/portainer/portainer.git
ln -s ${GOPATH}/src/github.com/portainer/portainer ${PWD}/portainer/api
cd portainer
yarn
yarn start

Did you set $GOPATH environment variable?

@linquize I am not sure. What does this involve? Sorry am not familiarized with go.
Thanks!

The simplest way is to set GOPATH to current dir
Before step2
export GOPATH=pwd

@linquize Appreciate the quick response. I tried that but still am getting the same error with exit code 6. These are the updates steps:

git clone https://github.com/portainer/portainer.git
export GOPATH=pwd
ln -s ${GOPATH}/src/github.com/portainer/portainer ${PWD}/portainer/api
cd portainer
yarn
yarn start

Any ideas what could be the cause?

Could you post your latest error message?
What is your go version?

My go version is go1.11.5 linux/amd64
Latest Error message:
root@Tool:~/portainer# yarn start
yarn run v1.13.0
$ grunt run-dev
Running "config:dev" (config) task
>> Configure 1 variable for current target.

Running "clean:app" (clean) task

Running "shell:buildBinary:linux:amd64" (shell) task
github.com/portainer/portainer (download)
package github.com/portainer/portainer/bolt: cannot find package "github.com/portainer/portainer/bolt" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/bolt (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/bolt (from $GOPATH)
package github.com/portainer/portainer/cli: cannot find package "github.com/portainer/portainer/cli" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/cli (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/cli (from $GOPATH)
package github.com/portainer/portainer/cron: cannot find package "github.com/portainer/portainer/cron" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/cron (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/cron (from $GOPATH)
package github.com/portainer/portainer/crypto: cannot find package "github.com/portainer/portainer/crypto" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/crypto (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/crypto (from $GOPATH)
package github.com/portainer/portainer/docker: cannot find package "github.com/portainer/portainer/docker" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/docker (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/docker (from $GOPATH)
package github.com/portainer/portainer/exec: cannot find package "github.com/portainer/portainer/exec" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/exec (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/exec (from $GOPATH)
package github.com/portainer/portainer/filesystem: cannot find package "github.com/portainer/portainer/filesystem" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/filesystem (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/filesystem (from $GOPATH)
package github.com/portainer/portainer/git: cannot find package "github.com/portainer/portainer/git" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/git (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/git (from $GOPATH)
package github.com/portainer/portainer/http: cannot find package "github.com/portainer/portainer/http" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/http (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/http (from $GOPATH)
package github.com/portainer/portainer/http/client: cannot find package "github.com/portainer/portainer/http/client" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/http/client (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/http/client (from $GOPATH)
package github.com/portainer/portainer/jwt: cannot find package "github.com/portainer/portainer/jwt" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/jwt (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/jwt (from $GOPATH)
package github.com/portainer/portainer/ldap: cannot find package "github.com/portainer/portainer/ldap" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/ldap (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/ldap (from $GOPATH)
package github.com/portainer/portainer/libcompose: cannot find package "github.com/portainer/portainer/libcompose" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/libcompose (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/libcompose (from $GOPATH)
main.go:9:2: no Go files in /home/admin/go/src/github.com/portainer/portainer
main.go:10:2: cannot find package "github.com/portainer/portainer/bolt" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/bolt (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/bolt (from $GOPATH)
main.go:11:2: cannot find package "github.com/portainer/portainer/cli" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/cli (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/cli (from $GOPATH)
main.go:12:2: cannot find package "github.com/portainer/portainer/cron" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/cron (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/cron (from $GOPATH)
main.go:13:2: cannot find package "github.com/portainer/portainer/crypto" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/crypto (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/crypto (from $GOPATH)
main.go:14:2: cannot find package "github.com/portainer/portainer/docker" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/docker (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/docker (from $GOPATH)
main.go:15:2: cannot find package "github.com/portainer/portainer/exec" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/exec (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/exec (from $GOPATH)
main.go:16:2: cannot find package "github.com/portainer/portainer/filesystem" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/filesystem (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/filesystem (from $GOPATH)
main.go:17:2: cannot find package "github.com/portainer/portainer/git" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/git (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/git (from $GOPATH)
main.go:18:2: cannot find package "github.com/portainer/portainer/http" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/http (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/http (from $GOPATH)
main.go:19:2: cannot find package "github.com/portainer/portainer/http/client" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/http/client (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/http/client (from $GOPATH)
main.go:20:2: cannot find package "github.com/portainer/portainer/jwt" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/jwt (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/jwt (from $GOPATH)
main.go:21:2: cannot find package "github.com/portainer/portainer/ldap" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/ldap (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/ldap (from $GOPATH)
main.go:22:2: cannot find package "github.com/portainer/portainer/libcompose" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/libcompose (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/libcompose (from $GOPATH)
mv: cannot stat 'portainer': No such file or directory
Warning: Command failed: if [ -f dist/portainer ]; then echo "Portainer binary exists"; else build/build_binary.sh linux amd64; fi
github.com/portainer/portainer (download)
package github.com/portainer/portainer/bolt: cannot find package "github.com/portainer/portainer/bolt" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/bolt (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/bolt (from $GOPATH)
package github.com/portainer/portainer/cli: cannot find package "github.com/portainer/portainer/cli" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/cli (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/cli (from $GOPATH)
package github.com/portainer/portainer/cron: cannot find package "github.com/portainer/portainer/cron" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/cron (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/cron (from $GOPATH)
package github.com/portainer/portainer/crypto: cannot find package "github.com/portainer/portainer/crypto" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/crypto (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/crypto (from $GOPATH)
package github.com/portainer/portainer/docker: cannot find package "github.com/portainer/portainer/docker" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/docker (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/docker (from $GOPATH)
package github.com/portainer/portainer/exec: cannot find package "github.com/portainer/portainer/exec" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/exec (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/exec (from $GOPATH)
package github.com/portainer/portainer/filesystem: cannot find package "github.com/portainer/portainer/filesystem" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/filesystem (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/filesystem (from $GOPATH)
package github.com/portainer/portainer/git: cannot find package "github.com/portainer/portainer/git" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/git (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/git (from $GOPATH)
package github.com/portainer/portainer/http: cannot find package "github.com/portainer/portainer/http" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/http (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/http (from $GOPATH)
package github.com/portainer/portainer/http/client: cannot find package "github.com/portainer/portainer/http/client" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/http/client (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/http/client (from $GOPATH)
package github.com/portainer/portainer/jwt: cannot find package "github.com/portainer/portainer/jwt" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/jwt (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/jwt (from $GOPATH)
package github.com/portainer/portainer/ldap: cannot find package "github.com/portainer/portainer/ldap" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/ldap (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/ldap (from $GOPATH)
package github.com/portainer/portainer/libcompose: cannot find package "github.com/portainer/portainer/libcompose" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/libcompose (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/libcompose (from $GOPATH)
main.go:9:2: no Go files in /home/admin/go/src/github.com/portainer/portainer
main.go:10:2: cannot find package "github.com/portainer/portainer/bolt" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/bolt (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/bolt (from $GOPATH)
main.go:11:2: cannot find package "github.com/portainer/portainer/cli" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/cli (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/cli (from $GOPATH)
main.go:12:2: cannot find package "github.com/portainer/portainer/cron" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/cron (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/cron (from $GOPATH)
main.go:13:2: cannot find package "github.com/portainer/portainer/crypto" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/crypto (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/crypto (from $GOPATH)
main.go:14:2: cannot find package "github.com/portainer/portainer/docker" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/docker (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/docker (from $GOPATH)
main.go:15:2: cannot find package "github.com/portainer/portainer/exec" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/exec (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/exec (from $GOPATH)
main.go:16:2: cannot find package "github.com/portainer/portainer/filesystem" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/filesystem (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/filesystem (from $GOPATH)
main.go:17:2: cannot find package "github.com/portainer/portainer/git" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/git (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/git (from $GOPATH)
main.go:18:2: cannot find package "github.com/portainer/portainer/http" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/http (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/http (from $GOPATH)
main.go:19:2: cannot find package "github.com/portainer/portainer/http/client" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/http/client (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/http/client (from $GOPATH)
main.go:20:2: cannot find package "github.com/portainer/portainer/jwt" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/jwt (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/jwt (from $GOPATH)
main.go:21:2: cannot find package "github.com/portainer/portainer/ldap" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/ldap (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/ldap (from $GOPATH)
main.go:22:2: cannot find package "github.com/portainer/portainer/libcompose" in any of:
        /snap/go/3129/src/github.com/portainer/portainer/libcompose (from $GOROOT)
        /home/admin/go/src/github.com/portainer/portainer/libcompose (from $GOPATH)
mv: cannot stat 'portainer': No such file or directory
 Use --force to continue.

Aborted due to warnings.
error Command failed with exit code 6.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Could you cd to a new empty directory and run all your steps again?

@linquize I have created a new directory and repeated all the steps in it. Unfortunately I still received the same error message.  I have nodejs version 8.10.0, and yarn version 1.13 if that is of any help.
I did this on a brand new VM, Ubuntu 18.04 with docker freshly installed.
Is this working for others?
Thanks for all the help!

The problem probably comes from that step:
export GOPATH=`pwd`

I'd recommend you to setup a proper GOPATH: https://github.com/golang/go/wiki/SettingGOPATH

Hey @deviantony !
Thanks for the instructions, I have followed those steps but am still presented with the same error noted above. I also uninstalled and reinstalled go using a method other than snap, and repeated the process with no success.
I am running on Ubuntu 18.04, before having GO as a requirement this worked fine. Do you think the issue may be with Ubuntu?
Thanks!

Nope, I'm pretty sure it's related to your go environment configuration as I am also working on Ubuntu 18.04.

@javierma14 ping me on slack and we'll try to resolve your problem.

@deviantony Will do :)


Rewrite system to use ArcGIS REST API

@iandees discovered the ArcGIS service that powers USDA's API. So that becomes the new place where we need to get data from.

[ ] determine the density of lon/lat pairs to have adequate resolution to capture the contours of the zones, but not so dense as to issue wasteful queries
[ ] modify the system to retrieve by lon/lat, rather than by ZIP
[ ] figure out the proper file format in which to store the results of those queries for maximum utility

I'm not sure if you're still interested in updating this project, but I was in search of similar data and found out a ton of this stuff has changed locations (ex: the link above is broken now). It seems like the company that was hosting this data has shut down:

Enhanced versions of these files were previously distributed by Climate Source, Inc., which closed its doors on February 1, 2017. The original files are now available free of charge on this site. However, they continue to be the property of Oregon State University, and are subject to OSU’s terms of use.

Through some spelunking I've found the raw data available for download which includes a CSV of zip codes very similar to what this project used to provide. A quick excerpt:
zipcode,zone,trange,zonetitle
01001,6a,-10 to -5,6a: -10 to -5
01002,5b,-15 to -10,5b: -15 to -10
01003,5b,-15 to -10,5b: -15 to -10
01004,5b,-15 to -10,5b: -15 to -10
01005,5b,-15 to -10,5b: -15 to -10
01007,5b,-15 to -10,5b: -15 to -10
01008,5b,-15 to -10,5b: -15 to -10

Additionally, there are some shapefiles and gridfiles which I've yet to dive into. This data also seems to be free to use so long as you display OSU & USDA ARS logos, which should put down the data usage legality questions.

Whoa!

This issue is obviated by #10.

@kneath, a belated "thank you so much" for bringing this to our attention! :dancer: :100:


[request]: Add types to deserialize SES S3 Action SNS notification events

A note for the community

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue, please leave a comment

Tell us about your request
Types to help deserialize the SES Receipt Rule S3 Action's optional SNS notification.
Tell us about the problem you're trying to solve.
I setup a SES Receipt Rule S3 Action with the optional SNS notification. This notification is delivered to a SQS Queue. The message body of the Queue message is an encoded JSON string. This string needs to be deserialized into a Rust struct. There are many fields and there's a risk of getting it wrong when modelling based on a small sample size. This is also something if done once can be reused by all users as opposed to everyone having to model this for their use.
Here's an example of the JSON:
{

   "notificationType":"Received",

   "mail":{

      "timestamp":"2022-02-10T04:25:13.995Z",

<EMAIL_ADDRESS>
      "messageId":"3rsfhsr2l6g08h0ddqs4f9ribuvfp4lpf4rqb6o8",

      "destination":[

<EMAIL_ADDRESS>
      ],

      "headersTruncated":false,

      "headers":[
...
],

      "commonHeaders":{
...
}

   },

   "receipt":{

      "timestamp":"2022-02-10T04:25:13.995Z",

      "processingTimeMillis":721,

      "recipients":[

<EMAIL_ADDRESS>
      ],

      "spamVerdict":{

         "status":"PASS"

      },

      "virusVerdict":{

         "status":"PASS"

      },

      "spfVerdict":{

         "status":"PASS"

      },

      "dkimVerdict":{

         "status":"PASS"

      },

      "dmarcVerdict":{

         "status":"PASS"

      },

      "action":{

         "type":"S3",

         "topicArn":"arn:aws:sns:us-east-1:<account-id>:mail_received_topic",

         "bucketName":"mail_received_bucket",

         "objectKey":"3rsfhsr2l6g08h0ddqs4f9ribuvfp4lpf4rqb6o8"

      }

   }

}

Are you currently working around this issue?
I couldn't find the exact Struct needed in this repo so I use a combination of types from the unofficial aws-lambda-events crate and added my own wrapper type to fit the exact shape of the received notification.
Additional context
No response

Thanks for submitting this. People have submitted similar issues in the past so things like this are on the team's radar. However, this isn't currently our highest priority so it might be a while before we address this need. In the meantime, if you have any specific questions related to this issue, don't hesitate to create a discussion post.


Filtering the list of tasks breaks when the page is reloaded

When I filter the list of tasks, then the URL of the page changes.
E.g., here I type "click" into the search list and it works, and the URL changes so that ?q=click is appended to the URL:

When I reload this page (or directly paste the URL https://www.tira.io/?q=click into the browser, the page is broken.
I.e., I only get a blank page with no tasks and no image at all:

Duplicate of #176


Some question about train dataset？

As paper says，“Instead, it leverages a more compact 0.5M pre-training caption data following llava”。
It means that “In the first pretrain stage, the train dataset is only blip_laion_cc_sbu_558k.json?”

Yes, this is amount of data used for initial alignment.


Update 1.1

[x] Change /party chat to /party toggle.
[x] Change /party info to /party list.
[x] Add /party kick <player>.
[x] Add /party disband.
[x] Add /party transfer <player>.
[x] Party auto disbands when the host disconnects.
[x] Add /adminparty spy
[x] Add /adminparty show <player> (Shows what players are in the selected player if any)
[x] Fix "null has joined the party!"
[x] Add expiration time to inviting the same player. (120 seconds)
[x] Reformatting messages.

Could not pass event PlayerQuitEvent to PartyChat v1.0
java.lang.NullPointerException: Cannot invoke "org.bukkit.entity.Player.equals(Object)" because the return value of "java.util.HashMap.get(Object)" is null
at com.exwundee.partychat.PartyChat.onLeave(PartyChat.java:60) ~[PartyChat.jar:?]
Putting this here to reference a bug later before release.

Could not pass event PlayerQuitEvent to PartyChat v1.0 java.lang.NullPointerException: Cannot invoke "org.bukkit.entity.Player.equals(Object)" because the return value of "java.util.HashMap.get(Object)" is null at com.exwundee.partychat.PartyChat.onLeave(PartyChat.java:60) ~[PartyChat.jar:?]
Putting this here to reference a bug later before release.

This has now been fixed.


Exclude ProcessBuilder Basic_id0 test on aix

ref https://github.com/AdoptOpenJDK/openjdk-infrastructure/issues/1644#issuecomment-737283413
This same test has been excluded on aarch64 due to https://github.com/eclipse/openj9/issues/9032. I am excluding it on aix for the same reason.
@smlambert Is editing this file all that is needed to exclude a test?

thanks @Haroon-Khel - I did not see that we need to exclude this test for other versions (if so, you'd need to update the version specific problemlist files.


information imbalance with automatic subsampling

Codecov Report
Attention: Patch coverage is 21.87500% with 25 lines in your changes are missing coverage. Please review.

Project coverage is 80.92%.  Consider uploading reports for the commit 77859a6 to get more accurate results

Files
Patch %
Lines

dadapy/metric_comparisons.py
10.71%
25 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #127      +/-   ##
==========================================
- Coverage   81.31%   80.92%   -0.39%
==========================================
  Files          20       20
  Lines        3302     3319      +17
==========================================
+ Hits         2685     2686       +1
- Misses        617      633      +16

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Can't tab-complete to highlight autcomplete entries for certain files which share prefixes

Platform Arch Linux
Terminal software alacritty
Nushell 71d604
It seems like under some circumstances I'm not able to press tab to highlight autocomplete for files. I think it's related to the files having the same prefix, but I'm not sure. I haven't fully bisected the issue, but I wasn't able to reproduce the issue on nushell 28a746 and was able to reproduce the issue on 71d604. There was a reedline update between those two commits which includes 2a57906, 4096b93, and 660a507. The latter seems the most related to the issue, so I suspect it's the culprint (@uek-1)
Steps to reproduce
In nushell,

Make a new directory and cd into it
touch testa testb testc
ls test<TAB>, then continue to press tab. testc will not be highlighted, however you can still select it with right arrow.

Resolved by #834


state of the project and ability to use extensions

I am curious if it is possible to use react native extensions with this project or create our custom extensions.And should i use this project for my next android and IOS project what are your recommendations ?

Extensibility is clearly one of the hot topic for this project, I've created issue #48 to track it. The amount of time I can dedicate is unfortunately limited, so not sure how fast it will move.
To answer your question, it really depends on the complexity of your application, your time to market and your will to contribute to the project.


[Event Request] Codeunit 6520 Item Tracing Mgt. - procedure ExitLevel - OnBeforeExitLevel

Please add the following existing Event OnBeforeExitLevel to procedure ExitLevel in Codeunit 6520 Item Tracing Mgt.
[Event Request] Codeunit 6520 - Item Tracing Mgt. - procedure ExitLevel
var
    ItemTrackingSetup: Record "Item Tracking Setup";
    IsHandled: Boolean; // <-- ADDED
begin

    IsHandled := false;
    OnBeforeExitLevel(TempItemTracingBuffer, IsHandled); // <-- NEW EVENT
    if IsHandled then
        exit(true);

    ItemTrackingSetup.CopyTrackingFromItemTracingBuffer(TempItemTracingBuffer);
    if not ItemTrackingSetup.TrackingExists() then
        exit(true);
    if CurrentLevel > 50 then
        exit(true);
    if not IsSpecificTracking(TempItemTracingBuffer."Item No.", ItemTrackingSetup) then
        exit(true);
    if TempItemTracingBuffer."Already Traced" then
        exit(true);

    exit(false);
end;

[IntegrationEvent(false, false)]
local procedure OnBeforeExitLevel(TempItemTracingBuffer: Record "Item Tracing Buffer" temporary; var IsHandled: Boolean)
begin
end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 52721.


Document deploy process for Care in Digital Ocean App platform

Lets document the process of deploying care to DO app platform.

[ ] Add the docs to the deploy docs
[ ] Get it reviewed by @vigneshhari
[ ] Publish

@dauntlessnomad

#57
Can we close this issue ?
@bodhish

@tellmeY18 Did you complete the checklist above?


Pub/Sub: please add Pub/Sub DLQ samples

Please add samples for

create a subscription with a dead letter policy
update a subscription's dead letter policy
remove a subscription's dead letter policy
receive messages that have a delivery attempts field

See existing Java, Go, Python, Node samples for how to name region tags.

Duplicate #1052


pip-sync Installs from sdist (.zip) after pip-compile --generate-hashes

Environment Versions

Ubuntu 14.04
Python version: 3.6.8
pip version: 21.2.4
pip-tools version: 6.2.0

Steps to replicate
The following was done in a virtualenv named pip-tools:
ss@ld:~/venv/PY3/pip-tools$ pip list
Package            Version
------------------ --------
click              8.0.1
importlib-metadata 4.8.1
pep517             0.11.0
pip                21.2.4
pip-tools          6.2.0
setuptools         58.0.4
tomli              1.2.1
typing-extensions  <IP_ADDRESS>
wheel              0.37.0
zipp               3.5.0
(pip-tools)

ss@ld:~/venv/PY3/pip-tools$ cat requirements.in
pygraphviz==1.5
(pip-tools)

ss@ld:~/venv/PY3/pip-tools$ pip-compile
#
# This file is autogenerated by pip-compile with python 3.6
# To update, run:
#
#    pip-compile
#
--index-url https://pypi.COMPANY.com/simple/

pygraphviz==1.5
    # via -r requirements.in
(pip-tools)

ss@ld:~/venv/PY3/pip-tools$ pip-sync --pip-args "--no-cache-dir"
Looking in indexes: https://pypi.COMPANY.com/simple/
Collecting pygraphviz==1.5
  Downloading https://pypi.COMPANY.com/pygraphviz/1.5/pygraphviz-1.5-cp36-cp36m-linux_x86_64.whl (150 kB)
     |████████████████████████████████| 150 kB 19.9 MB/s
Installing collected packages: pygraphviz
Successfully installed pygraphviz-1.5
(pip-tools)

ss@ld:~/venv/PY3/pip-tools$ pip uninstall -y pygraphviz
Found existing installation: pygraphviz 1.5
Uninstalling pygraphviz-1.5:
  Successfully uninstalled pygraphviz-1.5
(pip-tools)

ss@ld:~/venv/PY3/pip-tools$ pip-compile --generate-hashes
    Couldn't get hashes from PyPI, fallback to hashing files
#
# This file is autogenerated by pip-compile with python 3.6
# To update, run:
#
#    pip-compile --generate-hashes
#
--index-url https://pypi.COMPANY.com/simple/

pygraphviz==1.5 \
    --hash=sha256:50a829a305dc5a0fd1f9590748b19fece756093b581ac91e00c2c27c651d319d \
    --hash=sha256:99007fe4432d38c8d3ae40c9ceddccad88eaef88b319a8787fdb1aeceeeb1671
    # via -r requirements.in
(pip-tools)

ss@ld:~/venv/PY3/pip-tools$ pip-sync --pip-args "--no-cache-dir"
Looking in indexes: https://pypi.COMPANY.com/simple/
Collecting pygraphviz==1.5
  Downloading https://pypi.COMPANY.com/packages/packages/7e/b1/d6d849ddaf6f11036f9980d433f383d4c13d1ebcfc3cd09bc845bda7e433/pygraphviz-1.5.zip (117 kB)
     |████████████████████████████████| 117 kB 22.7 MB/s
Building wheels for collected packages: pygraphviz
  Building wheel for pygraphviz (setup.py) ... error
  ERROR: Command errored out with exit status 1:
...
pygraphviz/graphviz_wrap.c:2987:29: fatal error: graphviz/cgraph.h: No such file or directory
...
subprocess.CalledProcessError: Command '['/home/ssiano/venv/PY3/pip-tools/bin/python3.6', '-m', 'pip', 'install', '-r', '/tmp/tmp0tcqn2sm', '--index-url', 'https://pypi.zooxlabs.com/simple/', '--no-cache-dir']' returned non-zero exit status 1.

Expected result
Expected pip-sync to use the wheel whether or not the requirements.txt contained hashes.
Actual result
pip-sync used the wheel when requirements.txt did not contain hashes, and attempted to build the sdist (.zip) when requirements.txt did contain hashes.
I should mention that unlike pypi.org, both the .whl and the .zip exist in our Artifactory/PyPI:
ss@ld:~/venv/PY3/pip-tools$ jfrog rt search 'pypi/*/pygraphviz-1.5*'
[Info] Searching artifacts...
[Info] Found 2 artifacts.
[
  {
    "path": "files.pythonhosted.org-cache/7e/b1/d6d849ddaf6f11036f9980d433f383d4c13d1ebcfc3cd09bc845bda7e433/pygraphviz-1.5.zip",
    "type": "file",
    "size": 117810,
    "created": "2020-02-12T07:47:40.529Z",
    "modified": "2018-09-10T22:19:11.000Z",
    "sha1": "0171c160cc9cbec28162204b514f8595e2c88dac",
    "md5": "c186f5f6567e523a862063fc62ddcd2f",
    "props": {
      "artifactory.internal.etag": [
        "\"c186f5f6567e523a862063fc62ddcd2f\""
      ]
    }
  },
  {
    "path": "pypi-COMPANY/pygraphviz/1.5/pygraphviz-1.5-cp36-cp36m-linux_x86_64.whl",
    "type": "file",
    "size": 150257,
    "created": "2021-06-11T04:36:06.918Z",
    "modified": "2021-06-11T04:36:06.851Z",
    "sha1": "13a5974b031705bcc98c7b6a0985318784541f36",
    "md5": "ae9fe3872eb6e09bbf42a9bb51275c4c",
    "props": {
      "pypi.name": [
        "pygraphviz"
      ],
      "pypi.normalized.name": [
        "pygraphviz"
      ],
      "pypi.requires.python": [
        ""
      ],
      "pypi.summary": [
        "Python interface to Graphviz"
      ],
      "pypi.version": [
        "1.5"
      ]
    }
  }
]
(pip-tools)

I should also mention that our PyPI/Artifactory is an older version that does not return sha256 values, as can be seen in the JSON output above.

If I pip-compile with --generate-hashes and then remove the sha256 for the .zip from requirements.txt, then pip-sync uses the wheel.

This issue has been solved by upgrading our PyPI/Artifactory to a version that contains the following fix:
SHA256 hashes in PyPi repository metadata.
Now pip-sync installs the wheel when both hashes are in the requirements.txt.
Before, pip-sync was choosing the artifact with the lowest hash value.  It probably would have been better for pip-sync to fail with an error message.
But this is a strange corner case, so I think this issue should be closed.


chore(FDS-255): Add input file field

The input file type is adding to our module list.
This PR includes:

Module DataFile
Fixture
Unit test

Snapshot
A new fixture for the DataFile field is created.
New Component Checklist

[x] Includes unit tests for ALL required FDS use cases
[x] Does not mute any top level API props in React
[x] Includes an explanation for any changes to Jest snapshots (should be a PR tag automatically added if this happens)
[-] Component uses React.forwardRef() when a single DOM node is returned, AND it makes React-sense access that DOM node

Fails

:no_entry_sign:
Please add a '### Snapshots' section to explain the reason we are changing snapshots.

  Generated by :no_entry_sign: dangerJS against 6670b993c29a3abd4d60b75a355997249c680234


Rewrite the "documentation structure" page to better reflect how our docs are currently organised

This mostly reduces the complexity of this page by only focussing on 2i2c engineers as the audience, and the structure of the infrastructure.2i2c.org site only. It documents the SRE and Hub Deployment guides as well as the breakdown of our other docs that don't fall into those guides.
Note: I have kept a local copy of the original file contents because I do really like the idea of thinking about audiences and breaking down docs accordingly, and how we split that between infrastructure repo and the docs repo. But I think that discussion would be better placed into the team compass than in the infrastructure repo itself. So I will follow up with a PR over there bringing back some of the nuance and different audiences that this PR removes.
fixes #2055

@yuvipanda really keen to hear what you think and if this rewrite helps at all?

Thanks @sgibson91!


TestServiceLifecycle_PipelineError times out intermittently

Bug description
Examples:

https://github.com/ConduitIO/conduit/actions/runs/4103150469/jobs/7077290457
https://github.com/ConduitIO/conduit/actions/runs/4176638027/jobs/7233190852
https://github.com/ConduitIO/conduit/actions/runs/3989729342

Steps to reproduce
n/a
Version
Issue happened on different versions, see output of GitHub actions

Will be fixed in #857.


Fix "visibly" typo in Control.xml

The current text reads: "If true, parts of a child which would be visibly outside of this control's..."
This PR corrects the text to: "If true, parts of a child which would be visible outside of this control's..."

This is not necessarily a typo, it is correct English

This is not necessarily a typo, it is correct English
While the best wording can be discussed, for example if it's more accessible English, I don't think a change of a wording that isn't wrong is worth it here, as changes to the docs invalidate translations

Though I agree it's not necessarily a typo and is still technically valid English, it is not correct in the "intended spirit" of the sentence. I believe the intent was to refer to the "visibility" of the child elements, rather than their "being," It caused a mental double-take when I read it, and I had to think for a second to understand your interpretation. Google seems to agree:

Regardless, I understand your point about the translations. I will have a look at the translations and whether they would be invalidated by this change.

Except the way to read it is "the parts that are visibly outside" as in, the parts, that visibly exist outside it. It is a complete and valid English sentence. And Google isn't really a reference here for spelling

I will have a look at the translations and whether they would be invalidated by this change.

They would, the text has changed so the translations would be changed.

Fair enough. I see your point. Happy to close this.


Unreasonable fatal error: path ~/.local/share exists

Hi,
After
yay -S flutterup

I've got this:
~ % ls -l /usr/bin/flutter
lrwxrwxrwx 1 root root 9 июн 14 18:14 /usr/bin/flutter -> flutterup
~ % ls -l /usr/bin/dart
lrwxrwxrwx 1 root root 9 июн 14 18:14 /usr/bin/dart -> flutterup
~ % ls -l /usr/bin/flutterup
-rwxr-xr-x 1 root root 1239472 июн 14 18:14 /usr/bin/flutterup
~ % flutterup upgrade
fatal: destination path '/home/alexey/.local/share' already exists and is not an empty directory.
Flutter is installed
~ %

~/.local/share exists, most certainly. It isn't empty, of course. Flutter is installed is also wrong. Maybe flutterup help doesn't tell me everything it should?

oh, sorry, I make a mistake.. .. I will solve it later
https://github.com/Decodetalkers/flutterup/blob/master/src/constenv.rs#L35
this I miss to join "flutterup"

I feel so sorry, I always use the path in my config, not try the default path.. and since there is no issue, so I have not realize that there is such a serious bug

have the tag 0.2.0 solve your problem? I think I have fixed it


Logging during @compile_workload

Inspired by https://github.com/julia-vscode/LanguageServer.jl/pull/1222, we may need some specialized facilities to control log messages during precompilation.

We may also need to do something about error handling during precompilation as well.
See https://discourse.julialang.org/t/vscode-julia-server-fails-precompilation/98865?u=mkitti


No scrolling occurs on navigation forwards/back

Is there any reason we should expect this not to work with a setup like:
import { Router } from 'react-router-dom'; // Note we're using Router not MemoryRouter or BrowserRouter
import ScrollMemory from 'react-router-scroll-memory';

const Root = ({ store, children, history }) => (
  <Provider store={store}>
    <Router history={history}> // history is created with createMemoryHistory
      <div>
        <ScrollMemory elementID="myElementID" />
        {children}
      </div>
    </Router>
  </Provider>
);

I tried to inspect the code as it ran, but it's minified in development which makes that pretty much impossible without special effort.
We see history.location.state === undefined which seems unlikely to be the correct behavior
My best guess otherwise is maybe that the element hasn't loaded its content by the time the location change takes place, so it doesn't have the appropriate dimensions to scroll to the previously saved point?
<EMAIL_ADDRESS><EMAIL_ADDRESS>

Maybe is a problem with createMemoryHistory. I never tried with this package.

Hey @ipatate thanks for your reply.
Theoretically we're using the same setup as a regular MemoryRouter, only we're passing our own history object (so that we can read the state from anywhere.)
MemoryRouter itself uses createMemoryHistory

ok, i will tried when i have more time

Let me know if I can be of assistance. I don't know too much about React-Router, so I doubt I'm good for anything besides testing, but happy to try to help.


(5) Mean (Statistic)

[x] Implement function
[x] Include comments
[x] Write tests

Issue for proof: #122.


Fix installation on talos.dev according to https://www.talos.dev/v1.6…

When installing on talos.dev the prometheus is not running.
The issue is using of PodSecurityConfiguration
There some labels must be present on NS monitoring
I fixed it
I am kindly asking to accept this PR.

I am not a talos user today, but I may be one tomorrow... I am interested in checking this out and understanding if we support talos appropriately today, thanks for reporting this @gecube 🥇

@kingdonb any chance that it would be accepted? I don't like hanging PRs and stale branches

@gecube Yes we discussed this at Bug Scrub yesterday, but I didn't get around to updating the issue here.
I think we should expand support for talos, and I'd like to begin testing it myself. Immediately!
It is going to take me at least one more day to get my local dev environment up. But if we have one more Talos user here who can chime in and commit to report issues like this when we spot them, who can validate this change makes sense, I'd be glad to merge it.
Only problem is I do not have write access here. @fluxcd/maintainers Do we have a policy about write access to example repos? I think maybe they would fall under website/community and I should have access already. Or the example repos ought to have a MAINTAINERS file of their own, and I'll apply to be maintainer for the various docs repos.
I don't think I should be core maintainer, I don't have the golang experience to merge PRs in any old repo, but I can help in any of these example repos (and I'd volunteer for this.)

We're testing today in Bug Scrub:
  Warning  FailedCreate  7m28s                 daemonset-controller  Error creating: pods "kube-prometheus-stack-prometheus-node-exporter-lxl8c" is forbidden: violates PodSecurity "baseline:latest": host namespaces (hostNetwork=true, hostPID=true), hostPath volumes (volumes "proc", "sys", "root"), hostPort (container "node-exporter" uses hostPort 9100)
  Warning  FailedCreate  2m1s (x8 over 7m26s)  daemonset-controller  (combined from similar events): Error creating: pods "kube-prometheus-stack-prometheus-node-exporter-j25ff" is forbidden: violates PodSecurity "baseline:latest": host namespaces (hostNetwork=true, hostPID=true), hostPath volumes (volumes "proc", "sys", "root"), hostPort (container "node-exporter" uses hostPort 9100)

This is the daemonset which is not getting any pods fulfilled, preventing the HelmRelease from suceeding. All of the non daemonset pods are fine.
The talos pod security docs mention only the one label:
https://www.talos.dev/v1.6/kubernetes-guides/configuration/pod-security/
I've applied that one label and it does allow the HelmRelease to complete successfully, in my testing

@kingdonb @stefanprodan thanks for your comments and testing.
Fixed.


[BUG] Degenerate table metas were not getting copied to the heap

This a two-liner but a bad one. This makes sure that there is a JVM object for every TableMeta, not just non-degenerate ones.

@jlowe same contents, just forgot to sign-off before.

build

waiting for https://github.com/NVIDIA/spark-rapids/pull/530

build

I had to pick up #530 @jlowe and @revans2 fyi.

build


jumeg import error

I am running the MNE version 0.21. When trying to import the latest jumeg repo I get the follwing import error within jumeg_interpolate_bads:
ImportError: cannot import name '_map_meg_channels' from 'mne.forward' (/home/jdammers/anaconda3/envs/jumeg_cuda/lib/python3.8/site-packages/mne/forward/__init__.py)
Does anybody know how to solve this?

The issue should be solved by the above PR.

The issue should be solved by the above PR.

@pravsripad many thanks,  it works for me

@pravsripad many thanks,  it works for me


Server rejected websocket connection http 503

I have problem today with exception : server rejected websocket connection http 503
Can you take a look ?

I had same issue.

Same here. Anyone with a fix?

Same issue 😭 please fix

sorry @DONpromise1738-dot i will update everything by today ! sorry was little busy since last week

Thanks boss the new update is working highly appreciated boss

Thanks :)


Incorrect next_bit assignment?

https://github.com/bggardner/simplisafe-rf/blob/266d5e68d3e446fbbd7083f344c3688703a7d6cf/simplisafe/pigpio.py#L221
Should this be next_bit ^= 1 instead of next_bit ^= next_bit?. The equivalent section in the 'script' version of this method implies it should be.

Yes, I believe you're right.  However, I no longer have the V2 hardware so I can't test it.


Add "raw" flag to decode-secret sub-command

This commit connects to https://github.com/ministryofjustice/cloud-platform-cli/issues/103 and offers mitigation (not a fix) to a problem where a secret contains a unicode char. We use the stdlib json package to handle a "prettyprint" back to the end user. When doing so, we marshal a raw string into json, which handles UTF-8 only (please see here: https://pkg.go.dev/encoding/json#Marshal).
This commit gives the option to specify a --raw or -r flag to the subcommand and print before marshaling. This loops over all secret values, decodes the base64 and then prints them raw with no formatting applied.

Codecov Report
Base: 27.32% // Head: 27.53% // Increases project coverage by +0.20% :tada:

Coverage data is based on head (472d260) compared to base (e2d68cc).
Patch coverage: 69.23% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #211      +/-   ##
==========================================
+ Coverage   27.32%   27.53%   +0.20%
==========================================
  Files          41       41
  Lines        2064     2074      +10
==========================================
+ Hits          564      571       +7
- Misses       1426     1428       +2
- Partials       74       75       +1

Impacted Files
Coverage Δ

pkg/decodeSecret/decodeSecret.go
47.72% <69.23%> (+2.85%)
:arrow_up:

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

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


Auth headers not set on requests if proxy is set.

  db.info().then(function (info) {
    var src = new db.constructor(opts.proxy, opts);
    var target = new db.constructor(info.db_name, opts);
    var replIdOpts = {};
    if (opts.filter) {
      replIdOpts.filter = opts.filter;
    }

The following code changes seem to work.

Hm, yeah, that's not quite right, though, because it's applying the opts to both the local database and the remote one. Could have unintended results if you are replicating between two remote databases. Tricky problem...

Ah, okay, I see that I do support ajax options per the documentation. So the fix should be to copy over ajax to both, and also using the database's native db.__opts. I'll try to fix this soon.

Can you try https://github.com/nolanlawson/pouchdb-load/pull/17 and let me know if it works for you?

Awesome, thanks.
I've also noticed post load, I'm getting a large number of these errors, and its taking roughly 15 seconds to process the pouch-api requests, should the proxy be circumventing this?
pouchdb:api project_14b54b108d0-mrview-temp +1ms get error CustomPouchError {status: 404, name: "not_found", message: "missing", error: true, toString: function}

#17 seems to fix the auth header issue.

Cool, that's good enough for me. :)

1.3.4

Thank you.


Get latest tag, regardless of branch for workflows that rely on git-flow releases.

Create a new release using git-flow, generate changelog and finish the release.
Next release, you won't see the previous release tag when generating a new changelog.

Thanks @seivan  , I will take a look at all the PR and issues next week. Thanks a lot for contributing and also for answering the issues <3 <3 <3


modules/ui: Add zoom-frm module

This module adds zoom-frm support.
The hydra is based on the doom-text-zoom-hydra, just using zoom-frm functions instead.

After some thought, I decided to selectively extract the zoom functionality from zoom-frm into the new doom/{increase,decrease,reset}-font-size commands introduced in 0f0fdbc. I've also updated doom-text-zoom-hydra to use them. The decision was motivated by:

Avoiding pulling in more dependencies than we need (zoom-frm uses very little of frame-cmds and frame-fns)
Better integration with Doom (particularly the modeline and restoring doom-font when reverting to the base font size)
Reduce redundancy with doom-big-font-mode (it is now powered by these new commands)

In any case, these changes were inspired by this PR, so thank you for bringing it to my attention!


fix: Fixed swapped translation

Three translations were mixed up with each other 🙂.

Oh, thanks!

Unfortunatly, I will not release this until I finish entity link, but I guess, it will be today or early tommorow.


Include gtk-dark-mode-switch-fix patch

Description
Resolve prefer-color-scheme not reflecting GTK dark mode issue
Who's implementing?

[ ] I'm willing to implement this feature myself

The problem
Currently Chromium has a bug where it doesn't respect the preferred color scheme of the system.
Possible solutions
Including this patch would resolve this.
Alternatives
No response
Additional context
My eyes bleed at 4 AM otherwise.

I doubt this falls within objectives of the project, so one should apply this fix locally when compiling.
Please also note that the bug you mentioned has a proper fix for this (not the one you linked) and it works flawlessly for me for quite some time: https://github.com/PF4Public/gentoo-overlay/commit/84f77f55a09f6ce0523591d7c300bf9deb2a1c01

I hope your question(-s) has(-ve) been answered, otherwise please let us know.
Closing this issue as there is nothing left to do.


ARVR - Fight off some error spam in the editor

Because the editor is now interrogating the view frustum of the camera node, and the view frustum for an ARVRCamera isn't available until an ARVRinterface is active, the logs were filling up with errors.
This PR solves that differently and just returns the output of a normal camera in the editor. There is room for improvement by maybe returning a view frustum that has a wider FOV but this is enough for now.

Now that Godot 3.1 has been released, we don't plan to cherry-pick new features and enhancements to the 3.0 branch, unless there is very strong support in favor of it. Removing cherrypick label for 3.0.


Stop using removeNullCharacters in the addLinkAttributes helper function

Using removeNullCharacters on the URL should be completely redundant, given the kind of data that we're passing to the addLinkAttributes helper function. Note that whenever we're handling a URL, originating in the worker-thread, in the viewer that helper function is always being used.
Furthermore, on the worker-thread all URLs are parsed with the createValidAbsoluteUrl helper function, which uses new URL() to ensure that a valid URL is obtained. Note that the URL constructor will either throw, or in some cases just ignore them, when encoutering \u0000-characters during parsing.
Hence it should be impossible for a valid URL to contain \u0000-characters and we can thus simplify the viewer-code a tiny bit. The use of removeNullCharacters is most likely a left-over from back when new URL() wasn't generally available in browsers.

It isn't directly related to your patch but it could help to have a test for it.
I just created two pdfs:

plop.pdf containing an url with a \u0001 and in Acrobat it's replaced with a %01 so I guess we must try to escape the string.
plop1.pdf containing an url with a \u0000 and in Acrobat the bytes after the null char are removed.

It isn't directly related to your patch but it could help to have a test for it. I just created two pdfs:

plop.pdf containing an url with a \u0001 and in Acrobat it's replaced with a %01 so I guess we must try to escape the string.
plop1.pdf containing an url with a \u0000 and in Acrobat the bytes after the null char are removed.

Interesting, thank you!
However, I do wonder how "necessary" it actually is to attempt to support such URLs given that we're not the only PDF Viewer that won't handle those?
Testing quickly in PDFium, in Google Chrome Beta 117, neither of those PDF documents have working links (there's a link-cursor but nothing happens when clicking).

In the \u0000 I suppose some buggy pdf generators could have added a null terminator in the pdf itself so it could potentially fix some issues with some old pdfs.
In the \u0001 case, Acrobat at least doesn't escape the url when I created the pdf (I firstly created this one and then I open it (modulo qpdf) to change the 1 to a 0) and I'm pretty sure that some other generators do the exactly the same, so trying to escape them is probably a good idea.
I noticed too this behaviour in Chrome (the 0001 is failing in Edge but not the 0000) but I thought that Acrobat behavior is what we should follow.
That said I tried with this URL: https://www.mozilla<abcd>+123
and it's fine in Chrome and in Acrobat but not in Firefox:
plop2.pdf
the < and > chars are correctly escaped.

/botio integrationtest


Revit connector 2.6 crashed Revit '22

Just trying to send ''everything' from a view with only doors visible. This was a potentially catastrophic hard crash with no possibility to save my work or synchronize to central.
Please advise on how to collect debugging info.
24ee0a37-dd98-46e2-b87a-683e62506681

See also https://speckle.community/t/speckle-crashing-revit-2020-and-2022/3379

Hi @DuncanLithgow without a sample stream or reproducible steps we will not be able to help on this one.
Does the issue still occur in 2.7?


Input line too long when using generated bat file

The long set CLASSPATH line in the generated bat file throws an error on Windows.
Tested on Windows 7 64bit

You can try to install Gradle and use the gradle command instead of gradlew.bat

Sure, but at the moment there is some documentation missing when we do not use Gradle.
Also you write Recommended, not necessary: Gradle
https://github.com/jphp-compiler/jphp/wiki/Installation

What version of gradle are you using? Required 2.+

I use the linked Gradle version (2.3) ;-)
Anyway,I got it working.
Just replaced the very long line set CLASSPATH= ... with set CLASSPATH=%APP_HOME%\lib\*; ;-)

Do you want to build the core of jphp or only try to run a php script?

Run a PHP, but it works now.
I just use gradle to retrieve and build the sources from the repository (the jar files) and create the files needed for running the bat file.
After this I can directly use the bat file without any problems. The PHP fileis now executed,after I have changed the long line to the short version in the bat file.
Because this produces the Input line too long error on Windows.

It looks like a bug of the Gradle System and its wrapper task that creates gradlew files.

Right, it seems Gradle generates a line with all libraries instead of using an asterisk as placeholder and the issue 2292 is still open, but there are plenty workarounds.
Maybe we can mention this in the Wiki, if other developers and users face the same problem.
https://discuss.gradle.org/t/gradle-application-plugin-and-cmd-exe-line-size-limitations/2521/18
https://issues.gradle.org/browse/GRADLE-2992
http://stackoverflow.com/questions/32088966/gradle-generated-startscript-for-windows-produces-input-line-is-too-long


Vat does not use the correct amount of RF when modified in the config file

i changed this in the config file from 20 to 160 and 320
Power use (RF/t) used by the vat.
I:vatPowerUserPerTickRF=160
however it seems that it only uses 80 RF/tick no matter what number i change it to . i used capacitor bank next to  monitor the power consumption , also it seems that the power monitor doesn't identity the Vat power consumption , is this intended for all machines ? or it's just for monitoring power cells , banks . etc ???
Ender IO v2.2.8 367
Forge 1377

Did you connect the Vat to the Capbank & power monitor via a single energy conduit? Because the power monitor only monitors the energy conduit network.

yes i did it showed nothing but if i connected a capacitor bank the power monitor will show that it using 80 RF ( the same result when monitored by capacitor bank ) per tick even thought i changed the setting to 160 RF and even 320 RF.
it seems that it will use a maximum of 80 RF per/tick if "vatPowerUserPerTickRF" is increased to above 80 RF

The code for the power use of machines has changed massively in 2.3.

good to know ! THX


[CT-534] Add adapter plugin versions to telemetry + context

Today, there are a few places where we return dbt_version, which is really the installed version of dbt-core. Now that dbt-core and adapter plugins can differ for patch versions (and patches only!), let's make available both:

The version of dbt-core (current)
The version of plugin(s)

For point 2, that could be either:

The current "active" adapter plugin, and any upstream plugins used by the active plugin, e.g. dbt-redshift -> dbt-postgres. There are methods for this in adapters/factory.py
All installed plugins

I'm pretty happy with whichever is easier, and has fewer downstream implications.  Update from BLG:  Ensure this is structured data.
Context
Made available to the dbt-Jinja context as dbt_version:
https://github.com/dbt-labs/dbt-core/blob/979e1c74bf55bc6849c89accd75ce86531e7a1f9/core/dbt/context/base.py#L208-L226
Which is also included in the default query comment for all queries:
https://github.com/dbt-labs/dbt-core/blob/979e1c74bf55bc6849c89accd75ce86531e7a1f9/core/dbt/contracts/connection.py#L200-L204
For backwards compatibility, we'd want dbt_version to continue returning the core version. Looking forward, we could update this to be a dictionary containing the core version and active plugin(s).
Telemetry
Reported in our anonymous usage tracking:
https://github.com/dbt-labs/dbt-core/blob/979e1c74bf55bc6849c89accd75ce86531e7a1f9/core/dbt/tracking.py#L201
Let's update that to be core_version and plugin_versions (active or installed, whichever is simpler). We don't need to worry as much about backwards compatibility here, since we can update the modeling logic on our end :)

what's the impact for partner adapter developers here? does this make it easier to standardize on logging dbt-<<ADAPTER>>==<<VERSION>> in lieu of just "dbt"?