AKS Authorized IP Ranges - Static API IP

On our firewall I can only use IP addresses to define our split tunnels. It does not support domain name based rules. So my concern is that if I lock down access to our k8s API IP and that IP changes we will not be able to access the cluster.
Are AKS API IPs static or will they change over time?

@poochwashere -
Thank you for your question.
Can you please share with us the URL of the document that you are having issues with?
Please note that we scope issues on this repo to feedback related to the docs. If you have a product question, please post it on Microsoft QnA or Stack Overflow. Thank you for your understanding.

https://docs.microsoft.com/en-us/azure/aks/api-server-authorized-ip-ranges

This article is discussing locking down access from your IPs to the API server in AKS.  This means you are telling AKS, to accept traffic from a specific set of IP ranges (ones you can control on your side, etc).     My point is it is a config on the AKS side (specifying your IPs) .. so if your IPs change, then you need to update the "AKS config" for authorized ranges.
Are you asking something different than the article though, such as controlling what traffic is allowed from your firewall to specific IPs?  I ask this since you mention what happens if the "AKS side has an IP change" .. BTW the AKS side IP is alive for the lifetime of the AKS cluster resource by default.  There are ways to specify a static IP on AKS side a well though as well, see here:  https://docs.microsoft.com/en-us/azure/aks/static-ip

here's some info on the doc and if/when we change an IP on the API server:
On rare occasions, if there's a maintenance operation your API server IP might change. Planned maintenance operations that can change the API server IP are always communicated in advance.  From this doc:  https://docs.microsoft.com/en-us/azure/aks/limit-egress-traffic#required-outbound-network-rules-and-fqdns-for-aks-clusters

@mlearned - Thank you for providing your insights.
@poochwashere - I hope @mlearned has answered your question.
At this moment, Since there is no doc update required, We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


[SSM] SSM exits when another instance is functioning

Keep SSM single instance in the system.

This feature has been done.


AutoCommandBufferBuilder::begin_render_pass doesn't clear all cubemap layers

Version of vulkano: 0.19.0 from crates.io
OS: Windows 10 x64
GPU (the selected PhysicalDevice): GeForce RTX 2070 SUPER
GPU Driver: 460.79
See bottom of issue for a minimal example

Issue
AutoCommandBufferBuilder::begin_render_pass only clears the first layer of cubemap attachments. After some digging through the source, it appears this is because Dimensions::array_layers (called from FramebufferBuilder::add) returns 1 instead of 6 for Dimensions::Cubemap{size}. I noticed that if you convert the dimensions to a ImageDimensions it does return 6.
With my limited familiarity with the codebase, I see two possible solutions:

change the behavior of Dimensions::array_layers so that it returns 6 for cubemaps here I didn't see the Dimensions::array_layers_with_cube function, so this is probably not the solution
convert the Dimensions to ImageDimensions in FramebufferBuilder::add (via Dimensions::to_image_dimensions) here

Minimal Bug Reproduction
use vulkano::buffer::{BufferUsage, CpuAccessibleBuffer};
use vulkano::image::{Dimensions, StorageImage};
use vulkano::instance::InstanceExtensions;
use vulkano::command_buffer::AutoCommandBufferBuilder;
use vulkano::device::{Device, DeviceExtensions};
use vulkano::framebuffer::Framebuffer;
use vulkano::image::ImageUsage;
use vulkano::instance::{Instance, PhysicalDevice};
use vulkano::format::Format;
use vulkano::sync;
use vulkano::sync::GpuFuture;

use std::sync::Arc;

fn main() {

    let instance = Instance::new(None, &InstanceExtensions::none(), None).unwrap();

    let physical = PhysicalDevice::enumerate(&instance).next().unwrap();

    println!(
        "Using device: {} (type: {:?})",
        physical.name(),
        physical.ty()
    );

    let queue_family = physical
        .queue_families()
        .find(|&q| {
            q.supports_graphics()
        })
        .unwrap();

    let device_ext = DeviceExtensions {
        khr_swapchain: true,
        ..DeviceExtensions::none()
    };
    let (device, mut queues) = Device::new(
        physical,
        physical.supported_features(),
        &device_ext,
        [(queue_family, 0.5)].iter().cloned(),
    )
    .unwrap();

    let queue = queues.next().unwrap();

    let render_pass = Arc::new(
        vulkano::single_pass_renderpass!(
            device.clone(),
            attachments: {
                color: {
                    load: Clear,
                    store: Store,
                    format: Format::R32G32B32A32Sfloat,
                    samples: 1,
                }
            },
            pass: {
                color: [color],
                depth_stencil: {}
            }
        )
        .unwrap(),
    );

    let image_buffer = StorageImage::with_usage(
        device.clone(),
        Dimensions::Cubemap{size : 4},
        Format::R32G32B32A32Sfloat,
        ImageUsage{
            transfer_source          : true,
            transfer_destination     : true,
            sampled                  : false,
            storage                  : false,
            color_attachment         : true,
            depth_stencil_attachment : false,
            transient_attachment     : false,
            input_attachment         : true,
        },
        [queue.family()].iter().cloned()
    ).unwrap();

    let out_buffer = CpuAccessibleBuffer::from_iter(
        device.clone(),
        BufferUsage::all(),
        false, [0.0f32; 4*4*4*6].iter().cloned()
    ).unwrap();

    assert_eq!(image_buffer.dimensions().array_layers(), 1);
    assert_eq!(image_buffer.dimensions().to_image_dimensions().array_layers(), 6);

    let framebuffer = Arc::new(
        Framebuffer::start(render_pass.clone())
            .add(image_buffer.clone()).unwrap() // Framebuffer think the image only has 1 layer here
            .build().unwrap()
    );

    let clear_values = vec![[0.0, 0.0, 1.0, 1.0].into()];

    let mut builder = AutoCommandBufferBuilder::primary_one_time_submit(
        device.clone(),
        queue.family(),
    )
    .unwrap();

    builder
        // *** render pass only clears layer 0
        .begin_render_pass(framebuffer.clone(), false, clear_values).unwrap()
        .end_render_pass().unwrap()
        .copy_image_to_buffer(image_buffer.clone(), out_buffer.clone()).unwrap();

    let command_buffer = builder.build().unwrap();

    sync::now(device.clone())
        .then_execute(queue.clone(), command_buffer).unwrap()
        .then_signal_fence_and_flush().unwrap()
        .wait(None).unwrap();

    let data = out_buffer.read().unwrap();

    for (i, p) in data.chunks_exact(16).enumerate() {
        if i % 4 == 0 {
            println!("Layer: {}", i / 4);
        }
        println!("  {:?}", p);
    }

}

@Tenebryo Thank you for the bug report. Would you like to take a lead in fixing it? I'm fine with any solution you choose. It would be just more preferable if it wouldn't break existing public API(unless absolutely unavoidable).

@Eliah-Lakhin I created a pull request ( #1459 ) with my proposed fix. The only change is to use ImageDimensions instead of Dimensions for framebuffer attachments, which should only affect cube map attachments. I've been using this change in the project I found the bug in.

Fixed in #1459


Starting multiple cron jobs

I have trouble starting multiple cron jobs.
Here is my setup:
# schedule.yml

match_kickoff_watch_job:
  cron: "*/10 * * * *"
  class: "MatchKickoffWatch"
  queue: match_kickoff_watch
  active_job: true

season_ending_watch_job:
  cron: "18 30 * * *"
  class: "SeasonEndingWatch"
  queue: season_ending_watch
  active_job: true

# initializers/sidekiq.rb

redis_url = if Rails.env.development?
              "redis://localhost:6379"
            elsif Rails.env.staging?
              begin
                # for staging heroku app
                ENV.fetch("REDISCLOUD_TEAL_URL")
              rescue KeyError
                # for development heroku app
                ENV.fetch("REDISCLOUD_BLUE_URL")
              end
            elsif Rails.env.production?
              ENV.fetch("REDISCLOUD_GREEN_URL")
            end

Sidekiq.configure_server do |config|
  config.redis = { url: redis_url }

  schedule_file = "config/schedule.yml"

  if File.exists?(schedule_file) && Sidekiq.server?
    Sidekiq::Cron::Job.load_from_hash YAML.load_file(schedule_file)
  end
end

Sidekiq.configure_client do |config|
  config.redis = { url: redis_url }
end

This is output I get from rails console Sidekiq::Cron::Job.all

It also looks from the logs, when I start sidekiq, it only starts the first job in the schedule.yml.

Am I doing something wrong here?


Some documentation changes.

Title is a bit unclear.
The following is a first draft of some documentation changes I wanted to make.
Adding:

A general review of how to use terraform-compliance.

I talked about context a bit. I thought it would give a good idea of how steps interact and are suppose to work. (e.g. filtering, drilling down)
some examples were added to @noskip and Given
more information on how to test your pr's

Pull Request Test Coverage Report for Build 1075

0 of 0   changed or added relevant lines in 0 files are covered.
6 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.3%) to 59.497%

Files with Coverage Reduction
New Missed Lines
%

terraform_compliance/common/defaults.py
6
83.78%

Totals

Change from base Build 1070:
0.3%

Covered Lines:
1206

Relevant Lines:
2027

💛  - Coveralls

Another thing that can be added:

mention which steps do recursive seeking, which ones don't.

(Or recursively seek on every step for consistency)
(Would that make drilling down obsolete?)


Potential memory error

Describe the bug
A potentially memory bug for object fileDialog at line 197. It might be double deleted.
https://github.com/NCAR/VAPOR/blob/2bc9884cf88b84a2c3eb51cb41d8498dc27f4a38/apps/vaporgui/VaporWidgets.cpp#L195-L223
Reasoning

Object fileDialog was created on the stack, so this object is automatically destroyed by C++ at the end of the current function, at line 223.
Object fileDialog was created with a pointer to its parent, so it's added to the QT hierarchy tree. When VAPOR quits, all QWidgets on this hierarchy tree are deleted by QT.
For the same object, step 1 and 2 each attempts a deletion. A double deletion thus occurs.

QFileDialog can be created on the stack and still receive a 'this' pointer to its parent.  It will destroy itself when it leaves scope, unregister itself as a child of its parent at this point.   However, if the parent is destroyed while the QFileDialog is on the stack, the parent will attempt to destroy the dialog.  The dialog will then try to free itself upon leaving scope, resulting in a double delete.  For this reason, we want to always allocate QFileDialogs on the Heap.


chore(deps): start using renovate

Actually wait - then we should remove the Greenkeeper badge from the README right?

Done. AFAICT there is no renovate badge?

Correct, no badge.


example files unuseable

there is no data to even run an example. your description in readme is incorrent. python cf_demo.py not working. and in repo no folder dataset, and also no any documentation about format or content of this directory. wtf?
PS C:\Users\username\Desktop\pyCFTrackers\examples> python .\cf_demo.py Traceback (most recent call last):   File ".\cf_demo.py", line 7, in <module>     data_names=sorted(os.listdir(data_dir)) FileNotFoundError: [WinError 3] Системе не удается найти указанный путь: '../dataset/test' PS C:\Users\username\Desktop\pyCFTrackers\examples>

oh. i found it. in directory Cftracker/dataset/test/ should be at least one video in otb100 format. it would be cool if u add some default video just to show usage example


Add generation from seed string

It would be nice if it was possible to generate an avatar from a seed string

Can you go a little more into detail:

What do you hope to get out of this?
How would you want to use it?
Ideas how this could be implemented?
There is a limited number of combinations, so what should happen, if there are no more new combinations?

The goal is to generate an avatar from an user uuid. If there are redundancy it does not matter, it's just an avatar.

I would personally advice against this.
When you generate the avatar based on the uuid it can not be changed later

Those are not my requirements. My requirement is:

if the user does not have an image => use uuid to generate one
else use image.

I see.
The easiest solution I see rn would be to add an additional parameter to the random() method.
So you could pass the Random functions seed. This would ensure that you each time get the some avatar for the same uuid.
An issue I see there would be that other users could get the same one on a different seed.
I am personally not familiar with programming a seed generator :sweat_smile:

Looking around for avatar libraries I found one in react that has a design language that is more in line with my app, so I guess I'll eventually try to port that one. So I'll close this, unless you want me to reopen.


Crash in cachekey with specific capture-prefix-uri

I was doing some testing with cachekey and managed to make one that crashed it:
@plugin=cachekey.so @pparam=--separator= @pparam=--remove-all-params=true @pparam=--remove-path=true @pparam=--capture-prefix-uri=/http(s)?://([^?]*)/$1://$2/
The (s)? is what was added to cause the crash

Hi Evan,
Thanks for reporting it!
Based on the info you provided I was able to get a crash (exception thrown from unhandled case).
Here is the PR https://github.com/apache/trafficserver/pull/4101 https://github.com/apache/trafficserver/pull/4101 that should fix it.
Here is the test-case that got fixed.
@plugin=cachekey.so
@pparam=--separator=
@pparam=--remove-all-params=true
@pparam=--remove-path=true
@pparam=--capture-prefix-uri=/http(s)?://([^?]*)/$1://$2/
$ curl  http://example-cdn.com/path/file
Results in the following log:
[Aug 11 11:30:41.800] {0xb000c000} DIAG: (cachekey) cachekey/cachekey.cc:208:CacheKey() setting cache key from a remap plugin
[Aug 11 11:30:41.800] {0xb000c000} DIAG: (cachekey) cachekey/cachekey.cc:219:CacheKey() using remap uri 'http://example-cdn.com:8080/path/file'
[Aug 11 11:30:41.800] {0xb000c000} DIAG: (cachekey) cachekey/pattern.cc:277:replace() replacing:'$1://$2' in pattern:'http(s)?://([^?]*)', subject:'http://example-cdn.com:8080/path/file'
[Aug 11 11:30:41.800] {0xb000c000} DIAG: (cachekey) cachekey/pattern.cc:309:replace() start -1, len 0
[Aug 11 11:30:41.800] {0xb000c000} DIAG: (cachekey) cachekey/pattern.cc:313:replace() replacing '$1' with ''
[Aug 11 11:30:41.800] {0xb000c000} DIAG: (cachekey) cachekey/pattern.cc:313:replace() replacing '$2' with 'example-cdn.com:8080/path/file'
[Aug 11 11:30:41.800] {0xb000c000} DIAG: (cachekey) cachekey/pattern.cc:323:replace() replacing '$1://$2' resulted in '://example-cdn.com:8080/path/file'
[Aug 11 11:30:41.801] {0xb000c000} DIAG: (cachekey) cachekey/cachekey.cc:372:appendPrefix() added URI capture prefix, key: '://example-cdn.com:8080/path/file'
[Aug 11 11:30:41.801] {0xb000c000} DIAG: (cachekey) cachekey/cachekey.cc:663:finalize() finalizing cache key '://example-cdn.com:8080/path/file' from a remap plugin
$ curl  https://example-cdn.com/path/file
Results in the following log:
[Aug 11 11:30:48.543] {0xb000e000} DIAG: (cachekey) cachekey/cachekey.cc:208:CacheKey() setting cache key from a remap plugin
[Aug 11 11:30:48.543] {0xb000e000} DIAG: (cachekey) cachekey/cachekey.cc:219:CacheKey() using remap uri 'https://example-cdn.com:8443/path/file'
[Aug 11 11:30:48.543] {0xb000e000} DIAG: (cachekey) cachekey/pattern.cc:277:replace() replacing:'$1://$2' in pattern:'http(s)?://([^?]*)', subject:'https://example-cdn.com:8443/path/file'
[Aug 11 11:30:48.543] {0xb000e000} DIAG: (cachekey) cachekey/pattern.cc:313:replace() replacing '$1' with 's'
[Aug 11 11:30:48.543] {0xb000e000} DIAG: (cachekey) cachekey/pattern.cc:313:replace() replacing '$2' with 'example-cdn.com:8443/path/file'
[Aug 11 11:30:48.543] {0xb000e000} DIAG: (cachekey) cachekey/pattern.cc:323:replace() replacing '$1://$2' resulted in 's://example-cdn.com:8443/path/file'
[Aug 11 11:30:48.543] {0xb000e000} DIAG: (cachekey) cachekey/cachekey.cc:372:appendPrefix() added URI capture prefix, key: 's://example-cdn.com:8443/path/file'
[Aug 11 11:30:48.543] {0xb000e000} DIAG: (cachekey) cachekey/cachekey.cc:663:finalize() finalizing cache key 's://example-cdn.com:8443/path/file' from a remap plugin
Please let me know if any questions or problems!
Cheers,
—Gancho

On Jul 26, 2018, at 8:41 AM, Evan Zelkowitz<EMAIL_ADDRESS>wrote:
I was doing some testing with cachekey and managed to make one that crashed it:
@plugin https://github.com/plugin=cachekey.so @pparam https://github.com/pparam=--separator= @pparam https://github.com/pparam=--remove-all-params=true @pparam https://github.com/pparam=--remove-path=true @pparam https://github.com/pparam=--capture-prefix-uri=/http(s)?://([^?]*)/$1://$2/
The (s)? is what was added to cause the crash
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/apache/trafficserver/issues/4015, or mute the thread https://github.com/notifications/unsubscribe-auth/AKCQBFXuFee2IngsBvYXB0U51t00Dmijks5uKeMmgaJpZM4ViEzD.

@ezelkow1 Sounds like this can be closed?

@mlibbey yes


Update README.md

#13
Added Jetson TX2 camera issue to known issues.

Hello,
I think it's only a temporary fix for your specific case. In other systems, camera id = 0 is often corresponding to the first working camera, so modifying this parameter may not solve the problem. Using camera id is also not a recommended way on a production system.
I think we should not add this into README.md. Otherwise, we need to add a more stable way to identify the camera, such as product id or serial number.


Designer lists - table headings are misaligned

Describe the bug
Looks like the drag handle has been added in the wrong place so the table headings/table data are shifted across one
To Reproduce
Steps to reproduce the behavior:

Go to designer
Click on edit lists, and edit a list

Expected behaviour
text should line up with text input, value with value, etc
Repository

Designer

Desktop (please complete the following information):

OS: OSX 10.15.14 (likely to be across board)
Browser: chrome, safari
Version: Chrome - 83.0.4103.116 (Official Build) (64-bit), safari: Version 13.1

Hi Jen,
This issue has already been fixed?

Ah I see, I guess it hasn’t been deployed yet. Could you tag the PR it was fixed and closed the issue then? Thanks!


Error when requesting invoice

Hello,
I am getting the following error when clicking to pay for the image and requesting an invoice. I had everything working but now this happens.
POST /_invoice 500 47.941 ms - 148
Error: write EPROTO<PHONE_NUMBER>78528:error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol:../deps/openssl/openssl/ssl/s23_clnt.c:827:
at _errnoException (util.js:1003:13)
at WriteWrap.afterWrite [as oncomplete] (net.js:863:14)

GET /IMG_4349.jpg?preview 200 5.690 ms - 5214134

What URL did you configure for --charge-url when starting filebazaar?

Default
charge_url: https://localhost:9112

Try http://localhost:9112/, not https://

Or just don't set charge_url at all, http://localhost:9112/ is the default value you get if nothing is set.

That was it, thanks very much.


tests are missing from pypi sdist tarball

Hi! I'm packaging python-identify for Arch Linux.
We usually use the pypi sdist tarballs for packaging, as pypi.org offers a unique naming interface for tarballs (which is important in a build environment).
It would be great, if the tests could be included in an upcoming release of the sdist on pypi.org, as they ensure, that users can run tests against their environment before using a package.

hi, please use the github source tgz -- thanks!


Skip "Scan on push" when the Clair Vuln DB is not ready.

To avoid the situation when the vulnerable image is scanned automatically, but no vulnerability is reported.

Fixed in #2798


String damp indications for harp

In scores hand damping symbols can pop up everywhere, they are rarely connected to notes.

Yet in MEI it is only possible to encode them as artic.
In modern notation they are sometimes to something that looks like a glissando to muffle a particular group of notes.
(See The Sacred Harp Notation Guide and section Hand damping in Gould pp. 364-366.)
I propose to remove the values damp and dampall from data.ARTICULATION and have another control element for that purpose. Maybe it could/should be combined with what is currently harpPedal (see #643).

artic can occur directly in layer, and has @plist so you can attach the 'active participant' IDs.
It can also take various @tstamp values. Additionally, @artic could be modified to take @startid?
Just proposing alternate solutions...

Good point. But is harp damping an articulation at all? Or why are there special elements for piano pedal and laissez vibrer, which are closer related to harp damping than a marcato.

🤷

If we do choose to do a new element, I propose it not be called <damp>. Otherwise the brass might mistake it as a direction to empty their spit valves. 😀

The statement that "Yet in MEI it is only possible to encode them as artic." isn't true.  In MEI "secondary" entities, such as articulations, can either be associated with a "primary" entity, either via attributes or child elements of the primary entity, or associated with a staff, through the use of a so-called "control event".  When there is no specific control event, as is the case with damping symbols, one can/should use the generic control event <dir> with appropriate content -- in this case probably <symbol>.  Position and all kinds of other stuff can be recorded about the directive using the attributes of <dir>.
Some entities, such as <artic>, have been elevated from attributes and/or event children to control event status.  One justification for this, among others, is that the entity requires unique attributes of its own.  Obviously, every attribute or child could be elevated in this way, but doing so would cause a tremendous explosion in the number of new control events.  I admit haven't thought about it a lot, and I'd be happy to be proven wrong, but I don't think elevating @artic values of 'damp' and 'dampall' to <damp> (sorry, Andrew) is justified.

If one thinks that damping symbols aren't articulations, then using <artic> to encode them would be "tag abuse".

In my opinion they do look like control events. So maybe another idea would be to have damp to qualify a <dir> as suggested here https://github.com/music-encoding/music-encoding/issues/712 ?

@lpugin, that's fine, but adding @func will lead to confusion between it and @type even if @func uses a closed list of values.  I prefer a semi-closed value list for @type.

I don't. I prefer to separate them and leave @type totally free for project specific uses.

That's fine until the values in @type and @func are the same.  For example, if I use "damp" as the value of @type, Verovio will ignore my value until I put it in @func.  But doing so will a) cause me to repeat data, and/or force me to change my project-specific needs.
On the other hand, if there's a single place to put project-specific and Verovio-specific info (which is what @func is, I think) , then Verovio (or another app) can determine its behavior based on whether an approved value has been used or not and encoder confusion has been avoided completely.  If an approved value has not been used, Verovio can gleefully ignore it.

My point is that if we start (again) to fill @type with pre-defined values, then @type is not completely free for project specific needs. In other words, documenting its use will be more difficult, and that will introduce confusion. Your argument of putting damp in @type and introducing then duplication with @func or the need for the data to be changed could be used for any attribute (e.g., <accid func="edit" type="edit">)
Nothing is meant to be Verovio-specific, even though I understand that anything coming from me will look like it 🤣. Verovio can without problem handle values in @type, with no list, an open list, or a close list. It is only an idea to improve the semantic in MEI, and I am happy to hear that it is a bad one.

The problem by using dir is that this would be a visual only approach, which isn't very machine readable. What about e.g. MIDI information? And you could only encode the simple sign, but would not be able to add information about the affected pitch range.
Arguing that basically everything can be encoded with dir, I wonder then why we do have specialized elements at all? Why is there a dedicated element for piano pedaling, and not a similar element for harp? Only because there is much more piano music than harp music available? When we encounter commonly used specialized notation, there has to be a way to address this specifically.

Of course, there has to be a way to encode specialized directives and I don't oppose creating special elements when necessary.  The discussion at the moment is about whether it's necessary to create a new <damp> element.  What specific characteristics / attributes would you like <damp> to have that <dir> doesn't already supply?  MIDI is a bit of a canard, so it would be best to avoid it right now, but affected pitch(es) might be worth recording.  Why isn't @plist adequate for this?

This whole discussion reminds me about the argument I've given elsewhere: Sometimes, music notation simply doesn't want to follow our criteria for what is a control event and what is a note modifier. I'm fully aware that opening the door or blurring that line will cause madness, but maybe this is just the madness of the thing we're trying to encode?
If we'd agree that something along these lines is the underlying problem, then we should not rush into a solution here, but instead take some time to think this through as much as possible. We have quite some such topics in the backlog that need intense discussions and final decisions, but we're usually lacking the time to cover them as carefully as necessary. Maybe it's time for a dedicated modelling workshop, but I can't see how this should be accomplished in digital format…

I don't really see a difference between a control event and a note modifier. As mentioned, <artic> can be contained by both layer and note. If you need to express it with standoff notation, then that's OK. If you want to apply it to a specific note, then that's OK too.
I would second @lpugin's wish not to use @type. I too remember saying "Oh, just use @type for ... ". I also seem to remember pretty strong arguments to not propagate that once they were cleaned up, and the introduction of @nnnntype attributes (like @notationtype, etc.) so that we could be specific about what is meant by the value carried in type.
The suggestion about adapting harpPedal is interesting, but with my relatively poor knowledge of harp playing techniques, is this OK? Are there other ways of damping harps other than a pedal? Can you dampen the strings with your hands? Does that have a different indication?

Harp pedals are used to select the pitches of the strings.  They have nothing to do with damping, which is done entirely with the hands.

Well I could imagine a composer wanting the player to dampen the strings with the feet.
But what I was thinking of is to have an element for harp techniques, so rename harPedal to simply harp (or something similar) and use that for all things the harpist has to do except from plucking the strings (which of course would still be indicated by the notes).

Sorry, but that's going in the wrong direction.  Pedal settings can't be mixed with general technique indications because harp pedaling is specific, e.g., has specific function and data requirements.  <harpPedal> sets which pitches are actually available and is used to render a specific diagram showing the pedal settings.  When used for damping, a generic <harp> element would be overburdened with the attributes necessary for pedaling --
<harp c="f" d="f" e="f" f="f" g="f" a="f" b="f"> [damp sign] </harp>

This will only lead to confusion.


Forsetisecurity.org dev

Slack invitation URL + terraform import script documentation updates.

All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter.
We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only @googlebot I consent. in this pull request.
Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the cla label to yes (if enabled on your project).
ℹ Googlers: Go here for more info.

@gokeefe Can you please read through this and add the consent comment if you are OK with your commit being contributed to the project? Thanks!

@googlebot I consent.


error with account exemple get_all_transactions.py

I tried this address : '0xfbb1b73c4f0bda4f67dca266ce6ef42f520fbb98' , it took a while, then I got this error :
Traceback (most recent call last):
File "get_all_transactions.py", line 13, in
transactions = api.get_all_transactions(offset=10000, sort='asc', internal=True)
File "/usr/lib/python3.6/site-packages/etherscan/accounts.py", line 84, in get_all_transactions
trans_list += req['result']
TypeError: 'NoneType' object is not iterable
thanks for the work

Recent merge from @taylorjdawson should fix this.


chore: add peerid for [fc.bus.events]

Motivation
Prep for mainnet.
As per instructions on (ref):

Change Summary
Add peerid for @pjc (mainnet → fc.bus.events)
Merge Checklist

[x] PR title adheres to the conventional commits standard
[ ] PR has a changeset
(← N/A?? Please let me know if you need this generated. My reading of "CONTRIBUTING.md" guide indicated this was for meaningful changes only....this is a one liner)
[ ] PR has been tagged with a change label(s) (i.e. documentation, feature, bugfix, or chore)
[x] PR does not require changes to the protocol
[x] All commits have been signed

Additional Context
Who is this?:

Phil Cockfield
https://warpcast.com/pjc
Peer Id: 12D3KooWBhm9XdafZiBWPncDVcvMhcmV3kLFLnBiS83CjY833sWN

Identity created on dev machine (yarn identity create), prior to standing up full cloud-process to run the hub (which is targeted for subdomain fc.bus.events on bus.events)

PR-Codex overview
This PR adds a new peer to the allowedPeers list in allowedPeers.mainnet.ts file.
Detailed summary

Added 12D3KooWBhm9XdafZiBWPncDVcvMhcmV3kLFLnBiS83CjY833sWN to the allowedPeers list.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

Regarding "No Changeset"

@philcockfield may need to rebase, but otherwise lgtm

Thanks @sds


Fix pod annotation indentation

What this PR does / why we need it
Current pod annotation will result following result and make helm failed to deploy

STDERR:
  Error: YAML parse error on xxx/charts/promscale/templates/deployment-promscale.yaml: error converting YAML to JSON: yaml: line 38: did not find expected key
  Use --debug flag to render out invalid YAML

Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #

Special notes for your reviewer
Checklist

[x] Chart Version bumped
[x] CLA signed

 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.

@zfy0701 can you bump the chart version again?  That should fix the conflict.  Everything else looks good!

@zfy0701 can you bump the chart version again? That should fix the conflict. Everything else looks good!

done merging


[Feature]: Plugin apply in plugin

What problem does this feature solve?
As a infrastructure developer, we provides many plugins for team member to assemble for match the business cases.
Such as:

pluginContentSecretly -> do some secretly thinks like: remove invalid charsets / remove domains ...
pluginMultiBundle -> call modifyRsbuildConfig to add preset environments

Wanna to add the pluginContentSecretly into one of environment sets of the pluginMultiBundle.
Actually I can extract implements of the pluginContentSecretly and partially call the same API method set in pluginMultiBundle, But it's ugly.
The pluginContentSecretly content see like:
const pluginContentSecretly = () => {
  return {
    name: 'plugin-content-secretly',
    setup: (api) => {
      api.modifyRspackChain(chain => {
         chain.plugin('remove-invalid-content-plugin').use(Plugin, [[ ... ]])

        // .... many many other rules in this plugin
      })
    }
  }
}

The pluginMultiBundle content see like:
const pluginMultiBundle = () => {
  return {
    name: 'plugin-multi-bundle',
    setup: (api) => {
      api.modifyRsbuildConfig(config => {
         config.environments = {
           normal: {
             output: {
               target: 'web',
             }
           },
           safety: {
             output: {
               target: 'web',
             }
             plugins: [pluginContentSecretly()], // <- it's not work
             tools: { // <- now only can implement as this
               rspack: {
                 plugins: [
                   new Plugin({ .... })
                 ]
              }
            }
           }
         }
      })
    }
  }
}

What does the proposed API look like?
We can apply the plugins in another plugin, I think the plugin lifecycle well be modify. Should discuss about such how about the setting override, plugin order, etc..
const pluginContentSecretly = () => {
  return {
    name: 'plugin-content-secretly',
    setup: (api) => {
      api.modifyRspackChain(chain => {
         chain.plugin('remove-invalid-content-plugin').use(Plugin, [[ ... ]])
      })
    }
  }
}

const pluginMultiBundle = () => {
  return {
    name: 'plugin-multi-bundle',
    setup: (api) => {
      api.modifyRsbuildConfig(config => {
         config.environments = {
           normal: {
             output: {
               target: 'web',
             }
           },
           safety: {
             output: {
               target: 'web',
             }
             plugins: [pluginContentSecretly()],
           }
         }
      })
    }
  }
}

Recursively registering plugins may not be a good idea, here is an reference: https://github.com/vitejs/vite/issues/2484

I think Rsbuild can support nested plugins config, so users can return an array of plugins in a plugin function:
export default function myPlugin() {
  return [
    fooPlugin()
    barPlugin()
  ];
}

I think Rsbuild can support nested plugins config, so users can return an array of plugins in a plugin function:
function myPlugin() {
  return [
    fooPlugin()
    barPlugin()
  ];
}

export default {
  plugins: [myPlugin()]
}

Okay, This cannot solve this problem, but seems it's helpful for preset to select plugin sets.

Recursively registering plugins may not be a good idea, here is an reference: vitejs/vite#2484

Sound good, I think what if we expand full Rspack configuration can solve it same as the issue of vite.


Add timer to check connection between OCU and JRB

Description
If the Jaus Ros Bridge loses connection with the OCU, The mux will still sending commands to the Mux. Because the Jaus Ros Bridge has more priority than the Autopilot, the vehicle won't receive commands from the mission control / Autopilot.
Taking into accout that the OCU sends "Manual Command" to the Jaus Ros Brids every 1 second, this PR adds a timer in the Jaus Ros Bridge that check the connection with OCU.
Type of change
Please mark options that are relevant.

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] The code builds clean without any errors or warnings

How To Test
To check if the timer is working, the connection between the Jaus Ros Bridge and the OCU must be cut manually.

So two things:
It takes about 5 seconds to stop after disconnecting. This may be a limitation with the detection of loss of comms in which case we will have to just deal with it.
If it reconnects it starts going the speed it disconnected at.

This fixed the reconnect error where it started again after reconnecting.
Current Bug: The vehicle now drops to 0 rpm and immediately back to commanded every 3 seconds when connected.


Fix/SDK error message on network error was showing no details

Readiness checklist

[ ] I added/updated tests.
[x] I ensured that the PR title is good enough for the changelog.
[x] I labeled the PR.

When there is a network error between SDK and connector the errorPayload is undefined and the SDK crashes with an can not read property id of undefined


msglist: Make tapped-narrow-link handling better and more explicit

(This is atop #5694.)
Better, with this commit that fixes #5698:
msglist: Open "new"-format stream links in-app even when stream is unknown

And more explicit, with this commit:
messagesActions [nfc]: Handle unexpected narrow links more explicitly

Fixes: #5698
Fixes: #5702

Thanks for the revision! LGTM; merging.

Thanks for the review!


ANDROID_HOME???

[error] set the env variable ANDROID_HOME pointing to your Android SDK
Project loading failed: (r)etry, (q)uit, (l)ast, or (i)gnore?
but i both setted ANDROID_HOME and ANDROID_SDK_HOME, and echo $ANDROID_HOME works good.
How to fix this error?

+1 I've noticed this as well.
Having sdk.dir= in local.properties can handle this issue, but weirdly I just came across other project where this trick doesn't work...  I'm very confused.
Needles to say that sbt console works perfectly well ether way.

@WeiChou   Ok, I think I got it. I assume you are on mac os.
In this case the solution is simple - IDEA doesn't read on exported paths, to pass it variable you should run launchctl setenv ANDROID_HOME $ANDROID_HOME before running IDEA.

+1 Notice this too, thanks @WeiChou for the workaround in Mac OS


Add new Tien Giang University

Add new Tien Giang University to lib

@windcloudit Pull request merged. Thank you!


[upgrade] Add ability to upgrade system state at epoch change

This PR adds the following things:

Added a function that maps from protocol version to system state version. This allows us to decide what would be the new system state version in the new epoch.
Pass the system state version in the advance epoch transaction, and if it changes, we update the version and also upgrade the system state object. The actual upgrade doesn't happen today, and that will only be added when we have a real update. We will need to figure out a way to upgrade it for testing.

So to summarize, we will stick with this solution for now, and optimize the flow latter.


Alexa configuration details missing text

Describe the bug
upgrading to latest version of HA , and replacing the pi 3 to pi4 the integration was asking a reauth in loop.
disinstalled everything and during the reinstall the main mask is as below
To Reproduce
Steps to reproduce the behavior:

Go to integration add alexa media
Click on '....'
Scroll down to '....'
See error

Expected behavior
a mask with contents
Screenshots

System details

Home-assistant (249):
Hassio (Yes/No): (Please note you may have to restart hassio 2-3 times to load the latest version of alexapy after an update. This looks like a HA bug).
alexa_media  (latest):
alexapy (version from pip show alexapy or HA startup):
Amazon 2FA is enabled (y/n). We will not debug login issues if unanswered:

Logs
Please provide logs. We'll be most likely asking for them anyway.
Additional context
Add any other context about the problem here.

Hard refresh your browser cache.


Support for ExpiryOptions on BlobStore requests

I tried setting the expiry option on some blob store request, but I could not find the appropriate way to do so.
Setting an expiration is described in the official documentation:
https://docs.microsoft.com/en-us/rest/api/storageservices/set-blob-expiry
So far I could not figure out how I could send such options. I tried setting those parameters through the metadata field, but this lead to the following result.
let mut metadata = Metadata::new();
metadata.insert("x-ms-expiry-time".to_string(), "300000".to_string());
metadata.insert("x-ms-expiry-option".to_string(), "RealtiveToCreation".to_string());
let res = container
  .as_blob_client(blob_key)
  .put_block_blob(blob_data.clone())
  .content_type("text/plain")
  .hash(&hash)
  .metadata(&metadata)
  .execute()
  .await.unwrap();

The header was transformed into
  headers: {
    "content-length": "181",
    "x-ms-blob-type": "BlockBlob",
    "content-md5": "cew9Xo2MS8dQ+UyCtsta3w==",
    "content-type": "text/plain",
    "x-ms-meta-x-ms-expiry-option": "RealtiveToCreation",
    "x-ms-meta-x-ms-expiry-time": "300000",
    "x-ms-date": "Fri, 11 Jun 2021 15:23:19 GMT",
    "x-ms-version": "2019-12-12",
    "authorization": "SharedKey ******",
  },

What would be the correct way to set the expiration?
If this feature does not yet exist, what would be the best approach integrating this into the sdk?

Hi @JensWalter, no, the blob expiry is not currently supported by the SDK. The expiry feature is available since version 2020-02-10 but the SDK still targets 2019-12-12 as defined here: https://github.com/Azure/azure-sdk-for-rust/blob/fb5598b48d7523804c712d7ac5f6e0b5aa9f2066/sdk/storage/src/core/clients/storage_account_client.rs#L20
The metadata function you are using is related to this feature: set-blob-metadata. This basically attaches arbitrary key-value pairs to a blob. That's why your headers get mangled.
While there is no way to customize the service level nor pass extra headers right now, we are currently migrating to a pipeline-based approach that will be less strict, possibly allowing users to fully customize the headers sent to Azure.

OK, thanks for the explanation.
So I will wait for the necessary migrations to happen first.
Let me know when I can help in any way to get this into the SDK.

Support for blob expiry was added in #913


Add missing 'gl' dependency in useMemo()

Adding the gl dependency solves #611

that's it? :-D thanks for the fix!

Thanks for starting on this! We recently adjusted the react-hooks/exhaustive-deps eslint rule to help prevent these issues in the future. There are a few other spots in canvas.tsx that need to be adjusted as well. The rewrite isn't straight-forward though as strictly adding in the recommended dependencies causes breaking changes there. I'm hoping to get some time in the next week or so to help rewrite that file.


Allow to authorize with ZooKeepe by zooKeeperAuth.

Fixes #723

Can you rebase against master again?

@brndnmtthws done


Correct subdomain wildcard filter

In uBO *.domain.example does not filter domain.example and all of its subdomain, as I always though. We need to correct the current filter to achieve the desired behavior. I have to clarify how uBO blocks domains and subdomain.
It is important to note that we have different forms of filters in the current blocklist:

*://domain.example/*: domain
*://*.domain.example/*: domain and subdomains
*://domain.example/abc/*: domain and path. We might convert this form to a domain only filter (*://domain.example/*).

This seems to be the solution. We might use filters with the syntax ||example.com^.
I need to test it, but I didn't find time for now'

Seems to work:
*://domain.example/* ➡ ||domain.example^
*://www.domain.example/* ➡ ||www.domain.example^
*://*.domain.example/* ➡ ||domain.example^
*://domain.example/abc/* ➡ ||domain.example/abc$all

https://github.com/quenhus/uBlock-Origin-dev-filter/pull/149#issuecomment-1162206125

One may use filters in the branch test--feat-correct-ubo-wildcard to test if the new filter syntax is correct. Will merge next week if nobody finds an issue.
Example of filter you may test: Filter

This doesn't seem to be correct anymore. I am having an issue where it is not targeting any subdomains with the normal url and it tells me bad domain when I try anything involving * or ||.


Update README

Update README to reflect changes in game UI and UX design

Can i be given the opportunity to work on this?

I'd like to handle this task.

I am new to open source.
To address this issue, I would update the README to include a dedicated section that points out the changes of the game's UI and UX design. Provide before-and-after screenshots to visually show updates. Document new features, changes in layout, and enhanced user workflows so that contributors and users understand the reasoning behind the redesign.

I would like to work on this issue

Can I try solving this issue?

Is it okay if I take this?

Can I tackle this one?

Can I tackle this one?

Hello I'm Ekene, a frontend and blockchain developer with proficiency in Rust/solidity, Typescript and  react/next js, and I’m excited about the opportunity to collaborate and bring my skills to the table.
Can i handle this task

With my solid understanding of typescript and Cairo and my diverse contributions to open source projects, I can tackle this project by understanding the issue in the readme file and updating it accordingly
Please assign me.

@princeibs Thanks for the opportunity


Use decorators to serialize subclasses of known custom types

This resolves #446 and also resolves #555.
More work is required, and there also needs to be some more discussion in order to determine whether this would better be supported by some updates to the standard. Also, we need to evaluate current examples in GWCS, Astropy, and possibly Sunpy to evaluate how this can be improved.
cc @nden, @Cadair

Coverage decreased (-0.01%) to 93.843% when pulling 86eeae02fe1c2d238cdd3640d3b07d6ab6513335 on drdavella:subclass-decorator into 4976a5988c24a6545c9ace603637df82a5b49cc8 on spacetelescope:master.

@nden sorry for ignoring this for the past week, although I suspect you've been busy with other things too 😉.
I'd like to move forward with this if it's still useful to you. But I think we need to figure out how to support this kind of feature in the standard itself. I'm uncomfortable with having our implementation that adds subclass attributes willy-nilly.
We could consider modifying the tags themselves in the way I described above, but ultimately I think that's pretty heavy-handed and might be difficult to replicate in future implementations of ASDF.
I wonder if we can just make the subclass attribute a special word during validation? It would have a similar status to existing attributes like tag and description. We can encode this in the standard and update our validators to handle it properly.

The current implementation of this requires no changes to the standard. I have added important caveats to the documentation, so it should be clear that this is not necessarily a stable feature. Introducing it now should allow other packages to experiment with it. Eventually we may want to have a discussion about whether we can make changes to the standard to better support this.

I'm going to go ahead and merge this so it gets pulled in by repos that test against master. It shouldn't affect any existing functionality, but it's always good to confirm.


Stormblessed: Watch<EMAIL_ADDRESS>

Stormblessed requests the watch of the watch_keyword<EMAIL_ADDRESS>See the MS search here and the Stack Exchange search here.

<EMAIL_ADDRESS>has been seen in 1 true positive, 0 false positives, and 0 NAAs.

!!/approve

Approved by double-beep in Charcoal HQ


Team 5 - Polish off current gameplay and fix current bugs

Description
This feature is to finalise the backend of the stations and to ensure that they work as intended and fix bugs and ensure that components are fully tested. Additionally, we want to ensure that all of the parts can work together and ensure compatibility between these components. Also, code will be aimed to be cleaned up and tidied.
SubFeature/component

add loggers to the classes
ensure stations work as intended
write tests for station - player interaction
Clean up existing code
fix any bugs discovered during this process.
Add item acceptance to item handlers (done)

Dependencies
This feature relies on all previous tickets having some level of completion so that we are able to polish them.
Completion Deadline: Oct. 3
Members

Hayden
Zach
Callan
Nic
Andi

Closed since completed


Support of Django manage.py console

Please allow to use EnvFile in
https://www.jetbrains.com/help/pycharm/2016.1/running-tasks-of-manage-py-utility.html
picture: http://joxi.ru/RmzQLZ4tzd4jrO

This is no feasible to implement considering current design of the plugin so it won't be included in v2.0 but may be added in future. Stay tuned.

Closing in favor of #7.


chore: Configure Dependabot to update npm packages and GitHub Actions

I will hold off merging this as we haven't done much changes to this repository since we released it for helping folks migrate to v7. Updating current dependencies might break the tool. So we should do an update of this project as a whole first before we merge this PR.


[REFACTOR] Move sqlite3, firebase-admin to peer

Optional dependencies does not work as expected and installing both sqlite3 and firebase-admin for all apps/builds is not good at all :disappointed:
BREAKING CHANGE (v2)

OK, --no-optional flag is working, but all dependencies are added to package-lock.json and I don't know if Firebase is installing or not optional dependencies :thinking:
Maybe we should just publish<EMAIL_ADDRESS>and<EMAIL_ADDRESS>versions.


i get this

/tuxdump/src/formatter.cpp:6:10: fatal error: libconfig.h++: No such file or directory
#include <libconfig.h++>
^~~~~~~~~~~~~~~
compilation terminated.
CMakeFiles/tuxdump.dir/build.make:62: recipe for target 'CMakeFiles/tuxdump.dir/src/formatter.cpp.o' failed
make[2]: *** [CMakeFiles/tuxdump.dir/src/formatter.cpp.o] Error 1
CMakeFiles/Makefile2:69: recipe for target 'CMakeFiles/tuxdump.dir/all' failed
make[1]: *** [CMakeFiles/tuxdump.dir/all] Error 2
Makefile:129: recipe for target 'all' failed
make: *** [all] Error 2
halp ples? :(

Did you follow the build instructions?  In particular you need to run:
git submodule update --init --recursive
It depends on 3rd party libraries in order to compile.

Turned out this was an issue with the way I was handling the internal libconfig when it isn't installed on your system.  I pushed a commit which should fix this.  Thanks for the report.


SPDK engine is responsible for collecting the snapshot info and actual size

This PR fixes part of this issue: https://github.com/longhorn/longhorn/issues/7641

@shuo-wu Will you update instance-manager after getting merged?

LGTM


check data issues identified Jan 2022

@mawilliams99 , let's prioritize dealing with the data issues that Valentyna identified.
I've created this file from the one she sent. Let's fill in our responses in the comments field. I will give it a quick review to fill anything that I should fill.
A couple general comments:

It's likely that all the 0.0 values are both legitimate and meaningful.
Referring to the data location within source field should solve a lot of these

Okay I’ll work on this today. Thank you!
Get Outlook for iOShttps://aka.ms/o0ukef

From: Kristina Anderson-Teixeira @.>
Sent: Monday, January 24, 2022 8:43:35 AM
To: forc-db/IPCC-EFDB-integration @.>
Cc: Williams, Madison @.>; Mention @.>
Subject: [forc-db/IPCC-EFDB-integration] check data issues identified Jan 2022 (Issue #32)
External Email - Exercise Caution
@mawilliams99https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmawilliams99&data=04|01|WilliamsM%40si.edu|87be9b63bab34183bfb108d9df3f8506|989b5e2a14e44efe93b78cdd5fc5d11c|0|0|637786286183115802|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=yd6v0xicYt5Z%2FIGMrhIUi7hv%2BHE57tnQvjm0YvIQucI%3D&reserved=0 , let's prioritize dealing with the data issues that Valentyna identified.
I've created this filehttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fforc-db%2FIPCC-EFDB-integration%2Fblob%2Fmain%2Fdoc%2Fdata_review%2F2022_01_Data_check.csv&data=04|01|WilliamsM%40si.edu|87be9b63bab34183bfb108d9df3f8506|989b5e2a14e44efe93b78cdd5fc5d11c|0|0|637786286183115802|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=Nxosqm0aEjlBUGHmrZ2MeFGJGX6yAJQDyxsURwGcnpk%3D&reserved=0 from the one she sent. Let's fill in our responses in the comments field. I will give it a quick review to fill anything that I should fill.
A couple general comments:

It's likely that all the 0.0 values are both legitimate and meaningful.
Referring to the data location within source field should solve a lot of these

—
Reply to this email directly, view it on GitHubhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fforc-db%2FIPCC-EFDB-integration%2Fissues%2F32&data=04|01|WilliamsM%40si.edu|87be9b63bab34183bfb108d9df3f8506|989b5e2a14e44efe93b78cdd5fc5d11c|0|0|637786286183115802|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=B6u5vnD2i3HHynVI9B2V13NTMwp0okBIrtd%2FciisKsE%3D&reserved=0, or unsubscribehttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAKITRFN5JMCS4JRPJ62FGQDUXVJQPANCNFSM5MVNHQNQ&data=04|01|WilliamsM%40si.edu|87be9b63bab34183bfb108d9df3f8506|989b5e2a14e44efe93b78cdd5fc5d11c|0|0|637786286183115802|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=mqEp83YCaxjGQN276dmMlIO46Tkety%2FqigOaIQoxEFU%3D&reserved=0.
Triage notifications on the go with GitHub Mobile for iOShttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04|01|WilliamsM%40si.edu|87be9b63bab34183bfb108d9df3f8506|989b5e2a14e44efe93b78cdd5fc5d11c|0|0|637786286183115802|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=hsFSuPuC%2FcNS7icpOHzp8Aual9ddCUODlupJ5xdEDb4%3D&reserved=0 or Androidhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04|01|WilliamsM%40si.edu|87be9b63bab34183bfb108d9df3f8506|989b5e2a14e44efe93b78cdd5fc5d11c|0|0|637786286183115802|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=IKzqtFQhXtj3kVs7%2F6Ln98PMdSPfJfFXsyh%2BoBPsXiQ%3D&reserved=0.
You are receiving this because you were mentioned.Message ID: @.***>

@ValentineHerr


fix: rest api contract deployment issue

Addresses #262

This is blocked. @MissingNO57 can you have a look at this please?

@5A11 looks like workaround from @MissingNO57  is a good way to solve this issue.
assume it's ready to be merged in


remove ilmn-tes namespace when not used

@skanwal can discuss this in our meeting tomorrow. Looks like we can remove them from expressions but for the tool listed, we should probably just add in the ilmn-tes requirements?

@alexiswl - Yes, lets discuss before making changes.

Looks like the project token expired, which seems weirdly short since I only updated them a few weeks go?

Also can we fix the tool first (add in the ilmn resource requirements there) before merging

Also can we fix the tool first (add in the ilmn resource requirements there) before merging

@alexiswl - you're referring to this tools/create-dummy-file/1.0.0/create-dummy-file__1.0.0.cwl?

Yep

@mr-c - can you please make the suggested change https://github.com/umccr/cwl-ica/pull/115#issuecomment-1240031436?

@mr-c - can you please make the suggested change https://github.com/umccr/cwl-ica/pull/115#issuecomment-1240031436?

Sorry, I don't understand the exact request.

Looks like the project token expired, which seems weirdly short since I only updated them a few weeks ago?

Ah likely an issue when running the action from a fork and not having access to the secrets, so this checks out.

Sorry, I don't understand the exact request.

Yup no stress happy to do this on our end. Will close this PR and merge your branch into a branch on our remote first and add in the resources to that tool on that branch. Then when I do the PR the sync GH action will work too.


Calculated EMA seems not accurately

I am trying to calculate EMA and SMA of the same data values. However, the result is the same.
When comparing to TradingView's calculated EMA, it's not matched.

Same for MACD

Probably because it's using EMA by default

@redstrike EMA looks correct. Depending on the parameters they can yield the same results or not.
Look at this example:
const SMA = require('technicalindicators').SMA
let period = 3;
let values = [1.5554, 1.5555, 1.5558,1.5560];
                SMA.calculate({period : period, values : values})
const EMA = require('technicalindicators').EMA
let period = 3;
let values = [1.5554, 1.5555, 1.5558,1.5560];
EMA.calculate({period : period, values : values})

@juanvisoler I did an EMA calculation with a larger dataset before trying the above simple example and compare it with other true sources such as TradingView, and believe that EMA result is not accurate.

@redstrike can you give an example?

finmath's EMA result is more accurate as expected.
Also, I compare the result with TradingView's calculated result, so I want to report this issue.
If you believe that technicalindicators' EMA result is correct, then I have no more comment.

我用EMA计算的结果也是有问题哎

我用EMA计算的结果也是有问题哎

是我错了，当数据量较小时似乎看起来计算结果似乎不正确，但当数据量足够大时是正确的，这个库非常棒

我用EMA计算的结果也是有问题哎

是我错了，当数据量较小时计算结果似乎不正确，但当数据量足够大时是没问题的，这个库非常棒

唯一的遗憾是只能nextValue不能updateCurrentValue

@anandanand84 can you please look into this issue please?
looks like this is what's causing the issue in MACD(EMA based) as mentioned here: https://github.com/anandanand84/technicalindicators/issues/249#issuecomment-1321147767

Also comparing it to TradingView's EMA and seems incorrect


Swap prepend-text phrase descriptions

Closes https://github.com/cpsolver/Dashrep-language/issues/15

Also, the text "s-n If the target phrase is initially empty, the space is not inserted." should be moved from the "prepend-text-no-space" description to the "prepend-text" description.  The other part of this change looks good.  Liam, thank you for finding this error!

Hi Richard (@cpsolver),
I have made the suggested changes to this PR.
Kind Regards,
Liam


TimedConfigReloadStrategy as deamon timer?

The TimedConfigReloadStrategy currently uses a user-thread timer. This causes our program to not shut down correctly since the timer is keeping the process alive.
Would it be possible to make this deamon instead?

Beautiful, works like it should now 👍


[6.0] Omit Mentioned In section on module pages (#811)

rdar://125512559
This is a cherry-pick of #811 to release/6.0.

Explanation: Omits the Mentioned In section on module pages. This section might be included in the future as the mention logic changes, so this change is in the renderer for now.
Scope: Impacts all module documentation pages when --enable-experimental-mentioned-in is used with DocC.
Issue: rdar://125512559
Risk: Low. This is a small scope change with specific options enabled.
Testing: Added unit test; manual testing with Swift Markdown.
Reviewer: @mportiz08
Original PR: https://github.com/apple/swift-docc-render/pull/811

@swift-ci Please test

Yes. As I wrote in the description (probably too vaguely), this section might appear on module pages in a different location, especially if mention logic becomes aware across frameworks. If that ends up not being realistic next release cycle, we can push it down and just make it a hard rule.

@swift-ci Please test


Robot name - V1

@drosholt @djkotowski Please take a look at our comments and refactor. I really think getting away from calling a proc to generate your names will simplify your code throughout.


flare: init at 1.10

Motivation for this change
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@worldofpeace thank you for your helpful comments! Looks like I simply missed the tags on github :blush:
I didn't see any mention of running those scripts in the readme/install notes that you mentioned, nor have I worked with those sorts of translations before. I suppose I could just pass python or 'gettext' in the nativeBuildInputs and then run the script in the preInstall phase maybe?

I didn't see any mention of running those scripts in the readme/install notes that you mentioned, nor have I worked with those sorts of translations before.

Hmm, now I'm thinking that perhaps they just use them to regenerate them and commit it to the repo.
Probably don't need to do anything for those.


Portal Feedback from UI

It might be useful to enable a feedback button for users to provide feedback about portal function that captures the portal state and lets the user provide a comment and optional contact information, all of which goes to a Github issue.

I cannot really figure out what a good way to take feedback is. It could be related to 1) data or 2) data widgets or 3) website content or 4) general support questions about publishing. We see all on GBIF.org, but the most frequent is by far issues about taxonomy and classification of occurrence records.
Having multiple links isn't ideal, but neither is directing all feedback to one location i suspect.
On GBIF.org we log issues in Github (but left on gbif.org). To begin with we didn't require any login to leave feedback, but that resulted in a lot of spam in the Github repo. So we now require users to login. But that is a GBIF login. That might be a bit weird in this context. But then again it is needed for downloads as well.
Oh, it is tricky I find. Good ideas are welcomed

We (VertNet) gave a webinar on the way we manage feedback via GitHub repositories registered to specific data sets in our registry. We and the dataset publishers have been very happy with it. It has everything everyone needed, let's us opt in to being the middle-man, but connects the person with the feedback directly with everyone interested in the dataset (by watching the repository.

Feedback could be received in many ways

The simplest is to simply add a feedback menu item with a mailing address or a link to ones Github repository.
Then there is the option to use a 3-party provider
And finally there is the option, that we develop some sort of feedback system (act as a middle man and store the data in Github).

Feedback can be on many things

data processing  - best directed at GBIF. But what first appear as a processing issue is often solved at data level and visa versa.
data content  - best directed at the data owner probably. But could be a dead dataset. So perhaps the site owner. Or perhaps GBIF.
UI - best directed at GBIF
prose content (the markdown pages) - best directed at the site owner

It is hard to tell what goes where. Based on GBIF.org the referrer page is an indicator, but by no means a guarantee (feedback on data content is surprisingly often created from an article page).


Update Mixpanel Android SDK to 5.7

Updates the Mixpanel Android SDK to 5.7, which includes support for rich push notifications. Mixpanel Android is currently on 5.8.5 but I opted to just bump to 5.7 in this PR and test 5.8.5 more thoroughly later.
https://github.com/mixpanel/mixpanel-android/releases/tag/v5.7.0

Recreated PR


Scale mutation rate based on the number of alleles for the diploid case

The mutation rate can be scaled based on the number of distinct alleles per site in the haploid case. However, this it not yet implemented for the diploid case. To do this, get_emission_matrix_diploid in lshmm/api.py should be modified.

I think this should do. Does this make sense to you, @astheeggeggs ?
def get_emission_matrix_diploid(mu, num_sites, num_alleles, scale_mutation_rate):
    e = np.zeros((num_sites, 8))
    if isinstance(mu, float):
        mu = mu * np.ones(num_sites)
    for j in range(num_sites):
        if scale_mutation_rate:
            prob_mutation = mu[j]
            prob_no_mutation = 1 - (num_alleles[j] - 1) * mu[j]
        else:
            prob_mutation = mu[j] / (num_alleles[j] - 1)
            prob_no_mutation = 1 - mu[j]
        e[:, EQUAL_BOTH_HOM] = prob_no_mutation ** 2
        e[:, UNEQUAL_BOTH_HOM] = prob_mutation ** 2
        e[:, BOTH_HET] = prob_no_mutation ** 2 + prob_mutation ** 2
        e[:, REF_HOM_OBS_HET] = 2 * prob_mutation * prob_no_mutation
        e[:, REF_HET_OBS_HOM] = prob_mutation * prob_no_mutation
        e[:, MISSING_INDEX] = 1
    return e


[WIP] First version of G2EGM.

Comments, issues, and ideas will follow, but feel free to review.
I'm having some issues with acon still, the segment where all liquid resources are consumed or spent (no liquid savings). I've asked Jeppe for a meeting to discuss what might be going on here.
I should say that some things are on my list, but have been put lower on the priority list due to the acon problems. Such things are: don't hardcode C, D etc as parameters, but pass pass lists or higher dimensional arrays as appropriate (see cleanSegment for an example that doesn't require four specific arrays to be passed), don't use classes for "stablevalue"-things, use functions (I believe such a thing exists in HARK already? couldn't figure out if it was example specific) instead, and more.
The retirement is a standard EGM exercise. Should there be a separate HARK implementation for this?

What kinds of problems?
Probably related to one or both of the kink points?  And maybe how those interact with the discrete choice?

Consider these imshow pllots of the discrete policies (yellow is work)

These will be the solutions if you fully ignore the acon segment. Then consider uncommenting the line that is currently commented out to ignore acon and you get

So either I'm not filtering out the infeasible policies and or endogenous states correctly (c, d, m and n cannot endogenously become < 0.0 and still be feasible solutions to the FOCs), calculating the FOC candidates correctly, or something else. I'm hoping Jeppe and Thomas have seen similar results before and know what the solution is. I believe they do some special handling of infeasible points that I don't, and that might be the answer, but I don't know.

Regarding honoring the NARK, should risk free return factors then follow the Rfree notation somehow? There are two of them, since both investment in A and B is risk free.

I've added some additional commits. Few of them were directly related to the acon thing, but I just had a look, and it seems clear that this comes from the density of the endogenous grid in (m,n) space.
Coarse grid
A too coarse (as in this PR) grid over post decision cash on hand gives policies as above and (m,n) grids as shown below (first one shows all endogenous grid points, second one is zoomed in).

The artifacting is there and the grid is seen to be very coarse in the lower part of (m,n) space).
** Fine grid **

the problem seems to go away.

Regarding honoring the NARK, should risk free return factors then follow the Rfree notation somehow? There are two of them, since both investment in A and B is risk free.

Yes, please use Rfree.  And, generically, there is only ever a single risk free interest rate because if there were two all savers would choose the higher and all borrowers would choose the lower so saving would not match borrowing.

You're describing these results as 'artifacts' which is ambiguous as to whether they might actually be correct solutions to the problem as specified.  The problem itself has discontinuities in behavior, and those can interact with discrete probability distributions in funny ways.  Have you tried solving with the coarse grid that has the artifacts back to some period 0, then constructing a superfine grid for the prior period and solving that?  If so, and you get the same results as with the coarser grid, the result is probably reflecting a correct result to a problem that has some ugly little corners.

Yes, please use Rfree. And, generically, there is only ever a single risk free interest rate because if there were two all savers would choose the higher and all borrowers would choose the lower so saving would not match borrowing.

Okay, then maybe my terminology is wrong.
There are two assets: A and B. If you have a units of A at the end of period t, this will grow to a*R_a in period t+1. Similarly, if you have b units of B at the end of period t, this will grow to b*R_b in period t+1. This is why I'm calling them risk free. You invest one unit and you get R_x units back 100% guaranteed - no chance it'll be anything else.
However, A is fully liquid and B is illiquid in the sense that you can only consume it (or accumulate it in A if you wanted to do that) if you retire. R_a < R_b, so people want to invest (depending on the current state of course) in both.
Is R_b not the return factor of a risk free (although illiquid) asset in this description, or is there a better term than "risk free"?

You're describing these results as 'artifacts' which is ambiguous as to whether they might actually be correct solutions to the problem as specified. The problem itself has discontinuities in behavior, and those can interact with discrete probability distributions in funny ways. Have you tried solving with the coarse grid that has the artifacts back to some period 0, then constructing a superfine grid for the prior period and solving that? If so, and you get the same results as with the coarser grid, the result is probably reflecting a correct result to a problem that has some ugly little corners.

I'm going to push some more commits in the next half hour, but I'm quite certain that it's artifacting in "a bad way" :) I'm certain because I can make them go away simply by increasing precision in the sense that I add more points and interpolate on a finer grid. This, to me, shows that it's not a discontinuity in the solution (they're in there too!). It's basically related to some of the things discussed around pages 94-96 in the paper.

This PR can be removed, given the other DCEGM PR's are much more complete, yes?

Did you mean to write this comment on the DCEGM PR? #206

G2EGM got mashed into DCEGM in my brain.  Ignore.

I want this to continue living, and come back and revisit some of the things in the very near future when DCEGM is settled.

@pkofod, could you update the status of this, now that DCEGM is incorporated in core HARK?

DCEGM is in HARK as a tool that you can use to build a model of mixed discrete and continuous choices... If the EGM step involves 1 post-decision state. It seems to work quite well. G2EGM can also solve the same kinds of models. The "1 post-decision state" case is still solved in a different kind of way than DCEGM though, so G2EGM is not a generalization of DCEGM.
For models that involve 2 or more post-decision states, we cannot use DCEGM anymore (though we can actually solve a series of problems over one state given values of the other state). G2EGM can in principle be used in as high dimensions as you'd like, provided you want to write (or can automate the code generation of) the interpolation code for the number of dimensions you have.
This code is current in the state that the DCEGM code was in before I rewrote it, and split the model out into a REMARK and the "how does it work" out into a DemARK.
I think it's still worth doing, but I think the things that are explicitly linked to the TFI goals are more imporant - unless we end up having to solve a higher dimensional problem.
I could quite easily extract the G2EGM out just like I did with DCEGM, but the DemARK and REMARK parts would take a bit of time to get right.

@Mv77,
In our meeting today we were looking at this old PR which never got finished.  Could you look at it before our call next Monday and we can discuss whether you might be able to polish it off.

@Mv77,
In our meeting today we were looking at this old PR which never got finished. Could you look at it before our call next Monday and we can discuss whether you might be able to polish it off.

Sure, I'll take a look and be up to speed on it by our next call.

I have been revising/using the code and wanted to write an update.
I thought a good way to move forward would be to start the sketch of a REMARK of the G2EGM paper, trying to replicate it. In particular they have these plots where they show which segment is optimal on different parts of the state space. I produced a tool to get similar plots. Here is an example:
The original:

HARK's:

There is some resemblance and the segments' optimality regions are in the same general directions. However there puzzles that I am currently investigating:

dcon is never being highlighted as the optimal segment. Its region seems to be taken over by 'con'.
there are regions to the right where 'con' becomes optimal that shouldn't be there.

Retirement/Working decisions look very reasonable nonetheless:

You retire when you have enough resources, or when your liquid assets (M) are low enough that you retire just to tap into your retirement account.

There is definitely something going on with dcon. If I set the parameters to make asset b bad (Rb = 0.5, chi very small), then the agent should never want to put resources into it, and so the d constraint should always bind. Thus, in principle, 'ucon' should be dominated by 'dcon'.
However, I still get solutions where dcon is never optimal.

Update:
I've found what I think are two bugs.

The fixed C's in acon need to be transposed: they are generated row-wise using limits that make sense column-wise. The current version therefore generates many C-b combinations that imply negative d's and are thus thrown out. This is fixed in https://github.com/Mv77/HARK/commit/62c2e20a6dffafa9cb158cd47965e3dc9355b812. I think it might help with some of the previously documented issues with acon.

There indeed seems to be a major issue with dcon: in my tests, the denominator of the barycentric weights for this segment is always 0! This results in its values never being passed onto the common grid. I'm in the process of figuring out why this happens with this particular segment.

Hmmm, a denominator of zero does sound like a bit of a problem!
Sounds like you are pursuing the strategy of using the tool to solve a
simple problem for which you already know the answer?  (The "rettirement"
problem?).  That's always a good debugging strategy!
On Fri, Jul 24, 2020 at 6:09 PM Mateo Velásquez-Giraldo <
<EMAIL_ADDRESS>wrote:

Update:
I've found what I think are two bugs.

The fixed C's in acon need to be transposed: they are generated
row-wise using limits that make sense column-wise. The current version
therefore generates many C-b combinations that imply negative d's and are
thus thrown out. This is fixed in Mv77@62c2e20
https://github.com/Mv77/HARK/commit/62c2e20a6dffafa9cb158cd47965e3dc9355b812.
I think it might help with some of the previously documented issues with
acon.
There indeed seems to be a major issue with dcon: in my tests, the
denominator of the barycentric weights for this segment is always 0! This
results in its values never being passed onto the common grid. I'm in the
process of figuring out why this happens with this particular segment.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/econ-ark/HARK/pull/200#issuecomment-663753887, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKCK74WLJLKFFDW54UZDDDR5IBDLANCNFSM4F4JRNRA
.

--

Chris Carroll

Yes! I am doing that and also trying to match the solution of the model in the original paper.
The zero denominator issue was that the interpolator was being passed (M,M) instead of (M,N). This resulted in the intended 2-d mesh to just be a straight 45° line. No triangulation can be done across a line and this manifested itself in 0 denominators. That issue is fixed now.

This PR is superseded by #782 . @Mv77 is going to bring this home.


prevent NPE from suppressing actual exception

If an exception happens before publishExecService is created then in finally block that exception can be suppressed with NPE from  publishExecService.shutdownNow() statement.

:+1:

LGTM


CTD when loading presets

Hello, im playing on a heavily modded list and im not quite sure what is causing this. My game will crash whenever i merge/apply a preset. Im aware its most likely a "me" problem but i would like some experts opinion what could cause this, since its related to IED. Here is my crashlog, i had to upload it cause its too many characters.
Edit: I should clarify what exactly happens, so for example i installed Missile's preset and they are split up into multiple ones for different things. I merge one and it works fine, then if i will merge the next one it would crash. One time it crashed after merging all presets, but then i unequipped my chest armor and the ctd happened.
Crash_2022_7_21_20-58-44.txt

Seems like a bad mesh, most likely missile\clutter\TorchHolder.nif that seems to be sourced from FEXXX806 (Missile IED Meshes.esp).
Apparently a broken collision mesh, it crashes while the game is cloning it.


Created spaghetti.cpp

challenged myself to create the single most dumb way to get the absolute value of a number in c++ while i was bored in class. so here it is.

Thank you for this pull request! Would you mind adding a short comment in the code that explains the purpose of the function?

Absolutely! Will get that done ASAP


Zig encounters some problems when compiling

So Zig is now on the beta nodes, and it seems to be having a hard time when running from the site (@mattgodbolt has already confirmed it runs fine if ran directly on the nodes)
A simple repro link: https://godbolt.org/beta/z/U0YoIU
The compiler emits:
unable to open example.h: Read-only file system
/compiler-explorer/c-preload/compiler-wrapper: line 21:  3158 Aborted                 (core dumped) "$@"
Compiler returned: 134

CC @tiehuis & @andrewrk - What example.h is it trying to load?

https://godbolt.org/beta/z/HEfbrT that gives an error of Unexpected extra parameter. @andrewk you can play around a bit on the beta site (godbolt.org/beta) and see if you can help. The sandbox environment tries to prevent output to locations the compiler "shouldn't" be writing to. Looks like the header file is dumped unconditionally to the current directory?

When I mouse-over the information icon it shows this:
build-obj --cache-dir /tmp/compiler-explorer-compiler118823-54-gg2917.fjvz7 --output /tmp/compiler-explorer-compiler118823-54-gg2917.fjvz7/output.s --emit asm -mllvm --x86-asm-syntax=intel /dev/null /tmp/compiler-explorer-compiler118823-54-gg2917.fjvz7/example.zig
It's missing the --output-h parameter, which I think means that it is included in the "filter" set. It should be filtered as well as hard coded to be /dev/null in the configuration.

By the way I think it would be a better user experience if filtered options generated a user-visible error rather than being silently stripped. As one argument for this, the status quo behavior confused @mattgodbolt.


Unable to delete content inside text composer in IOU description thread

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Open a chat with money request
Click on the IOU card to open the description thread
Click on the text composer and type something (type something even if the text composer is hidden behind the description and is not visible)
Close the keyboard to observe the content inside the text composer
Observe the position of the cursor
Click on the text composer again and hit the backspace on your keyboard multiple times in order to clear the content inside the text composer
Close the keyboard and observe the content inside the text composer

Expected Result:
The position of the cursor should not jump to the beginning of the content inside the text composer after user clicks on the text composer. User should be able to delete the content inside the text composer. (I think the reason why user can't delete content is because the cursor jumps to the beginning of the word inside the composer and nothing happens when user hits the backspace since there is no word before the cursor.
Actual Result:
The cursor moves to the beginning of the content inside the text composer and hence user can't delete the content inside.
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[x] Android / Chrome - Samsung note 10+
[ ] iOS / native
[ ] iOS / Safari
[ ] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: 1.3.17-2
Reproducible in staging?: Needs reproduction
Reproducible in production?: Needs reproduction
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/43996225/8628c8e6-d56a-4657-9676-5e5d93383909
Expensify/Expensify Issue URL:
Issue reported by: @nathan-mulugeta
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1684931958346929
View all open jobs on GitHub

I notice that caret is at starting of t4ext, can you please try putting it at the end and try again

Yes @BhuvaneshPatil , that is the issue, the cursor automatically moves to the beginning of the content even after putting it at the end, look at the recording closely.

I cannot reproduce this. I tried it exactly on the device checked here - Samsung Note 20, Chrome.


malloc error in ClTracerLensing when setting A_SPLINE_MAX < 1

When creating a ClTracerLensing object with A_SPLINE_MAX set to less than 1, Python gives a malloc error.
python(26540,0x7fffb026f3c0) malloc: *** mach_vm_map(size=18446744056529686528) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
ERROR: Could not allocate memory for linear-spaced array (N=-2147483647)

The exception is just a type error
TypeErrorTraceback (most recent call last)
<ipython-input-2-eabf94f2e53d> in <module>()
     18
     19 lens1 = ccl.ClTracerLensing(ccl_cosmology, has_intrinsic_alignment=False,
---> 20                             n=[z_nofz, nofz],)

/Users/yooken/miniconda/envs/python3/lib/python3.5/site-packages/pyccl/cls.py in __init__(self, cosmo, has_intrinsic_alignment, n, z, bias_ia, f_red)
    193                  has_intrinsic_alignment=has_intrinsic_alignment,
    194                  z=z, n=n, bias=None, mag_bias=None,
--> 195                  bias_ia=bias_ia, f_red=f_red)
    196
    197

/Users/yooken/miniconda/envs/python3/lib/python3.5/site-packages/pyccl/cls.py in __init__(self, cosmo, tracer_type, has_rsd, has_magnification, has_intrinsic_alignment, z, n, bias, mag_bias, bias_ia, f_red, z_source)
     98                             self.z_rf, self.rf,
     99                             self.z_source,
--> 100                             status )
    101
    102     def __del__(self):

TypeError: 'int' object is not iterable

Here is  the code to cause this error, with A_SPLINE_MAX=0.98:
import os
import numpy as np
import pyccl as ccl

os.environ["CCL_PARAM_FILE"] = "./ccl_params_modified.ini"

ccl_cosmology = ccl.Cosmology(Omega_c=0.3,
                              Omega_b=0.05,
                              Omega_k=0.0,
                              h=0.7,
                              n_s=0.96,
                              sigma8=0.8)

z_nofz = np.linspace(0.1, 4, 1000)
nofz = np.exp(-0.5*(z_nofz-1.0)**2/0.2**2)

lens1 = ccl.ClTracerLensing(ccl_cosmology, has_intrinsic_alignment=False,
                            n=[z_nofz, nofz],)

Tested on master with Python 3.5.3 and 3.6.1.
Upon digging a bit through the code, it seems that ccl_comoving_radial_distance returns NAN for a = 1./(1+zmax), which results in a non-sensical nchi (line 309, ccl_cls.c). Directly calling ccl.comoving_radial_distance with the same a is fine, however.

It turns out that setting A_SPLINE_MAX to less than 1 breaks a lot of things because in quite a few places functions get called with a=1. For example

ccl_h_over_h0 (isn't this always 1 for a=1?)
https://github.com/LSSTDESC/CCL/blob/f6f2d48e0a7653538a155cf02bf7982f53236eb6/src/ccl_cls.c#L164
ccl_linear_spacing https://github.com/LSSTDESC/CCL/blob/f6f2d48e0a7653538a155cf02bf7982f53236eb6/src/ccl_cls.c#L310
ccl_linear_matter_power https://github.com/LSSTDESC/CCL/blob/f6f2d48e0a7653538a155cf02bf7982f53236eb6/src/ccl_power.c#L1572

I originally intended to use A_SPLINE_MAX to change the range of integration in the Limber integral but considering how much would have to be changed, I think this can be easier achieved by hacking ccl_angular_cl directly.
Since so many places explicitly use a=1 (often for good reason), does it make sense to remove A_SPLINE_MAX as a user-changeable parameter?

@tilmantroester Did this ever get resolved?

No, unfortunately not. The options are to go through the whole code and find instances where a=1 is used in some way and replace that with A_SPLINE_MAX (which might break other things) or remove A_SPLINE_MAX as a user-settable option.

Okay, thanks for the update. I was just going through older issues to check; looks like we should keep this one open then.

I think A_SPLINE_MAX is no longer a user-facing parameter - if so is it fair to close this? @tilmantroester

It still is: https://ccl.readthedocs.io/en/latest/source/notation_and_other_cosmological_conventions.html#controlling-splines-and-numerical-accuracy
There seems to be only few places where A_SPLINE_MAX is still used. I'll try to see if replacing all of them with a=1 works, in which case we can remove the option altogether.

Thank you! Let me know how it goes.

Addressed with #751.


ToTestWellFormattedTests.cs:38: 60m/DEV Implement rule:...

The puzzle 76-8f445bc5 from #76 has to be resolved:
https://github.com/DenisZhukovski/ObjectToTest/blob/8b1d2165defd551b53eac272eea8f33eda738235/tests/ObjectToTest.UnitTests/ToTestWellFormattedTests.cs#L38-L38
The puzzle was created by Denis Zhukovski on 22-Dec-22.
role: DEV.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

@0pdd the puzzle #168 is still not solved.

@0pdd the only puzzle #168 is solved here.

The puzzle 76-8f445bc5 has disappeared from the source code, that's why I closed this issue.


Coordinated computations in HPC-MEC system.

Related Reference

O'Keefe J, Dostrovsky J. The hippocampus as a spatial map: Preliminary evidence from unit activity in the freely-moving rat.
Hafting T, Fyhn M, Molden S, et al. Microstructure of a spatial map in the entorhinal cortex.
O'keefe J, Burgess N. Dual phase and rate coding in hippocampal place cells: theoretical significance and relationship to entorhinal grid cells.
Komorowski R W, Manns J R, Eichenbaum H. Robust conjunctive item–place coding by hippocampal neurons parallels learning what happens where.
Fyhn M, Hafting T, Treves A, et al. Hippocampal remapping and grid realignment in entorhinal cortex.
Solstad T, Boccara C N, Kropff E, et al. Representation of geometric borders in the entorhinal cortex.
Høydal Ø A, Skytøen E R, Andersson S O, et al. Object-vector coding in the medial entorhinal cortex.
Boccara C N, Nardin M, Stella F, et al. The entorhinal cognitive map is attracted to goals.
McNaughton B L, Battaglia F P, Jensen O, et al. Path integration and the neural basis of the'cognitive map'.
Whittington J C R, Muller T H, Mark S, et al. The Tolman-Eichenbaum machine: unifying space and relational memory through generalization in the hippocampal formation.
Ghosh D, Rahme J, Kumar A, et al. Why generalization in rl is difficult: Epistemic pomdps and implicit partial observability.
George D, Rikhye R V, Gothoskar N, et al. Clone-structured graph representations enable flexible learning and vicarious evaluation of cognitive maps.
Nakashiba T, Buhl D L, McHugh T J, et al. Hippocampal CA3 output is crucial for ripple-associated reactivation and consolidation of memory.
Yamamoto J, Tonegawa S. Direct medial entorhinal cortex input to hippocampal CA1 is crucial for extended quiet awake replay.
O’Neill J, Boccara C N, Stella F, et al. Superficial layers of the medial entorhinal cortex replay independently of the hippocampus.
Ólafsdóttir H F, Carpenter F, Barry C. Coordinated grid and place cell replay during rest.
Evans T, Burgess N. Coordinated hippocampal-entorhinal replay as structural inference.

Overview
The hippocampal-entorhinal system is important for spatial and relational memory tasks, which requires to learn and interpret the structure of the environment and finally enables flexible behavior. The concept of a cognitive map has emerged as one of the leading metaphors for these capacities. Here I will introduce the Tolman-Eichenbaum Machine, which provides a unifying framework for unraveling the learning and neural representation of such a map. Specifically, it provides a mechanistic understanding of the hippocampal role in generalization and entorhinal role in abstraction. Furthermore, many experimental findings propose that abstractions and structural learning may rely on hippocampal replay. Therefore, I will also discuss a recent modeling work about coordinated hippocampal-entorhinal replay.

The properties of place cell & grid cell
The properties of place cell in HPC

The hippocampus maps arbitrary spaces allowing flexible navigation.
Hippocampal maps are context-selective and enable contextual behavior.
Hippocampal maps are annotated with sensory information allowing inference.

Hippocampus contains conjunctive representations.
Such conjunctive representations emerge with learning of a task, rather than existing innately,
The firing rate of these conjunctive cells can predict the accuracy of behavioral responses (correlates with performance).

Insight: Hippocampal mapping of spaces might serve as a framework upon which relational conjunctions can be mapped to allow inference.

The properties of grid cell in MEC.
Insight: MEC mapping of spaces might serve as an abstract structure for spatial & non-spatial inference.

Representations in MEC are context invariant.

MEC responses represent transition statistics.

Context invariant representations (grid cells) support path integration.

A general framework: The Tolman-Eichenbaum Machine
The Tolman-Eichenbaum Machine

Task: Spatial & non-spatial inference.
Previous model (SR) fail:

Rapid inferences and generalizations.
Explain the myriad types of spatial representations.
Predict remapping.

Idea:

Re-casting both spatial and relational memory problems as examples of structural abstraction and generalization.
Spatial reasoning can be cast as structural generalization.

Implementation details of TEM

Since it is difficult for us to sample enough points (one point for one distribution!) to approximate the distribution, we remove distribution distances, e.g.
$$
ln\frac{p_{\theta}(\mathbf{p}_{t}|\mathbf{M}_{t-1},\mathbf{g}_{t})}{q_{\phi}(\mathbf{p}_{t}|\mathbf{x}_{\leq t},\mathbf{g}_{t})},
$$
from the free-energy type loss $J_{t}$. And we instead directly use the mean of these distribution to measure the loss, e.g. $L_{total}$.

Relation between TEM and experimental results

TEM learns and generalizes abstract relational knowledge.

TEM learned representations reflect transition statistics

Simulation: Non-diffusive transitions using a policy of spending time near boundaries or approaching objects.
Explanation:

Policy induces $p(s'|s)$.
Because the transition statistics change, so do the optimal representations for predicting future location.
In order to make next-state predictions, TEM learns predictive representations, with object vector cells predicting the next transition is towards the object.

TEM represents non-spatial reinforcement learning tasks

Discussion on TEM

Environments as graph structures, agent wanders and predicts sensory experience.
This is not a reinforcement learning problem as the agent does not choose the actions.
No location information given, only pure sensory information given.
Two types of weight:

The network weights must learn to generalize relational structure across environments through BP.
Hebbian weights are adjusted as part of the network computation on each timestep.

Explain remapping better than Successor Representation.
Shift or rebuild?

TEM as a passive learning model.

P as a Hopfield Network, no dynamics, depends on $x$ and $g$ for retrieval (infer just by diffusion, no levy, long-range reasoning).
P and G as an offline learning, no update policy by interacting with environment, thus representation depends on sampling policy over the environment.
TEM has no replay as a proactive learning (Exploration & Exploitation, Generalization & Reward).
$g$ learns $p(s'|s)$ rather than $p(s'|s,a)$, it's not purely about the environment transition, needs to be corrected by replay.

Build a cognitive map from sequence: CSCG
Build latent state representations from sequences

CSCG cannot explain place cell.

CSCG learns to separate or merge aliased observations appropriately

Circuit computations: spectral modulation, coordinated replay

Nakashiba et. al. 2009 & Yamamoto et. al. 2017

CA3 may be the source of SWRs in hippocampus.

CA3 blockade to CA1 suppresses ripples and replays in both quite awake and sleep.

MEC-Ⅲ may have different affects on CA1 in quite awake and sleep.

Ripple bursts co-occur in CA1 and MEC in quiet awake with alternating ripples.
MEC-Ⅲ blockade to CA1 reduces ripple bursts and extended replays in quite awake.
MEC-Ⅲ blockade to CA1 does not affect ripple bursts or extended replays in sleep.

Csicsvari et. al. 2017

Superficial layers of the medial entorhinal cortex replay independently of the hippocampus.
Hippocampus is not the sole initiator of spatial and episodic memory trace reactivation.
Computations in memory systems may be organized in a less hierarchical, more parallel way (multi-head attention?).

Barry et. al. 2016

Result:

MEC layer Ⅴ/Ⅵ and CA1.
Grid cells to be spatially coherent with place cells during replay (11ms delay).
Directionally modulated grid cells and forward replay exhibiting the greatest coherence with the CA1.

Thought(?):

Replay buffer.
Forward replay: consolidation and planning.
Reverse replay: reward planning.

Coordinated replay as structural inference


Inconsistent/Not-obvious Drop Area

So we have 2 columns that are draggable.  The left column is where we get New things from.  The right is where we prioritize them.  When the Right column has nothing in it and we try to drag the first thing into it, it seems like we need to have the cursor over the exact few pixels of an area vertically (seems almost as wide as the drop zone for pixel width.)  So if we drop it there, the next drop is not bad.  It is just that initial drop on an empty container that seems buggy.

It may be somewhat similar to an issue I see on the Edge browser (fine on Chrome and thus new Beta Edge browser) - but if I go to your https://kutlugsahin.github.io/vue-smooth-dnd/#/cards on Edge and Just click to start dragging and drag 1 pixel, the item I am dragging is way over to the left.

I have the same behaviour with a likewise setup in Google Chrome on macOS.

same here

did you try to make the drop area wider with CSS?


I have bug

I don't know what it keeps reminding me of “init() got an unexpected keyword argument 'n_classes' ”.

@Ban1-cmyk can you provide some more info, for example, which script in the repo causes this problem? Thanks!

@Ban1-cmyk can you provide some more info, for example, which script in the repo causes this problem? Thanks!

Thank youuuuuuuu!!!!!!!!!