Add Max Capacity to events

Would have to find a way to set this only for Ninjas tickets.
This may be too complex for users with each session also having capacity fields so I wouldn't just add it on without thought; would like to request comments from Champions/Mentors as to if they would use this.

If you could set the max capacity of each ticket type (EX: for ninjas or loaner equipment) and be able to leave them at infinite (EX: for parents) while others have a max, that would be ideal. Would need to be able to easily modify this even after the event is created. Max ninja levels may increase with additional mentors/volunteers registered.
Champions/Ticket Admins would need a way to be proactively notified when max capacities are almost and fully reached (maybe they can get more equipment or volunteers and increase the capacity of ticket types).

@rosalanghammer related to waiting list, am i right ?

Correct. Plan is now for waiting list to activate and then Dojo admins can easily add additional spaces from the waiting list (over capacity) with a trigger message 'Are you sure you want to add more tickets to this event - Current bookings X' 'Yes/No'
Too difficult to implement a ratio system based on mentors attending as different Dojos have varying policies and venues for this.
Also +1 on notification for Champions and Admins.

You can currently set amount for tickets so I consider this fulfilled.


Editing big template creates LatteMacroLexer exception and the whole PhpStorm freezes

Describe the bug
I was rewriting some legacy plain PHP code to Latte template so I pasted the whole code to the template then I added some Latte comments. After that I started editting the code line after line to make it valid Latte file. In that moment PhpStorm freezed for couple of minutes (1:20 according to logs). After unfreeze PhpStorm freezes everytime I try to edit the template. Unfortunately I have no idea which part of the template creates the exception because debugging is very annoying.
I also tried downgrading to previous PhpStorm version and also downgrading to the previous plugin versions but with no effect.
PhpStorm log: WARN - com.intellij.lexer.FlexAdapter - com.jantvrdik.intellij.latte.lexer.LatteMacroLexer
java.lang.Error: Error: could not match input
Environment:

PhpStorm version 2021.2.2, 2021.3
Plugin version 1.1.4, 1.1.3, 1.1.0
OS version MacOS 12.0.1

To Reproduce
Steps to reproduce the behavior (or attach video):

Open given template in PhpStorm
Edit random part of the template

Code
In the attached file.
Additional context
The original code is legacy and really messy - that was the reason to put it in the template.
overview.latte.zip

Maybe it will be resolved in next version


Build failure: vscode-js-debug

Hi, I'm getting the following error, when I try to install the vscode-js-debug package:
/nix/store/5gl8z4mxbfx4x4r5lamq9ccv4n7l6f1i-stdenv-linux/setup: line 118: jq: command not found

It seems stdenv-linux is expecting jq, which is not there. It seems similar to this old issue, which was resolved by adding jq to buildInputs:
https://github.com/NixOS/nixpkgs/issues/53405
Mentioning the init PR for this package: https://github.com/NixOS/nixpkgs/pull/305824
Steps To Reproduce
I tried installing using a minimal flake:
{
  inputs = { nixpkgs.url = "github:nixos/nixpkgs/master"; };
  outputs = { self, nixpkgs }:
    let pkgs = nixpkgs.legacyPackages."x86_64-linux";
    in {
      devShells."x86_64-linux".default = pkgs.mkShell {

        buildInputs = [ pkgs.vscode-js-debug ];

      };
    };
}

Build log
@nix { "action": "setPhase", "phase": "unpackPhase" }
Running phase: unpackPhase
unpacking source archive /nix/store/q55q0yy6z5mjp1a3j2drxkykng9fd8wf-source
source root is source
@nix { "action": "setPhase", "phase": "patchPhase" }
Running phase: patchPhase
/nix/store/5gl8z4mxbfx4x4r5lamq9ccv4n7l6f1i-stdenv-linux/setup: line 118: jq: command not found
/nix/store/5gl8z4mxbfx4x4r5lamq9ccv4n7l6f1i-stdenv-linux/setup: line 131: pop_var_context: head of shell_variables not a function

Additional context
Add any other context about the problem here.
Notify maintainers

Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.6.33, NixOS, 24.11 (Vicuna), 24.11.20240613.e9ee548`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.2`
 - nixpkgs: `/nix/store/qqwr649pc0qprc9lw2fmdsi1km6p7q2h-source`

Add a :+1: reaction to issues you find important.

Fix PR: https://github.com/NixOS/nixpkgs/pull/320877.

Fix PR: https://github.com/NixOS/nixpkgs/pull/320877.

Thanks, it's working for me now!


Allow selection of export to from YAML frontmatter

Is your feature request related to a problem? Please describe.
I would like to not have to use the modal to update what should be exported. YAML frontmatter is already an accepted way of configuring behaviour in Obsidian and markdown, this would appear to fit in well.
Describe the solution you'd like
---
html-export: true
---

<rest of note>

Describe alternatives you've considered
To solve this issue, unless you hook into the file creation script, then there doesn't appear to be another way.
Additional context
N/A

I have definitely considered this and will likely add it soon. Thanks!

+1 for this feature. My only (non-expert) build would be: what if you use the already accepted syntax for Obsidian Publish?:

publish: true
By taking this approach, then you can more easily switch between obsidian publish and self hosting. On the downside, maybe you want to publish something different to obsidian publish and your own self-hosted static site.
Thank you for an awesome plugin!


User provided URIS via command line argument

Be able to provide the command line with a list of DRS id strings with a flag option and download those Uris in this way without needing to provide a TSV file as input.

implemented in 89031e1347dd9352e36bea9500b789075a492643


Set Domain User Name to Null

@gjvoosten #65 does not set the domain user name to NULL during testing

@VassilIordanov  #91
Tried six new test cases without success

duplicate of NCI-Agency/anet#65


Add support_ignore_nulls and support_ordering in Aggregate expression

Which issue does this PR close?

Closes https://github.com/apache/arrow-datafusion/issues/9924.
Rationale for this change

What changes are included in this PR?

Are these changes tested?

Are there any user-facing changes?

Thanks @huaxingao -- I agree this does what the ticket requests; However given what you have found about SUM(ORDER BY ...) it may make sense to permit that case 🤔

this query is invalid, our parser allows it but it should fail. IGNORE NULLS have a limited functions to be worked with.  all other query engine parsers does.

this query is invalid, our parser allows it but it should fail. IGNORE NULLS have a limited functions to be working with. all other query engine parsers does.

IGNORE NULLS definitely makes sense to error if the aggregate doesn't handle it (as it would result in incorrect answers)
ORDER BY seems more gray to me -- as in the answers won't be incorrect but it would potentially be doing more work than necessary

Marking as draft as I think this PR is no longer waiting on feedback. Please mark it as ready for review when it is ready for another look

@alamb
I am not so sure how to proceed with this PR. Do we still need this PR?
For IGNORE NULLS, I think we have consensus to error in the parser if aggregates don't support IGNORE NULLS.
For ORDER BY, there are two options:

Keep the current behavior, that is, allow SUM(ORDER BY ...). The rationale is:

The DataFusion optimizer would remove the ORDER BY if the order doesn't matter.
For float type, the order matters, so we need the ORDER BY
Postgres allows the SUM(ORDER BY ...).

Error in the parser if ordering doesn't matter (That's what Spark does).

So, we will either change the parser or leave the current implementation as is. It seems to me we don't need this PR anymore?

For ORDER BY, there are two options:

Keep the current behavior, that is, allow SUM(ORDER BY ...). The rationale is:

The DataFusion optimizer would remove the ORDER BY if the order doesn't matter.
For float type, the order matters, so we need the ORDER BY
Postgres allows the SUM(ORDER BY ...).

Yes, let's follow this approach.

For IGNORE NULLS, I think we have consensus to error in the parser if aggregates don't support IGNORE NULLS.

Sounds good to me -- we can also move the error later if we want to enforce it for the expr_fn API as well
Thanks @huaxingao  and @ozankabak


Filling log after upgrade to Homebridge 1.3.0

After upgrade and restart the following gets logged  every two seconds (the second message only in debug mode):
[homebridge-soundtouch-platform] This plugin generated a warning from the characteristic 'On': SET handler returned write response value, though the characteristic doesn't support write response! See https://git.io/JtMGR for more info.
[homebridge-soundtouch-platform] Error:
at Characteristic.characteristicWarning (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2063:79)
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1618:22
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/util/once.ts:9:18
at /usr/local/lib/node_modules/homebridge-soundtouch-platform/node_modules/homebridge-base-platform/src/callback.ts:17:34
How can I prevent this from happening?

I have now upgraded to 1.3.2 and the error noted by @AndersKlinting persists.  I see the same:
[05/03/2021, 11:24:52] [homebridge-soundtouch-platform] This plugin generated a warning from the characteristic 'On': SET handler returned write response value, though the characteristic doesn't support write response. See https://git.io/JtMGR for more info.
While annoying, there doesn't seem to be any other effect.

I'm not seeing that error, but I'm getting this on a fairly regular basis:
[3/7/2021, 7:51:06 AM] [homebridge-soundtouch-platform] This plugin slows down Homebridge. The read handler for the characteristic 'On' was slow to respond! See https://git.io/JtMGR for more info.

The problem appears to be resolved for me, at least cosmetically, through installation of Homebridge 13.3.3.

I see the same as @spikester2391 after upgrade if homebridge to 1.3.3,  so I close this issue


test-infra: remove ebbSlotBefore in favor of the new epochSize

A quick simplification enabled by #1734.

bors r+


can not connect to esp32 return I/BluetoothAdapter(28870): isSecureModeEnabled

I am trying to connect to esp32 I could discover it but cannot connect it' does not throw errors but returns that at debug consol
I/BluetoothAdapter(28870): isSecureModeEnabled

I have a youtube demo with this plugin and esp32(micropython) source in the description, maybe it will help you out.
youtube link https://www.youtube.com/watch?v=LScpE0rUpiw
Thanks,
Sonny


🚀Introduction to Figma Part 5 - Figma Plugins

Description 📜
I have added Introduction to Figma plugins - Anima in Documentation
Fixes #184

Type of change 📝

[x] Documentation (Content Creation in the form of codes or tutorials)

Domain of Contribution 📊

[x] UI/UX

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GWOC'21 contributor

Screenshots / Gif (Optional) 📸

@Debasmita-01


Failed to load AcfCaltech+Detector.mat

