ruby-mqtt does not work with mathn library.

see also... https://gist.github.com/yoggy/aa77faba0a0840ef0faf2182d23a665c

Hi,
Sorry, I don't quite understand this. Why does the mathn library change the behaviour of the / operator?
What is the different between / and .div?
It looks like mathn is part of the standard ruby build?
Would it be possible to write a test that verifies this behaviour?
nick.

Hi njh,
I am interested in this strange behavier.
Do you know "Rational" class?
Rational is defined when you require mathn.

http://docs.ruby-lang.org/en/2.1.0/Rational.html

Rational overrides Numeric#/ method.
If Rational is defined, Fixnum#/ method returns a Rational number instead of a Fixnum.
$ irb
irb(main):001:0> 1000 / 123
=> 8
irb(main):002:0> (1000 / 123).class
=> Fixnum
irb(main):003:0> require 'mathn'
=> true
irb(main):004:0> 1000 / 123
=> (1000/123)     #### Fixnum#/ returns Rational number!! ####
irb(main):005:0> (1000 / 123).class
=> Rational

Rational does not overide Numeric#div method.
If you expect [Fixnum / Fixnum => Fixnum], you should use Fixnum#div method.
$ irb
irb(main):001:0> require 'mathn'
=> true
irb(main):002:0> 1000.div(128)
=> 7
irb(main):003:0> 1000.div(128).class
=> Fixnum

In this case, if require 'mathn'...
Step 1
                    .
                    .
          #### body_length is assumed to 10. ####
                    .
                    .
194       # Build up the body length field bytes
195       begin
196         digit = (body_length % 128)
197         body_length = (body_length / 128)  #### (1) body_lenght is Rational number (10/128) [Fixnum / Fixnum => Rational]     ####
198         # ....
199         digit |= 0x80 if (body_length > 0)
200         header.push(digit)
201       end while (body_length > 0)

Step 2
194       # Build up the body length field bytes
195       begin
196         digit = (body_length % 128)
197         body_length = (body_length / 128)
198         # ....
199         digit |= 0x80 if (body_length > 0)
200         header.push(digit)
201       end while (body_length > 0)          #### (2) Infinite loop generated, because body_length is not Zero!!  ####

Step 3
194       # Build up the body length field bytes
195       begin
196         digit = (body_length % 128)        #### (3) digit changes to Rational [Rational % Fixnum => Rational] ####
197         body_length = (body_length / 128)
198         # ....
199         digit |= 0x80 if (body_length > 0)
200         header.push(digit)
201       end while (body_length > 0)

Step 4
195       begin
196         digit = (body_length % 128)
197         body_length = (body_length / 128)
198         # ....
199         digit |= 0x80 if (body_length > 0) #### (4) NoMethodError occured. it is not defined to Rational#/ method ####
200         header.push(digit)
201       end while (body_length > 0)

Thanks for investigating yoggy.
So the key difference is that div will always return an integer - which is what we want because the remainder is being handled separately. We only what the whole number of divisions.
 "Uses / to perform division, then converts the result to an integer."

It doesn't specifically say if the conversion uses floor(), ceil() or round() but I think it is fairly safe to assume floor.
Also still unsure how to write a test for this.


luci-app-mwan3: Interface device for ping -I <> not properly resolved for alias interfaces. GENERAL QUESTION - what is the right way to handle these in the future?

If you try to diagnose a v6 interface in mwan3 such as pinging the tracking or gateway IP, we get back ping: bad address '@wan.
This isn't an edge-case, this is the current default documented setup for dual-stack interfaces. If you have a dual-stack interface using the v4/v6 alias convention as per the default documentation:
config interface 'wan'
	option ifname 'eth0.10'
	option proto 'dhcp'
	option metric '120'

config interface 'wan6'
	option ifname '@wan'
	option proto 'dhcpv6'
	option reqaddress 'try'
	option metric '120'
	option reqprefix '60'

You get:
root@g2s:/usr/sbin# uci get network.wan6.ifname
@wan_cc
root@g2s:/usr/sbin# uci get network.wan.ifname
eth0.10

The problem is here:
https://github.com/openwrt/luci/blob/485e5c930ff0a98f1155b04080f6736270c58a10/applications/luci-app-mwan3/luasrc/controller/mwan3.lua#L141
but I don't know the proper fix to issue a pull request. Seems like either UCI should be fully resolving option ifnames that have @ in them, or we should be doing a second resolution step to check to see that we have a real interface instead of an alias.
@feckert

local nm = require "luci.model.network".init()
local network = nm:get_network(interface)
local device = network and network:ifname()

if device then
    ...
end

Tested the patch from @jow- it is great except we cannot delete the 'local uci =' line because we reference 'uci' later in the function. I haven't set up a clone of packages for pull requests yet to make the pull request, but I'll try to do so in the next 24hrs if someone else hasn't already submitted it.
Thank you very much to @jow- for the awesome explanation of "the right way" to do it.

Pull request #1929

Fixed.


When will the Hydra-ViT-B pretrained weight release?

Hello!
Thanks for your excellent work.
When will the Hydra-ViT-B pretrained weight release?

We might work on releasing ViT experiments, but currently don't have fixed plans


Version 1.4.2 : Need equivalent functionlity for Globalize.findClosestCulture().calendar.patterns

Hi,
We are working on upgrading our globalize library from version 0.x to latest version 1.4.2.
We need a equivalent functionality for below property in Version 1.4.2 Globalize.findClosestCulture().calendar.patterns
I know that in latest version findClosestCulture() is not supported any more.
Based on the culture, we are getting calendar patterns in 0.x globalize. Howeever, i couldn't able to get the patterns in latest version.
imagine culture is set to 'en'
Globalize.findClosestCulture().calendar.patterns
Output:
{ D: "dddd, MMMM dd, yyyy"
F: "dddd, MMMM dd, yyyy h:mm:ss tt"
M: "MMMM dd"
S: "yyyy'-'MM'-'dd'T'HH':'mm':'ss"
T: "h:mm:ss tt"
Y: "yyyy MMMM"
d: "M/d/yyyy"
f: "dddd, MMMM dd, yyyy h:mm tt"
t: "h:mm tt"
}
I have tried to read cldr data content and get the calendar patterns in 1.4.2.
This is how we are creating globalize object now. I have tried see any equivalent property which gives calendar patterns like in old way, but i didn't get it.
const enGregorian = JSON.parse(require("text!cldr-data/main/en/ca-gregorian.json")),
enCurrencies = JSON.parse(require("text!cldr-data/main/en/currencies.json")),
enDateFields = JSON.parse(require("text!cldr-data/main/en/dateFields.json")),
enNumbers = JSON.parse(require("text!cldr-data/main/en/numbers.json")),
enTimeZoneNames = JSON.parse(require("text!cldr-data/main/en/timeZoneNames.json")),
enUnits = JSON.parse(require("text!cldr-data/main/en/units.json")),
currencyData = JSON.parse(require("text!cldr-data/supplemental/currencyData.json")),
likelySubtags = JSON.parse(require("text!cldr-data/supplemental/likelySubtags.json")),
metaZones = JSON.parse(require("text!cldr-data/supplemental/metaZones.json")),
pluralsData = JSON.parse(require("text!cldr-data/supplemental/plurals.json")),
timeData = JSON.parse(require("text!cldr-data/supplemental/timeData.json")),
weekData = JSON.parse(require("text!cldr-data/supplemental/weekData.json"));
Globalize.load(likelySubtags,
currencyData,
enCurrencies,
enDateFields,
enGregorian,
enNumbers,
enTimeZoneNames,
enUnits,
metaZones,
pluralsData,
timeData,
weekData);
this.globalize = Globalize('en');
Could you please guide me to write a function which gets same Output as mentioned sample object in latest version? Please let me know if i am missing something.
Thanks in advance.

I read two requests above:

Find the best match given a requested locale and the available list of supported locales
Get raw pattern data

Is that correct? Can you confirm?

It's the second point for pattern data.
Is there any alternative for this Globalize.findClosestCulture().calendar.patterns?

Using globalize.cldr.get() (docs) to get the data you want (not recommended). It's recommended you use formatDate and simply get a formatted date using the library

Closing as not an issue

This is what i am gettting when i query Globalize.findClosestCulture().calendar.patterns in 0.x version.
{ D: "dddd, MMMM dd, yyyy"
F: "dddd, MMMM dd, yyyy h:mm:ss tt"
M: "MMMM dd"
S: "yyyy'-'MM'-'dd'T'HH':'mm':'ss"
T: "h:mm:ss tt"
Y: "yyyy MMMM"
d: "M/d/yyyy"
f: "dddd, MMMM dd, yyyy h:mm tt"
t: "h:mm tt"
}
Now in version 1.x, is there anyway i can get the same object as above?


Updated typo (?) on documentation for Attention layer

Isn't value_input should be used instead query_input in value_embeddings? It feels like a typo error?

Please open PR against master branch. We don't update release branches (r...) after the final release of the corresponding TF version (i.e., we won't update r2.1 after TF2.1 is released).
The only time release branches are updated is when we make a patch release to fix a security vulnerability. As that requires expediency, we only accept minimal changes even then.


Unused detection misses out: Assigning a variable is not using it.

var x;
x = require( 'x' );

x is not used, albeit 'unused' is set to true in jshint's json file. jshint does not catch it.
Assigning a variable without ever reading it is not using it.
I like to catch these things, since I want to clean my code base of node modules I historically requried but do not seem to require any more.
Please don't tell me to write it all as var x = require( 'x' ); yes it is catched then. But in many cases these requirements are inside conditionals, like same code used for node and for browser where in browser its a global but node a require assignment I put an if (SERVER) around it.
Suggested solution: For undef checking, if a variable is simply assigned but never used as right-hand-side, it is not to be considered to be "used".
Kind regards,

The conversation in the PR says that this won't be released until 3.0 because it would break existing usage. Is there a target release date for 3.0? If this is somewhat far off, is there a backwards compatible way this can be released for 2.x?
Some possibilities:
a. Introduce another value(s) for unused, e.g varsWithIgnoreInit, trueWithIgnoreInit, strictWithIgnoreInit
b. Introduce a list of modifiers for an option, e.g semicolon delimited: "unused:vars;ignoreInit", "unused:true"
c. Split unused into two options since it really is doing two things: unused-vars and unused-params. unused-vars and unused-params trumps whatever is set for unused (which would be deprecated and still maintain existing functionality). unused-vars would do what the PR does.
A,B seem bad as they are more complicated and add complexity. C, however, seems like a good option since it is backwards compatible, addresses the complexity of the option as brought up in #2358, and makes this functionality available sooner rather than later.

@jugglinmike thoughts on the above proposal?

+1


PTVS Documentation Updates

PTVS 2022 documentation updates

Status
Link
Problem
Change

✅
Create new Python Env
Screenshot and instructions lead   user to search for and create a Python Console App
Replace Console App suggestion with Python Application and replace screenshot   (this is no longer an option)

