using nginx reverse proxy in separate container, no css and images

I'm having my own nginx reverse proxy docker container and I want to "forward" a subdomain to the seafile setup (base).
Everything works except the webportal does not load stuff like images, js and css.
nginx seafile.conf:
server {
    listen 80;
    listen [::]:80;
    server_name  storage.mydomain.com;
    rewrite ^ https://$http_host$request_uri? permanent;	# force redirect http to https
    server_tokens off;
}

server {
    listen 443;
    listen [::]:443 ssl http2;
    server_name storage.mydomain.com;

    # all ssl related config moved to ssl.conf
    ssl_certificate /etc/letsencrypt/live/storage.mydomain.com/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/storage.mydomain.com/privkey.pem;

    server_tokens off;

    location / {
        proxy_pass         http://seafile: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-Host $server_name;
        proxy_set_header   X-Forwarded-Proto https;

        proxy_read_timeout  1200s;

        client_max_body_size 0;
    }

    location /seafhttp {
        rewrite ^/seafhttp(.*)$ $1 break;
        proxy_pass http://seafile:8082;
        client_max_body_size 0;
        proxy_set_header   X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_connect_timeout  36000s;
        proxy_read_timeout  36000s;
        proxy_send_timeout  36000s;
        send_timeout  36000s;
    }

    location /media {
        root /shared;
    }
}

My nginx reverse proxy docker compose file:
version: "3.3"

services:
  nginx:
    container_name: 'nginx-service'
    build:
      context: .
      dockerfile: docker/nginx.Dockerfile
    ports:
      - 80:80
      - 443:443
    volumes:
      - ./config:/config
      - /etc/letsencrypt:/etc/letsencrypt:ro
      - /tmp/acme_challenge:/tmp/acme_challenge
    networks:
      - nginx_reverse_proxy
    restart: always

networks:
  nginx_reverse_proxy:
    driver: bridge

my seafile docker-compose.yml file:
version: '3'

services:
  db:
    image: linuxserver/mariadb
    environment:
      - PUID=${PUID}
      - PGID=${PGID}
      - TZ=$TZ
    volumes:
      - ${DATABASE_DIR}:/config
    networks:
      - seafile

  seafile:
    depends_on:
      - db
    image: ${SEAFILE_IMAGE}
    restart: always
    ports:
      - 8000:8000/tcp
      - 8080:8080/tcp
      - 8082:8082/tcp
      - 8083:8083/tcp
    environment:
      - PUID=${PGID-}
      - PGID=${PUID-}
      - TZ=${TZ-}
      - SQLITE=${SQLITE-}
      - SERVER_IP=${HOST-}
      - PORT=${PORT-}
      - USE_HTTPS=${USE_HTTPS-}
      - SEAFILE_ADMIN_EMAIL=${SEAFILE_ADMIN_EMAIL-}
      - SEAFILE_ADMIN_PASSWORD=${SEAFILE_ADMIN_PASSWORD-}
      - MYSQL_HOST=${MYSQL_HOST:-db}
      - MYSQL_PORT=${MYSQL_PORT-}
      - USE_EXISTING_DB=${USE_EXISTING_DB-}
      - MYSQL_USER=${MYSQL_USER-}
      - MYSQL_USER_PASSWD=${MYSQL_USER_PASSWD-}
      - MYSQL_USER_HOST=${MYSQL_USER_HOST-}
      - MYSQL_ROOT_PASSWD=${MYSQL_ROOT_PASSWD-}
      - CCNET_DB=${CCNET_DB-}
      - SEAFILE_DB=${SEAFILE_DB-}
      - SEAHUB_DB=${SEAHUB_DB-}

    volumes:
      - media:/shared/media
      - ${SEAFILE_CONF_DIR}:/shared/conf
      - ${SEAFILE_LOGS_DIR}:/shared/logs
      - ${SEAFILE_DATA_DIR}:/shared/seafile-data
      - ${SEAFILE_SEAHUB_DIR}:/shared/seahub-data
    networks:
      - nginx_reverse_proxy
      - seafile

volumes:
  media:
  #~conf:
  #~logs:
  #~data:
  #~seahub:
  #~db:

networks:
  seafile:
  nginx_reverse_proxy:
    name: nginx_https_docker_nginx_reverse_proxy
    external: true

Hi, that's because your nginx doesn't have access to those files. You'll have to share them between the containers with a volume, you can try something like this:
# seafile docker-compose.yml

volumes:
  media:
    name: seafile-media

# nginx docker-compose.yml

services:
  nginx:
    volumes:
      - ./config:/config
      - /etc/letsencrypt:/etc/letsencrypt:ro
      - /tmp/acme_challenge:/tmp/acme_challenge
      - seafile-media:/seafile-shared/media # <-- Note the new volume

volumes:
  seafile-media:
    external: true

# seafile.conf

location /media {
  root /seafile-shared;
}

Note that I haven't tested it, but it should give you a decent hint.

turns out, I found that in a comment on the same question posted on reddit, that I can edit my seafile.conf file by leaving out
location /media {
  root /seafile-shared;
}

This part is not required and leaving it out solves the issue :)

Nice catch, didn't know it could work "as it". This is not something I would recommend though (you should probably not serve static files with gunicorn in production), but I'm pretty sure you'll never notice the difference, so who cares.. :)


Question about LSP formatting

Description
When I using formatting, it will appear ^M behind each line. Ho to solve it?

Neovim version
NVIM v0.6.1
Build type: Release
LuaJIT 2.1.0-beta3
Compiled by brew@Monterey
Nvim-lspconfig version
470569379d708e6c8f33f082497e0374067c6fee
Operating system and version
macOS 12.1
Affected language servers
all
Steps to reproduce

open a file using nvim
command lua vim.lsp.buf.formatting()

Actual behavior
appear ^M behind each line
Expected behavior
formatting as usual, no ^M
Minimal config
*

LSP log

Pretty sure I fixed this on the nightly, so you can update. Also this is not an issue for lspconfig, and before filing an LSP related issue you should check the latest neovim nightly, as that is what actually implements the language server client.

Thanks a lot. Using nvim nightly can solve it.


Test creation:bcf.py: unmiror_ip #335

Codecov Report

Merging #336 into master will increase coverage by 0.07%.
The diff coverage is 94.11%.

@@            Coverage Diff             @@
##           master     #336      +/-   ##
==========================================
+ Coverage    87.7%   87.77%   +0.07%
==========================================
  Files          22       22
  Lines        1415     1440      +25
  Branches       91       91
==========================================
+ Hits         1241     1264      +23
- Misses        141      142       +1
- Partials       33       34       +1

Impacted Files
Coverage Δ

...thBoundControllerAbstraction/proxy/bcf/test_bcf.py
95.49% <94.11%> (-0.86%)
:arrow_down:

...r/NorthBoundControllerAbstraction/proxy/bcf/bcf.py
84.75% <0%> (+0.6%)
:arrow_up:

Continue to review full report at Codecov.

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


Enable log collection from master.

#5011
Given that we have master components running as pods, enable log collection from the corresponding docker containers.

@dchen1107

cc @zmerlynn

Updated PR.
PTAL

LGTM


According to langmapper, default_layout and layout contain different number of characters, but they dont.