Hi David,
As I said before, I could successfully load AcfInriaDetector.mat and perform pedestrian detection. However, when I tried to load AcfCaltech+Detector.mat without making any change of the code, I got the following error
"*** Error in './acf-detect': corrupted size vs. prev_size: 0x01a91098 ***"
It seems to me the code is using memory which was not allocated to it.
After further investigation, I found the error happed here
 int Detector::operator()(const MatP& IpTranspose, std::vector<cv::Rect>& objects, std::vector<double>* scores)
{
    // Create features:
    Pyramid P;
    chnsPyramid(IpTranspose, &opts.pPyramid.get(), P, true);

For AcfInriaDetector.mat, the window size is 100x41 while it is 50x20 for AcfCaltech+Detector.mat. These parameters are loaded automatically from .mat files.
Do I need to make any changes to the code if I want to load AcfCaltech+Detector.mat?

This relates to #20 .  I was able to reproduce this one as well on Raspberry Pi.  I think the *.mat format (or possibly cvmatio) has some problem loading models from a 64 bit host on a 32 bit system.  If ran acf-mat2cpb, now that the PI + *.cpb issue has been resolved, and that seems to load the model okay, but it turns up a depth=2 optimization assumption/assertion I had made in the original project.  I will fix that one for general purpose use.
Convert using this command on the host machine:
./bin/acf-mat2cpb  --input=share/AcfCaltech+Detector.mat --output=share/AcfCaltech+Detector.cpb

I've pushed https://github.com/elucideye/acf/pull/23 for now.  This removes the legacy depth==2 assertion and enables the overloadeddepth==0 variable depth tree evaluation.  I did test AcfCaltech+Detector.mat with an random image with pedestrians and the code runs but I didn't see any detections.  It might take a little more digging.  If you have a recommended test image for that classifier with known output you can post it here for testing and I can take a look.  I can look more this weekend.

@xingwangsfu : The variable tree depth evaluation needed by AcfCaltech+Detector.mat is fixed in  https://github.com/elucideye/acf/pull/25 .  I've compared this with the matlab code on a caltech sample frame (V002 # 1700).

The PR is currently being tested and should be merged soon.

@headupinclouds  Cool. Thanks a lot.


source.remote_address well known attribute

What
This PR introduces a new Well Known Attribute called source.remote_address.
Why
Envoy's source.address (well known) attribute includes the port as IP:PORT. It is desirable to run rate limiting or auth policies relying only on the client address. Hence, this source.remote_address can be used to implement those policies.
Attribute Value
This attribute evaluates to the trusted client address (IP address without port) as it is being defined by Envoy Doc.
In summary, the trusted client address is calculated as follows: By default, Envoy gateway instances are configured to append the source IP address of the immediate downstream node’s connection of the incoming HTTP connections to the X-Forwarded-For header. By default Envoy sets the number of trusted hops to 0,
indicating that Envoy should use the address the connection is opened from,
rather than a value inside the X-Forwarded-For list.
Increasing this count will have Envoy use the nth value from the list, counting from the right.
Where can I use it?
This attribute can be used on selector fields.
As conditions:
- conditions:
  - allOf:
    - selector: source.remote_address
      operator: eq
      value: <IP_ADDRESS>

As SelectorItem to generate descriptor entries.
data:
- selector:
    selector: source.remote_address

Fixes #97
Verification Steps
For the verification steps, this PR adds a new configuration to the existing local development environment. It's the new set of rules for *.d.rlp.com.
{
  "name": "rlp-ns-D/rlp-name-D",
  "hostnames": [
    "*.d.rlp.com"
  ],
  "rules": [
     {
          "conditions": [
               {
                    "allOf": [
                           {
                                "selector": "source.remote_address",
                                 "operator": "neq",
                                 "value": "<IP_ADDRESS>"
                             }
                     ]
                }
        ],
       "actions": [
           {
               "extension": "limitador",
               "scope": "rlp-ns-D/rlp-name-D",
               "data": [
                    {
                         "selector": {
                                 "selector": "source.remote_addres
                          }
                     }
                 ]
            }
         ]
      }
   ]
},

And a new limit configuration
- namespace: rlp-ns-D/rlp-name-D
  max_value: 2
  seconds: 10
  conditions: []
  variables:
  - source.remote_address

That configuration enables source based rate limiting on *.d.rlp.com subdomains, with only one "privileged" exception: IP "<IP_ADDRESS>" will not be rate limited.

Run the environment

make build && make local-setup

Port-forward envoy:
kubectl port-forward --namespace default deployment/envoy 8000:8000

Alice (IP: <IP_ADDRESS>) has 2 requests per 10 seconds:
while :; do curl --write-out '%{http_code}\n' --silent --output /dev/null  -H "X-Forwarded-For: <IP_ADDRESS>" -H "Host: test.d.rlp.com" http://<IP_ADDRESS>:8000/get | grep -E --color "\b(429)\b|$"; sleep 1; done

Curl tool logs should show only two requests allowed for every 10 requests.
Bob (IP: <IP_ADDRESS>) has 2 requests per 10 seconds:
while :; do curl --write-out '%{http_code}\n' --silent --output /dev/null  -H "X-Forwarded-For: <IP_ADDRESS>" -H "Host: test.d.rlp.com" http://<IP_ADDRESS>:8000/get | grep -E --color "\b(429)\b|$"; sleep 1; done

Curl tool logs should show only two requests allowed for every 10 requests.
Charley (the Boss) with privileged IP <IP_ADDRESS> does not get rate limited.
while :; do curl --write-out '%{http_code}\n' --silent --output /dev/null  -H "X-Forwarded-For: <IP_ADDRESS>" -H "Host: test.d.rlp.com" http://<IP_ADDRESS>:8000/get | grep -E --color "\b(429)\b|$"; sleep 1; done

Curl tool logs should show all requests being accepted.

Note: running all the three clients also shows that rate limiting counter is not shared and they have their own counter.  IOW, each one has 2 requests every 10 seconds.

Comments addressed. Ready for review @adam-cattermole @alexsnaps


Event thumbnail image display issue

I discovered this when I uploaded a thumbnail image for my workshop:
I uploaded a PNG at 2x size 620*480 px, but the displayed thumbnail is enlarged and only parts of the image are shown.

Oh yes, this is familiar.  I think I may have a fix for that on the test site, will have to check.

@xinyil I have the image displayed as a background and the change I've made in test is to set it be contained.  I don't think we can handle that much variation in image sizes, and after all you have documented what the images ought to be.

If we have the image size documented, I think we should set this to:
background-position: 50% 50%;
background-size: cover;

and upload the correct size images. I think it's better to enforce consistency among image size and alignment than to try to handle the edge case of an image with a weird aspect ratio or with text at its edges.

@thatbudakguy will that work for 2x images? I think I may have set it to contain to handle the 2x case (but it's been a while, I could be wrong). This sounds fine to me, you should be able to test display against events from production data.

we already had grid set up (on an <a> element, weirdly) with an image area blocked out, so this was super easy! added a div, locked it to the area, and applied the background styles to it. the MDN docs on cover say:

The cover value specifies that the background image should be sized so that it is as small as possible while ensuring that both dimensions are greater than or equal to the corresponding size of the container.

I think that's closest to our use case.


Assign lower priority to MS web access (e.g. searches) than to MS API access

Over the last while I've noticed a consistent correlation between when I do a search on MS via the search web interface and when I see, and people report, delays/timeouts in using FIRE/AIM.
SD being able to access MS and people being able to use the MS API (e.g. FIRE, AIM, etc.) is something that should not be affected by resources requested by someone using the MS web interface (or at most minimally affected).

This would be nice, but is kinda pretty difficult. I'm not convinced it's worth the significant effort it would take.

this isn't so much a "priority" thing as it is a "mysql queries are blocking and we only have one worker" deal


Update download.py - set cache_dir to the same directory as local_dir to prevent potential copying errors

There's a problem when a cache dir is on a different volume than the target dir:

‹[1Apytorch_model-00001-of-00002.bin: 100%|----------| 9.94G/9.94G [00:42<00:00, 235MB/s]
‹[1AFetching 7 files:  14%|-?        | 1/7 [00:42<04:14, 42.44s/it]
Traceback (most recent call last):
File "/opt/conda/lib/python3.9/shutil.py", line 825, in move
os.rename(src, real_dst)
OSError: [Errno 18] Invalid cross-device link: '/root/.cache/huggingface/hub/models--mistralai--Mistral-7B-Instruct-v0.1/blobs/2f237251ac3ecb3bcbd8978b3eb7b55b5e83c06cd5224b276d2d8462773488c8.incomplete' -> '/pretrained/checkpoints/mistralai/Mistral-7B-Instruct-v0.1/pytorch_model-00001-of-00002.bin'

Setting cache_dir to be equal to the target dir prevents it.

I'm concerned about accepting this change because it will pollute the checkpoint directory with the huggingface cache internal structure for everybody.
It seems to me like this would be a bug to report in https://github.com/huggingface/huggingface_hub, when moving is not possible (because the volumes are different) they could try to copy the data first and then remove the original source. What do you think of suggesting this fix to their issue tracker?


Fix acceptance tests

Looks like two changes got merged together causing this issue.
Signed-off-by: Luiz Carvalho<EMAIL_ADDRESS>

I'm gonna merge this since it fixes main.


Update form submissions API URL

We just added a new api-specific endpoint for form submissions:
https://github.com/dimagi/commcare-hq/pull/30784
https://confluence.dimagi.com/display/commcarepublic/Submission+API

@kaapstorm @orangejenny

Thanks for this @esoergel !

@kaapstorm do you have write access to merge this?  I'm waiting on this ticket before I can merge.


FreeCodeCamp Down

It looks like FreeCodeCamp is down.

Seems now everything is OK.

The best thing to do is to send me a message on Gitter when this happens.


Try again button for giving permission to mic not working

When I clicked on the mic button and denied it the permission it showed me a prompt to try again. But now when I click on try again it does not work.

Same thing happen to me right now!


coverage package should be private

What are you changing?

make the coverage package private

Why?

so canaries work

hat-tip to @oliverabrahams for spotting


Can not copy all result data as text

DBeaver trunc data:

psql does not:

If there only one result row I can select cell and copy it, but when there is many rows
I can not switch to text and copy all.
Copy as CSV also does not work:

You can configure maximum width of plaintext column in preferences (database->editors->data editor->Presentation). It is 255 by default.
In grid mode you can run command "Columns pack: fit values" in order to see full string values.
Please write some details about what is wrong with Copy as CSV (does it truncate values?)

On line 3 and 13 additional quotes appear. Where they from?

Please write some details about what is wrong with Copy as CSV (does it truncate values?)

It adds extra quotes


NavigationBar problem

Im compiling the sample app on master and the transparent navigation bar tinting seems not to be working for me 😞 .
When I set <item name="android:windowTranslucentNavigation">true</item> on my theme the bottom bar gets drawn behind the translucent navigation bar. Is there a specific way I'm supposed to use this?

Are your tabs colored?

Use this code  :
boolean hasMenuKey = ViewConfiguration.get(this).hasPermanentMenuKey(); boolean hasBackKey = KeyCharacterMap.deviceHasKey(KeyEvent.KEYCODE_BACK); if(!hasMenuKey && !hasBackKey) {((ViewGroup.MarginLayoutParams) mBottomBar.getLayoutParams()).bottomMargin += "NavigationBarHeight";}

@Sultone I'm facing this problem too. How should I use the snippet you provided above?
@FabianShallari  did you solve your problem?

@mehrdaad Paste it just after having declared your bottombar, then replace "NavigationBarHeight" by a method which get the nav bottombar height. You have few exemples here : http://stackoverflow.com/questions/20264268/how-to-get-height-and-width-of-navigation-bar-programmatically
It will add a bottom margin for your bottombar if there is a navigationbar :)

This is now fixed in the latest versions. You can have app:bb_behavior="underNavbar" and the BottomBar will automatically calculate the correct size for itself. No more "magical" auto detection for that, as it was highly unreliable.


Updated ApacheDS server script to work with lastest spoon + automatic…

…ally version itself

I think this  should go to :
https://github.com/turboapps/spoonme ;)
2015-09-07 17:17 GMT+02:00 Roman Stoffel<EMAIL_ADDRESS>
…ally version itself
You can view, comment on, or merge this pull request online at:
https://github.com/spoonapps/spoonme/pull/58
Commit Summary

Updated ApacheDS server script to work with lastest spoon +
automatically version itself

File Changes

M apache-directory/server/spoon-startup.bat
https://github.com/spoonapps/spoonme/pull/58/files#diff-0 (16)
M apache-directory/server/spoon.me
https://github.com/spoonapps/spoonme/pull/58/files#diff-1 (47)

Patch Links:

https://github.com/spoonapps/spoonme/pull/58.patch
https://github.com/spoonapps/spoonme/pull/58.diff

—
Reply to this email directly or view it on GitHub
https://github.com/spoonapps/spoonme/pull/58.

--
Regards
Piotr Galiszewski


Limitations of makeSubInfo/ info field selection

The info object used in resolvers includes the sub-selection of the query for the current field.
As described here https://github.com/graphcool/prisma-binding/issues/118, there are valid use-cases for extracting subfields from this selection to pass that into a binding.
In #118 and also this PR https://github.com/graphql-binding/graphql-binding/pull/69, an approach is presented that tries to solve this issue.
In the following I describe how this could be used and discuss what the fundamental limitation of this approach is, that we need to understand to move forward with this topic.
Let's say we have the following data model:
datamodel.graphql
type User {
  id: ID! @unique
  name: String!
}

type Address {
  id: ID! @unique
  street: String!
  userId: String!
}

In this case, for some reason we couldn't create a direct relation between both types, maybe because they're living in separate sources.
The schema that we actually want to expose is this:
type Query {
  me: User
}

type User {
  id: ID! @unique
  addresses(skip: Int first: Int): [Address!]!
}

type Address {
  id: ID! @unique
  street: String!
}

Now we want to establish this connection between types using graphql-yoga & graphql-binding.
The current approach without the new tooling would look like this:
{
  Query: {
    me(parent, args, ctx, info) {
      const userId = getUserId(ctx)
      return ctx.db.query.user({where: {id: userId}}, info)
    }
  },
  User: {
    addresses: {
      fragment: `fragment UserId on User { id }`,
      resolve(parent, args, ctx, info) {
        return ctx.binding.query.addresses({where: {userId: parent.id}}, info)
      }
    }
  }
}

As described in #118, it can be more efficient (query batching / saving queries) to combine this into one resolver.
Now makeSubInfo comes into play.
The API of makeSubInfo looks like this:
makeSubInfo(info: GraphQLResolveInfo, path: string, fragment?: string): GraphQLResolveInfo

We now can use that util function for our example:
{
  Query: {
    me(parent, args, ctx, info) {
      const userId = getUserId(ctx)
      const subInfo= makeSubInfo(info, 'address')
      const addresses = ctx.db.query.addresses({where: {userId}}, subInfo)
      return {
        id: userId,
        addresses
      }
    }
  },
}

For queries, that look like this, it's working as expected:
{
  me {
    id
    addresses {
      street
    }
  }
}

Problem
However, the following queries will break this resolver:
1. Not selecting the sub field
{
  me {
    id
  }
}

Here addresses are not selected at all, so the delegation to graphql binding will fail.
2. Using aliases in the query
{
  me {
    id
    first5: address(skip: 0, first: 5) {
      street
    }
    next5: address(skip: 5, first: 5) {
      street
    }
  }
}

Here we're using multiple aliases for the same field, but different args, so their respond has to differ.
The current implementation would just return an object of this form:
{
  me: {
    id: '',
    addresses: [],
  }
}

To actually provide the correct values for each aliased field, the returned object has to look like this:
{
  me: {
    id: '',
    first5: [],
    next5: []
  }
}

This means we have to either sacrifice the use of aliases or adjust the API of makeSubInfo.
Solution
The sacrifice of just not using aliases in queries is trivial, we don't have to further discuss that.
But let's say we still want to support aliases in our queries. This would mean, that we need to keep the output of the delegation to the binding with makeSubInfo dynamic.
One solution could be, that instead of directly returning the resolved value, we would have to wrap it in an object like this:
const query = `{ me { addresses { street } } }`
const result = binding.query.addresses({}, makeSubInfo(info, 'addresses'))

assert(result).toBe({
  addresses: []
})

or in the case of a query containing aliases:
const query = `{ me { addresses1 { street } addresses2 { street } } }`
const result = binding.query.addresses({}, makeSubInfo(info, 'addresses'))

assert(result).toBe({
  addresses1: [],
  addresses2: [],
})

This, however, would make typings on these bindings useless, as the response could look like anything. This is a trade-off we have to live with in this case.
To keep the nice typings and still have with flexible API, the proposal is to separate these into 2 APIs:
binding.delegateQuery.addresses({}, info)
binding.query.addresses({}, '{ id }')

The .delegateQuery method would return the type any as typings are of no value here, the .query method would return a type that is being generated based on the selection set in the last argument of the method, the fragment.
This is just a rough proposal for the future API, open for discussion.
Anyone interested working on this topic, please respond here or join our public Graphcool slack to join the conversation!

I am bit confused here. I mean the selection set is already implemented and works, you can do binding.query.addresses({}, '{ id }'). It's possible I've misunderstood something and this works differently, but that would a breaking change.
An addition of delegateQuery is somewhat interesting, but in my opinion not exactly essential. Honestly, I did not even know there are some aliases in graphql :)
I am coming from a bit different direction regarding subscriptions (see https://github.com/graphcool/prisma-binding/issues/78#issuecomment-377475090). If I am not mistaken, there is no solution for that in this proposal. In case that wasn't the intention, I apologize :)

Thanks for the answer @FredyC ! It would indeed be a breaking change, which we would of course be reflected in the semver version.
I'm answering in that issue separate, what I think you need is the opposite of makeSubInfo, which is embedding an info in a parent context

Thank you for your work @timsuchanek. Regarding the two problems:

Field not selected

In the case that there is no fragment (e.g. makeSubInfo(info, 'subfield')), couldn't we return null or throw an error that could be handled by the programmer? There is also the possibility of returning an info object with an empty selection ('{ }').
And in the case that there is a fragment (e.g. makeSubInfo(info, 'subfield', '{ id }')) it would make sense for me if it returns an info for that subfield and selection fragment (subfield { id }).

Aliases

I couldn't test with a field that returns an array, but my implementation of makeSubInfo is working with aliases and fields that return an object. I did a fast test here and
mutation {
  login(email<EMAIL_ADDRESS>password: "123456789") {
    gabrielToken: token
    names: user(alias: "names") { name, company { name } }
    ids: user(alias: "ids") { id, company { id } }
  }
}

Gave me
{
  "data": {
    "login": {
      "gabrielToken": "eyJhbGciO...hXa2Uhg",
      "names": {
        "name": "Gabriel",
        "company": {
          "name": "ACME"
        }
      },
      "ids": {
        "id": "cjftyusg900080827nwt39wds",
        "company": {
          "id": "cjftyusi300090827ub3s66m6"
        }
      }
    }
  }
}

But the object returned by my resolver wasn't using the aliases it was in the shape of
{
  token: '',
  user: {
    id: '',
    name: '',
    company: {
      id: '',
      name: '',
    },
  },
}

graphql-yoga probably did the work of extracting the right properties and mounting the correct response. I wounder how it behaves with your example, does it throw an error or return the full array for both aliases?
Now, about your solution, I think it would work great. We would just change this:
const addresses = await ctx.db.query.addresses({where: {userId}}, makeSubInfo(info, 'addresses'))
return {
  id: userId,
  addresses
}

To this
const addresses = await ctx.db.delegateQuery.addresses({where: {userId}}, info)
return {
  id: userId,
  ...addresses
}

Did I get it right?

@gcangussu thanks for your answer. Yes you got it exactly right. Interesting, that it has been resolved properly in your use case, I will try to reproduce that. In my case both aliases got the same payload back, even if the args differed.

@timsuchanek I found a minor bug (2 lines) in the makeSubInfo method that prevented using it for sub field selection see pull request here: https://github.com/graphql-binding/graphql-binding/pull/149

Thank you for reporting.
In the last few months, since the transition of many libraries under The Guild's leadership, We've reviewed and released many improvements and versions to graphql-cli, graphql-config and graphql-import.
We've reviewed graphql-binding, had many meetings with current users and engaged the community also through the roadmap issue.
What we've found is that the new GraphQL Mesh library is covering not only all the current capabilities of GraphQL Binding, but also the future ideas that were introduced in the original GraphQL Binding blog post and haven't come to life yet.
And the best thing - GraphQL Mesh gives you all those capabilities, even if your source is not a GraphQL service at all!
it can be GraphQL, OpenAPI/Swagger, gRPC, SQL or any other source!
And of course you can even merge all those sources into a single SDK.
Just like GraphQL Binding, you get a fully typed SDK (thanks to the protocols SDKs and the GraphQL Code Generator), but from any source, and that SDK can run anywhere, as a connector or as a full blown gateway.
And you can share your own "Mesh Modules" (which you would probably call "your own binding") and our community already created many of those!
Also, we decided to simply expose regular GraphQL, so you can choose how to consume it using all the awesome fluent client SDKs out there.
If you think that we've missed anything from GraphQL Binding that is not supported in a better way in GraphQL Mesh, please let us know!

In the context of that particular issue - GraphQL Mesh uses the new schema stitching introduced in GraphQL Tools v6 and together with the transform API should be able to cover optimizations like that.
But I might be missing the purpose here so, please feel free to open a new issue on the GraphQL Mesh repo.
We're looking forward for your feedback of how we can make your experience even better!


Errors are no longer listed in the order in which the compiler finds them (regression?)

Since a short while (15.6, 15.5?) the errors listed in the Error List window in Visual Studio 2017 are in some odd undefined order.
The order in the Output window is correct (first in declaration order comes first).
This is particularly confusing and becomes time-consuming when working on large solutions with large refactorings, where first-in-declaration-order is the usual way to go to fix errors.
Repro steps
Always reproducible, most visible when you have a lot of errors in multiple files:

Create a project with at least three files
Make sure you have an error in each file
The order will not be first-encountered-to-last-encountered

Expected behavior
Errors should be displayed in first-to-last order, that's also how this used to work. This has the benefit of (often) fixing the following errors by taking care of the first one in the list.
Actual behavior
Some undefined order. It is not the opposite order, nor alphabetical by description, nor numerical by error code, nor by severity.
As a consequence, "Next error" and "Previous error" make little sense with respect to the overview in the error list.
Note that within any one file the errors appear in line-number order.
Known workarounds
Use the Output window instead. This works, but it not as neat as working from the cleaner Error List.
Related information
Seen at least from 15.6, possibly a little earlier. Can't remember for certain how it was from 15.3 and before, but I do not have the ability to test it. In Visual Studio 2015 this was definitely not the case, they appeared in order (as far as I can remember).

@abelbraaksma I have tried the following with 15.8 Preview 5:
File2.fs
module File2

let f1 () = x

File1.fs
module File1

let f2 x = (x, 12)

Program.fs
// Learn more about F# at http://fsharp.org

open System
open File2
open File1

let f3 x y = f1 x |> f2 y

[<EntryPoint>]
let main argv =
    printfn "Hello World from F#!"

    f3 1 2 |> ignore
    0 // return an integer exit code

The error list is as follows:

Code
Description
Project
Line

FS0039
The value or constructor 'x' is not defined.
ConsoleApp20	C:\Users\phillip\source\repos\ConsoleApp20\ConsoleApp20\File2.fs
3

FS0001
(elided for formatting)
ConsoleApp20	C:\Users\phillip\source\repos\ConsoleApp20\ConsoleApp20\Program.fs
7

FS0001
(elided for formatting)
ConsoleApp20	C:\Users\phillip\source\repos\ConsoleApp20\ConsoleApp20\Program.fs
13

This would appear to be in order.

Closing this out. @abelbraaksma I cannot repro this with the release VS 15.8.x. Please do report back if you see it with that release.

@cartermp added the needs repro label on Aug 13

It's been a while, but I've added a repro in the newly created issue #5958. I believe it happens with any project, but it's a repro nonetheless ;). This issue should remain closed, I guess, let's continue in the new one, with new info.


Check whether the CA trust chain is needed

The trust anchor stored in the broker information reflects the trust
chain of the token, not necessarily the trust chain of the API
endpoint; but we're using it for the latter in all cases.
This changes NewDatastore to check whether the clientset can be used,
by retrieving the endpoints. This allows the configuration to be
verified, and switched to use the stored trust anchor if necessary.
Fixes: #649
Signed-off-by: Stephen Kitt<EMAIL_ADDRESS>

This code will be going away soon when we switch to use the admiral syncer API. Can you make these changes in _https://github.com/submariner-io/admiral/blob/master/pkg/syncer/broker/config.go_ instead?

I’d rather not make the changes in Admiral instead — I’ll do them in addition (I need this to work sooner rather than later).

This code will be going away soon when we switch to use the admiral syncer API. Can you make these changes in _https://github.com/submariner-io/admiral/blob/master/pkg/syncer/broker/config.go_ instead?

I’d rather not make the changes in Admiral instead — I’ll do them in addition (I’d like to get this working sooner rather than later).

OK - that's fine - I see this is for a POC.


I'm sorry

Based on https://github.com/parquet-go/parquet-go/issues/1 , I had the wrong impression I was the only one who stepped up and temporary taking over maintaining this project.
Fixing issues and ensuring the healthy of the library has been my core objective. I raised a ticket to outline first steps I had in mind for the project here https://github.com/parquet-go/parquet-go/issues/19.
Unfortunately, I was operating under the assumption I can make correct judgement while executing my duties. I had no impression that there are other maintainers out there who were actively involved for this I'm terribly sorry.
I love this project and I want it to thrive,  If my actions hurts the project in any way I apologise to anyone affected by it.
For those who were wondering.
I merged a fix to a critical issue https://github.com/parquet-go/parquet-go/pull/31 without giving time for maintainers to review.
That being said, I have some questions.

Is there governance for this project that I'm not aware of ?
Is there a list of active maintainers ?
Should I step down ?
What should be done moving forward ? I'm happy to revert  all non approved changes, Including removing the release just please let me know who I should talk to.

Thanks and  have a good day.

I don't think you should apologize. Personally I would rather bias towards doing things than bias towards waiting for a consensus that might not arrive. I really appreciate all of your energy towards improving the project.

I concur, you have done an amazing job so far and there is no need for apologies. I do wonder if we want a list of current and previous maintainers though for some basic visibility.

I appreciate your enthusiasm, but agree we should slow things down. There are a number of very large projects that depend on this library and we should be thoughful about changes.

Is there governance for this project that I'm not aware of ?
Is there a list of active maintainers ?

Not that I'm aware of, but I think we need it.

Should I step down ?

No.

What should be done moving forward ? I'm happy to revert all non approved changes, Including removing the release just please let me know who I should talk to.

All changes should require approval. We should definitely not be merging things that have not been code reviewed. We should setup a CODEOWNERS file so you can easily ping us for a review.
I am personally fine with the release, but we should have more coordination and awareness of cutting releases.

All changes should require approval. We should definitely not be merging things that have not been code reviewed. We should setup a CODEOWNERS file so you can easily ping us for a review.

I'd like to also get together a basic roadmap.  No strong preferences on how or what form, could be a section in the readme, GH discussion, etc.  The recent changes are all great and agreeable (go version, cleanup, etc), but need consensus before deprecating APIs or more impactful changes.

Seeing the feedback here its pretty clear to me the project is still alive and in good hands.
I paid close attention to this because I thought it was abandoned, I didn't want my favourite package to die.
I was committing to this between interviews,  I think Its best for me to focus more on my preps . I'm very happy to see all these people who are more capable than me chiming in. I see people from @grafana and @polarsignals
With that being said, I am officially stepping down as a maintainer .  I don't mind my permissions being taken away.


As a user I'd like the old Statoil news pages from 2016-2018 to be available as archived pages in the new solution

Extract data from AEM
Acceptance criteria

Live pages can be made static on demand
Pages available from Azure
Pages available from new site

Sub-tasks

[x] Create tool to extract content from AEM including assets
[ ] Figure out how to make pages available from new Sanity/Nextjs-based solution (implementation can wait)
[ ] Figure out how to do styling for the pages

@nilsml Refactoring script to extract the content of any page irrespective of its template.

https://nextjs.org/blog/incremental-adoption

@nilsml Updated code to fetch page title and description and created local nextjs server and working on fetching the data and adding styles.

@nilsml I am able to display raw news pages in nextjs application and next steps are to

Remove Lazy load jQuery dependencies to the image components HTML
Clean up the styles and add only necessary styles. For this, I will create a new gulp task in AEM source code and generate archive-style.css file

@nilsml I have updated the web scrapper scripts to fetch all the client libraries required for the styles to work. We now have a working nextjs application that serves archived news.
We have to discuss when to integrate this with energy vision project

@nilsml I will start looking into old archive pages in AEM which should be moved to nextjs


New version: BibInternal v0.1.4

Registering package: BibInternal
Repository: https://github.com/Azzaare/BibInternal.jl
Created by: @Azzaare
Version: v0.1.4
Commit: 4a4a39a0565bd16a8fff3d35e900b6a128cd65a6
Git reference: master
Release notes:

Bibtex entries now handle names composed of first, middle, particle, last and junior parts

Previous update v0.1.3 wasn't automatically merged yesterday (probably due to GitHub being down for a long while). As I am stuck and need to advance quickly today, I will pass to v0.2.0 . Please ignore this PR


(WIP) Mailer settings

Motivation and Context
Adding settings for student email notifications, so users can choose if they want to be subscribed.
Changes
Create migration to add receives_invite_emails and receives_results_emails columns to users table. (type boolean, default true)
Adding route for students to view settings. (including changing user_policy to allow students access)
Created view for settings, with form to patch current student attributes.
Updating mailer calls to check for student preferences.
Type of change (select all that apply):

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Refactoring (internal change to codebase, without changing functionality)
[ ] Test update (change that modifies or updates tests only)
[ ] Other (please specify):

Testing
Integration tests in the student controller to verify mailer settings.
Settings disablement tests added to mailer integration tests.
Shared example test verifying unsubscribe option in emails.
Questions/Comments
Checklist

[x] I have performed a self-review of my own code.
[x] I have added tests for my changes, if applicable.
[x] I have updated the Changelog.md.
[x] My change requires a change to the documentation (add details below).
[x] I have fixed any Hound bot comments (check after opening pull request).
[x] I have verified that the TravisCI tests have passed (check after opening pull request).
[x] I have reviewed the test coverage changes reported on Coveralls (check after opening pull request).

Required documentation changes (if applicable)
Adding to Wiki in Developers: Enabling Action Mailer in Development

Great work! I left some inline comments, and also here is one general comment:

Please add a validation for the new attributes for "inclusion" in [true, false], matching the validations for other boolean attributes. Then, add new tests in the Assignment model spec to check that this validation occurs.

Do you mean in the Student Model Spec?

Oh yes, the student model spec!


[Ubuntu] Failed to apt-get libmysqlclient-dev

Describe the bug
On Ubuntu 16.04, since today (1/29/2020), installation of libmysqlclient-dev errors out:
sudo apt-get libmysqlclient-dev
...
Err:87 http://security.ubuntu.com/ubuntu xenial-security/main amd64 libmysqlclient-dev amd64 5.7.28-0ubuntu<IP_ADDRESS>
  404  Not Found
Fetched 30.0 MB in 0s (30.3 MB/s)
E: Failed to fetch http://security.ubuntu.com/ubuntu/pool/main/m/mysql-5.7/libmysqlclient-dev_5.7.28-0ubuntu<IP_ADDRESS>_amd64.deb  404  Not Found

E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

Area for Triage:

Question, Bug, or Feature?:
Bug
Virtual environments affected

[ ] macOS 10.15
[x] Ubuntu 16.04 LTS
[ ] Ubuntu 18.04 LTS
[ ] Windows Server 2016 R2
[ ] Windows Server 2019

Expected behavior
Install successfully
Actual behavior
Errors out.
E: Failed to fetch http://security.ubuntu.com/ubuntu/pool/main/m/mysql-5.7/libmysqlclient-dev_5.7.28-0ubuntu<IP_ADDRESS>_amd64.deb  404  Not Found

@ivailop the image has been rolled out. Could you check that ibmysqlclient-dev is preinstalled?

It appears to be working fine now.


chore: deprecate disk_space option

About this change—what it does
Should be removed a long ago.

please fix the syntax error


Group and filtger data

Is it avaiable to group and filtger rereports ?
For example, take report "REFERRERS URLS" and is to possible to filter just URLS included some data ?

This will be addressed by #117. I'm working on it as we speak. Stay tuned!

Sorri i don t understand anything from  #117
Does it work  now? Or you ve been working at it?

It will let you filter/search the report based on the data that you are after. It's not available yet, it will come out soon.
Let me know if that makes sense.


When i run Runelite a see tiles with fire on them

When i run Runelite a see tiles with fire on them, i see the window the settings but the login screen is just in tiles, this bug is only on Runelite, other clients work well.
thanks

https://github.com/runelite/runelite/wiki/Disable-Hardware-Acceleration

after disabling hardware acceleration still the same problem

You did not followed the guide properly then

Then downgrade Java or something, we support only Java 8.

thanks


task_name

Hello! What does it mean to achieve task_name in print(f"Task: {task_name}: {index]} - {text_probs[0][index]}")?

Hello! Where is this code? (I forget why but I guess I wanted to print whether the predicted degradation type is correct.)

import torch
from PIL import Image
import open_clip
checkpoint = 'pretrained/daclip_ViT-B-32.pt'
model, preprocess = open_clip.create_model_from_pretrained('daclip_ViT-B-32', pretrained=checkpoint)
tokenizer = open_clip.get_tokenizer('ViT-B-32')
image = preprocess(Image.open("haze_01.png")).unsqueeze(0)
degradations = ['motion-blurry','hazy','jpeg-compressed','low-light','noisy','raindrop','rainy','shadowed','snowy','uncompleted']
text = tokenizer(degradations)
with torch.no_grad(), torch.cuda.amp.autocast():
text_features = model.encode_text(text)
image_features, degra_features = model.encode_image(image, control=True)
degra_features /= degra_features.norm(dim=-1, keepdim=True)
text_features /= text_features.norm(dim=-1, keepdim=True)
text_probs = (100.0 * degra_features @ text_features.T).softmax(dim=-1)
index = torch.argmax(text_probs[0])

print(f"Task: {task_name}: {degradations[index]} - {text_probs[0][index]}")there

Ok, according to the code, I think I just want to know whether the predicted degradation type is correct. The task name should be pre-defined like image dehazing.


Streaming openai api support

Description
Use transformers TextIteratorStreamer to support streaming response for the OpenAI API. #762
Ref https://huggingface.co/docs/transformers/internal/generation_utils
Related Issue
None

choice_data = ChatCompletionResponseStreamChoice(
    index=0, delta=DeltaMessage(content=new_text), finish_reason=None
)
chunk = ChatCompletionResponse(
    model=model_id, choices=[choice_data], object="chat.completion.chunk"
)

代码有些问题,流式接口返回时这块会报错,
ChatCompletionResponseStreamChoice和ChatCompletionResponse不匹配,
要在openai_api_protocol.py建一个ChatCompletionResponseStream进行替换
class ChatCompletionResponseStream(BaseModel):
    id: str = Field(default_factory=lambda: f"chatcmpl-{shortuuid.random()}")
    object: str = "chat.completion"
    created: int = Field(default_factory=lambda: int(time.time()))
    model: str = "chinese-llama-alpaca"
    choices: List[ChatCompletionResponseStreamChoice]

choice_data = ChatCompletionResponseStreamChoice(
    index=0, delta=DeltaMessage(content=new_text), finish_reason=None
)
chunk = ChatCompletionResponse(
    model=model_id, choices=[choice_data], object="chat.completion.chunk"
)

代码有些问题,流式接口返回时这块会报错, ChatCompletionResponseStreamChoice和ChatCompletionResponse不匹配,
要在openai_api_protocol.py建一个ChatCompletionResponseStream进行替换
class ChatCompletionResponseStream(BaseModel):
    id: str = Field(default_factory=lambda: f"chatcmpl-{shortuuid.random()}")
    object: str = "chat.completion"
    created: int = Field(default_factory=lambda: int(time.time()))
    model: str = "chinese-llama-alpaca"
    choices: List[ChatCompletionResponseStreamChoice]

您好，我修改了一下代码，使得ChatCompletionResponse兼容两种格式的返回。现在运行不会报错了
class ChatCompletionResponse(BaseModel):
    id: str = Field(default_factory=lambda: f"chatcmpl-{shortuuid.random()}")
    object: str = "chat.completion"
    created: int = Field(default_factory=lambda: int(time.time()))
    model: str = "chinese-llama-alpaca"
    choices: List[
        Union[ChatCompletionResponseChoice, ChatCompletionResponseStreamChoice]
    ]

Thank you for your contribution to our project.
Since we are working on Chinese-LLaMA-Alpaca-2, and it is still under construction, we will be very glad to accept PR to Chinese-LLaMA-Alpaca-2. Would you please create a PR on Streaming openai api support to Chinese-LLaMA-Alpaca-2? Most of the code of openai_api_protocol.py and openai_api_server.py in the two projects are the same, except for some prompts and naming conventions. We really appreciate for your contribution.
As long as we have reviewed your code, we will merge your PRs in both repos.

Thank you for your contribution to our project. Since we are working on Chinese-LLaMA-Alpaca-2, and it is still under construction, we will be very glad to accept PR to Chinese-LLaMA-Alpaca-2. Would you please create a PR on Streaming openai api support to Chinese-LLaMA-Alpaca-2? Most of the code of openai_api_protocol.py and openai_api_server.py in the two projects are the same, except for some prompts and naming conventions. We really appreciate for your contribution.
As long as we have reviewed your code, we will merge your PRs in both repos.

ok


Fix: Homepage class error issue in frontend preventing metadata image display

In this PR I've fixed an issue with className for image on HomePage

great work!


change entity and remove useless entity

would continue working on #234

deleted dev/work-0 since moving the change to dev/add-entity and close this PR

Duplicated of PR https://github.com/futurewei-cloud/alcor/pull/240.


Allow to not specify secrets even if it is running in a kubernetes cluster

ERROR com.instaclustr.cassandra.backup.cli.BackupApplication - This code is running in Kubernetes or as a Kubernetes client but there is not 'k8sSecretName' field set on backup request!
can this be upto the user if they want to specify a kubernetes secret?

@puneetloya sure I ll introduce some flag, do you want me to release it too or are you fine with snapshot for a while?

@puneetloya how do you want to invoke a backup then? where do you read these secrets from? or do you use local backuper which does not require you to provide a secret?

a flag is great. I am supplying secrets as environment variable.
Can the flag be something like running-as-client or running-as-kubernetes? If not the default behavior you have
Release is not required.

I am invoking the backup similar to what cassandra-sidecar project has? A bare bones http server to run the backup command.

@puneetloya pull master branch of this repo and build it, I have just pushed this
That component was just released and this is introduced there (2)
You have to set pretend.not.running.in.kubernetes to true as system property to override the default behaviour.
If you use cassandra-sidecar, you have to build this project and update cassandra-backup version there to 1.1.9-SNAPSHOT and build it. (3)
I can do it tomorrow for you and release it if you just dont know how to proceeed.
(1) https://github.com/instaclustr/cassandra-backup/commit/0738bc4b21c3133bb9de33de95df7d28ce803a73
(2) https://github.com/instaclustr/instaclustr-commons/blob/20cbd7625bc6c4c1a6693c5bd692aa06b807991a/src/main/java/com/instaclustr/kubernetes/KubernetesHelper.java#L24
(3) https://github.com/instaclustr/cassandra-sidecar/blob/master/pom.xml#L85

basically I set -Dpretend.not.running.in.kubernetes=true right?

pretty much


Chipyard-Standalone Testing with Config AXI4TestConfig00

command: make SUB_PROJECT=constellation BINARY=none CONFIG=AXI4TestConfig00 run-binary-debug
simulator: verilator
error log:
Exception in thread "main" java.lang.reflect.InvocationTargetException
at ... ()
at chipyard.stage.phases.PreElaboration.$anonfun$transform$1(PreElaboration.scala:35)
at ... ()
at ... (Stack trace trimmed to user code only. Rerun with --full-stacktrace to see the full stack trace)
Caused by: java.lang.UnsupportedOperationException: empty.max
I can pass the config Testconfig00 but fail with AXI/Tilelink config with error above.

Try make SUB_PROJECT=constellation BINARY=none CONFIG=AXI4TestConfig00 run-binary-debug MODEL=AXI4TestHarness

Thanks, it works


Copy url to clipboard

This is an idea I had, let me know what you think.
I love that now copies the address to my clipboard, and as I use serve a lot to quickly share a folder, I would love to have that feature here. Also, with the random port feature in the last version, I find this way easier to work with (cause before I would be always visiting :3000)

That's a really great idea, thanks!


InvalidCharacterError in /

Error in NPMGraph
InvalidCharacterError in /
Failed to execute 'btoa' on 'Window': The string to be encoded contains characters outside of the Latin1 range.
View on Bugsnag
Stacktrace
js/ModulePane.tsx:209 - Xn

View full stacktrace
Created by Robert Kieffer via Bugsnag

Just did a big code refactor... no idea if this is still a bug.  Will reopen if appropriate


BUG: #12624 where Panel.fillna() ignores inplace=True

[x] closes #12624
[x] tests added / passed
[x] passes git diff upstream/master | flake8 --diff
[x] whatsnew entry

Fixes #12624
Author: Pedro M Duarte<EMAIL_ADDRESS>

xref #12633

duped in #12633
thanks!

Thanks for the feedback, Jeff! I wanted to get home to fix it but seems like it has been taken care of.  Will look for another easy one I can try to help with.

@PedroMDuarte np. this actually happens pretty rarely when 2 people are working on the same issue. In any event lots of issues to try for!


Need to bump iohub version as there are issues to get info at position level

I was trying to use iohub info -v /hpc/projects/comp.micro/mantis/2023_08_09_HEK_PCNA_H2B/00-zarr_iohub_010dev4/test_convertscale.zarr and noticed this after pip install -e . the main branch of recorder. I think iohub #171 and #175 need to get merged first according to @ziw-liu.
This datset can be opened with iohub in Python code:

>>> from iohub import open_ome_zarr
>>> dataset = open_ome_zarr('/hpc/projects/comp.micro/mantis/2023_08_09_HEK_PCNA_H2B/00-zarr_iohub_010dev4/test_convertscale.zarr', mode='r')
(pyplay) [eduardo.hirata@gpu-sm01-08 00-zarr_iohub_010dev4]$ iohub info -v ./test_convertscale.zarr/0/0/0
Reading file:    /hpc/projects/comp.micro/mantis/2023_08_09_HEK_PCNA_H2B/00-zarr_iohub_010dev4/test_convertscale.zarr/0/0/0
Traceback (most recent call last):
  File "/hpc/mydata/eduardo.hirata/.conda/envs/pyplay/bin/iohub", line 8, in <module>
    sys.exit(cli())
  File "/hpc/mydata/eduardo.hirata/.conda/envs/pyplay/lib/python3.10/site-packages/click/core.py", line 1130, in __call__
    return self.main(*args, **kwargs)
  File "/hpc/mydata/eduardo.hirata/.conda/envs/pyplay/lib/python3.10/site-packages/click/core.py", line 1055, in main
    rv = self.invoke(ctx)
  File "/hpc/mydata/eduardo.hirata/.conda/envs/pyplay/lib/python3.10/site-packages/click/core.py", line 1657, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/hpc/mydata/eduardo.hirata/.conda/envs/pyplay/lib/python3.10/site-packages/click/core.py", line 1404, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/hpc/mydata/eduardo.hirata/.conda/envs/pyplay/lib/python3.10/site-packages/click/core.py", line 760, in invoke
    return __callback(*args, **kwargs)
  File "/hpc/mydata/eduardo.hirata/repos/iohub/iohub/cli/cli.py", line 43, in info
    print_info(file, verbose=verbose)
  File "/hpc/mydata/eduardo.hirata/repos/iohub/iohub/reader.py", line 310, in print_info
    f"Positions:\t {len(list(reader.positions()))}",
AttributeError: 'Position' object has no attribute 'positions'

Thanks for documenting


Failing test in the nargo crate

Description
Aim
Run nargo tests.
Expected behavior
All tests should pass.
Bug
Test fails with the following message
thread 'tests::noir_integration' panicked at 'range end index 322560156 out of range for slice of length 3585470', library/core/src/slice/index.rs:73:5
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

failures:
    tests::noir_integration

test result: FAILED. 0 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out; finished in 5.37s

To reproduce
This is assuming #401 is fixed.

Clone the repo.
cd crates/nargo.
cargo t

Environment
I'm using this repo's main branch.

OS: macOS Monterey 12.6

Can you retest this on latest with a fresh clone? These tests are automatically tested an CI and I just verified they pass for me locally as well. on an M1, macOS 13.0.

Closing this because this test does not fail when running the workspace's tests in the CI.


Fix error caused by proj4 6.0

As discussed in #22, version 6.0 of proj4 causes an error. Need to identify what changed between 5.2 and 6.0 and fix upstream in lmatools.
  File "examples/grid/make_GLM_grids.py", line 301, in <module>
    gridder(glm_filenames, start_time, end_time, **grid_kwargs)
  File "/data/probsevere/ancillary/miniconda3/envs/glmval/lib/python3.6/site-packages/glmtools-0.1.dev0-py3.6.egg/glmtools/grid/make_grids.py", line 826, in grid_GLM_flashes
    outputs = list(map(this_proc_each_grid, subgrids))
  File "/data/probsevere/ancillary/miniconda3/envs/glmval/lib/python3.6/site-packages/glmtools-0.1.dev0-py3.6.egg/glmtools/grid/make_grids.py", line 890, in proc_each_grid
    gridder.process_flashes(glm, **process_flash_kwargs_ij)
  File "/data/probsevere/ancillary/miniconda3/envs/glmval/lib/python3.6/site-packages/glmtools-0.1.dev0-py3.6.egg/glmtools/grid/make_grids.py", line 394, in process_flashes
    nadir_lon=nadir_lon)
  File "/data/probsevere/ancillary/miniconda3/envs/glmval/lib/python3.6/site-packages/glmtools-0.1.dev0-py3.6.egg/glmtools/io/mimic_lma.py", line 109, in read_flashes
    results = list(map(chunk_func,flash_chunks))
  File "/data/probsevere/ancillary/miniconda3/envs/glmval/lib/python3.6/site-packages/glmtools-0.1.dev0-py3.6.egg/glmtools/io/mimic_lma.py", line 162, in fast_fixed_grid_read_chunk
    np.zeros_like(flash_data.flash_x.data)))
  File "/data/probsevere/ancillary/miniconda3/envs/glmval/lib/python3.6/site-packages/lmatools/coordinateSystems.py", line 210, in toECEF
    return proj4.transform(self.fixedgrid, self.ECEFxyz, X, Y, Z)
  File "/data/probsevere/ancillary/miniconda3/envs/glmval/lib/python3.6/site-packages/pyproj/transformer.py", line 367, in transform
    xx=x, yy=y, zz=z, tt=tt, radians=radians, errcheck=errcheck
  File "/data/probsevere/ancillary/miniconda3/envs/glmval/lib/python3.6/site-packages/pyproj/transformer.py", line 180, in transform
    inx, iny, inz=inz, intime=intime, radians=radians, errcheck=errcheck
  File "pyproj/_transformer.pyx", line 107, in pyproj._transformer._Transformer._transform
