HT420-A Tweezers support

Hi there. My name is Niki. I'm PCB and 3D designer and I have been making many /mostly analog/ projects for over 15 years.
I checked your project. It looks good. I think to modify it a little bit the board since the tracks going to the pads has no teardrops and it's better to have ticker wires around the pads.
Anyway, I have JBC TH420-A soldering tweezers and I think it's good for having an optional way to power similar tweezers.
There is already one free thermocouple input - the spare input of ADS1118. So the only one extra hardware modification will be one wire for the current sense for another VN5E010AH. Both drivers can share the same PWM.
I can modify the PCB with all new improvements but I can't modify the code. I'm a PCB designer.
What do you think about that?
Another "Extra" modification could be two inputs - one for JBC iron and another for iron/tweezers.
Thanks and waiting for your answer.
Niki

If you have a look at the branch I made, there is code for tweezers. I designed it for PA120 tweezers, not 420. I have a feeling the maximum voltage is higher on the 420, so it would be worth checking it will work.
In any case, the code is there if you want it.
p.s. my PCB design is not great. my plan is do redo it.
https://github.com/PaulusSmallus/JBC-Soldering-Controller

I want do it to
can we do it together？
<EMAIL_ADDRESS>

Thanks for the update!
I started with the PCB design but I'm busy with some other projects. I hope I will be ready until the end of this year.

Hello liu wei,
I am sure there is something you can help with. What are you good at?

I am a  chinese, everything the project need is so easy and cheap to get .
I redesign your sch by orcad.    Meger the  arduino  in the main board .
I have a  team with my friend include the software and hareware ,structure .
Can we design a product with comparable or even better performance than JBC?


Update opentelemetry-agents.md

Fixing typo in logsConfiguration for AppInsights

@craigshoemaker

Can you review this PR?
IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Thanks for catching the typo!
#sign-off

#sign-off

#sign-off


feat: add NGRX_UPDATE_ON_TYPE type to library exports

I faced with a case where I need to programmatically set the ngrxUpdateOn value from a directive. Therefore It would be great to have an access to NGRX_UPDATE_ON_TYPE so I wouldn't need to have a crappy code like .ngrxUpdateOn = 'blur' as any.
I hope this might be relevant for others too.

Hi @MrWolfZ, thanks for the beautiful library.
Just a suggestion on the above type is it possible to export the NGRX_UPDATE_ON_TYPE as type instead of enum this will help the template to recognize the type while setting the value like ngrxUpdateOn="blur", currently the IDE sees this as unrecognized type. By converting this from enum to type user will be able to correctly set the values during development as well.
I will be ready to create a PR for this changes, let me know your thoughts on the same?
Thanks.


upgrading to ligo v1.1.0

with new Interfaces feature :P

Thank you @LigoSuzanneSoy . No worry , it is just an adaptation to recent Interface feature, just same code implementation at the end


Old kubernetes version is deployed

I installed kubernetes cluster few days ago and I noticed that after creating private docker images registry secret, It was using old docker format
kubectl get secret regcred --output=yaml

apiVersion: v1
data:
  .dockercfg: <secret>
kind: Secret
metadata:
  creationTimestamp: 2018-03-24T17:35:46Z
  name: regcred
  namespace: default
  resourceVersion: "531948"
  selfLink: /api/v1/namespaces/default/secrets/regcred
  uid: <uid>
type: kubernetes.io/dockercfg

In kubernetes 1.9 it uses type of type: kubernetes.io/dockerconfigjson
Here is kubernetes version that I see
Client Version: version.Info{Major:"1", Minor:"8", GitVersion:"v1.8.6", GitCommit:"6260bb08c46c31eea6cb538b34a9ceb3e406689c", GitTreeState:"clean", BuildDate:"2017-12-21T06:34:11Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"8", GitVersion:"v1.8.5", GitCommit:"cce11c6a185279d037023e02ac5249e14daa22bf", GitTreeState:"clean", BuildDate:"2017-12-07T16:05:18Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}

https://github.com/kahkhang/kube-linode/blob/master/manifests/container-linux/master-config.yaml#L55 Here default BOOTKUBE_VERSION is 0.9.3 which includes kuernetes 1.8