✅
Create new Python Env
"Python support in Visual   Studio includes several project templates, such as web applications in the   Bottle, Flask, and Django frameworks. For this tutorial, start with an empty   project."
User will only see this if they   installed the Python web support and development tools and features on   setup

✅
Create new Python Env
The Properties window shows more information for the item selected   in Solution Explorer,   including its exact location on disk (3).
The properties tile did not show   up automatically until I clicked on the file and then the wrench

✅
Create new Python Env
Selecting a file displays its   properties in the Properties window. (properties window doesn’t show upon click)
Click the wrench to view the   properties

✅
View Environments
The Packages tab in the Python Environments window lists all packages   that are currently installed in the environment.
I found it unclear as a new user that the packages tab was underneath the overview

Updated in https://github.com/MicrosoftDocs/visualstudio-docs-pr/pull/10529


NSFS | NC | Let the User Explicitly Set allow_bucket_creation

Environment info

NooBaa Version: master
Platform: NC

Actual behavior

Currently, the allow_bucket_creation value is inferred from the new_buckets_path: if the user passes a value to new_buckets_path then it is true, otherwise false.

Expected behavior

Allow the user to pass the value of allow_bucket_creation explicitly and update it (from true to false and vice versa).

Steps to reproduce

none

More information - Screenshots / Logs / Other output
Please take into account that it will be a flag is manage nsfs CLI and a property inside the file when using the from-file option.

Please add a unit test for updating a bucket (see this comment with manual description):

Create an account with new_buckets_path (allow_bucket_creation is true).
Created a bucket.
Update the account (in a way you choose) so allow_bucket_creation will be false.
Update the bucket already created (step 2) - for example --fs_backend GPFS instead of the default value => should pass.

The verification will be tracked by the BZ 2262992.

It was validated in mentioned BZ above.


[GDBStub] kconfig gdbstub runtime should be separate bool (IDFGH-10309)

See: https://github.com/espressif/esp-idf/issues/11568#issuecomment-1571565125
This is a runtime feature, not a panic feature.

@ESP-Marius

@ESP-Marius

@Lapshin can you help take a look?

@Lapshin bump

@chipweinberger , I still see open discussions for changes in this PR

oh I missed that. will update.

@Lapshin updated.

sha=ab757819aad60e0fb6a0e2d1b5c072cc71ab0520

@Lapshin any updates? would be great if you could ping some people to review this.

@Lapshin It looks like this did not get merged correctly https://github.com/espressif/esp-idf/commit/5f07ed87f6c3c8c4de97ef4f9afca83398c2f3cf
It should be a separate bool, not part choice ESP_SYSTEM_PANIC

@chipweinberger , it was separated into two commits, the second one will be synced with GitHub repo soon


SDK is missing Deployments.Delete

I don't think the client library includes a routine to delete deployments.
https://github.com/replicate/replicate-python/blob/b0bbc048d93b567b7817d1928a9ca717403afa10/replicate/deployment.py#L25
FYI @mattt

Thanks for pointing this out, @jlewi. I opened a PR implementing this in #331.

This is now available in 0.31.0


Is it proper way to configure gpt-4-1106-preview in mods --settings ?

Is it proper way to configure gpt-4-1106-preview?
$ mods --settings

# Default model (gpt-3.5-turbo, gpt-4, ggml-gpt4all-j...).
#default-model: gpt-4
default-model: gpt-4-1106-preview
(...)
# Default character limit on input to model.
#max-input-chars: 12250
max-input-chars: 398000
(...)
apis:
  openai:
    base-url: https://api.openai.com/v1
    api-key-env: OPENAI_API_KEY
    models:
(...)
      gpt-4-32k:
        aliases: ["32k"]
        max-input-chars: 98000
        fallback: gpt-4
      gpt-4-1106-preview:
        aliases: ["128k"]
        max-input-chars: 392000
        fallback: gpt-4-1106-preview
(...)

