add a new dataset

Hello, When I added a new dataset MI3DOR, the error" ValueError: The requested one is expected to belong to ['Digit5', 'VisDA17', 'CIFARSTL', 'Office31', 'DomainNet', 'OfficeHome', 'miniDomainNet', 'PACS', 'VLCS', 'FMoW', 'IWildCam', 'Camelyon17', 'CIFAR10C', 'CIFAR100C', 'DigitsDG', 'DigitSingle', 'OfficeHomeDG', 'CIFAR10', 'CIFAR100', 'SVHN', 'STL10'], but got [MI3DOR] (do you mean [CIFAR10]?)”. How to correctly add a new dataset? Thanks.

The code is based on the dassl library. There are some examples in the link of the library, and you can refer to these examples. By the way, you need to add @DATASET_REGISTRY.register() before the definition of the class to register your own dataset.


As an engineer, I would like to have big data support  in Vuu

Hadoop / Ignite
Discussion on
https://github.com/finos/vuu/issues/848
Large tables 10m - 10bn

https://github.com/finos/vuu/issues/989
https://github.com/finos/vuu/issues/1196


GPS data format matching

An error message appears when I run bag：
[ERROR] [1701932176.859127476]: Client [/lio_sam_mapOptmization] wants topic /gps/fix to have datatype/md5sum [nav_msgs/Odometry/cd5e73d190d741a2f92e81eda573aca7], but our version has [sensor_msgs/NavSatFix/2d3a8cd499b9b4a0249fb98fd05cfa48]. Dropping connection.
The error shows that the GPS data to be accepted does not match the GPS data type in the bag. How should I solve this problem?

in ros, a topic has a publisher and subscriber. In this topic exist one type of msg who is the same for pub and sub. So in your problem, the msg in your topic is "nav_msgs/Odometry" and the sub of that (the slam who is the sub) read and understand only "nav_msgs/Odometry".  The solution for that is maybe to change the topic (because you send GPS point in a topic for Odometrie). In the ReadMe for this slam it said "To enable the GPS function, change "gpsTopic" in "params.yaml" to "odometry/gps"." you test it ? If this solution don't work, you can create a node for read the "sensor_msgs/NavSatFix/" and translation it on "nav_msgs/Odometry".

Hi @Spirquel
"you can create a node for read the "sensor_msgs/NavSatFix/" and translation it on "nav_msgs/Odometry"."
what do I need to turn to? I use robot_localization's navsat_transform_node, but to use this, I need Odometry data, which LIO-SAM does not have.


No icon for tsx files in VS2013

We need to make changes to the project system in VS to support this, if there is another update we can try to add this, but for now going to close.


Interpreter: class comparison has incorrect result

Given code:
class P
end

class A < P
end

class Match(T)
  getter payload : T

  def initialize(@payload)
  end
end

m = Match(P.class).new(A)

puts m.payload
puts m.payload == A

Compiled mode result:
A
true

Interpreted mode result:
A
false

The interpreter should return true.

Reduced:
class P
end

class A < P
end

p = A.as(P.class)
puts p == A # true in compiled mode, false in interpreted mode


Add support for precompiled headers when using CMake.

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

With VS 2019 (16.5.0) using the built-in CMake version 3.16.19112601-MSVC_2, I'm getting a failure with the Visual C++ targets:
C:\PROGRA~2\MIB055~1\2019\ENTERP~1\VC\Tools\MSVC\1425~1.286\bin\HostX64\x64\cl.exe  /nologo /TP -DUNICODE -D_UNICODE -D_WIN32_WINNT=0x0601 -I..\..\..\Audio -I..\..\..\Src /DWIN32 /D_WINDOWS /Wall /GR /EHsc /MDd /Zi /Ob0 /Od /RTC1   /fp:fast /permissive- /Zc:__cplusplus /wd4365 /wd4710 /wd4820 /wd5039 /wd5045 -std:c++14 /Yu"pch.h" /showIncludes /FoCMakeFiles\xwbtool.dir\Audio\WAVFileReader.cpp.obj /FdCMakeFiles\xwbtool.dir\ /FS -c ..\..\..\Audio\WAVFileReader.cpp
D:\Microsoft\DirectXTK\Audio\WAVFileReader.cpp(13): fatal error C1083: Cannot open precompiled header file: 'pch.pch': No such file or directory

@walbourn I'm not sure how to do that... cmake is constant google search for me :-|

Looks like the easier solution is to use the new CMake 3.16 feature that directly supports pch

That was SO much easier... see this commit
Thanks again for your contribution!


💡[Feature]: Gender And Age Detection

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
To detect age and Gender
Use Case
Detecting Age and Gender
Benefits
N/A
Add ScreenShots
No response
Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

@sanjay-kv Can You Please assign me this Issue


[stable/drupal] Sidecar template pattern

See #4283
Example block for a values override file (in this example, someone is choosing to run memcached as a sidecar instead of stable/memcached):
helm install stable/drupal -f memcached-sidecar.yaml
sidecarContainers:
- name: memcached
  image: memcached:alpine
  command:
  - memcached
  - -m 64
  - -o modern
  - -v
  ports:
  - name: memcache
    containerPort: 11211
  livenessProbe:
    tcpSocket:
      port: memcache
    initialDelaySeconds: 30
    timeoutSeconds: 5
  readinessProbe:
    tcpSocket:
      port: memcache
    initialDelaySeconds: 5
    timeoutSeconds: 1

PS, let's discuss more at #4283 before merging. @unguiculus reminded me which PR we discussed, and it has additional options (for volumes and secrets), which I'll want to add here as well before this gets in.

I was looking at other PRs like this: https://github.com/kubernetes/charts/pull/4059/files
If the sidecar container required secrets, it is not clear to me how to create the corresponding secret object without having it created before hand.
I would use a secrets.yaml with a foreach that iterates between the secrets and creates several objects, each with their own unicity.

Closing because there may be other ways to solve this, and let's keep conversation about pod presets in #4283
But @javsalgar check out #4059 for your question


Provide HTTP example which works

The provided HTTP example doesn't work without disabling CORS. This can be very disconcerting for new users as immediately it looks as if Halogen's HTTP capacity doesn't work.

:+1: Should change the example to use a site supporting CORS so it works out of the box.

Try PureScript does use CORS.
Sent from my iPhone

On Jun 15, 2015, at 7:38 AM, John A. De Goes<EMAIL_ADDRESS>wrote:
Should change the example to use a site supporting CORS so it works out of the box.
—
Reply to this email directly or view it on GitHub.

It doesn't accept all domains though.
Sent from my iPhone

On 15 Jun 2015, at 16:46, Phil Freeman<EMAIL_ADDRESS>wrote:
Try PureScript does use CORS.
Sent from my iPhone

On Jun 15, 2015, at 7:38 AM, John A. De Goes<EMAIL_ADDRESS>wrote:
Should change the example to use a site supporting CORS so it works out of the box.
—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub.

Which domain doesn't work for you?

Localhost
Sent from my iPhone

On 15 Jun 2015, at 18:07, Phil Freeman<EMAIL_ADDRESS>wrote:
Which domain doesn't work for you?
—
Reply to this email directly or view it on GitHub.

You're running Try PureScript on localhost, or the example?
If I open the file from the filesystem in Chrome, and use the default try.purescript.org endpoint, everything works fine. CORS headers are enabled for try.purescript.org in nginx.
What browser are you using?

