RFC/PROPOSAL: add user_id to event.schema

What/Why
What are you proposing?
We propose that the event schema contain a dedicated user ID field so that consumers of UBI data can disambiguate between client_id and user_id and better standardize what we recommend the integrators track.
What users have asked for this feature?
We have spoken to data analysts who work on analyzing user behavior and they mentioned that the terms client_id, session_id and user_id have distinct meanings that cannot be merged.
What problems are you trying to solve?
The client_id in analytics parlance usually refers to a hash of the browser and its version. This would mean that if multiple unauthenticated users were using the same browser version, their activity would fall under the same id. The current approach has another caveat: if a user ID is logged in the client_id field, then the behaviors of unauthenticated users won't be logged. With this proposal, there won't be such a confusion any more. In case of an unauthenticated user, the user_id can remain empty.
Are there any security considerations?
No additional security impact as the existing recommendation was to already track the user ID under the client_id field
Are there any breaking changes to the API
No
What is the user experience going to be?
Customer can configure and analyze the user-behaviors along an additional axis that is well-separated from client_id.
Are there breaking changes to the User Experience?
No
Why should it be built? Any reason not to?
This will allow the separate customer personas (front-end developer and behavior analyst) to be able to perform their tasks better with less coordination required as it reduces ambiguity around what attributes are tracked in which fields.
What will it take to execute?

Merging this pull request
Documentation and samples updates.

Any remaining open questions?
No.

Makes sense - I'd consider making this nullable explicitly i.e.,
type": ["string", "null"]

I think this makes sense as well. Users would probably outlive several sessions and I imagine correlating data across disparate sessions would be troublesome otherwise.

@AnkitSiva would you be willing to update the PR for the null concept.   I did a bit of googling and yeah, you need to explicitly have the data type "null": https://turbo360.com/blog/specifying-json-schema-elements-null-in-logic-apps

For a moment I thought, hey, if this isn't in the required list, then that would mean it is null.  However, I can imagine that you might have user_id explicitly set to null, versus an abscense of the attribute meaning null..   So yeah, let's add the null data type, and not add it to the required list.

@AnkitSiva I'm thinking that the common pattern for folks using this would be to say "I am using user_id", and hten, for all the places where user_id is null, that they would set it explicitly null, versus skipping the attribute...
How about, for now, we just make the change as you have it, and look to dig in more on @miike  suggestion...

@dtaivpp @miike if the nullable thing is something we want to pursue, let's create a fresh PR for that.   I am somewhat under the gun to get the 1.1 release out the door in August...   and it's the 31st of August....


Enabling teslaMate in Sentry Mode increases battery consumption

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
Sentinel mode case with teslaMate on increases battery consumption. It consumes 3% more power than in I don't have teslaMate turned on.
Expected Behavior
First of all, I'm sorry for the delay, because of my lack of English and programming skills, I may not have seen the relevant documents. The following description is translated by translation software, it may be a bit strange, sorry.
Sentinel mode case with teslaMate on increases battery consumption. It consumes 3% more power than in I don't have teslaMate turned on.
Is it because with Sentinel Mode on, the vehicle will not be in sleep mode, causing the teslaMate to poll the query more often, which leads to an increase in power consumption.
I see that the database is now updating data once every 5 seconds, is it because the vehicle is in online mode that the polling frequency is so high.
Additionally, these data requests need to go to the vehicle location, whether this raises the power consumption.
Steps To Reproduce
No response
Relevant log output
null

Screenshots
No response
Additional data
No response
Type of installation
Docker
Version
latest

Sentry mode results in the car not going to sleep, independent of TeslaMate

Sentry mode results in the car not going to sleep, independent of TeslaMate哨兵模式导致汽车无法进入睡眠状态，与 TeslaMate 无关

So using the TeslaMate without going into sleep mode consumes the same amount of power as using the TeslaMate in sleep mode right?

In SentryMode the car is always awake, cameras are on, MCU is on (tesla tries currently to reduce the power consumption in Sentry Mode, in Cybertruck this has been succesfull).
The car will use ~300W/h in Sentry Mode, independend of TeslaMate

In SentryMode the car is always awake, cameras are on, MCU is on (tesla tries currently to reduce the power consumption in Sentry Mode, in Cybertruck this has been succesfull). The car will use ~300W/h in Sentry Mode, independend of TeslaMate

Thanks I got it. Perhaps the TeslaMate has statistics on the sentry mode state, with some sleep mode-like special handling for that state?

TeslaMate detects SentryMode, you can see an corresponding icon on the webpage.


[NOT AN ISSUE] Update to 1.20.1

Hi!
¿Any news or plans to update it to 1.20.1?
Thanks!

yes, you reminded me to update the mod. It should be available on curseforge and modrinth now


Implement Rez for Ayon

Is your feature request related to a problem? Please describe.
Ayon and even OpenPype had to handle dependencies, versions of packages and distributing vendored binaries. With Ayon resolving versions and its dependencies becomes more dynamic due to being able to mix and match addons which in itself can require specific versions of other addons.
As a part of this some of the work for Ayon has been involving resolving these dependencies and building an environment for launching a specific version of Ayon, etc. and has with OpenPype (v3) involved managing environments for Applications and Tools when launching even specific assets in a project.
This addon (package) management and dependency resolving with version ranges is exactly what Rez is built to solve and I feel like before we set of implementing complex resolving algorithms for the addons and their 'dependencies' we should maybe avoid time spent there and instead spent time on relying on Rez as much as we can.
By adopting Rez we can also get other benefits like:

Setting up a central repository of package versions (e.g. ffmpeg, ocio, otio, python packages) without requiring each build of Ayon to embed all those dependencies.
It can support local caching of having the dependencies on a network share but copy certian packages (or all) locally to improve runtime performance. This would then also automatically become possible for things like "tools" where e.g. redshift could be loaded through ayon configuration and its resolving could use that Redshift locally to improve the startup running time for the renderer.
Since Rez is built to resolve dependencies like this we can use its feature set to also help debug dependency problems, etc. without again having to re-write and manage our own.
It can even help the "version resolving" we are using for OpenPype itself currently by turning OpenPype ZIP packages into rez packages, etc. (e.g. at deployment time or alike) to avoid maintaining our own version resolving logic and be able to rely on Rez's mechanisms which have a much stronger backbone in production already.

Describe the solution you'd like
Have Ayon use rez to resolve the environment to launch an application in would be one first step.
I'd say the final goal would be to be able to run even Ayon itself through rez so from there you could e.g. pick a particular Ayon version to start with too - but that doesn't have to be a first priority I'd say. Being able to pick Ayon version through rez would open up e.g. Deadline resolving to a specific ayon version to also just move through rez to get the right package.
Describe alternatives you've considered
We've had Applications and Tools in OPv3 but with separating all addons for Ayon and them versioning independently with dependencies (requirements) to other addons will start complicating the version resolving logic that needs to be written.
I'd say we are getting to a point where Rez might be best way forward into development time and what we gain from it in the end.
Additional context
Rez feature requests have come up before
Even before Ayon having Rez support has come up as a request multiple times by multiple users on Discord:

@instinct-vfx mentioned it recently with regards to Ayon and automatic downloads of addons
A Rez thread on Ynput community discord showing interest from @davidlatwe @Tilix4 @Minkiu with some developers mentioning they had working prototypes with OpenPype like @Anti-Distinctlyminty
Some implementation discussion here and here
There have also been requests to keep it separate with some answers by @mkolar at the time about OP philosophy
And last but not least some questions about Rez package versus JSON configs from back in 2020

Rez is supported by Academy Software Foundation
Rez has ASWF support and used by a variety of bigger studios in the animation industry.
[cuID:OP-5252]

Just referencing this comment which describes a use case where version and dependency management through Rez could offer an improvement.

I think we've decided to go with the Rez (or at least try it) for handling Ayon addon dependencies as there is no reason (and no power) to implement some custom package manager just for Ayon. The issue with P4 mentioned is also great example of thing that couldn't be solved easily without something like Rez. Thanks for wrapping all those arguments to one place. We'll need to start working on it in very near future.

We'll need to start working on it in very near future.

Would be great if we could set up a team for that with maybe some scheduled meetings here and there to brainstorm and get the right heads together - we can also invite some of the Rez devs or a user with lots of experience to maybe aid in the brainstorm in a session here and there and help shape the future of Rez x Ayon.

I've worked a very short time with rez before leaving my previous studio, and it seemed very nice. I also think it could be a great solution we could rely on. My main expectation is for it to be compatible with remote artists, who are connected only through a OP sftp for example. The local caching system might solve this issue.

Hi @BigRoy and @antirotor , rez TSC member here. I already see common faces/names in this thread (including another TSC member, @instinct-vfx) , so you are probably in good hands. But I just wanted to drop by amd re-iterate that we will be happy to discuss and provide guidance and help and even brainstorm on how rez coule be used and integrated in Ayon.
We have a Slack channel that is very active and we also use GH discussions. We also have monthly open meetings where you can come and ask questions or show us what you have and ask for our opinion interactively.
Let us know how we can help!

Hello all,
I created a draft PR with a potential approach to using rez in the back end:
https://github.com/ynput/ayon-backend/pull/29
Any feedback provided is appreciated.
The elevator pitch is: Specify the path to a Rez repo via the settings, then a RezRepo class that abstracts some of the common rez actions and ties it with the current implementation on how to load addons.

Hello everyone,
I'd like to pick this conversation back up as I'm currently trying to plan for AYON + rez.
Current Workflow
I'm a little unclear on the exact workflow so please tell me if this sounds right:
Server
The current workflow described in the docs:

Virtual environment is created and dependencies installed. For example Resolve or all the other dccs in OpenPype
Third-party binaries are downloaded (https://github.com/ynput/ayon-third-party)
Python binaries are built
Addons, get zipped up (server + client), uploaded to the server.

Now addons are available on the sever and can be added to a bundle.
Client

AYON launcher is used to query the list of required plugins in the current bundle and downloads and distributes them.
Launcher dynamically loads the right addon versions with the dependencies from the zip files.

Rez Workflow
This is for a complete rez workflow, not only on the server but also on the client side.

This allows us to run rez on a studio server and dynamically distribute updates to clients. Everyone is always using the exact same setup and not using any local installs.
This allows for more command line tools when launching through the UI is not yet supported/wanted/needed. (For example rez-env maya ayon)
This integrates nicely with binaries, and other plugins outside AYON's pipeline. For example it resolved python conflicts with other plugins that need to be loaded.
This allows different python environments per dcc. If for whatever reason different dccs would require different packages, that is currently not supported with the venv installs, correct?

Server

The part of the api that is scanning the folders for zipped addons is rewritten to use a rez repo and provide packages that are tagged as plugins for ayon-server as addons.
Applications Addon is replaced by a rez addon that provides an interface to create applications. Instead of pointing to a maya binary one could point to something like rez-env maya -- maya. (Unclear how project overrides will happen just yet.)

Client

AYON launcher is used to query the list of required plugins in the current bundle (equivalent of a context in rez).
rez loads this "ayon.rxt" context and launches.
On application launch, the commands defined in the rez addon (above) will be executed.
In the example above, it could make sense that rez-env maya loads maya without ayon, and the launcher dynamically adds ayon to the environment to be resolved.

Next Steps
It is my understanding that in this rez workflow we would need these changes:

[ ] ayon-backend: add option to replace addon library with rez library (Essentially this PR https://github.com/ynput/ayon-backend/pull/29)
[ ] rez-addon: addon to replace applications addon specifying rez contexts and commands to launch applications through UI
[ ] ayon-launcher: add option to launch ayon in rez mode, that essentially loads a dynamically created context based on the bundle. (ayon bundle ~= rez context)

Please let me know if I got this right and if my plan makes sense, thank you all!

Please let me know if I got this right and if my plan makes sense, thank you all!

You've got it right, that is the plan. Thanks for the summary!


Remove unwrap_none/expect_none.

We're not going to stabilize Option::{unwrap_none, expect_none}. (See https://github.com/rust-lang/rust/issues/62633.) This removes the usage of those unstable methods from miri.

We're not going to stabilize Option::{unwrap_none, expect_none}

That's a bummer, I felt it made the code here a lot cleaner. :(

Another alternative is to use map(|what| panic!("expected none, got {:?}", what)) instead of using asserts. The advantage of this is the chaining.

Another alternative is to use map(|what| panic!("expected none, got {:?}", what)) instead of using asserts. The advantage of this is the chaining.

Yeah that's what I did in rustc to replace expect_none, which already had an error message. But in miri, these were all unwrap_none without any message, and I don't have enough context to come up with the right error message myself. (e.g. "allocation with id {} already exists as {}", etc.)

Putting this on hold until we figure out a better alternative for insert().unwrap_none(): https://github.com/rust-lang/rfcs/issues/3092
Thanks for the feedback.

Putting this on hold until we figure out a better alternative for insert().unwrap_none(): rust-lang/rfcs#3092

Thanks for opening the issue!
If the libs team wants to get rid of these functions, I certainly won't block that. I can also help figure out panic messages for .map(|_| panic!), though I have to say I view that pattern as more of a hack since the intent is only clear on second sight. But it is probably still nicer than adding new let-bindings.


Adapting for use with managed control plane

I have an EKS cluster and am hoping to adapt this to run as a second scheduler since I can't edit the default kube-scheduler as called for in your installation instructions (I don't believe, but correct me if I am wrong).
I have edited the yaml slightly to be in line with the guide at the below link:
https://kubernetes.io/docs/tasks/administer-cluster/configure-multiple-schedulers/
But it doesn't seem to be working (will admit I knew this was wishful thinking). Any ideas what else I need to do? I am very new to go so struggling to dig into the source code.
kind: ServiceAccount
apiVersion: v1
metadata:
  name: gpu-scheduler
  namespace: kube-system
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  name: gpu-scheduler-as-kube-scheduler
subjects:
- kind: ServiceAccount
  name: gpu-scheduler
  namespace: kube-system
roleRef:
  kind: ClusterRole
  name: system:kube-scheduler
  apiGroup: rbac.authorization.k8s.io
---
apiVersion: apps/v1 #extensions/v1beta1
kind: Deployment
metadata:
  labels:
    component: scheduler
    tier: control-plane
  name: gpu-scheduler
  namespace: kube-system
spec:
  selector:
    matchLabels:
      component: scheduler
      tier: control-plane
  replicas: 1
  strategy:
    type: Recreate
  template:
    metadata:
      labels:
        component: scheduler
        tier: control-plane
    spec:
      serviceAccountName: gpu-scheduler
      containers:
      - image: registry.cn-hangzhou.aliyuncs.com/acs/k8s-gpu-scheduler:1.11-d170d8a
        name: gpu-scheduler
        env:
        - name: LOG_LEVEL
          value: debug
        - name: PORT
          value: "12345"
      hostNetwork: true
      tolerations:
      - effect: NoSchedule
        operator: Exists
        key: node-role.kubernetes.io/master
      - effect: NoSchedule
        operator: Exists
        key: node.cloudprovider.kubernetes.io/uninitialized
      nodeSelector:
         node-role.kubernetes.io/master: ""

I need to implement a full second scheduler don't I...

I think it can work only when Kubernetes default scheduler can be configured.

@cheyang , why?

@ide8 afraid not, we decided on a different setup. I did see this but haven't tried it:
https://github.com/Deepomatic/shared-gpu-nvidia-k8s-device-plugin
The reason it won't work is that in a managed service you don't have access to the scheduler config to modify it (see installation instructions, this is a requirement).

Any updates on this? I was hoping by running a second scheduler we could simply call out to the second scheduler and apply extenders to it.

@tlives any updates from your end on this?


Can't record or show visits on Dashboard (closed #201)

Moved to CE recently and dashbord stopped updating or logging visits on websites.  Coming from #201 because my issue persists.
That's what I get from logs:
plausible_events_db-1  |  [ 1 ] {} <Warning> Context: Delay accounting is not enabled, OSIOWaitMicroseconds will not be gathered. You can enable it using `echo 1 > /proc/sys/kernel/task_delayacct` or by using sysctl.
plausible_events_db-1  |  [ 1 ] {} <Error> Application: Disabling cgroup memory observer because of an error during initialization: Code: 107. DB::Exception: Cannot find cgroups v1 or v2 current memory file. (FILE_DOESNT_EXIST), Stack trace (when copying this message, always include the lines below):
plausible_events_db-1  |
plausible_events_db-1  | 0. DB::Exception::Exception(DB::Exception::MessageMasked&&, int, bool) @ 0x000000000cbc851b
plausible_events_db-1  | 1. DB::Exception::Exception<>(int, FormatStringHelperImpl<>) @ 0x00000000076614c3
plausible_events_db-1  | 2. DB::CgroupsMemoryUsageObserver::CgroupsMemoryUsageObserver(std::chrono::duration<long long, std::ratio<1l, 1l>>) @ 0x000000000cce452e

Could be related to a wrong configuration in Nginx?
proxy_cache_path /var/run/nginx-cache/jscache levels=1:2 keys_zone=jscache:100m inactive=30d  use_temp_path=off max_size=100m;

server {
        listen 443 ssl http2;
        server_name stats.mydomain.com;
        include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
        ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot

       resolver <IP_ADDRESS>;
    set $plausible_script_url https://stats.mydomain.com/js/script.js; # Change this if you use a different variant of the script
    set $plausible_event_url https://stats.mydomain.com/api/event;

        location / {
                proxy_pass http://<IP_ADDRESS>:8000;
                proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        }

    location = /js/script.js {
        proxy_pass $plausible_script_url;
        proxy_set_header Host stats.mydomain.com;

        # Tiny, negligible performance improvement. Very optional.
        proxy_buffering on;

        # Cache the script for 6 hours, as long as plausible.io returns a valid response
        proxy_cache jscache;
        proxy_cache_valid 200 6h;
        proxy_cache_use_stale updating error timeout invalid_header http_500;

        # Optional. Adds a header to tell if you got a cache hit or miss
        add_header X-Cache $upstream_cache_status;
    }

    location = /api/event {
        proxy_pass $plausible_event_url;
        proxy_set_header Host stats.mydomain.com;
        proxy_buffering on;
        proxy_http_version 1.1;

        proxy_set_header X-Forwarded-For   $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header X-Forwarded-Host  $host;
    }

        add_header X-Content-Type-Options nosniff;
        add_header X-XSS-Protection "1; mode=block";
        add_header Referrer-Policy "no-referrer-when-downgrade" always;
        add_header Content-Security-Policy "default-src * data: 'unsafe-eval' 'unsafe-inline'" always;
        add_header Strict-Transport-Security "max-age=31536000; includeSubDomains; preload" always;

#    ssl_certificate /etc/letsencrypt/live/stats.mydomain.com/fullchain.pem; # managed by Certbot
#    ssl_certificate_key /etc/letsencrypt/live/stats.mydomain.com/privkey.pem; # managed by Certbot

    ssl_certificate /etc/letsencrypt/live/stats.mydomain.com/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/stats.mydomain.com/privkey.pem; # managed by Certbot

location = /robots.txt {
  add_header  Content-Type  text/plain;
  return 200 "User-agent: *\nDisallow: /\n";
}

location ~ ^/.* {
        proxy_pass http://<IP_ADDRESS>:8000;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header Connection 'upgrade';
        proxy_set_header Upgrade $http_upgrade;
        proxy_http_version 1.1;
}

}

docker-compose.yml:
    image: postgres:16-alpine
    restart: always
    volumes:
      - db-data:/var/lib/postgresql/data
    environment:
      - POSTGRES_PASSWORD=postgres
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -U postgres"]
      start_period: 1m

  plausible_events_db:
    image: clickhouse/clickhouse-server:<IP_ADDRESS>-alpine
    restart: always
    volumes:
      - event-data:/var/lib/clickhouse
#      - ./clickhouse/clickhouse-config.xml:/etc/clickhouse-server/config.d/logging.xml:ro
#      - ./clickhouse/clickhouse-user-config.xml:/etc/clickhouse-server/users.d/logging.xml:ro
#      - ./hosting/clickhouse/clickhouse-config.xml:/etc/clickhouse-server/config.d/logging.xml:ro
#      - ./hosting/clickhouse/clickhouse-user-config.xml:/etc/clickhouse-server/users.d/logging.xml:ro
      - event-data:/var/lib/clickhouse
      - event-logs:/var/log/clickhouse-server
      - ./clickhouse/logs.xml:/etc/clickhouse-server/config.d/logs.xml:ro
      # This makes ClickHouse bind to IPv4 only, since Docker doesn't enable IPv6 in bridge networks by default.
      # Fixes "Listen [::]:9000 failed: Address family for hostname not supported" warnings.
      - ./clickhouse/ipv4-only.xml:/etc/clickhouse-server/config.d/ipv4-only.xml:ro
    ulimits:
      nofile:
        soft: 262144
        hard: 262144
    healthcheck:
      test: ["CMD-SHELL", "wget --no-verbose --tries=1 -O - http://<IP_ADDRESS>:8123/ping || exit 1"]
      start_period: 1m

  plausible:
#    image: plausible/analytics:v2.1.4
    image: ghcr.io/plausible/community-edition:v2.1.4
    restart: always
    environment:
      - DISABLE_REGISTRATION=true
    command: sh -c "sleep 10 && /entrypoint.sh db createdb && /entrypoint.sh db migrate && /entrypoint.sh run"
    depends_on:
      plausible_db:
        condition: service_healthy
      plausible_events_db:
        condition: service_healthy
#      - mail
    volumes:
      - plausible-data:/var/lib/plausible
    ulimits:
      nofile:
        soft: 65535
        hard: 65535
    ports:
      - <IP_ADDRESS>:8000:8000
    env_file:
      - .env

volumes:
  db-data:
#    driver: local
  event-data:
#    driver: local
  event-logs:
  plausible-data:

I've reopened https://github.com/plausible/community-edition/issues/201


[FRONT] :sparkles: add country select for sms field and lang menu

https://github.com/Instant-Visio/InstantVisio-WebApp/issues/76

There is a lot of changes because i push flag svg icons (220)


Chat doesn't load backlog when joining a channel

definitely possible, landscape does it

Fixed! good catch


Can not cast (using pipe) on aggregated output?

I think this should work. Doing similar operations on pre-aggregated columns does work.
In [58]: df = pd.DataFrame(np.random.randn(10, 1), columns=['x']).reset_index().rename(columns={'index': 'i'})

In [59]: df['a'] = (df['x'] * 10).astype(int)

In [60]: q = to_sql("""
    ...: from df
    ...: filter s"x > -12"
    ...: aggregate [
    ...:   count = count,
    ...:   range = s"max(a) - min(a)",
    ...: ]
    ...: derive [
    ...:   c = (range | as double) / 10
    ...: ]
    ...: """); print(q); duckdb.query(q).df()
Traceback (most recent call last):

  File ~/anaconda3/envs/3.10.4/lib/python3.10/site-packages/IPython/core/interactiveshell.py:3397 in run_code
    exec(code_obj, self.user_global_ns, self.user_ns)

  Input In [60] in <cell line: 1>
    q = to_sql("""

  File <string>
SyntaxError: Error { span: Some(Span { start: 115, end: 121 }), reason: Simple("Unknown variable `double`"), help: None }

Thanks @cottrell, this is a bug, sorry about that.
Here's an even smaller example:
func add x y -> x + y

from x
select [a]
derive [
  c = (a | add b)
]

Syntax error!
Error:
   ╭─[:6:16]
   │
 6 │   c = (a | add b)
   ·                ┬
   ·                ╰── Unknown variable `b`
───╯

This is quite surprising; I'm guessing the select is messing with the name resolution of the function in the old name resolver.
If this is blocking you, I can look later today and see whether there's a quick fix. If it's not, it'll be solved by the new name resolver that we're merging in the next couple of weeks.
Thanks a lot for posting the error, this isn't great from PRQL pov so we appreciate your patience.

No worries, I think i've worked around it by doing something like x * 1.23 / 1.23 or similar which must rely on some inspection.

I believe this is now closed:
from df
filter x > -12
aggregate [
  count = count,
  range = (max a) - (min a),
]
derive [
  c = (range | as double) / 10
]

SELECT
  COUNT(*) AS count,
  MAX(a) - MIN(a) AS range,
  CAST(MAX(a) - MIN(a) AS double) / 10 AS c
FROM
  df
WHERE
  x > -12


pull request for e2e test at 01/07/2017 23:15:10

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


SHM

Opening this for comments:
Implementation of:

shmget
shmat
shmdt
shmctl

This is now a full PR request @jesings @TristanB22
Please review again. Thanks!


paper can't find.

Thank you for your excellent work. May I have a look at your paper? I can't find the original paper on the Internet.

Hi @linqika95,
Thank you for your interest. The paper is under revision now and will be released asap (I will also notify you in this issue).

Hi @linqika95,
We just release our arXiv version:
https://arxiv.org/abs/2006.09136
Thank you again for your interest.


Fix changing CesiumGlobeAnchor position while disabled

As noted in #476, the ellipsoid changes added a reference to _georeference in the longitudeLatitudeHeight property on CesiumGlobeAnchor. This is fine for most purposes, as _georeference will be set by the time longitudeLatitudeHeight is used - unless the CesiumGlobeAnchor is disabled. This change just makes sure the georeference has been found before trying to access it.

Looks good other than that one thing. Please remember to update CHANGES.md, too.

@kring Ashley probably won't be able to get back to this before the release (since she's out).
Would it be okay if you or @csciguy8 want to implement the feedback + merge this to main? (I will also be out, but can try to support if needed)

Yeah good call @j9liu. I'll make that small change and merge it.

???

@kring when will i be able to update the cesium unity package to receive this fix ?

We're planning to release it tomorrow. You can grab a build from CI in the meantime if you like.

CI ?

Continuous Integration. The plugin is built on GitHub Actions on every commit. If you're not familiar, better to just wait for the release.


Add filtering feature to get all programs endpoint

Purpose

The purpose of this PR is to fix #112
Goals

Add filtering feature to GET /programs endpoint
Approach

Updated the endpoint to support filtering states
Checklist

[x] This PR doesn't commit any keys, passwords, tokens, usernames, or other secrets.
[x] I have read and understood the development best practices guidelines ( http://bit.ly/sef-best-practices )
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation

Related PRs

N/A
Test environment

Ubuntu 20.04
OpenJDK 1.8
Learning

N/A

@Piumal1999 Is this the same PR that just got merged?

Yeah. That was reverted because the branch was wrong.

Oh okay


julius was installed with name "julius.dSYM" on Mac OS X

Julius rev.4.3.1
Mac OS X 10.6.8 (Snow Leopard)
Mac OS X 10.11.3 (EL Capitan)
*** Build ***
./configure
make
sudo make install
Build with no error
/usr/local/bin/julius.dSYM is work.

Check  http://stackoverflow.com/questions/17743993/dsym-files-generated-from-command-line-mac for a discussion on where this file might have come from. Does it provide a clue?

No.
"julius.dSYM" is executable file. It is not a  dSYM file.

The configure script automatically set executable file suffix, by actually testing compilation of a test code and see its output file.  Thus, it seems that it is a problem of your compiler, not Julius configuration.  What kind of compiler are you using?


Add dismiss/reopen notification button

It should be possible to dismiss or re-open any single notification within syslog. This should be done by ajax requests.

done.


Problems with overloading to FilePath

import           BasicPrelude hiding (find,(</>))
import qualified Control.Foldl as Fold
import qualified Prelude
import           Turtle

copyExtfiles :: Text -> IO [()]
copyExtfiles filext = do
  files <- fold (find (star anyChar *> "." *> text filext) ".") Fold.list
  let dir = fromText $ "data__" ++ filext
  mkdir dir
  zipWithM cp files $ map ((dir </>) . fromText . show) [1..]

tmp :: IO ()
tmp = mkdir "data"

I have to use fromText in copyExtfiles, but not in tmp

This has nothing to do with do notation.
Also, the title is misleading.  This type-checks, but gives an unexpected result.  I'm guessing you tried this and you got a slash inserted in between the "data_" and fileext.
I consider this a bug in the FilePath implementation from system-filepath.  The reason I consider it a bug is that I believe that any type that implements IsString and Monoid should satisfy these two laws:
fromString (str1 <> str2) = fromString str1 <> fromString str2

fromString mempty = mempty

However, as you discovered the FilePath type does not obey the first law, leading to the confusing behavior of inserting a slash.
Fixing the FilePath type is outside the scope of the turtle library.  I may eventually introduce a new file path type later on (See #54), but for now we have to live with the bugs of the current FilePath type.

Whoops, I realized that I made a mistake.  There was a type error, too.  The other problem is that fileExt is a Text, so at some point you have to convert it to a FilePath explicitly, either before concatenating it with a string literal or after.

No such thing as Text Overloading?

Haskell overloads literal values (like numeric literals and string literals) by representing them using a type class:
1 :: Num a => a

"foo" :: IsString a => a  -- With OverloadedStrings enabled

Under the hood it's as if you had written:
fromInteger (1 :: Integer) :: Num a => a

fromString ("foo" :: String) :: IsString a => a

So if you want to overload a string without using a string literal then you need to wrap the string with fromString.  In the case of Text, you would have to additionally unpack the value, too:
fromString . unpack :: IsString a => Text -> a

I found fromShow :: (Show a, IsString b) => a -> b -- Defined in ‘BasicPrelude’
copyExtfiles :: Text -> IO [()]
copyExtfiles fileExt = do
  files <- fold (find (star anyChar *> "." *> text fileExt) ".") Fold.list
  let dir = fromShow $ "data__" ++ fileExt
  mkdir dir
  zipWithM cp files $ map ((dir </>) . fromShow) [1..]

That might not do the correct thing, though.  The Show instance of Text will produce quotes around the string, so you may get a file name with quotation marks.

Yep, just figured that out. No Holy Grail for now.


Give silicons proper lobby/character editor previews

No more naked dummies, properly show a borg/AI sprite now.
This means taking the JobEntity into account when spawning the dummy. For AIs I had to add a "JobPreviewEntity" field because they'd look like a posibrain otherwise. AI therefore uses a custom dummy entity I defined.
Also I had to add some margins to the UI, because otherwise the 32x32 sprite of the AI would look bad.

:cl:

tweak: Silicons now have a proper preview in the lobby/character editor.

now all we need is https://github.com/space-wizards/space-station-14/pull/31303 and silicons will finally be playable :godo:


[Noetic] skyway fails to build on arm64 and armhf

Hey @nakakura,
It looks like skyway isn't building on some platforms:

Ubuntu Focal arm64
Ubuntu Focal armhf

I'm planning to add all chronically failing packages to per-platform blacklists later this week.
That just means the buildfarm won't try to build them every day.
When all issues causing the build failures are resolved, please make a PR to the production branch on ros_buildfarm_config removing it from the package_blacklist:

release-arm64-build.yaml
release-armhf-build.yaml

Sorry for the delay in confirming. Noted. I will correct it.


update electron

[x] update electron to 1.2.2
[x] install devtron
[x] change tab-bar flex stuff. was totally broken in new chrome. unclear why we need flex:2 and flex:0 here at all
[x] change depenency on purepack and framed-msgpack. with a dummy msgpack dependency (like we do in react-native) we can use mainline purepack and a smaller-diff from master of framed-msgpack. I think we could actually get on master but need to talk to max about getting this pr merged in (rn need some small changes to get it to work still, so we'll diverge from them for a short time)

@keybase/react-hackers

ok, to setup react devtools do this (with your homedir, i think full paths are required)
KEYBASE_DEV_TOOL_EXTENSIONS '/Users/chrisnojima/Library/Application Support/Google/Chrome/Default/Extensions/fmkadmapgofadopljbjfkapdkoienihi/0.14.11_0'

@keybase/react-hackers bump

:+1:


Bump sys-info dependency version

I'm creating this PR because the 0.8 version of sys-info fixes a bunch of bugs and notably a compilation error on Android.

Thank you. Unfortunately, the build now breaks on Windows.

I've created a PR for that in the sys-info repository: https://github.com/FillZpp/sys-info-rs/pull/87
So when that's merged and released I'll update this PR.

Thank you.


cmd/go: replace directives are not thoroughly documented

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

$ go version
go version devel +f0c383b833 Wed May 1 16:53:19 2019 +0000 linux/amd64

Does this issue reproduce with the latest release?
Yes
What did you do?
Read go help modules and go help go.mod.
What did you expect to see?
Some discussion of what replacements are and what they do.
What did you see instead?
The only documentation I can find is these lines in go help go.mod:
	replace bad/thing v1.4.5 => good/thing v1.4.5

	replace, to replace a module version with a different module version.
Exclude and replace apply only in the main module's go.mod and are ignored
in dependencies.  See https://research.swtch.com/vgo-mvs for details.

I think there's probably more to say about how replace works. For example, it doesn't explicitly state that the thing to replace is on the left side of the arrow. It also doesn't mention that the version on the left is optional.

Hello @heschik Can I pick up this task

@jayconrod or @bcmills would be the ones to review it, and they might be pretty busy getting 1.13 ready, so there might be a bit of delay on the review. For my part I say go for it.

A CL to document the existing behavior would be fine, but note that for Go 1.14 we're planning to both revamp the semantics of replace directives (#26904) and reorganize the modules documentation.

We should also note that replace replaces the source code of the given version, rather than retargeting requirements on the given version to instead require something else.

I guess we can close this now the cmd/go just links to https://go.dev/ref/mod for documentation, which has a dedicated replace section https://go.dev/ref/mod#go-mod-file-replace


Duplicated subscription for channel

We discovered in app logs, after application lost connection, after reconnect  pusher automatically recover connection and make subscribe to channels.
After some reconnects and application return from background, the event from channel can be duplicated.
Steps to reproduce

put network off \ on
put app in background \ open from background

Expected behavior
no duplicated events
Actual behavior
duplicated events
Any improvements you suggest
verify subscribe to channel after reconnect.
...
Using library: Swift package
Pusherswift 10.1.4

Is your code also creating a new connection / subscription when the network/app is restored?
The library will automatically reconnect to our service and subscribe to previous channels when network is restored so there is no need to manually take these actions.
Can you open the debug console and run the test? I'd be interested to see how many connections/subscriptions we see reported there


[CUDA][TVM] fix constructing invalid command line string for nvcc

This PR fixes the following problem:

options append to cmd as char list
nvcc raises an error (No input files specified) when any string (options in this case) exists between output filename and input filename

@merrymercy Thank you for your comment. I addressed and locally confirmed it. Could you review this again?


How to convert a PHAsset object to YPMediaItem? Is there a way to do this?

Hi,
I have an object of PHAsset and want to covert that to an object of YPMediaItem because I have an array of YPMediaItem.
Need urgent help!!
Thanks in advance

Hi @s4cha @NikKovIos
Please help on this. This is urgent. I have to launch the app and just waiting for this.
I am using - pod 'YPImagePicker', '~> 3.4.0' as the project does not supports above Swift 4.0
Thank you

Hello! I don't remember if it supports the initialization with PHAsset in 3.4.0 version. If bo5, you can copy the cureent project and translate to swift 4 by yourself. In YPMediaItem you would find initializators with PHAsset.

Hi @rahulrvarma I'm afraid3.4.0 version didn't support initializing a YPMediaItem with a PHAsset. This is only supported in later versions. My best bet would be for you to integrate the library manually with the code so that you can edit it to your needs.
Hope it helps

There is 2022 year outside🎉 Old outdated issues are closing. Please search if there are already existing issues with the same problem before opening new ☮


Add sandwich explorer feature

Should have shiny power and encounter power by default, and allow the user to toggle between the other powers.

Heavily related to pokemon-sandwich-simulator however I want the inverse. User selects the 'extra' power they want (shiny and encounter on by default), if a pokémon is dual typed the user should be able to select the type. Website then displays a few options.
Seems like it could be computationally expensive, but a greedy DFS approach could work, just adding ingredients that have a bias towards the users desired typings.


Feature request: add cxx-sources/cxx-options field

Cabal has added support for compiling C++ sources and added cxx-sources/cxx-options to the configuration (see here). It would be nice for hpack to support this :)

PR please! ;)


clickToUse: mouseDown instead of mouseUp

Hey,
the clickToUse option is really helpfull and overall a nice feature. Especially if the graph is embedded in a page where you have to scroll so you can scroll through the page without accidently zooming in or out the graph.
However, if one wants to move around elements in the graph and has to select it first it just feels bad.
So instead of having the graph selected once the users click is done (so on the MouseButtonRelease or MouseButtonUp event) it would be nice to have it select already on the MouseButtonPress or MouseButtonDown event.
An option where you can switch between default and "new" behavior would maybe be the best.

This won't be that simple. Click to use is based on overlay that swallows events. The mouse down would be swallowed by the overlay anyway and another mouse down would be necessary to drag nodes around. This would require either synthetic events (these could be a bit tricky) or complete overhaul of click to use.


Compatibility with twin.macro package

twin.macro allow me to make separate style file with features of StyledComponent and Tailwind.
Your plugin works perfect, but only for classes inside React component - is there any way to make it work inside ***.styles.tw.ts files?

Closing in favour of https://github.com/tailwindlabs/tailwindcss/discussions/7558


AP Test Week 3 Review Ticket - Derrick Huang

Score 2/2 (Graded by Punarvasu Sangam)
Github Page Link - Notes
AP Test + Corrections
AP Test 1 (45/50) - Corrections
AP Test 2 (34/50) - Corrections
AP Test 3 (42/50) - Corrections
THIS WEEK CORRECTIONS:
AP Test 5 (23/25) - Corrections

SCORE: 2/2

[x] GH Indi Page, Review Ticket, Crossover graded, Study Plan (1/1)
[x] Quiz5 MCQ results >50%, (1 or 0) and test corrections (1/1)


Update stable version in repo from 0.0.0 to 0.2.1

Think about adding version 0.2.1 to stable repository.
Version: stable=0.0.0 (0 days old) => latest=0.2.1 (30 days old)
Installs: stable=0 (0%), latest=162 (46.02%), total=352
Click to edit

Unstale

https://github.com/ioBroker/ioBroker.repositories/pull/2560


feat: warn on unused functions

Description
Problem
Now that we warn on unused imports, doing that for functions too is relatively straight-forward.
Summary
Now unused private or pub(crate) functions will be reported as unused.
Additional Context
I'd like to try this on some Aztec-Packages projects, but for that it would be nice to merge #5895 first so I could get all warnings/errors for a package inside VS Code.
We can eventually do the same thing with globals, traits, etc., once we track their visibility.
I also think we could warn on unused pub functions in a "bin" or "contract" package, not sure... but if we decide to do that, it could be a separate PR.
Documentation
Check one:

[x] No documentation needed.
[ ] Documentation included in this PR.
[ ] [For Experimental Features] Documentation to be submitted in a separate PR.

PR Checklist

[x] I have tested the changes locally.
[x] I have formatted the changes with Prettier and/or cargo fmt on default settings.

I pushed and reverted a commit that removed a couple of unused functions in the standard library: I don't know if users use them despite the warning that they are private so that's why I left them. They could be removed in a separate PR, though.


Add docs on typings in package.json

From https://github.com/typings/registry/pull/138#issuecomment-187884462

Should I Use The typings Field In package.json?
Maybe. If you're relying on typings to provide type dependencies, I recommend that you omit the typings entry for now. If you don't use the typings.json file, add typings in package.json. This is because TypeScript 1.6+ comes with node module resolution built-in, but unless all the packages in the NPM dependency tree have their own typings entry inline you'll be breaking TypeScript users of your library. Typings has complete support for the node module resolution strategy used in TypeScript.

I think making this clearer is a good shout.  Reading the above the following thoughts / questions occurred to me:

Does everyone know about the typings field in package.json?  I suspect not and it's not that well documented either.  I can find this and one line under "Improvements to module resolution" here and that's it.  An brief explanation of this is probably worthwhile.  It might be nice to link back to a thorough explanation if one exists somewhere too?

I'd get rid of the "Maybe" entirely; it doesn't help.

A basic rule of thumb is specified for using typings in package.json.  It might be worth emphasising that a little more.  Perhaps:

If you're relying on Typings to provide type dependencies omit typings from package.json.
If you don't use the typings.json file, add typings in package.json.

Then go on to explain the implications of each.  The current example isn't very clear.  Here's my brutal takedown of it:

This is because TypeScript 1.6+ comes with node module resolution built-in, [what does this mean?] but unless all the packages in the NPM dependency tree [every npm package you consume with *.d.ts files? Or something else?] have their own typings entry inline [inline?] you'll be breaking TypeScript users of your library**[breaking how exactly?]**). Typings has complete support for the node module resolution strategy used in TypeScript.

There's a lot of assumed knowledge in the explanation above which could do with being unpacked and clarified.
I hope this is helpful feedback; I mean it to be! :tulip:


Documenter

Migrates the documentation to Documenter.jl :tada:

Coverage remained the same at 91.045% when pulling c4e28da9ba566e7eb4afb3db823b688bb31fca9c on documenter into de1338502afa05f2686d93972e5813a466542daf on master.

Coverage increased (+0.1%) to 91.176% when pulling 3d4b5a05c5fa5a9877d44b9cd235bbf3f09dd6d5 on documenter into de1338502afa05f2686d93972e5813a466542daf on master.

Coverage decreased (-0.7%) to 90.37% when pulling f4dc81fc64c5a2563d48f4a4b4d81c99085f3cb2 on documenter into 0ec6d6d163f3a9bfcae16f2082965613a4567b36 on master.

Coverage decreased (-0.7%) to 90.37% when pulling f4dc81fc64c5a2563d48f4a4b4d81c99085f3cb2 on documenter into 0ec6d6d163f3a9bfcae16f2082965613a4567b36 on master.


Sort tables in ascending order

When Lyche admin adds a reservation, the tables are not sorted, and should be.

Fixed


Enhanced Selection doesn't work with GridLazyDataView

when using Enhanced Selection with Lazy Data Provider, this exception is thrown.
java.lang.IllegalStateException: GridListDataView only supports 'ListDataProvider' or it's subclasses, but was given a 'AbstractBackEndDataProvider'. Use either 'getLazyDataView()', 'getListDataView()' or 'getGenericDataView()' according to the used data type. 	at com.vaadin.flow.data.provider.AbstractDataView.verifyDataProviderType(AbstractDataView.java:114) 	at com.vaadin.flow.data.provider.AbstractDataView.<init>(AbstractDataView.java:74)

As mentioned in https://github.com/FlowingCode/GridHelpers/pull/110#issuecomment-1883122423, the current implementation iof this feature is intentionally restricted to in-memory data providers, because there is no efficient way to compute indexOf from a backend data provider. https://github.com/vaadin-component-factory/selection-grid-flow follows a different approach by capturing the indexes in the client-side, so that the data provider can resolve them.

I have the following use case. I can host in memory all of the items, so I can use my grid without lazy loading, but the performance is slow, because every time that I enter in the grid I have to load all the items in memory. In certain cases (very few, rare I would say) I would need to select all the items to do a bulk operation (and my idea is to use enhanced selection for that), and in that time I don't mind in waiting to load all the items in memory. So if I understand well, is this feature only going to fetch all the items when I select a "big range" of the grid and in the rest of the cases just let the lazy loading mechanism to work as always?

So if I understand well, is this feature only going to fetch all the items when I select a "big range" of the grid and in the rest of the cases just let the lazy loading mechanism to work as always?

If you are asking about the proposal in PR #110, it was rejected because selecting M items from a Grid with N items would be O(N*M), leading to O(N^2) complexity for selecting a "big range." Other add-ons solve the same problem in O(N).
Our limitation is that we designed the feature assuming that retrieving the index of an item is a cheap operation, which holds true for in-memory datasets.


chore: Styles improvements

SUMMARY
The aim of this PR was to improve styles of native filter components: Filter Bar, Cascading Popover and Config Modal.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
Before:

After:

TEST PLANs
Verify manually by opening Filter Bar, adding new filter (with/without parent filter), play around in Config Modal.
ADDITIONAL INFORMATION

[ ] Has associated issue:
[x] Changes UI
[ ] Requires DB Migration.
[ ] Confirm DB Migration upgrade and downgrade tested.
[ ] Introduces new feature or API
[ ] Removes existing feature or API

cc @villebro

Codecov Report

Merging #62 (c15d4ed) into native-filters-fast-follow (96c2cbc) will decrease coverage by 0.62%.
The diff coverage is n/a.

@@                      Coverage Diff                       @@
##           native-filters-fast-follow      #62      +/-   ##
==============================================================
- Coverage                       64.57%   63.95%   -0.63%
==============================================================
  Files                             472      472
  Lines                           29097    29082      -15
==============================================================
- Hits                            18790    18599     -191
- Misses                          10307    10483     +176

Flag
Coverage Δ

python
63.95% <ø> (-0.63%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

superset/db_engines/hive.py
0.00% <0.00%> (-85.72%)
:arrow_down:

superset/db_engine_specs/hive.py
54.61% <0.00%> (-29.62%)
:arrow_down:

superset/db_engine_specs/presto.py
69.95% <0.00%> (-12.45%)
:arrow_down:

superset/db_engine_specs/mysql.py
79.59% <0.00%> (-12.25%)
:arrow_down:

superset/examples/world_bank.py
97.10% <0.00%> (-2.90%)
:arrow_down:

superset/examples/birth_names.py
96.51% <0.00%> (-2.33%)
:arrow_down:

superset/views/database/mixins.py
80.70% <0.00%> (-1.76%)
:arrow_down:

superset/models/core.py
87.26% <0.00%> (-1.63%)
:arrow_down:

superset/reports/notifications/base.py
95.00% <0.00%> (-0.46%)
:arrow_down:

superset/views/core.py
74.77% <0.00%> (-0.46%)
:arrow_down:

... and 7 more

Continue to review full report at Codecov.

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

@agatapst whoops, there's a conflict on FilterConfigForm caused by a recent merge, can you fix that? I'll merge once that's done.


[Docs]: how to deploy an app using the gitops repository

What type of suggestions?
Missing Information
What page is concerned?
No response
What is the issue?
Need documentation on how to deploy an app using the gitops repository
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Steps listed in this thread by @jarededwards: https://kubefirst.slack.com/archives/C03U34WJ7FW/p1671848661002459?thread_ts=1671815801.191299&cid=C03U34WJ7FW


remove: with :pattern matching"

Is your feature request related to a problem? Please describe.
I am trying to override the fill color (bg-) of a button with a class that tails doesn't recognize
Describe the solution you'd like
remove:bg-* would remove all the classes that start with bg-
Describe alternatives you've considered
remove:* is available but it is too heavy handed. I don't want to remove every class. Can this support a comma-delimited list of wildcards?

Sounds interesting :) Didn't see this before for some reason. PRs welcome. We wouldn't support a comma separated list, but you can specify it multiple times, i.e remove:bg-* remove:.... Its an interesting idea, and it doesn't really hurt to have it, but at the same time it would likely be hard to use right since many unrelated things share the same prefix.


Issue with installation of haml-lint

I am trying to run gem install haml-lint -v '0.13.0' and get 404.
ERROR:  While executing gem ... (Gem::RemoteFetcher::FetchError)
bad response Not Found 404 (https://rubygems.global.ssl.fastly.net/quick/Marshal.4.8/haml-lint-0.13.0.gemspec.rz)

Hey @shmulikt,
Please install using haml_lint, not haml-lint. haml_lint matches RubyGems naming conventions.


Need Documentation for new IApplicationIdProvider

This to document the work done to address: https://github.com/Microsoft/ApplicationInsights-dotnet-server/issues/853
Need to add new document.
Describe configuration ( via config and code).
Both providers: Dictionary and ApplicationInsights.
Dictionary - How to chain providers
ApplicationInsights - How to proxy ProfileQueryEndpoint

Need to update ApplicationInsights.config:
https://docs.microsoft.com/en-us/azure/application-insights/app-insights-configuration-with-applicationinsights-config

Need to update the proxy instructions:
https://docs.microsoft.com/en-us/azure/application-insights/app-insights-troubleshoot-faq#proxy

Second PR (proxy settings) was addressed as a separate PR: https://github.com/MicrosoftDocs/azure-docs-pr/pull/39545


Webpush course refers to missing "TODO" in js/main.js

Web Push course refers to missing TODOs in the code of js/main.js: for example, 2.5, 2.6, 5.1.
These can be inferred by developers, but can also create some confusion on where to place the code snippets.

Hi @demianrenzulli, I just searched for the TODOs you listed in main.js and couldn't find them, but it looks like TODO 2.5 and 5.1 are actually added by the student in TODO 2.4 and TODO 2.6 is actually in the sw.js file, which the instructions note.
Does that clear up the potential confusion?

I think my main confusion came because I dodn't exactly followed the codelab copying the exact snippets of code, and skipped some steps. You're right about the comments, and also TODO 2.4, is also created by the student at 2.3.
Thank you!


Specify the selected answer progress bar impact

Estimation: 5hours
PREREQUISITES:
Have the value of the selected answer stored.
Have the visualized parameters implemented and displayed. (Progress bar API)
GODOT LOGIC / GODOT UI:
Implement the logic of the system of applying the impact:
Check if the value is for future or instant affection.
Store the value of impact in case of future affection.
Different values have different impact on the system parameters
Calculate the impact amount and to what parameter should be added.
Connect the impact with the methods created by task #60 and task #61 to update the progress bar or zones accordingly.
BOUNDARIES:
This task doesn’t directly update the progress bar or zones.
This task stores the future modification value
This task doesn’t consider future modifications (Future states)
OUTCOMES:
The progress bar is ready to get the modification value to be updated.
The future affection is stored to be implemented and timed.

Here "future effect" is intended as creating a progress bar zone that in the future will alter the bar speed when inside it


simpler version in setup

Description

Related Issues

Checklist:

[ ] I have followed the contribution guidelines and code style for this project.
[ ] I have added tests covering my contributions.
[ ] I have updated the documentation accordingly.
[ ] This PR is being made to staging branch and not to main branch.

the only issue with this is that it will only work if you are in the same directory as setup.py. that's probably the most likely spot anyone would run this, so I think it's fine to make this simplification, but just wanted to point that out.


dockerfile: add image annotations

Use standard image-spec annotations[1] to define minimal reference to SINK project within the samba-operator image itself.
[1] https://github.com/opencontainers/image-spec/blob/main/annotations.md
Signed-off-by: Shachar Sharon<EMAIL_ADDRESS>

@Mergifyio refresh

mergify failed because of an indentation issue. See #278

@Mergifyio rebase


[T2A3][T09-A1]Ken Oung Yong Quan

Ready for review

@kenoung Some comments added. Please close the PR after reading comments.


DNF Sort in C-plus-plus

💥 Proposal
Given an array of 0's,1's, and 2's, the sorting algorithm sorts them in the order where, first all 0's, then 1's, and lastly all 2's.
Have you read the Contributing Guidelines on Pull Requests?
Yes

/assign

Problem already present here


SFTP: Perform less strict permission checks on servers where the exec channel is disabled

Prior to this patch, all permissions checks would fail on servers
without an exec channel: SftpFileObject relied on the knowledge of the
current user's UID and GID. Neither of these can be obtained without an
exec channel. The SFTP specifications do not appear to mention any
alternative method of ascertaining the UID/GID.
As a workaround, when the UID can't be detected, SftpFileObject will use
a DummyPosixPermissions instance, which always "grants" RWX.
There are two sides to this coin:

This will allow normal operation against SFTP servers without an exec
channel.
This may cause JSchExceptions to be thrown when the actual
permissions are inconsistent with the dummy permissions.

This seems to be preferable to not being able to use exec-less SFTP
servers. Regressions should be limited to these kinds of servers.
Calling getUId when first making a connection might impose an overhead,
but this is presumably a trivial one.
This will probably fix VFS-590 and VFS-617.
This solution could be made a bit more elegant, perhaps by making this check optional, or by using an alternative way to detect whether the exec channel is present.

I'll try to process most of this feedback tomorrow and update the PR. Apologies for the lacking reactivity, been running this in production without issues so managed to forget all about it :-)

I've processed the feedback. Please let me know if there's anything else you need for me in order to get this accepted.

Hey, any progress on this please? It's blocking deployment for us

The patch is missing unit tests.
Gary
On Fri, Sep 21, 2018, 05:17 Duncan McGregor<EMAIL_ADDRESS>wrote:

Hey, any progress on this please? It's blocking deployment for us
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/apache/commons-vfs/pull/27#issuecomment-423498664,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABIfNyzwAa4xdU7VHs0OuPsdnGCucOl3ks5udMrlgaJpZM4REyoV
.

I see this was closed. I couldn't find anything else about this issue but our sftp servers disallows exec channel calls likes 'id -G' and returns this string "This service allows sftp connections only." and then fails with an exception and thus can't do any calls that use isWritable,isReadable, isExecutable. vfs sftp is unusable. It there anything in the works or an issue for this so vfs can handle this case at a future date time.
Current workaround is to create our own SFTP Provider and subclass and disable exec commands.

It was closed automatically when the obsolete trunk branch was deleted. I'd re-open the PR but the source repo has been deleted so I can't. If this is still a concern, please open a new PR against master.


Les keys ne semblent pas avoir été changées quand c'est passé de UBeat à UMovie dans la documentation.

Il semble y avoir des restants de UBeat (artist, trackName). Cependant, les values ont été updatées.
 That's what two men, Adam (Leigh Whannell) and Gordon (Cary Elwes), have to ask themselves when they're paired up in a deadly situation. Abducted by a serial killer, they're trapped up in a prison constructed with such ingenuity that they may not be able to escape before their captor decides it's time to dismantle their bodies in his signature way. Attempting to break free may kill them, but staying definitely will.",
"radioStationUrl": "https://itunes.apple.com/station/idra.265727087"
}
]
}

Ces clés viennent de l'API de iTunes. C'est le meme nom pour les films/séries (sadly). Closing.


Electron : setTimeout(...).unref() is not a function

There's an issue with Electron where setTimeout does not return anything since it's techinically a "browser", causing .unref() to crash the program in Vhost.js.
I have a fix (just checking if setTimeout contains unref) but can't create a branch.

Hi @scottk,
Thanks for reporting. I wonder whether there are other differences between node and electron. If this was the only incompatibility I'd be fine with your suggested approach, but I'm skeptical that there aren't others. Any thoughts?

Not that I can think of....Supposedly a common issue for a lot of different libraries being used in electron - electron uses a browser implementation of setTimeout causing it to not return anything/have any properties. There is a property for electron windows called "nodeIntegration", which still doesn't fix the problem (but does fix others like it)

https://www.electronjs.org/docs/tutorial/application-architecture#using-nodejs-apis says you're right.
I think your proposed solution is sound. Would you consider submitting a PR?
I'm not sure why you weren't able to make a branch - should be a case of

forking rascal to GitHub account you own
cloning locally
making the change
pushing and creating a PR

The tests do need RabbitMQ running locally. If you have docker installed the easiest way to do this is by typing npm run docker after cloning rascal.

I updated all locations with setTimeout if that's ok - only the one in Vhost was failing, and only when a connection was broken, but I figured we should cover all of them. Will make the PR now

Published as<EMAIL_ADDRESS>


warnings from msvc 2022

just sharing its warnings but i have no time to take a look at them and submit a pr,
cl : Command line warning D9025 : overriding '/MDd' with '/MT'
cl : Command line warning D9002 : ignoring unknown option '-fvisibility=hidden'
../shlr/qjs/src/quickjs.c(1351): warning C4244: 'function': conversion from 'int64_t' to 'double', possible loss of data
../shlr/qjs/src/quickjs.c(6149): warning C4244: '+=': conversion from 'double' to 'int64_t', possible loss of data
../shlr/qjs/src/quickjs.c(6150): warning C4244: '+=': conversion from 'double' to 'int64_t', possible loss of data
../shlr/qjs/src/quickjs.c(6278): warning C4244: '=': conversion from 'double' to 'int64_t', possible loss of data
../shlr/qjs/src/quickjs.c(6279): warning C4244: '=': conversion from 'double' to 'int64_t', possible loss of data
../shlr/qjs/src/quickjs.c(6281): warning C4244: '=': conversion from 'double' to 'int64_t', possible loss of data
../shlr/qjs/src/quickjs.c(6288): warning C4244: '+=': conversion from 'double' to 'int64_t', possible loss of data
../shlr/qjs/src/quickjs.c(6464): warning C4146: unary minus operator applied to unsigned type, result still unsigned
../shlr/qjs/src/quickjs.c(6497): warning C4146: unary minus operator applied to unsigned type, result still unsigned
../shlr/qjs/src/quickjs.c(10328): warning C4244: '=': conversion from 'uint64_t' to 'double', possible loss of data
../shlr/qjs/src/quickjs.c(11542): warning C4244: '=': conversion from 'double' to 'int', possible loss of data
../shlr/qjs/src/quickjs.c(11557): warning C4244: '=': conversion from 'double' to 'int', possible loss of data
../shlr/qjs/src/quickjs.c(40184): error C2099: initializer is not a constant
../shlr/qjs/src/quickjs.c(41005): warning C4244: '=': conversion from 'double' to 'int', possible loss of data
../shlr/qjs/src/quickjs.c(46826): warning C4244: '=': conversion from 'double' to 'int64_t', possible loss of data
../shlr/qjs/src/quickjs.c(49156): error C2099: initializer is not a constant
../shlr/qjs/src/quickjs.c(49267): warning C4244: '=': conversion from 'double' to 'int64_t', possible loss of data
../shlr/qjs/src/quickjs.c(49294): warning C4244: '=': conversion from 'int64_t' to 'double', possible loss of data
../shlr/qjs/src/quickjs.c(49295): warning C4244: '=': conversion from 'int64_t' to 'double', possible loss of data
../shlr/qjs/src/quickjs.c(49296): warning C4244: '=': conversion from 'int64_t' to 'double', possible loss of data
../shlr/qjs/src/quickjs.c(49297): warning C4244: '=': conversion from 'int64_t' to 'double', possible loss of data
../shlr/qjs/src/quickjs.c(49298): warning C4244: '=': conversion from 'int64_t' to 'double', possible loss of data
../shlr/qjs/src/quickjs.c(49299): warning C4244: '=': conversion from 'int64_t' to 'double', possible loss of data
../shlr/qjs/src/quickjs.c(49300): warning C4244: '=': conversion from 'int64_t' to 'double', possible loss of data
../shlr/qjs/src/quickjs.c(49301): warning C4244: '=': conversion from 'int64_t' to 'double', possible loss of data
../shlr/qjs/src/quickjs.c(49302): warning C4244: '=': conversion from 'int64_t' to 'double', possible loss of data
../shlr/qjs/src/quickjs.c(49332): warning C4244: '=': conversion from 'double' to 'int', possible loss of data
../shlr/qjs/src/quickjs.c(49333): warning C4244: '=': conversion from 'double' to 'int', possible loss of data
../shlr/qjs/src/quickjs.c(49456): warning C4244: '=': conversion from 'double' to 'int', possible loss of data
../shlr/qjs/src/quickjs.c(49457): warning C4244: '=': conversion from 'double' to 'int', possible loss of data
../shlr/qjs/src/quickjs.c(49458): warning C4244: '=': conversion from 'double' to 'int', possible loss of data
../shlr/qjs/src/quickjs.c(49459): warning C4244: '=': conversion from 'double' to 'int', possible loss of data
../shlr/qjs/src/quickjs.c(49460): warning C4244: '=': conversion from 'double' to 'int', possible loss of data
../shlr/qjs/src/quickjs.c(49461): warning C4244: '=': conversion from 'double' to 'int', possible loss of data
../shlr/qjs/src/quickjs.c(49462): warning C4244: '=': conversion from 'double' to 'int', possible loss of data
../shlr/qjs/src/quickjs.c(49463): warning C4244: '=': conversion from 'double' to 'int', possible loss of data
../shlr/qjs/src/quickjs.c(49464): warning C4244: '=': conversion from 'double' to 'int', possible loss of data
../shlr/qjs/src/quickjs.c(49563): warning C4244: '=': conversion from 'int64_t' to 'double', possible loss of data
../shlr/qjs/src/quickjs.c(51972): warning C4244: '=': conversion from 'double' to 'int', possible loss of data
../shlr/qjs/src/quickjs.c(51978): warning C4244: '=': conversion from 'double' to 'int', possible loss of data
../shlr/qjs/src/quickjs.c(52011): warning C4244: '=': conversion from 'int64_t' to 'double', possible loss of data
../shlr/qjs/src/quickjs.c(52016): warning C4244: '=': conversion from 'double' to 'int64_t', possible loss of data
[1977/2318] Compiling C object libr/lang/r_lang.dll.p/.._.._shlr_qjs_src_libbf.c.obj
cl : Command line warning D9025 : overriding '/MDd' with '/MT'
cl : Command line warning D9002 : ignoring unknown option '-fvisibility=hidden'
../shlr/qjs/src/libbf.c(484): warning C4146: unary minus operator applied to unsigned type, result still unsigned
../shlr/qjs/src/libbf.c(1224): warning C4146: unary minus operator applied to unsigned type, result still unsigned
../shlr/qjs/src/libbf.c(1233): warning C4146: unary minus operator applied to unsigned type, result still unsigned
../shlr/qjs/src/libbf.c(2403): warning C4146: unary minus operator applied to unsigned type, result still unsigned
../shlr/qjs/src/libbf.c(2404): warning C4146: unary minus operator applied to unsigned type, result still unsigned
../shlr/qjs/src/libbf.c(2405): warning C4146: unary minus operator applied to unsigned type, result still unsigned
../shlr/qjs/src/libbf.c(2575): warning C4146: unary minus operator applied to unsigned type, result still unsigned
../shlr/qjs/src/libbf.c(2591): warning C4146: unary minus operator applied to unsigned type, result still unsigned
../shlr/qjs/src/libbf.c(2627): warning C4146: unary minus operator applied to unsigned type, result still unsigned
../shlr/qjs/src/libbf.c(2652): warning C4146: unary minus operator applied to unsigned type, result still unsigned
../shlr/qjs/src/libbf.c(3348): warning C4146: unary minus operator applied to unsigned type, result still unsigned
../shlr/qjs/src/libbf.c(3391): warning C4146: unary minus operator applied to unsigned type, result still unsigned
../shlr/qjs/src/libbf.c(4448): warning C4146: unary minus operator applied to unsigned type, result still unsigned
../shlr/qjs/src/libbf.c(4981): warning C4146: unary minus operator applied to unsigned type, result still unsigned
../shlr/qjs/src/libbf.c(7150): warning C4146: unary minus operator applied to unsigned type, result still unsigned
../shlr/qjs/src/libbf.c(7168): warning C4146: unary minus operator applied to unsigned type, result still unsigned
ninja: build stopped: subcommand failed.
Ninja compilation has failed

https://github.com/quickjs-ng/quickjs/commit/62f4713780290cc8e5278e5045103c27a46fe24f
I will update and report again if any as ive seen several fixes after that

thats what i get with latest commit:
l : Command line warning D9002 : ignoring unknown option '-fvisibility=hidden'
../shlr/qjs/src/quickjs.c(1381): warning C4244: 'function': conversion from 'int64_t' to 'double', possible loss of data
../shlr/qjs/src/quickjs.c(6183): warning C4244: '+=': conversion from 'double' to 'int64_t', possible loss of data
../shlr/qjs/src/quickjs.c(6184): warning C4244: '+=': conversion from 'double' to 'int64_t', possible loss of data
../shlr/qjs/src/quickjs.c(6312): warning C4244: '=': conversion from 'double' to 'int64_t', possible loss of data
../shlr/qjs/src/quickjs.c(6313): warning C4244: '=': conversion from 'double' to 'int64_t', possible loss of data
../shlr/qjs/src/quickjs.c(6315): warning C4244: '=': conversion from 'double' to 'int64_t', possible loss of data
../shlr/qjs/src/quickjs.c(6322): warning C4244: '+=': conversion from 'double' to 'int64_t', possible loss of data
../shlr/qjs/src/quickjs.c(6498): warning C4146: unary minus operator applied to unsigned type, result still unsigned
../shlr/qjs/src/quickjs.c(6531): warning C4146: unary minus operator applied to unsigned type, result still unsigned
../shlr/qjs/src/quickjs.c(10377): warning C4244: '=': conversion from 'uint64_t' to 'double', possible loss of data
../shlr/qjs/src/quickjs.c(11591): warning C4244: '=': conversion from 'double' to 'int', possible loss of data
../shlr/qjs/src/quickjs.c(11606): warning C4244: '=': conversion from 'double' to 'int', possible loss of data
../shlr/qjs/src/quickjs.c(41109): error C2099: initializer is not a constant
../shlr/qjs/src/quickjs.c(41930): warning C4244: '=': conversion from 'double' to 'int', possible loss of data
../shlr/qjs/src/quickjs.c(47856): warning C4244: '=': conversion from 'double' to 'int64_t', possible loss of data
../shlr/qjs/src/quickjs.c(50186): error C2099: initializer is not a constant
../shlr/qjs/src/quickjs.c(50297): warning C4244: '=': conversion from 'double' to 'int64_t', possible loss of data
../shlr/qjs/src/quickjs.c(50324): warning C4244: '=': conversion from 'int64_t' to 'double', possible loss of data
../shlr/qjs/src/quickjs.c(50325): warning C4244: '=': conversion from 'int64_t' to 'double', possible loss of data
../shlr/qjs/src/quickjs.c(50326): warning C4244: '=': conversion from 'int64_t' to 'double', possible loss of data
../shlr/qjs/src/quickjs.c(50327): warning C4244: '=': conversion from 'int64_t' to 'double', possible loss of data
../shlr/qjs/src/quickjs.c(50328): warning C4244: '=': conversion from 'int64_t' to 'double', possible loss of data
../shlr/qjs/src/quickjs.c(50329): warning C4244: '=': conversion from 'int64_t' to 'double', possible loss of data
../shlr/qjs/src/quickjs.c(50330): warning C4244: '=': conversion from 'int64_t' to 'double', possible loss of data
../shlr/qjs/src/quickjs.c(50331): warning C4244: '=': conversion from 'int64_t' to 'double', possible loss of data
../shlr/qjs/src/quickjs.c(50332): warning C4244: '=': conversion from 'int64_t' to 'double', possible loss of data
../shlr/qjs/src/quickjs.c(50362): warning C4244: '=': conversion from 'double' to 'int', possible loss of data
../shlr/qjs/src/quickjs.c(50363): warning C4244: '=': conversion from 'double' to 'int', possible loss of data
../shlr/qjs/src/quickjs.c(50486): warning C4244: '=': conversion from 'double' to 'int', possible loss of data
../shlr/qjs/src/quickjs.c(50487): warning C4244: '=': conversion from 'double' to 'int', possible loss of data
../shlr/qjs/src/quickjs.c(50488): warning C4244: '=': conversion from 'double' to 'int', possible loss of data
../shlr/qjs/src/quickjs.c(50489): warning C4244: '=': conversion from 'double' to 'int', possible loss of data
../shlr/qjs/src/quickjs.c(50490): warning C4244: '=': conversion from 'double' to 'int', possible loss of data
../shlr/qjs/src/quickjs.c(50491): warning C4244: '=': conversion from 'double' to 'int', possible loss of data
../shlr/qjs/src/quickjs.c(50492): warning C4244: '=': conversion from 'double' to 'int', possible loss of data
../shlr/qjs/src/quickjs.c(50493): warning C4244: '=': conversion from 'double' to 'int', possible loss of data
../shlr/qjs/src/quickjs.c(50494): warning C4244: '=': conversion from 'double' to 'int', possible loss of data
../shlr/qjs/src/quickjs.c(50593): warning C4244: '=': conversion from 'int64_t' to 'double', possible loss of data
../shlr/qjs/src/quickjs.c(53174): warning C4244: '=': conversion from 'double' to 'int', possible loss of data
../shlr/qjs/src/quickjs.c(53180): warning C4244: '=': conversion from 'double' to 'int', possible loss of data
../shlr/qjs/src/quickjs.c(53227): warning C4244: '=': conversion from 'int64_t' to 'double', possible loss of data
../shlr/qjs/src/quickjs.c(53232): warning C4244: '=': conversion from 'double' to 'int64_t', possible loss of data
[1977/2318] Compiling C object libr/lang/r_lang.dll.p/.._.._shlr_qjs_src_libbf.c.obj
cl : Command line warning D9025 : overriding '/MDd' with '/MT'
cl : Command line warning D9002 : ignoring unknown option '-fvisibility=hidden'
../shlr/qjs/src/libbf.c(484): warning C4146: unary minus operator applied to unsigned type, result still unsigned
../shlr/qjs/src/libbf.c(1224): warning C4146: unary minus operator applied to unsigned type, result still unsigned
../shlr/qjs/src/libbf.c(1233): warning C4146: unary minus operator applied to unsigned type, result still unsigned
../shlr/qjs/src/libbf.c(2403): warning C4146: unary minus operator applied to unsigned type, result still unsigned
../shlr/qjs/src/libbf.c(2404): warning C4146: unary minus operator applied to unsigned type, result still unsigned
../shlr/qjs/src/libbf.c(2405): warning C4146: unary minus operator applied to unsigned type, result still unsigned
../shlr/qjs/src/libbf.c(2575): warning C4146: unary minus operator applied to unsigned type, result still unsigned
../shlr/qjs/src/libbf.c(2591): warning C4146: unary minus operator applied to unsigned type, result still unsigned
../shlr/qjs/src/libbf.c(2627): warning C4146: unary minus operator applied to unsigned type, result still unsigned
../shlr/qjs/src/libbf.c(2652): warning C4146: unary minus operator applied to unsigned type, result still unsigned
../shlr/qjs/src/libbf.c(3348): warning C4146: unary minus operator applied to unsigned type, result still unsigned
../shlr/qjs/src/libbf.c(3391): warning C4146: unary minus operator applied to unsigned type, result still unsigned
../shlr/qjs/src/libbf.c(4448): warning C4146: unary minus operator applied to unsigned type, result still unsigned
../shlr/qjs/src/libbf.c(4981): warning C4146: unary minus operator applied to unsigned type, result still unsigned
../shlr/qjs/src/libbf.c(7150): warning C4146: unary minus operator applied to unsigned type, result still unsigned
../shlr/qjs/src/libbf.c(7168): warning C4146: unary minus operator applied to unsigned type, result still unsigned
ninja: build stopped: subcommand failed.

../shlr/qjs/src/quickjs.c(41109): error C2099: initializer is not a constant

That's the JS_ALIAS_BASE_DEF macro. I don't understand why msvc has trouble with it but we can probably get rid of it.

../shlr/qjs/src/quickjs.c(50186): error C2099: initializer is not a constant

That line number doesn't correspond to anything (blank line); what commit specifically are you testing?

But wait, CI tests VS 17 2022 and it's definitely building there. I think we'll need to more info to figure out what exactly the issue is.

my main concernn are the errors xD:
../shlr/qjs/src/quickjs.c(41109): error C2099: initializer is not a constant
and
../shlr/qjs/src/quickjs.c(50186): error C2099: initializer is not a constant

QJS_COMMIT=e1a0f4f1cf7548ddb1d2b97220d3346f7fa44091

You are not using our build system, right? What build flags are you passing?

We're getting the same error in LLRT ci. I suspect something got updated in msys2/setup-msys2@v2 or in the worker because it started happening without being tied to a specific commit (failed on newer builds for older commits)

@richarddd your report is on MinGW right? @trufae ia on MSVC.
At any rate, are the rust bindings using the CMake build system? If not, what compiler flags are you using?

@richarddd your report is on MinGW right? @trufae ia on MSVC.
At any rate, are the rust bindings using the CMake build system? If not, what compiler flags are you using?

No we use MSVC. I'm a total Windows novice so we might have done something wrong. We use CC crate withthese build flags: /std:c11 /experimental:c11atomics
https://github.com/DelSkayn/rquickjs/blob/master/sys/build.rs#L159
This is the command that failes:
quickjs.c
  D:\a\llrt\llrt\target\debug\build\rquickjs-sys-683cbfbb52ef3647\out\quickjs.c(40539): error C2099: initializer is not a constant
  D:\a\llrt\llrt\target\debug\build\rquickjs-sys-683cbfbb52ef3647\out\quickjs.c(49511): error C2099: initializer is not a constant
  exit code: 0
  exit code: 0
  exit code: 0
  exit code: 2
  libbf.c
  cargo:warning=ToolExecError: Command "C:\\Program Files\\Microsoft Visual Studio\\2022\\Enterprise\\VC\\Tools\\MSVC\\14.42.34433\\bin\\HostX64\\x64\\cl.exe" "-nologo" "-MD" "-Brepro" "/std:c11" "/experimental:c11atomics" "-D_GNU_SOURCE" "-FoD:\\a\\llrt\\llrt\\target\\debug\\build\\rquickjs-sys-683cbfbb52ef3647\\out\\862492ac8e08571a-quickjs.o" "-c" "D:\\a\\llrt\\llrt\\target\\debug\\build\\rquickjs-sys-683cbfbb52ef3647\\out\\quickjs.c" with args cl.exe did not execute successfully (status code exit code: 2).

Right that is MSVC. The mention is the mays2 action threw me off.
I'll check it out.

This may be related:
https://github.com/igraph/igraph/issues/2701
https://github.com/microsoft/vcpkg/issues/42082
https://developercommunity.visualstudio.com/t/NAN-is-no-longer-compile-time-constant-i/10688907
Looks like the definition of NAN changed in latest version of Windows SDK?


[TALENT] Paloma Got Talent FE Bug List from December 20, 2024

[x] The Trading page is the endpoint for the ticker symbol: for example https://www.palomatalent.ai/syoma for Syoma. The HomePage will be on a separate ticket https://github.com/VolumeFi/paloma/issues/2462.
[x] Login has a picture of Syamo the cat as the default profile image. It needs to have a background so that user knows to upload new image. @joycehermosilla will you provide one? A grey pigeon outline. @jamie088 Image is here: https://www.figma.com/design/EjJt84TMuKi9DMVJvQmAiV/Paloma's-Got-CryptoTalent?node-id=1188-226&t=DbeTZfJEn0L1gf6C-4
[x] When a user enters information, the Name and Token name do not update
[x] As a user, when I register, I must click a box to agree to the Terms and conditions.
[x] Select Options: Why is this here? It does not show up in the UI. Please check with @joycehermosilla or remove?
[x] Back to Profile and Submit buttons are in non-intuitive location and are distracting. They need to be at the bottom of the action so that I complete the forms before clicking @joycehermosilla @jamie088 I added the new designs here: https://www.figma.com/design/EjJt84TMuKi9DMVJvQmAiV/Paloma's-Got-CryptoTalent?node-id=672-1405&t=DbeTZfJEn0L1gf6C-4 (1.Remove Location option, 2. Add back to profile button, 3. Add Save changes button on each section)
[x] Profile does not use Pics or Music. Please remove these.
[x] Submit on Profile Edit Page takes me back to the trading profile page in edit mode instead of the page in publish/view mode. Fix so that submit shows finished/updated page, not editable page.
[x] Logged in and back to the home page shows me the login button. If I'm logged in, no login button. I need to add my wallet. Please add wallet UI/UX as we have for lightnodes. FYI @joycehermosilla

Closing as complete. New issues moved to https://github.com/VolumeFi/paloma/issues/2463


Added additional file closes to ensure no file is ever kept open

This is to help with cleaning up the build files while working which is currently giving issues while android studio is open due to not all the file opens being closed after.
They have been wrapped in a try finally in order to ensure that it will always get done

Thanks, that seems like a good thing to do!


CASSANDRA-17797 All system properties and environment variables must be accessed via CassandraRelevantProperties

Thanks for sending a pull request! Here are some tips if you're new here:

Ensure you have added or run the appropriate tests for your PR.
Be sure to keep the PR description updated to reflect all changes.
Write your PR title to summarize what this PR proposes.
If possible, provide a concise example to reproduce the issue for a faster review.
Read our contributor guidelines
If you're making a documentation change, see our guide to documentation contribution

Commit messages should follow the following format:
<One sentence description, usually Jira title or CHANGES.txt summary>

<Optional lengthier description (context on patch)>

patch by <Authors>; reviewed by <Reviewers> for CASSANDRA-#####

Co-authored-by: Name1 <email1>
Co-authored-by: Name2 <email2>

The Cassandra Jira

@Mmuzaf could you please make one commit (squash it) and rebase it all on top of the current trunk after you are done with the review? Starts to be messy a bit ...

@smiklosovic Thank you for your review.
I've resolved and fixed all your comments. The commits have also been squashed.
I will re-run the tests and check them again once Jenkins gets up.

@Mmuzaf please don't force push and apply changes in separate commits; you will rebase once we finish the review phase

One more general idea is to have all those get/set methods in an interface as defaults and inherit them in CassandraRelevantProperties and the env counterpart

Doesn't this go against our code style. We don't add get/set methods if there's not a reason to do so, and we don't add interfaces unless there's a reason to do so.

One more general idea is to have all those get/set methods in an interface as defaults and inherit them in CassandraRelevantProperties and the env counterpart

Doesn't this go against our code style. We don't add get/set methods if there's not a reason to do so, and we don't add interfaces unless there's a reason to do so.

I'm not suggesting adding any new methods, just moving the existing methods to the interface because they can not go to a superclass (enums). The only difference between CassandraRelevantProperties and CassandraRelevantEnvs is the method they use to get the raw string. Sorry for the confusion - no set methods to be moved, just get.

Committed: https://github.com/apache/cassandra/commit/f6509086483983176f82a4b72912927693b6e573


Visium QC update - reagent lot number

@khelwood  Fix for the problem Katy reported for x957 - " it should be Reagent LOT number not Slide LOT number. And I keep getting an error of "failed to record visium QC on the page" not sure what I have done wrong?!".


[WIP] [Enhancement] change chunk_size of IO thread to 4096

What type of PR is this：

[ ] bug
[ ] feature
[x] enhancement
[ ] refactor
[ ] others

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

For some cases, the 16384 chunk_size of IO thread would encounter the memory allocation bottleneck, which cause performance regression between non-pipeline mode.
As a workaround, we change the chunk_size of IO thread to 4096, to eliminate the bottleneck.
In the future, we would decide the chunk_size based on the row-size, and optimize the memory allocator, to completely solve this issue.

@Mergifyio rebase

run starrocks_fe_unittest


A description of the models

Will not bother authour with my newbie question. Closing/Canceling.

:)
I guess the lines that you had quoted were from the start of the generator. Then 128 * 4 * 4 denotes an initial height and width of 4. 128 is the initial number of channels, which is progressively reduced to 3 (RGB channels) throughout the layers. How many channels to pick is up to experimentation, there is no "correct" number. I don't remember why it was reduced compared to the readme. My best guess would be, that it was for faster performance during testing and then forgotten to increase again. 128 is on the low side for the initial channels number. Nowadays, 1024 would be more standard.
And where to place PReLU is also up to experimentation. Placing it before the View means that it should have 128 * 4 * 4 weights (the slope of the activations), one for each neuron. Placing it behind the View should result in 128 weights, one for each channel. Having a single weight for all neurons of the same channel introduces a prior that these neurons somehow belong to each other and that might improve results or it might increase training speed (it might also do neither of these things).

Thank you a lot! :)


Fix English mistakes in some Markdown documents

This PR fixes up English mistakes in the following Markdown documents:

README.md
docs/content/page/index.en-us.md
docs/content/doc/installation/from-binary.en-us.md

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@7740779). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main   #20274   +/-   ##
=======================================
  Coverage        ?   46.90%
=======================================
  Files           ?      976
  Lines           ?   135144
  Branches        ?        0
=======================================
  Hits            ?    63383
  Misses          ?    63986
  Partials        ?     7775

Continue to review full report at Codecov.

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


[ApiView] Show Hidden APIs no longer works

Since the new UI rollout, it appears that Show Hidden APIs is not functional. Hidden APIs are always hidden regardless of the setting.
As an example, Event Grid API view should have a namespace of Azure.Messaging.EventGrid.Models in the sidebar when showing hidden APIs.
This feature was added in https://github.com/Azure/azure-sdk-tools/pull/4618

/cc @tg-msft

@maririos is there any other information needed to get this prioritized?

@chidozieononiwu could you please take a look?

@maririos is there any other information needed to get this prioritized?

You've done it all. Because of the holiday we didn't look at the issue this week. Added it to our release


Strange enum Error

Error contains new(String) - This is bad code!!!!!
i get such an error:
>> new("io error: Conn is closed")

i expected to get: Error::ErrConnectionClosed
I get this error when I try to write a packet to the track:
while let Some(sample) = appsink_stream.next().await {
            if let Some(buffer) = sample.buffer() {
                if let Ok(map) = buffer.map_readable() {
                    let slice = map.as_slice();

                    if let Err(err) = video_track_clone.write(slice).await {
                        match err {
                            webrtc::Error::ErrConnectionClosed => continue,
                            webrtc::Error::ErrClosedPipe => break,
                            err => {
                                tracing::error!("video_track write err: {err}");
                                break;
                            }
                        }
                    }
                } else {
                    break;
                }
            } else {
                break;
            }
        }

I am using Arc<TrackLocalStaticRTP> in several RTCPeerConnection
The error appears when closing several RTCPeerConnection

I suspect it was ported when @algesten moved the error type from anyhow to thiserror, anyhow is more stringly typed.
I think the way forward here is to start converting the errors that use the new variant to bespoke variants.
PRs that do this are welcome I expect


Stubs are not activated for appengine_config

I've some api calls inside of appengine_config, and since it's imported before any stubs being activated – my tests fails.
I could probably activate them manually as a workaround, but maybe it's worth to move import appengine_config inside of startTest?
Or, maybe, it's just a bad idea to use any api there.

Or, maybe, it's just a bad idea to use any api there.
I am going to go with this. I wouldn't use any api as an import side effect. If you are going to include api calls in there, they should be inside of a function that you call after the fact.


netty client source

I want to add netty client source to my project, which part of code is for netty client?

plz start with http://netty.io/wiki/user-guide-for-4.x.html and then ask specific questions after you have tried a few examples? If you are able to improve the docs after that would also be greatly appreciated.