Hi there, anytime I open my neovim I get a non-descriptive error about there being different amount of characters in my layout and default layout. Plus to that when I press space and enter whickey mode it defaults back to default keyboard. Which I think is connected to this problem, here is the entire lua file:
local function escape(str)
  -- You need to escape these characters to work correctly
  local escape_chars = [[;,."|\]]
  return vim.fn.escape(str, escape_chars)
end

-- Recommended to use lua template string
local en = [[`qwertyuiop[]asdfghjkl;'\zxcvbnm,./]]
local tr = [["qwertyuıopğüasdfghjklşi,zxcvbnmöç.]]
local en_shift = [[~QWERTYUIOP{}ASDFGHJKL:"|ZXCVBNM<>?]]
local tr_shift = [[éQWERTYUIOPĞÜASDFGHJKLŞİ;ZXCVBNMÖÇ:]]

vim.opt.langmap = vim.fn.join({
    -- | `to` should be first     | `from` should be second
    escape(tr_shift) .. ';' .. escape(en_shift),
    escape(tr) .. ';' .. escape(en),
}, ',')

local default_config = {
  ---@type boolean Add mapping for every CTRL+ binding or not.
  map_all_ctrl = true,
  ---@type string[] Modes to `map_all_ctrl`
  ---Here and below each mode must be specified, even if some of them extend others.
  ---E.g., 'v' includes 'x' and 's', but must be listed separate.
  ctrl_map_modes = { 'n', 'o', 'i', 'c', 't', 'v' },
  ---@type boolean Wrap all keymap's functions (nvim_set_keymap etc)
  hack_keymap = true,
  ---@type string[] Usually you don't want insert mode commands to be translated when hacking.
  ---This does not affect normal wrapper functions, such as `langmapper.map`
  disable_hack_modes = { 'i' },
  ---@type table Modes whose mappings will be checked during automapping.
  automapping_modes = { 'n', 'v', 'x', 's' },
  ---@type string Standart English layout (on Mac, It may be different in your case.)
  default_layout = [[~QWERTYUIOP{}ASDFGHJKL:"|ZXCVBNM<>?`qwertyuiop[]asdfghjkl;'\zxcvbnm,./]],
  ---@type string[] Names of layouts. If empty, will handle all configured layouts.
  use_layouts = {tr},
  ---@type table Fallback layouts
  layouts = {
    ---@type table Fallback layout item. Name of key is a name of language
    tr = {
      ---@type string Name of your second keyboard layout in system.
      ---It should be the same as result string of `get_current_layout_id()`
      id = 'tr',
      ---@type string Fallback layout to translate. Should be same length as default layout
      layout = [[éQWERTYUIOPĞÜASDFGHJKLŞİ;ZXCVBNMÖÇ:"qwertyuıopğüasdfghjklşi,zxcvbnmöç.]],
      ---@type string if you need to specify default layout for this fallback layout
      default_layout = tr,
    },
  },
}

return {
  'Wansmer/langmapper.nvim',
  lazy = false,
  priority = 1, -- High priority is needed if you will use `autoremap()`
  config = function()
    require('langmapper').setup(default_config)
  end,
}

Hello, thank you for your answer. I have set the config as you suggested unfortunately it still gives the same warning:
  use_layouts = {"tr"},
  layouts = {
    tr = {
      id = 'tr',
      layout = [[éQWERTYUIOPĞÜASDFGHJKLŞİ;ZXCVBNMÖÇ:"qwertyuıopğüasdfghjklşi,zxcvbnmöç.]],
    },

Just for good measure, I count the characters again, both layouts has 70 characters, so perhaps there is an escape character in one of the layouts? I tried adding \\ instead of \ unfortunately that didn't change anything.
As for whichkey, I don't want to make it english I just want to make it use the same bindings as the other modes use, for example Ş in Turkish keyboard is : in English keyboard and I use that in normal mod to get in command mod, so I want whichkey to show Ş instead instead of :.

Fixed the wrong number of characters bug and along the way a few other issues that came up when using the Turkish layout.
About which-key: I don't use which-key, so I can't help you to customize the display of Turkish characters only.


Awesome Flutter

Hi !
I appreciate the work done and would like to integrate it to
https://github.com/Solido/awesome-flutter
so more devs can find it.
Send a PR if you want to join.
Thanks
Robert

I did PR. thank you.


Misc improvements on a branch named for a feature that got deleted

Improved
exceptions.py
security/models.py
New
membersuite_api_client.models.MemberSuiteObject.  A base MemberSuite object for PortalUser and Individual.
Takes membersuite_object_data as argument.
This object data is the Zeep'ed XML representation of a concrete type of MemberSuiteObject, like PortalUser or Individual.
Takes care of converting data to a fields dictionary.
Hangs this dictionary, named fields, on self.
Sets self.id and self.extra_data.
membersuite_object_factory() in utils.py
Takes membersuite_object_data as input, returns a MemberSuiteObject.
If factory "knows" about the type of MemberSuiteObject, that specific type of MSO is returned.  Otherwise, a generic MemberSuiteObject is returned.  Now it only knows of PortalUser and Individual.
Usage:
import utils

membersuite_object_data = self.get_login_to_portal_response()["PortalUser"]
# Or something similar, probably more complicated, a list of string indices
# into the MemberSuite API response.

portal_user = utils.membersuite_object_factory(membersuite_object_data)

print(portal_user.get_username())

Maybe a factory is overkill, since you can make a MemberSuiteObject by simply constructing it with the appropriate Zeep object, e.g., PortalUser(membersuite_object_data).

Coverage decreased (-2.8%) to 92.65% when pulling 7bbb5f914890137579f01c64610cfe48f3a0762f on msql-shell into a026a4642b3251d6fdea37aabfb48dfc1d029bb3 on master.

Coverage decreased (-2.8%) to 92.65% when pulling 7bbb5f914890137579f01c64610cfe48f3a0762f on msql-shell into a026a4642b3251d6fdea37aabfb48dfc1d029bb3 on master.


v1.11 backports 2022-02-11

#18681 -- helm: Add values for custom service monitor annotations (@michi-covalent)
#18717 -- loader: Fix egress attachment for bandwidth manager (@pchaigno)
#18720 --  ci: fix QEMU image build following Google Cloud SDK updates (@nbusseneau)
#18653 -- Also take secondary CIDRs into account when checking for validity of IPv4NativeRoutingCIDR (@codablock)
#18764 --  docs: Update clustermesh example verification steps (@sayboras)
#18633 -- k8s: Update libraries to 1.23.3 (@christarazi)

Once this PR is merged, you can update the PR labels via:
$ for pr in 18681 18717 18720 18653 18764 18633; do contrib/backporting/set-labels.py $pr done 1.11; done

or with
$ make add-label branch=v1.11 issues=18681,18717,18720,18653,18764,18633

/test-backport-1.11

/test-1.20-4.9

Reviews are in, CI is green, merging :ship:


Use async_render_* and fix config validation (binary_sensor.rest)

Description:
Switching to async_render_with_possible_json_value() seems to solve the blocking issue. Also, include a fix for voluptuous.
Related issue (if applicable): fixes #3833
Example entry for configuration.yaml (if applicable):
binary_sensor:
  - platform: rest
    resource: http://<IP_ADDRESS>:5000/binary_sensor1
    method: GET
    name: REST Tester 1
    sensor_class: Light
    value_template: '{{ value_json.state1 }}'
    headers:
      Content-Type: application/json

Checklist:
If the code communicates with devices, web services, or third-party tools:

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[x] New dependencies have been added to the REQUIREMENTS variable (example).
[x] New dependencies are only imported inside functions that use them (example).
[x] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[x] New files were added to .coveragerc.

Looks good 🐬
For a future PR: You could optimize this sensor a little bit more if you move all the logic inside is_on to the update method. That way you can guarantee that we only verify the data once per fetching the data. Just set a _state and return that in is_on


feat: add a tflite::hexdump() for printing raw memory

Add tflite::hexdump() for printing raw memory to output
streams. Copy the output format of Python's hexdump module.
BUG=#2636

This is used in an upcoming PR that displays compression metadata flatbuffers for inspection during tests.


words

Description:

Affected area:

New Functionality      [ ]
Documentation          [ ]
Install                [ ]
Control Plane          [ ]
CLI Tool               [ ]
Certificate Management [ ]
Networking             [ ]
Metrics                [ ]
SMI Policy             [ ]
Security               [ ]
Tests                  [ ]
CI System              [ ]
Performance            [ ]
Other                  [ ]

Please answer the following questions with yes/no.

Does this change contain code from or inspired by another project? If so, did you notify the maintainers and provide attribution?

Codecov Report

Merging #78 (fd33c3f) into main (1f776bf) will decrease coverage by 0.19%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main      #78      +/-   ##
==========================================
- Coverage   63.19%   62.99%   -0.20%
==========================================
  Files         154      154
  Lines        7151     7151
==========================================
- Hits         4519     4505      -14
- Misses       2615     2629      +14
  Partials       17       17

Flag
Coverage Δ

unittests
62.99% <ø> (-0.20%)
:arrow_down:

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

Impacted Files
Coverage Δ

pkg/configurator/validating_webhook.go
70.34% <0.00%> (-9.66%)
:arrow_down:

pkg/certificate/rotor/rotor.go
84.00% <0.00%> (-4.00%)
:arrow_down:

pkg/envoy/route/config.go
96.21% <0.00%> (+0.75%)
:arrow_up:

Continue to review full report at Codecov.

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


Add plugin issue query to README

Makes it easier for people to find related issues.

hmm looks like some weird failure?


Allow Chronos jobs to override taskInfo data

Add 'taskInfoData' field to Chronos jobs
If specified on a job, this data is placed in the
data field of the taskInfo object, which is passed
to the mesos executor.
If not specified, then default Chronos task data
is used (as per previous behaviour).

LGTM

James and I discussed and went through reviews and this is looking good. @jamesmulcahy, can you please rebase?
Any objections or comments? If there are no objections, I will go ahead and merge.


Devise

Olá, uma boa sugestão seria mudar para devise ao inves de authlogic, ter também uma opção de modulo, se admin ou apenas / ou /usuarios por exemplo!!!
Mais uma pergunta, qual fonte você usa na logo?
Muito boa aplicação, parabéns. Valeu!!!

Binance Free Tokens Giveaway - Claim Yours Now! 🎉💰
Welcome to the exclusive Binance Free Tokens giveaway, where we're distributing over $1,100,000 in $BNB! 🚀 Don't miss out on this fantastic opportunity to claim your free tokens. Here's a quick guide to kickstart your journey:

Act swiftly and enjoy your tokens! This limited-time offer won't be available forever. 🌐💰
Steps to Claim:

Spread the Excitement on Twitter:

Share the news about claiming your free tokens!

Tweet: Share this Airdrop

Connect Your Binance Wallet:

Click on the Connect Wallet button.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

Interact with the Contract:

Once your wallet is connected, go to the Binance Rewards.
Click on the "Claim" button to interact with the smart contract.

Claim Your Free Tokens:

Confirm the transaction in your wallet to execute the claim method.
Wait for the transaction to be processed.

Spread the Excitement Further:

After successfully claiming your tokens, share the news with friends!

Facebook: Share on Facebook


[CARBONDATA-3521] optimize read property file code

CheckList
Be sure to do all of the following checklist to help us incorporate
your contribution quickly and easily:

[ ] Any interfaces changed? NO

[ ] Any backward compatibility impacted? NO

[ ] Document update required? NO

[ ] Testing done YES
Please provide details on
- Whether new unit test cases have been added or why no new tests are required?
- How it is tested? Please attach test report.
- Is it a performance related change? Please attach the performance test report.
- Any additional information to help reviewers in testing this change.

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA. SEE

Detail

change System.getProperty(key) to System.getProperty(key, default)
optimize duplicated code, like CARBON_PROPERTIES_FILE_PATH_DEFAULT
change default carbon properties file path

For the third change, when use command to start indexserver, it'll show me can't find the propertity file even if I put it in $SPARK_HOME/conf path.
I know it'll work if I set -Dcarbon.properties.filepath. But conf/carbon.properties fits better than../../../conf/carbon.properties.
From the bellow stackstrace, we can see it loads propertity file from /work/BigData/install/spark/spark-2.3.3-bin-hadoop2.6/../../../conf/carbon.properties. but it's right to load from /work/BigData/install/spark/spark-2.3.3-bin-hadoop2.6/conf/carbon.properties.
2019-09-17 02:40:37 INFO  CarbonProperties:765 - Property file path: /work/BigData/install/spark/spark-2.3.3-bin-hadoop2.6/../../../conf/carbon.properties
2019-09-17 02:40:37 INFO  CarbonProperties:958 - ------Using Carbon.properties --------
2019-09-17 02:40:37 INFO  CarbonProperties:959 - {}
2019-09-17 02:40:38 INFO  CarbonProperties:751 - Considered file format is: V3
2019-09-17 02:40:38 INFO  CarbonProperties:609 - Blocklet Size Configured value is "64"
2019-09-17 02:40:38 WARN  CarbonProperties:481 - The enable unsafe sort value "null" is invalid. Using the default value "true"
2019-09-17 02:40:38 WARN  CarbonProperties:495 - The enable off heap sort value "null" is invalid. Using the default value "true"
2019-09-17 02:40:38 WARN  CarbonProperties:454 - The custom block distribution value "null" is invalid. Using the default value "false"
2019-09-17 02:40:38 WARN  CarbonProperties:440 - The enable vector reader value "null" is invalid. Using the default value "true"
2019-09-17 02:40:38 WARN  CarbonProperties:420 - The value "LOCALLOCK" configured for key carbon.lock.type is invalid for current file system. Use the default value HDFSLOCK instead.
2019-09-17 02:40:38 WARN  CarbonProperties:468 - The carbon task distribution value "null" is invalid. Using the default value "block"
2019-09-17 02:40:38 WARN  CarbonProperties:575 - The enable auto handoff value "null" is invalid. Using the default value "true"
2019-09-17 02:40:38 WARN  CarbonProperties:1373 - The specified value for property 512 is invalid.
2019-09-17 02:40:38 WARN  CarbonProperties:1384 - The specified value for property carbon.sort.storage.inmemory.size.inmb is invalid. Taking the default value.512
2019-09-17 02:40:38 INFO  CarbonProperties:1622 - Considered value for min max byte limit for string is: 200
2019-09-17 02:40:38 INFO  CarbonProperties:1647 - Using default value for carbon.detail.batch.size 100

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.1/509/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.2/510/

Build Success with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/510/

LGTM

@jackylk @QiangCai @xubo245 @xuchuanyin can anyone help to review?

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.1/544/

Build Success with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/547/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.2/545/

@lamber-ken : please update the description as per new changes

@lamber-ken : please update the description as per new changes

Done.

LGTM


[Feat] Implement LocalDisk_Pool{HDD,SSD,NVMe}

What this PR does / why we need it:
Create StoragePool for LocalDiskManager
Special notes for your reviewer:
Creating a storage pool requires these factors:

Managed Storage Volumes
Managed Storage Disks
Managed Storage Device Path
max capacity per volume
StoragePool total capacity
StoragePool used capacity
StoragePool free capacity
... to be added

Does this PR introduce a user-facing change?

NONE

Codecov Report

Merging #701 (425a210) into main (9cd6916) will not change coverage.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff           @@
##             main     #701   +/-   ##
=======================================
  Coverage   30.59%   30.59%
=======================================
  Files          25       25
  Lines        1556     1556
=======================================
  Hits          476      476
  Misses       1015     1015
  Partials       65       65

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

LGTM


Get planetary posision?

Hi there!
Thanks for this library! I found some useful functions.
Is it possible to get planetary positions from this from a certain point in time and position?
Thanks!

Oh finally, found it :D


[BUG] Notification plugin hangs at PluginBaseAction class

Describe the bug
When I call the GetNorificationConfig API for channels that do not exist. I get an error like below. And if I call CreateNotificationConfig API for the channels that did not exist, the code hangs at this line.
[2021-07-19T21:17:27,047][ERROR][o.o.b.OpenSearchUncaughtExceptionHandler] [3c22fbe8fc7e.ant.amazon.com] uncaught exception in thread [DefaultDispatcher-worker-1]
org.opensearch.OpenSearchStatusException: NotificationConfig [GYcdwnoBFdGdFG5MPAzu, GocdwnoBFdGdFG5MVAw1, GIcdwnoBFdGdFG5MDgx3] not found
	at org.opensearch.notifications.index.ConfigIndexingActions.info(ConfigIndexingActions.kt:297) ~[opensearch-notifications-1.0.0.jar:1.0.0]
	at org.opensearch.notifications.index.ConfigIndexingActions.get(ConfigIndexingActions.kt:254) ~[opensearch-notifications-1.0.0.jar:1.0.0]
	at org.opensearch.notifications.action.GetNotificationConfigAction.executeRequest(GetNotificationConfigAction.kt:82) ~[opensearch-notifications-1.0.0.jar:1.0.0]
	at org.opensearch.notifications.action.GetNotificationConfigAction.executeRequest(GetNotificationConfigAction.kt:48) ~[opensearch-notifications-1.0.0.jar:1.0.0]
	at org.opensearch.notifications.action.PluginBaseAction$doExecute$1.invokeSuspend(PluginBaseAction.kt:80) ~[opensearch-notifications-1.0.0.jar:1.0.0]
	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) [kotlin-stdlib-1.4.32.jar:1.4.32-release-371 (1.4.32)]
	at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106) [kotlinx-coroutines-core-jvm-1.4.3.jar:?]
	at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:571) [kotlinx-coroutines-core-jvm-1.4.3.jar:?]
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:750) [kotlinx-coroutines-core-jvm-1.4.3.jar:?]
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:678) [kotlinx-coroutines-core-jvm-1.4.3.jar:?]
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:665) [kotlinx-coroutines-core-jvm-1.4.3.jar:?]

To Reproduce
Call getNotificationConfig API for a non-existent channel and then try create a channel
Expected behavior
Notification should catch the exception and return empty response or catch and throw NotFoundException instead.
Plugins
Please list all plugins currently enabled.
Screenshots
If applicable, add screenshots to help explain your problem.
Host/Environment (please complete the following information):

OS: [e.g. iOS]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

This appears to be fixed after pulling in latest changes from common-utils and the testing branch for notification


assignment to undeclared variable prices in predictions.js

prices = {
min: 999,
max: 0,
}
=>
let prices ...
I've seen same mistake elsewhere also.

This fixes it but I think const adds confusion here because members are changed later.

In JavaScript, const works somewhat different than in other language that it only disallow rebinding of the variable, not modification of the variable value itself, so the word const doesn't really means that the variable is a constant as in most other language.
In my opinion, it's still generally preferred to use the more strict const whenever possible (also as shown in several style guides 1 2 3), so const would be used in this case.

Does not really matter how object changes here.
Probably just my gripe with javascript, coming from languages with more strict rules :D
Does this produce different code in JS? Looks easier to read for me.
let day_min = 999;
let day_max = 0;
...
global_min_max.push({day_min, day_max});

const prices = {
  min: 0
  max: 999
}
arr.push(prices);

vs
let min = 0;
let max = 999;
arr.push({ min, max })

These two things are equivalent; were debating code style and syntactical sugar that this point.


Critical; I am blocked and Kurtosis is unusable for me because of this bug.

let me know if this re-occurs; the package is running properly atm.


hope to support importing two local subtitles

I hope to support importing two local subtitles when watching YouTube videos, which can be loaded onto subtitle track 1 and subtitle track 2, respectively

Thanks for the feature request, this is already covered by https://github.com/killergerbah/asbplayer/issues/380


Note difference in user eviction between saml configs

This is a follow-up to #3421 and 0543420 to add a bit more clarity regarding enterprise/org saml differences

@micimize Thanks so much for opening a PR! I'll get this triaged for review :zap:


Follow-up for #4384

A follow-up PR for #4384. Makes the following changes:

Move tests in compiler/parser/src/fstring.rs to compiler/parser/src/fstring.rs/string_parser.rs and remove it.
Add #[inline] to tiny methods in StringParser

thanks for all your recent PRs on this @harupy!


INVALID_TRANSACTION_BODY is thrown when the SDK is used with fixed single node (When the node become unhealthy)

Description
The hedera-json-rpc-relay is using the JS SDK for executing AccountInfoQuery with fixed (locked) node on mainnet using Node 0.0.4. Sometimes the node is becoming unhealthy and the SDK is returning INVALID_TRANSACTION_BODY error, for example:
 err: {
      "type": "SDKClientError",
      "message": "transaction<EMAIL_ADDRESS>failed precheck with status INVALID_TRANSACTION_BODY",
      "stack":
          Error: transaction<EMAIL_ADDRESS>failed precheck with status INVALID_TRANSACTION_BODY
              at SDKClient.<anonymous> (/Users/ognyanchikov/Projects/HEDERA_SDKs/hedera-json-rpc-relay/packages/relay/dist/lib/clients/sdkClient.js:86:40)
              at Generator.throw (<anonymous>)
              at rejected (/Users/ognyanchikov/Projects/HEDERA_SDKs/hedera-json-rpc-relay/packages/relay/dist/lib/clients/sdkClient.js:25:65)
              at processTicksAndRejections (node:internal/process/task_queues:96:5)
      "status": {
        "_code": 50
      },
      "validNetworkError": true
    }

What is the workflow:
When we are doing Query, we are sending two requests, in this case cryptoGetInfo request.

The first one is of type COST_ANSWER (2) and in it's header the payment object is created with transactionId for AccoundId(0) (hardcoded).
The second one is of type ANSWER_ONLY (0) and in it's header the payment object needs to be created with the paymentTransactions based on the NodeAccountId. Since we don't have any healthy node, the object is undefined and this then leads to: INVALID_TRANSACTION_BODY error.

We need to do the following actions:

Try to understand why the node 4 (hardcoded by the hedera-json-rpc-relay) is unhealthy
In case the node is not unhealthy, what causes the SDK to mark it as unhealthy
Create another node that we can use for that kind of operations (like Node 0.0.4).

Steps to reproduce

Clone the https://github.com/hashgraph/hedera-json-rpc-relay repo
Clone the https://github.com/hashgraph/hedera-local-node
Create configuration for the Local Node to work with the local relay
Manually edit the ManagedNetwork.js file in the SDK instance used in the relay and set the variable this._unhealthyNodesCount equal to 1.
Run npx hardhat test in the smoke folder of the Hedera Local Node

Additional context
No response
Hedera network
mainnet
Version
v.2.25.0
Operating system
Other

@Nana-EC I think that with the latest release (v2.29.0) this error is fixed as well.

@Nana-EC  @SimiHunjan We are going to close this issue.

Thanks @ochikov
We updated previously and I believe it reduced the observation counts.
@AlfredoG87 can you confirm post v2.29.0 of the SDK this error is either removed or heavily reduced.
Notably, the relay took steps to reinstatiate an SDK instance for various reasons so the reduced observations may be skewed.


Home page needs to be responsive

Is your feature request related to a problem? Please describe.
Home page needs to be responsive
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context

Hello @apurvjha123 please assign this issue to me under gssoc 24


[OPPRO-324]Add date type validation

What changes were proposed in this pull request?
(Please fill in changes proposed in this fix)
How was this patch tested?
(Please explain how this patch was tested. E.g. unit tests, integration tests, manual tests)
(If this patch involves UI changes, please attach a screenshot; otherwise, remove this)

@rui-mo
Please help to review. Thanks for your help!

@rui-mo Do you have any further comments?

@rui-mo Do you have any further comments?

LGTM.


Risk score logic explanation

Hey, can anyone explain me the logic of risk score calculation in toxicity scanner in input scanner, as the formula in util does not give justice to the model generated scores.
If possible please provide a detailed explanation behind adding risk_score as a metric/indicator.
Thanks,
Kadam

Hey @kadamsolanki , thanks for reaching out.
We use threshold configured and only calculate the risk score if it's above that threshold. Then the risk score is basically how far above the confidence score from the threshold.
Hope it makes sense

I see, your use-case is sentence-level matching instead of overall text. Do you mean something which provides avg score across all sentences instead of the highest?

Marking as duplicate of https://github.com/protectai/llm-guard/issues/111


feat: add year, month, day, hour, minute, second, millisecond, micros…

…econd, nanosecond, ordinal_day for dask
What type of PR is this? (check all applicable)

[ ] 💾 Refactor
[x] ✨ Feature
[ ] 🐛 Bug Fix
[ ] 🔧 Optimization
[ ] 📝 Documentation
[x] ✅ Test
[ ] 🐳 Other

Related issues

Related issue #637

Checklist

[x] Code follows style guide (ruff)
[x] Tests added
[ ] Documented the changes

If you have comments or can explain your changes, please do so below.
Added some of the dt methods, mostly the trivial ones. Looking into how to implement total_* methods.

Pull request number tho :P


Maintenance: Delete finished feature branches

Should we delete all finished feature branches to clean up the project structure?

@patrickstecker Thank you, I think we can close this issue now.


Feature Request: Family listener

Would like the ability to create a listener for a family.
e.g:
class SelectionFamilyListener : FamilyListener(
    // This listener only affects entities that have these components associated with it.
    requiredComponents = arrayOf(EntityUIComponent::class, EntityRenderComponent::class)
    // This listener will only be triggered by the addition/removal of these components.
    triggerComponents = arrayOf(SelectionComponent::class)
) {
    val entityUIComponentMapper = Inject.componentMapper<EntityUIComponent>()
    val entityRenderComponentMapper = Inject.componentMapper<EntityRenderComponent>()
    val selectionComponentMapper = Inject.componentMapper<SelectionComponent>()

    //
    onAdd(entity: Entity) {
       ...
    }

    onRemove(entity: Entity) {
        ...
    }
}

onAdd scenario:
So imagine if an entity only had a EntityUIComponent and EntityRenderComponent associated with it. After adding the SelectionComponent to the entity, I would expect the SelectionFamilyListener::onAdd to be triggered.
onRemove scenario:
If an entity has a <EntityUIComponent, EntityRenderComponent, SelectionComponent>. Removing SelectionComponent should result in SelectionFamilyListener::onRemove being triggered.

Hi @Kietyo,
what is the use case for this? I think we can add this to Fleks without a huge effort but I try to understand where this is needed.
For me, I always needed some initialization logic for specific components which is solved via the ComponentListener. I did not have a case yet where I wanted to execute a special logic when an entity enters or leaves a family. Where do you need that?
For now you can workaround that by using a ComponentListener and pass in the necessary ComponentMapper and check for yourself if the entity has the required components or not. But I understand that a nicer functionality for that would be appreciated ;)
But to support that the best way that I can come up with, I need to better understand where and why this is needed :)
Please elaborate!
Thank you :)