When running the halogen ajax example from the filesystem in chrome on windows, the origin is null and the server responds with a 403.
POST /compile/text HTTP/1.1
Host: try.purescript.org
Connection: keep-alive
Content-Length: 166
Pragma: no-cache
Cache-Control: no-cache
Origin: null
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.71 Safari/537.36
Content-Type: text/plain;charset=UTF-8
Accept: */*
Accept-Encoding: gzip, deflate
Accept-Language: en-US,en;q=0.8

We should probably just switch the example to use some public API that has Access-Control-Allow-Origin: *.

When I run the example with http-server, origin is localhost. Likewise the server gives a 403 response.
Origin:http://localhost:8080


Feature Request: Support for more Response Groups

Right now, there is very limited support for the "AlternateVersions" and "Variations" response groups. The API supports many response groups, and I would imagine that this package poorly supports many others as well. Based on a quick skim of the code, it seems like only "Large", and "BrowseNodeInfo" are explicitly supported. Response groups that happen to have elements that are shared by these two (ex "Medium" and "Small") will have limited support as well.
An alternate versions search will return an AmazonProduct object with None for almost all attributes and methods except for to_string(). I have been resorting to processing the xml myself using an lxml.etree.
This might be out of the scope of this project ("simple" is in the name), but it would be awfully nice to have this ability. Looking physical books is basically impossible using titles because Amazon always returns the kindle e-book if available, so looking at the "AlternativeVersions" is a necessity.
For AltenateVersions at least, returning a list of dictionaries of title, binding, ASIN values would be the logical thing. I imagine that "Variations" will be similar. I'm not sure if this is best done via a keyword argument (ie ResponseGroup="AltenateVersions") or a bunch of methods (ie api.search_alternate_versions()) though.

This should be closed as it's a repeat of #60.

@ThomasProctor, would you be interested in attempting the re-factor / becoming a core committer?

@yoavaviram, Hmm... I don't think I really have time to jump into the refactor now, and I can't imagine having it in the next 2-3 years.

@ThomasProctor i've added as a collaborator, feel free to jump in. I hope to have some time in the next weeks to fix the failing tests (and maybe find a better mechanism to prevent it breaking in the future).


Migrate hyperspace

This PR moves the Hyperspace monorepo into this monorepo.
To complete the migration, I made the following:

git subtree added the original repo.
checked that it would work with the same nixpkgs pinned in ngipkgs inputs.
extracted packages from original monorepo into by-name packages with the dream2nix V1 API (previous API is deprecated).
added installation checks for each individual package .

I have no experience with dream2nix, but I am asking myself whether package.nix and d2n-files/default.nix (per package) can be merged, so that we only have package.nix and even get rid of the d2n-files folder. That would be a lot leaner. I'd like to understand. Probably I should RTFM, but maybe you know and can tell me why the d2n-files/default.nix is required?

@lorenzleutgeb I simply started from the examples in the current d2n repo. The reason it's there is because there are only examples of "drea2nix monorepos". So I already generalized it to contain only a package.
I can still try to merge them further, it might still be possible. I just made this PR after a bunch of refactors that left this code in a functional and OK state. I'll also ask for single package examples upstream.
Worst case, I could extract away the current boilerplate in a function and add it to the scope.

@lorenzleutgeb with the help of @DavHau, this PR now makes it possible to add packages by-name and using dream2nix to evaluate them as modules.
In order to distinguish packages as modules from callPackage ones, the former need to be called module.nix inside it's named folder.

Awesome, looks much better!
The package names are missing version numbers. Is that intentional? Why?

nix flake show --json | jq -r '.packages."x86_64-linux"[].name' | sort

atomic-cli-0.34.5
atomic-server-0.34.5
autobase
corestore
flarum-1.8.0
gnunet-messenger-cli-0.1.1
hyperbeam
hyperblobs
hypercore
hyperswarm
lcrq
lcsync
libgnunetchat
librecast
nixos-system-server-23.11.20230919.8b5ab83
nixos-system-server-23.11.20230919.8b5ab83
nixos-system-test-flarum-23.11.20230919.8b5ab83
pretalx-2023.1.3
pretalx-2023.1.3
pretalx-frontend-2023.1.0
python3.10-euclid3-0.01
python3.10-kikit-1.3.0
python3.10-pcbnewTransition-0.3.4
python3.10-pretalx-downstream-1.1.5
python3.10-pretalx-media-ccc-de-1.1.1
python3.10-pretalx-pages-1.3.3
python3.10-pretalx-public-voting-1.3.0
python3.10-pretalx-venueless-1.3.0
python3.10-pybars3-0.9.7
python3.10-pymeta3-0.5.1
rosenpass-0.2.0
rosenpass-tools-0.2.0

Also I saw that you have version = "v" + # ..., i.e., version prefixed with 'v' in some of the modules. Again, this is unusual. Any particular reason?
And lastly, there's no meta information at all, it seems. Could you please add that?

@lorenzleutgeb We applied all of these suggestions, please have a look when you can.

We ended up moving the name and version but not much else; as you said, with this dream2nix it's a bit harder to enforce the order of the callPackage convention.

Regarding CI failures, I am slightly confused. Checks are green on e7be932, the last commit that actually has changes that are related to the PR. Checks fail on eb84483, the commit that "just" adds --debug --print-build-logs. The logs are very large (506MiB). The job is killed while it's compiling some Rust code. Probably because the logs are getting too big?! I don't think it's a timeout...
$ du -b log.txt
531484614       log.txt
$ head -n 6 log.txt
2023-10-25T13:44:51.0331804Z ##[group]Run nix flake check --debug --print-build-logs
2023-10-25T13:44:51.0332586Z nix flake check --debug --print-build-logs
2023-10-25T13:44:51.0379294Z shell: /usr/bin/bash -e {0}
2023-10-25T13:44:51.0379736Z env:
2023-10-25T13:44:51.0380281Z   MAGIC_NIX_CACHE_DAEMONDIR: /home/runner/work/_temp/magic-nix-cache-cMmTgQ
2023-10-25T13:44:51.0380970Z ##[endgroup]
$ tail -n 2 log.txt
2023-10-25T14:23:02.8720999Z rosenpass>    Compiling serde_derive v1.0.185
2023-10-25T14:23:20.1459141Z ##[error]The operation was canceled.

After many tries to figure out what was wrong with CI failures, I decided to split the individual packages into separate PRs.
It was quite puzzling that https://github.com/ngi-nix/ngipkgs/pull/82 consistently worked with any combination of 5 packages but ended up failing when adding the 6th.
I took the opportunity and applied the naming convention proposed in https://github.com/ngi-nix/ngipkgs/issues/74. This means, using dream2.nix  instead of using module.nix inside each by-name folder.
The list of PRs is:

#143
#144
#145
#146
#147
#148

I'll go ahead and start merging the separate PRs, since this one was only stalled because CI never got green.


Question: K8S HA setup

Hi,
is my understanding correct that Turing Pi Cluster defines only a single master node, and therefore this solution disqualifies for a HA setup of K8S.
Is this correct?
Regards
Thomas

The Turing Pi gives you a pool of Pi servers. You can set it up in any way you want, with one master, three masters, or more. I just set mine up with one since HA on the control plane wasn't a design goal I had.
The K3s Ansible project has an HA setup PR in the works, too: https://github.com/k3s-io/k3s-ansible/pull/97


Fixed bug related to getting solution when solver returns timeout

When the gurobi compute server reaches TimeLimit. it returns the OK flag, but may not have a solution. Fixed this by checking if termination condition is optimal before attempting to get the solution from the compute server.

Please fix the failing tests before we merge


fix: lowercase 'ID' in OpenAPI spec

Issue: https://github.com/moov-io/ach/issues/1086

Codecov Report

Merging #1087 (06df0ad) into master (4d3ddcb) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #1087   +/-   ##
=======================================
  Coverage   90.94%   90.94%
=======================================
  Files          68       68
  Lines        6392     6392
=======================================
  Hits         5813     5813
  Misses        340      340
  Partials      239      239


Legend Customization with RickshawGraph

please provide documentation as how we can customize legend to show more information

I'm currently looking a way to customize the legend too. Any updates for this?


<iframe> inside ShadowDOM will cause extension script hang

Platform: Chrome 94, Win 10 / macOS 11.4
Extension: Katalon Recorder (Selenium tests generator) <IP_ADDRESS>
One line description
If a page creates a Shadow DOM tree and then insert <iframe></iframe> into the tree, then this extension's content script will enter a dead loop and the whole page hangs.
Test steps
A simple test is: install Vimium C (https://github.com/gdh1995/vimium-c) and press / on a Google page. If without this extension, Vimium C should show a small input box at the bottom right corner and a user can type letters to search.
But with this enabled, a test page will hang (as reported in https://github.com/gdh1995/vimium-c/issues/457).
Buggy point
https://github.com/katalon-studio/katalon-recorder/blob/d118f95b2bdd126db824fa2c6b8b70461857a7cf/content/recorder.js#L89-L98
Here frames won't include child frames inside Shadow DOM trees, so currentWindow won't be updated, and then currentWindow !== window.top is always true.

Thank you for the report, we'll fix it and include it in the upcoming releases.

Any updates?

This issue is still occurring with Chrome extension 5.8.1 and my shadow dom that I am attempting to record does NOT have an iframe in it. In fact, it breaks the shadow dom causing the browser to freeze and having to force quit the entire browser without even trying to record. Had to turn off the extension to stop it from breaking the shadow dom. This is occurring on both Mac (Chrome v. 101) and Windows(Chrome v. 89) in either incognito or regular.

Hello, could you fix this in a next release?


Feature proposal: Daemon mode

This could ease performance issues due to suplemon being implemented in Python, without requiring a rewrite in C. One could run suplemon --daemon and connect using suplemonclient (like emacsclient). Also potential support for connection to a suplemon instance on another computer.

Do you mean the time it takes to load the app? On some slower servers I have sometimes noticed that I have to wait a couple of seconds for suplemon to start. But when I quit and start it again it loads instantly. I guess this is actually due to python and its libs being loaded into memory.
Other than the startup time I don't see very much benefit to daemonizing suplemon. It would be a major change to the entire architecture so it would be lots of work to do.

Are you sure this doesn't have to do with compiling the source and then caching it?

@lschumm let me know what kind of performance issues your experiencing.

Closing due to inactivity.


(Non-function value encountered for default slot. Prefer function slots for better performance. )Can you cancel this warning

If I write this in the entry file, there will be a warning if I change () =>
In this case, my component cannot be loaded, please give a solution or remove the warning message, do not want to see this warning message

Not for sure what warning you encountered.

Do you need to optimize this message?

Others say that this can be solved, but I need to optimize this root node to write in that way, but after optimizing in that way, my routing page can't be displayed properly

I'm not sure if this is the right information, so I need your help

Duplicate of https://github.com/vitejs/vite/issues/1044. Because the vite transform jsx by esbuild, some synax is not supported.You can use sfc  or switch to vue-cli as workaround for now.
I will discuss with other memebers, please wait some time for feedback.

Hello. Don't mind me. I'm just here to help others who are running into this problem while using vue3, jsx, with ESBuild. This is the first issue to come up in google.
This error happens because Vue requires a slightly different transform than what ESBuild has. But we can fix this by providing a small wrapper around Vue's h and use it as a shim in ESBuild's config.
import { h as vnode } from 'vue'

export const h = (tag, data, ...children) => {
  if (typeof tag === 'function') {
    return vnode(tag, data, ...children.map(child => () => child))
  }

  return vnode(tag, data, ...children)
}

In your ESBuild config make sure you're using you're injecting your shim.
{
    bundle: true,
    inject: ['./src/modules/vue-shim.js'], // <-- this is the one
    jsxFactory: 'h',
    nodePaths: ['src/modules'],
    sourcemap: true,
    write: false,
    define: {
      'process.env.NODE_ENV': `"${process.env.NODE_ENV}"`,
      '__VUE_OPTIONS_API__': true,
      '__VUE_PROD_DEVTOOLS__': false
    },
    loader: {
      '.js': 'jsx'
    }
  }

Sorry for jacking this thread 6 months later. It's just the one that comes up on Google. I hope this helps someone.


Need design pattern for when we have too many action buttons

I have noticed this coming up in various places. We try to display all actions as buttons but it gets too crowded, e.g. on a fiscal host page like this:

This also came up with expenses and will be coming up on the host dashboard too.
We need input from the designers. I suggest something like: 1 main action button for the most common one, with an "actions" dropdown next to it to access anything else.

This is being implemented in the new Collective page update.
It has a dedicated issue: #3640

This is done

This is done


glacier: Append random sequence to branch name to make it unique

Sometimes the user (me) will make a mistake (e.g. leave out
/rust-play/ from the URL) when invoking @rustbot glacier
that means the automatically-created PR has to be closed.
However, there was no way to try again, because the branch name
would conflict and triagebot would crash. Now, we append an
8-character random alphanumeric string to the branch name so that
the branch names are unique and you can try again.
This adds a dependency on rand, which is probably the most downloaded
crate all-time, but we already depended on it through other crates.
r? @Mark-Simulacrum

I'd prefer we use the API to delete the old branch or something like that instead.

Ideally that's what we'd do, but it's not necessarily easy to figure out when the branch should be deleted. We'd need to listen to the PR events and only delete it when the PR is closed or merged. I think it's better to just go with something simple for now so that it's not a pain if you make a typo when invoking the command.

I mean that we'd always delete it or "force push" or whatever to the branch? Like, I'd want repeated invocations to update the open PR ideally

Hmm... that seems like it might be confusing. I also think it would require significant changes to the current code, and I don't know octocrab etc. well enough to make those changes.

What about creating the file and the pull request as currently done if the branch was created successfully (i.e. it didn't exist), and just updating the file if the branch already exists? See https://docs.rs/octocrab/0.12.0/octocrab/repos/struct.RepoHandler.html#method.update_file

What about creating the file and the pull request as currently done if the branch was created successfully (i.e. it didn't exist), and just updating the file if the branch already exists? See https://docs.rs/octocrab/0.12.0/octocrab/repos/struct.RepoHandler.html#method.update_file

That could work, but probably triagebot should only do that if there's no PR open for that branch (i.e., the PR was closed). Otherwise there could be confusion if two people do @rustbot glacier with different MCVEs around the same time.

Otherwise there could be confusion if two people do @rustbot glacier with different MCVEs around the same time.

Didn't think of that, but what is the probability that it will happend ? Especially since only a limited number of people are allowed to issue the command ?
Which is better ? Having to close the PR to fix it or avoiding that potential confusion ?
What about duplicates PR for the same ICE ?

P.S. ok, definitely need to ignore commands in quoted text. I'll try to implement that

Otherwise there could be confusion if two people do @rustbot glacier with different MCVEs around the same time.

Didn't think of that, but what is the probability that it will happend ? Especially since only a limited number of people are allowed to issue the command ?
Which is better ? Having to close the PR to fix it or avoiding that potential confusion ?
What about duplicates PR for the same ICE ?

Personally, I think it would be best to start out by only updating the branch if there's no open PR, and then we can always lift that restriction in the future if it causes problems.

As you see fit. The question then is what to do when the a PR is open ? Emit a warning / error ? Or open a concurrent PR ?
I still think it's unlikely that two persons issue the command with different MCVEs but for same ICE / on the same issue. Anyway…

As you see fit. The question then is what to do when the a PR is open ? Emit a warning / error ? Or open a concurrent PR ?
I still think it's unlikely that two persons issue the command with different MCVEs but for same ICE / on the same issue. Anyway…

It's probably not a big deal. I guess I'm just thinking of if someone tried to spam the open PR, but it's probably unlikely.
So maybe updating the branch even if a PR is open is fine. Maybe @Mark-Simulacrum has thoughts on what makes sense here?

Spam is not something we're trying to solve too much.
I think either updating the branch in place or generating a new branch and updating that will both be fine. I think generally leaning towards one PR per invocation is probably better; PRs are relatively cheap and if need be could also be edited in place by reviewers.

It might be a little cleaner to associate the branch with a single (user, issue) pair and update that in place to provide an easy way to amend PRs, perhaps. But either way seems ok.

It might be a little cleaner to associate the branch with a single (user, issue) pair and update that in place to provide an easy way to amend PRs, perhaps. But either way seems ok.

That sounds like a good idea. E.g., if I used it on issue 123, the branch would be named triagebot-ice-camelid-123 or something like that. Then we wouldn't need to check if it's the same user because the branch name would do it for us.

Right. We'd still need the create if not exists & update logic, but hopefully that's not too hard to pull off.


Add  templates for new production configs

The proposal here is to create a new workflow allowing LST members to ask for a new production to be run through pull requests.
In this workflow, they open a new pull request following the provided template, the CI will check that the configuration is technically correct, we review that the proposal makes sense and launch the new production once the PR is accepted.
This will simplify the process, avoid mistakes in configs and introduce a better tracking of the requested official production, also allowing all analysers to see what configs and production are discussed or done.

Thanks a lot @vuillaut for this implementation.
How possible would be to compare (when doing the PR, so running an specific CI only for PRs), that makes a diff between the standard lstchain config file and the proposed one ?

Interesting! But we still launch it by hand if I understand correctly? Its "just" proposals, right?

Exactly. This way we will have a place to record the requested prods from people of the collab, and where other can have a look to check was already launched. Also, this will be another way to check that the configuration used is the correct one / desired by the users (lstchain config starts to get very big and with MANY parameters).

Let's implement this !


Provide a way to get notified when a request is timed out

Currently, when a request is timed out, users could get notified using:

Register callback using ServiceRequestContext.setRequestTimeoutHandler(callback).
But this is not recommended because it overrides the default behavior of the internal timeout task.
As like the Javadoc of setRequestTimeoutHandler() said, users should close a response manually.
Check the response cause usingctx.log().whenComplete().whenComplete((log, cause) => {
    if (cause == ResponseTimeoutException.get()) {
        // release some resources and cancel some tasks when a request is timed out.
    }
});

This is not a convenient way to listen to a timeout event.
I think we could add whenTimedOut() to RequestContext
interface RequestContext {
    CompletableFuture<Void> whenTimedOut();
}

ctx.whenTimedOut().thenRun(() => {
   // release some resources and cancel some tasks when a request is timed out.
});

Are we removing ctx.set*TimeoutHandler() then?

Are we removing ctx.set*TimeoutHandler() then?

That sounds good. Let me try it.


cmd/go: compilation fails with replace with repository module

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

$ go version
go version go1.12.5 linux/amd64

Does this issue reproduce with the latest release?
Sure, why  not?
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/ubuntu/.cache/go-build"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/ubuntu/go"
GOPROXY=""
GORACE=""
GOROOT="/usr/local/go"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/dev/null"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build755825477=/tmp/go-build -gno-record-gcc-switches"

What did you do?

$ env GO111MODULE= go get github.com/av86743/go-b0rken
go build github.com/av86743/go-b0rken: no non-test Go files in /home/ubuntu/go/src/github.com/av86743/go-b0rken
$ ( cd go/src/github.com/av86743/go-b0rken/ && env GO111MODULE=on go test . -run inner )
go: extracting github.com/syndtr/goleveldb v1.0.1-0.20190318030020-c3a204f8e965
go: extracting github.com/syndtr/goleveldb v1.0.0
# github.com/av86743/go-b0rken/inner
inner/inner.go:17:28: cannot use opt (type *"github.com/av86743/go-leveldb/leveldb/opt".Options) as type *"github.com/syndtr/goleveldb/leveldb/opt".Options in argument to leveldb.OpenFile
FAIL    github.com/av86743/go-b0rken [build failed]
$

What did you expect to see?
Compilation does not fail, at least.  See 'inner/inner.go' for a variant with imports replaced manually, which compiles.
What did you see instead?
Oh, come on now.  Repository 'github.com/av86743/go-leveldb' does not even exist.  Are you sure you know what you are talking about?

Thanks for accepting!

@av86743 the first error reported here:

env GO111MODULE= go get github.com/av86743/go-b0rken
go build github.com/av86743/go-b0rken: no non-test Go files in /home/ubuntu/go/src/github.com/av86743/go-b0rken

might be an instance of https://github.com/golang/go/issues/29268#issuecomment-447471173. Does that seem related?
Aside from that, can you expand a bit on what you are attempting to do here?
For example, you say:

Repository 'github.com/av86743/go-leveldb' does not even exist

Could you expand on why you are using a repository that does not exist? For example, is this a simplified example of something else you saw?

@av86743 the first error reported here:

env GO111MODULE= go get github.com/av86743/go-b0rken
go build github.com/av86743/go-b0rken: no non-test Go files in /home/ubuntu/go/src/github.com/av86743/go-b0rken

might be an instance of #29268 (comment). Does that seem related to the first error you reported here?

Irrelevant, disregard this.  It is just statement of a fact, it's not even tagged as an error.

Aside from that, can you expand a bit on what you are attempting to do here?

I am giving you a straight example where go.mod "replace" directive does not work. And registering your response.

For example, you say:

Repository 'github.com/av86743/go-leveldb' does not even exist

This is to bring your attention to the fact that compiler's error message reports a type from repository which does not even exist.  How much sense does it make to you?

Could you expand on why you are using a repository that does not exist? For example, is this a simplified example of something else you saw?

Whether that repository exists or not, is immaterial - in the presence of "replace" directive for this repository.  Don't you agree?

The replace directive replaces the source code for a module, not its import path (see #26904).
When you replace the package github.com/av86743/go-leveldb/leveldb, you end up loading the source code within github.com/syndtr/goleveldb/leveldb, and the files there import github.com/syndtr/goleveldb/leveldb/opt.
With the current semantics of replace, github.com/syndtr/goleveldb/leveldb/opt is a separate package from github.com/av86743/go-leveldb/leveldb/opt, even if they are built from source code in the same underlying repository. If github.com/syndtr/goleveldb is meant as a drop-in replacement for the source code of github.com/av86743/go-leveldb, then today it must use the original github.com/av86743/go-leveldb module and import paths.
We know that there is a use-case for replace to aid in un-forking modules that were previously forked, but we have not been able to address it yet. That's #26904 (and, to some extent, #30831).

Duplicate of #26904

@bcmills

The replace directive replaces the source code for a module, not its import path (see #26904).
When you replace the package github.com/av86743/go-leveldb/leveldb, you end up loading the source code within github.com/syndtr/goleveldb/leveldb, and the files there import github.com/syndtr/goleveldb/leveldb/opt.
With the current semantics of replace, github.com/syndtr/goleveldb/leveldb/opt is a separate package from github.com/av86743/go-leveldb/leveldb/opt, even if they are built from source code in the same underlying repository. If github.com/syndtr/goleveldb is meant as a drop-in replacement for the source code of github.com/av86743/go-leveldb, then today it must use the original github.com/av86743/go-leveldb module and import paths.

What do mean by saying "...it must use..." etc etc?  github.com/syndtr/goleveldb is what it is.  I have no control over its content.

The replace directive replaces the source code for a module, not its import path (see #26904).
When you replace the package github.com/av86743/go-leveldb/leveldb, you end up loading the source code within github.com/syndtr/goleveldb/leveldb, and the files there import github.com/syndtr/goleveldb/leveldb/opt.
With the current semantics of replace, github.com/syndtr/goleveldb/leveldb/opt is a separate package from github.com/av86743/go-leveldb/leveldb/opt, even if they are built from source code in the same underlying repository. If github.com/syndtr/goleveldb is meant as a drop-in replacement for the source code of github.com/av86743/go-leveldb, then today it must use the original github.com/av86743/go-leveldb module and import paths.
We know that there is a use-case for replace to aid in un-forking modules that were previously forked, but we have not been able to address it yet. That's #26904 (and, to some extent, #30831).

You could simply say: "@rsc solved it in https://golang.org/cl/174939 ."  Thanks, in any case.
Cox rocks. Which also rhymes. Niccce, whichever way you look at it.

Note that CL 174939 isn't merged (and won't be for 1.13). There are some remaining issues with replacement semantics that we need to work out (described in a comment on the CL), and I'm planning to make another run at it for 1.14.

I've backported that CL (plus related changesets) to go1.12.5.  It looks all right so far, but I need more time to validate typical use cases, review 5 items from CL which you mentioned, and just cool down a bit before I publish the port.


Add YoudaoDict 8.9

Microsoft Reviewers: Open in CodeFlow

It seems that Microsoft determined that the website of YoudaoDict is unsafe. I've submitted the request to report this issue.


useUnifiedTopology: "Maximum call stack size exceeded"

It appears as the code is written, it is possible for server selection (when sessions are enabled) to end up in an endless loop.

As I dig into this more, I realize this problem is because of how my test harness is setup. When mongodb launches, it does not have 4.0 feature compatibility turned on (so I initiate a executeDbAdminCommand like so):
{
replSetInitiate: {
  _id: 'mantis',
    version: 1,
    members: [
      {
        _id: 0,
        host: 'localhost:27017',
        priority: 1
      }
    ]
  },
  setFeatureCompatibilityVersion: '4.0'
}

If you are wondering, I use sessions/transactions for test isolations (so they can run in parallel) and do this at run-time to avoid needing to run "setup" commands prior to test execution (i wait until the server comes back as primary before continuing).

as a result, I now find that compared to before, hasSessionSupport() will not return true after running that command.. i currently have to trick the drive into thinking support is enabled, by doing this:
connection.db.s.topology.s.description.logicalSessionTimeoutMinutes = 30;
is there a public API method to expose "refreshing" the topology?

Hi @parisholley, thanks for the PR! I think I fixed this a bug a few days ago in this commit (NODE-2342). Is it possible for you to try out the master branch of the driver and see if it resolves your issue?

@mbroadst it did fix it, thanks

I think this is still happening
Version: "mongodb": "^3.6.6",
How I initiate mongo
    client = await MongoClient.connect(url, {
        useUnifiedTopology: true,
    })

Error:
RangeError: Maximum call stack size exceeded
at ClientSession.EventEmitter.init (events.js:150:20)
at ClientSession.EventEmitter.init (domain.js:468:20)
at new EventEmitter (events.js:65:21)
at new ClientSession (/overmind/node_modules/mongodb/lib/core/sessions.js:70:5)
at NativeTopology.startSession (/overmind/node_modules/mongodb/lib/core/sdam/topology.js:476:21)
at /overmind/node_modules/mongodb/lib/operations/execute_operation.js:46:28
at maybePromise (/overmind/node_modules/mongodb/lib/utils.js:685:3)
at executeOperation (/overmind/node_modules/mongodb/lib/operations/execute_operation.js:34:10)
at Object.callback (/overmind/node_modules/mongodb/lib/operations/execute_operation.js:160:5)
at processWaitQueue (/overmind/node_modules/mongodb/lib/core/sdam/topology.js:1049:21)


POS Email Case Sensitive

Emails entered in the POS are case sensitive and will not link the cart to an account if the capitalization is different than listed on the account

It sounds like, while 90% of emails can be not case sensitive, some email providers can, so making email not case sensitive is a security risk.

POS now searches for accounts based on email so carts can be linked to accounts directly


Breaking changes for types with union/recursive/generic when upgrading from v2.9.2 to v3.4.0

TypeScript Version:  3.4.0-dev.201xxxxx
The latest version 3.4.0-dev.20190220 still has this issue.

Search Terms:
Sorry. I do not even know any keyword that can describe my problem. I am not that good at compiler jargons.
Code
export interface WidgetBase {
    title?: string,
    widgetKey: string,
}

type NonOptionalKeys<T> = { [k in keyof T]-?: undefined extends T[k] ? never : k }[keyof T];

type Child<T extends WidgetBase> = { [P in NonOptionalKeys<T>]: T[P] }

export interface NumberWidget extends WidgetBase {
    type: "number",
    minimum: number,
    maximum: number,
}
export interface ListWidget extends WidgetBase {
    "type": "list",
    "minimum_count": number,
    "maximum_count": number,
    "each": ChildWidget //MARK1
}

export type PrimitiveWidget = | NumberWidget

export type ChildWidget =
    | Child<NumberWidget>
    | Child<ListWidget> //MARK2

type ListChild = Child<ListWidget>

Expected behavior:
ListChild should be equivalent to (exactly as it behaves in v2.9.2)
 {
    type: "list";
    minimum_count: number;
    maximum_count: number;
    each: ChildWidget;
    widgetKey: string;
}

Actual behavior:
type ListChild = {
    [x: string]: any;
}

DO NOTE that, if you comment out either the line containing MARK1 or the line containing MARK2, the type inference works correctly.

Playground Link:
Playground Link
Related Issues:

Simplified
type NonOptionalKeys<T> = { [k in keyof T]: T[k] extends number ? k : never }[keyof T];
type Child<T> = { [P in NonOptionalKeys<T>]: T[P] }

export interface ListWidget {
    "type": "list",
    "minimum_count": number,
    "maximum_count": number,
    "collapsable"?: boolean, //default to false, means all expanded
    "each": Child<ListWidget>;
}

type ListChild = Child<ListWidget>

@ryancavanaugh Thanks for the response. I suppose your simplified code is just another case similar to MARK1 and MARK2 in my question. The code I presented above is a minimal test case simplified from my original code. I have all sorts of widgets, primitive widgets like BooleanWidget, NumberWidget, etc and complex widgets like ListWidget, CompositeWidget which can contain other widgets. And child widgets can be any type of widget, not just Child.

@RyanCavanaugh After verifying your simplified code against v2.9.2, it is actually different from my original code. Your simplified version produces the same type in both v2.9.2 and v3.4.0.
type ListChild = {
    [x: string]: any;
}

It previously (sometimes) worked because our circularity detection wasn't particularly robust in 2.9. Child<T> generally isn't circular, but ends up having a circular constraint type if T itself has a property of type Child<T>. We now detect the circularity as we're resolving NonOptionalKeys<ListWidget> and then substitute the error type (basically an any) for NonOptionalKeys<ListWidget>. That's how we end up with the { [x: string]: any } type.
The core issue really is that we aren't reporting an error when we detect the circularity. It's tricky to do so because it only happens for certain instantiations and only when we actually resolve the members of the mapped type. Thus, there's no good source location to associate with the error.
Arguably, if we're not going to report an error, we should at least substitute never for a circular constraint in a mapped type such that the resolved type becomes {}.

To be clear, what's fixed is that we now error upon detecting the circular constraints during type instantiations.

@ahejlsberg Thanks for the quick response. I tried the nightly build （Version 3.4.0-dev.20190302 which I suppose contains the fix). But it seems to behave the same as v3.4.0. See both the screenshot and the result from command line.

➜  ts node node_modules/typescript/bin/tsc -V
Version 3.4.0-dev.20190302
➜  ts node node_modules/typescript/bin/tsc test.ts

Also, to be sure, is this fix meant to drop the support of such circular constraint type which actually worked in 2.9.2, and I need to figure out new ways to solve my problem?

The issue isn't uncovered until the compiler resolves the members of Child<ListWidget>, so you won't see an error until you include code in your program that actually references a member of ListChild. Just hovering over ListChild isn't enough. For example, add the following an the error appears:
declare let x: ListChild;
x.type;

Yes, you'll need to write the types in a manner that doesn't involve circular constraints.


Add MAX32680

The MAX32680 microcontroller (MCU) is an advanced system-on-chip (SoC) featuring an Arm® Cortex®-M4F and RISC-V CPU, large Flash and SRAM memories, and the latest generation Bluetooth® 5 Low Energy (LE) radio.
This PR add MAX32680 and it boards by providing basic functionalities

Add MAX32680 SoC support
Add MAX32680EVKIT support
Enable tests for peripherals drivers

Tested with:
blinky  example

button example

gpio_basic_api  test

uart_basic_api  test

Need to rebase and resolve conflicts

Need to rebase and resolve conflicts

Thanks, done.


Explicitly Mention Babel and Babel-Runtime in Installation in README

Very interesting library.  Please explicitly state these requirements in your installation documentation.

Would probably help out with #24

It used to be documented, but the next version has it explicitly in the dependencies: #26. Hoping to release 0.1.0 in the coming days. :)


File syncing in dev mode broke

v0.5.0 introduced a bug that fully broke file syncing when running in dev mode (ie acorn run --dev ...).

Reported in https://acorn-users.slack.com/archives/C03R9ME0SKC/p1674820672141939

Tested with acorn version v0.5.0-35-g0f895e7+0f895e74

Launched app in dev mode using -i option ( acorn run -i -n <name>)  with the  acorn file having dirs for container to mount cwd.

Acorn file for container app :
  app: {
    build: "."
    env: {
      "PG_USER": "postgres"
      "PG_PASS": "secret://quickstart-pg-pass/token"
      "WELCOME": args.welcome
      "MYARG": args.myarg
      if args.dev { "FLASK_ENV": "development" }
    }
    dependsOn: [
      "db",
      "cache"
    ]
    if args.dev { dirs: "/app": "./" }
    ports: publish: "5000/http"
  }

Made changes to the local files.

This results in syn initiated for the container and I am able to see the changes I make in the local files being reflected with the launched container when I exec into the container using acorn exec <container-name>
sync logs:
app-897f9bb6d-wq9rm: (sync): Upstream - Upload File '.app.py.swp'
app-897f9bb6d-wq9rm: (sync): Upstream - Upload 1 create change(s) (Uncompressed ~4.00 KB)
app-897f9bb6d-wq9rm: (sync): Upstream - Successfully processed 1 change(s)
app-897f9bb6d-wq9rm: (sync): Upstream - Upload File '.app.py.swp'
app-897f9bb6d-wq9rm: (sync): Upstream - Upload 1 create change(s) (Uncompressed ~4.00 KB)
app-897f9bb6d-wq9rm: (sync): Upstream - Successfully processed 1 change(s)
app-897f9bb6d-wq9rm: (sync): Upstream - Upload File '.app.py.swp'
app-897f9bb6d-wq9rm: (sync): Upstream - Upload 1 create change(s) (Uncompressed ~12.00 KB)
app-897f9bb6d-wq9rm: (sync): Upstream - Successfully processed 1 change(s)
app-897f9bb6d-wq9rm: <IP_ADDRESS> - - [30/Jan/2023 02:55:34] "GET / HTTP/1.1" 200 -
app-897f9bb6d-wq9rm: <IP_ADDRESS> - - [30/Jan/2023 02:55:34] "GET /favicon.ico HTTP/1.1" 404 -
app-897f9bb6d-wq9rm: (sync): Upstream - Handling 2 removes
app-897f9bb6d-wq9rm: (sync): Upstream - Remove '.app.py.swp'
app-897f9bb6d-wq9rm: (sync): Upstream - Remove '.app.py.swp'
app-897f9bb6d-wq9rm: (sync): Upstream - Remove '.app.py.swp'
app-897f9bb6d-wq9rm: (sync): Upstream - Upload File 'app.py'
app-897f9bb6d-wq9rm: (sync): Upstream - Upload 1 create change(s) (Uncompressed ~1.75 KB)
app-897f9bb6d-wq9rm: (sync): Upstream - Successfully processed 3 change(s)

Thanks folks! 🎉


refactor result table printing

This could still use work, but I took a shot at refactoring some of the table printing. In particular

now sorting so that Vectors and non-vectors come in separate chunks
can now optionally print in fixed-width columns.
made many of the formatting strings explicit parameters
removed code that prints constant-valued vectors as if they are scalars, as this seems possibly misleading

Here's an example of the current output for print sol.table()
Cost
 0.00474

Variables
 CDA : 0.005                              [m**2]    projectile drag area
   R : 211                                [m]       range
Vmax : 100                                [m/s]     max firing velocity
   g : 9.8                                [m/s**2]  gravity
   m : 1                                  [kg]      projectile mass
 rho : 1.2                                [kg/m**3] air density
   V : [ 1e+02    95       91      ... ]  [m/s]
  dt : [ 0.13     0.14     0.14    ... ]  [s]
  vx : [ 79       76       73      ... ]  [m/s]
  vy : [ 61       57       54      ... ]  [m/s]

Constant sensitivities
 CDA : 0.494   projectile drag area
Vmax : -1.01   max firing velocity
   g : 0.506   gravity
   m : -0.494  projectile mass
 rho : 0.494   air density

and here's print sol.table(fixedcols=False)

Cost
 0.00474

Variables
 CDA : 0.005    [m**2] projectile drag area
   R : 211      [m] range
Vmax : 100      [m/s] max firing velocity
   g : 9.8      [m/s**2] gravity
   m : 1        [kg] projectile mass
 rho : 1.2      [kg/m**3] air density
   V : [ 1e+02    95       91      ... ]  [m/s]
  dt : [ 0.13     0.14     0.14    ... ]  [s]
  vx : [ 79       76       73      ... ]  [m/s]
  vy : [ 61       57       54      ... ]  [m/s]

Constant sensitivities
 CDA : 0.494   projectile drag area
Vmax : -1.01   max firing velocity
   g : 0.506   gravity
   m : -0.494  projectile mass
 rho : 0.494   air density

Should I merge it?

Ah, not yet; just going to read and comment some more, then I'll pull it!

(ask for a code review, get a code review is my thinking here...)

yes yes, good!

Made some comments; looks great overall! I think my only question was on the assert.

:+1:

should I merge?

yup!


[11.0][PORT] pos_product_lot, product_lot

@Railia check that new tours are enough to test workflow

Too much conflicts


Ubuntu 17.04 works

I upgraded my machine to 17.04 and installed the latest version of DisplayLink (1.3.43) but the display isn't working using the DVI connection on a Thinkpad Pro docking station.
Networking is also not working.
If there is a way to get the logs, please let me know the commands and I'll paste the responses here.

Networking was broken because Ubuntu decided to stop managing the network interface, so that wasn't related. I fixed it by creating a blank file for the network manager to see.
sudo touch /etc/NetworkManager/conf.d/10-globally-managed-devices.conf
The 3rd monitor that I have connected to the DisplayLink interface showed up in the displays tool, and I enabled it, however it still doesn't receive signal using a DVI to VGA converter.

It works!
I had 1.3.43 installed when it showed the monitor in displays and didn't turn it on, and that would have worked, but I decided to uninstall it anyway and install 1.3.52 instead to see if that was the problem.
After a reboot with the new kernel module installed I noticed the same issue -- display is enabled but not displaying anything. Then I decided to wiggle the DVI connection and found that it was ever-so-slightly off kilter. Once I fully seated the adapter the monitor turned on! Go figure.

Sadly, upon further testing, the DisplayLink monitor is only running at 1fps. There is some configuration that  Ubuntu uses that's slowing the refresh rate. It may be related to various other Intel-based mouse flickering issues because my mouse is flickering as well.
Suggestions to disable vsync in ccsm don't help and drivers are all up to date.

The 1fps lag issue can be fixed by creating or editing the following configuration file (only with Intel-based graphics drivers). Make sure to install the Intel Graphics Update Tool for Linux.
/usr/share/X11/xorg.conf.d/20-intel.conf
Section "Device"
  Identifier "Intel Graphics"
  Driver "Intel"
  Option "AccelMethod" "sna"
  Option "TearFree" "true"
  Option "TripleBuffer" "true"
  Option "MigrationHeuristic" "greedy"
  Option "Tiling" "true"
  Option "Pageflip" "true"
  Option "ExaNoComposite" "false"
  Option "Tiling" "true"
  Option "Pageflip" "true"
EndSection

This is a very useful comment, thank you! I'll post this workaround to our forum for people using Intel.

@ajbogh the Section in 20-intel.conf plus the empty file for the NetworkManager did the trick. Upgraded to 17.04, running 4.10.0-19-generic and evdi 1.3.52 with intel graphics.
2 external Monitors and a Targus USB docking station. All works as before (16.04).
Many thanks!

I've actually just had to create the blank /etc/NetworkManager/conf.d/10-globally-managed-devices.conf file as well to get my Ethernet connection working... sadly, it kills my wifi connection.  So, I can have EITHER wifi or wired, but not BOTH, like I used to.

Just creating the /usr/share/X11/xorg.conf.d/20-intel.conf file from @ajbogh fixed the issue for me.
Cheers!

Is this fix with the /usr/share/X11/xorg.conf.d/20-intel.conf only working on Ubuntu 17.04 ?
At the moment I'm running on 16.04.2 LTS

I have three attached displays through dell D3100 dock.  Creating the 20-intel.conf file fixed the issue with the displays not showing at all.  I upgraded the bios and displaylink drivers to latest.  Unfortunately, I still have these issues:

Displays are very slow to be recognized, on the order of multiple minutes, where on 16.04 the came up almost instantly.
There are now trailing cursor artifacts left behind.
Thank you for any additional insights and for the above solution as well!

#1 resolved: wait until after login to attach dock
#2 resolved: remove Option "TearFree" "true" from /usr/share/X11/xorg.conf.d/20-intel.conf

For me (and apparently for others), the 20-intel.conf file doesn't need any "Option" lines at all. Just "Identifier" and "Driver" alone is enough to fix the display. It probably triggers setting some defaults that are otherwise undefined.

@JanneM I can confirm this as well on 17.04. The only caveat is you need to hook the dock in after login (otherwise the screen won't come on).

@ajbogh I noticed that your xorg conf file has several config options duplicated (Two pageflip and Tiling options). Does it need to be declared more than once? Otherwise this in theory should work without the duplicate instances:
Section "Device"   Identifier "Intel Graphics"   Driver "Intel"   Option "AccelMethod" "sna"   Option "TearFree" "true"   Option "TripleBuffer" "true"   Option "MigrationHeuristic" "greedy"   Option "Tiling" "true"   Option "Pageflip" "true"   Option "ExaNoComposite" "false"   Option "Tiling" "true"   Option "Pageflip" "true" EndSection

@compuguy It doesn't have to have duplicates. Those are just copy/paste errors.

Environment:
Razer Blade 14 2014
Intel GPU
Nvidia 870M
1x HDMI port
I originally had no video drivers installed and was using the Intel gpu and this did not work with DisplayLink with 1.4x drivers installed until i added xorg.conf.d/20-intel.conf. After this it worked as a third display but I had disappearing mouse cursor issues constantly and only with the DisplayLink hdmi usb adapter plugged in... there were times when the mouse wouldn't come back for minutes.  Most of the time the behavior would be: on the top half of the screen the mouse would only flicker and on the bottom half it would completely disappear. I experimented with all permutations between 20-nvidia.conf, 20-intel.conf one being active vs both and all of the params in each scenario: TearingFree false/true, TripleBuffering false/true, PageFlip false/true
Solution for me was to use the GNOME desktop, the 20-intel.conf with only:
Section "Device"
Identifier "Intel Graphics"
Driver "Intel"
EndSection
And using the Nvidia driver 340 proprietary in AdditionalDrivers while setting it to be primary usage in Nvidia application with rendering quality set to performance.
No more disappearing mouse, 3 monitors all plugged in at boot and only a 10 second wait for the USB DisplayLink monitor to show up after login.
Cheers

Just wish to confirm, this worked for me too running Ubuntu 18.04, I didn't have the folder /etc/X11/xorg.conf.d/ - but creating it and making the file inside with the full (deduplicated config) above fixed the issue. Finally I can move my mouse again!

Environment:
Razer Blade 14 2014
Intel GPU
Nvidia 870M
1x HDMI port
I originally had no video drivers installed and was using the Intel gpu and this did not work with DisplayLink with 1.4x drivers installed until i added xorg.conf.d/20-intel.conf. After this it worked as a third display but I had disappearing mouse cursor issues constantly and only with the DisplayLink hdmi usb adapter plugged in... there were times when the mouse wouldn't come back for minutes. Most of the time the behavior would be: on the top half of the screen the mouse would only flicker and on the bottom half it would completely disappear. I experimented with all permutations between 20-nvidia.conf, 20-intel.conf one being active vs both and all of the params in each scenario: TearingFree false/true, TripleBuffering false/true, PageFlip false/true
Solution for me was to use the GNOME desktop, the 20-intel.conf with only:
Section "Device"
Identifier "Intel Graphics"
Driver "Intel"
EndSection
And using the Nvidia driver 340 proprietary in AdditionalDrivers while setting it to be primary usage in Nvidia application with rendering quality set to performance.
No more disappearing mouse, 3 monitors all plugged in at boot and only a 10 second wait for the USB DisplayLink monitor to show up after login.
Cheers

My current environment is:
Lenovo Yoga 720
Intel GPU
Nvidia GeForce GTX 1050
Not only do I have the mouse flickering problem but despite having the nvidia drivers installed and running, I cant seem to set xorg to run with the GTX1050. Could you show me the config files you created for that purpose?
I would be thankful beyond measure!


When resuming training, text encoder is always re-trained from scratch...

Everytime I want to resume training my UNet model from a given checkpoint, the text encoder is always retrained from scratch.
Is it possible to save a trained text encoder and then re-use it when resuming the training of the UNet?

you simply un check the box "Enable_text_encoder_training" and it will train only the UNet

ok... but will it re-use the existing text encodings then?

Yes if you check the box "resume training" it will use the existing (trained) text encoder

ok thank you very much for the clarification!!


Could not send an Open Secure Channel request on Windows server 2019

Hi,
I am trying to connect the opc publisher with the opc server using certificates, but I am unable to. Both the server and the publisher are on the same Windows server 2019 machine. The folder pki/own contains the certificate that is auto created when the module runs and then I add the certificate of the server-client on the trusted folder. I set the Security Mode: true on the publishednodes_opcplc.json. I don’t know if I am missing a step installing certificates on the machine or something like that.
This is the Create Container Options of the module:
"Cmd": [
"publisher",
"--pf=/appdata/publishednodes_opcplc.json",
"--to",
"--aa",
"--at=Directory",
"--ih=Amqp_Tcp_Only",
"--tp=/appdata/pki/trusted",
"--rp=/appdata/pki/rejected",
"--ap=/appdata/pki/own",
"--ip=/appdata/pki/issuer"
],
This are the security policies enabled:

Error log:
Session creation to endpoint 'opc.tcp://xxx.xxx.xx.xx:xxxx' failed 1 time(s). Please verify if server is up and Publisher configuration is correct.                                                                                System.AggregateException: One or more errors occurred. (Error establishing a connection: Could not send an Open Secure Channel request.) ---> Opc.Ua.ServiceResultException: Error establishing a connection: Could not send an Open Secure Channel request.                                    at Opc.Ua.Client.Session.Create(ApplicationConfiguration configuration, ConfiguredEndpoint endpoint, Boolean updateBeforeConnect, Boolean checkDomain, String sessionName, UInt32 sessionTimeout, IUserIdentity identity, IList1 preferredLocales)                                           --- End of inner exception stack trace ---                                                                                at System.Threading.Tasks.Task1.GetResultCore(Boolean waitCompletionNotification)                                                             at OpcPublisher.OpcSession.ConnectSessionAsync(CancellationToken ct) in D:\a\1\s\modules\opc-publisher\opcpublisher\OpcSession.cs:line 444  ---> (Inner Exception #0) Opc.Ua.ServiceResultException: Error establishing a connection: Could not send an Open Secure Channel request.          at Opc.Ua.Client.Session.Create(ApplicationConfiguration configuration, ConfiguredEndpoint endpoint, Boolean updateBeforeConnect, Boolean checkDomain, String sessionName, UInt32 sessionTimeout, IUserIdentity identity, IList`1 preferredLocales)<---

We recently fixed the certificates recreation issue (#451). can you give it a try with the :preview tag container?
Please be aware though that also the publisher's certificate must be trusted by the server.
Nevertheless, looking at the exception I cannot tell if this is a security issue or a connectivity issue. Can you please provide a bit more insight?

Closing - please could you try current master branch and re-open if the issue still exists.


Seems like a bug when import InceptionV1

Hi, I use tensorboard draw the graph before final optimization and find a weird thing. That is the output of softmax2_pre_activation is 1008 dimension. I don't know whether it hurt the results of attribution method. Here is the screenshot about it.
Ps: classification results of the dog and cat image are right.

1008 is actually correct! InceptionV1 was trained with a couple extra "dummy" outputs in the softmax.


Remove gml:AssociationAttributeGroup from appearance property type

The  <core:appearance> property element of core:AbstractCityObjectType is currently defined such that it can carry the Appearance inline or reference it using an XLink.
Sharing appearances between city objects this way does not make much sense in my opinion. An inline property seems to be more appropriate. This might also be true for other feature properties that are strongly related to a specific city object (e.g. core:dynamizer).

For example, I think that core:CityObjectRelationPropertyType should also be changed into an inline property. Why should a relation between feature A and B be referenced and reused by feature C?


mmseqs download will no longer get the most up-to-date nr/nt databases

Expected Behavior
mmseqs download would be expected to download an up-to-date version of the target 'nr' and 'nt' databases.
Current Behavior
The download FASTA targets for the 'nr' and 'nt' databases are no longer being updated by NCBI. Explanation: focusing on 'NR' as an example, the URL in databases.sh points to https://ftp.ncbi.nlm.nih.gov/blast/db/FASTA/nr.gz.  The README in that FTP location states:

In April 2024, the BLAST FASTA files in this directory will no longer be
available. You can easily generate FASTA files yourself from the formatted
BLAST databases by using the BLAST utility blastdbcmd that comes with the
standalone BLAST programs. See NCBI Insights for more details
https://ncbiinsights.ncbi.nlm.nih.gov/2024/01/25/blast-fasta-unavailable-on-ftp/

Indeed, the nr.gz file was last updated on 2024-02-07.
Looking in the parent directoy, the various NR database files have been updated as recently as 2024-10-02. Therefore, the download targets for mmseqs2 are out of date by about 8 months, and this problem will get worse over time.
NCBI's solution for users is to download the blast-format files and then generate their own FASTA files:

Sequences in FASTA format can be generated from the pre-formatted databases by using the blastdbcmd utility;

Obviously this isn't ideal for many users, and it's been getting at least some hate.
Solution
Unless NCBI backflips on their decision, the only solution would be to change the mmseqs databases workflow for these databases to have an intermediate (slow) step of extracting a FASTA file before the mmseqs createdb step is run. However, this would obviously require extra dependencies, i.e. the blastdbcmd. Otherwise, I suppose you could host periodic builds of the databases on a server or something.
Just thought I should bring this to your attention in case you are unaware :smile:

I would recommend to just use UniProt instead of NR. it’s much better maintained, especially with the versioning. Any annotations against the NR are essentially unreproducible due to the lack of versioning by the NCBI.
I don’t plan on integrating the blast databases for the foreseeable future.


Introduce LoggingOptions.AuthorizeRequestSensitiveValuesFilter

We take some sensitive parameters with the "AuthorizeRequest" endpoint with some ICustomAuthorizeRequestValidator implementation to validate them.
We don't want those sensitive parameters be logged when the validation fails.
This commit introduces AuthorizeRequestSensitiveValuesFilter similar to TokenRequestSensitiveValuesFilter. This will allow us customize which parameter gets scrubbed.

Thanks!


Regression in v2: "Field 'name' on type 'RemoteDependencyData' is too long" with long URL

Seems issue #369 came back in v2... seeing a lot of these in SharePoint Online when using the OOTB AI JS v2 SDK:
Field 'name' on type 'RemoteDependencyData' is too long. Expected: 1024 characters, Actual: 1242

I've fixed this in #933 which will land in 2.0.2

Hello! I am still having this problem! My config is almost identical to this example, and my dependencies are as follows:
"@microsoft/applicationinsights-react-js": "^2.0.2",
"@microsoft/applicationinsights-web": "^2.0.1",

Would really appreciate some help. Thank you!

Hi @ecezalp 2.0.2 hasn't shipped yet, but for now you can add a (non-breaking) telemetry initializer in the meantime
appInsights.addTelemetryInitializer(item => {
    if (item.baseType === 'RemoteDependencyData') {
        if (item.baseData.name.length > 1024) {
            item.baseData.name = item.baseData.name.substring(0, 1024);
        }
    }
});


Heimdall script error

✅ Have you read and understood the above guidelines?
yes
📜 What is the name of the script you are using?
Heimdall Dashboard LXC
📂 What was the exact command used to execute the script?
bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/heimdall-dashboard.sh)"
📝 Provide a clear and concise description of the issue.
[ERROR] in line 25: exit code 0: while executing command RELEASE=$(curl -sX GET "https://api.github.com/repos/linuxserver/Heimdall/releases/latest" | awk '/tag_name/{print $4;exit}' FS='[""]')
⚙ What settings are you using?

[X] Default Settings
[ ] Advanced Settings

🖥 Which Linux distribution are you using?
Debian 12
🔄 Steps to reproduce the issue.
bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/heimdall-dashboard.sh)"
❌ Paste the full error output (if available).
[ERROR] in line 25: exit code 0: while executing command RELEASE=$(curl -sX GET "https://api.github.com/repos/linuxserver/Heimdall/releases/latest" | awk '/tag_name/{print $4;exit}' FS='[""]')
🖼 Additional context (optional).
No response

Works good on my end!

Can you try running in the proxmox shell the following commands?
RELEASE=$(curl -sX GET "https://api.github.com/repos/linuxserver/Heimdall/releases/latest" | awk '/tag_name/{print $4;exit}' FS='[""]')
echo ${RELEASE}

v2.6.3

Today I tried again with IPv4, this worked. Dont know why only this script with IPv6 doesn't worked on my machine.

When was the issue?

When I updated from 2.6.1 to 2.6.3, typing update did nothing, pasting the script gave a fail error, then I couldn't connect but after a reboot it said it had updated successfully.


Set minimum width and height for the client

The smallest resolution in the game that can be applied is 1024x768
It must be applicable to the client. This is a way to avoid issues with the display of content (usually these are overlapping views)

I don't know if we have to have the same min size as the game. But yeah some min size might be nice although I am not sure if it needs to be set to full screen. I know some people like having the screen split.
So maybe we just also have to make the client more responsive

So maybe we just also have to make the client more responsive

Okay. 👍


Error opening device on /host/dev/falco0

What happened:
kubectl logs falco-hmk8n
* Setting up /usr/src links from host
ls: cannot access '/host/usr/src': No such file or directory
* Unloading falco-probe, if present
* Running dkms install for falco
Error! echo
Your kernel headers for kernel 4.9.125-linuxkit cannot be found at
/lib/modules/4.9.125-linuxkit/build or /lib/modules/4.9.125-linuxkit/source.
* Running dkms build failed, couldn't find /var/lib/dkms/falco/0.15.3/build/make.log
* Trying to load a system falco-probe, if present
* Trying to find precompiled falco-probe for 4.9.125-linuxkit
Found kernel config at /proc/config.gz
* Trying to download precompiled module from https://s3.amazonaws.com/download.draios.com/stable/sysdig-probe-binaries/falco-probe-0.15.3-x86_64-4.9.125-linuxkit-598c2d809165b47f38383b83b6ff4798.ko
curl: (22) The requested URL returned error: 404 Not Found
Download failed, consider compiling your own falco-probe and loading it or getting in touch with the sysdig community
2019-06-25T12:51:34+0000: Falco initialized with configuration file /etc/falco/falco.yaml
2019-06-25T12:51:34+0000: Loading rules from file /etc/falco/falco_rules.yaml:
2019-06-25T12:51:35+0000: Loading rules from file /etc/falco/falco_rules.local.yaml:
2019-06-25T12:51:35+0000: Loading rules from file /etc/falco/k8s_audit_rules.yaml:
2019-06-25T12:51:35+0000: Unable to load the driver. Exiting.
2019-06-25T12:51:35+0000: Runtime error: error opening device /host/dev/falco0. Make sure you have root credentials and that the falco-probe module is loaded.. Exiting.

What you expected to happen: falco pod should not go into error
How to reproduce it (as minimally and precisely as possible):
I installed daemonsets without rbac on mac os mojave.
 sudo kubectl create -f falco-daemonset.yaml
Anything else we need to know?:
Environment:

Falco version (use falco --version): I cloned dev branch and this is the image in
daemonsets falcosecurity/falco:latest
System info <!-- Falco has a built-in support command you can use  "falco --support | jq .system_info" -->
Cloud provider or hardware configuration: mac book pro
OS (e.g: cat /etc/os-release): mac os mojave
Kernel (e.g. uname -a): Darwin usamas-mbp.lan 18.2.0 Darwin Kernel Version 18.2.0: Mon Nov 12 20:24:46 PST 2018; root:xnu-4903.231.4~2/RELEASE_X86_64 x86_64
Install tools (e.g. in kubernetes, rpm, deb, from source): I am running minikube on macbook pro
Others: I tried to run this on aws ec2 ubuntu 18.04 and it worked but not here on my machine. i think its probably kernel error. can someone give some pointer?

Hi @UsamaMehboob - multiple users reported the same problem you have, it is related to the fact that docker for mac is using linuxkit and you don't have kernel headers in it.
There is a way to load it described in this comment: https://github.com/falcosecurity/falco/issues/657#issuecomment-506303851
We are discussing on whether to include that in the installation procedure or docs.
I'm closing this as a duplicate but feel free to reopen in case you think that is not.
/triage duplicate

/close

@fntlnz: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.


Release v1.12.2

/lgtm

centos-stream buildroot is broken https://pagure.io/releng/issue/12305 . Ignore those.


Fix incorrect application icon behavior on Linux

Fixes jgraph/drawio-desktop#547. I have tested this change only on Linux+KDE and can confirm it works. Obviously some testing on Mac and Windows would be nice to confirm it doesn't break anything. More details in the linked issue.
Before:
https://user-images.githubusercontent.com/840021/149759445-c634f900-6231-47df-a629-bbfb343af455.mp4
After:
https://user-images.githubusercontent.com/840021/149759462-2e23400a-b4e3-447f-92a6-c18aae09564b.mp4

I went to check out the new release and sadly I noticed that the change wasn't included... Why is that @davidjgraph ? Was this change causing bugs on other platforms?

Because this isn't the real repo, it's just a mirror. It will come at some point.


Search bar and product list should be cleared after logout

Current behavior

After logout and then login again, the search bar field is pre-filled and the search results are visible
Expected behavior

After logout and then login again, then all the previous search query and result should be cleared.
Steps to reproduce the issue

Login into the application
Search for a keyword like MH, you will see products matching the results
Logout from the app and login again.
See that the previous searched keyword and search results are still visible.

Can you handle fixing this bug by yourself?

[ ] YES
[ ] NO

Environment details

Browser:
OS:
Code Version:

Additional information

closing task, duplicate of linked task


Print Option

Hey,
Talking to another Xwing player and had an idea.
Maybe at the print list option, you could include that the cards can be printed too, not just the card text and title, but the actual pilot or upgrade card photo/image
Cheers,
Vlad

Probably not allowed by FFG since the card images are likely copyrighted.

Fair point.
Vlad Serban
On Fri, Jul 13, 2018, 15:02 J. J. Cole<EMAIL_ADDRESS>wrote:

Probably not allowed by FFG since the card images are likely copyrighted.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/geordanr/xwing/issues/574#issuecomment-404813107, or mute
the thread
https://github.com/notifications/unsubscribe-auth/Ak7utxAkHH5E5z7TBMcB9SwEHQl7Xi7mks5uGIw_gaJpZM4Tjd2n
.


build: update bazel setup to latest dev-infra and rules_nodejs version

Updates the Bazel setup to the latest dev-infra and rules_nodejs
version. This includes:

The removal of the spec-bundling code as that has been moved over to
the shared dev-infra code.

The remoal of the AMD esbuild and devmode JS source extraction as
these rules have been moved to the shared dev-infra logic.

The removal of the Angular linker ESBuild plugin creation as this
logic is now exposed as shared script in the shared dev-infra package.

Targeted minor due to merge conflict with 13.0.x.. Please create another PR if this needs to go into patch as well.


DBZ-1395 Add ability to insert fields from original source struct to flattened record

https://issues.jboss.org/browse/DBZ-1395
Description
We have a use case that requires passing the Postgres LSN through to a sink, but also want to flatten the events produced by the Postgres connector. Similar to the __deleted field added by the ExtractNewRecordState transform, it would be great if we could specify fields from the source struct in the event to be added as metadata fields (prefixed with __) to the flattened record produced by ExtractNewRecordState.
This change allows users to specify a list of fields from the source struct that will be inserted into into the final flattened record as metadata fields prefixed with "__". For example:
transforms.unwrap.add.source.fields=table,lsn

adds "__table": "MY_TABLE", "__lsn": "123456789" to the flattened record.
We're currently using this in production from a branch off the 9.5 tag, figured someone else might find it useful.
Implementation
I followed the pattern used in the InsertField Transformation which uses a SynchronizedCache<> to cache the schema, and then produces a new record using the original record & the requested source fields.

@adriank-convoy Thanks a lot! I've added very few comments related to cache handling code. When addressed we are good to merge the PR.

Hey @jpechane, updated the cache code, let me know if there's anything else!

@adriank-convoy Applied, thanks a lot for the feature!


Job metrics page use new job exporter metrics

Job metrics page use new job exporter metrics & query
Page render doesn't change. Please ref https://github.com/Microsoft/pai/pull/387 pages image.
For example task view page

Pull Request Test Coverage Report for Build 843

0 of 0 (NaN%) changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-25.5%) to 45.404%

Totals

Change from base Build 836:
-25.5%

Covered Lines:
2280

Relevant Lines:
5122

💛  - Coveralls


Add setup instructions in README

@atulmy The setup works now. Kindly add these details in Readme, and maybe create a Docker service for no installation issues.

Thank you for the suggestion @VinayakBagaria. Added prerequisites section in Readme.


New release 🚀

I think it's time to craft a new release, especially for those who are using CocoaPods to reference Moya.
It will be a release with breaking changes and some great improvements, probably a 7.0.0 release?

I think this is a good idea, I don't see any other issues tagged "breaking changes", but we need to cleanup those issue tags anyway 😁
I'll give some time for other @Moya/contributors to chime in, and if no one objects, we'll release Moya 7.0.0 🎉

We might have a non-backwards-compatible feature request worth squeezing in: https://github.com/Moya/Moya/issues/542 I believe @colinta is taking a look, I can help too.

Working on it right now, looks straightforward.  Thanks for stalling!

On Jul 13, 2016, at 8:54 AM, Ash Furrow<EMAIL_ADDRESS>wrote:
We might have a non-backwards-compatible feature request worth squeezing in: #542 https://github.com/Moya/Moya/issues/542 I believe @colinta https://github.com/colinta is taking a look, I can help too.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/Moya/Moya/issues/535#issuecomment-232381039, or mute the thread https://github.com/notifications/unsubscribe/AABrsveZ90i0sXvBGz7tor_Fy5iC4WaAks5qVPxCgaJpZM4JKtqk.

Cool, I think we're good?

I'm done I swear! 😃

Okay! That's tagged and pushed to CocoaPods, Carthage folk have their GitHub release, too: https://github.com/Moya/Moya/releases/tag/7.0.0
Thanks for the help all our contributors have put in to getting us to Moya's seventh major release in two years!

👏

On Jul 13, 2016, at 5:20 PM, Ash Furrow<EMAIL_ADDRESS>wrote:
Closed #535.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.


CORS headers are not attached for serverless function

🐞 Describe the bug
After deploying Ackee to Vercel and setting ACKEE_AUTO_ORIGIN=true, I am not seeing any CORS headers in response to the OPTIONS ackee.example.com/api request (where example.com is replaced with my domain). I have also tested with ACKEE_ALLOW_ORIGIN=site.example.com, with the same result. In both cases I'm seeing:
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://ackee.example.com/api. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 204.

📚 To Reproduce

Set up the project on Vercel
Set the env variable ACKEE_AUTO_ORIGIN=true
Log in and create a site on Ackee for your domain
Add the tracking script to your site
Observe requests in the browser dev tools to see lack of CORS headers

💡 Expected behavior
The OPTIONS /api response includes CORS headers to allow the tracker script to connect.
⚙ Environment

Installation: Vercel
Ackee version: v3.4.0

📋 Additional context
I have validated that the origin handler is called and returns ["site.example.com"]. It seems that the CORS headers are calculated correctly, but somehow not applied.

Just double checked how I'm passing the origin to Apollo server and it seems to be the correct way.
type StaticOrigin = boolean | string | RegExp | (boolean | string | RegExp)[];

type CustomOrigin = (requestOrigin: string | undefined, callback: (err: Error | null, origin?: StaticOrigin) => void) => void;

That's basically what I'm doing: https://github.com/electerious/Ackee/blob/ba976a89dcde893371b881d5fc4496cfb1c2625c/src/serverless.js#L51
I'm not sure what's happening with the headers.

Yes, as far as I can see you're passing it correctly. I've been debugging this for a few hours with various logs and workaround attempts, but so far it seems like Vercel might not be passing the headers, or something else is happening between the Apollo server and the client. I'll report back if I figure out what's going wrong.

That's how the response of the handler looks when I log it. There seems to be a access-control-allow-origin and a access-control-allow-credentials, but I'm not sure what happens to the allowedHeaders.
{
  statusCode: 200,
  body: '[{"data":{"facts":{"id":"e875350a-09ae-59bf-ae72-2ae687ba00db","activeVisitors":0,"__typename":"Facts"}}}]\n',
  multiValueHeaders: {
    'x-powered-by': [ 'Express' ],
    'access-control-allow-origin': [ 'https://example.com' ],
    vary: [ 'Origin' ],
    'access-control-allow-credentials': [ 'true' ],
    'content-type': [ 'application/json; charset=utf-8' ],
    'content-length': [ '107' ],
    etag: [ 'W/"6b-LOgac06NQapfhEsmrItvJVDfH1c"' ]
  },
  isBase64Encoded: false
}

Thanks, that's great for debugging. I think that might've helped me uncover a related bug:
Bug with auto detected domains (ACKEE_AUTO_ORIGIN=true)
	const handler = apolloServer.createHandler({
		expressGetMiddlewareOptions: {
			cors: {
				origin,
				credentials: true,
				methods: 'GET,POST,PATCH,OPTIONS',
				allowedHeaders: 'Content-Type, Authorization, Time-Zone',
			},
		},
	})
+	const response = handler(event, context)
+	response.then((value) => console.log('Response', value))
+	return response

doesn't set the access-control-allow-origin (I'm guessing express thinks that the user domain https://site.example.com doesn't match the string site.example.com)
Response {
  statusCode: 204,
  body: '',
  multiValueHeaders: {
    'x-powered-by': [ 'Express' ],
    vary: [ 'Origin' ],
    'access-control-allow-credentials': [ 'true' ], // note lack of access-control-allow-origin
    'access-control-allow-methods': [ 'GET,POST,PATCH,OPTIONS' ],
    'access-control-allow-headers': [ 'Content-Type, Authorization, Time-Zone' ],
    'content-length': [ '0' ]
  },
  isBase64Encoded: false
}

but prepending protocols fixes that:
const origin = (origin, callback) => {
	if (config.autoOrigin === true) {
		fullyQualifiedDomainNames()
+			.then((names) => callback(null, names.flatMap((name) => [ `http://${ name }`, `https://${ name }` ])))
			.catch((error) => callback(error, false))
		return
	}

Response {
  statusCode: 204,
  body: '',
  multiValueHeaders: {
    'x-powered-by': [ 'Express' ],
    'access-control-allow-origin': [ 'https://site.example.com' ], // now it's here :)
    vary: [ 'Origin' ],
    'access-control-allow-credentials': [ 'true' ],
    'access-control-allow-methods': [ 'GET,POST,PATCH,OPTIONS' ],
    'access-control-allow-headers': [ 'Content-Type, Authorization, Time-Zone' ],
    'content-length': [ '0' ]
  },
  isBase64Encoded: false
}

Note that the protocol cannot be added to the site name directly in Ackee because it then wouldn't be recognized as a domain by is-valid-domain.

Regardless, the headers still aren't being returned to the browser for some reason. It looks like multiValueHeaders is just AWS specific syntax for setting headers, so it should work - I'll keep digging to see if I can force it to work.
Note: workaround if all you need is a single site or *
The only success I've had with getting headers sent out to the browser has been by setting them in vercel.json. This doesn't work for dynamic headers, but in case anyone is desperate for a workaround here's the vercel.json that forces CORS headers:
{
  "build": {
    "env": {
      "NODEJS_AWS_HANDLER_NAME": "handler"
    }
  },
  "headers": [
    {
      "source": "/(.*)",
      "headers": [
        {
          "key": "Access-Control-Allow-Origin",
          "value": "https://site.example.com"
        },
        {
          "key": "Access-Control-Allow-Credentials",
          "value": "true"
        },
        {
          "key": "Access-Control-Allow-Headers",
          "value": "X-Requested-With, Access-Control-Allow-Origin, X-HTTP-Method-Override, Content-Type, Cache-Control, Authorization, Accept"
        },
        {
          "key": "Access-Control-Max-Age",
          "value": "86400"
        }
      ]
    }
  ]
}

Finally! Your code helped a lot @electerious. I think I've finally found the issue: the AWS Lambda API is poorly documented, but seems to use both .headers and .multiValueHeaders to define headers. The Vercel shim that lets us run the serverless function without coding it specifically for Vercel seems to lack support for .multiValueHeaders.
The issue is fixed if we convert .multiValueHeaders to .headers:
// api/index.js
'use strict'

/**
 * A serverless function handler for the '/api' route, for use with Vercel.
 * This handler follows the AWS Lambda API; Vercel deployments are opted-in
 * using the "NODEJS_AWS_HANDLER_NAME" environment variable defined in vercel.json.
 *
 * See:
 *  - https://vercel.com/docs/serverless-functions/supported-languages#node.js
 *  - https://vercel.com/docs/runtimes#advanced-usage/advanced-node-js-usage/aws-lambda-api
 */
