text:
when filter value is ""

foo/?name=&type=
query :  {name:"",type:""}
The results of the query are not all.

resolved!
field-filter.ts:
case LookupFilter.EXACT:
if(this.value!==''&&this.value!==undefined){
queryToAdd = { [this.prop]: this.value };
}


text:
Options not updating when new data changes...

I have the following select2 component:
<Select2
                                ref={name}
                                name={name}
                                value={selectedValue}
                                className="form-control"
                                options={{
                                    minimumResultsForSearch: Infinity,
                                    dropdownAutoWidth: true
                                }}
                                data={dataArray}
                            />

When the dataArray content changes, the options in the drop-down list are not showing the latest values. I my specific case, I have three select2 components (a simple for loop will generate them) which all use the same dataArray and either none or some of the select2 components update with the latest values in dataArray.
I know that dataArray contains that latest values because I console.log these out beforehand, so this seems to suggest that it is a problem with the react-select2-wrapper package (?)
I am using version 1.0.2

Can you tell me how you change the data?
And are you sure about version 1.0.2?

I am sure about the version, i.e. I ran npm list react-select2-wrapper and react-select2-wrapper@1.0.2 came back.
I have an array that holds an array for each option in the select, for example:
var arr = [];
arr[0] = [];
arr[0]['id'] = 0;
arr[0]['text'] = "Option 1";
arr[1] = [];
arr[1]['id'] = 1;
arr[1]['text'] = "Option 2";

This data is injected into each select2 that I render and in my case there are 3 select2 components:
...
render(){
    var lists = [];
    for(s=0;s<3;s++){
        lists[a] = (
            <Select2
             ref={name}
             name={name}
             value={selectedValue}
             className="form-control"
             options={{
                 minimumResultsForSearch: Infinity,
                 dropdownAutoWidth: true
             }}
             data={arr}
             />
        );
    }
    var someBlock = (
{lists}
);

    return (

            {someBlock}

    );
}

If I change the values in the array (and React re-renders), when I do console.log(arr) before the for loop, i.e. before any select2 components are rendered, the data always shows correctly. However, in the first of the three select2 components, the old values remian, yet in the other two select2 components tha new values are showing the new values.

I can't reproduce this bug, can you show full example code for that?
You may use code from example.

Hmmm, I created a simple example too and cannot reproduce the bug either. Do you know how I can try and and resolve this... my code is too large and it is integrated with Meteor, so I cannot really provide any more examples. I tried adding console.log statements directly into the react-select2-wrapper npm package, but they did not output anything either to the browser console or the terminal. Any suggestions would be most welcome.

ok, I got console.log working within the node_modules/react-select2-wrapper/lib/components/Select2.js file.
I traced the text that the  was to display, within the makeOption function and it was correct just before the line:
return _react2.default.createElement('option', _extends({key: 'option-' + k, value: id}, itemParams), text);
Not sure what to check after this point?

I traced the text that the was to display, within the makeOption function and it was correct just before the line
…
Not sure what to check after this point?

This is last point.
Can you try to debug through React Developer Tools (Chrome)?
http://take.ms/NuBqb — were props change?

ok, I used the React dev tools to monitor the changes and in the dev tools the values change correctly. It is the visible select element on the page that does not update with the correct values (?)

Sorry for delays.
Can you add console.log before this line ?
console.log('update', value);
this.el.val(value).trigger('change');

it says update null

Note: this was in /lib, not /src folder.

Yep
Can you do following:

Add id to Select2 component

<Select2 id="select-tags" ... />

Add button and click

<button onClick={() => {
  const select = document.getElementById('select-tags');
  const option = document.createElement('option');
  option.text = 'NEW_ITEM';
  option.value = '9999';
  select.appendChild(option);
}}
>
 Add new item
</button>

Was a new item created?

Errr, this is wierd. So, I have 3 select elements on the page, each one I have given a unique id and each has the button that you coded above (with the unique id in the getElementById() bit). When I click ANY of the buttons, the option is ALWAYS appended to the last select element - the others are unaffected!

HI there, I haven't been able to explain this behaviour - have you mananged to look to see if there is anythgin code-wise that is causing this issue?

Hi, I can't reproduce this case, sorry.
I need example code.

Please, try a new pre-release 1.0.4-beta1

Stupid question, but how do I update to this beta version using npm? Have tried:
sudo npm update react-select2-wrapper@1.0.4-beta1

npm install react-select2-wrapper@1.0.4-beta1

Hmmm, did this and it came up with the line:
react-select2-wrapper@1.0.4-beta1  invalid

npm install react-select2-wrapper@1.0.4-beta1 --save

Thanks :)

source: gharchive/issue

authors: joetidee rkit

license: mit

license_type: permissive

license_source: bigquery


text:
Not picking up XState machine on reload

Thanks for this great tool!
I'm developing a React app using webpack-dev-server. The first time I start the server, Ninja works as expected. However, if I reload the page, I get the 'No state machines were found on the current page' screen, and I need to restart the dev server to get Ninja working again.
Redux dev tools pick up the transitions regardless.

Thanks for the report. Can you make a repro in Codesandbox please?

Not sure how I would get webpack-dev-server and xstate-ninja running in a Codesandbox.

Please update your web extension to v1.7.1.

authors: AriFordsham rlaffers

repo: rlaffers/xstate-ninja

license: ISC

license_source: github-api


text:
Test failing but I did not modify nothing

So I just cloned the project, followed the instructions from the readme and ran
npm install
bower install
grunt
and I got the following output
Running "clean:files" (clean) task
>> 1 path cleaned.

Running "jshint:gruntfile" (jshint) task

√ No problems

Running "jshint:src" (jshint) task

√ No problems

Running "jshint:test" (jshint) task

√ No problems

Running "babel:dist" (babel) task

Running "connect:server" (connect) task
Started connect web server on http://localhost:9000

Running "qunit:all" (qunit) task
Testing http://0.0.0.0:9000/test/main.html >> PhantomJS unable to load "http://0.0.0.0:9000/test/main.html" URI.
Warning: 1/1 assertions failed (0ms) Use --force to continue.

Aborted due to warnings.

Execution Time (2018-10-07 07:26:54 UTC-4)
jshint:gruntfile   45ms  ██ 1%
jshint:src        107ms  ███ 2%
jshint:test       124ms  ███ 3%
babel:dist        599ms  ███████████████ 14%
connect:server    415ms  ██████████ 9%
qunit:all          3.1s  █████████████████████████████████████████████████████████████████████████ 70%
Total 4.4s

I did no modify any files:
On branch develop
Your branch is up to date with 'origin/develop'.

Changes not staged for commit:
  (use "git add/rm <file>..." to update what will be committed)
  (use "git checkout -- <file>..." to discard changes in working directory)

        modified:   dist/dom-navigator.js
        deleted:    dist/dom-navigator.min.js

Untracked files:
  (use "git add <file>..." to include in what will be committed)

        package-lock.json