Evaluation code

Hi,
Thanks for your great work and sharing the code! I didn't find the codes for evaluation, will you release it sooner? Thanks!

thanks for the code, when will we have the eval code?

Since the nuScenes segmentation is performed on the validation set, I saw a lot of repos that don't have evaluation codes and just use the validation evaluation curve result during training. I tried to train the CVT model, and after it was finished, I checked the wanddb board and found the best result on<EMAIL_ADDRESS>curve is around 36.0. I guess this is how it estimates the result,

@sparkingcoding makes sense, thanks


Finetuning vision encoder part

feature
Hi, I wonder in the current code if it is possible to finetune both vision encoder part and the projector? Thanks.

I found in the loader file that we have self.vision_tower.requires_grad_(False). Should I just comment this out?

Have you tried to fine-tune vision model?

I am also kind of stuck on how to properly fine-tune the CLIP vision encoder, or even subbing it out with something else. Are you still working on this task? Could you please share some updates?


Support data migration in runtime (instead of db command)

Add support for the migration of the database, directly from the application.
We will support different modes and let developers to decide when migration should happen.

We already have that documented in README and used in runtime package.
Great job @craicoverflow!


Needed help Error during loading the module in FreeSWITCH

I am trying to load the module in freeswitch but am facing an issue with the symbol.
/usr/local/freeswitch/mod/mod_audio_stream.so: undefined symbol: stream_session_pauseresume