Also, maybe add it as option to default config now? After all it's one of available models?
(Or maybe make a flag mods --update-settings-with-curent-models that would fetch info about new models (from repo or via API...?)

This is how I have mind configured:
apis:
  openai:
    base-url: https://api.openai.com/v1
    api-key-env: OPENAI_API_KEY
    models:
      gpt-4-1106-preview:
        aliases: ["128k"]
        max-input-chars: 128000
        fallback: gpt-4-32k

If 32k model is configured as 98000 , then I assumed that 128k should be 392000 .

yes, that should work.
The max-input-chars is an estimation only...

added to config_template.yml: https://github.com/charmbracelet/mods/blob/main/config_template.yml

probably same change for gpt-4-turbo-preview moving target model


Crash Report - CrisF#3405

Just running snarkworker.  Crashed around the time I started BP on 2nd node.
coda_crash_report_2020-09-20_23-46-57.900224.tar.gz

"(monitor.ml.Error (\"Coda_lib.Snark_worker_error(1)\")\n  (\"Raised at file \\\"src/lib/coda_lib/coda_lib.ml\\\", line 183, characters 12-53\"\n    \"Called from file \\\"src/deferred0.ml\\\", line 56, characters 64-69\"\n    \"Called from file \\\"src/job_queue.ml\\\" (inlined), line 131, characters 2-5\"\n    \"Called from file \\\"src/job_queue.ml\\\", line 171, characters 6-47\"
This is a duplicate of #6028

Closing this issue as it is stale for a long time.


Move to junitparser==2.2.0, removing workaround solved in new version

Issue https://github.com/weiwei/junitparser/issues/71 has been resolved, upgrading junitparser version and removing workaorund.

@kvanbere the root cause for #184 has been fixed upstream. I have reverted the workaround and upgraded to the latest junitparser version. Can you please test if the issue is still fixed for you?
uses<EMAIL_ADDRESS>

OK, thanks! I will try this today.

Yes, it is working 👍


add a way to manually rotate the image

Hello 👋  I am loving this project, thanks for your work!
I love the auto rotate feature but sometimes I want to rotate the image regardless of how the document is oriented.
I am not an expert at Go so definitely appreciate any feedback regardless of if this PR gets merged.
I also looked into having these buttons within /conf instead of / but I could not figure that out 😅
Changes
add buttons to hit the orientation endpoint when autorotate is disabled either via  /conf or RK_CLIENT_AUTOROTATE
Screenshots

Tests

Thank you very much for this contribution (and for digging into the code ;)


⚠ Bofrost.de has degraded performance

In 5770dd6, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1175 ms

Resolved: Bofrost.de performance has improved in 9e9888d.


Multiple files at once

I tried doing a BinderTool.exe *.bnd  hoping it would do each file in the directory and create subfolders for each but it didnt appear to have this functionality. Would it be possible to include that?

cd path_to_root
for /R %%f in (*.bnd) do (
"C:\your binder directory\Bindertool.exe" "%%f"
)
Run this as a .bat files.
Cheers

This functionality is included in the Elden Ring branch and should be merged into the main branch when backwards compatibility with older games is checked out.

Can this Elden Ring branch version be used to unpack SOTF textures ?
if so , what would be the command ? I tried BinderTool d:_MODDING\unpack\ d:_MODDING\unpack textures\ --recurse true , but i get error "System.IO.IOException: Cannot create "d:_MODDING\unpack\chr\c0001.bnd" because a file or directory with the same name already exists." with a lot of files. So i am really unsure I am doing the right procedure at all.

Look at the command line usage section of the README in the Elden Ring branch: https://github.com/Atvaark/BinderTool/tree/elden-ring#usage
The Elden Ring branch should just autodetect the game for you, but you can specify it with -g DarkSouls2
But the main thing is that the path D:\MODDING\unpack textures\ has a space in it at unpack textures - you either need to rename the folder to not have spaces like unpack_textures or unpack-textures, or put quotes around that path in the command line like "D:\MODDING\unpack textures\"


musl fixes and musl+riscv32 fixes

https://github.com/kraj/libc/tree/kraj/musl-fixes rebased onto main with the duplicate symbols fixed up (though the logs from the previous run have expired so I might have missed something).
Closes #3191

@bors r+

:pushpin: Commit 06a97777286e86fba5394db23b8bd87f63373f23 has been approved by JohnTitor
It is now in the queue for this repository.

:hourglass: Testing commit 06a97777286e86fba5394db23b8bd87f63373f23 with merge fae8015f2ff9761f451b0cbe3c32ea360639b741...

:boom: Test timed out

@bors r+

:pushpin: Commit e955ae784b0f977979b44964e3fa19dd31469bde has been approved by JohnTitor
It is now in the queue for this repository.

:sunny: Test successful - checks-actions, checks-cirrus-freebsd-12, checks-cirrus-freebsd-13, checks-cirrus-freebsd-14
Approved by: JohnTitor
Pushing 5e32df0ee7861cfed0ea9c11cfcc59031750b454 to main...


VM: Implement Stack Manipulation Opcodes

TODO

Opcode
status
PR

DUPFROMALTSTACK
open

TOALTSTACK
open

FROMALTSTACK
open

XDROP
open

XSWAP
open

XTUCK
open

DEPTH
open

DROP
open

DUP
open

NIP
open

OVER
open

PICK
open

ROLL
open

ROT
open

SWAP
open

TUCK
open

All PRs are merged, so closing this one


[Model Request] OpenChat 3.5

⚙  Request New Models

Link to an existing implementation (e.g. Hugging Face/Github): https://huggingface.co/openchat/openchat-3.5-0106
Is this model architecture supported by MLC-LLM? (the list of supported models): Yes (Mistral)

Additional context
OpenChat 3.5 models are the best-performing 7B chat models on Chatbot Arena and HumanEval+. They share the same architecture as Mistral, but use a different conversation template as follows (no system message needed):
GPT4 Correct User: Hello<|end_of_turn|>GPT4 Correct Assistant: Hi<|end_of_turn|>GPT4 Correct User: How are you today?<|end_of_turn|>GPT4 Correct Assistant:

Starling-LM-7B-alpha, OpenChat-3.5-0106 share the same conversation template and architecture.

Actually it works well even now with the current new flow. It just needs in few adjustments. Because it's just tuned mistral architecture, and it's supported by mlc.
Here is my shell script for Intel Mac for convertation:
#!/bin/bash

name="openchat-3.5-0106"

model_dir="./models/${name}/" # your path to the model, this is just example
quantization="q4f16_1"
conv_template="gpt2"
output_dir="models/converted/${name}-${quantization}-MLC/"
device_metal="metal"
device_metal_x86_64="metal:x86-64"

output_lib_metal="${output_dir}/${name}-${quantization}-metal.so"
output_lib_metal_x86_64="${output_dir}/${name}-${quantization}-metal_x86_64.dylib"

# Convert weights
mlc_chat convert_weight ${model_dir} \
    --quantization ${quantization} \
    -o ${output_dir}

# Generate config
mlc_chat gen_config ${model_dir} \
    --quantization ${quantization} \
    --conv-template ${conv_template} \
    -o ${output_dir}

# Compile for m1 (or any other device)
mlc_chat compile ${output_dir}mlc-chat-config.json \
    --device ${device_metal} \
    -o ${output_lib_metal}

# Compile for intel mac
mlc_chat compile ${output_dir}mlc-chat-config.json \
    --device ${device_metal_x86_64} \
    -o ${output_lib_metal_x86_64}

Then you need to ajust conversation config.
## Openchat config
conv_config = ConvConfig(
    stop_str="<|end_of_turn|>",
    stop_tokens=[32000],
    separator_style=0,
    seps= [
      "<|end_of_turn|>"
    ],
    system="You system prompt",
)

chat_config = ChatConfig(conv_config=conv_config,)

cm = ChatModule(chat_config=chat_config, ...)


partition_by column changes type

I have a string column comprised of strings ('01','02'....) (these are US state codes, all 2 digit string). When I save a parquet and partition by this column, and then read the parquet back, it strings become integers. Is this behavior expected? If column state_code is a string column, once read it should also be a string column. Trying to specify the schema in the .to_parquet call does not help.
import dask.dataframe as dd
import pandas as pd
data = dd.from_pandas(pd.DataFrame({'state_code': ['01','01','02','02'], 'value': [1,2,3,4]}), npartitions=1)
data.to_parquet('test.parquet', partition_on=['state_code'], engine='pyarrow', write_index=False)
data = pd.read_parquet('test.parquet', engine='pyarrow')
print(data.state_code)

0    1
1    1
2    2
3    2
Name: state_code, dtype: category
Categories (2, int64): [1, 2]

I would like to return a string column. (Of course I can solve this by changing the type of the column once it has been read which is what I am currently doing)

pyarrow allows you to provide the full expected schema on reading.
import pyarrow as pa
schema = pa.schema([
    pa.field("state_code", pa.string()),
    pa.field("value", pa.int64()),
])

pd.read_parquet(
    'test.parquet',
    engine='pyarrow',
    schema=schema
)
0    01
1    01
2    02
3    02
Name: state_code, dtype: object

which works as expected. The downside here is that you have to specify the entire schema. Fields that are not provided explicitly will not be returned

@marcdelabarrera, just checking in, has this helped fix your problem?


Attempted relative import with no known parent package

When I run this demo.ipynb, I encounter the following import error. Theoretically, Python should be able to successfully import from the current directory using ..utils.easydict. Can you explain why this is happening?
ImportError                               Traceback (most recent call last)
Cell In[1], line 8
4 import cv2
6 import torch
----> 8 from config import (Config,
9                     eval_dict_leaf)
11 from utils import (retrieve_text,
12                   _frame_from_video,
13                   setup_internvideo2)
File InternVideo-main/InternVideo2/multi_modality/demo/config.py:17
13 from importlib import import_module
15 import yaml
---> 17 from ..utils.easydict import EasyDict
19 all = ["Config", "pretty_text"]
22 BASE_KEY = "base"
ImportError: attempted relative import with no known parent package

Perhaps the following can be helpful to you:
Method1:
Create a Package: The most straightforward solution is to structure your project as a package:
 InternVideo-main/InternVideo2/multi_modality/
    ├── __init__.py
    ├── utils/
    │   └── easydict.py
    |...

__init__.py: This empty file signals to Python that the my_project directory is a package.
Method2:
Absolute Imports: If you don't want to create a package structure, use absolute imports:
from  InternVideo-main.InternVideo2.multi_modality.utils.easydict import EasyDict

This assumes your my_project directory is on your Python path (either in your PYTHONPATH environment variable or in a location Python searches by default).

@yinanhe I am still running into this issue, it keeps saying "ImportError: attempted relative import with no known parent package" even though I put blank __init__.py files in every folder.

@qingy1337 I checked the code again, and maybe it just need to make sure that the easydict package has been installed, without using relative paths.
https://github.com/OpenGVLab/InternVideo/blob/1c57368fd1942da9e8a24f3404222cffa92cf5b9/InternVideo2/multi_modality/utils/config.py#L17

@yinanhe I solved it by running this code from the multi_modality folder, not multi_modality/demo:
import numpy as np
import os
import io
import cv2

import torch

from demo.config import (Config,
                    eval_dict_leaf)

from demo.utils import (retrieve_text,
                  _frame_from_video,
                  setup_internvideo2)

Now the problem is that flash_attn is taking forever (1+ hrs) to install....

@yinanhe I solved it by running this code from the multi_modality folder, not multi_modality/demo:
import numpy as np
import os
import io
import cv2

import torch

from demo.config import (Config,
                    eval_dict_leaf)

from demo.utils import (retrieve_text,
                  _frame_from_video,
                  setup_internvideo2)

Now the problem is that flash_attn is taking forever (1+ hrs) to install....

Yes, Installing flash_attn is time consuming, but not a necessary library without training

@yinanhe Sorry, I'm still a bit confused, would you mind creating a fork of this repo with a working demo.ipynb? Thanks!


Update Akka versions

Should not require additional changes I think.

Resolves https://github.com/theiterators/akka-http-microservice/issues/26


Nice to have: mock capability

The Promise extension to superagent is not compatible with the superagent-mock plugin (https://github.com/M6Web/superagent-mock).
Since that plugin changes method of the Request object, I tried to provide it with the PromiseRequest by adding the line:
request.Request = PromiseRequest;
But it modifies the end() method, so the problem is "deeper" than I thought. And I don't see how to cleverly solve it :-(
Thanks
Michel

@mdhooge I've got some tests that show how you'll be able to use superagent-promise with superagent-mock after superagent-mock merges my PR on their project. Feel free to bother them to merge it.

This was closed by #13 and is now documented in the readme.


fix SVGO ignoring config for datauri and path

The currently implemented code for multipass leads SVGO to completely ignore config options for datauri and path in most cases so that it will never base64-encode to datauri.

@TrySound Would you mind having a look eventually?

Fixed in https://github.com/svg/svgo/releases/tag/v3.0.0


[iOS] API to enumerate all images contained in a card

See parent #1094 for details

#1748 merged


nixos-render-docs: add support for examples

Description of changes
add support for real examples with toc entries (≍ docbook <example>). the module chapter conversion removed a few examples that can new be restored, and the remaining manual chapters have their examples adjusted to include proper titles for toc purposes. this will also be needed if the nixpkgs manual ever decides to use nrd, its lib section is full of examples that make sense to mark up properly.
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)
[x] Tested, as applicable:

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

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

[x] Fits CONTRIBUTING.md.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/2023-04-11-documentation-team-meeting-notes-40/27261/1


ResourceDictionaries do not support FontFamily and Storyboards

It seems that ResourceDictionary's do not support all the types that the general renderer does.
Perhaps the resources could be inlined into the Xaml / expanded if implementing the Dictionary types is too complex.

Implementing value generator is easy. Inlining XAML and then parsing it on any platform would be super hard. I use XamlReader.Parse in UI Generator. So I prefer to add new types, when there is a need for it  (and it was one of the reasons why UI Generator is open source). :)
I didn't added FontFamily to generator, because I wouldn't be able to auto generate font file for it (you need size etc.). So you would have to add all sprite font files by hand. Would that be a problem? :)
I don't remember, why Storyboard is not supported in resources at this moment. Tho you can use Storyboard in EventTriggers/Styles/ControlTemplates. Maybe I was thinking that reusing just Storyboard does not make sense. I will check that.

Font Family is supported in next version, Storyboard will have to wait a bit.


[33][UI] As a user, I can see error banner

Resolve https://github.com/llleyelll/ic-surveys-ios/issues/33
What happened 👀

Show ErrorView then fade out after one second.

Insight 📝

It is not required in the design but it would be better to show feedback on failure. I create a simple white banner to show error.
Add ErrorView

Proof Of Work 📹

@llleyelll can you share the usage of this view, please?

@llleyelll can you share the usage of this view, please?
I have a bit of worry about we have to layout this view every time we want to use it 😁

@markgravity Yes, it need to layout when use in the view controller.
Here is a example when use in view controller 🙆♀

@llleyelll can you share the usage of this view, please?
I have a bit of worry about we have to layout this view every time we want to use it 😁

@markgravity Yes, it need to layout when use in the view controller.
Here is an example when use in view controller 🙆♀

We may have to repeat this layout code every time we want to show alert, cause its position usually on top or center..
errorView.snp.makeConstraints {
     $0.top.equalToSuperview().offset(50.0)
     $0.leading.trailing.equalToSuperview().inset(24.0)
     $0.height.equalTo(60.0)
}

So I think you should do something like
let alert = AlertView(message: "a message")
alert.show(on: controller) // do your layout and begin animation

that could be cooler 😍
Btw, you should set up constraints to make it has dynamic height base on message content 👍

@markgravity Thank you. I'm not sure which approach you think it better
When use in view controller it will be something like:
func showError(message: String) {
    let errorView = ErrorView(message: message)
    view.addSubview(errorView)
    errorView.show(on: view)
}

Or should add ErrorView as subview and set the message when want to show like:
final class LoginViewController: UIViewController {
    ...
    private let errorView = ErrorView()
}
 // and show it like:
func showError(message: String) {
    errorView.setErrorMessage(message)
    errorView.show(on: view)
}

Or should add ErrorView as subview and set the message when want to show like:
final class LoginViewController: UIViewController {
    ...
    private let errorView = ErrorView()
}
 // and show it like:
func showError(message: String) {
    errorView.setErrorMessage(message)
    errorView.show(on: view)
}

I prefer this 😁
And you don't need to hold its reference if you don't need it later cause when view.addSubview, view will hold it for you
private let errorView = ErrorView()

@markgravity Thanks a lot. I updated the code please help check 🙏 😄


Deprecations

Deprecate the constants in RenderingStrategy as they are a code smell and mildly dangerous (SonarQube S2390)
Deprecate the DeleteWithMapper, SelectWithMapper, and UpdateWithMapper methods in favor of the new style of MyBatis3 specific support (#128)

Coverage remained the same at 100.0% when pulling bdec2d7301f00cfc45e0577923f622b6c9d8a8c3 on jeffgbutler:master into 61fd0cd984c446910ff6f709e3fd2739316e5b55 on mybatis:master.


Added some delays and root function.

Hey there! I am @isharp21. This is my pull request for users who uses ubuntu and other debian based systems.. :) I hope it helps :D :+1:  :astonished:

Sleeping is pointless; it merely wastes time. The OS is intended to be built in a VM, so sudo is not required either.

Why do you use sleep here?
The script executes one line after one another. So, the sleeps are completely useless, they are just taking your time away.

Well The hardware time collides so it makes errors. So that's why I add
sleep so that action first takes place than the time..


Add unsaved changes alert for pack changes

Show a warning if there are pending unsaved changes in the pack edit view when trying to navigate away.
My screen recorder won't show it, but if you try to close the tab or refresh it will do a normal JS alert to prevent the page from closing. Closes #10.

https://user-images.githubusercontent.com/1940054/104144554-9cbe1b80-5391-11eb-971d-040ec9dd47cf.mp4

This is great 🎉

This is great 🎉

