Failed at the<EMAIL_ADDRESS>install script

i am trying to start strapi on widows and its needs sharp package  , i trying the whole day and i face many errors with that
install" "--verbose" "--foreground-scripts" "sharp"
npm verb node v14.21.3
npm verb npm  v6.14.18
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>install: (node install/libvips && node install/dll-copy && prebuild-install) || (node install/can-compile && node-gyp rebuild && node install/dll-copy)
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm verb exit [ 1, true ]
npm timing npm Completed in 94249ms
npm ERR! A complete log of this run can be found in:

Hi @Yaman-kassas
I had the same experience as well, but I managed to fix it by upgrading the node version to v18.17.0.
I hope this works for you too.

Hi @Yaman-kassas I had the same experience as well, but I managed to fix it by upgrading the node version to v18.17.0. I hope this works for you too.

i use node v18.17.0 but it gives me this :
npm ERR! code 1
npm ERR! path C:\Users\z1h88\Desktop\web\New folder (2)\dev-blog\node_modules\sharp
npm ERR! command failed
npm ERR! command C:\WINDOWS\system32\cmd.exe /d /s /c (node install/libvips && node install/dll-copy && prebuild-install) || (node install/can-compile && node-gyp rebuild && node install/dll-copy)
npm ERR! sharp: Downloading https://github.com/lovell/sharp-libvips/releases/download/v8.14.5/libvips-8.14.5-win32-x64.tar.br
npm ERR! sharp: Please see https://sharp.pixelplumbing.com/install for required dependencies
npm ERR! sharp: Installation error: connect ETIMEDOUT <IP_ADDRESS>:443
npm ERR! A complete log of this run can be found in: C:\Users\z1h88\AppData\Local\npm-cache_logs\2023-10-28T23_43_10_652Z-debug-0.log

The salient error here is:

npm ERR! sharp: Installation error: connect ETIMEDOUT <IP_ADDRESS>:443

This suggests that there was a (temporary?) networking problem between the installation machine and GitHub.

This whole class of possible installation problem will be going away in the forthcoming v0.33.0 - please see https://github.com/lovell/sharp/issues/3750#issuecomment-1751172728 for details of a release candidate.

I succeeded with this command
sudo npm i -g cnpm
cnpm i sharp


Add shortNames to crd api resouces

Adding shortNames to kube api-resource CRDs. Short-names make it easier when interacting/troubleshooting api-resources with kubectl.
I have tried to follow the naming convention similar to what K8s uses which should help with avoiding any naming conflicts as well. For example:

Deployment has a shortName of deploy, so added rdeploy for runnerdeployment
HorizontalPodAutoscaler has a shortName of hpa, so added hra for HorizontalRunnerAutoscaler
ReplicaSets has a shortName of rs, so added rrs for runnerreplicaset

Please feel free to let me know if this needs to go somewhere else, or if you would like me to use different shortNames

LGTM, could you also make the change on Kustomize bases https://github.com/actions-runner-controller/actions-runner-controller/tree/master/config/crd/bases

LGTM, could you also make the change on Kustomize bases https://github.com/actions-runner-controller/actions-runner-controller/tree/master/config/crd/bases

Sure. @toast-gear, I have updated those as well. Thank you 😄

LGTM. I once considered using rd for RunnerDeployment's shortName but apparently rdeploy is much better. Thanks a lot for your contribution! @abhi-kapoor ☺

It is my pleasure, thank you for your kind words. CI seems to be failing on the Verify manifests are up-to date step. When I locally run, make manifests, I seem to be getting the below error :( Can you please advise? @mumoshu
Error: unable to parse option "crd:trivialVersions=true,generateEmbeddedObjectMeta=true": [unknown argument "generateEmbeddedObjectMeta" (at <input>:1:48) extra arguments provided: "true" (at <input>:1:49)]

@abhi-kapoor Probably your local copy of controller-gen is outdated. I have a makefile target that you can use to newly install the required version of controller-gen after you uninstall the current one https://github.com/actions-runner-controller/actions-runner-controller/blob/f858e2e43273a861b06b546c6311fe68fb6e1ce5/Makefile#L232
Also, the CI failure seems to say that controller-gen is reverting the changes made in this PR. I've just recovered my memory that you have to use kubebuilder comments in Go source to let controller-gen generate CRDs from Go structs and comments.
I think you can set shortName= in a kubebuilder:resource annotation for RunnerDeployment, RunnerReplicaSet, and HorizontalRunnerAutoscaler

https://book.kubebuilder.io/reference/markers/crd.html
You can find those Go structs in https://github.com/actions-runner-controller/actions-runner-controller/tree/master/api/v1alpha1
Once you've added required kubebuilder comments, try running make release. It will generate CRDs from Go structs.

@mumoshu Thank you kindly for such detailed explanation. It seems like the build doesn't auto trigger, can you please re-run the CI now?

Thank you for re-running the workflow and it seems to be passing now. Are we good to merge this one @mumoshu?

@abhi-kapoor Merged. Thanks again for your contribution ☺


Add cleanup of SASS source files

See https://github.com/dart-lang/build/issues/1308

Add a post process builder to remove .scss and .sass files. Enabled by
default only in release mode.
Upgrade the minimum version of package:build to one that include
PostProcessBuilder and FileDeletingBuilder.
Updgrae the mininmum version of package:build_config to one that
includes parsing of the post_process_builders section.
Drop the now unnecessary target config for the builder.
Upgrade the build_runner version in the example directory to one
that supports --release

See the difference in the example by building to an output directory
with and without the --release flag.

cc @nshahan
I can also drop the -dev from the pubspec so we can publish right away.

Thanks, go ahead and leave the -dev. I'll include this in the version I'm going to publish that removes the transformer.


Add duplicate connection feature

Motivation
Often you want to make a new connection based off an existing one.
Suggestion: add a 'Duplicate' button to the right mouse click menu on a existing connection.

@JannemanDev Hi, thanks for your advance. This is very useful and has now been implemented at https://github.com/emqx/MQTTX/releases/tag/v1.8.0


[Bug/question] Map timeout

Issue:
Members are reporting map time out in and out of game. The map does not show a change to info or a status change from online to offline in the upper left corner.
This can occur with in minutes to hours.
Behaviors of this range from:
a) Not show current corp member locations
b) Not allowing destination info to be set via the crest API with out reloading the map page

Current browsers have function to suspend inactive tabs, maybe this is causing your trouble. Try to open only one tab for Pathfinder, don´t minimize it.

Is this issue still relevant? if yes, please give us a screenshot from your "network" tab (browser dev tools)


[Epic]: AST parsing for BE

Objective
TBD
Success Metrics

Metric

Customer satisfaction score increases

Decrease churn rate down to 30%

Prioritised User Stories

User Story

e.g. as a user, I want to be able to access the platform via mobile phone

e.g as a user, I want to be able to communicate with the other members on the canvas

Developer Handoff Document in Figma
No response
Test Plan
No response
RACI matrix
| ------------- | ------------- |
| Responsible   |    @AmanAgarwal041    @Irongade         |
| Accountable   |  @Irongade              |
| Consulted     |    @ApekshaBhosale     @hetunandu        |
| Informed      |     @nidhi-nair @mohanarpit           |

Actionable points:

