Make replying more intuitive

I've noticed from on-boarding a few people into the lite client that it's not intuitive how to reply to a post in Patchbay. Most people seem to reply with a new message in the stream, which isn't the correct UX for threads.
I don't have any ideas about how to fix this, but I figure I'd open an issue about it.

hmm, how about a "reply" button that opens the thread in a lightbox? or takes you to the thread?

simple idea: why not
add a simple text of "reply" next to the hour.
this way people would click it. I would

Beyond the UX issue, I've discovered the actual issue here is threads do not work when you're running the lite client at a port and serving it up at a url. When you click a thread, it just opens patchbay in a new browser window.
Threads do work when you save the lite client to your desktop. This is also a faster experience because the browser isn't downloading 2mb of javascript every time you reload the page.
@benjajuarez are you using the lite client from ssb.evbogue.com or did you download the patchbay-latest html file from my site?

downloaded the patchbay-latest html file from your site

@dominictarr writing 1984 fanfic where winston enjoys his totalitarian society ironically!!! I'd love to read that!!!!

@benjajuarez Let's keep this thread focused on development, por fa.

my bad

@evbogue do you have ssb-links and ssb-query installed?

@dominictarr I didn't have them installed on my server. Installing ssb-links and ssb-query fixed the permalinks issue at http://ssb.evbogue.com/

@evbogue aha, I see it. when you click re: link it opens it in a new tab.
I put this in https://github.com/dominictarr/patchbay/blob/master/modules/tabs.js#L79-L80
and it stopped doing this (weird thing is that it only happens when use use http served html, but not when you open it as a file) the reply links must be being triggered via a different path...

Aha, no, the problem at
https://github.com/dominictarr/patchbay/blob/master/modules/tabs.js#L84
Which assumes that any http link is external. Instead, we need to check if it's on a different domain,
and treat links to the same domain as local links. I'll fix this.

fixed in 1.7.6!

oops, no i broke other stuff...

okay fixed in 1.7.7

confirmed fixed when deployed to ssb.evbogue.com

I believe 1.7.7 and #41 resolve this issue.


More button

ℹ Computer information

Spotify version: <IP_ADDRESS>5.g2a71e1b8
Windows version: Win10 21H2 19044.1706
PowerShell version: 5.1.19041.1682

📝 Description of the problem
i think the [more] button is gone in search result

I can confirm.

Are you talking about these buttons?

screenshot

Are you talking about these buttons?
screenshot

absolutely... PS: i have friend activity section

Maybe it's the features of the new search that I activated?
It seems to me that these category buttons for the new search, which are at the top, according to the idea of the developers, perform the function of the missing SEE ALL buttons in the old search.
I checked the work on the original client and these buttons (SEE ALL) are not there either.

There are 2 options, either everything remains as it is, or I can create a vote for returning to the old search, since I need to understand the number of people who do not like the new search.
Need a vote ?

Now you can specify various parameters for a more flexible installation, more details here


Deploy a pokemon in a gym when there is a free slot available

This is very basic functionality that deploys a pokemon in a free gym slot. By default this is disabled unless you add this, directly below "SpinFort" in the config file.
    {
        "type": "GymPokemon",
        "config": {
            "enabled": true,
            "feed_berries": true,
            "order_by": "cp",
            "min_interval":360,
            "min_recheck":30,
            "max_recheck":120
        }
    },

It will only use gyms that are in range and a max of 20 mons is hardcoded.

Will close this one, since I applied some bugfixing for special cases.


mut ref to opaque C++ class failed

As demonstrated by this repo, mut ref to opaque C++ class failed to build with log as
error: failed to run custom build command for `call-cc-mutable-class v0.1.0 (/github.com/sammyne/call-cc-mutable-class)`

Caused by:
  process didn't exit successfully: `/github.com/sammyne/call-cc-mutable-class/target/debug/build/call-cc-mutable-class-a20b9e389db3e0ce/build-script-build` (exit status: 1)
  --- stderr

  error[cxxbridge]: needs a cxx::ExternType impl in order to be used as a non-pinned mutable reference in signature of `say_hello_world`
    ┌─ src/main.rs:8:9
    │
  8 │         type Testbot;
    │         ^^^^^^^^^^^^ needs a cxx::ExternType impl in order to be used as a non-pinned mutable reference in signature of `say_hello_world`

  error[cxxbridge]: mutable reference to opaque C++ type requires a pin -- use `self: Pin<&mut Testbot>`
     ┌─ src/main.rs:12:28
     │
  12 │         fn say_hello_world(&mut self);
     │                            ^^^^^^^^^ mutable reference to opaque C++ type requires a pin -- use `self: Pin<&mut Testbot>`

warning: build failed, waiting for other jobs to finish...
error: build failed

where say_hello_world would increment Testbot.x, which require Testbot to be mutable. If I change it to self: Pin<&mut Testbot>, the UniquePtr<Testbot> cannot call say_hello_world.
Really appreciate if someone can help me to make mutable reference work for opaque C++ type.

The diagnostic is correct — you need to write self: Pin<&mut Testbot>.
-        fn say_hello_world(&mut self);
+        fn say_hello_world(self: Pin<&mut Testbot>);

-    let testbot = ffi::new_testbot();
-    testbot.say_hello_world();
+    let mut testbot = ffi::new_testbot();
+    testbot.pin_mut().say_hello_world();


package.json missing in .vscode\extensions\Ionide.Ionide-FAKE-1.0.9

when installed

Please try updating package to latest version (1.0.10) or reinstalling it completely .


Allow run to take an array

I think it would be nice to provide an array variant of the the run methods in addition to the APIs with variadic args. This would make code less awkward in cases where argument lists are generated programatically
I might be able to take a crack at it if you think it would be appropriate.
Thanks for the great package!

Oh I see now that the args get flattened so this isn’t needed. Closing 😇

Oh I see now that the args get flattened so this isn’t needed. Closing 😇

They already take arrays. Try it :)

jan. 2021 kl. 19:11 skrev Ryan Meisters<EMAIL_ADDRESS>

I think it would be nice to provide an array variant of the the run methods in addition to the APIs with variadic args. This would make code less awkward in cases where argument lists are generated programatically
I might be able to take a crack at it if you think it would be appropriate.
Thanks for the great package!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

They already take arrays. Try it :)

jan. 2021 kl. 19:11 skrev Ryan Meisters<EMAIL_ADDRESS>

I think it would be nice to provide an array variant of the the run methods in addition to the APIs with variadic args. This would make code less awkward in cases where argument lists are generated programatically
I might be able to take a crack at it if you think it would be appropriate.
Thanks for the great package!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


Loodse => Kubermatic, update OWNERS

What this PR does / why we need it:
This updates the OWNERS and fixes a few leftovers where the code still said "Loodse".
Optional Release Note:
NONE

/retest

/retest

/retest

vsphere cluster is currently unavailable, so these cannot succeed:
/override pull-machine-controller-e2e-vsphere
/override pull-machine-controller-e2e-vsphere-resource-pool


Update sql-server-migration-assistant-for-access-accesstosql.md

Correct typo in Working with SSMA for Access Console description

@brabe : Thanks for your contribution! The author, @Shamikg, has been notified to review your proposed change.

Merging typo fix
@brabe Thanks


occasionally  Found shared references to a collection

one entity:
   @OneToMany(cascade = CascadeType.ALL, fetch = FetchType.EAGER)
    @JoinColumn(name = "demand_no", referencedColumnName = "demand_no", insertable = false, updatable = false)
    List<Goods> goodsList;

query:
QueryResults<ProduceDemand> tuples = jpaQueryFactory.selectFrom(qProduceDemand)
                .where(buildPredicate(demandPageQuery))
                .orderBy(qProduceDemand.id.asc())
                .offset(pageable.getOffset())
                .limit(demandPageQuery.getPageSize())
                .fetchResults();

Occasionally. What seems to be the problem,thanks

Could you please provide more detail? This includes version numbers of Querydsl and other relevant dependencies, the relevant stacktrace and any other relevant information that could help others to understand the problem. Thanks!

Could you please provide more detail? This includes version numbers of Querydsl and other relevant dependencies, the relevant stacktrace and any other relevant information that could help others to understand the problem. Thanks!

querydsl:4.2.2
hibernate-core:5.4.9-Final
springboot:2.2.2.RELEASE
tomcat:9
jdk:11
ProduceDemand.goodsList once in a while is empty.
I found org.hibernate.engine.internal.StatefulPersistenceContext#addCollectionByKey  sometimes return empty
ProduceDemand:
@Getter
@Setter
@javax.persistence.Entity
@Table(name = "osiris_produce_demand")
@DynamicInsert
@DynamicUpdate
@AggregateRoot
@FieldDefaults(level = AccessLevel.PRIVATE)
@NoArgsConstructor
public class ProduceDemand extends BaseJpaEntity implements Entity<ProduceDemand> {

    private static final long serialVersionUID =<PHONE_NUMBER>313406381L;

    @Column(name = "demand_no")
    String demandNo;

    @Column(name = "demand_status")
    @Convert(converter = DemandStatusEnumConverter.class)
    DemandStatusEnum demandStatus;

    @Column(name = "seller_id")
    String sellerId;

    @Column(name = "seller_name")
    String sellerName;

    @Column(name = "company_name")
    String companyName;

    @Column(name = "total_amount")
    Long totalAmount;

    @Embedded
    Invoice invoice;

    @OneToOne(cascade = CascadeType.ALL, fetch = FetchType.LAZY)
    @JoinColumn(name = "demand_no", referencedColumnName = "demand_no", insertable = false, updatable = false)
    Craft craft;

    @OneToMany(cascade = CascadeType.ALL, fetch = FetchType.EAGER)
    @JoinColumn(name = "demand_no", referencedColumnName = "demand_no", insertable = false, updatable = false)
    List<Goods> goodsList;

Goods:
@Getter
@Entity
@Table(name = "osiris_produce_demand_goods")
@DynamicInsert
@DynamicUpdate
@AllArgsConstructor
@NoArgsConstructor
public class Goods extends BaseJpaEntity implements ValueObject<Goods> {

    @Column(name = "demand_no")
    String demandNo;

    String goodsName;

    Long goodsUnitPrice;

    Integer goodsNums;