Looks like it will require the conflict to be resolved and then we can merge it. @darinalleman

Looks like it will require the conflict to be resolved and then we can merge it. @darinalleman

Conflicts resolved!

Conflicts resolved!


Standardize builder naming

This pull request changes the DispatcherBuilder API to have non-consuming add_ methods in addition to the consuming with_ methods. The old add_ prefix was replaced by a with_ prefix.
One open question is whether we want the add_ methods to return &mut Self instead of ().
Need for this change arose from amethyst/amethyst#304. When standardizing the builder naming in Amethyst, we need non-consuming methods in order to pass Rusts borrow checker.
This is a breaking change.

I'm not sure yet when we want to release a new version. Specs 0.10 has been released lately, so I'm gonna wait a bit before doing any version bumps.
bors r+


Select Multiple Cells and Copy/Paste

Feature: Notebook Editor, Interactive Window, Python Editor cells

Description
One feature I've found myself wanting is the ability to select multiple cells to move or copy/paste them as a group (into the same notebook or into a different one).
As far as I can tell, this functionality has not been implemented in the native Code notebook editor. If it has been and I'm not seeing it, I apologize.
The native notebook editor is a gamechanger for me. Thank you so much for all of your hard work!

Hi, just started using VSCode notebooks instead of Jupyter notebooks and found it actually works pretty well except for this missing feature of copying/pasting/moving multiple or even single cells. Hopefully this feature will be added soon.

I'm trying migrate from jupyter to vscode, but some features on nbextensions doesn't existing, losing time to do the same operation. This multiple cells selection is an example of this missing feature.

I'm trying migrate from jupyter to vscode, but some features on nbextensions doesn't existing, losing time to do the same operation. This multiple cells selection is an example of this missing feature.

Until this feature is implemented, a workaround is to view the notebook as plain text (right click in explorer panel, Open With..., and select Text Editor).  Copy and paste the cell objects as desired, then close the text tab and re-open as notebook.  Not elegant but it works.

As a suggestion, this extension working on jupyter lab allows you to select many cells by holding down the shift key and playing with J and K keys following the vim convention: you can then cut/copy it at your ease.
This is one of the very few feature of this jlab extension that is not fully reproducible on vscode yet, would be awesome to see it coming on code!

This feature is currently available in VS Code Insiders today! Try it out and let us know your thoughts, this will be moving to VS Code Stable when ready :)


Using a higher input resolution than 160x120

Hi,
The code provides great results but at times it feels like the quality of the upscale and colorization of finer details is limited by the small input resolution of 160x120. Evaluation using evalute.py only seems to allow for an input resolution of 160x120 for our low-resolution greyscale video. For example, using frames with a size of 320x240 returns 'RuntimeError: stack expects a non-empty TensorList'. I also encountered at one point 'runtimeerror: Sizes of tensors must match except in dimension 1' when attempting to use a frame size above 160x120. Is there any way to use a higher resolution frames for our lr-set video set folders?

The evaluate.py is designed to work with dataset of an arbitrary resolution. Case in point, evaluation datasets used in the paper comprise of video sequences with multiple resolutions. Is it possible to provide more details about the error and your setup?

Hi @vb000 ,
I think I understand why the error is occuring. The evaluate.py is expecting a lr video set which is 1/4 the size of the hr video set, i.e. lr video set is 160x120, hr video set is 640x480.
Therefore, my question is: Is it possible to turn off the upscaling feature of Neuricam and only use color propagation?
For example, I would like to use a 640x480 input video set and generate a 640x480 output.
I have tried editing params.json in /experiments/bix4_keyvsrc_attn and changing "upscale_factor" from 4 to 1.
However the following error returns when trying to run evaluate.py
Traceback (most recent call last):   File "evaluate.py", line 182, in <module>     args.output_dir, args.file_fmt, args.profile)   File "evaluate.py", line 81, in evaluate     output_batch = model(train_batch)   File "/usr/local/lib/python3.7/dist-packages/torch/nn/modules/module.py", line 1130, in _call_impl     return forward_call(*input, **kwargs)   File "/content/NeuriCam/model/net.py", line 27, in forward     return self.model(model_in)   File "/usr/local/lib/python3.7/dist-packages/torch/nn/modules/module.py", line 1130, in _call_impl     return forward_call(*input, **kwargs)   File "/content/NeuriCam/model/keyvsrc/net.py", line 151, in forward     feats = self.propagate(lr_s, feats, key_frame_int)   File "/content/NeuriCam/model/keyvsrc/net.py", line 96, in propagate     feats = self.basicvsr_pp.propagate(feats, flows, module)   File "/content/NeuriCam/model/basicvsr_pp/basicvsr_pp.py", line 240, in propagate     flow_n1, flow_n2)   File "/usr/local/lib/python3.7/dist-packages/torch/nn/modules/module.py", line 1130, in _call_impl     return forward_call(*input, **kwargs)   File "/content/NeuriCam/model/basicvsr_pp/basicvsr_pp.py", line 433, in forward     out = self.conv_offset(extra_feat)   File "/usr/local/lib/python3.7/dist-packages/torch/nn/modules/module.py", line 1130, in _call_impl     return forward_call(*input, **kwargs)   File "/usr/local/lib/python3.7/dist-packages/torch/nn/modules/container.py", line 139, in forward     input = module(input)   File "/usr/local/lib/python3.7/dist-packages/torch/nn/modules/module.py", line 1130, in _call_impl     return forward_call(*input, **kwargs)   File "/usr/local/lib/python3.7/dist-packages/torch/nn/modules/conv.py", line 457, in forward     return self._conv_forward(input, self.weight, self.bias)   File "/usr/local/lib/python3.7/dist-packages/torch/nn/modules/conv.py", line 454, in _conv_forward     self.padding, self.dilation, self.groups) RuntimeError: Given groups=1, weight of size [64, 196, 3, 3], expected input[1, 136, 484, 644] to have 196 channels, but got 136 channels instead
Thanks for your help.

The model is designed to for 4x upscaling, other scaling factors might need some tweaks. A workaround for your use case is, you could upsample the key-frame sequence to 2560 x 1920 resolution, or downsample the lr-set to 160 x 120 resolution, using bilinear or bicubic interpolation. That way, the lr-set would be 4x downsampled relative to the key-set, allowing you to use the existing model and weights. In the former case, you would have to downsample the NeuriCam-net's output to 640x480 resolution. And in the latter case, the output resolution would be 640 x 480.
A thing to note: since all you want to do is color propagation, you can only take the ab channels from the NeuriCam-net's output and concatenate them with the original L channel of the input to obtain the color video.


[SITE REQUEST]Flying Lines

Flying Lines
Does the host have more than 15 novels?
Yes
Website link:
https://www.flying-lines.com

Flying Lines was previously discussed here. Unfortunately nothing has changed yet from what I can see.


Generated dollar-quote escape sequences are Bash-specific (in practice)

For the code
RUN apt-get update && \
	apt-get -y install --no-install-recommends

… Bash-TPL generates:
printf "%s\n" RUN\ apt-get\ update\ \&\&\ \\
printf "%s\n" $'\tapt-get -y install --no-install-recommends'

Which prints
RUN apt-get update && \
$\tapt-get -y install --no-install-recommends

…when run with Dash.
As the readme says, the generated scripts are not supposed to use Bashisms.

The shell scripts that Bash-TPL generates are not intended to be Bash-specific.

The feature in question is, as far as I can tell, part of POSIX 2024, but it’ll be a while until support for it is added to all shells.
Dash has committed a patch that adds it just a few hours ago.
I’m not sure whether it’s worth fixing it, but I guess this behavior should be at least documented here on the bug tracker.

Greetings @0xEAB  !
Looking into a bit more, i think the issue is that I use %s as the formatter, when I should probably be using %b
Paste this into your DASH shell:
swap %s with %b
printf "%b\n" RUN\ apt-get\ update\ \&\&\ \\
printf "%b\n" $'\tapt-get -y install --no-install-recommends'

%b does appear to be a standard for posix printf:

https://www.unix.com/man-page/posix/1posix/printf/

... An  additional  conversion  specifier character, b , shall be supported as follows. The argument shall be taken to be a string that may contain backslash-escape sequences

It appears that many shells treat %s and %b similarly, which is likely why I didn't discover the issue earlier.
This fix is simple, but would technically be a breaking change ...
Just the same I'll put a PR together as it seems like the right thing to do.
If you want to test it out, I believe the change will be:
before: line 560
	if [ -n "${args}" ]; then
		printf -v stmt "printf \"%%s\\\\n\" %s" "${args}"
	else
		printf -v stmt "printf \"\\\\n\""
	fi

after
	if [ -n "${args}" ]; then
		printf -v stmt "printf \"%%b\\\\n\" %s" "${args}"
	else
		printf -v stmt "printf \"\\\\n\""
	fi

Feel free to give that a try, and I'll also msg you when the PR  is up in case you want to take a test drive before merging.
Thanks for using my project and taking the time to submit an issue!

This however seems to work:
$ printf "%b\n" '\tapt-get -y install --no-install-recommends'
	apt-get -y install --no-install-recommends