const handler = require('../src/serverless').handler

const convertMultiValueHeaders = (response) => {
	if (!(response instanceof Object) || !('multiValueHeaders' in response)) {
		console.log('No multiValueHeaders, not converting')
		return response
	}
	response.headers = response.headers || {}
	for (const [ key, value ] of Object.entries(response.multiValueHeaders)) {
		if (value.length === 1) {
			response.headers[key] = value[0]
		}
	}
	return response
}

exports.handler = async (...args) => {
	const response = await handler(...args)
	console.log('Response before conversion:', response)
	const converted = convertMultiValueHeaders(response)
	console.log('Response after conversion:', response)
	return converted
}

I'll create a PR shortly

I've opened a support case with Vercel, which they say they'll try to respond to within 3-5 business days.
Would you like me to create a PR to fix this in Ackee @electerious, or should we wait for Vercel to respond and (possibly) update their AWS Lambda API shim?

Thanks a lot for your work! This would have taken me forever to figure out. A PR is welcome :)

Pushed a new version of Ackee. Please let me know if everything works now! :)

新版本还是Unexpected token A in JSON at position 0

Looks like it works! Thanks for the merge @electerious


Getting machine-translated prompts of xP3mt

Hi,
Thank you for the very interesting work and releasing the code. It is very helpful!
Is there a way I can get the machine-translated prompts per task?
For example, how would I get the Spanish (es) prompt for Paws-x only?