pyproj.exceptions.ProjError: x,y,z, and time must be same size

There have been some additional changes in pyproj since this bug report in the section where the time size check was added. This commit seems to substantially change the logic.
pyproj 2.0.2 does not have _transformer.pyx; it first appeared in 2.1. The time check did not appear until 2.2.
This conda environment, with pyproj-2.2.2 and proj4-6.1.1 fails with the error above, using glmtools and lmatools on the isatss branch. pyproj <2.2 did not fail.
blosc                     1.17.1               h4a8c4bd_0    conda-forge
bzip2                     1.0.8                h0b31af3_2    conda-forge
ca-certificates           2019.11.28           hecc5488_0    conda-forge
certifi                   2019.11.28               py36_0    conda-forge
cftime                    <IP_ADDRESS>          py36h3b54f70_0    conda-forge
curl                      7.68.0               h8754def_0    conda-forge
cycler                    0.10.0                     py_2    conda-forge
freetype                  2.10.0               h24853df_1    conda-forge
glmtools                  0.1.dev0                  dev_0    <develop>
hdf4                      4.2.13            h84186c3_1003    conda-forge
hdf5                      1.10.5          nompi_h3e39495_1104    conda-forge
jpeg                      9c                h1de35cc_1001    conda-forge
kiwisolver                1.1.0            py36ha1b3eb9_0    conda-forge
krb5                      1.16.4               h1752a42_0    conda-forge
libblas                   3.8.0               14_openblas    conda-forge
libcblas                  3.8.0               14_openblas    conda-forge
libcurl                   7.68.0               h709d2b2_0    conda-forge
libcxx                    9.0.1                         1    conda-forge
libedit                   3.1.20170329      hcfe32e1_1001    conda-forge
libffi                    3.2.1             h6de7cb9_1006    conda-forge
libgfortran               4.0.0                         2    conda-forge
liblapack                 3.8.0               14_openblas    conda-forge
libnetcdf                 4.7.3           nompi_hda4e5f1_101    conda-forge
libopenblas               0.3.7                h3d69b6c_7    conda-forge
libpng                    1.6.37               h2573ce8_0    conda-forge
libssh2                   1.8.2                hcdc9a53_2    conda-forge
llvm-openmp               9.0.1                h28b9765_2    conda-forge
lmatools                  0.6a0                    pypi_0    pypi
matplotlib                3.1.3                    py36_0    conda-forge
matplotlib-base           3.1.3            py36h11da6c2_0    conda-forge
mock                      3.0.5                    py36_0    conda-forge
ncurses                   6.1               h0a44026_1002    conda-forge
netcdf4                   1.5.3           nompi_py36hcf2264a_102    conda-forge
numexpr                   2.7.1            py36h4f17bb1_0    conda-forge
numpy                     1.18.1           py36hde6bac1_0    conda-forge
openssl                   1.1.1d               h0b31af3_0    conda-forge
pandas                    1.0.1            py36h4f17bb1_0    conda-forge
pip                       20.0.2                     py_2    conda-forge
proj4                     6.1.1                hca663eb_1    conda-forge
pyclipper                 1.1.0.post1      py36h4a8c4bd_0    conda-forge
pyparsing                 2.4.6                      py_0    conda-forge
pyproj                    2.2.2            py36h9bb365a_0    conda-forge
pytables                  3.6.1            py36h6f8395a_1    conda-forge
python                    3.6.7             h4285619_1006    conda-forge
python-dateutil           2.8.1                      py_0    conda-forge
pytz                      2019.3                     py_0    conda-forge
readline                  8.0                  hcfe32e1_0    conda-forge
scipy                     1.4.1            py36h82752d6_0    conda-forge
setuptools                45.2.0                   py36_0    conda-forge
six                       1.14.0                   py36_0    conda-forge
sqlite                    3.30.1               h93121df_0    conda-forge
stormdrain                0.1                      pypi_0    pypi
tk                        8.6.10               hbbe82c9_0    conda-forge
tornado                   6.0.3            py36h0b31af3_4    conda-forge
wheel                     0.34.2                     py_1    conda-forge
xarray                    0.15.0                     py_0    conda-forge
xz                        5.2.4             h1de35cc_1001    conda-forge
zlib                      1.2.11            h0b31af3_1006    conda-forge