Ugh, you're right - I didn't notice the $ at the start of the line when I tested that :(
OK so I see now that I didn't need %b previously because $'...' is rather equivalent, ie expands escape sequences ...
I think I'll need to find a posix friendly function I can add to the file and call instead of printf %q to escape my strings ...
I'll look into and let you know what I find - Please also share any further research you may do on the matter.
I'm going to leave this issue open but close the MR ...


Incorrect hot-cold clue dig location

Reported from Discord:

It worked 3 squares east

Looking into the code for the first time I am not sure what can be done for this one. It seems that dig coordinates are determined off of player coordinates when clicking the device. I'd like to see if this has been an issue for anyone else or he was just unlucky.

We could fix the worldpoint of this clue spot that we defined manually? I'm not sure what you mean "not sure what can be done for this".

Ahh okay I see it in the API now. I was looking the logic of possible dig locations too much. I have not looked much into the API yet but I'll give it a shot.


TiKV panic during import data because of RocksDB Corruption.

Bug Report

What version of TiKV are you using?

master
What operating system and CPU are you using?

Steps to reproduce

What did you expect?
What did happened?
TiKV panic and can not restart again

/severity Critical


Added meta tags and support data

Description
Meta tag changes  for better visibility
By submitting this pull request, I confirm that my contribution is made under the terms of the BSD-3-Clause License.

w00t!


Consider removing BlocksPerYear

Context
The inflation module (x/mint) proposed in https://github.com/celestiaorg/celestia-app/pull/1578 relies on an estimate for the number of blocks produced in a year. The estimate is currently hard-coded
	// BlocksPerYear is an estimate for the number of blocks produced by the
	// Celestia blockchain per year. This number is based on the assumption that
	// the block interval (i.e. TargetHeightDuration) is 15 seconds.
	//
	// 31,536,000 seconds in a year / 15 seconds per block = 2,102,400 blocks per year.
	BlocksPerYear        = 2_102_400

The estimate is used to calculate the amount of new tokens that should be minted on a per-block basis. The estimate is needed because the block interval in Tendermint chains isn't guaranteed. We expect the block interval to be 15 seconds but it may diverge.
Problem
If we keep the estimate hard-coded then it's likely that the actual number of blocks produces diverges slightly from the estimate. When this occurs, the amount of new tokens minted due to inflation will diverge slightly from the intended value.
It is worth noting that the BlocksPerYear constant can be updated in future hard-fork upgrades based on the observed network block intervals.
Proposal
Consider removing the BlocksPerYear constant in favor of a dynamic value based on a moving average of the block interval for the last N blocks (e.g. where N is 10,000). Functionally this would behave similarly to https://testnet.mintscan.io/celestia-incentivized-testnet/blocks/909774

Note this option has the downside that the number of tokens minted for a block is less predictable ahead of time because it will be dependent moving averages of block intervals.

not hardcoding blocks per year was my understanding of this thread, and imo we should do this to have stronger guarantees around inflation. Otherwise, if validators change their locally configured values for block times, then they could mint significantly more tokens than otherwise permitted.

Otherwise, if validators change their locally configured values for block times, then they could mint significantly more tokens than otherwise permitted.

This risk remains if we use a moving average estimate. Validators can configure their local block interval time to be shorter to mint more tokens but I don't think this type of attack is likely considering validators don't earn the inflation rewards on a per block basis. AFAICT block based inflation rewards land in a pool distributed to all delegators. If such an attack were likely, I would expect it to have already occurred on an existing Cosmos chain.
From my perspective, the only difference is that a dynamic moving average estimate would automatically update the BlocksPerYear whereas a hard-coded BlocksPerYear would require protocol engineers to update the value to reflect the network observed block interval.
I choose to punt this to after mainnet because I think there are risks associated with using a moving average. See
https://github.com/cosmos/cosmos-sdk/issues/5411#issuecomment-597228083 so we should thoroughly explore new attack vectors that may be introduced by a moving average estimate for BlocksPerYear.

I also agree that hardcoding this value is okay for now

We'd have stronger guarantees around time if proposer based timestamps was implemented. This could also be used to more strongly shape an adequate block production frequency.

Closed via https://github.com/celestiaorg/celestia-app/pull/1578/commits/ebd3775e55b164f828516e42aa828478567a6673


[WIP] Multi-top SW

This is still a WIP, please refrain from commenting too much on the details at this point. High-level comments are welcome.
This is a test PR for the multi-top SW effort. The goal of this PR is to see (1) how much is broken in CI, (2) allow for high-level comments on the approach.
Explanation:
TODO
Important: LTO is not enable in this PR.
How to regenerate everything after making changes to templates:
Run
util/topgen.py -t hw/top_earlgrey/data/top_earlgrey.hjson
make -C hw dt-api
util/make_new_dif.py --mode=regen --only=autogen

How to test:
Run
./bazelisk.sh test --test_output=streamed //sw/device/tests:aon_timer_irq_test_fpga_cw310_rom_with_fake_keys //sw/device/tests:sysrst_ctrl_outputs_test_fpga_cw310_sival

TODOs:

[ ] cleanup the templates (they are super messy and contain duplicated code)
[ ] think about how to handle ipgen-ed and topgen-ed headers in DIFs.
[ ] redo the LTO work from a clean state, see #22052

This is still a WIP, please refrain from commenting too much on the details at this point. High-level comments are welcome.

Just a reminder that Co-authored-by is a way to give attribution to code that wasn't only done by you. ;)

Just a reminder that Co-authored-by is a way to give attribution to code that wasn't only done by you. ;)

Sure no worries, I'll add you back :) I just created this PR because several people didn't like looking at code in my branch (the GitHub UI is pretty poor). I have basically just squashed all commits into a few. The original code is here if you want the messy history: https://github.com/lowRISC/opentitan/compare/master...pamaury:opentitan:dt_for_multitop

I have made a change to the file structure: now instead of generating some files using reggen and some using topgen, I am generating everything using topgen and putting it in hw/top_earlgrey/sw/autogen. The rationale for this change is that:

it's simpler on both the generator and user side,
it will be very useful for english breakfast where files are generated but not checked in.

I am now able to build the test_rom for english breakfast. For those interested:
./bazelisk.sh build --config=english_breakfast --config=riscv32 //sw/device/lib/testing/test_rom:test_rom

Note that there is no test infrastructure to EB yet so to be able to use this, it's still a very manual process:
./bazelisk.sh build --config=english_breakfast --config=riscv32 //sw/device/lib/testing/test_rom:test_rom
./bazelisk.sh cquery --config=english_breakfast --config=riscv32 //sw/device/lib/testing/test_rom:test_rom_sim_verilator
# copy the file test_rom_sim_verilator.32.vmem to somewhere safe, e.g /path/to/safe/test_rom_sim_verilator.32.vmem
# Then download the verilator build for EB from a CI run and put it somewhere, e.g. /path/to/safe/Vchip_englishbreakfast_verilator
# finally run:
./bazelisk.sh run //sw/host/opentitantool -- --logging=info --interface=verilator --verilator-bin=/path/to/safe/Vchip_englishbreakfast_verilator --verilator-rom=/path/to/safe/test_rom_sim_verilator.32.vmem console

I have rebased the PR, notably this included a change to english breakfast which now has two UARTs. Also going through linting fixes.

Hey Amaury, where do you expect the per-top SW files to reside? Not just the parameters, but the actual functions that will be top-specific?

Hey Amaury, where do you expect the per-top SW files to reside? Not just the parameters, but the actual functions that will be top-specific?

Hi @matutem, for now it's all in those targets:
build
./bazelisk.sh build //hw/top_earlgrey/sw/autogen/...
then query files:
./bazelisk.sh cquery //hw/top_earlgrey/sw/autogen:top_earlgrey_dttool_dt_api
./bazelisk.sh cquery //hw/top_earlgrey/sw/autogen:top_earlgrey_dttool_dt_lib_hdrs
./bazelisk.sh cquery //hw/top_earlgrey/sw/autogen:top_earlgrey_dttool_dt_lib_srcs

Regarding my last question about generated SW, this is a drawback of not committing generated files: to see the changes I will need to copy the PR, build, and inspect the generated objects: not particularly smooth. And probably more problematic, when generation changes it may be harder to view the differences, let alone see the history of those changes. I'd say that is undesirable.

Regarding my last question about generated SW, this is a drawback of not committing generated files: to see the changes I will need to copy the PR, build, and inspect the generated objects: not particularly smooth. And probably more problematic, when generation changes it may be harder to view the differences, let alone see the history of those changes. I'd say that is undesirable.

I am not sure that we should be checking those files: they are very verbose but most of the code is of no particular interest, also it makes diff very large when doing changes which is not particularly helpful. I believe that what is more useful than the code itself is the documentation so that people can see how to use it. Unfortunately, our documentation system currently cannot handle generated file but this is something that we should fix. Note that we are also not checking in the repo the IP register header and we have the same problem with the documentation.


Implement Vega-Lite 4.0 transforms

Vega-Lite 4.0 adds a number of additional transforms, including density, loess, pivot, quantile, and regression. These can't be fully supported until Altair 4.0 comes out, but we could start implementing them before that.

I was wondering if for these transforms the calculated values will now be accessible, as the current release of altair is 4.1.0?
Especially I would like to extract the values of a density transform, but get the NotImplementedError.
My current way around is to calculate a KDE outside of altair (using SKLearn, as @jakevdp recommended here). But it would be great if I was able to do it from altair directly because of the easy groupby functionality it provides.

Some of these transforms have been implemented on master, but there hasn't been a release of this package for a while/


FrancoisKan's File

Created a branch, created a file, and made a commit, and opened a pull request

Adjusted


Glide import is broken

Thrift has been pulled into the vendor folder:
opencensus-go/vendor/git.apache.org/thrift.git/
It was copied in an incomplete way, and contains a symbolic link that does not point to a valid target.
This breaks glide imports for the opencensus-go project

What is the name of the link?

https://github.com/census-instrumentation/opencensus-go/blob/master/vendor/git.apache.org/thrift.git/tutorial/erl/server.sh


HttpTrait is incorrectly required on RPC protocols

Describe the bug
According to Smithy docs (https://smithy.io/1.0/spec/aws/aws-json-1_1-protocol.html#supported-traits) RPC based protocols do not support HttpTrait, yet we currently require them on all protocols (https://github.com/smithy-lang/smithy-swift/blob/88529feec7b618eede831a82729f732f691e05fc/smithy-swift-codegen/src/main/kotlin/software/amazon/smithy/swift/codegen/integration/HttpBindingResolver.kt#L47).
Expected Behavior
We should only require HttpTrait on supported protocols which includes @restJson1 and @restXml.
Current Behavior
When using a smithy file with RPC based protocols such as @awsJson1 or @awsJson1_1 we improperly error, forcing the user to add an HttpTrait.
Reproduction Steps
Example Smithy File that errors:
namespace com.test

use aws.protocols#awsJson1_1
use aws.api#service
use aws.auth#sigv4

@awsJson1_1
@sigv4(name: "event-stream-test")
service Example {
    version: "123",
    operations: [TestStreamOperationWithInitialRequestResponse]
}

operation TestStreamOperationWithInitialRequestResponse {
    input: TestStreamInputOutputInitialRequestResponse,
    output: TestStreamInputOutputInitialRequestResponse,
    errors: [SomeError],
}

structure TestStreamInputOutputInitialRequestResponse {
    @required
    value: TestStream
    initial: String
}

@error("client")
structure SomeError {
    Message: String,
}

structure MessageWithString { @eventPayload data: String }

@streaming
union TestStream {
    MessageWithString: MessageWithString,
    SomeError: SomeError,
}

Example Error:
Oct 02, 2023 11:05:50 AM software.amazon.smithy.swift.codegen.model.AddOperationShapes$Companion execute
INFO: building unique input/output shapes for com.test#TestStreamOperationWithInitialRequestResponse

software.amazon.smithy.model.node.ExpectationNotMetException: Expected shape `com.test#TestStreamOperationWithInitialRequestResponse` to have a trait `software.amazon.smithy.model.traits.HttpTrait` (/Users/dayaffe/Documents/Development/SwiftSDKWorkspace/smithy-swift/smithy-swift-codegen/build/resources/test/event-stream-initial-request-response.smithy [14, 1])
	at app//software.amazon.smithy.model.shapes.Shape.lambda$expectTrait$0(Shape.java:332)
	at java.base@17.0.8/java.util.Optional.orElseThrow(Optional.java:403)
	at app//software.amazon.smithy.model.shapes.Shape.expectTrait(Shape.java:332)
	at app//software.amazon.smithy.swift.codegen.integration.HttpTraitResolver.httpTrait(HttpBindingResolver.kt:47)
	at app//software.amazon.smithy.swift.codegen.integration.HttpBindingProtocolGenerator.getHttpBindingOperations(HttpBindingProtocolGenerator.kt:488)
	at app//software.amazon.smithy.swift.codegen.integration.HttpBindingProtocolGenerator.initializeMiddleware(HttpBindingProtocolGenerator.kt:424)
	at app//HttpProtocolClientGeneratorTests.setupTests(HttpProtocolClientGeneratorTests.kt:162)
	at app//HttpProtocolClientGeneratorTests.it renders client initialization block for event streaming(HttpProtocolClientGeneratorTests.kt:13)
	at java.base@17.0.8/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

This same file works by adding @http(method: "POST", uri: "/example") to the operation.
Possible Solution
Only apply this expectation if the protocol supports it.
Additional Information/Context
We may also discover additional areas where we improperly call classes RestX when they actually use RPCx or apply checks which do not belong on all protocols.
AWS SWIFT SDK version used
latest
Compiler and Version used
latest
Operating System and version
latest

Effort is for investigation. We are not currently sure why we haven't seen errors during codegen for the 300+ supported AWS services.

Issue is contained to our testing setup. Will take up being able to have protocol-specific tests when needed in other issues.


Cannot add a file without extension as a path to scan

We have a file named application/console, and when I add it to the paths to scan, it fails with this error:
Unable to list files in /app/application/console
It looks like a file without extension is automatically assumed to be a directory.

Fixed in 1.2.1

It works. Thanks.


zml: sharding

First rough support for in-process sharding.
The goal of sharding is to allow leveraging several GPUs to collaborate to run one big model.
Current implementation:

added platform.sharding() describing how the set of devices managed by the current process should be used.
added a _sharding_info to shape.
A tensor / shape axis can be marked as needing sharding using .withSharding(.{ .a }) or .withSharding(.{ 1 }).
When using populateModelWeights tensors with sharded axes, will be populated by sharded buffers.
when generating the MLIR bytecode for a ZML function the input arguments, will see their _sharding_info converted into mhlo.sharding attributes

I don't totally understand the logic about contiguous in HostBuffer though.

HostBuffer can have strides, and don't need to be contiguous. This was introduced to support .pt where buffer can be stored non-contiguously.
I've also added the slice1d utility that allows to slice a HostBuffer in several non-contiguous slices.
Since it's possible (and now easy) to create non-contiguous slices, I've added a check in few places that we are indeed working on contiguous HostBuffer (which was always the case before adding .pt)

Thanks for the review and the suggested improvements !


Aux window + maximize group breakage

Type: Bug

Open a couple of editor groups, let's say 2 in the main window and 2 in the aux window.
Maximize one of the groups in the main window
Maximize one of the groups in the aux window (note the wrong Unmaximize menu label while at it)
Try to unmaximize the group in the main window

Expected behavior: aux window's group maximized state is decoupled from the main window's group maximized state.
Actual behavior: Maximizing groups in aux window(s) interferes with the main window's state.
While related to https://github.com/microsoft/vscode/labels/workbench-auxwindow, this is probably more within the area of https://github.com/microsoft/vscode/labels/workbench-editors or https://github.com/microsoft/vscode/labels/workbench-editor-grid.

VS Code version: Code - Insiders 1.84.0-insider (2f32f0edae007ddd03699c325a451184c4c5e89b, 2023-10-23T17:32:30.191Z)
OS version: Windows_NT x64 10.0.18362
Modes: Unsupported
Connection to 'ssh-remote+sestolabccv8' could not be established

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-8665U CPU @ 1.90GHz (8 x 2112)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
undefined

Memory (System)
15.81GB (4.84GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions: none

/duplicate https://github.com/microsoft/vscode/issues/196266

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Happy Coding!


[Bug]: Cannot Open Stretchly 1.13.0 on Windows 10

Version

[X] I'm using version 1.13.0

Known issues

[X] I've checked Known issues

Existing issues

[X] I've checked Existing issues

What operating system are you using?
Windows
Operating System Version
Windows 10 21H2
Reproduction steps

Download Stretchly-Setup-1.13.0.exe
Run the installer, issue occurs for both install for all users and install for me
Finish setup
Open Stretchly
Error Message Shows Up
...
Reproduces how often: 100%

Expected Behavior
No error
Actual Behavior
Error window

Relevant log output
[2022-12-23 21:44:42.513] [info]  Stretchly: initializing...
[2022-12-23 21:44:42.522] [info]  Stretchly: migrating preferences from Stretchly v0.0.0 to v1.13.0
[2022-12-23 21:44:42.525] [error] Error: Something went wrong during the migration! Changes applied to the store until this failed migration will be restored. TypeError: Use `delete()` to clear values
    at ElectronStore._migrate (C:\Users\ACER\AppData\Local\Programs\Stretchly\resources\app.asar\node_modules\conf\dist\source\index.js:429:23)
    at new Conf (C:\Users\ACER\AppData\Local\Programs\Stretchly\resources\app.asar\node_modules\conf\dist\source\index.js:150:18)
    at new ElectronStore (C:\Users\ACER\AppData\Local\Programs\Stretchly\resources\app.asar\node_modules\electron-store\index.js:69:3)
    at App.initialize (C:\Users\ACER\AppData\Local\Programs\Stretchly\resources\app.asar\main.js:167:16)
    at App.emit (node:events:513:28)

Preferences
No response
Additional information
This is my first installation of Stretchly
Also, Stretchly 1.12.0 installs and runs successfully.

Code of Conduct

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

Hi, I guess this is because it's first install. If you install 1.12 and then 1.13, it should work ok :) can you try?

I wrote a quick fix, so next version will have this :)

Insomnia update: yeah installing 1.12 and then 1.13 works. Thanks for the quick response!

Glad to hear that, hope you'll enjoy Stretchly!

I had the same issue on Windows 11 and installing 1.12 also resolved it. But that still makes it a bug right? Bit odd that 1.13 is not standalone?

Also just installed on a 2nd Win11 machine, and 1.12 needs to be run after install, then install and run 1.13. Only installing 1.12 is not sufficient.

Ah, okay :)  I am just making new release 1.13.1 that should fix that, so fingers crossed :)