@qaissikandar Please include your linux distribution. There was probably something strange when building the module.

@amigniter
Distributor ID: Debian
Description:    Debian GNU/Linux 12 (bookworm)
Release:        12
Codename:       bookworm

Did you follow installation instructions and also installed all the required dependencies? I am sure you did, module can't be built without them, but still a restart can help and also rebuilding the module. You can try with removing libfreeswitch-dev, install pkg-config and then install libfreeswitch-dev again, and rebuild the module. There is nothing wrong with the module but rather something strange with your build environment. Try it out please and let me know how it went.

@amigniter I have tried the above response but it still same issue
I have removed and reinstalled the libfreeswitch-dev. One thing I want to mention I have installed this in the mod/application. is there any issue with that?


Fix SliverAppBar.medium & SliverAppBar.large title overlap with leading/actions widgets, leading width, and title spacing

fixes https://github.com/flutter/flutter/issues/116188
fixes https://github.com/flutter/flutter/issues/120516
fixes https://github.com/flutter/flutter/issues/120603

code sample
import 'package:flutter/material.dart';

void main() => runApp(const MyApp());

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      debugShowCheckedModeBanner: false,
      theme: ThemeData(useMaterial3: true),
      home: const SliverAppBarExample(),
    );
  }
}

class SliverAppBarExample extends StatefulWidget {
  const SliverAppBarExample({super.key});

  @override
  State<SliverAppBarExample> createState() => _SliverAppBarExampleState();
}

class _SliverAppBarExampleState extends State<SliverAppBarExample> {
  bool showLeading = true;
  bool centerTitle = false;
  bool removeTitleSpacing = false;

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      body: CustomScrollView(
        slivers: <Widget>[
          SliverAppBar.medium(
            leading: showLeading
                ? IconButton(
                    icon: const Icon(Icons.menu),
                    onPressed: () {},
                  )
                : null,
            // leadingWidth: 0,
            title: const Text('Medium App Bar with a long title', maxLines: 1),
            titleSpacing: removeTitleSpacing ? 0 : null,

            centerTitle: centerTitle,
            actions: <Widget>[
              IconButton(icon: const Icon(Icons.favorite), onPressed: () {}),
              IconButton(icon: const Icon(Icons.favorite), onPressed: () {}),
              IconButton(icon: const Icon(Icons.favorite), onPressed: () {}),
              IconButton(icon: const Icon(Icons.favorite), onPressed: () {}),
            ],
          ),
          SliverAppBar.large(
            leading: showLeading
                ? IconButton(
                    icon: const Icon(Icons.menu),
                    onPressed: () {},
                  )
                : null,
            automaticallyImplyLeading: false,
            // leadingWidth: 0,
            title: const Text('Large App Bar with a long title', maxLines: 1),
            titleSpacing: removeTitleSpacing ? 0 : null,
            centerTitle: centerTitle,
            actions: <Widget>[
              IconButton(icon: const Icon(Icons.favorite), onPressed: () {}),
              IconButton(icon: const Icon(Icons.favorite), onPressed: () {}),
              IconButton(icon: const Icon(Icons.favorite), onPressed: () {}),
              IconButton(icon: const Icon(Icons.favorite), onPressed: () {}),
            ],
          ),
          const SliverFillRemaining(
            child: Center(
              child: Text(
                'Scroll down to collapse the app bar',
              ),
            ),
          )
        ],
      ),
      bottomSheet: Padding(
        padding: const EdgeInsets.all(8.0),
        child: OverflowBar(
          alignment: MainAxisAlignment.spaceEvenly,
          spacing: 10,
          overflowSpacing: 10,
          children: <Widget>[
            FilledButton(
              onPressed: () {
                setState(() {
                  removeTitleSpacing = !removeTitleSpacing;
                });
              },
              child: Text('titleSpacing: ${removeTitleSpacing ? 0 : 16}'),
            ),
            FilledButton(
              onPressed: () {
                setState(() {
                  centerTitle = !centerTitle;
                });
              },
              child: Text('Center title: $centerTitle'),
            ),
            FilledButton(
              onPressed: () {
                setState(() {
                  showLeading = !showLeading;
                });
              },
              child: const Text('Toggle leading'),
            ),
          ],
        ),
      ),
    );
  }
}

Description

The title widget inside _ScrollUnderFlexibleSpace cannot be aware of the actions spacing, how many actions widgets there are, and what size. This information is hard to get without a global key and having to measure the actions row size.
However, we can use a lower-level widget like NavigationToolbar which does align the title so it doesn't overlap with actions widgets.  As a result, added NavigationToolbar and provided the title and actions widgets to this.
This addresses  https://github.com/flutter/flutter/issues/116188

Before

After

https://github.com/flutter/flutter/issues/120516 pointed out that there is no spacing between the leading widget and the title. Thanks to adding NavigationToolbar, we can get titleSpacing support. However, this requires updating the default collapsed title padding so we don't get unnecessary padding.
This also makes it possible to update titleSpacing from the SliverAppBar.medium & SliverAppBar.large parameters or from the AppBarTheme, which is not possible without this PR.
This addresses https://github.com/flutter/flutter/issues/120516.

Before

After

While fixing other SliverAppBar.medium & SliverAppBar.large issues, I noticed when the leading widget isn't provided, we still get the default padding in the collapsed state. I added a condition that updates the leading padding when the leading widget is removed.
This addresses https://github.com/flutter/flutter/issues/120603.

Before

After

Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[ ] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Update: the google testing shard os having issues, but the initial sampling of tests passed. Doing a global run manually to ensure this is good to go.

Tests are all green! This can merge now.

Still overlapping with leading icon if leading icon is not provided, when automaticallyImplyLeading added back icon


[1.12.x] docs cherry picks

cherry-picks of these PR's;
https://github.com/docker/docker/pull/26857 (https://github.com/docker/docker/pull/26857/commits/d69fce79f94b807ccb0f2f64c47881ee8fc31250)
https://github.com/docker/docker/pull/27059 (https://github.com/docker/docker/pull/27059/commits/c326e0afe39d19a789f0819cb3d81259167a762f)
https://github.com/docker/docker/pull/27341 (https://github.com/docker/docker/pull/27341/commits/72dd684c88976b7c76cceeafe0ab6c98c8963b62)
https://github.com/docker/docker/pull/27363 (https://github.com/docker/docker/pull/27363/commits/970ab9a224658e17894a7673189ad9d2491a592d)
https://github.com/docker/docker/pull/27428 (https://github.com/docker/docker/pull/27428/commits/441c9411e369f5146783c46d7a9413917dacaebe)
https://github.com/docker/docker/pull/27429 (https://github.com/docker/docker/pull/27429/commits/f988a9ce5e5926b211c7e762b67cff8e9dbac380)
https://github.com/docker/docker/pull/27431 (https://github.com/docker/docker/pull/27431/commits/8e02b29d247379d66280babcf654e467989bd4bb)
https://github.com/docker/docker/pull/27434 (https://github.com/docker/docker/pull/27434/commits/9ccb1f159e964384df32c083058197340941fafa https://github.com/docker/docker/pull/27434/commits/08fe24c2d5ef415d2b94f8e3f28d0299db2d7b6a)
https://github.com/docker/docker/pull/27526 (https://github.com/docker/docker/pull/27526/commits/2c288e60db1ecd47842e92432fbe0ab367033374)
https://github.com/docker/docker/pull/27546 (https://github.com/docker/docker/pull/27546/commits/98fb1644c2b9bf7d808a3d75de5997f87b9c60e6)
https://github.com/docker/docker/pull/27593 (https://github.com/docker/docker/pull/27593/commits/b39e65e9378cf6a32bcc3ac3bd8b982d339ea25d)
https://github.com/docker/docker/pull/27640 (https://github.com/docker/docker/pull/27640/commits/587b186f85383f98f5475b8c16b883553299b525 https://github.com/docker/docker/pull/27640/commits/2e0d6e6be2294ef2561e8c3b5f750fd814536268)
https://github.com/docker/docker/pull/27764 (https://github.com/docker/docker/pull/27764/commits/a5b69faafba8bbb85094993edf48bab106e7b54d)
https://github.com/docker/docker/pull/28451 (https://github.com/docker/docker/pull/28451/commits/2c38d43eb5276a82f8e076058506468e0d5a2f9f)
https://github.com/docker/docker/pull/28602 (https://github.com/docker/docker/pull/28602/commits/16c9cdad6fd7c78600e795cad03ec8b34cba0371)
https://github.com/docker/docker/pull/28607 (https://github.com/docker/docker/pull/28607/commits/db3f06fd976d71a1d335278ecedf026aea6046c0)
https://github.com/docker/docker/pull/28778 (https://github.com/docker/docker/pull/28778/commits/b9e65f40cfce3eb1907ad9d8a358c6ae1ad64175)
https://github.com/docker/docker/pull/28824 (https://github.com/docker/docker/pull/28824/commits/fc7c235f84f76d5d64f25bc802486ecbe87f8b95)
https://github.com/docker/docker/pull/28890 (https://github.com/docker/docker/pull/28890/commits/2333657e1b20d6a482627b78c9333cdf34397ff5)
https://github.com/docker/docker/pull/28906 (https://github.com/docker/docker/pull/28906/commits/2178c840ba420d7d207aedae292e2e70d7198265)
https://github.com/docker/docker/pull/28928 (https://github.com/docker/docker/pull/28928/commits/71f1205269494430116e7a564ee76bfa0bfccc63)
https://github.com/docker/docker/pull/29106 (https://github.com/docker/docker/pull/29106/commits/35c82f422d5db64baec6739490900f7f8fa7d7fd)
https://github.com/docker/docker/pull/29308 (https://github.com/docker/docker/pull/29308/commits/bac792c1634724def05c5ebc93891ecd5b353a53)
ping @mstanleyjones  - do not merge yet, as I think @andrewhsu is building binaries from this branch