Updating to proj2.4.2 and proj 6.3.0 does not resolve the problem. Hmm...

glmtools@ugf-newgrid with lmatools@master (from today) fixes the problem, while glmtools@isatss and lmtools@master does have the problem. Seems like something was fixed in ugf-newgrid that unknowingly resolved this issue?

Looking at the traceback, the data structures in glmtools@ugf-newgrid that changed from glmtools@isatss had to have been (fl_events, fl_flashes) in mimic_lma.py. Those come from the _fake_lma_events_from_split_glm_lutevents and _fake_lma_from_glm_lutflashes functions, which definitely shows changes when comparing the branches. Something in the change to those data structures seems to have helped, though I confess to not knowing what that specific change was.

Given the eventual move to ugf-newgrid in #30 for all users, I'm inclined to consider this issue resolved.

With the fix for lmatools#29 in lmatools#28, I think I now understand why the above changes to glmtools fixed the issue. The newgrid-faster branch removed a bunch of extraneous coord transforms, and so probably simply stopped hitting the code in lmatools.coordinateTransforms that was sensitive to zero-length or scalar arrays.


Top level imports in module declaration files

Some days ago I posted this question in StackOverflow and realized that I was having an issue with top level imports in a module declaration file.
Let me summarize the problem:
Consider two modules Foo and Bar. The latter extends the first. We are writing the declaration files and tests for both to ideally have them in DefinitelyTyped, hence using their tests.
// /foo/foo.d.ts
declare module 'foo' {
    export class Foo {
        public constructor()
        // ...methods
    }