[shared engine] Consider letting developers take over life cycle events in add-to-app scenarios if they want

The current life cycle of AppLifecycleState is associated with the life cycle of FlutterActivity/FlutterViewController.
It seems that because we did not consider the add-to-app scenario when it was originally designed.
But in an add-to-app scenario, this may not work. This is because the application may have multiple FlutterViewController/FlutterActivity, and they share one FlutterEngine.
The wrong setting of AppLifecycleState may cause the frame to fail to be scheduled and rendered correctly.
So I guess we can provide a option to developers to let them take over life cycle events if they want. If so, flutter will no longer send life cycle events, but let developers send life cycle events themselves.
related issue:
https://github.com/flutter/flutter/issues/52456
/cc @gaaclarke @blasten

Where do you expect to manage the lifecycle events?
The concept of AppLifecycleState coupled the application-level lifecycle with a single activity lifecycles. However, I don't know if there's a good way to solve this problem other than giving you the control to call it when appropriate.

For scenarios where multiple FlutterActivity shares the same engine, I think it would be more reasonable to pair the AppLifecycleState with the app's lifecycle. So developers could send lifecycle events when the app goes to the background and back to the foreground.


Safari scroll behavior isn't patched on SSR

When using vue-snap with SSR in a Nuxt app, I noticed that the scroll behavior of Safari isn't smooth when using the arrow buttons. After doing some digging I see where the seamless-scroll-pollyfill is being included to pollyfill Safari, but it's being excluded from the SSR.
This makes sense as the pollyfill looks for the window object which won't exist on the server, but it raises the question what is the recommended way of patching Safari if you're using SSR? Would the right approach be to include the polyfill in the mounted() hook on the client side?

If anybody else encounters this, this is how I resolved it:
<script lang="ts">

import Vue from 'vue'
import { elementScrollToPolyfill } from 'seamless-scroll-polyfill'

export default Vue.extend({
  mounted() {
    if (!('scrollBehavior' in document.documentElement.style)) {
      elementScrollToPolyfill()
    }
  },
})
</script>

Is this plugin still under active development?


ssh: connect to host myfarmer port 22: Connection timed out

Hi recently getting
ssh: connect to host myfarmer port 22: Connection timed out
or connect to host myfarmer port 22: Connection refused

What's that mean? Where is plotman trying to connect to?

I would assume this to be related to the default archiving config. Either change the config to set it up for your system or disable it with the information here: https://github.com/ericaltendorf/plotman/wiki/Archiving#disable-archiving-in-plotman

ahh, ty!


SSL Issue when running a get command in Plain Text on MacOS

I received an ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1129) error when trying to run the synergy_dataset get on macOS Ventura Version 13.6.6.
It is a known issue on MacOS that I was able to solve using the open /Applications/Python\ 3.9/Install\ Certificates.command in a terminal.
This is a common issue on macOS where Python is not able to verify the SSL certificate provided by the server. To fix it we are using Certificates.command script from python.org for macOS.

I can verify this happening on more machines running OSx.


Deployment

Deployment
User Story
As a boot camp student,
I want the prework notes to be structured on a webpage,
So that I can easily find and read the information.
Acceptance Criteria
GIVEN a Prework Study Guide website,
WHEN I visit the website using the URL,
THEN I can access the website using any browser

deployed and page is live


Get the version number using git tags

This lets us avoid having a hardcoded file in the repo and having to update it for a release. This way releases can be done simply by tagging the appropriate commit and rebuilding.
This will be useful for when we publish packages, since it lets us publish a package every time we run CI and not have it conflict with or overwrite the latest package.

this will fail on windows or if e build from the github tarball

It works on Windows, I specifically modified the code so that it would. Why would we build from the github tarball?

@nbelakovski, thank you for proposing this. Ping me when both you and @jschueller think it is ready.

it wont work on windows without bash support, why not call directly the git command from cmake instead ?

also it should work from the tarball, macports already uses it, and so will linux distro usually

I changed it to use git describe so that it's not necessary to use a bash script. I had actually initially wanted to use it, but I think I didn't like the default output and so I wanted to make my own but long story short I'd rather keep things simple.
I also learned about export-subst in this process, which lets you write a file in such a way that git archive will substitute certain placeholders in the file with git information, and can even include the output of describe. This should solve the macports case.
I validated that the .git-archival.txt file is set up correctly by performing the following actions on my machine (I obtained the githash from going into the actions and looking at the output of the clone repository action):
$ curl -L https://api.github.com/repos/libprima/prima/tarball/9a0485ea -o myarchive.tgz
$ tar xzf myarchive.tgz
$ cd libprima-prima-9a0485e
$ cat .git-archival.txt
v0.7.2-162-g9a0485ea5

Note that the above commands will return a blank output on forked repos since they do not copy tags by default.

Hi @nbelakovski and @jschueller , is the PR ready? Thank you.


Create modrinth release

Need to create a release for modrinth. Can be done using the existing pipeline github action.
This should follow #45, #46, #47

Added to the yml, will resolve once mods approve on modrinth

https://modrinth.com/mod/gilly7ce-carpet-addons