Thanks for the catch @anjmao! I might have bumped the hyperkube version too early before bootkube upgraded their hyperkube version :(


Fix loss of precision on alpha values

Alpha was rounded to provide a resolution of only 100 gradations, whereas 32-bit color supports 256. Translating from decimal to hex and vice versa made over half of possible alpha values unavailable.

Hi, thanks for the PR.  Can you please come up with a small test case where this loss of precision was happening and add it to: https://github.com/bgrins/spectrum/blob/master/test/tests.js#L569?

Something wrong with the test? I ran it against the existing code and it detected the loss of precision for me.

Something wrong with the test? I ran it against the existing code and it detected the loss of precision for me.

I see that now.  It looks good, thanks

Landed in https://github.com/bgrins/spectrum/commit/8ee9561053c0facbe689cc88706674ea673be670


Add a method to manually remove an experiment from the database

Pruning is sometimes not sufficient in the case of mis-indexed experiments. An experiment can be manually cleared from the database with this new method.
Closes #217.
@aidanheerdegen note that the way the cascades are currently set up, this will clear any associated NCFile and NCVar objects, but not CFVariable -- would this cause a problem with experiment exploring?

Fairly painless rebase on the code formatting change, and the CI check appears to be working 🚀

@aidanheerdegen note that the way the cascades are currently set up, this will clear any associated NCFile and NCVar objects, but not CFVariable -- would this cause a problem with experiment exploring?

I don't think so, as it uses get_variables for each experiment, so all good I think from that POV


How to change icon image

Hi, I want to change the icon-star image in my theme. So I created a file thread-list.less, then I added these lines for my icon that resides in my template folder:
.thread-list .thread-icon.thread-icon-star,
.draft-list .thread-icon.thread-icon-star {
  background-image: url("../images/icon-star-@2x.png");
}

It seems to not working, what is the correct path to rely on the images folder on my theme?
Note : The CSS is loaded right, if I put background-image: none; The icon disapear.

I found how to do:
.thread-list .thread-icon.thread-icon-star,
.draft-list .thread-icon.thread-icon-star {
  background-image: url("mailspring://my-theme/images/icon-star-@2x.png");
}


password mandatory when converting to pkcs#8

Hi @youmark,
As the goal of this library is to support - and promote? - the use of password-protected private key with strong encryption algorithms, I suggest you make the password parameter mandatory when converting to PKCS#8.
Those who prefer to keep their private key in plaintext can still use MarshalPrivateKey, where the password remains optional.
Also, this way, ConvertPrivateKeyToPKCS8 and MarshalPrivateKey have two different purposes.
Regards,
Philippe.

This doesn't seem to cause regressions from the tests, but it's an API break, so it would require a major version bump.


Add set.isdisjoint

Codecov Report

Merging #853 into master will increase coverage by 0.01%.
The diff coverage is 77.77%.

@@            Coverage Diff             @@
##           master     #853      +/-   ##
==========================================
+ Coverage   63.14%   63.16%   +0.01%
==========================================
  Files          88       88
  Lines       14591    14607      +16
  Branches     3265     3269       +4
==========================================
+ Hits         9214     9226      +12
  Misses       3239     3239
- Partials     2138     2142       +4

Impacted Files
Coverage Δ

vm/src/obj/objset.rs
71.47% <77.77%> (+0.1%)
:arrow_up:

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 3afb5d3...3986e2f. Read the comment docs.


Add overloads to JSON::Value to allow assignment of size_t types (#214)

Addresses build-time issue on MacOS. Not tested on other platforms.

On Linux, this change breaks the build: size_t and uint64_t are aliases on 64-bit Linux configurations, and it will complain about a duplicate declaration.
The way we've fixed this so far (there were many more cases of this problem in the past) is to typecast to uint64_t whenever we assign a size_t to a JSON value. Been meaning to go through all the cases we missed, but MacOS is not exactly a priority at the moment since practically none of our customers use it.
It would probably be better to add a precompiler check around a size_t version of these functions, to only add them in if size_t is not already an alias of an existing declaration. 🤔


Update SetValidatorMaxCount to appropriate value

The maximum number of validators need to be updated to correctly reflect current limitations. Some of these limitations come from Validators staking cost, communication limitations, and ability to successfully submit accusations within the current gas limit.
These limitations can be determined from testing.

https://github.com/MadBase/MadNet/blob/main/blockchain/contracts.go#L571


Caching of one selection for all other crops selected later(Browser specific)

While creating a new guide for a crop, we are redirected to a new page where we select the crop and then the crop image is displayed. If we change our mind to make a guide on some other crop and go back to select that crop and then click on creating a new guide, it redirects us to a page, not asking for the crop but it displays our previous selection. This happens even if we login into our account again and we are able to enter our choice only after manually cancelling it.
For example:
We decided to make a guide on tomatoes.

Then we selected the option to create a new guide and selected tomatoes on the redirected page.

After that, display image for tomato was on the screen.

But after this step we realised that we wanted to make a guide for cherry tomatoes and decided to go back and selected cherry tomatoes.

After selecting create your guide in cherry tomato, instead of getting an option to choose a crop, we got an image of tomato already selected which was actually our previous selection.

This was resolved only after manually cancelling the selection we had made in the first attempt. This problem is browser specific. Entries are cached in that browser but not in our account.
@simonv3 @roryaronson @sophiakc please do look into it.

@Rupal-IIITD, I think this is happening because the browser is caching a partially completed Guide which we want to do in case you are farther along the guide creation process and your browser crashes or you accidentally close it. Right @simonv3?
Though it doesn't make much sense to cache the Guide if the user has only selected a Crop. Cause that's easy to re-do if the user needs to.

I think once the author completes the guide, the cache is cleared. If you click the "Add Guide" button from another Crop, rather than clearing the cache and starting off with the new Crop, it loads the cache.
Making the cache less aggressive such that it only starts caching if the user reaches a certain point in the Guide creation flow I think makes more sense. A logical point to me to begin caching would be on the Stage Details portion. Once the author has entered stage details then we start caching.
Oh, I also just realized - there used to a be a toast notification that popped up saying something like "Looks like you already started a guide but didn't complete it. We loaded it for you here, but if you want to start from scratch, click here". That notification does not seem to be working anymore which may have helped you have more clarity into the situation.

Ohh okay.
You rightly said that it makes more sense if we make it such a way that caching happens

Ohh okay.
You rightly said that

Thanks for creating this issue @Rupal-IIITD! I'm going to tag this into #813 so that we're aware of it while considering changes to guide creation.

Sure.
I and my teammate, @gargi-gupta will try and solve this issue.
Thanks :)

@Rupal-IIITD okay! Can you elaborate on this a bit?

I would like to add one thing here, as I mentioned earlier, that it should cache entries specific to a crop. Not for all.

For example: If a user is making a guide on tomatoes and accidentally closes the tab or loses power supply, then on reopening, the guide created till that point should be present. The user should not make the guide from scratch again.
But this caching for tomato should not appear for any other crop. On reopening the tab, if the user wants to make a guide on cherry tomatoes instead of tomatoes, then the saved guide for tomatoes should not appear for cherry tomatoes.
I think this is what @Rupal-IIITD meant to say.

Yeah @gargi-gupta is right!
Any suggestions?

So basically if the user is still on step one of guide creation, the guide shouldn't be cached?

It should cache the guide only when it is at a certain level of guide creation(after 1st step, of course) and that too only for that crop.

Sounds good to me. While you're in there can you also fix a thing where it's not properly caching nested stages? (kind of just kidding - I haven't debugged this properly, but if you do get around to it, that would be awesome!)

Yes, @Rupal-IIITD and I will definitely work on this.

Yeah!
Thanks @simonv3 @roryaronson for your inputs. We will try and work on this.


Reinstate "Use Swift 5.7 base image for Swift CI jobs to support bootstrapping"

With https://github.com/apple/swift/pull/66199, we're close(r) to the point where we can build the Swift compiler that integrates Swift code built using the host Swift.

@swift-ci please test

Ideally all our release images would install into /opt/swift/ instead of /usr

this is where I was going with my questions. I think we should fix this going forward

cc @etcwilde @MaxDesiatov

Yep, using /opt/swift-<version> means we can install toolchains for multiple versions of swift (important since we don’t have ABI stability guarantees on Linux), and so that we don’t conflict with the distribution toolchains. This is consistent with how redhat and centos bundle additional and newer toolchains. It’s also consistent the UNIX directory hierarchy spec.

reserved for the installation of add-on application software packages.

It gives us a lot more flexibility for how we want to distribute things.

fwiw, not all distributions like things in /opt so this may need to be refined per distribution, but 100% with the approach and we should def fix it in the toolchain packaging itself since its more correct

I've updated to use a downloaded toolchain rather than the base image for all Linux platforms - https://github.com/apple/swift-docker/pull/346. Made a new PR since I wanted to rebase + squash.


dedicated, password change-only page

It would be great to have a URL dedicated to password changes/resets only, mostly for scenarios where Modoboa serves as a configuration and management backend and users don't interface with Modoboa directly.
A (preferably skinable) simple web page with a simple form: login, old password, new password, repeat password and perhaps a reset password button sending new password to secondary e-mail (does Modoboa have this? Didn't find this option).
The idea is to isolate users from Modoboa in scenarios where they do not come to contact with it in any use cases and having them log in to an unknown environment might be confusing.
Please note that API is not the same as this feature and writing own service to change passwords via API is not viable as it would have to hold a full-access API key which is a security risk. This should be operable by user without any privileges.

It seems Modoboa identities contain a secondary email field already.
Password-reset pages are also a high demand from our communities.

A password reset service is available since 1.9.0.


Note about adding multitenant apps as application users.

Note about adding multitenant apps as application users.
Like with managed identities, enterprise applications needs to be exility added, as they do not show in the drop down (only app registrations does).

@paulliew, are you OK with this change?  If so, I'll merge it.  Thanks!


nss_wrapper: 1.1.12 -> 1.1.15

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/nss_wrapper/versions.
meta.description for nss_wrapper is: A wrapper for the user, group and hosts NSS API
meta.homepage for nss_wrapper is: https://git.samba.org/?p=nss_wrapper.git;a=summary;
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.1.13 with grep in /nix/store/97srb71ny58r0m3ripvkazb1igspwi9k-nss_wrapper-1.1.13
found 1.1.13 in filename of file in /nix/store/97srb71ny58r0m3ripvkazb1igspwi9k-nss_wrapper-1.1.13

Rebuild report (if merged into master) (click to expand)

5 total rebuild path(s)

5 package rebuild(s)

First fifty rebuilds by attrpath
autofs5
nss_wrapper
python310Packages.django-scim2
python311Packages.django-scim2
sssd

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/97srb71ny58r0m3ripvkazb1igspwi9k-nss_wrapper-1.1.13 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A nss_wrapper https://github.com/r-ryantm/nixpkgs/archive/c79d30f3449080589820420d5bfc2bcd8d01fe0e.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/97srb71ny58r0m3ripvkazb1igspwi9k-nss_wrapper-1.1.13
ls -la /nix/store/97srb71ny58r0m3ripvkazb1igspwi9k-nss_wrapper-1.1.13/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages failed to build:

python310Packages.django-scim2
python311Packages.django-scim2

3 packages built:

autofs5
nss_wrapper
sssd

Maintainer pings

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/nss_wrapper/versions.
meta.description for nss_wrapper is: A wrapper for the user, group and hosts NSS API
meta.homepage for nss_wrapper is: https://git.samba.org/?p=nss_wrapper.git;a=summary;
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.1.15 with grep in /nix/store/n7rkm0016p7y7g3vr3ch3y7jdsp2fnbc-nss_wrapper-1.1.15
found 1.1.15 in filename of file in /nix/store/n7rkm0016p7y7g3vr3ch3y7jdsp2fnbc-nss_wrapper-1.1.15

Rebuild report (if merged into master) (click to expand)

5 total rebuild path(s)

5 package rebuild(s)

First fifty rebuilds by attrpath
autofs5
nss_wrapper
python310Packages.django-scim2
python311Packages.django-scim2
sssd

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/n7rkm0016p7y7g3vr3ch3y7jdsp2fnbc-nss_wrapper-1.1.15 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A nss_wrapper https://github.com/r-ryantm/nixpkgs/archive/1735bedf66e2eb062dd793a1d72184d3f2f4f992.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/n7rkm0016p7y7g3vr3ch3y7jdsp2fnbc-nss_wrapper-1.1.15
ls -la /nix/store/n7rkm0016p7y7g3vr3ch3y7jdsp2fnbc-nss_wrapper-1.1.15/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

5 packages built:

autofs5
nss_wrapper
python310Packages.django-scim2
python311Packages.django-scim2
sssd

Maintainer pings


i18n null by default in the Flow component, which is not aligned with other components

The AvatarI18n is null by default, meaning the below code leads to a NullPointerException:
Avatar avatar = new Avatar();
avatar.getI18n().setAnonymous("new phone, who dis?");

This is different from how the Crud and LoginOverlay/LoginForm work, where the constructor creates a default i18n object if none is provided.

It's aligned with the set of the components that doesn't have default i18n. For example,
DatePicker datePicker = new DatePicker();
datePicker.getI18n().setCancel("cancel");

will lead to NPE as well.
Documentation also mentions that you are getting the i18n object previously set for this component
https://github.com/vaadin/vaadin-avatar-flow/blob/6f69cedf7945208bba4af9568db4f535b51bae5b/vaadin-avatar-flow/src/main/java/com/vaadin/flow/component/avatar/Avatar.java#L117

👍 the only i18n examples I could think of had a default set, but you're right, of course!
Would be nice as an enhancement, though.


Graphically moving path point displays a convoluted path

Steps to reproduce
Load arm26.osim. Select TRILat middle via point and drag.
Expected result
Path drawing updates contiguous with existing path points.
Actual result
Path point moves and is redrawn with respect to two phantom path points which remain stationary with respect to the other via points.

Environment and GUI version
OpenSim-43c1be65-2018-05-30

I see the same behavior, though if you wait a seconds, the muscle path is redrawn as you would expect.

Still present in Mac OpenSim 1e476f2-2018-06-13.
Discussed with @aymanhab and he felt that because this transitory (I am still dragging) that the kinks are not important since they disappear on release. I think it is goofy.

I think it is goofy.

Perhaps only the point (sphere) should be dragged and the path should update only once the mouse button has been released? That would also allow the user to see where they're moving the point in relation to the existing muscle path.

@tkuchida Since pathpoints can't exist in multiple places at the same time, and they need to exist in the old location for the old path to be drawn, I don't think this solution is sustainable without major rework.
We can try to update the visualization based on a timer (e.g. every .1 sec while dragging) but we need to prioritize relative to other issues.

While the transient behavior is likely to stay, there's a bug where graphically moving pathpoitns doesn't follow the full protocol of updating path and recreating system as done for other editing in Dialog. Fix in progress.

On Windows OpenSim 11d7a130-2018-08-03 I still don't think the behavior is correct.
Starting off like this:

Selecting points to edit seems to add a new path point and doesn't move the existing point! And unlike before it is not transitory - it persists. Undo does not work here either and undoes the hiding of muscles that were hidden rather than undo the current pathpoint edit.

This behavior is different on Windows vs Mac. On Mac, the path looks proper after one is done dragging.

Verfied fixed on windws

Verified.


Statistic - No of Teachers

Click 'Show School Data'
Displays table of schools
It would be useful to have a column: No of teachers
We could then very quickly identify all schools that have students registered but no teachers.

Fixed in 246364975fe78c6995283536ac9f820f58bdad3d


🐛透视表列头隐藏错误，当value多个时

🏷 Version

Package
Version

@antv/s2
1.28

@antv/s2-react
1.28

Sheet Type

[x] PivotSheet
[ ] TableSheet
[ ] GridAnalysisSheet
[ ] StrategySheet

🖋 Description
使用列头隐藏时，隐藏某一个value列，所有value列都会被隐藏，并且没有了按钮

⌨ Code Snapshots

🔗 Reproduce Link
https://codesandbox.io/s/suspicious-wood-4py200?file=/index.tsx

😊 Expected Behavior
正常隐藏对应列
💻 System information

any solutions?

@lijinke666 这个bug有修复预期不

已排期, 近期会修复

:tada: This issue has been resolved in version @antv/s2-v1.34.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version @antv/s2-v1.35.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version @antv/s2-v2.0.0-next.1 :tada:
The release is available on:

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version @antv/s2-react-v2.0.0-next.1 :tada:
The release is available on:

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version @antv/s2-vue-v2.0.0-next.1 :tada:
The release is available on:

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


train_model for fingerprint data

#Thanks Connor for publishing this project- it is a fascinating take on QSAR approaches-
I noticed that train_model in core.py assumes that all inputs are molecular tensors, so fingerprint-based models fail because they are single arrays.  For example, the command
python conv_qsar_fast/main/main_cv.py conv_qsar_fast/inputs/tox21_Morgan/tox21_ahr.cfg

fails with a error message along the lines of:
Error when checking model input: the list of Numpy arrays that you are passing to your model is not the size the model expected. Expected to see 1 arrays but instead got the following list of 3 arrays: [array([[1, 0, 1, 1, 1, 0, 0, 0, 1, 0, 0, 0, 0, 0, 0, 0, 1, 0, 0, 0, 1, 0,
        0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1, 0,
        0, 0, 0, 0, 0, 0, 0, 1, 0, 0, 0, 0, 0, 0, 0...

Hi @chepyle ,
When using a fingerprint representation, the use_fp keyword in architecture specification should be making its way to main.core.build_model() and main.data.get_data_full(), which will use a fixed FP input instead of the learned FP.  I see that the problem is coming from train_model(), because this feeds the three input arrays in (regardless of use_fp - this was a late change to the code after running the baseline models).
I've created a branch chepyle and modified main.core.train_model() to add two dummy inputs to the model. That way, when training or testing, these inputs will be accepted but ignored. Because these will be disconnected from the computational graph, you will have to pass on_unused_input='warn'  to Theano when running the script.
An alternate solution would be to change all of the calls to .fit or .predict to be inside conditionals that look at use_fp and pass only the first element of the inputs if using a fixed FP representation.
Let me know if this solves the issue; if so, I will merge it into the master branch.
-Connor

Thanks Connor, the model does run now for with the fingerprint data sets.  However, the disconnected graph causes problems with save_model similar to this:
https://github.com/fchollet/keras/issues/2790
Jake


Display issue on androit tablet

Checklist:

[x] I updated to the latest version available
[x] I cleared the cache of my browser

Release with the issue:
Last working release (if known):
Browser and Operating System:
Android companion app

Description of problem:

As per uploaded image, seems to be a rendering issue on the Android ha companion app. The issue is not present on the Chrome browser on the same Android tablet, or ios companion app.

Javascript errors shown in the web inspector (if applicable):

Additional information:

Is this going to be addressed?


JCK11 test bringup

It appears there are specific settings for JCK levels such as https://github.com/AdoptOpenJDK/openjdk-tests/blob/master/buildenv/jenkins/JenkinsfileBase#L52.
Not sure if there are other places.
Can we bring up JCK11 tests for coming JDK11?

The script should be updated to get JCK_VERSION from JAVA_VERSION, similar to https://github.com/AdoptOpenJDK/openjdk-tests/blob/ebef3ea96d7e2b937f463ef7d3e192f87d4bdb44/buildenv/jenkins/Jenkinsfile_personal#L129
We should only need to handle special case in the script, such as jck8b.
And JCK_VERSION should be a parameter, so that user can pass in their value.

Fixed by #507


New methods on ENV might be named too.. naturally.

When they were defined on the Environment namespace in the old implementation, these names seemed right, but now that they're on ENV, I'm concerned that some of them might not be obvious. And also, they aren't very searchable at all..
Proposal: rename all of the methods to ENV.load_<THING>, or something like that (perhaps another prefix?). Sadly, I already released 1.x, so if we dropped the prior methods we'd need to go to 2.0.. but I'm okay with that.

@rbellido @zmariscal @cdimartino, what do you think?


[Request] Discord bot integration to show current queue

The current bot has IP, Players, and uptime. It would be a great addition to be able to grab the current queue amount.

As txAdmin does not have a queue system integrated, I'm not sure how possible this would be. However, if someone created and PRed or suggested a txAdmin queue, there's a chance it could be added.

Now, as for a Discord bot integration with an existing queue resource, that is quite possible. I'm not shutting down your idea and I don't make the decisions, I'm offering a a suggestion of my own.

@notsiege-dev No worries, I'm trying to figure out how to implement it with Connect-Queue. There's a server convar to show queue in that resource, maybe there could be an option in txAdmin for that convar since it seems to be the most popular queue being used.

The issue is that txAdmin must maintain itself framework/resource agnostic.
If we were to make any exception, would be for some ESX features since there are basically 9 thousand servers using it - and it would still be completely optional.
If many queue resources decides "ohh, let me export this convar with standard name" then sure, we could get that data, but I just don't see it happening soon.


Preferences (brackets.json) don't support comments, although defaultPreferences do

Description
I'm trying to modify the preferences for Beautify plugin.
The defaultPreferences.json file contains comments:
// Beautifier-Language-Mapping, see https://github.com/brackets-beautify/brackets-beautify#configure-languages
	"bb.beautify.languages": {
		// Default: css
		"css": "css",

		// Default: html
		"ejs": "html",
...

When copy pasting the content of "bb.beautify.languages" into brackets.json in order to modify it, I get

This error is resolved when stripping the // comments from the json.
The default file and running file should either both not support comments, or preferably should both support comments.
Versions
Running Release 1.8 build 1.8.0-17108 (alf_localization_release_1.8 3af64fae4)
build timestamp: Wed Nov 02 2016 12:07:29 GMT+0000
on Windows.

Using http://hjson.org/ instead of plain JSON would be one option.


one test failure on s390x-unknown-linux-gnu (big endian)

I'm responsible for builds of ahash on Fedora Linux. With the latest bugfixes for LLVM and Rust, I was finally able to re-enable running the test suite during our builds, and I have now found a failure that only occurrs on s390x (IBM System Z), the only big-endian architecture we support:
failures:
---- operations::test::test_add_length stdout ----
thread 'operations::test::test_add_length' panicked at 'assertion failed: `(left == right)`
  left: `18446744073709551614`,
 right: `18446744073709551615`', src/operations.rs:380:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
failures:
    operations::test::test_add_length

All other tests pass on s390x-unknown-linux-gnu.
All tests succeed on the other architectures we support:

x86_64-unknown-linux-gnu
i686-unknown-linux-gnu
aarch64-unknown-linux-gnu
powerpc64le-unknown-linux-gnu
armv7-unknown-linux-gnueabihf

Tests were run with Rust 1.67.1 on Fedora Linux.

This is very confusing. Is it the case that this fails on s390x
    fn test_or() {
        assert_eq!(((u64::MAX as u128) << 64 | 50) >> 64, u64::MAX as u128);
    }

If so, is that a cpu bug?

Well, the bit pattern for 50u128 is different on little-endian and big-endian systems, by definition ... doing bitwise operations with hard-coded constants like this is bound to cause endianness related bugs.
I tried writing a small program for the test case above:
fn main() {
    println!("50u128 (LE): {:?}", 50u128.to_le_bytes());
    println!("50u128 (BE): {:?}", 50u128.to_be_bytes());
    assert_eq!(((u64::MAX as u128) << 64 | 50) >> 64, u64::MAX as u128);
}

Prints:
50u128 (LE): [50, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]
50u128 (BE): [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 50]

Though the assertion passes on both x86_64 and s390x, so I'm not sure what's going on.

I don't understand how the error you have above for operations::test::test_add_length could be generated if the assertion in the main you wrote passes.

Me neither ... I will investigate further. Thank you for looking into it.

Adding some debug prints as below, and running on both s390x and x86_64 shows the difference:
diff --git i/src/operations.rs w/src/operations.rs
index a420587..5646579 100644
--- i/src/operations.rs
+++ w/src/operations.rs
@@ -159,24 +159,14 @@ pub(crate) fn aesdec(value: u128, xor: u128) -> u128 {
 #[allow(unused)]
 #[inline(always)]
 pub(crate) fn add_in_length(enc: &mut u128, len: u64) {
-    #[cfg(all(target_arch = "x86_64", target_feature = "sse2", not(miri)))]
-    {
-        #[cfg(target_arch = "x86_64")]
-        use core::arch::x86_64::*;
-
-        unsafe {
-            let enc = enc as *mut u128;
-            let len = _mm_cvtsi64_si128(len as i64);
-            let data = _mm_loadu_si128(enc.cast());
-            let sum = _mm_add_epi64(data, len);
-            _mm_storeu_si128(enc.cast(), sum);
-        }
-    }
-    #[cfg(not(all(target_arch = "x86_64", target_feature = "sse2", not(miri))))]
     {
+        println!("{:#x}", enc);
         let mut t: [u64; 2] = enc.convert();
+        println!("{:#x} {:#x}", t[0], t[1]);
         t[0] = t[0].wrapping_add(len);
+        println!("{:#x} {:#x}", t[0], t[1]);
         *enc = t.convert();
+        println!("{:#x}", enc);
     }
 }

On x86_64
---- operations::test::test_add_length stdout ----
0xffffffffffffffff0000000000000032
0x32 0xffffffffffffffff
0x31 0xffffffffffffffff
0xffffffffffffffff0000000000000031

On s390x
---- operations::test::test_add_length stdout ----
0xffffffffffffffff0000000000000032
0xffffffffffffffff 0x32
0xfffffffffffffffe 0x32
0xfffffffffffffffe0000000000000032

As @decathorpe was supposing, it's a big-endian issue.

I can confirm that this passes the test on both endian types
diff --git i/src/operations.rs w/src/operations.rs
index a420587..460ce1c 100644
--- i/src/operations.rs
+++ w/src/operations.rs
@@ -175,7 +175,11 @@ pub(crate) fn add_in_length(enc: &mut u128, len: u64) {
     #[cfg(not(all(target_arch = "x86_64", target_feature = "sse2", not(miri))))]
     {
         let mut t: [u64; 2] = enc.convert();
-        t[0] = t[0].wrapping_add(len);
+        if cfg!(target_endian = "big") {
+            t[1] = t[1].wrapping_add(len);
+        } else {
+            t[0] = t[0].wrapping_add(len);
+        }
         *enc = t.convert();
     }
 }

Not sure if there are other (untested) big-endian issues still lurking elsewhere, but at least cross makes it easy to run tests for other architectures (https://github.com/ructions/cargo#cross-compilation).

@jamessan Ok good. That change is not actually necessary for the algorithm to be correct. We can make the test less sensitive by having it work with [u64; 2] and converting for the argument.

Based on your comments above I came up with the following patch, I tested it on both s390x and amd64 and the tests passed.
Does this look right to you?
bigendian.patch.txt

That worked, apparently. Thanks!


Cannot read property 'title' of undefined

I've got this error when trying to use getChannelInfo and getChannelVideos with some channels.
TypeError: Cannot read property 'title' of undefined
    at C:\Users\hazycora\Documents\GitHub\testing\node_modules\yt-channel-info\app\youtube-grabber.js:55:28
    at Array.map (<anonymous>)
    at Function.getChannelInfo (C:\Users\hazycora\Documents\GitHub\testing\node_modules\yt-channel-info\app\youtube-grabber.js:51:61)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)

From looking at youtube-grabber.js, I think YouTube's changed how continuation works, at least for some channels. I experimented with trying to fix it myself, but it seems my fix only moved the problem somewhere else.
It doesn't happen with all channels, but Ben Awad's causes it consistently.

I'm not sure if it should be new issue so i will post it there as it might be related.
ytch.getChannelInfo(channelId) returns empty array {} for some channels for example UC1DCedRgGHBdm81E1llLhOQ

My issue has been fixed in a recent update.


default admin password

Hi,
I used your docker-compose in advanced mode to bring up the taiga, everything worked out of the box for a test env I set up for it, however default taiga admin user password i.e 123123 did not work. I tried to look for it in all the files config settings there are no place I could find it. Can you state where in the code you set it and  how to find it please?
Thanks

remember to populate-db, and remember to change taiga-back/setting.py ALLOWED_HOSTS.
Like this to allow all:
ALLOWED_HOSTS = [
'*',
]

Hi @hsafe. Please, see Populate the database with initial data and line 50 in docker-compose.advanced.yml. Also, please don't modify ALLOWED_HOSTS as @KinGsNowGH suggested unless you know what you're doing.

@lubo Thanks, got it Cheers


Can't compile the code.

First of all thanks for such a good example and comparison of how memory allocator works.
Sadly, after I followed the instruction and compiled it in VS, compiler told me I can't use "void* address [m_nOperations]" since m_nOperations is not a constant. How did you get it work?

gzito's fork refractored for VS on Windows.

Hey! Sorry I did the project on Linux and later I added the instructions to generate the project files with CMake. I didn´t take into account differences in the compilers and system libraries. I'll fix it whenever I have some free time. But, as you said, Gzito seems to be doing a good job ;)

@mtrebi I can compile the code successfully now thanks to Gzito's version :P! Are you going to write Red Black tree version at some point?


Problems reading data from Binary store with intra-project dependency and capability resolution strategy

Building a shadowJar fails with:
Could not determine the dependencies of task ':p1:shadowJar'.
> Could not resolve all dependencies for configuration ':p1:runtimeClasspath'.
   > Problems reading data from Binary store in /private/var/folders/wc/1z_z159n7nxf31gbbnmldcmc0000gn/T/gradle871452152608880068.bin offset 203 exists? true

This seems to be an edge case that involves:

the order of an intra-project dependency
custom resolution strategy

More details in the repro project below.
Expected Behavior
Dependencies should resolve consistently
Current Behavior
See error above.
Context
I am trying to model some projects in our dependency graph that have multiple incompatible variants of generated code. I'd like to use a capability resolution strategy to resolve conflicts when they occur.
Steps to Reproduce
https://github.com/jdai8/gradle-bug-repro
Your Environment
Gradle nightly 6.8-20201005220043+0000, also tested with 6.6.1
Shadow plugin 6.0.0
Build scan URL:
https://scans.gradle.com/s/m4l36qd4jgzpk

Thank you so much for the reproducer, definitely helped!


Rendered models should be compiled as a blackbox test

Reason/Context
At the moment we do not directly test the correctness of the output. So when we receive PRs changing the rendering in any way we have no way of knowing whether the output can actually compile.
We already encountered this issue and having something in place to handle this logic would be awesome.
Description
I would suggest we implement a GitHub action per language we output to. For now, this means we would create a workflow for Java, Typescript, and JS.
Questions that need to be answered:

Should this workflow run for each PR?
Should we create one global input file which covers all possible values the output can be?
Say we scale to 10 languages, how much time would that affect the "wait time" for checks to complete?
What about different versions of languages, should that be tested?

Added an initial take on this but need some feedback if it makes sense, see https://github.com/asyncapi/generator-model-sdk/pull/173


Add last url that triggered the hint

It would be nice to have a "globe" icon at the end of the hint with the last occurrence that triggered the hint. That's would be specially helpful to new devs coming into existing projects and not super familiar with the content and its structure.

I’m not quite following. What exactly would the globe icon do or indicate?

Ah I just noticed the title indicates the “last url that triggered the hint”. Thanks for the suggestion, I’ll look into whether this is feasible to add.

That's nice, but I the reason I would rather have the last url that triggers the hint is so I could quickly see which page I can use to validate fixes.
My current DX flow is to:

See the hint
Look for the template and figure it out an route that trigger the hint (so I can validate the fix later)
Apply fix
"Clear all"
Visit the route that trigger the hint and see if that generates the hint again, or a different one.
Repeat

My dream DX scenario would looks like the image below, where the "globe" would be a link to the route that triggered the hint (for quick validation), and (or) the "refresh" button that would re-run the validation behind the scenes and validate / clear the specific hint hint.

Right now I constantly clearing the hints, refresh multiple FE routes, go back and refresh cp page to see what else needs fixing, again and again.
Maybe the way I've been using isn't the correct one, in which case feel free to enlighten me :grin:

That makes sense to me. With the changes coming in Craft 5, however, this is going to be a non-issue, as applying lazy eager-loading by adding .eagerly() to element queries is going to be a quick fix. I’ll revisit this when Craft 5 is out, but thanks for the suggestion!

That makes sense. As always, thanks for this awesome plugin!


We do not support sockets

We can already use monticelle with file-based repositories. Sockets would allow us to work with remote ones.

I have pushed some work into tim/sockets. It seems to work in my tests, but actually receiving data hangs when running the image with the translated product.

duplicates #53?

Status update: the current tim/sockets2 has an implementation that, hosted, can open and refresh a Monticello repository or a webpage. But after translation, there seems to be a bug with process switching so that it never reads the response...

This work was merged. There are still some transient issues, but we'll track these separately.


Sylvania Smart+A19 dimmable soft white bulb

{
zigbeeModel: ['A19 W 10 year'],
model: '74696',
vendor: 'Sylvania',
description: 'Smart+ A19 dimmable soft white bulb',
supports: generic.light_onoff_brightness().supports,
fromZigbee: generic.light_onoff_brightness().fromZigbee,
toZigbee: generic.light_onoff_brightness().toZigbee,
},

Thanks! Merged in https://github.com/Koenkk/zigbee-shepherd-converters/commit/6ba6dcdacd98eb9b07d0a09ee6dd3b2e25bec345


DocGenerator should respect

The documentation generator is skipping <inheritdoc /> declarations and failing to omit documentation - problem exists in XmlDocsVisitor.

Merging with #3559


Acm 1417

Signed-off-by: Joshua Packer<EMAIL_ADDRESS>
Description of the change(s):

hard code the version to 4.10.15 as the default OCP to deploy

Why do we need this PR:

Otherwise the default is 4.11 which does not deploy.

In which case you need to deploy with override: INFRA-ONLY, then update the release before removing override: INRA-ONLY

Issue reference:

acm-1417, full fix should be in acm-1420

Test API/Unit - Success
?       github.com/stolostron/hypershift-deployment-controller/api/v1alpha1     [no test files]
?       github.com/stolostron/hypershift-deployment-controller/pkg      [no test files]
?       github.com/stolostron/hypershift-deployment-controller/pkg/constant     [no test files]
ok      github.com/stolostron/hypershift-deployment-controller/pkg/controllers  0.131s  coverage: 77.9% of statements
ok      github.com/stolostron/hypershift-deployment-controller/pkg/controllers/autoimport       0.023s  coverage: 61.5% of statements
?       github.com/stolostron/hypershift-deployment-controller/pkg/helper       [no test files]
ok      github.com/stolostron/hypershift-deployment-controller/test/integration 20.991s coverage: [no statements]

/hold


Host a landing page on toonin.ml and the app on app.toonin.ml

I got feedback on play.pioneer.app that it would be helpful to have a landing page for Toonin that gives a description of the app.

We'll link to the Grey Software website instead.


Ensure render function does not have undefined object

don't all components need  const $ = render('component', {}) change made?


🐛 Bug Report: getSession() crash after unwrap null value

👟 Reproduction steps
call getSessions() or getSession(sessionsId:)
👍 Expected behavior
Get Session object
👎 Actual Behavior
Could not cast value of type 'NSNull' (0x7fa3b980b430) to 'NSString' (0x7fa3c8036140).

🎲 Appwrite version
Different version (specify in environment)
💻 Operating system
MacOS
🧱 Your Environment
Appwrite 0.13.x
Xcode 13.2.1 (13C100)
iOS 15
👀 Have you spent some time to check if this issue has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

This should no longer be an issue with Appwrite 0.14+ 👍


Automatize push to docker.io

Automatize pushes to PyPI can be risky as files cannot be  packages cannot be substituted.


BigTable: Cell.from_pb() performance improvement

Looking at the performance graph for reading a large number (1000) of rows, each row having 10 cells in one column family, the following class method on Cell takes more time percentage-wise (~10%) than expected:
    @classmethod
    def from_pb(cls, cell_pb):
        """Create a new cell from a Cell protobuf.

        :type cell_pb: :class:`._generated.data_pb2.Cell`
        :param cell_pb: The protobuf to convert.

        :rtype: :class:`Cell`
        :returns: The cell corresponding to the protobuf.
        """
        timestamp = _datetime_from_microseconds(cell_pb.timestamp_micros)
        if cell_pb.labels:
            return cls(cell_pb.value, timestamp, labels=cell_pb.labels)
        else:
            return cls(cell_pb.value, timestamp)

It turns out that _datetime_from_microseconds is relatively expensive:
    return _EPOCH + datetime.timedelta(microseconds=value)

If you trace down to look at the code for _EPOCH and datetime.timedelta you will see the amount of work done to get a proper datetime.
It is suggested that Cell store the microseconds from the Cell protobuf and a property annotation be used to get the timestamp as a datetime, when requested.   This makes sense since it moves the performance penalty to only the code which needs to access this timestamp, which may actually be a small minority of code.  The property annotation would implement the datetime conversion, using the saved cell_pb.timestamp_micros:
    @property
    def timestamp(self):
        return _EPOCH + datetime.timedelta(self.timestamp_micros)

As an additional consideration, the use of labels in the constructor for Cell should be evaluated to determine if this feature is in use consistently across languages.
See approved pull request #4745.

Via #4745.


Fully Customizable Button

I would kinda consider this an issue, because I would kinda say it's the reason I don't use mod menu. It would be cool if you could totally customize the mods button, so that it could replace "Give Feedback" AND "Report Bugs" (in game) in the menu but then also choose something else for the startup menu without changing the in game menu (when you press esc) when you have "adjacent" selected it replaces "Report Bugs" with the mods button so I think there should also be an option to replace "Give Feedback" and "Report Bugs" to make one big button. And also have an option remove it on either menu (startup menu or in game menu) too, as well as another option to replace the "Quit Game" button. Sorry if this was too long I never really find the right words to say lol. But thanks and have a good day.
(Also I think a /mods command with a toggle for it would be cool just to list the mods in the chat)

Seems like the main thing you're suggesting here is decoupling the mods button's pause menu position from its title screen position (which is what I came here to suggest). For the pause menu postions, I'd suggest:

Replace Bugs/Feedback (behavior you suggested)
Below Bugs/Feedback (current behavior for Below Realms or Replace Realms)
Replace Bugs only (current behavior for Adjacent)
Icon
Disabled (don't show mods button in-game, only on main menu like in Forge)

The reason I'm suggesting this myself is that I set the mods button to replace realms in my modpack, which causes it to move below bugs/feedback in the pause menu, but I'd like it to remain like in adjacent mode where it replaces report bugs. Tying the pause menu position to the title screen position doesn't make much sense considering that the rest of the options presented in these two menus are completely different from each other.

This has been mostly implemented in 1.19.4, it has a separate option but there's no Replace Bugs and Feedback option at the moment.


Add support for adding otherData

Adding support for adding some additional data for analysis purposes. My use case - I want lage to output the targetGraph too in the profile json, so that we can analyze the build graph and figure out the critical path which impacts the build duration the most.
otherData is supported by trace event format described here https://docs.google.com/document/d/1CvAClvFfyA5R-PhYUmn5OOQtYMH4h6I0nSsKchNAySU/preview#heading=h.uxpopqvbjezh. Tested the second profile format (with otherData) in edge and it seems to be working fine.

Would you mind adding some tests & a little paragraph about how this should be used in the readme.md ?

@kenotron Added tests and updated readme.md


Underscores in function names mistaken for formatting in docgen

For example, the documentation for AppDirs.user_data_dir shows as "user data dir" (https://www.main.actor/packages/appdirs/0.1.0/appdirs/appdirs)

This works fine with stdlib. So mkdocs handles this.
Should we consider this to be a bug in pony documentation generation (that it doesn't escape any markdown special characters?) or in main.actor?
I mostly want to say this is a main.actor issue Technically the markdown should be set_notify. not set_notify. But the former isn't exactly readable as plain text which is one of the key goals of markdown.
@EpicEric @Theodus input?

This is definitely a docgen problem. There are already parts of the document being properly escaped, such as generic types. This part, for example, shows both:
### from_iso_array
[[Source]](src/builtin/string.md#L71)

Create a string from an array, reusing the underlying data pointer

[... removed codeblock in clodeblock because it breaks this example ...]

#### Parameters

*   data: [Array](builtin-Array.md)\[[U8](builtin-U8.md) val\] iso

#### Returns

* [String](builtin-String.md) iso^

The only reason this doesn't break for https://stdlib.ponylang.io is because MkDocs tries to be "smart" and doesn't treat multiple underlines in the same word as emphasis.

CommonMark (which is the closest thing we have to a Markdown spec) says that "Emphasis with _ is not allowed inside words" (spec | example). Which would mean that MkDocs is correct here, and main.actor isn't.
Personally, I'd err on the side of compatibility and escape these characters, since we cannot guarantee that users' Markdown implementations will follow CommonMark. But I have no strong preference about fixing it only for main.actor and keeping docgen as-is.

@EpicEric I'm of the opinion that in the next documentation generation system (which will be coming eventually), we shouldn't be generating markdown documents, which could render this somewhat moot.

If we "fixed" main.actor, it would fix all the documentation on main.actor. If we fix docgen, then it will fix all documentation going forward.

@EpicEric main.actor is using remark which should be using commonmark. Which makes me think that we should be addressing on the main.actor side for now. It would appear to be an issue there.

@ChristopherBiscardi main.actor is using commonmark via remark, so this shouldn't, in theory, be happening, correct?

@EpicEric main.actor is using remark which should be using commonmark. Which makes me think that we should be addressing on the main.actor side for now. It would appear to be an issue there.

Okay, moving the issue back.


Can I check my local repository as a lint?

I'd like to use this library to prevent incorrectly publishing packages,

do what it does today, but read from a folder
assume all files to be published are already built
these should give a reasonable representation of what the "published version" will look like once npm pack is ran

checks package.json#files
checks .npmignore, if it exists, but package.json#files is better

I’m not going to reimplement npm pack, but I’m open to a mode that runs npm pack for you, with a (skippable with -y) confirmation prompt that says npm pack is about to run, and deletes the tarball after the analysis. The reason I didn’t want this by default is the potential of prepack or postpack scripts that would run without it being obvious to the user that that was going to happen. Several people have suggested this in a short period of time though, so I’m happy to include it. I’d use it myself, honestly. I think this is what happens when you run attw with no arguments or point it to a directory containing a package.json file (attw .).


De-duplicate methods in .mlem model metafile

If we TAL at metafile, we can see the duplication of methods as predict + sklearn_predict, predict_proba + sklearn_predict_proba. The reason to introduce them was to give a common interface to models from different frameworks. E.g. sklearn's predict and someotherframework's get_prediction would have the same endpoint once deployed.
I think we shouldn't duplicate them here. It should be configurable on the server level. This will make future changes depend not on the time when you saved the model, but on the MLEM version.
artifacts:
  data:
    hash: 5a38e5d68b9b9e69e9e894bcc9b8a601
    size: 163651
    uri: rf
model_type:
  methods:
    predict:
      args:
        - name: data
          type_:
            columns:
              - sepal length (cm)
              - sepal width (cm)
              - petal length (cm)
              - petal width (cm)
            dtypes:
              - float64
              - float64
              - float64
              - float64
            index_cols: []
            type: dataframe
      name: predict
      returns:
        dtype: int64
        shape:
          - null
        type: ndarray
    predict_proba:
      args:
        - name: data
          type_:
            columns:
              - sepal length (cm)
              - sepal width (cm)
              - petal length (cm)
              - petal width (cm)
            dtypes:
              - float64
              - float64
              - float64
              - float64
            index_cols: []
            type: dataframe
      name: predict_proba
      returns:
        dtype: float64
        shape:
          - null
          - 3
        type: ndarray
    sklearn_predict:
      args:
        - name: X
          type_:
            columns:
              - sepal length (cm)
              - sepal width (cm)
              - petal length (cm)
              - petal width (cm)
            dtypes:
              - float64
              - float64
              - float64
              - float64
            index_cols: []
            type: dataframe
      name: predict
      returns:
        dtype: int64
        shape:
          - null
        type: ndarray
    sklearn_predict_proba:
      args:
        - name: X
          type_:
            columns:
              - sepal length (cm)
              - sepal width (cm)
              - petal length (cm)
              - petal width (cm)
            dtypes:
              - float64
              - float64
              - float64
              - float64
            index_cols: []
            type: dataframe
      name: predict_proba
      returns:
        dtype: float64
        shape:
          - null
          - 3
        type: ndarray
  type: sklearn
object_type: model
requirements:
  - module: sklearn
    version: 1.1.2
  - module: numpy
    version: 1.22.4
  - module: pandas
    version: 1.5.0

Some thoughts:
Our common interface methods are always one of the existing methods that 1) renamed to predict 2) has only one required argument 3) renamed this arg to data
So probably we can do this dynamically later.
Also current approach does not solve cases when arg data type is changed (you will get serialization error on request)
We can make signature a part of server configuration. If it's not set, just use what model has. If it's set, either require model to have exact same signature or try to automatically conform model signature to server signature (find methods with same arg data types and rename/proxy them).
Consequently this should also be a builder/deployment configuration option


Print MarkersExtractor version number in Log File

Could we print and state the current version of MarkersExtractor in the Log file before starting the operation?

Could do, yes.
You can also do it yourself by piping the output of markers-extractor-cli -v to the log first.
While on this point, it could be a good idea to include the version in the result json file.

This feature could be particularly useful for our Marker Data app for debugging.
If Marker Data have several release down the line, when users encounters a bug or issue, it might be easier to trace?
The user might not be on the latest version of Marker Data.

That sounds more like you want to log Marker Data version. It's more likely that the same version of MarkersExtractor would be used with more than one release of Marker Data. So logging MarkersExtractor's version alone would only help for debugging extraction. It wouldn't really help for debugging Marker Data.

Thank you!

Version output to both log and result file is done. Will be in 0.2.9.

Will close this for now.

When I try and use -v, I get an error.
Error: Unknown option '-v'

The version is shown in the terminal but it is not printed in the log file.
Also are we able to print exactly like in the terminal into the log file?
MarkersExtractor 0.3.0
Using Notion export profile.
Parsing XML from "XYZ"
Note that this may take several seconds for very large projects. Please wait...
Extracting Markers...
5%
10%
15%
Project start timecode: 00:00:00:00 @ 25 fps.
Found project media file: "XYZ".
Generating PNG thumbnail images into "XYZ".
Generating metadata file(s) into "XYZ".
20%
Exporting marker icons...
24%
Generating PNG images for markers...
.
.
.

When I try and use -v, I get an error.

Sorry, I thought the argument parser had both -v and --version but now that I check, it's just --version.

The version is shown in the terminal but it is not printed in the log file.

I'm seeing it print to the log file (specified with --log CLI option). Maybe it wasn't working a while back, but it is now.
2024-01-03 23:42:50 info: MarkersExtractor 0.3.1
2024-01-03 23:42:50 info: Using CSV export profile.
...

I have just tested this 0.3.2
But for some reason, the full terminal is not printed into the log file.
I am using --log-level debug --log $ERROR_LOG.

Progress reporting to the log file is being called from a background thread I believe, which may be corrupting the log output.

It works fine when --no-progress is present.
Progress reporting to the log file is being called from a background thread I believe, which may be corrupting the log output.

Will using --no-progress affect's Marker Data's ability in reading MarkersExtractor progress percentage?

A simple solution may be to just omit progress percentage output from the log file. It's not really useful and adds extra noise to the log.

Let's omit progress reporting in the log file in the next build? We can also remove --no-progress flag.

Progress in console, progress in log file, and progress reporting in GUI are 3 different unrelated concepts.
Progress will remain in console but be omitted from log file. GUI progress has nothing to do with this.

I discovered why the log was getting corrupted. Mistakenly, the log file was being opened for writing twice. That's now resolved.

Console will continue to show progress (or hide it if --no-progress is passed) which is the same as before.
Now, progress will always be omitted from the log file.

Console output:
MarkersExtractor 0.3.2
Using CSV export profile.
Parsing XML from "/Users/stef/Dropbox/_coding/MarkersExtractor/GitHub Issues/Issue 37/SAM-BRS-TEST/BRS_LOCKED6_20210521 - 01 Opening Scene.fcpxmld/Info.fcpxml"
Note that this may take several seconds for very large projects. Please wait...
Extracting Markers...
5%
10%
15%
Project start timecode: 00:59:50:00.00 @ 25 fps.
Bypassing media file.
Generating metadata file(s) into "/Users/stef/Desktop/me-cli-output/BRS_LOCKED6_20210521 - 01 Opening Scene 2024-01-06 06-47-44 [CSV]".
20%
Exporting marker icons...
24%
96%
Creating result file "/Users/stef/Desktop/me-cli-output/result.json".
100%
Done

Log file output:
2024-01-06 18:47:42 info: MarkersExtractor 0.3.2
2024-01-06 18:47:42 info: Using CSV export profile.
2024-01-06 18:47:42 info: Parsing XML from "/Users/stef/Dropbox/_coding/MarkersExtractor/GitHub Issues/Issue 37/SAM-BRS-TEST/BRS_LOCKED6_20210521 - 01 Opening Scene.fcpxmld/Info.fcpxml"
2024-01-06 18:47:42 info: Note that this may take several seconds for very large projects. Please wait...
2024-01-06 18:47:43 info: Extracting Markers...
2024-01-06 18:47:44 info: Project start timecode: 00:59:50:00.00 @ 25 fps.
2024-01-06 18:47:44 info: Bypassing media file.
2024-01-06 18:47:44 info: Generating metadata file(s) into "/Users/stef/Desktop/me-cli-output/BRS_LOCKED6_20210521 - 01 Opening Scene 2024-01-06 06-47-44 [CSV]".
2024-01-06 18:47:44 info: Exporting marker icons...
2024-01-06 18:47:44 info: Creating result file "/Users/stef/Desktop/me-cli-output/result.json".
2024-01-06 18:47:44 info: Done

Thank you!


TestPushPop fails with future Go 1.12

When running go test with the future Go 1.12 release, TestPushPop fails:
> go test
--- FAIL: TestPushPop (0.00s)
    context_test.go:26: expected hash: e0d6724eb72033577811a55f7a642f6a != actual hash: 31e908ee1c2ea180da98fd5681a89d05
FAIL
exit status 1
FAIL	github.com/fogleman/gg	0.042s

This appears to be due to https://golang.org/cl/153059, which changes the exact bit results returned by some trigonometric math functions.  TestPushPop appears to be a change-detector test (https://testing.googleblog.com/2015/01/testing-on-toilet-change-detector-tests.html) in that it basically tests that some floating point operations return bit-for-bit identical results.

Updated test for 1.12.


Adds ReadItunes module

Adds ReadItunes module using iTunesPodcastFinder

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@daveaglick ready for review!

Very cool! I’ll try to get this reviewed and merged before the next release (which I’m hoping to get out the door this weekend)


linter_testing

What type of PR is this?
Add one of the following kinds:

tests

What this PR does / why we need it:
PR to test issue https://github.com/camaraproject/CarrierBillingCheckOut/issues/126
Which issue(s) this PR fixes:
Testing for Issue https://github.com/camaraproject/CarrierBillingCheckOut/issues/126

NOTE: DO NOT MERGE

Will generate a new PR with linter configuration into WG repo (during next weeks)


Make it clearer where to get the URL

Running the example from the README on Repl.it results in a key error
KeyError: 'REPLIT_DB_URL'

Where does one input the REPLIT_DB_URL when instantiating the client and where can one get this URL? (The repl.it docs say to press on the floppy disk icon but it's not obvious where to find this either)

Sorry about that rn, 2 things:

The example rn won't work (check editors note)
The url is only there for explorers, and some are experiencing that it's disappearing, ill try to make it work better and have a better error

Note: this is not the official client, I am currently helping with that one so this patch may take a bit longer

thanks for the response! I turned on explorer and the official client is working great now. Looking forward to using it.

glad you like it you can goto https://github.com/replit/replit-py for the whole module (its code is in src/replit/database)

oh great - I'm writing some tutorials for Amjad on using Repl.it and it would be great to chat about where you're going with this module so I can include one. Is there somewhere I can contact you directly (discord, slack, email etc?).
Specifically I'm a bit confused about how get() works / will work and would be interested to know what kind of querying and searching functionality you're adding if any.

Ok just goto that one and create an issue (on the official one) or contact scoder on discord, his tag is: Scoder12#1704, you can also dm me (but I'm just helping rn) my tag is: CoderMan51#8112


Document new issues seen with Storage hosts

How is it looking now @mnasiadka ?

Tox is moaning:
/home/runner/work/stackhpc-kayobe-config/stackhpc-kayobe-config/doc/source/operations/rocky-linux-9.rst:489: WARNING: Inline literal start-string without end-string.
/home/runner/work/stackhpc-kayobe-config/stackhpc-kayobe-config/doc/source/operations/rocky-linux-9.rst:489: WARNING: Inline literal start-string without end-string.

Tox is happy now :)


Fixes #92 Update README.md

Remove --dev flag (deprecated) in composer install command inside "Contribute" section.

Yes you're right. Thank's :)


Move sleigh to separate repository

I'm interested in incorporating the sleigh decompiler in a personal project, and it would be nice to have it in its own repo, so I don't need to clone all of ghidra.
I also think it would get more attention by the community if it were put in a separate repo to emphasize its use outside of ghidra.
It would also help because projects wanting to use sleigh as a dependency can git pull from a repo rather than a subfolder of another repo (not even sure thats possible).

Duplicate of #473


LWL proxy update

@lindsayking I think we have extraneous service ref's in the proxy. Let's update before we tag it .

[ ] State
[ ] Local

http://services.arcgis.com/P3ePLMYs2RVChkJx/arcgis/  = ? - LT no dependency
http://services6.arcgis.com/Pu6Fai10JE2L2xUd/arcgis/ = New try it org - LT uses
http://services.arcgis.com/b6gLrKHqgkQb393u/arcgis/" = LG dev ORG - LT no dependency
http://services.arcgis.com/doC3DvW5p9jGtDST/arcgis/ = ? -
http://arcgis-gov-1244222493.us-west-2.elb.amazonaws.com/arcgis/rest/services = State TIL -  LT no dependency
@lindsayking can you look at this ?

@LindsayThomas
http://services.arcgis.com/P3ePLMYs2RVChkJx/arcgis/ = ? - LT no dependency, LK no State dependency
http://services6.arcgis.com/Pu6Fai10JE2L2xUd/arcgis/ = New try it org - LT uses, LK uses
http://services.arcgis.com/b6gLrKHqgkQb393u/arcgis/" = LG dev ORG - LT no dependency, LK no dependency
http://services.arcgis.com/doC3DvW5p9jGtDST/arcgis/ = Former state TIL webmaps use this, new TIL webmaps do not
http://arcgis-gov-1244222493.us-west-2.elb.amazonaws.com/arcgis/rest/services = State TIL - LT no dependency, no State dependency for LWL TIL

@lindsayking can we go ahead and remove?

@lindsaythomas Yes.

@LindsayThomas  Extraneous serverUrls have been removed.


How to apply source map to paths reported by "ERROR in" or "WARNING in" messages?

Hi.
Is it possible to tell webpack to translate references in error/warning messages using source maps of the input files?
E.g. source-map-loader allows to bundle the pre-built JS content from dist/ (imagine we have tsc which builds dist/ content from src/), it works fine. Then, dist/ folder looks like this:
$ ls dist/
Some.js  # e.g. generated from src/Some.myesotericlanguage
Some.js.map

And, say, in transpiled Some.js I have a dummy require("aaa") where aaa doesn't exist. Then, when bundling Some.js, webpack generates the following error message to console:
ERROR in ../dist/Some.js
Module not found: Error: Can't resolve 'aaa' in '../dist'

I.e. it doesn't respect source map file for dist/Some.js path and just prints it as is (as well as examples from the code if there is some JS syntax error after transpilation; source map is not respected there too). Although it exists.

Currently this is not possible

Could you please provide some code pointers/hints on how to make it possible? Like, is there some hooks on these error/warning messages? (The closest I could google for is loader's emitError/emitWarning, but it may be irrelevant.)
Because from theoretical point of view, it's reading of .map file corresponding to the "Error in xyz" path and then translating location (source location would do 90% of the value; examples from the code which webpack shows in error message are less valuable.)
Also, at which abstraction level can it be implemented? It's not a loader and not a plugin, right?

You can write a plugin that hooks into Compilation.hooks.succeedModule and update the module.errors/warnings.

Answer above


clickhouse: <IP_ADDRESS> -> <IP_ADDRESS>

Description of changes
New LTS version
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

This looks ready, ofborg is passing.
Where you lookong for something else to take this out of draft ?

No, the build is failing. I'm currently looking into it.

@yu-re-ka Is there a reason we're sticking with LTS? The switch to LTS in #123488 didn't seem to come with any real reasoning, and ClickHouse is evolving pretty quickly / worth keeping up to date on.
If anyone has a need for LTS specifically, I'd rather see that as an additional attribute.

In my view the benefit from sticking to an LTS version is that we can provide security updates on a NixOS release channel without breaking applications.
But in the end it's probably going to require multiple attributes pointing to multiple versions, and the security updates thing only really works if we always have the latest LTS version right before our branchoff, which in this case we don't (it doesn't build).


Sound problem with <IP_ADDRESS>

Hi Anthony,
Yesterday I have updated last OnlyM version and i have a problem with sound media file.
When i play a song (or an other audio file), first second is repeat once time.
Good tracking ;)
Thank's for your job !

@AlexandreTortevois thanks for reporting this. I am having some problems with MP3 playback. Am investigating.

@AlexandreTortevois I haven't been able to reproduce this issue but have made some changes to MP3 playback in the latest release. I'll mark as fixed but please reopen if needed.


Air temperature doesn't look right in GFS reference forecast

I was looking at air temperature forecasts from GFS for Dec 23-24 and noticed that the forecasted values were surprisingly high. Opening the NetCDF file in NOAA's WCT, I'm seeing different values that are much lower (and more believable). I'm wondering if SFA is processing air temperature incorrectly.
As an example, I'm using the GFS forecast initialized at 2022-12-22 06:00Z and a valid time of 2022-12-24 00:00Z, for a location near Atlanta, GA (33.75, -84.30). I used the workshop reference_forecasts.ipynb as a starting point. Here's the NetCDF file zipped: sfa_test.zip.
Opening the .nc file in NOAA WCT, I get -8 deg C (265.1 K). But running through sfa, I get about -2 C. For reference, the actual temperature ended up being about -11.5 C (https://www.wunderground.com/history/daily/us/ga/atlanta/KATL/date/2022-12-24).
I tried a few other locations and got similar results. Maybe I'm doing something wrong, but it seems like the forecasted temperature never gets low enough, so something seems off.
Viewing the file in NOAA's WCT:

SFA results (code is included below):

import datetime
from functools import partial
from pathlib import Path

import numpy as np
import pandas as pd

from bokeh.core.properties import value
from bokeh.io import output_notebook
from bokeh.layouts import gridplot
from bokeh.models import ColumnDataSource
from bokeh.plotting import figure, show
from bokeh import palettes
from bokeh.palettes import Category10_10 as PALETTE
TOOLS = "pan,box_zoom,xwheel_zoom,reset,save"
output_notebook()

from solarforecastarbiter import datamodel
from solarforecastarbiter.io import nwp
from solarforecastarbiter.io.api import APISession, request_cli_access_token

# location of netcdf files
base_path = 'C:/Users/willh/Downloads/sfa_test' # path to folder used for "solararbiter fetchnwp"
# define file loading function that knows where to find the files
load_forecast = partial(nwp.load_forecast, base_path=base_path)

def plot_nwp(ghi, dni, dhi, air_temperature, wind_speed, ac_power):
    """Make a plot of the variables from processed NWP forecasts"""
    # data prep
    if ac_power is None:
        ac_power = pd.Series(np.nan, index=ghi.index)
    data = dict(zip(('GHI', 'DNI', 'DHI', 'Air temperature', 'Wind speed', 'AC power', 'index'),
                    (ghi, dni, dhi, air_temperature, wind_speed, ac_power, ghi.index)))
    source = ColumnDataSource(data)

    figs = []
    fig_kwargs = dict(tools=TOOLS, x_axis_type="datetime", plot_height=200)
    palette = iter(PALETTE)

    # irradiance figure
    fig1 = figure(**fig_kwargs)
    for name in ('GHI', 'DNI', 'DHI'):
        fig1.line(x='index', y=name, source=source, legend_label=name, color=next(palette), line_width=2)
    fig1.yaxis.axis_label = "Irradiance (W/m^2)"
    fig1.legend.location = "top_left"
    figs.append(fig1)

    # air temperature figure
    fig_kwargs['x_range'] = fig1.x_range  # link x-zoom
    fig2 = figure(**fig_kwargs)
    fig2.line(x='index', y='Air temperature', source=source, legend_label="Air temperature", color=next(palette), line_width=2)
    fig2.yaxis.axis_label = "Air temperature (C)"
    fig2.legend.location = "top_left"
    figs.append(fig2)

    # wind speed figure
    fig3 = figure(**fig_kwargs)
    fig3.line(x='index', y='Wind speed', source=source, legend_label="Wind speed", color=next(palette), line_width=2)
    fig3.yaxis.axis_label = "Wind speed (m/s)"
    fig3.legend.location = "top_left"
    figs.append(fig3)

    # ac power figure
    if not ac_power.dropna().empty:
        fig4 = figure(**fig_kwargs)
        fig4.line(x='index', y='AC power', source=source, legend_label="AC power", color=next(palette), line_width=2)
        fig4.yaxis.axis_label = "AC power (MW)"
        fig4.legend.location = "top_left"
        figs.append(fig4)

    figs[-1].xaxis.axis_label = 'Time (UTC)'

    grid = gridplot(figs, ncols=1, plot_width=800)
    return grid

# define coordinates (Atlanta, GA)
latitide = 33.75
longitude = -84.30
elevation = 225

# define a Site object
site = datamodel.Site(
    name='Atlanta, GA',
    latitude=latitude,
    longitude=longitude,
    elevation=elevation,
    timezone='America/New York'
)
# Complete GFS is available 5 hours after its initialization time
run_time = pd.Timestamp('20221222T1100Z')
issue_time = pd.Timestamp('20221222T0700Z')

# define a Forecast object
forecast = datamodel.Forecast(
    name='GFS 7day Weather Fcast',
    site=site,
    variable='ghi',
    interval_label='instant',
    interval_value_type='interval_mean',
    interval_length='1h',
    issue_time_of_day=datetime.time(hour=7),
    run_length=pd.Timedelta('24h')*7,
    lead_time_to_start=pd.Timedelta('0h')
)

# select the model
model = models.gfs_quarter_deg_to_hourly_mean

# tell the model where to find the NWP data
model_wrapped = partial(model, load_forecast=load_forecast)

# load and process the NWP data. ac_power is None because site is not a power plant.
ghi, dni, dhi, air_temperature, wind_speed, ac_power = main.run_nwp(forecast, model_wrapped, run_time, issue_time)

grid = plot_nwp(ghi, dni, dhi, air_temperature, wind_speed, ac_power)
show(grid)

Never mind. A colleague reviewed my code and found a typo in latitide = 33.75, so I was accidentally running with an earlier value I used for latitude that was still in memory (and very far from Atlanta...).
The output after fixing my mistake looks correct:


App Crashed

I am getting crash when I try to view Image in pager.
xcode 11.5
Simulator iPhone 11 Pro
iOS 13.5
Filename: SizeViewModifier.swift
line 23

My code where I am using it.
`
import CoreData
import SwiftUI
import SwiftUIPager
struct BoardPhotoView: View {
@Environment(\.presentationMode) var presentationMode
@FetchRequest(entity: Pedalboard.entity(), sortDescriptors: [
    NSSortDescriptor(keyPath: \Pedalboard.name, ascending: true),
    NSSortDescriptor(keyPath: \Pedalboard.imageD, ascending: true)
    ]
) var pedalboards: FetchedResults<Pedalboard>

@State var image : Data = .init(count: 0)

let pedalboard: Pedalboard
let imageArray:[Data]
// Magnification vars
@State private var scale: CGFloat = 1
@State var pageIndex = 0
// drag vars
@State private var position = CGSize.zero
@GestureState private var dragOffset = CGSize.zero

var body: some View {

    return
        ZStack {
            Color.newPrimaryColor2
            GeometryReader { proxy in
                VStack(spacing: 10) {
                    Pager(page: self.$pageIndex,
                          data: [0],
                          id: \.self) { page in
                            self.pageView(self.imageArray[page], index:page)
                    }
                    .disableDragging()
                    .itemSpacing(10)
                    //.padding(20)
                    .onPageChanged({ page in
                        withAnimation {
                            self.scale = 1.0
                            self.pageIndex = page
                        }
                    })
                    .frame(width: proxy.size.width,
                           height: proxy.size.height)
                    .background(Color.newPrimaryColor2.opacity(0.3))

                    Spacer()

                  /*  HStack {
                        Spacer()
                        Button(action: {
                            withAnimation {
                                self.scale = 1.0
                                self.pageIndex = max(0, self.pageIndex - 1)
                            }
                        }, label: {
                            HStack(spacing: 10) {
                                Image(systemName: "backward.fill")
                                    .padding()
                                Text("Previous")
                            }
                        }).disabled(self.pageIndex <= 0)
                        Spacer()
                        Button(action: {
                            withAnimation {
                                self.scale = 1.0
                                self.position = .zero
                                self.pageIndex = min(self.imageArray.count - 1, self.pageIndex + 1)
                            }
                        }, label: {
                            HStack(spacing: 10) {
                                Text("Next")
                                Image(systemName: "forward.fill")
                                    .padding()
                            }
                        }).disabled(self.pageIndex >= self.imageArray.count - 1)
                        Spacer()
                    }*/
                    Spacer()
                }
            }

    }
}

func pageView(_ imagePic: Data, index: Int) -> some View {
    GeometryReader {reader in
        //Image("pizza1delivery")
        Image(uiImage: UIImage(data: imagePic)!)
        .resizable()
        .scaledToFit()
        .cornerRadius(5)
        .scaleEffect(index == self.pageIndex ? self.scale : 1)
        .shadow(radius: 5)

        .animation(.default)
        .offset(index == self.pageIndex ? CGSize(width: self.position.width + self.dragOffset.width, height: self.position.height + self.dragOffset.height) : .zero)
        .gesture(index != self.pageIndex ? nil : self.scale <= 1 ? nil : DragGesture()
            .updating(self.$dragOffset, body: { (value, state, transaction) in
            state = value.translation
        })
        .onEnded({ (value) in
            self.position.height += value.translation.height
            self.position.width += value.translation.width
        })
        )

        .gesture(index != self.pageIndex ? nil :MagnificationGesture()
            .onChanged({ (value) in
                print(index)
                self.scale = value.magnitude
            })
            .onEnded({ (value) in
                self.position = .zero
                self.scale = value.magnitude
            })
        )
    }
}
}
struct BoardPhotoView_Previews: PreviewProvider {
static let moc = NSManagedObjectContext(concurrencyType: .mainQueueConcurrencyType)
static var previews: some View {
    let pedalboard = Pedalboard(context: moc)
    // pedalboard.imageD = "sampleBoard"
      return NavigationView {
        BoardPhotoView(pedalboard: pedalboard, imageArray: [pedalboard.imageD!])
    }
}}

`
EDIT: It is working fine in Xcode 11.3.1

Hi @rakesh1504 ,
This seems to be an issue related to GeometryReader. If it works fine in Xcode 11.3.1 but not in a more recent versions of Xcode, then there's not much I can do.
I've found this is an issue reported to Apple, see here. The error doesn't say much, sorry I can't help you more.
I can just say that depending on how you have your views arranged, you might run into this error or not. Meaning that if for some reason, you wrap the whole body or part of it into a VStack it might magically work. I've run myself into this issue, seemed to be caused by a NavigationView and could fix it by using .navigationViewStyle(StackNavigationViewStyle()), see here.
My advice is, take your code and start removing parts of it and see when you don't see that error. When you've identified the exact part that makes it crash, try to change something (maybe simply add another modifier) to make it work. There are plenty of potential "solutions" in SO.
Some more useful links:

https://forums.developer.apple.com/thread/129171
https://stackoverflow.com/questions/58573640/runtime-error-precondition-failure-attribute-failed-to-set-an-initial-value
https://stackoverflow.com/questions/58304009/how-to-debug-precondition-failure-in-xcode

HI @rakesh1504, I'm testing this on the new Xcode 12 beta and this issue has been fixed in SwiftUI 2.0. In my case, I can reproduce the crash when building with Xcode 11.5 but not when building with Xcode 12 beta

Thank you @fermoya for the info. I will check.


mpd: new package at 1

Description of package
Music Player Daemon
Installed manifest of package
(kiss manifest <pkg>)
/var/db/kiss/installed/mpd/version
/var/db/kiss/installed/mpd/sources
/var/db/kiss/installed/mpd/manifest
/var/db/kiss/installed/mpd/depends
/var/db/kiss/installed/mpd/checksums
/var/db/kiss/installed/mpd/build
/var/db/kiss/installed/mpd/
/var/db/kiss/installed/
/var/db/kiss/
/var/db/
/var/
/usr/share/icons/hicolor/scalable/apps/mpd.svg
/usr/share/icons/hicolor/scalable/apps/
/usr/share/icons/hicolor/scalable/
/usr/share/icons/hicolor/
/usr/share/icons/
/usr/share/doc/mpd/README.md
/usr/share/doc/mpd/NEWS
/usr/share/doc/mpd/COPYING
/usr/share/doc/mpd/AUTHORS
/usr/share/doc/mpd/
/usr/share/doc/
/usr/share/
/usr/bin/mpd
/usr/bin/
/usr/

New package

[x] Latest upstream version.
[x] I agree to maintain this package.
[x] I agree to notify the @kiss-community maintainers if I can no longer maintain this package.

Existing package

[ ] I am the maintainer of this package.

Are so many meson flags really needed ? The old mpd build seemed to work fine with just -Dlibmpdclient=disabled.


Easy way to add Authentication to kibana

Hi,
I am using Kibana from the Rancher catalog and I was wondering if there is an easy way to add basic authentication to it while deploying the service?

Useful
Info

Versions
Rancher v1.2.2 Cattle: v0.174.13 UI: v1.2.40

Access
github admin

Orchestration
Cattle

Route
catalog-tab.index

Create your own catalog item with Kibana v5 and than authentication is part of product (X-Pack). If you need 2.x ELK just simple add Nginx/Apache as a proxy (LDAP/volume with pass hashes). Or you can buy Shield licence which will give you AA for legacy versions.

With the release of Rancher 2.0, development on v1.6 is only limited to critical bug fixes and security patches.


Visual Studio Extensions Marketplace down?

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version:  1.91
OS Version: Microsoft Windows10.0

Steps to Reproduce:

Go to extensions tab
search for an extension

Looks like the VS Code Marketplace is down,it reports XHR failed,and it not only occurs on my VS Code,but also my coworkers'. Any official word on this?

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.91.1. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

https://status.dev.azure.com/
azure服务挂了,等恢复吧

It is indeed down

now it works


Close Settings Tooltip Hidden Behind Maximise Button

Description

Suggestion for fix
Make it so that the tooltip never appears in that location
Steps To Reproduce
1. Restore the window.
2. Open Settings.
3. Hover the mouse on the close button.
Requirements
Obvious
Files Version
<IP_ADDRESS>
Windows Version
10.0.25330.1000
Log file
debug.log

Thank you for reporting this issue, this seems to be a platform issue in WinAppSdk but I'll keep the issue open in case someone has a workaround.

What if we place the tooltip under the button?

What if we place the tooltip under the button or on its left?

That would work great, thanks!

What if we place the tooltip under the button or on its left?

That's a good workaround 👍


Fetch User by Email

We can fetch a user by id, but it would be great to also fetch by email.
This could be a new tool, but ideally it would be #2 on the existing fetch command.

Already complete with #2.


Upgrade tests hang with Twisted 16.6 and later

t.w.c.Agent now completely ignores 1xx responses. See https://github.com/twisted/twisted/pull/583.

Fixed with the move to asyncio in fec18a147589ebe933ecfd0200771002119a1a56.


Added custom steps to const and support for float numbers

Fixes:

https://github.com/sfstar/hass-victron/issues/48
https://github.com/sfstar/hass-victron/issues/18
number.victron_settings_systemsetup_maxchargevoltage is now 0.1 precision

tested with my setup

Thank you for opening this PR.
The changes seem to be OK.
However, I currently don't have the time to test them myself.
Since @michaelkuty tested it with his setup I will merge this change and create a release for it

I'm using  this branch and for me it seems to be working, at least we can set SoC and other values by sliders which were broken in your current main branch, but I cannot guarantee that it will not break something else

and thank you for merge/release I think that could help to boot up community to help us make it better/stable


Feature/get end point episodes model router

Description

What work was done?

A GET endpoint added for getting all the episodes that corresponds with a story ID.
Tests are written (newStories-test.js) to test the endpoint with related test data added in testData.js file

Why was this work done?
This is done to support the new story and recently added episodes schema. The episodes GET end point by the new story ID will get all the episodes that a story has.
What feature is it for?
New story and episodes data schema
Any relevant links or images / screenshots
https://trello.com/b/aZl8089B/scribble-stadium-schema

Type of change
Please delete options that are not relevant.

[ ] New feature (non-breaking change which adds functionality)
[ ] This change requires a documentation update

Change Status

[ ] Complete, tested, ready to review and merge

Has This Been Tested

[ ] Yes

Checklist

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] My code has been reviewed by at least one peer
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] There are no merge conflicts

A simple yet important piece of code. Good work.

Thank you! It is still in draft mode. We're running some issues with the tests. Will finalize once this is sorted.


Error when CMS is running re-save entries task.

I keep getting this error in the phperrors log when Craft is running it's re-save entries task.  It appears thhis stops the task from completing.
Call to a member function getUrl() on a non-object in Linkit_LinkitFieldType.php on line 384.
I am running Craft Pro 2.2.2588.

Fixed in the latest release, please make sure you backup and test out pre launch!


I don't see the mongodb configuration

From the background, you can see that mongodb connection error is reported. Check the code to see that file storage is used instead of mongo. It takes about a minute to start, and it crashes in about 10 minutes.

Redeploy again and no problem.

Redeploy again and no problem.

https://github.com/mengshukeji/LuckysheetServer/issues/2

https://github.com/mengshukeji/LuckysheetServer/issues/2

OK, got it.

OK, got it.


pull request for e2e test at 11/20/2016 00:26:06

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Possible lastUpdateCheck timestamp file corruption in UpdateChecker

This looks like a very similar (or the same) problem to #2294. However, this is a fairly minor and low-priority problem and mostly benign, because we auto-generate and overwrite the file every time. It will just be that Jib may do more frequent, unintended update checks.
In #2335, I saw this log:
03:03:20.913 [DEBUG] [org.gradle.api.Task] Failed to read lastUpdateCheck; Text '' could not be parsed at index 0

I am only guessing, but the message sounds like the file was empty.
We overwrite the file with Files.write(), and the JDK code works by opening an OutputStream. So I think it can have the same truncating issue with #2294.
        try (OutputStream out = Files.newOutputStream(path, options)) {
                ...
                out.write(bytes, (len-rem), n);

It will just be that Jib may do more frequent, unintended update checks.

I think it's better to fix this earlier than later, because the metrics may get skewed when we fix this eventually.


Update factor types and their use

The Distributions.jl package now has support for discrete distributions.
There has also been:

a change in how distribution shape parameters are handled/interpreted.
repeated use of "default" values when creating Param() types
issues in how bounds should be handled/specified for discrete factors (e.g., #630)
new evidence in the sampling literature that advices use of randomized Quasi-Monte Carlo approaches (#586)

This PR tracks a series of other planned changes to unify methods to be conceptually consistent, simplify use of ADRIA, and address associated bugs/annoyances.
This base PR defines a new constructor for Param types with ADRIA-specific metadata.
Principal changes include:

dists -> dist, and now expects a Distributions.jl type, rather than a string indicating the distribution type
bounds -> dist_params
ptype indicating the parameter distribution type now expects a more informative name (see discussion in #512)
one of: ["continuous", "ordered categorical", "unordered categorical", "discrete"]

This PR defines custom convenience constructors for ADRIA-specific factors (this base PR - MERGE LAST).
PRs related to this set of changes (note, these should be accepted/merged in the indicated order):

[ ] #637
[ ] #638
[ ] #639
[ ] Add/modify/update tests as appropriate
[ ] Update documentation to reflect changes

In the process of creating these PRs, the following issues are resolved:

#512
#586

@Zapiano you can start reviewing and merging the related PRs if you feel so inclined - just don't expect any tests to pass yet.
We'll run all tests on this PR when all the pieces are ready.

Bypassing review process and merging as I cannot wait. Will take responsibility for anything that breaks due to this PR.


Create an Alert Dialog with 3 buttons - XML ONLY

Create a xml layout for alert dialog with a title and 3 buttons.
This layout will be used as a prompt at the end of every work session to start a short or long break.
REQUIRED:

The title and buttons are center aligned and appear in this order from top to bottom

TITLE
LARGE BUTTON
Medium Button
small  or text-only low-importance button. (used for 'Cancel')

Java code isn't required for this task, just the xml file.

Interested in taking up this issue? Leave a comment expressing your interest along with your @slack id.abnd.
Each issue expects a 24hr turnaround time by default. In case where a student doesn't come back with an update after 24 hours have elapsed, the issue is up for grabs by anyone.

I would like to work on this issue.
Slack ID - @tirth.abnd

Great! Please start working on it.


policy: Do not share same policy for multiple cached selectors

Do not share the same PerSelectorPolicy object between multiple cached selectors. This makes sure that when rules are merged only the rules for the intended selectors are effected by the merging process.
Fixed entanglement of complex L7 rules in policy ingestion.

/test

/test-1.16-4.19

Fixed entanglement of complex L7 rules in policy ingestion.

Is there any user impact or is it more about simplifying the code? Label says it's the former, while the release note seems to say it's the latter.

ci-eks is known to be broken (https://github.com/cilium/cilium/issues/24774), marking as ready-to-merge.

May I know if this can be merged and released with 1.12.9 so I can confirm with the client we will have the fix in 1.12.9 for them?

Fixed entanglement of complex L7 rules in policy ingestion.

Is there any user impact or is it more about simplifying the code? Label says it's the former, while the release note seems to say it's the latter.

Yes, there is user impact when using policies of specific form as demonstrated by the added unit test.

@pchaigno Made the release note more explicit.

@liyihuang Marked this as a release blocker.

Fixed entanglement of complex L7 rules in policy ingestion.

Is there any user impact or is it more about simplifying the code? Label says it's the former, while the release note seems to say it's the latter.

Yes, there is user impact when using policies of specific form as demonstrated by the added unit test.

Thanks! It's now clear it's a bugfix but it's still hard to understand what is the impact for users. Does this lead to a policy bypass, to packet drops, to unnecessary proxy redirections, to a failure to apply the policy, etc.?

@jrajahalme This does not apply cleanly to any stable branches. I was able to fix it on v1.13, but the difference to 1.12 and 1.11 are larger. You will have to do the backport for 1.12 and 1.11 manually.


Use Java 8 when installing Jenkins

As of Jenkins 2.54, Java 8 is required, and using a Java 7 runtime may result in a non-functional Jenkins installation.
This PR also contains some small fixes regarding the home directory creation and shell of the Jenkins user.

Thanks @nre-ableton!

@emmetog thank you!