    Long goodsTotalPrice;

query:
 @Override
    public ProduceDemand loadByDemandNo(String demandNo) {
        return jpaQueryFactory.select(qProduceDemand)
                .from(qProduceDemand)
                .where(qProduceDemand.demandNo.eq(demandNo))
                .fetchOne();
    }

From : https://stackoverflow.com/a/1694236/2104280

Hibernate shows this error when you attempt to persist more than one entity instance sharing the same collection reference (i.e. the collection identity in contrast with collection equality).
Note that it means the same collection, not collection element - in other words relatedPersons on both person and anotherPerson must be the same. Perhaps you're resetting that collection after entities are loaded? Or you've initialized both references with the same collection instance?

This issue happens because managed entities in the persistence context that reference synchronised table spaces (the tables projected in the queries) are flushed to the database before executing the query.
If you want to prevent this flush you can do so by setting setFlushMode(FlushModeType.COMMIT) on your QueryDSL query.
Most likely however, you want to fix the bug in your code that causes these collisions between managed collections.


Ensure the exception message is logged in case of error.

Resolves #177

Codecov Report

Merging #182 into master will decrease coverage by 0.32%.
The diff coverage is 74.28%.

@@             Coverage Diff              @@
##             master     #182      +/-   ##
============================================
- Coverage     86.54%   86.21%   -0.33%
  Complexity      673      673
============================================
  Files            80       80
  Lines          2081     2097      +16
  Branches        110      110
============================================
+ Hits           1801     1808       +7
- Misses          206      215       +9
  Partials         74       74

Impacted Files
Coverage Δ
Complexity Δ

...service/WorkflowServiceInstanceBindingService.java
84.53% <100%> (+0.32%)
43 <2> (ø)
:arrow_down:

...ce/AppDeploymentDeleteServiceInstanceWorkflow.java
100% <100%> (ø)
11 <1> (ø)
:arrow_down:

...broker/service/WorkflowServiceInstanceService.java
98.94% <100%> (+0.03%)
42 <3> (ø)
:arrow_down:

...ce/AppDeploymentCreateServiceInstanceWorkflow.java
97.5% <50%> (-2.5%)
12 <0> (ø)

...ce/AppDeploymentUpdateServiceInstanceWorkflow.java
97.14% <50%> (-2.86%)
11 <0> (ø)

...oker/deployer/BackingServicesProvisionService.java
91.17% <57.14%> (-8.83%)
13 <1> (ø)

...ework/cloud/appbroker/deployer/DeployerClient.java
94.23% <62.5%> (-5.77%)
12 <2> (ø)

...ppbroker/deployer/BackingAppDeploymentService.java
95.83% <75%> (-4.17%)
10 <1> (ø)

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 3876ed6...5f843db. Read the comment docs.


Allow UdonSharp to be downloaded via unitypackage

Feature Description:
Allow UdonSharp to be downloaded via unitypackage
Additional context:
Many users still have not downloaded the VCC. There is still the ability for people to create projects through the template repos on github. However, there doesn't seem to be a way to install the latest version of UdonSharp, which a lot of projects rely on.

YES!  Honestly though there really isnt much of a point not using the VCC at this point since its basically just a package manager and thats it


Digitalocean metadata doesn't work anymore after switching to 20.03

Describe the bug
It fails to set up metadata as there is no route to the metadata service:
To Reproduce
[root@localhost:~]# curl  http://<IP_ADDRESS>/metadata/v1/hostname
curl: (7) Failed to connect to <IP_ADDRESS> port 80: No route to hos

Expected behavior
The metadata service is reachable
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
Notify maintainers

Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute:
# a list of nixos modules affected by the problem
module:

This seems to be an issue with networkd + systemd-nspawn. It seems to think 169.254.*.* is free and allocates the network range to a container I started up.
[root@localhost:~]# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
<IP_ADDRESS>         <IP_ADDRESS>     <IP_ADDRESS>         UG    1024   0        0 ens3
<IP_ADDRESS>         <IP_ADDRESS>         <IP_ADDRESS>         U     2048   0        0 vz-nixos
<IP_ADDRESS>     <IP_ADDRESS>         <IP_ADDRESS>     U     0      0        0 vz-nixos
<IP_ADDRESS>     <IP_ADDRESS>         <IP_ADDRESS>   U     0      0        0 ens3
<IP_ADDRESS>     <IP_ADDRESS>         <IP_ADDRESS> UH    1024   0        0 ens3
<IP_ADDRESS>    <IP_ADDRESS>         <IP_ADDRESS>   U     0      0        0 vz-nixo

I fixed this by enabling Link-Local addressing in networkd.
However changing the .networks option didn't result in networkd applying the change (networkd didn't restart) which is a bug
After manually restarting networkd the route was corrected but still couldn't access. After rebooting it did work
Fix is here for people interested: https://github.com/arianvp/nixos-stuff/commit/00253407df668fb436d1d7d8263a660b3d0fb921


Responsiveness

Currently the website is not responsive at all. Since the gameplay just consists of tapping and text input, it could just aswell work on mobile devices, if the elements are correctly made responsive via media queries and smart flexbox usage.

the webpage is not scrollable, you should look into that.

the webpage is not scrollable, you should look into that.


VS hangs when you show all folders in Core Web App

Install WPT 25803.00 and apply all work-arounds, fixes, etc.  Eliminate App Insights.
Create a Core Web Application Project (no auth)
Only the Controllers folder is displayed in Solution Explorer:

Click on the Project node and select the Show All Files button:

Result: VS hangs
Note: If I restart VS and reopen the project, I can now Show All Files.

I am unable to create a net core web app on latest wpt/d15prerel builds - I get an object reference not set to an object dialog on attempting to create it. @srivatsn Can you create one?

@balachir @jinujoseph - known?

I just tried this on d15prerel - 25825.2 and was able to create fine and did not see the hang as well.

Thanks @jinujoseph - I am closing this issue.


Support for augmenting with websearch_to_tsquery()

As seen here: https://www.postgresql.org/docs/11/functions-textsearch.html
I would assume this happens at the call level:
class Post < ApplicationRecord
	pg_search_scope :search_by_title, against: :title
end

Post.search_by_title("word|word")
Post.search_by_title.websearch("word or word")

I released a library based on pg_search supporting websearch queries. If your search usecase is simple enough, it might be a possible option.

I'm interested in this functionality as well. I'll like to get feedback from the core maintainers: how much work do you think would adding this feature require? I would like to get a sense of if I could dig in and contribute it, or if it's more of a massive effort. I have no prior knowledge of the pg_search codebase.

+1 on this, though I'd add that I'd find it most useful if I could do a multisearch that uses Postgres' websearch.

+1 on this ... is there a chance you could use something similar to Elixir ecto's fragments for it?

It would be great to have this feature.

+1 on this, I'm migrating an app to rails and I was previously using websearch_to_tsquery, this library has been amazing so far but would be great if we could choose which type of search function to use


Implement embed feature

Figure out how to embed YT videos into guide instead of it just being a link.

It looks pretty good on the website:

But won't look good on the readme in GH.

That's okay. Let's prioritize site over GitHub readme.


Update contact-pstn-service-desk.md

Updated information on contact info from the PSTN Service Desk to reflect updated contacts

@nenonix @JohanFreelancer9 Copy editing is needed for this PR. Thanks.

@tonysmit PR has been copyedited and is ready for final review, could you please check and merge? Thanks!

I accepted a couple minor copy edits to test a bug fix implemented by GitHub. @tonysmit still needs to review and merge.

@tonysmit could you help us review and push this change?


resolves #61 allow slide selector to be specified

This patch does introduce some cyclomatic complexity and a slight increase in file size, but I think it completes the picture.
For complaint browsers, the ideal arguments are as follows:
bespoke.from({ parent: 'article', slides: ':scope > section' }, [(plugins)]);

However, :scope is still a fairly recent addition. Of course, this patch provides plenty of other ways to arrive there, including:
bespoke.from({ parent: 'article', slides: 'article > section' }, [(plugins)]);

or even :root article > section to break out of the context.

Thanks for the pull request! I'll bump the version once we've merged your other pull request.

Super! Thanks @markdalgleish!


[Azure.AI.OpenAI] Add net8.0 target / remove RequiredTargetFrameworks workaround

A net8.0 target is going to be added to RequiredTargetFrameworks in https://github.com/Azure/azure-sdk-for-net/pull/46637
A workaround was added to Azure.AI.OpenAI because there are a number of blocking issues preventing it from adding a net8.0 target:
The primary issue is that OpenAI has internals visible to Azure.AI.OpenAI. However, OpenAI only has a net6.0 target. There are a couple internal polyfill attributes that are not trimmed from the net6.0 dll, since these attributes are not available in net6.0. Since there is no net8.0 target, the net8.0 target in Azure OpenAI falls back on the net6.0 target.
The following attributes cause compiler failures because these attributes exist in both System.Runtime and OpenAI:

ExperimentalAttribute
SetsRequiredMembersAttribute

In order for Azure OpenAI to be able to have a net8.0 target, I believe the OpenAI library will need to release with a net8.0 target first. Alternatively, it should work to turn off internals visible to in the OpenAI library. Once that is done the workaround should be removed from Azure.AI.OpenAI.

Created an issue in OpenAI as well for tracking: https://github.com/openai/openai-dotnet/issues/272


When Saving Buffer to Bytes (@db.bytea) Field In Postgres Connection Buffers of Length < 8192 Are Filled To Meet 8192 Length

Bug description
I am using the Bytes field in conjunction with the @db.bytea native type to save binary data through prisma2 to a postgres database. For Buffers larger than 8192 byte length this has worked well, and I can see saves correctly, but when the byte length is less than 8192, the buffer is filled with values to meet the 8192 length, resulting in invalid data polluting the retrieved buffer when querying the database. For example, when saving a Float32Array to database using this method, I can see the values do end up in the saved buffer, but is also polluted with other, invalid data.
How to reproduce

Create database with Bytes field on any model and @db.bytea native type using a Postgres database.
Create a buffer of byte length < 8192 and save it to the database.
Retrieve the buffer from the database.
Inspect buffer byte length and contents to confirm not does not match original buffer.

Expected behavior
Buffer should match original buffer used to add data to database.
Prisma information
Example Schema
model BufferData {
  id             Int            @id @default(autoincrement())
  buffer         Bytes          @db.ByteA
}

Example mutation and query:
const intArray= new Uint8Array([0, 1, 2, 3]);
const dataArrayBuffer = Buffer.from(intArray.buffer);

const newData = await prisma.dataBlock.create({
    data: {
        buffer: dataArrayBuffer,
    }
});

const exampleData = await ctx.prisma.bufferData.findUnique({
    where: {
        id: newData.id,
    },
});

console.log(exampleData.data.buffer.byteLength);

Environment & setup

OS: Windows 10
Database: PostgreSQL
Node.js version: v12.18.0

Prisma Version
prisma               : 2.24.1
@prisma/client       : 2.24.1
Current platform     : windows
Query Engine         : query-engine 18095475d5ee64536e2f93995e48ad800737a9e4 (at<EMAIL_ADDRESS>Migration Engine     : migration-engine-cli 3c463ebd78b1d21d8fdacdd27899e280cf686223 (at<EMAIL_ADDRESS>Introspection Engine : introspection-core 3c463ebd78b1d21d8fdacdd27899e280cf686223 (at<EMAIL_ADDRESS>Format Binary        : prisma-fmt 3c463ebd78b1d21d8fdacdd27899e280cf686223 (at<EMAIL_ADDRESS>Default Engines Hash : 18095475d5ee64536e2f93995e48ad800737a9e4
Studio               : 0.397.0

Sorry for late reply here.
I am unable to reproduce this with Prisma 2.28 and Node 14. Can you please try this again with the latest version and also update your node version?


smartdns: 40 -> 41

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/smartdns/versions.
meta.description for smartdns is: A local DNS server to obtain the fastest website IP for the best Internet experience
meta.homepage for smartdns is: https://github.com/pymumu/smartdns
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 41 with grep in /nix/store/gc363p7ya97hvy8m1bfjj5d1dpvk78l9-smartdns-41
found 41 in filename of file in /nix/store/gc363p7ya97hvy8m1bfjj5d1dpvk78l9-smartdns-41

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
smartdns

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/gc363p7ya97hvy8m1bfjj5d1dpvk78l9-smartdns-41 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A smartdns https://github.com/r-ryantm/nixpkgs/archive/7355953d4912a77670891d3eb82ab77ed998d03f.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/gc363p7ya97hvy8m1bfjj5d1dpvk78l9-smartdns-41
ls -la /nix/store/gc363p7ya97hvy8m1bfjj5d1dpvk78l9-smartdns-41/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

smartdns

Maintainer pings
cc @LEXUGE for testing.

Result of nixpkgs-review pr 220550 run on aarch64-linux 1

1 package built:

smartdns


[Feature Request] A configurable option to disable the bottom tabs

The bottom tabs frequently share a space with UI from other mods such as Scout as shown in the image below. This makes them effectively incompatible.

A way to move the tabs or an option to disable them would resolve this.

I'm currently planning on adding Scout compatibility, but adding the option to disable a row of tabs is a good idea.


Fork off the hyplerledger-client tree

It would certainly ease packing with NPM and also doc references if this tree was relocated to it's own repository. I could easily rewrite the tree into another repo if you want to do it. Then it could be installed with npm, and referenced on the official index.
https://github.com/hyperledger/fabric/tree/master/sdk/node

@EvanCarroll the client SDK can indeed be retrieved from npm. The module name is 'hfc'.. Closing.


RFC: plan for deprecating process hook's single-dispatch mode over the next couple versions

I wanted to see if anyone has any thoughts about this. I'm thinking it would be best to deprecate the process hook's single-dispatch mode which comes into play when you use the signature process({ getState, action }, dispatch)
// single dispatch mode enabled by including dispatch but not done
process({ getState, action }, dispatch) {
  dispatch(newAction) // call dispatch exactly once
}

We would keep the other two process hook signatures:

process({ getState, action }, dispatch, done) // multi-dispatch
process({ getState, action }) // return dispatching

We would also deprecate the dispatchMultiple option and add a warnTimeout option.
Here's some background on the issue and my proposed plan for deprecating is at the end.
tl;dr
The process hook has a variable signature that enables three modes currently (multi-dispatch, single-dispatch, and return dispatching). The original mode single-dispatch is confusing and easily misused by users.
Deprecating and eventually eliminating single-dispatch mode should reduce confusion and prevent many mistakes.
A new warnTimeout (configurable by option) will inform users in development if they are failing to call done after finishing dispatching. It can be disabled for intentional never ending logic.
Backstory
In that single-dispatch mode, the process hook expects dispatch to be called exactly once.
This is problematic since newcomers don't realize the nature of this, so they copy this single-dispatch code and will try to use it for multiple dispatches accidentally. It isn't obvious from the signature that they can't do this.
Another problem with single-dispatch mode is that since it requires dispatch to be called exactly once, you have to call it empty if you don't want to dispatch anything dispatch() which is also counter intuitive.
So while it seemed like a good idea originally for a common use case, it ends up being more confusing for people and that's not good.
However switching to the full signature (multiple-dispatch) form of process solves all of these problems with the slight disadvantage of an extra line of code to call done.
// normal multiple-dispatch mode
process({ getState, action }, dispatch, done) {
  dispatch(newAction) // call dispatch zero to many times
  done(); // call done when finished dispatching
}

To avoid confusion, I've changed the examples to use this since it is safer for people to learn from and they can do 0 to many dispatches as they see fit.
So going forward it is my proposal that we support only two of the three signatures for the process hook, dropping the single-dispatch mode.

process({ getState, action }, dispatch, done) // normal multi-dispach
process({ getState, action }) // return dispatching

For those that haven't seen the second form which was introduced with processOptions is great for working with promises, async/await, and observables. It uses the return value for dispatching:

undefined - no dispatch
object - assumed to be an action, so dispatched
promise - dispatch the resolved/rejected actions
observable - dispatch the next/error actions
error - dispatch the error, wrapping if no type

You can also influence the dispatching with processOptions as mentioned in the docs.
Proposed plan for deprecating process hook's single-dispatch mode
deprecate single-dispatch mode - breaking change v0.12

add warnTimeout option w/default of 60s - (development ENV only) that warns in console.error if logic is still running after the elapsed time

logic is still running after 60s, forget to call done()? For non-ending logic, set warnTimeout: 0.

console.error in createLogic for process hook definitions that omit done and don't have either dispatchMultiple=true or warnTimeout=0 (!production ENV) that

single-dispatch mode is deprecated, call done when finished dispatching. For non-ending logic, set warnTimeout: 0

console.error in createLogic for processOptions.dispatchMultiple=true (!production ENV),

dispatchMultiple is always true in next version. For non-ending logic, set warnTimeout to 0

eliminate single-dispatch mode - breaking change v0.13
(We would delay v0.13 for at least a couple weeks to allow for consumers to get deprecation warnings in development)

dispatchMultiple will be true by default internally but no longer can be set as an option. Users that were using it for never ending logic will want to set warnTimeout: 0 instead
throw error in createLogic if process hook definition has dispatch but omits done and the warnTimeout is not set to zero.

done must be called when dispatching is finished or never ending logic should set warnTimeout: 0.

throw error in createLogic if dispatchMultiple is set (!production ENV)

dispatchMultiple option is no longer needed, set warnTimeout:0 for non-ending logic

retain the warnTimeout w/default of 60s as is (development) to help people from having unintentional non-completing logic.

Hi, @jeffbski. This was definitely something that I overlooked when starting to use this tool.  I'd probably spent a few hours on it until I finally read more closely and saw that I needed to include and call done.
With that said, I was converting from thunks where I was hastily coping and pasting my previous code into the process hooks.
Are you finding that it's new users who have used neither of the previous middleware that are overlooking this as well?

@jktravis Yeah, just recently a few people who just started with redux-logic ran into the same problem. They would take the single-dispatch code and just add a few dispatches to it, which would seem to be fine but then it doesn't work. So it just seems that single-dispatch mode is more trouble than it's worth. We want everyone to fall into the pit of success. They shouldn't have any of the problems if they start from the full dispatch/done multi-dispatch signature. And then the new warnTimeout will even warn them (console.error) if they forget to call done in development mode.

I personally like the variability provided through the arity of the process().
This has become a common pattern used in such things as providing asynchrony to unit tests (i.e. the optional "done" parameter for asynchronous mocha tests).
Because I would assume that a single dispatch is more common, it seems inappropriate to require an additional done() call in the new proposal.
I personally think this is a training issue.  If you should decide to keep the current API, any confusion could be mitigated in two areas:

More emphasize in the documentation.
The same development warnTimeout (proposed here) could be applied to the existing API as well:

single-dispatch mode: failure to call dispatch(), or incorrectly calling dispatch() a second time
multi-dispatch mode:  failure to call done()

Thoughts?

@KevinAst That's an interesting idea that I hadn't considered. I'll ponder the failure cases for both situations some more.


Update PPO for better performance and closer alignment to sb3

Recently I played with the PPO model in rl-ts and found that the model was not very stable when playing the cartpole environment.
So I made a few changes and bug fixes with reference to the PPO implementation in sb3:

Add mini-batch updates
Unified policy and value function optimizers into one and combined loss from policy and value function
Adjusted return formula according to sb3 updated implementation
Updated a few formulas to match sb3 more closely
Removed KL limit by default

These changes made the implementation (magenta) much more stable and reach optimal return earlier as compared to the original one(blue and black):

I checked the sb3 version and it also doesn't have max KL limit by default, though it does reach the max limit of 1.5 * 0.01 slower (epoch 7/8) than this implementation (1/2). So more work is needed to get closer match to sb3.
Let me know if you are interested in updating this library. I can open a PR to merge my updates.

i'll welcome a PR!
In fact this library needs some massive changing as it was built to reference spinning ups implementations but they don't scale well on GPU due to storing the model on each separate cpu thread and combining gradients

Ok I will open a PR to merge meaningful changes.
Another thing in parallel computation: it seems that tfjs doesn't allow tidy in async functions, so there are memory leaks in the current implementation.
I had to remove the cluster tools in my code to resolve the memory leak, but I won't include that in this PR as it is a big change. Have to investigate how to get the parallel setup working without async or somehow clean up the tensors in another way.


Renamed the Metrics howto to Application Metrics

Done for better consistency among runtime docs in RHOAR. Relates to RHOARDOC-1437

[x] Have you followed the guidelines in our Contributing document?
[x] [v2] Have you created a JIRA and used it in the commit message?
[ ] [v4] Have you created a GitHub Issue and used it in the commit message?
[x] Have you checked to ensure there aren't other open Pull Requests for the same issue?
[x] Have you built the project locally prior to submission with mvn clean install?

Thanks, @Ladicek, merging.


Confidence scores with Zipformer models

Hi all,
I am decoding a Zipformer model with sherpa-onnx (and K2/icefall) and I am wondering if there is any way to get confidence scores for the hypothesized tokens with sherpa-onnx-offlne or other tools.
If this is not possible, can you please share any hints on where I can get this information from the source-code or how I can generate the confidence scores? Information from K2/icefall scripts and programs will be helpful also.
Many thanks.
Bac

Yes, it is possible.
Taking the greedy search as an example,
https://github.com/k2-fsa/sherpa-onnx/blob/03ff9db56e9ed7c0252ae036be333de5db75a746/sherpa-onnx/csrc/offline-transducer-greedy-search-decoder.cc#L52-L55
You can get the log_prob of a token from the above code.
Note that you can compute log_softmax from logit and then get the log_prob of the max token at time t.

Thanks a lot, Fangjun. It helps!

https://github.com/k2-fsa/sherpa-onnx/pull/571


Add Captions to Images

As described in this blog post it's fairly easy to add images captions in hugo. This adds that feature to smol without impacting existing articles.

Hey @pfandzelter, thanks for your PR! This looks like a fantastic feature to have. However, I can't get it to work - I can embed an image with a title and it correctly outputs HTML with the corresponding title tag, but the image caption doesn't actually show up in the browser. Do you have an idea why that might be? I assume it works on your end?
I'm testing this using Hugo v0.78 extended on Fedora Linux.

Thanks @colorchestra, I checked again and it seems that I needed to move the render-image.html to a _markup folder. I tried it with a new blog and it worked great now.

Hey @pfandzelter, thanks, the captions look great! However, I am now a bit unhappy about the fact that images with captions (or "figures") are displayed smaller than images without captions. Sorry for being this nitpicky, but could you help me fix this?
Adding the following lines to an article in my blog yields the result in the attached screenshot.
![Screenshot vom rpm-ostree Befehl](/static/fedora-silverblue-ostree.png)

![Screenshot vom rpm-ostree Befehl](/static/fedora-silverblue-ostree.png "The same image as above, but with a caption")

Thank you!

Actually, that seems to be a feature (?) of the HTML figure tag. Putting just these few lines into an HTML file (without CSS) gives me a similar result (the 'figure' is indented by a bit). I'll do some more research...

Hm yes, that appears to be caused by the use of the <figure> tag. We could also wrap the image without caption in a <figure> tag to make it consistent. Would you prefer both to be smaller or both to be larger?

I'd prefer them to be larger. It seems to work with inline css when using figures, like so: <figure style="margin:0">
But I'd like to avoid inline css and put it in style.css. Adding figure {margin:0} there doesn't seem to have an effect.

Ok, I wrapped the lone image in a figure tag as well (so if required, all image-related CSS can be customized consistently) and added figure: {margin: auto}, which worked for me.
In my Chrome I sometimes need to invalidate the cache with cmd/cntrl + shift + R to view the most recent CSS file, maybe that's why you didn't see the changes when changing it

That's perfect! And indeed, using "Disable cache" did the trick - TIL.
Merging this. Have a good evening!


Enhancements of Vec and CircularBuffer

Changelog

new file structure with one file per type and pub use in lib.rs
rustdoc and examples for public methods
add doctests and test modules
increased version number to 0.2.0
implement some of the methods from std::Vec for Vec
implement iter for CircularBuffer
remove deref for CircularBuffer

ok I will look into this after work

I don't have time to continue my review of this PR today but want to mention some improvements I've been meaning to add: (a) we can use the untagged-option crate to avoid needing an initial value in Vec::new, (b) we can drop the T: Copy bound by using ptr::{read,write} and being careful about destructors and (c) we can use the Unsize trait instead of AsRef and AsMut to allow using arrays larger than 32 elements as backup storage. I have prototype all these ideas in this gist.
It would be great to land these improvements in Vec, and probably in CircularBuffer as well before releasing 0.2.0. @XOSplicer would you be willing to integrate these improvements into this PR?
And in general about this PR I'd like to not provide more API surface than std::Vec for now. We can always add new API in patch releases but deprecating some API is a breaking change so I'd like to be cautious.

So I see you want to be conservative about new features in this crate, which is fine.
Incorporating the functionality for non-copy types would be out of the scope for this particular PR as I would need to remodel all trait binds. However I think working with non-copy types is essential for collections.

I propose the following:

I close this PR without it being merged to master as there are a lot of new features that might need more consideration from your side @japaric
I try to re-implement the basic functionality of this crate with non-copy types.
Only basic features are included, no extra methods that might impose maintenance burdens.
I open a new PR.

What  is your opinion on that?

A short note from my side: I work on this PR mostly for the purpose to improve my skills in rust, so I'm always happy to learn something new :smile:

@XOSplicer BTW, I took a stab at this in #4 while keeping the API minimal. (I'll need these features soon-ish so I implemented the changes). I'd love to get your feedback.

:umbrella: The latest upstream changes (presumably #4) made this pull request unmergeable. Please resolve the merge conflicts.

#4 has been merged so I'm going to close this.
@XOSplicer I hope that this served as a good exercise for you. If you are looking for more practice you could take a stab at issue #6.


[feature] #1425: add wasm runtime

Signed-off-by: Marin Veršić<EMAIL_ADDRESS>

Description of the Change
This PR adds support for executing wasm smartcontracts to Iroha.
Function parameters and return values are exchanged through linear memory via offset and length of the allocation. Since dealing with linear memory is very low-level(it's just a contiguous array of bytes) Rust types/values must be serialized to binary format before writing them to wasm memory.
Wasm binary to be able to execute must export:

WASM_MAIN_FN - function which the host calls to execute smartcontract
WASM_MEMORY - linear memory (used to exchange more complex data than integers/floats)
WASM_ALLOC_FN - function which hosts uses to allocate memory from wasm's linear memory

Notes:

Note that since wasm is sandboxed there is no way for the module to get access to hosts memory.
Writing wat directly or dealing with raw memory and manual allocation in Rust code that compiles to wasm is not a reasonable user experience. Helper functions and macros are kept for the followup PR.
Limits like wasm binary size and wasm fuel are added in a separate PR.

Should feature flag be introduced to include wasm support optionally?
Issue
#1425
Benefits
Possible Drawbacks
Usage Examples or Tests [optional]

Alternate Designs [optional]
Once WebAssembly specification adds support for Interface Types it would be much better to use those because no serialization would be required and types would just flow through wasm VM without VM actually understanding their representation.

Should feature flag be introduced to include wasm support optionally?

@takemiyamakoto what do you think?

linear memory (used to exchange more complex data than integers/floats)

I remember during the prototyping I found that the max limit for linear memory for WASM was 5GB. At the time wasmtime did not support limiting it further in an easy way (you needed to write your own allocator for this). Is there a feature to limit it further now?

Please create issues for the PRs that you plan to create and link them to this one.

I remember during the prototyping I found that the max limit for linear memory for WASM was 5GB. At the time wasmtime did not support limiting it further in an easy way (you needed to write your own allocator for this). Is there a feature to limit it further now?

@eadventurous Wasm memory is 32-bit addressable so you can't have more than 4GB of linear memory. Linear memory is allocated in 64Kb pages, limits can be defined in number of pages. Wasm module can import the memory from the host, rather than the other way around, and impose the limits on the host side

I remember during the prototyping I found that the max limit for linear memory for WASM was 5GB. At the time wasmtime did not support limiting it further in an easy way (you needed to write your own allocator for this). Is there a feature to limit it further now?

@eadventurous Wasm memory is 32-bit addressable so you can't have more than 4GB of linear memory. Linear memory is allocated in 64Kb pages, limits can be defined in number of pages. Wasm module can import the memory from the host, rather than the other way around, and impose the limits on the host side

You are correct - 4GB. I was referring to this mostly https://github.com/bytecodealliance/wasmtime/issues/2273 but I guess this needs a separate issue.


feature: Highlighting publisher if event was created by external user.

Description :sparkles:
Amazing blob to highlight if event is from external publisher.
Issues :bug:
Translations for external required?
Closes :no_good_woman:
LINK-1036:

Codecov Report

Merging #207 (1ea8699) into develop (1e2602e) will decrease coverage by 0.03%.
Report is 23 commits behind head on develop.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##           develop     #207      +/-   ##
===========================================
- Coverage    99.88%   99.86%   -0.03%
===========================================
  Files          506      507       +1
  Lines         9452     9468      +16
  Branches      2073     2083      +10
===========================================
+ Hits          9441     9455      +14
- Misses          11       13       +2

Files Changed
Coverage Δ

...ents/eventsTable/eventsTableRow/EventsTableRow.tsx
100.00% <100.00%> (ø)

... and 11 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Move done items to the bottom of the list

When marking items as done/bought, move them to the bottom

Not interesting at the moment. It feels better to keep the completed item in its place.


Better errorhandling, some logging and code cleanup

When calling the binary without arguments it would just  panic with a stack trace what is not a  great  UX. I also added two loglines so  you know  it's  running and where to reach it,  as well as a small README currently containing the generate help output of the flag module

@fleaz can you rebase this?

UX could be a bit better on required arguments. If I run this without any arguments, it now at least gives a hint about a missing host:
❯ ./vigor-exporter
panic: Post "http:///cgi-bin/wlogin.cgi": http: no Host in request URL

goroutine 1 [running]:
main.main()
	/home/flokli/dev/flokli/vigor-node-exporter/main.go:36 +0x268

It'd be nice if we could catch this already before, when parsing the command line flags.

It'd be nice if we could catch this already before, when parsing the command line flags.

This has already been fixed in 7213404acc28c3f6e5359b740d6d475644b5c5ed :)


Harmonic variable overhaul

This overhauls the HarmonicVariable type.
Previously, this would hold a pair of harmonic variables u , v which describe a harmonic, now this only holds one such variable. This makes it easier to implement cases such as a zero harmonic (= constant displacement), which is described by a single variable only.
Closes #25 (one may now use add_harmonic! to add a 0 harmonic, which creates one variable. See the quadratic_nonlinearity_renormalization.ipynb example in the notebook repo)

The checks fails because the GitHub action ignores Project.toml uses latest Symbolics 4.4.3 . The problem does not appear with 4.4.1 .


./configure: error: ngx_http_modsecurity_module requires the ModSecurity library

Hi,
I am trying to install modsecurity module for nginx
OS on i trying to install is Centos 6
steps i followed are
#-------------------------------------------------------------------------
cd /src
wget https://github.com/SpiderLabs/ModSecurity/releases/download/v3.0.6/modsecurity-v3.0.6.tar.gz
tar -xvzf modsecurity-v3.0.6.tar.gz
cd modsecurity-v3.0.6
sh build.sh
./configure --prefix=/usr/local
make
make install
#-------------------------------------------------------------------------
cd /src
wget https://github.com/SpiderLabs/ModSecurity-nginx/releases/download/v1.0.2/modsecurity-nginx-v1.0.2.tar.gz
tar -xvzf modsecurity-nginx-v1.0.2.tar.gz
#-------------------------------------------------------------------------
cd /src
wget http://nginx.org/download/nginx-1.20.2.tar.gz
tar -xvzf nginx-1.20.2.tar.gz
cd nginx-1.20.2
export MODSECURITY_INC="/src/modsecurity-v3.0.6/headers/"
export MODSECURITY_LIB="/src/modsecurity-v3.0.6/src/.libs/"
./configure --add-module=/src/nginx-rtmp-module --add-module=/src/modsecurity-nginx-v1.0.2
make
make install

Don't know what i am doing wrong , i am getting this error on ./configure command
checking for POSIX semaphores in libpthread ... found
checking for struct msghdr.msg_control ... found
checking for ioctl(FIONBIO) ... found
checking for ioctl(FIONREAD) ... found
checking for struct tm.tm_gmtoff ... found
checking for struct dirent.d_namlen ... not found
checking for struct dirent.d_type ... found
checking for sysconf(_SC_NPROCESSORS_ONLN) ... found
checking for sysconf(_SC_LEVEL1_DCACHE_LINESIZE) ... found
checking for openat(), fstatat() ... found
checking for getaddrinfo() ... found
configuring additional modules
adding module in /src/nginx-rtmp-module
 + ngx_rtmp_module was configured
configuring additional dynamic modules
adding module in /src/modsecurity-nginx-v1.0.2
checking for ModSecurity library in "/src/modsecurity-v3.0.6/src/.libs/" and "/src/modsecurity-v3.0.6/headers/" (specified by the MODSECURITY_LIB and MODSECURITY_INC env) ... not found
        ./configure: error: ngx_http_modsecurity_module requires the ModSecurity library and MODSECURITY_LIB is defined as "/src/modsecurity-v3.0.6/src/.libs/" and MODSECURITY_INC (path for modsecurity.h) "/src/modsecurity-v3.0.6/headers/", but we cannot find ModSecurity there.

Hello @GaneshKandu ,
I recently followed these instructions https://serverdiary.com/linux/how-to-install-and-configure-nginx-modsecurity-on-centos-7/ (with the exception that I just use a simple clone for the two git instructions) with nginx-1.20.1 on CentOS7 and did not encounter the error you report.
It's possible that you are encountering some issue related to the additional options and commands that you are using.
It is also possible that there is some difference related to use of CentOS 6. Since that is EOL, I haven't built with that recently.
However, perhaps the most likely explanation is that didn't do 'make install' after the 'make' within modsecurity-v3.0.6.
That exact error message will be seen if that 'make install' did not occur. See for example https://github.com/SpiderLabs/ModSecurity/issues/1805. I also just confirmed myself that that message appears if the 'make install' is missed.

Hi brother who is reading this issues, if you are having similar problems, please first check the version of ModSecurity you have installed and make sure you have v3.x installed instead of v2.x.
(In some lagging package repositories, you may have v2.x installed by default)

If you are v2.x, uninstall it. Download and compile a v3.x version from the release page, then recompile your Nginx.

If you have v3.x, then I'm sorry, I can't help you, so help yourself.

Good luck, from a programmer with an exploding mind.
Translated with www.DeepL.com/Translator (free version)


Fix phone display in whois and signup

Should list phone code on the same row, and should validate and should give choice of codes.

Please include profile too.


Add timestamps back in

I removed timestamps to make it simpler to move to Activities + Redux. Now that they're there, they can come back.
But it's worth talking about how we want them to work first.

a very simple version is back in. Awaiting your feedback and/or styles.

Noticed an issue: When the text of a sent message is really short, the chat bubble resizes abruptly when the timestamp disappears.


Can't build in watch mode or when emulators are running

Hi,
This is a quick question on why the build is not working as expected I am getting:
EBUSY: resource busy or locked, rmdir '......

When the emulators are running or when I call build watch
I am not sure why esbuild is not working any help would be appreciated.

Hi @Bullfrog1234 ,
I've never seen this issue (I'm using MacOS) and cant think of an obvious reason why it could happen.
So a couple of questions for you:

Are you running on Windows?
Is your workspace in a Dropbox or OneDrive type cloud sync folder?

Hi @simondotm,
Sorry for the late reply, been snowed under.
I am running on windows and my workspace is on a harddrive not in any autoupload areas.


🐛 Fix parsing of requests to root path of a workload cluster

Summary
kcp is rejecting (valid) calls to the root path of a cluster. With a default setup, the following error is returned:
# with KUBECONFIG pointing to some workload cluster within kcp
$ kubectl get --raw='/'
[{
  "metadata": {},
  "status": "Failure",
  "message": "unable to parse cluster: no `/` found in path root",
  "reason": "BadRequest",
  "code": 400
}]

This PR resolves this issue by fixing the parsing and removing the error. With this fix:
# with KUBECONFIG pointing to some workload cluster within kcp
$ kubectl get --raw='/'
{
  "paths": [
    "/api",
    "/api/v1",
    "/apis",
    "/apis/",
    "/apis/admissionregistration.k8s.io",
    "/apis/admissionregistration.k8s.io/v1",
    "/apis/apiextensions.k8s.io",
    ...
  ]
}

I think it may make sense to support /, /healthz, and /readyz, but we shouldn't expose /api and /apis at the root.

@ncdc Maybe I could have worded the title a bit better, but this PR solely fixes requests to the root path (/) of a workload cluster. So an endpoint like this: $HOST/apis/clusters/my-cluster/—it doesn't change anything at the root path of kcp itself

Ahh ok, thanks for clarifying. I got confused from the description, because kubectl get --raw='/' ignores any path in the kubeconfig's server and literally requests /, which we don't allow. I thought you were changing that.
I do now see what your PR is doing, and it's 👍:
Before:
k --user shard-admin get --raw /clusters/root
Error from server (BadRequest): unable to parse cluster: no `/` found in path root

After:
k --user shard-admin get --raw /clusters/root
{
  "paths": [
    "/api",
    "/api/v1",
    "/apis",
    "/apis/",
    "/apis/admissionregistration.k8s.io",
...

Some additional testing:
# get /clusters
Error from server (NotFound): the server could not find the requested resource

# get /clusters/
Error from server (InternalError): an error on the server ("cluster name is empty in the request context - RequestInfo: &request.RequestInfo{IsResourceRequest:false, Path:\"/\", Verb:\"get\", APIPrefix:\"\", APIGroup:\"\", APIVersion:\"\", Namespace:\"\", Resource:\"\", Subresource:\"\", Name:\"\", Parts:[]string(nil)}") has prevented the request from succeeding

I think the error for /clusters is good. Should we fix /clusters/ to also return a NotFound?
@stevekuznetsov do you want an e2e for this/these to make sure we don't regress?

@erwinvaneyk would you be able to fix /clusters/ too and also add a small e2e?

/lgtm
I'll follow-up with some fixes

/ok-to-test

/retest


Only arm64 Llinux headers

Describe the bug

machines:

ubuntu  23.10 mantic amd64

the file /sys/kernel/kheaders.tar.xz only  arch/arm64/

OrbStack: Version 1.5.1 (16857)

To Reproduce
No response
Expected behavior
No response
Diagnostic report (REQUIRED)
No response
Screenshots and additional context (optional)
No response

To maintain acceptable performance, OrbStack uses an arm64 kernel to run all machines, so it won't be possible to build an x86 kernel module.


openssl1.1.1c rpm build using spec file is showing issue during installtion

Hi Team ,
I have created a rpm using openssl1.1.1c source code. my rpm created successfully with name :
openssl-1.1.1c-01.x86_64.rpm
but when i am trying to upgrade my openssl old version then its showing me error something like below :+1:
error: Failed dependencies:
perl(WWW::Curl::Easy) is needed by openssl-1.1.1c-01.x86_64
openssl < 1:1.0.1-0.3.beta3 is obsoleted by (installed) openssl-libs-1:1.0.2k-19.el7.x86_64
I am not sure from where its picking up obsolete version of openssllib  - 1:1.0.1-0.3.beta3
Thanks in advance

This line was surprising too:
perl(WWW::Curl::Easy) is needed by openssl-1.1.1c-01.x86_64

I have no clue, and considering we don't even know what spec file you used, there's very little we can do.  Most of all, this sounds like a RPM / Fedora problem, so this may not be the right forum for your issue.

please find the spec file
openssl_spec.txt

Kindly check the spec file and suggest me if there is any issue with this file

I looked, and I see nothing that stands out.
Mind you, my knowledge of RPM specs is very rudimentary.  I did fiddle with that eons ago (seriously, early 2000's), but haven't touched the stuff since.  If someone else knows, they'll probably say something, but otherwise, I suggest asking somewhere else.

I would use a different package name and definitely not add Provides: openssl = %{version}_%{release}-prodeng
You are installing it outside of the system directories so there is no sense in clashing with the system openssl packages.

This question seems to have been answered. Closing.


⚠ Bofrost.fr has degraded performance

In 69fa0a3, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 999 ms

Resolved: Bofrost.fr performance has improved in 48db908 after 6 minutes.


wasapi: return early on draining for duplex callback

Return early from refill_callback_duplex when stm->draining is true

Draining is only useful for output only streams, to makes sure we've played everything that has been sent to the OS, so that the end of, say, a track, is not cut off.
This does not apply for duplex, because we're not playing files. What control the life-time of the stream is not a duration per se, or something that has to be played in its entirety. It's more like a user action, like, for example in Firefox, closing a tab, or calling AudioContext.close() or something.

Cool, code has been updated, let me know if it's ready for merge.


Update README to use latest release

EDIT: all of this is irelevant as I used a previous release.
Describe the bug
When a user launch a manual workflow after the setup, an unexplicit error happen
Steps to reproduce
Follow the steps described in the README.
Launch a manual workflow.
Expected behavior
Issues should be synchronized.
Additional context
Run<EMAIL_ADDRESS>  with:
    notion-token: ***
    notion-db: ***
context event: workflow_dispatch
context action: __instantish_notion-github-action
payload action: undefined
Starting...
Checking for issues already in the database...
Error: Cannot read property 'number' of undefined

I think that this is because there is a dummy issue in the template.

I copy and paste the workflow from the README without noticing that it uses v1.2.0. I've updated it to v1.2.3 and everything works as excepted.
You should consider update the README.

Thanks for pointing it out, I'll update it right away with the major version tag 👍🏻


VCFutils  output name kinship file

King output file is wrongly renamed:

filtered_variants.vcf VCF is used as input, output renamed as .kinship

Please change into:
print VCFUTILS_SH "cp king.kin0 $opt{OUTPUT_DIR}/$runName.filtered_variants.kinship\n";

It is renamed as $runName.kinship because king (or actually vcftools) ignores filter status. Therefore it would not make a lot of sense to call it $runName.filtered_variants.kinship?


Added a DeprecationWarning for Python 3.4

Same as issue https://github.com/nilearn/nilearn/issues/1877
Also replaced use of six with sys.version_info for Python version determination (stdlib use over ext lib).

LGTM, thx.

@bthirion  Review & Finalize but don't do any merges yet. I am exploring some merges on Nistats and if we should revert them and I don't want to complicate it if it comes to that.


Work with SSH keys only when testing on local VMs

When provisioning in artemis, artemis generates and shares SSH keys between machines

[citest]


set html and body height to 100%

Having the height of body equal to 100% of the page is necessary to set height of children elements. How about setting these by default inside skeleton-framework?
html {
  height: 100%;
}
body {
  min-height: 100%;
}

as in this stackOverflow answer.

That's a very useful technique for setting percentage based heights of child elements page-wide, for sure. However, it's not always the case that the technique is needed for a given layout. Many sites end up being built based on content height without using percentage heights at all, for instance.
It's a design decision that will be made for each project using Skeleton, so it'd be best to leave it out of the core framework.  Thanks for the suggestion!

ok thanks for the quick reply :)


How does SFU expose the portrange of webrtc portrange in the k8s container

As mentioned above, K8S does not seem to support exposing a port range, so SFU running in K8S containers cannot expose udp port range. Is there a corresponding solution?

Hi, the SFU container has hostNetwork: true, so it's able to expose UDP ports on the host machine. I chose to do this instead of assigning static ports, because it's not possible to expose a whole range in k8s so we'd be exposing ~200+ ports 1-by-1, and both scenarios share the same primary drawback (a limit of 1 SFU per host node).

I see, thanks!


Exchange version accepted

To connect from microsoft exchange, there is only until 2013 sp1 version.
The version that i used to connect in my exchange is Exchange/15.20.4778.018. 2016.
There are any other way to have sucssess in connect with exchange?

Detalhes do documento
⚠ Não edite esta seção. É necessário para a vinculação do problema do docs.microsoft.com ➟ GitHub.

ID: ee22751a-ede8-9d9e-f173-afb7b51385a5
Version Independent ID: 0bec19de-95a0-79b4-37f0-e771fa1415f0
Content: Exchange - Power Automate
Content Source: articles/desktop-flows/actions-reference/exchange.md
Service: power-automate
Sub-service: desktop-flow
GitHub Login: @mariosleon
Microsoft Alias: marleon

Hello @Mesquita07, thank you for using Power Automate. Please note that you may use the 2013 option for MS Exchange 15 as well.
Also please keep in mind that you may ask technical questions in the Power Automate community where technical experts can respond to questions and suggest solutions.


Slow first load

It takes around 8s before  component show for the first time on iOS. UI thread is frozen and after 8 seconds camera show on the screen. Any following showing/hiding camera is very fast.
Has anybody else similar issue?

I am having the same issue. I just show a spinner underneath...

Me too. I also show a spinner for now. I look into the code but I could not figure out what is taking so long.

Does anyone have a solution please?

I managed to get around this forcing '[self.session startRunning]' to run in the main queue. This can be found in the startSession method in the ALPRCameraManager.mm file. As this seems like a threading issue use at your own discretion.

Nice. Well done @mike-at-tiffik . Since it is just three lines of code, can you please submit a PR?

Will do.
Cheers
Mike
Mike Boyns
Software Developer
email<EMAIL_ADDRESS>web:	 http://www.tiffik.com
mobile:	07743 719932

Tiffik Solutions Limited
Specialising In Creating And Delivering Bespoke IT Solutions.
Website design, E-Commerce and Mobile
Registered in England and Wales. No 11398486

On 21 Sep 2018, at 13:58, Robert Sasak<EMAIL_ADDRESS>wrote:
Nice. Well done @mike-at-tiffik https://github.com/mike-at-tiffik . Since it is just three lines of code, can you please submit a PR?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/cardash/react-native-openalpr/issues/26#issuecomment-423522037, or mute the thread https://github.com/notifications/unsubscribe-auth/AoMdoLlODNmLLtJuSihgJ2yP7rA1QeWqks5udOJjgaJpZM4Qk5CJ.


PowerToys Run Mica disables

Microsoft PowerToys version
0.80.1
Installation method
GitHub, PowerToys auto-update
Running as admin
No
Area(s) with issue?
PowerToys Run
Steps to reproduce
I, really don't know, when I enter fullscreen on something, there is an extremely high chance of mica disabling, but other times when I use PT Run many times, it just disables by itself
✔ Expected Behavior
It having a Mica Effect
❌ Actual Behavior

it is stuck on a gray background
Other Software
No response

I checked all of them out, none of the original questions have any answers

Encountered the same issue.

/dup https://github.com/microsoft/PowerToys/issues/30297


panic when stream with more than one token ends with any white space

Hi, This code:
import (
	"bytes"

	"github.com/bzick/tokenizer"
)

func main() {
	// configure tokenizer
	parser := tokenizer.New()

	// create tokens' stream
	stream := parser.ParseStream(bytes.NewBufferString("test coucou\n"), 4096)
	defer stream.Close()

	// iterate over each token
	for stream.IsValid() {
		// do something...
		stream.GoNext()
	}
}

Produces this panic:
panic: runtime error: index out of range [1] with length 1

goroutine 1 [running]:
github.com/bzick/tokenizer.(*parsing).parse(0xc000196340)
	/home/nicolas/go/pkg/mod/github.com/bzick/tokenizer@v1.4.6/parser.go:158 +0x2db
github.com/bzick/tokenizer.(*Stream).GoNext(0xc0001a4120)
	/home/nicolas/go/pkg/mod/github.com/bzick/tokenizer@v1.4.6/stream.go:103 +0x6f
main.main()
	/home/nicolas/testmodule/main.go:21 +0x1d4
exit status 2

Removing either the \n or the coucou part of the string makes it work without crashing.

Thank you! v.1.4.7


Neeraj: Tasks 833-836 jnlpba, bn_hate_speech

@nrjvarshney, wondering if you can help review this PR?

General comments:

Follow the JSON format. You don't have categories, contributors field

Task 833-

Task definition needs improvement --> "A sequence of tokens will be provided in a list. ..". you are giving a string as input instead of a list. Start with something like "In this task, ...".
Define what a token is - is it one word or something else?
Elaborate the explanation

Apply these to all tasks. I'll review after that

@SagarRudagi, can you address reviewer comments and let @nrjvarshney know so that he can review further?

Hey Swaroop,
Sorry for the late reply. I was really caught up with other immediate
assignments. I'll do this tonight and update it.
Regards,
Sagar Rudagi
On Tue, 21 Sep, 2021, 4:13 pm Swaroop Mishra, @.***>
wrote:

@SagarRudagi https://github.com/SagarRudagi, can you address reviewer
comments and let @nrjvarshney https://github.com/nrjvarshney know so
that he can review further?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/swarooprm/CSE576HW/pull/94#issuecomment-924455111,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKKIPDSZXWTAECQQR2KA4ILUDEGSBANCNFSM5EBSBWLQ
.

@nrjvarshney, check if you are happy with the changes or have any other feedback?

suggested task definition:
'In this task, a sequence of tokens is provided and you need to classify each token as '0', '1', or '2' where '0' corresponds to  Non-bio entity, '1' to Bio entity start token, and '2' to Subsequent bio entity tokens. Each word in the sentence is called a token.


Allow typing with keyboard in menuitemKeyboard

https://github.com/user-attachments/assets/ada6d54b-cf66-4cf1-aa30-53680111a44d
Closes #489.
Features

Togglable between text input and traditional input modes
Utilizes SDL's text input event handling.
Filters input to only accept characters available to the on-screen keyboard.
Synchronizes capslock state with the OS (including shift). This means CAPS on the on-screen keyboard becomes disabled since it is managed under the hood.
Plays sound effects the same way as the traditional input. eg. entering/deleting a character, toggling CAPS, etc...
Exhibits all the same quirks as the traditional input, such as playing char entry sound effects when the screen space to enter a char has become exhausted but the buffer's limit hasn't been reached.
Disables and hides itself if the player is using a controller. Originally, it disabled and dimmed the text if using a controller, but I felt it was more appropriate to actually remove it from the dialog, in that case.

Issues

"TYPE WITH KEYBOARD" is a non-localized string.
backspace key will repeat at the game's framerate, as opposed to every other key, which will repeat at the OS's repeat interval.
Holding capslock will cause it to "repeat" and can desync its state from the hardware. I tried pretty hard to fix this but it seems to be intractable.

Hold on, if you're using the text input event, why the manual modifier key handling?

Manual capslock handling is necessary to synchronize the on-screen keyboard with my physical keyboard's capslock state, but, in reality, it's whatever the OS is reporting as the current capslock state. Technically, this synchronization is not required for it to actually function correctly (such as inserting capitalized keys by holding shift); I just thought it was a nice touch.

Okay, by testing with 3 players, I've found a potential issue, but I believe it is unrelated to the PR. Actually, I've also seemingly discovered a bunch of bugs unrelated to my PR for splitscreen multiplayer. I'll document them in their own issues.
The way I tested 3 players was hacky, though. If I turn off and turn on my controller, it detects both the controller and the receiver as separate controllers, so I'm able to control players 2 and 3 with a single controller.

Found out about FakeGamepads just now, so I can simulate 4 players. Realistically, a scenario where there is more than one connected keyboard won't happen, right? Otherwise, I'll need to make some changes.

There is no multiple keyboard support in SDL2, so we can't really do that even if we wanted to.

Fixed an issue with mouse scrolling in a keyboard menu. The taller height of it with the "TYPE WITH KEYBOARD" button had made it a much more noticeable problem.


Update nfdi4plants_ontology.obo

add "Jar"

The added term was falsely "is_a"ed to an external parent term.
@muehlhaus ;)


list formatting in http://scanner.run/docker.html

See list of configurations at bottom of page.   Not rendering as a list.

Should be fixed


Change visibility for SpanFactory and StartSpanOptions (#240)

Change visibility for SpanFactory and StartSpanOptions to allow testing and implementation. Add a public SpanContext.create. Make SpanFactory methods protected and StartSpanOptions getters public.

(cherry picked from commit 473af8e4205feac693b5f40d91824e0c5102b849)

Codecov Report

Merging #242 into v0.4.x will increase coverage by <.01%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             v0.4.x     #242      +/-   ##
============================================
+ Coverage     94.88%   94.89%   +<.01%
- Complexity      432      433       +1
============================================
  Files            60       60
  Lines          1311     1312       +1
  Branches         91       91
============================================
+ Hits           1244     1245       +1
  Misses           41       41
  Partials         26       26

Impacted Files
Coverage Δ
Complexity Δ

...google/instrumentation/trace/StartSpanOptions.java
92% <ø> (ø)
13 <0> (ø)
:arrow_down:

.../java/com/google/instrumentation/trace/Tracer.java
100% <ø> (ø)
9 <0> (ø)
:arrow_down:

.../com/google/instrumentation/trace/SpanContext.java
92% <100%> (+0.33%)
15 <2> (+1)
:arrow_up:

...umentation/trace/BinaryPropagationHandlerImpl.java
86.66% <100%> (ø)
8 <0> (ø)
:arrow_down:

.../com/google/instrumentation/trace/SpanFactory.java
100% <100%> (ø)
1 <1> (ø)
: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 71fb56b...ca844e5. Read the comment docs.

Good stuff


Precompiler fails if signature function's parent is not erased.

This is an old issue, but the failure mode is new. It now fails with an assert in precompiler.cc:1010:
ASSERT(!function.IsRedirectingFactory());
To reproduce, comment out this line in class_finalizer.cc:594:
signature.set_parent_function(Function::Handle());
And run any test in the precompiler, for example:
python tools/test.py -cprecompiler -rdart_precompiled -t960 vm/dart/error_stacktrace_test

I think this failure is correct and we should be erasing the parent function. A signature function X may be created based on a function Y that the tree shaker will remove and become the canonical function for that signature. References to X from surviving functions with the same signature should not cause Y to be included in the snapshot.

Thanks for looking into this. Your conclusion matches my comments in the source, but I was still puzzled on how the parent can be erased. Anyway, this is not critical anymore. I was afraid I would need to keep the parent to fully support nested generic functions, but with my new approach, this won't be necessary. Closing the bug.


[base-ui][docs] Improve Next.js Link docs

My goal here is to fix the "https://nextjs.org/learn/basics/navigate-between-pages/link-component" redirection:

https://app.ahrefs.com/site-audit/3524616/91/data-explorer?columns=pageRating%2Curl%2Ctraffic%2ChttpCode%2CcontentType%2Cdepth%2Credirect%2CincomingAllLinks&filterId=b3b75b6257a370fcf9f1f73befb5deb5&issueId=c64d8847-d0f4-11e7-8ed1-001e67ed4656&sorting=-pageRating
Note that we are working to move out of Google Groups to a system that allows a lot more control. This will allow us to delegate the SEO crawl ownership. I have handled them as high priorities so far. The automation is described in https://www.notion.so/mui-org/Scale-collaborative-inbox-in-Google-Groups-f6f3d7a8a6bd4c24be1fc8b13a8f33f6?pvs=4 the weekly ahrefs crawls for MUI Core will land on the replacement of<EMAIL_ADDRESS>and assigned to whoever wants to own this duty.
But I went a bit outside of the scope of the initial problem 😇

Notes on things that I can see while I was fixing the URL reference:

We should trend toward a place where updating the CSS and Tailwind CSS is automated, It feels like a waste of time to manually maintain this. I think we can set the priority of automation higher than adding more Tailwind CSS demos. For example, here, I fixed a few inconsistencies between demos, e.g. border disabled.
I think that we can't use :disabled as a CSS selector. Developers might render a div, .Mui-disabled seems to be the solution.
I noticed 2. because the disable button flashes on each mount

https://github.com/mui/material-ui/assets/3165635/1c9fe993-f30e-4492-ad09-7689975bc16c
https://mui.com/base-ui/react-button/#introduction
@michaldudak I'm afraid of cases where a form may be submitted because disabled isn't set in the DOM yet while that form shouldn't be submittable.

The duplication of the introduction demo throughout the page is not great. I think that fixing this duplication is more important than improving the demos of the Base UI docs. The solution can be to rely on demo tab #38911. This will help to have higher-quality demos. Right now, I think that it's a bit demotivating for the community to try to fix them all.
There is a strange useIsDarkMode toggle in the Tailwind CSS demo. I don't understand why it's here. I would expect that we rely on the default configuration for dark mode, have it customized for the docs, and be configured for CodeSandbox/StackBlitz exports.
I find it weird to have buttonClasses.active. It doesn't seem to be superior to :active. An API to remove to keep things simple? I noticed this while I added a scale(0.99) to match the box shadow removal depth effect.
We still have a good number of legacyBehavior props used for Next.js, even ones that leak to developers' public API. I think this should be a priority to fix since it's about keeping up with the latest dependencies, otherwise, it signals to the developers that we are lagging.

@michaldudak I'm afraid of cases where a form may be submitted because disabled isn't set in the DOM yet while that form shouldn't be submittable.

If I understand it correctly, it should be fixed in #38943 by @mj12albert

I find it weird to have buttonClasses.active. It doesn't seem to be superior to :active

The :active pseudoclass is not applied to non-interactive elements (such as a span) when they are activated with a keyboard.

If I understand it correctly

@michaldudak Ah perfect, we have an open issue for this: https://github.com/mui/material-ui/issues/38943

The :active pseudoclass is not applied to non-interactive elements (such as a span) when they are activated with a keyboard.

Oh, I see, I can reproduce this problem in https://codesandbox.io/s/fervent-snyder-vchc6f?file=/src/Demo.tsx.
In https://mui.com/material-ui/react-button/#basic-button we are not supporting this case, we managed to get away from it because the &:active style is only applied with the mouse pointer, when it's triggered by the keyboard, that style is ignored (for both button and non-button host elements). I'm reverting that part then.


Repository doesn't seem to be handling UTC unix timestamps correctly

Packages are always newer than themselves? Unsure what the cause is.

What are you using to timestamp?

Is this bit of code in question?
`    [Route("/builds", "GET")]
public class BuildListRequest : IReturn<List> {
static BuildListRequest() {
JsonSetup.Setup();
}
[DataMember(Name = "updatedAfter", IsRequired = false)]
public String UpdatedAfterString { get; set; }
    [IgnoreDataMember]
    public DateTime? UpdatedAfter {
        get {
            if(UpdatedAfterString == null) {
                return null;
            }
            return DateTime.SpecifyKind(long.Parse(this.UpdatedAfterString).FromUnixTimeStamp(), DateTimeKind.Utc);
        }
        set {
            if (!value.HasValue) {
                UpdatedAfterString = null;
                return;
            }
            value.Value.ToUnixTimeStamp();
        }
    }
}`

Confirmed this is the code in question

Importantly, DateTime.SpecifyKind makes a datetime ignore what type it thinks it was, effectively "shifting" the timezone without changing the raw value: instead of 17:00 at GMT-5 becoming 22:00 at GMT, SpecifyKind(..., DateTimeKind.Utc) makes it 17:00 at GMT. ToUniversalTime doesn't seem to effect Utc times, as they are already the correct type, but it will wind the clock in the opposite direction of the datetime shift when performed.

This should be fixed in faff9a2e8ce1c9a06acf882c2cafbf8d761d196a, but I have yet to see for sure.


Cleanup OWNERS file.

Since we now have a release shepherd, we should clean up OWNERS file to ease the process of choosing the next shepherd.
In addition, we need to come up with a governance policy to allow better community-based maintenance of the codebase. One possible solution would be to remove OWNERS file and replace it with GitHub feature of CODEOWNERS or model maintainers document after counterpart from thanos-io/thanos.
/cc @coreos/team-monitoring

I think the combination of the two would be a good idea.

Done with https://github.com/prometheus-operator/prometheus-operator/pull/3407 and https://github.com/prometheus-operator/prometheus-operator/pull/3398


[Question] How to make the header sticky?

Hi,
I'm using your Alembic theme and really love it.
I'd like to ask if it is possible to make the header sticky in your Alembic template?
I saw that the header that Alembic used is not stored in the <head/> section but in a section <header/> of the <body/>.
Hence, all solutions that I tried online like below don't work
https://css-tricks.com/fixed-headers-on-page-links-and-overlapping-content-oh-my/
https://www.w3schools.com/howto/howto_js_sticky_header.asp
Thank you!

That's going to require a bit of dev work. Here's what I'd do:

Move the feature out of the header component so it sits above the main content area
Add the following CSS:

.header {
  position: fixed;
  top: 0;
  left: 0;
  right: 0;
  background: white;
}

Let us know how it goes. Going to close this as it's not a bug, but happy to chat this through ✨

@daviddarnes : excellent! I think the key point here is to set background: white;. I didn't set it previously, hence when scrolling the content could go to the top of the page.
I also need to put margin-top: 5rem; insider .feature to push the feature image down below the header when the page is first loaded. My .feature setting is like below:
.feature {
  padding-bottom: .4rem;
  margin-bottom: 1.6rem;
  text-align: center;
  background: $featureBackgroundColour;
  background-size: cover;
  background-position: center;
  min-height: 200px;
  .container {
    min-height: 35vh;
    max-width: 60%;
    @include flex-direction(column);
    @include justify-content(center);
  }

  @media screen and (min-width: 10px) {
      margin-top: 0rem;
  }

  @media screen and (min-width: 800px) {
      margin-top: 5rem;
  }
}

I have a new question. Is this possible to change the background color of the header when the webpage is scrolled?
That is, initially, the header is white. But when the image feature is scrolled and disappear, can I change the background color to dark green like the footer?

I finally can change the header's background color by adding the following code to the fiel site-header.html:
<script type="text/javascript">
 window.onscroll = () => {
   const header = document.querySelector('header');
   if(this.scrollY <= 150) header.className = 'header';
   else header.className = 'header scroll';
 };
</script>

and using this code in the file _theme.scss
// sticky header
.header {
  position: fixed;
  width: 100%;
  background: white;
}

// sticky header, change color when scrolling
.header.scroll {
    position: fixed;
    width: 100%;
    background: #e4efee;
}

I decided to not change the background color, but draw a bottom line in the header, which look nicer. Here is my code:
.header.scroll {
    position: fixed;
    width: 100%;
    background: white;
    border-bottom: 1px solid $linkColour;
}

Also, I change all ordered lists to unordered lists, to avoid the bug that displays the indexing numbers on top of the sticky header. (But this bug still happens with ordered list).

I really liked this thread of you working it all out piece by piece. You should totally write this up in a blog post! 💚

Thanks a lot for your help and suggestion. I will try to write a blog post soon. :-)


Add better meta-layer approach

Instead of returning the second-highest layer as the meta-layer, we can:

explicitly label the meta layer as a label on the container config
explicitly label the UKI as a label on the container config (probably by its fs-verity digest)
have some kind of a nicer install-kernel command or so that defaults to unpacking in /boot.  We could use that during the OS image build, but it would also allow for easier "upgrades" on running systems.

The issue with just putting it in the filesystem is the circular hash dependency thing.  It needs to be out of band, either in an artifact or hidden layer.  That's the thing that needs to be identified.
In the hidden layer, I was actually imagining something like following the bootloader spec.
I started to lean against the idea of hardcoding UKI and having a verity digest for that one file.  Following BLS actually gives us the ability to also do this without a UKI, which seems like something that someone might like to do.

In what I'm thinking here, we do:

build rootfs (without /usr/lib/modules/$kver/uki.efi), get its fsverity digest, embed in uki
Add a new layer with that UKI
compute the standard fsverity digest (i.e. the non-bootable generic container one), add as label to the config as usual

When we boot it'd be into the rootfs without the uki, but it'd be in that regular place when we're run as a container image.
What I don't think we've talked about though is whether and how we want to try to create a chain that allows us to establish trust in the manifest/config starting from the rootfs. I think in the longer term we do need to do that in order to have things like bootc status as well as general bootc upgrade doing change detection (i.e. no-op upgrades if we're on a matching manifest digest already). We could start by saying that's just local unsigned state, but I think we can do it with something like https://github.com/containers/composefs/issues/294#issuecomment-2299142448

That means that it's going to be the "wrong" fs-verity compared to the one that we actually want to mount.

Yes for sure, we'd want a special annotation on the final kernel layer, so that tooling knows to extract and also make a composefs for everything before that layer as well.
I don't see this as weird at all - remember in a general image derivation case we'll often have around a composefs for layers 0..N for a base image and another for layers 0..(N+1) for a final derived image.

The "hidden metadata layer" approach is a massively gigantic hack

Can you write out a bit more what this is? There's not many comments in the code and it's not immediately obvious to me how it works in the code right now.

OK, right I think I remember you describing this "add then whiteout". I need to think harder about the security properties of this versus my proposal of "just add a layer".
First, do you agree that "bootable verified OCI" should just be a special case of "verified OCI" for apps or other use cases? If so, then in the "add then whiteout" we would have a situation where the config digest == UKI digest right?
But when we have the manifest layer annotations as I think we should, then we automatically will have a verifiable digest covering the "meta-layer" as you call it (the non-whiteout one) and given the config we can then find a verity digest of the UKI to install it.
But in the end what's the advantage of having "config digest == UKI digest"? We can equally well access the UKI in a "just add a layer" approach - here config digest != UKI digest, but I don't see a problem with that; from the system again given a verified config, finding the UKI is just traversing into its standard place in /usr/lib/modules instead of finding the meta-layer.
So they seem equivalent from a security PoV. From an elegance/understandable PoV, wouldn't you agree it's just nicer to have e.g. podman|docker run <image> let you see the UKI?


Add prefix/suffix match to HeaderMatcher

Title: Support prefix/suffix match in HeaderMatcher
Description:
The current HeaderMatcher doesn't support prefix/suffix match. Even though it supports regex match, a dedicated prefix/suffix match still have better performance and much easier to use.

@liminw @rodaine
I think the change is small and safe, will send the PR for review once it's ready. Thanks!


fix path/lib and update rust to current version in appveyor.yml

Should have been right in the first pull request but was not...

thanks! :)


helm install error

helm install ckan-p keitaro-charts/ckan
Error: INSTALLATION FAILED: YAML parse error on ckan/templates/deployment.yaml: error converting YAML to JSON: yaml: line 10: did not find expected key
any workaround?

This issue will be fixed soon.

thanks.

Hi @Filip3mac I am having the same issue working with AKS (Azure) 1.24. Is there any release date with the fix?
Thanks!

Hi. I was trying to install the helm release on AKS 1.23.5 and got the same issue, would be nice if you provided the fix :)

Hey guys so we are wating on datapusher+ to make a new release where it would bit its on extension until then try using this branch but you might need to edit out the datapusher+ stuff that is added.

Hi @Filip3mac , thanks for the approach. Working with the datapusher+ I get some errors creating the container related acces to the image repository:
t3-docker.pkg.dev/amplus-data/common/ckan-datapusher-plus:v0.10.1": failed to authorize: failed to fetch anonymous token: unexpected status: 403 Forbidden
failed to resolve reference "europe-west3-docker.pkg.dev/amplus-data/common/ckan-solar:v0.10.1": failed to authorize: failed to fetch anonymous token: unexpected status: 403 Forbidden

@miguelangelch @danseo-reisys @bartek-rvk  My bad thoose are private images can you check main branch it should be fixed now, we added a enabled feature for ckan labels.

Hi @Filip3mac  thanks, finally I've been able to deploy it. Question... Most of the variables in the production.ini (config file) are defined to pass to the docker container in the values.yaml (plugins, title, siteurl, etc.). However, I would like to add more variables based on my plugins added.
Is there any functionality or way in the helm chart for this case?

@miguelangelch https://github.com/keitaroinc/ckan-helm/issues/71


ci: script to read from components.toml when building channels

Reopened from #186
Closes https://github.com/FuelLabs/fuelup/issues/191
Followup to https://github.com/FuelLabs/fuelup/pull/181
We have append_package_to_channel.sh which we use to create channels, but this gets harder to maintain and adapt as we add more components to distribute.
The same components.toml used in https://github.com/FuelLabs/fuelup/pull/181 should be used to read publishable components, and publish them within our channels (latest/nightly) in the CI. Then the original shell script can be deprecated.
This is better because:

components.toml is declarative in nature - this means that once this PR is in, if we want to support/deprecate a component, we just need to edit that TOML file.
component.rs has been extracted as a lib which means we can leverage its abstractions to create a channel toml in more reliable and testable manner.

This should be good to go for reviews - the use case primarily is centred around usage for the CI.
I manually ran the the nightly publish CI once here: https://github.com/FuelLabs/fuelup/actions/runs/3132165597 and the resulting channel was here (has since been replaced by the actual nightly though): https://github.com/FuelLabs/fuelup/blob/88bb91b8df94cd6ca9e5c9de072559071dab19c6/channel-fuel-nightly.toml


Create tests for src/drone-charging/MissionParams.ts using Jest

first-timers-only
This issue is tagged :octocat: first-timers-only. It is only for people who have never contributed to open source before, and are looking for an easy way take their first steps.
Consider this your chance to dip your toe into the world of open-source, and get some bragging rights for writing code that makes drones fly, lets cars find charging stations, helps people and goods get from place to place, and more.
Find more first-timers-only issues from DAV Foundation here.
Thank you for your help :heart:
What is this project?
DAV (Decentralized Autonomous Vehicles) is a new foundation working to build an open-source infrastructure for autonomous vehicles (cars, drones, trucks, robots, and all the service providers around them) to communicate and transact with each other over blockchain.
As an organization that believes in building a large community of open-source contributors, we often create issues like this one to help people take their first few steps into the world of open source.
dav-js
This repo contains the DAV JavaScript SDK. This SDK allows developers to build applications and servers that connect to the DAV network. For example, allowing a drone to find charging stations, or an autonomous car to ask for traffic data.
How you can help
In order to foster a community that is welcoming for open source contributions, it is important for us to have good test coverage. And good tests are simple, readable tests.
Here is a good opportunity to simplify one of our tests.
The Issue
We currently do not have unit testing set up for src/drone-charging/MissionParams.ts. Please create Jest tests for the serialize() and deserialize() methods.
A good reference point would be src/ride-hailing/MissionParams.test.ts and customize it to the expected parameters and properties. If you are unsure what is expected, run npm run jest in the terminal and it should give you a hint.  Also, you can reach out to our gitter channel with any questions 😄
The test you write will be similar to this:
import MissionParams from './MissionParams';

describe('MissionParams class', () => {
  let missionParams: MissionParams;
  let serializedMissionParams: any;

  beforeEach(() => {
    missionParams = new MissionParams({
      id: 'TOPIC_ID',
      neederDavId: 'CONSUMER_DAV_ID',
      price: ['66666666'],
      vehicleId: 'VEHICLE_DAV_ID'
    });

    serializedMissionParams = {
      id: 'TOPIC_ID',
      neederDavId: 'CONSUMER_DAV_ID',
      price: ['66666666'],
      protocol: 'drone_charging',
      type: 'mission',
      vehicleId: 'VEHICLE_DAV_ID'
    };
  });

  describe('serialize method', () => {
    it('should return serialized MissionParams object with the current values', () => {
      expect(missionParams.serialize()).toEqual(serializedMissionParams);
    });
  });

  describe('deserialize method', () => {
    it('should return a MissionParams instance', () => {
      const missionParamsObject = new MissionParams();
      missionParamsObject.deserialize(serializedMissionParams);
      expect(missionParamsObject).toBeInstanceOf(MissionParams);
    });

    it('should return deserialize MissionParams instance with the current parameters', () => {
      const missionParamsObject = new MissionParams();
      missionParamsObject.deserialize(serializedMissionParams);
      expect(missionParamsObject).toEqual(missionParams);
    });
  });
});

After making your changes, run npm run tslint and npm run jest to make sure our tests are passing.
Contributing to dav-js

[ ] Make sure this issue is labeled up-for-grabs and not labeled claimed, to verify no one else is working on it.
[ ] Comment in this issue that you would like to do it.
[ ] Open dav-js GitHub page and click the ★ Star and then ⑂ Fork buttons.
[ ] Clone a copy to your local machine with $ git clone git@github.com:YOUR-GITHUB-USER-NAME/dav-js.git
[ ] Install dependencies by running npm install
[ ] Code Code Code
[ ] Once you've made sure all your changes work correctly and committed all your changes, push your local changes back to github with $ git push -u origin master
[ ] Visit your fork on GitHub.com (https://github.com/YOUR-USER-NAME/dav-js) and create a pull request for your changes.
[ ] Make sure your pull request describes exactly what you changed and references this issue (include the issue number in the title like this: #7)
[ ] Please do not fix more than one issue at a time. Your pull request should only fix what is described in this issue.

Asking for help
We appreciate your effort in taking the time to work on this issue and help out the open source community and the foundation. If you need any help, feel free to ask below or in our gitter channel. We are always happy to help 😄

I'll get this one!

Hi, I would like to make my first open source contribution and noticed that this issue is still labeled up-for-grabs. Can I work on it?

Hi @hackora thanks for picking this as your first contribution. Yes, you may work on this. 👍

Thanks for the good work @hackora 👍 Please check back often if you have the time 😃

@mariolo1985 It's been a pleasure :smiley: Thank you for being so welcoming to new contributors.  I will definetly check back whenever I can :+1:


Mojibake problem: Ã…

Hi,
U+00C3  Ã       [Lu] LATIN CAPITAL LETTER A WITH TILDE
U+2026  …       [Po] HORIZONTAL ELLIPSIS
SHOULD BE:
U+00C5  Å       [Lu] LATIN CAPITAL LETTER A WITH RING ABOVE

Example:

of IKEA TRÃ…DFRI

Is it possible to fix this?

The evidence is there, but it's not enough, because this looks almost like a reasonable string.
There were several examples of false positives that involved all-caps and ellipses (where it really was an all-caps string that got shortened, and the fix was wrong).


mixer: reconcile nondet bug fix between 1.0 and 1.1

Copies the test from 1.0 to 1.1 fix, and adds buffer leak fix.
/assign @geeknoid
Signed-off-by: Kuat Yessenov<EMAIL_ADDRESS>

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: kyessenov
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

mixer/OWNERS [kyessenov]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kyessenov: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
1d4052ac73373355f2b6f84a4c4d5587cf6f1f0e
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-mixer-no_auth-mcp.sh
1d4052ac73373355f2b6f84a4c4d5587cf6f1f0e
link
/test e2e-mixer-no_auth-mcp

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test istio-pilot-e2e-envoyv2-v1alpha3


Can not open the link for pretrained encoders

Dear authors,
Thank you for sharing your code with us.
I would like to use the "pretrained encoder" in the provided link in README.md, but I found the link is inaccessible (404 Error). Is it possible for you to update the link?
Thank you!

I have the same question,have you solve it?


Add tls option for sync and etcd plugin

add tls option for sync and etcd plugin

Please remove your vendor dir and reopen a pull request