    const foo: Foo;

    export default foo;
}

// /bar/bar.d.ts
/// <reference path="../foo/foo.d.ts"/>

import {
  Foo
} from 'foo';

declare module 'bar' {
  export class Bar extends Foo {
    public constructor();
    // more methods
  }
}

// /bar/bar-tests.ts
/// <reference path="../foo/foo.d.ts"/>
/// <reference path="./bar.d.ts"/>

import foo, {
  Foo
} from 'foo';

import {
  Bar
} from 'bar';

namespace TestBar {
  {
    let result: Foo;
    result = foo;
  }

  {
    let result: Foo;
    result = new Bar();
  }
}

With this setup, bar.d.ts and bar-tests.ts compilation was failing with:

/bar/bar-tests.ts: error TS2307: Cannot find module 'bar'.
/bar/bar.d.ts: error TS2664: Invalid module name in augmentation, module 'bar' cannot be found.

And the solution for it was to put the import statement inside declare module 'bar':
// /bar/bar.d.ts
/// <reference path="../foo/foo.d.ts"/>

declare module 'bar' {
  import {
    Foo
  } from 'foo';

  export class Bar extends Foo {
    public constructor();
    // more methods
  }
}

After fixing it I came to wonder, is there any case in which a top level import is allowed within a file declaring a module? In case there is not, I'd suggest adding a warning or error regarding this.