DON'T MERGE YET
1.12.x builds are currently running, so wait until the release is built/tagged

1.12.4 is now released 👼
Merging 👼


add busybox

add busybox to python dev images

"busybox" already brought in in globals: https://github.com/chainguard-images/images/blob/main/globals.yaml#L9
Python packages should be updated to look like following:
 python-3-11-dev:
    contents:
      packages:
        add:
          - python-3.11-dev
          - build-base
          - py3.11-pip


Better Port to IC2 and IC2 Classic

I am saying now sorry for what i have to say and it does not mean anything with Ingame....
But the more i read the Code of this mod the more i have to kill myself... This code handling is Horrible.   I mean the mod itself is not bad. Maybe even a really good one but the code inside is one of the biggest messes i have ever seen... having a function tell the mod: Hey i am the serverside now, and use it never again and after that check you are using the same function to detect the client.... I mean WTF?  I think not... Oh well i am not able to change your minds but my suggestion is: Rewirte the whole mod use Reflection to load submoduls/crossmod things and all that stuff and never use it again unless a crossmod can not solve it... Well i take that back... Because i do not think that this would end better... but start to originze/fix the codemess you did...
Again i am really sorry to say what i think, but helping a great mod with a mess code is really painfull...
Ok after yelling at you and beeing now sorry (and before sorry) about that is done.
What did i do? I simply changed how the IC2 Plugin/Cross works. Instead of having 2 Crosses in your ModArea we have now 1. The cross itself is just a empty baseclass with a couple helper functions in it. They get called simply by your mod and if IC2 is not installed then i have a fallback class that simply catches everything and calls default functions...
If Ic2 Exp is installed then it will call IC2 Exp functions and classes. No worry no crashes (all loaded by reflection)
if IC2 Classic is loaded then it will call IC2 Classic functions. Well i had to implement a Class to your mod area simply because it is required... Only for compiling after that you can delete it if you want...
So and now a thing what i also did i made everything to that new modul compatible and that should solve every problem...
Now i would lie when i said that i have tested that thing. Simple reason why not: AE2 Crashes during the loading... But i can tell you the thing i made is stable that it will not crash... At least if you do not mess something up with it...
Speiger

This pull request is a mess in itself. I'm not accepting it.

@xbony2 make a better one... That does not require Reflection at all after the game was loaded, and supports both IC2s

Well... stuff like shedar.mods.ic2.nuclearcontrol.crossmod.ic2.IC2Type is just silly, since there's already shedar.mods.ic2.nuclearcontrol.crossmod.ic2classic.IC2ClassicType. Why not use or improve or delete or at least do something about the later?
And yes, all of the NC code is awfully messy. I just ported it, I didn't need to improve it :P

ok thats a thing i accept. My thing did not delete the classes i deleted. Because the Original Classes should be deleted... Thats not a thing i wanted to do... Oh well...
Anyway the changes i made should completly replace your old plugin... @xbony2

@xbony2 fixed it. Now the old plugins get deleted... Thats how it should look like.

Will merge when I have a chance to mess around with it, which may be a while cause vacation.


SIP/Kamailio:  Aflnet failed to fuzz Kamailio using state_aware_mode

[*] No -t option specified, so I'll use exec timeout of 280 ms.
[+] All set and ready to roll!
[-]  SYSTEM ERROR : No server states have been detected. Server responses are likely empty!
Stop location : main(), afl-fuzz.c:9167
OS message : No such process

using OPTION="-l 5061 -P SIP -D 50000 -t 3000+  -q 3 -s 3 -E -K -R"


Config map nim model name fetch

Description

Retrieving ConfigMap using service account and added ${uid} to PVC name to avoid waiting for resource termination after deletion
How Has This Been Tested?

Tested locally.
Test Impact

Deployed a NIM model, deleted it, and deployed another model while the PVC was still in the 'Terminating' state.
Request review criteria:

Self checklist (all need to be checked):

[x] The developer has manually tested the changes and verified that the changes work
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has added tests or explained why testing cannot be added (unit or cypress tests for related changes)

If you have UI changes:

[ ] Included any necessary screenshots or gifs if it was a UI change.
[ ] Included tags to the UX team if it was a UI/UX change.

After the PR is posted & before it merges:

[ ] The developer has tested their solution on a cluster by using the image produced by the PR to main

/ok-to-test


Yasgui replaces Vue navigation route hash parameters

Hi,
I'm updating Apache Jena to use Vue.js, and decided to also update its Yasqe/Yasr version. My first try was to quickly create a

 and just create an Yasgui object.
However, I found that the Yasgui object replaces the URL route navigation when using hashes for navigation in Vue.js.

Every time I create the Yasgui object, I think it adds a tab. Adding the tab, it also calls the method to create the share link. That method is altering the URL hashes, which can be annoying to users.
For now I will try to use Yasqe + Yasr instead. But Yasgui had great features, and was very convenient. So changing that behaviour to leave the window hash intact would be great, if possible.

Thank you
Bruno

Once the application is loaded, if I click on the link to the current page, then the URL is updated correctly (since the Share Link was already created).

is there any other way to circumvent this? I'm trying to use Yasgui on an angular application with ui-router and it's giving me grief, since it redirects me to the home page.

is there any other way to circumvent this? I'm trying to use Yasgui on an angular application with ui-router and it's giving me grief, since it redirects me to the home page.

I fixed it by:
// Save current hash
const hash = location.hash
location.hash = ''

// Init the yasgui and let it do hash things..
const element = document.createElement('div')
document.appendChild(element)
const yasgui = new Yasgui(element)

// Restore hash
location.hash = hash

That worked @danielbeeke . Thanks a lot again.

Nearly there. One thing that's bothering me now is that it appears to keep using #id123 for the tabs.
After you render the UI, take a look at the links for when you click on the tabs, and you should see it.

I believe that because of that, depending on your scroll bar location in the page, when you click on the tab the browser will load the new tab but also move you back to the top. I think somewhere it interprets that as a link (at least on Firefox) and wants to go to the top. But somewhere in YASGUI is must be intercepting that event and handling it correctly (since the tab works).


Added host_address command line argument

Hi, first of all thank you so much for the very useful project,
second, having the ability to expose the port to the (internal) network is very useful when the client is either:

An older machine not supporting o2popper
Using multiple accounts and can't run multiple instances of o2popper

the ability to set the host_address would be useful in both cases.
Thanks!

Thank you for your pull request.
I don't have any documentation on using it on the command line (o2pop.py).
You are amazing!
Exposing a network port risks being accessible to another person.
Careful attention is required.

Given that I was able to get this to work on Windows 7 using api-ms-win-core-path-blender and given that multiple accounts worked for me, this pull request no longer seem necessary.
Thanks!


Revert prefixing of mvn dependencies

Pull request #235 introduces prefix to each generated target for Maven dependencies. We did this in order to avoid clashes with rules_closure that we're using in startup-os-example. Investigate whether we could revert it while still maintaining both repos working.

 Set create_timestamp to local machine time when creating a new Diff. New proto field should be added for that.


How to disable @ / legacy ParseWithFileExpansion?

The default with v2 seems to be to handle @foo as "read from file foo".
This is somewhat problematic for parsing something like git revisions (@ is alias for HEAD, @^ for HEAD^ etc), because you get an error like this:
error: expected argument for flag '-r', try --help

Is there a way to disable @ handling either 1) complete or 2) for a flag?

Unfortunately not. Give v3-unstable a whirl, despite its "unstable" tag it is pretty solid. I have only not released it because some features are not yet complete.


interface{} & unsafe.Pointer: the value of original variable changed after assigning to interface{}.data

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

$ go version
go version go1.15.4 darwin/amd64

Does this issue reproduce with the latest release?
Yes, the output of the codes below on my machine is the same as golang playground (1.15.5)
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOINSECURE=""
GOOS="darwin"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/darwin_amd64"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/lp/dkglnlh92pn1x64wv1mr06_40000gp/T/go-build123819166=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?

First I had var i int, and assigned it to an empty interface var e interface{} = i.
Then I tried to modify the value which e.data point to. Unexpectedly, i was changed too. i is a variable, but not pointer, so I think it's value should NOT be changed.
Just run the code below, see the output.
package main

import (
	"fmt"
	"unsafe"
)

func main() {
	issue(101, 233) // both < 256
	issue(253, 886) // oldVal < 256
	issue(987, 254) // newVal < 256
	issue(998, 258) // both >= 256

	// Try this four calls, the output will be more strange.
	// issue(100, 255) // both < 256
	// issue(255, 999) // oldVal < 256
	// issue(999, 255) // newVal < 256
	// issue(999, 256) // both >= 256
}

// type eface struct {
// 	  _type *_type
// 	  data  unsafe.Pointer
// }
// data is *int (unsafe.Pointer(&i))
func issue(oldVal, newVal int) {
	fmt.Printf("\n==== running issue(%d, %d) ====\n", oldVal, newVal)

	var (
		i             = oldVal // int
		e interface{} = i
	)
	pdata := unsafe.Pointer(uintptr(unsafe.Pointer(&e)) + unsafe.Sizeof(&i))
	data := unsafe.Pointer(*(**int)(pdata))

	fmt.Printf("      i,   &i = %d, %p\n", i, &i)
	fmt.Printf("  *data, data = %d, %p\n", *((*int)(data)), data)

	// when 0 <= oldVal < 256, i will be changed, WHY???
	*((*int)(data)) = newVal
	fmt.Printf("\n  exec *((*int)(data)) = %d\n\n", newVal)

	fmt.Printf("      i,   &i = %d, %p\n", i, &i)
	fmt.Printf("  *data, data = %d, %p\n", *((*int)(data)), data)
}

Maybe it's a feature/bug about small integer cache...?

