Get PlayReady PSSH from mspr:pro in DASH

Fix for https://github.com/google/shaka-player/issues/2058

The code doesn't work yet.

@TheModMaker I followed your comment https://github.com/google/shaka-player/issues/2058#issuecomment-522645561, but the error persists.. Can you help me?

@TheModMaker , I made all the changes, and now it works (I'll send you a stream to test it)

@TheModMaker , I fixed all issues and added some tests.

@TheModMaker I updated the PR with your last comments


TCA: An Efficient Two-Mode Meta-Heuristic Algorithm for Combinatorial Test Generation (T)

http://ieeexplore.ieee.org/xpl/articleDetails.jsp?arnumber=7372037&punumber%3D7371449%26filter%3DAND(p_IS_Number%3A7371976)%26pageNumber%3D3

No Data Found.
Tools available at : https://github.com/leiatpku/TCA


Listen to contract metrics via supabase

What's the status of this PR? Wasn't this blocking @mqp?

This is actually just way more complicated than I thought it would be -- I don't entirely understand this version yet, never mind how it should be made. I will have to look at it more tomorrow. If you like it, merge, but I think we will be due for a lot more work on this...

MQP and I had a 1:1 and decided on a few things to do before merging

Given these, why do you need the resubscribe timer? In what case do you want to resubscribe but it's not being handled internally by one of these? Is it if the initial join fails? That seems like you could do it once rather than having a timer though.

The resubscribe timer is needed bc it handles channel connection errors, and is on a timer bc the retry sometimes fails.

Why do we restart the channel? This seems to add an incredible amount of complexity managing the callbacks and I don't understand why we need to do it.

Unfortunately we can only hit subscribe once on a channel. If we want to add new events to subscribe to, we have to recreate the channel.

What is the plan for using this in cases where two different pieces of code are subscribing to an overlapping collection of stuff? (e.g. two places on the same page that both want the bets feed.) Is that possible for it to handle? It seems that this design will not work right, unless I am mistaken.

This handles that case: the two hooks pass a unique callback invoked based on the same event.

It would seem more React-y to put this all in a React context, rather than have it at the top level of a random Javascript module. I'm not sure if there's any important reason to do that though.

I'm not sure whether this is necessary either, @jahooma do you have an opinion? It'd be for the shared state (manChannel,subscriptionStatus,callbacks,mainChannelResubscribeInterval) at the top of use-subscription.ts

Just sent supabase the following message:
Hi,
We recently added a small number of realtime channel subscriptions to our app and are planning on adding them in more places. During testing I've been hitting the error: too_many_connections. Based on this I have a few questions:

Is the error I'm seeing related to the 500 max concurrent channels cap?
What is the purpose of the 500 max concurrent channels?  Is this a technical limitation or just a safety rail?
Can you raise our concurrent channel cap?
What is the pricing rate for higher concurrent channel caps?

Open question: how do we select the most up to date object if we don't use the firestore-dependent fs_updated_time?

You could use React Context if you are trying to cache the data so that multiple hooks don't refetch. Or, you could just use a usePersistentInMemoryState — which is probably what I'd prefer.
That seems like a future upgrade to this hook since it's not 100% necessary yet. (You would have to store the data by unique table and filter).

Open question: how do we select the most up to date object if we don't use the firestore-dependent fs_updated_time?

I don't see why we need this at all. In the realtime subscription, doesn't it give you the newer value? You then know that it is newer. If you want to know if it changed, then do a deep equality comparison with the old value, e.g. isEqual from lodash.

Open question: how do we select the most up to date object if we don't use the firestore-dependent fs_updated_time?

I don't see why we need this at all. In the realtime subscription, doesn't it give you the newer value? You then know that it is newer. If you want to know if it changed, then do a deep equality comparison with the old value, e.g. isEqual from lodash.

This is in reference to the state where you've subscribed, triggered fetching the initial state, gotten an update via subscription, then finished fetching the initial state.

This is in reference to the state where you've subscribed, triggered fetching the initial state, gotten an update via subscription, then finished fetching the initial state.

Minor race condition that mostly doesn't matter? You could also wait to start the subscription until after the initial state is loaded, as one solution.

I'm also skeptical about how this creates and restart channels. I've seen channels reconnect automatically. We've used them for the live feed and other cases and it hasn't been a problem just creating them once.

I'm also skeptical about how this creates and restart channels. I've seen channels reconnect automatically. We've used them for the live feed and other cases and it hasn't been a problem just creating them once.

I've tested this and if the client hits a channel_error you aren't resubscribed. Are you sure you've tested that case? Channels reconnect automatically if your wifi is toggled on/off, but not if there's a connection error.

I'm also skeptical about how this creates and restart channels. I've seen channels reconnect automatically. We've used them for the live feed and other cases and it hasn't been a problem just creating them once.

So, just checking up on this:
channel.subscribe(async (status) => {})
is the subscription code used throughout main, so it seems no one has actually tested an error on channel subscription.
  channel.subscribe(async (status, err) => {       console.log('channel subscribe status', status, err) // ... })
This is how it is written in this PR

So I just added the subscription status and error checking on main into the useRealtimeBets hook and after a couple refreshes I got a channel error that the subscription did not resubscribe to.

I see, interesting! Thanks for finding this error. 500 channels seems extremely limited.
Did supabase get back to you yet?

No response yet

BTW, after thinking about it for a bit I think we should just keep around an updated timestamp on all the DB tables we subscribe to -- it's easy to implement (you can just have it be a generated column in SQL) and then it means we can confidently order our updates without fear of the spooky race conditions Ian has mentioned. I basically see no downside.

Going to close this as mqp made his own pr for the same thing!


Slight updates to the layout

Proposed changes

Add break between upcoming and past
Sort the upcoming workshops with the nearest coming up on top #12

Hello @JaroCamphuijsen . This has been fixed by Lieke, see issue #12


Azure AD Auth : Error not found in cache

Issue Type: Bug
Trying to add a credential to connect to Azure SQL DB, triggers the Azure Data Studio link and code to authenticate in browser, and then throws the above error.
Azure Data Studio version: azuredatastudio-insiders 1.11.0-insider (b8518f5795ce15a5a524cbc0f9e531b8e02d8456, 2019-09-04T09:15:54.332Z)
OS version: Windows_NT x64 10.0.18362

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-6600U CPU @ 2.60GHz (4 x 2808)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwareoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_deferred_display_list: disabled_offskia_renderer: disabled_offsurface_synchronization: enabled_onvideo_decode: enabledviz_display_compositor: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.93GB (7.55GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions: none

Similar issue on Mac OSX: 10.14.6
Login Type: Microsoft MFA

seems to be similar to #7619 .

Closing as a duplicate of https://github.com/microsoft/azuredatastudio/issues/7619.  We're looking into this area for Dec release.  Please leave any additional related comments on https://github.com/microsoft/azuredatastudio/issues/7619.  Thanks!


[BUG] Unable to view any Profiles, "Twitter says the page does not exist, but that may not be true"

Describe the bug
When trying to view any profile, Fritter does not display any tweets and instead says "Twitter says the page does not exist, but that may not be true".
To Reproduce
Steps to reproduce the behavior:

Allow Fritter to open "twitter.com" links.
In a browser, Google any twitter profile and click on the link, which will redirect to Fritter.
Note the error.

Screenshots

(I do have a VPN on in the screenshot, but this error still occurs with the VPN off.)
Device
Pixel 6a, Android 13, English, Fritter 3.0.0-beta9

Closing as a duplicate of #756 (guess we were writing it at the same time :) )


Pong glitches after about 1 second

I got to the finished desktop build part, and space invaders for example runs fine. But when I try pong it completely glitches out without doing anything. Any fix?


App Center Build option for Unity Apps

Describe the solution you'd like
Add a build pipeline for Unity-based applications to App Center Build.
Describe alternatives you've considered
Will consider Azure DevOps pipelines to create a custom build pipeline supporting our application, but a simplified App Center Build option might be nice.
Currently use Jenkins, running an ant build script, which in turn executes Unity with commandline arguments invoking a custom build pipeline in the editor.

Very much on the radar of something we would like to do. We are currently investigating what options exist. No promises yet.

Any movement on this?

Also following up, any movement on this guy? :)

We could really use this too! Awesome to know that it's on the radar!!

Is it fair to say this is being abandoned?

Yes, thank you
On Sun, Jul 4, 2021 at 10:39 douglassophies @.***>
wrote:

Is it fair to say this is being abandoned?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/appcenter/issues/554#issuecomment-873631446,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AALIT67GISWXP6DL4WHUAG3TWCMG3ANCNFSM4HXLSILA
.

--
Roger Miller | Collective Mass |<PHONE_NUMBER>


Theme bug in RSS-Feed's browse feeds option torrents display.

Describe the bug
Theme bug in RSS-Feed's browse feeds option torrents display.
To Reproduce
Steps to reproduce the behavior:

Go to homepage and click add rss feed button on top right.
Add a rss-feed and select that feed label under the browse feeds option.
See the list displaying torrents have its borders as nearly invisible in the light mode of the app.

Expected behavior
Borders should be visible in light mode as well.
Screenshots

 Dark-Mode(RSS-Feed)
Light-Mode(RSS-Feed with theme bug)

Can you assign this issue to me I want work on it.

Can you please assign this issue to me, I want work on it.


Add support for emit direct

My experimentation with Trident required this, so adding it. Verified in an example trident topology.

Nothing's been decided about Trident at this point. This was the main feature that was blocking it, and after discussions with @mfu we realized it was easy to implement so I added it. There's a not a lot to supporting direct grouping, since it's very similar to custom grouping, so now that it's been developed we might as well add it IMO, regardless of Trident.

👍


Date Range Picker

Implement the Date Range Picker component.

How is this different from Date Picker https://github.com/onfido/castor/issues/73?

Material has a good example. https://material.io/components/date-pickers#desktop-pickers
Date Picker

Date Range Picker


New package: DaggerGPU v0.1.0

Registering package: DaggerGPU
Repository: https://github.com/jpsamaroo/DaggerGPU.jl
Created by: @jpsamaroo
Version: v0.1.0
Commit: b1ca6d9e3316636953af436dcea711b6e36a7312
Reviewed by: @jpsamaroo
Reference: https://github.com/jpsamaroo/DaggerGPU.jl/commit/b1ca6d9e3316636953af436dcea711b6e36a7312#commitcomment-38325349

Is the name "DaggerGPU" ok? I feel that it's pretty self-explanatory without being verbose.

Seems fine to me.
[noblock]


Add server tests

This pull request introduces 2 alerts when merging 9fc3553076f2ca542b08e9047ca8f1a210e91b59 into f1091b1bf58823caaa793fbf6413b0a1f13058ba - view on LGTM.com
new alerts:

2 for Useless conditional

Comment posted by LGTM.com


New ICRC1 Textual Representation

The textual representation for ICRC transfers implemented in #190 has become obsolete.
We need to support the new textual representation.

Textual encoding standard
Typescript implementation

:link: zboto Link

Closing this issue. This was solved in #209 already.


Logging twice when importing winerp with discord.py

import discord
import winerp

class MyClient(discord.Client):
    async def on_message(self, message):
        if message.content == 'raise error':
            raise Exception('test2')

intents = discord.Intents.all()
intents.typing = False
client = MyClient(intents = intents)

client.run(TOKEN)

This simple code, when using the raise error command, logs the exception twice, but the exact same code, without the second line import winerp logs only once. (note that winerp is not used at all here, only imported).
Tried and reproduced on windows and debian, with python 3.9 to 3.11

did you install winerp using pypi or git?

Pypi, and I'm up to date

I have identified the issue. Seems like the dependent module websockets_server uses basicConfig which also enables the logging for discord.py
https://github.com/Pithikos/python-websocket-server/issues/85


Remove memref type from ONNX Ops

In concept, ONNX Ops are defined on Tensor type and MemRef type is introduced when ONNX Ops are lowered to krnl dialect. However, in the process of lowering, some ONNX Ops are generated with the intermediate lowering result, which has the MemRef type. The previous solution is to allow AnyMemRef into the ONNX Op definition. This solution mixed the concept and implementation of ONNX Ops. We have to handle memref type in transformation of ONNX Ops.
This PR uses UnrealizedConversionCastOp to cast the memref back to tensor when an ONNX Op is created in lowering. The conversion is added into the builder utilities to avoid massive code changing.  As a result of this PR, the memref type is removed from ONNX Op definition.
Changes include:

gen_onnx_mlir.py: remove memref
Add the type conversion in builders: onnx/DialectBuilder and ONNXToKrnlCommon.cpp.
Modify lit test.

Issues

The tensor type is simply inferred from memref in the current implementation, not from the original tensor type. This approach works only for our current implementation. For more generic solution, our builder has to be changed to include original type and type converter  for conversion.
Manually defined ONNX Op has not been updated

Future work

Clearly define the interface of builder at different stage. For example, onnx builder always converts all input to tensor type, while memref builder always convert input to memref.
Integrate the builder with conversion. Use the  type converter, or addSourceMaterialization and addTargetMaterialization hook.

Jenkins Linux ppc64le Build #5511 [push] Remove memref type from ... started at 19:46

Jenkins Linux amd64 Build #6373 [push] Remove memref type from ... started at 18:44

Jenkins Linux s390x Build #6389 [push] Remove memref type from ... started at 19:44

Jenkins Linux amd64 Build #6373 [push] Remove memref type from ... passed after 1 hr 16 min

Jenkins Linux s390x Build #6389 [push] Remove memref type from ... passed after 1 hr 29 min


[BACKLOG-25015] Meta-inject - Move step to Kettle plugin system

Converted ETL metadata injection plugin from being an OSGi bundle, to the "classic" form of PDI plugins

Fixed failing UTs + ITs: you can try them out with mvn clean package -DrunITs

Plugin's structure is broken down as per the X-wing team's guidelines

/meta-inject
     /assemblies
     /impl
     /ui

Also separated "core" from "UI" code: org.pentaho.di.ui package has been moved to /ui module, as well as adjusting which dependencies are needed at each module
MetaInjectDialog is now leveraging on the new @PluginDialog annotation
Added ETL metadata injection to PDI plugin's assembly, meaning it will be bundled with the plugin list at data-integration/plugins

You can keep track of the test rails cases being used to test out this de-OSGifing work at https://jira.pentaho.com/browse/BACKLOG-25015?focusedCommentId=348799#comment-348799
To be merged alongside https://github.com/pentaho/pentaho-karaf-assembly/pull/472

Build Completed
:x: This pull request has errors. They will need to be addressed before it can be accepted. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
mvn -B -f 'pom.xml' -pl 'plugins/meta-inject' -P '!assemblies' -Dsurefire.runOrder=alphabetical -Daudit -amd clean install

Cleanup Commands
mvn -B -f 'pom.xml' -pl 'plugins/meta-inject' -P '!assemblies' -amd build-helper:remove-project-artifact

Changed files
  assemblies/plugins/pom.xml
  plugins/meta-inject/assemblies/plugin/pom.xml
  plugins/meta-inject/assemblies/plugin/src/assembly/assembly.xml
  plugins/meta-inject/assemblies/plugin/src/main/resources/version.xml
  plugins/meta-inject/assemblies/pom.xml
  plugins/meta-inject/impl/pom.xml
  plugins/meta-inject/impl/src/it/java/org/pentaho/di/trans/steps/denormaliser/DenormaliserMetaInjectionIT.java
  plugins/meta-inject/impl/src/it/java/org/pentaho/di/trans/steps/metainject/MetaInjectTemplateInFSAndRepoSpecMethodIT.java
  plugins/meta-inject/impl/src/it/java/org/pentaho/di/trans/steps/normaliser/NormaliserMetaInjectionIT.java
  plugins/meta-inject/impl/src/it/resources/org/pentaho/di/trans/steps/denormaliser/child.ktr
  plugins/meta-inject/impl/src/it/resources/org/pentaho/di/trans/steps/denormaliser/child2.ktr
  plugins/meta-inject/impl/src/it/resources/org/pentaho/di/trans/steps/denormaliser/pdi-11947.ktr
  plugins/meta-inject/impl/src/it/resources/org/pentaho/di/trans/steps/metainject/pdi-16420-template.ktr
  plugins/meta-inject/impl/src/it/resources/org/pentaho/di/trans/steps/metainject/pdi-16420.ktr
  plugins/meta-inject/impl/src/it/resources/org/pentaho/di/trans/steps/normaliser/injected-trans-pdi-13761.ktr
  plugins/meta-inject/impl/src/it/resources/org/pentaho/di/trans/steps/normaliser/injecting-trans-pdi-13761-does-not-inject-field.ktr
  plugins/meta-inject/impl/src/it/resources/org/pentaho/di/trans/steps/normaliser/injecting-trans-pdi-13761.ktr
  plugins/meta-inject/impl/src/it/resources/org/pentaho/di/trans/steps/normaliser/normaliser-13761-expected-output.txt
  plugins/meta-inject/impl/src/main/java/org/pentaho/di/trans/steps/metainject/MetaInject.java
  plugins/meta-inject/impl/src/main/java/org/pentaho/di/trans/steps/metainject/MetaInjectData.java
  plugins/meta-inject/impl/src/main/java/org/pentaho/di/trans/steps/metainject/MetaInjectMapping.java
  plugins/meta-inject/impl/src/main/java/org/pentaho/di/trans/steps/metainject/MetaInjectMeta.java
  plugins/meta-inject/impl/src/main/java/org/pentaho/di/trans/steps/metainject/MetaInjectMigration.java
  plugins/meta-inject/impl/src/main/java/org/pentaho/di/trans/steps/metainject/MetaInjectOutputField.java
  plugins/meta-inject/impl/src/main/java/org/pentaho/di/trans/steps/metainject/OpenMappingExtension.java
  plugins/meta-inject/impl/src/main/java/org/pentaho/di/trans/steps/metainject/RepositoryExporterExtension.java
  plugins/meta-inject/impl/src/main/java/org/pentaho/di/trans/steps/metainject/RepositoryImporterExtension.java
  plugins/meta-inject/impl/src/main/java/org/pentaho/di/trans/steps/metainject/SourceStepField.java
  plugins/meta-inject/impl/src/main/java/org/pentaho/di/trans/steps/metainject/TargetStepAttribute.java
  plugins/meta-inject/impl/src/main/resources-filtered/version.properties
  plugins/meta-inject/impl/src/main/resources/org/pentaho/di/trans/steps/metainject/messages/messages_en_US.properties
  plugins/meta-inject/impl/src/main/resources/org/pentaho/di/trans/steps/metainject/messages/messages_fr_FR.properties
  plugins/meta-inject/impl/src/main/resources/org/pentaho/di/trans/steps/metainject/messages/messages_it_IT.properties
  plugins/meta-inject/impl/src/main/resources/org/pentaho/di/trans/steps/metainject/messages/messages_ja_JP.properties
  plugins/meta-inject/impl/src/main/resources/org/pentaho/di/trans/steps/metainject/messages/messages_ko_KR.properties
  plugins/meta-inject/impl/src/main/resources/org/pentaho/di/trans/steps/metainject/messages/messages_zh_CN.properties
  plugins/meta-inject/impl/src/main/resources/org/pentaho/di/ui/trans/steps/metainject/img/GenericTransform.png
  plugins/meta-inject/impl/src/main/resources/org/pentaho/di/ui/trans/steps/metainject/img/GenericTransform.svg
  plugins/meta-inject/impl/src/test/java/org/pentaho/di/repository/RepositoryImporterTest.java
  plugins/meta-inject/impl/src/test/java/org/pentaho/di/trans/TransMetaTest.java
  plugins/meta-inject/impl/src/test/java/org/pentaho/di/trans/steps/metainject/MetaInjectMetaInjectionTest.java
  plugins/meta-inject/impl/src/test/java/org/pentaho/di/trans/steps/metainject/MetaInjectMetaLoadSaveTest.java
  plugins/meta-inject/impl/src/test/java/org/pentaho/di/trans/steps/metainject/MetaInjectMetaTest.java
  plugins/meta-inject/impl/src/test/java/org/pentaho/di/trans/steps/metainject/MetaInjectMigrationTest.java
  plugins/meta-inject/impl/src/test/java/org/pentaho/di/trans/steps/metainject/MetaInjectTest.java
  plugins/meta-inject/impl/src/test/java/org/pentaho/di/trans/steps/metainject/OpenMappingExtensionTest.java
  plugins/meta-inject/pom.xml
  plugins/meta-inject/src/main/resources/OSGI-INF/blueprint/pentaho-metainject-pdi-blueprint.xml
  plugins/meta-inject/ui/pom.xml
  plugins/meta-inject/ui/src/main/java/org/pentaho/di/ui/trans/steps/metainject/MetaInjectDialog.java
  plugins/meta-inject/ui/src/main/resources/org/pentaho/di/ui/trans/steps/metainject/img/GenericTransform.png
  plugins/meta-inject/ui/src/main/resources/org/pentaho/di/ui/trans/steps/metainject/img/GenericTransform.svg

Unit Test Coverage
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.

:warning: Coverage Changes: +12.7% (click to expand)
:new: org.pentaho.di.trans.steps.metainject.MetaInject

Coverage: 0% :exclamation:

:new: org.pentaho.di.trans.steps.metainject.MetaInjectData

Coverage: 0% :exclamation:

:new: org.pentaho.di.trans.steps.metainject.MetaInjectMeta

Branch Coverage: 42.2% :exclamation:
Complexity Coverage: 44% :exclamation:
Instruction Coverage: 58.8% :exclamation:
Line Coverage: 65.1% :exclamation:
Method Coverage: 65.6% :exclamation:

:new: org.pentaho.di.trans.steps.metainject.MetaInjectMigration

Branch Coverage: 75% :exclamation:
Complexity Coverage: 50% :exclamation:
Method Coverage: 50% :exclamation:

:new: org.pentaho.di.trans.steps.metainject.OpenMappingExtension

Branch Coverage: 50% :exclamation:
Complexity Coverage: 60% :exclamation:

:new: org.pentaho.di.trans.steps.metainject.RepositoryExporterExtension

Coverage: 0% :exclamation:

:new: org.pentaho.di.trans.steps.metainject.RepositoryImporterExtension

Branch Coverage: 13.6% :exclamation:
Complexity Coverage: 13.3% :exclamation:
Instruction Coverage: 33.1% :exclamation:
Line Coverage: 40% :exclamation:
Method Coverage: 50% :exclamation:

:new: org.pentaho.di.trans.steps.metainject.SourceStepField

Branch Coverage: 25% :exclamation:
Complexity Coverage: 45.5% :exclamation:
Instruction Coverage: 45% :exclamation:
Line Coverage: 64.7% :exclamation:
Method Coverage: 71.4% :exclamation:

:new: org.pentaho.di.trans.steps.metainject.TargetStepAttribute

Branch Coverage: 0% :exclamation:
Complexity Coverage: 38.5% :exclamation:
Instruction Coverage: 41.4% :exclamation:
Line Coverage: 42.9% :exclamation:
Method Coverage: 55.6% :exclamation:

License header violations

:heavy_exclamation_mark: Copyright year is not the current year on plugins/meta-inject/impl/src/it/java/org/pentaho/di/trans/steps/denormaliser/DenormaliserMetaInjectionIT.java. Found 2017. Was expecting 2018

:heavy_exclamation_mark: Copyright year is not the current year on plugins/meta-inject/impl/src/it/java/org/pentaho/di/trans/steps/metainject/MetaInjectTemplateInFSAndRepoSpecMethodIT.java. Found 2017. Was expecting 2018

:heavy_exclamation_mark: Copyright year is not the current year on plugins/meta-inject/impl/src/it/java/org/pentaho/di/trans/steps/normaliser/NormaliserMetaInjectionIT.java. Found 2017. Was expecting 2018

:heavy_exclamation_mark: Copyright year is not the current year on plugins/meta-inject/impl/src/main/java/org/pentaho/di/trans/steps/metainject/MetaInject.java. Found 2017. Was expecting 2018

:heavy_exclamation_mark: Copyright year is not the current year on plugins/meta-inject/impl/src/main/java/org/pentaho/di/trans/steps/metainject/MetaInjectData.java. Found 2017. Was expecting 2018

:heavy_exclamation_mark: Copyright year is not the current year on plugins/meta-inject/impl/src/main/java/org/pentaho/di/trans/steps/metainject/MetaInjectMapping.java. Found 2017. Was expecting 2018

:heavy_exclamation_mark: Copyright year is not the current year on plugins/meta-inject/impl/src/main/java/org/pentaho/di/trans/steps/metainject/MetaInjectMigration.java. Found 2017. Was expecting 2018

:heavy_exclamation_mark: Copyright year is not the current year on plugins/meta-inject/impl/src/main/java/org/pentaho/di/trans/steps/metainject/MetaInjectOutputField.java. Found 2017. Was expecting 2018

:heavy_exclamation_mark: Copyright year is not the current year on plugins/meta-inject/impl/src/main/java/org/pentaho/di/trans/steps/metainject/OpenMappingExtension.java. Found 2017. Was expecting 2018

:heavy_exclamation_mark: Copyright year is not the current year on plugins/meta-inject/impl/src/main/java/org/pentaho/di/trans/steps/metainject/RepositoryExporterExtension.java. Found 2017. Was expecting 2018

:heavy_exclamation_mark: Copyright year is not the current year on plugins/meta-inject/impl/src/main/java/org/pentaho/di/trans/steps/metainject/RepositoryImporterExtension.java. Found 2017. Was expecting 2018

:heavy_exclamation_mark: Copyright year is not the current year on plugins/meta-inject/impl/src/main/java/org/pentaho/di/trans/steps/metainject/SourceStepField.java. Found 2017. Was expecting 2018

:heavy_exclamation_mark: Copyright year is not the current year on plugins/meta-inject/impl/src/main/java/org/pentaho/di/trans/steps/metainject/TargetStepAttribute.java. Found 2017. Was expecting 2018

:heavy_exclamation_mark: Copyright year is not the current year on plugins/meta-inject/impl/src/test/java/org/pentaho/di/repository/RepositoryImporterTest.java. Found 2017. Was expecting 2018

:heavy_exclamation_mark: Copyright year is not the current year on plugins/meta-inject/impl/src/test/java/org/pentaho/di/trans/TransMetaTest.java. Found 2017. Was expecting 2018

:heavy_exclamation_mark: Copyright year is not the current year on plugins/meta-inject/impl/src/test/java/org/pentaho/di/trans/steps/metainject/MetaInjectMetaInjectionTest.java. Found 2017. Was expecting 2018

:heavy_exclamation_mark: Copyright year is not the current year on plugins/meta-inject/impl/src/test/java/org/pentaho/di/trans/steps/metainject/MetaInjectMetaLoadSaveTest.java. Found 2017. Was expecting 2018

:heavy_exclamation_mark: Copyright year is not the current year on plugins/meta-inject/impl/src/test/java/org/pentaho/di/trans/steps/metainject/MetaInjectMetaTest.java. Found 2017. Was expecting 2018

:heavy_exclamation_mark: Copyright year is not the current year on plugins/meta-inject/impl/src/test/java/org/pentaho/di/trans/steps/metainject/MetaInjectMigrationTest.java. Found 2017. Was expecting 2018

:heavy_exclamation_mark: Copyright year is not the current year on plugins/meta-inject/impl/src/test/java/org/pentaho/di/trans/steps/metainject/MetaInjectTest.java. Found 2017. Was expecting 2018

:heavy_exclamation_mark: Copyright year is not the current year on plugins/meta-inject/impl/src/test/java/org/pentaho/di/trans/steps/metainject/OpenMappingExtensionTest.java. Found 2017. Was expecting 2018

Checkstyle violations
The code submitted is not complying with one or more of our guidelines. To perform these checks locally, please use this tool.
/home/buildguy/project/plugins/meta-inject/impl/src/main/java/org/pentaho/di/trans/steps/metainject/RepositoryExporterExtension.java

:heavy_exclamation_mark: Line has trailing spaces at Line: 39

:heavy_exclamation_mark: Line has trailing spaces at Line: 74

/home/buildguy/project/plugins/meta-inject/impl/src/main/java/org/pentaho/di/trans/steps/metainject/RepositoryImporterExtension.java

:heavy_exclamation_mark: Line has trailing spaces at Line: 38

:heavy_exclamation_mark: '}' at column 9 should be on the same line as the next part of a multi-block statement (one that directly contains multiple blocks: if/else-if/else, do/while or try/catch/finally). at Line: 59 Column: 9

:heavy_exclamation_mark: Line has trailing spaces at Line: 65

:heavy_exclamation_mark: Line has trailing spaces at Line: 67

:heavy_exclamation_mark: Line has trailing spaces at Line: 86

Build Completed
:fire: This pull request has some issues. It would be preferable to fix them in order for it to be just perfect. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
mvn -B -f 'pom.xml' -pl 'plugins/meta-inject' -P '!assemblies' -Dsurefire.runOrder=alphabetical -Daudit -amd clean install

Cleanup Commands
mvn -B -f 'pom.xml' -pl 'plugins/meta-inject' -P '!assemblies' -amd build-helper:remove-project-artifact

Changed files
  assemblies/plugins/pom.xml
  plugins/meta-inject/assemblies/plugin/pom.xml
  plugins/meta-inject/assemblies/plugin/src/assembly/assembly.xml
  plugins/meta-inject/assemblies/plugin/src/main/resources/version.xml
  plugins/meta-inject/assemblies/pom.xml
  plugins/meta-inject/impl/pom.xml
  plugins/meta-inject/impl/src/it/java/org/pentaho/di/trans/steps/denormaliser/DenormaliserMetaInjectionIT.java
  plugins/meta-inject/impl/src/it/java/org/pentaho/di/trans/steps/metainject/MetaInjectTemplateInFSAndRepoSpecMethodIT.java
  plugins/meta-inject/impl/src/it/java/org/pentaho/di/trans/steps/normaliser/NormaliserMetaInjectionIT.java
  plugins/meta-inject/impl/src/it/resources/org/pentaho/di/trans/steps/denormaliser/child.ktr
  plugins/meta-inject/impl/src/it/resources/org/pentaho/di/trans/steps/denormaliser/child2.ktr
  plugins/meta-inject/impl/src/it/resources/org/pentaho/di/trans/steps/denormaliser/pdi-11947.ktr
  plugins/meta-inject/impl/src/it/resources/org/pentaho/di/trans/steps/metainject/pdi-16420-template.ktr
  plugins/meta-inject/impl/src/it/resources/org/pentaho/di/trans/steps/metainject/pdi-16420.ktr
  plugins/meta-inject/impl/src/it/resources/org/pentaho/di/trans/steps/normaliser/injected-trans-pdi-13761.ktr
  plugins/meta-inject/impl/src/it/resources/org/pentaho/di/trans/steps/normaliser/injecting-trans-pdi-13761-does-not-inject-field.ktr
  plugins/meta-inject/impl/src/it/resources/org/pentaho/di/trans/steps/normaliser/injecting-trans-pdi-13761.ktr
  plugins/meta-inject/impl/src/it/resources/org/pentaho/di/trans/steps/normaliser/normaliser-13761-expected-output.txt
  plugins/meta-inject/impl/src/main/java/org/pentaho/di/trans/steps/metainject/MetaInject.java
  plugins/meta-inject/impl/src/main/java/org/pentaho/di/trans/steps/metainject/MetaInjectData.java
  plugins/meta-inject/impl/src/main/java/org/pentaho/di/trans/steps/metainject/MetaInjectMapping.java
  plugins/meta-inject/impl/src/main/java/org/pentaho/di/trans/steps/metainject/MetaInjectMeta.java
  plugins/meta-inject/impl/src/main/java/org/pentaho/di/trans/steps/metainject/MetaInjectMigration.java
  plugins/meta-inject/impl/src/main/java/org/pentaho/di/trans/steps/metainject/MetaInjectOutputField.java
  plugins/meta-inject/impl/src/main/java/org/pentaho/di/trans/steps/metainject/OpenMappingExtension.java
  plugins/meta-inject/impl/src/main/java/org/pentaho/di/trans/steps/metainject/RepositoryExporterExtension.java
  plugins/meta-inject/impl/src/main/java/org/pentaho/di/trans/steps/metainject/RepositoryImporterExtension.java
  plugins/meta-inject/impl/src/main/java/org/pentaho/di/trans/steps/metainject/SourceStepField.java
  plugins/meta-inject/impl/src/main/java/org/pentaho/di/trans/steps/metainject/TargetStepAttribute.java
  plugins/meta-inject/impl/src/main/resources-filtered/version.properties
  plugins/meta-inject/impl/src/main/resources/org/pentaho/di/trans/steps/metainject/messages/messages_en_US.properties
  plugins/meta-inject/impl/src/main/resources/org/pentaho/di/trans/steps/metainject/messages/messages_fr_FR.properties
  plugins/meta-inject/impl/src/main/resources/org/pentaho/di/trans/steps/metainject/messages/messages_it_IT.properties
  plugins/meta-inject/impl/src/main/resources/org/pentaho/di/trans/steps/metainject/messages/messages_ja_JP.properties
  plugins/meta-inject/impl/src/main/resources/org/pentaho/di/trans/steps/metainject/messages/messages_ko_KR.properties
  plugins/meta-inject/impl/src/main/resources/org/pentaho/di/trans/steps/metainject/messages/messages_zh_CN.properties
  plugins/meta-inject/impl/src/main/resources/org/pentaho/di/ui/trans/steps/metainject/img/GenericTransform.png
  plugins/meta-inject/impl/src/main/resources/org/pentaho/di/ui/trans/steps/metainject/img/GenericTransform.svg
  plugins/meta-inject/impl/src/test/java/org/pentaho/di/repository/RepositoryImporterTest.java
  plugins/meta-inject/impl/src/test/java/org/pentaho/di/trans/TransMetaTest.java
  plugins/meta-inject/impl/src/test/java/org/pentaho/di/trans/steps/metainject/MetaInjectMetaInjectionTest.java
  plugins/meta-inject/impl/src/test/java/org/pentaho/di/trans/steps/metainject/MetaInjectMetaLoadSaveTest.java
  plugins/meta-inject/impl/src/test/java/org/pentaho/di/trans/steps/metainject/MetaInjectMetaTest.java
  plugins/meta-inject/impl/src/test/java/org/pentaho/di/trans/steps/metainject/MetaInjectMigrationTest.java
  plugins/meta-inject/impl/src/test/java/org/pentaho/di/trans/steps/metainject/MetaInjectTest.java
  plugins/meta-inject/impl/src/test/java/org/pentaho/di/trans/steps/metainject/OpenMappingExtensionTest.java
  plugins/meta-inject/pom.xml
  plugins/meta-inject/src/main/resources/OSGI-INF/blueprint/pentaho-metainject-pdi-blueprint.xml
  plugins/meta-inject/ui/pom.xml
  plugins/meta-inject/ui/src/main/java/org/pentaho/di/ui/trans/steps/metainject/MetaInjectDialog.java
  plugins/meta-inject/ui/src/main/resources/org/pentaho/di/ui/trans/steps/metainject/img/GenericTransform.png
  plugins/meta-inject/ui/src/main/resources/org/pentaho/di/ui/trans/steps/metainject/img/GenericTransform.svg

Unit Test Coverage
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes.  It would be preferable to fix them in order for it to be just perfect. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
mvn -B -f 'pom.xml' -pl 'plugins/meta-inject' -P '!assemblies' -Dsurefire.runOrder=alphabetical -Daudit -amd clean install

Cleanup Commands
mvn -B -f 'pom.xml' -pl 'plugins/meta-inject' -P '!assemblies' -amd build-helper:remove-project-artifact

Changed files
  assemblies/plugins/pom.xml
  plugins/meta-inject/assemblies/plugin/pom.xml
  plugins/meta-inject/assemblies/plugin/src/assembly/assembly.xml
  plugins/meta-inject/assemblies/plugin/src/main/resources/version.xml
  plugins/meta-inject/assemblies/pom.xml
  plugins/meta-inject/impl/pom.xml
  plugins/meta-inject/impl/src/it/java/org/pentaho/di/trans/steps/denormaliser/DenormaliserMetaInjectionIT.java
  plugins/meta-inject/impl/src/it/java/org/pentaho/di/trans/steps/metainject/MetaInjectTemplateInFSAndRepoSpecMethodIT.java
  plugins/meta-inject/impl/src/it/java/org/pentaho/di/trans/steps/normaliser/NormaliserMetaInjectionIT.java
  plugins/meta-inject/impl/src/it/resources/org/pentaho/di/trans/steps/denormaliser/child.ktr
  plugins/meta-inject/impl/src/it/resources/org/pentaho/di/trans/steps/denormaliser/child2.ktr
  plugins/meta-inject/impl/src/it/resources/org/pentaho/di/trans/steps/denormaliser/pdi-11947.ktr
  plugins/meta-inject/impl/src/it/resources/org/pentaho/di/trans/steps/metainject/pdi-16420-template.ktr
  plugins/meta-inject/impl/src/it/resources/org/pentaho/di/trans/steps/metainject/pdi-16420.ktr
  plugins/meta-inject/impl/src/it/resources/org/pentaho/di/trans/steps/normaliser/injected-trans-pdi-13761.ktr
  plugins/meta-inject/impl/src/it/resources/org/pentaho/di/trans/steps/normaliser/injecting-trans-pdi-13761-does-not-inject-field.ktr
  plugins/meta-inject/impl/src/it/resources/org/pentaho/di/trans/steps/normaliser/injecting-trans-pdi-13761.ktr
  plugins/meta-inject/impl/src/it/resources/org/pentaho/di/trans/steps/normaliser/normaliser-13761-expected-output.txt
  plugins/meta-inject/impl/src/main/java/org/pentaho/di/trans/steps/metainject/MetaInject.java
  plugins/meta-inject/impl/src/main/java/org/pentaho/di/trans/steps/metainject/MetaInjectData.java
  plugins/meta-inject/impl/src/main/java/org/pentaho/di/trans/steps/metainject/MetaInjectMapping.java
  plugins/meta-inject/impl/src/main/java/org/pentaho/di/trans/steps/metainject/MetaInjectMeta.java
  plugins/meta-inject/impl/src/main/java/org/pentaho/di/trans/steps/metainject/MetaInjectMigration.java
  plugins/meta-inject/impl/src/main/java/org/pentaho/di/trans/steps/metainject/MetaInjectOutputField.java
  plugins/meta-inject/impl/src/main/java/org/pentaho/di/trans/steps/metainject/OpenMappingExtension.java
  plugins/meta-inject/impl/src/main/java/org/pentaho/di/trans/steps/metainject/RepositoryExporterExtension.java
  plugins/meta-inject/impl/src/main/java/org/pentaho/di/trans/steps/metainject/RepositoryImporterExtension.java
  plugins/meta-inject/impl/src/main/java/org/pentaho/di/trans/steps/metainject/SourceStepField.java
  plugins/meta-inject/impl/src/main/java/org/pentaho/di/trans/steps/metainject/TargetStepAttribute.java
  plugins/meta-inject/impl/src/main/resources-filtered/version.properties
  plugins/meta-inject/impl/src/main/resources/org/pentaho/di/trans/steps/metainject/messages/messages_en_US.properties
  plugins/meta-inject/impl/src/main/resources/org/pentaho/di/trans/steps/metainject/messages/messages_fr_FR.properties
  plugins/meta-inject/impl/src/main/resources/org/pentaho/di/trans/steps/metainject/messages/messages_it_IT.properties
  plugins/meta-inject/impl/src/main/resources/org/pentaho/di/trans/steps/metainject/messages/messages_ja_JP.properties
  plugins/meta-inject/impl/src/main/resources/org/pentaho/di/trans/steps/metainject/messages/messages_ko_KR.properties
  plugins/meta-inject/impl/src/main/resources/org/pentaho/di/trans/steps/metainject/messages/messages_zh_CN.properties
  plugins/meta-inject/impl/src/main/resources/org/pentaho/di/ui/trans/steps/metainject/img/GenericTransform.png
  plugins/meta-inject/impl/src/main/resources/org/pentaho/di/ui/trans/steps/metainject/img/GenericTransform.svg
  plugins/meta-inject/impl/src/test/java/org/pentaho/di/repository/RepositoryImporterTest.java
  plugins/meta-inject/impl/src/test/java/org/pentaho/di/trans/TransMetaTest.java
  plugins/meta-inject/impl/src/test/java/org/pentaho/di/trans/steps/metainject/MetaInjectMetaInjectionTest.java
  plugins/meta-inject/impl/src/test/java/org/pentaho/di/trans/steps/metainject/MetaInjectMetaLoadSaveTest.java
  plugins/meta-inject/impl/src/test/java/org/pentaho/di/trans/steps/metainject/MetaInjectMetaTest.java
  plugins/meta-inject/impl/src/test/java/org/pentaho/di/trans/steps/metainject/MetaInjectMigrationTest.java
  plugins/meta-inject/impl/src/test/java/org/pentaho/di/trans/steps/metainject/MetaInjectTest.java
  plugins/meta-inject/impl/src/test/java/org/pentaho/di/trans/steps/metainject/OpenMappingExtensionTest.java
  plugins/meta-inject/pom.xml
  plugins/meta-inject/src/main/resources/OSGI-INF/blueprint/pentaho-metainject-pdi-blueprint.xml
  plugins/meta-inject/ui/pom.xml
  plugins/meta-inject/ui/src/main/java/org/pentaho/di/ui/trans/steps/metainject/MetaInjectDialog.java
  plugins/meta-inject/ui/src/main/resources/org/pentaho/di/ui/trans/steps/metainject/img/GenericTransform.png
  plugins/meta-inject/ui/src/main/resources/org/pentaho/di/ui/trans/steps/metainject/img/GenericTransform.svg

Unit Test Coverage
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes.


Use pathmap for cross-machine determinism

This is at least required for PDBs, as documented here but I also noticed absolute paths in our DLLs.
We can't trivially do this in Bazel. We need to figure out all of our command line flags during the analysis phase, which doesn't (afaik) know where the build will actually execute (it could be on a remote machine, and analysis also gets cached) so we can't know what paths to map.
We could wrap the compiler to inject this argument at runtime.
We're talking about adding a wrapper already in #12, but I have some concerns. That thing itself needs to be compiled, and probably also needs pathmap to be deterministic, so we've got an even worse chicken and egg problem. Maybe when we compile the wrapper we need a small C program to inject this argument?
I think we need to be flexible and experiment to find out what will work best. The experiments should look at how local and remote caching behave.

I did some digging on MacOS and this is what I found:
We're going to need to paths mapped (either with /pathmap:{x}={y},{a}={b} or with two /pathmap args) to get full reproducibility.

It seems we need to path map the real dir containing WORKSPACE to something stable. This gets deterministic PDBs, which is good but not mission-critical (for D2L). We mightttt be able to figure that out in csharp_repositories but then that also might not work the same for remote builds. Needs investigation.
Some path related to exec/the output root gets embedded into DLLs. This is very important for our caching story. I don't have the full details right now. Bazel likes to have lots of symlinks, so it's a bit of investigation to figure out what we should do here. This also might be different in remote builds.

So we still want to have a wrapper to do the injections as far as I can tell, but it's still a bit of work to figure out what they should be.


How the Kind proof assistant works (the implementation)?

So to briefly summarize, here is what I have seen so far:

THEOREMS.md, which gives some example exercises on how to use the Kind proof assistant.
FMC_SPECIFICATION.md, and old document it looks like, but super helpful for knowing some of your all thought processes.
FormCore.js A very small type theory with dependent types in JavaScript.
The blog and self types intro.
Examples in Kind.
Kind implementing itself?

So I have to explore the last one some more, but have explored the rest (though I haven't done the theorem tutorial yet, just browsed through it). I also ordered a copy of TAPL, to learn more about how to implement type theories. Even looking at your FormCore.js and how simple it is, I don't know the reasoning as to why things were done the way they were done. It would be super helpful if you could add some annotations to it or create a blog post about the theory behind it, or if you already have something out there please share the link :). I know it's about dependent types, but why did you include each piece (App, Var, etc.), and how do the algorithms generally work, etc.
I have a sort of foundational question. I have an undergraduate science degree, so took up to calculus in math, learned software engineering and computer science on my own, and am slowly learning math / type theory (I know basically up through basic abstract algebra, not really category theory, proof theory, or much type theory). I don't know how to do proofs, but I gather it is simply about rewriting terms until the left and right sides match (or top and bottom), applying theorems and rules and such. But I don't get it beyond that, it's still a black box mystery to me!
My first exposure to real math and type systems was with Coq and HoTT. I found that while looking for a mathematical system that could be used in code, and I wanted to figure out how to write proofs instead of just unit tests in code, like I've seen you all mention in the docs. I looked through the HoTT codebase, played a little with the proof assistant, tried to apply some "proof tactics", but still felt like it was a black box mystery and it was very unintuitive, and I don't know why things need to be modeled the way they do. Like why do we need to model the natural numbers as a sequence with succ and Peano's axioms and all that? Etc. tons of fog when I look into the proof assistant / automated theorem proving world. But I want to crack the nut!
It totally looks like Kind lang and the community has fully mastered all of this stuff, obviously 🙂. What I wanted to ask was if you could put together a blog post, or just point to the write things or whatnot in this thread, on how to get where you are in terms of knowledge and grasp of the various type theories/systems and proof assistant implementation stuff. What needs to be studied? What were the key roadblocks that you got past that would be of use to know about, and how did you get past them haha basically. That would be the ideal to know at least.
But in terms of practicality, would love to know how the proof assistant works in some technical detail. First, where is the implementation exactly? Second, what does it technically do when it reads your "proof"? And what exactly is a proof in Kind lang? (i.e. what are all those things you are doing in the THEOREMS.md doc?). When you write a proof, what are you writing? (types? functions? something else?). What does the code do which does the proving correct or disproving (meeting the goals), how does that work?
Anyways, probably a long discussion. Was going to reach out on telegram but it doesn't want to work on my phone and I'm too afraid to download external software on my laptop. Looking forward to hearing from you all! Hopefully there is some piece to this you would feel cool with sharing, I know you all have a wealth of knowledge in there to share. So excited to have found kind lang, it looks so cool and is already teaching me a lot.

Hi, I'm also still learning a ton of stuff, but I'm almost finished reading TaPL, and when you read it you'll recognize a ton of terms/concepts that are applied in Kind and similar languages, stem from primary concepts of a type theory and an implementation of it.
I am not at all in the same level of experience as the library's maintainers/contributors, but I think I can aid in just pasting a few links that helped me.
But talking about dependent types, you basically have another "axis" of flexibility that you can use to prove propositions(https://en.wikipedia.org/wiki/Lambda_cube). Also related videos:

https://www.youtube.com/watch?v=SknxggwRPzU
https://www.youtube.com/watch?v=U5i2VQj5jPk

There's also the "advanced topics in TaPL" that stems from the "original TaPL" book.
And there's also this Reddit thread that people gave their opinion about reading TaPL, and what to do next: https://www.reddit.com/r/types/comments/5r8sv0/how_well_has_pierces_types_and_programming/

I recommend going through "Software Foundations". It teaches theorem proving in Coq. The learning curve is not too steep if you know a bit of programming.


Compilation and installation issues

Hi,
When I make it, the following error appears:

/mnt/Netopeer2/src/log.c:155:10: error: ‘NC_VERB_DEBUG_LOWLVL’ undeclared (first use in this function)
Then I commented NC_VERB_DEBUG_LOWLVL and it can be compiled successfully.
But when I make install, I got an error again:

`-- Set runtime path of "/usr/local/bin/netopeer2-server" to ""
-- Installing missing sysrepo modules...
/usr/local/bin/sysrepoctl: error while loading shared libraries: libsysrepo.so.5: cannot open shared object file: No such file or directory
/usr/local/bin/sysrepoctl: error while loading shared libraries: libsysrepo.so.5: cannot open shared object file: No such file or directory
CMake Warning (dev) at cmake_install.cmake:61 (if):
given arguments:
"127"

An argument named "127" appears in a conditional statement.  Policy CMP0012
is not set: if() recognizes numbers and boolean constants.  Run "cmake
--help-policy CMP0012" for policy details.  Use the cmake_policy command to
set the policy and suppress this warning.
This warning is for project developers.  Use -Wno-dev to suppress it.
CMake Error at cmake_install.cmake:63 (elseif):
given arguments:
"GREATER" "0"

Unknown arguments specified
Makefile:61: recipe for target 'install' failed
make: *** [install] Error 1
    It seems to be a problem with libsysrepo.so.5, but I do have this fileroot@76a0fa33d8d8:/mnt/Netopeer2/build# find / -name libsysrepo.so.5
/usr/local/lib/libsysrepo.so.5
/mnt/sysrepo/build/libsysrepo.so.5
root@76a0fa33d8d8:/mnt/Netopeer2/build# ls /usr/local/lib/libsysrepo.so.5*
/usr/local/lib/libsysrepo.so.5  /usr/local/lib/libsysrepo.so.5.5.0
`
I wonder if my sysrepo is not installed correctly.
Can you help point out my problem
Regards,
Fred

Hi Fred,
as for your first problem, please correctly update libnetconf2, that is why the symbol is not found. The second problem is caused by your dynamic linker not having found libsysrepo.so. You should be able to fix that by simply running # ldconfig. Check that it was found by executing ldconfig -p | grep libsysrepo.
Regards,
Michal

Yes, this problem caused by a problem with sysrepo installation has been solved, thank you


Add repos LICENSE file in image under /licenses dir

Adding the repos LICENSE file to the image under /license.
See https://redhat-internal.slack.com/archives/CKR568L8G/p1731535620986049?thread_ts=1731455170.342769&cid=CKR568L8G and https://redhat-internal.slack.com/archives/CKR568L8G/p1731915836475649 for full context.

/approve
/lgtm


The Donate Button's is not styled properly

The open icon '>' is not aligned to the right of the button.
I can fix it please assign this issue to me
see the icon '>' is appearing below the donate button.

hye @anuragverma108 please assign me this work.


[HOLD for payment 2024-04-15] [$500] Kill ReconnectToReport

In the context of optimizing ReconnectToReport, we are proposing to just get rid of it since it became redundant after reliable updates was implemented.
ReconnectToReport command was introduced to get the missing reportActions after coming back online. This was necessary because ReconnectApp didn't get reportActions, but now that we have "reliable updates", we are able to fetch and retrieve the missed Onyx updates which contain the missing report Actions (The missed updates are returned by ReconnectApp).

Version Number:
Reproducible in staging?:
Reproducible in production?:
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by:
Slack conversation:
Action Performed:
With a report open, go offline and the online again
Expected Result:
Looking at the network requests, we should only see a ReconnectApp request and not a ReconnectToReport request
Actual Result:
ReconnectToReport is there, is sometimes slow and is useless.
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:

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

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

View all open jobs on GitHub

Adding @c3024 in the role of C+ to review the PR https://github.com/Expensify/App/pull/34902

@aldo-expensify
Backend sends a 'deprecated version' error. Clicking on update or refreshing the page does not fix it. 🤔
https://github.com/Expensify/App/assets/102477862/f9456413-ed9f-4a86-9dde-291f79ac6a12

It looks like the linked PR was merged but isn't deployed to prod yet. Once it is, the payment date will be set.

Offer sent to @c3024 in Upwork - https://www.upwork.com/nx/wm/offer/101841684

@lschurr accepted. Thanks.

Payment summary:

$500 to @c3024 (paid in Upwork)


Discord link is not valid

If I press "i" and then "Discord Server" I get an "invitation not valid" warning:

DeepL:

Invalid invitation
This invitation may have expired or you do not have permission to log in.
Continue on Discord
Why is my invitation invalid?

Some other people also reported this, but I have no idea what's wrong.


Add tutorial YAML files parameters

Should close #352, PTAL @jacobperron @maryaB-osr and let me know how can I improve it. I tried to follow a similar format of the section used for launch files migration.
Signed-off-by: Jorge Perez<EMAIL_ADDRESS>

Refactored and merged in #887 , thank you @Blast545


[DOCFIX] Small update in the chinese document of Running-Alluxio-Faul…

…t-Tolerant.md

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/16530/
Test PASSed.


admin interface now checks for both username AND password

Otherwise you can use any password ;)

Oh my, you're totally right! It went unnoticed. Thanks!


Unknown error

I think it's either nothing matches the label, or no networking. But error is not helpful.

❯ cat job.yaml | bacalhau create
Reading from /dev/stdin; send Ctrl-d to stop.Job successfully submitted. Job ID: 7a577139-80d8-4da4-bd02-cca0a70df9c8
Checking job status... (Enter Ctrl+C to exit at any time, your job will continue running):

	Communicating with the network  ................  done ✅  0.1s
	   Creating job for submission  ................  err  ❌  0.0s

Error submitting job: not enough nodes to run job. requested: 1, available: 0.
Job Results By Node:

To get more details about the run, execute:
	bacalhau describe 7a577139-80d8-4da4-bd02-cca0a70df9c8
❯ bacalhau describe 7a577139-80d8-4da4-bd02-cca0a70df9c8
Job:
  APIVersion: V1beta2
  Metadata:
    ClientID: 3aa6bb9e9bd5ed21781a1f16cf1f45f01b3f139ed003aa8ba0a6e486a151ca0f
    CreatedAt: "2023-10-25T17:26:49.473778378Z"
    ID: 7a577139-80d8-4da4-bd02-cca0a70df9c8
    Requester:
      RequesterNodeID: QmdZQ7ZbhnvWY1J12XYKGHApJ6aufKyLNSvf8jZBrBaAVL
      RequesterPublicKey: CAASpgIwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDVRKPgCfY2fgfrkHkFjeWcqno+MDpmp8DgVaY672BqJl/dZFNU9lBg2P8Znh8OTtHPPBUBk566vU3KchjW7m3uK4OudXrYEfSfEPnCGmL6GuLiZjLf+eXGEez7qPaoYqo06gD8ROdD8VVse27E96LlrpD1xKshHhqQTxKoq1y6Rx4DpbkSt966BumovWJ70w+Nt9ZkPPydRCxVnyWS1khECFQxp5Ep3NbbKtxHNX5HeULzXN5q0EQO39UN6iBhiI34eZkH7PoAm3Vk5xns//FjTAvQw6wZUu8LwvZTaihs+upx2zZysq6CEBKoeNZqed9+Tf+qHow0P5pxmiu+or+DAgMBAAE=
  Spec:
    Deal:
      Concurrency: 1
    Docker: {}
    EngineSpec:
      Params:
        Entrypoint:
        - /bin/bash
        - -c
        - python3 /process.py /var/log/logs_to_process/aperitivo_logs.log.1 "SELECT
          * FROM log_data WHERE message LIKE '%[SECURITY]%' ORDER BY '@timestamp'"
        EnvironmentVariables: null
        Image: docker.io/bacalhauproject/motherduck-log-processor:1.1.1
        Parameters: null
        WorkingDirectory: ""
      Type: docker
    Inputs:
    - Name: file:///var/log/logs_to_process
      Path: /var/log/logs_to_process
      StorageSource: localDirectory
    - Name: file:///db/
      Path: /db
      StorageSource: localDirectory
    Network:
      Type: Full
    NodeSelectors:
    - Key: zone
      Operator: =
      Values:
      - europe-west4-b
    PublisherSpec:
      Type: ipfs
    Resources:
      GPU: ""
    Timeout: 1800
    Wasm:
      EntryModule: {}
State:
  CreateTime: "2023-10-25T17:26:49.473778378Z"
  Executions: []
  JobID: 7a577139-80d8-4da4-bd02-cca0a70df9c8
  State: Error
  TimeoutAt: "2023-10-25T17:56:49.473778378Z"
  UpdateTime: "2023-10-25T17:26:49.483037476Z"
  Version: 2

Source: I accidentally scheduled against the public network which didn't have any nodes that matched the label.

Could also be "didn't have access to LocalDir"

Feel free to expand this bug to also take on what more information we can provide during regular job running.

As part of this, you should say what the IP address/DNS address you are submitting to

See if outputting the labels on the requestor node is valuable?

Resolved by #3008.


Pipeline execution

Using a blue-green style deployment strategy we'll run two separate environments for forecasting, one leading the other in experimental terms:

[x] Trial green environment run
[x] Versioning/conda environment for green
[x] Analysis of green
[x] Trial blue environment run
[x] Remove development environment
[x] Analysis of blue
[x] Set up for daily predictions: green
[x] Set up for daily predictions: blue

All execution tasks have now been tested in dualised environment form. Running a single execution environment which can host networks for blue and green. Further conda environments and/or pipeline checkouts can deal with version increments, which basically means we can get an end-to-end devops workflow automated.
Will train blue and green for both hemispheres and leave in situ for automated predictions

Have cron jobs running on the dev environment and instantiated a second environment. Needs detailing (in the notebooks) but this is completed and working


I'm using Tabfragments with navigation drawer

I'm using this from a fragment
I tried to target a view but it dos not work
final View mView = inflater.inflate(R.layout.tab1_content1, container, false); TapTargetView.showFor(mView,                                 TapTarget.forView(mView.findViewById(R.id.checkHomeBroadband), "This is a target", "We have the best targets, believe me")
when I tried to use getActivity()  the target dos not go where the button that I want it to go to,It gos to the main activity view in this case it is the navigation drawer I think
here is a Screenshot:
https://ibb.co/kMQAAf
I want it to target my button how to do that ?
please help
BTW thank you for this great library
Originally posted by @Hararot in https://github.com/KeepSafe/TapTargetView/issues/229#issuecomment-430142459

Hi!, did you find the solution? :(


update pullapprove

Purpose
The pullapprove list of comp bios and and software engineers needs updating.

Changes
Removed Jishu and Dave, add Phil and Nick
Review Instructions
Verify that the list of users is up to date.
PR Checklist
Please ensure the following when opening a PR:

[ ] This PR added or updated tests.
[ ] This PR updated docstrings or documentation.
[ ] Let Jodi (jodihir) know when there is user-facing documentation updates needed!
[ ] This PR applied the Mint style guide for WDL.
[ ] This PR has no WDL linting errors reported by miniwdl
[ ] This PR considered generalizability beyond our own use case.

Follow-up Discussions

@pshapiro4broad, it looks like the changes in this PR are covered by https://github.com/HumanCellAtlas/skylab/pull/172!


Deploy Your Multi-Target Application (MTA)

Tutorials: https://developers.sap.com/tutorials/btp-app-cap-mta-deployment.html
Write here how you think we can improve the tutorial ...
Step 6 Exclude CSV files from deployment describes that CSV files used for testing purposes shall be deleted using npx rimraf for productive deployments.
The better approach would be to define this sample data in the folder test/data instead. This ensures that it will be loaded by default when using cds watch, but it will not be added by cds build --production or cds watch --production.
You may want to give it a try.
See also https://answers.sap.com/questions/13823398/csv-file-ignore-while-deploying-to-production.html
Regards,
Lothar

Hi @LotharBender ,
I could not find test/data mentioned on capire other than in the multitenancy chapter, I can check with my colleagues but do you have any resource mentioning this is the recommendation/best practice?
Best regards,
Manju

Hi Manju,
this documentation is currently being written, but not yet available.
I will add a link once the corresponding Capire documentation has been released. We will distinguish test data from predefined application data.

Lothar

Hi,
I'll close this issue as it has been open for some time now. Please contact me or create a new issue if there has been a resolution already.
Best regards,
Manju


Failing to set price on item in stash

Everytime I try to set a price on an item while its in the stash, I see poe-overlay trying to set the price, but it ends up with no price set and the chat window open.
I have 0.6.25
Playing on windowed fullscreen.

Check out #629. There are a couple videos. Sounds like your issue ^_^

Duplicate of #629


Register existing tables in Iceberg HiveCatalog

This PR allows us to register existing tables in Iceberg HiveCatalog and resolves #251.

@rdblue this is what I meant in #240.

@aokolnychyi, this looks ready. But before we commit it, I want to suggest an alternative for you to consider. What about instead of adding the registerTable method, we added a way to set an existing table's metadata location directly? That would avoid extra public methods in the Catalog interface. It would also be a way to roll back the entire table state, not just rolling back the current snapshot.
This would primarily be an administrator change, so we could expose it through a method in TableOperations, like setMetadataLocation. What do you think? This may be difficult with the new table UUID...

I also thought about registering tables by giving a pointer to the metadata location and not a specific metadata file. However, my assumption was that a location can be shared by multiple Iceberg tables (which is possible because we have random UUIDs in metadata version file names). So, we need to somehow determine what is the last metadata file for a particular table if the location is shared (which can be done using Table UUID we added recently, but someone has to find that UUID anyway).
As always, I am open to considering any alternatives. To avoid changes to the Catalog API, we can require users interested in this to interact with HiveTableOperations directly, meaning they have to create a separate pool of HMS clients and pass a Hadoop config. I am not sure that's a good idea, though.

I also thought about registering tables by giving a pointer to the metadata location and not a specific metadata file.

That isn't quite what I'm suggesting. I'm suggesting that to do the same thing that registerTable does, you create a table and then set its metadata location directly. I've been doing this to troubleshoot by creating a new table, then copying another table's metadata file over its current metadata location. Having a way to simply replace that metadata location of a table would support the use case you have here, but would also allow rolling back to a previous metadata file for the same table.
I think the UUID would be fine. You'd just have to reload the table from the Catalog instead of calling refresh because refresh would detect the UUID change and throw an exception.

I think I am getting it now but there are a couple of questions I want to clarify before updating the PR.
Of course, having a way to roll back the entire table state and minimizing changes to the Catalog API are reasonable benefits. The drawback is that we will have to create a separate instance of HiveTableOperations with its own HMS client pool.
I am not sure we need to create a table and then replace its metadata to simply register a table from a metadata file. If we do so, someone might actually query the table before we swap the metadata location.
This snippet creates a table and sets the location correctly from the beginning:
TableOperations ops = newTableOps(identifier);
HadoopInputFile metadataFile = HadoopInputFile.fromLocation(metadataFileLocation, conf);
TableMetadata metadata = TableMetadataParser.read(ops, metadataFile);
ops.commit(null, metadata);

In theory, this can be executed directly without the catalog and will be sufficient to create a table form an existing metadata file. As suggested, we can extend TableOperations with setMetadataLocation that will be used for rolling back entire table state for tables already present in the catalog.

Of course, having a way to roll back the entire table state and minimizing changes to the Catalog API are reasonable benefits. The drawback is that we will have to create a separate instance of HiveTableOperations with its own HMS client pool.

Why is this? Wouldn't the table use the client pool from the Catalog instance? I think TableOperations is exposed from BaseTable, right? So as long as you are using the HiveCatalog, you'd get a table with an accessible operations object.
To avoid the issue of a table being available before the metadata is replaced, we should add the create/replace transaction methods to Catalog. We'll need those for atomic operations anyway.

@rdblue You are right, we can fetch TableOperations via BaseTable. Create/replace table transactions will solve the second issue as well.
Then table state can be rolled back using these lines:
TableOperations ops = ((BaseTable) table).operations();
ops.commit(ops.current(), TableMetadataParser.read(ops, metadataFile));

Having said that, I think we can close this PR. What do you think?

@aokolnychyi, sounds good to me if that works for you! I didn't think about using TableMetadataParser to do this. That looks better than what I've been doing.


feat: dev script for mitosis cli

The main changes made were in the packages/cli/src/build/dev.ts file and packages/cli/src/commands/dev.ts.
Basically, it runs something like the "build" command on each file change, only on the files changed.

I have not added tests because I'm not very good at writing them. If you could provide me with guidance, that would be great!

@samijaber anything else I can do to get this pr merged?

@samijaber Isn't this feature very important? Does it need some more love? I would very much use this feature. Looking more at what it does, I don't think it should be called dev but rather it should be a --watch flag.
@rgodha24 I guess you closed this issue because it passed a long time with no answer, am I right? Would you care to reopen this issue and refactor it from dev to --watch? I'm willing to help if necessary.

mitosis already has a "--watch" flag, but that's much slower, especially when there's large amounts of files. this only rebuilds the files that are actually changed which is why I called it "dev"

@rgodha24 I see. Maybe we should try to improve that one instead. What do you think about that?

It would be perfect if we supported incremental build.

I'd be down to reimplement a pr starting on may 11 (my last ap test 💀).

Apologies for the delay in getting to this PR @rgodha24. This is definitely a very useful feature! And there is currently no --watch flag for mitosis build, so re-implementing this as mitosis build --dev would be very useful indeed. 🙏🏽
If you have any doubts or questions, I would suggest opening a github issue outlining how you plan on doing it so we can go over it there before a PR is put up.


Set verify_mode according to the new CTX in SSL_set_SSL_CTX

When we deal with SNI, but the serveral CTX have different verify mode, this is useful.
I have this need in one of my project.

Looks sensible.
:+1:

Hmmm. I'm not sure about this. But then I'm not sure about the concept behind the whole function!!!! Why do we copy across just this field from the ctx?

That is a good question. My thinking here, though, is that there's no reason not to let this particular field through.

But what do we do...just add fields ad-hoc as and when people ask for them to be copied? That doesn't seem a great approach. Personally I'm wondering whether this whole function should be deprecated, and we just leave it alone.

Frankly, I haven't even noticed this function before, so I'm pretty much dumbfounded. Deprecation may very well be the answer.

Ok...so how do we take this forward?

Dunno. libssl isn't my forte. This function is obviously used by at least one user, so it's a matter of finding another mechanism to replace it with... But then, it's a bit late to do anything major, at least for 1.1.0...
... The other option is to have a long hard look at the fields that are copied when a SSL is created and see what can and should be copied in this function as well. That would fit in 1.1.0, methinks.

My feeling is this function is potentially dangerous....I could imagine all sorts of subtle bugs if suddenly the ctx changes underneath your feet. Perhaps raise a discussion with the team?

A discussion is a good idea. Take the lead :-)

After discussion with the team there is a view that this could be a breaking change that is unjustified this late in the release cycle. I'm not closing this as we may want to look at this again, post 1.1.0, but changing the milestone for this PR.

Since SSL_set_SSL_CTX is called in the servername callback in this case, the callback itself can copy the various options and verify settings as needed. No need to have SSL_set_SSL_CTX update the SSL's settings.

This is stalled and probably not a good idea according to the discussion above.


Add jitter to scheduled snapshots and retry harder on conflicts

Proposed Changes
Add jitter to scheduled snapshots and retry harder on conflicts
Also ensure that the snapshot job does not attempt to trigger multiple concurrent runs, as this is not supported.
Types of Changes
bugfix
Verification
See linked issue
Testing

Linked Issues

https://github.com/k3s-io/k3s/issues/6714

User-Facing Change

Scheduled etcd snapshots are now offset by a short random delay of up to several seconds. This should prevent multi-server clusters from executing pathological behavior when attempting to simultaneously update the snapshot list ConfigMap. The snapshot controller will also be more persistent in attempting to update the snapshot list.

Further Comments

Merging despite codespell flake


Test PR 225 (install/pre-install: Update containerd)

I'm trying to merge https://github.com/confidential-containers/operator/pull/179 before PR #225 so that the later would be tested before merge. However, PR #179 is blocked due to what seems network issues on SEV and TDX machine when it comes to build the  pre-install image.
As we are approaching the 0.7.0 release I think it is more prudent to unblock the merge of #225. So this PR, where I pilled up #225 on #179 then I will run the non-TEE tests jobs. After the merge of #225 and when a new pre-install image is built then we will have the opportunity to test the updated containerd on SEV and TDX (as the pre-install image won't be built on those machines I expect the test suite to just run).
That's my rationale for this PR. Marking as do-not-merge.

/test-kata-qemu
/test-kata-clh

On both kata-clh and kata-qemu jobs we are getting connectivety issues to build the pre-install image:
09:42:53 #9 96.23 E: Failed to fetch https://packages.cloud.google.com/apt/dists/kubernetes-xenial/main/binary-s390x/by-hash/SHA256/5347fddf3a45c1f4bef10ba934363533f13544e91c325ce8a276bcfbf3ef1f01  404  Not Found [IP: <IP_ADDRESS> 443]
09:42:53 #9 96.23 E: Some index files failed to download. They have been ignored, or old ones used instead.
09:42:53 #9 ERROR: process "/bin/bash -o pipefail -c apt-get update && apt-get install -y --no-install-recommends apt-transport-https ca-certificates curl xz-utils systemd && mkdir -p /etc/apt/keyrings/ && curl -fsSLo /etc/apt/keyrings/kubernetes-archive-keyring.gpg https://dl.k8s.io/apt/doc/apt-key.gpg && echo \"deb [signed-by=/etc/apt/keyrings/kubernetes-archive-keyring.gpg] https://apt.kubernetes.io/ kubernetes-xenial main\" | tee /etc/apt/sources.list.d/kubernetes.list && apt-get update && apt-get install -y --no-install-recommends kubectl && apt-get clean && rm -rf /var/lib/apt/lists/ && curl -fOL --progress-bar [https://github.com/confidential-containers/containerd/releases/download/v${VERSION}/containerd-${VERSION}-linux-${ARCH}.tar.gz](https://github.com/confidential-containers/containerd/releases/download/v$%7BVERSION%7D/containerd-$%7BVERSION%7D-linux-$%7BARCH%7D.tar.gz) && tar xvzpf containerd-${VERSION}-linux-${ARCH}.tar.gz -C ${DESTINATION}/opt/confidential-containers" did not complete successfully: exit code: 100
09:42:53 ------

This might be a long shot but can you replace the repo url with:
http://packages.cloud.google.com/apt/ instead of  https://apt.kubernetes.io/ (the http is intentional).

This might be a long shot but can you replace the repo url with: http://packages.cloud.google.com/apt/ instead of https://apt.kubernetes.io/ (the http is intentional).
Otherwise (if that doesn't help) lets do like you suggested: fetch kubectl with curl directly.

hmmm... trying this solution first: https://github.com/confidential-containers/operator/pull/226/commits/91e2c8a415531fc8fe354750ef29f9b212dc25da

/test-kata-qemu
/test-kata-clh

Forgot to install gpg in the container... let's see:
/test-kata-qemu
/test-kata-clh

Updated this PR to include the commit https://github.com/confidential-containers/operator/pull/226/commits/cf3aaef619d2597c2f00e37fcc7f6a28982605ea which changed the pre-install Dockerfile to pull the kubectl binary, instead of installing via package which has been a nightmare.
/test-kata-qemu
/test-kata-clh

/test

SEV tests have failed with:
10:37:06 + docker manifest push --insecure localhost:5000/container-engine-for-cc-payload:latest
10:37:06 failed to put manifest localhost:5000/container-engine-for-cc-payload:latest: errors:
10:37:06 manifest blob unknown: blob unknown to registry
10:37:06 manifest blob unknown: blob unknown to registry
10:37:06 manifest blob unknown: blob unknown to registry
10:37:06 manifest blob unknown: blob unknown to registry
10:37:06 manifest blob unknown: blob unknown to registry
10:37:06 manifest blob unknown: blob unknown to registry

and
11:31:13 fatal: [localhost]: FAILED! => {"changed": false, "msg": "Failure downloading https://go.dev/dl/go1.18.5.linux-amd64.tar.gz, Request failed: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1131)>"}

I've requeued, so hoping for third time lucky

The third sev attempt failed with:
13:07:22 + docker manifest push --insecure localhost:5000/container-engine-for-cc-payload:8056fd0d9fc0b4e2bb3201bc939b85ad414ce9a4
13:07:22 failed to put manifest localhost:5000/container-engine-for-cc-payload:8056fd0d9fc0b4e2bb3201bc939b85ad414ce9a4: errors:
13:07:22 manifest blob unknown: blob unknown to registry
13:07:22 manifest blob unknown: blob unknown to registry
13:07:22
13:07:22 make: *** [Makefile:8: containerd-container-image] Error 1

again, so I'm not going to try and re-do it a fourth time. @UnmeshDeodhar @ryansavino - do you have any ideas?

The third sev attempt failed with:
13:07:22 + docker manifest push --insecure localhost:5000/container-engine-for-cc-payload:8056fd0d9fc0b4e2bb3201bc939b85ad414ce9a4
13:07:22 failed to put manifest localhost:5000/container-engine-for-cc-payload:8056fd0d9fc0b4e2bb3201bc939b85ad414ce9a4: errors:
13:07:22 manifest blob unknown: blob unknown to registry
13:07:22 manifest blob unknown: blob unknown to registry
13:07:22
13:07:22 make: *** [Makefile:8: containerd-container-image] Error 1

again, so I'm not going to try and re-do it a fourth time. @UnmeshDeodhar @ryansavino - do you have any ideas? Any reason why the node can't built the new container image?

It is failing to push the image to a local registry. I've almost sure I saw that error before but can't remember the reason. As I commented on PR #225 I think we can disregard the sev results, merge that PR then test again with the new built image.

I am going to close this as the PR #225 is merged already.


[FX-4590] Setup tailwind

FX-4590
Description
Setup TailwindCSS to work properly in the Cypress and the Storybook.
It is only for development right now, we will announce the need to setup Tailwind in the user repositories and after some time, we will add Tailwind as peer dependency of Picasso and it will be breaking change.
How to test

Temploy
Check the accordion in the storybook, it should have red background
We should see breaking snapshots and and also new happo screenshots

Screenshots

Before.
After.

Insert screenshots or screen recordings
Insert screenshots or screen recordings

Development checks

N/A Add changeset according to guidelines (if needed)
[x] Read CONTRIBUTING.md and Component API principles
[x] Make sure that additions and changes on the design follow Toptal's BASE design, and it's been already discussed with designers at #-base-core
[x] Annotate all props in component with documentation
[x] Create examples for component
[x] Ensure that deployed demo has expected results and good examples
[x] Ensure the changed/created components have not caused accessibility issues. How to use accessibility plugin in storybook.
[x] Self reviewed
[x] Covered with tests (visual tests included)

Breaking change

N/A codemod is created and showcased in the changeset
N/A test alpha package of Picasso in StaffPortal

All development checks should be done and set checked to pass the
GitHub Bot: TODOLess action

PR commands

List of available commands:

@toptal-bot run package:alpha-release - Release alpha version
@toptal-anvil ping reviewers - Ping FX team for review

PR Review Guidelines

When to approve? ✅
You are OK with merging this PR and

You have no extra requests.
You have optional requests.

Add nit: to your comment. (ex. nit: I'd rename this variable from makeCircle to getCircle)

When to request changes? ❌
You are not OK with merging this PR because

Something is broken after the changes.
Acceptance criteria is not reached.
Code is dirty.

When to comment (neither ✅ nor ❌)
You want your comments to be addressed before merging this PR in cases like:

There are leftovers like unnecessary logs, comments, etc.
You have an opinionated comment regarding the code that requires a discussion.
You have questions.

How to handle the comments?

An owner of a comment is the only one who can resolve it.
An owner of a comment must resolve it when it's addressed.
A PR owner must reply with ✅ when a comment is addressed.

@toptal-bot run package:alpha-release

@toptal-bot run package:alpha-release

@toptal-bot run package:alpha-release

@toptal-anvil ping reviewers

@toptal-anvil ping reviewers


Suggestion for Securing Group Creation

Hi sir,
I've been implementing NIP-29 groups in 0xchat and noticed some changes in relay29. Thank you for the updates! 🙏
However, I encountered an issue during group creation. Currently, groups can be created by simply inputting an npub and name. This allows others to potentially impersonate an npub and create a group as if they were the group owner.
I suggest enhancing the group creation process by requiring a JSON event to be sent to the server, which can also initialize some group information. Here’s a proposed structure for the JSON event:
{
  "pubkey": creator pubkey,
  "kind": create group event kind,
  "content": "",
  "tags": [
    ["name", "Pizza Lovers"],
    ["picture", "https://pizza.com/pizza.png"],
    ["about", "A group for people who love pizza"],
    ["public"], // or ["private"]
    ["open"] // or ["closed"]
  ],
  "sig": sig
}

I don't follow. Why can't you create a group and be the group owner? That is the idea.
But that group creation page is nonstandard, it's there for testing purposes and will be removed or modified later.

In the current implementation, when you create a group chat, you don't need to verify if you are the owner of the pubkey. You just need to enter a pubkey and a group name. Therefore, you can enter anyone's pubkey to create a group and make them the group owner.
So I think a signature verification is needed?

I see. Yes, that's indeed a flaw. Will improve on that.

See also: https://github.com/nostr-protocol/nips/pull/1344


How to use preserve state on close correctly?

Good afternoon. I made a modal window according to the instructions, but when I close it loads, after which the background is updated. How can I fix this problem? Thank you in advance for your cooperation.

Same problem. I can't explain why it pops up on the page before. The modal is only implemented in the sub route.


PROCESS build error if default numpy is used

In GitLab by @ajpearcey on Oct 27, 2022, 10:08
IF you follow the installation guide the PROCESS install procedure will fail as PROCESS now required a certain version of numpy to work.
If you run the command pip3 install -r requirements.txt it will uninstall the install the combatable version of numpy (1.21.5).

This is related to #2935.


Current grpc plugin can't be applied to grpc client in nacos 2.3

when injecting classes, the following error is reported:
java.lang.NoClassDefFoundError: com/alibaba/nacos/shaded/io/grpc/ForwardingClientCallListener$SimpleForwardingClientCallListener

The missed class is used in ClientCallInterceptor

The nacos is using grpc 1.57(https://github.com/alibaba/nacos/blob/develop/pom.xml), while the plugin is using 1.60


Better and complete descriptions of the metrics under GMD

Hey all
Some of the metrics under GMD have incomplete information about how to calculate them. Example:

issue-resolution-efficiency: how do we say that an issue has been abandoned?
open-issue-age: do we calculate the average open issue age or should we chart each open issue individually in a graph along with the days since they were opened.
closed-issue-resolution-duration: here, the description seems wrong.

Hi @aswanipranjal, you're right :)
The way that this has evolved as been for us to capture the metrics that people would like to see (even if there is not necessarily a known implementation). In essence, we have cast a wide net to listen to what people would like.
That said, as work in places like the GMD workgroup find ways to implement in any respective technology (GL, Augur, Kibble), they can update the metric template.

@germonprez, it is a wide net indeed :P I am also trying to implement them in manuscripts according to my understanding. I'll update on them once I have a better understanding and I solidify my ideas.

Since all child issues are closed, I think we can close this one as well. Please reopen if you feel that's needed.


Went online and downloaded the latest today and the top left panel is all messed up.

The Culture/Science panel showing progress has disappeared with the latest to be replaced by this:

I had decided to try the Better Report Screen and Expanded Policy Cards mods and thought that had messed things up so I disabled and uninstalled them but it didn't help.
I run Win10 with all the game expansions and only CQUI (plus brightness and city state wall mods).

Forgot to mention I also have the notification log mod.

Many tests later I have isolated this to the log mod. It has not changed but it seems their last game update has broken something.


feat: annotate context with feature flags when handling flux queries

Annotate the context with feature flags when handling flux queries in influxdb.
Taking advantage of this in flux end-to-end tests. Using a custom flagger that
can set overrides based on the test case that is about to be run, allowing us
to enable features in the end-to-end tests.

This seems sane @adrian-thurston and avoids the problem of changing flags for all tests, as was my concern with the last approach. Nice one!
I think you could simplify things by avoiding the use of a new flagger implementation. The override flagger should return the default in case an override is not present for a given flag, so simply using an override flagger with an empty override map should be equivalent to using a default flagger. I think you can get rid of TestFlagger and just always use an override flagger, in other words.
Let me know if that idea pans out. Besides that idea this looks good to me!

Thank you for having a look @gavincabbage!
I need the flags to change state from one test to the next. Each test is allowed to specify it's own feature flags state. Can I use override flagger for that? I couldn't see how I could alter the flags after passing them to the request handler, via the launcher.
I noticed all the flaggers are passed around by value, in IDPE and influxdb. So I didn't want to go around changing everything to a pointer so I could access it during run time. I thought using a custom flagger with a pointer back to the state would be less disruptive. Am I understanding things right?


.voicepresence removed?

Was .voicepresence removed? I can't find it in the commands list and Nadeko no longer longs voice presence after updating to latest just a few minutes ago.

Scratch that. Found .logevents. ¯\_(ツ)_/¯


!text-[var(--damu-font-size)] is incorrect

UnoCSS version
^0.47.6
Describe the bug

why not
Reproduction
Shouldn't the snippet result be ??

System Info
No response
Validations

[X] Read the Contributing Guidelines.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

You could do:

!text-size-[var(--damu-font-size)]
![font-size:var(--damu-font-size)]


Error running lua:

Getting the following error in CI on github:
Error running Lua:
No render function for Block value 'Figure';
define a function `Writer.Block.Figure` that returns a string or Doc.
stack traceback:
	/scripts/panvimdoc.lua:61: in upvalue 'blocks'
	/scripts/panvimdoc.lua:196: in function 'pandoc.scaffolding.Writer.Pandoc'
	while rendering Pandoc
stack traceback:

I dont think this is solved. I am getting this now:
No render function for Inline value 'Quoted';
define a function `Writer.Inline.Quoted` that returns a string or Doc.
stack traceback:
      /scripts/panvimdoc.lua:52: in upvalue 'inlines'
      /scripts/panvimdoc.lua:261: in function 'pandoc.scaffolding.Writer.Block.Para'
      /scripts/panvimdoc.lua:61: in upvalue 'blocks'
      /scripts/panvimdoc.lua:195: in function 'pandoc.scaffolding.Writer.Pandoc'
      while rendering Pandoc

Can you point me to the README file that is causing the error? If I'm able to test it locally I should be able to fix it.

Thank you.
Seems to be solved now.


particle setup without WiFi card

By default the particle setup tries to configure the Photon by WiFi using the Soft-AP mode, but I guess this option should not appear when the computer has no WiFi network interface.
In my case I'm running OSX without a WiFi card, and when running the particle setup I would have not other option than choosing No to the latest question shown below:
$ particle setup
                  _   _      _        _
 _ __   __ _ _ __| |_(_) ___| | ___  (_) ___
| '_ \ / _` | '__| __| |/ __| |/ _ \ | |/ _ \
| |_) | (_| | |  | |_| | (__| |  __/_| | (_) |
| .__/ \__,_|_|   \__|_|\___|_|\___(_)_|\___/
|_|                     https://particle.io/

> Setup is easy! Let's get started...
> It appears as though you are already logged in as<EMAIL_ADDRESS>? Would you like to log in with a different account? No

! PROTIP: Hold the MODE/SETUP button on your device until it blinks blue!
! PROTIP: Please make sure you are connected to the internet.

> I have detected a Photon connected via USB.
? Would you like to continue with this one? Yes
! The Photon supports secure Wi-Fi setup. We'll try that first.

! PROTIP: Wireless setup of Photons works like a wizard!
! PROTIP: We will automagically change the Wi-Fi network to which your computer is connected.
! PROTIP: You may lose your connection to the internet for a moment.

> No nearby Photons detected. Try the `particle help` command for more information.
? Would you like to wait and monitor for Photons entering setup mode? No

> Ok, bye! Don't forget `particle help` if you're stuck! <3

If I choose Yes to the latest question, the script attempts forever to find a Photon by an inexistent WiFi connection:
...
? Would you like to wait and monitor for Photons entering setup mode? Yes
> Monitoring nearby Wi-Fi networks for Photons. This may take up to a minute.
* Waiting for a wild Photon to appear... (press ctrl + C to exit)

So, if it's not possible to autodetect the presence of a WiFi card in the current computer, why don't you just enter in the manual WiFi credentials setup after choosing Noin the latest question... as it would apprear when executing particle setup wifi:
$ particle setup wifi
? Should I scan for nearby Wi-Fi networks? No
? SSID: XXXXXXX
? Security Type: WPA2
? Wi-Fi Password: *********

That is, the particle setup would make sense at least to continue like this, after choosing No in the latest question:
...
? Would you like to wait and monitor for Photons entering setup mode? No
? SSID: XXXXXXX
? Security Type: WPA2
? Wi-Fi Password: *********

@javier-rodas, thank you for the suggestion! I will be working on improving the logic around automagic Wi-Fi and manual modes. I think you propose a sensible way to handle this better.

One thing to note is that we cannot configure a claim code over serial, so we would need to initiate the old claim process (device add) once the device is online.

The claim code over serial is supported from firmware version 0.6.0-rc.1, so we could use the new claim process over serial.  We can also set the claim code via dfu in all versions, so that might provide a simpler alternative.

setup the device wifi credentials via serial
trigger the device to enter DFU mode by switching to 14400 baud
obtain the claim code from the cloud and use dfu to write the claim code to the DCT region

I'm closing this one because claiming over serial is part of particle setup now.


Finish erb to slim transition

Together with @gazay we just finished erb to slim transition. We tried to keep everything as is, and we have plans to fix view issues we found in near future.

Looks good to me.


[BUG] Swiping through gallery doesn't work sometimes

Describe the bug
When using photo_view to swipe through photos in a gallery, swiping (horizontal drag gesture) doesn't work sometimes. I enabled debugPrintGestureArenaDiagnostics and the logs gives an idea of what's happening internally.
When swiping works:
I/flutter (26426): Gesture arena 170  ❙ ★ Opening new gesture arena.
I/flutter (26426): Gesture arena 170  ❙ Adding: DoubleTapGestureRecognizer#b7996(debugOwner: PhotoViewGestureDetector)
I/flutter (26426): Gesture arena 170  ❙ Adding: PhotoViewGestureRecognizer#36e70(debugOwner: PhotoViewGestureDetector)
I/flutter (26426): Gesture arena 170  ❙ Adding: HorizontalDragGestureRecognizer#3afc9(start behavior: start)
I/flutter (26426): Gesture arena 170  ❙ Closing with 3 members.
I/flutter (26426): Gesture arena 170  ❙ Accepting: HorizontalDragGestureRecognizer#3afc9(start behavior: start)
I/flutter (26426): Gesture arena 170  ❙ Self-declared winner: HorizontalDragGestureRecognizer#3afc9(start behavior: start)

When swiping doesn't work:
I/flutter (26426): Gesture arena 169  ❙ ★ Opening new gesture arena.
I/flutter (26426): Gesture arena 169  ❙ Adding: DoubleTapGestureRecognizer#b7996(debugOwner: PhotoViewGestureDetector)
I/flutter (26426): Gesture arena 169  ❙ Adding: PhotoViewGestureRecognizer#36e70(debugOwner: PhotoViewGestureDetector)
I/flutter (26426): Gesture arena 169  ❙ Adding: HorizontalDragGestureRecognizer#3afc9(start behavior: start)
I/flutter (26426): Gesture arena 169  ❙ Closing with 3 members.
I/flutter (26426): Gesture arena 169  ❙ Accepting: PhotoViewGestureRecognizer#36e70(debugOwner: PhotoViewGestureDetector)
I/flutter (26426): Gesture arena 169  ❙ Self-declared winner: PhotoViewGestureRecognizer#36e70(debugOwner: PhotoViewGestureDetector)

So at times PhotoViewGestureRecognizer wins instead of HorizontalDragGestureRecognizer which is causing this issue.
To Reproduce
Use the example app (https://github.com/bluefireteam/photo_view/releases/tag/0.14.0) and go to "gallery". Open the first photo from the gallery and swipe to the next photo. The first swipe doesn't work, the second does. The bug comes up randomly too while swiping through photos.
What is the current behaviour?
Swiping (horizontal drag gesture) doesn't work sometimes.
Expected behaviour
Swiping will always work and shows next/prev photo.
Screenshots
https://github.com/bluefireteam/photo_view/assets/77285023/e8001129-3cd6-4399-a331-5103841b58bb
Which versions of Flutter/Photo View, and which browser / OS are affected by this issue? Did this work in previous versions of Photo View?
Flutter v3.10.6
photo_view v0.14.0
Reproducible on both Android and iOS.

Same error here, any solution?

Same issue. Every first swipe it doesn't work:
I/flutter (26851): Gesture arena 581  ❙ ★ Opening new gesture arena.
I/flutter (26851): Gesture arena 581  ❙ Adding: DoubleTapGestureRecognizer#2dfb4(debugOwner: PhotoViewGestureDetector)
I/flutter (26851): Gesture arena 581  ❙ Adding: PhotoViewGestureRecognizer#7fa14(debugOwner: PhotoViewGestureDetector)
I/flutter (26851): Gesture arena 581  ❙ Adding: HorizontalDragGestureRecognizer#d9dac(start behavior: start)
I/flutter (26851): Gesture arena 581  ❙ Closing with 3 members.
I/flutter (26851): Gesture arena 581  ❙ Accepting: PhotoViewGestureRecognizer#7fa14(debugOwner: PhotoViewGestureDetector)
I/flutter (26851): Gesture arena 581  ❙ Self-declared winner: PhotoViewGestureRecognizer#7fa14(debugOwner: PhotoViewGestureDetector)
Then on the second on it works:
I/flutter (26851): Gesture arena 582  ❙ ★ Opening new gesture arena.
I/flutter (26851): Gesture arena 582  ❙ Adding: DoubleTapGestureRecognizer#2dfb4(debugOwner: PhotoViewGestureDetector)
I/flutter (26851): Gesture arena 582  ❙ Adding: PhotoViewGestureRecognizer#7fa14(debugOwner: PhotoViewGestureDetector)
I/flutter (26851): Gesture arena 582  ❙ Adding: HorizontalDragGestureRecognizer#d9dac(start behavior: start)
I/flutter (26851): Gesture arena 582  ❙ Closing with 3 members.
I/flutter (26851): Gesture arena 582  ❙ Accepting: HorizontalDragGestureRecognizer#d9dac(start behavior: start)
I/flutter (26851): Gesture arena 582  ❙ Self-declared winner: HorizontalDragGestureRecognizer#d9dac(start behavior: start)
[GETX] CLOSE TO ROUTE /MyPhotoViewGallery

Is there a workaround ?

same issue

I think it's related to "android gesture navigation" because when this is disabled it works without issue.

look this issues https://github.com/bluefireteam/photo_view/issues/383


setTimeout is broken

Not really sure here but somethign is fishy.. I am running on device via debug mode.
componentDidMount()` {
    console.log('Modal Mounts!')
    setTimeout(() => {
      console.log('Open')
      this.props.openModal()
    }, 10000)

  }

This will always fire instantly... about 100 ms
componentDidMount() {
    console.log('Modal Mounts!')
    setTimeout(() => {
      console.log('Open')
      this.props.openModal()
    }, 30000)

  }

Fires instantly as well
componentDidMount() {
    console.log('Modal Mounts!')
    setTimeout(() => {
      console.log('Open')
      this.props.openModal()
    }, 80000)

  }

Fires after about 30 seconds

To further illustrate this problem...
console.log('In Modal')
setTimeout(() => console.log('Five Seconds'), 5000)

Check that your device/simulator's time matches that of your computer!

There is already an issue open for this. There doesn't seem to be any fix on the way however.
https://github.com/facebook/react-native/issues/4470

Looks like this is now fixed as discussed in https://github.com/facebook/react-native/issues/9436 .

got problem with 0.49.5 version.
setTimeout(() => console.log('Five Seconds'), 5000) // NOT WORKING
setTimeout(() => console.log('ZERO Seconds'), 0) // WORKING


Need a license

Soon we will need to add a license. This is to protect contributors and anyone who wants to own the project.
https://choosealicense.com/

I have added BSD 3 license for this project. Please let me know your feedback.

License Added.


Change Img Tag  to Image Component

Hey guy change the img tag to Image component for faster and better experience

done with TeamCards component

donw


Avoid generating async methods when there are no ones in service impl

Resolves #63  .
I made some changes so that when there are absolutely no async calls in the service impl, only sync methods will be generated.

@reviewer-or-team

Noticed this issue and is revising


Provide guidance on logging frameworks

Provide guidance on logging frameworks for ie logging exceptions.
Ideas:

Cloud:

Application Insights

On-Prem:

ETW?

For practical reasons, let’s move this to the “should have”

In the API guidelines, I would emphasize on how / what to log (using operation-id's, correlation-ids, ...) and not advice on using a certain Logging Framework.
Instead, I'd suggest to make use of Microsoft.Extensions.Logging.ILogger interface which abstracts away the specific logging framework that is being used.   Most modern logging frameworks have extensions that implement this interface, so you're nog tightly coupled on a specific implementation.  (SeriLog), NLog.

Sounds good to me, leaning towards that appraoch as well nowadays.
We should also provide guidance what not to log ie due to GDPR