Code Animation

Many years ago Microsoft had a product called Quick Basic and Professional Development System.  They are the grandfathers/ancestors of VS Code!
One amazing feature was code animation. It would automatically step thru code like a movie and you can sit back and watch! You can also set the speed and watch variables. This feature disappeared over the years but is useful, both for new dev and  an experienced dev with a new complex codebase.
I had a project years back where I helped write an IDE for a proprietary language, and this was a very helpful feature! I could even see this going to the next level with a graphical overlay path where the statements execute.
I wonder if this can be added to VS code.  If I had the time I would try to dig into it.

We try to keep VS Code lean and we think the functionality you're asking for is great for a VS Code extension. Maybe you can already find one that suits you in the VS Code Marketplace. Just in case, in a few simple steps you can get started writing your own extension. See also our issue reporting guidelines.
Happy Coding!


Sporadic i/o timout when proxying to container with Spring Boot application

What version of Traefik are you using (traefik version)?
traefik:camembert
What is your environment & configuration (arguments, toml...)?
docker swarm mode (1.2.5).
acme enabled and certificates resolve via host rules.
I have a duplicate setup in test.
What did you do?
Made several requests to the spring boot application AND to an nginx container – both through traefik.
What did you expect to see?
All requests should have gone through without timeouts on both contaienrs
What did you see instead?
Some requests times out on the spring boot container - also in my duplicate test environment.
time="2016-12-21T06:33:59Z" level=warning msg="Error forwarding to http://<IP_ADDRESS>:8080, err: dial tcp <IP_ADDRESS>:8080: i/o timeout"

I thought it was related to https://github.com/containous/traefik/issues/615, but that seems to be fixed after traefik bumped to go 1.7?
I have the same container running in another docker environment behind an nginx without issues.

@michaelkrog I reproduced a lightweight stack to try to reproduce your issue and was not able to reproduce it yet.
I have some questions :

I your other docker environment with spring boot behind nginx, are you also using swarm ?
How many requests do you need to reproduce the issue ?
Did you try to reach the spring boot container directly to see it you have the same type of errors ?

@trecloux

I am using swarm mode. I have no nginx involved. It is traefik -> spring boot directly.
If I make 200 requests over af period of 2-3 minutes, then I get approx. 1-5 timeouts.
Yes. I have two other services behind traefik running websites. I tried logging into one of those containers and did 1000 requests using curl to my spring boot container without any issues.

Do you have any hints towards getting more relevant debug info out of it?

@michaelkrog
For question 1, I was referring to

I have the same container running in another docker environment behind an nginx without issues.

In this context, are you using swarm mode ?
Can you provide us your toml configuration, the traefik log output and a summary of your docker swarm commands.

Could it be related to https://github.com/containous/traefik/issues/719?
This service is connected to 2 networks. The other services are only connected to 1 network and they have no issues.
Not saying that's is the cause - only that's it's possibility.

@trecloux
This seems to be the same issue as #999. When I add a traefik.docker.networklabel that specifies which network traefik must use, then the issue is gone.

Closing as duplicate of #999 then.

If I put this config I have the same issue
services:
  thingsboard:
    image: thingsboard/application:1.2.3
    ports:
      - 8089:8080
      - 1883:1883
      - 5683:5683/udp
    networks:
      - thingsNetwork
      - traefikNetwork

    labels:
      - traefik.backend=thingsboard
      - traefik.frontend.rule=Host:iotpilot.ddns.net
      - traefik.port=8080
      - traffic.docker.network=traefik_traefikNetwork

networks:
   traefikNetwork:
      external:
        name: traefik_traefikNetwork
   thingsNetwork:
      driver: bridge

But if I put the traefik network first, it works
services:
  thingsboard:
    image: thingsboard/application:1.2.3
    ports:
      - 8089:8080
      - 1883:1883
      - 5683:5683/udp
    networks:
      - traefikNetwork
      - thingsNetwork

    labels:
      - traefik.backend=thingsboard
      - traefik.frontend.rule=Host:iotpilot.ddns.net
      - traefik.port=8080
      - traffic.docker.network=traefik_traefikNetwork

networks:
   traefikNetwork:
      external:
        name: traefik_traefikNetwork
   thingsNetwork:
      driver: bridge

So I think that traefik takes the ip from the first network found in networks

Thanks for your interest in Traefik 😃
This issue is closed. Please open a new issue or discuss this in :

Stack Overflow using the "traefik" tag
the Traefik community Slack channel

Hi,
I've been messing with this for WEEKS! I just added those three parameters and I think it help traefik to clear up to error I had.
	--label traefik.backend.loadbalancer.method="wrr" \
	--label traefik.backend.loadbalancer.swarm="true" \
	--label traefik.weight="10" \

All attributes

part of my docker service create ...

	--label traefik.frontend.rule="Host:$ENV_DOMAIN_LEV_1;PathPrefix:/$ENV_DOMAIN_LEV_2" \
	--label traefik.backend="$CTN_ghost_app" \
	--label traefik.port="2368" \
	--label traefik.docker.network="$NTW_FRONT" \
	--label traefik.frontend.entryPoints="https,http" \
	--label traefik.backend.loadbalancer.method="wrr" \
	--label traefik.backend.loadbalancer.swarm="true" \
	--label traefik.weight="10" \

Screenshot

@pascalandy The issue tracker is for reporting bugs and feature requests only, it's for reduce the noise.

The knowledge is getting lost and I had experience where my question are getting completely bypassed by the flow of other conversations.

You are completely true and we know the problem of "memory" in Slack, it's for that we trying to redirect to StackOverflow  as much as possible. And it's also what we created https://awesome.traefik.io.
We always enjoy your contributions and we hope you add your repositories to https://awesome.traefik.io.

People in this thread are reporting a bug actually, but you ask us to go on Slack / SO. That's why I feel confuse.
Thanks for reminding me :)

We always enjoy your contributions and we hope you add your repositories to https://awesome.traefik.io.


[FEATURE] Analytics | Add Functionality For Download Button

Detailed description
Right now this button is not doing anything :
[FEATURE] Analytics | Add Functionality For Analytics Page
Context
I was thinking it could save the different graph data from this page for example.
Possible implementation
No response
Additional information
No response
Code of Conduct

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

@kabir0x23 do we have in backend option to download pdf files?

@kabir0x23 do we have in backend option to download data as pdf files?

we dont have anything in backend for now, we can skip this or add sampledata.cve file or json
with data we have mentnioend
actually that dowload button will download our analytics data, we can create. a function to create a json or cve file data with dummy data we have

we dont have to have a file to download,
click on download button (data -> file(cve/json))

@kabir0x23 do we have in backend option to download data as pdf files?

we dont have anything in backend for now, we can skip this or add sampledata.cve file or json
with data we have mentnioend
actually that dowload button will download our analytics data, we can create. a function to create a json or cve file data with dummy data we have

Sounds good I will create a function that creates CVS file with the data and download it.

@kabir0x23  Hey are you ok with me adding react-csv library for the file creation?

yes we can, it is safe library we can go with it


Docs: OpenAPI spec incorrectly mentions teamId instead of slug

What is the improvement or update you wish to see?
The OpenAPI spec for Turbo found here - https://turbo.build/api/remote-cache-spec mentions the use of teamId as a query parameter in most of it's routes.

I was updating my own custom remote cache server to comply with the API spec, however the actual requests made by the turbo client do not match what is specified in the OpenAPI spec for teamId.
Is there any context that might help us understand?
I'm running turbo version 1.13.2
The environment variables given to turbo are
TURBO_TEAM=team_my_team_name
TURBO_API=http://localhost:8787
TURBO_TOKEN=SECRET
TURBO_REMOTE_CACHE_SIGNATURE_KEY=SECRET

