About the setup of LinearWarmupCosineAnnealingLR, seems no different between the step-level or epoch-level information

First, thanks for this amazing github repo 👍
However, I want to ask some questions related with the closed issue #264 .
Suppose we enable the warmup_cosine scheduler, the default 10 warmup-epoch is defined in the base.py.
The code snippet implements the LinearWarmupCosineAnnealingLR setup,
# code snippet in base.py
...
if self.scheduler == "warmup_cosine":
            scheduler = {
                "scheduler": LinearWarmupCosineAnnealingLR(
                    optimizer,
                    # suppose we have 10 warmup epoch as SimCLR..
                    warmup_epochs=10 * self.num_training_steps,
                    max_epochs=self.max_epochs * self.num_training_steps,
                    warmup_start_lr=self.warmup_start_lr if self.warmup_epochs > 0 else self.lr,
                    eta_min=self.min_lr,
                ),
                "interval": self.scheduler_interval,  # step-level, instead of epoch-level
                "frequency": 1,
            }

In the aforementioned code snippet, why don't we just setup warmup_epochs=10, instead we do the following modification :

change the interval to step-level
calculate the number of step for each epoch

suppose 40 step per epoch

apply the step-level setup with exactly epoch-level setting (s.t. 10 epoch)

warmup_step=10*40 (since interval is step) , which equivalent warmup_epoch=10 (while interval is epoch)

I can't figure out why we did the above setup with the default action is still perform the exactly 10 "epoch" warmup finally.
My guess : some situation, maybe we can setup "397 step" warmup, which is close to 10 epoch, but not "exactly" equivalent to some epoch. So, we need to manually setup 397 instead ?
Thank you for taking a look, any suggestion will be appreciated ~

The result is similar but not exactly the same. With the step setting the lr is updated at every step, while with the epoch setting it is increased only in-between epochs and then kept constant for the whole epoch. We found the step setting slightly improves the performance and also makes some methods more stable.

Oh.. thanks for your explanation, the reason is a bit out of my suppose, it's great to understand the detail implementation behind the solo-learn 👍


Bug at binary search

Overflow will be happen at this line because if end=2147483647 & start=214 then the sum of start+end will be overflow.
So try to use the following formula to prevent overflow - - > mid=start+((end-start)/2)
https://github.com/amritansh22/Data-Structures-and-Algorithms-in-cpp/blob/1d8ccd7b89ef093f173e80b9a3932104511062e5/SearchingAlgorithms/binary_search.cpp#L14

Hello, here it says the issue is still open. Does it still require any bug fixes ? I am new to contributing and haven't contributed to anything yet so I would very much like to help if needed.

Instead of using mid = (start+end)/2 , use mid = start+((end-start)/2).

Use mid = start + (end - start) / 2


Thanks For Your Work

Just wanted to say thank you for all your repositories.
I love scripting in Bash and they are really useful to me :-)

You're welcome.  Do let me know if you find any bugs with this one; I literally just finished it and am only just about to start using it myself.


React Semantic : why slide left transition is not available in  ? Any alternative to use custom animation in this?

There is definitely a slide left transition in SUI core.  It appears we've simply missed it in the enum.

Thanks @levithomason for quikcly fixing the issue. I have one more question, Can we define separate Animation for mount and unmount in <Transition.Group>, if yes, how?

@jatinatgit that is unfortunately not something the Transition component currently supports.
Please open new reports for different bugs.


Integration with redux devtools?

Many developers consider that a deciding factor for choosing one or the other store solution.
Could you give an example how to integrate that?

middleware could of course forward to the devtool api, but you are free to create functional actions without types, that leaves only the mutations/pre-state/after-state. unless of course you use a dispatch(type, ...args) reducer with a middleware around that.

you are free to create functional actions without types

It's fine to make that optional, but require it for redux devtools support.

i thought about a middleware that injects dispatch and expects a typed signature. do you know an easy tutorial where i could learn how it integrate with redux devtools? i would give it a go ...

The only way I can think of is if you implement a middleware for zustand that builds a redux store based on your zustand store, which can then be watched by the redux devtools

i'll investigate a bit. sticking to a redux like structure would be easy - just haven't use redux devtools much.

Here's an example integration for unistore: https://github.com/developit/unistore/blob/master/devtools.js

got it working: https://twitter.com/0xca0a/status/1136037199533805573
works with action dispatchers and generic setState :)

How do we publish this? @JeremyRH
Should it be an export like
import create from 'zustand'
import devtools from 'zustand/devtools'
import redux from 'zustand/redux'

And should the redux middleware be included, too? Or under another name?

Yeah it looks like we can make it reasonably typesafe. Adding an extra file for people to import is the simplest solution but this doesn't scale well if you plan to add a lot of middlewares. Lots of middlewares would increase the package size (not bundle size, just the files you download when running npm install zustand) and slow the build and tests (if we add tests).
We could set up a mono-repo. I haven't done that before so it would be fun to learn even though it's not really necessary for a single middleware.

As you wish, sounds good to me to take scaling into account. can't help you with monorepos, i have zero experience, but @aleclarson has just transformed react-spring into a monorepo, see https://github.com/react-spring/react-spring/pull/687 maybe he could answer questions you have

Feature added with PR #38
I think this is safe to close.


Is there an easy way to wrap around left and right?

I couldn't find it in the documentation, but I'm sure I might have missed something.

Not sure what you mean by wrap around left or right

If I have 5 tabs and I get to the far left and swipe left, go to the one on the far right.  i.e.    tab5<-tab1   or tab5->tab1.     or like    5,0,1,2,3,4,5,0.

Sorry @grimace, I'm still not able to understand your question.
Could you please demonstrate it with a video? or provide an example?

Sorry for the confusion.  How about this?
Let's say you have 3 tabs;  Tab1, Tab2, Tab3.

Starting from the left ( Tab1 )
Swipe right to Tab2
Swipe right to Tab3
Continue to swipe right from Tab3 - currently, nothing happens  ( of course you could go back the other way, but not what I was looking for )
What I'm interested in is the ability to swipe right from Tab3 ( wrapping back around ) to Tab1.  So that you could actually continuously swipe in one direction forever ( or until you get tired of the exercise).

@grimace
oh, so like  the loop option on ion-slides ?
There isn't an option for that right now. I should be able to implement it in the near future.

@ihadeed I'm expecting for loop option too!
Anyway, thank you for this beautiful plugin :)

Yes, exactly what I was looking for. Also like to express my gratitude. Great project. Thanks!

Really hope to see this feature implemented soon.

@NgYueHong I'll try to implement this if it performs well. The new super tabs is based on a flex box .. so it should be easier to move the tabs around and give the user the feeling of an infinite loop.

@ihadeed
I work on ionic 4 application
but when I loop the super-tab-button and super-tab
I have this error :
core.js:15723 ERROR Error: Uncaught (in promise): TypeError: Cannot set property 'active' of undefined TypeError: Cannot set property 'active' of undefined     at<EMAIL_ADDRESS>(super-tab-button_2.entry.js:249)

@ihadeed It's great to see that Ionic 4 is now officially supported and I am really looking forward to see this feature implemented soon. With this feature, it will be a HUGE UPGRADE to this plugin that the plugin will be able to be used for infinite page swiping. Just like Gmail app, where user can just continuously swipe to view the next email.  Just imagine how much more useful this plugin will be with the implementation of infinite loop feature.

@ihadeed Is there any news on this?


YARN-11165. Use default java.policy when no group policy is set.

Description of PR
https://issues.apache.org/jira/browse/YARN-11165
When JavaSandboxLinuxContainerRuntime is used, we can specify yarn.nodemanager.runtime.linux.sandbox-mode.policy to use self-provided java.policy file. When this setting is not specified, JavaSandboxLinuxContainerRuntime will use the default java.policy file.
However, when user belongs to a group (or more groups), and yarn.nodemanager.runtime.linux.sandbox-mode.policy.group.$groupName setting is not specified, JavaSandboxLinuxContainerRuntime still skips the default java.policy file, resulting in a final policy which looks like this:
grant codeBase "file:/usr/local/hadoop/-" {
  permission java.security.AllPermission;
};
grant {
   permission java.io.FilePermission "/tmp/hadoop-yarn/nm-local-dir/usercache/yarn/appcache/application_1653546011283_0006//-", "read";
   permission java.io.FilePermission "/tmp/hadoop-yarn/nm-local-dir/usercache/yarn/appcache/application_1653546011283_0006/filecache/13/-", "read";
   permission java.io.FilePermission "/tmp/hadoop-yarn/nm-local-dir/usercache/yarn/appcache/application_1653546011283_0006/filecache/11/-", "read";
   permission java.io.FilePermission "/tmp/hadoop-yarn/nm-local-dir/usercache/yarn/appcache/application_1653546011283_0006/filecache/12/-", "read";
   permission java.io.FilePermission "/tmp/hadoop-yarn/nm-local-dir/usercache/yarn/appcache/application_1653546011283_0006/filecache/10/-", "read";
};

which will cause problem running applications.
This PR ensures that the default java.policy will still be used when no group policy is set.
How was this patch tested?
For code changes:

[ ] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
[ ] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 47s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
39m 11s

trunk passed

+1 :green_heart:
compile
1m 44s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
compile
1m 35s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
0m 49s

trunk passed

+1 :green_heart:
mvnsite
0m 57s

trunk passed

+1 :green_heart:
javadoc
0m 57s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
0m 44s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m 46s

trunk passed

+1 :green_heart:
shadedclient
24m  6s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 41s

the patch passed

+1 :green_heart:
compile
1m 32s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javac
1m 32s

the patch passed

+1 :green_heart:
compile
1m 24s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
1m 24s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 30s

the patch passed

+1 :green_heart:
mvnsite
0m 43s

the patch passed

+1 :green_heart:
javadoc
0m 37s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
0m 34s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m 33s

the patch passed

+1 :green_heart:
shadedclient
23m 47s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
23m 23s

hadoop-yarn-server-nodemanager in the patch passed.

+1 :green_heart:
asflicense
0m 43s

The patch does not generate ASF License warnings.

128m 29s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4361/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/4361

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux f20b836f4d41 4.15.0-175-generic #184-Ubuntu SMP Thu Mar 24 17:48:36 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 8817b3691f553c2396e091d896a7af17b1f9bcc8

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS> /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4361/1/testReport/

Max. process+thread count
607 (vs. ulimit of 5500)

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager U: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4361/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.


Conflict with DnD Beyond importer show to players feature.

When you activate the module, it takes away your ability as DM to show art and other images within journal entries in foundry.

https://i.gyazo.com/3dc4e7296f3207b6f2f47c96b82a35a0.mp4


the web view

hello，when i run  node ./tools/grabber.js
how i view it in the chrome explorer？

now, i know use  node app.js to start web service.
but mongo connection has error:MongoError: Authentication failed.
i don't know node.js     can you tell me how to modify mongo connection files？ and modify how many files？


[FEAT]: Integrating Docker into the project

Docker is a must for open-source projects nowadays as it has its benefits.
Use Case
Dockerfile has many benefits but consistency and isolation stand out the most.
Docker allows you to package your entire application, including its dependencies, into a single container. That makes sure your application will run across different environments.
another benefit is that it runs in its environment without interfering with other applications or the host system.
I will be creating and updating the docs and creating the Dockerfile for the project

Duplicate of https://github.com/HITK-TECH-Community/Community-Website/issues/543
Thanks for opening the issue but please check once among the opened issues


OCI runtime create failed: container_linux.go

Action: vscode-docker.containers.start
Error type: 400
Error Message: (HTTP code 400) unexpected - OCI runtime create failed: container_linux.go:345: starting container process caused "process_linux.go:430: container init caused "rootfs_linux.go:58: mounting \"/c/GitClone/articulate-0.29.0/articulate-0.29.0/local-storage/rasa/rasa-config.yml\" to rootfs \"/mnt/sda1/var/lib/docker/overlay2/9f4e33366db7199d6132fd4bc6e3e8ed295db06b495460d2ec17a28dbfc2e4a3/merged\" at \"/mnt/sda1/var/lib/docker/overlay2/9f4e33366db7199d6132fd4bc6e3e8ed295db06b495460d2ec17a28dbfc2e4a3/merged/app/config.yml\" caused \"not a directory\""": unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type
Version: 0.8.1
OS: win32
Product: Visual Studio Code
Product Version: 1.38.1
Language: en

Call Stack
extension.bundle.js:157:703034extension.bundle.js:157:703034
extension.bundle.js:157:702997extension.bundle.js:157:702997
module.exports.m.buildPayload extension.bundle.js:157:703007
IncomingMessage.<anonymous> extension.bundle.js:157:702507
IncomingMessage.emit events.js:187:15
endReadableNT _stream_readable.js:1092:12

Two things:

Make sure Docker is configured for linux containers now Windows containers
Try setting COMPOSE_CONVERT_WINDOWS_PATHS as seen here.

@Cesarcuna did that resolve your issue?


Error: Could not find a definition

With the following code sample, placing my cursor in the middle of the function doSomething on line 4 foo.doSo[cursor here]mething('one', 'two'); hitting alt+. returns Error: Could not find a definition
function Thing(){}
Thing.prototype.doSomething = function(arg1, arg2) {};
var foo = new Thing();
foo.doSomething('one', 'two');

Should ternjs jump to requirejs defined resource like in demo editor (test_dep.js)?

Can you give me an example project where the requirejs plugin fails to find the proper file?

@marijnh I'd like to go ahead and close this issue. Would you be ok with that?

Yes, let's close


Supporting snap layout menu for Windows 11

On Windows 11, when the mouse hovers over the maximize button of a native window, or Win+Z is pressed, a snap layout menu pops up. However, when using this library, nothing happens when I hover the mouse over maximize button. Consider adding this feature to keep consistent with native window behavior.
See https://learn.microsoft.com/zh-cn/windows/apps/desktop/modernize/apply-snap-layout-menu
If your project already supports this feature, please tell me the minimum version that supports this feature, thanks

This project has support for snap layout for a long time already. All you need to do is to follow the instructions from the README.


Tweaking 'Speakers & TV' access level error message to make it more clearer

Ran into an issue (refer to #264 ) with the 'Speakers & TV access level' error. Found out you gotta tweak both the Home app (Settings > Airplay and Homekit > Allow Access) and TV settings for it to work.
Made a pull request to fix the error message and include info on adjusting ATV settings. Hoping it clears things up for users who run in the same problem as I did. Take a look when you can, and feel free to tweak if needed.
Cheers!

I have taken your commit and modified it a bit. It is now merged to develop. I will close the PR. Don't worry, you are still listed as the author https://github.com/maxileith/homebridge-appletv-enhanced/commit/63d8910e4f179ce049809d26b24b8ddf6ea96ca1 :)


[COMMODITY] fixing of wrong 'children' record fetching stuff

Some of commodities can be found in search, but visiting of commodity details page
causes redirect to search page.
As I found we have an issue in Commodity#children method.
Issue come with fix for https://trello.com/c/VOrEAwts/441-tariff17-duplicate-commodity-codes-in-search-box-and-non-declarable-commodity-clickable-searchable
So rolling back of this update - fixed issue for all previously errored commodities:
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/0306111010?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/0306119000?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/0306141000?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/0306143000?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/0306149010?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/0306169100?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/0306169920?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/0306169930?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/0306179100?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/0306179220?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/0306179300?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/0306179400?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/0306179910?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/0306191000?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/0406309000?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/0406900100?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/0406901300?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/0406901500?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/1001990060?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/1001990092?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/1515909920?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/1515909992?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/1602499000?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/2001909781?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/2001909791?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/2003102000?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/2006009991?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/2008994090?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/2008996390?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/2008996791?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/2008996795?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/2009419910?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/2009419970?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/2009719910?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/2101129299?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/2208903300?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/2401106000?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/2401107010?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/2401206000?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/2401207010?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/2830100090?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/2905490090?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/2909309090?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/3502902000?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/3706102000?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/3706905200?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/3706909100?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/3901300010?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/3913900093?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/3913900095?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/3920102300?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/3920102410?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/3920621976?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/3926300090?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/4016930090?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/4016999110?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/4408101500?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/4408395500?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/4408901500?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/4804193000?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/4804315800?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/4804398000?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/4823709000?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/6110909030?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/6207910099?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/6207999091?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/6208910090?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/6208990091?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/7005292500?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/7222208900?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/7222305100?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/7228102000?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/7228105000?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/7304299090?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/7304312020?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/7304312099?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/7304318030?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/7304395220?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/7304395830?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/7304399230?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/7304399299?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/7304399320?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/7304499990?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/7304518120?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/7304518199?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/7304518930?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/7304518999?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/7304599230?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/7306307280?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/7306307290?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/7306307780?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/7308905100?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/7312106191?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/7312106591?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/7312106599?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/7312106991?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/7312108112?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/7312108113?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/7312108312?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/7312108313?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/7312108512?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/7312108513?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/7312108912?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/7312108913?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/7312108990?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/7312109812?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/7312109813?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/7606129310?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/7606129920?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/8108300090?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/8108905085?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/8108909030?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/8108909091?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/8413702100?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/8428907100?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/8462211000?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/8462218000?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/8462291000?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/8462299100?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/8466209800?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/8466912000?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/8467292000?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/8467295100?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/8467295300?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/8467297000?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/8477591000?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/8477901000?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/8479893000?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/8481309920?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/8501539410?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/8501539910?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/8504405510?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/8504408410?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/8504409025?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/8504409030?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/8504409080?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/8504901810?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/8507908010?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/8507908060?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/8507908070?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/8507908080?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/8514101000?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/8514201000?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/8522902000?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/8526912030?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/8529101100?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/8529103100?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/8537209110?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/8537209910?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/8540120010?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/9017201000?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/9403109100?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/9405105000?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/9405109120?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/9405403990?day=1&month=1&year=2018
https://www.trade-tariff.service.gov.uk/trade-tariff/commodities/9608109200?day=1&month=1&year=2018
TRELLO CARD

 [TARIFF17] Duplicate commodity codes in search box and non-declarable commodity clickable/searchable


Enhancements. Fixes. & Ukrainian language

Enhancements:

Added a button to copy the text of the ADB command to the ADB dialog.
Added a dynamic color variable that depends on the system for the application icon (Alternative to monochrome icons).

Fix:

Corrected the layout of the settings window so that long sentences do not go beyond it (this is relevant for other languages, for example, Ukrainian).
Small change in the manifest for translating tile name when adding it.

Translation into Ukrainian
Full and optimized translation into Ukrainian. I hope this will start new translations into other languages for this useful small app.

Thanks a lot for your work. Everything looks good to me—I'll get it merged once the checks pass.


Please issue new release 1.0.4

Hi,
It seems Bitcoin has run of with a recent development snapshot of univalue and treated it as release 1.0.4.
Please formally issue a release 1.0.4, for those (like Debian) who prefer system-shared libraries tracking single unified upstream projects.
(or document if in fact this is a fork and the proper source is what is maintained by the Bitcoin project).

Here's the detail in Bitcoin: https://github.com/bitcoin/bitcoin/pull/12666

Done on August 31 in https://github.com/jgarzik/univalue/commit/88967f658663654a67f1cda93ca6f99de1f7c91f


docs: add yarn dev:full docks

Summary
Adding more info on how to run local services as currently we don't have this documented enough.

Awesome! Maybe we can add some info on how to run only the UI. That'll be helpful for frontend dev


enableBodyScroll unsuccessful on v2

Hey, thanks a lot for the amazing plugin, iv been using since v1 and today i have attempted to updated to v2 beta, and it was a breeze.
Just noticed a little error on the console that seems to root on TModal Component, and wanted to report, not sure if you have noticed:
enableBodyScroll unsuccessful - targetElement must be provided when calling enableBodyScroll on IOS devices
Node 12
VueTailwind 2.0.01
Vue 2
Not sure if this is already fixed on the current pull request but let me know if something needs to be done or set any option.
Once again thanks for the amazing work! :) Keep it up.

I did :disable-body-scroll="false", but it didn't change anything for me.

@D-Marc1  on the modal component?

Yes, I'm using the modal component. I now see I misread your post actually, as I'm using v1.3, and your question is about v2.

Yeah, but thanks for pointing this out, ill check if that works for me as temporary fix, otherwise will rollback back to 1.x until stable 👍

Same problem here

@igerslike maybe was fixed on2.0.0-2 didn't make a comprehensive test,

Btw 2.0 will include a default theme that still is a WIP so some components may look different if you didn't override the theme

that default theme will be awesome

A quick update here. Adding :disableBodyScroll="false" supresses the error, because it seems like it ignored the IF condition here :
https://github.com/alfonsobries/vue-tailwind/blob/ff241564694f868ef23a5a9665673da98f84ed20/src/components/TDialog.ts#L268
Also not sure if that matters but im using Vue-Portal to delivery the modals.

Just released v2 that should fix that problem, let me know @igerslike

@igerslike I'm gonna close this ticket for now but feel free to open it again if you still see the issue


cc build error - libgrpc_runtime.so missing

I got the same issue as documented here:
https://storage.googleapis.com/kubernetes-jenkins/pr-logs/pull/tensorflow_minigo/512/pull-tf-minigo-cc/384/build-log.txt
ERROR: missing input file '//cc:tensorflow/libgrpc_runtime.so'
when I tried to build the c++ version. Also in GRPC github nor in tensorflow a lib like this is visible. How to build this lib?

You will need to rerun `//cc/configure_tensorflow.sh', it was recently updated to build that library: https://github.com/tensorflow/minigo/commit/10410035dd2d73d153648dfc79c4d3e4e43ebd05#diff-dc0a2c249773d31d3d4755f00de5892d
Please reopen this issue if that doesn't fix your problem.

yes. correct. thx. after a bazel update to 18.1 and running configure_tensorflow.sh the lib is available.


Fixes integration tests from rattler-build 0.18.0 update

<EMAIL_ADDRESS>introduces a new check for the deprecated min_pin/max_pin arguments used in a number of JINJA pinning functions.
This simple regex replaces the terms with the new nomenclature, fixing the underlying issue.
In making this simple replacement, however, the integration tests started failing for the bioconda_recipes_02 data set. Diving deeper uncovered that yaml.dump() enforces a strict 80-character line limit by default, causing a number of unexpected issues when converting recipes. Fixing that greatly improved compatibility with all bioconda datasets, as many bioconda recipes exceed 80 characters in length on at least 1 line.

There is another outstanding issue with the latest version of rattler-build. It looks like they made some changes to tests/script and now the tests won't execute in a build. Looking into it...

@schuylermartin45 let me know what you find with regard to the script please. What changed is that in the tests you are supposed to be able to use the 'full' syntax now (including interpreter and other keys) which wasn't possible before.

But the simple version (e.g.
tests:
  script:
    - foo

Should continue to work.

Thanks, indeed, it looks like something is going wrong! I am debugging this.

I found the issue in rattler-build (in the test serialization). Fixing it up right now.

Wolf addresses this issue in https://github.com/prefix-dev/rattler-build/pull/946

Wolf's on 🔥 today, we have a point release: https://github.com/prefix-dev/rattler-build/pull/947


[turborepo] Install in FreeBSD

What version of Turborepo are you using?
1.7.0
What package manager are you using / does the bug impact?
npm
What operating system are you using?
Other
Describe the Bug
On 1.2.8 it was working totally fine: Now, I have this issue.
npm ERR! path /tank_data_1/clients/app/node_modules/turbo
npm ERR! command failed
npm ERR! command sh -c node install.js
npm ERR! /tank_data_1/clients/app/node_modules/turbo/node-platform.js:38
npm ERR!     throw new Error(`Unsupported platform: ${platformKey}`);
npm ERR!           ^
npm ERR!
npm ERR! Error: Unsupported platform: freebsd x64 LE
npm ERR!     at pkgAndSubpathForCurrentPlatform (/tank_data_1/clients/app/node_modules/turbo/node-platform.js:38:11)
npm ERR!     at checkAndPreparePackage (/tank_data_1/clients/app/node_modules/turbo/install.js:260:28)
npm ERR!     at Object.<anonymous> (/tank_data_1/clients/app/node_modules/turbo/install.js:310:1)
npm ERR!     at Module._compile (node:internal/modules/cjs/loader:1165:14)
npm ERR!     at Object.Module._extensions..js (node:internal/modules/cjs/loader:1219:10)
npm ERR!     at Module.load (node:internal/modules/cjs/loader:1043:32)
npm ERR!     at Function.Module._load (node:internal/modules/cjs/loader:878:12)
npm ERR!     at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
npm ERR!     at node:internal/main/run_main_module:22:47

Expected Behavior
A correct installation.
To Reproduce
npm i turbo@latest
Reproduction Repo
No response

same on platform (unix like):
linux s390x BE
turbo/node-platform.js  L19:
const knownUnixlikePackages = {   "darwin arm64 LE": "turbo-darwin-arm64",   "darwin x64 LE": "turbo-darwin-64",   "linux arm64 LE": "turbo-linux-arm64",   "linux x64 LE": "turbo-linux-64", };

Closing in favor of discussions on #7083.


chunkExtractor.getScriptElements returns nested array in 5.13.1

🐛 Bug Report
Public API for chunkExtractor.getScriptElements is described as being an Array of React

Yep, it could flatten scripts before returning.

@theKashey happy to pick this up if you're busy.

@markwoodward23 - that would be very good. It's like a few lines to change, but I don't have any time to work on this.

@theKashey - tried forking and install but I keep seeing this error:
FAIL  packages/server/src/ChunkExtractor.test.js
  ● Test suite failed to run

    Cannot find module '@loadable/component' from 'sharedInternals.js'

    However, Jest was able to find:
    	'./sharedInternals.js'

Any ideas?

@markwoodward23 sounds like you need lerna bootstrap or yarn build made at the top level.

@bendvc / @theKashey https://github.com/gregberge/loadable-components/pull/607


font list used for training/testing

It seems that the font_ttfs.zip includes many fonts and only a subset of it is used for training and testing. So could you please provide the font list you used?

It seems the log file output by our preprocess script will record which fonts are filtered out. Please check it out. Thanks!

You can also check the font id entry (pkl or dirs) in our dataset.

Thanks! The font id entry in pkl makes sense. But some fonts in font_ttfs.zip are corrupted. Anyway, I could get the ground truth font SVGs by running test_sf.py.


Ensure namespaces are entered in correct order

During exec namespaces were entered in arbitrary order. This leads to a high probability of the exec call failing because once a mount namespace is entered which contains /proc mounted by a process from a different pid namespace, we are unable to locate the rest of the namespaces we want to enter.

Codecov Report

Merging #674 (73d35a3) into main (e86f2b4) will decrease coverage by 0.00%.
The diff coverage is 90.00%.

@@            Coverage Diff             @@
##             main     #674      +/-   ##
==========================================
- Coverage   69.64%   69.64%   -0.01%
==========================================
  Files          84       84
  Lines       10990    10989       -1
==========================================
- Hits         7654     7653       -1
  Misses       3336     3336


Updated singular tests section to show they can now be documented

Resolves https://github.com/dbt-labs/docs.getdbt.com/issues/6132
What are you changing in this pull request and why?
The description property is available for singular data tests beginning in dbt v1.9, and this PR highlights how singular tests can now be documented.
🎩 Previews

document singular data tests
description
docs-paths
documentation placement

Checklist

[x] I have reviewed the Content style guide so my content adheres to these guidelines.
[x] The topic I'm writing about is for specific dbt version(s) and I have versioned it according to the version a whole page and/or version a block of content guidelines.
[ ] Wait until https://github.com/dbt-labs/dbt-core/pull/10792 is merged
[x] Add a note to the prerelease version Migration Guide

Log: moving this blocked in Kanban until status update from engineering

Closed off as Core project has been paused

Moved to https://github.com/dbt-labs/docs.getdbt.com/pull/6191


[SP-6276] Backport of PDI-19287 - "Ping a host": When you type a stri…

…ng in "Timeout (ms)", an execution is successful. (9.3 Suite)

:white_check_mark: Build finished in 26m 22s
Build command:
mvn clean verify -B -e -Daudit -amd -pl engine,ui

:exclamation: No tests found!
:information_source:  This is an automatic message


Material system crash on Mesa

I'm running current Mesa main branch from today after the fix for the previous bug was merged, I get that:
0x00005d5c10d1bf3a in MaterialSystem::GenerateWorldCommandBuffer (this=this@entry=0x5d5c118da000 <materialSystem>) at Unvanquished/daemon/src/engine/renderer/Material.cpp:1019
1019				surfaceCommand.drawCommand = material->drawCommands[drawSurf->drawCommandIDs[stage]].cmd;

Thread 1 (Thread 0x748b5b7bca80 (LWP 1844614) "daemon"):
#0  0x00005d5c10d1bf3a in MaterialSystem::GenerateWorldCommandBuffer (this=this@entry=0x5d5c118da000 <materialSystem>) at Unvanquished/daemon/src/engine/renderer/Material.cpp:1019
#1  0x00005d5c10d1d89e in MaterialSystem::AddAllWorldSurfaces (this=0x5d5c118da000 <materialSystem>) at Unvanquished/daemon/src/engine/renderer/Material.cpp:1501
#2  MaterialSystem::GenerateWorldMaterials (this=this@entry=0x5d5c118da000 <materialSystem>) at Unvanquished/daemon/src/engine/renderer/Material.cpp:1493
#3  0x00005d5c10d5bf18 in RE_RenderScene (fd=0x7ffda539fba0) at Unvanquished/daemon/src/engine/renderer/tr_scene.cpp:659
#4  0x00005d5c10c58adb in operator() (rd=..., __closure=<optimized out>) at Unvanquished/daemon/src/engine/client/cl_cgame.cpp:1731
#5  Util::apply_impl<CGameVM::CmdBuffer::HandleCommandBufferSyscall(int, int, Util::Reader&)::<lambda(refdef_t)>, std::tuple<refdef_t>, 0> (func=..., tuple=...) at Unvanquished/daemon/src/common/Util.h:136
#6  Util::apply<CGameVM::CmdBuffer::HandleCommandBufferSyscall(int, int, Util::Reader&)::<lambda(refdef_t)>, std::tuple<refdef_t> > (tuple=..., func=...) at Unvanquished/daemon/src/common/Util.h:141
#7  HandleMsg<CGameVM::CmdBuffer::HandleCommandBufferSyscall(int, int, Util::Reader&)::<lambda(refdef_t)>, IPC::Id<0, 45>, refdef_t> (func=..., reader=...) at Unvanquished/daemon/src/engine/client/cl_cgame.cpp:1529
#8  HandleMsg<IPC::Message<IPC::Id<0, 45>, refdef_t>, CGameVM::CmdBuffer::HandleCommandBufferSyscall(int, int, Util::Reader&)::<lambda(refdef_t)> > (func=..., reader=...) at Unvanquished/daemon/src/engine/client/cl_cgame.cpp:1534
#9  CGameVM::CmdBuffer::HandleCommandBufferSyscall (this=<optimized out>, major=<optimized out>, minor=<optimized out>, reader=...) at Unvanquished/daemon/src/engine/client/cl_cgame.cpp:1730
#10 0x00005d5c10ddc821 in IPC::CommandBufferHost::Consume (this=this@entry=0x5d5c111689d0 <cgvm+752>) at Unvanquished/daemon/src/engine/framework/CommandBufferHost.cpp:77
#11 0x00005d5c10ddc9e6 in operator() (__closure=<optimized out>) at Unvanquished/daemon/src/engine/framework/CommandBufferHost.cpp:48
#12 Util::apply_impl<IPC::CommandBufferHost::Syscall(int, Util::Reader&, IPC::Channel&)::<lambda()>, std::tuple<> > (tuple=..., func=...) at Unvanquished/daemon/src/common/Util.h:136
#13 Util::apply<IPC::CommandBufferHost::Syscall(int, Util::Reader&, IPC::Channel&)::<lambda()>, std::tuple<> > (tuple=..., func=...) at Unvanquished/daemon/src/common/Util.h:141
#14 IPC::detail::HandleMsg<IPC::CommandBufferHost::Syscall(int, Util::Reader&, IPC::Channel&)::<lambda()>, IPC::Message<IPC::Id<7, 1> >, IPC::Reply<> > (func=..., reader=..., channel=...) at Unvanquished/daemon/src/common/IPC/Channel.h:217
#15 IPC::HandleMsg<IPC::SyncMessage<IPC::Message<IPC::Id<7, 1> > >, IPC::CommandBufferHost::Syscall(int, Util::Reader&, IPC::Channel&)::<lambda()> > (func=..., reader=..., channel=...) at Unvanquished/daemon/src/common/IPC/Channel.h:241
#16 IPC::CommandBufferHost::Syscall (this=0x5d5c111689d0 <cgvm+752>, index=<optimized out>, reader=..., channel=...) at Unvanquished/daemon/src/engine/framework/CommandBufferHost.cpp:47
#17 0x00005d5c10c571dc in CGameVM::Syscall (this=<optimized out>, id=<optimized out>, reader=..., channel=...) at Unvanquished/daemon/src/engine/client/cl_cgame.cpp:1069
#18 0x00005d5c10c4c97a in VM::VMBase::SendMsg<IPC::SyncMessage<IPC::Message<IPC::Id<(unsigned short)0, (unsigned short)3>, int, bool>, IPC::Reply<> >, int&, bool&>(int&, bool&)::{lambda(unsigned int, Util::Reader)#1}::operator()(unsigned int, Util::Reader) (reader=..., id=458753, __closure=0x7ffda53a02a0) at Unvanquished/daemon/src/engine/framework/VirtualMachine.h:141
#19 IPC::detail::SendMsg<VM::VMBase::SendMsg<IPC::SyncMessage<IPC::Message<IPC::Id<(unsigned short)0, (unsigned short)3>, int, bool>, IPC::Reply<> >, int&, bool&>(int&, bool&)::{lambda(unsigned int, Util::Reader)#1}&, IPC::Message<IPC::Id<(unsigned short)0, (unsigned short)3>, int, bool>, IPC::Reply<>, int&, bool&>(IPC::Channel&, VM::VMBase::SendMsg<IPC::SyncMessage<IPC::Message<IPC::Id<(unsigned short)0, (unsigned short)3>, int, bool>, IPC::Reply<> >, int&, bool&>(int&, bool&)::{lambda(unsigned int, Util::Reader)#1}&, IPC::SyncMessage<IPC::Message<IPC::Id<(unsigned short)0, (unsigned short)3>, int, bool>, IPC::Reply<> >, int&, bool&) (channel=..., messageHandler=...) at Unvanquished/daemon/src/common/IPC/Channel.h:174
#20 0x00005d5c10c4cbf7 in IPC::SendMsg<IPC::SyncMessage<IPC::Message<IPC::Id<(unsigned short)0, (unsigned short)3>, int, bool>, IPC::Reply<> >, VM::VMBase::SendMsg<IPC::SyncMessage<IPC::Message<IPC::Id<(unsigned short)0, (unsigned short)3>, int, bool>, IPC::Reply<> >, int&, bool&>(int&, bool&)::{lambda(unsigned int, Util::Reader)#1}, int&, bool&>(IPC::Channel&, VM::VMBase::SendMsg<IPC::SyncMessage<IPC::Message<IPC::Id<(unsigned short)0, (unsigned short)3>, int, bool>, IPC::Reply<> >, int&, bool&>(int&, bool&)::{lambda(unsigned int, Util::Reader)#1}&&, int&, bool&) (messageHandler=..., channel=...) at Unvanquished/daemon/src/common/IPC/Channel.h:234
#21 VM::VMBase::SendMsg<IPC::SyncMessage<IPC::Message<IPC::Id<(unsigned short)0, (unsigned short)3>, int, bool>, IPC::Reply<> >, int&, bool&>(int&, bool&) (this=<optimized out>) at Unvanquished/daemon/src/engine/framework/VirtualMachine.h:139
#22 CGameVM::CGameDrawActiveFrame (demoPlayback=<optimized out>, serverTime=<optimized out>, this=<optimized out>) at Unvanquished/daemon/src/engine/client/cl_cgame.cpp:997
#23 CL_CGameRendering () at Unvanquished/daemon/src/engine/client/cl_cgame.cpp:655
#24 0x00005d5c10c7659d in SCR_DrawScreenField () at Unvanquished/daemon/src/engine/client/cl_scrn.cpp:266
#25 0x00005d5c10c76627 in SCR_UpdateScreen () at Unvanquished/daemon/src/engine/client/cl_scrn.cpp:318
#26 0x00005d5c10c6afdd in CL_Frame (msec=msec@entry=3) at Unvanquished/daemon/src/engine/client/cl_main.cpp:2074
#27 0x00005d5c10bfdc1c in Com_Frame () at Unvanquished/daemon/src/engine/qcommon/common.cpp:958
#28 0x00005d5c10bf71ed in Application::ClientApplication::Frame (this=0x5d5c10f0cea0 <Application::GetApp()::app>) at Unvanquished/daemon/src/engine/client/ClientApplication.cpp:96
#29 0x00005d5c10bf6815 in main (argc=<optimized out>, argv=<optimized out>) at Unvanquished/daemon/src/engine/framework/System.cpp:750

This doesn't crash in Mesa anymore, but the engine still crashes.

Which map is this on? It does not seem to be a driver issue at least.

Oh, this is probably because of heathaze, since I changed Render_heatHaze() to just do a return; rather than Tess_DrawElements() when building material system buffers, so material->drawCommands[drawSurf->drawCommandIDs[stage]].cmd never gets set for it.
I'll see if I can make heathaze work with material system later today, I think just splitting it into 2 stages and making the second stage dynamic (since it does gl_heatHazeShader->SetUniform_CurrentMapBindless( 		GL_BindToTMU( 1, tr.currentRenderImage[1 - backEnd.currentMainFBO] )  	);) should work.

Which map is this on? It does not seem to be a driver issue at least.

I guess plat23, that's usually the first map I test.

Which map is this on? It does not seem to be a driver issue at least.

I guess plat23, that's usually the first map I test.

This tracks with the above, since heathaze was added to plat23.

Confirmed crashing on plat23 with heatHaze. Will fix in a bit.


chore(Exp): Add EBS Loss Experiment in GO

Signed-off-by: Udit Gaurav<EMAIL_ADDRESS>Details

This PR is for adding the EBS Loss experiment in GO which includes the EBS volume detachment and attachment chaos.

ChaosResult
Name:         nginx-chaos-disk-loss
Namespace:    default
Labels:       app.kubernetes.io/component=experiment-job
              app.kubernetes.io/part-of=litmus
              app.kubernetes.io/version=latest
              chaosUID=9f13427b-cc5c-4fad-b683-764b7567699c
              controller-uid=8012962a-54d2-4250-990c-dc105857f2e0
              job-name=disk-loss-z3mud3
              name=nginx-chaos-disk-loss
Annotations:  kubectl.kubernetes.io/last-applied-configuration:
                {"apiVersion":"litmuschaos.io/v1alpha1","kind":"ChaosResult","metadata":{"annotations":{},"labels":{"chaosUID":"054dea0f-8a20-4b33-985c-56...
API Version:  litmuschaos.io/v1alpha1
Kind:         ChaosResult
Metadata:
  Creation Timestamp:  2020-10-22T13:41:38Z
  Generation:          77
  Resource Version:    23619647
  Self Link:           /apis/litmuschaos.io/v1alpha1/namespaces/default/chaosresults/nginx-chaos-disk-loss
  UID:                 7e26ecc0-1b7e-4be6-84ad-9d3eb0c20948
Spec:
  Engine:      nginx-chaos
  Experiment:  disk-loss
Status:
  Experimentstatus:
    Fail Step:  N/A
    Phase:      Completed
    Verdict:    Pass
Events:
  Type    Reason   Age   From                    Message
  ----    ------   ----  ----                    -------
  Normal  Awaited  31m   disk-loss-wl9h86-mxxgm  experiment: disk-loss, Result: Awaited
  Normal  Pass     30m   disk-loss-wl9h86-mxxgm  experiment: disk-loss, Result: Pass

Experiment Log
udit@ubuntu ~> kubectl logs -f disk-loss-z3mud3-s26tf
W1024 20:20:34.086261       1 client_config.go:541] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
time="2020-10-24T20:20:34Z" level=info msg="Experiment Name: ebs-loss"
time="2020-10-24T20:20:34Z" level=info msg="[PreReq]: Getting the ENV for the  experiment"
time="2020-10-24T20:20:34Z" level=info msg="[PreReq]: Updating the chaos result of disk-loss experiment (SOT)"
time="2020-10-24T20:20:34Z" level=info msg="The application information is as follows" Ramp Time=0 Device Name=/dev/sdf Namespace=default Label="run=nginx"
time="2020-10-24T20:20:34Z" level=info msg="[Status]: Verify thadisk-status-check.got the AUT (Application Under Test) is running (pre-chaos)"
time="2020-10-24T20:20:34Z" level=info msg="[Status]: Checking whether application containers are in running state"
time="2020-10-24T20:20:34Z" level=info msg="[Status]: The running status of container are as follows" container=nginx Pod=nginx-7bb7cd8db5-fcb5n Status=Running
time="2020-10-24T20:20:36Z" level=info msg="[Status]: Checking whether application pods are in running state"
time="2020-10-24T20:20:36Z" level=info msg="[Status]: The running status of Pods are as follows" Pod=nginx-7bb7cd8db5-fcb5n Status=Running
time="2020-10-24T20:20:38Z" level=info msg="[Authentication]: Creates directory for aws configuration"
time="2020-10-24T20:20:38Z" level=info msg="[Authentication]: Creating credential file in aws directory"
time="2020-10-24T20:20:38Z" level=info msg="[Authentication]: Copying aws credentials from cloud_config"
time="2020-10-24T20:20:38Z" level=info msg="The selected instance information is as follows:" Instance Id=i-02423ef800178b9b1 Instance Type=t3.medium KeyName=udit-ec2
time="2020-10-24T20:20:38Z" level=info msg="The selected EBS volume information is as follows:" DeviceName=/dev/sdf VolumeId=vol-0ecdd0f5b7880184f Status=attached
time="2020-10-24T20:20:38Z" level=info msg="[Chaos]: Detaching the EBS volume from the instance"
time="2020-10-24T20:20:38Z" level=info msg="Detaching ebs having:" VolumeId=vol-0ecdd0f5b7880184f State=detaching Device=/dev/sdf InstanceId=i-02423ef800178b9b1
time="2020-10-24T20:21:38Z" level=info msg="[Chaos]: Attaching the EBS volume from the instance"
time="2020-10-24T20:21:38Z" level=info msg="Attaching ebs having:" InstanceId=i-02423ef800178b9b1 VolumeId=vol-0ecdd0f5b7880184f State=attaching Device=/dev/sdf
time="2020-10-24T20:21:38Z" level=info msg="[Confirmation]: EBS loss chaos has been injected successfully"
time="2020-10-24T20:21:38Z" level=info msg="[Status]: Verify that the AUT (Application Under Test) is running (post-chaos)"
time="2020-10-24T20:21:38Z" level=info msg="[Status]: Checking whether application containers are in running state"
time="2020-10-24T20:21:38Z" level=info msg="[Status]: The running status of container are as follows" container=nginx Pod=nginx-7bb7cd8db5-fcb5n Status=Running
time="2020-10-24T20:21:40Z" level=info msg="[Status]: Checking whether application pods are in running state"
time="2020-10-24T20:21:40Z" level=info msg="[Status]: The running status of Pods are as follows" Status=Running Pod=nginx-7bb7cd8db5-fcb5n
time="2020-10-24T20:21:43Z" level=info msg="The selected instance information is as follows:" KeyName=udit-ec2 Instance Id=i-02423ef800178b9b1 Instance Type=t3.medium
time="2020-10-24T20:21:43Z" level=info msg="The selected EBS volume information is as follows:" VolumeId=vol-0ecdd0f5b7880184f Status=attached DeviceName=/dev/sdf
time="2020-10-24T20:21:43Z" level=info msg="[The End]: Updating the chaos result of disk-loss experiment (EOT)"


Cannot override configurations from cockpit/custom/config.php

Overriding default configurations from cockpit/custom/config.php file does not working:
Here is the configuration file:
return [
    'app.name' => 'Demo Website',
    'session.name' => 'session',
    'sec-key'      => 'HelloWorld',
    'i18n'         => 'en'
];

and the app index.php file:

require_once __DIR__ . '/admin/bootstrap.php';

$app = new Lime\App();
$app->path('views', __DIR__.'/views');
$app->get('/', function() use($app) {
    return $app->render('views:index.php');
});

$app->run();

var_dump($app);

Here is result:
object(Lime\App)#21 (10) {
  ["registry":protected]=>
  array(15) {
    ["debug"]=> bool(true)
    ["app.name"]=>  string(7) "LimeApp"
    ["session.name"]=> string(14) "limeappsession"
    ["sec-key"]=> string(36) "xxxxx-SiteSecKeyPleaseChangeMe-xxxxx"
    ["route"]=> string(1) "/"
    ["charset"]=> string(5) "UTF-8"
    ["helpers"]=>  array(0) {    }
    ["base_url"]=>  string(0) ""
    ["base_route"]=>  string(0) ""
    ["base_host"]=>   string(17) "local.cockpit.com"
    ["base_port"]=>   string(2) "80"
    ["docs_root"]=>   string(29) "Z:/home/local.cockpit.com/www"
    ["site_url"]=>    string(24) "http://local.cockpit.com"
  }
  ....

as you can see "sec-key" didn't changed.

There are actually two instances of Lime used in your project. Cockpit itself has one instance which loads the custom config as you want.
However, when you create your own $app = new Lime\App();, this is a new instance, that doesn't use the custom config.
If you want to load the custom config on your own Lime instance as well, just hand in the config array to the constructor. Something like this could work (haven't tried):
$config = require("cockpit/custom/config.php");
$app = new Lime\App($config);

// ...

Thanks


Improved README rendering on GitHub

Hi Cory, I made some small changes so the table with dependencies is rendering properly on GitHub.

Thanks!


add update resource definition workflow

add get_ctx_from_kwargs to utils
get ctx in several functions
#71

This approach is needlessly complicated and possibly brakes a lot of functions that work.


Update Upptime to latest, add config

Hi @alanhamlett, thanks for using @upptime! We've made some changes to how the template works, and this PR updates it to the latest version.
Here are some changes:

All legacy code is now gone, and it uses the Upptime GitHub Action and npm package (3bd078b)
I've taken the liberty of adding the @wakatime logo as the favicon from your site (b7e9e66)
I noticed that you wanted to link the logo to https://wakatime.com (you did that in 9b0d04b), so I've added that as a configuration parameter now
I've also removed the older docs from the README for a cleaner repository

All these changes are already tested and work perfectly: https://github.com/koj-co/status (you can take my word for it!)

I've resolved the conflicts with the new version of README.md

Awesome, thank you!


Unexpected token in components/Dialog.js

while I upgrade 0.5.20 -> 0.7.22
it shows the error below at runtime:
node_modules/react-native-popup-dialog/src/components/Dialog.js: Unexpected token, expected , (16:14)
seems the problem is at
import { type DialogType} from ...
run on:
react 15.4.2
react-native 0.41.2
any suggestion??

Getting the same error ^^^^

@vault13tech @joegoodall1 I tried but I didn't get the error  🤔

Problem seems to have resolved itself. Thanks for replying so quickly.

interesting...
@jacklam718 I'll try to figure out what happened
@joegoodall1 is there any clue to be notice??

@vault13tech Thanks a lot

This error seems to be back now when trying to build apk for release?

Just noticed in the packager that react-native-pop-up-dialog gets missed out?
:react-native-linear-gradient:transformNative_libsWithSyncJniLibsForRelease UP-TO-DATE :react-native-linear-gradient:bundleRelease UP-TO-DATE :react-native-sound:preBuild UP-TO-DATE :react-native-sound:preReleaseBuild UP-TO-DATE

@vault13tech @joegoodall1 Can you try install this version 0.7.23 ? This version might be can solve  the issue.

at first, I tried to upgrade to 0.7.23 directly, it show some error message at runtime,
then I just uninstall and reinstall again, it works just fine! (how strange).
thank you @jacklam718 , excellent works :+1:

@vault13tech Nice.

oh!! we got problems.
when I tried to build a app release, the error shown:
TransformError: \Projects\ProjectA\node_modules\react-native-popup-dialog\index.js: Unknown plugin "flow-react-proptypes" specified in "\\Projects\\ProjectA\\node_modules\\react-native-popup-dialog\\.babelrc" at 0, attempted to resolve relative to "\\Projects\\ ProjectA\\node_modules\\react-native-popup-dialog"

@vault13tech So sorry. I will fix it.

@jacklam718
I change .babelrc from
"plugins": ["babel-plugin-flow-react-proptypes"]
to
"env": { 	"development": { 		"plugins": ["babel-plugin-flow-react-proptypes"] 	} }
it will only work on development

@vault13tech Can you try install this version 0.7.24 thanks.

@jacklam718 I accidentally install the version: 0.7.26 :smile:
and it seems works fine both on development & release build.
thanks again :smile:

@vault13tech Nice. So sorry about that 😅


Update to 0.6.4

Updated my repository to 0.6.4

@moleculartear could you please take a look?

Thank you!


Naming inconsistency

The package is called sometimes "fabrikam-function" or "fabrikam-functions".

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

ID: e656bde5-b5d8-8d80-b7b3-ab430e57613e
Version Independent ID: 329eb12f-7302-4ecf-c1bf-a50ba3f34bdf
Content: Create your first function in Azure with Java and Maven
Content Source: articles/azure-functions/functions-create-first-java-maven.md
Service: functions
GitHub Login: @rloutlaw
Microsoft Alias: routlaw, glenga

Thanks for the feedback! We are currently investigating and will update you shortly.

@algattik I addressed the inconsistencies. Once the PR merges this issue will close and the changes will go live in a few hours.
Thanks!


Feat/sentry-integration

This adds Sentry integration to the dashboard which will report any
errors or issues. In the future, we can add a modal as well where the
user can provide their own feedback.
For the CI workflow it is strongly advised we add SENTRY_AUTH_TOKEN environment variable with an auth token and provide it to the production build on both prod and stg. Likewise for VITE_SENTRY_DSN with the dsn value

Fixes #239
RELEASE NOTES BEGIN
Added Sentry integration to dashboard
RELEASE NOTES END

@lbarcziova I changed it. If you want we can rotate the dsn as well but I doubt it'll be an issue

@lbarcziova Np! Feel free to merge when the environment variables are in the CI/deployment process for stg prod


Upgrade to Swift 4.1

For details, please see commit notes.
Note: Must not be merged before Xcode 9.3 is out of beta, as the changes require Swift 4.1.

@shagedorn Thank you for Pull Request. I commented some change request. Can you please fix them?

 I cannot see any comments other than your summary.

@shagedorn I forgot to submit reviews, sorry.

I don't really understand why my latest changes affect code coverage so severely. Any hints appreciated.

@kishikawakatsumi do you have any feedback on this one?

Xcode 9.3 is out. I will merge these changes soon, thank you! @shagedorn

…feel free to take a look why the code coverage has dropped so badly, I cannot really explain this.

@shagedorn This PR is superseded by https://github.com/kishikawakatsumi/KeychainAccess/pull/376. I added some commit to your PR. Thank you very much for contributing!!


Need documentation to show how to run k3s with an external cloud-controller-manager

Version:
k3s version v0.10.2 (8833bfd9)

Describe the bug
When running with a cloud-controller-manager (which one should do, since everything is out of tree), at various calls, it is expected to pass the node provider ID to the ccm as <provider>://<id>.
k3s, though, passes it as k3s://<hostname>. This makes a CCM reject it.

To Reproduce

Deploy k3s (which is so nice and easy :-) )
Deploy a ccm for whatever provider you are in (I have been working on Packet's)
Look at the logs, see a message like: provider name from providerID should be packet: k3s://ccm01 (replace for your provider)

Expected behavior
The provider ID passed should be composed of <provider>://<id>

Actual behavior
It gives k3s://<hostname>

Additional context

By default k3s will run internal cloud provider, this will add k3s:// as provider and add node name as id, to disable this default cloud provider and run your own, you can pass --disable-cloud-controller to the server and run your own ccm.

Thanks. Are there docs somewhere? And do I need to do anything else to enable it, set up —cloud-provider=external?

It's enabled (our own cloud provider for external ip capability) if you pass the --node-external-ip flag with value. e.g. --node-external-ip=x.x.x.x That's all you should have to do.
Docs aren't great (trying to improve that) but it's listed here as a flag and also listed in --help in cli
https://rancher.com/docs/k3s/latest/en/installation/single-server/

If you pass --disable-cloud-controller then our cloud controller will be completely disabled.

@deitch Just to clarify, --disable-cloud-controller will disable our own implementation of ccm, so if you still need to run an external ccm you need to pass cloud-provider=external to kubelet extra_args, and start the ccm as a pod in the system

Yup. I’ve got the starting it separately. How do I tell k3s to pass the extra commands? Is it documented?

yeah its documented, its:
--kubelet-arg value                        (agent/flags) Customized flag for kubelet process

So —disable-cloud-controller —kubelet-arg —cloud-provider=external ?

yup, and pass kube-arg for workers as well

Is there any way to put this in some bootstrap config file, so I can run the usual k3s installation but it will pick it up?

Hmm, apparently args passed to --kubelet-arg add on their own -- at the beginning, so my line above:
k3s server --disable-cloud-controller --kubelet-arg --cloud-provider=external

Resulted in kubelet running as
----cloud-provider=external

Apparently, I need to do it as:
k3s server --disable-cloud-controller --kubelet-arg cloud-provider=external

Is that documented?

I can confirm that this works. I think if the documents somewhere showed, "how to run k3s with your own cloud-controller-manager" (or similar), we can close this issue out. It is just a documentation issue, not a code issue.
I will rename it. :-)

Turned this into a documentation issue

@deitch Just to clarify, --disable-cloud-controller will disable our own implementation of ccm, so if you still need to run an external ccm you need to pass cloud-provider=external to kubelet extra_args, and start the ccm as a pod in the system

This is inconsistent with the documentation PR that closed this issue.  It just mentions --disable-cloud-controller
See https://github.com/k3s-io/docs/pull/98/files#diff-1a7a1207c35dc4e390f7a6ebcd2e0b5f6fa9f8ebab16c1c409179ca6d69d65ecR86
Is the documentation correct?

Greetings!
I have done everything what mentioned above, but it's not worked for me.
I have only one server and it is run with command:
ExecStart=/usr/bin/k3s server --disable=servicelb --disable=traefik --disable-cloud-controller --kubelet-arg="cloud-provider=external"

bit my providerID is not changed: providerID: k3s://
what am I doing wrong?

You cannot change the providerID once the node has been added to the cluster. Changing the providerID can only be done by deleting the node and re-joining it. This is partly why we do not support changing the cloud provider on a running cluster.

Thanks for your reply, tell me please, how to do it Changing the providerID can only be done by deleting the node and re-joining it ? I have only one node:
➜  ~ kubectl get nodes
NAME            STATUS   ROLES                        AGE    VERSION
kub-00          Ready    control-plane,master   23d    v1.27.4+k3s1

I added this flags --disable-cloud-controller --kubelet-arg="cloud-provider=external" and restarted the k3s server, it is not helped.

Delete the node with kubectl, then restart k3s?


Trust artifacts and protocols

We should add:

normative text about the Entity Configuration and Metadata for all entities
protocol details (normative and non-normative examples) about how the trust must be established

@fmarino-ipzs in which section it is supposed to be done?
I would suggest to move this in the next milestone, since we're working with other member states in several contexts on this topic.
Once we'll have completed the work we'll be therefore able to merge in this specification the relevan parts for the resolution of this issue

The first part of this issue is covered by PR #328. I will create a new issue about the second part.

The new issue can be found in Issue #332


:sparkles: Add TCP Kiss

Add the capability to use Kiss TCP connection #2.
I tested with the Direwolf console where I see packets but not in "live". I'll try it soon but I'm confident.
Do what you want with my PR :)

Looking good! I'll try this out shortly and merge if it works as expected :) Thanks for the pull request!

Thanks for the patch! It's merged now. I changed the option format for KISS TCP a bit, to make it unambiguous, and also changed your bcopy and bzero calls, since they have been deprecated from the POSIX specs in favor of the mem... functions. If there's some specific reason you used the BSD variants that I have missed, please let me know!
I'll test this out with Direwolf over the air now, and if it all seems to work as it should, I'll compile and release it all as version 0.1.8 :)
Oh, and please don't take this the wrong way, just a word of advice, but when you change all the indentation in a file from tabs to spaces, and then do all your changes in the same commit, it's practically impossible for the poor maintainer (eg., me) to see what you changed in the diff. I don't have anything against spaces, but please maybe keep it in a separate commit ;)

Thanks a lot for the merge !
I did not find the time to test over the air yet but I will !
My projet is an Orange Pi on solar panel connected to Hamnet (2.3 Ghz) and I want a link in UHF. Soon in "prod" I hope.
I'm not a C developer at all (only for hobbies) so do not care for bcopy. I'm not aware of deprecated functions :)
Sorry for all indentation. My IDE has certainly formated all files when I commited and I didn't notice it.

Ah, very cool project! No worries with the indent, it just took some more time to get the diff sorted out, just wanted to let you know. All good with the memory functions then!
Please let me know how it goes when you have tested it as well, I am interested in the feedback!

And it's released as version 0.1.8 :) Everything is looking good so far. I tested it over the air with a couple of FTP transfers between one computer running DireWolf and another with an OpenModem.
Let me know if you find any bugs or hiccups.


html encoding issue

Hi kalvn ,
when I'm editing a link, shaarli is showing the html encoding code:

Moreover, when I'm adding a link like https://budgetparticipatif.paris.fr/bp/jsp/site/Portal.jsp?document_id=1959&portlet_id=123.
& gets encoded into &. And it gets saved with the badly encoded form.
I'm having the problem since a long time actually.
Of course it might be a problem on my side.
I'm using last version (master) of shaarli community and of your theme.
Thanks
J.

For more information, see my comment here: https://github.com/shaarli/Shaarli/issues/352#issuecomment-140360056
Thanks for the feedback, jeekajoo.

Looks like you fixed it with https://github.com/kalvn/Shaarli-Material/commit/10f77f3df928a1977a138a3bf2a1cac267351077
This is great. Thanks


feat(AlgebraicGeometry/RingHomProperties): a property induced from Locally Q is equivalent to locally Q

If P is a morphism property of schemes associated to the property Locally Q for a property of ring homomorphisms Q, then for a morphism f, P f is equivalent to: for every point x in the source there exist open affine neighborhoods around x and f.val.base x respectively such that the induced map of rings satisfies Q.
This guarantees that we may define properties of scheme morphisms explicitly as described above for properties of ring homomorphisms that are not necessarily local at the target and still use the API for HasRingHomProperty.

[x] depends on: #17032
[x] depends on: #17302

bors merge


Decrease contrast in dark mode

Changes text colour to #ddd
It's a smal tweek but worth it. The current website hurts my eyes. I have to resort to a JavaSoypt dark theme plugin on this already beautiful site. Thoughts?
I would have gone for #ccc but I though I would be pushing it.
To many sites these days have a "dark mode" which is lighter than what I get with a plugin. It's embarrasing.

Can you show a visual preview of the changes? Thanks. @torresjrjr

@DGKSK8LIFE
Here's a preview I made with comparisons and annotations.


fix: WAF block based on inputs and IP reputation

Summary
Enable request blocking based on requests that have known bad input
(e.g. the Log4j exploit) or are from IP addresses with a poor
reputation score.
A subsequent PR will be created to enable logging so we can determine
which additional AWS managed rules can be set to block as well.
Related

cds-snc/platform-sre-security-support#75

its that simple? lgtm but I dont know what I am approving so will wait for someone else.

Yup, it's definitely an "easy change, high impact" kind of situation 😅
If we set all the managed rules to block we'd definitely mess with some legitimate Notify requests because of things like large request body size or missing user agent headers.


Nightly Builds Fail [API-1527]

Release builds of all nightly builds fail as seen here.

Only release builds fail for Ubuntu and MacOS.
All builds fail for Windows. For Windows problem seems to be related to boost install.
Logs:
Ubuntu Logs.zip
MacOS Logs.zip
Windows Logs.zip
"

Changing windows version to 2019 fixes boost installation error.

Ubuntu builds fail because of undefined reference error and fix #1022 also solves this issue.
MacOS release builds fail because we treat a warning as an error and new version of boost which generates a warning message which tells that language standard of Boost.Math module will be increased to C++14 in July 2023.
Windows builds fail because windows-latest update to windows-2022 and it comes with VS17-2022 toolchain which boost is compilable only after 1.78 version but the action downloads 1.76.0.


Pass dynamic base url to Angular app

Hi,
I'm trying to solve a problem where an application may pre-configure some variables before linking to the child app, providing the selections via the path. So the child app would be routed something like this:
/:variable1/:variable2/my-child-app
Doing the matching is not problem but, the issue is that the APP_BASE_HREF in my angular apps needs to be dynamic and the Angular app needs access to the variables matched by the wildcards.
Is there any way of passing information into the Angular app when loading it? I'm not sure if this is the sort of thing that props can be used for? I took a look but I couldn't see a way to use them like this. I could use local/session storage but I thought maybe there was a cleaner way via single-spa[-angular-cli].
Thanks

Obviously in this case I could take the first two parts of the path but I'd like my child app not to have to know about where it is until it's loaded.

Hello @freon27, I undersand the issue, the variable are in use on the main portal app or inside the my-child-app? Or both?

They would be used inside the child apps. To be honest, since I asked the question I've fed this back to management as not possible (or at least something we shouldn't do).  It feels very messy (although I would still be interested to know how one might pass context information to child apps when they are loaded)

This project is deprecated (see #36). Use single-spa-angular@3, instead.


Linker errors

I get linker errors while trying to use libnabo (inside a ros node) - when I compile (in Ubuntu) from catkin_ws the linker throws an error:
undefined reference to `Nabo::NearestNeighbourSearch<float, Eigen::Matrix<float, -1, -1, 0, -1, -1> >::createKDTreeLinearHeap(Eigen::Matrix<float, -1, -1, 0, -1, -1> const&, int, unsigned int, Nabo::Parameters const&)'
undefined reference to `Nabo::NearestNeighbourSearch<float, Eigen::Matrix<float, -1, -1, 0, -1, -1> >::knn(Eigen::Matrix<float, -1, 1, 0, -1, 1> const&, Eigen::Matrix<int, -1, 1, 0, -1, 1>&, Eigen::Matrix<float, -1, 1, 0, -1, 1>&, int, float, unsigned int, float) const'
collect2: error: ld returned 1 exit status
I had built from source using the master branch ...

Probably you are effectively linking to an outdated version of nabo.a or nabo.so. Could you please double check that you are not linking to a different version of libnabo? E.g. by running make VERBOSE=1 in the build/libnabo folder of your catkin_workspace and parsing the linker arguments for nabo?
It should point into the appropriate devel space.
If that is the case please try to resolve or report back.
If that is the not the case try run make install in the build/libnabo folder and link (build) your client code again after that.

Seems obsolete. Closing it.


Added angle widget, some changes on ruler and on ROI

The ruler and the angle can be moved dragging the lines or the text boxes. The angle needs to be initialized with 3 handles. So the first three input points should be temporarily captured outside of the Widget.

@jgonzabal can you please remove the build files?


Auth Credentials: Default values

Closes https://github.com/3scale-labs/authorino/issues/71

default KeySelector is Bearer
default In (location) is authorization_header

@didierofrivia, do we need to change something here as well maybe?
https://github.com/3scale-labs/authorino/blob/578b9a7f7e6ad1ce8c8fcaff4f98699a83adbacc/controllers/service_controller.go#L109-L112


Enable macros to create an alert

Hello @SalieriC, I'm not sure I fully understand the question. You can already create an alert with a macro. I would encourage you to check out the Turn Alert Wiki as well as the example macros compendium included with the module. Those should be a good starting point at least. Once you've looked through those, if you have a specific question ping me in the #macro-polo channel in the Foundry discord (@cole#9640).
If I've misinterpreted your question somehow, feel free to reopen the issue.


Wse Acceptor: Missing HTTP header: X-WebSocket-Protocol in response

Wse k3po spec test failed
file:
gateway.transport.wseb/src/test/java/org/kaazing/gateway/transport/wse/specification/ws/acceptor/OpeningHandshakeIT.java
test:
requestHeaderWebSocketProtocol()

Fixed in PR https://github.com/kaazing/gateway/pull/418


Prepare for bazaar MVP

When https://github.com/encointer/encointer-node/pull/93 is merged, the node will incorporate all the basics for the bazaar.
This means we can revive the bazaar in the app. The dart side might need some updates because the modules have been commented out, but the wallet's bazaar structure is still valid.
We need:

JS: extra functions to query the new bazaar-rpcs (the logic can be copied from communities_getAll, add them here, or in a separate module.
Dart + JS: the legacy xxxShopRegistry calls must use one the new bazaar rpcs. This is in  apiEncointer
Dart: The transaction details to create new shop must be renamed to the new extrinsics name. This is in createShopForm
Dart: Add transaction to create Offerings, I don't think that this exists yet?
Dart + JS: Rebrand all the Shop fields to Business and Article to Offering
Update encointer-js: This might be problematic.
Dart: Ipfs uploads to localhost, make this configurable and make the default be gesell.encointer.org:8080

@clangenb whats the status here? I remember refactoring all the shop data to business and also implementing the rpc calls for businesses.
is this still open?


@sweir27 => [Auction] Hide / swap fields if sale

Addresses a few more things caught in QA desktop / mobile:

On mobile, the info window pop up needed a swapped 'Sale' title; hidden Auctions FAQ button; hidden time if empty or invalid

Hidden auction time if missing / invalid

Hidden clock if no end_at:

Toggle Clock text on closed

Merging per offline discussion 👍


Agent example for v1.0 release

Description

Add retrieval mega-service as tool for agent
Enabled llama3.1-70B-instruct served by TGI-gaudi as llm engine for agents

Issues
https://github.com/opea-project/GenAIExamples/issues/489
https://github.com/opea-project/GenAIExamples/issues/491
Type of change
List the type of change like below. Please delete options that are not relevant.

[x] New feature (non-breaking change which adds new functionality)

Dependencies
No new dependencies
Tests
test_agentqna_on_gaudi.sh

@minmin-intel , what is the retrival service  differs with the one here: https://github.com/opea-project/GenAIExamples/tree/main/DocIndexRetriever.
Any chance you can update that one to meet your demand?


ENH: Allow 2D input in cum_returns_final.

Fixes https://github.com/quantopian/empyrical/issues/100

lgtm

lgtm, thanks @ssanderson!


Sharing the same DNS with another cluster

Hi,
I have created a k8s cluster and installed BKPR on top of it. its working fine, I have used dev.xyz.com dns domain for this.
I would like to create another isolated k8s cluster and want to install BKPR and use the same DNS domain. Would this works?
Thanks,
Rajashekhar

Hi,
Could you provide more information about the installation mode you used? If you used azure or google I think conflicts with the dns entries may appear.

i'm using azure(aks).

Hi,
Then I think that some conflicts could potentially appear. My advice would be using different domains.


fix(android): avoid send event when has no listener

Overview

This commit just make sure that module will not  read MAC info before add listener for it.
Everytime createConnectivityEventMap method called when send event, it will get wifiinfo.
It's illegal in China when app read MAC info before user agree the privacy agreement.
Test Plan

Thanks @mikehardy. I think you are right that we need explicit APIs to init/destroy this lib. But I do think sending event when there's no listener is also something need to optimize. For now we will use patch-package as a workaround, would love to follow the progress of the change you mensioned.

I think that's a little bit of a misunderstanding of how it will go. I'm just a volunteer on the internet, and I don't personally care about this use case in the sense that I need it for any work projects. So I'm not going to personally touch the code. That's how open source works - those that need it do it when they need it, and share it, and they later get to take advantage of others doing the same. I assume that's why you're here, because the module is useful from so many people making effort prior.
If you want changes here, it's your turn to make the effort, in other words. I'm here to collaborate with folks and keep the project moving forward by keeping the API reasonably stable and making releases as needed.
I had a really important question for even your smaller change, and I need the answer prior to merging this at all:

If I understand that correctly, then I do not think this change is necessary but I am not certain. If I understand the code control flow of the javascript correctly, this library will not add listeners to native side or fetch state until you call configure, useNetInfo, fetch or addListener, will it? On the native side the AndroidManifest does not register for any broadcast events

However: it looks to me like when the native module loads in NetInfoModule the constructor creates the Receiver objects and during initialize() they register for network events, and then call the method you have modified.

My question is: when is the native module loaded? Is it dynamic and only loaded if the javascript side first references it? Or is that native module loaded (triggering even registration and a connectivity map update) when the app boots no matter what?

The follow on of a new API that the module completely quiet until something was asked of it would be follow-on work I'd be happy to merge but again, it's not a use case for my work projects right now, so without a champion taking up the cause, there will be no progress - just a design sketch with no work behind it until someone needs it

Oh @mikehardy  sorry for my poor reading and my rush reply. I just misunderstood that you were explaining this commit and rethinking about the API design.
What I found so far is native module's initialize will be called even after removing all the code references 'react-native-netinfo'. I think the native modules are initialized here once CatalystInstance is initialized, which happens before any user actions like agreeing to the privacy policy.
@mikehardy 's suggestion about converting to explicit APIs is a good one to solve this problem but maybe a little bit overwhelming, maybe we can start another proposal thread later to discuss about it, to see if there are enough people need this change. This is what I mean that I want to follow the progress of this potential change.
On the iOS side, I found RNCNetInfo has been optimized to avoid sending events without registered listeners . So I think this PR is still reasonable to at least make things more consistent on both platforms, and avoid calling methods unnecessarily on Android.
Thank you.

Okay, thanks a lot for testing my main question:

My question is: when is the native module loaded? Is it dynamic and only loaded if the javascript side first references it? Or is that native module loaded (triggering even registration and a connectivity map update) when the app boots no matter what?

What I found so far is native module's initialize will be called even after removing all the code references 'react-native-netinfo'. I think the native modules are initialized here once CatalystInstance is initialized, which happens before any user actions like agreeing to the privacy policy.

That's the critical result, and it means that we must make at least a minimal change now in order to handle these use cases.
This:

On the iOS side, I found RNCNetInfo has been optimized to avoid sending events without registered listeners . So I think this PR is still reasonable to at least make things more consistent on both platforms, and avoid calling methods unnecessarily on Android.

...is also great additional information and provides great support for the minimal / temporary solution you've proposed
I agree that an API rework is out of scope for this, then. We need at at least a minimal fix now and this contains a minimal fix. No need to slow it down with a larger idea.
I re-reviewed this and I'm really sad to see there is no general infrastructure in the Java native modules for managing observer count. The counts are maintained in javascript on the other side of the bridge. The same is only partially true for the iOS side - your link there combined with a re-review of the react-native core code solved the mystery I had of why #487 caused #492 and needed a revert in #493 - we partially override the superclass listener counting infrastructure there but without managing observer status. We need something on the iOS side more like what you've implemented here.
That is also out of scope for this PR, but as I document these things, then I have the ability to make new issues from them, thus the typing effort ;-).
I'll merge this and get this released. Thanks for the privacy-conscious improvement here @HatCloud I appreciate it.

Oh wait - Just realized if you don't also override method onCatalystInstanceDestroy to reset listener state, this won't work across fast-refresh or bundle reloads (like with react-native-code-push). in addition to needing onCatalystInstanceDestroy (which should just toggle hasListener to false I think, for now) in that implementation please note that after react-native 0.65 is the minimum supported version we need to override invalidate (onCatalystInstanceDestroy is deprecated and on the way out, but invalide is only called as of react-native 0.65 I think?)

new commit pushed for this advice

:tada: This PR is included in version 7.1.6 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


HTML elements follow a logical structure

HTML elements follow a logical structure independent of styling and positioning

Changed the h3 tags to h2 as they are not displayed in a subchapter.


Solution deployment guide fails with repo not found errors

Running through the solution guide, https://cloud.google.com/architecture/application-development/dynamic-app-javascript#customize-application
we encounter multiple errors along the way, but this one at the end halted progress completely:
name unknown: Repository "dev-journey-repo" not found
ERROR: push attempt 10 detected failure, retrying: step exited with non-zero status: 1
ERROR: failed to push because we ran out of retries.
ERROR
ERROR: error pushing image "us-central1-docker.pkg.dev/thiswillbedeleted/dev-journey-repo/dev-journey": generic::unknown: retry budget exhausted (10 attempts): step exited with non-zero status: 1
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

BUILD FAILURE: Docker image push failure ("The push refers to repository [us-central1-docker.pkg.dev/thiswillbedeleted/dev-journey-repo/dev-journey]
ca9a3adeb884: Preparing
07f7c28049f0: Preparing
116344037089: Preparing
1364bd94561a: Preparing
867af6f6d10e: Preparing
d6d2691c9349: Preparing
11a856782b2a: Preparing
e26f62b026b3: Preparing
f7134ea9d132: Preparing
dbdfa07812e8: Preparing
571ade696b26: Preparing
11a856782b2a: Waiting
e26f62b026b3: Waiting
f7134ea9d132: Waiting
dbdfa07812e8: Waiting
571ade696b26: Waiting
d6d2691c9349: Waiting
name unknown: Repository "dev-journey-repo" not found
"): Verify that the repositor(y|ies) us-central1-docker.pkg.dev/thiswillbedeleted/dev-journey-repo/dev-journey exists.
ERROR: (gcloud.builds.submit) build be962c26-58dd-4fd2-859e-a88741fa2b15 completed with status "FAILURE"

You can resolve this by creating the expected repository:
gcloud artifacts repositories create dev-journey-repo \
        --repository-format=docker \
        --location=us-central1

The gcloud builds submit command should then work.
I am working to update the documentation to add this.

The documentation should now be correct.


Can this allow more than 255 split keys?

Just wondering, since I would like to do something really flexible with Shamir, being used for weighted voting.

No. Maximum 16 groups of 16 members.


Support for .NET Standard 2.0 and .NET Framework

Since .NET Framework cannot use .NET Standard 2.1 based libraries, could you please add support for .NET Standard 2.0?

For .NET Framework you can try Swashbuckle.WebApi.
.NET Standard 2.0 will not be supported on this package.
CS


Fix type overrides on columns for parameters inside an IN clause

Depends on https://github.com/kyleconroy/sqlc/pull/2351

@Jille I merged #2351 could you please rebase this PR?

Rebased.


issue-304 : new param for createOrUpdateApplicationLtpsAsync

Fixes #304

@at00825957 , as discussed last week , please close this PR if the changes are not required for version 2.1.

Closing this PR , as the changes are cherry picked in this PR https://github.com/openBackhaul/OamLog/pull/340