Create new column in AST Documentation called Control Measures - which talks about quality, test plan and performance implications
Decide whether to go with MonoRepo approach or create separate github repo for AST logic.
Task breakdown and Estimation (Ensure issues don't have more than 4 or 5 Story points)
Deliberate whether to add MetaData Analysis of code written by users on Appsmith as part of scope for AST v1.

Here is the Notion documentation to the POC for the Shared AST Logic project.

Closing this Epic as Successful. 👺


updated portfolio url

updated portfolio url from adityaseth.me to adityaseth.in

Thank you for this xD


The error happened when I did multi-node distributed training

🐛 Describe the bug
Excuse me. When I enter the command "colossalai run --nproc_per_node 4 --host [host1 ip addr],[host2 ip addr] --master_addr [host1 ip addr] train.py", I got this message: Error: failed to run torchrun --nproc_per_node=4 --nnodes=2 --node_rank=1 --rdzv_backend=c10d --rdzv_endpoint=[host1 ip addr]:29500 --rdzv_id=colossalai-default-job train.py on [host2 ip addr]
What are the configurations I have to set in the train.py you provided with?
Environment
CUDA Version: 11.3
PyTorch Version: 1.12.0
CUDA Version in PyTorch Build: 11.3
PyTorch CUDA Version Match: ✓
CUDA Extension: ✓

Hi, are these two machines connected by ssh without password?


sample of dubbo-go-istio

What this PR does:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

https://github.com/apache/dubbo-go-pixiu-samples


Adding a non-async PowerNotificiations::EffectivePowerMode method

The original PowerNotifications have EffectivePowerMode is an IAsyncOperation typed as a property. Instead of introducing a breaking change, it was suggested to introduce a non-async version and update the documentation to use it instead. This PR adds the said API.

/azp run


CU-86drpndnn - Throw a compilation error when variable type declaration doesn't match the assigned value type

Summary or solution description
When assigning a variable and defining the type of said as a constant (like a number or hardcoded string) of a different type, it should throw an error.
Platform:

OS: Windows 10 x64
Python version: Python 3.11

Task linked: CU-86drpndnn Throw a compilation error when variable type declaration doesn't match the assigned value type


Improve videos playback experience

Is your feature request related to a problem? Please describe.
Default Mastodon UI requires only 1 click for video to be started with sound.
Phanpy UI requires 2 (or even 3) clicks for the same thing:

Click on the video – modal opens, video started without sound
Click on the sound icon
(Optional) rewind video to the beginning to hear the missed sound

Describe the solution you'd like
I wish Phanpy to have same video playback flow as Mastodon
Additional context
In Mastodon UI videos are not preloaded, so traffic is not wasted until video is started
<video
preload="none"
role="button"
src="https://files.mastodon.social/media_attachments/files/112/282/620/914/170/241/original/02a1e4569b858a61.mp4"
poster="https://files.mastodon.social/media_attachments/files/112/282/620/914/170/241/small/02a1e4569b858a61.png"
tabindex="0" aria-label="" title="" lang="en" style="width: 100%;"></video>

Haha so it was a bug report after all
7376cb1


Add "Expand All" option to tree control nodes

A nice convenience to add to the Event Browser would be an "Expand All" option to the "+" controls in the Event Browser's tree control, perhaps bound to the right-click. This command would expand the selected node and all child nodes, and reduce the amount of clicks necessary to navigate a nested frame capture hierarchy. Not a high priority item, but a convenience that should hopefully be easy to add.

That was a nice easy one :grinning:. Should do the trick, I added "Collapse All" while I was at it, since that might also be useful for cleaning up when you've looked for one draw and want to find another in a different part of the frame.

Closing this issue as the feature is implemented in v0.30. Feel free to re-open if it's not as you expect!


Issue connection timeout on pulling db, while running the command docker-compose up

Pulling db (postgres:9.6.6-alpine)...
ERROR: Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
Can Any one explain,why its coming.
I am using Window10 pro , visualization Enabled.
Docker version 18.09.0, build 4d60db4
docker-compose version 1.23.2, build 1110ad01

It was because , I did not login to Docker Data Hub.
Once I login , docker-compose up command ran successfully


n1614884424

fix: use ntl_append2 to fix memory leak

ntl_append2 will take an address of NTL. It frees the old list inside the function.  Can you please take a look if you understand this?  The rest uses of ntl_append should be replaced this one too.


Have you tested RCAN result on benchmark?

Thanks for your amaing work.
I want to know if you have trained RCAN and the final result is close to original paper?
Wishsing for your reply!

Now the RCAN is not completed.
In my preliminary experiments, the training results are similar to the officially released repo.

I may update it later.

To be honest, I personally think that many of the models in the last three years have not successfully reproduced the results in the paper, even if they provide the source code, which makes me feel very confused. If you can reproduce good models such as RCAN or SAN, this may be very valuable work in this field.
Thanks again for your reply!

Thanks
You can also make contributions to BasicSR 😃

@1187697147 I think there are some tricks in SR network training that have not been mentioned by the authors in their paper. For example, you could train your model first, and then load the model as the pre-trained model and train it once again. It can always improve the performance. This is like using the cosine learning rate.

@zpkosmos Okay, thanks for your reminding, I will try the tricks above.

@zpkosmos You mean finetune the model which is trained before?

@1187697147 Yes, you can first train the model for 1000 epochs with a learning rate of 2e-4, and then train the model for another 1000 epochs with a learning rate of 1e-4. You can also change the validation set. Note that we are calculating the PSNR on the Y channel. Finally, 你可以跟我中文.

@zpkosmos ok, 谢谢


archive function; permanently done button

In the readme, e has been assigned to "delete" (which I can confirm is its function now). However, the text below the table still states:

Archiving a task via e is fairly similar to marking it complete via d. Here are the differences:
If the task is a child task, if you "Complete" it it will be checked and greyed out (and will remain in the list under the uncompleted parent task until the parent task is completed). If you "Archive" the child task it will be checked and then removed from view.

If the task is a Recurring Task (e.g. every day) and you "Complete Task" it will be scheduled for the next date of recurrence. If you "Archive Task" it will be completed and not recur again.

I'd suggest to update this text.
Furthermore, I suggest to have a button that marks recurrent tasks as permanently done.

Good catch!  Thanks for opening the issue.  I've updated the readme text


Button connects doesn't work with latest gintro version

Gintro: gintro-#head
GTK: 3.24.24-4+deb11u2
Problem: Program failed to compile. It worked perfectly with version 0.9.6.  I guess macro failed to pass a function via argv.

Did a test with
nimble install https://github.com/dmknght/anonsurf.git
Downloading https://github.com/dmknght/anonsurf.git using git
  Verifying dependencies for<EMAIL_ADDRESS> Installing<EMAIL_ADDRESS>   Building AnonSurfGUI/AnonSurfGUI using c backend
/tmp/nimble_33554/githubcom_dmknghtanonsurfgit/src/AnonSurfGUI.nim(1, 15) Error: cannot open file: gintro/gtk
       Tip: 2 messages have been suppressed, use --verbose to show them.
     Error: Build failed for package: AnonSurfGUI
        ... Execution failed with exit code 1
        ... Command: /home/salewski/Nim/bin/nim c --colors:on --noNimblePath -d:release -d:NimblePkgVersion=0.1.0 --hints:off -o:/tmp/nimble_33554/githubcom_dmknghtanonsurfgit/AnonSurfGUI /tmp/nimble_33554/githubcom_dmknghtanonsurfgit/src/AnonSurfGUI.nim

Will investigate later or tomorrow.

proc ansurf_gtk_do_restart*(b: Button, cb_send_msg: proc)

I did not even know that passing a proc as optional parameter to the connect() macro was possible. It was never intended and never tested. That it refuse to work since v0.9.7 is related with our patches for Mr. Avr. I always said that the patches are ugly, only to support tuples, which could be replaced by ref objects just fine. But well, now we have the tuple code in gintro for more than six months. The ugly part is, that we have to handle each data type of the optional parameters now separately. So we have to see how we can handle a proc data type. But we should really rewrite the connect macro to use pure AST manipulation. I am not really good in writing macros, maybe more than a week for me, when I manage it at all. And I try to concentrate on the Nim book, I would like to finish it before Nim looses all its users. But I will try one more ugly patch to get your code working again. I really wonder that it was working with v0.9.6 -- I have no idea what a proc data type really is, and how passing a Nim proc to C functions may work. And the calling convention, cdecl and such, may also be a problem. I was really surprised that tuples have worked, but that procs have worked is magic.

Oh the passing proc was working with 0.8.0 as well. And i believe passing callback is normal in C lang? I don't know anything about Macro so i just did a quick check and I saw mconnect is totally different. That's all LoL.
I added a line like this

Assume the last kind is when program failed to build, the at.kind showed type nnkProcTy

So i guess, at least it could be a dirty way to check and handle it in macro

I have just looked at some of your code, and I have to admit that I do understand not much. You do even create new threads, to which you pass that proc. Really interesting that all that has been working. I think I have never used proc parameters in pure Nim code before, and I still have to learn how Nim ensures matching parameter lists. Seems that we can assign to a proc variable procedures with different parameter lists. But then, when we later call that proc, how does Nim ensures that all parameters are correct. In C this is a problem.
But I think I do not have to understand all that to fix your issue, what I have to know is if I have to call GC_ref() on the proc to avoid destroying it by the GC. Will see.

You do even create new threads, to which you pass that proc.

Oh that was something I asked here long time ago about GUI not responding when use thread (the refesh GUI and time wait). I used procs because the logic when click on some buttons is the same, and I want to do the logic for both GUI and CLI, so I used call back procs that handle either echoing in CLI or showing system's notification.

I still have to learn how Nim ensures matching parameter lists

I think I had similar issue before but i managed to made it work and I can't remember LoL.

But I think I do not have to understand all that to fix your issue

That's great! If you need to test the code, I'm available to help :D

Maybe this plain fix will do:
diff ~/.nimble/pkgs/gintro-#head/gintro/gimplgobj.nim gimplgobj.nim
96,99d95
<
<   elif at.kind == nnkProcTy: # v0.9.8
<     ats = at.toStrLit.strVal

Please try with
nimble install gintro@#head

Thank you it worked perfectly. I'm closing this issue now. Thanks a lot <3


Dead Repository

It is obvious that the owner of this repository has no intent to maintain this repository any longer. He has 4 contributions on github in the last year as of this moment. There are 59 open issues prior to this one and 13 pending pull-requests ranging from December 15 2014 to today.
Is anyone willing to take on maintaining this code base? @nickperkinslondon are you willing to pass ownership of the repository to the next maintainer?

Hopefully someone will keep maintaining this.
I would really love the possibility to add a right-click handler.

@nickperkinslondon I see you merged a pull request a few days ago. Does that mean that you're continuing support for this component? Any communication is appreciated.

He merged #77 which I submitted a long ways back. Maybe he just needs more maintainers.

Hi everyone.  I created this thing a few years ago while on vacation, just for fun and learning.  I am pleasantly surprised by the number of people who have used it.  However, I did not anticipate that I would get so many feature requests, even years later.  I never had any intention of maintaining this thing into the future.  In fact, I don't even use Angular any more ( I have used React for a while, and now I am trying to learn Elm ).
So, yes, I am willing to pass the torch to someone else.  How is that done?  If there is a fork that will be maintained I would be happy to deprecate this package and put a prominent "re-direct" to it.  So...who would like to take over this project?

Has anyone taken over this from @nickperkinslondon yet?

Hey all, I have started addressing and cleaning up old issues/PRs. I would like to at the very least fix or close all issues/PRs. I may also investigate updating this project to current gen tooling (typescript instead of coffeescript, gulp instead of grunt, investigate implementing component version for modern angular, etc...)
Hopefully I can breathe a little more life into this really useful library and help us get that much more out of it. It seems that there is no shortage of similar libraries, but this is one that a long standing project at my work uses so I have a vested interest in keeping it alive for the near future.
Any assistance or feedback is appreciated as I clean the cobwebs and start moving PRs. Thanks!


Startplay from specific time

Sorry for this question, maybe it's something very easy.
How can I startPlay from a specific time(seconds or milliseconds)
thank you

@ehuamaniquispe  you can use seek player for same thing check about seek player

Thank you very much for your answer. I had tried seek method before with milliseconds as a parameter but it didn't work. then I tried with seconds and it worked, thank you.
// actually it seeks 4000 seconds
onStatusPress = async (e) => {
this.audioRecorderPlayer.seekToPlayer(4000); // in miliseconds
this.onStartPlay();
};
// actually it seeks 4 seconds
onStatusPress = async (e) => {
this.audioRecorderPlayer.seekToPlayer(4); // in seconds
this.onStartPlay();
};


Multiple tests are failing with upcoming OpenSSL 3.0 release

Hi,
We are doing a test run with upcoming OpenSSL 3.0 release (we are testing 3.0 alpha2 atm.) and multiple tests are failing, e.g:

cwd: /home/abuild/rpmbuild/BUILD/qpdf-10.0.1/qpdf/qtest/qpdf
command: qpdf-ctest 2 enc-R2,V1,U=view,O=view.pdf '' a.qdf
expected output in c-invalid-password.out
at qpdf.test line 3503.
--> BEGIN EXPECTED OUTPUT <--
error: enc-R2,V1,U=view,O=view.pdf: invalid password
code: 4
file: enc-R2,V1,U=view,O=view.pdf
pos : 0
text: invalid password
--> END EXPECTED OUTPUT <--
--> BEGIN ACTUAL OUTPUT <--
error: openssl error
code: 2
file:
pos : 0
text: openssl error
--> END ACTUAL OUTPUT <--
--> DIFF EXPECTED ACTUAL <--
--- /tmp/testtemp.12117/expected	2020-05-25 08:16:22.300000000 +0000
+++ /tmp/testtemp.12117/actual	2020-05-25 08:16:22.300000000 +0000
@@ -1,5 +1,5 @@
-error: enc-R2,V1,U=view,O=view.pdf: invalid password

code: 4
file: enc-R2,V1,U=view,O=view.pdf
+error: openssl error

code: 2
file:
pos : 0

text: invalid password

text: openssl error

warning: c-r2.pdf: object 15/0: error reading object: openssl error
code: 5
file: c-r2.pdf
pos : 0
text: object 15/0: error reading object: openssl error
error: openssl error
code: 2
file:
pos : 0
text: openssl error
--> END ACTUAL OUTPUT <--
+warning: c-r2.pdf: object 15/0: error reading object: openssl error

code: 5
file: c-r2.pdf
pos : 0
text: object 15/0: error reading object: openssl error
+error: openssl error
code: 2
file:
pos : 0
text: openssl error
--> END DIFFERENCES <--

warning: c-r3.pdf: object 15/0: error reading object: openssl error
code: 5
file: c-r3.pdf
pos : 0
text: object 15/0: error reading object: openssl error
error: openssl error
code: 2
file:
pos : 0
text: openssl error
--> END ACTUAL OUTPUT <--
+warning: c-r3.pdf: object 15/0: error reading object: openssl error

code: 5
file: c-r3.pdf
pos : 0
text: object 15/0: error reading object: openssl error
+error: openssl error
code: 2
file:
pos : 0
text: openssl error
--> END DIFFERENCES <--

I'm attaching the full build log for reference.
opeensl3-log.txt.zip

I'm not sure how these test PDFs are encrypted, but I am guessing they are using a legacy method, and we are hit by https://github.com/openssl/openssl/issues/9349

@ismail The amount of actual openssl code in qpdf is pretty small and is all contained within a single source file, libqpdf/QPDFCrypto_openssl.cc. I would be interested in ensuring that qpdf works with openssl 3, and if possible, also with older versions. I would welcome a patch or pull request, or even just a quick pointer saying, "Use this instead of that." I can't imagine this would be hard to fix. The openssl code was contributed by another user. I didn't write it myself. But it is a full part of qpdf, and I would like it to be done correctly and in a way that will work with whatever supported version of openssl someone may be using. Thanks.

Yes, this is ok. Once OpenSSL comes up with a fixed API, I or someone else can easily fix this. I just wanted the problem to be tracked :-)