The docs mention the use of teamId query parameter, however, in actuality, the turbo client uses the slug parameter.
We can see this behavior through the warnings generated
 WARNING  failed to contact remote cache: Error making HTTP request: HTTP status client error (400 Bad Request) for url (http://localhost:8787/v8/artifacts/99469f3053174e08?slug=team_my_team_name)

This clearly slows that the turbo client uses slug instead of teamId. I have verified this by observing API calls to my production hosted instance as well.
Does the docs page already exist? Please link to it.
No response

Apologies for the confusion, both teamId and slug are valid query params for specifying which team you are using. If you connect your repository though something like turbo link, then a team id will be saved and teamId will be used when accessing the remote cache. TURBO_TEAM uses the slug query parameter instead since it isn't a team id.
Looking into fixing this in the upstream OpenAPI spec.

Hey @chris-olszewski , thanks for confirming this 😄
Looking forward to having this updated in the OpenAPI spec.
I had another question, I know this is off topic to the current issue, so happy to open a new one if you want.
I'm wondering if you could help explain what the POST /v8/artifacts route is supposed to do.
The docs say it has this input
{
  "hashes": [
    "string"
  ]
}

and gives this as an example for output
{
  "additionalProp1": {
    "size": 0,
    "taskDurationMs": 0,
    "tag": "string"
  },
  // ...
}

The output example is super unclear, I'm really not sure what data I'm meant to be returning here. What are the additionalProp keys? Is this saying that I have to echo the metadata even to the server via the /v8/artifacts/events endpoint?
Keen to get some clarity 🙏 . This is the last unimplemented endpoint I have left for my custom server.

I just double checked and we currently don't make use of that endpoint so you will be fine not implementing it.
I will update the OpenAPI spec to omit that endpoint.

OpenAPI spec has been updated to mention slug and teamId. Still working on fully removing the POST /v8/artifacts since it's unused.

Thanks Chris.
I'm happy to close out this issue, or keep it open your other changes are synced, whatever you'd like


Alex ip/stacker switch

G'day all...
Peter Tan is still using the old stacker and desperately needs to exclude any timeslices which don't have both NBAR & PQA. This minor change only extends the stacker.py functionality with new command line options: "--complete-only" and "--levels" which provide two different ways of solving his problem.
The --complete-only switch exposes the previously existing function parameter to only include certain processing levels (now NBAR & PQA), but the level names are hard-coded and, hence, Landsat specific. I would prefer to regard this option as deprecated.
The --levels option allows a comma-separated list of level names to be specified, e.g. "NBAR,PQA" or "FC,PQA". Ideally, this should also only produce temporal stacks for the defined levels instead of doing all of them, but it doesn't yet - I may get to that later but it's not important right now. This option will ensure that the temporal stacks created for the specified levels will have identical timeslices (at least for equivalent bands which exist for all sensors).

Hi Alex,
WOfS had a similar problem and solved it by excluding "timeslices sans PQ" elements at the application code level. It was a one line "if test". Is this an option for Peter?
Why do we have tiles that lack a PQ dataset? This seems to be a QA issue that should be solved at source. Or are there circumstances that admit the absence of PQ datasets (processing delays perhaps)?
What is the status of Stacker? I thought it was deprecated in favour of the new API.
There is value in encouraging application developers to move their code to the new API ASAP. It is easier to use and will give greater insulation from future DB changes. It will also focus our collective (and limited) resources into the specification and development of the new API.
A quick look at the new API confirms that tiles can be cherry-picked based on their dataset membership. I've not tested this capability.

G'day Steve...
I think Peter Tan's development use case sits outside the ones currently supported by the API. He is the only user I am aware of who is working with temporal stacks of raw band data (generated by the Stacker) as input to CUDA processes.
I did suggest to Peter that he raise the issue with ops, but, given that ops decided to do the ingestions on the live database with no staging, it is impossible to guarantee matches across products in every timeslice.
As with the previous, equally minor, stacker update, this one is just exposing its existing functionality to the command line so users can access it. Once the new API can support everything that Peter and others are currently doing with the Stacker (like Landsat /MODIS blending) then we can let it die, but not until then.
We can either put this minor tweak in to keep Peter going, or the team will have to allocate resources to supporting his use case sooner. I don't mind either way.
Regards,
Alex.
On 1 April 2015 7:28:34 am AEDT, Steven Ring<EMAIL_ADDRESS>wrote:

Hi Alex,
WOfS had a similar problem and solved it by excluding "timeslices sans
PQ" elements at the application code level. It was a one line "if
test". Is this an option for Peter?
Why do we have tiles that lack a PQ dataset? This seems to be a QA
issue that should be solved at source. Or are there circumstances that
admit the absence of PQ datasets (processing delays perhaps)?
What is the status of Stacker? I thought it was deprecated in favour of
the new API.
There is value in encouraging application developers to move their code
to the new API ASAP. It is easier to use and will give greater
insulation from future DB changes. It will also focus our collective
(and limited) resources into the specification and development of the
new API.
A quick look at the new API confirms that tiles can be cherry-picked
based on their dataset membership. I've not tested this capability.

Reply to this email directly or view it on GitHub:
https://github.com/GeoscienceAustralia/agdc/pull/22#issuecomment-88234185

--
Sent from my mini-tablet. Please excuse my brevity and possible typos.

Has the new API been released? Last I heard (a few weeks ago) it wasn't released and didn't support datasets other than landsat, nor multiple databases (assuming a decision is taken to support this governance approach to data), and the documentation is limited to command line utilities, not the core of the API.
To my knowledge Stacker is still the only official API being supported.

+1 for the change, though not the second point:

It appears multi-sensor (and thus MODIS at the moment) safe
We need a way of notifying users of the change in behavior of --complete only so it no longer defaults its use to Landsat. Perhaps a deprecation warning should popup when this is used?

The operation of the "--complete-only" switch is (still) Landsat specific, but I left the functionality in there just in case somebody was using it. I'm happy to kill it off if people think I should - it's unlikely that anyone will complain and they can always switch to using the new "levels" parameter of the stack_tiles function instead.
The "levels" parameter to the stack_tiles function and the corresponding "--levels" command line option is sensor-agnostic - that's why I added it and used that to feed the same  filtering function rather than the hard-coded processing level names of NBAR and PQA.
On 1 April 2015 9:09:38 am AEDT, Rob Woodcock<EMAIL_ADDRESS>wrote:

+1 for the change, though not the second point:

It appears multi-sensor (and thus MODIS at the moment) safe
We need a way of notifying users of the change in behavior of
--complete only so it no longer defaults its use to Landsat. Perhaps a
deprecation warning should popup when this is used?

Reply to this email directly or view it on GitHub:
https://github.com/GeoscienceAustralia/agdc/pull/22#issuecomment-88267942

--
Sent from my mini-tablet. Please excuse my brevity and possible typos.

Hi Alex,
NCI is down for maintenance today, I will test the new stacker tomorrow when NCI service resume. Thanks for updating the stacker.
Cheers,
Peter
From: Alex Ip<EMAIL_ADDRESS>Sent: Wednesday, 1 April 2015 9:22 AM
To: GeoscienceAustralia/agdc
Subject: Re: [agdc] Alex ip/stacker switch (#22)
The operation of the "--complete-only" switch is (still) Landsat specific, but I left the functionality in there just in case somebody was using it. I'm happy to kill it off if people think I should - it's unlikely that anyone will complain and they can always switch to using the new "levels" parameter of the stack_tiles function instead.
The "levels" parameter to the stack_tiles function and the corresponding "--levels" command line option is sensor-agnostic - that's why I added it and used that to feed the same filtering function rather than the hard-coded processing level names of NBAR and PQA.
On 1 April 2015 9:09:38 am AEDT, Rob Woodcock <notifications<EMAIL_ADDRESS>wrote:

+1 for the change, though not the second point:

It appears multi-sensor (and thus MODIS at the moment) safe
We need a way of notifying users of the change in behavior of
--complete only so it no longer defaults its use to Landsat. Perhaps a
deprecation warning should popup when this is used?

Reply to this email directly or view it on GitHub:
https://github.com/GeoscienceAustralia/agdc/pull/22#issuecomment-88267942

--
Sent from my mini-tablet. Please excuse my brevity and possible typos.
—
Reply to this email directly or view it on GitHubhttps://github.com/GeoscienceAustralia/agdc/pull/22#issuecomment-88270239.
Geoscience Australia Disclaimer: This e-mail (and files transmitted with it) is intended only for the person or entity to which it is addressed. If you are not the intended recipient, then you have received this e-mail by mistake and any use, dissemination, forwarding, printing or copying of this e-mail and its file attachments is prohibited. The security of emails transmitted cannot be guaranteed; by forwarding or replying to this email, you acknowledge and accept these risks.

Looks good. +1 from me.


Ability to Edit Existing Vera Devices?

ENHANCEMENT REQUEST:
Any chance you can add the ability to edit existing Vera Devices and scenes?  It would be easier to troubleshoot a device by editing it, rather than deleting and re-creating it.

In the configuration tab next to your created device, hit the Edit/Copy button.....

Ah yes, I was on the Vera tab.  Thanks.
From: BWS Systems<EMAIL_ADDRESS>Sent: Friday, May 06, 2016 12:39 PM
To: bwssytems/ha-bridge<EMAIL_ADDRESS>Cc: Sean P. Ford<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [bwssytems/ha-bridge] Ability to Edit Existing Vera Devices? (#109)
In the configuration tab next to your created device, hit the Edit/Copy button.....
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHubhttps://github.com/bwssytems/ha-bridge/issues/109#issuecomment-217493303


changing fps in the config file doesn't seem to work

I added:
mpf-mc:
  fps: 60

Yet the log still reported fps of 30, so need to see if that's a logging issue or it's not being set right or what.

fixed


How to close the popover by pressed a close button in body Widget?

something like this
Widget _test(){
 return OutlinedButton(
        child: Text("close this popover"),
        onPressed: () {
           // close this popover
          // ....?
        }
  )
}

Widget _show(){
  return GestureDetector(
      onTap: () {
        showPopover(
            width: ScreenUtil.getScreenW(context),
            context: context,
            radius: 0,
            arrowHeight: 0,
            arrowWidth: 0,
            bodyBuilder: (context) =>  _test(counter));
   })
}

Having the same issue around here...
Any updates?

Working with Tyemy Kuga she realized that this packages uses a route to show the tooltip.
So we can call Navigator.of(context).pop(); to close it.
All credits to Tyemy 🚀

Thanks to everyone. Closing it.


Automate the building process

This should now be implemented and on the main branch. It works such that when a push/merge happens on the main branch, the project gets built and released on TestPyPi. Afterwards you can test the package, and if it runs well you can run another github action, which will build and release on PyPi automatically.


Install permissions for SQL account

The current documentation states that SA in SQL server is required so that it can create a login in the SQL instance. This does not adhere to least privilege principles. Instead, this account only needs to be granted access to dbcreator and securityadmin roles. I updated the SQL permissions in the section "Install required components"

Hi @DamianWiese, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no contribution license agreement is required at this point. Real humans will now evaluate your PR.

TTYL, AZPRBOT;

@DamianWiese - thanks very much for your contribution!
@billmath - Damian is a MSFT employee. Can you review and LMK if you're OK with merging? Thanks!

Verifying the technical accuracy with the PM.

It is currently not supported to not use SA, so this would be a DCR and not just a doc update.  At this point, the PR needs to be declined.

Closin per @billmath .


Why SubscribeImmediate

Hello,
I still do not understand why you have SubscribeImmediate when you depend on HotStream.Subscribe which already propagates the current value? This was problematic for us in that we had to rewrite a bunch of combinators that wouldn't push extra values to the back end...

Indeed, I think previously HotStream didn't always propagate the current value. SubscribeImmediate is now obsolete, I marked it as such and made its implementation equivalent to Subscribe.


Contributing to Indic Acceleration

hey sphinx,
count me in for Indic Acceleration. can leverage my mechanical and programming skills to build stuff that can make India a better place.
unable to dm, create a pr, hence creating an issue 🙂

Can please check again? There are PRs raised such as https://github.com/protosphinx/in/pulls?q=is:pr+is:closed+
Let's sync again if that does not help


Pre-populating the Deposit Max Amount

Deposit Max Amount should be prepopulated in the Dialog to make the process of depositing quicker, currently this is a slow experience requiring the user to enter an amount. Ideally this popup should be an advanced feature and the default flow should be a simple button as it was before to deposit the Max voting power to participate in the respective Governance

@asktree this update fixes UI/UX issues with depositing tokens to a governance, although this is a button should have been pushed as in an advanced menu in the "My Governance Power" and not exposed for regular users who would like to quickly deposit and participate in Governance:

Added Max helper button amount
Set default input to have the max amount (as it is typically intended by the user to deposit the entire amount to governance)
Label prop was moved outside the input field to support a Max button

This should improve the experience significantly so users are not guessing the amount they have as a balance while in this prompt

The intended UX is that the max is a placeholder, and hitting confirm without any value entered would use it. It's just an oversight in the code that this isn't the case. However, it seems like this intended UX wasn't very obvious. I'm going to fix this bug in another PR quickly. I think the ideal UI would be a 1% to 100% slider, with a text entry box.

Default should be set to Max, this PR resolves the issue immediately until you push your changes


AI recall/call button should be removed on action

Description

It looks unintended when its an intended feature
Screenshots

Intended, the console can be disabled by crew, the action menu cannot

Intended, the console can be disabled by crew to avoid AI interference, the action menu cannot
source: #31852

the button should be entirely removed then, otherwise it feels like a bug.

the button should be entirely removed then, otherwise it feels like a bug

Wyci
(Ill try to look into it)

In 13, AI evac shenanigans are prevented by allowing it to always call but never recall, so it can’t force crew to stay, but can still start the timer if the station is majorly damaged and nobody can get to a working comms console. This should probably implemented here instead of just hiding the button entirely.


Customer request: support multiple node-pools

We've received a couple of requests for supporting multiple node-pools.
Currently, when you create an OKE cluster, the driver only supports configuring a single node-pool for workers.
https://github.com/rancher/terraform-provider-rancher2/issues/634

@jlamillan  - Is there an update on when this will be available?