In the HuggingFace repo bigscience/xP3mt seems to contains the input, output pairs in Spanish for all the training tasks. Is there a way I can get the input, output pairs for Paws-x only?
In the creation script data/xp3/prepare_xp3_train.py, setting USE_ENGLISH_PROMPTS to False seems to load prompts in different languages from PromptSource, but PromptSource only has prompts in English for Paws-x (https://github.com/bigscience-workshop/promptsource/tree/main/promptsource/templates/paws-x)

Also, more generally, how do you do machine-translation for prompts if the language is from right-to-left instead of left-to-right or has different ordering like subject-object-verb instead of subject-verb-object? Would the target come before the input or would you reorder the sentences in the input (i.e premise or hypothesis) in the prompt? And if the target comes before the input, how would the model work since it generates from left to right?
Thank you,
Derek

Is there a way I can get the machine-translated prompts per task? / For example, how would I get the Spanish (es) prompt for Paws-x only?

The prompts are here: https://github.com/Muennighoff/promptsource/blob/xp3mt/promptsource/templates/paws-x/es/templates.yaml

Is there a way I can get the input, output pairs for Paws-x only?

You can just download the paws-x files: https://huggingface.co/datasets/bigscience/xP3mt/tree/main/es e.g. https://huggingface.co/datasets/bigscience/xP3mt/blob/main/es/xp3_paws-x_es_train_task_description-no-label_esmt.jsonl
Also see the usage guidelines here that may help: https://huggingface.co/datasets/Muennighoff/xP3x#usage

Also, more generally, how do you do machine-translation for prompts if the language is from right-to-left instead of left-to-right or has different ordering like subject-object-verb instead of subject-verb-object? Would the target come before the input or would you reorder the sentences in the input (i.e premise or hypothesis) in the prompt? And if the target comes before the input, how would the model work since it generates from left to right?

We use Google Machine Translate to translate the prompts and then just put them in the same place for all languages. For right-to-left languages like Arabic everything is the same (i.e. they are processed from beginning of sentence to the end). Usually browsers handle displaying it as right-to-left so we can treat it as left-to-right in the modelling phase.

Thank you for the quick response and the pointer. It is very helpful.
In the templates https://github.com/Muennighoff/promptsource/blob/xp3mt/promptsource/templates/paws-x/es/templates.yaml, I saw the metrics was Null, but it seems they have answer choices and the original prompt https://github.com/Muennighoff/promptsource/blob/xp3mt/promptsource/templates/paws/labeled_final/templates.yaml has Accuracy as a metric? Could I still use Accuracy as a metric for the machine-translated prompts?

Yes you can use accuracy. The metric field in that file is never used.

Great. Thank you for all your help!


Add welcome messages

Thank you for your very cool project.
I would like to suggest adding the ability to send a welcome message to the general chat with the ability to delete it after a specified period of time. Is it possible to implement this?

Not sure what welcome message you meant, but the system already has an optional startup message. It is off by default, but you can set it to any text you like, and it will send it to the group as it starts. I don't see why this message should be deleted after a specified period of time.
If you meant a welcome message for a new user who joined the group, in this case, I don't see how this is related to the spam protection functionality this project is trying to provide.

I think you are right. Thank you for your project.


Crash cheat

Hi Daniel, after the launch of the second card in MM, the osiris began to crash, by debugging I found out that it crashes setMaterialVarFlag

Please verify game files https://support.steampowered.com/kb_article.php?ref=2037-QEUH-3335

did not help, crash

Should now be fixed. Thanks for you report!

Thanks for the correction!
Good luck in the development of the project.


Hydration error in next.js with MUI

Steps to reproduce
I am using a <LoadingButton /> in my app. I can't reliably reproduce this. In most cases, it works fine. Sometimes it doesn't.
Current behavior
Button uses default MUI styling and ignores all the theme overrides I have upon a hard refresh. When navigating to the page via next.js routing, it works fine. Then if I refresh, the styles use the default MUI stylings. In the console I get the following warning:
[Error] Warning: Prop `className` did not match. Server: "MuiButtonBase-root MuiButton-root MuiLoadingButton-root MuiButton-contained MuiButton-containedPrimary MuiButton-sizeLarge MuiButton-containedSizeLarge MuiButton-colorPrimary MuiButton-fullWidth MuiButton-root MuiLoadingButton-root MuiButton-contained MuiButton-containedPrimary MuiButton-sizeLarge MuiButton-containedSizeLarge MuiButton-colorPrimary MuiButton-fullWidth css-sppx0e-MuiButtonBase-root-MuiButton-root-MuiLoadingButton-root" Client: "MuiButtonBase-root MuiButton-root MuiLoadingButton-root MuiButton-contained MuiButton-containedPrimary MuiButton-sizeLarge MuiButton-containedSizeLarge MuiButton-colorPrimary MuiButton-disableElevation MuiButton-fullWidth MuiButton-root MuiLoadingButton-root MuiButton-contained MuiButton-containedPrimary MuiButton-sizeLarge MuiButton-containedSizeLarge MuiButton-colorPrimary MuiButton-disableElevation MuiButton-fullWidth css-e1igr2-MuiButtonBase-root-MuiButton-root-MuiLoadingButton-root"
button
MuiButtonBase-root
ButtonBase
MuiButton-root
Button
MuiLoadingButton-root
LoadingButton
div
Styled(div)
Box
form
div
Styled(div)
Box
section
MuiContainer-root
Container
div
Styled(div)
Box
ContentWrapper
ContactFormSection
ContactUs
Contact
div
Styled(div)
Box
div
Styled(div)
Box
HeaderStateContext
DefaultLayout
ConfirmationDialogProvider
Component@
QueryClientProvider
ReactQueryWrapper
Component@
SnackbarProvider
RtlProvider
ThemeProvider
ThemeProvider
ThemeProvider
ThemeProvider
SettingsProvider
div
MotionComponent
LazyMotion
MotionLazy
App
AppLayout
Provider
Integrow
PathnameContextProviderAdapter
PureComponent@
ReactDevOverlay
Component@
AppContainer
Root
"
See more info here: https://nextjs.org/docs/messages/react-hydration-error"
	(anonymous function) (hydration-error-info.js:63)
	(anonymous function) (setup-hydration-warning.js:18)
	printWarning (react-dom.development.js:86)
	error (react-dom.development.js:60)
	warnForPropDifference (react-dom.development.js:9571)
	diffHydratedProperties (react-dom.development.js:10414)
	prepareToHydrateHostInstance (react-dom.development.js:12564)
	completeWork (react-dom.development.js:22176)
	completeUnitOfWork (react-dom.development.js:26591)
	performUnitOfWork (react-dom.development.js:26563)
	workLoopSync (react-dom.development.js:26461)
	renderRootSync (react-dom.development.js:26429)
	performConcurrentWorkOnRoot (react-dom.development.js:25733:89)
	workLoop (scheduler.development.js:266)
	flushWork (scheduler.development.js:239)
	performWorkUntilDeadline (scheduler.development.js:533)

In the screenshot you can see the difference. The fonts/styles are using the default MUI styles:

Expected behavior
Button loads with correct styles always
Context
No response
Your environment
  System:
    OS: macOS 15.0
  Binaries:
    Node: 20.14.0 - ~/.nvm/versions/node/v20.14.0/bin/node
    npm: 10.7.0 - ~/.nvm/versions/node/v20.14.0/bin/npm
    pnpm: 9.5.0 - ~/.nvm/versions/node/v20.14.0/bin/pnpm
  Browsers:
    Chrome: 126.0.6478.183
    Edge: Not Found
    Safari: 18.0
  npmPackages:
    @mui/lab: 5.0.0-alpha.171 => 5.0.0-alpha.171
    @mui/material: 5.16.4 => 5.16.4
    @mui/material-nextjs: 5.16.4 => 5.16.4
    @types/react: 18.3.3 => 18.3.3
    react: 18.3.1 => 18.3.1
    react-dom: 18.3.1 => 18.3.1

Tried in safari and chrome
Search keywords: loadingbutton hydration

We are also experiencing this issue, after updating emotion dependencies, we are getting hydration errors in styled MUI components. I raised an issue. @emotion/styled and other packages are a peer dependency of multiple MUI packages.

Amen plz we have this issue too

same here!

Same problem here with Nextjs Pages router. For anyone looking for a fix, I recommend trying to override "@emotion/serialize" as mentioned in the linked issue by @ddembo

I don't know if my issue is similar, but I'm facing another hydration error. These are the versions I'm using:
"@emotion/cache": "11.14.0",
"@emotion/react": "11.14.0",
"@emotion/server": "11.11.0",
"@emotion/styled": "11.14.0",
"@mui/material": "6.2.0",
"@mui/material-nextjs": "^6.2.0",
"@mui/system": "6.2.0",
"next": "15.1.0"

I'm using pages router, and the functions/components from @mui/material-nextjs/v15-pagesRouter are set up correctly in code.


Updated Navbar of Chapters and Events Page

Fixed issue #37

On clicking Chapters position of 'Blogs' and 'Chapters' is changing.
On clicking Events it's disappearing from the navbar when we're on the Events page.
Updated Both the page's navbar as follows -
At Home -
Before & After-

On the Chapters Page -
Before -

After -

On the Events Page -
Before -

After -

Thanks for contributing to our repo, we will review and merge it soon :)