From https://www.openssl.org/docs/OpenSSLStrategicArchitecture.html it looks like OpenSSL 3 is a large departure from OpenSSL 1.1.0 and not intended to be API compatible.  While we could hack it in to the current qpdf crypto-openssl provider with some autoconf checks and preprocessor guards, I think it would be cleaner to support from a new qpdf crypto provider.  There are no doubt parts we could factor out and share between the two.
A second reason for making a new provider is that currently OpenSSL 1.1.0 and BoringSSL are substitutable so far as qpdf is concerned.  It doesn't look like BoringSSL will have a 3.0-equivalent API.
Finally, OpenSSL 3.0.0 still isn't released, so it feels premature for qpdf to support it.  However, a continuous integration test (marked as an expected failure) could be useful in the meantime to help track known failures.

I have no problem with having a completely separate provider for openssl 3 and am inclined to agree that that is the correct approach. I don't care whether we factor out common sections or not. It might complicate the build a little, and there's very little code in the crypto provider.

No one is rushing to support openssl3 yet ;) Anyhow OpenSSL has version macros which we can use. I'm just waiting for them to release a stable before working on this.
tl;dr It's not my intention to break what's working

@ismail Current master now works with both openssl 1 and 3. The windows builds for 10.4 will be built with openssl 3. The detection is made at compile time. Basically the issue was that rc4 and md5, both of which are unavoidable in PDF, are in the legacy provider, so I had to change the code to load those, plus update for a few other minor API issues. It took me about 2 or 3 hours to get everything working and tested, most of which was getting it to work on Windows.


Error during pip install pyaudio

Hello when i try running pip install pyaudio I git this error:
src/_portaudiomodule.c:29:23: fatal error: portaudio.h: Bestand of map bestaat niet
#include "portaudio.h"
^
compilation terminated.
error: command 'arm-linux-gnueabihf-gcc' failed with exit status 1
Any idea?

Is it something to do with this?
https://stackoverflow.com/questions/20023131/cannot-install-pyaudio-gcc-error
This is off-topic for this library, so I will close it soon

Fixed: I had to do this: sudo apt-get install portaudio19-dev.
Thanks for the quick response

This is not working for me. Using Ubuntu 18.04.
src/_portaudiomodule.c:29:10: fatal error: portaudio.h: No such file or directory
#include "portaudio.h"
^~~~~~~~~~~~~
compilation terminated.
error: command 'gcc' failed with exit status 1

I fixed it making an update with sudo.


[SPARK-11068][SQL] add callback to query execution

With this feature, we can track the query plan, time cost, exception during query execution for spark users.

cc @yhuai

Merged build triggered.

Merged build started.

Test build #43579 has started for   PR 9078 at commit ea523b9.

Test build #43579 has finished for   PR 9078 at commit ea523b9.

This patch fails RAT tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
trait QueryExecutionListener
class ExecutionListenerManager extends Logging

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43579/
Test FAILed.

Merged build finished. Test FAILed.

Build triggered.

Build started.

Test build #43583 has started for   PR 9078 at commit 4e9f27a.

Test build #43583 has finished for   PR 9078 at commit 4e9f27a.

This patch fails to build.
This patch does not merge cleanly.
This patch adds the following public classes (experimental):
trait QueryExecutionListener
class ExecutionListenerManager extends Logging

Build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43583/
Test FAILed.

Merged build triggered.

Merged build started.

Test build #43592 has started for   PR 9078 at commit 8f9bb8d.

Does this need to be a public interface?
If yes, can we add experimental label to it.

