Web server error logs in 0.35

These are some of the error logs I am seeing in 0.35. Also streaming updates option from the sidebar is no longer there.
16-12-18 14:21:13 aiohttp.server: Error handling request Traceback (most recent call last):   File "/home/hass/.homeassistant/deps/aiohttp/web_server.py", line 61, in handle_request     resp = yield from self._handler(request)   File "/home/hass/.homeassistant/deps/aiohttp/web.py", line 249, in _handle     resp = yield from handler(request)   File "/usr/lib/python3.4/asyncio/coroutines.py", line 143, in coro     res = yield from res   File "/usr/lib/python3.4/asyncio/coroutines.py", line 143, in coro     res = yield from res   File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/http/__init__.py", line 415, in handle     result = yield from result   File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/api.py", line 123, in get     payload = yield from to_write.get()   File "/usr/lib/python3.4/asyncio/queues.py", line 186, in get     return (yield from waiter)   File "/usr/lib/python3.4/asyncio/futures.py", line 388, in __iter__     yield self  # This tells Task to wait for completion. concurrent.futures._base.CancelledError 16-12-18 14:21:15 homeassistant.core: Error doing job: Task exception was never retrieved Traceback (most recent call last):   File "/usr/lib/python3.4/asyncio/tasks.py", line 237, in _step     result = next(coro)   File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/helpers/entity_component.py", line 335, in _async_process_entity     new_entity, self, update_before_add=update_before_add   File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/helpers/entity_component.py", line 204, in async_add_entity     yield from entity.async_update_ha_state()   File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/helpers/entity.py", line 229, in async_update_ha_state     device_attr = self.device_state_attributes   File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/zwave/__init__.py", line 606, in device_state_attributes     battery_level = self._value.node.get_battery_level()   File "/srv/hass/hass_venv/lib/python3.4/site-packages/openzwave-0.3.1-py3.4.egg/openzwave/command.py", line 284, in get_battery_level     for val in self.get_battery_levels():   File "/srv/hass/hass_venv/lib/python3.4/site-packages/openzwave-0.3.1-py3.4.egg/openzwave/command.py", line 306, in get_battery_levels     type='Byte', readonly=True, writeonly=False)   File "/srv/hass/hass_venv/lib/python3.4/site-packages/openzwave-0.3.1-py3.4.egg/openzwave/node.py", line 440, in get_values     for value in self.values: RuntimeError: dictionary changed size during iteration 16-12-18 14:21:17 homeassistant.core: Error doing job: Task exception was never retrieved Traceback (most recent call last):   File "/usr/lib/python3.4/asyncio/tasks.py", line 237, in _step     result = next(coro)   File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/helpers/entity_component.py", line 335, in _async_process_entity     new_entity, self, update_before_add=update_before_add   File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/helpers/entity_component.py", line 204, in async_add_entity     yield from entity.async_update_ha_state()   File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/helpers/entity.py", line 229, in async_update_ha_state     device_attr = self.device_state_attributes   File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/zwave/__init__.py", line 606, in device_state_attributes     battery_level = self._value.node.get_battery_level()   File "/srv/hass/hass_venv/lib/python3.4/site-packages/openzwave-0.3.1-py3.4.egg/openzwave/command.py", line 284, in get_battery_level     for val in self.get_battery_levels():   File "/srv/hass/hass_venv/lib/python3.4/site-packages/openzwave-0.3.1-py3.4.egg/openzwave/command.py", line 306, in get_battery_levels     type='Byte', readonly=True, writeonly=False)   File "/srv/hass/hass_venv/lib/python3.4/site-packages/openzwave-0.3.1-py3.4.egg/openzwave/node.py", line 440, in get_values     for value in self.values: RuntimeError: dictionary changed size during iteration 16-12-18 14:21:39 homeassistant.components.zwave: zwave not ready after 30 seconds, continuing anyway 16-12-18 14:53:20 aiohttp.server: Error handling request Traceback (most recent call last):   File "/home/hass/.homeassistant/deps/aiohttp/web_server.py", line 61, in handle_request     resp = yield from self._handler(request)   File "/home/hass/.homeassistant/deps/aiohttp/web.py", line 249, in _handle     resp = yield from handler(request)   File "/usr/lib/python3.4/asyncio/coroutines.py", line 143, in coro     res = yield from res   File "/usr/lib/python3.4/asyncio/coroutines.py", line 143, in coro     res = yield from res   File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/http/__init__.py", line 415, in handle     result = yield from result   File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/api.py", line 123, in get     payload = yield from to_write.get()   File "/usr/lib/python3.4/asyncio/queues.py", line 186, in get     return (yield from waiter)   File "/usr/lib/python3.4/asyncio/futures.py", line 388, in __iter__     yield self  # This tells Task to wait for completion.   File "/usr/lib/python3.4/asyncio/tasks.py", line 286, in _wakeup     value = future.result()   File "/usr/lib/python3.4/asyncio/futures.py", line 269, in result     raise CancelledError concurrent.futures._base.CancelledError 16-12-18 16:55:23 aiohttp.server: Error handling request Traceback (most recent call last):   File "/home/hass/.homeassistant/deps/aiohttp/web_server.py", line 61, in handle_request     resp = yield from self._handler(request)   File "/home/hass/.homeassistant/deps/aiohttp/web.py", line 249, in _handle     resp = yield from handler(request)   File "/usr/lib/python3.4/asyncio/coroutines.py", line 143, in coro     res = yield from res   File "/usr/lib/python3.4/asyncio/coroutines.py", line 143, in coro     res = yield from res   File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/http/__init__.py", line 415, in handle     result = yield from result   File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/api.py", line 123, in get     payload = yield from to_write.get()   File "/usr/lib/python3.4/asyncio/queues.py", line 186, in get     return (yield from waiter)   File "/usr/lib/python3.4/asyncio/futures.py", line 388, in __iter__     yield self  # This tells Task to wait for completion.   File "/usr/lib/python3.4/asyncio/tasks.py", line 286, in _wakeup     value = future.result()   File "/usr/lib/python3.4/asyncio/futures.py", line 269, in result     raise CancelledError concurrent.futures._base.CancelledError 16-12-18 18:53:38 aiohttp.server: Error handling request Traceback (most recent call last):   File "/home/hass/.homeassistant/deps/aiohttp/web_server.py", line 61, in handle_request     resp = yield from self._handler(request)   File "/home/hass/.homeassistant/deps/aiohttp/web.py", line 249, in _handle     resp = yield from handler(request)   File "/usr/lib/python3.4/asyncio/coroutines.py", line 143, in coro     res = yield from res   File "/usr/lib/python3.4/asyncio/coroutines.py", line 143, in coro     res = yield from res   File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/http/__init__.py", line 415, in handle     result = yield from result   File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/api.py", line 123, in get     payload = yield from to_write.get()   File "/usr/lib/python3.4/asyncio/queues.py", line 186, in get     return (yield from waiter)   File "/usr/lib/python3.4/asyncio/futures.py", line 388, in __iter__     yield self  # This tells Task to wait for completion.   File "/usr/lib/python3.4/asyncio/tasks.py", line 286, in _wakeup     value = future.result()   File "/usr/lib/python3.4/asyncio/futures.py", line 269, in result     raise CancelledError concurrent.futures._base.CancelledError

Streaming updates disappeared a few versions ago. It's now always streaming through to the Websocket API.

Ah, thanks!

I am also seeing these errors in 0.35.2.
16-12-19 10:09:39 aiohttp.server: Error handling request
Traceback (most recent call last):
  File "/home/hass/.homeassistant/deps/aiohttp/web_server.py", line 61, in handle_request
    resp = yield from self._handler(request)
  File "/home/hass/.homeassistant/deps/aiohttp/web.py", line 249, in _handle
    resp = yield from handler(request)
  File "/usr/lib/python3.4/asyncio/coroutines.py", line 143, in coro
    res = yield from res
  File "/usr/lib/python3.4/asyncio/coroutines.py", line 143, in coro
    res = yield from res
  File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/http/__init__.py", line 427, in handle
    result = yield from result
  File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/api.py", line 123, in get
    payload = yield from to_write.get()
  File "/usr/lib/python3.4/asyncio/queues.py", line 186, in get
    return (yield from waiter)
  File "/usr/lib/python3.4/asyncio/futures.py", line 388, in __iter__
    yield self  # This tells Task to wait for completion.
  File "/usr/lib/python3.4/asyncio/tasks.py", line 286, in _wakeup
    value = future.result()
  File "/usr/lib/python3.4/asyncio/futures.py", line 269, in result
    raise CancelledError
concurrent.futures._base.CancelledError
16-12-19 10:09:53 aiohttp.server: Error handling request
Traceback (most recent call last):
  File "/home/hass/.homeassistant/deps/aiohttp/web_server.py", line 61, in handle_request
    resp = yield from self._handler(request)
  File "/home/hass/.homeassistant/deps/aiohttp/web.py", line 249, in _handle
    resp = yield from handler(request)
  File "/usr/lib/python3.4/asyncio/coroutines.py", line 143, in coro
    res = yield from res
  File "/usr/lib/python3.4/asyncio/coroutines.py", line 143, in coro
    res = yield from res
  File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/http/__init__.py", line 427, in handle
    result = yield from result
  File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/api.py", line 123, in get
    payload = yield from to_write.get()
  File "/usr/lib/python3.4/asyncio/queues.py", line 186, in get
    return (yield from waiter)
  File "/usr/lib/python3.4/asyncio/futures.py", line 388, in __iter__
    yield self  # This tells Task to wait for completion.
  File "/usr/lib/python3.4/asyncio/tasks.py", line 286, in _wakeup
    value = future.result()
  File "/usr/lib/python3.4/asyncio/futures.py", line 269, in result
    raise CancelledError
concurrent.futures._base.CancelledError
16-12-19 10:15:56 aiohttp.server: Error handling request
Traceback (most recent call last):
  File "/home/hass/.homeassistant/deps/aiohttp/web_server.py", line 61, in handle_request
    resp = yield from self._handler(request)
  File "/home/hass/.homeassistant/deps/aiohttp/web.py", line 249, in _handle
    resp = yield from handler(request)
  File "/usr/lib/python3.4/asyncio/coroutines.py", line 143, in coro
    res = yield from res
  File "/usr/lib/python3.4/asyncio/coroutines.py", line 143, in coro
    res = yield from res
  File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/http/__init__.py", line 427, in handle
    result = yield from result
  File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/api.py", line 123, in get
    payload = yield from to_write.get()
  File "/usr/lib/python3.4/asyncio/queues.py", line 186, in get
    return (yield from waiter)
  File "/usr/lib/python3.4/asyncio/futures.py", line 388, in __iter__
    yield self  # This tells Task to wait for completion.
  File "/usr/lib/python3.4/asyncio/tasks.py", line 286, in _wakeup
    value = future.result()
  File "/usr/lib/python3.4/asyncio/futures.py", line 269, in result
    raise CancelledError