After fixing it I came to wonder, is there any case in which a top level import is allowed within a file declaring a module?

Module augmentation. please see http://www.typescriptlang.org/docs/handbook/declaration-merging.html#module-augmentation for more details.

@mhegazy Could you provide more details on how can I use one top level import for multiple declared modules?
declare module 'a' {
    import { Component } from 'react'
}

declare module 'a/b' {
    import { Component } from 'react'
}

running dtslint on this declaration results in:

no-duplicate-imports             Multiple imports from 'react' can be combined into one.

looks like a dtslint issue to me.

@mhegazy Thanks! https://github.com/Microsoft/dtslint/issues/79


Documentations: Naming convention - 33

To ease the code reading, it will be better if we use the accepted convention. It certainly will help reader differentiate between function, class, constant, etc. Read below
https://realpython.com/python-pep8/#naming-conventions

function done.
Left:
variable
constant

done.


compilerOptions css does not bundle external css files

If I set compilerOptions.css to true (or `inject with Svelte 4), it still generates a CSS file and doesn't include it in the Javascript file.
To Reproduce
Steps to reproduce the behavior:
Import a css file into a svelte file
Expected behavior
The CSS is included into the JS and get's injected
Environment:

esbuild-svelte version: 0.7.3
esbuild version: 0.18.10
svelte-preprocess: 5.0.4

I can replicate this, but there is a bit of nuance as follows (all with css: "injected"):

Using @import "./test.css"; in component style results in the output js file still including the import statement but not copying the css file over
Using import "./test.css"; in the component script results in the test.css file being copied over but no import call from the component css
Using both @import and import results in a functioning component, with the imported css in an external file

None of these are exactly what you are looking for. Since Svelte deals with the css -> css-in-js transformation internally, there is limited ability for a bundler to interfere. I'll continue to think about possible solutions.
Since I see you are using svelte-preprocess, it might be worth looking into their sourcing solution https://github.com/sveltejs/svelte-preprocess#external-files


Remove allow_failures on Travis CI Python 3 tests

With #197 merged, the Python 3 crucial tests now pass in Travis CI so let's lock that criteria into all future PRs.

Thanks.


How to get the url of the from a collection of tiles after annotation.

I have a whole slide image. It is being chopped into a collection of tiles with specific size. I am using openseadragon to load all the tile images. I am also able to annotate region of interest. I need a way to store the image url of the region which I annotate.

Are you saying you want to be able to export a specific sub-view of your slide after it's been annotated? Or are you saying you want to be able to store the annotation data and positioning information so the user can come back to it later?
Also, what annotation system are you using?

Hi thanks for you're reply, I need a way to get the specific tile URL from the entire collection of Deep Zoom Images. Currently I am able to mark the region of interest and store the coordinates.I also want to store the specific tile image url. Is there a way where I can store the tile URL?

You might be better off exporting the current view than trying to use a specific tile. For instance, what if the annotated area is right on the edge between two tiles? Which tile would you choose?
To export the current view, you should be able to do view.drawer.canvas.toDataURL() and store the result or convert it into an image file to save.
As for figuring out which actual tiles you're looking at, OSD doesn't really have a mechanism for that. You can use debugMode: true in the viewer options to get a sense for how the tiles are laid out. You can also get the TiledImage (e.g. var tiledImage = viewer.world.getItemAt(0) and look through its array of currently visible tiles, lastDrawn. You could pick whichever one takes up the most screen space, for instance.
I hope these ideas help!


Treat Pipfile.lock as a binary file within git

Related to https://github.com/AbletonAppDev/devtools/issues/1466, ping @AbletonDevTools/gotham-city

LGTM :+1:


[Test] Remove Auth0 service dependency from all unit tests

Description
Auth0 service dependency in TokenOauth2AuthenticatedProducerConsumerTest was removed in #20465.
It turns out that there is an Auth0 service dependency also in these 2 locations:
https://github.com/apache/pulsar/blob/d565c953a7deab1ea93949bfefa44477e51e417f/pulsar-proxy/src/test/java/org/apache/pulsar/proxy/server/ProxyTlsTestWithAuth.java#L67-L70
https://github.com/apache/pulsar/blob/82237d3684fe506bcb6426b3b23f413422e6e4fb/pulsar-testclient/src/test/java/org/apache/pulsar/testclient/Oauth2PerformanceTransactionTest.java#L87-L89
These should also be covered.
An additional detail is that it would be better to change the OAuth2 audience claim https://dev-kt-aa9ne.us.auth0.com/api/v2/ in TokenOauth2AuthenticatedProducerConsumerTest during this change since that could cause confusion for future maintainers.
Implementation hints
It's possible to share test classes via pulsar-broker test-jar dependency:
        <dependency>
          <groupId>${project.groupId}</groupId>
          <artifactId>pulsar-broker</artifactId>
          <version>${project.version}</version>
          <scope>test</scope>
          <type>test-jar</type>
        </dependency>

This is already specified in pulsar-proxy/pom.xml and pulsar-testclient/pom.xml
It would be possible to extract some test classes from TokenOauth2AuthenticatedProducerConsumerTest for Wiremocking OAuth and put the classes under some package in pulsar-broker/src/test/java/org/apache/pulsar . This would be a way to reduce code duplication across tests where similar logic is needed.

Great points @lhotari. I can follow up on this tomorrow.


chore(main): release core-js 1.5.14-experimental

:robot: I have created a release beep boop
1.5.14-experimental (2024-11-13)
🧹 Chore

release main (f9555bc)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

core-js-v1.5.14-experimental
:sunflower:


Configurable "Minimum Window Size" check before managing a new window

I've had some success setting up rules to ignore alerts, notifications or "sub-windows" spawned by apps but sometimes the names are tricky or too dynamic to write rules for. It's usually not a big deal to quickly "unmanage" these windows but it would be nice to have a configurable minimum size that a window has to be greater-than or equal to before wwm grabs it.
A good example is when copying a large file to a drive, I'll usually end up with a tile dedicated to a progress bar I don't really want to actively watch. Not sure if this is a separate issue, but when that happens I sometimes can't kill the tile and have to use task manger to close it, but that just might be that the managing aspect of wwm forces the window to behave differently than it was designed?

Added min_width and min_height.


Slack

Merging branches slack and master

Deploy preview for fcccolumbus processing.
Built with commit c56b21c92597126136295459944ba8f9c646ecdb
https://app.netlify.com/sites/fcccolumbus/deploys/5a77a9040b79b7581af99f3a


add IMMEDIATE refresh policy

Description
[Describe what this change achieves]
Issues Resolved
[List any issues this PR will resolve]
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Should we also add this for the ml-config index?


Added Changelog for Remrem generate

Coverage remained the same at 60.0% when pulling 2d563ecbfa36228902b7d39e35ac74083daca29d on SantoshNC68:changelog into ff5653c87f70135764f81256bf999c61d1d7550e on Ericsson:master.


Clear button is not working with onSelect date change.

Hi,
In Datepicker component, we can use isClearable  property to clear the date input.
However, if i use onSelect property rather than onChange, then the clear button is not working.
Could anyone sugggest some other way to do it?
Thanks in advance!

Thanks for the update. I somehow missed to mention that the issue got resolved.  I used a combination of onChange & onSelect method to do the business logic.
Thanks anyways. :)
Best,
Rajat.


How to extend a typedef parameter in JSDOC?

Description: http://stackoverflow.com/questions/36737921/how-to-extend-a-typedef-parameter-in-jsdoc

Anybody knows correct way to extend typedefs?

looks like @augments (@extends) doesn't work

Wanted to know this myself, and tried the follwing, which works for IntelliJ intellisense:
/**
 * @typedef {Object} Store
 * @property {function(): Rx.Observable.<OBJ[]>} getAll
 * @property {function(DATA): Rx.Observable.<OBJ>} create
 * @template OBJ, DATA
 */

/**
 * @typedef {Store} MeetingStore
 * @property {function(DATA): Rx.Observable.<OBJ>} update
 * @template OBJ, DATA
 */

Has anyone found a solution for this, or is it still not supported?
@dietergeerts did you have to do anything special to get that working for IntelliJ intellisense? I implemented the same pattern but it doesn't work for VS Code intellisense unfortunately - it just shows the original base type, not the base type with the new field(s) merged in

Yes, I agree. This is something I really would like as it'd make my life 9000% easier.

@MatthewHerbst We also have devs in our team that use VS Code, and there we see that it lacks in intellisense for jsdocs compared with IntelliJ/WebStorm, especially in these cases. Even WebStorm doesn't always correctly show everything, depending on the number of extends etc....
What we do is first play with the docblocks to get it correctly working in WebStorm, and then the VSCode guys pray it also works there. Mongoose Models for example are a very hard thing to document, but we found the 'perfect' solution for it after a lot of trial and error.....

Intersection type works great in most cases, but what about when your base type defines a required prop, but your child type makes it optional?
/**
 * @typedef {Object} Base
 * @prop {string} activeId
 */

/**
 * @typedef {Object} Extra
 * @prop {string} [activeId]
 */

// this will still give "activeId missing" errors in `Composed` component:
/** @type {Base & Extra} Composed */

I've also tried this:
/**
 * @typedef {Base} Composed
 * @prop {string} [activeId]
 */

@nemoDreamer , from a functional view, what you are doing just makes no sense. Composed is both Base and Extra, where one requires activeId to be there, so that means it is required....
For extending typedefs, I know do the following, which works better in WebStorm:
/**
 * @typedef {IBase,IComposed} Composed
 */

/**
 * @typedef {IComposed}
 * @property {string} activeId
 */

If extending a typedef like the first block, you can't add props to the same block, otherwise it doesn't work. In some cases, this still isn't completely fail save, but it's the best we found up until now.

@nemoDreamer, I believe that with type intersections where one object has a required type that another has it optional, the former wins out. The only way around this would be to define another type without the required property and another type with optional properties then combining them:
/**
 * @typedef {Object} Person
 * @prop {string} name
 * @prop {number} age
 */
/**
 * @typedef {Object} Job
 * @prop {string} [job]
 */

/**
 * @typedef {Person & Job} Bozo
 */

/**
 * @type {Bozo}
 */
const bozo1 = {
  name: 'Bozo the Clown',
  age: 50,
  job: 'clown'
}
// or:
const bozo2 = {
  name: 'Bozo the Clown',
  age: 50
}

Not sure if this is related, but intellisense doesn't seem to be showing an Object typedef as shown below.

In this screenshiot, I'd expect SearchOptions to show the properties.

@GioLogist, that looks right to me. I would expect it to show anything other that what the type is for that parameter, in this case, SearchOptions. Are you in VSCode or what editor? If you're using VSCode then you can add a configuration file to turn on live type checking, which will give you even more type safety. For VSCode, in your project's root create a folder named .vscode (notice the leading dot, it's supposed to be invisible). Inside that create a file settings.json. In that put the following:
{
  "javascript.implicitProjectConfig.checkJs": true
}

And here's what happen's with your code and this setting. Notice how getSearchTerms has red squiggle underlining, indicating something is wrong. And hovering you get the reason, missing parameters:

If we provide the arguments as defined in the JSDoc types, everybody is happy and on hover we can see what the type of the argument is:

However, if we screw up and use the wrong type in our parameters, such as giving where a number instead of a string, we are informed about the error:

@rbiggs Interesting! Thanks for the insightful follow up! So I guess my question here is, there's no setting that can be enabled that will show the expected properties for that object?
In the original SO post I found, OP suggested he expected something along the lines of this screenshot. Which is what I too would expect as well.

I doubt it. You see, Intellisense is trying to show a call signature for the function. It's a common thing for intellisense to do. It just shows the types for the call signature. What if one of the parameters was an object type that had two dozen properties? That gets really hard to show as well as to grok.
Now if you wanted to organize your code a bit. You could have the getSearchTerms in one file with its type definition. Then import it and its type definition into another file where you use it. Here the source file:

Then the file we import it into:

In the file where we import the function, we can right click on it and choose peek definition:

This will give us the following popup, where we can see the original source definition for this function, as well as its type definition:

We can also hover over the imported type and see the type structure, which is more what you were looking for. This always works like this for imported types:

What if one of the parameters was an object type that had two dozen properties? That gets really hard to show as well as to grok.

Good point.

Now if you wanted to organize your code a bit. You could have the getSearchTerms in one file with its type definition. Then import it and its type definition into another file where you use it. Here the source file:

In the context of a library, I don't think the general user would import type definitions in order to get this benefit. Although, I can see the value for local dev. And more than anything, I learned something new today 🤓 Thanks @rbiggs !

Yup, but peek definition will show  you a popup of any function/object that was imported from a module, and go to definition will take you directly to the definition in the source module. Besides, showing only type information on hover, while useful, is secondary to really good descriptions. TypeScript's Intellisense is so good because it provides a lot more than just type information. It also provides detail descriptions based on MDN documentation. You can spice things up by using the @exmple tag to show how to use the code.
Here's an example of that in an NPM module that I published:

And scrolling down you can see the full @example and the JSDoc types at the end:

And here's an example of a complex type consisting of a main type and a subtype. State has an items property which is Item[]. On hover we can see what Item type consists of. But if we try to use it we discover that it has only two properties key: number and value: string. Trying to use any other property will give us a warning. So through Intellisense and good JSDoc types everything does get exposed to the end user through Intellisense or discoverability.

By the way, these same issues with types in Intellisense with JSDoc comments also apply to TypeScript types and Intellisense. It's the way Intellisense works. Now a way to get around this would be to enable the ability to drill down into types from the Intellisense popup, maybe by right clicking on a type in the popup. But that would probably introduce a level of complexity to the current Intellisense implementation that the VSCode team would not want to consider it. Kind of like introducing type inception, down a rabbit hole.

Extremely useful stuff here @rbiggs ! I see you're in Reno, happy to get you a beer next time i'm in Tahoe (pretty often), if you're up for it 🤘🏻

Now a way to get around this would be to enable the ability to drill down into types from the Intellisense popup, maybe by right clicking on a type in the popup.

Really like this idea. Funny enough, I tried ctr+clicking the type from the popup originally, which is what led me here.

Woohoo! Join us at BeerJS in Reno: https://github.com/beerjs/reno. This December is quick talks. I'll be doing a whirlwind intro to the Elm Architecture for React. You might already know Jordan
Papaleo, who used to run the JavaScript Meetup in Tahoe. ;-)
Oh yeah, control clicking stuff in VSCode can take you to unexpected places, he he.

Woohoo! Join us at BeerJS in Reno: https://github.com/beerjs/reno. This December is quick talks. I'll be doing a whirlwind intro to the Elm Architecture for React. You might already know Jordan
Papaleo, who used to run the JavaScript Meetup in Tahoe. ;-)
Oh yeah, control clicking stuff in VSCode can take you to unexpected places, he he.

@nicoespeon Which version of jsdoc are you using? I get
ERROR: Unable to parse a tag's type expression for source file
Invalid type expression "testBase & testSubType": Expected "|" but "&" found.

Take a look at this plugin:
https://github.com/chriseaton/jsdoc-plugin-intersection

Not sure what you'e referring to as a problem. Can you provide some code?

Sorry, let me rephrase the whole thing:
@nicoespeon provided (half) a solution with the intersection type and this example snippet:
/**
 * @typedef {Object} ChildType
 * @property {String} childProp
 *
 * @typedef {Base & ChildType} Child
 */

The problem is that this syntax is not (and most likely will never be) recognized by jsdoc, hence the error mentioned by @henhal (when he runs the generation):
ERROR: Unable to parse a tag's type expression for source file
Invalid type expression "testBase & testSubType": Expected "|" but "&" found.

But @chriseaton made this plugin and it works like a charm (I tested it) : it « Converts TypeScript intersection types (joined with an "&") to a jsDoc type union "|" allowing the file to be processed downstream. This allows you to use the amperstand "&" in your code. »
So when using this plugin, one can use the intersection syntax so that one has the right completion in VSCode (for example) and still has the ability to generate the doc as usual.

/**
 * @typedef {Object} ChildType
 * @property {String} childProp
 *
 * @typedef {Base & ChildType} Child
 */

Can you try the following (which does work for our use-case very well, even our IDE can work with it:
/**
 * @typedef {Object} ChildType
 * @property {string} childProp
 */
/**
 * @typedef {Base, ChildType} Child
 */

Notice that they need to be in their own separate docblock to have this working.

Unfortunately, my editor (VS Code) only takes the first type def:

Trackback to #1285 -- current stance is that intersection types won't be supported but I asked them to reconsider.  Maybe this is a helpful use-case in support of that?

It works in WebStorm:

And this is how I get it works in VSCode:

And using the | also works in WebStorm apparently:

So the | symbol appears to be the way to go to have it working in both WebStorm and VSCode.

Those are two different things -- they both do what it says on the tin.  Intersection type (A & B) is a type containing the properties common to both A and B; union type (A | B) is all the properties in A plus all the properties in B.

Those are two different things -- they both do what it says on the tin. Intersection type (A & B) is a type containing the properties common to both A and B; union type (A | B) is all the properties in A plus all the properties in B.

I know they are different, but your explanation of both are not what the TS docs, nor the JSDoc docs are saying:

https://www.typescriptlang.org/docs/handbook/advanced-types.html#intersection-types.
https://jsdoc.app/tags-type.html

So it is:

& means it will both be A and B, so all props of A and all props of B (This only exists in TS)
| means it will either be A or B, so OR it is A, OR it is B, but not both (This exists in both TS and JSDoc)

You're right, I didn't explain it well, probably because I haven't thought it all the way through myself.
With Intersection, it is known to be an A "and" a B, at the same time, while with a Union it's known to be A "or" B but you can't tell which without further checking.  My mental model of a Union is that you can access properties that are common to A and B, or you can make a runtime type check to narrow down which one you actually have.  That's why I say it has "all the properties", because it could have them at runtime.
When I say that the Intersection contains "properties common to both" I was specifically thinking of the way that Intersections can make possible types that otherwise can't exist.  I came to this issue because I currently use type DictionaryClass = {a(): string, b(): number} & {[k: string]: boolean} to describe a type whose a and b properties are functions but where any other property is a boolean.  Normally the index signature would make declaring a or b impossible, because they're not booleans, and that's why the merging behavior is so important.

@thw0rted , no prob. Thx for that example.

I found the best solution on here: https://stackoverflow.com/questions/36737921/how-to-extend-a-typedef-parameter-in-jsdoc
See the second answer, it suitable for jsdoc.

What I'd like to know is a very simple use case:
const utils = {
    "meta_chars": new RegExp('[\\^$.|?*+()[{]', 'g'),
    /** Escapes regexp meta characters
     *
     * @param {string} string A string to be quoted.
     * @returns {string} Quoted string.
     */
    "preg_quote": (string) => string.replace(utils.meta_chars, '\\$&'),
}

/** ???
 */
String.prototype.quote = (string) => utils.preg_quote(string);

How should I document this thing to see the hint in other places of the project?

Apparently still doesn't work.

/**
 * Base
 *
 * @typedef {Object} Base
 * @property {string} prop1
 * @property {string} prop2
 */

/**
 * Represents a local outbound.
 * @typedef {Base& {
 * 	prop1: 'value_case_1', // Override something in the Base type
 * 	prop2: string, // Unique property in the Child type
 * }} Child
 */

This works in VSCode.

8 years, still no official JSDoc solution.


Add aten::soft_margin_loss and its variants

soft_margin_loss
soft_margin_loss_backward

Close this PR because CUDA is not registered separately; it is a composite op.


Release automation

Proposed changes
As we noticed several times, generating the release, changelog is not always consistent nor accurate.
To face that this PR brings several features:

One click release
Changelog generation
Framework & Browsers versions
Works on master and other branches.

Lifecycle changed a bit:

Create draft release
Generate tag
Build and attach artifacts (template, docker image,  runner bundle)
Publish release

Types of changes

[ ] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Update (if none of the other choices apply)

Checklist

[ ] Lint and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)

Further comments
Examples:

https://github.com/FriggaHel/sauce-cypress-runner/releases
https://github.com/FriggaHel/sauce-cypress-runner/actions

@tianfeng92 @dpgraham Resetting review since lots of changes happened since first approbation.
to all: It's preferable to take a look to the final script more that the diff, it would be easier to understand the flow :)


expose currentReward as a function

closes: #10
Signed-off-by: Krasi Georgiev<EMAIL_ADDRESS>

anyone want to add a test for it before we merge it in?

I'm writing a test

This function now has a test in this PR


add a license statement to project

can you please add a license statement to your readme.md file.

I prefer MIT License. @andrew-w-ross what are you think?

@vslinko MIT all the way.

Closed by https://github.com/andrew-w-ross/typings-react-redux/commit/7350ae03b5e0b657d3d55a974fa74d1ca9092761


How to visualize the predicted fMRI signal by pycortex

I want to visualize the predicted ImageNet signal via PyCortex, could you share the souce code? I would deeply appreciate it if you would do that!

Hi, once you install pycortex (https://github.com/gallantlab/pycortex), you will have to install the fsaverage subject template from here.
https://figshare.com/articles/dataset/fsaverage_subject_for_pycortex/9916166/1
Then you can check out this notebook brain_visualization_pycortex.ipynb (that I just added to the repository) to visualize the predictions.
Hope this is helpful.

Hi, once you install pycortex (https://github.com/gallantlab/pycortex), you will have to install the fsaverage subject template from here.
https://figshare.com/articles/dataset/fsaverage_subject_for_pycortex/9916166/1
Then you can check out this notebook brain_visualization_pycortex.ipynb (that I just added to the repository) to visualize the predictions.
Hope this is helpful.

I'll try it! Thank you for your help!

btw，how to solve the background color issue?
My background color will change with the change of colorbar.
I have also checked my numpy arrary value, which is nan outside the ROI.

Looks good. Since the value for those vertices is nan the color is the color you have for the most negative value so if you change the color bar that also changes.

But why the quickshow API can present the right way?


:memo: add Polish translation

This PR adds Polish translation to the project.

Amazing ! Thanks for help :-)


Modifications for managing users assigned to the applications

Following are a few changes that need to be made for managing application users:

[ ] Currently, there is no way to delete a user added to an application. Provide the ability to delete the users from the interface developed as part of the task above.
[ ] Display the users assigned to an application on the edit application page. Also, provide the ability to add existing organiation users to the application form here. Currently, the only way to add the users is to add them through the + on the application list. The current user flow is not user-friendly and very confusing.

This is completed already


Feat/chart tooltip number format

Solves #575

👋 Thanks for creating a pull request! 🚀 Checkout the storybook we've created for it: angular-charts


Task 299

Schema Version downgrade and rename from jsonc to json.

Functionality already covered in PR #332.