Actually if QueryExecution is not a public interface (it is in execution - I think it's incorrectly labeled developer api), this should probably be in execution as well as a semi private interface?

Test build #43592 has finished for   PR 9078 at commit 8f9bb8d.

This patch fails to build.
This patch merges cleanly.
This patch adds the following public classes (experimental):
trait QueryExecutionListener
class ExecutionListenerManager extends Logging

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43592/
Test FAILed.

Merged build finished. Test FAILed.

retest this please.

Merged build triggered.

Merged build started.

Test build #43600 has started for   PR 9078 at commit 8f9bb8d.

Test build #43600 has finished for   PR 9078 at commit 8f9bb8d.

This patch fails to build.
This patch merges cleanly.
This patch adds the following public classes (experimental):
trait QueryExecutionListener
class ExecutionListenerManager extends Logging

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43600/
Test FAILed.

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #43604 has started for   PR 9078 at commit e5c2120.

Test build #43604 has finished for   PR 9078 at commit e5c2120.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43604/
Test FAILed.

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #43626 has started for   PR 9078 at commit e43c955.

Test build #43626 has finished for   PR 9078 at commit e43c955.

This patch fails MiMa tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
trait QueryExecutionListener
class ExecutionListenerManager extends Logging

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43626/
Test FAILed.

retest this please.

Merged build triggered.

Merged build started.

Test build #43637 has started for   PR 9078 at commit e43c955.

Test build #43637 has finished for   PR 9078 at commit e43c955.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
trait QueryExecutionListener
class ExecutionListenerManager extends Logging

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43637/
Test PASSed.

Merged build triggered.

Merged build started.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43648/
Test FAILed.

Merged build finished. Test FAILed.

retest this please.

Merged build triggered.

Merged build started.

Test build #43652 has started for   PR 9078 at commit b7927d8.

Test build #43652 has finished for   PR 9078 at commit b7927d8.

This patch fails to build.
This patch merges cleanly.
This patch adds the following public classes (experimental):
trait QueryExecutionListener
class ExecutionListenerManager extends Logging

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43652/
Test FAILed.

Merged build triggered.

Merged build started.

Test build #43660 has started for   PR 9078 at commit 903d65e.

Test build #43660 has finished for   PR 9078 at commit 903d65e.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
trait QueryExecutionListener
class ExecutionListenerManager extends Logging

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43660/
Test FAILed.

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #43667 has started for   PR 9078 at commit 2d81674.

Merged build triggered.

Merged build started.

Test build #43674 has started for   PR 9078 at commit 0846260.

Test build #43667 has finished for   PR 9078 at commit 2d81674.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
trait QueryExecutionListener
class ExecutionListenerManager extends Logging

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43667/
Test PASSed.

Merged build triggered.

Merged build started.

Test build #43685 has started for   PR 9078 at commit 9943fea.

Test build #43674 has finished for   PR 9078 at commit 0846260.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
trait QueryExecutionListener
class ExecutionListenerManager extends Logging

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43674/
Test PASSed.

LGTM, waiting for tests.

Test build #43685 has finished for   PR 9078 at commit 9943fea.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
trait QueryExecutionListener
class ExecutionListenerManager extends Logging

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43685/
Test PASSed.

Merged into master, thanks!


  :   DE
ID des codierten Zeichensatzes (CCSID)  . . . . . :   1141
Standard-ID des codierten Zeichensatzes . . . . . :   1141
When i check files: wrkf some_file: 273
ID des codierten Zeichensatzes  . . . . . . : CCSID        273
I tried to change the Source file CCSID in the settings to 1141 and 273 and 65535 and *FILE but none works.
How can i solve the issue ?
The characters that cannot be displayed are ä ö ü.

Does this info from the documentation help?
https://codefori.github.io/docs/tips/ccsid/

I set everything as suggested and now i works.
But when i change everything back to how it was before it still works.
Even after reconnecting and restarting the ssh daemon.
Not sure why but i will keep the changes i guess, when we will upgrade to 7.4 it will be like this anyway i guess.
Thank you.


Generate FIDIL JSON

FIDIL organizes dataset at the timeseries level. Assume each FIDIL timeseries can be uniquely specified by the triple (dataset_id, variable_id, country). For the purpose of Causx, except for the time qualifier, ignore qualifiers.  Each uploaded Excel/CSV file can generate one or more timeseries.
FIDIL JSON is an array of timeseries objects, each timeseries object has properties

id: string, uuid md5 hash of concat(dataset_id, variable_id, country)
country: string, country label
country_cameo: string, URI for country
label: string, variable (property) label
description: string, concat(document description, variable (property) description)
excelFile: array of strings, where each string is the name of an uploaded file
sheet: array of strings, where each string is the name of a sheet. If the uploaded file is CSV, then use the CSV filename without the suffix.
units: string
structuredDataMapping, object with properties

docID, string
factorClass, string
normalizer, string
relevance, number
other-user-defined-keys, string

structuredData, array of objects, each object with properties

timestamp, string in ISO format
value, number

excelFile: array of strings, where each string is the name of an uploaded file
sheet: array of strings, where each string is the name of a sheet. If the uploaded file is CSV, then use the CSV filename without the suffix.

in  a case with N excel files with M sheets, sheets contains MxN values?

other-user-defined-keys, string

this is a single key whose string value is concatted from multiple keys, or a filler entry for any other user keys, ie
structuredDataMapping, object with properties
docID: string
factorClass: string
normalizer: string
relevance:number
mykey1: string
mykeyt2: string2

attached is an example FIDIL json (from the freedom house press example)
please look at it and let me know if I've built it correctly. Thanks @kyao
example_fidil_freedomhousepress.txt

The file looks good to me. I am sending it to the CX folks to have them take a look.

One thing is all the factor classes should have the prefix: http://ontology.causeex.com/ontology/odps/ICM#

ok, i have pushed the necessary change to add the prefix


Running a GROUP BY on the result of a CASE column results in a ProgrammingError being logged for a valid query

Driver version
2.0.907
Redshift version
PostgreSQL 8.0.2 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 3.4.2 20041017 (Red Hat 3.4.2-6.fc3), Redshift 1.0.38551
Client Operating System
Linux - kernel version 5.13
Python version
3.8.13
Table schema
See Reproduction Code
Problem description
When trying to group query results on the outcome of a case statement, driver complains that the original column needs to be part of the GROUP BY clause or needs to be used in an aggregate function.
Sqlalchemy doesn't use the label provided in the CASE statement for grouping columns, but instead uses the same case statement again when compiling the actual query. See an example below:
SELECT
  CASE
     WHEN (adhoc.test_table.col1 IN ('a', 'b', 'c') THEN adhoc.test_table.col1
     ELSE 'Other'
  END AS new_col,
  sum(adhoc.test_table.col2) AS sum_col2
FROM adhoc.test_table
GROUP BY
  CASE
    WHEN (adhoc.test_table.col1 IN ('a', 'b', 'c') THEN adhoc.test_table.col1
    ELSE 'Other'
END

As a result, it looks like the driver is confused.
However, when running the query manually on Redshift everything is fine and the results are ok.
Also changing the driver to psychopg2 seems to result in the correct output.
Python Driver trace logs
Traceback (most recent call last):
  File "/{pythondir}/lib/python3.8/site-packages/redshift_connector/core.py", line 1648, in execute
    ps = cache["ps"][key]
KeyError: ('SELECT CASE WHEN (adhoc.test_table.col1 IN (%s, %s, %s)) THEN adhoc.test_table.col1 ELSE %s END AS new_col, sum(adhoc.test_table.col2) AS sum_col2 \nFROM adhoc.test_table GROUP BY CASE WHEN (adhoc.test_table.col1 IN (%s, %s, %s)) THEN adhoc.test_table.col1 ELSE %s END', ((705, 0, <function text_out at 0x7f1970a1be50>), (705, 0, <function text_out at 0x7f1970a1be50>), (705, 0, <function text_out at 0x7f1970a1be50>), (705, 0, <function text_out at 0x7f1970a1be50>), (705, 0, <function text_out at 0x7f1970a1be50>), (705, 0, <function text_out at 0x7f1970a1be50>), (705, 0, <function text_out at 0x7f1970a1be50>), (705, 0, <function text_out at 0x7f1970a1be50>)))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/{pythondir}/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1819, in _execute_context
    self.dialect.do_execute(
  File "/{pythondir}/lib/python3.8/site-packages/sqlalchemy/engine/default.py", line 732, in do_execute
    cursor.execute(statement, parameters)
  File "/{pythondir}/lib/python3.8/site-packages/redshift_connector/cursor.py", line 231, in execute
    self._c.execute(self, operation, args)
  File "/{pythondir}/lib/python3.8/site-packages/redshift_connector/core.py", line 1718, in execute
    self.handle_messages(cursor)
  File "/{pythondir}/lib/python3.8/site-packages/redshift_connector/core.py", line 1986, in handle_messages
    raise self.error
redshift_connector.error.ProgrammingError: {'S': 'ERROR', 'C': '42803', 'M': 'column "test_table.col1" must appear in the GROUP BY clause or be used in an aggregate function', 'F': '../src/pg/src/backend/parser/parse_agg.c', 'L': '486', 'R': 'check_ungrouped_columns_walker'}

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/{localdir}//test.py", line 42, in <module>
    main()
  File "/{localdir}//test.py", line 35, in main
    engine.execute(stmt)
  File "<string>", line 2, in execute
  File "/{pythondir}/lib/python3.8/site-packages/sqlalchemy/util/deprecations.py", line 401, in warned
    return fn(*args, **kwargs)
  File "/{pythondir}/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 3176, in execute
    return connection.execute(statement, *multiparams, **params)
  File "/{pythondir}/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1306, in execute
    return meth(self, multiparams, params, _EMPTY_EXECUTION_OPTS)
  File "/{pythondir}/lib/python3.8/site-packages/sqlalchemy/sql/elements.py", line 325, in _execute_on_connection
    return connection._execute_clauseelement(
  File "/{pythondir}/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1498, in _execute_clauseelement
    ret = self._execute_context(
  File "/{pythondir}/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1862, in _execute_context
    self._handle_dbapi_exception(
  File "/{pythondir}/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 2043, in _handle_dbapi_exception
    util.raise_(
  File "/{pythondir}/lib/python3.8/site-packages/sqlalchemy/util/compat.py", line 207, in raise_
    raise exception
  File "/{pythondir}/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1819, in _execute_context
    self.dialect.do_execute(
  File "/{pythondir}/lib/python3.8/site-packages/sqlalchemy/engine/default.py", line 732, in do_execute
    cursor.execute(statement, parameters)
  File "/{pythondir}/lib/python3.8/site-packages/redshift_connector/cursor.py", line 231, in execute
    self._c.execute(self, operation, args)
  File "/{pythondir}/lib/python3.8/site-packages/redshift_connector/core.py", line 1718, in execute
    self.handle_messages(cursor)
  File "/{pythondir}/lib/python3.8/site-packages/redshift_connector/core.py", line 1986, in handle_messages
    raise self.error
sqlalchemy.exc.ProgrammingError: (redshift_connector.error.ProgrammingError) {'S': 'ERROR', 'C': '42803', 'M': 'column "test_table.col1" must appear in the GROUP BY clause or be used in an aggregate function', 'F': '../src/pg/src/backend/parser/parse_agg.c', 'L': '486', 'R': 'check_ungrouped_columns_walker'}
[SQL: SELECT CASE WHEN (adhoc.test_table.col1 IN (%s, %s, %s)) THEN adhoc.test_table.col1 ELSE %s END AS new_col, sum(adhoc.test_table.col2) AS sum_col2
FROM adhoc.test_table GROUP BY CASE WHEN (adhoc.test_table.col1 IN (%s, %s, %s)) THEN adhoc.test_table.col1 ELSE %s END]
[parameters: ('a', 'b', 'c', 'Other', 'a', 'b', 'c', 'Other')]
(Background on this error at: https://sqlalche.me/e/14/f405)

Reproduction code
# Reproduces the issue
import pandas as pd
from sqlalchemy import Column, Integer, String, create_engine
from sqlalchemy.ext.declarative import declarative_base
from sqlalchemy.sql.expression import case, func, select

Base = declarative_base()

class TestTable(Base):
    __tablename__ = "test_table"
    __table_args__ = {"schema": "adhoc"}

    col1 = Column(String, primary_key=True, nullable=False)
    col2 = Column(Integer, nullable=False)
    col3 = Column(String)

def main():
    new_col = case(
        [
            (
                TestTable.col1.in_(["a", "b", "c"]),
                TestTable.col1,
            )
        ],
        else_="Other",
    ).label("new_col")

    stmt = select(new_col, func.sum(TestTable.col2).label("sum_col2")).group_by(new_col)

    engine = create_engine(
        "redshift+redshift_connector://{user}:{password}@{cluster}.redshift.amazonaws.com:5439/{db}"
    )

    engine.execute(stmt)
    # with engine.connect() as conn:
    #     df = pd.read_sql(stmt, conn)
    #     print(df.shape)

if __name__ == "__main__":
    main()

Hi @v-kox , thank you for reaching out about this issue. I will look into reproducing it using the attached code and follow up with my findings.

@Brooke-white added an issue in the redshift-dialect project #252

closing in favor of sqlalchemy-redshift issue


Build started failing at Carthage step - fails to find Cartfile

Description of the issue
Build started failing at Carthage step. I've also tried to build a previous commit that succeeded before but it still fails with the error: 'Failed to read file or folder at /Users/vagrant/git/Cartfile'
Environment:
Where did the issue happen?
In Bitrise.io, stack: Xcode 8.0.x, on OS X 10.11 (El Capitan)
Which build Step causes the issue and which version of the step?
Carthage, tried both 3.0.0 and 2.4.0
Reproducibility
Started today and It's consistent.  I'm not using caching. Happens also with the last version of the step.

Does a "Rebuild" help? (You can trigger a rebuild from the Build's page, by clicking the "Rebuild" button in the top right corner of a finished build)

No

Does a rebuild without caches help? (You can remove the Cache:Pull and Cache:Push steps temporarily to not to use the cache, or you can delete all the caches on the Settings tab of the app.

I'm not using caching

If it's an issue which happens sporadically, what's the frequency? (e.g. Once a day ; about x% of the builds)

It's consistent

Does upgrading the build Step to the latest version help?

No

When did the issue start?

Today 18th November
Linux/Android stack builds

Can it be reproduced by running the build locally with Docker (using the same docker images we use on bitrise.io), after doing a clean git clone (git clone the repository, into a new directory, somewhere on your Mac/PC) and running the build from there? (Related guide: http://blog.bitrise.io/2016/08/08/debug-your-android-linux-builds-locally-with-docker.html )

NA
Other stacks

Can it be reproduced by running the build locally with our CLI ( https://www.bitrise.io/cli ), after doing a clean git clone (git clone the repository, into a new directory, somewhere on your Mac/PC) and running the build from there with the CLI?

120d8e074abab772.txt
Build log
Please attach the build log (you can download the build log from the build's page,
once the build is finished, using the "Download log" button - floating at the bottom right corner of the log viewer),
or if you can't attach the whole log then the related step's build log, or as much as you can share.
120d8e074abab772.txt

Are you sure that the Cartfile is in the root of the repository?
From your other configs it seems it might be in the EATMade directory inside the repository, and not in the repository root

It's in the EATMade folder but that didn't change.

Yes, but the Step did change - and you most likely upgraded to v3 of the step. Please see the release notes of 3.0.0 for a migration guide: https://github.com/bitrise-steplib/steps-carthage/releases/tag/3.0.0

I've noticed that and rolled back to 2.4.0 with the same result. The attached log uses 2.4.0

Just updated the release note for a migration note for the workdir input (which was removed) -> use the --project-directory ./EATMade parameter of carthage to define the work directory

I've noticed that and rolled back to 2.4.0 with the same result. The attached log uses 2.4.0

Yes, but as you upgraded to 3.0.0 and saved it, the unused/removed inputs were removed from your config too

Got it! Didn't notice that. Thanks

Yeah, it wasn't included in the original release notes' migration guide - just added it to it. Sorry for the inconvenience!


Publish lxd image no respond

When I run lxc publish, there is no response, and I have tried restarting lxd, but it doesn't work. I don't know where the problem is."

Solved.
Referenced to this.
The solution was quite simple — just restart the device.


can't install octal bonescript on debian 3.8

I saw that it is recommended to use version 1.0.0 on 3.8 kernel. I tried to install it but got a lot of errors. What more info do I need to provide?
root@beaglebone:/var/lib/cloud9/grow-io/realgrow# npm install<EMAIL_ADDRESS>\

<EMAIL_ADDRESS>install /var/lib/cloud9/grow-io/realgrow/node_modules/octalbonescript/node_modules/i2c
node-gyp rebuild

make: Entering directory /var/lib/cloud9/grow-io/realgrow/node_modules/octalbonescript/node_modules/i2c/build'   CXX(target) Release/obj.target/i2c/src/i2c.o   SOLINK_MODULE(target) Release/obj.target/i2c.node   SOLINK_MODULE(target) Release/obj.target/i2c.node: Finished   COPY Release/i2c.node make: Leaving directory /var/lib/cloud9/grow-io/realgrow/node_modules/octalbonescript/node_modules/i2c/build'

<EMAIL_ADDRESS>install /var/lib/cloud9/grow-io/realgrow/node_modules/octalbonescript/node_modules/epoll
node-gyp rebuild

make: Entering directory /var/lib/cloud9/grow-io/realgrow/node_modules/octalbonescript/node_modules/epoll/build'   CXX(target) Release/obj.target/epoll/src/epoll.o In file included from ../src/epoll.cc:15:0: ../node_modules/nan/nan.h:328:47: error: ‘REPLACE_INVALID_UTF8’ is not a member of ‘v8::String’ cc1plus: warning: unrecognized command line option "-Wno-unused-local-typedefs" [enabled by default] make: *** [Release/obj.target/epoll/src/epoll.o] Error 1 make: Leaving directory /var/lib/cloud9/grow-io/realgrow/node_modules/octalbonescript/node_modules/epoll/build'
gyp ERR! build error
gyp ERR! stack Error: make failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/share/node-gyp/lib/build.js:267:23)
gyp ERR! stack     at ChildProcess.emit (events.js:98:17)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:809:12)
gyp ERR! System Linux 3.8.13-bone70
gyp ERR! command "nodejs" "/usr/bin/node-gyp" "rebuild"
gyp ERR! cwd /var/lib/cloud9/grow-io/realgrow/node_modules/octalbonescript/node_modules/epoll
gyp ERR! node -v v0.10.29
gyp ERR! node-gyp -v v0.12.2
gyp ERR! not ok
npm WARN This failure might be due to the use of legacy binary "node"
npm WARN For further explanations, please read
/usr/share/doc/nodejs/README.Debian

<EMAIL_ADDRESS>install /var/lib/cloud9/grow-io/realgrow/node_modules/octalbonescript/node_modules/serialport
node-pre-gyp install --fallback-to-build

module.js:340
throw err;
^
Error: Cannot find module '/var/lib/cloud9/grow-io/realgrow/node_modules/octalbonescript/node_modules/serialport/node_modules/.bin/node-pre-gyp'
at Function.Module._resolveFilename (module.js:338:15)
at Function.Module._load (module.js:280:25)
at Function.Module.runMain (module.js:497:10)
at startup (node.js:119:16)
at node.js:906:3
npm WARN This failure might be due to the use of legacy binary "node"
npm WARN For further explanations, please read
/usr/share/doc/nodejs/README.Debian
npm ERR<EMAIL_ADDRESS>install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script.
npm ERR! This is most likely a problem with the epoll package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get their info via:
npm ERR!     npm owner ls epoll
npm ERR! There is likely additional logging output above.
npm ERR! System Linux 3.8.13-bone70
npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "install"<EMAIL_ADDRESS>npm ERR! cwd /var/lib/cloud9/grow-io/realgrow
npm ERR! node -v v0.10.29
npm ERR! npm -v 1.4.21
npm ERR! code ELIFECYCLE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     /var/lib/cloud9/grow-io/realgrow/npm-debug.log
npm ERR! not ok code 0

Can you try npm install<EMAIL_ADDRESS>?

it still didn't work, is there a problem with my node version? I know nothing about node...
root@beaglebone:/var/lib/cloud9/grow-io/realgrow/node_modules# ls -a
.  ..
root@beaglebone:/var/lib/cloud9/grow-io/realgrow/node_modules# cd ..
root@beaglebone:/var/lib/cloud9/grow-io/realgrow# npm install<EMAIL_ADDRESS>
<EMAIL_ADDRESS>install /var/lib/cloud9/grow-io/realgrow/node_modules/octalbonescript/node_modules/i2c
node-gyp rebuild

make: Entering directory /var/lib/cloud9/grow-io/realgrow/node_modules/octalbonescript/node_modules/i2c/build'   CXX(target) Release/obj.target/i2c/src/i2c.o   SOLINK_MODULE(target) Release/obj.target/i2c.node   SOLINK_MODULE(target) Release/obj.target/i2c.node: Finished   COPY Release/i2c.node make: Leaving directory /var/lib/cloud9/grow-io/realgrow/node_modules/octalbonescript/node_modules/i2c/build'

<EMAIL_ADDRESS>install /var/lib/cloud9/grow-io/realgrow/node_modules/octalbonescript/node_modules/epoll
node-gyp rebuild

make: Entering directory /var/lib/cloud9/grow-io/realgrow/node_modules/octalbonescript/node_modules/epoll/build'   CXX(target) Release/obj.target/epoll/src/epoll.o In file included from ../src/epoll.cc:15:0: ../node_modules/nan/nan.h:328:47: error: ‘REPLACE_INVALID_UTF8’ is not a member of ‘v8::String’ cc1plus: warning: unrecognized command line option "-Wno-unused-local-typedefs" [enabled by default] make: *** [Release/obj.target/epoll/src/epoll.o] Error 1 make: Leaving directory /var/lib/cloud9/grow-io/realgrow/node_modules/octalbonescript/node_modules/epoll/build'
gyp ERR! build error
gyp ERR! stack Error: make failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/share/node-gyp/lib/build.js:267:23)
gyp ERR! stack     at ChildProcess.emit (events.js:98:17)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:809:12)
gyp ERR!  Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script.
npm ERR! This is most likely a problem with the epoll package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get their info via:
npm ERR!     npm owner ls epoll
npm ERR! There is likely additional logging output above.
npm ERR! System Linux 3.8.13-bone70
npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "install"<EMAIL_ADDRESS>npm ERR! cwd /var/lib/cloud9/grow-io/realgrow
npm ERR! node -v v0.10.29
npm ERR! npm -v 1.4.21
npm ERR! code ELIFECYCLE
npm ERR! Error: ENOENT, lstat '/var/lib/cloud9/grow-io/realgrow/node_modules/octalbonescript/node_modules/serialport/node_modules/optimist/node_modules/minimist/index.js'
npm ERR! If you need help, you may report this entire log,
npm ERR! including the npm and node versions, at:
npm ERR!     http://github.com/npm/npm/issues
npm ERR! System Linux 3.8.13-bone70
npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "install"<EMAIL_ADDRESS>npm ERR! cwd /var/lib/cloud9/grow-io/realgrow
npm ERR! node -v v0.10.29
npm ERR! npm -v 1.4.21
npm ERR! path /var/lib/cloud9/grow-io/realgrow/node_modules/octalbonescript/node_modules/serialport/node_modules/optimist/node_modules/minimist/index.js
npm ERR! fstream_path /var/lib/cloud9/grow-io/realgrow/node_modules/octalbonescript/node_modules/serialport/node_modules/optimist/node_modules/minimist/index.js
npm ERR! fstream_type File
npm ERR! fstream_class FileWriter
npm ERR! code ENOENT
npm ERR! errno 34
npm ERR! fstream_stack /usr/lib/nodejs/fstream/lib/writer.js:284:26
npm ERR! fstream_stack Object.oncomplete (evalmachine.:107:15)
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     /var/lib/cloud9/grow-io/realgrow/npm-debug.log
npm ERR! not ok code 0

OK, success. I'm new to linux and didn't realizes you had to worry about versions of software changing so much. I install Debian 7.9 back in December from the beaglebone site, but apparently it was already out of date Here is the site that showed me 3 different ways of fixing this.
https://github.com/fivdi/onoff/wiki/Node.js-v0.10.29-and-native-addons-on-the-BeagleBone-Black
The problem was that I had node.jsv0.10.29, which is old.
Solution:
run these two obvious lines before attempting to install octalbonescript:
sudo apt-get update
sudo apt-get upgrade
I'm root so i didn't need the sudo...


[OpenAI] Update sample link

Update it to point to main instead of the deleted branch.

/check-enforcer override

API change check
API changes are not detected in this pull request.


Cross region discovery

Does Native-s3-ping support Cross Region Discovery?
I see the nodes write to s3 buckets however they are not able to connect to each other.

Can you post to the mailing list instead of creating an issue? The latter is for keeping track of feature requests/issues...


add blockid,blockheight, transactionid,siacoinoutputid to /consensus/blocks endpoint

I made several small changes to get the data I need to construct transactions manually. Wish you could help check if it's right. No need to merge to the codebase.

Now that we've merged https://github.com/NebulousLabs/Sia/pull/2980, you can get the block ID and height. As for the siacoin output IDs, that's a bit trickier. Instead of modifying types.SiacoinOutput, you could have the response include a map[types.UnlockHash]types.SiacoinOutputID. You could also replace the types.SiacoinOutput with a modules.ProcessedOutput.

Looks like we've merged all the relevant changes, closing this for now. Feel free to re-open if the master branch is still missing things


Cache all the mongodb/version folder

Seems that it may fix our problem by caching a folder up.

@flovilmart updated the pull request.

Merging as it has no side effects on the codebase


Naming convention for assembly instructions

Arithmetic instructions
With the work done in various recent PRs (#311, #326, #327) we have refactored u32 operations to follow the naming convention similar to u64 module in stdlib. Specifically, for many instructions we have checked, unchecked, wrapping, and overflowing variants. For example, for 32-bit addition we have the following:

u32checked_add
u32overflowing_add
u32wrapping_add

In the similar spirit, #327 also refactored pow2 operation to consist of 2 variants:

checked_pow2 which fails if the power parameter is greater than 63.
unchecked_pow2 which does not fail for any inputs, but for power parameter greater than 63 produces an undefined result.

We can take this naming convention further: if an operation can fail for some set of inputs, prefix it as checked.  For example:

inv -> checked_inv - can fail for divide-by-zero.
not -> checked_not - can fail if the input is not a binary value.
and -> checked_and - can fail if the inputs are not binary values.
or -> checked_or - can fail if the inputs are not binary values.
xor -> checked_xor - can fail if the inputs are not binary values.

Overall, I think the above would be cleaner, and it would be nice if we could always say that checked variants may fail for some inputs, while anything which is not checked will never fail, but for some inputs may produce undefined results. However, there are a couple of wrinkles:

There are some unchecked instructions which could fail on some inputs. For example: u32unchecked_div does not check if the inputs are 32-bit values, but would still fail in case of divide-by-zero`.
Some non-arithmetic instructions could fail for wrong inputs (e.g., cswap, cdrop, mtree.get, mtree.set).

So, the question is: given that we can't make the rule universal, should we still try to apply in cases where we can?
Other instructions
In the above convention, we use underscores to specify different variants of a given instruction and provide parameters for the instruction using dot notation. Should we try to apply it to other instructions as well?
In same cases, the renaming could be fairly trivial:

assert.eq -> assert_eq
mtree.get -> mtree_get
mtree.set -> mtree_set
mtree.cwm -> mtree_cwm

But in other cases, I'm not sure it is worth it. For example should pop.mem become pop_mem?

So, the question is: given that we can't make the rule universal, should we still try to apply in cases where we can?

Just to clarify - are you proposing having both checked and unchecked variants for the instructions you listed (inv, neg, and, etc) or are you proposing adding checked_ as a prefix to the existing instructions without adding any new ones? I probably wouldn't do the latter, since I don't think there's much benefit, and seeing a checked option usually gives the expectation of an unchecked option. (If you're proposing the former option, I'd want to think about it a bit more.)
Either way, I probably wouldn't try to apply the proposed rule to non-arithmetic instructions like cswap, cdrop, etc. It's less familiar, since in the broader context checked/unchecked is usually arithmetic, and it makes the rule less universal as mentioned.

In the above convention, we use underscores to specify different variants of a given instruction and provide parameters for the instruction using dot notation. Should we try to apply it to other instructions as well?

Consistency makes things more predictable & easier to use and maintain, so I think it might make sense to do this. I also have a preference for treating variants and inputs differently (as we are now doing with the u32 ops), since I think it's clearer. If we make a change at all, I think we should do it everywhere, including the io ops.
I took a look at the io ops to see how much work this would require. The biggest change needed would be in the validate_operation macro, and it should actually result in a simpler macro and simpler validation requirements (I think we could remove the top level validation), so it would probably even be an improvement in isolation. Due to the structure of the i/o instruction parsing, I don't think much is needed beyond this.

Closed by #341


Fix documentation of extra fields

Change Summary

Related issue number

Checklist

[ ] The pull request title is a good summary of the changes - it will be used in the changelog
[ ] Unit tests for the changes exist
[ ] Tests pass on CI
[ ] Documentation reflects the changes where applicable
[ ] My PR is ready to review, please add a comment including the phrase "please review" to assign reviewers

Yes, although it doesn't hurt understanding the meaning in general. The most important thing here was the missing leading spaces for the code annotation


Difference in isoWeek

Hi,
Because moment('2017/01/01').isoWeek() returns 52 and moment('2017/01/02').isoWeek() returns 1, I was expected that moment('2017/01/01').diff(moment('2017/01/02'), 'isoWeek')will return 1 as well.
But it returns value in milliseconds.
May the difference of isoWeek can be added to the diff method?
This could be very handy.
Iso dates have this great advantage to start on Mondays ;-)
Environment: Chrome 49 on OSX

That wouldn't make sense.  isoweek vs week is important when you are aligning to some representation of a week numbering system.  We use that with functions like .startOf(isoWeek) and .isoWeek().
The diff function does not align to any particular week numbering system.  It is just measuring the difference between the values provided.  A week is 7 days.
moment('2017-01-08').diff('2017-01-01', 'days')  // 7
moment('2017-01-09').diff('2017-01-02', 'days')  // 7
moment('2017-01-10').diff('2017-01-03', 'days')  // 7

Therefore:
moment('2017-01-08').diff('2017-01-01', 'weeks')  // 1
moment('2017-01-09').diff('2017-01-02', 'weeks')  // 1
moment('2017-01-10').diff('2017-01-03', 'weeks')  // 1


v 1.0.4

Draft proposal for v1.0.4 maintenance release.

Copy all files from v1.0.3 to v1.0.4.

Change parallel to sequential semantics.

Add field.valid as a key for matching in tables.

Update descriptions for primitive operations to clarify which ones produce undefined values.

Because of the copy step above, it will be easiest to review this by examining the individual commits, excluding the first.
Note that this pull request was originally #126. That pull request got mangled due to making p4-spec public. There is some discussion there that may be of interest.

My only remaining comment is that we should update the date from "March XX" when we are ready to pull the trigger on releasing.  Thanks!

I've fixed the dates, added a changelog, and built the PDF.
@cc10512 please review and then we'll merge and post?


Flags in STBImageResize are incorrect

Version
3.3.2 (nightly)
Platform
Linux x64, Linux arm64, Linux arm32, macOS x64, macOS arm64, Windows x64, Windows x86, Windows arm64
JDK
Zulu 17, but irrelevant
Module
stb
Bug description
The flags defined in STBImageResize are incorrect.
    /**
     * Set this flag if your texture has premultiplied alpha. Otherwise, stbir will use alpha-weighted resampling (effectively premultiplying, resampling,
     * then unpremultiplying).
     */
    public static final int STBIR_FLAG_ALPHA_PREMULTIPLIED = -1;

    /** The specified alpha channel should be handled as gamma-corrected value even when doing sRGB operations. */
    public static final int STBIR_FLAG_ALPHA_USES_COLORSPACE = -1;

Flags in stb_image_resize.h:
// Set this flag if your texture has premultiplied alpha. Otherwise, stbir will
// use alpha-weighted resampling (effectively premultiplying, resampling,
// then unpremultiplying).
#define STBIR_FLAG_ALPHA_PREMULTIPLIED    (1 << 0)
// The specified alpha channel should be handled as gamma-corrected value even
// when doing sRGB operations.
#define STBIR_FLAG_ALPHA_USES_COLORSPACE  (1 << 1)

Stacktrace or crash log output
No response

Hey @theagentd,
LWJGL 3.2.2-snapshot+9 is now available and includes this fix.

Thank you very much! :)


Added Kafka Streams sample dashboard

ad-hoc contribution by Marcelo ;)

ad-hoc contribution by Marcelo ;)

and @mcascallares :)

@jeanlouisboudart 🛎 😆


Expand compatibility descriptions

Based on discussion with Mark Miller and Priya.

cc @marklio

I think this is a big improvement from a content perspective. I'm not entirely familiar with the template process to know whether this would be a breaking change to the template (would it make new issues different from existing ones and make it hard to to machine categorization, etc.)

Thanks. We only just added these compatibility types, so I don't think any issues are actually labeled accordingly yet. A good time to make it right.


Try and fix the clear command for tests

No real test in Clear anyways. Just Shells out based on OS. Maybe find something that works later...


How to get inheritance working in an existing theme

I managed to get inheritance to work with antimatter using this instructions, I'm trying to do the same with bones, but the new theme will not inherit the theme Bones properly —no CSS in the header— .
The developer does not seem to know how to solve the issue, an open issue has been unanswered for 3 months.
How could I solve this issue myself? what has to be added to a theme in order for it to work properly with inheritance when creating a theme based on it?

@ganar Well, I can see I'm not alone with same issue... #1353

I'm glad you managed to make it work. I'm abandoning the idea of using inheritance in my new template, and instead will move forward with an skeleton template suggested by another user. Inheritance: it was good while it lasted.

Should be sorted with this commit: https://github.com/getgrav/grav/commit/874160480faf5d968a8f32a3f254618e4dd0ad0d

It really works. :+1:

Sorry to dig this up, but is there something else to do to make it work?
I tried with a fresh install today (1.3.3) and pulled bones theme via gpm, but sadly, no inheritance. Just unformatted content. Firefox's web console said it could not load some foundation css stuff with a "-" in the filename, so I suspect I am still experiencing the original issue here maybe?

It might be an issue with bones skeleton, it's definitely working for most themes.

Probably then...
it is not that big of an issue for me anyway, it's just that earlier this year i started a project for a client on a copy of bones and I thought I could maybe switch to properly using inheritance before handing the site over soon.
But now I will just finish it like this which is totally fine, too.
Thank you for your answer.


fix: use createResolver from kit

❓ Type of change

[ ] 📖 Documentation (updates to the documentation or readme)
[x] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

This PR aims to refactor all resolve functions to use createResolver from @nuxt/kit (this should also help in development steps such as not re-triggering build for every pnpm run dev but rather use stubs).
📝 Checklist

[ ] I have linked an issue or discussion.
[ ] I have updated the documentation accordingly.

Files with resolve:

module.ts
alias.ts
bundler.ts
dirs.ts
pages.ts
utils.ts

Good contribution!
I appreciate your help!

Just realised that this in the TODO as well 😄 https://github.com/nuxt-modules/i18n/blob/7943ca10a11ed07dc60b4bf3aa9896f8069ecd0f/TODO.md?plain=1#L8

Sorry need to close - should declutter some PRs! Will be reopen when convenient.


After BuildPack 8.7.0, JVM Launch Error in JRE 8

What happened?

What were you attempting to do?
Run a docker image built by bootBuildGradle with Gradle 7.1, Java 8 and Spring Boot 2.5.4.

What did you expect to happen?
Successfully run a docker image

What was the actual behavior? Please provide log output, if possible.
When I run a docker image built by BuildPack, Some JVM error occurs. This error appears after 8.7.0 released.
below is a log header and full log file hs_err_pid1.log
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007f2fc8dc22f7, pid=1, tid=0x00007f2fc9f2a700
#
# JRE version:  (8.0_302-b08) (build )
# Java VM: OpenJDK 64-Bit Server VM (25.302-b08 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# V  [libjvm.so+0xb2a2f7]  VirtualMemoryTracker::add_reserved_region(unsigned char*, unsigned long, NativeCallStack const&, MemoryType, bool)+0x77
#
# Core dump written. Default location: /workspace/core or core.1
#
# If you would like to submit a bug report, please visit:
#   https://bell-sw.com/support
#

Build Configuration

What platform (pack, kpack, tekton buildpacks plugin, etc.) are you
using? Please include a version.
I have no idea. I used only pure bootBuildImage

What buildpacks are you using? Please include versions.
A log of bootBuildImage with JVM errored verion,
error_version_log.txt
A log of bootBuildImage at yesterday that successfully launched. and it is same when force downgrade to 8.6.0
success_version_log.txt
I think JVM Option changes after BuildPack 8.7.0 cause error.
I checked UnlockDiagnosticVMOptions NativeMemoryTracking PrintNMTStatistics options are added
And  I've tried set docker env or gradle build option with JAVA_TOOL_OPTIONS to disable those things. But not works.
So, I forced downgrade builderpack version to 8.6.0 and it works.
bootBuildImage {
  builder = "paketobuildpacks/builder@sha256:3c5f88e55da475957bd03b4d6e852e0938bb73ee1a5184ae291a7566ca83d97f"
  runImage = "paketobuildpacks/run@sha256:562ddd10160a2629168a0108894766b46dff7f4b0db263ecabe35cd56fcbe56d"
}

What builder are you using? If custom, can you provide the output from pack inspect-builder <builder>?
No Customs

Can you provide a sample app or relevant configuration (buildpack.yml,
nginx.conf, etc.)?
Simple docker image build with run ./gradlew bootBuildImage with Spring Boot project in Github Action.
And Simple launch with Docker docker run [built-image]
name: ci

on:
  push:
    branches:
      - 'release'

jobs:
  docker:
    runs-on: ubuntu-latest
    steps:
      - name: Set up Docker Buildx
        uses: docker/setup-buildx-action@v1
      - uses: actions/checkout@v2
      - name: Set up JDK 1.8
        uses: actions/setup-java@v1
        with:
          java-version: 1.8
      - name: Grant execute permission for gradlew
        run: chmod +x gradlew
      - name: Build bootBuildImage with version
        run: ./gradlew bootBuildImage

Checklist

[x] I have included log output.
[x] The log output includes an error message.
[x] I have included steps for reproduction.

Interesting. I see this happening with Gradle builds, but not Maven builds. I need to investigate further and see what is different here.
Good news is I can replicate this. I'll keep you posted.

OK, so not related to Gradle. It is just purely Java 8 vs 11. My sample gradle app was using Java 8 by default, so it was impacted in my initial tests. We can look into this some more. The JVM has some bugs around enabling Java NMT using JAVA_TOOL_OPTIONS, which is what's triggering this. I thought we had worked around this in our tests, but seems like it's still triggering the bug.
You can work around this for now by adding BPL_JAVA_NMT_ENABLED=false when you run your application image. This will disable Java NMT. You must do this at runtime, not build time.

OK, so not related to Gradle. It is just purely Java 8 vs 11. My sample gradle app was using Java 8 by default, so it was impacted in my initial tests. We can look into this some more. The JVM has some bugs around enabling Java NMT using JAVA_TOOL_OPTIONS, which is what's triggering this. I thought we had worked around this in our tests, but seems like it's still triggering the bug.
You can work around this for now by adding BPL_JAVA_NMT_ENABLED=false when you run your application image. This will disable Java NMT. You must do this at runtime, not build time. So if you are running your container images with Docker, then you'd use docker run -it -p 8080:8080 -e BPL_JAVA_NMT_ENABLED=false apps/maven.

 -e BPL_JAVA_NMT_ENABLED=false  It works well. Thank you for a first aid guide.

OK, so not related to Gradle. It is just purely Java 8 vs 11. My sample gradle app was using Java 8 by default, so it was impacted in my initial tests. We can look into this some more. The JVM has some bugs around enabling Java NMT using JAVA_TOOL_OPTIONS, which is what's triggering this. I thought we had worked around this in our tests, but seems like it's still triggering the bug.
You can work around this for now by adding BPL_JAVA_NMT_ENABLED=false when you run your application image. This will disable Java NMT. You must do this at runtime, not build time.

Thanks！！！

We cut a release to workaround this issue today: https://github.com/paketo-buildpacks/java/releases/tag/v5.17.0. It disables Java NMT if you're on Java 8. If you try to enable Java NMT, it's going to fail with the same error.
There will be a fix in the next Bellsoft Liberica Java 8 release so we can enable Java NMT. It should go upstream to other OpenJDK releases after, but it's unclear how long that will take.


Adding outline and authors

As the title says...

@hartm Can you, please, use Stanislav for my name in the authors section? I prefer to use that in public documents.


Introduce Grouper objects

Builds on the refactoring in #7206

[x] xref #6610
[x] Use TimeResampleGrouper

@Illviljan could use some typing help here if you have the time :)

I'm not sure about the rest of the errors, @dcherian. Maybe IndexVariable needs to use the DataWithCoords mixin?
xarray/core/groupby.py:577: error: Value of type variable "DataAlignable" of "align" cannot be "Union[DataArray, IndexVariable]"  [type-var]
xarray/core/groupby.py:577: error: Value of type variable "DataAlignable" of "align" cannot be "Union[Dataset, DataArray, IndexVariable]"  [type-var]
xarray/tests/test_groupby.py:55: error: List item 1 has incompatible type "int"; expected "slice"  [list-item]

https://github.com/pydata/xarray/blob/d4db16699f30ad1dc3e6861601247abf4ac96567/xarray/core/alignment.py#L581-L588
https://github.com/pydata/xarray/blob/d4db16699f30ad1dc3e6861601247abf4ac96567/xarray/core/alignment.py#L31
https://github.com/pydata/xarray/blob/d4db16699f30ad1dc3e6861601247abf4ac96567/xarray/core/common.py#L376-L377

Variables don't have coordinates so that won't work.
mypy is correct here, it's a bug and we don't test for grouping by index variables. A commit reverting to the old len check would be great here, if you have the time.
It's not clear to me why we allow this actually. Seems like .groupby("DIMENSION") solves that use-case.


Basically working with pure JS AG Grid

Added an extra Tab ‘AG Grid’ for the grid display, but have retained the original Table tab so we can compare the results.   Have needed to use the pure JS version of AG Grid as couldn't manage to integrate the Vue component version in our project - see separate email.
Fix the scrolling issue on the Text tab (the whole pane including tab bar was scrolling).

Thanks for this @ihull - closing out as we have now moved to the new React implementation.


This database has local access protection

Hello,
Please remove local access protection.

Thank you !

@mihaiandreicut thanks for an creating a ticket. It should be fixed.

I will close the ticket but otherwise let me know if it still bugging you.


Add input group support for custom selects and custom files

Closes #24437, closes #22457

There's a duplicate id here @mdo; I'll leave it to you to fix later.


Pair programming poetry turtle

@jamesma560 @nataliele you'll need some spaces after the hyphens on this one.

fixed! :cake:


Move the bmp180 cmd into experimental

It looks like this cmd was forgotten when the experimental folder became more structured.

ah and we also had forgot to add it to https://github.com/google/periph/blob/master/cmd/README.md.
I'll merge this but I think I've received the two I ordered (lost somewhere in my stack of junk) so we should write a smoke test and unit test and we could migrate this back into non-experimental soonish.

Perfect, let me fix the readme first.

@fd0 fyi.

Ok, nvm :)

Codecov Report

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

@@           Coverage Diff           @@
##           master     #140   +/-   ##
=======================================
  Coverage   84.09%   84.09%
=======================================
  Files          61       61
  Lines        4679     4679
=======================================
  Hits         3935     3935
  Misses        674      674
  Partials       70       70

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 889812a...7f8b27b. Read the comment docs.

Thanks!


Improve shader performance

We can probably gain some performance by improving our shaders. Investigate possible options to make our shaders faster.

Sure...one day... one day...


[ISSUE] Oxygen Gear and Thermal Padding getting reset after re-joining a world/server

Issue Description:
When re-joining a world/server the oxygen gear and thermal padding inventory gets reset to default deleting any new tanks or padding that the player has added
What happens:
Before leaving a world:

After leaving a world:

Important Versions Info (Do not use "latest"):

Modpack: Astroblock 2 (Not out yet)
Minecraft: 1.12.2
Forge: <IP_ADDRESS>54
GalacticTweaks: GalacticTweaks-1.0.0
Galacticraft: GalacticraftCore-1.12.2-<IP_ADDRESS>0
Using a server (yes/no): Yes

If yes, are any Server API's used, what version? (ex: Sponge): No

List any Galacticraft Addons w/ versions:
Addons:
GalacticraftTweaker-1.12.2-1.0.3
GalaxySpace-1.12.2-2.0.14
PlanetProgression-1.12.2-0.4.4

Your most recent log file where the issue was present:
https://gist.github.com/knoxhack/71e671cffde8dd59ea689fc9883a40e2

Ill get this fixed asap

Thanks 😊

Not a problem thanks for pointing that out
the updated version is now avilable
https://www.curseforge.com/minecraft/mc-mods/galactictweaks/files/3032603


ArrayIndexOutOfBoundsException

When crafting certain items using a shapeless recipe (crafting table -> crafting station in my case, but it varies), minecraft fails to lookup the recipe output and, if I check the log, I find an error like this:
Error executing task on Server
java.lang.ArrayIndexOutOfBoundsException: 4
	at it.unimi.dsi.fastutil.ints.IntArrayList$1.nextInt(IntArrayList.java:500)
	at it.unimi.dsi.fastutil.ints.IntIterator.next(IntIterator.java:43)
	at it.unimi.dsi.fastutil.ints.IntListIterator.next(IntListIterator.java:102)
	at it.unimi.dsi.fastutil.ints.IntListIterator.next(IntListIterator.java:30)
	at java.util.AbstractCollection.toArray(AbstractCollection.java:141)
	at java.util.List.sort(List.java:477)
	at net.minecraft.item.crafting.Ingredient.func_194139_b(Ingredient.java:97)
	at shadows.placebo.recipe.FastShapelessRecipe.func_77569_a(FastShapelessRecipe.java:40)
	at shadows.placebo.recipe.FastShapelessRecipe.func_77569_a(FastShapelessRecipe.java:15)
	at net.minecraft.item.crafting.IRecipeType.func_222148_a(SourceFile:29)
	...

With Polymorph installed I'll also get this:
Attempted to craft using [1 oak_planks, 1 air, 1 air, 1 air] but an error occurred while fetching recipes!
java.lang.ArrayIndexOutOfBoundsException: 4
	at it.unimi.dsi.fastutil.ints.IntArrayList.add(IntArrayList.java:260)
	at net.minecraft.item.crafting.Ingredient.func_194139_b(Ingredient.java:94)
	at shadows.placebo.recipe.FastShapelessRecipe.func_77569_a(FastShapelessRecipe.java:40)
	at shadows.placebo.recipe.FastShapelessRecipe.func_77569_a(FastShapelessRecipe.java:15)
	at net.minecraft.item.crafting.IRecipeType.func_222148_a(SourceFile:29)
	...

and later:
Attempted to craft using [1 air, 1 air, 1 crafting_table, 0 air] but an error occurred while fetching recipes!
java.lang.ArrayIndexOutOfBoundsException

This can also result in item duplication for the ingredients.
This also happens for logs->planks and plank->button
As you stated in your comments on curseforge this may be related to a broken recipe in another mod, but this seems to break every shapeless recipe, and provides no information about which recipe is causing the problem.
latest.log
Placebo-1.15.2-3.0.2.jar
polymorph-FORGE-1.15.2-0.3.jar
forge-31.2.30
minecraft 1.15.2

I don't know what mod is causing the problem, it doesn't occur in any of the major 1.15 modpacks, but you can use this jar to determine what recipe is causing the issue https://github.com/Shadows-of-Fire/Placebo/releases/tag/3.1.0-recipedebug

What makes you think it doesn't occur in any of the major 1.15 modpacks? We get this issue reported several times per day on the Valhelsia Discord for Valhelsia 2. I just haven't been able to track down the cause yet due to illness, and the crash reports + logs are essentially identical so don't provide any additional information (prior to you releasing that JAR there, of course).
It's why I asked about disabling the changes that Placebo makes like the CurseForge description still says is possible. I wanted to rule it out as an issue entirely if I could so that I could narrow down the possible causes.

Try as I might I cannot get it to happen on Valhelsia, and if it was happening in ATM5, drunk would be yelling at me nonstop, which is what precedes that statement.

Pretty common example: https://paste.ee/p/e9U8Z
I try not to yell at people, especially as in this case as I have no idea who I should be yelling at and haven't had the energy to deal with things in depth yet. My only frustration with you was the inaccurate CurseForge description leading me to trying to figure out how to disable the functionality for far too long before giving up.
For the most part, people say they're trying to craft simple things like planks from logs. This one here: https://paste.ee/p/1vGLJ was somebody who said they started a new world, harvested some birch logs, and crashed as soon as they opened their inventory. After updating to the version of Polymorph that prevents the game crashing they were unable to convert birch logs into birch planks in their inventory crafting screen.

I'm having a hard time getting this bug to show up when I want it to.  I've installed your debug mod though, and when it turns up again I'll report it.
If you're right about the cause, this should be easy enough to reproduce (same mods, same recipes, same bug), but it seems to be pretty fickle.

I think perhaps the most confusing part is this: https://paste.ee/p/e9U8Z#s=0&l=6043
Where this is happening, the array should've already been resized to make this effectively impossible.  I'm starting to wonder if this is even a recipe or mod issue, as it may be an issue with the mojang-provided FastUtil library...
Until someone can mark a recipe as erroring with this, I can't really determine the cause.  There's also a possibility that it's something more complex such as a JVM internal issue based on the type being run, but that would be really weird.
The only other place this functionality is used is in the recipe book, and with that being disabled in every modpack, this issue won't ever pop up there.

I'm going to make a prediction now based on where I have seen issues with FastUtil before (and where it's being called in the exception you linked to): This is some annoying concurrency issue, since FastUtil isn't thread safe.

Hm, that is.... theoretically possible?
Question is what is doing recipe ops like that off the main thread in the first place.
Technically it would be avoidable by invoking getValidItemStacksPacked immediately after the recipes are constructed (so that the initialization is never in a race condition)

Looking closer, I'm thinking more and more like that's the issue. See that log again - there's two threads in play, the Server Thread and the Render Thread. The former is handling the CClickWindowPacket and the latter is handling Polymorph's various methods.

I can't promise that fixes it, but if it is a race condition, it should.

If it's on CurseForge in the near future, then I will know soon enough, since we're pushing the next Valhelsia release as soon as we can... if it works then the reports will stop coming. :)
Appreciate the quick fix.

not fixed...
Error executing task on Server
java.lang.RuntimeException: The recipe silents_mechanisms:metals/electrum_nuggets has thrown an exception while matching, this is a bug in the owning mod.
	at shadows.placebo.recipe.FastShapelessRecipe.func_77569_a(FastShapelessRecipe.java:49)
	at shadows.placebo.recipe.FastShapelessRecipe.func_77569_a(FastShapelessRecipe.java:15)
	at net.minecraft.item.crafting.IRecipeType.func_222148_a(SourceFile:29)
	...

Attempted to craft using [1 air, 1 air, 1 spruce_log, 1 air] but an error occurred while fetching recipes!
java.lang.RuntimeException: The recipe silents_mechanisms:metals/electrum_nuggets has thrown an exception while matching, this is a bug in the owning mod.
	at shadows.placebo.recipe.FastShapelessRecipe.func_77569_a(FastShapelessRecipe.java:49)
	at shadows.placebo.recipe.FastShapelessRecipe.func_77569_a(FastShapelessRecipe.java:15)
	at net.minecraft.item.crafting.IRecipeType.func_222148_a(SourceFile:29)
	...

latest.log
mc 1.15.2
forge-31.2.30
Placebo-1.15.2-3.1.0.jar
polymorph-FORGE-1.15.2-0.3.jar
SilentMechanisms-1.15.2-0.7.6+57.jar
Looking at the recipe json in SilentMechanisms, I really don't see any problems, but I'm not great with datapacks yet:
{
  "type": "minecraft:crafting_shapeless",
  "ingredients": [
    {
      "tag": "forge:ingots/electrum"
    }
  ],
  "result": {
    "item": "silents_mechanisms:electrum_nugget",
    "count": 9
  }
}

You're not using the release that was pushed to curse, which is the one that fixes the problem

yeah, just noticed both the debug version I manually installed and the curseforge release were in the mods folder and neither disabled.  Not really sure why that didn't give me an error during startup.

Hey @Vaelzan , in 1.15 have you noticed any shapeless recipes being broken (to the degree of what's happening in #16)

No, 1.15 is currently fine from what I can tell after the fix a while back. Everybody yelling at us recently about recipe issues has been talking about 1.16.1.


[BUG] The claims for verification control have not been verified (B2C login)

Library name and version
Microsoft.AspNetCore.Authentication 6.0.6 (not sure if this is even correct?)
Describe the bug
My client receives "The claims for verification control have not been verified" on the B2C login.
see: https://github.com/azure-ad-b2c/samples/issues/293  and https://docs.microsoft.com/en-us/answers/questions/934866/error-34the-claims-for-verification-control-have-n.html
difference between pressing enter and clicking with mouse in Azure B2C login.
(not sure if this is the appropriate place (don't know where to post), but a ticket was not made for it).
Expected behavior
don't see the error message.
Actual behavior
error message: "The claims for verification control have not been verified"
Reproduction Steps
https://docs.microsoft.com/en-us/answers/questions/934866/error-34the-claims-for-verification-control-have-n.html
see: https://github.com/azure-ad-b2c/samples/issues/293
but there was not a ticket made for it in Azure, so here it is.
Environment
Visual Studio 2022
.net 6, Azure, B2C login, Blazor server side app.

Label prediction was below confidence level 0.6 for Model:ServiceLabels: 'Storage:0.2254071,Azure.Identity:0.1402401,Service Bus:0.112383276'

I don't believe this bug is related to the Azure SDK. Is this what you're looking for? https://docs.microsoft.com/en-us/azure/active-directory-b2c/find-help-open-support-ticket#open-a-support-ticket

Closing this as we are unable to help since this is not an issue related to the Azure SDK.

In case anyone comes here by accident... according @thesheebs it has been fixed:
Alas, after more than a year and a lot of persistence, Microsoft has fixed the bug. SelfAsserted 2.1.17 and UnifiedSSP 2.1.8 are now available.
https://github.com/azure-ad-b2c/samples/issues/293#issuecomment-1310662126


Actions test

Brief Description
Implemented small github action for unit testing.
References Issue
N/A
Type of change

[ ] Bug fix
[x] Feature
[ ] Major change (potentially breaking, list anything that is broken below)
[ ] Documentation

Breaking Changes
N/A
Testing done

[ ] Testing with a working test branch

[x] Docker was used.

[ ] Docker was not used and I have listed my configuration below.

System Specifications:

Operating System:
Node Version:
NPM Version:

Checklist:

[ ] My code follows the styling guidelines.
[ ] I have added unit tests and verified that they pass.
[ ] I have used the linter and fixed any linting issues.
[ ] I have commented the code.
[ ] I have adjusted the documentation to match the changed code.
[ ] Prior to submitting the PR, I made sure the latest changes were merged with my branch.
[ ] Existing tests pass locally with changes.

Explanation for unchecked
This is a github actions PR.
Additional information:
Provide any additional information that might be useful for this commit.

If anyone other than me merges this, please squash before merge.


Gaussian naive bayes

I implemented the Gaussian Naive Bayes algorithm. I added tests, a notebook and updated the docs.

Closes #4

Thanks! What linter would you recommend? I've used pyflakes and pylint but they missed most of the things you pointed out.

Also, not directly related to this: most python packages adopt the snake_case naming convention for files. Wouldn't it make sense to do the same here?

I implemented most of the requested changes. I am not sure the docstrings in the rest of the package follow PEP8. I left mine as they were; I can follow the rest of the package, and we may address this in an another PR.

First of all, I appreciate your enthusiasm for this project. I'm glad you have a lot of ideas to contribute.
However, I would ask that you please follow the contributor guidelines (https://github.com/parsing-science/pymc3_models/blob/master/CONTRIBUTING.rst), particularly the section about following existing conventions. I made thoughtful deliberate decisions about style and the code itself so I'd appreciate if you respected those.
If you want to refactor your code to match the rest of the repo, I'll be happy to take another look at your PR.

Sorry, I wasn't questioning your choices. Seeing the references to scikit-learn and numpy in the README and CONTRIBUTING, I started writing code with those in ming. I realised after the fact that the conventions adopted here were slightly different. Not a problem for me, I was happy to refactor to match the rest of the repo.
I ran pyflakes and pycodestyle on both the model and tests. All I got were unused variables in the declaration of the model, and lines longer than 79 characters---they are all shorter than 100 characters thought.

This looks great! @parsing-science are there any outstanding issues you see?

I've been busy with some personal stuff in the last few months. I'll try to take a look in the next few weeks.

Is there anything I can do to help? I started implementing other models, but I would like to have this PR merged before making them PR-ready.

I'm still waiting for the tests to finish, please wait before reviewing the changes.

All right, I made all the requested changes and the tests now pass (your fix did the trick). I also added a picture of the graphical model corresponding to Naive Bayes for the sake of being fancy. If this looks ok to you I can do a final rebase to clean this up before merging.

I (finally) addressed all the issues you raised, rebased my branch onto master and update the date in the changelog. This should be ready to merge if you approve of the changes.


Interface sensitivity only affects when moving cursor to sides, and game sensitivity affects cursor when moving up/down

Seems like interface sensitivity isn't quite properly implemented
https://github.com/Wilyicaro/Legacy-Minecraft/assets/39068731/21aa6db3-a6e1-4347-b003-21262d414a40

Fixed in version 1.5.1, thanks for reporting.


Migrate from Travis CI to GitHub actions

We're looking to move from Travis CI to GitHub Actions to match the rest of the Cesium organization.
While there's a lot of awesome features in GitHub Actions we can start taking advantage of to automate more of or processes, this initial PR migrates the existing Travis CI functionality. That includes:

Linting
Running tests
Verifying npm packages
Building and deploying to S3
Running coverage and deploying results to S3
Setting the status to include links to both of the above deployments
A specialized deployment when pushing to the cesium.com branch
Slack notifications on a failed commit on main or cesium.com branches

Thanks for the pull request @ggetz!

:heavy_check_mark: Signed CLA found.
:grey_question: CHANGES.md was not updated.

If this change updates the public API in any way, please add a bullet point to CHANGES.md.

:grey_question: Unit tests were not updated.

Make sure you've updated tests to reflect your changes, added tests for any new code, and ran the code coverage tool.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.

@ggetz If you search for travis there are still a ton of references, mostly doc but a few in .gitignore and build.js (and even a few code comments).
It's probably worth doing a pass to clean these up as well. If you think it makes sense to do them as a follow-up PR instead, that's fine too. Let me know.

The deployment link in the PR status 404s: http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/github-actions/
All other artifacts seem to work though.

That's all I have for this go around @ggetz

Thanks for the review @mramato!

The deployment link in the PR status 404s

This was due to the 30-day cleanup in s3 since we skip re-uploading existing files. We disabled this behavior for the main branch so that the files would be "touched" each CI run for the sake of this cleanup rule. Since it's showing up here as well, I've gone ahead and disabled it for development branches as well.

If you search for travis there are still a ton of references, mostly doc but a few in .gitignore and build.js (and even a few code comments).

I've gone ahead and replaced these in this PR, as well as updating the contributor documentation.

Thanks, @ggetz I pushed one last tweak for some leftover travis references I found but will merge as soon as this goes green.


Using Ollama llama3.1:8b  the UI never references entity nodes and HAS_ENTITY relationships created

Apologies in advance for duplicating issue - can't find the note that there are known Ollama issues:
My graph created using LLM set to Ollama llama3.1:8b creates looks correct - lots of entities but
Clicking on View column in the results table gives
No Nodes and Relations for the  file
The KG does though contain nodes and HAS_ENTITY relationships.
The chatbot does work. In Retrieval information, Sources used is correct. But Top Entities used and Chunks are blank

which mode you used for chat?

Make sure that you should chat after post processing call for better/advanced retrieval

Hi Michela,
Can you please provide some screenshots from your graph and outputs from the processing?
You can also copy the whole table row now into a json and download the chat as json as well for sharing.
And perhaps also the file that you used  for testing?