Update stylesheet & Fix issues related with external APIs

New Features

Giscus user guide
Expose post entity ahead of the category items in search result

Minor Updates

Remove magnifying glass icon next to the search input area
Update stylesheet

Bug Fixes

Resolve indentation issues in search & categorization
Posting date is not displayed
Search result include Home URL
Top arrow button is not displayed
Wrong format for Goatcounter user code

I'd not seen any other functional issues. Thanks to @cvlian, minor bugs had been corrected in time and I inspected the demo website whenever a new build happens. It is working nicely now.

I had checked too @byanko55.
Think this is just an alpha test. You would not have to do patches all at once.

Looks like the text inside a code element is floating high

Think this is just an alpha test. You would not have to do patches all at once.

Looks like the text inside a code element is floating high

Which OS/device type did you test on?

Looks like the text inside a code element is floating high

Which OS/device type did you test on?

Firefox (CentOS 9 stream)

So, how about this? It seems the floating text is due to the inherent characteristic of 'Consolas' font. I selected new font-family to resolve it.

So, how about this? It seems the floating text is due to the inherent characteristic of 'Consolas' font. I selected new font-family to resolve it.

Looks better than it was. Thanks.


when using texteditiputformatter with textformfield The following assertion was thrown during a platform message callback: A KeyDownEvent is dispatched, but the state shows that the physical key is already pressed. If this occurs in real application, please report this bug to Flutter. If this occurs in unit tests, please ensure that simulated events follow Flutter's event model as documented in HardwareKeyboard. This was the event: KeyDownEvent#b75bd(physicalKey: PhysicalKeyboardKey#00000(usbHidUsage: "0x1100000000", debugName: "Key with ID 0x1100000000"), logicalKey: LogicalKeyboardKey#00008(keyId: "0x100000008", keyLabel: "Backspace", debugName: "Backspace"), character: " ", timeStamp: 55:18:26.243770) 'package:flutter/src/services/hardware_keyboard.dart': Failed assertion: line 437 pos 16: '!_pressedKeys.containsKey(event.physicalKey)'

Steps to Reproduce

Execute flutter run on the code sample
...
...

Expected results:
Actual results:

Code sample

Logs

@AhkamKhalaaf
Please don't put the entire error message as issue title. Follow new issue template and provide the requested details in it so that we'll have enough details to work with.
Closing as empty issue and no code or logs provided.


Prevent people from deleting datasources that have associate slices

We've had people deleting datasources without knowing that other slices/dashboard were making use of them, breaking things.  This should prevent that from happening.
This PR is also breaking down superset/connectors/base.py into a folder that aligns better with the related sqla and druid folders.
Ideally FAB would have something like the Django admin where it cascades deletes, but prompts the user first showing the tree of related objects getting deleted.

Coverage decreased (-0.002%) to 69.268% when pulling 6c89e829e97fbb7e28432c37d03485598b7e6b2a on mistercrunch:delete_datasource into c34df3eea40eacc59097fba14fab395bb0cd5989 on apache:master.

Coverage decreased (-0.002%) to 69.268% when pulling 6c89e829e97fbb7e28432c37d03485598b7e6b2a on mistercrunch:delete_datasource into c34df3eea40eacc59097fba14fab395bb0cd5989 on apache:master.

Coverage decreased (-0.002%) to 69.268% when pulling 6c89e829e97fbb7e28432c37d03485598b7e6b2a on mistercrunch:delete_datasource into c34df3eea40eacc59097fba14fab395bb0cd5989 on apache:master.


info & use case - "no way to override inheriting default/root layout in /routes" should be in documentation

Describe the problem
Based on Sveltekit documentation, it seems confusing that a +page.svelte can skip inheriting layouts in parent folders with the exception of the default layout in the /routes folder. Somewhere along the line Sveltekit team decided this was best, and I won't try to make the case for an override flag, although seems common for just outlier pages. My issue is I think this should be explained more clearly in the documentation.
This section should say something more like
https://kit.svelte.dev/docs/advanced-routing#advanced-layouts

Advanced layoutspermalink
By default, the layout hierarchy mirrors the route hierarchy. In some cases, that might not be what you want.
(group)permalink
Groups are a way to distinguish the layouts applied to pages; however, the default +layout.svelte in /routes will always be inherited unless it does not exist in /routes. Perhaps you have some routes that are 'app' routes that should have one layout (e.g. /dashboard or /item), and others that are 'marketing' routes that should have a different layout (/blog or /testimonials). We can group these routes with a directory whose name is wrapped in parentheses — unlike normal directories, (app) and (marketing) do not affect the URL pathname of the routes inside them:

Or adding a section of just added notes
*Note - if a default +layout.svelte is present in the /routes folder, this will be inherited by all routes.
Describe the proposed solution
This seems like a common use case. This issue already talks about it, and clearly confusion there also: https://github.com/sveltejs/kit/issues/6423
Is there any way we can add use cases to the documentation? I end up trying everything in the documentation, finding tons of outdated Reddit, Stack Overflow, Svelte.dev, Discord suggestions to recreate what seems like a common use case, skip inheriting a root layout, only to find its not possible. Whereas if the References section has some common Use Cases, we could build that out. In this case you could have use case with alternate path and indicating the default layout should have {#if} as discussed here https://github.com/sveltejs/kit/issues/6423
Alternatives considered
No response
Importance
would make my life easier
Additional Information
No response

This is noted in the first sentence of https://kit.svelte.dev/docs/advanced-routing#advanced-layouts-breaking-out-of-layouts , which is the more suiting place for this info since this is related to breaking out of layouts.

Yeah it makes more sense there @dummdidumm, but I found myself looking for "default layout" instead of "root layout" in the docs. Searching "root layout" I would have found this sooner. Can these terms be added to the Glossary? I found the definition for "default layout" but not "root layout" in the docs. Should I bother trying to fork and write up definitions?

I was looking for something like an added definition of 'root layout' in the documentation in whichever sections, something explicit, I ultimately can infer what the root layout is from here:

and here

I just thought something more clear and explicit could be put in the documentation to prevent the confusion I had along with the other post I found.
I'll just close though, as @dummdidumm  pointed out can at least get that info reading through documentation.


One post is breaking our RSS feed

Hey @mbjoseph -- the file: _posts/python/2016-07-05-creating-animated-maps-matplotlib-basemap.md is breaking our RSS feed. i'm not sure why. the YAML is ok so something in the code on the page is breaking it. in ATOM the file completely hangs up.
To fix this we have two options

you figure out why it's breaking the feed - it is something with the output md that is breaking it
A quick lazy fix for the RSS feed  - i add a YAML element that tells the rss feed to ignore this one post so the feed works.

i'm happy to do #2 to get the site up unless you have time to figure out 1 in the next week? Let me know! This won't affect the site and the feed on the website given this is an older post.

Very weird. This post has an interactive graphic, but it doesn't render on Jekyll. I think option 2 is probably our best bet.

temporarily turning off this post in the feed via an if clause using the title as the filter.
67b777272032dd3953ea86bf6a204ea224644760
it is a hack but for now, it is good enough to get the site up and running. closing this issue.

:/ too much goin on? Lemme know if the website stuff is too much!

It's fine - just making a joke! I have pushed the site https://earthlab.github.io/ (not sure whether you saw this)

I didn’t – I’ll check it out! I’ll update the feeds on the website and will remove a few lessons that I’m working on that are under dev. I forgot I didn’t want to push them just yet!!
Yay!
From: Max Joseph<EMAIL_ADDRESS>Reply-To: earthlab/dev-earthlab-site<EMAIL_ADDRESS>Date: Friday, December 2, 2016 at 2:07 PM
To: earthlab/dev-earthlab-site<EMAIL_ADDRESS>Cc: Leah Wasser<EMAIL_ADDRESS>State change<EMAIL_ADDRESS>Subject: Re: [earthlab/dev-earthlab-site] One post is breaking our RSS feed (#35)
It's fine - just making a joke! I have pushed the site https://earthlab.github.io/ (not sure whether you saw this)
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHubhttps://github.com/earthlab/dev-earthlab-site/issues/35#issuecomment-264562882, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AHS3quQtWlMtkr1Ur8DVw9RTxfjVWFg4ks5rEIiegaJpZM4LC3fT.


Permission denied error from home dictionary

As the title suggests, when I try to use cheat in my home directory I get the error message:
"failed to list cheatsheets: failed to load cheatsheets: failed to walk path: open /home/myuser/.cheat: permission denied"
when I am anywhere else (like /, /home,  /home/myuser/Downloads, /home/myuser/.cheat, /home/myuser/Documents, etc)
it is working as it is supposed to.
I checked ownership, permissions, they seem to be fine.
Any idea what the issue can be?

Hi, @matraven
This is likely related to the "directory-scoped cheatpaths" feature, though I don't understand the precise failure mode yet.
Please execute the following and paste the output in this thread:
ls -al ~/.cheat

(Feel free to redact anything that you feel could be sensitive.)
That should help us to figure out what's going on.
Thanks.

Hi @chrisallenlane,
Here it is.
─(12:11:11)──> la -al ~/.cheat                                 ──(Thu,Apr29)─┘
total 8.0K
drwxr-xr-x  2 name name 4.0K Apr  9 11:40 .
drwxr-xr-x 49 name name 4.0K Apr 29 12:11 ..

Thanks, @matraven. I'll drill into this.

@ddan4 that is a valid hint, as the snap version does not support dot folders in the users home directory.
@matraven is your installation snap based?

@bernermic It is.


Doc bug (?): UnpackArgs's optional params must all be marked with "?".

I think this is a documentation bug, but it might also be an implementation bug. For UnpackArgs, it says:
// If the parameter name ends with "?",
// it and all following parameters are optional.

To me, this implies that you only need to mark the first optional parameter with "?" and all following parameters are automatically optional.
However, the check is:
        // Check that all non-optional parameters are defined.
        // (We needn't check the first len(args).)
        for i := len(args); i < nparams; i++ {

In skipping the first len(args), you might skip over the first one marked with "?".
So the requirement (with the current implementation) seems to be that all optional parameters must be marked with "?" (and that they must be consecutive at the end of the list).
(Or you could make it work as the comment suggests by not skipping the first len(args).)

@nicks Nick, perhaps you could fold this into your PR?

:+1: sure!

re-reading this code, I think the bug report is wrong, because it misses the "break" a few lines below. I'm folding a test for it under https://github.com/google/starlark-go/pull/350


Check LFS version for smudge filter

As discussed in the issue: https://issues.jenkins-ci.org/browse/JENKINS-59139 , the smudge filter is no longer active for git >= 2.15 and git-lfs >= 2.3.0 .

Needs tests to confirm correct behavior when CLI git is not new enough and when it is new enough.

If the LFS backend requires authentication this is a breaking change because existing jobs would fail and require one of the workarounds below.
The current workaround I'm using is to not use the additional "Git LFS Pull after checkout" step and run git lfs pull manually in a controlled environment after after the checkout.
With this merged I'd have to either disable git lfs hooks globally on all slaves or set GIT_LFS_SKIP_SMUDGE=1 manually in my job.

I don;t see any activity on this pull request from the submitter.  I'm closing it.  We can reopen it if further activity happens.


Add a Hyperparameter Optimization survey paper

May I add a comprehensive Hyperparameter Optimization survey paper to this awesome list, please?
It is a very comprehensive survey paper about Hyperparameter Optimization and autoML, and it has the Github code as a tutorial:
https://github.com/LiYangHart/Hyperparameter-Optimization-of-Machine-Learning-Algorithms
Thanks!

@LiYangHart
Thanks for your contributions.
But it may be better to put this survey paper to the survey section.


[RFC] Idea to make testing more flexible: Effect interceptors

related #518
Redux Saga allows unit testing Sagas by using the Iterator approach. We iterate over the generator getting next values, and inspect the returned effects by some form of equality testing (eg deepEqual)
The approach allows testing a workflow without mocking APIs but some developpers raised an understandable concern: it couples the test to the internal implementation. Some may find this as desirable (test acts as specification of the Saga) but I think the lib can (and should) allow more flexibility around testing story.
Actually the lib offers only a choice between 2 extremes

Unit testing Saga by iterating over all the yielded effects
Integration testing using the classic mock approach (mocking the Redux store, APIs ...)

So I propose a new feature I called: Effect Interceptors. The idea is to make possible a fine-grained control over Effect resolution when running Sagas (using runSaga or through sagaMiddeware.run) we can provide an object which can intercept yielded effects and either

return a custom resolution value
execute the redux-saga's builtin interpreter
or combine both approaches

Example. Considering the Saga below

function* watchActions() {
  yield takeEvery('ACTION', handleActions)
}

function* handleActions(action) {
  const {data, error} = yield call(api.fetchData, action.payload)
  if(data) {
    yield put({type: 'SUCCESS', data})
  } else {
    yield put({type: 'ERROR', error})
  }
}

We can either test the whole watchActions workflow without mocking the api.fetchData function. We can let the middleware execute all the Effects normally and only intercept the execution of call effects to the API.
const mockApiResults = [
  { data: 'mock data' },   // the 1st call will return this result
  { error: 'mock error' }, // the 2nd call will return this result
  ...
]

const dispatchedActions = []

sagaMiddleware = createSagaMiddleware({
  interceptors: {
    call({context, fn, args}, execBuiltin, cb) {
      if(fn === api.fetchData) {
        cb(mockApiResults.shift())
      } else {
        execBuiltin(cb)
      }
    },
    put({action}, execBuiltin, cb) {
       // exec both builtin (dispatch to store) && custom (store dispatched actions)
       //  We could have monkey-patched the store.dispatch function but this would give us
       //  all dispatched actions (both dispatched by the Saga and from outside)
       // With this we're only interested in the actions dispatched by this Saga

       dispatchedActions.push(action)
       execBuiltin(cb)
    }
  }
})

const store = createStore(reducer, applyMiddleware(sagaMiddleware))
sagaMiddeware.run(watchActions)

// dispatch some actions
//store.dispatch(...)
//...

// Then inspect the result
assert.deepEqual(dispatchedActions, ...)

// can also inspect the state
assert.deepEqual(store.getState(), ...)

Or we can only test handleActions in isolation
const mockApiResults = [
  { data: 'mock data' },   // the 1st call will return this result
  { error: 'mock error' }, // the 2nd call will return this result
  ...
]

const dispatchedActions = []

runSaga(
  handleActions({type: 'ACTION', payload: ...})
  {
    interceptors:  { ... } // same as above
   }
)

// inspect the actions dispatched by this Saga
assert.deepEqual(dispatchedActions, ...)

Those are very rough examples. But the overall idea should be clear
What do you think? Is this something redux-saga should add? Can we improve the proposed approach?
And also, the main goal in my mind is to improve testing; but could we benefit from Effect interceptors in other areas?

Here's my 2 cents, worth what you paid for it:
I really like the idea in general, testing right now IMO is overly tied to the internal implementation. While I think the effect interceptors may be a good choice for a low-level primitive that will aid testing. I can't reasonably see myself constructing them due to the complicated signature/behavior:
interceptors: {
    call({context, fn, args}, execBuiltin, cb) {
      if(fn === api.fetchData) {
        cb(mockApiResults.shift())
      } else {
        execBuiltin(cb)
      }
    },
    put({action}, execBuiltin, cb) {
       // exec both builtin (dispatch to store) && custom (store dispatched actions)
       //  We could have monkey-patched the store.dispatch function but this would give us
       //  all dispatched actions (both dispatched by the Saga and from outside)
       // With this we're only interested in the actions dispatched by this Saga

       dispatchedActions.push(action)
       execBuiltin(cb)
    }
  }

But I could see myself doing something like #518 and running the saga with the full set of reducers and a given initial state but requiring certain effects such as call to be mocked so that we're limiting effect/state-riddled code (since the reducers should be pure). But it would probably be easiest as a library on top of redux-saga, or something built on top of the lower-level primitives.

I really like the attempt to give another possibility of testings as I think, just like @axelson, that the way of iterating through the iterator is just too tied to the implementation.
That being said I dont yet what to think about those interceptors. First of all - would be nice to find use case for them outside of testings, cause I generally dont like adding the code just for testings purposes, ofc completely different thing is writing the code in a way it can be tested more easily and/or exposing some external helpers/APIs which can help in testing, but are not included in the core lib.
When I think about it now, the solution I would be pleased with would include:

running the saga, alone or in context of the store, aint sure which yet
collecting effects in some organised manner, so they can be tested later with deep equality checks
custom resolution when needed, which is included in your interceptors example
some way of 'spying' on forked tasks, could be done by running saga in the context of store and actually running forked workers which cannot be done now with iterating approach

The thing I dont know how to solve for now are the endless loops inside the generators. It would be the best if we could have knowledge about them and just group yields from such a loop as some kind of endlessTask without need of knowing how many yields are inside and all the branching in it. Such endlessTask logic would become more easily tested then.
We could introduce a new effect - repeat, so the endlessTask content is already grouped in the userland for us and we can just expose ability to run it in the tests on demand with various branching logic. WDYT? It would be roughly equivalent of:
function repeat(worker, ...args) {
	const task = yield fork(function* () {
		while (true) {
			yield call(worker, ...args)
		}
	})

	return task
}

@yelouafi Looks great. A little hard for me at first to understand the function signatures as written, particularly the meaning of execBuiltin and cb, hopefully they'd get some more descriptive names or at least adequate documentation (which given what I've seen from redux-saga so far, I'm definitely not worried. A+ docs :) )

I like this! I've recently been working on a library for testing sagas using an approach similar to what @Andarist suggested above. Here's an example of what testing a saga might look like.
Given this saga:
function *complexHelper(arg) {
  yield 123;
}

function *complexSaga() {
  try {
    const number = yield select(state => state.number);
    yield put({ type: 'NUMBER_CHANGED', number: number + 1 });

    const { fruit } = yield take('FRUIT_CHOSEN');
    yield call(complexHelper, fruit);
    yield fork(complexHelper, fruit),
    yield spawn(complexHelper, fruit)

    yield "I don't care about this";
  } catch (err) {
    yield put({ type: 'UH_OH' });
  }
}

You could test it this way:
test('Complex Saga: successful', t => {
  const runner = new SagaRunner(complexSaga());
  runner.expects(select(state => state.number)).returns(42);
  runner.expects(put({ type: 'NUMBER_CHANGED', number: 43 }));
  runner.expects(take('FRUIT_CHOSEN')).returns({ fruit: 'apple' });
  runner.expects(fork(complexHelper, 'apple'));
  runner.expects(spawn(complexHelper, 'apple'));
  runner.expects(call(complexHelper, 'apple'));
  runner.run(t);
  t.end();
});

The basic idea is to create a "runner" that wraps a generator instance. You set up expectations on that runner, and can optionally specify that when the runner is yielded a specific value, it will call next with another value. This would let you define the result of a call to an API, for example. Then, you tell the runner to run your saga, which does so and then asserts things about the expectations you set up.
The expectations are order-independent, and you only have to set up expectations for things you care about testing, instead of needing to add a bunch of generator.next() calls in the middle of your tests when the implementation changes. It also couples the "return" values for with the original call, instead of forcing you to pass them to the next step in the saga.
The library still has bugs and is missing most features, but I want to get some thoughts on the approach as I expand functionality so it will be useful to the community.

What do you plan to do with endless loops like while (true)?
On Fri, 18 Nov 2016 at 16:17, Kevin Smith<EMAIL_ADDRESS>wrote:

I like this! I've recently been working on a library
https://github.com/ksmithbaylor/redux-saga-test-runner for testing
sagas using an approach similar to what @Andarist
https://github.com/Andarist suggested above. Here's
https://github.com/ksmithbaylor/redux-saga-test-runner/blob/master/tests/complexSaga.test.js
an example of what testing a saga might look like.
Given this saga:
function *complexHelper(arg) {
yield 123;
}
function *complexSaga() {
try {
const number = yield select(state => state.number);
yield put({ type: 'NUMBER_CHANGED', number: number + 1 });
const { fruit } = yield take('FRUIT_CHOSEN');
yield call(complexHelper, fruit);
yield fork(complexHelper, fruit),
yield spawn(complexHelper, fruit)

yield "I don't care about this";

} catch (err) {
yield put({ type: 'UH_OH' });
}
}
You could test it this way:
test('Complex Saga: successful', t => {
const runner = new SagaRunner(complexSaga());
runner.expects(select(state => state.number)).returns(42);
runner.expects(put({ type: 'NUMBER_CHANGED', number: 43 }));
runner.expects(take('FRUIT_CHOSEN')).returns({ fruit: 'apple' });
runner.expects(fork(complexHelper, 'apple'));
runner.expects(spawn(complexHelper, 'apple'));
runner.expects(call(complexHelper, 'apple'));
runner.run(t);
t.end();
});
The basic idea is to create a "runner" that wraps a generator instance.
You set up expectations on that runner, and can optionally specify that
when the runner is yielded a specific value, it will call next with
another value. This would let you define the result of a call to an API,
for example. Then, you tell the runner to run your saga, which does so and
then asserts things about the expectations you set up.
The expectations are order-independent, and you only have to set up
expectations for things you care about testing, instead of needing to add a
bunch of generator.next() calls in the middle of your tests when the
implementation changes. It also couples the "return" values for with the
original call, instead of forcing you to pass them to the next step in the
saga.
The library still has bugs and is missing most features, but I want to get
some thoughts on the approach as I expand functionality so it will be
useful to the community.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/yelouafi/redux-saga/issues/586#issuecomment-261556394,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJWMkpPC4JQwfj879IZOYDC3YXQIcU8wks5q_cGcgaJpZM4KW3Yi
.

That's still an open question. I was considering either allowing you to specify how many steps you wanted to allow, or specify a "break point" where it would stop calling next after seeing a particular effect.

That being said I dont yet what to think about those interceptors. First of all - would be nice to find use case for them outside of testings, cause I generally dont like adding the code just for testings purposes,

@Andarist I think a more perspective pf the proposal could be someting similar to Aspect Oriented Programming in the sense it can allow isolating cross cutting concerns (logging, persistence ...). Although didn't think in detail how this could be benefited in the context of a React/Redux application

Also Error handling itself could be seen as a cross cutting Error

Could it also be done in a per-saga basis? I'd like to bind some specific effects (take, put and select) to an instance ID for composition (e.g. CounterList uses Counter). Version 4 of the library redux-elm already solves it in a nice way for components, action creators and reducers, but we still need to inject these custom bound effects into our original sagas.

@Andarist I had something in mind but, ideally, I should compose the sagas by passing down actions and selectors as arguments. Intercepting effects outside a test environment doesn't look right.

Still, composing could be achieved in various ways I guess - would be cool to see what you have in mind, so I could evaluate if its suitable for implementing

You can keep an eye on the v1 progress. You can also notice that Im being active lately and committing to the master few times a week.
That said there is still some work (not really any hard work, but it is still time-consuming) left to be done. I plan to give my attention to this particular issue soon, it doesn't mean that I will release v1 as soon as it's done, I can publish some alpha version though if you want. You can checkout latest commits, there was no really ground breaking changes, and there wont be, so I would say that using what's on the master (its tested after all) shouldn't really cause any real problems. I wouldn't hesitate upgrading in my own projects, just have no time for this atm as pushing v1 forward is just more important. Let me know if you are interested in becoming the first alpha tester ;)

Cool, I'll let you know asap when that feature is ready then. I will also start to sum up recent changes so you won't get blindsided.

Version 4 of the library redux-elm already solves it in a nice way for components, action creators and reducers, but we still need to inject these custom bound effects into our original sagas.

@eliseumds isn't it only a problem of syncing appropriately (preferably automatically) your sagas to instances? I guess enhanceComponent from redux-elm is doing this for components, you could probably have additional wrapper or have this one parametrized with saga - and just proxy or something yielded effects to inject instance-based parameter to ur take/put/select.
Im not familiar with redux-elm though so I don't quite know if that's completely feasible. It seems it still needs quite a lot of boilerplate in the List~ view to generate selectors etc manually.

This feature (in slightly different form - as effectMiddlewares) got implemented by @eloytoro and it got merged in. Gonna do a beta v1 release in following hour. @frankandrobot I'd appreciate testing and any feedback you can give on this.
How it might be used can be checked here


sst: add checks for nil pointer args

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (586e1ac) 78.52% compared to head (0e0028c) 78.52%.

:exclamation: Current head 0e0028c differs from pull request most recent head 7ac12c9. Consider uploading reports for the commit 7ac12c9 to get more accurate results

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #119   +/-   ##
=======================================
  Coverage   78.52%   78.52%
=======================================
  Files          12       12
  Lines        1490     1490
=======================================
  Hits         1170     1170
  Misses        213      213
  Partials      107      107

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


EarlGrey 2.0 - OCMock compatibility

Sorry for creating a new issue, i've been asking at other open issues but not getting any response
is it possible to use OCMock or mocking objects in EarlGrey 2.0 ? i found a GREY_STUB_CLASS_IN_APP_MAIN_QUEUE macro but it doesn't seem to stub anything. Please add me to the slack channel / google group if it's preferred to discuss there
Thank you 🙇♂

You can stub OCMock objects with GREY_REMOTE_CLASS_IN_APP as well. Have you tried it?

@tirodkar i tried to use GREY_REMOTE_CLASS_IN_APP in helper bundle where i can access my class thanks to eDO but the macro returns nil so i can't mock it. i read the docs that mentioned "The class interface must be exposed to the test
process for doing this." does this mean i need to build the class in my test target ?

@tirodkar i tried to use GREY_REMOTE_CLASS_IN_APP in helper bundle where i can access my class thanks to eDO but the macro returns nil so i can't mock it. i read the docs that mentioned "The class interface must be exposed to the test
process for doing this." does this mean i need to build the class in my test target ?


Travis test 1.8 and 1.9

fixes #33

LGTM, will pull it after goveralls is fixed, i'm quite busy will take a week i guess

Sry for the long wait, travis should be up to date now #43

result is fine, no worries :wink:


[pipeline] autorest upgrade to 6.2.7

Fix pipeline failure for automation: https://github.com/Azure/azure-rest-api-specs/pull/21128

https://github.com/Azure/azure-sdk-for-python/pull/27526


Internal error on sign declaration reqiest

Response:
{
  "meta": {
    "url": "http://dev.ehealth.world/api/declaration_requests/639a0b51-e9cf-4f6b-b70f-9b8e3bdbee4e/actions/sign",
    "type": "object",
    "request_id": "uq7kfq1n06gookt48eq63akchr036ggk",
    "code": 500
  },
  "error": {
    "type": "internal_error"
  }
}

Log
{"timestamp":"2017-08-09T11:17:35.399Z","sourceLocation":{"line":19,"function":"Elixir.EHealth.API.Helpers.MicroserviceCallLog.log/5","file":"/opt/app/lib/ehealth/api/helpers/microservice_call_log.ex"},"severity":"INFO","metadata":{"request_id":"uq7kfq1n06gookt48eq63akchr036ggk","application":"ehealth"},"jsonPayload":{"serviceContext":{"version":[48,46,52,46,56,54],"service":"ehealth"},"message":"Calling POST on http://api-svc.ael/media_content_storage_secrets with body=%{\"secret\" => %{\"action\" => \"PUT\", \"bucket\" => \"declaration-requests-dev\", \"resource_id\" => \"639a0b51-e9cf-4f6b-b70f-9b8e3bdbee4e\", \"resource_name\" => \"signed_content\"}} and headers=[{\"x-consumer-id\", \"a0c7e078-cb88-4f18-bb4e-698c479bb0a3\"}, {\"x-consumer-scope\", \"employee:read employee_request:approve employee_request:read employee_request:reject legal_entity:read declaration:read declaration_request:sign declaration_request:approve division:read declaration_request:write declaration_request:read otp:write otp:read\"}, {\"x-consumer-metadata\", \"{\\\"scope\\\":\\\"employee:read employee_request:approve employee_request:read employee_request:reject legal_entity:read declaration:read declaration_request:sign declaration_request:approve division:read declaration_request:write declaration_request:read otp:write otp:read\\\",\\\"refresh_token\\\":\\\"NGlQQTQ2K1h5bUVLTC85bmFrdEpvUT09\\\",\\\"redirect_uri\\\":\\\"http://example2.com\\\",\\\"grant_type\\\":\\\"authorization_code\\\",\\\"client_id\\\":\\\"9c81824b-bc13-4d07-bc76-b069e2a2876b\\\"}\"}, {\"x-request-id\", \"uq7kfq1n06gookt48eq63akchr036ggk\"}, {\"cache-control\", \"no-cache\"}, {\"postman-token\", \"da0eb0cc-adb0-45ad-b02d-5a9c036ee248\"}, {\"authorization\", \"Bearer UDBQYVE1eUlIQlN6UzVEbTl3WW02dz09\"}, {\"user-agent\", \"PostmanRuntime/6.1.6\"}, {\"accept\", \"*/*\"}, {\"host\", \"dev.ehealth.world\"}, {\"accept-encoding\", \"gzip, deflate\"}, {\"connection\", \"keep-alive\"}, {\"x-forwarded-for\", \"<IP_ADDRESS>\"}, {\"x-forwarded-proto\", \"http\"}, {\"content-type\", \"application/json\"}, {\"content-length\", \"405584\"}]."}}
{"timestamp":"2017-08-09T11:17:35.410Z","sourceLocation":{"line":61,"function":"Elixir.EHealth.API.MediaStorage.put_signed_content/2","file":"/opt/app/lib/ehealth/api/media_storage.ex"},"severity":"ERROR","metadata":{"request_id":"uq7kfq1n06gookt48eq63akchr036ggk","application":"ehealth"},"jsonPayload":{"serviceContext":{"version":[48,46,52,46,56,54],"service":"ehealth"},"message":"Cannot create signed url. Response: {:error, %{\"error\" => %{\"type\" => \"internal_error\"}, \"meta\" => %{\"code\" => 500, \"request_id\" => \"uq7kfq1n06gookt48eq63akchr036ggk\", \"type\" => \"object\", \"url\" => \"http://dev.ehealth.world/media_content_storage_secrets\"}}}"}}
{"timestamp":"2017-08-09T11:17:35.410Z","sourceLocation":{"line":34,"function":"Elixir.Plug.Logger.call/2","file":"/opt/app/deps/plug/lib/plug/logger.ex"},"severity":"INFO","metadata":{"request_id":"uq7kfq1n06gookt48eq63akchr036ggk","application":"plug"},"jsonPayload":{"serviceContext":{"version":[49,46,51,46,53],"service":"plug"},"message":"Sent 500 in 537ms"}}

Ael was offline due migration to ehealth.charts


[ini] implement save function

Support model section save (#1534)
Support inbound connection save
Support optimizer section save
Support dataset section save
Add layer properties to make it savable (@lhs8928)

:octocat: cibot: Thank you for posting issue #1536. The person in charge will reply soon.

Resolved


How to get data in other langauges (e.g., Chinese or Japanese)?

Thanks for the great work! I'm wondering where to modify the code to fetch the data in other languages.
Could you give me some pointers? Thanks!

Ah sorry, the script in main branch have stopped working from last 5 days. Because the site structure changed that doesnot allow for scraping from js chunk files anymore.
You can use raw_data.py from dev branch.
It is a bit documented.
It is still work in progress because I have not typed the models yet. Nonetheless, it will fetch all data and save it in json, as far as I have tried.
the O_VALUE in constants.py sometimes changes. Its working for now, so you would have to look in site main js file.
You can dm me on discord if you need any help. reko#8221

Thanks for the quick response! And really appreciate the comprehensive explanation.
I'll give the dev branch a try. And I'm glad to connect through discord : ) (I'm making discord bots for HSR.)


add parameter type support to getClient

I kept getting getClient Expected 0 arguments, but got ... because makeClient has no parameters

That is kinda intentional - if I may ask, what are you passing in there?

@phryneas i pass fetchOptions:{ cache: ...} for next as well as fetch headers.
I just remembered that i can use context for setting such things. the only difference is they have to be provided to every query/mutation on page while getClient  passes them directly to the HttpLink
If you want to keep it without parameters you can close the PR.
Thanks 🙌

Yeah, you definitely should avoid doing it this way.
If you pass different arguments into getClient for two calls, you will get two different client instances.
The purpose of getClient is to create a new Apollo Client instance for every new request, but to always return the same instance within that request.
As soon as you call it with potentially different arguments, that functionality stops working.
=> Yeah, please use the per-request context for this :)
I'm going to close this issue. Have a great day!


require extension-safe api for RxMoya and ReactiveMoya

augmenting #1416 to include ReactiveMoya target as well

Codecov Report

Merging #1417 into master will increase coverage by 2.06%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1417      +/-   ##
==========================================
+ Coverage   86.35%   88.41%   +2.06%
==========================================
  Files          24        5      -19
  Lines         784      164     -620
==========================================
- Hits          677      145     -532
+ Misses        107       19      -88

Impacted Files
Coverage Δ

Sources/Moya/MultipartFormData.swift

Sources/Moya/MoyaProvider+Internal.swift

Sources/Moya/Plugins/NetworkLoggerPlugin.swift

Sources/Moya/Plugins/CredentialsPlugin.swift

Sources/Moya/URL+Moya.swift

Sources/Moya/MoyaProvider.swift

Sources/Moya/TargetType.swift

Sources/Moya/Endpoint.swift

Sources/Moya/Moya+Alamofire.swift

Sources/Moya/MultiTarget.swift

... and 9 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4935fe4...5ede358. Read the comment docs.

Yup, can you add a Changelog entry for this one, @spookyvision? Other than that it looks great.
About the Changelog update - you should rebase master before you add this one, as we already have one fix in it. This entry should be under Fixed column, as we enabled this flag before, but not for each target for both debug and release.

First time doing this, hope I did things right :)

SwiftLint found issues
Warnings

File
Line
Reason

EndpointSpec.swift
274
Colons should be next to the identifier when specifying a type and next to the key in dictionary literals.

EndpointSpec.swift
275
Colons should be next to the identifier when specifying a type and next to the key in dictionary literals.

  Generated by :no_entry_sign: Danger

@spookyvision it's a little worrying to see 25 commits in this PR. Any idea why your PR is pulling in so many other commits?

@AndrewSB I rebased onto master as requested by @sunshinejr - my commits are actually far less. Should I start from scratch and cherrypick them?

I just did a roundtrip swap on the target branch of this PR and it seemed to remove a lot of the excess commits in this PR. I don't know if we want to squash the commits further but the changes LGTM

I've resolved conflicts, it seems ready to merge! Thanks @spookyvision! 🎉

Thanks a lot for contributing to Moya! I've invited you to join the Moya GitHub organization – no pressure to accept! If you'd like more information on what that means, check out our contributor guidelines and feel free to reach out with any questions.


[Fix upstream] [$2000] Settings - Side menu blinks if close it by swiping to the right

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Seems like this is related to https://github.com/react-navigation/react-navigation/issues/11309 lets try to fix this upstream
Action Performed:

Open http://staging.new.expensify.com
Tap on Profile icon / Search icon
Swipe Settings menu / LHN to the right

Expected Result:
Side menu closes smoothly after swiping it to the right
Actual Result:
Side menu blinks before being closed if swipe it to the right
Workaround:
Unknown
Platforms:

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

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[x] iOS / Safari
[ ] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: <IP_ADDRESS>
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/78819774/67cdf287-9976-452a-8fb2-58b61129f92f
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01ca84ca563738697d
Upwork Job ID:<PHONE_NUMBER>523150848
Last Price Increase: 2023-06-22

Hm I can't reproduce this one on my iPhone.
I am rapidly taping the 🔍  and then < to try and trigger the laggy behavior.

OH WAIT, you said to "swipe to the right" on the top nav to go back to LHN.
That I can easily reproduce and it's buggy. I see! Adding external label let's fix it.

Wanted to do a Proposal but after reading this documentation it seems like a specific "React Navigation" implementation, in iOS it does seem like the animation event is triggered twice, one by swipe and one by the pop event. @WoLewicki @mountiny  maybe a work for SWMantion? I don't see any native code in Expensify that might alter this.
Only idea: Listen to gestureEnd and avoid double animation but sounds a little forced for something that seems related to the library

cc @adamgrzybowski probably something wrong with how react-navigation works under the hood.

@daordonez11 @lanitochka17 would you be able to try and reproduce it in a simple react native app with a stack with 2 screens on mobile web?

@lanitochka17 probably wont be able to help with this one
Would be great to see if this issue is react-navigation related

@mountiny Hello, still reproducible, in search dialog  a lot of old chats, but in Split bill - no. Checked with<EMAIL_ADDRESS>“problematic” account
https://github.com/Expensify/App/assets/78819774/41dfeea1-d639-413e-9960-640b100d0712

@lanitochka17 I am not sure but the video seems like a different issue.

@mountly sorry for the confusion

It looks like this is the same issue that we have https://github.com/react-navigation/react-navigation/issues/11309

is this issue still open for proposals?

@adamgrzybowski it does seem like the same issue! @mountiny should I  do the proposal in the library issue or directly here? Let me know if it is still external or something por SW mansion

I am currently investigating this issue.

SWM will have a look at this

Still working on this

Assigning Adam so it's clear progress is being made

Still working on this. Found some clues 🕵

Adam is focusing on other higehr priority issue for navigation and will come back to this after the unmount issue is solved. Adding weekly

Upstream fix is being reviewed

@adamgrzybowski could you link the upstream fix here?

Making this will as we will have to wait for the upstream fix

I haven't created a fix for that because I haven't found a fully working solution for this problem. Events on the mobile iOS are broken while this gesture takes place.
I switched to the issue with resizing because of the priority but now I have a few more ideas to try to resolve this issue

Seems like no speed bonus is due here!
Only payment due is $2000 to @fedirjh via upwork. Invited you to the upwork job https://www.upwork.com/jobs/~01ca84ca563738697d

Paid!


Implement new POTel span processor

only acts on on_end instead of both on_start/on_end as before
store children spans in a dict mapping span_id -> children
new dict only stores otel span objects and no sentry transaction/span objects so we save a bit of useless memory allocation
I'm not using our current Transaction/Span classes at all to build the event because when we add our APIs later, we'll need to rip these out and we also avoid having to deal with the instrumenter problem
if we get a root span (without parent), we recursively walk the dict and find the children and package up the transaction event and send it

I didn't do it like JS because I think this way is better
they group an array of finished_spans every time a root span ends and I think this uses more cpu than what I did
and the dict like I used it doesn't take more space than the array either

if we get a span with a parent we just update the dict to find the span later
moved the common is_sentry_span logic to utils

tested simple nested trace
import sentry_sdk
from opentelemetry import trace
from time import sleep

sentry_sdk.init(
    debug=True,
    traces_sample_rate=1.0,
    _experiments={"otel_powered_performance": True},
)

tracer = trace.get_tracer(__name__)

with tracer.start_as_current_span("request"):
    sleep(0.1)
    with tracer.start_as_current_span("db"):
        sleep(0.5)
        with tracer.start_as_current_span("redis"):
            sleep(0.2)
    with tracer.start_as_current_span("http"):
        sleep(1)

@sentrivana moved op/description/status logic to utils, but status mapping will be done separately. Maybe @szokeasaurusrex can look into making this logic as similar to JS as possible, but for now this is good enough for this PR.
https://github.com/getsentry/sentry-javascript/blob/master/packages/opentelemetry/src/utils/mapStatus.ts
https://github.com/getsentry/sentry-javascript/blob/master/packages/opentelemetry/src/utils/parseSpanDescription.ts


Examples Key has expired.

Steps to reproduce

Click the example link on the Github page.

Stack trace
# Maps JavaScript API error: ExpiredKeyMapError

@webdagger Thank you for opening this issue. 🙏
Please check out these other resources that might be applicable:

Support Console - If you have a support contract.
Discord - chat with other developers
StackOverflow - use the google-maps tag
Google Maps Platform issue trackers

This is an automated message, feel free to ignore.

closed in https://github.com/googlemaps/js-markerwithlabel/commit/b0ae1a34afb9ab5ef4c4a4c723acb271ed3259c2


Nuget v2.0.2 - attestation option "direct" - TPM class

Hi,
We have noticed an issue.
When using the attestation option "direct" then clientDataJson appears to have 118 bytes when the tpm/ pubarea class expects 84. This throws an exception "throw new Fido2VerificationException("Leftover bytes decoding pubArea");" in TPM.cs line 634.
We were able to replicate the issue on your codebase changing attestation_type variable in custom.register.js to "direct".
We've temporarily changed our codebase to use "none" until fixed. Is there an alternative?
Please let me know if you need further details.
Thanks
Himesh

I don't recall seeing anything like this before, do you have a sample clientDataJson that exhibits this behavior?

Hi Aseigler,
Sorry for the late response. So decode of array below:-
'{"type":"webauthn.create","challenge":"ztuB2Bt0h_t4sPpMraDctA","origin":"https://localhost:41111","crossOrigin":false,"other_keys_can_be_added_here":"do not compare clientDataJSON against a template. See https://goo.gl/yabPex"}'
Thanks
Himesh

I suspect this is going to be due to TPM attestations quietly being made with ES256 instead of RS256, which got fixed here.  We need to get a new build cut to get this on Nuget, I don't think we have one with this in it.

No, the last release (3.0) doesn't have the changes as far as I can see. Would be nice to get the fix out.

@aseigler @m-gug 3.0.1 is available :shipit:
https://www.nuget.org/packages/Fido2/3.0.1
https://github.com/passwordless-lib/fido2-net-lib/releases/tag/v3.0.1

Please let us know ASAP if v3.0.1 does not fix the problem.

Thanks for the quick release, the problem is solved, the registration is working again. :raised_hands:
However, another problem has emerged that did not exist before. On .Net 6, the System.Json.Text serializer now seems to choke on the return value in the MakeAssertion function.
It throws this exception:
"Serialization and deserialization of 'System.IntPtr' instances are not supported. Path: $.Result.AttestationCertificate.Handle."
The problem can also be recreated in your current master branch if you register a new credential in the demo app under Custom.
As a workaround I am not returning the complete result of MakeNewCredentialAsync(..), but returning a new CredentialMakeResult only with status="ok".
The frontend doesn't need the complete result, as far as I understand it, does it?

Thanks for the report!

The frontend doesn't need the complete result, as far as I understand it, does it?
@m-gug The frontend is not interested in the result once the credential is created, only the CredentialCreateOptions in the first step of the dance.


Reinforce Java serialization security

And create a Serializer interface with implementations (Java, Kryo) instead of the helpers with static methods.

Related discussion: https://groups.google.com/forum/?fromgroups#!topic/pac4j-users/muVwe0qh0xc


Automate local linking of packages

This automates the linking step a bit to make local development a bit easier. As I'm going over the package sources to update some of the TypeScript types, I found it easy to get them linked to the incorrect versions. For example, when updating a type inside the src/ in the client package, those changes won't show up in the React package, unless I would:

Rebuild the client package
Link them with NPM

This script automates that process.
To use it, simply cd into one of the secondary package directories, and run ../../scripts/link.sh. (If you use direnv and have the set up from #128, you can simply run link.sh without the ../../scripts/ prefix from anywhere—can recommend!)
What this script will do:

Checks to see if the client package needs to be rebuilt. If determines that by looking at the file modification timestamps in client/src and client/lib. All files in lib/ must be older than any file in src/. If not, it rebuilds things.
Checks to see if the current package has been linked locally correctly. If not, it will link it up.

Basically, this makes link.sh an idempotent script that you can run at any time and it will check your local setup and fix it if necessary.
Future Work
I would love to generalize this script in another pass, to make it work with any of our local packages, meaning you could run this inside any example directory as well, and it would check and link all Liveblocks packages that that project needs.

The tricky part is the peer dependencies and duplicated React packages: https://github.com/liveblocks/liveblocks/blob/main/examples/nextjs-whiteboard/scripts/link-liveblocks.sh

Yeah, I would love to automate that process by autodetecting what the "current" project needs are from looking at its package.json file, and doing The Right Thing™ automatically. That way, we wouldn't have to copy this script into each project either - you just cd into a project, run the link script, and you're good.
Will see if I can add that in before merging this PR in. Would be nice to have a single way to do it, rather than to have a mix of approaches between packages and projects.

It now works reliably with the CI build, too! 🙌
I've gone ahead and updated the instructions here too: https://www.notion.so/liveblocks/How-to-074d3dfa5b944adb986fe176572d6887#0e1c03df0bee49e78d62dedfa4bf9856


Add settings screen

This is an update to https://github.com/tripleblindmarket/private-kit/pull/233 with the latest changes from #develop merged in. I didn't make any changes beyond resolving merge issues and reverting a few style changes unrelated to the PR. Screenshots below:

cc @penrods

I started similar work here:
https://github.com/StartupSam/private-kit/pull/3
The history is cleaner there, but.. I think this should be going into safe-paths branch, not develop.


Only show "Running hook" if one exists

Currently we show a LOT of headers in the 3.x agent. This removes "Running hook" headers if the header doesn't exist.

😻


CampaignStatistics  are wrong using email as customValue

Reading the v3 maijet API reference for the campaginstatistics method, it seems that properties marked as unique can be used to fetch campaignstatistics.
http://dev.mailjet.com/email-api/v3/campaignstatistics/
Apparently, an email is a contact unique property :
http://dev.mailjet.com/email-api/v3/contact/
When I use an email as a customValue :
$customvalue =<EMAIL_ADDRESS>$params = array(
"method" => "VIEW",
"unique" => $customvalue
);
$this -> m_oMailJet -> campaignstatistics($params);
I get :
404
Status
stdClass Object
(
[ErrorInfo] =>
[ErrorMessage] => Object not found
[StatusCode] => 404
)

Hey @AkobmanD :airplane:
We just released a new PHP API wrapper.
It is now more PHP-ish (including namespace, PSR-0 compliance, and globally a better architecture).
All it requires is PHP 5.4
In addition to our API Guides, we would be happy to help you get started with it.
Guillaume, from Mailjet!


CyberDogAPP Where is the source code repository?

Brief modification description
I didn't find the CyberDogAPP source code to compile and make some own version

manager of the team refuses to give it out.
sadly killing his own product

Thank you for the reply.
So it's not opensource project

@vitorcalvi sadly they sold us on this, but are not honoring the commitment to open source.
I understand the manager<EMAIL_ADDRESS>does not care. Email him and ask why? Maybe if enough of us mail him he will care?
Notice how we have no Gazebo support either? It is a joke.

We have to join and kindly ask<EMAIL_ADDRESS>to really open the source code to who bought the cyberdog as an opensource product.
I will send now kindlying ask about it.
Let's do the same too


Update RPMI Message Protocol chapter

This PR contains improvements to message protocol chapter.

@lftan I suggest getting this PR merged first before others since it changes the message format which will affect all service groups


Cannot freeze this Storyboard timeline tree for use across thread

Gets "Cannot freeze this Storyboard timeline tree for use across". This problem/exception occurs in version 1.1.

Struggling to repro this.

Should be fixed now, can't point to a commit.


Migration from in-tree to CSI drivers missing explanation if existing data can be re-attached or must be copied to new PV-s

This migration guide promises no data loss and this is correct as the guide clearly presents how to change reclaimPolicy from Delete to Retain for existing volumes (PV-s).
Then, the guide explains how to 4. Create a new PV using the new StorageClass and then the new PV is claimed as volume by re-created POD-s.
But, this guide does not explain how to re-attach the already existing (old) PV-s to re-created pods.
List of I think important questions that the migration guide is not answering:

Why the new PV-s are created?
What about existing old PV-s?
Is it possible to re-attach existing PV-s to re-created POD-s after switching from in-tree to CSI drivers?
Is user supposed to perform copy of data from old retained PV-s to newly created PV-s?

I have upgraded my AKS cluster to Kubernetes 1.25.5 and during migration to the new CSI drivers, I noticed that re-created POD-s have re-attached existing PV/PVC-s, but new PV-s have been created and POD-s attached to new ones:
$ kubectl get pv
pvc-56fac82e-c516-4bbb-b539-b0633cabf262   64Gi   RWX   Delete   Bound      default/demo-myapp-pvc-azurefile             azurefile-csi   39m
pvc-8e0c6dcf-e2a5-48b1-bacb-32e8fb31974c   10Gi   RWX   Delete   Bound      default/demo-myapp-secondary-pvc-azurefile   azurefile-csi   39m
pvc-163fa4f5-0045-4018-a93a-8c5f3c8bc819   10Gi   RWX   Retain   Released   default/demo-myapp-secondary-pvc-azurefile   azurefile-csi   162d
pvc-73a65645-26ad-41eb-bb67-70b0c4a120d3   64Gi   RWX   Retain   Released   default/demo-myapp-pvc-azurefile             azurefile-csi   162d

$ kubectl get pvc
demo-myapp-pvc-azurefile             Bound   pvc-56fac82e-c516-4bbb-b539-b0633cabf262   64Gi   RWX   azurefile-csi   39m
demo-myapp-secondary-pvc-azurefile   Bound   pvc-8e0c6dcf-e2a5-48b1-bacb-32e8fb31974c   10Gi   RWX   azurefile-csi   39m

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

ID: be462320-52fc-31fa-43e2-5e5dcb172edc
Version Independent ID: d84447c0-1b17-1150-32ad-327047958a44
Content: Migrate from in-tree storage class to CSI drivers on Azure Kubernetes Service (AKS) - Azure Kubernetes Service
Content Source: articles/aks/csi-migrate-in-tree-volumes.md
Service: azure-kubernetes-service
GitHub Login: @MGoedtel
Microsoft Alias: magoedte

@mloskot
Thanks for your feedback! We will investigate and update as appropriate.

@Naveenommi-MSFT @MGoedtel Any update on this? Document is still not updated, nor there was an update here. To be honest, in AWS EKS similar migration is done in the backend by the addon itself, no action nor changes needed from users (besides installing addon prior upgrade), so here at least documentation should be done right.

@andyzhangx Thank you! Your answer should be turned into the docs update, IMHO.

that's not necessary since new PV references the same file share

This is a subtle Azure Storage specific detail that I had missed and I'm confident many users may miss it as well: lifetime of PVC vs lifetime of PV vs lifetime of underlying cloud-based storage.

We've addressed the feedback in a PR that was just merged this morning, and as a result I'm going to proceed with closing this issue. Thanks.
#please-close


hive外表（sqoop导入，snappy压缩）无法查询

Steps to reproduce the behavior (Required)
创建了hive外部表或者hive catalog ，使用sr查询时报无法解析snappy压缩类型
Expected behavior (Required)
query failed: Unknown compress type: 3:file = hdfs://nameservice1/user/hive/warehouse/ods.db/ods_biz_outline_urge_staff/dt=2022-10-27/part-m-00002.snappy
Real behavior (Required)

![image](https://user-images.githubusercontent.com/108266979/203913360-7850792c-51bc-423f-9e57-3af519a684b6.png)
StarRocks version (Required)

You can get the StarRocks version by executing SQL select current_version()
-2.4.0 c0fa2bb

Does StarRocks support read hive data with snappy compression?


Provide an api to upload images

We should implement that with Qiniu storage service. Moreover, it would be better if we can edit the images with Meitu api.

Won't fix.


Name suggestions

How about "Schwa"? https://en.wikipedia.org/wiki/Schwa
Never been used before, and it has a cute symbol

Thanks for the suggestion! I like that it's short, but I think it might be a little too "exotic". Probably because of the four adjacent consonants. In my opinion, the name should be more familiar to English speakers, so that e.g. you know how to spell it when you hear it, etc.

Closing this for now since this isn't a current priority.


Question: Should "A conflict exists with inherited definition X in class Y" be a warning?

Hi Josh,
When hiding a base method by reducing its scope generates an error in the editor but doesn't fail the compilation.
Should this be therefore considered as a warning?

I wasn't aware that you could hide a method by reducing its scope. I'll need to compare the various AS3 compilers to see if that's standard, or just a quirk of one of them.

But all errors in vscode-as3mxml come from the Royale compiler (which was a fork of the Adobe AIR compiler, sometimes called ASC 2.0, donated to Apache). If it needs to change, it needs to change there.

Finally got around to trying out various compilers.

Royale reports the error mentioned in this issue description.

ASC 2.0 (AIR SDK) compiles the code without any errors or warnings.

Flex reports the following errors:
ClassA.as(24): col: 19 Error: Incompatible override.

        private function methodA():void {}
                         ^

ClassA.as(24): col: 19 Error: Overriding a function that is not marked for override.

        private function methodA():void {}
                         ^

I tried placing ClassA and ClassC into separate files, so that I could instantiate both and call methodA() on both to see what the runtime behavior is when ASC 2.0 compiles successfully.
package com.example
{
	public class ClassA
	{
		public function ClassA()
		{
		}

		public function methodA():void
		{
			trace("ClassA.methodA");
		}
	}
}

package com.example
{
	public class ClassC extends ClassA
	{
		public function ClassC()
		{
		}

		private function methodA():void
		{
			trace("ClassC.methodA");
		}
	}
}

var a:ClassA = new ClassA();
a.methodA();

var c:ClassC = new ClassC();
c.methodA();

The debug output is:
ClassA.methodA
ClassA.methodA

Since thus code compiles successfully too, it means that ASC 2.0 is not reducing the scope of methodA from public to private. The original public methodA from ClassA is called for ClassC.
It is, in fact, possible to call the private version of methodA(), but it must happen inside ClassC.
package com.example
{
	public class ClassC extends ClassA
	{
		public function ClassC()
		{
			methodA();
		}

		private function methodA():void
		{
			trace("ClassC.methodA");
		}
	}
}

Keeping all of the other code the same, including calling the public version of methodA on both classes, the debug output becomes:
ClassA.methodA
ClassC.methodA
ClassA.methodA

You can call the public methodA inside ClassC too. You just need to use public::methodA(), with the public:: namespace modifier.
So, in ASC 2.0, the private methodA and the public methodA are actually considered separate methods, even though they share the same name. Which one gets called depends on the context.
I wouldn't plan on the Royale compiler (which provides code intelligence for vscode-as3mxml) being updated to support this behavior, even optionally.

Thanks a lot for having taken the time to dig into this compilation nightmare 😬 ...and sorry for having pushed you in there 😅
It indeed makes no sense to "fixed" that in such context.


Using the alert message on Admin LTE

Hi, I am new in developing ASP.net with bootstrap and Admin LTE. I am trying to work with the alert but I am not able to solve the issue.
I placer the html code as follows.

×
Info!
   Data is Saved

I want the alert box to be hidden, and display when the information is saved with a code behind.
Protected Sub BtnGrabar_Click(sender As Object, e As EventArgs) Handles BtnGrabar.Click
Tabla = "Terceros"
Campos = "(Identificacion, Nombre, Direccion, Ciudad, Telefono1, Email)"
Camposfrm = "('" + TxtCodigo.Text + "','" + TxtNombre.Text + "','" + TxtDireccion.Text + "','" + TxtCiudad.Text + "','" + TxtTelefono.Text + "','" + TxTEmail.Text + "')"
Consulta = "Identificacion='" + TxtCodigo.Text + "'"
Try
conexion.ValidarExiste(Tabla, Consulta)
If conexion.ds.Tables(0).Rows.Count = 0 Then
conexion.Insertar(Tabla, Campos, Camposfrm)
            "display the alert with a text (Information is saved)"
        Else
             "display the alert with a text (Information is not saved)"

        End If
    Catch ex As Exception
    End Try
End Sub

Thanks for your help.
Celorza

I think you need to improve the issue presentation since it isn't clear. HTML code can't be seen correctly.
The best option here is to use a javascript function to call ajax, use a webmethod on your page and based on the respond show the box.
By the way your issue is more about how to use bootstrap than about AdminTemplate so i recommend to close the incident.

Hello,
Since I am not an ASP.NET developer, I am afraid I can't be of much help. I would suggest trying StackOverflow to post this issue since you might find a wider variety of developers there.
Thanks!


Need an option to allow the user to choose their own new password

When a user generates a password reset email and then follows the link back to the site, the user should be able to reset their password there.  Emailing the random password back to the user in plain text is not only inconvenient, it's a security risk.

I agree. I don't have time to do this now, but would accept a PR. :)


What does Apple universal mean?

What does isMobile.apple.universal mean?
Is that supposed to be a mobile device? 🤔
https://github.com/kaimallea/isMobile/blob/05abb5552d9887e3033762a6c92dc7cfeccb0b8b/src/isMobile.ts#L4
Thank you

This is from https://github.com/kaimallea/isMobile/pull/116. I don't remember if I did my due diligence back in 2020, and I can't find any real-world examples of this string. I'll be removing it in the next release.


Fix error when no TERM environment variable

Fixes #13

Thanks for fixing ❤

Thank you for the quick response! 💚
I'm looking forward to this fix making its way to boxen and throughout the ecosystem 👍


abuild: fix build

abuild: fix build
Errors as:

find: unrecognized: -printf

Log: https://termbin.com/j3w1
Builds with gnu find.
I don't know how to fix this with busybox find. (Tricky?)
Would this be acceptable? (Question!)
CC @onny @jopejoe1

Hydra build: https://hydra.nixos.org/build/262910068

Result of nixpkgs-review pr 322288 run on x86_64-linux 1

1 package built:

abuild

Thank you!


I think the XXX_ field is real bad idea,what happen if i remove them from the code

I'm using the message in the cache and flush them into file/db at some time. it's small in memory and fast when write files.
But not any more after the XXX_ fields were put in generated structs.
message SmallDecimal {
    bool neg = 1;
    uint64 value = 2;
    int32 exp = 3;
}

message Order {
    uint64 orderId = 1;
    SmallDecimal amount = 2;
    SmallDecimal price = 3;
    uint64 timestamp = 4;
}

type NoXXXSmallDecimal struct {
	neg   bool
	value uint64
	exp   int32
}

type NoXXXOrder struct {
	orderId   uint64
	amount    *NoXXXSmallDecimal
	price     *NoXXXSmallDecimal
	timestamp uint64
}

func main() {
	fmt.Println("Sizeof SmallDecimal", unsafe.Sizeof(SmallDecimal{}))
	fmt.Println("Sizeof Order", unsafe.Sizeof(Order{}))

	fmt.Println("Sizeof NoXXXSmallDecimal", unsafe.Sizeof(NoXXXSmallDecimal{}))
	fmt.Println("Sizeof NoXXXOrder", unsafe.Sizeof(NoXXXOrder{}))
}

I have do a lot of things to reduce the copy of memory and the cost of memory.
Sizeof SmallDecimal 56
Sizeof Order 64
Sizeof NoXXXSmallDecimal 24
Sizeof NoXXXOrder 32

What it would happen  if i remove the XXX_* field by comment generateInternalStructFields in proto-gen-go?

The XXX_unrecognized fields are to support unknown fields. If you're using proto3, they were a proto language change added by https://github.com/protocolbuffers/protobuf/issues/272.
I filed two other issues to address the root problem you are hitting: #857, #858


Sketch Page - Custom Pencil cursor instead of crosshair

Issue
Currently, the cursor for the canvas on the Sketch Page is a crosshair, which is not really related to drawing. A custom css cursor like a pencil, might look more appropriate.
Link to Cursor demo
https://custom-cursor.com/en/collection/life-style/pencil
If you like this idea, I would love to add a custom pencil cursor exactly like the demo one

Assigned for 2 days


(WIP) Updates to the dev environment for working with modules

The purpose of this branch is to migrate our development tooling so that we can work with ES modules directly.
Ignore the first commit ("Transformed").  The changes in this commit are generated by running npm run transform.  I'll be rebasing this branch on master frequently and reworking this first commit based on changes to the transform script.  The focus of this branch is the commits on top of that first commit.
Things that need to be working:

[x] a script to build/serve examples in development mode (npm run serve-examples)
[x] a script to build examples for production (npm run build-examples)
[ ] a script that runs the tests
[ ] a script that builds the docs
[ ] a script that builds with the Closure Compiler
[ ] an equivalent of make ci for Travis

Assorted blocking TODOs:

[ ] fix test-extensions.js to avoid instanceof checks (see #7182);
[ ] fix bin/pyglslunit.py and shader templates so they work with the "one provide per module" rule (see #7191)

For people interested in experimenting with ES Modules and the Closure Compiler, the key is setting module_resolution: 'NODE'.  Here is an example build script that you can start with: https://github.com/openlayers/closure-es-modules/blob/master/build.js

I created #7191 to fix the provide/require structure for the autogenerated shader files.

After 4.6 is out, I'll create a new branch with this work.  This will transform our sources to ES modules and give us working examples and tests.  After that, we can continue working on the rest of the tooling for the docs and the Closure Compiler.

Closing this in favor of #7570.  The remaining tasks above will be done separately.


getting error after migration to async-rest

I used to be able to manipulate my spectrum app with this library like this
zone = connection.zones.find_by_id(cf_config['zone_id'])
# get all apps
spectrum = zone['spectrum/apps'].get()
apps = spectrum.body[:result]
# find a spectrum app by name
found_app = apps.find {|app| app[:dns][:name] == name}

Now I get the following error from the latest version (4.0.0):
Traceback (most recent call last):
test.rb:20:in `<main>': undefined method `[]' for #<Cloudflare::Zone:0x00007fddb41085d0> (NoMethodError)

Is there a way to do this in the latest version?
FWIW - I am using this library for a chef recipe to register autoscale servers in CF DNS and Spectrum.

This might help you.
https://github.com/socketry/cloudflare/issues/44

I've updated the README with documentation that should help you. If not, can you please make a new issue? Thanks.

By the way, this code won't work:
zone = connection.zones.find_by_id(cf_config['zone_id'])
# get all apps
spectrum = zone['spectrum/apps'].get()
apps = spectrum.body[:result]
# find a spectrum app by name
found_app = apps.find {|app| app[:dns][:name] == name}

In order to do this, you'll need to write something like the following:
spectrum = zone.with(path: 'spectrum/apps')
apps = spectrum.get

I don't have access to test these features though. Happy to screen share some time.


Use dotnet-test

Supercedes #4509 and #4550
VS still doesn't like this. :cry:
Fix #4495
cc @bricelam @Eilon

@bricelam fixed the tests that use roslyn to compile. Everything suceeds on dotnet-test

To the concern of VS tooling: I found how to launch tests from VS. But it is about as ugly as the current command-line setup we have.
Here is what it takes (on my machine...haven't tried elsewhere.)

Remove "net451" from all project.json (source and test)
dotnet-restore from command line. DO NOT restore packages from VS. This will fail.
Unload all except the test project you want to work on. (Test Discovery has a bug that starts test discovery on the wrong projects in the wrong order.)
Build the test project. (This will fail.) But test discovery for Test Explorer should start anyways. (See Output > Tests" to see if it works.)
If tests are discovered, you can run them by selecting the list and rightclick > Run Selected Tests. (Don't "Run all". This tries to build which fails and cancels the test run.)

@natemcmaster - I just ran dotnet restore on command line and build solution in VS. Build fails as usual but all tests are discovered.

@smitpatel Hmm. Weird. Which version of ASP.NET Web tooling? I have
ASP.NET and Web Tools 2015 (RC1 Update 1)   14.1.20203.0 (Help > About MS VS)

RC1 Update 1 - 14.1.11120.0 I am behind!

Well, good news. If you didn't update with the latest "greatest" version of WTE, then these changes shouldn't break you too bad.

@divega @bricelam despite our best efforts, VS will only sort-of work. We need to push this through anyways as the netstandard rename is coming along anyways. Can we merge?


WIP: Generate dist mappings

#476  👈 (View in Graphite)
main

This stack of pull requests is managed by Graphite. Learn more about stacking.


undefined error in isPropertyAccessExpression

TypeScript Version:  3.1.0-dev.20180907
(3.0.3 works fine)

Search Terms:
isPropertyAccessExpression undefined kind
Code
I couldn't replicate this in a small example. The bug can be reproduced with the following steps:

Download https://github.com/ivogabe/gulp-typescript/tree/1b655ff5ea4a84889af509bb433bf6a809aebae3
npm install
npm install<EMAIL_ADDRESS>./node_modules/.bin/tsc -p lib

Expected behavior:
Compilation succeeds without errors
Actual behavior:
[..]/node_modules/typescript/lib/tsc.js:68651
                throw e;
                ^

TypeError: Cannot read property 'kind' of undefined
    at Object.isPropertyAccessExpression ([..]/node_modules/typescript/lib/tsc.js:9975:20)
    at [..]/node_modules/typescript/lib/tsc.js:46202:91
    at Object.forEachEntry ([..]/node_modules/typescript/lib/tsc.js:5689:26)
    at Object.isJSContainerFunctionDeclaration ([..]/node_modules/typescript/lib/tsc.js:46202:25)
    at transformTopLevelDeclaration ([..]/node_modules/typescript/lib/tsc.js:63058:43)
    at visitDeclarationStatements ([..]/node_modules/typescript/lib/tsc.js:63020:26)
    at Object.visitNodes ([..]/node_modules/typescript/lib/tsc.js:51643:48)
    at transformRoot ([..]/node_modules/typescript/lib/tsc.js:62524:33)
    at [..]/node_modules/typescript/lib/tsc.js:1203:42
    at transformRoot ([..]/node_modules/typescript/lib/tsc.js:63498:82)

Related Issues:
#26964
#26978
#26832

Probably due to expando functions, because I the only thing in lib/ is .ts files.

isExpandoFunctionDeclaration assumes that all exports are values, which have valueDeclarations. But namespaces can export types, which do not. Here's a short repro:
function compile(): void { }
namespace compile {
    export interface Settings { }
}

I have a fix and as soon as I add a test, I'll send out a PR.

Thanks for the quick fix! I'll test the next nightly

@sandersn, I am still seeing this behavior with ~3.1.0-dev.20180922

I tried @ivogabe's repro with ~3.1.0-dev.20180922 and that now builds fine.

@blink1073 I’ll try your repro when I’m at my desk. Unless your stack trace is identical, then it’s likely a different issue.

I'm afk, but my stack trace was identical, and was what led me to this issue.

Hmm. I just tried the repro and it doesn't happen with builds from Friday (9/21) or today (9/24) or 3.1.0-dev.20180922.
Note that I couldn't get yarn build:packages to work because of its dependency on jlpm, which seems just to be a custom-wrapped yarn (?). So I followed the tasks in package.json and it looks like build:packages just calls tsc -b src inside packages/metapackage. If that's not right, let me know.

Thanks for checking!   That sounds right as far as procedure.   I'll try again when I get back.

Hmm, this is still happening for me with "typescript": "~3.1.0-dev.20180925":
$ ./node_modules/.bin/tsc -b src
/Users/ssilvester/workspace/jupyter/lab/node_modules/typescript/lib/tsc.js:69059
                throw e;
                ^

TypeError: Cannot read property 'kind' of undefined
    at Object.isPropertyAccessExpression (/Users/ssilvester/workspace/jupyter/lab/node_modules/typescript/lib/tsc.js:10282:20)
    at /Users/ssilvester/workspace/jupyter/lab/node_modules/typescript/lib/tsc.js:46606:91
    at Object.forEachEntry (/Users/ssilvester/workspace/jupyter/lab/node_modules/typescript/lib/tsc.js:5976:26)
    at Object.isJSContainerFunctionDeclaration (/Users/ssilvester/workspace/jupyter/lab/node_modules/typescript/lib/tsc.js:46606:25)
    at transformTopLevelDeclaration (/Users/ssilvester/workspace/jupyter/lab/node_modules/typescript/lib/tsc.js:63465:43)
    at visitDeclarationStatements (/Users/ssilvester/workspace/jupyter/lab/node_modules/typescript/lib/tsc.js:63427:26)
    at Object.visitNodes (/Users/ssilvester/workspace/jupyter/lab/node_modules/typescript/lib/tsc.js:52047:48)
    at transformRoot (/Users/ssilvester/workspace/jupyter/lab/node_modules/typescript/lib/tsc.js:62928:33)
    at /Users/ssilvester/workspace/jupyter/lab/node_modules/typescript/lib/tsc.js:1204:42
    at transformRoot (/Users/ssilvester/workspace/jupyter/lab/node_modules/typescript/lib/tsc.js:63905:82)

False alarm, I ran git clean -dfx and tried again, and all is well.  Thanks again!

No, something is definitely not right.  It is still failing on CI: https://travis-ci.org/blink1073/jupyterlab/jobs/432833170#L464.
git clone https://github.com/blink1073/jupyterlab --branch use-ts-31
cd jupyterlab/packages/metapackage
yarn
yarn build

$ tsc -b src
/Users/ssilvester/temp/jupyterlab/node_modules/typescript/lib/tsc.js:69059
                throw e;
                ^

TypeError: Cannot read property 'kind' of undefined
    at Object.isPropertyAccessExpression (/Users/ssilvester/temp/jupyterlab/node_modules/typescript/lib/tsc.js:10282:20)
    at /Users/ssilvester/temp/jupyterlab/node_modules/typescript/lib/tsc.js:46606:91
    at Object.forEachEntry (/Users/ssilvester/temp/jupyterlab/node_modules/typescript/lib/tsc.js:5976:26)
    at Object.isJSContainerFunctionDeclaration (/Users/ssilvester/temp/jupyterlab/node_modules/typescript/lib/tsc.js:46606:25)
    at transformTopLevelDeclaration (/Users/ssilvester/temp/jupyterlab/node_modules/typescript/lib/tsc.js:63465:43)
    at visitDeclarationStatements (/Users/ssilvester/temp/jupyterlab/node_modules/typescript/lib/tsc.js:63427:26)
    at Object.visitNodes (/Users/ssilvester/temp/jupyterlab/node_modules/typescript/lib/tsc.js:52047:48)
    at transformRoot (/Users/ssilvester/temp/jupyterlab/node_modules/typescript/lib/tsc.js:62928:33)
    at /Users/ssilvester/temp/jupyterlab/node_modules/typescript/lib/tsc.js:1204:42
    at transformRoot (/Users/ssilvester/temp/jupyterlab/node_modules/typescript/lib/tsc.js:63905:82)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

$ cat package.json | grep typescript
    "typescript": "~3.1.0-dev.20180925"

If I change the tsc code to return node && node.kind === 187;, it builds fine.

Interestingly, if I replace tsc.js with the one in the release-3.1 branch, it builds.  If I still see the error with the final 3.1 release I'll open a new issue.

3.1 final is released now

Works now locally and on CI!  :tada:


type-enum fills in with angular values even when a lintrc file is included

Hi, I have a lintrc file that includes 7 values for type-enum. When I write a commit that fails that check, the list of possible type-enums includes 3 values from the angular config: 'revert', 'style' and 'test'.
my lintrc rule looks like this:
"type-enum": [             2,             "always",             [                 "Fix",                 "New",                 "Breaking",                 "Docs",                 "Build",                 "Upgrade",                 "Chore",                 "Update"             ]         ],
and I'm using husky in my package.json with "commitmsg": "conventional-changelog-lint -e",
this is my terminal output when I fail that check:
type must be one of ["Fix", "New", "Breaking", "Docs", "Build", "Upgrade", "Chore", "Update", "revert", "style", "test"] [type-enum]
Thanks for making this library!

Thanks for reporting - I'll check on this over the next days!

Fixed by #30 and released:
❯ npm show conventional-changelog-lint .version
1.1.9


Hosting fonts at jatsby.com

As per spec, cross-domain @import doesn't fly. Nevertheless, Google Fonts manages to host fonts and cross-domain @import isn't an issue. This is thanks to Access-Control-Allow-Origin, which is based on the Cross-Origin Resource Sharing standard.
More information, including how to enable jatsby.com to properly serve fonts, can be found here: https://developers.google.com/fonts/docs/troubleshooting
and here:
http://superuser.com/questions/811907/apache-add-access-control-allow-origin-header
Attempts to make the modifications necessary to the Jatsby Server have been unsuccessful, and frankly this is likely to be the straw that breaks the camel's back for finally moving from OS X (Server) to Linux.
It's entirely possible that this issue won't be remedied until a conversion from OS X to Linux can be achieved. ETA for this is March 2015.... Which isn't too far out, however this more or less prevents a proper v1.0 release of the Jatsby Web Framework.

Actually, that wasn't so bad! It was one of those things where the Internet has an answer, but it's rather buried.
Enabled font hosting on jatsby.com by adding:
ddType font/woff2 .woff2
AddType font/woff .woff
<FilesMatch ".(woff2|woff)$">

Header set Access-Control-Allow-Origin "*"

to the Apache2 config file ("httpd_server_app.conf" on OS X Server).
Courtesy of http://www.cssbakery.com/2010/07/fixing-firefox-font-face-cross-domain_25.html.
Closed.


How to pass unique state data into a resolver?

This issue tracker is for Bug Reports and Feature Requests only.
Please direct requests for help to StackOverflow.  See http://bit.ly/UIR-SOF for details.
This is a:

[ ] Bug Report
[ ] Feature Request
[x] General Query

My version of UI-Router is: (version) 1.0.1
Bug Report
Current Behavior:
(current behavior here)
Expected Behavior:
(expected behavior here)
Link to Plunker that reproduces the issue:
http://bit.ly/UIR-Plunk
Feature Request
(feature request here)
General Query
Please direct general implementation questions to StackOverflow:
http://stackoverflow.com/questions/ask?tags=angularjs,angular-ui-router
Please review the Sample Application which highlights common approaches:
https://github.com/ui-router/sample-app-ng1

[x] I have already asked my question on StackOverflow and nobody could answer the question

[x] I have already reviewed the sample application for examples of common approaches

[x] I believe my question can only be answered by the UI-Router maintainers

(general query here)
Hey there, I am currently rebuilding routing from ng-route to ui-router and have a question about loading custom data from a specific state, into that states resolver.
Example:
 {         url: '/' + locale,         params: {           pageStrings: ['data', 'data2', 'data3', 'data4'],           apiUrl: '/api/home',         },         controller: 'ContentPageCtrl',         name: 'homePageLocale',         resolve: resolvers.content, //an object containing resolver functions         templateUrl:home.html       },
in the snippet above, I am unable to access params:{} inside of the resolvers, however, the data it holds are is required by the resolver in order to obtain the correct content.
I have tried usings $state.params, and $stateParams inside of the resolvers to no avail, including using them inside of the URL.
Any ideas?

Chiming in to give you an example of how i'm accessing param data within a resolve. Make sure you pass $stateParam into the resolve function.
  params: {
    id: undefined,
  },
  resolve: {
    menu: ['Menus', '$stateParams', (Menus, $stateParams) => Menus.get({ id: $stateParams.id })]
}


Possible to use a different version of Ruby in bundler_capistrano?

I have an application that runs on Ruby 2.2.2 and I have the Ruby version specified in the Gemfile: ruby '2.2.2'.
When I try to deploy with heaven, I get the message:
Your Ruby version is 2.1.2, but your Gemfile specified 2.2.2

Is there any way I can deploy a Rails application with a different version of Ruby than heaven itself?

I don't think I've ever tried doing that so I'm not entirely sure. I figured the Bundler.with_clean_env stuff would handle that but perhaps it doesn't. How are you managing your ruby installs?

On our servers we use chruby and we have a .ruby-version file in the root of our project directory containing the text 2.2.2.
I'm running heaven on Heroku, if that helps.
The first few lines of the Gemfile are:
source 'https://rubygems.org'

ruby '2.2.2'

gem 'rails', '4.2.2'

It turns out that Heroku uses the Ruby version from the application Gemfile (i.e. heaven) and doesn't seem to support changing the Ruby version for other commands.
I'm still looking into the possibilty of doing this programmatically but currently I'm not getting anywhere.


Browser: ctrl/cmd+s in custom editor opens native save dialog

In latest github.dev, ctrl+s opens the native save dialog instead of just saving the document like Text Editor.

Duplicate of #148545


[Core] Backport:1.54 Improve HPACK

Cherry-pick https://github.com/grpc/grpc/pull/33597

@ctiller This and older branches than this all failed these tests

//test/core/end2end:h2_proxy_test@large_metadata
//test/core/end2end:h2_ssl_proxy_test@large_metadata

Is this just a wrong test or soething we should address?


No links exist in colebemis.com/feather/

Just a heads up, all the download and icon links on http://colebemis.com/feather/ return 404s.
This was pretty confusing since colebemis.com/feather is the first result on google over the alternative https://feather.netlify.com/ link.

Oops. Thanks for the heads up! I'll have to redirect colebemis.com/feather to feathericons.com. Do you happen to know how to set up a redirect with GitHub pages?

This github help page suggests using this jekyll extension to help with redirects:
https://github.com/jekyll/jekyll-redirect-from

Fixed! colebemis.com/feather should redirect to feathericons.com now.


BUG: tags in comment  with PHP

func();// normal comment to show
func();// <img src='' /> a little wrong here

Sadly this is more or less a known issue. Markup is handled first during highlighting and it may break it when it appears inside PHP code (instead of the opposite: PHP embedded inside HTML)...
As far as I know, nobody has found a solution so far.

Check prism-grammar external parsing add-on for Prism, which uses a grammar to highlight solving all these issues (and more)

I can't reproduce this issue anymore on the Test drive page.


Fix typo

These docs are auto-generated, we need to fix this in the upstream swagger (and/or the generator)


Crash When Generating Multiple Rooms

Describe the bug
As I mentioned in #326 , Infinigen crashed while generating an indoor scene with multiple rooms containing objects.
Steps to Reproduce
python -m infinigen.datagen.manage_jobs --output_folder outputs/huge_dataset_nooverride \
--num_scenes 5 --pipeline_configs local_256GB.gin monocular.gin blender_gt.gin indoor_background_configs.gin \
--pipeline_overrides get_cmd.driver_script='infinigen_examples.generate_indoors' manage_datagen_jobs.num_concurrent=16

This will run tens of hours and then crash.
What version of the code were you using?
v1.8.1
commit 88fb49cde0bbca401601d05d672b31d28e9b45cb (HEAD -> main, origin/main, origin/HEAD)
Merge: 126a41eb ef50641f
Author: Alex Raistrick<EMAIL_ADDRESS>Date:   Fri Aug 23 13:01:23 2024 -0400

    Merge pull request #252 from princeton-vl/develop

    v1.8.1

What command did you run?
python -m infinigen.datagen.manage_jobs --output_folder outputs/huge_dataset_nooverride \
--num_scenes 5 --pipeline_configs local_256GB.gin monocular.gin blender_gt.gin indoor_background_configs.gin \
--pipeline_overrides get_cmd.driver_script='infinigen_examples.generate_indoors' manage_datagen_jobs.num_concurrent=16

What are your FULL output logs?
crash_summaries.txt
First Sample
92139964677_0_log.out.txt
92139964677_0_log.err.txt
Second Sample
80530831448_0_log.out.txt
80530831448_0_log.err.txt
If this is your first time running Infinigen, what are the full install logs?**
Not the first time running. If turn on --configs singleroom.gin and --overrides compose_indoors.restrict_single_supported_roomtype=True, it does not lead to a crash.
Platform

OS & OS Version: Ubuntu 24.04.1 LTS
GPU: 4090
GPU Driver Version: 535
RAM (GB): 64GB

Additional context
I suspect this might be a memory leak issue. I noticed that swap usage was over 85%, while memory utilization was only around 50%. I think it's possible that memory is leaking during execution and eventually consuming all available memory. I've just installed Prometheus on my system and started another execution with the same configuration to monitor memory usage. I'll update you once I have the results.

It seems like there are some kind of memory leak. I'm using python -m infinigen.datagen.manage_jobs --output_folder outputs/single_data_test --num_scenes 1 --pipeline_configs local_64GB.gin monocular.gin blender_gt.gin indoor_background_configs.gin  --pipeline_overrides get_cmd.driver_script='infinigen_examples.generate_indoors' manage_datagen_jobs.num_concurrent=16 running single job, and it takes more than 55G of ram gradually then crashed.


Update runIf/runIfNot to run_if/run_if_not to be consistent across .ci.yaml

Most of variables in .ci.yaml have been using snake case fomat, but runIf/runIfNot were created as camel case. Nit to keep all variables consistent across all repos.
This also needs cocoon change to reference the correct name.
Related: https://github.com/flutter/flutter/issues/143671

This feature was removed.


[8.x] Enable mailgun batch sending

This patch enables batch sending of Mailgun, while still using Mailable class for mail.
Nothing will happen if the application developer does not add 'batch_sending' => true to config/services.php, mailgun section.
Have tested in my own project which requires https://github.com/leondeng/laravel-batch-mailgun.

Thanks for your pull request to Laravel!
Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.
If possible, please consider releasing your code as a package so that the community can still take advantage of your contributions!
If you feel absolutely certain that this code corrects a bug in the framework, please "@" mention me in a follow-up comment with further explanation so that GitHub will send me a notification of your response.

@taylorotwell ,
Thanks, Taylor.
This patch is not supposed to fix any bug, but only enhance the Mail stuff of Laravel when using Mailgun as transport.
I will take your advice and release it as a package.
Cheers!


Update grpc zlib dependency

zlib version 1.3.1.bcr.3 resolved some build issues as per the description in the PR https://github.com/bazelbuild/bazel-central-registry/pull/2498

Hello @bazelbuild/bcr-maintainers, modules without existing maintainers (grpc) have been updated in this PR. Please review the changes.


fixed build

Issue: https://github.com/FalcoSuessgott/gitget/issues/6
tested on mac.
updated he go mods

thanks!


API 31: DEVICE SECURITY COMPROMISED dialog vanishes automatically

On API 24, click CREATE NEW WALLET and then the dialog pops up.
But on API 31, it pops up immediately when the app starting, and disappeared automatically.
https://user-images.githubusercontent.com/735708/148150883-5ad5a8e2-bbc7-4da5-9ab2-0f1c0551899f.mp4

When first running, start HomeActivity, the dialog shows, then HomeActivity finished, start SplashActivity, click create new wallet, navigate to HomeActivity, the dialog not shown, because it was marked as showed once.
I think move the checkRoot() to SplashActivity can simplify the logic.


Set-CsUser cmdlet returns an error

Hi! When we try to run the Set-CsUser on S4B Online then we get the following error "A parameter cannot be found that matches parameter name 'OnPremLineUri'. This article https://docs.microsoft.com/en-us/skypeforbusiness/troubleshoot/online-configuration/admins-cant-use-set-csuser states that this cmdlet cannot be used with parameters mentioned in above article. Please advise which cmdlet should be used to configure direct routing.

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

ID: df318fdb-6d58-86f8-de31-6eca533a9746
Version Independent ID: a2248abf-bdf0-2c22-2604-74b482156684
Content: Configure Direct Routing
Content Source: Teams/direct-routing-configure.md
Service: msteams
GitHub Login: @CarolynRowe
Microsoft Alias: crowe

@Larryngolog Thank you for submitting feedback and contributing to the docs. We are currently investigating this.

@Larryngolog Thank you for reaching out. Please have a look at this article and let me know if it helps at all. https://docs.microsoft.com/powershell/module/skype/new-csonlinevoiceroute?view=skype-ps

Hi! Unfortunately not. This cmdlet defines the route that is taken by specific numbers but does not assign these numbers to users.
We have checked internally on different environments and it looks like the cmdlet is working as described in the "Configure Direct Routing". It looks like the Troubleshooting article is not correct or does not include information under which scenarios set-csuser will not work.

@Larryngolog thanks for clearing that up. Is this the troubleshooting article you are referring to that doesn't reflect correctly. https://docs.microsoft.com/microsoftteams/direct-routing-monitor-and-troubleshoot

@CarolynRowe

@CarolynRowe Could you please help out with this issue? Thanks!

@CarolynRowe Could you please help out with this issue? Thanks!

What is the ask specifically?  To update the troubleshooting article?  To configure Direct Routing, you should be following the instructions in Configure Direct Routing, which were correct?  Can you explain what sent you to the troubleshooting article?

@lindspea Please see Carolyn's comment.

@Larryngolog please see @CarolynRowe comments above and elaborate please. Thank you for taking the time to help improve MS Docs.

Hi @CarolynRowe  as I mentioned we were trying to configure Direct Routing using the provided cmdlet and got an error. We searched for the error and found the troubleshooting article. I thought that there are contrary information in this article and the troubleshooting articles. So either article needs clarification as this article states that you should use the "Set-CsUser" cmdlet with -EnterpriseVoiceEnabled HostedVoiceMail and OnPremLineURI parameters, and the troubleshooting one states that "AudioVideoDisabled is the only parameter that you can use together with the Set-CsUser cmdlet in Skype for Business Online". When we get error when configuring Direct Routing we get contradictory statements and do not know if this is by design or not.

@CarolynRowe Following up on this issue. Thanks!

Please follow the instructions under Configure Direct Routing.  I will follow up with the PMs about whether we need to update the troubleshooting content.  If you continue to have problems configuring Direct Routing, please contact technical support.

In case anyone else runs into this issue, we resolved it by adding the "Skype for Business Administrator" role to the admin user - despite being Teams Only tenant-wide, "Teams Service Administrator" was not enough to get this property when connecting to the online connector.


Vit solution fixes

This should fix a couple of runtime errors I got when running in colab the solutions to the ViT tutorials, in particular:

in scaled_dot_product the final call to jnp.sweepaxes was missing the axis1 and axis2 positional parameters
in the MultiHeadAttention module the __call__ method was taking a single x parameter but was still using input_q and input_kv in the implementation (as in the original version of the tutorial); I realigned it to the input_q + input_kv params versions as I found it more general and easier to understand, but obviously it could also be fixed in a way that uses a single x param (which might be more intuitive when reasoning about self-attention)

Let me know if there's anything to be changed further, I'd be more than happy to give a hand.
Thanks a lot for the amazing tutorials!

Thanks for the PR addressing the inconsistencies in MultiHeadDotProductAttention.
Could you also please look at how MultiHeadDotProductAttention is used later on in AttentionBlock, and make sure that those required changes are in this PR too?

Thanks for the PR addressing the inconsistencies in MultiHeadDotProductAttention.
Could you also please look at how MultiHeadDotProductAttention is used later on in AttentionBlock, and make sure that those required changes are in this PR too?

Yeah, sure, I just need to find some time (it might very likely be after the weekend).
While I'm at it, I'll also make sure to test the whole notebook in colab to double check everything works as expected.


fix(http): use route name from 'r.Pattern' instead

I have a Go project running latest Chi - v5.1.0 and Go 1.22.x. Every root span becomes: GET /*/*/*. I don't think this is an issue on Chi though. Hoping this would fix that.

So http.Request.Pattern only exists on Go 1.23, yet the route matching exists on Go 1.22 :/

Looks good to me. Not too fond of the new package name (traceutils), but can't think of something better at the moment.
Please update changelog as well.


Working on generating field. Currently field, player & hat are generated

Yay, @Akuli I've spent the last two hours debugging what I wrote yesterday, and I've found several of the comments you've made without seeing your comments! Points to me! :D
There are more things to resolve here, so I will get to the things that I have not yet resolved. I would need help to continue debugging. As soon as I choose too high values (field size and hole percentage) the while loop seems to get stuck in an infinite loop.

@Akuli I also had a really interesting git adventure. Found a bug, so I started doing git checkout commit-hash to find it. Then to get back, I did the same command to get to the latest commit. However, I didn't know that I left my branch that way. So I did all work on "no branch".
After some panic, and then some googling I found git reflog -> git cherry-pick Thank god..

So I did all work on "no branch".

I see you didn't use git status, which displays a red warning message in "no branch" mode :)

I decided to come to irc a bit earlier today. I'm there now :)