no changes added to commit (use "git add" and/or "git commit -a"

I'm running it on windows using powershell if it makes any difference.

Mmmmm, gonna check later or tomorrow.
On Sun, Oct 7, 2018, 07:30 Cristian Gomez notifications@github.com wrote:

So I just cloned the project, followed the instructions from the readme
and ran
npm install
bower install
grunt
and I got the following output
Running "clean:files" (clean) task

1 path cleaned.

Running "jshint:gruntfile" (jshint) task
√ No problems
Running "jshint:src" (jshint) task
√ No problems
Running "jshint:test" (jshint) task
√ No problems
Running "babel:dist" (babel) task
Running "connect:server" (connect) task
Started connect web server on http://localhost:9000
Running "qunit:all" (qunit) task
Testing http://0.0.0.0:9000/test/main.html >> PhantomJS unable to load "http://0.0.0.0:9000/test/main.html" URI.
Warning: 1/1 assertions failed (0ms) Use --force to continue.
Aborted due to warnings.
Execution Time (2018-10-07 07:26:54 UTC-4)
jshint:gruntfile   45ms  ██ 1%
jshint:src        107ms  ███ 2%
jshint:test       124ms  ███ 3%
babel:dist        599ms  ███████████████ 14%
connect:server    415ms  ██████████ 9%
qunit:all          3.1s  █████████████████████████████████████████████████████████████████████████ 70%
Total 4.4s
I did no modify any files:
On branch develop
Your branch is up to date with 'origin/develop'.
Changes not staged for commit:
(use "git add/rm ..." to update what will be committed)
(use "git checkout -- ..." to discard changes in working directory)
    modified:   dist/dom-navigator.js
    deleted:    dist/dom-navigator.min.js

Untracked files:
(use "git add ..." to include in what will be committed)
    package-lock.json

no changes added to commit (use "git add" and/or "git commit -a"
I'm running it on windows using powershell if it makes any difference.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/rmariuzzo/dom-navigator/issues/22, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAa2H2NTZaRQU-jUqyVNFRY3EDwquLooks5uieXNgaJpZM4XLzFf
.

@cgomezmendez looks like something related to your OS and:

PhantomJS unable to load "http://0.0.0.0:9000/test/main.html"

I just ran your code on OSX and it work flawlessly. Is the port 9000 in use?

No it's not, maybe an OS dependent issue, I'll check when I have more time.

authors: cgomezmendez rmariuzzo

repo: rmariuzzo/dom-navigator


text:
Not being able to open the 'RCTMGL.xcodeproj' project

Describe the bug
When trying to open the 'RCTMGL.xcodeproj' you get the error that the project cannot be opened due to parse errors
To Reproduce
Download the repo, go to the iOS folder and click on 'RCTMGL.xcodeproj'
Expected behavior
Being able to open the RCTMGL.xcodeproj
Actual behavior
Showing a pop up with the error "The project 'RCTMGL' is damaged and cannot be opened due to a parse error. Examine the project file for invalid edits or unresolved source control conflicts."
Versions (please complete the following information):

Platform: [iOS]
Device: [e.g. iPhone6]
Dev OS: [e.g. OSX 11.6.1]

I experience same problem did you already find a solution?

You don't need the RCTMGL.xcodeproj, it was for pre CocoaPods ReactNative integration we don't support any more

authors: DimmyMaenhout janeviceral08 mfazekas

repo: rnmapbox/maps

license: MIT


text:
[Bug]: Android: SIGSEGV crash after updating rnmapbox version

Mapbox Implementation
Mapbox
Mapbox Version
default
Platform
Android
@rnmapbox/maps version
10.0.15
Standalone component to reproduce
import React from 'react';
import {
  MapView,
  ShapeSource,
  LineLayer,
  Camera,
} from '@rnmapbox/maps';

const aLine = {
  type: 'LineString',
  coordinates: [
    [-74.00597, 40.71427],
    [-74.00697, 40.71527],
  ],
};

class BugReportExample extends React.Component {
  render() {
    return (
      <MapView />
    );
  }
}

Observed behavior and steps to reproduce
After updating rnmapbox version from 10.0.0-rc.13 to 10.0.15, opening any screen with a mapbox map causes the app to immediately crash with the following stack trace:
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
pid: 0, tid: 18821 >>> com.xovation.weski <<<

backtrace:
  #00  pc 0x00000000000f8000  [anon:stack_and_tls:18821]
  #01  pc 0x00000000000e8238  /data/app/~~1cmB8bMYMLeAeaTLpYvN2w==/com.xovation.weski-8cBK0YxjolLvsDxLYFU2QA==/split_config.arm64_v8a.apk!libc++_shared.so (BuildId: fcc246cbb373c5edee634b117c4b4564cc9becf3)
  #02  pc 0x00000000000e7e6c  /data/app/~~1cmB8bMYMLeAeaTLpYvN2w==/com.xovation.weski-8cBK0YxjolLvsDxLYFU2QA==/split_config.arm64_v8a.apk!libc++_shared.so (BuildId: fcc246cbb373c5edee634b117c4b4564cc9becf3)
  #03  pc 0x00000000000e3f50  /data/app/~~1cmB8bMYMLeAeaTLpYvN2w==/com.xovation.weski-8cBK0YxjolLvsDxLYFU2QA==/split_config.arm64_v8a.apk!libc++_shared.so (BuildId: fcc246cbb373c5edee634b117c4b4564cc9becf3)
  #04  pc 0x00000000000e3da4  /data/app/~~1cmB8bMYMLeAeaTLpYvN2w==/com.xovation.weski-8cBK0YxjolLvsDxLYFU2QA==/split_config.arm64_v8a.apk!libc++_shared.so (__gxx_personality_v0+224) (BuildId: fcc246cbb373c5edee634b117c4b4564cc9becf3)
  #05  pc 0x0000000000143d4c  /data/app/~~1cmB8bMYMLeAeaTLpYvN2w==/com.xovation.weski-8cBK0YxjolLvsDxLYFU2QA==/split_config.arm64_v8a.apk!libmapbox-common.so (BuildId: f2ed5d81095e1796)
  #06  pc 0x0000000000144254  /data/app/~~1cmB8bMYMLeAeaTLpYvN2w==/com.xovation.weski-8cBK0YxjolLvsDxLYFU2QA==/split_config.arm64_v8a.apk!libmapbox-common.so (BuildId: f2ed5d81095e1796)
  #07  pc 0x0000000000180aec  /data/app/~~1cmB8bMYMLeAeaTLpYvN2w==/com.xovation.weski-8cBK0YxjolLvsDxLYFU2QA==/split_config.arm64_v8a.apk!libmapbox-common.so (BuildId: f2ed5d81095e1796)
  #08  pc 0x00000000001a67cc  /data/app/~~1cmB8bMYMLeAeaTLpYvN2w==/com.xovation.weski-8cBK0YxjolLvsDxLYFU2QA==/split_config.arm64_v8a.apk!libmapbox-common.so (BuildId: f2ed5d81095e1796)
  #09  pc 0x000000000028e914  /data/app/~~1cmB8bMYMLeAeaTLpYvN2w==/com.xovation.weski-8cBK0YxjolLvsDxLYFU2QA==/split_config.arm64_v8a.apk!libmapbox-common.so (BuildId: f2ed5d81095e1796)
  #10  pc 0x000000000028eec8  /data/app/~~1cmB8bMYMLeAeaTLpYvN2w==/com.xovation.weski-8cBK0YxjolLvsDxLYFU2QA==/split_config.arm64_v8a.apk!libmapbox-common.so (BuildId: f2ed5d81095e1796)
  #11  pc 0x000000000028f83c  /data/app/~~1cmB8bMYMLeAeaTLpYvN2w==/com.xovation.weski-8cBK0YxjolLvsDxLYFU2QA==/split_config.arm64_v8a.apk!libmapbox-common.so (BuildId: f2ed5d81095e1796)
  #12  pc 0x000000000019896c  /data/app/~~1cmB8bMYMLeAeaTLpYvN2w==/com.xovation.weski-8cBK0YxjolLvsDxLYFU2QA==/split_config.arm64_v8a.apk!libmapbox-common.so (BuildId: f2ed5d81095e1796)
  #13  pc 0x00000000001a9854  /data/app/~~1cmB8bMYMLeAeaTLpYvN2w==/com.xovation.weski-8cBK0YxjolLvsDxLYFU2QA==/split_config.arm64_v8a.apk!libmapbox-common.so (mapbox::common::platform::processTask(std::__ndk1::function<void ()> const&)+32) (BuildId: f2ed5d81095e1796)
  #14  pc 0x000000000019add0  /data/app/~~1cmB8bMYMLeAeaTLpYvN2w==/com.xovation.weski-8cBK0YxjolLvsDxLYFU2QA==/split_config.arm64_v8a.apk!libmapbox-common.so (BuildId: f2ed5d81095e1796)
  #15  pc 0x00000000000c9ccc  /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+204)
  #16  pc 0x000000000005db00  /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64)

Expected behavior
App should not crash.
Notes / preliminary analysis
I upgraded from 10.0.0-rc.13 to 10.0.15.
I upgraded RN from 0.71.6 to 0.72.7.
No code changes were made.
I released a beta version with these changes to the Play Store, and updated the version on my phone. Now, opening any screen with a Mapbox map causes the app to crash. I tried clearing the Cache and it still crashes. I tried changing the code to simply render a MapView with no style, props, handlers or content, and it still crashes.
The only thing that stops the crashing is uninstalling and reinstalling the app.
So it seems like some data has been cached by Mapbox that is not compatible with the latest version.
Is there a programmatic way to clear cached data?
Additional links and references
No response

It looks like I need to try the following:
await Mapbox.offlineManager.clearAmbientCache();
I will try this as soon as I am able to access a broken device, and will report back.

I have narrowed down the problem, but am at a loss as to how to fix.
First, Mapbox.offlineManager.invalidateAmbientCache() is deprecated (docs should be updated to reflect this). So I tried Mapbox.offlineManager.resetDatabase(). Unfortunately, the issue persists.
I then uinstalled the app, installed the version that used rnmapbox v10.0.0-rc.13, and browsed some maps (to seed the database). I then updated to the 10.0.15 version, and the issue did not resurface.
This surprised me, so I uninstalled again, installed a much older version that used rnmapbox v10.0.0-beta.68, browed some maps, and updated to the version that has rnmapbox v10.0.15. The issue resurfaced.
So it seems to be an issue with cached data stored by version 10.0.0-beta.68 that is supported by version 10.0.0-rc.13, but not compatible with version 10.0.15.
Since resetDatabase doesn't help, I'm not sure how to fix it.
Any ideas?

I had to set the access token before calling resetDatabase, otherwise the app would crash.
I see that a recent commit from a few days ago sets the access token on the tile store.
But I am using v10.0.15 which does not set the access token. Since offlineManager.resetDatabase is the first method I am calling (after Mapbox.setAccessToken), could that be why resetDatabase doesn't work?

@bradstiff We also have https://rnmapbox.github.io/docs/components/MapView#cleardata but it's on MapView so might be too late.
In v11 it's static so we could make it a static method there.
https://docs.mapbox.com/android/maps/api/11.0.0/mapbox-maps-android/com.mapbox.maps/-mapbox-map/-companion/clear-data.html?query=fun clearData(callback: AsyncOperationResultCallback)
You can also give it a try with 10.1.*-rc
You can also look into logcat messages.
Also you can use the RNMapboxMapsImpl to change mapbox versions.
https://github.com/rnmapbox/maps/blob/v10.0/android/install.md#using-non-default-mapbox-version

Thanks. I can't render a Mapview at all without crashing, so clearData won't work.
I'll try v10.1.
I have looked very closely at logcat. I don't see anything that gives me any ideas. I do notice that around the same time as the crash, the entry below appears a few ms prior. It is not the same process ID as the app, so I don't think much of it. But it is strange that it is there every time.
2023-12-04 23:08:17.471 19325-19325 chromium                pid-19325                            E  [19325:19325:20231204,230817.471087:ERROR file_io_posix.cc:144] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq: Permission denied (13)
One thing I forgot to mention: in Crashlytics, the reported RAM at the time of the crash is always very low, e.g., a few hundred MB. Essentially, RAM goes from normal, e.g., 2GB+, down to a few hundred MB just before the crash. As I said earlier, the crash occurs even rendering an empty Mapview, e.g., the memory drawdown I am describing has nothing to do with the map I'm trying to render.

@bradstiff in 10.1.0 I've also implemented clearData static method. But you might need to use 11.0 Mapbox to use it as native android  10.* requires a MapView instance to call clearData.

I upgraded to 10.1.0-rc.2 and it appears the problem went away.
I'm still concerned about what it could have been.
Fresh installs worked fine. Only specific upgrades had the issue.

authors: bradstiff mfazekas


text:
GraphQL subscriptions

Howdy 👋
Absolutely love the project. Are there are plans to support GraphQL subscriptions? I see a lot of potential to have rock solid, performant subscriptions with Delta Lake Tables. But it would also be handy to have a polling fallback mechanism like liveQuery implemented in other projects like Hasura.

Definitely seems like a very cool idea and something not hard to implement! There is no active plan to working on this feature, but PRs are very welcome :D

It is cool idea. Looks like this will depends on ROAPI auto refresh? e.g. option 2 or 3 from https://github.com/roapi/roapi/issues/55#issuecomment-962533615

yeah, we will need option 2 or 3 to implement this.

authors: houqp jychen7 rupurt

repo: roapi/roapi


text:
Setup special keybindings using terminfo

The support for special keys right now is simply with hardcoded values,
this commit changes that to using terminfo information for the keys to
set the binds.  Should be much more general, and just work.  This also
fixes a bug in the vi-mode plugin where the special keys were not bound
because setting vi mode removes binds set in emacs mode.
Fixes the problem with 53854754e0d052 not setting the special key
keybindings and those keys not being recognized when using vi-mode.

Could you rebase this PR if you'd like to pursue it, or close it? The aspect of using terminfo for the escape sequence lookups is now being used (since #1355 and the #2608 stuff). Now this PR is providing the notion of a higher-precedence layer of key mappings, which I think can be considered separately.

I'm closing this PR, we're moving on a different direction and it's 3 years old now.

source: gharchive/pull-request

authors: apjanke jimhester mcornella

repo: robbyrussell/oh-my-zsh


text:
relation "docs" does not exist

Do I need to run anything besides api.sql? I'm getting an error with your example.
select * from save_document('monkies', '{"name" : "foofer"}');
SQL Error: ERROR:  Error: Error: relation "docs" does not exist
DETAIL:  save_document() LINE 6:     plv8.execute("select create_document_table('" + tbl + "');");

I sit here with a beer in hand, thinking about the Seahawks game where they lost in the last minute of the game for like the 5th time this season... and I'm in a Slack chat with 5 friends, two of which I'm trying to build a new application. My daughter is waiting for me to read her a bedtime story and I'm finishing off a KILLER 80s playlist on Spotify...
api.sql? I need just a bit more detail here to catch up with what you're doing. I want to help - I do. Just  a bit more detail would help me read to my daughter just a few minutes faster...

Hi, sorry about the Seahawks. I imagine they will beat the 49ers on Sunday. This question is regarding your pg_docs_api project on github. I watched your talk and decided to do things your way although I am  old and know my way around RDBMS just fine. Like you said, I want to get to mars first. Anyway, I ran api.sql on my server but I am not able to invoke save_document due to error "relation "docs" does not exist." I will dig into it. By the way, I have not used Slack but have started on Discord which works with larger teams. http://discordapp.com I too enjoy beer and the days of reading to my daughter are behind me. I guess I'm back to only having work again.

Ahh - thanks for this! Yes, you should be able to run api.sql to seed the functions, and then save should create the functions for you. That's the idea at least. I'll give it a go tonite when I get a chance.

The fix is in create_document_table .. add variable name to string instead of hard-coded 'doc'
plv8.execute("create index idx_" + name + " on " + name + " using GIN(body jsonb_path_ops)");
plv8.execute("create index idx_" + name + "_search on " + name + " using GIN(search)");

By the way, if you intend to keep this project going, could I please ask for the id to be text instead of int

That fix is already checked in. It appears that I got an old api.sql somehow. My apologies.

authors: robconery terrisgit


text:
Time Varying Constraints Based on Benchmark Weights

What are you trying to do?
Are we able to add in time-varying sector constraints? For example if the sector weights in a benchmark change over time, I want the constraints on my portfolio's sector weights to dynamically adjust based on these changes. The constraints would be set as a certain percentage range (e.g., ±10%) around the sector weights in the benchmark index at each time step.

Hi, I don't think there's a better way to do this than looping through, and at each time step re-optimising the portfolio using your new constraints.
You can include a turnover penalty to stop the optimiser from massively changing the weights.


text:
Update CHANGELOG.md

Small typo in the year.
Changes proposed:

[ ] Add
[ ] Prepare
[ ] Delete
[X ] Fix

Things I've done:

[X ] My pull request fixes an issue, I referenced the issue.

Just notice had year of 2016 for latest changes.

2017 is too fresh for us 😆

Thanks @cswanson0!

authors: JimiC cswanson0 robertohuertasm

repo: robertohuertasm/vscode-icons


text:
🛑 Museo de la Luz is down

In d7b63a7, Museo de la Luz (http://www.museodelaluz.unam.mx) was down:

HTTP code: 502
Response time: 3271 ms

Resolved: Museo de la Luz is back up in 66acbb0.

repo: robertormzg/upptime-dgdc


text:
cron job not work

testcode
`package main
import (
"fmt"
"log"
"github.com/robfig/cron/v3"

)
func main() {
log.Println("Starting...")
c := cron.New()  // 新建一个定时任务对象
EntryID,_ := c.AddFunc("* * * * * *", func() {
	log.Println("hello world")
})  // 给对象增加定时任务
fmt.Println(EntryID)
c.Start()
select {
}

}`
log.Println like this:
2020/05/04 15:42:47 Starting... 0
i`m sure the  program not exited,and i try use c.Run() also. but nothing ,no hello world,

emmmm, i import "github.com/robfig/cron" and `c := cron.New()
c.AddFunc(spec,sendMail)
c.Run()
select {
}`  is work

I have the same problem, why V3 doesn't work

repo: robfig/cron


text:
Ftp Client Download File hang when file size is 0?

FTP Server OS: Unkonw
FTP Server Type: Unknow
Client Computer OS: Windows
FluentFTP Version: 45.2.0
Framework: .NET 4.8
Hi,
I implemented the following C# code to download a file every 10 seconds from an FTP server on the local network and everything works correctly (see LOG 1), but unpredictably the download is bloked (see LOG 2).
 client = new FtpClient("192.168.0.238")
        {
            Credentials = new NetworkCredential("BROTHER", "******"),

            Config = new FtpConfig
            {
                ReadTimeout = 3000,
                RetryAttempts = 5,
                SocketPollInterval = 5000,
                ConnectTimeout = 2000,
                DataConnectionConnectTimeout = 2000,
                DataConnectionReadTimeout = 2000
            }
        };

client.Connect();

client.DownloadFile("D:\AgileCOM\Service\\Temp\kcbhe3c1.txt", "/PRD3.NC", FtpLocalExists.Overwrite, `FtpVerify.None);`

client.Disconnect();

LOG 1 - DOWNLOAD NORMALLY:
2023_02_27-13_51_59 Status:   Testing connectivity using Socket.Poll()...
2023_02_27-13_51_59 Command:  QUIT
2023_02_27-13_51_59 Status:   Waiting for response to: QUIT
2023_02_27-13_51_59 Response: 221 Service closing control connection [9ms]
2023_02_27-13_51_59 Status:   Closing/Disposing FtpSocketStream(control connection)
2023_02_27-13_51_59 >         Connect(False)
2023_02_27-13_51_59 Status:   FluentFTP 45.1.0.0
2023_02_27-13_51_59 Status:   Connecting to IP #1= ***:21
2023_02_27-13_51_59 Status:   Waiting for a response
2023_02_27-13_51_59 Response: 220 Welcome  [50ms]
2023_02_27-13_51_59 Command:  USER ***
2023_02_27-13_51_59 Status:   Waiting for response to: USER ***
2023_02_27-13_51_59 Response: 331 Password required for *** [8ms]
2023_02_27-13_51_59 Command:  PASS ***
2023_02_27-13_51_59 Status:   Waiting for response to: PASS ***
2023_02_27-13_51_59 Response: 230 Logged on [7ms]
2023_02_27-13_51_59 Command:  FEAT
2023_02_27-13_51_59 Status:   Waiting for response to: FEAT
2023_02_27-13_51_59 Response: 502 Command not implemented. [8ms]
2023_02_27-13_51_59 Status:   Text encoding: System.Text.ASCIIEncoding
2023_02_27-13_51_59 Command:  SYST
2023_02_27-13_51_59 Status:   Waiting for response to: SYST
2023_02_27-13_51_59 Response: 502 Command not implemented. [8ms]
2023_02_27-13_51_59 Warning:  Cannot auto-detect listing parser for system 'Unknown', using Unix parser
2023_02_27-13_51_59 Status:   Listing parser set to: Unix
2023_02_27-13_51_59 Command:  PWD
2023_02_27-13_51_59 Status:   Waiting for response to: PWD
2023_02_27-13_51_59 Response: 257 "/" is current directory. [7ms]
2023_02_27-13_51_59 >         DownloadFile("D:\AgileCOM\Service\\Temp\n3rk0vwv.txt", "/PRD3.NC", Overwrite, None)
2023_02_27-13_51_59 >         OpenRead("/PRD3.NC", Binary, 0, 0)
2023_02_27-13_51_59 >         GetFileSize("/PRD3.NC")
2023_02_27-13_51_59 Command:  TYPE I
2023_02_27-13_51_59 Status:   Waiting for response to: TYPE I
2023_02_27-13_51_59 Response: 200 Type set to I. [6ms]
2023_02_27-13_51_59 >         OpenDataStream("RETR /PRD3.NC", 0)
2023_02_27-13_51_59 >         OpenPassiveDataStream(AutoPassive, "RETR /PRD3.NC", 0)
2023_02_27-13_51_59 Command:  EPSV
2023_02_27-13_51_59 Status:   Waiting for response to: EPSV
2023_02_27-13_51_59 Response: 502 Command not implemented. [8ms]
2023_02_27-13_51_59 >         OpenPassiveDataStream(PASV, "RETR /PRD3.NC", 0)
2023_02_27-13_51_59 Command:  PASV
2023_02_27-13_51_59 Status:   Waiting for response to: PASV
2023_02_27-13_51_59 Response: 227 Entering Passive Mode (192,168,0,228,13,84) [8ms]
2023_02_27-13_51_59 Status:   Connecting to IP #1= ***:3412
2023_02_27-13_51_59 Command:  RETR /PRD3.NC
2023_02_27-13_51_59 Status:   Waiting for response to: RETR /PRD3.NC
2023_02_27-13_51_59 Response: 150 Opening BINARY mode data connection for file transfer. [143ms]
2023_02_27-13_52_00 Status:   Downloaded 161061 bytes
2023_02_27-13_52_00 Status:   Closing/Disposing FtpSocketStream(data connection)
2023_02_27-13_52_00 Status:   Waiting for response to: *DOWNLOAD*
2023_02_27-13_52_00 Response: 226 Transfer complete. [577ms]

LOG 2 - DOWNLOAD BLOCKED:
2023_02_27-13_52_12 Status:   Testing connectivity using Socket.Poll()...
2023_02_27-13_52_12 Command:  QUIT
2023_02_27-13_52_12 Status:   Waiting for response to: QUIT
2023_02_27-13_52_12 Response: 221 Service closing control connection [11ms]
2023_02_27-13_52_13 Status:   Closing/Disposing FtpSocketStream(control connection)
2023_02_27-13_52_13 >         Connect(False)
2023_02_27-13_52_13 Status:   FluentFTP 45.1.0.0
2023_02_27-13_52_13 Status:   Connecting to IP #1= ***:21
2023_02_27-13_52_13 Status:   Waiting for a response
2023_02_27-13_52_13 Response: 220 Welcome  [58ms]
2023_02_27-13_52_13 Command:  USER ***
2023_02_27-13_52_13 Status:   Waiting for response to: USER ***
2023_02_27-13_52_13 Response: 331 Password required for *** [8ms]
2023_02_27-13_52_13 Command:  PASS ***
2023_02_27-13_52_13 Status:   Waiting for response to: PASS ***
2023_02_27-13_52_13 Response: 230 Logged on [5ms]
2023_02_27-13_52_13 Command:  FEAT
2023_02_27-13_52_13 Status:   Waiting for response to: FEAT
2023_02_27-13_52_13 Response: 502 Command not implemented. [7ms]
2023_02_27-13_52_13 Status:   Text encoding: System.Text.ASCIIEncoding
2023_02_27-13_52_13 Command:  SYST
2023_02_27-13_52_13 Status:   Waiting for response to: SYST
2023_02_27-13_52_13 Response: 502 Command not implemented. [6ms]
2023_02_27-13_52_13 Warning:  Cannot auto-detect listing parser for system 'Unknown', using Unix parser
2023_02_27-13_52_13 Status:   Listing parser set to: Unix
2023_02_27-13_52_13 Command:  PWD
2023_02_27-13_52_13 Status:   Waiting for response to: PWD
2023_02_27-13_52_13 Response: 257 "/" is current directory. [9ms]
2023_02_27-13_52_13 >         DownloadFile("D:\AgileCOM\Service\\Temp\kcbhe3c1.txt", "/PRD3.NC", Overwrite, None)
2023_02_27-13_52_13 >         OpenRead("/PRD3.NC", Binary, 0, 0)
2023_02_27-13_52_13 >         GetFileSize("/PRD3.NC")
2023_02_27-13_52_13 Command:  TYPE I
2023_02_27-13_52_13 Status:   Waiting for response to: TYPE I
2023_02_27-13_52_13 Response: 200 Type set to I. [7ms]
2023_02_27-13_52_13 >         OpenDataStream("RETR /PRD3.NC", 0)
2023_02_27-13_52_13 >         OpenPassiveDataStream(AutoPassive, "RETR /PRD3.NC", 0)
2023_02_27-13_52_13 Command:  EPSV
2023_02_27-13_52_13 Status:   Waiting for response to: EPSV
2023_02_27-13_52_13 Response: 502 Command not implemented. [8ms]
2023_02_27-13_52_13 >         OpenPassiveDataStream(PASV, "RETR /PRD3.NC", 0)
2023_02_27-13_52_13 Command:  PASV
2023_02_27-13_52_13 Status:   Waiting for response to: PASV
2023_02_27-13_52_13 Response: 227 Entering Passive Mode (192,168,0,228,19,146) [7ms]
2023_02_27-13_52_13 Status:   Connecting to IP #1= ***:5010
2023_02_27-13_52_13 Command:  RETR /PRD3.NC
2023_02_27-13_52_13 Status:   Waiting for response to: RETR /PRD3.NC
2023_02_27-13_52_13 Response: 150 Opening BINARY mode data connection for file transfer. [238ms]
2023_02_27-13_52_13 Status:   Downloaded 0 bytes
2023_02_27-13_52_13 Status:   Closing/Disposing FtpSocketStream(data connection)
2023_02_27-13_52_13 Status:   Waiting for response to: *DOWNLOAD*

The problem would seem to be due to the null size (0 bytes) of the file.
Is there a bug or some option to avoid the problem?
Thank's

You are using FluentFTP 45.1.0.0 (I can see that in your log) and not "45.2.0"
45.2.0 fixes some of these edge case that were broken some time ago:
Improve GetReply to handle connection loss edge cases and timeout exceptions
https://github.com/robinrodricks/FluentFTP/blob/master/RELEASES.md#4520

Thank's FanDjango
I'll try today with version 45.2.0 which I had downloaded, but actually not yet deployed.

authors: EcTomBot FanDjango

repo: robinrodricks/FluentFTP


text:
seems tpl function not working in hooks args

helmfile.yaml
repositories:
  - name: incubator
    url: https://kubernetes-charts-incubator.storage.googleapis.com

values:
  - domain: example.com

releases:
  - name: test
    chart: incubator/raw
    values:
      - resources:
          -
            apiVersion: extensions/v1beta1
            kind: Ingress
            metadata:
              name: test
            spec:
              rules:
                - host: {{ .Values.domain }}
                  http:
                    paths:
                      - backend:
                          serviceName: test
                          servicePort: 80
                        path: /
    hooks:
      - events: [prepare]
        showlogs: true
        command: bash
        args:
          - -c
          - echo kubectl patch ingress/test --type=json -p="{{`{{ tpl (readFile "test-patch.yaml.gotmpl") . }}`}}"

test-patch.yaml.gotmpl
- op: add
  path: /spec/tls
  value:
    - hosts:
        - {{ .Values.domain }}
      secretName: {{ .Values.domain }}-tls

expected behavior: rendering test-patch.yaml.gotmpl with actual values
current behavior:
$ helmfile template
helmfile.yaml: basePath=.
in ./helmfile.yaml: [hook[bash]: template: stringTemplate:1:51: executing "stringTemplate" at <tpl (readFile "test-patch.yaml.gotmpl") .>: error calling tpl: template: stringTemplate:5:20: executing "stringTemplate" at <.Values.domain>: map has no entry for key "Values"]

helmfile version v0.129.3

@kupnu4x Thanks for reporting! #1485 should add that.

repo: roboll/helmfile


text:
Add  --output-dir to the helmfile template command

For cases when helmfile is used only for templating, will be great to support --output-dir as original helm does.
$ helm template --help
...
      --output-dir string        writes the executed templates to files in output-dir instead of stdout
...

Some benefits:

it renders yamls to corresponding files, preserving structure of the original chart
it ignores empty files [helm/helm/issues/3979]

@lwolf Thanks for submitting this request! Yeah, this sounds like a great enhancement to helmfile.

@olivierboudet Hey! Thanks for submitting your PR #693 with this.
I wanted to discuss with you folks what the expected behavior of this should be.
Just passing --output-dir USER_SPECIFIED_DIR to every helm template command called by helmfile breaks when there are two or more releases and nested state files that uses the same chart, because it uses the name of the chart as the directory name:
helm template --name foo mysql-1.2.0.tgz --output-dir test1
wrote test1/mysql/templates/secrets.yaml
wrote test1/mysql/templates/tests/test-configmap.yaml
wrote test1/mysql/templates/pvc.yaml
wrote test1/mysql/templates/svc.yaml
wrote test1/mysql/templates/tests/test.yaml
wrote test1/mysql/templates/deployment.yaml

In other words, the question is - what if mysql chart is used by multiple releases, shouldn't it override the previously "templated" one?
So probably we want the chart name part in the directory name to be <state-file-id>-<release-name>.
We can probably use some hash of the absolute path to the state file as state-file-id, and append an index suffix when there are two or more file that ends up with the same state-file-id.
WDYT?

Also cc / @lwolf

Yes @mumoshu I did not thought about that, just passing a user specified output dir to every helm template command was enough for my use case.
I agree with your proposal but I think the directory <state-file-id>-<release-name> should also contain the state file name so that users can easily find generated templates for each state file...
I probably miss something but if we generate a hash of the absolute path to the state file, we may consider that only one file can have the same state-file-id, am I wrong ?

Yeah, it makes sense to have unique directory for each release inside the user speficied directory

I probably miss something but if we generate a hash of the absolute path to the state file, we may consider that only one file can have the same state-file-id, am I wrong ?

@olivierboudet You aren't missing anything! Only one file can have the same state-file-id, yes. That's why I wrote:

and append an index suffix when there are two or more file that ends up with the same state-file-id.

I wrote it based on my assumption that no hash function is capable of generating unique IDs(although they have low probability to collide).
WDYT?

I pushed a new implementation with a subdirectory by release.
For a simple state file like this :
releases:
  - name: my-release
    chart: stable/mysql

The result is :
Fetching stable/mysql
wrote output/helmfile-e9b37d2f-my-release/mysql/templates/secrets.yaml
wrote output/helmfile-e9b37d2f-my-release/mysql/templates/tests/test-configmap.yaml
wrote output/helmfile-e9b37d2f-my-release/mysql/templates/pvc.yaml
wrote output/helmfile-e9b37d2f-my-release/mysql/templates/svc.yaml
wrote output/helmfile-e9b37d2f-my-release/mysql/templates/tests/test.yaml
wrote output/helmfile-e9b37d2f-my-release/mysql/templates/deployment.yaml

The first part is the name of the helmfile (I keep it because I have multiple helmfiles named helmfile-middlewares, helmfile-apps, helmfile-ingress and I want to see easily the output for them).
The second part is first 8 chars of the sha1 of the absolute path of the state file.
The third part is the release name.
For the moment it will not add an index if the sha1 collide with another but I will try to add it later.
PS : I am not a go developer, do not hesitate if I can improve some things

@olivierboudet Thanks a lot for your work. It looks great!
I'd appreciate it if you could all some unit test so that we don't unintentionally break it in the future. But it isn't a requisite for merging

@mumoshu yes I will try to add some as soon as possible. As I can see, there is no unit tests for template command for now that I can enrich ?

@olivierboudet Thanks! Yeah I think there's no unit tests for template now.
There may be several options to start with. I'll describe one of them here.

Create an another TestWhatever function copying one of existing tests in app_test.go. It is the high-level test suite that basically calls various helmfile external/internal commands in go code and verifies the result.

Probably you want to run err := app.Template() in order to test the helmfile template command as a whole. But it isn't that simple, unfortunately.. Just calling app.Template() ends up calling actual helm commands in your "unit" test, which isn't nice.

If you have enough time, try changing the code a bit to allow dependency-injecting the helmexec.Execer implementation that is currently hard-coded at https://github.com/roboll/helmfile/blob/f61334d9bb4cf637d3a9152b1595b8d4b6462db5/pkg/app/app.go#L277. Maybe you can add execer as a field to App struct, so that you can inject your own mock execer for testing.

I try to add a unit test but I have some issues.
I have mocked the helmexec.Execer, so the test is running correctly. But I don't know how to do assertions.
I try to catch the logger output in debug to verify that the command (ie helm template) is correct but the path where the chart is downloaded is dynamically generated. For example :
exec: helm template /tmp/707176687/myrelease1/latest/mychart1 --name myrelease1 --output-dir output/subdir/helmfile-a94eb40d-myrelease1 --kube-context dev

How can I verify that the command is correct ignoring the 707176687 part ?
My test case is as follow for the moment :
func TestTemplate_SingleStateFile(t *testing.T) {
	files := map[string]string{
		"/path/to/helmfile.yaml": `
releases:
- name: myrelease1
  chart: mychart1
- name: myrelease2
  chart: mychart1
`,
	}

	var buffer bytes.Buffer
	logger := helmexec.NewLogger(&buffer, "debug")

	app := appWithFs(&App{
		glob:        filepath.Glob,
		abs:         filepath.Abs,
		KubeContext: "default",
		Env:         "default",
		Logger:      logger,
		helmExecer:  MockExecer(logger, "dev"),
	}, files)
	app.Template(configImpl{})

	expected := `Generating templates to : output/subdir/helmfile-a94eb40d-myrelease1
exec: helm template /tmp/707176687/myrelease1/latest/mychart1 --name myrelease1 --output-dir output/subdir/helmfile-a94eb40d-myrelease1 --kube-context dev
exec: helm template /tmp/707176687/myrelease1/latest/mychart1 --name myrelease1 --output-dir output/subdir/helmfile-a94eb40d-myrelease1 --kube-context dev:

exec: helm template /tmp/707176687/myrelease1/latest/mychart1 --name myrelease2 --output-dir output/subdir/helmfile-a94eb40d-myrelease2 --kube-context dev
exec: helm template /tmp/707176687/myrelease1/latest/mychart1 --name myrelease2 --output-dir output/subdir/helmfile-a94eb40d-myrelease2 --kube-context dev:
`
	if !strings.Contains(buffer.String(), expected) {
		t.Errorf("app.Template()\nactual = %v\nexpect = %v", buffer.String(), expected)
	}
}

@olivierboudet Nice try!
I'd suggest enhancing mockHelmExec so that can capture what are "templated" like we do for other helm commands https://github.com/roboll/helmfile/blob/1df9b0e9e9cfd6230afdb3c34b9e406df58b4a37/pkg/state/state_test.go#L737
Based on that, you'll be able to assert each set of directory and flags used for calling helm template, like /tmp/707176687/myrelease1/latest/mychart1 and --name myrelease1 --output-dir output/subdir/helmfile-a94eb40d-myrelease1 --kube-context dev respectively.
You still see /tmp/<number> in the directory, but as you have access to each entry it should be easier to extract the myrelease1/latest/mychart1 part only and make assertion on that.

awesome!

authors: bitsofinfo lwolf mumoshu olivierboudet


text:
Enhance support for kube-version and api-versions

This adds support for kube-version and api-versions to be available to chartify so that it works even if your release requires chartify due to that you use features like forceNamespace, jsonPatches, strategicMergePatches, and so on.
This also enhances ReleaseSpec which corresponds to each item of releases[] in your helmfile.yaml to also accept kubeVersion and apiVersions, in addition to the top-level kubeVersion and apiVersions we have today.
The top-level ones works as the default values for release-specific ones. If you have been using the top-level ones, keep using it. It is backward-compatible. If you want to specify it per release, because, for example, your releases are deployed across clusters(in case you differentiate kubeContext fields), try the new fields added to the release spec.
Resolves #1864

@mumoshu This looks awesome - will this also work for specifying kubeVersion at the environment level? We do a lot of custom configs per environment - would be nice to be able to specify it there if possible vs at the release.

authors: mumoshu rayterrill


text:
SimpleApp demo fails to launch on macOS 10.12 (Sierra)

The app compiles without errors, but on launch it fails with this error:

Detected missing constraints for <private>.  It cannot be placed because there are not enough constraints to fully define the size and origin. Add the missing constraints, or set translatesAutoresizingMaskIntoConstraints=YES and constraints will be generated for you. If this view is laid out manually on macOS 10.12 and later, you may choose to not call [super layout] from your override. Set a breakpoint on DETECTED_MISSING_CONSTRAINTS to debug. This error will only be logged once.

@typemytype any clues on how to fix this? I tried to set translatesAutoresizingMaskIntoConstraints somewhere in vanilla.vanillaWindows.Window without success.

After adding these two lines
import pdb
pdb.set_trace()

to SimpleApp.py I now get this message in Console,

GetDYLDEntryPointWithImage(/System/Library/Frameworks/AppKit.framework/Versions/Current/AppKit,_NSCreateAppKitServicesMenu) failed.

@miguelsousa did you manage to get this working?

https://github.com/typesupply/vanilla/pull/32 has a comment about it running on 10.12.1.
I don't know the last time I tried to compile or launch the SimpleApp.

What is the oldest version of macOS that should be supported by vanilla?

authors: dyyybek miguelsousa schriftgestalt

repo: robotools/vanilla


text:
“Not” combinator

Matches any character not matched by the argument parser.

What’s the implication of noting a multi-character pattern? (I am a dumb hairless ape).

@davidcairns: TL;DR: Makes no different how many characters the pattern matches (zero, one, n), it’s whether it returns nil or not.
!a would match a single character iff a does not match; so it doesn’t matter if a would consume input because we don’t care how much it consumes, we just care whether it matches or fails.
My current thinking is that it’d be better to do zero-width negative lookahead instead. In that model, ?!a would never consume any input, but would succeed iff a does not match. Then you’d do ?!a ++ b to allow b to parse when a cannot.
This works because parser combinators return (/*parseTree: */ T, /*restOfInput:*/ String)?, so they can return the input unmodified in the tuple to do this. And they indicate failure by returning nil, so we can unambiguously determine whether they matched zero characters or failed.
Here’s an example using ?! to recover the behaviour described at top (parsing any single character not matched by its argument):
let quote = ignore("\"")
let string = quote ++ (?!quote ++ any)* ++ quote

OHHHHHHHHHH I get it now.

Given the less-regex-y API direction in #110 (removal of postfix * and +). Any opinions on what operator/name this should have? /cc @joshvera

@bencochran I’ve been stealing names from Parsec and Lightyear, so I’m a fan of not or notFollowedBy. I think this might be Parsec’s notFollowedBy.

Added in #111

authors: bencochran davidcairns joshvera robrix

repo: robrix/Madness


text:
Control the included quota and storage providers via Go build tags

https://github.com/google/trillian/pull/3644#discussion_r1822420304 notes that the log-signer and log-server binaries are huge, due in part to the presence of multiple quota and storage providers.  This PR enables providers to be included selectively via Go build tags.
By default and for backwards compatibility, all providers are included:
> go build && ls -sh trillian_log_server
62M trillian_log_server*

Specify one build tag to include just one provider:
> go build -tags=cloudspanner && ls -sh trillian_log_server
54M trillian_log_server*
> go build -tags=crdb && ls -sh trillian_log_server
37M trillian_log_server*
> go build -tags=mysql && ls -sh trillian_log_server
34M trillian_log_server*
> go build -tags=postgresql && ls -sh trillian_log_server
40M trillian_log_server*

Specify multiple, comma-separated build tags to include multiple providers.  e.g.,:
> go build -tags=mysql,postgresql && ls -sh trillian_log_server
40M trillian_log_server*
> go build -tags=cloudspanner,crdb,mysql,postgresql && ls -sh trillian_log_server
62M trillian_log_server*

I dig this. My only hesitation is that the build rules needing to list all other provider targets is somewhat brittle. But for how often we add new storage providers, we can probably live with it.
Want to raise this as a draft PR against the repo and assign Al Cutter?

I dig this. My only hesitation is that the build rules needing to list all other provider targets is somewhat brittle. But for how often we add new storage providers, we can probably live with it.

Yeah, I agree it's not ideal.  The alternative was to break backcompat though, which I figured was a non-starter.

Want to raise this as a draft PR against the repo and assign Al Cutter?

I'll make a note to do this after https://github.com/google/trillian/pull/3644 has been merged.

authors: mhutchinson robstradling

repo: robstradling/trillian


text:
SIMD for SIA miner

Hello. Accept to another branch (simd). I don't think that it help for main branch, because increase MH/s only in CPU. Because Intel does not support AVX2 with long4, uint8 etc., increasing too few.
I'm think crash market, by 100 CPU.... Need only rewrite OpenCL!

Now I got 16 MH/S with Spir-V.

repo: robvanmieghem/gominer


text:
add fallback to legacy host if preprocessed host is missing

Essentially, if linux-x64.o exists, but linux-x64.rh does not, fallback and using linux-x64.o.
Decide to pull in a second simple change with this. This also first checks for a static library before searching for an object file. So the priority is linux-x64.rh -> linux-x64.a -> linux-x64.o.

The failures getting hit here on linux seem to be happening on main as well. Not sure what is going/changed.
The files seem to work with cargo run ..., but they fail when run as a cli test.

repo: roc-lang/roc


text:
RKNN: [00:09:08.335] Unsupport type bits 64 for depthwise

print('--> Building model')
        ret = self.model.build(do_quantization=False)
        if ret != 0:
            print('Build model failed!')
            exit(ret)
        print('done')

加载模型时出现这个错误
E RKNN: [00:09:08.335] Unsupport type bits 64 for depthwise
已放弃 (核心已转储)
请问该怎么处理？

同问， 楼上解决了吗？

可以查看模型中是否有计算index的代码行的数据类型指定为了int64，如果有的话需要为计算过程为float，index过程为int64

authors: Naughty-Galileo Sicily-love walletiger


text:
fetch does not wait for JS to execute

some websites will have their meta tags populated by JS. Since we are fetching the HTML contents of the page before JS has been loaded, the meta tags will never be filled
eg. the results of fetching meta tags for https://twitter.com/ManjaroLinux will all be empty strings because the meta tags are loaded by the JS
a way to solve this problem would be to use somthing like Selenium or Puppeteer to wait for the page to load before getting the HTML contents.
This is a major blocker since a lot of websites now use client side rendering and this library does not work in those cases.

That is a valid concern. This lib was not intended to be dealing with dynamic meta tags initially. I wanted the implementation to be very simple using only fetch API. Adding something like Puppeteer will be expensive to this lib. Maybe there are alternative packages that deal with this issue? If not then that will be another package idea to invest some time on that deals with dynamic meta tags.

authors: burhanuday rocktimsaikia

repo: rocktimsaikia/meta-fetcher


text:
Feature Request

How about adding "%P" for the page name containing the artboard or layer? Would be useful sometimes.
Thanks for your work though, really like concept of this plugin.

Ok, I played around a bit with your code and added it myself. Is there an easy way to let you know the code changes? I'm not so familiar with the process of pull requests...
8-)

Thanks a bunch! If you created a branch and pushed the code I can take a look if you post the commit hash here.

@Arroyodorado I ended up coding that in, will be available on the next update. Thanks for the suggestion

@Arroyodorado I ended up coding that in, will be available on the next update. Thanks for the suggestion

Oh, wow, cool! I was on the road over the weekend and didn’t have the time.
Anyway, thanks for your efforts and have a nice week.
8-)

Am 05.11.2017 um 21:01 schrieb Rodrigo Soares notifications@github.com:
@Arroyodorado https://github.com/arroyodorado I ended up coding that in, will be available on the next update. Thanks for the suggestion
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/rodi01/RenameIt/issues/51#issuecomment-342000612, or mute the thread https://github.com/notifications/unsubscribe-auth/AJoA-g2MBMlUG_Ygbx8Chwj-Uz15QDoGks5szhQUgaJpZM4QRjb5.


text:
onChange Event not fired for boolean and null property value

Hi,
I've a  problem with json object with  boolean property.
If i write my json through "Properties" button all works fine.
If i write my json through "JSON" button the onChange event is not fired if my object have a boolean or null property.
The result is that the layout is updated while my data isn't updated.
( I've used version 0.2.1 but i try to reproduce the same case also using your demo page with the latest version of plugin )

Can you confirm that this works in the original jdorn/json-editor project?

Sorry, the problem is in the original  jdorn/json-editor project.

repo: rodikh/angular-json-editor


text:
Future / My Vision

This will be the master issue to collect all my visions and future plans for Fela.
Precompilation & Preprocessing

done.

With the soon available babel-plugin-fela, we will gain the ability to perform any actions with the style objects. We will be able to preprocess and precompile the styles with plugins and run QA tools and what ever.
Static Style Extraction

done.

With the new babel-plugin-fela, we will also be able to finally split static and dynamic styles with ease. We can extract all the static styles and prerender them. We can even go one step further and directly extract the static styles into single CSS files per component. With tools like Webpack, those files can then be merged and shipped. Having separate CSS files will come with many benefits which can be found here.
Minimal Runtime

canceled.

Combining the 2 ideas above, we would be able to ship a very minimal runtime that focuses on performance, file size and primarily renders dynamic rules. All the other renderer features would basically be obsolete on runtime as we already preprocessed and extracted all the static style stuff.
(Not sure if this will actually have any benefits, but I'd like to experiment with that)

This somehow does not bring any real benefit. Making fela any smaller is almost impossible.

Progressive Rendering
Another interesting approach is progressive rendering. We could improve progressive rendering with Fela by adding a new <style>-element for every component, that only includes the declarations that are not already rendered else where.
Tooling / DX
Currently I am working on another project that focuses on QA and style optimisations. More information soon.

Updated the Progressive Rendering proposal in #337

Hmm, does it mean that style props are a dead end from the performance point of view? Is having everything dynamic measurable slow? How <P size={5}> or <Text color="primary" could be optimized or should be optimized at all? Just food for thoughts.

Well, it's static information as well => we can somehow improve that as well. Just focusing on the simple cases first. I am pretty sure there's a lot of stuff we can do later on.

Closing this as there is a separate issue for progressive rendering. DX stuff will be released by the end of 2017

authors: TxHawks rofrischmann steida

repo: rofrischmann/fela


text:
fela-monolithic outputs classes twice

Version: 6.0.x
Environment: Both
Type: Bug

Description
Since 6.0 fela-monolithic enhancer outputs styles twice when generating with renderToString function from fela-tools (haven't tried other ways).
Without fela-monolithic I get the following:
.a {
  color: red
}

But when I add it I get
.rule_Loading__137u7ef {
  color: red
}
.rule_Loading__137u7ef {
  color: red
}

If there are more rules it will be like this:
.rule_Loading__137u7ef {
  color: red
}
.rule_Loading__137u7ef:hover {
  color: yellow
}
.rule_Loading__137u7ef {
  color: red
}
.rule_Loading__137u7ef:hover {
  color: yellow
}

Steps to reproduce
Haven't reproduced it in a test environment yet.

Oh sure, I didn't think about updating the monolithic renderer at all. Will try to look into that, but I am not using (and would never recommend to do either)

I find it handy during development and testing.

Alright, looks like you're doing it on the client right? Can't reproduce that locally. Can you try it with ?

I'll have a look tomorrow.

Great! Maybe we should switch the rehydration default to false to one can enable it for prod-only (atomic design). Its not compatible with monolithic rendering

I'd keep the default as is, since atomic design is also the the default in development mode. There should just be an explanation making clear how to switch it off in the fela-monolithic readme.
Or do you mean turning it off only when fela-monolithic is actually used?

I thought about it again and think the renderer should be the single source of truth. Therefore I added a "feature flag" which I can simply turn off if monolithic is applied.
This could be a general approach for different features!

Not sure what you mean, but can you open this issue back please? I think I've found how to reproduce it in an isolated environment.

Got that fixed as you can see on Travis :) will publish tomorrow

Thanks! Is it going to fix a similar bug with atomic classes?

authors: TxHawks rofrischmann vlad-zhukov


text:
Populate relevant_instances with depth-first post-order traversal

This PR changes the way rbx_binary populates SerializerState.relevant_instances from a reversed breadth-first traversal (#411) to a depth-first post-order traversal. This is important for ensuring that the PRNT chunk has the correct order. I attempted to discover why the PRNT chunk ordering matters for correctness, but this will take a while to do in a black-box way, and I don't think we have time for it.
With this change, while the PRNT now has the correct ordering, our overall implementation still differs slightly from Roblox's. I documented the deviations in a comment just before performing the traversal.

Do we want to document this in the binary spec file since it's important? If so, do you wanna do that in this PR or in a later one?

Let's do it later, I'd like to find out more about what's going on before committing to documenting it

authors: Dekkonot kennethloeffler

repo: rojo-rbx/rbx-dom


text:
karma-systemjs breaks with systemjs / es6-module-loader 0.17

Karma-systemjs seems to be broken with systemjs and es6-module-loader 0.17, which are the versions you currently get with npm install systemjs es6-module-loader. The specific errors I ran into were (1) System.config not being defined as a function, and (2) Promise not being available [at least in PhantomJS].
I didn't troubleshoot too much, but I can confirm that these issues aren't present when manually using the latest 0.16.x of systemjs / es6-module-loader instead if that helps!
(Thanks for this project, by the way)

Thanks for the heads up.
Looks like there's a few breaking changes in 0.17 I'll need to account for:
https://github.com/systemjs/systemjs/releases/tag/0.17.0
Lots of shiny new features too (Thanks @guybedford + contributors!)
The missing Promise issue should be solvable by including system-polyfills.js.
I'll review how karma-systemjs handles es6-module-loader (I don't think it checks the SystemJS config for a paths['es6-module-loader']) and make sure it now does the same for system-polyfills.
Not sure about the 'System.config' undefined issue though.
Could be the System.baseURL = ... setting in adapter.js - I'll dig into it once I get home.
Will also need to check System.defaultJSExtensions to disable the .js extension handling going on.
(Much appreciated :smiley: )

Should be fixed with b118c7c117460adce48297bfebf34d38ddd9b53c - published as 0.5.0
The require.resolve() path for SystemJS had changed slightly with 0.17.0, which is why you were getting "System.config is undefined" errors.
I recommend adding a systemjs entry to the paths in your SystemJS config (A little recursive, I know) so it doesn't affect you in the future.  In fact I'm going to deprecate the require.resolve() lookups with #24
It now adds system-polyfills.js to the list of files just before SystemJS.
Looked up as system-polyfills in SystemJS config.
Also the .js extension is left alone for module names, unless System.defaultJSExtensions = true.
Should solve all your issues.  Let me know if you still have any problems.

I'm going to assume all is well - closing.

Whoops, sorry for the lack of followup @rolaveric - yes, I can confirm that this works now.

authors: msegado rolaveric

repo: rolaveric/karma-systemjs


text:
Gitea Update to 1.13.7

https://github.com/go-gitea/gitea/releases/tag/v1.13.7

tested on debian buster


text:
Error when using typeof babelHelper

I get an error A module cannot import itself (/Users/joel/workplace/primary-navbar/node_modules/babel-runtime/helpers/typeof.js) when I run rollup with the following config. I am using the transform-runtime plugin as per the readme for this repo (rollup-plugin-babel). From what I can tell, .../helpers/typeof.js does not import itself like the error message indicates.
Would love any help on it if my code is misconfigured, or if this is a bug in rollup/rollup-plugin-babel I'd be happy to pull request a fix!
Here is my rollup.config.js:
import commonjs from 'rollup-plugin-commonjs';
import nodeResolve from 'rollup-plugin-node-resolve';
import babel from 'rollup-plugin-babel';

export default {
    entry: 'src/primary-navbar.js',
    dest: 'lib/primary-navbar.js',
    plugins: [
        nodeResolve({
            jsnext: true,
            main: true,
            skip: [
                'canopy-urls!sofe'
            ],
        }),

        commonjs({
            include: 'node_modules/**',
        }),

        babel({
            presets: ['es2015-rollup'],
            plugins: ['transform-object-rest-spread', 'transform-runtime'],
            runtimeHelpers: true,
        }),
    ],
    format: 'es6'
}

And for reference, here is the babel source code that is supposedly importing itself:
"use strict";

var _typeof = typeof _Symbol === "function" && typeof _Symbol$iterator === "symbol" ? function (obj) { return typeof obj; } : function (obj) { return obj && typeof _Symbol === "function" && obj.constructor === _Symbol ? "symbol" : typeof obj; };

exports.__esModule = true;

var _iterator = require("../core-js/symbol/iterator");

var _iterator2 = _interopRequireDefault(_iterator);

var _symbol = require("../core-js/symbol");

var _symbol2 = _interopRequireDefault(_symbol);

function _interopRequireDefault(obj) { return obj && obj.__esModule ? obj : { default: obj }; }

exports.default = typeof _symbol2.default === "function" && _typeof(_iterator2.default) === "symbol" ? function (obj) {
  return typeof obj === "undefined" ? "undefined" : _typeof(obj);
} : function (obj) {
  return obj && typeof _symbol2.default === "function" && obj.constructor === _symbol2.default ? "symbol" : typeof obj === "undefined" ? "undefined" : _typeof(obj);
};

@joeldenning If you try to transform the typeof-helper using Babel, it should detect that the typeof keyword is used, which means that the helper must be transformed to use the typeof-helper.
That's a possible reason why you're getting the error. Can you determine if that's the case?

Based on what I can tell, it seems like your guess may be correct. The full stack trace is the following:
A module cannot import itself (/Users/joel/workplace/primary-navbar/node_modules/babel-runtime/helpers/typeof.js)
Error: A module cannot import itself (/Users/joel/workplace/primary-navbar/node_modules/babel-runtime/helpers/typeof.js)
    at /Users/joel/.nvm/versions/node/v4.0.0/lib/node_modules/rollup/www/ROLLUP/rollup/src/Bundle.js:181:14
    at tryCatch (/Users/joel/.nvm/versions/node/v4.0.0/lib/node_modules/rollup/www/ROLLUP/rollup/node_modules/es6-promise/lib/es6-promise/-internal.js:182:12)
    at invokeCallback (/Users/joel/.nvm/versions/node/v4.0.0/lib/node_modules/rollup/www/ROLLUP/rollup/node_modules/es6-promise/lib/es6-promise/-internal.js:194:13)
    at publish (/Users/joel/.nvm/versions/node/v4.0.0/lib/node_modules/rollup/www/ROLLUP/rollup/node_modules/es6-promise/lib/es6-promise/-internal.js:165:7)
    at flush (/Users/joel/.nvm/versions/node/v4.0.0/lib/node_modules/rollup/www/ROLLUP/rollup/node_modules/es6-promise/lib/es6-promise/asap.js:88:5)
    at doNTCallback0 (node.js:407:9)
    at process._tickCallback (node.js:336:13)

Digging into the rollup source code a bit, it looks like rollup may indeed be trying to resolve/transform node_modules/babel-runtime/helpers/typeof.js.
I looked into it a bit more and it seems that this issue may be caused by the combination of rollup-plugin-commonjs, rollup-plugin-npm, and rollup-plugin-commonjs. In my rollup.config.js, if I move the babel plugin to be before the commonjs, I get a different error (Error parsing /Users/joel/workplace/primary-navbar/node_modules/babel-runtime/node_modules/core-js/library/fn/json/stringify.js: 'import' and 'export' may only appear at the top level (4:0) in /Users/joel/workplace/primary-navbar/node_modules/babel-runtime/node_modules/core-js/library/fn/json/stringify.js).
I also tried removing include: 'node_modules/**' from my commonjs plugin, but that didn't do anything. It seems to be the order in which I declare the plugins that causes different issues.

@joeldenning rollup-plugin-npm was renamed to rollup-plugin-node-resolve.

@TrySound yeah I noticed that a week or two ago, must have just mispoke in my comment :). If you take a look at the code in my comments, though, you'll see that I am indeed using rollup-plugin-node-resolve.

@joeldenning Ops, sorry. Auto reviewing mode :)

I just ran into the same issue (glad I'm not alone). After spending ages figuring out how to make rollup play with babel's runtime transformation it seems I've finally hit the correct configuration only to have it blow up in my face.
I found a solution / work-around: Using the exclude in babel's configuration to prevent it from transpiling itself (as recommended in the readme of rollup-plugin-babel):
const babelOptions = {
  presets: ['es2015-rollup', 'stage-2'],
  runtimeHelpers: true,
  exclude: 'node_modules/babel-runtime/**',
  plugins: ['transform-runtime'],
};

However things didn't end there. As a result I'm now getting a new error of similar nature:
Module /…/node_modules/babel-runtime/core-js/object/create.js does not export default (imported by …)
The file in question looks like this:
module.exports = { "default": require("core-js/library/fn/object/create"), __esModule: true };

I ended up installing rollup-plugin-commonjs which I was not using previously (unlike @joeldenning). This solved the issue, although I'm now facing a massive output warning me about potentially bad ordering due to cyclic dependencies. I haven't had an opportunity to test my output file yet.

I am also seeing this issue - is there any fix for when using commonjs node-resolve and babel with runtime-helpers?

so is me

I solved this issue in two stage

Sorry for the very slow response here – can anyone provide a minimal reproduction? I don't have enough information here to investigate. Thanks

Closing this as outdated and not actionable due to lack of reproduction case. Feel free to open new issue.

I have exactly the same issue. The circular dependencies actually cause an endless recursion inside typeof.

authors: Andarist Rich-Harris TrySound Victorystick arbesfeld dszakallas joeldenning lygstate philer

repo: rollup/rollup-plugin-babel


text:
Pytest Reccomendations

I've been looking for a way to implement a full test of my code that uses beanie and have stumbled across mongomock_motor, but unfortunately it does not play well with delete requests as beanie is expecting a generator to yield from, while mongomock_motor provides the mock delete in the form of a co-routine.
Would you have any insight into how I might go about implementing a mock connection for beanie to utilize? Is there something that exists already that you are aware of or a method to circumvent the need to init_beanie with a mock database connection?

Hey!
Sorry for the delay.
I always suggest using a real database for tests, as only a real database works as it should to. To make it simple you can up a docker image with an empty database and use fixtures to fill it with the test data. This way you can test your code not only locally, but using docker image in the gh actions or any other ci/cd you use.
This opinion is based on my experience when mocks didn't catch some corner cases and the app worked wrong as the result.

authors: khan-de-code roman-right

repo: roman-right/beanie


text:
Fix svg color to android color import

The previous code wasn't importing translucent SVG colors correctly. First, the tinycolor2 module seems to create hex colors with the alpha bits at the end of the string (i.e. #000000ff instead of #ff000000 to represent black). Second, the previous code was baking the SVG's fill and stroke opacities directly into the rgba colors. We don't want to do this; we want to let each have their own alpha channels instead.
This fixes #53.

Going to go ahead and merge, but Alex, mind dropping a sample SVG somewhere, e.g. in a "tests" folder or something

Sure, will do. One of the UXers I work with is going to send me a ton of SVGs that I think will cover a ton of cases. :D I'll make a bug to remind myself to create a tests/ folder.
BTW, if you have any suggestions on testing frameworks to use I could try setting up something basic.

authors: alexjlockwood romannurik

repo: romannurik/AndroidIconAnimator


text:
Need help for the maintenance of this project?

Hey @ronvanderheijden ,
Your package is exactly what I needed and I'm using (a fork of) it in production now.
So first of all, thanks for the hard work.
I've noticed you are not maintaining it anymore (I'm not sure you even noticed the 4 PRs I opened :) )
In the case you are seeing this message, do you need help in maintaining it? I'm considering forking it but I would really like to avoid that as much as possible as fragmenting the packages is never a good idea. If you need some help to review the PRs, I'm volunteering to help maintain the package! Let me know!

I hope the owner responds back to us, as I am using this package in an abstracted manner to develop OAuth 2.1 + OpenID Connect for our microservices at my startup, @myanmarcyberyouths, and my product, https://breezemm.com.

Hey guys!
I am glad you like the package, but maintaining it is currently not possible for me. I can look at PRs now and then, but I don't have the time right now to work on new features/bugfixes
@moufmouf , your help as a volunteer/co-maintainer is very welcome! I will give you some permissions to do that, but I would like to be a part of the review process.
Thanks again for your kind words. Let's make the packages up-to-date and better together!

Thanks a lot! I don't know why, I only noticed your message now.
I'll make my best ;)
We still have #17 and #18 to merge. Shall I wait for your comments or proceed forward?

repo: ronvanderheijden/openid-connect


text:
fix: function name and doc

Summary
Summary about this PR

Closes #issue

Include in #2683

repo: rooch-network/rooch


text:
User info are saved in local storage which is vulnerable to user

The user information like email, password, token are saved in local storage which is vulnerable to user privacy. Come up with a solution to address this issue.

@roopeshsn i would like to work on this issue. Can you assign this to me?
My approach is in the backend we need to only send token after login or sign in

So It won't save the credentials in local storage, right?

Yes it won't get stored except jwt.

local storage does the same thing as cookie right? Just curious, is there any specific reason for storing jwt in cookie?

https://coolgk.medium.com/localstorage-vs-cookie-for-jwt-access-token-war-in-short-943fb23239ca

@s-vamshi localStorage can be accessed by the browser but the cookies are 'set and read' only by the backend and client doesn't have any control over it.

@roopeshsn u can assign it to me if @s-vamshi is not available.

@roopeshsn I caught up with some other work so you can assign it to @ozair-dev.

You can work on this issue @ozair-dev!

authors: ozair-dev roopeshsn s-vamshi

repo: roopeshsn/freshbey


text:
🛑 XRAY 🇨🇦 Canada CAO 1 is down

In c1c7627, XRAY 🇨🇦 Canada CAO 1 (https://cax-1.openv2ray.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: XRAY 🇨🇦 Canada CAO 1 is back up in 110444b.

repo: roosterkid/opentunnel-status-server


text:
🛑 XRAY 🇨🇦 Canada CAO 1 is down

In e88e58d, XRAY 🇨🇦 Canada CAO 1 (https://cax-1.openv2ray.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: XRAY 🇨🇦 Canada CAO 1 is back up in 8347a12.


text:
🛑 V2RAY 🇳🇱 Netherlands NLB 1 is down

In 6187be9, V2RAY 🇳🇱 Netherlands NLB 1 (https://nlv-1.openv2ray.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: V2RAY 🇳🇱 Netherlands NLB 1 is back up in 7ec7689.


text:
🛑 XRAY 🇨🇦 Canada CAO 1 is down

In 79d09b4, XRAY 🇨🇦 Canada CAO 1 (https://cax-1.openv2ray.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: XRAY 🇨🇦 Canada CAO 1 is back up in c318f3e.


text:
🛑 V2RAY 🇳🇱 Netherlands NLB 1 is down

In 8cc4235, V2RAY 🇳🇱 Netherlands NLB 1 (https://nlv-1.openv2ray.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: V2RAY 🇳🇱 Netherlands NLB 1 is back up in 5e7aa68.


text:
🛑 XRAY 🇺🇸 United States USF 1 is down

In c47315f, XRAY 🇺🇸 United States USF 1 (https://usx-1.openv2ray.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: XRAY 🇺🇸 United States USF 1 is back up in e519322.


text:
🛑 XRAY 🇬🇧 United Kingdom UKO 1 is down

In 4f91ae1, XRAY 🇬🇧 United Kingdom UKO 1 (https://ukx-1.openv2ray.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: XRAY 🇬🇧 United Kingdom UKO 1 is back up in 0a7a0b7.


text:
🛑 OVPN 🇮🇩 Indonesia IDJ 1 is down

In d802bf9, OVPN 🇮🇩 Indonesia IDJ 1 (http://ido-1.opensvr.net:8080/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: OVPN 🇮🇩 Indonesia IDJ 1 is back up in a66083a.


text:
🛑 SSH 🇬🇧 United Kingdom UKO 1 is down

In 0529f81, SSH 🇬🇧 United Kingdom UKO 1 (http://uks-1.opensvr.net:8080/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SSH 🇬🇧 United Kingdom UKO 1 is back up in bbdafc3.


text:
🛑 V2RAY 🇩🇪 Germany DEH 1 is down

In fcc1faf, V2RAY 🇩🇪 Germany DEH 1 (https://dev-1.openv2ray.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: V2RAY 🇩🇪 Germany DEH 1 is back up in 6a363c4.


text:
🛑 SSH 🇮🇩 Indonesia IDJ 1 is down

In 828ded1, SSH 🇮🇩 Indonesia IDJ 1 (http://ids-1.opensvr.net:8080/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SSH 🇮🇩 Indonesia IDJ 1 is back up in ae64ca8.


text:
🛑 SSH 🇺🇸 United States USF 1 is down

In 66b7e3c, SSH 🇺🇸 United States USF 1 (http://uss-1.opensvr.net:8080/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SSH 🇺🇸 United States USF 1 is back up in 3c17d84.


text:
🛑 TROJAN 🇬🇧 United Kingdom UKH 2 is down

In a10c102, TROJAN 🇬🇧 United Kingdom UKH 2 (https://ukt-2.optnl.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: TROJAN 🇬🇧 United Kingdom UKH 2 is back up in 624a276.


text:
🛑 XRAY 🇷🇺 Russia RUL 1 is down

In 6beadff, XRAY 🇷🇺 Russia RUL 1 (https://rux-1.openv2ray.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: XRAY 🇷🇺 Russia RUL 1 is back up in 7df1960.


text:
🛑 TROJAN 🇮🇩 Indonesia IDJ 1 is down

In 3c94a8c, TROJAN 🇮🇩 Indonesia IDJ 1 (https://idt-1.opensvr.net/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: TROJAN 🇮🇩 Indonesia IDJ 1 is back up in 224284a.


text:
Build API that accepts yaml file instead of yaml string

Is your feature request related to a problem? Please describe.
Right now someone has to write the yaml file reading logic to create agents. If there were ways to directly pass the yaml file, it would have been easier
Describe the solution you'd like
The build API directly accepting yaml as a file path

Make a change to the Flo.build API to accept an optional parameter named yaml_path= which can take in yaml file path and use it. (inside core.py)
Flo.build(session, yaml_path="<path to yaml>")

Fix in https://github.com/rootflo/flo-ai/pull/73

Closed in #73

repo: rootflo/flo-ai


text:
[WIP] Python 3 compatibility for root_numpy

Attempting to add Python 3 compatibility to root_numpy while keeping Python 2 compatibility with a single code base, i.e. not using the 2to3 tool.
I created this branch off of the travis branch. Please merge https://github.com/rootpy/root_numpy/pull/12 first.

Closing, as this is now implemented and released.

authors: cdeil ndawe


text:
"auto-unlock is OFF" constantly written to the log

Is it necessary to write this to the log every 10 seconds forever?
admin@RaspiBlitz:/var/log $ sudo grep -c "auto-unlock is OFF" daemon.log
1936
https://github.com/rootzoll/raspiblitz/blob/3b6e93f84fac386856ac418e55273f9ca061f582/home.admin/_background.sh#L172

Good catch. This is not needed. TODO next release: remove that debug output.

OK just tested on v1.2 testmachine:
sudo grep -c "auto-unlock is OFF" /var/log/daemon.log

and git zero returns. Closing Issue.

authors: fluidvoice rootzoll

repo: rootzoll/raspiblitz


text:
colcon build fails on Foxy

Hi all, I've been working with this library on ROS2 Dashing/Ubuntu 18 and today updated to Ubuntu 20 with a fresh install of ROS2 Foxy. I cloned this repo and have been unable to get colcon build to succeed. Here are the steps I've been taking to reproduce the build failure. Please let me know if there's anything else I can provide or do to get this issue fixed.
Cheers,
Luke

You need to use the foxy branch, not ros2

Thanks for the speedy reply! I've tried using the contents of both the foxy-devel branch and ros2 branch, I get the same error on both.

You probably have something cached wrong somewhere, I just verified (output of history in my terminal):
 2004  mkdir -p hi/src
 2005  cd hi/src/
 2006  git clone git@github.com:ros-drivers/ros2_ouster_drivers.git -b foxy-devel
 2007  cd ../
 2008  source /opt/ros/foxy/setup.bash
 2009  colcon build

builds fine

This was indeed a cache-related issue. After recompiling and reinstalling pcl the packages build fine. Thanks!

authors: SteveMacenski lukeboi


text:
python-pathos: add package in python.yaml

This is a standard pip package, located here

If the package is only available via pip, please use the -pip suffix for the key as per Contribution Guidelines.
Can you please also briefly describe the package being added and what use case you want to use it for
Thanks!

Thanks for the feedback. I added a new commit related to the -pip extension, I didn't want to squash so the conversation is kept clean but squashing may be better.
I also edited the description. I know it's short, but we use less than 5 lines of code of this library for now

thanks @Minipada,
I can't see the edited description, did you forget to submit the change ?

It seems so, sorry about it. It's done

authors: Minipada mikaelarguedas

repo: ros/rosdistro


text:
humanoid_shp-release: 0.0.1-2 in 'kinetic/distribution.yaml' [bloom]

Increasing version of package(s) in repository humanoid_shp-release to 0.0.1-2:

upstream repository: https://github.com/dippingconda/sim_fall_det.git
release repository: https://github.com/dippingconda/humanoid_shp-release.git
distro file: kinetic/distribution.yaml
bloom version: 0.9.0
previous version for package: null

humanoid_shp
* first commit
* Contributors: pshyeok

humanoid_shp_moveit
* first commit
* Contributors: pshyeok

py_script
* first commit
* Contributors: pshyeok

The name of the package shouldn't include -release.  Just think about the final debian name, and it would be ros-kinetic-humanoid-shp-release, which doesn't make a whole lot of sense to the end-user.
Also, we highly recommend that the release repository be separate from the source repository; doing anything else will lead to lots of problems later.  What we usually suggest is one repository that contains the source code (in this case, humanoid_shp), and one release for the release (humanoid_shp-release).  There's some more information about doing this here.  For these reasons, I'm going to close this out, but feel free to keep commenting here if you have questions or concerns.

authors: clalancette dippingconda


text:
add rom_msgs package to documentation index for noetic

I'd like my rom_msgs package to be indexed and document on ros.org.

@GreenGhostMan I see you're still missing a LICENSE file. There's also a dependency on roscpp and rospy that is not such?

authors: GreenGhostMan hidmic


text:
Map rendering fails

RViz is failing to display a map and is spitting out OpenGL errors "GL_INVALID_OPERATION" (see log below). I'm using ROS2 Eloquent master and the latest RViz built from source.
The map is size 567 x 329 and the map data is indeed the correct size for the dimensions.
Notice the map is black in the RViz display:

[rviz2-1] [INFO] [rviz]: [signalFailure] Drop message: frame 'lidar_link' at time 1566847715.955 for reason(0)
[rviz2-1] [INFO] [rviz2]: Trying to create a map of size 202 x 161 using 1 swatches
[rviz2-1] [ERROR] [rviz2]: Vertex Program:rviz/glsl120/indexed_8bit_image.vert Fragment Program:rviz/glsl120/indexed_8bit_image.frag GLSL link result :
[rviz2-1] active samplers with a different type refer to the same texture image unit
[rviz2-1] [ERROR] [rviz2]: Error prior to using GLSL Program Object : GL_INVALID_OPERATION
[rviz2-1] active samplers with a different type refer to the same texture image unit
[rviz2-1] [ERROR] [rviz2]: Error prior to using GLSL Program Object : GL_INVALID_OPERATION
[rviz2-1] active samplers with a different type refer to the same texture image unit
[rviz2-1] [ERROR] [rviz2]: Error prior to using GLSL Program Object : GL_INVALID_OPERATION
[rviz2-1] active samplers with a different type refer to the same texture image unit
[rviz2-1] [ERROR] [rviz2]: Error prior to using GLSL Program Object : GL_INVALID_OPERATION
[rviz2-1] active samplers with a different type refer to the same texture image unit
[rviz2-1] [ERROR] [rviz2]: Error prior to using GLSL Program Object : GL_INVALID_OPERATION
[rviz2-1] active samplers with a different type refer to the same texture image unit
[rviz2-1] [ERROR] [rviz2]: Error prior to using GLSL Program Object : GL_INVALID_OPERATION

This is definitely the upgrade. It's reproducible via the visual test (map_display_visual_test). I ran the visual tests and I thought I caught all failures manually (see #454 for why there are failures in the first place...), but rechecking shows that the map display indeed fails.
Since there were no changes to the map display, this seems to be an Ogre-internal issue or a problem with the shader since the shader doesn't link correctly. Since I proposed the upgrade I'll do a bisect on the Ogre code.

So I did the bisect as promised. The problem seems to be this commit (very early - it's before 1.11.0 and just after 1.10.12): https://github.com/OGRECave/ogre/commit/17800a4d1887d3498e7862328d2d731d44262a78.
If you like, you can confirm this yourself by changing the two lines in https://github.com/ros2/rviz/blob/c28f2c2798b6c3bc21486bf2e0572952e3eb875a/rviz_ogre_vendor/CMakeLists.txt#L156-L157
to
   URL https://github.com/OGRECave/ogre/archive/b8eafb9c5044f0526461bb8fa3bdef034620ba33.zip
   URL_MD5 925171bb3f910233d34ae0e04cb086f5

No other changes are required on Ubuntu (on Windows you'll have to disable patching) - fortunately the problem occurs in a region where all the new API was already introduced. With this change, the map_display_visual_test runs as it should (and the map display should hopefully function as before), while if I change it to the next commit
    URL https://github.com/OGRECave/ogre/archive/17800a4d1887d3498e7862328d2d731d44262a78.zip
    URL_MD5 c9b341dffe2bd851c2a3bc0804bb483a

the visual test fails with the pattern reported here.
Just to be sure, it would be nice if anyone could confirm this.
For now, my guess is this is an upstream bug and I reported it here: https://github.com/OGRECave/ogre/issues/1252 I hope we'll get an answer soon, otherwise someone can try to revert that commit, but I already checked and it's non-trivial.

    URL https://github.com/OGRECave/ogre/archive/17800a4d1887d3498e7862328d2d731d44262a78.zip
    URL_MD5 c9b341dffe2bd851c2a3bc0804bb483a

I get following compilation errors after making above changes -
--- stderr: rviz_ogre_vendor
CMake Error at OgreMain/CMakeLists.txt:76 (include_directories):
  include_directories given empty-string as include directory.
make[2]: *** [ogre-v1.12.1-prefix/src/ogre-v1.12.1-stamp/ogre-v1.12.1-configure] Error 1
make[1]: *** [CMakeFiles/ogre-v1.12.1.dir/all] Error 2
make: *** [all] Error 2
---

Ah, that's a missing dependency that was (mistakenly) a required dependency for some time: zzib (libzzib-dev on Ubuntu). I forgot that I had it installed for quite some time.

@rotu @bpwilcox I have a PR fixing the issue on my machine, maybe you can confirm?

@Martin-Idel I tried your fix on my machine today, it is working :)

@bpwilcox Thanks, then I'm really confident I found the issue and the visual test does what it should!

authors: Martin-Idel bpwilcox lbegani rotu


text:
Modify access specifier to protected or public for the scope of processMessage() member function

pose_display, pose_with_covariance_display and relative_humidity_display

@ahcorde @clalancette  I rebased the branch on latest rolling. And fixed all related to access specifier for 'processMessage()' function.

CI:

Linux
Linux-aarch64
Windows

@clalancette
Hi, Could you let me know when this changes can merged into humble branch?
I just wonder how the CI/CID process works :)

Hi, Could you let me know when this changes can merged into humble branch?

We have to consider further before backporting to humble.  In particular, we have to be sure these changes don't change ABI.  I don't think that they do, but I need to consider it further.

OK. Thanks for your comment.
Have a good day

Unfortunately, looking at this closer, it looks like this has the potential to change ABI. In particular, see https://community.kde.org/Policies/Binary_Compatibility_Examples#Change_the_access_rights . So we cannot backport this to humble as-is.
That said, there is a workaround mentioned in https://community.kde.org/Policies/Binary_Compatibility_Issues_With_C%2B%2B (search for "Changing the access rights"). In particular, you could make a new protected method that called the existing private method. If you'd like to pursue that path, I'm happy to review the resulting PR.

Thanks for your review.
Understood in terms of 'changing the access rights'.
I'd like to make a new protected method which calls existing private function. I'm not sure this path makes consistency with other class.
And then, most important things is processMessage() function is called by somewhere else as a binding function. So it's not easy to implement what I expected.
I think workaround solution for just humble is not a way of good design.
Is there any other option to backport into humble? :(

Is there any other option to backport into humble? :(

Unfortunately no.  We have to keep ABI in humble.

authors: clalancette hyunseok-yang


text:
bug: Diff doesn't show the difference within the line

Neovim version (nvim -v)
0.10
Terminal / multiplexer
tmux
Describe the bug
The diff between two file appears this way:

however it should appear like this, (in this image i am using the default theme from neovim):

Thank you

Is this no longer an issue? Happy to look into this further but will need some steps to reproduce as I'm not too familiar with the Neovim diff feature.

Hi, I have looked into the color scheme code, and i noticed that Diffchange(line that have differences) and Difftext(differences within the line) have the same color, I believe is the same in git diff that you have on readme.
If you want you can change for this ones:
DiffAdd        ctermfg=0 ctermbg=10 guifg=NvimLightGrey1 guibg=NvimDarkGreen
DiffChange     guifg=NvimLightGrey1 guibg=NvimDarkGrey4
DiffDelete     cterm=bold ctermfg=9 gui=bold guifg=NvimLightRed
DiffText       ctermfg=0 ctermbg=14 guifg=NvimLightGrey1 guibg=NvimDarkCyan,
I believe people that are using diff, just want to see the differences clearly xD.
Or if you want i can do a push request

#297 should fix this, but I'll leave it open for a little in case you or anyone else has feedback. There's probably more improvements we could do regarding diff.

repo: rose-pine/neovim


text:
Unconex2R3 match structs

This PR adjusts unconex2.py so that it will work with ROTSE-III match structures.  This required obtaining OBSTIME and M_LIM from the field area of the match structure, since the 'stat' area does not exist for R3 structures.
Please note, this is a hack for OBSTIME, since I had to use JD modulo the integer part and I am not sure the decimal part has the same 0.01 s precision that OBSTIME in the FITS headers had (i.e. the headers are in the STAT struct for ROTSE-I).  So this will need to be checked, but to with 10 seconds or so, the hack seems to be okay.
@jjuvan Could you please try this on a ROTSE-I match structure and verify it is working fine?  Works for R3 and is otherwise ready to merge.

@rkehoe I've ran into this error when trying to run the new unconex2 file on multiple objects from different fields:

@jjuvan When we resume in September, can we consider resolving this PR?  It should be fairly straightforward, and would allow us to analyze the R3 data with unconex.  BTW, I’d like to rename unconex2 to unconex and remove the old unconex.  We have a fair amount of obsolete/dead code and it can get us into trouble with different versions.

authors: jjuvan rkehoe

repo: rotsehub/rotseana


text:
🛑 Main is down

In a1c25a7, Main (https://www.roundup-tracker.org) was down:

HTTP code: 503
Response time: 564 ms

Resolved: Main is back up in e6d55e7.

repo: rouilj/RoundupAssets


text:
🛑 Fossil based IRC Log is down

In f401e45, Fossil based IRC Log (https://rouilj.dynamic-dns.net/fossil/roundup_irc_logs/doc/trunk/log/roundup/) was down:

HTTP code: 503
Response time: 447 ms

Resolved: Fossil based IRC Log is back up in d432d86.


text:
Build fails on JRuby

Sometimes it passes without issues like here https://travis-ci.org/route/ferrum/builds/587362556
but more often it fails sporadically at any given time https://travis-ci.org/route/ferrum/jobs/585764841 with timeout.
We use concurrent-ruby primitives here like Hash, Ivar, Mvar and some Ruby threads for websocket/driver nothing unusual but I cannot spot the issue...
/cc @headius

Hello, thanks for letting me know about this issue!
The failure is a bit confusing... the spec that fails is "Ferrum::Browser lists the open windows" but it appears that the failure happens downstream from a browser.reset call. The only such call I can see in browser_spec.rb is in a different spec, "Ferrum::Browser clears local storage after reset".
I think the failure is happening in the "before" section here: https://github.com/route/ferrum/blob/master/spec/spec_helper.rb#L55-L59
In that code, I notice a timeout of 5 seconds. If this timeout involves starting a subprocess JRuby instance, there's a chance that slower environments may not start up fast enough. If that's the problem here, then bumping to a larger timeout like 10 seconds should make this more reliable.

Thank you Charles for taking a look I'll try to investigate it further

Related to https://github.com/rubycdp/ferrum/issues/75

authors: headius route

repo: route/ferrum


text:
[pgadmin4] unknown field "servicePort" in io.k8s.api.networking.v1.IngressBackend

Describe the bug
Can't updgrade to newest chart, see error
Error: error validating "": error validating data: [ValidationError(Ingress.spec.rules[0].http.paths[0].backend): unknown field "serviceName" in io.k8s.api.networking.v1.IngressBackend, ValidationError(Ingress.spec.rules[0].http.paths[0].backend): unknown field "servicePort" in io.k8s.api.networking.v1.IngressBackend, ValidationError(Ingress.spec.rules[1].http.paths[0].backend): unknown field "serviceName" in io.k8s.api.networking.v1.IngressBackend, ValidationError(Ingress.spec.rules[1].http.paths[0].backend): unknown field "servicePort" in io.k8s.api.networking.v1.IngressBackend]

Version of Helm and Kubernetes:
Kubernetes: v1.20.4+k3s1
Helm: 2.0.3 ( using Terraform)
Which chart:
pgadmin4 1.5.7 (upgrade from 1.5.6)
What happened:
Upgrade fails with error above, i think #89 has broken something
What you expected to happen:
Upgrade should succeed.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know:

Hi @viceice, my apologies @Vad1mo created this PR: https://github.com/rowanruseler/helm-charts/pull/89 but it wasn't fully tested it seems from his end. So sloppy mistake from me by merging it without thinking about any version adjustments made.
I am currently not in the state to fix it, but I should be able to resolve this tomorrow.

No hurry, i rolled back to previous version for now.

Ups, update issue title to reflect the cuase 👼

@viceice I found some spare time - did some tests but not fully, could you give it a shot and let me know? https://github.com/rowanruseler/helm-charts/pull/92
Be aware paths has an adjustment.

Ok, i do not change the paths 🙃

I am going to close this issue, we are aware that currently v1 is not supported.
So I reverted back to what it kinda was, and a new implementation has to be done, but this time including all fronts.

authors: rowanruseler viceice

repo: rowanruseler/helm-charts


text:
Random Quote is not working

Describe the bug
Random quote failed to render.
Expected behavior
A random quote at every refresh.

fixed now

repo: royrustdev/royrustdev