feature -  handle error recent

Github Issue URL/Tags (required)
What's this PR do? Please give a technical summary (required)

[x] show alert error

Any references (stackoverflow …) (optional)

:+1: There are no linter violations.


Elak/lang1

What does this PR do? Please provide some context
Avoid the duplicates from the Preferred Language drop down
Where should the reviewer start?
Register as a new user user in the home page
How can this be manually tested? (brief repro steps)
Before: The Preferred Language drop down has few duplicates values
After: No duplicates in the language list
What are the relevant TFS items? (list id numbers)
Bug 100756
Definition of done:

[ ] Title of the pull request is clear and informative
[ ] Add pull request hyperlink to relevant TFS items
[ ] For large or complex change: schedule an in-person review session
[ ] This change has appropriate test coverage

Reminders BEFORE merging

Get at least two approvals
If you're merging from a feature branch into the development branch then "flatten" or "squash" commits
If merging from the development branch into master (or porting changes from upstream) then use github's UI to get review feedback, but use the git command line interface to complete the actual merge.

Reminders AFTER merging

Delete the remote feature branch
Resolve relevant TFS items
(reverse merge) If you merged from the development branch into master then check to see if there are any changes in master that can be merged down to the development branch (like hotfixes, etc). In this case, use github's UI for feedback and the git command line interface for the actual merge.

@ElakkiyaMohanRajan,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot