Add Atlassian to Homepage examples

Atlassian's AtlasKit is the best implementation of Storybook I've seen yet. It definitely deserves to be added to the homepage, maybe under "Used by these fine folks"
https://atlaskit.atlassian.com/components

I don't think it's storybook under the hood. Looks like a custom framework they built with some design cues from Storybook and other similar projects.

Hmm... any idea why they have the Storybook link and versioning dropdown at the top right? Maybe they are exporting to Storybook?
Thanks for the clarification @danielduan.

Oh I completely missed that! Yeah that linked page from the versions is definitely Storybook, but not the AtlasKit part with the blue styling.


Lexer tokenization improvement

The current lexer codepoint window is managed in a very inefficient way (copying for every advance).
Also token value stack slots are cleared and reinitialized for every token which is not necessary: the slots can hold previous values with the only impact that the values will be reachable until another token overwrites the values or tokenization ends.

Draft branch:

https://github.com/svaarala/duktape/compare/perf-lexer-window

The branch:

Uses a sliding lexer codepoint window for better performance
Replaces the large lexer if-else ladder with (mostly) a switch

The mandelbrot compile test (perf-testcases/test-compile-mandel.js) is 10% faster with the changes: on x64 laptop drops from ~20 seconds to ~18 seconds.
Code footprint change (from master) for x64, gcc -Os:

With sliding window: +336 bytes
Without sliding window (but with the if-else change): +240 bytes

The differences are quite trivial; interestingly the switch-case structure compiles to more code even in a size-optimized build.
The memory usage difference with and without sliding window is around 0.6kB which is small but might matter for low memory devices. Not sure if it's large enough to warrant keeping two window algorithms in the lexer.

Yeah, I was going to say, you should use a circular buffer for the CP window but I see you already did that ("sliding codepoint window") :)

Technically a circular window would be a bit different, access to the window would use an offset and modulo arithmetic (masking in practice). It would never need to copy codepoints.
The sliding window has no offset masking for lookups but needs to "scroll" the window once in a while.
Not sure which would be better; I opted for the sliding one because the codepoint lookup code will be smaller (and there quite many forward lookups in the tokenizer).

Merged to master.

Geez, you're as productive as me!  I built minisphere, a fully functional 2D game engine, from the ground up to its current state in 5 months.  Looks like I have some competition for rapid development here. :)


perlPackages.Mojolicious: 8.55 -> 8.58

Motivation for this change
https://metacpan.org/changes/release/SRI/Mojolicious-8.58
Things done

[X] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
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)
[X] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] 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)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

@GrahamcOfBorg build perlPackages.Mojolicious perldevelPackages.Mojolicious


How to serializer result like django rest framework

I have two models:
UserModel:
   name: str
   age: int

ItemsModel:
    desc: str
    user_id: ForeignKey

db data:
user = {"id": 1, "name": "user1",  "age": 18}
items = {"id": 1, "desc": "some desc", "user_id": 1}

I want the result: (like django rest framework nested serializer)
items: {
  "id": 1,
  "desc": "some desc",
  "user": {  # serializer this, do not return user.id
    "id": 1,
    "name": "user1",
    "age": 18
    }
}

FastAPI doesn't have a built in way to accomplish this -- you'll have to manually create the appropriate "merged" output model.
Something like:
class ItemsMerged(BaseModel):
    desc: str
    user: UserModel

    class Config:
        orm_mode = True

That said, by using a SQLAlchemy Relationship it should be possible to return an orm instance in your endpoint function and have the user data automatically populate the user field of ItemsMerged.
As far as I'm aware, there isn't currently a good way to do this asynchronously, or without making use of the SQLAlchemy ORM. If performance is enough of a concern that that's a problem though, I suspect you'd be better off manually writing the relevant query logic anyway.

thank you, It works very well.

Thanks for the help here @dmontagu ! :clap: :bow:
Thanks @zhimingzhang123  for reporting back and closing the issue :+1:


[OAP Server] Register lock implementation.

Use elasticsearch's document version to implement a lock for register source id.

Coverage decreased (-0.07%) to 22.913% when pulling cead3c46a91f7de8d64cd33dadbacf32b4d9b04a on peng-yongsheng:feature/oap/lock into e8456c0f83d0fb08bfb7173cc3dc8d69d799fc9f on apache:6.0.


maps are not showing on Nuvla installed from scratch

You need to create an account on mapbox. Create an access-token and configure it into ui-config file variable mapbox-access-token.

Opened documentation related issue https://github.com/nuvla/deployment/issues/74.
Closing.


Neba Model statistics console: Internal Cache hits are no longer reported

In 5.1.0, internal caching was significantly simplified (#338 ). However, it appears internal cache statistics collection was erroneously dropped in the process, resulting in the model statistics console always reporting "0" as the number of cache hits.
This issue does not affect caching, the internal model caching is working fine, but is a mere statistics collection issue,

Fixed!


Move globals like debug and verbose to their own module.

Instead of accessing langchain.debug, langchain.verbose, or langchain.llm_cache, please use the new getter/setter functions in langchain.globals:

langchain.globals.set_debug() and langchain.globals.get_debug()
langchain.globals.set_verbose() and langchain.globals.get_verbose()
langchain.globals.set_llm_cache() and langchain.globals.get_llm_cache()

Using the old globals directly will now raise a warning.

Still needs:

[ ] better deprecation warning message that points users to the new code to use
[ ] conversion of internal uses to make them use the new code path instead of using top-level langchain import

Any idea how to remove this warning, it appear after each message:
D:\Agents\langchain.venv\Lib\site-packages\langchain_init_.py:34: UserWarning: Importing llm_cache from langchain root module is no longer supported. Please use langchain.globals.set_llm_cache() / langchain.globals.get_llm_cache() instead.
warnings.warn(

Any idea how to remove this warning, it appear after each message:
D:\Agents\langchain\.venv\Lib\site-packages\langchain\__init__.py:34: UserWarning: Importing llm_cache from langchain root module is no longer supported. Please use langchain.globals.set_llm_cache() / langchain.globals.get_llm_cache() instead.
  warnings.warn(

I believe this might have been fixed in a subsequent PR, though I'm not exactly sure if it was already released or not yet. Please try upgrading langchain, and if the problem persists consider opening a new issue for it.


Japan Data Oddity

Is something wrong with the data for Japan?  The Aggregate confirmed drops sharply between Mar 13 and 14, which doesn't seem mathematically possible (unless they revised their numbers)

because on March 12, the number of people on the cruise was excluded.

Got it, thanks!


[Feature Request ] - Pylon without web server.

Is your feature request related to a problem? Please describe.
Would love access to opportunity to use pylon in a way that still allows me native control of the underlying http server.
const app = new Hono(<opportunity to configure here>)
// <various app logic
Bun.serve({
	port: Number(process.env.PORT || 3001),
	idleTimeout: 120,
	fetch: (request, ctx) => {
	        // some programmatic logic here.
	        // opportunity to use pylon here.
		return app.fetch(request, ctx);
	},
});

This has the following advantages:

Potential to use pylon in other web frameworks that aren't Hono.
Potential for people to integrate pylon into brownfield apps more easily.
Simplifies documentation / maintenance because all documentation relating to the "web server" component can be removed or kept for backwards compatibility in another section; Or 'in parallel compatibility'.
Potential to configure idleTimeout (https://bun.sh/docs/api/http#idletimeout) which prevents slow loris attack and solve other problems.
Potential to configure PORT as environment variable including the environment variables name which simplifies the pylon command.
Potential to use different commands for dev I.E

"dev": "pylon dev -c \"bun run .pylon/index.js\" --client --client-port 3003 --client-path gqty\\index.ts",
// becomes
"dev": "bun run --watch ./src/server.ts"

Simplifies docker entry point command.
Potential to use pylon (graphql) in environments outside of http I.E udp, LoRA, etc.

The summary of above is it would provide people to separate "pylon" from the underlying "runtime" and "web framework" allowing more flexibility to developers.
Issues and simplifications
export const graphql = { Query: { hello: () => 'Hello World'}, Mutation: {} }

This syntax would potentially need to expose a type of a function that matches the app.fetch signature from Hono. I see this though as an improvement because it would allow people to create different adapters for different web frameworks.
I.E
export const graphql = { Query: { hello: () => 'Hello World'}, Mutation: {} }
export default graphql // existing setup non-breaking change stays the same.

// web server control way being proposed
import { adapter } from "pylon/hono";
export const graphql = adapter({ Query: { hello: () => 'Hello World'}, Mutation: {} });

Which leaves room for express/elysia/node/etc adapters.
Adapters would setup a AsyncLocalStorage context, allowing developers to set getContext and potential to use that (request storage context) for other properties/state I.E tracing etc.
resloves
https://github.com/getcronit/pylon/issues/9
https://github.com/getcronit/pylon/issues/21  (because can leverage existing auth strategy's in underlying web framework)

Hi @ShanonJackson!
Thank you for your interesting request. I need to give this deeper thought to determine how a more "general" approach would be feasible, considering Pylon aims to be a framework that simplifies development rather than a universal library for all frameworks.
Here's what I can say for now:

Pylon's dev command is designed this way because it relies on a prebuild step for schema and client generation. That's why you need to execute .pylon/index.js. I'm not sure if it's technically possible to change that at this point.
You already have control over the "server." The proposed Bun.serve command works out of the box, so you can configure idleTimeout, PORT as an environment variable, etc.

Could you elaborate on how this would fix issue #9?

for #9
app.post("/2024-10-10/graphql", adapter({
    Query: {
          resource: () => "hello 2024-10-10"
     }
});
app.post("/graphql", adapter({
    Query: {
          resource: () => "hello 2024-10-10"
     }
});

and via spread to override a specific resource without rewriting the whole graphql constant.
const gql = graphql({Query: {resource: () => "hello non versioned"});
app.post("/2024-10-10/graphql", adapter({...gql, Query: {...gql.Query, resource: "hello 2024-10-10"}})); // with "resource" overridden but everything else same.
app.post("/graphql", adapter(gql));

This way you can create new versions of specific resources and/or entire new graphql schemas using whatever version system you desire. I.E standard api numerical based versioning or by date.

Pylon's dev command is designed this way because it relies on a prebuild step for schema and client generation

For this yes, the intention was to decouple this "prebuild step" from the dev command itself and run it as an entirely separate command.
I.E pylon generate --watch dev would be concurrently watch and serve. Not that I'm a fan of saying "here they do x" but in most code gen based tooling they have decoupled watch commands.

You already have control over the "server." The proposed Bun.serve

Can you show me the syntax for this?

Can you show me the syntax for this?

import {app} from '@getcronit/pylon'

export const graphql = {
  Query: {
    test: () => 'Hello, world!'
  }
}

export default app

const server = Bun.serve({
  fetch: app.fetch,
  port: 4000,
  idleTimeout: 120
})

console.log(`Server running at ${server.url}`)

for #9

#9 is not just about configuring date based routes, but rather automatic backwards compatible versioning handled by Pylon. Related to #8.
So for example when you release a API with a a test query and later remove the test query, it will still be available in old version endpoint, but no longer in latest.
This should then be the case with all breaking changes that you introduce in your pylon application.

Hi @ShanonJackson.
I just released a new feature that allows setting up the graphql routes manually.
This is mainly used for dependency mocking during test, but is also the first step to be more framework agnostic.
https://pylon.cronit.io/docs/guides/testing#optional-mocking-dependencies


rest: add initial support for PATCH

Signed-off-by: Francesco Ilario<EMAIL_ADDRESS>

/hold adding strategic-merge

/unhold strategic-merge added in d001c6a5cbc5176912793640ffd72cce84969969


Garten of banban 4

Porfin tenéis garten of banban 4
Changes

Checks
By submitting your pull request for review, you agree to the following:

[x] This contribution was created in whole or in part by me, and I have the right to submit it under the terms of this repository's open source licenses.
[x] I understand and agree that this contribution and a record of it are public, maintained indefinitely, and may be redistributed under the terms of this repository's open source licenses.
[x] To the best of my knowledge, all proposed changes are accurate.

SKIBIDI TOILET


Regenerate Speech for v1p1beta1

Regenerated v1 and v1p1beta1. The manual test needs to be updated, so I didn't try to run the smoke tests yet.
Also note that it looks like the credentials.rb change isn't included. I think we have another release coming this week if you want to include it in this update - your call. I thought we had already released that change but it looks like I was wrong.

@frankyn Are you okay waiting for the upcoming change to generated credentials.rb file before a release?

Let's wait so we don't have to update the migration guide when credentials are released. I'm not sure I'm in the right place to define release timing. However, I have one issue I'm working on resolving so waiting a bit would help.

Sent an email out on release requirements. Pending response.

Where are we with this PR? Is it ready?

@jbolinger Can you give us an update? When can you update these files again to get the credentials.rb changes included?

@blowmage I can manually update it if you want to get this out now. The version change hasn't been (correctly) released in the generator yet. Is it ready to go otherwise?

We would like to get this PR merged as soon as is reasonable. We were waiting on updated generated files to get the credentials.rb change.

Sorry I didn't realize this was the only open item - didn't mean to be the bottleneck.
@blowmage could you take a look? Is this the way you were thinking of aliasing the credentials.rb?
While doing this I noticed that our unit tests have some cross talk. I had to rename the MockSpeechCredentials in one of the versions to get things working. I wonder if there's a better way to run the tests? Could it be related to the errors that you mentioned that I couldn't reproduce? No reason to block this PR on it, but looks like we've got another issue to solve.


HNC: Prevent updating labels and annotations with hnc.x-k8s.io suffix on propagated objects

 Issue by yiqigao217
Thursday Apr 29, 2021 at 21:12 GMT
Originally opened as https://github.com/kubernetes-sigs/multi-tenancy/issues/1500

The webhook does prevent editing the propagated object itself or labels but doesn't prevent updating annotations:
# I'm annotating a propagated object:

$ kubectl annotate role -n b rl propagate.hnc.x-k8s.io/select=abc
role.rbac.authorization.k8s.io/rl annotated

$ kubectl get role -n b -oyaml
apiVersion: v1
items:
- apiVersion: rbac.authorization.k8s.io/v1
  kind: Role
  metadata:
    annotations:
      propagate.hnc.x-k8s.io/select: abc
    creationTimestamp: "2021-04-29T21:02:29Z"
    labels:
      app.kubernetes.io/managed-by: hnc.x-k8s.io
      hnc.x-k8s.io/inherited-from: a
    name: rl
    namespace: b
    resourceVersion: "5297867"
    selfLink: /apis/rbac.authorization.k8s.io/v1/namespaces/b/roles/rl
    uid: 2fc22fd7-7a34-492c-b823-79dd9383b2f8
  rules:
  - apiGroups:
    - apps
    resources:
    - deployments
    verbs:
    - update
kind: List
metadata:
  resourceVersion: ""
  selfLink: ""

@adrianludwin could you give some pointers to get started for this issue? where to look in code for propagated objects?

The validator for propagated objects is https://github.com/kubernetes-sigs/hierarchical-namespaces/blob/master/internal/objects/validator.go.
I just glanced at the code and it looks like we will stop users from modifying any annotation except the annotations that include hnc.x-k8s.io (see this line). The problem is that the canonical function returns the object with all HNC labels/annotations stripped out, which probably isn't the right thing to do for this function.
How about this as a solution: a few lines above, we check whether the hnc.x-k8s.io/inherited-from label has been modified. But really, we don't want any labels or annotations to be modified by users on propagated objects, and this function (handleInherited) is only called for propagated objects that are being modified by users. So maybe we should modify this code to check for all HNC labels and annotations (i.e., exactly the ones the canonical strips out). Or maybe modify canonical so that we can choose whether to strip out the HNC metadata, and only keep it when calling it here.
Whatever you do, can you please add unit tests that fail before you add the fix, and pass afterwards? And note this in the commit comment (e.g. like this). Thanks!

I updated the title to reflect what I believe the problem actually is.

/assign

@adrianludwin Thanks for the brief explanation .I got the problem.
I will start with writing the unit tests!!
I have one qs though:
why does canonical() strips out HNC label?
can't we compare the objects without stripping HNC label?

This was fixed correctly
/remove-lifecycle stale


Suggestion: It would be nice if we can use our own HAL without worrying about conflicts with upstream

In case of writing new HAL for some system which mruby/c doesn't cover yet, this pull request provide a clean way to develop without conflicts with upstream/master.
Please check for details: src/hal_user_reserved/README.md

Thank you.


Fix GHC 7.10 warnings.

So tempting to just say depends on GHC 7.10, but that would be mean. Or would it?
AfC

In the Cabal project we have a policy of supporting versions of GHC that are up to 3 years old. I think that this a good idea in general.

We still have production apps running GHC 7.6 with compelling reasons for not having upgraded yet.  Also Snap has a policy of supporting the past three Haskell Platform releases.  So I definitely think compatibility is important.  Although just fixing warnings is maybe not quite as big of a deal.

Spurious warnings are bad because they drown out real ones.

Or we could just add {-# OPTIONS -fwarn-unused-imports #-} (or whichever)
AfC

{-# OPTIONS_GHC -fno-warn-unused-imports #-}. That's not ideal because you won't be getting such warnings when you decide to change something later.

Spurious warnings are bad, but if they only show up on older compilers then they're effectively not an issue for developers working on newer compilers.
Also, -fno-warn-unused-imports is not ideal, but conditional compilation with CPP is also not ideal.  So it's a tradeoff.

Spurious warnings are bad, but if they only show up on older compilers then they're effectively not an issue for developers working on newer compilers.

In this case the warnings show up on GHC 7.10.

Also, -fno-warn-unused-imports is not ideal, but conditional compilation with CPP is also not ideal. So it's a tradeoff.

Yep.


Use PyUniProt to incorporate members of Enzyme classes

It's directly possible to iterate over all instances of each enzyme class through PyUniProt.

Generate final portion of EC tree
Generate EC - UniProt mapping (or even better, using PyUniProt it would be possible to generate an EC-HGNC mapping. Might as well do both if they're both easy)

what is the "final portion" of EC tree?

The final portion is the 4th level, which refers to actual proteins that have the activities in the first 3 levels from the EXPASY tree. You can go through UniProt to get these annotations and use text parsing to infer the parents.
http://pyuniprot.readthedocs.io/en/latest/query_functions.html#ec-number
import pyuniprot
query = pyuniprot.query()
for ec in query.ec_number():
   # get actual EC number, infer the parent, and the annotated children

i am gonna query only humans
as it takes forever and has a memory leak

which part? does it not provide a lazy iterator over the database?
because we fixed the memory leak with loading and now it only uses 117mb total :)

it's looking fine now. seems to be working.. have to wait


Fire Danger 0 Sensor regularly going  "unknown"

let me guess.... around 10PM? It does seem to do that. It's BOM, not the integration doing this

let me guess.... around 10PM? It does seem to do that. It's BOM, not the integration doing this

It is actually about 16:30 each day.  Would that still be BOM ? if so I will close the issue.

It is actually about 16:30 each day.  Would that still be BOM ? if so I will close the issue.

Yeah it's BOM but I think Brendon is writing a previous state now in the latest version so maybe fixed..

Yeah it's BOM but I think Brendon is writing a previous state now in the latest version so maybe fixed..

Yeah, BOM stop publishing the value, but I have tried to make it so my integration will retain the value when it disappears from BOM. So this is a bug. I am able to reproduce it too so will try and push out a patch soon.

Yeah, BOM stop publishing the value, but I have tried to make it so my integration will retain the value when it disappears from BOM. So this is a bug. I am able to reproduce it too so will try and push out a patch soon.

Doing it this morning as well (I think it's BOM)

Hey all, firstly, love the plugin.
This happens for min temperature all the time for me as well.

This is a BOM issue, not an issue with this integration. For my weather card this is why I use a Template Sensor as BOM zeros some forecast sensors for the current day regularly.

This is a BOM issue, not an issue with this integration. For my weather card this is why I use a Template Sensor as BOM zeros some forecast sensors for the current day regularly.

Oh yeah, I realise it's the BOM, but could the integration store the last valid value perhaps?

I know Brendan was thinking about doing that but it's not even logical if you consider it. The minimum for the day is ~4am and after that time (or in the afternoon BOM makes it unavailable) So given by then you HAVE the actual observed minimum why do you care what the forecast was? This is why I use a Template sensor giving me the actual minimum for today.

Actually, yeah, good point. I look at it in the evening to determine what the low point will be during the night for my animals, but at some point I figured it just swapped over to the next day.
I'll have to look into templated sensors like you suggest.

Actually, I just used a conditional card to swap between today and tomorrow when it returns unknown, thanks for the point in the right direction. :)

Yeah the Min_1 is actually the upcoming overnight temp and it will tick over to min_0 at midnight. Checking for unknown as you are is the way to go.

I'm also having the 'unknown' status for the last few days, but rather than just being at the end of the day, it's the whole day, like there is no info available or something.
I just had a look at the RFS ratings for today and it seems that the whole state is listed as None, but my status is Unknown.

That's because NSW is out of the fire danger period and the BOM won't produce Fire Danger Ratings until October. They run Oct - March by default, but can be brought forward or extended based on needs.
(Ex employee).

They only publish a status in Summer.

Well, that's annoying, makes sense, but annoying.
Is it possible to update the plugin to reflect this? Maybe have it just default to None then or something?
For now I've just modified my conditional card to show the older fire ratings integration status if there is an unknown status.

Or use a Template sensor if you don't like unknown. Actually not Summer but Fire Season. The FRS site also doesn't show a status out of season either. (Just saw @DeanoAus response too..)

Ah right. Well, something to think about.

Hey all, firstly, love the plugin.
This happens for min temperature all the time for me as well.

I get the same thing too, Based on previous comments its a BOM issue, what is the workaround?

The work around is to use either the average or statistics sensors with a template sensor for whatever card you are using to display the minimum


Fixed gazebo's 3D model shaking problem.

There was a problem #51 that 3D model of pedestrian was shaky up and down when showing pedestrian on gazebo with pedsim_gazebo_plugin.
When I added half of the model's height to the pose.z as an offset, the problem seemed to be temporarily solved.
However, this method depends on the model represented by the current cube, so if you change the 3D model to something else, you'll have to change it.

Thanks for the contribution


Add support to igluctl for temporary access key

When running a setup with cross account role access there is no option to use temporary access key.
To use the temporary access key we need to pass the access key id, secret access key and also the session token.
Tried to run igluctl using the following options:

Passing access key id, secret access key and session token using env vars
Creating a profile with access key id, secret access key and session token

None of the above options worked. There is no way to directly pass the session token to igluctl.
The aws documentation on temporary access key is at https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_use-resources.html#using-temp-creds-sdk-cli

@jrluis - please don't link to internal Snowplow documentation from public repos

Migrated to https://github.com/snowplow-incubator/igluctl/issues/18


Customize application to contain RC4 related information

As a user, I can view relevant information about RC4 residents

As discussed, include:

n/NAME
 p/PHONE_NUMBER
e/EMAIL
r/FLOOR-UNIT
g/GENDER
h/HOUSE
m/MATRIC_NUMBER
t/TAG


Some helix agents failing with Bad return status for module build on kernel: 6.5.0-1022-azure (x86_64) when installing some packages with apt-get

Some helix agents are failing when running sudo apt-get -o DPkg::Lock::Timeout=120 install -y libgbm1 libxkbcommon0 with:
Loading new lttng-modules-2.13.8 DKMS files...
Building for 6.5.0-1022-azure
Building initial module for 6.5.0-1022-azure
Error! Bad return status for module build on kernel: 6.5.0-1022-azure (x86_64)
Consult /var/lib/dkms/lttng-modules/2.13.8/build/make.log for more information.
dpkg: error processing package lttng-modules-dkms (--configure):
 installed lttng-modules-dkms package post-installation script subprocess returned error exit status 10

Only some helix agents seem to fail. For example - failure case from a failing build. And a working case from a working build.
This has been happening pretty randomly, but frequently enough to be blocking dotnet/aspire PRs. This helix run has all passing jobs.
I haven't been able to connect to a helix-repro-vm to reproduce the issue. Does it sound like an issue with some particular running VMs, or the image itself? The suggested alternative was https://github.com/dotnet/dnceng/issues/3122 - which would mean that we can drop this apt-get invocation.
cc @joperezr @eerhardt
(moved from https://github.com/dotnet/dnceng/issues/3140)

make.log on build:
make: Entering directory '/usr/src/linux-headers-6.5.0-1022-azure'
warning: the compiler differs from the one used to build the kernel
  The kernel was built by: x86_64-linux-gnu-gcc-11 (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
  You are using:           gcc-11 (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/Kbuild:27: File ./mm/slab.h not found. Probe "kmem" is disabled. Use full kernel source tree to enable it.
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/Kbuild:80: File ./arch/x86/kvm/lapic.h not found. Probe "kvm" x86-specific is disabled. Use full kernel source tree to enable it.
  CC [M]  /var/lib/dkms/lttng-modules/2.13.8/build/src/lib/ringbuffer/ring_buffer_backend.o
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/Kbuild:187: Files ./fs/btrfs/*.h not found. Probe "btrfs" is disabled. Use full kernel source tree to enable it.
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/Kbuild:206: Files ./mm/internal.h not found. Probe "compaction" is disabled. Use full kernel source tree to enable it.
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/Kbuild:215: Files ./fs/ext4/*.h not found. Probe "ext4" is disabled. Use full kernel source tree to enable it.
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/Kbuild:244: File ./drivers/base/regmap/trace.h not found. Probe "regmap" is disabled. Need Linux 4.1+ kernel source tree to enable it.
  CC [M]  /var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-sched.o
  CC [M]  /var/lib/dkms/lttng-modules/2.13.8/build/src/lib/ringbuffer/ring_buffer_frontend.o
  CC [M]  /var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-irq.o
  CC [M]  /var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-timer.o
  CC [M]  /var/lib/dkms/lttng-modules/2.13.8/build/src/lib/ringbuffer/ring_buffer_iterator.o
  CC [M]  /var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-module.o
  CC [M]  /var/lib/dkms/lttng-modules/2.13.8/build/src/lib/ringbuffer/ring_buffer_vfs.o
  CC [M]  /var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-power.o
  CC [M]  /var/lib/dkms/lttng-modules/2.13.8/build/src/lib/ringbuffer/ring_buffer_splice.o
  CC [M]  /var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-statedump.o
  CC [M]  /var/lib/dkms/lttng-modules/2.13.8/build/src/lib/ringbuffer/ring_buffer_mmap.o
/var/lib/dkms/lttng-modules/2.13.8/build/src/lib/ringbuffer/ring_buffer_mmap.c: In function ‘lib_ring_buffer_mmap_buf’:
/var/lib/dkms/lttng-modules/2.13.8/build/src/lib/ringbuffer/ring_buffer_mmap.c:116:23: error: assignment of read-only member ‘vm_flags’
  116 |         vma->vm_flags |= VM_DONTEXPAND;
      |                       ^~
make[4]: *** [scripts/Makefile.build:251: /var/lib/dkms/lttng-modules/2.13.8/build/src/lib/ringbuffer/ring_buffer_mmap.o] Error 1
make[3]: *** [scripts/Makefile.build:488: /var/lib/dkms/lttng-modules/2.13.8/build/src/lib] Error 2
make[3]: *** Waiting for unfinished jobs....
  CC [M]  /var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-9p.o
  CC [M]  /var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-i2c.o
  CC [M]  /var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-kvm.o
  CC [M]  /var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-x86-irq-vectors.o
  CC [M]  /var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-x86-exceptions.o
  CC [M]  /var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-signal.o
  CC [M]  /var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-block.o
  CC [M]  /var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-napi.o
  CC [M]  /var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-skb.o
In file included from /var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/define_trace.h:87,
                 from /var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/skb.h:92,
                 from /var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-skb.c:29:
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:133:6: error: conflicting types for ‘trace_consume_skb’; have ‘void(struct sk_buff *)’
  133 | void trace_##_name(_proto);
      |      ^~~~~~
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:45:9: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’
   45 |         LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), PARAMS(args))
      |         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/skb.h:64:1: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’
   64 | LTTNG_TRACEPOINT_EVENT_MAP(consume_skb,
      | ^~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from ./include/trace/events/skb.h:10,
                 from /var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-skb.c:18:
./include/linux/tracepoint.h:255:28: note: previous definition of ‘trace_consume_skb’ with type ‘void(struct sk_buff *, void *)’
  255 |         static inline void trace_##name(proto)                          \
      |                            ^~~~~~
./include/linux/tracepoint.h:432:9: note: in expansion of macro ‘__DECLARE_TRACE’
  432 |         __DECLARE_TRACE(name, PARAMS(proto), PARAMS(args),              \
      |         ^~~~~~~~~~~~~~~
./include/linux/tracepoint.h:566:9: note: in expansion of macro ‘DECLARE_TRACE’
  566 |         DECLARE_TRACE(name, PARAMS(proto), PARAMS(args))
      |         ^~~~~~~~~~~~~
./include/trace/events/skb.h:54:1: note: in expansion of macro ‘TRACE_EVENT’
   54 | TRACE_EVENT(consume_skb,
      | ^~~~~~~~~~~
make[4]: *** [scripts/Makefile.build:251: /var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-skb.o] Error 1
make[4]: *** Waiting for unfinished jobs....
  CC [M]  /var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-net.o
make[3]: *** [scripts/Makefile.build:488: /var/lib/dkms/lttng-modules/2.13.8/build/src/probes] Error 2
make[2]: *** [scripts/Makefile.build:488: /var/lib/dkms/lttng-modules/2.13.8/build/src] Error 2
make[1]: *** [/usr/src/linux-headers-6.5.0-1022-azure/Makefile:2039: /var/lib/dkms/lttng-modules/2.13.8/build] Error 2
make: *** [Makefile:234: __sub-make] Error 2
make: Leaving directory '/usr/src/linux-headers-6.5.0-1022-azure'

Relevant tests were disabled in https://github.com/dotnet/aspire/pull/4694 .

Closing this in favor of https://github.com/dotnet/aspire/issues/4921 because:

the tests no longer fail randomly because apt-get install was removed, and instead we rely on the helix agent having the dependencies already installed
https://github.com/dotnet/aspire/issues/4921 is the current issue now as the tests are disabled, and if enabled they would fail complaining about missing dependencies.


[improve] : Optimize refactoring code, and supplement documentation

[improve] : Optimize refactoring code, and supplement documentation

@zhangshenghang please，cr


Investigate process delegating to S3 events to start step functions

process currently uploads input payloads to S3 and also starts the step function execution using the sfn API. However, we have seen a race condition with this process, as we can't guarantee the step function starts after we claim processing, mainly due to service limits restricting the number of concurrent step function executions.
Instead of having process limited by step functions, we could use the S3 upload to generate an EventBridge event, which can use to start a step function execution. This eliminates the one lengthy step from process and more or less ensures it would not long have time out issues under heavy load.
A disadvantage is that process would not longer have the sfn backpressure, and would move the processing queue from the highly visible SQS queue to the opaque EventBridge. We'd also have to churn through that EventBridge queue before messages start to time out. Unfortunately, it looks like the max age of an EventBridge event is one day, whereas SQS can be configured to queue for up to 14 days (4 days being the default).
In short, this may not be the best idea, but may be worth considering.

Ha, just realized this probably doesn't work because we won't have a way to write out the execution ARN to the state database. 😞


use auto-generated region. scopes

In recent dev builds new auto-generated scopes have become available that provide a way to reliably get a color without having color schemes to support package-specific scopes. With SublimeLinter we're currently testing this new approach and it's and excellent way of getting red underlines etc. without color schemes having to add sublimelinter.mark.error etc. Here you can do away with throwing a bunch of scopes at it in hopes that color schemes will have a match for at least one of them.
I don't believe you can do a version check in sublime-syntax files, so for the time being you can keep the markup.error/deleted etc. scopes in there. Perhaps the sublimelinter scopes should be kept for now too, no sure how effective they are.
One thing to be aware of though is that for instance region.redish has both red fore- and background, although with reasonable contrast. So the diagnostics panel will look a bit different (but not badly so).

All in all I think adopting region.<color> scopes is a better approach than hoping color schemes will adopt specific scopes. Not sure how you feel about having version checks in the code and supporting experimental features, but I think it's a good way to get some exposure for the new approach and it indicated how we intend to move forwards with this.

I think the version check is okay. Looks like build 3148 supported this, so > 3147 should be enough?
The contrast is not great in the diagnostics panel, would be usable without that background color.

Contrast is definitely not good there. I know they were contemplating foreground only regions, this might be a good case. Let’s wait for that.

FYI, I'm working on a similar panel for SublimeLinter, learning some tricks too. I intend to update this PR later to make them match.

@tomv564 we ended up using the following in SublimeLinter:
Highlights:
warning:  region.yellowish markup.changed.sublime_linter markup.warning.sublime_linter
error:    region.redish    markup.deleted.sublime_linter markup.error.sublime_linter

Text:
warning:  markup.changed.sublime_linter markup.warning.sublime_linter
error:    markup.deleted.sublime_linter markup.error.sublime_linter

Perhaps some day we get region.colorish scopes for just the foreground, but until that happens it should work just fine without for most color schemes.
With SublimeLinter 4, we will no longer generate color schemes. If a color scheme is used that doesn't provide colors for the above scopes, we provide an option to change the scopes for highlights. For text (i.e. in the output panel), you're just out of luck. Current ST dev releases provide an easy way for users to extend color schemes, so that will eventually sort itself out. At some point there is only so much you can do for ancient and unmaintained color schemes, at least on the package end. I think that's a better approach than generating color schemes and messing with user space stuff like settings etc.
For LSP this means sublimelinter.<something> will stop doing anything very soon. You can leave it in because it doesn't hurt anyone, but consider it legacy and deprecated at this point.

Agree, nice work with moving on from the manipulated color schemes (which worked well for me for many years)!
Too bad the colorish option didn't work out, thanks for driving this proposal!


feat: Use dockerhub image for faster execution

https://hub.docker.com/r/speakeasysagar/sdk-generation-action/tags

Aah right we need to update the action metadata, thanks for the spot.


sending a test email not working

I am running pocketbase on debian and created a superuser. When sending a test email without a SMTP server it fails saying it is unable to find the send mail executable. I installed the send mail executable then I tried to send another test email, and I did not receive it in my inbox or junk folder.

Please don't open issues like this, especially when this was discussed at least several times in the past. The Q&A discussions are usually the better place for this type posts.
Anyway, as mentioned in the documentation it is recommend to use a SMTP server for sending emails because by default it fallbacks to the unix sendmail command which may not be available or enabled on all platforms. And even if it is enabled, the mail server of the receiver may reject the email and refuse to deliver it to the receiver. We have no control over this. For test purposes I recommend using mailtrap.io or smtpbucket.com.

I also forgot to mention that if you are running PocketBase on a VPS keep in mind that most hosting providers (_at least the one I've tested in the recent couple years - Linode, Hetzner, DigitalOcean) blocks common outgoing emails ports like 25, 465, etc. as a very rudimentary abuse protection and may require to contact their support to be explicitly enabled.


Website is not accessible.

https://cloudup.com/cMZMM32ZP2D

sorry about that will fix this weekend.
duplicate of duplicate https://github.com/node-xmpp/node-xmpp.github.io/issues/11

fixed, sorry for the delay

no problem, thank you!


How to pass additional jinja template context variables?

My inertia template inertia_base.html extends from regular jinja template base.html which needs some additional context variables, such as account. How can I pass these variables to render_inertia? It doesn't seem to support it.
My use case is incremental adoption of inertia/svelte into an existing flask app. I'd like to embed my svelte into an existing hierarchy of jinja templates. Currently It looks like I'd be forced to use an iframe for the svelte app.

Hello Alex.
May I ask which version of flask-inertia do you use ? Since version 0.5 you can use the view_data argument in render_inertia to add template related context https://flask-inertia.readthedocs.io/en/stable/#root-template-data. You should be able to use it to add variables in tour templates.

There is no other way to pass context to the template.
render_inertia does not accept kwargs arguments that would be used in render_template

Thanks for the quick response.
Is there any chance of adding a context argument or **kwargs to render_inertia to support this usecase? context would probably be less of a breaking change, but **kwargs would parallel the API of flask.render_template a bit better.
Personally I'm not a fan of the view_data API because it's kind of invasive to the way you have to write your base template.

Sorry, I fail to see why context instead of view_data would be less invasive in your template code.
Concerning mimicking the flask.render_template API, I'm not sure I would support this feature. The API has been designed in the purpose of separating explicitly the inertia and the flask contexts.

Ok I undestand what you meant.
Your solution would introduce two args for the render_inertia method with same purpose : passing args to your templates outside of inertia's context, which I find redundant. As said, the API has been designed to explicitly separate the inertia and the flask contexts. Adding a new argument to bypass this logic seems unintuitive.
Concerning the alternative solution, as you mentioned it would be a major breaking change concerning how the API was designed. The package version actually mirrored the inertiajs one in its minor revisions and is not a state of the development status at this point (I need to upgrade it to version 1 after revising Inertia changelog).
I will not support change in the render_inertia API to support a new way to pass arguments to templates


[zh] Resync PR wranglers filters

Resync PR wranglers page for filters that were improved.

/approve


fix negative border-width on inputgroup and buttongroup

Description
fixes bugs from my previous changes, the variable border-width.

https://deploy-preview-37344--twbs-bootstrap.netlify.app/docs/5.2/forms/input-group/

Motivation & Context

Type of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Refactoring (non-breaking change)
[ ] Breaking change (fix or feature that would change existing functionality)

Checklist

[ ] I have read the contributing guidelines
[ ] My code follows the code style of the project (using npm run lint)
[ ] My change introduces changes to the documentation
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[ ] All new and existing tests passed

Live previews

https://deploy-preview-37356--twbs-bootstrap.netlify.app/docs/5.2/forms/input-group/

Related issues

Thanks for the PR @jonnysp. Could you explain in the description the use case fixed with some examples?

fixes bugs from my previous changes, the variable border-width.
https://deploy-preview-37344--twbs-bootstrap.netlify.app/docs/5.2/forms/input-group/


Find out the Author

Assalomu alaykum. Who is the author of this project?

Wa alaikum assalam. I guess, mainly it is me for now.

Agreed. Closing the issue!


Disable all default Key Bindings feature please...

I'd like to request a setting to disable all default keybindings and to use only those keybindings provided explicitly by the user. Currently, I have to manually disable each and every default keybinding explicitly and check after every update whether further additions or modifications are needed. This is annoying at best and error-prone at worst.

Duplicate of https://github.com/microsoft/vscode/issues/134332


How could I make my own theme?

I want to have Ayu Mirage in this app, it looks something like this;

I would want to have an option to make my own themes and if there would not be one, atleast document how to add your own theme using the source and then building the app.

You can add your own theme in https://github.com/deadlyjack/code-editor/blob/master/src/styles/themes.scss


Remove append* and insert* from API

Reverts the API introduced to address #18352.
Instead of removing the API content altogether, it has been moved to internal interfaces.
Reviewing cheatsheet
Before merging the PR, comments starting with

❌ ❓must be fixed
🤔 💅 should be fixed
💭 may be fixed
🎉 celebrate happy things

@bot-gradle test RFR

I've triggered the following builds for you. Click here to see all build failures.

ReadyForRelease build

The merge queue build has failed. Click here to see all failures.


Refactor accidental module load in SuccessTypings

A lot of reflective capabilities of elixir-ls and elixir_sense depends on modules being loaded. However, currently module load happens as a side effect of dialyzer integration in https://github.com/elixir-lsp/elixir-ls/blob/3acc1fdb2ef2c1167935f7b6e74300e039200ec5/apps/language_server/lib/language_server/dialyzer/success_typings.ex#L22. This needs to be refactored and added as a build step instead.

Ah, nice find. Agreed :+1:


Can not install the requirements

When I ran pip3 install -r requirements.txt, a warning rised.
Collecting git+https://github.com/thu-ml/zhusuan.git@48c0f4e (from -r requirements.txt (line 17))
  Cloning https://github.com/thu-ml/zhusuan.git (to revision 48c0f4e) to /tmp/pip-req-build-fg_b1f04
  Running command git clone --filter=blob:none -q https://github.com/thu-ml/zhusuan.git /tmp/pip-req-build-fg_b1f04
  WARNING: Did not find branch or tag '48c0f4e', assuming revision or ref.

It's an intermediate version of zhusuan. You can manually install it via pip install, or directly install the tfsnippet 0.2.0a4 as in requirements (installing tfsnippet via pip will automatically install the correct version of zhusuan).


Uncaught TypeError: Cannot read property 'props' of undefined

[Enter steps to reproduce:]

...
...

Atom: 1.19.2 x64
Electron: 1.6.9
OS: Mac OS X 10.12.6
Thrown From: Atom Core
Stack Trace
Uncaught TypeError: Cannot read property 'props' of undefined
At /Applications/Atom.app/Contents/Resources/app/node_modules/etch/lib/patch.js:161

TypeError: Cannot read property 'props' of undefined
    at getKey (/Applications/Atom.app/Contents/Resources/app/node_modules/etch/lib/patch.js:161:27)
    at mapOldKeysToIndices (/Applications/Atom.app/Contents/Resources/app/node_modules/etch/lib/patch.js:166:23)
    at updateChildren (/Applications/Atom.app/Contents/Resources/app/node_modules/etch/lib/patch.js:102:15)
    at patch (/Applications/Atom.app/Contents/Resources/app/node_modules/etch/lib/patch.js:18:15)
    at updateChildren (/Applications/Atom.app/Contents/Resources/app/node_modules/etch/lib/patch.js:77:13)
    at patch (/Applications/Atom.app/Contents/Resources/app/node_modules/etch/lib/patch.js:18:15)
    at Object.updateSync (/Applications/Atom.app/Contents/Resources/app/node_modules/etch/lib/component-helpers.js:108:26)
    at LinesTileComponent.update (/Applications/Atom.app/Contents/Resources/app/src/text-editor-component.js:3504:18)
    at updateComponent (/Applications/Atom.app/Contents/Resources/app/node_modules/etch/lib/patch.js:52:19)
    at patch (/Applications/Atom.app/Contents/Resources/app/node_modules/etch/lib/patch.js:16:25)
    at updateChildren (/Applications/Atom.app/Contents/Resources/app/node_modules/etch/lib/patch.js:77:13)
    at patch (/Applications/Atom.app/Contents/Resources/app/node_modules/etch/lib/patch.js:18:15)
    at updateChildren (/Applications/Atom.app/Contents/Resources/app/node_modules/etch/lib/patch.js:77:13)
    at patch (/Applications/Atom.app/Contents/Resources/app/node_modules/etch/lib/patch.js:18:15)
    at updateChildren (/Applications/Atom.app/Contents/Resources/app/node_modules/etch/lib/patch.js:77:13)
    at patch (/Applications/Atom.app/Contents/Resources/app/node_modules/etch/lib/patch.js:18:15)
    at updateChildren (/Applications/Atom.app/Contents/Resources/app/node_modules/etch/lib/patch.js:77:13)
    at patch (/Applications/Atom.app/Contents/Resources/app/node_modules/etch/lib/patch.js:18:15)
    at updateChildren (/Applications/Atom.app/Contents/Resources/app/node_modules/etch/lib/patch.js:77:13)
    at patch (/Applications/Atom.app/Contents/Resources/app/node_modules/etch/lib/patch.js:18:15)
    at Object.updateSync (/Applications/Atom.app/Contents/Resources/app/node_modules/etch/lib/component-helpers.js:108:26)
    at TextEditorComponent.updateSyncBeforeMeasuringContent (/Applications/Atom.app/Contents/Resources/app/src/text-editor-component.js:379:16)
    at TextEditorComponent.updateSync (/Applications/Atom.app/Contents/Resources/app/src/text-editor-component.js:273:16)
    at etch.getScheduler.updateDocument (/Applications/Atom.app/Contents/Resources/app/src/text-editor-component.js:224:46)
    at ViewRegistry.module.exports.ViewRegistry.performDocumentUpdate (/Applications/Atom.app/Contents/Resources/app/src/view-registry.js:187:15)
    at /Applications/Atom.app/Contents/Resources/app/src/view-registry.js:3:65

Commands
     -2:25 core:backspace (input.hidden-input)
     -2:24.3.0 core:paste (input.hidden-input)
 11x -2:23.9.0 core:move-left (input.hidden-input)
  8x -2:22 core:select-left (input.hidden-input)
     -2:20.2.0 core:cut (input.hidden-input)
     -2:19.7.0 core:backspace (input.hidden-input)
     -2:18.3.0 core:paste (input.hidden-input)
     -2:16.9.0 intentions:highlight (input.hidden-input)
     -2:16.7.0 editor:delete-to-beginning-of-word (input.hidden-input)
     -2:16.4.0 core:backspace (input.hidden-input)
     -2:16 core:paste (input.hidden-input)
     -2:15 core:save (input.hidden-input)
     -0:54.1.0 snippets:next-tab-stop (input.hidden-input)
     -0:54.1.0 snippets:expand (input.hidden-input)
     -0:54.1.0 editor:indent (input.hidden-input)
     -0:52.9.0 core:undo (input.hidden-input)

Non-Core Packages
atom-easy-jsdoc 4.12.1
atom-typescript 11.0.7
auto-detect-indentation 1.3.0
banana-js 0.2.5
busy-signal 1.4.3
intentions 1.1.5
language-lua 0.9.11
linter 2.2.0

Thanks for the report!  Can you confirm a few things for us?

what were you doing at the time of the error?
is the error is reproducible?
if reproducible, do you see the error in safe mode (atom --safe)?

/cc @nathansobo

All similar exceptions reported in BugSnag were preceded by an exception Cannot read property 'domNode' of undefined' from within Etch code, which leads me to believe we are somewhere calling etch.updateSync` with an uninitialized component. I've added some exceptions upstream from that error that name the constructor of the component in question so we can hopefully get some more insight.

Thanks again for your issue!
We haven't received a response to our question in this comment https://github.com/atom/atom/issues/15391#issuecomment-323662550. With only the information that is currently in the issue, we don't have enough information to take action. I'm going to close this but don't hesitate to reach out if you have or find the answers we need, we'll be happy to reopen the issue.


Maintainers: remove myself as docs collaborator

I am still interested in contributing to the documentation, but I am
tired of the spam I'm getting from zephyrbot whenever any pull request
touches anything in doc/.

We should have two areas, one is for documentation infrastructure and some key files like top level indexes and common high level areas.
Second area probably for GSG and other high level guides, but subsystems and other content should be covered by existing areas in the MAINTAINER file. Documentation of a subsystem or a service should be maintained and reviewed by the maintainer of that subsystem and not by one single person!


fix:  the order of layerState when AnimatorStatePlayState.Finished

Please check if the PR fulfills these requirements

[x] The commit message follows our guidelines
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
What is the current behavior? (You can also link to an open issue here)
What is the new behavior (if this is a feature change)?
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
Other information:

Codecov Report

Merging #774 (acff361) into main (a2c728c) will decrease coverage by 0.00%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main     #774      +/-   ##
==========================================
- Coverage   43.69%   43.68%   -0.01%
==========================================
  Files         419      419
  Lines       22847    22848       +1
  Branches     3129     3129
==========================================
  Hits         9982     9982
- Misses      12865    12866       +1

Impacted Files
Coverage Δ

packages/core/src/animation/Animator.ts
4.01% <0.00%> (-0.01%)
:arrow_down:

Continue to review full report at Codecov.

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


Question: The number of walks in evaluation

Hi, the paper mentioned that the walk number in classification task is 32, for segmentation task it's 32 * #SegClsNum.
But as I read the code, I don't know if I am misunderstanding the code, I found that for shrec, cubes, the default value is 16, see code. For modelnet40, the number is 64, see code
For the segmentation task, the walk number is 32 * 32 see code.
I wonder to know the number of walks for the results in the paper. Any help regarding this is appreciated! Thanks in advance.
Best wishes.

Hi, I am sorry for the delay.
I think that there will be no significant difference in the results anyway.
Not sure if the mismatch is due to older code or the parameter in the paper are not accurate.


add tag to Instagram Component.

Hello Anthony,
I add a tag parameter to the component like you did in your  'react-google-login', like that the component is more flexible.
If you see any irregularity I am happy to make a change.
Love your work!

Thanks!


fix fix use-after-free in load stream stub

Proposed changes
Fix use-after-free in load stream stub handler on_closed().
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall


Resizing result panel makes the incorrect table view

Sometimes the table is not using all spaces on the panel.

stats take too much space, move approximate in-font of the data, tell user sampling


Add context support

RTM (websockets) support is not yet present, to be determined how to be best implemented.

Uhm, turns out this breaks the Go < 1.7 support. People should be at least on 1.7, right?

Well, I've made a new release to get around this problem.

This will be merged on May 31, 2017

@dlsniper May 31 has come and gone, would you mind merging? This is a great improvement to the package.

Hi @joefitzgerald, I must apologize for the delay, something came up and I also took the opportunity to have it tested a bit more via gopher before I release such a big change to the world.


Support endpoint overriding

There are two kinds of overrides:

overriding regular endpoint
overriding default handler (such as chttpd_db:handle_request/1)

Therefore there are two distinct options for overriding.
url_handler(<<"_all_dbs">>) ->
    {override, fun mymodule:handle_all_dbs_req/1};

url_handler(_) ->
    {default, fun mymodule:handle_request/1};

Wrong commit message
s/checkpoint/endpoint/g

s/checkpoint/endpoint/g --- fixed

+1


Please include a "HOME" button

Please include a "HOME" button
maybe put it somewhere near the github logo on the top left?
the reason to have a home button, it is nice to go to the main index page without needing to focus the cursor into the URL bar and deleting the necessary amount of characters.

by the way, great site, thanks for it, i will be giving the link to my friends.

nevermind, use the flags for navigating to the home index


ci: fix container build for parameter-setup

Describe your changes
Follow-up to #4930, in which we inadvertently broken container builds, due to a workspace dependency being introduced. We don't build container images on every PR push, so CI passed fine, only failing when trying to build/deploy post-merge. Tacked on a small change to address.
For testing, leave it to me: I'll re-deploy after this lands to get it going.
Issue ticket number and link
Refs #4933.
Checklist before requesting a review

[x] I have added guiding text to explain how a reviewer should test these changes.

[x] If this code contains consensus-breaking changes, I have added the "consensus-breaking" label. Otherwise, I declare my belief that there are not consensus-breaking changes, for the following reason:

build logic only, no changes to consensus

For testing, leave it to me: I'll re-deploy after this lands to get it going.

Built a container from this branch and confirmed build passing. Then I deployed a pindexer instance from that image tag and confirmed the problem described in #4933 was resolved. There's another error emitted now, but at least we've unblocked the image builds, so we're running the latest code again.


Outdated Documentation

Hi guys,
Could we get this documentation updated to reflect the latest changes on the portal and on the apple software.
The current steps are not easily followed on with the new apple interface.

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

ID: 07303594-9639-aa5f-1c57-e404a90cf96e
Version Independent ID: 97cba838-e304-bbd8-de7f-dc6d700cd9d0
Content: Token-based (HTTP/2) Authentication for APNS in Azure Notification Hubs
Content Source: articles/notification-hubs/notification-hubs-push-notification-http2-token-authentification.md
Service: notification-hubs
GitHub Login: @sethmanheim
Microsoft Alias: sethm

@ukez15 Can you please provide the document link you are referring for an update, so that appropriate team can be engaged.

It's a documentation on notification hub:
https://docs.microsoft.com/en-us/azure/notification-hubs/notification-hubs-push-notification-http2-token-authentification
I'm a support engineer with CSS and a customer is having difficulty following the documentation as the screenshots reflecting the apple part are outdated.

@ukez15 Thanks for pointing out this. I am assigning this to the doc author for updating the screenshots as applicable.

@ukez15 Thank you for reporting this -- we will get this updated as soon as possible, but realistically it may be a couple of weeks.

Piecing things together this code appears to be the right way to use the APNS key, key id and team id from Apple:
    public static string CreateAPNSToken(string teamid, string kid, string privateKey)
    {
        CngKey cngkey = CngKey.Import(
            Convert.FromBase64String(privateKey),
            CngKeyBlobFormat.Pkcs8PrivateBlob);

        ECDsaCng dsa = new ECDsaCng(cngkey);

        var jkey = new Microsoft.IdentityModel.Tokens.ECDsaSecurityKey(dsa);
        jkey.KeyId = kid;

        var credentials = new Microsoft.IdentityModel.Tokens.SigningCredentials
                         (jkey, SecurityAlgorithms.EcdsaSha256);

        var header = new JwtHeader(credentials);

        var payload = new JwtPayload(teamid, null, null, null, null, DateTime.Now);

        var secToken = new JwtSecurityToken(header, payload);
        var handler = new JwtSecurityTokenHandler();

        var tokenString = handler.WriteToken(secToken);

        return tokenString;
    }

However, the result is a '.' separated string which appears correct according to JWT docs, but is not accepted by Azure to configure the notification hub for APNS.

It turns out that the value to put in the Token field is in fact the private key contained in the .p8 file containing the APNS key that one downloads from developer.apple.com -- only the base64 key itself, not the header/footer.

We tried just copy/paste the value from the p8 file but azure throws back a validation error every time. According to the apple docs this needs to be in "Provider Authentication Token" format which just looks like a fancy JWT

Ignore the Apple documentation.  You probably need to remove the -----BEGIN* and -----END* header and footer and paste the private key as a single line of base64 text.

What could really help is to try the repo on the documentation and update with the latest screenshots from both the notification hub side and the apple developer side while putting all likely information (like the code and p8 Keys) in there.
this would help customer's easily walk through when trying to attempt this on their own

@craigwi Craig, can you please clarify what you mean by the "Token field"? I have the values and clarification from Brannon, but I'm not sure if this applies to your C# code above, a section of the article in question, or other, or maybe you mean secToken...?

There are four fields in the APNS configuration in the Azure Portal: "Key Id", "Bundle Id", "Team Id" and "Token".  I'm referring to the last one.  I'll send you an email with more details.

@ukez15 Thank you for taking the time to send your feedback! I have made a lot of updates to this article, so please have a look and open a new GitHub issue if you have any further feedback on this article.

#please-close


Fix : fastify example

Fix the fastify example :

Use the new root option
Remove the throw statement and properly start the Fastify server

Oops. thanks a lot!
btw, it's still not going to work with the new version. we are missing the import.meta.hot.boundary usage in the import expression. also, we don't need reload anymore too
but I'm currently in the process or reworking the different examples and also the documentation, so no worries, I will handle that
Thanks !

Please see the readme for the new version: https://github.com/Julien-R44/hot-hook#boundary and also this PR : https://github.com/Julien-R44/hot-hook/pull/1
sorry for this major change only 24 hours after the initial release 😅
the fastify example has also been updated and works correctly
let me know if you need any help or have any feedback regarding an integration of hot hook in fastify

Oops. thanks a lot!
btw, it's still not going to work with the new version. we are missing the import.meta.hot.boundary usage in the import expression. also, we don't need reload anymore too
but I'm currently in the process or reworking the different examples and also the documentation, so no worries, I will handle that
Thanks !

Haha no problem, I'm just testing the module! Great work! :wink:


Error 500 on unmatched route

Environment
node 16
nitropack: 0.4.12
Reproduction
Unmatched route throws a 500 error instead of 404.
When a directory such as routes/test has no file and a request to /test or /hello is done, an error is thrown and a 500 response is sent instead of a 404. However if a index.get.ts is available in /routes/test, the error is normally handled with a method not allowed error.
Describe the bug
{"url":"/api/technicals/general","statusCode":500,"statusMessage":"Internal Server Error","message":"Cannot read properties of undefined (reading 'post')","stack":["at createError (./node_modules/h3/dist/index.mjs:191:15)","at Server.nodeHandler (./node_modules/h3/dist/index.mjs:381:21)"]}
Additional context
No response
Logs
No response

Yes, this error happened when I deployed a nuxt app to vercel-edge.

Might be related to https://github.com/unjs/nitro/issues/717

Lets track via https://github.com/unjs/nitro/issues/717 unless you have another reproduction.


Fix gradient inversion

Problem
Gradient inversion used distances instead of weights. This could result in unexpected inversion.
Solution
The weights are calculated first and then inverted if the option is selected.
Type of change

Bug fix (non-breaking change which fixes an issue)

Change summary:

update weights instead of distances while inverting gradients
add credentials file to gitignore

Steps to Verify:

pack -r cellpack/tests/recipes/v2/test_mesh_image_gradient.json -c cellpack/tests/packing-configs/test_mesh_config.json

Screenshots:
Inverting distances:

Inverting weights:

Keyfiles:

Gradient.py

Codecov Report
All modified lines are covered by tests :white_check_mark:

Comparison is base (58c0256) 98.52% compared to head (4363247) 98.52%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #196   +/-   ##
=======================================
  Coverage   98.52%   98.52%
=======================================
  Files          16       16
  Lines         476      476
=======================================
  Hits          469      469
  Misses          7        7

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

Looks good to me! I was able to pack the test recipe, however, it's taking a very long time to load the model in Simularium, I'm still waiting to visualize the result.
One question(might not related to this PR):
In terminal logs, the message Packing test_mesh_image_gradient_1.0.0: appeared twice with the first one remaining at 0% progress. Should we make any modifications to address this if one of them is being skipped or something?

@rugeli,  were you able to visualize the output? It might help if you change the radius of the primitive_sphere to 1 so that there are fewer grid points to visualize.
As for the progress bar, it gets reprinted/interrupted when something else gets printed to the terminal. The Known pipe types message seems to have reset the bar -- we can look into what causes that message and whether we can prevent it from being displayed.

@rugeli, were you able to visualize the output? It might help if you change the radius of the primitive_sphere to 1 so that there are fewer grid points to visualize.
As for the progress bar, it gets reprinted/interrupted when something else gets printed to the terminal. The Known pipe types message seems to have reset the bar -- we can look into what causes that message and whether we can prevent it from being displayed.

Thanks for getting back to me! I wasn't able to visualize the output yesterday. I just changed the primitive_sphere to 1, but the simularium has been in loading for the past 20 minutes.

@rugeli the recipe has been updated so you should be able to run it faster and visualize in simularium. Let me know if there are still any issues


No event for text label of Sankey diagram node

Version
4.8.0
Reproduction link
https://gallery.echartsjs.com/editor.html?c=xoA4NXaEpO&v=2
Steps to reproduce
option = {
  series: {
    type: 'sankey',
    data: [{
      name: 'aaa'
    }, {
      name: 'bbb'
    }],
    label: {
      show: true,
      slient: false,
      triggerEvent: true,
      textStyle: {
        fontSize: 20
      }
    },
    silent: false,
    links: [{
      source: 'aaa',
      target: 'bbb',
      value: 5
    }]
  }
};

What is expected?
Move the mouse to the text label to have an effect, click to trigger the event
What is actually happening?
No effect.

In 5.x version, label will have better event handling.


💔 Called on_block_announce with a bad peer ID

ubuntu 18.04 LTS
cpu:8
40 GB
ssd 700 GB
I noticed frequent mistakes about the inconsistency of "peers", after restart service everything returned to normal. I am adding a log:
https://drive.google.com/file/d/1H8iJvi6JHetLHuvdfFQj7Ew_v5zA9MS-/view?usp=sharing

@CNazar could you check it on latest release please

agreed so far without errors a new release


Strip protocol in paths returned by 'ls'

The previous changes had as an effect to by pass the 'ls' method which is used in the base class AbstractFileSystem.
There seem to be a difference between what is returned by ls in the test docker in dask and what is returned using an actual HDFS server.
In my case, when doing:
hdfs=pyarrow.hdfs.connect(host="myserver", port=xxxx)
hdfs.ls("path/to/file", detail=True)

... the protocol information is prepended to the path while it is not the case in the test docker.
This explains while nothing was detected. My corrections consists in calling _strip_protocol on the output as expected by the info method on the AbstractFileSystem.
this PR is related to the dask issue: https://github.com/dask/dask/issues/5285
and reverts and correct modifictation in the PR: https://github.com/intake/filesystem_spec/pull/107

and reverts and correct modifictation in the PR: #107

Should that be the incorrect modification?

I mean it reverts and corrects (i.e. fixes) the modification in PR...

Thanks for the clarification. Based on the docs this seems to be the correct change:

full path to the entry (without protocol)

Can we add a test for this change, to ensure that we don't regress on this in the future?

Thank you for finding this.
Testing with the Dask image shows that there is nothing special about the image: if you use the default server, you get paths without the protocol, and if you specify the server, you get "hdfs://...".
This must always have been the case, I'm not quite following why the move to fsspec exposed it. Nevertheless, this should go in, but I agree with @TomAugspurger that a test would be good. That test would have to be in Dask, though, which is the only place that runs the HDFS implementation right now. Since we run hadoop-test-cluster anyway for the webhdfs test, it would be reasonable to reuse that infrastructure here - @jcrist , would that be hard?

libhdfs (the library underneath pyarrow's wrapper) has differences between versions/builds that sometimes result in prefixes in certain calls, and sometimes doesn't. This has to do with the version of hadoop/libhdfs, and not the version of pyarrow. This has bit us in other libraries (e.g. https://github.com/jcrist/hdfscm/issues/2). This may be why there's a difference between test environments.

Since we run hadoop-test-cluster anyway for the webhdfs test, it would be reasonable to reuse that infrastructure here - @jcrist , would that be hard?

You'd have to run the tests inside the docker container, since you'd need access to libhdfs, and port access to the hdfs namenode. We do this for other libraries using hadoop-test-cluster, no reason it wouldn't work here.


Add scripthash_to_address

Format address_to_scripthash output

> python3 cly.py --address-to-scripthash AKq8w9TCEwp2b9da8up8na9R57F1gEDUKf
Script Hash: 0x52e8def10107b89ac8c416a8148ba43f12837e2c -- Python format: b',~\x83\x12?\xa4\x8b\x14\xa8\x16\xc4\xc8\x9a\xb8\x07\x01\xf1\xde\xe8R'

Add scripthash_to_address

> python3 cly.py --scripthash-to-address 0x52e8def10107b89ac8c416a8148ba43f12837e2c
AKq8w9TCEwp2b9da8up8na9R57F1gEDUKf

Better scripthash_to_address implementation.
There's no need to reinvent the wheel, better use native methods from neocore

awesome, thanks :D

Could you add a test here please? https://github.com/CityOfZion/neo-python-core/blob/master/tests/test_cli.py


Version 0.3.3

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

15 of 15 (100.0%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 92.238%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1937

Relevant Lines:
2100

💛  - Coveralls


Catalog path confussion

I am trying to use NGetText using T.cs and suggested Catalog loading code
Here is what I use to load a mo file
public static readonly ICatalog _Catalog = new Catalog("MyTestWebsite",  "./locale");
I can't get the translated string from GetText function. So I am most probably pointing to some wrong location.
My problem is the same line just works the same way if I use a random string instead of MyTestWebsite. It should throw an exception if that file does not exist.  And I see no filename when I debug into that variable.
So I am not sure what file it is trying to load, is it /bin/locale/... ? is it /locale/.... ? or is it trying to load the file from another directory?

new Catalog("MyTestWebsite", "./locale") will try to load translation file from <CurrentApplicationWorkingDirectory>/locale/<CurrentUICulture>/LC_MESSAGES/Example.mo.
You can find out what is the working directory by calling the System.IO.Directory.GetCurrentDirectory() method. Or you can specify a different path to your locale folder instead of ./locale.

Follow on question, I'm sure there is an historical precedent for the LC_MESSAGES path and so forth, would you mind clarifying that please? Not trying to be an L10N expert myself, but a little more in depth insight would be helpful.
Also, are these MO thingies loaded as file? Or may they be embedded as resources?
Lastly, sort of tangent to the actual assets themselves, it is possible to contain different L10N contexts using the Catalog DomainName, correct? For instance, in WPF, if we wanted to localize a Window apart from a Control or perhaps an Enum with DisplayAttribute annotation, along these lines.

Follow on question, I'm sure there is an historical precedent for the LC_MESSAGES path and so forth, would you mind clarifying that please? Not trying to be an L10N expert myself, but a little more in depth insight would be helpful.

Yeah it's for historical reasons. This library follows the existing convention of the path to the translation files as any other GNU-based library. But you can easily load the translations from a different path.

Also, are these MO thingies loaded as file? Or may they be embedded as resources?

Lastly, sort of tangent to the actual assets themselves, it is possible to contain different L10N contexts using the Catalog DomainName, correct? For instance, in WPF, if we wanted to localize a Window apart from a Control or perhaps an Enum with DisplayAttribute annotation, along these lines.

Not really sure what you mean, but you can use multiple different catalogs loaded from different files at the same time. Or you can use the GetParticular* methods to distinguish translation strings with different contexts.

I enjoy the flexibility, sounds great, thank you!


Automatically embed Twitter

Hi!
I have tried many things to get Twitter embed automatically working. I made this regex to identify the twitter status string:
/^https?:\/\/twitter\.com\/(?:#!\/)?(\w+)\/status(?:es)?\/(\d+)(?:\/.*)?$/

The problem is that I am unable to generate the proper HTML to display the tweet. It seems that the Twitter embed HTML is a bit more complicated and has sub-nested elements.
Can someone guide me in the proper direction?

Hook onto the inlineUrl() method and then check if URL is from Twitter from the href property using your pattern:
protected function inlineUrl($Excerpt) {
    if (!$Inline = parent::inlineUrl($Excerpt)) {
        return;
    }
    $href = $Inline['element']['attributes']['href'];
    if (preg_match('/ ... /', $href, $matches)) {
        // Replace link markup into embed code
        $Inline['element'] = array( ... );
    }
    return $Inline;
}

@taufik-nurrohman Thanks, I came that far indeed. But the problem with the twitter embed is that it uses sub-elements and I am unsure how to render those..
Example Twitter HTML:

            Today is launch day 👀
— Documentator (@Documentator_io)

            April 2, 2020

Fetch the tweet data by its ID with CURL → https://developer.twitter.com/en/docs/tweets/post-and-engage/api-reference/get-statuses-show-id
And then build the block quote element from the JSON returned.

Performance wise not a fan of that solution doing a cURL each time. I could cache it, but it seems unnecessary to be honest.
Maybe anyone else has a solution? 🤝

Here's what I came up with on PHP:
$tweeter="jack";
$tweetID ="1247616214769086465";
$url = "https://publish.twitter.com/oembed?url=https://twitter.com/$tweeter/status/$tweetID";
$contents = file_get_contents($url);
$tweet = json_decode($contents, true);
echo $tweet['html'];

The $url will pull the json file from twitter. Then the json_decode() will turn the content to array and $tweet['html'] will display the blockquote part. The blockqoute surprisingly includes the js script https://platform.twitter.com/widgets.js, so pulling just the ['html'] from the array will do. Below code is the json content using PHP var_dump().
array(11) {
  ["url"]=>
  string(51) "https://twitter.com/jack/status/1247616214769086465"
  ["author_name"]=>
  string(4) "jack"
  ["author_url"]=>
  string(24) "https://twitter.com/jack"
  ["html"]=>
  string(686) "

I’m moving $1B of my Square equity (~28% of my wealth) to #startsmall LLC to fund global COVID-19 relief. After we disarm this pandemic, the focus will shift to girl’s health and education, and UBI. It will operate transparently, all flows tracked here: https://t.co/hVkUczDQmz
— jack (@jack) April 7, 2020

"
  ["width"]=>
  int(550)
  ["height"]=>
  NULL
  ["type"]=>
  string(4) "rich"
  ["cache_age"]=>
  string(10) "3153600000"
  ["provider_name"]=>
  string(7) "Twitter"
  ["provider_url"]=>
  string(19) "https://twitter.com"
  ["version"]=>
  string(3) "1.0"
}

With this may I suggest a twitter render using this markdown? If it's not too much to ask.
[tweet](jack:1247616214769086465)
I hope I explained it properly.
Thank you!


feat: add flags for dependencies and dev-dependencies that should be added to new features, subinfrastructure packages and ui package on create feature or subinfra/activate of platform

Might be not needed use Rapid Command Groups instead to achieve same result.
rapid <platform> add feature foo_page --dependencies cool: ^2.3.3, swag:, --dev-dependencies fresh 1.0.0
can be achieved by
rapid begin
rapid pub add cool: ^2.3.3, swag:, dev:fresh 1.0.0
rapid end


Fix: stage names for gathering messages.

Signed-off-by: dblock<EMAIL_ADDRESS>Description
Regression from https://github.com/opensearch-project/opensearch-build/pull/924/files
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #942 (6610d1c) into main (430a331) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #942   +/-   ##
=======================================
  Coverage   92.25%   92.25%
=======================================
  Files          88       88
  Lines        2323     2323
=======================================
  Hits         2143     2143
  Misses        180      180

Continue to review full report at Codecov.

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


Filter listings by availability

Issue

Closes #103

Description
Adds ability to filter based on UnitsSummary notion of availability.
UI changes adding the filter option:

Example of a filtered listings page:

Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Prototype/POC (not to merge)
[ ] This change is a refactor/address technical debt
[ ] This change requires a documentation update
[ ] This change requires a SQL Script

How Can This Be Tested/Reviewed?

[x] Desktop View
[x] Mobile View

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have reviewed the changes in a desktop view
[x] I have reviewed the changes in a mobile view
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules
[x] I have assigned reviewers
[x] I have updated the changelog to include a description of my changes
[x] I have run yarn generate:client if I made backend changes

The ui mocks currently have a drop down. I'd imagine that there were a few options we were thinking of instead of just has availability yes/no. @tomgebauer what were the drop down options for unit availability?

The original idea here was to have availability contain Yes, No, and Waitlist, and to have it as a dropdown to function as a catch-all for any future states there might be. However if we will only realistically have yes/no, then we can change this to a radio selector between two options * Yes and * No

Spoke with Tom offline, we'd like to have a dropdown with the follow options:

Has availability
no availability
Waitlist
Any Availability

I'll make changes accordingly.

Wouldn't "Any Availability" be the same as not selecting a value for that filter?

@willrlin yes, any availability would be the same as not selecting a value, and would be the default option


Customize "About Header image" ratio [Request]

Please allow customization of About Header image ratio (default 16:7 in fragment_about_item_header) as i think height is very low (screenshot attached) and i found no possible way of doing it (marked private) except to use library as a module itself which is not ideal.

Instead the value, you also able to override the layout. Copy fragment_about_item_header.xml layout to your project and change height and width ratio.

Oo teri..i didn't knew that we can override resource of any included library by including same resource in project and modifying it..i thought i have to include it as module dependancy and than modify the resource file..thanks a ton...but does that mean accidently i can override things like string, color, drawable, etc of libraries..anywayz thanku


fzf theme

Just created a fzf theme, would be happy to transfer it to the org!
https://github.com/caarlos0/dracula-fzf

Hey @caarlos0, that's awesome man.
All of our themes follow the same template: https://github.com/dracula/template
Can you please update the repo before we start the transfer?

Sure @zenorocha, done: https://github.com/caarlos0/dracula-fzf
Also tried to send the transfer request, but it seems I need some sort of permission on the dracula org...

Awesome! You should be able to transfer now @caarlos0

done!
https://github.com/dracula/fzf
Thanks @zenorocha 🖤

I had to rename main to master in order to follow the organization standard and for the website to be able to fetch it correctly, okay?
It's live now, thanks @caarlos0 for building this theme!
https://draculatheme.com/fzf 🎉

no problem at all, thanks @zenorocha ! 🚀


Clarification needed for Android loader AAR location and usage

For version 1.0.22, the Release notes contain the following text:

The Android loader can be found on Maven Central, by adding the following line to your Android app's build.gradle dependencies section:
implementation 'org.khronos.openxr:openxr_loader_for_android:1.0.22'

However, checking Maven Central as of Jan 29, 2022, there is no package corresponding to version 1.0.22, only for 1.0.20.
Also, there is no clear explanation on how, for a CMake project that uses OpenXR-SDK (instead of OpenXR-SDK-Source), one would go to include and use the proposed Android loader. Additional documentation is needed for existing projects to stop using the vendor-supplied loader and start using the new loader.

Hmm. GitHub was supposed to have pushed that automatically. Looks like maybe it was still on manual, oops. I kicked it off now.
Does your cmake project get built by gradle? If so, just use the artifact that way. It gets exposed to CMake (via prefab) just like on desktop: find_package(OpenXR), OpenXR::Loader, etc. Otherwise let me know a bit more about how you're building so I can help.
(The files used by the loader are in both -sdk and -sdk-source repos, and you can see the cmake and gradle scripts in there to see how it builds.)

OK, those jobs finished. I think it should show up on Maven Central soon - there's a little bit of a promotion delay.

Ah, I did have to manually poke it. I've updated my instructions. Let me know about your build system and I'll see how I can help.

OK, those jobs finished. I think it should show up on Maven Central soon - there's a little bit of a promotion delay.

1.0.22 shown up on maven: https://search.maven.org/artifact/org.khronos.openxr/openxr_loader_for_android/1.0.22/aar.

@rpavlik
When I use the build.gradle in the androidteapots project .mavenCentral(), implementation'org.khronos.openxr:openxr_loader_for_android:1.0.22'.
Cmake Build Can not find openx.cmake.
ErrorMessage:
Could not find a package configuration file provided by "OpenXR" with any
of the following names:
OpenXRConfig.cmake
openxr-config.cmake
The actual Cmake is here
. /classic-teapot/.cxx/cmake/debug/prefab/armeabi-v7a/prefab/lib/arm-linux-androideabi/cmake/OpenXR/OpenXR-config.cmake
I had to write a Find*.cmake to Fix it.

oh... I wonder if that's a bug in the teapot app (I never finished it), or if it's due to an old version of prefab. There were some issues regarding capitalization in older versions of the prefab tool used by the android gradle plugin.

@rpavlik What about adding aar dependency usage for Android to Loader spec?

I'm planning a presentation and blog post in the next few weeks


multi-cluster: istiod repeatedly fails to patch configmap

2022-06-01T06:17:40.048065Z	error	klog	error retrieving resource lock istio-system/istio-namespace-controller-election: configmaps "istio-namespace-controller-election" is forbidden: User "system:serviceaccount:istio-system:istio-reader-service-account" cannot get resource "configmaps" in API group "" in the namespace "istio-system"

We enabled "external istiod" flag by default, so we'll try to win leader locks and patch webhooks/etc:
#39189
But the permissions are still conditional:
https://github.com/istio/istio/blob/12f5ad29c4b83898077902f3e63826d2dd8d7d6f/manifests/charts/istiod-remote/templates/reader-clusterrole.yaml#L45-L55
We should either:

Always give permission, rely on leader elect to prevent the wrong istiod doing the patching
Conditionally try to participate in this patching based on some metadata in the remote-secret or a label on the istio-system namespace (some per-cluster metadata that indicates primary, remote, istiodless-remote, etc.)
Auto-detect the cluster-type somehow?
Fail closed on forbidden

@stevenctl I was on vacation last week but had started #39151 to address this issue. PTAL.


Udpate docker

Type of Change
feature or bug fix or documentation or others
API changed or not
Description
detail description
JIRA ticket: xxx
Expected Behavior & Potential Risk
the expected behavior that triggered by this PR
How has this PR been tested?
how to reproduce the test (including hardware information)
Dependency Change?
any library dependency introduced or removed

https://inteltf-jenk.sh.intel.com/job/ITREX-Chatbot-Inference-HPU/186/


Better Portals compatability: Only able to use a portal once in cubic worlds

https://github.com/Johni0702/BetterPortals/issues/369
This issue only occurs if the world is cubic.

Resolved with Better Portals 0.3.6


brave-spancollector-scribe:Frame size<PHONE_NUMBER>) larger than max length (16384000)!

Hi, I just run demo, like these.
 @Test
	public void contextLoads() {
		collector = new ScribeSpanCollector("localhost", 9411);
		collector.collect(new Span().setTrace_id(1).setName("ScribeServiceTest"));
	}

Then throw exception like these.
2017-01-24 11:16:52.782  WARN 13268 --- [pool-1-thread-1] c.g.k.brave.scribe.SpanProcessingThread  : Logging spans failed. 1 spans are lost!

org.apache.thrift.transport.TTransportException: Frame size<PHONE_NUMBER>) larger than max length (16384000)!
	at org.apache.thrift.transport.TFramedTransport.readFrame(TFramedTransport.java:137) ~[libthrift-0.9.0.jar:0.9.0]
	at org.apache.thrift.transport.TFramedTransport.read(TFramedTransport.java:101) ~[libthrift-0.9.0.jar:0.9.0]
	at org.apache.thrift.transport.TTransport.readAll(TTransport.java:84) ~[libthrift-0.9.0.jar:0.9.0]
	at org.apache.thrift.protocol.TBinaryProtocol.readAll(TBinaryProtocol.java:378) ~[libthrift-0.9.0.jar:0.9.0]

I'm not sure what I'm doing wrong.
Thanks for the help!

Scribe is port 9410 not 9411 (in the default zipkin server). If you are
interested in http, I'd recommend looking at the javadoc on
Brave.Builder.reporter() which shows how. Or maybe this example:
https://github.com/openzipkin/brave-webmvc-example

@adriancole that done! thank you! In my project will use http, and I also want to know scribe,thank you!


:(

There is a lack of more complete documentation to assist users.

You can just follow the official guide: https://docs.docker.com/compose/


Add further workflow run support - create, find, and all

While there exists a WorkflowRuns resource for Onfido Studio support, it only has the method evidence(). Some other actions, such as create, list, and retrieve are not yet added to this SDK. This PR adds those actions in.
I performed validation using the following code, although depending on your Onfido settings you may have different required applicant fields and other configuration differences. There are also new unit tests for the added methods.
import onfido
from onfido.regions import Region

ONFIDO_API_KEY = "" # TODO: populate with secret
ONFIDO_WORKFLOW_ID = "" # TODO: populate with value

if __name__ == "__main__":
    onfido_api = onfido.Api(ONFIDO_API_KEY, region=Region.CA)

    applicant_id = onfido_api.applicant.create({
        "first_name": "FIRST_NAME",
        "last_name": "LAST_NAME",
        "dob": "2000-01-01"
    })["id"]

    create_resp = onfido_api.workflowrun.create({
        "applicant_id": applicant_id,
        "workflow_id": ONFIDO_WORKFLOW_ID
    })
    print("Create:")
    print(create_resp)

    workflow_run_id = create_resp["id"]
    find_resp = onfido_api.workflowrun.find(workflow_run_id)
    print("\nFind:")
    print(find_resp)

    all_resp = onfido_api.workflowrun.all()
    print("\nAll:")
    print(all_resp)

@DavidMealha hi David, was wondering if you would be able to review my PR

hey @DavidMealha, I was using str.removesuffix() that was introduced in python3.9. I've made some updates and tested with python3.7 -- it should work now. Could I ask you to rerun the CI?

Hey @peggalex, this has been release as part of v2.10.0. Thank you again for your contribution!


Fix headers in contributing README

What was the end-user problem that led to this PR?
Some headers in contributing/README.md aren't displaying properly.

Also, I promised @indirect that I'd start contributing to bundler last night.
Was was your diagnosis of the problem?
The markdown was missing some spaces.
What is your fix for the problem, implemented in this PR?
I added some spaces. TADA!

Why did you choose this fix out of the possible options?
Adding spaces seemed like the most reasonable choice to transition from a state of non-spaces to a spaceful state.

<3, not only for the fix but for the wonderful PR description
@bundlerbot r+


classic-level  rebuild failed when electron-forge package

problem
I am using level as my local db server ,when pack my electron app ,I got this error and could not fix it .
I tried  using a different version of electron ,but still the same
 make: *** No rule to make target `Release/obj.target/leveldb/deps/leveldb/leveldb-1.20/db/builder.o', needed by `Release/leveldb.a'.  Stop.
  Error: `make` failed with exit code: 2
  at ChildProcess.onExit (/Users/neptune/github/xxx/app/node_modules/node-gyp/lib/build.js:203:23)
  at ChildProcess.emit (node:events:513:28)
  at ChildProcess._handle.onexit (node:internal/child_process:291:12)

An unhandled rejection has occurred inside Forge:
Error: node-gyp failed to rebuild '/private/var/folders/v6/51277h6j2258m8yvl9rknkhr0000gp/T/electron-packager/darwin-arm64/nnk-24h-live-darwin-arm64-MeCAK9/Electron.app/Contents/Resources/app/node_modules/classic-level'
at ChildProcess.<anonymous> (/Users/neptune/github/xxx/app/node_modules/@electron/rebuild/lib/module-type/node-gyp/node-gyp.js:118:24)
    at ChildProcess.emit (node:events:513:28)
    at ChildProcess._handle.onexit (node:internal/child_process:291:12)

env
node version v18.15.0
electron  abi   116
electron version  v25.8.1
classic-level  1.3.0
deps
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>

Rebuilding is not necessary, because classic-level includes prebuilt binaries that work for both node and electron. There should be a flag in electron-forge to skip rebuilding, check the docs.

Rebuilding is not necessary, because classic-level includes prebuilt binaries that work for both node and electron. There should be a flag in electron-forge to skip rebuilding, check the docs.

Thanks , after read the docs, I add a conf  at forge.config.js
  rebuildConfig: {
    onlyModules: [],
  },

It works.Though occurs another error unrelated to classic-level

After a few tries, I soved the problem;It has nothing wrong about classic-level,instead my forge.config.js;
Before
  packagerConfig: {
    ignore: [/logs/,/temp/,/cache/], // what i set before
  },

After
  packagerConfig: {
    ignore: [/logs/], // what i set after
  },

The regular expressions are matched against the absolute path of a given file/directory to be copied..

Awkward，i just ignored the corresponding file !!!
packagerConfig.ignore