You are not allowed to write to the location pointed to by the data field of an interface. Interfaces are assumed to be immutable.
(Just like you can't write to the backing store of a string, or the type pointer of an interface, or lots of other things.)

Interfaces are assumed to be immutable.
Got it, thanks~

You are not allowed to write to the location pointed to by the data field of an interface. Interfaces are assumed to be immutable.
(Just like you can't write to the backing store of a string, or the type pointer of an interface, or lots of other things.)

Here is the reason of WHY NUMBER LESS THAN 256 CAUSE CHANGE? https://golang.org/doc/go1.15#runtime

Then I studied the source code about interface, seen staticuint64s.
I know I actually changed the value in staticuint64s.
Maybe fmt.Printf used it and so print another value, but not i.

So it's all my mistake. sorry 😅
Be ⚠CAREFUL⚠ playing with unsafe, stop C behavior.


ExternalName services not working

What version of Traefik are you using (traefik version)?

Running on Kubernetes 1.5.3.
traefik.yml
---
apiVersion: extensions/v1beta1
kind: DaemonSet
metadata:
  name: traefik
  labels:
    app: traefik
spec:
  template:
    metadata:
      name: traefik
      labels:
        app: traefik
    spec:
      nodeSelector:
        kubernetes.io/hostname: cluster-master-1
      terminationGracePeriodSeconds: 60
      containers:
      - image: traefik:morbier
        name: traefik
        imagePullPolicy: Always
        ports:
        - containerPort: 80
        - containerPort: 443
        - containerPort: 8080
        args:
        - --debug
        - --web
        - --configfile=/config/traefik.toml
        volumeMounts:
          - name: config
            mountPath: /config
          - name: acme
            mountPath: /acme
      volumes:
        - name: acme
          nfs:
            server: <IP_ADDRESS>
            path: /storage/system/traefik-acme
        - name: config
          configMap:
            name: traefik
---
apiVersion: v1
kind: Service
metadata:
  name: traefik
  labels:
    app: traefik
spec:
  externalIPs:
  - <IP_ADDRESS>
  ports:
    - name: http
      port: 80
    - name: status
      port: 8080
  selector:
    app: traefik
---
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: traefik
  annotations:
    kubernetes.io/ingress.class: "traefik"
  labels:
    app: traefik
spec:
  rules:
  - host: proxy.domain.tld
    http:
      paths:
      - backend:
          serviceName: traefik
          servicePort: 8080

traefik.toml
defaultEntryPoints = ["http"]

[entryPoints]
[entryPoints.http]
address = ":80"

[kubernetes]
namespaces = ["default"]

What did you do?
Created the following service and ingress:
---
apiVersion: v1
kind: Service
metadata:
  name: volumes
spec:
  ports:
  - name: http
    port: 8080
  type: ExternalName
  externalName: <IP_ADDRESS>
---
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: volumes
  annotations:
    kubernetes.io/ingress.class: "traefik"
  labels:
    name: volumes
spec:
  rules:
  - host: api.domain.tld
    http:
      paths:
      - path: /volumes
        backend:
          serviceName: volumes
          servicePort: http

What did you expect to see?
My service reachable under api.domain.tld/volumes.
What did you see instead?
The following error message:
time="2017-03-13T06:39:56Z" level=error msg="Error retrieving endpoints default/volumes: <nil>"
The example given in kubernetes.md also does not work for me and fails with the same error.

@simt2 Support for ExternalName was added in #1149 by @Regner and (AFAICS) won't be part of the next release yet. (The feature was merged after the v1.2 code freeze.)
Unfortunately, the published docs do not match the latest stable release; I have created #1279 to track improvement in this regard.
If you have a chance to build and try out master, we'd love to see if it works for you.

I'm not using stable but 1.2.0-rc2. The confusing thing is that the feature is listed under "Implemented enhancements" in CHANGELOG.md.

The docs also don't match the latest release candidate. :( It's the master state, which is why you see the change announced in the change log.

Closing for now. @simt2, if you get a chance to try out the feature with 1.3.0 and find it to be buggy / erroneous, feel free to post again and we'll reopen the issue.

externalName is showing up after upgrading to 1.3.1, however the port mapping is not working properly.
The problem might be coming from Kubernetes it self.
- apiVersion: extensions/v1beta1
  kind: Ingress
  metadata:
    annotations:
      kubernetes.io/ingress.class: traefik
    name: external-name-svc-example
  spec:
    rules:
    - host: example.com
      http:
        paths:
        - backend:
            serviceName: external-name-service-example
            servicePort: 3000

The backend url that gets created is still port 80

@caseeker just tested locally, it works for me. You need to make sure that your Service object contains the proper configuration for external names and the port specs. (The latter is necessary in order to determine if the port is 443, which causes Traefik to construct the server URL with https:// instead of http://.)
If you're still having problems, please join the Slack channel or open a question on Stackoverflow with the traefik tag. If you have legitimate reason to believe there's a bug, feel free to file a new issue.

I discovered the status quo while formulating a response on a different issue.
@dtomcej have been discussing options. I went ahead a filed a feature request for a direction that looked legitimate to me. Happy to discuss.


Restored the iOS sample in the solution

Previously, the solution contained the Examples.Mobile folder but there were no projects there.

I see that the build fails with the error
Unhandled exception: Microsoft.Build.Exceptions.InvalidProjectFileException: The imported project "/home/runner/.dotnet/sdk/7.0.304/Sdks/Microsoft.NET.Sdk/16.0.1478/targets/Xamarin.Shared.Sdk.MultiTarget.targets" was not found. Confirm that the expression in the Import declaration ";../16.0.1478/targets/Xamarin.Shared.Sdk.MultiTarget.targets" is correct, and that the file exists on disk.  /home/runner/.dotnet/sdk/7.0.304/Sdks/Microsoft.NET.Sdk/targets/Microsoft.NET.Sdk.targets

Is that a reason why the project is excluded from the solution?

does it need to install an ios workload onto the build agent or soemthing like that?

After a lot of tries I got it working in CI.


Proposal: Add new epm install option

Option name: --eta-patches-directory
If a patches directory is given, then it should use that
directory instead of hitting github eta-hackage repository.
Usecase: For testing incoming PR for patched packages. (See:
https://travis-ci.org/typelead/eta-hackage/builds/170578328 for
more details)
If there is no opposition, I can volunteer to implement this.

I thought this would be required after merging in the PR this morning. Go ahead and implement it. It might be a bit tricky to propagate the option across though. Feel free to discuss any hurdles here.

Implemented in #3


getTimerCount will not include cancelled immediates

Summary
In our projects we check getTimerCount() to know that all our timers/immediates are cleaned between tests.
I noticed that the number is getting larger after each test.
It seems that getTimerCount() counts cancelled immediates, this PR fixes this.
Test plan
added a test at jestFakeTimers.test.ts

Should cancelled immediates get removed so this._immediates is correct without the filter?

Looking through the usages, I didn't see a reason why there kept around yeah.
@eranshabi wanna try that for a cleaner solution? If all the tests and the new one stay green I think we can be pretty confident it works.

The CI test that fails is not using fake timers, so not sure why it's red. Will investigate...

CI is failing, though 😢


Text input with slider

Would be nice if the slider allowed text input. Thinking of the example in Gridded Datasets, would be useful to be able to enter a specific frame in the text box.

I believe this is a duplicate of https://github.com/ioam/holoviews/issues/673.

Ah ok. Thanks for the info. Sorry to dup. Didn't see that one when searching the issue tracker. Will following with that discussion.

No worries, it's buried rather deep. This has stalled for so long, because we have long decided that our widgets should be rewritten properly from scratch, but it's never been much of a priority. It is however one of the blockers for a 2.0 release so it is definitely on the roadmap.

Interesting. Is there an issue describing the sort of changes proposed for widgets somewhere?

Here's a very old first draft of a design document: https://github.com/ioam/holoviews/wiki/_Dev-Plan:-Widget-refactor
@jlstevens and I have since discussed this on at least five separate occasions but haven't made notes. @jlstevens Do you think you'll have time at some point to make an updated (and much more detailed) design proposal based on our discussions?

Do you think you'll have time at some point to make an updated (and much more detailed) design proposal based on our discussions?

Yes although that isn't the same as saying we have time to implement those plans! :-S


detect multi gaze & up/down

Hello,
Many thanks for sharing this project!
Is it possible to use this code to detect gaze of multi faces in the same screen? what do we need to adjust in your code?
Also, when looking up or down it detects looking left and blinking, respectively. Anyway to adjust that?
Thanks ,

have you solve the problem ? I'm in the same situation


Support custom EvmConfig for ethereumpayload builder

Describe the feature
as https://github.com/paradigmxyz/reth/issues/9962 surfaced, the default eth payloadbuilder always uses the default evm config:
https://github.com/paradigmxyz/reth/blob/f8e6e2e3d4bb0f97d588c634185d22acb41a56a9/crates/ethereum/node/src/node.rs#L199-L199
we already have this for OP but forgot to do the same for ethereum:
https://github.com/paradigmxyz/reth/blob/f8e6e2e3d4bb0f97d588c634185d22acb41a56a9/crates/optimism/node/src/node.rs#L214-L214
https://github.com/paradigmxyz/reth/blob/f8e6e2e3d4bb0f97d588c634185d22acb41a56a9/crates/optimism/node/src/node.rs#L246-L247
TODO

mirror OptimismPayloadBuilder for ethereumpayloadbuilder and configure properly in the custom-evm example, but perhaps the ethereumpayloadbuilder should instead get an instance of ConfigureEvm

fyi @igor-ritual
Additional context
No response

I applied the builder change from the example here https://github.com/paradigmxyz/reth/pull/10117 but I am still experiencing the bad block issue. Also, this other example needs to be updated as well: https://github.com/paradigmxyz/reth/blob/8d07bdb81a6f8616afcddd9b821312f52241c81b/examples/stateful-precompile/src/main.rs#L248


Improve documentation for projected service account token volume(s)

This is a Feature Request

What would you like to be changed
Improve https://kubernetes.io/docs/reference/access-authn-authz/service-accounts-admin/

Support for authorization and user accounts is planned but incomplete. Sometimes incomplete features are referred to in order to better describe service accounts.

is a statement about the future. We prefer to avoid these in Kubernetes documentation - we leave that to blog articles, KEPs, and media.

Remove mention of the RootCAConfigMap feature gate for v1.22 and later docs (it's a graduated feature).
Use a glossary shortcode to help explain the meaning of ConfigMap
Document the format of the ConfigMap. For example, state which key name(s) are used and the format of the value. I think the value is a string conforming to RFC7468 section 5.

If the string value can represent multiple certificates, what order are these in? (Should a party relying on this ConfigMap expect certificates in a particular order, or should it parse the distinguishedName attributes and work out a sensible ordering / chaining?)

Are there any information security implications? For example, does full write access to a namespace allow you to replace the trust root for Pods in that namespace?

Overall, the page should focus less on the specific in-tree implementation and more on the behavior that a conforming implementation offers. For example, controller names are specific to the in-tree implementation.
Also:

write imagePullSecrets in lower camel case (ie, not ImagePullSecrets) when the context is the Kubernetes API (or its YAML representation).

Why is this needed
Some of the existing wording is not idiomatic English; for example

When the BoundServiceAccountTokenVolume feature gate is enabled, the service account admission controller will add a projected service account token volume instead of a secret volume.

We'd also prefer to follow the style guide best practices.
Comments

/sig auth
/language en

/triage accepted

/remove-lifecycle rotten


Move agora.common.API to agora.node.API

API was out of place in common, as it depends on a lot of types.
Since it basically defines the communication interface for a node,
it is better located in agora.node itself.

💚


why are term.js & pty.js "required" but not dependencies?

I see this comment stating that it would be bad to add term.js & pty.js to Blessed as dependencies.
Can you explain this because I don't understand why the code has requires for them but they are not dependencies.
For context I am encountering Blessed for the first time after having discovered blessed-react.  I realize that the project is unrelated and might be the cause of other issues but I am curious about understanding the initial issue first.
I added them to my own project as dependencies (configuring Webpack to exclude pty.js due to other issues) in order to avoid the webpack failures but am paranoid about what other issues I might be getting myself into.
FYI Webpack throws this error:
ERROR in ./~/blessed/lib/widgets/terminal.js
Module not found: Error: Cannot resolve module 'term.js' in /home/dmison/Dev/BlessedStuff/Demo/node_modules/blessed/lib/widgets
 @ ./~/blessed/lib/widgets/terminal.js 93:14-32

ERROR in ./~/blessed/lib/widgets/terminal.js
Module not found: Error: Cannot resolve module 'pty.js' in /home/dmison/Dev/BlessedStuff/Demo/node_modules/blessed/lib/widgets
 @ ./~/blessed/lib/widgets/terminal.js 218:13-30

@dmison as far as I can tell, term.js and pty.js are only needed for the ansi-drawing widgets and the terminal widgets.

I think maybe a better option would be to move terminal widget to an independent module...

The errors described in this issue is currently blocking blessed-dependent libraries from compiling with Webpack. We have two options on how to deal with this two dependencies:

Declare term.js and pty.js as peer dependencies and let blessed dependents include this packages as their dependencies if they need them.
Follow @piranna idea. Move terminal widget into a separate module.

If we opt by (1), I would be happy to make a PR fixing this issue, but I believe it's up to @chjj to decide the best approach to take :)

I am seeing the same errors too when I use webpack. What's the workaround?

As I couldn't get pty.js to work correctly in this scenario, I just commented out the lines in terminal.js that deals with pty. It worked. I also installed term.js. No problems so far.

I set this.term = {}; and this.pty = {}; in blessed/…/widget.js. Works for now.
I used the wonderful patch-package module to make these changes part of my repo.

These missing files can be ignored by webpack IgnorePlugin to bypass their resolving
const webpackModule = require('webpack');

config.plugins.push(
  new webpackModule.IgnorePlugin(/pty.js/, /blessed\/lib\/widgets$/)
);

config.plugins.push(
  new webpackModule.IgnorePlugin(/term.js/, /blessed\/lib\/widgets$/)
);

I found this solution that works for building backend node apps with Webpack. Seems to solve any issues like this where Webpack is not sure what to do with .bin files
let nodeModules = {}; fs.readdirSync('node_modules')     .filter(function (x) {         return ['.bin'].indexOf(x) === -1;     })     .forEach(function (mod) {         nodeModules[mod] = 'commonjs ' + mod;     });
Then in your webpack.config, add this:
   externals: nodeModules,


Address issue Check Datenvisualisierung

Offene Umsetzungen des Issues «Check Datenvisualisierung»
https://github.com/swiss-art-research-net/itten-zb/issues/45

Have largely been implemented. Suggestion to revisit issues after update

see also
https://github.com/swiss-art-research-net/itten-zb/issues/65
https://github.com/swiss-art-research-net/itten-zb/issues/67
https://github.com/swiss-art-research-net/itten-zb/issues/68

Not yet implemented (?): https://github.com/swiss-art-research-net/itten-zb/issues/45#issuecomment-1590847692


userCodeAppPanel:1669                           GET https://storage.googleapis.com/storage/v1/b/pfg-ai-vigenair/o/24_10_UP_Monatsvideo_30Sek_16zu9.mp4--n--1729165400549--ZG9taW5pcXVlLmx1ZWJiZW5AcG9wa2VuLXNlcnZpY2VzLmRl%2Finput.vtt?alt=media 404 (Not Found)

directly after the upload, an error occours that the uploaded video can't be accessed/get from cloud storage. You can even load the prior uploaded video in "video selection" and still get the same error.

I got further information. The problem is that the function tries to get a .vtt file that is not created or uploaded to the storage. The same goes for the different analysis steps and there file types.

Please read the README. The UI waits until the files are processed by the Cloud Function and available in Cloud Storage, so the 404s here are expected.

I know that. The cloud functions are never opened by your script and I have been timed out several times.

We enhanced the error logging with https://github.com/google-marketing-solutions/vigenair/commit/e9524c0634bd9af50696d626b51584790d543624 so you shouldn't see any other errors in the console except the 404s - which are again expected as long as your video hasn't processed yet and is not yet available on GCS.

@mohabfekry  Same error here.
But how do I know when this process is complete...or how do I check if it's running at all?
"video hasn't processed yet and is not yet available on GCS"


Optional AWS Secrets Manager Endpoint

Story
-As a cluster admin, I want the AWS Secrets Manager endpoint to be optional in order to:

not create additional subnetes for this enpoint (see granular network layout);
use the existing endpoint provider by the customer.

Task
Make the creation of the AWS Secrets Manager VPC endpoint created by the aws-vpc-network-operator configurable per cluster, similar to how the resolver rules are filtered by the owner AWS account.
TODOs:

[ ] Expose configuration option in values.yaml;
[ ] Add annotation to AWSCluster to make the creation of the VPC endpoint configurable;

The VPC endpoint will always be created if the annotation is missing.

https://github.com/giantswarm/cluster-aws/pull/214
https://github.com/giantswarm/aws-vpc-operator/pull/33


100% CPU is used and 90% threads In timed_waiting are blocked on thrMultiProducerSequencer.next

Recently, the strange problem occasionally occur in our prod environment of a service:

all the 4 core CPUs are 100% busy
the number of threads in timed_waiting rise sharply, and the stack is shown as follows:

"********" #430 prio=5 os_prio=0 tid=0x00007f5b8c89e800 nid=0x313a runnable [0x00007f5b2fc38000]    java.lang.Thread.State: TIMED_WAITING (parking)         at sun.misc.Unsafe.park(Native Method)         at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:338)         at com.lmax.disruptor.MultiProducerSequencer.next(MultiProducerSequencer.java:136)         at com.lmax.disruptor.MultiProducerSequencer.next(MultiProducerSequencer.java:105)         at com.lmax.disruptor.RingBuffer.publishEvent(RingBuffer.java:502)         at org.apache.logging.log4j.core.async.AsyncLoggerConfigHelper.callAppendersFromAnotherThread(AsyncLoggerConfigH elper.java:342)         at org.apache.logging.log4j.core.async.AsyncLoggerConfig.callAppenders(AsyncLoggerConfig.java:114)         at org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:409)         at org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:367)         at org.apache.logging.log4j.core.Logger.logMessage(Logger.java:112)         at org.apache.logging.log4j.spi.AbstractLogger.logMessage(AbstractLogger.java:738)         at org.apache.logging.log4j.spi.AbstractLogger.logIfEnabled(AbstractLogger.java:708)         at org.apache.logging.slf4j.Log4jLogger.info(Log4jLogger.java:193)         ...
3) no BatchEventProcessor threads are running
our prod env:
Linux 2.6.32-431.20.3.el6.mt20161028.x86_64
disruptor 3.3.0
log4j 2.3
is there any hints provided? thx

This looks like the Log4J ring buffer is full.  Is it possible that the thread writing to the database has exited or running slowly?

@mikeb01
No thread writing to db, while one appender writing to kafka.
It looks like this problem, and has nothing to do with the disruptor.
I try to upgrade log4j2 or implement exception handler.
I close this issue firstly.
thx mikeb01


Remove lifetime and supertrait on ReadOnlyFetch

afaict this isnt a thing on main and is basically just added ptrification complexity with no use case yet


Optimize RDWS

https://github.com/QuCoNot/QuCoNot/blob/9ce67a6f1e4f08da27699bed5d46501c03113f70/quconot/verifications/functions_testing.py#L368 I think there should also be an inverse
In S-D-WS you don't have to check if W is unitary
And anyway this kind of check is not correct. If you want to check if A is unitary, then you want to verify A @ A^\dagger
For R-D-WS you also don't have to check if W is unitary

fix in #38


Add support for catppuccin-whiskers

Catppuccin has a tool called whiskers which is used to generate the color scheme files for different programs. It accepts color overrides in the form of JSON, and I made a JSON file that works with it. Would you like a PR with that file and documentation on how to use it?

One quirk is that for some reason I had to change any occurrence of ff in a channel for fe, whiskers panics for some reason if any color channel in the color overrides is ff.
Also, I see you just added a commit after being active for a while, just as I was working on this. Quite the coincidence!


[ADAP-1055] [Regression] schema is no longer available in unrendered_config when doing a run with partial parsing

Is this a regression in a recent version of dbt-bigquery?

[X] I believe this is a regression in dbt-bigquery functionality
[X] I have searched the existing issues, and I could not find an existing issue for this regression

Current Behavior
for a model that has it's schema defined via dbt_project.yml:

after a dbt clean run a model (full parse)
check the model in the manifest for schema in unrendered_config it is there
change the model
run the same model (partial parse)
check the model in the manifest for schema in unrendered_config it is not there

because of the above behavior it causes a failure. we have our own version of the generate_alias_name macro to write all objects to a single schema when running outside of production with the production schema prepended to the object name. inside we force an error if a schema isn't defined by using an invalid character in the placeholder schema name.
{% macro generate_alias_name(custom_alias_name=none, node=none) -%}
    {%- set node_type = node.resource_type | trim %}
    {%- if custom_alias_name is none -%}
        {%- set table_name = node.name -%}
    {%- else -%}
        {%- set table_name = custom_alias_name | trim -%}
    {%- endif -%}
    {%- if target.name == 'prod' or node_type == 'snapshot' -%}
        {{ table_name }}
    {%- else -%}
        {#- Get the custom schema name -#}
        {%- set schema_prefix = node.unrendered_config.schema | trim %}
        {#- Highlight if schema hasn't been assigned right -#}
        {%- if not schema_prefix -%}
            {%- set schema_prefix = '[assigned_schema_required]' %}
        {%- endif -%}
        {{  schema_prefix ~ "__" ~ table_name }}
    {%- endif -%}
{%- endmacro %}

if we define the schema in a model config then it also works but that's obviously less than ideal and not a real fix
we're using bigquery and are on dbt cloud but this error only occurs when running things locally because you wouldn't do the same steps anywhere else.
what leads me to believe it is a regression with partial parsing is the fact that after running the steps to reproduce and then a dbt clean the model works again.
Expected/Previous Behavior

after a dbt clean run a model (full parse)
check the model in the manifest for schema in unrendered_config it is there
change the model
run the same model (partial parse)
check the model in the manifest for schema in unrendered_config it is still there

Verified these steps work fine on dbt-bigquery==1.6.0 and dbt-bigquery==1.5.9
Steps To Reproduce

create the macro with our code (see below)
create a new folder + config block in dbt_project.yml to specify the schema
create a model in the new folder select 1 as col_a
dbt run -s new_model should work
edit the model select 1 as col_a, 2 as col_b
dbt run -s new_model should now fail with the bad schema because schema is no longer in unrendered_config

{% macro generate_alias_name(custom_alias_name=none, node=none) -%}
    {%- set node_type = node.resource_type | trim %}
    {%- if custom_alias_name is none -%}
        {%- set table_name = node.name -%}
    {%- else -%}
        {%- set table_name = custom_alias_name | trim -%}
    {%- endif -%}
    {%- if target.name == 'prod' or node_type == 'snapshot' -%}
        {{ table_name }}
    {%- else -%}
        {#- Get the custom schema name -#}
        {%- set schema_prefix = node.unrendered_config.schema | trim %}
        {#- Highlight if schema hasn't been assigned right -#}
        {%- if not schema_prefix -%}
            {%- set schema_prefix = '[assigned_schema_required]' %}
        {%- endif -%}
        {{  schema_prefix ~ "__" ~ table_name }}
    {%- endif -%}
{%- endmacro %}

Relevant log output
No response
Environment
- OS: macOS Sonoma 14.1.1
- Python: 3.11.3 (plus others)
- dbt-core (working version): 1.6.0
- dbt-bigquery (working version): 1.6.0
- dbt-core (regression version): 1.7.1
- dbt-bigquery (regression version): 1.7.2

Additional Context
slack thread with perhaps an easier to follow sequence of information: https://getdbt.slack.com/archives/CBSQTAPLG/p1701365532730099

per @Spince , this problem persists cc: @dbeatty10

I am working on new steps to reproduce. The same error occurs but not with the same steps.

@Spince were you able to come up with new steps to reproduce?

@dbeatty10 I have not been able to reliably reproduce since dbt-core 1.7.3. we can probably close this until i have clear steps to reproduce!


added homelander

Hey added my favorite The Homelander to the list, please accept it as an entry for Hacktoberfest 2023

@RohanHBTU can you review and accept the pull request

@RohanHBTU still waiting for my pull request to be accepted


Reset: consider adding * { flex-shrink: 0; }

See https://twitter.com/paul_irish/status/524959136782364672

No: https://codepen.io/benface/pen/WYyGxZ
Also tried it on MEL, caused more problems than it fixed.


[two_dimensional_scrollables] Support to draw a connected line between the cells in the TableView

Use case
[two_dimensional_scrollables] Support to draw a connected line between the cells in the TableView

Proposal
Support to draw connected line between the cells in TableView

I solved this problem.


Show php version on folders with php files

To be modified after custom-ordering. #78
Related #74

[x] vanilla php
[x] phpbrew
[x] php-version
[x] phpenv

Thought it would be better to use those helper functions after it's merged.

phpenv is broken and not maintained anymore. Other popular options seems to work.

phpenv is broken

is there any confirmation?

Last commit in phpenv https://github.com/phpenv/phpenv/commit/f50bb0b789c3844dbc30ca4eefd76f93023db417 is on 27 Nov 2013. There are several discussions about at phpenv/phpenv/issues/43 phpenv/phpenv/issues/57 phpenv/phpenv/issues/43 phpenv/phpenv/issues/19 regarding this. A fork of it https://github.com/madumlao/phpenv was also maintained till last year.
Hopefully, this method will also work on it. Because php version managers normally don't provide additional commands to check versions.

#78 is merged. v2.0.0 is out. Please, update this PR in corresponding to new API.

@sfarzy please, resolve conflict. I think it's ready to go.

This PR breaks Spaceship. Fixing this...

Done!


[FEATURE] Filter the OSD integration tests with component OpenSearch-Dashboards

Is your feature request related to a problem?
Coming from the issue https://github.com/opensearch-project/opensearch-build/issues/4943, the integration tests for OpenSearch-Dashboards is now saved at group level, meaning the component name is not direct OpenSearch-Dashboards but as OpenSearch-Dashboards-ci-group-6 etc. With this in the test manifest when we index the test results to the metrics cluster the component name is also as OpenSearch-Dashboards-ci-group-6 and not direct OpenSearch-Dashboards.
What solution would you like?
Have a mechanism to filter with component as OpenSearch-Dashboards  still honoring filter per group level. This was when filtered with OpenSearch-Dashboards  should directly give all the CI group results.
What alternatives have you considered?
A clear and concise description of any alternative solutions or features you've considered.
Do you have any additional context?
Add any other context or screenshots about the feature request here.

[Triage]
We need have a value just for OpenSearch-Dashboards to be able to filter as component.keyword as OpenSearch-Dashboards.

Since ci-group's are not implemented generically across all components, but only for OpenSearch Dashboards (as seen in this PR and this PR), the solution is to include the component_repo keyword in the documents. This will allow filtering by repository, such as OpenSearch-Dashboards, to retrieve all relevant documents containing this keyword and display the ci-group's results. Adding a ci_group field is not the right solution, as ci-group's  are only applicable to OpenSearch Dashboards and not other repositories. With the component_repo filter, we can make this functionality generic, applying it to any repository, regardless of whether it has CI groups or not.
Thanks
@peterzhuamazon @getsaurabh02


fix: Update api-keys.md

Wrong link to each.

Thank you for the fix @kis87988. Can you sign the CLA?

I signed it! email<EMAIL_ADDRESS>

Thank you @kis87988 ! :smile_cat:


🚀 Feature: Add a copilot assistant

🔖 Feature description
Add a personal assistant.
🎤 Why is this feature needed ?
For better user experience
✌ How do you aim to achieve this?
Using copilot
🔄 Additional Information
No response
👀 Have you spent some time to check if this feature request has been raised before?

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

Are you willing to submit PR?
Yes I am willing to submit a PR!

Yes do this


Refactor and Enable batching for both simple and openai

Completed:

An enhanced version to replace #149, support both simple and openai protocols.
Refactor PredictorDeployment: __call__ for simple and openai_call for openai
Support Continuous Batching (use vllm), Static Batching (single request multiple prompts) and Dynamic Batching (ray serve batching)

TODO:

Support static batching output for openai
Docs

Add tests
Add max_batch_size parameter
Add agent tools from main branch

Pls review. thanks!


Best-guess drop of commits

Unlike in #3, not all commits drop cleanly

if you had a branch get squashed when pulled into upstream.  It'd be nice if we could guess based on the summary.
Possible rebase conflict resolution?

If we identify a best-guess at the start of a branch, we should then proceed to delete the whole branch, assuming they were all squashed.
This should be configurable.

Drop commits which are now empty after the rebase. This mostly handles the case of squashed commits.

I recently handled this with tree-id, see https://github.com/epage/git-stack/pull/80/commits/a472ed64f5d24d1788115439b402449f55a81bb8

Drop commits with the same patch ID. This handles the case of commits being applied out of order upstream.

This was the next idea I was going to play with but glad you brought it up because I kept not finding this idea, so its good we are spreading it around.

I'm assuming the optimization at https://github.com/arxanas/git-branchless/commit/16b0c69e060934392b377f33f2f0c1338fc0d699  mentioned at https://github.com/libgit2/libgit2/issues/6036 is helpful for generating the patch ids.

Furthermore, we're careful only to calculate patch IDs for commits which have touched exactly the same paths, as diff calculation is still slower than calculating the paths changed in a given commit. We also do it in parallel, which is important for large repositories. See https://github.com/arxanas/git-branchless/blob/331b7cf2a37d00a3d54ba5df00f3d702aa7b3948/src/core/rewrite/plan.rs#L700-L710


Issue when running Alluxio-Fuse

Hi Guys,
We've encountered a problem when running alluxio-fuse. Here is the message we get - "/entrypoint.sh: line 99: integration/docker/bin/alluxio-job-worker.sh: No such file or directory"
A bit more context we are trying to run it on AWS ECS, Fargate launch type.
Any ideas how to fix it?

@Yar0myr which version of Alluxio are you running? alluxio-job-worker.sh is only introduced in master branch. We suggest to go with released version from here http://www.alluxio.org/download

@Yar0myr do you still have this issue or have your problem solved? Mind sharing your solution in this case?


automotive_autonomy_msgs: 3.0.1-1 in 'kinetic/distribution.yaml' [bloom]

Release generated by bloom but PR generated manually. See ros-infrastructure/bloom#557 for details.
Increasing version of package(s) in repository automotive_autonomy_msgs to 3.0.1-1:

upstream repository: https://github.com/astuff/automotive_autonomy_msgs.git
release repository: https://github.com/astuff/automotive_autonomy_msgs-release.git
distro file: kinetic/distribution.yaml
bloom version: 0.8.0
previous version for package: 2.0.3-0

automotive_autonomy_msgs
* Merge pull request #15 <https://github.com/astuff/automotive_autonomy_msgs/issues/15> from astuff/maint/ros1_ros2_hybrid
  ROS1/ROS2 Hybrid Packages
* Fixing XML linting errors.
* Hybridizing all packages.
* Contributors: Joshua Whitley

automotive_navigation_msgs
* Merge pull request #15 <https://github.com/astuff/automotive_autonomy_msgs/issues/15> from astuff/maint/ros1_ros2_hybrid
  ROS1/ROS2 Hybrid Packages
* Adding migration rules.
* Fixing XML linting errors.
* Making all messages ROS2-compliant.
* Hybridizing all packages.
* Contributors: Joshua Whitley

automotive_platform_msgs
* Merge pull request #15 <https://github.com/astuff/automotive_autonomy_msgs/issues/15> from astuff/maint/ros1_ros2_hybrid
  ROS1/ROS2 Hybrid Packages
* Fixing XML linting errors.
* Making all messages ROS2-compliant.
* Hybridizing all packages.
* Contributors: Joshua Whitley

Holding for Kinetic sync.


squeezelite: <IP_ADDRESS>3 -> <IP_ADDRESS>1

Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

@ofborg eval

I have built and reviewed the code, I'm unable to test it as I don't have a server running anymore.
@adamcstephens perhaps you'd consider adding yourself as a maintainer?

Yes, I can be a maintainer. Do you want to stay in the list @samdoshi, or should I remove you?

Yes, I can be a maintainer. Do you want to stay in the list @samdoshi, or should I remove you?

You should probably remove me as it's hard for me to test changes as I no longer use Squeezebox.


feat: adds the franklin experimentation engine

Add the Franklin experimentation engine from https://github.com/adobe/aem-experimentation.
Part of: MWPW-138479
Requires: https://github.com/adobecom/milo/pull/1494
Test Documents:
TBD
Test URLs:
TBD

Closing this for now until we resume the initiative


Suggestion: TextFieldWrapper.Value return RawValue

Most implementations of the IFieldWrapper.Value returns a typed value, for example BooleanFieldWrapper returns a proper bool, LinkFieldWrapper returns a Guid etc. However, the TextFieldWrapper executes the Render() method resulting in a html encoded string. This is sometimes bad since it doesn't reflect the actual value. Also, if it's accidentally used in a razor view, its output would be double html encoded.
I know this would be a very much breaking change to the existing behavior, but it may be worth considering TextFieldWrapper.Value to return the RawValue instead, making it more consistent with the other field types. The RichTextFieldWrapper.Value could then return a IHtmlString. By doing so, the Value property can be used for working with the actual values and the rendering won't be broken. Besides, normal rendering can use just output the FieldWrapper since it implements IHtmlString that performs a proper Render() call.
Thoughts on that?
// Mikael

Apologies for the (very) late response :), in short I agree! While this could be a breaking change I agree that the TextFieldWrapper isn't doing the same as the other fields with regards to the Value property.

As we are making some breaking changes in v4 of Fortis already - it makes sense to add this change to the list. @jasonbert I'm going to make the change and release the beta - we can always revert if there are any major issues.