concurrent.futures._base.CancelledError


Check tty in ProgressBar#terminate

Could you add a test/tty.test.js file or similar that tests for these cases?

A stream that is not a TTY
A scenario where process.stderr is not set

Were there already tests in place, I would have added some, but since the project itself has no tests (somewhat to my surprise), I don't feel like this is the patch to add them. I don't have any idea what the author wishes to use for test and assertion libraries, and while I might be game, I don't think it's my job to take this project from being "test-free" to tested. If you'd like to set up some sort of test framework I will be happy to add tests to the patch or via another.

Haha okay, if you say so. :-)
There's no need for a test framework and for assertions there is a library in Node core.
The tests serve a purpose as to let me see where you are getting with a pull requests like this and checks for whether or not the stream is set. Why would you add a check to the value of this.stream when this.stream is the result of options.stream || process.stderr -- are you expecting this to fail and process.stderr be falsy? In that case I would like to see a test case where this happens. That's all :)

You're right, I wasn't considering that the if-case also was covered by the || case. Initially I had written/wanted to write it as an instanceof check, but fs.SyncWriteStream isn't an instance of stream.Writable, so I simplified it with the intent to possibly write a different patch with some better error checking. I'll just drop the line entirely, it doesn't add anything.

Okay. So now all we check for is that we do not call functions are TTY specific if we are not an TTY? Right?

Basically. I'm not sure they are 'TTY specific' functions so much as they are methods of the 'readline' module that get automatically(?) extended onto stdout/stderr by Node; I replicated the existing logic in this case, though I can't guarantee its efficacy.

I'm not 100% sure my self of the nature of the stdout and stderr. Streams API have changed.


[c@e] Report currently running service version in context

The currently running version of the Fastly Compute at Edge service should be available in the context passed to the main() function.
Expected Behaviour
The version of the currently deployed service should be available in the context.
Actual Behaviour
Currently this information is not available.
Platform and Version
9.3.9

Initial attempt to implement this: https://github.com/bosschaert/helix-deploy/commit/7eef5a02ea3c35eb82925aa44ab7b4e504c2fc09


Adding Kroto Plus to a project with Springfox Swagger2 causes infinite loop before start

Arrangement:
Project with a Spring Web MVC @RestController that uses a protobuf generated class as an input, and calls the same server code as the @GrpcSpringService (using https://github.com/yidongnan/grpc-spring-boot-starter). Kroto Plus configured to generate builders, message extensions, and coroutines for the service and messages defined in the proto files.
Kroto Plus version 0.6.0-SNAPSHOT was used
Expected:
Works the same as before, starts up fine with a Swagger UI.
Actual:
Fails to start, gets lost in the gRPC generated code.
Workaround:
Remove Kroto Plus, observe that it starts up again.

Thanks for submitting this issue.
So I can better understand did this application instance always serve rest and grpc controllers and only broke once introducing kroto services?
Does the start up get hung up or is there an error written to console?

So I don’t think the issue lies with spring specifically. I have a local project with kroto and spring working but without any rest controller or spring fox configured. Are you able to startup your application with the debug flag and see exactly what stage does the start up hang?
java -jar myapp.jar --debug

the start-up hangs when Springfox Swagger2 starts scanning the parameters of the REST controller- I'm running using gradlew bootRun and passing --debug unfortunately looks like it turns on debugging logs for gradle instead of java

So I can better understand did this application instance always serve rest and grpc controllers and only broke once introducing kroto services?

It always served REST and gRPC, and recently added Kroto. Then we added Swagger2 to both our services (the other one doesn't use Kroto yet).

Does the start up get hung up or is there an error written to console?

Without debug level it looks hung, but with it on, it's spewing stuff about walking gRPC classes and looks like it's in an infinite loop

Can you try again but disabling except the proto builders generator. Im want to be able to isolate which generator is creating code that hangs up spring fox. My immediate guess it the proto builders generator, specifically because it is the only one creating resources used / scanned by spring fox

Sorry, I haven't had a chance to try this yet. When I disabled the unpackBuilders option I realized I had to first remove the code that used it to even get back to where the error was. I'm just about done with that work, so I'll be able to cleanly add Kroto Plus back in afterwards in a test branch. Unfortunately it is lower priority than a few other tasks on my plate at work, so it may take a few days to get back to.

Thanks for the help debugging to issue. When you do get a chance to get back to it, you can do a static import of the builder objects so you don’t have to update the usages in your code.


WebP support by Hugo

It would be great if WebP can be supported by Hugo. So far, I only see solution like these for making WebP format render on your site. @bep one more way to make Hugo as good as JS frameworks.

We added webp support to Hugo a few months back.


✨ [REQUEST] TriliumNext

Checked

[X] If a new addon, I have checked on  Google that such as addon doesn't already exists
[X] If a new feature, I have searched in the discussions & issues that it was not already covered

Which addon?
TriliumNext
(successor of Trilium)
Is your feature request related to a problem? Please describe
No
Describe the solution you'd like
Hi,
Would be awesome to have TriliumNext as HA addon :)
It is one of the best Note apps available.
There is a docker container:
https://triliumnext.github.io/Docs/Wiki/docker-server-installation.html
Best regards
Hyper

I was looking for something similar: Affine
https://community.home-assistant.io/t/affine-notes-pkm-notion-miro-alternative/798682
Its similar in notekeeping, but offers more on the graphical aspects like flow diagrams and mindmaps.


Support for ZodString#length() validation

For schemas with ZodString#length() validation, it would be very helpful to automatically apply it to minLength and maxLength.
import { z } from "zod";
import {
    extendZodWithOpenApi,
    OpenAPIGenerator,
    OpenAPIRegistry,
} from '@asteasolutions/zod-to-openapi';

extendZodWithOpenApi(z);

const str1 = z.string().length(5);
const str2 = z.string().min(5).max(5);

const apiRegistry = new OpenAPIRegistry();

apiRegistry.registerParameter('Str1', str1.openapi({
    param: { name: 'Str-1', in: 'path' },
}));
apiRegistry.registerParameter('Str2', str2.openapi({
    param: { name: 'Str-2', in: 'path' },
}));

Currently, the above schema definitions output the following YAML:
openapi: 3.1.0
components:
  schemas: {}
  parameters:
    Str1:
      in: path
      name: Str-1
      schema:
        type: string
      required: true
    Str2:
      in: path
      name: Str-2
      schema:
        type: string
        minLength: 5
        maxLength: 5
      required: true
paths: {}

@j-murata it should now be available as part of the 4.5.0 Release


Need for speed

@duck57, I just did some refactoring on the puzzle generation code to speed things up (especially on larger puzzles and puzzles with large word counts). After doing some profiling on what was slow and making changes, I was able to increase speed by 32% percent on non-masked puzzles and 48% on masked puzzles. I thought this may be useful for your crossword generator.

@duck57, I got the speed increase up to 53% faster on non-masked puzzles and 58% on masked puzzles. I'm sure there are more places I could optimize but I think this is good enough for now. Cheers!

Good work finding those slow spots; I would not have thought of some of those changes.


[▔NEW. .SEX. .VIDEO▔]— Rida Isfahani Leaked Viral Video Original On Social Media X

20 seconds ago
L𝚎aked Video Rida Isfahani Original Video Viral Video L𝚎aked on X Twitter Telegram
🟢🔴💝➤ ➤ 🌐 CLICK HERE ➤ ➤ VIRAL LEAKED VIDEO
🟢🔴💝➤ ➤ 🌐 DOWNLOAD NOW ➤ ➤ VIRAL FULL ORIGINAL LEAKED VIDEO
Full VIDEOS Chief Baltasar Engonga Original Viral Video on Twitter
[-wATCH-]— Rida Isfahani Video Original Video Link Rida Isfahani Video Viral On Social Media X Trending Now
[-wATCH-]— Rida Isfahani ʟᴇᴀᴋᴇᴅ Video ᴠɪʀᴀʟ On Social Media ˣ ᵀʷⁱᵗᵗᵉʳ
[-wATCH-]— Rida Isfahani ʟᴇᴀᴋᴇᴅ Video ᴠɪʀᴀʟ On Social Media ˣ ᵀʷⁱᵗᵗᵉʳ
[-wATCH-]— Rida Isfahani Video Original Video Link Rida Isfahani Video Viral On Social Media X Trending Now
Rida Isfahani Original Video video took the internet by storm and amazed viewers on various social media platforms. Rida Isfahani, a young and talented digital creator, recently became famous thanks to this interesting video.
L𝚎aked Video Rida Isfahani Original Video Viral Video L𝚎aked on X Twitter
Rida Isfahani Original Video video oficial twitter
L𝚎aked Video Rida Isfahani Original Video Viral Video L𝚎aked on X Twitter..

fvgdfgfd


SAP system requirements for ADF SAP CDC connector

Regarding section "SAP system requirements"
It says that ODP is supported starting with ODP 1.0 and SAP NetWeaver 7.0 SPS 24. It might be true, but seems like ADF SAP CDC connector internally uses RODPS_REPL_CONTEXT_GET_LIST, RODPS_REPL_ODP_* functional module that are a part of ODP 2.0 (see https://help.sap.com/docs/SUPPORT_CONTENT/bwdabc/3361383574.html)
So, ODP 1.0 appears not to be supported. If it is true then the "SAP system requirement" should be updated accordingly

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 0110a5b0-432a-0d53-063a-c3f3c4d440d3
Version Independent ID: b10b4bf7-ac9e-622e-b55c-47b2258054e2
Content: Prerequisites and setup for the SAP CDC connector - Azure Data Factory
Content Source: articles/data-factory/sap-change-data-capture-prerequisites-configuration.md
Service: data-factory
Sub-service: data-movement
GitHub Login: @ukchrist
Microsoft Alias: ulrichchrist

@SergeyKalashnikovEPAM
Thanks for your feedback! We will investigate and update as appropriate.

@ukchrist
Could you please review add comments on this, update as appropriate.

@SergeyKalashnikovEPAM
Thank you for bringing this to our attention.
I've delegated this to content author @ukchrist, who will review it and offer their insightful opinions.

Updated docs to reflect dependency on ODP 2.0 API.

#please-close


Benchmarks?

I'd like to add some benchmarks to the engine. If we intend to be a serious alternative for real-time use cases, it needs to be fast so we need to know how fast it is. Also feels like a good way to learn about how the engine works for me personally.

Some things to benchmark:

"compilation" times when building the policy system (e.g, booting up the server).
Evaluation of the types that don't involve I/O.
Evaluation of functions that do involve I/O or complex processing.

I will create some basic patterns in Rego and Dogma and compare


Find swap positions by looking at 4 lines concurrently.

From https://github.com/jp7677/adventofcode/issues/5#issuecomment-751355799

Some numbers:
Day 11 - Part 1 from https://adventofcode.com/2020/day/11

benchmark name
samples
iterations
estimated

_
mean
low mean
high mean

_
std dev
low std dev
high std dev

Run rounds for part 1
100
1
194.301 ms

_
1.94452 ms
1.93969 ms
1.9526 ms

_
31.3132 us
20.0392 us
45.1801 us

Run rounds (MT) for part 1
100
1
137.956 ms

_
1.46623 ms
1.4104 ms
1.53156 ms

_
309.748 us
269.396 us
359.295 us

Day 11 - Part 2 from https://adventofcode.com/2020/day/11#part2

benchmark name
samples
iterations
estimated

_
mean
low mean
high mean

_
std dev
low std dev
high std dev

Run rounds for part 2
100
1
293.996 ms

_
2.93928 ms
2.93489 ms
2.94773 ms

_
30.6484 us
18.7071 us
44.0428 us

Run rounds (MT) for part 2
100
1
201.577 ms

_
2.09778 ms
2.03819 ms
2.17071 ms

_
335.697 us
282.775 us
399.405 us


Uncaught TypeError: Cannot read property 'offsetWidth' of undefined

[Enter steps to reproduce below:]

...
...

Atom Version: 1.2.4
System: Mac OS X 10.10.5
Thrown From: activate-power-mode package, v0.4.1
Stack Trace
Uncaught TypeError: Cannot read property 'offsetWidth' of undefined
At /Users/sid/.atom/packages/activate-power-mode/lib/activate-power-mode.coffee:126

TypeError: Cannot read property 'offsetWidth' of undefined
    at Object.module.exports.ActivatePowerMode.drawParticles (/Users/sid/.atom/packages/activate-power-mode/lib/activate-power-mode.coffee:126:35)

Commands
  4x -0:45.2.0 core:backspace (atom-text-editor.editor.is-focused)
     -0:12.1.0 command-palette:toggle (atom-pane.pane.active)
     -0:01.2.0 activate-power-mode:toggle (atom-pane.pane.active)

Config
{
  "core": {
    "themes": [
      "atom-dark-ui",
      "atom-dark-syntax"
    ]
  }
}

Installed Packages
# User
activate-power-mode, v0.4.1

# Dev
No dev packages

Activating Shadow DOM fixed for me, can @SidFeng confirm?

@frnco @SidFeng, that worked for me, I disabled it and enabled again :)


Migrate plugin documentation to github

Move plugin documentation from wiki to github
Links
https://github.com/jenkinsci/parameterized-remote-trigger-plugin/pull/72
https://github.com/jenkinsci/basic-branch-build-strategies-plugin/pull/8
https://github.com/jenkinsci/greenballs-plugin/pull/13
https://github.com/jenkinsci/rebuild-plugin/pull/65

Thanks for your contribution!
@all-contributors please add @res0nance for docs


Make sure that the property interfaceOnly is exposed

See: https://openapi-generator.tech/docs/generators/jaxrs-spec/
We already use this generator underneath. The property interfaceOnly can be exposed by the plugin. The trick here is also to update the templates to ensure that the property is considered.
Request: https://github.com/quarkiverse/quarkus-openapi-generator/issues/128#issuecomment-1310557441

Im a little confused.

We already use this generator underneath.
My understanding was that this extension uses the Java client generator, has something changed? / Can this extension also generate server stubs?
Cheers

We use the Java Client Generator from the OpenAPI Generator library. Theoretically we can generate server stubs too, but it's out of scope.
The idea behind this issue is to implement a similar behavior in the client side, so instead of generating something like this:
@Produces(MediaType.APPLICATION_JSON)
@Path("/petstore")
public class PetResource {

    @RestClient
    @Inject
    PetApi petApi;
}

We do this:
@Produces(MediaType.APPLICATION_JSON)
@Path("/petstore")
public class PetResource {

    @RestClient
    @Inject
    Response petApi;
}

@KiMurray that's what you're looking for, right?

Sorry @KiMurray. It seems to be the same as @ricardozanini is saying in his previous comment.
Am I missing something?

@ricardozanini, yes! your updated comment is exactly what we need. Had me a little confused for a moment there. 😄

@ricardozanini this issue's requirement is not very clear.
My understanding from @KiMurray's original comment is 2 requirements:

Generate server code
This could be achieved by exposing interfaceOnly, but this is out of the scope of this extension and we won't implement it.

Return Response instead of a model
Is this related with interfaceOnly? If yes, I think we shouldn't use interfaceOnly to enable/disable this, since it may confuse users and actually wouldn't describe the "return Response" feature.

interfaceOnly is just a name. As soon as we start working on the enhancement, we can develop a new name for this property.
The problem is that this property name can be used for a server side or client code gen, hence the confusion. But no, we won't generate server-side code. The requirement is to generate the Model with the Response interface instead of the actual data model.


EliqOnline Channel ID not working

Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
**Home Assistant release (hass --version):0.50.2
**Python release (python3 --version):3.6
**Component/platform:EliqOnline
Description of problem:
Code issue in api.py file:
File "/usr/lib/python3.6/site-packages/eliqonline/api.py", line 108, in get_data_now
parameters = "&channelid=%d" % channelid
TypeError: %d format: a number is required, not str
Expected:
Don't know if correct way but i have been solving it by changing it like this:
parameters = "&channelid=%d" % int(channelid)
Then it works... but this need to be done after every update as this restore original file again, so it would be nice if this issue could be fixed in source package.
Problem-relevant configuration.yaml entries and steps to reproduce:

Traceback (if applicable):

Additional info:
This is only a problem when having more than one sensor and then need to use EligOnline channelid option in configuration.yaml
This issue started already in version 0.3xx something.

What if you change this line https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/components/sensor/eliqonline.py#L33 to cv.positive_int instead?


How to decide the bandwidth?

Firstly, thank you for the great work!
As the paper mentioned The maximum frequency b is known as the bandwidth, and is related to the resolution of the spatial grid (Kostelec and Rockmore, 2007).
I notice that the bandwidth is set to 30 when you generate the new MNIST dataset. For each S2Convolution and SO3Convolution, the bandwidth is different.
I wonder how to decide the parameter bandwidth when we use S2Convolution or SO3Convolution? Is it also a super parameter (empirical value) or need to be calculated meticulously?
Why you set bandwidth = 30 when you generate the new MNIST dataset?
Thank you!

Ultimately it is a hyperparameter, similar to the spatial resolution in a planar CNN. In a planar CNN this is purely determined by by the stride of the convolutions and the pooling, but in spherical CNNs you have more flexibility: you can in principle choose the resolution freely in each layer.
There are currently no good "best practices" for spherical CNN architecture design, and this includes the bandwidth/resolution, but there are a couple of considerations that would factor into the decision:

Higher resolution means you can represent more small details
Higher resolution means higher computational cost
If you reduce the resolution too quickly, you would ignore units in the input, just like when you use 2D convolution with a stride that is larger than the filter size.
If the task is classification, you would typically start with a high resolution and gradually decrease it. The final layer can have very low resolution, and each unit has a receptive field that covers the whole input.
If the task is e.g. segmentation, you could try a U-net like architecture.

We choose bandwidth=30 because it's not too large, but still allows us to represent MNIST digits without losing too much detail. MNIST images are 28x28, but we project them only on the top of the sphere, so using a spherical grid with 2*b=60 samples per dimension, we can represent it fairly accurately.

Thank you for your quick reply!
As the paper describes, We created two instances of this dataset: one in which each digit is projected on the northern hemisphere and one in which each projected digit is additionally randomly rotated. Why  do you just project on the northern hemisphere instead of the entire sphere?
Thank you!

Also, for VGG Net, there are some nn.MaxPool2d(kernel_size=2, stride=2) layers. Is there any implementations of MaxPool2d() operation or MaxPool3d() operation for Spherical CNN? Probably so3_integrate() is one possible solution as this issue mentioned. However can we feed the output of so3_integrate as the input of the next SO3Convolution()?  I am afraid the shape is not appropriate. Or can we directly use torch.nn.MaxPool2d / torch.nn.MaxPool3d same as standard 2D CNN?
Thank you for your suggestion.

Great thanks to your quick reply! Your work is so  fascinating!


Git tag feature

Fixes #68
Also adds the createReference op
Please @juanpedromoreno could you review? Thanks!

Codecov Report

Merging #71 into master will decrease coverage by 1.3%.
The diff coverage is 75%.

@@            Coverage Diff             @@
##           master      #71      +/-   ##
==========================================
- Coverage   80.04%   78.74%   -1.31%
==========================================
  Files          34       34
  Lines         471      795     +324
  Branches        2        4       +2
==========================================
+ Hits          377      626     +249
- Misses         94      169      +75

Impacted Files
Coverage Δ

.../main/scala/github4s/free/domain/PullRequest.scala
100% <ø> (ø)
:arrow_up:

.../src/main/scala/github4s/free/domain/GitData.scala
0% <ø> (ø)
:arrow_up:

.../main/scala/github4s/free/algebra/GitDataOps.scala
33.33% <0%> (-9.53%)
:arrow_down:

...4s/shared/src/main/scala/github4s/GithubAPIs.scala
95.55% <100%> (+0.31%)
:arrow_up:

...s/shared/src/main/scala/github4s/api/GitData.scala
100% <100%> (ø)
:arrow_up:

...cala/github4s/free/interpreters/Interpreters.scala
84.44% <33.33%> (-3.32%)
:arrow_down:

...thub4s/shared/src/main/scala/github4s/Github.scala
81.81% <0%> (-1.52%)
:arrow_down:

...ub4s/shared/src/main/scala/github4s/Decoders.scala
95.09% <0%> (-0.74%)
:arrow_down:

...src/main/scala/github4s/free/algebra/AuthOps.scala
100% <0%> (ø)
:arrow_up:

... and 30 more

Continue to review full report at Codecov.

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


DRY/Refactor hard coded config file keys

The motivation of this issue is to prevent bugs like #1645.
The Config object uses various keys for storing configuration properties. Currently many of those get populated during argument parsing (e.g. https://github.com/elastic/rally/blob/4c7141aac0179c38c08c134c25f7a23e6f07d2d9/esrally/rally.py#L1024-L1029), and the same keys are referenced, again as strings, in other code locations e.g. in metrics.py.
This approach is brittle and error prone. We should DRY things up and instead reference the config options via meaningful variable names in some module (e.g. config.py) such that a typo becomes a real error.

Hi @dliappis, I'm interested in working on this issue, can you please assign me this.
Thank you

@MadhuMPandurangi thank you for your interest. I've assigned it to you.

@dliappis I'm also interested. How about this way? I feel like I may reinvent the wheel somewhere else, though.
# erally/const.py
from collections import UserDict

class Node(UserDict):
    def __init__(self):
        super().__init__(self._iterattrs())

    def _iterattrs(self):
        attributes = vars(type(self))
        for k in attributes:
            if k.startswith('_'):
                continue
            yield k, attributes[k]

class Section(Node):
    def _iterattrs(self):
        for _, v in super()._iterattrs():
            yield v[1], v

class SectionA(Section):
    _section = "section_a"
    snake_case_key = (_section, "snake_case_key")
    dot_notation_key = (_section, "dot.notation.key")

class Root(Node):
    section_a: SectionA = SectionA()

CONFIG_PATH = Root()

With the above, (section, key) will be accessible like this:
from esrally.const import CONFIG_PATH as CFG

CFG.section_a.snake_case_key
CFG.section_a.dot_notation_key
CFG.section_a["dot.notation.key"]

So, the example code will be refactored in the following with some bonuses, such as nice code completion, pprint capability thanks to an inheritance from dict, the same line length between before and after the change, etc. In addition to those, if you prefer, we can capitalize sections and keys (or inject more magics for auto-conversion) to be able to write like *CFG.SYSTEM.LIST_CONFIG_OPTION.
 cfg.add(config.Scope.applicationOverride, *CFG.system.list_config_option, args.configuration)
 cfg.add(config.Scope.applicationOverride, *CFG.system.list_max_results, args.limit)
 cfg.add(config.Scope.applicationOverride, *CFG.system.admin_track, args.track)
 cfg.add(config.Scope.applicationOverride, *CFG.system.list_races_benchmark_name, args.benchmark_name)
 cfg.add(config.Scope.applicationOverride, *CFG.system.list_from_date, args.from_date)
 cfg.add(config.Scope.applicationOverride, *CFG.system.list_races_to_date, args.to_date)

--- a.py        2023-10-26 19:08:49.359047597 +0900
+++ b.py        2023-10-26 19:09:01.960758334 +0900
@@ -1 +1 @@
- cfg.add(config.Scope.applicationOverride, "system", "list.config.option", args.configuration)
+ cfg.add(config.Scope.applicationOverride, *CFG.system.list_config_option, args.configuration)

There'd be other ways, like using dataclass or some non-standard libraries, but I thought this is probably good enough not to overkill.

cc @elastic/es-perf

@sakurai-youhei Many thanks for your interest in making Rally better, feel free to assign this issue to yourself and contribute.
I've looked at the proposal based on UserDict. My understanding is the benefit of UserDict is the following usage: CFG.section_a["dot.notation.key"] but is this a requirement at all? I think all we need is to refer to config keys as class attributes, so perhaps there's a room for making it simpler? To be honest it took me a while to figure out what your code is doing.
I like the idea of returning tuples and unpacking them in cfg API calls. I don't like the _section repetition in the section class code.
I was thinking about something as simple as this:
class Section:
    def __init__(self, name):
        self._name = name

    def __getattribute__(self, item):
        return super().__getattribute__("_name"), super().__getattribute__(item)

class System(Section):
    def __init__(self):
        super().__init__("system")

    # description ...
    list_config_option = "list.config.option"
    # description ...
    list_max_results = "list.max_results"

class Root:
    system: System = System()

CFG = Root()
print(CFG.system.list_config_option)
print(CFG.system.list_max_results)
#print(CFG.system.does_not_exist) <--- error

with a simple path to . removal (breaking change with config file version increment):
class Section:
    def __init__(self, name):
        self._name = name

    def __getattribute__(self, item):
        return super().__getattribute__("_name"), item

class System(Section):
    def __init__(self):
        super().__init__("system")

    # description ...
    list_config_option = None
    # description ...
    list_max_results = None

I'm also curious what was your idea with the dataclass?
To move forward I would suggest to start working on a single section (the smallest, the better) to see how it goes.

@gbanasiak Thank you for your comment.
I have played my idea, your idea, dataclass, etc., more to see what would be the best, and I find enum can be used to express dot-notation straightforwardly like the PR https://github.com/elastic/rally/pull/1795.
I hope you like it, as I have also incorporated the concept of avoiding repetition and giving descriptions.

P.S. I have come to the conclusion that the literal check like this PR #1798 should come first before DRY, refactoring, auto-completion, etc.
https://github.com/elastic/rally/actions/runs/6773039463/job/18406946647?pr=1798#step:5:202

@sakurai-youhei I like this approach. I'll leave more detailed comments in each PR.


Can u change Daemon capital under DEXes into Maladex?

We changed name from daemon -> Maladex, could u update list? Thank you in advance

sure, no problem. We'll get that updated for you. Thanks for letting us know!

is this your new website? https://maladex.com/

Yes sir ;)
On Mon, Sep 20, 2021, 12:59 Niamh Ahern @.***> wrote:

is this your new website? https://maladex.com/
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/input-output-hk/essential-cardano/issues/112#issuecomment-922823853,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEG5YZBVDYYOHKJMANAQOV3UC4HXNANCNFSM5EJRN2RQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

updated for you.


Thank you for your work on this project and making it public!

No bugs to report, just wanted to thank you and tell you to keep it up!
If you have a buy me coffee or support project it would be great :)

Hello, I really appreciate my lib being useful to you!
I have setup a buy me a coffee page.
Thanks you ❤

Donated, not much but honest work! have a good day :D

I left a message @ the buymecoffee link hope you check it out 😊

I have some issues with telegram, is it possible to send me a dm on discord @n.ste ?

Mine is smol8106


Typescript

This PR dresses the library with Typescript. It also removes some tests that seem less than ideal. In particular, there are several tests that verify internal implementation (such as "proxies v1 function of uuid", etc). These tests were deemed unnecessary (and inconvenient) in light of the fact that the library interface itself is fully covered by tests.

@kurttheviking please let me know if you're interested in this and/or if there's anything that you'd like me to do to make this PR more appetizing to you :).

Bumping. I would also like to see this merged.

Note that you can also just use my fork by requiring @kael-shipman/uuid-with-v6 at version ^2.0.0. To do this, however, you must set your repo up for GitHub packages and point npm to my GitHub namespace. If you need help, i can explain more when I'm back to my computer.

Yes, I figured, thank you, but I'd rather use the npm distribution given that I'm using it in many projects. I'll wait a couple of days if @kurttheviking notices this.

Sure; let me take a look -- I haven't yet because the Travis build was complaining and it's usually easier to clean that up prior to the merge. I don't want to remove the tests though -- most of those were added in response to other bugs we found during use in live settings.

While reviewing dependencies, I noticed that npm now throws warnings that this version is depending on a very old version of uuid. If merging this PR requires too much work, would it be possible to at least loosen the dependencies?


docs: updated tutorials for Image generation and Vector Search

Description: docs: updated tutorials for Image generation and Vector Search
@lkuligin for review

@Adi8885  thanks for working on this!
Could you add a link to Imagegen documentation, please? And also add a hint that we follow the chat interface to deal with multimodality, but only single-turn chat is supported.

LGTM, thanks!


Add HinkalTest Operator

Name - hinkal_test
Short Description - for testing
Ethereum operator address - 0xd4b276Fe7a06625727947d44c99b062C0C14AB55
Validator consensus address - EC1BB5D07D73DA16BB2A0D225DA1798DB1F35A56

already registered

Done. Sorry, I somehow forgot to call this function.


Code size when using DEFMT_LOG

I was trying to figure out why my binary had gotten so huge when I realized that DEFMT_LOG is causing a massive blowup in code size.  Those 2.5KB log calls add up, fast, and my final debug binary ends up being 30% check() functions!
It looks like this code is being generated by defmt_macros::function_like::log::env_filter::path_check, which has the comment "Builds a compile-time check that returns true when module_path! can emit logs at the "requested log level". That may be true in optimized builds, but in a regular debug build this all gets compiled and executed at runtime.

This should emit a const item, not a const fn, which would guarantee compile-time evaluation

@jonas-schievink said:

This should emit a const item, not a const fn, which would guarantee compile-time evaluation

What do you think about just wrapping the current version in a const CHECK: bool? It does compile, but I don't know how to test if it actually solves the problem.
// current
if {
    const fn check() -> bool {
        if we_want_to_emit_log() {
            return true;
        }
        false
    }
    check()
} {
    emit_defmt_log();
}

// new
if {
    const CHECK: bool = {
        const fn check() -> bool {
            if we_want_to_emit_log() {
                return true;
            }
            false
        }
        check()
    };
    CHECK
} {
    emit_defmt_log();
}

I first tried to get rid of the function altogether, but this gives me an "error[E0572]: return statement outside of function body":
if {
    const CHECK: bool = {
        if we_want_to_emit_log() {
            return true;
        }
        false
    };
    CHECK
} {
    emit_defmt_log();
}

(All options are in this playground: https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=d82fe98724afa36aeb244d8d80c399ce)

It seems like it does not work. I adapted the app-template to use defmt as path dependency and collected data for the levels example, but there is no change in the code size.
That's the data:

--release
size (current)
size (new)

false
7984
7984

true
7364
7364

I collected the data like following:
# current
$ DEFMT_LOG=trace cargo build --bin levels -q && size target/thumbv7em-none-eabihf/debug/levels
   text	   data	    bss	    dec	    hex	filename
   7984	     56	   1032	   9072	   2370	target/thumbv7em-none-eabihf/debug/levels

$ DEFMT_LOG=trace cargo build --bin levels -qr && size target/thumbv7em-none-eabihf/release/levels
   text	   data	    bss	    dec	    hex	filename
   7364	     56	   1032	   8452	   2104	target/thumbv7em-none-eabihf/release/levels

# new
$ DEFMT_LOG=trace cargo build --bin levels -q && size target/thumbv7em-none-eabihf/debug/levels
   text	   data	    bss	    dec	    hex	filename
   7984	     56	   1032	   9072	   2370	target/thumbv7em-none-eabihf/debug/levels

$ DEFMT_LOG=trace cargo build --bin levels -qr && size target/thumbv7em-none-eabihf/release/levels
   text	   data	    bss	    dec	    hex	filename
   7364	     56	   1032	   8452	   2104	target/thumbv7em-none-eabihf/release/levels

The app-template uses opt-level = 3 for debug builds, did you change that to 0 before testing?

The app-template uses opt-level = 3 for debug builds, did you change that to 0 before testing?

No, I did not. Will do that now.

Okay, now there is a difference:

size (current)
size (new)
diff abs
diff %

20728
16880
-3848
-18.6%


GF180MCU w/ Simulation Tests

GF180 brought up to a same standard + simulations for all primitive components, two bugs to resolve:

[x] hdl21.netlist doesn't like the diodes for some reason.
[x] MiM capacitors seem to be broken, waiting on Slack here

So what needs to happen with this PR? Should we have all the digital cells ready, tests up to #124 standards?

Howdy, merged main into PR, CI now works.
SKY130 digital cells were added as an ease-of-use for GDSFactory... which I need to ask Joaquin about... Otherwise it would just be adding some symmetry to the PDK modules and allowing users to do what they like - which is cool but does deviate from the core mission and makes those PDK imports hefty.

Hey @curtisma, thanks for taking the time to review, I was wondering what you thought about the Mos compilation mapping on line 240 in pdk_data.py.

Ok, I'll try taking a look at that mapping tonight.
Why are more than half of the CI checks failing?

Ok, I'll try taking a look at that mapping tonight. Why are more than half of the CI checks failing?

That'd be because the latest version of vlsir distributed is 3.0.1. And all the PDK stuff needs what I call version 4.0.0 which doesn't exist on pypi yet.

Adding a few smaller comments in review, coming right up

@dan-fritchman is there also a phantom review here a-lurkin'?

Re digital cells - go for it

Okay, for this one I decided to seperate the digital cells into seperate namespaces that can be accessed a lot like modules which contains foundry primitives. This lowers the loading time and I think just makes it a little more obvious where things go.

Going to ask that we merge to main here, then you sync #148 and I'll push a couple commits to this PR to straighten out the Sky130 PDK testing issues.

#148's merged & closed, have at it

Why are the parameter names for each primitive so specific?
Why not use w and l for all of them rather than w_resistor, w_transistor?

Howdy @curtisma, sorry for the late reply, this just reflects the model definition of these components. Ideally paramclasses would be able to alias these, but for now it's WYSIWYG w.r.t. the SPICE.
Did you take a peek at that Mos compilation yet?

Yeah, can you make a comment on the section you want me to review?  I didn't see it where you last said to look.

@curtisma Good question, pdks/Gf180/gf180/primitives/prim_dicts.py at line 7, there is the definition of xtors. This dict as a key takes the common Hdl21 attributes:

model name, aka. what do we want to call our FET?
MosType, is this a pmos or an nmos?
MosFamily, what "camp" does this mosfet fall into?

I've been told that in any given PDK, you can categorize the MOSFETs into groups such as the CORE logic and higher voltage IO, I'm not sure where things should fit, we have the following Enum that we use right now:
class MosFamily(Enum):
    """# MOS Family Enumeration"""

    NONE = "NONE"
    CORE = "CORE"
    IO = "IO"
    LP = "LP"
    HP = "HP"

During Hdl21 primitive compilation, primitives are mapped to their ExternalModules using gf180.compile() which runs a lazy search over the keys in xtor and returns the first match.
So are you happy with the mapping, what would you change if not?

Right this should be ready to go, opening up for final review. :shipit:


spaces: Cleaned up eol whitespace

Simple PR for testing code review options on GitHub.
Signed-off-by: Noel Eck<EMAIL_ADDRESS>

This change is

THis is a test

Review status: 0 of 2 files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Reviewed 2 of 2 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


[5th Edition OGL by Roll20 Companion] Spell Level undefined

When casting a spell that does not have a "Cast at Higher Level" option. The api does not decrement the available spell slots.

Started to trouble shoot this issue and was unable to reproduce.


Dynamics @place and @staff possible values

The explanation of the @place attribute in the dynam element is not including the value between that is used in the last example of the section:
<dynam tstamp="1" tstamp2="2m+1" extender="true" place="between" staff="1 2">dim.</dynam>

thanks for spotting this


Add info: Deployed on Kovan

Just FYI and for the doc, I deployed this contract on Kovan: 0xa7bd1E08df70855654aDae825b81CA3481b4e8B3

Need the contract to be verified if you want it listed.


go/types: guarantee that a finite number of distinct instances are reachable via the API

In #52715, we see an example of unexpanded types escaping type-checking, that result in an infinite number of reachable types when interrogated via Underlying (though only a finite number of identical types).
It would be nice if we could avoid such infinite expansion, as it is bound to cause problems for our users (see e.g. https://go.dev/cl/404335). One way to achieve this would be to provide wrappers for Underlying and Method that accept a Context. Another option would be to enforce that unexpanded types do not escape the API, though this can result in a lot of unnecessary work when underlying types or instance methods are not needed.
CC @griesemer @adonovan @mdempsky

Just to add a bit more context:
Laziness serves at least three purposes:

To avoid type expansion before underlying types are fully set-up.
To avoid infinite recursion in the type checker.
To avoid inefficiency due to generic types that expand enormously. The way I think about this is: we want type checking to scale with the source being type-checked, not the expanded source after instantiating.

Of these:

(1) is convenient but can lead to subtle bugs. We've seen this in the past with interface completion, and are seeing it now with type expansion (e.g. https://go.dev/issue/52529). We should probably work toward a more phased approach to type construction.
(2) probably shouldn't be necessary any more, with our checks for monomorphizability and infinite expansion.
(3) is a real concern, and an argument for preserving laziness.

With regard to point 3 it would be interesting to think about how many clients of the type-checker end up having to expand generic types, anyway.
Since #52715 spawned this conversation, I'm also curious how the type-checker, which itself needs to know method sets, can avoid expanding types?

With regard to point 3 it would be interesting to think about how many clients of the type-checker end up having to expand generic types, anyway.

Yes, this is a good point. I would guess that in some clients (such as gopls) most types get expanded anyway.

I'm also curious how the type-checker, which itself needs to know method sets, can avoid expanding types?

The type-checker expands types whenever necessary. It just so happens that the method set is not needed in the example in question:
https://go.dev/play/p/hmJjiNWzm9G

CC @timothy-king as well.
The more I think about this, the more I think it was just a mistake not to guarantee that reachable types are always finite. Because of instantiation we can't guarantee that instances are canonical, but we can guarantee that they are finite.
I think there's actually a way to achieve this lazily, without pinning a (full) types.Context. Right now during the type-checking pass we avoid type duplication during e.g. calls to Underlying by pinning a *Checker to the Named type. This allows us to use a regular API, but still share state during expansion. However, at the end of type-checking we nil-out the *Checker to avoid unnecessarily pinning memory to the created types.
It occurred to me that we can do something similar during lazy expansion, even if we don't have a *Checker available. We already create a new context during expansion. I would propose that we save that *Context to the Named type and any instances created during its expansion. We can nil it out when we detect that the *Named type is fully expanded, because it won't be necessary anymore.
In other words, we introduce a new invariant. Exactly one of the following hold for a named type N:

N is fully expanded, meaning its underlying and all methods have been instantiated.
N has a pinned *Checker
N has a pinned *Context

As a result of this change, we would guarantee that any instance reachable from N shares a context with N. In the specific example of #52715, it would work as follows:

<Tree[int]> would initially have a pinned *Checker.
When we clean up after type-checking, we replace the *Checker with a *Context containing exactly one instance (<Tree[int]>), which we can call C. (N.B. we could probably create this context upon the first expansion, but for simplicity of the invariant let's assume that it is created now).
When we call NewMethodSet, we access <Tree[int]>.Underlying(), which triggers an expansion and creation of Node[int]. We save C as the context of <Node[int]>. C now has two instances: <Tree[int]> and <Node[int]>.
We then access <Node[int]>.Underlying() for the <Node[int]> instance above. Since it has C pinned, it finds (and re-uses) <Tree[int]>.

In other words, each instance is expanded in a shared *Context. During type-checking, this is shared across the package. After type-checking this is shared across a "lineage", starting with the first type that was expanded. It's still possible to have identical named types with different pointer identity, but there will be a finite set of such types. While expanding it's true that this lineage grows, but anyway its maximum size is proportional to the number of types that would be created if we were to expand eagerly. This seems like a reasonable compromize.

This seems like it could work. Worth a try.

This seemed to work out well in the associated stack of CLs, but of course these sorts of changes require great care. It is possible that I will land this stack on Monday (within the parameters of the freeze grace period, since the stack was mailed before the freeze), but even if I don't I think this is a sufficiently severe problem that it warrants being made a release blocker for 1.19.  I am not sure if it should be back-ported to 1.18, since the fix is not small and the problem with NewMethodSet and LookupFieldOrMethod has been avoided.

Checking in on this as it's currently blocking beta 1. Any updates? Thanks.

This has been implemented. The number of changes is significant, so we're not sure yet whether this should go in or not.

Update: We will try to land this by Monday (pending availability of @findleyr).


Fixed chunker chunk length calculation

What kind of change does this PR introduce?
Bug fix
What is the current behavior?
Cookie is too large
Value not encoded before splitting.
Sometimes, this causes too big chunks because the encoded cookie value length is longer than not encoded.
What is the new behavior?
Added splitting by encoded value

Thank you for this PR. We just need to test it out and make sure the unit tests for the chunker is still passing and then we can get this merged in.

Unit tests are failing on this change, the chunk length returned is always 1 which cannot be correct.

@silentworks
Changed regexp back, now tests are passing
Sorry that haven't checked the tests in the first commit.

@silentworks
Added test for encoded string and fixed bug in my code

@dvvolynkin you've made too many logic change in this code, please revert the logic to what it was before as your changes are complicating the code.

@silentworks okay
I revert all logic of chunker and leave a test that is not passing.
You can implement a logic in your style.

Cookie value should be splitted into chunks that length can fit 4096 symbols after encoding.
If you use the initial regexp on the encoded string then you will face that your chunks can be broken because of % sequence.

hi @dvvolynkin, thanks for working with @silentworks to hash out the possible solutions we can take to chunk the cookies correctly. just an update, we've decided to go with this approach: https://github.com/supabase/auth-helpers/pull/726 so i'll be closing this PR


How do i configure the connection in Visual Basic?

I'm a beginner in programming, a friend showed me some Things and i got to a Point were i couldn't get any further. My problem is now that i can't set the configuration in Visual Basic. Is it even possible?
(Sorry if my english is bad ._.)

`    Private Shared _spotify As SpotifyLocalAPI
Public Shared Sub Main(ByVal args As String())
    _spotify = New SpotifyLocalAPI()
    If Not SpotifyLocalAPI.IsSpotifyRunning() Then Return
    If Not SpotifyLocalAPI.IsSpotifyWebHelperRunning() Then Return
    If Not _spotify.Connect() Then Return
    Dim status As StatusResponse = _spotify.GetStatus()
End Sub
Public Class Auth
    Public Shared Async Sub Main()
        Dim _spotify As New SpotifyAPI.Web.SpotifyWebAPI

        Dim webApiFactory As New WebAPIFactory("http://localhost", 4371, "1a5217eb07f44d29a3851b03ccf9b265", Scope.UserReadPrivate Or Scope.UserReadEmail Or Scope.PlaylistReadPrivate Or Scope.UserLibraryRead Or Scope.UserReadPrivate Or Scope.UserFollowRead Or Scope.UserReadBirthdate Or Scope.UserTopRead)
        Try
            _spotify = Await webApiFactory.GetWebApi()
        Catch ex As Exception
            MessageBox.Show(ex.Message)
        End Try

        If _spotify Is Nothing Then
            Return
        End If
    End Sub
End Class`

This is the Code where it should connect to Spotify, well if didnt do something wrong


[#769] Refactor getters for design tokens

Fixes #769
Changes

Adds design-token.get() sass function
Replaces size.get(), palette.get(), shadow.get(), line-height.get(), custom-property.get(), and font-size.get() uses with the unified design-token.get
Uses var() at the point of use instead of as part of the outp[ut (as was specified in the issue), because it seems more transparent and expected
Animation $transition variables are now a map just like the other design tokens, and all uses of the transition variables now use the CSS custom properties for those, matching the other design tokens
Divides the design tokens into primary & secondary to avoid issues with Sass modules (@using the design tokens in tools/design-token in order to allow validation of a design token’s existence was causing import loops when design-tokens.get() was used in the design-tokens files themselves. Now primary design tokens can’t use the design-token.get() helper)

How to QA
👀 Visual changes
No visual changes
👾 Code changes
Check:

[ ] The documentation is correct, understandable, and up-to-date.

Preflight checks

[x] Storybook documentation has been updated
[x] Fixtures in test/scss/ have been updated
[x] Your changes have been added to the unreleased section of CHANGELOG.md

Still TODO:

[ ] Update docs for all each of the design tokens (some done, but check they reflect the current status
[ ] Update the design token overview to reflect the requirements to divide into primary/secondary design tokens


Current sessions in Memcache + Datastore

The goal is to secure the Target ID : it should be unique.
Or find a way with Pusher (listener count, etc.).

Closely related to #54

b7a956d

See also issue #77 for some Pusher facilities

Undone per #108 : f6a8209248e
All code removed.


Add trigger_build API

The API to execute a trigger is not documented on the same page as the
rest of the trigger management API, but this seems the most appropriate
place for it.
The trigger method has been renamed to trigger_detail to prevent
confusion as to its behaviour, it retrieves details about a trigger, and
doesn't cause a trigger to be activated.

Actually, after a second look at this patch, I think I've implemented it and the tests incorrectly. Will revise it.

I'm working on rebasing this to the v4 API.

I have rebased this PR onto the patch in #275, and updated it to be compatible with API v4.

@edgemaster I think I'll just close #275 and merge this one.  If I merge #275 I'm pretty sure there will be a conflict because there will be a merge commit between the two commits listed here.

Oh neat, it auto closed #275 when I merged this PR.


Samples all point to one giant index.html

Is this a joke? How are people supposed to actually use these modal if we have to dig through your giant index.html just to see how it's implemented...

Not a joke. Currently I am not working on any Angular 1 projects, so any time spent on this is 100% for the community. Closing this issue in favour of https://github.com/dwmkerr/angular-modal-service/issues/73, where I will note that smaller files would be an improvement too.


Integrate with dms-vep pipeline

Is it possible to integrate this with dms-vep (presumably not hard because it only needs avg escape files and site references that we already have), so that we could get the .json files thought there as opposed to needing to run a separate pipeline.

I think this is a good idea, but I'm going to move this over to the configure_dms_viz repository.


windows: '~' Home reference bug

Prerequisites

[X] Write a descriptive title.
[X] Search the existing issues.
[X] Make sure you are able to repro it on the latest released version
[X] Refer to the FAQ.
[ ] Refer to Differences between Windows PowerShell 5.1 and PowerShell.

Steps to reproduce
when i update PowerShell in my windows 11 workstation version to 7.4.0 below is version
$ $PSVersionTable
Name                           Value

PSVersion                      7.4.0
PSEdition                      Core
GitCommitId                    7.4.0
OS                             Microsoft Windows 10.0.22621
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0
when i use the ~ to refer my work home, that may conjunct with current path; at old version that method like resolve ~ to $HOME environment variation.
Hope can resolve this problem. thanks
Expected behavior
ps> more ~\test
1

Actual behavior
# xxxxxx @ SHC5CG33131WZL in ~\AppData\Local\Temp\tmphcnstt.tmp [18:41:39]
$ more ~\test
Cannot access file C:\Users\xxxxxx\AppData\Local\Temp\tmphcnstt.tmp\~\test

Error details
No response
Environment data
Name                           Value
----                           -----
PSVersion                      7.4.0
PSEdition                      Core
GitCommitId                    7.4.0
OS                             Microsoft Windows 10.0.22621
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Visuals
No response

My understanding is the implementation of tilde expansion is Linux/macOS specific.
https://github.com/PowerShell/PowerShell/issues/20754

Curious. It works for type and Get-Content, but not more.
Is it really using more.com?
c:\windows\system32\more.com

It looks like you found the issue when using an external command.
I suggest this is not a bug because C:\WINDOWS\system32\cmd.exe does not expand tilde so existing native commands are not designed to handle that expansion.

it actually use more.com in powershell, and it still not work in such like
code.exe(vscode) --diff
This kinds of extend command that need path as parameters.
So have u fix it or add this feature?

So have u fix it or add this feature?

I suggested

Work around, if you mean $HOME in PowerShell then use $HOME.

it actually use more.com in powershell

If you about powershell.exe you are confusing a function with an application
Get-Command more*

CommandType     Name                                               Version    Source
-----------     ----                                               -------    ------
Function        more
Application     more.com                                           10.0.22... C:\WINDOWS\system32\more.com

PowerShell Core does not have the function
PowerShell 7.4.0
PS> Get-Command more*

CommandType     Name                                               Version    Source
-----------     ----                                               -------    ------
Application     more.com                                           10.0.2262… C:\WINDOWS\system32\more.com

To summarize:

On Windows, ~ is only recognized by the provider cmdlets, such as Get-Content and Get-ChildItem (there it refers to the home location of the provider underlying the current location; for the FileSystem providers, that is $HOME, i.e. the current user's home directory (same as $env:USERPROFILE on Windows).

External programs - such as more.com or code - do not understand ~ and - unlike on Unix-like platforms - PowerShell performs no translation of ~ to the value of $HOME behind the scenes.

See https://github.com/PowerShell/PowerShell/issues/20750#issuecomment-1822843581 for a discussion about possibly changing that.

In Windows Powershell more ~\test happened to work, because there more refers to a PowerShell function by that name (run $function:more to see its body) that wraps more.com and passes the file-path argument to Get-Content, which, as stated, does  understand ~.

Because this function was removed in PowerShell Core, more ~\test now passes ~\test directly to more.com, which therefore fails (because more.com doesn't understand ~).

Up to v7.3 you could use tab-completion to work around that problem, as tab-completing a ~-prefixed path would instantly convert ~ to the value of $HOME - this was changed in 7.4.0; again, see #20750

~ is not converted if quoted.

The  behaviours are the same on Linux
bash
$ /bin/echo ~ '~' "~"
/home/bythesea ~ ~

PowerShell
PS> /bin/echo ~ '~' "~"
/home/bythesea ~ ~

The behaviours are the same on Linux

This means pwsh for Windows has intentionally disabled this feature.

This means pwsh for Windows has intentionally disabled this feature.

Yes, the interpretation of ~ in PowerShell is Linux/macOS only at the moment.
Now tilde does have two existing historical interpretations in Windows, one as a common prefix or extension for temporary files, the second in batch files when getting the directory where the batch file comes from, eg %~dp0.

Now tilde does have two existing historical interpretations in Windows, one as a common prefix or extension for temporary files,

Unlike Unix, we do not have to expand ~name because we do not have to care about user profile folders of other users in Windows.

the second in batch files when getting the directory where the batch file comes from, eg %~dp0.

It is not affected because it does not start with ~.

Unlike Unix, we do not have to expand ~user because we do not have to care about user profile folders of other users in Windows.

Why is that the case? Windows is a multi-user operating system and servers often have multiple accounts and need to be administered. That is the original purpose behind PowerShell.

I forgot Windows Server. However, it will be difficult to take users whose names contain space into account.

Implementing ~<username> expansion is the subject of this long-standing feature request:

#12387

As for usernames with spaces (which are rare, as is ~<username> use in general, but there's no reason not to fully emulate the tilde expansion of POSIX-compatible shells): The spaces need to be `-escaped, e.g., ~jane` doe
As for bringing the emulation of tilde expansion to Windows (for native programs only, as on Unix): In addition to the discussion in the previously linked issue, there is a also a PR, though it would initially be just an experimental feature:

#20402

As for usernames with spaces (which are rare, as is ~<username> use in general, but there's no reason not to fully emulate the tilde expansion of POSIX-compatible shells): The spaces need to be `-escaped, e.g., ~jane` doe

I would really hope that scripts don't have hard coded usernames in them! They should be parameterised, for example the following works on macOS zsh...
% ( FOO=root ; echo ~$FOO )
/var/root

And ksh
$ ( FOO=root ; echo ~$FOO )
/var/root

but not in bash
$ ( FOO=root ; echo ~$FOO )
~root

in sh
$ ( FOO=root ; echo ~$FOO )
~root

So for true emulation you need to be exactly clear on all the use cases and at what point in the expansion the ~ occurs, given the above example it looks like it is after the environment variable substitution. But zsh and ksh behaves differently to bash and sh

I agree that ~<username> isn't terribly useful, @rhubarb-geek-nz, and personally I don't miss it.
But, as stated, there's no reason not to fully emulate the tilde expansion features of POSIX-compatible shells.
Good point re the different behaviors in different shells - I was only aware of the Bash behavior, where only a verbatim username works: This is in line with the POSIX spec (you can infer it from the fact that tilde expansion is prescribed to occur before parameter expansion).
This, and the prevalence of Bash, point to the fact that  ~<username> is primarily an interactive convenience, such as typing ls ~j<tab>, which expand to ls ~jdoe and therefore refers to user jdoe's home directory.
Thus, one option is to limit PowerShell to emulating the POSIX-compliant / Bash behavior and allow verbatim usernames only.
To also support variable-based usernames, the logic would have to be (as implied by the usual quoting rules of POSIX-compatible shells), with $user = 'jdoe':

~jdoe, ~$user, ~"$user" should expand to jdoe's home dir. (but only - as usual - if either followed by no additional characters or an unquoted /)
Any other forms shouldn't  (e.g., '~jdoe', "~$user")

This would make it a bit more useful, because it makes it suitable for use in scripts too.
I suggest continuing this discussion in #12387, if necessary.


Add demo on DNA recombination with different kinds of transformations

This issue was moved to Dallinger/Dallinger#60


0.8.0-alpha - poor formatting

Prerequisites
Put an x into the box that applies:

[ x] This issue describes a bug.
[ ] This issue describes a feature request.

For more information, see the Contributing Guidelines.
Description
I tried out 0.8.0-alpha and the formatting was less than ideal.  The content in the Type and Default columns are wrapped with code and pre so the rows are very long when there are complex types and defaults.  I removed the pre tags to avoid this.  I also had a default that was a one element list of "*" which should be escaped.
The variables file, the original generated md table, and my modified md table are in this gist https://gist.github.com/grimm26/a0ced6cdfb0f8d6ec5377abe2ca5ba3f
Version
terraform-docs version v0.8.0-alpha darwin/amd64 BuildDate: 2019-12-23T10:16:00-06:00

Thank you @grimm26 for the feedback, and specially for providing the full config example to work with. I'll take a look later today.

Sorry for the delayed response. I found something interesting. It seems the issue is not with the way terraform-docs generates the result, rather than the different markdown engines processes them, which unfortunately makes it even harder to solve.
I've used your example config to generate the table output, and

VS Code markdown preview mode: shows 100% correct
GitLab Markdown engine: shows almost correct
GitHub Markdown engine: messes up the content
Shoved generated md file into a Hugo site: shows nearly 100% correct

I tried something else to generate fully html based table rather than mixing html tags inside markdown table, which unfortunately didn't make any difference.
So at the moment I'm a bit out of options and trying to understand the difference between these markdown renderer engines. But I wanted to ask you, in the meantime, to give it a try with markdown document command (as a test), I know this is inconvenient but it can help narrowing down the issue to only table format and not markdown in general.

@khos2ow I added the output using the document option to my gist.  The result is definitely cleaner, but I'd much rather have a table format.

@grimm26 yeah I completely understand, I was only trying to see if the issue is within the markdown as a whole or it's limited to markdown table. I'll try to come up with a fix.


[UI] Recognize rancherd clusters as "rancherd"

What kind of request is this (question/bug/enhancement/feature request):
Feature Component
Summary:
RancherD will need to be recognized separately from rke2 clusters. Today, with no changes made, RancherD would be recognized as an RKE2 cluster. This will need to be changed so it is recognized as a "rancherd" cluster. Could be done via annotations?
Related:
RKE2 clusters will need to be shown as "RKE Federal". A separate issue here tracks this: https://github.com/rancher/rancher/issues/28650

a specific driver was set for rancherd pr : https://github.com/rancher/rancher/pull/29075
It's correctly showed in dashboard :

and in ecm api cluster driver is set to 'rancherd' but the ember ui shows imported

probably because there's no config assigned https://github.com/rancher/ui/blob/master/app/models/cluster.js#L165

We should move the cluster page to start using the Rancher provider to show the Provider. Seeing as this is a bigger change, I've moved it to 2.5.1.

In Rancher version v2.5.0-rc6, on the rancher dashboard provider is seen as RKE Government.
rancherd -v
rancherd version v2.5.0-rc6 (HEAD)

Snippet from cluster API
driver": "rancherd",
provider": "rke2",
gitVersion": "v1.18.9-rc1+rke2",

We need a v2.5.3 RC to test this fix

Rancher version v2.5.4-rc1 (12/04/2020)
RancherD cluster is now properly recognized as RancherD in the EmberUI and RKE Government in the Dashboard.


Compare always false

Trying to use the compare helper and every time it will return false. Even using your examples:
{{log (compare 2 '>' 1)}}
{{log (compare 'one' '==' 'one')}}
Any idea?

Hello @2gen
Returns true in both cases on my end.
Could we have minimal reproduction repo?

Forgot to update.
Yes, it was my error. There was a helper defined previously with the same name "compare" so the Meteor-Template-helpers "compare" wasn't being used. Removing the previously declared helper resolved the issue.
Thanks.


About alternate proxies

Do I need to modify something besides the files from "AlternateProxies"? Since I get an error because this line
Btw, I get the same error when I try to compile as "release" even with the original files (d2d1)
log:
VNTextProxy.log

Until now, D2DProportionalizer.cpp required the D2D1 proxy to be active, meaning that if you used a different proxy, you had to remove the D2DProportionalizer from the project. I changed the code so this is no longer necessary.


addition of columns for status/icons

Adds functionality for a user to specify a status column (colored circle) as well as a column for an individual icon

Does this look more right?
https://github.com/raiyni/timeline/commit/c26bbfada52c70e6212a10277aa20c98398dfbd5
Line drawn to illustrate the alignment

Yeah, that looks great

Added in f90bcb4833447aab7de0a46ed9b994caf662ee16


[gui] Deprecate PySide Qt binding

Merge PR #1997 first!
This PR:

adds a deprecation warning when loading PySide,
moves PySide to the last probed Qt binding
removes PySide from the documentation.

Are you OK with this?

OK with me,

LGTM then


git: 'noclone' is not a git command

I'm trying to create no clone using git, but i'm getting:
git: 'noclone' is not a git command. See 'git --help'.

I couldn't find the noclone command in the help, even though it says i should look for it there.
Please help.

Instead of git noclone, you should try:

You will see following output:

Thanks @genacrys . That worked.
If above solution doesn't work then you might have to restart your system.

Thanks, fixed it. Closing.


RedisClient.shutdown  Cannot connect, Event executor group is terminated.

Bug Report

Current Behavior
i pop list  from redis . but i shutdown my application .when i restart my application .i find the stack message.
it is fixed  the problem via #998 , why do it comes again?

Stack trace
java.lang.IllegalStateException: Cannot connect, Event executor group is terminated.
at io.lettuce.core.AbstractRedisClient.initializeChannelAsync(AbstractRedisClient.java:290)
at io.lettuce.core.RedisClient.connectStatefulAsync(RedisClient.java:293)
at io.lettuce.core.RedisClient.connectStandaloneAsync(RedisClient.java:273)
at io.lettuce.core.RedisClient.connect(RedisClient.java:206)
at org.springframework.data.redis.connection.lettuce.StandaloneConnectionProvider.lambda$getConnection$1(StandaloneConnectionProvider.java:115)

Input Code

Input Code
// your code here;

Expected behavior/code

Environment

Lettuce version(s): [e.g. 5.3.2.RELEASE]
Redis version: [e.g. 3.3.0]

Possible Solution

Additional context

The bug within Lettuce was fixed with #998. However, your application must not create a new connection after shutting down RedisClient. That's something that must be fixed on your side.


Remake dirtyStates

Input component must set dirty state independently if changed.
ValidationBox should have fieldPath in context and all input components which locates in ValidationBox should set dirtyState via context.form.setDirtyState(context.fieldPath)
Also this enhancement should affect on cursor - from context.fieldPath and context.form.cursor we may construct path to input cursor.

Fixed in v2.0.0


Sorry, the page you are looking for could not be found.

i use laravel5.1.4. the problem is "Sorry, the page you are looking for could not be found.".
can someone help me?thankyou

sounds like you are not installed correctly cause the routes are not picking up. Please follow these instructions:
https://github.com/FrozenNode/Laravel-Administrator/blob/dev/docs/installation.md


Need to store additional information with uploaded images

Using the Python high-level API, I am able to create a "task" and "upload" images using a modified version of the example given in: https://opencv.github.io/cvat/docs/api_sdk/sdk/highlevel-api/
Along with each image, I need to store additional "meta data" that relates to the origin of the image.
I have been searching the net, and reading the documentation, but I cannot find a "key" that I can use to store this additional information. Is it not possible to add extra information/description to an image?
Thanks.

Binding 3rdparty metadata to images is not supported.

@bsekachev I just submitted this as a feature request.  See dev-328.  Thanks!


Wrong position of pop-over in Firefox

pop-overs do not respect scrolled offset in Firefox.
Tested with latest ember-bootstrap 1.0.0-beta.1 on Mac (macOS Sierra) with FF 53.0.2.
On Chrome and Safari, position is correct.
See this twiddle for reproduction:
https://ember-twiddle.com/54d3b05d8c6f88b2ba530f45a158e864

I tackled it down to the problem.
Seems like an outdated scrollPosition attribute is used:
https://github.com/kaliber5/ember-bootstrap/blob/master/addon/utils/get-position.js#L20
According to: https://stackoverflow.com/questions/28633221/document-body-scrolltop-firefox-returns-0-only-js
The lines should be replaced as following:
  let elOffset = isBody ? { top: 0, left: 0 } : (isSvg ? {} : {
    top: rect.top + (window.pageYOffset || document.documentElement.scrollTop || document.body.scrollTop || 0),
    left: rect.left + document.body.scrollLeft
  });

Tested in latest Chrome, Firefox, Safari.
PS1: Thanks for the awesome addon :+1:
PS2: btw. is it possible to close the pop-over on-click-outside? as the dropdown...


Use datasapce function info to load function explorer panel for dataspace

Summary

Use datasapce function info to load function explorer panel for dataspace
How did you test this change?

[ ] Test(s) added
[x] Manual testing (please provide screenshots/recordings)
[ ] No testing (please provide an explanation)

https://github.com/user-attachments/assets/1f5c557c-e845-4394-a571-109f476db207

closed by https://github.com/finos/legend-studio/pull/3517


Add API schema for /__admin/near-misses/request

Split off from PR #888 to make it easier to review. This adds an API schema for /__admin/near-misses/request, which is required for OpenAPI 3 conversion to work.

Thanks again for all these!


CupertinoSwitch - Provide the ability to add a border

Use case
The CupertinoSwitch has no way to add a border to it. Attempting to use a Container with a BoxDecoration and borderRadius creates a thick border around the CupertinoSwitch.
return Container(
      decoration: BoxDecoration(
        borderRadius: BorderRadius.circular(20.0),
        color: value
            ? activeBorderColor
            : inactiveBorderColor,
      ),
      child: CupertinoSwitch(
        value: value,
        activeColor: activeColor,
        onChanged: onChanged,
      ),
    );

The above creates a thick border around the CupertinoSwitch.
Proposal
Add the ability to change the borderColor and borderWidth of a CupertinoSwitch. This will also allow the creation of thin borders around the CupertinoSwitch.
PR implementation
https://github.com/flutter/flutter/pull/63423

@HansMuller Hi, apologizes for bothering you, can I get this looked at by the appropriate parties? PR has been up for a while.
Thank you!

We'd like to generally limit the scope of the Cupertino package to what's feasible in Xcode natively. Is there a customizable border with UISwitch?

@xster
This is how the CupertinoSwitch currently looks like on Flutter

Here is an example straight from the iOS settings I believe. You can see that the switches in the OFF state have a light grey colour with a darker outline.

Another iOS image, check out the OFF state switch

There are also other images I found with some outline. Some being apart of iOS and others packages for other libraries.

This has changed in iOS 14. There are no borders, as seen here:

Closing until there's further need in the future.


ARTEMIS-3720 Max Number Of Messages on a deciding policy for paging (global and address-settings)

@gemmellr you mentioned me the other day that Page would run a task twice when releasing max-size on blocking. This would address that I think  (as well)

Dont think I did? Oh....actually, do you mean https://issues.apache.org/jira/browse/ARTEMIS-3591 from a while back? I had forgotten about that. Skimming the change here, it doesnt seem like it would directly address that.

@gemmellr there is an atomic  flag on a new class called SizeAwareMetric (something like that). I don't have a test for the issue you reported but this could address that.

@gemmellr there is an atomic flag on a new class called SizeAwareMetric (something like that). I don't have a test for the issue you reported but this could address that.

I've added a test and the trivial fix in #3985

Oops... I need to add tests for the parsing.. and I forgot to change the XSD for the address-settings

@jbertram I applied the changed


Add option to not store sensitive request info (API keys, etc.) in cached PreparedRequest objects

When using a backend that's shared with other services, a user may not want to store certain pieces of request information, like API keys, auth tokens, etc. These could be in either request parameters, headers, or keys in a JSON request body.
We could add a separate option to specify params/keys to not store in the cache. Alternatively, we could add this to the existing behavior of ignore_parameters, since the main purpose of that is for things like auth tokens. It may also be worthwhile to make it the default behavior to remove a handful of the most common authentication params & headers, e.g. for OAuth. Either way this would just affect the stored PreparedRequest object.
Anyone else have opinions on this?

Is this an issue? For all backends, the caching mechanism is to create a secure hash of the request parameters (see requests_cache/cache_keys.py).  As a result, the only thing stored in the backend is an irreversible secure hash of whatever sensitive information was in the request.
The consequence of this is that whatever secure information was in the request is irrecoverable from the backend, even if the data produced in response to that request could be obtained by querying the backend. But that's related to the security of the response, not the request.
As a result, I don't think this is an enhancement that needs to be made. The current architecture protects against recovery of sensitive materials (e.g. API keys, auth tokens, etc) in the request from the backends. And if you want to protect any sensitive information in the response, then you can use the other mechanisms to either disable caching to specific endpoints, or disable the cache before sensitive requests.
One related question would be if we want to add encrypted backends to prevent recovery of even the response data, such as adding SEE or SQLCipher support. But that feels pretty far afield from the basic functionality of this package, and maybe should be left as an exercise for the user.

Thanks for the input! It's probably a small minority of cases where this would potentially be an issue, but credentials sent in the request could still be recoverable if the backend itself isn't secured at all. Besides the hash value used as a cache_key, request info is also stored on response.request, which is a PreparedRequest object.
You're right that if you need to secure either your request or response data, using whatever tools are already available for the backend you're using (like the options you linked for SQLite, or just a username/password for the other backends) is going to be the best option. So I guess what this is really about is providing an easier option if you don't want to set up authentication or encryption.

Ah! For some reason I didn't realize that. Then yeah! By all means. Seems like a great feature. I suspect it would resemble something like the related feature in VCRpy
Separately - and maybe a separate issue - encryption on backends might be a good idea to the extent that secret key material unlocks secret data in the response. That wouldn't be too hard, since this package already has a good backend base class.

FYI - I would love to contribute on this feature. Unless you've already put in some work, let me take a stab at an implementation.
This library has been fantastic for a number of uses I've put it to, and I'd love to be able to give back!

Yeah, that would be great! Especially if this is something you would potentially use in patent_client. I'll add some notes on what I've thought of so far, and let you take it from there.

Here's the general approach I've been trying to take with adding new cache features:

Add a simple, concise option that covers the majority of basic use cases (preferably via a new or existing keyword arg for CachedSession)
Also allow for more fine-grained control for more complex use cases (and this usage can be more verbose, if needed)
Try to integrate with existing features when possible

Request params & body
Looking at the ignored_parameters option would be a good place to start. This already applies to both request params and the request body, since many APIs out there treat these interchangeably, e.g. they let you pass a given parameter either in request params or in a JSON-formatted request body.
One approach would be to extend the existing ignored_parameters option to apply to both cache keys and cached data, which I think makes sense since the main use case for ignored_parameters also happens to be auth tokens.
If you can think of a common enough case where you would want to ignore a parameter when generating cache keys, but include it in the cached response (or vice versa), then adding a separate keyword arg would make more sense.
Headers
We could add an ignored_headers option that works the same as  ignored_parameters. So that would also apply to both cache keys (if include_get_headers is used) and cached data. I'm open to other suggestions for that, though.
Advanced usage
For more fine-grained control of what exactly gets cached, I think this would fall under the category of post-processing responses (see #98, for example). That can be done currently with something like:
response = session.get('http://httpbin.org/ip')
response = postprocess(response)
session.cache.save_response(response)

But I've seen enough variations of that that I'm considering adding support for a generic hook that takes a CachedResponse and does whatever you want to it before saving. That would be a separate issue, though.

Hey! I started working on this before your notes, but I think our heads were in the same place. I basically implemented as you suggested (with testing and docs!)

Sweet! I'll take a look soon.

Merged. Thanks for the contribution! Your changes will be available in the latest pre-release build soon.
I think we're good to close this issue for now. Feel free to create a new one if there are more features related to this that you'd like to see.


Name mappings, so I can work with multiple Minecraft versions at the …

issue #25
Now MappingsProvider will name the mojmap file mappings-{mc version}.tiny-final.jar
and I don't have to do refresh dependencies every time I change the version.

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


Feature/binary theme values

Codecov Report

Merging #20 (35cbdd9) into master (0359822) will increase coverage by 0.15%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #20      +/-   ##
==========================================
+ Coverage   96.26%   96.42%   +0.15%
==========================================
  Files          10       10
  Lines         134      140       +6
  Branches       41       45       +4
==========================================
+ Hits          129      135       +6
  Misses          4        4
  Partials        1        1

Impacted Files
Coverage Δ

default.theme.js
100.00% <ø> (ø)

src/fragments/blueprints.js
100.00% <ø> (ø)

src/utils/index.js
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


[11.x] Enhance testability of batched jobs

The current approach to testing batched jobs, as shown below, is somewhat unconventional:
Bus::assertBatched(fn (PendingBatchFake $batchedCollection) =>
    $batchedCollection->jobs->count() === 1 && $batchedCollection->jobs->first()->value === 'hello';
);

This pull request introduces some helper functions to enhance the testability of batched jobs. Inspired by fluent JSON testing, these methods provide a more streamlined and readable approach to testing job batches within the Laravel application. The goal is to improve developer experience by offering clear, concise methods with illustrative examples.
Example Usage
has
public function has(string|int $expectedJob, array $expectedParameters = [])

Assert that the batch contains a job of the given type. You can also pass an integer to assert that the batch contains the exact number of jobs.
Example:
Bus::fake();

Bus::batch([
    new AJob(1, 2),
    new BJob,
])->dispatch();

Bus::assertBatched(fn (PendingBatchFake $batch) =>
    $batch->has(2)
        ->has(AJob::class, [1, 2])
);

missing
public function missing(string $expectedJob)

Assert that the batch does not contain a job of the given type.
Example:
Bus::fake();

Bus::batch([
    new BJob,
])->dispatch();

Bus::assertBatched(fn (PendingBatchFake $batch) =>
    $batch->missing(AJob::class)
);

hasAll
public function hasAll(array $expectedJobs)

Assert that the batch contains all of the given jobs.
Example:
Bus::fake();

Bus::batch([
    new AJob,
    new BJob,
])->dispatch();

Bus::assertBatched(fn (PendingBatchFake $batch) =>
    $batch->hasAll([AJob::class, BJob::class])
);

missingAll
public function missingAll(array $expectedJobs)

Assert that the batch does not contain any of the given jobs.
Example:
Bus::fake();

Bus::batch([
    new AJob,
    new BJob,
])->dispatch();

Bus::assertBatched(fn (PendingBatchFake $batch) =>
    $batch->missingAll([CJob::class, DJob::class])
);

hasAny
public function hasAny(...$expectedJobs)

Assert that the batch contains any of the given jobs.
Example:
Bus::fake();

Bus::batch([
    new AJob(1, 2),
    new BJob,
])->dispatch();

Bus::assertBatched(fn (PendingBatchFake $batch) =>
    $batch->hasAny(AJob::class, CJob::class)
);

first
public function first(callable $callback)

Assert that the first job in the batch matches the given callback.
Example:
Bus::fake();

Bus::batch([
    [
        new AJob(1, 2),
        new BJob,
    ],
    new CJob,
])->dispatch();

Bus::assertBatched(fn (PendingBatchFake $batch) =>
    $batch->first(fn (PendingBatchFake $firstBatch) =>
        $firstBatch->has(AJob::class, [1, 2])
            ->has(BJob::class)
    )
);

nth
public function nth(int $index, callable|string $callback, array $parameters = [])

Assert that the nth job in the batch matches the given callback or type and parameters.
Example:
Bus::fake();

Bus::batch([
    [
        new AJob(1, 2),
        new BJob
    ],
    new CJob::class(1)
])->dispatch();

Bus::assertBatched(fn (PendingBatchFake $batch) =>
    $batch->nth(0, fn (PendingBatchFake $batch) =>
        $batch->has(AJob::class, [1, 2])
            ->has(BJob::class)
    )->nth(1, CJob::class, [1])
);

equal
public function equal(array $expectedJobs)

Assert that the batch contains exactly the given jobs with the specified parameters.
Example:
Bus::fake();

Bus::batch([
    [
        new AJob(1, 2),
        new BJob
    ],
    new CJob::class(1)
])->dispatch();

Bus::assertBatched(fn (PendingBatchFake $batch) =>
    $batch->equal([
        [
            AJob::class => [1, 2],
            BJob::class
        ],
        CJob::class => [1]
    ])
);

etc
public function etc()

Assert that the batch has unexpected jobs beyond those checked.
Example:
Bus::fake();

Bus::batch([
    new AJob(1, 2),
    new BJob,
    new CJob::class(1)
])->dispatch();

Bus::assertBatched(fn (PendingBatchFake $batch) =>
    $batch->has(AJob::class, [1, 2])
        ->has(BJob::class)
        ->etc()
);

Thanks for your pull request to Laravel!
Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.
If applicable, please consider releasing your code as a package so that the community can still take advantage of your contributions!

I've put this code into a package, which might be useful for others. Please let me know if you find it helpful, or if there's anything I can improve.


Typescript migration

Hi @ableda
Thanks for the time you've put into this. I'll keep this open for a bit while I consider it.

Hi @mcnamee, I am sorry I did not realize I was submitting an official PR here. This was meant as an experiment, an initial kit for an app using Typescript which I prefer. Thanks so much for sharing this with the world, very helpful to get started learning react-native.


[Need help]iOS 打包失败

Describe your needs
If possible, add prototypes / designs and other supporting documents to help others understand your needs.
Xcode报错截图

Android studio 报错截图

你倒是把armv7选项关掉啊！


Several app elements do not have high res retina graphics

Except for text, animated stickers (only when moused over) and the blue icons in the top toolbar, everything else lacks high res graphics. The messenger.com web version fully supports it though.
Adding retina capabilities in the plist doesn't seem to make a difference.
Running 10.11.5.

Messenger.com has retina graphics:

It seems that messenger.com has fixed the issue, so you can close this ticket.


update go 1.19.1

updated Go version to v1.19.1 which includes security update.
removed io/ioutil which has been deprecated in Go 1.16.

CI/CD example(including tag-release):
https://github.com/to-lz1/dsps/actions

@hirosassa Please review for Go update of Dsps 🙏

@to-lz1 Thanks for your contribution!
I wonder why the CIs didn't run 🤔