Remove Export Guide V1 to V2

With sunsetting of v1 completed, we should remove the guide on how to export from v1 to v2: https://zitadel.com/docs/guides/integrate/export-and-import

I would leave it for a moment in the docs.
We may have self-hosting customers with V1 that want to migrate to V2

Sure, makes sense. Then as a reminder for later.


no compile sdK 6.1.1

this error please
[ERROR] :  Failed to run dexer:
[ERROR] :
[ERROR] :  Uncaught translation error: java.lang.IllegalArgumentException: already added: Lcom/google/android/gms/gcm/GcmListenerService;
[ERROR] :  Uncaught translation error: java.lang.IllegalArgumentException: already added: Lcom/google/android/gms/gcm/GcmListenerService$1;
[ERROR] :  Uncaught translation error: java.lang.IllegalArgumentException: already added: Lcom/google/android/gms/gcm/GcmListenerService$2;
[ERROR] :  Uncaught translation error: java.lang.IllegalArgumentException: already added: Lcom/google/android/gms/gcm/GcmNetworkManager;
[ERROR] :  Uncaught translation error: java.lang.IllegalArgumentException: already added: Lcom/google/android/gms/gcm/GcmPubSub;
[ERROR] :  Uncaught translation error: java.lang.IllegalArgumentException: already added: Lcom/google/android/gms/gcm/GcmReceiver;
[ERROR] :  Uncaught translation error: java.lang.IllegalArgumentException: already added: Lcom/google/android/gms/gcm/GcmTaskService;
[ERROR] :  Uncaught translation error: java.lang.IllegalArgumentException: already added: Lcom/google/android/gms/gcm/GcmTaskService$zza;
[ERROR] :  Uncaught translation error: java.lang.IllegalArgumentException: already added: Lcom/google/android/gms/gcm/GoogleCloudMessaging;
[ERROR] :
[ERROR] :  UNEXPECTED TOP-LEVEL EXCEPTION:
[ERROR] :  java.lang.RuntimeException: Translation has been interrupted
[ERROR] :  	at com.android.dx.command.dexer.Main.processAllFiles(Main.java:615)
[ERROR] :  	at com.android.dx.command.dexer.Main.runMultiDex(Main.java:368)
[ERROR] :  	at com.android.dx.command.dexer.Main.runDx(Main.java:289)
[ERROR] :  	at com.android.dx.command.dexer.Main.main(Main.java:247)
[ERROR] :  	at com.android.dx.command.Main.main(Main.java:94)
[ERROR] :  Caused by: java.lang.InterruptedException: Too many errors
[ERROR] :  	at com.android.dx.command.dexer.Main.processAllFiles(Main.java:607)
[ERROR] :  	... 4 more

Comming to say the same:
Ti SDK 6.1.2 and I get this error:
08-08 12:42:41.679: E/AndroidRuntime(3078): java.lang.UnsatisfiedLinkError: Cannot load library: link_image[1962]:   101 could not load needed library 'libstlport_shared.so' for 'libnl.vanvianen.android.gcm.so' (load_library[1117]: Library 'libstlport_shared.so' not found)

I will autorespond: there is a fork updated with 6.x
https://github.com/skypanther/gcmpush/tree/master/dist

@mcvendrell The module from the link you've provided works just fine w/ Ti SDK 6+, however I'm experiencing an issue when the Push Notification does not show up when the app is closed/background (even if I can see some console logs regarding that the push notification message was received). Do you know by chance what can cause that problem? Thanks! :+1:

Hi @vasilestefirta . I have no issues with this module. Works well for me, no matter if app is closed or backgrounded.
Just be sure that the expected payload from the server is right (if you are building the payload manually)

Interesting! Do you mind sharing your implementation for gcm.registerPush() method and your <android>...</android> section from your project's tiapp.xml file? I would really appreciate that! :pray:

Of course, nothing special (GCMsender... is the name for the FCM id):
	gcm.registerPush({ 		senderId: Alloy.CFG.GCMsenderNotifId, 		notificationSettings: { 			smallIcon: 'notify.png',  // Place icon in platform/android/res/drawable/ 			largeIcon: 'notify.png',  // Same 			vibrate: true,  // Whether the phone should vibrate                         sound: 'default', 		},         success: deviceTokenSuccess, // Success returns event.registrationId         error: deviceTokenError, // Error returns event.error 		callback: receivePushMessage // Callback returns event.data 	});
And nothing in the tiapp.xml, this module doesn't need it.

@mcvendrell Thanks! It looks like the issue was happening because of the data I was sending from the server. I was sending text instead of message :simple_smile: Fixed it and now it works just fine!

@vasilestefirta that's why I warn about be sure on the payload. Excellent.


Split List view and Grid view demos

We have Column View which is a separate demo, no reason for List View and Grid View to be together.
Let's split the demo "List View Widgets" into "List View" and "Grid View"

Screengrabs:
https://github.com/workbenchdev/demos/assets/72352158/e6e61d1f-2535-4871-9ff3-fb7b34ef78ea
https://github.com/workbenchdev/demos/assets/72352158/2501a863-c141-4094-b2e0-0303c645caa0
Do you think these look good?
Also, do we need to change the description for them? I changed the grammar but it's the same sentence for both


css assets got wrong order after building

I use vite vue 3 with AntDesign, recently found that after running 'npm run build', the css assets is not in correct order.
usually the vendor should go before common, if not, some custom css will be covered by third-party css.

here is the config
  ViteComponents({
      dts: true,
      resolvers: [
        AntDesignVueResolver({
          importStyle: 'less',
          resolveIcons: true
        })
      ]
    }),
`

They also have different hash... maybe something wrong with your config? But either way, there is no guarantee that the CSS is imported in order. You should explicitly import them beforehand if the order of them matters.

They also have different hash... maybe something wrong with your config? But either way, there is no guarantee that the CSS is imported in order. You should explicitly import them beforehand if the order of them matters.

different hash? emm... it's just js and css, i mean the css should be in same order with js, vendor goes before. thought it's related with the auto importing of ant components css. my custom css has been covered by it.

bro, have you solved this yet, i have the same problem @CaiWenlie

bro, have you solved this yet, i have the same problem @CaiWenlie

FYI. https://juejin.cn/post/6938351367517896712


.swiper-scrollbar-drag not given a width after showing/hiding slides - window resize brings it back

Swiper Version: 5.3.0
Platform/Target and Browser Versions: Windows Firefox, but assume all

https://stackblitz.com/edit/swiper-demo-1-default-jm95cg?file=index.html
This is a minimal reproduction of my use case.  I filter slides based on their data-attribute values (not included in this example).  I hide the ones that do not match and show the ones that do.  After any changes I update swiper as needed to make it aware of these changes.  All of this works great.  Note that my scrollbar is 'outside' of the normal .swiper-container div.
My problem is the scrollbar.  If all slides are hidden it disappears obviously and when slides are shown it reappears, BUT there is no width given to the draggable area (.swiper-scrollbar-drag).  So there is a scrollbar without a visible draggable part.
I would expect that one of the many update calls (see below) would take care of this, but it does not.
update calls after hiding/showing slides :
swiper.updateSlides();
swiper.updateProgress();
swiper.updateSlidesClasses();

swiper.scrollbar.updateSize();
swiper.scrollbar.setTranslate();
swiper.scrollbar.setTransition();

With the above said, I found that if the browser window is resized the draggable area is given a width value and the scrollbar shows again as expected.  Is there any way to trigger a 'resize' check on swiper as a workaround to this?

observeParents: true, seemed to do the trick and is working now.


distribution has a perl prereq of 5.021008

This is because [MinimumPerl] is finding something interesting in one of the css files.
To exclude it, you need to modify MinimumPerl with a custom filefinder:
[FileFinder::Filter / TestFiles_no_CSS]
finder = :TestFiles
skip = \.css$

[MinimumPerl]
test_finder = TestFiles_no_CSS

However, since [MinimumPerl] is being brought in through your plugin bundle, you need to do things a little differently: modify your bundle to compose the Dist::Zilla::Role::PluginBundle::PluginRemover and Dist::Zilla::Role::PluginBundle::Config::Slicer roles, then do this in dist.ini:
; define the filefinder as before
[@IDOPEREL]
MinimumPerl.test_finder = TestFiles_no_CSS

Thanks for the info. Just a question though, I don't see where the distribution is showing perl 5.021008 as the minimum required version. Both the Makefile.PL and the META.json file show 5.006.

Running 'dzil build' on the repository at the time I created the issue would result in a perl prereq of 5.021008, because the .css file was being scanned by the [MinimumPerl] plugin.
You can see it directly by running perlver --blame on the file.


Ability to add a new file (file metadata) in ingest

In order to update projects which initially did not include the file metadata for a particular file (e.g. gene expression matrix file, fastq file), we need to be able to add a new file (file metadata) to a submission in ingest.
We can currently add new protocols or biomaterials for example, not there is not an  "Add file" button.
An example dataset where this is needed:
https://github.com/ebi-ait/hca-ebi-wrangler-central/issues/624

Hey other wranglers, can you please advise if you have come across such a scenario?
@ESapenaVentura @Wkt8 @idazucchi

It would be useful, but I think we have an alternate route of creating new submissions (which I believe fits this use case of contributors coming back and relaying new information) to add a new file in ingest


[Docs] Add descriptive error message for augmentColor failure

[x] I have followed (at least) the PR section of the contributing guide.

This should close #20288 by adding a more descriptive error message.
Below are a couple changes to the proposed solution #20288 (comment). First is adding name as a parameter of augmentColor() because it wasn't declared in local scope. Second is adding name: 'secondary' when the function is called on the secondary color. This change to the required augmentColor() parameters is reflected in modified tests as well.
diff --git a/packages/material-ui/src/styles/createPalette.js b/packages/material-ui/src/styles/createPalette.js
index fa53482ca..c17ebaf99 100644
--- a/packages/material-ui/src/styles/createPalette.js
+++ b/packages/material-ui/src/styles/createPalette.js
@@ -154,7 +154,7 @@ export default function createPalette(palette) {
     return contrastText;
   }

-  const augmentColor = ({color, mainShade = 500, lightShade = 300, darkShade = 700}) => {
+  const augmentColor = ({color, name, mainShade = 500, lightShade = 300, darkShade = 700}) => {
     color = { ...color };
     if (!color.main && color[mainShade]) {
       color.main = color[mainShade];
@@ -218,6 +218,7 @@ export default function createPalette(palette) {
       // The colors used to represent secondary interface elements for a user.
       secondary: augmentColor({
         color: secondary,
+        name: 'secondary',
         mainShade: 'A400',
         lightShade: 'A200',
         darkShade: 'A700',

Hold up.. Those name isn't a required parameter because it is destructured within function parameters. I've modified the tests accordingly.

@reedanders Thanks


Maven Central repository is down or unavailable

Plugin Repository in Maven Central is unavailable
https://mvnrepository.com/artifact/com.saveourtool.diktat
I can't download the plugin in my Android project
org.gradle.api.plugins.UnknownPluginException: Plugin [id: 'com.saveourtool.diktat.diktat-gradle-plugin', version: '1.2.5', apply: false] was not found in any of the following sources:

Gradle Core Plugins (plugin is not in 'org.gradle' namespace)
Plugin Repositories (could not resolve plugin artifact 'com.saveourtool.diktat.diktat-gradle-plugin:com.saveourtool.diktat.diktat-gradle-plugin.gradle.plugin:1.2.5')
Searched in the following repositories:
Google
MavenRepo
Gradle Central Plugin Repository

Hey, 1.2.5 is still in org.cqfn. We are now in process of changing the namespace: https://mvnrepository.com/artifact/org.cqfn.diktat/diktat-gradle-plugin/1.2.5


Sys: Executor: Don't wake all futures immediately

Futures are responsible for waking themselves.

see #345 for details


Propose new language.

Hello, can i create make new language? "Ślōnskŏ gŏdka"
https://en.wikipedia.org/wiki/Silesian_language
It's a local dialect.
Language code is 'SZL'.

If that is a dialect of polish, then it would be pl-SZL?
Yes, you can do that, through a PR to the translations repo.


Implement Encoding.Bin fields

https://vega.github.io/vega-lite/docs/bin.html

@datamusing ok for Roger to work on this one too? Trying to share load around given deadline approaching.

This example plot needs Bin. A good one to shoot for for this issue.
https://vega.github.io/vega-editor/?mode=vega-lite&spec=scatter_binned


English pedantry - "Lighted" -> "Lit"

This is technically a matter of opinion so you're welcome to discard this if you like, I just notice it every time I play.

If I where to change that, I'd have to also change the mod name or the inconsistency would annoy me forever.
Besides only the oxford dictionary doesn't fully agree with lighted as synonym for illuminated:
https://www.oxfordlearnersdictionaries.com/definition/english/lighted?q=lighted
https://en.wiktionary.org/wiki/lighted
https://www.dict.cc/?s=lighted

Fair enough, I can accept that - figured I'd see what your thoughts were.


Option to not collapse search results

In search results view, if a file has many results its node appears collapsed. There should be an option to disable that or specify a number of results over which the node will be collapsed.
Many times I run a search with many results across many files and think I'm looking at all the results in front of me, but it turns out I missed a collapsed node in the middle with many results underneath. It's very easy to miss so I want to disable that feature.

Just got a request for the opposite :)
This would cover customizing the collapse behavior in the search view: https://github.com/Microsoft/vscode/issues/48641


Use lib prefix in target_name is dropped when naming .node file

Node Version: node: 12.18.1 npm: 6.14.5
Platform: macOS 10.15.2
Compiler: clang 11.0.3
Module: node-gyp 7.0.0

I'm not having any issues building or getting node-gyp to work. I am experiencing some weirdness, where the opening chars of my target_name are dropped in the outputted binary file. I'm using a target_name of lib{REST_OF_NAME}.
The lib part of my target name is dropped in the outputted .node file. In my lib{REST_OF_NAME}.target.mk file, the lib is dropped in lines like:
$(builddir)/{REST_OF_NAME}.node: GYP_LDFLAGS := $(LDFLAGS_$(BUILDTYPE))
$(builddir)/{REST_OF_NAME}.node: LIBS := $(LIBS)
$(builddir)/{REST_OF_NAME}.node: GYP_LIBTOOLFLAGS := $(LIBTOOLFLAGS_$(BUILDTYPE))
$(builddir)/{REST_OF_NAME}.node: TOOLSET := $(TOOLSET)
$(builddir)/{REST_OF_NAME}.node: $(OBJS) FORCE_DO_CMD
	$(call do_cmd,solink_module)

I see the desired name in lines like:
TARGET := lib{REST_OF_NAME}
DEFS_Debug := \
	'-DNODE_GYP_MODULE_NAME=lib{REST_OF_NAME}' \

Is there some feature I need to switch on, or some reason that a target cannot have a prefix of lib? If I put an underscore or some other character in front of lib it works. Normally I'd just rename my project and move on, but I am wrapping an existing library and can't change the name.

Hello. I just came accross the same problem. I don't have a solution but a workaround:
You can perform actions after the build by adding an build item with type "none" and an actions section.
I have this from this bindings.gyp example file: binding.gyp
My example looks like this:
{
    'target_name': 'action_after_build',
    'type': 'none',
    'dependencies': [ "name of last item" ],
    'conditions': [
        ['OS=="linux"', {
            'actions': [{
            'action_name': "copylib",
            'inputs': [
                '<@(PRODUCT_DIR)/mylib.so'
            ],
            'outputs': [
                "<@(PRODUCT_DIR)/libyasdi_drv_serial.so"
            ],
            'action': ['cp', "<@(PRODUCT_DIR)/mylib.so", "<@(PRODUCT_DIR)/libmylib.so"]
            }]
        }]
    ]
}

The inputs and outputs sections seem to be required. I added the name of the last created item (or which at least in my optionion will be generated at last). So that this item will be the very last. It worked on my first try so I dont know if this is correct. It is also placed at the end of the gyp file.


2.13 documentation update

There's nothing to do here. gh-pages and the 213 branch are the same - all the commits to 213 were also committed to gh-pages.


Question/bug: Fusion reactor turns off after server restart and needs reignition

Hey there! I love this mod and really enjoy building the infrastructure (and complexity) for getting fusion reactors up and running.
Background: I have a H-H fusion reactor (toroid size 3) up and running in MC Eternal. My friend and I are using a hosted server which restarts in the middle of the night each day. When I sign in the next day after a restart, when fusion was up and running in the 90's for efficiency before the restart, I noticed the reactor was back to square one for fusion (i.e. temperature was at 0 and my ender energy conduits had all been disconnected from the bottom of the machine).
Just to clarify that my setup is correct: yes, I have plenty of hydrogen being generated (more than I need), plenty of power to get the reactor to be self-sustaining for the electromagnets, and 5000 k/t for active cooling with water connected and working as expected. My entire base is also chunk loaded so none of the machines should ever turn off.
As I mentioned, the reactor works great, but I'm a little concerned about having to restart the reactor every time the server restarts.
Is this a known issue on server restart?

Just a note on this, I made a  second reactor for deuterium and am still experiencing the issue. It seems to be primarily with the connections after the server restarts. I first noticed with the ender energy conduits and also have the same problem with cryo-stabilized fluxducts. If I remove the connecting cable and replace it, then power is correctly pulled into the fusion reactor and it automatically restarts.

Did you ever solve this issue ? I think I'm experiencing the same on an MC Eternal server. Today reactor was humming along at 82% when I logged off for dinner. Logged back on after an hour, and it had dropped to almost 0 efficiency. Full tanks of hydrogen, 100% active cooling, no redstone signal on core, magnets powered from huge induction matrix. Haven't found a solution yet......

Did you ever solve this issue ? I think I'm experiencing the same on an MC Eternal server. Today reactor was humming along at 82% when I logged off for dinner. Logged back on after an hour, and it had dropped to almost 0 efficiency. Full tanks of hydrogen, 100% active cooling, no redstone signal on core, magnets powered from huge induction matrix. Haven't found a solution yet......

I never did. I started to get bored after spending too much time in my server and this issue made me quit since it was my primary power source. I eventually made two chained reactors then one and the other both stopped working after server restarts. I decided it was way to much work to keep destroying and recreating the reactors.  I'm pretty sure it had to do with things not automatically reconnecting on server restart. Even the fluxducts had to be removed and re-added to connect again to the reactors.

I never did. I started to get bored after spending too much time in my server and this issue made me quit since it was my primary power source. I eventually made two chained reactors then one and the other both stopped working after server restarts. I decided it was way to much work to keep destroying and recreating the reactors.  I'm pretty sure it had to do with things not automatically reconnecting on server restart. Even the fluxducts had to be removed and re-added to connect again to the reactors.

I understand. Thanks for the update 👍

I understand. Thanks for the update 👍

@znorman17 Unfortunately I was never able to work out why this happened for some people. Sorry for the inconvenience!


recursive persistent ZK watch

Seeing accumulation of persistent watches, we probably want to remove the watch at here as well
https://github.com/cowpaths/fullstory-solr/blob/3fb37d5df7161a8210eafc72e177c3581b768b90/solr/solrj-zookeeper/src/java/org/apache/solr/common/cloud/ZkStateReader.java#L2161


[youtube-banner]

banner with link to youtube videos

Looks good. When your requests are satisfied @JuroUhlar we can merge it. 👍


CASMINST-5025: Create more shared functions for automated scripts; prove methods for determing NCN lists

Summary and Scope
TL;DR

Create common function to determine if script is running on the PIT node; update other scripts to call it.
Create common function to generate list of NCNs; update other scripts to call it.
Update goss-k8s-nodes-age-valid and goss-k8s-nodes-joined-cluster tests so they realize ncn-m001 is not in the cluster if they are running on the PIT node.
Update value of kubectl variable for the PIT node
Create common goss variable file for variables with same value between PIT and NCN; Modify RPM builder so that it generates NCN/PIT variable files by combining common file with PIT/NCN file.
Moved a couple of common functions into the common function library.
General linting and cleanup to make the scripts more consistent.

Details
This ticket began just as a fix to a problem being seen on the surtur install, where the dnsmasq statics file had been deleted from the PIT node at some point, which caused the csm-testing scripts to assume that it was a normal NCN. This caused other problems.
While there is no surefire way to determine the node identity if someone may be going around changing things in the environment (like deleting the dnsmasq file), it seems better to key off something like the pit-release file regardless. So this PR was originally going to make that change. But then I realized that there was code all across the automated scripts that was deciding whether or not the particular script was running on the PIT node. So I used this PR to change all of those to instead use a shared function for this, so we don't play whack-a-mole when individual scripts mess up.
In the process of doing that, I also noticed some other code that could be made common, in order to make the scripts more consistent and less error prone. And I realized that if we were assuming that the dnsmasq file may not be there, then our code for making a list of NCNs would need to change. And this is code which existed in different forms in several places. So another common function I created was one to get the list of NCNs on the system (either all of them, or particular types, with an option to exclude the PIT).
In the process of testing this, I discovered that a couple of Kubernetes checks were being made for ncn-m001 even though the test was running from the booted PIT node. So I modified those tests to omit ncn-m001 when executing on the PIT node.
While doing all of that, I tried to do other minor cleanup, linting, etc, to make the scripts more consistent in appearance and convention.
And finally, I noticed on surtur today that path for kubectl on the PIT node had changed, which tripped some of the goss tests up, so I am correcting that here as well. When doing that, I noticed that we had a fair number of variables which were in common from NCNs and LiveCDs. So I created a common variables file with the shared values, and then added a little code in the RPM builder to have it create the installed variable files based on a merger of the PIT/NCN variable file and the common variable file.
Issues and Related PRs
https://jira-pro.its.hpecorp.net:8443/browse/CASMINST-5025
Testing
I tested the changes on surtur by running all of the automated scripts on both the PIT node and on other NCNs. In addition, I made sure that the updated goss service script file was correctly populating the variable file and starting the servers.
Risks and Mitigations
Moderate risk in the sense that a lot of code was touched. But the result is a much more maintainable situation than we had before, so even if problems are found that eluded my testing on surtur, it should be much easier to correct them.
Pull Request Checklist

[X] License file intact
[X] Target branch correct
[X] Testing is appropriate and complete, if applicable

Good changes overall, and these look to be tested so I approved.

The RPMs for this are currently installed on surtur (all NCNs and PIT), if anyone wants to check anything in particular.


NIFI-12700: refactored PutKudu to optimize memory handling for AUTO_F…

…LUSH_SYNC flush mode (unbatched flush)

Introduced PutKuduResult to store results of processing FlowFiles in PutKudu.
Introduced two implementations for PutKuduResult, namely AutoFlushSyncPutKuduResult and StandardPutKuduResult. AutoFlushSyncPutKuduResult includes optimizations considering it's an un-batched flush. StandardPutKuduResult encapsulates all the logic that was used to store the results for processing FlowFiles in the existing implementation.
Refactored AbstractKuduProcessor to separate out the closeKuduSession and flushKuduSession functionality.
Refactored PutKudu to utilize the new PutKuduResult class.

Summary
NIFI-12700
Tracking
Please complete the following tracking steps prior to pull request creation.
Issue Tracking

[x] Apache NiFi Jira issue created

Pull Request Tracking

[x] Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
[x] Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000

Pull Request Formatting

[x] Pull Request based on current revision of the main branch
[x] Pull Request refers to a feature branch with one commit containing changes

Verification
Please indicate the verification steps performed prior to pull request creation.
Build

[x] Build completed using mvn clean install -P contrib-check

[x] JDK 21

Licensing

[ ] New dependencies are compatible with the Apache License 2.0 according to the License Policy
[ ] New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

[ ] Documentation formatting appears as expected in rendered files

Will review...

Reviewing...

Verified the requested changes were made. +1 LGTM, thanks for the improvement! Merging to main


Testing V4 Beta-7: Module build failed: Error: Can't resolve<EMAIL_ADDRESS>

Bug Report
Ionic Info
Run ionic info from a terminal/cmd prompt and paste the output below.
Ionic:

   ionic (Ionic CLI)          : 4.1.1 (C:\Users\peter\AppData\Roaming\npm\node_modules\ionic)
   Ionic Framework            : @ionic/angular 4.0.0-beta.7
   @angular-devkit/core       : 0.7.5
   @angular-devkit/schematics : 0.7.5
   @angular/cli               : 6.1.5
   @ionic/ng-toolkit          : 1.0.7
   @ionic/schematics-angular  : 1.0.5

Cordova:

   cordova (Cordova CLI) : 8.0.0
   Cordova Platforms     : none
   Cordova Plugins       : no whitelisted plugins (0 plugins total)

System:

   NodeJS : v8.11.3 (C:\Program Files\nodejs\node.exe)
   npm    : 6.4.0
   OS     : Windows 10

Describe the Bug
Fail to compile
[ng] chunk {121} 121.js, 121.js.map () 8.11 kB  [rendered]
[ng] chunk {122} 122.js, 122.js.map () 5.15 kB  [rendered]
[ng] chunk {123} 123.js, 123.js.map () 9.87 kB  [rendered]
[ng] chunk {124} 124.js, 124.js.map () 4.67 kB  [rendered]
[ng] chunk {125} 125.js, 125.js.map () 1.8 kB  [rendered]
[ng] chunk {126} 126.js, 126.js.map () 1.03 kB  [rendered]
[ng] chunk {127} 127.js, 127.js.map () 3.49 kB  [rendered]
[ng] chunk {128} 128.js, 128.js.map () 7.29 kB  [rendered]
[ng] ERROR in ./src/global.scss (./node_modules/raw-loader!./node_modules/postcss-loader/lib??embedded!./node_modules/sass-loader/lib/loader.js??ref--15-3!./src/global.scss)
[ng] Module build failed: Error: Can't resolve<EMAIL_ADDRESS>in 'C:\ae\adaept.com\aeion4\src'
[ng]     at doResolve (C:\ae\adaept.com\aeion4\node_modules\enhanced-resolve\lib\Resolver.js:180:19)
[ng]     at hook.callAsync (C:\ae\adaept.com\aeion4\node_modules\enhanced-resolve\lib\Resolver.js:238:5)
[ng]     at _fn0 (eval at create (C:\ae\adaept.com\aeion4\node_modules\tapable\lib\HookCodeFactory.js:24:12), <anonymous>:15:1)
[ng]     at resolver.doResolve (C:\ae\adaept.com\aeion4\node_modules\enhanced-resolve\lib\UnsafeCachePlugin.js:37:5)
[ng]     at hook.callAsync (C:\ae\adaept.com\aeion4\node_modules\enhanced-resolve\lib\Resolver.js:238:5)
[ng]     at _fn0 (eval at create (C:\ae\adaept.com\aeion4\node_modules\tapable\lib\HookCodeFactory.js:24:12), <anonymous>:15:1)
[ng]     at hook.callAsync (C:\ae\adaept.com\aeion4\node_modules\enhanced-resolve\lib\Resolver.js:238:5)
[ng]     at _fn0 (eval at create (C:\ae\adaept.com\aeion4\node_modules\tapable\lib\HookCodeFactory.js:24:12), <anonymous>:12:1)
[ng]     at resolver.doResolve (C:\ae\adaept.com\aeion4\node_modules\enhanced-resolve\lib\DescriptionFilePlugin.js:42:38)
[ng]     at hook.callAsync (C:\ae\adaept.com\aeion4\node_modules\enhanced-resolve\lib\Resolver.js:238:5)
[ng]     at _fn5 (eval at create (C:\ae\adaept.com\aeion4\node_modules\tapable\lib\HookCodeFactory.js:24:12), <anonymous>:57:1)
[ng]     at resolver.doResolve (C:\ae\adaept.com\aeion4\node_modules\enhanced-resolve\lib\ModuleKindPlugin.js:23:37)
[ng]     at hook.callAsync (C:\ae\adaept.com\aeion4\node_modules\enhanced-resolve\lib\Resolver.js:238:5)
[ng]     at _fn0 (eval at create (C:\ae\adaept.com\aeion4\node_modules\tapable\lib\HookCodeFactory.js:24:12), <anonymous>:15:1)
[ng]     at hook.callAsync (C:\ae\adaept.com\aeion4\node_modules\enhanced-resolve\lib\Resolver.js:238:5)
[ng]     at _fn1 (eval at create (C:\ae\adaept.com\aeion4\node_modules\tapable\lib\HookCodeFactory.js:24:12), <anonymous>:24:1)
[ng] i ｢wdm｣: Failed to compile.

Steps to Reproduce
Steps to reproduce the behavior:
Manual upgrade to Beta-7
Related Code
If you are able to illustrate the bug with an example, please provide a sample application via an online code collaborator such as StackBlitz, or GitHub.
Expected Behavior
Working app.
Additional Context
List any other information that is relevant to your issue. Stack traces, related issues, suggestions on how to fix, Stack Overflow links, forum links, screenshots, OS if applicable, etc.
Some theme color updates here:
https://github.com/ionic-team/ionic/commit/096d9a76f3ec62711913d14326b7734739c1c734
but I do not know if it is related.

Not sure if i understand the error here but i'll put my 2 cents in. In beta.5 i believe, colors was merged inside the global/core css file and no longer needs to be imported. Check out https://github.com/ionic-team/ionic/releases for breaking changes

This is indeed merged into core.css, see https://github.com/ionic-team/ionic/releases/tag/v4.0.0-beta.6

According the changelog this import should be removed.

@aldaircruz is right.

@aldaircruz etc.
That was the smoking gun! Thanks.


direct.fen.json outdated for FEN v1.18.21

direct.fen.json does no longer work for TV shows with the latest version of FEN (1.18.21). As a result, the following error is produced (see also the attached file). Unfortunately, I do not know how to update this.
2020-12-06 11:07:02.570 T:5848   ERROR: EXCEPTION Thrown (PythonToCppException) :
-->Python callback/script returned the following error<--

NOTE: IGNORING THIS CAN LEAD TO MEMORY LEAKS!
Error Type: <type 'exceptions.AttributeError'>
Error Contents: Sources instance has no attribute 'season'
Traceback (most recent call last):
File "C:\Kodi\portable_data\addons\plugin.video.fen\resources\lib\fen.py", line 5, in
routing(argv[2])
File "C:\Kodi\portable_data\addons\plugin.video.fen\resources\lib\modules\router.py", line 114, in routing
Sources().playback_prep(params)
File "C:\Kodi\portable_data\addons\plugin.video.fen\resources\lib\modules\sources.py", line 69, in playback_prep
else: self._grab_meta()
File "C:\Kodi\portable_data\addons\plugin.video.fen\resources\lib\modules\sources.py", line 514, in _grab_meta
episodes_data = tikimeta.season_episodes_meta(self.meta['tmdb_id'], self.meta['tvdb_id'], self.season,
self.meta['tvdb_summary']['airedSeasons'], self.meta['season_data'], meta_user_info)
AttributeError: Sources instance has no attribute 'season'
-->End of Python script error report<--
2020-12-06 11:07:25.715 T:12952  NOTICE: Stopping player

kodi.log

I did notice yesterday as well same issue Doesn’t work with TV shows I get the same exact error as posted above

Maybe @tikipeter would have a look?

@drinfernoo
This has just been fixed (issue with Fen, not the player).


Max_Temp looks incorrect

Hi Adam,
For certain stations, the data(TMAX) seems incorrect. When I view the data for a specific year for these particular stations using the web tool, I get different data .
For e.g. for the station, RIVERSIDE FIRE STATION 3, CA US (GHCND:USC00047470), I am getting
TMAX in range of 200, which seems incorrect. I get different results when queried from web
(https://www.ncdc.noaa.gov/cdo-web/datasets/GHCND/stations/GHCND:USC00047470/detail).
#Example
from datetime import date
from pyncei.reader import NCEIReader
import datetime as dt
import csv
import pandas as pd
token = '##############'
ncei = NCEIReader(token,encode_queries=False)
mindate = '1970-01-01'  # either yyyy-mm-dd or a datetime object
maxdate = dt.datetime.today().strftime("%Y-%m-%d")
datatypes = ['TMAX']
dataset = 'GHCND'
minyear = int(mindate[:4])
year = date.today().year
val='GHCND:USC00047470'
ncei.get_data(dataset=dataset,
station=val,
datatype=datatypes,
startdate=date(1990, 1, 1),
enddate=date(1990, 12, 31))
There are several other stations for which the data seems incorrect.
Thanks

Hi Adam,
Could you kindly tell what could be the reason for this difference.
Thanks

This has to do with the how the NCEI data endpoint returns data if no units keyword is specified. I’ve added that keyword to the get_data() method. It accepts either ‘standard’ or ‘metric’. I think that should solve your issue, but let me know if not.
Thanks!
Adam
From: Amandeep Singh<EMAIL_ADDRESS>Sent: Thursday, April 20, 2017 7:06 AM
To: adamancer/pyncei<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: Re: [adamancer/pyncei] Max_Temp looks incorrect (#2)
Hi Adam,
Could you kindly tell what could be the reason for this difference.
Thanks
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/adamancer/pyncei/issues/2#issuecomment-295445362, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AOMCeEb6OL31mUqC-_A2uaCS2nzzmja_ks5rxnjWgaJpZM4NBD6R.

Hi Adam,
It works now.
Thanks


setup with zero to cloud

Try get a docker setup with the other zero to cloud examples working.

Initial version for zero to cloud in my fork:
https://github.com/brharrington/zerotocloud/
Still remaining to do:

I restricted the security settings so it wasn't so wide open. Need to update the previous sections docs.
Need to document creating the updated baseami with java8. Unfortunately there is no default java8 package for trusty.
Configure the eureka and edda apps to publish data using @dmuino 's plugin (https://github.com/dmuino/atlas-oss-plugin). Also need to find a better home for the plugin.
One-JAR's class loaders don't play well with guice, but we still want a simple mode to test with a single jar. Trying a simple alternative that ships as single jar and just has a minimal class to extract and then setup a URLClassLoader.
Configure a distributed setup and document all the config options.


Refresh data when switching to live view

Is your feature request related to a problem? Please describe.
When switching the recent blocks page to live view, it will leave out blocks that have shown up since the last refresh of the page. For example, in the screenshot below, I opened the page at block 35, then blocks 36, 37, and 38 arrived. During block 38, I switched on live view, so 39 and 40 showed up in the list when they were confirmed.
Describe the solution you'd like
It would be great if switching on live view first refreshed the data, so that there is no unusual skipped block behavior like this.
Describe alternatives you've considered
Users can just manually refresh and then flip the switch, but I could definitely see this confusing someone, so if it is not too hard to fix, would be worth the effort.
Additional context

:tada: This issue has been resolved in version 1.136.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Set up the development environment

Set up the Development Environment
As a developer
I need a fully configured development environment
So that I can build, test, and deploy the microservice efficiently
Details and Assumptions
Use Docker containers for consistent development environments.
Ensure all necessary dependencies and development tools are available.
Given I have access to the repository
When I clone the repository and run the setup script
Then the development environment should be configured with all dependencies installed


Invalid argument(s): A directory corresponding to fileSystemPath "...jaspr/experiments/minimal_app/lib/web" could not be found

I've checked out wip/v0.2 branch and whenever trying to run main.dart within the lib folder I end up seeing the following error.
Unhandled exception:
Invalid argument(s): A directory corresponding to fileSystemPath ".../jaspr/experiments/minimal_app/lib/web" could not be found
#0      createStaticHandler (package:shelf_static/src/static_handler.dart:50:5)
#1      staticFileHandler (package:jaspr/src/server/server_app.dart:273:7)
#2      staticFileHandler (package:jaspr/src/server/server_app.dart)
#3      _createHandler (package:jaspr/src/server/server_app.dart:278:38)
#4      ServerApp._run.<anonymous closure> (package:jaspr/src/server/server_app.dart:120:21)
#5      ServerApp._run.<anonymous closure> (package:jaspr/src/server/server_app.dart:117:22)
#6      new Future.microtask.<anonymous closure> (dart:async/future.dart:276:37)
#7      _microtaskLoop (dart:async/schedule_microtask.dart:40:21)
#8      _startMicrotaskLoop (dart:async/schedule_microtask.dart:49:5)
#9      _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:122:13)
#10     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:193:5)

I've noticed this same issue on master branch and have moved the main.dart file up 1 directory so it is located at ...jaspr/experiments/minimal_app/main.dart instead of ...jaspr/experiments/minimal_app/lib/main.dart which lets me run the project although I'm not sure if there's a reason not to do this

Are you running the main.dart file directly? Because this wouldn't work. You should always use jaspr serve.

Yup I'm running the main.dart file directly, my bad!
Tried running it with jaspr serve and this is the result
Starting jaspr development server...
The Dart VM service is listening on http://<IP_ADDRESS>:8181/EI7Tq9drx3w=/
The Dart DevTools debugger and profiler is available at: http://<IP_ADDRESS>:8181/EI7Tq9drx3w=/devtools/#/?uri=ws%3A%2F%2F<IP_ADDRESS>%3A8181%2FEI7Tq9drx3w%3D%2Fws
lib/main.dart:1:8: Error: Error when reading '../../../../../.pub-cache/hosted/pub.dartlang.org/jaspr-0.1.5/lib/server.dart': No such file or directory
import 'package:jaspr/server.dart';
       ^
lib/app.dart:5:2: Error: Undefined name 'app'.
@app
 ^^^
lib/app.dart:5:2: Error: This can't be used as an annotation; an annotation should be a reference to a compile-time constant variable, or a call to a constant constructor.
@app
 ^
lib/counter.dart:4:2: Error: Undefined name 'island'.
@island
 ^^^^^^
lib/counter.dart:4:2: Error: This can't be used as an annotation; an annotation should be a reference to a compile-time constant variable, or a call to a constant constructor.
@island
 ^
lib/main.dart:9:7: Error: Undefined name 'StyleRule'.
      StyleRule.import('https://fonts.googleapis.com/css?family=Roboto'),
      ^^^^^^^^^
lib/main.dart:11:40: Error: Undefined name 'Selector'.
        selector: const Selector.list([Selector.tag('html'), Selector.tag('body')]),
                                       ^^^^^^^^
lib/main.dart:11:49: Error: Method invocation is not a constant expression.
        selector: const Selector.list([Selector.tag('html'), Selector.tag('body')]),
                                                ^^^
lib/main.dart:11:62: Error: Undefined name 'Selector'.
        selector: const Selector.list([Selector.tag('html'), Selector.tag('body')]),
                                                             ^^^^^^^^
lib/main.dart:11:71: Error: Method invocation is not a constant expression.
        selector: const Selector.list([Selector.tag('html'), Selector.tag('body')]),

I initially thought that the pubspec.yaml for the example project might be outdated and that it might need to use the jaspr packages located within the repo and so I added this at the bottom of my pubspec.yaml
dependency_overrides:
  jaspr:
    path: ../../packages/jaspr
  jaspr_builder:
    path: ../../packages/jaspr_builder

This resulted in the same error message as the opening post.

Yeah this seems to be some version mismatch with the new version.
Generally when not using the released version, better do dart run jaspr serve since this then uses the version defined for the project instead of the globally activated version.
And the pubspec_overrides.yaml should work when they point to the right paths, but only if you are on dart >=2.17.

I've now got the minimal_app launching! Thanks!
However when clicking on the buttons, they aren't doing anything. Want me to open a separate issue for this? What's the best way to debug this issue?

I don't think this makes sense, the experiments and example aren't all updated to the new version yet, It's still all work in progress.


Unable to retain decimal point in unmasked value

Hi Robin,
love the plugin!
qq on logic for removal of decimal mask.
e.g. I have following mask within document.ready function:
$('#myInputField').inputmask("$9,999,999.99", {numericInput: true} );
Input field will display correct mask as set above  and e.g. if user enters 3.33 then entered value will be $,__,__3.33.
On a test button click,  I want to retrieve unmasked value as 3.33. For that, I coded this to remove the mask within onclick event handler:  $('#myInputField').inputmask('remove');
My issue is, upon removal of input mask, value results to be 333. I lost decimal point (but I want to be able to get value as 3.33. i.e. retain decimal point).
I see pointers to use onunmask function. I will try that out and post the update if successful. In the mean time, if you can provide any guidance, will appreciate the help. Thanks!

@mnrfeb19 ,
The onunmask provides you with the maskedvalue and unmaskedvalue.  You can manipulate the output to suite you needs.


cmd/compile: failure to diagnose re-declaring dot-imported identifiers

This program should fail to compile with an error that Index was already declared due to dot-importing package bytes: https://play.golang.org/p/EAPSJQRfm2F
go/types and gccgo correctly diagnose this; cmd/compile does not.

this dot-imported  identifiers   diagnose ,  not often  use. and it's not very consistent with the concept of go.

@KeKe-Li Sorry, I don't follow.
The Go spec defines how import declarations should behave: https://golang.org/ref/spec#Import_declarations. go/types and gccgo are correctly implementing that for the linked program. cmd/compile is not.

@mdempsky seems that we don't check for re-declared when processing VarDecl in noder.go?

@cuonglm I think we weren't setting Block correctly for the imported symbols, so importdot didn't set it correctly for the local aliases, and so declare didn't recognize it as a redeclaration.
I have fixes for a bunch of these dot-import issues. Just polishing up the CLs to get ready for upload.

@cuonglm I think we weren't setting Block correctly for the imported symbols, so importdot didn't set it correctly for the local aliases, and so declare didn't recognize it as a redeclaration.
I have fixes for a bunch of these dot-import issues. Just polishing up the CLs to get ready for upload.

Ah right, seems that s.Block should be changed to types.Block in importdot.

Fixed on dev.regabi.

Fixed on dev.regabi.


Patch Teleport for reliability

Adonis sometimes lags out and players sit right on a seat again causing the anchored seat to teleport with the player.

Might be better to look for welds to parts related to the character rather than clearing all children in the seat. If the seat, for instance, had a mesh or something in it this would delete that.

That should be better?

If the seat is welded to another object, and the weld is inside of the seat, the current method will remove that weld.


Lab 13 Use tools to optimize Power BI performance

Lab title: Use tools to optimize Power BI performance
Task: Load BPA Rules
Step: 02
Description of issue
The instruction says, "To load the BPA rules, select the Advanced Scripting tab" whereas, on the Tabular Editor, it's called "C# Scripting" and not "Advanced Scripting"
Repro steps:

Thanks for pointing this out @pnk1119. The labs were created with an older version of Tabular Editor, which was labeled slightly differently. I've updated the instructions to reflect the changes in the latest version of Tabular Editor.


Include VisualStringDistances.jl for CI

We should include https://github.com/ericphanson/VisualStringDistances.jl in CI.

Also some edit distance from https://github.com/matthieugomez/StringDistances.jl, probably Damerau-Levenshtein.

Definitely. I think @ericphanson has worked on this at some point

Moving this to RegistryCI.jl


LocalVideoSource error missing namespace in UWP Build

Hi, when I try to build for in UWP for hololens in console I get several errors regarding the LocalVideoSource namespace, I can ask which step I skipped or if I am missing some reference in the project.

Unity 2019.2.21f1, VS 2019, NuGet packages 1.0.3, WebRTC sources from latest release branch, MRTK 2.3.0

Thank you so much for your attention, availability and patience

See #165, this was fixed on master with 243e629b506982cdafaac62f4a6157134b9807f3.

Thanks a lot, problem solved. Also I wanted to apologize, next time I will try better before making a duplicate of the same issue.

Not to worry. It's easier for me to know it's a duplicate than for you to search for it 😉


Accessibility enhancements

Hey y'all, I wanted to put in this request to see if two minor adjustments could be made to improve accessibility of the text in the Nudge prompt window.

"Important Notes" text. It's currently red which can cause challenges for readers that are colorblind. It may take some experimentation to find the right shade that works against the background for both light mode and dark mode (I'd imagine blue for light mode and orange for dark mode would be good options that would maintain a high enough contrast to be more easily readable).
Apple has some documentation on color for visual design and accessibility here:
https://developer.apple.com/design/human-interface-guidelines/macos/visual-design/color/
https://developer.apple.com/design/human-interface-guidelines/accessibility/overview/color-and-contrast/
There are some other handy resources out there too, like:
https://uxdesign.cc/color-blindness-in-user-interfaces-66c27331b858
and Xcode has its own built-in accessibility inspector:
https://zonneveld.dev/accessibility-inspector/

Improving contrast ratio in sidebar text. The integer column (where the required/current OS version, days, deferred counts reside) doesn't meet the standard 4.5 to 1 contrast ratio recommendation for accessibility. Should be a relatively simple color tweak to improve the ratio (something the Xcode accessibility checker can check).

There are other things that the accessibility checker may flag (e.g., spacing, element layouts) but I think focusing on font colors and contrast is a great place to start.
Happy to talk through this further with anyone that has the cycles to look into this. 💙

As a red/green colorblind person, the red one is interesting to me. I've never seen an issue with it and I'm very sensitive to it since red is one of my worst colors that I can see.
As for contrast ratio, could you potentially show in a screenshot what exactly you mean?

Maybe it is possible that we get a preference key to determine the color? So that you can enter a hex value?
// mainContentNote
HStack {
Text(mainContentNote)
.font(.callout)
.fontWeight(.bold)
.foregroundColor(Color.red)
Spacer()
}

@bartreardon would know :)

yeah, that's easy to do - If you want you can specify hex value or one of the built in colours. I have code that can do that. happy to do a PR.

something like that?

So it occurs to me that specifying hex will be literal. When using the colour names, although limited they should adjust according to colour accessibility https://developer.apple.com/design/human-interface-guidelines/macos/visual-design/color/

So I have some thoughts.
I believe I have address point 1 with the following:
https://www.hackingwithswift.com/books/ios-swiftui/supporting-specific-accessibility-needs-with-swiftui
https://davidmathlogic.com/colorblind/#%23D81B60-%231E88E5-%23FFC107-%23004D40
By setting the following in accessibility

it will look like this

vs this

For point 2, again by setting the following in accessibility

it will look like this

I'm going to make an executive decision if I don't hear back soon. I'm still waiting 8 days from my initial question and I personally believe these accessibility enhancements in https://github.com/macadmins/nudge/pull/323 will address the two concerns on this issue.
If I don't hear back by tomorrow, I'm going to merge this and close it.

I think the emphasize without color option that makes the font slightly bigger helps for sure. On the issue of contrast it has more to do with the degree of contracts between the font color and background color on the text itself. I'm struggling to get Xcode to compile the app locally so I can show you what I'm talking about, but if you go to View > Inspectors > Accessibility you should see results around what I'm talking about.

I'm struggling to understand here. The background color is the default swiftui background color and so is the font color. This implies that all swiftui applications would inherently have this issue of contrast.
If you look at the accessibility inspector itself, its font color RGB 37, 37, 37, which is identical to nudge's font color. The background color of accessibility showing a window is RGB 242, 242, 242 and Nudge is barely different (not sure why) if 243, 239, 243.

I'm not sure what I can do here except change the color itself and that likely presents more problems should apple in the future change the primary/secondary colors built into the OS.

I read up on this for ios and learned how to better use this tool.
From what I can tell there's only one element that doesn't match the 4.5 min ratio and that's the More Info button.

Actually I think I finally understand.

The integer column

FFS. Would help if I fully comprehended what you were saying in the beginning :)


MG - 7.2(.0) - Hardware Hiding Module - Is it needed?

From what I understood, hardware-hiding modules are for hiding extra IO devices (sensors, keyboard input, mouse input, internet connections, etc.). In other words, it would be wrappers around interactions with external (to the program) devices. I don't think you have any sort of hardware-hiding needs here, but if you did, it might also be good to note that Python's virtual machine and standard library will do the heavy lifting. I also ask this because you have written "Impl. By: NumPy - Python" for 7.3.1, but "OS" here.

Also, you had "Modules" in the section title, but I think you wanted the singular "Module" (?).

Dear Jason, 7.3.1 is about module M11, a sequence data structure. I use the Numpy library for creating arrays for joints and etc. OS implements M1 but Phyton implements M11. Also, Professor admitted that M11 is needed in my project :)


sorted nominated, qualified, and ranked playlist according to their respective dates from newest to oldest

untested, because it returns an exception for me on startup, but I don't see how this could be wrong

tested and works


SKBounceAnimation in Swift

It's not an issue, but do you guys have plans to port this code to Swift?

Nope, no plans.


Traefik HTTP redirection

I have installed tus via helm in a bare metal kuberntes cluster and I have created an ingress route TLS terminated and I can access it via HTTPS. Although, I've tested the upload process and when a client uploads a file in the Pod logs the request is being sent as HTTP.
[tusd] 2022/06/23 11:52:59 event="UploadCreated" id="2d9f1162d084d41842af83a7778da198" size="10051" url="http://tus-eia.scio.services:18102/files/2d9f1162d084d41842af83a7778da198"  [tusd] 2022/06/23 11:52:59 event="ResponseOutgoing" status="201" method="POST" path="" requestId=""
The client also returns a 404 error as indeed the HTTP route does not exist.
raise TusCommunicationError(msg, resp.status_code, resp.content) tusclient.exceptions.TusCommunicationError: Attempt to retrieve offset fails with status 404

Same behaviour occurs also using ingress-nginx controller (not the embeded one in the values.yml)

Did you setup your proxy and tusd according to https://github.com/tus/tusd/blob/master/docs/faq.md#can-i-run-tusd-behind-a-reverse-proxy?

@Acconut To my understanding according to the above guide the first thing that needs to be done is to pass -behind-proxy flag in the values.yml. Is that correct?

Setting -behind-proxy is necessary, but not enough. Just must also configure the proxy to set the X-Forwarded-* headers, as mentioned in the guide.

Cool! how this flag can be passed in the values.yml file?

I don´t know, unfortunately. I am not a Kubernetes user. You will have to try it out on your own.

After doing these be sure to clear your browser's local storage otherwise it's gonna keep going to a bad endpoint if it changed at all


Wrong type definition for v-model directive on native input

I posted this issue first as a Stack Overflow question and @andrei-gheorghiu provided a useful answer that let him file a ticket in the Nuxt repo already but as it turned out there it seems to be a bug in the language tools as @danielroe suggested so I ended up here.
@andrei-gheorghiu already boiled this issue down perfectly to the following so I cite him here:
v-model on native <input /> tags should not be treated as an alias of :value. Firstly, because it's a directive. In essence, a function. In some cases, it has the same effect as
<input
   :value="text"
   @input="event => text = event.target.value
/>

but not in all cases (e.g: types of 'checkbox' | 'radio', where v-model can be set to a selection array and :value points the individual item).
Reproduction
https://codesandbox.io/p/sandbox/agitated-mendeleev-ypytew?file=%2Fcomponents%2Finput-list.vue&selection=[{"endColumn"%3A19%2C"endLineNumber"%3A11%2C"startColumn"%3A19%2C"startLineNumber"%3A11}]
Temporary fixes
The bug can be circumvented by using v-bind but at least in my particular case only if v-model comes after v-bind otherwise I would get a new error on the v-model instead.
<input
  v-bind="{ value: option, type }"
  v-model="selection"
/>

Or it can be ignored:
<input
   v-model="selection"
   :data-foo="/* ts-ignore */"
   :value="option"
   :type="type"
/>

but that doesn't change the fact the type definition for v-model directive is wrong.

Thanks for the report!

Thanks for the fix!


Intellisense should understand clodules/fundules

Intellisense currently only has 1 completion list item and no special icon to indicate various merged declaration types. When looking at a clodule in an Intellisense list it appears to only be a module (via icon and description) with no clear indication it is also a class. Likewise for fundules. We could consider having separate completion list items for each part of the merged declaration, or create a new icon/display scheme for them.

In general we do not find users aware of these merged constructs. more over adding new icons requires changes to different places of the system, and i am not sure the value gained justifies the cost.


Failed to connect to server after time-out and refresh

This happens to me regularly.

I was connected to a database and then a time-out of the connection occurs after not using the connection for a while.
I disconnect the server connection via right-click.
I refresh the servers and reconnect to the specific server and database.
The server connection indicator is green
Go to views, right-click on a view and select "Script as create, drop or alter".
I get an error "An error occurred while scripting the objects. Failed to connect to server...".
When I try to do a select top 1000, nothing happens.
I need to re-open Data Studio to be able to resume.

Exception message:
Microsoft.SqlServer.Management.Common.ConnectionFailureException: Failed to connect to server brabantwatera004asa001-ondemand.sql.azuresynapse.net.
---> Microsoft.Data.SqlClient.SqlException (0x80131904): Login failed for user ''. Token is expired.
at Microsoft.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
at Microsoft.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
at Microsoft.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at Microsoft.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)
at Microsoft.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean ignoreSniOpenTimeout, TimeoutTimer timeout, Boolean withFailover)
at Microsoft.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString connectionOptions, SqlCredential credential, TimeoutTimer timeout)
at Microsoft.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(TimeoutTimer timeout, SqlConnectionString connectionOptions, SqlCredential credential, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance)
at Microsoft.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString userConnectionOptions, SessionData reconnectSessionData, Boolean applyTransientFaultHandling, String accessToken, DbConnectionPool pool)
at Microsoft.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)
at Microsoft.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup, DbConnectionOptions userOptions)
at Microsoft.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)    at Microsoft.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource1 retry, DbConnectionOptions userOptions)
at Microsoft.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry, SqlConnectionOverrides overrides)
at Microsoft.Data.SqlClient.SqlConnection.Open(SqlConnectionOverrides overrides)
at Microsoft.SqlServer.Management.Common.ConnectionManager.InternalConnectImpl()
at Microsoft.SqlServer.Management.Common.ConnectionManager.InternalConnect()
at Microsoft.SqlServer.Management.Common.ConnectionManager.Connect()
ClientConnectionId:f8af5671-83bc-47aa-948b-3fbb4e94827d
Error Number:18456,State:233,Class:14
--- End of inner exception stack trace ---
at Microsoft.SqlServer.Management.Common.ConnectionManager.Connect()
at Microsoft.SqlTools.ServiceLayer.Scripting.ScriptAsScriptingOperation.Execute() in D:\a_work\1\s\src\Microsoft.SqlTools.ServiceLayer\Scripting\ScriptAsScriptingOperation.cs:line 84

@nielsvdc which version of ADS are you using?  We've made several changes to the token refresh code in recent releases that should fix most these issues.
@cssuh could you take a look at the exception to confirm this is one of the cases we'd have expected to be fixed by recent refresh token fixes?

@kburtram I'm using the latest version 1.39.1. Btw, connected query still keep working. And refresh of objects also works, Viewing of tables and view, editing tables and requesting object scripts does not.


Allow scrolling in playlist view

Whenever the playlist fills up (which I'm not too sure how, or with what limits?), clicking on a given track will move around all tracks with no clear way of simply looking at the current playlist to pick a song.

I know what you mean I wasn't sure how to make the skip behave but I'll follow your suggestion

I'm not sure that this has been fixed? I still see the same behavior on the latest change.
The interface is still confusing to me, but I don't want to ask too much given how early it is in the project and the fact that you probably have plenty of things in mind that you haven't written yet.
Would you be interested in my two cents?

Have you recompiled on the latest commit ? Or used the releases (Because they are behind the commits I think). On my side it seems to behave as you said maybe I misinterpreted something.
Thank you for asking ! If you don't care about those cents alright.

@Alphare Is the scrolling fixed

No, but I don't think I explained my problem correctly in the first place.
The player view hardcodes the scroll position in the list: there is always 3 "previous" songs, then the focused song, then the rest of them. We have no way of scrolling (either with mousewheel or using arrow keys, those are bound to volume control) to see the playlist in full and look through it.
Concrete example:
- Have a playlist with 10+ songs
- Click the last one to play it
- Only the last 4 songs (including the current) will be shown
- You have to click the top displayed one multiple times to get back to the top of the playlist, interrupting play multiple times
I see in the code that there is some sort of manual state manipulation hardcoding the 3 previous entries, etc.

As a starting point, this change removes the current jumping and hiding behavior, but still doesn't allow you to scroll when you have playlists that don't fit the screen.
diff --git a/src/systems/player.rs b/src/systems/player.rs
index d037b20..fdc41ad 100644
--- a/src/systems/player.rs
+++ b/src/systems/player.rs
@@ -143,7 +143,7 @@ pub fn get_action(
         return Some(MusicStatusAction::Downloading);
     }
     index -= dw_len;
-    let previous_len = previous.len().min(3);
+    let previous_len = previous.len();
     if index < previous_len {
         return Some(MusicStatusAction::Before(previous_len - index));
     }
@@ -162,7 +162,6 @@ pub fn get_action(
 }

 pub fn generate_music<'a>(
-    lines: usize,
     queue: &'a VecDeque<Video>,
     previous: &'a [Video],
     current: &'a Option<Video>,
@@ -197,7 +196,7 @@ pub fn generate_music<'a>(
             ))
             .style(download_style)
         }));
-        music.extend(previous.iter().rev().take(3).rev().map(|e| {
+        music.extend(previous.iter().map(|e| {
             ListItem::new(format!(
                 " {} {} | {}",
                 MusicStatus::Previous.character(),
@@ -216,7 +215,7 @@ pub fn generate_music<'a>(
                 ListItem::new(format!(" {} {} | {}", status.0, e.author, e.title)).style(status.1),
             );
         }
-        music.extend(queue.iter().take(lines + 4).map(|e| {
+        music.extend(queue.iter().map(|e| {
             ListItem::new(format!(
                 " {} {} | {}",
                 MusicStatus::Next.character(),
diff --git a/src/term/music_player.rs b/src/term/music_player.rs
index cfd7acd..9390a0d 100644
--- a/src/term/music_player.rs
+++ b/src/term/music_player.rs
@@ -134,9 +134,8 @@ impl Screen for PlayerState {
             progress_rect,
         );
         // Create a List from all list items and highlight the currently selected one
-        f.render_stateful_widget(
+        f.render_widget(
             List::new(generate_music(
-                f.size().height as usize,
                 &self.queue,
                 &self.previous,
                 &self.current,
@@ -144,7 +143,6 @@ impl Screen for PlayerState {
             ))
             .block(Block::default().borders(Borders::ALL).title(" Playlist ")),
             list_rect,
-            &mut ListState::default(),
         );
     }

Oh yeah this problem is known it is really difficult to implement it from scratch so I came to this system which is better than nothing. I can always add more previous music if we have enough room

Fixed in 73eb767632502c1883ba6c43da986174d9e34e70 and f88b814cf3379a8171d353737ed67fb610d63877 @Alphare


Clarify that temporal and bbox args must be tuples in docstrings, fix docstring formatting

Addresses #279, but does not resolve it. This work exposed and addresses a couple of concerns, but there are some still I think that need more work.
Docstring formatting
On the main branch,  there are some formatting errors that are causing key information to be omitted from the docs. It seems really easy to make these mistakes, and Mkdocs doesn't complain about them! How can we protect ourselves?

We could really use some linting rules that can catch docstrings that are not formatted properly in the Google style. Ruff has some docstring PEP linters, but I don't think that's enough here. Can Ruff lint for Google docstring style?
We need to be very careful with line-continuation. Line continuation must be done with an indent or everything on the next line will be either omitted or misformatted. A better option, IMO, is to use block style like many of the changes in this PR.
We need to be very careful with whitespace. A blank line under Parameters: will cause the entire parameters block to be formatted like a code block instead of parsed.
We have redundant type information in docstrings, e.g. strategy (String): duplicates the type (str) in the function signature. Mkdocs will pick up the type from the function signature so we don't need to keep these values in sync over time.

📚 Documentation preview 📚: https://earthaccess--448.org.readthedocs.build/en/448/

Wow, thanks Daniel for going all out on these docstrings!!! We needed this :)

@mfisher87 , @jhkennedy , we could enable linting of docstrings via ruff this way. What do you think?
I just ran it and got many more things to potentially fix...

Heck yes, thank you for looking in to that!!!

Heck yes, thank you for looking in to that!!! Should we break that in to another PR so we can merge this one?

sounds good to me 👍


KNOX-2104 - Removing redundant resource cleanup so that data table can keep track of its activePage/rowsOnTable attributes

What changes were proposed in this pull request?
Staying on the same page after updating/removing a Knox resource (note: currently only Service Definitions is displayed with pagination since the number of other resources is less than 10).
(another note: having this one line change is a result of several hours of coding and analyzing DataTable and trying to understand why did activePage always got reset even if I told the exact number. That one line caused the headache :) )
How was this patch tested?
See this video about my manual testing.

@lmccay Please review.


any way to make value absolute instead of relative?

Let's say you have a little animation every time an event occurs and you want to reuse the timeline.
In this case, scale the button by 25% and then scale it back to 100%.
Right now I have to use this code:
var timeline= Timeline()
timeline.add(Kinetic.to(square, duration: 0.2, options: [ .Scale(1.25) ]).ease(Easing.inOutSine))
timeline.add(Kinetic.to(square, duration: 0.25, options: [ .Scale(0.8) ]).ease(Easing.inOutSine))

while with most other engines I specify absolute values like this:
var timeline= Timeline()
timeline.add(Kinetic.to(square, duration: 0.2, options: [ .Scale(1.25) ]).ease(Easing.inOutSine))
timeline.add(Kinetic.to(square, duration: 0.25, options: [ .Scale(1) ]).ease(Easing.inOutSine))

The current implementation makes it very very hard to use it for complex animations since you can't guarantee that the item looks exactly the same at the end.
Any way there could be an absolute mode?

@markuswinkler I've made some improvements to how transforms are handled in the engine, and now all tween properties are absolute except for a few properties, specifically .Shift() currently. There's some additional refactoring and cleanup I want to do before pushing out a 0.9.1 release, so you can check out these latest changes from master.
Thanks for running the library through some good tests and definitely keep the suggestions coming.

Great! Just tested and confirmed.
I've used TweenMax (and GSAP) extensively in the past, your engine makes me feel like home and makes working with cascading animations a delight again (in swift) :).


⚠ Bofrost.at has degraded performance

In 2d2fc8b, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1288 ms

Resolved: Bofrost.at performance has improved in b5da88f.


Stack outside of range error

Running into this error when I run Make:
rgbasm -p 0xFF -isrc/ -isrc/include/ -Wall -Wextra -h -o obj/build_date.o src/res/build_date.asm rgblink -p 0xFF -m bin/boilerplate.map -n bin/boilerplate.sym -o bin/boilerplate.gb obj/sgb.o obj/header.o obj/vectors.o obj/misc.o obj/crash_handler.o obj/unpb16.o obj/intro.o obj/build_date.o \ && rgbfix -v -p 0xFF -v -i "BOIL" -k "HB" -l 0x33 -m 0x00 -n 0 -r 0x00 -t BOILERPLATE bin/boilerplate.gb warning: Section "Stack"'s fixed address 0xdfc0 is outside of range [0xc000; 0xcfff] warning: Section "Stack"'s end address 0xe000 is greater than last address 0xd000 error: Sanity checks failed make: *** [Makefile:97: bin/boilerplate.gb] Error 1
I haven't touched any of the files, this is right after I did a 'git clone "repo link" --recursive'. Both includes are there, and make clean doesn't help. RGBDS is v 0.4.0

TBF, there is a comment right here:
https://github.com/JL2210/gb-starter-kit/blob/add68b4b9ecade42dc8f1cee150b0133af2304ce/src/header.asm#L147-L149


Add Endpoint CRD and enhance @http directive to support it

In some cases to perform REST call more than only URL is needed.
Sometimes some additional details are needed to be added to HTTP request.
It may beAuthorization header or some required headers like x-api-client and etc.
So we need the way to declare this details in gql schema objects.
Continuing conversation with @Yshayy we thought to add endpoint CRD.
This is the definition proposal sample:
apiVersion: graphql.gateway/v1alpha
kind: GqlEndpoint
metadata:
  name: user-service-endpoint
spec:
  host: "https://user-service.svc"
  headers:
    - name: "x-api-client"
      value: "graphql"
  auth:
    type: application-only
    authority: "https://login.windows.net/tenantId"
    parameters:
      - name: client_id
        valueFrom:
          secretKeyRef:
            name: user-service-credentials
            key: client_id
      - name: client_secret
        valueFrom:
          secretKeyRef:
            name: user-service-credentials
            key: client_secret
      - name: resource
        value: user-service-resource

To integrate this CRD with @http directive we can choose several alternatives:

Replace argument url to endpoint (maybe continue to support url as optional for in-cluster calls)
Endpoint definition will be used in the directive logic in cases there will be match between url argument of @http directive and host parameter of endpoint.

In future we need to refer some more aspects related to perforing http request like retry,
timeout, maybe caching.

Looks good, in the host I won't add the https:// prefix, might worth adding protocol/type.
I would allow adding target host, can useful for local testing (same schemas, different endpoints).
As for oauth, I would be explicit about oauth2. (can be auth-flow, or something)

Some changes in endpoint definition:
apiVersion: graphql.gateway/v1alpha
kind: HttpEndpoint
metadata:
  name: user
  namespace: accounts
spec:
  matchHosts: # optional, automatically matches user.accounts due to name+namespace
  - user.myservice.com
  - user.myservice.com
  host: "https://user-service.svc"
  headers: # optional, adding headers
  - name: "x-api-client"
    value: "graphql"
  auth:
    type: ouath2/client_credentials
    spec:
      authority: "https://login.windows.net/tenantId"
      client_id: "some_client_id"
      client_secret:
          secretKeyRef:
            name: user-service-credentials
            key: client_secret
      resource: "user-service-resource"

#50 Closes this


gvatrack error

Hi,
I have extended the example provided in c++,  by adding the element gvatrack, and changed  a couple of things in order to detect and track cars, although i am facing the issue that the tracker throws the following error:
OpenCV Error: Bad argument (Unknown interpolation method) in resize, file /build/opencv-SWG7hS/opencv-3.2.0+dfsg/modules/imgproc/src/imgwarp.cpp, line 3367 0:00:03.747921807  2755 0x7fbe20003a10 ERROR                default tracker.cpp:122:track: Exception within tracker occured: /build/opencv-SWG7hS/opencv-3.2.0+dfsg/modules/imgproc/src/imgwarp.cpp:3367: error: (-5) Unknown interpolation method in function resize
The error gets thrown from the gvatrack element itself.
I am Using Ubuntu 18
openvino_2020.4.287
Thanks

Hi @zizo1111 ,
It looks like wrong OpenCV version (opencv-3.2.0+dfsg) was linked with the app. Gvatrack element from openvino_2020.4.287 should be used with the OpenCV 4.4.0 that is a part of OpenVino installation. Could you double check that the app uses the appropriate OpenCV version?

Hi @zizo1111,
The library file of @adranit comment is at /opt/intel/openvino_2020.4.287/opencv/lib or /opencv/lib. You should make sure your environment point to it.
Let me know if this advice doesn't solve your problem.
Mark

Hi @adranit @mliu2020 ,
Thanks for the reply, the reason here for my problem is that i am using ROS and Openvino together, ROS has only opencv 3.2 while openvino has 4.4, so basically i face problems with either one when i am using the other version of opencv.

Thanks @zizo1111,
Could you find a way to use them at the same time, or isolate them in their own environment like Docker?
Mark

Hi @zizo1111,
I believe we found the root cause and it is related to your environment, do you find a way to solve it yet?
Mark

Hi @zizo1111,
Since you agreed with our analysis and no further request, I believe the problem was solved.
Let me close this issue for now and feel free to re-open it if you still need help.
Mark

Hi @zizo1111,
Since you agreed with our analysis and no further request, I believe the problem was solved.
Let me close this issue for now and feel free to re-open it if you still need help.
Mark


Translate a Docker Compose File to Kubernetes Resources

Problem
This demonstration for converting docker compose to a kubernetes demo is referencing some old docker image / manifest types that are no longer supported and I think they fail to build, this breaks the demo workflow.
Steps to Reproduce
Following the guide as described isn't working... To test, running a docker compose up --build confirms this sample yaml file is using an obsolete version tag, and more so the container images aren't compliant.
$ docker compose up --build

[+] Running 2/3
 ⠹ redis-master Pulling                                                                                0.3s
 ✘ redis-slave Error    context canceled                                                                            0.3s
 ✘ frontend Error       context canceled                                                                            0.3s
[DEPRECATION NOTICE] Docker Image Format v1 and Docker Image manifest version 2, schema 1 support is disabled by default and will be removed in an upcoming release. Suggest the author of registry.k8s.io/redis:e2e to upgrade the image to the OCI Format or Docker Image manifest v2, schema 2. More information at https://docs.docker.com/go/deprecated-image-specs/

Running the kompose conversion & apply works, but the application never shows up when attempting to curl (using minikube tunnel for the LoadBalancer, or even just changing to NodePort for local dev).
$ kompose convert
$ kubectl apply -f frontend-tcp-service.yaml,redis-master-service.yaml,redis-slave-service.yaml,frontend-deployment.yaml,redis-master-deployment.yaml,redis-slave-deployment.yaml

trying to get the minikube service (with minikube tunnel running), it fails with the following:

$minikube service frontend-tcp

|-----------|--------------|-------------|---------------------------|
| NAMESPACE |     NAME     | TARGET PORT |            URL            |
|-----------|--------------|-------------|---------------------------|
| default   | frontend-tcp | 80/80       | http://<IP_ADDRESS>:31656 |
|-----------|--------------|-------------|---------------------------|

❌  Exiting due to SVC_UNREACHABLE: service not available: no running pod for service frontend-tcp found

Checking the pod confirms the image pull fails with an ImagePullBackOff:
$ kubectl get pods

NAME                            READY   STATUS             RESTARTS   AGE
frontend-967776856-dbntg        0/1     ImagePullBackOff   0          3m50s
redis-master-6d74dffd5d-ngj7s   0/1     ImagePullBackOff   0          3m50s
redis-slave-64b5589df9-nzrb4    1/1     Running            0          3m50s

Same when trying to curl

$ curl "http://$(minikube ip):$(kubectl get svc frontend-tcp -o=jsonpath='{.spec.ports[0].nodePort}')"

curl: (7) Failed to connect to <IP_ADDRESS> port 31656: Connection refused```

## Resolution

I believe the maintainers need to kindly update the Docker Compose yaml sample file provided to reflect newer docker images! Thanks in advance for this helpful demonstration 💯

This refers specifically to the information contained here: https://kubernetes.io/docs/tasks/configure-pod-container/translate-compose-kubernetes/ which was last updated funny enough on my birthday, February 5th, 2023. Probably just needs to be updated given newer Dockerfile support versions / manifests

It was also I think necessary to add the Ingress add-on for minikube https://minikube.sigs.k8s.io/docs/start/?arch=%2Flinux%2Fx86-64%2Fstable%2Fdebian+package#LoadBalancer

/language en

maybe the updated version of this demo is here: https://github.com/kubernetes/kompose  as it looks like that docker compose.yaml sample does in fact build with docker. Running kompose convert though doesn't work on that. Probably just some divergence

/kind bug

/retitle Stale page "Translate a Docker Compose File to Kubernetes Resources"

/triage accepted

/assign

Issues with image pull:
Warning  Failed     17m (x4 over 19m)     kubelet            Failed to pull image "gcr.io/google-samples/gb-frontend:v4": Error response from daemon: manifest for gcr.io/google-samples/gb-frontend:v4 not found: manifest unknown: Failed to fetch "v4" from request "/v2/google-samples/gb-frontend/manifests/v4"
Changes to commands/files:
#Upgrade to v1.33
curl -L https://github.com/kubernetes/kompose/releases/download/v1.33.0/kompose-linux-amd64 -o kompose
#Update to docker-compose.yml based on kompose site examples
At kompose/examples/compose.yaml at main · kubernetes/kompose (github.com)
services:
redis-leader:
container_name: redis-leader
image: redis
ports:
- "6379"
redis-replica:
container_name: redis-replica
image: redis
ports:
- "6379"
command: redis-server --replicaof redis-leader 6379 --dir /tmp
web:
container_name: web
image: quay.io/kompose/web
ports:
- "8080:8080"
environment:
- GET_HOSTS_FROM=dns
labels:
kompose.service.type: LoadBalancer
#Apply new yaml files
kubectl apply -f redis-leader-deployment.yaml, redis-replica-deployment.yaml, web-deployment.yaml, redis-leader-service.yaml,redis-replica-service.yaml,web-tcp-service.yaml
Changes to Output:
INFO Kubernetes file "redis-leader-service.yaml" created
INFO Kubernetes file "redis-replica-service.yaml" created
INFO Kubernetes file "web-tcp-service.yaml" created
INFO Kubernetes file "redis-leader-deployment.yaml" created
INFO Kubernetes file "redis-replica-deployment.yaml" created
INFO Kubernetes file "web-deployment.yaml" created
deployment.apps/redis-leader created
deployment.apps/redis-replica created
deployment.apps/web created
service/redis-leader created
service/redis-replica created
service/web-tcp created
Changes to Testing Services:
minikube service web-tcp
|-----------|---------|-------------|---------------------------|

NAMESPACE
NAME
TARGET PORT
URL

default
web-tcp
8080/8080
http://<IP_ADDRESS>:31624/

-----------
---------
-------------
---------------------------

🏃  Starting tunnel for service web-tcp.

-----------
---------
-------------
------------------------

NAMESPACE
NAME
TARGET PORT
URL

-----------
---------
-------------
------------------------

default
web-tcp

http://<IP_ADDRESS>:45953/

-----------
---------
-------------
------------------------

🎉  Opening service default/web-tcp in default browser...

❗  Because you are using a Docker driver on linux, the terminal needs to be open to run it.

kubectl describe service web-tcp
Name:                     web-tcp
Namespace:                default
Labels:                   io.kompose.service=web-tcp
Annotations:              kompose.cmd: kompose convert
kompose.service.type: LoadBalancer
kompose.version: 1.33.0 (3ce457399)
Selector:                 io.kompose.service=web
Type:                     LoadBalancer
IP Family Policy:         SingleStack
IP Families:              IPv4
IP:                       <IP_ADDRESS>
IPs:                      <IP_ADDRESS>
Port:                     8080  8080/TCP
TargetPort:               8080/TCP
NodePort:                 8080  31624/TCP
Endpoints:                <IP_ADDRESS>:8080
Session Affinity:         None
External Traffic Policy:  Cluster
Events:


Rustc perf

From irlo:

We should also think about integrating http://perf.rust-lang.org/index.html, if not importing the data and re-visualizing it, then at least linking to it.

It's linked now. I think it's probably not worth investing energy in duplicating any of the actual work there.

Sounds good. I have a dream of this being the one ring to rule them all and in the JSON bind them, but that can probably wait :).


Incorrectly marking valid code as invalid

I've seen it mark this stuff as wrong when it's actually valid Luau code:

Type checking

The += & -= operators

That code is all valid Luau (runs fine in-game and in studio)

The Luau extension only provides syntax highlighting and snippets. The type check errors are potentially the result of another extension you have installed.


[BUG] Backup Target - NFS - the k8s node supports only 4.0 - an incorrect mount option was specified

Hi,
I've the following error from the front-end #/backup when I configure Longhorn to use a NFS "Backup Target".
error listing backups: error listing backup volumes: Failed to execute: /var/lib/longhorn/engine-binaries/longhornio-longhorn-engine-v1.1.0/longhorn [backup ls --volume-only nfs://dnas-share-rb-c1-n1.dnas:/backup/rb-c1], output Cannot mount nfs dnas-share-rb-c1-n1.dnas:/backup/rb-c1: Failed to execute: mount [-t nfs4 -o nfsvers=4.2 dnas-share-rb-c1-n1.dnas:/backup/rb-c1 /var/lib/longhorn-backupstore-mounts/dnas-share-rb-c1-n1_dnas/backup/rb-c1], output mount.nfs4: an incorrect mount option was specified , error exit status 32 , stderr, time="2021-04-01T15:05:29Z" level=error msg="Cannot mount nfs dnas-share-rb-c1-n1.dnas:/backup/rb-c1: Failed to execute: mount [-t nfs4 -o nfsvers=4.2 dnas-share-rb-c1-n1.dnas:/backup/rb-c1 /var/lib/longhorn-backupstore-mounts/dnas-share-rb-c1-n1_dnas/backup/rb-c1], output mount.nfs4: an incorrect mount option was specified\n, error exit status 32" , error exit status 1

From my understanding, the error is raised by [util.Execute] when called in [nfs.mount].
[util.Execute] https://github.com/longhorn/backupstore/blob/51dcc71901ed7f377a80df143196933096605cf4/util/util.go#L152
[nfs.mount] https://github.com/longhorn/backupstore/blob/51dcc71901ed7f377a80df143196933096605cf4/nfs/nfs.go#L99
Environment:

Longhorn version: 1.1.0
Kubernetes version: v1.20.4+k3s1
Node config

Linux 4.4.213-rockchip64 SMP aarch64
CPU per node: 4CPU
Memory per node: 4Gi
Disk type: emmc + sdcard
Network bandwidth and latency between the nodes: local network

Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal): Baremetal, 3 nodes

Analysis:
In fact, the k8s node (Debian Buster Linux 4.4.213-rockchip64 SMP aarch64) is not able to mount the NFS share with the option nfsvers=4.2. However, it is possible to mount the NFS share with nfsvers=4.0.
XXXXX:~$ sudo mount -t nfs4 -v -o nfsvers=4.2 <IP_ADDRESS>:/backup /tmp/dnas
mount.nfs4: timeout set for Thu Apr  1 15:10:43 2021
mount.nfs4: trying text-based options 'nfsvers=4.2,addr=<IP_ADDRESS>,clientaddr=<IP_ADDRESS>'
mount.nfs4: mount(2): Invalid argument
mount.nfs4: an incorrect mount option was specified
XXXXX:~$ sudo mount -t nfs4 -v -o nfsvers=4.1 <IP_ADDRESS>:/backup /tmp/dnas
mount.nfs4: timeout set for Thu Apr  1 15:10:46 2021
mount.nfs4: trying text-based options 'nfsvers=4.1,addr=<IP_ADDRESS>,clientaddr=<IP_ADDRESS>'
mount.nfs4: mount(2): Invalid argument
mount.nfs4: an incorrect mount option was specified
XXXXX:~$ sudo mount -t nfs4 -v -o nfsvers=4.0 <IP_ADDRESS>:/backup /tmp/dnas
mount.nfs4: timeout set for Thu Apr  1 15:10:50 2021
mount.nfs4: trying text-based options 'nfsvers=4.0,addr=<IP_ADDRESS>,clientaddr=<IP_ADDRESS>'
XXXXX:~$ sudo umount /tmp/dnas
/tmp/dnas: nfs4 mount point detected
/tmp/dnas: umounted

FYI it works when I mount the NFS share from another computer (Linux 5.8.0-48-generic SMP  x86_64).
XXXXX:~$ sudo mount.nfs -v -o nfsvers=4.2 <IP_ADDRESS>:/backup /tmp/dnas
mount.nfs: timeout set for Thu Apr  1 17:21:12 2021
mount.nfs: trying text-based options 'nfsvers=4.2,addr=<IP_ADDRESS>,clientaddr=<IP_ADDRESS>'
XXXXX:~$ sudo umount /tmp/dnas
/tmp/dnas: nfs4 mount point detected
/tmp/dnas: umounted

So, from my understanding, even if the server support NFS 4.0, 4.1 and 4.2, the k8s node supports only NFS 4.0.
Question:
According to [nfs.MinorVersions], the version 4.0 should be supported.
[nfs.MinorVersions] https://github.com/longhorn/backupstore/blob/51dcc71901ed7f377a80df143196933096605cf4/nfs/nfs.go#L19
I'm not a Go developer so I'm wondering if there is something to do in the [loop] in order to iterate from 4.2 to 4.0 each time the client raised an error of type an incorrect mount option was specified.
[loop] https://github.com/longhorn/backupstore/blob/51dcc71901ed7f377a80df143196933096605cf4/nfs/nfs.go#L97
Thank you for the support!
Best regards

Leaving a note here, this happens because the error message does not contain: "Protocol not supported"
So once the first mount fails, the other versions won't be even attempted.
The fix should probably be to try all mount versions in the error case instead of parsing the error message.
Since if all of them fail the last error will be returned, which is the baseline v4.0
See:

https://github.com/longhorn/backupstore/blob/51dcc71901ed7f377a80df143196933096605cf4/nfs/nfs.go#L100
https://github.com/longhorn/backupstore/blob/51dcc71901ed7f377a80df143196933096605cf4/nfs/nfs.go#L71

cc @innobead this issue should be easy to fix see my comment here: https://github.com/longhorn/longhorn/issues/2438#issuecomment-812011216
Currently the client needs to support nfs v4.2 otherwise the mount for the backupstore will fail.
Since there is a bug in the way it's tested. The solution for this is to just try from 4.2, 4.1, 4.0
And only return the final error if the last try 4.0 fails to mount.
That way we don't need to do any evaluation of the error messages or other such stuff.

PR V3:
longhorn/longhorn-engine#671
https://github.com/longhorn/backupstore/pull/86

Validating in progress,
Testing master image set with nfsv3-only worker nodes,
In Scenario 2., when trying to use the NFS as backup target user will now see this error notification:

error listing backup volume names: failed to execute: /var/lib/longhorn/engine-binaries/longhornio-longhorn-engine-master-head/longhorn [backup ls --volume-only nfs://longhorn-test-nfs-svc.default:/opt/backupstore], output Cannot mount nfs longhorn-test-nfs-svc.default:/opt/backupstore: vers=4.0: Failed to execute: mount [-t nfs4 -o nfsvers=4.0 -o actimeo=1 longhorn-test-nfs-svc.default:/opt/backupstore /var/lib/longhorn-backupstore-mounts/longhorn-test-nfs-svc_default/opt/backupstore], output mount.nfs4: No such device , error exit status 32: vers=4.1: Failed to execute: mount [-t nfs4 -o nfsvers=4.1 -o actimeo=1 longhorn-test-nfs-svc.default:/opt/backupstore /var/lib/longhorn-backupstore-mounts/longhorn-test-nfs-svc_default/opt/backupstore], output mount.nfs4: No such device , error exit status 32: vers=4.2: Failed to execute: mount [-t nfs4 -o nfsvers=4.2 -o actimeo=1 longhorn-test-nfs-svc.default:/opt/backupstore /var/lib/longhorn-backupstore-mounts/longhorn-test-nfs-svc_default/opt/backupstore], output mount.nfs4: No such device , error exit status 32: Cannot mount using NFSv4 , stderr, time="2021-11-16T02:57:27Z" level=error msg="Cannot mount nfs longhorn-test-nfs-svc.default:/opt/backupstore: vers=4.0: Failed to execute: mount [-t nfs4 -o nfsvers=4.0 -o actimeo=1 longhorn-test-nfs-svc.default:/opt/backupstore /var/lib/longhorn-backupstore-mounts/longhorn-test-nfs-svc_default/opt/backupstore], output mount.nfs4: No such device\n, error exit status 32: vers=4.1: Failed to execute: mount [-t nfs4 -o nfsvers=4.1 -o actimeo=1 longhorn-test-nfs-svc.default:/opt/backupstore /var/lib/longhorn-backupstore-mounts/longhorn-test-nfs-svc_default/opt/backupstore], output mount.nfs4: No such device\n, error exit status 32: vers=4.2: Failed to execute: mount [-t nfs4 -o nfsvers=4.2 -o actimeo=1 longhorn-test-nfs-svc.default:/opt/backupstore /var/lib/longhorn-backupstore-mounts/longhorn-test-nfs-svc_default/opt/backupstore], output mount.nfs4: No such device\n, error exit status 32: Cannot mount using NFSv4" , error exit status 1

Validation - PASSED
Tested with master images.
On cluster with with NFSv3-only kernel installed,
The message will be shown as mentioned in above message.
And the Backup Target won't work.
On cluster with with NFSv4-only kernel installed,
There won't be info or error messages.
And the Backup Target can set to the NFSv4 server.

Thank you!!! :rocket:

Having this issue on Longhorn 1.5.1.
Our current storage (Isilon OneFS supports only NFS 4.0) and the error I get is:
error listing backup volume names: timeout executing: /var/lib/longhorn/engine-binaries/rancher-mirrored-longhornio-longhorn-engine-v1.5.1/longhorn [backup ls --volume-only nfs://<IP_ADDRESS>:/ifs/data/kubernetes/longhorn], output , stderr, time="2023-10-17T14:52:00Z" level=warning msg="Trying reading mount point /var/lib/longhorn-backupstore-mounts/172_16_10_199/ifs/data/kubernetes/longhorn to make sure it is healthy" pkg=nfs time="2023-10-17T14:52:00Z" level=info msg="Attempting mount for nfs path <IP_ADDRESS>:/ifs/data/kubernetes/longhorn with nfsvers 4.2" pkg=nfs time="2023-10-17T14:52:00Z" level=info msg="Mounting NFS share nfs://<IP_ADDRESS>:/ifs/data/kubernetes/longhorn on mount point /var/lib/longhorn-backupstore-mounts/172_16_10_199/ifs/data/kubernetes/longhorn with options [nfsvers=4.2 actimeo=1 soft timeo=300 retry=2]" pkg=nfs , error <nil>
There's no retry to 4.1, 4.0 etc. I can mount manually from the node by specifying -o vers=4.0. Any ideas?
Thanks


Update meta.yaml with build/number 1

I'm trying to fix https://github.com/galaxyproject/galaxy/issues/18761
Build number should be increased to generated the proper singularity image on the galaxy side (?)

Just to be sure. This has nothing to do with Galaxy. Your bioconda PR has not created a new biodonda package. And no package means no container. You always need to bump the tool version or the build number to get a new package.

@bgruening

This has nothing to do with Galaxy

yes, but I found the problem via galaxy

Your bioconda PR has not created a new biodonda package.

no

You always need to bump the tool version or the build number to get a new package.

the build/number was increased from 0 to 1 in this PR. This is the only change here.

I was trying to explain why it didn't worked in the first place.

@bgruening  Oh, I see, thanks.


Reduce container size

Since this image has over 100k downloads and nobody complained about the size yet, I'll assume the size is ok.


Habitat Classification Model

Create/develop a model to assess and understand what kind of habitat exists in the extracted frame from the stills. This would help in reducing the amount of time taken to manually analyse the transect and mark each of the stills with its respective habitat.
The 3 main habitats are:

Sand/Mud
Shell
Gravel

I would like to work on it.


Suggested edits for https://github.com/DevExpress/DevExtreme.AspNet.Data/pull/205

If we want to care about thread safety and resource disposal I would converted CustomAggregators to singleton instead of having CustomAggregatorsBarrier:
    public class CustomAggregators {
        private static readonly CustomAggregators _instance = new CustomAggregators();
        private readonly Dictionary<string, Type> _aggregatorTypes = new Dictionary<string, Type>();

        internal CustomAggregators() {
        }

        public static void RegisterAggregator(string summaryType, Type aggregatorType) {
            _instance.RegisterAggregatorInternal(summaryType, aggregatorType);
        }

        internal void RegisterAggregatorInternal(string summaryType, Type aggregatorType) {
            _aggregatorTypes[summaryType] = aggregatorType;
        }

        internal Aggregator<T> CreateAggregator<T>(string summaryType, IAccessor<T> accessor) {
            if (_aggregatorTypes.TryGetValue(summaryType, out var aggregatorType)) {
                var genericAggregatorType = aggregatorType.MakeGenericType(typeof(T));
                return (Aggregator<T>)Activator.CreateInstance(genericAggregatorType, accessor);
            }

            return null;
        }
    }

And then in tests we can just create class instance:
var customAggregators = new CustomAggregators();
customAggregators.RegisterAggregatorInternal("sum", typeof(SumAggregator<>));

Any way I can merge you code.

How the AggregateCalculatorTests.CustomAggregator case would look then?

In AggregateCalculatorTests.CustomAggregator we can use static register method:
CustomAggregators.RegisterAggregator("comma", typeof(CommaAggregator<>));

Static aggregators collection should not conflict with other unit tests where instance of CustomAggregators will be used.
Or we can create an instance of CustomAggregators and pass it to AggregateCalculator constructor:
var customAggregators = new CustomAggregators();
customAggregators.RegisterAggregatorInternal("sum", typeof(SumAggregator<>));
var calculator = new AggregateCalculator<int>(data, new DefaultAccessor<int>(),
                new[] { new SummaryInfo { Selector = "this", SummaryType = "comma" } },
                new[] { new SummaryInfo { Selector = "this", SummaryType = "comma" } }
            ), customAggregators);

Static aggregators collection should not conflict with other unit tests where instance of CustomAggregators will be used.

Sure. However, a conflict will arise with the next test case (in another class) accessing the static collection.

Or we can create an instance of CustomAggregators and pass it to AggregateCalculator constructor

Ultimately, the goal is to cover end-user scenarios. If we inject CustomAggregators into AggregateCalculator then we need another test ensuring that the public API works.
Do you see any issues with CustomAggregatorsBarrier?

Lambda expressions are often hard to debug and you have to duplicate CustomAggregatorsBarrier code in each test. Perhaps to test static classes each test should be run in separate AppDomain. Not sure if it is supported by xunit. Perhaps you will change it later. Now I will do the merge


Moved SearchableListMixin to wagtailadmin

And add wagtailsearch support.
As suggested by @ababic in https://github.com/wagtail/wagtail/pull/3774#discussion_r141448118

Thanks for the review @BertrandBordage!


compress option in terser inside production es rollup config produces invalid JS

Current Behavior
here is my repo i'm working on https://github.com/sw-yx/react-netlify-identity-widget/tree/rollupProductionIssue
if you:
yarn build
yarn link
cd example
yarn && yarn link "react-netlify-identity"
yarn start

you will see this error:

however if you change the package.json to use the development versions:

it works!!
to me this indicates a rollup config issue.
Expected behavior
the production output should work the same as development output
Suggested solution(s)
i think this could be a terser bug. or a setting that is incompatible with React.
here is the offending unexpected token - prettified for easier reading

i'm not sure what rollup setting caused this but it definitely only exists in the production build.
Your environment

Software
Version(s)

TSDX
0.3.4

TypeScript
3.4.4

Browser
chrome

npm/Yarn
yarn

Operating System
osx

what's the size impact on you if you turn off compress? i dont have the option because my code plain doesnt work without it (and its not like i'm doing some crazy nonidiomatic React stuff). as far as i can see, thats the only option for now, and i pray @TrySound can figure it out.
We can also choose to document it as well as how to patch the package, for early adopters of TSDX who may run into this.

To be honest terser code is unreadable. I can't find a fix for that. You may turn off collapse_vars option. It should fix the problem.

ohh i see. i thought there was no option available. thank you i will try that.

So what should we do for now?

@jaredpalmer  i have verified that Bogdan's solution works. i recommend adopting it in tsdx and have PR'ed accordingly